7210 SAS-MXP, R6, R12, S, SX, T BASIC SYSTEM
CONFIGURATION GUIDE RELEASE 22.9.R1
Virtual chassis
Expected outcome
When the VC configuration information has been committed in the CLI, the active CPM node sends the VC
configuration to all other nodes in the VC through VC management messages over the stacking ports.
When the IMM-only nodes receive the VC management messages from the active CPM, they confirm
the VC configuration by matching their chassis address to the MAC address contained in the VC
message.They then retrieve the TiMOS image from the active CPM and use it to boot up.
While booting up with the TiMOS image, the standby CPM node undergoes another CPM election
arbitration process, which results in the node detecting itself as standby. The node then executes the
HA reconcile process and synchronizes its management and control plane state with the active CPM. It
receives the current running configuration with the VC configuration and the current BOF configuration
present on the active CPM.
The VC is now ready for use.
5.6.2 Subsequent reboot of the stack (with correct BOF present)
This scenario assumes that the BOF configured on each node during the first time boot up is saved locally
and contains the VC configuration required for the node to boot up. It also assumes that the chassis-role
parameter in the bootflash is set to standalone-vc for each node.
The following sequence occurs in the boot loader context and in the TiMOS context. There is no user
intervention required:
• In the boot loader context, all the nodes in the VC read their bootflash and the BOFs that are present
locally, and receive their VC configuration.
• In the boot loader context, the nodes configured as cpm-imm go through a CPM election process and
the node with the lower slot number is chosen as the active CPM. Both nodes proceed to boot up using
the TiMOS image (both.tim).
• In the TiMOS context, both the cpm-imm nodes again read the BOFs that are present locally and
receive their VC configuration.
• In the boot loader context, the imm-only nodes wait to receive VC management messages from the
active CPM, when the active CPM has booted up. When the imm-only nodes receive VC management
messages that contain their MAC address and slot number, they proceed to boot up using the TiMOS
image (both.tim). A local copy of the TiMOS image is used if it matches the version available on the
active CPM; otherwise, the imm-only nodes retrieve the newer version from the active CPM. The imm-
only nodes do not participate in the CPM election process.
• In the TiMOS context, the cpm-imm nodes go through the CPM election arbitration process to elect
the active CPM node. The active CPM node then initializes the chassis manager and initiates a HA
reconcile process with the standby CPM node.
If both the cpm-imm nodes come up as active, which is detected by both nodes receiving each other's VC
management messages claiming themselves to be active, the node with the higher slot number reboots
itself.
5.7 Replacing and upgrading a node in a VC
This section describes how to:
3HE 18197 AAAB TQZZA
© 2022 Nokia.
Use subject to Terms available at: www.nokia.com/terms/.
235
SPACER TEXT
To Next Page
Loading...