LISTSERV - HP3000-L Archives

HP3000-L Archives

July 2008, Week 4

HP3000-L@RAVEN.UTC.EDU

	LISTSERV Archives
	HP3000-L Home
	HP3000-L July 2008, Week 4

	Log In
	Register

	Subscribe or Unsubscribe

	Search Archives

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 >>]

Subject:	FW: [HP3000-L] network oddity again...
From:	james hofmeister <[log in to unmask]>
Reply To:	james hofmeister <[log in to unmask]>
Date:	Thu, 24 Jul 2008 05:02:21 -0400
Content-Type:	text/plain
Parts/Attachments:	text/plain (22 lines)

-----Original Message-----
From: james hofmeister <[log in to unmask]>
Sent: Thursday, July 24, 2008 4:44 AM
To: [log in to unmask]
Subject: RE: [HP3000-L] network oddity again...

Hello all

The linkcontrol crc errors could be unrelated to the current problem.

1- linkcontrol dtslink;status=reset
2- start job to linkcontrol dtslink;status=all and showtime every 10 minutes.
3- record dates / times of problem/events and compare to linkcontrol dtslink;status output in step 2 above.

Note: crc errors are a hardware problem, suspect parts are: external transciever, ethernet cables, electrical interference on ethernet cables, switch port, switch, ethernet network interface card (nic) in system.  Fyi: Troubleshoot in the above listed order, the 3000 nic are not a frequently failing part.

regards,   james hofmeister
big thumbs, little motoQ9 keyboard, my other desktop is ubuntu with evolution and open office! 

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

ATOM RSS1 RSS2

RAVEN.UTC.EDU