ServiceNow CMDB Explained: What It Is, How It Works, Why It Matters

What is ServiceNow's CMDB?

Definition and Purpose

• The ServiceNow Configuration Management Database (CMDB) is defined as a series of tables and fields that contain all configuration items (CIs) controlled by a company, including their attributes and relationships.

• A CI is any component necessary for delivering services, typically encompassing both hardware and software elements.

• Essentially, the CMDB serves as a logical model of the company's IT infrastructure, detailing how components are connected and configured to provide services.

Exploring the Now Platform

• Accessing the Now platform UI allows users to view all existing tables in the ServiceNow database, with 4605 tables available.

• Filtering for CMDB-related tables reveals 923 specific tables that store various hardware, software, and service components relevant to the company's infrastructure.

How Does Data Populate the CMDB?

Data Entry Channels

• Configuration items can be added manually through forms in the ServiceNow user interface; however, this method can be time-consuming and prone to errors.

• Integrations with existing inventory systems allow for automated data import into the CMDB using supported connectors like Excel files or SQL databases.

• Scheduled integrations ensure that data remains fresh and accurate by regularly pulling updates from external sources.

Automated Discovery Tools in ServiceNow

Overview of Automated Discovery

• Automated discovery tools are the most efficient and preferred method for ingesting configuration items (CIs) into a Configuration Management Database (CMDB). These tools crawl networks to identify IP-based devices using configurable patterns.

• ServiceNow provides training courses on automated discovery, featuring two primary tools: Discovery and Service Mapping. The Discovery tool focuses on identifying devices and software (horizontal discovery), while Service Mapping identifies relationships between CIs (vertical discovery).

Integration with Third-party Tools

• In addition to ServiceNow's tools, third-party solutions like Microsoft SCCM can be utilized for automated discovery. Multiple discovery tools can populate a single CMDB.

• Automated discovery is also applicable to cloud environments, allowing for the inclusion of CIs from platforms such as AWS, Google Cloud, or Microsoft Azure.

Challenges with Multiple Data Sources

• Having multiple data sources feeding into a single CMDB can lead to conflicts and inaccuracies, such as duplication of CIs when an item is entered manually, integrated through another source, or discovered automatically.

• Overloading occurs when attributes meant for separate items mistakenly update a CI. Conflicting attribute values from different sources may cause flip-flopping updates.

Identification and Reconciliation Engine

• To mitigate these issues, ServiceNow employs the Identification and Reconciliation Engine (IRE), which uses configurable rules to uniquely identify items and manage updates effectively.

Hierarchical Database Structure

• The hierarchical database schema used by ServiceNow allows efficient management of potentially millions of CIs by creating parent-child table relationships that propagate attributes down the hierarchy.

• For example, a base table named "Hardware" can have child tables for specific types like printers and computers that inherit common attributes while adding their own unique fields.

Example of Table Hierarchy

• If we create additional tables under "Computer" for personal computers and servers, each can store specific details relevant to their category while still retaining common hardware attributes.

• Records can be added at any level within this hierarchy; inserting records into various tables demonstrates how they aggregate into total counts across categories.

Base Tables in CMDB

• Tables at the top of the hierarchy are known as base tables; in this case, "Hardware" serves as a base table.

• The ultimate ancestor in this structure is the "Configuration Item" table which stores common attributes for all CIs across the platform.

This structured approach ensures clarity regarding how automated discovery works within ServiceNow's ecosystem while highlighting potential challenges associated with data integration.

CMDB Overview and CI Class Manager

Introduction to CMDB and CI Class Manager

• The Configuration Management Database (CMDB) includes various modules, with the CI Class Manager being particularly useful for creating and updating configuration item classes.

• In ServiceNow, the term "class" refers to a type of configuration item, each corresponding to a database table that stores these items.

Understanding the Hierarchy of Classes

• The configuration item class is at the top of the hierarchy, with 2785 total CIs in the current CMDB.

• The hardware class contains 902 hardware CIs and is extended by nine additional classes, illustrating how specificity increases as one delves deeper into the hierarchy.

Exploring Class Details

• Within each class, tabs allow navigation through parameters; basic info includes display name, extendability status, and database table names.

• The attributes tab lists fields within the database for this item type, allowing filtering based on field origin.

Identification and Reconciliation Rules

• The Identification and Reconciliation Engine (IRE) uses configurable rules to identify existing CIs or create new ones to prevent duplication.

• IRE searches according to identifier entries in order of priority; if no match is found after all entries are exhausted, a new CI is created.

Matching Process Explained

• For example, when identifying a computer type item, searches occur across multiple tables: serial number table first, followed by hardware table checks for name matches.

• Reconciliation rules dictate how updates are processed once a match is found; they can prioritize data sources for accuracy.

Suggested Relationships and Health Metrics

• Suggested relationships define logical connections between classes (e.g., computers powered by racks), aiding integration efforts.

• Health metrics can be set up in the dashboard to measure completeness, compliance, and correctness of items within this class.

Additional Tools Related to CMDB

• Beyond CI Class Manager, other tools like CMDB Data Manager help manage policies as CMDB grows while dashboards provide insights into data quality.

• Stakeholders are identified as primary users who benefit from services provided by the CMDB.

ServiceNow CMDB Fundamentals

Understanding Service Outages and the Role of CMDB

• In the event of a service outage, numerous users may be affected, prompting involvement from service desk analysts, technicians, and support teams to diagnose and resolve issues quickly.

• A well-implemented Configuration Management Database (CMDB) can provide immediate access to critical information necessary for rapid issue resolution, including details about impacted services and their supporting hardware and software relationships.

• Various stakeholders rely on the CMDB for different purposes: security teams may need to scan databases for vulnerabilities, asset management requires insights into hardware/software usage, and auditing needs comprehensive listings of business applications.

Importance of CMDB in Modern Enterprises

• The tables that constitute the CMDB are essential components of the larger ServiceNow platform; many applications within this platform are designed to reference related configuration items through incident management processes.

• ServiceNow provides standardized definitions and guidelines for modeling within the CMDB through its Common Services Data Model (CSDM), which aligns configuration items with business strategies. This serves as a best practices guide for managing the ServiceNow CMDB.

Conclusion

• The video concludes by encouraging viewers to subscribe and engage with comments while emphasizing the importance of understanding how the CMDB integrates into the broader scope of the ServiceNow platform.