Service Entities
Page 46 7705 SAR OS Services Guide
SAP Configuration Considerations
In addition to being an entry or exit point for service traffic, a SAP has to be configured for a
service and, therefore, has properties. When configuring a SAP, consider the following.
• A SAP is a local entity and is only locally unique to a given device. The same SAP
ID value can be used on another 7705 SAR.
• There are no default SAPs. All subscriber service SAPs 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 are also deleted.
• A SAP is owned by and associated with the service in which it is created.
• An Ethernet port or channel with a dot1q encapsulation type means that 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 is 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.
• A TDM circuit emulation service (for example, CESoPSN) requires a channel
group. The channel group must be created before it can be assigned to a SAP.
• An ATM service (for example, ATM N-to-1 VCC cell transport) requires a channel
group. For this case, the channel group requires the assignment of all 24 timeslots
(T1) or 30 timeslots (E1). The timeslot assignments are made automatically after a
channel group is configured for ATM encapsulation.
• If a port or channel is administratively shut down, all SAPs on that port or channel
will be operationally out of service.
• A SAP cannot be deleted until it has been administratively disabled (shut down).
• Each SAP can have one of the following policies assigned to it:
→ Ingress QoS policy
→ Egress QoS policy
→ Accounting policy
→ Ingress filter policy (for Epipes, Ipipes, VPRN, IES, and IES in-band
management SAPs)
To Next Page
Loading...
