Skip to main content

network test-link run-test

Contributors
Suggest changes
PDFs

Test link bandwidth

Availability: This command is available to cluster administrators at the advanced privilege level.

Description

The network test-link run-test command runs a performance test between two nodes. The command requires a source node, Vserver, and destination address.

Before executing the network test-link run-test command, the network test-link start-server command must be run to start a server on the node hosting the destination LIF. After all tests to that node are complete the network test-link stop-server command must be run to stop the server.

The test results are stored non-persistently and can be viewed using the network test-link show command. Results include input parameters, the bandwidth achieved, and the date and time of the test.

Parameters

-node {<nodename>|local} - Node Name (privilege: advanced)

Use this parameter to specify the node which initiates the test.

-vserver <vserver> - Vserver (privilege: advanced)

Use this parameter to specify the Vserver to access the destination LIF. DC (Data Channel) Vserver option is available only in an ONTAP Select or Cloud Volumes ONTAP cluster. It is a special vserver that hosts LIFs that are used to mirror data aggregates to partner node.

-destination <Remote InetAddress> - Destination (privilege: advanced)

Use this parameter to specify the destination IP address.

Examples

The following example runs a test between the cluster LIFs, including the start and stop of the server side of the test:

cluster1::*> network test-link start-server -node node1

cluster1::*> network test-link run-test -node node2 -vserver Cluster -destination 172.31.112.173
Node: node2
     Vserver: Cluster
 Destination: 172.31.112.173
Time of Test: 4/22/2016 15:33:18
        MB/s: 41.2678

cluster1::*> network test-link stop-server -node node1
cluster1::*> network test-link show
Node                Vserver             Destination       Time of Test          MB/s
-----------------   -----------------   ---------------   -------------------   ------------
node2               Cluster             172.31.112.173    4/22/2016 15:33:18         41.2678