Document Managed by Network Architecture

Introduction

This document defines a formal naming convention intended to manage the RUNet device namespace. Device hostnames are important to effectively manage a large network, and should reflect a device's function, geographical and logical location within the network. RUNet is designed hierarchically, using a core layer, a distribution layer and an access layer. Devices within the network will fall logically into one of these three layers. Functionally, these devices are described as core routers, distribution switches, distribution or access routers, and access switches. The network design is such that any device is a member of a tree, rooted at a core device, and is fed from a device logically higher in the tree. A well-formed hostname will indicate the device's location and role in this hierarchy. This convention encodes the most useful information about a device into its hostname while minimizing the length of the hostname. This recommendation follows the DNS convention of most-specific to least-specific name hierarchy.

RUNet Hierarchy

RUNet design follows a general hierarchy with unique elements at each level, as described below. Not all of this information is useful at all times, and may introduce complexity into the naming convention. Lower elements in the hierarchy are easily encapsulated in higher elements, making unique identification at all levels complex and cumbersome. In the RUNet hierarchy, A-tree, building, room, device type and interface are considered significant.

• Domain
• Subdomain
• Zone
• A Tree
• Building
• Room
• Device type
• Interface 

Mnemonics

Interface

The mnemonic used for interface names in the naming convention will be an abbreviation of the name used by the Cisco IOS. The '/' character is replaced with with a '-' character. An interface "Ethernet0/0/0" would translate to "e0-0-0" in the interface field.

ATM  atm  BRI  bri  BVI  bvi  Ethernet  E  FastEthernet  Fe  GigabitEthernet  Ge  Group-Async  gro  Hssi  Hs  Loopback   Lo POS  pos  Port-channel   pc SRP  srp  Serial  Se  Vlan  Vl

Device

There are several logical types of devices used in RUNet2000. These mnemonics are for their use:
 

Access Router  ar Access Switch  as Aggregation Router gr Aggregation Switch  gs Core Router  cr Core Switch  cs Distribution Router  dr Distribution Switch  ds External router  er Service Router  sr Service Switch  ss Virtual Console  vc Network Service System ns

Collocated devices of the same function are numbered 01, 02, 03, etc. When assigning hostnames, the lowest available number is used. For example, if there are two access switches as01 and as03 in a particular location, then a new access switch should be assigned the name as02. In the event that a device is decommissioned other devices' hostnames should not be affected. For example if there are three access switches as01, as02 and as03, and device as02 is decommissioned, but not replaced, the device names for as01 and as03 should not change.

Building

There is an authoritative list of building mnemonic codes to be used by this convention. The Standard Campus and Building Codes list can be found in its entirety on the Telecommunications Division Website, located at http://www.td.rutgers.edu/documentation/Reference/Network_Device_Name_Building_Codes/index.php.

A-Tree

There are approximately 20 A-trees comprising the RUNet core. The trees and their mnemonics are identified below.

Administrative Services Building   asb Alexander Library  alx  Business and Science Building  bsb  Cook Campus Center  ccc  Douglas Library  dlib  Engelhard Hall  engl  Food Science  fsci  Hill Center for Math and Sciences  hill  Hill Hall  hilh  Kilmer Library  Kilm  Library for Science and Medicine  lsm  Loree lor  New Jersey Hall  njh  Tillett Hall  til  Services Area  svcs Rutgers Regional Network rrn Rutgers Extranet Ext

Name Construction Guidelines

The formal definition for RUNet devices names follows the procedure below.

1. Device names are constructed of mnemonics derived from the interface, device type, building/room and A-tree information for the device.
2. The loopback0 interface is defined to be the identity of a managed device, and the interface description is omitted.
3. Conventionally, the building mnemonic will refer to the Equipment Room (ER) located in that building. For other rooms in a building, the room number is appended to the building mnemonic.
4. Device hostnames should be constrained to the DNS "inside view" as defined by [Network Systems]. Notable exceptions to this rule include external routers (er devices), and network elements whose hostnames must be exposed to the public internet.

Examples

Loopback address of a core router located in the ASB ER, Busch Campus, Piscataway:
           cr01-asb-asb
Distribution Switch, located in ASB ER, Busch Campus, Piscataway: 
           ds01-asb-asb
Interface VLAN 1000 of an access router located in McCormick ER, Busch Campus, Piscataway:
           Vl1000-ar01-mccr-asb
Three access switches, located in room 232 of Thomas Hall. Busch Campus, Piscataway:
           as01-thms232-asb
           as02-thsm232-asb
           as03-thms232-asb

References

1. Standard Campus and Building Codes
2. Network Systems., "Split Horizon Domain Name Service"