From: Nick Shah (nshah@xxxxxxxxxxxxxx)
Date: Mon Jun 03 2002 - 00:36:18 GMT-3
There is one more way to do it (albeit much similar to redistribution) and
that is to have the *border router* generate a default route. This will act
much the same way as redistributing BGP into IGP (with some limitations).
rgds
Nick
-----Original Message-----
From: Ludwig Morales <lud.morales@codetel.net.do>
To: Michael Popovich <m.popovich@mchsi.com>
Cc: ccielab@groupstudy.com <ccielab@groupstudy.com>
Date: Monday, 3 June 2002 11:21
Subject: Re: PRPOBLEM WITH BGP SYNCHRONIZATION
>yes network 192.168.100.0 is in the BGP table of the other peers,
apparently
>i had it all wrong, i was trying to make this network (learned from EBGP at
>the border router and passed as IBGP to interna routers) appear in the
>internal routers (look at solies page 175, i was trying to make that
network
>appear on aspen and telluride's routing table) by redistributing static
>routes and doing all kinds of stuff but aparently I was missing a rule,
>"IBGP learned routes are no entered in the routing table when
>synchronization is enable" at least this is what Solie says in Routing
>TCP/IP Vol.2 page170,
>
>This brings up my next quetion, is redistribution at the border router the
>only way to make the internal routers (IBGP peering routers) know about the
>external networks?
>
>Thanks for your help!!
>
>Ludwig
>
>
>
>----- Original Message -----
>From: "Michael Popovich" <m.popovich@mchsi.com>
>To: "Ludwig Morales" <lud.morales@codetel.net.do>
>Sent: Sunday, June 02, 2002 8:26 PM
>Subject: Re: PRPOBLEM WITH BGP SYNCHRONIZATION
>
>
>> If you go to the other IBGP peers what do you see when a "show ip bgp"
>>
>> is the 192.168.100.0 network in their bgp table?
>>
>> If so what do you see when you do a "show ip bgp 192.168.100.0" on the
>other
>> routers? That should give you a clue as to what the issue is.
>>
>> I would be interested in see what the other routers show with the above
>> commands.
>>
>> MP
>> ----- Original Message -----
>> From: "Ludwig Morales" <lud.morales@codetel.net.do>
>> To: <ccielab@groupstudy.com>
>> Sent: Sunday, June 02, 2002 6:03 PM
>> Subject: PRPOBLEM WITH BGP SYNCHRONIZATION
>>
>>
>> > Pie ChartsHi everyone!
>> >
>> > Can someone digest the BGP synchronization rule for me and explain it,
>for
>> > what i thought BGP would not put a route in the routing table until it
>was
>> > learn from an IGP if sync was on, well this router has 2 IBGP sessions
>> with
>> > border routers, 1 border router advertises the netwotk 192.168.100.0/24
>> (you
>> > can see that i learn this router int the BGP table) so i made a static
>> route
>> > and redistribute it in OSPF, no i have a route to 192.168.100.0/24 in
my
>> > routing table but still BGP would not put it's route in the table, what
>am
>> i
>> > doing wrong here? how do i make the IBGP peering routers learn the BGP
>> > routes without actually redistributing IGP?
>> >
>> > Regards,
>> >
>> > Ludwig
>> >
>> > !
>> > !
>> > interface Loopback0
>> > ip address 1.1.1.1 255.255.255.0
>> > !
>> > interface Ethernet0
>> > no ip address
>> > shutdown
>> > !
>> > interface Serial0
>> > no ip address
>> > encapsulation frame-relay
>> > frame-relay lmi-type cisco
>> > !
>> > interface Serial0.1 point-to-point
>> > ip address 192.168.1.222 255.255.255.252
>> > frame-relay interface-dlci 108
>> > !
>> > interface Serial0.2 point-to-point
>> > ip address 192.168.1.198 255.255.255.252
>> > frame-relay interface-dlci 107
>> > !
>> > interface Serial1
>> > no ip address
>> > !
>> > router ospf 100
>> > log-adjacency-changes
>> > redistribute static subnets
>> > network 192.168.1.0 0.0.0.255 area 0
>> > !
>> > router bgp 100
>> > bgp log-neighbor-changes
>> > network 192.168.1.196 mask 255.255.255.252
>> > network 192.168.1.220 mask 255.255.255.252
>> > neighbor 192.168.1.197 remote-as 100
>> > neighbor 192.168.1.221 remote-as 100
>> > !
>> > ip classless
>> > ip route 192.168.100.0 255.255.255.0 192.168.1.221
>> > ip http server
>> > !
>> > !
>> > alias exec f show running-config | begin
>> > !
>> > line con 0
>> > line 1 7
>> > modem Host
>> > transport input all
>> > stopbits 1
>> > line 8
>> > modem InOut
>> > transport input all
>> > stopbits 1
>> > line aux 0
>> > line vty 0 4
>> > login
>> > !
>> > end
>> >
>> > R1#sh ip ro
>> > 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
>intea
>> > * - candidate default, U - per-user static route, o - ODR
>> > P - periodic downloaded static route
>> >
>> > Gateway of last resort is not set
>> >
>> > 1.0.0.0/24 is subnetted, 1 subnets
>> > C 1.1.1.0 is directly connected, Loopback0
>> > 192.168.1.0/30 is subnetted, 3 subnets
>> > O 192.168.1.224 [110/74] via 192.168.1.221, 00:02:28, Serial0.1
>> > C 192.168.1.196 is directly connected, Serial0.2
>> > C 192.168.1.220 is directly connected, Serial0.1
>> > S 192.168.100.0/24 [1/0] via 192.168.1.221
>> > R1#sh ip bgp
>> > BGP table version is 5, local router ID is 1.1.1.1
>> > Status codes: s suppressed, d damped, h history, * valid, > best, i -
>intl
>> > Origin codes: i - IGP, e - EGP, ? - incomplete
>> >
>> > Network Next Hop Metric LocPrf Weight Path
>> > *> 192.168.1.196/30 0.0.0.0 0 32768 i
>> > * i192.168.1.204/30 192.168.1.197 0 100 0 i
>> > * i192.168.1.208/30 192.168.1.221 0 100 0 i
>> > *> 192.168.1.220/30 0.0.0.0 0 32768 i
>> > *>i192.168.1.224/30 192.168.1.221 0 100 0 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
>> > R1#
This archive was generated by hypermail 2.1.4 : Tue Jul 02 2002 - 08:12:21 GMT-3