network

To verify the data transfer capabilities of your TCP/IP network devices, run the network test. This test gathers information about your wired devices and checks their connection speeds, bandwidths, and partitioning functions.

What the test covers

The network test checks devices that transfer data over a TCP/IP network. The test can check multiple connection speeds and bandwidths of wired devices based on the corresponding test, as listed in the following table:

The following table mentions different tests under the network test:

Ethernet test Description

1GigEthernet

The network test with added speed detection for 1 gigabit Ethernet connections.

10GigEthernet

The network test with added speed detection for 10 gigabit Ethernet connections.

20GigEthernet

The network test with added speed detection for 20 gigabit Ethernet connections.

25GigEthernet

The network test with added speed detection for 25 gigabit Ethernet connections.

40GigEthernet

The network test with added speed detection for 40 gigabit Ethernet connections.

50GigEthernet

The network test with added speed detection for 50 gigabit Ethernet connections.

100GigEthernet

The network test with added speed detection for 100 gigabit Ethernet connections.

200GigEthernet

The network test with added speed detection for 200 gigabit Ethernet connections.

Ethernet

If the Ethernet test is listed in your local test plan, it indicates that the test suite did not recognize the speed of that device. Check the connection before attempting to test that particular device.

RHEL version supported
  • RHEL 8
  • RHEL 9
  • RHEL 10
What the test does

The test runs the following subtests to gather information about all the network devices:

  1. The bounce test on the interface is conducted using nmcli conn up and nmcli conn down commands.
  2. If the root partition is not NFS or iSCSI mounted, the bounce test is performed on the interface. Additionally, all other interfaces that will not be tested are shut down to ensure that traffic is routed through the interface being tested.
  3. If the root partition is NFS or iSCSI mounted, the bounce test on the interface responsible for the iSCSI or NFS connection is skipped, and all other interfaces, except for the one handling the iSCSI or NFS connection, will be shut down.
  4. A test file gets created at location /dev/urandom, and its size is adjusted with the speed of your NIC.
  5. TCP and UDP testing - The test uses iperf tool to:
    1. Test TCP latency between the test server and host under test. The test checks if the system runs into any OS timeouts and fails if it does.
    2. Test the bandwidth between the test server and the host under test. For wired devices, it is recommended that the speed is close to the theoretical maximum.
    3. Test UDP latency between the test server and host under test. The test checks if the system runs into any OS timeouts and fails if it does.
  6. File transfer testing - The test uses SCP to transfer a file from the host under test to the remote system or test server and then transfers it back to the host under test to check if the transfer works properly.
  7. ICMP (ping) test - The script causes a ping flood at the default packet size to ensure nothing in the system fails (the system should not restart or reset or anything else that indicates the inability to withstand a ping flood). 5000 packets are sent and a 100% success rate is expected. The test retries 5 times for an acceptable success rate.
  8. Finally, the test brings all interfaces back to their original state (active or inactive) when the test is executed.
Preparing for testing wired devices

You can test as many network devices as you want in each test run.

Before you begin:

  • Ensure to connect each device at its native (maximum) speed, or else the test fails.
  • Ensure that the test server is up and running.
  • Ensure that each network device has an IP address assigned either statically or dynamically via DHCP.
  • Ensure that multiple firewall ports are open, for the iperf tool to run TCP and UDP subtests.
Note

By default, ports 52001-52101 are open. If you want to change the default ports, update the iperf-port and total-iperf-ports values in the /etc/rhcert.xml configuration file. For example, server listener-port="8009", iperf-port="52001", total-iperf-ports="100".

If the firewall ports are not open, the test prompts to open the firewall ports during the test run.

Partitionable networking

The test checks if any of the network devices support partitioning, by checking the data transfer at full speed and the partitioning function.

Running the test based on the performance of NIC:

  • If NIC runs at full speed while partitioned then, configure a partition with NIC running at its native speed and Perform the network test in that configuration.
  • If NIC does not run at full speed while partitioned then, run the test twice - first time, run it without partitioning to see the full-speed operation, and the second time, run it with partitioning enabled to see the partitioning function.
Note

Red Hat recommends selecting either 1Gb/s or 10Gb/s for your partitioned configuration so that it conforms to the existing network speed tests.

Running the test
The network test is non-interactive. Run the following command and then select the appropriate network test name from the list that displays.
rhcert-run
Manually adding and running the test
To manually add and run an Ethernet test, use the commands listed in the following table:
Speed Type Command to manually add Ethernet Test Command to Manually run Ethernet Test

1GigEthernet

rhcert-cli plan --add --test 1GigEthernet --device <device name> rhcert-cli run --test 1GigEthernet --server <test server IP addr>

10GigEthernet

rhcert-cli plan --add --test 10GigEthernet --device <device name> rhcert-cli run --test 10GigEthernet --server <test server IP addr>

20GigEthernet

rhcert-cli plan --add --test 20GigEthernet --device <device name> rhcert-cli run --test 20GigEthernet --server <test server IP addr>

25GigEthernet

rhcert-cli plan --add --test 25GigEthernet --device <device name> rhcert-cli run --test 25GigEthernet --server <test server IP addr>

40GigEthernet

rhcert-cli plan --add --test 40GigEthernet --device <device name> rhcert-cli run --test 40GigEthernet --server <test server IP addr>

50GigEthernet

rhcert-cli plan --add --test 50GigEthernet --device <device name> rhcert-cli run --test 50GigEthernet --server <test server IP addr>

100GigEthernet

rhcert-cli plan --add --test 100GigEthernet --device <device name> rhcert-cli run --test 100GigEthernet --server <test server IP addr>

200GigEthernet

rhcert-cli plan --add --test 200GigEthernet --device <device name> rhcert-cli run --test 200GigEthernet --server <test server IP addr>

400GigEthernet

rhcert-cli plan --add --test 400GigEthernet --device <device name> rhcert-cli run --test 400GigEthernet --server <test server IP addr>

Replace <device name> and <test server IP addr> with the appropriate value.

Run time
The network test takes about 2 minutes to test each PCI Express (PCIe)-based, gigabit, wired Ethernet card, and the required Supportable test adds about a minute to the overall run time.