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 switch 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 switch changed (for example, the switch imported routes).
| Name | Meaning |
|---|---|
oid |
Indicates the MIB object ID of the alarm. |
LsdbAreaId |
Indicates the area ID of a new LSA. |
LsdbType |
Indicates the type of the LSA.
|
LsdbLsid |
Indicates the LS 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 neighbor or interface status change trap is generated and no manual operations are performed within the period, services may be affected.
1. The status of the interface changed.
2. The status of the neighbor changed.
3. The routes imported by OSPF changed.
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.
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.