@networkengineeryangsir: 4 hours buried in CLI, routes, and packet tracers😭……Got completely destroyed by a loose Ethernet cable 🫣 #networkengineer #serverroom #itlife #Tech #networking

Woodyspin :

I once had an issue where 3 separate people checked the cable was fully pushed in... still no network. after 3 hours I unplugged it, and plugged it back in within less than a second. started working. pls explain.

Mstrksh :

start at layer 1 homie

Abdullah Gondal :

The step supposed to be checked at first

Funfan342 :

You laugh at that, but I noticed one of the interns installed a cable between 2 switches right before the network went down. I, also an intern with a CCNT cert, asked of the network administrator set up BPDU filtering. I was told I was an idiot as I watched the switches lock up. Network was down for 4 days on those two switches. The fix? The network admin disconnected the patch cable causing the traffic. He never did set up the bpdu guard. We had a weekend project to clean up the patch runs and set up some new vlans for VoIP phones, and I intentionally went to the main floor, and plugged a patch cable into 2 neighboring jacks (with permission from the IT director who understood my findings) to test the net admin to see if he could figure it out without causing downtime as we were all cutting cables anyway. He just kept blaming the cable cutting, refusing to even look at the logs reporting the bpdu traffic. I was awarded with a conversion to FT and showed the other admin how to set it up.

Timothy Davis :

damn bro, if im logged into the switch, ITS PLUGGED IN

romeblanc :

Lolllll everyone saying start at level one I mean we know duhhh but when you have so much to do and you’re trying to fix something big some days you definitely skip straight to logical connectivity 😭 if you say you haven’t don’t it you’re lying

Vengeance Gaming :

😂 The PSU was never connected to any of the devices....its been chargin for nothing

seinfeld :

and he was correct

Kael :

That is the basic, no?

Mike :

I have been both. Even had a special case, though it was at home. Desktop wouldn't power on. Checked both sides to confirm they hadn't come loose. Both ends were snug The cable about 7" from the computer side however got separated.

RedbeardWV :

Start at layer 1 and work up bro

الذكاء الاصطناعي للأعمال :

what cable?

jackxattack :

Got called to a client because a remote tech couldn’t find the issue when communicating with the customer over the phone and FaceTime. Got there. The main plug from switch to the sonicwall was unplugged

Spammith :

Konstantinos Daras :

did you check the power supply cable

Ryckie :

Did you though?? 🤔

Fiction :

we all losing it fr fr 🤣

MartrimCauthon :

Or in our case... Apparently our network connection just kills our 20+ YO tool when it pings if it's connected...

Lucky :

If you don't learn the mac address of the equipment check cabling

Network Engineer Yang :

I cringe thinking about this🤣 Always check cables first! Share your dumbest troubleshooting fails below👇

海姿 :

bro really do 1st level checking

Allen Melhorn :

Do you know how many times I have been on site and a huge issue was caused by something being unplugged, hours of troubleshooting and a fresh set of eyes walk up oh this is unplugged and resolve the issue. The more experienced we become the less we pay attention to the simple things

_marly690_ :

Solution: They just didn't pay the internet bill👍

user074168692 :

he didn't check

NetPositive :

needs more redundancy