DHCP Relay Log Messages
| Component | Message | Cause |
|---|---|---|
| DHCP (Dynamic Host Configuration Protocol) 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. |
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. |
OSPFv3 Log Messages
| Component | Message | Cause |
|---|---|---|
| OSPFv3 (Open Shortest Path First version 3) | 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. |
Routing Table Manager Log Messages
| Component | Message | Cause |
|---|---|---|
| RTO | RTO is no longer full. Routing table contains xxx best routes, xxx total routes, xxx reserved local routes. | When the number of best routes drops below full capacity, RTO logs this notice. The number of bad adds may give an indication of the number of route adds that failed while RTO was full, but a full routing table is only one reason why this count is incremented. |
| RTO | RTO is full. Routing table contains xxx best routes, xxx total routes, xxx reserved local routes. The routing table manager stores a limited number of best routes. The count of total routes includes alternate routes, which are not installed in hardware. | The routing table manager, also called “RTO,” stores a limited number of best routes, based on hardware capacity. When the routing table becomes full, RTO logs this alert. The count of total routes includes alternate routes, which are not installed in hardware. |
VRRP Log Messages
| Component | Message | Cause |
|---|---|---|
| VRRP | VRRP packet of size xxx dropped. Min VRRP packet size is xxx; Max VRRP packet size is xxx. |
This message appears when there is flood of VRRP messages in the network. |
| VRRP | VR xxx on interface xxx started as xxx. | This message appears when the virtual router (VR) is started in the role of a Master or a Backup. |
| VRRP | This router is the IP address owner for virtual router xxx on interface xxx. Setting the virtual router priority to xxx. | This message appears when the address ownership status for a specific VR is updated. If this router is the address owner for the VR, set the VR's priority to MAX priority (as per RFC 3768). If the router is no longer the address owner, revert the priority. |
ARP Log Message
| Component | Message | Cause |
|---|---|---|
| ARP | IP address conflict on interface xxx for IP address yyy. Conflicting host MAC address is zzz. | When an address conflict is detected for any IP address on the switch upon reception of ARP packet from another host or router. |
RIP Log Message
| Component | Message | Cause |
|---|---|---|
| RIP (Routing Information Protocol) | RIP: discard response from xxx via unexpected interface | When RIP response is received with a source address not matching the incoming interface‘s subnet. |
Print
this page
Email this topic
Feedback
View PDF
Download EPUB