Kevin We have had failures of our node bus ( between two Fibre Optic Node Bus extender modules ) and the system manager has marked the CPs as bad when in fact they were still going fine. The Network Fault Detection (NFD) software can get confused and mark the items as bad. This software runs on the AW or AP depending on your system therefore a reboot of the AW / AP will restart the software and hopefully get your system moving again with out needing to reboot the CP's. The problem at our site was that we had the AW and the CB Lan modules in one segment and all the CPs in another segment. Stephen Lewis NRG Gladstone Power Station Australia > ---------- > From: Lemieux, Tom[SMTP:[EMAIL PROTECTED]] > Reply To: Foxboro DCS Mail List > Sent: Saturday, 11 March 2000 5:04 > To: 'Foxboro DCS Mail List' > Subject: RE: Problem with CP30??? > > Kevin, > > It sounds allot like a node bus problem. Whether the problem was do to > real > failure or loading is another story. If System monitor can not talk to the > CP then as far as it is concerned it has failed. As far as the CP reboot > was > concerned I would bet that the problem was more with the AW than anything > else. I am an old site (Alabama River Pulp) that started with AP20's and > have found that the AW's are much less tolerant of node bus problems. > Obviously these are all SWAG's but it is something to keep an eye on. > > Thanks, Tom Lemieux > > > -----Original Message----- > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] > Sent: Friday, March 10, 2000 12:38 PM > To: Foxboro DCS Mail List > Subject: Problem with CP30??? > > > Hello all, > We had an unusual problem last night and I was hoping one of you might > have > some insight. > > We have a fairly small system: a WP51B and an AW51B hosting a CP30 fault > tolerant pair and 6 AB stations. We are running version 4.3. > > With no warning, the System Monitor reported the CP station had failed. > System manager showed the system failed. The CP appeared to continue > working however. Both CPs had green lights. The processes they were > controlling did not crash, and appear to have stayed in tight control > during the incident. The historian appears to have continued to bring in > valid readings from the CP, and our trends continued to update (albeit > slowly). The display managers were showing smurfed or blank areas for > values from the CP. The CP does not appear to have been able to > communicate with the AB stations during this time. The host CPU loading > was low (around 8%) prior to the problem and even lower (4-5%) during. > > > We push-pulled the CPs several times, each time they seemed to be stuck > downloading. We rebooted the host AW and reset the entire cabinet that > houses our CP, commo cards, several AB stations, etc. and the system came > up with no problems. We contacted Foxboro for support and they were very > supportive, but did not find anything that might have caused the problem > when they dialed in to our system after we had managed to bring it back > up. > The only thing of any note prior to this failure was that Foxboro had > logged on our system earlier that afternoon to run their Foxwatch stuff. > > If any of you have had similar failures or have any ideas on what might > have happened I'd sure appreciate hearing from you. > > Thanks! > > Kevin FitzGerrell > Fairbanks Gold Mining, Inc. ----------------------------------------------------------------------- This list is neither sponsored nor endorsed by the Foxboro Company. All postings from this list are the work of list subscribers and no warranty is made or implied as to the accuracy of any information disseminated through this medium. By subscribing to this list you agree to hold the list sponsor(s) blameless for any and all mishaps which might occur due to your application of information received from this mailing list. To be removed from this list, send mail to [EMAIL PROTECTED] with "unsubscribe foxboro" in the Subject. Or, send any mail to [EMAIL PROTECTED]
