Re: [foxboro] CBLAN Module failures

Fabian,

One of the most common causes of CBLAN fault alarms is excessive traffic =
through the modules.
I have seen this on a number of occasions when files have been =
transferred between nodes combined with traffic due to process upsets =
i.e. alarms etc.
You may want to check which QF image revision that you are running on =
your CBLAN modules as you should be at=20
QF1000550.
Have a look at helpful hints numbers 875,960 and 991 for info regarding =
CBLAN.
Also there is an excellent fault finding guide for Tokenbus/Nodebus on =
the Foxboro CSC website under Resources -> Trouble Shooting Guides.

Hope this is of use to you.

Regards=20
Ian

-----Original Message-----
From: Fabian, Jude F [mailto:jffabian@xxxxxxxxxxxxx]
Sent: Friday, 23 January 2004 6:22 AM
To: foxboro@xxxxxxxxxxxxx
Subject: [foxboro] CBLAN Module failures



Hi All,
        We are facing a problem with repeated CBLAN module fault alarms, cables 
=
=3D
and Passive Taps have been changed in random
and still the problem persists inconsistently.Any case studies and =3D
solutions on similar problem on CBLAN modules.

Regards,
Fabian
=20
=20
_______________________________________________________________________
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
=20
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
=20
 
 
_______________________________________________________________________
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: