Re: OSPF route-type per neighbor

Routes had wrong names:

 1.1.1.0/24 |R1--R3| |R2-------R4]
                 [OSPF 1 ][OSPF 2]

R1 = ASBR redistributing default E2
R3 = Internal OSPF router
R2 = ASBR, have it running a separate OSPF process for the link to R4 an
then redistribute between the OSPF processes.
R4 = internal OSPF router

You can use the route-map to set the desired routes to E1, however all the
others from OSPF1 will be E2.

On Wed, Dec 18, 2013 at 10:37 AM, Sam Bibby <sammybibs_at_gmail.com> wrote:

> Ahh shoot, well it was worth a look i suppose.
>
> The only other thing I can think of that you can do is make separate
> routing instance and redistribute between them:
>
>
> 1.1.1.0/24 |R1--R3| |R2-------R4]
> [OSPF 1 ][OSPF 2]
>
> R1 = ASBR redistributing default E2
> R2 = Internal OSPF router
> R3 = ASBR, have it running a separate OSPF process for the link to R4 an
> then redistribute between the OSPF processes.
> R4 = internal OSPF router
>
> You can use the route-map to set the desired routes to E1, however all the
> others from OSPF1 will be E2.
>
> Sam.
>
>
> On Wed, Dec 18, 2013 at 10:31 AM, Alexei Monastyrnyi <alexeim73_at_gmail.com>wrote:
>
>> Hey.
>> PBR won't work I am afraid, that route-map functionality is for
>> redistribution only.
>> Have just tested in the lab, no cigar... :-)
>>
>> A.
>>
>>
>> On 18 December 2013 10:14, Sam Bibby <sammybibs_at_gmail.com> wrote:
>>
>>> Sam,
>>>
>>> On R1 when redistributing set them as E2 as you put them in, that's the
>>> easy part.
>>>
>>> For making them E1 on r2 on ingress you could *try*:
>>>
>>> !R2
>>> ip prefix-list SET->E1->To->E2 permit 1.1.1.0/24
>>> !
>>> route-map MED_TYPE_MOD permit 10
>>> match ip address prefix-list SET->E1->To->E2
>>> set metric-type type-1
>>> !
>>> route-map MED_TYPE_MOD permit 1000
>>> !
>>> Interface fas 0/0 !!!whatever interface is learning the routes
>>> ip policy route-map MED_TYPE_MOD
>>> !
>>>
>>>
>>> I am not saying this will work, but it may be worth giving it a shot in
>>> the lab. Or you could try applying the route map within ospf:
>>> !!R2
>>> router osfp 1
>>> distribute-list route-map MED_TYPE_MOD in
>>>
>>> But as Al said, "would make the database inconsistent", so you prob can
>>> do it, but you may break stuff.
>>>
>>> My 2 cents :)
>>>
>>> \Sam
>>>
>>>
>>>
>>>
>>> On Wed, Dec 18, 2013 at 8:59 AM, Alexei Monastyrnyi <alexeim73_at_gmail.com
>>> > wrote:
>>>
>>>> Hi.
>>>> I reckon you can not, as the prefix is in the OSPF database and
>>>> manipulating the routs type on hop by hop basis would make the database
>>>> inconsistent. Entire OSPF logic relies on the database being consistent
>>>> across the board.
>>>>
>>>> Unless I am missing something.
>>>>
>>>> Cheers
>>>> A.
>>>>
>>>> Sent from my iPhone
>>>>
>>>> > On 18 dec 2013, at 09:39, sameer khan <khanzadap_at_hotmail.com> wrote:
>>>> >
>>>> > hey folks
>>>> > 1.1.1.0/24|R1--R3| <http://1.1.1.0/24%7CR1--R3%7C> |R2--R4
>>>> >
>>>> > R1 is the asbr redistributing routes from rip (1.1.1.0/24). Is it
>>>> possible to
>>>> > set route-type to E1 for R2 and E2 for R3.
>>>> > Thanks
>>>> >
>>>> >
>>>> > Blogs and organic groups at http://www.ccie.net
>>>> >
>>>> >
>>>> _______________________________________________________________________
>>>> > Subscription information may be found at:
>>>> > http://www.groupstudy.com/list/CCIELab.html
>>>>
>>>>
>>>> Blogs and organic groups at http://www.ccie.net
>>>>
>>>> _______________________________________________________________________
>>>> Subscription information may be found at:
>>>> http://www.groupstudy.com/list/CCIELab.html

Blogs and organic groups at http://www.ccie.net
Received on Wed Dec 18 2013 - 10:38:48 ART