Re: [foxboro] What causes System Alarms and What doesn't??
- From: "Boulay, Russ" <Russ.Boulay@xxxxxxxxxxxx>
- To: "'foxboro@xxxxxxxxxxxxx'" <foxboro@xxxxxxxxxxxxx>
- Date: Mon, 3 Jun 2002 13:40:40 -0400
You must optionally create the file if you wish to use the RED blink.....
cd /usr/fox/sysmgm/sysmon
touch ftblink_sys.cx
With 6.2 and above ...the smon_ech process will look for this file and
perform the function of flashing RED on a single CP failure of a FT pair.
Uses the file only as a trigger to implement the option.
If on a 6.1 system the QF990104B installs a new smon_ech file which has
support for this file.
> -----Original Message-----
> From: foxboro-bounce@xxxxxxxxxxxxx@CORP On Behalf Of "Tom Lorenz"
> <Tom.Lorenz@xxxxxxxxxx>
> Sent: Monday, June 03, 2002 10:49 AM
> To: foxboro@xxxxxxxxxxxxx
> Subject: Re: [foxboro] What causes System Alarms and What doesn't??
>
>
>
> My system is at V6.3 & does not have the ftblink_red.cx file. Where can I
> get this file to add to the /usr/fox/sysmgm/sysmon/ directory?
>
>
>
> "Boulay, Russ"
> <Russ.Boulay@Inven To:
> "'foxboro@xxxxxxxxxxxxx'" <foxboro@xxxxxxxxxxxxx>
> sys.com> cc:
> Sent by: Subject: Re: [foxboro]
> What causes System Alarms and What doesn't??
> foxboro-bounce@fre
> elists.org
>
>
> 06/03/2002 09:15
> AM
> Please respond to
> foxboro
>
>
>
>
>
>
>
> This issue always spurred arguments even within Foxboro Co.
> The explanation was:
>
> A RED SYS key indicates loss of operation. Because a single module failure
> in a FT pair did not cause loss of operation of the CP...they decided to
> flash the current color state of the SYS key only. After much
> debate...Foxboro has implemented the following option...( There are still
> users that agree with the single module theory, so it is optional)
>
> Changes were made to the System Monitor; If the file
> /usr/fox/sysmgm/sysmon/ftblink_red.cx exists and one side of a FT station
> fails, the SYS bar will flash RED; If the ftblink_red.cx file is not
> present, the SYS bar will remain it's original color and flash. (even if
> it
> was green, and flash that color). This change has been applied to 6.2
> systems and above. and a QF990104B released for V6.1.
>
> ***Remember just because the SYS key didn't flash RED...it did flash the
> existing color...and many messages do get delivered to System printer
> designating "CP now single".
>
>
> > -----Original Message-----
> > From: foxboro-bounce@xxxxxxxxxxxxx@CORP On Behalf Of "Neil Martin"
> > <neil_martin@xxxxxxxxxxxx>
> > Sent: Monday, June 03, 2002 9:54 AM
> > To: foxboro@xxxxxxxxxxxxx
> > Subject: Re: [foxboro] What causes System Alarms and What doesn't??
> >
> >
> >
> > A year or so ago, Foxboro offered a QF or QC that enabled this function
> > for
> > at least one of the 6.X versions. I have not seen it mentioned lately,
> so
> > I do not know what the current state of the offering is. I would hope
> the
> > option is built into the more recent versions of I/A.
> >
> > Neil Martin
> > Huntsman Corporation
> > 7114 North Lamar Blvd
> > Austin, TX. 78752
> > ph) 512-483-0119
> >
> >
> >
> > "Anderson, Gary
> > T(Z02256)" To:
> > foxboro@xxxxxxxxxxxxx
> > <GTANDERS@xxxxxxxx cc:
> > > Subject: [foxboro]
> What
> > causes System Alarms and What doesn't??
> > Sent by:
> > foxboro-bounce@fre
> > elists.org
> >
> >
> > 05/31/02 01:50 PM
> > Please respond to
> > foxboro
> >
> >
> >
> >
> >
> >
> > Hello All
> >
> > We were recently surprised to discover that upon a fault of a single CP
> in
> > a
> > fault-tolerant pair that our 6.1.2 IA System did not annunciate the
> > problem
> > and only the System button in Foxview started blinking green (as if an
> > alarm
> > had reset). I'm amazed that cable faults annunciate but the fault of a
> > FT-CP pair doesn't.
> >
> > I'd appreciate some discussion on what other hardware failures do not
> > annunciate and/or just blink, together with how you handle system
> alarms.
> > I'm now aware that Foxboro has a solution to turn the binking green to
> > blinking red for this situation. What else will surprise us?
> >
> > It appears that Foxboro has no plans to provide an upgrade for the SMDH
> or
> > the ICC - these are just available on new systems. I wonder why they
> > can't
> > provide an upgrade.
> >
> > Thank you,
> > Gary Anderson
> > Arizona Public Service
> >
> >
> >
> > _______________________________________________________________________
> >
> >
> >
> >
> >
> >
> >
> >
> > _______________________________________________________________________
> > 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
> >
>
>
> -- No attachments (even text) are allowed --
> -- Type: application/ms-tnef
>
>
>
>
> _______________________________________________________________________
> 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
>
-- No attachments (even text) are allowed --
-- Type: application/ms-tnef
_______________________________________________________________________
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:
