X

News, tips, partners, and perspectives for Oracle’s virtualization offerings

  • December 15, 2017

Friday Spotlight: Upgrade to Oracle Private Cloud Appliance 2.3.2 from 2.3.1 with Oracle Enterprise Manager 13.2

Simon Hayler
Senior Technical Product Manager

Recently we announced the Oracle Private Cloud Appliance (PCA) software 2.3.2 release which adds support for the X7-2 compute nodes.

The high level steps for the PCA 2.3.1 to 2.3.2 upgrade with Oracle Enterprise Manager 13c are as follows. If your PCA is not 2.3.1 then refer to My Oracle Support note 2242177.1 which includes steps for Oracle Enterprise Manager.

- Update the required Enterprise Manager Plug-ins
- If needed, install patches on the Enterprise Manager 13.2 Server (OMS) and agents
- Backup the oraInventory
- Move the PCA to a blackout state
- Upgrade PCA to 2.3.2
- Recover the PCA management node agent 
- Remove the blackout state 

Step 1: Update the required Enterprise Manager Plug-ins:
The Systems Infrastructure (SI) plug-in has been updated to support the Oracle X7 servers. This plugin needs to be updated to the latest version which currently is 13.2.3. The following plug-ins should also be at the latest version: Virtualization (VT), Cloud Framework (CFW) and Oracle Cloud Application (SSA).
To check the current versions go to Setup > Extensibility > Plugins

 

Expose the Server folder and look firstly for the SI plugin:

The Blue icon tells us there is a later version of the plugin available. To download this latest version follow the documentation which is here. Check the versions of the VT, CFW and SSA plug-in and if required update to the latest version. With the SI plug-in upgrade down time is required for the Oracle Enterprise Manager server (OMS) and the agent on the PCA.

Step 2: If needed, install patches on the Oracle Enterprise Manger 13.2 Server (OMS) and PCA management node agent:

Enterprise Manager has the concept of PSU’s (Patch Set Update), plugin patches and agent patches. From My Oracle Support (MOS) use the following document to determine the version of your Enterprise Manager environment: Doc ID 2319892.1 EM 13c: How to Determine the Patch Set Update (PSU) Applied to the Enterprise Manager 13c Cloud Control OMS and the Bundle Patch applied to Plug-ins and Agent. This document also refers to a master document: Master Note for Enterprise Manager Proactive Patch Program Doc ID 822485.1 which has links to documents for the latest PSU (Patch Set Update), agent and plugin patches.
Oracle recommend that the Oracle Enterprise Manager Server (OMS) and Agents are at the latest PSU, plugin and agent patches. For the agent patches it is recommended to deploy any bundle, plugin, discovery and monitoring patches.
In January 2018 a PSU was released (13.2.0.0.180116 Enterprise Manager Base Platform Patch Set Update (PSU)) contained in patch 27116243. This patch should be deployed on the Enterprise Manager Server (OMS) using the latest version of omspatcher including the following version of opatch:  Patch 6880880: OPatch version 13.9.2.1.1 for EMCC 13.x customers Only (not for FMW 12c). Use the various patch readme files for further information.

In summary, using the January 2018 PSU for the Oracle Enterprise Manager Server (OMS) the following patches are required:
- 27116243 – January 2018 PSU
- 6880880 -  OPatch version 13.9.2.1.1 for the OMS and Management Agent on the OMS
- 27336172 – January 2018 plugin bundle patch
- 27319514  - January 2018 agent bundle patch for the agent running on the OMS

In summary using the January 2018 PSU for the PCA Management Agent the following patches are required:
- 6880880 -  OPatch version 13.9.2.1.1
- 27319514  - January 2018 agent bundle patch
- 27359568  - January 2018 VT Plugin Monitoring patch
- 27110236 -  November 2017 VT Plugin Discovery patch

Step 3: Backup the Oracle inventory:

The first step is to take a backup of the PCA management node agent
oraInventory. The Oracle Inventory directory (oraInventory) stores an inventory of all
software installed on the system. It is required and shared by all Oracle software installations on a single system.

Firstly, as the root user ssh into the active management VIP (Virtual IP
Address) and confirm we are on the active management node:
[root@ovcamn06r1
~]# pca-check-master
NODE:
192.168.4.4 MASTER: True

Backup the oraInventory and copy to the shared NFS storage:
[root@ovcamn06r1~]# cd /u01/app
[root@ovcamn06r1 app]# tar -cvf EMagent_oraInventory.tar oraInventory
[root@ovcamn06r1 app]# cp EMagent_oraInventory.tar /nfs/shared_storage/

Step 4: Move the PCA to a blackout state:

We should place the PCA into a blackout state within Oracle Enterprise Manger 13c. Blackouts allow Oracle Enterprise Manager administrators to suspend all data collection activity on one or more monitored targets. The primary reason for blacking out targets is to allow Oracle Enterprise Manager administrators to perform scheduled maintenance on those targets. Alerts may also being sent to other management tools external to Oracle Enterprise Manager therefore this procedure is vital in false alerts being sent.

Using the Enterprise Manager 13c UI as the Cloud Administrator go to the Private Cloud Appliance Home Page.
Oracle Enterprise Manager 13c is able to manage multiple Oracle Private Cloud Appliances, therefore if this is the case click on the Oracle Private Cloud Appliance to update.

From the Oracle Private Cloud Appliance home page menu select the Create Blackout option:

Enter suitable information describing the reason for the blackout (see below example) It is suggested to tick Enable Full blackout for all hosts and agents. Also on the Schedule set the duration to Indefinitely. Notice that there is a single target of type Oracle Private Cloud Appliance and also in the Related Targets Included in the Blackout. This single target of the Oracle Private Cloud Appliance will encapsulate all the physical and logical / virtual components.The Home Page will return with a notification that the Oracle Private Cloud Appliance is now under Blackout.

Similarly as with the physical targets the single target of the Oracle VM Manager will encapsulate all the logical targets it manages into a single blackout. This is shown with a wrench / screwdriver icon as follows within the Infrastructure Cloud View:

Step 5: Upgrade PCA to 2.3.2 by referring to the documentation.

Step 6: Recover the PCA management node agent:

The next step is to recover the Oracle Enterprise Manager agent installed on the NFS shared storage which is presented to both active and passive management nodes.

We firstly restore the oraInventory backup we took in the first step as the root user on the active management node:
[root@ovcamn06r1 ~]# pca-check-master
NODE: 192.168.4.4  MASTER: True

[root@ovcamn06r1 ~]# cp /nfs/shared_storage/EMagent_oraInventory.tar /u01/app
[root@ovcamn06r1 ~]# cd /u01/app
[root@ovcamn06r1 app]# ls
EMagent_oraInventory.tar  oracle
[root@ovcamn06r1 app]# tar -xvf Emagent_oraInventory.tar

We then need to change the oracle passwd to the same one we used on the original Oracle Enterprise Manager agent install as the root user on both management nodes active and passive:
[root@ovcamn06r1 ~]# passwd oracle
[root@ovcamn05r1 ~]# passwd oracle

Next on the active management node and as the root user we need to run the privilege scripts:
[root@ovcamn06r1 ~]# /nfs/shared_storage/oem13agent/agent_13.2.0.0.0/root.sh
[root@ovcamn06r1 ~]# /u01/app/oraInventory/orainstRoot.sh

These scripts create the /etc/oragchomelist /etc/oraInst.loc & /etc/init.d/gcstartup scripts.

We need the Oracle Enterprise Manager agent to be under the control of the Oracle Private Cloud Appliance software and not any local OS based startup scripts. Therefore we need to remove any OS based rc.* links to scripts. As the root user on the active management node:
[root@ovcamn06r1 ~]# for x in `find /etc/rc.*/rc* | grep gcstart`; do rm $x; done

Next, copy the the Oracle Enterprise Manager agent installation files from the active management node (in our case ovcamn06r1) to the passive management node (ovcamn05r1) as the root user:
[root@ovcamn06r1 ~]# scp /etc/init.d/gcstartup root@ovcamn05r1:/etc/init.d/
[root@ovcamn06r1 ~]# rsync -og /etc/oragchomelist root@ovcamn05r1:/etc/oragchomelist
[root@ovcamn06r1 ~]# rsync -rog /u01/app/oraInventory/ oracle@ovcamn05r1:/u01/app/oraInventory

The Oracle Private Cloud Appliance software is automatically configured with the default Oracle Enterprise Manager agent firewall port (3872) open. If you are not using the default port of 3872 you need to open the firewall as the root user on both the active and passive management nodes to enable the Oracle Enterprise Manager agent to function:
[root@ovcamn06r1]# iptables -A INPUT -m state --state NEW -m tcp -p tcp --dport <Chosen Port> -j ACCEPT
[root@ovcamn06r1]# service iptables save
iptables: Saving firewall rules to /etc/sysconfig/iptables:[ OK ]
[root@ovcamn06r1]# service iptables start
[root@ovcamn06r1]# service iptables status|grep <Chosen Port>
22 ACCEPT tcp -- 0.0.0.0/0 0.0.0.0/0 state NEW tcp dpt:<Chosen Port>

[root@ovcamn05r1]# iptables -A INPUT -m state --state NEW -m tcp -p tcp --dport <Chosen Port> -j ACCEPT
[root@ovcamn05r1]# service iptables save
iptables: Saving firewall rules to /etc/sysconfig/iptables:[ OK ]
[root@ovcamn05r1]# service iptables start
[root@ovcamn05r1]# service iptables status|grep <Chosen Port>
22 ACCEPT tcp -- 0.0.0.0/0 0.0.0.0/0 state NEW tcp dpt:<Chosen Port>

We now need to start the Oracle Enterprise Manager agent either as the root or oracle user on the active management node.
Example as the root user:
[root@ovcamn06r1 ~]# /etc/init.d/gcstartup start

Example as the oracle user:
-bash-4.1$ /nfs/shared_storage/oem13agent/agent_inst/bin/emctl start agent

Step 7: Remove the blackout state:

We now need to remove the indefinite Blackout from the Oracle Private Cloud Appliance physical, logical and virtual components. To do this either go to the Oracle Private Cloud Appliance home page and use the main menu to select Control=>End Blackout. From this page click on the Yes button to stop the Blackout. The Blackout will now be stopped and confirmed by being removed from the Oracle Private Cloud Appliance home page.

Be the first to comment

Comments ( 0 )
Please enter your name.Please provide a valid email address.Please enter a comment.CAPTCHA challenge response provided was incorrect. Please try again.Captcha