From: Daniel C. Young (danyoung99@xxxxxxxxxxxx)
Date: Mon Aug 20 2001 - 14:33:11 GMT-3
Peter, I concur with your observations
Mike, just a shot in the dark here, but I've found (from personal
experience) that synchronization does not work with a lot of things, namely
confeds and RRs. This is looking like an IOS bug, but try to disable
synchronization on Telluride and then see if it receives the correct
next-hop information. Telluride is definately the problematic router here.
Let us know if you have resolved this.
Regards,
Daniel
-----Original Message-----
From: Peter Rybaczyk [mailto:psrsam@globalins.com]
Sent: Monday, August 20, 2001 10:03 AM
To: Michael Wong
Cc: 'afiddler'; young@pobox.com; Ccielab (E-mail)
Subject: Re: BGP synchronisation: Doyle page 175
Michael,
I've set this configuration up again (exactly as Doyle has it) with the
exception of having AS300 and Tahoe and it works. All of the AS200 routes
show up on Alta. After analyzing the configs and the output you sent the
only thing that I noticed that's a BIG difference is that in my setup on
Telluride, the BGP routes from AS 200 show up with a next hop of
192.168.1.221. Take a look below at the BGP tables on Telluride and Alta
from my setup. 192.168.1.221 is a Vail's IP. However, when I look at the
output from Tullride that you sent, the same routes from AS 200 show up with
the next hop of 192.168.1.225, which is the IP on Taos. It's as though the
next-hop-self configuration on Vail had no effect.
Without synchronization enabled (which it is not supposed to be in this
case), if Tullride does not have an IP route to a subnet from which the BGP
next hop is derived (which in your case it does not have, as there is no
route to 192.168.1.224 in the IP table on Tullride), it is not going to pass
those routes on to Alta, which is exactly what you are having a problem
with.
What do you think? This is beginning to drive me crazy too. Take a look at
the next hop address for BGP routes from AS 200 and AS300 on Tullride, in
those instances where you got this thing to work with changing OSPF wildcard
masks or using EIGRP. Is it the IP from Vail or Taos/Tahoe? If it's from
Taos/Tahoe, them my question would be why?
Thanks.
Peter
Telluride#sh ip bgp
BGP table version is 7, local router ID is 199.1.3.1
Status codes: s suppressed, d damped, h history, * valid, > best, i -
internal
Origin codes: i - IGP, e - EGP, ? - incomplete
Network Next Hop Metric LocPrf Weight Path
*> 192.168.1.200/30 192.168.1.205 0 0 400 i
*>i192.168.1.216/30 192.168.1.221 0 100 0 200 i
*> 192.168.50.0 192.168.1.205 0 0 400 i
*> 192.168.75.0 192.168.1.205 0 0 400 i
*>i192.168.100.0 192.168.1.221 0 100 0 200 i
*>i192.168.200.0 192.168.1.221 0 100 0 200 i
Telluride#
Alta#sh ip bgp
BGP table version is 7, local router ID is 192.168.75.1
Status codes: s suppressed, d damped, h history, * valid, > best, i -
internal
Origin codes: i - IGP, e - EGP, ? - incomplete
Network Next Hop Metric LocPrf Weight Path
*> 192.168.1.200/30 0.0.0.0 0 32768 i
*> 192.168.1.216/30 192.168.1.206 0 100 200 i
*> 192.168.50.0 0.0.0.0 0 32768 i
*> 192.168.75.0 0.0.0.0 0 32768 i
*> 192.168.100.0 192.168.1.206 0 100 200 i
*> 192.168.200.0 192.168.1.206 0 100 200 i
Alta#
Michael Wong wrote:
Guys
Don't forget I changed the wildcard masks on the OSPF routing process in
Aspen and the problem got better. All the routes (except the default
generated by Taos, don't ask me why???) were propagated through to Telluride
and then to Alta. In doing this there was "no" redistribution from OSPF back
into BGP. Synchronisation was at work here. Redistribution from OSPF back
into BGP is dangerous and real-life networks do not encourage this.
I'm starting to think dodgy IOS ..... I'll try upgrading and see what
happens.
MW :)
-----Original Message-----
From: afiddler [mailto:afiddler@wi.rr.com]
Sent: Monday, 20 August 2001 2:56 am
To: young@pobox.com; Ccielab (E-mail)
Subject: Re: BGP synchronisation: Doyle page 175
--Oops! Daniel, I see what you are saying. It was looking to me like
the
192.168.1.220/30 network was between Vail and Telluride, but it is
between
Vail and Aspen.
However, if you look at Telluride's routing table and BGP table, it is
getting only OSPF routes from Aspen. If it is not redistributing routes
from OSPF to BGP, how would Alta ever get the routes?
----- Original Message -----
From: "Daniel C. Young" <danyoung99@mediaone.net>
To: "'afiddler'" <afiddler@wi.rr.com>; "'Groupstudy - CCIELAB (E-mail)'"
<ccielab@groupstudy.com>
Sent: Sunday, August 19, 2001 11:13 AM
Subject: RE: BGP synchronisation: Doyle page 175
> Hmm, I would have to disagree.
>
> Aspen does not run BGP. That's why the section is titled: "Case Study:
IBGP
> Over an IGP". Aspen is supposed to run only OSPF. Also, how can you
explain
> that Telluride still has all the original next-hops unaltered, even
though
> Vail has a next-hop-self statement on his config.
>
> I'd like to say buggy IOS, but I cannot be sure without access to them
to
do
> further testing.
>
> Regards,
> Daniel
>
> -----Original Message-----
> From: nobody@groupstudy.com [mailto:nobody@groupstudy.com]On Behalf Of
> afiddler
> Sent: Sunday, 19 August 2001 7:38 AM
> To: 'Groupstudy - CCIELAB (E-mail)'
> Subject: Re: BGP synchronisation: Doyle page 175
>
>
> I believe there is a mistake in the book. Two of the neighbor
statements
on
> Vail should refer to 192.168.1.222 instead of 192.168.1.197, which is
> Telluride's link to Aspen, not Vail. Telluride is getting all of its
routes
> from Aspen and none from Vail. Since the routes from Aspen are all
OSPF
> routes, and Telluride does not redistribute OSPF back into BGP, those
routes
> are not showing up on Alta.
>
> I ran into the same problem a few weeks ago when I did this lab. OSPF
is
> not the culprit.
>
> ----- Original Message -----
> From: "Michael Wong" <Michael.Wong@nec.com.au>
> To: <young@pobox.com>; "'Peter Rybaczyk'" <psrsam@globalins.com>
> Cc: "'Groupstudy - CCIELAB (E-mail)'" <ccielab@groupstudy.com>
> Sent: Saturday, August 18, 2001 11:39 PM
> Subject: RE: BGP synchronisation: Doyle page 175
>
>
> > Things are definitely strange !!!! ..... I thought I'd get rid of
OSPF
and
> use EIGRP instead. Guess what ..... it worked perfectly. There was
nothing
> fancy with the EIGRP configs, it was running as an IGP in place of
OSPF.
All
> the routes came through to Alta including the default route originated
from
> Taos.
> >
> > So I investigated further with OSPF and here is what I found .....
> >
> > I changed the network statement in the OSPF process on Aspen from
"network
> 192.168.1.0 0.0.0.255 area 0" to two individual network statements
with a
> quad zero mask. So I used "network 192.168.1.222 0.0.0.0 area 0" and
> "network 192.168.1.198 0.0.0.0 area 0". You wouldn't believe it .....
but
> the after that change, the routes were advertised through to Alta.
However
> only the actual network routes were advertised, no default route from
Taos.
> I couldn't believe it, so I put it back to the network wildcard mask
and
the
> routes weren't advertised, then back to the quad zero mask and routes
came
> back. This is all on the Aspen router .... bizarre ???
> >
> > I also played with the wildcard mask on the Vail and Telluride
routers,
> going between a network mask and quad zero mask ..... however this had
no
> impact on whether the routes came through to Alta. It was only the
changes
> in Aspen that made the routes come through.
> >
> > As documented in Cisco, the network statement under the OSPF process
> specifies which interface should be included in the OSPF routing
process.
It
> shouldn't affect how routes are advertised etc. However I have read in
> certain instances on this mailing list that people have had problems
with
> using a quad zero mask as opposed to a network range mask.
> >
> > What do you guys think ???? .... Dodgy IOS ???? .... or does it go
deeper
> than that ....
> >
> > MW :)
> >
> >
> >
> >
> > -----Original Message-----
> > From: Daniel C. Young [mailto:danyoung99@mediaone.net]
> > Sent: Sunday, 19 August 2001 2:04 pm
> > To: Michael Wong; 'Peter Rybaczyk'
> > Cc: 'Groupstudy - CCIELAB (E-mail)'
> > Subject: RE: BGP synchronisation: Doyle page 175
> >
> >
> >
> > Mike,
> >
> > That's funny. I see 'next-hop self' on Vail pointing to Telluride,
but
if
> > you check Telluride's BGP table all the prefixes learned from AS 300
and
> AS
> > 200 have not had their next-hop attribute altered. The issues still
seems
> to
> > be that you have a next-hop reachability issue on Telluride. But why
has
> > Vail ignore the 'next-hop self' command, though? Strange...
> >
> > A 'clear ip bgp *' perhaps on Vail?
> >
> > Let me know...
> > Daniel
> >
> > -----Original Message-----
> > From: nobody@groupstudy.com [mailto:nobody@groupstudy.com]On Behalf
Of
> > Michael Wong
> > Sent: Saturday, 18 August 2001 8:24 PM
> > To: 'Peter Rybaczyk'
> > Cc: Groupstudy - CCIELAB (E-mail)
> > Subject: RE: BGP synchronisation: Doyle page 175
> >
> >
> > OK .... here we go (ignore the real names of the routers), I
attached
the
> > configs and outputs for Tahoe, Vail, Aspen, Telluride and Alta.
> >
> > All the routes from Alta seem to be propagated out to the other
AS's,
> > however nothing is being propagated into Alta. It funny how Tahoe
gets
the
> > routes, but Alta doesn't ..... am I going crazy here ????!!!!
> >
> > Thanking you in advance ...... MW :)
> >
> >
> > *** Tahoe ***
> > !
> > router bgp 300
> > bgp log-neighbor-changes
> > network 192.168.1.212 mask 255.255.255.252
> > network 192.168.250.0
> > neighbor 192.168.1.209 remote-as 100
> > neighbor 192.168.1.209 default-originate
> > !
> >
> > p1r1#sh ip route
> > Codes: C - connected, S - static, I - IGRP, R - RIP, M - mobile, B -
BGP
> > D - EIGRP, EX - EIGRP external, O - OSPF, IA - OSPF inter
area
> > N1 - OSPF NSSA external type 1, N2 - OSPF NSSA external type
2
> > E1 - OSPF external type 1, E2 - OSPF external type 2, E - EGP
> > i - IS-IS, L1 - IS-IS level-1, L2 - IS-IS level-2, * -
candidate
> > default
> > U - per-user static route, o - ODR
> >
> > Gateway of last resort is not set
> >
> > B 192.168.75.0/24 [20/0] via 192.168.1.209, 00:34:58
> > B 192.168.200.0/24 [20/0] via 192.168.1.209, 01:19:06
> > C 192.168.250.0/24 is directly connected, Loopback0
> > B 192.168.50.0/24 [20/0] via 192.168.1.209, 00:34:58
> > 192.168.1.0/30 is subnetted, 4 subnets
> > B 192.168.1.200 [20/0] via 192.168.1.209, 00:34:58
> > B 192.168.1.216 [20/0] via 192.168.1.209, 01:19:06
> > C 192.168.1.208 is directly connected, Serial0/0
> > C 192.168.1.212 is directly connected, Loopback1
> > B 192.168.100.0/24 [20/0] via 192.168.1.209, 01:19:06
> >
> > p1r1#sh ip bgp
> > BGP table version is 17, local router ID is 192.168.250.1
> > Status codes: s suppressed, d damped, h history, * valid, > best,
i -
> > internal
> > Origin codes: i - IGP, e - EGP, ? - incomplete
> >
> > Network Next Hop Metric LocPrf Weight Path
> > *> 192.168.1.200/30 192.168.1.209 0 100 400
i
> > *> 192.168.1.212/30 0.0.0.0 0 32768 i
> > *> 192.168.1.216/30 192.168.1.209 0 100 200
i
> > *> 192.168.50.0 192.168.1.209 0 100 400
i
> > *> 192.168.75.0 192.168.1.209 0 100 400
i
> > *> 192.168.100.0 192.168.1.209 0 100 200
i
> > *> 192.168.200.0 192.168.1.209 0 100 200
i
> > *> 192.168.250.0 0.0.0.0 0 32768 i
> >
> > p1r1#sh ip bgp summary
> > BGP router identifier 192.168.250.1, local AS number 300
> > BGP table version is 17, main routing table version 17
> > 8 network entries and 8 paths using 968 bytes of memory
> > 3 BGP path attribute entries using 292 bytes of memory
> > BGP activity 12/4 prefixes, 12/4 paths
> >
> > Neighbor V AS MsgRcvd MsgSent TblVer InQ OutQ Up/Down
> > State/PfxRcd
> > 192.168.1.209 4 100 88 84 17 0 0 01:19:42
> 6
> >
> >
> >
> > *** Vail ***
> > !
> > router ospf 100
> > redistribute bgp 100 subnets
> > network 192.168.1.220 0.0.0.3 area 0
> > log-adjacency-changes
> > !
> > router bgp 100
> > bgp log-neighbor-changes
> > neighbor 192.168.1.197 remote-as 100
> > neighbor 192.168.1.197 next-hop-self
> > neighbor 192.168.1.210 remote-as 300
> > neighbor 192.168.1.225 remote-as 200
> > !
> >
> > p1r5#sh ip route
> > Codes: C - connected, S - static, I - IGRP, R - RIP, M - mobile, B -
BGP
> > D - EIGRP, EX - EIGRP external, O - OSPF, IA - OSPF inter
area
> > N1 - OSPF NSSA external type 1, N2 - OSPF NSSA external type
2
> > E1 - OSPF external type 1, E2 - OSPF external type 2, E - EGP
> > i - IS-IS, L1 - IS-IS level-1, L2 - IS-IS level-2, ia - IS-IS
inter
> > area
> > * - candidate default, U - per-user static route, o - ODR
> > P - periodic downloaded static route
> >
> > Gateway of last resort is 192.168.1.210 to network 0.0.0.0
> >
> > O E2 192.168.75.0/24 [110/1] via 192.168.1.222, 00:23:56, Serial1/1
> > B 192.168.200.0/24 [20/0] via 192.168.1.225, 01:08:09
> > B 192.168.250.0/24 [20/0] via 192.168.1.210, 01:08:30
> > O E2 192.168.50.0/24 [110/1] via 192.168.1.222, 00:23:56, Serial1/1
> > 192.168.1.0/30 is subnetted, 7 subnets
> > C 192.168.1.224 is directly connected, Serial1/3
> > O E2 192.168.1.200 [110/1] via 192.168.1.222, 00:23:56, Serial1/1
> > O 192.168.1.196 [110/791] via 192.168.1.222, 00:36:37,
Serial1/1
> > B 192.168.1.216 [20/0] via 192.168.1.225, 01:08:10
> > C 192.168.1.220 is directly connected, Serial1/1
> > C 192.168.1.208 is directly connected, Serial1/0
> > B 192.168.1.212 [20/0] via 192.168.1.210, 01:08:31
> > B 192.168.100.0/24 [20/0] via 192.168.1.225, 01:08:10
> > B* 0.0.0.0/0 [20/0] via 192.168.1.210, 00:33:44
> >
> > p1r5#sh ip bgp
> > BGP table version is 18, local router ID is 192.168.1.226
> > Status codes: s suppressed, d damped, h history, * valid, > best,
i -
> > internal
> > Origin codes: i - IGP, e - EGP, ? - incomplete
> >
> > Network Next Hop Metric LocPrf Weight Path
> > *> 0.0.0.0 192.168.1.210 0 300 i
> > *>i192.168.1.200/30 192.168.1.205 0 100 0 400 i
> > *> 192.168.1.212/30 192.168.1.210 0 0 300 i
> > *> 192.168.1.216/30 192.168.1.225 0 0 200 i
> > *>i192.168.50.0 192.168.1.205 0 100 0 400 i
> > *>i192.168.75.0 192.168.1.205 0 100 0 400 i
> > *> 192.168.100.0 192.168.1.225 0 0 200 i
> > *> 192.168.200.0 192.168.1.225 0 0 200 i
> > *> 192.168.250.0 192.168.1.210 0 0 300 i
> >
> >
> > *** Aspen ***
> > !
> > router ospf 100
> > log-adjacency-changes
> > network 192.168.1.0 0.0.0.255 area 0
> > !
> >
> > p1r2#sh ip route
> > Codes: C - connected, S - static, I - IGRP, R - RIP, M - mobile, B -
BGP
> > D - EIGRP, EX - EIGRP external, O - OSPF, IA - OSPF inter
area
> > N1 - OSPF NSSA external type 1, N2 - OSPF NSSA external type
2
> > E1 - OSPF external type 1, E2 - OSPF external type 2, E - EGP
> > i - IS-IS, L1 - IS-IS level-1, L2 - IS-IS level-2, * -
candidate
> > default
> > U - per-user static route, o - ODR
> >
> > Gateway of last resort is not set
> >
> > O E2 192.168.75.0/24 [110/1] via 192.168.1.197, 00:26:02,
Ethernet0/0
> > O E2 192.168.200.0/24 [110/1] via 192.168.1.221, 00:38:44, Serial0/0
> > O E2 192.168.250.0/24 [110/1] via 192.168.1.221, 00:38:44, Serial0/0
> > O E2 192.168.50.0/24 [110/1] via 192.168.1.197, 00:26:03,
Ethernet0/0
> > 192.168.1.0/30 is subnetted, 5 subnets
> > O E2 192.168.1.200 [110/1] via 192.168.1.197, 00:26:03,
Ethernet0/0
> > C 192.168.1.196 is directly connected, Ethernet0/0
> > O E2 192.168.1.216 [110/1] via 192.168.1.221, 00:38:44, Serial0/0
> > C 192.168.1.220 is directly connected, Serial0/0
> > O E2 192.168.1.212 [110/1] via 192.168.1.221, 00:38:45, Serial0/0
> > O E2 192.168.100.0/24 [110/1] via 192.168.1.221, 00:38:45, Serial0/0
> >
> >
> > *** Telluride ***
> > !
> > router ospf 100
> > log-adjacency-changes
> > redistribute bgp 100 subnets
> > network 192.168.1.196 0.0.0.3 area 0
> > !
> > router bgp 100
> > bgp log-neighbor-changes
> > neighbor 192.168.1.205 remote-as 400
> > neighbor 192.168.1.221 remote-as 100
> > neighbor 192.168.1.221 next-hop-self
> > !
> >
> > p1r6#sh ip route
> > Codes: C - connected, S - static, I - IGRP, R - RIP, M - mobile, B -
BGP
> > D - EIGRP, EX - EIGRP external, O - OSPF, IA - OSPF inter
area
> > N1 - OSPF NSSA external type 1, N2 - OSPF NSSA external type
2
> > E1 - OSPF external type 1, E2 - OSPF external type 2, E - EGP
> > i - IS-IS, L1 - IS-IS level-1, L2 - IS-IS level-2, ia - IS-IS
inter
> > area
> > * - candidate default, U - per-user static route, o - ODR
> > P - periodic downloaded static route
> >
> > Gateway of last resort is not set
> >
> > B 192.168.75.0/24 [20/0] via 192.168.1.205, 00:27:17
> > O E2 192.168.200.0/24 [110/1] via 192.168.1.198, 00:39:59,
FastEthernet0/0
> > O E2 192.168.250.0/24 [110/1] via 192.168.1.198, 00:39:59,
FastEthernet0/0
> > B 192.168.50.0/24 [20/0] via 192.168.1.205, 00:27:17
> > 192.168.1.0/30 is subnetted, 6 subnets
> > B 192.168.1.200 [20/0] via 192.168.1.205, 00:27:17
> > C 192.168.1.204 is directly connected, FastEthernet0/1
> > C 192.168.1.196 is directly connected, FastEthernet0/0
> > O E2 192.168.1.216 [110/1] via 192.168.1.198, 00:40:00,
FastEthernet0/0
> > O 192.168.1.220 [110/65] via 192.168.1.198, 00:40:00,
> FastEthernet0/0
> > O E2 192.168.1.212 [110/1] via 192.168.1.198, 00:40:00,
FastEthernet0/0
> > O E2 192.168.100.0/24 [110/1] via 192.168.1.198, 00:40:00,
FastEthernet0/0
> >
> >
> > p1r6#sh ip bgp
> > BGP table version is 12, local router ID is 192.168.1.206
> > Status codes: s suppressed, d damped, h history, * valid, > best,
i -
> > internal
> > Origin codes: i - IGP, e - EGP, ? - incomplete
> >
> > Network Next Hop Metric LocPrf Weight Path
> > * i0.0.0.0 192.168.1.210 100 0 300 i
> > *> 192.168.1.200/30 192.168.1.205 0 0 400 i
> > * i192.168.1.212/30 192.168.1.210 0 100 0 300 i
> > * i192.168.1.216/30 192.168.1.225 0 100 0 200 i
> > *> 192.168.50.0 192.168.1.205 0 0 400 i
> > *> 192.168.75.0 192.168.1.205 0 0 400 i
> > * i192.168.100.0 192.168.1.225 0 100 0 200 i
> > * i192.168.200.0 192.168.1.225 0 100 0 200 i
> > * i192.168.250.0 192.168.1.210 0 100 0 300 i
> >
> > p1r6#sh ip bgp summary
> > BGP router identifier 192.168.1.206, local AS number 100
> > BGP table version is 12, main routing table version 12
> > 9 network entries and 9 paths using 1197 bytes of memory
> > 4 BGP path attribute entries using 240 bytes of memory
> > 3 BGP AS-PATH entries using 72 bytes of memory
> > 0 BGP route-map cache entries using 0 bytes of memory
> > 0 BGP filter-list cache entries using 0 bytes of memory
> > BGP activity 13/175 prefixes, 13/4 paths, scan interval 15 secs
> >
> > Neighbor V AS MsgRcvd MsgSent TblVer InQ OutQ Up/Down
> > State/PfxRcd
> > 192.168.1.205 4 400 48 49 12 0 0 00:30:32
> 3
> > 192.168.1.221 4 100 49 51 12 0 0 00:43:36
> 6
> >
> >
> > *** Alta ***
> > !
> > router bgp 400
> > bgp log-neighbor-changes
> > network 192.168.1.200 mask 255.255.255.252
> > network 192.168.50.0
> > network 192.168.75.0
> > neighbor 192.168.1.206 remote-as 100
> > !
> >
> > p1r3#sh ip route
> > Codes: C - connected, S - static, I - IGRP, R - RIP, M - mobile, B -
BGP
> > D - EIGRP, EX - EIGRP external, O - OSPF, IA - OSPF inter
area
> > N1 - OSPF NSSA external type 1, N2 - OSPF NSSA external type
2
> > E1 - OSPF external type 1, E2 - OSPF external type 2, E - EGP
> > i - IS-IS, L1 - IS-IS level-1, L2 - IS-IS level-2, * -
candidate
> > default
> > U - per-user static route, o - ODR
> >
> > Gateway of last resort is not set
> >
> > C 192.168.75.0/24 is directly connected, Loopback1
> > C 192.168.50.0/24 is directly connected, Loopback0
> > 192.168.1.0/30 is subnetted, 2 subnets
> > C 192.168.1.200 is directly connected, Loopback2
> > C 192.168.1.204 is directly connected, Ethernet0/0
> >
> > p1r3#sh ip bgp
> > BGP table version is 6, local router ID is 192.168.75.1
> > Status codes: s suppressed, d damped, h history, * valid, > best,
i -
> > internal
> > Origin codes: i - IGP, e - EGP, ? - incomplete
> >
> > Network Next Hop Metric LocPrf Weight Path
> > *> 192.168.1.200/30 0.0.0.0 0 32768 i
> > *> 192.168.50.0 0.0.0.0 0 32768 i
> > *> 192.168.75.0 0.0.0.0 0 32768 i
> >
> > p1r3#sh ip bgp summary
> > BGP router identifier 192.168.75.1, local AS number 400
> > BGP table version is 6, main routing table version 6
> > 3 network entries and 3 paths using 363 bytes of memory
> > 1 BGP path attribute entries using 148 bytes of memory
> > BGP activity 4/1 prefixes, 4/1 paths
> >
> > Neighbor V AS MsgRcvd MsgSent TblVer InQ OutQ Up/Down
> > State/PfxRcd
> > 192.168.1.206 4 100 34 33 6 0 0 00:29:35
> 0
> >
> >
> >
> >
> >
> > -----Original Message-----
> > From: Peter Rybaczyk [mailto:psrsam@globalins.com]
> > Sent: Sunday, 19 August 2001 2:23 am
> > To: Michael Wong
> > Cc: Groupstudy - CCIELAB (E-mail)
> > Subject: Re: BGP synchronisation: Doyle page 175
> >
> >
> > Michael,
> > I duplicated the setup but can't duplicate the problem. Can you send
> > relevent portions of your configs (BGP and OSPF parts) for all of
the
> > routers? Also the IP table for Telluride would be helpful.
> > Thanks.
> > Peter
> >
> > Michael Wong wrote:
> >
> > > BGP gurus ..... I am trying to do the example in Doyle Vol II,
page
175
> > with BGP synchronisation and OSPF.
> > >
> > > I have BGP routes going between AS100, AS300 and AS200 .....
however
for
> > some reason the routes from these AS's are not being advertised into
> AS400.
> > If I do a debug on the Telluride router I get the output below. I
cannot
> > seem to find what this output means anywhere on the Cisco site. I am
> > assuming it's got something to do with these routes not being able
to be
> > propagated to Alta.
> > >
> > > 00:07:16: BGP(0): no valid path for 0.0.0.0/0
> > > 00:07:16: BGP(0): no valid path for 192.168.1.208/30
> > > 00:07:16: BGP(0): no valid path for 192.168.1.212/30
> > > 00:07:16: BGP(0): no valid path for 192.168.1.216/30
> > > 00:07:16: BGP(0): no valid path for 192.168.1.224/30
> > > 00:07:16: BGP(0): no valid path for 192.168.100.0/24
> > > 00:07:16: BGP(0): no valid path for 192.168.200.0/24
> > > 00:07:16: BGP(0): no valid path for 192.168.250.0/24
> > >
> > > If I look in Alta's BGP routing table, all I see is the following
(no
> > routes from the other AS's), even though it has an adjacency with
> Telluride
> > ....
> > >
> > > BGP table version is 6, local router ID is 192.168.75.1
> > > Status codes: s suppressed, d damped, h history, * valid, > best,
i -
> > internal
> > > Origin codes: i - IGP, e - EGP, ? - incomplete
> > >
> > > Network Next Hop Metric LocPrf Weight Path
> > > *> 192.168.1.200/30 0.0.0.0 0 32768 i
> > > *> 192.168.50.0 0.0.0.0 0 32768 i
> > > *> 192.168.75.0 0.0.0.0 0 32768 i
> > >
> > > Telluride's BGP table has all the routes so I'm assuming that
> > synchronisation is OK.
> > >
> > > BGP table version is 6, local router ID is 192.168.1.206
> > > Status codes: s suppressed, d damped, h history, * valid, > best,
i -
> > internal
> > > Origin codes: i - IGP, e - EGP, ? - incomplete
> > >
> > > Network Next Hop Metric LocPrf Weight Path
> > > * i0.0.0.0 192.168.1.221 100 0 100 i
> > > *> 192.168.1.200/30 192.168.1.205 0 0 400 i
> > > * i192.168.1.212/30 192.168.1.221 0 100 0 300 i
> > > * i192.168.1.216/30 192.168.1.221 0 100 0 100 i
> > > *> 192.168.50.0 192.168.1.205 0 0 400 i
> > > *> 192.168.75.0 192.168.1.205 0 0 400 i
> > > * i192.168.100.0 192.168.1.221 0 100 0 100 i
> > > * i192.168.200.0 192.168.1.221 409600 100 0 100 i
> > > * i192.168.250.0 192.168.1.221 0 100 0 300 i
> > >
> > > The previous example used the same network without BGP
synchronisation
> and
> > just using IBGP, this was OK and routes were propagated into AS400.
> > >
> > > Help please ....... MW
> > > **Please read:http://www.groupstudy.com/list/posting.html
> > **Please read:http://www.groupstudy.com/list/posting.html
> > **Please read:http://www.groupstudy.com/list/posting.html
> **Please read:http://www.groupstudy.com/list/posting.html
**Please read:http://www.groupstudy.com/list/posting.html
**Please read:http://www.groupstudy.com/list/posting.html
**Please read:http://www.groupstudy.com/list/posting.html
This archive was generated by hypermail 2.1.4 : Thu Jun 13 2002 - 10:31:54 GMT-3