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-1200078 Bond Slave Status Abnormal

ALM-1200078 Bond Slave Status Abnormal

Description

This alarm is generated when the slave NIC of the bond port, including the Linux bond port on the OVS and the DPDK bond port on the EVS or OVS-DPDK, on the EVS/OVS-DPDK or OVS bridge is abnormal.

Attribute

Alarm ID

Alarm Severity

Auto Clear

1200078

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

The uplink bandwidth of the bond on the host reduces, the network services are interrupted, or the active/standby switchover of the bond fails.

Possible Causes

  • The cable of the slave physical NIC is disconnected.
  • The status of the slave physical NIC is not up.
  • The status of the peer physical NIC connected to the slave physical NIC is not up.
  • The link of the slave node is abnormal.

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. Based on the bond name and slave name displayed in additional information, obtain information about the faulty bond and slave information and run the following command to check whether the bond port exists:

    ovs-vsctl list interface bond_name

    • If information similar to the following is displayed, the bond port exists.

      If type is dpdkbond, the port is a user-mode-bridge port. In this case, go to 8. Otherwise, go to 6.

    • If information similar to the following is displayed, the port does not exist. In this case, manually clear the alarm.

  6. If the port is not a user-mode-bridge port, run the following command to check whether the slave NIC status UP:

    ifconfig Slave NIC name

    • If the NIC status is not UP, run the following command to enable the NIC and then check whether the alarm is cleared. If the alarm is not cleared, go to 7.

      ifconfig Slave NIC name up

    • If the NIC status is UP, go to 7.

  7. Run the following command to check whether the NIC link is normal:

    ethtool Slave NIC name

    • If the value of Link detected is yes, check whether the alarm is cleared.
      • If yes, no further action is required.
      • If no, manually clear the alarm.
    • If the value of Link detected is no, go to 9.

  8. If the port is a user-mode-bridge port, run the following command to check whether the status of the slave port of the DPDK bond is normal:

    ovs-appctl dpdk-bond-slave/show bond_name

    • If yes, check whether the alarm is cleared.
      • If yes, no further action is required.
      • If no, manually clear the alarm.
    • If no, go to 9.

  9. Check whether the connection between the peer physical NIC and the uplink port is normal.

    • If yes, go to 10.
    • If no, connect the network cable of the peer port and check whether the alarm is cleared. If the alarm persists, go to 10.

  10. Contact technical support for assistance.
Translation
Download
Updated: 2019-08-30

Document ID: EDOC1100062365

Views: 38193

Downloads: 31

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