Finding Feature Information

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.

Prerequisites for MPLS Pseudowire Status Signaling

Before configuring this feature, make sure that both peer routers are capable of sending and receiving pseudowire status messages.

Restrictions for MPLS Pseudowire Status Signaling

Both peer routers must support the ability to send and receive pseudowire status messages in label advertisement and label notification messages. If both peer routers do not support pseudowire status messages, Cisco recommends that you disable the messages with the
nostatus command.

This feature is not integrated with Any Transport over MPLS (AToM) Virtual Circuit Connection Verification (VCCV).

This feature is not integrated with Bidirectional Forwarding Detection (BFD).

The standby and required switchover values from IETF draft-muley-pwe3-redundancy-02.txt are not supported.

How MPLS Pseudowire Status Switching Works

The pseudowire status messages are sent in label advertisement and label notification messages if the peer also supports the MPLS Pseudowire Status Signaling feature. You can issue the
showmplsl2transportvcdetail command to show that both the local and remote routers support pseudowire status messages. The following example shows the line of output to look for:

Router# showmplsl2transportvcdetail

.

.

.

status TLV support (local/remote): enabled/supported

How MPLS Pseudowire Status Switching Works using the commands associated with the L2VPN Protocol-Based CLIs feature

The pseudowire status messages are sent in label advertisement and label notification messages if the peer also supports the MPLS Pseudowire Status Signaling feature. You can issue the
showl2vpnatomvcdetail command to show that both the local and remote routers support pseudowire status messages. The following example shows the line of output to look for:

Device# showl2vpnatomvcdetail

.

.

.

status TLV support (local/remote): enabled/supported

When One Router Does Not Support MPLS Pseudowire Status Signaling

The peer routers must support the ability to send and receive pseudowire status messages in label advertisement and label notification messages. If one router does not support pseudowire status messages, Cisco recommends that you disable the messages with the
nostatus command. This returns the router to label withdraw mode.

If the peer does not support the MPLS Pseudowire Status Signaling feature, the local router changes its mode of operation to label withdraw mode. You can issue the
showmplsl2transportvcdetail command to show that the remote router does not support pseudowire status messages. The following example shows the line of output to look for:

Router# showmplsl2transportvcdetail

.

.

.

status TLV support (local/remote): enabled/not supported

When you issue the following
debugmplsl2transportvccommands, the messages show that the peer router does not supportthe MPLS Pseudowire Status Signaling feature and that the local router is changing to withdraw mode, as shown in bold in the following example:

When One Router Does Not Support MPLS Pseudowire Status Signaling using the commands associated with the L2VPN Protocol-Based CLIs feature

The peer routers must support the ability to send and receive pseudowire status messages in label advertisement and label notification messages. If one router does not support pseudowire status messages, we recommend that you disable the messages with the nostatus command. This returns the router to label withdraw mode.

If the peer does not support the MPLS Pseudowire Status Signaling feature, the local router changes its mode of operation to label withdraw mode. You can issue the showl2vpnatomvcdetail command to show that the remote router does not support pseudowire status messages. The following example shows the line of output to look for:

Device# show l2vpn atom vc detail

.

.

.

status TLV support (local/remote): enabled/not supported

When you issue the following debugl2vpn atomvc commands, the messages show that the peer router does not support the MPLS Pseudowire Status Signaling feature and that the local router is changing to withdraw mode, as shown in the following example:

How to Configure MPLS Pseudowire Status Signaling

Enabling MPLS Pseudowire Status Signaling

Perform the following task to enable the router to send pseudowire status to a peer router even when the attachment circuit is down. If both routers do not support pseudowire status messages, then disable the messages with the
nostatus command.

SUMMARY STEPS

1.enable

2.configureterminal

3.pseudowire-classname

4.status

5.encapsulationmpls

6.exit

7.exit

8.showmplsl2transportvcdetail

DETAILED STEPS

Command or Action

Purpose

Step 1

enable

Example:

Router> enable

Enables privileged EXEC mode.

Enter your password if prompted.

Step 2

configureterminal

Example:

Router# configure terminal

Enters global configuration mode.

Step 3

pseudowire-classname

Example:

Router(config)# pseudowire-class atom

Establishes a pseudowire class with a name that you specify and enters pseudowire class configuration mode.

Step 4

status

Example:

Router(config-pw)# status

(Optional) Enables the router to send pseudowire status messages to the peer router through label advertisement and label notification messages.

Note

By default, status messages are enabled. This step is included only in case status messages have been disabled.

If you need to disable status messages because both peer routers do not support this functionality, enter the
nostatuscommand.

Perform this task to enable the router to send pseudowire status to a peer router even when the attachment circuit is down. If both routers do not support pseudowire status messages, then disable the messages with the
nostatus command.

SUMMARY STEPS

1.enable

2.configureterminal

3.interfacepseudowirenumber

4.status

5.encapsulationmpls

6.neighborpeer-address vcid-value

7.exit

8.exit

9.showl2vpnatomvcdetail

DETAILED STEPS

Command or Action

Purpose

Step 1

enable

Example:

Router> enable

Enables privileged EXEC mode.

Enter your password if prompted.

Step 2

configureterminal

Example:

Device# configure terminal

Enters global configuration mode.

Step 3

interfacepseudowirenumber

Example:

Device(config)# interface pseudowire 1

Establishes an interface pseudowire with a value that you specify and enters pseudowire configuration mode.

Step 4

status

Example:

Device(config-pw)# status

(Optional) Enables the router to send pseudowire status messages to the peer router through label advertisement and label notification messages.

Note

By default, status messages are enabled. This step is included only in case status messages have been disabled.

If you need to disable status messages because both peer routers do not support this functionality, enter the
nostatuscommand.

Example MPLS Pseudowire Status Signaling

The following example configures the MPLS Pseudowire Status Signaling feature on two PE routers. By default, status messages are enabled. The
status command is included in this example in case status messages have been disabled.

The following example configures the MPLS Pseudowire Status Signaling feature on two PE routers. By default, status messages are enabled. The
status command is included in this example in case status messages have been disabled.

RFCs

RFC

Title

No new or modified RFCs are supported by this feature, and support for existing RFCs has not been modified by this feature.

--

Technical Assistance

Description

Link

The Cisco Support and Documentation website provides online resources to download documentation, software, and tools. Use these resources to install and configure the software and to troubleshoot and resolve technical issues with Cisco products and technologies. Access to most tools on the Cisco Support and Documentation website requires a Cisco.com user ID and password.

Feature Information for

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 MPLS Pseudowire Status Signaling

Feature Name

Releases

Feature Information

MPLS Pseudowire Status Signaling

Cisco IOS XE Release 2.3

The MPLS Pseudowire Status Signaling feature enables you to configure the router so it can send pseudowire status to a peer router, even when the attachment circuit is down.

The following commands were introduced or modified:
debugmplsl2transportvc,
showmplsl2transportvc,
status (pseudowire class).