<?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: Creating a New Content Rule in Application Networking</title>
    <link>https://community.cisco.com/t5/application-networking/creating-a-new-content-rule/m-p/384509#M6729</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;create a new service for your sorry server.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Then under the content rule defined for http traffic, you add the following line:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;primarySorryServer &lt;SERVICE sorry="" server=""&gt;&lt;/SERVICE&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regarding the config you provided, what you show is a 'show service &lt;NAME&gt;' and we can clearly see that even if your 2 services have different name, they are identical.&lt;/NAME&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I believe you would want to configure different keepalive.&lt;/P&gt;&lt;P&gt;ie: for HTTP&lt;/P&gt;&lt;P&gt;keepalive port 80&lt;/P&gt;&lt;P&gt;keepalive type http&lt;/P&gt;&lt;P&gt;keepalive uri "/"&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;for rtsp&lt;/P&gt;&lt;P&gt;keepalive port 554&lt;/P&gt;&lt;P&gt;keepaliave type tcp&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Gilles.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Mon, 17 Jan 2005 14:50:13 GMT</pubDate>
    <dc:creator>Gilles Dufour</dc:creator>
    <dc:date>2005-01-17T14:50:13Z</dc:date>
    <item>
      <title>Creating a New Content Rule</title>
      <link>https://community.cisco.com/t5/application-networking/creating-a-new-content-rule/m-p/384508#M6728</link>
      <description>&lt;P&gt;I need some help creating a content rule for a service that we offer to our end users.  We have a video server that people can hit via the web.  Currently it sits on one server in a DMZ and is not going through a CSS.  We have just built a new environment and as a prereq for future expansion we want to put the video server behind a CSS.  Even though there is currently only one server it will make the addition of another and load balancing easier.  &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I believe that our video service uses ports 80 and 554.  I have created the following services to check this:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt; Name: video_rtsp        Index: 13&lt;/P&gt;&lt;P&gt;  Type: Local            State: Alive&lt;/P&gt;&lt;P&gt;  Rule ( 10.0.1.19  ANY  ANY )&lt;/P&gt;&lt;P&gt;  Session Redundancy: Disabled&lt;/P&gt;&lt;P&gt;  Redirect Domain:&lt;/P&gt;&lt;P&gt;  Redirect String: (null)&lt;/P&gt;&lt;P&gt;  Keepalive: (ICMP  60   3  60 )&lt;/P&gt;&lt;P&gt;  Last Clearing of Stats Counters: 01/09/2005 15:47:20&lt;/P&gt;&lt;P&gt;  Mtu:                       1500        State Transitions:            14&lt;/P&gt;&lt;P&gt;  Total Local Connections:   0           Total Backup Connections:     0&lt;/P&gt;&lt;P&gt;  Current Local Connections: 0           Current Backup Connections:   0&lt;/P&gt;&lt;P&gt;  Total Connections:         0           Max Connections:              65534&lt;/P&gt;&lt;P&gt;  Total Reused Conns:        0&lt;/P&gt;&lt;P&gt;  Weight:                    1           Load:                         2&lt;/P&gt;&lt;P&gt;  DFP:                       Disable&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt; Name: video_www         Index: 14&lt;/P&gt;&lt;P&gt;  Type: Local            State: Alive&lt;/P&gt;&lt;P&gt;  Rule ( 10.0.1.19  ANY  ANY )&lt;/P&gt;&lt;P&gt;  Session Redundancy: Disabled&lt;/P&gt;&lt;P&gt;  Redirect Domain:&lt;/P&gt;&lt;P&gt;  Redirect String: (null)&lt;/P&gt;&lt;P&gt;  Keepalive: (ICMP  60   3  60 )&lt;/P&gt;&lt;P&gt;  Last Clearing of Stats Counters: 01/09/2005 15:47:20&lt;/P&gt;&lt;P&gt;  Mtu:                       1500        State Transitions:            12&lt;/P&gt;&lt;P&gt;  Total Local Connections:   0           Total Backup Connections:     0&lt;/P&gt;&lt;P&gt;  Current Local Connections: 0           Current Backup Connections:   0&lt;/P&gt;&lt;P&gt;  Total Connections:         0           Max Connections:              65534&lt;/P&gt;&lt;P&gt;  Total Reused Conns:        0&lt;/P&gt;&lt;P&gt;  Weight:                    1           Load:                         2&lt;/P&gt;&lt;P&gt;  DFP:                       Disable&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;They are alive as you can see.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;If the service is unavailable I would like to redirect to a sorry server.  My question is this...what would my content rule(s) have to look like in order to accomplish this!  Thanks for the help guys.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;bc&lt;/P&gt;</description>
      <pubDate>Fri, 14 Jan 2005 15:47:05 GMT</pubDate>
      <guid>https://community.cisco.com/t5/application-networking/creating-a-new-content-rule/m-p/384508#M6728</guid>
      <dc:creator>cantorb</dc:creator>
      <dc:date>2005-01-14T15:47:05Z</dc:date>
    </item>
    <item>
      <title>Re: Creating a New Content Rule</title>
      <link>https://community.cisco.com/t5/application-networking/creating-a-new-content-rule/m-p/384509#M6729</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;create a new service for your sorry server.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Then under the content rule defined for http traffic, you add the following line:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;primarySorryServer &lt;SERVICE sorry="" server=""&gt;&lt;/SERVICE&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regarding the config you provided, what you show is a 'show service &lt;NAME&gt;' and we can clearly see that even if your 2 services have different name, they are identical.&lt;/NAME&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I believe you would want to configure different keepalive.&lt;/P&gt;&lt;P&gt;ie: for HTTP&lt;/P&gt;&lt;P&gt;keepalive port 80&lt;/P&gt;&lt;P&gt;keepalive type http&lt;/P&gt;&lt;P&gt;keepalive uri "/"&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;for rtsp&lt;/P&gt;&lt;P&gt;keepalive port 554&lt;/P&gt;&lt;P&gt;keepaliave type tcp&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Gilles.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 17 Jan 2005 14:50:13 GMT</pubDate>
      <guid>https://community.cisco.com/t5/application-networking/creating-a-new-content-rule/m-p/384509#M6729</guid>
      <dc:creator>Gilles Dufour</dc:creator>
      <dc:date>2005-01-17T14:50:13Z</dc:date>
    </item>
  </channel>
</rss>

