05 ZXG10 BSC (V2.97) Unpacking Inspection Guide

ZXG10 BSC (V2.
97)
Base Station Controller
Engineering Data Setting
Specifications
(V2007-R1.0)
ZTE CORPORATION
ZXG10 BSC (V2.97) Base Station Controller
Engineering Data Setting Specifications (V2007-R1.0)
Planned by: ZTE Global After-Sales Service Center
Compiled by: Zhong Junbiao
Reviewed by: Liu Zike
* * * *
ZTE CORPORATION
Address: ZTE Plaza, Keji Road South, Hi-tech Industrial Park, Nanshan District, Shenzhen, P.R.China
Post code: 518057
Technical support website: http://tsm.zte.com.cn
Hotline: +86 755 26770800 800-830-1118
Fax: +86 755 26770801
* * * *
Legal Information
Copyright © 2007 ZTE CORPORATION.
The contents of this document are protected by copyright laws and international treaties. Any reproduction
or distribution of this document or any portion of this document, in any form by any means, without the
prior written consent of ZTE CORPORATION is prohibited. Additionally, the contents of this document
are protected by contractual confidentiality obligations.
All company, brand and product names are trade or service marks, or registered trade or service marks, of
ZTE CORPORATION or of their respective owners.
This document is provided “as is”, and all express, implied, or statutory warranties, representations or
conditions are disclaimed, including without limitation any implied warranty of merchantability, fitness for
a particular purpose, title or non-infringement. ZTE CORPORATION and its licensors shall not be liable
for damages resulting from the use of or reliance on the information contained herein.
ZTE CORPORATION or its licensors may have current or pending intellectual property rights or
applications covering the subject matter of this document. Except as expressly provided in any written
license between ZTE CORPORATION and its licensee, the user of this document shall not acquire any
license to the subject matter herein.
The contents of this document and all policies of ZTE CORPORATION, including without limitation
policies related to support or training are subject to change without notice.
Preface
This ZXG10 BSC (V2.97) Base Station Controller Engineering Data Setting
Specifications specifies data setting for the ZXG10 BSC (V2.97) engineering to set
software data more normalized and reasonable so that commissioning tests can be
successfully performed, system can run normally, and system failures by these causes
can be reduced. Hence, maintenance can be easier.
ZXG10 BSC (V2.97) Base Station Controller Engineering Data Setting Specifications For Internal Use Only▲
Contents
1 Network Management system configuration..........................................................................................1-1
1.1 Server basic configuration setting......................................................................................................1-1
1.1.1 Server hardware configuration.................................................................................................1-1
1.1.2 The operation system requirements of the server.....................................................................1-2
1.1.3 Planning disk partitions............................................................................................................1-2
1.1.4 The requirement for performance table space and performance index table space of database1-
5
1.1.5 Oracle8.1.7 Enterprise Edition installation..............................................................................1-6
1.1.6 DB2 Universal Database V8.1 installation.............................................................................1-12
1.2 Net management parameter setting..................................................................................................1-12
1.2.1 The requirement and setting for version information.............................................................1-12
1.2.2 Server domain, machine NO. and IP address.........................................................................1-12
1.2.3 Network parameter planning for BSC, client, alarm box and upper level NM.....................1-12
1.2.4 Upper level NM configuration...............................................................................................1-13
1.2.5 Performance parameter and the timer setting.........................................................................1-13
1.2.6 Timer parameter setting..........................................................................................................1-14
1.2.7 The configuration of alarm box and parameter setting..........................................................1-15
1.2.8 The NM user and right management setting..........................................................................1-17
1.2.9 FTP setting..............................................................................................................................1-18
1.3 The server configuration file.............................................................................................................1-18
1.3.1 syscfg.ini file...........................................................................................................................1-18
1.3.2 dbcfg.ini file............................................................................................................................1-19
1.3.3 bsccfg.ini file...........................................................................................................................1-20
1.3.4 Lmfcfg.ini file.........................................................................................................................1-21
1.3.5 Pmcfg.ini file...........................................................................................................................1-22
1.3.6 ampcfg. Ini file........................................................................................................................1-22
1.3.7 define.ini file...........................................................................................................................1-23
Confidential and Proprietary Information of ZTE CORPORATION. i

1.4 Client configuration..........................................................................................................................1-26

1.4.1 Hardware configuration..........................................................................................................1-26
1.4.2 Software configuration...........................................................................................................1-26
2 Board software and hardware Setting....................................................................................................2-1

2.1 board switch and jumper setting.........................................................................................................2-1
2.2 MP software setting............................................................................................................................2-1
2.3 MP LOGON file setting......................................................................................................................2-1
2.4 ZXG10.cfg file setting........................................................................................................................2-1
2.5 TCPIP.CFG file setting.......................................................................................................................2-4
3 Configuration management......................................................................................................................3-1
3.1 Function class of configuration interface...........................................................................................3-1
3.2 The sequence of data configuration....................................................................................................3-1
3.3 Physical resource configuration..........................................................................................................3-1
3.3.1 Information data of MSC..........................................................................................................3-1
3.3.2 Configuring BSC Data..............................................................................................................3-2
3.3.3 Configuring Abis Interface TIC (BSC)....................................................................................3-2
3.3.4 Configuring A-interface TIC....................................................................................................3-2
3.3.5 CSSS7(MTP/SCCP)Protocol timer setting of A interface.......................................................3-3
3.3.6 Allocation of HW......................................................................................................................3-3
3.3.7 MTP board configuration..........................................................................................................3-3
3.3.8 The configuration of A interface...............................................................................................3-3
3.3.9 A interface connection..............................................................................................................3-4
3.3.10 Notice about the connection of ZTE BSC and other MSC....................................................3-5
3.3.11 Physical site configuration......................................................................................................3-9
3.3.12 Radio configuration of BSC...................................................................................................3-9
3.3.13 Configuration of FM rack.......................................................................................................3-9
3.4 Radio resource configuration............................................................................................................3-10
3.4.1 Create cell radio information..................................................................................................3-10
3.4.2 Create trx radio information(neighbor cell)...........................................................................3-10
Confidential and Proprietary Information of ZTE CORPORATION. ii

4 GPRS Data Setting....................................................................................................................................4-1

4.1 Physical Configuration........................................................................................................................4-1
4.1.1 GPRS Function On-off Setting.................................................................................................4-1
4.1.2 HW allocation...........................................................................................................................4-1
4.1.3 BRCH........................................................................................................................................4-1
4.1.4 NSVC........................................................................................................................................4-1
4.2 Radio configuration............................................................................................................................4-1
4.2.1 Configuration environment selection.......................................................................................4-1
4.2.2 Configuration of GPRS cell......................................................................................................4-2
4.2.3 Configuration of channels.........................................................................................................4-2
5 HR Setting..................................................................................................................................................5-1
5.1 Software Configuration Data Setting..................................................................................................5-1
5.1.1 DSP software loading...............................................................................................................5-1
5.1.2 HR General Software Setting...................................................................................................5-1
5.2 Physical Configuration Data Setting..................................................................................................5-2
5.2.1 EDRT Board Changing.............................................................................................................5-2
5.2.2 BSC DSP Type Configuration..................................................................................................5-2
5.2.3 RRM Module Adjustment.........................................................................................................5-3
5.3 Radio Configuration Data Setting......................................................................................................5-3
5.3.1 FR/HR Priority Setting.............................................................................................................5-4
5.3.2 HR Configuration.....................................................................................................................5-4
5.3.3 Dynamic HR Configuration......................................................................................................5-4
Appendix A Abbreviations............................................................................................................................A-1
Confidential and Proprietary Information of ZTE CORPORATION. iii

一 Network Management system
configuration
一.1 Server basic configuration setting
一.1.1 Server hardware configuration
To configure server hardware, you need to take database, CPU process capability,
number of managed objects, and response time of system to user order into
consideration so that the system can perform in optimal configuration.
Table Network Management system configuration-1 shows the typical server hardware
configuration. When designing actual deployment project, you can change the
parameters according to system-related factors and system performance so that the
system can work in different environments. For example, when the number of managed
TRXs is increased, you can increase the CPU frequency, add CPUs and enlarge
memory.
Table Network Management system configuration-1 Typical System Hardware Configuration (Main Parts)
System Configuration capacity

configure Small Moderate Large Larger
Number of
1 set 2 sets 2 or 3 sets ≥ 3 sets
servers
400 MHz*4
400 MHz*4
CPU 400 MHz*2 400 MHz*8 ≥ 400 MHz*8
400 MHz*4
400 MHz*8
1 GB
1 GB
Memory 512 MB 2 GB ≥ 2 GB
1 GB
2 GB
Disk 40 GB 80 GB 120 GB ≥ 120 GB
Number of In the range of

Smaller than In the range of 20,000
managed 150,000 and Greater than 400,000
20,000 and 150,000
MOs 400,000
Confidential and Proprietary Information of ZTE CORPORATION. -1-

ZXG10-BSC (V2.97) Base Station Controller Engineering Data Setting Specification For Internal Use Only▲
System Configuration capacity

configure Small Moderate Large Larger
Based on large capacity
The configuration is configuration, this configuration is
The configuration
for dual-server system. for three-server system.
is for dual- or three-
The It is recommended to 1) Extend each part (vertically
server system. It is
configuration is use Redundant Arrays extension)
Remarks recommended to use
for single-server of Inexpensive Disks 2) Add more severs (horizontal
RAID to enable
system. (RAID) to ensure high extension)
high speed and high
speed and high reliable 3) RAID is required to enable
reliable data access.
data access. high speed and high reliable data
access
Note: 1) The moderate-, large-, and larger-capacity servers in the table must Sun or Fujitsu servers. The small-capacity servers can be Sun servers,
Fujitsu servers or PCs.
2) In actual design, the disk capacity must be increased for the RAID. The disk capacity is related to the disk type.
一.1.2 The operation system requirements of the server
OMCR V2 system requires Solaris with the patch“Generic_108528-29” .e.g. “SunOS

wgwy11 5.8 Generic_108528-29 sun4us sparc FJSV, GPUSC-M”。
If lower than that, it is necessary to upgrade the system.
一.1.3 Planning disk partitions
Disk partition is based on the number and capacity of hard disks, so the partition
planning varies with disk size. It is required to make RAID1 to all the disks.
The requirement is showed as follow tables from 1-2 to 1-4
Confidential and Proprietary Information of ZTE CORPORATION. 2

Table Network Management system configuration-1 disk partition (1)
Logical disk
Physical disk disk slice File system size
[after RAID1]
0 / 7096M
1 Swap 4096M
3 /var 5060M
2×73G 1×73G 4 /metadb 72M
disk1
5 /opt 3072M
6 /datafile 23552M
Remaining size of the
7 /export/home
disk
0 / 7096M
1 Swap 4096M
3 /var 5060M
4 /metadb 72M
disk1
5 /opt 3072M
4×73G 2×73G 6 /datafile/u01 4096M
7 /export/home
disk
0 /metadb 72M
disk2 Remaining size of the
1 /datafile/u02
disk
0 / 7096M
1 Swap 4096M
3 /var 5060M
4 /metadb 72M
disk1
5 /opt 3072M
6 /datafile/u01 3072M
6×73G Remaining size of the
3×73G 7 /export/home
disk
0 /metadb 72M
1 /datafile/u02
disk
0 /metadb 72M
1 /datafile/u03
disk

Logical disk
Physical disk disk slice File system Size
[after RAID1]
0 / 7096M
1 Swap 8192M
3 /var 5060M
disk 1 4 /metadb 72M
5 /opt 3072M
7 /export/home
disk
8×73G 4×73G
0 /metadb 72M
disk 2 Remaining size of the
1 /datafile/u01
disk
0 /metadb 72M
1 /datafile/u02
disk
0 /metadb 72M
disk 4
1 /datafile/u03 v
0 / 7096M
1 Swap 8192M
3 /var 5060M
4 /metadb 72M
disk 1
5 /opt 3072M
2×146G+4×73G Remaining size of the
1×146G＋2×73G 7 /export/home
disk
0 /metadb 72M
1 /datafile/u02
disk
0 /metadb 72M
1 /datafile/u03
disk
10×73G 5×73G 0 / 7096M
1 Swap 12288M
3 /var 5060M
5 /opt 3072M
7 /export/home
disk

Logical disk
Physical disk disk slice File system Size
[after RAID1]
1 /datafile/u01
disk
0 /metadb 72M
1 /datafile/u02
disk
0 /metadb 72M

disk 4
1 /datafile/u03
disk
0 /metadb 72M
1 /datafile/u04
disk
Logical disk Slic

Physical disk disk File system size
[RAID1 后] e
0 / 7096M
1 Swap 12288M
3 /var 5060M
4 /metadb 72M
disk 1
5 /opt 3072M
7 /export/home
disk
2×146G+6×73G
1×146G＋3×73G 0 /metadb 72M
1 /datafile/u02
disk
0 /metadb 72M
1 /datafile/u03
disk
0 /metadb 72M
1 /datafile/u04
disk
一.1.4 The requirement for performance table space and performance index table space
of database
To the V.2.52 or higher class, the following requirements must be satisfied:
1. The performance table space must be 1G at least without any data.

2. The performance index table space must be 600M at least without any data.
3. The ratio between the space occupied by the data in the performance table
space and that in the performance index space must be 8:1
一.1.5 Oracle8.1.7 Enterprise Edition installation
Required disk space: 500 MB for system partition, 3 GB for Oracle main directory, and
8 GB for database table space files.
一.1.5.1 Oracle8.1.7 database parameter adjustment
Note:
1. database instance parameter adjustment
2. database compatibility adjustment
3. the emender to the BUG that will cause 4031 error in DIF
4. database rollback segment adjustment
5. database log space adjustment
 Database instance adjustment
1． Calculate the available memory
To “integrated server”．
Database instance available memory ． physical memory - (TRX

NUM×0.3MB + 100MB)
to “independent DB server configuration”．
Database instance available memory ． physical memory - (100MB +

100MB)
The command to check the memory is:
$/usr/platform/sun4us/sbin/prtdiag
2． Changing the parameter
Oracle instance
adjust five main parameters according to the available memory (db_block_size

is 8192) ．
Parameter Name Description

db_block_buffers Indicates the size of the data buffer area
shared_pool_size Indicates the shared SQL and PL/SQL statements
sort_area_size Indicates the data sorting area
Indicates the area reserved during acquiring data, and the
sort_area_retained_size
number of sort_area_size/concurrent queries
Indicates the buffer recorded in a log (it should be multiples of
log_buffer
db_block_size)
db_block_size Indicates the size of data block
processes Indicates the processes
You can find out the row firstly meeting the condition from the bottom to the
top in the following table, according to the calculated available memory. Then
log in as an oracle user and modify the file
$ORACLE_BASE/admin/omc/pfile/initomc.ora by changing the above-
indicated parameters as the data in this line. (Since the 32-bit oracle only can
use 1.7GB memory, the max memory in the following table is 1.7GB)
Available db_block_b shared_pool sort_area_siz sort_area_re

log_buffer
memory uffers _size e tained_size
>=128MB 10000 8000000 8000000 2000000 3276800
>=256MB 20000 20000000 16000000 4000000 6553600
>=400MB 30000 20000000 33000000 8000000 13107200
>=512MB 40000 33000000 67000000 16000000 13107200
>=700MB 50000 33000000 100000000 25000000 26214400
>=1GB 80000 65000000 134000000 33000000 26214400
>=1.2GB 90000 65000000 200000000 50000000 40960000
>=1.5GB 120000 65000000 200000000 50000000 40960000
>=1.7GB 130000 65000000 200000000 50000000 40960000
If the Large_pool_size parameter is set, the parameter value must be the

maximal value of other pool_size.
Note:
After the setting, you need to determine whether it is valid. Run the SQL script
below as the sys user to check whether the output meets the condition contained
in “[]". If it meets, that means the modification is valid; otherwise, you need to
readjust the parameters.

select decode(pool, NULL, 'log data buffers', pool) "Buffer(Pool) Name",

sum(bytes) "Size"
from v$sgastat
group by pool;
select 1 - sum(decode(name, 'physical reads', value, 0))

/(sum(decode(name, 'db block gets', value, 0))
+sum(decode(name, 'consistent gets',value, 0)))
"Data Buffer Hit Ratio[>.95]"
from v$sysstat;
select 1-sum(getmisses)/sum(gets) "Directory Hit Ratio[>.85]"

from v$rowcache;
select 1-(sum(reloads)/sum(pins)) "Procedure Hit Ratio[>.95]"

from v$librarycache;
select b.value/(b.value + a.value) "Memory Sort Ratio[>.95]"

from v$sysstat a, v$sysstat b
where a.name = 'sorts (disk)' and
b.name = 'sorts (memory)';
select a.value "Redo log Retries[inc near 0]"

from v$sysstat a
where a.name ='redo buffer allocation retries';
 Adjustment of database compatibility
Execute the commands below to modify the parameters in the initomc.ora file
(if the related statement does not exist, add it).
compatible = “8.1.0.0.0”
query_rewrite_enabled=true
query_rewrite_integrity=trusted
 emender to the BUG that will cause the -4031 error in DIF
Execute the commands below to modify the parameters in the initomc.ora file
(if the related statement does not exist, add it).
_db_handles_cached=0
 Add the database rollback section

Script name．modify_rollback.sql
Purpose: To extend the rollback section of the oracle database and avoid the
situation that the rollback section is insufficient in use during the running of the
OMCR server.
Execution steps:
$sqlplus internal/oracle
sqlplus>@modify_rollback.sql;
ORACLE
Extend the rollback section of the

ORACLE database modify_rollback.s
ql
 Adjustment of the database log space
Follow the methods below to modify the log file size from 1,200K to 80M, and
it is recommended to perform the operation when the office traffic is low:
(1) Log in to the database as the sys user through sqlplus. Find the number of the
existing log group by querying the dynamic view. To implement it, execute the
following sql statement:
SQL> select g.GROUP#,g.STATUS,f.MEMBER from V$LOG g,V$LOGFILE

f where g.GROUP#=f.GROUP#;
For example, the output result may be as follows:
GROUP# STATUS MEMBER

---------------------------------------------------------------------------------------------
1 ACTIVE /oracleapp/u02/oradata/omc/redo01.log
2 CURRENT /oracleapp/u02/oradata/omc/redo02.log
3 INACTIVE /oracleapp/u02/oradata/omc/redo03.log
In the query result, the GROUP# field is the number of the log group. This
example includes three log groups, which are respectively group 1, group 2 and
group 3. The MEMBER field indicates the log file in a log group, including the
absolute path and file name. The STATUS field shows the current update status
of a log group, which may be ACTIVE, CURRENT, or INACTIVE.
(2) Create three new consecutive log groups with the numbers closely following 3
to increase the log file size to 80M. At the same time, please make sure that the
new log file and original log file are located in the same directory. If the
original log file is stored in the directory /oracleapp/u02/oradata/omc/, run the
sql statement as follows:
SQL>ALTER DATABASE ADD LOGFILE GROUP 4

('/datafile/u02/oradata/omc/redo04.log') SIZE 80M;

('/datafile/u02/oradata/omc/redo02.log') SIZE 80M;

('/datafile/u02/oradata/omc/redo06.log')SIZE 80M;
Otherwise, replace /oracleapp/u02/oradata/omc/ with the absolute path name

that is queried in step
(3) Force the active log groups and current log groups to enter the newly created
log groups 4, 5 and 6, and execute the sql statement as follows:
SQL>alter system switch log file;
Then immediately check the current active state of each log group:
SQL>select g.GROUP#,g.STATUS,f.MEMBER from V$LOG g,V$LOGFILE f

where g.GROUP#=f.GROUP#;
The output may be as follows:

------------------------------------------------------------------------------------------
5 UNUSED /oracleapp/u02/oradata/omc/redo05.log
Repeat the above two sql statements several times until the states of all the
original three groups (groups 1, 2 and 3) are INACTIVE like below:

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

(After repeated executions of SQL>alter system switch logfile;, the states of log
groups 1, 2 and 3 are changed as INACTIVE, but those of groups 4, 5 and 6 are
respectively current, unused and inactive. But this has no impact on the
following steps. After success of upgrade, you will find the states of groups 4, 5
and 6 are changed as ACTIVE.)
(4) Delete the original 1200K log groups as follows:
SQL>ALTER DATABASE DROP LOGFILE GROUP 1;
Note: Only the log groups whose states are INACTIVE can be deleted
successfully.
(5) Delete the old log files according to the log file names queried in step (1).
Perform the operation as the oracle user, as follows
rm /oracleapp/u02/oradata/omc/redo01.log
一.1.5.2 ORACLE Net8 configuration
In the database server． tnsnames.ora is as shown ins．
OMC =
(DESCRIPTION =
(ADDRESS_LIST =
(ADDRESS = (PROTOCOL = TCP)(HOST = Host)(PORT = 1521))
(CONNECT_DATA =
(SERVICE_NAME = omc)
Replace the Host with the machine name of database server.

一.1.6 DB2 Universal Database V8.1 installation
Reserve disk space ． DB2 main partition reserves 270M~700M ． database table space
partition reserve 8G at least.
一.2 Net management parameter setting
一.2.1 The requirement and setting for version information
1. BSCV2.97 and OMCRV2.97 must be used together
2. BTSV3 series only can be used with BSCV2.97 series.
3. BSCV2.97 and OMCRV2.97 release are compatible with all the BTS releases.
一.2.2 Server domain, machine NO. and IP address
1． NM domain NO.．1~254, integer.
2． Machine NO.．128~139, integer.
3． IP address: IP for the server.
4. The IP address set in the client must be the same as that in the server .
一.2.3 Network parameter planning for BSC, client, alarm box and upper level NM
一.2.3.1 IP planning rule for MP of BSC
1． IP addresses for all the MP of BSC should in the same subnetwork.
一.2.3.2 Planning rule for OMCR, alarm box and client
1. Planning rule for OMCR:NM system make sure that the communication among
OMCR,MP and client is normal.
2. Planning rule of alarm box:
Alarm box connects with the client , it is required that the IP address must be in
the same subnetwork with that of the client. Alarm box communicates with the
client in the peer to peer way.
Else, it is also right as follows:
The client has two IP addresses, one for communicating with the server ,the
other for the alarm box. In this way, the two IP addresses need not be in the
same subnetwork.

3． Planning rule for client: the communication between the client and alarm box is
normal.
一.2.4 Upper level NM configuration
1. The directory where the installation script is:
China Mobile．/export/home/omc/sql/pnms/yidong/
China Unicom．/export/home/omc/sql/pnms/liantong/
2. Fmmgr.ini configuration．
[NAF]/Start
If any NM, set the parameter 1,otherwise set the parameter 0.
[NAF]/IP
The IP address for the NM server, set the parameter circumstantial.
[NAF]/Port
The port receiving the real-time alarm, set the parameter circumstantial.
一.2.5 Performance parameter and the timer setting
一.2.5.1 Delete the log periodically
In $OMCHOME/omcboot/omcclean file, the operation for deleting the log several days
ago is as shown ins:
find /export/home/omc/tmp/log -name "*.log" -mtime +3 -exec rm -fr {} \;
find /export/home/omc/tmp/mplog -name "*.log" -mtime +7 -exec rm -fr {} \;
find /export/home/omc/tmp/pmmeas -name "*.gz" -mtime +2 -exec rm -fr {} \;
cd /export/home/omc/tmp/ftp && find . $ ! -name . -prune $ -type f -mtime +3 -exec

rm -fr {} \;
#find /export/home/omc/tmp/pmmeas/ -name "*.dat" -mtime +3 -exec rm -fr {} \;
The meaning of each line :
(1) delete the log 3 days ago in the directory /export/home/omc/tmp/log
(2) delete the MP log 7 days ago in the directory /export/home/omc/tmp/mplog
(3) delete the backup data 2 days ago in the directory /export/home/omc/tmp/pmmeas

The operation is valid only after activating the performance backup function
(4) delete the temporary data 3 days ago in the directory /export/home/omc/tmp/ftp
Note:
(1) add“#” in front of a line , it can disable a specific function.
(2) If there are thousands of files ,first move the file ,then start the OMCR
(3) modify the number in the command to set the period of saving the data
(4) the command execute every morning by default, it also can be changed in the
file $OMCHOME/conf/croncfg.ini
一.2.6 Timer parameter setting
一.2.6.1 The setting for synchronizing the clock both in the MP and client
1． Make sure the file croncfg.ini, esos and omciniread.pl in the directory
$HOME/conf
2． Make sure the file croncfg.ini is UNIX format, that is ,opening it with VI, there
is no ^M.
3． croncfg.ini can be modified.
4． all the three files are belong to OMC
5． The method of setting the clock both in the MP and client．
(1) recover the command line in the file croncfg.ini．
#0 0 -1 -1 -1 -1 sh $HOME/conf/esos 5
modify．
0 0 -1 -1 -1 -1 sh $HOME/conf/esos 5
(2) active it in the following way．
Restart the server or
omckill -HUP pid.10
(pid is the PID for cron process ． use the command omcps | grep CRON to
check)
6． Notes．
(1) check the log for OMCCRON to make sure that the setting is active

(2) if synchronize the clock ,it will be recorded in the $HOME/conf/esos.log
(3) the command to set the clock is ESOS, to check the clock is ESOF.
(put help:esos;or help:esof;to get the detail information)
一.2.7 The configuration of alarm box and parameter setting
一.2.7.1 Client file fmwsf.ini
The file is in the directory:$OMCHOME\conf\Chinese(Chinese version) ,or

$OMCHOME\conf\English(English version) .There are some contents．
[ALMPLATE]
OmcrFlag=0
SysPrd=100000
EBssId=0
Trace=0
AlmLevel=1&2&3&4
IP1=0.0.0.0$0.0.0.0
IP2=0.0.0.0$0.0.0.0
IP3=0.0.0.0$0.0.0.0
IP4=0.0.0.0$0.0.0.0
IP5=0.0.0.0$0.0.0.0
All these are for alarm box ,notes．
 OmcrFlag．monitor the OMCR alarm or not. 0 stand for no;1 stands

for yes. Usually set 0,stand for doing not monitor the alarm.
 SysPrd．the synchronization period(100ms) ,do not modify.
 EbssId ． reserved parameter, the number for the monitored BSC,0

stands for all the BSS,0 is default, NULL stand for none ,do not
modify.
 Trace．stand for print the log or not,0 is default.
 AlmLevel．stand for the level,1&2&3&4 is default, do not modify.
 IPx (IP1．IP2．IP3．IP4．IP5) ．stand for the IP address, one client

can connect 5 alarm boxes at most. The IP address on the left of

“$”stand for the address of the alarm box chip, the one on the right
of “$”stand for the address delivered by the client, before use
modify the IP first, the detail information is in the step 2.
一.2.7.2 IP address for the alarm box
(1) the ip for the chip and client must be in the same subnetwork. Put the IP for the
chip on the left side of the “$”. If don’t get the IP first ,it need to burn it on the
site.
(2) if use several alarm box at the same time, the MAC address must different ,if
not, need burn the address again .
一.2.7.3 Connect the cable of alarm box
一.2.7.4 Start the process:fmpc.exe
(1) configure the file syscfg.ini．
(2) note the follow field:
[SYSCFG]
StartAlmplate = 0
StartAlmplate stand for whether start the alarm box process with the uisf or not.
0 stand for no;1 stands for yes. the default is 0, if want start the alarm box ,set it
is 0.
(3) when finish the configuration file and start the uisf ,the fmpc.exe will start
automatically. If everything is ok, there is a process fmpc.exe (marked blue) in
the list as follows.

The process of alarm box
一.2.8 The NM user and right management setting
一.2.8.1 user group and user configuration
for example．
1． add user group
groupadd [–g gid] omc
gid is an integer, it is recommended that gid should be more than 200.
2． add user
useradd –gomc –d/export/home/omc –m –c “User for omcr running” [-u uid]

omc
passwd omc
uid is an integer, it is recommended that uid should be more than 200.
useradd –gomc –d/export/home/omc/tmp/ftp –c “User for omcr ftp” [-u uid]

FtpUser
notes: no –m option.
passwd ftpuser
uid is an integer, it is recommended that uid should be more than 200 and be
different with uid of omc user.

If the user and the user group already exist, for example, expand one server to two, the
simple way is deleting the original user and user group ,deleting the directory
/export/home/omc , then recreate the user and user group.
一.2.9 FTP setting
The FTP user name and password should be same with that in the FTP server.
一.3 The server configuration file
一.3.1 syscfg.ini file
As the server critical configuration file, syscfg.ini sets such parameters as server
number, NM domain number, IP address and start processes.
Server number, NM domain number, and IP address must be configured according to

network planning requirements.
For a multi-server system, the NMDomain must be the same value on all servers while
the MNo must be different values.
For example:
[LOCAL]
Server = 1
MNo = 131
NMDomain = 198
NMDomainAlias = Domain198
IP = 10.61.113.80
MNo: OMCR server number.
NMDomain: OMCR server NM domain number.
NMDomainAlias: OMCR server NM domain alias.
IP: OMCR server IP address.
According to the user needs, the log parameters are configured as follows:
[SYSCFG]
Trace =1
TracePrint = 0

TraceMode = 2
TracePath =/export/home/omc/tmp/log
TraceLev = 1
Environment = GPRS
Trace: To enable process log recording, set it to 1; to disable process log recording, set
it to 0.
TracePrint: To enable process log display on the server, set it to 1; to disable process
log display on the server, set it to 0.
TraceMode: Accept the default setting.
TracePath: Set the full path for saving logs.
TraceLev: Set the level for recording logs. Only one level is supported at present. It is 1
by default.
Environment: If the server does not support GPRS configuration, set it to GSM; if the
server does not support GPRS configuration, set it to GPRS.
一.3.2 dbcfg.ini file
As the file for configuring link between server and database, dbcfg.ini sets database
version, user name and password.
For a multi-server system, all dbcfg.ini are identical.
The parameters that require modification are DBVERSION, USERNAME and

PASSWORD.
[DATABASE]
DBMSTYPE = oracle
DBINSTANCE = OMC
DIFVERSION = V2.0
DBVERSION = Build 97c - 2.97.000c
USERNAME = omc
PASSWORD = omc
USERNAME = omc@omc
PASSWORD = omc

DBMSTYPE ． Database type. If the database is Oracle, set it to ORACLE; if the

connected database is DB2, set it to DB2.
DBVERSION．Database version.
USERNAME ． Database user name and connection string. Use a symbol (@) to
separate the user name and the connection string.
PASSWORD．database password
一.3.3 bsccfg.ini file
Bsccfg.ini configures the link between the server and foreground. This file is
configured on Application Server (AS) only.
Parameters need to be configured include BSCNum, BSCID, ModuleNum,

LocalModuleNum, and IP address and ModuleID.
[GENERAL]
BSCNum = 1
# Number of BSCs in each MP supporting split
MComBsc = 1
# BSC1: Local BSC. All are local modules.
[BSC1]
#BSC ID．that is the Network Element ID.
BSCID = 130
IsRemote = 0
# Number of modules in the BSC.
ModuleNum = 2
# Number of local modules in the BSC.
LocalModuleNum = 2
# IP addresses of the module: the first one is the IP address of the left MP and the
second one is that of the right MP.
IP1 = 192.169.132.1 192.169.132.33
IP2 = 192.169.132.2 192.169.132.34

IP3 = 192.169.132.3 192.169.132.35
IP4 = 234.234.43.3 234.34.34.34
# Foreground received and sent process IDs.
BmfRecePno = 90
BmfSendPno = 91
# Information of each module. The first module must be the central module, that is
module 1.
ModuleID1 = 1
ModuleID2 = 2
ModuleID3 =9
ModuleID4 = 5
BSCNum．Number of foreground BSCs.
BSCID．Foreground BSC ID.
ModuleNum．Number of foreground modules.
LocalModuleNum: Number of foreground local modules.
IP address: IP address of the foreground.
ModuleID: Foreground module ID.
一.3.4 Lmfcfg.ini file
Lmfcfg.ini configures FTP user name and password on server.
For a multi-server system, the value of FtpUserName must be identical on all the
servers, so must that of FtpPassword.
Parameters need to be configured include:
[FTPINFO]
FtpUserName = ftpuser
FtpPassword = ftp123
FtpUserName: FTP user name.
FtpPassword: FTP password.

一.3.5 Pmcfg.ini file
Pmcfg.ini configures files relative to performance management parameters.
Parameters need to be configured include LocalMeasFilePath, HistoryDataFilePath and

ImpDataFilePath.
[BAFINFO]
LocalMeasFilePath = /export/home/omc/tmp/pmmeas
[DATABAKUPINFO]
HistoryDataFilePath = /export/home/omc/tmp/pmhist
ImpDataFilePath = /export/home/omc/tmp/pmhist
LocalMeasFilePath: Full path for performance test data files.
HistoryDataFilePath: Full path for history data files.
ImpDataFilePath: Full path for imported files.
一.3.6 ampcfg. Ini file
Ampcfg.ini configures files relative to process management parameters.
The [LOAD] section in ampcfg.ini on the database server is as shown ins:
[LOAD]
MaxLoad = 1
Load1 = DB
[DB]
MaxTakeover=2
Takeover1 = COM
Takeover2 = AP
The [LOAD] section in ampcfg.ini on the application server is as shown ins:
[LOAD]
MaxLoad = 2 Load1 = COM
Load2 = AP
Apd:
MaxTakeover = 1

Takeover1 = DB
MaxTakeover: sets the migration function. The value range is 0–2. To disable the
migration function, set it to 0; to enable the migration function with the module that
Takeover1 specified started, set it to 1; to enable the migration function with the
modules that Takeover1 and Takeover2 specified started, set it to 2.
The migration function is available in dual-server system. If the server breaks down or
the network is disconnected when the server is running, the other server automatically
starts the module that should have been running on the peer server to ensure the normal
running of the OMCR (V2) server. For example, if the DB server fails, the AP server
starts the processes in the DB module automatically to ensure the normal running of
the OMCR (V2) server. Other items in ampcfg.ini can be kept unchanged.
一.3.7 define.ini file
The parameters that can be modified include:
1． define schema． the number of cells managed by the server, the default value is
1024.
2． define language．omcr database language．--1.chinese(default)．--2.english.
3． DATABASE． the name of the databse
4． TABLESPACEPATH．Path of the OMCR table space to be created. If the path

is null, the table space will be created in different directories. Parameters
MSPACEDIR, FMSPACEDIR, P MSPACEDIR, MISCSPACEDIR, and
TESTSPACEDIR must be set as follows:
define cmpath='';
define fmpath='';
define pmpath='';
define miscpath='';
define testpath='';
define temppath='';
define cbcpath='';
5. By modifying the parameter ,it can change the size of the specific table space.
For example:
--omcr database setup parameters

--omcr management size.
--managed cell number,default 1024.
define schema=200;
--omcr database language.
--1.chinese(default)
--2.english
define language=1;
--omcr office definition.
--1.telecom(default)
--2.unicom
--3.paktel
define office=1;
--omcr database username.
--default OMC
define dbuser=OMC;
--omcr database user password.
--default omc
define dbpasswd=omc;
--omcr database sys password.
--default oracle
define syspasswd=oracle;
--omcr database servicename.
--default omc
define dbname=omc;
--omcr server disk definition,standard partition.
--1.one disk
--2.two disk(default)
--3.three disk

--3.three disk
--4.four disk
--5.five disk
define disknum=2;
--omcr database tablespace path, which disables disknum.
--all data files created under this parameter.
--default ''
define tablespacepath='/oracleapp/u02';
--compatible parameters, which used under old version.
--when these parameters all set and tablespacepath
--set null, disknum becomes disable and all data files
--created under these parameters.
--default ''
define cmpath='';
define fmpath='';
define pmpath='';
define miscpath='';
define testpath='';
define temppath='';
define cbcpath='';
--omcr database upgrade parameters
--month of the data in pm basicm measure tables reserved during upgrade,
--default 1 means reserve one month data
define pmbasicsavetime=1;
--month of the data in pm middle measure tables reserved during upgrade,
--default 3 means reserve three month data
define pmmidsavetime=3;
--month of the data in pm common measure tables reserved during upgrade,

--default 0 means reserve no data
define pmcomsavetime=0;
--whether the time-consuming scirpt will run in the upgrade,
--default Y means run,
--N means the time-consuming scirpt will run separately after the upgrade
define timeconsumeexec=Y;
note :the installation in the ZXG10 OMCR(V2.97):
log in the OMCR server as the omc user
$perl setup.pl
一.4 Client configuration
一.4.1 Hardware configuration
PCs are used as clients. The hardware of the client must contain a CPU running at 800
MHz or faster, a hard disk of 10 GB or larger, and a memory of 128 MB or larger.
一.4.2 Software configuration
一.4.2.1 Requirements for OS
Windows 2000 or XP
一.4.2.2 MS OFFICE requirement
Excel 2000 and word 2000 or above
一.4.2.3 Software tools
Install the FTP tools, NETTERM,PCANYWHERE, LMT and so on
一.4.2.4 syscfg.ini
[LOCAL]/Mno
Machine NO. , it is a number between 140． 254,if there are several clients,the number
of each client should be different.
[LOCAL]/IP

IP address for the client.
[LOCAL]/DOMAINNUM
Multi-domain number. It doesn’t refer to the daisy-chain, but the multi-NM

configuration, the default value is 1.
[DOMAINn]/ALIAS
Server alias
[DOMAINn]/SvrNum
The number of the servers in the server group
[DOMAINn]/SvrMNoX
The number of a specific server , which match with the setting of the server.
[DOMAINn]/SvrIPX
The IP address of a specific server, which match with the setting of the server.
[SYSCFG]/Trace
The same as that of the server in the syscfg.ini file
[SYSCFG]/TracePath
[SYSCFG]/TraceLev
[SYSCFG]/StartAlmplate
Start the alarm box process with the client or not., default is 0(do not start) . If there is
an alarm box ,it must be 1.

二 Board software and hardware Setting
二.1 board switch and jumper setting
Please refer to the document:． ZXG10 BSC(V2.97) base station controller manual． .
二.2 MP software setting

Upload the MP software to the MP and change its name to zxgbsc
二.3 MP LOGON file setting

Enter the directory C:\USER\SUPER\PROG , remove the read only and hidden
attribute with the command “attrib’. modify the file C:\USER\SUPER\PROG\LOGON
to ． “ ． sb ． version/zxgbsc” , after that add the read only and hiden attribute. The
command is as shown ins:
attrib –h –r C:\USER\SUPER\PROG\LOGON
二.4 ZXG10.cfg file setting

The path of the configuration document is \\CONFIG\ZXG10.CFG; the configuration
statements in the configuration document are case insensitive but the number of spaces
in the character string will affect configuration retrieval.
Entries in the configuration document have no precedence; the system with un-
configured options will initialize then according to the default value.
Description of configuration items

Table Board software and hardware Setting-4 ZXG10.CFG Configuration Variable
Name of
Configuration Meaning Supplementary Description
Variable
Whether to conduct monitoring of the The captured information will be saved in
TICK TRAP
process operation duration, defaulted as 0 \TRACE\MSGTRAP.LOG document
Associate the above switches; the capture threshold
Process operation capture threshold,
TICK LIMIT should not be less than 2; otherwise the system will
defaulted as 20
crash and reset due to over- frequent write-document
TRAP MSG Maximum length of the recorded The message body part beyond this threshold will be
LEN message upon capture, defaulted as 100. cut off.
Monitored task bitmap, defaulted as Bit 0~7 respectively represent No.1~8 scheduling
TRAP TASK
0XFF tasks.
System information is saved in the shared memory
board so that useful information can be recorded in
Whether to save the system operation
REG SMEM document \TRACE\POWERON.LOG in case of re-
information into SMEM, defaulted as 1
power-on. If the switch is shut off, then the information
recorded in the record document is invalid.
RESET ON Whether to reset MP when there are The errors here refer to infinite loop or over-frequent
ERROR errors, defaulted as 0 operation errors.
The threshold of CPU full-load operation can enhance
the system’s shock resistance capability; but if the
system discovers infinite loop errors, it will not meter
RESET TIMES MP overload times in case of reset,
but directly reset. The threshold will be used by the
LIMIT defaulted as 3
memory resource monitoring part at the same time.
When the memory resource consumption passes this
threshold, the system will be automatically reset.
PROC MANY Scheduling process ManyRun capture
RUN threshold, defaulted as 13000
TASK MANY External task ManyRun capture
RUN threshold, defaulted as 13000
OPEN TRACE Whether this flag is opened can control the function
Process tracking flag, defaulted as 0
FLAG implementation of the process monitor.
When the peripheral module TCP communication is
Global ID; whether TCP can use
TCP ROUTE interrupted, open this flag bit can forward
forward, defaulted as 0
communication through the central module.
Signaling error print switch, defaulted as
SPS PRINT Control some frequently-printed error information.
0
PRINT ERROR Print error storage switch, defaulted as 1
MEAS Version type of performance
VERSION measurement, defaulted as 0
LAPD CUT LAPD flow control removal stop board After removal stops, it immediately enters the

Name of
Variable
threshold, defaulted as 95 recovery process
LAPD LAPD flow control recovery security
RECOVER threshold, defaulted as 70
Start the flow control service load
CSCPU LIMIT It refers to the load occupied by task No.2.
threshold, defaulted as 80
CPU ALARM CPU alarm threshold, defaulted as 70
Whether load alarm is reported to MSC,
ALARM MSC
defaulted as FALSE
Whether to convert field SIONI
(conversion between the domestic active
CONVERT
and standby), defaulted as 0; for no
SIONI
conversion, defaulted as non 0; then
conduct conversion, the default value is 0
Select the value of SIONI sent to MSC.
0x0C refers to domestic standby; 0x08
SELECT SIONI refers to domestic active. This item is
only valid on the condition of CONVERT
SIONI =1. it is defaulted as 0x0C
Control variable of the data probe, used
to distinguish the old and new probes
PROBE
(new probe is carried by OMC-R). 0: old
probe; 1: new probe. Defaulted as 0
Whether to report field CircuitPool to
SEND MSC. 0 means reporting; 1 means
CIRCUITPOOL connecting the Bel MSC and this field is
not reported. Defaulted as 0
USERPRIENAB Whether to start the Sri Lanka channel
LE allocation policy, defaulted as 0
CSMEAS Whether to open CS basic measurement,
ENABLE defaulted as 1
PSMEAS Whether to open GPRS basic
ENABLE measurement, defaulted as 1
Q3MODULEME Whether to open Q3 module basic
AS ENABLE measurement, defaulted as 1
Q3BTSMEAS Whether to open Q3 cell BTS basic
CELLMEAS Whether to open Q3 NM cell basic
UB CHECK Whether to conduct write protection to
the unallocated UB; this item in version
RELEASE is invalid; it is only used in

Name of
Variable
version DEBUG, defaulted as 1
Buffer zone queue size used for This item should be set according to the MP memory
MEAS QUEUE
performance data transmission, defaulted size; one queue element occupies 620 bytes; queue size
SIZE
as 20480 is generally set as 40960
The maximum number of performance
data packets transmitted per second is set
MAX PKG PER
as 1~30; if over 30, the system will be
SEC
automatically initialized as 30; defaulted
as 10
Whether to send the MP print log
directly to the background; defaulted as 0; This item only affects print (print??.log); other logs
SEND PRINT
save the log into the document, defaulted such as error.log, int13.log and poweron.log will not be
TO SVR
as 1; send the log directly to the affected and still saved on MP.
background, defaulted as 1
The idle time (second) needed for hard,
DISK PARK namely, after how much time the hard If it is set less than 60 seconds, it still takes 60
IDLE SEC disk will enter the dormant status after it seconds when the hard disk sleeps
is in the idle status, defaulted as 900
二.5 TCPIP.CFG file setting
The path of TCP communication configuration document is \\CONFIG\TCPIP.CFG;

the configuration statements in the configuration document are case insensitive but the
number of spaces in the character string will affect configuration retrieval. Blank lines
will not affect retrieval. Entries in the configuration document have no precedence but
should be placed under corresponding sub-types, otherwise there will be errors in
parameter configuration.
Description of configuration items

Table Board software and hardware Setting-5 TCPIP.CFG Configuration Variable
Name of
Configuration Sub-Item Meaning
Variable
BSC ID, the foreground is insensitive to this setting but OMC-R
BscID [MAIN]
manages multiple BSCs one by one; BYTE type is non-zero value.
IsRemote [MAIN] Whether this module is place at the remote end, defaulted as 0 or 1
This MP receives the port for TCP link setup request, usually set as
TcpPort [MAIN]
5000.
UdpPort [MAIN] UDP port
TcpCard [MAIN] Network card used for tcp communication
UdpCard [MAIN] Network card used for UDP communication
UDP SubNet [MAIN] The subnet number used for udp
Machine No. of the server. There can be configured multiple servers;
Server Mno [SERVER] currently the maximum number is 2; specific configuration number is
defined in SYSCFG.H.
IP address of the server, corresponding with the machine number of the
Server IP [SERVER] server. It should not be mutually repetitive with the following all the IP
addresses.
IP address of the test server should not be the same with all the IP
Test IP [SERVER]
addresses between the server and LMT.
LMT Mno [LMT] Machine No. of the local maintenance terminal.
LMT IP [LMT] IP address of the local maintenance terminal.
MP module No. If the current MP is the same with the module No., then
Module [MODULE] the IP. 1 after it will be retrieved as the central module (namely the
switching module); numbers other than 2~9 represent modules.
Left IP [MODULE] If MP is inserted on the left, the setting of IP address
Right IP [MODULE] If MP is inserted on the right, the setting of IP address
note :when writing the IP address, the number must be separated with space not dot.

三 Configuration management
三.1 Function class of configuration interface
configure the physical setting and radio parameter in the integrated management.
adjust the detail radio parameter in the radio resource management.
configure the MP software in the software loading
Commissioning the system in the dynamic data management including block/unblock

the TS.
三.2 The sequence of data configuration

It is demanded to the sequence of data configuration , as the FigFig Configuration
management-1 show.
Fig Configuration management-1 the logic of data configuration
General sequence: first physical MSC, BSC→BSC RACK→BSC SHELF→BSC

BOARD． SITE→SITE RACK→SITE SHELF→SITE PANEL．transparent passage．
radio BSC→radio SITE→CELL→TRX．FHS．related cell．external cell.
三.3 Physical resource configuration
三.3.1 Information data of MSC
1． MSCID．must be identical in configuration.

2． MSC signaling point code: is obtained through specific algorithm at the MSC-
side Originating signaling Point Code (OPC). Suppose the 14-digit OPC is X, Y
and Z. Convert X, Y, and Z to 3-digit (X13X12X11), 8-digit (X10X9X8X7X6X5X4X3)
and 3-digit (X2X1X0) binary values. Add “0” to the beginning of values less than
3 or 8 digits. The three groups of binary values form a 14-digit binary value
X13X12X11 X10X9X8X7X6X5X4X3 X2X1X0. Convert this value to a decimal value F,
which is the value of MSC signaling point code.
三.3.2 Configuring BSC Data
1. MSCID: must be identical in configuration.
2. BSC signaling point code: The BSC signaling point code is obtained through the
algorithm, through which the MSC signaling point code is obtained, at the
Destination signaling Point Code (DPC) of the BSC office direction
corresponding to the MSC. You can set the “Hex test code” to any value. The
“Initialize radio information” option must be selected. The link error correction
parameter must be changed to 1. For other parameters, you can accept the
default settings.
3. Link error correction method: must be set to 1.
三.3.3 Configuring Abis Interface TIC (BSC)
The configuration of the Abis interface TIC must be consistent with the actual physical
connection line.
三.3.4 Configuring A-interface TIC
The configuration of A-interface trunk must meet the engineering design requirements.
According to the load sharing principle, you need to configure No. 7 signaling to the
trunk board uniformly. Where,
1. The BSC N7PCM number must be identical with that of the MSC-side office
direction, or calls cannot get through.
2. If signaling connection exists between the TIC and MSC, you must specify the
corresponding PCM as the signaling link (N7LINK).
3. The BSC Signaling Link Code (SLC) must be identical with that of the MSC-
side office direction, or calls cannot get through.

4. The TCPP communication capacity is limited, so the last PCM interface on the
last TIC on the right cannot be configured when the TIC is in full configuration
state. Otherwise, loading data will fail.
三.3.5 CSSS7(MTP/SCCP)Protocol timer setting of A interface
三.3.5.1 The value of Timerlar
Non-activate receiving timer(100ms) ． default value is 2400, in case of call drop at 4

minutes, set the value >10 minutes. e.g. 6000, 9600 ． The value of TimerIas and
TimerIar can not bigger or smaller than the value of the other at the same time, other
else, it will appear call drop at 4 minutes.
三.3.5.2 The value of Timerlas
Non-active receiving timer(100ms) ．default value is 900 ． The value of TimerIas and
TimerIar can not bigger or smaller than the value of the other at the same time, other
else, it will appear call drop at 4 minutes.
三.3.6 Allocation of HW
1． The allocation of HW for the TCPP,BIPP,FSPP and NSPP should consistent

with the physical cable connection.
2． The port A of the HW of TCPP, BIPP, and GIPP connects to T-net, port B
connects PP board.
3． For the HW between GIPP and PUC, the port A connects PUC, the port B
connects to GIPP.
三.3.7 MTP board configuration
When configure the 2M NO.7 signaling ,set the [communication type] to

[CMT_ZXG10_2MMTP] . if there are two MTP boards the [communication type]
should be same.
三.3.8 The configuration of A interface
三.3.8.1 The data for BSC

 The manufacturer and version of MSC
 MSC system software version, A interface protocol version, MTP/SCCP timer
parameter．
 The circuit status of A interface on MSC side．

 The type of E1 and PCM e.g. resistance is 75 Ohm or 120 Ohm．the type of cable
interface．
 MSC SPC．(14 bit , have to convert to decimal) (MSC decide the data )
 BSC SPC．(14 bit , have to convert to decimal) (MSC decide the data )
 PCM code．(begin from 1．also support 0~255) (MSC decide the data)
 TS for NO.7 signaling．(default :TS16) (MSC decide the data)
 SLC for NO.7 signaling．(0~15) (MSC decide the data)
 The sequence of CIC (33~47, 49~63)(CIC NO. ． PCM NO.×32+TS NO. ．ZTEb
begin from 33)
 The NO. of NO.7 signaling．(ZTE NO.7 PCM NO. are 1, 5, 9……the interval is 3
PCM)
三.3.8.2 The data for cell

 LAC(decimal)
 CID(decimal)
 ARFCN
 BSIC(BSIC=NCC+BCC)
 Neighbor cell and radio parameter
 Option ：other radio parameter
三.3.8.3 The data for other MSC/BSC
 Record the LAC+CI，and point to the BSC SPC
 The handover and reselect cell in other OMCR
 Neighbor cell and radio parameter
 Power control parameter
三.3.9 A interface connection
Operation of BSC
1. Configure the data;
2. Check the transmission between BSC and MSC;
3. Active the N7LINK in the dynamic data management;
4. Load the PCM in the dynamic data management;

The indication of successful A interface connection
1. Check the status of N7LINK in the dynamic data management, it should be

Normal.
2. The E1 light of A interface and MTP board flash rapidly(4Hz)
3. Check the status of the cell and trx, it should be idle or occupied.
4. There are signaling of A interface and Abis interface in the signal tracing.
Note
1. It is required to reset the MP after modify the parameter of A interface.
2. Do not self loop the other 3 E1 if there is only on N7PCM. Otherwise there are
unknown signaling of A interface.
Diagnose
1． There are 3 kinds of case when the NO7 unavailable.
(1) all the links are unavailable.
(2) some links are unavailable.
(3) links are available but there are some wrong messages and alarms.
The third case mainly occurs at the beginning of commissioning, especially for
other MSC. in this case ,usually it is the problem of software version. Check it
and solve it.
2． Check in the BSS
(1) make sure the MTP, MPPP, and DSNI-C board are on the slots tightly.
(2) loop the PCM , if the NO7 is normal , it indicates that the T-network is
normal. otherwise solve it.
(3) check the LINK by the OMCR to locate the problem..
Note :one MTP can only process 8 LINKs. Only the first LINK is normal ,
can the LED flash on the MTP.

三.3.10 Notice about the connection of ZTE BSC and other MSC
三.3.10.1 The modification of NO7 timer
When connect with other manufacturer’s MSC, the MTP and SCCP timer use the
default value., in some case, the timer should change from 240s to 360s or more
,there are once the problem of 3m call drop in alcaltel and northtel MSC(that is
:set the timer to 180s, when the call keep 3m, BSS reset the circuit to MSC, it
cause the call drop.) and 4m call drop(that is :set the timer to 240s, when the call
keep 4m, BSS reset the circuit to MSC, it cause the call drop.) when connect with
ZTE MSC , there is no such problem.
When connect with other MSC, pay attention to the timer. If any problem above,
set the timer to 600s.
三.3.10.2 Notice about connection with Alcatel MSC
1． Pay attention to the version, phase1 or phase2
Once ,the Alcatel MSC upgrade the version to phase 2+ but don’t notice the
ZTE, it cause the subscriber can not call.
Analyze the signaling of A interface, it is caused by Alcatel new version. It

locates in the process of “Assignment Complete” ：when the BSS receive the
“Assignment Request” from the MSC, after it assign the TCH, return the
“Assignment Complete”, the message contains three information unit:RR
Cause ， Chosen Channel ， Circuit Pool. now the MSC send the” Clear
Command” when it receives the message from the BSC, clear the call, the
reason is “the protocol wrong between BSC and MSC”. By the analysis, the
unit of Chosen Channel in the phase 2 is as shown in Fig Configuration
management-2.
8 7 6 5 4 3 2 1
Element identifier Octet 1
Spare Channel Octet 2
Fig Configuration management-2 the structure of Chosen Channel (old)
In the new GSM Phase II+ the structure is as shown in Fig Configuration
management-3
8 7 6 5 4 3 2 1
Element identifier Octet 1

Channel mode Channel Octet 2
Fig Configuration management-3 the structure of Chosen Channel (new)
The definition of Channel mode：

Bit 8765
0000 no channel mode indication
1001 speech (full rate or half rate)
1110 data， 14.5 kbit/s radio interface rate
1000 signaling only
All other values are reserved。
The ZTE BCC adopt the GSM Phase II, fill the high 4 bit in Chosen Channel
with 0, but Alcatel have bug in the new version, wrongly judge and clear the
call. At the same time ,when there is any handover between the BSC, there is
the same bug. After use the old version, the problem solved.
2． Frame asynchronous, loop on each side normal , but connection failure.
Reason ：the checkout way is different, Alcatel is CRC but ZTE is not.
Solution ：change the CRC to non in Alcatel.
Method: in the UNIX, enter 379(check ) 378(modify)
1＝“R_OBC_INIT”
NA=H-XXX
1=“R_OBC_INIT”
2，3＝“D_TR_CRC4&0&0”
NA=H-XXX
Change the “D_TR_CRC4”from 80 to 00(80:CRC，00:non) .
三.3.10.3 Notice about the connection with Siemens MSC
When connect with the Siemens MSC, it is required to match the data on both sides.
1． 14 bit SPC of BSC
2． 14 bit SPC of MSC

4． CIC
5． SLC between BSC and MSC
6． NO7 TS.
Moreover, pay attention to the checkout kind of circuit. Usually change the kind from
CRC4 to basical.
三.3.10.4 Notice about the connection with Ericsson MSC
When connect with the Siemens MSC, it is required to match the data on both sides.
3． CIC
5． NO7 TS.
The CIC begins from 1 and SLC from 0. but the CIC should be from 33 according to
the protocol.
CIC：PCM code*32+2M TS
SLC is the code for all the links between BSC and MSC.
三.3.10.5 Notice about the connection with the Northtel MSC
Notice the operation concerning the circuit status: there is a status bit on SCCP, it needs
set.
When finishing all the setting, one NO7 is normal, the statrs bit of R-OFFICE, R-SSN,
R-LINK is “0” on BSC side, all the circuits are normal in dynamic , but the circuits on
MSC are “LOCK”, can not make calls, there two messages in A interface:1, layer 3
message,2, disconnect indicate. Blocking and resetting on BSC is no effect , the SCCP
is broken.
Check the data on MSC, set a status bit on MSC to “0”, the system is normal. as in the
Figure Configuration management-4

C7RouteSet BJBSC05RTE1 InSv LinkSet Transfer
Rte State Mode Cost Linkset State status

0 Insv Assoc 0 BJBSC05ls1 Insv
All is “Ok” when set this parameter

as “INSV” status form “OFEL”
status (OMC at the MSC side).
Figure Configuration management-4 Modify parameters
三.3.10.6 Notice about the connection with Nokia MSC
When connect with the Nokia MSC, it is required to match the data on both sides.
4． CIC
6． NO7 TS.
三.3.10.7 Notice about the connection with Lucent MSC
Since the Lucent MSC have lots of bug, it is required:
First make the format of NO7 is “demostic master” or not(0x08) .if it is, modify the
parameter:
Modify the file ..\config\zxg10.cfg in the master MP of center module
Add two lines
CONVERT SIONI = 1
SELECT SIONI = 8
Others are the same as the above manufacturer.

三.3.11 Physical site configuration
The PCM physical configuration should keep consistent with the physical site.
三.3.12 Radio configuration of BSC
At the beginning ,make sure the national code and network code is correct, because
they can not modify.
三.3.13 Configuration of FM rack
1． Configure the TIC board in the 12,13 slot.
2． The FM rack NO. ranges from 1 to 16,othe rack ranges from 1 to 6.
3． The TIC board in the FM rack should be corresponding to the TIC board in the
NM rack.
4． Judge the HW satisfy the PCM or not.
5． If there is one FM rack , but no BATC layer, and congire the TIC group of FM
and NM,if save the setting ,there is an erroe,it because there is no BATC, it can
continue the configuration.
6． It is suggested one NM with one FM rack
三.4 Radio resource configuration
三.4.1 Create cell radio information
1．The LAC must be same as that of MSC.
2．MCC, MNC, LAC, CI is unique.
3．Cell type, GSM type and HO must be the same as others.
三.4.2 Create trx radio information(neighbor cell)
In one cell ,there must be on BCCH trx and must be only one BCCH trx.

四 GPRS Data Setting
四.1 Physical Configuration
四.1.1 GPRS Function On-off Setting
Before make GPRS configuration, we need confirm the parameter “Environment” in

the file of “$OMCHOME/conf/syscfg.ini”. “Environment = GSM” should be changed
to “Environment = GPRS” or “Environment = EDGE”.
Reset OMCR service to make the change available.
四.1.2 HW allocation
The HW for GIPP and PUC should be consistent with the physical cable connection.
四.1.3 BRCH
1． Add the TS on BRCH according to the data given by SGSN.
BRCH：bear channel.
2． The FRPNO connecting the same PUC must be different.
四.1.4 NSVC
1． Get the NSEI, NSVCI, DLCI from the SGSN.
NSEI：network service entity identity,usually is the same as the BSCID.
NSVCI：network service virtual connection identity,usually is the same as the

NSEI.
DLCI：data link connection identity. Usually is the same as the NSVCI.
2． When configure the NSVC , the burst package should be 640kB×NO.of TS,
e.g. there is 8 TSs,the burst package should be 640×8＝5120kB.
四.2 Radio configuration
四.2.1 Configuration environment selection
Radio configuration can be done in both integrated and radio configuration. Each have
advantage and disadvantage.

In the integrated configuration, the advantage is speediness, but when the channel is
occupied, it will failure, and can not modify the timer and dynamic channel.
In the radio resource, the advantage is all the parameter can be modified, but is slowly.
Suggestion: configure the cell in the integrated management and modify the channel
and timer in the radio resource.
四.2.2 Configuration of GPRS cell
1． NSE
2． BVC:BSSGP BVC, in one NSE, every GPRS cell can be marked by BVCI.
usually it sets as SITEID＋CELLID.
3． RAC: it ranges from 0 to 255 and decided by BSC.
4． BRP group:
(1) it ranges from 1 to 6。
(2) the relationship between BRP group and BRP:
BRP is designed as N+M backup. The frist BRP board that turn normal is the
first BRP group. It gets the data from te R_BRP.
(3) arrange the BRP group in advance.
四.2.3 Configuration of channels
1． There are enough channel and BRP group:
(1) the cell with one TRX, set “1 dynamic channel ＋1 static channel”.
(2) the cell with two TRX, set “1 dynamic channel ＋2 static channel”.
(3) the cell with more than two TRX, set “1 dynamic channel ＋3 static channel”.
2． There are not enough channel and BRP group:
(1) the cell with one TRX , set “1 dynamic channel”.
(2) the cell with two TRX, set “1 dynamic channel ＋1 static channel”.
(3) the cell with three TRX, set “1 dynamic channel ＋1 static channel’ or “2 static
channel”.
(4) the cell with more than three TRX, set “1 dynamic channel ＋2 static channel”.
To improve the speed ,it is suggested that the system should be “1dynamic
channel ＋3 static channel”.

五 HR Setting
五.1 Software Configuration Data Setting
HR software data configuration is set through GUI of software loading in OMCR. To
realize the HR function of system, we need load DSD version and set HR general
software version. After those configurations, we can set system DSP with supporting
HR function property.
五.1.1 DSP software loading
When make DSP software loading, in software loading GUI we select “HREN
software” to load version. The GUI is showing asFig HR Setting-5
Fig HR Setting-5 DSP software loading
五.1.2 HR General Software Setting
After DSP software loading, we set HR general software configuration, showing as

picture .5-2. Here we select BSC_HREN as the board type.
Fig HR Setting-6 HR general software
五.2 Physical Configuration Data Setting

When make HR physical data configuration, we need change EDRT board and BSC
DSP type to make sure BSC can support HR function. Besides, allocation of RRM
module is adjusted according to real situation when needed.
五.2.1 EDRT Board Changing
Before commissioning HR, we need not only proper software version, hardware type,
boot and logic version, but also replace DRT, EDRT386 and EDRT860 which do not
support HR function with EDRT852 board and configure EDRT852 as HR type.
五.2.2 BSC DSP Type Configuration
ZXG10 BSC2.97 data setting criterion can supply reference of detailed content and
attention of BSC DSP type configuration. Here we emphasize the BSC DSP type
checking.
BSC DSP type should be FR/EFR/HR when commission HR function. We need check
whether DSP type is set correctly or not. It is show asHR Setting-7

Fig HR Setting-7 BSC DSP type configuration
After creating the board, EDRT will download the HR DSP software. After that check
the software version to make sure it is right.
五.2.3 RRM Module Adjustment
When commission HR function, the total number of channels in the whole BIU unit is
fixed but the number of channels of each cell is increasing, that leads the maximal
number of TRX supported by RRM unit is decreasing. Therefore, we should
recalculate the total number of channels of cell managed by RMM unit. If we find after
commissioning HR function, the total number of FR + static HR + dynamic HR is
more than 1920 (240*8), the we should adjust RMM allocation or add a new RMM
module to support business traffic increase.
五.3 Radio Configuration Data Setting

Radio configuration data setting is composed of FR/HR priority setting, static HR and
dynamic HR configuration.

五.3.1 FR/HR Priority Setting
Channel priority of each cell is set in radio resource management module GUI of
OMCR. Configuration GUI is as Fig.6-4. It can set FR/HR priority separately
according to user priority.
Fig HR Setting-8 priority setting
五.3.2 HR Configuration
Check in the BTS data setting document.
五.3.3 Dynamic HR Configuration
Dynamic HR function uses BSC and cell as unit. Within one network manager domain,
we can configure one BSC supporting HR function but the other not supporting HR
function. Within one BSC, we can configure one cell supporting dynamic HR function
but the other not supporting dynamic HR function.
Dynamic HR data configuration is completed in integrated configuration management.

It is composed of BSC dynamic HR parameter configuration, cell dynamic HR
parameter configuration and dynamic HR sub-timeslot configuration.
【Attention】

Only BTS V2X series (include BTSV2, BS21, BS30 and OB06) and 8000 series
(include 8018, B8112, and M8202) can support dynamic HR. BTS like BTSV1.0,
BTSV1A and MB does not support dynamic HR function.
五.3.3.1 BSC Dynamic HR Parameter Configuration
See the detail as the Fig Picture HR Setting-9
Picture HR Setting-9 configure the dynamic HR
Notice:
1. The threshold for FR to HR in Single TRX cell: it is the upper limit,only for
single TRX cell. When the ratio of FR occupied > threshold, the FR convert to
HR.
2. The threshold for FR to HR in Multiple TRX cell: it is the upper limit,only for
multiple TRX cell. When the ratio of FR occupied > threshold, the FR convert
to HR.
3. The threshold for HR to FR: it is the lower limit, When the ratio of HR
occupied < threshold, the FR convert to HR.
4. Protection time for FR to HR:when there is a convertionfrom FR to HR,the

system begins to time,in this time ,the system will not convert the HR to FR.

5. The protection time for HR to FR:once there is a convertion from HR to FR,the

system begins to time. In this time the system will not convert the FR to HR.
五.3.3.2 Dynamic HR configuration
Refer to the BTS data setting.
五.3.3.3 Dynamic HR PCM configuration in BIU
The configuration is in the integrated management. as the Fig HR Setting-10. there is

rules:
1． The basicalunit is BIU for the HR PCM, there are two PCM in each BIU at
most. HR PCM can not used by other function.
2． The dynamic HR PCM configuration.
Fig HR Setting-10 configuie dynamic HR PCM

Appendix A Abbreviations
Abbreviation Full Name
A
AbisGP Abis Global Part
AIPP A Interface Peripheral Processor
AIS A interface subsystem
AIU A Interface Unit
AGP A Global Part
APP Application Processing Part
ATM Asynchronous Transfer Mode
B
BATC Backplane of A interface and TransCoder
BBIU Backplane of aBis Interface Unit
BCCH Broadcast Control Channel
BCTL Backplane of ConTroL
BHCA Busy-Hour Call Attempts
BIE Base station Interface Equipment
BIPP aBis Interface Peripheral Processor
BIU aBis Interface Unit
BNET Backplane of NET
BOSN Bit_Oriented Switching Network
BRP BSSGP RLC/MAC Protocol processor
BSC Base Station Controller
BSMU Backplane of SubMultiplexing Unit
BSS Base Station System
BSSAP Base Station System Application Part
BSSGP Base Station System EDGE/GPRS Protocol
BSSMAP BSS Management Application Part
BSSOMAP BSS Operation and Maintenance Application Part
BTS Base Transceiver Station
BTSM BTS Site Management
BVC BSSGP Virtual Connection
C
CBC Cell Broadcast Centre
CBE Cell Broadcast Equipment
CC Calling Control


CCCH Common Control Channel
CCM Channel Change Module
CCS7 Common Channel Signaling System NO.7
CKI ClocK Interface board
CM Communication Management
COMI COMmunication Interface board
COMM COMMunication board
CPU Central Processing Unit
CS Circuit Switch
D
DBS Data Base Subsystem
DC Direct Current
DCE Data Circuit terminating Equipment
DDN Digital Data Network
DLCI Data Link Connection Identifier
DRT Dual-Rate Transcoder
DSNI Digital Switch Network Interface
DSP Digital Signal Processor
DSS1 Digital Subscriber Signaling No1
DTAP Direct Transfer Application Part
DTE Data Terminal Equipment
DTX Discontinuous Transmission
E
EBRP Enhanced BSSGP RLC/MAC Protocol processor
EDRT Enhanced DRT
EFRP Enhanced Frame Relay Protocol processor
EFRS Enhanced Full Rate Service
EIR Equipment Identification Register
EMC ElectroMagnetic Compatibility
EMI Electro Magnetic Interference
ETSI European Telecommunications Standards Institute
F
FIFO First-In-First-Out
FR Frame Relay
FRP Frame Relay Protocol processor
FRS Full Rate Service
FSMU Far SubMultiplexing Unit
FSPP Far Submultiplexing Peripheral Processor


G
GbIS Gb Interface Service Subsystem
GDPP General Data Protocol Processor
GGSN Gateway EDGE/GPRS Support Node
GIPP Gb Interface Peripheral Processor
GIU EDGE/GPRS Interface Unit
GND GrouND
GNDP GrouND Protection
GPP General Peripheral Processor
EDGE/GPRS General Packet Radio Service
GSM Global System for Mobile Communication
GTP EDGE/GPRS Tunnelling Protocol
H
HDLC High-level Data Link Control protocol
HLR Home Location Register
HPI Host Port Interface
HSCSD High Speed Circuit Switched Data
I
IMSI International Mobile Subscriber Identity
ISDN Integrated Services Digital Network
L
L1 Layer 1
L2 Layer 2
L3 Layer 3
LAN Local Area Network
LapD Link Access Protocol on the D channel
LLC Logical Link Control
LMT Local Management Terminal
M
MAC Medium Access Control
MF Mediation Function
MM Mobility Management
MO Manage Object
MON MONitor board
MP Main Processor
MS Mobile Station
MSC Mobile services Switching Center
MSS Mobile Switch System


MTP Message Transfer Protocol
N
NEF Network Element Function
NS Network Service
NSE Network Service Entity
NSMU Near SubMultiplexing Unit
NSPP Near Submultiplexing Peripheral Processor
NSU Net Switching Unit
NS-VC NS Virtual Circuit
O
OMC Operation and Maintenance Center
OMM Operation and Maintenance Module
OMS Operating Maintenance Subsystem
OSF Operation System Function
OSI Open System Interconnection
OSS Operating & Support Subsystem
P
P0 Processor 0
P0DS P0 Dispatch System
PACCH Packet Associated Control Channel
PAGCH Packet Access granted Channel
PBCCH Packet Broadcast Control Channel
PCB Process Control Block
PCH Paging Channel
PCM Pulse Code Modulation
PCOM Packet COMmunication board
PCU Packet Control Unit
PDN Public Data Network
PDP Packet Date Protocol
PDTCH Packet Data Traffic Channel
PDU Protocol Data Unit
PEPD Peripheral Environment & Power Detect board
PHS PHysical Subsystem
PnDS Abis Dispatch System
PLMN Public Land Mobile Network
POWB POWer B
POWP POWer P
PPCH Packet Paging Channel


P-RMS Packet- Radio Management Module
PS Packet Switch
PSPDN Packet Switched Public Data Network
PSTN Public Switching Telephone Network
PTP Point To Point
PUC Packet Unit Controller
Q
QoS Quality of Service
R
RACH Random Access Channel
RLC Radio Link Control
RMM Radio Management Module
RMS Radio Management subsystem
RMU Radio Management Unit
RR Radio Resource
RRU Radio Resource Unit
S
SACCH Slow Associated Control Channel
SAPI Service Access Point Indicator
SCCP Signal Connect Control Part
SCM System Control Module
SCU System Control Unit
SDCCH Stand alone dedicated Control Channel
SGSN Serving EDGE/GPRS Support Node
SM SubMultiplexing
SMC Short Message Center
SMEM Share MEMory
SMPP Subchannel Multiplexing Peripheral Processor
SMS Short Message Service
SMU Subchannel Multiplexing Unit
SPCU Sub Packet Control Unit
SPS Service Processing Subsystem
SSM Subjoin Service Management
SYCK SYnchronous ClocK board
T
TBF Temporary Block Flow
TC TransCoder
TCH Traffic Channel


TCP Transmission Control Protocol
TCPP TransCoder unit Peripheral Processor
TCU TransCoder Unit
TDMA Time Division Multiple Access
TE Terminal Equipment
TEI Terminal Equipment Identification
TIC Trunk Interface Circuit
TMM Transport Management Module
TRAU Transcoder Rate Adaption Unit
TRX Transmitter & Receiver
TS Time Slot
TTL Transistor-Transistor Logic
U
UDP User Datagram Protocol
Um Um Interface
V
VLR Visitor Location Register

05 ZXG10 BSC (V2.97) Unpacking Inspection Guide

Caricato da

Informazioni sul documento

Titolo originale

Copyright

Formati disponibili

Condividi questo documento

Condividi o incorpora il documento

Opzioni di condivisione

Hai trovato utile questo documento?

Questo contenuto è inappropriato?

Copyright:

Formati disponibili

05 ZXG10 BSC (V2.97) Unpacking Inspection Guide

Caricato da

Copyright:

Formati disponibili

ZXG10 BSC (V2.

Planned by: ZTE Global After-Sales Service Center

Compiled by: Zhong Junbiao

Reviewed by: Liu Zike

Post code: 518057

Technical support website: http://tsm.zte.com.cn

Hotline: +86 755 26770800 800-830-1118

Fax: +86 755 26770801

Confidential and Proprietary Information of ZTE CORPORATION. i

1.4 Client configuration..........................................................................................................................1-26

2 Board software and hardware Setting....................................................................................................2-1

Confidential and Proprietary Information of ZTE CORPORATION. ii

4 GPRS Data Setting....................................................................................................................................4-1

Confidential and Proprietary Information of ZTE CORPORATION. iii

一.1.1 Server hardware configuration

System Configuration capacity

Disk 40 GB 80 GB 120 GB ≥ 120 GB

Number of In the range of

Confidential and Proprietary Information of ZTE CORPORATION. -1-

System Configuration capacity

Fujitsu servers or PCs.

一.1.2 The operation system requirements of the server

OMCR V2 system requires Solaris with the patch“Generic_108528-29” .e.g. “SunOS

If lower than that, it is necessary to upgrade the system.

一.1.3 Planning disk partitions

The requirement is showed as follow tables from 1-2 to 1-4

Confidential and Proprietary Information of ZTE CORPORATION. 2

Table Network Management system configuration-1 disk partition (1)

Confidential and Proprietary Information of ZTE CORPORATION. 3

Table Network Management system configuration-2 disk partition (2)

Confidential and Proprietary Information of ZTE CORPORATION. 4

disk 4 0 /metadb 72M

Table Network Management system configuration-3 disk partition (3)

Logical disk Slic

To the V.2.52 or higher class, the following requirements must be satisfied:

1. The performance table space must be 1G at least without any data.

Confidential and Proprietary Information of ZTE CORPORATION. 5

一.1.5 Oracle8.1.7 Enterprise Edition installation

一.1.5.1 Oracle8.1.7 database parameter adjustment

2. database compatibility adjustment

4. database rollback segment adjustment

5. database log space adjustment

 Database instance adjustment

1． Calculate the available memory

Database instance available memory ． physical memory - (TRX

to “independent DB server configuration”．

Database instance available memory ． physical memory - (100MB +

The command to check the memory is:

2． Changing the parameter

adjust five main parameters according to the available memory (db_block_size

Parameter Name Description

Available db_block_b shared_pool sort_area_siz sort_area_re

If the Large_pool_size parameter is set, the parameter value must be the

Confidential and Proprietary Information of ZTE CORPORATION. 7

select decode(pool, NULL, 'log data buffers', pool) "Buffer(Pool) Name",

select 1 - sum(decode(name, 'physical reads', value, 0))

select 1-sum(getmisses)/sum(gets) "Directory Hit Ratio[>.85]"

select 1-(sum(reloads)/sum(pins)) "Procedure Hit Ratio[>.95]"

select b.value/(b.value + a.value) "Memory Sort Ratio[>.95]"

select a.value "Redo log Retries[inc near 0]"

 Adjustment of database compatibility

 Add the database rollback section

Confidential and Proprietary Information of ZTE CORPORATION. 8