RNC Commissioning Guide 01-04 Commissioning the RNC Equipment

4 Commissioning the RNC Equipment

About This Chapter

This task describes how to commission the RNC equipment, including commissioning the BAM,commissioning the RNC LMT, loading the RNC software and data files, verifying the RNClicense configuration, and verifying the switchover between RNC active and standby boards.

4.1 Commissioning BAMsThis task describes how to commission the BAMs, including verifying the BAM settings beforecommissioning and installing the BAM software on site.

4.2 Commissioning the RNC LMTThis task describes how to commission the RNC LMT, including checking the computerconfiguration of the RNC LMT, installing the RNC LMT application, connecting the RNC LMTto the BAM, and starting the RNC Local Maintenance Terminal.

4.3 Loading RNC Software and Data FilesThis task describes how to load the host software and data during RNC commissioning.

4.4 Activating and Verifying the LicenseThis task describes how to activate the RNC license and to verify whether the licenseconfiguration information is valid.

4.5 Verifying Switchover Between Active and Standby BoardsThis task describes how to verify switchover between active and standby boards.

RNCCommissioning Guide 4 Commissioning the RNC Equipment

Issue 02 (2007-08-15) Huawei Technologies Proprietary 4-1

4.1 Commissioning BAMsThis task describes how to commission the BAMs, including verifying the BAM settings beforecommissioning and installing the BAM software on site.

PrerequisiteThe setup disk of BAM application that is consistent with the local office version is obtained.

Procedure

Step 1 4.1.1 Obtain the Installation Information of the BAM SoftwareBefore commissioning the BAM, obtain the Data Sheet of BAM Software Installation withinformation already filled in.

Step 2 4.1.2 Remotely Logging In to the BAMBefore commissioning the BAM, remotely log in to the BAM on an operating terminal that canrun the mstsc.exe program.

Step 3 4.1.3 Checking BAM SoftwareBefore commissioning the BAM, check the operating system and software setting of the BAMto ensure that the BAM application is successfully installed and operational.

Step 4 4.1.4 Checklist for BAM Software Settings Performed Before DeliveryBefore installing the BAM application, check the software installation and setting beforedelivery of the BAM.

Step 5 4.1.5 Installing the BAM Application in the Active WorkspaceInstall the BAM application in the active workspace of the BAM. Install the BAM applicationon all the BAMs of the RNC.

Step 6 4.1.6 Checking the Operation of the BAM ApplicationAfter installing the BAM application, check the operation of the BAM application including theoperation of the BAMService and SecurityManager.

Step 7 4.1.7 Installation Directory of the BAM ApplicationAfter installing the BAM software, check the data stored in the BAM installation directory. Thisdata includes the data related to the BAM application components, data related to the RNC hostsoftware, and various data used or generated by the RNC.

----End

4.1.1 Obtain the Installation Information of the BAM SoftwareThis task describes how to obtain the installation information of the BAM software before theBAM application installation. The information contains the information of the operating system,database software, and IP address settings of Ethernet adapter teams.

ProcedureBefore installing the BAM application, get the following information by referring to Data Sheetof BAM Software Installation:

4 Commissioning the RNC EquipmentRNC

Commissioning Guide

4-2 Huawei Technologies Proprietary Issue 02 (2007-08-15)

l Administrator password of Windows Server 2003

l Password for the user sa to log in to SQL Server 2000

l Fixed IP addresses of the internal and external networks

----End

4.1.2 Remotely Logging In to the BAMThis task describes how to remotely log in to the BAM by running mstsc.exe on a computer. Byperforming this task, you can remotely perform some OM operations on the BAM.

Prerequisitel You are logged in to the Windows Server 2003 operating system on the BAM.

l The computer for remote login to the BAM is installed with Windows XP or a later version.

l The computer for remote login to the BAM works and connects to the BAM externalnetwork properly.

l The fixed IP address or the virtual IP address of the external network is obtained. For detailsabout the external IP address of the BAM, refer to Data Sheet of BAM SoftwareInstallation.

l When the computer used for remote login to the BAM is connected to the BAM through aLAN, the IP address of this computer must be in the same network segment as one of theBAM external IP addresses.

ContextTo prevent multiple users from logging in to the BAM at the same time, run mstsc.exe with theconsole parameter.

Procedure

Step 1 On the computer for remote login to the BAM, choose Start > Run. The Run dialog box isdisplayed.

Step 2 Enter mstsc /console and click OK. The Remote Desktop Connection dialog box is displayed,as shown in Figure 4-1.

CAUTIONWhen entering the mstsc /console, leave a space between mstsc and /console.



Figure 4-1 Remote Desktop Connection dialog box

Step 3 Enter the external IP address of the BAM for remote login, and then click Connect.

NOTE

l If you remotely log in to the BAM before installing the BAM application, enter the fixed IP addressof the external network.

l If you remotely log in to the BAM after installing the BAM application, enter the virtual IP address ofthe external network.

Step 4 Enter the name and password of an administrator-level user of the BAM, and then click OK.You are remotely logged in to the BAM.

CAUTIONBy running mstsc.exe with the console parameter, you can connect the BAM to only onecomputer. In other words, another computer connected to the BAM in this way will bedisconnected from the BAM after you click OK on the local computer.

----End

4.1.3 Checking BAM SoftwareThis task describes how to check the software on the BAM to ensure that the BAM applicationcan be installed and run properly.

Procedure

Step 1 Check the version of Windows Server 2003 on the BAM.

Step 2 Check active services on the BAM.

Step 3 Check the version of SQL Server on the BAM.

Step 4 Check the operation of the SQL Server database.

Step 5 Check the login mode of the SQL Server database on the BAM.

Step 6 Check the data sequence of the SQL Server database on the BAM.

Step 7 Check the name consistency between the BAM and SQL Server.


Commissioning Guide


Step 8 Check the teaming of the Ethernet adapters on the BAM.

Step 9 Check the teaming modes of the Ethernet adapters on the BAM.

Step 10 Check the system time and time zone of the BAM and ensure that it is consistent with the localtime.

Step 11 Stopping the System Patron.

----End

4.1.4 Checklist for BAM Software Settings Performed BeforeDelivery

This part provides a checklist for BAM software settings before delivery. The checklist recordsthe BAM software installation and settings that are performed before delivery.

Table 4-1 Checklist for BAM software settings performed before delivery

Item Remarks

Setting the RAID 1relationship between twoSAS hard disks on theOMUa board

-

Setting BAM BIOS Set the first boot device of the BAM to CD-ROM drive.

Installing Windows Server2003

l The default password of the administrator of the active andstandby BAMs is 11111111.

l The computer default name of the OMUa board in slots 20and 21 in the RSS subrack is BAM_Right.

l The computer default name of the OMUa board in slots 22and 23 in the RSS subrack is BAM_Left

Activating the License ofWindows Server 2003

-

Installing the IPMI driver -

Installing Windows memorydiagnosis driver

-

Starting the Routing andRemote Access service

The Routing and Remote Access service is started and StartupType is set to Automatic.

Disabling the WindowsTime service

-

Disabling the ComputerBrowser service

-

Starting the TerminalServices service

The Terminal Services service is started and Startup Type isset to Automatic.

Enabling remote login -



Item Remarks

Installing the teaming driverof Intel 82571 Ethernetadapters

-

Installing the TeamingDriver of BACS Ethernetadapters

-

Creating the internalnetwork team

The preset IP addresses of the internal Ethernet adapters are:l Active BAM: 80.168.3.50 (255.0.0.0)

l Standby BAM: 80.168.3.60 (255.0.0.0)

Creating the externalnetwork team

The preset IP addresses of the external Ethernet adapters are:l Active BAM: 172.121.139.201 (255.255.255.0)

l Standby BAM: 172.121.139.202 (255.255.255.0)

Configuring backup channelIP addresses of the activeand standby BAMs

The preset backup channel IP addresses are:l Active BAM: 192.168.3.50 (255.255.255.0)

l Standby BAM: 192.168.3.60 (255.255.255.0)

Configuring commissioningIP addresses of the activeand standby BAMs

The preset commissioning IP addresses are:l Active BAM: 192.168.6.50 (255.255.255.0)

l Standby BAM: 192.168.6.60 (255.255.255.0)

Installing SQL Server 2000 The default password of the sa account is 11111111.

Installing SQL Server 2000Service Pack 4

The version number is 8.00.2039.

4.1.5 Installing the BAM Application in the Active WorkspaceThis task describes how to install the BAM application in the active workspace. If the RNC isconfigured with two OMUa boards, the BAM application must be installed in the activeworkspaces of both boards.

Prerequisitel You are remotely logged in to the BAM. Refer to 4.1.2 Remotely Logging In to the

BAM.l The BAM software is checked. Refer to 4.1.3 Checking BAM Software.

l The installation information of the BAM software is obtained. Refer to 4.1.1 Obtain theInstallation Information of the BAM Software.

l The setup disk of the BAM application is obtained and the files on the setup disk are copiedto the BAM hard disk in directory sharing mode. The setup disk of BSC6810 V200R009is delivered with the OMUa board.


Commissioning Guide


Context

CAUTIONWhen copying the files from the setup disk of the BAM application to a directory in the harddisk, ensure that these files are saved to a folder. The name of the folder contains no singlequotation mark. Otherwise, the BAM application cannot be successfully installed.

l It is not recommended to install the BAM application through the network.

l If you need to change the password of the system administrator on Windows Server 2003,the password of the user sa on SQL Server 2000, or the IP addresses of adapter teams beforeinstalling the BAM application, refer to Appendix: BAM Auxiliary Operations.

Procedure

Step 1 Double-click Setup.exe in the setup program pack of the BAM application. A window isdisplayed, as shown in Figure 4-2.

Figure 4-2 Selecting a language

Step 2 Select a language for the installation. For example, select English(United States). Click OK.A welcome dialog box is displayed.

Step 3 Click Next. The license agreement dialog box is displayed.

Step 4 Click Yes. A dialog box is displayed, as shown in Figure 4-3.



Figure 4-3 Selecting an installation option

Step 5 Select Install and then click Next. A dialog box is displayed, as shown in Figure 4-4.

Figure 4-4 Entering user information


Commissioning Guide


Step 6 Enter the user name, company name and serial number (all are case sensitive) in the dialog box.Then click Next to continue. A dialog box is displayed, as shown in Figure 4-5.

NOTE

The Next button appears dimmed until you type the right user name, company name, and serial number.

Figure 4-5 Verifying SQL Server information

Step 7 Enter the password of the account sa and then click Next. A dialog box is displayed, as shownin Figure 4-6.



Figure 4-6 Setting administrator information

Step 8 Enter the system administrator password in the Password box. This password consists of 6 to32 alphanumeric and case-sensitive characters. Confirm the password in the ConfirmPassword box, record it in Data Sheet of BAM Software Installation, and then click Next. Adialog box is displayed, as shown in Figure 4-7.


Commissioning Guide


Figure 4-7 Setting FTP user information

Step 9 Enter the FTP user password in the Password box. This password consists of 6 to 32alphanumeric and case-sensitive characters. Confirm the password in the Confirm Passwordbox, record it in Data Sheet of BAM Software Installation, and then click Next. A dialog boxis displayed, as shown in Figure 4-8.



Figure 4-8 Selecting an installation type

Step 10 Set the installation type as described in Table 4-2, and then click Next. A dialog box is displayed,as shown in Figure 4-9.

Table 4-2 Parameters in the Installation Type Selection dialog box

Parameter Description Remarks

Install stand-alonesystem

When the RNC is configuredwith one OMUa board, installthe stand-alone system on theBAM.

When the RNC is configured withone OMUa board, select thisoption.

Install dual system When the RNC is configuredwith two OMUa boards, installthe dual system on the BAM.

When the RNC is configured withtwo OMUa boards, select thisoption.


Commissioning Guide


Figure 4-9 Configuring the network interface

Step 11 Set the parameters as described in Table 4-3, record the settings in Data Sheet of BAM SoftwareInstallation, and then click Next. A dialog box is displayed, as shown in Figure 4-10.

Table 4-3 Parameters in the Installation Type Selection dialog box

Parameter Description Remarks

Subnet Network segments of internaland external virtual IPaddresses

The parameter is automaticallygenerated.

Mask Masks of internal and externalvirtual IP addresses


IP Address Internal and external virtual IPaddresses

l The internal virtual IP addressis automatically generated.

l For the principles of setting theexternal virtual IP address,refer to IP Addresses andPlanning Principle of theBAM.

Network Card Ethernet adapter teamcorresponding to internal/external virtual IP address




Figure 4-10 Configuring system information

Step 12 Enter a unique name (with no space) for the local office, record the settings in Data Sheet ofBAM Software Installation, and then click Next. A dialog box is displayed, as shown in Figure4-11.


Commissioning Guide


Figure 4-11 Selecting a license file

Step 13 Select a license file.

If... Then...

You select default license Click Next. A dialog box is displayed, as shown in Figure 4-12.

You select new license Specify a new license file for Target File, and then click Next. Adialog box is displayed, as shown in Figure 4-12.



Figure 4-12 Selecting the destination location

Step 14 Use the default path D:\WCDMA RNC or specify another path to save the BAM application. Indual-BAM mode, the paths must be the same. Then click Next. A dialog box is displayed foryour confirmation.

Step 15 Check the settings. If the settings are correct, click Next. The setup program starts copying files.

Step 16 When the files are copied, click Finish in the displayed dialog box.

Step 17 Check the following items to ensure that the installation is successful. Choose Start > AllPrograms. If there is a WCDMA RNC BAM program group including Start Bam Service,Stop Bam Service, Uninstall WCDMA RNC BAM, WCDMA RNC BAM Data Backup andRestore Tool, and WCDMA RNC BAM Data Upgrade Tool, you can infer that the BAMapplication in the active workspace is successfully installed.

NOTE

If the BAM application installation fails, uninstall the installed part. Then restart the server to reinstall theBAM application. If the installation still fails, contact the technical engineers in your local Huawei office.

Step 18 Start the BAMService. Refer to Starting BAMService.

----End

4.1.6 Checking the Operation of the BAM ApplicationThis task describes how to check the operation of the BAM application that includes operationof the BAMService and the SecurityManager.


Commissioning Guide


Procedure

Step 1 Choose Start > All programs > Administrative Tools > Services, and check the state of theBAMService in the displayed window.l If State is started, the installation is successful and the BAMService is running properly.

l If State of the BAMService is not started, you can infer that the BAMService is notstarted after the installation of the BAM application. In this situation, right-clickBAMService and click Start on the shortcut menu.

Step 2 When the BAMService starts, the icon shown in Figure 4-13 is displayed in the status area.Click the icon of the SecurityManager. The SecurityManager window is displayed. States ofService Processes During Proper BAM Operation describes different displays ofSecurityManager on single-BAM and dual-BAM systems.

Figure 4-13 Icon of the SecurityManager

----End

4.1.7 Installation Directory of the BAM ApplicationAfter the BAM application is installed, the BAM programs and data are stored in the installationdirectory of the BAM application. The default installation path is D:\WCDMA RNC\BAM. Thereare the following items are stored in the installation directory of the BAM application: thecomponents of the BAM application, the RNC host software, and various data used or generatedby the RNC.

Directory Structurel If the BAM application is installed on only the active workspace, the directory structure is

similar to that shown in Figure 4-14.l If the BAM application is installed on both the active workspace and the standby workspace,

the directory structure is similar to that shown in Figure 4-15. The directory structures ofthe VersionA and VersionB folders are the same.



Figure 4-14 Directory structure of BAM application of the active workspace


Commissioning Guide


Figure 4-15 Directory structure of BAM application of the active/standby workspace

CAUTIONDo not delete any file in the installation directory of the BAM application because the deletionmay cause severe faults to the system performance.

File Folders

Table 4-4 lists the file folders.

Table 4-4 File folders of the BAM application

Folder Name Description

Common\M2000 Stores the M2000 related data.

Common\NodeB Stores the NodeB related data.

Common\Services Stores the common programs of the active and standbyworkspaces.

Patch Stores the patch programs for remote upgrade.

Backup\RNCDataBackup\DBData

Stores configuration data in DB format for RNC backup.

Backup\RNCDataBackup\MML

Stores configuration data in MML format for RNC backup.

Backup\RNCDataRestore\DBData

Stores configuration data in DB format downloaded fromthe M2000 for restoring the RNC.

Backup\RNCDataRestore\MML

Stores configuration data in MML format downloadedfrom the M2000 for restoring the RNC.

EqpArch Stores equipment documents.

FTP\DefaultMeas Stores default performance measurement counters.

FTP\DefaultMeasSync Stores default measurement counters for synchronization.

FTP\DeviceFile Stores the device files exported from the RNC.




FTP\EmptyDirectory Internal directory, used by the FTP server.

FTP\ExportCfgXML Stores exported data configuration files.

FTP\ExportXMLFile Stores the files exported from the BAM, Perf, and Alarmdatabases.

FTP\License Stores the unactivated license file.

FTP\MeasDefinition Stores performance definition.

FTP\MeasResult Stores performance measurement results.

FTP\MeasResultList Stores performance measurement result lists.

FTP\NastarResult Stores the measurement results obtained by Nastar.

FTP\ReparentNodeBMML Stores the scripts exported during the relocation of theNodeB.

FTP\SDP Stores the description files of streaming programs.

License Stores the activated license file.

LoadDATA Stores the program files and data files of the boards on theFAM and the following directories: famlog, FamlogFmt,PFM, and FAD.

LoadData\famlog Stores FAM operation logs to be loaded to the BAM.

LoadData\FamlogFmt Stores FAM tracing log.

LoadData\PFM Stores performance data.

LoadData\FAD Stores diagnostic results to be loaded to the BAM.

LoadData\SMLC Stores the single-point positioning information generatedafter the single-point positioning.

MSSQL\Data Stores database files.

Onlinehelp\chs Stores help files in Chinese.

Onlinehelp\eng Stores help files in English.

Patch Stores the patch files of the BAM application and thePatchClient directory.

Patch\PatchClient Stores the client program of the BAM Remote Patch Tool.

Patch\PatchClient\Report\image

Stores the reports generated by the execution of the BAMRemote Patch Tool.

RNCVersions\MainArea Stores the current version of the RNC.

RNCVersions\StandbyArea Stores the standby version of the RNC.


Commissioning Guide



SecurityFile Stores the configuration files for the system patron andcustomized tools for Windows.

Services Stores the executable files of all the service modules in theBAM application, BAM tools, and the followingdirectories: CfgFiles, ExeDLL, Ipsec, Log, Restore, andUpgradeRule.

Services\CfgFiles Stores the current configuration files of modules.

Services\ExeDLL Stores language resource files of all the service modules ofthe BAM application.

Services\Ipsec Stores the execution programs for defining or removing theInternet protocol security policies.

Services\Log Stores log files of all the service modules of the BAMapplication.

Services\Restore Stores temporary files during upgrade.

Services\UpgradeRule Stores files of upgrade rules.

4.2 Commissioning the RNC LMTThis task describes how to commission the RNC LMT, including checking the computerconfiguration of the RNC LMT, installing the RNC LMT application, connecting the RNC LMTto the BAM, and starting the RNC Local Maintenance Terminal.

PrerequisiteThe RNC BAM has passed the commissioning.

1. 4.2.1 Checking the RNC LMTThis task describes how to check computer configuration of the RNC LMT beforecommissioning.

2. 4.2.2 Installing the RNC LMT ApplicationThis task describes how to install the RNC LMT application. It takes V200R009C01B040as an example.

3. 4.2.3 Connecting the RNC LMT to the BAMThis task describes how to connect the LMT to the BAM in the LAN. It instructs how toconnect the LMT to the OM network. This task is only performed before the LMT is usedfor the first time.

4. 4.2.4 Starting the Local Maintenance Terminal of the RNCThis task describes how to start the LMT and connect it to the specified RNC. This tasktakes the Local user account as an example to describe how to log in to the RNC on theLMT.

4.2.1 Checking the RNC LMTThis task describes how to check computer configuration of the RNC LMT beforecommissioning.



Procedure

Check the hardware configuration of the RNC LMT to ensure that the requirements in ComputerRequirements of the LMT are satisfied.

----End

4.2.2 Installing the RNC LMT ApplicationThis task describes how to install the RNC LMT application. It takes V200R009C01B040 as anexample.

Prerequisitel The setup disk and the instructions about the LMT application installation are available.

Huawei provides both the disk and the instructions.

l The valid CD-KEY of the LMT application is available.

l The PC on which the LMT application will be installed meets all the requirements listedin Computer Requirements of the LMT.

Procedure

Step 1 Use the administrator account to log in to the Windows XP operating system.

Step 2 Insert the setup disk into the CD-ROM drive.

l The setup program runs automatically. A dialog box is displayed, as shown in Figure4-16.

l If the setup program fails to run automatically, double-click setup.bat or setup.vbs in thedirectory of the setup disk. A dialog box is displayed, as shown in Figure 4-16.

Figure 4-16 Selecting a setup language

CAUTIONIf the setup languages of the LMT and BAM applications are different, some functions areunavailable, for example, managing RNC LMT operator accounts. It is recommended to keepthe two languages consistent.

Step 3 Select a language for the installation, and then click OK. A dialog box is displayed, as shownin Figure 4-17.


Commissioning Guide


Figure 4-17 Introduction to the setup wizard

Step 4 Read the introduction, and then click Next. A dialog box is displayed, as shown in Figure4-18.

Figure 4-18 Copyright notice

Step 5 Read the copyright notice. If you accept the agreement terms, select I accept these terms, andthen click Next to go to Step 6. A dialog box is displayed, as shown in Figure 4-19. If you donot accept the agreement terms, click Cancel to quit the installation.



Figure 4-19 Selecting the installation directory

Step 6 Use the default directory or set a new directory, and then click Next.

l If the installation directory does not exist, a dialog box is displayed, prompting whether toset up the directory. Click Yes. A dialog box is displayed, as shown in Figure 4-20.

l If the installation directory exists, a dialog box is displayed, as shown in Figure 4-20.

Figure 4-20 Selecting software components


Commissioning Guide


NOTE

The default installation path is D:\HW LMT. If the LMT application of other versions or of other NetworkElements (NEs) has already been installed, the default installation path is the path of the previousinstallation and cannot be changed. To change it, you must uninstall the existing LMT application.

If an LMT application is running, the Warning dialog box is displayed. If you click Yes, the LMTapplication is automatically stopped. If you click No, you need to manually stop the LMT application.

Step 7 Select the software components and then click Next. It is recommended to select all components.A dialog box is displayed for entering the CD-KEY, as shown in Figure 4-21.

Figure 4-21 Entering the CD-KEY

Step 8 Enter the CD-KEY correctly, and then click Next. The dialog box as shown in Figure 4-22 isdisplayed for confirming the installation.

NOTE

The CD-KEY is BSC6810.



Figure 4-22 Confirming installation

Step 9 Confirm the installation parameters and click Next. A dialog box for copying files is displayed.When the task for copying files is complete, the dialog box for initializing components isdisplayed. When all programs are installed, the Installation Completed dialog box is displayed.

Step 10 Click Finish. The installation is complete.

NOTE

When the installation is complete, the LMT Service Manager automatically starts.

----End

4.2.3 Connecting the RNC LMT to the BAMThis task describes how to connect the LMT to the BAM in the LAN. It instructs how to connectthe LMT to the OM network. This task is only performed before the LMT is used for the firsttime.

Prerequisitel The BAM communicates with the RNC host properly.

l The physical connection between the LMT and the BAM is established. Thecommunication between them is normal.

ContextYou can connect the LMT to the BAM through a LAN or a router.

Procedure

Step 1 To set the IP address of the LMT PC, refer to Setting the IP Address of the RNC LMT PC.


Commissioning Guide


Step 2 On the LMT PC, choose Start > Run, enter the cmd command in the Run dialog box, and thenpress Enter. The cmd.exe window is displayed.

Step 3 Enter ping BAM external virtual IP address in the cmd.exe window.

If the window displays similar information as follows, the communication between the LMTand the BAM is functional. The task is complete. In this example, the external virtual IP addressof the BAM is 10.161.197.206.

Pinging 10.161.197.206 with 32 bytes of data:Reply from 10.161.197.206: bytes=32 time<1ms TTL=125Reply from 10.161.197.206: bytes=32 time<1ms TTL=125Reply from 10.161.197.206: bytes=32 time<1ms TTL=125Reply from 10.161.197.206: bytes=32 time<1ms TTL=125Ping statistics for 10.161.197.206:Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),Approximate round trip times in milli-seconds:Minimum = 0ms, Maximum = 0ms, Average = 0ms

----End

4.2.4 Starting the Local Maintenance Terminal of the RNCThis task describes how to start the LMT and connect it to the specified RNC. This task takesthe Local user account as an example to describe how to log in to the RNC on the LMT.

Prerequisitel The physical link connecting the LMT to the BAM is established.

l The LMT application is installed correctly.

Context

WARNINGWhen the LMT application is running, do not modify the system time. Otherwise, serious errorsmay occur on the system. If you have to modify the system time, stop all the LMT applicationfirst.

Procedure

Step 1 Choose Start > All Programs > Huawei Local Maintenance Terminal > Local MaintenanceTerminal. The User Login dialog box is displayed, as shown in Figure 4-23.

If this is the first time to start the LMT? Then...

Yes Go to Step 2.

No Select the office to be connected in the Officedrop-down list, and then go to Step 6.



Figure 4-23 User Login dialog box

NOTE

l Click Offline to log in to the LMT offline. In this way, you do not log in to the BAM, but still canperform part of the functions of the LMT. For example, you can browse the online help.

l Click Exit to exit the LMT.

Step 2 Click . The Office Management dialog box is displayed, as shown in Figure 4-24.

Figure 4-24 Office Management dialog box before adding an office

Step 3 Click Add. The Add dialog box is displayed, as shown in Figure 4-25.


Commissioning Guide


Figure 4-25 Adding an office

Step 4 Set the office name and enter the external virtual IP address of the BAM. Click OK. The systemreturns to the Office Management dialog box shown in Figure 4-26.

NOTE

If the LMT PC is installed with the LMTs of other Network Elements (NEs) such as SGSN, you can selectone NE from the NE Type drop-down list, and then set the office for the NE.

Figure 4-26 Office Management dialog box after adding an office

Step 5 In the Office Management dialog box, click Close. The system returns to the User Login dialogbox, as shown in Figure 4-27.



Figure 4-27 User Login dialog box

Step 6 Enter the user name and password, and then click Login. The main interface of the LocalMaintenance Terminal is displayed.

NOTE

Before logging in to an NE as an EMS user on the LMT, you need to set up the connection between theNE and the M2000 server.If the LMT communicates with the BAM through the M2000 Proxy Server, select the Proxy Server in theUser Login dialog box and then enter the IP address of the proxy server.Log in with the account of admin for the first login. The password is set during the installation of the BAMapplication.

----End

4.3 Loading RNC Software and Data FilesThis task describes how to load the host software and data during RNC commissioning.

Prerequisitel The commissioning of the BAM and the RNC LMT is complete.

l The MML command scripts applicable to the local office are available.

l The license of the local office is in BAM Active Workspace Installation Directory\FTP\License and the file name is license.lic.

4.3.1 Generating RNC Data FilesThis task describes how to generate the loadable RNC data files by using the MML commanddata scripts.

4.3.2 Setting RNC Loading Modes (Commissioning)This task describes how to set the loading mode of subsystems of all the boards before resettingRNC boards.

4.3.3 Starting the RNC Message Tracing (Commissioning)This task describes how to start the RNC message tracing before RNC loading to record themessages in setting up cells.

4.3.4 Starting the Loading Progress Window


Commissioning Guide


This task describes how to start the loading progress window to monitor the loading progress ofthe programs and data of the RNC FAM boards and the host.

4.3.5 Loading the RSS SubrackThis task describes how to load the RSS host software and data files in BAM InstallationDirectory to the RSS subrack.

4.3.6 Loading the RBS SubrackThis task describes how to load the host software and data files in BAM Active WorkspaceInstallation Directory to the RBS subrack.

4.3.1 Generating RNC Data FilesThis task describes how to generate the loadable RNC data files by using the MML commanddata scripts.

Prerequisitel The LMT is started and properly communicates with the BAM.

l The MML command data scripts applicable to the local office are verified and the contentsare precise and complete.

ContextThe generated subrack loading file is saved in BAM Active Workspace Installation Directory\LoadData. The file name is in ABCXXYYZ.DAT format, such as SPU00020.DAT. Table 4-5lists the detailed information.

Table 4-5 Name of the loading file

Parameter Content

ABC Board name, such as SPUa.

XX Subrack number.

YY Slot number.

Z Subsystem number

Procedure

Step 1 On the MML client, run the SET OFFLINE command and set all the subracks to the offlinemode.

Step 2 Run the RST DATA command to set the parameters as follows: A dialog box is displayed. ClickYes to initialize the RNC configuration data on the BAM database. The Executionsucceeded message is displayed.

Step 3 On the main menu of the Local Maintenance Terminal, choose System > BatchCommands. The running commands in batches window is displayed, as shown in Figure4-28.



Figure 4-28 Running commands in batches

Step 4 In the Immediate Batch Command tab page, click Open. The Open dialog box is displayed.Select the prepared MML command data script. Click Open. The selected script is displayed inthe Immediate Batch Command window.

Step 5 Click Set. The setting batch commands dialog box is displayed. Set Sending CommandsInterval(s) to 0. Select Save Failed Results, and then set the saving path of the unsuccessfullyexecuted commands. Click OK to complete the setting of the batch commands, as shown inFigure 4-29.

Figure 4-29 Setting the batch commands

Step 6 On the window of the batch commands, set Execution Type to Execute All, as shown in Figure4-30.


Commissioning Guide


Figure 4-30 Setting the execution type

Step 7 Click Go. The system runs the MML commands one by one.

NOTE

Click OK when the system prompts that the current configuration is in offline mode. The execution ofMML commands may take a long time.

Step 8 Click OK when the system prompts that the running of all the MML commands is complete.The running result is shown in Figure 4-31.

Figure 4-31 Running result of immediate batch commands

NOTE

If the number of Failure in Total Results is not 0, modify the MML command script and go to Step1 to rerun the commands.

Step 9 Run the FMT DATA command to set Format type to ALL_SUBRACK(Format allsubracks) for formatting all the subracks.The Execution succeeded message is displayed. The generated data files can be obtainedin the loading path of the BAM.

Step 10 Run the SET ONLINE command to set all the subracks to the online mode.

----End

4.3.2 Setting RNC Loading Modes (Commissioning)This task describes how to set the loading mode of subsystems of all the boards before resettingRNC boards.

PrerequisiteThe LMT is started and properly communicates with the BAM.

ContextFor details about how to set the RNC loading mode, refer to RNC Loading Management.



ProcedureOn the MML client, run the SET LODCTRL command to set Board start load control. toLFB (Load from BAM and write flash). If the Execution succeeded message is displayed, thesetting of the RNC loading modes is complete.

----End

4.3.3 Starting the RNC Message Tracing (Commissioning)This task describes how to start the RNC message tracing before RNC loading to record themessages in setting up cells.


Contextl In ATM transport over the Iub interface, the tasks of the Iub interface message tracing,

QAAL2 protocol tracing, and SAAL protocol tracing are started.l In IP transport over the Iub interface, the tasks of the Iub interface message tracing, SCTP

protocol tracing, and IP tracing are started.l In ATM/IP dual stack transport over the Iub interface, the tasks of the Iub interface message

tracing, QAAL2 protocol tracing, SAAL protocol tracing, SCTP protocol tracing, and IPtracing are started.

Procedurel Starting the Iub interface message tracing

1. On the RNC Local Maintenance Terminal, click the Maintenance tab. ChooseTrace Management > Interface Trace Task in the left pane. Double-click Iub. Adialog box is displayed, as shown in Figure 4-32.


Commissioning Guide


Figure 4-32 Setting parameters of the Iub interface tracing

2. Set the parameters according to Table 4-6.

Table 4-6 Parameters of the Iub interface tracing

Parameter Setting

Tracing type Set it to All ports under the specified NodeB.

NodeB ID Enter the ID of the NodeB to be traced. Run theLST NODEB command to query the ID.



Parameter Setting

SPUa subsystem (SubrackNo.- Slot No.- Subsystem No.)

Set it to Select All.

Tracing message type Set it to Select All.

Auto save File Select it, and then specify a path or use the defaultone.

3. Click OK. After data is loaded to the RBS, the tracing messages are reported, as shownin Figure 4-33.

Figure 4-33 Iub interface tracing messages

NOTE

To query a record, right-click in the tracing message window, and then clear the Auto Scrolloption on the shortcut menu.

l Starting the QAAL2 protocol tracing1. On the RNC LMT, click the Maintenance tab. Choose Trace Management >

Interface Trace Task on the left pane. Double-click QAAL2. A dialog box isdisplayed, as shown in Figure 4-34.


Commissioning Guide


Figure 4-34 Setting parameters of the QAAL2 protocol tracing


Table 4-7 Parameters of the QAAL2 protocol tracing

Parameter Setting

Tracing type Set it to Trace the specified NodeBs.

NodeB ID (N1/N2/...) Enter the ID of the NodeB to be traced. Run theLST NODEB command to query the ID.

SPUa subsystem (Subrack No.-Slot No.- Subsystem No.)

Set it to Select All.


3. Click OK. After data is loaded to the RBS subrack, the tracing messages are reported,as shown in Figure 4-35.



Figure 4-35 QAAL2 protocol tracing messages

l Starting the SAAL protocol tracing1. On the RNC LMT, click the Maintenance tab. Choose Trace Management >

Interface Trace Task in the left pane. Double-click SAAL. A dialog box is displayed,as shown in Figure 4-36.


Commissioning Guide


Figure 4-36 Setting parameters of the SAAL protocol tracing


Table 4-8 Parameters of the SAAL protocol tracing

Parameter Setting

Link No. Enter the number of the SAAL link to be traced.


Set it as required.

Tracing message type Set it as required.





Figure 4-37 SAAL protocol tracing messages

NOTE

l You can also set the SAAL protocol tracing in the Setting parameters of the Iub interfacetracing dialog box. Select SAAL from Other Tracing Type. Set in the SAAL tab pageLink No. and Tracing message type.

l The results of setting the SAAL protocol tracing in the Setting parameters of the Iubinterface tracing dialog box and of double-clicking SAAL in the navigation tree are thesame.

l If the SAAL protocol tracing is set in the Setting parameters of the Iub interfacetracing dialog box, the tracing results of the SCTP protocol tracing and the Iub interfacetracing are displayed at the same time.

l Starting the SCTP protocol tracing1. On the RNC LMT, click the Maintenance tab. Choose Trace Management >

Interface Trace Task in the left pane. Double-click SCTP. A dialog box is displayed,as shown in Figure 4-38.


Commissioning Guide


Figure 4-38 Setting parameters of the SCTP protocol tracing


Table 4-9 Parameters of the SCTP protocol tracing

Parameter Setting

Link No. Enter the number of the SCTP link to be traced.


Set it as required.

Tracing message type Set it as required.

Auto save File Select it, and then specify a path or use thedefault one.




Figure 4-39 SCTP protocol tracing messages

NOTE

l You can also set the SCTP protocol tracing in the Parameter setting for the Iub interfacetracing dialog box. Select SCTP from Other Tracing Type. Set in the SCTP tab pageLink No. and Tracing message type.

l The results of setting the SCTP protocol tracing in the Setting parameters of the Iubinterface tracing dialog box and of double-clicking SCTP in the navigation tree are thesame.

l If the SCTP protocol tracing is set in the Setting parameters of the Iub interfacetracing dialog box, the tracing results of the SCTP protocol tracing and the Iub interfacetracing are displayed at the same time.

----End

4.3.4 Starting the Loading Progress WindowThis task describes how to start the loading progress window to monitor the loading progress ofthe programs and data of the RNC FAM boards and the host.

PrerequisiteThe LMT is started and properly communicates with the BAM.

Procedure

Step 1 On the main menu of the Local Maintenance Terminal, choose Check > Output Window.

Step 2 Click the Progress Management tab on the lower panel of the output window, as shown inFigure 4-40.


Commissioning Guide


Figure 4-40 Progress management

----End

4.3.5 Loading the RSS SubrackThis task describes how to load the RSS host software and data files in BAM InstallationDirectory to the RSS subrack.

Prerequisitel The RSS host software and data files in BAM Active Workspace Installation Directory

\LoadData are ready.

l The LMT is started and properly communicates with the BAM.

l The loading progress window is started. For details, refer to 4.3.4 Starting the LoadingProgress Window.

ContextThe process of loading the RSS subrack lasts three to five minutes.

Procedure

Step 1 Check whether the RSS subrack is powered on.



If... Then...

The RSS subrack is not powered on. Go to Step 2.

The RSS subrack is powered on. Go to Step 3.

Step 2 Switch on the power distribution boxes SW3 and SW6 to power on the RSS subrack. Obtain therelationship between the switches and subracks on the front panel of the power distribution box.The boards in the RSS subrack automatically load the host software and data file from the BAM.Go to Step 4.

Step 3 On the MML client, run the RST SUBRACK command to set Subrack No. to 0. A dialog isdisplayed, asking you whether to proceed. Click Yes. The boards in the RSS subrackautomatically load the host software and data file from the BAM.

Step 4 Observe the loading progress of the associated RSS subrack in Progress Management.

Step 5 After the loading of the RSS subrack, click the Device Panel tab in the navigation tree and thendouble-click the shelf node to be queried. The device panel is displayed, as shown in Figure4-41.

Figure 4-41 Device panel

If... Then...

The device panel displays the valid statusof the boards.

The loading of the RSS subrack is complete.

The device panel displays the invalidstatus of the boards.

Troubleshoot according to the prompt. Fordetails, refer to 15.7 RNC Boards LoadingFailures.

----End


Commissioning Guide


4.3.6 Loading the RBS SubrackThis task describes how to load the host software and data files in BAM Active WorkspaceInstallation Directory to the RBS subrack.

Prerequisitel The RBS host software and data files in BAM Active Workspace Installation Directory

\LoadData are ready.l The LMT is started and properly communicates with the BAM.

l The message tracing window is started. For details, refer to 4.3.3 Starting the RNCMessage Tracing (Commissioning).

l The loading progress window is started. For details, refer to 4.3.4 Starting the LoadingProgress Window.

l The RSS subrack is loaded and operational.

ContextThe process of loading one RBS subrack lasts three to five minutes.

Procedure

Step 1 Check whether the RBS subrack is powered on.

If... Then...

The RBS subrack is not powered on. Go to Step 2.

The RBS subrack is powered on. Go to Step 3.

Step 2 Switch on the power distribution box to power on the RBS subrack. Find the relationship betweenthe switches and subracks on the front panel of the power distribution box. The boards in theRBS subrack automatically load the host software and data file from the BAM. Go to Step 4.

Step 3 On the MML client, run the RST SUBRACK command to set Subrack No. to Number of theRBS to be loaded. A dialog box is displayed, asking whether to proceed. Click Yes. The boardsin the RBS subrack automatically load the host software and data file from the BAM.

Step 4 Observe the loading progress of the associated RBS subrack in the Progress Managementwindow.

Step 5 After the current RBS subrack is loaded, go to Step 3 to load other RBS subracks until all theRBS subracks of the RNC are loaded.

Step 6 After all the RBS subracks are loaded, click the Device Panel tab in the navigation tree, andthen double-click the shelf node to be queried. The device panel is displayed, as shown in Figure4-42.




If... Then...

The device panel displays the valid statusof the boards.

The loading of the RBS subrack is complete.

The device panel displays the invalidstatus of the boards.

Troubleshoot according to the prompt. Fordetails, refer to 15.7 RNC Boards LoadingFailures.

Step 7 Observe the signaling connection setup on the Iub interface and cell setup in the message tracingwindow.

If... Then...

The setup process is correct. End this task.

The setup process is incorrect. Troubleshoot according to the prompt. For details, refer to15.5 Signaling Link Failures on the Iub Interface or 15.4Cell Setup Failures.

----End

4.4 Activating and Verifying the LicenseThis task describes how to activate the RNC license and to verify whether the licenseconfiguration information is valid.


l The communication between the RNC FAM and the BAM is operational.


Commissioning Guide


l The license of the local office is in BAM Active Workspace Installation Directory\FTP\License and the file name is license.lic.

Procedure

Step 1 On the MML client, run the LST LICENSE command and enter the name of the license file tobe activated to query the detailed configuration information of the license file.

If... Then...

The license is consistent with that applied Go to Step 2.

The license is inconsistent with that applied Contact Huawei for confirmation.

Step 2 Run the LST CFGMODE to query the data configuration of all the subracks. If the subrack isin offline mode, run the SET ONLINE command to set the subrack to the online mode.

Step 3 Run the ACT LICENSE command to activate the licenses of all operators. The activation isperformed in sequence from the primary operator to the secondary operator. If there are multipleoperators, run the command repeatedly.

Step 4 Run the CMP LICENSE command to check whether the license of the host and that of theBAM are consistent.

If... Then...

The two licenses are consistent. End the task.

The two licenses are inconsistent. Go to Step 5.

Step 5 Run the DSP LICENSE command to check whether the license in the memory of the SCUa orSPUa board is consistent with that applied.

If... Then...

The query result is consistent with the actual configuration. End this task.

The query result is inconsistent with the actual configuration. Go to Step 1.

----End

4.5 Verifying Switchover Between Active and StandbyBoards

This task describes how to verify switchover between active and standby boards.



Prerequisitel The active and standby boards are operational.

l The communication between the RNC FAM and the BAM is operational.

l The LMT is started and properly communicates with the BAM.

Contextl The RNC supports switchover of boards such as the OMUa, SCUa, SPUa, CSUa, GCUa,

AOUa, UOIa, FG2a, and GOUa.l After the switchover of boards, the existing standby board becomes the active one. The

process lasts two to five seconds. The existing active board becomes the standby one andis reset. The process lasts two to five minutes.

NOTE

l If the existing RNC board to be switched over lacks the standby board, switchover cannot be performed.

l If the existing RNC board to be switched over is not backed up, switchover cannot be performed.

l If the RNC interface board is not configured in active and standby mode, switchover cannot beperformed.

l If the reference clock resource of the existing standby GCUa board is unavailable, switchover cannotbe performed.

l Switchover of boards does not have any impact on RNC services. The OM, however, is temporarilyinterrupted during switchover.

Procedure

Step 1 On the RNC LMT, click the Device Panel tab. In the navigation tree, double-click the shelfnode to be queried, as shown in Figure 4-43.


Step 2 Check the states of the active and standby boards to be switched over.


Commissioning Guide


If... Then...

The active and standby boards areoperational, that is, the active board panel isgreen and the standby board panel is blue.

Go to Step 3.

The standby boards are not operational,that is, the standby board panel is not blue.

l If the standby board is not in position, re-insert or reset the standby board. If theproblem persists, contact the local Huaweioffice for technical support.

l If the standby board is faulty, contact thelocal Huawei office for technical support.

l If a warning alarm is reported on thestandby board, contact the local Huaweioffice for technical support.

Step 3 On the MML client, run the SWP BRD command to switch over the active board:l Set Subrack No. to the number of the subrack where the board to be switched over is located.

l Set Slot No. to the number of the slot holding the board to be switched over.

In the displayed dialog box, click Yes. Expectation: The Execution succeeded messageis displayed.

Step 4 Go to Step 2 to check whether all the boards that are switched over are operational.

----End



RNC Commissioning Guide 01-04 Commissioning the RNC Equipment

Documents

Transcript of RNC Commissioning Guide 01-04 Commissioning the RNC Equipment