What Happens When You Delete A Controller; What Happens When A Slave Is Added - Cisco BPX 8620 Installation And Configuration Manual

Chapter 23 Configuring BXM Virtual Switch Interface
Once the controllers have been added to the node, the connection infrastructure is always present.
Note
Depending on their state, the controllers may decide to use it or not.
The addition of a controller to a node will fail if there are not enough channels available to set up the
control VCs in one or more of the BXM slaves.
The BCC also informs the slaves of the new controller through a VSI configuration CommBus message
(the BPXs internal messaging protocol). The message includes a list of controllers attached to the switch
and their corresponding controller IDs. This internal firmware command includes the interface where
the controller is attached. This information, when advertised by the slaves, can be used by the controllers
to set up an inter-master communication channel.
When the first controller is added, the BCC behaves as it did in releases previous to Release 9.2. The
BCC will send a VSI configuration CommBus message to each of the slaves with this controller
information, and it will set up the corresponding control VCs between the controller port and each of the
slaves.
When a new controller is added to drive the same partition, the BCC will send a VSI configuration
CommBus message with the list of all controllers in the switch, and it will set up the corresponding set
of control VCs from the new controller port to each of the slaves.

What Happens When You Delete a Controller

To delete a controller from the switch, use either delshelf or delctrlr.
Use the command delshelf to delete generic VSI controllers.
Use the command delctrlr to delete controllers that have been added to Annex G-capable interfaces.
When one of the controllers is deleted by using the delshelf command, the master-slave connections
associated with this controller are deleted. The control VCs associated with other controllers managing
the same partition will not be affected.
The deletion of the controller triggers a new VSI configuration (internal) CommBus message. This
message includes the list of the controllers attached to the node. The deleted controller is removed from
the list. This message is sent to all active slaves in the shelf. In cluster configurations, the deletion of a
controller is communicated to the remote slaves by the slave directly attached through the interslave
protocol.
While there is at least one controller attached to the node controlling a given partition, the resources in
use on this partition should not be affected by a controller having been deleted. Only when a given
partition is disabled will the slaves release all the VSI resources used on that partition.
The addshelf command allows multiple controllers on the same partition. You are prompted to confirm
the addition of a new VSI shelf with a warning message indicating that the partition is already used by
a different controller.

What Happens When a Slave Is Added

When a new slave is activated in the node, the BCC will send a VSI configuration CommBus (internal
BPX protocol) message with the list of the controllers attached to the switch.
The BCC will also set up a master-slave connection from each controller port in the switch to the added
slave.
Release 9.3.30, Part Number 78-12907-01 Rev. E0, May 2005
VSI Master and Slave Redundancy
Cisco BPX 8600 Series Installation and Configuration
23-23