HTTP probe getting failed .

Unanswered Question
Aug 18th, 2010
User Badges:

Hi  ,

Please find the below probe configuration   of  probe and  the probe failed  out put of  t he server farm

But the same probe is  operational for some  other serverfarm . 

Also  we can telnet to the server  with  port number  80 . So please tell us if we need any other criteria to be met for configuring the  probe  .

Here the serverfarm status also  showing as INACTIVE .So we are suspecting this is because of the probe failure .

Test/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: DCmctiweb01

       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: DCmctiweb02

       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

2)) Probe  Configuration

probe http DC_MC-ACC-HTTP_PROBE

  interval 5

  faildetect 2

  passdetect interval 2

  receive 2

  expect status 200 400

  open 2

Regards ,

Sinjish.K

  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 0 (0 ratings)
Loading.
yushimaz Wed, 08/18/2010 - 01:31
User Badges:
  • Cisco Employee,

Do you configure 'HTTP_PROBE' and apply this probe to DC_HTTP_SF_NEW?

When I configure 'DC_MC-ACC-HTTP_PROBE' probe and apply it to serverfarm,

show serverfarm output is as below.




ACE20/Admin# sh serverfarm detail

serverfarm     : sf, 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 : 10

total conn-dropcount : 0

Probe(s) :

    DC_MC-ACC-HTTP_PROBE,  type = HTTP  <<==



Your output was 'HTTP_PROBE'. So, I guess you configure 'HTTP_PROBE' and apply to DC_HTTP_SF_NEW, not 'DC_MC-ACC-HTTP_PROBE'.

I couldn't see DCweb01(10.199.7.222) and Cweb02(10.199.7.223) in show probe detail output in previous discussion. Normally, we can see them.

https://supportforums.cisco.com/thread/2037302


If you configure 'HTTP_PROBE', please check 'show probe HTTP_PROBE detail'?

I checked above behavior with A2(3.1). Even If you configure probe and apply it to serverfarm correctly, please let me know your version?


Regards,

Yuji

k_sinjish Wed, 08/18/2010 - 03:57
User Badges:

HI ,

I have  configured the  probe with the correct serverfarm only .The hostname change might be a typo.

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

Test _ACE1/DC # sh serverfarm DC_HTTP_SF_NEW

serverfarm     : DC_HTTP_SF_NEW, type: HOST

total rservers : 2

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

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

       real                  weight state        current    total      failures

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

   rserver: xxxDCctiweb01

       10.199.7.222:80       8      PROBE-FAILED 0          0          0

   rserver: xxxDCctiweb02

       10.199.7.223:80       8      PROBE-FAILED 0          0          0

Also please find the  device details .

Software

  loader:    Version 12.2[120]

  system:    Version A2(3.0) [build 3.0(0)A2(3.0)]

  system image file: [LCP] disk0:c6ace-t1k9-mz.A2_3_0.bin

  installed license: ACE-VIRT-020 ACE-VIRT-UP1 ACE-VIRT-UP2

Please suggest me what will be the reasons for getting the probe failed.Also from the ACE I can telnet to the server with port number 80 . (The probe is also HTTP)

Regards ,

Sinjish.K

yushimaz Wed, 08/18/2010 - 08:57
User Badges:
  • Cisco Employee,

I want to make clear whether probe status goes FAILED or not.

So, please get 'show probe detail | b 10.199.7.222' and 'show probe detail | b 10.199.7.223'.

If these probe are SUCCESS, please get 'show probe detail | i FAILED' and 'sh run serverfarm | b DC_HTTP_SF_NEW'.

k_sinjish Thu, 08/19/2010 - 05:34
User Badges:

Hi ,

After trying with  another probe without expect value the probe has turned up .And I got update  from net pro as we need t o  apply  - connection term forced   in the  probe configuration if we are not sure , what ( response) value  being returned from server .

Thanks everyone .

Regards ,

Sinjish.K

Actions

This Discussion