Or run a decent setup to keep backups, like this one: https://github.com/ytti/oxidized. Source: over 1 year ago
You didn't mention about brand of the switches, but majority of vendors is covered with Oxidized: https://github.com/ytti/oxidized Just configure it with git backend, and you have version control and device backups. Also, if you wish, there are bundled sone extra scripts that could report git changes via email. Source: over 1 year ago
RANCID was great before Oxidized ;) Https://github.com/ytti/oxidized From description of Oxi: Oxidized is a network device configuration backup tool. It's a RANCID replacement! Source: over 1 year ago
If you're just looking to backup/inventory configs, give Oxidized a try https://github.com/ytti/oxidized. Source: over 1 year ago
What about the tried and trusted oxidized? Source: almost 2 years ago
I can recommend Oxidized for storing configs in CVS - https://github.com/ytti/oxidized. Source: about 2 years ago
Also, I replace my rancid/viewvc setup with oxidized, I like it better: https://github.com/ytti/oxidized. Source: about 2 years ago
Docker: My very first Docker container was Oxidized. Though any will do. After I got it working, I analysed the Dockerfile and used the Docker docs to get a full understanding of how it worked. Source: over 2 years ago
I would look at Oxidized. https://github.com/ytti/oxidized. Source: over 2 years ago
I recommend oxidized for device backups. Source: over 2 years ago
If you want to use this as an opportunity to learn Ansible, or you don't want to add another tool to the stack, this is a fine use case. Otherwise, I would consider using either RANCID or Oxidized for configuration backup. Source: over 2 years ago
We use https://github.com/ytti/oxidized to automatically pull configs from a few hundred different switches and routers. Source: over 2 years ago
Have you tried using https://github.com/ytti/oxidized? Works great for us so far. Source: over 2 years ago
One reason this seems like a reasonable approach is that on the main GitHub page for Oxidized, they mention running git blame. So it seems like part of their intent is for users to be able to use git commands. Source: over 2 years ago
Set up netdisco and have it discover everything. You'll have to seed it switch IPs and have snmp RO set up but it should be able to help map things out. Use oxidized to get the configs, this will need an account on the switches and knowledge of all the switch IPs. This would be my bare minimum. Make some diagrams too, manually doing this helps me understand how things are laid out and connected. Source: over 3 years ago
We use oxidized for config backups. Works fine with fortinet. https://github.com/ytti/oxidized. Source: over 3 years ago
If you have all the host names you can just setup oxidized which will take config backups AND get the serials for you. https://github.com/ytti/oxidized. Source: over 3 years ago
You're better off using something like Oxidized for that. Source: over 3 years ago
Do you know an article comparing Oxidized to other products?
Suggest a link to a post with product alternatives.
This is an informative page about Oxidized. You can review and discuss the product here. The primary details have not been verified within the last quarter, and they might be outdated. If you think we are missing something, please use the means on this page to comment or suggest changes. All reviews and comments are highly encouranged and appreciated as they help everyone in the community to make an informed choice. Please always be kind and objective when evaluating a product and sharing your opinion.