Been staring at the wiring diagram and realizing just how much I can get done/rule out with good old fashioned caveman techniques.
That tends to work best and teach you the most anyway.
I cannot COUNT the number of "IT engineers" I've worked with in 30+ years
who use all kinds of fancy software and high end network diagnostics tools, and simply go with whatever the tool/software says is wrong.
About 50% of the time, that's just the topmost symptom discovered by the tool or software. There's an underlying reason.
Just today I was working on why some IP phones would not power up
and others would, and the problem moved around the office involved from day to day.
The younger engineer whipped out his Fluke LanMeter and started checking things. He got a couple of cables that didn't test at 100% for each test he ran. So he decided it was patch cables, and tossed out $50 in cables
and started re-wiring wall jacks.
Meantime, I thought it odd that the problem moved around, but was always 4-5 phones working, but never all 12.
So I checked the switch, found the fan running at half speed, full of dirt, checked the power supply stats at the command line, and found that the switch had cut back the PoE power by half because the powersupply was overheating due to it being just as dirty as it's fan was.
Cleaned everything, and re-seated all the connectors.
All 12 phones booted up.
Yell comes from the other room "What did you do! "
I still haven't told him....that his Fluke won't measure dirt....literally...
