Specifications

10-39
Cisco IGX 8400 Series Provisioning Guide, Release 9.3.3 and Later Releases
OL-1166-04
Chapter 10 Cisco IGX 8400 Series IP Service
IP Service Provisioning
In a Y-redundancy pair configuration, the VSI capability is determined by the minimum of the two cards.
A card without VSI capabilities will mismatch if any of the interfaces has an active partition on
controller. Attempts to enable a partition or add a controller on a logical card that does not support VSI
are blocked.
Adding and Deleting Controllers and Slaves
You add an LSC to a node by using the addctrlr command. When adding a controller, you must specify
a partition ID. The partition ID identifies the logical switch assigned to the controller. The valid
partitions are 1, 2, and 3.
Note You can configure partition resources between Automatic Routing Management PVCs and three VSI
LSC controllers.
To display the list of controllers in the node, use the command dspctrlrs. The functionality is also
available via SNMP using the switchIfTable in the switch MIB.
The management of resources on the VSI slaves requires that each slave in the node has a
communication control PVC to each of the controllers attached to the node. When a controller is added
to the IGX by using the
addctrlr command, the NPM sets up the set of master-slave connections between
the new controller port and each of the active slaves in the switch. The connections are set up using a
well known VPI.VCI. The default value of the VPI for the master-slave connection is 0. The default
value of the VCI is (40 + [slot - 2]), where slot is the logical slot number of the slave.
Note After the controllers are added to the node, the connection infrastructure is always present. The
controllers may or may not decide to use it, depending on their state. Inter-slave channels are present
whether controllers are present or not.
The addition of a controller to a node will fail if enough channels are not available to set up the control
VCs (14 in a 16-slot through 30 in a 32-slot switch) in one or more of the UXM slaves.
When the slaves receive the controller configuration message from the NPM, the slaves send a VSI
message trap to the controller informing of the slaves existence. This prompts an exchange from the
controller that launches the interface discovery process with the slaves.
When the controller is added, the NPM will send a VSI configuration CommBus message to each slave
with this controller information, and it will set up the corresponding control VCs between the controller
port and each slave.
Adding a Slave
When a new slave is activated in the node by upping the first line/trunk on a UXM card which supports
VSI, the NPM will send a VSI configuration CommBus (internal IGX protocol) message with the list of
the controllers attached to the switch.
The NPM will setup master-slave connections from each controller port on the switch to the added slave.
It will also set up interslave connections between the new slave and the other active VSI slaves.
Note Slaves in standby mode are not considered VSI configured and are not accounted for in the interslave
connections.