| |
|
|
This chapter describes messages generated by the bgp-events subsystem.
Major
Message: BGP Max Route Instance Exceeded Dropping Route peer <name> Current Prefixes : <number> Limit: <prefixes>Meaning: The BGP sesion on the Avici router detected that the received number of routes were greater than or equal to the max number of supported routes.
Action: Save your system log to a file and contact Avici Customer Support.
Message: BGP Max Unique Routes Exceeded. Dropping Route. Peer [<name>] Current Prefixes : <number> Limit: <routes>Meaning: The BGP sesion on the Avici router detected that the received number of unique routes was greater than or equal to the max number supported uniques routes.
Action: Save your system log to a file and contact Avici Customer Support.
Message: BGP Mem Low. Dropping Route Peer <name> Mem Avail: <memory> bytes Threshold: <minimum required memory> Total: <Tot_Sys_Mem> Prefixes: <unique routes> Instances: <route instances>Meaning: The BGP sesion on Avici router detected that the available system memory is less than the min required memory after receiving a route.
Action: Save your system log to a file and contact Avici Customer Support.
Message: Cfg value <max route instances> Lower than Current # of Routes Instances: <number>Meaning: The BGP session on the Avici router detected that the number of current route instances exceeded the number of configured maximum route instances.
Action: Check the BGP configuration. If the problem persists, contact Avici Customer Support.
Message: Cfg value <max unique routes> Lower than Current # of Unique Routes: <number>Meaning: The BGP session on Avici router detected that the current number of unique routes exceeded the number of configured max route instances.
Action: Check the BGP configuration. If the problem persists, contact Avici Customer Support.
Message: Polluted Peer: <name> Cleared. Num polluted peers <number>Meaning: This message shows the information for the polluted peer when an established BGP sesion on the Avici router goes down.
Action: Save your system log to a file and contact Avici Customer Support.
Message: buffer already allocatedMeaning: The BGP session on Avici Router tried to allocate memory.
Action: Save your system log to a file and contact Avici Customer Support.
Message: buffer not presentMeaning: The BGP session on Avici router tried to free the memory.
Action: Save your system log to a file and contact Avici Customer Support.
Message: connection error to remote peer (<Peer Name>): errno <error name>(<error number>)Meaning: The BGP session failed to get the peer's socket address after the connection was completed.
Action: Save your system log to a file and contact Avici Customer Support.
Message: couldn't get BGP listen socket!!Meaning: The BGP session on Avici router failed to get the listen socket descriptor.
Action: Save your system log to a file and contact Avici Customer Support.
Message: error sending KEEPALIVE to <name>Meaning: The BGP session on the Avici router failed to send a keepalive message to it's peer when the local keepalive timed out.
Action: Save your system log to a file and contact Avici Customer Support.
Message: getting local adddress task_get_addr_local(<name>)Meaning: The BGP session on Avici router failed to allocate memory for a local socket address while making a peer connection.
Action: Save your system log to a file and contact Avici Customer Support.
Message: holdtime expired for <name>Meaning: The BGP session on the Avici router detected that it didn't establish the BGP connection with it's peer or the peer exceeded holdtime.
Action: Save your system log to a file and contact Avici Customer Support.
Message: holdtime expired for <peer name> time since sockets processed: <time since socket processed last time> last received: <time since data received last time> num of reads skipped since last receive: <# of reads skipped> session state: <peer state>Meaning: The hold timer expired for the neighbor.
Action: Either the local system or the neighbor is busy. Collect the system log and contact Avici Customer Support.
Message: listenMeaning: The BGP session on Avici router failed to listen on the BGP socket.
Action: Save your system log to a file and contact Avici Customer Support.
Message: notify message <sent to | received from> <name> is truncated (length <value>)Meaning: The BGP session on Avici router received a shorter than minimum length notification message from a peer whose BGP notification message is corrupted.
Action: Save your system log to a file and contact Avici Customer Support.
Message: received OPEN message from <name>, state is ESTABLISHEDMeaning: The BGP session on Avici router expected an update message from a peer but receives an open message.
Action: Save your system log to a file and contact Avici Customer Support.
Message: sending <length> (sent <number>) bytes to <name> failedMeaning: The BGP session on the Avici router failed to create a notification message
Action: Save your system log to a file and contact Avici Customer Support.
Message: sending <bytes sent> (sent <total bytes sent>) bytes to <peer name> failed errno: <error name>Meaning: Sending data to the peer failed.
Action: The socket is full or the neighbor is busy. Check the TCP connection to the neighbor.
Message: sending <length> (sent <number>) bytes to <name>: connection closedMeaning: The BGP session on Avici router could not write a notification message on a peer's spooled data because of the closed connection.
Action: Save your system log to a file and contact Avici Customer Support.
Message: sending to <name> (sent <number>, <remaining message length> remain<blank or s>) loopingMeaning: The BGP session on Avici router could not write a notification message on a peer's spooled data after trying several times
Action: Save your system log to a file and contact Avici Customer Support.
Message: synchronization failure with BGP task <name>Meaning: The BGP session on Avici router received an open message from a peer and the peer's default authentication information doesn't match the BGP default authentication information on router.
Action: Save your system log to a file and contact Avici Customer Support.
Message: task_get_addr_local() failed, terminating!!Meaning: The BGP session on Avici router could not get it's local socket address pointer when processing an incomming connection request from a peer.
Action: Save your system log to a file and contact Avici Customer Support.
Message: unsupported BGP version <version>!!!Meaning: The BGP session on Avici router received a bgp update message from a peer whose BGP version is not BGP-4.
Action: Save your system log to a file and contact Avici Customer Support.
Minor
Message: Closing peer <peer address>. Interface Down. Current BGP Session State: <peer state>Meaning: The interface on which the peer is enabled has gone down.
Action: Check the status of the interface.
Message: bgp_recv: peer <name>: received unexpected EOFMeaning: An unexpected EOF was received when reading data from the peer
Action: Check the connectivity to the remote peer.
Message: error sending KEEPALIVE to <peer address>, errno: <error name>(<error number>) from rtn: <calling function>Meaning: A KEEPALIVE message sent to the peer has failed.
Action: The socket is full or the neighbor has closed the TCP connection. Check the TCP connection to the neighbor.
Message: peer <peer name> keepalive not received ignored! last processed sockets <time since sockets processed> seconds ago! hold time <hold time> last received <time since last data received from Nbr> last sent: <time since data sent last time to Nbr> byes in rx buffer: <# of bytes in the socket>Meaning: There is unprocessed data from the neighbor in the socket that the hold timer timeout ignored
Action: Collect system logs and contact Avici Customer Support.
Warning
Message: BGP peer <peer address> interface not found. Leaving peer idledMeaning: The interface to the peer was not found.
Action: Check whether the correct peer address has been configured.
Message: Could not find group to which peer <peer> belongs.Dropping him.Meaning: Could not find the peer-group to which the specified peer belongs.
Action: Check whether the peer is configured in the local system.
Message: connect <address> (Routing AS <n>)Meaning: The initial attempt to connect to the peer <ip_address> failed.
Action: Check peer connectivity and reachability.
Message: connect <peer address>: errno <error name>(<error number>)Meaning: Opening the TCP connection to the remote peer failed.
Action: Check the status of the connectivity to the peer.
Message: connection error to remote peer (<address> (Routing AS <n>))Meaning: The connection attempt to peer <ip_address> has failed.
Action: Check peer connectivity and reachability.
Message: holdtime expired RCVD for <peer name> time in seconds: since last sent: <time since data sent to Nbr> since write blocked: <time since write blocked for Nbr> since write ready: <time since write_ready was called> bgp state: <peer state>Meaning: The hold timer expired notification was received from the Neighbor.
Action: Find the reason in the local system for not sending the keepalive message to the neighbor.
Message: peer <peer name> local address <local address> unavailable, connection failedMeaning: Binding the local address to the socket failed.
Action: Check whether the configured local address is correct.
Message: peer <peer name> sent invalid capabilityMeaning: The peer has sent an invalid capability or there is no common capability between the local system and the peer.
Action: Check the capabilities configured in local system and the remote system.
Message: peer <peer name> timed out waiting for OPENMeaning: A time out occurred while waiting for open message from the peer.
Action: Check the status of the peer in remote system.
Message: received route refresh failed: peer <remote address> has not negotiated the SAFI <SAFI not negotiated> valueMeaning: A Peer has sent the route refresh message with the SAFI, which is not negotiated for this BGP session
Action: Check the peer for the negotiated address families for this BGP session.
Message: rejecting connection from <remote address>, peer in state <state>Meaning: The BGP session to the peer is in established/open/confirm/idle state and an open message has been received from the peer. The new TCP connection initiated by the remote peer is rejected and the existing connection is used
Action: No action required
| |
|
|
Copyright © 2006
Avici Systems Inc.
Avici® and TSR®
is a registered trademark of Avici Systems Inc.
IPriori™, Composite Links™, SSR™, QSR, and NSR® are
trademarks of Avici Systems Inc.
Source
File Name: bgp-events.fm
HTML File Name: bgp-events.html
Last Updated: 09/26/06 at 14:21:02