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

Hmm...I've seen this issue when telnetting from my G box over the nodebus 
to the switches themselves (as the RCNI apparently will only transmit to 
one or the other switch as it sees fit), but not from a D/E box to the G. 
However, I usually use a 2nd ethernet for that kind of thing.

As I mentioned earlier, I do have some lag from the E box to the F box, 
but I still suspect this is a network configuration issue on the F since 
it occurs on the 2nd ethernet.


But early on I realized that the nodebus was a fragile thing and made 
efforts to get every one of my stations on a 2nd ethernet.  It was the 
best I/A investment I ever made.  I am surprised Foxboro never sold such a 
setup as part of the standard system.  I would think it would have saved 
them a few support calls.


Corey Clingo
BASF Corporation






Kevin FitzGerrell <fitzgerrell@xxxxxxxxxxxxxxx> 
Sent by: foxboro-bounce@xxxxxxxxxxxxx
07/26/2006 10:34 PM
Please respond to
foxboro@xxxxxxxxxxxxx


To
"foxboro@xxxxxxxxxxxxx" <foxboro@xxxxxxxxxxxxx>
cc

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






Jim,

Yes, that's what I meant.  We have 51F boxes using RCNI running 7.1 
connected to
16 port fibre switches.  These switches connect via NCNIs to nodebus 
segments.
If I telnet from a nodebus workstation (AW51E, WP51B/D at 6.5/6.5.1 with 
current
QFs) I sometimes see delays and very slow response.  When using vi it is
particularly frustrating, because typing during one of the delays often 
causes
unintended characters and control sequences to be inserted.

Ping times indicate virtually no delay, a ping -s to the 7.1 workstation 
from
anywhere on the network will normally show 1-2ms on the first ping and 0 
on all
subsequent ones.

This problem only affects our V7.1 workstations.  I can telnet from a 
6.5.x
workstation on one segment through ncni-switch-ncni to another 6.5.x 
workstation
on a different segment with no problems.

We are using the same switches for our version 8 system and see no 
problems
(although with different firmware).

We do have QF1003903B installed.

Regards,

Kevin FitzGerrell
+64 27 460 9994

Quoting Jim Kahlden <James.Kahlden@xxxxxxxx>:

> 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.
>
>
> -----Original Message-----
> From: foxboro-bounce@xxxxxxxxxxxxx
> [mailto:foxboro-bounce@xxxxxxxxxxxxx]
> On Behalf Of Kevin FitzGerrell
> Sent: Thursday, 27 July 2006 9:16 AM
> To: foxboro@xxxxxxxxxxxxx
> Subject: Re: [foxboro] R: DNBI Cabling for long Distance
>
> Jaime,
>
> It's my understanding that this is a known issue. We see the same
> behavior when using rlogin to a V7.1.1 workstation - we have short UTP
> cables (2 meters) and experience these problems. =3D20
>
> Regards,
>
> Kevin FitzGerrell
> +64 27 460 9994
>
> Quoting "Jaime Claramunt R. (Inforsa)" <jclaramunt@xxxxxxxxxxxxxxx>:
>
> > what about distance between RCNI and AW ? UTP cable side , I mean.
> > We are suspecting of collitions or some other problem making very
> slow
>
> > =3D3D comms with other nodes. Maybe we exceed this distance.
> > For instance, opening ICC from other AW or try to edit sequences, is
> =
> =3D3D
>
> > very slow... much slower than before the upgrade to 7.1.1 (just
> for=3D20
> > this node AW other 3 ones are OK)
> >=3D20
> >=3D20
> > Jaime Claramunt
> > Depto.Ing.Planta
> > INFORSA
> > 43-631576
> >=3D20
> >=3D20
> >=3D20
> >=3D20
> > -----Mensaje original-----
> > De: foxboro-bounce@xxxxxxxxxxxxx
> > [mailto:foxboro-bounce@xxxxxxxxxxxxx]En
> > nombre de Corey R Clingo
> > Enviado el: Martes, 25 de Julio de 2006 16:20
> > Para: foxboro@xxxxxxxxxxxxx
> > Asunto: Re: [foxboro] R: DNBI Cabling for long Distance
> >=3D20
> >=3D20
> > Yes, it worked much better for us.
> >=3D20
> > Corey Clingo
> > BASF Corporation
> >=3D20
> >=3D20
> >=3D20
> >=3D20
> >=3D20
> >=3D20
> > "BrianLong" <blong@xxxxxxx>=3D3D20
> > Sent by: foxboro-bounce@xxxxxxxxxxxxx
> > 07/25/2006 11:51 AM
> > Please respond to
> > foxboro@xxxxxxxxxxxxx
> >=3D20
> >=3D20
> > To
> > <foxboro@xxxxxxxxxxxxx>
> > cc
> >=3D20
> > Subjec t
> > Re: [foxboro] R: DNBI Cabling for long Distance
> >=3D20
> >=3D20
> >=3D20
> >=3D20
> >=3D20
> >=3D20
> > To summarize is it correct to say, don't use DNBX, use NCNI's with a
> =
> =3D3D
>
> > rack and a DNBI?
> >=3D20
> > Brian Long
> > Arkansas Kraft
> >=3D20
> > DCS Administrator
> > Tele +9663577-5396
> > Pager +9663870-1474
> > eFax +96638744444 / Ext. 133732
> >=3D20
> >=3D20
> >=3D20
> >=3D20
> >=3D20
> >=3D20
> >=3D20
> >=3D20
>  >=3D20
> > =3D3D20
> > =3D3D20
> > ____________________________________
> > ___________________________________
> > This mailing list is neither sponsored nor endorsed by Invensys=3D20
> > Process Systems (formerly The Foxboro Company). Use the info you=3D20
> > obtain here at your own risks. Read=3D20
> > http://www.thecassandraproject.org/disclaimer.html
> > =3D3D20
> > foxboro mailing list: http://www.freelists.org/list/foxboro
> > to subscribe: =3D3D
> > mailto:foxboro-request@xxxxxxxxxxxxx?subject=3D3D3Djoin
> > to unsubscribe: =3D3D
> > mailto:foxboro-request@xxxxxxxxxxxxx?subject=3D3D3Dleave
> > =3D3D20
> > =3D20
> > =3D20
> >
> ______________________________________________________________________
>  > _
> > This mailing list is neither sponsored nor endorsed by Invensys=3D20
> > Process Systems (formerly The Foxboro Company). Use the info you=3D20
> > obtain here at your own risks. Read=3D20
> > http://www.thecassandraproject.org/disclaimer.html
> > =3D20
> > foxboro mailing list: http://www.freelists.org/list/foxboro
> > to subscribe: mailto:foxboro-request@xxxxxxxxxxxxx?subject=3D3Djoin
> > to unsubscribe:
> mailto:foxboro-request@xxxxxxxxxxxxx?subject=3D3Dleave
> > =3D20
> > =3D20
>
> =3D20
> =3D20
> _________________________________________________
> ______________________
> 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
> =3D20
> foxboro mailing list: http://www.freelists.org/list/foxboro
> to subscribe: mailto:foxboro-request@xxxxxxxxxxxxx?subject=3D3Djoin=
>
> to unsubscribe: mailto:foxboro-request@xxxxxxxxxxxxx?subject=3D3Dleave=
>
> =3D20
>
>
> =3 D0A=3D0ANOTICE - This message and any attached files may contain =
> informatio=3D
> n that is confidential and intended only for use by the intended =
> recipien=3D
> t. If you are not the intended recipient or the person responsible for
> =
> de=3D
> livering the message to the intended recipient, be advised that you have
> =
> =3D
> received this message in error and that any dissemination, copying or =
> use=3D
>  of this message or attachment is strictly forbidden, as is the =
> disclosur=3D
> e of the information therein. If you have received this message in error
> =
> =3D
> please notify the sender immediately and delete the message.
> =20
> =20
> ____________________________________________________
> ___________________
> 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
> =20
> foxboro mailing list: http://www.freelists.org/list/foxboro
> to subscribe: mailto:foxboro-request@xxxxxxxxxxxxx?subject=3Djoin
> to unsubscribe: mailto:foxboro-request@xxxxxxxxxxxxx?subject=3Dleave
> =20
>
>
>
> ______________________________________________________________________
> _
> 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



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