Re: [foxboro] CP Islanding

Dave,

Do you have nodebus extenders in Node 05  or in Node 06?  If yes, check
them or replace them.  Copper is bad for this. Fibre optic works much
better and latest is to use NCNI.

Have you performed nodebus cable tests in SMDH while the "island"
exists? It has been seen to correct the same problem at other sites.

If you use cables to connect different racks (not nodebus extenders)
then check these cables very carefully for mechanical defects. The thin
white cables have been known to get caught in doors and pinched which
breaks the dielectric. Check all node cable connectors to ensure that
they did not vibrate loose.

Did this site work great for a while and just start giving you a problem
or has it always been a problem?  Were there any recent changes in the
communication load such as adding lots of data connections over the
CLAN?

Terry


******************************************************

Brief Description of Problem:

I/A version 6.5.3

A CP40A in node 05 islands. Green in field. Red in SysMgt. Cyan on
workstations.

A CP60 in node 06 islands. Same symptoms. Same time.

A reboot of the CBLAN module for node 05 will correct it in this node
for a while, but it returns after a short time.

A check of the performance counters in SysMgt for the node 06 CP's boot
host, shows very slow  response time and over 2000 NO RECEIVE RESOURCE
errors.

I perform a netstat and snoop on le0 of the AW51B and suddenly the
islanding disappears. Moreover, the number of packets passing through
the node 06 LI module drop by almost half (from 180 pkts/s to 108
pkts/s).

That's my story and I'm sticking to it. Any ideas???

Thanks,
Dave
 
 
_______________________________________________________________________
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: