Re: Filtering OSPF LSA type 3

From: Nick Shah (nshah@connect.com.au)
Date: Thu Oct 17 2002 - 01:31:13 GMT-3


Nathan

Filtering in NSSA happens at 2 places, on the NSSA ABR or ASBR.

If the NSSA ABR is also an ASBR, then you can control that the type-5;'s are
not injected into NSSA as type-7's. So you use

area x nssa no-redistribution.

On the NSSA ASBR or ABR, you can control which type-7's are not leaked outof
NSSA, u use

summary-address x not-advertise

rgds
Nick
----- Original Message -----
From: "Nathan Chessin" <nchessin@cisco.com>
To: "'Nick Shah'" <nshah@connect.com.au>; "'Donny MATEO'"
<donny.mateo@sg.ca-indosuez.com>; <ccielab@groupstudy.com>
Sent: Thursday, October 17, 2002 2:07 PM
Subject: RE: Filtering OSPF LSA type 3

> you can use this command on the ABR or ASBR to not allow type 7 LSA to be
> translated to type 5 LSA, but does this command work with normal areas? I
> *believe* this is only for NSSA areas. Any verification?
>
>
> Nate
>
>
> > -----Original Message-----
> > From: nobody@groupstudy.com [mailto:nobody@groupstudy.com]On Behalf Of
> > Nick Shah
> > Sent: Wednesday, October 16, 2002 8:28 PM
> > To: Donny MATEO; ccielab@groupstudy.com
> > Subject: Re: Filtering OSPF LSA type 3
> >
> >
> > Try using area-range xxx NOT-ADVERTISE option. I guess its available
> > starting 12.1.
> >
> > IP ospf database filter, filters out 'all' LSA's.
> >
> > Thanks
> > Nick
> > ----- Original Message -----
> > From: "Donny MATEO" <donny.mateo@sg.ca-indosuez.com>
> > To: <ccielab@groupstudy.com>
> > Sent: Thursday, October 17, 2002 12:37 PM
> > Subject: RE: Filtering OSPF LSA type 3
> >
> >
> > > can't find this ospf filter-list command on 12.1(13).
> > > Can you tell me where this command is or does it require higher IOS
> > version ?
> > >
> > > Donny
> > >
> > >
> > >
> > > Senthil Kumar
> > > <senthil.kumar@intechno To:
> > Peter van
> > Oene <pvo@usermail.com>, Senthil Kumar
> > > logy.co.uk>
> > <senthil.kumar@intechnology.co.uk>, Dimitris Vassilopoulos
> > > Sent by:
> > <Dimitris.Vassilopoulos@eurodyn.com>, ccielab@groupstudy.com
> > > nobody@groupstudy.com cc:
> > > Subject: RE:
> > Filtering OSPF LSA type 3
> > >
> > > 16-10-2002 21:12
> > > Please respond to
> > > Senthil Kumar
> >
> > >
> > >
> > >
> > >
> > >
> > >
> > > you can filter lsa's with ospf filter-list
> > >
> > > -----Original Message-----
> > > From: Peter van Oene [mailto:pvo@usermail.com]
> > > Sent: 16 October 2002 14:06
> > > To: Senthil Kumar; Dimitris Vassilopoulos; ccielab@groupstudy.com
> > > Subject: RE: Filtering OSPF LSA type 3
> > >
> > >
> > > Keep in mind that you can't filter LSAs. You can filter routing
> > > information as it moves from the LSDB to the local routing
> > table, but not
> > > the reception and publication of the LSAs to the LSDB.
> > Filtering LSA
> > > reception would directly violate the specifications and
> > likely lead to
> > > routing instability as SPF is only effective when everyone
> > looks at the
> > > same topology.
> > >
> > > At 01:58 PM 10/16/2002 +0100, Senthil Kumar wrote:
> > > >true, but what if you want to filter some lsa-3
> > only..distribute list
> > might
> > > >help when introduced on inbound routes at all peers.wont it?
> > > >
> > > >-----Original Message-----
> > > >From: Peter van Oene [mailto:pvo@usermail.com]
> > > >Sent: 16 October 2002 13:36
> > > >To: Dimitris Vassilopoulos; ccielab@groupstudy.com
> > > >Subject: Re: Filtering OSPF LSA type 3
> > > >
> > > >
> > > >All you can do here is use the totally stubby knob on the
> > ABR(s). Once
> > the
> > > >LSA is in the area, it is mandatory that all area resident routers
> > receive
> > > >the LSA and correctly process it. Distribute-list in
> > simply prevents any
> > > >relevant reachability information from making it to the
> > local routing
> > > >table, but has no effect on LSA's.
> > > >
> > > >At 01:35 PM 10/16/2002 +0300, Dimitris Vassilopoulos wrote:
> > > > >Team,
> > > > >
> > > > >Cisco says in
> > > >
> > >
> > >http://www.cisco.com/univercd/cc/td/doc/product/software/ios1
> > 22/122newft/12
> > > >2t/122t4/ftabrt3f.htm
> > > > >
> > > > >that if you want to filter OSPF type 3 LSA you have to
> > run 12.2(4)T.
> > > > >I know that the image running in the lab is 12.1.x
> > > > >
> > > > >What if we're asked to filter inbound type 3 LSAs from a
> > BB router?
> > > > >We must use " distribute-list x in " in EVERY ospf router ?
> > > > >
> > > > >Any comment on that would be appreciated...
> > > > >
> > > > >Dimitris
> > > >
> > >
> > >_____________________________________________________________
> > ___________
> > > >This message has been checked for all known viruses by the
> > > >CitC Virus Scanning Service powered by SkyLabs. For
> > further information
> > > >visit
> > > >http://www.citc.it
> > > >
> > > >___
> > > >
> > >
> > >_____________________________________________________________________
> > > >This message has been checked for all known viruses by the
> > > >CitC Virus Scanning Service powered by SkyLabs. For
> > further information
> > > visit
> > > >http://www.citc.it
> > >
> > >
> > >
> > >
> > ______________________________________________________________
> > __________
> > > This message has been checked for all known viruses by the
> > > CitC Virus Scanning Service powered by SkyLabs. For further
> > information
> > > visit
> > > http://www.citc.it
> > >
> > > ___
> > >
> > >
> > _____________________________________________________________________
> > > This message has been checked for all known viruses by the
> > > CitC Virus Scanning Service powered by SkyLabs. For further
> > information
> > visit
> > > http://www.citc.it
> > >
> > >
> > >
> > >
> > >
> > > This message is for information purposes only and its content
> > > should not be construed as an offer, or solicitation of an offer,
> > > to buy or sell any banking or financial instruments or services
> > > and no representation or warranty is given in respect of its
> > > accuracy, completeness or fairness. The material is subject
> > > to change without notice. You should take your own independent
> > > tax, legal and other professional advice in respect of the content
> > > of this message. This message may contain confidential or
> > > legally privileged material and may not be copied, redistributed
> > > or published (in whole or in part) without our prior
> > written consent.
> > > This email may have been intercepted, partially destroyed,
> > > arrive late, incomplete or contain viruses and no liability is
> > > accepted by any member of the Credit Agricole Indosuez group
> > > as a result. If you are not the intended recipient of this message,
> > > please immediately notify the sender and delete this message
> > > from your computer.



This archive was generated by hypermail 2.1.4 : Tue Nov 05 2002 - 08:35:49 GMT-3