The trouble continues in Trimble Hall. A malfunction occurred with the same symptoms. We have isolated the problem to the switch in Trimble 007. We disconnected the TH network piece by piece while monitoring connectivity with ping. When the 007 switch was disconnected, connectivity returned. Upon reconnecting the 007 switch, the network maintained connectivity. We will have to wait until the next failure to isolate the trouble to a specific port on that switch.

The Trimble Hall problem continues with a similar malfunction this afternoon. Jim dropped the Trimble Hall uplink to 10 Mbps, which cleared the problem.
Continue reading →

The network in Trimble Hall malfunctioned again, causing campuswide network slowdowns. It appears that rebooting any switch in Trimble will clear the problem. This time, the switch in Trimble 007 was rebooted.

A switch in Trimble Hall 107 malfunctioned and caused a traffic flood into the rest of the network. Trimble Hall was disconnected from the network for approximately 1 hour while the issue was resolved. A reboot of the switch solved the problem.
Continue reading →

Webboard hung. To correct the problem, the machine was rebooted.

We have been struggling with a faulty disk array on tahoma. Compaq service was on site, and replaced a faulty connector cable. The disk array is functioning normally.

The Webboard server was rebooted to re-enable access.

The database servers, tahoma & baker, and the frontend forms servers snidley, dudley, and fenwick, began dropping persistent client Oracle and telnet connections. ICMP packets were also lost.

Speed and duplex settings on the switch ports to which these servers were connected were checked and found to be correct (100 Mbps, full duplex).

The problem cleared up after about 1 hour. Will check further.