HP3000-L Archives

May 1998, Week 3

HP3000-L@RAVEN.UTC.EDU

Options: Use Monospaced Font
Show Text Part by Default
Show All Mail Headers

Message: [<< First] [< Prev] [Next >] [Last >>]
Topic: [<< First] [< Prev] [Next >] [Last >>]
Author: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Subject:
From:
"Stigers, Greg ~ AND" <[log in to unmask]>
Reply To:
Stigers, Greg ~ AND
Date:
Tue, 19 May 1998 15:06:27 -0400
Content-Type:
text/plain
Parts/Attachments:
text/plain (40 lines)
I would like to thank those who have replied already, and welcome more
replies. I do ask for the sake of the list that they be emailed to me
off list. I fully intend to abstract and summarize what I learn in a
single posting, on the chance that it may be of benefit to those on the
list.

I have received enough responses that it makes sense for me to state my
issues here. Follow up questions that I have asked respondents are:
If you don't mind my asking, can you tell me whose token ring card you
are using in the 3000?
Have you had inexplicable hangs? Under what circumstances?
Did anyone connect thru telnet?
Have you had any performance issues with this connection?
Any issues setting up the connection, or tuning done for the sole reason
that it worked with it, but not without it?
Do you have a significant number of users connecting to the 3000 across
token ring?
What kind of volume do you see, how much traffic?
Were they accessing across a LAN or a WAN? If a WAN, were there any
issues with bandwidth or speed? Was there any frame relay in the mix?
Were they pure token ring, or did you have Ethernet as well? (Our local
PC LAN is Ethernet, and our LAN segment for our hosts is token ring.)

As for why I am asking, we see a single client office using telnet and
failing intermittently during high traffic hours (bad enough to keep
from deploying), going across a huge corporate WAN, into a router, onto
the token ring segment, where live our various hosts, including our HP
3000. Months of tracing, network analyzering and sniffering, and
application debugging later, we have determined that data that the
application appeared to be sending to the client application, never
appears on the local token ring segment. HPRC and three other groups
have looked at traces and memory dumps, and are again, trying to figure
out where our data is getting lost. Correspondence with another token
ring user suddenly made me ask, perhaps it's not telnet, nor TCP, but
the token ring driver, or the card itself (at the moment, that is my
biggest concern - it is not an HP card, nor a name that I recognize).
Thus my posting.

Thanks again.

ATOM RSS1 RSS2