User guide

Provisioning the iMG/RG Provisioning Strategy
664
AlliedView NMS Administration Guide
ip dhcp-relay server-address 10.52.201.36
!
Note: Customers on each switch must be in non-shared subnets, because the AlliedWare Plus devices do standard DHCP Relay with
option 82 as circuit ID only (no remote ID) and do not perform DHCP Snooping.
7.2.5.6 Summary of Steps for iMG Provisioning
The following table summarizes the steps needed for iMG provisioning for the iMG types and the upstream devices.
7.2.6 Naming Conventions to Identify Components (DNS)
7.2.6.1 Overview
The DNS naming conventions for components are extremely important for administrators because they help in allowing
services to be delivered to subscribers within a specific Access Island.
Note: When dynamic DNS services are required (as in the case of the G6) the voice DHCP server must be separate from the
rgboot/rgmgmt. The DNS servers can be on separate servers or they can coexist on DHCP servers.
For the iMAPs, the remoteID is used as part of the DNS name, and it follows a very specific naming convention, as explained
in 7.2.6.2. The DNS server will scope on the first set of digits (depending on the naming convention used) of the remote-ID,
TABLE 7-4 Summary of iMG Provisioning
Discovery
Method iMG Type Upstream Device Steps
DHCP TR69 (i.e.
iMG 1525)
Allied Telesis
DHCP TR69 (i.e.
iMG 1525)
non-Allied Telesis
DHCP non-TR69 Allied Telesis
DHCP non-TR69 non-Allied Telesis
TFTP non-TR69 non-Allied Telesis