Alcatel-Lucent 7750 SR OS Service Manual page 172

Configuring a VLL Service with CLI
Configuring Ingress and Egress SAP Parameters
By default, QoS policy ID 1 is applied to ingress and egress service SAPs. Existing filter policies
or other existing QoS policies can be associated with service SAPs on ingress and egress ports.
An existing scheduler policy can be applied to ingress and egress SAPs to be used by the SAP
queues. The schedulers comprising the policy are created at the time the scheduler policy is
applied to the SAP. If any orphaned queues (queues with a non-existent local scheduler defined)
exist on a SAP and the policy application creates the required scheduler, the status on the queue
becomes non-orphaned at this time.
Ingress and Egress SAP parameters can be applied to local and distributed Epipe service SAPs.
This example displays SAP ingress and egress parameters.
ALA-1>config>service# epipe 5500
config>service>epipe# sap 2/1/3:21
config>service>epipe>sap# ingress
config>service>epipe>sap>ingress# qos 555
config>service>epipe>sap>ingress# filter ip 1
config>service>epipe>sap>ingress# exit
config>service>epipe>sap# egress
config>service>epipe>sap>egress# qos 627
config>service>epipe>sap>egress# scheduler-policy alpha
config>service>epipe>sap>egress# exit
config>service>epipe>sap#
The following example displays the Epipe SAP ingress and egress configuration:
ALA-1>config>service#
----------------------------------------------
...
----------------------------------------------
ALA-1>config>service#
Page 172
epipe 5500 customer 5 vpn 5500 create
description "Distributed epipe service to east coast"
sap 2/1/3:21 create
ingress
qos 555
filter ip 1
exit
egress
scheduler-policy "alpha"
qos 627
exit
exit
spoke-sdp 2:123 create
ingress
vc-label 6600
exit
egress
vc-label 5500
exit
exit
no shutdown
exit
7750 SR OS Services Guide