Dell NX3610 Riding Toy User Manual


 
CIFS Locking Inconsistency
Description CIFS service is interrupted due to CIFS interlocking issues.
Cause CIFS client interlocking scenarios.
Workaround System recovers itself automatically, issuing the above event when recovered.
CIFS Maximum Connections Reached
Description Maximum number of CIFS connections per NAS controller is reached.
Cause Each NX3600 appliance is limited to 200 concurrent CIFS connections and each
NX3610 and FS8600 is limited to 1500 connections.
The system is in an optimal state and the number of CIFS clients accessing one of
the controllers reaches the maximum. In such a scenario, consider adding another
NAS appliance.
The system is in optimal state but the clients are significantly unbalanced between
NAS controllers. In this case, rebalance the clients using the NAS Manager.
The system is in degraded state (one or more NAS controllers are down) and the
CIFS clients are left over on the remaining controller. In this case, wait until the
system returns to optimal or decrease the number of CIFS clients in the system.
Workaround If all NAS controllers are in optimal mode, the connections are divided between both
of them.
CIFS Share Does Not Exist
Description Client attempts to connect to an inexistent share.
Cause
Spelling mistake on client side.
Accessing the incorrect server.
Workaround List the available NAS shares and verify that all shares are displayed and nothing has
changed unintentionally.
Verify that you can access the problematic share using a Windows client:
1. Click Run.
2. Enter the client access VIP and share name: \\<Client_VIP>\<CIFS_share_name>
CIFS Path Share Not Found
Description Client accessed a share which refers to an inexistent directory in the NAS container.
Cause
The NAS system is restored from a backup or remote replication. During restore
time, the directory structure is not complete and a few directories may not exist.
Communicate the status and wait for the restore process to complete.
A client with authorization, deletes or alters a directory that is mounted by another
client.
If multiple users are accessing the same dataset, it is recommended that you apply
a strict permission scheme to avoid such conflicts.
Workaround List all available shares on the NAS and identify the problematic share. It must have an
indication that it is not accessible.
1. Restore the problematic path from a backup.
174