No relevant resource is found in the selected language.

This site uses cookies. By continuing to browse the site you are agreeing to our use of cookies. Read our privacy policy>Search

Reminder

To have a better experience, please upgrade your IE browser.

upgrade

HUAWEI CLOUD Stack 6.5.0 Alarm and Event Reference 04

Rate and give feedback:
Huawei uses machine translation combined with human proofreading to translate this document to different languages in order to help you better understand the content of this document. Note: Even the most advanced machine translation cannot match the quality of professional translators. Huawei shall not bear any responsibility for translation accuracy and it is recommended that you refer to the English document (a link for which has been provided).
ALM-1200076 Trunk Port Packet Loss

ALM-1200076 Trunk Port Packet Loss

Description

This alarm is generated when the packet loss rate of the physical network port (Trunk port) reaches the percentage configured in the alarm configuration.

Attribute

Alarm ID

Alarm Severity

Auto Clear

1200076

Major

Yes

Parameters

Name

Meaning

Fault Location Info

  • host_id: specifies the ID of the host for which the alarm is generated.
  • trunk_name: specifies the name of the trunk for which the alarm is generated.

Additional Info

  • hostname: specifies the name of the host for which the alarm is generated.
  • DropRate: specifies the packet loss rate of the alarm.
  • Threshold: specifies the threshold for generating an alarm.

Impact on the System

Service data packet loss occurs, or the network is disconnected.

Possible Causes

  • Network I/O reaches the upper limit.
  • The CPU resources used for forwarding are insufficient.
  • Network configuration is incorrect.

Procedure

  1. Log in to the FusionSphere OpenStack web client.

    For details, see Logging In to the FusionSphere OpenStack Web Client (ManageOne Mode).

  2. On the Summary page, obtain the management IP address of the host in the OM IP Address column based on the host ID or host name in the alarm additional information.
  3. Use PuTTY to log in to the host for which the alarm is generated using the management IP address of the host.

    The default user name is fsp. The default password is Huawei@CLOUD8.

    The system supports both password and public-private key pair for identity authentication. If the public-private key pair is used for login authentication, see detailed operations in Using PuTTY to Log In to a Node in Key Pair Authentication Mode.

  4. Run the following command and enter the password of user root to switch to user root:

    su - root

    The default password of user root is Huawei@CLOUD8!.

  1. Obtain the name of the abnormal port based on the trunk port name in alarm information (If the port name is ethx, no ports are bound to a bond). Run the ip link | grep Port name command to query port information and check whether the command output is empty.

    • If yes, the abnormal port is on the user-mode bridge. In this case, go to 6.
    • If no, the abnormal port is on the kernel-mode bridge. In this case, go to 7.

  2. Run the following command to query the port status:

    ovs-vsctl get interface port_name link_state

    • If the connection is abnormal, remove and insert the network cable.
    • If the connection is normal, run the following command to collect packet loss information and then go to 9.

      Run the ovs-vsctl iface-to-br port_name command to obtain the bridge name.

      Run the ovs-ofctl dump-ports bridge_name port_name command to collect packet loss information.

  3. Run the following command to check whether the link status of the port is normal:

    ethtool port_name

    • If the value of Link detected is no, remove and reinsert the network cable and check the port.
    • If the value of Link detected is yes, go to 8.

  4. Run the following command to check whether the traffic on the target port reaches the maximum bandwidth supported by the NIC:

    sar -n DEV 1

    Information similar to the following is displayed.

    • If the port traffic reaches the maximum bandwidth and the traffic is normal service traffic, replace the original NIC with a new NIC that supports high bandwidth or improve the uplink bandwidth in binding mode.
    • If no, go to 9.

  5. Contact technical support for assistance.

Related Information

None

Translation
Download
Updated: 2019-08-30

Document ID: EDOC1100062365

Views: 49279

Downloads: 33

Average rating:
This Document Applies to these Products
Related Version
Related Documents
Share
Previous Next