Restrictions for Trunk EFP Support
-
The rewrite ingress tag pop 1 symmetric command is the only rewrite command that is supported for trunk EFP configurations. The rewrite ingress tag pop 1 symmetric command must be included in the configuration when the Trunk EFP Support feature is enabled.
-
A bridge-domain number that is part of a trunk EFP configuration cannot be shared by other EFPs under the same port or interface.
-
Only one trunk EFP can be configured under one port or interface.
-
All features configured on a trunk EFP (other than encapsulations and bridge-domain assignments) are applied uniformly to all VLANs and bridge domains. If a feature requires VLAN-specific or bridge-domain-specific configuration values, the feature cannot be applied on the trunk EFP. Those special VLANs or bridge domains must be removed from the EFP trunk to form individual EFPs.
-
Trunk EFP MET supports a maximum of 4078 VLANs and the maximum threshold supported is 20480.
-
Untagged EFP should be added to the BDI when untagged packets are directed towards the interface to avoid packets punting to host queue.
Restrictions for Trunk EFP Support
-
Only 1000 VLANs can be configured for a trunk EFP (with or without port channel).
-
Trunk EVC and encapsulation default EVC cannot co-exist on the same interface.
-
Dynamically changing the Trunk EFP number on an interface is not supported on the RSP3 module.
Restrictions for Trunk EFP with Encapsulation from Bridge Domain
-
When an EFP is created on an interface followed by a TEFP with encapsulation from bridge domain (BD), all the BDs in the switch gets added to the TEFP with encapsulation from BD except the ones present in the EFP configured .
-
You cannot create an EFP or TEFP after configuring TEFP with encapsulation from BD. It is recommneded that TEFP with encapsulation from BD should be the last EFP created on an interface.
-
You cannot make changes to EFP after you have configured TEFP with encapsulation from BD. If you need to edit the EFP, you must first remove the TEFP with encapsulation from BD and then edit the TEFP.
-
You cannot convert a TEFP into a TEFP with encapsulation from BD or vice versa.
-
It is recommended to have a service instance ID of the TEFP with encapsulation from BD greater than the ID of any other EFP configured on that interface.
-
You must maintain some delay when detaching and attaching the scaled TEFP with encapsulation from BD configurations.
-
On an access interface having both EFP and TEFP or TEFP with encapsulation from BD configured, any data traffic with VLAN ID equal to bridge domain of EFP is flooded if the VLAN ID present in the data traffic does not match the encapsulation values present in the EFP and TEFP with encapsulation from BD.