Understanding the cmdb_ci_ip_switch Table in ServiceNow
In the world of IT service management, effective management of network infrastructure is paramount. ServiceNow, a leading platform in this domain, offers a comprehensive solution for managing Configuration Management Databases (CMDBs), which serve as a centralized repository for IT infrastructure information. Among the crucial tables within the ServiceNow CMDB is the cmdb_ci_ip_switch table, which plays a pivotal role in managing network switches. In this article, we delve into the significance and functionalities of the cmdb_ci_ip_switch table in ServiceNow.
What is the cmdb_ci_ip_switch Table?
The cmdb_ci_ip_switch table is a core component of the ServiceNow CMDB, specifically designed to store information related to network switches. These switches serve as the backbone of enterprise networks, facilitating the flow of data between devices and ensuring seamless communication.
Derivation Hierarchy
ServiceNow
Key Attributes of the cmdb_ci_ip_switch Table:
Name: This field represents the name of the network switch, which is typically assigned based on organizational conventions or device specifications.
Serial Number: A unique identifier assigned to each network switch, aiding in asset tracking and management.
Model: Indicates the model or type of switch, providing insights into its capabilities and features.
Manufacturer: Specifies the manufacturer of the switch, crucial for warranty tracking and vendor management.
MAC Address: The Media Access Control address uniquely identifies the switch within the network, facilitating communication at the data link layer.
Functionality and Use Cases:
Inventory Management: The cmdb_ci_ip_switch table serves as a centralized repository for storing information about network switches deployed across the organization. This facilitates efficient inventory management, enabling IT teams to track the availability, location, and status of switches.
Relationship Mapping: ServiceNow CMDB allows for the establishment of relationships between various configuration items. The cmdb_ci_ip_switch table can be linked to other CI tables such as servers, routers, and access points, providing a holistic view of network infrastructure dependencies.
Configuration Management: IT administrators can utilize the cmdb_ci_ip_switch table to manage configuration details of network switches, including firmware versions, port configurations, and VLAN assignments. This ensures compliance with organizational standards and enhances network security.
Incident and Problem Management: In the event of network issues or outages, the cmdb_ci_ip_switch table provides vital information for troubleshooting and resolving incidents. By accessing switch details such as port status and connectivity, IT support teams can expedite problem resolution and minimize downtime.
Best Practices for Managing cmdb_ci_ip_switch Records:
Regular Updates: Ensure that switch information in the cmdb_ci_ip_switch table is regularly updated to reflect changes in the network infrastructure, such as hardware upgrades or relocations.
Documentation: Maintain comprehensive documentation for each switch, including configuration settings, maintenance records, and network diagrams, to facilitate efficient management and troubleshooting.
Automation: Leverage automation capabilities within ServiceNow to streamline tasks such as discovery, reconciliation, and provisioning of network switches, reducing manual effort and minimizing errors.
Security Considerations: Implement access controls and encryption measures to safeguard sensitive information stored in the cmdb_ci_ip_switch table, preventing unauthorized access or tampering.
Conclusion:
The cmdb_ci_ip_switch table in ServiceNow plays a crucial role in managing network infrastructure, providing a centralized repository for storing, managing, and analyzing information related to network switches. By leveraging the capabilities of this table, organizations can achieve greater visibility, efficiency, and control over their network environment, ultimately enhancing service delivery and reliability.
| Image | Description |
|
01. Access ServiceNow: Log in to your ServiceNow instance using your user credentials. |
 |
02. Navigate to CMDB: In the main menu of ServiceNow, locate and access the CMDB (Configuration Management Database) module.
>>All > Configuration > Network > Switches |
|
Click New |
|
|
 
|
|
|
|
|
| Table | Column label | Column name | Type | Reference Table | Max length |
| cmdb_ci_ip_switch | Approval group | change_control | Reference | Group | 32 |
| cmdb_ci_ip_switch | Asset | asset | Reference | Asset | 32 |
| cmdb_ci_ip_switch | Asset tag | asset_tag | String | 40 | |
| cmdb_ci_ip_switch | Assigned | assigned | Date/Time | 40 | |
| cmdb_ci_ip_switch | Assigned to | assigned_to | Reference | User | 32 |
| cmdb_ci_ip_switch | Attestation Score | attestation_score | Integer | 40 | |
| cmdb_ci_ip_switch | Attestation Status | attestation_status | String | 40 | |
| cmdb_ci_ip_switch | Attested | attested | True/False | 40 | |
| cmdb_ci_ip_switch | Attested By | attested_by | Reference | User | 32 |
| cmdb_ci_ip_switch | Attested Date | attested_date | Date/Time | 40 | |
| cmdb_ci_ip_switch | Attributes | attributes | String | 65000 | |
| cmdb_ci_ip_switch | Business Unit | business_unit | Reference | Business Unit | 32 |
| cmdb_ci_ip_switch | Can hub IP | can_hub | True/False | 40 | |
| cmdb_ci_ip_switch | Can partition VLANs | can_partitionvlans | True/False | 40 | |
| cmdb_ci_ip_switch | Can Print | can_print | True/False | 40 | |
| cmdb_ci_ip_switch | Can route IP | can_route | True/False | 40 | |
| cmdb_ci_ip_switch | Can switch IP | can_switch | True/False | 40 | |
| cmdb_ci_ip_switch | Category | category | String | 40 | |
| cmdb_ci_ip_switch | Change Group | assignment_group | Reference | Group | 32 |
| cmdb_ci_ip_switch | Channels | channels | Integer | 40 | |
| cmdb_ci_ip_switch | Checked in | checked_in | Date/Time | 40 | |
| cmdb_ci_ip_switch | Checked out | checked_out | Date/Time | 40 | |
| cmdb_ci_ip_switch | Class | sys_class_name | System Class Name | 80 | |
| cmdb_ci_ip_switch | Comments | comments | String | 4000 | |
| cmdb_ci_ip_switch | Company | company | Reference | Company | 32 |
| cmdb_ci_ip_switch | Correlation ID | correlation_id | String | 512 | |
| cmdb_ci_ip_switch | Cost | cost | Floating Point Number | 40 | |
| cmdb_ci_ip_switch | Cost center | cost_center | Reference | Cost Center | 32 |
| cmdb_ci_ip_switch | Cost currency | cost_cc | String | 3 | |
| cmdb_ci_ip_switch | CPU count | cpu_count | Integer | 40 | |
| cmdb_ci_ip_switch | CPU manufacturer | cpu_manufacturer | Reference | Company | 32 |
| cmdb_ci_ip_switch | CPU speed (MHz) | cpu_speed | Decimal | 15 | |
| cmdb_ci_ip_switch | CPU type | cpu_type | String | 40 | |
| cmdb_ci_ip_switch | Created | sys_created_on | Date/Time | 40 | |
| cmdb_ci_ip_switch | Created by | sys_created_by | String | 40 | |
| cmdb_ci_ip_switch | Default Gateway | default_gateway | String | 40 | |
| cmdb_ci_ip_switch | Department | department | Reference | Department | 32 |
| cmdb_ci_ip_switch | Description | short_description | String | 1000 | |
| cmdb_ci_ip_switch | Device type | device_type | String | 40 | |
| cmdb_ci_ip_switch | Discovery Protocol ID | discovery_proto_id | String | 256 | |
| cmdb_ci_ip_switch | Discovery Protocol Type | discovery_proto_type | String | 40 | |
| cmdb_ci_ip_switch | Discovery source | discovery_source | String | 40 | |
| cmdb_ci_ip_switch | Disk space (GB) | disk_space | Decimal | 15 | |
| cmdb_ci_ip_switch | DNS Domain | dns_domain | String | 255 | |
| cmdb_ci_ip_switch | Domain | sys_domain | Domain ID | 32 | |
| cmdb_ci_ip_switch | Domain Path | sys_domain_path | Domain Path | 255 | |
| cmdb_ci_ip_switch | Due | due | Date/Time | 40 | |
| cmdb_ci_ip_switch | Due in | due_in | String | 40 | |
| cmdb_ci_ip_switch | Duplicate Of | duplicate_of | Reference | Configuration Item | 32 |
| cmdb_ci_ip_switch | Environment | environment | String | 40 | |
| cmdb_ci_ip_switch | Estimated bandwidth | bandwidth | Integer | 40 | |
| cmdb_ci_ip_switch | Fault count | fault_count | Integer | 40 | |
| cmdb_ci_ip_switch | Firmware manufacturer | firmware_manufacturer | Reference | Company | 32 |
| cmdb_ci_ip_switch | Firmware version | firmware_version | String | 40 | |
| cmdb_ci_ip_switch | First discovered | first_discovered | Date/Time | 40 | |
| cmdb_ci_ip_switch | Fully qualified domain name | fqdn | String | 255 | |
| cmdb_ci_ip_switch | GL account | gl_account | String | 40 | |
| cmdb_ci_ip_switch | Hardware Status | hardware_status | String | 40 | |
| cmdb_ci_ip_switch | Install Status | install_status | Integer | 40 | |
| cmdb_ci_ip_switch | Installed | install_date | Date/Time | 40 | |
| cmdb_ci_ip_switch | Internet Facing | internet_facing | True/False | 40 | |
| cmdb_ci_ip_switch | Invoice number | invoice_number | String | 40 | |
| cmdb_ci_ip_switch | IP Address | ip_address | IP Address (Validated IPV4, IPV6) | 255 | |
| cmdb_ci_ip_switch | Justification | justification | String | 80 | |
| cmdb_ci_ip_switch | Lease contract | lease_id | String | 40 | |
| cmdb_ci_ip_switch | Life Cycle Stage | life_cycle_stage | Reference | Life Cycle Stage | 100 |
| cmdb_ci_ip_switch | Life Cycle Stage Status | life_cycle_stage_status | Reference | Life Cycle Stage Status | 100 |
| cmdb_ci_ip_switch | Location | location | Reference | Location | 32 |
| cmdb_ci_ip_switch | MAC Address | mac_address | String | 24 | |
| cmdb_ci_ip_switch | Maintenance schedule | maintenance_schedule | Reference | Schedule | 32 |
| cmdb_ci_ip_switch | Managed by | managed_by | Reference | User | 32 |
| cmdb_ci_ip_switch | Managed By Group | managed_by_group | Reference | Group | 32 |
| cmdb_ci_ip_switch | Manufacturer | manufacturer | Reference | Company | 32 |
| cmdb_ci_ip_switch | Model ID | model_id | Reference | Product Model | 32 |
| cmdb_ci_ip_switch | Model number | model_number | String | 255 | |
| cmdb_ci_ip_switch | Monitor | monitor | True/False | 40 | |
| cmdb_ci_ip_switch | Most frequent logged in user | most_frequent_user | Reference | User | 32 |
| cmdb_ci_ip_switch | Most recent discovery | last_discovered | Date/Time | 40 | |
| cmdb_ci_ip_switch | Name | name | String | 255 | |
| cmdb_ci_ip_switch | Operational status | operational_status | Integer | 40 | |
| cmdb_ci_ip_switch | Order received | delivery_date | Date/Time | 40 | |
| cmdb_ci_ip_switch | Ordered | order_date | Date/Time | 40 | |
| cmdb_ci_ip_switch | Owned by | owned_by | Reference | User | 32 |
| cmdb_ci_ip_switch | Physical interface count | physical_interface_count | Integer | 40 | |
| cmdb_ci_ip_switch | PO number | po_number | String | 40 | |
| cmdb_ci_ip_switch | Ports | ports | Integer | 40 | |
| cmdb_ci_ip_switch | Purchased | purchase_date | Date | 40 | |
| cmdb_ci_ip_switch | RAM (MB) | ram | Integer | 40 | |
| cmdb_ci_ip_switch | Range | range | Integer | 40 | |
| cmdb_ci_ip_switch | Requires verification | unverified | True/False | 40 | |
| cmdb_ci_ip_switch | Schedule | schedule | Reference | Schedule | 32 |
| cmdb_ci_ip_switch | Serial number | serial_number | String | 255 | |
| cmdb_ci_ip_switch | Skip sync | skip_sync | True/False | 40 | |
| cmdb_ci_ip_switch | SNMP Location | snmp_sys_location | String | 255 | |
| cmdb_ci_ip_switch | Stack | stack | True/False | 40 | |
| cmdb_ci_ip_switch | Stack Mode | stack_mode | String | 40 | |
| cmdb_ci_ip_switch | Start date | start_date | Date/Time | 40 | |
| cmdb_ci_ip_switch | Subcategory | subcategory | String | 40 | |
| cmdb_ci_ip_switch | Substatus | hardware_substatus | String | 40 | |
| cmdb_ci_ip_switch | Support group | support_group | Reference | Group | 32 |
| cmdb_ci_ip_switch | Supported by | supported_by | Reference | User | 32 |
| cmdb_ci_ip_switch | Sys class path | sys_class_path | System Class path | 255 | |
| cmdb_ci_ip_switch | Sys ID | sys_id | Sys ID (GUID) | 32 | |
| cmdb_ci_ip_switch | Updated | sys_updated_on | Date/Time | 40 | |
| cmdb_ci_ip_switch | Updated by | sys_updated_by | String | 40 | |
| cmdb_ci_ip_switch | Updates | sys_mod_count | Integer | 40 | |
| cmdb_ci_ip_switch | Vendor | vendor | Reference | Company | 32 |
| cmdb_ci_ip_switch | Warranty expiration | warranty_expiration | Date | 40 |
>> cmdb > cmdb_ci > cmdb_ci_hardware > cmdb_ci_netgear > cmdb_ci_ip_switch
Approval Group
The "Approval Group" field in the table of ServiceNow typically refers to the group responsible for approving changes related to the CI registered in the CMDB (Configuration Management Database). This field is used to designate the group of users who have the authority to review and approve changes or requests related to CI within the organization.
When a change or request involving a CI is submitted, it may need to undergo an approval process before being implemented. The "Approval Group" field is where the group responsible for this approval is specified. This group may include members of the IT team, network administrators, or other individuals responsible for the governance and security of the network infrastructure.
By defining the approval group, the organization can ensure that changes to the CI are reviewed by individuals with the necessary authority and knowledge before being implemented, helping to minimize risks and ensure the integrity of the network.
Asset
The Asset field serves as a link between the network switch (CI) and its corresponding asset record.
Traditionally, the Asset field may refer to tangible physical assets such as network switches, including their hardware specifications, serial numbers, and physical locations within the organization's infrastructure. This information is vital for inventory management, asset tracking, and maintenance planning.
.
Asset tag
The "Asset Tag" field within the CI table serves as a unique identifier assigned to individual network switches within the ServiceNow CMDB framework. This alphanumeric or numeric label acts as a digital fingerprint, facilitating precise identification and tracking of network assets across the IT landscape. While seemingly straightforward, the Asset Tag carries layers of significance and functionality crucial for effective asset management.
.
Assigned
.
Assigned to
The "Assigned to" field in the CI table in ServiceNow typically refers to the person or team responsible for the maintenance and management of the specific CI registered in the CMDB (Configuration Management Database).
When a new CI record is created or when changes or issues related to an existing CI occur, the "Assigned to" field can be used to designate who is responsible for handling that particular CI. This may include network administrators, IT support team members, or anyone designated to address operation, configuration, maintenance, or troubleshooting issues with the CI.
By assigning someone as "Assigned to" for a specific CI, the organization can ensure clear responsibility and accountability for managing that network asset, facilitating communication and tracking related issues. This can also help ensure that tasks and problems are handled efficiently and promptly.
Attestation Score
.
Attestation Status
he "Attestation Status" field in the CI table in ServiceNow typically refers to the attestation or verification status of a CI registered in the CMDB (Configuration Management Database).
The attestation process in ServiceNow is used to verify and confirm the accuracy and integrity of configuration data stored in the CMDB. This often involves periodic reviews of configuration records to ensure they are up-to-date, accurate, and aligned with the organization's actual IT infrastructure.
The "Attestation Status" field may have different values to indicate the attestation status of a specific CI. Some common examples of values include:
Attested: Indicates that the CI has successfully passed the attestation process and that the associated configuration data has been verified and confirmed as accurate and up-to-date.
Not Yet Reviewed: Pending - Indicates that the CI is awaiting review and verification during the attestation process. This may occur when a periodic review is scheduled but has not yet been completed.
Rejected: Indicates that the CI does not meet the criteria for accuracy or integrity during the attestation process and that the configuration data may require correction or updating.
The "Attestation Status" field is important for ensuring the quality and reliability of the data stored in the CMDB, helping organizations maintain an accurate and up-to-date view of their IT infrastructure, and quickly identify and address any discrepancies or configuration issues.
.
Attested
.
Attested By
The "Attested By" field is filled with the name of the person or entity who performed the attestation of the CI. This attestation is part of a rigorous process to ensure that the data in the CMDB is accurate and up-to-date. The presence of a name in the "Attested By" field means that the identified person has reviewed and validated the CI’s information, ensuring it meets the organization’s quality standards.
The integration of this field with the "Attestation Status" field allows organizations to maintain an accurate and up-to-date view of their IT infrastructure, quickly identifying and addressing any discrepancies or configuration issues that may arise.
In summary, the "Attested By" field not only enhances accountability and traceability but also significantly contributes to maintaining the quality and reliability of the data in the CMDB.
.
Attested Date
The "Attested Date" field is a critical component of the attestation process within the CMDB. This date ensures that the data about each CI is not only accurate but also regularly reviewed and validated, enhancing the overall reliability and governance of the IT infrastructure data.
Attributes
.
Business Unit
.
Can hub IP
.
Can partition VLANs
.
Can Print
.
Can route IP
Can switch IP
Category
Change Group
Channels
Checked in
Checked out
Class
The "Class" field in the CI table in ServiceNow refers to the classification or category of the CI entity within the Configuration Management Database (CMDB).
In ServiceNow, the CMDB is used to store information about various configuration items (CIs) within an organization's IT infrastructure. These configuration items can include hardware, software, network devices, and other assets. The "Class" field helps organize and categorize these items based on their characteristics and functionalities.
For the CI table specifically, the "Class" field would indicate that the record represents a CI device within the CMDB. This classification is important for identifying and managing CI's separately from other types of network devices or IT assets.
By utilizing the "Class" field, organizations can effectively organize and classify their IT assets in the CMDB, making it easier to search for, report on, and manage specific types of devices within their infrastructure. Additionally, it helps standardize the data model and allows for consistent handling of different types of configuration items.
Comments
Company
The "Company" field in the CI table of ServiceNow refers to the company or organization to which the CI is associated or belongs. This field is used to designate the entity within the ServiceNow instance that owns or is responsible for the CI device.
In ServiceNow, companies or organizations are often represented as separate entities or records, typically stored in a table such as "core_company" or similar. The "Company" field in the CI table establishes a relationship between the CI record and the corresponding company record.
Assigning a value to the "Company" field allows organizations to organize and manage their CI devices based on ownership or responsibility. It helps in segmenting data within the CMDB, enabling users to view and access CI records specific to their company or organizational unit.
This field is particularly useful in multi-company or multi-tenant ServiceNow instances where different companies or business units share the same instance but have separate sets of data and configurations. By utilizing the "Company" field, organizations can maintain data segregation and ensure that CI records are associated with the appropriate company or organizational entity.
Correlation ID
Cost
cost_center
The "cost_center" field in the CI table of ServiceNow is used to store information about the cost center associated with the CI A cost center is an entity within an organization that is responsible for controlling and accounting for costs associated with certain activities, projects, or business areas.
In the context of ServiceNow, associating a cost center with a network CI allows organizations to track and assign specific costs related to the operation, maintenance, and support of that network device. This can be useful for accounting purposes, financial planning, and resource allocation.
For example, a cost center may be assigned to a CI used by a specific department within the organization. This enables the operational costs associated with that department to be separated and tracked independently of other departments or business areas.
By associating a cost center with the "cost_center" field in ServiceNow, organizations can gain a clearer and more granular view of the costs related to the operation and maintenance of their CI's, aiding in financial decision-making and effective resource management.
Cost currency
CPU count
CPU manufacturer
CPU speed (MHz)
CPU type
Created
Created by - sys_created_by
The "sys_created_by" field in the CI table of ServiceNow is an automatic field that stores the username or user ID of the individual who created the record of the CI in the system. This field is populated automatically and captures the identity of the user who performed the action of creating the record, this field would be described as "Created by" or "Created by User". It provides information about who was responsible for adding the CI to the ServiceNow CMDB database. This is useful for tracking and auditing purposes, allowing system administrators to know who executed certain actions in the system.
Default Gateway
Department
Description
Device type
Discovery Protocol ID
Discovery Protocol Type
Discovery source
Disk space (GB)
DNS Domain
Domain - sys_domain
The "sys_domain" field in the CI table of ServiceNow represents the domain to which the CI record belongs.
In ServiceNow, domains are used to group records and users within the instance based on organizational boundaries or functional divisions. Each record in the CMDB can be associated with a specific domain, which helps in organizing and securing data within the system his field would be described as "Domain". It signifies the domain context or scope of the CI within the ServiceNow instance, indicating which organizational unit or functional area it belongs to. This can be useful for access control, permissions management, and data segmentation purposes within the CMDB.
Domain Path
Due
Due in
Duplicate Of
Environment
Estimated bandwidth
Fault count
Firmware manufacturer
Firmware version
First discovered - first_discovered
The "first_discovered" field in the CI table of ServiceNow indicates the date and time when the CI was first discovered or detected within the organization's IT infrastructure.
This field is automatically populated by ServiceNow and captures the timestamp of when the CI record was initially identified by a discovery process or integration with network monitoring tools.
In essence, the "first_discovered" field serves as a historical record, providing insight into the timeline of when the CI became known to the ServiceNow CMDB. This information can be valuable for tracking changes in the network environment, troubleshooting issues, and maintaining an accurate inventory of IT assets over time.
Fully qualified domain name
GL account
Hardware Status
Install Status
Installed
Internet Facing
Invoice number
IP Address
Justification
Lease contract
Life Cycle Stage
Life Cycle Stage Status
Location
MAC Address
Maintenance schedule - maintenance_schedule
The "maintenance_schedule" field in the CI table of ServiceNow typically stores information about the scheduled maintenance activities planned for the CI.
This field allows organizations to record and manage planned maintenance activities, such as software updates, hardware upgrades, or routine maintenance tasks, for their CI. It may include details such as the date, time, duration, and description of the scheduled maintenance.
By documenting maintenance schedules in ServiceNow, organizations can keep track of upcoming maintenance activities, coordinate with relevant teams or personnel, and ensure minimal disruption to network operations. Additionally, it facilitates historical tracking of maintenance activities for auditing and compliance purposes.
Managed by - managed_by
The "managed_by" field in the CI table of ServiceNow typically indicates the individual, team, or entity responsible for managing or overseeing the CI.
This field stores information about who is assigned or designated as the manager or responsible party for the CI / device within the organization. It may contain the name, username, or ID of the person, team, or department responsible for tasks such as configuration, monitoring, maintenance, and troubleshooting of the CI.
Assigning a value to the "managed_by" field helps ensure clear accountability and ownership for the management of the CI within the organization. It facilitates communication, coordination, and collaboration among team members or departments involved in network management activities. Additionally, it provides valuable information for tracking and auditing purposes, allowing organizations to maintain visibility into CI management responsibilities.
Managed By Group
Manufacturer
Model ID - model_id
The "model_id" field in the CI table of ServiceNow typically stores the unique identifier or reference to the specific model of the CI.
This field is used to link the CI record in the CMDB to a corresponding entry in the "cmdb_model" table, which contains detailed information about various models of IT assets, including switches, routers.
By storing the model identifier in the "model_id" field, ServiceNow enables organizations to maintain a standardized and structured representation of their CI's. This allows for efficient tracking, reporting, and management of CI's models throughout their lifecycle, including inventory management, configuration management, and procurement processes.
Having accurate model information associated with CI records helps organizations make informed decisions regarding maintenance, upgrades, and replacements, as well as ensures compliance with configuration standards and compatibility requirements.
Model number
Monitor
Most frequent logged in user
Most recent discovery
name
The "name" field in the CI table of ServiceNow typically stores the name or label assigned to the CI.
This field contains a human-readable identifier that helps to distinguish and identify the CI within the organization's IT infrastructure. The name assigned to the CI can be based on various factors, such as location, function, or any other relevant naming convention used by the organization.
By populating the "name" field, ServiceNow allows users to easily search for and reference specific CI within the CMDB. This facilitates efficient management, monitoring, and troubleshooting of network devices by providing a clear and identifiable label for each CI record.
In summary, the "name" field serves as a descriptive identifier for the CI enabling users to quickly identify and work with CI records in ServiceNow.
Operational status - operational_status
The "operational_status" field in the CI table of ServiceNow typically indicates the current operational status or condition of the CI.
This field stores information about whether the CI is operational, offline, undergoing maintenance, or experiencing any other status that affects its functionality within the organization's IT infrastructure. The values stored in this field may include:
- Operational: Indicates that the CI is currently functioning normally and is operational, actively routing network traffic.
- Non-Operational: Indicates that the CI is not currently operational or is offline, meaning it is not actively routing network traffic and may be experiencing issues.
- Repair in Progress: Indicates that the CI is undergoing repairs or maintenance activities to address issues and restore functionality. It may be temporarily out of service during this time.
- DR Standby: Indicates that the CI is in standby mode and ready to be activated as part of a disaster recovery (DR) plan. It is typically used as a backup CI to maintain network connectivity in the event of a primary CI failure.
- Ready: Indicates that the CI is prepared and available for use but may not currently be actively routing network traffic.
- Retired: Indicates that the CI has been decommissioned or retired from service and is no longer actively used in the network infrastructure. It may be kept for archival purposes or eventual disposal.
By tracking the operational status of CI's in the CMDB, ServiceNow enables organizations to monitor the health and availability of their network infrastructure. This information helps IT teams quickly identify and respond to issues, plan maintenance activities, and ensure the smooth operation of the network. Additionally, it provides valuable insights for reporting, analysis, and decision-making purposes within the organization.
Order received
Ordered
Owned by
Physical interface count
PO number
Ports
Purchased
RAM (MB)
Range
Requires verification
Schedule
Serial number
Skip sync
SNMP Location
Stack
Stack Mode
Start date
Subcategory - subcategory
The "subcategory" field in the CI table of ServiceNow typically refers to a more specific classification or categorization of the CI.
This field is used to further categorize CI's based on their specific attributes, characteristics, or functionalities. It provides additional granularity beyond the general category of "CI" and allows organizations to organize and manage CI's based on more detailed criteria.
By using the "subcategory" field, organizations can classify CI's according to their specific roles, configurations, or deployment scenarios, facilitating more targeted management, monitoring, and reporting of network infrastructure. This enhances the organization's ability to effectively manage its IT assets and ensure alignment with business needs and objectives.
Substatus
Support group - support_group
he "support_group" field in the "CI" table of ServiceNow typically indicates the group or team responsible for providing support and assistance for the network CI.
This field stores information about the specific support group within the organization that is tasked with handling incidents, requests, and other issues related to the CI. The support group may include members of the IT support team, network operations center (NOC), or other specialized teams responsible for network infrastructure management.
Assigning a value to the "support_group" field helps ensure that incidents and requests concerning the CI's are routed to the appropriate team or individuals for resolution. It streamlines communication and coordination, allowing for efficient handling of issues and minimizing downtime.
By tracking the support group associated with each CI record, ServiceNow enables organizations to effectively manage and prioritize support activities, allocate resources appropriately, and ensure timely resolution of network-related issues.
Supported by
Sys class path - sys_class_path
The "sys_class_path" field in the "CI" table of ServiceNow typically stores the class path of the CI record within the CMDB (Configuration Management Database) hierarchy.
This field contains a hierarchical path or reference that indicates the location of the CI record within the CMDB's class hierarchy. The class hierarchy represents the structure and relationships between different types of configuration items (CIs) in the CMDB.
For example, the class path might include the names of parent classes, such as "cmdb_ci" (the base class for all CIs) and "cmdb_ci_network_device" (the class for network devices), followed by the specific CI class name.
The "sys_class_path" field is useful for navigation and categorization within the CMDB hierarchy. It provides a way to understand the context of the CI record within the broader classification scheme of configuration items in the CMDB.
By storing the class path, ServiceNow enables users to efficiently locate and work with CI records, as well as to understand their relationships to other configuration items in the CMDB. This supports effective configuration management, troubleshooting, and reporting activities within the organization's IT infrastructure.
Sys ID
What is the "Sys ID" Field?
The "Sys ID" field is a unique identifier assigned to each record in ServiceNow. This identifier is a 32-character globally unique identifier (GUID) that ensures each record can be uniquely distinguished from others within the system.
The "Sys ID" field is a fundamental element in ServiceNow, providing a unique identifier for each record. This unique ID is essential for maintaining data integrity, creating relationships between records, supporting API interactions, and ensuring accurate tracking and auditing of changes within the system.
Updated
The "Updated" field in ServiceNow is a system-generated field that records the date and time when a particular record was last modified. This field is automatically updated by the system whenever any change is made to the record.
The "Updated" field in ServiceNow is a critical component for tracking the modification history of records. It enhances data integrity, supports audit and compliance requirements, facilitates synchronization with external systems, and aids in reporting and analytics. By automatically recording the date and time of the last update, this field ensures that the modification history of every record is accurately documented.
Updated by
The "Updated by" field in ServiceNow is a system-generated field that records the username of the user who last modified a particular record. This field is automatically updated by the system whenever any change is made to the record.
The "Updated by" field in ServiceNow is a vital component for tracking who last modified a record. It enhances accountability, supports audit and compliance efforts, and facilitates better coordination among team members. By automatically recording the username of the user making the changes, this field ensures that the modification history of every record is accurately documented and attributable.
Updates
Vendor
Warranty expiration
Diagram
Improving Configuration Item Data Quality
Exploring CMDB: A Deep Dive into cmdb_ci_router in ServiceNow
https://demo.erm4sn.com/table/100/dbc4d32533452a9ed66535cf42e82d89
The Who, What, When, Where, and Why for Asset Management Training
Best Practices for CMDB Data Integration
@jtshone
Hi! The device_type field in the cmdb_ci table is used to categorize and identify the type of device that the Configuration Item represents. This field can be mapped from the asset information collected during the discovery process or manually entered. Essentially, device_type helps to ensure that the cmdb_ci and alm_asset tables are in sync regarding the type of device being managed
The cmdb_ci table and the alm_asset table are linked through the reference field ci in the alm_asset table. This field ensures that each asset in the alm_asset table is associated with its corresponding configuration item in the cmdb_ci table, maintaining accurate relationships and data integrity across the system
