Preface Maintenance Experience

Semiyearly for Integrated Intellligent Network

In pursuit of the idea First-class service, Customer service, No.3 Issue 82, February 2008

and in order to make more profit and provide better service for
our customers, we have compiled this Maintenance Experience, Maintenance Experience
which focuses on ZTE's service products. Editorial Committee
Carriers pay much attention to the equipment maintenance
along with the increasingly fierce competition in the telecom Director: Zhou Susu
market, since high-quality telecom networks are the basis of Deputy Director: Chen Jianzhou
Editor-in-Chief: Yang Cheng
customer service. ZTE's Integrated Intelligent Network products
Editors:
are widely used in China and overseas. This issue includes 16
Jiang Guobing, Zhang Shoukui, Wu Feng, Yuan
articles on installation & commissioning, daily maintenance and
Yufeng, Tang Hongxuan, Chen Huachun, Li
troubleshooting, involving operating system, database, switch, Gangyi, Gu Yu, Song Jianbo, Tian Jinhua, Zhu
platform and services. These articles introduce experience of Wensheng, Ling Changwen, Zhang Zhongdong,

technical engineers gained from equipment commissioning and Liu Xianmin, Wang Zhaozheng, Liu Wenjun, Lei
Kun, Wang Tiancheng, Chen Fuqi, Cai Hongming
maintenance overseas. We hope the articles may help you as a
reference for your maintenance.
Technical Senior Editor:
For more maintenance experience articles and related Zhou Fangying
technical documents, please log into ZTE's technical support
website (http://ensupport.zte.com.cn). Executive Editor:

If you have any requirement, question, or suggestion, please Chen Xiaoling

feel free to contact us. Your attention and support are greatly
appreciated.
Maintenance Experience
Newsroom
Maintenance Experience Editorial Committee
Address: ZTE Plaza, Keji Road South, Hi-Tech
ZTE Corporation
Industrial Park, Nanshan District,
February, 2008
Shenzhen, P.R.China
Postal code: 518057
Contact: Song Chunping
Email: doc@zte.com.cn
Tel: +86-755-26770600,26771195
Fax: +86-755-26772236
Document support mail box: doc@zte.com.cn
Technical support website: http://ensupport.zte.
com.cn
Contents

Shared Disk mount Failure 2

AIX Small Computer Unable to Recognize the Disk Array 3
IBM 7133 Disk Slot Not displayed 4
Unix SCP Platform Clock Synchronization Issue 5
Synchronization between local NTP (Windows system) and the NTP in Area A 6
Local Disks Cannot be Found When Installing Suse Linux 9 on the HP PC Server 8
Hardware Check Failed upon Power-On After TurboLinux10 is Installed 9
Dell Disk Array Configuration Description 10
Hard Disks Cannot Start After Dell Server Power-Down 14
Handling Method for Master Database Crash 15
Cannot Edit the Segments with More Than 255 Characters on a Sybase 11.92 Client 17
Sybase Installation Failure Under Suse Linux 18
IP Cannot Play Announcements in the CDMA Service Call Flow 19
MRB Tone Playing Circuits All Busy 20
ETC Failure in Independent IP Announcement Playing 21
Noisy Tone Playing in an American Office 23
The Shortest GT Code in GT Translation Must be 3 Bits 26
ZXCOMM Process Cannot be Started After Configuring the NEWMC Module 27
SMAP Clients with Different IDs Cannot Log in at the Same Time 28
Corrective Action for Service Load Failure 28
Abnormal Billing 30
SCP CPU Overload 31
IMP Link Setup 32
Analysis for Failed Card Creation via Web by Independent VC 33
Brief Description of Service Logs for vsftp Used by Linux Web Server for CRBT 35
Detailed Description of Linux Web Server for CRBT 37
February 2008 Issue 82
Shared Disk mount Failure
Peng Wei, ZTE Corporation
Product: ZXUP10
Keyword: Disk mount
Problem Description
In the HP-Unix system, the sybdev6 on
the shared disk array cannot be mounted
to /data after the primary power supply in
the equipment room is down.
Background
The abnormal power-down on the
server causes the disk array problem.
Analysis
Execute mount after activating
vgsybase manually, the following error
message appears:
# mount /dev/vgsybase/sybdev6 /data
vxfs mount: /dev/vgsybase/sybdev6 is
corrupted. needs checking.
Action
The disk array is in an abnormal state.
 Maintenance Experience
Try to mount after removing the improper state or
checking the disk array.
Execute the following commands to check the
partitions of the shared disk.
[root@scp]fsck -F vxfs -o full -y /dev/vgsybase/
sybdev6
log replay in progress
pass0 - checking structural files
pass1 - checking inode sanity and blocks
pass2 - checking directory linkage
pass3 - checking reference counts
pass4 - checking resource maps
OK to clear log? (ynq)y
set state to CLEAN? (ynq)
Execute mount again after check-up. The
execution is successful.
Brief Summary
Check the disk array if it is in an improper
state.
 www.zte.com.cn

AIX Small Computer Unable to

Recognize the Disk Array
Wang Peng, ZTE Corporation

Product: ZXIN10
Keyword: AIX EMC disk array

Problem Description Only two rootvg pv can be displayed,

System: AIX
Disk array: EMC CX300
The disk array is connected to an AIX small
computer and is powered on properly. But the AIX
system cannot recognize any physical hard disk.
Only the hard disks on rootvg can be seen after
executing lspv, but no hard disk in the disk array
can be read. After executing Smitty vg - list all vg,
vgsybase can be seen. But no volume group can
be activated, and you cannot view or perform any
operation to any logical partition on vgsybase.
After executing varyonvg vgsybase, the error
message "The volume group cannot be varied on
because there are no good copies of the descriptor
area" appears.
Execute:
# smitty
Devices
SSA RAID Arrays
Add an SSA RAID Array
Unable to recognize the corresponding
hardware.
The synchronous volume group information has
no use.
Execute:
# cfgmgr -v
Then
# lspv
and vgsybase still cannot be found.
Close one of the computers and restart
the other one. The disk array still cannot
be found in the single-computer mode.
Check mount and processes. No
impact on disk array activation or mount is
found.
Analysis
After the operations described above,
the problem is located to the connection
between the disk array and the small
computers. Recheck all the connecting
cables between small computers and the
disk array. Restart the disk array and small
computers, and try to recognize the disk
array again.
Action
1. Shut down the two small computers
a n d t h e d i s k a r r a y. C h e c k a l l t h e
connecting cables between the disk array
and the small computers. It is better
to re-plug the cables to ensure secure
connections.
2. Power on the disk array first and
then the small computers. After the system
is started, perform operations according

Integrated Intelligent Network 

February 2008 Issue 82

to the procedure described in the "Shared generally caused by the connection failure between
Disk Space Synchronization" section in the disk array and small computers. If the problem
the installation manual. Generally, the disk persists after verifying the connections are proper,
array can be recognized. This problem is contact the disk array agent.

IBM 7133 Disk Slot Not displayed

Tang Genmao, ZTE Corporation

Product: ZXIN10
Keyword: Service key

Problem Description Where, no slot information is available for

System architecture: IBM AIX 5L + pdisk2.
7133 disk array
After executing lsdev -Cc pdisk to Action
check the disk array, the following disk Perform one of the two methods:
information appears: 1. Restart the host where the problem occurs.
pdisk0 Available 14-08-6D5D-08-P The system is recovered after restarting.
SSA160 Physical Disk Drive 2. Execute rmdev for all the disks to obtain
pdisk1 Available 14-08-6D5D-06-P configuration information again.
SSA160 Physical Disk Drive #rmdev -dl pdisk0
pdisk2 Available 14-08-P SSA160 #rmdev -dl pdisk1
Physical Disk Drive #rmdev -dl pdisk2
pdisk3 Available 14-08-6D5D-01-P #rmdev -dl pdisk3
SSA160 Physical Disk Drive #rmdev -dl pdisk4
pdisk4 Available 14-08-6D5D-02-P #rmdev -dl pdisk5
SSA160 Physical Disk Drive #cfgmgr
pdisk5 Available 14-08-6D5D-05-P #lsdev -Cc pdisk
SSA160 Physical Disk Drive

 Maintenance Experience

Unix SCP Platform Clock
Synchronization Issue
Song Yanjun, ZTE Corporation
Product: ZXIN10
Keyword: SCP, Unix, NTP
Overview
Relevant configurations of SCP clock
synchronization.
Detailed Description
By default, SCP obtains clock from MP. MP
obtains clock from external clock sources through
DTI or from 129 using the R03.exe program.
However, in some offices, SCP is required to obtain
clock from the specified clock server. This article
introduces the configuration procedure in detail.
Procedure
(Take the IBM AIX system as an example)
Synchronization principle: SCP synchronizes
the clocks from a local NTP server. SCP acts as a
client. The local NTP server obtains the standard
www.zte.com.cn
time from the standard clock server and
acts as both the server and the client.
The following example illustrates the
SCP clock synchronization in an oversea
office.
Server IP addresses are as follows:
NTP address of Area A: 10.75.10.35
Local NTP address: 200.48.3.111
Floating IP address of SCP:
200.48.3.133
Current active server IP address:
200.48.1.142
Current standby server IP address:
200.48.1.141
Server modification required:
SCP: 200.48.3.133 (200.48.1.141/142)
CDR: 200.48.3.150
Integrated Intelligent Network 
February 2008 Issue 82
Synchronization between Local
NTP (Windows system) and the
NTP in Area A
This configuration enables the NTP
Server function of the Windows system.
It is the clock source for other external
servers. The local server obtains clock
from the standard clock server.
Open the registry.
1. Basic settings
1) HKEY_LOCAL_MACHINE\
SYSTEM\CurrentControlSet\Services\
W32Time\Parameters\Type
Change the value of Type to NTP.
2) HKEY_LOCAL_MACHINE\
SYSTEM\CurrentControlSet\Services\
W32Time\Config\AnnounceFlags
Change the DWORD value of
AnnounceFlag2 to 5.
2. Enable NTPServer
 Maintenance Experience
HKEY_LOCAL_MACHINE\SYSTEM\
CurrentControlSet\Services\W32Time\
TimeProviders\NtpServer
Change the DWORD value of Enabled to 1.
3. Specify the clock source
1) HKEY_LOCAL_MACHINE\SYSTEM\
CurrentControlSet\Services\W32Time\Parameters\
NtpServer
Right click NTP Server > Edit String. In the
Value text box, type in Peers, and click OK.
2) Select a polling interval
HKEY_LOCAL_MACHINE\SYSTEM\
CurrentControlSet\Services\W32Time\
TimeProviders\NtpClient\SpecialPollInterval
Change the DWORD value of
SpecialPollInterval to 900 (decimal system).
Configure time calibration

HKEY_LOCAL_MACHINE\SYSTEM\
CurrentControlSet\Services\W32Time\Config\
MaxPosPhaseCorrection
Change the DWORD value of
MaxPosPhaseCorrection to 3600/1800 (decimal
system).
HKEY_LOCAL_MACHINE\SYSTEM\
CurrentControlSet\Services\W32Time\Config\
MaxNegPhaseCorrection
Change the DWORD value of
MaxNegPhaseCorrection to 3600/1800.
4. Exit the registry
In the DOS command line interface, execute:
1) net time /setsntp:10.75.10.35 to establish the
NTP Server IP address. The value of
HKEY_LOCAL_MACHINE\SYSTEM\
CurrentControlSet\Services\W32Time\Parameters\
NtpServer is changed to 10.75.10.35.
2) Restart the clock service
net stop w32time && net start w32time
In the Administration Tools > Services, set
window time to Automatic.
Synchronization between SCP and the local
NTP
Log into the standby SCP with IP address
200.48.1.141 as user "zxin10". Perform the
following steps to modify the configuration file,
which prevents SCP from obtaining clock from MP.
1. Find zxin10.scr in the etc directory. Decrypt
the file using zxtool2 -d zxin10.scr and then get
zxin10.ini.
Modify vi zxin10.ini:
[GENERAL]
StopAdjustTime = 1
Save the modification and encrypt zxin10.ini
using zxtool2 -e zxin10.ini and then get zxin10.
scr.
2. Perform active/standby switch-over.
It is recommended to re-log into 200.48.3.133
as user "zxin10". Switch over between the active
and standby SCP using superstop. The login
may be interrupted. After it is normal, log into
www.zte.com.cn
200.48.3.133. Execute netstat -in to make
a check-up. The address 200.48.1.141
should be seen. It is found to be
200.48.1.142. This operation may cause
call loss, so it is recommended to execute
zxtool2 -g to check the number of current
calls and perform the operation at an
appropriate time.
3. After successful switch-over, execute
a command on the currently standby SCP
to start the cluster, which ensures the
SCPs can be switched over normally next
time.
Execute smit clstart to start the cluster
process to ensure normal switch-over next
time.
4. Start the monitoring process for SCP
getting time (both the active and standby
SCPs are modified).
The following steps must only be
performed on the currently active SCP
with the IP address 200.48.1.141, that is,
the SCP after the login to 3.133:
1) In etc/ntp.conf, add the server
200.48.3.111 under broadcastclient. Save
and exit.
2) Execute startsrc -s xntpd to start
the daemon process.
3) Execute startsrc -s xntpd to check
the state.
4) Execute ntpdate 200.48.3.111 to
perform synchronization.
5) In home/zxin10/task/mytab, add 2 *
* * * ntpdate 200.48.3.111, which denotes
that the synchronization is performed
every two minutes.
Execute crontab home/zxin10/task/
mytab to complete task customization.
For the synchronization between
CDR and the local NTP, refer to the
configuration procedure for the local NTP
server.
Integrated Intelligent Network 
February 2008 Issue 82

Local Disks Cannot be Found

When Installing Suse Linux 9
on the HP PC Server
Li Lin, ZTE Corporation

Product: ZXIN10
Keyword: Suse Linux 9

Problem Description Suse Linux 9 versions do not support the servers.

Install Suse Linux 9 on an HP PC
server with a disk array. After successful
installation, it becomes abnormal. The
installed operating system cannot be
found.
Problem background/Site Environment
HP DL380G5, HP DL580G4 and higher
versions; Suse Linux 9 x86
The latest patch SP3 is required for the installation.
Action
Download the latest patch SP3 for Suse Linux 9.
Burn the patch in a CD. Boot the installation from
the SP3 CD.
Note: The installation CD with SP3 patch must
be delivered with the product later.

Analysis Brief Summary

HP DL380G5 and HP DL580G4 are Make sure that the Linux system you want to
new PC Servers launched by HP. The old install must support the hardware device.

 Maintenance Experience
 www.zte.com.cn

Hardware Check Failed upon

Power-On After TurboLinux10
is Installed
Xia Rui, ZTE Corporation

Product: ZXIN10
Keyword: DL580 turbolinux, hardware check

Problem Description since no error message appears in the

The web server delivered to the site is pre-
installed with the Windows 2003 operating system.
The server, HP DL580, should be installed with
Turbo Linux10 as a replacement according to
the requirement. After successful installation,
restart the system. The system is down upon
new hardware check. The screen displays "CPU8
exception 0000000000000004" with no more
response. The computer has four 4-core CPUs.
Analysis
1. The computer was installed with Windows
2003. Normally the Task Manager > Performance
window shows 16 CPUs, so the hardware has no
problem.
2. For the accordance with the Turbo Linux 10,
the web servers are designed in a dual-computer
configuration. The other server can be installed
with Turbo Linux 10 and can be started normally.
So there is no accordance problem.
installation process. As mentioned above,
the other of the two servers is normal, so
replace the CPU module units of the two
computers.
Figure 1 shows the front panel of the
HP DL580 server. The red frame indicates
the CPU module unit, which is easy to
be removed with no tools needed. After
exchanging the CPU module unit of the
two servers, both of the two servers
can start the operating system normally.
Restart the system for a few times for
verification. It shows that the problem is
eliminated completely.

Action
It is not recommended to re-install the system Figure 1. Front Panel of HP DL580 Server

Integrated Intelligent Network 

February 2008 Issue 82

Dell Disk Array Configuration

Description
Wu Jun, ZTE Corporation

Product: ZXIN10
Keyword: Dell

Overview
Dell PC server is often used in the on-site
engineering. So how to perform operations to the
SCSI card and SCSI disk array connected to the
server and use them properly? This may be a
trouble to the new users. This article provides an
easy-to-understand instruction for the new users.

Figure 1. Shared Disk Array Connections in a Dell Cluster
Detailed Description
1. Shut down the two servers and the disk
array. Connect the cables according to the
following steps.
Note: For the shared disk array in a cluster
configuration, the bus of the cluster must be moved
to the lower part, as shown in Figure 1.

10 Maintenance Experience
 www.zte.com.cn

The SCSI cables must be connected to the that controls the disk array), as shown in
same path, that is, the same side of the SCSI Figure 4.
interface cards of the two small computers. 3) Select Disable BIOS, as shown in
2. Configure the disk array information of the Figure 5.
two servers. Power on the disk array. 4) Select YES in the Adapter
Note: configuration, as shown in Figure 6.
1) Even if only the half part of the disk array has 5) Modify the cluster mode by selecting
hard disks and the other part has no disk, all the Cluster Mode.
power must be switched on; otherwise an alarm 6) Select Enable, as shown in Figure 8.
will be raised.
2) Configurations are performed in order, which
is identified as A and B in the following steps.
3. Shut down Computer B. Press CTRL + M to
enter PERCs BIOS when starting Computer A, as
shown in Figure 2.
1) Enter the Objects menu, as shown in Figure 3.
2) Select an adapter (Note that if there are
two adapters on the Dell Server, which serve for
Figure 5. Adapter Configuration - 1
the local hard disk group and the disk array group
respectively, make sure to select the adapter

Figure 2. Entering the BIOS Settings Interface

Figure 6. Adapter Configuration - 2

Figure 3. Entering the Objects Menu

Figure 7. Adapter Configuration - 3

Figure 4. Selecting the Adapter Corresponding to the

Disk Array Figure 8. Adapter Configuration - 4

Integrated Intelligent Network 11

February 2008 Issue 82
Figure 9. Adapter Configuration - 5
Figure 10. Adapter Configuration - 6
Figure 11. Adapter Configuration - 7
7) Confirm the modification by selecting
YES. Press Enter, as shown in Figure 9.
8) Select Initiator as shown in Figure
10. Set Initiator to 6 as shown in Figure 11.
Make sure it must be different on the two
computers. Set it to 6 on Computer A and
7 on Computer 7. Confirm the settings, as
shown in Figure 12.
9) Exit the configuration by pressing
ESC and restart the computer, as shown
in Figure 13.
4. After Computer A is started, enter
PERC's BIOS, as shown in Figure 14.
1) After entering the BIOS configuration
12 Maintenance Experience
Figure 12. Adapter Configuration - 8
Figure 13. Restarting the Server After Finishing the
Configuration
Figure 14. Entering the BIOS Configuration Again
After Restart
Figure 15. Entering the Configure Menu to Setting the
Disk Array - 1
interface as shown in Figure 15, select the
Configure menu.
Note: First, click the Select Adapter menu on
the bottom to select the card that serves the disk
array. This menu is not displayed in this example.
Make sure to select the correct one in your
 www.zte.com.cn

configuration; otherwise the following operation will

delete all the hard disk information!
Select Clear Configuration to clear all the
disk array settings on Computer A. Then select
the New Configuration menu item to create a new
configuration again. Click YES to save the settings,
as shown in Figure 16.
2) Confirm and finish the modification as shown Figure 16. Entering the Configure Menu to Setting the
in Figure 18. Select the View/Add Configuration Disk Array - 2

menu. All the disks should be displayed as "ready".

Put the cursor on the first disk and select all the
disks by pressing the Enter key (the selected disks
will be displayed as "ON_LINE".
Press the Enter key to finish the selection.
Then press F10. A dialog box appears. Press
Enter, and then F10. A new window appears, as
Figure 17. Entering the Configure Menu to Setting the
shown in Figure 18.
Disk Array - 3
3) Select the type of RAID as required, and
then click Accept, as shown in Figure 19. The
configuration for Computer A is finished. Restart
the computer.
5. After Computer A is started, right click My
Computer > Control Panel > Administrative
Tools > Computer Management > Storage >
Disk Management to start the disks in the disk
Figure 18. Configuring the Disks in the Disk Array - 1
array and format the disks.
6. If Step 5 is done successfully, shut down
Computer A and then the disk array.
7. Start Computer B to configure its settings.
The procedure for confirming the Adapter in Object
is similar to that for Computer A, except that the ID
is different from that of Computer A.
Next, perform the following steps to configure
the disk information: Figure 19. Configuring the Disks in the Disk Array - 2
1) Select Configure in the window as shown in
Figure 20. Then select Clear Configuration.
Note: Make sure the select the proper adapter
number before you begin. Otherwise all the local
disk information will be lost. Shut down Computer
B after selection.
8. Confirm Computer B is shut down. Power
on the disk array and wait for 2 minutes. Then, Figure 20. Configuring the Disk Information on
start Computer B to re-enter PERC's BIOS. In the Computer B

Integrated Intelligent Network 13

February 2008 Issue 82
Figure 21. Viewing the Disk Information on Computer B
interface as shown in Figure 21, select
View/Add Configuration to check if all
the disks have been synchronized to the
ON_LINE state.
Hard Disks Cannot Start After
Dell Server Power-Down
Peng Wei, ZTE Corporation
Product: ZXIN10
Keyword: Dell Server, start
Problem Description
After a Dell server is powered down,
the hard disk indicator turns off after a
flash when the disks start. The server
cannot be started normally.
Background
The server is powered down abnormally.
Analysis
Power off the server, then pull out
the hard disks and replug them in. If the
server still cannot start, exchange the two
disks sequentially and restart the server.
14 Maintenance Experience
9. If there is no problem, restart Computer
B. Make sure the disk array can be seen in Disk
Management, and then format the disks.
10. After finishing Step 9, restart Computer A,
which allows you to see the disk array on the two
servers.
Notice that there are two indicators lit on the
front panel of the disk array, which are the first and
third ones. The first indicator indicates that the disk
array is working. The second indicator indicates
that it works in a cluster mode.
Note: If you have different operation results,
please contact me at doc@zte.com.cn.
The server can be started normally. Power off the
server again, then the same problem appears.
Action
Upgrade the main board drive of the Dell 2850
server.
Configure BIOS again. Delete the information
of the two local disk of the server and configure it
again. Restart the server. Power down the server
many times for test. The server can start normally.
Brief Summary
Delete and re-configure the local disk
information in BIOS when the problem appears.

Handling Method for Master
Database Crash
Wu Jun, ZTE Corporation
Product: ZXIN10
Keyword: Database, master
Problem Description
The database fails to be started in the
Intelligent Network platform upgrade process. An
error message appears indicating that the master
database is unable to be recovered. The log
records some important information as follows:
00:00000:00000:2006/06/02 05:19:49.55 kernel
Either the config parameter 'use security services'
is set to 0, or ASE does not support use of external
security mechanisms on this platform. The Security
Control Layer will not be initialized. No external
security mechanisms will be supported.
00:00000:00000:2006/06/02 05:19:49.55 kernel
engine 0, os pid 4708 online
00:00000:00000:2006/06/02 05:19:49.55 server
No active traceflags
00:00000:00001:2006/06/02 05:19:49.56 kernel
Component Integration Services loaded; version
'Component Integration Services/12.0.0.6/P/EBF
10629 ESD 1/HP9000-829/HP-UX 11.0/1918/32bit/
FBO/Fri Oct 18 16:29:20 2002'.
00:00000:00001:2006/06/02 05:19:49.56 kernel
Component Integration Services: using 'Sybase
Client-Library/12.0/P-EBF10230 INTERNAL/
DRV.12.0.1/hpux/HP-UX 11.00/BUILD120-012-1/
OPT/Fri Apr 19 10:06:58 2002'
00:00000:00001:2006/06/02 05:19:49.56 server
Opening Master Database ...
00:00000:00001:2006/06/02 05:19:49.60 server
Loading SQL Server's default sort order and
character set
www.zte.com.cn
00:00000:00001:2006/06/02
05:19:49.60 server Loaded default Unilib
conversion handle.
00:00000:00002:2006/06/02
05:19:49.60 kernel network name scp,
type ether, port 4100
00:00000:00001:2006/06/02
05:19:49.60 server Timestamp in page
623 of text object 45 is out of sync. Please
run DBCC REBUILD_TEXT(45) to fix this.
00:00000:00001:2006/06/02
05:19:49.76 server Timestamp in page
621 of text object 45 is out of sync. Please
run DBCC REBUILD_TEXT(45) to fix this.
00:00000:00001:2006/06/02
05:19:49.77 server Recovering database
'master'
00:00000:00001:2006/06/02
05:19:49.78 server No such message:
624
00:00000:00001:2006/06/02
05:19:49.78 server Cannot recover the
master database, exiting.
00:00000:00001:2006/06/02
05:19:49.78 kernel ueshutdown: exiting
Analysis
The single server started the database
in the upgrade process. This problem
appears only when the single server
is recovered to the cluster mode. This
Integrated Intelligent Network 15
February 2008 Issue 82
indicates the problem is not caused by the
upgrade, but it is induced in the upgrade
process. Analyze the log. The following
important information is found:
1. server Cannot recover the master
database, exiting.
2. server Timestamp in page 621 of
text object 45 is out of sync. Please run
DBCC REBUILD_TEXT(45) to fix this.
The first information indicates the
cause of the database start failure. The
second information indicates the method
to solve this problem.
Action
1. Edit RUN_servername
Add the following at the end of the
command line:
-T3607
2. Start ASE in the single user mode
using the following commands:
16 Maintenance Experience
$cd install
$startserver -f RUN_servername -m
3. Execute DBCC REBUILD_TEXT(45)
4. Try to start the database in the single server
mode. The database is started successfully.
5. Try again in the cluster mode. The database
is started successfully.
There are other methods to recover the master
database. Please refer to the Sybase training
manual provided by ZTE. The above procedure is
very useful for solving such problems.
Brief Summary
In the case of a major failure on which the
master database cannot start, locate the problem
according to the log as soon as possible. If you
cannot solve the problem according to the manuals
on site, contact ZTE's local office personnel for
help as soon as possible. It is very important to
enable logging. The problem should be analyzed
specifically according to the actual conditions.
 www.zte.com.cn

Cannot Edit the Segments with

More Than 255 Characters on a
Sybase 11.92 Client
Li Lin, ZTE Corporation

Product: ZXIN10
Keyword: Sybase 11.92 client, 255 characters

Problem Description Sybase 11.92 client only supports up to

When running the SMS program to edit a KPI
formula on a Sybase 11.92 client, segments with
more than 255 characters are cut off. Meanwhile,
when executing an insert command in the SQL
Advantage, segments with more than 255
characters are also cut off.
Background
Sybase database version: Sybase12.53.
Sybase client version: Sybase 12.53.
Analysis
It is located as a Sybase client problem. The
255 characters. So no application program
running on the client can select, insert or
update more than 255 characters when
they access the database. The client must
be upgraded to Sybase 12.5 or above.
Action
Uninstall the previously installed
Sybase 11.92 client and install Sybase
12.5 client. Try again, then the problem
disappears.

Integrated Intelligent Network 17

February 2008 Issue 82
Sybase Installation Failure
Under Suse Linux
Feng Kefeng, ZTE Corporation
Product: ZXIN10
Keyword: Suse, Sybase
Problem Description
Sybase database always fails to be
installed under Suse Linux. The following
error messages appear:
13:16:01.01 kernel os_create_region:
can't allocate 42510336 bytes
13:16:01.01 kernel kbcreate: couldn't
create kernel region.
13:16:01.01 kernel kistartup: could not
create shared memory
13:16:01.09 kernel Use license file
/home/sybase/SYSAM-1_0/licenses/
license.dat.
Action
It is doubted the problem is caused by
the size of the shared RAM according to
the error messages. Use the RAM size
modification command to change the size
18 Maintenance Experience
to the half of the physical RAM. Install the database
again, then it is successful. The procedure is as
follows:
1. In YaST->System->Runlevel Editor, open
Export Mode and find the boot.sysctl service.
Define the service to run at Level B.
2. Create an /etc/sysctl.conf file and add the
following content:
kernel.shmmax = 536870912
(1G RAM = 1024M 1024 1024byte, then set
it to the half size.)
Where, the capacity of kernel.shmmax should
be 50% of the physical RAM.
3. Save and exit. Run sysctl p to validate
it. The boot.sysctl service has been set to run
automatically. The parameters can be applied
automatically every time when the system is
started.

IP Cannot Play Announcements
in the CDMA Service Call Flow
Li Huaide, ZTE Corporation
Product: ZXIN10
Keyword: Call flow, IP announcement playing
Problem Description
The CDMA PPC service uses IP to play
announcements. The service uses IP to play a
"balance is too low" announcement to the calling
party when the user's balance is too low. But the
IP sends a REL message automatically when it
receives the IAM message from the MSC.
Background
In the CDMA OCS system commissioning on
an overseas office site, the IP, which is used to play
announcements in the call flow of the PPC service,
sent a REL message to the MSC immediately when
it received the IMA message from the MSC without
www.zte.com.cn
any reason for the release.
Analysis
The CDMA network uses TLDN to
locate the settings. The length of the
international TLDN number set on the IP
must range from 10 to 12 digits according
to the requirement. But the TLDN set on
the IP is actually a 9-digit number.
Action
Modify the length of the TLDN number
set on the IP device to meet the system
requirement.
Integrated Intelligent Network 19
February 2008 Issue 82
MRB Tone Playing Circuits
All Busy
Cheng Tiecheng, ZTE Corporation
Product: CRBT
Keyword: VPB, busy
Problem Description
Users cannot hear CRBT tones.
Background
The called party switch in the CRBT
system in which the problem occurred
is retrofitted. The system uses 3 MRB
modules.
Analysis
1. Perform dial-up tests. Dial a
subscriber number many times. No CRBT
tone can be heard every 2 to 3 times.
So it can be determined that it is not a
system fault. The service does not provide
any alarm message. It is preliminarily
determined that it is a MRB resource or IP
problem.
2. Track IP messages through the
foreground ipmtrace. It is found there
are a lot of error messages. Most of the
messages are resource error messages,
and the tone played is the ring back tone
No.140.
3. Check the use of VPB. All the 360
resources of the three VPBs are used.
The system capacity is 50,000. The 3
MRB modules configured are enough
20 Maintenance Experience
for the capacity. Check a random user who has
an announcement playing request. It is found the
user does not exist in the CRBT system. So it is
determined the problem occurred on the HLR,
which routed the non-CRBT user to the CRBT
system.
4. Check the core network associated with the
problem. The fact is the same as described above.
All the users, more than 100,000 approximately,
in the core network have subscribed to the CRBT
service, but only 50,000 of them have numbers
issued in the CRBT system. This causes non-CRBT
subscribers request resources in the CRBT system,
which finds the subscribers do not exist and plays
ordinary ring back tone No. 140 to them. This also
uses a VPB resource, which causes valid CRBT
subscribers cannot hear CRBT tones sometimes.
Action
Modify the data on the HLR in the core network
to remove the CRBT subscription information of the
non-CRBT subscribers from the HLR. This releases
the resources and thus allows CRBT subscribers to
use the service normally.
Brief Summary
This problem is caused by the loose
management of the customer.

ETC Failure in Independent IP
Announcement Playing
Tang Genmao, ZTE Corporation
Product: ZXIN10
Keyword: ETC
Problem Description
After SCP delivers an ETC, MSC returns an
ETC Failed message directly, which results in an
announcement playing failure.
Background
An independent IP is used to play
announcements to the GSM users. Two types of
devices, ZTE MSC and Siemens MSC, are used in
the network.
Analysis
After SCP delivers an ETC, MSC returns an
www.zte.com.cn
ETC Failed message directly, which results
in an announcement playing failure.
Analysis: Decode the ETC.
0 1 2 3 4 5 6 7 8 9 A B C D E F
================================
00| 30 20 80 0A 80 03 13 00 19 89 41
40 17 81 81 05
01| 00 10 02 65 85 83 06 19 89 41 40
27 11 A7 03 82
02| 01 0
The three italic parts correspond to the
subsidiary address, scfid, and related ID,
respectively.
Integrated Intelligent Network 21
February 2008 Issue 82
Decode the successful ETC in the
network:
0 1 2 3 4 5 6 7 8 9 A B C D E F
================================
00| 30 12 80 0B 80 03 13 88 88 88 41
10 10 11 32 A7
01| 03 82 01 01
The italic part indicates a subsidiary
address, which includes four parts. 80
03 13 denotes number attribute. 88 88
indicates the subsidiary address of the
service. 88 14 01 is SCFID (configured in
zxin10.ini). 01 11 32 indicates the related
ID (distributed by the platform).
The subsidiary address, SCFID and
related ID of the ETC can be delivered
separately or packed to the subsidiary
22 Maintenance Experience
address for delivery. Siemens MSC support packed
delivery only.
SCP controls the delivery mode through
the IPRoutingFlag set in zxin10.ini. 0 indicates
separate delivery. 1 indicates packed delivery.
Action
Change the value of IPRoutingFlag to 1 in
zxin10.ini. After restarting the platform, ETC can be
delivered successfully and announcements can be
played successfully.
Brief Summary
Generally, IPRoutingFlag seldom requires
the modification. However, if the system is
interconnected with a device of other vendors, try
to modify the parameter to locate the problem in
the case of ETC failure.

Noisy Tone Playing in an
American Office
Wu Jun, ZTE Corporation
Product: ZXIN10
Keyword: tone playing
Problem Description
The service and platform are installed
successfully in the fixed-network Intelligent
Network (IN) environment. Functions of the 300
Service can be tested successfully. After loading
the new version of service tones, the tones are
played badly. There are two situations: 1. Noisy. 2.
Unstable and shivering.
Analysis
After consulting several experts, the problem is
located to a special rule in a different country. The
transmission in the U.S., which is T1, is different
from that in other countries. T1 transmission
requires a -law tone file. ZTE uses CCITT A-Law
8.000 kHz 8-bit mono wave files. Switching experts
say the format that ZTE uses obviously does not
meet the requirement. So this problem might be
solved by unpacking the .64 file, converting it into
-law, repacking it and uploading it to the server.
But after trying this method, the problem persists
without any change or improvement. This symptom
implies two points. One is that the thinking is not
correct. The other is the conversion method is not
proper. The analysis shows that the tones were
played normally before. The problem appears only
when the new version of tone files are used. So
the problem should be located in the file format.
Reanalyze the announcement upload and loading.
www.zte.com.cn
There are several combinations of laws.
1. The wav file is a-law. The 64 file is a
combination of a-law.
2. The wav file is -law. The 64 file is a
combination of -law.
3. The wav file is -law. The 64 file is a
combination of -law.
4. The wav file is a-law. The 64 file is a
combination of -law. However, switching
experts do not agree with this conjecture.
After several tries, tones are played
normally using the last combination.
Action
In American offices, the a-law wav file
must be packed into a -law .64 file before
being loaded. That is, unpack the .64 file in
the new version, keep the file unchanged
(CCITT a-law, 8K). Create a new -law .64
file through tone management and upload
the tone file.
The following is a detailed procedure
(including how to unpack and repack the
.64 file in the old version).
1. Put the original tone files of the
version to c:\zxj10\tone on the 129 Server.
2. Run the tone management program,
which is c:\zxj10\tone\tonesh.exe.
3. Open the tone management tool.
Integrated Intelligent Network 23
February 2008 Issue 82

The menu as shown in Figure 1 files you want to replace and change them to the files
appears. corresponding to the file numbers.
4. In the menu as shown in Note: Make sure the files are CCITT A-Law 8.000
Figure 2, click the select tonefile kHz 8-bit mono wave files. It is recommended to use the
button in the tone file selection goldenwav software.
tab page to select the desired file. 7. Pack the wav files into a .64 file and upload it. First
Note: To unpack the unicom.64 you should put the files in the corresponding directory.
file, select it and click OK. 8. Click Batch input tone data in the Tone transfer
5. Open the tone transfer tab tab page, as shown in Figure 4.
page. Click the batch output tone Note: Make sure to check Generate New ToneFile
data button. In the pop-up window, and _law, and select a new file name. After completing
set the path for the unpacked wav the setting, click OK. In the pop-up window, select the
files, as shown in Figure 3. Click
the Confirm button.
Note: After completing this
step, the .64 file is unpacked
successfully. All the wav files
appear in the specified directory.
Check the format of the files.
6. Get ready for repacking.
For example, make the tone

Figure 3. Selecting the Directory to Save Tone Files

Figure 4. Selecting the Format of the Tone Files to be Created

Figure 1. Opening the Tone Management Tool

Figure 2. Selecting the Tone File to be Uploaded Figure 5. Creating a Tone File - 1

24 Maintenance Experience
 www.zte.com.cn

Figure 6. Creating a Tone File - 2

Figure 8. Uploading a File - 1

Figure 9. Uploading a File - 2

Figure 7. Creating a Tone File - 3

directory saving the wav files. Confirm button to upload the file,
9. The system starts to input tone data, as shown in as shown in Figure 9.
Figure 6. After completion, the following window appears:
10. Click Generate file in the Tone transfer tab page, Brief Summary
as shown in Figure 7. There are many reasons to
After completion, the file is created successfully. cause the noise. After roughly
11. Click Load tone in the Tone transfer tab page to locating the problem, find out all the
upload the .64 file created in the previous step, as shown possible (combinations of) reasons
in Figure 8. and have a try. Do not be restrained
12. Confirm all the tone numbers and click the by conventional thinking.

Integrated Intelligent Network 25

February 2008 Issue 82
The Shortest GT Code in GT
Translation Must be 3 Bits
Zhu Yu, ZTE Corporation
Product: ZXIN10
Keyword: GT translation, GT code length
Problem Description
All the digits between 0 and 9 are
translated into GT codes. GT translation
may still fail.
Background
In the commissioning of the Call Back
Center service, there is no response after
the ICA message is sent to the fixed-
network SSP. This symptom is generally
caused by GT translation failure according
to the experience. However, site personnel
have translated all the digits between
0 and 9 to GT codes according to the
requirements described in the product
documentation.
An expansion of the problem is, if
only the ten digits between 0 and 9 are
translated on any device, GT translation
26 Maintenance Experience
may still fail.
Analysis
Surely, such a message will neither be
terminated nor forwarded after being sent to
the fixed-network SSP. Mostly it is caused by a
GT configuration or number analysis error. Site
personnel have translated all the digits between
0 and 9 and the problem still exists. The only way
in this case is to contact the product development
personnel for help.
The GT code must be 3 bits at least according
t o t h e d e v e l o p m e n t p e r s o n n e l . D e l e te th e
translated digits between 0 and 9. After translating
the first three digits of the number received, the
problem is solved.
Action
The GT code must be 3 bits at least according
t o t h e d e v e l o p m e n t p e r s o n n e l . D e l e te th e
translated digits between 0 and 9. After translating
the first three digits of the number received, the
problem is solved.
Brief Summary
The length of a GT code must be no less than 3
bits in GT translation. Otherwise the GT translation
will not be validated.

ZXCOMM Process Cannot be
Started After Configuring the
NEWMC Module
Xia Rui, ZTE Corporation
Product: ZXIN10
Keyword: newmc, zxcomm
Problem Description
NEWMC is an SIU emulation program
developed by ZTE. It is installed in the Windows
system. It emulates SIU service triggering for
service test. After adding a NEWMC module on
SCP according to the configuration instruction in
commissioning, the zxcomm process cannot be
started.
Analysis
Check zxcom.log. The following error is
reported:
F[zxcomm.c] L[694] ipaddress1 is null of section
module1 in file /home/zxin11/etc/win_mgt.ini
www.zte.com.cn
11-30 9:45:54:11 F[zxcomm.c] L[254]
GetConfig() error!
This error report indicates that the
ipaddress1 of the MEWMC module has
not been configured. After setting the
ipaddress1 at random, zxcomm can be
started normally.
For the platform processes in win_mgt.
ini, according to the consultation with the
R&D personnel, those whose module
number is smaller than 128 must be
configured with ipaddress and ipaddress1,
even if there is one address only.
Integrated Intelligent Network 27
February 2008 Issue 82

SMAP Clients with Different IDs

Cannot Log in at the Same Time
Li Dan, ZTE Corporation

Product: ZXIN10
Keyword: SMAP, different ID, Log in

Problem Description Action

A program can run at the same time
on the two SMAP clients being installed.
Otherwise one of the clients will exit
automatically.
Background
The PPC client will be logged out
forcefully when two different IDs try to log
in at the same time. Generally, the one that
logs in firstly will be forcefully logged out.
Check the value of loadid under \
hkey_local_machine\software\zxin10\smap in the
SMAP registry. If the values of the loadid of the
two SMAP devices are the same, the problem will
occur. Delete the loadid value of any of the two
devices and leave it blank. The problem is solved.
After logging into any program on the SMAP
again, the system will assign a value to loadid
automatically.

Corrective Action for Service

Load Failure
Wu Jun, ZTE Corporation

Product: ZXIN10
Keyword: Version Load

Problem Description service loaded is MVS 81.

When we reload a service previously
loaded on the platform V3.63, the Analysis
service is loaded directly instead of being The analysis of the whole process finds no
unloaded, which causes a load failure. The SCP database operation is performed when the

28 Maintenance Experience

service is loaded, that is, no SCP database script is
executed. Only a CP file is uploaded to the service
directory. The FTP process is actually uploaded to
the service directory by the user zxin10. But why
does an error message appear when the file is
uploaded successfully?
After checking the zxom log, the following error
message is found:
3-14 14:6:20:6 F[slpm.c] L[910] SLPM LOAD
SERVICE SUCCESS!
3-14 14:6:20:57 F[sdfodbc.c] L[2542] ERROR
in Exec:'insert into zxinsys.zxin_re
sult values(62,1,1,1,rtrim('[load the xsmp81
service, version 1.0] [scp133]: Successful
'),0,'2007.03.14 14:06:20')'
3-14 14:6:20:57 F[sdfodbc.c] L[1782]
ConnectNo=1 OCI ERROR CODE = 1
3-14 14:6:20:57 F[sdfodbc.c] L[1784]
ORA-00001: unique constraint (ZXINSYS.
I_RESULT) violated
After the CP file is uploaded, no SCP database
operation is performed in deed, which is actually
required. That is, an operation log must be written
into the SMP database. But since an error is
recorded, no new information can be displayed
normally. This is a common confliction error due to
www.zte.com.cn
database uniqueness restriction.
Why does such a uniqueness
restriction error occur? After checkup,
we find a service is loaded, which is the
insertion to the following four tables:
Zxinsys.zxin_identity
Zxinsys.zxin_service
Zxinsys.zxin_servicedevice
Zxinsys.zxin_result
To avoid such an error in loading the
service, make sure to avoid any conflict in
the four tables.
Action
Check the four tables and delete
the conflicting records. Restart the host
or release the RAM record. Restart the
database and the zxin10 process. Then
the service is loaded normally.
Brief Summary
The problem may not occur in normal
service load conditions. If the problem
occurs due to improper operation, solve
the problem with the above the method.
Integrated Intelligent Network 29
February 2008 Issue 82
Abnormal Billing
Cheng Tiecheng, ZTE Corporation
Product: ZXIN10
Keyword: Billing, free of charge
Problem Description
The billing in an office is abnormal,
resulting in all the calls are free of charge.
Signaling trace showed that the billing
plan for the calling party is correct. After
synchronizing the fee rates at 15:00, the
problem is solved.
Background
The platform version is 3.51.02.10.
Analysis
1. When we tried to solve the problem
by synchronizing the fee rates, no new
fee rate was prompted, that is, no fee
rates were changed, which excludes the
possibility of fee rate changes.
2. The CDR shows that all calls were
free of charge after 11:20 a.m. on that day.
The billing log shows that the free rates
were synchronized at 11:20, 11:25 and
11:38, so it is determined that it is related
to the abnormal billing.
The billing log shows that the fee
rate configuration modified during
30 Maintenance Experience
synchronization has no problem and has no impact
on the charge free. Further analysis shows that the
charge program on the synchronizing client has
a problem. The c:\zxin10\smap\transfee.dll file is
too old and does not match the version. The old
version of fee rates are stored as integers, so the
old transfee.dll only supports integer conversion.
The new version uses float type of fee rates. The
old transfee.dll cannot process it properly, so all the
fee rates in the created charge.dat are 0, resulting
in abnormal billing after synchronization.
Action
Synchronize the fee rates using the new
version of client. The problem is solved.
Brief Summary
Generally an Intelligent Network (IN) has
several SMAP clients. Maybe some clients not
used frequently have not been updated.
The charge.exe program using the old version
of client can also open, configure, and synchronize
the fee rates, which causes the problem.
It is necessary to make sure that all the client
programs match the latest version.
 www.zte.com.cn

SCP CPU Overload

Cheng Tiecheng, ZTE Corporation

Product: CRBT
Keyword: CPU, overload

Problem Description following CPU information is displayed:

The SMS often reports CPU overload alarms: * * * * * sar 1 10|awk '/Average/{print
9- 4 17:38:30:16 F[overload.c] L[300] CP $1, "0 0 0", $NF}' >/tmp/.zxin_tmp_cpu;mv
Overload ! Service: value[128] /tmp/.zxin_tmp_cpu /tmp/.zxin_cpu
9- 4 17:38:30:16 F[overload.c] L[300] CP The development personnel affirm the
Overload ! Service: value[9128] current version is 3.51.02.10. The new
version uses getsysinfo.sh to collect the
Background statistics of system information. So it has a
The platform version is 3.51.02.10. conflict with the old version, which causes
the problem.
Analysis
The SMS CPU usage is 96%. /tmp/.zxin_cpu Action
shows: Modify the mytabs file. Delete the CPU
Average 0 0 0 4.00 statistics task from the file and set it to
In fact, the CPU usage shows no problem: collect statistics using getsysinfo. The
# sar 1 100 problem is then solved.
AIX scp3 3 5 00CECECB4C00 09/04/07 That is, mytabs contains the following
System configuration: lcpu=8 task:
17:39:31 %usr %sys %wio %idle physc * * * * /home/zxin10/bin/getsysinfo.sh
17:39:32 0 1 0 99 3.99 >/dev/null 2>&1
17:39:33 0 0 0 100 4.00
17:39:34 0 1 0 99 4.00 Brief Summary
Note the information collection mode
So it can be concluded that it is an improper in the new version. Make sure the version
overload error report. Check the system tasks. The must match the statistics collection.

Integrated Intelligent Network 31

February 2008 Issue 82

IMP Link Setup

Zhao Hongzhi, ZTE Corporation

Product: ZXIN10
Keyword: IMP, link setup

Problem Description Action

A process on the Interface Message Add a space between the IP address and the
Processor (IMP) does not set up any link. semicolon. Then the link is set up successfully.

Analysis Brief Summary

No problem is found in all the settings. Make sure to add at least one space between
Later it is found in itcom.ini that there is no the IP address and the semicolon when you
space between the IP address corresponding configure itcom.ini for the IMP.

to the process and the semicolon.

32 Maintenance Experience
 www.zte.com.cn

Analysis for Failed Card

Creation via Web by
Independent VC
Wu Jun, ZTE Corporation

Product: OCS
Keyword: Independent VC

Problem Description no independent server for the database.

Install the WEB server for the OCS system.
After the successful installation, operate the WEB
page to create card files, it displays: db access file
directory failed
Version:
WASV2.01.01
WSMAP2.01.21
IIN-INDEPENDENT-VCENUV1.01.02
IMPV1.3-INDEPENDANT-VCENUV1.01.01
Networking information
We only have one WEB server for VC. There is
And the ZTEsoft database is used as the
database part.
Analysis
To understand why we have this
problem, we must first know the purpose of
creating card files and the exact operations
that we have performed. The purpose of
creating card files is to create passwords
for the created VC cards. Before selling
a card, the switch owner must obtain the

Integrated Intelligent Network 33

February 2008 Issue 82

pin information for the password of the card. The

Figure 1. Creating a Directory for Created Card Files on the Platform
procedure for creating a card file is as follows: Log
into the Oracle database server via the VC system.
Perform an operation to create a card file. The
operation is to invoke an operation similar to writing
export of DBMS of Oracle, that is, to execute the
storing process of the Oracle database and then
perform a file-writing operation. A specific system
parameter of the Oracle database determines
the writing. And then IMP uses parameters
configuration to fetch the file via FTP.
In the configuration file, /home/oracle is
configured as the destination address for fetching
the card file. But for SUN servers, the home
directory is unwritable. Therefore, /home/oracle
does not exist, and the above file cannot be
created. Of course, we cannot log in to /home/
oracle to fetch the card file. For the same reason,
the IMP cannot fetch the file via FTP. Obviously,
card files cannot be created. In addition, we detect
that the directory for created card files in the
system parameter configuration is empty. All these
lead to the failed card creation.

Solution
1. Create a directory on the platform for
Figure 2. Configuring the Path for Created Card Files on Oracle storage as shown in Figure 1. Create a directory
Database on the Oracle database server for the created files
(mandatory) as shown in Figure 2.
2. Modify the core parameters of the Oracle
database to change the dir for data files into the
directory we just created. And then restart the
database, as shown in Figure 3.
3. After the database is restarted, try again to
create the card files. The creation succeeds.

Figure 3. Restarting the Oracle Database
Brief Summary
To t r o u b l e s h o o t p r o b l e m s f o r t h e O C S
system, an important principle is: understand the
processing method of the system and how it works.
By this means, you can locate the fundamental
cause of the problem.

34 Maintenance Experience
 www.zte.com.cn

Brief Description of Service

Logs for vsftp Used by Linux
Web Server for CRBT
Xia Rui, ZTE Corporation

Product: CRBT
Keyword: Linux vsftp logs

Problem Description tongs, vsftpd.log is created in the /var/

The Linux web server uses vsftp as the ftp log directory. The file records your ftp
program. FTP failures occur while CRBT tongs operations.
are uploaded or downloaded. When a FTP Example:
failure occurs, we can do nothing but turn to our Mon Nov 5 15:20:25 2007 1
experienced colleagues for help. It is because we 192.200.1.141 0 /0/5/5_2004_8.wav b _ i r
have no logs to troubleshoot the problem. To solve zxin10 ftp 0 * i
the problem independently, we need to enable the Mon Nov 5 15:21:02 2007 1
log function of vsftp. 192.200.1.141 335511 /0/5/5_2004_9.wav
b _ i r zxin10 ftp 0 * c
Analysis Mon Nov 5 15:21:02 2007 1
When you upload and download CRBT 192.200.1.152 16384 /0/5/5_2004_9.wav

Integrated Intelligent Network 35

February 2008 Issue 82
b _ o r zxin10 ftp 0 * i
The above is the log content.
Explanation of the first line:
Mon Nov 5 15:20:25 2007 1
192.200.1.141 0 /0/5/5_2004_8.wav b _ i r
zxin10 ftp 0 * i
Mon Nov 5 15:20:25 2007 the time
when the fpt occurred
1 Total duration of the ftp process;
unit: second.
192.200.1.141 Address of the opposite
end
0 Size of the transferred file. Note
that it is not the size of the file; it is the size
of the transferred file. For example, the file
size is 500byte. If the file is transferred, it
is 500. If the transfer failed, it should be 0.
/0/5/5_2004_8.wav ftp directory
and filename
b transfer in the bin mode
_ special operation identifier. It
indicates that there is no special operation
during the transfer
i indicate income, the file is coming
in
36 Maintenance Experience
r log in as a real user.
a: log in as an anonymous user;
g: log in as a guest user.
zxin10 the login username
ftp service name
Authentication method
* authenticate id. As the previous parameter
is set to 0, this parameter is disabled
I indicates the transfer is not completed, c:
the transfer is completed
The first line is for the failed creation due to
the missing directory. The second line is for the
successful creation after the directory is created.
Compare these two lines.
Solution
1. Modify the configuration file /etc/vsftpd/
vsftpd.conf
2. Modify or add the following:
xferlog_enable=YES
xferlog_file=/var/log/vsftpd.log
Under normal conditions, you only need to
eliminate the # before the two lines.
Execute /etc/init.d/vsftpd restart to restart the
database to make the configurations become
effective.

Detailed Description of Linux
Web Server for CRBT
Xia Rui, ZTE Corporation
Product: CRBT
Keyword: linux web server
Introduction to Web Software of
Linux Version
Even engineers who have installed CRBT web
servers can hardly understand the relationship
between was, apache, and tomcat. To understand
the relationship between apache and tomcat is
even harder. Some engineers may have used EBA
weblogic for web servers. So we are confused and
do not know which software are installed.
Apache and Tomcat
Apache and Tomcat are explained together, not
only because they are installed at the same time,
www.zte.com.cn
more importantly, they are functionally
related and complementary to each other.
A p a c h e i s a w e b s e r v e r. I t o n l y
supports static web pages, e.g. html. It
does not support dynamic web pages
s u c h a s a s p , p h p , c g i , a n d j s p . To
run JSP on Apache, an interpreter is
needed to execute JSP pages. As the
interpreter is Tomcat, so why we need
JDK? The reason is, if JSP is to connect
the database, it needs JDK to provide
Integrated Intelligent Network 37
February 2008 Issue 82
the driver for the connection. Therefore,
Apache+Tomcat+JDK are needed by the
web server to run JSP. The advantages of
the combination are:
If static pages are requested by the
client, only Apache needs to respond. If
dynamic pages are requested, the Tomcat
server will respond. As JSP interprets
codes in the server, this combination
reduces Tomcat overhead.
Apache is characterized by simplicity,
high speed, stable performance, and can
be used as a proxy server. It was initially
applied to small-sized or test-oriented
Internet networks, and later applied to
various Unix systems. It has perfect
support for Linux especially. Apache
contains many products. It supports SSL
and multiple virtual hosts. Apache has a
process-based architecture. As processes
consume more system resources than
threads do, Apache is not suitable for a
multiprocessor environment. Therefore,
when it comes to capacity expansion for
an ApacheWeb site, the usual method is to
add servers or expand the cluster nodes
instead of adding processors. Apache
is successful for its open source codes,
its open development team, its support
to cross-platform applications (can run
on almost all Unix, Windows, and Linux
platforms), and the portability.
For our CRBT web servers:
What Apache needs to do is to
38 Maintenance Experience
construct a platform to provide HTTP services. As
to Tomcat, it needs to construct a platform for the
applications by ZTE.
Relationship between WAS Software and
Apache, Tomcat
In short, WAS is a software package containing
Apache, Tomcat, and JDK. It uses the default
configuration files and simplifies the installation.
It enables the engineers to easily deploy the web
applications. Firstly, the easy application enables
engineers unfamiliar with Apache and Tomcat to
deploy the service easily. On the other hand, when
problems occur, we will have to depend much more
on our developers than other companies do.
Apache+Tomcat and other web software,
such as weblogic
Free software with open source is preferred, but
this is not the only reason. Apache+Tomcat is the
most frequently used software in web networking.
Thanks to the open-source, we can modify them
easily.
Introduction to the related
configuration files
httpd.conf of Apache
httpd.conf is the main configuration file of
Apache. The file contains many configuration
items, but only a few determine the deployment of
web servers. They are:
DocumentRoot: Root directory of the Web.
This item determines the position of service
deployment.
F o r C R B T, t h e r e a r e t w o c o m m o n
configurations:
DocumentRoot /home/zxin10/was/tomcat/
webapps/ROOT
or DocumentRoot /home/zxin10/was/tomcat/
webapps/ROOT/webapps
You will have a question if you understand this
 www.zte.com.cn

configuration item. The directory for the CRBT DirectoryIndex index.html index.htm
service is /home/zxin10/was/tomcat/webapps/ index.jsp
ROOT/webapps/colorring, but why not the above ErrorLog logs/shsc-error.log
two directories? The reason is: WAS is a platform CustomLog logs/shsc-access.log
for the company applications. The platform is warn
not only for the CRBT service, it is also for many <Location "/*.jsp" >
other services. So it is inappropriate to choose JkUriSet group loadbalancer
colorring as the directory for service deployment. </Location>
Therefore we create index.html under the ROOT or <Location "/*.action" >
the webapps directory. As the service deployment JkUriSet group loadbalancer
directory is set as ROOT or webapps, Apache will </Location>
search the directory first for the file. The function </VirtualHost>
of the file is to make a transfer to the colorring
directory. If it is another application, it will be <VirtualHost *>
transferred to the corresponding directory. ServerAdmin admin@tomcat.apache.
If it is only for the CRBT service, we can set org
the root directory to /home/zxin10/was/tomcat/ DocumentRoot /home/zxin10/was/
webapps/ROOT/webapps/colorring. tomcat/webapps/coloring/manager/
Listen: Listener port ServerName 192.200.1.151
The main page in CRBT service is the dynamic DirectoryIndex index.html index.htm
page index.jsp, but Apache only supports static index.jsp
pages, so we only modified the port, we did not ErrorLog logs/shsc-error.log
modify the port through which you visit the CRBT CustomLog logs/shsc-access.log
page. warn
ServerRoot: Configuration of Apache <Location "/*.jsp" >
management page JkUriSet group loadbalancer
After WAS is installed, the default server root is </Location>
/home/zxin10/was/apache. <Location "/*.action" >
After WAS is installed and the Apache service JkUriSet group loadbalancer
is started, you only need to input the WEB IP </Location>
address in the IE address bar to open the page. If </VirtualHost>
the page cannot be opened, it indicates that WAS You can see the differences between
was not properly installed. the above configurations:
<VirtualHost *> virtual host When the floating address
You can use virtual hosts to make customized 192.200.1.150 is used, the colorring
configurations. You can configure multiple virtual directory provides web services.
hosts to use CRBT web more easily. When the local address 192.200.1.151
<VirtualHost *> is used, the colorring/manager directory
ServerAdmin admin@tomcat.apache.org provides web services.
DocumentRoot /home/zxin10/was/tomcat/ It looks as if there are two Apache
webapps/coloring/ services on the computer. Though virtual
ServerName 192.200.1.150 hosts enable us to use Apache in an

Integrated Intelligent Network 39

February 2008 Issue 82

easier way to provide services, it also Allow from all

increases the configuration items. This
shall be noted.
Alias: Virtual directory
It is used to map virtual directories to
real directories. What is a virtual directory?
The root service directory is set as we
set DocumentRoot. For Apache services,
the directory is /. If you need /tomcatlog,
Apache will search the DocumentRoot
directory. Generally, Apache searches
ROOT. If you do not want to set the
directory under ROOT, the configuration
item allows you to set it to a specified
directory. For example:
Alias /tomcatlog/ "/home/zxin10/was/
tomcat/logs/"
<Directory "/home/zxin10/was/tomcat/
logs/">
Options Indexes MultiViews
AllowOverride None
Order allow,deny
</Directory>
Define /tomcatlog to /home/zxin10/was/tomcat/
logs/
Configuration file of Tomcat: server.xml
Generally, Tomcat works well with the default
setting in its configuration files. Sometimes we
change the port number through which Tomcat
provides services. The table 1 provides brief
information for your reference.
Other configuration files such as config.xml,
socketman.xml
For detailed information on these configuration
files, refer to the installation and configuration
description attached to the version.
Common problem analysis
Procedure for handling failed
startup of web services
Symptom
1. Web page cannot be opened; internal error
is reported.

Table 1 (1)

Element Attribute Description

Server port Specify a port to listen requests to shut down tomcat

shutdown The command character string specified to send to the port

Service name Name of the specified service

Connector (indicates
the connection The port number to be created on the specified server; client
port
between the client requests will be listened on the port.
and service)
minProcessors The number of threads created as the server starts up

maxProcessors The maximum number of threads allowed to be created

If true, you can invoke request.getRemoteHost() to query

enableLookups DNS to obtain the real host name of the remote client.
If false, it does not query DSN, but only returns the IP address

The port number redirected after a specified server receives

redirectPort
an SSL transmission request while handling an http request

Specify the number of requests allowed to be queued when

acceptCount all the available threads are used to handle requests. Extra
requests will not be handled.

connectionTimeout The specified time for timeout (unit: ms)

40 Maintenance Experience
 www.zte.com.cn

Table 1 (2)

Element Attribute Description

Engine (indicates the

request processor
in the specified The name of the specified default host for handling requests.
defaultHost
service receives and It is same as the name of at least one host.
handles request s
from Connector)

Context (refers to
one web application
program, generally
is a WAR file. For docBase The path for application programs or for storing WAR files
information on WAR,
refer to servlet
specifications)

Indicates the url prefix of web application programs. The

path
requested url is http://localhost:8080/path/****

This attribute is very important. If true, Tomcat automatically

checks the changes of the two directories of application
reloadable programs: /WEB-INF/lib and /WEB-INF/classes. And Tomcat
automatically loads new application programs. It supports
changing application programs without restarting Tomcat.

host (a virtual host) name Name of the specified host

The basic directory for application programs. That is the

appBase
directory containing application programs.

If true, Tomcat automatically extracts WAR files. Otherwise,

unpackWARs TOMCAY does not extract them and run the application
program from the WAR file directly.

Logger (logs, debug Name of the specified class used by logger. The class shall
className
or error information) accomplish the org.apache.catalina.Logger interface.

prefix Prefix of the specified log file

suffix Suffix of the specified log file

If true, time shall be added into the log file name. For
timestamp
example: localhost_log.2001-10-04.txt

Realm (the database

storing usernames, Name of the specified class used by Realm. The class shall
className
passwords, and accomplish the org.apache.catalina.Realm interface.
roles)

Valve (has similar

function as Logger.
Name of the specified class used by Valve, for example, org.
The attributes
className apache.catalina.valves. The AccessLogValve class records
description for prefix
information on application program access
and suffix are same
as Logger)

directory Storage location of the specified log file.

Two values. The common mode records the remote host
name and IP address, the username, date, the character
pattern string of the first line, HTTP response code, and the sent
byte. The combined mode records more values than common
does.

Integrated Intelligent Network 41

February 2008 Issue 82
2. Use netstat to check the connection
status, port 4100 is in the Established
state.
3 . To m c a t c a n n o t b e s t a r t e d
completely; stdou.log does not print logs.
Failure cause
The cause can be classified as follows:
1. Errors with configuration files related
to the web server lead to the failed startup
of web service
2. Database connection between the
web server and SMP/SCP failed to be
established
Solution
1. Change debug to 9 in config.xml;
restart Tomcat, observe stdout.log. The log
prints the error occurred at startup.
2. If it is an error with the configuration
file, replace the incorrect configuration file
with the correct one and make a test.
3. If the connection to the database
failed, check the database log on SCP
to determine whether there are errors
with the database. Focus on problems
including deadlocks, too many connections
to the database, or insufficient space on
the database.
4. If there are no errors in the
database, we need to locate the cause of
connection failures step by step. First we
use the sybase client on web server to test
the connection. If the client connects the
server, we can determine that it is not a
network problem.
5. Then check if the connection
between JDBC and the database is
available. Use xbaseimp for the test
(4.09.03, 4.10.02, 4.11.01 contains
xbaseimp). Change the configuration of
xbaseimp to test the web server; check if
JDBC can connect to the database. If the
connection succeeds, Apache and Tomcat
42 Maintenance Experience
need to be installed again. If the connection failed,
database changeover is needed to solve the
problem.
6. Before implementing database changeover,
use platform script to grab SCP information for
subsequent analysis.
Procedure for handling failed or
slow web page display
1. Make sure the connection between the web
and SCP, IMP is available. Socket logs can be
used for the check. Frequent link breaks between
the web and IMP can lead to failed display of web
user interface. Such a failure occurred in Beijing
Unicom: the shutdown of a statistical server led
to repeated restart of IMP and thus affected web
applications (Beijing Unicom).
2. Check config.xml to make sure the
configuration of web connection pool complies with
the specifications. Insufficient web connection may
lead to slow displaying of web pages.
3. Check stdout.log to make sure there is no
obvious error alarm (Beijing Unicom).
Check xbase
1. Check if the process xbase exists. If xbase
does not exist, check if the process webmonitor
exists (Guizhou Mobile).
2. Check if c:\zxin10\was\test.txt has been
deleted (Guizhou Mobile).
3. Check xbasejava.dll (two places, shall be
consistent) and xbaseodbc.dll are consistent with
the version (Guizhou Mobile).
4. Check if wsmap.jar is unique. If it is not,
delete the extra wsmap.jar.
5. Use xsql to connect to the xbase database
manually, and then check if it contains data
(Guizhou Mobile).
6. Check xbase for the data import/export log to
make sure that the import and export are normal.
Disk fragmentation check
Index check
1. Check if sdf.log contains the storage process

execution timeout logs (timeout printed for tasks
executed in the early morning can be ignored). If
the log exists, print the query plan of the storage
process, and then check if the table used the index
(Xinjiang Telecom).
2. Open the page, check the deadlock, and
then focus on the table with the most locks. It
is probably because the table has no index or
the related query did not use the index (Xinjiang
Telecom).
3. If there is no index, create one. After the
index is created, compile all the storage process.
Check if the index has been created successfully.
Error at startup, cannot use web
Symptom
1. Cannot open the home page (java.lang.
NoClassDefFoundError).
2. The administrator cannot log on (error no db
pool name).
3. Under the new architecture, the system
reports that no number segment exists for such a
number.
4. stdout.log reports No scp has service at
startup.
Solution
The following conditions must be satisfied at
smp table:
1. In the zxinsys.zxin_device table of SMP, it
shall be: scf=1 and sdf=1.
2. In the zxinsys.zxin_servicedevice table
of SMP, for the corresponding SCP, it shall be:
servicekey ='pstn51 and sdfstatus =1.
3. In the zxinsys.zxin_cardmap table of SMP, it
shall be servicekey=pstn51 and cardprefix=1112
and devicemodule = xxSCP.
Cannot pre-listen ringtones
1. The page indicates: The system is busy. Try
again later.
Solution Check IMP. If IMP reports an FTP
error, check FTP server logs. Otherwise contact
www.zte.com.cn
IMP personnel for help.
2. The players scroll bar on the page
does not move
Solution
1. Check the source file and find the
files URL.
2. Visit the URL with Flashget or IE. If
the file can be downloaded successfully,
it indicates that no audio driver is installed
on the computer. If the file cannot be
downloaded, do as follows:
1) If no port number is used when
accessing the web, check httpd.conf of
Apache to see whether the configured
destination directory for alias /colorring/
wav is the same as that for wavdir in
db.properties.
2) If port number is used when
accessing the web, wavdir in db.properties
shall be configured as the main directory
of web application: on Tomcat, the main
directory is webapps/colorring; on jbuilder,
the main directory is the directory for the
created web application.
Cannot upload ringtones
(1) The path is not existed
Cause: The directory to which wavdir
is defined does not contain tmp, sys and
other 24 directories (0-23).
Integrated Intelligent Network 43
February 2008 Issue 82
2. FTP operation by SP failed
Causes:
1) .wavdir and ftp server main user
directory must not be the same directory.
2) The user of ftp server must lock user
in home directory
3) Trace FTP server logs
3. For information on other symptoms:
check the IMP logs.
System execution errors,
please contact system
administrator
Cause: An error occurs during
database execution; or an error exists
in the SQL statement or in the storage
process. Check tomcat/logs/zxdb_conn.
log for error information.
Skills and configurations
FTP path issue
For uploading the ringtone, the IP
address, account, password, and FTP path
are all defined in the db.po file, which can
be designated to the directory directly:
/home/zxin10/was/tomcat/webapps/
colorring/wav.
For people who listen to the ringtone,
the IP address, FTP account, and FTP
44 Maintenance Experience
password are all contained in crbtcfg.ini on IMP:
[SP1]
SPCode = 000
Password = abcd
FtpUserid = zxin10
FtpPwd = zxin10
IsAuth =0
As the path is not defined, it will be located in
the main directory /home/zxin10 during the process
of pre-listening. Therefore, /home/zxin10 must
contain directories including 0-23, tmp, and sys.
Otherwise, the ringtone cannot be pre-listened.
For limiting ZXIN10 users to the main directory
during the FTP process, for Linux operating
systems that use vsftp, the configuration file /etc/
vsftpd/vsftpd.conf needs to be modified as follows:
delete # before the two lines, or add the following
two lines separately:
Chroot_list_enable=yes
Chroot_list_file=/etc/vsftpd.chroot_list
Create vsftpd.chroot_list in the /etc directory.
Each account has a line. We just added one line
for zxin10.
The setting becomes effective after you restart
vsftp.
If you want to limit all users to the main
directory during ftp, modify the configuration
file /etc/vsftpd/vsftpd.conf and add one line:
Chroot_local_user=yes
It becomes effective after restart.
Tomcat uses virtual memory configuration
of JAVA
For Windows version, it is the configuration of
memory occupied by Java when configuring tomcat
in the tomcat directory.
For Linux version, it is configured in the line
CATALINA_OPTS="$CATALINA_OPTS -server
-Xms512m -Xmx512m in /home/zxin10/was/tomcat/
bin/catalina.sh. Xms indicates the minimum memory,
and Xmx indicates the maximum memory.
www.zte.com.cn

Integrated Intelligent Network 45

February 2008 Issue 82

46 Maintenance Experience