HP3000-L Archives

December 2001, 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:
"HOFMEISTER,JAMES (HP-USA,ex1)" <[log in to unmask]>
Reply To:
HOFMEISTER,JAMES (HP-USA,ex1)
Date:
Mon, 17 Dec 2001 23:59:46 -0500
Content-Type:
text/plain
Parts/Attachments:
text/plain (84 lines)
hello folks @ 3000-l,

re: Weird problem on HP3000 (not really)

-----------------------------------------------Greg Terterian writes--
I have a customer that has 20 workstations.   Every 5-10 minutes
people are getting logged off automatically by NS/VT (everybody is
running TCP/IP connections using VT-MGR (streams 1570 TCP port).  It
is very inconsistent and hard to pinpoint as what is going on.  We
have checked all the stations to make sure that they are running on
10mbits half duplex (I remember long time ago we had similar
scenario and it was because one of the stations' network card was set
to Auto...).  We rebooted the system, stopped the JINETD (Which should
not have to do anything with VT-MGR anyway), recycle the power on DTC
and the HUB.   Any ideas as where else should we look???
----------------------------------------------------------------------

The problem you describe is not really "weird", as the network
engineers in the HP Response Center face and solve a wide variety of
network problems in unique environments and configurations every day.

I would start by enabling the NS-Transport logging, :switchnmlog
update and then monitor the network until the next failure and then
record the date/time the problem is seen.

With the logging enabled, the Response Center engineers can then
evaluate the errors logged at the date/time the problem was reported
and give you a solution or feedback on the network problems found.

The NS-Transport logging is found in NMMGR:

:nmmgr
[open config]
[ns]
[unguided config]
[go to logging]

----------------------------------------------------------------------
           Class    Console Disk
Subsystem  Name     Logging Logging  Event


SUB0003    CLAS0001  [Y]     [Y]     Serious internal error
Network    CLAS0002  [Y]     [Y]     Internal error/operator attention
Transport  CLAS0003  [N]     [Y]     Non-critical errors
           CLAS0004  [Y]     [Y]     Nodal messages (start/stop)
           CLAS0005  [N]     [Y]     Informative messages
           CLAS0006  [N]     [Y]     Statistical information
----------------------------------------------------------------------

Specify "Y" for Disk Logging for all "CLAS" for "SUB0003" - Network
Transport.

[save data]
[validate netxport]
(Press RETURN when done viewing screen contents)
[prior screen]
[prior screen]
[prior screen]
[prior screen]
[exit program]

:switchnmlog update

I hope this helps.

P.S. You might also want to consider the recommended general release
patches for NS-Services, NS-Transport and the Buffer Manager which are
the primary subsystems involved in your problem:

NSSFDA5 for C.60.00
NSTGD19 for C.60.00
NMSFDQ9 for C.60.00

Regards,

James Hofmeister
Hewlett Packard
Worldwide Technology Network Expert Center
P.S. My Ideals are my own, not necessarily my employers.

* To join/leave the list, search archives, change list settings, *
* etc., please visit http://raven.utc.edu/archives/hp3000-l.html *

ATOM RSS1 RSS2