OSPF_1.3.6.1.2.1.14.16.2.11 ospfVirtIfTxRetransmit

Description

OSPF/3/VIFRETX:OID [oid]: An OSPF packet is retransmitted on a virtual interface. (VirtIfAreaId=[area-id], VirtIfNeighbor=[neighbor-router-id], LsdbAreaId=[lsdb-area-id], LsdbType=[lsa-type], LsdbLsid=[lsdb-ls-id], LsdbRouterId=[lsdb-router-id], ProcessId=[process-id], RouterId=[router-id], PacketType=[packet-type], InstanceName=[instance-name])

OSPF packets were retransmitted on virtual-link interfaces. The possible cause was that the physical link was unreachable or the information about entries in the routing table was incorrect.

Attribute

Alarm ID	Alarm Severity	Alarm Type
1.3.6.1.2.1.14.16.2.11	Minor	environmentalAlarm (6)

Parameters

Name	Meaning
oid	Indicates the MIB object ID of the alarm.
VirtIfAreaId	Indicates the area ID.
VirtIfNeighbor	Indicates the router ID of a neighboring switch.
LsdbAreaId	Indicates the area ID of an LSDB.
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 switch.
PacketType	Indicates the type of a packet. 1: Hello packet 2: DD packet 3: Request packet 4: Update packet 5: Acknowledgement packet 6: Update packet Retrans 7: Update packet flood
InstanceName	Indicates the instance name.

Impact on the System

This trap message is generated when an OSPF packet is retransmitted on a virtual link interface. The cause may be that the network is busy, and thus LSDB update and route calculation convergence are slow.

Possible Causes

1. The address used to forward the packets could not be pinged through.

2. The peer regarded the packet as an invalid packet.

Procedure

Run the display ospf vlink command to check the peer switch of the vlink. Then log in to this switch and run the display ospf vlink command again to check the vlink interface status or neighbor status.
- If the vlink interface status or neighbor status is Down, see the procedures in traps 1.3.6.1.2.1.14.16.2.1 and 1.3.6.1.2.1.14.16.2.3.
- If the vlink neighbor status is Full, find the IP address displayed in the interface field in the output and ping this address from the switch that generates the alarm.
  - If the ping fails, go to Step 3.
  - If the ping succeeds, go to Step 2.
Check whether the local switch and the neighbor have trap 1.3.6.1.2.1.14.16.2.9 and locate the fault according to the trap. Otherwise, go to Step 3.
Collect alarm information and configuration information, and then contact technical support personnel.
End.

Related Information

None