This post was originally published on ZPE Systems
My name is Ahmed Algam. I am an IT & Systems Administrator for ZPE Systems – A Brand of Legrand, with over 20 years of experience in network administration, system infrastructure, Microsoft ERP solutions, and enterprise IT management. I have a B.S. in Computer Science and will soon complete my Master’s of Information and Data Science.
Every IT person knows that network updates are routine. Sometimes they can work perfectly, and other times, the update messes things up and you have to roll back to the last good configuration.
But what do you do when the rollback goes wrong?
Here’s my first-hand experience with this exact scenario.
We recently implemented what was intended to be a routine update for our engineering network. The change timeframe, internal signoff, test coverage, and rollback strategy were all set up. Every step was even pre-documented. The setup was textbook.
But if you’ve been in IT for more than five minutes, you know that upgrades don’t always fail in the first stage.
The initial steps had gone smoothly and we had a sense of confidence. But midway through, this one failed. It damaged a core routing service and stopped our ability to reach our remote sites.
— Read the rest of this post, which was originally published on ZPE Systems.
