10 messages in net.nether.puck.cisco-nsp[c-nsp] Hardware accel. paths for pol...
FromSent OnAttachments
Sam SticklandJan 24, 2005 12:27 pm 
lis...@hojmark.orgJan 24, 2005 7:13 pm 
Per CarlsonJan 25, 2005 2:27 am 
Sam SticklandFeb 15, 2005 9:39 am 
Tim StevensonFeb 15, 2005 11:36 am 
Sam SticklandFeb 15, 2005 11:51 am 
Tim StevensonFeb 15, 2005 12:11 pm 
Arie VaynerFeb 16, 2005 4:13 pm 
Tim StevensonFeb 16, 2005 5:13 pm 
Tim StevensonFeb 16, 2005 5:20 pm 
Actions with this message:
Paste this link in email or IM:
Paste this link in email or IM:
Atom feed for this thread
Paste this URL into your reader:
Subject:[c-nsp] Hardware accel. paths for policy routing on C6500Actions...
From:lis...@hojmark.org (lis@hojmark.org)
Date:Jan 24, 2005 7:13:45 pm
List:net.nether.puck.cisco-nsp

Would the following route-map used for policy routing be hardware accelerated on a SUP2/MFSC2/PFC2 combo?

route-map ROUTE_PARTIAL permit 10 match ip address match_partial set ip next-hop 1.2.3.4

ip access-list extended ACL_MATCH_PARTIAL permit ip any any dscp af21

Yes, both 'match ip address' and 'set ip next-hop' are handled in hardware on the Sup222.

If the route-map is:

route-map ROUTE_PARTIAL permit 10 match ip address match_partial set ip next-hop 1.2.3.4 5.6.7.8

Then the router will try 1.2.3.4 if it's reachable, and if it's not it will go on to try 5.6.7.8 ?

That's the idea. There was a DDTS, however, where the second choice wasn't programmed in hardware, but was instead handled in software, I think. I don't have the DDTS number handy, and am not totally sure about the details. You may want to look this up.

-A