From: Jason Cash (cash2001@xxxxxxxxxx)
Date: Sat Aug 10 2002 - 12:42:35 GMT-3
Well, as a quick fix, I installed IOS 11.2 and all the problems were
resolved as you can see. I have no idea what is up with ath version
code, but I could not find much on there website without opening a case
with TAC:
r2#sh ip bgp nei
BGP neighbor is 192.1.1.1, remote AS 100, external link
Index 1, Offset 0, Mask 0x2
BGP version 4, remote router ID 2.2.2.2
BGP state = Established, table version = 5, up for 00:17:03
Last read 00:00:03, hold time is 180, keepalive interval is 60 seconds
Minimum time between advertisement runs is 30 seconds
Received 33 messages, 0 notifications, 0 in queue
Sent 32 messages, 0 notifications, 0 in queue
Connections established 2; dropped 1
Last reset 00:17:31, due to : User reset request
No. of prefix received 2
Connection state is ESTAB, I/O status: 1, unread input bytes: 0 Local
host: 192.1.1.2, Local port: 11005 Foreign host: 192.1.1.1, Foreign
port: 179
Enqueued packets for retransmit: 0, input: 0 mis-ordered: 0 (0 bytes)
Event Timers (current time is 0x18DD24):
Timer Starts Wakeups Next
Retrans 22 0 0x0
TimeWait 0 0 0x0
AckHold 21 19 0x0
SendWnd 0 0 0x0
KeepAlive 0 0 0x0
GiveUp 0 0 0x0
PmtuAger 0 0 0x0
DeadWait 0 0 0x0
iss: 3553991820 snduna: 3553992256 sndnxt: 3553992256 sndwnd:
15949
irs: 1627376381 rcvnxt: 1627376824 rcvwnd: 15942 delrcvwnd:
442
SRTT: 337 ms, RTTO: 1253 ms, RTV: 289 ms, KRTT: 0 ms
minRTT: 8 ms, maxRTT: 308 ms, ACK hold: 300 ms
Flags: higher precedence, nagle
Datagrams (max data segment is 1460 bytes):
Rcvd: 23 (out of order: 0), with data: 21, total data bytes: 442
Sent: 42 (retransmit: 0), with data: 21, total data bytes: 435
BGP neighbor is 194.1.1.1, remote AS 200, internal link
Index 0, Offset 0, Mask 0x0
BGP version 4, remote router ID 4.4.4.4
BGP state = Established, table version = 5, up for 00:17:28
Last read 00:00:27, hold time is 180, keepalive interval is 60 seconds
Minimum time between advertisement runs is 5 seconds
Received 25 messages, 0 notifications, 0 in queue
Sent 28 messages, 0 notifications, 0 in queue
Connections established 2; dropped 1
Last reset 00:17:34, due to : User reset request
No. of prefix received 0
Connection state is ESTAB, I/O status: 1, unread input bytes: 0 Local
host: 194.1.1.2, Local port: 11003 Foreign host: 194.1.1.1, Foreign
port: 179
Enqueued packets for retransmit: 0, input: 0 mis-ordered: 0 (0 bytes)
Event Timers (current time is 0x18E6D0):
Timer Starts Wakeups Next
Retrans 23 0 0x0
TimeWait 0 0 0x0
AckHold 20 18 0x0
SendWnd 0 0 0x0
KeepAlive 0 0 0x0
GiveUp 0 0 0x0
PmtuAger 0 0 0x0
DeadWait 0 0 0x0
iss: 2005929142 snduna: 2005929617 sndnxt: 2005929617 sndwnd:
15910
irs: 1236596856 rcvnxt: 1236597263 rcvwnd: 15978 delrcvwnd:
406
SRTT: 333 ms, RTTO: 1172 ms, RTV: 253 ms, KRTT: 0 ms
minRTT: 8 ms, maxRTT: 300 ms, ACK hold: 300 ms
Flags: higher precedence, nagle
Datagrams (max data segment is 1460 bytes):
Rcvd: 35 (out of order: 0), with data: 20, total data bytes: 406
Sent: 42 (retransmit: 0), with data: 22, total data bytes: 474
BGP neighbor is 195.1.1.2, remote AS 200, internal link
Index 0, Offset 0, Mask 0x0
BGP version 4, remote router ID 3.3.3.3
BGP state = Established, table version = 5, up for 00:08:27
Last read 00:00:27, hold time is 180, keepalive interval is 60 seconds
Minimum time between advertisement runs is 5 seconds
Received 23 messages, 0 notifications, 0 in queue
Sent 23 messages, 0 notifications, 0 in queue
Connections established 2; dropped 1
Last reset 00:08:54, due to : Peer closing down the session
No. of prefix received 2
Connection state is ESTAB, I/O status: 1, unread input bytes: 0 Local
host: 192.1.1.2, Local port: 179 Foreign host: 195.1.1.2, Foreign port:
11035
Enqueued packets for retransmit: 0, input: 0 mis-ordered: 0 (0 bytes)
Event Timers (current time is 0x18EF80):
Timer Starts Wakeups Next
Retrans 14 0 0x0
TimeWait 0 0 0x0
AckHold 13 9 0x0
SendWnd 0 0 0x0
KeepAlive 0 0 0x0
GiveUp 0 0 0x0
PmtuAger 0 0 0x0
DeadWait 0 0 0x0
iss: 353233207 snduna: 353233511 sndnxt: 353233511 sndwnd:
16081
irs: 3568242406 rcvnxt: 3568242756 rcvwnd: 16035 delrcvwnd:
349
SRTT: 408 ms, RTTO: 2346 ms, RTV: 765 ms, KRTT: 0 ms
minRTT: 12 ms, maxRTT: 300 ms, ACK hold: 300 ms
Flags: passive open, nagle, gen tcbs
Datagrams (max data segment is 536 bytes):
Rcvd: 18 (out of order: 0), with data: 13, total data bytes: 349
Sent: 23 (retransmit: 0), with data: 13, total data bytes: 303
version 11.2
service timestamps debug uptime
service timestamps log uptime
no service password-encryption
service udp-small-servers
service tcp-small-servers
!
hostname r2
!
!
ip subnet-zero
no ip domain-lookup
!
!
interface Loopback0
ip address 2.2.2.2 255.255.255.0
!
interface Ethernet0
ip address 192.168.0.51 255.255.255.0
no ip route-cache
no ip mroute-cache
!
interface Serial0
ip address 192.1.1.2 255.255.255.0
no ip route-cache
no ip mroute-cache
clockrate 500000
!
interface Serial1
ip address 194.1.1.2 255.255.255.0
no ip route-cache
no ip mroute-cache
clockrate 500000
!
router ospf 1
passive-interface Serial0
network 192.1.1.0 0.0.0.255 area 0
network 194.1.1.0 0.0.0.255 area 0
!
router bgp 200
no synchronization
neighbor 192.1.1.1 remote-as 100
neighbor 194.1.1.1 remote-as 200
neighbor 195.1.1.2 remote-as 200
!
ip classless
!
alias exec shi sh ip int brief
!
line con 0
exec-timeout 60 0
transport input none
line aux 0
transport input all
line vty 0 4
login
!
end
-----Original Message-----
From: ying c [mailto:bf5tgh1@yahoo.com]
Sent: Saturday, August 10, 2002 9:08 AM
To: ying c; Darryl Munro; 'Jim Brown'; 'Jason Cash';
ccielab@groupstudy.com
Subject: RE: BGP Problems
Jason,
My mistakes again. BGP does not use loopback as RID
like OSPF, need to check something else for the
problem.
Chang
--- ying c <bf5tgh1@yahoo.com> wrote:
> Jason,
>
> If you look closely, you have 2.2.2.2 appeared in
> both
> r1 and r2, which means both r1 and r2 are using
> 2.2.2.2 ad their RID. If you get rid off loopback1
> from r1, it should solve your problem. If you want
> to
> keep 2.2.2.2 in both r1 and r2 for whatever reasons,
> you should use 'bgp router-id' command to hardcode
> the
> RID.
>
> Chang
> --- Darryl Munro <Darryl.Munro@computerland.co.nz>
> wrote:
> > It appears to me that this BGP peer is being
> formed
> > over a P2P connection
> > and the neighbor statements are to IP address's on
> > directly connected
> > networks, hence there is no need for update-source
> > command or ebgp-multihop
> > commands. There would seem to be something else
> > wrong here and I can't see
> > what is wrong with the config.
> >
> > Here is a really good link that may help you with
> > some more troubleshooting
> > techniques.
> >
> >
>
http://www.cisco.com/networkers/nw01/pres/preso/RoutingandSwitchingTechn
olog
> > ies/RST-310.pdf
> >
> > Cheers
> >
> >
> > -----Original Message-----
> > From: Jim Brown [mailto:Jim.Brown@caselogic.com]
> > Sent: Saturday, 10 August 2002 2:51 p.m.
> > To: 'Jason Cash'; ccielab@groupstudy.com
> > Subject: RE: BGP Problems
> >
> > Jason,
> >
> > BGP by default doesn't use the loopback like OSPF.
> > You must specify the
> > source address for your BGP advertisement with the
> > 'update source' command
> > on the neighbor statement.
> >
> > When advertising between EBGP peers you must also
> > include the 'EBGP
> > multihop' statement on the neighbor to account for
> > the additional hops to
> > the loopback address.
> >
> > This statement is not necessary for advertisements
> > between IBGP peers,
> > obviously this is why it is called EBGP multihop
> and
> > not BGP multihop.
> >
> >
> >
> > -----Original Message-----
> > From: Jason Cash [mailto:cash2001@swbell.net]
> > Sent: Friday, August 09, 2002 8:37 PM
> > To: ccielab@groupstudy.com
> > Subject: BGP Problems
> >
> >
> > Error msg recv'd on R1:
> > 02:19:03: %BGP-3-NOTIFICATION: sent to neighbor
> > 192.1.1.2 2/3 (BGP
> > identifier wrong)
> > 4 bytes 02020202
> >
> > Error msg recv'd on R2:
> > 02:17:55: %BGP-3-NOTIFICATION: sent to neighbor
> > 192.1.1.1 2/3 (BGP
> > identifier wrong)
> > 4 bytes 02020202
> >
> > Also, the 'sh ip bgp nei' from each router. For
> > whatever reason, it is
> > not obtaining the loopback address(es)
> >
> > r1#sh ip bgp nei
> > BGP neighbor is 192.1.1.2, remote AS 200,
> external
> > link
> > BGP version 4, remote router ID 0.0.0.0
> > BGP state = Idle
> > Last read 00:00:08, hold time is 180, keepalive
> > interval is 60 seconds
> > Received 8 messages, 3 notifications, 0 in queue
> > Sent 8 messages, 5 notifications, 0 in queue
> > Route refresh request: received 0, sent 0
> > Default minimum time between advertisement runs
> is
> > 30 seconds
> >
> > For address family: IPv4 Unicast
> > BGP table version 1, neighbor version 0
> > Index 1, Offset 0, Mask 0x2
> > 0 accepted prefixes consume 0 bytes
> > Prefix advertised 0, suppressed 0, withdrawn 0
> > Number of NLRIs in the update sent: max 0, min 0
> >
> > Connections established 0; dropped 0
> > Last reset never
> > No active TCP connection
> >
> > r2#sh ip bgp nei
> > BGP neighbor is 192.1.1.1, remote AS 100,
> external
> > link
> > BGP version 4, remote router ID 0.0.0.0
> > BGP state = Active
> > Last read 00:00:08, hold time is 180, keepalive
> > interval is 60 seconds
> > Received 6 messages, 4 notifications, 0 in queue
> > Sent 6 messages, 2 notifications, 0 in queue
> > Route refresh request: received 0, sent 0
> > Default minimum time between advertisement runs
> is
> > 30 seconds
> >
> > For address family: IPv4 Unicast
> > BGP table version 1, neighbor version 0
> > Index 1, Offset 0, Mask 0x2
> > 0 accepted prefixes consume 0 bytes
> > Prefix advertised 0, suppressed 0, withdrawn 0
> > Number of NLRIs in the update sent: max 0, min 0
> >
> > Connections established 0; dropped 0
> > Last reset never
> > No active TCP connection
> >
> > Configs: (Very simple)
> >
> > R1
> > version 12.2
> > no service single-slot-reload-enable
> > service timestamps debug uptime
> > service timestamps log uptime
> > no service password-encryption
> > service udp-small-servers
> > service tcp-small-servers
> > !
> > hostname r1
> > !
> > logging rate-limit console 10 except errors
> > !
> > ip subnet-zero
> > no ip finger
> > no ip domain-lookup
> > !
> > no ip dhcp-client network-discovery
> > !
> > interface Loopback0
> > ip address 1.1.1.1 255.255.255.0
> > !
> > interface Loopback1
> > ip address 2.2.2.2 255.255.255.0
> > !
> > interface Loopback2
> > no ip address
> > !
> > interface Loopback3
> > no ip address
> > !
> > interface Loopback4
> > no ip address
> > !
> > interface Ethernet0
> > no ip address
> > no ip route-cache
> > no ip mroute-cache
> > !
> > interface Serial0
> > ip address 192.1.1.1 255.255.255.0
> > no ip route-cache
> > no ip mroute-cache
> > !
> > interface Serial1
> > ip address 193.1.1.1 255.255.255.0
> > no ip route-cache
> > no ip mroute-cache
> > !
> > router bgp 100
> > bgp log-neighbor-changes
> > neighbor 192.1.1.2 remote-as 200
> > !
> > ip kerberos source-interface any
> > ip classless
> > no ip http server
> > !
> > !
>
=== message truncated ===
This archive was generated by hypermail 2.1.4 : Sat Sep 07 2002 - 19:48:22 GMT-3