Alcatel-Lucent 7750 SR OS Service Manual page 245

SONET/SDH IPCP
SONET/SDH BCP-Null
TDM
SONET/SDH BCP-Dot1q
TDM
SONET/SDH Frame Relay
TDM
SONET/SDH ATM
ATM
endpoint — Adds a SAP endpoint association.
no endpoint — removes the association of a SAP or a spoke-sdp with an explicit endpoint name.
create — Keyword used to create a SAP instance. The create keyword requirement can be enabled/
agg-rate-limit
Syntax agg-rate-limit agg-rate
no agg-rate-limit
Context config>service>apipe>sap>egress
config>service>epipe>sap>egress
config>service>fpipe>sap>egress
Description
This command defines a maximum total rate for all egress queues on a service SAP or multi-service
site. The agg-rate-limit command is mutually exclusive with the egress scheduler policy. When an
egress scheduler policy is defined, the agg-rate-limit command will fail. If the agg-rate-limit
command is specified, at attempt to bind a scheduler-policy to the SAP or multi-service site will fail.
A multi-service site must have a port scope defined that ensures all queues associated with the site are
on the same port or channel. If the scope is not set to a port, the agg-rate-limit command will fail.
Once an agg-rate-limit has been assigned to a multi-service site, the scope cannot be changed to card
level.
A port scheduler policy must be applied on the egress port or channel the SAP or multi-service site
are bound to in order for the defined agg-rate-limit to take effect. The egress port scheduler enforces
the aggregate queue rate as it distributes its bandwidth at the various port priority levels. The port
scheduler stops offering bandwidth to member queues once it has detected that the aggregate rate
limit has been reached.
If a port scheduler is not defined on the egress port, the queues are allowed to operate based on their
own bandwidth parameters.
The no form of the command removes the aggregate rate limit from the SAP or multi-service site.
7750 SR OS Services Guide
-
0
0 — 4094
16 — 991
vpi (NNI) 0 — 4095
vpi (UNI) 0 — 255
vci 1, 2, 5 — 65535
-
disabled in the environment>create context.
Virtual Leased Line Services
The SAP is identified by the channel. No BCP is
deployed and all traffic is IP.
The SAP is identified with a single service on the
channel. Tags are assumed to be part of the customer
packet and not a service delimiter.
The SAP is identified by the 802.1Q tag on the channel.
The SAP is identified by the data link connection
identifier (DLCI).
The SAP is identified by port or by PVPC or PVCC
identifier (vpi, vpi/vci, or vpi range)
Page 245