After finishing projects on PRTG, I was assigned to a new project regarding creating a documentation on Emergency Switch Recovery. The documentation aims to prepare the IT team for cases when a switch go down and it will provide step-by-step instruction on doing the recovery.
There are several things to keep in mind in this project, firstly, the test should not be done in the production line. The tests will ensure that the switch configuration files could be transferred to the switch properly and would be able to load configuration of the failing switch. Secondly, the workflow would be to transfer the file using FTP from the FTP backup server. However, to have to test with the FTP backup server, the switch has to be inside the production line which currently will not be able to be done.
My supervisor will try to get in touch with the network administrator of NPIL to try get some insight on how to proceed with the testing of the emergency recovery. But for now, the tests will be done in isolation without getting in contact with the production line.
Thus, there will be two parts in the documentation which will be created. The first one would be the best case when a switch is down and the FTP backup server is accessible. The second one would be the case when a switch is down and the FTP backup server is inaccessible.
The second method would be the one that I looked into this week. That is the case when the team already have the configuration file in a local PC and will be transferred to the switch through terminal. The communication will be executed from a console port from that PC.
Next week project would still cover more on the switch backup system and if done, my supervisor recommended me to look more into a backup software Veeam.
Marcellus's Blog 