From: Adel Abushaev (adel@netmasterclass.net)
Date: Mon Dec 29 2003 - 11:03:45 GMT-3
Would you please send the following configuration:
On R3:
1. sh ip bgp sum
2. sh ip bgp 192.168.104.0
sh ip bgp 192.168.105.0
sh ip bgp 192.168.100.0
3. sh ip ospf database | beg Ex
On R2:
1. sh ip bgp
On R4: sh ip bgp sum
Thanks,
Adel Abouchaev
CCIE# 12037, MCSE
http://www.netmasterclass.net
----- Original Message -----
From: "Jeff Nelson" <jnelson@rackspace.com>
To: <ccielab@groupstudy.com>
Sent: Sunday, December 28, 2003 11:40 PM
Subject: route reflection--netmaster sample
> I've been going throught the netmaster sample and I came across an issue
with the route reflection of R3.
> It short, it does seem to be passing along the 192.168 routes to R4.
>
> no sync is configured on R4 (it is receiveing the 3.0.0.0 route, but I can
see from a show blahblah advertised routes that R3 is not re-advertising the
192.168 range)
>
> bgp is being redistributed into OSPF on R2
>
> There does not seem to be a valid reason, but I'm sure I'm missing
?something? No time to waste time, but this kind of stuff should be cake.
>
> Here is the bgp configs from each router:
> r4:
> router bgp 64600
> no synchronization
> bgp log-neighbor-changes
> neighbor 172.16.34.3 remote-as 64600
>
> r3:
> router bgp 64600
> bgp log-neighbor-changes
> network 3.0.0.0
> neighbor 172.16.34.4 remote-as 64600
> neighbor 172.16.34.4 route-reflector-client
> neighbor 172.16.123.2 remote-as 64600
> neighbor 172.16.123.2 route-reflector-client
>
> r2:
> router bgp 64600
> bgp log-neighbor-changes
> neighbor 172.16.123.1 remote-as 100
> neighbor 172.16.123.3 remote-as 64600
>
> r1
> router bgp 100
> no synchronization
> bgp log-neighbor-changes
> aggregate-address 192.168.100.0 255.255.252.0 as-set summary-only
> neighbor 172.16.17.7 remote-as 700
> neighbor 172.16.17.7 remove-private-AS
> neighbor 172.16.123.2 remote-as 64600
> no auto-summary
>
> This is the routing table on R3:
> O E2 192.168.104.0/24 [110/1] via 172.16.123.1, 00:06:27, Serial0/1
> 3.0.0.0/24 is subnetted, 1 subnets
> C 3.3.3.0 is directly connected, Loopback31
> O E2 192.168.105.0/24 [110/1] via 172.16.123.1, 00:06:27, Serial0/1
> 172.16.0.0/16 is variably subnetted, 12 subnets, 4 masks
> O IA 172.16.50.0/24 [110/129] via 172.16.123.2, 00:06:27, Serial0/1
> D EX 172.16.40.0/23 [170/156160] via 172.16.34.4, 02:29:34,
FastEthernet0/0
> C 172.16.34.0/24 is directly connected, FastEthernet0/0
> C 172.16.28.0/22 is directly connected, Loopback30
> O IA 172.16.25.0/24 [110/128] via 172.16.123.2, 00:06:28, Serial0/1
> O IA 172.16.20.0/24 [110/65] via 172.16.123.2, 00:06:28, Serial0/1
> O E2 172.16.17.0/24 [110/100] via 172.16.123.1, 00:06:28, Serial0/1
> O E2 172.16.2.0/24 [110/20] via 172.16.123.2, 00:06:28, Serial0/1
> C 172.16.123.0/24 is directly connected, Serial0/1
> O E2 172.16.88.0/24 [110/100] via 172.16.123.1, 00:06:28, Serial0/1
> O E2 172.16.80.0/27 [110/100] via 172.16.123.1, 00:06:28, Serial0/1
> O E2 172.16.77.0/24 [110/100] via 172.16.123.1, 00:06:28, Serial0/1
> O*E2 0.0.0.0/0 [110/1] via 172.16.123.2, 00:06:28, Serial0/1
> O E2 192.168.100.0/22 [110/1] via 172.16.123.1, 00:06:28, Serial0/1
>
> Here is the bgp table from R3 (note type is IGP and not incomplete because
I was playing with how it was injected to see if it would propagate--of
course it didn't)
> Network Next Hop Metric LocPrf Weight Path
> *> 3.0.0.0 0.0.0.0 0 32768 i
> * i192.168.100.0/22 172.16.123.1 100 0 100 700 i
> * i192.168.104.0 172.16.123.1 100 0 100 700 i
> * i192.168.105.0 172.16.123.1 100 0 100 700 i
>
>
> Would appreciate a tip from someone that's gone through this scenario.
>
> Thanks,
> Jeff
>
> _______________________________________________________________________
> Please help support GroupStudy by purchasing your study materials from:
> http://shop.groupstudy.com
>
> Subscription information may be found at:
> http://www.groupstudy.com/list/CCIELab.html
This archive was generated by hypermail 2.1.4 : Sat Jan 03 2004 - 08:25:46 GMT-3