408 Automatic Loading and Activation of BTS TMU Version

Description

This alarm is generated when the BSC detects that the version of the existing TMU software is inconsistent with that of the configured TMU software and the BTS activates the configured TMU software.

Attribute

Alarm ID Alarm Severity Alarm Type
408 Minor Event

Parameters

ID Name Meaning
1 Site No.

Number of the site where the TMU version is loaded and activated automatically.

2 Cause

1=Querying the current version number of the BTS failed,4=Activating the TMU version failed,5=Activating the TMU version succeeded,6=Get TMU software to download failed

3 NACK cause

14= Parameter value limit exceeded,19= Bts board not config,38= Target file does not exist,39= File cannot be activated,100= Bts version is same whit the running software version,145= No management rights,255=Null

4 Site Name

Site Name

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

  • If the value of Cause is 5, the configured TMU software is activated. During the activation, the BTS is re-initialized and the services are interrupted.
  • If the value of Cause is not 5, the configured TMU software is not activated, and the BTS is running on the existing version. The BTS is not re-initialized, and the services are not interrupted.

System Actions

None

Possible Causes

  • The TMU software is successfully activated. The value of Cause is 5.
  • The BTS is in abnormal state. The value of Cause of 4 and that of NACK cause is 255.
  • There are conflicts in the BTS management rights. The value of Cause of 4 and that of NACK cause is 145.
  • The transmission between the BSC and the BTS is faulty. The value of Cause of 1 or 4 and that of NACK cause is 14.
  • The communication between the BSC and the BTS is faulty. The value of Cause of 1 or 4 and that of NACK cause is 14.
  • The BTS device is faulty. The value of Cause of 1 or 4 and that of NACK cause is 38 or 39.
  • The BSC device is faulty. The value of Cause of 1 or 4 and that of NACK cause is 255.
  • The BTS software version fails to be obtained from the OMU. The value of Cause is 6.

Procedure

  1. Check the Cause and the NACK cause in Location info.
    1. If the value of Cause is 5, you can infer that the TMU software is successfully activated. Check whether the TMU software version is the same as the target version.

      Y => The alarm handling is complete.

      N => Reload the correct version of the TMU software. The alarm handling is complete.

    2. If the value of Cause is 4 and that of NACK cause is 145, you can infer that there are conflicts in the BTS management rights. Go to 2.
    3. If the value of Cause is 4 and that of NACK cause is 255, you can infer that the BTS is in abnormal state. Go to 3.
    4. If the value of Cause is 1 or 4 and that of NACK cause is 255, you can infer that the BTS is in abnormal state or the Abis interface board of the BSC is faulty. Go to 3.
    5. If the value of Cause is 1 or 4 and that of NACK cause is 14, you can infer that the transmission or communication between the BSC and the BTS is faulty.Go to 5
    6. If the value of Cause is 6, you can infer that the BTS software version fails to be obtained from the OMU. Go to 7.
    7. If the value of Cause is 1 or 4 and that of NACK cause is 38 or 39, you can infer that the TMUis faulty. Go to 8.
  2. Check the BTS management rights.
    1. Check whether local management rights are obtained according to the Site No.

      Y => The Management Authority in the Near End is Ok. Go to b.

      N => The Management Authority in the Near End is No. Contact Huawei Customer Service Center.

    2. Contact the BTS maintenance engineer to Release the site management right at the local end.
    3. Reload the correct version of the TMU. Check whether the TMU software version is the same as the target version.

      Y => The alarm handling is complete.

      N => Contact Huawei Customer Service Center.

  3. Check whether the alarm 4770 Site Reset Alarm is reported.
    1. Log in to the LMT, and then choose Alarm Maintenance > Browse Alarm. Check whether 4770 Site Reset Alarm is reported according to the Site No.

      Y => Go to b.

      N => Contact Huawei Customer Service Center.

    2. Rectify the fault according to the alarm help.
    3. Reload the correct version of the TMU. Check whether the TMU software version is the same as the target version.

      Y => The alarm handling is complete.

      N => Contact Huawei Customer Service Center.

  4. Check whether the Abis interface board of the BSC reports equipment-related alarms related to equipment.
    1. Log in to the LMT, and then choose Alarm Maintenance > Browse Alarm. Check whether the following alarms are reported.

      21205 Board Fault

      21206 CPU Fault

      Y => Go to b.

      N => Contact Huawei Customer Service Center.

    2. Rectify the fault according to the alarm help.
    3. Reload the TMU software. Check whether the TMU software version is the same as the target version.

      Y => The alarm handling is complete.

      N => Contact Huawei Customer Service Center.

  5. Check whether the Abis interface board reports parent alarms related to the trunk cables.
    1. Log in to the LMT, and then choose Alarm Maintenance > Browse Alarm. Check whether the corresponding port on the Abis interface board reports any of the following alarms related to transmission.

      408 Automatic Loading and Activation of BTS TMU Version

      20081 Loss of E1/T1 Signals (LOS)

      20082 Loss of E1/T1 Frames (LOF)

      20083 Remote E1/T1 Alarm (RAI)

      20084 E1/T1 Alarm Indication Signal (AIS)

      20085 Loss of E1/T1 Multiframes (LOM)

      20086 E1/T1 Link Loopback

      20087 High BER over the E1/T1 Link

      20221 Loss of Clock on the Optical Port (RLOC)

      20222 Loss of Signals on the Optical Port (RLOS)

      20223 Loss of Received Signal Frames on the Optical Port (RLOF)

      20224 Out-of-Synchronization of Received Signal Frames on the Optical Port (ROOF)

      20226 Regenerator Section Signal Failure (RSF)

      20227 Regenerator Section Signal Deteriorated (RSD)

      20228 Multiplex Section Alarm Indication Signal (MAIS)

      20229 Multiplex Section Remote Defect Indication (MRDI)

      20230 Loopback on the Optical Port

      20231 Administration Unit Alarm Indication Signal (AUAIS)

      20232 Loss of Administration Unit Pointer (AULOP)

      20233 Service Unequipped on the High-Order Path of the Optical Port (HPUNEQ)

      20235 High-Order Path Signal Label Byte Mismatch (HPSLM)

      20236 High-Order Path Signal Failure (HPSF)

      20237 High-Order Path Signal Deteriorated (HPSD)

      20238 Remote Defect Indication on the High-Order Path of the Optical Port (HPRDI)

      20239 Loss of Tributary Unit Multi-frames (TULOM)

      20240 Tributary Unit Alarm Indication Signal (TUAIS)

      20241 Loss of Tributary Unit Pointer (TULOP)

      20242 Service Unequipped on the Lower-Order Path of the Optical Port (LPUNEQ)

      20244 Signal Flag Mismatch on the Low-Order Path of the Optical Port (LPSLM)

      20245 Low-Order Path Remote Failure Indicaton (LPRFI)

      20246 Low-Order Path Remote Defect Indication (LPRDI)

      20247 Tributary Unit Type Mismatch (TUSIZEERR)

      20248 Loss of Tributary Signals (LOS)

      20249 Tributary Alarm Indication Signal (AIS)

      20250 Loss of Tributary Frames (LOF)

      20251 Remote Alarm Indication over the Tributary (RAI)

      20254 Tributary Loopback Alarm

      20255 Optical Module Fault

      Y => Go to b.

      N => Go to 6.

    2. Rectify the fault according to the alarm help.
    3. Reload the TMU software. Check whether the TMU software version is the same as the target version.

      Y => The alarm handling is complete.

      N => Go to 6.

  6. Check whether the Abis interface board reports alarms related to transmission.
    1. Log in to the LMT, and then choose Alarm Maintenance > Browse Alarm. Check whether the following alarms are reported.

      1000 LAPD OML Fault

      4102 TRX LAPD Link Interrupt Alarm

      Y => Go to b.

      N => Go to 7.

    2. Rectify the fault according to the alarm help.
    3. Reload the TMU software. Check whether the TMU software version is the same as the target version.

      Y => The alarm handling is complete.

      N => Contact Huawei Customer Service Center.

  7. Check whether the software is downloaded to the GBAM.

    Y => Contact Huawei Customer Service Center.

    N => Download the software to the GBAM again. If the alarm is cleared, the alarm handling is complete. If the alarm persists, Contact Huawei Customer Service Center.

  8. Check the TMU of the BTS.
    1. Reset the TMU. Check whether the TMU software version is the same as the target version.

      Y => The alarm handling is complete.

      N => Go to 6.

    2. Replace the TMU. Check whether the TMU software version is the same as the target version.

      Y => The alarm handling is complete.

      N => Contact Huawei Customer Service Center.


Huawei Proprietary and Confidential
Copyright © Huawei Technologies Co., Ltd.