User guide

Provisioning the iMG/RG (no iMAP or AW+) Overview
AlliedView NMS Administration Guide (Provisioning the iMG/RG)
7-220
7.11 Provisioning the iMG/RG (no iMAP or AW+)
7.11.1 Overview
Note: Section 7.6.9 provides an overview of provisioning the iMG/RG on AlliedWare Plus (AW+) devices, and
how it has the same feature coordiantion as with iMAPs.
When both the iMG/RG and upstream port are controlled by the NMS, certain provisioning features can be coordinated, allow-
ing the administrator to provision, query, and control one or more iMG/RGs quickly and efficiently.
However, this does not mean the iMG/RG can only be configured by the NMS when it is connected to an iMAP or AW+ port.
If the correct steps are taken, the NMS can provision the iMG/RG so that it provides all of its supported services.
When the iMAP and its attributes are not included and are therefore not part of a provisioning/maintaining scenario, the follow-
ing concepts are altered or not applicable.
• Port Profiles are not part of provisioning.
• DNS Entries for iMAPs (remote IDs) are not included. This is what controls the next item.
• Scoping in the iMG profiles is not part of provisioning.
• The Customer ID applies only to the iMG/RG (and optionally to GenBand).
• In the Triple Play Provisioning window, preferences should be set so that iMAP-related fields do not appear or are masked
out.
• Only statistics related to the iMG/RG are displayed in the Triple Play Management window.
• DHCP is still used for provisioning, but the set-up and steps followed are different.
• 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
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-182, 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-182, which shows the steps that are followed