Taking down a network is not the end of the world. 1 * * * 2 * * * 3 * * * 4 * * * 5 * * * 6 * * * 7 * * * 8 * * * 9 * * * 10 * * * 11 * * * 12 * * * 13 * * * 14 * * * 15 * * * 16 * * * 17 * * * 18 * * * But it could be the end of your job. Don’t feel bad. We’ve all been there.pic.twitter.com/KlPYklJndH
-
-
Prikaži ovu nitHvala. Twitter će to iskoristiti za poboljšanje vaše vremenske crte. PoništiPoništi
-
-
-
#NetworkEngineerProTip Mistakes happen. Here’s some tips to help prevent them. 1. Create a workplan that has your verification and configuration steps. 2. Have your workplan peer reviewed. 3. Create a blackout plan just in case. 4. Backup the current config 5. Have a Co-pilotPrikaži ovu nitHvala. Twitter će to iskoristiti za poboljšanje vaše vremenske crte. PoništiPoništi
-
-
-
Oh man. Where to even begin. I've killed NIPRnet, and as a result SIPRnet, for half of USAFE Taken down many branch offices until I could get someone out to reboot the switch/router because of all kinds of mistakes Apparently it's been >10 years now, and it adds up lol
-
Man U did that. I was stationed there when that happened lol.
- Još 1 odgovor
Novi razgovor -
-
-
This might be the best thing on twitter right now
-
It’s the most refreshing thread can remember reading in years
- Još 1 odgovor
Novi razgovor -
-
-
Yes! Was upgrading a pair of nexus 5ks. One rebooted as expected but when it came back up, the Peer link never recovered so they went into a split brain situation. Datacenter was out for 20 minutes

-
The longest 20 minutes ever lol.
- Još 2 druga odgovora
Novi razgovor -
-
-
I have not but I did take down a server once
-
Same thing. I bet that was stressful.
- Još 1 odgovor
Novi razgovor -
Čini se da učitavanje traje već neko vrijeme.
Twitter je možda preopterećen ili ima kratkotrajnih poteškoća u radu. Pokušajte ponovno ili potražite dodatne informacije u odjeljku Status Twittera.