[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: Debian And Advanced Layer3 9924T

Ron Johnson put forth on 4/6/2010 5:18 AM:
> On 2010-04-06 02:08, Andreas Weber wrote:
>> On 2010-04-04 01:42, Stan Hoeppner wrote:
>>> Telling the OP to throw out a multi thousand dollar 24 port managed GigE
>>> switch due to a minor issue with one PC or server is not very sage
>>> advice.
>> I said "try changing", not "throw out" (reading and quoting is a basic
>> skill). Having sold many _multi-thousand-Euro-switches_ let me tell you
>> that they can be broken right from the start. DOA should ring a bell. A
>> simple temporary change of the switch (often the replacement is provided
>> by the vendor) would immediately show if this could be the problem.
>> It's a bit of a general problem on lists like this one (very technical
>> ones) that some very smart people dislike simple straight forward
>> solutions to be checked first, although it happens all the time that
>> smart people stumble over simple problems. Instead they like to tell
>> other people they're not sage enough.
>> So sorry for my "Is the cable ok?" approach as a first aid, I will keep
>> my mouth shut now, knowing that there's a savvy elite around.
> Stan definitely did not exercise sufficient reading comprehension.
> Adding the word "temporarily" would have reduced all ambiguity, though.

This isn't an issue of my reading comprehension.  I fully understood what
Andreas wrote.  I simply disagree with his recommendation.

I'm not sitting in the OPs lab or at his desk.  However, it seems clear that
one way or another he is going to have to go through that Allied Telesis
managed switch.  So, temporarily swapping out the "switch" doesn't seem a
real option.  Sure, he could uplink an el cheapo non managed switch sitting
on his desk through the wall jack to the Allied Telesis switch in the
closet, and then plug the Debian box into the temporary dumb switch, but
he'd likely still have the same issue if indeed the original problem is VLAN
related or if there's a dead PHY on that particular port on the AT switch.
He could always re jumper the patch panel to a different port on the AT.
That would have been my next recommendation if he couldn't solve it via
programming the current port.

There are many possible scenarios on how the OPs network is setup.  He could
already have the AT switch sitting on his desk.  Regardless, the first
troubleshooting step should be to check the VLAN programming on the switch,
and specifically the port he is jacked into.


Reply to: