User guide

Naming Conventions to Identify Components (DNS) Provisioning Strategy
7-19
AlliedView NMS Administration Guide (Provisioning the iMG/RG)
The fully qualified name for the first iMAP would be:
DVLKND-AI01-MN1x71.ai.corp.int
2. From a different servicing location, Hut 1, (HT) within the service area DVLKND, the initial four x700 equipment
shelves in the second access island might be called
• DVLKND-AI02-HT1x71
• DVLKND-AI02-HT1x72
• DVLKND-A0I2-HT1x73
• DVLKND-AI02-HT1x74
The fully qualified name for the first iMAP would be:
DVLKND-AI01-HT1x71.ai.corp.int
3. In the case where the number of customers from a specific serving location is expected to be greater than 1000 (such as
the Devils Lake Hut 1 location) an additional three x700 equipment shelves would make up a third Access Island (AI3)
and might be called:
• DVLKND-AI03-HT1x71
• DVLKND-AI03-HT1x72
• DVLKND-AI03-AI3_HT1x73
The fully qualified name for the first iMAP would be:
DVLKND-AI03-HT1X71.ai.corp.int
4. From the same serving location (Devils Lake Hut 1), a 9100 might be servicing a MTU/MDU from this same access
island (AI03) and might be called:
DVLKND-AI03PL1x11 (PL = premise location)
The fully qualified name for the first iMAP would be:
dvlkndai3-pl1x11.ai.corp.int
5. From the same serving location (Devils Lake Hut 1) location a ATI cabinet with a x700 equipment shelf from this the 3rd
access island and might be called
DVLKND-AI03-CB1x71
The fully qualified name for the first iMAP would be:
dvlknd-ai03-cb1x71.ai.corp.int
6. If you were to need to place a second x700 equipment shelf in this cabinet to service more subscribers it would be called:
DVLKND-AI03-CB1x72
The fully qualified name for the first iMAP would be:
dvlknd-ai03-cb1x72.ai.corp.int
These same names will be used as the hostname in the MAPs as well as the DHCP remote id for ALL instances.
The following table summarizes the naming convention and can be used as a reference.