RE: Filtering OSPF LSA type 3

From: Peter van Oene (pvo@usermail.com)
Date: Thu Oct 17 2002 - 10:28:25 GMT-3


At 02:41 AM 10/17/2002 -0400, you wrote:
>My understanding is that ALL routers in the same area MUST have the same
>"picture" of their common area, hence in all my examinations of the LSA
>database they all have the same Type 1 and 2 database.
>I remember someone mentioned that this is part of the RFC??
>Correct me if I'm wrong, it's getting late. Good night and happy
>studying y'all.

All routers in the same area must maintain identical Link State Databases
for the area. This includes all LSA's, not just type 1/2 etc. The RFC in
question is 2328 and is likely worth a read.

>Elmer
>
>-----Original Message-----
>From: nobody@groupstudy.com [mailto:nobody@groupstudy.com] On Behalf Of
>aansar@sscomp.com.sg
>Sent: Wednesday, October 16, 2002 11:28 PM
>To: Donny MATEO
>Cc: ccielab@groupstudy.com; nobody@groupstudy.com
>Subject: RE: Filtering OSPF LSA type 3
>
>i think coz type 1 and type2 LSA are within the area .. filtering doesnt
>make sense ( i think so.. i am not sure)
>but type 3 generated by ABR forwarded to another areas , so if you use
>ip
>ospf database filter all out in ABR interface going towards another area
>,
>in turn your filtering only LSA3
>
>there is filtering for E2/E1 using distribute-list <xxx> out <routing
>process> <routing process no>
>eg: distribute-list 1 out eigrp 1
>
>
>
>
>
>
> "Donny MATEO"
>
> <donny.mateo@sg.ca-ind To:
>aansar@sscomp.com.sg
> osuez.com> cc:
>ccielab@groupstudy.com
> Sent by: Subject: RE:
>Filtering OSPF LSA type 3
> nobody@groupstudy.com
>
>
>
>
>
> 17-10-02 11:10 AM
>
> Please respond to
>
> "Donny MATEO"
>
>
>
>
>
>
>
>
>
>Ok I knew this one.
>Was getting an impression that there is a filter list for only type 3
>LSA.
>
>Am I correct to assume that
>1. ip ospf database filter all out => will filter all LSA advertisement
>from this router and
>2. neigh x.x.x.x database filter all out => will filter all LSA
>advertisement to this neighbor ?
>
>meaning you still can't specify which LSA type. If you're only asked to
>filter LSA type 3
>advertisement both wouldn't be applicable ?
>
>tks
>Donny
>
>
>
> aansar@sscomp.com
>
> .sg To: "Donny MATEO"
><donny.mateo@sg.ca-indosuez.com>
> cc:
>ccielab@groupstudy.com, nobody@groupstudy.com
>
> 17-10-2002 10:43 Subject: RE: Filtering
>OSPF
>LSA type 3
>
>
>
>
>
>
>
>there is two commands
>1. ip ospf database filter all out (it is interface command)
>2. neighbor <x.x.x.x> database filter all out (remember this command
>requires the interface which connecting the neighbor to be multipoint
><ospf multi point interface>
>it is there in 12.1
>
>
>
>
> "Donny MATEO"
> <donny.mateo@sg.ca-ind To:
>ccielab@groupstudy.com
> osuez.com> cc:
> Sent by: Subject: RE:
>Filtering OSPF LSA type 3
> nobody@groupstudy.com
>
>
> 17-10-02 10:37 AM
> Please respond to
> "Donny MATEO"
>
>
>
>
>
>
>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/ios122/122newf
>t/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 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