STAGING This is not the live site
CMDB Cis | centrexIT Knowledge Center
Loading...
centrexIT
Knowledge Center

CentrexIT CMDB Cis

KB00039462
Mike Hicks Standard 1 min
Publishedv2

A guide for the required data fields and slot definitions for each CI type in the Halo CMDB

A configuration management database (CMDB) is a repository of information about the configuration items (CIs) that are part of an client organization’s IT infrastructure. A CI can be any hardware, software, or service that is used to deliver IT services.

This document defines the standards for the required data fields that should be populated for each CI type in the CMDB. The data fields are categorized into three types: mandatory, recommended, and optional. Mandatory fields are essential for the identification and management of the CI and are considered required to fully manage the CI. Recommended fields are useful for providing additional information and context about the CI and are highly encouraged but may not be needed or relevant to support the CI in all instances. Recommended and Optional fields are not required, however can be added if relevant for the CI.

CI Types not listed in the document do not have a defined standard at this time. Use of those CI types is at the best judgement of the engineer or vITM.

Italicized Items below are automatically imported from the N-able n-central RMM platform and should be adjusted in N-central, not Halo.

The virtual IT Manager (vITM) for each client is accountable to audit, and ensure, as best is possible, the accuracy of the data for their clients CMDB CIs. However, all centrexIT employees and contractors making changes to any CI, or client network environment, are required to update and maintain the accuracy of the CMDB and individual CIs. If inaccuracies are encountered it is the responsibility of all to ensure that the data is corrected.

Mandatory fields:

  • Name: The unique name of the service.

  • Service Type: The end service type that this service provides.

  • Relationships: At minimum, the underlying systems or software must be linked to the service they provide.

Optional Fields:

  • Description: Additional information and short summary of the service.

  • Scope: Who and how do they use this service.

  • Functions & Features: Details as to the functions and features of the service.

  • Initiation: Details as to the initiation of the service

  • Delivery Channels: Details of the service delivery channels, these are the ways that customers interact with the service or system, such as phone, email, chat, self-service, social media, or face-to-face, etc.

Mandatory fields:

  • Name: The unique name of the computer.

  • Serial Number: The serial number of the computer. (needs to be greyed out and pull from n-central)

  • Model: The model of the computer. (needs to be greyed out and pull from n-central)

  • OS (Operating System): The operating system installed on the computer.

  • Last logged in user: The last user to log into the computer.

  • State: The lifecycle State of the computer (New, Available, Pre-Production, Production, Maintenance, Decommission, Archived). Initially set by n-able to new but should be updated.

Recommended fields:

  • Asset Tag: The asset tag of the computer. This is a schema and can be added in the upper right corner using the “+” which is the Add Schema button.

  • Location: The n-central sub space or network.

  • Assigned To: The specific user the computer is assigned to.

  • Primary support type dropdown: Who supports the system (Person, Company, or group), which will then open a sub slot allowing for further details.

  • Relationships: These are relationships to other CIs, locations, work (incident, alerts, requests, Problem, etc.), Physical Rack or Room, KB articles, RFCs, Services, etc.

  • For devices not currently assigned it is recommended to create a relationship to a location and room, or physical rack, where the device can be found.

Optional fields:

  • Notes: Any additional notes or comments about the computer.

Mandatory fields:

  • Name: The unique name of the server.

  • Hostname: The hostname of the server.

  • Serial Number: The serial number of the server.

  • Model: The model of the server.

  • OS (Operating System): The operating system installed on the server.

  • IP Address: The IP address assigned to the server.

  • MAC Address: The MAC address of the network interface card (NIC) of the server.

  • Location: The physical location of the server.

  • Memory: The amount and type of memory installed on the server.

  • Disk: The size and type of hard disk installed on the server.

  • CPU: The type and speed of the CPU of the server.

  • State: The lifecycle State of the Server (New, Available, Pre-Production, Production, Maintenance, Decommission, Archived, Unknown). Initially set by n-able to new but should be updated.

Recommended fields:

  • Primary support type dropdown: Who supports the system (Person, Company, or group), which will then open a sub slot allowing for further details.

  • Asset Tag: The asset tag of the computer. This is a schema and can be added in the upper right corner using the “+” which is the Add Schema button.

  • Is virtual: Is the system a virtual machine. (Toggle on or off)

  • Validated: Is this a validated system. (Toggle on or off)

  • Relationships: These are relationships to other CIs, locations, work (incident, alerts, requests, Problem, NRFC, SRFC, etc.), Physical Rack or Room, KB articles, Services, Other CIs, etc.

Optional fields:

  • Notes: Any additional notes or comments about the computer.

Mandatory fields:

  • Name: The unique name of the storage device.

  • Hostname: The unique network name of the storage device.

  • Serial Number: The serial number of the storage device.

  • Model: The model of the storage device.

  • OS (Operating System): The operating system installed on the computer.

  • IP Address: The IP address assigned to the server.

  • Location: The physical location of the storage device.

  • Disk: ??

  • State or Lifecycle State: The State of the computer (New, Available, Pre-production, Production, Maintenance, Unknown, Decommission, or Archived). Initially set by n-able but can be set to a maintenance state manually.

Recommended fields:

  • Asset Tag: The asset tag of the storage device.

  • Managed By: The person or group who owns the storage device.

  • Interface: The interface of the storage device (e.g. iSCSI, ethernet, SATA, USB, etc.).

Optional fields:

  • Description: A brief description of the storage device.

  • Notes: Any additional notes or comments about the storage device.

  • Validated: Is this a validated system. (Toggle on or off)

Mandatory fields:

  • Name: The unique name of the printer. (needs to be locked)

  • Serial Number: The serial number of the printer.

  • Model: The model of the printer.

  • State: The current State of the printer (New, Available, Pre-production, Production, Maintenance, Unknown, Decommission, or Archived).

  • Primary Support Type: Defines the person or group who supports the printer.

  • Location: The physical location of the printer.

  • MAC Address: The MAC address of the network interface card (NIC) of the printer.

Recommended fields:

  • Asset Tag: The asset tag of the printer.

  • IP Address: The IP address assigned to the printer.

Optional fields:

  • Notes: Any additional notes or comments about the printer.

Mandatory fields:

  • Name: The unique name of the network device.

  • Serial Number: The serial number of the network device.

  • Model: The model of the network device.

  • Type: The type of the network device (e.g. switch, router, etc.).

  • IP Address: The IP address assigned to the network device.

  • OS: The

  • State: The current State of the network device (New, Available, Pre-production, Production, Maintenance, Unknown, Decommission, or Archived).

  • Location: The physical location of the network device.

Recommended fields:

  • Managed by: The person or group who manages the network device.

  • Asset Tag: The asset tag of the network device.

  • Notes: Any additional notes or comments about the network device.

  • Validated: Is this a validated system. (Toggle on or off)

Mandatory fields:

  • Name: The unique name of the firewall.

  • Serial Number: The serial number of the firewall.

  • Model: The model of the firewall.

  • IP Address: The IP address assigned to the firewall.

  • State: The current State of the firewall (New, Available, Pre-production, Production, Maintenance, Unknown, Decommission, or Archived).

  • Primary support type: The person or group who manages or supports the firewall.

  • Location: The physical location of the firewall.

Recommended fields:

  • Asset Tag: The asset tag of the firewall.

  • Notes: Any additional notes or comments about the firewall.

  • Validated: Is this a validated system. (Toggle on or off)

Mandatory fields:

  • Name: The unique name of the VLAN.

  • Subnet: The subnet mask of the VLAN.

  • Gateway: The gateway address of the VLAN.

  • State: The current State of the VLAN (New, Available, Pre-production, Production, Maintenance, Unknown, Decommission, or Archived.).

  • Purpose / Use Case: What is the primary purpose of this VLAN

  • Managed by: The person or group who manages or owns the VLAN.

  • Description: A brief description of the VLAN.

  • Located In (Location) Relationship: What sites use this VLAN? Build relationships with each site that uses this VLAN.

Mandatory fields:

  • Name: The unique name of the circuit.

  • Circuit ID: The numerical identifier of the circuit.

  • Type: The type of the circuit (e.g. T1, T3, DSL, etc.).

  • Carrier Circuit Type: Single Carrier/Last mile carrier

  • Circuit Handoff Type: IE Fiber, ethernet, coax, etc

  • Connection Type: The type of the circuit.

  • Upload Speed: The upload speed of the circuit.

  • Download Speed: The download speed of the circuit.

  • Vendor: The provider of the circuit.

  • State: The current State of the circuit (New, Available, Pre-production, Production, Maintenance, Unknown, Decommission, or Archived).

  • Primary support type: The person or group who manages the circuit.

  • Location: The physical location of the circuit.

Optional fields:

  • Description: A brief description of the circuit.

Mandatory fields:

  • Name: The unique name of the software.

  • Version: The version number of the software.

  • Manufacturer: The manufacturer of the software.

  • Application Type: The type of the software.

  • State: The current State of the software (New, Available, Pre-production, Production, Maintenance, Unknown, Decommission, or Archived).

  • Primary support type: The person or group who owns or primarily manages the software.

  • Primary Business Owner: (Need to change the “Assigned To slot to be “Primary Business Owner”: The person who is the primary business contact for the software. IE the system owner or admin within the client.

  • Login Location: The physical or logical location of the software.

  • Directory Services Integrated? (on off check/make toggle?)

Optional Fields:

  • Database Backup Enabled: Is the database backed up (on off check/make toggle?)

  • Server Client Information

  • Server Installation Location:

  • Server Database location:

  • Database type:

  • Database backup enabled:

  • Database backup configuration

  • License Key: The license information of the software.

  • Description: Any additional notes or comments about the software

  • Client Installation Information:

  • Client installer location:

  • Client installation location:

  • Website url:

  • Client License Key:

  • Additional Installation Notes: Any additional notes or comments about the installation of the software.

  • Validated (Toggle): Is this a validated software. (Toggle on or off)