Problem and solution when the original active firewall does not preempt the active role after recovery

2

Possible causes are as follows:
The preemption function is disabled.
The preemption hold-on timer has not expired. The original active firewall does not perform preemption immediately after recovery. Setting preemption hold-on prevents repeated switchover resulting from unstable active firewall status.

Other related questions:
Why does not the original active firewall preempt after recovery
Possible causes are as follows: -The preemption function is disabled. -The preemption conditions are not met. The original active firewall does not immediately preempt after recovery. Instead, it waits for a delay before the preemption. The preemption delay is set to avoid unstable active/standby switchover.

Why are services interrupted after the original active firewall preempts
Services are normal after the active/standby switchover, but services are interrupted after the active firewall preempts. The possible cause is that the network has not converged or sessions are not completely backed up. Besides, if a switch fails, its interfaces may go up and down repeatedly when the switch restarts. If the firewall preempts during the process, services may be interrupted. In this case, adjust the preemption delay of the original active firewall.

Problem and solution when the sessions of the current active firewall are tagged with remote after active/standby switchover
Sessions with the remote tag are synchronized from the originally active firewall. After active/standby switchover, the backup session entries are still tagged with remote until they are aged out.

Introduction to OceanStor ReplicationDirector in the data center disaster recovery solution (active-active mode)
The solution uses the VIS mirror function to mirror host services from the production center to the remote disaster recovery center. This achieves disaster recovery protection at zero RPO and RTO. This solution also supports the tri-mirror function, enhancing data reliability and can use VIS snapshots of protected objects to roll back data, preventing data loss and virus attacks. 1. The solution uses the VIS mirror function to mirror host services from production center 1 to production center 2. Both data centers work concurrently to share service loads, improving disaster recovery service capability and system resource utilization. The data centers are mutually backed up. If one data center fails, the other takes over its services, ensuring business continuity. 2. In this solution, deploy one piece of OceanStor ReplicationDirector to manage disaster recovery services in the active-active data centers. You are advised to deploy OceanStor ReplicationDirector at the active-active disaster recovery center. The OceanStor ReplicationDirector Agent automatically detects the applications on hosts and the storage systems used by the applications. The OceanStor ReplicationDirector Server automatically identifies the configurations of the active-active disaster recovery solution and formulates disaster recovery protection policies. 3. This solution supports the active-active (VIS) technology.

Application types supported by OceanStor ReplicationDirector in the disaster recovery data center solution (active-active mode)
The disaster recovery data center solution (active-active mode) supports the following applications:

If you have more questions, you can seek help from following ways:
To iKnow To Live Chat
Scroll to top