User guide

Provisioning the iMG/RG Provisioning the iMG/RG (no iMAP or AW+)
862
AlliedView NMS Administration Guide
• Since there are no iMAPs in this scenario, the administrator is responsible for all network connections between the iMG/
RG, DHCP server, NMS, and service providers. (The network is shown as only a cloud rather than a cloud that includes
iMAP interfaces and specific service providers.)
These concepts are explained below.
7.11.2 DHCP Provisioning
7.11.2.1 iMGs/RGs at Release 3-x
As explained in 7.2.5, the iMG/RG, DHCP server, and AlliedView NMS use DHCP to provide provisioning information and to
download files until the iMG/RG and its network connections are recognized so that services can be supported. This is still
done, as shown in Figure 7-188, but the following is changed.
• Provisioning is tied to the MAC address of the iMG/RG, and must be known before provisioning.
• At the NMS, the RGbootConfigurator must be filled out with TFTP Discovery Enabled. When selected, after the RG
reboots it sends a DHCP discovery message to the DHCP server (over the RGMgmt VLAN). The iMG/RG then sends a
tftp request to the NMS, containing its MAC and IP address. The NMS uses its tftp listener to discover the iMG/RG with
this MAC and IP Address. With the IP and MAC Address, the AlliedView NMS can proceed with discovery and
provisioning.
Note: With the iMG/RG provisioned with a specific MAC address, the iMG/RG cannot simply be swapped with another one when
performing provisioning or maintenance and having the NMS automatically provision the new iMG/RG. At the NMS, the
administrator must delete all objects or traces so that the iMG is no longer known to the NMS. You would then start
provisioning from the beginning, by knowing the MAC address of the new iMG.
• The dhcpd.conf file must include the NMS IP address.
Refer to Figure 7-188, which shows the steps that are followed