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.
RSP3 Module:
-
L2 port will start dropping untagged traffic when untagged/default/ptag EFP is not configured and it may start impacting any control plane protocol which requires untagged traffic to be processed. If that happens, you need to explicitly configure the untagged EFP. For example, LACP.
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.