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


---

# OCI virtual machine

# OCI virtual machine pattern-based discovery {#ariaid-title1}

Release version: Australia  
Updated September 10, 2026  
![](https://www.servicenow.com/docs/portal-asset/ico-clock) 3 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 OCI virtual machine pattern-based discovery

The OCI virtual machine pattern-based discovery enables ServiceNow customers to identify and populate Oracle Cloud Infrastructure (OCI) virtual machine (VM) instances into the Configuration Management Database (CMDB).
This discovery process requires the latest Discovery and Service Mapping Patterns application and appropriate REST API permissions.
Show full answer Show less  

## Key Features

* **REST API Permissions:** Customers must verify and grant necessary REST API permissions using a downloadable Cloud Discovery patterns spreadsheet, which also details pattern names, types, CI classes, and vendor documentation links.
* **OCI Prerequisites:** Customers should ensure all OCI discovery prerequisites are met, including special configuration for GovCloud accounts that require using a datacenter URL in the OCI service account setup.
* **Data Collection:** The discovery populates critical VM instance data in the *cmdbcivminstance* table, capturing fields such as VM name, unique Oracle object ID, CPU count, memory size, private IP address, VM state, install status, and operational status.
* **Image Data:** OS images are stored in either the *cmdbciostemplate* or the preferred *cmdbcicloudosimage* table to effectively manage large numbers of records and avoid duplication.
* **CI Relationships and References:** The pattern creates comprehensive relationships between VMs, OCI datacenters, availability zones, images, servers, and endpoints to build a detailed and accurate discovery map.
* **OCI Tag Discovery:** Tags from OCI are collected and stored in the *cmdbkeyvalue* table, associating tag names and values directly with VM instances.
* **BYOL License Discovery:** Starting with version 1.35.1 of the patterns, Windows VM licenses are discovered and classified as either Bring Your Own License (BYOL) or License Included, with this information stored in the *cmdbkeyvalue* table.

## Key Outcomes

* Automated and accurate population of OCI VM instances and related configuration items into the CMDB.
* Detailed VM hardware and software attributes captured, supporting configuration management and asset tracking.
* Robust relationship mapping between VMs and their underlying infrastructure components enhances visibility and impact analysis.
* Tag and license information integrated into the CMDB supports governance, compliance, and license management.
* Support for OCI GovCloud environments and license type discovery ensures comprehensive coverage in diverse OCI deployments.  
Discovery and Service Mapping Patterns finds OCI virtual machines (VMs) in your cloud environment. Discovering some of these resources might require updating to the latest version of the Discovery and Service Mapping Patterns application from the ServiceNow Store.

## Pattern-based discovery and mapping requirements {#oracle-vm-pattern__section_rpj_fj2_bgc}

Verify the REST API permissions
:   Download the [Cloud Discovery patterns spreadsheet](https://downloads.docs.servicenow.com/resource/enus/api/servicenow-discovery-patterns-api-details.xlsx) so you can grant user permissions required for running the Discovery patterns. In addition to permissions, the spreadsheet also includes useful information such as pattern names, types, CI Classes, and links to vendor documentation. New patterns are available quarterly, so check periodically to be sure you have the latest version of the spreadsheet.{#oracle-vm-pattern__cloud-discovery-api-ph-short-prereq}

Verify the OCI discovery prerequisites
:   For more information, see the prerequisites section in [Oracle Cloud Infrastructure (OCI) discovery](https://www.servicenow.com/docs/cQhDQlR5AKA0e3vdDdSSGg "ServiceNow Discovery uses the Oracle Cloud Infrastructure (OCI) discovery patterns to provide real-time elasticity for enterprise applications by combining Oracle autonomous services, integrated security, and cloud compute. Discovering some of these resources might require updating to the latest version of the Discovery and Service Mapping Patterns application from the ServiceNow Store.").

Configure the Discovery schedule to support GovCloud
:   Discovering OCI GovCloud accounts requires using a datacenter URL when setting up an OCI service account. For more information, see [Create OCI service accounts](https://www.servicenow.com/docs/Mfvl~mYZP9TwzjqAPuihqA "Create Oracle Cloud Infrastructure (OCI) service accounts on the ServiceNow AI Platform to access your Oracle account during Oracle discovery.").

## Data collected by Discovery during horizontal discovery {#oracle-vm-pattern__section_ggp_ql2_bgc}

Discovery populates the data in the CMDB when running the Oracle OCI - Virtual Machine (LP) pattern.  
{#oracle-vm-pattern__table_vm_instance__entry__2}

| Field | Description |
|-|-|
| Name \[name\] | The display name of the VM instance. |
| Object ID \[object_id\] | A unique identifier, allocated by Oracle OCI for this resource. |
| CPUs \[cpus\] | The number of Oracle CPU (OCPUs) available to the instance. |
| Memory (MB) \[memory\] | The amount of memory available to the instance, in gigabytes. |
| IP Address \[ip_address\] | The private IP address of the primary network interface attached to the instance. |
| State \[state\] | The current state of the virtual machine instance. For example: on, off, starting, stopping, scheduled, terminated, or error. |
| Install Status \[install_status\] | Install status of the resource. Default value is Installed. |
| Operational status \[operational_status\] | Operational status of the resource. Default value is Operational. |
[Table 1. Virtual Machine Instance \[cmdb_ci_vm_instance\]]

{#oracle-vm-pattern__table_vm_instance}  
{#oracle-vm-pattern__table_os_template__entry__2}

| Field | Description |
|-|-|
| Object ID \[object_id\] | A unique identifier, allocated by Oracle OCI for this image. |
| Provider \[provider\] | The cloud provider, which is OCI. This field is only populated in the Cloud Image \[cmdb_ci_cloud_os_image\] table. |
[Table 2. Image \[cmdb_ci_os_template\] or Cloud Image \[cmdb_ci_cloud_os_image\]]

{#oracle-vm-pattern__table_os_template}  
Note:  
When using the Image \[cmdb_ci_os_template\] table to store Cloud OS images, you may notice an unusually large number of records. To avoid this issue, you can store the discovered OS images in the Cloud Image \[cmdb_ci_cloud_os_image\] table. For more information, see [Enable Cloud OS Image discovery](https://www.servicenow.com/docs/AM9L2gpoJH8rga6KPXl_5g "Enable the Cloud OS Image [cmdb_ci_cloud_os_image] table to store the cloud OS image records for Amazon AWS Cloud, Microsoft Azure Cloud, Google Cloud Platform (GCP), Oracle Cloud Infrastructure (OCI), and IBM Cloud.").

## CI relationships and references {#oracle-vm-pattern__section_dc4_ghc_dgc}

The Oracle OCI - Virtual Machine (LP) pattern creates the following relationships and references to support OCI VM discovery. References link to records in other tables and don't appear in the CI Relationship \[cmdb_rel_ci\] table.  
{#oracle-vm-pattern__table_bkg_jhc_dgc__entry__3}

| CI | Relationship | CI |
|-|-|-|
| Virtual Machine Instance \[cmdb_ci_vm_instance\] | Hosted on::Hosts | OCI Datacenter \[cmdb_ci_oci_datacenter\] |
| Availability Zone \[cmdb_ci_availability_zone\] | Contains::Contained by | Virtual Machine Instance \[cmdb_ci_vm_instance\] |
| Virtual Machine Instance \[cmdb_ci_vm_instance\] | DR provided by::Provides DR for | Availability Zone \[cmdb_ci_availability_zone\] |
| Virtual Machine Instance \[cmdb_ci_vm_instance\] | Provisioned From::Provisioned | Image \[cmdb_ci_os_template\] or Cloud Image \[cmdb_ci_cloud_os_image\] |
| Image \[cmdb_ci_os_template\] or Cloud Image \[cmdb_ci_cloud_os_image\] | Hosted on::Hosts | OCI Datacenter \[cmdb_ci_oci_datacenter\] |
| Server \[cmdb_ci_server\] | Virtualized by::Virtualizes | Virtual Machine Instance \[cmdb_ci_vm_instance\] |
| Virtual Machine Instance \[cmdb_ci_vm_instance\] | Use End Point To::Use End Point From | VNIC Endpoint \[cmdb_ci_endpoint_vnic\] |
| VNIC Endpoint \[cmdb_ci_endpoint_vnic\] | Implement End Point To::Implement End Point From | Cloud Mgmt Network Interface \[cmdb_ci_nic\] |
| Virtual Machine Instance \[cmdb_ci_vm_instance\] | Provisioned From::Provisioned | Cloud Hardware Type \[cmdb_ci_cloud_hardware_type\] |
[Table 3. CI relationships]

{#oracle-vm-pattern__table_bkg_jhc_dgc}  
{#oracle-vm-pattern__table_ci_references__entry__3}

| CI | Field | Referenced CI |
|-|-|-|
| Key Value \[cmdb_key_value\] | Configuration item \[configuration_item\] | Virtual Machine Instance \[cmdb_ci_vm_instance\] |
[Table 4. CI references]

{#oracle-vm-pattern__table_ci_references}

## OCI tag discovery {#oracle-vm-pattern__section_lyw_zhc_dgc}

The Oracle OCI - Virtual Machine (LP) pattern collects tags and populates them in the Key Value \[cmdb_key_value\] table.  
{#oracle-vm-pattern__table_ojy_vss_5hc__entry__2}

| Field | Description |
|-|-|
| Key \[key\] | Tag name. |
| Value \[value\] | Tag value. |
| Configuration item \[configuration_item\] | References the Virtual Machine Instance \[cmdb_ci_vm_instance\] table. |
[Table 5. Key Value \[cmdb_key_value\]]

{#oracle-vm-pattern__table_ojy_vss_5hc}

## OCI BYOL discovery {#oracle-vm-pattern__section_hgz_w3n_zjc}

Starting with Discovery and Service Mapping Patterns version 1.35.1, the pattern extension section discovers the following license types for Windows VMs:

* Bring Your Own License (BYOL)
* License included
{#oracle-vm-pattern__ul_pd1_1jn_zjc}The pattern stores the license type and model in the Key Value \[cmdb_key_value\] table.  
{#oracle-vm-pattern__table_p3y_djn_zjc__entry__2}

| Field | Description |
|-|-|
| Key \[key\] | The license type key, which is Windows_OS_License_Type_automatic. |
| Value \[value\] | The license model, which is one of the following: * BYOL * License Included {#oracle-vm-pattern__ul_wx1_hjn_zjc} |
| Configuration item \[configuration_item\] | References the Virtual Machine Instance \[cmdb_ci_vm_instance\] table. |
[Table 6. Key Value \[cmdb_key_value\]]

{#oracle-vm-pattern__table_p3y_djn_zjc}