OSPF_1.3.6.1.2.1.14.16.2.12 ospfOriginateLsa

Description

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 wireless access controller 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 wireless access controller changed (for example, the wireless access controller imported routes).

Attribute

Alarm ID	Alarm Severity	Alarm Type
1.3.6.1.2.1.14.16.2.12	Warning	environmentalAlarm (6)

Parameters

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. 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
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 wireless access controller.
InstanceName	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.

Procedure

Check the LSA type:
- In the case of Type 1 and Type 2 LSAs, check whether the following alarms exist:
  
  1.3.6.1.2.1.14.16.2.1
  
  1.3.6.1.2.1.14.16.2.2
  
  1.3.6.1.2.1.14.16.2.3
  1.3.6.1.2.1.14.16.2.16
  - 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, go to Step 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.
Collect alarm information and configuration information, and then contact technical support personnel.
End.

Related Information

None