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-73101 Virtual Network Port Packet Loss Rate Exceeds the Threshold

ALM-73101 Virtual Network Port Packet Loss Rate Exceeds the Threshold

Description

This alarm is generated when the packet loss rate of the virtual switch port reaches the percentage configured in the alarm configuration.

Attribute

Alarm ID

Alarm Severity

Auto Clear

73101

Major

Yes

Parameters

Name

Meaning

Name

Specifies the alarm name.

Object ID

Specifies the alarm object ID.

If an alarm is generated for a resource, such as a host or VM, the value is the resource ID, for example, the host ID. If an alarm is generated for a service module, the value is the ID of the service module, for example, FusionSphere OpenStack OM.

Object Type

Specifies the alarm object type. Example values: host and heart beat (indicating the heartbeat detection system).

Object Name

Specifies the object for which the alarm is generated.

If an alarm is generated for a resource, such as a host or VM, the value is the resource name, for example, the host name. If the alarm is generated for a service module, the value is the name of the service module, for example, FusionSphere OpenStack OM.

Component Type

Specifies the type of the component that reports the alarm, for example, FusionSphere OpenStack or FusionSphere OpenStack OM.

Component

Specifies the component that reports the alarm.

Fault Location Info

Provides detailed information about the alarm object, usually in the form of key value pairs. For example: host=*****,portName=###, indicating that the alarm is generated on port ### of host ****.

Additional Info

Provides additional information about the alarm, usually in the form of key value pairs. For example: Threshold=70,current_value=75, indicating that the alarm is generated because the threshold is 70 and the current value is 75.

Generated At

Specifies the time when the alarm is generated.

Cleared At

Specifies the time when the alarm is cleared.

Clearance Type

Specifies how the alarm is cleared (manually or automatically).

Cleared By

Specifies the name of the user who clears the alarm. This parameter is left blank if the alarm is automatically cleared.

Alarm Clearance User ID

Specifies the ID of the user who clears the alarm. This parameter is left blank if the alarm is automatically cleared.

Alarm Cleared At

Specifies the system view (tenant view or administrator view) in which the alarm is manually cleared.

SN

Specifies the sequence number of the 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!.

  5. Run the following command to disable user logout upon system timeout:

    TMOUT=0

  6. Run the following command to import environment variables:

    source set_env

    Information similar to the following is displayed:

      please choose environment variable which you want to import: 
      (1) openstack environment variable (keystone v3) 
      (2) cps environment variable 
      (3) openstack environment variable legacy (keystone v2) 
      (4) openstack environment variable of cloud_admin (keystone v3) 
      please choose:[1|2|3|4] 

  7. Enter 1 to enable Keystone V3 authentication and enter the password of OS_USERNAME as prompted.

    Default account format: DCname_admin; default password: FusionSphere123.

  8. Query the virtual network monitoring alarm log and obtain the virtual network port whose packet loss rate exceeds the threshold.

    vim /var/log/sysmonitor/unetwork_alarm.log

  9. Run the following command to check whether the port on which packet loss occurs exists:

    ovs-vsctl list interface port_name

    In the command, port_name indicates the port name.

    • If port tap0 is used as an example, information similar to Figure 3-2 is displayed.
      Figure 3-2 Information indicating that the port exists
    • If information similar to the following is displayed, the port does not exist. Manually clear the alarm.
      Figure 3-3 Information indicating that the port does not exist

  10. Run the following command to query the bridge to which the port belongs:

    ovs-vsctl iface-to-br port_name

    If port tap0 is used, information similar to the following is displayed, indicating that port tap0 belongs to bridge br0.

    Figure 3-4 Bridge

  11. Run the following command to check whether the port is a physical port:

    If the value of driver_name in the status field is ixgbe, i40e, or mlx4_en, the port is a physical port.

    ovs-vsctl list interface port_name

    Figure 3-5 Physical port

  12. Check whether the bridge is a user-mode bridge or kernel-mode bridge.

    Assume that the port belongs to bridge br0 and run the following command to check whether the value of the datapath_type field is dpdk:

    ovs-vsctl list br br0

    • If yes, a user-mode bridge is used. In this case, go to 15.
    • If no, a kernel-mode bridge is used. In this case, go to 13.
      Figure 3-6 datapath_type field

  13. Run the following command to check whether the port link is normal:

    ethtool port_name

    Information similar to Figure 3-7 is displayed.

    Figure 3-7 Port link status
    • If the value of Link detected is no in Figure 3-7, check whether the port cable is connected normally. Ensure that the port cable is connected normally and then go to 13.
    • If the value of Link detected is yes in Figure 3-7, go to 14.

  14. If the bridge is a kernel-mode bridge and the port is a physical port, run the following command to check whether the port traffic reaches the maximum bandwidth supported by the NIC:

    Sar -n DEV 1

    Information similar to 14 is displayed.

    Figure 3-8 Port traffic
    • 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 16.

  15. If the bridge is a user-mode bridge and the port is a physical port, check whether the network port is properly connected.

    • If no, remove and insert the network cable.
    • If yes, run the following command to collect packet loss information and then go to 16.

      ovs-appctl dpif-dpdk/dump-loss bridge_name port_name

  16. After these operations are performed, if the alarm persists and the problem cannot be located, contact technical support for assistance.

Related Information

None

Translation
Download
Updated: 2019-08-30

Document ID: EDOC1100062365

Views: 33928

Downloads: 31

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