From: GAURAV MADAN (gauravmadan1177@gmail.com)
Date: Sun Aug 17 2008 - 10:17:46 ART
Even "debug ip bgp" gives me same :
Rack1R5(config-router)#do sh debug
IP routing:
BGP debugging is on for address family: IPv4 Unicast
Rack1R5(config-router)#
*Aug 17 13:06:24.666: BGP: 192.10.1.254 read request no-op
*Aug 17 13:06:24.666: BGP: 192.10.1.254 open failed: Connection timed
out; remote host not responding, open active delayed 1351ms (5000ms
max, 90% jitter)
Rack1R5(config-router)#
*Aug 17 13:06:26.018: BGP: 192.10.1.254 open active, local address 192.10.1.5
Rack1R5(config-router)#
*Aug 17 13:06:56.018: BGP: 192.10.1.254 read request no-op
*Aug 17 13:06:56.018: BGP: 192.10.1.254 open failed: Connection timed
out; remote host not responding, open active delayed 8749ms (10000ms
max, 60% jitter)
Rack1R5(config-router)#
*Aug 17 13:07:04.770: BGP: 192.10.1.254 open active, local address 192.10.1.5
Rack1R5(config-router)#
Rack1R5(config-router)#
Rack1R5(config-router)#
*Aug 17 13:07:34.770: BGP: 192.10.1.254 read request no-op
*Aug 17 13:07:34.770: BGP: 192.10.1.254 open failed: Connection timed
out; remote host not responding, open active delayed 15020ms (20000ms
max, 60% jitter)
Rack1R5(config-router)#
*Aug 17 13:07:49.790: BGP: 192.10.1.254 open active, local address 192.10.1.5
Rack1R5(config-router)#
*Aug 17 13:08:19.790: BGP: 192.10.1.254 read request no-op
*Aug 17 13:08:19.790: BGP: 192.10.1.254 open failed: Connection timed
out; remote host not responding, open active delayed 20060ms (35000ms
max, 60% jitter)
========================================================
On Sun, Aug 17, 2008 at 6:30 PM, Sam Z <uniqsam@gmail.com> wrote:
> "debug ip bgp" will detect it.
>
> Sam.
>
> R1#deb ip bgp
> BGP debugging is on for address family: IPv4 Unicast
> R1#
> *Sep 6 10:15:55.044 EDT: %TCP-6-BADAUTH: Invalid MD5 digest from
> 151.11.11.1(31226) to 151.32.32.1(179) tableid - -1
> *Sep 6 10:15:55.132 EDT: %TCP-6-BADAUTH: Invalid MD5 digest from
> 151.11.11.1(31226) to 151.32.32.1(179) tableid - -1
> *Sep 6 10:15:55.132 EDT: %TCP-6-BADAUTH: Invalid MD5 digest from
> 151.11.11.1(31226) to 151.32.32.1(179) tableid - -1
> *Sep 6 10:15:55.344 EDT: %TCP-6-BADAUTH: Invalid MD5 digest from
> 151.11.11.1(31226) to 151.32.32.1(179) tableid - -1
> *Sep 6 10:15:55.976 EDT: %TCP-6-BADAUTH: Invalid MD5 digest from
> 151.11.11.1(31226) to 151.32.32.1(179) tableid - -1
> *Sep 6 10:15:57.184 EDT: %TCP-6-BADAUTH: Invalid MD5 digest from
> 151.11.11.1(31226) to 151.32.32.1(179) tableid - -1
>
>
> On Sun, Aug 17, 2008 at 8:39 AM, GAURAV MADAN <gauravmadan1177@gmail.com>
> wrote:
>>
>> Hi All
>>
>> What debug can actually reflect that peer BGP neighor is expecting a
>> password that we are not providing .
>>
>> I did .. " debug ip bgp <neighbor>" which gives me :
>>
>> *Aug 17 12:27:47.350: BGP: 192.10.1.254 read request no-op
>> *Aug 17 12:27:47.350: BGP: 192.10.1.254 open failed: Connection timed
>> out; remote host not responding, open active delayed 6865ms (10000ms
>> max, 60% jitter)
>>
>> Can someone point to exact debug .?
>>
>> Thnx in advance
>> Gaurav Madan.
>>
>>
>> Blogs and organic groups at http://www.ccie.net
>>
>> _______________________________________________________________________
>> Subscription information may be found at:
>> http://www.groupstudy.com/list/CCIELab.html
Blogs and organic groups at http://www.ccie.net
This archive was generated by hypermail 2.1.4 : Mon Sep 01 2008 - 08:15:31 ART