Configuring Any Transport over MPLS Pseudowire Provisioning

This chapter describes how to configure static pseudowires in cases where you cannot use directed control protocols, such as Label Distribution Protocol or Resource Reservation Protocol over traffic-engineered (RSVP-TE) tunnels.

This chapter includes the following sections:

Finding Feature Information

Your software release might not support all the features documented in this module. For the latest caveats and feature information, see the Bug Search Tool at https://tools.cisco.com/bugsearch/ and the release notes for your 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 “New and Changed Information” chapter or the Feature History table below.

Licensing Requirements for Any Transport over MPLS Pseudowire Provisioning

The following table shows the licensing requirements for this feature:

Product
License Requirement

Cisco NX-OS

Layer 2 MVPN requires an MPLS license. For a complete explanation of the Cisco NX-OS licensing scheme and how to obtain and apply licenses, see the Cisco NX-OS Licensing Guide.

Guidelines and Limitations for Any Transport over MPLS Pseudowire Provisioning

Any Transport over MPLS (AToM) pseudowire provisioning has the following guidelines and limitations:

  • A traffic engineering (TE) tunnel can be configured and the Interior Gateway Protocol (IGP) can use the tunnel as the outgoing route for pseudowire packets. For more information, see the “Configuring the Basic MPLS TE” chapter.
  • The following functionality is not supported for static pseudowires:

blank.gif Tunnel stitching is not supported.

blank.gif Pseudowire redundancy is not supported.

blank.gif Autosensing of the virtual circuit type for Ethernet over MPLS (EoMPLS) is not supported.

Configuring Any Transport over MPLS Pseudowire Provisioning

SUMMARY STEPS

1.blank.gif configure terminal

2.blank.gif mpls label range min-label max-label [ static min-static-label max-static-label ]

3.blank.gif [ no ] interface pseudowire pw-id

4.blank.gif signaling protocol none

5.blank.gif neighbor peer-ip-address vc-id

6.blank.gif encapsulation mpls

7.blank.gif label local remote

8.blank.gif no shutdown

9.blank.gif (Optional) copy running-config startup-config

DETAILED STEPS

Command
Purpose

Step 1

configure terminal

 

switch# configure terminal

switch(config)#

Enters global configuration mode.

Step 2

mpls label range min-label max-label [ static min-static-label max-static-label ]

 

switch(config)# mpls label range 20 199 static

200 400

Reserves a range of labels for static label assignments.

  • The values for the min-label and max-label arguments identify a generic group of reserved label numbers.
  • The optional static keyword reserves a group of label numbers specifically for assigning static pseudowires labels.
  • The range is from 16 to 471804 for all arguments.

Step 3

[ no ] interface pseudowire pw-id

 

switch(config)# interface pseudowire 12

switch(config-if-pseudowire)#

Enters interface pseudowire configuration mode and configures a static pseudowire logical interface.

  • The pw-id argument is a unique per-interface identifier for this pseudowire. The range is from 1 to 200000. The range for a static pseudowire is from 1 to 8192.

Note You can use the no form of this command to delete the pseudowire interface and the associated configuration.

Step 4

signaling protocol none

 

switch(config-if-pseudowire)# signaling protocol none

Disables signaling to use manually configured pseudowires.

Step 5

neighbor peer-ip-address vc-id

 

switch(config-if-pseudowire)# neighbor 10.2.2.2 100

Configures a emulated virtual circuit for this interface.

  • The combination of the peer-ip-address and vc-id arguments must be unique on a device.
  • The peer IP address is the address of the provider edge (PE) peer.
  • The vc-id argument is an identifier for the virtual circuit between devices. The valid range is from 1 to 4294967295.

Step 6

encapsulation mpls

 

switch(config-if-pseudowire)# encapsulation mpls

switch(config-pseudowire-mpls)#

Specifies MPLS encapsulation for this profile.

Step 7

label local remote

 

switch(config-pseudowire-mpls)# label 200 400

Sets a value for the local pseudowire label and the remote pseudowire label.

  • The value for the local and remote arguments must be within the range specified by the mpls label range command with the static keyword.

Step 8

no shutdown

 

switch(config-pseudowire-mpls)# no shutdown

Brings the port administratively up.

Step 9

copy running-config startup-config

 

switch(config-pseudowire-mpls)# copy running-config startup-config

(Optional) Saves this configuration change.

Verifying Any Transport over MPLS Pseudowire Provisioning

To verify pseudowire configuration information, perform the following task:

Command
Purpose

show l2vpn atom vc detail

Displays detailed information about Any Transport over MPLS (AToM) virtual circuits (VCs) and static pseudowires that have been enabled to route Layer 2 packets on a device.

Additional References for Any Transport over MPLS Pseudowire Provisioning

For additional information about provisioning static pseudowires for Any Transport over MPLS (AToM), see the following section:

Related Documents

Related Topic
Document Title

Interface commands

Cisco Nexus 7000 Series NX-OS Interfaces Command Reference

VLAN commands

Cisco Nexus 7000 Series NX-OS Layer 2 Switching Command Reference

Traffic engineering tunneling

“Configuring the Basic MPLS TE” chapter

Feature Information for Any Transport over MPLS Pseudowire Provisioning

Table 28-1 lists the release history for this feature.

Table 28-1 Feature Information for Any Transport over MPLS Pseudowire Provisioning

Feature Name
Releases
Feature Information

Any Transport over MPLS Pseudowire Provisioning

6.2(2)

The Any Transport over MPLS (AToM) Pseudowire Provisioning feature allows you to provision an AToM 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 command-line interface.