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}nnWhere:
{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. |
| Info | ||
|---|---|---|
| ||
|
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 | 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 beginIf ServiceNow will be used to track incidents, changes, or task assignments during the initial steps then a CI will be required. Otherwise, a CI is not required until the equipment is ready to be ordered. |
| 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 A 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 serverManagement Form is submitted by a member of the team supporting the server and the new CI will be added to the CMDB by the CMDB Administration Team. |
Phase 3: Server Installed & Tested | 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 | The Ongoing adjustments to the Status, State, and other fields are maintained by the asset owner throughout the service life of in the CI record are made as needed by a member of the team supporting the server. |
Phase 5: Server Retired | The Status and State are updated by a member of the team supporting the server owner to reflect the fact that the server it is no longer operational and has been retired. At the same time, the server 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 use. 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 software 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. |
Suggested Dependencies
The following are typical relationships used when defining dependencies forSuggested Relationships
When mapping dependencies and relationships, the following are typical connections to other CI classes used by physical servers:
| Relationship | Dependent Class |
|---|---|
| Connects to | Network Gear |
| DR provided by | Server |
| Mirrored to | Mirrors |
| Node of | Cluster |
| Powered by | Circuit |
| Include Page | ||||
|---|---|---|---|---|
|
On this page...
| Table of Contents | ||||||
|---|---|---|---|---|---|---|
|