<?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: Keepalives for service in Application Networking</title>
    <link>https://community.cisco.com/t5/application-networking/keepalives-for-service/m-p/815045#M15917</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Syed, this worked perfectly. I am monitoring both ports and have tested if one goes down the service is down and requests go to other service. For new people, the 5th line in above config is:&lt;/P&gt;&lt;P&gt;keepalive type script then the ap-kal etc...&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks, and the only thing I am watching now is when the service goes down clients have to refresh the page from no service page, unless there is an auto redirection that I can put in config above. I'll update if I can figure it out.&lt;/P&gt;&lt;P&gt;Thanks&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Wed, 27 Jun 2007 10:24:36 GMT</pubDate>
    <dc:creator>thumpercisco</dc:creator>
    <dc:date>2007-06-27T10:24:36Z</dc:date>
    <item>
      <title>Keepalives for service</title>
      <link>https://community.cisco.com/t5/application-networking/keepalives-for-service/m-p/815037#M15909</link>
      <description>&lt;P&gt;I have a service dependent on two separate keepalive ports for an ip address. The first keepalive monitors the root server web service and the second keepalive monitors an application web service on the server. If either go down I want the Load Balancer to stop services to that VIP.&lt;/P&gt;&lt;P&gt;I would like the state to go down if either service keepalive goes down or how can I have keepalive services watch each other and go down if it sees the other service down.&lt;/P&gt;&lt;P&gt;Thanks &lt;/P&gt;</description>
      <pubDate>Thu, 14 Jun 2007 14:36:00 GMT</pubDate>
      <guid>https://community.cisco.com/t5/application-networking/keepalives-for-service/m-p/815037#M15909</guid>
      <dc:creator>thumpercisco</dc:creator>
      <dc:date>2007-06-14T14:36:00Z</dc:date>
    </item>
    <item>
      <title>Re: Keepalives for service</title>
      <link>https://community.cisco.com/t5/application-networking/keepalives-for-service/m-p/815038#M15910</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;You didnt mention the Loadbalancer you are using.I will discuss all the three Cisco LBs for multiple probes requirement&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;If you are using CSS&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;There is a custom scripted keepalive; which tests different TCP, however TAC does not&lt;/P&gt;&lt;P&gt;support scripted keepalives. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Cisco TAC can provide you with the script.I dont remember the name of the script but it checks two ports and mark the service down if either one of the probe fails.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;On CSM&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;when you configure multiple probes for the same serverfarm, all of them&lt;/P&gt;&lt;P&gt;have to be succeful in order to maintain the servers in serverfarm  OPERATIONAL&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;serverfarm sfarm1&lt;/P&gt;&lt;P&gt; nat server &lt;/P&gt;&lt;P&gt; no nat client&lt;/P&gt;&lt;P&gt; real 1.1.1.1&lt;/P&gt;&lt;P&gt;  inservice&lt;/P&gt;&lt;P&gt; real 1.1.1.2&lt;/P&gt;&lt;P&gt;  inservice&lt;/P&gt;&lt;P&gt; probe PING&lt;/P&gt;&lt;P&gt; probe GET&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;In the above example if we are CSM doesnt get a GET response, CSM will mark it down inpsites of the fact that pings from CSM to service are  successful.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;On ACE&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Similar to CSM if you configure multiple probes, service will go down as soon as one probe fails&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Hope it helps&lt;/P&gt;&lt;P&gt;Syed Iftekhar Ahmed&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 14 Jun 2007 18:26:54 GMT</pubDate>
      <guid>https://community.cisco.com/t5/application-networking/keepalives-for-service/m-p/815038#M15910</guid>
      <dc:creator>Syed Iftekhar Ahmed</dc:creator>
      <dc:date>2007-06-14T18:26:54Z</dc:date>
    </item>
    <item>
      <title>Re: Keepalives for service</title>
      <link>https://community.cisco.com/t5/application-networking/keepalives-for-service/m-p/815039#M15911</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;On the CSS you can use the ap-kal-httplist:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The script "ap-kal-httplist" will check a list of webpages with a HEAD request and will be considered failed if any of the pages does not&lt;/P&gt;&lt;P&gt;answer or replies with something different that "200 OK". With it, you should be able to check the status of both the web server and&lt;/P&gt;&lt;P&gt;applications server at the same time.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The correct syntax to use this script is /"keepalive type script ap-kal-httplist "server1 web1 server2 web2 ...."", /so for your environment, you will need to use something like:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;        service test&lt;/P&gt;&lt;P&gt;          ip address 10.10.10.11&lt;/P&gt;&lt;P&gt;          protocol tcp&lt;/P&gt;&lt;P&gt;          port 80&lt;/P&gt;&lt;P&gt;          keepalive port 80&lt;/P&gt;&lt;P&gt;keepalive type script ap-kal-httplist "10.10.10.11 /index_web.html &lt;IP of="" app1=""&gt;&lt;/IP&gt;&lt;/P&gt;&lt;P&gt;/index_app.html"&lt;/P&gt;&lt;P&gt;          active&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Also you use the ap-kal-tcpports:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;A class="jive-link-custom" href="http://www.cisco.com/en/US/products/hw/contnetw/ps792/products_tech_note09186a00801e1e14.shtml" target="_blank"&gt;http://www.cisco.com/en/US/products/hw/contnetw/ps792/products_tech_note09186a00801e1e14.shtml&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;You need to copy the script and then upload it into the CSS, it open a socket connection for the amount of ports that you need.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Hope this help.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;- Rodrigo&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 15 Jun 2007 01:49:18 GMT</pubDate>
      <guid>https://community.cisco.com/t5/application-networking/keepalives-for-service/m-p/815039#M15911</guid>
      <dc:creator>RODRGUTI</dc:creator>
      <dc:date>2007-06-15T01:49:18Z</dc:date>
    </item>
    <item>
      <title>Re: Keepalives for service</title>
      <link>https://community.cisco.com/t5/application-networking/keepalives-for-service/m-p/815040#M15912</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;all I want to do on my CSS11506 is monitor this server ip 192.168.1.1 address and port 80(web service) and 2099(app service) so that if either of these ports goes down the state goes down and users are directed to other server and vice versa.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;service server1&lt;/P&gt;&lt;P&gt;ip address 192.168.1.1&lt;/P&gt;&lt;P&gt;port 80&lt;/P&gt;&lt;P&gt;protocol tcp&lt;/P&gt;&lt;P&gt;keepalive port 80&lt;/P&gt;&lt;P&gt;keepalive type tcp&lt;/P&gt;&lt;P&gt;keepalive freq 15&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;service server1&lt;/P&gt;&lt;P&gt;ip address 192.168.1.1&lt;/P&gt;&lt;P&gt;port 2099&lt;/P&gt;&lt;P&gt;protocol tcp&lt;/P&gt;&lt;P&gt;keepalive port 2099&lt;/P&gt;&lt;P&gt;keepalive type tcp&lt;/P&gt;&lt;P&gt;keepalive freq 15&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;service server2&lt;/P&gt;&lt;P&gt;ip address 192.168.1.1&lt;/P&gt;&lt;P&gt;port 80&lt;/P&gt;&lt;P&gt;protocol tcp&lt;/P&gt;&lt;P&gt;keepalive port 80&lt;/P&gt;&lt;P&gt;keepalive type tcp&lt;/P&gt;&lt;P&gt;keepalive freq 15&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;service server2&lt;/P&gt;&lt;P&gt;ip address 192.168.1.1&lt;/P&gt;&lt;P&gt;port 2099&lt;/P&gt;&lt;P&gt;protocol tcp&lt;/P&gt;&lt;P&gt;keepalive port 2099&lt;/P&gt;&lt;P&gt;keepalive type tcp&lt;/P&gt;&lt;P&gt;keepalive freq 15&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;content with vip and add services&lt;/P&gt;&lt;P&gt;and&lt;/P&gt;&lt;P&gt;group vip and add destination services&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;thanks&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 15 Jun 2007 13:19:40 GMT</pubDate>
      <guid>https://community.cisco.com/t5/application-networking/keepalives-for-service/m-p/815040#M15912</guid>
      <dc:creator>thumpercisco</dc:creator>
      <dc:date>2007-06-15T13:19:40Z</dc:date>
    </item>
    <item>
      <title>Re: Keepalives for service</title>
      <link>https://community.cisco.com/t5/application-networking/keepalives-for-service/m-p/815041#M15913</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;1. Save the script text  as a file with no extension. i.e. ap-kal-tcp-ports&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Script text is available at &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;A class="jive-link-custom" href="http://www.cisco.com/en/US/products/hw/contnetw/ps792/products_tech_note09186a00801e1e14.shtml" target="_blank"&gt;http://www.cisco.com/en/US/products/hw/contnetw/ps792/products_tech_note09186a00801e1e14.shtml&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;(&lt;/P&gt;&lt;P&gt;stating line :!--- No echo.&lt;/P&gt;&lt;P&gt;Ending line: function SOCKET_CONNECT end )&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;2. Open an FTP session to the CSS (use CSS credentials).&lt;/P&gt;&lt;P&gt;3. change the directory to scripts&lt;/P&gt;&lt;P&gt;4. upload the file (ap-kal-tcp-ports)&lt;/P&gt;&lt;P&gt;5. configure keepalive type ap-kal-tcp-ports under service&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;service server1&lt;/P&gt;&lt;P&gt;ip address 192.168.1.1&lt;/P&gt;&lt;P&gt;port 80&lt;/P&gt;&lt;P&gt;protocol tcp&lt;/P&gt;&lt;P&gt;ap-kal-tcp-ports "192.168.1.1 80 2099"&lt;/P&gt;&lt;P&gt;keepalive freq 15&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;6. Activate the service&lt;/P&gt;&lt;P&gt;7. Activate the Content rule&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;hope it helps&lt;/P&gt;&lt;P&gt;Syed iftekhar Ahmed&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, 15 Jun 2007 17:48:30 GMT</pubDate>
      <guid>https://community.cisco.com/t5/application-networking/keepalives-for-service/m-p/815041#M15913</guid>
      <dc:creator>Syed Iftekhar Ahmed</dc:creator>
      <dc:date>2007-06-15T17:48:30Z</dc:date>
    </item>
    <item>
      <title>Re: Keepalives for service</title>
      <link>https://community.cisco.com/t5/application-networking/keepalives-for-service/m-p/815042#M15914</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;When I ran script ap-kal-tcp-ports both ports opened however I received error at end &lt;/P&gt;&lt;P&gt;Error could not remove variable. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;attached script play result&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>Tue, 26 Jun 2007 12:49:23 GMT</pubDate>
      <guid>https://community.cisco.com/t5/application-networking/keepalives-for-service/m-p/815042#M15914</guid>
      <dc:creator>thumpercisco</dc:creator>
      <dc:date>2007-06-26T12:49:23Z</dc:date>
    </item>
    <item>
      <title>Re: Keepalives for service</title>
      <link>https://community.cisco.com/t5/application-networking/keepalives-for-service/m-p/815043#M15915</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;When I ran script ap-kal-tcp-ports both ports opened however I received error at end &lt;/P&gt;&lt;P&gt;Error could not remove variable. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;attached script play result&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 26 Jun 2007 12:58:48 GMT</pubDate>
      <guid>https://community.cisco.com/t5/application-networking/keepalives-for-service/m-p/815043#M15915</guid>
      <dc:creator>thumpercisco</dc:creator>
      <dc:date>2007-06-26T12:58:48Z</dc:date>
    </item>
    <item>
      <title>Re: Keepalives for service</title>
      <link>https://community.cisco.com/t5/application-networking/keepalives-for-service/m-p/815044#M15916</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;When I ran script ap-kal-tcp-ports both ports opened however I received error at end &lt;/P&gt;&lt;P&gt;Error could not remove variable. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;attached script play result&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 26 Jun 2007 13:16:58 GMT</pubDate>
      <guid>https://community.cisco.com/t5/application-networking/keepalives-for-service/m-p/815044#M15916</guid>
      <dc:creator>thumpercisco</dc:creator>
      <dc:date>2007-06-26T13:16:58Z</dc:date>
    </item>
    <item>
      <title>Re: Keepalives for service</title>
      <link>https://community.cisco.com/t5/application-networking/keepalives-for-service/m-p/815045#M15917</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Syed, this worked perfectly. I am monitoring both ports and have tested if one goes down the service is down and requests go to other service. For new people, the 5th line in above config is:&lt;/P&gt;&lt;P&gt;keepalive type script then the ap-kal etc...&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks, and the only thing I am watching now is when the service goes down clients have to refresh the page from no service page, unless there is an auto redirection that I can put in config above. I'll update if I can figure it out.&lt;/P&gt;&lt;P&gt;Thanks&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 27 Jun 2007 10:24:36 GMT</pubDate>
      <guid>https://community.cisco.com/t5/application-networking/keepalives-for-service/m-p/815045#M15917</guid>
      <dc:creator>thumpercisco</dc:creator>
      <dc:date>2007-06-27T10:24:36Z</dc:date>
    </item>
  </channel>
</rss>

