Buy or Renew
Buy or Renew
cancel
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for 
Search instead for 
Did you mean: 
cancel
Start a conversation
982
Views
0
Helpful
4
Replies

Local Director stops sending HTTP probe packets

pvladimirov
Level 1
Level 1

‎03-11-2004 12:21 PM

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.

virtual 10.1.1.1:80

reals: 10.10.1.1:80, 10.10.1.2:80, 10.10.1.3:80

virtual 10.1.1.1:443

reals: 10.10.1.1:443, 10.10.1.2:443, 10.10.1.3:443

virtual 10.1.1.2:80

reals: 10.10.1.1:8082, 10.10.1.2:8082, 10.10.1.3:8082

virtual 10.1.1.2:443

reals: 10.10.1.1:444, 10.10.1.2:444, 10.10.1.3:444

Similar setup can be found in the 'Multiple Virtual Servers and Multiple Real Servers' part of the configuration guide.

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.

As a result the server "abandoned" by the LD is declared EFAILED after several "unsuccessful" attempts.

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.

I already have TAC Case opened on this issue but may be someone here also could help with this issue.

Labels:
0 Helpful
4 Replies 4

pvladimirov
Level 1
Level 1

‎03-11-2004 12:44 PM

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.

I should not use SSL ports at all in the example.

0 Helpful

stevehall
Level 1
Level 1
In response to pvladimirov

‎03-11-2004 01:49 PM

Can you paste in your probe commands so I can take a look at it?

-steve

0 Helpful

pvladimirov
Level 1
Level 1
In response to stevehall

‎03-11-2004 03:33 PM

Thank you for response. This is bind and probe config:

bind 10.1.1.54:443:0:tcp 10.1.1.20:443:0:tcp

bind 10.1.1.54:443:0:tcp 10.1.1.19:443:0:tcp

bind 10.1.1.53:443:0:tcp 10.1.1.18:443:0:tcp

bind 10.1.1.53:443:0:tcp 10.1.1.17:443:0:tcp

bind 10.1.1.52:443:0:tcp 10.1.1.16:443:0:tcp

bind 10.1.1.52:443:0:tcp 10.1.1.15:443:0:tcp

bind 10.1.1.51:443:0:tcp 10.1.1.14:443:0:tcp

bind 10.1.1.51:443:0:tcp 10.1.1.13:443:0:tcp

bind 10.1.1.51:443:0:tcp 10.1.1.12:443:0:tcp

bind 10.1.1.51:443:0:tcp 10.1.1.11:443:0:tcp

bind 10.1.1.54:80:0:tcp 10.1.1.20:8004:0:tcp

bind 10.1.1.54:80:0:tcp 10.1.1.19:8004:0:tcp

bind 10.1.1.53:80:0:tcp 10.1.1.18:8003:0:tcp

bind 10.1.1.53:80:0:tcp 10.1.1.17:8003:0:tcp

bind 10.1.1.52:80:0:tcp 10.1.1.16:8002:0:tcp

bind 10.1.1.52:80:0:tcp 10.1.1.15:8002:0:tcp

bind 10.1.1.51:80:0:tcp 10.1.1.14:8001:0:tcp

bind 10.1.1.51:80:0:tcp 10.1.1.13:8001:0:tcp

bind 10.1.1.51:80:0:tcp 10.1.1.12:8001:0:tcp

bind 10.1.1.51:80:0:tcp 10.1.1.11:8001:0:tcp

bind 10.1.1.55:80:0:tcp 10.1.1.11:8081:0:tcp

bind 10.1.1.55:80:0:tcp 10.1.1.12:8081:0:tcp

bind 10.1.1.55:80:0:tcp 10.1.1.13:8081:0:tcp

bind 10.1.1.55:80:0:tcp 10.1.1.14:8081:0:tcp

bind 10.1.1.56:80:0:tcp 10.1.1.15:8082:0:tcp

bind 10.1.1.56:80:0:tcp 10.1.1.16:8082:0:tcp

bind 10.1.1.58:80:0:tcp 10.1.1.19:8084:0:tcp

bind 10.1.1.58:80:0:tcp 10.1.1.20:8084:0:tcp

bind 10.1.1.55:443:0:tcp 10.1.1.11:543:0:tcp

bind 10.1.1.55:443:0:tcp 10.1.1.12:543:0:tcp

bind 10.1.1.55:443:0:tcp 10.1.1.13:543:0:tcp

bind 10.1.1.55:443:0:tcp 10.1.1.14:543:0:tcp

bind 10.1.1.56:443:0:tcp 10.1.1.15:543:0:tcp

bind 10.1.1.56:443:0:tcp 10.1.1.16:543:0:tcp

bind 10.1.1.58:443:0:tcp 10.1.1.19:543:0:tcp

bind 10.1.1.58:443:0:tcp 10.1.1.20:543:0:tcp

probe virtual 10.1.1.54:80:0:tcp http 30

probe virtual 10.1.1.53:80:0:tcp http 30

probe virtual 10.1.1.52:80:0:tcp http 30

probe virtual 10.1.1.51:80:0:tcp http 30

probe virtual 10.1.1.55:80:0:tcp http 30

probe virtual 10.1.1.56:80:0:tcp http 30

probe virtual 10.1.1.58:80:0:tcp http 30

probe real 10.1.1.18:8003:0:tcp http 30

probe real 10.1.1.17:8003:0:tcp http 30

probe real 10.1.1.16:8002:0:tcp http 30

probe real 10.1.1.15:8002:0:tcp http 30

probe real 10.1.1.14:8001:0:tcp http 30

probe real 10.1.1.13:8001:0:tcp http 30

probe real 10.1.1.12:8001:0:tcp http 30

probe real 10.1.1.11:8001:0:tcp http 30

probe real 10.1.1.20:8004:0:tcp http 30

probe real 10.1.1.19:8004:0:tcp http 30

probe real 10.1.1.11:8081:0:tcp http 30

probe real 10.1.1.12:8081:0:tcp http 30

probe real 10.1.1.13:8081:0:tcp http 30

probe real 10.1.1.14:8081:0:tcp http 30

probe real 10.1.1.15:8082:0:tcp http 30

probe real 10.1.1.16:8082:0:tcp http 30

probe real 10.1.1.19:8084:0:tcp http 30

probe real 10.1.1.20:8084:0:tcp http 30

probehttp virtual 10.1.1.54:80:0:tcp file /probe

probehttp virtual 10.1.1.53:80:0:tcp file /probe

probehttp virtual 10.1.1.52:80:0:tcp file /probe

probehttp virtual 10.1.1.51:80:0:tcp file /probe

probehttp virtual 10.1.1.55:80:0:tcp file /probe

probehttp virtual 10.1.1.56:80:0:tcp file /probe

probehttp virtual 10.1.1.58:80:0:tcp file /probe

probehttp real 10.1.1.18:8003:0:tcp file /probe

probehttp real 10.1.1.17:8003:0:tcp file /probe

probehttp real 10.1.1.16:8002:0:tcp file /probe

probehttp real 10.1.1.15:8002:0:tcp file /probe

probehttp real 10.1.1.14:8001:0:tcp file /probe

probehttp real 10.1.1.13:8001:0:tcp file /probe

probehttp real 10.1.1.12:8001:0:tcp file /probe

probehttp real 10.1.1.11:8001:0:tcp file /probe

probehttp real 10.1.1.20:8004:0:tcp file /probe

probehttp real 10.1.1.19:8004:0:tcp file /probe

probehttp real 10.1.1.11:8081:0:tcp file /probe

probehttp real 10.1.1.12:8081:0:tcp file /probe

probehttp real 10.1.1.13:8081:0:tcp file /probe

probehttp real 10.1.1.14:8081:0:tcp file /probe

probehttp real 10.1.1.15:8082:0:tcp file /probe

probehttp real 10.1.1.16:8082:0:tcp file /probe

probehttp real 10.1.1.19:8084:0:tcp file /probe

probehttp real 10.1.1.20:8084:0:tcp file /probe

probeconfig http 3

0 Helpful

pvladimirov
Level 1
Level 1
In response to stevehall

‎03-12-2004 06:59 PM

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.

It took them two weeks just to find it out... Sad.

0 Helpful
Customers Also Viewed These Support Documents

Review Cisco Networking for a $25 gift card