Category Archives: Technology

CentOS7 Cacti Virtual Appliance Upgrade commands

Here is a list of steps for upgrading my Cacti virtual appliance in place retaining all data. This will only work on the Centos7_Cacti-v1.1.6 or greater. This assumes you are still using the original Cacti user, passwords, and paths.

If there are any questions, please use GitHub Issues, and I can assist and update as needed.


 [Update 12/4/2018]

It turns out there has been some development in Smokeping after almost 4 years of quiet! New v2.7.2 is available, so I created a new Smokeping update routine and added it to the script. This will check if you have Smokeping installed, and offer to upgrade if you wish. This can be run via the same routine as the Cacti upgrade from Github below.

[UPDATE 11-28-2018]

I have a first working version of an automated update routine for the cacti-template you can get here. You can get the instructions on how to run it here…

https://github.com/KnoAll/cacti-template

Cacti Network Grapher Virtual Appliance

cactiThis virtual appliance is based on CentOS 7 and is designed to be lightweight, and stable. It has only a minimum of tools installed to make Cacti work.

The OS is set to DHCP, and Cacti is installed.

The username at the console, and passwords set for everything should be ‘cacti’ this will include root and mysql. **With the exception of the Cacti web ui “admin” user, which has the password “Cactipw1!” (no quotes)

The web UI username and password are “admin” and “Cactipw1!” (no quotes)

Cacti is all configured up and includes some plugins, which are not installed by default. It also has some additional host templates for Palo Alto firewalls, Cisco ASA Firewalls, F5 BIG-IP load balancers, and a few other things I have found useful over the years.

There is not a ton of documentation, as I simply have not had time.  If you are already familiar with Cacti it should be a breeze.  If there are any questions, please use GitHub Issues, and I can assist and update as needed.




[Update 10/30/2020]

  • Upgraded to new Cacti and Spine v1.2.14 released 8/02/2020
  • Updated all plugins
  • Upgraded PHP to v7.3
  • Upgraded MariaDB to v10.5
  • Various other fixes and tweaks

CentOS7 Appliance with v1.2.14 Cacti, OVA is ~2.6g

[Update 12/10/2019]

  • Upgraded to new Cacti and Spine v1.2.8 released 12/08/2019
  • Updated all plugins
  • Various other fixes and tweaks

LEGACY – CentOS7 Appliance with v1.2.8 Cacti, OVA is ~2.4g

[Update 7/17/2019]

  • Upgraded to new Cacti and Spine v1.2.5 released 7/15/2019
  • Updated all plugins
  • Various other fixes and tweaks
  • Now can upgrade the virtual disk in VMWare

LEGACY – CentOS7 Appliance with v1.2.5 Cacti, OVA is ~2.3g

[Update 1/23/2019]

  • Upgraded to new Cacti and Spine v1.2.1 released 1/20/2019
  • Updated all plugins
  • Various other fixes and tweaks
  • ./cacti-upgrade.sh now installed by default at root of cacti user directory

LEGACY – CentOS7 Appliance with v1.2.1 Cacti, OVA is ~2.3g

[Update 1/4/2019]

New Cacti v1.2.0 is released! TONS of new features and fixes. You can run my update script to automatically update the template. https://github.com/KnoAll/cacti-template this will also offer to update the Smokeping to newly released v2.7.3 as well. There is also a new prompt to disable the Smokeping service if you do not use Smokeping.

 [Update 12/4/2018]

It turns out there has been some development in Smokeping after almost 4 years of quiet! New v2.7.2 is available, so I created a new Smokeping update routine and added it to the script. This will check if you have Smokeping installed, and offer to upgrade if you wish. This can be run via the same routine as the Cacti upgrade from Github below.

[Update 11/28/2018]

I have a first working version of an automated update routine for the cacti-template you can get here. You can get the instructions on how to run it here…

https://github.com/KnoAll/cacti-template

[Update 11/16/2018]

Hello anyone who is listening! the Cacti team is working on the new v1.2 of Cacti which is now in it’s 2nd beta release. I am working on updating the template along with this and there are a lot of changes! I’m also building an upgrade script that can be used to upgrade the appliance with little effort. (Sorry, for now it will only work on the new v1.2.x appliance) More to follow as things progress.

[Update 4/2/2018]

  • Upgraded to new Cacti and Spine v1.1.37 released 3/25/2018
  • Updated all plugins

LEGACY – CentOS7 Appliance with v1.1.37 Cacti, OVA is ~2.2g


Web Farm Framework IIS Bindings

Ok, so here is my approach to bindings in IIS using  Web Farm Framework 2.x. I have seen several ways of doing this, but all involved setting up replace rules for WFF and I didn’t want to mess with that.

What I do is, on my controller webserver, I add all of the bindings for each of the machines. In the drop down menu for IP address, you can manually type in the IP, and the server will let you add anything, regardless of it being assigned to the machine. Then IIS will accept the requests for which it has an assigned IP address, the rest will be there but not do anything. These settings will propagate to all of your servers in your WFF Server Farm, and you will be able to maintain your single point of administration for IIS.

Unintentional load test

I’ve been a little out of touch with this blog in the last month or so. Ever since Thanksgiving things have been crazy, especially at work with the busy season.

Over the last year we have made some great efforts to dramatically increase our stability as well as availability by increasing redundancy to remove single points of failure. This was on many levels including the networking layer by introducing an HA firewall pair, and an HA load balancer pair. We also built out our server infrastructure by implementing 3 web servers for the load balancing, as well as clustering our database hardware and our application server hardware. All of this was intended to be able to easily handle the load of the retail busy season, between Thanksgiving and New Year’s weekend. To be able to really know how much we could handle we wanted to load test the infrastructure top to bottom. Continue reading Unintentional load test

Polling an F5 Load balancer using MRTG and SNMP

[UPDATE 3-6-2015:] Check out my newly posted Cacti Virtual Appliance. It is much easier to use than MRTG, and has a pre-loaded host template for F5 BIG-IP Load Balancers!

After getting MRTG setup and running in my MRTG Virtual Appliance as I call it, I started setting up all my networking devices for monitoring.  One of the devices I really wanted to poll some more advanced data from is our Load Balancer.  What I really wanted to be able to see was the number of concurrent connections to the LB and each of the Virtual Servers if possible.  This proved to be much more complicated than I had anticipated.

My first problem is that my SNMP software in Ubuntu was not configured correctly.  By default the SNMPd was looking for /usr/share/snmp/mib to load the mib files.  In the version of Ubuntu that I had the path was /usr/share/snmp/mib2c-data so I had to update the snmp.conf file.  Once I did that then SNMP was able to correctly load all the add-on MIBs so that I could have the OID definitions load correctly.

My second problem was the the MIB file that I had gotten from the web was incorrect, or more to the point it was outdated.  The search that I did for F5 MIBs returned many hits, but the one that I went to for most of the information I started with was a nice post at vegan.net.  Unfortunately, I didnt realize that this was really out of date.  As a result the LOAD-BAL-SYSTEM-MIB.txt is invalid with the software version that my F5 is running and fails the OID lookups.

My F5 is hosted so I dont have direct access to the device.  I was able to get the hosting company to grab the MIB files from the filesystem of the F5, and then I put them into my /usr/share/snmp/mib2c-data directory.  After that my MRTG graphs for Virtual Server connections started working. One mistake that I made in this process was only putting some of the MIB files on my machine.  Do yourself a favor and just get ALL the MIBs and load them to your SNMP MIBs folder.

I found a nifty script here called Buils_mrtg_cfg_for_virtual_servers.pl.txt that was able to do an snmpwalk and get all the information about my Virtual Servers that I needed to get current connections and bandwidth on a per VS basis.  From there MRTG was up and running with some pretty good stats about concurrent connection rate and bandwidth utilization across all my domains.