<?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: HTTP &amp; HTTPS Keepalives on the same server in Application Networking</title>
    <link>https://community.cisco.com/t5/application-networking/http-https-keepalives-on-the-same-server/m-p/142295#M1674</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;You would need to create two services and specify keepalive tcp and keepalive port&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Example &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;service s1-80&lt;/P&gt;&lt;P&gt;  ip address 10.1.1.1&lt;/P&gt;&lt;P&gt;  keepalive type tcp&lt;/P&gt;&lt;P&gt;  keepalive port 80&lt;/P&gt;&lt;P&gt;  active&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;service s1-443&lt;/P&gt;&lt;P&gt;  ip address 10.1.1.1&lt;/P&gt;&lt;P&gt;  keepalive type tcp&lt;/P&gt;&lt;P&gt;  keepalive port 443&lt;/P&gt;&lt;P&gt;  active&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;You then create to content rules for each port.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;  content port80&lt;/P&gt;&lt;P&gt;    vip address 10.1.1.3.&lt;/P&gt;&lt;P&gt;    protocol tcp&lt;/P&gt;&lt;P&gt;    port 80&lt;/P&gt;&lt;P&gt;    add service s1-80&lt;/P&gt;&lt;P&gt;    active&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;content port443&lt;/P&gt;&lt;P&gt;    vip address 10.1.1.3.&lt;/P&gt;&lt;P&gt;    protocol tcp&lt;/P&gt;&lt;P&gt;    port 443&lt;/P&gt;&lt;P&gt;    add service s1-80&lt;/P&gt;&lt;P&gt;    active&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Your other option would be to write a custom keepalive script that would monitor both ports with one keepalive.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Link to scripted keepalives&lt;/P&gt;&lt;P&gt;&lt;A class="jive-link-custom" href="http://www.cisco.com/en/US/partner/products/hw/contnetw/ps789/products_configuration_guide_chapter09186a00800ae3cd.html#38632" target="_blank"&gt;http://www.cisco.com/en/US/partner/products/hw/contnetw/ps789/products_configuration_guide_chapter09186a00800ae3cd.html#38632&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Scripting Language&lt;/P&gt;&lt;P&gt;&lt;A class="jive-link-custom" href="http://www.cisco.com/en/US/partner/products/hw/contnetw/ps789/products_configuration_guide_chapter09186a00800d6b3f.html" target="_blank"&gt;http://www.cisco.com/en/US/partner/products/hw/contnetw/ps789/products_configuration_guide_chapter09186a00800d6b3f.html&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Mon, 02 Dec 2002 18:58:10 GMT</pubDate>
    <dc:creator>msardzin</dc:creator>
    <dc:date>2002-12-02T18:58:10Z</dc:date>
    <item>
      <title>HTTP &amp; HTTPS Keepalives on the same server</title>
      <link>https://community.cisco.com/t5/application-networking/http-https-keepalives-on-the-same-server/m-p/142294#M1673</link>
      <description>&lt;P&gt;I have A CSS11050 load balancing two servers that host two web sites one is HTTP the other is HTTPS.  each server hosts a copy of the HTTP and HTTPS sites.   The physical address of these servers is 10.1.1.1 and 10.1.1.2 with a VIP of 10.1.1.3.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;How do I configure the service or content rule to simultaneously send both HTTP and HTTPS keepalives to the same server. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks&lt;/P&gt;</description>
      <pubDate>Mon, 02 Dec 2002 13:25:41 GMT</pubDate>
      <guid>https://community.cisco.com/t5/application-networking/http-https-keepalives-on-the-same-server/m-p/142294#M1673</guid>
      <dc:creator>cox</dc:creator>
      <dc:date>2002-12-02T13:25:41Z</dc:date>
    </item>
    <item>
      <title>Re: HTTP &amp; HTTPS Keepalives on the same server</title>
      <link>https://community.cisco.com/t5/application-networking/http-https-keepalives-on-the-same-server/m-p/142295#M1674</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;You would need to create two services and specify keepalive tcp and keepalive port&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Example &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;service s1-80&lt;/P&gt;&lt;P&gt;  ip address 10.1.1.1&lt;/P&gt;&lt;P&gt;  keepalive type tcp&lt;/P&gt;&lt;P&gt;  keepalive port 80&lt;/P&gt;&lt;P&gt;  active&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;service s1-443&lt;/P&gt;&lt;P&gt;  ip address 10.1.1.1&lt;/P&gt;&lt;P&gt;  keepalive type tcp&lt;/P&gt;&lt;P&gt;  keepalive port 443&lt;/P&gt;&lt;P&gt;  active&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;You then create to content rules for each port.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;  content port80&lt;/P&gt;&lt;P&gt;    vip address 10.1.1.3.&lt;/P&gt;&lt;P&gt;    protocol tcp&lt;/P&gt;&lt;P&gt;    port 80&lt;/P&gt;&lt;P&gt;    add service s1-80&lt;/P&gt;&lt;P&gt;    active&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;content port443&lt;/P&gt;&lt;P&gt;    vip address 10.1.1.3.&lt;/P&gt;&lt;P&gt;    protocol tcp&lt;/P&gt;&lt;P&gt;    port 443&lt;/P&gt;&lt;P&gt;    add service s1-80&lt;/P&gt;&lt;P&gt;    active&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Your other option would be to write a custom keepalive script that would monitor both ports with one keepalive.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Link to scripted keepalives&lt;/P&gt;&lt;P&gt;&lt;A class="jive-link-custom" href="http://www.cisco.com/en/US/partner/products/hw/contnetw/ps789/products_configuration_guide_chapter09186a00800ae3cd.html#38632" target="_blank"&gt;http://www.cisco.com/en/US/partner/products/hw/contnetw/ps789/products_configuration_guide_chapter09186a00800ae3cd.html#38632&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Scripting Language&lt;/P&gt;&lt;P&gt;&lt;A class="jive-link-custom" href="http://www.cisco.com/en/US/partner/products/hw/contnetw/ps789/products_configuration_guide_chapter09186a00800d6b3f.html" target="_blank"&gt;http://www.cisco.com/en/US/partner/products/hw/contnetw/ps789/products_configuration_guide_chapter09186a00800d6b3f.html&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 02 Dec 2002 18:58:10 GMT</pubDate>
      <guid>https://community.cisco.com/t5/application-networking/http-https-keepalives-on-the-same-server/m-p/142295#M1674</guid>
      <dc:creator>msardzin</dc:creator>
      <dc:date>2002-12-02T18:58:10Z</dc:date>
    </item>
    <item>
      <title>Re: HTTP &amp; HTTPS Keepalives on the same server</title>
      <link>https://community.cisco.com/t5/application-networking/http-https-keepalives-on-the-same-server/m-p/142296#M1675</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Is the URL for the scripted keepalives just for Cisco people?  I have a CCO log on but can't seem to get to the page.  Seems like the bit at the end ie #38632 is what is not accessible.  Would appreciate some clarification.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;regards&lt;/P&gt;&lt;P&gt;Tony Barnett&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 03 Dec 2002 00:10:07 GMT</pubDate>
      <guid>https://community.cisco.com/t5/application-networking/http-https-keepalives-on-the-same-server/m-p/142296#M1675</guid>
      <dc:creator>barnettt</dc:creator>
      <dc:date>2002-12-03T00:10:07Z</dc:date>
    </item>
    <item>
      <title>Re: HTTP &amp; HTTPS Keepalives on the same server</title>
      <link>https://community.cisco.com/t5/application-networking/http-https-keepalives-on-the-same-server/m-p/142297#M1676</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;This has solved my problem.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Many thanks.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 03 Dec 2002 12:32:05 GMT</pubDate>
      <guid>https://community.cisco.com/t5/application-networking/http-https-keepalives-on-the-same-server/m-p/142297#M1676</guid>
      <dc:creator>cox</dc:creator>
      <dc:date>2002-12-03T12:32:05Z</dc:date>
    </item>
  </channel>
</rss>

