by Arlos » Thu May 26, 2005 3:26 pm
I used to work Tech Support for many years, and have my own set of horror stories to tell. I've also worked for Mindspring doing business internet installation turnups, and as a result have had to talk to techs at pretty much every single major Telco corporation (AT&T, Sprint, MCI, UUNet, US Worst, NYNEX, Bell South, Pac Bell, etc. etc. etc.)
Some of the people who I've gotten on calls, it surprised me they were able to breathe without outside intervention, they were that stupid. And actually, they're not the worst ones. The WORST ones are the ones that know just enough to be dangerous, but think they're absolute experts. They argue with you at every step, even if you know exactly what the issue is, and often would try and "anticipate" what you were going to tell them to do, and do 3 or 4 steps on their own without saying anything, usually making things worse, and making it impossible to actually fix anything. Not to mention, the problem usually came from them fucking around with something they shouldn't have, and breaking everything.
Of course, some of the times I've called in to an ISP, I've gotten raving idiots too. When I had Cable modem a while back, I was having bad latency, and seeing a lot of packet loss. So, I grabbed my trusty Win-MTR (great program), and documented their network issues, starting with the first box my cable modem connected to. I was averaging 20% packet loss to that first hop router, and ping times to it of > 100 ms, and the tech tried to tell me "Oh, that's normal". Riiiiight.
As for telcos, even when I was placing a call to supposed upper level techs, which I got to do by being a tech at an ISP that was buying circuits from them, I ran into some seriously spectacular idiots. I once spent 2 hours on a phone with someone from Bell South, while trying to turn up a T-3 for a new Internap site, before we finally figured out that Bell South had somehow managed to terminate the T-3 to the wrong *TOWN*. Not the wrong cabinet, not a failed cross-connect at the demarc, the wrong entire TOWN. I can't imagine the level of incompetance their first line tech people must have had, if their techs handling such high end stuff as dedicated T3s are that big of fuckups.
Even at other networking jobs, you can't get away from talking to ISPs and Telcos, unfortunately. Even if you do enough business to get a semi-dedicated account manager assigned to you, trying to get knowledgeable and timely tech help can be iffy at best. And you just TRY and find someone at AT&T/CERFnet at 4 in the morning who can make BGP updates on an emergency basis, cause someone there screwed up and started passing you routing advertisements, while partially blocking yours, with the upshot of anyone trying to reach you from AT&T space can't because the AT&T routers are giving them a route that goes to a black hole, and it needs to work NOW because there's several hundred thousand dollars worth of business from conferences scheduled that morning, starting on the east coast in an hour.... Yeah, that was fun.
How some of these techs stay employed, while I'm sitting here looking for work, I have no goddamn idea. *grumble* heh.
Edit: Oh, and don't get me started on AOL. I once spent > a week straight in 8-10hr a day meetings at their HQ for a project when I worked at Oracle. Their internal network/data center setup was the biggest kludge I have ever seen in my entire life. You just know you're in for a long week when they show you the network diagram, and there are things on it labled (I shit you not) "Tater-TOTs"....
-Arlos