IP Address Manager Events
The following are the events related to IP Address Manager.
Event ID: 514 (Severity: Warning)
| Message | Unable to learn HW IP host routes- table FULL |
| Platforms | K, KA, KB, RA, WB, WC, YA, YB, YC |
| Category | IP Address Manager |
| Severity | Warning |
Event ID: 515 (Severity: Warning)
| Message | IP host route table is nearing max capacity |
| Platforms | K, KA, KB, RA, WB, WC, YA, YB, YC |
| Category | IP Address Manager |
| Severity | Warning |
Event ID: 516 (Severity: Warning)
| Message | IPAM Control task delayed due to "slave message queues too full" |
| Platforms | K, KA, KB, RA, WB, WC, YA, YB, YC |
| Category | IP Address Manager |
| Severity | Warning |
| Description | While flushing the IpAddrMgr message with master generated sub messages in it to the IPAM slave control task, the flush is delayed for a timeout period. This is used when the caller might expect additional buffering to take place after the flush and the delay gives time to pack the buffer before sending it. The IPAM master control task will flush the buffer (if needed) upon processing the delay timer. Now this is enhanced to also check the slave queue depth before adding the master msg. |
Event ID: 517 (Severity: Warning)
| Message | <COUNTER VAL ROUTE> table entries marked as stale removed from FIB - where as <COUNT VAL> == counters.staleRtesRemovedAfterFailover, <ROUTE> == route"(for Ex). ==> 5 route table entries marked as stale removed from FIB |
| Platforms | K, KA, KB, RA, WB, WC, YA, YB, YC |
| Category | IP Address Manager |
| Severity | Warning |
| Description | In platforms that support HA if the active MM fails and the standby MM takes over the IPADDRMGR subsystem on the new MM which maintains the software FIB/route table and the FIB entries relationships to the corresponding L3 forwarding entries in HW needs to be sync. We sync information from an active line card up to the new master. Part of the sync action is to mark all entries being replayed from the line card and then wait a period of time to see if the routing protocols running above the IPADDRMGR subsystem end up programming the same routes. If IPADDRMGR gets a route addition from the routing protocols we clear the entry of the mark. After we’ve waited a period of time we sweep through the table and remove the entries that are still marked. This message is the indication of the removal of those stale entries. |
Event ID: 518 (Severity: Warning)
| Message | For displaying warning messages like "Please disable Openflow flow security to enable Virus Throttling" "Please disable Virus Throttling to enable Openflow Flow Security" "L3 FIB replay took 1000(ex only) ms" .......... etc |
| Platforms | K, KA, KB, RA, WB, WC, YA, YB, YC |
| Category | IP Address Manager |
| Severity | Warning |
| Description | This is internal to the implementation of the subsystem. This type is used for a various set of warnings that the user may want to be aware of – BFD, Openflow, Slave messages, NUD. |
Event ID: 519 (Severity: Warning)
| Message | Module <MODULE NAME>: unknown msg opcode: <OPCODE_ADDRESS_MESSAGE> |
| Platforms | K, KA, KB, RA, WB, WC, YA, YB, YC |
| Category | IP Address Manager |
| Severity | Warning |
| Description | These types are internal to the implementation of the subsystem and will indicate that the subsystem received a message type that it does not recognize. |
Event ID: 520 (Severity: Warning)
| Message | Ports <PORT_ID>: unknown msg opcode: <OPCODE_ADDRESS_MESSAGE> |
| Platforms | K, KA, KB, RA, WB, WC, YA, YB, YC |
| Category | IP Address Manager |
| Severity | Warning |
| Description | These types are internal to the implementation of the subsystem and will indicate that the subsystem received a message type that it does not recognize. |
Event ID: 901 (Severity: Warning)
| Message | Failed to allocate new <ENTRY TYPE> FIB entry |
| Platforms | K, KA, KB, RA, WB, WC, YA, YB, YC |
| Category | IP Address Manager |
| Severity | Warning |
| Description | These types are internal to the implementation of the subsystem and will indicate that we were unable to allocate an actual HW entry or dealloc an actually HW for a specific FIB entry type. As the FIB keeps track of routes, neighbors, tunnel interfaces, NFD entries, multicast groups the output will differ based on what type of entry we are dealing with. This won't be of much use to customer. |
Event ID: 902 (Severity: Warning)
| Message | Failed to deallocate <ENTRY TYPE> FIB entry |
| Platforms | K, KA, KB, RA, WB, WC, YA, YB, YC |
| Category | IP Address Manager |
| Severity | Warning |
| Description | These types are internal to the implementation of the subsystem and will indicate that we were unable to allocate an actual HW entry or dealloc an actually HW for a specific FIB entry type. As the FIB keeps track of routes, neighbors, tunnel interfaces, NFD entries, multicast groups the output will differ based on what type of entry we are dealing with. This won't be of much use to customer. |
Event ID: 903 (Severity: Warning)
| Message | Failed to allocate FIB memory for <ENTRY TYPE> |
| Platforms | K, KA, KB, RA, WB, WC, YA, YB, YC |
| Category | IP Address Manager |
| Severity | Warning |
| Description | Similar to the ENTRY_ALLOC_FAIL above, this is a type internal to the implementation of the subsystem and will indicate that we were unable to allocate memory (Heap space/from system RAM) to keep track of the software entries that make up the FIB. As the FIB keeps track of routes, neighbors, tunnels, mcast flows, security entries the output will differ based on what type of software entry we are dealing with. This won't be of much use to customer. |
Event ID: 904 (Severity: Warning)
| Message | Failed to add FIB entry "- route gateway is switch ip, vrf: VRFID, IPADDR, MASKLEN" |
| Platforms | K, KA, KB, RA, WB, WC, YA, YB, YC |
| Category | IP Address Manager |
| Severity | Warning |
| Description | Failure warning messages. |
Event ID: 905 (Severity: Warning)
| Message | Failed to add FIB entry "- route gateway is switch ip, vrf: VRFID, IPADDR, MASKLEN" |
| Platforms | K, KA, KB, RA, WB, WC, YA, YB, YC |
| Category | IP Address Manager |
| Severity | Warning |
| Description | Failure warning messages. |
Event ID: 906 (Severity: Warning)
| Message | Invalid FIB route descriptor for entry <****> rtDesc: rtDescID, vrf, VRFID, IPADDR, MASKLEN Where <***> ==> - neighbor to update/- route to delete/- neighbor to clear/- next-hop router, route add failed/- route next-hop/- route to add/- neighbor to add |
| Platforms | K, KA, KB, RA, WB, WC, YA, YB, YC |
| Category | IP Address Manager |
| Severity | Warning |
| Description | Much like the others this is internal to the implementation of the subsystem. In a distributed system where information is replicated across different members, you sometimes want to use an index value that is common across the entire system. IPADDRMGR uses a route descriptor table (array) and we sometimes pass around the array index (route descriptor) rather than all the information that makes up a route or neighbor or ownIP. This message indicates that the route descriptor being passed around is invalid. |
Event ID: 907 (Severity: Warning)
| Message | <PORTS|MODULE> <ID> parity recovery <MEMORY_IDX> 0x<LOCATION>. |
| Platforms | K, KA, KB, RA, WB, WC, YA, YB, YC |
| Category | IP Address Manager |
| Severity | Warning |
| Description | This is also internal to the implementation of the subsystem. In systems that have parity memory as a form of error detection we have to handle parity errors. This RMON type is to indicate that we'’ve recovered from a parity error. |
Event ID: 908 (Severity: Warning)
| Message | Failed to add neighbor timer entry for rtDesc: <RT_DESC_STR> timeout: <TIMEOUT_VAL> vrf: <VRF_ID> ipAddr: <IP_ADDRESS> |
| Platforms | K, KA, KB, RA, WB, WC, YA, YB, YC |
| Category | IP Address Manager |
| Severity | Warning |
| Description | This is internal to the implementation of the subsystem. As IPAM handles the NUD process in our switch SW, this RMON type is used to indicate that we were unable to add a neighbor entry to the timeout tree that helps us implement the NUD state machine. |