Log Messages
738
ProSafe Managed Switch
OSPFv2 Warning: OSPF LSDB is 90% full (22648
LSAs). OSPFv2 limits the number of Link State
Advertisements (LSAs) that can be stored
in the link state database (LSDB). When
the database becomes 90 or 95 percent
full, OSPFv2 logs this warning. The
warning includes the current size of the
database.
OSPFv2 The number of LSAs, 25165, in the OSPF
LSDB has exceeded the LSDB memory
allocation.
When the OSPFv2 LSDB becomes full,
OSPFv2 logs this message. OSPFv2
reoriginates its router LSAs with the metric
of all non-stub links set to the maximum
value to encourage other routers to not
compute routes through the overloaded
router.
OSPFv2 Dropping the DD packet because of MTU
mismatch OSPFv2 ignored a Database Description
packet whose MTU is greater than the IP
MTU on the interface where the DD was
received.
OSPFv2 LSA Checksum error in LsUpdate,
dropping LSID 1.2.3.4 checksum 0x1234. OSPFv2 ignored a received link state
advertisement (LSA) whose checksum was
incorrect.
Table 41. OSPFv3 Log Messages
Component Message Cause
OSPFv3 Best route client deregistration failed for
OSPFv3 Redist OSPFv3 registers with the IPv6 routing
table manager (“RTO6”) to be notified of
best route changes. There are cases where
OSPFv3 deregisters more than once,
causing the second deregistration to fail.
The failure is harmless.
OSPFv3 Warning: OSPF LSDB is 90% full (15292
LSAs). OSPFv3 limits the number of Link State
Advertisements (LSAs) that can be stored
in the link state database (LSDB). When
the database becomes 90 or 95 percent
full, OSPFv3 logs this warning. The
warning includes the current size of the
database.
OSPFv3 The number of LSAs, 16992, in the OSPF
LSDB has exceeded the LSDB memory
allocation.
When the OSPFv3 LSDB becomes full,
OSPFv3 logs this message. OSPFv3
reoriginates its router LSAs with the R-bit
clear indicating that OSPFv3 is overloaded.
OSPFv3 LSA Checksum error detected for LSID
1.2.3.4 checksum 0x34f5. OSPFv3
Database may be corrupted.
OSPFv3 periodically verifies the checksum
of each LSA in memory. OSPFv3 logs this
Table 40. OSPFv2 Log Messages (Continued)
Component Message Cause