From: Ajay Prakash (ajay.prakash@networkpeople.co.in)
Date: Thu Sep 27 2007 - 04:26:08 ART
Hello,
 
I managed to get it up. Seems like this peering needed authentication to
come up, however this was not mentioned in the task itself. The peering came
up as soon as I configured password for the neighbor :-) 
 
Thanks,
Ajay
 
 
 
  _____  
From: Ajay Prakash [mailto:ajay.prakash@networkpeople.co.in] 
Sent: Thursday, September 27, 2007 12:45 PM
To: 'ccielab@groupstudy.com'
Subject: Cannot Get BGP peering to come up!!
 
Hello,
 
I am kind of stuck while trying to get the BGP peering up between R2
(192.10.2.2) and BB1 (192.10.2.254). Please give me some tips as to how to
troubleshoot this
 
R2 Fa0/0 ---------------- BB2
 
Rack2R2(config-router)#do sh run | s bgp
router bgp 200
 no synchronization
 bgp log-neighbor-changes
 neighbor 154.2.23.3 remote-as 300
 neighbor 154.2.23.3 send-community
 neighbor 192.10.2.1 remote-as 200
 neighbor 192.10.2.1 send-community
 neighbor 192.10.2.254 remote-as 254
 neighbor 192.10.2.254 ebgp-multihop 255  <<------ I dont think required,
but just put in while trying to troubleshoot
 neighbor 192.10.2.254 update-source BVI1
 neighbor 192.10.2.254 send-community
 no auto-summary
 
Rack2R2#sh run int bvi1
interface BVI1
 ip address 192.10.2.2 255.255.255.0
end
 
Rack2R2#sh run int fa0/0
interface FastEthernet0/0
 no ip address
 duplex auto
 speed auto
 bridge-group 1
end
 
Rack2R2(config-router)#do sh ip bgp summ
 
 
Neighbor        V    AS MsgRcvd MsgSent   TblVer  InQ OutQ Up/Down
State/PfxRcd
154.2.23.3      4   300      21      21       13    0    0 00:14:24        0
192.10.2.1      4   200      23      20       13    0    0 00:16:27       10
192.10.2.254    4   254       0       0        0    0    0 never    Active
 
 
Rack2R2#p 192.10.2.254
 
Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 192.10.2.254, timeout is 2 seconds:
!!!!!
Success rate is 100 percent (5/5), round-trip min/avg/max = 1/2/4 ms
 
Rack2R2#traceroute 192.10.2.254 
 
Type escape sequence to abort.
Tracing the route to 192.10.2.254
 
  1 192.10.2.254 4 msec
 
Rack2R2(config-router)#
*Dec 17 08:42:26.950: BGP: 192.10.2.254 open failed: Connection timed out;
remote host not responding, open active delayed 34335ms (35000ms max, 28%
jitter)
 
Rack2R2#debu ip bgp 
*Dec 17 08:35:15.482: BGP: Regular scanner event timer
*Dec 17 08:35:15.482: BGP: Import timer expired. Walking from 1 to 1
Rack2R2#debu ip bgp 
*Dec 17 08:35:29.926: BGP: 192.10.2.254 open failed: Connection timed out;
remote host not responding, open active delayed 31912ms (35000ms max, 28%
jitter)
*Dec 17 08:35:30.482: BGP: Regular scanner event timer
*Dec 17 08:35:30.482: BGP: Import timer expired. Walking from 1 to 1
This archive was generated by hypermail 2.1.4 : Sat Oct 06 2007 - 12:01:16 ART