<?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: load balancing FTP/HTTP on same VIP in Application Networking</title>
    <link>https://community.cisco.com/t5/application-networking/load-balancing-ftp-http-on-same-vip/m-p/1377608#M28665</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hello Muhammad,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Two points on your config:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;OL&gt;&lt;LI&gt;It is recommended to perform protocol inspection (ie.&amp;nbsp; inspect ftp) only on the required protocol, so it is better to separate them out.&lt;/LI&gt;&lt;LI&gt;Your config requirement is a bit more complex than normal due to the client NAT and one-armed.&amp;nbsp; &lt;/LI&gt;&lt;/OL&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I would recommend trying this with the following config.&amp;nbsp; This way, both the FTP and HTTP will be source-NAT'd as desired, then the passive FTP data channel will also be NAT'd.&amp;nbsp; This config will likely be required if you are using passive FTP.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-family: courier new,courier;"&gt;class-map match-any WCVS-WWW&lt;BR /&gt;&amp;nbsp; 2 match virtual-address 20.0.0.1 tcp eq www&lt;BR /&gt;class-map match-any WCVS-FTP&lt;BR /&gt;&amp;nbsp; 2 match virtual-address 20.0.0.1 tcp eq ftp&lt;BR /&gt;class-map match-all NAT-VIP&lt;BR /&gt;&amp;nbsp; 2 match destination-address 20.0.0.1 255.255.255.255&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-family: courier new,courier;"&gt;policy-map type loadbalance first-match VS-l7slb&lt;BR /&gt;&amp;nbsp; class class-default&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp; serverfarm SERVERS&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-family: courier new,courier;"&gt;policy-map multi-match int3&lt;BR /&gt;&amp;nbsp; class WCVS-WWW&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp; loadbalance vip inservice&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp; loadbalance policy VS-l7slb&lt;BR /&gt;&amp;nbsp; class WCVS-FTP&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp; loadbalance vip inservice&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp; loadbalance policy VS-l7slb&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp; inspect ftp&lt;BR /&gt;&amp;nbsp; class NAT-VIP&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp; nat dynamic 5 vlan 20&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-family: courier new,courier;"&gt;int vl20&lt;BR /&gt;&amp;nbsp; service-policy input int3&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Don't forget that your VLAN interface will also need an ACL applied that will permit the traffic to this VIP.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Hope this helps,&lt;/P&gt;&lt;P&gt;Sean&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Mon, 01 Feb 2010 14:01:08 GMT</pubDate>
    <dc:creator>Sean Merrow</dc:creator>
    <dc:date>2010-02-01T14:01:08Z</dc:date>
    <item>
      <title>load balancing FTP/HTTP on same VIP</title>
      <link>https://community.cisco.com/t5/application-networking/load-balancing-ftp-http-on-same-vip/m-p/1377607#M28664</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Please could someone confirm if it is possible to load balance FTP and HTTP on same VIP? Would something like this work in a one-armed design?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;class-map match-any WCVS&lt;BR /&gt;&amp;nbsp; 2 match virtual-address 20.0.0.1 tcp eq www&lt;BR /&gt;&amp;nbsp; 4 match virtual-address 20.0.0.1 tcp eq ftp&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;policy-map multi-match int3&lt;BR /&gt;&amp;nbsp; class WCVS&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp; loadbalance vip inservice&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp; loadbalance policy VS-l7slb&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp; inspect ftp&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp; nat dynamic 5 vlan 20&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;int vl20&lt;BR /&gt;service-policy input int3&lt;/P&gt;</description>
      <pubDate>Fri, 29 Jan 2010 15:51:55 GMT</pubDate>
      <guid>https://community.cisco.com/t5/application-networking/load-balancing-ftp-http-on-same-vip/m-p/1377607#M28664</guid>
      <dc:creator>Muhammad Khan</dc:creator>
      <dc:date>2010-01-29T15:51:55Z</dc:date>
    </item>
    <item>
      <title>Re: load balancing FTP/HTTP on same VIP</title>
      <link>https://community.cisco.com/t5/application-networking/load-balancing-ftp-http-on-same-vip/m-p/1377608#M28665</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hello Muhammad,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Two points on your config:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;OL&gt;&lt;LI&gt;It is recommended to perform protocol inspection (ie.&amp;nbsp; inspect ftp) only on the required protocol, so it is better to separate them out.&lt;/LI&gt;&lt;LI&gt;Your config requirement is a bit more complex than normal due to the client NAT and one-armed.&amp;nbsp; &lt;/LI&gt;&lt;/OL&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I would recommend trying this with the following config.&amp;nbsp; This way, both the FTP and HTTP will be source-NAT'd as desired, then the passive FTP data channel will also be NAT'd.&amp;nbsp; This config will likely be required if you are using passive FTP.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-family: courier new,courier;"&gt;class-map match-any WCVS-WWW&lt;BR /&gt;&amp;nbsp; 2 match virtual-address 20.0.0.1 tcp eq www&lt;BR /&gt;class-map match-any WCVS-FTP&lt;BR /&gt;&amp;nbsp; 2 match virtual-address 20.0.0.1 tcp eq ftp&lt;BR /&gt;class-map match-all NAT-VIP&lt;BR /&gt;&amp;nbsp; 2 match destination-address 20.0.0.1 255.255.255.255&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-family: courier new,courier;"&gt;policy-map type loadbalance first-match VS-l7slb&lt;BR /&gt;&amp;nbsp; class class-default&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp; serverfarm SERVERS&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-family: courier new,courier;"&gt;policy-map multi-match int3&lt;BR /&gt;&amp;nbsp; class WCVS-WWW&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp; loadbalance vip inservice&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp; loadbalance policy VS-l7slb&lt;BR /&gt;&amp;nbsp; class WCVS-FTP&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp; loadbalance vip inservice&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp; loadbalance policy VS-l7slb&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp; inspect ftp&lt;BR /&gt;&amp;nbsp; class NAT-VIP&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp; nat dynamic 5 vlan 20&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-family: courier new,courier;"&gt;int vl20&lt;BR /&gt;&amp;nbsp; service-policy input int3&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Don't forget that your VLAN interface will also need an ACL applied that will permit the traffic to this VIP.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Hope this helps,&lt;/P&gt;&lt;P&gt;Sean&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 01 Feb 2010 14:01:08 GMT</pubDate>
      <guid>https://community.cisco.com/t5/application-networking/load-balancing-ftp-http-on-same-vip/m-p/1377608#M28665</guid>
      <dc:creator>Sean Merrow</dc:creator>
      <dc:date>2010-02-01T14:01:08Z</dc:date>
    </item>
    <item>
      <title>Re: load balancing FTP/HTTP on same VIP</title>
      <link>https://community.cisco.com/t5/application-networking/load-balancing-ftp-http-on-same-vip/m-p/1377609#M28666</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Sean,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thank you for your reply.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I have tested the config. HTTP part seems to be working well but FTP is failing. When I try to establish a FTP connection I get connected message but nothing beyone:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;C:\&amp;gt;ftp &lt;A href="http://www.xxx.com"&gt;www.xxx.com&lt;/A&gt;&lt;BR /&gt;Connected to &lt;A href="http://www.xxx.com"&gt;www.xxx.com&lt;/A&gt;.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I have attached device config if you get a chance to review.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 01 Feb 2010 17:55:42 GMT</pubDate>
      <guid>https://community.cisco.com/t5/application-networking/load-balancing-ftp-http-on-same-vip/m-p/1377609#M28666</guid>
      <dc:creator>Muhammad Khan</dc:creator>
      <dc:date>2010-02-01T17:55:42Z</dc:date>
    </item>
    <item>
      <title>Re: load balancing FTP/HTTP on same VIP</title>
      <link>https://community.cisco.com/t5/application-networking/load-balancing-ftp-http-on-same-vip/m-p/1377610#M28667</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hello,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I assume you want to ultimately use cookie sticky, since it is in your config, but not yet used.&amp;nbsp; The '80' next to the rservers within the serverfarm will keep FTP from working because that will force the ACE to always use a destination port of 80 to the rservers, which is good for HTTP, but not so good for FTP.&amp;nbsp; Below is your config with some modifications.&amp;nbsp; I've created a new serverfarm for FTP, created a new probe for that farm, included HTTP cookie-sticky, and created a new L7 policy-map.&amp;nbsp; There is one line that I would like you to remove and see if it works.&amp;nbsp; If it does not, then add this line and see if it works.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Let me know how it goes...&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-family: courier new,courier;"&gt;logging enable&lt;BR /&gt;logging buffered 6&lt;BR /&gt;&lt;BR /&gt;access-list ALL line 8 extended permit ip any any&lt;BR /&gt;access-list ALL line 16 extended permit icmp any any&lt;BR /&gt;&lt;BR /&gt;probe http Probe_HTTP&lt;BR /&gt;&amp;nbsp; interval 5&lt;BR /&gt;&amp;nbsp; passdetect interval 60&lt;BR /&gt;&amp;nbsp; expect status 200 200&lt;BR /&gt;&amp;nbsp; open 2&lt;BR /&gt;&amp;nbsp; receive 2&lt;BR /&gt;&lt;BR /&gt;probe tcp Probe_FTP&lt;BR /&gt;&amp;nbsp; port 21&lt;BR /&gt;&amp;nbsp; interval 5&lt;BR /&gt;&amp;nbsp; passdetect interval 60&lt;BR /&gt;&amp;nbsp; open 2&lt;BR /&gt;&amp;nbsp; receive 2&lt;BR /&gt;&lt;BR /&gt;rserver host Server1&lt;BR /&gt;&amp;nbsp; ip address 10.10.10.10&lt;BR /&gt;&amp;nbsp; conn-limit max 4000000 min 4000000&lt;BR /&gt;&amp;nbsp; inservice&lt;BR /&gt;rserver host Server2&lt;BR /&gt;&amp;nbsp; ip address 10.10.10.11&lt;BR /&gt;&amp;nbsp; conn-limit max 4000000 min 4000000&lt;BR /&gt;&amp;nbsp; inservice&lt;BR /&gt;&lt;BR /&gt;serverfarm host FARM-HTTP&lt;BR /&gt;&amp;nbsp; probe Probe_HTTP&lt;BR /&gt;&amp;nbsp; rserver Server1 80&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp; conn-limit max 4000000 min 4000000&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp; inservice&lt;BR /&gt;&amp;nbsp; rserver Server2 80&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp; conn-limit max 4000000 min 4000000&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp; inservice&lt;BR /&gt;&lt;BR /&gt;serverfarm host FARM-FTP&lt;BR /&gt;&amp;nbsp; probe Probe_FTP&lt;BR /&gt;&amp;nbsp; rserver Server1&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp; conn-limit max 4000000 min 4000000&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp; inservice&lt;BR /&gt;&amp;nbsp; rserver Server2&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp; conn-limit max 4000000 min 4000000&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp; inservice&lt;BR /&gt;&lt;BR /&gt;sticky http-cookie XXX_tempCookie XXX_tempCookie&lt;BR /&gt;&amp;nbsp; cookie insert&lt;BR /&gt;&amp;nbsp; serverfarm FARM-HTTP&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;class-map type management match-any Management&lt;BR /&gt;&amp;nbsp; 201 match protocol http any&lt;BR /&gt;&amp;nbsp; 202 match protocol https any&lt;BR /&gt;&amp;nbsp; 203 match protocol icmp any&lt;BR /&gt;&amp;nbsp; 204 match protocol kalap-udp any&lt;BR /&gt;&amp;nbsp; 205 match protocol ssh any&lt;BR /&gt;&amp;nbsp; 206 match protocol telnet any&lt;BR /&gt;&amp;nbsp; 207 match protocol xml-https any&lt;BR /&gt;&lt;BR /&gt;class-map match-any XXX-WCVS-WWW&lt;BR /&gt;&amp;nbsp; 2 match virtual-address 10.10.10.100 tcp eq www&lt;BR /&gt;&lt;BR /&gt;class-map match-any XXX-WCVS-FTP&lt;BR /&gt;&amp;nbsp; 2 match virtual-address 10.10.10.100 tcp eq ftp&lt;BR /&gt;&amp;nbsp; 3 match virtual-address 10.10.10.100 tcp range 1023 65535&amp;nbsp;&amp;nbsp; &amp;lt;-- try first without this, then with this&lt;BR /&gt;&lt;BR /&gt;class-map match-any NAT-VIP&lt;BR /&gt;&amp;nbsp; 2 match destination-address 10.10.10.100 255.255.255.255&lt;BR /&gt;&lt;BR /&gt;policy-map type management first-match Management&lt;BR /&gt;&amp;nbsp; class Management&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp; permit&lt;BR /&gt;&lt;BR /&gt;policy-map type loadbalance first-match XXX_VS-l7slb-WWW&lt;BR /&gt;&amp;nbsp; class class-default&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp; sticky-serverfarm XXX_tempCookie&lt;BR /&gt;&lt;BR /&gt;policy-map type loadbalance first-match XXX_VS-l7slb-FTP&lt;BR /&gt;&amp;nbsp; class class-default&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp; Serverfarm FARM-FTP&lt;BR /&gt;&lt;BR /&gt;policy-map multi-match int3&lt;BR /&gt;&amp;nbsp; class XXX-WCVS-WWW&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp; loadbalance vip inservice&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp; loadbalance policy XXX_VS-l7slb-WWW&lt;BR /&gt;&amp;nbsp; class XXX-WCVS-FTP&amp;nbsp;&amp;nbsp;&amp;nbsp; &lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp; loadbalance vip inservice&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp; loadbalance policy XXX_VS-l7slb-FTP&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp; inspect ftp&amp;nbsp;&amp;nbsp;&amp;nbsp; &lt;BR /&gt;&amp;nbsp; class NAT-VIP&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp; nat dynamic 5 vlan 12&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp; &lt;BR /&gt;&lt;BR /&gt;interface vlan 12&lt;BR /&gt;&amp;nbsp; ip address 10.10.10.1 255.255.255.0&lt;BR /&gt;&amp;nbsp; alias 10.10.10.3 255.255.255.0&lt;BR /&gt;&amp;nbsp; peer ip address 10.10.10.2 255.255.255.0&lt;BR /&gt;&amp;nbsp; access-group input ALL&lt;BR /&gt;&amp;nbsp; nat-pool 5 10.10.10.100 10.10.10.100 netmask 255.255.255.0 pat&lt;BR /&gt;&amp;nbsp; service-policy input Management&lt;BR /&gt;&amp;nbsp; service-policy input int3&lt;BR /&gt;&amp;nbsp; no shutdown&lt;BR /&gt;&lt;BR /&gt;ip route 0.0.0.0 0.0.0.0 10.10.10.254&lt;/SPAN&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 01 Feb 2010 18:53:33 GMT</pubDate>
      <guid>https://community.cisco.com/t5/application-networking/load-balancing-ftp-http-on-same-vip/m-p/1377610#M28667</guid>
      <dc:creator>Sean Merrow</dc:creator>
      <dc:date>2010-02-01T18:53:33Z</dc:date>
    </item>
    <item>
      <title>Re: load balancing FTP/HTTP on same VIP</title>
      <link>https://community.cisco.com/t5/application-networking/load-balancing-ftp-http-on-same-vip/m-p/1377611#M28668</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Sean,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thank you for your reply it works perfect.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;It works without range so inspect takes care of Active FTP connection.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-family: Courier New;"&gt;&amp;nbsp; 3 match virtual-address 10.10.10.100 tcp range 1023 65535 [Not required]&lt;BR /&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-family: Courier New;"&gt;&lt;SPAN style="font-family: arial,helvetica,sans-serif;"&gt;For FTP probe I would assume it only checks the successful hand-shake as oppose to establishing a TCP connection to the server and then issues a quit command as it would do in an FTP type probe?&lt;/SPAN&gt; &lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-family: arial,helvetica,sans-serif;"&gt;"A TCP probe makes a connection, and if the connection through a 3-way handshake (SYN, SYN-ACK, and ACK) is successful, the server is marked as passed" [Cisco 4700 Series Application Control Engine Appliance Server Load-Balancing Configuration Guide]&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;An FTP probe establishes a TCP connection to the server and then issues a quit command.[&lt;SPAN style="font-family: arial,helvetica,sans-serif;"&gt;Cisco 4700 Series Application Control Engine Appliance Server Load-Balancing Configuration Guide]&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thank you for your help.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Muhammad.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 02 Feb 2010 15:28:05 GMT</pubDate>
      <guid>https://community.cisco.com/t5/application-networking/load-balancing-ftp-http-on-same-vip/m-p/1377611#M28668</guid>
      <dc:creator>Muhammad Khan</dc:creator>
      <dc:date>2010-02-02T15:28:05Z</dc:date>
    </item>
    <item>
      <title>Re: load balancing FTP/HTTP on same VIP</title>
      <link>https://community.cisco.com/t5/application-networking/load-balancing-ftp-http-on-same-vip/m-p/1377612#M28669</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Muhammad,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks for the follow-up, and glad to hear it is working.&amp;nbsp; You are correct about the TCP probe.&amp;nbsp; I only wanted to get across the idea of using a unique probe for each application.&amp;nbsp; You would be better off using the FTP probe for the FTP servers, rather than using a TCP probe.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;- Sean&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 02 Feb 2010 15:34:58 GMT</pubDate>
      <guid>https://community.cisco.com/t5/application-networking/load-balancing-ftp-http-on-same-vip/m-p/1377612#M28669</guid>
      <dc:creator>Sean Merrow</dc:creator>
      <dc:date>2010-02-02T15:34:58Z</dc:date>
    </item>
  </channel>
</rss>

