MaxRep: MaxRep Engine status is Unknown After Upgrading FS1-2 to Version 6.2.11 or Higher

Asset ID:	1-72-2192488.1
Update Date:	2017-02-26
Keywords:

Solution Type Problem Resolution Sure

Solution 2192488.1 : MaxRep: MaxRep Engine status is Unknown After Upgrading FS1-2 to Version 6.2.11 or Higher

Applies to:

Pillar Axiom Replication Engine (MaxRep) - Version 3.0 to 3.0 [Release 3.0]
Information in this document applies to any platform.

Symptoms

After completing the FS1-2 software upgrade to release 6.2.11 or higher, the status of the MaxRep Engine may change to Unknown. In the FS1-2 GUI navigate to the "System" tab -> click "Status Summary" from the left menu. In the main page under "Replication Engines" the Service Status and Agent Status is Unknown.

A fix for this issue is targeted for MaxRep release 3.0.8.008.

The MaxRep Engine will keep trying to log in, in the server.log file on the Pilot, Pacman will log the IP address of the MaxRep Engine and its use of a disallowed protocol. The error message will look like the following:

ERROR 2016-10-11 16:07:09,049 com.pillardata.util.log.Logger.logErrorOrDebugWithThreadDump(Logger.java:328)
NettyServerWorker-1[New I/O worker #1] - In NetworkIoHandlerEx, exception occurred for
[id: 0x189229ff, /10.79.178.157:48489 => /10.79.185.38:26012].
javax.net.ssl.SSLHandshakeException: Client requested protocol TLSv1 not enabled or not supported
at sun.security.ssl.Handshaker.checkThrown(Unknown Source)
at sun.security.ssl.SSLEngineImpl.checkTaskThrown(Unknown Source)
at sun.security.ssl.SSLEngineImpl.readNetRecord(Unknown Source)
at sun.security.ssl.SSLEngineImpl.unwrap(Unknown Source)
at javax.net.ssl.SSLEngine.unwrap(Unknown Source)

10.79.178.157:48489 => /10.79.185.38:26012 indicates the IP address 10.79.178.157 TCP port [we don't care about the client port] 48489 is attempting to connect to the share FS1-2 IP address 10.79.185.38 TCP port 26012

Cause

FS1-2 software release 6.2.11 and higher no longer supports TLSv1.0, only TLSv1.1 or higher. The issue will cause MaxRep Engine not to automatically download the new pcli version. This affects MaxRep Engines on releases above 3.0.1 and below release 3.0.8

Solution

Use the following steps to workaround this issue.

1. SSH into the MaxRep Engine host console as root user. The default password can be found in <Document 2046703.1> FS System: Passwords Associated with the Oracle FS1-2 Flash Storage System

2. On the MaxRep Engine host console, cd to /usr/local/InMage/Vx/bin

3. Type 'ls -l' to display the registered FS1-2 IP address as shown in the example below.

4. Rename the folder. For example if the registered FS1-2 IP is 10.0.0.2:

# cd /usr/local/InMage/Vx/bin/
# ls -l
drwxrwxrwx 3 root root 4096 Dec 4 2015 10.0.0.2
# mv 10.0.0.2 backup_10.0.0.2
# ls -l
drwxrwxrwx 3 root root 4096 Dec 4 2015 backup_10.0.0.2

5. Log into the MaxRep UI to Re-Discover the FS1-2 Storage. In the MaxRep UI navigate to "Settings" tab -> from the left menu click "Manage Oracle Storage".

6. In the main page click on link "Re-Discover" for the registered FS1-2 Storage.

7. Wait for the discovery to complete, click on "History" link and verify the Oracle Storage Discovery Status is a Success.

NOTE: If the Re-Discover does not complete successfully, please use the fscli utility to verify that the account can log into the FS1-2 successfully with the following command:
fscli login -u replication -oracleFS <FQDN or IP address of FS1-2>

For the default replication user account password please refer to Document 2046703.1 FS System: Passwords Associated with the Oracle FS1-2 Flash Storage System

Log back into the FS1-2 GUI to check MaxRep Engine status. In the FS1-2 GUI navigate to "System" tab -> click "Status Summary" from the left menu. In the main page under "Replication Engines" the Service Status should be Normal and Agent Status should be All Communicating. Please contact Oracle Support if you have any questions.

References

<BUG:23723000> - CAAXM085:SYSTEM IN WARNING AS MAXREP ENGINE STATUS UNKNOWN IN GUI AFTER NDU

Attachments

This solution has no attachment