Command Reference Guide
Routing
CLI Command Reference
September 2014 Page 702
HP Moonshot Switch Module CLI Command Reference
Routing
Table 52: DHCP Relay Log Messages
Component Message Cause
DHCP relay REQUEST hops field more than config value The DHCP relay agent has processed a DHCP
request whose HOPS field is larger than the
maximum value allowed. The relay agent will
not forward a message with a hop count
greater than 4.
DHCP relay Request's seconds field less than the config
value
The DHCP relay agent has processed a DHCP
request whose SECS field is larger than the
configured minimum wait time allowed.
DHCP relay processDhcpPacket: invalid DHCP packet
type: %u\n
The DHCP relay agent has processed an
invalid DHCP packet. Such packets are
discarded by the relay agent.
Table 53: 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.