Netgear XSM7224S User Manual Page 516

  • Download
  • Add to my manuals
  • Print
  • Page
    / 579
  • Table of contents
  • BOOKMARKS
  • Rated. / 5. Based on customer reviews
Page view 515
ProSafe XSM7224S Managed Stackable Switch CLI Manual, Software Version 9.0
Log Messages 8-18
v1.0, November 2010
Table 8-38: OSPFv2 Log Messages
Component Message Cause
OSPFv2 Best route client deregistration failed for
OSPF Redist
OSPFv2 registers with the IPv4 routing table
manager (“RTO”) to be notified of best route
changes. There are cases where OSPFv2
deregisters more than once, causing the
second deregistration to fail. The failure is
harmless.
OSPFv2 XX_Call() failure in _checkTimers for thread
0x869bcc0
An OSPFv2 timer has fired but the message
queue that holds the event has filled up. This
is normally a fatal error.
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 8-39: 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.
Page view 515
1 2 ... 511 512 513 514 515 516 517 518 519 520 521 ... 578 579

Comments to this Manuals

No comments