What are the CIFS file and session Limits?

johnlburns · ‎06-24-2010

I have two 7341s (different sites) that fan out to a number of 502s (~100), and a few 612 & 674

Each of the 7341s will periodically report the following in the syslog:

java: %WAAS-CMS-4-723008: ce(DataFeedPoll): Exited badly `runExecCLI snmp trigger create esCifsOpenFiles.0 60 greater-than absolute 4500 \"More than 4500 currently opened files\"' 1

java: %WAAS-CMS-4-713003: ce(DataFeedPoll): CLI command failed : failed `snmp trigger create esCifsOpenFiles.0 60 greater-than absolute 4500 \"More than 4500 currently opened files\"'

java: %WAAS-CMS-4-723008: ce(DataFeedPoll): Exited badly `runExecCLI snmp trigger create esConnectedSessionCount.0 120 greater-than absolute 2295 \"More than 2295 sessions (~users) are currently connected\
' 1

java: %WAAS-CMS-4-713003: ce(DataFeedPoll): CLI command failed : failed `snmp trigger create esConnectedSessionCount.0 120 greater-than absolute 2295 \"More than 2295 sessions (~users) are currently connect
ed\"'

This would seem to indicate that there are cifs limitations above and beyond the TFO limitations on each device. If so, what are the limits, and how does the WAE respond when the limit is reached?

corpitsol · ‎06-25-2010

Receiving the same errors on our WAAS box; Very interested in what this means and the impact to end-users/sites;

2010 Jun 9 20:13:10 WAASCOLO1 java: %WAAS-CMS-4-723008: ce(DataFeedPoll): Exite
d badly `runExecCLI snmp trigger create esCifsOpenFiles.0 60 greater-than absolu
te 4500 \"More than 4500 currently opened files\"' 1

2010 Jun 9 20:13:12 WAASCOLO1 java: %WAAS-CMS-4-723008: ce(DataFeedPoll): Exite
d badly `runExecCLI snmp trigger create esConnectedSessionCount.0 120 greater-th
an absolute 2295 \"More than 2295 sessions (~users) are currently connected\"' 1

Zach Seils · ‎06-25-2010

The maximum number of CIFS sessions supported is equal to the lesser of the maximum number of TCP connections ans 32,000.

For the maximum number of concurrent open files, there is a per-box and a per-user limit. You can check them from the WAAS CLI:

Box Limit: sh stat acc cifs expert RxCIFS MaxRxOpenFiles
User Limit: sh stat acc cifs expert RxCIFS MaxUserOpenFiles

When either one of these limits is reached, the connection is handled as pass-through.

Regards,

Zach

corpitsol · ‎06-25-2010

I checked this on our WAAS headend running oe574-4.1.7.11, which the case with all of our customer units (Wave 274) as well. I'm a bit confused here however.

Output of those commands:

| Type | int
| Access | RW

|| Value | 512

We can see that the SNMP trigger on open files is 4500 and now these lower values shown. Is this limit global for our entire head-end or a limit for each WAVE device we attach? Trying to boil this down and determine the impact/root cause of the alert shown above.

Zach Seils · ‎06-25-2010

Sounds like the trigger amounts aren't being adjusted for the platform limits. The error message you are seeing is because the command to implement the trigger is failing.

Are you running 4.1(7) on all the devices where you are seeing this error?

Zach

johnlburns · ‎06-28-2010

For my case both 7341s are running 4.1.5f

#sh stat acc cifs expert RxCIFS MaxUserOpenFiles

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

| Name | MaxUserOpenFiles |

| Type | int |

| Access | RW |

| Value | 512 |

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

#sh stat acc cifs expert RxCIFS MaxRxOpenFiles

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

| Name | MaxRxOpenFiles |

| Type | int |

| Access | RW |

| Value | 24000 |

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

Similar case on a 612 4.1.5f

%WAAS-CMS-4-713003: ce(DataFeedPoll): CLI command failed : failed `snmp trigger create esCifsOpenFiles.0 60 greater-than absolute 4500 \"More than 4500 currently opened files\"'
%WAAS-CMS-4-723008: ce(DataFeedPoll): Exited badly `runExecCLI snmp trigger create esConnectedSessionCount.0 120 greater-than absolute 2250 \"More than 2250 sessions (~users) are currently connected\"' 1

corpitsol · ‎06-28-2010

Zach,

All versions are 4.1.7.11 on the main head-end (WAVE-574-K9) and the attached Wave-274 devices.

These errors are coming from some of the main syslog files on the device.

Thanks,

Matthew

Zach Seils · ‎06-28-2010

I think this is a bug with the SNMP triggers. Let me dig some more into this.

Zach

corpitsol · ‎07-01-2010

Zach,

Does this error indicate an actual threshhold is being exceeded? I'm trying to understand how it relates to any possible performance issues, or if it is purely a SNMP thing.

We just upgraded all of our devices to the latest 4.2.x platform, didn't see it in the changelog though.

Zach Seils · ‎07-01-2010

No. It means that the command used to configure the SNMP trigger failing. It does not indicate that the threshold has been exceeded.

Zach