You can manage mapping inconsistencies by performing several tasks.
About this task
If a user cannot access a file that should be accessible, there are several possible reasons:
- You granted access recently and the WAFL credential cache does not have the new mapping entry.
You can determine mapping inconsistencies between recently granted rights and the WAFL credential cache by comparing CIFS credential mappings. You can display mapping results for the user’s UNIX name or user’s Windows name.
- The NFS client could not obtain CIFS credentials.
You can determine whether an NFS client can perform a CIFS login to the storage system by tracing CIFS logins.
- Depending on the NFS client, it might be necessary to wait for the NFS attribute cache to time out before changes to the CIFS credential take effect.
Steps
- Display the current CIFS credential mapping of a UNIX name by entering the following command: wcc -s uname
uname is the Windows user name. You can further narrow the specification of the user by adding -i, followed by the IP address of the host that the user is on. You can get more detailed information by appending -v to the command line. You can have up to three instances of the -v option (-vvv) per command; each instance represents an increasing level of detail.
- Note the CIFS credential information.
- To display information about all connected users, enter the following command: cifs sessions -s
- Locate the user’s information in the output.
- Compare the two CIFS credential mappings.
- If the CIFS credential mappings are different, disconnect the client by entering the following command: cifs terminate workstation
Result
When the client reconnects, the CIFS credential mappings will be correct.