User guide

Provisioning the iMG/RG Provisioning the iMG/RG (no iMAP or AW+)
864
AlliedView NMS Administration Guide
7.11.2.2 iMGs/RGs at Release 4 and above
As described above, the TFTP Discovery option is used to handle customer provisioning without an iMAP or AlliedWare
Plus upstream device and without forwarding DHCP Relay messages to the NMS (option 82).
The iMGs at release 4 and above do not support TFTP discovery, and so the RGbootConfigurator does not have the TFTP
Discovery option (tab 4; refer to 7.2.5). DHCP Discovery must be used, with the following rules:
• Ensure the DHCP Server File (dhcpd.conf) has the options associated with the specific VLAN in the DHCP message
(refer to 7.2.5.3).
• The upstream devices must be configured to forward DHCP Relay messages to the NMS when it gives out RgMgmt IPs as
in section 7.2.5.3.
• Use the vendor-specific option 82 value to define separate classes for the Boot and Mgmt VLANs.
• Configure the Boot class as in section 7.2.5.3.
• Configure the DHCP Mgmt class as in section 7.2.5.3, that is, option bootfile-name is not required.
• Enter the iMG MAC address in the "Provision New Triple Play Customer" dialog, as shown in Figure 7-191.
7.11.3 GUI Provisioning
With the Display Preferences feature (5.6.2), the administrator sees only the fields that are relevant for the provisioning
scenario, and fields that need to be filled in are highlighted as the user fills out the fields. In the Display Preferences GUI,
there is the iMG/RG Configuration Panel. When selected, the Triple Play form limits the shown fields to only those that are
iMG/RG related. Refer to the following figures.
FIGURE 7-190 Display Preferences set for iMG/RG