From: k c (jwongccie@yahoo.com.hk)
Date: Sat May 21 2005 - 05:00:09 GMT-3
Hi Group,
It is strange. BGP peer between R7 and R4 using sec IP does work and between R3 amd R5 using sec IP doesn't work. Pls see the following config/sh ip bgp su/debug on each routers.
1) BGP peer between R7 and R4 does work
R7
interface FastEthernet0/0
ip address 2.2.2.7 255.255.255.0 secondary
ip address 150.100.10.7 255.255.255.0
router bgp 700
bgp log-neighbor-changes
network 7.7.7.136 mask 255.255.255.248
neighbor 2.2.2.4 remote-as 100
R7#sh ip bgp su
BGP router identifier 192.168.108.1, local AS number 700
BGP activity 1/0 prefixes, 1/0 paths, scan interval 60 secs
Neighbor V AS MsgRcvd MsgSent TblVer InQ OutQ Up/Down State/PfxRcd
2.2.2.4 4 100 1231 1233 2 0 0 00:03:36 0
R4
interface FastEthernet4/0
ip address 2.2.2.4 255.255.255.0 secondary
ip address 150.100.10.4 255.255.255.0
router bgp 61111
no synchronization
bgp log-neighbor-changes
bgp confederation identifier 100
bgp confederation peers 62222
neighbor 2.2.2.7 remote-as 700
neighbor 172.16.14.1 remote-as 62222
R4 #sh ip bgp su
BGP router identifier 172.16.194.1, local AS number 61111
BGP table version is 4, main routing table version 4
BGP activity 2/1 prefixes, 2/1 paths, scan interval 60 secs
Neighbor V AS MsgRcvd MsgSent TblVer InQ OutQ Up/Down State/PfxRcd
2.2.2.7 4 700 1232 1230 4 0 0 00:02:57 1
172.16.14.1 4 62222 1227 1230 4 0 0 20:23:20 0
2) BGP peer between R3 amd R5 does not work
R3
interface FastEthernet4/0
ip address 3.3.3.3 255.255.255.0 secondary
ip address 172.16.35.3 255.255.252.0
router bgp 62222
no synchronization
bgp log-neighbor-changes
bgp confederation identifier 100
bgp confederation peers 61111
neighbor 3.3.3.5 remote-as 500
neighbor 172.16.101.1 remote-as 62222
neighbor 172.16.101.1 update-source Loopback0
neighbor 172.16.102.1 remote-as 62222
neighbor 172.16.102.1 update-source Loopback0
R3 #sh ip bgp su
BGP router identifier 172.16.170.1, local AS number 62222
BGP table version is 1, main routing table version 1
Neighbor V AS MsgRcvd MsgSent TblVer InQ OutQ Up/Down State/PfxRcd
3.3.3.5 4 500 8 8 0 0 0 00:15:28 Active
172.16.101.1 4 62222 1248 1248 1 0 0 20:44:55 0
172.16.102.1 4 62222 1248 1248 1 0 0 20:44:56 0
R5
interface FastEthernet3/0
ip address 3.3.3.5 255.255.255.0 secondary
ip address 172.16.35.5 255.255.252.0
router bgp 500
no synchronization
bgp log-neighbor-changes
neighbor 3.3.3.3 remote-as 100
R5-r4#sh ip bgp su
BGP router identifier 172.16.105.1, local AS number 500
BGP table version is 1, main routing table version 1
Neighbor V AS MsgRcvd MsgSent TblVer InQ OutQ Up/Down State/PfxRcd
3.3.3.3 4 100 0 0 0 0 0 never Active
3) Debug messages for R4 and R7
R4:
ay 20 23:14:47 UTC: BGP: 2.2.2.7 open active, local address 150.100.10.4
May 20 23:14:47 UTC: BGP: 2.2.2.7 open failed: Connection refused by remote host
May 20 23:15:08 UTC: BGP: 2.2.2.7 passive open
May 20 23:15:08 UTC: BGP: 2.2.2.7 went from Active to Idle
May 20 23:15:08 UTC: BGP: 2.2.2.7 went from Idle to Connect
May 20 23:15:08 UTC: BGP: 2.2.2.7 rcv message type 1, length (excl. header) 26
May 20 23:15:08 UTC: BGP: 2.2.2.7 rcv OPEN, version 4
May 20 23:15:08 UTC: BGP: 2.2.2.7 went from Connect to OpenSent
May 20 23:15:08 UTC: BGP: 2.2.2.7 sending OPEN, version 4, my as: 100
May 20 23:15:08 UTC: BGP: 2.2.2.7 rcv OPEN w/ OPTION parameter len: 16
May 20 23:15:08 UTC: BGP: 2.2.2.7 rcvd OPEN w/ optional parameter type 2 (Capability) len 6
May 20 23:15:08 UTC: BGP: 2.2.2.7 OPEN has CAPABILITY code: 1, length 4
May 20 23:15:08 UTC: BGP: 2.2.2.7 OPEN has MP_EXT CAP for afi/safi: 1/1
May 20 23:15:08 UTC: BGP: 2.2.2.7 rcvd OPEN w/ optional parameter type 2 (Capability) len 2
May 20 23:15:08 UTC: BGP: 2.2.2.7 OPEN has CAPABILITY code: 128, length 0
May 20 23:15:08 UTC: BGP: 2.2.2.7 OPEN has ROUTE-REFRESH capability(old) for all address-families
May 20 23:15:08 UTC: BGP: 2.2.2.7 rcvd OPEN w/ optional parameter type 2 (Capability) len 2
May 20 23:15:08 UTC: BGP: 2.2.2.7 OPEN has CAPABILITY code: 2, length 0
May 20 23:15:08 UTC: BGP: 2.2.2.7 OPEN has ROUTE-REFRESH capability(new) for all address-families
May 20 23:15:08 UTC: BGP: 2.2.2.7 went from OpenSent to OpenConfirm
May 20 23:15:08 UTC: BGP: 2.2.2.7 send message type 1, length (incl. header) 45
May 20 23:15:08 UTC: BGP: 2.2.2.7 went from OpenConfirm to Established
May 20 23:15:08: %BGP-5-ADJCHANGE: neighbor 2.2.2
R7:
3d05h: BGP: 2.2.2.4 went from Idle to Active
3d05h: BGP: 2.2.2.4 open active, delay 22648ms
3d05h: BGP: 2.2.2.4 open active, local address 2.2.2.7
3d05h: BGP: 2.2.2.4 went from Active to OpenSent
3d05h: BGP: 2.2.2.4 sending OPEN, version 4, my as: 700
3d05h: BGP: 2.2.2.4 send message type 1, length (incl. header) 45
3d05h: BGP: 2.2.2.4 rcv message type 1, length (excl. header) 26
3d05h: BGP: 2.2.2.4 rcv OPEN, version 4
3d05h: BGP: 2.2.2.4 rcv OPEN w/ OPTION parameter len: 16
3d05h: BGP: 2.2.2.4 rcvd OPEN w/ optional parameter type 2 (Capability) len 6
3d05h: BGP: 2.2.2.4 OPEN has CAPABILITY code: 1, length 4
3d05h: BGP: 2.2.2.4 OPEN has MP_EXT CAP for afi/safi: 1/1
3d05h: BGP: 2.2.2.4 rcvd OPEN w/ optional parameter type 2 (Capability) len 2
3d05h: BGP: 2.2.2.4 OPEN has CAPABILITY code: 128, length 0
3d05h: BGP: 2.2.2.4 OPEN has ROUTE-REFRESH capability(old) for all address-families
3d05h: BGP: 2.2.2.4 rcvd OPEN w/ optional parameter type 2 (Capability) len 2
3d05h: BGP: 2.2.2.4 OPEN has CAPABILITY code: 2, length 0
3d05h: BGP: 2.2.2.4 OPEN has ROUTE-REFRESH capability(new) for all address-families
3d05h: BGP: 2.2.2.4 went from OpenSent to OpenConfirm
3d05h: BGP: 2.2.2.4 went from OpenConfirm to Established
3d05h: %BGP-5-ADJCHANGE: neighbor 2.2.2.4 Up
4) Debug messages for R3 and R5
R3
*May 21 16:09:33.022: BGP: 3.3.3.5 went from Idle to Active
*May 21 16:09:33.022: BGP: 3.3.3.5 open active, delay 20676ms
*May 21 16:09:35.530: BGP: Import timer expired. Walking from 1 to 1
*May 21 16:09:50.530: BGP: Import timer expired. Walking from 1 to 1
*May 21 16:09:53.698: BGP: 3.3.3.5 open active, local address 172.16.35.3
*May 21 16:09:53.698: BGP: 3.3.3.5 open failed: Connection refused by remote host
R5
*May 21 06:44:37.366: BGP: 3.3.3.3 open active, local address 172.16.35.5
*May 21 06:44:37.366: BGP: 3.3.3.3 open failed: Connection refused by remote host
Thanks.
k c <jwongccie@yahoo.com.hk> <6<g:
Hi Group,
Does anybody reply this question or I miss it?
"I want to know whether there is solution for BGP peering using secondary IP addresses. I checked the old posts and couldn't find the answer (one old post mentioned using NAT, does it work?)."
Thanks.
k c <6Hi Group,
I want to know whether there is solution for BGP peering using secondary IP addresses. I checked the old posts and couldn't find the answer (one old post mentioned using NAT, does it work?).
Thanks,
---------------------------------
7Q'Y.I&,(l7s email 3q*>!H
$U8| Yahoo! Messenger
http://messenger.yahoo.com.hk
This archive was generated by hypermail 2.1.4 : Fri Jun 03 2005 - 10:11:59 GMT-3