This section explains features and tasks specific to Oracle EXAchk on Oracle Exalogic.
Oracle EXAchk is a health check tool that is designed to audit important configuration settings in an Oracle Exalogic Elastic Cloud machine.
Oracle EXAchk examines the following components:
Compute nodes
Storage appliance
InfiniBand fabric
Ethernet network
Exalogic Control vServers, relevant only in virtual configurations
Guest vServers, relevant only in virtual configurations
Oracle EXAchk audits the following configuration settings:
Hardware and firmware
Operating system kernel parameters
Operating system packages
You must run Oracle EXAchk for Exalogic in the following conditions:
After deploying the machine.
Before and after patching or upgrading the infrastructure.
Before and after making any changes in the system configuration.
Before and after any planned maintenance activity.
See Also:
My Oracle Support Note 1449226.1 for the latest scope and supported platforms specific to Oracle EXAchk on Oracle Exalogic, which is available at the following URL:
Review the list of prerequisites.
Oracle recommends that you install Oracle EXAchk on the pre-existing share /export/common/general
on the ZFS storage appliance on the Exalogic machine. You can then run Oracle EXAchk and access the Oracle EXAchk generated HTML reports from a compute node on which the /export/common/general
share is mounted.
For Exalogic machines in a virtual configuration, Oracle recommends that you mount the /export/common/general share
on the vServer that hosts the Enterprise Controller component of the Exalogic control stack, and run Oracle EXAchk from that vServer.
To install Oracle EXAchk on the /export/common/general
share, you must complete the following steps:
Enable NFS on the /export/common/general
share.
Mount the /export/common/general
share.
export/common/general
, enable NFS share mode on the share.el01cn01
is used as the example of the host on which the /export/common/general
share is mounted.Before installing Oracle EXAchk on the pre-existing share export/common/general
, enable NFS share mode on the share.
In this section, compute node el01cn01
is used as the example of the host on which the /export/common/general
share is mounted.
Note:
For an Exalogic machine in a virtual configuration running EECS 2.0.6, mount the export/common/general
share on the vServer that hosts the Enterprise Controller component of the Exalogic Control stack. Substitute the compute node el01cn01
in this procedure with the host name or IP address of that vServer.
For an Exalogic machine running EECS 2.0.4 (virtual), if traffic from the eth-admin
network cannot be routed to the EoIB-external-mgmt
network, when you run Oracle EXAchk from the Enterprise Controller vServer, then health checks are not performed for the switches and the storage appliance. On such racks, to perform health checks on the physical components, you must mount the export/common/general
share on a compute node as well.
In a virtual configuration, if you run Oracle EXAchk from a compute node, Oracle EXAchk does not perform health checks for the Exalogic Control components.
Review the prerequisite for viewing Oracle EXAchk HTML Report in a web browser.
Enable access to the /export/common/general
share through the HTTP/WebDAV Protocol
To enable access to a share through the HTTP/WebDAV protocol, complete the following steps:
Follow these instructions to install and upgrade Oracle EXAchk on Oracle Exalogic.
Follow these instructions to install Oracle EXAchk on a physical Oracle Exalogic machine.
See Also:
Mount the /export/common/general Share share section in the Exalogic Elastic Cloud Exachk User's Guide, for more details.
Install Oracle EXAchk in the /export/common/general
share by completing the following steps:
Follow these instructions to install Oracle EXAchk on a virtual Oracle Exalogic machine.
See Also:
Mount the /export/common/general Share share section in the Exalogic Elastic Cloud Exachk User's Guide, for more details.
Install Oracle EXAchk in the /export/common/general
share by completing the following steps:
For optimum performance of the Oracle EXAchk tool, Oracle recommends that you complete the following steps.
Oracle EXAchk is a minimal impact tool. However, Oracle recommends that you run Oracle EXAchk when the load on the system is low. The runtime of Oracle EXAchk depends on the number of nodes to check, CPU load, network latency, and so on.
Do not run the scripts in the Oracle EXAchk directory unless specifically documented.
To avoid problems while running the tool from terminal sessions on a workstation or laptop, connect to the Exalogic machine and then run Oracle EXAchk by using VNC. Even if a network interruption occurs, Oracle EXAchk continues to run.
Run Oracle EXAchk as root
.
Whenever the tool requires root user privileges, it displays a message as follows:
7 of the included audit checks require root privileged data collection. If sudo is not configured or the root password is not available, audit checks which require root privileged data collection can be skipped. 1. Enter 1 if you will enter root password for each host when prompted (once for each node of the cluster) 2. Enter 2 if you have sudo configured for oracle user to execute /tmp/root_exachk.sh script 3. Enter 3 to skip the root privileged collections 4. Enter 4 to exit and work with the SA to configure sudo or arrange for root access and run tool later Please indicate your selection from one of the above options:-
If you select 1, then the tool prompts you to enter the root
password for each node. Enter the root
password once for each node.
If you select 2, and if you have sudo
configured on your system, then the tool performs the root
privileged collection by using the sudo
credentials.
If you select 3, then the tool skips all of the root privileged collections and audit checks. Perform those checks manually.
Perform health checks in a virtual or physical racks.
Prerequisites
The term infrastructure is used here to indicate the compute nodes, switches, storage appliance, and, additionally, the Exalogic Control stack in the case of a machine in a virtual configuration.
Before running Oracle EXAchk for the Exalogic infrastructure components, ensure to meet the following prerequisites:
Ensure that Oracle EXAchk is installed as described in Installing EXAchk.
Before running Oracle EXAchk for the first time, make a note of the short names of the storage nodes and switches: el01sn01
, el01sw-ib01
, and so on. Oracle EXAchk prompts you for these names at the start of the health check process. This is a one time prompt. Oracle EXAchk stores the names you provide, and uses the stored names for subsequent runs.
Running Oracle EXAchk for Physical Racks
To perform health checks for all the infrastructure components in an Exalogic machine in a physical Linux or Solaris configuration, complete the following steps:
SSH as root
to the compute node on which you installed Oracle EXAchk.
# cd /u01/common/general/exachk
# ./exachk
When running Oracle EXAchk for the first time, the tool detects the size of the Exalogic rack and prompts for the host name or IP address of the switch and storage node. For information about overriding the IP addresses and host names set during the first run.
Running Oracle EXAchk for Virtual Racks
To perform health checks for all the infrastructure components in an Exalogic machine in a virtual configuration, complete the following steps:
SSH as root to the vServer that hosts the Enterprise Controller.
# cd /u01/common/general/exachk
# ./exachk
Oracle EXAchk automatically discovers the IP addresses or host names of all the components in the machine, and starts performing the health checks.
See Also:
Section 4.4, “Overriding Discovered Component Addresses” in the Oracle Exalogic Elastic Cloud EXAchk User's Guide, for more details.
Note:
For an Exalogic machine running EECS 2.0.4 (virtual), if traffic from the eth-admin
network is not routed to the EoIB-external-mgmt
network when you run Oracle EXAchk from the Enterprise Controller vServer, Oracle EXAchk does not run health checks for the switches and storage heads. On such racks, do the following to perform health checks on all the components:
Perform health checks for the Exalogic Control components:
SSH as root
to the Enterprise Controller vServer.
# cd /u01/common/general/exachk
# ./exachk -profile control_VM
Oracle EXAchk reports that all the checks on the compute nodes passed. However, this command did not perform any health checks on the compute nodes, the storage appliance, and the switches.
Perform health checks for the physical components, such as compute nodes, storage appliance, and switches:
SSH as root
to the compute node on which you installed Oracle EXAchk.
Ensure that passwordless SSH to the Oracle VM Manager CLI shell is enabled.
# cd /u01/common/general/exachk
# ./exachk -profile el_extensive
Running Oracle EXAchk for Hybrid Racks
To perform health checks for all the infrastructure components in an Exalogic machine in a hybrid configuration, that is, a machine on which half the nodes are running Oracle VM Server and the other half are on Oracle Linux, complete the following steps:
SSH as root
to the vServer that hosts the Enterprise Controller component of the Exalogic Control stack.
# cd /u01/common/general/exachk
./exachk -hybrid -phy physical_node_1[,physical_node_2,...]
In this command, physical_node_1
, physical_node_2
, and so on are the eth-admin
IP addresses of the compute nodes running Oracle Linux.
The -phy physical_node_1[,physical_node_2,...]
must be specified only the first time you run Oracle EXAchk with the -hybrid
option. Oracle EXAchk stores the host names in the exachk_exalogic.conf
file. For subsequent runs, you can run Oracle EXAchk without specifying the -phy
option. Oracle EXAchk uses the host names stored in theexachk_exalogic.conf
file.
Run Oracle EXAchk to perform health checks for guest vServers.
Prerequisites
This section describes the prerequisites that you must complete before running Oracle EXAchk for all guest vServers.
Install Oracle EXAchk as described in Installing Oracle EXAchk.
Install IaaS CLI and API on the vServer that hosts the Enterprise Controller. Note that the IaaS CLI and API are pre-installed on the Enterprise Controller vServer in EECS 2.0.4.
To verify this prerequisite, check whether the /opt/oracle/iaas/cli
and /opt/oracle/iaas/api
directories exist on the vServer. If the directories exist, then the IaaS CLI and API are installed.
To install the IaaS CLI and API, complete the following steps:
Go to https://edelivery.oracle.com.
Sign in by using your Oracle account.
Read and accept the Oracle Software Delivery Cloud Trial License Agreement and the Export Restrictions. Click Continue.
In the Select a Product Pack field, select Oracle Fusion Middleware.
In the Platform field, select Linux x86-64.
Click Go.
In the results displayed, select Oracle Exalogic Elastic Cloud Software 11g Media Pack, and click Continue.
Look for Oracle Exalogic <version> IaaS Client for Exalogic Linux x86-64 (64–bit), and download the appropriate version – 2.0.4.0.0, 2.0.6.0.0, or 2.0.6.0.1 depending on the EECS release installed on the Exalogic machine.
Unzip the downloaded file.
rpm -i *.rpm
Additional Prerequisites for STIG-hardened vServers
You can harden guest vServers using the STIGfix tool. The STIGfix tool is packaged as part of the Exalogic Lifecycle Toolkit.
Download the toolkit installer and tar bundle.
See Also:
My Oracle Support Note 1586312, which is available at the following URL:
Refer to My Oracle Support Note for toolkit install instructions.
To run Oracle EXAchk on STIG-hardened vServers, you must perform the following prerequisites:
Run Oracle EXAchk on STIG-hardened vServers separately from other guest vServers.
The vServer that hosts the Enterprise Controller and the STIG-hardened guest vServers must have the same user with sudo
privileges. You can create these users by doing the following.
Create the account on the vServer hosting Enterprise Controller as follows:
Log in to the vServer hosting Enterprise Controller as root.
# useradd -d /home/ELAdmin -s /bin/bash -m ELAdmin # echo "ELAdmin:<password>"|chpasswd # echo "PATH=$PATH.:/usr/kerberos/sbin:/usr/kerberos/bin:/usr/local/sbin:/usr/local/bin:/sbin:/bin:/usr/sbin:/usr/bin:/root/bin" >>/home/ELAdmin/.bashrc # usermod -a -G oinstall ELAdmin
Replace password
with a password of your choice.
Run the visudo
command.
%ELAdmin ALL=(ALL) ALL
%ELAdmin ALL=(ALL) NOPASSWD: ALL
Save the file.
Create the ELAdmin account that you created on the Enterprise Controller, on the guest vServer that is STIG-hardened as follows:
Log in to the vServer that is STIG-hardened.
su root
# useradd -d /home/ELAdmin -s /bin/bash -m ELAdmin # echo "ELAdmin:<password>"|chpasswd # echo "PATH=$PATH.:/usr/kerberos/sbin:/usr/kerberos/bin:/usr/local/sbin:/usr/local/bin:/sbin:/bin:/usr/sbin:/usr/bin:/root/bin" >>/home/ELAdmin/.bashrc
Replace password
with a password of your choice.
Run the visudo
command.
%ELAdmin ALL=(ALL) ALL
%ELAdmin ALL=(ALL) NOPASSWD: ALL
Save the file.
Running Oracle EXAchk for vServers that are not STIG-hardened
To perform health checks for all the guest vServers that are not STIG-hardened, in a vDC on an Exalogic machine, complete the following steps:
SSH as root
to the vServer that hosts the Enterprise Controller.
# cd /u01/common/general/exachk
# ./generate_guests_list.sh
Note:
IaaS API is not installed. Please consult with user guide for more information on IaaS API installation.
If this error occurs, install the IaaS CLI and API, as described above and then perform this procedure from step 1.
When prompted, enter the root
password.
Note:
At times, particularly right after installing the IaaS CLI and API, when you enter the root password, the generate_guests_list.sh
script may hang.
If this error occurs, complete the following steps:
# export IAAS_HOME="/opt/oracle/iaas/cli" # export JAVA_HOME="/usr/java/latest/"
# /opt/oracle/iaas/cli/bin/akm-describe-accounts --base-url https://localhost/ --user root
At the prompt to accept the trust certificate, enter yes
.
Run generate_guests_list.sh
again.
The script generates a set of .out files, one for each Cloud User. The files are named guest_vm_ip_user.out
, where user is a Cloud User. Each .out
file contains the IP addresses of the guest vServers created by a Cloud User.
-vmguest
option, and specify one or more guest_vm_ip_user.out
files as arguments, depending on the users for which you want to perform health checks for guest vServers:
# ./exachk -vmguest guest_vm_ip_user-1.out[,guest_vm_ip_user-1.out,...]
Running Oracle EXAchk for STIG-hardened vServers
Run Oracle EXAchk for STIG-hardened vServers by doing the following:
Log in as root on the vServer that hosts the Enterprise Controller.
ELAdmin
user by running the following command:
su - ELAdmin
Note:
When running Oracle EXAchk on STIG-hardened vServers, Oracle recommends using only the ELAdmin user which you created above.
guest_vm_ip_user.out
manually. The guest_vm_ip_user.out
has the following format:
ip_address_of_stig_hardened_guest_vserver1 ip_address_of_stig_hardened_guest_vserver2 ip_address_of_stig_hardened_guest_vserver3
-vmguest
option, and specify one or more guest_vm_ip_user.out
files as arguments, depending on the users for which you want to perform health checks for guest vServers:
# ./exachk -vmguest guest_vm_ip_user-1.out[,guest_vm_ip_user-1.out,...]
Review the Oracle EXAchk start up sequence of events.
At the start of the health check process, Oracle EXAchk prompts you for the names of the storage nodes and switches. At the prompt, enter the names or IP addresses of the storage nodes and switches. This is a one time process. Oracle EXAchk remembers these values and uses them for the consequent health checks.
$ ./exachk Could not find infiniband gateway switch names from env or configuration file. Please enter the first gateway infiniband switch name : el01sw-ib02 Could not find storage node names from env or configuration file. Please enter the first storage server : el01sn01 Checking ssh user equivalency settings on all nodes in cluster Node el01cn02 is configured for ssh user equivalency for root user Node el01cn03 is configured for ssh user equivalency for root user Node el01cn04 is configured for ssh user equivalency for root user Node el01cn05 is configured for ssh user equivalency for root user Node el01cn06 is configured for ssh user equivalency for root user
Note:
Enter the host names or IP addresses for the nodes, in the sequence in which they are arranged on the machine.
The health check tool checks the SSH user equivalency settings on all of the nodes in the cluster.
If the tool determines that the user equivalence is not established on the nodes, it provides you an option to set the SSH user equivalency either temporarily or permanently.
If you choose to set SSH user equivalence temporarily, then EXAchk does this for the duration of the health check. However, after the completion of the health check, Oracle EXAchk returns the system to the state in which it found.
When Oracle EXAchk prompts you to specify your preference. Enter the password for the nodes for which you are prompted. The default preference, 1, allows you to enter the root password once for all of the nodes on each host of the Exalogic machine.
Using cached file /root/exachk/o_ibswitches.out for gateway infiniband switches list .... Using cached file /root/exachk/o_storage.out for storage nodes list .... Checking ssh user equivalency settings on all nodes in cluster Node 0 is configured for ssh user equivalency for root user Node 0 is configured for ssh user equivalency for root user root user equivalence is not setup between 2 and STORAGE SERVER. 1. Enter 1 if you will enter root password for each STORAGE SERVER when prompted. 2. Enter 2 to exit and configure root user equivalence manually and re-run exachk. 3. Enter 3 to skip checking best practices on STORAGE SERVER. Please indicate your selection from one of the above options[1-3][1]:- 1-3 Is root password same on all STORAGE SERVER?[y/n][y]
On confirming the option and entering the credentials to proceed, Oracle EXAchk creates a number of output files, log files, and collection files for collecting the data required for the health check.
Preparing to run root privileged commands on INFINIBAND SWITCH el01sw-ib04. root@el01sw-ib04's password: Collecting - Environment Test Collecting - Ethernet over infiniband data and control SL Collecting - Free Memory Collecting - Gateway Configuration Collecting - Infiniband status Collecting - List Link Up Collecting - Localhost Configuration in /etc/hosts Collecting - VNICS Collecting - Version Collecting - configvalid Collecting - opensm Preparing to run root privileged commands on INFINIBAND SWITCH el01sw-ib05. root@el01sw-ib05's password: Collecting - Environment Test Collecting - Ethernet over infiniband data and control SL Collecting - Free Memory Collecting - Gateway Configuration Collecting - Infiniband status Collecting - List Link Up Collecting - Localhost Configuration in /etc/hosts Collecting - VNICS Collecting - Version Collecting - configvalid Collecting - opensm
Oracle EXAchk checks the status of the components of the Exalogic stack, such as compute nodes, storage nodes, and InfiniBand switches. Depending on the status of each component, the tool runs the appropriate collections and audit checks.
================================================================== Node name - 0 ================================================================== WARNING => NTP is not synchronized correctly. INFO => One or more NFS Mount Points don't sue the current recommended NFSv4. WARNING => One or more NFS Mount Points uses incorrect rsize or wsize. WARNING => Virtual Memory is not tuned to the recommended configuration. WARNING => Ypbind is not configured correctly. WARNING => DNS service is not configured correctly. WARNING => IP Configuration for eth0 and bond0 are not configured correctly. INFO => EoIB Setup is not set up. INFO => Please verify BIOS Setting. See the Action / Repair section for instructions. WARNING => Lock Daemon Configuration is not configured correctly. ================================================================== Node name - 0 ================================================================== WARNING => NTP is not synchronized correctly. INFO => One or more NFS Mount Points don't sue the current recommended NFSv4. WARNING => One or more NFS Mount Points uses incorrect rsize or wsize. WARNING => Virtual Memory is not tuned to the recommended configuration. WARNING => Ypbind is not configured correctly. WARNING => DNS service is not configured correctly. WARNING => IP Configuration for eth0 and bond0 are not configured correctly. INFO => EoIB Setup is not set up. INFO => Please verify BIOS Setting. See the Action / Repair section for instructions. WARNING => Lock Daemon Configuration is not configured correctly.
Oracle EXAchk runs in the background monitoring the progress of the command run. If any of the commands times out, Oracle EXAchk either skips or terminates that command so that the process continues. Oracle EXAchk logs such cases in the log files.
# ps -ef | grep exachk
# kill pid
In this command pid
is the process ID of the Oracle EXAchk process that you want to terminate.
Verify if /tmp/.exachk/
, the temporary directory generated by Oracle EXAchk during the previous run is deleted. If the directory still exists, delete it.
When Oracle EXAchk completes the health check, it produces an HTML report and a zip file.
Follow these procedures to run Oracle EXAchk in silent mode. When you run Oracle EXAchk in silent mode, it does not perform health checks for storage nodes and InfiniBand switches.
Related Topics
In a physical environment, the component IP addresses or host names are determined in the first run based on user input. In a virtual environment, Oracle EXAchk has an in-built mechanism to automatically discover the IP addresses or host names of all the components. These features are designed to minimize the need for end-user input.
If you are running Oracle EXAchk from a compute node, then do the following:
To override the names of the I switches, edit or create the file o_ibswitches.out
in the directory that contains the exachk
binary. The file should contain a list of host names of the NM2-GW switches, each on a separate line.
To override the names of the storage components, edit or create the file o_storage.out
in the directory that contains the exachk
binary. The file should contain a list of host names of the storage heads, each on a separate line.
export RAT_CLUSTERNODES="el01cn01 el01cn02 el01cn03 el01cn04"
If you are running Oracle EXAchk from the vServer that hosts the Enterprise Controller component of the Exalogic Control stack, you must use a file named exachk_exalogic.conf
to define the names of the components.
The exachk.zip
contains the following templates for exachk_exalogic.conf
in the templates subdirectory:
exachk_exalogic.conf.tmpl_full
exachk_exalogic.conf.tmpl_half
exachk_exalogic.conf.tmpl_quarter
exachk_exalogic.conf.tmpl_eight
Copy the template that corresponds to the size of your Exalogic machine to the directory that contains the exachk
binary, and rename the template file to exachk_exalogic.conf
.
Modify exachk_exalogic.conf
to match your IP address schema.
Note:
Oracle recommends that you create a copy of the exachk_exalogic.conf
file that Oracle EXAchk generates the first time when the system is fully populated and functional, so that you can use the file later.
Oracle EXAchk attempts to derive all the data it needs from the environment in which it is run. However, at times, the tool does not work as expected due to local system variations. In such cases, you can use local environment variables to override the default behavior of Oracle EXAchk.
Table 3-7 Oracle EXAchk Environment Variables
Environment Variables | Description | Example |
---|---|---|
RAT_OS |
Enables the utility to verify the platform information. |
For a 64 bit Oracle Enterprise Linux 5 machine, with x86 architecture, use the following command to set the RAT_OS variable:
export RAT_OS=LINUXX8664OELRHEL5 For a 64 bit Oracle Solaris 11 machine, with x86 architecture, use the following command to set the RAT_OS variable:
export RAT_OS=SOLARISX866411 |
RAT_SSHELL |
Redirects Oracle EXAchk to the default secure shell location. |
export RAT_SSHELL="/usr/bin/ssh -q" |
RAT_SCOPY |
Redirects Oracle EXAchk to the default secure copy (scp) location. |
export RAT_SCOPY="/usr/bin/scp -q" |
RAT_LOCALONLY |
If set to 1, then directs Oracle EXAchk to perform health checks on only the compute node from which Oracle EXAchk is run; that is, Oracle EXAchk skips the checks for the storage nodes, the switches, and all the compute nodes other than one from which it is run. |
To direct Oracle EXAchk to perform health checks on only the compute node from which Oracle EXAchk is run, use the following command:
export RAT_LOCALONLY=1 |
RAT_CELLS |
Directs Oracle EXAchk to run checks on one of the two storage nodes. If the names of the storage nodes are non-standard, then edit the |
To direct Oracle EXAchk to run checks on the second storage node, use the following command:
export RAT_CELLS="el01sn02" |
RAT_SWITCHES |
Directs Oracle EXAchk to run checks on sub-sets of the InfiniBand switches, in addition to the default checks on the InfiniBand switches. If the names of the switches are non-standard, then edit the |
To direct Exact to run on the InfiniBand switch
el01sw-ib02 and its subsets, use the following command:
export RAT_IBSWITCHES="el01sw-ib02" |
RAT_CLUSTERNODES |
Directs Oracle EXAchk to run checks on specific nodes. |
On a quarter rack, which has eight compute nodes, use the following command to list the compute nodes on which the health check needs to be performed:
export RAT_CLUSTERNODES="el01cn01 el01cn02 el01cn03 el01cn04 el01cn05 el01cn06 el01cn07 el01cn08" |
RAT_ELRACKTYPE |
Indicates whether the machine is an eighth rack (0), quarter rack (1), half rack (2), or full rack (3). |
To specify that the system is a full rack, use the following command:
export RAT_ELRACKTYPE="3" |
Note:
In a virtual configuration, when running Oracle EXAchk from the vServer that hosts the Enterprise Controller component of the Exalogic Control stack, do not use the RAT_CELLS, RAT_SWITCHES, and RAT_CLUSTERNODES variables to override the storage node, switches, and compute nodes for which Oracle EXAchk should perform health checks. Instead, use the exachk_exalogic.conf
file.
Related Topics
For Exalogic systems, support has been added to run health checks on External ZFS Storage appliances. The results of these checks are displayed in the External ZFS Storage Appliance of the report.
Figure 3-8 External ZFS Storage Appliance
Identify the checks that you need to act immediately to remediate, or investigate further to assess the checks that might cause performance or stability issues.
Reading and Interpreting the Oracle EXAchk HTML Report
http://el01sn01/export/common/general/exachk/exachk_el01cn01_053112_101705/exachk_el01cn01_053112_101705.html
In this example, el01sn01
is the name of the storage node, el01cn01
is the name of the compute node on which the share is mounted, and 053112_101705
is the date-and-time stamp for the report.
See Also:
"Enable Access to the /export/common/general Share Through the HTTP/WebDAV Protocol", for more details about enabling access to a share through the HTTP/WebDAV protocol.
The following is specific to Oracle EXAchk on Exalogic:
Table 3-8 Oracle EXAchk on Exalogic Message Definitions
Message Status | Description or Possible Impact | Action to be Taken |
---|---|---|
FAIL |
Shows checks that did not pass due to issues. |
Address the issue immediately. |
WARNING |
Shows checks that might cause performance or stability issues if not addressed. |
Investigate the issue further. |
ERROR |
Shows errors in system components. |
Take corrective measures, and restart Oracle EXAchk. |
INFO |
Indicates information about the system. |
Read the information displayed in these checks, and follow the instructions provided, if any. |
System-Wide Firmware and Software Versions
This section lists the firmware and software versions of all the components for which the health check was performed.
Skipped Nodes
This section lists components for which Oracle EXAchk did not perform any health check. Skipped components are those that, typically, Oracle EXAchk cannot access.
The following table lists the typical situations when Oracle EXAchk skips a component and the solutions for each situation:
Table 3-9 Oracle EXAchk on Exalogic Skipped Nodes
Situation | Solution |
---|---|
The IP address of the component is incorrect or the host name cannot be resolved. |
Update |
The component is not running. |
Ping or SSH to the component. If the ping or SSH command fails, ensure that the component is started. Then, run Oracle EXAchk again. |
The network is congested and very slow, causing an SSH time-out. |
Try increasing the value of the environment variable, RAT_TIMEOUT, and run Oracle EXAchk again. |
The component is overloaded and low on memory, causing a password time-out. |
Try increasing the value of the environment variable, RAT_PASSWORDCHECK_TIMEOUT, and run Oracle EXAchk again. |
Comparing Component Versions in Two Oracle EXAchk Collections
You can use the -exadiff
option of Oracle EXAchk to compare two Oracle EXAchk collections. When you use this option, Oracle EXAchk generates a comparison report in HTML format, highlighting the differences in the versions of the infrastructure components, hardware, firmware, and software between the two reports. The two Oracle EXAchk reports can be for different Exalogic racks or at different points in time for the same rack, such as before and after upgrading the rack.
To compare two Oracle EXAchk collections, complete the following steps:
Identify the two Oracle EXAchk collections, zip files that you want to compare.
If the collections do not already exist on the host, compute node or vServer on which you are running Oracle EXAchk, then copy the collections to the host.
./exachk -exadiff collection_1 collection_2
In this command, collection_1
and collection_2
are the full paths and names of the two collections that you want to compare. You can specify either the collection zip file or the directory in which the zip file has been extracted.
Wait for the command to finish running.
After comparing the two collections, Oracle EXAchk saves the results of the comparison in an HTML file named rack_comparison_date_time.html
, for example, rack_comparison_131219_213435.html
.
You can view the HTML report in a browser by using an HTTP URL as shown in the following example:
Example 3-1 Comparing Component Versions in Two Oracle EXAchk Collections
http://el01sn01/export/common/general/exachk/rack_comparison_131219_213435.html
In this example, el01sn01
is the name of the active storage node, /common/general
is the share in which the Oracle EXAchk reports are stored, and 131219_213435
is the date-and-time stamp for the report.
List of command line options applicable to Exalogic.
Command Options Applicable to Exalogic
Table 3-10 Command Options Applicable to Exalogic
Option | Purpose and Syntax |
---|---|
|
Performs checks on only the specified compute nodes and all the other components, and exclude the unspecified compute nodes. Syntax:
./exachk -clusternodes cn_1[,cn_2,...] |
|
Compares two Oracle EXAchk HTML reports and generate an HTML report showing the changes in the health of the Exalogic rack between Oracle EXAchk runs. Syntax:
# ./exachk -diff report1 report2 [-outfile compared_report.html] See Section 5.3, “Comparing Health-Check Results in Two EXAchk HTML Reports” in the Exalogic Elastic Cloud EXAchk User's Guide, for more details. |
|
Compares two Oracle EXAchk zip collections and generate an HTML report showing the differences in the versions of the infrastructure components, hardware, firmware, and software between the two reports. The two Oracle EXAchk reports can be for different Exalogic racks or at different points in time for the same rack, such as before and after upgrading the rack. Syntax:
./exachk -exadiff exachk_collection_zip_1 exachk_collection_zip_2 See Section 5.5, “Comparing Component Versions in Two EXAchk Collections” in the Exalogic Elastic Cloud EXAchk User's Guide, for more details. |
|
Performs checks on already collected data. Syntax:
./exachk -f report_name |
|
Performs checks for guest vServers as well. Syntax:
./exachk -vmguest conf_file_1[,conf_file_2,...] See Section 3.3, “Performing Health Checks for Guest vServers” in the Exalogic Elastic Cloud EXAchk User's Guide, for more details. |
|
Performs checks on physical nodes as well in a hybrid rack. Syntax:
./exachk -hybrid See Section 3.2.4, “Running EXAchk for Hybrid Racks” in the Exalogic Elastic Cloud EXAchk User's Guide, for more details. |
|
Perform checks for only the host on which Oracle EXAchk is running. Syntax:
./exachk -localonly |
|
Excludes passed checks from the HTML report. Syntax:
./exachk -nopass |
|
Displays results for all checks, including those that passed. Syntax:
./exachk -o v |
|
Use this option along with Syntax:
./exachk -hybrid -phy node_1[,node_2,...] See Section 3.2.4, “Running EXAchk for Hybrid Racks” in the Exalogic Elastic Cloud EXAchk User's Guide, for more details. |
|
Performs specific checks or checks for specific components. Syntax:
./exachk -profile profile_name See Supported Profiles for the -profile option, for more details. |
|
Runs Oracle EXAchk in silent mode. Syntax:
./exachk -s See Section 4.3, “Running EXAchk in Silent Mode” in the Exalogic Elastic Cloud EXAchk User's Guide, for more details. |
|
Displays the version of the tool. Syntax:
./exachk -v |
Supported Profiles for the -profile Option
Table 3-11 Supported Profiles for the -profile option
Profile | Description |
---|---|
|
Runs health checks for only the Exalogic Control components. |
|
In addition to the standard set of checks, run the following checks that are useful for a freshly installed or upgraded machine:
Note: Before running Oracle EXAchk with the |
|
Runs checks for the switches. |
|
Runs checks for the Exalogic virtual infrastructure. This check is applicable to only Exalogic machines in a virtual configuration. |
|
Runs checks for the storage appliance. |
el_extensive
profile, you must verify whether passwordless SSH is enabled for the CLI shell of Oracle VM Manager.Before running Oracle EXAchk with the el_extensive
profile, you must verify whether passwordless SSH is enabled for the CLI shell of Oracle VM Manager.
# ssh -l admin host_name_of_localhost -p 10000
is the host name of the localhost.host_name_of_localhost
If you can log in without having to enter a password, that is, if the OVM>
prompt is displayed, then passwordless SSH is enabled.
If a password prompt is displayed, do the following:
welcome1
.OVM>
shell, and try logging in again through SSH. If the password prompt continues to display, then passwordless SSH is not enabled. To enable passwordless SSH to the Oracle VM Manager CLI, complete the following steps:
Troubleshoot and fix Oracle EXAchk on Exalogic issues.
See Also:
My Oracle Support Note 1478378.1 for the latest known issues specific to Oracle EXAchk on Oracle Exalytics, which is available at the following URL:
Issues with the Local Environment Settings
See Setting Environment Variables for more details.
Contacting Support with Oracle EXAchk Report
–profile el_extensive
option to include a larger set of health checks in the generated HTML report:
./exachk -profile el_extensive
Contact Support with Oracle EXAchk result bundle as needed for further assistance.
-debug
option as shown below:
./exachk -debug
Contact Support with the resulting output zip file.