<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: Advanced Loadbalancing Decisions in Application Networking</title>
    <link>https://community.cisco.com/t5/application-networking/advanced-loadbalancing-decisions/m-p/1067471#M21576</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;As per the ACE policy order Server Loadbalancing will happen first and then Inspection will take place.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Something like this should do&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;class-map type http inspect match-any BLOCK-HTTP&lt;/P&gt;&lt;P&gt;            match request-method rfc post&lt;/P&gt;&lt;P&gt;            match url &lt;REG ex=""&gt;&lt;/REG&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;class match-all ALLOW-HTTP&lt;/P&gt;&lt;P&gt;  match port tcp eq http&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;policy-map type inspect HTTP first-match PM-L7-Inspect-webserver&lt;/P&gt;&lt;P&gt;           class BLOCK-HTTP&lt;/P&gt;&lt;P&gt;               reset&lt;/P&gt;&lt;P&gt;           class ALLOW-HTTP&lt;/P&gt;&lt;P&gt;               permit&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;       &lt;/P&gt;&lt;P&gt;policy-map multi-match PM-BasicVIPs&lt;/P&gt;&lt;P&gt;class CM-webserver&lt;/P&gt;&lt;P&gt;loadbalance vip inservice&lt;/P&gt;&lt;P&gt;loadbalance policy PM-L7-webserver&lt;/P&gt;&lt;P&gt;loadbalance vip icmp-reply&lt;/P&gt;&lt;P&gt;inspect http policy PM-L7-Inspect-webserver&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Try it in a test environment first.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Syed&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Fri, 26 Sep 2008 22:55:08 GMT</pubDate>
    <dc:creator>Syed Iftekhar Ahmed</dc:creator>
    <dc:date>2008-09-26T22:55:08Z</dc:date>
    <item>
      <title>Advanced Loadbalancing Decisions</title>
      <link>https://community.cisco.com/t5/application-networking/advanced-loadbalancing-decisions/m-p/1067468#M21573</link>
      <description>&lt;P&gt;I have some requirements from my app developers that are puzzling me.  I'm not sure the ACE can do what I want, but with the flexibility of the policy and class maps I'm thinking there has to be a way.  &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I have a VIP that is used for two different server farms.  If a user goes to the general URI &lt;A class="jive-link-custom" href="http://mainwebserver.com" target="_blank"&gt;http://mainwebserver.com&lt;/A&gt; they go to the main web serverfarm.  However, if they go to &lt;A class="jive-link-custom" href="http://mainwebserver.com/internal" target="_blank"&gt;http://mainwebserver.com/internal&lt;/A&gt; they will go to a different serverfarm.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I have this set up and working right now.  Easy.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;However, my application guys want to use the ACE enforce certain policies with regard to request METHODs and actions.  &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Example, if the user is doing a POST and they go to the mainwebserver.com URL with /internal/ and then /makechange in the URL, then they have to be using SSL.  In other words, if they go to &lt;A class="jive-link-custom" href="http://mainwebserver.com/internal/stuff/blah/makechange" target="_blank"&gt;http://mainwebserver.com/internal/stuff/blah/makechange&lt;/A&gt; with the POST method and are coming via HTTP (as opposed to HTTPS), then I need to reject the call.  If they aren't POSTing, or aren't going to /makechange, then it doesn't matter if they are using HTTP or HTTPS.  &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Can anyone come up with a way to accomplish this task?  &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Oh yeah, it's also not only /makechange, but also /getchanges combined with a POST method, that would require SSL.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Let me know if anyone needs further clarification.  It looks like a fun puzzle, so have it.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks!&lt;/P&gt;</description>
      <pubDate>Fri, 26 Sep 2008 17:08:52 GMT</pubDate>
      <guid>https://community.cisco.com/t5/application-networking/advanced-loadbalancing-decisions/m-p/1067468#M21573</guid>
      <dc:creator>lou_young</dc:creator>
      <dc:date>2008-09-26T17:08:52Z</dc:date>
    </item>
    <item>
      <title>Re: Advanced Loadbalancing Decisions</title>
      <link>https://community.cisco.com/t5/application-networking/advanced-loadbalancing-decisions/m-p/1067469#M21574</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;With HTTP Inspection you can look for HTTP methods and Request urls and can reset the client conns if there is a match.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Something in lines with&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;class-map type http inspect match-all  xyz&lt;/P&gt;&lt;P&gt;match request-method  rfc post&lt;/P&gt;&lt;P&gt;match url &lt;REGULAR expression=""&gt;&lt;/REGULAR&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;policy-map type inspect http all-match  HTTP_INSPECT_L7POLICY&lt;/P&gt;&lt;P&gt;class xyz&lt;/P&gt;&lt;P&gt;reset&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Syed&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 26 Sep 2008 17:53:07 GMT</pubDate>
      <guid>https://community.cisco.com/t5/application-networking/advanced-loadbalancing-decisions/m-p/1067469#M21574</guid>
      <dc:creator>Syed Iftekhar Ahmed</dc:creator>
      <dc:date>2008-09-26T17:53:07Z</dc:date>
    </item>
    <item>
      <title>Re: Advanced Loadbalancing Decisions</title>
      <link>https://community.cisco.com/t5/application-networking/advanced-loadbalancing-decisions/m-p/1067470#M21575</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I was thinking that the way to go would be with an INSPECT policy.  But I wasn't sure how to implement it.  Assuming I have a service policy of:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;policy-map multi-match PM-BasicVIPs&lt;/P&gt;&lt;P&gt;  class CM-webserver&lt;/P&gt;&lt;P&gt;    loadbalance vip inservice&lt;/P&gt;&lt;P&gt;    loadbalance policy PM-L7-webserver&lt;/P&gt;&lt;P&gt;    loadbalance vip icmp-reply&lt;/P&gt;&lt;P&gt;    inspect http policy PM-L7-Inspect-webserver&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Would the policy action on the inspect portion and reset the connection or will it action on the loadbalance portion and service the request?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Also, the policy PM-L7-webserver is the one analyzing the URI and pushing the user to one of two serverfarms.  I don't think that'll matter since the inspect class is doing the same check in the URI.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thoughts?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 26 Sep 2008 18:58:48 GMT</pubDate>
      <guid>https://community.cisco.com/t5/application-networking/advanced-loadbalancing-decisions/m-p/1067470#M21575</guid>
      <dc:creator>lou_young</dc:creator>
      <dc:date>2008-09-26T18:58:48Z</dc:date>
    </item>
    <item>
      <title>Re: Advanced Loadbalancing Decisions</title>
      <link>https://community.cisco.com/t5/application-networking/advanced-loadbalancing-decisions/m-p/1067471#M21576</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;As per the ACE policy order Server Loadbalancing will happen first and then Inspection will take place.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Something like this should do&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;class-map type http inspect match-any BLOCK-HTTP&lt;/P&gt;&lt;P&gt;            match request-method rfc post&lt;/P&gt;&lt;P&gt;            match url &lt;REG ex=""&gt;&lt;/REG&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;class match-all ALLOW-HTTP&lt;/P&gt;&lt;P&gt;  match port tcp eq http&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;policy-map type inspect HTTP first-match PM-L7-Inspect-webserver&lt;/P&gt;&lt;P&gt;           class BLOCK-HTTP&lt;/P&gt;&lt;P&gt;               reset&lt;/P&gt;&lt;P&gt;           class ALLOW-HTTP&lt;/P&gt;&lt;P&gt;               permit&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;       &lt;/P&gt;&lt;P&gt;policy-map multi-match PM-BasicVIPs&lt;/P&gt;&lt;P&gt;class CM-webserver&lt;/P&gt;&lt;P&gt;loadbalance vip inservice&lt;/P&gt;&lt;P&gt;loadbalance policy PM-L7-webserver&lt;/P&gt;&lt;P&gt;loadbalance vip icmp-reply&lt;/P&gt;&lt;P&gt;inspect http policy PM-L7-Inspect-webserver&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Try it in a test environment first.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Syed&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 26 Sep 2008 22:55:08 GMT</pubDate>
      <guid>https://community.cisco.com/t5/application-networking/advanced-loadbalancing-decisions/m-p/1067471#M21576</guid>
      <dc:creator>Syed Iftekhar Ahmed</dc:creator>
      <dc:date>2008-09-26T22:55:08Z</dc:date>
    </item>
    <item>
      <title>Re: Advanced Loadbalancing Decisions</title>
      <link>https://community.cisco.com/t5/application-networking/advanced-loadbalancing-decisions/m-p/1067472#M21577</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I implemented this last Friday afternoon, and while it took some tweaking on the RegEx to get the URL match correct, it seems to be working to reset the connections for the various scenario's the app guys are throwing at me.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks for your help!&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 29 Sep 2008 19:40:24 GMT</pubDate>
      <guid>https://community.cisco.com/t5/application-networking/advanced-loadbalancing-decisions/m-p/1067472#M21577</guid>
      <dc:creator>lou_young</dc:creator>
      <dc:date>2008-09-29T19:40:24Z</dc:date>
    </item>
  </channel>
</rss>

