Evyone Sharp highlights just how fragile the operational state of Cisco software is today because of poor software design.
We’ve all been there. You make a simple configuration change that should have no impact on production traffic. Suddenly your phone begins to ring, or worse, you lose access to the equipment you were working on.
Here are some common mistakes network engineers make on Cisco gear that cause unexpected outages.
- Forget the add command when adding a vlan to a trunk port.
- Run no ip access list on a Cisco Router like you would on an ASA firewall.
- Issue a global spanning tree command instead of an interface specific command.
Now that I’m standing further away from the day-to-day fear of breaking a Cisco network I can see more clearly just how badly designed Cisco software is.
9 Easy Ways to Break a Cisco Network : http://www.esharp.net/9-easy-ways-to-break-a-cisco-network/