Maintenance Manual

Maintenance Manual

iManager M2000 Mobile Element Management SystemTable of Contents

Table of Contents1-1Chapter 1 Requirements on Maintenance Personnel

Chapter 2 System Knowledge2-12.1 Overview of System Knowledge2-12.2 Support Software2-12.3 Databases2-12.4 Related Users2-22.4.1 Overview of Related Users2-22.4.2 Operating System Users2-22.4.3 Database Users2-32.4.4 M2000 Software Users2-42.5 System Logs2-42.5.1 Overview of System Logs2-42.5.2 Operation Log2-42.5.3 System Log2-42.5.4 Debugging Log2-52.6 M2000 Processes and Services2-52.6.1 Overview of M2000 Processes and Services2-52.6.2 SystemConfigurator2-52.6.3 sac_agent2-52.6.4 em_agent2-62.6.5 monitor_agent2-62.6.6 partition_agent2-62.6.7 audit_agent2-62.6.8 mo_agent2-62.6.9 sm_agent2-72.6.10 med_agent2-72.6.11 ts_agent2-72.6.12 ifms_agent2-72.6.13 manager_agent2-72.6.14 pm_agent2-72.6.15 cmserver_agent2-82.6.16 swm_agent2-82.6.17 proxy_agent2-82.6.18 notify_agent2-82.7 Directory Structure2-82.8 Server Maintenance Commands and Scripts2-92.8.1 Environment Setting Script2-92.8.2 Maintenance Commands2-10Chapter 3 Routine Maintenance3-13.1 Overview of Routine Maintenance3-13.2 Routine Maintenance Items3-13.2.1 Daily Maintenance3-13.2.2 Weekly Maintenance3-23.2.3 Monthly Maintenance3-23.3 Maintenance Procedures3-23.3.1 Checking CPU Utilization3-23.3.2 Checking Process Status3-33.3.3 Checking Database Status3-53.3.4 Querying Alarm Information3-53.3.5 Querying Log Information3-63.3.6 Backing up System3-63.3.7 Checking Hard Disk Space3-73.3.8 Operating Magnetic Tape Drive3-73.3.9 Logging in as root Through Telnet or ftp3-83.4 Items for Attention3-93.4.1 Not Modifying Server Time3-93.4.2 Not Modifying Server Host Name3-103.4.3 Not Modifying Server IP Address3-11Chapter 4 Alarm Handling4-14.1 Overview of Alarm Handling4-14.2 System Performance Alarm4-14.2.1 Alarm Meaning4-14.2.2 Possible Causes4-14.2.3 Handling Suggestions4-14.3 Disk Status Alarm4-24.3.1 Alarm Meaning4-24.3.2 Possible Causes4-24.3.3 Handling Suggestions4-24.4 Database Threshold Alarm4-34.4.1 Alarm Meaning4-34.4.2 Possible Causes4-44.4.3 Handling Suggestions4-44.5 Service Status Alarm4-54.5.1 Alarm Meaning4-54.5.2 Possible Causes4-54.5.3 Handling Suggestions4-64.6 System Log Status Alarm4-64.6.1 Alarm Meaning4-64.6.2 Possible Causes4-64.6.3 Handling Suggestions4-64.7 OMC Connection Fault Alarm4-74.7.1 Alarm Meaning4-74.7.2 Possible Causes4-74.7.3 Handling Suggestions4-7Chapter 5 Troubleshooting5-15.1 Overview of Troubleshooting5-15.2 Troubleshooting Procedure5-15.2.1 Information Collection5-15.2.2 Fault Location5-15.2.3 Fault Removal5-25.3 Faults During M2000 Installation5-25.3.1 Failure in Installing Disk Mirror5-25.3.2 Failure in Building Sybase5-45.3.3 Failure in Reinstalling Sybase5-45.3.4 Failure in Installing M2000 Server Application Software5-55.3.5 Failure in Reinstalling M2000 Server Application Software5-55.3.6 Failure in Installing M2000 Client Application Software5-65.3.7 Failure in Reinstalling M2000 Client Software5-65.4 Faults During M2000 Running5-75.4.1 Abnormal Service Restart5-75.4.2 Failure in Starting or Stopping Services5-85.4.3 Failure in Logging in from M2000 Client5-85.4.4 Failure in Starting NE LMT at Client5-105.4.5 Abnormal Termination of Client Program5-105.4.6 Failure in Running Client Program5-115.4.7 Failure in Printing Alarm Information in Real Time5-115.4.8 Failure in Receiving Alarm Short Messages5-125.4.9 Failure in Receiving Alarm Short Messages in Real Time5-125.4.10 Abnormal Display of Characters on the Window of Client5-13

Chapter 1 Requirements on Maintenance Personnel iManager M2000 Mobile Element Management System (M2000 for short) maintenance personnel must be familiar with the following items: Operating systems Solaris and Windows Database Sybase Knowledge of computer networks such as Ethernet, TCP/IP, and Client/Server M2000 system and its functionsRefer to iManager M2000 Mobile Element Management System System Description and Chapter 2 System Knowledge in this manual. Installation of M2000 Server and Client application softwareRefer to iManager M2000 Mobile Element Management System Installation Manual Routine operation on M2000Refer to iManager M2000 Mobile Element Management System Online Help

Routine maintenance, alarm handling and troubleshooting on M2000Refer to this manual.Chapter 2 System Knowledge2.1 Overview of System KnowledgeTo maintain M2000 system, you need to know the following aspects:

Support software

Databases Related users

System logs

Processes and services Directory structure

Server Maintenance Commands and Scripts

2.2 Support Software

The M2000 system works in Server/Client mode. M2000 Server communicates with NEs, stores O&M data of these NEs and provides interfaces for NMS. The M2000 Server software is based on the UNIX operating system and some basic software. The basic software provides the database, ftp, NTP and CORBA functions. For example, Sybase is responsible for providing the database function. The CORBA communication function provided by TAO implements the communications between the Server software, Client software and NMS through a CORBA bus. The installation software packet of the M2000 Server contains the software providing the functions such as ftp, NTP and CORBA communication. The M2000 Client software provides users with a window for operating and maintaining NEs. It runs on a JAVA virtual machine. The installation software packet of the M2000 Client contains the JAVA virtual machine that can run in Windows operating systems. 2.3 DatabasesM2000 contains four databases built based on the Sybase database. They are omcdb, fmdb, pmdb and sysmdb. The spaces of these databases are set automatically during the installation of the M2000 Server application software. It is unnecessary to modify them manually. The database omcdb stores configuration data and security data of the M2000 system. The database fmdb stores alarm data of NEs and the M2000 system. The database pmdb stores the performance statistic data of NEs. The database sysmdb stores the software version information and configuration data of NEs. 2.4 Related Users2.4.1 Overview of Related Users

The following three kinds of users are involved with M2000 system running. Operating system users Database users M2000 software usersThe parts below respectively define the level and authorities for each kind of users.2.4.2 Operating System UsersI. Overview of Operating System Users

To ensure the security of the operating system of M2000 Server, you should create three users, dbuser, omcuser, and ftpuser, except the default user root. You should also create a user group omcsysm.If you install Intelligent Report System, the installer will create the user inrpt and the user group inrpt automatically. II. root

The user root is the system administrator, with the highest authority to the system. The user can control all the resources, create other users, grant authorities to other users, and perform all the operation functions provided by the operating system. Only the user root can install and uninstall the M2000 server application software, and start and stop M2000 services. III. dbuser

The user dbuser is in charge of routine operation and maintenance of Sybase database. The user can perform any operation such as interaction with the database through isql on the database. You should create dbuser before installing Sybase. The related attributes are as follows: Home directory: /opt/sybase The group that it belongs to: staff

Login shell: /bin/bashIV. omcuser

The user omcuser has the authority to perform routine O&M on the M2000 system, including querying system status, backing up and restoring system data, and the authority to access to databases. The user can neither install/uninstall M2000 Server application software, nor start/stop M2000 services. You should create omcuser before installing the M2000 software. The attributes of the user are as follows: Home directory: /export/home/omc

The primary group that it belongs to: staff. The secondary group that it belongs to: sys, root, omcsysm. Login shell: /bin/bashV. ftpuser

The user ftpuser manages software of NEs and transfers software information to NEs. You should create ftpuser before installing M2000 software. The attributes of the user are as follows: Home directory: /export/home/sysm

The group that it belongs to: omcsysm

Login shell: /bin/bashVI. inrpt

The user inrpt manages the Intelligent Report System. You need not to create inrpt. The attributes of the user are as follows:

Home directory: /opt/inrpt The group that it belongs to: inrpt Login shell: /usr/bin/csh2.4.3 Database UsersThere is a default database user sa after the Sybase database installation. The database user sa empowers the highest administrative authority to the database. 2.4.4 M2000 Software UsersThere is a default user admin after the M2000 software is installed successfully. The M2000 software user admin is a super user with all the operation authorities to the M2000 system. The authorities include M2000 user administration, NE configuration, NE operation, NE management, and NE status query. 2.5 System Logs2.5.1 Overview of System Logs

The M2000 system provides three kinds of logs:

Operation log System log

Debugging log

Different logs keep different kinds of information for different users. 2.5.2 Operation LogThe operation log records operations of M2000 users. You can query or displace the user operation log through graphic user interface (GUI) on the Client. The operation log is stored in the path /export/home/omc/var/audits/.2.5.3 System LogThe system log records the system running process for the M2000 system administrator to query.The system log is stored in the path /export/home/omc/var/logs/. Table 2-1 shows the meaning of each field in the system running log. Table 2-1 Meaning of each field in the system running logField Description

Level identification Indicates the level of the recorded information. There are four levels of information in the log, namely LOG-NORM, LOG-WARN, LOG-ERR and LOG-CRIT.

Service identificationIndicates the service module of the recorded information. It can be MOMGR, COMMON, SM, EM, FM or SAC.

Date and timeRecords the date and time of the Log, for example, Mon Sep 17 14:30:36 2003.

ContentSaves the content of the information recorded in this Log, for example, getServiceAgent: Can not connect to ServiceAgent.

2.5.4 Debugging LogIt helps locate system problems. The debugging log is saved in the path /export/home/omc/var/logs/. 2.6 M2000 Processes and Services2.6.1 Overview of M2000 Processes and Services

During normal operation of the M2000 system, the Server starts 19 processes: SystemConfigurator, sac_agent, em_agent, monitor_agent, partition_agent, audit_agent, mo_agent, sm_agent, med_agent, ts_agent, ifms_agent, manager_agent, pm_agent, cmserver_agent, swm_agent, proxy_agent and notify_agent. Each of them includes different services, which provide different functions. 2.6.2 SystemConfigurator

SystemConfigurator manages all other local processes. In a distributed environment, it communicates and interacts with imapsysd processes on other machines, avoiding the impact on application processes caused by the distributed system.2.6.3 sac_agent

The process sac_agent provides the following services: ScheduleManagerScheduleManager provides a frame construction, which enables the scheduling and control of user tasks. SysBackupMgrSysBackupMgr backs up important configuration files, database data and managed object (MO) instance data of the system periodically. LicenseMgr

LicenseMgr provides a service interface for checking the validity of License file of the current version. LogServer

LogServer records system log. It receives, manages and stores the system logs from other processes through a socket.2.6.4 em_agent

The process em_agent provides the service EventManager. EventManager controls the transmission and reception of system events to ensure that system events can be sent to the correct destinations.2.6.5 monitor_agent

The process monitor _agent provides the service SystemMonitor. SystemMonitor monitors the system status and utilization of system resources, such as database status, CPU utilization and memory and free disk space. It periodically checks the status of various configurations and takes measures accordingly. 2.6.6 partition_agent

The process partition_agent provides the service PartitionManager. PartitionManager manages the distributed information of MIT and Mediation, and provides interfaces for querying information and registering entities in it.2.6.7 audit_agent

The process audit-agent provides the service AuditServer. AuditServer records operation logs. The Client collects operation logs and sends them to the Server. The Server localizes the operation logs, writes them into the database, and sends event notifications.2.6.8 mo_agent

The process mo_agent provides the following services: LockManagerLockManager manages MO locks. RelationManagerRelationManager manages the relations between MOs. MOManagerMOManager adds, deletes, modifies and queries MO.2.6.9 sm_agent

The process sm_agent provides the service SecurityController. SecurityController controls the access to the sensitive resources in the EMS, so that only those authorized users can access to these resources. It realizes the access control by restricting the users' rights to use various interfaces.2.6.10 med_agent

The process med_agent provides the service MediationController. MediationController manages the adaptation module of interaction between EMS and physical NEs and provides protocol independent NE functional interfaces for other services.2.6.11 ts_agent

The process ts_agent provides the service TSService. TSService maintains the common topology architecture, provides common topology data, and refreshes the alarm and status information of NEs in the topology interface.2.6.12 ifms_agent

The process ifms_agent provides the service FaultManager. FaultManager collects, analyzes, handles, stores and displays the faults reported by equipment.

2.6.13 manager_agentThe process manager_agent provides the service SystemManagerServer. SystemManagerServer provides self-management function, which includes querying the Client OS information and checking if the Client software version is matching with the Server software version.2.6.14 pm_agent

The process pm_agent provides the service PMService. PMService realizes the performance service procedure of all NEs, and is entirely independent of individual NE, MO and the interaction with Hosts.2.6.15 cmserver_agent

The process cmserver_agent provides the service CMServer. CMServer realizes the configuration service procedure of all NEs, and is entirely independent of individual NE, MO and the interaction with Hosts.2.6.16 swm_agent

The process swm_agent provides the service SWMService. SWMService manages the versions, configuration data and other files of all NEs. It provides download, upload, active and rollback functions, and is entirely dependent on CMServer, MO and ftp services.2.6.17 proxy_agentThe process proxy_agent provides the service ProxyServer. ProxyServer enables M2000 Client to access NEs through a proxy server to run the LMT programs of these NEs.2.6.18 notify_agentThe process notify_agent provides the service NotifyManager.NotifyManager realizes the remote notification of alarms.2.7 Directory StructureTable 2-2 shows the directory structure of the M2000 Server software.Table 2-2 M2000 Server software directories Directory UserDescription

/rootRoot directory of M2000

//binrootExecutable files

//etcrootSystem configuration file and SQL scripts

//idl_northboundrootNorthbound IDL interface file provided

//librootLibrary files concerning system running

//lbinrootSystem management command

//modelrootModel file

//3rdToolsrootThird party software used

/export/home/omc/var/cmrootData and files of CM module

/export/home/omc/var/pmrootData and files of PM module

/export/home/omc/var/fmrootData and files of FM module include FM dumping files

/export/home/omc/var/logsrootSystem running logs and debugging logs

/export/home/omc/var/auditsrootUser operation log

/export/home/omc/var/sysmrootData and files of SM module

/export/home/omc/var/itf_nrootData and files of Northbound module

2.8 Server Maintenance Commands and Scripts 2.8.1 Environment Setting ScriptBefore carrying out a M2000 command, execute the environment setting script svc_profile.sh. Use this script to set the user environment such as command searching path and dynamic data library (DDL) searching path. This script is in the root directory of M2000 installation. Execute the script as follows: bash-2.03$ . //svc_profile.sh

Caution:There is a "." at the start of the command and a space between the "." and the subsequent "/". The script should be in the .profile of omcuser after M2000 installation according to iManager M2000 Mobile Element Management System Installation Manual. When logging in to the system as omcuser, you need not execute the script. ( Note: The iManager M2000 Mobile Element Management System Installation Manual describes the method of setting the user environment of omcuser. 2.8.2 Maintenance CommandsThe M2000 maintenance commands are in the directory //bin. I. Common commandsTable 2-3 lists some common maintenance commands. Table 2-3 Common maintenance commands of M2000CommandDescription

start_tao_servicesUsed to start the TAO naming service and notification serviceIt is necessary to start this service before starting other M2000 services.

stop_tao_servicesUsed to stop the TAO naming service and notification service

start_svcUsed to start all the M2000 services

stop_svcUsed to stop all the M2000 services

kill_svcUsed to stop all the M2000 services forcibly

svc_adm cmd statusUsed to query service status

svc_psUsed to query M2000 process status

topUsed to check the CPU utilization of each process in the system

II. Advanced commands Table 2-4 lists some advanced maintenance commands. You can use them only when you are very familiar with the M2000 system. It is recommended not executing them in general situations to avoid system accidents.You can obtain some parameters involved in these commands from the configuration file imap.xml. The file is in the directory //etc/conf. Avoid modifying the file content because any modification to it will affect the M2000 services. Table 2-4 Advanced maintenance commandsCommandDescription

svc_adm cmd startsvcUsed to start a definite service

svc_adm cmd stopsvcUsed to stop a definite service

svc_backuprestore cmd backupUsed to back up the M2000 system

svc_backuprestore cmd restoreUsed to restore the M2000 system

svc_adm cmd reloadUsed to reload imap.xml

svc_bulkprov -exportUsed to export the information of management objects in batches, such as the configuration data of NEs

svc_bulkprov -importUsed to import the information of management objects in batches

svc_adm cmd log type log mode [enable, disable]Used to enable or disable the system running log of a service

svc_adm cmd log type log mode isenableUsed to query the system running log status of a service

svc_adm cmd audit mode [enable, disable]Used to enable or disable a type of operation log of a service agent

svc_adm cmd audit mode [enableall, disableall]Used to enable or disable all types of the user operation log of a service agent

svc_adm cmd audit mode [enableaudit, disableaudit]Used to enable or disable the user operation log under a service agent

svc_audb -exportUsed to export the user operation log

svc_audb -purgeUsed to purge the user operation log

Chapter 3 Routine Maintenance 3.1 Overview of Routine Maintenance

This chapter lists the routine maintenance items and describes the maintenance operation procedure. It also lists the items requiring attention during M2000 maintenance. You can: Log in to the Client as admin to observe the system operation status. Log in to the Server as omcuser to do routine operation and maintenance. Log in as root to perform some system commands.3.2 Routine Maintenance ItemsThis section lists daily, weekly, and monthly maintenance items. For the detailed information or commands of each item, see 3.3 Maintenance in this manual. 3.2.1 Daily Maintenance Table 3-1 lists the daily maintenance items of the M2000 system. Table 3-1 Daily maintenance checklistSNItemReference

1Check CPU utilizationCPU utilization is lower than 80%.

2Check process statusAll the services are running normally.

3Check database statusDatabase system operates normally.

4Check alarm informationThere is no alarm information.

5Check log informationThere is no abnormal and malicious operations implemented.

3.2.2 Weekly Maintenance Table 3-2 lists the weekly maintenance items of the M2000 system.Table 3-2 Weekly maintenance checklistSNItemReference

1System backupOpen the [Periodic Backup] dialog box on M2000 Client, and select all the data to be backed up.

3Check hard disk spaceThe used space of each partition is lower than 80%

3.2.3 Monthly MaintenanceTable 3-3 lists the monthly maintenance items of the M2000 system.Table 3-3 Monthly maintenance checklistSNItemReference

1Check power supply The power supply of the Server is normal.

2Check Server hardware The Server is not damaged physically.

3Check the auxiliary devices of the Server The devices such as the magnetic tape drive and CD-ROM drive are working normally.

3.3 Maintenance Procedures 3.3.1 Checking CPU UtilizationI. MethodThe M2000 system supports the monitoring of CPU utilization of the Server at the Client. You can also log in to the Server directly and execute the CPU monitoring command. At the Client Select [Tools/System Monitor/Monitor Browser] in the main window to display the [System Monitor Browser] dialog box, and then click the [Performance Monitor] tab. At the Server Log in as omcuser and execute the command below:bash-2.03$ /usr/openwin/bin/perfmeter.II. Exception Handling In normal situations, the CPU utilization should be lower than 80%. In case of exceptions, see 4.2 System Performance Alarm in this manual.3.3.2 Checking Process Status

I. MethodThe M2000 system supports the monitoring of the processes of the Server at the Client. You can also log in to the Server directly and execute the process monitoring command. At the ClientSelect [Tools/System Monitor/Monitor Browser] in the main window to display the [System Monitor Browser] dialog box, and then click the [Service Monitor] tab. At the ServerLog in as omcuser and execute the command below: bash-2.03$ svc_adm cmd status

Number of hosts: 1

Host: DEFAULTSYSAGENT

SystemConfigurator: running

Service Agent: sac_agent [4 service(s)] pid: 8625

ScheduleManager [running ]

SysBackupMgr [running ]

LicenseMgr [running ]

LogServer [running ]

Service Agent: em_agent [1 service(s)] pid: 8627

EventManager [running ]

Service Agent: monitor_agent [1 service(s)] pid: 8629

SystemMonitor [running ]

Service Agent: partition_agent [1 service(s)] pid: 8637

PartitionManager [running ]

Service Agent: audit_agent [1 service(s)] pid: 8643

AuditServer [running ]

Service Agent: mo_agent [3 service(s)] pid: 8649

LockManager [running ]

RelationManager [running ]

MOManager [running ]

Service Agent: sm_agent [1 service(s)] pid: 8831

SecurityController [running ]

Service Agent: med_agent [1 service(s)] pid: 19134

MediationController [running ]

Service Agent: ts_agent [1 service(s)] pid: 8845

TSService [running ]

Service Agent: ifms_agent [1 service(s)] pid: 8861

FaultManager [running ]

Service Agent: manager_agent [1 service(s)] pid: 8633

SystemManager [running ]

Service Agent: pm_agent [1 service(s)] pid: 19840

PMService [running ]

Service Agent: cmserver_agent [1 service(s)] pid: 8891

CMServer [running ]Service Agent: swm_agent [1 service(s)] pid: 15852

SWMService [running ]Service Agent: proxy_agent [1 service(s)] pid: 8953

ProxyServer [running ]

Service Agent: notify_agent [1 service(s)] pid: 8873

NotifyManager [running ]( Note: To highlight the information in the left half part of the output window, the information on the right half part is omitted here. II. Exception HandlingIn case of abnormal disappearance of a process, see 4.5 Service Status Alarm in this manual. 3.3.3 Checking Database StatusI. MethodThe M2000 system supports the monitoring of the database status at the Client. You can also log in to the Server directly and execute the database status monitoring command. At the Client Select [Tools/System Monitor/Monitor Browser] in the main window to display the [System Monitor Browser] dialog box, and then click the [Database Monitor] tab. At the ServerLog in as omcuser and execute the command below: bash-2.03$ isql SSYB -Usa -P 1> sp_helpdb2> goII. Exception HandlingSee 4.4 Database Threshold Alarm in this manual if the database is full. In case of other problems with the database, contact Huawei technical support personnel for troubleshooting. 3.3.4 Querying Alarm InformationI. MethodTo query alarm information, proceed as follows: Log in to the M2000 ClientSelect [Fault/Query/Current Alarm] in the main window to display the [Alarm Query and Statistic] dialog box, and then click . Check whether there is any alarm information.

II. Exception HandlingHandle the alarm according to the suggested alarm handling method. For alarm handling of M2000 system, refer to Chapter 4 Alarm Handling. For alarm handling of NEs, refer to the online help at the M2000 client.3.3.5 Querying Log InformationI. MethodTo query log information, proceed as follows: Log in to the M2000 ClientSelect [System/Log/Query] in the main window to display the [User Monitor] dialog box, and then click .Check whether there are abnormal and malicious operations, such as a user fail to log in to the system in succession.II. Exception HandlingCheck the validity of the user who has performed the abnormal and malicious operations. Restore the original settings.3.3.6 Backing up System

I. MethodThe M2000 system supports the backup of the files on the Server at the Client. You can also log in to the Server directly and execute the system backup command. At the ClientSelect [Tools/System Backup/Periodic Backup] in the main window to display the [Periodic Backup] dialog, and then select all the data to be backed up. At the serverLog in as omcuser and execute the command below: bash-2.03$ svc_backuprestore cmd backup -module The module name can be one of the following:

SecurityController

pm

alarm

II. Exception HandlingIf a system fault occurs, execute the command below to restore the system. bash-2.03$ svc_backuprestore cmd restore -module [-file] < restorefile > The module name can be one of the following:

SecurityController

pm

alarm

3.3.7 Checking Hard Disk SpaceI. MethodThe M2000 system supports the monitoring of the hard disk space at the Client. You can also log in to the Server directly and execute the hard disk space monitoring command. At the ClientSelect [Tools/System Monitor/Monitor Browser] in the main window to display the [System Monitor Browser] dialog box, and then click the [Hard Disk Monitor] tab. At the ServerLog in as omcuser and execute the command below:

bash-2.03$ df k II. Exception handlingIn normal, the used space of each partition should be lower than 80%.

See 4.3 Disk Status Alarm in this manual if there is no space in the hard disk. 3.3.8 Operating Magnetic Tape DriveYou can operate the magnetic tape drive using M2000 Tape Management Tool. Tool name and path to save the tool : Server//tapemanager/tapemanager.sh

Run tapemanager.sh and a window as shown in Figure 3-1 is displayed.The window provides operations as those in the file manager. You can copy or delete files, load tapes, format tapes, and retrieve files in the window.

Figure 3-2 Tape controller 3.3.9 Logging in as root Through Telnet or ftp For the sake of security, the user root can log in to the system only through the console after Solaris8 is installed. I. Through Telnet

If it is necessary to log in to the system through telnet as root, follow the procedure below. It is recommended restoring the original setting after that. Log in as rootOpen the file /etc/default/login. Find the line of CONSOLE=/dev/console. Add "#" in the front of the line to turn it to a comment line. Save the settings and exit. After that, you can log in to the system as root through telnet. II. Through ftp

If it is necessary to log in to the system as root through ftp, follow the procedure below. It is recommended restoring the original setting after that.Log in as rootOpen the file /etc/ftpusersFind the line of root user, and delete the line. Save the settings and exit. After that, you can log in to the system as root through ftp. 3.4 Items for AttentionThe user cannot modify the system settings at will, especially during M2000 running. Otherwise, M2000 will be running abnormally or even the database and the operating system will be abnormal. 3.4.1 Not Modifying Server Time System time modification during M2000 running will affect the system timer, thus disabling the timed cleaning of the database tempdb. When tempdb is full, Sybase cannot work and M2000 cannot run.

Carry out the following steps if it is necessary to modify the system time. However, these actions will lead to loss of performance and alarm data of some NEs because of stopping M2000.

I. Becoming root

To become root, execute the following command:

bash-2.03$ su - rootII. Stopping M2000 ServicesTo stop M2000 services, execute the following commands: # stop_svc

# stop_tao_servicesIII. Stopping Sybase

To stop the Sybase, execute the following command:

# isql -SSYB -Usa -P1> shutdown SYB_BACKUP

2> go

1> shutdown SYB2> go

IV. Modifying the System TimeUse the command date to modify the system time to the local time. For example, to modify the date and time to 2003-11-17 16:30:43, execute the command:

# date 111716302004.43Mon Nov 17 17:53:29 CST 2003V. Restarting the ComputerTo restart the computer, execute the following command:

# init 6After the operating system reboots, the database and M2000 services will start automatically. 3.4.2 Not Modifying Server Host Name Do not modify the host name of the Server during M2000 running. Otherwise, the M2000 services will stop abnormally. Carry out the following steps if it is necessary to modify the host name. However, these actions will lead to loss of the performance and alarm data of some NEs because of stopping M2000.I. Becoming root

To become root, execute the following command:

bash-2.03$ su - rootII. Stopping M2000 ServicesTo stop M2000 services, execute the following commands:# stop_svc

# stop_tao_servicesIII. Stopping Sybase

To stop the Sybase, execute the following command:

# isql -SSYB -Usa -P1> shutdown SYB_BACKUP

2> go

1> shutdown SYB2> go

IV. Modifying Host NameModify the file /etc/hosts Modify the old host name to a new one.

Modify the file /etc/hostname.hme0

Modify the old host name to a new host name. ( Note:

The file names are different in different computers. Modify the file /etc/nodenameModify the old host name to a new one.Modify the file /etc/conf/tao.cfg

Modify the old host name to a new one.V. Restarting the ComputerTo restart the computer, execute the following command:

# init 6After the operating system reboots, the database and M2000 services will start automatically. 3.4.3 Not Modifying Server IP Address Do not modify the IP address of the Server during M2000 running. Otherwise, the M2000 services will stop abnormally.Carry out the following steps if it is necessary to modify the IP address. However, these actions will lead to loss of the performance and alarm data of some NEs because of stopping M2000I. Becoming root

To become root, execute the following command:

bash-2.03$ su - rootII. Stopping M2000 ServicesTo stop M2000 services, execute the following commands:# stop_svc

# stop_tao_servicesIII. Stopping Sybase

To stop the Sybase, execute the following command:

# isql -SSYB -Usa -P1> shutdown SYB_BACKUP

2> go

1> shutdown SYB2> go

IV. Modifying IP AddressTo modify the IP address, proceed as follows:Modify the file /etc/hosts.Modify the old IP address to a new one.For example, if you want to modify "10.129.27.118" to "10.130.5.1", edit the file /etc/hosts as follows:# vi /etc/hosts10.129.27.118 Jupiter loghostModify "10.129.27.118" to "10.130.5.1".Modify the file /opt/sybase/interfacesModify the old IP address to a new one.The value of the IP address in this file is saved in a hexadecimal format. In the line with a string of "/dev/tcp", the eight characters starting from the ninth character behind "\x" refer to the IP address. For example, if you want to modify "10.129.27.118" to "10.130.5.1", edit the file /opt/sybase/interfaces as follows:

# vi /opt/sybase/interfacesmaster tli tcp /dev/tcp \x000210040a811b760000000000000000

query tli tcp /dev/tcp \x000210040a811b760000000000000000The "0a811b76" is "10.129.27.118". To modify the IP address to "10.130.5.1", it is necessary to modify "0a811b76" to "0a820501". Modify the M2000 Configuration file of //etc/conf/imap.xmlIn the [ftp] tab, modify the old IP address behind "HostIP" to a new one. For example, if you want to modify "10.129.27.118" to "10.130.5.1", edit the file //etc/conf/imap.xml as follows:# vi //etc/conf/imap.xml

10.129.27.118Modify 10.129.27.118 to 10.130.5.1.V. Modifying Mask and Route of SubnetTo modify the mask and route of the subnet, proceed as follows:

Modify the file /etc/netmasksModify the old gateway to a new gateway and the old subnet mask to a new subnet mask. For example, if you want to modify the gateway "10.161.38.0" to "10.161.34.0", edit the file /etc/netmasks as follows:# vi /etc/netmasks10.161.38.0 255.255.254.000Modify "10.161.38.0" to "10.161.34.0".Modify the file /etc/defaultrouterModify the old route to a new one.

( Note:

If no such file exists, create one. Add an IP address in this file to indicate the route information, for example, "10.121.4.1". For example, if you want to modify the gateway "10.161.38.1 " to "10.161.34.1", edit the file /etc/defaultrouter as follows:# vi /etc/defaultrouter10.161.38.1

Modify "10.161.38.1" to "10.161.34.1".VI. Restarting the ComputerTo restart the computer, execute the following command:

# init 6After the operating system reboots, the database and M2000 services will start automatically.Chapter 4 Alarm Handling 4.1 Overview of Alarm Handling

The chapter describes the meanings and handling methods of M2000 system alarms. For NE alarm handling, refer to the online help at the M2000 Client. 4.2 System Performance Alarm4.2.1 Alarm MeaningThe CPU/memory utilization exceeds the threshold set by the user. The default threshold is 90%. 4.2.2 Possible CausesThe possible causes of this alarm include: The number of reported NE alarms exceeds the threshold in the specified period. For alarm response of the system, refer to iManager M2000 Mobile Element Management System System Description. The memory configuration of the database system is improper. The hardware configuration of the system fails to satisfy the requirements of the standard configuration. The system has an internal problem. 4.2.3 Handling Suggestions To clear the alarm, proceed the following:I. Querying the Information of Reported NE Alarms Check whether the CPU/memory utilization is too high because the number of reported NE alarms exceeds the threshold in the specified period. II. Querying CPU Utilization of Each Process Execute the following command to query the CPU utilization of each process:bash-2.03$ top

PID USERNAME THR PRI NICE SIZE RES STATE TIME CPU COMMAND

15061 root 35 58 0 109M 101M sleep 45:17 1.11% dataserverIII. Checking the Memory Configuration of the DatabaseIf the memory allocated to the database is too small, the efficiency of the database system will decrease greatly. Modify the in the line set shmsys:shminfo_shmmax= of the file /etc/system The here is: Memory size of the server (unit: MB) x 1024 x 1024 / 2. For example, if the memory size of the server is 4096MB, the value is 4,294,967,296.IV. Improving Hardware Environment Contact Huawei technical support personnel. 4.3 Disk Status Alarm4.3.1 Alarm MeaningThe disk partition utilization exceeds the threshold set by the user. The default threshold is 80%.4.3.2 Possible CausesThe possible causes of this alarm include: The utilization of a disk partition exceeds the threshold. The disk partitioning is inappropriate. 4.3.3 Handling Suggestions To clear the alarm, proceed the following:I. Clearing Useless Files in the System Clear overdue log files Log in as omcuser, open the directory /export/home/omc/var/logs, and clear the files *.log and *.trace with the command:

bash-2.03$ > . Clear temporarily files Log in as root and delete all the files in the directory /var/tmp. Clear useless files Delete useless files. II. Querying Disk Space Usage Execute the following command to query the disk space usage of each file system. bash-2.03$ df -kFilesystem kbytes used avail capacity Mounted on

/dev/md/dsk/d10 4131866 1548768 2541780 38% /

/proc 0 0 0 0% /proc

fd 0 0 0 0% /dev/fd

mnttab 0 0 0 0% /etc/mnttab

swap 7226880 16 7226864 1% /var/run

/dev/md/dsk/d30 4131866 2436502 1654046 60% /opt

/dev/md/dsk/d50 461119 64400 350608 16% /export/home

/dev/dsk/c1t5d0s1 106363848 37131072 68169138 36% /disk2

/dev/dsk/c1t5d0s3 92939212 32398589 59611231 36% /disk3Table 4-1 Disk space usage ParameterDescription

FilesystemFile system installed in the disk

kbytesSize of the file system

usedUsed space

availAvailable space

capacityDisk space utilization

For disk partitioning standards, refer to iManager M2000 Mobile Element Management System Installation Manual. Partition the disk according to the standards. 4.4 Database Threshold Alarm 4.4.1 Alarm MeaningThe database space usage exceeds the threshold set by the user. 4.4.2 Possible CausesThe possible causes of this alarm include: The free data space is insufficient in a database. The free transaction log space is insufficient in a database. 4.4.3 Handling Suggestions To clear the alarm, proceed the following:I. Querying Database Space ( Note:The following describes the alarm handling for the database fmdb. For the databases omcdb, pmdb, and sysmdb, the methods of alarm handling are the same. To query the space of the database fmdb, execute the following command:bash-2.03$ isql SSYB -Usa -P 1> sp_helpdb fmdb2> goname db_size owner dbid

created

status

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

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

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

--------

fmdb 300.0 MB sa 5

Dec 31, 2003

select into/bulkcopy/pllsort, trunc log on chkpt, ddl in tran, allow nulls by default

(1 row affected)

device_fragments size usage

free kbytes

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

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

fmdb_dev 200.0 MB data only

184334

fmdb_log 100.0 MB log only

not applicable

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

--

log only free kbytes = 101996

(return status = 0)

1>The numbers in bold indicate the sizes of the free data space and transaction log space in the database.II. Cleaning up the DatabaseClean up the transaction log If there is no sufficient free transaction log space, clean up the transaction log through the following two steps:1> dump tran fmdb with no_log2> goClean up the dataIf there is no sufficient free data space, it is necessary to displace the history data. It is recommended displacing the history data through [Fault/Alarm Displace] on the main menu of the M2000 Client. 4.5 Service Status Alarm 4.5.1 Alarm MeaningA service is terminated abnormally without executing the corresponding stop command. 4.5.2 Possible CausesThe possible causes of this alarm include: The service is terminated by using the kill command. A core dump occurs to the service. 4.5.3 Handling Suggestions To clear the alarm, proceed the following:I. Waiting for Auto Restart of the Service or Start All the M2000 Services Manually If the M2000 monitoring process is killed, it is necessary to start all the M2000 services manually. Become root and execute this command: # start_svc If one of other M2000 processes is killed, the M2000 monitoring process will restart the service without human intervention. II. Checking Whether a Core Dump Occurs to the ServiceCheck whether there is a core file in the directory /export/home/omc/var/logs. If yes, the service stops because a core dump occurs to it. In this case, back up the core file and all the log files in the directory /export/home/omc/var/logs and contact Huawei technical support personnel for troubleshooting. 4.6 System Log Status Alarm4.6.1 Alarm MeaningThe system fails to record the system log. 4.6.2 Possible CausesThe possible causes of this alarm include: The disk space is full. The service is running abnormally. 4.6.3 Handling Suggestions To clear the alarm, proceed the following:I. Cleaning up the Disk SpaceFor the method of cleaning up the disk space, see 4.3.3

REF _Ref70158273 \h Handling Suggestions in this manual. II. Querying the System LogView the system log files in the directory /export/home/omc/var/logs to find the causes of abnormal services. 4.7 OMC Connection Fault Alarm4.7.1 Alarm MeaningIf the communication between M2000 and an NE is abnormal, the system will generate this alarm. 4.7.2 Possible CausesThe possible causes of this alarm include: A fault occurs to the physical connection between M2000 and the NE. A fault occurs to the NE to be managed. The IP address of the NE at the M2000 Client is incorrect. The IP address of the M2000 at the NE is incorrect.4.7.3 Handling Suggestions To clear the alarm, proceed the following:I. Removing Faults in the Physical Connection Between M2000 and the NE After removing all the faults in the physical connection, perform a synchronization operation at the M2000 Client to make the Client synchronize with the NE. II. Modifying the IP Address of the NE Modify the IP address of the NE in M2000 so that it can be consistent with the actual IP address. III. Modifying the IP Address of M2000Modify the IP address of M2000 in the NE so that it can be consistent with the actual IP address.IV. Removing NE FaultsCheck whether the communication board or port of the NE is wrong. Chapter 5 Troubleshooting5.1 Overview of TroubleshootingThis chapter describes the troubleshooting procedure, provides common troubleshooting methods during M2000 installation and running.For maintenance and troubleshooting of Solaris operating system, refer to Solaris System Administration Manual. For maintenance and troubleshooting of Sybase, refer to Sybase System Administration Manual.5.2 Troubleshooting ProcedureGenerally, a troubleshooting procedure covers information collection, fault location and fault removal.5.2.1 Information Collection In case of a system fault, it is necessary to collect the following information: When and where the fault occurs Fault phenomena Alarm information System log5.2.2 Fault LocationFault location refers to the processes of looking for the actual fault cause from many possible causes. Collection and analysis of fault information help locate the fault cause.M2000 system faults include hardware faults and software faults. I. Hardware FaultsThe hardware faults include the ones occurring to M2000 server, client and networking equipment. The appearance and status indicators of hardware help locate hardware faults easily. II. Software FaultsThe software faults include the ones occurring to M2000 system, the operating system and the database that M2000 is based on. 5.2.3 Fault Removal I. Hardware FaultsRefer to the manual delivered with device. II. Software Faults Handle a software fault according to its cause. The software fault may be:

A M2000 system faultRefer to 5.3 Faults During M2000 Installation and 5.4 Faults During M2000 Running in this manual for handling.

A operating system faultRefer to Solaris System Administration Manual for handling. A database faultRefer to Sybase System Administration Manual for handling.III. Irremovable FaultsCollect all the information about an irremovable fault and contact Huawei for handling immediately. 5.3 Faults During M2000 InstallationThis section describes the faults occurring during M2000 installation.

For M2000 Installation, refer to iManager M2000 Mobile Element Management System Installation Manual.5.3.1 Failure in Installing Disk Mirror I. SymptomAfter mirroring, some child mirrors are found not in Okay status by executing the command metastat. II. Analysis The configuration file vfstab.mirror, mirr1.sh, or mirr2.sh is incorrect. Caution:

The names of physical devices vary with types and hard disk controllers. In the example below, the name of the first disk is c1t0d0 and the name of the second disk is c1t1d0. III. Handling To remove the fault, proceed as follows:Restore the original system file # cp /etc/vfstab.old /etc/vfstab# cp /etc/system.old /etc/system

Delete metadb

# metadb df /dev/dsk/c1t0d0s6

# metadb df /dev/dsk/c1t1d0s6Restart the system# rebootCheck and modify the configuration file Check vfstab.mirror, mirr1.sh, and mirr2.sh, and modify them. Reinstall the disk mirroring ( Note:

For the content and path of vfstab.mirror, mirr1.sh, and mirr2.sh, refer to 3.8 Installing Disk Mirror of the software installation in iManager M2000 Mobile Element Management System Installation Manual. 5.3.2 Failure in Building Sybase I. SymptomIn case building Adaptive Server fails during Sybase installation, the system will give an error message as follows: Building Adaptive Server 'xxxx':

Building master device... Master device complete.

Writing entry into directory services... Directory services entry complete.

Writing RUN_SERVER file... RUN_SERVER file complete.

Starting server... Task failed

Unable to boot server 'xxxx'.

Server 'xxxx' was not created.II. Analysis Before installing Sybase, it is necessary to modify the parameters of the shared memory of the operating system. Otherwise, the above situation will occur. III. Handling To remove the fault, proceed as follows:Modify the file /etc/systemAt the end of the file add the following: set shmsys:shminfo_shmmax= The is: memory size of the Server (unit: MB) x 1024 x 1024 / 2For example, if the server memory is 4,096 MB, = 4096 x 1024 x 1024/ 2 = 2,147,483,648.Restart M2000 and log in as dbuser# /usr/sbin/shutdown i6 g0 y

The login user name: dbuserReinstall Sybase

5.3.3 Failure in Reinstalling Sybase I. SymptomDuring Sybase reinstallation, the system prompts messages such as "Server XXX already exists in the file interfaces. II. Analysis The Sybase installer will create the file interfaces in the Sybase Install Directory. This file contains the description of the specified Server to be configured. During reinstallation, the Sybase installer will check the file. If the file and the name of the specified Server to be configured already exist, the installer will consider that Sybase has been installed in the system. In this case, the installer will stop. III. Handling Delete the file interfaces before reinstalling the Sybase.5.3.4 Failure in Installing M2000 Server Application Software I. SymptomThe system prompts an error message indicating database initialization failure during the installation of M2000 Server application software. II. Analysis The Sybase is not running or is running abnormally. III. Handling To remove the fault, proceed as follows:Check Sybase running status For the check of Sybase running status and reinstallation of Sybase, refer to iManager M2000 Mobile Element Management System Installation Manual.Reinstall M2000 Server application software5.3.5 Failure in Reinstalling M2000 Server Application Software I. SymptomSome M2000 services are not running after reinstallation of the M2000 Server application software. II. Analysis The installed M2000 software has not been uninstalled before M2000 software reinstallation. III. Handling To remove the fault, proceed as follows:Become root with the command:bash-2.03$ su - rootUninstall the installed M2000 software with the command:# . //uninstall.shReinstall the M2000 Server application software. 5.3.6 Failure in Installing M2000 Client Application Software I. SymptomDuring the installation of M2000 Client application software, the system prompts an error message indicating that there is no sufficient space in the disk and the installation fails. II. Analysis There should be at least 150 MB free space in the disk for the installation of M2000 Client application software. III. Handling To remove the fault, proceed as follows:Reserve enough free space in the disk. Reinstall M2000 Client application software. 5.3.7 Failure in Reinstalling M2000 Client Software I. SymptomThe M2000 Client program runs abnormally after it is reinstalled. II. Analysis The installed M2000 software has not been uninstalled before M2000 software reinstallation. III. Handling To remove the fault, proceed as follows:Uninstall the installed M2000 software. Run the M2000 uninstall program in the installation directory. Reinstall M2000 Client application software 5.4 Faults During M2000 Running5.4.1 Abnormal Service RestartI. Symptom

Some services automatically restart abnormally. II. AnalysisTo find out the cause of the fault, perform an analysis as follows: Sybase is abnormal. The internal system is abnormal. III. HandlingTo remove the fault, proceed as follows:Become root with the command:bash-2.03$ su - rootStop M2000 services with the commands:# stop_svc

# stop_tao_servicesStop Sybase with the command: # isql -SSYB -Usa -P1> shutdown SYB_BACKUP

2> go

1> shutdown

2> go

Set Sybase running parameters Refer to iManager M2000 Mobile Element Management System Installation Manual Software Installation. Start Sybase with the commands:# cd /opt/sybase/ASE-12_0/install# ./startserver f ./RUN_SYB

# ./startserver f ./RUN_SYB_backStart M2000 services with the commands: # start_ tao_services# start_svcView the system log.View the system log file in the directory /export/home/omc/var/logs to find the cause. 5.4.2 Failure in Starting or Stopping Services I. Symptom

Executing one of the following commands fails:

start_svc

stop_svc

kill_svc

II. Analysis

More than one users are executing the command above at the same time.III. Handling

Only one user can execute the command above at the same time.5.4.3 Failure in Logging in from M2000 Client I. SymptomThe user fails to log in when running the M2000 Client application software. II. Analysis To find out the cause of the fault, perform an analysis as follows: The login password is incorrect. (The system prompts that Invalid password.) The communication between the Client and the Server is abnormal. (The system prompt that The server doesnt exist or not running.)

The Server is running abnormally. (The system prompt that The server doesnt exist or not running.) M2000 locks the user because the number of login attempts of the user exceeds the maximum.

The Server has two or more IP addresses. The number of Clients accessing the Server exceeds the threshold. ( Note:

The system allows up to 15 Clients to access the Server at a time.III. Handling To remove the fault, proceed as follows:Log in again with the correct password. Check the connection between the Client and the Server. Refer to iManager M2000 Mobile Element Management System Installation Manual. Make sure that the Client can ping the Server. Check the running status of the Server. Refer to iManager M2000 Mobile Element Management System Installation Manual. Make sure that the Server can run normally. Wait for M2000 to unlock the user (normally 30 minutes)

Edit the file /etc/hosts Assign one IP address to the host name. M2000 Server uses this IP to communicate with M2000 Client.For example, M2000 Server has two IP addresses, 10.161.70.200 and 10.121.5.208, and the IP address 10.121.5.208 is used to communicate with M2000 Client. From the file //etc/conf/tao.cfg, you know that the host name is aries. Open the file /etc/hosts, and add # before 10.161.70.200 as follows:#10.161.70.200 aries loghost

10.121.5.208 aries loghostRestart M2000 Server application with the commands:bash-2.03$ su - root# stop_svc

# stop_tao_services# start_ tao_services# start_svc5.4.4 Failure in Starting NE LMT at Client I. SymptomThe user fails to start the LMT of an NE in the topology map at the M2000 Client.II. Analysis To find out the cause of the fault, perform an analysis as follows: The LMT software of the NE has not been installed in the M2000 client. The version of the installed LMT software is inconsistent with the NE version. The M2000 Server software is running abnormally. III. Handling To remove the fault, proceed as follows:Delete the installed LMT software. Obtain the LMT software consistent with the NE version. Reinstall the LMT software and then check whether the fault still exists. If yes, go to the next step. Log in to the Server. Query the status of M2000 services with svc_adm cmd status. If there is any service that is not running, start it with start_svc. 5.4.5 Abnormal Termination of Client Program I. SymptomThe main window of M2000 Client is closed automatically. II. Analysis To find out the cause of the fault, perform an analysis as follows: A user with the operation authority such as the system administrator kicks out the user operating the Client. In this case, the system will prompt a message before the Client interface is closed. The Server is running abnormally. In that case, the system will prompt a message before the Client interface is closed. III. Handling To remove the fault, proceed as follows:Request the system administrator to grant the operation rights. Check the running status of the Server. Refer to iManager M2000 Mobile Element Management System Installation Manual. Make sure that the Server can run normally. Restart the Client program. 5.4.6 Failure in Running Client ProgramI. SymptomThe user fails to run the M2000 Client program. II. Analysis To find out the cause of the fault, perform an analysis as follows: The computer is out of memory. The standard memory of the M2000 Client is 256 MB. If the memory is not enough, the system prompts message "out of memory". The Client software installation is incorrect. III. Handling To remove the fault, proceed as follows:Do not run multiple M2000 Client programs at the same operation terminal. Stop other running programs in the operation terminal. Reinstall the Client software. Uninstall the Client software and then install it again. 5.4.7 Failure in Printing Alarm Information in Real Time I. SymptomIf the real-time alarm printing is enabled at the Client, the printer fails to print the information of reported alarms in real time when the browser window displays these alarms. II. Analysis With the real-time alarm print enabled, M2000 does not print one alarm at a time. Instead, it performs a print every time when the number of received alarms reaches the preset value or in five minutes after it receives an alarm. III. Handling The situation is normal, requiring no handling. 5.4.8 Failure in Receiving Alarm Short Messages I. SymptomThe user specifies an E-mail address and a mobile phone to receive short messages in the Client. If an alarm occurs, the user can receive an E-mail but cannot receive any short message. II. Analysis The number of the mobile phone is set incorrectly. The number must start with a country code, for example, "8613612340001". The "86" is the country code of China. III. Handling To remove the fault, proceed as follows:Select [Fault/Fault service settings] to display the [Fault service settings] dialog box.

Click the [Remote Notify] tab.

Enter the correct mobile phone number in [Mobile telephone]. 5.4.9 Failure in Receiving Alarm Short Messages in Real TimeI. SymptomThe mobile phone receives an alarm message in ten minutes after the alarm occurs. II. Analysis It takes about six seconds to transmit and receive a short message. Therefore, M2000 can transmit up to ten short messages every minute. If a large quantity of alarms occurs, there will be a delay in short message reception. III. Handling To remove the fault, proceed as follows:Select [Fault/Fault service settings] to display the [Fault service settings] dialog box.

Click the [Remote Notify] tab.

Deselect one or more selected alarms according to the actual situation. 5.4.10 Abnormal Display of Characters on the Window of Client I. SymptomThe characters on the window are displayed abnormally when the Client is running. II. Analysis The configuration file is incorrect. III. Handling To remove the fault, proceed as follows:Uninstall the current M2000 Client application software. Reinstall the M2000 Client application software. 1iii