Running a typical trace

The following steps describe how to run a typical trace.

It is assumed that the trace system is reset for the type of trace that you want to run: SMB, Network, or Object. The examples use the SMB trace.

  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
    The response to this command displays the current settings from the trace configuration file. For more information about this file, see Trace configuration file.
  2. Clear the trace records from the previous trace of the same type:
    mmprotocoltrace clear smb
    This command responds with an error message if the previous state of a trace node is something other than DONE or FAILED. If this error occurs, follow the instructions in the Resetting the trace system section.
  3. Start the new trace:
    mmprotocoltrace start smb -c <clientIP>
    The following response is typical:
    Setting up traces
    Trace '5d3f0138-9655-4970-b757-52355ce146ef' created successfully for 'smb'
    Waiting for all participating nodes...
    Trace ID:           5d3f0138-9655-4970-b757-52355ce146ef
    State:              ACTIVE
    Protocol:           smb
    Start Time:         09:22:46 24/04/20
    End Time:           09:32:46 24/04/20
    Trace Location:     /tmp/mmfs/smb.20200424_092246.trc
    Origin Node:        ces5050-41.localnet.com
    Client IPs:         10.0.100.42, 10.0.100.43
    Syscall:            False
    Syscall Only:       False
    Nodes:
          Node Name:            ces5050-41.localnet.com
          State:                ACTIVE
          Node Name:            ces5050-42.localnet.com
          State:                ACTIVE
          Node Name:            ces5050-43.localnet.com
          State:                ACTIVE
    To display more status information, add the -v (verbose) option:
     mmprotocoltrace -v status smb

    If the status of a node is FAILED, the node did not start successfully. Look at the logs for the node to determine the problem. After you fix the problem, reset the trace system by following the steps in Resetting the trace system.

  4. 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.
  5. 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 'node1'
    Waiting for node 'node2'
    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'
    
    If you do not stop the trace, it continues until the trace duration expires. For more information, see Trace timeout.
  6. Look in the trace log files for the results of the trace. For more information, see Trace log files.