cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
489
Views
0
Helpful
1
Replies

BGP ebgp configuration

DEV1389
Level 1
Level 1

Hallo All, 

 

trying to lab configuration for IBGP-EBGP-IBGP am getting these errors, IBGP are working fine but getting problems with ebgp logs and config are mentioned below for any tip. :-

 

*Feb 25 21:46:10.479: BGP: ses global 200.200.200.1 (0x1102E198:0) act Reset (Active open failed).
*Feb 25 21:46:10.486: BGP: 200.200.200.1 active went from Active to Idle
*Feb 25 21:46:10.486: BGP: nbr global 200.200.200.1 Active open failed - open timer running
*Feb 25 21:46:10.486: BGP: nbr global 200.200.200.1 Active open failed - open timer running
*Feb 25 21:46:11.345: BGP: 200.200.200.6 active went from Idle to Active
*Feb 25 21:46:11.346: BGP: 200.200.200.6 open active, local address 3.3.3.3
*Feb 25 21:46:22.609: BGP: 200.200.200.1 active went from Idle to Active
*Feb 25 21:46:22.610: BGP: 200.200.200.1 open active, local address 3.3.3.3
*Feb 25 21:46:41.354: BGP: 200.200.200.6 open failed: Connection timed out; remote host not responding
*Feb 25 21:46:41.355: BGP: 200.200.200.6 Active open failed - tcb is not available, open active delayed 8192ms (35000ms max, 60% jitter)
*Feb 25 21:46:41.355: BGP: ses global 200.200.200.6 (0x116799C8:0) act Reset (Active open failed).
*Feb 25 21:46:41.362: BGP: 200.200.200.6 active went from Active to Idle
*Feb 25 21:46:41.362: BGP: nbr global 200.200.200.6 Active open failed - open timer running
*Feb 25 21:46:41.362: BGP: nbr global 200.200.200.6 Active open failed - open timer running
*Feb 25 21:46:49.248: BGP: 200.200.200.6 active went from Idle to Active
*Feb 25 21:46:49.249: BGP: 200.200.200.6 open active, local address 3.3.3.3
*Feb 25 21:46:52.620: BGP: 200.200.200.1 open failed: Connection timed out; remote host not responding
*Feb 25 21:46:52.621: BGP: 200.200.200.1 Active open failed - tcb is not available, open active delayed 10240ms (35000ms max, 60% jitter)

************************************************************************

NXOS15# show ip int br

IP Interface Status for VRF "default"(1)
Interface IP Address Interface Status
Lo1 10.10.10.15 protocol-up/link-up/admin-up
Eth1/1 200.200.200.6 protocol-up/link-up/admin-up
Eth1/2 192.168.35.2 protocol-up/link-up/admin-up
Eth1/3 192.168.45.2 protocol-up/link-up/admin-up
NXOS15# show running-config section router
show running-config | section router
ip router ospf 1 area 0.0.0.0
ip router ospf 1 area 0.0.0.0
ip router ospf 1 area 0.0.0.0
router ospf 1
router-id 10.10.10.15
router bgp 200
router-id 10.10.10.15
log-neighbor-changes
address-family ipv4 unicast
network 200.200.200.4/30
neighbor 10.10.10.13
remote-as 200
update-source loopback1
address-family ipv4 unicast
send-community extended
address-family l2vpn evpn
send-community extended
neighbor 10.10.10.14
remote-as 200
update-source loopback1
address-family ipv4 unicast
send-community extended
address-family l2vpn evpn
send-community extended
neighbor 200.200.200.5
remote-as 300
update-source loopback1
address-family ipv4 unicast
NXOS15#

************************************************************************

router ospf 1
router-id 10.10.10.5
router bgp 100
router-id 10.10.10.5
log-neighbor-changes
address-family ipv4 unicast
network 200.200.200.0/30
neighbor 10.10.10.1
remote-as 100
update-source loopback1
address-family ipv4 unicast
send-community extended
address-family l2vpn evpn
send-community extended
neighbor 10.10.10.2
remote-as 100
update-source loopback1
address-family ipv4 unicast
send-community extended
address-family l2vpn evpn
send-community extended
neighbor 200.200.200.2
remote-as 300
update-source loopback1
address-family ipv4 unicast
NXOS5# show ip int brief

IP Interface Status for VRF "default"(1)
Interface IP Address Interface Status
Vlan50 172.16.50.1 protocol-up/link-up/admin-up
Vlan100 172.16.100.1 protocol-up/link-up/admin-up
Lo1 10.10.10.5 protocol-up/link-up/admin-up
Eth1/1 192.168.52.1 protocol-up/link-up/admin-up
Eth1/2 192.168.51.2 protocol-up/link-up/admin-up
Eth1/3 200.200.200.1 protocol-up/link-up/admin-up
NXOS5#

************************************************************************

WANEdge#show running-config | sec router bgp
router bgp 300
bgp router-id 3.3.3.3
bgp log-neighbor-changes
neighbor 200.200.200.1 remote-as 100
neighbor 200.200.200.1 update-source Loopback1
neighbor 200.200.200.6 remote-as 200
neighbor 200.200.200.6 update-source Loopback1
!
address-family ipv4
network 3.3.3.3 mask 255.255.255.255
neighbor 200.200.200.1 activate
neighbor 200.200.200.1 next-hop-self
neighbor 200.200.200.6 activate
neighbor 200.200.200.6 next-hop-self
exit-address-family
WANEdge#
WANEdge#
WANEdge# show ip int br
Interface IP-Address OK? Method Status Protocol
GigabitEthernet0/0 200.200.200.5 YES NVRAM up up
GigabitEthernet0/1 200.200.200.2 YES NVRAM up up
GigabitEthernet0/2 unassigned YES NVRAM administratively down down
GigabitEthernet0/3 unassigned YES NVRAM administratively down down
Loopback1 3.3.3.3 YES NVRAM up up  

*********************************************************************

 

Thanks

WAQ

1 Reply 1

Muhammad Awais Khan
Cisco Employee
Cisco Employee

Hi,

 

I notice that you are peering EBGP with using suorce Lo1 on both sides but in actual BGP Peering/neighbor configuration you are not specifying the Loopback IP of the peer, instead you used Physical IP.

 

NXOS15# show running-config section router

Loopback1:= 10.10.10.15
router bgp 200
router-id 10.10.10.15
neighbor 200.200.200.5
remote-as 300
update-source loopback1
address-family ipv4 unicast
NXOS15#

on WANEDGE:
router bgp 300
bgp router-id 3.3.3.3
bgp log-neighbor-changes
neighbor 200.200.200.6 remote-as 200
neighbor 200.200.200.6 update-source Loopback1

 

Either change the neighbor address on both above configuration to the respective loopback interfaces or remote the update-source loopback 1