Fail over issues

[Wallace192]

Hi,

Is there a way to assign a secondary IP address to a host in cacti?

I have 70 remote sites. At each site there is a Cisco ASA with 3 interfaces (Inside, MPLS, VPN). The primary connection back to the main office is via the MPLS interface. If the MPLS link goes down the the site fails over to the VPN connection. Each interface has it's own IP address.

We use the MPLS IP in Cacti right now, but if a site fails over we can not connect to that site via the primary IP. I do not really want to have 2 hosts (one of which will always be down) Cacti for each ASA. I would like to be able to assign the secondary so that Cactil would try the primary and if down then try the secondary. If both are down THEN consider the host as down.

Wally

[BSOD2600]

Try adding another IP after a semi-colon. IF that doesn't work, then I think the other temporarly solution would to specify a name in cacti, then use the OS HOSTS file to specify the other IPs for it.

If that semicolon thing doesn't work, then it'd be a good feature request, IMO. http://www.cacti.net/bugs.php

[TheWitness]

We need to know if you are using spine or cmd.php. In either case, there needs to be changes to the following code to support a semi-colon delimited list of hosts:

Cacti Changes:
lib/ping.php (ping functions for UI and cmd.php)
include/global_form.php (better information on the host form indicating that dotted notation is acceptable)
cmd.php (handle the new notation, explosion of new notation and failover)

Spine Changes:
ping.c (new notation detection, explosion, and pinging)

To be honest, this would be a good excuse to rearchitect cmd.php to properly align with spine. This is going to be much easier to do in spine due to the way I work with structures.

In either case, you need to submit an RFC at the bugs site.

TheWitness

[Wallace192]

Sorry about the delay.

To answer your question I am using cmd.php. I have also opened a case in the bug system.

http://bugs.cacti.net/view.php?id=1569

If you need anything else let me know.

[TheWitness]

Ok

[TheWitness]

The developers discussed this yesterday, and it's a low priority issue. As BSOD2600 suggested, you can maintain a /etc/hosts file with all the various IP addresses there. Then, you simply place the primary router in the hosts file first and the backup route as the second entry.

Then, Cacti will fail over to the alternate route using the Operating systems ability to traverse the hosts file to find the working route. We could do a hack to Cacti, but it looks like the OS is the way to go.

TheWitness