User guide

Configuring Components for DHCP Discovery Provisioning Strategy
7-11
AlliedView NMS Administration Guide (Provisioning the iMG/RG)
7.2.5 Configuring Components for DHCP Discovery
7.2.5.1 Overview
For the RG to be discovered using DHCP, the user must configure the following tools and files correctly.
Note: For the iMG/RGs to use DHCP correctly, all iMAPs must use DHCP Relay, not DHCP Snooping. Refer to
the Allied Telesis Feature Guide for details on the differences between the two types of DHCP.
Note: For the iMG/RGs to use DHCP correctly, all AlliedWare Plus devices connected directly to iMG/RGs must
use DHCP Relay, not DHCP Snooping, which was added in release 5.3.4. Refer to the Allied Telesis
Software Reference for AlliedWare Plus™ Operating System for details on the differences between the
two types of DHCP.
7.2.5.2 iMG/RG Boot Load Configurator
This tool creates bootstrap loads for the RGs. The Bootstrap load consists of:
• firmware
• snmpinit file - defines the device's SNMP communities
• snmpd.cnf file - includes defining the device's trap host
• im.conf file - includes defining the device's management VLAN identifier
• MD5SUM file - used by RGs as a guide to which files need to be downloaded
• cm.bsvlan7t file - This file is used to set up the Mgmt VLAN (the number entered in the Mgmt VLAN ID field) and dhcp
using the VLAN to configure the iMG/RG.
DHCP needs to direct iMG/RGs to a TFTP server to download their firmware and bootstrap files. Normally this will be used
once-the first time an RG is installed in a network. The AlliedView NMS has a TFTP server installed that can be used for this
process.
The boot load configurator places bootstrap loads into the NMS's TFTP server directory tree, where they are accessible to
TFTP clients (RG/iMGs).
The tool can only be launched from the NMS server. Navigate to the bin directory under the AlliedView NMS installation
directory. Launch the tool with:
• AT_BootConfigurator.bat on Windows (or use the load menu and select Tools -> RG Boot Configurator)
• AT_BootConfigurator.sh on Solaris.
The GUI will appear, as shown below.
Caution: While the tool simplifies the process, it still must be used with caution, since the loads created
have to be consistent with the DHCP configuration, which is not, and generally cannot be,
integrated into the tool (since it is likely to run on a different host with different security
credentials). This tool will create loads with whatever parameters are entered, so the user must
be sure the parameters are valid and meaningful. Mistakes can be corrected by repeating the
process and overwriting invalid loads.