Documentation
Rate This Document
Findability
Accuracy
Completeness
Readability
SubmitClose

Creating a Network I/O Diagnosis Task

The tool supports network dialing tests, network load monitoring, packet loss diagnosis, and packet capture diagnosis for Ethernet NICs, providing reference data for locating network problems and optimizing network performance.

Prerequisites

At least one node has been installed successfully.

Creating a Network I/O Diagnosis and Analysis Task

  1. Click next to System Diagnosis.
  2. Set task parameters based on "Task Management" and Table 1.
    Figure 1 Creating a network I/O diagnosis task
    Table 1 Parameters for creating a network I/O analysis task

    Parameter

    Description

    Task Name

    Name of the task. The name must meet the following requirements:

    • Contain only letters, digits, and special characters (including @#$ %^&*()[]<>._-!-+ and spaces).
    • Contain 1 to 32 characters.

    Diagnosis Object

    Select Network I/O.

    Diagnosis Scenario

    Network I/O diagnosis scenario. The options are:

    • Network dialing test
    • Packet loss diagnosis
    • Packet capture
    • Network load monitoring
    NOTE:

    Select either network dialing test or packet loss diagnosis. Packet capture and network load can be selected together.

    Dialing Test Scenario

    Dialing test scenario to be diagnosed. The options are:

    • Connectivity
    • TCP
    • UDP

    IP Protocol Type

    This parameter is mandatory when Diagnosis Scenario is set to Network dialing test and Dialing Test Scenario is set to Connectivity.

    IP protocol type to be diagnosed. The options are:

    • IPv4
    • IPv6

    Node Information

    This parameter is mandatory when Diagnosis Scenario is set to Network dialing test and Dialing Test Scenario is set to Connectivity.

    • Task Node: Enter the IP address of the server where the task is executed.
    • Source IP Address (for IPv4): Enter the client IP address.
    • Target Server IP Address: Enter the IP address of the target server.
    • Source Network Port: This is required when an IPv6 address is used.
    NOTE:

    You can click to add a node or click to delete a node.

    Networking Parameters

    This parameter is mandatory when Diagnosis Scenario is set to Network dialing test and Dialing Test Scenario is set to TCP or UDP.

    • Server Task Node
    • Server IP Address
    • Server Port
    • Client Task Node
    • Client IP Address
    • Client Port
    • Client Network Port (for IPv6)

    Report Interval (ms)

    This parameter is mandatory when Diagnosis Scenario is set to Network dialing test and Dialing Test Scenario is set to TCP or UDP.

    Interval for sending dialing test reports. The value ranges from 100 to 10000, in milliseconds. The default value is 1000.

    Dialing Test Threshold

    This parameter is mandatory when Diagnosis Scenario is set to Network dialing test and Dialing Test Scenario is set to TCP or UDP.

    • Dialing Test Duration (s): The default value is 10. The value ranges from 1 to 60.
    • Total Length of Dialing Test Packets: The value ranges from 1 KB to 1,048,576 KB.
    • Number of Dialing Test Packets: The value ranges from 1 to 10000.

    (Optional) Dialing Test Packet Length (byte)

    This parameter is available when Diagnosis Scenario is set to Network dialing test.

    Length of a dialing test packet. The value ranges from 16 bytes to 65,507 bytes. The default value is 56 bytes.

    (Optional) Dialing Test Interval (ms)

    This parameter is available when Diagnosis Scenario is set to Network dialing test.

    Dialing test interval. The value ranges from 10 to 10000, in milliseconds. The default value is 1000.

    (Optional) Dialing Test Duration (s)

    This parameter is available when Diagnosis Scenario is set to Network dialing test.

    Dialing test duration. The value ranges from 1 to 60, in seconds. The default value is 10.

    (Optional) Fragmentation Policy

    This parameter is available when Diagnosis Scenario is set to Network dialing test and Dialing Test Scenario is set to Connectivity.

    The options are want, do, and dont.

    NOTE:

    do: Fragmentation is not allowed, even if the packet is discarded; want: Packet is fragmented when it is too large; dont: DF flag is not set.

    (Optional) TTL

    This parameter is available when Diagnosis Scenario is set to Network dialing test and Dialing Test Scenario is set to Connectivity.

    Packet lifetime. The value ranges from 1 to 255. The default value is 30.

    Collection Duration (s)

    This parameter is mandatory when Diagnosis Scenario is set to Network load.

    Duration of load monitoring. The value ranges from 2 to 300, in seconds. The default value is 10.

    Collection Interval (s)

    This parameter is mandatory when Diagnosis Scenario is set to Network load.

    Collection interval of load monitoring. The value ranges from 1 to 10, in seconds. The default value is 10.

    (Optional) Network Data Flow Statistics

    This parameter is available when Diagnosis Scenario is set to Network load.

    Enables or disables the network data traffic statistics function.

    NOTE:

    After this configuration item is enabled, key functions in the kernel network protocol stack are traced and analyzed in the collection phase, which occupies a large number of system resources and increases the network latency.

    This function is supported only by OSs with the kernel version 4.15.0 to 5.4.0 in the System Profiler compatibility list. The kernels of UOS 20 do not support this function.

    Server CPU Affinity

    This parameter is mandatory when Diagnosis Scenario is set to Network dialing test and Dialing Test Scenario is set to TCP or UDP.

    Configure the server CPU affinity and enter the CPU core ID.

    Client CPU Affinity

    This parameter is mandatory when Diagnosis Scenario is set to Network dialing test and Dialing Test Scenario is set to TCP or UDP.

    Configure the client CPU affinity and enter the CPU core ID.

    Dialing Test Bandwidth

    This parameter is mandatory when Diagnosis Scenario is set to Network dialing test and Dialing Test Scenario is set to TCP or UDP.

    Bandwidth for the dialing test. The unit is Mbit/s and Kbit/s.

    Dialing Test Packet Length (byte)

    This parameter is mandatory when Diagnosis Scenario is set to Network dialing test and Dialing Test Scenario is set to TCP or UDP.

    Total length of a dialing test packet.

    Dialing Test Packets

    This parameter is mandatory when Diagnosis Scenario is set to Network dialing test and Dialing Test Scenario is set to TCP or UDP.

    Number of dialing test packets to be sent.

    Number of Concurrent Connections

    This parameter is mandatory when Diagnosis Scenario is set to Network dialing test and Dialing Test Scenario is set to TCP or UDP.

    Number of concurrent connections during a dialing test. The default value is 1.

    Socket Buffer (byte)

    This parameter is mandatory when Diagnosis Scenario is set to Network dialing test and Dialing Test Scenario is set to TCP or UDP.

    Size of the socket buffer.

    MSS (byte)

    This parameter is available when Diagnosis Scenario is set to Network dialing test and Dialing Test Scenario is set to TCP.

    Maximum TCP fragment length. The value ranges from 88 to 1460 bytes, and the default value is 1460 bytes.

    Support Zero Copy

    This parameter is mandatory when Diagnosis Scenario is set to Network dialing test and Dialing Test Scenario is set to TCP or UDP.

    Indicates whether to support zero-copy data transmission.

    (Optional) Filter Criteria

    This parameter is optional when Diagnosis Scenario is set to Packet loss diagnosis.

    IP addresses and network adapter names to be filtered.

    Sampling Duration (s)

    This parameter is mandatory when Diagnosis Scenario is set to Packet loss diagnosis.

    Sampling duration for packet loss diagnosis. The value ranges from 1s to 300s, and the default value is 10s.

    (Optional) Sampling Frequency (ms)

    This parameter is mandatory when Diagnosis Scenario is set to Packet loss diagnosis and Sample Kernel Packet Loss Call Stack is enabled.

    Sampling frequency for packet loss diagnosis. The value ranges from 1 ms to 1000 ms, and the default value is 1 ms.

    (Optional) Size of the Collected File (MiB)

    This parameter is optional when Diagnosis Scenario is set to Packet loss diagnosis and Sample Kernel Packet Loss Call Stack is enabled.

    Size of the file to be sampled for packet loss diagnosis. The value ranges from 1 MiB to 1024 MiB, and the default value is 1024 MiB.

    Packet Capture Network Port

    This parameter is mandatory when Diagnosis Scenario is set to Packet capture.

    NIC for capturing network packets.

    Filter Criteria

    This parameter is mandatory when Diagnosis Scenario is set to Packet capture.

    • IP Protocol Type (optional): IP protocol type for packet capture. You can select more than one protocol.
    • IP1
    • Port1
    • IP2
    • Port2
    • Transfer Direction: specifies the transfer direction of the captured packets. The value can be Send, Receive, or Both.

    Packet Capture Duration (s)

    This parameter is mandatory when Diagnosis Scenario is set to Packet capture.

    Duration for capturing network packets. The value ranges from 1s to 300s, and the default value is 10s.

    Number of Captured Packets

    This parameter is mandatory when Diagnosis Scenario is set to Packet capture.

    Number of packets to be captured. The value ranges from 1 to 10000. The default value is 1000.

    File Size

    This parameter is mandatory when Diagnosis Scenario is set to Packet capture.

    Size of the packet capture file. The default value is 100. The value ranges from 10 to 1024.

    Number of Files

    This parameter is mandatory when Diagnosis Scenario is set to Packet capture.

    Number of files for packet capture. The default value is 1. The value ranges from 1 to 10.
  3. Click OK.

    You can click the icons next to the task name to perform the following operations:

    • : stops the analysis task. After an analysis task is stopped, the collected information will be deleted.
    • : restarts the analysis task. You can modify task parameter settings and restart an analysis task. This button is available when a task is canceled or fails.
    • : performs the analysis again. The analysis task is renamed and restarted.
    • : deletes the analysis task. After a task is deleted, all data of this task will be deleted. Exercise caution when performing this operation.
    • : changes the task or report name. The report naming rule is the same as that of a task.

    The collection and analysis task will not be interrupted if you exit or switch to another page.

    After being authenticated, you can log in to the system again to view the execution progress of an ongoing task or the analysis report of a completed task.

Parent topic: Network I/O Diagnosis