Information on Ethernet Data Plane Loopback
The Ethernet data plane loopback feature provides a means for remotely testing the throughput of an Ethernet port. You can verify the maximum rate of frame transmission with no frame loss. This feature allows for bidirectional or unidirectional throughput measurement, and on-demand/out-of-service (intrusive) operation during service turn-up. This feature supports two types of Ethernet loopback. RSP3 supports the following types of loopback from Cisco IOS XE Everest 16.5.1 release.
-
Facility loopback (external)—Traffic loopback occurs at the Ingress interface. Traffic does not flow into the router for loopback.
-
Terminal loopback (internal)—Traffic loopback occurs at the Egress interface. Traffic loopback occurs after the traffic flows into the router to the other interface.
QoS Support for Ethernet Data Plane Loopback
-
Ingress QoS is bypassed in external loopback on service instances.
-
Internal loopback sequence is as follows:
-
Ingress QoS
-
Egress QoS (egress port) (both, shaper and policer are supported).
-
Ingress QoS on ingress port and egress QoS on egress port (both, shaper and policer are supported) on the RSP3 module.
-
Ingress QoS on egress port and egress QoS on ingress port on the RSP3 module.
-
-
All port-level and EFP-level QoS is applicable for internal Ethernet data plane loopback.
-
For external Ethernet data plane loopback:
-
All port-level and EFP-level QoS is bypassed except for shaper.
-
Port-level shaper cannot be bypassed.
-