![]() |
Asynchronous Transfer Mode Configuration Guide, Cisco IOS XE Release 3S
|
||||||||||||
N:1 PVC Mapping to PWE with Nonunique VPIs
![]() |
|||||||||||||
|
Contents
N:1 PVC Mapping to PWE with Nonunique VPIsLast Updated: August 8, 2012
The N:1 PVC Mapping to PseudoWire Emulation (PWE) with Nonunique virtual path identifiers (VPIs) feature maps one or more ATM permanent virtual circuits (PVCs) to a single pseudowire (PW). There are two modes of AAL0 encapsulation, N:1 and 1:1 mapping. In N:1 mapping, multiple unrelated virtual path identifier/virtual channel identifier (VPI/VCI) are carried over a single Multiprotocol Label Switching (MPLS) PW. This is an efficient mapping method because less resources are used from the MPLS network. In 1:1 mapping, a single VPI/VCI is carried over a single MPLS PW. Benefits of this feature include the following:
Finding Feature InformationYour 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 N:1 PVC Mapping to PWE with Nonunique VPIs
Information About N:1 PVC Mapping to PWE with Nonunique VPIsN:1 PVC Mapping to PWE with Nonunique VPIs Feature DescriptionTo transport ATM cells over Multiprotocol Label Switching (MPLS), a VC is established between the provider edge (PE) routers on both ends of the MPLS backbone. With the N:1 permanent virtual circuit (PVC) Mapping to PseudoWire Emulation (PWE) with Nonunique VPIs feature, multiple PVCs irrespective of their Virtual Path Identifiers (VPIs), are transported over a single pseudowire configured on a subinterface. ("N:1" refers to the number of PVCs transported over one pseudowire). ATM cells are packed together in a single frame and sent over the single pseudowire. The ATM cell header information is packed together with the cell payload on a per-cell basis in the packets so that packets received at the egress end are unpacked and the ATM cells are mapped to the respective PVCs. In N:1 PVC mapping mode, the device can pack cells only from a single PVC in an MPLS packet to transmit over a pseudowire; cells from multiple PVCs cannot be packed in a single MPLS packet and mapped to a single pseudowire for transmission. However, if a device receives an MPLS packet that is packed with cells from multiple PVCs, then those cells will be unpacked and sent to the respective PVCs. How to Configure N:1 PVC Mapping to PWE with Nonunique VPIsConfiguring N:1 PVC Mapping to PWE with Nonunique VPIsSUMMARY STEPS
DETAILED STEPS Configuration Examples for N:1 PVC Mapping to PWE with Nonunique VPIsExample: Configuring N:1 PVC Mapping to PWE with Nonunique VPIsThe following example shows how to configure the N:1 ATM permanent virtual circuit (PVC) mapping to pseudowires with non unique virtual path identifiers ( VPIs): Device> enable Device# configure terminal Device(config)# interface atm 9/1/1 Device(config-if)# atm mcpt-timers 500 5000 50000 Device(config-if)# exit Device# configure terminal Device(config)# interface atm 9/1/1.1 multipoint Device(config-subif)# no ip address Device(config-subif)# atm enable-ilmi-trap Device(config-subif)# cell packing 20 mcpt-timer 2 Device(config-subif)# xconnect 10.1.1.1 100 encapsulation mpls Device(config-subif)# pvc 10/100 l2transport Device(config-subif)# pvc 11/122 l2transport Device(config-subif)# pvc 19/231 l2transport Device(config-subif)# end Additional ReferencesTechnical Assistance
Feature Information for N:1 PVC Mapping to PWE with Nonunique VPIsThe 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.
© 2012 Cisco Systems, Inc. All rights reserved.
|
||||||||||||
|
|