RE: BGP identifier wrong

From: Huan Pham (huan.pham@valuenet.com.au)
Date: Thu Dec 13 2007 - 01:50:23 ART


Hi Bradford,

It seems that you use Loopback IP of 170.241.127.228 on both router.

In order for BGP to form, you need to allocate unique IP as BGP neighbor ID
for each router. May be it's good idea to nail down the BGP ID using
router-id x.x.x.x under BGP.

Cheers,
 
Huan
-----Original Message-----
From: nobody@groupstudy.com [mailto:nobody@groupstudy.com] On Behalf Of
Bradford Hung
Sent: Thursday, 13 December 2007 2:49 PM
To: ccielab@groupstudy.com
Subject: BGP identifier wrong

Hi All,

  R4 and R5 are directly connecting and running OSPF and BGP, but BGP is not
working as follow:

r5#sho ip bgp sum
BGP router identifier 170.241.127.228, local AS number 100
BGP table version is 1, main routing table version 1

Neighbor V AS MsgRcvd MsgSent TblVer InQ OutQ Up/Down
State/PfxRcd
144.1.1.1 4 100 12 12 1 0 0 00:04:24 0
144.2.2.2 4 100 11 12 1 0 0 00:04:15 0
144.4.4.4 4 100 10 10 0 0 0 never Active

r4#sho ip bgp sum
BGP router identifier 170.241.127.228, local AS number 100
BGP table version is 1, main routing table version 1

Neighbor V AS MsgRcvd MsgSent TblVer InQ OutQ Up/Down
State/PfxRcd
144.1.1.1 4 100 13 13 1 0 0 00:05:08 0
144.2.2.2 4 100 12 13 1 0 0 00:05:04 0
144.5.5.5 4 100 10 10 0 0 0 never Idle

And following is the error message:

r4#
8w2d: %BGP-3-NOTIFICATION: received from neighbor 144.5.5.5 2/3 (BGP
identifier wrong) 4 bytes AAF17FE4

r5#
*Dec 13 04:12:15.599: %BGP-3-NOTIFICATION: sent to neighbor 144.4.4.4 2/3
(BGP identifier wrong) 4 bytes AAF17FE4
r5# FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF 0035 0104 0064 00B4 AAF1 7FE4
1802 0601 0400 0100 0102 0601 0400 0100 8002 0280 0002 0202 00

Config:
R5:
router ospf 100
 router-id 144.5.5.5
 log-adjacency-changes
 network 133.1.1.0 0.0.0.255 area 0
 network 144.5.5.5 0.0.0.0 area 0
 network 170.241.127.228 0.0.0.0 area 0
!
router bgp 100
 no synchronization
 bgp log-neighbor-changes
 neighbor 144.1.1.1 remote-as 100
 neighbor 144.1.1.1 update-source Loopback0
 neighbor 144.2.2.2 remote-as 100
 neighbor 144.2.2.2 update-source Loopback0
 neighbor 144.4.4.4 remote-as 100
 neighbor 144.4.4.4 update-source Loopback0
 no auto-summary
 !
 address-family vpnv4
  neighbor 144.1.1.1 activate
  neighbor 144.1.1.1 send-community both
  neighbor 144.1.1.1 next-hop-self
  neighbor 144.2.2.2 activate
  neighbor 144.2.2.2 send-community both
  neighbor 144.2.2.2 next-hop-self
  neighbor 144.4.4.4 activate
  neighbor 144.4.4.4 send-community both
  neighbor 144.4.4.4 next-hop-self
 exit-address-family
 !
 address-family ipv4 vrf client01
  redistribute connected metric 200
  neighbor 133.1.59.9 remote-as 65005
  neighbor 133.1.59.9 activate
  no synchronization
 exit-address-family
!

R4:
r4#sb ospf 100
router ospf 100
 router-id 144.4.4.4
 log-adjacency-changes
 network 133.1.1.0 0.0.0.255 area 0
 network 144.4.4.4 0.0.0.0 area 0
 network 170.241.127.228 0.0.0.0 area 0
!
router bgp 100
 no synchronization
 bgp log-neighbor-changes
 neighbor 144.1.1.1 remote-as 100
 neighbor 144.1.1.1 update-source Loopback0
 neighbor 144.2.2.2 remote-as 100
 neighbor 144.2.2.2 update-source Loopback0
 neighbor 144.5.5.5 remote-as 100
 neighbor 144.5.5.5 update-source Loopback0
 !
 address-family ipv4 vrf client01
 redistribute connected metric 200
 neighbor 133.1.48.8 remote-as 65004
 neighbor 133.1.48.8 activate
 no auto-summary
 no synchronization
 exit-address-family
 !
 address-family vpnv4
 neighbor 144.1.1.1 activate
 neighbor 144.1.1.1 next-hop-self
 neighbor 144.1.1.1 send-community both
 neighbor 144.2.2.2 activate
 neighbor 144.2.2.2 next-hop-self
 neighbor 144.2.2.2 send-community both
 neighbor 144.5.5.5 activate
 neighbor 144.5.5.5 next-hop-self
 neighbor 144.5.5.5 send-community both
 exit-address-family
!

Please advise.

Thanks,



This archive was generated by hypermail 2.1.4 : Tue Jan 01 2008 - 12:04:30 ARST