3.2.3 BGP4 [SL-L3A]

The following table gives the event information for IPv4 routing protocol information (RTM).

Table 3-4 IPv4 Routing Protocol (BGP4) EventInformation
No.	Message text	Description
1	bgp_check_auth: Synchronization failure with BGP task <task name>	Error (remote device)
1		The value of the header marker of the message received by BGP4 task is invalid. [Explanation of message variables] <task name>: BGP4 task name [Action] Check the unicast routing program (BGP4) in the peer.
2	bgp_trace: Unsupported BGP version <version>!!!	Error (local device)
2	bgp_trace: Unsupported BGP version <version>!!!	The BGP version number in control data was invalid. The unicast routing program automatically restarts. [Explanation of message variables] <version>: BGP version number in control data [Action] Take appropriate action by following the rtm aborted log.
3	bgp_log_notify: Notify message received from <bgp name> [(<description>)] is truncated (length <length>)	Error (remote device)
3		The length of the NOTIFICATION message received from the relevant peer was invalid. [Explanation of message variables] <bgp name>: Source peer name <description>: Description name of the source peer <length>: Received data length [Action] Check the unicast routing program (BGP4) in the peer.
4	bgp_send: Sending <length> bytes to <bgp name> [(<description>)] blocked (no spooling requested): <error string>	Warning (local device)
4		An attempt to send a message to the relevant peer failed because the socket buffer becomes full. [Explanation of message variables] <length>: Send request message length <bgp name>: Target peer name <description>: Description name of the destination peer <error string>: Error cause [Action] If this error frequently occurs, determine the cause of the error.
5	bgp_send: Sending <length> bytes to <bgp name> [(<description>)] failed: <error string>	Warning (local device)
5		An attempt to send a message to the relevant peer has failed. [Explanation of message variables] <length>: Send request message length <bgp name>: Target peer name <description>: Description name of the destination peer <error string>: Error cause [Action] If this error frequently occurs, determine the cause of the error.
6	bgp_send: Sending <length> bytes to <bgp name> [(<description>)]: Connection closed	Warning (local device, remote device, or network)
6		Sending of the message to the peer failed because the connection was disconnected. [Explanation of message variables] <length>: Send request message length <bgp name>: Target peer name <description>: Description name of the destination peer [Action] If this error occurs frequently, check the cause of the disconnection.
7	bgp_send: Sending to <bgp name> [(<description>)] looping: <error string>	Warning (local device)
7		An attempt to send a message to the relevant peer has timed out. [Explanation of message variables] <bgp name>: Target peer name <description>: Description name of the destination peer <error string>: Error cause [Action] If this error frequently occurs, determine the cause of the error.
8	bgp_send_open: Internal error! peer <bgp name> [(<description>)], version <version>	Error (local device)
8		The BGP version number of the OPEN message to be sent to the relevant peer was invalid. The unicast routing program automatically restarts. [Explanation of message variables] <bgp name>: Target peer name <description>: Description name of the destination peer <version>: BGP version number in the send message [Action] Take appropriate action by following the rtm aborted log.
9	bgp_path_attr_error from <routine>: Update error subcode <code> (<error string>) for peer <bgp name> [(<description>)] detected. <length> bytes error data - 1st five: <error data>	Error (remote device)
9		An error was detected in the UPDATE message received from the relevant peer. [Explanation of message variables] <routine>: Internal routine name <code> (<error string>): Error cause <bgp name>: Source peer name <description>: Description name of the source peer <length>: Error data length <error data>: First five bytes of error data [Action] Check the unicast routing program (BGP4) in the peer.
10	bgp_recv: Read from peer <bgp name> [(<description>)] failed: <error string>	Warning (local device)
10		An attempt to receive a message from the relevant peer failed. [Explanation of message variables] <bgp name>: Source peer name <description>: Description name of the source peer <error string>: Error cause [Action] If this error frequently occurs, determine the cause of the error.
11	bgp_recv: Peer <bgp name> [(<description>)]: Received unexpected EOF	Warning (local device, remote device, or network)
11		An attempt to receive a message from the relevant peer failed due to disconnection. [Explanation of message variables] <bgp name>: Source peer name <description>: Description name of the source peer [Action] If this error occurs frequently, check the cause of the disconnection.
12	bgp_read_message: Peer <bgp name> [(<description>)]: <message type> message arrived with length <length>	Error (remote device)
12		An invalid-length message was received from the relevant peer. [Explanation of message variables] <bgp name>: Source peer name <description>: Description name of the source peer <message type>: Received message type invalid, Open, Update, Notification, KeepAlive <length>: Received data length [Action] Check the unicast routing program (BGP4) in the peer.
13	bgp_read_message: Peer <bgp name> [(<description>)]: <message type1> arrived, expected <message type2> [or <message type2> ]	Error (remote device)
13		A message whose message type is inappropriate for the current state was received from the relevant peer. [Explanation of message variables] <bgp name>: Source peer name <description>: Description name of the source peer <message type1>: Received message type invalid, Open, Update, Notification, KeepAlive <message type2>: Message type appropriate for the current state invalid, Open, Update, Notification, KeepAlive [Action] Check the unicast routing program (BGP4) in the peer.
14	bgp_get_open: Peer <bgp name> [(<description>)]: Received short version <version> message (<length> octets)	Error (remote device)
14		An invalid-length OPEN message was received from the relevant peer. [Explanation of message variables] <bgp name>: Source peer name <description>: Description name of the source peer <version>: BGP version number in the received message <length>: Received data length [Action] Check the unicast routing program (BGP4) in the peer.
15	bgp_get_open: Received unsupported version <version> message from peer <bgp name> [(<description>)]	Warning (remote device)
15		An OPEN message that has an unsupported BGP version was received from a peer. [Explanation of message variables] <version>: BGP version number of received messages <bgp name>: Source peer name <description>: Description name of the source peer [Action] Make sure that the peer supports BGP version 4.
16	bgp_get_open: Peer <bgp name> [(<description>)]: Hold time too small (<holdtime>)	Error (remote device)
16		An OPEN message whose hold time is less than three seconds was received from the relevant peer. [Explanation of message variables] <bgp name>: Source peer name <description>: Description name of the source peer <holdtime>: Hold time in the received message [Action] Check the peer configuration.
17	bgp_get_open: Peer <bgp name> [(<description>)]: Invalid BGP identifier <router id>	Error (remote device)
17		An OPEN message that has an invalid BGP identifier was received from the relevant peer. [Explanation of message variables] <bgp name>: Source peer name <description>: Description name of the source peer <router id>: BGP identifier in the received message [Action] Check the unicast routing program (BGP4) in the peer.
18	bgp_get_open: Peer <bgp name> [(<description>)]: Unsupported optional parameter <option>	Error (remote device)
18		An OPEN message that contains an invalid option code was received from the relevant peer. [Explanation of message variables] <bgp name>: Source peer name <description>: Description name of the source peer <option>: Option code in the received message [Action] Check the unicast routing program (BGP4) in the peer.
19	bgp_recv_open: Peer <bgp name> [(<description>)] claims AS <as1>, <as2> configured	Warning (local device or remote device)
19		An OPEN message that has a different AS number than the configured AS number was received from the relevant peer. [Explanation of message variables] <bgp name>: Source peer name <description>: Description name of the source peer <as1>: AS number of the received message <as2>: AS number of the peer in the configuration [Action] Check the configuration.
20	bgp_recv_open: Peer <bgp name> [(<description>)] accepted mismatched versions: Peer <version1> this system <version2>	Warning (remote device)
20		A KEEPALIVE message that has a mismatched BGP version number was received from the relevant peer. [Explanation of message variables] <bgp name>: Source peer name <description>: Description name of the source peer <version1>: Remote BGP version number <version2>: Local BGP version number [Action] Make sure that the peer supports BGP version 4.
21	bgp_pp_recv: No group for <bgpp name> found, dropping peer	Warning (local device or remote device)
21	bgp_pp_recv: No group for <bgpp name> found, dropping peer	An OPEN message was received from a peer that was not set. [Explanation of message variables] <bgpp name>: Source peer name [Action] Check the configuration.
22	bgp_pp_recv: Rejecting connection from <bgp name> [(<description>)], peer in state <state>	Warning (remote device or network)
22		An OPEN message was received from the relevant peer during the Idle, OpenConfirm, or Established state. [Explanation of message variables] <bgp name>: Source peer name <description>: Description name of the source peer <state>: Peer state Idle, OpenConfirm, Established [Action] The connection has become unstable. If this error occurs frequently, check the cause of the instability.
23	bgp_pp_recv: Dropping <bgpp name> version <version>, <bgp name> [(<description>)] wants version 4	Warning (remote device)
23		An OPEN message that has an unsupported BGP version was received from a peer. [Explanation of message variables] <bgpp name>, <bgp name>: Source peer name <version>: BGP version number of received messages <description>: Description name of the source peer [Action] Check the BGP version supported by the peer.
24	bgp_pp_recv: Peer <bgp name> [(<description>)] sent unexpected extra data, probably insane	Error (remote device)
24		Unnecessary data is appended to the message from the relevant peer. [Explanation of message variables] <bgp name>: Source peer name <description>: Description name of the source peer [Action] Check the unicast routing program (BGP4) in the peer.
25	bgp_check_capability_match: Capability of peer <bgp name> [(<description>)] is unmatched	Warning (remote device)
25		The capability settings specified for the Switch are not specified for the relevant peer. [Explanation of message variables] <bgp name>: Source peer name <description>: Description name of the source peer [Action] Check the configuration.
26	bgp_write_flush: Sending <length1> (sent <length2>) bytes to <bgp name> [(<description>)] failed: <error string>	Warning (local device)
26		An attempt to send a message to the relevant peer has failed. [Explanation of message variables] <length1>: Send request data length <length2>: Sent data length <bgp name>: Target peer name <description>: Description name of the destination peer <error string>: Error cause [Action] If this error frequently occurs, determine the cause of the error.
27	bgp_write_flush: Sending <length1> (sent <length2>) bytes to <bgp name> [(<description>)]: Connection closed	Warning (local device, remote device, or network)
27		Sending of the message to the peer failed because the connection was disconnected. [Explanation of message variables] <length1>: Send request data length <length2>: Sent data length <bgp name>: Target peer name <description>: Description name of the destination peer [Action] If this error occurs frequently, check the cause of the disconnection.
28	bgp_write_flush: Sending to <bgp name> [(<description>)] (sent <length1>, <length2> remain[s]) looping: <error string>	Warning (local device)
28		An attempt to send a message to the relevant peer has timed out. [Explanation of message variables] <bgp name>: Target peer name <description>: Description name of the destination peer <length1>: Length of the sent data <length2>: Length of the data that remains unsent <error string>: Error cause [Action] If this error frequently occurs, determine the cause of the error.
29	bgp_peer_connected: task_get_addr_local(<bgp name> [(<description>)]): <error string>	Warning (local device)
29		Extraction of the local address used for establishing a connection to the relevant peer failed. [Explanation of message variables] <bgp name>: Connection target peer name <description>: Description name of the connection target peer <error string>: Error cause [Action] If this error frequently occurs, determine the cause of the error.
30	bgp_connect_start: Peer <bgp name> [(<description>)] local address <ipv4 address> unavailable, connection failed	Warning (local device)
30		An attempt to establish a connection failed because the local address used for establishing a connection to the relevant peer could not be used (bind failure). [Explanation of message variables] <bgp name>: Connection target peer name <description>: Description name of the connection target peer <ipv4 address>: Local address used for peering [Action] If this error frequently occurs, determine the cause of the error.
31	bgp_traffic_timeout: Holdtime expired for <bgp name> [(<description>)]	Warning (remote device or network)
31		A hold timeout for the relevant peer occurred. [Explanation of message variables] <bgp name>: Connection target peer name <description>: Description name of the connection target peer [Action] Check the unicast routing program (BGP4) in the peer.
32	bgp_traffic_timeout: Error sending KEEPALIVE to <bgp name> [(<description>)]: <error string>	Warning (local device)
32		An attempt to send a KEEPALIVE message to the relevant peer failed. [Explanation of message variables] <bgp name>: Target peer name <description>: Description name of the destination peer <error string>: Error cause [Action] If this error frequently occurs, determine the cause of the error.
33	bgp_listen_accept: accept(<socket>): <error string>	Warning (local device)
33	bgp_listen_accept: accept(<socket>): <error string>	An attempt to accept the connection failed. [Explanation of message variables] <socket>: Socket descriptor number <error string>: Error cause [Action] If this error frequently occurs, determine the cause of the error.
34	bgp_listen_accept: task_get_addr_local() failed, terminating!!	Error (local device)
34		Extraction of the local address used for establishing a connection failed. The connection will be closed. [Explanation of message variables] None. [Action] If this error frequently occurs, check the unicast routing program (BGP4) in the peer.
35	bgp_listen_start: Couldn't get BGP listen socket!!	Error (local device)
35	bgp_listen_start: Couldn't get BGP listen socket!!	An attempt to create a socket for establishing a connection failed. The unicast routing program automatically restarts. [Explanation of message variables] None. [Action] Take appropriate action by following the rtm aborted log.
36	bgp_listen_start: listen: <error string>	Error (local device)
36	bgp_listen_start: listen: <error string>	Preparation for accepting a connection failed. The unicast routing program automatically restarts. [Explanation of message variables] <error string>: Error cause [Action] Take appropriate action by following the rtm aborted log.
37	bgp_set_peer_if: BGP peer <bgp name> [(<description>)] interface not found. Leaving peer idled	Warning (local device)
37		The interface connected to the relevant peer was not found. [Explanation of message variables] <bgp name>: Connection target peer name <description>: Description name of the connection target peer [Action] Check the configuration.
38	bgp_set_peer_if: BGP peer <bgp name> [(<description>)] local address <ipv4 address> not on shared net. Leaving peer idled	Warning (local device)
38		The local address used for establishing a connection to the relevant peer is not in the same network. [Explanation of message variables] <bgp name>: Connection target peer name <description>: Description name of the connection target peer <ipv4 address>: Local address used for establish a connection [Action] Check the configuration.
39	bgp_pp_timeout: Peer <bgpp name> timed out waiting for OPEN	Warning (remote device or network)
39		The timer for waiting for an OPEN message from the relevant peer timed out. [Explanation of message variables] <bgpp name>: Connection target peer name [Action] Check the unicast routing program (BGP4) in the peer.
40	bgp_peer_init: BGP peer <bgp name> [(<description>)] local address <ipv4 address> not found. Leaving peer idled	Warning (local device)
40		The interface for the local address used for establishing a connection to the relevant peer is not found. [Explanation of message variables] <bgp name>: Connection target peer name <description>: Description name of the connection target peer <ipv4 address>: Local address used for establish a connection [Action] Check the configuration.
41	bgp_recv_v4_update: Peer <bgp name> [(<description>)]: Strange message header length <length>	Error (remote device)
41		The message length in the message header of a message received from the relevant peer is invalid. [Explanation of message variables] <bgp name>: Source peer name <description>: Description name of the source peer <length>: Message length of the received message header [Action] Check the unicast routing program (BGP4) in the peer.
42	bgp_recv_v4_update: Peer <bgp name> [(<description>)] unrecognized message type <type>	Error (remote device)
42		The message type of a message received from the relevant peer is invalid. [Explanation of message variables] <bgp name>: Source peer name <description>: Description name of the source peer <type>: Message type [Action] Check the unicast routing program (BGP4) in the peer.
43	bgp_recv_v4_update: Received OPEN message from <bgp name> [(<description>)], state is ESTABLISHED	Warning (remote device or network)
43		An OPEN message was receive from the relevant peer in the ESTABLISHED state. [Explanation of message variables] <bgp name>: Source peer name <description>: Description name of the source peer [Action] The connection has become unstable. If this error occurs frequently, check the cause of the instability.
44	bgp_recv_v4_update: Peer <bgp name> [(<description>)] UPDATE length <length> too small	Error (remote device)
44		The length of the UPDATE message from the relevant peer is too short. [Explanation of message variables] <bgp name>: Source peer name <description>: Description name of the source peer <length>: Received data length [Action] Check the unicast routing program (BGP4) in the peer.
45	bgp_recv_v4_update: Peer <bgp name> [(<description>)] UPDATE unreachable prefix length <length1> exceeds packet length <length2>	Error (remote device)
45		The prefix length of unreachable routing information of the UPDATE message from the relevant peer exceeds the packet length. [Explanation of message variables] <bgp name>: Source peer name <description>: Description name of the source peer <length1>: Prefix length of unreachable routing information in the received message <length2>: Received packet length [Action] Check the unicast routing program (BGP4) in the peer.
46	bgp_recv_v4_update: Peer <bgp name> [(<description>)] UPDATE zero attribute length followed by <length> bytes of garbage	Error (remote device)
46		The attribute length of the UPDATE message from the relevant peer is 0 even though actual data exists. [Explanation of message variables] <bgp name>: Source peer name <description>: Description name of the source peer <length>: Actual data length [Action] Check the unicast routing program (BGP4) in the peer.
47	bgp_recv_v4_update: Peer <bgp name> [(<description>)] UPDATE path attribute length <length1> too large (<length2> bytes remaining)	Error (remote device)
47		The path attribute length of the UPDATE message from the relevant peer is too long compared to the actual path attribute length. [Explanation of message variables] <bgp name>: Source peer name <description>: Description name of the source peer <length1>: Path attribute length of the received message <length2>: Entity data length [Action] Check the unicast routing program (BGP4) in the peer.
48	bgp_recv_v4_update: Peer <bgp name> [(<description>)] UPDATE no next hop found	Error (remote device)
48		The next-hop attribute is not found in the UPDATE message from the relevant peer. [Explanation of message variables] <bgp name>: Source peer name <description>: Description name of the source peer [Action] Check the unicast routing program (BGP4) in the peer.
49	bgp_recv_v4_update: External peer <bgp name> [(<description>)] UPDATE included LOCALPREF attribute	Error (remote device)
49		The LOCALPREF attribute is included in the UPDATE message from the relevant external peer. [Explanation of message variables] <bgp name>: Source peer name <description>: Description name of the source peer [Action] Check the unicast routing program (BGP4) in the peer.
50	bgp_recv_v4_update: Peer <bgp name> [(<description>)] UPDATE no LOCALPREF attribute found	Error (remote device)
50		The LOCALPREF attribute is not found in the UPDATE message from the relevant internal peer. [Explanation of message variables] <bgp name>: Source peer number <description>: Description name of the source peer [Action] Check the unicast routing program (BGP4) in the peer.
51	bgp_recv_v4_update: Peer <bgp name> [(<description>)] UPDATE has path attributes but no reachable prefixes!	Error (remote device)
51		The UPDATE message from the relevant peer has path attributes but has no reachability information. [Explanation of message variables] <bgp name>: Source peer name <description>: Description name of the source peer [Action] Check the unicast routing program (BGP4) in the peer.
52	bgp_recv_v4_unreach: Peer <bgp name> [(<description>)] UPDATE: Invalid unreachable prefix length <length>	Error (remote device)
52		The prefix length of unreachable routing information of the UPDATE message received from the relevant peer is invalid. [Explanation of message variables] <bgp name>: Source peer name <description>: Description name of the source peer <length>: Prefix length in received messages [Action] Check the unicast routing program (BGP4) in the peer.
53	bgp_recv_v4_unreach: Peer <bgp name> [(<description>)] UPDATE: Prefix length <length1> exceeds unreachable prefix data remaining (<length2> bytes)	Error (remote device)
53		The prefix length of unreachable routing information of the UPDATE message received from the relevant peer exceeds the prefix data of unreachable routing information. [Explanation of message variables] <bgp name>: Source peer name <description>: Description name of the source peer <length1>: Prefix length in received messages <length2>: Entity data length [Action] Check the unicast routing program (BGP4) in the peer.
54	bgp_recv_v4_unreach: Peer <bgp name> [(<description>)] UPDATE: Ignoring unreachable route with two or more labels (<length1> of <length2>)	Warning (remote device)
54		Routes of unreachable routing information that has multiple labels of the UPDATE message received from the relevant peer are ignored [Explanation of message variables] <bgp name>: Source peer name <description>: Description name of the source peer <length1> of <length2>: The location of invalid information in the message [Action] Check the unicast routing program (BGP4) in the peer.
55	bgp_recv_v4_unreach: Peer <bgp name> [(<description>)] UPDATE: Ignoring unreachable route with RD 0 prefix (<length1> of <length2>)	Error (remote device)
55		Routes of unreachable routing information that has RD 0 of the UPDATE message received from the relevant peer are ignored. [Explanation of message variables] <bgp name>: Source peer name <description>: Description name of the source peer <length1> of <length2>: The location of invalid information in the message [Action] Check the unicast routing program (BGP4) in the peer.
56	bgp_recv_v4_unreach: Peer <bgp name> [(<description>)] UPDATE: Ignoring invalid unreachable route <ipv4 address>/<mask> (<length1> of <length2>)	Error (remote device)
56		Invalid routes of unreachable routing information of the UPDATE message received from the relevant peer are ignored. [Explanation of message variables] <bgp name>: Source peer name <description>: Description name of the source peer <ipv4 address>: Destination address of unreachable routing information <mask>: Network mask of unreachable routing information <length1> of <length2>: The location of invalid information in the message [Action] Check the unicast routing program (BGP4) in the peer.
57	bgp_recv_v4_reach: Peer <bgp name> [(<description>)] AS <as1> received path with first AS <as2>	Error (remote device)
57		The AS path whose next- hop AS number is <as2> was received from the peer whose AS number is <as1>. [Explanation of message variables] <bgp name>: Source peer name <description>: Description name of the source peer <as1>: AS number of the source peer <as2>: Next-hop AS number in the received message [Action] Check the unicast routing program (BGP4) in the peer.
58	bgp_recv_v4_reach: Peer <bgp name> [(<description>)] UPDATE: Invalid prefix length <length>	Error (remote device)
58		The prefix length of the UPDATE message received from the relevant peer is invalid. [Explanation of message variables] <bgp name>: Source peer name <description>: Description name of the source peer <length>: Prefix length in received messages [Action] Check the unicast routing program (BGP4) in the peer.
59	bgp_recv_v4_reach: Peer <bgp name> [(<description>)] UPDATE: Prefix length <length1> exceeds prefix data remaining (<length2> bytes)	Error (remote device)
59		The prefix length of the UPDATE message received from the relevant peer exceeds the actual prefix length. [Explanation of message variables] <bgp name>: Source peer name <description>: Description name of the source peer <length1>: Prefix length in received messages <length2>: Actual prefix length [Action] Check the unicast routing program (BGP4) in the peer.
60	bgp_recv_v4_reach: Peer <bgp name> [(<description>)] UPDATE: Ignoring route with two or more labels (<length1> of <length2>)	Warning (remote device)
60		Routes that have multiple labels of the UPDATE message received from the relevant peer are ignored. [Explanation of message variables] <bgp name>: Source peer name <description>: Description name of the source peer <length1> of <length2>: The location of invalid information in the received message. [Action] Check the unicast routing program (BGP4) in the peer.
61	bgp_recv_v4_reach: Peer <bgp name> [(<description>)] UPDATE: Ignoring route with RD 0 prefix (<length1> of <length2>)	Error (remote device)
61		Routes that have RD 0 of the UPDATE message received from the relevant peer are ignored. [Explanation of message variables] <bgp name>: Source peer name <description>: Description name of the source peer <length1> of <length2>: The location of invalid information in the received message. [Action] Check the unicast routing program (BGP4) in the peer.
62	bgp_recv_v4_reach: Peer <bgp name> [(<description>)] UPDATE:Included invalid route <ipv4 address>/<mask> (<length1> of <length2>)	Error (remote device)
62		The UPDATE message received from the relevant peer includes invalid routes. [Explanation of message variables] <bgp name>: Source peer name <description>: Description name of the source peer <ipv4 address>: Destination address <mask>: Network mask <length1> of <length2>: The location of invalid information in the received message. [Action] Check the unicast routing program (BGP4) in the peer.
63	bgp_recv_v4_reach: Ignoring network 0 route <ipv4 address>/<mask> from peer <bgp name> [(<description>)] (<length1> of <length2>)	Warning (remote device)
63		Routes addressed to network 0 from the relevant peer are ignored. [Explanation of message variables] <ipv4 address>: Destination address <mask>: Network mask <bgp name>: Source peer name <description>: Description name of the source peer <length1> of <length2>: The location of invalid information in the received message. [Action] Check the unicast routing program (BGP4) in the peer.
64	bgp_recv_v4_reach: Ignoring loopback route from peer <bgp name> [(<description>)] (<length1> of <length2>)	Warning (remote device)
64		Loopback routes from the relevant peer are ignored. [Explanation of message variables] <bgp name>: Source peer name <description>: Description name of the source peer <length1> of <length2>: The location of invalid information in the received message. [Action] Check the unicast routing program (BGP4) in the peer.
65	bgp_recv_mp_unreach: Peer <bgp name> [(<description>)] UPDATE: Invalid length of MP_UNREACH_NLRI attribute(<length>) : No address family	Error (remote device)
65		The length of the MP_UNREACH_NLRI attribute for the UPDATE message received from the peer is invalid. No address family exists. [Explanation of message variables] <bgp name>: Source peer name <description>: Description name of the source peer <length>: Received MP_UNREACH_NLRI attribute length [Action] Check the unicast routing program (BGP4) in the peer.
66	bgp_recv_mp_unreach: Peer <bgp name> [(<description>)] UPDATE: Invalid address family (<address family>) in MP_UNREACH_NLRI attribute	Error (remote device)
66		The address family of the MP_UNREACH_NLRI attribute for the UPDATE message received from the peer is invalid. [Explanation of message variables] <bgp name>: Source peer name <description>: Description name of the source peer <address family>: Address family information of the received MP_UNREACH_NLRI attribute [Action] Check the unicast routing program (BGP4) in the peer.
67	bgp_recv_mp_reach: Peer <bgp name> [(<description>)] UPDATE: Invalid length of MP_REACH_NLRI attribute(<length>) : No address family	Error (remote device)
67		The length of the MP_REACH_NLRI attribute for the UPDATE message received from the peer is invalid. No address family exists. [Explanation of message variables] <bgp name>: Source peer name <description>: Description name of the source peer <length>: Received MP_REACH_NLRI attribute length [Action] Check the unicast routing program (BGP4) in the peer.
68	bgp_recv_mp_reach: Peer <bgp name> [(<description>)] UPDATE: Invalid address family(<address family>) in MP_REACH_NLRI attribute	Error (remote device)
68		The address family of the MP_REACH_NLRI attribute for the UPDATE message received from the relevant peer is invalid. [Explanation of message variables] <bgp name>: Source peer name <description>: Description name of the source peer <address family>: Address family information of the received MP_REACH_NLRI attribute [Action] Check the unicast routing program (BGP4) in the peer.
69	bgp_recv_mp_reach: Peer <bgp name> [(<description>)] UPDATE: Invalid length of MP_REACH_NLRI attribute(<length>) : No nexthop length	Error (remote device)
69		The length of the MP_REACH_NLRI attribute for the UPDATE message received from the peer is invalid. No next-hop length exists. [Explanation of message variables] <bgp name>: Source peer name <description>: Description name of the source peer <length>: Received MP_REACH_NLRI attribute length [Action] Check the unicast routing program (BGP4) in the peer.
70	bgp_recv_mp_reach: Peer <bgp name> [(<description>)] UPDATE: Invalid nexthop length(<length>) in MP_REACH_NLRI attribute	Error (remote device)
70		The next-hop length of the MP_REACH_NLRI attribute for the UPDATE message received from the peer is invalid. [Explanation of message variables] <bgp name>: Source peer name <description>: Description name of the source peer <length>: Next-hop length of the received MP_REACH_NLRI attribute [Action] Check the unicast routing program (BGP4) in the peer.
71	bgp_recv_mp_reach: Peer <bgp name> [(<description>)] UPDATE: Invalid length of MP_REACH_NLRI attribute(<length>) : No nexthop	Error (remote device)
71		The length of the MP_REACH_NLRI attribute for the UPDATE message received from the peer is invalid. No next hop exists. [Explanation of message variables] <bgp name>: Source peer name <description>: Description name of the source peer <length>: Received MP_REACH_NLRI attribute length [Action] Check the unicast routing program (BGP4) in the peer.
72	bgp_recv_mp_reach: Peer <bgp name> [(<description>)] UPDATE: Invalid rd of nexthop (<rd1>:<rd2>) in MP_REACH_NLRI attribute	Error (remote device)
72		The next-hop RD of the MP_REACH_NLRI attribute for the UPDATE message received from the peer is invalid. [Explanation of message variables] <bgp name>: Source peer name <description>: Description name of the source peer <rd1>:<rd2>: Next-hop RD of the received MP_REACH_NLRI attribute [Action] Check the unicast routing program (BGP4) in the peer.
73	bgp_recv_mp_reach: Peer <bgp name> [(<description>)] UPDATE: Invalid length of MP_REACH_NLRI attribute(<length>) : No reserved	Error (remote device)
73		The length of the MP_REACH_NLRI attribute for the UPDATE message received from the peer is invalid. No reserved field exists. [Explanation of message variables] <bgp name>: Source peer name <description>: Description name of the source peer <length>: Received MP_REACH_NLRI attribute length [Action] Check the unicast routing program (BGP4) in the peer.
74	bgp_recv_mp_reach: Peer <bgp name> [(<description>)] UPDATE: Invalid length of MP_REACH_NLRI attribute(<length>) : No snpa length	Error (remote device)
74		The length of the MP_REACH_NLRI attribute for the UPDATE message received from the peer is invalid. No SNPA length exists. [Explanation of message variables] <bgp name>: Source peer name <description>: Description name of the source peer <length>: Received MP_REACH_NLRI attribute length [Action] Check the unicast routing program (BGP4) in the peer.
75	bgp_recv_mp_reach: Peer <bgp name> [(<description>)] UPDATE: Invalid length of MP_REACH_NLRI attribute(<length>) : No snpa	Error (remote device)
75		The length of the MP_REACH_NLRI attribute for the UPDATE message received from the peer is invalid. No SNPA exists. [Explanation of message variables] <bgp name>: Source peer name <description>: Description name of the source peer <length>: Received MP_REACH_NLRI attribute length [Action] Check the unicast routing program (BGP4) in the peer.
76	bgp_peer_established: Peer <bgp name> [(<description>)] connection established	Information (local or remote device)
76		A BGP4 connection was established with the relevant peer. [Explanation of message variables] <bgp name>: Connection target peer name <description>: Description name of the connection target peer [Action] None.
77	bgp_ifachange: Peer <bgp name> [(<description>)]: Closed connection by changing interface state	Information (local or remote device)
77		A BGP4 connection was closed due to a change in the interface state. [Explanation of message variables] <bgp name>: Connection target peer name <description>: Description name of the connection target peer [Action] Check the cause of the change in the interface state.
78	bgp_terminate: Peer <bgp name> [(<description>)]: Closed connection by terminating bgp	Information (local device)
78		A BGP4 connection was closed due to the termination of a BGP4 task. [Explanation of message variables] <bgp name>: Connection target peer name <description>: Description name of the connection target peer [Action] Check the cause of the termination of BGP4 task.
79	bgp_peer_delete: Peer <bgp name> [(<description>)]: Closed connection by changing configuration	Information (local device)
79		A BGP4 connection was closed due to a change in the configuration (deletion of peer information). [Explanation of message variables] <bgp name>: Connection target peer name <description>: Description name of the connection target peer [Action] None.
80	bgp_init: Peer <bgp name> [(<description>)]: Closed connection by changing configuration	Information (local device)
80		A BGP4 connection was closed due to a change in the configuration. [Explanation of message variables] <bgp name>: Connection target peer name <description>: Description name of the connection target peer [Action] None.
81	bgp_peer_clear: Peer <bgp name> [(<description>)]: Closed connection by clearing peer	Information (local device)
81		A BGP4 connection was closed by entering the clear ip bgp command. [Explanation of message variables] <bgp name>: Connection target peer name <description>: Description name of the connection target peer [Action] None.
82	bgp_pp_recv: Peer <bgp name> in graceful-restart failed to retain stale routes, deleting all the stale routes from the peer	Error (remote device)
82		A peer that executed a graceful restart failed to save the forwarding path. All the paths learned from the relevant peer will be deleted. [Explanation of message variables] <bgp name>: Connection target peer name [Action] Check the unicast routing program (BGP4) in the peer.
83	bgp_recv_open: Peer <bgp name> in graceful-restart failed to retain stale routes, deleting all the stale routes from the peer	Error (remote device)
83		A peer that executed a graceful restart failed to save the forwarding path. All the paths learned from the relevant peer will be deleted. [Explanation of message variables] <bgp name>: Connection target peer name [Action] Check the unicast routing program (BGP4) in the peer.
84	bgp_restart_timeout: Peer <bgp name> [(<description>)]: Timed out waiting for reconnect.	Error (local or remote device)
84		A graceful restart failed. A connection to the peer router could not be established within the restart-time specified by the peer router. [Explanation of message variables] <bgp name>: Connection target peer name <description>: Description name of the connection target peer [Action] Check if a communication can be established with the peer router. Check if BGP is running on the peer router. If the peer router is running, increase the restart-time value of the peer router so that the peer router can recover and establish a connection.
85	bgp_restart_timeout: Peer <bgp name> [(<description>)]: Timed out waiting for End-Of-RIB marker from restart router.	Error (remote device)
85		A graceful restart failed. End-Of-RIB could not be received from the peer router. [Explanation of message variables] <bgp name>: Connection target peer name <description>: Description name of the connection target peer [Action] Check if BGP is running on the relevant peer router. If it is running, increase the stalepath-time value.
86	bgp_peer_established: Peer <bgp name> [(<description>)] connection established with graceful restart.	Information (local or remote device)
86		A BGP connection with the relevant peer was re-established. [Explanation of message variables] <bgp name>: Connection target peer name <description>: Description name of the connection target peer [Action] None.
87	bgp_receive_End-Of-RIB: End-Of-RIB marker received from <bgp name> [(<description>)].	Information (local device)
87		End-Of-RIB was received. [Explanation of message variables] <bgp name>: Source peer name <description>: Description name of the source peer [Action] None.
88	bgp_send_End-Of-RIB: End-Of-RIB marker sent to <bgp name> [(<description>)].	Information (local device)
88		End-Of-RIB was sent. [Explanation of message variables] <bgp name>: Target peer name <description>: Description name of the destination peer [Action] None.
89	BGP: NOTIFICATION sent to <bgp name> [(<description>)]: code <code> (<code string>) [subcode <subcode> (<subcode string>)] [value <value>] [data <data>]	Warning (remote device)
89		A NOTIFICATION message was sent to the relevant peer. [Explanation of message variables] <bgp name>: Target peer name <description>: Description name of the destination peer <code> (<code string>), <subcode> (<subcode string>): The following error codes and subcodes: Error code 1 (Message Header Error) - Error subcode 1 (lost connection synchronization) - Error subcode 2 (bad length) - Error subcode 3 (bad message type) Error code 2 (Open Message Error) - Error subcode 0 (unspecified error) - Error subcode 1 (unsupported version) - Error subcode 2 (bad AS number) - Error subcode 3 (bad BGP ID) - Error subcode 4 (unsupported optional parameter) - Error subcode 6 (unacceptable holdtime) Error code 3 (Update Message Error) - Error subcode 1 (invalid attribute list) - Error subcode 2 (unknown well known attribute) - Error subcode 3 (missing well known attribute) - Error subcode 4 (attribute flags error) - Error subcode 5 (bad attribute length) - Error subcode 6 (bad ORIGIN attribute) - Error subcode 9 (error with optional attribute) - Error subcode 10 (bad address or prefix field) - Error subcode 11 (AS path attribute problem) Error code 4 (Hold Timer Expired Error) Error code 5 (Finite State Machine Error) Error code 6 (Cease) - If the <code> value is invalid, invalid is displayed for <code string>.- If the <subcode> value is invalid, unknown is displayed for <subcode string>. - Information in the data field of the Notification message is displayed for <value> or <data>. <value>: Decimal representation <data>: Hexadecimal representation [Action] Check the network configuration and peer configuration. If there is no problem with them, check the unicast routing program (BGP4) in the peer.
90	BGP: NOTIFICATION received from <bgp name> [(<description>)]: code <code> (<code string>) [subcode <subcode> (<subcode string>)] [value <value>] [data <data>]	Warning (local device)
90		A NOTIFICATION message was received from the relevant peer. [Explanation of message variables] <bgp name>: Source peer name <description>: Description name of the source peer <code> (<code string>), <subcode> (<subcode string>): The following error codes and subcodes: Error code 1 (Message Header Error) - Error subcode 1 (lost connection synchronization) - Error subcode 2 (bad length) - Error subcode 3 (bad message type) Error code 2 (Open Message Error) - Error subcode 0 (unspecified error) - Error subcode 1 (unsupported version) - Error subcode 2 (bad AS number) - Error subcode 3 (bad BGP ID) - Error subcode 4 (unsupported optional parameter) - Error subcode 6 (unacceptable holdtime) - Error subcode 7 (unsupported capability) Error code 3 (Update Message Error) - Error subcode 1 (invalid attribute list) - Error subcode 2 (unknown well known attribute) - Error subcode 3 (missing well known attribute) - Error subcode 4 (attribute flags error) - Error subcode 5 (bad attribute length) - Error subcode 6 (bad ORIGIN attribute) - Error subcode 7 (AS loop detected) - Error subcode 8 (invalid NEXT_HOP) - Error subcode 9 (error with optional attribute) - Error subcode 10 (bad address or prefix field) - Error subcode 11 (AS path attribute problem) Error code 4 (Hold Timer Expired Error) Error code 5 (Finite State Machine Error) Error code 6 (Cease) - If the <code> value is invalid, invalid is displayed for <code string>.- If the <subcode> value is invalid, unknown is displayed for <subcode string>. - Information in the data field of the Notification message is displayed for <value> or <data>. <value>: Decimal representation <data>: Hexadecimal representation [Action] Check the network configuration and peer configuration.
91	BGP: No MD5 digest from <source ipv4>+<port no.> to <destination ipv4>+<port no.> [VRF <vrf id>]	Warning (remote device)
91		The MD5 authentication option is not set for the TCP segment received by BGP4 connection. This operation message is output according to the following conditions: The messages from the first to the 16th event are output. After 17 times from the beginning of the event occurrence, this message is output once every 256 times the event occurs. If an event occurs 3 minutes or more after the last event occurred, this message is output when 1 or 2 above occurs. Note that the above number of messages includes the count of BGP: Invalid MD5 digest from <source ipv4> + <port no.> to <destination ipv4> + <port no.>. [Explanation of message variables] <source ipv4>: Source IPv4 address <port no.>: TCP port number <destination ipv4>: Destination IPv4 address <vrf id> VRF ID [Action] Check whether the MD authentication is set in BGP4 of the remote system. If it is not set, set the MD authentication so that it matches. If the setting matches, check whether TCP segments are sent from a peer other than the source BGP4 peer.
92	BGP: Invalid MD5 digest from <source ipv4>+<port no.> to <destination ipv4>+<port no.> [VRF <vrf id>]	Warning (local device or remote device)
92		The MD5 authentication option for TCP segments received by BGP4 connection is invalid. This operation message is output according to the following conditions: The messages from the first to the 16th event are output. After 17 times from the beginning of the event occurrence, this message is output once every 256 times the event occurs. If an event occurs 3 minutes or more after the last event occurred, this message is output when 1 or 2 above occurs. Note that the above number of messages includes the count of BGP: No MD5 digest from <source ipv4> + <port no.> to <destination ipv4> + <port no.>. [Explanation of message variables] <source ipv4>: Source IPv4 address <port no.>: TCP port number <destination ipv4>: Destination IPv4 address <vrf id> VRF ID [Action] Check if the MD5 authentication keys match in BGP4 of the local and remote systems. If the MD5 authentication keys do not match, set them so that they do match. If the MD5 authentication keys match, check if TCP segments are sent from a peer other than the source BGP4 peer.
93	BGP: Number of prefix received from <bgp name> [(<description>)]: reached <routes1>, limit <routes2>	Warning (remote device)
93		The number of paths (active paths and inactive paths) learned from the relevant peer exceeded the threshold. [Explanation of message variables] <bgp name>: Source peer name <description>: Description name of the source peer <routes1>: Number of paths learned from peers <routes2>: Maximum number of paths learned from peers [Action] If the number of paths learned from the peer further increases, check the number of the paths advertised by the peer.
94	BGP: Number of prefix received from <bgp name> [(<description>)]: <routes1> exceed limit <routes2>	Warning (remote device)
94		The number of paths (active paths and inactive paths) learned from the relevant peer exceeded the maximum value. [Explanation of message variables] <bgp name>: Source peer name <description>: Description name of the source peer <routes1>: Number of paths learned from peers <routes2>: Maximum number of paths learned from peers [Action] Check the number of the paths advertised by the relevant peer.
95	BGP: Peer <bgp name> [(<description>)]: Closed connection by maximum-prefix	Information (remote device)
95		BGP4 connection was closed due to the limitation of the number of learned paths. [Explanation of message variables] <bgp name>: Connection target peer name <description>: Description name of the connection target peer [Action] Check the number of the paths advertised by the relevant peer. To reconnect the peer, make sure that the number of paths advertised by the peer is equal to or less than the maximum value, and then enter the clear ip bgp command.
96	BGP: Peer <bgp name> [(<description>)] UPDATE included attribute type code (0) [- AS Path (<as number>): <aspath>]	Warning (remote device)
96		An UPDATE message including the path attribute of type code 0 was received from the relevant peer. This operation message is not output again on the same peer for an hour after the previous output. [Explanation of message variables] <bgp name>: Source peer name <description>: Description name of the source peer <as number>: Number of AS numbers <aspath>: AS paths, in the following format: AS sequential number: AS_SEQ {AS sequential number}: AS_SET (AS sequential number): AS_CONFED_SEQUENCE Note that, the entire AS path might not be output because there is a limit to the number of characters that can be output in an operation message. [Action] Check the unicast routing program (BGP4) in the peer.
97	bgp_pp_recv: Peer <bgp name> as receiving-speaker failed to retain stale routes, the packets forwarded to the peer may be discarded.	Warning (remote device)
97		A peer operating as a receiving router could not save the forwarding route. Packets forwarded to the relevant peer may be discarded. [Explanation of message variables] <bgp name>: Connection target peer name [Action] A graceful restart negotiation informed of a forwarding-disabled state. Check to see if the peer router has failed.
98	BGP: Completed the learning from receiving-speakers	Information (local device)
98	BGP: Completed the learning from receiving-speakers	Route learning from the receiving router is complete. [Explanation of message variables] None. [Action] None.
99	BGP: Start advertisement, giving up learning from several receiving-speakers	Information (local device)
99		Interrupts route learning from some receiver routers and starts route advertisement. [Explanation of message variables] None. [Action] None.
100	bgp_recv_open: Peer <bgp name> as receiving-speaker failed to retain stale routes, the packets forwarded to the peer may be discarded.	Warning (remote device)
100		A peer operating as a receiving router could not save the forwarding route. Packets forwarded to the relevant peer may be discarded. [Explanation of message variables] <bgp name>: Connection target peer name [Action] A graceful restart negotiation informed of a forwarding-disabled state. Check to see if the peer router has failed.
101	BGP: A peer connection closed because of a BFD state change. (peer = <bgp name>[ (<description>)])	Information (local device)
101		The connection of the relevant peer was disconnected due to a change in BFD session status. [Explanation of message variables] <bgp name>: Connection target peer name <description>: Description name of the connection target peer [Action] Check BFD session status.