Bts3900-Bts3900a-Bts3900l-Dbs3900 Wcdma v200r011c01spc752 Upgrade Guide (Lmt-based)

HUAWEI BTS3900-BTS3900A-BTS3900L-DBS3900 WCDMA

V200R011C01SPC752

Upgrade Guide

Issue 01

Date 2012-1-29

HUAWEI TECHNOLOGIES CO., LTD.

Copyright © Huawei Technologies Co., Ltd. 2011. All rights reserved.

No part of this document may be reproduced or transmitted in any form or by any means without prior written consent of Huawei Technologies Co., Ltd.

Trademarks and Permissions

and other Huawei trademarks are trademarks of Huawei Technologies Co., Ltd.

All other trademarks and trade names mentioned in this document are the property of their respective holders.

Notice

The purchased products, services and features are stipulated by the contract made between Huawei and the customer. All or part of the products, services and features described in this document may not be within the purchase scope or the usage scope. Unless otherwise specified in the contract, all statements, information, and recommendations in this document are provided "AS IS" without warranties, guarantees or representations of any kind, either express or implied.

The information in this document is subject to change without notice. Every effort has been made in the preparation of this document to ensure accuracy of the contents, but all statements, information, and recommendations in this document do not constitute the warranty of any kind, express or implied.

Huawei Technologies Co., Ltd.

Address: Huawei Industrial Base

Bantian, Longgang

Shenzhen 518129

People's Republic of China

Website: http://www.huawei.com

Email: [email protected]

Issue 01 (2011-11-15)Huawei Proprietary and Confidential

Copyright © Huawei Technologies Co., Ltd.iii

mailto:[email protected]

http://www.huawei.com/

BTS3900-BTS3900A-BTS3900L-DBS3900 WCDMA

V200R011C01SPC752 Upgrade GuideAbout This Document

About This Document

SummaryThis document provides version upgrade instructions for the BTS3900-BTS3900A-BTS3900L-DBS3900 WCDMA V200R011C01SPC752. This document consists of the following chapters:

Chapter Details

1 Reading Before Upgrade Describes the version requirements for the upgrade.

2 Upgrade Procedure Describes the upgrade procedure.

3 Preparations for Upgrade Describes the preparations before upgrade.

4 Upgrade Operations Describes how to upgrade the NodeB.

5 Verifying the Upgrade Describes the verification operations after upgrade.

6 Version Rollback Describes how to roll the version back to the one before upgrade.

7 FAQs Provides answers to the frequently asked questions.

8 Appendix Provides the dial test and verification sheets used after the upgrade.


Copyright © Huawei Technologies Co., Ltd.v

BTS3900-BTS3900A-BTS3900L-DBS3900 WCDMA V200R011C01SPC752 Upgrade Guide Contents

Contents

1 Reading Before Upgrade.............................................................................................1-11.1 Application Scope......................................................................................................................... 1-1

1.2 Version Requirements for Upgrade..............................................................................................1-1

1.3 Impact on the Existing Systems During Upgrade.........................................................................1-1

1.4 Notes and Cautions...................................................................................................................... 1-2

1.4.1 Version Requirements for Other NEs...................................................................................1-2

1.4.2 Key Precautions for Upgrading Specific Versions................................................................1-2

1.4.3 Notes................................................................................................................................... 1-3

1.4.4 Download Duration of Involved Software.............................................................................1-3

2 Upgrade Procedure......................................................................................................2-1

3 Preparations for Upgrade............................................................................................3-23.1 Preparations Before Upgrade.......................................................................................................3-2

3.2 Having Resources for Verification and Spare Parts Ready..........................................................3-3

3.3 Obtaining Files for Upgrade.........................................................................................................3-3

3.4 Checking the Network..................................................................................................................3-3

3.5 Checking the Operating Status of the Equipment Before the Upgrade........................................3-3

3.6 Upgrading the LMT....................................................................................................................... 3-4

3.7 Upgrading a CME Version or a CME Component Package.........................................................3-4

3.8 Confirming the Configuration Baseline.........................................................................................3-5

4 Upgrade Operations.....................................................................................................4-14.1 Setting the Load Control Rights...................................................................................................4-1

4.2 Upgrading the NodeB Software....................................................................................................4-2

4.3 (Optional) Upgrading the NodeB Monitoring Boards....................................................................4-5

5 Verifying the Upgrade..................................................................................................5-15.1 Checking current alarms..............................................................................................................5-1

5.2 Checking the cell status...............................................................................................................5-1

5.3 Querying the active NodeB version..............................................................................................5-1

5.4 Performing a dial test...................................................................................................................5-1

5.5 Determining whether the KPIs are normal....................................................................................5-1

6 Version Rollback..........................................................................................................6-1


Copyright © Huawei Technologies Co., Ltd.vii

ContentsBTS3900-BTS3900A-BTS3900L-DBS3900 WCDMA

V200R011C01SPC752 Upgrade Guide

7 FAQs..............................................................................................................................7-17.1 FAQ Table.................................................................................................................................... 7-1

7.2 FAQ1............................................................................................................................................ 7-1

7.3 FAQ2............................................................................................................................................ 7-3

7.4 FAQ3............................................................................................................................................ 7-4

7.5 FAQ4............................................................................................................................................ 7-5

7.6 FAQ5............................................................................................................................................ 7-7

8 Appendix.......................................................................................................................8-18.1 Dial Test After NodeB Upgrade.....................................................................................................8-1

8.2 Checking the Device Panel Status...............................................................................................8-2

viiiHuawei Proprietary and Confidential

Copyright © Huawei Technologies Co., Ltd.Issue 01 (2012-01-29)

BTS3900-BTS3900A-BTS3900L-DBS3900 WCDMA V200R011C01SPC752 Upgrade Guide 1 Reading Before Upgrade

1 1 Reading Before Upgrade

1.1 Application ScopeThe NodeB upgrade can be performed on the M2000 or LMT.

On the M2000, multiple NodeBs can be upgraded at the same time. For detailed operations, see the BTS3900-BTS3900A-BTS3900L-DBS3900 WCDMA V200R011C01SPC752 Upgrade Guide (M2000-Based).

On the LMT, only one NodeB can be upgraded at a time. The detailed operations are described in this document.

1.2 Version Requirements for UpgradeAll of the history software versions can be upgraded to BTS3900-BTS3900A-BTS3900L-DBS3900 WCDMA V200R011C01SPC752 directly.

There is no need to upgrade the BootROM version.

1.3 Impact on the Existing Systems During Upgrade

Impact on Services

During the activation of the NodeB software, the CPU usage increases. When the activation is completed, the CPU usage is automatically recovered.

Therefore, you are advised to activate the software when the traffic is low.

After the NodeB software is activated, the NodeB is automatically reset and services are disrupted. Table 1-1 lists the disruption duration of services during upgrade involved software.


Copyright © Huawei Technologies Co., Ltd.1

1 Reading Before UpgradeBTS3900-BTS3900A-BTS3900L-DBS3900 WCDMA


Table 1-1 Disruption duration of services during upgrade involved software

Software Services Disrupted

Service Disruption Duration (Min)

Maintenance Disrupted

Maintenance Disruption Duration (Min)

NodeB software Y 2~5 Y 10

Impact on Network Communication

None

1.4 Notes and Cautions

1.4.1 Version Requirements for Other NEsCheck "Related Product Version" and “Software Versions” in the BTS3900-BTS3900A-BTS3900L-DBS3900 WCDMA V200R011C01SPC752 Release Notes released with the version to determine whether the RNC, CME, LMT, and M2000 should also be upgraded.

1.4.2 Key Precautions for Upgrading Specific Versions

Table 1-1 The PMU maintenance link is broken

Upgrade Risk Related to Functions

Description

Problem Description Scenario: The NodeB is configured with the PMU whose software version is 112.

Trigger condition: The NodeB is reset.

Symptom: Maintenance of the PMU cannot be performed, or an alarm is reported indicating that the PMU maintenance link is broken.

Impact The PMU maintenance link is broken. The fault is rectified only after the PMU is re-installed.

Workaround Before upgrading the NodeB, upgrade the PMU software to the 113 version or later.

Probability None

2Huawei Proprietary and Confidential



Table 1-2 License deliver failure


Description

Problem Description When the NodeB license is used to change the state of the dynamic CE switch, the license may fail to be delivered.

Impact When changing the state of the dynamic CE switch of the NodeB, the site should carry no UE, that is, all the cells should be disabled. Otherwise, the license may fail to be delivered.

Workaround Deactivate all the cells, and then deliver the license to change the state of the dynamic CE switch of the NodeB.

Probability None

Table 1-3 The RRU3804/RRU3801E/RRU3806/WRFU fails to be activated


Description

Problem Description When the NodeB is upgraded from V200R011 to V200R011C01 or a later version, there is a probability that the RRU3804/RRU3801E/RRU3806/WRFU fails to be activated.

Impact The RRU3804/RRU3801E/RRU3806/WRFU fails to be activated.

Workaround Reactivate the RRU3804/RRU3801E/RRU3806/WRFU or upgrade the NoedB again.

Probability 10%

1.4.3 Notes The upgrade procedure must be in strict compliance with the upgrade guide. No

reverse procedure is allowed.

During the upgrade, wait for the command response and check whether the command is run successfully before you run the next one. If the command fails, follow the instructions provided in this guide.

Do not perform the following operations on the WMPT (WCDMA Main Processing&Transmission unit) when upgrading the software:

− Power off the WMPT

− Manually reset the WMPT

− Pull out or insert the WMPT

If there is a standby WMPT, check it before the upgrade in terms of the following:





− The standby WMPT status is Available

If the upgrade fails or the network performance seriously deteriorates in the dialing test after the upgrade, a version rollback is recommended.The rollback depends on the real situations of the network and the requirements of the customer. For details about how to perform the rollback, see chapter 6 “Version Rollback.”

1.4.4 Download Duration of Involved SoftwareTable 1-1 lists the duration of downloading NodeB-related software on the M2000 and number of NodeBs that can be simultaneously upgraded in terms of different OMCH bandwidths.

Table 1-1 Download duration and number of NodeBs simultaneously upgraded through the M2000

NodeB OMCH Bandwidth

Download NodeB Software Time

Remarks

10 mbit/s 15' Local

128 kbit/s, VBR 69'43" Remote

512 kbit/s, VBR 34'49" Remote




2 2 Upgrade Procedure

During a NodeB upgrade, follow the upgrade procedure, as shown in Figure 2-1.

Figure 2-1 Upgrade flow chart





3 3 Preparations for Upgrade

3.1 Preparations Before Upgrade

Table 3-1 Checklist for preparations before upgrade

Preparation Item Remarks

Location of the equipment to be upgraded -

Upgrade time and duration allowed by the operator

-

Upgrade requirements of the operator -

Type and model of the NodeB to be upgraded

-

Number of NodeBs to be upgraded -

Target version after upgrade -

Active version of the M2000 server on the operator side

-

Active version of the RNC on the operator side

Check how many patches have been installed so far.

Active version of the CME on the operator side

Check the active CME version and the CME component package.

Active software version of the NodeB on the operator side

-

Data configuration file of the operator equipment

Back up the data configuration file.

Whether the M2000 server should be upgraded for synchronization

-

Whether the RNC should be upgraded for synchronization

If the RNC needs to be upgraded, contact the engineers responsible for the RNC to prepare for upgrade.

Whether the CME should be upgraded for synchronization

To upgrade a CME version or a CME component package, see the CME-related upgrade guide.

Other data that should be recorded -




3.2 Having Resources for Verification and Spare Parts Ready

The resources for verification required after the upgrade are as follows:

Mobile phones for dial tests

SIM cards

Test vehicles

Have spare parts ready according to the actual requirements.

3.3 Obtaining Files for UpgradeTo obtain the files for upgrade, perform the following steps:

Step 1 Obtain the software packages.

Obtain the files corresponding to the version from http://support.huawei.com. The files are the installation files of the LMT and NodeB software package.

Step 2 Decompress the version files to the destination folders.

It is assumed that the version files are decompressed to the D:\NodeBVer path. We will take it as an example in the follow upgrade steps.

----End

3.4 Checking the NetworkSave the latest KPI report before upgrading the version. For the KPIs to be checked, see section 5.5 “Determining whether the KPIs are normal“.

Perform dial tests before the upgrade. For the test items, refer to section 8.1 “Dial Test After NodeB Upgrade“. Record the related traced messages.

3.5 Checking the Operating Status of the Equipment Before the Upgrade

Table 3-1 lists the items for checking the operating status of the equipment on the LMT before upgrading the version.



http://support.huawei.com/



Table 3-1 Checklist for the operating status of the equipment before the upgrade on the LMT

Item Result Conclusion

Checking active alarm data:

Check all alarms of the NodeBs to be upgraded on the LMT. Clear the alarms according to the alarm online help.

Checking cell status:

Run the DSP LOCELL command on the LMT, and then check the status of all the cells controlled by the NodeBs to be upgraded.

Check whether all the local and logical cells configured are available. If not, see the alarm reference to rectify the fault.

Checking data consistency:

Run the CHK DATA command on the LMT, and then check the consistency between the NodeB flash data and the running data.

If the two are inconsistent, reset the NodeB.

3.6 Upgrading the LMTConfirm the version of the LMT provided by the BTS3900-BTS3900A-BTS3900L-DBS3900 WCDMA V200R011C01SPC752 Release Notes.

To upgrade the NodeB LMT, perform the following steps:

Step 1 Log in to the operating system as an administrator.

Step 2 Double-click setup.exe in the LMT installing folder to start installing the LMT.

Step 3 Install the LMT by using the default settings.

The default installation path is D:\HW LMT.

----End

3.7 Upgrading a CME Version or a CME Component Package

Confirm the version of the CME or a CME Component Package provided by the BTS3900-BTS3900A-BTS3900L-DBS3900 WCDMA V200R011C01SPC752 Release Notes.

For details about upgrading a CME version, see the CME V200R009C00SPCXXX Upgrade Guide.




For details about upgrading a CME component package, see the CME BTS3900-BTS3900A-BTS3900L-DBS3900 WCDMA V200R011C01SPCXXX Component Upgrade Guide.

3.8 Confirming the Configuration BaselineRun the CFM CB command to back up the active version, including software version and data configuration file, to create a new Configuration Baseline (CB). For version rollback after the upgrade, you need to confirm the CB, for details about rollback operation steps see 6 "Version Rollback. "

There are two modes to confirm the CB: FORCED and UNFORCED. If the FORCED mode is selected, the system recreates a CB even if the active CB is confirmed. If the UNFORCED mode is selected, reconfirming the CB fails if the active CB is confirmed.

It is recommended that Confirm Mode be set to UNFORCED, which is the default value of the parameter. Because the name of the CB cannot be duplicated, the CB might be named with the corresponding current running version and date, such as V200R011C01SPC100_20091023.

After the confirmation of the CB, do not change the configuration. Otherwise, the CB should be reconfirmed.




4 4 Upgrade Operations

Table 4-1 describes the procedure for upgrading the NodeB.

Table 4-1 Procedure for upgrading the NodeB

Step

Description Reference Duration (for Reference Only)

1 Set the load control rights 4.1 Setting the Load Control Rights

1 minute

2 Upgrade the NodeB software.

4.2 Upgrading the NodeB Software

30 minutes

3 Upgrade the NodeB monitoring boards.

4.3 (Optional) Upgrading the NodeB

5 minutes

NOTE

This section takes the DBS3900 WCDMA as an example.

The CPU overload alarm may be generated during the following operations:

Downloading the NodeB software package

Activating the NodeB software

Activating the WMPT board software

The alarm is automatically cleared after the upgrade.





4.1 Setting the Load Control Rights

Step 1 Enter SET LOADCTRL in the Command Input box, and then click Assist .

Figure 4-1 Setting the load control rights

Parameter Setting

Control Flag Select YES(Set Control Flag).

Effect Immediately Flag

Select NO(Effect Later).

Self Software Version

Set it to V200R011C01SPC752.

Peer Software Version

Enter the current version number of the GBTS.

Step 2 Click and view the MML command output.

----End

4.2 Upgrading the NodeB SoftwareTo upgrade the NodeB software, perform the following steps:

Step 1 On the NodeB LMT, click the Maintenance tab in the navigation pane.

Step 2 Double-click Software Management > Software Update.

The Software Update dialog box is displayed, as shown in Figure 4-1.




Figure 4-1 Starting to upgrade the NodeB software

Step 3 Select Upgrade NodeB Software, and then click Next.

The Update NodeB Software dialog box is displayed.

Step 4 Select the Download NodeB Software Package, Activate NodeB Software, and Download by Configuration check boxes, and enter the NodeB software package path (for example, D:\NodeBVer\BTS3900-BTS3900A-BTS3900L-DBS3900V200R011C01SPC752) in the Directory Name box, as shown in Figure 4-1.

For the reason why the Download by Configuration check box is selected, see section 7.5 "FAQ4."





Figure 4-1 Upgrading the NodeB software

Step 5 Click Next. A dialog box is displayed, shown as Figure 4-1.

Figure 4-1 Confirmation dialog box

Step 6 Click Yes.

A dialog box is displayed, indicating the status and progress of the NodeB software upgrade. After the NodeB software activation is complete, the boards whose software is activated and those whose software fails to be activated are listed.




Step 7 If there are boards whose software fails to be activated, perform troubleshooting by referring to section 7.2 "FAQ1."

----End

4.3 (Optional) Upgrading the NodeB Monitoring Boards

Table 4-1 Cabinet, subrack, and slot information about the monitoring boards

Board Name

Cabinet No.

Subrack No.

Slot No. Version After Upgrade

PMU 0-30 7 0 Typical PMU: 115

Solar PMU: 102

TCU 0-30 8 0 1.03

FMU 0-30 11-12 0 103

EMU 0-30 40-59 0 2.10

Step 1 Run the DSP BRD command to query the types of all the configured boards. If you configure any board that is listed in Table 4-1, that board may need to be upgraded by performing Step 2.

Step 2 Run the DSP BRDVER command to query the board version. If the board version is consistent with that listed in Table 4-1, you do not need to upgrade the board. If the board version is inconsistent, you need to upgrade the board by performing Step 3.

Step 3 Run the ACT SOFTWARE command to upgrade the monitoring board. Select the ONEBRDSW (Software of an individual board) in the Software Type. Figure 4-1 shows an example of upgrading a PMU in slot 0 of subrack 7 in cabinet 0.

Figure 4-1 Upgrading a PMU

Step 4 After the upgrade, run the DSP BRDVER command to query the board version of the upgraded board. If the version is consistent with that listed in Table 4-1, the upgrade is successful. If the version is inconsistent, repeat Step 3.




5 5 Verifying the Upgrade

After the upgrade, follow the description to verify the upgrade.

5.1 Checking current alarmsCheck all the current alarms of the upgraded NodeB, and clear the alarms according to the alarm online help.

5.2 Checking the cell statusRun the DSP LOCELL command to check the status of all the cells controlled by the upgraded NodeB.

Check whether all the local and logical cells configured are available.

If yes, the upgrade is successful.

If no, see the alarm online help for troubleshooting.

5.3 Querying the active NodeB versionRun the LST VER command. Then, check whether the active NodeB software version is V200R011C01SPC752.

There is no need to confirm the BootROM version for the BootROM does not need to be upgraded.

5.4 Performing a dial testConduct the test by following the instructions provided in section 8.1 "Dial Test After NodeB Upgrade." Ensure that the system services are not affected after the NodeB upgrade.





5.5 Determining whether the KPIs are normalStep 1 Ensure that no major alarm remains relating to the RNC or the NodeB after the

upgrade.

Step 2 Ensure that all services are successfully admitted by the network and perform the related drive tests to check whether the following requirements are met:

The services are admitted and function properly in terms of AMR speech service, R99 PS, VP, HSDPA, and HSUPA.

The mobility is normal in terms of AMR, VP, PS R99, HSDPA, HSUPA, inter-RAT handover, and inter-frequency handover.

The throughput is normal in terms of R99 PS 384K, HSDPA, and HSUPA.

Step 3 Ensure that the traffic statistics in the first peak traffic period (busiest hours of the day) after the upgrade does not show substantial fluctuation when compared with the traffic statistics one day before the upgrade. The KPIs in the whole day should meet the following requirements:

The traffic difference does not exceed 5% in terms of CS Erlang, PS 64K/128K/384K, HSDPA, HSUPA, RRC connection setup times, and RAB setup times (in the cases of CS, PS, and HSPA).

The difference among the service access success rates does not exceed 0.2% in terms of RRC, RAB, HSDPA, and HSUPA.

The difference among the handover success rates does not exceed 0.2% in terms of intra-frequency handover, inter-frequency handover, and inter-RAT handover.

The difference of the service drop rate does not exceed 0.2% in terms of AMR, PS, HSDPA, and HSUPA.

The difference among the paging success rates does not exceed 1%.

The difference among the SPU load during busy hours does not exceed 5%.

Step 4 (Optional) To ensure that no major problem occurs after the upgrade, collect the KPI statistics on an hourly basis for the first 24 hours after the upgrade. The KPIs in the same period of the present day and the previous day should meet the following requirements:

The traffic difference does not exceed 20% in terms of CS Erlang, PS 64K/128K/384K, HSDPA, HSUPA, RRC connection setup times, and RAB setup times (in the cases of CS, PS, and HSPA).

The difference among the service access success rates does not exceed 1% in terms of RRC, RAB, HSDPA, and HSUPA.

The difference among the handover success rates does not exceed 0.5% in terms of intra-frequency handover, inter-frequency handover, and inter-RAT handover.

The difference among the drop rates does not exceed 1% in terms of AMR, PS, HSDPA, and HSUPA.

The difference among the paging success rates does not exceed 5%.

The difference among the SPU load during does not exceed 10%.




If the NodeB does not pass the verification and the problem cannot be solved, you can activate the CB by running ACT CB to roll back the version. For details, see chapter 6 "Version Rollback."

If the NodeB passes the verification, you can run CFM CB as required to confirm the current CB.




6 6 Version Rollback

If the upgrade fails or the network performance seriously deteriorates in the dialing test after the upgrade, the version requires a rollback. The rollback, however, depends on the actual situations of the network and the customer requirements.

Run the DSP CB command to query the status of the target CB. The target CB is the one that you have confirmed before the upgrade, such as V200R011C01SPC100_20091023, which is described in section 3.8 "Confirming the Configuration Baseline."

If the CB status is valid, run the ACT CB command to roll back the software version.

If the CB status is invalid, download the software version corresponding to the target CB and then run the ACT CB command to roll back the software version.

When rolling back the version by running ACT CB, if the alarm with ID 26253 (Board Software Auto-Supply Failure) is generated, see section 7.6 "FAQ5."




7 7 FAQs

7.1 FAQ Table

Table 7-1 FAQ table

No. Question

FAQ1 How to handle the fault in activating the NodeB software when upgrading the NodeB on the LMT?

FAQ2 How to clear the fault in an abnormal IPoA channel at the far end?

FAQ3 How to handle the fault in access of a UE to a NodeB after the NodeB is upgraded?

FAQ4 Why can the download rate be higher during the upgrade process if the Download by Configuration check box is selected?

FAQ5 How to handle the following alarms generated when rolling back the version by running ACT CB: the alarm with ID 26253 (Board Software Auto-Supply Failure)?

7.2 FAQ1

Question

How to handle the fault in activating the NodeB software when upgrading the NodeB on the LMT?

Answer

Click View Details to list the boards whose software fails to be activated, according to the result of the NodeB software activation. Figure 7-1 shows an example of the result.





Figure 7-1 Software upgrade result

You may choose to activate the software of only one board or all boards of the same type, depending on the result of the NodeB software activation. The latter method is applicable to the situation in which the software fails to be activated for a number of boards of the same type.

To activate the board software, perform the following steps:

Step 1 On the LMT, click the Maintenance tab in the navigation pane.

Step 2 Double-click Software Management > Software Update.

The Software Update dialog box is displayed.

Step 3 Select Activate Board, and then click Next.

The Software Update – Activate Board dialog box is displayed.

Step 4 Click Single board on the right of Activate Software, and then enter the related subrack number and the slot number.

If there are a number of boards whose software fails to be activated and the boards are of the same type, click A type of boards on the right of Activate Software, and then select the type of boards in the Board type drop-down list.

Step 5 Click Next, a dialog box is displayed, shown as Figure 7-1.




Figure 7-1 Confirmation dialog box

Step 6 Click Yes to activate the software of a single board or a type of boards.

Step 7 Repeat Step 1 through Step 6 to activate the software of other types of boards.

----End

7.3 FAQ2

Question

How to clear the fault in an abnormal IPoA channel at the far end?

Answer

If the NodeB OM IP address fails to be pinged, see Table 7-1 for specific solutions.

Table 7-1 Solutions to the failure to ping the NodeB OM IP address

Symptom Solution

The related alarms indicate that the E1 link between the RNC and the NodeB or the IMA/UNI/CP port incurs faults.

Rectify the faults in the E1 transmission until all the related alarms are cleared.

The result of running DSP E1T1 command at the RNC indicates that the IMA groups at the RNC and NodeB fail to interwork because there is an E1 link working in loopback mode in the IMA group of the NodeB configured at the RNC.

Reset the IMA group at the RNC. If the fault in the IPoA channel persists, reset the IMA group after removing the E1 link that works in loopback mode at the RNC.

The result of the on-site check indicates that the RUN/ALM/ACT LEDs on the WMPT are not in the expected states.

Contact Huawei technical support engineers or NodeB troubleshooting specialists immediately. Collect the related data under the guidance of the specialist. After getting the approval of the specialist, reset, remove, install, or replace the WMPT until all the related faults are rectified.





Symptom Solution

Login to the NodeB through the Ethernet port from the LMT failed. The IP address cannot be pinged.

Contact Huawei technical support engineers or NodeB troubleshooting specialists immediately. Collect the related data under the guidance of the specialist. After getting the approval of the specialist, reset, remove, install, or replace the WMPT until all the related faults are rectified.

7.4 FAQ3

Question

How to handle the fault in access of a UE to a NodeB after the NodeB is upgraded?

Answer

Contact Huawei technical support engineers or NodeB troubleshooting specialists immediately. Collect the related data under the guidance of the specialist. Rectify the fault at the far end until all the related faults are cleared.

For the troubleshooting steps and the collected data, see Table 7-1.

Table 7-1 Troubleshooting steps and collected data

Action Result Data Collected

Check the NodeB active alarms on the NodeB LMT, and then clear the alarms if any.

NodeB alarm data

Check the active alarms associated with the NodeB on the RNC LMT, and then clear the alarms if any.

NodeB alarm data

Upload the main board logs by running the following command:

ULD FILE: DSTF="c:\mainbrdLog.txt",

FLAG=MAINBRDLOG, IP="10.161.41.71", USR="admin",

PWD="admin", CF=UNCOMPRESSED;

Uploaded main board logs

Check the availability of the local cells at the NodeB by running the DSP LOCELL command.

Check the availability of the logical cells at the RNC by running the DSP CELL command.

MML command messages saved

Check the NodeB output power. MML command messages saved




Action Result Data Collected

Check the locking of frequency and scramble of the UE under test.

Check the accessibility of another UE or another SIM card to the NodeB.

If possible, check whether the UE under test sends an RRC CONNET REQ message.

Logs recorded

Check the RTWP of the NodeB. The RTWP should be a value at –106 dBm±3 dB.

RTWP measurement files recorded

Query the Iub connection data carried over all AAL2 paths of the NodeB by running the DSP AAL2CHN command at the RNC.

MML command messages saved

Trace and save all messages of the UE under test through single UE tracing at the RNC.

Single UE tracing

Trace and save all messages of the UE under test over the Uu, Iu, and Iub interfaces at the RNC.

Messages traced over the Iu, Iub and Uu interfaces

Trace messages over the Iub interface of the NodeB.

Messages traced over NodeB Iub interface

Export RNC CDR log files before and after the NodeB upgrade.

CDR log files before and after NodeB upgrade

7.5 FAQ4

Question

Why can the download rate be higher during the upgrade process if the Download by Configuration check box is selected?

Answer

The NodeB software package contains the software for all the boards supported by the NodeB. Each board type corresponds to one board software package.

In regular mode, the entire NodeB software package is downloaded to the NodeB. In practice, however, only some types of board are configured on the NodeB, and not all board software packages are required.

Download by configuration refers to the action to download the required board software from the file server during the upgrade according to the types of board currently configured on the NodeB. This can effectively reduce the total volume of





data to be downloaded, minimize the duration, and ensure that the software package occupies the least storage space on the hard disk.

Generally, download by configuration has the following benefits:

Only the required board software packages are downloaded according to the current NodeB configuration.

The valuable maintenance link bandwidth is utilized effectively, the duration of downloading the software is minimized, and the upgrade efficiency is improved.

The storage space on the hard disk of the NodeB is utilized effectively, and waste of storage space for software not to be used is avoided.

This mode features a higher download rate when the NodeB is configured with boards of fewer types.

Table 7-1 Comparison between regular download and download by configuration

Typical Configuration

Board Duration Storage Space Band-width

Type Qty. Regular By Configuration

Regular By Configuration

DBS3900 3 x 1 configuration

WMPT 1 60 min 50 min 21 MB 18 MB 128 kbit/s

MRRU 3

NOTE

The NodeB uses one active directory and one standby directory to store two pieces of software. For the DBS3900, the saved space on the hard disk in download by configuration mode is 3 MB x 2= 6 MB.

The methods of adding a type of board to the NodeB vary with the download modes, as described in Table 7-2.

Table 7-2 Methods of adding new types of board to the NodeB

Mode Description How to Add a Type of Board

Exception Remarks

Regular download

Download the entire NodeB software package to the NodeB.

The system obtains the board software package directly from the NodeB and automatically activates it.

None. None.

Download by configuration

Download only the required board software packages for the boards currently configured on the NodeB.

You should obtain the software package from the specific file server. Then, the system automatically activates it to upgrade the board.

An alarm is reported if the file server cannot be connected to or no corresponding version is found on the server.

Alarm ID:

ID 26253 (Board Software Auto-Supply Failure)




NOTE

The NodeB supports download by configuration for the flash software on the boards but does not support download by configuration for the BootROM. The NodeB BootROM package must be downloaded in regular mode.

If the alarm with the ID 26253 (Board Software Auto-Supply Failure) is generated, run the SPL SOFTWARE command to supplement the software.

7.6 FAQ5

Question

How to handle the following alarms generated when rolling back the version by running ACT CB: the alarm with ID 26253 (Board Software Auto-Supply Failure)?

Answer

During the upgrade, the version to be rolled back is downloaded according to the configuration. In this case, if some boards are not configured, the corresponding software packages are not downloaded to the NE. When these boards are configured and the NE is being upgraded to another version, the corresponding software packages are not available in the standby directory. If the version is rolled back to the version before upgrade by ACT CB, the alarm with ID 26253 (Board Software Auto-Supply Failure) is generated.

To solve the problem using the M2000, upload the corresponding software packages again to the M2000 server, and then run SPL SOFTWARE to manually supplement the board software. The NodeB automatically activates the board software.

To solve the problem using the LMT, run SPL SOFTWARE to manually supplement the board software. The NodeB automatically activates the board software. If the command cannot be run successfully and the software packages are removed from the local hard disk or their paths are changed, you should download the software packages again and activate them.




8 8 Appendix

8.1 Dial Test After NodeB Upgrade

Table 8-1 Dial test after NodeB upgrade

Record of the NodeB Dial Test

NodeB name

Test time

Test result □Pass □Not Pass

Cell name

Cell ID

Cell scramble

Dial Test Result Remarks

Speech: fixed-line phone to mobile (3G)

□Pass □Not Pass □N/A

Speech: mobile (3G) to fixed-line phone


Speech: mobile (3G) to mobile (2G)










VP: mobile (3G) to mobile (3G)


PS: PDP activation □Pass □Not Pass □N/A

Speech conversation quality

□Good □Bad □N/A

VP conversation quality


PS communications quality


Call drop □Pass □Not Pass □N/A

Soft handover □Pass □Not Pass □N/A

RSCP (should > –70 dBm)

Ec/I0 (should > –10 dB)

Remarks

Tested by (signature)

8.2 Checking the Device Panel Status

Table 8-1 Checklist for the device panel status

No. Item Check Point Result

1 Whether the device panel can be properly started

Y

2 Whether there is any board in red (faulty) N

3 Whether there is any board in yellow (reporting an alarm)

N

4 Whether there is any board in blue (blocked) N




No. Item Check Point Result

5 Whether there is any board in dark gray (in position but not configured)

N

6 Whether there is board in light gray (configured but not in position)

N

7 Whether the board configured after upgrade is consistent with that before upgrade

Y

8 Whether the RRUs are properly displayed Y

9 Whether the RHUBs are properly displayed Y

10 Whether the Pico RRUs are properly displayed Y



Documents

Bts3900-Bts3900a-Bts3900l-Dbs3900 Wcdma v200r011c01spc752 Upgrade Guide (Lmt-based)