---
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


---

# IBM Virtualization and HMC

# IBM Virtualization and Hardware Management Console discovery {#ariaid-title1}

Release version: Australia  
Updated March 12, 2026  
![](https://www.servicenow.com/docs/portal-asset/ico-clock) 4 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 IBM Virtualization and Hardware Management Console discovery

The IBM Virtualization and Hardware Management Console (HMC) discovery enables ServiceNow customers to automatically discover and populate Configuration Items (CIs) related to IBM hardware virtualization environments into their CMDB.
This discovery focuses on HMC servers, IBM frames (physical machines hosting logical partitions), and LPARs (logical partitions or virtual machines on IBM hardware).
Show full answer Show less  
It requires running the IBM HMC Server discovery pattern via SSH on supported operating systems: IBM AIX for LPARs and Linux for HMC servers. The discovery process populates detailed hardware and virtualization data into the CMDB to improve asset visibility and management.

## Prerequisites

* Ensure the Discovery and Service Mapping Patterns application is updated to the latest version from the ServiceNow Store.
* Verify permissions on HMC and AIX servers for specific commands essential for data gathering, such as `lssyscfg`, `lshmc`, `lshwres`, `lssysconn` on HMC, and `lparstat -i` on AIX LPARs.
* Configure SSH credentials in the ServiceNow AI Platform to enable secure access and discovery execution.

## Discovery Process

Discovery is conducted in two stages:

1. Run horizontal discovery on the HMC server IP address using the IBM HMC Server pattern.
2. After successful HMC discovery, run discovery on individual LPARs using their AIX machine IP addresses.

This sequence ensures proper hierarchical detection of hardware and virtualized instances.

## Data Collected and CMDB Population

The discovery populates specific CI classes with detailed attributes:

* **IBM HMC Server:** Includes name, frame count, serial number, IP address, OS version, CPU specs, and RAM.
* **IBM Frame:** Captures frame name, serial number, processor and memory units (current, configurable, installed), and management IP.
* **IBM LPAR Instance:** Records LPAR name, operational state (On/Off), serial number, unique object ID, VIO server flags, processing units, memory allocation, IP address, OS version, and frame association.
* **LPAR Resource:** Tracks dynamic CPU usage (high watermark) and node name linked to the LPAR instance.
* **Serial Number:** Stores the serial number of CIs for identification and tracking.

## CI Relationships

The discovery establishes relationships to accurately reflect dependencies and management hierarchies within IBM virtualization environments, such as:

* IBM HMC Server **defines** and **gets resources from** IBM frames and LPAR instances.
* IBM Frame is **managed by** the IBM HMC Server and **virtualizes** LPAR instances.
* LPAR instances reference their parent IBM frame and are linked to processor pools as members.

## Benefits for ServiceNow Customers

Using this discovery capability, customers can automate the accurate identification and mapping of IBM hardware and virtualization assets within their IT infrastructure. This leads to:

* Improved CMDB accuracy and completeness for IBM virtualization environments.
* Better visibility into hardware relationships and resource utilization.
* Enhanced ability to manage, troubleshoot, and optimize IBM virtualized resources.  
The Discovery and Service Mapping Patterns application uses the IBM HMC Server pattern to find information about Hardware Management Console (HMC), frame, and logical partition (LPAR) servers. Discovering some of these resources might require updating to the latest version of the Discovery and Service Mapping Patterns application from the ServiceNow Store.
Discovery supports the following configuration items (CIs):

* HMC server
* IBM frame
* LPAR instanceAn LPAR is the virtual machine equivalent of IBM.

* LPAR resource
{#ibm-hmc-discovery__ul_myl_nvl_43b}

Discovery is used on the HMC server and the individual AIX machines
(LPARs).

The IBM HMC Server pattern runs using SSH. It's supported to run on IBM AIX OS for LPAR and on Linux for HMC servers only.

## Request apps on the Store {#ibm-hmc-discovery__section_gvb_cql_rlb}

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).{#ibm-hmc-discovery__inline-send-to-store}

## Prerequisites {#ibm-hmc-discovery__section_vpk_ylk_43b}

Verify that the applications are up to date
:
    * Discovery and Service Mapping Patterns
    * CMDB CI Class Models
    {#ibm-hmc-discovery__ul_ktf_r2l_pdc}

Verify permissions for HMC and AIX servers
:
    * Verify you have permissions for the following HMC commands:
      * `lssyscfg`
      * `lshmc`
      * `lshwres`
      * `lssysconn -r all -F type_model_serial_num:ipaddr`
      {#ibm-hmc-discovery__ul_xvc_nbl_pdc}{#ibm-hmc-discovery__verify-permission-hmc-discovery}
    {#ibm-hmc-discovery__verify-permission-hmc-discovery}
    * Verify you have permissions for the following AIX (LPAR) command: `lparstat -i`.  
      Note:  
      The `lparstat -i` command is in addition to the commands required for AIX server discovery. For more information on AIX server discovery, see [AIX server discovery](https://www.servicenow.com/docs/7bJb1dwU52RPYL4XW1zbJw "Discovery identifies and classifies information about AIX servers."). For a list of the AIX commands, see [Service Mapping commands requiring a privileged user](https://www.servicenow.com/docs/fMLKP9ztw9H4ZPck4RnumQ "Service Mapping uses commands requiring elevated rights to discover and map Unix-based hosts in your organization. In addition to configuring necessary credentials, configure servers in your organization to allow Service Mapping to run these commands with elevated rights.").{#ibm-hmc-discovery__verify-permission-lpar-discovery}
    {#ibm-hmc-discovery__verify-permission-lpar-discovery} {#ibm-hmc-discovery__ul_hjn_vdf_qdc}

Configure SSH credentials
:   Configure SSH credentials on the ServiceNow AI Platform. For more information, see [SSH credentials](https://www.servicenow.com/docs/access?context=r_SSHCredentialsForm&version=australia&pubname=australia-platform-security&ft:locale=en-US).

Run a horizontal discovery for HMC Server and LPARs
:
    1. Run a discovery on the HMC IP address.
    2. Only when the HMC Server discovery has successfully completed, run a discovery on the LPARs using the AIX machine IP address.

    {#ibm-hmc-discovery__ol_brd_fvl_pdc}For more information on running a discovery, see [Schedule a horizontal discovery](https://www.servicenow.com/docs/VO0owNull6HAfXGFWMKxhg#t_CreateADiscoverySchedule "A discovery schedule determines what horizontal discovery searches for, when it runs, and which MID Servers are used. Create a discovery schedule for your local environment or a schedule for discovering the resources in your cloud service account.").

## Data collected by Discovery during horizontal discovery {#ibm-hmc-discovery__section_cq4_pzk_43b}

Discovery populates the data in the CMDB when running the IBM HMC Server pattern.  
{#ibm-hmc-discovery__table_c2h_qgk_pdc__entry__2}

| Field | Description |
|-|-|
| Name \[name\] | Name of the HMC. |
| Frame count \[frame_count\] | Number of frames managed for the HMC. A frame is the physical machine on which the LPARs reside. A frame is the equivalent of an ESX machine. |
| Serial number \[serial number\] | Serial number of the HMC server. |
| IP Address \[ip_address\] | IP address of the HMC. |
| OS Version \[os_version\] | Operating system version. |
| CPU type \[cpu_type\] | CPU type. |
| CPU speed (MHz) \[cpu_speed\] | CPU speed. |
| CPU count \[cpu_count\] | CPU count. |
| CPU core count \[cpu_core_count\] | CPU core count. |
| RAM (MB) \[ram\] | Memory RAM. |
[Table 1. IBM HMC Server \[cmdb_ci_hmc_server\]]

{#ibm-hmc-discovery__table_c2h_qgk_pdc}  
{#ibm-hmc-discovery__table_vx2_rgk_pdc__entry__2}

| Field | Description |
|-|-|
| Name \[name\] | Name of the frame. |
| Serial number \[serial number\] | Serial number of the Frame server. |
| Current available processor units \[curr_avail_sys_proc_units\] | Current available processor units. |
| Configurable processor units \[configurable_sys_proc_units\] | Configurable processor units. |
| Installed processor units \[installed_sys_proc_units\] | Installed processor units. |
| Current available memory units \[curr_avail_sys_mem\] | Current available memory units. |
| Configurable memory units \[configurable_sys_mem\] | Configurable memory units. |
| Installed memory units \[installed_sys_mem\] | Installed memory units. |
| IP Address \[ip_address\] | Management IP address of the IBM frame. |
[Table 2. IBM Frame \[cmdb_ci_ibm_frame\]]

{#ibm-hmc-discovery__table_vx2_rgk_pdc}  
{#ibm-hmc-discovery__table_u15_f1l_43b__entry__2}

| Field | Description |
|-|-|
| Name \[name\] | Name of the LPAR instance. |
| State \[state\] | Operational state. Possible values are On or Off. * On: running * Off: not activated or not available {#ibm-hmc-discovery__ul_pb2_jjl_43b} |
| Serial number \[serial_number\] | Serial number of the LPAR. |
| Object ID \[object_id\] | Unique object identifier. This identifier is concatenated from the frame serial number and the LPAR identifier. |
| Is VIO \[is_vio\] | Identifies the LPAR as a VIO server. A VIO server is the LPAR that manages the physical components for other LPARs, such as network interface cards (NICs) and optical drives. |
| VIO Servers \[vio_servers\] | * Client LPARs: Identifies the VIO servers that manage the client LPARs. * VIO servers: Identifies the Client LPARs the VIO servers manage. {#ibm-hmc-discovery__ul_jls_skl_43b} |
| Current Min Proc Units \[curr_min_proc_units\] | Minimum number of processing units that can be assigned to the partition dynamically. |
| Running Proc Units \[run_proc_units\] | Number of processing units that are varied on for the partition. |
| Current Memory \[curr_mem\] | The amount of memory in megabyte (MB) assigned to the partition. |
| Running Memory \[run_mem\] | Current amount of memory in MB that the partition has varied on. |
| IP Address \[ip_address\] | IP address assigned to the VIOS LPAR instance. |
| Model number \[model_number\] | OS version of the VIOS LPAR instance. |
| Frame Name \[frame_parent\] | References the IBM Frame \[cmdb_ci_ibm_frame\] table. |
[Table 3. IBM LPAR Instance \[cmdb_ci_lpar_instance\]]

{#ibm-hmc-discovery__table_u15_f1l_43b}  
{#ibm-hmc-discovery__table_pzf_rgk_pdc__entry__2}

| Field | Description |
|-|-|
| High Watermark VCPU \[high_watermark_vcpu\] | Highest recorded value of the Online Virtual CPUs field, as collected by the `lparstat-i` command. Because the value is dynamic, the results of a discovery could affect the value: * If the value of the Online Virtual CPUs field is lower than the value collected by the `lparstat-i` command, the value doesn't change. * If the value of the Online Virtual CPUs field is higher than the value collected by the `lparstat-i` command, the higher value is used. {#ibm-hmc-discovery__ul_dn1_3pl_43b} |
| Node name \[node_name\] | Name of the instance, along with the field that refers to the LPAR instance CI. |
[Table 4. LPAR Resource \[cmdb_ci_lpar_resource\]]

{#ibm-hmc-discovery__table_pzf_rgk_pdc}  
{#ibm-hmc-discovery__table_kzg_rgk_pdc__entry__2}

| Field | Description |
|-|-|
| Serial number \[serial_number\] | Serial number of the CI. |
[Table 5. Serial Number \[cmdb_serial_number\]]

{#ibm-hmc-discovery__table_kzg_rgk_pdc}

## CI Relationships {#ibm-hmc-discovery__section_dmq_yfk_pdc}

Discovery creates these relationships to support the IBM Virtualization and HMC discovery.  
{#ibm-hmc-discovery__table_av2_dgk_pdc__entry__3}

| CI | Relationship | CI |
|-|-|-|
| IBM HMC Server \[cmdb_ci_hmc_server\] | Defines resources for::Gets resources from | IBM HMC Processor Pool \[cmdb_ci_processor_pool\] |
| IBM LPAR Instance \[cmdb_ci_lpar_instance\] | Virtualized by::Virtualizes | IBM Frame \[cmdb_ci_ibm_frame\] |
| IBM Frame \[cmdb_ci_ibm_frame\] | Managed by::Manages | IBM HMC Server \[cmdb_ci_hmc_server\] |
| IBM HMC Processor Pool \[cmdb_ci_processor_pool\] | Members::Member of | IBM LPAR Instance \[cmdb_ci_lpar_instance\] |
| IBM LPAR Instance \[cmdb_ci_lpar_instance\] | References | IBM Frame \[cmdb_ci_ibm_frame\] |
[ ]

{#ibm-hmc-discovery__table_av2_dgk_pdc}