BGP message

3825-1(config)#
*Jan 27 16:00:39.591: BGP: 172.16.2.1 passive open to 172.16.1.1
*Jan 27 16:00:39.591: BGP: 172.16.2.1 went from Active to Idle

The state from Active to Idle was caused by BGP reset using clear ip bgp *

*Jan 27 16:00:39.591: BGP: 172.16.2.1 went from Idle to Connect

The state from Idle to Connect, means 3825-1 is establishing TCP three-way handshake if successful the state will proceed to OPEN.

*Jan 27 16:00:39.595: BGP: 172.16.2.1 rcv message type 1, length (excl. header) 26
*Jan 27 16:00:39.595: BGP: 172.16.2.1 rcv OPEN, version 4, holdtime 180 seconds

TCP TLV message. TLV stands for Type, Length and Version.

BGP message type codes

Type 1: Open – After TCP connection is established, an Open message will start.

Type 2: Update – Routing update either the route is down or up.

Type 3: Notification – When problems happen.

Type 4: Keepalive – Every 60 seconds by default.

*Jan 27 16:00:39.595: BGP: 172.16.2.1 went from Connect to OpenSent

TCP connection established, router is waiting for open message to confirm the parameters.

*Jan 27 16:00:39.595: BGP: 172.16.2.1 sending OPEN, version 4, my as: 64512, holdtime 180 seconds
*Jan 27 16:00:39.595: BGP: 172.16.2.1 rcv OPEN w/ OPTION parameter len: 16
*Jan 27 16:00:39.595: BGP: 172.16.2.1 rcvd OPEN w/ optional parameter type 2 (Capability) len 6
*Jan 27 16:00:39.595: BGP: 172.16.2.1 OPEN has CAPABILITY code: 1, length 4
*Jan 27 16:00:39.595: BGP: 172.16.2.1 OPEN has MP_EXT CAP for afi/safi: 1/1
*Jan 27 16:00:39.595: BGP: 172.16.2.1 rcvd OPEN w/ optional parameter type 2 (Capability) len 2
*Jan 27 16:00:39.595: BGP: 172.16.2.1 OPEN ha
3825-1(config)#end
3825-1#s CAPABILITY code: 128, length 0
*Jan 27 16:00:39.595: BGP: 172.16.2.1 OPEN has ROUTE-REFRESH capability(old) for all address-families
*Jan 27 16:00:39.595: BGP: 172.16.2.1 rcvd OPEN w/ optional parameter type 2 (Capability) len 2
*Jan 27 16:00:39.595: BGP: 172.16.2.1 OPEN has CAPABILITY code: 2, length 0
*Jan 27 16:00:39.595: BGP: 172.16.2.1 OPEN has ROUTE-REFRESH capability(new) for all address-families
BGP: 172.16.2.1 rcvd OPEN w/ remote AS 777
*Jan 27 16:00:39.595: BGP: 172.16.2.1 went from OpenSent to OpenConfirm

All parameters confirmed and agreed by both routers, waiting for keepalive message

*Jan 27 16:00:39.595: BGP: 172.16.2.1 send message type 1, length (incl. header) 45
*Jan 27 16:00:39.611: BGP: 172.16.2.1 went from OpenConfirm to Established

BGP connection fully established.

*Jan 27 16:00:39.611: %BGP-5-ADJCHANGE: neighbor 172.16.2.1 Up
*Jan 27 16:00:40.375: %SYS-5-CONFIG_I: Configured from console by console
3825-1#

 

BGP keepalive message

3825-1#
*Jan 27 16:29:39.958: BGP: 172.16.2.1 sending KEEPALIVE (io)
*Jan 27 16:29:39.966: BGP: 172.16.2.1 received KEEPALIVE, length (excl. header) 0

Advertisements
This entry was posted in BGP, Route and tagged . Bookmark the permalink.

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s