05-20-2013 02:14 AM
Hello
Instruction:
CONN WEB server farm online sh
Failure occurs on a particular server. The cause of the failure?
sh serverfarm WEB
serverfarm : WEB, type: HOST
total rservers : 3
---------------------------------
----------connections-----------
real weight state current total failures
---+---------------------+------+------------+----------+----------+---------
rserver: WEB1
172.32.20.11:80 8 OUTOFSERVICE 22 0 0
rserver: WEB2
172.32.20.14:80 8 OPERATIONAL 37 859 0
rserver: WEB3
172.32.20.17:80 8 OPERATIONAL 60 1168 21
There is no result to failure of the probe.
Software
loader: Version 12.2[120]
system: Version A2(3.2a) [build 3.0(0)A2(3.2a)]
Thank you.
05-20-2013 06:15 AM
Hi,
The failure counter here could increment due to a couple reasons. One is that a SYN timeout occurs and the connection is unable to be established. A second reason is that the ACE received a RST. Another reason could be a internal exception. Typically, a packet capture would be leveraged to determine what is actually occurring during the connection lifetime that would cause the ACE to increment the "failure" counter.
-Alex
05-20-2013 09:23 PM
Hi Gyoun,
Are these failures increasing constantly ? Was there a probe failure? Can you check what is the last diconnect err shown when you do show probe
Regards,
Kanwal
05-21-2013 02:51 AM
Thank you for answer.
Has now continued failure occurs. Is there to be resolved method to SYN timeout occurrence at the time?
The ace is the problem? The problem is the server?
inside_l4# sh probe 80 detail
probe : 80
type : TCP
state : ACTIVE
description :
----------------------------------------------
port : 80 address : 0.0.0.0 addr type : -
interval : 2 pass intvl : 2 pass count : 5
fail count: 2 recv timeout: 2
conn termination : FORCED
expect offset : 0 , open timeout : 10
expect regex : -
send data : -
--------------------- probe results --------------------
probe association probed-address probes failed passed health
------------------- ---------------+----------+----------+----------+-------
serverfarm : WEB
real : WEB1[80]
172.32.20.11 0 0 0 DISABLED
Socket state :
No. Passed states : 0 No. Failed states : 0
No. Probes skipped : 0 Last status code : 0
No. Out of Sockets : 0 No. Internal error: 0
Last disconnect err : -
Last probe time : Never
Last fail time : Never
Last active time : Never
real : WEB2[80]
172.32.20.14 46499 0 46499 SUCCESS
Socket state : CLOSED
No. Passed states : 1 No. Failed states : 0
No. Probes skipped : 0 Last status code : 0
No. Out of Sockets : 0 No. Internal error: 0
Last disconnect err : -
Last probe time : Tue May 21 18:42:58 2013
Last fail time : Never
Last active time : Mon May 20 16:46:57 2013
real : WEB3[80]
172.32.20.17 45704 0 45704 SUCCESS
Socket state : CLOSED
No. Passed states : 1 No. Failed states : 0
No. Probes skipped : 0 Last status code : 0
No. Out of Sockets : 0 No. Internal error: 0
Last disconnect err : -
Last probe time : Tue May 21 18:42:57 2013
Last fail time : Never
Last active time : Mon May 20 17:13:32 2013
serverfarm : WEB_EDI
real : WEB4[80]
172.32.20.21 972749 3 972746 SUCCESS
Socket state : CLOSED
No. Passed states : 1 No. Failed states : 0
No. Probes skipped : 1 Last status code : 0
No. Out of Sockets : 0 No. Internal error: 0
Last disconnect err : -
Last probe time : Tue May 21 18:42:58 2013
Last fail time : Never
Last active time : Mon Apr 29 04:17:06 2013
real : WEB5[80]
172.32.20.24 972746 2 972744 SUCCESS
Socket state : CLOSED
No. Passed states : 1 No. Failed states : 0
No. Probes skipped : 4 Last status code : 0
No. Out of Sockets : 0 No. Internal error: 0
Last disconnect err : -
Last probe time : Tue May 21 18:42:58 2013
Last fail time : Never
Last active time : Mon Apr 29 04:17:06 2013
============================================================
inside_l4# sh serverfarm WEB
serverfarm : WEB, type: HOST
total rservers : 3
---------------------------------
----------connections-----------
real weight state current total failures
---+---------------------+------+------------+----------+----------+---------
rserver: WEB1
172.32.20.11:80 8 OUTOFSERVICE 0 0 0
rserver: WEB2
172.32.20.14:80 8 OPERATIONAL 28 55085 622
rserver: WEB3
172.32.20.17:80 8 OPERATIONAL 5 44150 414
MINISTOP/inside_l4#
05-21-2013 06:09 AM
Hi,
From your output Web1, 2, and 3 have not failed any probes. To determine what is actually occuring, gather a simultatneous packet capture on the ACE and on the server while the issue is occurring. You want to make sure that the failure counter is incrementing when the capture is taken. Another way to focus in would be to determine what, if any, symptoms the client sees while the issuing is occurring. This could help you to hone in on where to look. Once you get the captures, anaylze them to find the problem traffic and determine the cause.
Regards,
Alex
05-26-2013 09:40 PM
hi
Normalization Results confirm
MINISTOP/inside_l4# show np 1 me-stats "-s norm"
Normalization Statistics: (Current)
------------------------
[Drops] TCP invalid conn miss flags: 283038 0
TCP no of cleared options: 4 0
[Drops] TCP non-syn options on syn: 7 0
[Drops] fp TCP RST has wrong ack: 1 0
(Context 3 Statistics)
[Drops] fp TCP normalization: 283042 0
[Drops] TCP invalid conn miss flags
increase in count
Phenomenon occurs, what is the problem?
Thank you
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide