<?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 Status-Tracking on ACE in Application Networking</title>
    <link>https://community.cisco.com/t5/application-networking/status-tracking-on-ace/m-p/1523003#M31313</link>
    <description>&lt;P&gt;Hello&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;On the CSM there was a feature called status tracking, it's description:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;TABLE border="1" cellpadding="3" cellspacing="0" class="steptable" id="wp1042914table1042910" width="80%"&gt;&lt;TBODY&gt;&lt;TR align="left" valign="top"&gt;&lt;SPAN class="content"&gt;&lt;/SPAN&gt;&lt;TD&gt;&lt;DIV class="pEx1_Example1"&gt;&lt;PRE&gt;Router(config-module-csm)#&lt;SPAN style="color: black; font-style: normal; font-weight: bold;"&gt; &lt;/SPAN&gt;&lt;STRONG class="cCN_CmdName" style="font-weight: bold;"&gt;vserver&lt;/STRONG&gt;&lt;SPAN style="color: black; font-style: normal; font-weight: bold;"&gt; &lt;BR /&gt;&lt;/SPAN&gt;&lt;EM class="cArgument" style="font-weight: normal;"&gt;dependent_virtserver_name&lt;BR /&gt;&lt;/EM&gt;&lt;/PRE&gt;&lt;/DIV&gt;&lt;/TD&gt;&lt;TD&gt;&lt;A name="wp1042922"&gt;&lt;/A&gt;&lt;P class="pB1_Body1"&gt;Identifies the dependent virtual server and enters the virtual server configuration mode.&lt;/P&gt;&lt;/TD&gt;&lt;/TR&gt;&lt;/TBODY&gt;&lt;/TABLE&gt;&lt;TABLE border="1" cellpadding="3" cellspacing="0" class="steptable" id="wp1042914table1042910" width="80%"&gt;&lt;TBODY&gt;&lt;TR align="left" valign="top"&gt;&lt;SPAN class="content"&gt;&lt;/SPAN&gt;&lt;TD&gt;&lt;DIV class="pEx1_Example1"&gt;&lt;PRE&gt;Router(config-slb-vserver)#&lt;SPAN style="color: black; font-style: normal; font-weight: bold;"&gt; &lt;BR /&gt;&lt;/SPAN&gt;&lt;STRONG class="cCN_CmdName"&gt;virtual&lt;/STRONG&gt;&lt;SPAN style="color: black; font-style: normal; font-weight: bold;"&gt; &lt;/SPAN&gt;&lt;EM class="cArgument" style="font-style: oblique; font-weight: normal;"&gt;ip-address&lt;/EM&gt; [&lt;EM class="cArgument"&gt;ip-mask&lt;/EM&gt;]&lt;EM class="cEmphasis"&gt; &lt;BR /&gt;&lt;/EM&gt;&lt;EM class="cArgument"&gt;protocol port-number&lt;/EM&gt; [&lt;STRONG class="cKeyword"&gt;service&lt;/STRONG&gt; {&lt;STRONG class="cKeyword"&gt;ftp&lt;/STRONG&gt;&lt;STRONG class="cBold"&gt; &lt;BR /&gt;&lt;/STRONG&gt;| &lt;STRONG class="cKeyword"&gt;rtsp&lt;/STRONG&gt; | &lt;STRONG class="cKeyword"&gt;termination&lt;/STRONG&gt;}] &lt;BR /&gt;&lt;/PRE&gt;&lt;/DIV&gt;&lt;/TD&gt;&lt;TD&gt;&lt;A name="wp1042934"&gt;&lt;/A&gt;&lt;P class="pB1_Body1"&gt;Sets the IP address for the dependent virtual server optional port number or name and the connection coupling and type&lt;A href="http://www.cisco.com/en/US/docs/interfaces_modules/services_modules/csm/4.2.x/configuration/guide/mapolcy.html#wp1047232"&gt;&lt;SUP class="cSuperscript" style="vertical-align: super;"&gt;2&lt;/SUP&gt;&lt;/A&gt;. The &lt;EM class="cArgument"&gt;protocol&lt;/EM&gt; value is &lt;STRONG class="cBold"&gt;tcp&lt;/STRONG&gt;, &lt;STRONG class="cBold"&gt;udp&lt;/STRONG&gt;, &lt;STRONG class="cBold"&gt;any&lt;/STRONG&gt; (no port number is required), or a &lt;EM class="cArgument"&gt;number&lt;/EM&gt; value (no port number is required).&lt;/P&gt;&lt;/TD&gt;&lt;/TR&gt;&lt;/TBODY&gt;&lt;/TABLE&gt;&lt;TABLE border="1" cellpadding="3" cellspacing="0" class="steptable" id="wp1042914table1042910" width="80%"&gt;&lt;TBODY&gt;&lt;TR align="left" valign="top"&gt;&lt;SPAN class="content"&gt;&lt;/SPAN&gt;&lt;TD&gt;&lt;DIV class="pEx1_Example1"&gt;&lt;PRE&gt;Router(config-slb-vserver)#&lt;SPAN style="color: black; font-style: normal; font-weight: bold;"&gt; &lt;BR /&gt;&lt;/SPAN&gt;&lt;STRONG class="cCN_CmdName" style="font-weight: bold;"&gt;status-tracking&lt;/STRONG&gt;&lt;SPAN style="color: black; font-style: normal; font-weight: bold;"&gt; &lt;BR /&gt;&lt;/SPAN&gt;&lt;EM class="cArgument" style="font-weight: normal;"&gt;tracked_virtserver_name&lt;BR /&gt;&lt;/EM&gt;&lt;/PRE&gt;&lt;/DIV&gt;&lt;/TD&gt;&lt;TD&gt;&lt;A name="wp1042943"&gt;&lt;/A&gt;&lt;P class="pB1_Body1"&gt;Identifies the tracked virtual server. When this virtual server is taken out of service or fails, the dependent virtual server identified in Step 1 is automatically taken out of service.&lt;/P&gt;&lt;/TD&gt;&lt;/TR&gt;&lt;/TBODY&gt;&lt;/TABLE&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;From &lt;/SPAN&gt;&lt;A class="jive-link-external-small" href="http://www.cisco.com/en/US/docs/interfaces_modules/services_modules/csm/4.2.x/configuration/guide/mapolcy.html"&gt;http://www.cisco.com/en/US/docs/interfaces_modules/services_modules/csm/4.2.x/configuration/guide/mapolcy.html&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I am wondering if anyone knows of a similar feature in ACE?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The additional complexity is now the dependant vserver and tracked vserver are in different ACE contexts, does anybody know if there is way to track vservers in a different context?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Got to admit I'm relatively new to ACE but hope this makes sense.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks for any replies in advance&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Martin&lt;/P&gt;</description>
    <pubDate>Tue, 26 Oct 2010 16:39:07 GMT</pubDate>
    <dc:creator>martin.foote</dc:creator>
    <dc:date>2010-10-26T16:39:07Z</dc:date>
    <item>
      <title>Status-Tracking on ACE</title>
      <link>https://community.cisco.com/t5/application-networking/status-tracking-on-ace/m-p/1523003#M31313</link>
      <description>&lt;P&gt;Hello&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;On the CSM there was a feature called status tracking, it's description:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;TABLE border="1" cellpadding="3" cellspacing="0" class="steptable" id="wp1042914table1042910" width="80%"&gt;&lt;TBODY&gt;&lt;TR align="left" valign="top"&gt;&lt;SPAN class="content"&gt;&lt;/SPAN&gt;&lt;TD&gt;&lt;DIV class="pEx1_Example1"&gt;&lt;PRE&gt;Router(config-module-csm)#&lt;SPAN style="color: black; font-style: normal; font-weight: bold;"&gt; &lt;/SPAN&gt;&lt;STRONG class="cCN_CmdName" style="font-weight: bold;"&gt;vserver&lt;/STRONG&gt;&lt;SPAN style="color: black; font-style: normal; font-weight: bold;"&gt; &lt;BR /&gt;&lt;/SPAN&gt;&lt;EM class="cArgument" style="font-weight: normal;"&gt;dependent_virtserver_name&lt;BR /&gt;&lt;/EM&gt;&lt;/PRE&gt;&lt;/DIV&gt;&lt;/TD&gt;&lt;TD&gt;&lt;A name="wp1042922"&gt;&lt;/A&gt;&lt;P class="pB1_Body1"&gt;Identifies the dependent virtual server and enters the virtual server configuration mode.&lt;/P&gt;&lt;/TD&gt;&lt;/TR&gt;&lt;/TBODY&gt;&lt;/TABLE&gt;&lt;TABLE border="1" cellpadding="3" cellspacing="0" class="steptable" id="wp1042914table1042910" width="80%"&gt;&lt;TBODY&gt;&lt;TR align="left" valign="top"&gt;&lt;SPAN class="content"&gt;&lt;/SPAN&gt;&lt;TD&gt;&lt;DIV class="pEx1_Example1"&gt;&lt;PRE&gt;Router(config-slb-vserver)#&lt;SPAN style="color: black; font-style: normal; font-weight: bold;"&gt; &lt;BR /&gt;&lt;/SPAN&gt;&lt;STRONG class="cCN_CmdName"&gt;virtual&lt;/STRONG&gt;&lt;SPAN style="color: black; font-style: normal; font-weight: bold;"&gt; &lt;/SPAN&gt;&lt;EM class="cArgument" style="font-style: oblique; font-weight: normal;"&gt;ip-address&lt;/EM&gt; [&lt;EM class="cArgument"&gt;ip-mask&lt;/EM&gt;]&lt;EM class="cEmphasis"&gt; &lt;BR /&gt;&lt;/EM&gt;&lt;EM class="cArgument"&gt;protocol port-number&lt;/EM&gt; [&lt;STRONG class="cKeyword"&gt;service&lt;/STRONG&gt; {&lt;STRONG class="cKeyword"&gt;ftp&lt;/STRONG&gt;&lt;STRONG class="cBold"&gt; &lt;BR /&gt;&lt;/STRONG&gt;| &lt;STRONG class="cKeyword"&gt;rtsp&lt;/STRONG&gt; | &lt;STRONG class="cKeyword"&gt;termination&lt;/STRONG&gt;}] &lt;BR /&gt;&lt;/PRE&gt;&lt;/DIV&gt;&lt;/TD&gt;&lt;TD&gt;&lt;A name="wp1042934"&gt;&lt;/A&gt;&lt;P class="pB1_Body1"&gt;Sets the IP address for the dependent virtual server optional port number or name and the connection coupling and type&lt;A href="http://www.cisco.com/en/US/docs/interfaces_modules/services_modules/csm/4.2.x/configuration/guide/mapolcy.html#wp1047232"&gt;&lt;SUP class="cSuperscript" style="vertical-align: super;"&gt;2&lt;/SUP&gt;&lt;/A&gt;. The &lt;EM class="cArgument"&gt;protocol&lt;/EM&gt; value is &lt;STRONG class="cBold"&gt;tcp&lt;/STRONG&gt;, &lt;STRONG class="cBold"&gt;udp&lt;/STRONG&gt;, &lt;STRONG class="cBold"&gt;any&lt;/STRONG&gt; (no port number is required), or a &lt;EM class="cArgument"&gt;number&lt;/EM&gt; value (no port number is required).&lt;/P&gt;&lt;/TD&gt;&lt;/TR&gt;&lt;/TBODY&gt;&lt;/TABLE&gt;&lt;TABLE border="1" cellpadding="3" cellspacing="0" class="steptable" id="wp1042914table1042910" width="80%"&gt;&lt;TBODY&gt;&lt;TR align="left" valign="top"&gt;&lt;SPAN class="content"&gt;&lt;/SPAN&gt;&lt;TD&gt;&lt;DIV class="pEx1_Example1"&gt;&lt;PRE&gt;Router(config-slb-vserver)#&lt;SPAN style="color: black; font-style: normal; font-weight: bold;"&gt; &lt;BR /&gt;&lt;/SPAN&gt;&lt;STRONG class="cCN_CmdName" style="font-weight: bold;"&gt;status-tracking&lt;/STRONG&gt;&lt;SPAN style="color: black; font-style: normal; font-weight: bold;"&gt; &lt;BR /&gt;&lt;/SPAN&gt;&lt;EM class="cArgument" style="font-weight: normal;"&gt;tracked_virtserver_name&lt;BR /&gt;&lt;/EM&gt;&lt;/PRE&gt;&lt;/DIV&gt;&lt;/TD&gt;&lt;TD&gt;&lt;A name="wp1042943"&gt;&lt;/A&gt;&lt;P class="pB1_Body1"&gt;Identifies the tracked virtual server. When this virtual server is taken out of service or fails, the dependent virtual server identified in Step 1 is automatically taken out of service.&lt;/P&gt;&lt;/TD&gt;&lt;/TR&gt;&lt;/TBODY&gt;&lt;/TABLE&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;From &lt;/SPAN&gt;&lt;A class="jive-link-external-small" href="http://www.cisco.com/en/US/docs/interfaces_modules/services_modules/csm/4.2.x/configuration/guide/mapolcy.html"&gt;http://www.cisco.com/en/US/docs/interfaces_modules/services_modules/csm/4.2.x/configuration/guide/mapolcy.html&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I am wondering if anyone knows of a similar feature in ACE?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The additional complexity is now the dependant vserver and tracked vserver are in different ACE contexts, does anybody know if there is way to track vservers in a different context?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Got to admit I'm relatively new to ACE but hope this makes sense.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks for any replies in advance&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Martin&lt;/P&gt;</description>
      <pubDate>Tue, 26 Oct 2010 16:39:07 GMT</pubDate>
      <guid>https://community.cisco.com/t5/application-networking/status-tracking-on-ace/m-p/1523003#M31313</guid>
      <dc:creator>martin.foote</dc:creator>
      <dc:date>2010-10-26T16:39:07Z</dc:date>
    </item>
    <item>
      <title>Re: Status-Tracking on ACE</title>
      <link>https://community.cisco.com/t5/application-networking/status-tracking-on-ace/m-p/1523004#M31314</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Martin,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;I've never used the CSM platform myself, but I think what you're looking for, is a PROBE.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Basically, a probe is a set of parameters, that can be applied to any of your configured serverfarms and can "track" the status of the underlying real-server, using a variety of protocols, e.g. icmp, tcp, http etc.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Try and have a look at this and see, if it's what you're looking for:&lt;/P&gt;&lt;P&gt;&lt;A class="jive-link-external-small" href="http://www.cisco.com/en/US/docs/interfaces_modules/services_modules/ace/vA2_3_0/command/reference/probe.html"&gt;http://www.cisco.com/en/US/docs/interfaces_modules/services_modules/ace/vA2_3_0/command/reference/probe.html&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;hth&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;/Ulrich&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 26 Oct 2010 19:54:09 GMT</pubDate>
      <guid>https://community.cisco.com/t5/application-networking/status-tracking-on-ace/m-p/1523004#M31314</guid>
      <dc:creator>UHansen1976</dc:creator>
      <dc:date>2010-10-26T19:54:09Z</dc:date>
    </item>
    <item>
      <title>Re: Status-Tracking on ACE</title>
      <link>https://community.cisco.com/t5/application-networking/status-tracking-on-ace/m-p/1523005#M31315</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;&lt;SPAN style="font-family: arial,helvetica,sans-serif;"&gt;Hi &lt;SPAN style="font-size: 11pt; sans-serif&amp;quot;: ; font-family: &amp;quot; ,&amp;quot;: ; Calibri&amp;quot;: ; "&gt;Ulrich&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks for the reply. I'm not sure I was clear on my question, the PROBE would allow me to check the first service is up. What I want to do is make the internal server unavalaible if the external is not PROBING correctly or vice versa. I recognise now this is not identical to status-tracking which operates at a VIP level.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;In an example I have two FTP servers which are dual homed with internal and external interfaces in a DMZ both of which are load balanced using the ACE. If the external interface goes down I would want the internal real server to be marked out of service so as FTP traffic is no longer sent there and vice versa if the internal went down I would want to mark the external as down. The configuration in this case is there are different contexts for the internal and external - not saying that's ideal from a security perspective but you can only play with the cards your dealt!.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks&lt;/P&gt;&lt;P&gt;Martin&lt;!--[if gte mso 10]&gt;
&lt;style&gt;
 /* Style Definitions */
 table.MsoNormalTable
	{mso-style-name:"Table Normal";
	mso-tstyle-rowband-size:0;
	mso-tstyle-colband-size:0;
	mso-style-noshow:yes;
	mso-style-priority:99;
	mso-style-qformat:yes;
	mso-style-parent:"";
	mso-padding-alt:0cm 5.4pt 0cm 5.4pt;
	mso-para-margin:0cm;
	mso-para-margin-bottom:.0001pt;
	mso-pagination:widow-orphan;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";
	mso-ascii-font-family:Calibri;
	mso-ascii-theme-font:minor-latin;
	mso-fareast-font-family:"Times New Roman";
	mso-fareast-theme-font:minor-fareast;
	mso-hansi-font-family:Calibri;
	mso-hansi-theme-font:minor-latin;}
&lt;/style&gt;
&lt;![endif]--&gt;&lt;!--[if gte mso 10]&gt;
&lt;style&gt;
 /* Style Definitions */
 table.MsoNormalTable
	{mso-style-name:"Table Normal";
	mso-tstyle-rowband-size:0;
	mso-tstyle-colband-size:0;
	mso-style-noshow:yes;
	mso-style-priority:99;
	mso-style-qformat:yes;
	mso-style-parent:"";
	mso-padding-alt:0cm 5.4pt 0cm 5.4pt;
	mso-para-margin:0cm;
	mso-para-margin-bottom:.0001pt;
	mso-pagination:widow-orphan;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";
	mso-ascii-font-family:Calibri;
	mso-ascii-theme-font:minor-latin;
	mso-fareast-font-family:"Times New Roman";
	mso-fareast-theme-font:minor-fareast;
	mso-hansi-font-family:Calibri;
	mso-hansi-theme-font:minor-latin;}
&lt;/style&gt;
&lt;![endif]--&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 27 Oct 2010 10:20:48 GMT</pubDate>
      <guid>https://community.cisco.com/t5/application-networking/status-tracking-on-ace/m-p/1523005#M31315</guid>
      <dc:creator>martin.foote</dc:creator>
      <dc:date>2010-10-27T10:20:48Z</dc:date>
    </item>
  </channel>
</rss>

