<?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: Basic ACE questions in Application Networking</title>
    <link>https://community.cisco.com/t5/application-networking/basic-ace-questions/m-p/954323#M18751</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;1) Ethernet Interface config (duplex, speed, ....), Trunking ,Portchannel and FT config is done in Admin context. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;You assign vlans from Admin contexts to non-Admin contexts using "allocate-interface vlan" command in Admin Context. Then you create   vlan interfaces in user (Or even in Admin context if needed) contexts. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;2. Default-class is only used when all classes fail to match.In situations where there is no need to match any advance characteristics of the traffic, this is the only class that is used under a policy map. One such example is Layer 4 policy.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;3. There are different tpe of class-maps and policy-maps on ACE. For a typical Layer 4 LB rule You need following&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;a. Class-map &lt;/P&gt;&lt;P&gt;To match traffic against Virtual address -- VIP)&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;b. Multi-match policy &lt;/P&gt;&lt;P&gt;It will create kind of "if-then-else" logic for different "Virtual address matching" class-maps.This policy matches the vip and then call the "loadbalance policy" for interesting traffic ( which selects appropriate server farm).&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;c. Load balance policy &lt;/P&gt;&lt;P&gt;It will match a different set of class maps and will select Serverfarm based on the matching criteris (default-class is used here as last resort class).&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;If you need to match Layer 7 stuff (url, cookies, haeaders...) then you need to create class-maps to map these conditions and these class-maps will be used in "Load balance policy-maps"&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;4. Source NAT doesnt happen automatically in most LB devices (same is the case here). Normally destination NAt (VIP -&amp;gt; Real Server)  happens by default on all LB devices (Same is the case here). &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;HTH&lt;/P&gt;&lt;P&gt;Syed Iftekhar Ahmed&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Mon, 14 Jul 2008 02:28:07 GMT</pubDate>
    <dc:creator>Syed Iftekhar Ahmed</dc:creator>
    <dc:date>2008-07-14T02:28:07Z</dc:date>
    <item>
      <title>Basic ACE questions</title>
      <link>https://community.cisco.com/t5/application-networking/basic-ace-questions/m-p/954322#M18750</link>
      <description>&lt;P&gt;I'm about to do my first ACE install. I'm familiar with the CSS but am having difficulty getting my arms around some ACE concepts. Your assistance is appreciated.&lt;/P&gt;&lt;P&gt;1) When using mutiple contexts, does the L2 configs such as trunking, channel groups, etc go into the "admin" context or do they go in the individual contexts? Is that true with the VLAN interfaces also?&lt;/P&gt;&lt;P&gt;2) I'm looking at the ACE quick config guide and have a questions with the example they show (see below). In particular, their use of the "default-class" and how it is listed first in the first-match policy map...&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;class-map match-all L4_VIP_ADDRESS_CLASS&lt;/P&gt;&lt;P&gt;  10 match virtual-address 172.16.110.9 any&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;policy-map type loadbalance first-match L7_VIP_LB_ORDER_POLICY&lt;/P&gt;&lt;P&gt;  class CLASS-DEFAULT&lt;/P&gt;&lt;P&gt;   serverfarm SFARM1&lt;/P&gt;&lt;P&gt;policy-map type multi-match L4_LB_VIP_POLICY&lt;/P&gt;&lt;P&gt;  class L4_VIP_ADDRESS_CLASS&lt;/P&gt;&lt;P&gt;   loadbalance vip inservice&lt;/P&gt;&lt;P&gt;   loadbalance L7_VIP_LB_ORDER_POLICY&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;3) Conceptually, the Policy Map appears to me to tie in a class-map that specifies the front-end (VIP) traffic and the class-map that ties in the back-end server farm. Is that fair?&lt;/P&gt;&lt;P&gt;4) Does NAT happen automatically or do I need to specify it like in the CSM?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;THANKS!!!&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Mike.&lt;/P&gt;</description>
      <pubDate>Mon, 14 Jul 2008 00:26:58 GMT</pubDate>
      <guid>https://community.cisco.com/t5/application-networking/basic-ace-questions/m-p/954322#M18750</guid>
      <dc:creator>mmertens</dc:creator>
      <dc:date>2008-07-14T00:26:58Z</dc:date>
    </item>
    <item>
      <title>Re: Basic ACE questions</title>
      <link>https://community.cisco.com/t5/application-networking/basic-ace-questions/m-p/954323#M18751</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;1) Ethernet Interface config (duplex, speed, ....), Trunking ,Portchannel and FT config is done in Admin context. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;You assign vlans from Admin contexts to non-Admin contexts using "allocate-interface vlan" command in Admin Context. Then you create   vlan interfaces in user (Or even in Admin context if needed) contexts. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;2. Default-class is only used when all classes fail to match.In situations where there is no need to match any advance characteristics of the traffic, this is the only class that is used under a policy map. One such example is Layer 4 policy.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;3. There are different tpe of class-maps and policy-maps on ACE. For a typical Layer 4 LB rule You need following&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;a. Class-map &lt;/P&gt;&lt;P&gt;To match traffic against Virtual address -- VIP)&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;b. Multi-match policy &lt;/P&gt;&lt;P&gt;It will create kind of "if-then-else" logic for different "Virtual address matching" class-maps.This policy matches the vip and then call the "loadbalance policy" for interesting traffic ( which selects appropriate server farm).&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;c. Load balance policy &lt;/P&gt;&lt;P&gt;It will match a different set of class maps and will select Serverfarm based on the matching criteris (default-class is used here as last resort class).&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;If you need to match Layer 7 stuff (url, cookies, haeaders...) then you need to create class-maps to map these conditions and these class-maps will be used in "Load balance policy-maps"&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;4. Source NAT doesnt happen automatically in most LB devices (same is the case here). Normally destination NAt (VIP -&amp;gt; Real Server)  happens by default on all LB devices (Same is the case here). &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;HTH&lt;/P&gt;&lt;P&gt;Syed Iftekhar Ahmed&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 14 Jul 2008 02:28:07 GMT</pubDate>
      <guid>https://community.cisco.com/t5/application-networking/basic-ace-questions/m-p/954323#M18751</guid>
      <dc:creator>Syed Iftekhar Ahmed</dc:creator>
      <dc:date>2008-07-14T02:28:07Z</dc:date>
    </item>
    <item>
      <title>Re: Basic ACE questions</title>
      <link>https://community.cisco.com/t5/application-networking/basic-ace-questions/m-p/954324#M18752</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Syed,&lt;/P&gt;&lt;P&gt;  Thanks for taking the time. Good stuff....this definitely helps.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Mike.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 14 Jul 2008 11:50:21 GMT</pubDate>
      <guid>https://community.cisco.com/t5/application-networking/basic-ace-questions/m-p/954324#M18752</guid>
      <dc:creator>mmertens</dc:creator>
      <dc:date>2008-07-14T11:50:21Z</dc:date>
    </item>
  </channel>
</rss>

