Re: [foxboro] OM lists

From: Terry Doucet <doucet427@xxxxxxxxxxx>
To: <foxboro@xxxxxxxxxxxxx>
Date: Wed, 25 Aug 2010 10:57:52 -0400
Michael,The peer in peer to peer is station. So the FCP270 can make a total of 
51 station to station connections (31 where the FCP270 is a SOURCE (owner of 
the C:B.P) and 20 where it is a SINK (user of some other station's C:B.P). You 
are not likely to exceed these limits.
To ensure that any C:B.P that changes its value in this CP - gets sent off to 
WP's, CPs and Historians, etc there is an OM Scanner Entry created. The limit 
in the FCP270 is 600 so this limit is not likely to be reached. However the 
limit for the Int30 is 150 in the Scanner Entries and I have seen (counted with 
rsom) this limit reached many times.
If any limit is reached, your system will not work as you might want (expect) 
it to work.  As Alex stated, the OM and its limits and methodology are not 
trivial. TAC has the experts to help you identify these limits and determine if 
you have run up against one or other of the limits. Earlier releases of IA, 
some of which may still be running in many sites, were more susceptible to OM 
issues where IPC connections or lists were not closed out when the SINK station 
closed a FV or DM session or called another display that no longer had 
connections to specific stations.
Terry

> Date: Wed, 25 Aug 2010 10:35:46 -0400
> From: mkessler@xxxxxxxxxxxx
> To: foxboro@xxxxxxxxxxxxx
> Subject: Re: [foxboro] OM lists
> 
> I looked through the document and found the maximum number of Inter 
> Process Connections (IPC)'s be 51 for FCP270 however I did not see any 
> reference to the total number of values that can be passed (ie peer to 
> peer connections).
> 
> I suppose the limit will depend on the type of connection (ie bit, 
> float, int). Just curious if anyone has hit any limits?
> 
> mk
> 
> Terry Doucet wrote:
> > Have a read of EDOC B0193BC - Object Manager Calls
> > Be clear on the issues of:1. Inter Process Connections - IPC's both SINK 
> > and SOURCE connections which are connections between stations. There are 
> > limits on the numbers of these but with current technology you are not 
> > likely to run into these limits.
> > 2. Object Manager (OM) Lists - The SINK station creates an OM list of C:B.P 
> > that it wants and the SOURCE station will create an OM Scanner Entry for 
> > the C:B.P that it owns to send the updated data to the SINK. Different 
> > stations have different sized OM lists and Scanner Entries. See Table 1-2 
> > in the EDOC.  Scanner Entries are formed from the Source station for points 
> > in the OM lists that are to be scanned (monitored for changes in value).  
> > The Int30 has the same limits as the CP30 and for Scanner Entries it is 150 
> > points. Once you reach 150 in the Int30, the next station to request data 
> > (perhaps a new WP coming online and displaying points from this Int30) will 
> > not get data. 
> > The tools   som    and    rsom   are used to count the numbers in the 
> > various lists and entries.
> > When a SINK station is rebooted it will broadcast its letterbug.  SOURCE 
> > stations are supposed to watch for these broadcasts and close out lists and 
> > connections that were initiated by the rebooting station. So if you reboot 
> > and AW, all the points in its historian (for example) that are in Int30 are 
> > wiped out in the Int30 OM and then new demands for updates (graphic called 
> > in a WP) are able to use the resources in the Int30 to populate the 
> > graphics. 
> > Terry
> >
> >   
> >> From: Jack.Easley@xxxxxxxxxxxx
> >> To: foxboro@xxxxxxxxxxxxx
> >> Date: Tue, 24 Aug 2010 15:19:03 -0500
> >> Subject: Re: [foxboro] OM lists
> >>
> >> I hesitate to answer as I was into this so long ago it's fuzzy, but I'll 
> >> make two comments. Hopefully someone else with recent experience can help 
> >> you more.
> >> 1. show_params is just the tip of the iceberg. You must learn about rsom 
> >> and som to track these problems to the source. Not easy as I can't readily 
> >> tell you where to find documentation, although perhaps Alex Johnson or 
> >> your Fox Service Rep can help. All show_parms will indicate is the number 
> >> of local lists and other resources you are using at any given time versus 
> >> the number you (aka Foxboro) have configured to be maximum.
> >> 2. The Integrator 30 probably isn't the culprit, it's just where you see 
> >> the symptoms from lack of resources on the AW (especially if you do not 
> >> see this on the same displays other WP/AWs. The real problem is probably 
> >> remote display access, or Aspen, or a custom C application, etc running 
> >> (or that has run) on the AW.
> >>
> >> Jack Easley
> >> Sr. I&C Technician
> >> Luminant Power, Martin Lake Plant
> >> Phone 903.836.6273
> >> jack.easley@xxxxxxxxxxxx 
> >>
> >>
> >> -----Original Message-----
> >> From: foxboro-bounce@xxxxxxxxxxxxx [mailto:foxboro-bounce@xxxxxxxxxxxxx] 
> >> On Behalf Of Brown, Stanley
> >> Sent: Tuesday, August 24, 2010 2:57 PM
> >> To: foxboro@xxxxxxxxxxxxx
> >> Subject: Re: [foxboro] OM lists
> >>
> >> Can you clarify something for me?
> >>
> >> If the AW in question had established OM lists to the Integrator 30 in 
> >> question, would these lists show up with show_params? If (somehow) the 
> >> Integrator 30 had established lists with the AW (why would it do this?) 
> >> would show_params show these lists?
> >>
> >>
> >>     
> >>> -----Original Message-----
> >>> From: Stan Brown [mailto:stanb@xxxxxxxxx] On Behalf Of Johnson, Alex P
> >>> (IOM)
> >>> Sent: Tuesday, August 24, 2010 10:59 AM
> >>> To: foxboro@xxxxxxxxxxxxx
> >>> Subject: Re: [foxboro] OM lists
> >>>
> >>> /usr/local/show_params reports on ONLY the station on which it is
> >>> running.
> >>>
> >>> Rsom (remote stations) and som (local station) can be used (not as a
> >>> scripts (easily) though) to monitor OM list usage. There is some
> >>> documentation in B0193JB.
> >>>
> >>> If the GW/DI ran out of lists opened by the AW, there is some program
> >>> on the AW that is not closing its lists properly. You can use rsom to
> >>> examine the lists in the GW/DI and determine what tags are in use.
> >>> Often that will tell you the application that opened the lists. Also,
> >>> you can look at the PID of the process that opened the list in the GW
> >>> and the station that opened the list. This can be used to identify who
> >>> is opening lists and still running.
> >>>
> >>>
> >>>
> >>> Regards,
> >>>
> >>> Alex Johnson
> >>> Invensys Operations Management
> >>> 10900 Equity Drive
> >>> Houston, TX 77041
> >>> +1 713 329 8472 (desk)
> >>> +1 713 329 1600 (operator)
> >>> +1 713 329 1944 (SSC Fax)
> >>> +1 713 329 1700 (Central Fax)
> >>> alex.johnson@xxxxxxxxxxxx (current)
> >>> alex.johnson@xxxxxxxxxxxxxxxx (good until September 2010)
> >>>
> >>>
> >>> Attend OpsManage'10
> >>> Real Collaboration. Real-Time Results.
> >>>
> >>> Click Here to learn more about these events and to register.
> >>>
> >>>
> >>>
> >>>
> >>> -----Original Message-----
> >>> From: foxboro-bounce@xxxxxxxxxxxxx [mailto:foxboro-
> >>> bounce@xxxxxxxxxxxxx] On Behalf Of stan
> >>> Sent: Tuesday, August 24, 2010 10:42 AM
> >>> To: Foxboro List
> >>> 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
> >>>
> >>>
> >>>
> >>> *** Confidentiality Notice: This e-mail, including any associated or
> >>> attached files, is intended solely for the individual or entity to
> >>> which it is addressed. This e-mail is confidential and may well also be
> >>> legally privileged. If you have received it in error, you are on notice
> >>> of its status. Please notify the sender immediately by reply e-mail and
> >>> then delete this message from your system. Please do not copy it or use
> >>> it for any purposes, or disclose its contents to any other person. This
> >>> email comes from a division of the Invensys Group, owned by Invensys
> >>> plc, which is a company registered in England and Wales with its
> >>> registered office at 3rd Floor, 40 Grosvenor Place, London, SW1X 7AW
> >>> (Registered number 166023). For a list of European legal entities
> >>> within the Invensys Group, please go to
> >>> http://www.invensys.com/legal/default.asp?top_nav_idw&nav_id¤&prev_
> >>> idw.
> >>>
> >>> You may contact Invensys plc on +44 (0)20 3155 1200 or e-mail
> >>> reception@xxxxxxxxxxxxx This e-mail and any attachments thereto may be
> >>> subject to the terms of any agreements between Invensys (and/or its
> >>> subsidiaries and affiliates) and the recipient (and/or its subsidiaries
> >>> and affiliates).
> >>>
> >>>
> >>>
> >>>
> >>> _______________________________________________________________________
> >>> 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
> >>  
> >>
> >>
> >> Confidentiality Notice: This email message, including any attachments, 
> >> contains or may contain confidential information intended only for the 
> >> addressee. If you are not an intended recipient of this message, be 
> >> advised that any reading, dissemination, forwarding, printing, copying or 
> >> other use of this message or its attachments is strictly prohibited. If 
> >> you have received this message in error, please notify the sender 
> >> immediately by reply message and delete this email message and any 
> >> attachments from your system. 
> >>
> >>  
> >>  
> >> _______________________________________________________________________
> >> 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
> >>  
> >>     
> >                                       
> >  
> >  
> > _______________________________________________________________________
> > 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
> >  
> >
> >
> >   
>  
>  
> _______________________________________________________________________
> 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
>  
                                          
 
 
_______________________________________________________________________
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
References:
- Re: [foxboro] OM lists
  - From: Brown, Stanley
- Re: [foxboro] OM lists
  - From: Easley, Jack
- Re: [foxboro] OM lists
  - From: Terry Doucet
- Re: [foxboro] OM lists
  - From: Michael Kessler
Re: [foxboro] OM lists

Other related posts:
