Oracle^® MiniCluster S7-2 Administration Guide

List Details of a DB VM Group Profile (CLI)

Use this procedure to list details about a DB VM group profile.

1. Log into the MCMU CLI as a primary admin, such as mcinstall.

   See Log in to the MCMU CLI.

2. Use this syntax:

   % mcmu tenant -P -L VMgroupID

   where VMgroupID is the ID of the DB VM group profile. To determine the VMgroupID, see List a Summary of a DB VM Group Profile (CLI).

   For example, to get details on a DB VM group profile with an ID of 1, type:

   % mcmu tenant -P -L 1
   Getting DB VM Group Profile...
   
   GRID DEFINITION
           Status : Active
           inventoryLocation : /u01/app/oraInventory
           gridLocation : /u01/app/12.1.0.2/grid
           redoDiskGroup : HIGH
           dataDiskGroup : NORMAL
           recoDiskGroup : NORMAL
           SCAN_name : dbgp1-scan
           SCAN_ip : 192.0.2.4,192.0.2.5,192.0.2.6
   
   STORAGE DEFINITION
           redundancy : NORMAL
           numberOfDisks : None
           storageArrays :
   
   DB VM GROUP DEFINITION
           status : Active
           VMGroupDesc : Initial DB VM Group
    - NORMAL redundancy
    - Shared Storage
    - CIS
           VMGroupType : database
           VMGroupName : dbgrp1
           operationType : DBZoneGroup_MapIP
           VMGroupID : 1
           globalName : mc3-n1,mc3-n2
           compliance benchmark : No
           shared storage : Yes
   
   DB VM DEFINITIONS
   
   VM 1
           status : Active
           id : 1
           name : dbgp1-vm1-mc3-n1
           globalName : mc3-n1
           cores : 0
           DNSServers : 192.0.2.7,192.0.2.8
           memory : 522496
           virtualNetworks
                   private_ip : 192.0.2.10
                   private_hostname : mc3-n1vm1-z1-priv
                   private_mask : 24
                   public_ip : 192.0.2.11
                   public_hostname : mc3-n1vm1-z1
                   public_mask : 20
                   public_gateway : 192.0.2.1
                   virtual_ip : 192.0.2.13
                   virtual_hostname : mc3-n1vm1-z1-vip
   
   VM 2
           status : Active
           id : 2
           name : dbgp1-vm1-mc3-n2
           globalName : mc3-n2
           cores : 3
           DNSServers : 192.0.2.7,192.0.2.8
           memory : 522496
           virtualNetworks
                   private_ip :192.0.2.14
                   private_hostname : mc3-n2vm1-z1-priv
                   private_mask : 24
                   public_ip : 192.0.2.15
                   public_hostname : mc3-n2vm1-z1
                   public_mask : 20
                   public_gateway : 192.0.2.1
                   virtual_ip : 192.0.2.15
                   virtual_hostname : mc3-n2vm1-z1-vip
   
   VM 3
           status : Active
           id : 3
           name : dbgp1-vm2-mc3-n1
           globalName : mc3-n1
           cores : 0
           DNSServers : 192.0.2.7,192.0.2.8
           memory : 522496
           virtualNetworks
                   private_ip : 192.0.2.16
                   private_hostname : mc3-n1vm1-z2-priv
                   private_mask : 24
                   public_ip : xx.xxx.xxx..198
                   public_hostname : mc3-n1vm1-z2
                   public_mask : 20
                   public_gateway :  192.0.2.1
                   virtual_ip : 192.0.2.17
                   virtual_hostname : mc3-n1vm1-z2-vip
   
   VM 4
           status : Active
           id : 4
           name : dbgp1-vm2-mc3-n2
           globalName : mc3-n2
           cores : 2
           DNSServers : 192.0.2.7,192.0.2.8
           memory : 522496
           virtualNetworks
                   private_ip : 192.0.2.18
                   private_hostname : mc3-n2vm1-z2-priv
                   private_mask : 24
                   public_ip : 192.0.2.19
                   public_hostname : mc3-n2vm1-z2
                   public_mask : 20
                   public_gateway :  192.0.2.1
                   virtual_ip : 192.0.2.20
                   virtual_hostname : mc3-n2vm1-z2-vip