CSM serverfarm has reached configured max-conns

Unanswered Question
Feb 27th, 2007

Recently, one of our soon to be deployed serverfarm stopped responding to requests, because it has reached the max-conn limit.

The strange thing is, the serverfarm is usually under very little load.

Here are some dumps of the CLI

CSM01#sh mod csm 7 vservers name ipc2.web.http config

IPC2.WEB.HTTP, type = SLB, state = OPERATIONAL, v_index = 64

virtual = 20.254.127.24/32:81 bidir, TCP, service = NONE, advertise = FALSE

idle = 3600, replicate csrp = connection, vlan = 801, pending = 30, layer 4

max parse len = 2000, persist rebalance = TRUE

ssl sticky offset = 0, length = 32

conns = 1, total conns = 76532

maxconn drops = 0, total drops = 242

Policy <default>

serverfarm IPC2.WEB.HTTP, type = SLB, predictor = Src IP

Description:

nat = SERVER

bind id = 0, fail action = none

inband health config: <none>

retcode map = <none>

Probes:

PORT-80, type = tcp

Real servers:

20.254.52.4:80, weight = 8, OPERATIONAL

20.254.52.6:80, weight = 8, OPERATIONAL

20.254.52.5:80, weight = 8, MAXCONNS

CSM01#sh mod csm 7 server name ipc2.web.http detai

IPC2.WEB.HTTP, type = SLB, predictor = Src IP

Description:

nat = SERVER

virtuals inservice = 2, reals = 3, bind id = 0, fail action = none

inband health config: <none>

retcode map = <none>

Probes:

PORT-80, type = tcp

Real servers:

20.254.52.4:80, weight = 8, OPERATIONAL, conns = 0

20.254.52.6:80, weight = 8, OPERATIONAL, conns = 4294967295

20.254.52.5:80, weight = 8, MAXCONNS, conns = 4294967294

Total connections = 4294967293

CSM01#sh mod csm 7 conns vserver ipc2.web.http detail

prot vlan source destination state

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

As you can see, the counter has maxed out, even thoguh the connections table is blank.

Any help is much appreciated.

Jim

I have this problem too.
0 votes
  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 0 (0 ratings)
Loading.
Gilles Dufour Fri, 03/02/2007 - 00:13

what CSM version ?

Looks like the counter wrapped around. That is, you had 0 connections and for some reason the counter was decremented by one, which gave the huge number of connections.

Definitely a bug, but will need to know the config, the version, and if possible information about the tests that have been done prio to be in this state.

Gilles.

Actions

This Discussion