The egress port shaper cannot be bypassed. To bypass Ingress/Egress Port level policies as it works as configured.ĭata plane loopback on routed port infrastructure is not supported.Įtype, src-mac, or llc-oui based loopback traffic filtering is not supported.
![loopback mac loopback mac](https://pic.macsc.com/pic/202106/macv-30111638_ac5fdc65e9.jpeg)
QoS for facility loopback does not work due to the platform restriction.įacility loopback behavior on Gibraltar: Ingress and egress QoS policies on the EFP/TEFP gets bypassed. If the facility loopback is active on either Nile 0 or Nile 1, then only the Ingress QoS policy works on this facility. Loopback can be launched even when the physical interface port state is down. Loopback sessions configured must be within the 1 GB reserved bandwidth. Loopback sessions are supported only of EFPs (service instances, Ethernet flowĭot1q tags are not configured for default and untagged EFPs.Įthernet loopback sessions are supported on dot1q or QinQ or
#Loopback mac verification#
Verification of Ethernet Dataplane Loopback Configuration on Bundle Interface.Configure Ethernet Dataplane Loopback Stop Session on Bundle Interface.Configure Ethernet Dataplane Loopback Start Session on Bundle Interface.Restrictions for Ethernet Dataplane Loopback on Bundle Interface.Support for Ethernet Data Plane Loopback on Bundle Interface.Example: Configuring Ethernet Data Plane Loopback Session.Example: Configuring Ethernet Loopback Active.Configuring Ethernet Data Plane Loopback Session.Information on Enhanced Ethernet Data Plane Loopback.Example: Verifying Ethernet Dataplane Loopback on Physical Interfaces.Example: Configuring Terminal Loopback on Physical Interfaces.Example: Configuring External Loopback on Physical Interfaces.Starting an Ethernet Data Plane Loopback Session on Physical Interfaces.Enabling Ethernet Data Plane Loopback on Physical Interfaces.
#Loopback mac how to#
![loopback mac loopback mac](https://f.fameile.net/upload/2021/06/zdjFSB.jpg)