Connectivity: To configure interface redundancy it is best practice to set up an interface bond and use one single IP address.
- Agree, I would love to do it but I can't at the moment. We are connecting the Manager to two switch/routers in HA. Unfortunately they don't run VPC, so we need two different IP networks to support this configuration in HA.
Security: Your security management should be a management host running at one specific host IP address that is directly segmented and protected by your security gateways. Configuring a secondary interface means you maintain a management gateway and not a management host which is not recommended.
- Totally agree. But yeah, both NICs are in the same security zone, so it is a host with two NICS, with two default routes. So no security concerns.
License: You already figured it out by now, right?
- Good question, but I have tested it and I don't see any problem when the licensed IP is down (I am testing with temporary licenses though). I think the GAIA is happy as long as the IP is configured even if the NIC is down.
Web Extensions: These and many other management functions rely on your managements' main IP address, so don't change it and put it on an interface bond instead.
- For all these reason it would be nice if the Security Manager Extensions could support a manager with two IPs. I think that the Smartconsole and the standard SMS actually supports two ips but not the Security Manager Extensions.
