ā01-31-2019 07:15 PM
In our environment we cannot use templates to configure the switches as each switch is unique in the port layout. Without templates there does not appear any way to move the configuration to the new hardware. Even if you pull the configuration from the switch itself and restore it to the new switch you cannot pull that back into HiveManager. Currently it is a 2-3 hour process for a 48 port switch to replace hardware.
ā02-01-2019 12:26 AM
Perhaps it's not optimal, but under extenuating circumstances, you could use supplemental cli to expedite in a pinch.
ā01-31-2019 10:54 PM
You can do that but there is no way to bring that back into HiveManager. You still have to recreate the entire config in the GUI and push it to the switch. I actually have Solarwinds NCM pulling the configs and in a pinch it would get me going but it does not solve the HiveManager issue.
ā01-31-2019 10:50 PM
Why not keep a copy of the config via cli? For newer switches, run the following commands to copy to a tftp server, then copy and paste into the new switch...
copy nvram:startup-config tftp://x.x.x.x/config
ā01-31-2019 07:59 PM
Unfortunately you cannot program all the features and setting in the template. If you did a template per switch then you have to create every possible combination of switch port type based on VLANs in combination with voice VLANs. Even if you did this the templates do not allow you to set any of the other port setting such as speed, duplex, storm control, lldp, client monitoring, stp and so on. Look at all the other tabs on a switch port, none of those can be set in a template, only on the switch itself.
ā01-31-2019 07:48 PM
Unfortunately without templates there is no way to copy a config from one switch to the next. Even if each switch has it's own template, if you made one for each switch when you replaced the physical switch you could apply the appropriate template to it so you didn't have to rebuild?