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


To have a better experience, please upgrade your IE browser.


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).
OSPF_1. ospfOriginateLsa

OSPF_1. ospfOriginateLsa


OSPF/4/OGNLSA:OID [oid]: An LSA is generated. (LsdbAreaId=[area-id], LsdbType=[lsa-type], LsdbLsid=[lsdb-ls-id], LsdbRouterId=[lsdb-router-id], ProcessId=[process-id], RouterId=[router-id], InstanceName=[instance-name])

A router generated new LSAs. The possible cause was that the status of the interface changed, the status of the OSPF neighbor changed, or the role of the router changed (for example, the router imported routes).


Alarm ID Alarm Severity Alarm Type Warning environmentalAlarm (6)


Name Meaning


Indicates the MIB object ID of the alarm.


Indicates the area ID of a new LSA.


Indicates the type of the LSA.
  • 1: Router LSA
  • 2: Network LSA
  • 3: Summary LSA type 3
  • 4: Summary LSA type 4
  • 5: AS External LSA
  • 7: NSSA LSA
  • 9: Opaque LSA - scope Local
  • 10: Opaque LSA - scope area
  • 11: Opaque LSA - scope AS


Indicates the LS ID of an LSDB.


Indicates the router ID of an LSDB.


Indicates the process ID.


Indicates the router ID of the local router.


Indicates the instance name.

Impact on the System

If the neighbor or interface status change trap is generated and no manual operations are performed within the period, services may be affected.

Possible Causes

1. The status of the interface changed.

2. The status of the neighbor changed.

3. The routes imported by OSPF changed.


  1. Check the LSA type:

  2. Run the display ip routing-table lsdb-ls-id command to check whether the routing table changes.

    • If the routing table does not change, go to Step 3.

    • If the routing table changes, continue to check the cause of the route change or go to Step 3.

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

Related Information


Updated: 2019-03-06

Document ID: EDOC1100041475

Views: 106655

Downloads: 61

Average rating:
This Document Applies to these Products

Related Version

Related Documents

Previous Next