Inspecting Network Performance

To use this API, you must ensure that the iperf utility is installed on all cluster hosts. Run the appropriate commands from the list below for your operating system. You must run the commands on all hosts and run them as the root user.

• Ubuntu/Debian:

  Run the following command on all cluster hosts:

  apt-get install iperf3

• SLES 12:
  1. Add the SLES 12 repository that contains iperf package. Note that the iperf3 package is named iperf on SLES 12.

     See https://software.opensuse.org/download.html?project=network%3Autilities&package=iperf.

  2. Run the following command on all cluster hosts:

     zypper addrepo https://download.opensuse.org/repositories/network:utilities/SLE_12_SP3/network:utilities.repo
     zypper refresh
     zypper install iperf

• RHEL 6.8/6.9/6.10

  For RHEL 6.8, 6.9, or 6.10, the iperf3 package is part of the EPEL repository.

  1. Enable the EPEL repository for RHEL 6:

     https://fedoraproject.org/wiki/EPEL#Quickstart

  2. Run the following command on all cluster hosts:

     yum install https://dl.fedoraproject.org/pub/epel/epel-release-latest-6.noarch.rpm
     yum install iperf3

• RHEL 7.2/7.3

  The iperf3 package is not available in the base repository nor the EPEL repository.

  1. Install iperf-3.1.3 from the official iperf website: https://iperf.fr/iperf-download.php#fedora
  2. Run the following command on all cluster hosts:

     yum install https://iperf.fr/download/fedora/iperf3-3.1.3-1.fc24.x86_64.rpm

• RHEL 7.4 or higher

  For RHEL 7.4 and higher, the iperf3 package is part of the base repository.

  Run the following command on all cluster hosts:

  yum install iperf3

1. Log in to the Cloudera Manager Admin Console as a user with the Full Administrator role.
2. Click Support > API Explorer.

   The Swagger interface displays.

3. Click ClouderaManagerResource.
4. Click POST /cm/commands/clustersPerfInspector.

   The interface for the PerfInspector command displays.

5. In the Parameters section, copy the following JSON code into the body text box.

   {
     "sourceCluster": "<SourceClusterName>",
     "targetCluster": "<TargertClusterName>",
     "pingArgs": {
       "pingTimeoutSecs": 10,
       "pingCount": 10,
       "pingPacketSizeBytes": 56
     },
     "bandwidthArgs": {
       "runBandwidthDiagnostics": true,
       "bandwidthTimeoutSecs": 10
     },
     "policyType": "QUICK"
   }

6. Replace the <SourceClusterName> and <TargertClusterName> arguments with the names of the clusters you want to inspect.
7. Optionally, set the values of the pingArgs arguments as needed.
8. Optionally, set the value of the bandwidthTimeoutSecs argument. A lower value will allow the inspector to inspect more hosts within the two minute limit, but will return less accurate results.
9. Click the Try it out! button.
10. In the Cloudera Manager Admin Console, click the Running Commands Icon () in the upper-right of the screen.

    If the command is still running, click the Clusters Performance Inspector link. If the command has finished, click the All Recent Commands link and then click the Clusters Performance Inspector link.

    The Clusters Performance Inspector Command page displays.

11. Click the second group labeled Execute <N> steps in parallel.
    
    
    
    

    A grouping displays for each host in the source cluster.

12. To view bandwidth data for each host in the source cluster:
    1. Click the Open in New Tab icon () located to the left of the host URL.
       
       
       
       

       The command details page for the host opens.

    2. Click the Download button.
       A JSON file with the bandwidth results for the host in the target cluster displays. For example:

       {
           "targetHostsNetStats": [
               {
                   "avgLatencyMillisecs": 0.408, 
                   "bwSentBitsPerSecond": 1035665000.0, 
                   "packetLossPercent": 0.0, 
                   "success": true, 
                   "maxLatencyMillisecs": 0.611, 
                   "hostName": "sales-storage-4.prod.myco.com", 
                   "minLatencyMillisecs": 0.299, 
                   "bwReceivedBitsPerSecond": 1033526000.0, 
                   "mdevLatencyMillisecs": 0.082
               }
           ]
       }

       In this JSON file:

       • hostName is the host in the target cluster that was tested.
       • bwSentBitsPerSecond is the results of the send bandwidth test.
       • bwReceivedBitsPerSecond is the results of the receive bandwidth test.
    3. Repeat the above steps to view bandwidth data for each source host.