Oracle Exalogic Elastic Cloud Software
 
Oracle Exalogic Elastic Cloud X2-2 Hardware
 
Exalogic Elastic Cloud X3-2 Hardware
 

PLA-Support>Eng Systems>Exalogic/OVCA>Oracle Exalogic>MW: Exalogic Core
 

Exalogic Control services running on Exalogic X2-2 and X3-2 systems in a virtualized configuration (not physical), meeting the following prerequisite:

The Exalogic Infrastructure was upgraded from version 2.0.4.0.x to 2.0.6.0.0 using the 2.0.6.0.0 Upgrade Kit (not applicable to fresh install of 2.0.6.0.0).

In this Document

Purpose

Details

Applies to:

Purpose

This document provides instructions to download tooling and associated step-by-step procedure to add missing vServer tag to Exalogic Control vServers.

The procedure provided in this document is to fix a known issue where EM Agent can not discover Control Stack vServers after upgrade to 2.0.6.0.0.

Details

The procedure described in this document resolves issues with the EM Ops Center (EMOC) components of the Exalogic Control stack.

1. The following items attached to this note are required to perform this procedure:
   
   
   1. A tarball, opt_exalogic_elcontrol.tgz, containing scripts and a jar file
   2. A python script, print_assets.py, for verification of the fix.
      
      
2. Obtain the rack system identifier
   

   log into the first compute node and run: 
   

   ipmitool sunoem cli 'show /SP system_identifier'

   The output will be similar to the following:  
   

   Connected. Use ^D to exit.
   -> show /SP system_identifier
   
   /SP
   Properties:
   system_identifier = Oracle Exalogic X2-2 AK00012345
   
   -> Session closed
   Disconnected

   
   The rack system identifier follows the "Oracle Exalogic <compute node type>".

3. Set up the VM Tags
   
   
   1. Log into the ExalogicControlOVMM vServer as root. This is the vServer running both Ops Center and the OVMM.
      
      
   2. Download and open the attached opt_exalogic_elcontrol.tgz file as follows:  
      
      # tar -xzv -f opt_exalogic_elcontrol.tgz -C /
   3. Create an environment variable, PASSWORD, with the OVM "admin" user password as follows (replace welcome1 with the actual password)  
      
      # export PASSWORD=welcome1
   4. Create an environment variable, RACKID, with the rack system identifier as follows (replace AK00012345 with the rack identifier from step 1 above)  
      
      # export RACKID=AK00012345
   5. Set the tags by running each of the following commands:
      

        

      # /u01/app/oracle/java/bin/java -classpath /opt/exalogic/elcontrol/emoc/vmTags.jar:/u01/app/oracle/ovm-manager-3/ovm_shell/lib/OvmClient.jar:/u01/app/oracle/ovm-manager-3/ovm_shell/lib/commons-logging.jar setvmtags.SetVMTags --ovmmurl=tcp://localhost --username=admin --password=${PASSWORD} --cmd=set --vmname=ExalogicControlOVMM --type.0=ENTERPRISE_CONTROLLER --version.0=12.1.0.0.0 --description.0="Ops Center Enterprise Controller" --softwarename.0="Enterprise Controller"
      
      # /u01/app/oracle/java/bin/java -classpath /opt/exalogic/elcontrol/emoc/vmTags.jar:/u01/app/oracle/ovm-manager-3/ovm_shell/lib/OvmClient.jar:/u01/app/oracle/ovm-manager-3/ovm_shell/lib/commons-logging.jar setvmtags.SetVMTags --ovmmurl=tcp://localhost --username=admin --password=${PASSWORD} --cmd=set --vmname=ExalogicControlOpsCenterPC1 --type.2=PROXY_CONTROLLER --version.2=12.1.0.0.0 --description.2="Ops Center Proxy Controller" --softwarename.2="Proxy Controller"
      
      # /u01/app/oracle/java/bin/java -classpath /opt/exalogic/elcontrol/emoc/vmTags.jar:/u01/app/oracle/ovm-manager-3/ovm_shell/lib/OvmClient.jar:/u01/app/oracle/ovm-manager-3/ovm_shell/lib/commons-logging.jar setvmtags.SetVMTags --ovmmurl=tcp://localhost --username=admin --password=${PASSWORD} --cmd=set --vmname=ExalogicControlOpsCenterPC2 --type.2=PROXY_CONTROLLER --version.2=12.1.0.0.0 --description.2="Ops Center Proxy Controller" --softwarename.2="Proxy Controller"
      
      # sh /u01/app/oracle/ovm-manager-3/ovm_shell/ovm_shell.sh --url=tcp://localhost --username=admin --password=${PASSWORD} --inputfile=/opt/exalogic/elcontrol/jy/TagExalogicID.py exalogic_id=${RACKID}

        
      

      Ensure that the output from the above commands does not include a message with text: 
      

      Error while setting the VM tags

        

   6. Verify that the tagging worked by changing to the directory containing the attached print_assets.py script and running ovm_shell.sh as follows: 
      

      # sh /u01/app/oracle/ovm-manager-3/ovm_shell/ovm_shell.sh --username=admin --password=${PASSWORD} --inputfile=`pwd`/print_assets.py

        

      Sample output from the command follows: 
      

      --------------------------------
      Printing distributed assets for Control VM : ExalogicControlOpsCenterPC2
      Distributed Assets Object ' {oc.internal.ovmm.resource.tags.description.2=Ops Center Proxy Controller, oc.internal.ovmm.resource.tags.softwarename.2=Proxy Controller, oc.internal.ovmm.resource.tags.url.2=null, oc.internal.ovmm.resource.tags.type.2=PROXY_CONTROLLER, oc.internal.ovmm.resource.tags.version.2=12.1.0.0.0} '
      KEY=' oc.internal.ovmm.resource.tags.description.2 ' VALUE=' Ops Center Proxy Controller '
      KEY=' oc.internal.ovmm.resource.tags.softwarename.2 ' VALUE=' Proxy Controller '
      KEY=' oc.internal.ovmm.resource.tags.url.2 ' VALUE=' None '
      KEY=' oc.internal.ovmm.resource.tags.type.2 ' VALUE=' PROXY_CONTROLLER '
      KEY=' oc.internal.ovmm.resource.tags.version.2 ' VALUE=' 12.1.0.0.0 '
      --------------------------------
      --------------------------------
      Printing distributed assets for Control VM : ExalogicControlOVMM
      Distributed Assets Object ' {oc.internal.ovmm.resource.tags.softwarename.0=Enterprise Controller, oc.internal.ovmm.resource.tags.description.0=Ops Center Enterprise Controller, oc.internal.ovmm.resource.tags.url.0=null, oc.internal.ovmm.resource.tags.type.0=ENTERPRISE_CONTROLLER, oc.internal.ovmm.resource.tags.version.0=12.1.0.0.0} '
      KEY=' oc.internal.ovmm.resource.tags.softwarename.0 ' VALUE=' Enterprise Controller '
      KEY=' oc.internal.ovmm.resource.tags.description.0 ' VALUE=' Ops Center Enterprise Controller '
      KEY=' oc.internal.ovmm.resource.tags.url.0 ' VALUE=' None '
      KEY=' oc.internal.ovmm.resource.tags.type.0 ' VALUE=' ENTERPRISE_CONTROLLER '
      KEY=' oc.internal.ovmm.resource.tags.version.0 ' VALUE=' 12.1.0.0.0 '
      --------------------------------
      --------------------------------
      Printing distributed assets for Control VM : ExalogicControlOpsCenterPC1
      Distributed Assets Object ' {oc.internal.ovmm.resource.tags.description.2=Ops Center Proxy Controller, oc.internal.ovmm.resource.tags.softwarename.2=Proxy Controller, oc.internal.ovmm.resource.tags.url.2=null, oc.internal.ovmm.resource.tags.type.2=PROXY_CONTROLLER, oc.internal.ovmm.resource.tags.version.2=12.1.0.0.0} '
      KEY=' oc.internal.ovmm.resource.tags.description.2 ' VALUE=' Ops Center Proxy Controller '
      KEY=' oc.internal.ovmm.resource.tags.softwarename.2 ' VALUE=' Proxy Controller '
      KEY=' oc.internal.ovmm.resource.tags.url.2 ' VALUE=' None '
      KEY=' oc.internal.ovmm.resource.tags.type.2 ' VALUE=' PROXY_CONTROLLER '
      KEY=' oc.internal.ovmm.resource.tags.version.2 ' VALUE=' 12.1.0.0.0 '
      --------------------------------

        

   7. Clean up references to the password in the bash history by running: 
      

      # unset PASSWORD
      # unset RACKID
      # history -c

        
      

This solution has no attachment