21020 Software Version Inconsistency

Description

This alarm is generated when the GBAM/GOMU detects version inconsistency during periodical checking of the software files saved in the flash of all the boards in position according to the version mapping information. The software files include host program files, patch files, license files, and level 2 BIOS files.

Attribute

Alarm ID	Alarm Severity	Alarm Type
21020	Minor	Fault

Parameters

ID	Name	Meaning
1	Subrack No.	Number of the subrack where the board on which the inconsistent versions are detected is located
2	Slot No.	Number of the slot where the board on which the inconsistent versions are detected is located
3	CPU No.	Number of the CPU on which the inconsistent versions are detected (GXPUx has four CPUs numbered from 0 to 3; other boards have only one CPU numbered 0)
4	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

If the version of the files saved in the flash of the boards in position is inconsistent with these saved on the GBAM/GOMU, the activation of files such as patch files and license files fails, or the boards cannot work normally after the activation of files such as version software files and level 2 BIOS files. As a result, the services may be affected.

System Actions

None.

Possible Causes

The board is not correctly upgraded.
The GBAM/GOMU is not correctly upgraded.
The files saved on the GBAM/GOMU are damaged.

Procedure

Check whether the board is successfully upgraded and whether the software saved in the flash of the board is consistent with that on the OMU.
1. Query the version of the faulty board on the LMT. Then, check whether the software version of the board is the latest one.
  Y=> Go to 2.
  
  N=> Run the MML command LOD SOFTWARE on the MML client to reload the host software and BIOS software. Then, load the patch file and incense file. Go to 4.
Check the parent alarm.
1. Log in to the LMT, choose Alarm Maintenance > Browse Alarm to check whether the following parent alarm is reported.
  21024 GBAM File Check Failure
2. Rectify the fault according to the alarm help. Then, check whether the alarm is cleared.
  Y=> The alarm handling is complete.
  
  N=> Go to 3.
Run the MML command LST SOFTWARE on the MML client to check whether the software version on the GBAM/GOMU is correct.
Y=> Go to 4.

N=> Run the MML command LOD SOFTWARE on the MML client to reload the host software. Go to 4.
Check whether the alarm is cleared.
Y=> The alarm handling is complete.

N=> Contact Huawei Customer Service Center.