Thread regarding Cisco Systems Inc. layoffs

why we should not and can not replace TAC

Recently, we noticed there are more and more huge network outages. Why do we have this kind of serious problems again and again? The answer is very simple, because there's some kind of progressive idea that traditional networking knowledge are outdated and can be replaced by automation. So they hired some software engineers who don't have enough networking knowledge and let them touch the network. And we all have seen the results.

In this world, we need to have a real trade skill to survive and contribute to the society, it can be software programming, it can be networking knowledge, it can be management, or cooking or just toilet cleaning. But if one only have just a little knowledge and experience but not solid on anything. Then one can only cause bad results for oneself and organizations.

Cisco TAC is the best and real technical consulting service out there, it serves our customer needs very well. We help them on network specialties and they can focus on automation as they want. Please don't try to destroy it using some empty pictures. The market is realistic. For example, has anyone landed a better job from your DevNet? Why? because the market doesn't recognize it. Those MS, Google, AMZ managers and seniors have enough experience to tell how deep your software skills are. We need to have good leadership like Mr. Holloman back and hire some great leadership with real software experiences such as Jeff Weiner. Otherwise, we will be in huge trouble. Please don't try to use so called flexible rotation to replace US TAC, with the coming chaos world, we need to have a strong TAC in US for national security reason.

by
| 2290 views | | 8 replies (last ) | Reply
Post ID: @OP+1iCx1pq4

8 replies (most recent on top)

@7zyi+1iCx1pq4 start actually working and they won’t have to call your lazy a-s

by
| | Reply
Post ID: @7jhm+1iCx1pq4

My team has decided to never respond to annoying HTOMs or SEs harrasing us while we are working on issues. They dont add anything other than make you lose focus.

by
| | Reply
Post ID: @7zyi+1iCx1pq4

Customer facing roles at Cisco generally involve getting shot in the face by customers and getting shot in the back by the rest of Cisco.

My calls to TAC are all due to bad software and bad documentation. These are unforced errors and instead of advancing the customer experience they’re left trying to fish it out of the cr----r. Budgets and hiring become based on this and everyone loses.

by
| | Reply
Post ID: @5vhb+1iCx1pq4
@liq+1iCx1pq4 - It's a lot more complicated than a misconfigured trunk or VLAN

If this is all you think TAC does, you've either been "that" Customer who's called up for that type of problem and really have no idea the level of detail some TAC Engineers go to.

by
| | Reply
Post ID: @3cnu+1iCx1pq4
@liq+1iCx1pq4 says: It's a lot more complicated than a misconfigured trunk or VLAN

Right, so don't chop the legs from out under TAC. Right at the time you need a strong and skilled workforce troubleshooting your hacked together code and products (Like DNAC) that are still missing some of the features of Prime and literally sh-t the bed when asked to do basic operations.

Your Automation tools and SE's cannot help your end customers if they're too busy working on $nextBigThing to either write stable code or write the correct introspection tools in the product to self troubleshoot.

They might not have all the answers, but a cool level headed approach from a TAC Engineer is far better than a bunch of Customers shooting from the hip trying to solve a problem.

by
| | Reply
Post ID: @3ykn+1iCx1pq4

Heh heh you said wiener

by
| | Reply
Post ID: @rlg+1iCx1pq4

A senior network engineer acquiring a decent development skill set can easily demand 200k in todays market. I know of several that are making 300k+. All outside of the Bay Area.

I agree that a development skillset, as it relates to systems engineering, should serve a secondary role.

Additionally, the market demands these skills due to the increasing complexity, size, and performance requirements of modern networks. There’s simply not enough people interested in network engineering, nor the budgets, to keep pace with demand.

by
| | Reply
Post ID: @frv+1iCx1pq4

Things are way more complex than 10 years ago. Automation, ACI, SDA, DNAC, Vipetla, AWS, Azure, etc. They are a lot of moving parts and many things that can go wrong that are very hard for even experts to troubleshoot. When things blow up big nowadays, TAC resources would be hard pressed to figure it out. It's a lot more complicated than a misconfigured trunk or VLAN.

by
| | Reply
Post ID: @liq+1iCx1pq4

Post a reply

: