11-05-2007 09:27 PM
I had 2 RRs in the same cluster running for sometime without any problems until I shutdown one of the RR router (RR1) and move it to new location. After power up again, I have this problem where the iBGP session between RRs keep on change state from up/down every 2-3 minutes. RR clients session to RRs no problem at all.
- does it caused by no cluster-id configured ?
- after session up, I can see OutQ=90 on show ip bgp summ.
RR1-172.18.255.254
RR2-172.18.255.253
RR1#sh ip bgp vpnv4 all summ
BGP router identifier 172.18.255.254, local AS number 10081
BGP table version is 879, main routing table version 879
878 network entries using 120286 bytes of memory
1267 path entries using 86156 bytes of memory
221/158 BGP path/bestpath attribute entries using 27404 bytes of memory
8 BGP AS-PATH entries using 192 bytes of memory
50 BGP extended community entries using 1456 bytes of memory
0 BGP route-map cache entries using 0 bytes of memory
0 BGP filter-list cache entries using 0 bytes of memory
BGP using 235494 total bytes of memory
BGP activity 1756/878 prefixes, 2534/1267 paths, scan interval 15 secs
Neighbor V AS MsgRcvd MsgSent TblVer InQ OutQ Up/Down State/PfxRcd
172.18.255.1 4 10081 338 686 879 0 0 00:32:04 502
172.18.255.2 4 10081 349 687 879 0 0 00:32:04 511
.....
....
..
172.18.255.253 4 10081 80 522 0 0 90 00:00:06 0
show log
----------
Nov 6 03:04:19 MYT: %BGP-5-ADJCHANGE: neighbor 172.18.255.254 Up
Nov 6 03:07:20 MYT: %BGP-5-ADJCHANGE: neighbor 172.18.255.254 Down BGP Notification sent
Nov 6 03:07:20 MYT: %BGP-3-NOTIFICATION: sent to neighbor 172.18.255.254 4/0 (hold time expired) 0
bytes
Nov 6 03:08:04 MYT: %BGP-5-ADJCHANGE: neighbor 172.18.255.254 Up
Nov 6 03:11:04 MYT: %BGP-5-ADJCHANGE: neighbor 172.18.255.254 Down BGP Notification sent
Nov 6 03:11:04 MYT: %BGP-3-NOTIFICATION: sent to neighbor 172.18.255.254 4/0 (hold time expired) 0
bytes
Nov 6 03:11:45 MYT: %BGP-5-ADJCHANGE: neighbor 172.18.255.254 Up
Nov 6 03:14:46 MYT: %BGP-5-ADJCHANGE: neighbor 172.18.255.254 Down BGP Notification sent
Nov 6 03:14:46 MYT: %BGP-3-NOTIFICATION: sent to neighbor 172.18.255.254 4/0 (hold time expired) 0
bytes
Nov 6 03:15:27 MYT: %BGP-5-ADJCHANGE: neighbor 172.18.255.254 Up
Nov 6 03:18:27 MYT: %BGP-5-ADJCHANGE: neighbor 172.18.255.254 Down BGP Notification sent
Nov 6 03:18:27 MYT: %BGP-3-NOTIFICATION: sent to neighbor 172.18.255.254 4/0 (hold time expired) 0
RR1
---
router bgp 10081
bgp router-id 172.18.255.254
no bgp default ipv4-unicast
bgp log-neighbor-changes
bgp graceful-restart restart-time 120
bgp graceful-restart stalepath-time 360
bgp graceful-restart
neighbor VPN-RR-CLIENT peer-group
neighbor VPN-RR-CLIENT remote-as 10081
neighbor VPN-RR-CLIENT password 7 xxx
neighbor VPN-RR-CLIENT update-source Loopback0
neighbor VPN-RR peer-group
neighbor VPN-RR remote-as 10081
neighbor VPN-RR password 7 xxx
neighbor VPN-RR update-source Loopback0
neighbor 172.18.255.1 peer-group VPN-RR-CLIENT
neighbor 172.18.255.2 peer-group VPN-RR-CLIENT
neighbor 172.18.255.253 peer-group VPN-RR
address-family vpnv4
neighbor VPN-RR-CLIENT send-community both
neighbor VPN-RR-CLIENT route-reflector-client
neighbor VPN-RR send-community both
neighbor 172.18.255.1 activate
neighbor 172.18.255.2 activate
neighbor 172.18.255.253 activate
exit-address-family
11-05-2007 09:28 PM
RR2 config below
RR2
-----
router bgp 10081
bgp router-id 172.18.255.253
no bgp default ipv4-unicast
bgp log-neighbor-changes
bgp graceful-restart restart-time 120
bgp graceful-restart stalepath-time 360
bgp graceful-restart
neighbor VPN-RR-CLIENT peer-group
neighbor VPN-RR-CLIENT remote-as 10081
neighbor VPN-RR-CLIENT password 7 xxx
neighbor VPN-RR-CLIENT update-source Loopback0
neighbor VPN-RR peer-group
neighbor VPN-RR remote-as 10081
neighbor VPN-RR password 7 xxx
neighbor VPN-RR update-source Loopback0
neighbor 172.18.255.1 peer-group VPN-RR-CLIENT
neighbor 172.18.255.2 peer-group VPN-RR-CLIENT
neighbor 172.18.255.254 peer-group VPN-RR
!
address-family vpnv4
neighbor VPN-RR-CLIENT send-community both
neighbor VPN-RR-CLIENT route-reflector-client
neighbor VPN-RR send-community both
neighbor 172.18.255.1 activate
neighbor 172.18.255.2 activate
neighbor 172.18.255.254 activate
exit-address-family
11-06-2007 01:06 AM
Hi all,
Managed to get problem solved.
When RR1 established TCP session to another RR2 or vice versa. The Datagrams max data segment is 1540 bytes (at the end of show ip bgp neighbors x.x.x.x) But RRs established to other clients, it was 1516 bytes in size. I am not sure why.
There is another message appear during " show ip bgp neighbors RR2 ip"
[Keepalives are temporarily in throttle due to TCP]
After I configured the global command " ip tcp mss 1516 " on both RR1 and RR2 , problem resolved and show ip bgp neighbors RR2 ip this time it shown the The Datagrams max data segment is 1516 bytes.
And the message [Keepalives are temporarily in throttle due to TCP] dissapeared.
All working fine now the peering between RRs no longer flapping,it now stable and working fine.
Regards
Find answers to your questions by entering keywords or phrases in the Search bar above. New here? Use these resources to familiarize yourself with the community: