03_ZXG10-BSS Version Upgrade ManualV6.20.10 & Later Versions¬ 2011

  • View
    212

  • Download
    0

Embed Size (px)

DESCRIPTION

BSC version upgradation

Text of 03_ZXG10-BSS Version Upgrade ManualV6.20.10 & Later Versions¬ 2011

Document Title

Product Type Technical Proposal

ZXG10-BSS Version Upgrade Manual

BTSV6.20.10

TABLE OF CONTENTS11BTSV6.20 Version Upgrade Description

11.1BTS Version Upgrade Summarized Procedures

11.2Remarks

11.3Notices

22Upgrade Preparations

22.1BTS Upgrade Preparation Work List

3-13BTSV6.20 (under iBSC) Version Upgrade Steps

3-13.1Version Upgrade Procedures for a Single Site

3-83.2Version Upgrade of Batch Sites

3-123.3Special Version Upgrade Flow

4-124Version Rollback

1 BTSV6.20 Version Upgrade Description1.1 BTS Version Upgrade Summarized Procedures AlarmBefore the upgrading, check whether the preparation has been completed according to ZXG10-BSS Version Upgrading

Always record the BS status before the upgradingStep 1: Choose one site from the physical view to perform BTS single site version upgrade.Step 2: Perform the batch sites upgrade when the single site version is upgraded successfully.Step 3: When the upgrade succeeds, delete the version of the site upgraded on the basis of the physical view, so as to keep the version consistency on the whole network.See notice for the BTS version upgrade in special cases1.2 RemarksThis manual is applicable to BTSV6.20.102E/BTSV6.20.200E and later versions. 1.3 NoticesBTSV6.20.10 and later versions support enhanced CMB and TRXs. Therefore, please pay attention to the following items. During the upgrade, it is necessary to upload and configure CML and CLL versions. Otherwise, the BTS cannot be started. During version rollback, the CML and CLL versions cannot be deleted. Instead, they should be kept there as special versions. Otherwise, the BTS cannot be powered up. And these two versions can be deleted after the rollback succeeds. IBSCV6.10.003L/IOMCRV6.10.102E supports the download of BTSV6.20.10 and later versions. But the CML\CLL versions cannot be queried. OMCRV2.97.020B supports the upload and installation of BTSV6.20.10 and later versions. For versions lower than OMCRV2.97.020B, do not use BTSV6.20.10 and later versions. 2 Upgrade Preparations2.1 BTS Upgrade Preparation Work ListSNItemRecordRemarks

1Current version number8018

2Backup of foreground ZDB filesCompleteIncomplete

3Later version softwareYesNo

4LMT software on ClientYesNo

5Local LMT download cableYesNo

6Definition of BTS SoftwareThrough general software

Independent

Both

7BTS Alarm in alarm managementYesNo

8Channel status in dynamic managementNormalExceptional

9Channel occupation in dynamic managementNormalExceptional

10Site running status in performance statistic reportNormalExceptional

11Record of interrupted/not commissioned siteYesNo

12Test MSYesNo

13Test GPRS /EDGEMSYesNo

3 BTSV6.20 (under iBSC) Version Upgrade Steps 3.1 Version Upgrade Procedures for a Single Site1.Copy the Software Version to the Client Directory.2.Store the Software and send it to the Peripheral Modules. Choose View > Software Version Management > BTS Software Version Management > Create Version File in Batch to OMC, as shown in Figure 3-1.

TypeSoftwareRemarks

8018

8112

8202CMM, CHP, FUC, CLG, FLG, CMl, CLL, EAMFor all types, CLL and CML versions must be uploaded. Otherwise, the BTS will reboot repeatedly.

For Type 8112, the EAM version must be uploaded. Otherwise the BTS will reboot repeatedly.

Figure 3-1 Store BTS Software

3.Synchronize software version to NE. Right-click the version file to be synchronized, and then click Add version file to NE to upload the version file to OMP.

Figure 3-2 Adding Version File to NE

4.Open the Site Specific Software tab and see whether the specific version is created. If it is not created, go to Step 6. If it has been created, deactivate the version first. On the Site Specific Software tab, select all the specific versions, right-click them and choose Cancel activation.

Figure 3-3 Deactivating File Version

5.Delete specific software version from OMC. Figure 3-4 Deleting Specific Version

6.Create specific version fileFigure 3-5 Creating Specific Version File

Configure Site ID.

Figure 3-6 Configuring Site ID

Upload CMM, CLG, FUC, FLG, CHP, CLL, and CML versions respectively with the steps above. After finishing the upload, the created specific versions will be displayed on the Site Specific Software tab. Figure 3-7 Created Specific Version Files

7.Activate the specific software version of the BTS. Then, BTS will start version download automatically.Select CMM, CLG, FUC, FLG, CHP, CLL, and CML and activate the versions.Figure 3-8 Activating Specific Versions

Figure 3-9 Confirm Dialog Box

If the activation succeeds, the BTS starts downloading the version file. We can switch to the signaling tracking software to check whether the installation finishes. Figure 3-10 Result Group

If the operation fails, please check whether link is established between BTS and BSC, and reactivate the version after troubleshooting.

8.Trace the OAM signaling of the site and make sure the software is installed.

9.Observe the Site Running Observe through the alarm management whether the site has alarms. Observe through the dynamic data management whether the channel status is normal and whether the site is occupied normally. Open the Software Version Management tab and check the running version of BTS. Figure 3-11 Checking the Running Version of BTS

Figure 3-12 Query NE Version Information

Figure 3-13 Appointed Board Running Version Query

10.Complete the version upgrade for a Single SiteThe site upgrade is completed when everything returns to normal.

3.2 Version Upgrade of Batch Sites1.Copy the Software Version to the Client Directory.2.Store the Software and send it to the Peripheral ModulesChoose View > Software Version Management > BTS Software Version Management > Create Version File in Batch to OMC.TypeSoftwareRemarks

BTS8000 seriesCMM, CHP, FUC, CLG, FLG, CMl, CLL, EAMFor all types, CLL and CML versions must be uploaded. Otherwise, the BTS will reboot repeatedly.

For Type 8112, the EAM version must be uploaded. Otherwise the BTS will reboot repeatedly.

Figure 3-14 Store BTS Software

3.Synchronize software version to NE.Right-click the version file to be synchronized, and then click Add version file to NE to upload the version file to OMP.

Figure 3-15 Adding Version File to NE

4.Update Site General Software.On the Site General Software tab, select site types to be updated, right-click them and choose Update.

Figure 3-16 Updating General Software

Select the software version to be upgraded in the uploaded software list.

Figure 3-17 Selecting Software Versions

Update other software versions with the same steps. Then, BTS will start version download automatically. CMM, CHP, FUC, CLG, FLG, CMl, CLL5.Trace the OAM signaling of the site and make sure the software is installed. 6.Observe the Site Running Observe through the alarm management whether the site has alarms. Observe through the dynamic data management whether the channel status is normal and whether the site is occupied normally. Open the Software Version Management tab and check the running version of BTS.Figure 3-18 Checking the Running Version of BTS

Figure 3-19 Query NE Version Information

Figure 3-20 Appointed Board Running Version Query

Perform dialup test on the various cells of the key sties. Observe the performance indexes of the whole network within two days after the upgrade, and handle the poorest cell (if any) as soon as possible7.The site upgrade is completed when everything returns to normal.The site upgrade is completed when everything returns to normal.3.3 Special Version Upgrade FlowNULL.4 Version RollbackIf the BTS does not work properly after the version upgrade, and it is necessary to roll back the version, please reinstall the old version according to the upgrade flow.

Note:

During version rollback, the CML and CLL versions cannot be deleted. Instead, they should be kept there as special versions. Otherwise, the BTS cannot be powered up. And these two versions can be deleted after the rollback succeeds.

ZTE CORPORATION

2011

VI 2014ZTE CORPORATION. All rights reserved.ZTE Confidential Proprietary

ZTE Confidential Proprietary 2011 ZTE Corporation. All rights reserved.4(3)