User guide

Naming Conventions to Identify Components (DNS) Provisioning Strategy
7-21
AlliedView NMS Administration Guide (Provisioning the iMG/RG)
FIGURE 7-6 DHCP Discovery - Bootstrap VLAN
1. The RG powers up and sends a DHCP discover message over the untagged VLAN for its port.
2. The iMAP adds the Remote ID, slot.port, and VID information to the circuit ID and forwards the DHCP discover mes-
sage to the DHCP server over the inband iMAP Management interface. (Neither the RG nor the end user devices need
unicast access to the DHCP server as the iMAP is the proxy relay for them.)
Note: The iMAP is configured with DHCP Relay so that is sends DHCP messages to both Server and Listener
along with the circuit ID attributes.
3. The DHCP server classifies the Discovery and then sends a DHCP offer message with the free IP address allocated for
the RG bootstrap, including a mask, the boot directory, the gateway, the vendor class ID, and the tftp server address of the
AlliedView NMS. (As noted, the DHCP server has been configured to know the tftp address.)
4. The RG requests the MD5SUM file from the tftp server, and compares the checksum of its files versus those in the
MD5SUM (with its list of files and checksum). The RG performs a GET on any files that differ, as well as the im.conf
file that sets up the RGMgmt VLAN using DHCP. (The system light is 4 Hz red while downloading, 2 Hz red while writ-
ing to FLASH, steady green when correctly loaded.)
Note: The recovery code is updated first if needed. (*.rec), then the RG reboots and starts again. Then as
needed the main image code and basic “bootstrap” configs elements for the given access island are
loaded.
5. The RG reboots and makes a DHCP discover message to the DHCP server, but this time over the RGMgmt VLAN.
Note: When an RG is de-provisioned and removed from the server (when customer moves) the RG must be
set back to factory. This can be done using the console “sys conf set factory” command or the tic box on
the Deprovision Ports form.