Service Entities
Page 32 7210 SAS-X, R6 OS Services Guide
• With default QinQ SAPs on the ring ports When a VPLS service with default QinQ SAPs
on the ring ports is used for transit traffic in a ring deployment, users can use either G8032
or M-VPLS with xSTP for ring protection. When using G8032, the state of the default
QinQ SAPs in the VPLS service can be managed using a separate G8032 control instance.
NOTE: G8032 control instance cannot use Default QinQ SAPs.cannot be enabled in the
service with Default QinQ SAPs
• MVPLS with xSTP can be used for loop prevention. The Default QinQ SAPs inherit the
state from the associated MVPLS instance.
SAP Configuration Considerations
When configuring a SAP, consider the following:
• A SAP is a local entity and only locally unique to a given device. The same SAP ID value
can be used on another 7210 SAS-Series.
• There are no default SAPs. All SAPs in subscriber services must be created.
• The default administrative state for a SAP at creation time is administratively enabled.
• When a SAP is deleted, all configuration parameters for the SAP will also be deleted.
• A SAP is owned by and associated with the service in which it is created in each router.
• A port with a dot1q encapsulation type means the traffic for the SAP is identified based on
a specific IEEE 802.1Q VLAN ID value. The VLAN ID is stripped off at SAP ingress and
the appropriate VLAN ID placed on at SAP egress. As a result, VLAN IDs only have local
significance, so the VLAN IDs for the SAPs for a service need not be the same at each
SAP.
• If a port is administratively shutdown, all SAPs on that port will be operationally out of
service.
• QinQ access SAPs of type Q1.0 is not supported.
• A SAP cannot be deleted until it has been administratively disabled (shutdown).
• Each SAP can have one each of the following policies assigned:
→ Ingress filter policy
→ Egress filter policy
→ Ingress QoS policy
→ Accounting policy
Note: Access-egress QoS policy is assigned per access port.
To Next Page
Loading...
