Publication Date: 2019-07-17 | Views: 299 | Downloads: 0 | Author: SU1001785932 | Document ID: EKB0000400957
This problem can be determined by using errlog and dbms-query:"alminv.dbf",drdb commands.
1. If the error log contains the following records, you can determine that the problem is caused by the setting of alarm inversion function:
fatal task errorcode=1, Line 2069 in alm_char.cpp:TA
2. Run the :dbms-query:"alminv.dbf",drdb command. In the following results, "4d" and "57" indicate that scenario 1 exists and
"ff" indicates that scenario 2 exists.
record num BID OPPORT PATH ALLOW
1 ff 01 0001 01
2 05 02 0001 01
3 05 03 0001 01
4 05 04 0001 01
5 05 05 0001 01
6 4d 06 0001 01
7 57 07 0001 01
Solution 1: If the alarm inversion function is enabled on the existing network, disable the function, replace the main control board with a new one (If there are two main control boards on the existing network, you need to remove both of them), and upload configuration data through the T2000.
Solution 2: If the BID of the extended subrack is found in the alarm inversion database when the OSN 3500 runs normally, you need to delete the alarm inversion database to avoid repeated resetting of the OSN3500 after the main control board is reset, and perform the following operations to recover the state.
:dbms-set-autobackup:disable; // When the query result of (1) is enable, set disable.
:dbms-set-cyclebackup:disable；// When the query result of (2) is enable, set disable.
:dbms-set-autobackup:enable; // When the query result of (1) is enable, recover the original state.
:dbms-set-cyclebackup:enable; // When the query result of (2) is enable, recover the original state.
Solution 3: Upgrade the version to the following version that solves the problem:
V version T version
OSPV100R007C03 T15 and later versions
OSPV100R008 B01D and later versions
OSPV100R009 B01D and later versions