Location via proxy:   [ UP ]  
[Report a bug]   [Manage cookies]                
0% found this document useful (0 votes)
8 views5 pages

Exalogic Exapatch Step-By-Step

Download as docx, pdf, or txt
Download as docx, pdf, or txt
Download as docx, pdf, or txt
You are on page 1/ 5

Preparing to use ExaPatch

ExaPatch is a Utility that applying patches to an Exalogic. This describes how to install, configure, and use ExaPatch, a utility the
process of patching and upgrading the Exalogic (BIOS,ILOM, Firmware, and Software) for the Exalogic Physical.

The new release Exapatch is installed during the PSU bundle installation in the ZFS shares at /exalogic-lctools/bin/ and the complete
directory structure as mentioned:

[root@el01cn]# /exalogic-lcdata/patches/Linux/17666825/Infrastructure/2.0.3.0.5
[root@el01cn]# /exalogic-lctools/bin/exapatch <options> -a <action>

Installing ExaPatch
ExaPatch is included in the Infrastructure folder of Exalogic Patch Set Updates(PSUs) as mention above and ExaPatch is installed
when you run execute command session mention in "Installing the Patch Set Bundle" section.

Creating the Rack Configuration file from the ouput of Exadiscover


ExaPatch requires a rack configuration file containing the IP addresses and login name for each patchable component on the rack.
For each component, the configuration file also includes a directive that specifies how ExaPatch should obtain the login password.

For Exalogic physical configurations, you must create the rack configuration file by using a template and from the Output of
ExaDiscover.

Creating the Rack Configuration File by Using a Template

You can create the rack configuration file from a template by running the createrackconfig.sh as follows:

[root@el01cn]# /exalogic-lctools/lib/exapatch/scripts/createrackconfig.sh -p -c <Number


of Compute Nodes> > /exalogic-lcdata/inventory/rack_configuration.py

For most actions, ExaPatch requires a rack configuration file, which contains the IP addresses and login credentials for each
component in the Exalogic machine.

[root@el01cn]# /exalogic-lctools/lib/exapatch/scripts/createrackconfig.sh -p -c 8 >


/exalogic-lcdata/inventory/rack_configuration.py
Here, the options:

-c number : Specifies the number of compute nodes on the Exalogic machine


-p : Specifies that the rack is in a physical configuration
-v : Specifies that the rack is in a virtual configuration

Creating the Rack Configuration file from the ouput of Exadiscover

To generate the rack configuration file from the output of the ExaDiscover utility, which is bundled with ExaPatch, do the following
from the exadiscover directory:

1. Navigate to the exadiscover directory in the installation directory of ExaPatch:

[root@el01cn]# cd /exalogic-lctools/lib/exapatch/exadiscover

2. Generate a list of the components on the rack by running ExaDiscover from the Exalogic Control vServer, as follows:
[root@el01cn]# ./exadiscover.sh -h address_of_compute_node1 > /tmp/exadiscover_output.out

In this command, address_of_compute_node1 is the hostname or IP address of the first compute


node in your Exalogic machine or the compute node on which Exalogic Configuration Utility was run.

Note : When running ExaDiscover, you can specify the root user password for the compute node by
using the -p password option.

3. Generate the rack configuration file from the output of ExaDiscover, by running the
createrackconfig.sh script, which is available in the /exalogic-lctools/lib/exapatch/scripts folder, as
follows:

[root@el01cn]# cd ../scripts
[root@el01cn]# ./createrackconfig.sh /tmp/exadiscover_output.out >
/exalogic-lcdata/inventory/rack_configuration.py

In this command, rack_configuration.py is the rack configuration file.

Note: Oracle recommends creating a rack configuration file called rack_configuration.py in the
exalogic-lcdata/inventory/ directory. By default, ExaPatch searches exalogic-lcdata/inventory/ for the
rack configuration file.

The rack configuration file that is generated based on the output of ExaDiscover contains, by default,
the IPoIB-admin IP addresses of the components on the rack.

The generated rack configuration file will be of the format:

# [root@el01cn scripts]# more rack_configuration_file.py


class RackConfig:
# This file includes tables of form:
# [ 'host IP', 'username', password ]
# password values can be:
# - DefaultPassword (factory default value)
# - PromptPassword (user will be prompted for the component's password)
# - PromptGroupPassword (user will be prompted once for the password of a group of rack components
of the same type)
# - PromptRackPassword (user will be prompted once for the physical rack components password)
# - PromptECVServerPassword (user will be prompted once for Exalogic Control vServer password)
def getComputeNodesHostInfo(self):
return [
['10.XX.YY.43', 'root', DefaultPassword],
['10.XX.YY.44', 'root', DefaultPassword],
]
def getComputeNodeIlomHostInfo(self):
return [
['10.XX.XX.107', 'root', DefaultPassword],
['10.XX.XX.108', 'root', DefaultPassword],
]
def getZfsHeadHostInfo(self):
return [
['10.XX.XX.101', 'root', DefaultPassword],
['10.XX.XX.102', 'root', DefaultPassword],
]
def getZfsHeadIlomHostInfo(self):
return [
['10.XX.XX.119', 'root', DefaultPassword],
['10.XX.XX.120', 'root', DefaultPassword],
]
def getNM2_gwIbSwitchHostInfo(self):
return [
['10.XX.XX.121', 'root', DefaultPassword],
['10.XX.XX.122', 'root', DefaultPassword],
]
def getNM2_gwIbSwitchIlomHostInfo(self):
return [
['10.XX.XX.121', 'ilom-admin', DefaultPassword],
['10.XX.XX.122', 'ilom-admin', DefaultPassword],
]
def getNM2_36pIbSwitchHostInfo(self):
return [
]
def getNM2_36pIbSwitchIlomHostInfo(self):
return [
]
def getPduHostInfo(self):
return [
['10.XX.XX.125', 'admin', DefaultPassword],
['10.XX.XX.125', 'admin', DefaultPassword],
]
# class definitions for password values
class PromptPassword:
pass
class PromptGroupPassword:
pass
class PromptRackPassword:
pass
class PromptECVServerPassword:
pass
class DefaultPassword:
pass

Replace each 'FIXME' entry with the IP address of the host, and update the password directive as
described above. Ensure that all the patchable components on the rack are listed in the
configuration file. For reference, a sample rack configuration file is included in the ExaPatch
User's Guide. Once ready, the rack configuration file should be copied to the
/exalogic-lcdata/inventory/. ExaPatch looks for a file named rack_configuration.py in the inventory
directory.

Verifying the Rack Components in the Rack Configuration File

Syntax:

root@el01cn :~# /exalogic-lctools/bin/exapatch -a listComponents

For Example (on Exalogic X3 -2 Eighth Rack ):

root@el01cn :~# /exalogic-lctools/bin/exapatch -a listComponents


Rack Components:
el01cn 10.XX.XX.91 root
el01cn 10.XX.XX.92 root
ILOM-ComputeNode 10.XX.XX.109 root
ILOM-ComputeNode 10.XX.XX.110 root
ILOM-ZFS 10.XX.XX.119 root
ILOM-ZFS 10.XX.XX.120 root
NM2-36p-IB-Switch FIXME root
NM2-GW-IB-Switch 10.XX.XX.121 root
NM2-GW-IB-Switch 10.XX.XX.122 root
PDU FIXME admin
PDU FIXME admin
ZFS-Storage-Head 10.XX.XX.101 root
ZFS-Storage-Head 10.XX.XX.102 root

Validating the Password Directives in the Rack Configuration File

Syntax:

[root@el01cn]#/exalogic-lctools/bin/exapatch -a checkAuthentication

For Example:

[root@el01cn]# /exalogic-lctools/bin/exapatch -a checkAuthentication


Logging to file /var/log/exapatch_2014mmddt.log
Login results:
el01cn 10.XX.XX.91 root Succeeded
el01cn 10.XX.XX.92 root Succeeded
ILOM-ComputeNode 10.XX.XX.109 root Failed
ILOM-ComputeNode 10.XX.XX.110 root Succeeded
ILOM-ZFS 10.XX.XX.119 root Succeeded
ILOM-ZFS 10.XX.XX.120 root Succeeded
NM2-36p-IB-Switch FIXME root Failed
NM2-GW-IB-Switch 10.XX.XX.121 root Succeeded
NM2-GW-IB-Switch 10.XX.XX.122 root Succeeded
PDU FIXME admin Failed
PDU FIXME admin Failed
ZFS-Storage-Head 10.XX.XX.101 root Succeeded
ZFS-Storage-Head 10.XX.XX.102 root Succeeded

Verifying the Rack Components in the Rack Configuration File

Validating the Password Directives in the Rack Configuration File

Checking the Version Number of Each Component

Before Proceeding to Patch,create a Rack history File :

Before applying the patches, verify that all the pre-requisites of the components are met. :

Patching and Upgrading the Exalogic Infrastructure Using ExaPatch

Patching the InfiniBand Switches

Patching the NM2-GW Switches


Patching the NM2-36p Switch

Patching the ILOM on the ZFS Storage Heads

Patching the ZFS Software to 2011.1.8

Patching Compute Nodes ILOM

Patching Compute Nodes (Physical)

Patch the OVMM, PC1, and PC2 Templates

Upgrade the Guest vServer

You might also like