Solutions to some of the issues you might encounter when setting up a new Rancher cluster on Ubuntu.
Author: Patrik Jonsson
![](https://loadbalancing.se/wp-content/uploads/robot-2937861_1280.jpg)
If you’re using the F5 GeoIP database in your environment it’s important to keep it up to date. Public IP networks moves around quite often
![](https://loadbalancing.se/wp-content/uploads/vacuum-cleaner-268179_1280.jpg)
It’s very common to start at a place and realizing that the F5 environment contains loads pools with members down. Often, the reason for this
![Docker](https://loadbalancing.se/wp-content/uploads/ship-3493887_960_720.jpg)
If you are unfamiliar with Docker this might seem like a daunting task but trust me, it’s the easiest way to get up and running.
![](https://loadbalancing.se/wp-content/uploads/cows-4383468_1920.jpg)
The previous article covered getting rancher up and running using their container service. This is great to test it out but for a production purpose
![](https://loadbalancing.se/wp-content/uploads/container-4203677_1920.jpg)
For fun I decided to try out Rancher in my VMware lab environment and I did not find any quick and dirty guides so I’ll
![](https://loadbalancing.se/wp-content/uploads/coffee-2306471_1920.jpg)
Cautionary note to the reader. While this works great to see configuration revisions it is not a full backup of the F5 configuration. Aside from
![](https://loadbalancing.se/wp-content/uploads/marta-filipczyk-QQmINQz8E-c-unsplash.jpg)
This guide assumes that you have a functioning Oxidized installation. If you don’t you can head over to Part 1 and go back here when
![](https://loadbalancing.se/wp-content/uploads/door-2358259_1280.jpg)
It’s time to do a refresh of the backup strategy and we since we already used LibreNMS we figured that Oxidized could be a good
![](https://loadbalancing.se/wp-content/uploads/stock-1863880_1920.jpg)
We realized the other day that one of our Firewalls was broken. Instead of our monitoring system (LibreNMS) alerting us we found out the “organic