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

S600-E V200R010C00

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

OSPF_1. ospfMaxAgeLsa


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

LSAs in the LSDB of the switch reached the maximum aging time. The possible cause was that the routes imported by OSPF were deleted or the OSPF interface was Down.


Alarm ID Alarm Severity Alarm Type Warning environmentalAlarm (6)


Name Meaning


Indicates the MIB object ID of the alarm.


Indicates the area ID of an aged LSA.


Indicates the type of an 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 link state ID of an LSDB.


Indicates the router ID of an LSDB.


Indicates the process ID.


Indicates the router ID of the local switch.


Indicates the instance name.

If the instance name is null, the OSPF process is a public process.

Impact on the System

In the case of Type 1 and Type 2 LSAs, services may be affected, and thus you need to check the interface or neighbor status. In the case of Type 3, Type 5, and Type 7 LSAs, only the routes associated with lsdb-ls-id will be affected.

Possible Causes

1. The interface was Up or Down.

2. The status of the neighbor changed.

3. The routes imported by OSPF changed.


  1. Check the LsdbRouterId of the LSA in the trap.

    • If the LSA is generated by the local switch, go to Step 2.

    • If the LSA is not generated by the local switch, go to Step 4.

  2. Check the LSA type:

    • In the case of Type 1 and Type 2 LSAs, check whether the following alarms exist:
      • If so, handle the alarms according to the handling procedures of these alarms.

      • If not, go to Step 3.

    • In the case of Type 3, Type 5, and Type 7 LSAs, run the display ip routing-table lsdb-ls-id command to check whether the route exists or switch flapping occurs.
      • Collect routing or flapping information, and go to Step 3.

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

Related Information


Updated: 2019-09-24

Document ID: EDOC1000141873

Views: 158639

Downloads: 15

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