Re: [foxboro] Alarms
- From: Kevin Fitzgerrell <fitzgerrell@xxxxxxxxx>
- To: foxboro@xxxxxxxxxxxxx
- Date: Tue, 17 Feb 2009 06:14:01 +0900
How many CBLAN nodes do you have, and in what configuration? Are you using
all fiber (after copper-fiber converters)? Do you have passive taps, and if
so are they the isolated ones? What image are the CBLAN modules running -
and are they all running the same image? Do a "what" on the
/usr/fox/sp/files/OS1LI file in each host and see the image revision near
the top.
How frequent are these failures? You may have a hardware problem, but most
of these errors can be caused by noise and/or loading also.
Copper CBLANs in my experience are very sensitive to installation issues.
I've seen CBLAN faults increase after checking and tightening electrical
connections (even if by Foxboro field service engineers). Don't just
tighten - measure resistance and ground performance. Measure to ensure that
you have no ground loops in the copper CBLAN. Measure your dB loss on each
of the fibers end to end.
How heavy is the CBLAN loading? If you have a recent CBLAN image check your
counters - on average, what are your PDUS30 counters reading (don't
historize these, just sample them with omget or omgetimp? Sample the rest
of the counters in each of your CBLAN modules once and then again 10 and 60
minutes later and see what kind of error messages you are getting - these
can help determine what kind of problems you are having on your LAN.
Regards,
Kevin FitzGerrell
On Tue, Feb 17, 2009 at 2:57 AM, <Ajit.S.Kumar@xxxxxxxxxxxxx> wrote:
> Hi,
> We have been getting failures on Carrierband lan Modules,P0960KA , One of
> the Primary Modules is taken offline with LED status as Red/green. Alarm
> messages are at random. Could anybody out there let me know what could be
> the possible cause of the messages.Is it related to Hardware fault. Note
> all elctrical connections were checked and tighted, Copper to Fibre
> Connectors were cleaned and secured. RG6 Drop cables and RG-11 Cables were
> checked. Fibre Optic Converter is OK too. We have listed the most common
> alarms.
> CCLN03 Process = NFD000106 , NF8023 -00051 Station/SSB error detected on
> cable A : A2MI01 State:BB or A2CP02 or CCMI01
> SYSMON = A1SM01 CCLN01 Error Protocol FTXSS 000024 JABBER error has
> occurred 00006C06A120,
> SYSMON = A1SM01 CCLN01 Error Protocol FTXSS 000024 JABBER error has
> occurred 00006C06A269,
> CCLN03 Process = NFD000106 NF8023 -00025 Masters TxB Failed. NB Cable test
> to A2WP21 and A2CP02 OK
> CCLN01 Error Protocol RAMDSS 000014 COOP TBC Fail Tbc listen test on bus
> "A". 00006C060623
> CCLN03 Error Protocol FTXSS 000081 Error Escalation Threshold has been
> exceeded 00006C060204
> CCLN03 Process = NFD000106 NF8023 -00004 Cable B to CCWP22 and A2MI01 OR
> NB Masters RxB Failed
> CCLN03 Error Protocol RAMDSS 000022 SSB cooperative ssb external loopback
> failure. 00006C06A269
> CCLN01 Process = NFD000101 NF8023 -00024 A1WP21 RxB Failed. NB Cable Test
> to A1AW11 OK
> ____________________
> Thanks and Best Regards
> A.Kumar
>
>
>
>
> _______________________________________________________________________
> 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
Other related posts:
