08-17-2010 08:46 AM
Hi All ,
Please find the below steps and help us to bring up the VIP.
1)We could see the r server status as active but the concerned probes for the rserver showing as failed .
2)Also we are getting the status of the VIP as out of service.
3) We ensured the rservers are responding for the probe (http ).
5) We removed and applied the inservice and tested but it is not coming up .
For your reference I am attaching the configuration what we have done.
A) Configuration
1) probe http DC_MC-ACC-HTTP_PROBE
interval 5
faildetect 2
passdetect interval 2
receive 2
expect status 200 400
open 2
2) TestACE(config)# rserver host DCweb01
TestACE(config-rserver-host)# ip address 10.199.7.222
TestACE(config-rserver-host)# inservice
TestACE(config)# rserver host DCweb02
TestACE(config-rserver-host)# ip address 10.199.7.223
TestACE(config-rserver-host)# inservice
3) TestACE(config)# serverfarm host DC_HTTP_SF_NEW_80
TestACE(config-sfarm-host)# probe DC_MC-ACC-HTTP_PROBE
TestACE(config-sfarm-host)# rserver DCweb01 80
TestACE(config-sfarm-host-rs)# inservice
TestACE(config-sfarm-host)# rserver DCweb02 80
TestACE(config-sfarm-host-rs)# inservice
4) policy-map type loadbalance first-match DC-HTTP-NEW
class class-default
serverfarm DC_HTTP_SF_NEW_80
5) VIP
TestACE(config)# class-map match-any DC_MC-VIP -HTTP
TestACE (config-cmap)# 2 match virtual-address 10.199.7.226 tcp eq 80
6)
policy-map multi-match LB-VIP
class DC_MC-VIP-HTTP
loadbalance vip inservice
loadbalance policy DC-HTTP-NEW
loadbalance vip icmp-reply
7) service-policy input DC_TI-HTTP
B)
TestACE# sh service-policy DC_TI-HTTP class-map DC_MC-VIP-HTTP summary
service-policy: DC_TI-HTTP
Class VIP Prot Port VLAN State Curr Conns Hit Count Conns Drop
DC_MC-VIP-HTTP 10.199.7.226 tcp eq 80 ALL OUT-SRVC 0 80 80
So please suggest us how can I trouble shoot it and bring it up .
Thanks and regards,
Sinjish.K
Solved! Go to Solution.
08-18-2010 07:38 AM
this probe is is sucessful it hasn't failed on this server since jul 19
last response was 302 which falls in teh range so it is good.
what do you see for probe on server that is in the probe_failed state ?
IF you can't share config here you may be better off with a tac case.
08-18-2010 09:23 PM
So Sinjish.K, what exactly your query or problem is now, litrenta
thanks for your explaination.
08-19-2010 12:02 AM
Hey Sinjish, have your post makred Answered to help others. Thanks
08-17-2010 11:47 AM
what do you see for output of
show probe DC_MC-ACC-HTTP_PROBE detail ?
08-17-2010 11:48 AM
also what do you see with
sh service-policy DC_TI-HTTP class-map DC_MC-VIP-HTTP detail
08-17-2010 01:49 PM
Hi ,
The server farm what I have mentioned earlier DC_HTTP_SF_NEW_80 in the given configuration is a typo .
So please take it as DC_HTTP_SF_NEW
The output what I have taken is from direct ACE , if there are any minor change with the given conf please treat the below pasted as right one .
Also we observed in the probe details the serverfarm is not being displayed . So please suggest us do I need to make any more conf apart from the above given conf )
1. TestACE# sh probe DC_MC-ACC-HTTP_PROBE detail
probe : DC_MC-ACC-HTTP_PROBE
type : HTTP
state : ACTIVE
description :
----------------------------------------------
port : 80 address : 0.0.0.0 addr type : -
interval : 5 pass intvl : 2 pass count : 3
fail count: 2 recv timeout: 2
http method : GET
http url : /
conn termination : GRACEFUL
expect offset : 0 , open timeout : 2
expect regex : -
send data : -
--------------------- probe results --------------------
probe association probed-address probes failed passed health
------------------- ---------------+----------+----------+----------+-------
serverfarm : DC_MC-ACC-HTTP
real :DCmctiweb01[80]
10.199.7.164 1343852 250 1343602 SUCCESS
Socket state : CLOSED
No. Passed states : 27 No. Failed states : 26
No. Probes skipped : 33 Last status code : 400
No. Out of Sockets : 0 No. Internal error: 0
Last disconnect err : -
Last probe time : Tue Aug 17 21:32:37 2010
Last fail time : Thu Jul 8 13:10:01 2010
Last active time : Thu Jul 8 13:10:08 2010
real :DCmctiweb02[80]
10.199.7.165 1343841 210 1343631 SUCCESS
Socket state : CLOSED
No. Passed states : 19 No. Failed states : 18
No. Probes skipped : 32 Last status code : 400
No. Out of Sockets : 0 No. Internal error: 0
Last disconnect err : -
Last probe time : Tue Aug 17 21:32:36 2010
Last fail time : Thu Jun 24 09:33:07 2010
Last active time : Thu Jun 24 09:33:14 2010
serverfarm : DC_MC-ACC-HTTPS
real :DCmctiweb01[80]
10.199.7.164 1343852 250 1343602 SUCCESS
Socket state : CLOSED
No. Passed states : 27 No. Failed states : 26
No. Probes skipped : 33 Last status code : 400
No. Out of Sockets : 0 No. Internal error: 0
Last disconnect err : -
Last probe time : Tue Aug 17 21:32:37 2010
Last fail time : Thu Jul 8 13:10:01 2010
Last active time : Thu Jul 8 13:10:08 2010
real :DCmctiweb02[80]
10.199.7.165 1343841 210 1343631 SUCCESS
Socket state : CLOSED
No. Passed states : 19 No. Failed states : 18
No. Probes skipped : 32 Last status code : 400
No. Out of Sockets : 0 No. Internal error: 0
Last disconnect err : -
Last probe time : Tue Aug 17 21:32:36 2010
Last fail time : Thu Jun 24 09:33:07 2010
Last active time : Thu Jun 24 09:33:14 2010
TestACE#
2) TestACE# sh service-policy DC_TI-HTTP class-map DC_MC-VIP-HTTP detail
Status : ACTIVE
Description: -----------------------------------------
Context Global Policy:
service-policy: DC_TI-HTTP
class: DC_MC-VIP-HTTP
VIP Address: Protocol: Port:
10.199.7.226 tcp eq 80
loadbalance:
L7 loadbalance policy: DC-HTTP-NEW
VIP Route Metric : 77
VIP Route Advertise : DISABLED
VIP ICMP Reply : ENABLED
VIP state: OUTOFSERVICE
curr conns : 0 , hit count : 80
dropped conns : 80
client pkt count : 80 , client byte count: 4800
server pkt count : 0 , server byte count: 0
conn-rate-limit : 0 , drop-count : 0
bandwidth-rate-limit : 0 , drop-count : 0
L7 Loadbalance policy : DC-HTTP-NEW
class/match : class-default
LB action: :
primary serverfarm: DC_HTTP_SF_NEW
state: DOWN
backup serverfarm : -
hit count : 0
dropped conns : 0
Here we can ping to the rservers as well can do the telnet to the same with port – 80 ( But the serverfarm state showing as down - also we ensured the inservice command applied early ).
08-17-2010 01:59 PM
can you attach a show tech from the context ?
08-17-2010 11:55 PM
Hi ,
I am very sorry to say no because of some security reason and company policy I could not share the tech support . Probably you can help me by giving any trouble shooting method or by providing any of your findings. Also please let us know if you faced any issues that are similar to what I have given .
Thanks & Regards,
Regards,
Sinjish.K
08-18-2010 01:33 AM
Hi,
Can you paste the output of sh serverfarm DC_HTTP_SF_NEW_80 and make sure they are in "in service" state.
Thanks
08-18-2010 03:44 AM
Please find the output as probe failed in serverfarm . We have already configured probe in the serverfarm .Also the serverfarm showing as INACTIVE. We removed and applied again the inservice but there is no effect . The serverfarm name is DC_HTTP_SF_NEW . There are some changes in names then what i given previously .
Test _ACE1/DC# sh serverfarm DC_HTTP_SF_NEW detail
serverfarm : DC_HTTP_SF_NEW, type: HOST
total rservers : 2
active rservers: 0
description : -
state : INACTIVE
predictor : ROUNDROBIN
failaction : -
back-inservice : 0
partial-threshold : 0
num times failover : 0
num times back inservice : 0
total conn-dropcount : 0
Probe(s) :
HTTP_PROBE, type = HTTP
---------------------------------
----------connections-----------
real weight state current total failures
---+---------------------+------+------------+----------+----------+---------
rserver: xxxxDCmctiweb01
10.199.7.222:80 8 PROBE-FAILED 0 0 0
description : -
max-conns : - , out-of-rotation count : -
min-conns : -
conn-rate-limit : - , out-of-rotation count : -
bandwidth-rate-limit : - , out-of-rotation count : -
retcode out-of-rotation count : -
load value : 0
rserver: xxxxDCmctiweb02
10.199.7.223:80 8 PROBE-FAILED 0 0 0
description : -
max-conns : - , out-of-rotation count : -
min-conns : -
conn-rate-limit : - , out-of-rotation count : -
bandwidth-rate-limit : - , out-of-rotation count : -
retcode out-of-rotation count : -
load value : 0
08-18-2010 04:54 AM
without more data it is hard to say. IF the probe is failing then we need to see what gets returned on the probe. IF you are doing an http probe that is failing but van telent to the server on port 80 then the possibilities are:
server is returning something outside the range of response codes (404 for example).
or
Server responds but does not send a fin. normally
ace sends get or head and sends fin then server sends response and sends fin.
if server does not send fin probe will fail. a packet capture on server will reveal this.
If this is the case then you should configure another probe for this farm with the same parameters but with the addition of "connection term forced"
08-18-2010 05:49 AM
Hi ,
Thanks for your support .
I have removed the existing probe and created a simple probe with the below configuration .
probe tcp HTTP_TEST
interval 4
passdetect interval 10
passdetect count 4
Now it is working fine . Also the VIP turned as inservice .
So also please let me know what I need to do on server side to enable the below probe .
probe http HTTP_PROBE
interval 5
faildetect 2
passdetect interval 2
receive 2
expect status 200 302
open 2
I could not find the command - connection term forced in the serverfarm mode . Also please let me know what is the use of - expext status 200 302 .
Regards,
Sinjish.K
08-18-2010 06:00 AM
connection term forced goes under probe config not serverfarm config
expect status 200 302 means that server http response needs to be in the range of 200-302
when you configure the probe and then apply to serverfarm you need to do
show probe HTTP_PROBE detail
to get a clue as to how server is responding.
08-18-2010 07:27 AM
Hi ,
Please find the below output and please suggest us how can i know the server responding in which value for setting the " expect value " in probe .
Is it the last status code in the below output ?
Test/DC# sh probe HTTP_PROBE detail
probe : HTTP_PROBE
type : HTTP
state : ACTIVE
description :
----------------------------------------------
port : 80 address : 0.0.0.0 addr type : -
interval : 5 pass intvl : 2 pass count : 3
fail count: 2 recv timeout: 2
http method : GET
http url : /
conn termination : GRACEFUL
expect offset : 0 , open timeout : 2
expect regex : -
send data : -
--------------------- probe results --------------------
probe association probed-address probes failed passed health
------------------- ---------------+----------+----------+----------+-------
serverfarm : DC_PRODUCTION
real : XXXDCWEB01[80]
10.199.7.196 1357262 1518 1355744 SUCCESS
Socket state : CLOSED
No. Passed states : 112 No. Failed states : 111
No. Probes skipped : 894 Last status code : 302
No. Out of Sockets : 0 No. Internal error: 0
Last disconnect err : -
Last probe time : Wed Aug 18 15:58:53 2010
Last fail time : Mon Jul 19 01:24:54 2010
Last active time : Mon Jul 19 01:25:01 2010
In this case the expect value in probe is 200 and 302.
Regards ,
Sinjish.K
08-18-2010 07:38 AM
this probe is is sucessful it hasn't failed on this server since jul 19
last response was 302 which falls in teh range so it is good.
what do you see for probe on server that is in the probe_failed state ?
IF you can't share config here you may be better off with a tac case.
08-18-2010 09:23 PM
So Sinjish.K, what exactly your query or problem is now, litrenta
thanks for your explaination.
08-18-2010 10:56 PM
Hi EphraimMani,
My problem solved after i applied the proble without the expect value .
Thanks everyone and Litrenta for your help and support .
Regards,
Sinjish.K
Find answers to your questions by entering keywords or phrases in the Search bar above. New here? Use these resources to familiarize yourself with the community: