The following will occur during a failover event:
Step 1:
Who | Task | Notes |
---|---|---|
Palo Alto and FortiGate users | Have a copy of your firewall configuration ready | This will make the recovery faster |
Have the authcode (Palo Alto) or license file (FortiGate) of your firewall ready | This will make the recovery faster |
Step 2:
Scenario 1: Node-to-node failover within the same region
Who | Task | Notes |
---|---|---|
Cybera’s VFS team | a. Confirm the issue; b. Contact the users impacted; c. Initiate failover | |
Palo Alto and FortiGate users | a. Make sure there is no instance under the VFS project; b. Re-launch firewall instance from the Rapid Access Cloud dashboard | The firewall will be relaunched using the latest baseline version of the firewall image uploaded on the Rapid Access Cloud |
Scenario 2: Failover between regions
Who | Task | Notes |
---|---|---|
Cybera’s VFS team | a. Confirm the issue; b. Contact the users impacted; c. Initiate failover d. Create the user’s network on the backup region; e. Grant the appropriate flavor access; f. Make sure there is no instance on the primary region | |
Palo Alto and FortiGate users | a. Re-launch firewall instance from Horizon dashboard | The firewall will be relaunched using the latest baseline version of the firewall image uploaded on the Rapid Access Cloud |
Step 3:
Who | Task | Notes |
---|---|---|
Cybera’s VFS team | a. Guide the user to upload their firewall authcode/license file |
|
b. Guide the user to upload the most recent firewall configuration file |
| |
c. Ensure the new firewall is operational | ||
d. Hand over the firewall | ||
Palo Alto and FortiGate users | a. Monitor new firewall b. Confirm all services are operational |
At a later time, the Cybera VFS team will contact you to schedule moving the firewall back to the primary region.
Note |
---|
Palo Alto users might have to perform an additional "hard reboot" for their firewall to become functional. If your firewall has been active for at least 15 minutes and are not seeing activity or traffic, please perform a hard reboot. |