This instance was odd in that we were seeing smurfed tags on the AW, and both of the AW's. It seemed localized to an integrator 30, so our theory is that it is what ran out of lists. Is that data I have global for the node, or specific to the AW? > -----Original Message----- > From: Stan Brown [mailto:stanb@xxxxxxxxx] On Behalf Of Corey R Clingo > Sent: Tuesday, August 24, 2010 10:50 AM > To: foxboro@xxxxxxxxxxxxx > Subject: Re: [foxboro] OM lists > > My old AW is pretty mangy as well, but hosing the keyboard and mouse > down > with Lysol usually takes care of it :) > > Seriously, we resolve this issue by rebooting as well. It's infrequent > enough that we haven't implemented any active OM-list-killing scripts > or > anything (if that's even possible), It is usually our Aspen IP.21 > collector AW that is the culprit, and gateways that are the "victims" > (have the smurfed tags on operator stations). > > > C > > > > > > stan <stanb@xxxxxxxxx> > Sent by: foxboro-bounce@xxxxxxxxxxxxx > 08/24/2010 09:42 AM > Please respond to > foxboro@xxxxxxxxxxxxx > > > To > Foxboro List <foxboro@xxxxxxxxxxxxx> > cc > > Subject > [foxboro] OM lists > > > > > > > WE had an instance where we ran out of OM lists last night. Foxboro TAC > logged in and determined that the AW on this node was using too mangy, > and > we resolved the issue (for the moment) by rebooting this machine. > > However,, I am not convinced we have found the root cause on this. The > configuration on this node has been stable for quite a while, and the > last > time the AW was rebooted was 150+ days ago, after an upgrade to 7.1.5 > software. > > We have run a variant of the checkit script from the Casandra site for > a > number of years, and it uses /usr/local/show_params to report on some > OM > statistics. Frankly I am not all that familiar with the output of this > section of the report. Can someone tell me if these values are global > to > the node? If not, is there a script that I can run to get statistics > for a > specific station (AB integrator 30A in this case). > > Thanks for any suggestions as to forensics on this. > > -- > A: Because it messes up the order in which people normally read text. > Q: Why is top-posting such a bad thing? > A: Top-posting. > Q: What is the most annoying thing in e-mail? > > > > > > > _______________________________________________________________________ > This mailing list is neither sponsored nor endorsed by Invensys Process > Systems (formerly The Foxboro Company). Use the info you obtain here at > your own risks. Read http://www.thecassandraproject.org/disclaimer.html > > foxboro mailing list: //www.freelists.org/list/foxboro > to subscribe: mailto:foxboro-request@xxxxxxxxxxxxx?subject=join > to unsubscribe: mailto:foxboro-request@xxxxxxxxxxxxx?subject=leave > The information contained in this message and any attached files may be privileged and/or confidential and protected from disclosure. If you are not the intended recipient, any disclosure, copying, distribution or use of any of the information contained in or attached to this transmission is strictly prohibited. If you have received this transmission in error, please so notify the sender immediately without reading it. Also, please promptly destroy the original transmission and its attachments. Any views or opinions presented in this message or attachments are those of the author and do not necessarily represent those of KapStone Paper and Packaging Corporation or its subsidiaries. _______________________________________________________________________ This mailing list is neither sponsored nor endorsed by Invensys Process Systems (formerly The Foxboro Company). Use the info you obtain here at your own risks. Read http://www.thecassandraproject.org/disclaimer.html foxboro mailing list: //www.freelists.org/list/foxboro to subscribe: mailto:foxboro-request@xxxxxxxxxxxxx?subject=join to unsubscribe: mailto:foxboro-request@xxxxxxxxxxxxx?subject=leave