Generating Network Performance Statistics for HyperScale X Nodes

Updated

Network performance statistics on the storage/private network for Commvault HyperScale X nodes in a storage pool can be obtained using the cv_net_perf.py script.

The script computes network performance statistics between pairs of storage pool nodes, where one node is configured as a server and another as client.

The script must be executed from one of the nodes in the storage pool. The script automatically identifies the the other nodes in storage pool and forms pairs and runs the tool on all the pairs, sequentially. Standard transfer size is 20GB.

Before You Begin

To obtain precise results, run the network performance tools when there are no backup jobs to the storage pool.

Procedure

  1. Logon to any one of nodes in the storage pool and navigate to the following folder:

    # cd /opt/commvault/MediaAgent
        
    
  2. Run the following command:

    # ./python3 cv_net_perf.py <option>
        
    

    <option> can be one of the following:

    • CvNetworkTestTool to run the command using Commvault network performance tool.

      Example:

      # ./python3 cv_net_perf.py CvNetworkTestTool
          
      
    • iperf3 to run the tool using using the linux native iperf3 command.

      Example:

      # ./python3 cv_net_perf.py iperf3
          
      

      Caution

      Do not run CvNetworkTestTool or iperf3 commands independently on the nodes while running the script. Any existing runs of CvNetworkTestTool or iperf3 will be killed.

Result

Note

The run time may vary from few minutes to hours depending on the write size, load and resources on the nodes.

  • The output is logged in the following folder:

    /var/log/commvault/Log_Files/CVFSPerfMon/

  • The output is logged using the following format:

    network_performance_<timestamp>.log

    For example:

    /var/log/commvault/Log_Files/CVFSPerfMon/network_performance_20221007081957.log

  • The SUMMARY section provides brief details of network throughput between nodes. (The rest of the log contains details of the parameters of the run and debug traces.)

Was this page helpful?