801 Data Out of Synchronization

Description

A data consistency check is performed between the core process of the GBAM/GOMU and the local process of the GBAM/GOMU or between the core process of the GBAM/GOMU and the service boards. If the data is inconsistent, the alarm is generated.

Attribute

Alarm ID	Alarm Severity	Alarm Type
801	Critical	Fault

Parameters

ID	Name	Meaning
1	Subrack No.	Number of the subrack where the board with inconsistent data is located.
2	Slot No.	Number of the slot where the board with inconsistent data is located.
3	Subslot No.	Number of the subslot where the board with inconsistent data is located.
4	CPU No.	Number of the CPU where the board with inconsistent data is located.
5	Alarm Attribute	0=Normal, Alarms period are longer than the Transient Threshold. 1=Transient Count, The times and the period of the alarms whose periods are shorter than the Transient Threshold are summed up. If the sum result is longer than the Alarm Occurrence Period Threshold or Alarm Occurrence Times Threshold, an alarm so called Transient Count Alarm is triggered. Because Transient Count Alarm is based on accumulative result, the recovery of the alarm may occur at least one Summing Cycle later. The Summing Cycle can be query by MML "LST STATSLDWIN".

Impact on the System

When the data between the GBAM core process or GBAM local process and a service board is inconsistent, the configuration data fails to take effect on the GBAM local process or the service board if you perform dynamic data configuration. If you do not perform dynamic configuration, some operations may not be executed and some services cannot be processed normally.

System Actions

None

Possible Causes

The user performs data configuration when the communication between the boards is abnormal. The BSC detects that the data between the core process of the GBAM/GOMU and the local process of the GBAM/GOMU or that between the core process of the GBAM/GOMU and a service board is inconsistent after the communication between the boards becomes normal.
The data used for loading and restoring is inconsistent with that run on the service board. After data is loaded and restored, the BSC detects the data inconsistency between the core process of the GBAM/GOMU and the local process of the GBAM/GOMU or between the core process of the GBAM/GOMU and the service board.
The local process and core process of the GBAM/GOMU run abnormally.

Procedure

Log in to the LMT and then choose Alarm Maintenance > Browse Alarm. Check relevant alarms.
1. Check whether the following alarms related to communication are reported, according to the Subrack No. and the Slot No. in the Location Info.
  NOTE:
  The Subrack No. and Slot No. of relevant alarms are the same as those of this alarm.
  
  20113 Faulty GE Link on the Sub-board of GXPUx
  20114 Inter-Board HIG Link Faulty
  20115 Intra-Board HIG Link Faulty
  20116 Inter-Board HIG Trunk Communication Failure
  20117 Board Fault-GE Switch Unit Failure
  20118 Inter-Board HIG Communication Failure
  20128 Faulty GE Link on the Backplane of GSCU board
  20129 Faulty GE Link on the Backplane of transaction board
  20125 GESW Back Trunk Group Link Failure
  20126 GE Trunk Group Link Fault of transaction board
  Y=> Any of the previous alarms is reported. This indicates that the communication between the boards is abnormal. Go to b.
  Y=> None of the previous alarms is reported. This indicates that the communication between the boards is normal. Go to 2.
2. Rectify the fault according to the alarm help. After the alarm is cleared, Go to 2.
Run SYN CFG, and then check wether the data is successfully synchronized.
Y => The alarm is cleared. The alarm handling is complete.
N => Go to 3.
Reset the board that fails the synchronization, and then check whether the alarm is cleared.
Y => The alarm handling is complete.
N => Go to 4.
Run LOD CFGFILE to load data. Then, check whether the alarm is cleared.
Y => The alarm handling is complete.
N => Run LOD CFGFILE again, and Go to 5.
NOTE:
If the loading of the board data times out, run LOD CFGFILE again.
Check whether the alarm is cleared.
Y => The alarm handling is complete.
N => Go to 6.
Check the local process and core process of the server.
1. Check whether the local process and core process of the server run normally.
  Y => Contact Huawei Customer Service Center.
  N => Go to b.
2. Reset the local process and core process of the server. Then, check whether the alarm is cleared.
  Y => The alarm is cleared. The alarm handling is complete.
  N => The alarm is not cleared. Contact Huawei Customer Service Center.