From: Mahesh Shivaswamy (maheshs.cisco@gmail.com)
Date: Thu Oct 23 2008 - 03:31:17 ARST
its not an L2 issue,
R3#pi 154.1.0.5
Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 154.1.0.5, timeout is 2 seconds:
!!!!!
Success rate is 100 percent (5/5), round-trip min/avg/max = 28/30/32 ms
R3#pi
Protocol [ip]:
Target IP address: 154.1.0.5
Repeat count [5]: 500
Datagram size [100]:
Timeout in seconds [2]:
Extended commands [n]:
Sweep range of sizes [n]:
Type escape sequence to abort.
Sending 500, 100-byte ICMP Echos to 154.1.0.5, timeout is 2 seconds:
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!!!!!!!!!!
Success rate is 100 percent (500/500), round-trip min/avg/max = 28/29/36 ms
R3#debu ip bgp
BGP debugging is on for address family: IPv4 Unicast
R3#cle
R3#clear ip bgp 154.1.0.5
R3#
*May 4 12:02:29.791: BGPNSF state: 154.1.0.5 went from nsf_not_active to
nsf_not_active
*May 4 12:02:29.791: BGP: 154.1.0.5 went from OpenConfirm to Idle
*May 4 12:02:29.791: BGP: 154.1.0.5 closing
*May 4 12:02:29.791: BGP: 154.1.0.5 went from Idle to Active
*May 4 12:02:29.791: BGP: 154.1.0.5 open active delayed 33844ms (35000ms
max, 28% jitter)
R3#
*May 4 12:04:04.067: BGP: 154.1.0.5 open active, local address 154.1.0.3
R3#
*May 4 12:04:34.067: BGP: 154.1.0.5 open failed: Connection timed out;
remote host not responding, open active delayed 27215ms (35000ms max, 28%
jitter)
R3#
*May 4 12:04:50.039: BGP: 154.1.0.5 passive open to 154.1.0.3
*May 4 12:04:50.039: BGP: 154.1.0.5 went from Active to Idle
*May 4 12:04:50.039: BGP: 154.1.0.5 went from Idle to Connect
*May 4 12:04:50.051: BGP: 154.1.0.5 rcv message type 1, length (excl.
header) 26
*May 4 12:04:50.051: BGP: 154.1.0.5 rcv OPEN, version 4, holdtime 180
seconds
*May 4 12:04:50.051: BGP: 154.1.0.5 went from Connect to OpenSent
*May 4 12:04:50.051: BGP: 154.1.0.5 sending OPEN, version 4, my as: 300,
holdtime 180 seconds
*May 4 12:04:50.051: BGP: 154.1.0.5 rcv OPEN w/ OPTION parameter len: 16
*May 4 12:04:50.051: BGP: 154.1.0.5 rcvd OPEN w/ optional parameter type 2
(Capability) len 6
*May 4 12:04:50.051: BGP: 154.1.0.5 OPEN has CAPABILITY code: 1, length 4
*May 4 12:04:50.051: BGP: 154.1.0.5 OPEN has MP_EXT CAP for afi/safi: 1/1
*May 4 12:04:50.051: BGP: 154.1.0.5 rcvd OPEN w/ optional parameter type 2
(Capability) len 2
*May 4 12:04:50.051: BGP: 154.1.0.5 OPEN has CAPABILITY cod
R3#e: 128, length 0
*May 4 12:04:50.051: BGP: 154.1.0.5 OPEN has ROUTE-REFRESH capability(old)
for all address-families
*May 4 12:04:50.051: BGP: 154.1.0.5 rcvd OPEN w/ optional parameter type 2
(Capability) len 2
*May 4 12:04:50.051: BGP: 154.1.0.5 OPEN has CAPABILITY code: 2, length 0
*May 4 12:04:50.051: BGP: 154.1.0.5 OPEN has ROUTE-REFRESH capability(new)
for all address-families
BGP: 154.1.0.5 rcvd OPEN w/ remote AS 400
*May 4 12:04:50.051: BGP: 154.1.0.5 went from OpenSent to OpenConfirm
*May 4 12:04:50.051: BGP: 154.1.0.5 send message type 1, length (incl.
header) 45
rgds
Mahesh
On Thu, Oct 23, 2008 at 12:05 AM, Shahid Ansari <shahid1357@gmail.com>wrote:
> Hi Mahesh ,
>
> I think there is problem in basic ip connectivity might be due to bad cable
> on R5.
> can you check sh interface on R5 .Check layer two encapsulation completion
> .
>
> post us debug ip bgp if L2 is Up .
>
> --
> Regards,
>
> Shahid Ansari
> Saudi Arabia(Riyadh)
>
>
> On Thu, Oct 23, 2008 at 6:07 AM, Mahesh Shivaswamy <
> maheshs.cisco@gmail.com> wrote:
>
>> These are real labs, I get the following error after debugging keepalives
>>
>> R3#
>> *May 4 09:42:59.072: BGP: 154.1.13.1 sending KEEPALIVE (io)
>> R3#
>> *May 4 09:43:02.332: BGP: 154.1.38.8 received KEEPALIVE, length (excl.
>> header) 0
>> *May 4 09:43:03.072: BGP: 154.1.38.8 sending KEEPALIVE (io)
>> R3#
>> *May 4 09:43:22.072: BGP: 154.1.0.4 sending KEEPALIVE (io)
>> *May 4 09:43:22.092: BGP: 154.1.0.4 received KEEPALIVE, length (excl.
>> header) 0
>> R3#
>> *May 4 09:43:57.948: BGP: 154.1.23.2 sending KEEPALIVE (io)
>> *May 4 09:43:57.948: BGP: 154.1.13.1 received KEEPALIVE, length (excl.
>> header) 0
>> *May 4 09:43:57.960: BGP: 154.1.23.2 received KEEPALIVE, length (excl.
>> header) 0
>> R3#
>> *May 4 09:43:59.072: BGP: 154.1.13.1 sending KEEPALIVE (io)
>> R3#
>> *May 4 09:44:02.344: BGP: 154.1.38.8 received KEEPALIVE, length (excl.
>> header) 0
>> *May 4 09:44:03.072: BGP: 154.1.38.8 sending KEEPALIVE (io)
>> R3#
>> *May 4 09:44:22.072: BGP: 154.1.0.4 sending KEEPALIVE (io)
>> *May 4 09:44:22.092: BGP: 154.1.0.4 received KEEPALIVE, length (excl.
>> header) 0
>>
>> On Wed, Oct 22, 2008 at 10:03 PM, Hobbs <deadheadblues@gmail.com> wrote:
>>
>> > Is this dynamips or real lab? I get this in dynamips sometimes a few
>> hours
>> > into a big lab. also try this :
>> >
>> > debug ip bgp keepalive
>> >
>> > On Wed, Oct 22, 2008 at 8:42 PM, Mahesh Shivaswamy <
>> > maheshs.cisco@gmail.com> wrote:
>> >
>> >> Hi,
>> >>
>> >> I have a FR P-M interface on R3 connecting to R4 & R5, R3 establishes
>> BGP
>> >> connection to R4 but R3 -> R5 is getting hold time expired message, no
>> >> luck
>> >> with google,
>> >>
>> >>
>> >> R3#sh run | in nei
>> >> neighbor 154.1.0.4 remote-as 400
>> >> neighbor 154.1.0.5 remote-as 400
>> >>
>> >>
>> >> R3#sh ip bgp s | be Neighbor
>> >> Neighbor V AS MsgRcvd MsgSent TblVer InQ OutQ Up/Down
>> >> State/PfxRcd
>> >> 154.1.0.4 4 400 155 169 16 0 0 00:34:19
>> >> 0
>> >> 154.1.0.5 4 400 54 134 0 0 0 00:30:33
>> >> OpenConfirm
>> >>
>> >>
>> >> R4#sh run | in nei
>> >> neighbor 154.1.0.3 remote-as 300
>> >>
>> >> R4#sh ip bgp s | be Neighbor
>> >> Neighbor V AS MsgRcvd MsgSent TblVer InQ OutQ Up/Down
>> >> State/PfxRcd
>> >> 154.1.0.3 4 300 51 46 16 0 0 00:42:51
>> >> 15
>> >>
>> >>
>> >> R5#sh run | in nei
>> >> bgp log-neighbor-changes
>> >> neighbor 154.1.0.3 remote-as 300
>> >>
>> >> R5#sh ip bgp s | be Neighbor
>> >> Neighbor V AS MsgRcvd MsgSent TblVer InQ OutQ Up/Down
>> >> State/PfxRcd
>> >> 154.1.0.3 4 300 16 92 0 0 0 00:29:52
>> >> OpenSent
>> >>
>> >> R3#%BGP-3-NOTIFICATION: sent to neighbor 154.1.0.5 4/0 (hold time
>> >> expired) 0
>> >> bytes
>> >>
>> >> any info will be helpful...
>> >>
>> >> rgds
>> >> Mahesh
>> >>
>> >>
>> >> 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
>>
>> _______________________________________________________________________
>> 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 : Sat Nov 01 2008 - 15:35:22 ARST