How to avoid resume-generating events

I was recently reminded of an important thing when working with any production environment. Wanting to learn as much as possible, we often practise on rack rental equipment and because we want to be as quick as possible, we don’t shy away from clearing neighborships with other routers (clear ip bgp *), changing roots for STP, shutting down entire ranges of ports etc. Because we want to be quick and develop habits, like :

int gi0/1

spanning-tree host

int range Gi0/2-20




spanning-tree vlan 1-4094 root primary


, we sacrifice the overall view of how the change will impact the network. Thus we type like crazy because the clock is tick away tick tock tick tock.

In a lab environment this is ok, because nobody will be affected by the change. However, habits have a way of persisting. Therefore, it is vital to really think through the impact of each command that is typed in a production environment. You want to keep your job right?

  1. Think what you want to achieve
  2. Draw a diagram
  3. Think what commands you will want to use
  4. Think about their impact. Will there be disruption? If yes, notify users + prepare a backup/backout plan.
  5. If possible, consult a colleague.
  6. Put on a pair and type in the commands.
  7. Document your changes.


I’ve seen more than one situation where only point 6) was followed.



Wprowadź swoje dane lub kliknij jedną z tych ikon, aby się zalogować:


Komentujesz korzystając z konta Wyloguj /  Zmień )

Zdjęcie z Twittera

Komentujesz korzystając z konta Twitter. Wyloguj /  Zmień )

Zdjęcie na Facebooku

Komentujesz korzystając z konta Facebook. Wyloguj /  Zmień )

Połączenie z %s

%d blogerów lubi to: