Sun ZFS Storage 7420
 
Sun Storage 7110 Unified Storage System
 
Oracle ZFS Storage ZS3-2
 
Sun Storage 7210 Unified Storage System
 
Oracle ZFS Storage ZS4-4
 
Sun Storage 7410 Unified Storage System
 
Sun Storage 7310 Unified Storage System
 
Sun ZFS Storage 7120
 
Oracle ZFS Storage ZS3-4
 
Sun ZFS Storage 7320
 
Oracle ZFS Storage Appliance Racked System ZS4-4
 
Oracle ZFS Storage ZS3-BA
 

PLA-Support>Sun Systems>DISK>ZFS Storage>SN-DK: ZS
 
Tools>Primary Use>Configuration
 

Updating  the password of the ZFSSA user for the SRA connection customer may  not be  to connect to  Oracle ZFS Storage Appliance 
discovery may fail   JAVA_OUTPUT: ' DiscoverArrays.aksh' 不是內部或外部命令、可執行的程式或批次檔。

In this Document

Symptoms

Changes

Cause

Solution

References

Created from <SR 3-13009657278>

Applies to:

Symptoms

Unable to connect with the Oracle ZFS Storage Appliance when array discovery is initiated from the VMware vCenter SRM.

Verify the following:

• The Oracle ZFS Storage Appliance DNS hostname or IP address is correctly specified.
• Login credentials (including the password) are valid for the designated SRA account.
• The designated SRA account has been established with the correct roles and privileges.
• Protected and recovery storage servers are running the correct Oracle ZFS Storage Appliance software release.

Unable to discover replicated devices when array discovery is initiated from the VMware vCenter SRM.

Verify the following:
• The VMware vCenter SRM Rescan Array operation is performed after any protected or recovery storage system reconfiguration.
NOTE: Hardware (including network hardware) configuration changes, changes in the replication configuration, and upgrading of Oracle ZFS Storage Appliance software are some of the events that require a Rescan Array operation.

SRA will give a specific error with a defined error code. To debug the issue with the error code, refer to the following table.

The table also lists specific SRM errors returned because of configuration issues.

Problem: Authentication error Error code: 1001
This is an authentication error. To fix it, verify the following:
• The Oracle ZFS Storage Appliance DNS hostname or IP address is correctly specified.
• Login credentials (including the password) are valid for the designated SRA account.

Problem: Possible plug-in corruption Error code: 1002
This error refers to a missing SRA script. If you get this error:
• Check if any of the installed files have been modified.
• Try re-installing the plug-in.

Uninstalling the Oracle ZFS Storage Appliance SRA

To remove the Oracle ZFS Storage Appliance SRA for VMware vCenter SRM, use the Windows Add/Remove Programs feature to launch the uninstall program for the SRA.

The designated SRA account has been established with the correct roles and privileges.

Protected and recovery storage servers are running the correct Oracle ZFS Storage Appliance software release (2013.1)

VMWARE SRM with ZFS SRA Error after changing  ZFSSA SRA account password

SRM discovery error as shown.

But SRA LOG seems as below.

Changes

The only change made was to altering the  Credentials of the ZFSSA user for the SRA connection.

Cause

Usage of  Special characters  "&" ,  "~" ,"`", "!"  character in the password will cause this error during SRA configuration.

The error is picked up from SRM. SRA plugs is installed on the vmnode/server such that ZFSSA appliance are managed via VMware vCenter SRM.

Usage of the SRA occurs entirely within the VMware vCenter SRM application.

Solution

Check 1.
======
If the issue has occurred after changing the ZFSSA password, then reverting back to the older password should resolve the issue ?

If not The new password is somehow not respected my the clients/Vmservers/nodes.

The VMware vCenter SRM Rescan Array operation is performed after any protected or recovery storage system reconfiguration.

Verify the Oracle ZFS Storage Appliance is operating normally.

Verify in the VMware vCenter SRM log that the SRA operation is indeed at fault.  Take assistance from VmWare Administrator Warranted

Verify the Oracle ZFS Storage Appliance management URL and port are valid. Take  <<<Check with Onsite System Admin Needed>>>

What is the SRM timeout.
By default, the CommandTimeout is set to 300 seconds from the
VMware vCenter Site Recovery Manager at.\VMware vCenter Site Recovery Manager\config\vmware-dr.xml.
Minimum recomended is 600 to 900 seconds.

From ZFSSA Side :

Action Plan To Resolve

As per the Guide Customer should be 2013.1 or Later.

The SRA must be plugged into VMware vCenter Site Recovery Manager 5.1.x, 5.5.x, 5.8.x or 6.0.x.

If VMware vCenter Site Recovery Manager 6.0.x is used, Java 7 or later must be installed  on the SRM servers.
Please restart the servers after installation of Java.

VMware vCenter and VMware vCenter Site Recovery Manager must be installed on the same host.

Oracle ZFS Storage Appliance cluster heads must be in a healthy cluster state during initial discovery of Oracle ZFS Storage Appliances

SRA assumes by default that cluster heads are in a healthy state. If any head fails, and is taken over by the other head,  manual intervention by the SRM administrator will be required.
For more details, read the section "Preparing for Discovery'

NOTE: IN MY CASE ALL THE ABOVE WAS DONE STILL CUSTOMER WAS FACING DISCOVERY ERROR.

After changing the password of the ZFSSA user for the SRA connection,  customer would need to edit the existing array manager to fill the new password  into the configuration.

To do so, please refer to the following VMware documentation:

Edit Array Managers

https://pubs.vmware.com/srm-55/topic/com.vmware.srm.install_config.doc/GUID-9209F20B-40DE-4D97-A8E8-EE3AE9488765.html

After doing that, a rescan of that specific array manager is required.   Rescan Arrays to Detect Configuration Changes

https://pubs.vmware.com/srm-55/topic/com.vmware.srm.install_config.doc/GUID-5C390B19-7380-42F1-B0BD-DD3B424A1C53.html

Special Note: SRA installations to version 5.1.  carries resolution  several compatibility issues, and added a few useful enhancements. So its a must all customer gets their version upgraded to 5.1. Version 5.1 could work properly on OS 8.4 and above.

RESOLUTION: DO NOT USE SPECIAL CHARACTERS SUCH AS  &,!,`,~#@ AS PASSWORD 

Although “&” is acceptable during the AK password creation, it cannot work correctly in the SRA.

The next update of SRA admin guide and/or release notes will include this issue.

References

This solution has no attachment