From: CCIE FUN (ccieexam2002@yahoo.com)
Date: Wed Mar 12 2003 - 02:57:49 GMT-3
Mohamed
I don't see a route to 5.5.5.5 in R2's routing table.
or is it intentionally not shown.
well i think the deal with BGP is it that if does not
have a valid path then it does not advertise the
routes to BGP (both IBGP or EBGP) peers.
First it needs to get to its next hop and then it will
be able to advertise that route to its BGP peers.
Try this :
I see you are learning 200.200.200.0/24 via
120.20.234.4
establish a neighbor relationship with 120.20.234.4 on
R2 and do the same thing on Router A establish BGP
peering with R2's address which is reachable(pingable)
via an IGP from Router A.
I think this should work.
--- Donny MATEO <donny.mateo@sg.ca-indosuez.com>
wrote:
> ----- Forwarded by Donny
> MATEO/ADPC/ASIA/BANQUE_INDOSUEZ/FR on 11-03-2003
> 14:45 -----
>
>
>
> Donny MATEO
>
>
> To:
> <mohammed@sulafsolutions.com>
>
> 11-03-2003 14:20 cc:
>
>
>
> Subject: RE: BGP problem, BGP's relation with
> IGPs(Document link: Donny MATEO)
>
>
>
>
>
>
> No problem,
>
> router id has nothing to do with subnet
> advertisement. Even if that subnet is not known to
> the other router it doesn't matter. It's only used
> for ID.
> try it out first and see how it goes.
>
> Donny
>
>
>
>
>
> "Mohammed Al-zubi"
>
>
> <mohammed@sulafsol To:
> "'Donny MATEO'"
> <donny.mateo@sg.ca-indosuez.com>
>
> utions.com> cc:
> <ccielab@groupstudy.com>,
> <nobody@groupstudy.com>
>
> Subject: RE: BGP problem, BGP's relation with IGPs
>
> 11-03-2003 14:07
>
>
> Please respond to
>
>
> mohammed
>
>
>
>
>
>
>
>
>
>
>
>
> Well, I failed to mention this, it gets complicated,
> router A has a loopback
> 5.5.5.5, and it has to be in an ospf area that is
> deferent than the area
> between A and B, and router B has a loopback
> 2.2.2.2 but that loopback is
> in another routing protocol (ISIS) which is
> distributed into OSPF at some
> router on the network, the IBGP session between A
> and B uses loopback
> (update-source ...) and A see's the loopback of B
> and vise versa. let me
> know what you think
>
> Mohamemd
>
> -----Original Message-----
> From: Donny MATEO
> [mailto:donny.mateo@sg.ca-indosuez.com]
> Sent: Monday, March 10, 2003 9:55 PM
> To: Mohammed Al-zubi
> Cc: ccielab@groupstudy.com; nobody@groupstudy.com
> Subject: Re: BGP problem, BGP's relation with IGPs
>
>
>
> Hi,
> I think you got one of those problem indicated by
> the OSPF router ID should
> match the BGP router ID.
> fixed you BGP router id or OSPF router ID to the
> same value.
> >From your show command either you fix your ospf
> router id to 200.200.200.5
> or you fix your BGP router id to 5.5.5.5
>
> Regards,
> Donny
>
>
>
> "Mohammed Al-zubi"
> <mohammed@sulafsol To:
> <ccielab@groupstudy.com>
> utions.com> cc:
> Sent by:
> Subject: BGP problem, BGP's
> relation with IGPs
> nobody@groupstudy.
> com
>
>
> 11-03-2003 09:26
> Please respond to
> "Mohammed Al-zubi"
>
>
>
>
>
>
> Hello group,
> the issue is related to synchronization, from my
> understanding (and it
> could be wrong) is that if sync is enabled (default)
> a route would not be
> advertised to an EBGP peer unless that route is in
> the routing table of the
> sending router. So here comes the question, I have
> 2 routers that are not
> directly connected that have an IBGP session between
> them, A and B. B also
> has an EBGP session with C. There is a loopback on
> A with the address
> 200.200.200.5 /24, and there is a network statement
> in the BGP process for
> that address on A, also, the loopback is part of the
> OSPF process so router
> B sees the route in its routing table as an OSPF
> route, it also sees the
> route in the BGP RIP, but its not synchronized. Why
> is it not synched if
> its in the routing table, I added a static route on
> router B for
> 200.200.200.0/24 and pointed it to null zero, and it
> works, I delete it, the
> B router stops advertising that route to its EBGP
> neighbors and the route
> becomes not synchronized. I have attached the
> different shows I did
>
>
> <----IBGP----><-----EBGP---->
> A-------X----Y-----B(R2)-------------------C
>
>
>
> 2#sho ip route 200.200.200.0
> Routing entry for 200.200.200.0/24
> Known via "ospf 1", distance 110, metric 846, type
> inter area
> Last update from 120.20.234.4 on Serial0/0.234,
> 00:06:05 ago
> Routing Descriptor Blocks:
> * 120.20.234.4, from 5.5.5.5, 00:06:05 ago, via
> Serial0/0.234
> Route metric is 846, traffic share count is 1
>
>
> R2#sho 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
> O IA 200.200.200.0/24 [110/846] via 120.20.234.4,
> 00:06:35, Serial0/0.234
> 170.70.0.0/24 is subnetted, 10 subnets
> D 170.70.13.0 [90/158208] via 120.20.23.7,
> 00:19:22, FastEthernet0/0
> D 170.70.15.0 [90/158208] via 120.20.23.7,
> 00:19:22, FastEthernet0/0
>
=== message truncated ===
This archive was generated by hypermail 2.1.4 : Sat Apr 05 2003 - 08:51:37 GMT-3