Oracle Cloud Infrastructure Documentation

Discovering Managed Instances

Identifythe managed instances to migrate to OS Management Hub and resolve any incompatibility issues before migration.

Tip

For simplicity and efficiency, we recommend that you use the migration assistant tool to perform this task. For more information, see Installing the Migration Assistant.

Using the Migration Assistant

Use the osms-to-osmh discover managed-instance command and required parameters to examine managed instances in a compartment or tenancy that need to be migrated to OS Management Hub.

For example, to discover all managed instances you have in OS Management:

osms-to-osmh discover managed-instance

The output for the command displays the following information about managed instances in a compartment or tenancy:

  • The OCID assigned to the managed instance.
  • The name of the managed instance.
  • The OS vendor, version, and architecture.
  • The number of scheduled jobs assigned to the managed instance.
  • The name of the group that it's a member of (if applicable).
  • Whether the instance is an Autonomous Linux instance.
  • Whether the instance has been migrated to OS Management Hub.

The following is sample output:

$ osms-to-osmh discover managed-instance 
Discovering instances ......

OCID                             Name                 Vendor     Version              Arch    Jobs  Compartment  Groups            ALX  Compatible  Migrated                                                                                                                                                                          
-------------------------------  -------------------  ---------  -------------------  ------  ----  -----------  ----------------  ---  ----------  --------  
ocid1.instance.oc1..<unique_ID>  osms-ol8-standalone  ORACLE     Oracle Linux 8       x86_64  0     idg          -                 No   Yes         No      
ocid1.instance.oc1..<unique_ID>  osms1-ol8            ORACLE     Oracle Linux 8       x86_64  1     idg          osms-linux-group  No   Yes         No      
ocid1.instance.oc1..<unique_ID>  osms2-ol8            ORACLE     Oracle Linux 8       x86_64  2     idg          osms-linux-group  No   Yes         No      
ocid1.instance.oc1..<unique_ID>  osms3-ol9            ORACLE     Oracle Linux 9       x86_64  1     idg          osms-linux-group  No   Yes         No      
ocid1.instance.oc1..<unique_ID>  osms4-ol9            ORACLE     Oracle Linux 9       x86_64  1     idg          osms-linux-group  No   Yes         No      
ocid1.instance.oc1..<unique_ID>  windows1-2022        MICROSOFT  Windows Server 2022  X86_64  1     idg          windows           No   Yes         No      
ocid1.instance.oc1..<unique_ID>  windows2-2022        MICROSOFT  Windows Server 2022  X86_64  1     idg          windows           No   Yes         No      
ocid1.instance.oc1..<unique_ID>  windows3-2019        MICROSOFT  Windows Server 2019  X86_64  1     idg          windows           No   Yes         No      
ocid1.instance.oc1..<unique_ID>  windows4-2019        MICROSOFT  Windows Server 2019  X86_64  3     idg          windows           No   Yes         No

Use the --verbose option if the migration assistant reports incompatible resources. For more information, see Resolving Incompatible Managed Instances.

Usage

osms-to-osmh discover managed-instance [-c | --compartment name] [-v | --verbose] [--managed-instance-id ocid] [--migrated] [--notmigrated] [--export-json] [ --help]

Option Details

Parameter Description
-c | --compartment name

Displays information about managed instances in the specified compartment. For name, specify either the name of the compartment or the OCID assigned to the compartment.

If no compartment is specified, managed instances from all compartments are displayed.
-v | --verbose Displays details about incompatible custom software sources.
--managed-instance-id ocid Displays information about the specified managed instance. For ocid, specify the OCID assigned to the managed instance.
--migrated Displays managed instances that have been created in OS Management Hub.
--notmigrated Displays managed instances that haven't been created in OS Management Hub.
--export-json Exports results to a JSON file.
--help Displays help information about the migration assistant command, such as the available options and the supported values for each option.

Using the Console

Important

Determining what instances are actively using OS Management requires multiple steps using the Console. We recommend that you use the migration assistant to simplify this task.
  1. Open the navigation menu, click Compute, and then click Instances.
  2. Find the instance and click its name.
  3. On the Instance Details page, click Oracle Cloud Agent.
  4. Verify that OS Management Service Agent plugin is enabled. For more information, see the Oracle Cloud Agent documentation.
  5. On the Instance Details page, under Resources, click OS Management.

    • If the instance is being actively managed by OS Management, the Overview tab displays "Use the OS Management service to manage updates and patches on compute instances."

    • If the instance isn't showing OS Management information, it's either not managed by OS Management or isn't communicating with the service. See OS Management Service Shows Unavailable on an Instance for more information.

  6. Review the list of scheduled jobs for the OS Management managed instance.
    1. Click the Actions icon (three dots) and click View OS Management Details.
    2. Under Resources, click Scheduled Jobs.
    3. In the Scheduled Jobs section, review and record the scheduled jobs for the managed instance.
Note

Repeat the previous steps for every managed instance in the compartment that you plan to migrate. If you are managing instances that reside in other compartments, repeat these steps on the instances in those compartments in the tenancy.