Troubleshooting Manual M900/M1800 Base Station Subsystem

Chapter 2 Troubleshooting for OMC

Chapter 2

Troubleshooting for OMC

2.1 GSM BSS-OMC Overview

GSM BSS-OMC system can be divided into the following parts:

Browser The browser is used to browse and view OMC network configuration and the information of each node and to monitor the entire OMC network. Its operation environment is Window9x or Windows2000. BAM BAM is the server for the various service consoles to communicate with foreground BSC. Service console Service console is the classification set of some service functions. It includes BSC maintenance system, BSC traffic statistics system, BSC data management system, BSC data auto configuration system, alarm system, traffic statistics report, and (local and remote) BTS maintenance system. Each service console consists of WS (man-machine interface) and its corresponding BAM module. WS provides the interface for input and operation. BAM module applies operations to host in accordance with WS commands, and sends operation results to WS. OMC Server

OMC Server is used to

1) Store OMC configuration information and provide the necessary configuration data for the browser. 2) Store HLR subscriber data. The database platform is Sybase. 3) Store traffic statistics data. 4) Store alarm data.
The operation system of OMC Server is Solaris2.6. BSS-OMC structure is as shown in Figure 1.1 .

Troubleshooting Manual M900/M1800 Base Station Subsystem

Chapter 2 Troubleshooting for OMC

Figure 1.1

OMC structure

The mode of connecting through OMC Server is remote maintenance and the mode of connecting through OMC Local WS is local maintenance. App 1 ~ App n refer to service consoles, including BSC maintenance system, BSC traffic statistics system, BSC data management system, data auto configuration system, alarm system, traffic statistics report, and (local and remote) BTS maintenance system.

2.2 Examples
2.2.1 Communication was Interrupted between BAM and Host
I. Description
After the BAM program is started, the indicator for the communication between BAM and the host is red.

II.

Analysis 1) Check whether the host program runs normally. You can exam the indicators on GMPU (for single-module BSC) or GSNT, and GMCCM (for multi-module BSC). 2) Check whether the cable between MCP card and the host is correctly connected. 3) Check whether the field INSTALLED of [MAILBOX] in bam.ini is set to 1.

Troubleshooting Manual M900/M1800 Base Station Subsystem

Chapter 2 Troubleshooting for OMC

III. Handling process 1) Configure the data and load the data to make the host operate normally. 2) Replace MCP card cable or change the connection mode of MCP card. 3) Set the field INSTALLED of [MAILBOX] in bam.ini to 1 and restart the BAM.

2.2.2

Communication was Interrupted between BAM and Server

I. Description
After the BAM program starts, Connecting to Switch is displayed periodically or it is not displayed. But the corresponding icon in OMC Shell is marked by a cross.

II.

Analysis 1) You may use command ping to check whether TCP/IP is installed correctly. . 2) Check whether the ServerAddress in [Network] in bam.ini is set to the expected server IP address. 3) Check whether Server processes operate normally. For this purpose, you may directly login to the Server to check it. 4) Check whether the installed in [Network] in bam.ini is set to 0 and clinetinstalled to 1.

III. Handling process 1) Ensure the TCP/IP of the BAM is normal. 2) Ensure both OMC Shell and BAM are connected to the same Server. 3) Ensure OMC Server processes operate normally. 4) Ensure the installed in [Network] in bam.ini is set to 0 and clinetinstalled to 1. After the setting, restart the BAM.

Troubleshooting Manual M900/M1800 Base Station Subsystem

Chapter 2 Troubleshooting for OMC

2.2.3

Data Table Error is Prompted during BAM Startup

I. Description
After BAM program is started, the system pops up a dialog box showing data table error or database engine error.

II.

Analysis 1) Restart the computer and the BAM program to see whether the problem disappears. 2) Check the data table indicated in the prompted dialog box to see whether the version is correct ( mis-upgrading can cause version error ). 3) Check whether the BAM installation directory is damaged. For example, check whether the directory IDAPI and the directory IDAPI32 exist and whether the files in the directories are complete.

III. Handling process 1) Restart the computer and the BAM program. 2) Delete the data tables prompted in the dialog box (or rename the tables). Then restart the BAM computer, the deleted tables will be created automatically. Configure them again. 3) Reinstall the same OMC version.

2.2.4

Loading Host Programs from BAM Failed

I. Description
Loading host programs from BAM fails and BSC cannot run.

II.

Analysis 1) Check whether any error is prompted in the main window of the BAM program. 2) Ensure the field address related to the loading in the bam.ini is correctly set. 3)

Troubleshooting Manual M900/M1800 Base Station Subsystem

Chapter 2 Troubleshooting for OMC

Ensure the host software and the physical board are matched.

III. Handling process 1) Ensure that the files to be loaded exist in ...\bam\dload directory. If not, copy necessary files to this directory. 2) Correctly set the field address and restart the BAM program. 3) Use the correct version (matched with the board) host software and load it.

2.2.5

Data cannot be Modified/Deleted

I. Description
During data configuration, the data of some modules cannot be modified/deleted.

II.

Analysis 1) The data operation of non-common tables is designed to be related to the module. So first check AM description table to find out the module IDs that have not corresponding module. 2) As there is no corresponding module ID in AM module description table, the data are regarded as being illegal when the service console performs the data check. So the related operation is not accepted.

III. Handling process 1) Add the modules whose data cannot be modified/deleted into AM module description table and re-convert all data. 2) Restart the BAM program. 3) Restart BSC data management system.

2.2.6 Error

At Least One Table in BSC Data Management System Report Has

I. Description
At least one table in BSC data management system has error after the data of all

Troubleshooting Manual M900/M1800 Base Station Subsystem

Chapter 2 Troubleshooting for OMC

tables are converted.

II.

Analysis
The tables with error and the corresponding cause are listed in BAM main window.

III. Handling process

Modify the data of the corresponding table according to the information provided in BAM main window.

2.2.7

Communication Timeout of Interface Tracing

I. Description
Communication timeout dialog box is prompted after the interface to be traced is selected.

II.

Analysis
The module to be traced is not configured or it is in inactive state; the communication between the foreground and background parts of the node that the module belongs to is interrupted.

III. Handling process 1) Check the module state: click Maintenance to pop up a menu and then select the Module State. 2) Check the working state of the node in OMC Shell; if the icon of this node is marked by a red slash, this indicates that the communication between the BAM and host is interrupted. If the icon of this node is marked by a red cross, this indicates the communication between the BAM and OMC Server is interrupted or the BAM program is not running.

2.2.8

Alarm System Cannot Receive Alarms

I. Description
Alarm system cannot receive any alarm that has been sent to the BAM from foreground. And the history alarms cannot be viewed by the browser.

Troubleshooting Manual M900/M1800 Base Station Subsystem

Chapter 2 Troubleshooting for OMC

II.

Analysis 1) Use the following command to check whether the alarm server process is normal:
ps-ef|grep alarmbam There are should be two alarmbam processes.

2) Database error, including:

Alarm data space is full and master or alarm log space is full.

III. Handling process 1) If the alarm process is abnormal, please close alarm process, then use kill XXX (process number) to kill newfhlrsvr, newcommdriver and alarmbam in order. Then restart these processes in reverse order.
End the process (newfhlrsvr): ps -ef|grep newfhlrsvr The screen displays: newomc 345 newomc 346 1 0 12-08 0:0 12-08 10:35 newfhlrsvr newfhlrsvr

345 0

newomc in the first column is the user name, 345 and 346 in the second column are the process numbers, and the 345 in third column is the parent process number. Then use kill command to end the process, as shown in the following: kill 345 346 Restart the process: $ alarmbam $newcommdriver $ newfhlrsvr

2) Check whether the SYBASE in OMC Server has been started. 3) If the alarm data space is full, back up the history data and clean up the database.
Back up the history database:

Troubleshooting Manual M900/M1800 Base Station Subsystem

Chapter 2 Troubleshooting for OMC

$ bcp warn..history out history.dat -Usa P password -c Clean up the history database: $ isql -Usa 1> use warn 2> go 1> truncate table history 2> go

4) If master or alarm warn log space is full, use dump tran + database name + with no_log to clean up the space. If the space is still not available, check whether there are any tables or storage processes that should be established in other database have been wrongly created in the master database. If so, delete them. 5) Restart the process. If the problem remains, handle the problem according to the printed Fail information.

2.2.9

BAM Prints Fail to shake hands with alarm server

I. Description
In BAM message tracing, BAM prints Fail to shake hands with alarm server.

II.

Analysis
Sending the handshaking message frame to OMC Server fails. Usually the cause is the connection between the BAM and OMC Server is interrupted or the alarm server process is abnormally started.

III. Handling process 1) Check the network communication

Use the command ping to check the state of the communication between the faulty computer and OMC Server.

2) Check the number of processes

Check whether there are two alarmserver processes and two newcommdriver processes. If not,

Troubleshooting Manual M900/M1800 Base Station Subsystem

Chapter 2 Troubleshooting for OMC

(a). Use isql -Usa -Pserver1234 to login to the sybase system, (b). Check whether the alarm log and data space is full. sp_helpdb warn device_fragments size usage free bytes

------------------------------ ------------- -------------------- ----------data_dev1 data_dev1 data_dev1 log_dev1 20.0 MB 50.0 MB 30.0 MB 100.0 MB data only data only log only log only 20464 46944 30192 102400

If the sum of the size of data only is 0 or its free bytes is less than 1000, or the sum of the size of log only is 0 or its free bytes is less than 1000, this indicates that the data or log space is not enough. If Warn database is normal, check whether the master is normal. The method is the same as above one. (c). Firstly, If warn database and master database are normal, enter the log directory of the OMC user and use the command vi to view the Fail information in alarm.log, or use the following command to measure the error information: grep Fail switch.log Then solve the problem according to the given error information. Secondly, check whether there are two newcommdriver processes. If not, enter the log directory of the OMC user and use the command vi to view the Fail information in commdrv.log, or use the following command to measure the error information: grep Fail commdrv.log

3) Check whether the hard disk is full. Use the command df-k to check whether the related file systems in the hard disk is full.

2.2.10

Records in Alarm Box and Those in Fault Alarm table Inconsistent

I. Description
The number of alarms in alarm box is different from that queried from alarm system.

Troubleshooting Manual M900/M1800 Base Station Subsystem

Chapter 2 Troubleshooting for OMC

II.

Analysis
Generally this is because the manual operation has been made to the database and some alarms in the alarm fault table are deleted, or the alarms are cleaned up when the BAM restarts but the alarms in alarm box still exist.

III. Handling process

Only after the host restarting or the host faults disappearing, and BAM is restarted, can the records in the alarm box and those in alarm table be the same.

2.2.11

Shaking Hand with BAM Fails When the Alarms are Deleted
I. Description
If over 100,000 records in history table are to be delelted in one time, select Maintain->Delete history alarm->OK to delete all alarm history tables. After 3~4 minutes, then the BAM prints Fail to shake hands with alarm server.

II.

Analysis
Server program uses the single-process dbproc to access the database, if 100,000 records or a large number of data are deleted at one time, it will take a long time to process the operation and all CPUs will be occupied till the operation completes. Thus the handshaking messages are ignored.

III. Handling process

It is recommended that the data should not be deleted in large batch in one time and they should be deleted in small batches. The new version now is available to solve this problem. In the new version, the deletion can be completed through a sub-process and this will not have any impact on the processing of handshaking and query messages.

2.2.12

Failed to Register due to Server Failure

I. Description
Start OMC Shell, after the main window appears, Failed to register due to server failure is prompted.

10

Troubleshooting Manual M900/M1800 Base Station Subsystem

Chapter 2 Troubleshooting for OMC

II.

Analysis
When OMC Shell is connected to the server, it reports the serial number input during the installation. So the server checks the License.dat in the data directory to verify the serial number. When this problem occurs, the cause might be there is no License.dat in the server or this file has been damaged. Being unable to verify the serial number, then the server returns the failure information.

III. Handling process

Login to the server to check whether License.dat exists or it has been damaged. If necessary, copy this file again from installation disk.

2.2.13

Service Console Running Failed

I. Description
When open the service console, Operation failure: Create process failed, error code:***** is prompted.

II.

Analysis
If the problem occurs repeatedly, generally this is because the service console program file is faulty or it has been damaged.

III. Handling process 1) Double click the node icon of the service console to check the version number of the service console program. 2) Reinstall the same version service console.

2.2.14

Loading Shell Map Failed

I. Description
When OMC Shell is opened, the system prompts Loading map failed and OMC Shell program is terminated.

II.

Analysis
OMC Shell cannot load the map file. The cause might be that the file does not exist, the format is incorrect, or the path is incorrect.

11

Troubleshooting Manual M900/M1800 Base Station Subsystem

Chapter 2 Troubleshooting for OMC

III. Handling process 1) Open the omc.ini in C:\WINDOWS. The map file path and filename are listed behind MAP= in [OPTION] field. 2) If the map file name is not there, please add it. 3) If the path or the filename is incorrect, modify omc.ini. 4) The map file extension must be .BMP. If not, convert the file into BMP format.

2.2.15

Cant Refresh Templates in BSC Traffic Statistics System

I. Description
When the template refresh is performed, two of four client computers that connect with the same Server cannot complete the operation.

II.

Analysis
When these two computers are used to perform only FTP operation, it is found that it takes one hour to send a file of 20k. So it is certain that the network fault occurs.

III. Handling process

Check the network cable to ensure the communication is clear.

12