I’ve mentioned before that, despite being on the Routing Protocols team, I spent a lot of time handling crash cases in TAC. At the time, my queue was just a dumping ground for cases that didn’t fit into any other bucket in the High Touch structure. Backbone TAC had a much more granular division of […]
Category: TAC Tales
TAC Tales #19: Butt-in-Chair
This one falls into the category of, “I probably shouldn’t post this, especially now that I’m at Cisco again,” but what the heck. I’ve often mentioned, in this series, the different practices of “backbone TAC” (or WW-TAC) and High Touch Technical Support (HTTS), the group I was a part of. WW-TAC was the larger TAC […]
TAC Tales #18: All at once
The case came into the routing protocols queue, even though it was simply a line card crash. The RP queue in HTTS was the dumping ground for anything that did not fit into one of the few other specialized queues we had. A large US service provider had a Packet over SONET (PoS) line card […]
TAC Tales #17: Escalations
When you open a TAC case, how exactly does the customer support engineer (CSE) figure out how to solve the case? After all, CSEs are not super-human. Just like any engineer, in TAC you have a range of brilliant to not-so-brilliant, and everything in between. Let me give an example: I worked at HTTS, or […]
TAC Tales #16: To microburst or not to microburst
I’ve mentioned before that EIGRP SIA was my nightmare case at TAC, but there was one other type of case that I hated–QoS problems. Routing protocol problems tend to be binary. Either the route is there or it isn’t; either the pings go through or they don’t. Even when a route is flapping, that’s just […]
TAC Tales #15: Loopy
I’ve mentioned in previous TAC Tales that I started on a TAC team dedicated to enterprise, which made sense given my background. Shortly after I came to Cisco the enterprise team was broken up and its staff distributed among the routing protocols team and LAN switch team. The RP team at that time consisted of […]
TAC Tales #14: Stuck in Active
Everyone who’s worked in TAC can tell you their nightmare case–the type of case that, when they see it in the queue, makes them want to run away, take an unexpected lunch break, and hope some other engineer grabs it. The nightmare case is the case you know you’ll get stuck on for hours, on […]
TAC Tales #13: All Zeros
A common approach for TAC engineers and customers working on a tough case is to just “throw hardware at it.” Sometimes this can be laziness: why troubleshoot a complex problem when you can send an RMA, swap out a line card, and hope it works? Other times it’s a legitimate step in a complex process […]
TAC Tales #12: SACK of trouble
When I first started at Cisco TAC, I was assigned to a team that handled only enterprise customers. One of the first things my boss said to me when I started there was “At Cisco, if you don’t like your boss or your cubicle, wait three months.” Three months later, they broke the team up […]
TAC Tales #11: Full up
No customer is happy if they have to reboot one of their Internet-facing routers periodically, and this was one of our biggest customers. (At HTTS, they were all big customers.) This customer had a GSR connecting to the Internet, with partial BGP routes, and he kept getting this error: %RP-3-ENCAP: Failure to allocate encap table entry, […]