User guide

Provisioning the iMG/RG Provisioning Strategy
661
AlliedView NMS Administration Guide
• 300 = 12C for TEST, so string is"\x01\x2C"
• 301 = 12D for AI01, so string is"\x01\x2D"
• 400 = 190 for TEST, so string is"\x01\x90"
• 401 = 191 for AI01, so string is "\x01\x91"
• 500 = 1F4 for TEST, so string is"\x01\xF4"
• 501 = 1F5 for AI01, so string is"\x01\xF5"
• 600 = 258 for TEST, so string is "\x02\x58"
• 601 = 259 for AI01, so string is "\x02\x59"
You need a class defined for all the iMG/RG types expected/planned to be used in each Access Island in the network.
Following are some examples. (For a complete list refer to the iMG/RG Software Reference Manual, Preface.)
• RG613TX
• RG613SH
• RG613LH
• RG613BD
• iMG646BD
• iMG606BD
• iMG646BD-ON
• iMG646PX-ON
• RG656BD
• RG624A
• RG634A
• RG624B
• RG634B
The above example shows that when the message comes in over VLAN 200 (usually the bootstrap VLAN for the RG for this
Access Island), there is a pointer to the tftp IP address and a bootstrap filename. If the message comes in over VLAN 300
(RGMgmt), there is no pointer to the tftp IP address with no bootstrap file name.
7.2.5.4 DHCP Relay Configured on the iMAPs (VLAN Configuration)
The DHCP Relay configuration in the iMAP associated with the RG must be data filled so that DHCP instances match the
correct IP address for the DHCP server and are associated with the correct VLAN.
The iMAP should be provisioned with at least two DHCP relay instances where data service VLANs (like RGBootstrap,
RGVoice, Video, Internet VLANs) are in one relay instance (e.g. MAIN) and the management VLAN (e.g. RGMgmt) is in the
second instance (called for example MGMT). Each of these instances should be configured to relay to the specific service
provider’s operational DHCP server(s) supporting option 82. The second DHCP relay instance (MGMT) will be configured
to copy to the AlliedView NMS tftp server as well as to the service providers operational DHCP server(s) supporting option
82.
Note: It is good practice to have one DHCP Relay instance for each service, as well as one for MGMT. Refer to the second example.
Following is the example for MAIN.
DHCP Instance Name Mode Remote ID Servers