I'm trying to layout a process which will enable us to quickly setup a replacement unit when a switch fails.
For example, we have lots of 3560 switches, so we have a few of them lying around as spares. My goal is to have a spare 3560 already hooked to some lab subnet, managed by LMS, and already with a current IOS, so that when a production 3560 dies, I can just push its config to the spare and proceed to replace the failed unit with the spare, now running the same config.
Setting up the spare, managing it with LMS and upgrading the IOS is no problem.
However, I'm trying to find a quick and easy method to deploy the config of a dead switch to the spare. Idealy what I would like is a "Take that config and deploy it there" button but I haven't found it.
The deploy button in the config editor for the dead device only lets me deploy to the same device (not helpful since I would have to reconfig my spare to be able to receive the new config). I've also tried saving the dead config to the "Public" space in Config Editor, and then try to deploy it from there, but it's still bound to the dead switch so I can't deploy it to another device.
The only idea I have left is to copy (CTRL-C) the config from the dead switch, edit the config of the spare, paste over it, and deploy that. Is that really the most efficient way to do this in LMS 3.1 ?
Also, if LMS 3.2 offers new features in this area, please do tell!
Thank your very much!