<?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 Same context load balancing in Application Networking</title>
    <link>https://community.cisco.com/t5/application-networking/same-context-load-balancing/m-p/2395816#M41322</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt; Hi Brian,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Inter context traffic is not allowed but you can use a L3 device to communicate across contexts.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regarding your second question you can have the LB between the same set of IP's but you would NAT so that traffic goes through loadbalancer all the time and not directly since devices are in same subnet.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;From one of the other posts:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;ACE does not allow intercontext communication for security reasons. This can't be changed.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;However, you can still achieve communication by going through an external gateway.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;If rserver RA in vlan A of context A wants to communicate with vlan B, VIP-B, you should configure context A with a static host route, pointing VIP-B to the default gateway on the shared vlan. This default gateway will then forward the traffic to context B and for ACE it is like the connection comes from outside and not another context.&lt;/P&gt;&lt;P&gt;Same for the response, you need on context B a route for vlan A via the shared vlan and the gateway - not the other context.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;Kanwal&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Sun, 01 Dec 2013 20:25:42 GMT</pubDate>
    <dc:creator>Kanwaljeet Singh</dc:creator>
    <dc:date>2013-12-01T20:25:42Z</dc:date>
    <item>
      <title>Same context load balancing</title>
      <link>https://community.cisco.com/t5/application-networking/same-context-load-balancing/m-p/2395815#M41321</link>
      <description>&lt;P&gt;Bear with me, I'm reasonable new to the ACE module, my main experience of Cisco Load Balancing was on the CSM.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Can I load balance between a group of servers and another group within the same context and in the same ip address range?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I've just taken a job where the previous guy put everything in one context.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I've recommended that the two different type of servers should be seperated into seperate contextes but we're too far down the design road for that!&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Traffic will be HTTP and LDAP.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Any help really appreciated!&lt;/P&gt;</description>
      <pubDate>Sun, 01 Dec 2013 20:03:52 GMT</pubDate>
      <guid>https://community.cisco.com/t5/application-networking/same-context-load-balancing/m-p/2395815#M41321</guid>
      <dc:creator>brianwhelton</dc:creator>
      <dc:date>2013-12-01T20:03:52Z</dc:date>
    </item>
    <item>
      <title>Same context load balancing</title>
      <link>https://community.cisco.com/t5/application-networking/same-context-load-balancing/m-p/2395816#M41322</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt; Hi Brian,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Inter context traffic is not allowed but you can use a L3 device to communicate across contexts.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regarding your second question you can have the LB between the same set of IP's but you would NAT so that traffic goes through loadbalancer all the time and not directly since devices are in same subnet.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;From one of the other posts:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;ACE does not allow intercontext communication for security reasons. This can't be changed.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;However, you can still achieve communication by going through an external gateway.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;If rserver RA in vlan A of context A wants to communicate with vlan B, VIP-B, you should configure context A with a static host route, pointing VIP-B to the default gateway on the shared vlan. This default gateway will then forward the traffic to context B and for ACE it is like the connection comes from outside and not another context.&lt;/P&gt;&lt;P&gt;Same for the response, you need on context B a route for vlan A via the shared vlan and the gateway - not the other context.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;Kanwal&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Sun, 01 Dec 2013 20:25:42 GMT</pubDate>
      <guid>https://community.cisco.com/t5/application-networking/same-context-load-balancing/m-p/2395816#M41322</guid>
      <dc:creator>Kanwaljeet Singh</dc:creator>
      <dc:date>2013-12-01T20:25:42Z</dc:date>
    </item>
    <item>
      <title>Same context load balancing</title>
      <link>https://community.cisco.com/t5/application-networking/same-context-load-balancing/m-p/2395817#M41323</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi &lt;SPAN style="font-size: 10pt;"&gt;Kanwal&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-size: 10pt;"&gt;Thanks for the answer,&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-size: 10pt;"&gt;To clarify what I meant was this.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-size: 10pt;"&gt;Only one context, host from outside sends request to the ACE modules VIP and it forwarded to servers type A (Lets say two servers A1 and A2), this works fine.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-size: 10pt;"&gt;I want to know the practicalities or the request then being load balanced again from either A1 or 2 to servers type 2 (B1, B2 and B3) in the same context and ip address range before returning to the host either via servers A agin or direct.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-size: 10pt;"&gt;Is that clearer?&lt;/SPAN&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Sun, 01 Dec 2013 20:32:50 GMT</pubDate>
      <guid>https://community.cisco.com/t5/application-networking/same-context-load-balancing/m-p/2395817#M41323</guid>
      <dc:creator>brianwhelton</dc:creator>
      <dc:date>2013-12-01T20:32:50Z</dc:date>
    </item>
    <item>
      <title>Same context load balancing</title>
      <link>https://community.cisco.com/t5/application-networking/same-context-load-balancing/m-p/2395818#M41324</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Brian,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Yeah it should work. Request from A1 or 2 would be considered as a new request and should be loadbalanced normally. Just ensure that NAT is in place so that traffic doesn't go directly to servers but via ACE for loadbalancing to work properly.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;Kanwal&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Sun, 01 Dec 2013 20:38:59 GMT</pubDate>
      <guid>https://community.cisco.com/t5/application-networking/same-context-load-balancing/m-p/2395818#M41324</guid>
      <dc:creator>Kanwaljeet Singh</dc:creator>
      <dc:date>2013-12-01T20:38:59Z</dc:date>
    </item>
    <item>
      <title>Same context load balancing</title>
      <link>https://community.cisco.com/t5/application-networking/same-context-load-balancing/m-p/2395819#M41325</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Thanks, I'll look into it!&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Sun, 01 Dec 2013 20:40:57 GMT</pubDate>
      <guid>https://community.cisco.com/t5/application-networking/same-context-load-balancing/m-p/2395819#M41325</guid>
      <dc:creator>brianwhelton</dc:creator>
      <dc:date>2013-12-01T20:40:57Z</dc:date>
    </item>
  </channel>
</rss>

