Advice given as posted on this forum does not construe a support relationship or other relationship with Convergent Information Security Solutions, LLC or its subsidiaries. Use the advice given at your own risk.
Advice given as posted on this forum does not construe a support relationship or other relationship with Convergent Information Security Solutions, LLC or its subsidiaries. Use the advice given at your own risk.
I logged in and checked a few things this morning.
Thing 1.) As suggested, I looked at the interfaces menu & options and found that the units were using an interface as a dedicated heartbeat channel (the interface used was eth3). The eth3 interfaces were not available to be changed because they were not visible anywhere within the "general" sub-tab. presumably because they had been claimed for use by the High Availablity system already. They could only be identified through looking into the "Hardware" sub-tab within the interfaces menu. As they were not available, they could not be set to "Internal", as suggested in a previous post.
Thing 2.) I found that the systems seem to be attempting to create a back-up heartbeat via a network cable between the two eth3 ports.
Thing 3.) The secondary heartbeat had not been set up, so I configured it to use the internal (LAN) interfaces.
Thing 4.) The 2nd firewall (passive) system had not been rebooted for some time so I rebooted.
The result of the above changes did produce a slightly different message than before. Now the second firewall no longer shows as "unlinked", but rather is now permanently indicating that it is "syncing". Please see attached images.
We are getting closer, but we're not quite there yet I fear.
