.TL
DSSP-002: Naming Conventions and Labeling
.br
\fIRevision 1.6 (05/09/19)\fP
.AU
Serena Willis
.AI
Datashed Proprietor
.AB
This document details standards for equipment naming and labeling, to
be followed in new system or network deployments
.AE
.NH
Naming Conventions
.NH 2
Network Equipment
.LP
Network equipment \fBMUST\fP be named according to the following
convention:
.CD
\fIaa\fP-\fIbbbb\fP-\fInn
.DE
.LP
\fIaa\fP represents one of the following equipment classes:
.IP *
\fBsw\fP - switch
.IP *
\fBrt\fP - router
.IP *
\fBap\fP - access point
.IP *
\fBfw\fP - firewall
.LP
\fIbbbb\fP represents one of the following roles:
.IP *
\fBcore\fP - core
.IP *
\fBtor\fP - top-of-rack
.IP *
\fBedge\fP - network edge
.IP *
\fBacc\fP - access
.IP *
\fBagg\fP - aggregation
.IP *
\fBvirt\fP - virtual
.LP
Finally, \fInn\fP represents a sequential number from 00-99. Numbers
less than 10 \fBMUST\fP be padded with a leading zero.
.NH 3
Naming Exceptions
.LP
Nonconforming names \fBMUST\fP be allowed in the following circumstances:
.IP *
Where the nonconforming name has exceptional personal or historical meaning
.IP *
Where the device being attached cannot, for technical, legal, or contractual
reasons, be assigned a conforming name
.IP *
Where networks connected pursuant to DSSP-008 have a differing set of
naming conventions
.FS
Names that violate DSSP-012 \fBSHALL NOT\fP be allowed on the network,
without regard to the usual naming exceptions in DSSP-002.
.FE
.NH 2
Network Hosts
.LP
Network hosts \fBMUST\fP be named after Greek mythological figures.
It is acceptable to provide an alias, e.g. mail, web, nsXX, via local
name resolution mechanisms (DNS, WINS, NIS/NIS+, LDAP, etc.) as-needed,
as long as the primary hostname follows this standard.
.NH 3
Naming Exceptions
.LP
Nonconforming names may be allowed in the following circumstances:
.IP *
Where the nonconforming name has exceptional personal or historical meaning
.IP *
Where the host being attached cannot, for technical, legal, or contractual
reasons, be assigned a conforming name
.IP *
Where networks connected pursuant to DSSP-008 have a differing set of
naming conventions
.NH
Physical Requirements
.NH 2
Labeling
.LP
Labeling of cables \fBMUST\fP follow ANSI/TIA-606-B labeling standards.
The following facilities exist:
.IP *
\fI1DCA\fP is the datashed itself (1st floor, Data Center A)
.IP *
\fI1HTR\fP is the IDF in the house (1st floor, Home, Telecom Room)
.LP
The following special considerations are to be followed for 1DCA:
.IP *
Rack numbering begins at C01 (Cabinet 01), the left primary networking rack,
and proceeds counter-clockwise around the building.
.NH 3
Remote End Representation
.LP
The label on the near terminus of a given cable \fBMUST\fP denote the location
of the far terminus and vice-versa.
.NH 3
Example Label
.LP
A label with designation \fI1DCA.C02-36:1\fP would be read as follows:
.IP *
\fI1DCA\fP represents the floor and building; in this case, "1st floor, data
center A"
.IP *
C02 represents the location within 1DCA (C02 for Cabinet 2).
TIA-606-B suggests using grid coordinates denoted by raised floor tiles for
this portion of the label, but allows for custom nomenclature in data centers
where grid coordinates are not feasible: 1DCA has only five racks, numbered
\fIC01\fP through \fIC05\fP, and no raised floors.
.IP *
\fI36\fP represents the location at which the equipment is installed within
the rack or enclosure, as numbers of rack units from the floor (i.e., the
lowest position in the rack is \fI01\fP, and the number increases as you
move towards the ceiling).
Note that in cases where a piece of equipment occupies more than a single
rack unit, the number is the uppermost rack position occupied by the
equipment in question.
.IP *
\fI1\fP represents a 1-based port number on the equipment.
.LP
Thus, \fI1DCA.C02-36:1\fP represents the first port in the top-of-rack
switch in cabinet 2 in the first floor of data center A.
.LP
@(#)dssp-002.ms 1.6
FreeBSD-CVSweb <freebsd-cvsweb@FreeBSD.org>