This section provides information to configure cards, MDAs, and ports.
Topics in this section include:
The following fields require specific input (there are no defaults) to configure VSM:
The following example shows VSM defaults when a ccag-id is created.
This section provides a brief overview of the tasks that should be performed to configure VSM on an MDA, router, router interface, and services.
Use the CLI syntax shown below to configure the following entities:
Before a CCA module may be utilized in the system, the CCA must be provisioned into an MDA slot. The MDA provisioning command must be modified to support provisioning a CCA adapter type. Up to 8 member CCAs can be configured per CCAG.
The following example shows the command usage to provision CCA on an MDA:
The following output shows the configuration:
Once a CCA is provisioned into the system, it must be placed in a Cross Connect Aggregation Group (CCAG) to be used by cross connect objects. Besides CCA membership, the CCAG also supports bandwidth control parameters (see Configure Path Components) used to manipulate forwarding distribution between objects in the alpha and beta path groups and the aggregate rate allowed on the CCA.
Use the following CLI syntax to provision CCAG components.
The following example shows the command usage to provision CCAG components:
The following example shows the configuration:
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.
Use the following CLI syntax to provision path components.
Use the following CLI syntax to provision CCAG path components.
The following example shows a CCAG path configuration example:
To support cross connection between services and network IP interfaces, the network interface port command has been augmented to allow the binding of the IP interface to a ccag cc-id. Similar to service CCAG SAPs, the network IP interface port binding command must reference the ccag-id, the CCA path (.a or .b) and the cc-id used by the service CCAG SAP on the other CCA path.
Use the following CLI syntax to configure CCAG a network IP interface.
The following shows CCAG network IP interface configuration examples:
Services are provisioned onto a CCAG using a special CCAG SAP definition. CCAG SAPs must reference a ccag-id, a CCA path (a or b), a pairing type (sap-sap or sap-net) and a unique cc-id. The ccag-id identifies the group of CCAs that will be used for forwarding packets associated with the SAP. The path identifies the bandwidth control grouping used to manage CCA egress bandwidth. The pairing type helps the system identify which buffering resources will be used to manage egress queuing of packets. Finally, the cc-id is used to explicitly cross connect the SAP to another SAP or network IP interface configured with the same cc-id.
The following example shows an Epipe SAP configuration referencing a ccag-id:
The following example shows a VPLS SAP configuration referencing a ccag-id:
The following example shows an IES SAP configuration referencing a ccag-id:
The following example shows the configuration:
This section discusses the following service management tasks:
To change or delete a VSM MDA already provisioned for a specific slot, first you must shut down and remove all service SAP and router interface associations to delete the VSM MDA from the configuration.
The following example shows the configuration:
The following example shows the command usage:
The following example shows the command usage to provision CCAG components:
The following example shows the configuration:
The following example shows the command usage to provision CCAG path parameters:
The following example shows the configuration:
The following service examples show the command usage to provision CCAG.
The following output shows the configuration:
The following output shows the configuration:
The following output shows the configuration:
The following output shows the configuration: