<?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 Single LAN for ACE deployment in Application Networking</title>
    <link>https://community.cisco.com/t5/application-networking/single-lan-for-ace-deployment/m-p/1741557#M34752</link>
    <description>&lt;P&gt;Hi there,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;We're looking to deploy an ACE 4710 using a single LAN.&amp;nbsp; Our physical servers are on 10.1.1.0/24.&amp;nbsp; We'd like to put the ACE on the same LAN, and make the virtual servers 10.1.1.x as well.&amp;nbsp; I see that this is supported.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;My question is about the management interface.&amp;nbsp; If we want management on that same LAN, do we still use two interfaces, one for management and one for connecting to the servers?&amp;nbsp; Even though they'll both be 10.1.1.0/24?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I should note that this is only for a lab proof of concept of an application failover test.&amp;nbsp; Our real deployment would have multiple interfaces in an etherchannel. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks&lt;/P&gt;</description>
    <pubDate>Mon, 15 Aug 2011 14:59:22 GMT</pubDate>
    <dc:creator>billmatthews</dc:creator>
    <dc:date>2011-08-15T14:59:22Z</dc:date>
    <item>
      <title>Single LAN for ACE deployment</title>
      <link>https://community.cisco.com/t5/application-networking/single-lan-for-ace-deployment/m-p/1741557#M34752</link>
      <description>&lt;P&gt;Hi there,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;We're looking to deploy an ACE 4710 using a single LAN.&amp;nbsp; Our physical servers are on 10.1.1.0/24.&amp;nbsp; We'd like to put the ACE on the same LAN, and make the virtual servers 10.1.1.x as well.&amp;nbsp; I see that this is supported.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;My question is about the management interface.&amp;nbsp; If we want management on that same LAN, do we still use two interfaces, one for management and one for connecting to the servers?&amp;nbsp; Even though they'll both be 10.1.1.0/24?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I should note that this is only for a lab proof of concept of an application failover test.&amp;nbsp; Our real deployment would have multiple interfaces in an etherchannel. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks&lt;/P&gt;</description>
      <pubDate>Mon, 15 Aug 2011 14:59:22 GMT</pubDate>
      <guid>https://community.cisco.com/t5/application-networking/single-lan-for-ace-deployment/m-p/1741557#M34752</guid>
      <dc:creator>billmatthews</dc:creator>
      <dc:date>2011-08-15T14:59:22Z</dc:date>
    </item>
    <item>
      <title>Single LAN for ACE deployment</title>
      <link>https://community.cisco.com/t5/application-networking/single-lan-for-ace-deployment/m-p/1741558#M34753</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt; Bill,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;it is not required. but usually i would recommend to use the management in a seperate connection . If in case you are taking periodic backup or SNMP configuration is there , then we dont want to overload the physical interface or the production network.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;nevertheless ,&amp;nbsp; coming to your question , I hope you are trying to use ACE in bridged more where both real and VIP falls in the same IP range.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;You can very much use the management in the same IP address range having said you configured it correctly.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;it will look like something (sample)&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;class-map type management match-any mgmt&lt;BR /&gt;&amp;nbsp; 10 match protocol icmp any&lt;BR /&gt;&amp;nbsp; 20 match protocol telnet any&lt;BR /&gt;&amp;nbsp; 30 match protocol snmp any&lt;BR /&gt;&amp;nbsp; 40 match protocol http any&lt;/P&gt;&lt;P&gt;policy-map type management first-match mgmt&lt;BR /&gt;&amp;nbsp; class mgmt&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp; permit&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;interface vlan XXX&lt;BR /&gt;&amp;nbsp; description *** Server Side VLAN ***&lt;BR /&gt;&amp;nbsp; bridge-group 1&lt;BR /&gt;&amp;nbsp; mtu 9216&lt;BR /&gt;&amp;nbsp; access-group input ANY&lt;BR /&gt; service-policy input mgmt&lt;BR /&gt;&amp;nbsp; no shutdown&lt;/P&gt;&lt;P&gt;interface vlan 951&lt;BR /&gt;&amp;nbsp; description *** Client Side VLAN ***&lt;BR /&gt;&amp;nbsp; bridge-group 1&lt;BR /&gt;&amp;nbsp;&amp;nbsp; mac-sticky enable&lt;BR /&gt;&amp;nbsp; access-group input ANY&lt;BR /&gt;&amp;nbsp; service-policy input mgmt&lt;BR /&gt;&amp;nbsp; no shutdown&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;interface bvi 1&lt;BR /&gt;&amp;nbsp; ip address &lt;IP address=""&gt; &lt;SUBNETMASK&gt;&lt;/SUBNETMASK&gt;&lt;/IP&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp; no shutdown&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Configuration is not complete ... just a sample.... So this way , you can configure both Mgmt and your requirement in the same IP subnet .&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;HTH,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;-Parvees&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 16 Aug 2011 03:30:53 GMT</pubDate>
      <guid>https://community.cisco.com/t5/application-networking/single-lan-for-ace-deployment/m-p/1741558#M34753</guid>
      <dc:creator>parveesm123</dc:creator>
      <dc:date>2011-08-16T03:30:53Z</dc:date>
    </item>
  </channel>
</rss>

