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

AR100, AR120, AR160, AR1200, AR2200, AR3200, and AR3600 V300R003

This document provides the trap description, attributes, parameters, impact on the system, possible causes, procedures, and references. This document provides a complete set of traps, through which intended readers are kept of the running status of the device so as to locate faults.
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).
RSVP_1.3.6.1.4.1.2011.5.25.148.1.12.2.1 hwRsvpTeHelloLost

RSVP_1.3.6.1.4.1.2011.5.25.148.1.12.2.1 hwRsvpTeHelloLost

Description

RSVP/2/HWRSVPHELLOLOST:OID [oid] The RSVP Hello neighbor is lost. (IpAddress=[ipaddr])

The RSVP neighbor relationship was interrupted.

Attribute

Alarm ID Alarm Severity Alarm Type
1.3.6.1.4.1.2011.5.25.148.1.12.2.1 Major communicationsAlarm(2)

Parameters

Name Meaning

oid

Indicates the MIB object ID of the alarm.

IpAddress

IP address of a neighbor

Impact on the System

If GR has been enabled, services will not be affected. If GR has not been enabled, the LSP goes Down or a master/slave LSP switchover is performed using FRR.

Possible Causes

The RSVP neighbor or the link over which the RSVP neighbor relationship is established became faulty.

Procedure

  1. Check whether the physical link or the RSVP neighbor is faulty.

    • If so, repair the physical link or restart the RSVP neighbor.

    • If not, go to step 2.

  2. Run the display ip routing-table command to check whether there is a route to the RSVP neighbor.

    • If so, go to step 3.

    • If not, configure an IGP to advertise routes.

  3. Collect alarm information and configuration information, and then contact technical support personnel.
  4. End.

Related Information

None.

Translation
Download
Updated: 2019-03-06

Document ID: EDOC1100041475

Views: 71887

Downloads: 47

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