We recommended to avoid performing any dynamic changes to the interface state when the Ethernet Data Plane Loopback (ELB) Internal Ethernet Data Plane Loopback session can also be launched when the interface or port is in down state. This scale reduces if RSPAN or SADT is configured.
UNINSTALL LOOPBACK MAC
This scale reduces if SPAN or RSPAN is configured.Ī maximum number of 12 terminal loopback sessions can be created per system, provided 8 sessions are with dot1q and 4 sessionsĪre with dot1q and destination MAC address. Only one Ethernet loopback (terminal or facility) session can be active on an EFP at any instance.Įgress SPAN on the port and internal loopback on an EFP on the same port cannot be configured at the same time.Ī maximum number of 20 facility loopback sessions can be created per system, provided 16 sessions are with dot1q and 4 sessionsĪre with dot1q and destination MAC address.
Loopback sessions cannot be initiated on a port that is configured with SPAN or RSPAN.ĭuring Internal loopback, MAC swap is not supported for multicast or broadcast traffic. Port shaper on the ingress port in both external and internal loopback cannot be bypassed.Įthernet loopback is not supported on a range of dot1q tags.ĭefault EFP loopback is not supported in the shutdown state. 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. 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 Feature Information for Ethernet Dataplane LoopbackĪ means for remotely testing the throughput of an Ethernet port.
UNINSTALL LOOPBACK 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.
UNINSTALL LOOPBACK HOW TO
0 kommentar(er)
