Page 238 7750 SR OS Services Guide
QoS Policies
When applied to 7750 SR Epipe, Apipe, and Fpipe services, service ingress QoS policies only
create the unicast queues defined in the policy. The multipoint queues are not created on the
service.
With Epipe, Apipe, and Fpipe services, egress QoS policies function as with other services where
the class-based queues are created as defined in the policy. Note that both Layer 2 or Layer 3
criteria can be used in the QoS policies for traffic classification in a service. QoS policies on
Apipes cannot perform any classification and on Fpipes Layer 3 (IP) classification is performed.
Filter Policies
7750 SR Epipe, Fpipe, and Ipipe services can have a single filter policy associated on both ingress
and egress. Both MAC and IP filter policies can be used on Epipe services.
Filters cannot be configured on 7750 SR Apipe service SAPs.
MAC Resources
Epipe services are point-to-point layer 2 VPNs capable of carrying any Ethernet payloads.
Although an Epipe is a Layer 2 service, the7750 SR Epipe implementation does not perform any
MAC learning on the service, so Epipe services do not consume any MAC hardware resources.
To Next Page
Loading...
