---
sourceDocument: Australia IT Operations Management
sourceDocumentLink: https://www.servicenow.com/docs/r/australia/it-operations-management

 Release :

    - australia

ft:locale :

    - en-US

ft:publication_title :

    - Australia IT Operations Management

ft:clusterId :

    - itom

bundleId :

    - itom

workflow :

    - Technology


---

# Cisco UCS

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

Release version: Australia  
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 enables ServiceNow customers to discover Cisco UCS equipment, including chassis and blades, using the Discovery and Service Mapping Patterns application.
This process populates the Configuration Management Database (CMDB) with detailed information about B-series UCS devices, facilitating efficient asset management and operational visibility.
Show full answer Show less  
Note that discovery of C, S, or E series devices is not supported by the UCS - HD pattern, and some resources may require updating the Discovery and Service Mapping Patterns application from the ServiceNow Store.

## Prerequisites

* **Create SNMP credentials:** Required for accessing device information via SNMP.
* **Create applicative credentials:** Specifically for the Cisco UCS Equipment CI type to enable authenticated discovery.
* **Verify network connectivity:** Ensure the MID Server can access the UCS Manager over HTTPS on port 443 and reach the management IP.
* **Verify UCS Manager account permissions:** The account must have at least read-only access and permission to execute XML API queries on key object classes such as computeRackUnit, equipmentChassis, computeBlade, mgmtIf, topSystem, versionEp, equipmentFan.

## Discovery Process and Data Collection

The discovery uses a UCS classifier with a HorizontalDiscoveryProbe to launch the UCS - HD pattern. It leverages specific SNMP OIDs to identify UCS equipment models and manufacturers, focusing on fabric interconnects and aggregation switches.

When discovery runs, it populates the following CMDB tables with detailed attributes:

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

## Relationships Created

To accurately model the UCS environment, discovery establishes relationships such as:

* Chassis contains blades.
* Equipment contains rack units and chassis.
* Blades run servers.

## Practical Impact for ServiceNow Customers

By leveraging UCS - HD device discovery, customers can automate the population of their CMDB with detailed and structured Cisco UCS device data. This enables better asset tracking, configuration management, and supports IT operations and service management processes dependent on accurate infrastructure data.  
Discovery and Service Mapping Patterns application uses the to find Cisco UCS equipment, including chassis and blades. Discovering some of these resources might 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) 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=australia&pubname=australia-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=australia&pubname=australia-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}