Re: [foxboro] R: DNBI Cabling for long Distance

We upgraded to V6.5/7.1 in the not-too-distant past.  We have an AW51G and 
a WP51F at 7.1 on the switches, and an AW51E and numerous WP51Ds on the 
nodebus via DNBTs.  The E is our primary engineering station, the G is the 
CP host.

I have not seen any issues with ICC in this scenario, but we have had some 
slowness pushing display file updates over the 2nd ethernet to the WP51F. 
The AW51G seems to have no problems.  I'm guessing a reverse name lookup 
issue or something, but have not really looked into it.


We've also had NFD declare 1/2 or greater of the stations on the nodebus 
bad a few times, but no smurfing occurred, so I am concluding that this is 
bogus.  Usually the G box gets very confused also, and requires a reboot. 
It is so intermittent though that we have not gotten a handle on what is 
causing it yet.


Corey Clingo
BASF Corporation






"Jim Kahlden" <James.Kahlden@xxxxxxxx> 
Sent by: foxboro-bounce@xxxxxxxxxxxxx
07/26/2006 08:21 PM
Please respond to
foxboro@xxxxxxxxxxxxx


To
<foxboro@xxxxxxxxxxxxx>
cc

Subject
Re: [foxboro] R: DNBI Cabling for long Distance






We have experienced the same problem when we switched to version 7.1.1 and 
=
used DBNTs to connect the 51F boxes to the nodebus. (This by the way is no 
=
longer supported by Foxboro and we will be changing to RCNIs and NCNIs). =
Are you saying that even connecting the version 7.1.1 stations together =
with RCNIs, NCNIs and switches that you still experience the slow rlogin =
and telnet sessions?

We connected all of our stations together via the second ethernet port and 
=
now use that connection to move data with rlogin and telnet and do not =
experience the slow connections that were introduced with version 7.1.1 =
over the nodebus.



Jim Kahlden
System Reliability Analyst
Lower Colorado River Authority
Fayette Power Project
6549 Power Plant Road
La Grange, TX 78945
(979) 249-8514 (Ph)
(979) 249-8390 (Fax)
jim.kahlden@xxxxxxxx
>>> Frits.Schouten@xxxxxxxxxxxxxxxxxx 07/26/06 4:47 PM >>>
A very known problem.
Try telnetting from your AW to a WP on the switched network (V7.x).=3D20
That's near impossible.
I don't think it has anything to do with the cable length.=3D20
Looks to me more like a switch problem. It just looses the path or so.
I have great issues between CP's and the AW trying to utilise SENDMSG to
execute programs on the host and then to get some data back to the CP.
This fails on a regular basis.

Cheers,
Frits Schouten
NZSteel.





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