Configuration Item - Physical Servers DRAFT

A physical server is a computer used to provide data to other computers or systems on a local network or over the internet. While any computer can be configured as a server, most production servers use specialized server hardware mounted in racks and installed in a data center. A physical server can be used for a number of applications, including databases, applications, network management, email, directory services, etc. The life cycle outlined here applies to any physical server equipment irrespective of its application.

Physical Server Naming Convention

Host names for physical servers are often specified by the client at the time the server is ordered. However, when this is not the case, server names should follow the form of:

      {assigned_to}-{environment}-{serviceID}nn

Where:

{assigned_to}	Identifier indicating the team, project, application, or other campus department associated with the server.
{environment}	Single-character identifier indicating the environment in which the server will be operating. See the Environment Classification Codes table below for a list of valid codes for this segment.
{serviceID}	Service identifier provided by the client using the server. This is usually something meaningful to the client to help identify the purpose of the server.
{nn}	Sequential two-digit number beginning with "00" to prevent duplication of names.

NOTE

When a physical server is retired, the server name must be modified in the CMDB to include a prefix of RETIRED to make it obvious in listings and searches that the server is no longer being used.
For additional information on server host naming conventions used by OIT, see: OIT Host Name Guideline (EAID 19)

Environment Classification Codes

Only the following environment classification codes may be used in a server name:

Code	Used For
P	Production
N	Non-Production (AWS)
D	Development
Q	Quality Assurance testing
S	Staging
T	Testing

Examples

The following are examples of CI names using this standard:

mail-n-dev0 - The first general-purpose, non-production, development server for the MAIL service.
bus-s-bar0 - The first BUS application staging server for the BAR project.
bus-q-baz1 - The second BUS application QA server (the first ends in "0") for the BAZ project.
RETIRED - find-p-query1 - The second query server (the first ends in "0") for the production FIND application. This server has been retired from active use.

Typical Life Cycle

Phase	CI Activity
Phase 1: Server Requested & Approved During this phase, a need for the server is determined and a decision is made to acquire new equipment. Specifications are determined, quotes are obtained, approvals are collected from appropriate stakeholders, and a supplier is selected. In some cases, the "supplier" may be internal if, for example, an existing device can be repurposed or one is located in another department. This phase ends when all internal documentation is complete and a PO (or transfer documentation) is being prepared.	No CI required. A CI does not need to be added to the CMDB until the server is acquired (or developed) and work is ready to begin.
Phase 2: Order Placed & Server Acquired If the server is being acquired from a third party, an order is placed. If the server is being transferred internally within OIT or from another department, the required documentation is prepared and executed. This phase ends at the point where the server has been delivered and is ready for installation or configuration.	Submit a ServiceNow Configuration Item Update Request and a new CI representing the server will be added by the CMDB Administration Team. The Status field should be set to On Order or Installed, depending on the physical status of the server. Once the CI has been added to the CMDB, the Status and State fields are adjusted by the server owner to indicate the actual current state of the server.
Phase 3: Server Installed & Tested The server must be compared to the original specifications and acquisition documents to confirm that it matches the original requirements. Any required assembly and configuration is done during this phase. This includes operating system software, application software and services, databases, network connections, user definition and security rules, and arrangements made for backups and disaster recovery. When all configuration steps are complete, a final system test is performed on the server in place to ensure it meets all client requirements. This phase ends when the server is ready to be used for its intended purpose.	Once the server is installed, the Status field should be set to Installed. This should be the status throughout the configuration and testing phase.
Phase 4: Server in Service & Maintained This phase represents the useful production life of the server. Throughout this phase, the server will undergo periodic maintenance, upgrades, failures, and fixes. At some point, its usefulness will come to an end and plans need to be made to take it out of service. This phase ends when the server is deactivated and is no longer being used, even for archive purposes, and is ready to be deinstalled.	The Status, State, and other fields are maintained by the asset owner throughout the service life of the server.
Phase 5: Server Retired When the server 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 the server owner to reflect the fact that the server is no longer operational and has been retired. *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 server and any activity documented by incidents and change requests. When there is no longer a need for the server, the server name in the CI is modified to include a prefix of RETIRED** to make it obvious in listings and searches that the server is no longer in use.