VSM Configuration Commands
Page 1276 7750 SR OS Services Guide
VSM Path Commands
path
Syntax path {a | b}
Context config>vsm>ccag ccag-id
Description This command changes the current CLI context to the path nodal context. The CCA path nodal
context is where each CCA path bandwidth, buffer and accounting parameters are maintained. The
path context command must be specified with either the a or b keyword specifying the CCA path
context to be entered.
Each CCA is divided into two distinct paths for bandwidth management purposes. One path is
identified as alpha (a) and the other beta (b). The significance of each path for bandwidth distribution
is dependent on the relative path weights each path is given in relationship to the other. A maximum
path rate may also be defined allowing the provisioning of a maximum cap on the aggregate
bandwidth allowed to the SAP or IP interface queues associated with the path. Each path is separated
into three other contexts; SAP-2-SAP (sap-sap), SAP-2-Net (sap-net) and Net-2-SAP (net-sap). Each
path context allows for the definition of the features that are usually associated with physical ports on
other MDAs in the system. These include buffer pool management, ingress network queue
definitions and accounting policy control.
The CCA path nodal contexts always exist and cannot be removed.
Parameters a — The a keyword is mutually exclusive to the b keyword and defines the CLI CCA path context to
be the alpha path. Either the a or b path must be specified. If the a or b keyword is not present,
the path command will fail without changing the current CLI context.
b — The b keyword is mutually exclusive to the a keyword and defines the CLI CCA path context to
be the beta path. Either the a or b path must be specified. If the a or b keyword is not present, the
path command will fail without changing the current CLI context.
rate
Syntax rate kilobits-per-second [aggregate | cca]
no rate
Context config>vsm>ccag ccag-id>path {a | b}
Description This command defines a specific bandwidth rate limitation for the alpha or beta paths on each
member CCA in the CCAG. Use of the rate command is optional. When the rate command is not
executed or the no rate command is executed, bandwidth allocated to the path is not limited to a
specific rate.
Path limiting on a CCA prevents the aggregate bandwidth for the path from exceeding a certain rate.
If the rate is exceeded, the CCA will backpressure all active egress queues sending on that path.
Access to the available bandwidth is dependent on the various parameters associated with each object
egress queue.