First time manual boot of nodes in the stack

About this task

The following steps describe how to manually bring up a VC using nodes shipped from the factory that are being booted up for the first time.

Users can boot up a single node or a set of nodes that are to be part of a VC. As well, users can power on one node, all the nodes, or a set of nodes; there is no restriction on the power sequence. The following steps describe the sequence when all nodes are booted up together; however, the steps here do not dictate the order of service provisioning and do not preclude preprovisioning of services on the active CPM. Service preprovisioning is allowed after the VC configuration, including the VC node member configuration, is complete.

Note:

The CPM-IMM nodes are configured through the BOF and do not require further configuration to be part of the VC.

Procedure

Identify the two nodes that will take on the CPM role.
Ensure there is console access to each CPM node to drive the boot process.
See the following for information: 7210 SAS-Sx 10/100GE console port, 7210 SAS-S 1/10GE console port, and Procedure to connect to a console.
Ensure the CPM nodes are powered on.
Ensure that the SD card containing the boot loader (boot.tim) and TiMOS (both.tim) software is installed in the SD card slot for each CPM node.
In Release 11.0, the TiMOS image (both.tim) for the CPM-IMM nodes can be obtained from the local SD card or obtained through the network by specifying the primary/secondary/tertiary image locations appropriately.
On the node that will be the active CPM for the first time boot, log in through the console port and manually interrupt the boot process.
The boot prompt appears.

Configure BOF parameters as follows:

Specify standalone-vc for the boot loader parameter chassis-role.
Specify a name for the boot loader parameter vc-stack-name.
Specify cpm-imm for the boot loader parameter vc-stack-node-type.
Specify the slot number and MAC address of each CPM-IMM node in the bof>vc-stack-node command.
Specify the management IP address for the active and standby CPM-IMM nodes in the bof>eth-mgmt-address command.
Configure the TiMOS image location.
Configure the configuration file location.

See System boot options for 7210 SAS-Mxp, 7210 SAS-S 1/10GE, 7210 SAS-Sx 1/10GE, and 7210 SAS-Sx 10/100GE in standalone mode for information about configuring BOF parameters.

Example

The following output shows an example of a BOF configuration for a CPM-IMM node.

A:Dut-A# show bof
========================================================================
BOF (Memory)
========================================================================
    primary-image      ftp://*:*@135.250.127.36/./images/7xxx-hops/
    primary-config     cf1:\default.cfg
#eth-mgmt Port Settings:
    no  eth-mgmt-disabled
    eth-mgmt-address   10.135.17.166/24 active
    eth-mgmt-address   10.135.17.167/24 standby
    eth-mgmt-route     10.250.0.0/16 next-hop 10.135.17.1
    eth-mgmt-autoneg
    eth-mgmt-duplex    full
    eth-mgmt-speed     100
#System Settings:
    wait               3
    persist            off
    console-speed      115200
    no  console-disabled
    vc-stack-name      VC-3
    vc-stack-node-type cpm-imm
    vc-stack-node cpmA slot-num 1 mac-addr d0:99:d5:91:1c:41
    vc-stack-node cpmB slot-num 2 mac-addr d0:99:d5:90:1e:41
=======================================================================

On the node that will be the standby CPM for the first time boot, log in through the console port and manually interrupt the boot process.
Expected outcome
The boot prompt appears.
Configure BOF parameters as follows:
- Specify standalone-vc for the boot loader parameter chassis-role.
- Specify a name for or the boot loader parameter vc-stack-name.
- Specify cpm-imm for the boot loader parameter vc-stack-node-type.
- Specify the slot number and MAC address of each CPM-IMM node in the bof>vc-stack-node command.
- Configure the TiMOS image location.
The CPM-IMM nodes undergo an arbitration process where the node assigned the lower slot number gets chosen as the active CPM node.

The node chosen as the active CPM node loads the TiMOS image and boots up as the active CPM-IMM node. The standby CPM also proceeds with boot up. However, it does not have the VC configuration on first-time boot and needs to wait for the active CPM to provide the VC configuration through VC management messages.
Identify the node that will take on the IMM role.
Ensure there is console access to the IMM node to drive the boot process.
Ensure that the SD card containing the appropriate boot loader (boot.tim) software is installed in the SD card slot.
Power on the node that will be the IMM node, log in through the console port and manually interrupt the boot process.
Expected outcome
The boot prompt appears.
Configure the boot loader BOF parameter chassis-role as standalone-vc.
The boot loader parameter vc-stack-node-type retains its default value of imm-only.

Note:
The vc-stack-node-type parameter is stored in the boot flash (and not in the boot option file) and must be modified using the BOF menu prompts.

The VC stack name, slot number, image location, configuration location, IP addresses, and route information do not need to be configured on the IMM-only node.
Example
The following output shows an example of a BOF configuration for a IMM-only node.
```
========================================================================
BOF (Memory)
========================================================================
#System Settings:
    wait               3
    persist            off
    console-speed      115200
    no console-disabled
    vc-stack-node-type imm-only
=======================================================================
```
After the IMM-only BOF parameters are configured, save the BOF by typing Yes when prompted to save the BOF. Allow the boot loader proceed with the boot process.

The IMM-only node waits to receive VC configuration information from the active CPM-IMM node.
Take note of the MAC address of the node chosen as the IMM-only node. The MAC address is the chassis MAC address printed on the label of the node.
At the TiMOS prompt on the active CPM node, proceed with the VC configuration by using the config>system>vc-stack>vc-stack-node command to configure the IMM-only node slot number and MAC address.

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.