From: Andy Mrozek (andymrozek@yahoo.com)
Date: Fri Jan 14 2005 - 16:15:41 GMT-3
Tim,
I am sure you have reset that particular neighbor ?
where the timers were modified not sure that is
required but alot of neighbor modifications do need
this....
--- Mark Lasarko <mlasarko@co.ba.md.us> wrote:
> Greetings Tim,
>
> I am not sure what happens on the neighbor
> statement?
> I have used "timers bgp 0 0", which seems to work
> for me:
>
> 2621XM-A#sh ip bgp nei 1.1.1.3
> BGP neighbor is 1.1.1.3, remote AS 200, internal
> link
> BGP version 4, remote router ID 150.1.4.4
> BGP state = Established, up for 00:00:09
> Last read 00:00:09, hold time is 0, keepalive
> interval is 0 sal is 0
> seconds
> Neighbor capabilities:
> Route refresh: advertised and received(old &
> new)
> Address family IPv4 Unicast: advertised and
> received
> Message statistics:
> InQ depth is 0
> OutQ depth is 0
> Sent Rcvd
> Opens: 1 1
> Notifications: 0 0
> Updates: 0 0
> Keepalives: 2 2
> Route Refresh: 0 0
> Total: 3 3
> Default minimum time between advertisement runs is
> 5 seconds
>
> For address family: IPv4 Unicast
> BGP table version 1, neighbor version 1
> Index 1, Offset 0, Mask 0x2
> 1 update-group member
> Sent Rcvd
> Prefix activity: ---- ----
> Prefixes Current: 0 0
> Prefixes Total: 0 0
> Implicit Withdraw: 0 0
> Explicit Withdraw: 0 0
> Used as bestpath: n/a 0
> Used as multipath: n/a 0
>
> Outbound
> Inbound
> Local Policy Denied Prefixes: --------
> -------
> Total: 0
> 0
> Number of NLRIs in the update sent: max 0, min 0
>
> Connections established 1; dropped 0
> Last reset never
> Connection state is ESTAB, I/O status: 1, unread
> input bytes: 0
> Local host: 1.1.1.1, Local port: 11000
> Foreign host: 1.1.1.3, Foreign port: 179
>
> Enqueued packets for retransmit: 0, input: 0
> mis-ordered: 0 (0 bytes)
>
> Event Timers (current time is 0x8FA658):
> Timer Starts Wakeups Next
> Retrans 4 0 0x0
> TimeWait 0 0 0x0
> AckHold 2 0 0x0
> SendWnd 0 0 0x0
> KeepAlive 0 0 0x0
> GiveUp 0 0 0x0
> PmtuAger 0 0 0x0
> DeadWait 0 0 0x0
>
> iss: 3563012222 snduna: 3563012306 sndnxt:
> 3563012306 sndwnd:
> 16301
> irs: 1109474488 rcvnxt: 1109474572 rcvwnd:
> 16301 delrcvwnd:
> 83
>
> SRTT: 124 ms, RTTO: 1405 ms, RTV: 1281 ms, KRTT: 0
> ms
> minRTT: 0 ms, maxRTT: 300 ms, ACK hold: 200 ms
> Flags: active open, retransmission timeout, nagle
> IP Precedence value : 6
>
> Datagrams (max data segment is 1460 bytes):
> Rcvd: 4 (out of order: 0), with data: 2, total data
> bytes: 83
> Sent: 5 (retransmit: 0, fastretransmit: 0), with
> data: 3, total data
> bytes: 83
> 2621XM-A#
>
> HTH,
> ~M
>
>
>
> >>> "ccie2be" <ccie2be@nyc.rr.com> 1/14/2005 1:22:42
> PM >>>
>
> Hi guys,
>
> I'm trying to prevent bgp from sending keepalives
> across an isdn link.
>
> I configured the following on each side:
>
> router bgp 200
> bgp router-id 150.1.4.4
> bgp log-neighbor-changes
> neighbor 130.1.124.1 remote-as 100
> neighbor 130.1.234.3 remote-as 200
> neighbor 150.1.5.5 remote-as 200
> neighbor 150.1.5.5 update-source Loopback0
> neighbor 150.1.5.5 timers 0 0
> <-- Stop
> keepalives
>
> Yet, BGP is still sending keepalives across the
> link. See debug output
> below.
> Why is that?
>
> Is there anything I can do to stop these keepalives?
>
> R4's debug
> *Mar 9 16:47:32.188: IP: s=150.1.5.5 (BRI0/0),
> d=150.1.4.4, len 40,
> rcvd 4
> *Mar 9 16:47:32.188: TCP src=179, dst=11263,
> seq=264761101,
> ack=1280955899,
> win=16270 ACK
> *Mar 9 16:47:32.396: %LINEPROTO-5-UPDOWN: Line
> protocol on Interface
> BRI0/0:1,
> changed state to up
> *Mar 9 16:47:37.320: %ISDN-6-CONNECT: Interface
> BRI0/0:1 is now
> connected to
> 22
> 21 ROUTER5
> *Mar 9 16:47:44.560: IP: s=150.1.5.5 (BRI0/0),
> d=150.1.4.4, len 59,
> rcvd 4
> *Mar 9 16:47:44.560: TCP src=179, dst=11263,
> seq=264761082,
> ack=1280955899,
> win=16270 ACK PSH
> *Mar 9 16:47:44.764: IP: tableid=0, s=150.1.4.4
> (local), d=150.1.5.5
> (BRI0/0),
> routed via RIB
>
> R5's debug
> *Mar 7 03:52:49.763: IP: tableid=0, s=150.1.5.5
> (local), d=150.1.4.4
> (BRI0/0),
> routed via RIB
> *Mar 7 03:52:49.979: IP: tableid=0, s=150.1.4.4
> (BRI0/0), d=150.1.5.5
> (Loopback
> 0), routed via RIB
> *Mar 7 03:52:49.979: IP: s=150.1.4.4 (BRI0/0),
> d=150.1.5.5, len 40,
> rcvd 4
> *Mar 7 03:52:49.979: TCP src=11263, dst=179,
> seq=1280955918,
> ack=264761120,
> win=16251 ACK
> Rack1R5#
>
>
> TIA, Tim
>
>
This archive was generated by hypermail 2.1.4 : Wed Feb 02 2005 - 22:10:22 GMT-3