In my experience the first thing we always check is layer1. 80+% of our
logged tickets can be traced down to bad cat-5, bad crimps, poor patch
cables, etc.
Justin
--
Justin Wilson <[email protected]>
Aol & Yahoo IM: j2sw
http://www.mtin.net/blog xISP News
http://www.twitter.com/j2sw Follow me on Twitter
Wisp Consulting Tower Climbing Network Support
From: Rubens Kuhl <[email protected]>
Reply-To: WISPA General List <[email protected]>
Date: Mon, 6 Dec 2010 00:35:52 -0200
To: WISPA General List <[email protected]>
Subject: Re: [WISPA] You would think after 20 years we have this down.
> We recently upgraded a link and started having some packet loss. Looking at
> the manged switch, it was obvious the CMM on that tower was getting ethernet
> errors. Auto negotiation on GigE switches is flaky as hell. This is the
> second time in a month I've had to hard code both ends. This has occurred
> on both Cisco and HP Procurve hardware.
GigE auto-neg not working is a hint pointing to bad cable,
interference and/or defective hardware. Unlike Fast-Eth, Gig-E autoneg
works and you lose link quality monitoring by disabling it.
Rubens
----------------------------------------------------------------------------
----
WISPA Wants You! Join today!
http://signup.wispa.org/
----------------------------------------------------------------------------
----
WISPA Wireless List: [email protected]
Subscribe/Unsubscribe:
http://lists.wispa.org/mailman/listinfo/wireless
Archives: http://lists.wispa.org/pipermail/wireless/
--------------------------------------------------------------------------------
WISPA Wants You! Join today!
http://signup.wispa.org/
--------------------------------------------------------------------------------
WISPA Wireless List: [email protected]
Subscribe/Unsubscribe:
http://lists.wispa.org/mailman/listinfo/wireless
Archives: http://lists.wispa.org/pipermail/wireless/
