Pseudowire Redundancy Service Models
Page 164 7210 SAS-X, R6 OS Services Guide
fields of contained packets and this association of forwarding class at the ingress will determine
both the queuing and the Dot1P bit setting of packets on the Ethernet VLL on the egress.
SAP ingress classification and Policing - The traffic at the SAP ingress is classified and metered
according to the SLA parameters. All the traffic ingressing on the SAP is classified to a particular
forwarding class. All the forwarding class is metered through and marked in-profile or put-profile
based on the Meter parameters.
When applied to Epipe services, service ingress QoS policies only create the unicast defined in
the policy. The multipoint are not created on the service. Note that both Layer 2 or Layer 3 criteria
can be used in the QoS policies for traffic classification in a service.
Egress Network DOT1P Marking - Marking of IEEE DOT1P bits in VLAN tag is as per the FC-
to-Dot1p map. For details see the default network QoS policy in the QoS user guide. This marking
is applied at the port level on access ports and access uplink ports.
Ingress Network Classification - Ingress network classification is based on the Dot1p bits in the
outer VLAN tag received on the access uplink port. Dot1p-to-FC mapping is based on the network
ingress QoS policy.
Filter Policies
7210 SAS Epipe 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.
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, the 7210 SAS X 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...
