Collecting network trace

System Administrator Guide for Virtual Storage Platform E Series

Version
93-07-0x
Audience
anonymous
Part Number
MK-97HM85028-18

If an abnormal event occurs on a network connecting to the SVP, you can use the network trace collection tool to capture the packets to and from the SVP. The network trace collection tool is supported by the following SVP firmware versions:
  • 93-06-22 or later
  • 93-06-02 to 93-06-20
  • 93-05-05 to 93-05-20
CAUTION:
  • When you are asked by maintenance personnel to collect network trace, you can agree with collecting network trace and sending the collected information to maintenance personnel. If you do not agree with this, contact maintenance personnel.

    Note that information about all packets to and from the SVP through the network is collected while this tool is running. Be careful when handling collected information.

  • While the network trace collection tool is running, the network interface card (NIC) link on the SVP might be momentarily down. There is no problem with this link-down event because it is caused by the netsh trace command (Windows standard command) that is used internally by the tool.
  • Do not perform other maintenance operations while using the network trace collection tool.
  • You must be able to reproduce the abnormal event on the network while the network trace collection tool is running. Make sure that you can reproduce the event on the SVP before running the tool. If you are not able to reproduce the event, contact maintenance personnel.
  • You must have 8 GB of capacity for storing the network trace and dump files that are output by the dump tool.
  1. On the SVP, start a Windows command prompt as Administrator.
  2. Move the current directory to the folder where the tool is available.
    Example: <SVP-root-directory>\DKC200\mp\pc
  3. Run the network trace collection tool (GetNetTrace.bat) and specify the output destination of the network trace and dump files.
    For example, to store the network trace and dump files to C:\Result_934000600001, enter the following command to run the tool:
    GetNetTrace.bat C:\Result_934000600001
    Note:
    • A space is required between GetNetTrace.bat and the output destination.
    • You cannot specify a folder under a network drive as the output destination.
    • Do not click on or close the command prompt window while the tool is running. If you accidentally close the window, restart the SVP.
    • While the tool is running, Executing… is displayed in the command prompt.

    When the message Do you want to stop the network tracing session?(Y): is displayed, do not respond to this message until after you have reproduced the network event.

  4. Reproduce the network event.
  5. After the network event has been reproduced, stop the network tracing session by entering Y (uppercase) in response to the message Do you want to stop the network tracing session?(Y):.
    CAUTION:
    You must stop the network tracing session soon after the network event has been reproduced. If the tool remains running for one hour or more after the network event was reproduced, the network trace might be lost.
    When you stop the network tracing session, the dump tool automatically starts, collects the dump files, and stops. When the dump tool stops, Network Trace tool END. is displayed in the command prompt.
  6. Confirm that the following files were output to the specified destination folder:
    • SVP_NetTrace.etl: Network trace log
    • SVP_NetTrace.cab: Log for related information regarding network trace log. This file might not be output.
    • hdcp.tgz: Dump file
    • zSv_AutoDump.log: Log file of the dump tool
    • DumpResult.txt: Collection results file

    In some cases the dump tool might fail to collect files due to an OS problem. If these result files were not output, you can collect the dump files manually. For details, see Collecting dump files manually.

  7. Close the command prompt.
  8. Send all files output by the tool to maintenance personnel.