User guide

Naming Conventions to Identify Components (DNS) Provisioning Strategy
7-17
AlliedView NMS Administration Guide (Provisioning the iMG/RG)
Here is an example of the config required for dhcp relay on aw+ for the rgboot and rgmgmt vlans:
interface vlan201
ip address 10.52.110.177/28
ip dhcp-relay agent-option
ip dhcp-relay information policy replace
op dhcp-relay server-address 10.52.201.36
interface vlan301
ip address 10.52.110.193/28
ip dhcp-relay agent-option
ip dhcp-relay information policy replace
ip dhcp-relay server-address 10.52.201.36
ip dhcp-relay server-address 10.52.201.4 //nms
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.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 ser-
vices 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, 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 com-
ponents 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-4 explains this naming, with the result as follows:
• The Service Area is DVLKND