Could indicate a bad port on the procurve module, or a bad port on the
N. any other ports on thw switch seeing errors?

Troubleshooting::
- move N xonnection to another switch port. If fixed, bad port on
switch. Replace module. If not:
- reboot switch. If fixed, indicates possible switch firmware problem.
Update. If not:
- reboot N. If fixed, indicates N software problem. Check for patches. If not:
- replace network cable. If fixed, throw out old cable. If not:
- N NIC problem. Replace.

On 1/27/11, John Pitman <[log in to unmask]> wrote:
> Its now reporting excessive crc and late collisions on the N series
> connection?
>
> Stop and restart network soon, or is it a sign of something more serious?
>
> Regards,
>
> John Pitman
>
> ________________________________
> CAUTION: This message may contain privileged and confidential information
> intended only for the use of the addressee named above. If you are not the
> intended recipient of this message you are hereby notified that any use,
> dissemination, distribution or reproduction of this message is prohibited.
> If you have received this message in error please notify RYCO Hydraulics
> Pty. Ltd. immediately. Any views expressed in this message are those of the
> individual sender and may not necessarily reflect the views of RYCO
> Hydraulics Pty. Ltd.
>
> * To join/leave the list, search archives, change list settings, *
> * etc., please visit http://raven.utc.edu/archives/hp3000-l.html *
>

-- 
Sent from my mobile device

"He's old enough to know what's right and young enough not to choose
it. He's strong enough to win the world and weak enough to lose it." -
Neal Peart

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