Thanks for quick response.

Output is in attached file.

Thanks,

Colin.

all these processes are responsible to handle traffic.

Seems like you have reach some limit.

Get a 'flow stat' from llama mode so we can see amount of connections.

Gilles.

Thanks Giles,

Details are -

chdccss01(debug)# flow statistics

Flow Manager Statistics:

Cur High Avg

UDP Flows per second 22 502 15

TCP Flows per second 42 310 39

Total Flows per second 64 624 55

Hits per second 0 0 0

Number of Allocated Flows (non-purged) 3451

Number of Free Flows 94853

Number of Flow Drops 0

Max Number of Flow Control Blocks 159359

Number of Flows with SynAckPending 83

Accumulated Port Flow Statistics:

Current Number of Active Flows 3474

Total Flow Accounting Reports received 25690664

Total Out of Sequence Packet Received 165

Total Spoof Queue Mis-Hits 0

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

Port CE Active Total Acct TCP UDP Rst FCBs

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

#e1 1f00 2 7 5 2 0 0 15231

#e13 3001f00 1290 12715311 12714022 1027 263 0 26216

#e14 3401f00 0 12125 12121 0 0 0 26195

#e15 3801f00 1296 6241815 6240727 1171 125 0 26211

#e16 3c01f00 886 6722438 6723789 757 137 0 26214

chdccss01(debug)#

Cheers,

Colin

Colin,

that's not that much of flows, but it depends what kind of rules you have.

Any L7 rule ?

Do you have some acl logging ?

Do you have a lot of keepalives ?

I can confirm the processes consuming the cpu are the ones handling the traffic.

So, this box is running at its max.

Gilles.

Gilles,

Thankyou for the information. As a result we looked at the traffic flow in more detail through the CSS and it appears that we have some type of looping FIN/ACK traffic which is generating high volumes of small packets.

When this traffic is blocked the CSS CPU returns to normal (4-5%).

Thankyou for your assistance.

Kind Regards,

Colin.