CIFS accelerator keepalive failure

[Bedevere Curry]

Software Release 4.4.5

WAVE-294-K9

Alert:

cceAlarmHistModuleId= 1000  cceAlarmHistCategory= 3  cceAlarmHistInfo= Raise-Alarm: CIFS accelerator keepalive failure.   cceAlarmHistTimeStamp= 3539553200

I got the following alert.

Does anyone know where I can find the log files or the CIFs accelerator keepalive failure counter?

I wanted to know the best way to clear the counter statistics and make sure that if this hits up again I can at least get a better

idea of how frequent it is happening.

I ran the following command and was curious if the "sessions timeout" is related to this keepalive failure?

show statistics accelerator cifs detail

CIFS:

Global Statistics

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

Time Accelerator was started: Wed Sep 25 08:51:51 2013

Time Statistics were Last Reset/Cleared: Wed Sep 25 08:51:51 2013

Total Handled Connections: 15293

Total Optimized Connections: 166

Total Connections Handed-off with Compression Policies Unchanged: 13638

Total Dropped Connections: 0

Current Active Connections: 0

Current Pending Connections: 0

Maximum Active Connections: 9

Number of local reply generating requests: 166596

Number of remote reply generating requests: 217438

The Average time to generate a local reply (msec): 4

Average time to receive remote reply (ms): 92

Policy Engine Statistics

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

Session timeouts: 13, Total timeouts: 121

Last keepalive received 00.0 Secs ago

Last registration occurred 19:03:18:36.6 Days:Hours:Mins:Secs ago

Hits: 1218122, Update Released: 142074

Active Connections: 18, Completed Connections: 821832

Drops: 0, Pre-Resource Counter: 0

Rejected Connection Counts Due To: (Total: 254198)

Not Registered : 3, Keepalive Timeout : 65

No License : 0, Load Level : 0

Connection Limit : 0, Rate Limit : 0

Minimum TFO : 254130, Resource Manager : 0

Global Config : 0, TFO Limit : 0

Server-Side : 0, DM Deny : 0

No DM Accept : 0

Auto-Discovery Statistics

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

Total Connections queued for accept: 487511

Connections queuing failures: 0

Socket pairs queued for accept: 487511

Socket pairs queuing failures: 0

AO discovery successful: 741192

AO discovery failure: 6

[Kanwaljeet Singh]

Hi,

The accelerator is failing to perform a wellness update within the allotted time. That is
why we see keepalive failures. The implications are that some connections may not be
getting optimized properly by the AO, and thus optimization performance may be reduced.
 
I don't think there is any counter for number of keep alive failure messages you get but you can 
 see if Keepalive Timeout counter is increasing.
 
 You can find this counter under "policy engine statistics".
 
 Keepalive Timeout : 65--->You can check if this value is increasing during the time you get this message.
 
 
 Regards,
 Kanwal