[foxboro] FW: AW51F Issues
- From: "Ellis, Jeff" <Jeff.Ellis@xxxxxxxxxxxxxxxxxx>
- To: "foxboro@xxxxxxxxxxxxx" <foxboro@xxxxxxxxxxxxx>
- Date: Wed, 17 Nov 2010 14:20:39 -0600
I need a little help (o.k. a LOT of help) with diagnosing issues around an
AW51F box.
THE ISSUE
Instrumentation personnel complained that when trying to go into PLB_MONITOR
they would receive a “Termination is progress; Object Manager Error”. In
addition, no one could open a remote Exceed session on this AW.
We started by checking memory and then rebooted the AW. The AW would boot up to
the point of starting the DM then an error message would occur stating it is
unable to display alarms because Alarm Server Task is unavailable. The AW would
not boot any further and the DM menu picks are unselectable. Had to remote into
the Box to shutdown / reboot or perform STOP-a. Numerous attempts to fix it
includes: Reloading previous tape backup, Day Zero and install tape backup, and
finally Day Zero and loaded up Version 7.0, new DNBT and moved DNBT to
different slot in the rack. All have had the same issue (only booting so far
into the DM w/ AST error). Checked the Alarm Sever status by using “ps –eaf |
grep AST” and the AST task appeared to be working in all scenarios.
However, we then disconnected the AW from the nodebus and the box booted up
(even with the original configuration). We were then able to reconnect the AW
to the DNBT and everything appears to be working. So we used a 1X8 rack and
likewise it booted up when connected to the DNBT.
Note: It is already known there are nodebus issues. Nodebus Cable errors are
occurring at an increasing rate (sometimes on A bus and sometimes on B ) over
the last several weeks. Error goes away after “Run Nodebus Cable Test” is
performed from System Monitor. Unforetunately this nodebus controls two
different parts of the mill that are seldomly down together... may be a while
to address.
Questions:
Has anyone had a similar experience? Any suggestions?
Could the PLB_Monitor errors and the AST issue be caused the Nodebus issues?
Could there be a timing issue of sequences preventing the AST being available
when the DM is looking for it?(i.e. could this issue be related to the nodebus
cable error issue?) If so is there a way of modifying the timing?
Background – Maybe be relevant…
Version 7.1.1 – Display Manager (no FoxView graphics in this area )
AW51F w/ DNBT
4 WP51D workstations w/ DNBTs
3 CommProcessors
ATS to Mesh (Mesh is not hosting any CPs in this area though)
4 CP60s
3 WP30s
1 Allen-Bradley 30B
** There have also been numerous workstation failures in this area - Mostly
apparent HW failures.
Thanks,
Jeff Ellis
Confidentiality Notice:
The information contained in this message is private and confidential. This
information is intended only for the individual or entity named above. If the
reader of this message is not the intended recipient, you are hereby notified
that any use, review, dissemination, distribution, copying or action taken
based on this message or its attachments, if any, is strictly prohibited. If
you are not the intended recipient, please contact the sender by reply email
and delete or destroy all copies of this message and any attachments. Thank
you.
_______________________________________________________________________
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
Other related posts:
- » [foxboro] FW: AW51F Issues - Ellis, Jeff
