Table Of Contents
Configuring Pseudowire
Understanding Pseudowire
Structure-Agnostic TDM over Packet
Structure-Aware TDM Circuit Emulation Service over Packet-Switched Network
Transportation of Service Using ATM over MPLS
Transportation of Service Using Ethernet over MPLS
Limitations
Configuring Pseudowire
Using Pseudowire Classes
Using CEM Classes
Configuring a Backup Peer
Configuring Structure-Agnostic TDM over Packet (SAToP)
Configuring Circuit Emulation Service over Packet-Switched Network (CESoPSN)
Configuring a CESoPSN Pseudowire with UDP Encapsulation
Configuring Transportation of Service Using ATM over MPLS
Configuring the Controller
Configuring an IMA Interface
Configuring the ATM over MPLS Pseudowire Interface
Configuring Transportation of Service Using Ethernet over MPLS
Configuring VLAN Mode
Configuration Examples for Pseudowire
Asymmetric PWE3 Configuration
PWE3 Redundancy Configuration
TDM over MPLS Configuration
CESoPSN with UDP Configuration
ATM over MPLS Configuration
Ethernet over MPLS Configuration
Configuring Pseudowire
Cisco Pseudowire Emulation Edge-to-Edge (PWE3) allows you to transport traffic using traditional services such as E1/T1 over a packet-based backhaul technology such as MPLS or IP. A pseudowire (PW) consists of a connection between two provider edge (PE) devices that connects two attachment circuits (ACs), such as ATM VPIs/VCIs or E1/T1 links.
The following sections describe how to configure pseudowire on the Cisco MWR 2941:
•
Understanding Pseudowire
•
Configuring Pseudowire
•
Configuration Examples for Pseudowire
Figure 22-1 Cisco MWR 2941 Router in a PWE3—Example
Understanding Pseudowire
PWs manage encapsulation, timing, order, and other operations in order to make it transparent to users; the PW tunnel appears as an unshared link or circuit of the emulated service.
There are limitations that impede some applications from utilizing a PW connection. For more information, see the section describing the PW service.
Cisco supports the following standards-based PWE types:
•
Structure-Agnostic TDM over Packet
•
Structure-Aware TDM Circuit Emulation Service over Packet-Switched Network
•
Transportation of Service Using ATM over MPLS
•
Transportation of Service Using Ethernet over MPLS
Structure-Agnostic TDM over Packet
SAToP encapsulates TDM bit-streams (T1, E1, T3, E3) as PWs over PSNs. It disregards any structure that may be imposed on streams, in particular the structure imposed by the standard TDM framing.
The protocol used for emulation of these services does not depend on the method in which attachment circuits are delivered to the PEs. For example, a T1 attachment circuit is treated the same way for all delivery methods, including: PE on copper, multiplex in a T3 circuit, mapped into a virtual tributary of a SONET/SDH circuit, or carried over a network using unstructured Circuit Emulation Service (CES). Termination of specific carrier layers used between the PE and circuit emulation (CE) is performed by an appropriate network service provider (NSP).
For instructions on how to configure SAToP, see Configuring Structure-Agnostic TDM over Packet (SAToP). For a sample SAToP configuration, see Configuration Examples for Pseudowire.
Structure-Aware TDM Circuit Emulation Service over Packet-Switched Network
CESoPSN encapsulates structured (NxDS0) TDM signals as PWs over PSNs. It complements similar work for structure-agnostic emulation of TDM bit-streams, such as PWE3-SAToP.
Emulation of NxDS0 circuits saves PSN bandwidth and supports DS0-level grooming and distributed cross-connect applications. It also enhances resilience of CE devices due to the effects of loss of packets in the PSN.
CESoPSN supports channel-associated signaling (CAS) for E1 and T1 interfaces. CAS provides signaling information within each DS0 channel as opposed to using a separate signaling channel. CAS also referred to as in-band signaling or robbed bit signaling.
For instructions on how to configure SAToP, see Configuring Circuit Emulation Service over Packet-Switched Network (CESoPSN). For a sample SAToP configuration, see Configuration Examples for Pseudowire.
Transportation of Service Using ATM over MPLS
An Asynchronous Transfer Mode (ATM) over MPLS PW is used to carry ATM cells over an MPLS network. It is an evolutionary technology that allows you to migrate packet networks from legacy networks, yet provides transport for legacy applications. ATM over MPLS is particularly useful for transporting 3G voice traffic over MPLS networks.
You can configure ATM over MPLS in the following modes:
•
N-to-1 Cell Mode—Maps one or more ATM virtual channel connections (VCCs) or virtual permanent connection (VPCs) to a single pseudowire.
•
1-to-1 Cell Mode—Maps a single ATM VCC or VPC to a single pseudowire.
•
Port Mode—Map one physical port to a single pseudowire connection.
The Cisco MWR 2941 also supports cell packing and PVC mapping for ATM over MPLS pseudowires.
Note
Release 15.0(1)MR does not support ATM over MPLS N-to-1 Cell Mode or 1-to-1 Cell Mode.
For more information about how to configure ATM over MPLS, see Configuring Transportation of Service Using ATM over MPLS. For sample ATM over MPLS configurations, see Configuration Examples for Pseudowire.
Transportation of Service Using Ethernet over MPLS
Ethernet over MPLS (EoMPLS) PWs provide a tunneling mechanism for Ethernet traffic through an MPLS-enabled Layer 3 core network. EoMPLS PWs encapsulate Ethernet protocol data units (PDUs) inside MPLS packets and use label switching to forward them across an MPLS network. EoMPLS PWs are an evolutionary technology that allows you to migrate packet networks from legacy networks while providing transport for legacy applications. EoMPLS PWs also simplify provisioning, since the provider edge equipment only requires Layer 2 connectivity to the connected customer edge (CE) equipment. The Cisco MWR 2941 implementation of EoMPLS PWs is compliant with the RFC 4447 and 4448 standards.
For instructions on how to create an EoMPLS PW, see Configuring Transportation of Service Using Ethernet over MPLS.
Limitations
When configuring an EoMPLS pseudowire on the Cisco MWR 2941, you cannot configure an IP address on the same interface as the pseudowire.
Configuring Pseudowire
This section describes how to configure pseudowire on the Cisco MWR 2941. The Cisco MWR 2941 supports pseudowire connections using SAToP, CESoPSN, and ATM over MPLS. The following sections describe how to configure pseudowire connections on the Cisco MWR 2941.
•
Using Pseudowire Classes
•
Using CEM Classes
•
Configuring a Backup Peer
•
Configuring Structure-Agnostic TDM over Packet (SAToP)
•
Configuring Circuit Emulation Service over Packet-Switched Network (CESoPSN)
•
Configuring Transportation of Service Using ATM over MPLS
•
Configuring Transportation of Service Using Ethernet over MPLS
For full descriptions of each command, see the Cisco MWR 2941 Mobile Wireless Edge Router IOS Command Reference, Release 15.0(1)MR. For pseudowire configuration examples, see Configuration Examples for Pseudowire
Using Pseudowire Classes
A pseudowire class allows you to create a single configuration template for multiple pseudowire connections. You can apply pseudowire classes to all pseudowire types. Follow these steps to configure a pseudowire class:
|
Command
|
Purpose
|
Step 1
|
enable
Example:
Router> enable
|
Enables privileged EXEC mode.
• Enter your password if prompted.
|
Step 2
|
configure terminal
Example:
Router# configure terminal
|
Enters global configuration mode.
|
Step 3
|
Router(config)# pseudowire-class
newclass
|
Creates a new pseudowire class.
|
Step 4
|
Router(config-pw-class)#
encapsulation mpls
|
Sets an encapsulation type. For an ATM over MPLS pseudowire, use mpls. For a CESoPSN pseudowire using UDP encapsulation, use udp.
|
Step 5
|
Router(config-pw-class)# mpls
experimental 5
|
Specifies the 3-bit EXP field in the MPLS label used for pseudowire packets.
Note For more information about the mpls experimental command, see the Cisco MWR 2941 Mobile Wireless Edge Router IOS Command Reference, Release 15.0(1)MR.
|
Step 6
|
Router(config-pw-class)#
preferred-path peer 50.0.0.1
|
Specifies a preferred path if there are multiple paths that traffic can cross within the pseudowire class.
Note This command applies only to MPLS pseudowires.
|
Step 7
|
Router(config)# interface atm0/ima0
Router(config-if)# pvc 0/40
l2transport
Router(cfg-if-atm-l2trans-pvc)#
encapsulation aal0
|
Configures the pseudowire interface to use for the new pseudowire class. This example shows an ATM IMA interface.
|
Step 8
|
Router(cfg-if-atm-l2trans-pvc)#
xconnect 1.1.1.1 40 pw-class
myclass
|
Binds an attachment circuit to the ATM IMA interface to create an ATM pseudowire. Use the pw-class parameter to specify the pseudowire class that the ATM pseudowire interface uses.
|
Step 9
|
exit
Example:
Router#
|
Exits configuration mode.
|

Note
You cannot use the encapsulation mpls parameter with the pw-class parameter.
Note
The use of the xconnect command can vary depending on the type of pseudowire you are configuring.
Using CEM Classes
A CEM class allows you to create a single configuration template for multiple CEM pseudowires. Follow these steps to configure a CEM class:
Note
You cannot apply a CEM class to other pseudowire types such as ATM over MPLS.
|
Command
|
Purpose
|
Step 1
|
enable
Example:
Router> enable
|
Enables privileged EXEC mode.
• Enter your password if prompted.
|
Step 2
|
configure terminal
Example:
Router# configure terminal
|
Enters global configuration mode.
|
Step 3
|
Router(config)# class cem
mycemclass
|
Creates a new CEM class
|
Step 4
|
Router(config-cem-class)#
payload-size 512
Router(config-cem-class)#
dejitter-buffer 10
Router(config-cem-class)#
idle-pattern 0x55
|
Enter the configuration commands common to the CEM class. This example specifies a sample rate, payload size, dejitter buffer, and idle pattern.
|
Step 5
|
Router(config-cem-class)# exit
|
Returns to the config prompt.
|
Step 6
|
Router(config)# interface cem 0/0
Router(config-if)# no ip address
Router(config-if)# cem 0
Router(config-if-cem)# cem class
mycemclass
Router(config-if-cem)# xconnect
10.10.10.10 200 encapsulation mpls
|
Configure the CEM interface that you want to use for the new CEM class.
Note The use of the xconnect command can vary depending on the type of pseudowire you are configuring.
|
Step 7
|
Router(config-if-cem)# exit
Router(config-if)#
|
Exits the CEM interface.
|
Step 8
|
exit
Example:
Router#
|
Exits configuration mode.
|
Configuring a Backup Peer
A backup peer provides a redundant pseudowire (PW) connection in the case that the primary PW loses connection; if the primary PW goes down, the Cisco MWR 2941 diverts traffic to the backup PW. Follow these steps to configure a backup peer.
|
Command
|
Purpose
|
Step 1
|
enable
Example:
Router> enable
|
Enables privileged EXEC mode.
• Enter your password if prompted.
|
Step 2
|
configure terminal
Example:
Router# configure terminal
|
Enters global configuration mode.
|
Step 3
|
Router(config)# backup peer
peer-router-ip-address vcid
[pw-class pw-class name]
|
Defines the address and VC of the backup peer.
|
Step 4
|
Router(config)# backup delay
enable-delay {disable-delay |
never}
|
Specifies the delay before the router switches pseudowire traffic to the backup peer VC.
Where:
• enable-delay—Time before the backup PW takes over for the primary PW.
• disable-delay—Time before the restored primary PW takes over for the backup PW.
• never—Disables switching from the backup PW to the primary PW.
|
Step 5
|
exit
Example:
Router#
|
Exits configuration mode.
|
Configuring Structure-Agnostic TDM over Packet (SAToP)
Follow these steps to configure SAToP on the Cisco MWR 2941:
|
Command
|
Purpose
|
Step 1
|
enable
Example:
Router> enable
|
Enables privileged EXEC mode.
• Enter your password if prompted.
|
Step 2
|
configure terminal
Example:
Router# configure terminal
|
Enters global configuration mode.
|
Step 3
|
Router(config)# controller [T1|E1]
0/4
Router(config-controller)#
|
Configures the T1 or E1 interface.
|
Step 4
|
Router(config-if)# cem-group 4
unframed
|
Assigns channels on the T1 or E1 circuit to the CEM channel. This example uses the unframed parameter to assign all the T1 timeslots to the CEM channel.
|
Step 5
|
Router(config)# interface CEM0/4
Router(config-if)# no ip address
Router(config-if)# cem 4
|
Defines a CEM group.
|
Step 6
|
Router(config-if)# xconnect
30.30.30.2 304 encapsulation mpls
|
Binds an attachment circuit to the CEM interface to create a pseudowire. This example creates a pseudowire by binding the CEM circuit 304 to the remote peer 30.30.2.304.
|
Step 7
|
exit
Example:
Router#
|
Exits configuration mode.
|

Note
When creating IP routes for a pseudowire configuration, we recommend that you build a route from the xconnect address (LDP router-id or loopback address) to the next hop IP address, such as ip route 30.30.30.2 255.255.255.255 1.2.3.4.
Configuring Circuit Emulation Service over Packet-Switched Network (CESoPSN)
Follow these steps to configure CESoPSN on the Cisco MWR 2941.
Note
To configure a CESoPSN pseudowire with UDP encapsulation, see Configuring a CESoPSN Pseudowire with UDP Encapsulation.
|
Command
|
Purpose
|
Step 1
|
enable
Example:
Router> enable
|
Enables privileged EXEC mode.
• Enter your password if prompted.
|
Step 2
|
configure terminal
Example:
Router# configure terminal
|
Enters global configuration mode.
|
Step 3
|
Router(config)# controller [e1|t1]
0/0
Router(config-controller)#
|
Enters configuration mode for the E1 or T1 controller.
|
Step 4
|
Router(config-controller)# mode
{atm | cas}
|
Sets the controller in asynchronous transfer mode (ATM) or channel-associated signaling (CAS) mode.
|
Step 5
|
Router(config-controller)#
cem-group 5 timeslots 1-24
|
Assigns channels on the T1 or E1 circuit to the circuit emulation (CEM) channel. This example uses the timeslots parameter to assign specific timeslots to the CEM channel.
|
Step 6
|
Router(config-controller)# exit
Router(config)#
|
Exits controller configuration.
|
Step 7
|
Router(config)# interface CEM0/5
Router(config-if-cem)# cem 5
Router(config-if-cem)# signaling
inband-cas
|
Defines a CEM channel.
|
Step 8
|
Router(config-if-cem)# xconnect
30.30.30.2 305 encapsulation mpls
|
Binds an attachment circuit to the CEM interface to create a pseudowire. This example creates a pseudowire by binding the CEM circuit 5 to the remote peer 30.30.30.2.
Note When creating IP routes for a pseudowire configuration, we recommend that you build a route from the xconnect address (LDP router-id or loopback address) to the next hop IP address, such as ip route 30.30.30.2 255.255.255.255 1.2.3.4.
|
Step 9
|
Router(config-if-cem)# exit
Router(config)#
|
Exits the CEM interface.
|
Step 10
|
exit
Example:
Router#
|
Exits configuration mode.
|
Configuring a CESoPSN Pseudowire with UDP Encapsulation
Follow these steps to configure a CESoPSN pseudowire with UDP encapsulation:
|
Command
|
Purpose
|
Step 1
|
enable
Example:
Router> enable
|
Enables privileged EXEC mode.
• Enter your password if prompted.
|
Step 2
|
configure terminal
Example:
Router# configure terminal
|
Enters global configuration mode.
|
Step 3
|
Router(config)# pseudowire-class
udpClass
|
Creates a new pseudowire class.
|
Step 4
|
Router(config-pw-class)#
encapsulation udp
|
Specifies the UDP transport protocol.
|
Step 5
|
Router(config-pw-class)# ip local
interface Loopback1
|
Configures the IP address of the provider edge (PE) router interface to be used as the source IP address for sending tunneled packets.
|
Step 6
|
Router(config-pw-class)# ip tos
value 100
|
Specifies the type of service (ToS) level for IP traffic in the pseudowire.
|
Step 7
|
Router(config-pw-class)# ip ttl 100
|
Specifies a value for the time-to-live (TTL) byte in the IP headers of Layer 2 tunneled packets.
|
Step 8
|
Router(config-pw-class)# exit
Router(config)#
|
Exits pseudowire-class configuration mode.
|
Step 9
|
Router(config)# controller [e1|t1]
0/0
Router(config-controller)#
|
Enters E1 or T1 controller configuration mode.
|
Step 10
|
Router(config-controller)#
cem-group 5 timeslots 1-24
|
Assigns channels on the T1 or E1 circuit to the circuit emulation (CEM) channel. This example uses the timeslots parameter to assign specific timeslots to the CEM channel.
|
Step 11
|
Router(config-controller)# exit
Router(config)#
|
Exits controller configuration.
|
Step 12
|
Router(config)# interface CEM0/5
Router(config-if-cem)# cem 5
|
Defines a CEM channel.
|
Step 13
|
Router(config-if-cem)# xconnect
30.30.30.2 305 pw-class udpClass
|
Binds an attachment circuit to the CEM interface to create a pseudowire. This example creates a pseudowire by binding the CEM circuit 5 to the remote peer 30.30.30.2.
Note When creating IP routes for a pseudowire configuration, we recommend that you build a route from the xconnect address (LDP router-id or loopback address) to the next hop IP address, such as ip route 30.30.30.2 255.255.255.255 1.2.3.4.
|
Step 14
|
Router(config-if-cem)# udp port
local 50000 remote 55000
|
Specifies a local and remote UDP port for the connection.
Note Valid port values for CESoPSN pseudowires using UDP are from 49152-57343.
|
Step 15
|
Router(config-if-cem)# exit
Router(config)#
|
Exits the CEM interface.
|
Step 16
|
exit
Example:
Router#
|
Exits configuration mode.
|
Configuring Transportation of Service Using ATM over MPLS
ATM over MPLS pseudowires allow you to encapsulate and transport ATM traffic across an MPLS network. This service allows you to deliver ATM services over an existing MPLS network.
The following sections describe how to configure transportation of service using ATM over MPLS:
•
Configuring the Controller
•
Configuring an IMA Interface
•
Configuring the ATM over MPLS Pseudowire Interface
Note
For sample configurations for ATM over MPLS, see Configuration Examples for Pseudowire.
Configuring the Controller
Follow these steps to configure the controller.
|
Command
|
Purpose
|
Step 1
|
enable
Example:
Router> enable
|
Enables privileged EXEC mode.
• Enter your password if prompted.
|
Step 2
|
configure terminal
Example:
Router# configure terminal
|
Enters global configuration mode.
|
Step 3
|
Router(config)# card type e1 0 0
|
Configures IMA on an E1 or T1 interface.
|
Step 4
|
Router(config)# controller E1 0/4
Router(config-controller)#
|
Specifies the controller interface on which you want to enable IMA.
|
Step 5
|
Router(config-controller)# clock
source internal
|
Sets the clock source to internal.
|
Step 6
|
Router(config-controller)#
ima-group 0 scrambling-payload
|
If you want to configure an ATM IMA backhaul, use the ima-group command to assign the interface to an IMA group. For a T1 connection, use the no-scrambling-payload to disable ATM-IMA cell payload scrambling; for an E1 connection, use the scrambling-payload parameter to enable ATM-IMA cell payload scrambling.
The example assigns the interface to IMA group 0 and enables payload scrambling.
|
Step 7
|
exit
Example:
Router#
|
Exits configuration mode.
|

Note
For more information about configuring IMA groups, see the "Configuring ATM IMA" section.
Configuring an IMA Interface
If you want to use ATM IMA backhaul, follow these steps to configure the IMA interface.
|
Command
|
Purpose
|
Step 1
|
enable
Example:
Router> enable
|
Enables privileged EXEC mode.
• Enter your password if prompted.
|
Step 2
|
configure terminal
Example:
Router# configure terminal
|
Enters global configuration mode.
|
Step 3
|
Router(config-controller)#
interface ATMslot/IMAgroup-number
Example:
Router(config-controller)#
interface atm0/ima0
Router(config-if)#
|
Specifies the slot location and port of IMA interface group. The syntax is as follows:
• slot—The slot location of the ATM IMA port adapter.
• group-number—The group number of the IMA group.
The example specifies the slot number as 0 and the group number as 0.
Note To explicitly configure the IMA group ID for the IMA interface, you may use the optional ima group-id command. You cannot configure the same IMA group ID on two different IMA interfaces; therefore, if you configure an IMA group ID with the system-selected default ID already configured on an IMA interface, the system toggles the IMA interface to make the user-configured IMA group ID the effective IMA group ID. At the same, the system toggles the original IMA interface to select a different IMA group ID.
|
Step 4
|
Router(config-if)# no ip address
|
Disables the IP address configuration for the physical layer interface.
|
Step 5
|
Router(config-if)# atm bandwidth
dynamic
|
Specifies the ATM bandwidth as dynamic.
|
Step 6
|
Router(config-if)# no atm
ilmi-keepalive
|
Disables the ILMI keepalive parameters.
|
Step 7
|
exit
Example:
Router#
|
Exits configuration mode.
|
For more information about configuring IMA groups, see the "Configuring ATM IMA" section.
Configuring the ATM over MPLS Pseudowire Interface
You can configure ATM over MPLS is several modes according to the needs of your network. Use the appropriate section according to the needs of your network. You can configure the following ATM over MPLS pseudowire types:
•
Configuring N-to-1 VCC Cell Transport Pseudowire—Maps multiple VCCs to a single pseudowire
•
Configuring N-to-1 VPC Cell Transport—Maps multiple VPCs to a single pseudowire
•
Configuring ATM AAL5 SDU VCC Transport—Maps a single ATM PVC to another ATM PVC
•
Configuring a Port Mode Pseudowire—Maps one physical port to a single pseudowire connection
•
Optional Configurations
Note
Release 15.0(1)MR does not support N-to-1 VCC Cell Transport for mapping multiple PVCs, 1-to-1 VCC Cell Mode, or PVC mapping.
Note
When creating IP routes for a pseudowire configuration, build a route from the xconnect address (LDP router-id or loopback address) to the next hop IP address, such as ip route 30.30.30.2 255.255.255.255 1.2.3.4.
Configuring N-to-1 VCC Cell Transport Pseudowire
An N-to-1 VCC cell transport pseudowire maps one or more ATM virtual channel connections (VCCs) to a single pseudowire. Follow these steps to configure an N-to-1 pseudowire.
You can use the following methods to configure an N-to-1 VCC Cell Transport pseudowire.
Mapping a Single PVC to a Pseudowire
To map a single PVC to an ATM over MPLS pseudowire, apply the xconnect command at the PVC level. This configuration type only uses AAL0 encapsulation. Follow these steps to map a single PVC to an ATM over MPLS pseudowire.
Note
Release 15.0(1)MR does not support mapping multiple VCCs to a pseudowire.
|
Command
|
Purpose
|
Step 1
|
enable
Example:
Router> enable
|
Enables privileged EXEC mode.
• Enter your password if prompted.
|
Step 2
|
configure terminal
Example:
Router# configure terminal
|
Enters global configuration mode.
|
Step 3
|
Router(config-controller)#
interface atm0/ima0
|
Configures the ATM IMA interface.
|
Step 4
|
Router(config-if)# pvc 0/40
l2transport
Router(cfg-if-atm-l2trans-pvc)#
|
Defines a PVC. Use the l2transport keyword to configure the PVC as layer 2 virtual circuit.
|
Step 5
|
Router(cfg-if-atm-l2trans-pvc)#
encapsulation aal0
|
Defines the encapsulation type for the PVC.
|
Step 6
|
Router(config-if)# xconnect 1.1.1.1
40 encapsulation mpls
Router(cfg-if-atm-l2trans-pvc-xconn)#
|
Binds an attachment circuit to the ATM IMA interface to create a pseudowire. This example creates a pseudowire by binding PVC 40 to the remote peer 1.1.1.1.
|
Step 7
|
Router(cfg-if-atm-l2trans-pvp-xconn)#
end
Router#
|
Exits configuration mode.
|
Configuring N-to-1 VPC Cell Transport
An N-to-1 VPC cell transport pseudowire maps one or more ATM virtual path connections (VPCs) to a single pseudowire. While the configuration is similar to one-to-one VPC cell mode, this transport method uses the N-to-1 VPC Pseudowire protocol and format defined in RFCs 4717 and 4446. Follow these steps to configure an N-to-1 VPC pseudowire.
Note
Release 15.0(1)MR does not support mapping multiple VPCs to a pseudowire.
|
Command
|
Purpose
|
Step 1
|
enable
Example:
Router> enable
|
Enables privileged EXEC mode.
• Enter your password if prompted.
|
Step 2
|
configure terminal
Example:
Router# configure terminal
|
Enters global configuration mode.
|
Step 3
|
Router(config)# interface atm0/ima0
Router(config-if)#
|
Configures the ATM IMA interface.
|
Step 4
|
Router(config-if)# atm pvp 10
l2transport
Router(cfg-if-atm-l2trans-pvp)#
|
Maps a PVP to a pseudowire
|
Step 5
|
Router(cfg-if-atm-l2trans-pvp)#
xconnect 30.30.30.2 305 encapsulation
mpls
Router(cfg-if-atm-l2trans-pvp-xconn)#
|
Binds an attachment circuit to the ATM IMA interface to create a pseudowire. This example creates a pseudowire by binding the ATM circuit 305 to the remote peer 30.30.30.2.
|
Step 6
|
Router(cfg-if-atm-l2trans-pvp-xconn)#
end
Router#
|
Exits configuration mode.
|
Configuring ATM AAL5 SDU VCC Transport
An ATM AAL5 SDU VCC transport pseudowire maps a single ATM PVC to another ATM PVC. Follow these steps to configure an ATM AAL5 SDU VCC transport pseudowire.
|
Command
|
Purpose
|
Step 1
|
enable
Example:
Router> enable
|
Enables privileged EXEC mode.
• Enter your password if prompted.
|
Step 2
|
configure terminal
Example:
Router# configure terminal
|
Enters global configuration mode.
|
Step 3
|
Router(config)# interface atm
0/ima0
Router(config-if)#
|
Configures the ATM IMA interface.
|
Step 4
|
Router(config-if)# pvc 0/12
l2transport
Router(cfg-if-atm-l2trans-pvc)#
|
Configures a PVC and specify a VCI/VPI.
|
Step 5
|
Router(cfg-if-atm-l2trans-pvc)#
encapsulation aal5
|
Sets the PVC encapsulation type to AAL5.
Note You must use AAL5 encapsulation for this transport type.
|
Step 6
|
Router(cfg-if-atm-l2trans-pvc)#
xconnect 25.25.25.25 125
encapsulation mpls
|
Binds an attachment circuit to the ATM IMA interface to create a pseudowire. This example creates a pseudowire by binding the ATM circuit 125 to the remote peer 25.25.25.25.
|
Step 7
|
exit
Example:
Router#
|
Exits configuration mode.
|
Configuring a Port Mode Pseudowire
A port mode pseudowire allows you to map an entire ATM interface to a single pseudowire connection. Follow these steps to configure a port mode pseudowire:
|
Command
|
Purpose
|
Step 1
|
enable
Example:
Router> enable
|
Enables privileged EXEC mode.
• Enter your password if prompted.
|
Step 2
|
configure terminal
Example:
Router# configure terminal
|
Enters global configuration mode.
|
Step 3
|
Router(config)# interface atm
0/ima0
|
Configures the ATM interface.
|
Step 4
|
Router(cfg-if)# xconnect
25.25.25.25 2000 encapsulation mpls
|
Binds an attachment circuit to the ATM IMA interface to create a pseudowire. This example creates a pseudowire by binding the ATM circuit 200 to the remote peer 25.25.25.25.
|
Step 5
|
exit
Example:
Router#
|
Exits configuration mode.
|
Optional Configurations
You can apply the following optional configurations to a pseudowire link.
Configuring Cell Packing
Cell packing allows you to improve the efficiency of ATM-to-MPLS conversion by packing multiple ATM cells into a single MPLS packet. Follow these steps to configure cell packing.
|
Command
|
Purpose
|
Step 1
|
enable
Example:
Router> enable
|
Enables privileged EXEC mode.
• Enter your password if prompted.
|
Step 2
|
configure terminal
Example:
Router# configure terminal
|
Enters global configuration mode.
|
Step 3
|
Router(config)# int atm1/0
|
Configures the ATM interface.
|
Step 4
|
Router(config)# int atm1/0
Router(config-if)# atm mcpt-timers
1000 2000 3000
|
Defines the three Maximum Cell Packing Timeout (MCPT) timers under an ATM interface. The three independent MCPT timers specify a wait time before forwarding a packet.
|
Step 5
|
Router(config)# pvc 0/11
l2transport
Router(cfg-if-atm-l2trans-pvc)#
encapsulation aal0
Router(cfg-if-atm-l2trans-pvc)#
cell-packing 20 mcpt-timer 3
|
Specifies the maximum number of cells in PW cell pack and the cell packing timer that the Cisco MWR 2941 uses. This example specifies 20 cells per pack and the third MCPT timer.
|
Step 6
|
end
Example:
Router(cfg-if-atm-l2trans-pvc)# end
Router#
|
Exits configuration mode.
|
Configuring Transportation of Service Using Ethernet over MPLS
Ethernet over MPLS PWs allow you to transport Ethernet traffic over an existing MPLS network. For an overview of Ethernet over MPLS pseudowires, see Transportation of Service Using Ethernet over MPLS.
Configuring VLAN Mode
An Ethernet over MPLS pseudowire in VLAN mode creates a connection based on an existing VLAN ID on the Cisco MWR 2941. Follow these steps to configure an Ethernet over MPLS pseudowire in VLAN mode.
|
Command
|
Purpose
|
Step 1
|
enable
Example:
Router> enable
|
Enables privileged EXEC mode.
• Enter your password if prompted.
|
Step 2
|
configure terminal
Example:
Router# configure terminal
|
Enters global configuration mode.
|
Step 3
|
Router(config)# interface vlan 100
|
Creates the VLAN interface to bind to a pseudowire.
|
Step 4
|
Router(config-if)# xconnect 1.1.1.2
101 encapsulation mpls
|
Binds the Ethernet port interface to an attachment circuit to create a pseudowire. This example uses virtual circuit (VC) 101 to uniquely identify the PW. Ensure that the remote VLAN is configured with the same VC.
Note When creating IP routes for a pseudowire configuration, we recommend that you build a route from the xconnect address (LDP router-id or loopback address) to the next hop IP address, such as ip route 30.30.30.2 255.255.255.255 1.2.3.4.
|
Step 5
|
Router(config-if)# interface
GigabitEthernet 0/1
Router(config-if)# switchport trunk
allowed vlan 100
Router(config-if)# switchport mode
trunk
|
Adds the GigabitEthernet interface to the VLAN.
|
Step 6
|
|
Creates a corresponding configuration on the remote router with the same VCID value. This configuration uses VCID 101.
|
Step 7
|
exit
Example:
Router#
|
Exits configuration mode.
|

Note
The Cisco MWR 2941 supports VLAN rewriting on EoMPLS PWs. If the two networks use different VLAN IDs, the router rewrites PW packets using the appropriate VLAN number for the local network.
Note
For more information about configuring VLANs on the Cisco MWR 2941, see the "Configuring VLANs" section.
Configuration Examples for Pseudowire
The following sections contain full configuration examples for pseudowire connections.
•
Asymmetric PWE3 Configuration
•
PWE3 Redundancy Configuration
•
TDM over MPLS Configuration
•
ATM over MPLS Configuration
•
Ethernet over MPLS Configuration
Asymmetric PWE3 Configuration
The following example shows an Asymmetric PWE3 configuration (Figure 22-2).
Figure 22-2 Asymmetric PWE3 Configuration
MWR_1
service timestamps debug datetime msec localtime
service timestamps log datetime msec localtime
preferred-path peer 50.0.0.2
ip address 50.0.0.1 255.255.255.255
xconnect 50.0.0.2 1 encapsulation mpls
ip address 20.0.0.1 255.0.0.0
xconnect 50.0.0.2 2 encapsulation mpls
ip address 60.0.0.1 255.0.0.0
xconnect 50.0.0.2 3 encapsulation mpls
xconnect 50.0.0.2 4 encapsulation mpls
xconnect 50.0.0.2 5 encapsulation mpls
xconnect 50.0.0.2 6 encapsulation mpls
interface GigabitEthernet0/0
switchport access vlan 20
interface GigabitEthernet0/1
switchport access vlan 60
mcpt-timers 1000 5000 10000
cell-packing 10 mcpt-timer 3
xconnect 50.0.0.2 10 pw-class mpls
xconnect 50.0.0.2 20 pw-class mpls
cell-packing 28 mcpt-timer 3
xconnect 50.0.0.2 30 encapsulation mpls pw-class mpls one-to-one
xconnect 50.0.0.2 40 pw-class mpls
xconnect 50.0.0.2 50 pw-class mpls one-to-one
interface ATM1/0.1 point-to-point
xconnect 50.0.0.2 13 pw-class mpls
interface ATM1/0.2 multipoint
cell-packing 2 mcpt-timer 1
xconnect 50.0.0.2 12 encapsulation mpls
interface ATM1/0.3 point-to-point
xconnect 50.0.0.2 14 encapsulation mpls
interface ATM1/0.4 point-to-point
xconnect 50.0.0.2 15 pw-class mpls one-to-one
interface ATM1/0.6 multipoint
xconnect 50.0.0.2 16 pw-class mpls
cell-packing 8 mcpt-timer 3
xconnect 50.0.0.2 17 pw-class mpls
cell-packing 16 mcpt-timer 2
xconnect 50.0.0.2 18 pw-class mpls
interface ATM1/0.7 multipoint
mcpt-timers 1000 5000 10000
cell-packing 20 mcpt-timer 2
xconnect 50.0.0.2 11 encapsulation mpls
interface ATM1/1.1 point-to-point
interface ATM1/1.2 multipoint
ip route 50.0.0.2 255.255.255.255 20.0.0.2
mpls ldp router-id Loopback50 force
network-clock-select 1 BITS
MWR_2
service timestamps debug datetime msec
service timestamps log datetime msec
enable password mypassword
preferred-path peer 50.0.0.1
ip address 50.0.0.2 255.255.255.255
xconnect 50.0.0.1 1 encapsulation mpls
ip address 20.0.0.2 255.0.0.0
ip address 60.0.0.2 255.0.0.0
interface GigabitEthernet0/0
switchport access vlan 20
interface GigabitEthernet0/1
switchport access vlan 60
xconnect 50.0.0.1 2 encapsulation mpls
xconnect 50.0.0.1 3 encapsulation mpls
xconnect 50.0.0.1 4 encapsulation mpls
xconnect 50.0.0.1 5 encapsulation mpls
xconnect 50.0.0.1 6 encapsulation mpls
ip address 1.1.1.2 255.0.0.0
mcpt-timers 1000 5000 10000
cell-packing 25 mcpt-timer 3
xconnect 50.0.0.1 10 pw-class mpls
xconnect 50.0.0.1 20 pw-class mpls
cell-packing 12 mcpt-timer 2
xconnect 50.0.0.1 30 encapsulation mpls pw-class mpls one-to-one
xconnect 50.0.0.1 40 pw-class mpls
xconnect 50.0.0.1 50 pw-class mpls one-to-one
protocol ip 1.1.1.1 broadcast
interface ATM1/0.1 point-to-point
xconnect 50.0.0.1 13 pw-class mpls
interface ATM1/0.2 multipoint
cell-packing 10 mcpt-timer 2
xconnect 50.0.0.1 12 encapsulation mpls
interface ATM1/0.3 point-to-point
xconnect 50.0.0.1 14 encapsulation mpls
interface ATM1/0.4 point-to-point
xconnect 50.0.0.1 15 pw-class mpls one-to-one
interface ATM1/0.6 multipoint
xconnect 50.0.0.1 16 pw-class mpls
cell-packing 18 mcpt-timer 3
xconnect 50.0.0.1 17 pw-class mpls
cell-packing 24 mcpt-timer 2
xconnect 50.0.0.1 18 pw-class mpls
interface ATM1/0.7 multipoint
mcpt-timers 1000 5000 10000
cell-packing 20 mcpt-timer 2
xconnect 50.0.0.1 11 encapsulation mpls
ip route 50.0.0.1 255.255.255.255 60.0.0.1
mpls ldp router-id Loopback50 force
network-clock-select 1 BITS
PWE3 Redundancy Configuration
The following example shows a PWE3 Redundancy configuration (Figure 22-3).
Figure 22-3 PWE3 Redundancy Configuration
MWR_1
service timestamps debug datetime msec
service timestamps log datetime msec
xconnect 2.2.2.2 1 encapsulation mpls
xconnect 2.2.2.2 3 encapsulation mpls
ip address 1.1.1.1 255.255.255.255
ip address 9.9.9.6 255.255.255.0
xconnect 2.2.2.2 10 encapsulation mpls
interface GigabitEthernet0/1
interface GigabitEthernet0/2
switchport access vlan 10
ip route 2.2.2.2 255.255.255.255 9.9.9.8
exception data-corruption buffer truncate
MWR_2
service timestamps debug datetime msec
service timestamps log datetime msec
xconnect 1.1.1.1 1 encapsulation mpls
xconnect 1.1.1.1 2 encapsulation mpls
xconnect 1.1.1.1 3 encapsulation mpls
xconnect 1.1.1.1 4 encapsulation mpls
ip address 2.2.2.2 255.255.255.255
ip address 9.9.9.8 255.255.255.0
xconnect 1.1.1.1 10 encapsulation mpls
xconnect 1.1.1.1 20 encapsulation mpls
interface GigabitEthernet0/1
interface GigabitEthernet0/2
switchport access vlan 10
interface GigabitEthernet0/3
switchport access vlan 20
ip route 1.1.1.1 255.255.255.255 9.9.9.6
mpls ldp router-id Loopback1 force
exception data-corruption buffer truncate
TDM over MPLS Configuration
Figure 22-4 shows a TDM over MPLS configuration. The configuration uses both SAToP and CESoPSN for E1 and T1.
Figure 22-4 TDM over MPLS Configuration
MWR_A
service timestamps debug datetime msec localtime show-timezone
service timestamps log datetime msec localtime show-timezone
no service password-encryption
cem-group 0 timeslots 1-31
description E1 CESoPSN example
description E1 SATOP example
description E1 SATOP example
cem-group 5 timeslots 1-24
description E1 CESoPSN example
ip address 30.30.30.1 255.255.255.255
interface GigabitEthernet0/1
ip address 50.50.50.1 255.255.255.0
xconnect 30.30.30.2 300 encapsulation mpls
xconnect 30.30.30.2 301 encapsulation mpls
xconnect 30.30.30.2 304 encapsulation mpls
xconnect 30.30.30.2 305 encapsulation mpls
ip route 30.30.30.2 255.255.255.255 50.50.50.2
network-clock-select 1 BITS
MWR_B
service timestamps debug datetime msec localtime show-timezone
service timestamps log datetime msec localtime show-timezone
no service password-encryption
cem-group 0 timeslots 1-31
description E1 CESoPSN example
description E1 SATOP example
description T1 SATOP example
cem-group 5 timeslots 1-24
description T1 CESoPSN example
ip address 30.30.30.2 255.255.255.255
interface GigabitEthernet0/1
ip address 50.50.50.2 255.255.255.0
xconnect 30.30.30.1 300 encapsulation mpls
xconnect 30.30.30.1 301 encapsulation mpls
xconnect 30.30.30.1 304 encapsulation mpls
xconnect 30.30.30.1 305 encapsulation mpls
ip route 30.30.30.1 255.255.255.255 50.50.50.1
network-clock-select 1 E1 1/0
CESoPSN with UDP Configuration
The following configuration uses CESoSPN with UDP encapsulation.
Note
This section provides a partial configuration intended to demonstrate a specific feature.
ip address 2.2.2.8 255.255.255.255
pseudowire-class udpClass
ip local interface Loopback 0
cem-group 0 timeslots 1-31
xconnect 2.2.2.9 200 pw-class udpClass
udp port local 50000 remote 55000
ATM over MPLS Configuration
This example shows how to accomplish the following configurations (Figure 22-5):
Note
Release 15.0(1)MR does not support N-to-1 VCC Cell Transport for mapping multiple PVCs, 1-to-1 VCC Cell Mode, or PVC mapping.
•
AAL5 SDU mode PW on 0/1 PVC 0/100
•
N:1 VCC cell mode PW on 0/1 PVC 0/101
•
Multiple PVCs N:1 VCC cell mode PW on 0/1.1
•
1:1 VCC cell mode PW on 0/1 PVC 0/102
•
Cell-packing for port mode PWs
•
VCC cell-relay mode PWs
•
PVC mapping for 0/1.1 N:1 VCC cell relay PWs
Figure 22-5 ATM over MPLS Configuration
MWR_A
service timestamps debug datetime msec
service timestamps log datetime msec
enable password mypassword
pseudowire-class mpls-exp-5
ip address 88.88.88.88 255.255.255.255
mcpt-timers 1000 2000 3000
cell-packing 28 mcpt-timer 3
xconnect 99.99.99.99 100 encapsulation mpls
interface GigabitEthernet0/0
mcpt-timers 1000 2000 3000
xconnect 99.99.99.99 1100 encapsulation mpls
cell-packing 28 mcpt-timer 3
xconnect 99.99.99.99 1101 encapsulation mpls
cell-packing 28 mcpt-timer 3
xconnect 99.99.99.99 1102 encapsulation mpls
cell-packing 28 mcpt-timer 3
xconnect 99.99.99.99 1103 pw-class mpls-exp-5
interface ATM0/1.1 multipoint
cell-packing 28 mcpt-timer 3
xconnect 99.99.99.99 1200 encapsulation mpls
interface GigabitEthernet0/1
description interface to 7600 fas 3/5
ip address 2.2.2.2 255.255.255.0
ip route 99.99.99.99 255.255.255.255 2.2.2.3
mpls ldp router-id Loopback0
network-clock-select 1 E1 1/0
MWR_B
service timestamps debug datetime msec
service timestamps log datetime msec
enable password mypassword
pseudowire-class mpls-exp-5
ip address 99.99.99.99 255.255.255.255
mcpt-timers 1000 2000 3000
cell-packing 28 mcpt-timer 3
xconnect 88.88.88.88 100 encapsulation mpls
interface GigabitEthernet0/0
mcpt-timers 1000 2000 3000
xconnect 88.88.88.88 1100 encapsulation mpls
cell-packing 28 mcpt-timer 3
xconnect 88.88.88.88 1101 encapsulation mpls
cell-packing 28 mcpt-timer 3
xconnect 88.88.88.88 1102 encapsulation mpls
cell-packing 28 mcpt-timer 3
xconnect 88.88.88.88 1103 pw-class mpls-exp-5
interface ATM0/1.1 multipoint
cell-packing 28 mcpt-timer 3
xconnect 88.88.88.88 1200 encapsulation mpls
interface GigabitEthernet0/1
ip address 2.2.2.3 255.255.255.0
ip route 88.88.88.88 255.255.255.255 2.2.2.2
mpls ldp router-id Loopback0
network-clock-select 1 E1 0/0
Ethernet over MPLS Configuration
The following configuration example shows an Ethernet pseudowire (aka EoMPLS) configuration.
MWR_A
service timestamps debug datetime msec
service timestamps log datetime msec
no service password-encryption
enable password mypassword
network-clock-select 1 E1 0/0
multilink bundle-name authenticated
ip address 4.4.4.4 255.255.255.255
interface GigabitEthernet0/4
switchport trunk allowed vlan 1,2,20,1002-1005
interface GigabitEthernet0/5
switchport trunk allowed vlan 1,2,40,1002-1005
ip address 20.20.20.1 255.255.255.0
xconnect 2.2.2.2 10 encapsulation mpls
ip route 2.2.2.2 255.255.255.255 20.20.20.2
mpls ldp router-id Loopback0
MWR_B
service timestamps debug datetime msec
service timestamps log datetime msec
no service password-encryption
enable password mypassword
network-clock-select 1 E1 0/0
multilink bundle-name authenticated
ip address 2.2.2.2 255.255.255.255
interface GigabitEthernet0/4
switchport trunk allowed vlan 1,2,20,1002-1005
interface GigabitEthernet0/5
switchport trunk allowed vlan 1,2,40,1002-1005
ip address 20.20.20.2 255.255.255.0
xconnect 4.4.4.4 10 encapsulation mpls
ip route 4.4.4.4 255.255.255.255 20.20.20.1
mpls ldp router-id Loopback0