/
Configuration Item Life Cycle - Equipment Racks

Configuration Item Life Cycle - Equipment Racks

Equipment racks (including those for servers, PDUs, telecom equipment, etc.) are supporting frameworks containing computer equipment and other hardware modules. Equipment racks typically contain servers, hard disk drive arrays, network gear, and other computing equipment. Racks make it possible to contain a lot of equipment in a small physical footprint without requiring shelving.

CI Naming Convention

Equipment racks require unique identifiers based primarily on the rack's physical location. Rack names are divided into three segments with the segments separated by hyphens. Since rack names are based on the rack's location, a rack name could change in the event the rack is moved from one physical location to another. Rack names follow the form of:

      {data_center}-{zone}-{identifier}

Where:

{data_center}

A code representing the standard abbreviation for the data center or computer room in which the rack is located. All data centers and computer rooms have a unique identifier. See the list below for acceptable data center codes.

{zone}

A code indicating the space identified for the room or area where the rack is located. If the zone has a room number that defines the entire zone then that room number should be used. If the rack is located in a room that is divided into several smaller areas then use a code that indicates in which area in the room the rack is located. A zone may also be a row of racks installed in a physical location, a group of racks being used for a common purpose, etc. See below for a list of valid zone codes when a room number is not an appropriate choice to indicate the zone.

{identifier}

An identifier that is unique to the rack within the data center and zone where the rack is located. The identifier can be any combination of characters, numbers, or symbols but should be kept fairly simple in order to keep the complete rack name easy to manage.

NOTE

When a rack is no longer is use and is not being replaced, the rack name must be modified to include a prefix of RETIRED to make it obvious in listings and searches that the rack is no longer available. If a rack is being replaced by a new one that will be installed in the same location as the original then a new identified must be used to indicate the replacement. Typically, the addition of a single letter or number suffix to the identifier segment of the name is all that is needed.

Data Center Codes Used in Rack Names

Only data center codes from the following list should be used when generating rack names:

OITDC

OIT Data Center at Engineering Gateway

CPDCCentral Plant Data Center

SLDC

Science Library Data Center

SDSCSan Diego Supercomputer Center

Code

Data Center

Zone Codes Used in Rack Names

Only zone codes from the following list should be used when a room number is not appropriate for a rack name:

CodeZone

SSP

Secure Server area in the OIT Data Center at Engineering Gateway

CORE

Core Server area in the OIT Data Center at Engineering Gateway

EG1141Room 1141 at Engineering Gateway
ROWxA row of racks with x being the row designation.

Examples

The following are examples of equipment rack names that use this standard:

  • CPDC-ROWD-08 - Rack 08 located in Row D at the Central Plant Data Center.
  • OITDC-CORE-J31 - Rack J31 located in the Core Zone of the OIT Data Center at Engineering Gateway.
  • OITDC-SSP-H15 - Rack H15 in the SSP Zone of the OIT Data Center at Engineering Gateway.
  • RETIRED - CPDC-ROWA-05 - Rack 05 in Row A at the Central Plant Data Center.

Typical Life Cycle

CAUTION

Additions and changes to the CMDB should be made carefully and at the appropriate time. Be sure to review How to Maintain the CMDB Quality and Data Integrity before making any changes. This article explains when and how CIs are maintained and who should be maintaining them. If you have any questions about maintaining CIs then contact the ServiceNow Support Team for more information.

PhaseCI Activity

Phase 1:Rack Sourced & Acquired

This phase covers the original requirements definition, sizing, sourcing, and acquisition of the equipment rack. This phase ends when the rack is ready to be installed and used for production.

If ServiceNow will be used to track incidents, changes, or task assignments while the rack is being acquired and installed then a CI will be required. Otherwise, a CI is not required until the rack is ready for use.

Phase 2: Rack Deployed

When the client is satisfied that the rack meets all the initial requirements and OIT determines that it is ready to begin installing equipment in the rack, the rack is installed in an appropriate environment. This phase ends when the equipment rack is ready to be used for its intended purpose.

Configuration Item Management Form is submitted by a member of the data center support team and the new CI will be added to the CMDB by the CMDB Administration Team.

Phase 3: Rack in Service & Maintained

This phase represents the useful production life of the hardware. Throughout this phase, the rack will undergo periodic maintenance, failures, and fixes. At some point, the rack will no longer be needed and plans need to be made to deinstall it. This phase ends when the rack is no longer being used and is ready for disposal.

Ongoing adjustments to the StatusState, and other fields in the CI record are made as needed by a member of the team supporting the equipment rack.

Phase 4: Rack Retired

When the equipment rack is no longer needed, either because it is being replaced by something newer or it no longer serves any useful function, it is retired.

The Status and State are updated by a member of the team supporting the rack to reflect the fact that it is no longer operational and has been retired. At the same time, the rack name in the CI is modified to include a prefix of RETIRED to make it obvious in listings and searches that it is no longer in service. Under no circumstances should a CI ever be deleted from the CMDB. Deleting a CI record will make it impossible to trace the history of the software and any activity documented by incidents and change requests.

Suggested Relationships

When mapping dependencies and relationships, the following are typical connections to other CI classes used by equipment racks:

Relationship

Dependent Class

Powered by

Circuit

Located inZone