Skip to main content

BGP Neighbor Adjacency States in Lab

We can see the bgp states with 'debug ip bgp events' command.

*Mar  1 01:48:40.675: BGP: 10.1.12.1 went from Idle to Active
*Mar  1 00:50:27.127: BGP: 10.1.12.1 open active, local address 10.1.12.2
*Mar  1 00:50:27.155: BGP: 10.1.12.1 went from Active to OpenSent
*Mar  1 00:50:27.155: BGP: 10.1.12.1 sending OPEN, version 4, my as: 200, holdtime 180 seconds
*Mar  1 00:50:27.159: BGP: 10.1.12.1 send message type 1, length (incl. header) 45
*Mar  1 00:50:27.187: BGP: 10.1.12.1 rcv message type 1, length (excl. header) 26
*Mar  1 00:50:27.187: BGP: 10.1.12.1 rcv OPEN, version 4, holdtime 180 seconds
*Mar  1 00:50:27.191: BGP: 10.1.12.1 rcv OPEN w/ OPTION parameter len: 16
*Mar  1 00:50:27.191: BGP: 10.1.12.1 rcvd OPEN w/ optional parameter type 2 (Capability) len 6
*Mar  1 00:50:27.191: BGP: 10.1.12.1 OPEN has CAPABILITY code: 1, length 4
*Mar  1 00:50:27.191: BGP: 10.1.12.1 OPEN has MP_EXT CAP for afi/safi: 1/1
*Mar  1 00:50:27.191: BGP: 10.1.12.1 rcvd OPEN w/ optional parameter type 2 (Capability) len 2
*Mar  1 00:50:27.195: BGP: 10.1.12.1 OPEN has CAPABILITY code: 128, length 0
*Mar  1 00:50:27.195: BGP: 10.1.12.1 OPEN has ROUTE-REFRESH capability(old) for all address-families
*Mar  1 00:50:27.195: BGP: 10.1.12.1 rcvd OPEN w/ optional parameter type 2 (Capability) len 2
*Mar  1 00:50:27.195: BGP: 10.1.12.1 OPEN has CAPABILITY code: 2, length 0
*Mar  1 00:50:27.195: BGP: 10.1.12.1 OPEN has ROUTE-REFRESH capability(new) for all address-families
BGP: 10.1.12.1 rcvd OPEN w/ remote AS 200
*Mar  1 00:50:27.195: BGP: 10.1.12.1 went from OpenSent to OpenConfirm
*Mar  1 00:50:27.195: BGP: 10.1.12.1 went from OpenConfirm to Established
*Mar  1 00:50:27.195: %BGP-5-ADJCHANGE: neighbor 10.1.12.1 Up

Comments

Popular posts from this blog

Access-list at SVI

SVI (Switch Virtual Interfaces) We use the SVI for inter vlan routing. In this scenario I will configure the access list with SVI. In this scenario I want to permit vlan 10 network to vlan 50 Server farm. Vlan 10 and vlan 20 can communicate each other. First create vlan and then interface vlan#. Switch(config)#vlan 10 Switch(config)#interface vlan 10 Switch(config-if)#ip address 192.168.10.254 255.255.255.0 Switch(config)#vlan 20 Switch(config)#interface vlan 20 Switch(config-if)#ip address 192.168.20.254 255.255.255.0 Switch(config)#vlan 50 Switch(config)#interface vlan 50 Switch(config-if)#ip address 192.168.50.254 255.255.255.0 when we finish the vlan interface create make sure the switch port are belong to each vlan. Port to vlan assign configure is Switch(config)#interface g0/1 Switch(config-if)#switchport access vlan 10 Switch(config)#interface g0/2 Switch(config-if)#switchport access vlan 20 Switch(config)#int...

OSPF Stub

The following restrictions apply to stub areas:     You cannot create a virtual link through a stub area.   A stub area cannot contain an AS boundary router.   You cannot configure the backbone as a stub area.   You cannot configure an area as both a stub area and an not-so-stubby area (NSSA). Ref : Juniper.net

Why does OSPF need backbone area?

Why does OSPF require all traffic between non-backbone areas to pass through a backbone area (area 0)?   Because inter-area OSPF is distance vector, it is vulnerable to routing loops. It avoids loops by mandating a loop-free inter-area topology, in which traffic from one area can only reach another area through area 0. Ref : Jeff Doyle article at Network world http://www.networkworld.com/article/2348778/cisco-subnet/my-favorite-interview-question.html