---
sourceDocument: Yokohama IT Operations Management
sourceDocumentLink: https://servicenow-prod.fluidtopics.net/r/yokohama/it-operations-management

 Release :

    - yokohama

ft:locale :

    - en-US

ft:publication_title :

    - Yokohama IT Operations Management

ft:clusterId :

    - itom

bundleId :

    - itom

workflow :

    - Technology


---

# Cisco UCS

# Cisco Unified Computing System (UCS)-HD device discovery {#ariaid-title1}

* Release version: Yokohama
* 
* Updated June 1, 2026
* 
* ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 2 minutes to read

Summarize  
![AI sparkle icon](https://servicenow.com/docs/portal-asset/ai-sparkle-icon) Summarized using AI  
This content was generated using new OpenAI-powered functionality. Results are provided on an as is basis and are not guaranteed to be accurate or complete.  

## Summary of Cisco Unified Computing System (UCS)-HD device discovery

The Cisco Unified Computing System (UCS)-HD device discovery feature in ServiceNow's Discovery and Service Mapping Patterns application enables automated detection and mapping of Cisco UCS equipment, specifically chassis and B-series blades.
This discovery capability helps ServiceNow customers maintain an accurate and up-to-date Configuration Management Database (CMDB) by populating detailed hardware and relationship data for UCS devices.
Show full answer Show less  
To use this feature effectively, customers may need to update to the latest Discovery and Service Mapping Patterns application from the ServiceNow Store. The discovery process is focused on B-series devices; it does not detect C, S, or E series UCS devices.

## Prerequisites

* **SNMP Credentials:** Create SNMP credentials for secure access to UCS devices.
* **Applicative Credentials:** Create credentials specifically for the Cisco UCS Equipment CI type to allow pattern execution.
* **Network Connectivity:** Ensure the MID Server has HTTPS access on port 443 to the UCS Manager's management IP address.
* **UCS Manager Account:** The account must have at least read-only permissions and rights to execute XML API queries on key UCS object classes such as computeRackUnit, equipmentChassis, computeBlade, and others.

## Discovery Process and Data Collected

The discovery uses the **HorizontalDiscoveryProbe** to trigger the UCS - HD pattern, employing specific SNMP OIDs to identify UCS equipment models like the 6120XP, 6140XP, 6248UP, and 6296UP Fabric Interconnects.

When running the UCS - HD pattern, Discovery populates the CMDB with detailed information across several CI types:

* **Cisco UCS Equipment:** Includes fields such as name, IP address, model ID, distinguished name, and UCS Manager version.
* **Cisco UCS Chassis:** Captures name, model number, serial number, chassis ID, operational status, and distinguished name.
* **Cisco UCS Blade:** Records details including model number, serial number, CPU and core counts, RAM, adapter count, chassis and slot IDs, operational status, and blade serial number.
* **Cisco UCS Rack Mount Units:** Contains vendor, server ID, availability, UUID, rack serial, CPU counts, model ID, total memory, state, and distinguished name.

## Relationships Created

To support comprehensive UCS discovery, ServiceNow establishes key relationships between CIs, including:

* Chassis contains blades and rack units.
* Equipment contains chassis and rack units.
* Servers run on UCS blades.

## Benefits for ServiceNow Customers

This discovery pattern enables customers to:

* Automatically and accurately populate their CMDB with Cisco UCS hardware details and relationships.
* Maintain up-to-date configuration data critical for IT operations, asset management, and service mapping.
* Enhance visibility into UCS infrastructure by leveraging native ServiceNow discovery capabilities and patterns.  
Discovery and Service Mapping Patterns application uses the to find Cisco UCS equipment, including chassis and blades. Discovering some of these resources may require updating to the latest version of the Discovery and Service Mapping Patterns application from the ServiceNow Store.
Note:  
For information on Probe to Pattern migration see the knowledge article [KB0694477](https://support.servicenow.com/kb_view.do?sysparm_article=KB0694477).

## Request apps on the Store {#r-CiscoUCSHD__section_lp4_mnf_fjb}

Visit the [ServiceNow Store](https://store.servicenow.com/sn_appstore_store.do#!/store/home) website to view all the available apps and for information about submitting requests to the store. For cumulative release notes information for all released apps, see the [ServiceNow Store version history release notes](https://www.servicenow.com/docs/r/store-release-notes/sn-store-release-notes.html).{#r-CiscoUCSHD__inline-send-to-store}

## Prerequisites {#r-CiscoUCSHD__section_op5_x1f_nhc}

Create SNMP credentials
:   For more information, see [SNMP credentials](https://www.servicenow.com/docs/access?context=c_SNMPCredentials&version=yokohama&pubname=yokohama-platform-security&ft:locale=en-US).

Create applicative credentials
:   Create applicative credentials for the Cisco UCS Equipment \[cmdb_ci_ucs_equipment\] CI type. For more information, see [Applicative credentials](https://www.servicenow.com/docs/access?context=applicative-creds&version=yokohama&pubname=yokohama-platform-security&ft:locale=en-US).

Verify network connectivity
:   Verify that the MID Server has HTTPS access to the UCS Manager on port 443 and is able to reach the management IP address of the UCS equipment.

Verify UCS Manager account requirements
:   Verify that the account has at least the read-only role in UCS Manager and has permissions to execute XML API queries for the following object classes:

    * `computeRackUnit`
    * `equipmentChassis`
    * `computeBlade`
    * `mgmtIf`
    * `topSystem`
    * `versionEp`
    * `equipmentFan`
    {#r-CiscoUCSHD__ul_xm2_tvg_ljc}

Classifier, pattern, and OIDs
:
    The UCS classifier uses HorzontalDiscoveryProbe to launch the UCS - HD pattern. The classifier also uses these SNMP OIDs, which specify the Cisco UCS Equipment `[cmdb_ci_ucs_equipment]` table: {#r-CiscoUCSHD__table_jxv_mzm_qbc__entry__4}

    | OID | Manufacturer | Model | Table |
    |-|-|-|-|
    | 1.3.6.1.4.1.9.12.3.1.3.847 | Unified Computing Cisco UCS 6120XP 20-Port Fabric Interconnect | 1.4(3u)(NX-OS) 5.0 Aggregation Switch | Cisco UCS Equipment |
    | 1.3.6.1.4.1.9.12.3.1.3.899 | Unified Computing Cisco UCS 6140XP 40-Port Fabric Interconnect | 1.4(3u)(NX-OS) 5.0 Aggregation Switch | Cisco UCS Equipment |
    | 1.3.6.1.4.1.9.12.3.1.3.1062 | Unified Computing Cisco UCS 6248UP 48-Port Fabric Interconnect | 2.0(1t)(NX-OS) 5.0.2 Aggregation Switch | Cisco UCS Equipment |
    | 1.3.6.1.4.1.9.12.3.1.3.1063 | Unified Computing Cisco UCS 6296UP 96-Port Fabric Interconnect | 2.0(1t)(NX-OS) 5.0.2 Aggregation Switch | Cisco UCS Equipment |
    [ ]

    {#r-CiscoUCSHD__table_jxv_mzm_qbc}

## Data collected by Discovery during horizontal discovery {#r-CiscoUCSHD__section_pp5_x1f_nhc}

Discovery populates the data in the CMDB when running the UCS - HD pattern pattern. Only B-series devices are discovered. The UCS - HD pattern does not find C, S, or E series devices.  
{#r-CiscoUCSHD__table_hsy_ql3_cy__entry__2}

| Label | Field Name |
|-|-|
| Name | name |
| IP address | ip_address |
| Model | model_id |
| Distinguished name | dn |
| UCS Manager Version | version |
[Table 1. Cisco UCS Equipment \[cmdb_ci_ucs_equipment\]]

{#r-CiscoUCSHD__table_hsy_ql3_cy}  
{#r-CiscoUCSHD__table_jmt_rtv_cy__entry__2}

| Label | Field Name |
|-|-|
| Name | name |
| Model number | model_number |
| Serial number | serial_number |
| Chassis ID | chassis_id |
| Operational status | operational_status |
| Distinguished name | dn |
[Table 2. Cisco UCS Chassis \[cmdb_ci_ucs_chassis\]]

{#r-CiscoUCSHD__table_jmt_rtv_cy}  
{#r-CiscoUCSHD__table_igv_rtv_cy__entry__2}

| Label | Field Name |
|-|-|
| Name | name |
| Model number | model_number |
| Serial number | serial_number |
| CPU count | cpu_count |
| CPU core count | cpu_core_count |
| Ram | ram |
| Number of Adapters | number_of_adapters |
| Chassis ID | chassis_id |
| Slot ID | slot_id |
| Description | short_description |
| Distinguished name | dn |
| Blade Serial Number | blade_serial_number |
| Operational status | operational_status |
[Table 3. Cisco UCS Blade \[cmdb_ci_ucs_blade\]]

{#r-CiscoUCSHD__table_igv_rtv_cy}  
{#r-CiscoUCSHD__table_m1l_nt3_xdb__entry__2}

| Label | Field Name |
|-|-|
| Name | name |
| Vendor | vendor |
| Server ID | server_id |
| Availability | availability |
| UUID | uuid |
| Rack serial | rack_serial |
| Number of CPUs | num_of_cpus |
| Number of cores | num_of_cores |
| Model ID | model_id |
| Total Memory | total_memory |
| Distinguished name | dn |
| State | state |
[Table 4. Cisco UCS Rack Mount Units \[cmdb_ci_ucs_rack_unit\]]

{#r-CiscoUCSHD__table_m1l_nt3_xdb}

## Relationships {#r-CiscoUCSHD__section_qp5_x1f_nhc}

These relationships are created to support UCS - HD discovery.{#r-CiscoUCSHD__table_xrx_1s3_xdb__entry__3}

| CI | Relationship | CI |
|-|-|-|
| cmdb_ci_ucs_chassis | Contains::Contained by | cmdb_ci_ucs_blade |
| cmdb_ci_ucs_equipment | Contains::Contained by | cmdb_ci_ucs_rack_unit |
| cmdb_ci_ucs_equipment | Contains::Contained by | cmdb_ci_ucs_chassis |
| cmdb_ci_server | Runs on::Runs | cmdb_ci_ucs_blade |
[ ]

{#r-CiscoUCSHD__table_xrx_1s3_xdb}