tag:blogger.com,1999:blog-3993498847203183398.post6435168654679903129..comments2024-03-28T09:19:27.451+00:00Comments on RevK<sup>®</sup>'s ramblings: Replacing switchesRevKhttp://www.blogger.com/profile/12369263214193333422noreply@blogger.comBlogger2125tag:blogger.com,1999:blog-3993498847203183398.post-7795642561228432832016-03-24T10:28:54.173+00:002016-03-24T10:28:54.173+00:00It seems to have worked rather well? Line dropped ...It seems to have worked rather well? Line dropped for a bit, but not that long...Anonymoushttps://www.blogger.com/profile/18427000118752159232noreply@blogger.comtag:blogger.com,1999:blog-3993498847203183398.post-6314922960614479522016-03-21T13:45:42.763+00:002016-03-21T13:45:42.763+00:00Sounds a bit better than when someone at work has ...Sounds a bit better than when someone at work has to do a horrendous patching job, and then it turns out that there's a design flaw in there somewhere. Good luck figuring that one out! (Please don't ask us to check the same thing 5 times like one customer did; it's still correct just as it was the last few times)<br /><br />What's also fun with L1 troubleshooting is trying to trace mislabelled cables that go under the floor. By "fun", I really mean "not happening as it's out of scope for me".<br /><br />Then there's the time a customer sent through a blatantly incorrect config where the IP and gateway where in a different subnet, and this was obvious at a first glance since it helpfully was using /24. After mentioning that this needed fixing as it would never ever connect, I get a somewhat snooty response.<br /><br />The next day, the customer meekly emailed the corrected details. Turns out network engineers can spot the most basic config errors. Who knew!Ferrocene Cloudhttps://www.blogger.com/profile/03811061917059971410noreply@blogger.com