Link Test using IPERF in CLISH

Command Line Interface (CLISH) Access

Access to command line is provided via SSH protocol version 2.

To access CLISH user can use the “admin” identity.

From your machine you can use “putty” or any other preferred ssh client to connect to the device.

ssh -l admin <ip address>

Example :

ssh -l admin 169.254.1.1

Enter the password for user admin when prompted.

The default password for admin is “admin”, unless the password was changed by the user.

image

Iperf Test

Iperf is commonly used network tool for measuring throughput of a network.

cnWave provides iperf tool using the command line interface to measure the basic link and study the radio link parameters.

Note: This should not be considered as a performance throughput tool.

Iperf has server and client functionality and can create data streams between two devices in one or both directions.

IPERF SERVER

Login to the device where you want to run the server utility as mentioned above.

Note: The ssh session will not come back to CLISH in the server side, user must close the ssh session.

STEP 1: Kill any previous iperf sessions running.

CLISH> system iperf kill

STEP 2: Clear previous iperf results. This will erase all old results in the system.

CLISH> system iperf clear

After one second enter again to get to the CLISH prompt.

STEP 3: Run iperf server

CLISH> service iperf -s -i 1 -p 6000

image

The above session will make the iperf to wait for packets on port 6000.

The “-p” option is MUST so as to have multiple results and user can use any port up to 65535

IPERF CLIENT

Login to the device where you want to run the client utility as mentioned above.

STEP 1: Kill any previous iperf sessions running.

CLISH> system iperf kill

STEP 2: Clear previous iperf results. This will erase all old results in the system.

CLISH> system iperf clear

After one second enter twice to get the prompt again.

STEP 3: Find the remote end ip address.

CLISH>show breeze decision adj

> node-00.04.56.88.30.64

Neighbor Local Intf Remote Intf Metric Label NextHop-v4 NextHop-v6 Uptime Area

node-00.04.56.88.30.25 terra0 terra16 1 0 0.0.0.0 fe80::2004:56ff:fe88:3025 5h6m N/A

STEP 4: Running iperf client

Make sure the server is running before iperf client is run.

If the server is not running the iperf command will come out immediately.

CLISH> service iperf -c fe80::2004:56ff:fe88:3025%terra0 -i 1 -P 4 -t 10 -p 6000

Wait for 10 to 12s for the above command to complete.

STEP 5: Read result

CLISH>system iperf show

image

I noticed a small bug…
“system iperf clear” it seems to hang and i have to press enter again to get the prompt back it’s a small bug but annoying :slight_smile:

also after running clear “system iperf show” still shows a result not sure if thats expected result or not i thought it would be blank.

I was also testing the iperf yesterday it was working but today when i tried i’m getting

CLISH>service iperf -c fe80::2004:56ff:fe88:f8f8%terra0 -i 1 -P 4 -t 10 -p 6000
##Error Processing Command

CLISH>system iperf show
iperf3: error - unable to send control message: Bad file descriptor
iperf3: error - unable to send control message: Bad file descriptor
iperf3: error - unable to send control message: Bad file descriptor
iperf3: error - unable to send control message: Bad file descriptor

Hi
i did same command but the result is to small even though The link running on MCs 12