It¹s across a wide variety of clients. My guys always check layer1
before they do much of anything. We fixed two just yesterday which were bad
patch cables.
We always reference the following article when we bring a new guy on:
http://www.iphelp.ru/faq/24/ch16lev1sec1.html
I have seen guys spend hours troubleshooting configurations that have
not changed in 6 months, do memory tests, and all sorts of things. Then a
jumper is replaced and all is good. My only point is start at the bottom of
the OSI model and work up if nothing has changed.
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: Josh Luthman <[email protected]>
Reply-To: WISPA General List <[email protected]>
Date: Sun, 5 Dec 2010 22:23:10 -0500
To: WISPA General List <[email protected]>
Subject: Re: [WISPA] You would think after 20 years we have this down.
I don't think 1% accounts for those in my experience. Wonder what you're
doing differently.
On Dec 5, 2010 9:52 PM, "Justin Wilson" <[email protected]> wrote:
> 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/
--------------------------------------------------------------------------------
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/
