Re: [foxboro] Nodebus..Displays..Smurfing..William..Shatner..Acting

David,

We don't have the ATS yet, but here a couple of ideas I learned via our
mixed V6.5.X/V7.1 system that may help.  The V7.1 stations connect to
Nodebus via a redundant pair of switches and then a NCNI out to each
Nodebus segment.

Have you tried running a Nodebus Cable test to clear up the smurfing?

If you can copy the files to a slower Nodebus station first, and then use
that slower machine to copy the files to the other Nodebus stations, you
may not experience the problem.

Neil Martin




                                                                           
             David Johnson                                                 
             <drjohn@xxxxxxxxx                                             
             t>                                                         To 
             Sent by:                  foxboro@xxxxxxxxxxxxx               
             foxboro-bounce@fr                                          cc 
             eelists.org                                                   
                                                                   Subject 
                                       Re: [foxboro] [foxboro]             
             09/25/2006 03:14          Nodebus..Displays..Smurfing..Willia 
             PM                        m..Shatner..Acting                  
                                                                           
                                                                           
             Please respond to                                             
             foxboro@freelists                                             
                   .org                                                    
                                                                           
                                                                           




Well.......
The problem initially manifested itself when we were syncing files
from the WP70 master to the other WP70s.  We were moving an entire
directory tree, definitely pushing our luck, and we got smurfed.  Not
a big deal, since the machine was down.  So we let the displays go to
all of the WP70s.  We had to reboot several of the stations to clear
the smurf condition.  So now everything was synced up and we started
production.  We found a minor change on one display that needed to be
made, corrected it on the F box, and ftp'ed it over to the master
WP70.  The file transfer had completed, and I was in the process of g
to fdf ing  the file when everything smurfed again.  One .g file, not
too big and BAM! So once again reboots ensued.  Now the machine is
running and display changes are being copied to a floppy and
sneakernet is being used.

Here is some additional information.
During this outage an AW70x was added with the ATS and CP270, CSA was
promoted to the AW70x.  Foxboro did a day 1 for the system.  The ATS
has 3 TCP/IP addresses on the nodebus (I think).  One problem we had
was one of the IP addresses that was assigned to the ATS was
duplicated on the AW51F (I'm sure).  We found this only because of
bizarre behavior when we were trying to ftp some files ... sometimes
it worked, sometimes it didn't.  So Foxboro re-assigned some of the
TCP/IP addresses on the ATS and it started working correctly.  All of
this was prior to the smurfing issue.

That's probably the extent of my knowledge of the problem.  I don't
know if the ATS has any involvement, or the fact that things were
misconfigured initially my have lingering adverse effects, or some
other gremlin is in the system.

Regards,
David










_______________________________________________________________________
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



 
 
_______________________________________________________________________
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: