why data didn't synchronize from active node to standby and local node?

Verifying the Connection Between the Active and Standby Nodes

[Expected result]

When the primary node is faulty and the standby node is running properly, the system switches services to the standby node and the standby node is in active state.

Run the show connectstates stationtype primaryserver and show workstatus commands on the standby eSpace U1980. The following information is displayed:

show connectstates stationtype primaryserver

 ------------ ------------------ ------------ ----------------- ------------- ------------ 
   RemoteIP     RemoteDataPort     LocalIP      LocalDataPort       State     SynDataState 
 ============ ================== ============ ================= ============= ============ 
 192.168.10.4 4799               192.168.10.3 4799              Disconnected  Routine 
 ------------------------------------------------------------------------------------------ 

 ====  Command executed success !  ==== 

show workstatus

 ==========  
   status    
 ==========  
 ACTIVATE  
 ------------------------------------------------------------------------------------------ 

 ====  Command executed success !  ====     

The value of State is Disconnected, and the value of status is ACTIVATE.

[Troubleshooting]

• If the values State and status are Disconnected and DEACTIVATE respectively after you run the show connectstates stationtype and show workstatus commands on the primary and standby nodes, see 3.3.1 Configuring the Active Node to verify the network configurations. Ensure that the primary node and standby nodes are connected properly.
• When the primary node is faulty and the standby node is running properly, recover the active node.

Verify intra-office calls

[Expected result]

Calls can be made properly between two intra-office users, such as 5000 and 5010, 7000 and 7001, 5000 and 7000, and 5000 and 8000.

[Troubleshooting]

• If the announcement "The number you dialed does not exist" is played, rectify the fault by referring to section"A Caller Hears the Voice Prompt That "The number you dialed does not exist" When Calling an Intra-Office User" in "Troubleshooting Guide" in the eSpace U1980 Unified Gateway Product Documentation.
• If the call is set up, but neither party can hear the other party, rectify the fault by referring to section"Calling Party and Called Party Cannot Hear Each Other" in"Troubleshooting Guide" in the eSpace U1980 Unified Gateway Product Documentation.
• If the called party's phone does not ring or another phone rings, rectify the fault by referring to section"ONLY Number cannot be bound" in "Troubleshooting Guide" in the eSpace U1980 Unified Gateway Product Documentation.

Verifying Calls Between Users at the Active Node and Local Node and External Users

[Expected result]

1. User 5000 can call an outer-office user successfully, and the calling number 83785000 is displayed on the called party's phone.
2. User 7100 can call an outer-office user successfully, and the calling number 68907888 is displayed on the called party's phone.
3. User 8100 can call an outer-office user successfully, and the calling number 80808888 is displayed on the called party's phone.
4. When an outer-office user dials 83785000, the user 5000's phone starts ringing.
5. When an outer-office user dials 68907888, the user hears the VU voice prompts and is asked to dial the extension number 7100. User 7100's phone starts ringing.
6. When an outer-office user dials 80808888, the user hears the VU voice prompts and is asked to dial the extension number 8100. User 8100's phone starts ringing.

[Troubleshooting]

• If the announcement "The number you dialed does not exist" is played when a user at the active node calls to an external user, rectify the fault by referring to section "Number Is Displayed Abnormally" in "Troubleshooting Guide" in the eSpace U1980 Unified Gateway Product Documentation.
• If the calling number is not correctly displayed when a user at the active node calls an external user, rectify the fault by referring to section "Number Is Displayed Abnormally" in"Troubleshooting Guide" in the eSpace U1980 Unified Gateway Product Documentation.
• If the user does not hear the voice prompt when the user dials the switchboard number, rectify the fault by referring to section "Voice Prompt Faults" in "Troubleshooting Guide" in the eSpace U1980 Unified Gateway Product Documentation.

Verifying the Switchover Function Between the Active and Standby Nodes

1. Log in to the local maintenance terminal (LMT) and connect to the standby node.
2. Export the data stored in the standby node.
3. Connect to the primary node through LMT.
4. Import the data exported from the standby node to the primary node.
5. Connect to the standby node through LMT and switch the services back to the primary node.
    NOTICE:

   During the switchover between the primary and standby node, the services are interrupted. To minimize service interruption impact, perform the switchover during off-peak hours.

   Perform a manual switchover in either of the following ways:

   • Run the execute manualswitch command to perform manual switchover.
   • Run the start autoswitch time <hh:mm:ss> command to perform scheduled switchover

6. Verify the switchover.
   1. Connect to the standby node, and check the alarm information in Deviationism Disconnect. Make sure the alarm status displayed in Resumption Flag is Yes.
   2. Access the command tree configuration page of the primary node. Run the show workstations command and make sure the working status of the primary node is ACTIVATE.
   3. Access the command tree configuration page of the standby node. Run the show workstations command and make sure the working status of the standby node is DEACTIVATE.