[c-nsp] Routing based on traffic type question

[Scott Granados]

Hi, thanks, I thought that was heading in the right direction.

So I found this example here...
http://www.cisco.com/en/US/docs/ios/12_2/qos/configuration/guide/qcfpbr_ps1835_TSD_Products_Configuration_Guide_Chapter.html

In this example, they use only simple access lists matching an individual IP address and setting some bits.  Instead of a simple IP acl can I use something more complex where it say matches on a type of service bit or given port and acts else forwards normally or is a full IP at /32 length as granular as I can get?  The example they provide seems simple but not sure what will happen if I define my acl more granular.  Will any accept ACL expressions work or what’s my limiter the doc is a little confusing.

Thanks and thanks for the pointer, I really appreciate it.

Scott



From: Chuck Church 
Sent: Wednesday, July 13, 2011 11:21 AM
To: Scott Granados 
Cc: cisco-nsp at puck.nether.net 
Subject: Re: [c-nsp] Routing based on traffic type question

Scott, 

     Yes, policy routing will work, using it to off-load http and other non time sensitive traffic for a customer.  Using static object tracking to avoid black-holing towards a dead next hop.  

Chuck

On Jul 13, 2011 10:54 AM, "Scott Granados" <scott at granados-llc.net> wrote:
> Hi,
> 
> This is a new one for me and wanted to get some pointers / possible config examples.
> 
> We have a branch office that is presently being fed back to a pop via single T1 which is about as vanilla as can be expected. It’s a simple connected /30 with a few /29 blocks routed for the inside interfaces. On my end is a Cisco 7206VXR with a channelized DS3 which receives the circuit and I have full access to this device to make changes as needed.
> The branch office is being upgraded to a wireless connection which will attach to a different segment on the same router and we will be migrating their routed blocks to the new connection as you’d expect using entirely static routing. 
> The issue is we’d like to leave the T1 in place and simply use that for VOIP traffic while leaving the rest of the traffic to traverse the wireless link. 
> 
> How would I split the two effectively? I have definite destinations for all their VOIP traffic which are also on my network so there are specific soft switches that the branch uses. Is this a case for policy based routing? Does anyone have anything like this in place that they could provide some snippets to give me a starting point. Any pointers would be appreciated. Is this even possible?
> 
> Thank you
> 
> Scott
> _______________________________________________
> cisco-nsp mailing list cisco-nsp at puck.nether.net
> https://puck.nether.net/mailman/listinfo/cisco-nsp
> archive at http://puck.nether.net/pipermail/cisco-nsp/