Policy Based Routing on a Cisco Switch

While policy based routing is available on a great many Cisco switches, you will need the right firmware that supports it.  For my home lab, a 3560X is my main switch, it requires 15.1-15.3 to work, currently 15.2 has MD releases, which is what I used.  A quick show sdm prefer will output the features you have available, ensure ip routing is enabled as well.

Lastly, as far as creating an access list for policy based routing, ensure you deny your internal networks in the ACL prior to implementation or a lot of things won't work.

access-list 100 deny   ip 192.168.1.0 0.0.0.255 192.168.0.0 0.0.255.255
access-list 100 permit ip 192.168.1.0 0.0.0.255 any

 This ACL will allow you to policy route all traffic that is external to a next hop.

Enjoy!

Comments

Post a Comment

Popular posts from this blog

Policy Based Routing on a Nexus

First of all, let's just admit, I am a collab guy, doing work on a Nexus is a foreign experience. While some things are intuitive not everything follows RFC's and the Nexus platform is a bit more restrictive. First of all, to get PBR going, I had to change the hardware profile, since I have no intention of using QoS internally in my lab, I decided to steal from it: hardware profile tcam region qos 0 hardware profile tcam region pbr 256 This then requires a reboot.  After this is done and the pbr feature is enabled: feature pbr You can get into creating the route-maps.  However, unlike IOS devices you can only use permits in your acl's and then use a deny statement on the route map itself: ip access-list PBR_DENY statistics per-entry 10 permit ip any 192.168.1.0/24 ip access-list PBR_PERMIT  statistics per-entry  10 permit ip any any route-map PBR_RULE pbr-statistics route-map PBR_RULE deny 10  match ip address PBR_DENY route-map PBR_R...
Read more

Cloudflare Calls API to SIP broker

Update: Given the amount of time I sacrifice to game development outside of collaboration work, my site has become defunct. Cloudflare has a calls beta. My intention is to create a SIP to API broker for the CMS and try to get their CDN working with it's anycast to beat out GeoDNS solutions. I will probably post more about this later here, however, don't expect me to be overly timely on it. Also, why is the Cisco Meeting Server doesn't grey out UI items that have been configured in the API so people don't make mistakes and cause conflicts? Why is it that Cisco doesn't publish the methodology by which all cospaces are assigned to callbridges/nodes at the time of build. I have many questions for many things that don't make sense these days and a lot of rants, but I will save those for some knowledge drops in the future. Take care everyone!
Read more