[nsp] Not using "redist sta sub" in OSPF

[Matt Ryan]

I don't see the logic of using "network" statements over redistributing
statics. If I have a customer connected on a leased line (numbered with a
/30 or /31 subnet) and they have a /24 on the back of their CPE router how
am I supposed to announce the route back into my IGP? Speak a routing
protocol with the CPE device (which I'd say is much more dangerous than
using statics)? Using a route-map as Ryan suggests would seem the pragmatic
solution to avoid any screw-ups by adding an incorrect static.


Matt.

-----Original Message-----
From: Ryan O'Connell [mailto:ryan@complicity.co.uk]
Sent: 09 August 2002 10:49
To: Mark Drayton; cisco-nsp@puck.nether.net
Subject: Re: [nsp] Not using "redist sta sub" in OSPF


On Fri, 9 Aug 2002 10:30:47 +0100 Mark Drayton
<mark.drayton@izrsolutions.com> wrote:
> I have a few static routes pointing at frame relay subifs that I'd like
> to get into OSPF, without using "redist sta sub" as that redistributes
> all the static routes I have.
[snip]
> I tried using "network 192.168.20.0 0.0.0.255 area 0" but that doesn't
> work (not a surprise after consulting documentation). Is there a better
> way to do this?

Use a route-map on the redistribute command, like this:

router ospf 100
  redistribute static 1 subnets route-map static-to-ospf

route-map static-to-ospf permit 10
  match ip address 1

access-list 1 permit host 192.168.20.0

--
         Ryan O'Connell - CCIE #8174
<ryan@complicity.co.uk> - http://www.complicity.co.uk

I'm not losing my mind, no I'm not changing my lines,
I'm just learning new things with the passage of time

_______________________________________________
cisco-nsp mailing list  real_name)s@puck.nether.net
http://puck.nether.net/mailman/listinfo/cisco-nsp
archive at http://puck.nether.net/pipermail/cisco-nsp/

------------------------------------------------------------------------------
Live Life in Broadband
www.telewest.co.uk


The information transmitted is intended only for the person or entity to which it is addressed and may contain confidential and/or privileged material.
Statements and opinions expressed in this e-mail may not represent those of the company. Any review, retransmission, dissemination or other use of, or taking of any action in reliance upon, this information by persons or entities other than the intended recipient is prohibited. If you received this in error, please contact the sender immediately and delete the material from any computer.


==============================================================================