<?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 Local Director stops sending HTTP probe packets in Application Networking</title>
    <link>https://community.cisco.com/t5/application-networking/local-director-stops-sending-http-probe-packets/m-p/262086#M3830</link>
    <description>&lt;P&gt;I have Local Director 417 with 4.2.5. It has several virtual machines configured on it. Each machine is bound to group of real machines. However real machines for some of virtual groups are hosted on same group of boxes (on different ports of course). E.g.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;virtual 10.1.1.1:80&lt;/P&gt;&lt;P&gt;reals: 10.10.1.1:80, 10.10.1.2:80, 10.10.1.3:80&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;virtual 10.1.1.1:443&lt;/P&gt;&lt;P&gt;reals: 10.10.1.1:443, 10.10.1.2:443, 10.10.1.3:443&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;virtual 10.1.1.2:80&lt;/P&gt;&lt;P&gt;reals: 10.10.1.1:8082, 10.10.1.2:8082, 10.10.1.3:8082&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;virtual 10.1.1.2:443&lt;/P&gt;&lt;P&gt;reals: 10.10.1.1:444, 10.10.1.2:444, 10.10.1.3:444&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Similar setup can be found in the 'Multiple Virtual Servers and Multiple Real Servers' part of the configuration guide.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I have HTTP probes configured on the Local Director. However with some periodicity the LD stops sending the probes to one of real machines, randomly choosen (e.g. 10.10.1.1:8082), although the probes to other real machines, including ones hosted on same box are still being sent (so the probes to 10.10.1.1:80, 10.10.1.1:443 and 10.10.1.1:444 are still sent). We used network analyzer to observe the traffic and that's the way we found out the probes are not sent. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;As a result the server "abandoned" by the LD is declared EFAILED after several "unsuccessful" attempts.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The 'restart' command does not help. I did not try to reboot the LD (I think it should help but I am not interested in this kind of solution). Sometimes it seems to be helpful when entire web server box troubled stays disconnected from the network for some time, but not always yet.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I already have TAC Case opened on this issue but may be someone here also could help with this issue.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;</description>
    <pubDate>Thu, 11 Mar 2004 20:21:09 GMT</pubDate>
    <dc:creator>pvladimirov</dc:creator>
    <dc:date>2004-03-11T20:21:09Z</dc:date>
    <item>
      <title>Local Director stops sending HTTP probe packets</title>
      <link>https://community.cisco.com/t5/application-networking/local-director-stops-sending-http-probe-packets/m-p/262086#M3830</link>
      <description>&lt;P&gt;I have Local Director 417 with 4.2.5. It has several virtual machines configured on it. Each machine is bound to group of real machines. However real machines for some of virtual groups are hosted on same group of boxes (on different ports of course). E.g.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;virtual 10.1.1.1:80&lt;/P&gt;&lt;P&gt;reals: 10.10.1.1:80, 10.10.1.2:80, 10.10.1.3:80&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;virtual 10.1.1.1:443&lt;/P&gt;&lt;P&gt;reals: 10.10.1.1:443, 10.10.1.2:443, 10.10.1.3:443&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;virtual 10.1.1.2:80&lt;/P&gt;&lt;P&gt;reals: 10.10.1.1:8082, 10.10.1.2:8082, 10.10.1.3:8082&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;virtual 10.1.1.2:443&lt;/P&gt;&lt;P&gt;reals: 10.10.1.1:444, 10.10.1.2:444, 10.10.1.3:444&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Similar setup can be found in the 'Multiple Virtual Servers and Multiple Real Servers' part of the configuration guide.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I have HTTP probes configured on the Local Director. However with some periodicity the LD stops sending the probes to one of real machines, randomly choosen (e.g. 10.10.1.1:8082), although the probes to other real machines, including ones hosted on same box are still being sent (so the probes to 10.10.1.1:80, 10.10.1.1:443 and 10.10.1.1:444 are still sent). We used network analyzer to observe the traffic and that's the way we found out the probes are not sent. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;As a result the server "abandoned" by the LD is declared EFAILED after several "unsuccessful" attempts.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The 'restart' command does not help. I did not try to reboot the LD (I think it should help but I am not interested in this kind of solution). Sometimes it seems to be helpful when entire web server box troubled stays disconnected from the network for some time, but not always yet.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I already have TAC Case opened on this issue but may be someone here also could help with this issue.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;</description>
      <pubDate>Thu, 11 Mar 2004 20:21:09 GMT</pubDate>
      <guid>https://community.cisco.com/t5/application-networking/local-director-stops-sending-http-probe-packets/m-p/262086#M3830</guid>
      <dc:creator>pvladimirov</dc:creator>
      <dc:date>2004-03-11T20:21:09Z</dc:date>
    </item>
    <item>
      <title>Re: Local Director stops sending HTTP probe packets</title>
      <link>https://community.cisco.com/t5/application-networking/local-director-stops-sending-http-probe-packets/m-p/262087#M3831</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Sorry, there is one mistake. There is no SSL probe support of course. So of course probes to 10.10.1.1:443 and 10.10.1.1:444 are not sent, only to 10.10.1.1:80.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I should not use SSL ports at all in the example.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 11 Mar 2004 20:44:24 GMT</pubDate>
      <guid>https://community.cisco.com/t5/application-networking/local-director-stops-sending-http-probe-packets/m-p/262087#M3831</guid>
      <dc:creator>pvladimirov</dc:creator>
      <dc:date>2004-03-11T20:44:24Z</dc:date>
    </item>
    <item>
      <title>Re: Local Director stops sending HTTP probe packets</title>
      <link>https://community.cisco.com/t5/application-networking/local-director-stops-sending-http-probe-packets/m-p/262088#M3832</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Can you paste in your probe commands so I can take a look at it?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;-steve&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 11 Mar 2004 21:49:22 GMT</pubDate>
      <guid>https://community.cisco.com/t5/application-networking/local-director-stops-sending-http-probe-packets/m-p/262088#M3832</guid>
      <dc:creator>stevehall</dc:creator>
      <dc:date>2004-03-11T21:49:22Z</dc:date>
    </item>
    <item>
      <title>Re: Local Director stops sending HTTP probe packets</title>
      <link>https://community.cisco.com/t5/application-networking/local-director-stops-sending-http-probe-packets/m-p/262089#M3833</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Thank you for response. This is bind and probe config:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;bind 10.1.1.54:443:0:tcp 10.1.1.20:443:0:tcp&lt;/P&gt;&lt;P&gt;bind 10.1.1.54:443:0:tcp 10.1.1.19:443:0:tcp&lt;/P&gt;&lt;P&gt;bind 10.1.1.53:443:0:tcp 10.1.1.18:443:0:tcp&lt;/P&gt;&lt;P&gt;bind 10.1.1.53:443:0:tcp 10.1.1.17:443:0:tcp&lt;/P&gt;&lt;P&gt;bind 10.1.1.52:443:0:tcp 10.1.1.16:443:0:tcp&lt;/P&gt;&lt;P&gt;bind 10.1.1.52:443:0:tcp 10.1.1.15:443:0:tcp&lt;/P&gt;&lt;P&gt;bind 10.1.1.51:443:0:tcp 10.1.1.14:443:0:tcp&lt;/P&gt;&lt;P&gt;bind 10.1.1.51:443:0:tcp 10.1.1.13:443:0:tcp&lt;/P&gt;&lt;P&gt;bind 10.1.1.51:443:0:tcp 10.1.1.12:443:0:tcp&lt;/P&gt;&lt;P&gt;bind 10.1.1.51:443:0:tcp 10.1.1.11:443:0:tcp&lt;/P&gt;&lt;P&gt;bind 10.1.1.54:80:0:tcp 10.1.1.20:8004:0:tcp&lt;/P&gt;&lt;P&gt;bind 10.1.1.54:80:0:tcp 10.1.1.19:8004:0:tcp&lt;/P&gt;&lt;P&gt;bind 10.1.1.53:80:0:tcp 10.1.1.18:8003:0:tcp&lt;/P&gt;&lt;P&gt;bind 10.1.1.53:80:0:tcp 10.1.1.17:8003:0:tcp&lt;/P&gt;&lt;P&gt;bind 10.1.1.52:80:0:tcp 10.1.1.16:8002:0:tcp&lt;/P&gt;&lt;P&gt;bind 10.1.1.52:80:0:tcp 10.1.1.15:8002:0:tcp&lt;/P&gt;&lt;P&gt;bind 10.1.1.51:80:0:tcp 10.1.1.14:8001:0:tcp&lt;/P&gt;&lt;P&gt;bind 10.1.1.51:80:0:tcp 10.1.1.13:8001:0:tcp&lt;/P&gt;&lt;P&gt;bind 10.1.1.51:80:0:tcp 10.1.1.12:8001:0:tcp&lt;/P&gt;&lt;P&gt;bind 10.1.1.51:80:0:tcp 10.1.1.11:8001:0:tcp&lt;/P&gt;&lt;P&gt;bind 10.1.1.55:80:0:tcp 10.1.1.11:8081:0:tcp&lt;/P&gt;&lt;P&gt;bind 10.1.1.55:80:0:tcp 10.1.1.12:8081:0:tcp&lt;/P&gt;&lt;P&gt;bind 10.1.1.55:80:0:tcp 10.1.1.13:8081:0:tcp&lt;/P&gt;&lt;P&gt;bind 10.1.1.55:80:0:tcp 10.1.1.14:8081:0:tcp&lt;/P&gt;&lt;P&gt;bind 10.1.1.56:80:0:tcp 10.1.1.15:8082:0:tcp&lt;/P&gt;&lt;P&gt;bind 10.1.1.56:80:0:tcp 10.1.1.16:8082:0:tcp&lt;/P&gt;&lt;P&gt;bind 10.1.1.58:80:0:tcp 10.1.1.19:8084:0:tcp&lt;/P&gt;&lt;P&gt;bind 10.1.1.58:80:0:tcp 10.1.1.20:8084:0:tcp&lt;/P&gt;&lt;P&gt;bind 10.1.1.55:443:0:tcp 10.1.1.11:543:0:tcp&lt;/P&gt;&lt;P&gt;bind 10.1.1.55:443:0:tcp 10.1.1.12:543:0:tcp&lt;/P&gt;&lt;P&gt;bind 10.1.1.55:443:0:tcp 10.1.1.13:543:0:tcp&lt;/P&gt;&lt;P&gt;bind 10.1.1.55:443:0:tcp 10.1.1.14:543:0:tcp&lt;/P&gt;&lt;P&gt;bind 10.1.1.56:443:0:tcp 10.1.1.15:543:0:tcp&lt;/P&gt;&lt;P&gt;bind 10.1.1.56:443:0:tcp 10.1.1.16:543:0:tcp&lt;/P&gt;&lt;P&gt;bind 10.1.1.58:443:0:tcp 10.1.1.19:543:0:tcp&lt;/P&gt;&lt;P&gt;bind 10.1.1.58:443:0:tcp 10.1.1.20:543:0:tcp&lt;/P&gt;&lt;P&gt;probe virtual 10.1.1.54:80:0:tcp http 30&lt;/P&gt;&lt;P&gt;probe virtual 10.1.1.53:80:0:tcp http 30&lt;/P&gt;&lt;P&gt;probe virtual 10.1.1.52:80:0:tcp http 30&lt;/P&gt;&lt;P&gt;probe virtual 10.1.1.51:80:0:tcp http 30&lt;/P&gt;&lt;P&gt;probe virtual 10.1.1.55:80:0:tcp http 30&lt;/P&gt;&lt;P&gt;probe virtual 10.1.1.56:80:0:tcp http 30&lt;/P&gt;&lt;P&gt;probe virtual 10.1.1.58:80:0:tcp http 30&lt;/P&gt;&lt;P&gt;probe real 10.1.1.18:8003:0:tcp http 30&lt;/P&gt;&lt;P&gt;probe real 10.1.1.17:8003:0:tcp http 30&lt;/P&gt;&lt;P&gt;probe real 10.1.1.16:8002:0:tcp http 30&lt;/P&gt;&lt;P&gt;probe real 10.1.1.15:8002:0:tcp http 30&lt;/P&gt;&lt;P&gt;probe real 10.1.1.14:8001:0:tcp http 30&lt;/P&gt;&lt;P&gt;probe real 10.1.1.13:8001:0:tcp http 30&lt;/P&gt;&lt;P&gt;probe real 10.1.1.12:8001:0:tcp http 30&lt;/P&gt;&lt;P&gt;probe real 10.1.1.11:8001:0:tcp http 30&lt;/P&gt;&lt;P&gt;probe real 10.1.1.20:8004:0:tcp http 30&lt;/P&gt;&lt;P&gt;probe real 10.1.1.19:8004:0:tcp http 30&lt;/P&gt;&lt;P&gt;probe real 10.1.1.11:8081:0:tcp http 30&lt;/P&gt;&lt;P&gt;probe real 10.1.1.12:8081:0:tcp http 30&lt;/P&gt;&lt;P&gt;probe real 10.1.1.13:8081:0:tcp http 30&lt;/P&gt;&lt;P&gt;probe real 10.1.1.14:8081:0:tcp http 30&lt;/P&gt;&lt;P&gt;probe real 10.1.1.15:8082:0:tcp http 30&lt;/P&gt;&lt;P&gt;probe real 10.1.1.16:8082:0:tcp http 30&lt;/P&gt;&lt;P&gt;probe real 10.1.1.19:8084:0:tcp http 30&lt;/P&gt;&lt;P&gt;probe real 10.1.1.20:8084:0:tcp http 30&lt;/P&gt;&lt;P&gt;probehttp virtual 10.1.1.54:80:0:tcp file /probe&lt;/P&gt;&lt;P&gt;probehttp virtual 10.1.1.53:80:0:tcp file /probe&lt;/P&gt;&lt;P&gt;probehttp virtual 10.1.1.52:80:0:tcp file /probe&lt;/P&gt;&lt;P&gt;probehttp virtual 10.1.1.51:80:0:tcp file /probe&lt;/P&gt;&lt;P&gt;probehttp virtual 10.1.1.55:80:0:tcp file /probe&lt;/P&gt;&lt;P&gt;probehttp virtual 10.1.1.56:80:0:tcp file /probe&lt;/P&gt;&lt;P&gt;probehttp virtual 10.1.1.58:80:0:tcp file /probe&lt;/P&gt;&lt;P&gt;probehttp real 10.1.1.18:8003:0:tcp file /probe&lt;/P&gt;&lt;P&gt;probehttp real 10.1.1.17:8003:0:tcp file /probe&lt;/P&gt;&lt;P&gt;probehttp real 10.1.1.16:8002:0:tcp file /probe&lt;/P&gt;&lt;P&gt;probehttp real 10.1.1.15:8002:0:tcp file /probe&lt;/P&gt;&lt;P&gt;probehttp real 10.1.1.14:8001:0:tcp file /probe&lt;/P&gt;&lt;P&gt;probehttp real 10.1.1.13:8001:0:tcp file /probe&lt;/P&gt;&lt;P&gt;probehttp real 10.1.1.12:8001:0:tcp file /probe&lt;/P&gt;&lt;P&gt;probehttp real 10.1.1.11:8001:0:tcp file /probe&lt;/P&gt;&lt;P&gt;probehttp real 10.1.1.20:8004:0:tcp file /probe&lt;/P&gt;&lt;P&gt;probehttp real 10.1.1.19:8004:0:tcp file /probe&lt;/P&gt;&lt;P&gt;probehttp real 10.1.1.11:8081:0:tcp file /probe&lt;/P&gt;&lt;P&gt;probehttp real 10.1.1.12:8081:0:tcp file /probe&lt;/P&gt;&lt;P&gt;probehttp real 10.1.1.13:8081:0:tcp file /probe&lt;/P&gt;&lt;P&gt;probehttp real 10.1.1.14:8081:0:tcp file /probe&lt;/P&gt;&lt;P&gt;probehttp real 10.1.1.15:8082:0:tcp file /probe&lt;/P&gt;&lt;P&gt;probehttp real 10.1.1.16:8082:0:tcp file /probe&lt;/P&gt;&lt;P&gt;probehttp real 10.1.1.19:8084:0:tcp file /probe&lt;/P&gt;&lt;P&gt;probehttp real 10.1.1.20:8084:0:tcp file /probe&lt;/P&gt;&lt;P&gt;probeconfig http 3&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 11 Mar 2004 23:33:07 GMT</pubDate>
      <guid>https://community.cisco.com/t5/application-networking/local-director-stops-sending-http-probe-packets/m-p/262089#M3833</guid>
      <dc:creator>pvladimirov</dc:creator>
      <dc:date>2004-03-11T23:33:07Z</dc:date>
    </item>
    <item>
      <title>Re: Local Director stops sending HTTP probe packets</title>
      <link>https://community.cisco.com/t5/application-networking/local-director-stops-sending-http-probe-packets/m-p/262090#M3834</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;TAC finally said it is the bug CSCed84569 found in 4.2.5. Not open to general public yet otherwise I would find it myself. In case of emergency they recommended downgrade to 4.2.4.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;It took them two weeks just to find it out... Sad.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Sat, 13 Mar 2004 02:59:03 GMT</pubDate>
      <guid>https://community.cisco.com/t5/application-networking/local-director-stops-sending-http-probe-packets/m-p/262090#M3834</guid>
      <dc:creator>pvladimirov</dc:creator>
      <dc:date>2004-03-13T02:59:03Z</dc:date>
    </item>
  </channel>
</rss>

