bgp-updates Messages

This chapter describes messages generated by the bgp-updates subsystem.

Critical

Message: Unable to add a route to the routing information base

Meaning: This message indicates that a route advertised by a BGP peer could not be added to the routing information base.

Action: Check the next hop's configuration, as well as the local system's memory usage. If the problem persists save your system log to a file and contact Avici Customer Support.

Message: Unable to send a BGP open message to peer <address>, <AS> running BGP version <version>

Meaning: This message occurs when the TSR cannot send a open message to BGP peer because a corrupted BGP open message was received from the peer or the version of BGP running on peer is not compatible with TSR.

Action: Check the BGP configuration and version of both routers. If the problem persists save your system log to a file and contact Avici Customer Support.

Major

Message: Ignoring <route type> routes from non-<route type> neighbor <name>

Meaning: This message indicates that TSR will ignore this type of routes if it is not configured to accept them.

Action: Check the BGP configuration. If the problem persists, contact Avici Customer Support.

Message: peer <name> UPDATE no localpref attribute found

Meaning: This message occurs when the BGP session on TSR receives an update message which doesn't include the local preference attribute.

Action: Save your system log to a file and contact Avici Customer Support.

Message: peer <address> UPDATE no next hop found

Meaning: This message occurs when the BGP session on TSR receives an update message which doesn't include the nexthop attribute.

Action: Save your system log to a file and contact Avici Customer Support.

Message: peer <name> UPDATE prefix length <length> exceeds unreachable prefix data remaining (<remaining prefix length> bytes)

Meaning: This occurs when the BGP session on TSR detects that the length of unreachable prefix field from a peer's update message exceeds the remaining prefix data length message.

Action: This occurs when the BGP session on TSR detects that the length of unreachable prefix field from a peer's update message exceeds the remaining prefix data length message.

Message: peer <name> UPDATE prefix length <length> too long

Meaning: This message occurs when the BGP session on TSR receives an update message which has withdrawn routes and the length of the prefix is too long.

Action: Save your system log to a file and contact Avici Customer Support.

Message: peer <name> UPDATE unreachable prefix length <length> too long

Meaning: This occurs when the BGP session on TSR detects that the length of unreachable prefix field from a peer's update message exceeds the maxinum prefix length.

Action: Save your system log to a file and contact Avici Customer Support.

Message: peer <name> update included invalid route <address>/<mask> (<remaining prefix length> of <value>)

Meaning: This message occurs when the BGP session on TSR detects that the network prefixs from a peer's update message are invalid.

Action: Save your system log to a file and contact Avici Customer Support.

Message: sending <length> bytes to <name> blocked (no spooling requested)

Meaning: This occurs when the BGP session on TSR cannot send an updated message to a peer.

Action: Save your system log to a file and contact Avici Customer Support.

Message: sending <length> bytes to <name> failed

Meaning: This occurs when the BGP session on TSR fails to send the message.

Action: Save your system log to a file and contact Avici Customer Support.

Message: sending <bytes> bytes to <peer name> failed, errno: <error>(<error name>)

Meaning: The bgp messages sent to the peer failed due to one of the following errors in the socket: EWOULDBLOCK - occurs when required resources are not available. Either no data is available to be received, or there is no available buffer space for the data to be transmitted. In either case the operation is automatically retried until it succeeds. EPIPE(32) - occurs when the local end of a connection oriented socket has been shut down.

Action: No action required.

Message: sending <length> bytes to <name>: connection closed

Meaning: This occurs when the BGP session on TSR fails to send any message to a peer because the connection is closed.

Action: Save your system log to a file and contact Avici Customer Support.

Message: sending to <name> looping

Meaning: This occurs when the BGP session on TSR fails to send a message to it's peer after try several times because of the failure of writing data to sending socket.

Action: Save your system log to a file and contact Avici Customer Support.

Minor

Message: BGP read from peer <remote address> failed, errno: <number>(<number>)

Meaning: A socket failed for a neighbor while BGP was reading data.

Action: Check the connectivity to the peer.

Message: Peer <peer name> Failed write status: <write status> errno: <error>(<error #>). request: <length> bytes buf space: <buffer space>

Meaning: A write to the peer failed due to an error. The bytes requested to send and buffer space available are logged.

Action: Check for the socket status. Also, using the specified error number, identify the cause for the error.

Message: sending <bytes> bytes to <peer name> blocked (no spooling requested) at time <number>

Meaning: Specifies the socket is blocked when sending a message to the peer.

Action: Based upon the socket parameter, analyze the cause for the block. Check whether the socket is opened and established.

Warning

Message: BGP peer <peer name> : received <received message>, expected <expected type 1><OR string when 2 msgs are expected><expected type 2>

Meaning: An expected message was not received from the peer.

Action: No action required. This log can be useful for debugging minor/major issues.

Message: BGP read from peer <address>+<n> (proto) failed

Meaning: The TCP session to peer <ip_address> was lost while in the process of bringing up the adjacency (connection not established).

Action: Verify the validity of the physical connection to the peer, or the configuration of the peer.

Message: Processing <unicast/multicast> route <address>/<mask> from peer <name>: Next Hop and Prefix Identical; Raising Admin-Distance to <admin distance>

Meaning: The admin distance will be raised on this route because the Destination and Nexthop are same.

Action: No action required.

Information

Message: <counted out> <peer name> received <# of octets received> octet<suffix based on count> <# of updates received> update<suffix> <# of NLRIs received> route<suffix>

Meaning: Provides detailed information about the updates received from the peer, such as octets, NLRI, and updates count.

Action: No action required.

Message: Peer <peer name> requested: <bytes requested> bytes. Buf space available: <available buffer space>

Meaning: The buffer space is not sufficient to write the requested data on the socket for a peer.

Action: No action required.

Message: Peer <peer name> written: <bytes written> bytes. request: <bytes requested> bytes buf space: <buffer space>

Meaning: Specifies the number of bytes written to the peer and the available buffer space.

Action: No action required.

Message: group <peer group name> <# of routes ready> route<suffix> ready <# of routes deferred> deferred

Meaning: Specifies the number of routes ready and deferred, when a policy is applied for a group.

Action: No action required.

Message: group <peer group name> neighbor <peer name> <# of routes ready to send> route<suffix> ready to go

Meaning: Provides information about the number of routes ready to send to a peer in a group.

Action: No action required.

Message: group <peer group name> sent <# of routes sent> route<suffix> <next timer expiry> <# of routes to flash next> awaiting flash <# of peers> peer<suffix> dropped sync

Meaning: Provides information about the number of routes successfully sent to the peers in the group and the number of peers awaiting to flash the routes in the next timer expiry.

Action: No action required.

Message: group <peer group name> sent <# of routes sent> route<suffix> <next expiry timer> <# of peers> peer<suffix> dropped sync

Meaning: Provides the number of routes sent to the peer group and the number of peers dropped by sync.

Action: No action required.

Message: group <update type> update <group name>

Meaning: Provides running policy (flash/newpolicy/route refresh) for a group.

Action: No action required.

Message: group peer <peer name> <write error type (blocked/failed)> after <# of routes sent successfully> route<suffix for routes count> sent

Meaning: Write error (block/fail) after sending x number of routes to peer. This information will be useful when debugging major issues along with the error number reported in the log file.

Action: No action required.

Message: group peer <peer name> sent <# of routes sent> route<suffix> <next timer expiry>

Meaning: Provides information about the number of routes successfully sent to the peer.

Action: No action required.

Message: group peer <peer name> sent <# of routes sent> route<suffix> <next timer expiry> <# of routes awaiting> awaiting flash

Meaning: Provides information about the number of routes sent to the peer and the number of routes awaiting flash that will be sent in next timer expiry.

Action: No action required.

Message: group sending to <# of sync peers> in-sync peers in <peer group name>

Meaning: Specifies the number of peers in sync of a group to which the updates are to be sent.

Action: No action required.

Message: receiving updates from <peer name>

Meaning: Updates are being received from the peer.

Action: No action required.

Message: sending <# of bytes> bytes to <peer name>

Meaning: Specifies the number of bytes being sent to the peer.

Action: No action required.

Message: sending to peer <peer>

Meaning: BGP updates are being sent to the specified peer.

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-updates.fm
    HTML File Name: bgp-updates.html
    Last Updated: 09/26/06 at 14:21:04

Please email suggestions and comments to: doc@avici.com