From: ying chang (ying_c@xxxxxxxxxxx)
Date: Mon Apr 29 2002 - 01:57:14 GMT-3
Hi Parry,
That's what I thought. Now R5 has 220.128.1.0/24 in its routing table, but
it doesn't have a default route. How can you generate a default route into
eigrp when there's no default route in the routing table? eigrp understands
0/0 route, but there's no ospf "default-info originate always route-map ..."
equivalent command that I'm aware of.
I can have R2 generate 0/0 route into R5 and have R5 check 220.128.1.0/24
and send both 0/0 and 220.128.1.0/24 into R6, but I don't think this is the
solution the question is asking for though.
Thanks,
Chang
>From: "Chua, Parry" <Parry.Chua@compaq.com>
>To: "ying chang" <ying_c@hotmail.com>, <ccielab@groupstudy.com>
>Subject: RE: Solie "The Enchilada" BGP default route question
>Date: Mon, 29 Apr 2002 12:07:11 +0800
>
>This is how I interpret this question, R5 must receive a bgp route of
>220.128.1.0/24 and then it will generate a default into eigrp.
>
> > Parry Chua
> >
> >
>
>
>-----Original Message-----
>From: ying chang [mailto:ying_c@hotmail.com]
>Sent: Monday, April 29, 2002 11:30 AM
>To: ccielab@groupstudy.com
>Subject: Solie "The Enchilada" BGP default route question
>
>
>The question is from Solie's "The Enchilada" section X: BGP configuration,
>question 3:
>
>"Have R5 advertise a default route to the ATM network if and only if it has
>the route 220.128.1.0/24."
>
>For those who don't have the book, the topology is like below:
>
>220.128.1.0--R4(AS4)---R7(As2001)----R2(AS2001)---R5(AS5)---eigrp---R6
>
>Where ATM cloud is between R5 and R6, but any media would do.
>
>I personally don't think this problem is solvable unless there is a default
>route in R5 that we can redistribute into R6. Although the default route
>can
>be generated from R4, R7 or R2 dynamically or statically define in R5, but
>I'm not sure if it is allowed.
>
>The solution provided from CiscoPress for this question is incorrect, it
>generates default route towards to bgp world instead of R6. I am wondering
>if someone has a creative way to solve this problem.
>
>Thanks,
>Chang
>
>
>
This archive was generated by hypermail 2.1.4 : Thu Jun 13 2002 - 10:58:21 GMT-3