Network OS Administration Guide

Supporting Network OS 6.0.1a

Part Number: 53-1003768-04

DAD on the principal node

The following steps describe the procedure for DAD enabled by the dad.py Python script for the logical chassis and fabric cluster mode. The dad.py Python script runs once you enable DAD on the switch.

NOTE
Refer to the "Script for upgrading and reconfiguring switches" section in the Network OS Administration Guide for more information on the dad.py script.

The following prerequisites apply to the DAD process.

  • Set up the FTP server directory structure containing the firmware, Python script or the switch configuration file.
  • Create the DAD configuration file for the cluster, such as the VCS mode, VCS ID, RBridge ID etc. Then upload the file to the FTP server.
  • In the DAD configuration file, for the RBridge ID, you should change the values from the default settings of VCS ID=1 and RBridge ID=1. The globalcfg should be set only for the DAD principal node, and left empty for the secondary nodes.
  • Set up the DHCP server configuration to assign fixed IP addresses to each switch and DAD configuration file for each switch.

The principal node in the logical chassis cluster completes the DAD as a standalone node first.

  1. Power down all the secondary nodes in the cluster.
  2. Enable DHCP. If the switch is currently in the fabric cluster mode, use the copy running-config startup-config command.
  3. Enable DAD using the dhcp auto-deployment enable command.
Once you enable DAD on the switch, the following process begins. For the logical chassis mode, the run order of the script is 3, 1, 2 on the principal node.

1. global - Run logical chassis cluster global configuration commands from the principal node.

2. rbridge-id 2 - Configuration commands for a specific node run from the principal node.

3. rbridge-id 2 - local - Configuration commands allowed to be run from the local node.

Check on the deployment progress until the process is complete. If any of the switches fail the process, you will need to run the process again before the principal node deployment times out.