OSPF routes advertised by the local device were deleted by another device, and the possibly faulty device did not support OSPF flush LSA source trace. Log in to the possibly faulty device. If the device is deleting routes, reset or isolate it from the network. Otherwise, check other devices. Neither of the devices displayed in the display ospf flush-source-trace analysis-info command output is the faulty device. (SysProcessId=[hwOspfv2ProcessIdIndex], HostName=[hwOspfv2PurgeHostName], HostIpAddress=[hwOspfv2PurgeIpAddress], RouterID=[hwOspfv2PurgeRouterId], Area=[hwOspfv2AreaId], FlushLsaNum=[hwOspfv2FlushLsaNum], AffectedNodeNum=[hwOspfv2AffectedNodeNum], TotalNodeNum=[hwOspfv2TotalNodeNum], RuledOutDeviceNum=[hwOspfv2RuledOutDeviceNum], Interval=[hwOspfv2PurgeStatPeriod])
The OSPF LSAs advertised by the local device were flushed by a remote device, and possibly faulty devices do not support OSPF flush LSA source tracing. In this case, log in to a possibly faulty node and check whether it is flushing LSAs. If it is flushing LSAs, reset or isolate it. If the possibly faulty node is not flushing LSAs, check other possibly faulty nodes. To check the analysis report output by OSPF flush LSA source tracing, run the display ospf flush-source-trace analysis-info command.
| Trap Attribute | Description |
|---|---|
Alarm or Event |
Alarm |
Trap Severity |
Critical |
Mnemonic Code |
ospfRouteBeDeletedByPurgeInexact |
Trap OID |
1.3.6.1.4.1.2011.5.25.155.31.24 |
MIB |
HUAWEI-OSPFV2-MIB |
Alarm ID |
0x00F1015c |
Alarm Name |
OSPF_ROUTE_BE_DEL_BY_PURGE_INEXACT |
Alarm Type |
qualityOfServiceAlarm |
Raise or Clear |
Raise |
Match trap |
OSPF_1.3.6.1.4.1.2011.5.25.155.31.25 hwOspfv2RouteBeDeletedByPurgeInexactClear |
| Parameter | Description |
|---|---|
hwOspfv2ProcessIdIndex |
Process ID on the faulty node |
hwOspfv2PurgeHostName |
Hostname of the faulty node |
hwOspfv2PurgeIpAddress |
Host IP address of the faulty node |
hwOspfv2PurgeRouterId |
Router ID in the process |
hwOspfv2AreaId |
OSPF area ID |
hwOspfv2FlushLsaNum |
Number of times an LSA was flushed |
hwOspfv2AffectedNodeNum |
Number of affected nodes |
hwOspfv2TotalNodeNum |
Total number of nodes on the network |
hwOspfv2RuledOutDeviceNum |
Number of nodes that have been identified as faultless nodes |
hwOspfv2PurgeStatPeriod |
Statistical period |
| VB OID | VB Name | VB Index |
|---|---|---|
1.3.6.1.4.1.2011.5.25.155.3.1.1 |
hwOspfv2ProcessIdIndex |
hwOspfv2ProcessIdIndex |
1.3.6.1.4.1.2011.5.25.155.30.9 |
hwOspfv2PurgeHostName |
- |
1.3.6.1.4.1.2011.5.25.155.30.10 |
hwOspfv2PurgeIpAddress |
- |
1.3.6.1.4.1.2011.5.25.155.30.11 |
hwOspfv2PurgeRouterId |
- |
1.3.6.1.4.1.2011.5.25.155.30.3 |
hwOspfv2AreaId |
- |
1.3.6.1.4.1.2011.5.25.155.30.12 |
hwOspfv2FlushLsaNum |
- |
1.3.6.1.4.1.2011.5.25.155.30.13 |
hwOspfv2AffectedNodeNum |
- |
1.3.6.1.4.1.2011.5.25.155.30.14 |
hwOspfv2TotalNodeNum |
- |
1.3.6.1.4.1.2011.5.25.155.30.16 |
hwOspfv2RuledOutDeviceNum |
- |
1.3.6.1.4.1.2011.5.25.155.30.15 |
hwOspfv2PurgeStatPeriod |
- |
Network flapping occurs, which adversely affects network stability and traffic forwarding.
In the alarm, the value of FlushLsaNum may be 0. The interval at which the alarm is cleared and the interval at which the value of FlushLsaNum on the faulty node is cleared are both 3600s. There may be a short period (5 minutes at most) during which the value of FlushLsaNum on the faulty node is cleared but the alarm still persists. This is a normal situation.