What Do I Do If FS`s connection between product and recovery is lost Is Displayed When the DR Status Is Checked After OperationCenter DR Is Configured

8

【Product�?
ManageOne OperationCenter

【Version�?
All versions

【Question�?
What do I do if "FS`s connection between product and recovery is lost" is displayed when the DR status is checked after OperationCenter DR is configured?

【Answer�?
Step 1 Log in to the active node at the DR site, and run the following command:
vi /home/appuser/.ssh/id_rsa.pub
Copy the contents in the id_rsa.pub file and put them in the text for later use.
Step 2 Log in to the active node at the production site, and run the following command:
vi /home/appuser/.ssh/authorized_keys
Add the copied id_rsa.pub to the authorized_keys file. If the authorized_keys file on the standby node at the production site does not contain the public key of the active and standby nodes at the DR site, add the copied public key to the standby node at the production site. Save and close the authorized_keys file.
Step 3 Run the following command on the active node at the DR site to check the DR status:
check_recovery_status.sh
If the following information is displayed, the DR is in the normal state:
HA status is ok.
DB is running in recovery mode normally.
FS is running in recovery mode normally.
All connection is normal, status is good.


----End

Other related questions:
What Do I Do If the Synchronization Status Is Displayed as Abnormal After the cascadeTool query Command Is Executed on the Active Node of ServiceCenter at the Production Site and the Active Node at the DR Site
【Product�? ManageOne ServiceCenter 【Version�? 3.X 【Question�? What do I do if the synchronization status is displayed as abnormal after the cascadeTool query command is executed on the active node of ServiceCenter at the production site and the active node at the DR site? 【Answer�? The active node at the DR site synchronizes data from the active node at the production site. If any of the following situations occurs, the database at the production site cannot be synchronized. The synchronization status is displayed as abnormal after you run the cascadetool query command. The active and standby nodes of ServiceCenter at the production site or the active node at the DR site are faulty. The network at the production or DR site is faulty. Network ports required for DR synchronization are not enabled based on the communication matrix. ----End

OceanStor 9000 disaster recovery (DR) method
OceanStor 9000 provides the InfoReplicator feature to recover data and services upon disasters.

What are DR, BDR, DR other and election rules
DR means designated router. BDR means backup designated router. DR Other indicates a device that is neither a DR or a BDR. The DR advertises link-state advertisements (LSAs) to all the devices in the network. The DR election rules are as follows: When going Up, an interface sends Hello messages and enters the waiting state. In the waiting state, a waiting timer is triggered. The waiting timer duration is the same as the dead timer duration. By default, the waiting timer duration is 40 seconds, which cannot be changed. Before the waiting timer is triggered, sent Hello messages carry no DR or BDR field. In the waiting state, if a received Hello message carries the DR and BDR fields, the DR and BDR are accepted directly without any election triggered, and neighbor state synchronization starts, directly exiting the waiting state. Assume that a DR and a BDR exist on the network. Any device newly connected to the network will accept the DR and BDR that exist on the network regardless of the router ID of the device. If the DR fails and goes down, the BDR takes over the role of the DR and the remaining devices whose priority is greater than 0 compete to become the new BDR. DR election rules are used to elect a DR only when devices with different router IDs or configured with different DR priorities are started at the same time. The election rules are that the device with the highest DR priority is elected as DR and the device with the second highest DR priority as BDR. A device with a DR priority of 0 can be a DR Other only. In the case of the same priority, the device with the greatest router ID is elected as DR, the device the second greatest router ID becomes the BDR, and other devices are DR Others.

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