Alarms Inter System

Generation Principles and Handling Measures of Configuration Conflicts on the 3900 Series Multi-Mode Base Station

Contents

1 Overview.......................................................................................51.1 Purpose...............................................................................................................................................................8

1.2 Overview............................................................................................................................................................8

1.3 Usage Guide.......................................................................................................................................................8

2 Alarm ID: 26270.............................................................................92.1 Alarm Detection Principle.................................................................................................................................9

2.2 Impact on the System.........................................................................................................................................9

2.3 Alarm Handling Measure...................................................................................................................................9

3 Alarm ID: 26271...........................................................................103.1 Alarm Detection Principle...............................................................................................................................10

3.2 Impact on the System.......................................................................................................................................10

3.3 Alarm Handling Measure.................................................................................................................................10

3.3.2 Alarm Suppression/Enabling Settings....................................................................................................11

3.3.3 EMU Configuration Parameter Settings.................................................................................................12

3.3.4 Output Port Status Settings.....................................................................................................................13

3.3.5 Standby Analog Sensor Configuration...................................................................................................14

3.3.6 Boolean Alarm Level Configuration......................................................................................................14

3.3.7 Power System Controlling Parameter Settings.......................................................................................14

3.3.8 Battery Management Parameter Settings...............................................................................................15

3.3.9 Battery Group Temperature Compensation Parameter Settings.............................................................17

3.3.10 Power Module Parameter Settings.......................................................................................................19

3.3.11 Environment Parameter Settings..........................................................................................................20

3.3.12 Standby Parameter Settings..................................................................................................................22

3.3.13 High-Temperature Shutdown Protection Parameter Settings...............................................................23

3.3.14 Battery Group Capacity Detection Parameter Settings........................................................................25

3.3.15 Voltage Measurement Reference Settings............................................................................................25

3.3.16 Power Distribution Analog Calibration Coefficient Settings...............................................................25

3.3.17 Alarm Severity Settings........................................................................................................................25

3.3.18 Battery Auto-Test Parameter Settings...................................................................................................26

3.3.19 Power System Parameter Settings........................................................................................................26

3.3.20 Board Speed Regulation Settings.........................................................................................................27

3.3.21 Speed Regulation Message Delivery....................................................................................................27

Issue 01 (2010-02-08) Huawei Confidential Page 1 of 50


3.3.22 High/Low Temperature Alarm Threshold Settings...............................................................................28

3.3.23 Heater Controlling Parameter Settings.................................................................................................29

3.3.24 Temperature Control Parameter Settings in the Temperature Control System.....................................29

3.3.25 Speed Regulation Settings....................................................................................................................30

3.3.26 Speed Regulation Message Settings.....................................................................................................31

3.3.27 High/Low Temperature Alarm Threshold Settings of Air Inlet............................................................31

3.3.28 Speed Regulation Controlling Parameter Settings...............................................................................32

3.3.29 Environmental Alarm Suppression/Enabling Settings.........................................................................32

3.3.30 Boolean Alarm Level Configuration....................................................................................................33







5.3.1 Configuration Conflict of the Dry Contact Alarm Levels......................................................................36

5.3.2 GPS Parameter Configuration Conflict..................................................................................................37




6.3.2 Cabinet, Subrack, and Slot Configuration Inconsistency of the Same Board........................................40

6.3.3 Same Cabinet, Subrack, and Slot Configuration for Different Boards...................................................41




7.3.1 Handling Measure Before Software Upgrade........................................................................................44

7.3.2 Handling Measure After Upgrade...........................................................................................................46











Figures

Figure 3-1 Parameters of the alarm.......................................................................................................................11

Figure 3-2 Analog alarm/Boolean alarm...............................................................................................................12

Figure 3-3 LST EMU............................................................................................................................................12

Figure 3-4 LST BTSEXD.....................................................................................................................................13

Figure 3-5 LST BTSENVALMPORT...................................................................................................................14

Figure 3-6 LST BTSAPMUBP.............................................................................................................................15

Figure 3-7 LST BATTERY...................................................................................................................................16

Figure 3-8 LST BTSAPMUBP.............................................................................................................................16

Figure 3-9 LST BATTERY...................................................................................................................................17

Figure 3-10 LST BTSAPMUBP...........................................................................................................................18

Figure 3-11 LST BATTERY.................................................................................................................................19

Figure 3-12 LST BTSBRD...................................................................................................................................19

Figure 3-13 LST PSU...........................................................................................................................................20


Figure 3-15 LST PMU..........................................................................................................................................22

Figure 3-16 LST BTSENVALMPORT.................................................................................................................23

Figure 3-17 LST ALMPORT................................................................................................................................23


Figure 3-19 LST HTPROTECT............................................................................................................................24




Figure 3-23 LST BTSDHEUBP...........................................................................................................................28

Figure 3-24 LST TCU...........................................................................................................................................29

Figure 3-25 LST BTSDHEUBP...........................................................................................................................30

Figure 3-26 LST BTSFMUABP...........................................................................................................................31







Figure 5-1 Alarm about the configuration conflict of the dry contact..................................................................36

Figure 5-2 LST BTSENVALMPORT...................................................................................................................37

Figure 5-3 LST ALMPORT..................................................................................................................................37

Figure 5-4 LST BTSUSCUBP..............................................................................................................................38

Figure 5-5 LST GPSDELAY................................................................................................................................38

Figure 6-1 Cabinet, subrack, and slot configuration inconsistency of the same board.........................................40

Figure 6-2 Same cabinet, subrack, and slot configuration for different boards....................................................40

Figure 6-3 Cabinet, subrack, and slot configuration inconsistency of the same board.........................................41

Figure 6-4 Same cabinet, subrack, and slot configuration for different boards....................................................42

Figure 7-1 Configuration conflict of the cabinet type...........................................................................................43

Figure 9-1 Setting loading control rights at the UMTS side.................................................................................49

Figure 9-2 Setting loading control rights at the GSM side...................................................................................49

Figure 9-3 Querying the running version of NodeB.............................................................................................50

Figure 9-4 Querying the running version of the GSM..........................................................................................50



Tables

Table 7-1 Cabinet type conversion........................................................................................................................44



1 Overview

1.1 PurposeThis document describes the generation principles and handling measures of the configuration conflict alarms in the SRAN3.0 and SRAN5.0. Currently, the codes keep unchanged. Field engineers and test engineers, however, are not familiar with the generation principles and handling measures of the configuration conflict alarms. Therefore, when these alarms are generated, they tend to ask development engineers to locate or clear these alarms. This greatly reduces the alarm processing efficiency.

This document aims to instruct field engineers and test engineers to check whether the configuration is incorrect and solve problems immediately when configuration conflict alarms are generated.

1.2 OverviewThis document provides the generation principles and clearance measures of seven types of conflict alarms. The seven types of conflict alarms are as follows:

Inter-System Communication Failure

Inter-System Monitoring Device Parameter Settings Conflict

Inter-System RF Unit Parameter Settings Conflict

Inter-System BBU Board Parameter Settings Conflict

Inter-System Board Object Configuration Conflict

Inter-System Cabinet Configuration Conflict

Inter-System Site-Level Configuration Conflict

Inter-System Control Rights Conflict

1.3 Usage GuideSearch for the alarm ID or alarm name reported by the alarm console and obtain the required content.

You can also search for the name of the configuration item related to the conflict alarm.



2 Alarm ID: 26270

Alarm name: Inter-System Communication Failure

2.1 Alarm Detection PrincipleIn the case of the multiple-mode configuration, this alarm is generated when communication between the main control board of this system and the main control board of another mode becomes abnormal.

2.2 Impact on the SystemThe base station cannot perform consistency check on inter-system configuration or shield inter-system public alarms. In this case, different systems report public alarms repeatedly.

2.3 Alarm Handling MeasureSee the handling suggestions for the alarm.



3 Alarm ID: 26271

Alarm name: Inter-System Monitoring Device Parameter Settings Conflict

3.1 Alarm Detection PrincipleIn the case of the multiple-mode configuration, this alarm is generated when the monitor device parameter configured for a system is inconsistent with this parameter configured for another system.

This alarm is detected and reported by the SMS software. The configuration conflict alarm is detected only when the parameters are sent to the integrated-equipment board by the SMS software.

This alarm is reported only in the dual mode or multiple mode scenarios.

Case:

When you configure the power system type (APM30, APM100, APM200, PS4890, EPS4815, or SC48200) for the PMU on the BSC, the configuration is sent only to the main control board. The main control board does not send the configuration to the PMU. Therefore, when different power types are configured for the two GU sides, the GU does not generate a conflict alarm.

3.2 Impact on the SystemWhen the setting of the monitor device parameter for a certain system is incorrect, the data sent from this side does not take effect, and an error alarm is generated.



3.3 Alarm Handling MeasureThis alarm contains five major parameters, namely, Cabinet No., Subrack No., Slot No., Configuration Item, and Board Type (as shown in Figure 3-1).

Cabinet No., Subrack No., and Slot No indicate the cabinet, subrack, and slot where the faulty board is located. Configuration Item indicates the parameter that causes configuration conflict. Board Type indicates the type of the faulty board. The following part describes the generation principle and handling measure of the conflict alarm caused by each configuration item.

Figure 3-1 Parameters of the alarm

3.3.2 Alarm Suppression/Enabling Settings

Condition：

In the case of the multiple-mode configuration, the alarm of this configuration item is generated when MU dry contact alarm enabling, special Boolean alarm enabling, or analog sensor alarm enabling configured for the main control boards of different systems are different.

Handling Measure：

Step 1 To check whether the configuration conflict of dry contact alarm enabling occurs, check whether the port configurations of the EMU dry contacts for the two GU sides are the same. If the port configurations are the same, go to step 2. If the port configurations are different, modify the configurations to ensure that the port configurations of the EMU dry contacts for the two GU sides are the same.

To view the dry contact configuration at the GSM side, run LST BTSENVALMPORT.

To view the dry contact configuration at the UMTS side, run LST ALMPORT.

To change the dry contact configuration at the GSM side, run SET BTSENVALMPORT.

To change the dry contact configuration at the UMTS side, run SET ALMPORT.



Step 2 Check whether the configuration conflict of special Boolean alarm enabling occurs. If yes, modify the configuration of one side to ensure that the special Boolean alarm enabling configurations of the two GU sides are the same.

To view the configuration of the special Boolean alarm and analog sensor at the GSM side, run LST BTSDEMUBP.

Figure 3-1 Analog alarm/Boolean alarm

To view the configuration of the special Boolean alarm at the UMTS side, run LST EMU.

Figure 3-2 LST EMU

To set the configuration of the special Boolean alarm at the UMTS side, run MOD EMU.

Step 3 Check whether the alarm is cleared. If not, contact Huawei customer service center.

3.3.3 EMU Configuration Parameter Settings

Condition：

In the case of the dual-modes or multiple-mode configuration, this alarm is generated when the EMU temperature, humidity, and lower and upper thresholds (alarm lower and upper



thresholds of -48 V, +24 V, temperature sensor, humidity sensor, external analog sensor) configured for main control boards of different systems are different.

Only the lower and upper thresholds of the temperature sensor and humidity sensor can be configured on the maintenance console, and other parameters are not configurable. Therefore, when the alarm of this configuration item is generated, you only need to check whether the lower and upper thresholds of the temperature sensor and humidity sensor configured for the two GU sides are the same.

Handling Measure：

Step 1 View the lower and upper thresholds of the temperature sensor and humidity sensor at the GSM side.

To view the lower and upper thresholds of the temperature sensor and humidity sensor at the GSM side, run LST BTSEXD.

To modify the lower and upper thresholds of the temperature sensor and humidity sensor at the GSM side, run SET BTSEXD.

Figure 3-1 LST BTSEXD

Step 2 View the lower and upper thresholds of the temperature sensor and humidity sensor at the UMTS side.

To view the lower and upper thresholds of the temperature sensor and humidity sensor at the UMTS side, run LST EMUTHLIMIT.

To modify the lower and upper thresholds of the temperature sensor and humidity sensor at the UMTS side, run SET EMUTHLIMIT.

Step 3 Check whether the settings of the preceding parameters at the two GU sides are the same. If the settings are different, modify the settings to ensure that the settings of the preceding parameters for the two GU sides are the same. If the settings of the two GU sides are the same but the alarm still exists, contact Huawei customer service center.

3.3.4 Output Port Status SettingsCondition

In the case of the dual-mode or multiple-mode configuration, the alarm of this configuration item is generated when the EMU output port status configured for the main control boards of different systems is different.

Handling Measure

Step 1 Check whether the relay parameter settings for the two GU sides are the same. If not, modify the settings to ensure that the relay parameter settings for the two GU sides are the same. If yes, contact Huawei customer service center.

To view the relay parameter setting at the GSM side, run LST BTSOUTPUT.



To view the relay parameter setting at the UMTS side, run LST OUTPORT.

To modify the relay parameter setting at the GSM side, run SET BTSOUTPUT.

To modify the relay parameter setting at the UMTS side, run SET OUTPORT.

3.3.5 Standby Analog Sensor ConfigurationCurrently, the GSM does not support the relevant command. Therefore, the conflict alarm of this configuration item will not be generated.

3.3.6 Boolean Alarm Level ConfigurationCondition

In the case of the dual-mode or multiple-mode configuration, the alarm of this configuration item is generated when the EMU main control point alarm level and special Boolean alarm level configured for the main control boards of different systems are different.

Only the dry contact alarm level can be modified on the maintenance console. When this alarm is generated, you only need to check whether the dry contact alarm level configured for the two GU sides is the same.

Handling Measure

Step 1 To check whether the configuration conflict of the dry contact alarm level occurs, check whether the configurations of the EMU dry contact alarm level for the two GU sides are the same. If not, modify the configurations to ensure that the configurations for the two GU sides are the same. If yes, contact Huawei customer service center.

To view the dry contact configuration at the GSM side, run LST BTSENVALMPORT.

Figure 3-1 LST BTSENVALMPORT

To view the dry contact configuration at the UMTS side, run LST ALMPORT.

To change the dry contact configuration at the GSM side, run SET BTSENVALMPORT.

To change the dry contact configuration at the UMTS side, run SET ALMPORT.

3.3.7 Power System Controlling Parameter SettingsCondition

In the case of the dual-mode or multiple-mode configuration, the alarm of this configuration item is generated when the settings of the PMU power system controlling parameter for the main control boards of different systems are different.

Handling Measure



Currently, the GSM does not send this parameter. Therefore, the alarm of this configuration item will not be reported to the maintenance console.

3.3.8 Battery Management Parameter SettingsCondition

In the case of the dual-mode or multiple-mode configuration, the alarm of this configuration item is generated when the settings of the PMU battery management parameter for the main control boards of different systems are different. This alarm is generated only when the maintenance console is configured with the battery.

To check whether the battery is configured at the GSM side, run LST BTSAPMUBP (the information in red circle in the following figure indicates that a battery box is configured).

Figure 3-1 LST BTSAPMUBP

To check whether the battery is configured at the UMTS side, run LST BATTERY.



Figure 3-2 LST BATTERY

Handling Measure

Step 2 Check whether the settings of the charge current coefficient for the two GU sides are the same.

Step 3 Check whether the configurations of the battery capacity for the two GU sides are the same.

Step 4 Check whether the configurations of the battery’s scheduled boost charging time for the two GU sides are the same. In the SRAN3.0, the boost charging time cannot be set at the GSM side, and the code is hard-coded to 60. Therefore, the boost charging time at the UMTS side must be 60 days.

Figure 3-1 shows the charge current coefficient and battery capacity at the GSM side.


Figure 3-2 shows the charge current coefficient and battery capacity at the UMTS side.




3.3.9 Battery Group Temperature Compensation Parameter SettingsCondition

In the case of the dual-mode or multiple-mode configuration, the alarm of this configuration item is generated when the settings of the PMU battery group compensation parameter for the main control boards of different systems are different.

The parameters in the configuration item that may cause configuration conflict include Upper Assembled Battery 1 Temp Measure, Lower Assembled Battery1 TEMP Measure, Temperature Alarm Upper Threshold, Temperature Alarm Lower Threshold, Upper Assembled Battery 2 Temp Measure, Lower Assembled Battery 2 TEMP Measure, Temperature Compensation Coefficient, and Temperature Basis for Compensation.

In versions later than SRAN3.0, only the Temperature Alarm Upper Threshold and Temperature Alarm Lower Threshold can be configured.

Handling Measure

Step 1 View the Temperature Alarm Upper Threshold and Temperature Alarm Lower Threshold at the GSM side.

To view the Temperature Alarm Upper Threshold and Temperature Alarm Lower Threshold at the GSM side, run LST BTSAPMUBP.

To set the Temperature Alarm Upper Threshold and Temperature Alarm Lower Threshold at the GSM side, run SET BTSAPMUBP.




Step 2 View the Temperature Alarm Upper Threshold and Temperature Alarm Lower Threshold at the UMTS side.

To view the Temperature Alarm Upper Threshold and Temperature Alarm Lower Threshold at the UMTS side, run LST BATTERY.

To set the Temperature Alarm Upper Threshold and Temperature Alarm Lower Threshold at the UMTS side, run SET BATTERY.




Step 3 Check whether the settings of Temperature Alarm Upper Threshold and Temperature Alarm Lower Threshold for the two GU sides are the same by comparison. If not, modify the settings to ensure that the settings are the same. If yes, contact Huawei customer service center.

3.3.10 Power Module Parameter SettingsCondition

In the case of the dual-mode or multiple-mode configuration, the alarm of this configuration item is generated when the PSU quantities configured for main control boards of different systems are different.

Handling Measure

Step 1 Check whether the PSU quantities configured at the two GU sides are the same.

To view the PSU quantity at the GSM side, run LST BTSBRD.

The information shown in Figure 3-1 indicates that one PSU board is configured at the GSM side.

Figure 3-1 LST BTSBRD

To view the PSU quantity at the UMTS side, run LST PSU.



Figure 3-2 LST PSU

To add a PSU board at the GSM side, run ADD BTSBRD.

To add a PSU board at the UMTS side, run ADD PSU.

3.3.11 Environment Parameter Settings

Condition

In the case of the dual-mode or multiple-mode configuration, the alarm of this configuration item is generated when the settings of the PMU environmental parameters for main control boards of different systems are different.

The environmental parameters that are sent to the PMU include Upper ENV TEMP Alarm, Lower ENV TEMP Alarm, Upper Threshold of Humidity Alarm, and Lower Threshold of Humidity Alarm. The parameters also include the environmental temperature measurement lower and upper thresholds and environmental humidity measurement lower and upper thresholds.

At the GSM side, only the Upper ENV TEMP Alarm, Lower ENV TEMP Alarm, Upper Threshold of Humidity Alarm, and Lower Threshold of Humidity Alarm can be configured. The other parameters are hard-coded. Therefore, when manually setting parameters at the UMTS side, you can only modify settings of Upper ENV TEMP Alarm, Lower ENV TEMP Alarm, Upper Threshold of Humidity Alarm, and Lower Threshold of Humidity Alarm. If you modify the other parameters, a conflict alarm may result.

Handling Measure

Step 1 To view Upper ENV TEMP Alarm, Lower ENV TEMP Alarm, Upper Threshold of Humidity Alarm, and Lower Threshold of Humidity Alarm at the GSM side, run LST BTSAPMUBP.

To modify Upper ENV TEMP Alarm, Lower ENV TEMP Alarm, Upper Threshold of Humidity Alarm, and Lower Threshold of Humidity Alarm at the GSM side, run SET BTSAPMUBP.




Step 2 To view Upper ENV TEMP Alarm, Lower ENV TEMP Alarm, Upper Threshold of Humidity Alarm, and Lower Threshold of Humidity Alarm at the UMTS side, run LST PMU.



Figure 3-1 LST PMU

To modify Upper ENV TEMP Alarm, Lower ENV TEMP Alarm, Upper Threshold of Humidity Alarm, and Lower Threshold of Humidity Alarm, you can only delete the PMU by running RMV PMU and then add the PMU by running ADD PMU. When entering information about the PMU, you can modify the default environmental temperature and humidity alarm lower and upper thresholds.

Step 3 Check whether the settings of the parameters for the two GU sides are the same by comparison. If not, modify the settings to ensure that the settings of the parameters for the two GU sides are the same. If yes, contact Huawei customer service center.

3.3.12 Standby Parameter SettingsCondition

In the case of the dual-mode or multiple-mode configuration, the alarm of this configuration item is generated when the configurations of the PMU dry contact alarm level for main control boards of different systems are different.

Handling Measure

Step 1 View the high and low levels of the dry contact at the GSM side.



To view the high and low levels of the dry contact at the GSM side, run LST BTSENVALMPORT.

To set the high and low levels of the dry contact at the GSM side, run SET BTSENVALMPORT.


Step 2 View the high and low levels of the dry contact at the UMTS side.

To view the high and low levels of the dry contact at the UMTS side, run LST ALMPORT.

To set the high and low levels of the dry contact at the UMTS side, run SET ALMPORT.

Figure 3-1 LST ALMPORT

Step 3 Check whether the settings of the dry contact alarm levels for the two GU sides are the same by comparison. If not, modify the setting to ensure that the dry contact alarm levels for the two GU sides are the same. If yes, contact Huawei customer service center.

3.3.13 High-Temperature Shutdown Protection Parameter SettingsCondition

In the case of the dual-mode or multiple-mode configuration, the alarm of this configuration item is generated when the settings of the PMU high-temperature shutdown protection parameters for main control boards of different systems are different.

The high-temperature shutdown protection parameters that are sent to the PMU include High Temp Load Power Off and Shutdown Temperature, and also load power off and load temperature.

Only High Temp Load Power Off and Shutdown Temperature can be configured on the maintenance console. Therefore, when checking whether a configuration conflict occurs, you need to check whether the values of only High Temp Load Power Off and Shutdown Temperature for the two GU sides are the same.



Handling Measure

Step 1 View High Temp Load Power Off and Shutdown Temperature at the GSM side.

To view High Temp Load Power Off and Shutdown Temperature at the GSM side, run LST BTSAPMUBP.

To modify High Temp Load Power Off and Shutdown Temperature at the GSM side, run SET BTSAPMUBP.


Step 2 View High Temp Load Power Off and Shutdown Temperature at the UMTS side.

To view High Temp Load Power Off and Shutdown Temperature at the UMTS side, run LST HTPROTECT.

To modify High Temp Load Power Off and Shutdown Temperature at the UMTS side, run SET HTPROTECT.

Figure 3-1 LST HTPROTECT



Step 3 Check whether the settings of High Temp Load Power Off and Shutdown Temperature for the two GU sides are the same by comparison. If not, modify the setting to ensure that the settings of High Temp Load Power Off and Shutdown Temperature for the two GU sides are the same. If yes, contact Huawei customer service center.

3.3.14 Battery Group Capacity Detection Parameter Settings

Currently, this configuration item is not supported. Therefore, the conflict alarm of this configuration item will not be generated.

3.3.15 Voltage Measurement Reference SettingsCurrently, this configuration item is not supported. Therefore, the conflict alarm of this configuration item will not be generated.

3.3.16 Power Distribution Analog Calibration Coefficient Settings

Currently, this configuration item is not supported. Therefore, the conflict alarm of this configuration item will not be generated.

3.3.17 Alarm Severity SettingsCondition

In the case of the dual-mode or multiple-mode configuration, the alarm of this configuration item is generated when the settings of the PMU dry contact alarm enabling (it refers to whether the port is enabled rather than the setting of high and low levels) for main control boards of different systems are different.

Handling Measure

Step 1 View the port configuration of the dry contact at the GSM side (whether the port is enabled).

To view the port configuration of the dry contact at the GSM side, run LST BTSENVALMPORT.

To set the port configuration of the dry contact at the GSM side, run SET BTSENVALMPORT.


Step 2 View the port configuration of the dry contact at the UMTS side.

To view the port configuration of the dry contact at the UMTS side, run LST ALMPORT.

To set the port configuration of the dry contact at the UMTS side, run SET ALMPORT.




Step 3 Check whether the port configurations of the dry contacts for the two GU sides are the same by comparison. If not, modify the configurations to ensure that the port configurations of the dry contacts for the two GU sides are the same. If yes, contact Huawei customer service center.

3.3.18 Battery Auto-Test Parameter SettingsCurrently, this configuration item is not supported. Therefore, the conflict alarm of this configuration item will not be generated.

3.3.19 Power System Parameter SettingsCondition

In the case of dual-mode or multiple-mode configuration, the alarm of this configuration item is generated when the settings of the PMU power system parameters for main control boards of different systems are different.

The power system parameters that are sent to the PMU include Boost-Charging Voltage, Float-Charging Voltage, Load Shutdown Flag, Low Voltage Shutdown Flag, Load Shutdown Voltage, Shutdown Voltage, Low Temperature, StartLoadPower-off Allowed State, Low Temperature Start Load Power Off Temp., AC Voltage Upper Threshold, AC Voltage Lower Threshold, DC Voltage Upper Threshold, and DC Voltage Lower Threshold.

Handling Measure

Step 1 View the power system parameters sent from the GSM side.

To view the power system parameters sent from the GSM side, run LST BTSAPMUBP.

To modify the power system parameters sent from the GSM side, run SET BTSAPMUBP.




Step 2 View the power system parameters sent from the UMTS side.

To view the boost-charging voltage and float-charging voltage, run LST BCFCVOLTAGE.

To modify the boost-charging voltage and float-charging voltage, run SET BCFCVOLTAGE.

To view the PMU power-off parameter setting, run LST SDPA.

To modify the PMU power-off parameter setting, run SET SDPA.

To view the PMU DC/AC alarm threshold, run LST ACDCVLIMIT.

To modify the PMU DC/AC alarm threshold, run SET ACDCVLIMIT.

Step 3 Check whether the settings of the parameters for the two GU sides are the same by comparison.

3.3.20 Board Speed Regulation Settings

Currently, the command word for implementing the configuration item is unavailable. Therefore, the conflict alarm of this configuration item will not be generated.

3.3.21 Speed Regulation Message DeliveryCurrently, the command word for implementing the configuration item is unavailable. Therefore, the conflict alarm of this configuration item will not be generated.



3.3.22 High/Low Temperature Alarm Threshold SettingsCondition

In the case of the dual-mode or multiple-mode configuration, this alarm is generated when the configurations of the TCU high/low temperature alarm threshold for main control boards of different systems are different.

Handling Measure

Step 1 View the high and low temperature alarm thresholds at the GSM side.

To view the high and low temperature alarm thresholds at the GSM side, run LST BTSDHEUBP.

To modify the high and low temperature alarm thresholds at the GSM side, run SET BTSDHEUBP.

Figure 3-1 LST BTSDHEUBP

Step 2 View the high and low temperature alarm thresholds at the UMTS side.

To view the high and low temperature alarm thresholds at the UMTS side, run LST TCU.

To modify the high and low temperature alarm thresholds at the UMTS side, run MOD TCU.



Figure 3-1 LST TCU

Step 3 Check whether the settings of the high and low temperature alarm thresholds for the two GU sides are the same.

3.3.23 Heater Controlling Parameter SettingsIn versions later than SRAN3.0, the UMTS does not send this parameter. Therefore, the conflict alarm of this configuration item will not be generated.

3.3.24 Temperature Control Parameter Settings in the Temperature Control SystemCondition

In the case of the dual-mode or multiple-mode configuration, the alarm of this configuration item is generated when the settings of the temperature control parameters in the TCU temperature control system for main control boards of different systems are different.

The temperature control parameters in the temperature control system include Low Temperature Critical Point, High Temperature Critical Point, Tout Limit, Dead Band, Normal Temperature Delta Tin, Normal Temperature Delta Tout, and High Temperature Delta Tout.

Handling Measure

Step 1 View the settings of the temperature control parameters in the temperature control system at the GSM side.

To view the settings of the temperature control parameters in the temperature control system at the GSM side, run LST BTSDHEUBP.

To modify the settings of the temperature control parameters in the temperature control system at the GSM side, run SET BTSDHEUBP.



Figure 3-1 LST BTSDHEUBP

Step 2 View the settings of the temperature control parameters in the temperature control system at the UMTS side.

To view the settings of the temperature control parameters in the temperature control system at the UMTS side, run LST HTCDPA.

To modify the settings of the temperature control parameters in the temperature control system at the UMTS side, run MOD HTCDPA.

3.3.25 Speed Regulation SettingsCondition

In the case of dual-mode or multiple-mode configuration, this alarm is generated when the settings of the FMU speed regulation modes for main control boards of different systems are different.

The GSM sends two speed regulation modes, namely, main control board speed regulation and temperature control speed regulation. The UMTS sends only one speed regulation mode, main control. If a conflict alarm is generated, it indicates that the GSM sends the temperature control mode.

The GSM sends the temperature control mode in the following scenarios:

In the board parameters sent by the BSC, Smart Temperature Control is set to Disabled.

The links of all TRX boards managed by the FMU are broken.

Handling Measure



Step 1 Check whether the setting of Smart Temperature Control in the board parameters sent by the BSC. If it is set to Disabled, change the value to Enabled. If it is set to Enabled, go to step 2.

To view the settings of the smart temperature control parameter at the GSM side, run LST BTSFMUABP.

To set the smart temperature control parameter at the UMTS side, run SET BTSFMUABP.

Figure 3-1 LST BTSFMUABP

Step 2 Check whether the links of all TRX boards managed by the FMU are broken. If yes, process the TRX communication alarm first. If not, contact Huawei customer service center.

When the following conditions are met, it indicates that the FMU manages this TRX board.

For the non-3900L large cabinet, check whether the FMU and RFU are in the same cabinet. If the FMU and RFU are in the same cabinet, the FMU manages the TRX board.

For the 3900L large cabinet, you also need to check the subrack No. The FMU in subrack 11 can manage only the TRX board of subrack 4, and the FMU in subrack 12 can manage only the TRX board of subrack 5.

3.3.26 Speed Regulation Message SettingsThe relevant command word is not checked according to confirmation of the SMS software engineers. Therefore, the conflict alarm of this configuration item will not be generated.

3.3.27 High/Low Temperature Alarm Threshold Settings of Air Inlet




3.3.28 Speed Regulation Controlling Parameter Settings


3.3.29 Environmental Alarm Suppression/Enabling SettingsCondition

In the case of the dual-mode or multiple-mode configuration, this alarm is generated when the settings of FMU dry contact alarm enabling for main control boards of different systems are different.

Handling Measure

Step 1 View the configuration of the dry contact at the UMTS side.

To view the high and low levels of the dry contact at the GSM side, run LST BTSENVALMPORT.



Step 2 View the configuration of the dry contact at the UMTS side.




Step 3 Check whether the settings of the high and low levels of the dry contact for the two GU sides are the same by comparison.



3.3.30 Boolean Alarm Level ConfigurationCondition

In the case of the dual-mode or multiple-mode configuration, this alarm is generated when the configurations of the FMU dry contact alarm level for main control boards of different systems are different.

Handling Measure

Step 1 View the high and low levels of the dry contact at the GSM side.

To view the high and low levels of the dry contact, run LST BTSENVALMPORT.



Step 2 View the high and low levels of the dry contact at the UMTS side.




Step 3 Check whether the settings of the high and low levels of the dry contact for the two GU sides are the same by comparison.



4 Alarm ID: 26272

Alarm name: Inter-System RF Unit Parameter Settings Conflict

4.1 Alarm Detection PrincipleIn the case of multiple-mode configuration, this alarm is generated when the working standards or other parameter settings of the same RF unit are different for different systems.

4.2 Impact on the SystemIf the working systems of the RF unit for different systems are different, software management of the RF unit is affected, which may affect services.

If other parameter settings of the RF unit for different systems are different, data sent from this side cannot take effect.

4.3 Alarm Handling MeasureStep 1 If the working systems of the RF unit for the two GU sides are different, for example, GO for

the GSM side and UO for the UMTS side, change both the working systems to GU.

Step 2 If other parameter settings of the RF unit for different systems are different, solve the problem using the relevant tool.



5 Alarm ID: 26273

Alarm name: Inter-System BBU Board Parameter Settings Conflict

5.1 Alarm Detection PrincipleIn the case of the multiple-mode configuration, this alarm is generated when the parameter settings of boards in the same BBU are different.

This alarm is generated when any of the following conditions is met:

The dry contact alarm levels of the same port configured for different systems conflict.

The relevant GPS parameters configured for the NE of this system are inconsistent with the GPS parameters configured for the NE of another system.

5.2 Impact on the SystemIf the dry contact configurations of the PEU/EIU for different systems conflict, an error alarm is generated at the side with incorrect configuration.

If the GPS parameter settings of the USCU for different systems conflict, data sent from this side cannot take effect.

5.3 Alarm Handling MeasureThis alarm contains five major parameters, namely, Cabinet No., Subrack No., Slot No., Configuration Item, and Board Type.

Cabinet No., Subrack No., and Slot No indicate the cabinet, subrack, and slot where the faulty board is located. Configuration Item indicates the parameter that causes configuration conflict. Board Type indicates the type of the faulty board. This alarm involves two types of configuration item, namely, configuration conflict of the dry contact alarm levels and configuration conflict of GPS parameter configuration conflict. The following sections describes the generation principles and handling measures of the alarms of the two types of configuration item.



5.3.1 Configuration Conflict of the Dry Contact Alarm LevelsCondition

In the case of the dual-mode configuration, the SMS software reports the alarm indicating the configuration conflict of the dry contact alarm levels after detecting that the dry contact of the UPEU board in slot 18 or 19 is configured with different high and low levels at the two GU sides.

This alarm is generated when both the following conditions are met:

The same port is enabled at the two GU sides.

Different high and low levels are set for the same port at the two GU sides.

Only the dry contact configuration of the UPEU in slot 18 or 19 is detected in this alarm.

Figure 5-1 Alarm about the configuration conflict of the dry contact

Handling Measure

Step 2 View the alarm high and low levels of the dry contact at the GSM side.

To view the alarm high and low levels of the dry contact at the GSM side, run LST BTSENVALMPORT.

To set the alarm high and low levels of the dry contact at the GSM side, run SET BTSENVALMPORT.




Step 3 View the alarm high and low levels of the dry contact at the UMTS side. The port is enabled and the configuration conflict is detected only when Work Mode is CUSTOM in Figure 5-1.

To view the alarm high and low levels of the dry contact at the UMTS side, run LST ALMPORT.

To set the alarm high and low levels of the dry contact at the UMTS side, run SET ALMPORT.


Step 4 Compare the configurations of the two GU side to check whether the alarm levels of the port about which an alarm is reported are different for the two GU sides. If the alarm levels of the port are different for the two GU sides, modify the high and low levels of the GSM side or UMTS side. If the alarm levels of the port are the same for the two GU sides, contact Huawei customer service center.

5.3.2 GPS Parameter Configuration ConflictCondition

In the case of the dual-mode configuration, the proxy module reports the alarm indicating the configuration conflict of GPS parameter settings after detecting that the settings of the USCU antenna mask angle, antenna delay, and time zone are different fro the two GU sides.

Currently, the settings of the antenna angle and time zone are not supported. Therefore, these two parameters do not cause the configuration conflict alarm.

Handling Measure



Step 1 View the antenna delay configured for the GSM side.

To view the antenna delay at the GSM side, run LST BTSUSCUBP.

To set the antenna delay at the GSM side, run SET BTSUSCUBP.

In the output of LST BTSUSCUBP shown in Figure 5-1, GPS Antenna Delay is Null. It indicates that the BSC does not send this parameter. In this case, the GPS antenna delay sent to the USCU is 0.

Figure 5-1 LST BTSUSCUBP

Step 2 View the antenna delay at the UMTS side.

To view the antenna delay at UMTS side, run LST GPSDELAY.

To set the antenna delay at the UMTS side, run SET GPSDELAY.

Figure 5-1 LST GPSDELAY

Step 3 Check whether the antenna delay settings for the two GU sides are the same. If not, modify the settings to ensure that the antenna delay settings for the two GU sides are the same.

Outstanding Defects

In versions earlier than V100R009C00SPC072B786, the alarm of this configuration item cannot be reported normally due to problems of code processing and alarm resource file. If the test related to this alarm is required, upgrade the base station to V100R009C00SPC072B786 or later versions.



6 Alarm ID: 26274

Alarm name: Inter-System Board Object Configuration Conflict

6.1 Alarm Detection PrincipleIn the case of the multiple-mode configuration, this alarm is generated when the same physical board is configured with different cabinets, subracks, and slots for different systems or different physical boards are configured with the same cabinet, subrack, and slot for different systems.

This alarm is generated when any of the following conditions is met:

In the dual-mode base station, the same physical board is configured with different cabinets, subracks, and slots for different systems.

In the dual-mode base station, different physical boards are configured with the same cabinet, subrack, and slot for different systems.

6.2 Impact on the SystemThe board cannot be configured or maintained as a public board, which causes inventory information error. As board of the RF unit, the board cannot update software automatically during software upgrade, which causes service interruption.

6.3 Alarm Handling MeasureThis alarm contains eight major parameters, namely, Cabinet No., Subrack No., Slot No., Board Type, Peer Cabinet No., Peer Subrack No., Peer Slot No., and Specific Problem, as shown in the Figure 6-1. Specific Problems indicates whether the alarm is caused by cabinet, subrack, and slot configuration inconsistency of the same board or same cabinet, subrack, and slot configuration for different boards.



Figure 6-1 Cabinet, subrack, and slot configuration inconsistency of the same board

Figure 6-2 Same cabinet, subrack, and slot configuration for different boards

6.3.2 Cabinet, Subrack, and Slot Configuration Inconsistency of the Same BoardCondition

In the case of the dual-mode configuration, the RB MM module reports this alarm after detecting that the same physical board is configured with different cabinets, subracks, and slots for the two GU sides.

Handling Measure



Step 1 Modify the cabinet, subrack, and slot configuration of the board at the two GU sides based on location information in the alarm. For example, for the alarm shown in Figure 6-1, you can change the cabinet No, subrack No., and slot No. of the local PMU board to 1, 7, and 0 respectively, or change the cabinet No, subrack No., and slot No. of the peer PMU board to 0, 7, and 0 respectively.

Figure 6-1 Cabinet, subrack, and slot configuration inconsistency of the same board

Step 2 Check whether the alarm is cleared after modification. If the alarm persists, contact Huawei customer service center.

6.3.3 Same Cabinet, Subrack, and Slot Configuration for Different BoardsCondition

In the case of the dual-mode configuration, the RB MM module reports this alarm after detecting that different physical boards are configured with the same cabinet, subrack, and slot for the two GU sides.

The system checks whether two TRX boards are the same physical board based on the actually scanned topology structure. If the CPRI port number and topology level of the TRX board scanned at one GU side is the same as those scanned at the other side, the two TRX boards are the same physical board.

Check whether two integrated-equipment boards are the same physical board based on the port number and address configuration on the maintenance console. If the port numbers and addresses of the two boards are the same, the two boards are the same physical board.

Handling Measure

Step 1 If a configuration conflict of TRX boards occurs, it indicates that different boards are configured with the same cabinet, subrack, and slot based on location information in the alarm. In this case, you need to modify the cabinet, subrack, and slot configuration of the TRX board at the GSM side or UMTS side to ensure that different TRX boards are configured with different cabinets, subracks, and slots.



Figure 6-1 Same cabinet, subrack, and slot configuration for different boards

Step 2 If a configuration conflict of integrated-equipment board occurs, it indicates that the serial port numbers and addresses of the integrated-equipment board in the same cabinet, subrack, and slot are different for the two GU sides. In this case, you need to change the serial port or address of the board at the GSM side or UMTS side to the actual serial port number or address.

Step 3 Check whether the alarm is cleared after modification. If the alarm persists, contact Huawei customer service center.



7 Alarm ID: 26275

Alarm name: Inter-System Cabinet Configuration Conflict

7.1 Alarm Detection PrincipleIn the case of a multiple-mode base station, this alarm is generated when the cabinet type of a system is inconsistent with the cabinet type of another system.

Figure 7-1 Configuration conflict of the cabinet type

7.2 Impact on the SystemIf an inter-system cabinet type configuration conflict occurs, the cabinet configuration and maintenance and cabinet inventory information record are affected.



7.3 Alarm Handling MeasureThis alarm contains two major parameters, namely, cabinet No. and configuration item.

7.3.1 ConditionIn the dual-mode scenario, the RB MM module reports this alarm after detecting that the same cabinet is configured with different cabinet types in the two systems.

7.3.2 Handling Measure Before Software UpgradeSolve the problems based on the 3900 Series Multi-Mode Base Station V100R002C00SPCxxx Upgrade Guide (SingleRAN2.0 to SingleRAN3.0, M2000-Based).

After the base station is upgraded from SingleRAN2.0 to SingleRAN3.0, the cabinet type is automatically changed based on the configuration of SingleRAN2.0. If the cabinet type configurations of the GSM and UMTS are inconsistent in SingleRAN2.0, an alarm is reported after SingleRAN2.0 is upgraded to SingleRAN3.0. You are advised to check the cabinet type configurations of the GSM and UMTS and ensure that the cabinet type configured for the GSM is consistent with that configured for the UMTS.

Currently, only the problems of the DTCU type and APMU type inconsistency between the GSM and UMTS can be solved before upgrade of the GSM. Other problems can be solved at the GSM side only after upgrade.

Step 1 Query the configuration of the GSM side.

Run LST BTSBRD to query the integrated-equipment boards that are configured for the base station, such as APMU and DTCU.

Run LST BTSAPMUBP to query the APMU configuration.

Step 2 Query the configuration of the UMTS side.

Run LST NODEBTYPE to query the type of the base station.

Run LST PWRSYSCFG to query the PMU configuration.

Run LST NCMUCFG to query the CMU configuration.

Step 3 Obtain the cabinet types of the GSM and UMTS after the base station is upgraded to SingleRAN3.0 based on the configuration in SingleRAN2.0 and the cabinet type conversion table. If the cabinet types of the GSM and UMTS are inconsistent, change the cabinet type of one side to ensure that the cabinet types of the two sides are consistent.

Table 7-1 Cabinet type conversion

GSM side

Base Station Type

Cabinet No.

Configuration Conditions of SingleRAN2.0

Cabinet Type of SingleRAN3.0

DBS3900 0 A non-remote APMU exists. The APMU type is APM4815.

OMB

0 A non-remote APMU exists. The APMU type is APM30.

APM30



GSM side

Base Station Type

Cabinet No.

Configuration Conditions of SingleRAN2.0


0 A non-remote DTCU module exists. TMC

0 Others Virtual

BTS3900A 0 A non-remote APMU exists. The APMU type is APM4815.

OMB

0 A non-remote APMU exists. The APMU type is APM30.

APM30

0 A non-remote APMU exists. The APMU type is APM100/APM200.

APM100

0 A non-remote DTCU module exists. TMC

0 Others Virtual

DBS3900 0 The PMU and CMU are not configured on the BBU.

Virtual

0 The PMU type is APM100/200/30. APM100/200/30

0 The PMU type is OMB and the CMU is also configured.

OMB

0 The PMU type is OMB and the CMU is not configured.

BTS3900D

BTS3900A 0 The type of the PMU configured in subrack 7 is APM30.

APM30

Step 4 Modify the configurations of the GSM side and UMTS side.

GSM side

− Run ADD BTSBRD or RMV BTSBRD to add or delete the APMU and DTCU boards of the base station.

− Run SET BTSAPMUBP to modify the configuration type of the APMU board.

UMTS side

− Run SET PWRSYSCFG to modify the configuration status and type of the PMU.

− Run SET NCMUCFG to modify the configuration status of the CMU.

− End

Example:

Step 1 Query the configurations of the GSM side and UMTS side.

GSM: DBS3900, configured with the non-remote APMU whose type is APM30.

UMTS: DBS3900, not configured with the PMU or CMU.



Step 2 After upgrade, the type of cabinet 0 at the GSM side is APM30, and the type of cabinet 0 at the UMTS side is Virtual based on 7.1.1 Figure 7-1. The two cabinet types are inconsistent. This causes the cabinet configuration conflict alarm. Therefore, you need to modify the cabinet type configuration.

Step 3 Based on 7.1.1 Figure 7-1, the PMU needs to be configured for the APM30 at the UMTS. Then, the type of cabinet after upgrade is APM30. In this case, the cabinet types of the GSM side and UMTS side are consistent. Therefore, you need to modify the configuration of the UMTS side and add the PMU whose type is APM30 before upgrade.

Base Station Type

Cabinet No. Configuration Conditions of SingleRAN2.0


UMTS: DBS3900

0 The PMU type is APM100/200/30.

APM100/200/30

7.3.3 Handling Measure After UpgradeThis section describes the alarm handling measure when alarm 26275 is generated after the base station is upgraded to SingleRAN3.0 or later versions.

Step 1 View the type of the cabinet about which a configuration conflict occurs at the GSM side.

To view the cabinet type at the GSM side, run LST BTSCABINET.

Step 2 View the type of the cabinet about which a configuration conflict occurs at the UMTS side.

To view the cabinet type at the UMTS side, run LST CABINET.

Step 3 View whether the configurations of the type of the cabinet (corresponding cabinet No.) with configuration conflict are different at the two GU sides. If yes, run MOD CABINETTYPE to modify the cabinet type of the UMTS side.

For example, to change cabinet 3 to APM30, run the following command on the NodeB LMT:

MOD CABINETTYPE: CN=3, CT=APM30;

For the value of CT, see the value of this parameter in ADD CABINET.



8 Alarm ID: 26276

Alarm name: Inter-System Site-Level Configuration Conflict

8.1 Alarm Detection PrincipleIn the case of the multiple-mode configuration, this alarm is generated when the site-level configuration (such as clock source type) of a certain system is inconsistent with that of another system. In the case of the dual-mode configuration, this alarm is generated when one system is configured with the GPS clock and the other system is configured with an external clock.

8.2 Impact on the SystemIf the clock source type configured for a certain system is incorrect, the clock source cannot be used, and the system clock is in free-oscillation mode. This does not affect services in a short period (three months).

8.3 Alarm Handling MeasureStep 1 View the clock source type at the GSM side.

To view the clock source type at the GSM side, run LST BTSCLK.

To modify the clock source type at the GSM side, run SET BTSCLK.

Step 2 View the clock source type at the UMTS side.

To view the clock source type at the UMTS side, run LST CLKMODE.

To modify the clock source type at the UMTS side, run SET CLKMODE.

Step 3 Check whether the clock source configurations of the two GU sides conflict. If yes, modify the configuration of one side to ensure that the configurations of the two GU sides are consistent.



9 Alarm ID: 26277

Alarm name: Inter-System Control Rights Conflict

9.1 Alarm Detection PrincipleThis alarm is generated when the dual-mode base station is not configured with loading control rights or the loading control rights configured for the systems are inconsistent.

9.2 Impact on the SystemIf a configuration conflict of loading control rights occurs, the software versions of the USCU board and RF unit shared by multiple systems may be incorrect. This may cause certain functions of the base station to lose effect and the reliability to reduce.

9.3 Alarm Handling MeasureStep 1 To query the current G/U version, run the following commands:

NodeB LMT: LST SOFTWARE

BSC6900: DSP BTSVER

Step 2 Set loading control rights. You need to set loading control rights only at one side. For details on how to set loading control rights, see the upgrade guide.

NodeB LMT:

Enter SET LOADCTRL in the Command Input field, click (assistance), and set the

required parameters, as shown in Figure 9-1.



Figure 9-1 Setting loading control rights at the UMTS side

Parameter Name

Parameter Setting

Control Flag Select YES(Set Control Flag) or NO(Cancel Control Flag).

Note:If loading control rights belong to the UMTS, select YES(Set Control Flag). If loading control rights belong to the GSM, select NO(Cancel Control Flag).

It is recommended that loading control rights belong to the UMTS.

Effect Immediately Flag

Set this parameter to NO (Effect Later).

Self Software Version

The target version of NodeB is the version queried in Step 1.

Peer Software Version

The target version of the GBTS is the version queried in Step 1.

BSC6900:

Run SET BTSLOADCTRL on the BSC6900.

Figure 9-2 Setting loading control rights at the GSM side

Step 3 Run the following commands to check whether the settings are successful and whether the alarm is cleared.

On the NodeB LMT, run DSP LOADCTRL.

On the BSC6900, run DSP BTSLOADCTRL.



Example:

NodeB LMT:

Figure 9-1 Querying the running version of NodeB

GSM, BSC6900:

Figure 9-2 Querying the running version of the GSM

To set loading control rights on the NodeB LMT, run the following command:

SET LOADCTRL: CTRLFLAG=YES, EFTIMMFLAG=NO, SELFVERSION="

V200R011C01SPC500", PEERVERSION="BTS3000V100R009C00SP72";

SELFVERSION indicates the local version number. When this command is run on the

NodeB LMT, it indicates the 3G version number. This version number is the available version

number in the active version area obtained by running LST SOFTWARE.

PEERVERSION indicates the peer version number. It refers to the GSM version

BTS3000V100R009C00SP72.


Documents

Alarms Inter System