Internal Use Only

iBSC Commissioning
Intended audience: Staff with Skill Certificate Level III or Lower Released by GU Product Support Dept.

Internal Use Only

Version Introduction
Version
R1.0

Date
2011-2-18

Author
Sun Jingjing

Checked by
Su Shaoli, Fei Aiping, Liu Yu, Wu Zhiliang, Tsai Kai, Sun Jinye

Revision Record
None

References:
1. 2. ZXG10 iBSC(V6.20) Commissioning Guide

Internal Use Only

Course Objectives:
To grasp the knowledge about OMP directory To be familiar with the startup process of the OMP board and peripheral boards

To know how to set DIP switches and calculate the Control Plane IP
To be familiar with the iBSC single-server commissioning steps To master the method of iBSC single-server commissioning

Internal Use Only

Contents

Rudimentary Knowledge
iBSC Single-Server Commissioning Steps Configuration of Basic iBSC Data

OMP Board Commissioning

Peripheral Board Commissioning

Internal Use Only

OMP Directory Structure

The storage device of OMP consists mainly of two parts: DOC0 and IDE0. DOC0 is a flash chip used for storing the data necessary for the startup of the OMP. The chip has two types, 64M and128M. IDE0 is a 2G micro drive.

Internal Use Only

OMP Directory Structure

/DOC0/VER: The configuration data and CPU & FPGA version files necessary for the startup of the OMP board. Please refer the file attached for the five configuration files under the VER directory.

Internal Use Only

OMP Directory Structure

/DOC0/USERINFO: Set the user name and password of the telnet and ftp service. After /DOC0 is cleared or is initialized, the username and password of the ftp user will be lost, but that of the telnet user will not be lost. There are two ways of adding ftp users:

telnet to the OMP board and execute addFtpUserInfo zte,zte,3,3,0 Execute OSS_AddFtpUserByPort "zte","zte",0 through the serial port.

Internal Use Only

OMP Directory Structure

/DOC0/TEMP: The directory for storing temporary files

/DOC0/DATA1 : The ZDB file, which contains NE configuration data and version data /DOC0/CFG/zxg10.cfg: OMC IP, and the username/password of the ftp user /DOC0/Exc_Omp.txt: Abnormal records of the OMP board /DOC0/Exc_pp.txt : Abnormal records of peripheral boards /DOC0/Exc_pp.txt.bak: The backup file of the abnormal records of peripheral boards

Internal Use Only

OMP Directory Structure

/IDE0/DATA1: The backed-up ZDB file /IDE0/FTPDATA: The ZDB file stored during data synchronization /IDE0/RELEVER: The version package of the iBSC peripheral boards /IDE0/VERSION: The version package of non-SDR base stations /IDE0/EXCINFO: The abnormal log of boards, being low in priority

Internal Use Only

How to Upload/Download Files in OMP

ftp to OMP: ftp OMP IP Username/password: zte/zte Open the destination directory with the cd path command. Close the interactive mode with the prompt command. Upload or download data with the bin command. Provide the local path with the lcd path command. Upload or download the file name with the put or get command. Upload or download data in batch with the mput . or mget . Command.

Internal Use Only

How to Upload/Download Files in OMP

Use the zxgomcr-ftptool tool of the R9 iOMCR software Path: iOMCRV6.20.614cP001-OMCBV4.00.200m \gsmomcr\ums-clnt\tools\zxgomcr-ftptool

Internal Use Only

Startup Process of OMP

Read the bootcfg.ini file, set the startup mode, and set the IPs of Port OMC2, MAC, mask, and gateway IP. Read the ompboot.inf file, and set the iOMCR FTP IP, username & password, and the relative path for storing the ompcfg.ini file. Upload/download the ompcfg.ini file to/from the iOMCR with the FTP function, and get the specific CPU version data of OMP. Compare the acquired data with the existing version package under the /DOC0/VER directory (filename and CheckSum). If they are the same, load the local version package. If they are not the same, download the new version package with ftp and overwrite the local file, and then reload the new version package. Load the FPGA version file of OMP with the same method at Step 3. After finishing loading CPU and FPGA version, load the ZDB file: Download the ZDB file under the /DOC0/DATA1 directory. If the file does not exist, check whether it is under the /IDE0/DATA1 directory. If it exists, copy it to the /DOC0/DATA1 directory. If it does not exist, the loading fails. The OMP will restart after the timer is timeout.

Internal Use Only

Starting up the Peripheral Board

The peripheral board reads the its own version data from the Specific Version Table/General Version Table in the VerTable.ZDB file, and then compare the data with the existing version in the local flash. If the file name is the same as the CheckSum, it will load the version file in the local flash and starts booting. If they are not the same, the peripheral board will download the specified version package in the VerTable.ZDB from the /IDE0/RELEVER directory of OMP and overwrite the local version package. After the downloading process finishes, the board will load and start the local file. If the specified file does not exist under the /IDE0/RELEVER directory, the startup will fail. If there is no version data about this board in the VerTable.ZDB file, the startup will also fail. In this case, it is necessary to create the general or specific version on iOMCR and activate the version package and reset the board.

Internal Use Only

DIP Switches on the Shelf

TRIB: 3bits, YYYX Rack: 4bits, YYYY Shelf: 3bits, YYYX

Trib ON OFF Rack Shelf

Turning the switch ON means BIT=0, and turning the switch OFF means BIT=1. Currently, the ON bit is above the OFF bit. Y means valid Bit. X means invalid Bit. For each DIP switch, low-order bit is on the left, and high-order bit is on the right (110X means 3, and 100X means 1).

Internal Use Only

DIP Switches on the Shelf

Set the 100 M iBSC by the DIP switch on the shelf backplane Set the Gigabit iBSC by the DIP switch on the shelf backplane or by the RBID board RBID and the DIP switch on the shelf backplane cannot be valid at the same time. The RBID is valid only when all the DIP switches are set as 1 Engineering specifications: When the RBID is available, set the iBSC by the RIBD.

Internal Use Only

DIP Switches on the Shelf

TRIB: The value of the DIP switch on the backplane is an expected value. For TRIB 3, the TRIB switch should be 110X. RACK: The value of the DIP switch on the backplane + 1 is an expected value. For Rack 1, the Rack switch should be 0000. SHELF: The value of the DIP switch on the backplane + 1 is an expected value. For Shelf 2, the Shelf switch should be 100X. The shelf the OMP is in must be set as the second shelf of the first rack, that is, Rack 0, Shelf 1.

Internal Use Only

Control Plane IP

To connect to a board by a probe, a UDPWatch, or other commissioning tools, we must be clear about the control plane IP corresponding to the board. By convention, the DIP switches of the shelf the OMP is in are: DRIB YYY, RACK 0000, SHELF 100X, that is, Shelf 2, Rack 1. The IP of the OMP is fixed as 128.0.31.1 or 128.0.31.9. 128.0.31.1 is the IP of the OMP at Slot 11. 128.0.31.9 is the IP of the OMP at Slot 12. The calculation of the IP of the RPU (the second CPU) on the OMP is the same as that of other boards.

Internal Use Only

Control Plane IP

For a peripheral board, the system will read the TRIB, RACK No., and SHELF No. by the DIP switches on the shelf, and work out the control plane IP address, based on the Slot No. and the CPU No.
BURE AU SHEL F CONTR OL POR /MEDIA T

RACK

SLOT

CPU

MAC : IP:

PREFI X 128
The part reserved, clear The ssupplementary part that needs to be calculated through physical boards Distinguish the control plane and the user plane. 0: user plane, 1: control plane The fixed header. 24 bits for MAC addresses, and 8 bits for IP addresses

Internal Use Only

Control Plane IP

The formula for calculating the Control Plane IP of a CPU: IP=128 . TRIB*16+(RACK-1) . (SHELF-1)*32+SLOT NO. (CPU-1)*8+1

OMP/CMP has two CPUs. SPB/SPB2 has four CPUs. CLKG has no CUP. Other boards have only one CPU respectively. Question: What is the Control Plane IP of Slot 9, Shelf 2, Rack 1, TRIB 0? The Control Plane IP (UIM) of Slot 9, Shelf 2, Rack 1, TRIB 0 is 128.0.41.1.

What is the Control Plane IP of the OMP at Slot 12, Shelf 2, Rack 1, TRIB 2? And the RPU IP? The Control Plane IP of the OMP at Slot 12, Shelf 2, Rack 1, TRIB 2 is 128.0.31.9 (fixed). The Control Plane IP of RPU is 128.32.44.1.

Internal Use Only

Control Plane IP

Query the Control Plane IP of a CPU by the Device Test function on the ISMG.

Prerequisite: The link between the ISMG and board is established. Choose View > Test Management. Right-click the target board on the Test Management tree, and choose Execute Instant Test . Set Test Type as BSC Board Test, and click OK. The test result will display the Control Plane IP.

Internal Use Only

Contents

Rudimentary Knowledge
iBSC Single-Server Commissioning Steps Configuration of Basic iBSC Data

OMP Board Commissioning

Peripheral Board Commissioning

Internal Use Only

Purpose and Flow

Purpose

To configure the basic data correctly To make sure all boards run properly To make sure all boards are of the specified versions To establish links between OMM and iBSC To make sure the configuration data has been synchronized to the iBSC

Flow
Commission ing preparations Basic data configuratio n OMP Commission ing Peripheral boards commission ing

Internal Use Only

Preparations

Check whether ISMG is available Check whether the network cable of the ISMG and iBSC is connected correctly Prepare the OMP serial port cables Prepare a PC with serial ports and available HyperTermial software Prepare the software package for iBSC commissioning Prepare the ZXG10 iBSC(Vx.xx) Commissioning Guide

Internal Use Only

Contents

Rudimentary Knowledge
iBSC Single-Server Commissioning Steps Configuration of Basic iBSC Data

OMP Board Commissioning

Peripheral Board Commissioning

Internal Use Only

Configuration of Basic iBSC Data

Creating GERAN Subnetwork Creating BSC Managed Element Creating BSC Function Creating BSC Rack, Shelf, and Board Creating the A-interface Data Checking Data Validity

Internal Use Only

Basic Data Configuration

Creating GREAN Subnetwork

User label must be configured. It is usually set as GERAN.

Subnetwork ID must

be configured, with the

value as an integer.

Internal Use Only

Basic Data Configuration

Creating BSC Managed Element

Internal Use Only

Basic Data Configuration

Creating BSC Managed Element

Internal Use Only

Basic Data Configuration

Applying Mutex Right

A managed element can be added, deleted, or modified by only one used at the same time. We can apply, release, or delete the Mutex Right. We can judge the Mutex Right status according to the icon in the front of the managed element.

Internal Use Only

Basic Data Configuration

Creating BSC Function

BSC Function defines Managed Element related parameters. MNC/MCC, TC type support, and GE support cannot be modified once created.

Internal Use Only

Basic Data Configuration

Creating BSC Function

Internal Use Only

Basic Data Configuration

Creating BSC Function

Internal Use Only

Basic Data Configuration

Creating BSC Rack

Internal Use Only

Basic Data Configuration

Creating Shelf

Internal Use Only

Basic Data Configuration

Shelf Configuration Rules

The base station has one resource shelf only

The resource shelf can be configured at any layer. The resource shelf can be configured at any layer The resource shelf is usually configured at Layer 1 and Layer 3. The packet switch shelf is usually configured at Layer 4. The control shelf can only be configured at Layer 2, Cabinet 1. The resource shelf is configured at Layer 1 and Layer 3 of Cabinet 1, and any layer of Cabinet 2. The packet switch shelf is usually configured at Layer 4, Cabinet 1.

The base station has one cabinet only

The base station has two cabinets

Internal Use Only

Basic Data Configuration

Creating Board

Internal Use Only

Basic Data Configuration

Sequence of board configuration:

Control shelf: OMP Board > UIMC Board > other boards Resource shelf: UIMU Board > other boards Packet switch shelf: No requirement for the configuration sequence of UIMC, GLI, and PSN

Internal Use Only

Contents

Rudimentary Knowledge
iBSC Single-Server Commissioning Steps Configuration of Basic iBSC Data

OMP Board Commissioning

Peripheral Board Commissioning

Internal Use Only

OMP Board Commissioning

Purpose

OMP loads correct software version and configuration data with correct boot parameters. OMB can establish link with the ISMG server.

Main Steps

Upload the OMP version and create the ompcfg.ini file.

Connect OMP to the serial port of the PC, and set OMP boot parameters. Check the board status, and find out whether the OMP commissioning succeeds.

Internal Use Only

OMP Commissioning
Uploading Software Version

Open the BSC Software Management tab, and upload the software version one by one. Upload the CPU version (e.g.: IBSC_MPX86_2_MP_P4_V6.20.200F_Z.BIN) Upload the FPGA version (e.g.: MPX862_04_040704_FPGA_109.RBF)

Internal Use Only

OMP Commissioning
Creating the ompcfg.ini File

OMP Type: If the iBSC has only one resource shelf, and the functions of both OMP and CMP are fulfilled by the OMP, please select OMP+CMP+SMP. otherwise, please select OMP.

Internal Use Only

OMP Commissioning
Connecting OMP to the Serial Port of PC

Connecting the commissioning cable

The commissioning cable is a serial port commissioning cable delivered together with iBSC Connect the commissioning port of the OMP (usually, it is the DEBUG2-232 port of the RMPB board) to the serial port of the commissioning PC Commission the HyperTerminal program of the Windows OS of the PC The backup OMP board must be plugged out before the commissioning

Commissioning software

Internal Use Only

OMP Commissioning

Type in 1 to display the 1- Config MP net parameters(only for Omp and Cmp) configuration item. Then, set the following five sub-items one by one.

Config selection: 1 - Set Omp(or Cmp)s Omc Ip and Mac! //Set the OMP IP and MAC 2 - Set Omp Boot Paras! //Set OMP boot parameters 3 - Set OMP Boot Type ! //Set OMP boot mode to Boot from OMC 4- Set Net_Element Bureau No.! //Set the Bureau No. of iBSC 5 - Quit config, return to bootmenu! //Quit configuration, type in 0, and perform OMP reboot 6 - print this help list

Internal Use Only

OMP Commissioning

After the OMP is started up, check the indicator status: the RUN indicator of the OMP CPU on the MPX86 board flashes slowly, and the Alarm indicator is OFF. Type in SCSShowMcmInfo after the HyperTerminal prompt ->, and press Enter to check the process status.

SCSMCProc: End all 69 base process power on sucess.

SCSMCProc: Current Proc InnerState is MASTER SCSMCProc: Current MCM State is WORK value = 1 = 0x1

Type in SCSShowVerInfo after the HyperTerminal prompt ->, and check whether the CPU version and the FPGA version of the OMP are correct. Please refer to 07 ZXG10 iBSC(V6.20) Commissioning Guide for the detailed steps of OMP commissioning.

Internal Use Only

OMP Commissioning
Three frequently-used commands:

SCSShowMcmInfo: Check the running status of OMP SCSShowVerInfo: Check the running version of OMP ifShow: Check the IP of the OMC2 port on OMP

Internal Use Only

OMP Commissioning
Troubleshooting of three common faults

There is no prompt after the HyperTerminal is opened: Type in 3gzte to activate the HyperTerminal. ftp connection timeout occurs when OMP downloads version package from OMM: Check OMP boot parameters, the ompcfg.ini file, and the OMP version package on OMM. OMP reboots repeatedly after the version package is loaded successfully:

Check whether the three ZDB files (CfgTable.ZDB, VerTable.ZDB, and DBVer.ZDB) missed under the /DOC0/DATA1 directory of OMP. Check whether the table structure of the ZDB files matches with the version. Solution: Perform all table synchronization to the iSMG (matches with the iBSC) and generate the three ZDB files, and upload the three files to the /DOC0/DATA1 directory manually.

Internal Use Only

Contents

Rudimentary Knowledge
iBSC Single-Server Commissioning Steps Configuration of Basic iBSC Data

OMP Board Commissioning

Peripheral Board Commissioning

Internal Use Only

Peripheral Board Commissioning

Uploading Version File

Purpose: To upload the version file from the ISMG client to the /tmp/ftp/version/bscX directory on the ISMG server. Classification: Uploading single version file, uploading version files in batch

Internal Use Only

Peripheral Board Commissioning

Uploading Version File

The first + icon is used to load a single version file

The second + icon is used to load version files in batch

Internal Use Only

Peripheral Board Commissioning

Creating General Version File

Purpose: To indicate which version file to load when a board is booted Priority: General Version File is lower in priority than Specific Version File

Internal Use Only

Peripheral Board Commissioning

Adding Version File to NE

Purpose: To upload the version file from the ISMG server to the OMP board Directory of the version file:

iSMG Server: ums-svr/tmp/ftp/version/bscxx OMP Board: /IDE0/RELEVER

Internal Use Only

Peripheral Board Commissioning

Version Activation

Perform version switching. If Reset is selected, the running version of the current board will also be switched, besides the change of version data in the database. If Reset is not selected, only the version data in the database changes, but the board is still in the old version.

Internal Use Only

Peripheral Board Commissioning

Checking the Data of the Running Version

Internal Use Only

Peripheral Board Commissioning

Checking the Data of the Running Version

Check whether the status of both the master board and the slave board has been reported to ISMG Check whether the RUN indicator of the board is flashing at 1Hz Check the alarms of each board in Alarm Management of ISMG Open the BSC Software Management tab, and check whether the running version of each board is the correct version, and make sure no version file is missed The GUP2 board needs both the CPU version file and the DSP version file. If only the CPU version file is loaded, and the DSP version file is missed, user plane faults will occur due to the unavailability of the DSP version file.

Internal Use Only

Peripheral Board Commissioning

Two Common Faults

The version files fail to be uploaded, and the system prompts ftp faults: Check the contents of the hosts file The version files fail to be added to NE, and the system prompts ftp faults:

Check the configuration of ftp in the deploy-gsmomcr01.properties file of the ISMG server (the internal IP of eth6, Port 20021) Check the port mapping status Check whether the port in the umssvr/tools/ftpserver/conf/uep-psl-ftpserver-port.conf file is set as 20021

Internal Use Only

Review

What are the two main directories of the OMP board? Where is the version file of OMP stored? And the version file of the peripheral board? What are the steps of OMP board commissioning? How to check whether the OMP board commissioning succeeds? What are the steps of peripheral board commissioning? How to check whether the peripheral board commissioning succeeds? How to set the DIP switches of the shelf? How to calculate the Control Plane IP? What is the function of this IP

Internal Only