HP3000-L Archives

September 2008, Week 1

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:
Tom Hula <[log in to unmask]>
Reply To:
Date:
Wed, 3 Sep 2008 12:08:32 -0400
Content-Type:
text/plain
Parts/Attachments:
text/plain (39 lines)
Today, things seem to be back to normal on our network.
I'm still trying to figure out what happened.

I did verify that the port on the managed switch was setup
as 100 full duplex with auto-sensing on, same as I have
it defined on the HP.

At one point, after power cycling everything once again
and rebooting the HP, it ran fairly well in the afternoon,
although there were still pockets of trouble, like I couldn't
basically get to the HP from my PC. When I tried pinging,
it would either time out or give me these crazy settings.
On one try, the first ping was over 3,000 ms and then
the second try was 22 ms and then the third was over
2,000 ms and the fourth was around 64 ms. People
would sometimes get booted off, but would be able
to get back on to work.

I ended up working until 3 am making sure month end
finished up and fixing some problems that arose.
At 3 am I power cycled all the network hardware and
rebooted the windows server and the HP.

For some reason, everything is operating within
normal parameters and pings look normal.
Sunspots? Solar flares? So far, not sure what
is different. A local service is going to set up
a sniffer, but I have a feeling there is nothing
to sniff at this point. But just as sure it will
happen again. Hey, I know what it is...first day
of school. Something about negative energy.

Thanks for all your responses.

Tom 

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

ATOM RSS1 RSS2