Cisco Cisco IOS Software Release 12.2(33)SRE
AToM Static Pseudowire Provisioning
How to Provision an AToM Static Pseudowire
5
Any Transport over MPLS
DETAILED STEPS
Step 1
show mpls l2transport vc detail
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:
labels (such as LDP). For static pseudowire configuration, the value of the signaling protocol field
should be Manual. Following is sample output:
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
ping mpls pseudowire ipv4-address vc-id vc-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:
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:
Router# ping mpls pseudowire 10.7.1.2 vc-id 1001
Sending 5, 100-byte MPLS Echos to 10.7.1.2,
timeout is 2 seconds, send interval is 0 msec:
Codes: '!' - success, 'Q' - request not sent, '.' - timeout,
'L' - labeled output interface, 'B' - unlabeled output interface,
'D' - DS Map mismatch, 'F' - no FEC mapping, 'f' - FEC mismatch,
'M' - malformed request, 'm' - unsupported tlvs, 'N' - no label entry,
'P' - no rx intf label prot, 'p' - premature termination of LSP,
'R' - transit router, 'I' - unknown upstream index,
'X' - unknown return code, 'x' - return code 0
Type escape sequence to abort.
!!!!!
Success rate is 100 percent (5/5), round-trip min/avg/max = 1/2/4 ms