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.
| Name | Meaning |
|---|---|
oid |
Indicates the MIB object ID of the alarm. |
LsdbAreaId |
Indicates the area ID of an aged LSA. |
LsdbType |
Indicates the type of an LSA.
|
LsdbLsid |
Indicates the link state ID of an LSDB. |
LsdbRouterId |
Indicates the router ID of an LSDB. |
ProcessId |
Indicates the process ID. |
RouterId |
Indicates the router ID of the local switch. |
InstanceName |
Indicates the instance name. If the instance name is null, the OSPF process is a public process. |
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.
1. The interface was Up or Down.
2. The status of the neighbor changed.
3. The routes imported by OSPF changed.
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.
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.
Collect routing or flapping information, and go to Step 3.