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-6027 Rate of an Autonegotiation-Supported Network Port Has Not Reached half of the Maximum Port Rate

ALM-6027 Rate of an Autonegotiation-Supported Network Port Has Not Reached half of the Maximum Port Rate

Description

FusionSphere OpenStack checks the network port rates for all network ports every 60s. This alarm is generated when the actual rate of a network port that supports autonegotiation is lower than half of the maximum port rate.

Attribute

Alarm ID

Alarm Severity

Auto Clear

6027

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 reliability of the communication between the network plane where the network port is located and external devices may deteriorate. The communication between the server and the connected devices may be interrupted.

Possible Causes

  • Autonegotiation is not enabled on this port.
  • Autonegotiation is not enabled on the peer network port.
  • The maximum port rate supported by the peer network port is lower than that supported by the local port.
  • The network cable is not properly connected to the network port.
  • The network cable connected to the network port is damaged.
  • The network cable of the switch connected to the network port is damaged or not properly connected.

Procedure

  1. Use PuTTY to log in to the first FusionSphere OpenStack node through the IP address of the External OM plane.

    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.

    NOTE:
    To obtain the IP address of the External OM plane, search for the required parameter on the Tool-generated IP Parameters sheet of the xxx_export_all.xlsm file exported from HUAWEI CLOUD Stack Deploy during software installation. The parameter names in different scenarios are as follows:
    • Region Type I scenario:

      Cascading system: Cascading-ExternalOM-Reverse-Proxy

      Cascaded system: Cascaded-ExternalOM-Reverse-Proxy

    • Region Type II and Region Type III scenarios: ExternalOM-Reverse-Proxy

  2. 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!.

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

    TMOUT=0

  4. 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] 

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

    Default account format: DCname_admin; default password: FusionSphere123.

  6. Log in to the FusionSphere OpenStack web client.

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

  7. 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.
  8. Run the following commands to log in to the faulty host using SSH:

    su - fsp

    ssh fsp@Host External OM plane IP address

    Enter the system private key password as prompted. The default password is Huawei@CLOUD8!. If newly generated public and private key files have replaced the old ones, enter the password of the new private key. Alternatively, press Enter and enter the password of user fsp.

    After login, run the su - root command to switch to the user root.

  9. Run the ethtool eth* command (eth* indicates the faulty network port) to check whether autonegotiation is enabled on the port.

    • If the Auto-negotiation value is off, go to 10.
    • If the Auto-negotiation value is on, go to 11.

  10. Run the ethtool -s eth* autoneg on command to enable autonegotiation on the port. After 1 to 2 minutes, check whether the alarm is cleared.

    • If yes, no further action is required.
    • If no, go to 11.

  11. Contact the O&M personnel to check whether autonegotiation is enabled on the peer network port.

    • If no, go to 12.
    • If yes, go to 13.

  12. Contact the O&M personnel to enable autonegotiation on the peer network port. After 1 to 2 minutes, check whether the alarm is cleared.

    • If yes, no further action is required.
    • If no, go to 13.

  13. Contact the O&M personnel to check whether the maximum port rate of the peer network port is less than half of that of the local port.

    • If yes, go to 14.
    • If no, go to 22.

  14. Replace the NIC by referring to "Replacing Hosts and Accessories" in HUAWEI CLOUD Stack 6.5.0 Parts Replacement. Ensure that the network port rate is greater than or equal to half of the maximum specifications of the local end. Wait for 1 to 2 minutes and check whether the alarm is cleared.

    • If yes, no further action is required.
    • If no, go to 15.

  15. Check whether the network cable connected to the network port is inappropriately connected.

    • If yes, go to 16.
    • If no, go to 17.

  16. Reconnect the network cable. After 2 or 3 minutes, check whether the alarm is cleared.

    • If yes, no further action is required.
    • If no, go to 17.

  17. Check whether the network port indicator of the switch connected to the network port is normal.

    If the indicator is steady on or blinking, the connection is normal. If the indicator is off, the connection is abnormal.

    • If yes, go to 22.
    • If no, go to 18.

  18. Check whether the network cable of the switch connected to the network port is inappropriately connected.

    • If yes, go to 19.
    • If no, go to 20.

  19. Reconnect the network cable. After 2 or 3 minutes, check whether the alarm is cleared.

    • If yes, no further action is required.
    • If no, go to 20.

  20. If the network cable between the server and the switch is damaged, replace the network cable. After 2 to 3 minutes, check whether the alarm is cleared.

    • If yes, no further action is required.
    • If no, go to 21.

  21. If the network port or NIC of the server is faulty, contact hardware maintenance personnel to replace the NIC. After 2 to 3 minutes, check whether the alarm is cleared.

    • If yes, no further action is required.
    • If no, go to 22.

  22. Contact technical support for assistance.

Related Information

None

Translation
Download
Updated: 2019-08-30

Document ID: EDOC1100062365

Views: 34529

Downloads: 31

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