Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 33 Next »

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.

Names of 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:

      {part1} [({part2})] [{part3}] [ - (part4)]

Where:

{part1}

 

{part2}

 

{part3}

 

{part4}

 

Physical Server CI Name Examples

The following are examples of CI names that have been standardized using the conventions described above.

Common
Standard

x

y

x

y
xy

Typical Life Cycle for Physical Servers

Unable to render {include} The included page could not be found.

CI Ownership Matrix

Typical Relationships

The following relationships should be used when defining dependencies for physical servers:

Relationship

Dependent Class

Hosts

Database

Contained in

Equipment Rack

Powered by

Circuit

Runs

{operating_system}

Receives data from

Mass Storage Device

Used by

Business Service

 

 

 

 

 

 

  • No labels