Network OS Administration Guide

Supporting Network OS 6.0.1a

Part Number: 53-1003768-04

Example DHCP and DAD configuration files

The following sample configuration files provide a reference for DHCP and DAD deployment environments.

DHCP server configuration file example

The following is an example of the dhcp.conf file.

#ddns-update-style standard;
ddns-update-style interim;
ddns-ttl 600;
ignore client-updates; # Overwrite client configured FQHNs
ddns-domainname "infralab.com.";
ddns-rev-domainname "in-addr.arpa.";

option ntp-servers 192.168.0.2;
option domain-name-servers 192.168.0.2;
option domain-name "infralab.com";
option domain-search "infralab.com";

default-lease-time 600;
max-lease-time 7200;

authoritative;

log-facility local7;

key "rndc-key" {
	algorithm hmac-md5;
	secret "dtBgNTAoqZmwV5c4SueybjOvhe6OIqgac1uQrzGBv5O4X4nIEBEEGWRf0lCnbFhuIJXGExNBjDdNSqgBMeNI8w==";
};

subnet 192.168.0.0 netmask 255.255.255.0 {
  range 192.168.0.100 192.168.0.200;
  option subnet-mask 255.255.255.0;
  option broadcast-address 192.168.0.255;
  zone 0.168.192.in-addr.arpa. {
        primary 192.168.0.2;
        key "rndc-key";
  }
  zone infralab.com. {
        primary 192.168.0.2;
        key "rndc-key";
  }
}
# cluster switches
group{
  option bootfile-name "/config/unified-cfg.min";
  option tftp-server-name "192.168.0.2";
  option routers 192.168.0.2;
  # device 82
  host host10 {
	option dhcp-client-identifier = "CGS0333H00R";
	hardware ethernet 00:05:33:E5:85:37;
 	fixed-address 192.168.0.82; 		# fixed ip address
 }}
  host host11 {
	option dhcp-client-identifier = "CGS0333H00R";
	hardware ethernet 00:05:33:E5:85:38;
	fixed-address 192.168.0.82; 		# fixed ip address
 }

  # device 90
  host host12 {
	option dhcp-client-identifier = "CPL2549J0EG";
	hardware ethernet 00:27:F8:D2:CE:5F;
	fixed-address 192.168.0.90; 		# fixed ip address
 }
  host host13 {
	option dhcp-client-identifier = "CPL2549J0EG";
	hardware ethernet 00:27:F8:D2:CE:5E;
	fixed-address 192.168.0.90; 		# fixed ip address
 }

}

DAD configuration file example

The following is an example of a DAD configuration file.

version=3
date=10/22/2014
supported_nos=6.0.1
  
  

  #host(device 82)
  host_mac=00:05:33:E5:85:37
  host_mac=00:05:33:E5:85:38
  host_sn=CGS0333H00R
  rbridgeid=82
  defaultconfig=no
  startup=/config/mc/rbridge-82.cfg
  globalcfg=/config/mc/global.cfg
  host_end
  
  #host(mm 145)
  host_mac=00:27:F8:46:E7:D9
  host_mac=00:27:F8:38:6C:2C
  host_sn=CDU2539H00L

  fwdir=/min/bld/bld_dadm
  rbridgeid=145
  defaultconfig=no
  startup=/config/mc/rbridge-145.cfg
  globalcfg=/config/mc/global.cfg
  host_end

  #host(device 90)
  host_mac=00:27:F8:D2:CE:5E
  host_mac=00:27:F8:D2:CE:5F
  host_sn=CPL2549J0EG

  rbridgeid=90
  startup=/config/mc/rbridge-90.cfg
  globalcfg=/config/mc/global.cfg
  defaultconfig=no
  host_end

  #host(device 91)
  host_mac=00:27:F8:DC:1E:6B
  host_mac=00:27:F8:DC:1E:6D
  host_sn=CPL2501K01G

  rbridgeid=91
  startup=/config/mc/rbridge-91.cfg
  globalcfg=/config/mc/global.cfg
  defaultconfig=no
  host_end
Table 3 DAD configuration file definitions
Variable Description
version

version 1 support from NOS4.0.0 to NOS6.0.0

version 2 support from NOS5.0.0 to NOS6.0.0

version 3 support NOS6.0.1+

date The last modification date.
supported_nos The firmware version.
host_mac, host_sn, host_end

The MAC addresses or serial number of the switch. "host_mac" or "host_sn" mark the beginning of the configuration section for a switch. The section ends with "host_end".

NOTE
You must confirm the serial number on the switch with Brocade before adding the MAC address or serial number.
vcsmod VCS mode: cluster VCS mode, LC or FC.
vcsid The cluster VCS ID. The range is 1 to 8192.
rbridgeid

The unique ID for each node. When commented out with # sign, for example, "#rbridgeid=5", DAD is disabled for the node.

If the variable startup is set, the value should match the configuration file set at "startup". If not, the DAD sanity check will fail. The range is from 1 to 239. You should change the default settings of vcsid=1 and rbridgeid=1.

principalrbridgeid Principal node rbridige id of the cluster. The designated node will become the principal node of the cluster. Depending on the topology of the cluster, ideally the principal node should have direct connection to most of secondary nodes.
defaultconfig

Using the defaultconfig setting resets all the user configured settings to the factory defaults.

If set to yes, the script, globalconfig, and number of nodes will be ignored and the DAD process is for single node only, not for the cluster.

startup

The local configuration file. The value can be default or configuration file. If the variable defaultconfig is set to yes, startup should be commented out or set empty. If not the DAD sanity check will fail.

  • For NOS 6.0.0 and prior releases this means the switch running configuration. It must be uploaded from each switch with NOSCLI copy running-config ftp://... command.
  • For NOS 6.0.1 and later releases, this means the local configuration only.

globalcfg The cluster global configuration file. This is only set for the DAD principal node and will be ignored by secondary nodes. This should be either set empty or a valid configuration file path must be specified. This is created using the copy global-running-config ftp://... command.
scriptcfgflag

defaultconfig must be set to no. This is not a mandatory variable. The default is 0, when not specified. The meaning of the value is:

0 - only use startup and globalcfg, script is ignored

1 - only use script, startup and globalcfg are ignored

script The set up script file.
ztp ZTP mode: 1 - enabled (default), 0 - disabled. When enabled, it changes the behavior of DAD.
fwdir Firmware path in FTP server. If set to empty, DAD will skip firmware download.