From: Niall El-Assaad (nelassaa@xxxxxxxxx)
Date: Mon Apr 30 2001 - 17:17:13 GMT-3
Its shown here for OSPF into RIP by using a static.
http://www.cisco.com/warp/public/105/52.htmlb
=======================================================
Niall El-Assaad, Systems Engineer
EMEA-UK Retail Finance North
C i s c o S y s t e m s Mobile: +44 (0)772 088 4650
VMail: +44 (0)208 734 4206
| | Fax: +44 (0)161 864 4508
| |
||| |||
.:|||||:..:|||||:. E-mail: nelassaa@cisco.com
------------------ Web : http://www.cisco.com
Crescent House, Towers Business Park, Wilmslow Road,
Didsbury, Manchester M20 2JE, United Kingdom
========================================================
-----Original Message-----
From: nobody@groupstudy.com [mailto:nobody@groupstudy.com]On Behalf Of
Jim Graves
Sent: 30 April 2001 16:08
To: wgustavus@mentortech.com; jim.fitzpatrick@verizon.com
Cc: ccielab@groupstudy.com
Subject: RE: OSPF summar-address into IGRP
Ooooooooh, clever. So by redistributing connected into OSPF, the connected
route appears as external, which is then subject to the summary-address
command. Nice. I'll have to play with this in my lab.
One question -- does this still work if the connected network is also
included as part of an OSPF area (via the "network" command)?
At 11:02 AM 4/30/2001 -0400, Wayne Gustavus wrote:
>I think you will find that the easiest, most consistent way to do this
>(given most of the requirements listed so far) is to redistribute connected
>into your OSPF process. The summary-address configured under the ospf
>process will then correctly summarize to the /24 address which gets passed
>to IGRP b/c you are redistributing OSPF to IGRP. This is all configured on
>the ASBR and it works. Of course, normal tips for redistribution apply:
>don't forget subnets parameter and probably want a route-map to control
>which connected routes get injected.
>
>HTH,
>
>
This archive was generated by hypermail 2.1.4 : Thu Jun 13 2002 - 10:30:02 GMT-3