Anda di halaman 1dari 5

For Internal Use Only▲

(GSM) Technical Requisition 20090311-012 Confidential Class: B

SN G20090311-012 (SN. 284) Requisition Type Notice

Subject Notice of Data Validity Inspection in iBSC

Issued by GSM Customer Service Dept. Urgent class Urgent

Marketing & Sales


No. 1, 3, 4, 5 Divisions Operator All
Division
All regional offices, GSM
Issued to Applicable Product ZXG10-iBSC
Customer Service Dept.
Note: the old GSM Technical Notice 20090114-002 (Notice of Data Validity Inspection in iBSC) is invalid.
Take this notice to check the illegal data.
Problem:

In the current version, the data configured in several ways (like GUI, MML, EXCEL import) on the iSMG may be
illegal. By now, the data validity inspection system is not perfect. After the illegal data is synchronized to the
foreground, once OMP and CMP reset, the severe fault of CMP and OMP startup failure will happen.
It is necessary to check the illegal data in advance. Before performing the critical operations such as version
upgrade, check the illegal data in advance as per the following steps.

Inspection:
Use the following two steps to check the illegal data:
1. Use the database script to check the illegal data. Manually modify the illegal data.
2. Use the tool UDPWatch to trace the database subsystem print of OMP and CMP during the whole table
synchronization. Check whether there is other illegal data.
 Use the following steps to check the illegal data with the database script.
1. Upload the data validity inspection script jiancha.sql to the server. Log on the database as per the
following steps, run the script to check the illegal data.
-bash-3.00$ sqlplus uep/uep@gomcr
SQL> set linesize 1024
SQL> spool jiancha.txt
SQL> @jiancha.sql

jiancha.sql

2. After running the script, jiancha.txt will be created in the current directory. Download this file to the local
for viewing. The script checks the following four kinds of illegal data.
(1) The object quoted by the adjacent cell does not exist.
(2) The LAC and CI of the adjacent cell in the adjacent cell table are inconsistent with that of the quoted
object.
(3) The site module ID is inconsistent with cell module ID.
(4) The site module ID is inconsistent with DSP module ID of UPPB board.
After running the script, if the illegal data is found, feed back the check result and backup data of the

Confidential and Proprietary Information of ZTE CORPORATION.


For Internal Use Only▲

configuration set to the First GSM Fault Handling Response Group.


Examples of check result are as follows:
(1) The object quoted by the adjacent cell does not exist.
CONFSETID OMCBSCID SITEID BTSID HORESOBJECTID RELATIONDN
55 51 40 1 1 SITEID=81,BTSID=5
The above data indicate BSC51, configuration set 55, site ID 40, handover and re-selection cell 1
of cell 1. The relation objects SITEID=81 and BTSID=5 do not exist.
There are two reasons for the above condition.
 The relation object does not exist, such as SITEID=81,BTSID=5 in the above table.
 The excel import tool is used on site. When there is redundant space during importing,
the data will be error.
Handle the above two problems in the following ways:
 Check and make sure the relation object does not exist. Delete this adjacent cell.
 Check and make sure the relation object exists. Delete this adjacent cell and re-
configure it.
Perform increment synchronization after modifying the error data.

(2) The LAC and CI of the adjacent cell in the adjacent cell table are inconsistent with that of the quoted
object.
CONFSETID OMCBSCID SITEID BTSID HORESOBJECTID HORES_LAC HORES_CI BTS_LAC BTS_CI RELATIONDN
20 1 1 1 1 1 10012 1 2 SITEID=1,BTSID=2
The above data indicate BSC1, configuration set20, site ID 1, handover and re-selection cell 1 of cell
1, LAC1, CI 10012.
But the LAC and CI of the relation object SITEID=1 and BTSID=2 is 1 and 2.
It is caused by the base station created by the custom template in which the base station
has the adjacent cell.
Delete all the adjacent cell relation of this site and re-create the adjacent cell as per the
correct adjacent relation.
Perform increment synchronization after modifying the error data.

(3) The site module ID is inconsistent with cell module ID.


CONFSETID OMCBSCID SITEID BTSID SITE_MODULE CELL_MODULE
75 21 1 1 4 3
75 21 1 2 4 3
75 21 1 3 4 3
The above data indicate BSC21, configuration set75. The site module ID is 4 but the cell module
ID is 3.
Delete this adjacent cell and re-configure it.
Perform increment synchronization after modifying the error data.

(4) The site module ID is inconsistent with DSP module ID of UPPB board.
CONFSETID OMCBSCID SITEID BTSID SITE_MODULE CELL_DSP_MODULE
69 5 171 1 5 4

Confidential and Proprietary Information of ZTE CORPORATION.


For Internal Use Only▲

The above data indicate BSC5, configuration set69, site ID 171. the UPPB DSP module ID of cell 1
is 4 but this site belongs to module 5. Reconfigure a UPPB DSP of module 5 for the cell.
Perform increment synchronization after modifying the error data.

 Use the tool UDPWatch to trace CMP print to check the other illegal data.
Use the following steps to check other illegal data except the above four kinds of illegal data.
1. Use UDPWATCH to trace DBS and DBSAPP print of all the master OMP and CMP (CMP includes
CPU1 and CPU2). The setting of print is as follows.

Confidential and Proprietary Information of ZTE CORPORATION.


For Internal Use Only▲

2. Initiate the whole table synchronization from the background NM. Observe the print of each CMP and
check whether there is loading failure print.

1073 3/ 5/14:11:42 Table R_3GBA is loading!


1074 3/ 5/14:11:42 Table R_HO is loading!
1075 3/ 5/14:11:42 Table R_RESEL is loading!
1076 3/ 5/14:11:42 [File=x:/ibsc_app/Dbs/dbt/source/DBS_R_HORES.c,Line=257], [LAC=120,CI=120],
Cell NOT Exist in this Module!
1077 3/ 5/14:11:42 [File=x:/ibsc_app/Dbs/dbt/source/DBS_R_HORES.c,Line=257], [LAC=120,CI=120],
Cell NOT Exist in this Module!
1078 3/ 5/14:11:42 Table R_HORES is loading!
1079 3/ 5/14:11:42 Table R_INTF is loading!
1080 3/ 5/14:11:42 Table R_3GHO is loading!
1081 3/ 5/14:11:42 Table R_3GRS is loading!
0508 3/ 5/13:48:23 file:x:/code/DBS/dbms/Manage/source/DBS_P_SSyncRx.c,line:1523;The load table from FileReg
buffer fail!!

The above is the print information of loading failure. It indicates the errors (in red) appear during R_HORES
loading. But other table, like R_RESEL (in blue), indicates the loading succeeds.

If there is table loading error during the loading process, it indicates the illegal data exist. Immediately feed
back the background configuration backup (ztd) and the foreground ZDB file to the First GSM Fault Handling

Confidential and Proprietary Information of ZTE CORPORATION.


For Internal Use Only▲

Response Group. It is prohibited to perform CMP and OMP reset.

Appendix:
The error CMP print:

CMP错误打印.txt

This notice will take effect upon the date of issuing. All of the onsite maintenance engineers shall strictly
carry it out.

Prepared by Chen Qi Date Mar.11, 2009 Reviewed by Yang Yong Date Mar.12, 2009

Wei Fang
Approved by Date Mar.12, 2009 Issued by Date Mar.12, 2009
Guangtuan Guangzhi

Confidential and Proprietary Information of ZTE CORPORATION.