Restrictions for N:1 PVC Mapping to PWE with Nonunique VPIs
-
N:1 permanent virtual circuits (PVC) mapping configuration is supported only on multipoint subinterfaces; it is not supported on main interfaces or point-to-point subinterfaces.
-
N:1 PVC mapping mode is not supported on Access Circuit Redundancy subinterfaces.
-
Preconfigured PVCs cannot exist on the multipoint subinterface on which you want to configure N:1 PVC mapping.
-
An attachment circuit that has been bound to a pseudowire cannot be removed unless all Layer 2 virtual circuits (VCs) have been removed.
-
Layer 3 PVCs cannot be configured on N:1 subinterfaces.
-
Cell packing values configured under a VC class attached to the PVC, main interface, or subinterface will not be inherited by N:1 PVCs.
-
Operation, Administration, and Maintenance (OAM) functionality is not supported on N:1 Layer 2 PVCs. OAM cells coming from the customer edge (CE) network will be treated as normal data traffic and will traverse through the pseudowire.
-
Only ATM adaptation layer type 0 (AAL0) encapsulation is supported for N:1 PVCs.
-
The service policy configuration can be configured only at the subinterface level for N:1 PVCs.
-
ATM N:1 and PVP modes cannot be configured on different subinterfaces that belong to a physical interface.
-
You cannot change the ATM interface mode from point-to-point to multipoint or from multipoint to point-to-point.
-
If you change a layer 2 ATM interface to a layer 3 ATM interface, traffic will not flow.