File:  [Coherent Logic Development] / dssp / dssp-002.ms
Revision 1.1.1.1 (vendor branch): download - view: text, annotated - select for diffs
Mon Apr 21 22:18:10 2025 UTC (3 months, 1 week ago) by snw
Branches: MAIN, CoherentLogicDevelopment
CVS tags: start, HEAD
Datashed Systems Standards and Procedures

    1: .TL
    2: DSSP-002: Naming Conventions and Labeling
    3: .br
    4: \fIRevision 1.6 (05/09/19)\fP
    5: .AU
    6: Serena Willis
    7: .AI
    8: Datashed Proprietor
    9: .AB
   10: This document details standards for equipment naming and labeling, to
   11: be followed in new system or network deployments
   12: .AE
   13: .NH
   14: Naming Conventions
   15: .NH 2
   16: Network Equipment
   17: .LP
   18: Network equipment \fBMUST\fP be named according to the following
   19: convention:
   20: .CD
   21: \fIaa\fP-\fIbbbb\fP-\fInn
   22: .DE
   23: .LP
   24: \fIaa\fP represents one of the following equipment classes:
   25: .IP *
   26: \fBsw\fP - switch
   27: .IP *
   28: \fBrt\fP - router
   29: .IP *
   30: \fBap\fP - access point
   31: .IP *
   32: \fBfw\fP - firewall
   33: .LP
   34: \fIbbbb\fP represents one of the following roles:
   35: .IP *
   36: \fBcore\fP - core
   37: .IP *
   38: \fBtor\fP - top-of-rack
   39: .IP *
   40: \fBedge\fP - network edge
   41: .IP *
   42: \fBacc\fP - access
   43: .IP *
   44: \fBagg\fP - aggregation
   45: .IP *
   46: \fBvirt\fP - virtual
   47: .LP
   48: Finally, \fInn\fP represents a sequential number from 00-99. Numbers 
   49: less than 10 \fBMUST\fP be padded with a leading zero.
   50: .NH 3
   51: Naming Exceptions
   52: .LP
   53: Nonconforming names \fBMUST\fP be allowed in the following circumstances:
   54: .IP *
   55: Where the nonconforming name has exceptional personal or historical meaning
   56: .IP *
   57: Where the device being attached cannot, for technical, legal, or contractual
   58: reasons, be assigned a conforming name
   59: .IP *
   60: Where networks connected pursuant to DSSP-008 have a differing set of
   61: naming conventions
   62: .FS
   63: Names that violate DSSP-012 \fBSHALL NOT\fP be allowed on the network,
   64: without regard to the usual naming exceptions in DSSP-002.
   65: .FE
   66: .NH 2
   67: Network Hosts
   68: .LP
   69: Network hosts \fBMUST\fP be named after Greek mythological figures.
   70:  
   71: It is acceptable to provide an alias, e.g. mail, web, nsXX, via local
   72: name resolution mechanisms (DNS, WINS, NIS/NIS+, LDAP, etc.) as-needed,
   73: as long as the primary hostname follows this standard.
   74: .NH 3
   75: Naming Exceptions
   76: .LP
   77: Nonconforming names may be allowed in the following circumstances:
   78: .IP *
   79: Where the nonconforming name has exceptional personal or historical meaning
   80: .IP *
   81: Where the host being attached cannot, for technical, legal, or contractual
   82: reasons, be assigned a conforming name
   83: .IP *
   84: Where networks connected pursuant to DSSP-008 have a differing set of
   85: naming conventions
   86: 
   87: .NH 
   88: Physical Requirements
   89: .NH 2
   90: Labeling
   91: .LP
   92: Labeling of cables \fBMUST\fP follow ANSI/TIA-606-B labeling standards. 
   93: 
   94: The following facilities exist:
   95: .IP *
   96: \fI1DCA\fP is the datashed itself (1st floor, Data Center A)
   97: .IP *
   98: \fI1HTR\fP is the IDF in the house (1st floor, Home, Telecom Room)
   99: .LP
  100: The following special considerations are to be followed for 1DCA:
  101: 
  102: .IP *
  103: Rack numbering begins at C01 (Cabinet 01), the left primary networking rack,
  104: and proceeds counter-clockwise around the building.
  105: 
  106: .NH 3
  107: Remote End Representation
  108: .LP
  109: The label on the near terminus of a given cable \fBMUST\fP denote the location
  110: of the far terminus and vice-versa.
  111: .NH 3
  112: Example Label
  113: .LP
  114: A label with designation \fI1DCA.C02-36:1\fP would be read as follows:
  115: 
  116: .IP *
  117: \fI1DCA\fP represents the floor and building; in this case, "1st floor, data 
  118: center A"
  119: .IP *
  120: C02 represents the location within 1DCA (C02 for Cabinet 2). 
  121: 
  122: TIA-606-B suggests using grid coordinates denoted by raised floor tiles for 
  123: this portion of the label, but allows for custom nomenclature in data centers 
  124: where grid coordinates are not feasible: 1DCA has only five racks, numbered 
  125: \fIC01\fP through \fIC05\fP, and no raised floors.
  126: .IP *
  127: \fI36\fP represents the location at which the equipment is installed within
  128: the rack or enclosure, as numbers of rack units from the floor (i.e., the
  129: lowest position in the rack is \fI01\fP, and the number increases as you
  130: move towards the ceiling). 
  131: 
  132: Note that in cases where a piece of equipment occupies more than a single
  133: rack unit, the number is the uppermost rack position occupied by the 
  134: equipment in question.
  135: .IP *
  136: \fI1\fP represents a 1-based port number on the equipment.
  137: .LP
  138: Thus, \fI1DCA.C02-36:1\fP represents the first port in the top-of-rack
  139: switch in cabinet 2 in the first floor of data center A.
  140: 
  141: .LP
  142: @(#)dssp-002.ms	1.6
  143: 
  144: 
  145: 
  146: 
  147: 
  148: 
  149: 
  150: 
  151: 
  152: 
  153: 
  154: 
  155: 

FreeBSD-CVSweb <freebsd-cvsweb@FreeBSD.org>