Technical Note: Eth1 Interface Not Coming Up After L2 HA Failover or Resume

[FortiKoala]

Description

Eth1 Interface Not Coming Up After L2 HA Failover or Resume

Scope
Version:   CentOS 7 with Network Sentry 8.0.6 (and earlier), 8.1.0 (and earlier)
Solution

Version:  CentOS 7 with Network Sentry 8.0.6 (and earlier), 8.1.0 (and earlier)


Issue:  If the system that is "not in control" (either primary or secondary) is rebooted, interfaces other than eth0 are not configured. When that system is made "in control" only eth0 is active. That leaves the isolation network interface inoperable.

Affects L2 High Availability (HA) NetworkControlApplicationServer and NetworkApplicationServer systems.  L3 HA is not affected.


Workaround:  Call Support to apply a fix.  Reference Solution 2252.


Solution: To be addressed in the next release of Network Sentry 8.0 and 8.1.1.