FS System: Oracle Enterprise Manager (EM) May Display a Target Status of "Availability Evaluation Error"

Asset ID:	1-72-2203211.1
Update Date:	2017-07-17
Keywords:

Solution Type Problem Resolution Sure

Solution 2203211.1 : FS System: Oracle Enterprise Manager (EM) May Display a Target Status of "Availability Evaluation Error"

Applies to:

Oracle FS1-2 Flash Storage System - Version 6.2 and later
Information in this document applies to any platform.

Symptoms

After upgrading the Oracle Flash Storage FS1-2 to 6.2.7 or higher, Oracle Enterprise Manager, used to manage and monitor the FS1-2, displays a Target status of "Availability Evaluation Error".

Cause

The FS1-2 release 6.2.7 and higher require Transport Layer Security (TLS) v1.1 or higher for all storage management applications and plugins that access the FS1-2 management interface. TLS v1.1 is not enabled by default for Oracle EM12c or EM13c.

Solution

Upgrades for Oracle Enterprise Manager (EM) are required. Although EM 12c can be upgraded to support TLS, the easier method is to upgrade to EM 13c. Please contact Oracle Customer Support for Oracle Enterprise Manager for assistance in upgrading.

The EM for Oracle Flash Storage System (EM Plugin) must also be updated to version 12.1.0.2.0 to support TLS v1.1. This version is available using one of the following methods:

Use the Oracle Enterprise Manager Self Update Console to install the plug-in "Oracle Flash Storage System 12.1.0.2.0". For detailed information on this process, review the Managing Plug-Ins topic in the Oracle Enterprise Manager online help or the Oracle Enterprise Manager Cloud Control Administrator's Guide.
The updated EM Plugin can also be downloaded from Oracle Technical Network under Oracle Flash Storage System and Pillar Axiom Downloads, as "Oracle EM 12c/13c Plug-in (Oracle Flash Systems Only)". The extracted zip file should be "12.1.0.2.0_oracle.ofs.ofss_2000_0.opar" which is the version compatible with Enterprise Manager 12.1.0.5.0 and higher.

The Oracle Enterprise Manager for Flash Storage Systems User's Guide is available in the Oracle Flash Storage Systems Utilities Documentation Library.

Note: If the upgrade of EM cannot be performed rapidly and you temporarily require it to manage the FS1-2 running 6.2.7 or higher, you can follow the instructions below to disable TLS v1.1. Please be aware that disabling TLS v1.1 can introduce security risks.

Download the file enableDisableEM.sh.gz attached to this document.
Refer to <Document 2029847.1> FS System: How to Enable SSH Access to the Pilot to enable SSH on the FS1-2.
Use either scp or any other tool (ie: filezilla) to transfer the file into the active Pilot by using the FS1-2 public IP address.

Note: Refer to <Document 2046703.1> FS System: Passwords Associated with the Oracle FS1-2 Flash Storage System if you do not remember the default password.

Example using scp:

# scp enableDisableEM.sh.gz root@<Shared FS1-2 IP address>:/var/tmp
root@xxx.xxx.xxx.xxx's password:
enableDisableEM.sh.gz 100% 1672 1.6KB/s 00:00
#
Connect to the active Pilot by opening a SSH connection to the FS1-2 public IP address:

Note: This procedure only needs to be executed on the active Pilot.

Example:

# ssh -l root <Shared FS1-2 IP address>
Password:
Prepare the script "enableDisableEM.sh".

Example:

[root@pilot1 tmp]# cd /var/tmp
[root@pilot1 tmp]#
[root@pilot1 tmp]# gzip -d enableDisableEM.sh.gz
[root@pilot1 tmp]#

[root@pilot1 tmp]# chmod u+x enableDisableEM.sh
[root@pilot1 tmp]#
Execute the script "enableDisableEM.sh" to enable the EM access:

Note: A reboot is not required. However, you will need to re-enable EM access if you upgrade the release on the FS1-2.

Example:
[root@pilot1 tmp]# ./enableDisableEM.sh
Original File saved and necessary copies and modifications made.
Enabling EM Access
EM Access enabled
Restarting WebCLI service...
Stopping httpd-webcli: Stopped (0)
Starting httpd-webcli: [ OK ]
WebCLI restarted.
The current directory: /var/tmp
enableDisableEM.sh
Copying this script over to passive
enableDisableEM.sh 100% 4805 4.7KB/s 00:00
Running on Pilot 1 so calling Pilot 2 - the passive pilot
Call is on the passive pilot
Original File saved and necessary copies and modifications made.
Enabling EM Access
EM Access enabled <=== EM access enabled
[root@pilot1 tmp]#
If you need to disable the EM access, you can simply re-run the same script:

Example:
[root@pilot1 tmp]# ./enableDisableEM.sh
No work necessary
Disabling EM Access
EM Access disabled
Restarting WebCLI service...
Stopping httpd-webcli: Stopped (0)
Starting httpd-webcli: [ OK ]
WebCLI restarted.
The current directory: /var/tmp
enableDisableEM.sh
Running on Pilot 1 so calling Pilot 2 - the passive pilot
Call is on the passive pilot
No work necessary
Disabling EM Access
EM Access disabled <=== EM access disabled
[root@pilot1 tmp]#

Attachments

This solution has no attachment