×

Warning message

  • Cisco Support Forums is in Read Only mode while the site is being migrated.
  • Cisco Support Forums is in Read Only mode while the site is being migrated.

Service down due to keepalive

Unanswered Question
Apr 24th, 2006
User Badges:

How to resolve service down event together with informing client this has happened possibly with TCP reset sending from CSS to client?

We have ordinary configuration with two real servers and two content rules for http (L5) and https (L4). When service is dying and is already down, CSS still have flow information in its table. Client who is connected to this service is hanging up waiting for application to time out. New connections are sent to the other live service as expected. Is there a way for CSS to notify client that this has happened, let say via TCP reset packet?

This could be done with "flow-reset-reject" command on content rule, but it is not functioning like expected.


Regards,

Branko

  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 0 (0 ratings)
Loading.
Gilles Dufour Wed, 04/26/2006 - 06:14
User Badges:
  • Cisco Employee,

Branko,


you have identified the right command 'flow-reset-reject' but it does work with arp table only [not status of keepalive].

There is unfortunately no other existing solution.


Gilles

Actions

This Discussion