Netman4000 OMC-A: Network Management System Maintenance Guide

Netman4000 OMC-A
Network Management System

Maintenance Guide
Release 3.1.0
Doc. Code L2 FC10 31017 11 10 00

Copyright © 2007 UTStarcom, Inc. All rights reserved.
No part of this documentation may be reproduced in any form or by any means or
used to make any derivative work (such as translation, transformation, or adaptation)
without prior, express and written permission from UTStarcom, Inc.
UTStarcom, Inc. reserves the right to revise this documentation and to make changes
in content from time to time without obligation on the part of UTStarcom, Inc. to
provide notification of such revision or changes.
UTStarcom, Inc. provides this documentation without warranty of any kind, implied or
expressed, including but not limited to, the implied warranties of merchantability and
fitness for a particular purpose. UTStarcom may make improvements or changes in
the product(s) and/or the program(s) described in this documentation at any time.
UNITED STATES GOVERNMENT LEGENDS:
If you are a United States government agency, then this documentation and the
software described herein are provided to you subject to the following:
United States Government Legend: All technical data and computer software is
commercial in nature and developed solely at private expense. Software is delivered
as Commercial Computer Software as defined in DFARS 252.227-7014 (June 1995)
or as a commercial item as defined in FAR 2.101(a) and as such is provided with only
such rights as are provided in UTStarcom's standard commercial license for the
Software. Technical data is provided with limited rights only as provided in DFAR
252.227-7015 (Nov 1995) or FAR 52.227-14 (June 1987), whichever is applicable.
You agree not to remove or deface any portion of any legend provided on any
licensed program or documentation contained in, or delivered to you in conjunction
with, this User Guide.
UTStarcom, the UTStarcom logo, !-Volution, AccessGuard 500, AIRSTAR, AN-2000,
AN-FTTB, CommWorks, the CommWorks logo, iAN, iCell, Internode, Intranode,
iPATH, ISP, MovingMedia, mSwitch, Next Generation Network Technology. Now,
NGDLC, PAS, PAS Wireless, Seamless World, Softexchange, Sonata, Sonata
Access Tandem, Sonata HLR, Sonata IP, Sonata MSC, Sonata WLL, Telos, Total
Control, Unitech, WACOS, WICOPS, WLL, and Xtreme IP are registered trademarks
or trademarks of UTStarcom, Inc. and its subsidiaries.
Other brand and product names may be registered trademarks or trademarks of their
respective holders.
Any rights not expressly granted herein are firmly reserved.
Contents
About This Guide ........................................................................................................3
Introduction ........................................................................................................................3
Conventions.......................................................................................................................3
Notice ............................................................................................................................3
Text................................................................................................................................3
Figures and Screen Captures .......................................................................................4
Related Documentation .....................................................................................................4
1 Routine Maintenance .........................................................................................5

Daily Maintenance Tasks ..................................................................................................5
Checking NE Configuration Files Backup Status ..........................................................5
Checking Free Disk Space............................................................................................6
Checking Connection between iAN-8000 and OMC-A .................................................6
Weekly Maintenance Tasks...............................................................................................8
Checking Archived Files................................................................................................8
Viewing Performance Report ........................................................................................9
Oracle Database Maintenance Tasks ...............................................................................9
Checking Oracle Background Processes......................................................................9
Checking Oracle Listener Status.................................................................................10
Checking Database Instance ......................................................................................11
Checking TableSpace Status ......................................................................................11
Checking Control File ..................................................................................................12
Checking Redo Log File ..............................................................................................13
Checking Database File Status ...................................................................................13
Checking Tablespace Used Space .............................................................................14
Checking Archive Mode ..............................................................................................15
Checking Database Log ..............................................................................................15
Sybase Database Maintenance Tasks............................................................................16
Checking the Adaptive Server.....................................................................................16
Checking Default Sort Order .......................................................................................17
2 Troubleshooting...............................................................................................19
Cannot Access Security Management after Changing the User Password....................19
The User is Locked Out...................................................................................................19
The Alarm Timestamp is Incorrect ..................................................................................19
Configuring the Password Attempts and Lockout Time ..................................................20
NMS Login Failure...........................................................................................................20
ADSL Line Profile Assign Failure ....................................................................................21
Netman 4000 OMC-A Maintenance Guide

ii
Updating License Online..................................................................................................23

Modifying the reminder time ahead of password expiration ............................................23
Maintenance Guide Netman 4000 OMC-A

About This Guide
Introduction
This guide gives the details of how to maintain Netman4000 OMC-A.
Conventions
This guide may contain notices, figures, screen captures, and certain text
conventions.
Notice
The following table lists notices icons used in this guide.
Icon Notice Type Description
Information that contains important features or instructions but is not

Note
hazard-related.
Information to alert of potential damage to a program, data, system, or

device. If not avoided, may result in minor or moderate damage. It may
Caution
also alert against unsafe practices and potential program, data, system,
device damage.
Information to alert of operations that may cause potential accident,
Warning casualty, personal injury, fatality or potential electrical hazard. If not
avoided, could result in death or serious injury.
Information that indicates proper grounding precautions is required
ESD
before handling a product.
Text
The following table lists text conventions in this guide.
Convention Description
This typeface represents text that appears on a terminal
screen, including, configuration file names (only for system
Text represented by output file names), and command names, for example login.
Courier New Font
Commands entered by users are represented by bold, for
example, cd $HOME.
This typeface represents window names, dialog box names,
Text represented by bold tabs, field names, function names, directory, file names, process
names, and commands in text, for example, set the Time field.
Text represented by [Menu] This square brackets represents menus such as [File], and
and [Menu/Sub-menu] [File/New]
Text represented by This angle bracket represents button on screen, function key on
<Button> the keyboard and icon names for example, click <OK>.
Text represented by This typeface represents documents for reference, for example,
Document Name Netman 2020 Installation Guide

4 Chapter 0 About This Guide
Convention Description
Text represented by
This typeface represents files in Unix/Linux system files.
# File format:
Figures and Screen Captures

This guide provides figures and screen captures as examples. These examples
contain sample data. This data may vary from the actual data on an installed system.
Related Documentation
This section lists documents containing further information about Netman4000 OMC-
A, including:
• Netman4000 OMC-A System Overview
• Netman4000 OMC-A Operation Guide
• Netman4000 OMC-A Installation Guide

Routine Maintenance
1 1
This section describes the items that need to be monitored.
Daily Maintenance Tasks

Checking NE Configuration Files Backup Status
Task Description
Check whether the NE configuration file has been backed up or not.
Procedure
1 From OMC-A main menu, click [Tools/NE File Management System].
2 Click <Backup NE Config> in the left pane of the NE File Management System
window, and click Backup Tasks in the left pane.

3 If there is no back up task, click <Add> to add a backup task.
See more details on how to schedule a backup task in Netman 4000 OMC-A
Operation guide
4 Select a backup task, and click <Report> to see the report.
The Task Report window is displayed.
Figure 1 Task Report
The Status will be 'Success' in the Task Report window for successful back-up.
If the status is not 'Success', click <Show Detail> to see a detailed explanation.

6 Chapter 1 Routine Maintenance
Results and Verification

By default, the OMC-A saves the latest three NE configuration files automatically.
If the NE configuration files need to be backed up to tape, or other media, enter the
directory and backup these files manually.
Checking Free Disk Space

Task Description
Check if there is adequate free disk space on the OMC-A server.
Procedure
1 Telnet to the OMC-A server as root
2 Enter the following command
#df –k
Filesystem kbytes used avail capacity Mounted on

/dev/dsk/c0t0d0s0 3096423 1045740 1988755 35% /
/dev/dsk/c0t0d0s4 4129290 1950734 2137264 48% /usr
/proc 0 0 0 0% /proc
fd 0 0 0 0% /dev/fd
mnttab 0 0 0 0% /etc/mnttab
/dev/dsk/c0t0d0s3 2053605 258014 1733983 13% /var
swap 3425272 16 3425256 1% /var/run
swap 3670424 245168 3425256 7% /tmp

This command prints the allocation in KB. Capacity, the percentage of available
space that is currently allocated to all files on the file system should be lower than
75%.
If the allocated space is more than 75%, clear the unused files and free more space.
Checking Connection between iAN-8000 and OMC-A

Task Description
Check whether the communication between iAN-8000 and OMC-A is OK.
Procedure
1 From the OMC-A main menu, click [Fault/Current Alarm Management]
2 From Current Alarm Management main menu, click [Custom View/Add View].
3 In the Add Custom View window:
- Enter Heart-beat in the Custom View Name
- Select Heart-beat connection lost in Specific Problem
Chapter 1 Routine Maintenance 7
- Click <OK>
Figure 2 Add Custom View 1
4 Select Heart-beat from the Current Alarm View tree and the heart-beat alarm will
be displayed.
Check whether there is heart-beat failure alarm between the NMS and node.
Result and Verification

If there is heart-beat failure alarm, it shows the connection failure between iAN-8000
and OMC-A.

Weekly Maintenance Tasks

Checking Archived Files
Task Description
By default, there are seven archival tasks scheduled by the system automatically, for
event data, system log, user log, inventory log, history session, history alarm data
and history performance data. For each data type, only one task can be added.
Procedure
1 From OMC-A main menu, click [System Admin/Archiving Management].
Archiving Management window is displayed as following.
Figure 3 Archiving Management
2 Check whether "success" is shown in the Last Execution column.

1 Telnet to the OMC-A server as root.
2 Access the archived file.
Get the archived file directory by clicking <View> in the Archiving Management
window. The file directory can be modified by clicking <Modify>. Modify the File
directory parameter in the Modify Task window.
3 Check whether the archived file is created according to the configuration.
4 Backup the archived files to tape or other media, and delete the archived files if
the remaining disk space is limited.

Viewing Performance Report

Task Description
A performance report can be generated automatically or manually.
If Generate Report Automatically is checked for a specific template, OMC-A
automatically generates performance report according to the Auto-Report type.
Procedure and Result

1 Access the directory where the NMS is installed.
2 Access the directory where the automatic reports are stored.
For example, if you selected to store the performance report in local server,
when adding template, these report files will be saved at WebNMS/report_auto
under the OMC-A installation directory.
3 Check all the files. Backup the report files to the tape or other media, and delete
unnecessary report files if the remaining disk space is limited.
Oracle Database Maintenance Tasks

Routinely inspect the Oracle database to ensure maximum performance.
Checking Oracle Background Processes

Task Description
The following background processes that start when an Oracle instance is started.
• Database Write (DBWn) is the process that writes data files.
• Log Writer (LGWR) is the process that writes log files.
• System Monitor (SMON) is the process that monitors the instance status.
• Process Monitor (PMNO) is the process that monitors the client connection to the
database.
• Checkpoint (CKPT) is the process that updates the headers of all data files to
record the checkpoint details.
Procedure
1 Telnet to the Oracle database server;
2 Input the following command:
# ps –ef|grep “ora_”|grep –v grep
oracle 6586 1 0 May 15 ? 0:00 ora_pmon_inms

oracle 6594 1 0 May 15 ? 0:06 ora_smon_inms
oracle 6588 1 0 May 15 ? 6:50 ora_dbw0_inms
oracle 6590 1 0 May 15 ? 37:48 ora_lgwr_inms
oracle 6592 1 0 May 15 ? 0:45 ora_ckpt_inms
oracle 6596 1 0 May 15 ? 0:01 ora_reco_inms

All of the following Oracle background processes should be listed: dbw0, lgwr, pmno,
smon, ckpt. The name after those processes names is the Oracle database instance
name that was created during Oracle installation. In this book, we assume the
instance name suffix is inms.
Checking Oracle Listener Status

Task Description
Check whether the connection to the Oracle Database is ok.
Procedure
1 Telnet to the Oracle database server
# lsnrctl status
LSNRCTL for Solaris: Version 8.1.7.0.0 - Production on 08-FEB-2007

14:50:57
(c) Copyright 1998 Oracle Corporation. All rights reserved.
Connecting to (DESCRIPTION=(ADDRESS=(PROTOCOL=IPC)(KEY=EXTPROC)))
STATUS of the LISTENER
------------------------
Alias LISTENER
Version TNSLSNR for Solaris: Version 8.1.7.0.0 -
Production
Start Date 02-FEB-2007 11:48:05
Uptime 6 days 3 hr. 2 min. 52 sec
Trace Level off
Security OFF
SNMP OFF
Listener Parameter File /opt/oracle/db01/network/admin/listener.ora
Listener Log File /opt/oracle/db01/network/log/listener.log
Services Summary...
PLSExtProc has 1 service handler(s)
inms has 1 service handler(s)
The command completed successfully
Result
The Service Summary lists the database instance the Oracle listener is listening to.
The instance name INMS should be listed.
The instance INMS in Services Summary should be listed
Checking Database Instance

Task Description
Check the instance name and the status of the instance.
Procedure
1 Log on to Oracle database server as DBA.
2 Input the following command
SQL> select instance_name,status from v$instance;
INSTANCE_NAMW STATUS
--------------------------- -------------
INMS OPEN

The status of the current instance should be OPEN.
Checking TableSpace Status

Task Description
Check whether the status of the current tablespaces works normally.
Procedure
1 Log on to Oracle database server as DBA
2 input the following command:
SQL>select tablespace_name,status from dba_tablespaces;
TABLESPACE_NAME STATUS
------------------------------ ---------
SYSTEM ONLINE
UNDOTBS1 ONLINE
TEMP ONLINE
CWMLITE ONLINE
DRSYS ONLINE
EXAMPLE ONLINE
INDX ONLINE
ODM ONLINE
TOOLS ONLINE
USERS ONLINE

XDB ONLINE
TABLESPACE_NAME STATUS
------------------------------ ---------
INMS_TBLS_IDX_STATIC ONLINE
INMS_TBLS_DATA_STATIC ONLINE
INMS_TBLS_DATA_DYNAMIC ONLINE
INMS_TBLS_IDX_DYNAMIC ONLINE
Result
The status of all tablespaces should be ONLINE.
Checking Control File

Task Description
Check the associated control files of the Oracle instance.
Procedure
1 Log on to Oracle database server as DBA
SQL> select * from v$controlfile;
STATUS
-------
NAME
----------------------------------------------------------------------
/opt/oracle/db01/oradata/inms/control01.ctl
Result and Verifaciton

STATUS should be null, and there should be at least three entries under NAME.

Checking Redo Log File

Task Description
This command displays the associated log files of the Oracle instance.
Procedure
SQL> select * from v$logfile;
GROUP# STATUS
---------- -------
MEMBER
----------------------------------------------------------------------
1
/opt/oracle/db01/oradata/inms/redo01.log
2
3

STATUS should be null, and should show the location and status of three redo logs.
Checking Database File Status

Task Description
This command displays the location of each data files, status, and size in megabytes.
Procedure
SQL> select name, status, enabled, bytes/1024/1024 sizeMB from
v$datafile;
Part of the:
NAME
----------------------------------------------------------------------
STATUS ENABLED SIZEMB
------- ---------- ----------

/opt/oracle/db01/oradata/inms/system01.dbf
SYSTEM READ WRITE 480
/opt/oracle/db01/oradata/inms/tools01.dbf
ONLINE READ WRITE 1136.75
/opt/oracle/db01/oradata/inms/rbs01.dbf
ONLINE READ WRITE 516
NAME
----------------------------------------------------------------------
STATUS ENABLED SIZEMB
------- ---------- ----------
/opt/oracle/db01/oradata/inms/temp01.dbf
ONLINE READ WRITE 196.75
/opt/oracle/db01/oradata/inms/users01.dbf
/opt/oracle/db01/oradata/inms/indx01.dbf
Checking Tablespace Used Space

Task Description
This command displays the percent tablespace usage.
Procedure
SQL>select
A.tablespace_name,(1-(A.total)/B.total)*100 used_percent
from
(select tablespace_name,sum(bytes) total
from dba_free_space group by tablespace_name) A,
(select tablespace_name,sum(bytes) total
from dba_data_files group by tablespace_name) B
where A.tablespace_name=B.tablespace_name;
TABLESPACE_NAME USED_PERCENT
------------------------------ ------------
INDX .014467593
RBS 23.2015625
SYSTEM 20.9855769
TEMP .00390625
TOOLS .09765625
USERS 87.5003906
6 rows selected.
Result
Monitor those tablespaces with a USED_PERCENT above 65%. If the percent is
higher than 90%, the tablespace needs to be expanded by adding data files.
Checking Archive Mode

Task Description
Check the information about the Archive log mode status and the archives destination
folder.
Procedure
1 Log on to Oracle database server.
$sqlplus “/ as sysdba”
SQL> archive log list
Database log mode Archive Mode
Automatic archival Enabled
Archive destination /opt/oracle/db01/dbs/arch
Oldest online log sequence 29935
Current log sequence 29937
Result
Log mode should be Archive Mode and Automatic archival should be Enabled .
Checking Database Log

Task Description
Inspect the database logs.

Procedure
1 Log on to Oracle database server.
$ more $ORACLE_BASE/admin/inms/bdump/alert_inms.log
Expected Result
1 The redo log file should switch periodically.
2 There should be no error information. If has the error information, contact a
UTStarcom GSS engineer.
3 Check for ora- errors and warnings.
...
Thread 1 opened at log sequence 1
Current log# 1 seq# 1 mem# 0:
/opt/oracle/db01/oradata/omcx/redo01.log
...
Thread 1 advanced to log sequence 2
...
...

Successful open of redo thread 1.
Sybase Database Maintenance Tasks

Checking the Adaptive Server
Task Description
Check whether the Sybase Adaptive Server is started.
Procedure
Note: Here assume the Adaptive Server name is inms.
1 Open the Command Prompt window.

2 Connect to the Sybase database:

isql -Usa -P –Sinms
Result
If the above command execution succeeds, it represents that Sybase database
already is started. Otherwise, the following figure will be displayed and it represents
that the Sybase database is not started yet.
Figure 4 Error Information Prompt
Checking Default Sort Order

Task Description
Check whether the default sort order is already configured correctly.
Procedure
Execute the following commands to check the default sort order:
sp_helpsort
go
Result
As the following figure displays Sort Order = 101, utf8_nocase, it represents the
default sort order is configured correctly.
Figure 5 Check Default Sort Order Result

Troubleshooting
2 2
The following are the most common problems encountered when using Netman 4000
OMC-A, and suggested solutions.
Cannot Access Security Management after Changing the User

Password
Symptom
The user cannot access security management after changing the user password. The
system displays the error message:
The error ID is 210001 or the user information is outdated, please log on again.
Probable Cause
The user password contains special characters, such as "#".
Solution
Change the user password. The password should be alphanumeric character strings.
It is recommended to set the password with only alphanumeric character strings
when creating a new user.
The User is Locked Out

If the wrong password is entered in the Netman 4000 OMC-A three times, the
account will be locked out and the system will display a log on error message. This
mechanism helps to prevent unauthorized user access to the OMC system.
To unlock the system, log on to the application server as root and then launches IE
and enters the following URL in the address bar:
http://xxx.xxx.xxx.xxx:9090/jsp/test/smtest/unlock.jsp
The xxx.xxx.xxx.xxx is the NMS server IP address. For example, if the Netman 4000
OMC-A Server IP address is 172.21.73.66, then the following message is displayed:
This script was used to unlock all users! The user is
unlocked :root172.21.73.66
The Alarm Timestamp is Incorrect

Symptom
The alarm timestamp is incorrect in the client.
Probable Cause
The time zone is not consistent with the server.
Solution
1 Check that the time zone in the client is the same as the server.

20 Chapter 2 Troubleshooting
Click start button. Click Control Panel, and then double-click Date and Time.
Click the Time Zone tab, and then select the correct time zone from the drop-
down list. Click <Apply>.
2 On the server, use the following command to view the time zone in Solaris OS.
#cat /etc/TIMEZONE
3 Change the time zone on the client, then log on to the Netman 4000 again. The
alarm timestamps should now be correct.
Configuring the Password Attempts and Lockout Time

Symptom
By default when the user attempts to log on with an incorrect password three times,
the client will be locked out 120 minutes.
Solution
1 Shut down the Netman 4000 OMC-A application.
2 Modify WebNMS/conf/ngnms/SM/UNMS_SM.conf
Modify the following lines:
Attempttimes = 3
Locktime = 120
Modify locktime (minutes) and attempttimes (attempts) as desired. .

3 Restart the Netman 4000 OMC-A application to take effect the parameters.
NMS Login Failure

Symptom
1 None of the clients can log on to the NMS System
2 Some clients can’t log on to the NMS System.
Probable Cause
• The Netman 4000 OMC-A disk or Database Server disk is full.
• Java Web Start configuration is incorrect.
• The client firewall (Windows XP) is disabled.
• The client Internet Explorer configuration is incorrect.
• The client hostname isn’t configured.
Solution
1 Log on to the Netman 4000 Application Server and Database Server. Check that
there is sufficient disk space.
#df -k.

Chapter 2 Troubleshooting 21
2 Determine if JRE has been installed correctly in the client. Ensure the Java Web
Start configuration is correct.
a Click start, point to Settings, click Control Panel to open Control Panel
window.
b Click Java icon to open Java Control Panel window.
c Click the Java tab and click View button in the Java Application Runtime
Settings frame.
The Java Runtime Version should be 1.5.0_XX.
d Clear the check box of any earlier versions.
e Click <OK>.
Figure 6 JNLP Runtime Settings
3 Determine if the client firewall is disabled (Windows XP).

Launch the Local Area connection.
Click Properties, and then click the Advanced tab;
Click Settings, and then select Off to turn off Windows firewall.
4 Determine if the client Internet Explorer configuration is correct
Launch the IE;
On the Tools menu, click the Internet Options, and then click the Connections tab.
Click LAN Settings. In the Automatic Settings group, clear Automatically detect
settings. In the Proxy server group, clear Use a proxy server…
ADSL Line Profile Assign Failure

Note: The section is only for OMC-A Windows version.

22 Chapter 2 Troubleshooting
Symptom
Fail to assign ADSL Line Profile to the port in iAN8k-B110.
Cause
The MTU value of the network card is set to 1200, so the data package which is large
than 1200Bytes can not be sent to the device successfully.
Solution
Follow the steps below to delete the MTU item in the registry.
1 From the Windows Start menu, click [Start/Run] to open the Run window.
2 Enter regedit in the text box, and click OK to open the registry editor.
3 From the navigation tree, find [My
Computer\HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\TCTi
p\Parameters\Interfaces].
4 Double-click Interfaces to display all the sub-items. Each sun-item is
corresponding to a network card.
5 Check the value of IPAddress in every sub-item, if it is exactly the IP address of
the server, the sub-item is the one we need. The following picture is shown as an
example.

Chapter 2 Troubleshooting 23
6 Find MTU key in the sub-item which was found in the Step 5, select Delete in the
right-click menu, and then click Yes to confirm the deletion.
7 Close the registry editor.
8 Restart the server.
Updating License Online

To update the license when the system is running, execute the following steps:
1 Copy the license file license.xml.sig to the folder<APP server installation
directory>.
2 On an OMC client, log in to NMS system.
3 Select [Help/About] from the main menu
4 Click <License Info…> to display the license information
5 Click <Reload> to load the latest license file.
Modifying the reminder time ahead of password expiration

If the user password expiration time is approaching, a message will be prompted to
remind the user to modify the password. The reminder time ahead of expiration can
be configured; the default value is 7 days. The corresponding parameter is
PwdExpire (in day) in the file <APP server installation
directory>/conf/ngnms/SM/UNMS_SM.conf.

UTStarcom, Inc. USA
1275 Harbor Bay Parkway Alameda, CA 94502, USA
Tel: 510-864-8800 Fax: 510-864-8802
China India Japan Europe Latin America
No. 368 Liuhe Road, 805 Signature Towers II, Shiba Koen Parktower 9F/10F Campus Kronberg 7 2801 SW 149th Ave
Hi-Tech Industry Development Zone, South City I 2-11-1 Shiba-koen, Minato-ku Kronberg, 61476 Suite 100
Binjiang, Hangzhou 310053, PRC Gurgaon, Tokyo 105-0011 JAPAN Germany Miramar, FL 33027, USA
+86-571-81920000 Haryana 122001, India +81-3-6430-8600 +49 (617) 3946-3460 954-447-3077
+91 124 5166100
About UTStarcom www.utstar.com
Headquartered in the United States with sales, support, and manufacturing facilities worldwide, UTStarcom designs, manufactures, sells, and installs an integrated
suite of wireless and wireline access network and switching systems. UTStarcom's complete suite of network equipment gives telecommunication service providers
the means to cost-effectively provide efficient and scalable voice, data, and Internet services around the globe.
Copyright ® 2007 UTStarcom, the UTStarcom logo, !-Volution, AIRSTAR, AN-2000, AN-FTTB, CommWorks, the CommWorks logo, iAN, iCell, Internode,
Intranode, iPATH, ISP, MovingMedia, mSwitch, Next Generation Network Technology. Now, NGDLC, PAS, PAS Wireless, Seamless World, Softexchange, Sonata,
Sonata Access Tandem, Sonata HLR, Sonata IP, Sonata MSC, Sonata WLL, Telos, Total Control, Unitech, WACOS, WICOPS, WLL, and Xtreme IP are registered
trademarks or trademarks of UTStarcom, Inc. and its subsidiaries.

Netman4000 OMC-A: Network Management System Maintenance Guide

Uploaded by

Copyright:

Available Formats

You might also like

Netman4000 OMC-A: Network Management System Maintenance Guide

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Netman4000 OMC-A: Network Management System Maintenance Guide

Uploaded by

Copyright:

Available Formats

Netman4000 OMC-A

Network Management System

Doc. Code L2 FC10 31017 11 10 00

1 Routine Maintenance .........................................................................................5

Netman 4000 OMC-A Maintenance Guide

Updating License Online..................................................................................................23

Maintenance Guide Netman 4000 OMC-A

Icon Notice Type Description

Information that contains important features or instructions but is not

Information to alert of potential damage to a program, data, system, or

Netman 4000 OMC-A Maintenance Guide

Figures and Screen Captures

Maintenance Guide Netman 4000 OMC-A

This section describes the items that need to be monitored.

Daily Maintenance Tasks

window, and click Backup Tasks in the left pane.

Netman 4000 OMC-A Maintenance Guide

Results and Verification

Checking Free Disk Space

Filesystem kbytes used avail capacity Mounted on

Results and Verification

Checking Connection between iAN-8000 and OMC-A

Result and Verification

Netman 4000 OMC-A Maintenance Guide

Weekly Maintenance Tasks

2 Check whether "success" is shown in the Last Execution column.

Results and Verification

Maintenance Guide Netman 4000 OMC-A

Viewing Performance Report

Procedure and Result

Oracle Database Maintenance Tasks

Checking Oracle Background Processes

oracle 6586 1 0 May 15 ? 0:00 ora_pmon_inms

Results and Verification

Checking Oracle Listener Status

LSNRCTL for Solaris: Version 8.1.7.0.0 - Production on 08-FEB-2007

(c) Copyright 1998 Oracle Corporation. All rights reserved.

The instance INMS in Services Summary should be listed

Checking Database Instance

Result and Verification

Checking TableSpace Status

Netman 4000 OMC-A Maintenance Guide

Checking Control File

Result and Verifaciton

Maintenance Guide Netman 4000 OMC-A

Checking Redo Log File

Result and Verification

Checking Database File Status

Netman 4000 OMC-A Maintenance Guide

Checking Tablespace Used Space

Checking Archive Mode

Checking Database Log

Netman 4000 OMC-A Maintenance Guide

Thread 1 advanced to log sequence 4

Sybase Database Maintenance Tasks

Note: Here assume the Adaptive Server name is inms.

1 Open the Command Prompt window.

2 Connect to the Sybase database: