随着网络设备的增多，通过人手备份网络设备倍感压力，而且效率低。有编程基础的人可能会通过Python的parimiko 或者netmiko 连接到设备操作 把文件通过ftp 上传到FTP服务器, 在通过定时任务,定期自动备份。这个应该是现阶段主流非人民币网络玩家的最优解决方案。
今天我们来看看oxidized这个被称之为”最好用的”网络备份系统，友好的支持不同厂商。
oxidized简介
oxidized 是一个网络设备备份系统, 轻量级,可扩展,支持超过90多个操作系统。个人觉得它无与伦比的优势, 同时支持h3c,华为,思科。
随着容器化的兴起，部署软件变得的越来越简单，有的已经帮您封装好，你开箱即用就可以了。好了下面，我们看看这个oxidized系统有没有镜像的。
[root@node1 ~]# docker search oxidized
NAME DESCRIPTION STARS OFFICIAL AUTOMATED
oxidized/oxidized Oxidized is a network device configuration b... 27 [OK]
alectolytic/oxidized Oxidized: Alpine Linux based Docker image 1 [OK]
klinnex/oxidized Oxidized 0 [OK]
bootc/oxidized Oxidized, the configuration backup software ... 0
edeln/oxidized oxidized as a framework, using its ssh and s... 0
mkbarry/oxidized-worker 0
mkbarry/oxidized-tooling 0
b3vis/oxidized Oxidized config backup software in an Alpine... 0 [OK]
neteng1/oxidized Backup Network Devices 0
rbrayner/oxidized older oxidized 0 [OK]
macaty/oxidized oxidized 0 [OK]
ossobv/oxidized Edited oxidized (ios.rb) so you can use read... 0
dbrockus/oxidized This is a TEST, DO NO USE 0
voravitl/oxidized 0
zxandy/oxidized Oxidized - Configuration backup software htt... 0
deesel/oxidized 0
zeyanlin/oxidized configuration backup software (IOS, JunOS) -... 0 [OK]
samkdocker/oxidized 0
talibaiiika/oxidized 0
splendid/oxidized mtk 0
sfoster/oxidized Docker Oxidized auto build 0 [OK]
xrlx/graphite-rust Oxidized graphite stack 0 [OK]
View Code
把官方的 oxidized/oxidized 镜像拉下来
bash;gutter:false;
[root@node1 ~]# docker pull oxidized/oxidized:latest</p>
<pre><code>
下载完启动镜像
;gutter:true;
[root@node1 data]# docker run –name=’oxidized’ -itd -v /data/oxidized:/root/.config/oxidized -p 8888:8888/tcp -t oxidized/oxidized4bbb01b608e38c59469b1056e24c65f1f36f6e65b0734ab1e86b64b4efcf3306
说明一下：挂载本地/data/oxidized目录到容器内的/root/.config/oxidized目录下，将本地8888端口映射到容器的tcp8888端口。
查看是否已经启动完
[root@node1 data]# docker logs oxidized
*** Running /etc/my_init.d/00_regen_ssh_host_keys.sh...
*** Running /etc/my_init.d/10_syslog-ng.init...
Jul 11 15:03:44 4bbb01b608e3 syslog-ng[13]: syslog-ng starting up; version='3.13.2'
*** Booting runit daemon...
*** Runit started as PID 21
Jul 11 15:03:45 4bbb01b608e3 cron[29]: (CRON) INFO (pidfile fd = 3)
Jul 11 15:03:45 4bbb01b608e3 cron[29]: (CRON) INFO (Running @reboot jobs)
edit ~/.config/oxidized/config
I, [2019-07-11T15:03:47.866728 #34] INFO -- : Oxidized starting, running as pid 34
F, [2019-07-11T15:03:47.869750 #34] FATAL -- : Oxidized crashed, crashfile written in /root/.config/oxidized/crash
no source csv config, edit ~/.config/oxidized/config
I, [2019-07-11T15:03:49.179948 #36] INFO -- : Oxidized starting, running as pid 36
I, [2019-07-11T15:03:49.180885 #36] INFO -- : lib/oxidized/nodes.rb: Loading nodes
F, [2019-07-11T15:03:49.181047 #36] FATAL -- : Oxidized crashed, crashfile written in /root/.config/oxidized/crash
No such file or directory @ rb_sysopen - /root/.config/oxidized/router.db
从以上日志看到缺失router.db这个文件，导致启动失败。解决方法在/data/oxidized目录下新建router.db文件，并在router.db随意添加一条记录。后重新启动容器
bash;gutter:true;
[root@node1 oxidized]# touch router.db[root@node1 oxidized]# cat router.db 192.168.1.1:vrp:admin:admin
[root@node1 oxidized]# docker restart oxidized
oxidized
[root@node1 oxidized]#</p>
<pre><code>
再次查看日志
;gutter:true;
[root@node1 data]# docker logs oxidized……省略Puma starting in single mode…
* Version 3.11.4 (ruby 2.5.1-p57), codename: Love Song
* Min threads: 0, max threads: 16
* Environment: development
* Listening on tcp://127.0.0.1:8888
Use Ctrl-C to stop
[root@node1 oxidized]#
修改配置文件
router.db是记录设备备份配置的本地信息文件
`bash;gutter:true;
x.x.x.x:device type:username:password
10.10.24.241:ios:admin:password
10.10.28.235:comware:admin:password
10.10.0.107:vrp:admin:password
注解：device对应的是容器目录/var/lib/gems/2.5.0/gems/oxidized-0.26.3/lib/oxidized/model/的文件名
### config文件
Original: https://www.cnblogs.com/alanlin/p/11173214.html
Author: 北根娃
Title: 利用docker部署oxidized网络设备备份系统
原创文章受到原创版权保护。转载请注明出处：https://www.johngo689.com/644229/
转载文章受原作者版权保护。转载请注明原作者出处！