Oracle ZFS Storage Appliance Racked System ZS5-4
 
Sun ZFS Storage 7320
 
Oracle ZFS Storage ZS5-4
 
Oracle ZFS Storage Appliance Racked System ZS4-4
 
Oracle ZFS Storage ZS3-2
 
Oracle ZFS Storage ZS3-4
 
Oracle ZFS Storage ZS5-2
 
Sun ZFS Storage 7420
 
Oracle ZFS Storage ZS4-4
 
Sun ZFS Storage 7120
 

PLA-Support>Sun Systems>DISK>ZFS Storage>SN-DK: 7xxx NAS
 

Oracle ZFS Storage may deny access to SMB share from some interfaces after upgrading to 8.7 or later.

Applies to:

Symptoms

Customers with Oracle ZFS Storage Appliance (ZFSSA) in clustered configuration may be denied access to SMB shares if the access is through the IP address owned by the peer node. The symptom was first observed in cluster configurations, however, the access issues to SMB shares is observed also in standalone configurations.

When the problem occurs, messages similar to the following will be observed in the log. (/var/ak/logs/debug.sys)

The above message can be verified by generating a support bundle and its content.

Please see the "Solution" section of this document for further details.

Changes

This issue can occur in the following releases:

ZFSSA Platform

• 2013.1.7.0 (Version string ak-2013.06.05.7.0) or later.

Solaris platforms are not impacted by this issue. The feature is unique to ZFSSA Platform.

Cause

BUG:27046617 - UNABLE TO ACCESS THE SHARE AFTER TAKEOVER DUE TO ASN VERIFY
BUG:22870185 - SMB SERVER SHOULD NOT MIX INTERFACES AND POOLS OWNED BY DIFFERENT NODES.

Solution

Until a final fix is available, the Workaround to this issue is as follows:

Verifying The Symptom

In order to verify the symptoms, there are two methods that can be used:

(a) Use a ZFSSA workflow to check if the problem exists.
(b) Generate a support bundle, extract the file and view debug.sys file.

Running a ZFSSA Workflow

If you choose to use the workflow (attached below), please follow the steps below:

(1) Please upload the attached workflow.
(2) Click on the uploaded workflow to execute.
(3) Provide your email address and SR number for the record.
(4) After it completes, check the audit log under Maintenance -> Log -> Audit.
You will see either one of the messages.

• A 'denied access' message was found.  This appliance is affected by bug 22870185 and 27380040.  Please contact Oracle Support.
• No 'denied access' messages found.  You are not affected by this issue.

If you are asked to contact support, please reach us by opening a Service Request.

Verifying The Log File in Support Bundle

If you choose to check the log file in the support bundle, please follow the step below:

Generate the support bundle, then once your ZFSSA finishes the generation of the support bundle and start uploading, then cancel the upload. Please download the support bundle and extract the bundle locally.

If you are a Solaris/Linux user, please use the following command to extract:

For example, you will run something like below.

After extraction, please check the content of logs/debug.sys to see if the message such as below exists.

If you find the message similar to the above example, it is likely the system is affected by this issue.  Please reach us by opening a Service Request.

Workaround For Clustered Configuration

(a) Check the status of the cluster and the owners of the network interfaces by running commands below.

(Status of Cluster)

(Owners of Network Interfaces)

Check the OWNER column. If you have an empty interface and TYPE is 'singleton', it would cause the access issue that is described here.

(b) If you have OWNER names against all interfaces, a cluster fail back will resolve the problem.

(c) If you have network interfaces whose TYPE is 'singleton' and missing OWNER names, then the network interfaces must be recreated.

Workaround for Stand-alone Configuration

If you have a problem in a stand-alone configuration, network interfaces must be recreated.

If you have any questions or have difficulties resolving the problem, please contact Oracle Support.

Resolution

A final resolution for this issue is pending completion. Also see Service Alert <Document:2370372.1> for more information and updates on the Resolution to this issue.

References

This solution has no attachment