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.