This article helps to investigate SMB or NFS access issues.
SMB Tracing
1. Before you start the trace, you can check the configuration settings for the type of trace that you plan to run
# mmprotocoltrace config smb 2. The response to this command displays the current settings from the trace configuration file. For more information about this file, see the “Trace configuration file”
3. Clear the trace records from the previous trace of the same type:
# mmprotocoltrace clear smb 4. This command responds with an error message if the previous state of a trace node is something other than DONE or FAILED.
5. If this error occurs, follow the instructions in the “Resetting the trace system ”
6. Start the new trace:
# mmprotocoltrace start smb -c 7. The following response is observed :
Trace ’3f36dbed-b567-4566-9beb-63b6420bbb2d’ created successfully for ’smb’ 8. Check the status of the trace to verify that tracing is active on all the configured nodes:
# mmprotocoltrace status smb 9. The following response is typical:
Trace ID: fcb7cb07-c45e-43f8-8f1f-2de50cf15062
State: Active
User ID: root
Protocol: smb
Start Time: 10:57:43 04/03/2016
End Time: 11:07:43 04/03/2016
Client IPs: 10.0.100.42, 10.0.100.43
Origin Node: ch-42.localnet.com
Syscall: False
Syscall Only:False
Nodes: Node Name: ch-41.localnet.com
State: ACTIVE
Trace Location: /tmp/mmfs/smb.20160304_105742.trc
Node Name: ch-42.localnet.com
State: ACTIVE
Trace Location: /tmp/mmfs/smb.20160304_105742.trc
Node Name: ch-43.localnet.com
State: ACTIVE
Trace Location: /tmp/mmfs/smb.20160304_105742.trc 10. If all the nodes started successfully, perform the actions that you want to trace. For example, if you are tracing a client IP address, enter commands that create traffic on that client.
11. Stop the trace:
# mmprotocoltrace stop smb The following response is typical. The last line gives the location of the trace log file:
Stopping traces Trace ’01239483-be84-wev9-a2d390i9ow02’ stopped for smb
Waiting for traces to complete
Waiting for node ’clusternode1’
Waiting for node ’clusternode2’
Finishing trace ’01239483-be84-wev9-a2d390i9ow02’
Trace tar file has been written to ’/tmp/mmfs/smb.20150513_162322.trc/smb.trace.20150513_162542.tar.gz 11. If you do not stop the trace, it continues until the trace duration expires.
12. Look in the trace log files for the results of the trace.
NFS Tracing
1. NFS tracing is achieved by increasing the log level, repeating the issue, capturing the log file, and then restoring the log level.
2. To increase the log level, use the command mmnfs configuration change LOG_LEVEL=FULL_DEBUG.
3. You can set the log level to the following values:
NULL, FATAL, MAJ, CRIT, WARN, EVENT, INFO, DEBUG, MID_DEBUG, and FULL_DEBUG.
NOTE: FULL_DEBUG is the most useful for debugging purposes. 4. After the issue is recreated by running the gpfs.snap command either with no arguments or with the --protocol nfs argument, the NFS logs are captured.
5. The logs can then be used to diagnose any issues.
6. To return the log level to normal, use the same command but with a lower logging level (the default is EVENT)
#IBMSofteware#spectrumscale#Softwaredefinedstorage#IBMSpectrumScale#softwaredefinedstorage#SpectrumScaleAuthentication#IBMSoftwareDefinedStorage