ACE : Connection failures counter

Unanswered Question
Nov 16th, 2009

Hi,

In the command show serverfarm :

CH01AC03/P-115-A# sh serverfarm NCL_FARM_PROD

serverfarm : NCL_FARM_PROD, type: HOST

total rservers : 6

---------------------------------

----------connections-----------

real weight state current total failures

---+---------------------+------+------------+----------+----------+---------

rserver: HQBUUN203

10.56.7.209:443 8 OPERATIONAL 16 130388 15

rserver: HQBUUN205

10.56.7.210:443 8 OPERATIONAL 10 130392 10

rserver: HQBUUN221

10.56.7.94:443 8 OPERATIONAL 9 130383 19

rserver: HQBUUN222

10.56.7.93:443 8 OPERATIONAL 7 130391 12

rserver: HQVEUN218

10.56.7.96:443 8 OPERATIONAL 13 130390 13

rserver: HQVEUN219

10.56.7.95:443 8 OPERATIONAL 9 130389 14

What does the connections failures field mean ? Is it the number of time the ACE did not receive a SYN-ACK packet within a time window after having sent a SYN ? If it is true, what is the timeout value and can I modify it ?

Thank you

Yves Haemmerli

I have this problem too.
0 votes
  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 0 (0 ratings)
Loading.
Gilles Dufour Mon, 11/16/2009 - 06:46

Yves,

the timeout is the embryonic timeout and it can be configured within a parameter-map.

Other reason for this counter to increment is if the rserver responds with a RST.

We have also seen bugs where the client sending a RST results in this counter to increment.

If you can, verify with a sniffer trace in what condition you are before changing the embryonic timeout.

Gilles.

Actions

This Discussion