You can check this in the Credentials screen. If you don't, you can get Unimus from our downloads page, and we have guides on our Wiki here and here that will help you deploy Unimus.įirst we need to make sure we have proper credentials in Unimus which we will be using to connect to our routers. Configuring Unimus to talk to the devices we want to upgradeįor this article, we assume that you have an empty, but fully deployed Unimus instance ready. I created a ros-packages directory, and put them there.Īnd that's actually everything you need to do on our Package Source "server". For this demo, I just downloaded the latest packages for ARM and x86.Īfter you get the packages, you can upload them to your package source router using SCP. You can get packages from the MikroTik download page. To make this CHR a package source for all our other MikroTiks, we first need to get the packages we are interested in. The Package Source will be a MikroTik CHR for this demo. then we have 5 MikroTiks we want to update RouterOS on.we have a Package Source (which is just a normal RouterOS device - for this demo a CHR).The topology for the network we will be testing on is simple:
What's even better, doing the entire upgrade process (including setup of Unimus and RouterOS Package Source) can be done in under an hour.
This article will focus on MikroTik - we will show you how you can do a network wide mass upgrade of RouterOS using Unimus, and the RouterOS Package Source feature. Cisco also recently had a bad ASA vulnerability ( info here), and just last year Ubiquiti had a massive exploit which brought down many networks around the world ( more details). Recently, MikroTik has had a series of severe vulnerabilities. However, it is absolutely necessary to keep the firmware/software of your networking equipment up to date. Let's face it - doing a network-wide roll-out of a new version of software for your switches or routers is painful and takes a LOT of time.
0 kommentar(er)
