![]() Due to that reason, Automatic failover is not possible if illustrated active cable (or interface) got faulty / malfunction. In FortiGate, High Availability cannot monitor virtual switches. Limitations in Virtual Switch configuration. Reason for state change: Incorrect configuration - Local cluster member has fewer cluster interfaces configured compared to other cluster member(s)ĭue to that LACP was not an option. ![]() Due to that failover will never happen! FortiGate keeps its passive appliance’s interfaces inactive whereas Checkpoint keeping its interfaces up and manage the communications via Virtual IP addresses. The reason is checkpoint will identify as the FortiGate secondary firewall’s interfaces down. However Checkpoint HA status will be Active-Down. What if we use LACP (Aggregates) than this Virtual switches.įortiGate HA will not show any issue because it works as Active-Passive. Tested Operating systems: FortiGate FortiOS 6.2.3 | Checkpoint R80.30 | Hardware appliances with physical connectivity. ![]() But it works.įortiGate HA status : Active-Passive : Hardware failover & monitored interface failover works without issue.Ĭheckpoint HA status : Active-Stand By : Hardware failover & monitored interface failover works without issue. | Operation Mode: Active-Backup | Three IP addresses : Each cluster & VIPįortiGate: Virtual Switch with 2 physical interfaces. Checkpoint Bond: with 2 physical interfaces.
0 Comments
Leave a Reply. |