Solution to locate the database syn problem (DBSYNC_FAIL)

Publication Date: 2012-07-24Views: 80Downloads: 0

Issue Description

After one OSN2500 upgraded, the system report DBSYNC_FAIL, from the alarm we can see the standby SCC can not synchronize the active one.and the database backup status keep 0000 and 0002 status. and we found the standby SCC keep rebooting.

Alarm Information

DBSYNC_FAIL

Handling Process

1. we checked the version information like:Extbios, nesoftware, .ini, FPGA, all is the same between active board and the standby one.2. changed the standby SCC board with another one. and we found the same problem. so we can cofirm that the standby one should be no defect, but the active works well with out any defect hint/3. we tried to switch between the active and the standby SCC(now only cold reset the active board can be cause the switch),check the software file compile date, first result:BIOS 08.09.45T01 20060106 14:21:44 inactiveExtBios 9.09.44T01 20051117 19:39:00 activeNeSoft(P) 5.36.13.47P01 20061213 16:03:42Platform(T) 5.00.07.C02T16D1 20061010 21:05:47Logic (U9)120(U21)110Dsp second result.BIOS 08.09.45T01 20060106 14:21:44 inactiveExtBios 9.09.44T01 20051117 19:39:00 activeNeSoft(P) 5.36.13.47P01 20061213 16:48:50Platform(T) 5.00.07.C02T16D1 20061010 21:05:47AosSoft(T) 5.99.01.10T18 20051117 19:11:03Logic (U9)120(U21)110Dsp 4. we found "NeSoft(P) 5.36.13.47P01 20061213 16:48:50 5.36.13.47P01 20061213 16:03:42"only the compile time is different. however, the board which the software compile at 16:03:42 is the wrong software, 5. redownload the software , the problem solved.6. this case mainly caused by the software misdownload(download the Q1CXL software to Q2CXL).