Re: [foxboro] ATS and nodebus loading

David,
A few things....

The ATS can easily pass 1000-1500 pkts/sec
Just because the ATS is capable of that rate, the old nodebus is still
the old nodebus. So you could easily hammer the nodebus with constant
rates above 500 pkts/sec.

One of the key loading considerations is Multicasts.
The ATS can handle 20 multicasts/.5sec before dropping them.
So, unoptimized displays, trends without dedicated historian names, api
calls that broadcast, etc could cause some issues.
You can use the omgetimp to get some key values from ATS.
  omgetimp ATS006PDUS30 (packets thru ATS)
  omgetimp ATS006DRMCAST (Dropped Multicasts)
  omgetimp ATS006TXFRAME
  omgetimp ATS006RXFRAME
  omgetimp ATS006COLLS

Lastly, what CP images are your old CP's running?
When an ATS is added to a node it becomes the NFD master.
If your old CP's are runnng images below those that ship with I/A 6.5.2
and 7.1.1 than they can be subject to nodebus islanding.
There is a QF that allows NFD to be shutoff in the ATS in those cases.

-----Original Message-----
From: foxboro-bounce@xxxxxxxxxxxxx [mailto:foxboro-bounce@xxxxxxxxxxxxx]
On Behalf Of David Johnson
Sent: Sunday, April 27, 2008 11:11 AM
To: Foxboro@xxxxxxxxxxxxx
Subject: [foxboro] ATS and nodebus loading

Hello all,

Does anyone know how much data I can pass through an ATS onto the =

nodebus before encountering problems.  In preparation for an upcoming =

outage we are sending many (several hundred) values from a new FCP270 =

through an ATS to a CP40 on the old nodebus side.  Everything worked =

fine until last week. Each week we are passing more data through the =

ATS.  Now we are encountering occasional (3 times in the last week) =

smurf-outs on all of the operator displays of data coming from the =

old CPs.   So it is like this, I think.  FCP270 AIN (mesh side)-> OLD =

CP40  AIN(nodebus side) -> New Displays (mesh side).  This is making =

for a LOT of remote connections in the old CPs and everything gets =

passed through the ATS twice.  I'm guessing the nodebus occasionally =

gets swamped.  It's all temporary in an effort to move everything to =

the mesh, but I need to roll another 50-100 points like this (real =

world wiring issues) for the next two weeks without a =

catastrophe.  Any advice would be appreciated.

Regards,
David


 =

 =

_______________________________________________________________________
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:             http://www.freelists.org/list/foxboro
to subscribe:         mailto:foxboro-request@xxxxxxxxxxxxx?subject=3Djoin
to unsubscribe:      mailto:foxboro-request@xxxxxxxxxxxxx?subject=3Dleave
 =



* Confidentiality Notice:
This e-mail and any associated files are intended solely for the individual=
 or entity to whom they are addressed. Please do not copy it or use it for =
any purposes, or disclose its contents to any other person. Further, this e=
-mail and any associated files may be confidential and further may be legal=
ly privileged. This email is from the Invensys Process Systems business uni=
t of Invensys plc which is a company registered in England and Wales with i=
ts registered office at Portland House, Bressenden Place, London, SW1E 5BF =
(Registered number 166023).  For a list of European legal entities within t=
he Invensys Process Systems business group, please click here http://www.in=
vensys.com/legal/default.asp?top_nav_id=3D77&nav_id=3D80&prev_id=3D77.

If you have received this e-mail in error, you are on notice of its status.=
 Please notify us immediately by reply e-mail and then delete this message =
from your system. Thank you for your co-operation. You may contact our Help=
desk on +44 (0)20 7821 3859 / 2105 or email inet.hqhelpdesk@xxxxxxxxxxxxx T=
his e-mail and any attachments thereto may be subject to the terms of any a=
greements 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:             http://www.freelists.org/list/foxboro
to subscribe:         mailto:foxboro-request@xxxxxxxxxxxxx?subject=join
to unsubscribe:      mailto:foxboro-request@xxxxxxxxxxxxx?subject=leave

Other related posts: