Job Search, Job Listing, Opportunity
Work at home job, job vacancy
find a job, vacancy list, cari lowongan
Butuh, Segera, secretary, director

OSPF intra area filtering


Piotr, that he does not wants to do (he needs to do it on more routers). I have also misread the post the first time.
Ok, Sergei, here are the options in my opinion:
1. Redistribute connected, effectively making router an ASBR. Then use “summary-address not-advertise” option i.e.* router ospf 1 redistribute connected subnets summary-address 1.1.1.0 255.255.255.0 not-advertise *
2. Redistribute connected using E1 metric, set the metric to nearly maximum value. i.e. (out of my head, not for copy-pasting of course)
route-map TRICK match interface lo0 set type E1 set metric to about maximum -5
router ospf 1 redistribute connected subnets

On Wed, Jan 7, 2009 at 12:21 AM, Piotr wrote:
> My bad. I misread your email. > > You an redistribute the loopback on R1. > Then use a distribute-list out. > > int lo0 > ip address 1.1.1.1 255.255.255.0 > > access-list 1 deny 1.1.1.0 > access-list per any > > route-map REDIST_LO0 per 10 > match inter lo0 > > router ospf 1 > redistribute connected subnets route-map REDIST_LO0 > distribute-list 1 out > > > On Tue, Jan 6, 2009 at 6:16 PM, Piotr wrote: > > > Try this > > > > On R2 > > > > ip prefix-list FILTERLSA3 seq 5 deny 111.111.111.0/24 > > ip prefix-list FILTERLSA3 seq 10 permit 0.0.0.0/0 le 32 > > router ospf 1 > > area 1 range filter-list FILTERLSA3 in > > > > > > On Tue, Jan 6, 2009 at 7:34 AM, Sergei Udovenko >wrote: > > > >> Hello to all CCIE candidates! > >> I’ve the following topology: > >> > >> lo:1.1.1.x->R1—R2—-R3 > >> > >> R1 - area 1 > >> R2 - ABR > >> R3 - area 0 > >> > >> The issue that I want that 1.1.1.x will not be advertised to the R2(ABR) > >> and > >> all other routers int area 0. So the problem here is that I want to find > >> workaround to filter route in intra- area and not on ABR with area 1 > range > >> 1.1.1.0 255.255.255.0 not-advertise command. Also because there are > about > >> 20 > >> routers in area 0 that shouldn’t receive 1.1.1.x and I don’t want to > >> use distribute-list > >> x in on each router in area 0 to filter the local routing table on each > >> router. > >> > >> > >> May be some of you have any suggestion how to get this workaround? > >> > >> ——————– > >> Best regards, > >> Sergei > >> > >> > >> 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 > > > > > > > >
— Pavel Bykov —————- Don’t forget to help stopping the braindumps, use of which reduces value of your certifications. Sign the petition at http://www.stopbraindumps.com/
Blogs and organic groups at http://www.ccie.net

Bookmark this post:These icons link to social bookmarking sites where readers can share and discover new web pages.
  • blinkbits
  • BlinkList
  • blogmarks
  • co.mments
  • connotea
  • del.icio.us
  • De.lirio.us
  • digg
  • Fark
  • feedmelinks
  • Furl
  • LinkaGoGo
  • Ma.gnolia
  • NewsVine
  • Netvouz
  • RawSugar
  • Reddit
  • scuttle
  • Shadows
  • Simpy
  • Smarking
  • Spurl
  • TailRank
  • Wists
  • YahooMyWeb
keywords found: subnets organic metric routing petition issue using 

Leave a Comment

Related Post