Allied Telesis AT-iMG606BD Spezifikationen PDF herunterladen (Seite 647)

100

101

14. Provisioning the iMG/RG Provisioning Strategy

638

AlliedView NMS Administration Guide

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.

14.1.5 Naming Conventions to Identify Components (DNS)

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 14.1.5.1. 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 14.1.5.1.

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 14.1.5.3.

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.

14.1.5.1 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 14-3 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.

TABLE 14-3 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.

1 2 ... 642 643 644 645 646 647 648 649 650 651 652 ... 994 995

Kommentare zu diesen Handbüchern

Keine Kommentare

Allied Telesis AT-iMG606BD Spezifikationen Seite 647

Kommentare zu diesen Handbüchern

Verwandte Produkte und Handbücher für Gateways / Controller Allied Telesis AT-iMG606BD