08 commissioning i hspa adapter

Commissioning I-HSPA Adapter

DN70360523Issue 1-3 en draft

# Nokia Siemens Networks 1 (32)

The information in this document is subject to change without notice and describes only theproduct defined in the introduction of this documentation. This document is not an officialcustomer document and Nokia Siemens Networks does not take responsibility for any errors oromissions in this document. This document is intended for the use of Nokia Siemens Networkscustomers only for the purposes of the agreement under which the document is submitted. Nopart of this documentation may be used, reproduced, modified or transmitted in any form ormeans without the prior written permission of Nokia Siemens Networks. The documentation hasbeen prepared to be used by professional and properly trained personnel, and the customerassumes full responsibility when using it. Nokia Siemens Networks welcomes customercomments as part of the process of continuous development and improvement of thedocumentation.

The information or statements given in this documentation concerning the suitability, capacity orperformance of the mentioned hardware or software products are given “as is” and all liabilityarising in connection with such hardware or software products shall be defined conclusively andfinally in a separate agreement between Nokia Siemens Networks and the customer.

IN NO EVENT WILL Nokia Siemens Networks BE LIABLE FOR ERRORS IN THISDOCUMENTATION OR FOR ANY DAMAGES, INCLUDING BUT NOT LIMITED TO SPECIAL,DIRECT, INDIRECT, INCIDENTAL OR CONSEQUENTIAL OR ANY LOSSES SUCH AS BUTNOT LIMITED TO LOSS OF PROFIT, REVENUE, BUSINESS INTERRUPTION, BUSINESSOPPORTUNITY OR DATA, that might arise from the use of this document or the information in it.

THE CONTENTS OF THIS DOCUMENT ARE PROVIDED "AS IS". EXCEPT AS REQUIREDBY APPLICABLE MANDATORY LAW, NO WARRANTIES OF ANY KIND, EITHER EXPRESSOR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OFMERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NON-INFRINGEMENT,ARE MADE IN RELATION TO THE ACCURACY, RELIABILITY OR CONTENTS OF THISDOCUMENT. NOKIA SIEMENS NETWORKS RESERVES THE RIGHT TO REVISE THISDOCUMENT OR WITHDRAW IT AT ANY TIME WITHOUT PRIOR NOTICE.

This document and the product it describes are considered protected by copyrights and otherintellectual property rights according to the applicable laws.

The wave logo is a trademark of Nokia Siemens Networks Oy. Nokia is a registered trademark ofNokia Corporation. Siemens is a registered trademark of Siemens AG.

Other product names mentioned in this document may be trademarks of their respective owners,and they are mentioned for identification purposes only.

Copyright © Nokia Siemens Networks 2008. All rights reserved.

2 (32) # Nokia Siemens Networks DN70360523Issue 1-3 en draft


Contents

Contents 3

Summary of changes 5

1 Introduction to I-HSPA Adapter commissioning 7

2 Site Configuration File 11

3 Loading the I-HSPA Adapter Software 153.1 Loading the I-HSPA Adapter software 15

4 Performing commissioning 194.1 Launching the Site Configuration File Hit Macro Tool 194.2 Logging into the I-HSPA Adapter 204.3 Parsing the Site Configuration File 21

5 Verifying commissioning 25

6 Troubleshooting 316.1 Select SCF file 316.2 Parameters missing from SCF 316.3 Incorrect length of RNC-Id 32



Contents

Summary of changes

Changes between document issues are cumulative. Therefore, the latestdocument issue contains all changes made to previous issues.

Changes between issues 1-2 and 1-3

Sections Site Configuration file, Loading the I-HSPA Adapter software,Launching the SCF Hit Macro Tool, and Parsing the Site Configuration File(SCF) have been updated.

Editorial changes.


. New chapter added Loading the I-HSPA Adapter Software.


. Precondition for commissioning laptop date and date settings addedto Commissioning preconditions.

. New section added Launching the SCF Hit Macro Tool.

. Screenshots of the SCF HIT Macro Tool added to Logging into the I-HSPA Adapter.

. Screenshots of the SCF HIT Macro Tool added to Parsing the SiteConfiguration File (SCF).



Summary of changes

1 Introduction to I-HSPA Adaptercommissioning

This document describes how to commission Nokia Siemens Networks I-HSPA Adapter.

Nokia Siemens Networks recommends that you should have the relevantknowledge of base station systems and equipment. Pay careful attentionto all warnings and cautions.

These instructions are based on the assumption that the user knows howto use basic computer software and has the appropriate user rights for thenecessary actions.

Note

Nokia Siemens Networks recommends only properly trained andauthorized personnel perform installation, cabling, commissioning, andmaintenance operations on any Nokia Siemens Networks BTS site.

Commissioning procedure

The commissioning procedure is divided into actions performed by thecommissioning engineer and those performed by I-HSPA Adaptersoftware.

The procedure steps are as follows:

. Actions performed by commissioning engineer:

1. Logging into the I-HSPA Adapter.

2. Loading I-HSPA Adapter software.

3. Entering the time and date.



Introduction to I-HSPA Adapter commissioning

4. Running the SCF Hit Macro to parse the Site ConfigurationFile (SCF) and send configuration commands to the I-HSPAAdapter.

5. Integrating I-HSPA Adapter software to Flexi WCDMA BTS.

Note that you need to commission Flexi WBTS with the SiteCommissioning File (SCF) or manually using thecommissioning wizard in the WBTS Manager.

Actions performed by I-HSPA Adapter software:

1. Configuration of the I-HSPA Adapter, including IP security (IPSec,optional feature) configuration if required.



Figure 1. Commissioning

Check prerequisites

Commissioning

Check the site configuration file

Load the I-HSPA Adapter software

Launch the SCF Hit Macro Tool

Log into I-HSPA Adapter

Run the commissioning macro (SCF)

Conclude commissioning

Integration

Check prerequisites

Integrate I-HSPA to NetAct

Create RNW plan

Configure Iu-PS interface

Configure Iu-CS interface

Configure Iur interface

Integrate I-HSPA with SAS

Download the license files

Download and activate RNW plan

Verify integration



Introduction to I-HSPA Adapter commissioning

Commissioning preconditions

Before commissioning can be performed, the following tools, files andinformation are required:

. SCF HIT Macro Tool

. HIT tools to execute HIT macro

. I-HSPA Adapter SCF

You have created the SCF with the Plan Editor using either the I-HSPA OMS or NetAct. For more information, see Site ConfigurationFile. For more details on Plan Editor, see Plan Editor Help and PlanEditor Principles in NetAct product documentation.

. Default user name and password pair

. IP address of the I-HSPA Adapter

. Time and date settings of the commissioning laptop are the same asthe network to which the I-HSPA Adapter is being installed into.

. WBTS commissioning (if SCF is used, it should contain both FTMand BTS SCF files). For instructions, see Commissioning FlexiWBTS.



2 Site Configuration File

The commissioning information for the I-HSPA Adapter is held in the SiteConfiguration File (SCF). The SCF is created in the Plan Editor before theintegration phase, either in NetAct or OMS, and is then uploaded to I-HSPA Adapter and activated.

The SCF contains the following information:

. Adapter ID (RNCId)

. Adapter name (RNCName)

. Adapter basic IP configuration

. A flag indicating whether the FTM is used

. C-Plane / M-Plane IPSec installation parameters

For more information, see I-HSPA Adapter Site Configuration Parameters.

Content of the SCF

It is important to gather all necessary information in the right place beforerunning the commissioning script for the first time:

10.8.228.33 //example value, the real must be edited

according to the actual network

10.8.228.41 //example value, the real must be edited


28 //example value, the real must be edited


0 //default value

10.8.147.40 //example value, the real must be

edited according to the actual network

10.8.228.39 //this IP cannot be changed afterwards.

The value must be the same than Southbound IP in I-HSPA OMS (=BTS O&M IP)

SYSTEM //default value

SYSTEM //default value

10.8.228.36 //example value, the real must be edited


28 //example value, the real must be edited



Site Configuration File

IADA-71 //example value, the real must be edited according

to the actual network

10.8.229.33/28 //example value, the real must be

edited according to the actual network

Here is an example of the SCF file:

<?xml version="1.0"?>

<raml version="2.1" xmlns="raml21.xsd">

<cmData type="plan" scope="all" domain="IADASCF" name="adaSc"

adaptationVersionMajor="IH1.0">

<header>

<log user="unknown" action="created" dateTime="2008-02-21T13:57:31" appInfo="Nokia

Plan Editor">No description</log></header>

<managedObject class="ADASC" operation="create" distName="IADA-71/ADASC-1">

<!--p name="LocalTelnetFTPDest">Not defined

<!--p name="CALDAPServerIpAddress">Not defined

<!--p name="CMPlaneIPSecUsage">0

<!--p name="CMPPreSharedKey">Not defined

<!--p name="CMPReferenceNumber">0

<!--p name="CoreIPDestinations">Not defined

<!--p name="CoreVPNGWIPAddr">Not defined

<!--p name="CRLIndicator">0

10.8.228.33

10.8.228.41

28

0

<!--p name="IKEKeyVPNAccessCA">Not defined

<!--p name="CACertificateFilename">Not defined

<!--p name="LDAPDNForCACertificate">Not defined

<!--p name="UserPlaneIPSecUsage">0

10.8.147.40

<!--p name="OMSFTPPassword">SYSTEM

<!--p name="OMSFTPUserName">SYSTEM

10.8.228.39

10.8.228.36

28

<!--p name="OwnCertificateFilename">Not defined

<!--p name="OwnPrivateKeyFilename">Not defined

IADA-71

<!--p name="SecuredIurIPDest">Not defined

<!--p name="SubjNameADAOwnCert">Not defined

<!--p name="URLToCACMPServer">Not defined

10.8.229.33/28

</managedObject>

</cmData>

</raml>

Note that I-HSPA OMS IP address is a Northbound IP, which is used forSSH or HTTPS sessions. It is not used in the SCF or by the I-HSPAAdapter:

I-HSPA OMS Adapter (SCF)

I-HSPA OMS IP = Northbound IP -

I-HSPA OMS BTS O&M IP = Southbound IP OMSIpAddress

Modes of operation

The SCF macro operates in three modes:

. SIMU

. SYSTEM

. DEBUG

In simulator mode (SIMU), you can execute the macro and select the SCF,but the MML commands are not sent to the system. However, theinformation is shown in the message window.

In SYSTEM mode, you can execute the macro as well as commission theadapter. The MML commands prepared from the SCF data are sent to theadapter for commissioning.

In DEBUG mode, you can debug the macro. Before sending each of thecommands, the macro waits for user input.

Note that the user name and password for each of the modes are themode name itself. For example, in SIMU mode, the user name is SIMUand the password is SIMU.



Site Configuration File

3 Loading the I-HSPA Adapter Software

3.1 Loading the I-HSPA Adapter software

Purpose

The I-HSPA Adapter software package must be installed before you cancontinue the commissioning of the I-HSPA Adapter. There may already besoftware in use in the adapter. Ensure that the level of the software is valid.If the software is valid, no software installation procedure is needed andyou can continue the commissioning procedure from chapter Performingcommissioning.

Before you start

1. Check the software delivery on the I-HSPA Adapter with the MMLcommand:

ZWQO:EX;

Note that the I-HSPA Adapter has a limitation of two packages - onlytwo software builds can be on a disk at the same time.

2. If more than one package is shown in the printout, check the statusof the packages in SOMAFI with the MML command ZWQO:CR;.

ZWQO:CR;

LOADING PROGRAM VERSION 13.8-0

PACKAGES CREATED IN OMU:

SW-PACKAGE STATUS DIRECTORY ENVIRONMENT DEF ACT

PACKAGE-ID (REP-ID) DELIVERY

CD-ID

A BU A Q3 6.11-0 Y Y

Q3 6.11-0 CID000QX 8.3-0

COMMAND EXECUTED

SOFTWARE PACKAGE ADMINISTRATION COMMAND <WQ_>



Loading the I-HSPA Adapter Software

3. Delete the non-default package using the MML command:

ZWQD:name=(name of package to be deleted),DIRE,PRINTS;

4. Ensure that the default software build is the one that should be usedbased on release or trial information. If the software build is not valid,install new software as described below. If the default software isvalid, you can continue from chapter Performing commissioning.

Summary

The following is an example of how to put the software to the adapterlocally. The example uses RIS 7.2 build 6.9-1.

Steps

1. Unzip the software package on your local computer.

2. Connect to the BTS (LMP port OMU IP addess 192.168.255.143).

3. Connect your computer to OMU with FTP software.

Check that binary mode is for file transfer.

4. Upload the whole package from your local computer to thefolder /shadows/ of OMU.

You get a new folder /shadows/ <package>, which contains all thefiles needed for the load package.

For example: /shadows/ Q3060901

5. Create the SW package with the MML command.

Remember the limitation of two packages: only two software buildsare allowed at the same time in the I-HSPA Adapter:

ZWQC:NAME=<package>,DIRE=<package>,STAT=NW;

6. Check the package you created with the MML command.

ZWQO:CR;

7. Set the created package as default.

ZWSD:STAT=NW;

The system reboots automatically.

8. Check that the default package is correct.

ZWQO:CR;

9. Change the status of the network created package to BU.

ZWSC;STAT=BU:STAT=NW;

ZWQO:CR;

10. Delete the old package.

ZWQD:NAME=(name of old package to be deleted):DIRE;

11. Check that the package has been deleted.

ZWQO:EX;



Loading the I-HSPA Adapter Software

4 Performing commissioning

4.1 Launching the Site Configuration File Hit MacroTool

Purpose

The Site Configuration File (SCF) Hit Macro Tool is used for running theSCF Hit Macro, which parses the SCF file. The I-HSPA Adapter iscommissioned using the settings provided in the SCF file.

Before you start

Note that before the SCF Hit Macro has been run, no other actions areallowed.

The commissioning laptop has to be connected to the WBTS LMP portwith the correct IP (192.168.255.143) settings.

Take safecopies of the empty data files located in the LFILES directory inthe OMU. They can be used to restore the state if the launch is notsuccessful.

Summary

Before you start I-HSPA Adapter commissioning, you need to execute theSCF Hit Macro and provide the correct SCF file as input.

In case of an error, you can choose to revert to the older configuration. It ispossible to correct mistakes as a fallback copy of the configuration iscreated.

Steps

1. Double-click the desktop SCF Hit Macro Tool icon.



Performing commissioning

2. Open the Message window.

3. To take the configuration file (SCFHIT.INI) in use, select Device >Set Configuration > Configuration File <Browse>.

4. In the RUN menu, select RUN or press F9 .

The SCF Hit Macro is run.

Note that if the SCF Hit Macro has to be run again for some reason,LFILES needs to be emptied and replaced with the original files inLFILES.

5. To continue, select the Continue check box.

4.2 Logging into the I-HSPA Adapter

Purpose

The I-HSPA Adapter is delivered with a default user name and password,which are used at the start of the commissioning process. After initial login,new user name and password are requested. These are used throughoutthe rest of the commissioning process and to open the connectionbetween the I-HSPA Adapter and OMS.

Steps

1. Enter default user name and password.

2. Change the user name and password.

Use the SCF HIT Macro Tool to enter the new user name andpassword.

Figure 2. Enter new user name

Figure 3. Enter password

4.3 Parsing the Site Configuration File

Purpose

The Site Configuration File (SCF) is parsed by the SCF HIT Macro and thenecessary configuration commands are sent from the commissioninglaptop to the I-HSPA Adapter.

Steps

1. Select Choose SCF File.

From the menu, select Choose SCF File and click OK.




Figure 4. Commissioning menu

2. Select SCF File.

In the Explorer view, browse to the desired SCF file location andclick Open.



Figure 5. Select SCF file

If the SCF file is correct and does not contain errors, theCommissioning menu will reappear.

If the SCF file contains errors, you are asked to select again thecorrect SCF file and the invalid parameters are displayed.

3. Parse the SCF.

From the menu, select Start Adapter Commissioning and clickOK.




Figure 6. Start I-HSPA Adapter commissioning

Expected outcome

The status of the commissioning process is displayed in the Messagesview.

During this process the I-HSPA Adapter is automatically restarted.

Successful completion of the commissioning process is displayed in theMessages view:

Figure 7. Commissioning complete



5 Verifying commissioning

The I-HSPA Adapter is configured by the I-HSPA Adapter software with theconfiguration commands sent by the SCF Hit Macro from thecommissioning laptop. The connection to the I-HSPA OMS is configuredby the SCF. The use of the FTM will be determined by the SCF and the I-HSPA Adapter is set accordingly. The basic IP parameters needed forintegration will also be contained within the SCF.

After the commissioning has been completed, the I-HSPA Adapterconfiguration process is continued from the OMS to integrate the I-HSPAAdapter into the network. A connection to the OMS should be openedbefore the rest of the configuration procedure is executed.

Security

The use of IPSec in the I-HSPA Adapter is optional, but if required, thenecessary IPSec configuration is carried out automatically during the I-HSPA Adapter configuration process. The IPSec settings are containedwithin the SCF and the required commands included in the SCF Hit Macro.

1. Check unit states.

< ZUSI;


WORKING STATES OF UNITS 2008-05-15 16:00:11

UNIT PHYS LOG STATE INFO

OMU-0 0000H 4002H WO-EX -

DSP-0 0011H 4A31H WO-EX -

NUMBER OF UNITS DISPLAYED = 2

COMMAND EXECUTED



Verifying commissioning

2. Check the I-HSPA Adapter IP configuration using the MMLcommand:

< ZQRI;


RNC IPA2800 2002-01-06 23:44:40

INTERROGATING NETWORK INTERFACE DATA

IF ADM IF ADDR

UNIT NAME STATE MTU PRIORITY TYPE TYPE IP ADDRESS

--------- --------- ------ ---- --------- ---- ---- -----------------------

OMU-0 EL0 UP 1500 - P 192.168.254.143/24

VLAN1 UP 1496 - P 192.168.1.143/24

VLAN2 UP 1496 - P 192.168.255.143/24

P 10.8.229.33/28

VLAN3 UP 1496 - P 10.8.228.36/28

DSP-0 ETH0.3 UP 1500 - P (10.8.228.41)/28

ETH1.1 UP 1496 - P (192.168.1.142)/24

ETH1.2 UP 1496 - P (192.168.255.142)/24

COMMAND EXECUTED

Note that if IPoA is in use, the ZQRI output is different:

OMU-0 AA0 UP 1464 - N P 10.20.163.10/29

->10.20.163.13

AA1 UP 1464 - N P 10.10.1.153/24

->10.10.1.1

EL0 UP 1500 - P 192.168.254.143/24

VLAN1 UP 1496 - P 192.168.1.143/24

VLAN2 UP 1496 - P 192.168.255.143/24

P 10.20.163.193/29

DSP-0 ATM0 UP 1464 - N P (10.20.163.11)/29

ATM1 UP 1464 - N P (10.10.1.152)/24

ETH0 UP 1500 - P (192.168.254.142)/24

ETH1.1 UP 1496 - P (192.168.1.142)/24

ETH1.2 UP 1496 - P (192.168.255.142)/24

3. Check the RNC ID in object MML:

RNCId is stored to two first bytes. In the file they are in hexadecimalformat.

< ZDFD:OMU,O:09F20001,0,;

RNC IPA2800 2002-01-06 23:41:14

OMU-0 FILE N:O 09F20001 RECORD N:O 00000000 RESERVED

47 00 49 41 44 41 2D 37 31 00 00 00 00 00 00 00 G.IADA-71.......

00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................

00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................

00 00 00 00 00 02 00 00 00 00 00 03 00 00 00 00 ................

00 00 00 00 00 00 00 00 00 00 00 01 00 00 00 00 ................

00 00 00 00 00 00 00 00 00 00 01 00 00 00 00 00 ................

00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 90 ................

01 05 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................

00 00 00 00 00 00 00 00 00 01 05 C8 F4 01 0A 14 ................

E8 03 E8 03 F4 01 C8 00 01 C8 00 C8 00 08 00 08 ................

00 03 00 04 03 00 05 00 14 0C 00 05 14 70 17 70 .............p.p

17 FA 00 00 03 03 01 0A 05 30 C8 00 08 0C 10 12 .........0......

14 16 18 08 0C 10 12 14 16 18 08 0C 10 12 14 16 ................

18 02 02 0A 3C 00 01 00 00 00 00 00 00 00 00 00 ....<...........

19 19 19 00 00 00 00 0A 0A 0A 00 00 00 00 00 00 ................

00 00 00 00 00 00 00 00 00 00 00 1E 00 00 00 00 ................

00 00 00 04 04 00 00 04 04 00 00 00 00 00 00 01 ................

00 00 00 19 00 00 00 00 00 00 00 00 00 00 00 00 ................

03 00 0A 06 00 00 00 00 00 00 00 00 00 00 00 00 ................

00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................

00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................

00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................

00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................

00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................

00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................

00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................

00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................

00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................

00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................

00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................

00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................

00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................

00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................

00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................

00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................

00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................

00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................

00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................

00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................

00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................

00 00 00 02 00 00 A8 00 01 00 A8 00 00 00 00 00 ................

00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................

00 00 00 00 00 00 00 00 00 00 00 00 00 01 01 C8 ................

00 03 02 00 00 A8 00 01 00 A8 00 00 00 00 00 00 ................

00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................

00 00 00 00 00 00 00 00 00 00 00 00 01 01 C8 00 ................

03 06 5A 1E 00 08 00 02 00 00 A8 00 01 00 68 01 ..Z...........h.

00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................

00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................

00 02 01 6E 00 03 03 00 00 A8 00 01 00 A8 00 02 ...n............

00 A8 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................

00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................

01 00 C8 00 03 02 00 00 50 00 01 00 50 00 00 00 ........P...P...

00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................

00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 01 ................

00 D2 00 03 01 00 00 00 00 00 01 00 00 00 00 00 ................

00 08 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................

00 00 00 00 00 00 00 00 00 00 00 00 01 00 00 00 ................

00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................

00 00 00 00 00 03 00 01 00 00 00 00 00 00 00 00 ................

00 14 00 00 00 00 00 00 00 00 46 2C 01 0F 02 29 ..........F,...)

00 00 2B 00 00 00 00 00 00 00 00 00 00 00 00 00 ..+.............

00 00 00 00 00 00 00 00 FF 17 17 00 00 00 00 00 ................

00 00 00 00 00 00 00 00 00 00 00 02 14 00 00 00 ................

00 00 00 00 00 00 00 00 00 00 00 01 00 00 00 01 ................

00 00 00 00 00 00 01 00 00 00 00 00 00 00 00 00 ................

00 00 00 00 FF 00 00 00 00 00 00 00 00 00 00 00 ................

00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................

00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................

00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................

00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................

00 00 00 00 00 00 00 00 00 00 00 00 23 00 23 00 ............#.#.

CD 00 CD 00 00 00 00 01 00 00 00 00 00 00 00 00 ................

00 00 00 00 00 00 00 00 00 00 00 CC 00 03 00 00 ................

00 64 64 64 64 64 64 64 64 64 64 64 64 64 64 64 .ddddddddddddddd

64 64 64 64 64 3C 3C 3C 3C 64 64 64 64 64 64 64 ddddd<<<<ddddddd

64 64 64 64 64 64 64 64 64 64 64 64 64 64 64 08 ddddddddddddddd.

1E 3C 08 1E 3C 0A 0A 0A 0A 0A 0A 0A 0A 0A 00 00 .<..<...........

00 64 00 64 0A 00 00 3C 00 00 00 00 00 00 00 00 .d.d...<........

00 00 00 00 00 00 00 00 00 0A 01 00 28 00 46 00 ............(.F.

2C 01 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ,...............

00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................

00 00 00 00 00 00 0A 14 50 00 0F 0C 0C 8C 00 04 ........P.......

17 01 46 00 00 00 00 00 00 00 00 00 00 00 00 00 ..F.............

00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................

00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................

00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................

00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................

00 00 00 00 00 00 00 00 00 00 00 00 00 00 E8 03 ................

00 00 00 00 00 00 00 00 00 00 00 00 00 00 0A 08 ................

E4 27 00 00 00 00 00 00 00 00 00 00 00 00 00 1E .'..............

00 00 00 00 00 00 01 00 00 00 00 00 00 00 00 00 ................

00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................

00 00 00 00 00 00 00 00 00 00 00 00 ............

4. Check that Flexi WCDMA BTS and OMS have established BTSO&M connections using the MML command:

< ZQRS:OMU,O;


RNC IPA2800 2002-01-06 23:45:17

UNIT: OMU-0

Active Internet connections (including servers)

Proto Recv-Q Send-Q Local Address Foreign Address State

tcp 65 0 10.8.228.36.65533 10.8.228.39.BS-O&M ESTABLISHED

tcp 0 36 192.168.255.143.telnet 192.168.255.126.1622 ESTABLISHED

tcp 0 0 192.168.255.143.telnet 192.168.255.126.1619 ESTABLISHED

tcp 0 0 10.8.229.33.BS-O&M 10.8.229.34.65137 ESTABLISHED

tcp 0 0 *.832 *.* LISTEN

tcp 0 0 *.8019 *.* LISTEN

tcp 0 0 *.ftp *.* LISTEN

tcp 0 0 *.www *.* LISTEN

tcp 0 0 *.11111 *.* LISTEN

tcp 0 0 *.BS-O&M *.* LISTEN

tcp 0 0 *.telserve *.* LISTEN

tcp 0 0 *.telnet *.* LISTEN

udp 0 0 127.0.0.1.524 *.*

udp 0 0 192.168.255.143.1002 *.*

udp 0 0 192.168.255.143.1000 *.*

udp 0 0 *.bootps *.*

Active Internet6 connections (including servers)

Proto Recv-Q Send-Q Local Address Foreign Address State

tcp6 0 0 *.21 *.* LISTEN

tcp6 0 0 *.23 *.* LISTEN

COMMAND EXECUTED

5. Check that a correct profile has been created for OMS softwaredownload (SOKERI is an example):

< ZIAI:PROFILE=SOKERI;

EXECUTION STARTED

RNC IPA2800 2002-01-06 23:46:24

PROFILE NAME: SOKERI

COMMAND CLASS AUTHORITIES:

A=250 B=250 C=250 D=250 E=250 F=250 G=250 H=250 I=250 J=250

K=250 L=250 M=250 N=250 O=250 P=250 Q=250 R=250 S=250 T=250

U=250 V=250 W=250 X=250 Y=250

PASSWORD VALIDITY TIME: PASSWORD NEVER EXPIRES

MML COMMAND LOG ACCESSIBILITY: LIMITED

UNIQUE PROFILE: NO

MML SESSION IDLE TIME LIMIT: 15 MIN(S)

FTP ACCESSIBILITY: WRITE

PROFILE IS USED BY: SOKERI

COMMAND EXECUTED

6 Troubleshooting

6.1 Select SCF file

Description

You have not selected any SCF file and you are performing an operationthat requires SCF settings.

Symptoms

An error message appears on the screen asking you to select the SCF filefirst.

Recoveryprocedures

Go back and select the correct SCF file. Then, try to perform the operationagain.

6.2 Parameters missing from SCF

Description

The parameters mentioned in the error message are missing from the SCFfile.

Symptoms

An error message appears on the screen, listing the parameters that aremissing from the SCF file.



Troubleshooting

Recoveryprocedures

Select the correct SCF file.

6.3 Incorrect length of RNC-Id

Description

The SCF contains an incorrect value for the distName parameter. Themaximum length of the value for this parameter is eight digits, but now thevalue is longer than that.

Symptoms

An error message appears on the screen informing that the RNC-Id lengthis wrong.

Recoveryprocedures

Correct the parameter value to contain a maximum of eight digits.



08 commissioning i hspa adapter

Engineering

Transcript of 08 commissioning i hspa adapter