Is there any way to monitor and alert on pblock utilization via DFM or another monitoring tool? We had an issue recently where CIFS operations ground to a halt that was not resolved until we disabled fpolicy. We believe the entire pblock pool wound up in use and CIFS operations ground to a halt.
We're considering running something like this to ensure that CIFS never runs out of pBLKs in the future: setflag fp_maxcifsreqs_pblkpercent X
But we want to determine what the current range is before we make any changes.
Cifs stat shows the value under Max pBLKs = xxx, but XXX is a number without context, like 1700, and doesn't help much.
This e-mail, including any attachment(s), is intended solely for use by the named addressee(s). If you are not the intended recipient, you are not authorized to disclose, copy, distribute or retain this message, without written authorization from Jennison Associates LLC ("Jennison"). This e-mail may contain proprietary, confidential or privileged information. If you have received this message in error, please notify the sender immediately. If you have requested Jennison to e-mail any account information to you or your designee, you are deemed to have consented to electronic delivery of information from Jennison. E-mail messages are not secure and may contain computer viruses or other defects, may not be accurately replicated on other systems, or may be intercepted, deleted or interfered with without the knowledge of the sender or the intended recipient.
We (LogicMonitor) had to add that monitoring recently for a customer, for a very similar issue, where pblocks were exhausted. cifs stat will show max pBlks and Current Pblks, but they are not exposed by snmp or the API, so we had to write a datasource that collects them periodically via ssh.
We did that, but it's dependent on our collection systems (using a groovy/expect type API), so not generically useful to share (and only about 6 lines, anyway.) We could set you up with free trial, though,so you could play with it for two weeks..
As I recall, pblocks were being exhausted, on 7.3.3. Not sure of the resolution....
Steve Francis * * LogicMonitor Inc
sfrancis@logicmonitor.com www.logicmonitor.com Ph: 1 888 41 LOGIC x500 Ph: 1 805 698 0770 NetApp Monitoring made easy.
Steve Francis * * LogicMonitor Inc
sfrancis@logicmonitor.com www.logicmonitor.com Ph: 1 888 41 LOGIC x500 Ph: 1 805 698 0770 Get a signature like this. http://r1.wisestamp.com/r/landing?promo=19&dest=http%3A%2F%2Fwww.wisestamp.com%2Femail-install%3Futm_source%3Dextension%26utm_medium%3Demail%26utm_campaign%3Dpromo_19 CLICK HERE.http://r1.wisestamp.com/r/landing?promo=19&dest=http%3A%2F%2Fwww.wisestamp.com%2Femail-install%3Futm_source%3Dextension%26utm_medium%3Demail%26utm_campaign%3Dpromo_19
On Mon, Nov 28, 2011 at 8:47 AM, Jon Hill JHill@jennison.com wrote:
Is there any way to monitor and alert on pblock utilization via DFM or another monitoring tool? We had an issue recently where CIFS operations ground to a halt that was not resolved until we disabled fpolicy. We believe the entire pblock pool wound up in use and CIFS operations ground to a halt.****
We’re considering running something like this to ensure that CIFS never runs out of pBLKs in the future:****
setflag fp_maxcifsreqs_pblkpercent X****
But we want to determine what the current range is before we make any changes.****
Cifs stat shows the value under Max pBLKs = xxx, but XXX is a number without context, like 1700, and doesn’t help much.****
This e-mail, including any attachment(s), is intended solely for use by the named addressee(s). If you are not the intended recipient, you are not authorized to disclose, copy, distribute or retain this message, without written authorization from Jennison Associates LLC ("Jennison"). This e-mail may contain proprietary, confidential or privileged information. If you have received this message in error, please notify the sender immediately. If you have requested Jennison to e-mail any account information to you or your designee, you are deemed to have consented to electronic delivery of information from Jennison. E-mail messages are not secure and may contain computer viruses or other defects, may not be accurately replicated on other systems, or may be intercepted, deleted or interfered with without the knowledge of the sender or the intended recipient.
Toasters mailing list Toasters@teaparty.net http://www.teaparty.net/mailman/listinfo/toasters
-
Jon Hill -
Steve Francis