MIBS, SMMPv1, SMMPv2, SMMPv3 and management
Hello gurus, 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!Alex.
This feature exists in LMS 2.5 and higher. There are a lot of ways of getting to it, but the easiest is probably just to go to RME > Config Mgmt > Archive Mgmt > Version Tree, and select the device and desired config version (this assumes the new device is already online, and has the same name and IP as the device it is replacing).When the config is open, you'll notice a DEploy button in the bottom right-hand corner. Click that button, then select to do a Merge deployment. After that, the new device will have the same config as the device it is replacing.
Hi JClarke and thanks for the quick reply!I'd like to be able to do that without requiring the spare device to be pre-configured with the dead device's ip address. The new physical location of the switch may be totally different, so I couldn't push the config until the device is physically moved to it's destination. And if I have to manually configure the switch (IP addr) to push its config from LMS, I'll just copy and paste the config and skip LMS!You mentionned "there are a lot of ways of getting to it", could you suggest another that doesn't require the new device to be preconfigured with the old devices ip/credentials ?Thank you!Alex.
No, this is not possible. RME does not yet support a zero-touch deployment. This feature is being considered for the next release of LMS, but may require the Config Engine to make it happen.When I said there are multiple ways of getting the functionality, I was referring to multiple ways within RME to do what I already told you. You would still need a basic config on the device (i.e. IP, SNMP).
Okay so I'll go with the Copy/paste option from within Config Editor for now.As for zero-touch deployment, if it counts for anything, this feature has my vote!Thanks Jclarke!Alex.