Finding Feature Information
Your software release may not support all the features documented in this module. For the latest feature information and caveats, see 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 for BCP Support on MLPPP section.
Use Cisco Feature Navigator to find information about platform support and Cisco software image support. To access Cisco Feature Navigator, go to http://www.cisco.com/go/cfn. An account on Cisco.com is not required.
Prerequisites for BCP Support on MLPPP
Cisco IOS XE Everest 16.5.1 or a later release that supports the BCP Support on MLPPP feature must be installed previously.
Restrictions for BCP Support on MLPPP
- IPv6 is not supported.
Routing is not supported, hence, BDI is also not supported on BCP over MLPPP.
- Spanning Tree Protocol (STP) and Resilient Ethernet Protocol (REP) are not supported.
- Jumbo frames are not supported.
- Supports 16 T1/E1 and OC3 IM only. A maximum number of 16 (0-15) links per MLPPP bundle are supported, where traffic rate is not beyond MLPPP bandwidth. For E1 link, 16 E1 serial interfaces can be in one MLPPP bundle. For T1, 16 T1 links can be in one MLPPP bundle.
- The following encapsulations are not supported: QinQ , dot1ad , and dot1ad-dot1q .
- You cannot configure default or untagged encapsulations on two different multilinks. When default is configured on a multilink, you can configure another EFP as untagged on the same multilink. For untagged , the same multilink cannot have another EFP configured as untagged .
- Two different multilinks cannot bridge the same encapsulated VLAN.
- The same bridge domain cannot be configured twice on the same interface.
- Connectivity Fault Management (CFM), Y.1731, and Layer 2 protocol forward tagged are not supported.
- Set qos-group is not supported in the output policy of physical Gigabit interface and EVC of the multilink interface. Set qos-group on NCS 4200 will not mark the packet. The scope of the set qos-group is limited to the router.
QoS policy is not supported on multilink at the interface level. However, it is supported on different EVCs of the multilink interfaces.
Qos-group classification will work only on the egress interface or EFP interface.
- The MLPPP interface bundle supports only a maximum of 64 EVCs.
A miximum of 64 VLANs are supported across all the MLPPPs.
- Layer 3 traffic with default encapsulation is not supported.
- Multicast and IGMP is not supported.
For ingress classification to work, it should be classified based on “match cos inner <>” or “match vlan inner <>”.
Layer 2 QoS behavior is supported only on tagged/priority tagged packets. It is not supported for untagged packets.
Only 1r2C policer is supported at the egress.
With BCP on MLPPP, the COS bits in the paylod are not preserved end to end.