The AToM Static Pseudowire Provisioning feature allows provisioning an Any Transport over Multiprotocol Label Switching (MPLS) (AToM) static pseudowire without the use of a directed control connection. In environments that do not or cannot use directed control protocols, this feature provides a means for provisioning the pseudowire parameters statically at the Cisco IOS command-line interface (CLI).
Your software release may not support all the features documented in this module. For the latest caveats and feature information, see
Bug Search Tool and the release notes for your platform and software release. To find information about the features documented in this module, and to see a list of the releases in which each feature is supported, see the feature information table at the end of this module.
Use Cisco Feature Navigator to find information about platform support and Cisco software image support. To access Cisco Feature Navigator, go to
www.cisco.com/go/cfn. An account on Cisco.com is not required.
Restrictions for AToM Static Pseudowire Provisioning
The following parameters are exchanged using directed control protocol messages on pseudowires, but cannot be changed using the AToM Static Pseudowire Provisioning feature introduced in Cisco IOS Release 12.33(SRB). Instead, the software has preconfigured defaults.
The Virtual Circuit Connectivity Verification (VCCV) options used for fault detection, isolation, and verification at both ends of the connection are set as follows:
Control channel type 1 sets the control word.
Control channel type 2 sets the MPLS router alert label.
Connectivity verification type 2 sets the label switched path (LSP) ping command.
In Cisco IOS Release 12.2(33)SRE, support for cell packing for static pseudowires was added. This feature has the following restrictions:
Both provider-edge routers (PEs) must run Cisco IOS Release 12.2(33)SRE, and the maximum number of cells that can be packed must be set to the same value on each PE router.
Autosensing of the virtual circuit type for Ethernet over MPLS is not supported.
Additionally, the following functionality is not supported for static pseudowires:
Sequence number resynchronization--configured by the sequencing function in the pseudowire-class command--is not supported because the sequence number resynchronization is done when the Label Distribution Protocol (LDP) software sends an LDP Label Release or Withdraw message followed by a Label Request or Mapping message, and static pseudowires do not use LDP.
Tunnel stitching is not supported because it requires an extension of the neighbor command to start the mode that allows configuring static pseudowire parameters such as remote and local labels. Note that a tunnel switch point can be configured using a different static label command. The tunnel switch point will not process control words, but label swapping will occur.
Pseudowire redundancy is not supported because it requires using a directed control protocol between the peer provider edge routers.
Information About AToM Static Pseudowire Provisioning
The AToM Static Pseudowire Provisioning feature allows you to configure static pseudowires in cases where you cannot use directed control protocols. .In most cases, pseudowires are dynamically provisioned using LDP or another directed control protocol, such as Resource Reservation Protocol over traffic-engineered tunnels (RSVP-TE), to exchange the various parameters required for these connections.
The AToM Static Pseudowire Provisioning feature is platform-independent, but has been tested on only the Cisco 7600 series routers.
Benefits of Statically Provisioned Pseudowires
This feature allows provisioning an AToM label switching static pseudowire without the use of a directed control connection. This feature also includes static provisioning of the tunnel label and the pseudowire label.
In this configuration task, you use options in the xconnect Ethernet interface configuration command to specify a static connection, and mpls commands in xconnect mode to statically set the following pseudowire parameters:
The label must be an unused static label within the static label range configured using the mplslabelrange command.
The mplslabel command checks the validity of the label entered and displays an error message if it is not valid. The label supplied for the remote-pseudowire-labelargument must be the value of the peer PE's local pseudowire label.
Step 6
[no]mplscontrol-word
Example:
Router(config-if-xconn)# no mpls control-word
Sets whether the MPLS control word is sent.
This command must be set for Frame Relay data-link connection identifier (DLCI) and ATM adaptation layer 5 (AAL5) attachment circuits. For other attachment circuits, the control word is included by default.
If you enable inclusion of the control word, it must be enabled on both ends of the connection for the circuit to work properly.
Inclusion of the control word can be explicitly disabled using the nomplscontrol-word command.
Step 7
exit
Example:
Router(config-if-xconn)# exit
Exits the configuration mode.
Continue entering the exitcommand at the router prompt until you reach the desired configuration mode.
Verifying the AToM Static Pseudowire Configuration
To verify the AToM static pseudowire configuration, use the showrunning-config EXEC command. To verify that the AToM static pseudowire was provisioned correctly, use the showmplsl2transportvcdetailand pingmplspseudowireEXEC commands as described in the following steps.
SUMMARY STEPS
1.showmplsl2transportvcdetail
2.pingmplspseudowireipv4-addressvc-idvc-id
DETAILED STEPS
Step 1
showmplsl2transportvcdetail
For nonstatic pseudowire configurations, this command lists the type of protocol used to send the MPLS labels (such as LDP). For static pseudowire configuration, the value of the signaling protocol field should be Manual. Following is sample output:
Example:
Router# show mpls l2transport vc detail
Local interface: Et1/0 up, line protocol up, Ethernet up
Destination address: 10.0.1.1, VC ID: 200, VC status: up
Output interface: Et3/0, imposed label stack {17}
Preferred path: not configured
Default path:
Next hop: 10.0.0.2
Create time: 00:27:27, last status change time: 00:27:24
Signaling protocol: Manual
MPLS VC labels: local 17, remote 17
Group ID: local 0, remote 0
MTU: local 1500, remote 1500
Sequencing: receive disabled, send disabled
VC statistics:
packet totals: receive 193, send 193
byte totals: receive 19728, send 23554
packet drops: receive 0, send 0
Step 2
pingmplspseudowireipv4-addressvc-idvc-id
Because there is no directed control protocol exchange of parameters on a static pseudowire, both ends of the connection must be correctly configured. One way to detect mismatch of labels or control word options is to send an MPLS pseudowire LSP ping command as part of configuration task, and then reconfigure the connection if problems are detected. An exclamation point (!) is displayed when the ping command is successfully sent to its destination. An example of command use and output follows:
The following examples show the configuration commands for an AToM
static pseudowire connection between two PEs, PE1 and PE2.
The
mplslabelrangestatic command must be used to configure the static
label range prior to provisioning the AToM static pseudowire.
Router# configure terminal
Router(config)# mpls label range 200 16000 static 16 199
% Label range changes will take effect at the next reload.
The
mplsip command must also be configured on the
core-facing interface of both PE1 and PE2 (which is also done for directed
control protocol signaled pseudowires). Following is a configuration example:
Router(config)# interface Ethernet 0/0
Router(config-if)# description Backbone interface
Router(config-if)# ip address 10.0.0.1 255.255.255.0
Router(config-if)# mpls ip
Router(config-if)# exit
Following is an example AToM static pseudowire configuration for PE1:
This feature also allows tunnel labels to be statically configured
using the
mplsstaticbindingipv4vrf command. See the MPLS Static Labels feature module and the Cisco
IOS Multiprotocol Label Switching Command Reference for information about
static labels and the
mplsstaticbindingipv4vrfcommand.
Additional References
The following sections provide references related to the AToM Static Pseudowire Provisioning feature.
The Cisco Support website provides extensive online resources, including documentation and tools for troubleshooting and resolving technical issues with Cisco products and technologies.
To receive security and technical information about your products, you can subscribe to various services, such as the Product Alert Tool (accessed from Field Notices), the Cisco Technical Services Newsletter, and Really Simple Syndication (RSS) Feeds.
Access to most tools on the Cisco Support website requires a Cisco.com user ID and password.
Feature Information for AToM Static Pseudowire Provisioning
The following table provides release information about the feature or features described in this module. This table lists only the software release that introduced support for a given feature in a given software release train. Unless noted otherwise, subsequent releases of that software release train also support that feature.
Use Cisco Feature Navigator to find information about platform support and Cisco software image support. To access Cisco Feature Navigator, go to
www.cisco.com/go/cfn. An account on Cisco.com is not required.
Table 1
Feature Information for AToM Static Pseudowire Provisioning
Feature Name
Releases
Feature Information
AToM Static Pseudowire Provisioning
12.2(33)SRB 12.2(33)SRE
This feature allows provisioning an AToM static pseudowire without the use of a directed control protocol connection.
The AToM Static Pseudowire feature is platform-independent, but has been tested on only the Cisco 7600 series routers for Cisco IOS Release 12.33(SRB).
In Cisco IOS Release 12.2(33)SRE, the L2VPN Support for Cell Packing on Static PW feature was added.
The following commands were introduced or modified by this feature:
cell-packing,
mplscontrol-word,
mplslabel,
showmplsl2transportvc,
xconnect.
Cisco and the Cisco logo are trademarks or registered trademarks of Cisco and/or its affiliates in the U.S. and other countries. To view a list of Cisco trademarks, go to this URL:
www.cisco.com/go/trademarks. Third-party trademarks mentioned are the property of their respective owners. The use of the word partner does not imply a partnership relationship between Cisco and any other company. (1110R)
Any Internet Protocol (IP) addresses and phone numbers used in this document are not intended to be actual addresses and phone numbers. Any examples, command display output, network topology diagrams, and other figures included in the document are shown for illustrative purposes only. Any use of actual IP addresses or phone numbers in illustrative content is unintentional and coincidental.