2 Installing and Upgrading Exachk for Exalogic

This chapter contains the following sections:

2.1 Prerequisites

This section describes the following prerequisites:

2.1.1 Prerequisites for Installing Exachk

Oracle recommends that you install Exachk on the pre-existing share /export/common/general on the ZFS storage appliance on the Exalogic machine. You can then run Exachk and access the 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 Exachk from that vServer.

To be able to install Exachk on the /export/common/general share, you must complete the following steps:

Enable NFS on the /export/common/general Share

Before installing Exachk on the pre-existing share export/common/general, ensure that the NFS share mode is enabled on the share.

  1. In a web browser, enter the IP address or host name of the storage node as follows:

    https://ipaddress:215

    or

    https://hostname:215

  2. Log in as the root user.

  3. Click Shares in the top navigation pane.

  4. Place your cursor over the row corresponding to the share /export/common/general.

  5. Click the Edit entry button (pencil icon) near the right edge of the row.

    Surrounding text describes four_c.png.
  6. On the resulting page, select Protocols in the top navigation pane.

  7. In the NFS section, deselect Inherit from project, and click the plus (+) button located next to NFS Exceptions.

    Surrounding text describes four_d.png.
  8. Edit the following in the NFS Exceptions section:

    Element Action/ Description
    TYPE Select Network.
    ENTITY Enter the IP address of the host that will access the share.

    Example:

    192.168.10.0/24
    
    ACCESS MODE Select Read/write
    CHARSET Keep the default setting.
    ROOT ACCESS Select the check box.

  9. Click APPLY.

  10. Log out.

Mount the /export/common/general Share

Note:

  • In this section, compute node el01cn01 is used as the example of the host on which the /export/common/general share is mounted.

    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. So substitute 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 Exachk from the Enterprise Controller vServer, health checks will not be 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.

  • Note that, in a virtual configuration, if you run Exachk from a compute node, Exachk will not perform health-checks for the Exalogic Control components.

  1. Check whether the /export/common/general share is already mounted at the /u01/common/general directory on compute node el01cn01.

    You can do this by logging in to el01cn01 as the root user and running the following command:

    # mount
    

    If the /export/common/general share is already mounted on the compute node, the output of the mount command contains a line like the following:

    192.168.10.97:/export/common/general on /u01/common/general ...
    

    In this example, 192.168.10.97 is the IP address of the storage node, el01sn01.

    • If you see the previous line in the output of the mount command, skip step 2.

    • If the output of mount command does not contain the previous line, perform step 2.

  2. Mount the /export/common/general share at a directory on compute node el01cn01.

    1. Create the directory /u01/common/general to serve as the mount point on el01cn01.

      # mkdir -p /u01/common/general
      
    2. Depending on the operating system running on the host on which you want to mount the /export/common/general share, complete the following steps:

      Oracle Linux:

      Edit the /etc/fstab file by using a text editor like vi, and add the following entry for the mount point that you just created:

      el01sn01-priv:/export/common/general /u01/common/general nfs4 rw,bg,hard,nointr,rsize=131072,wsize=131072,proto=tcp
      

      Oracle Solaris:

      Edit the /etc/vfstab file by using a text editor like vi, and add the following entry for the mount point that you just created:

      el01sn01-priv:/export/common/general - /u01/common/general nfs - yes  rw,bg,hard,nointr,rsize=131072,wsize=131072,proto=tcp
      
    3. Save and close the file.

    4. Mount the volumes by running the following command:

      # mount -a
      

2.1.2 Prerequisite for Viewing the 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:

  1. In a web browser, enter the IP address or host name of the storage node as follows:

    https://ipaddress:215

    or

    https://hostname:215

  2. Log in as the root user.

  3. Enable the HTTP service on the appliance, by doing the following:

    1. Click Configuration in the top navigation pane.

      Surrounding text describes three_a.png.
    2. Click HTTP under Data Services.

      Surrounding text describes three_b.png.
    3. Ensure that the Require client login check box is not selected.

      Surrounding text describes three_c.png.
    4. Click APPLY.

      If the button is disabled, select and deselect the Require client login check box.

      Surrounding text describes three_d.png.
  4. Enable read-only HTTP access to the /export/common/general share by doing the following:

    1. Click Shares in the top navigation pane.

    2. Place your cursor over the row corresponding to the /export/common/general share.

    3. Click the Edit entry button (pencil icon) near the right edge of the row.

    4. On the resulting page, click Protocols in the navigation pane.

    5. Scroll down to the HTTP section.

    6. Deselect the Inherit from project check box.

    7. In the Share mode field, select Read only.

      Surrounding text describes five_abcb.png.
    8. Click APPLY located at the top right of the page.

  5. Log out.

2.2 Installing Exachk

Install Exachk in the /export/common/general share by completing the following steps:

  1. This step varies depending on whether you are installing Exachk on an Exalogic machine in a physical or virtual configuration:

    • For Exalogic machines in a physical configuration:

      a. Ensure that /export/common/ general share is mounted on the compute node el01cn01 as described in "Mount the /export/common/general Share".

      b. SSH to the compute node el01cn01.

      c. Create a subdirectory named exachk in /u01/common/general/ to hold the Exachk binaries:

      # mkdir /u01/common/general/exachk
      
    • For Exalogic machines in a virtual configuration:

      a. Ensure that /export/common/ general share is mounted on the vServer that hosts the Enterprise Controller, as described in "Mount the /export/common/general Share".

      Note:

      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 Exachk from the Enterprise Controller vServer, health checks will not be 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.

      b. SSH to the vServer.

      c. Create a subdirectory named exachk in /u01/common/general/ to hold the Exachk binaries:

      # mkdir /u01/common/general/exachk
      

      Note:

      If the vServer is down or otherwise inaccessible, you can run Exachk from a compute node, but in this case, the health checks will not be performed for the Exalogic Control components.
  2. Go to the /u01/common/general/exachk directory.

  3. Download the exachk_version_exalogic_bundle.zip file from the link provided in the following My Oracle Support document.

    https://support.oracle.com/epmos/faces/DocumentDisplay?id=1449226.1

  4. Extract the contents of the exachk_version_exalogic_bundle.zip file.

    # unzip exachk_version_exalogic_bundle.zip
    

    The result is another zip file, exachk.zip.

  5. Extract the contents of exachk.zip.

    # unzip exachk.zip
    

    The Exachk tool is now available at the following location on compute node el01cn01:

    /u01/common/general/exachk/exachk
    

2.3 Upgrading Exachk

You can obtain the latest release of Exachk from the following My Oracle Support document:

https://support.oracle.com/epmos/faces/DocumentDisplay?id=1449226.1

To upgrade to the latest release of Exachk, complete the following steps:

  1. Back up the directory containing the existing Exachk binaries by moving it to a new location.

    For example, if the Exachk binaries are currently in the directory /u01/common/general/exachk, move them to a directory named, say, exachk_05302012, by running the following commands:

    # cd /u01/common/general
    # mv exachk exachk_05302012
    

    In this example, the date when Exachk is upgraded (05302012) is used to uniquely identify the backup directory. Pick any unique naming format, like a combination of the backup date and the release number, and use it consistently.

  2. Create the exachk directory afresh.

    $ mkdir /u01/common/general/exachk
    
  3. Install the new version of Exachk by following steps 2 onward in Section 2.2.