Have you tried...
route-map ospf-to-bgp deny 10 match ipv6 address prefix-list deny-list route-map ospf-to-bgp permit 20 ipv6 prefix-list deny-list seq 5 permit 2222:9:9:1000::9/128 ? On Dec 1, 2010, at 2:38 PM, Tyson Scott wrote: > You can definitely filter with deny statements when redistributing with a > route-map. Either a deny in the prefix-list or access-list or a deny > sequence in the route-map. > > Regards, > > Tyson Scott - CCIE #13513 R&S, Security, and SP > Managing Partner / Sr. Instructor - IPexpert, Inc. > Mailto: [email protected] > Telephone: +1.810.326.1444, ext. 208 > Live Assistance, Please visit: www.ipexpert.com/chat > eFax: +1.810.454.0130 > > IPexpert is a premier provider of Self-Study Workbooks, Video on Demand, > Audio Tools, Online Hardware Rental and Classroom Training for the Cisco CCIE > (R&S, Voice, Security & Service Provider) certification(s) with training > locations throughout the United States, Europe, South Asia and Australia. Be > sure to visit our online communities at www.ipexpert.com/communities and our > public website at www.ipexpert.com > > From: Baldwin, Patrick A. [mailto:[email protected]] > Sent: Wednesday, December 01, 2010 12:55 AM > To: Tyson Scott > Subject: FW: [OSL | CCIE_RS] Vol 1 LAB 34 route-map calling a prefix list > question > > Is this correct? I thought you could use route-maps to filter routes during > redistribution. I think I can find some examples of that. > > Thanks > > Patrick A. Baldwin (Alex) > Network Engineering > Colsa Corp., HOSC Contract > NASA , Marshall Space Flight Center > (Office: (256) 544-2089 > ÊFax: (256) 544-8629 > *E-mail: [email protected] > > From: Rogelio Gamino [mailto:[email protected]] > Sent: Tuesday, November 30, 2010 8:09 PM > To: Baldwin, Patrick A. > Subject: Re: [OSL | CCIE_RS] Vol 1 LAB 34 route-map calling a prefix list > question > > Yeah, you're right. I thought you were setting an attribute to the prefix to > make the route invalid. > > I believe the only options you have are using a prefix-list or a > distribute-list. > > A route-map may work if you can set an attribute to the prefix to make it > invalid (ie change the AD to 255? I don't know if you can do that or set the > next-hop to something not reachable by the peer receiving the route?). If you > find a way to do this you're not filtering the route but the neighbor would > not put the route in the routing table. Not sure if that would meet the > requirement. > > I don't think route-maps are meant for route filtering. > > > > On Tue, Nov 30, 2010 at 7:45 PM, Baldwin, Patrick A. <[email protected]> > wrote: > ok, but if I permit it in the prefix list that is called in a permit > statement in the route-map that would distribute it right? I am trying to > exclude just that one? > > Patrick A. Baldwin (Alex) > Network Engineering > Colsa Corp., HOSC Contract > NASA , Marshall Space Flight Center > (Office: (256) 544-2089 > ÊFax: (256) 544-8629 > *E-mail: [email protected] > > From: Rogelio Gamino [mailto:[email protected]] > Sent: Tuesday, November 30, 2010 6:40 PM > > To: Baldwin, Patrick A. > Cc: [email protected] > Subject: Re: [OSL | CCIE_RS] Vol 1 LAB 34 route-map calling a prefix list > question > > Try ipv6 prefix-list deny-list seq 5 permit 2222:9:9:1000::9/128 > > > > Sent from my iPhone > > On Nov 30, 2010, at 6:21 PM, "Baldwin, Patrick A." <[email protected]> > wrote: > > ipv6 prefix-list deny-list seq 5 deny 2222:9:9:1000::9/128 > > _______________________________________________ > For more information regarding industry leading CCIE Lab training, please > visit www.ipexpert.com
_______________________________________________ For more information regarding industry leading CCIE Lab training, please visit www.ipexpert.com
