<?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 ACE probe question in Application Networking</title>
    <link>https://community.cisco.com/t5/application-networking/ace-probe-question/m-p/1192370#M24655</link>
    <description>&lt;P&gt;Team,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Is the ACE module able to probe a specific context for a webpage? What would I need to configure on the probe to search for the following context?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;GET &lt;A class="jive-link-custom" href="https://wil-02.testtnet.com/index.jsp" target="_blank"&gt;https://wil-02.testtnet.com/index.jsp&lt;/A&gt;&lt;/P&gt;&lt;P&gt;Look for â&amp;#128;&amp;#156;windows-password-usernameâ&amp;#128;&amp;#157;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt; The server admins are telling me that when one server is frozen it's not being taken out of the rotation. The current probe is configured as follows:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;probe https https-probe-wilsonvdi&lt;/P&gt;&lt;P&gt;  interval 10&lt;/P&gt;&lt;P&gt;  passdetect interval 3&lt;/P&gt;&lt;P&gt;  request method get url &lt;A class="jive-link-custom" href="https://wilsonvdi" target="_blank"&gt;https://wilsonvdi&lt;/A&gt;&lt;/P&gt;&lt;P&gt;  expect status 200 200&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;John...&lt;/P&gt;</description>
    <pubDate>Wed, 13 May 2009 17:33:24 GMT</pubDate>
    <dc:creator>jteixido</dc:creator>
    <dc:date>2009-05-13T17:33:24Z</dc:date>
    <item>
      <title>ACE probe question</title>
      <link>https://community.cisco.com/t5/application-networking/ace-probe-question/m-p/1192370#M24655</link>
      <description>&lt;P&gt;Team,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Is the ACE module able to probe a specific context for a webpage? What would I need to configure on the probe to search for the following context?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;GET &lt;A class="jive-link-custom" href="https://wil-02.testtnet.com/index.jsp" target="_blank"&gt;https://wil-02.testtnet.com/index.jsp&lt;/A&gt;&lt;/P&gt;&lt;P&gt;Look for â&amp;#128;&amp;#156;windows-password-usernameâ&amp;#128;&amp;#157;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt; The server admins are telling me that when one server is frozen it's not being taken out of the rotation. The current probe is configured as follows:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;probe https https-probe-wilsonvdi&lt;/P&gt;&lt;P&gt;  interval 10&lt;/P&gt;&lt;P&gt;  passdetect interval 3&lt;/P&gt;&lt;P&gt;  request method get url &lt;A class="jive-link-custom" href="https://wilsonvdi" target="_blank"&gt;https://wilsonvdi&lt;/A&gt;&lt;/P&gt;&lt;P&gt;  expect status 200 200&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;John...&lt;/P&gt;</description>
      <pubDate>Wed, 13 May 2009 17:33:24 GMT</pubDate>
      <guid>https://community.cisco.com/t5/application-networking/ace-probe-question/m-p/1192370#M24655</guid>
      <dc:creator>jteixido</dc:creator>
      <dc:date>2009-05-13T17:33:24Z</dc:date>
    </item>
    <item>
      <title>Re: ACE probe question</title>
      <link>https://community.cisco.com/t5/application-networking/ace-probe-question/m-p/1192371#M24656</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi John,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;An HTTPS probe is similar to an HTTP probe except that it uses SSL to generate encrypted data. HTTPS probes are hardware assisted, which causes the ACE to send them from the data plane instead of the control plane. This feature causes the ACE to use the routing table (which may bypass the real server IP address) to direct HTTPS probes to their destination regardless of whether you specify the routed option or not in the ip address command.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Also, ACLs may impact HTTPS probes if you apply them incorrectly.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The server response must include the Content-Length header for the expect regex or hash command to function. Otherwise, the probe does not attempt to parse the regex or hash value. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The version in the ClientHello message sent to the server indicates the highest supported version. By default, the probe supports all as the SSL version. You can configure the version of SSL that the probe supports by using the ssl version command in probe HTTPS configuration mode. The syntax of this command is as follows: &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;ssl version all | SSLv3 | TLSv1 &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The keywords are as follows: &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;â&amp;#128;¢all-(Default) Specifies all SSL versions. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;â&amp;#128;¢SSLv3-Specifies SSL version 3. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;â&amp;#128;¢TLSv1-Specifies TLS version 1. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;By default, the HTTPS probe accepts any of the RSA configured cipher suites. You can configure the probe to expect a specific type of RSA cipher suite from the back-end server by using the ssl cipher command.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Kindly sent the out of the 'show probe detail' &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;So that I can see what is the expec status is returned.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Please reply back to troubleshoot this for you.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Kind Regards,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Sachin Garg&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>Wed, 13 May 2009 18:33:00 GMT</pubDate>
      <guid>https://community.cisco.com/t5/application-networking/ace-probe-question/m-p/1192371#M24656</guid>
      <dc:creator>sachinga.hcl</dc:creator>
      <dc:date>2009-05-13T18:33:00Z</dc:date>
    </item>
    <item>
      <title>Re: ACE probe question</title>
      <link>https://community.cisco.com/t5/application-networking/ace-probe-question/m-p/1192372#M24657</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt; probe       : https-probe-wilsonvdi&lt;/P&gt;&lt;P&gt; type        : HTTPS&lt;/P&gt;&lt;P&gt; state       : ACTIVE&lt;/P&gt;&lt;P&gt; description :&lt;/P&gt;&lt;P&gt;----------------------------------------------&lt;/P&gt;&lt;P&gt;   port      : 443     address     : 0.0.0.0         addr type  : -&lt;/P&gt;&lt;P&gt;   interval  : 10      pass intvl  : 3               pass count : 3&lt;/P&gt;&lt;P&gt;   fail count: 3       recv timeout: 10&lt;/P&gt;&lt;P&gt;   http method      : GET&lt;/P&gt;&lt;P&gt;   http url         : &lt;A class="jive-link-custom" href="https://wilsonvdi" target="_blank"&gt;https://wilsonvdi&lt;/A&gt;&lt;/P&gt;&lt;P&gt;   conn termination : GRACEFUL&lt;/P&gt;&lt;P&gt;   expect offset    : 0         , open timeout     : 10&lt;/P&gt;&lt;P&gt;   expect regex     : -&lt;/P&gt;&lt;P&gt;   send data        : -&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 13 May 2009 19:40:54 GMT</pubDate>
      <guid>https://community.cisco.com/t5/application-networking/ace-probe-question/m-p/1192372#M24657</guid>
      <dc:creator>jteixido</dc:creator>
      <dc:date>2009-05-13T19:40:54Z</dc:date>
    </item>
    <item>
      <title>Re: ACE probe question</title>
      <link>https://community.cisco.com/t5/application-networking/ace-probe-question/m-p/1192373#M24658</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi John,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Can you try to add connection term forced  in your probe config as  By default, the ACE terminates a TCP connection gracefully by sending a FIN to the server. To configure the ACE to terminate a TCP connection by sending a RST, use the connection term command.This command applies only to TCP-based probes.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Also add the &lt;A class="jive-link-custom" href="https://wil-02.testtnet.com/index.jsp" target="_blank"&gt;https://wil-02.testtnet.com/index.jsp&lt;/A&gt;  to your request method not &lt;A class="jive-link-custom" href="https://wilsonvdi" target="_blank"&gt;https://wilsonvdi&lt;/A&gt; &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;So your probe look like this after addition and chages ,as follows:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;probe https https-probe-wilsonvdi &lt;/P&gt;&lt;P&gt;interval 10 &lt;/P&gt;&lt;P&gt;passdetect interval 3 &lt;/P&gt;&lt;P&gt;request method get url &lt;A class="jive-link-custom" href="https://wil-02.testtnet.com/index.jsp" target="_blank"&gt;https://wil-02.testtnet.com/index.jsp&lt;/A&gt; &lt;/P&gt;&lt;P&gt;expect status 200 200 &lt;/P&gt;&lt;P&gt;connection term forced&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Add the correct url(for probe testing page) for get method. Because DNS will not resolve it. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Kindly go throught this url for a lot more:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;A class="jive-link-custom" href="http://docwiki.cisco.com/wiki/Cisco_Application_Control_Engine_" target="_blank"&gt;http://docwiki.cisco.com/wiki/Cisco_Application_Control_Engine_&lt;/A&gt;(ACE)_Module_Troubleshooting_Guide,_Release_A2(x)_--_Troubleshooting_ACE_Health_Monitoring&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;A class="jive-link-custom" href="http://docwiki.cisco.com/wiki/Cisco_ACE_4700_Series_Appliance_Quick_Start_Guide,_Release_A3" target="_blank"&gt;http://docwiki.cisco.com/wiki/Cisco_ACE_4700_Series_Appliance_Quick_Start_Guide,_Release_A3&lt;/A&gt;(1.0)_--_Configuring_Health_Monitoring_Using_Health_Probes&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;P&gt;Kindly add your inputs on this.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;If it works then please rate.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Kind Regards,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Sachin Garg&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 14 May 2009 21:38:16 GMT</pubDate>
      <guid>https://community.cisco.com/t5/application-networking/ace-probe-question/m-p/1192373#M24658</guid>
      <dc:creator>sachinga.hcl</dc:creator>
      <dc:date>2009-05-14T21:38:16Z</dc:date>
    </item>
    <item>
      <title>Re: ACE probe question</title>
      <link>https://community.cisco.com/t5/application-networking/ace-probe-question/m-p/1192374#M24659</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Kindly add &lt;A class="jive-link-custom" href="http://" target="_blank"&gt;http://&lt;/A&gt; to the websites mentioned below &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;docwiki.cisco.com/wiki/Cisco_Application_Control_Engine_(ACE)_Module_Troubleshooting_Guide,_Release_A2(x)_--_Troubleshooting_ACE_Health_Monitoring&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;docwiki.cisco.com/wiki/Cisco_ACE_4700_Series_Appliance_Quick_Start_Guide%2C_Release_A3%281.0%29_--_Configuring_Health_Monitoring_Using_Health_Probes&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;and then paste there to the IExplorer.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Tell me if it works then.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Sachin Garg&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>Thu, 14 May 2009 21:59:26 GMT</pubDate>
      <guid>https://community.cisco.com/t5/application-networking/ace-probe-question/m-p/1192374#M24659</guid>
      <dc:creator>sachinga.hcl</dc:creator>
      <dc:date>2009-05-14T21:59:26Z</dc:date>
    </item>
  </channel>
</rss>

