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

Alarm Handling

CloudEngine 12800 and 12800E V200R005C00

This document provides the explanations, causes, and recommended actions of alarms on the product.
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).
SYSTEM_1.3.6.1.4.1.2011.5.25.219.2.2.17 hwBoardHeartbeatTimeout

SYSTEM_1.3.6.1.4.1.2011.5.25.219.2.2.17 hwBoardHeartbeatTimeout

Description

The heartbeat connection between the board and main control board timed out. (EntityPhysicalIndex=[EntityPhysicalIndex], PhysicalIndex=[PhysicalIndex], PhysicalName=[PhysicalName])

The heartbeat packets between a board and the main control board were lost.

This trap is supported only on the Admin-VS.

Attributes

Attribute

Description

Alarm or Event

Event

Trap Severity

Warning

Mnemonic Code

hwBoardHeartbeatTimeout

Trap OID

1.3.6.1.4.1.2011.5.25.219.2.2.17

Alarm ID

This is an event trap and does not involve alarm ID.

Alarm Type

This is an event trap and does not involve alarm type.

Raise or Clear

This is an event trap and does not involve alarm generation or clearance.

Match trap

This is an event trap and does not involve the matching trap.

Parameters

Parameter Description

EntityPhysicalIndex

Heartbeat index

PhysicalIndex

Physical index

PhysicalName

Name of a physical entity

VB

VB OID

VB Name

VB Index

1.3.6.1.4.1.2011.5.25.219.1.1

hwEntityPhysicalIndex

N/A

1.3.6.1.2.1.47.1.1.1.1.7

entPhysicalName

entPhysicalIndex

Impact on the System

Services on the board will be affected.

Possible Causes

Cause 1: A communication failure occurred.

Cause 2: The system was busy.

Procedure

  • Cause 1: A communication failure occurred.
    1. Check whether the board is properly installed or whether a link is faulty.
  • Cause 2: The system was busy.
    1. Check whether the CPU usage on the board is too high.
Translation
Download
Updated: 2019-04-20

Document ID: EDOC1100039527

Views: 68727

Downloads: 21

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