User guide

Provisioning the iMG/RG Provisioning Strategy
665
AlliedView NMS Administration Guide
which identifies a specific Access Island. This, along with the VLAN IDs and Vendor-Class ID, determine which layer 3
subnets should be used for a specific subscriber. This is explained in detail in 7.2.6.2.
For all of the iMG/RGs within a specific voice subnet, there must be a DNS entry with a structured name. When configured
correctly (for the DNS servers and the AlliedView NMS Profiles) the AlliedView NMS correctly coordinates the voice
components so that voice service works correctly. This is explained in detail in 7.2.6.4.
Note: Before beginning the configuration of iMGs/RGs, the naming system should be planned out, and then set up in the DNS or a
local host file.
Note: You must add RGMgmt subnets to discovered and managed subnets before any devices can be discovered on these subnets.
7.2.6.2 DNS Entries for Allied Telesis Components (iMAPs)
The naming of the iMAPs identifies the Service Area (the Access Island) and how it maps to service locations. Each iMAP
component includes an identification ID (remoteID in the DHCP instance) that includes this Service Area, Service Location,
and Access Island number. It then includes the specific iMAP. Table 7-5 explains this naming, with the result as follows:
The Service Area is SPSI
The specific Access Island the component is part of is included as well (AI1 for Access Island 1)
All components use this prefix as part of their ID and are used for DNS naming.
Note: Refer to for character usage rules.
With the domain suffix of “ai.corp.int”:
The fully qualified name for the first iMAP would be:
SPSI-AI00-MAP1x7.ai.corp.int
The following table summarizes the naming convention and can be used as a reference.
TABLE 7-5 Recommended Naming Convention for Remote ID of iMAP for DHCP
Attribute Value
CCCCSS-AInn-LLnTTnn General format for Remote ID (See below)
CCCC 4 character name for the serving area
SS- 2 character name for the state the serving area is located in.A dash at the end helps to
identify the Access Island, which is next in the string. This is optional.
AInn- The Access Island that this device belongs in, so AI0I 1 would be Access Island 1. For
a test Access Island, a 00 or T instead of a number would be used.
Note there is a dash (-) after the Access Island. This allows the user to more easily
discern the digits that identify the Access Island
These make up the10-digit prefix that identifies the Access Island.
Also, this is used to scope Profiles, explained later.
nnnn.... Characters that help identify the device and any attributes for its location, type, etc.
Examples iMAP 1 9700 = SPSI-AI00-MAP1x7
iMAP 2 9400 = SPSI-AI00-MAP2x4
iMAP 5 9810 = SPSI-AI00-MAP5x8
x3112 NCSU = SPSI-AI00-x3112-NCSU