HA Mode Nebula (Workaround?)
ItMerc
Posts: 8
As much as we want to have a cloud managed firewall, we also want to have an HA mode configured to improve redundancy.
Unfortunately this is currently not supported in Nebula, because a cloud managed firewall is essential I have thought about a "Workaround".
It works as follows:
In Nebula create an organization with 2 sites, 1 site called Office *address* Master
and 1 site called Office *address* Slave.
So:
Site 1: Office *address* Master
Site 2: Office *address* Slave
(Both sites are paired to the same organization).
Import the master firewall to site 1, in this case we will call it: FW-M (M=Master).
Import the slave firewall to site 2, in this case we will call it: FM-S (S=Slave).
Configure Site 1 (Master site) as you will.
In Nebula there is an option to synchronize the configuration between sites, this will be useful to minimize the changes in case of a failover scenario.
Okay, let's say there is an incident and the master firewall must be replaced with the slave. It would work as follows:
•In Nebula, remove the master firewall from site 1 (through the inventory)
•After deleting the master firewall, you can move the slave firewall from site 2 to site 1 (master site)
•When selecting the "move to another site" function, you will be prompted to select the mode which the firewall will be configured on the other site. Because the firewall is already managed through Nebula, you can select "Nebula Native Mode" and the slave firewall will automatically be active in site 1. (After physically replacing the master firewall).
The only downside to this "Workaround" is that the firewall needs to be physically replaced.
Unfortunately this is currently not supported in Nebula, because a cloud managed firewall is essential I have thought about a "Workaround".
It works as follows:
In Nebula create an organization with 2 sites, 1 site called Office *address* Master
and 1 site called Office *address* Slave.
So:
Site 1: Office *address* Master
Site 2: Office *address* Slave
(Both sites are paired to the same organization).
Import the master firewall to site 1, in this case we will call it: FW-M (M=Master).
Import the slave firewall to site 2, in this case we will call it: FM-S (S=Slave).
Configure Site 1 (Master site) as you will.
In Nebula there is an option to synchronize the configuration between sites, this will be useful to minimize the changes in case of a failover scenario.
Okay, let's say there is an incident and the master firewall must be replaced with the slave. It would work as follows:
•In Nebula, remove the master firewall from site 1 (through the inventory)
•After deleting the master firewall, you can move the slave firewall from site 2 to site 1 (master site)
•When selecting the "move to another site" function, you will be prompted to select the mode which the firewall will be configured on the other site. Because the firewall is already managed through Nebula, you can select "Nebula Native Mode" and the slave firewall will automatically be active in site 1. (After physically replacing the master firewall).
The only downside to this "Workaround" is that the firewall needs to be physically replaced.
I know this is not the most sophisticated approach or the most practical for an HA configuration, but I think for a workaround this enabled to still manage firewall through Nebula with the option to "Failover".
Let me know what you think and share your idea's.
1
Categories
- All Categories
- 415 Beta Program
- 2.4K Nebula
- 147 Nebula Ideas
- 96 Nebula Status and Incidents
- 5.7K Security
- 262 USG FLEX H Series
- 271 Security Ideas
- 1.4K Switch
- 74 Switch Ideas
- 1.1K Wireless
- 40 Wireless Ideas
- 6.4K Consumer Product
- 249 Service & License
- 387 News and Release
- 84 Security Advisories
- 29 Education Center
- 10 [Campaign] Zyxel Network Detective
- 3.5K FAQ
- 34 Documents
- 34 Nebula Monthly Express
- 85 About Community
- 73 Security Highlight