Guest

Preview Tool

Cisco Bug: CSCsy77263 - Slowstart should kick in on transition from PROBE-FAILED to OPERATIONAL

Last Modified

Apr 23, 2010

Products (1)

  • Cisco ACE 4700 Series Application Control Engine Appliances

Known Affected Releases

3.0(0)A3(1.0)

Description (partial)

Symptom:

On a serverfarm configured with predictor leastconns slowstart   (and possibly  failaction purge) a rserver that is in PROBE-FAILED status when becomes OPERATIONAL won't be put on slowstart mode, not even if it has 0 connections (for example due to failaction purge).
The server will be put in slowstart only if an operator will manually do no inservice and inservice

The configuration guide is correct but not explicit about it:
"To ensure that a failed server with existing connections enters slow-start mode when it is placed back in service, configure failaction purge"

The requested enhancement would be to have the rserver enter slowstart mode when becoming OPERATIONAL after PROBE-FAILED/ARP-FAILED status if it has 0 connections

Conditions:
serverfarm configured with <CmdBold>predictor leastconns slowstart <noCmdBold><CmdArg>time<noCmdArg>, rserver going into PROBE-FAILED
Bug details contain sensitive information and therefore require a Cisco.com account to be viewed.

Bug Details Include

  • Full Description (including symptoms, conditions and workarounds)
  • Status
  • Severity
  • Known Fixed Releases
  • Related Community Discussions
  • Number of Related Support Cases
Bug information is viewable for customers and partners who have a service contract. Registered users can view up to 200 bugs per month without a service contract.