The enhancement is applicable only on internal loopback. Shaper configuration, when terminal ELB session is activated or deactivated to rate the limit the ELB session traffic. The Ethernet data plane loopback feature is enhanced to avoid control packets getting dropped. Information on Enhanced Ethernet Data Plane Loopback Router# ethernet loopback stop local interface GigabitEthernet
#Metro e loopback plug how to
This example shows how to stop the sessions on the router.
This is an intrusive loopback and the packets matched with the service will not be able to pass through.Ĭontinue? (yes/): yes Example: Configuring Router# ethernet loopback start local interface gigabitEthernet 0/4/1 service instance 10 external dot1q 10 cos 1ĭestination mac-address 0000.0000.0001 timeout none This example below shows how to start external (facility) loopback on the router. This example shows external (facility) loopback on the Gigabit Ethernet 0/4/1 interface: interface GigabitEthernet0/4/1Įthernet loopback permit external =? For facility loopback Router(config-if-srv)# ethernet loopback permit external Router(config-if-srv)# encapsulation dot1q 120 Router(config-if)# service instance 1 ethernet Router(config)# interface gigabitEthernet 0/4/1 This example shows how to configure external (facility) loopback. If traffic is more than 650Mbps and if the packet size is less than a frame size of 64, then BFD and OSPF flaps are expected. When loopback is configure for a default EFP on the interface, then all the traffic (ingressing) in this interface gets loopedīFD flaps on enabling internal loopback and traffic looped back with line rate as both the traffic passes through the HPCT There is a behavior change when interface is moved from up to down state,Īs internal ELB session will not be stopped or removed.Įthernet data plane Loopback is not supported with the XConnect service when the physical interface port state is down.Įthernet data plane Loopback will be affected on STP enabled interface.ĭynamic addition of rewrite ingress tags with default EFP is not supported.ĭynamic changes at EFP and interface level are not supported when Ethernet Data Plane Loopback is active.ĭot1q tag inclusion in the configuration for default and untagged EFP disables the Ethernet Data Plane Loopback. Is configured on a port that is in the down state. 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.
#Metro e loopback plug 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.
0 kommentar(er)
