31040812-N2000 Installation Manual

HUAWEI
HUAWEI iManager N2000 Fixed Network

Integrated Management System
Installation Manual
V200R002
HUAWEI iManager N2000 Fixed Network Integrated

Management System
Installation Manual
Manual Version T2-100412-20030924-C-2.20

Product Version V200R002
31040812
BOM
Huawei
Technologies
Co.,
Ltd.
provides
customers
with
comprehensive technical support and service. Please feel free to

contact our local office, customer care center or company
headquarters.
Huawei Technologies Co., Ltd.

Address: Administration Building, Huawei Technologies Co., Ltd.,
Bantian, Longgang District, Shenzhen, P. R. China
Postal Code: 518129
Website: http://www.huawei.com
Email: support@huawei.com
2003 Huawei Technologies Co., Ltd.
All Rights Reserved

No part of this document may be reproduced or transmitted in any
form or by any means without prior written consent of Huawei
Technologies Co., Ltd.
Trademarks
, HUAWEI, C&C08, EAST8000, HONET,
, ViewPoint, INtess,
ETS, DMC, TELLIN, InfoLink, Netkey, Quidway, SYNLOCK, Radium,

M900/M1800, TELESIGHT, Quidview, Musa, Airbridge, Tellwin,
Inmedia, VRP, DOPRA, iTELLIN, HUAWEI OptiX, C&C08 iNET,
NETENGINE, OptiX, SoftX, iSite, U-SYS, iMUSE, OpenEye, Lansway,
SmartAX are trademarks of Huawei Technologies Co., Ltd.
Notice
The information in this document is subject to change without notice.
Every effort has been made in the preparation of this document to
ensure accuracy of the contents, but all statements, information, and
recommendations in this document don't constitute the warranty of
any kind, express or implied.
About This Manual
Version
The product version corresponds to the manual is iManager N2000
Fixed Network Integrated Management System V200R002.
Contents
This manual introduces the installation and configuration of iManager
N2000 Fixed Network Integrated Management System (hereinafter
referred to as iManager N2000), as well as that of Solaris operating
system, Sybase database system, Oracle database system and SQL
Server database system. Frequently Asked Questions (FAQ) are
given to help solve problems during installation.
The manual consists of four chapters and appendix as follows:
z
Chapter 1 System Overview introduces the system features and

software/hardware structure of iManager N2000.
Chapter 2 Installing iManager N2000 on Solaris + Sybase

describes the installation of Solaris operating system, Sybase
database system and iManager N2000 on Solaris.
Chapter 3 Installing iManager N2000 on Solaris + Oracle

describes the installation of Solaris operating system, Oracle
database system and iManager N2000 on Solaris.
Chapter 4 Installing iManager N2000 on Windows describes

the installation of SQL Server database system and iManager
N2000 on Windows.
Chapter 5 Frequently Asked Questions collects the FAQ

during the installation of iManager N2000.
Appendix describes disk partitioning rules, database space

configuration, how to uninstall NMS, how to install and use tape
drive, as well as abbreviations used in this manual.
Target Readers
The manual is intended for the following readers:
z
Network design & management personnel
Network maintenance personnel
Engineer for iManager N2000 Integrated Network Management

System
Conventions
This document uses the following conventions:
I. General conventions
Convention
Description
Arial
Normal paragraphs are in Arial.
Arial Narrow
Warnings, cautions, notes and tips are in Arial Narrow.
Bold
Headings, Command, Command Description are in boldface.
Terminal Display
Terminal Display is in Courier New; message input by the

user via the terminal is in boldface.
II. GUI conventions

Convention
Description
<>
Message entered via the terminal is within angle brackets.
[]
MMIs, menu items, data table and field names are inside
square brackets [ ].
Multi-level menus are separated by forward slashes (/). For

example, [File/Create/Folder].
III. Keyboard operation

Format
Description
<Key>
Press the key with key name expressed with a pointed

bracket, e.g. <Enter>, <Tab>, <Backspace>, or<A>.
<Key1+Key2>
Press the keys concurrently; e.g. <Ctrl+Alt+A> means the

three keys should be pressed concurrently.
<Key1, Key2>
Press the keys in turn, e.g. <Alt, A> means the two keys
should be pressed in turn.
[Menu Option]
The item with a square bracket indicates the menu option,

e.g. [System] option on the main menu. The item with a
pointed bracket indicates the functional button option, e.g.
<OK> button on some interface.
[Menu1/Menu2/Menu3]
Multi-level menu options, e.g. [System/Option/Color setup]

on the main menu indicates [Color Setup] on the menu
option of [Option], which is on the menu option of [System].
IV. Mouse operation

Action
Click
Description
Press the left button or right button quickly (left button by
default).
Action
Description
Double Click
Press the left button twice continuously and quickly.
Drag
Press and hold the left button and drag it to a certain

position.
V. Symbols
Eye-catching symbols are also used in this document to highlight the
points worthy of special attention during the operation. They are
defined as follows:
Caution: Means reader be extremely careful during the

operation.
Note: Means a complementary description.
[!]: Some important steps are marked by it for special notice.
Environmental Protection
This product has been designed to comply with the requirements on
environmental protection. For the proper storage, use and disposal of
this product, national laws and regulations must be observed.
Installation Manual
Table of Contents
Table of Contents
Chapter 1 System Overview .........................................................1-1
1.1 Architecture ........................................................................1-2
1.1.1 Hardware Architecture.............................................1-2
1.1.2 Software Architecture ..............................................1-4
1.2 About Installation................................................................1-5
1.2.1 Installation Mode .....................................................1-5
1.2.2 Installation Flow.......................................................1-6
1.3 Configuration Requirements ..............................................1-7
1.3.1 Server ......................................................................1-7
1.3.2 Client .......................................................................1-9
1.4 About Licensing................................................................1-11
1.4.1 Why Licensing Needed .........................................1-11
1.4.2 Applying for License ..............................................1-11
Chapter 2 Installing iManager N2000 on Solaris + Sybase .......2-1
2.1 Introduction ........................................................................2-1
2.2 Preparations for Installation ...............................................2-1
2.3 Standalone Installation Mode.............................................2-3
2.3.1 Installing Operating System ....................................2-4
2.3.2 Installing Operating System Patch ........................2-11
2.3.3 Installing Sybase Database System......................2-14
2.3.4 Installing Sybase Database Patch.........................2-34
2.3.5 Installing NMS Server............................................2-36
2.3.6 Starting NMS Server and Client ............................2-55
2.4 Client Installation Mode....................................................2-59
i
Installation Manual
Table of Contents
2.4.1 Installing Operating System ..................................2-59

2.4.2 Installing NMS Client .............................................2-60
Chapter 3 Installing iManager N2000 on Solaris + Oracle.........3-1
3.1 Introduction ........................................................................3-1
3.3.2 Installing Operating System Patch ..........................3-4
3.3.3 Installing Oracle Database System .........................3-4
Chapter 4 Installing iManager N2000 on Windows ....................4-1
4.1 Introduction ........................................................................4-1
4.3.2 Installing Operating System Patch ..........................4-3
4.3.3 Install Database System..........................................4-4
4.3.4 Install Database Patch ..........................................4-12
4.3.5 Configure Database Memory ................................4-14
4.4.1 Installing Operating System ..................................4-38
4.4.2 Installing NMS Client .............................................4-39
Chapter 5 Frequently Asked Questions ......................................5-1
5.1 Workstation ........................................................................5-1
ii
Installation Manual
Table of Contents
5.1.1 How to Set up Sun Workstation from CD Drive

(Sun/Solaris)?...................................................................5-1
5.1.2 How to Set IP Address of Sun Workstation
(Sun/Solaris)?...................................................................5-2
5.1.3 How to Install Solaris from Remote Workstation
(Sun/Solaris)?...................................................................5-3
5.1.4 How to Modify Hostname of Sun Workstation
(Sun/Solaris)?...................................................................5-4
5.1.5 How to Configure DNS of Sun Workstation
(Sun/Solaris)?...................................................................5-4
5.1.6 How to Boot up from CD Drive (Sun/Solaris)? ........5-5
5.1.7 How to Enable FTP? ...............................................5-5
5.1.8 How to Enable Telnet? ............................................5-6
5.1.9 File Size Changed after FTP Transmission.........5-6
5.1.10 Cannot Execute Program Files after FTP
Transmission.................................................................5-7
5.2 Database System...............................................................5-7
5.2.1 After Abnormally Shut down of SUN Workstation
(Sun/Solaris/Sybase) ....................................................5-7
5.2.2 How to Set the sa Password (Sun/Solaris/Sybase)?5-8
5.2.3 How to Set the sa Password (Windows/SQL Server)?5-9
5.2.4 Unable to Start Sybase........................................5-9
5.2.5 How to Install Sybase11.9.2?................................5-10
5.2.6 Sybase 11.9.2 Dynamic Database Interface Memory
Leakage..........................................................................5-11
5.2.7 Sybase 12.0 Dynamic Database Interface Memory
Leakage..........................................................................5-13
5.2.8 How to Add, Delete and Modify an Oracle Instance
(Oracle)...........................................................................5-14
iii
Installation Manual
Table of Contents
5.2.9 How to Modify the Maximum Number of Oracle

Connections (Oracle)......................................................5-14
5.2.10 Where to Put the Configuration Information and Files
after Oracle is Installed (Oracle).....................................5-15
5.2.11 How to Uninstall Oracle Database Completely
(Oracle)...........................................................................5-15
5.2.12 Unable to Start Oracle Database (Oracle).......5-15
5.2.13 NMS Database Files Are Deleted by Mistake and Fail
to be Created When NMS Is Reinstalled (Oracle) .........5-16
5.2.14 How to Modify Oracle SA system Password (Oracle)5-17
5.3 Network Management System.........................................5-17
5.3.1 Abnormal NMS Functions..................................5-17
5.3.2 Unable to Install the NMS again ........................5-18
5.3.3 Illegal Characters ...............................................5-19
5.3.4 Unable to Log in to System Monitor...................5-19
5.3.5 Unable to Display File Names while Copying....5-19
5.3.6 No Response during Installation........................5-19
5.3.7 Cannot Install Normally After Uninstalling.............5-20
5.3.8 Installation Fails Due to Improper Password Setting5-20
Appendix A Disk Partitioning Rules ........................................... A-1
A.1 For Solaris ........................................................................ A-1
A.1.1 Disk Partitioning Rules........................................... A-1
A.1.2 Disk Partitioning Plan............................................. A-1
A.2 For Windows..................................................................... A-6
A.2.1 Disk Partitioning Rules........................................... A-6
A.2.2 Disk Partitioning Plan............................................. A-7
Appendix B Database Space Configuration .............................. B-1
B.1 For Solaris ........................................................................ B-1
iv
Installation Manual
Table of Contents
B.2 For Windows..................................................................... B-2

Appendix C Uninstall NMS .......................................................... C-1
C.1 For Solaris ........................................................................ C-1
C.1.1 Uninstalling NMS Server........................................ C-1
C.1.2 Uninstalling NMS Client ......................................... C-2
C.2 For Windows..................................................................... C-3
C.2.1 Uninstalling NMS Server........................................ C-3
C.2.2 Uninstalling NMS Client ......................................... C-4
Appendix D Install and Use Tape Drive...................................... D-1
D.1 For Solaris ........................................................................ D-1
D.1.1 Installing and Uninstalling of Tape Drive ............... D-1
D.1.2 Commands............................................................. D-3
D.2 For Windows..................................................................... D-5
D.2.1 Installing and Uninstalling Tape Drive ................... D-5
Appendix E Abbreviations........................................................... E-1
Installation Manual
Chapter 1 System Overview

iManager N2000 is a network management system (NMS)
developed by Huawei, which provides unified management and
maintenance
communication
of
switching
&
access
products,
equipment.
It
implements
and
network
data
element
management and network management.

Some terms are listed below before starting to install iManager
N2000.
Server: It may refer to hardware or software. In terms of
client/server architecture, server means software, that is, the server
application. The computer that runs the server application may also
be called the server. Here in this manual, the server means
hardware.
Client: Likewise, In terms of client/server architecture, client
refers to the client application. The client application can run with the
server application or independently on a computer. The computer
that runs with the client application only is called a client.
Workstation: In this manual, workstation refers to a computer
running the UNIX system. It can run the network management server
application (now referred to as NMS server), or can run the network
management client application (now referred to as NMS client).
Client/Server Architecture:
1-1
Installation Manual
The client/server architecture means that multiple clients are

interconnected with the server through Local Area Network (LAN) or
Wide Area Network (WAN). The user can operate on the client and
share the data saved in the server.
The client of iManager N2000 implements the workstation
function (WSF) of Telecommunication Management Network (TMN).
The user can manage network devices through the client.
The server of iManager N2000 implements the Operating
System Function (OSF) of TMN. It is used to save network data and
provide management functions for network devices.
1.1 Architecture
1.1.1 Hardware Architecture
I. Standard client/server architecture
The server application and the client application of iManager
N2000 run on different computers, which are respectively called
server and client. They can run on either Windows or Solaris.
iManager
N2000
employs
architecture, as shown in Figure 1-1.
1-2
the
standard
client/server
Installation Manual
iManager N2000
Client 1
iManager N2000
ClientNN
Client
iManager N2000
Server
ATM/IP
Figure 1-1 Standard client/server architecture of iManager N2000
II. Multiple client/server architecture

The management capability of iManager N2000 can satisfy
most of the management requirements. If a large scale network is
beyond the management range of the standard client/server
architecture, multiple client/server architecture is recommended, as
shown in Figure 1-2:
1-3
Installation Manual
iManager N2000
Client 1
iManager N2000
Server 1
ATM/IP
iManager N2000
Client M
iManager N2000
Server 2
iManager N2000
Server N
ATM/IP
ATM/IP
Figure 1-2 Multiple client/server architecture of iManager N2000

Under this architecuture, a client can log in to different servers.
1.1.2 Software Architecture

Figure 1-3 shows the software architecture of iManager N2000.
It consists of server application and client application.
1-4
Installation Manual
Server Application
Server
Sybase/SQL Server
Solaris/Windows
Client Application
Client Application
Java Virtual Machine
Java Virtual Machine
Solaris/Windows
Solaris/Windows
Client N
Client 1
Figure 1-3 Software architecture of iManager N2000
1.2 About Installation

1.2.1 Installation Mode
Standalone installation mode: If this mode is selected, both
client application and server application will be installed. It is usually
used to install the NMS server. Database system should be also
installed.
Client installation mode: If this mode is selected, only the
client application will be installed. You are not allowed to install
server application only. The client application will not occupy too
much disk space.
1-5
Installation Manual
1.2.2 Installation Flow

Figure 1-4 shows the installation flow of NMS installation.
Herein, the NMS includes client application and server application.
Start
Preparation
Install OS
Installation
Mode
Standalone
Client
Install Database
Install NMS
End
Figure 1-4 Installation flow

Figure 1-4 shows the installation flow of iManager N2000.
During the NMS deployment, Huawei pre-installs the operating
system and database. Herein, only the NMS needs to be installed by
the user. The password for pre-installed operating system and
database depends on the specific environment. The following table
1-6
Installation Manual
shows the default user names and passwords for pre-installed

operating system and database:
Table 1-1 List of default usernames and passwords
System configuration
Solaris+Sybase
Solaris+Oracle
Windows 2000 +
SQL Server 2000
Super username
Password
Solaris
root
root
Sybase
sa
sa
Solaris
root
root
sys
change_on_install
system
manager
Windows 2000
administrator
admin
SQL Server 2000
sa
sa
Oracle
1.3 Configuration Requirements

1.3.1 Server
I. Hardware configuration
Table 1-2 iManager N2000 server hardware (Windows)
Configuration Item
Host
CPU
RAM
Hard Disk
CD Drive
Network Adapter
Sound Card
Typical System Requirements

PC server
1.8G Hz
1GB
36GB
48X
Integrated
Integrated
1-7
Installation Manual
Table 1-3 iManager N2000 server hardware (Solaris)

Configuration Item
Workstation
CPU
RAM
Hard Disk
CD Drive
Network Adapter
Sound Card
Typical System Requirments

Blade 2000
900MHz
1GB
2*73GB
DVD
Integrated
Integrated
II. Software configuration

iManager N2000 server can be installed either on Windows
operating system or on Solaris operating system. Installation on
Solaris operating system falls into two modes in accordance with
different databases installed: One is Solaris operating system +
Sybase database, and the other is Solaris operating system + Oracle
database.
Table 1-4 iManager N2000 server software (Windows)
Software Name
OS
Database
NMS
Software Version
Windows 2000 Server
Microsoft SQL Server 2000
iManager N2000 Fixed Network Integrated Management System
Server and Client
Table 1-5 iManager N2000 server software (Solaris + Syabse)

Software Name
OS
Database
Software Version
Solaris 8 for SPARC
Sybase 12.0 for Solaris (SPARC)
1-8
Installation Manual
Software Name
NMS
Software Version
Server and Client
Table 1-6 iManager N2000 server software (Solaris + Oracle)

Software
Name
OS
Database
NMS
Software Version
Solaris 8 for SPARC
Oracle 8.1.7.0.0 for Solaris
iManager N2000 Fixed Network Integrated Management System Server and
Client
1.3.2 Client
I. Hardware configuration
Table 1-7 iManager N2000 client hardware (Windows)
Configuration Item
Host
CPU
RAM
Hard Disk
CD Drive
Network Adapter
Sound Card

Desktop Computer
1.8GHz
512MB
20GB
48X
Integrated
Integrated
Either a PC or a workstation can be adopted as the client,

whose typical configuration is as follows:
1-9
Installation Manual
Table 1-8 iManager N2000 client hardware (Solaris)

Configuration Item
Workstation
CPU
RAM
Hard Disk
CD Drive
Network Adapter
Sound Card

Blade 150
500M Hz
512MB
20GB
Original
Integrated
Integrated
II. Software configuration

Table 1-9 iManager N2000 client software (Windows)
Software Name
OS
NMS
Software Version
Windows 2000 Professional
Client
Table 1-10 iManager N2000 client software (Solaris)

Software Name
OS
NMS
Software Version
Solaris 8 for SPARC
Client
1-10
Installation Manual
1.4 About Licensing

1.4.1 Why Licensing Needed
With license, iManager N2000 can be controlled from the
following aspects:
z
Installation Software Package: iManager N2000 consists

of several software packages. Each package needs a
license for installation.
Managed Device Number: A license is needed for adding a

device. If the authorized licenses run out, no more devices
are allowed to add into the NMS.
Accessed Client Number: The number of clients that

access to the NMS at the same time is limited by the
license number. If the authorized licenses run out, no more
clients are allowed to access the NMS.
Expiry Date: The NMS will be unavailable after the system

running time expires according to the license agreement.
1.4.2 Applying for License

I. Query license
Select [Help/About] from the client main menu to pop up About
dialog box. The "License tab shows the details of the license
information and the usage of it.
1-11
Installation Manual
II. Apply for license

A temporary license is provided in the install disk of iManager
N2000. The expiry date is 30 days.
To apply for formal license or a license of expanding
authorization, please contact the local agent, customer care center
or company headquarters of Huawei.
For how to upgrade license, please refer to "Upgrade License"
from the operation list of the online help.
1-12
Installation Manual
Chapter 2 Installing iManager

N2000 on Solaris + Sybase
Chapter 2 Installing iManager N2000

on Solaris + Sybase
2.1 Introduction
This chapter describes the installation of iManager N2000 on
Solaris operating system + Sybase database, including standalone
installation mode and client installation mode, as well as that of
Solaris and Sybase.
2.2 Preparations for Installation

I. Check hardware
Before workstation power-on, find the 110V/220V AC switch
attached to the power module. Adjust the switch according to the
local AC voltage. Otherwise, the power module may be burned!
It is necessary to equip Uninterrupted Power Supply (UPS) to the
workstation and ensure the good cable connection. Sudden
power-off may damage the file system, or even cause the failure of
system reboot.
Start the workstation, and check whether the following parts
work:
z
Keyboard
2-1
Installation Manual
z
Mouse
CD drive
Monitor

If no built-in CD drive is available or it does not work, prepare an

external CD drive with Small Computer Systems Interface (SCSI)
and proper interface cables.
II. Check software

Make preparations according to different installation modes.
See Table 2-1.
Table 2-1 Software checklist
Installation Mode
Software
Solaris 8 for SPARC Install Disk
Standalone
Sybase12 Install Disk and License

iManager N2000 Install Disk and License
Client
Solaris 8 for SPARC Install Disk

iManager N2000 Install Disk
iManager N2000 software can only be installed locally instead

of remotely.
For license files in the checklist, see About License set out in
Section 1.3 of Chapter 1 System Overview.
2-2
Installation Manual

III. Collect information

Before the installation, collect the following information.
z
IP address and mask of the workstation
Disk partitioning plan. For details, refer to Appendix.
Workstation name should be a unique alphanumerical

string including more than two letters, digits or hyphens.
The name must begin with a letter, and no space should be
contained.
Naming rules:
In order to differentiate servers and clients, it is recommended
to name them as follows.
1)
Single server: N2000Server
2)
Multiple clients and servers
Server: N2000Server-X
Client: N2000Client-X
Here, X represents the serial number.
2.3 Standalone Installation Mode

Main steps for standalone installation mode:
z
Installing operating system
Installing operating system patch
Installing database system
Installing NMS server and client
2-3
Installation Manual

2.3.1 Installing Operating System

Before installation, you can query the Solaris version through
showrev command. The version format is like SunOS 5.8 Generic
108528-18 November 2002. It is recommended to install Solaris 8
(2002/2) or later. Problems may occur when running NMS on earlier
versions of Solaris.
This section applies to the installation of Solaris 8 (2002/2). For
the installation of the other versions, please visit http://docs.sun.com.
I. Operation procedures
1)
Power on the Sun workstation, and insert the installation

disk of the Solaris 8 labeled 1 OF 2 to the CD drive.
2)
When the user login interface appears, press <Stop+A>

(that is, hold on <Stop>, which is on the upper left of the
Sun keyboard, and press <A> at the same time.).
3)
When OK is prompted, enter boot cdrom, press <Enter>,

and then the system starts installing the Solaris 8 operating
system from the CD drive.
The system will be restarted. In 5 minutes, the system will

prompt you to select the language for installation.
2-4
Installation Manual

Note:
When the external CD is adopted:
1) Input the command at the OK prompt:
probe-scsi-all
If /pci@8700000/scsi@61 is displayed, it means that the external CD has been
detected.
2) Input the command to search for other aliases of the CD:
devalias
If the other alias of the CD is /pci@8700000/scsi@6/disk@60:f, then
/pci@8700000/scsi@61/disk@60:f points to the external CD.
3) Input the command:
boot /pci@8700000/scsi@61/disk@60:f
The system will be restarted.
4)
Select the language for the installation.
[!]
Input the number representing English: 0.
Note:
Some important steps are marked with [!]. Such steps are significant in correct
installation, so do be sure the proper operation.
5)
Select the locale for English: 0.
2-5
[!]
Installation Manual

The system is running. The following prompts will appear in the

Solaris Install Console:
Starting OpenWindows
The system is coming up. Please wait.
In.rdisc: No interface up
6)
The Solaris Installer dialog box appears. The system

prompts:
The installation of Solaris is divided into several

sections.
Related
installation
information
will
be
provided for you at each stage. At the end of each section,

you can change your selections before continuing.
Click <Continue>.
7)
The Identify This System dialog box appears. The system

prompts:
On the next screens, you must identify the system as

networked or non-networked, and set the default time zone
and data/time. If this system is networked, the software
will try to find the information if needs to identify the
system; you will be prompted to supply any information it
cannot find.
Click <Continue>.
8)
The Network Connectivity dialog box appears.
Select Networked: [Yes]. Click <Continue>.

9)
The DHCP dialog box appears.
Select Use DHCP: [No]. Click <Continue>. To ensure the

stability and security of system running, do not use DHCP.
2-6
Installation Manual

10) The Main Network Interface dialog box appears. Click

<Continue>.
11) The Host Name dialog box appears.
[!]
Enter the host name, like N2000Server.Click <Continue>.

12) The IP Address dialog box appears.
[!]
Input the IP address set to the workstation, e.g. 10.11.106.46.

Click <Continue>.
13) The Subnets dialog box appears.
System part of a subnet: [Yes]. Click <Continue>.
14) The Netmask dialog box appears.
Netmask: e.g. 255.255.255.248. Click <Continue>.
15) The IPv6 dialog box appears.
Enable IPv6: [No]. Click <Continue>.
16) The Confirm Information dialog box appears.
Click <Continue> if there is nothing wrong.
17) The Configure Security Policy dialog box appears.
Configure Kerberos security: [No]. Click <Continue>.
19) The Name Service dialog box appears.
Name service: [None]. Click <Continue>.
21) The Time Zone dialog box appears.
2-7
[!]
Installation Manual

Specify time zone by: [Offset from GMT]. Click <Set>.

22) The Offset from GMT dialog box appears.
To specify the offset from Greenwich Mean Time, move the
slider. For example, for GMT+8, move the slider to 8. Click
<Continue>.
23) The Date and Time dialog box appears.
[!]
Set an accurate time, and click <Continue>.
Caution:
The sytem time should be accurate and in the specified format. While the NMS
server is running, the system time must not be modified.

Click <Continue>. The Solaris Install Console displays:
System identification is completed.
25) The Solaris Interactive Installation dialog box appears.

Click <Initial>.
2-8
Installation Manual

Note:
With a new computer on which no operating system is installed, no <Initial> button is
available, you need click <Continue> to proceed.
26) The Solaris Interactive Installation dialog box appears.

Click <Continue>.
27) The Select Geographic Regions dialog box appears.
Select the region. Click <Continue>.
28) The Select Software dialog box appears.
29) Select software group Entire Distribution plus OEM
support. Click <Continue>.
[!]
30) The Select Disks dialog box appears.

Move c0t0d0(boot disk) in Selected. If there are two hard
disks, move the second hard disk in Selected. Click <Continue>.
31) The Preserve Data? dialog box appears.
Click <Continue>.
32) The Automatically Layout File Systems? dialog box
appears.
Click <Manual Layout>.
33) The File System and Disk Layout dialog box appears.
Click <Customize>.
34) The Customize Disks dialog box appears.
2-9
[!]
Installation Manual

Specify the sizes of different partitions. Please refer to the

partition rules in the Appendix. Click <OK>.
Caution:
No matter which partitioning method is adopted, make sure that there is enough
space for primary partition. Insufficient disk space may result in unexpected
problems, such as system boot failure. Delete the useless files in time, when
copying or backing up the files.
35) Return to the File System and Disk Layout dialog box:
Click <Continue>.
36) The Mount Remote File Systems? dialog box appears.
Click <Continue>.
37) The Profile dialog box appears.
Click <Begin Installation>.
38) The prompt dialog box appears.
Click <Auto Reboot>.
39) The system begins installation, and the Installing Solaris
Software-Progress dialog box appears to indicate the
installation process.
The installation may take 25 minutes.
2-10
Installation Manual

40) After that, the system will be restarted. It prompts to set the
password for the super user (root). Set and remember it. It
will be used afterwards.
41) The Specify Media dialog box appears.
Select the CD and Click <Next>.
42) The Insert CD dialog box appears, and the CD is ejected.
Insert the CD labeled 2 OF 2 into the CD drive, and then click
<OK>.
The installation may take 20 minutes.
43) After the installation is finished, the Installation Summary
dialog box appears.
Click <Next>.
44) The original CD is automatically ejected, and the Reboot
dialog box appears. Click <Reboot Now>.
45) After the system reboot, the operating system log-in
interface appears.
Enter the user name as root and the password. Common
Desktop Environment (CDE) is entered, indicating the installation of
Solaris 8 operating system is completed.
2.3.2 Installing Operating System Patch

After installing Solaris 8, install the patch before other software
is installed.
2-11
Installation Manual

1)
After logging in as the "root" user, first copy the

"8_Recommended.zip" file on the patch CD to "/tmp"
directory and then unzip it. Enter the directory of the patch
file, and execute the following commands:
#cp 8_Recommended.zip /tmp

#cd /tmp
#unzip 8_Recommended.zip
2)
The directory 8_Recommended is created after the

decompression. Enter this directory and install the patch
using the following commands:
#cd 8_Recommended
#./install_cluster
-nosave
The following prompt appears:

Are you ready to continue with install? [y/n]: Enter y.
3)
Some information about installation failure might appear

during the installation of patch, but it does not matter.
Installation of the patch may take a rather long time, so
please wait patiently.
4)
After the installation, restart the operating system to make

patch effective.
II. Set NMS workstation route

After the OS installation, route and gateway should be set for
NMS workstation to realize TCP/IP communication with the
managed devices. According to the NMS security strategy, the
2-12
Installation Manual

default gateway should not be used. There are two ways to set
routes between device and workstation.
Method 1:
Log in as root. Add a line in the /etc/rc3 file for every
destination network segment.
route add [Destination Segment Address] [Gateway IP]
[Destination Mask]
For example:
#vi /etc/rc3
Add a line:
route add 61.128.78.0
61.128.89.93
255.255.255.0
It represents that the devices with IP address between

61.128.78.0 and 61.128.89.93 can access the workstation. Be sure
to press <Enter> after inputting the line. Otherwise, it may be mixed
with some other characters automatically added in the case of
workstation power failure or abnormal shutdown.
Method 2:
Log in as root. Create a file with a name beginning with S
under /etc/rc3.d/. Add a line in this file for every destination network
segment.
route add [Destination Segment Address] [Gateway IP]
[Destination Mask]
For example:
2-13
Installation Manual

#cd /etc/rc3.d
#vi Srouter
Add a line:
route add 61.128.78.0
61.128.89.93
255.255.255.0
It represents that the devices with IP address between

61.128.78.0 and 61.128.89.93 can access the workstation.
2.3.3 Installing Sybase Database System

This section applies to the installation of Sybase 12.0, which is
most often used. For installation of Sybase database of other
versions, visit http://www.sybase.com.
Besides, sufficient space should be ensured for installing
database server. For space requirement, refer to Disk Partitioning
Rules (for Solaris) in Appendix.
1)
Set shared memory
Start the workstation and log in as the root user (super user).
Compute the shared memory according to the actual physical
capacity of the memory of the workstation, and add the shared
memory to the system file under the etc directory, which is under
the root directory.
Use the following formula to compute the shared memory:
2-14
Installation Manual

Y=X*1024*1000, where X is the capacity of the actual physical

memory, with MB as the unit. To view the actual capacity of the
memory, use the command prtconf | grep Memory.
If the actual physical memory is 1024MB, use the following
formula to compute the shared memory:
Y=1024*1024*1000=1048576000
Edit the system file under etc directory with the vi editor, by
using the following command.
#vi /etc/system
Add the following line to the file. Save and exit.

set shmsys:shminfo_shmmax=1048576000
Finally, restart the workstation by executing the following

commands:
# sync
[!]
# reboot
2)
Then log in as root. If the language is not English, set the

language variable LANG by executing the following
commands:
#LANG=C
#export
3)
[!]
LANG
Put the Sybase install disk in the CD drive. Enter the

/cdrom/cdrom0 directory, and start the installer by
executing the following commands:
# cd
/cdrom/cdrom0
# ./install
The initial installation interface appears, as shown in Figure 2-1.

2-15
Installation Manual

Figure 2-1 Initial installation interface

4)
The dialog box appears, as shown in Figure 2-2. Select the

installation type.
2-16
Installation Manual

Figure 2-2 Installation type dialog box

Click to select Customized Install, and click <Next>.
5)
The dialog box appears, as shown in Figure 2-3. Select the

installation directory.
Figure 2-3 Installation directory selection dialog box

2-17
Installation Manual

The installation directory is /opt/sybase, click <Next>.

6)
The dialog box appears, as shown in Figure 2-4.
Figure 2-4 Component selection dialog box

Click <Next>.
7)
2-18
Installation Manual

Figure 2-5 Summary dialog box

Click <Next>.
8)
Figure 2-6 Directory creation dialog box

2-19
Installation Manual

Click <Yes>.
9)
The installation process appears, as shown in Figure 2-7.
Figure 2-7 Installation progress dialog box

10) When the installation is completed, the dialog box appears,
as shown in Figure 2-8.
Figure 2-8 Sybase license management dialog box

Click <Yes>.
11) The dialog box appears, as shown in Figure 2-9.
2-20
Installation Manual

Figure 2-9 License information setting dialog box

Fill in license information, which is available in the license paper
document delivered with Sybase install disk. Click <Continue
Install>.
Figure 2-10 Sybase installer dialog box

Click <Yes>.
2-21
[!]
Installation Manual

Figure 2-11 ASE setup & configuration dialog box

A terminal window is opened. Create the directory data to
store database files by using the following commands:
#cd
/opt/sybase
#mkdir
data
Click <Configure a new server>.

2-22
[!]
Installation Manual

Figure 2-12 Srvbuild - select servers to build dialog box

For Server type, select Adaptive Server and Backup Server.
The input box behind Adaptive Server and Backup Server is
activated.
For Adaptive Server, enter N2000DBServer as the name of
Adaptive Server. Then other server names will be changed
accordingly. Click <OK>.
2-23
[!]
Installation Manual

Figure 2-13 Srvbuild - server attribute editor dialog box

In this dialog box, set attributes of the database as follows:
Master device path: /opt/sybase/data/master.dat.
Master device size (MB): 120.
Master database size (MB): 100.
Sybsystemprocs
device
/opt/sybase/data/systemprocs.dat.
2-24
path:
Installation Manual

Sybsystemprocs device size (MB): 100.

Sybsystemprocs database size (MB): 100.
For other parameters, accept the default value.
Click <OK>.
Note:
Assign the space according to the actual need. The above configuration is
suggested here for reference. Please refer to the space configuration rules in the
Appendix.
2-25
Installation Manual

Figure 2-14 Srvbuild - server attribute editor dialog box

Click <Build Servers!>.
17) Next comes the building of the database system. The
dialog box appears, as shown in Figure 2-15.
2-26
Installation Manual

Figure 2-15 Srvbuild status output dialog box

Figure 2-16 Srvbuild question dialog box
2-27
Installation Manual

Click <No>.
Figure 2-17 Srvbuild status output dialog box

Click <Exit>.
Figure 2-18 Srvbuild question dialog box

Click <Yes>.
2-28
Installation Manual

Figure 2-19 ASE Setup & Configuration dialog box

Click <Exit>.
Figure 2-20 Prompt dialog box

2-29
Installation Manual

Click <OK>.
Now, the installation of the database is completed.
23) Set environment variables of the database.
After installation of the Sybase database, the environment
parameters should be set through executing the following three files
in the terminal window:
#cd /opt/sybase
#. ./SYBASE.sh
#cd /opt/sybase/OCS-12_0
#. ./OCS-12_0.sh
#cd /opt/sybase/ASE-12_0
#. ./ASE-12_0.sh
Note:
After system restart, the above setting will become invalid and you should set the
environment parameters again. However, if you log in as n2kuser, which is
automatically created during NMS installation, the system will automatically
configure the environment parameters.
II. Check if the database server is properly installed

1)
Check if the database server and database backup server

are normally started.
Execute the following commands in the terminal window:

2-30
Installation Manual

#cd /opt/sybase/ASE-12_0/install
#./showserver
If the following information appears, it indicates that both the

database server and the database backup server are normally
started.
Figure 2-21 Database running checking dialog box
Note:
If the database server and database backup server are not running, start them
manually by executing the following commands:
#cd /opt/sybase/ASE-12_0/install
#./startserver -f ./RUN_N2000DBServer
#./startserver -f ./RUN_N2000DBServer_back
Where N2000DBServer and N2000DBServer_back are respectively the name of
the database server and of the database backup server.
2)
Check if the database can be connected to.
Execute the following commands in the terminal window:

#cd /opt/sybase/OCS-12_0/bin/
2-31
Installation Manual
#./isql
-SN2000DBServer -Usa

-P
By default, the sa password is null. If the password is not null,

enter the password like: isql
-SN2000DBServer -Usa
-Pxxx.
Herein, xxx represents the sa password.

If the following display appears,
1>
It indicates that the database server can be connected to and

the database server is successfully installed. Use the quit
command to exit the isql application.
III. Set the sa password

After the Sybase database is installed, the password of sa is
null by default. To ensure the security of the database, it is
recommended to set the password of sa immediately after the
installation. For example, to set the password of the sa of
N2000DBServer to n2000n2000, execute the following commands
in the terminal window:
#./isql SN2000DBServer -Usa -P
1>sp_password nulln2000n2000
2>go
The following display appears.

Setting password succeeded!
(return status=0)
1>
2-32
Installation Manual

Input quit to exit. The password of sa cannot be changed to

null after being set. In addition, the password of sa should be at
least six digits long.
Caution:
To ensure the security of the database, be sure to set the password of sa and
remember it. It will be used in the following step Set database information when
installing the NMS Server.
After the above setting, directly install NMS server and client,
but do not restart workstation. The database server is already started
and the environment parameters are already set.
If the workstation is restarted, set firstly database environment
parameters before installing NMS server and client. For details,
please refer to Set environment variables of the database and Check
if the database server is properly installed.
Caution:
To ensure the security of the database, after installation, unless otherwise specified,
no modification is allowed to the database. Otherwise, normal operation of the NMS
will be affected.
2-33
Installation Manual

2.3.4 Installing Sybase Database Patch

Dynamic database memory leakage may occur to Sybase11.9
and Sybase12.0. Therefore, after the database installation,
corresponding patch should be installed according to the database
version.
If the database version is Sybase11.9, Sybase11.9.2 patch
should be installed. The procedures are as follows:
I. Create a temporary directory, such as: /opt/patch

#cd /opt
#mkdir patch
II. Copy or ftp syb119_ebf10491_install.sh to /opt/patch.

syb119_ebf10491_install.sh should be executable.
Copy or ftp Sybase11_9_2_patch.tgz to /opt/patch.
III. To unpack the patch package under the directory

/opt/patch, execute the following commands:
#cd /opt/patch
#gzip -d Sybase11_9_2_patch.tgz
IV. To further unpack the package, enter the following

command:
#tar xvf Sybase11_9_2_patch.tar
An ebf10491 directory will be added to /opt/patch.

2-34
Installation Manual

V. Close sybase database process, and log in as a root

user. To set sybase environment varialbes, execute the
following command:
#./syb119_ebf10491_install.sh
Prompt: To avoid that the files under the sybase directory

belong to root group after loading the patch, execute the following
command after installing the patch:
#chown sybase $SYBASE
Some systems may have no Sybase user, whereto the system

will prompt: chown unknown user ID: sybase after the execution is
completed. This is normal.
If the database version is Sybase 12.0, Sybase12.0 patch
should be installed. The procedures are as follows:
VI. Create a temporary directory, such as: /opt/patch

#cd /opt
#mkdir patch
VII. Copy or ftp syb12_ebf11089_install.sh to /opt/patch.

Copy or ftp Sybase12_0_patch.tgz to /opt/patch.
VIII. To unpack the patch package under the directory

/opt/patch, execute the following commands:
#cd /opt/patch
#gzip -d
Sybase12_0_patch.tgz
2-35
Installation Manual

IX. To further unpack the package, enter the following

command:
#tar xvf Sybase12_0_patch.tar
X. Close sybase database process, and log in as a root

user. To set sybase environment varialbes, execute the
following command:
#./ syb12_ebf11089_install.sh
Prompt: To avoid that the files under the sybase directory

belong to root group after loading the patch, execute the following
command after installing the patch:
Execute the following command after installing the patch:
Some systems may have no sybase user, whereto the system

will prompt: chown unknown user ID: sybase after the execution is
2.3.5 Installing NMS Server

If an NMS has already been installed in the workstation, when
reinstalling, be sure that the original NMS server and the sysmoni
daemon stop running and the original database is not being used.
To determine whether the original NMS and the sysmoni
daemon stop running, you may:
2-36
Installation Manual

I. Start NMS server

Log in to the operating system as an n2kuser. Enter into the
public desktop environment, and the system will automatically start
the NMS server, which runs in the form of daemon process.
II. Start system monitoring terminal

Right
click
in
the
CDE
desktop,
and
select
[Applications/iManager N2000/N2000 SysMonitor] to pop up the

Login" dialog box. Enter the login password (N2000 by default), and
set the NMS server to be logged in to to enter into the system
monitoring terminal window, where you may perform maintenance to
the NMS server process, database, system resources, hard disk and
system version information.
III. Stop NMS server

Select [System/Stop Server] in the main menu, and the NMS
server process will stop in 30 seconds.
To determine whether the NMS database is used, log in to
Sybase as a sa user with the command isql.
#./isql -SN2000DBServer -Usa -P
This statement considers that the database sa password is

blank by default. If it has been set, you should enter this password,
such as isql -SN2000DBServer -Usa -Pxxx, where xxx indicates the
database sa password.
If the following information is displayed:
2-37
Installation Manual

1>
enter the following command:

1>sp_who
Run sp_who to check whether the NMS database is connected.

If yes, disconnect it. Otherwise, the installation may fail.
Before installation, set the system time of workstation
accurately and make sure that the Sybase database server is
running normally.
Besides, sufficient space should be ensured for installing NMS
server. For space requirement, refer to Disk Partitioning Rules (for
Solaris) in Appendix.
Note:
If the Standalone mode is selected, NMS client application will be also installed
with NMS server application.
IV. Operation procedures

1)
Log in as root user to CDE. Set the language to English".

Insert the install disk of iManager N2000 into the CD drive.
Enter the root directory of the CD and run the setup.sh file
by executing the following commands:
# cd
/cdrom/cdrom0
# ./setup.sh
2-38
Installation Manual

The initial installation interface appears, as shown in Figure

2-22.

2)
The dialog box appears, as shown in Figure 2-23. Confirm

the installation license.
2-39
Installation Manual

Figure 2-23 Software license file

Read the license agreement carefully and confirm the
agreement. Click I accept the terms of the license agreement. radio
button, and then click <Next>.
3)
The dialog box appears, as shown in Figure 2-24. Select

the installation directory.
2-40
Installation Manual


The
default installation directory
is
/opt/n2000.
Click
<Browse> to select any other directory. Then click <Next>.
Caution:
The installation directory is not allowed to contain blank or illegal characters such as
MBCS (Multi-byte Character Set).
2-41
Installation Manual
4)

[!]
Figure 2-25 Standalone installation mode selection dialog box

Select the "Standalone as the installation mode of the NMS
Server. Click <Next>.
5)
The license selection dialog box appears, as shown in

Figure 2-26.
2-42
Installation Manual

Figure 2-26 License file selection dialog box

Click <Browse> to select a normal license file, which should
have been purchased.
By default, a temporary license file is available. Click <Next>.
The prompt box appears, as shown in Figure 2-27.
2-43
Installation Manual

Figure 2-27 Temporary license prompt

Click <OK>.
6)
The dialog box similar to Figure 2-28 appears. Select the

functional components to be installed.
Figure 2-28 Functional components selection dialog box

2-44
[!]
Installation Manual

Check and select the desired functional components. The

component Element Management Essence is mandatory while
others are optional. After the selection, click <Next>.
Then the installer checks the component dependency. If the
checking fails, the failure results will pop up. Click <Back> to select
components again. If the checking is succeeded and the
components are already installed, then come to next step.
[!]
Note:
In actual installation, the functional components might be different from those as
shown in Figure 2-28.
7)
The database configuration dialog box appears, as shown

in Figure 2-29. Select different database according to
different database type.
[!]
2-45
Installation Manual

Figure 2-29 Database information setting dialog box

In this dialog box, input the NMS database user name and the
basic information of the database server, as shown below:
Sybase database
z
NMS Database User Name: The user name used to

connect the NMS with the database. It is N2000user by
default and allows no change.
NMS Database User Password: The password of the DB

NMS user. It should be at least 6 characters long.
Password Confirm: Re-enter the DB NMS password.
2-46
Installation Manual
z

Database sa Password: The password of the system

administrator of the database. It is set during the database
installation.
Database Server Name: The name of the NMS database

server. It is N2000DBServer by default. It should be
identical to the name of Adaptive Server, which is set
during the installation of Sybase database.
Database Type: Select Sybase.
MDP IP: The IP address of the NMS Server. It is

127.0.0.1 by default.
After the setting, click <Next>.

Then
the
installer
automatically
[!]
checks
the
system
configuration, including OS Version, Memory, Disk Free Space and

Database Version. If the checking fails, the failure results will pop up.
Change the configuration according to the current value and the
requirement. If the checking is succeeded, then come to next step.
Note:
To make sure the database server name, query the xxx.cfg file under the Sybase
installation directory. Herein, xxx represents the database server name. Or list the
database server names by executing the following command.
#ls ${SYBASE}/${SYBASE_ASE}/install | grep RUN | awk -F_ '{print $2}' | uniq
2-47
Installation Manual

Caution:
After setting the basic database information, click <Next>, the system will
automatically log in to the database server. If the login fails, check from the following
aspects:
1) Whether the database server runs normally. Please refer to Check if the
database server is properly installed.
2) Whether the database sa password is correct.
3) Whether the database server name is correct.
4) Whether the Sybase environment parameters are set correctly. Please refer to
Set environment variables of the database.
8)
The confirmation dialog box appears, as shown in Figure

2-30.
2-48
Installation Manual

Figure 2-30 Installation information confirmation dialog box

This dialog box shows the installation directory, the installed
functional components and the needed disk space. If there is no error,
click <Next> to start the installation. Otherwise click <Back> to return
to the corresponding steps to make selection again.
9)
The installation begins, and a progress bar appears, as

shown in Figure 2-31. It takes you about 10 minutes.
2-49
Installation Manual

Figure 2-31 Installation progress dialog box

10) Then the installation script is executed, and a process bar
appears, as shown in Figure 2-32. It takes you about 30
minutes.
2-50
Installation Manual

Figure 2-32 Script execution progress dialog box

After the installation script is executed, the interface appears, as
2-51
Installation Manual

Figure 2-33 Script execution completion dialog box

Click <Next>.
11) The interface appears, as shown in Figure 2-34. Set the
NMS security for root user.
2-52
Installation Manual

Figure 2-34 Installation parameter setting dialog box

Select the check box. Click <Next>.
[!]
Note:
To ensure the security of the NMS server, it is recommended to close some services
of operating system during the installation, such as telnet, ftp and so on. After the
installation, you can enable the services manually. Refer to 4.1.7 How to enable
FTP and 4.1.8 How to enable Telnet in Chapter 4 Frequently Asked Questions.
2-53
Installation Manual

12) The installation summary appears, as shown in Figure

2-35.
Figure 2-35 Installation summary

Click <Finish> to complete the installation.
The installer will automatically create shortcuts for starting
system monitor client and NMS client on the CDE desktop. And a
default user name n2kuser is also created but without password.
At the first login as n2kuser, the system will prompt you to set a
password. Click <OK>. An input box will appear. Input a password
and confirm it. Then restart the workstation, log in as n2kuser again.
The system will ask you for a password.
2-54
Installation Manual

2.3.6 Starting NMS Server and Client

If NMS server and client can be normally started, it indicates
that they are properly installed.
I. Start NMS server

After login as n2kuser, the system will automatically start the
NMS Server as the daemon. View the status of daemons through the
system monitor and then perform the corresponding maintenance
operations.
Note:
Start NMS server as follows:
1) Switch to the user sa.
2) Run the .profile file under the directory n2kuser by executing the following
command:
#. ./.profile
3) Start the system monitor by executing the following command:
#cd /opt/n2000/server/bin
#./EmfSysMoniDm
The NMS server will be automatically started.
2-55
Installation Manual

II. Start system monitor

Right click on the CDE, and select [Applications/iManager
N2000/N2000 SysMonitor] to pop up the Login dialog box, as
Figure 2-36 User login

Enter the password (N2000 by default). Then the system
monitor window appears, as shown in Figure 2-37:
2-56
Installation Manual

Figure 2-37 Initial interface of system monitor

This window can be used to maintain daemons, databases,
system resources, hard disks, and system version information.
In the Login dialog box, click <> to pop up the Setting"
dialog box, as shown in Figure 2-38. You can log in to different
servers by adding, modifying and deleting the server information.
The IP address is expressed in dotted decimal notation system, and
the port number defaults to 9800.
2-57
Installation Manual

Figure 2-38 Server setting
III. Start NMS client

N2000/N2000 Client], or click the icon
on the desktop. Then
Login dialog box pops up.

When the system is installed, only the default user admin is
provided, with the default password being N2000. The user admin
is a superuser, who has all operation and management authorities.
At that time, the Access Control List (ACL) is empty. The user can log
in to it only through the server. After the password is entered in the
"Login dialog box, the topology main window of the NMS Client is
entered, as shown in Figure 2-39.
2-58
Installation Manual

Figure 2-39 Initial interface of NMS Client
2.4 Client Installation Mode

Steps for client installation mode:
z
Installing Operating System
Installing NMS Client

Before the installation of NMS Client, make sure that the Solaris
OS has been properly installed. The installation method is
2-59
Installation Manual

completely the same as in the standalone installation mode. For

details, see 2.3.1 Installing Operating System.
2.4.2 Installing NMS Client

The installation of NMS client is similar to the installation of NMS
server. Please refer to 2.3.5 Installing NMS Server.
1)
Start the installer.
2)
Confirm the license file.
3)
Select the installation directory.
4)
Select the Client installation mode to install the NMS

Client.
[!]
5)
Select the functional components.
6)
Confirm the functional components.
7)
The installation begins, and a progress indicator box

shows the installation progress.
8)
Execute the installation script.
9)
The installation summary appears. Click <Finish> to

complete the installation. The installer will automatically
create the shortcut for starting the NMS Client on the CDE
desktop.
II. Check if the NMS client is properly installed

After the NMS client is installed, you can start it to check if the
NMS client application is properly installed. For details, please see
the section 2.3.6 III. Start NMS client.
2-60
Installation Manual

N2000 on Solaris + Oracle
Chapter 3 Installing iManager N2000

on Solaris + Oracle
3.1 Introduction
Solaris operating system + Oracle database, including standalone
installation mode and client installation mode, as well as installation
of Solaris operating system and Oracle.

Before workstation power-on, find the 110V/220V AC switch
attached to the power module. Adjust the switch according to the
local AC voltage. Otherwise, the power module may be burned!
It is necessary to equip Uninterrupted Power Supply (UPS) to the
workstation and ensure the good cable connection. Sudden
power-off may damage the file system, or even cause the failure of
system reboot.
I. Check hardware
Start the workstation, and check whether the following parts
work:
z
Keyboard
Mouse
3-1
Installation Manual
z
CD drive
Monitor

Note:
If no built-in CD drive is available or it does not work, prepare an external CD drive
with Small Computer Systems Interface (SCSI) and proper interface cables.
II. Check software

Make preparations according to different installation modes.
See Table 3-1 for details.
Installation Mode
Software
Solaris 8 for SPARC Install Disk and CD-KEY
Standalone
Oracle 8.1.7.0.0 (or later) Install Disk and License

Client
Solaris 8 for SPARC Install Disk and CD-KEY

Note:
iManager N2000 software can only be installed locally instead of remotely.
3-2
Installation Manual

III. Collect information

Before the installation, collect the following information.
z
IP address and mask of the workstation.
Disk partitioning plan. For details, refer to Appendix.
Workstation name should be a unique alphanumerical

string including more than two letters, digits or hyphens.
The name must begin with a letter, and no space should be
contained.
Naming rules:
In order to differentiate servers and clients, the following naming
rules are recommended.
1)
2)
Multiple clients and servers
z

Main steps for standalone installation mode:
z
Installing operating system patch
3-3
Installation Manual


Refer to Section 2.3.1.

Refer to Section 2.3.2.
3.3.3 Installing Oracle Database System
Note:
This section applies to the installation of Oracle 8.1.7.0.0, which is most often used.
For installation of Oracle database of other versions, visit http://www.oracle.com.
When iManager N2000 is installed on Sun workstation, either the Sybase or the
Oracle database can be used.
Before installing Oracle database, make sure that:
1) The operating system has been properly installed and "Entire Solaris Software
Group plus OEM" has been selected during the installation of Solaris8.
2) Sufficient hard disk space should be ensured for installing database server (the
available disk space of the partition of /opt/oracle should be more than 1GB, that of
the data files should be more than 2GB, and that of /tmp should be more than
300MB).
1)
Start the workstation and log in as a root user (super user).
2)
Use the admintool to create the user group oinstall.
3-4
Installation Manual

Use the admintool to create a user oracle. Set its user group as
oinstall, the $HOME directory as /export/home/oracle, and shell as
ksh.
Use the following commands to create the /opt/oracle directory.
Set its group as oinstall, and owner as oracle.
# mkdir /opt/oracle
# chgrp oinstall /opt/oracle
# chown oracle /opt/oracle
# mkdir /opt/oracle/data
# chgrp oinstall /opt/oracle/data
# chown oracle /opt/oracle/data
3)
Modify and save /export/home/oracle/.profile of the oracle

user according to the following requirements.
ORACLE_BASE=/opt/oracle
export ORACLE_BASE
ORACLE_HOME=$ORACLE_BASE/home
export ORACLE_HOME
NLS_LANG=American_america.us7ascii
export NLS_LANG
ORA_NLS33=$ORACLE_HOME/ocommon/nls/admin/data
export ORA_NLS33
PATH=$PATH:$ORACLE_HOME/bin
export PATH
3-5
Installation Manual

LD_LIBRARY_PATH=$LD_LIBRARY_PATH:$ORACLE_HOM
E/lib
export LD_LIBRARY_PATH
ORACLE_SID=N2000
export ORACLE_SID
Caution:
If Oracle has been installed previously, delete contents under /var/opt/oracle and
$ORACLE_BASE. Do not delete the $ORACLE_BASE directory itself.
4)
Use vi command to add the following to the system file vi

/etc/system:
set shmsys:shminfo_shmmax=4294967295
set shmsys:shminfo_shmmin=1
set shmsys:shminfo_shmmni=100
set shmsys:shminfo_shmseg=10
set semsys:seminfo_semmni=100
set semsys:seminfo_semmsl=100
set semsys:seminfo_semmns=1000
3-6
Installation Manual

set semsys:seminfo_semopm=100
set semsys:seminfo_semvmx=32767
5)
Restart the workstation:
# sync
# reboot
6)
Log in as the oracle user and enter the oracle install

package directory. Execute the following command to run
runInstaller.
#./runInstaller
Note:
If a prompt as shown in Figure 3-1 appears, delete the /tmp/OraInstall directory and
restart runInstaller.
Figure 3-1 Error dialog box

7)
Enter the installation interface, as shown in Figure 3-2.

3-7
Installation Manual

Figure 3-2 Welcome interface

Click <Next>.
8)
A "Set ORACLE_HOME path interface appears, as shown

in Figure 3-3.
3-8
Installation Manual

Figure 3-3 Installation directory dialog box

As the path displayed on the interface has been set in the
previous .profile file, no modification is needed here. Click <Next>.
9)
The system starts to load product information, as shown in

Figure 3-4.
3-9
Installation Manual

Figure 3-4 Product information loading dialog box

10) An interface appears, as shown in Figure 3-5. Set the user
group name for oracle maintenance.
3-10
Installation Manual

Figure 3-5 Unix group name setting dialog box

Enter oinstall, and click <Next>.
11) A dialog box appears, as shown in Figure 3-6.
3-11
Installation Manual

Figure 3-6 Prompt dialog box

Switch to the root user in another terminal window according to
the prompt and execute the /opt/oracle/home/orainstRoot.sh script.
Return to Figure 3-6 and click <Retry>.
12) An interface appears, as shown in Figure 3-7.
3-12
Installation Manual

Figure 3-7 Installation product selection dialog box

Select the product to be installed (you can keep the default
setting), and click <Next>.
13) The Installation Type interface appears, as shown in
Figure 3-8.
3-13
Installation Manual

Figure 3-8 Installation type selection dialog box

Select Custom, and click <Next>.
14) The Available Product Components interface appears, as
3-14
Installation Manual

Figure 3-9 Product components selection dialog box

Clear the following options:
z
Oracle Http Server
Oracle Product Options
Oracle Java Products
Oracle Enterprise Manager Products
Development Tools
Oracle8i for Unix Documentation
After that, click <Next>.

3-15
Installation Manual

Figure 3-10 Component locations dialog box

Keep the default setting and click <Next>
16) An interface appears, as shown in Figure 3-11. Enter the
database administrator group and database operator
group names.
3-16
Installation Manual

Figure 3-11 Privileged operating system group setting dialog box

Enter oinstall in both fields, and click <Next>.
17) The Create Database interface appears, as shown in
Figure 3-12.
3-17
Installation Manual

Figure 3-12 Database creation dialog box

Keep the default setting and click <Next>.
3-18
Installation Manual

Figure 3-13 Database identification dialog box

Enter "N2000" in both Global Database Name and SID fields,
keeping consistent with ORACLE_SID in the .profile file. Click
<Next>.
3-19
Installation Manual

Figure 3-14 Database File Location dialog box

Enter the database directory as "/opt/oracle", and click <Next>.
Caution:
The database directory should be created separately instead of under the HOME
directory of oracle user (/export/home/oracle).
Be sure that the database directory group is oinstall, and owner is oracle.
3-20
Installation Manual

20) At last, the Summary interface appears, as shown in Figure

3-15. Click <Install>.
Figure 3-15 Summary dialog box

21) If all proceed well, the Install interface appears, as shown
in Figure 3-16.
3-21
Installation Manual

Figure 3-16 Installationl prompt box

A dialog box pops up during the installation, as shown in Figure
3-17. Do not click <OK>.
3-22
Installation Manual

Figure 3-17 Setup privilege prompt box

According to the prompt, execute the /opt/oracle/home/root.sh
script file as the root user from another terminal window. The
following prompts appear:
Enter the full pathname of the local bin directory:
[/usr/local/bin]:
Enter /usr/bin and press <Enter>. Switch back to the Install

interface as shown in Figure 3-17, and click <OK>.
22) Configure Net8, as shown in Figure 3-18.
3-23
Installation Manual

Figure 3-18 Configuration tools dialog box

Once the above window appears, another window pops up
immediately, as shown in Figure 3-19.
3-24
Installation Manual

Figure 3-19 Welcome dialog box

Click <Next>. A dialog box appears, as shown in Figure 3-20.
3-25
Installation Manual

Figure 3-20 Net8 directory service access dialog box

Select No, and click <Next>. A dialog box appears, as shown
in Figure 3-21.
3-26
Installation Manual

Figure 3-21 Net8 listener name configuration dialog box

Keep the default setting and click <Next>. A dialog box appears,
3-27
Installation Manual

Figure 3-22 Protocol selection dialog box

Select the installed TCP in the above options and click <Next>.
An interface appears, as shown in Figure 3-23.
3-28
Installation Manual

Figure 3-23 TCP/IP dialog box

Keep the default setting and click <Next>. An interface appears,
3-29
Installation Manual

Figure 3-24 Listener configuration dialog box

Keep the default setting and click <Next>. An interface appears,
3-30
Installation Manual

Figure 3-25 Listener configuration completion dialog box

Click <Next>. An interface appears, as shown in Figure 3-26.
3-31
Installation Manual

Figure 3-26 Naming method configuration dialog box

Keep the default setting and click <Next>. A Configuration
Completion dialog box appears. Click <Finish>.
3-32
Installation Manual

Figure 3-27 Net8 configuration completion dialog box

23) A Create Database dialog box appears, as shown in Figure
3-28.
3-33
Installation Manual

Figure 3-28 Application type dialog box

Select Online Transaction Processing (OLTP), and click
<Next>. A dialog box appears, as shown in Figure 3-29.
3-34
Installation Manual

Figure 3-29 Number of concurrently connected users setting dialog box

Enter 300, and click <Next>. A dialog box appears, as shown
in Figure 3-30.
3-35
Installation Manual

Figure 3-30 Database default operation mode selection dialog box

Select Dedicated Server Mode, and click <Next>. A dialog box
appears, as shown in Figure 3-31.
3-36
Installation Manual

Figure 3-31 Database configuration options dialog box

Clear all components, and click <Next>. A dialog box appears,
3-37
Installation Manual

Figure 3-32 Recheck database information dialog box

Click <Change Character Set>, and set the character set
consistent with that in environment variable $NLS_LANG of the
oracle user.
3-38
Installation Manual

Figure 3-33 Control file parameters recheck dialog box

Keep the default setting and then click <Next>. A dialog box
3-39
Installation Manual

Figure 3-34 Tools table space information recheck dialog box

In the Tools tab, modify the size of tools to be 32MB.
In the Rollback tab, modify RBS (Roll Back Segment) to be
100MB, as shown in Figure 3-35.
3-40
Installation Manual

Figure 3-35 Rollback table space information recheck dialog box

In the Temporary tab, set temp as 256MB, as shown in Figure
3-36.
3-41
Installation Manual

Figure 3-36 Temporary tablespace information recheck dialog box

Click <Next>, and modify the log file to be 32MB (32000KB), as
3-42
Installation Manual

Figure 3-37 Log file parameters recheck dialog box

3-43
Installation Manual

Figure 3-38 Log parameter information review dialog box

Keep the default setting, that is, not enable archiving log, and
then click <Next>, a dialog box appear as shown in Figure 3-39.
3-44
Installation Manual

Figure 3-39 SGA parameters recheck dialog box

Set Shared Pool Size (Bytes) as 125893600 and then click
<Next>. A dialog box appears, as shown in Figure 3-40.
3-45
Installation Manual

Figure 3-40 User debugging directory path recheck dialog box

3-46
Installation Manual

Figure 3-41 Database creating or information saving options dialog box

Click <Finish>. A confirmation dialog box pops up. Click <Yes>
to create the database, as shown in Figure 3-42.
3-47
Installation Manual

Figure 3-42 Database creation process

Upon completion, a dialog box pops up, as shown in Figure
3-43.
3-48
Installation Manual

Figure 3-43 Database creation summary

Click <OK>. An interface appears, as shown in Figure 3-44.
3-49
Installation Manual

Figure 3-44 Installation completion prompt box

Click <Exit>. A confirmation dialog box pops up. Click <Yes> to
exit the installation and complete the database creation.
24) Execute the following command to start Oracle listening
program:
$ $ORACLE_HOME/bin/lsnrctl start
Now, Oracle database is installed.
3-50
Installation Manual


If an NMS has already been installed in the workstation, when
reinstalling, be sure that the original NMS server and the sysmoni
daemon stop running and the original database is not being used.
To determine whether the original NMS and the sysmoni
daemon stop running, do the following:
I. Start NMS server

Log in to the operating system as the n2kuser and enter the
common desktop environment. The system will automatically start
the NMS server, which runs in the form of daemon process.
II. Start system monitoring terminal

Right
click
in
the
CDE
desktop,
and
select
[Application/iManager N2000/N2000 SysMonitor] to pop up the user

login dialog box. Enter the login password (N2000 by default), set the
NMS server to be logged in, then enter the system monitoring
terminal window, where you may maintain the NMS server process,
database, system resources, hard disk and system version
information.
III. Stop NMS server

Select [System/Stop Server] from the main menu, and the NMS
server process will stop in 30 seconds.
To determine whether the NMS database is used:
3-51
Installation Manual
1)

Log in to the Oracle database as the administrator:
sqlplus system/manager@N2000
2)
Query the user which is connected to the database and the

name of the PC initiating the connection.
>select username,machine from v$session
Check whether there exists any user named "XXXXDBUSER".

If yes, it indicates that an NMS database user has logged in. Before
installation, disconnect the user.
Caution:
If the Standalone mode is selected, NMS client application will also be installed
with NMS server application.
Before installation, set the system time of workstation accurately, which is vital to
the stability of iManager N2000. Modifying the system time is prohibited while
iManager N2000 is running. If it is a must, exit iManager N2000 first, and then restart
it after modification.
Besides, make sure that the Oracle database server is running normally, otherwise,
the installation may fail.
IV. Operation procedures

1)
You can operate in two modes:
Log in as an oracle user, then use su to switch to the root

user. Otherwise, the system may exist due to Oracle
3-52
Installation Manual

environment parameters not starting or insufficient

privilege.
z
Switch to root user from other users, and then run .profile
of the oracle user. Insert iManager N2000 install disk into
the CD drive. Enter the root directory of the CD and run the
setup.sh file by executing the following commands:
# cd
/cdrom/cdrom0
# ./setup.sh
The initial installation interface appears, as shown in Figure

3-45.

2)
The dialog box appears, as shown in Figure 3-46. Confirm

the installation license.
3-53
Installation Manual

Figure 3-46 Software license file

3)
Read the license agreement carefully and confirm the

agreement. Click the I accept the terms of the license
agreement. radio button, and then click <Next>.
4)
The dialog box appears, as shown in Figure 3-47. In the

dialog box, select the installation directory.
3-54
Installation Manual


The default installation directory is /opt/n2000. You can click
<Browse> to specify any other directory. Then click <Next>.
Caution:
The installation directory is not allowed to contain blank or illegal characters,
otherwise, the installation may fail.
3-55
Installation Manual
5)


the setup type.
Figure 3-48 Standalone installation mode selection dialog box

6)
Select the "Standalone as the installation mode of the

NMS Server. Click <Next>.
7)
[!]

the license file.
3-56
Installation Manual

Figure 3-49 License file selection dialog box

8)
Click <Browse> to select a normal license file, which

should have been purchased. By default, a temporary
license file is available. Click <Next>. The prompt box

3-57
Installation Manual
9)

Click <OK>.
10) The dialog box similar to Figure 3-51 appears. Select the
functional component to be installed.
Figure 3-51 Functional components selection dialog box

11) Select the desired functional components. The component
Element Management Essence is mandatory while
others are optional. After the selection, click <Next>.
12) Then the installer checks the component dependency. If
the checking fails, the failure information interface appears.
Click <Back> to select components again. If the checking
succeeds, that is, the components are already installed,
then come to next step.
3-58
[!]
Installation Manual

Note:
In actual installation, the user should select the components according to the actual
situation, so the functional components shown might be different from those as
13) The dialog box appears, as shown in Figure 3-52. Select

different databases according to different database types,
and set basic information of the database.
Figure 3-52 Database information setting dialog box
3-59
Installation Manual

z
NMS Database User Name: Invalid interface setting. Each

table space corresponds to a user name, with the naming
rule as table space name + USER;
NMS Database User Password: Set by the user;
Password Confirm: Re-enter the DB NMS password;
Oracle Database superuser Password: system user

password.
Note:
You can set the NMS Database User Password flexibly according to the actual
requirements. Re-enter the password in the Password Confirm and remember it.
In Oracle database, each table space corresponds to a user name, and the user
password is the unified interface input password.

server. It is N2000 by default. It should be identical with
the database instance name, which is set during the
installation of Oracle database;
Database Type: Select Oracle;
MDP IP: The IP address of the NMS Server. It is

127.0.0.1 by default.
3-60
[!]
Installation Manual
Then
the
installer

automatically
checks
the
system
configuration, including OS version, memory, disk free space and

database version. If the checking fails, the failure results will pop up.
Change the configuration according to the current value and the
maximum requirement. If the checking is succeeded, then come to
step 14.
Caution:
After you setting the basic database information and then clicking <Next>, the
system will automatically log in to the database server. If the login fails, check from
the following aspects:
1) Whether the database server runs normally.
2) Whether the database superuser password is correct.
3) Whether the database server name is correct.
14) The confirmation dialog box appears, as shown in Figure

3-53.
3-61
Installation Manual

Figure 3-53 Installation information confirmation dialog box

functional components and the needed disk space. If there is no error,
click <Next> to start the installation, otherwise click <Back> to return
15) The installation begins, and a progress bar appears, as
shown in Figure 3-54. It takes you about 10 minutes.
3-62
Installation Manual

Figure 3-54 Installation process

16) Then the installation script is executed, and a process bar
appears, as shown in Figure 3-55. It takes you about 30
minutes.
3-63
Installation Manual

Figure 3-55 Script execution progress

After the installation script is executed, the dialog box appears,
3-64
Installation Manual

Figure 3-56 Script execution completion dialog box

Click <Next>.
17) The dialog box appears, as shown in Figure 3-57. Set the
NMS security for root user.
3-65
Installation Manual

Figure 3-57 NMS installation setting dialog box

By default, related operating system services such as telnet, ftp
will be closed so as to ensure the security of NMS server operation.
Click <Next>.
[!]
3-66
Installation Manual

Note:
To ensure the security of the NMS server, it is recommended that you close services
of the operating system during the installation. After the installation, you can enable
the services manually. Refer to 4.1.7 How to enable FTP and 4.1.8 How to enable
Telnet in Chapter 4 Frequently Asked Questions.
18) The installation summary appears, as shown in Figure

3-58.
3-67
Installation Manual

19) Click <Finish> to complete the installation. The installer

has automatically created shortcuts for starting system
monitoring client and NMS client on the CDE desktop.
Restart the workstation, and log in to the operating system
as n2kuser (at the first login as n2kuser, select CDE as the
default desktop).
Note:
Herein, the installer automatically generates an OS user n2kuser without a
password. Log in to the operating system and set a password for this user.
At the first login as n2kuser, the system will prompt you to set a password. Click
<OK>. An input box will appear at the upper left corner. Input a password and
confirm it.
When running iManager N2000, the user is required to log in to the operating
system as n2kuser.

If NMS server and client can be normally started, it indicates
that they are properly installed.
I. Start NMS server

After login as n2kuser, the system will automatically start the
NMS Server as the daemon. View the status of daemons through the
3-68
Installation Manual

system monitor and then perform the corresponding maintenance

operations.
Note:
If the NMS server is not started, start it manually following the steps below:
1) Switch to the root user using the command "su";
2) Run the .profile file under the directory n2kuser by executing the following
command:
#. /n2kuser/.profile
3) Start the system monitor by executing the following commands:
#cd /opt/n2000/server/bin
#./EmfSysMoniDm
The NMS server will be automatically started.
II. Start system monitor client

N2000/N2000 SysMonitor] to pop up the Login dialog box, as
3-69
Installation Manual

Figure 3-59 User login

Enter the password (N2000 by default). Then the system
monitor window appears, as shown in Figure 3-60.
3-70
Installation Manual

Figure 3-60 System monitor client

This window can be used to maintain daemons, databases,
system resources, hard disks, and system version information.
In the Login dialog box, click <> to pop up the Setting
dialog box, as shown in Figure 3-61. You can log in to different
servers by adding, modifying and deleting the server information.
The IP address is expressed in dotted decimal notation system, and
the port number defaults to 9800.
3-71
Installation Manual

Figure 3-61 Sever setting

N2000/N2000 Client], or click the icon
on the desktop. Then
Login dialog box pops up.

When the system is installed, only the default user admin is
provided, with the default password being N2000. The user admin
is a super user, who has all operation and management authorities.
At that time, the Access Control List (ACL) is empty. The user can log
in to it only through the server. After the password is entered in the
"Login dialog box, the topology main window of the NMS Client is
entered, as shown in Figure 3-62.
3-72
Installation Manual
Figure 3-62 Initial interface of NMS client

See Section 2.4.
3-73

Installation Manual

N2000 on Windows
Chapter 4 Installing iManager N2000 on

Windows
4.1 Introduction
Windows and also that of SQL server.

Make preparations according to different installation modes. See
Table 4-1.
Installation Mode
Software
Windows 2000 Server Install Disk and CD-Key
Standalone
Microsoft SQL Server 2000 Install Disk and CD-Key

Client
Windows 2000 Professional Install Disk and CD-Key

4-1
Installation Manual

N2000 on Windows
Note:
The client can be installed either on Windows 2000 Professional or on Windows 2000
Server, and on Windows 2000 Professional by default.

Steps for the standalone installation mode:
z
Configuring database memory

Windows 2000 should be installed first before the installation of
the database and the NMS. Please refer to the installation guide
attached to the install disk of Windows 2000.
I. Installation requirements
z
The network attributes of the computer should be configured

in order to ensure the connectivity of the network.
It is recommended to set the display mode as 1024768

pixel, 256 colors or higher.
Set the system time of the NMS server accurately. A stable

system time is vital to iManager N2000, so any change to
the system time is prohibited during the operation of the
NMS.
4-2
Installation Manual
z

N2000 on Windows
It is recommended not to install the screen saver, nor use

the screen saver carried by Windows, as CPU occupation
will be high when the screen saver runs thus affecting
normal operation of the NMS.
Computer name should be a unique alphanumerical string

including more than two letters, digits or hyphens. The name
must begin with a letter, and no space should be contained.
Naming rules:
In order to differentiate servers and clients, it is recommended to
name them as follows.
1)
2)
Multiple clients and servers:

To ensure the stability and security of system running, please
install patch after the OS installation. The installation of Windows 2000
Service Pack 4 is described below.
1)
Start the patch installer, which will be automatically

unpacked and then the installation wizard appears. Click
<Next>.
4-3
Installation Manual
2)

N2000 on Windows
Read the license agreement carefully and confirm it by

selecting I agree. Click <Next>.
3)
Select
installation
options.
Save
Document
is
recommended for the convenience of future uninstall. Click

<Next>.
4)
Check the current configuration, backup the configuration

file, and then refresh the configuration status. Click <Next>.
5)
The patch installation is completed. Click <Finish>. Restart

computer to make the patch valid.
II. Check patch version

Right click My Computer on the desktop and select [Attribute] to
pop up System Properties dialog box. Click General tab. The patch
information is shown in the System list, for example, Service Pack
4, which indicates that the patch is installed successfully.
4.3.3 Install Database System

To install database server through Microsoft SQL Server 2000,
the Windows 2000 Server operating system should be installed firstly.
This section applies to the installation of the commonly used Microsoft
SQL Server 2000 database. For the installation of database of any
other version, please refer to the installation manual attached to the
respective install disk.
Besides, sufficient space should be ensured for installing
database server. For space requirement, refer to Disk Partitioning
Rules (for Windows) in Appendix.
4-4
Installation Manual

N2000 on Windows
1)
Log in to Windows 2000 Server as Administrator.
2)
Insert the SQL Server 2000 compact disk into the CD drive.
If the disk does not run automatically, double click
Autorun.exe in the root directory of the CD.
3)
Select SQL Server 2000 Components.
4)
Select Install Database Server, and setup prepares the

SQL Server Installation wizard. At the Welcome screen,
click <Next>.
5)
In the Computer Name dialog box, Local Computer is the

default option and the local computer name appears in the
edit box. Click<Next>.
Note:
Local installation is recommended. For remote installation, click Remote Computer.
Enter a computer name or click <Browse> to locate a remote computer. If a cluster is
detected, Virtual Server is the default option. Besides, the local computer should be
authorized.
6)
In the Installation Selection dialog box, click the Create a

new instance of SQL Server, or install Client Tools, and then
click <Next>.
7)
In the User Information dialog box, set the user name and
company name. Click <Next>.
4-5
Installation Manual
8)

N2000 on Windows
In the Software License Agreement dialog box, read the

license and confirm it. Click <Yes>.
9)
In the CD-Key dialog box, follow the direction on the

interface and key in the correct CD-key. Click <Next>.
10) In the Installation Definition dialog box, click Server and

Client Tools, and then click <Next>.
11) In the Instance Name dialog box, select the Default check
box, and then click <Next>.
[!]
Caution:
Be sure to select Default for instance name so as to select Multiprotocol when
installing network database. Otherwise, the NMS may not run normally.
Note:
Some important steps are marked with [!] for special notice.
12) In the Setup Type dialog box, click the default Typical,
and then click <Next>.
In the Service Accounts dialog box, specify the login accounts
to two Microsoft SQL Server service: SQL Server and SQL Server
agent.
4-6
Installation Manual

N2000 on Windows
Click the Customize the setting for each service option, and
then set the two services:
z
Set SQL Server, as shown in Figure 4-1:
Figure 4-1 Set SQL Server

Click the SQL Server option, and then click the Use the Local
System account option.
z
Set SQL Server agent, as shown in Figure 4-2:
4-7
Installation Manual

N2000 on Windows
Figure 4-2 Set SQL Server agent

Click the SQL Server Agent option, and then click the Use a
Domain User account. For the username and domain, accept the
default value. For example, the default user name is Administrator,
and the default computer name is N2000SERVER. Just enter the
password.
13) The Authentication Mode dialog box appears, as shown in
Figure 4-3.
[!]
4-8
Installation Manual

N2000 on Windows
Figure 4-3 Set authentication mode

Click the Mixed Mode (Windows Authentication and SQL Server
Authentication) option, add password for the sa login, and then click
<Next>.
Note:
For the sake of database security, make sure that the password of sa is not empty.
Be sure to remember it. It will be used in the following step Set database information
when installing the NMS.
4-9
Installation Manual

N2000 on Windows
14) In the Start Copying Files dialog box, click <Next>.

15) In the Choose Licensing Mode dialog box, make selections
according to the license agreement.
z
Every Client: Every client should have a license to access

SQL Server 2000 server. This mode suits the network where
a client may connect more than one server.
Processor License: Every processor needs a license in the

computer running SQL Server. There is no limitation for the
number of clients to access the server through Intranet or
Internet. This mode suits the customers accessing SQL
Server database through Internet or those with large amount
of clients.
Every Client is recommended. The number of authorized clients

can be set as 5. That is, no more than 5 clients can log in to SQL
server at the same time. The number can be modified through the
SQL server authorization tool in Control Panel. For detail, please
refer to the license agreement of SQL Server 2000.
After setting, click <Continue> to begin the installation.
16) In the Setup Complete dialog box, click Yes, I want to
restart my computer now and then click <Finish>. Then the
installation of the database is completed.
II. Check if the database is properly installed

After the database is installed, the database server needs to be
started manually. Then use the isql application to connect the
database server and to check if the database server is properly
installed.
4-10
Installation Manual
1)

N2000 on Windows
Select [Program/Microsoft SQL Server/Service Manager]

from the [Start] menu. Then the SQL Server Service
Manager dialog box pops up.
2)
Select the server name in the Server drop down list. It is

suggested to select the default computer name, such as
N2000SERVER.
3)
Select SQL Server in the Services drop down list.
4)
Check the Auto-start service when OS starts box so as to

automatically start the database server when the OS is
restarted.
5)
Click <Start/Continue> to start the database server, as

Figure 4-4 SQL Server service manager
4-11
Installation Manual

N2000 on Windows
Note:
In the step 4.3.1 I. 11), if you select Default for instance name, here you can specify
different server names to stop and start different default instances.
6)
Check if the database can be connected to.
In the command line window, enter "isql command and click

<Enter>. The command format is as follows:
isql.exe -Usa
-Pxxx
Herein, xxx is the password for the sa login.

If the following display appears,
1>
It indicates that the database server can be connected to and the

database server is successfully installed. Use the quit command to
exit the isql application.
4.3.4 Install Database Patch

To ensure the stability and security of system running, please
install SQL Server 2000 patch.
1)
If the SQL Server 2000 is not newly installed, backup

databases
first.
Select
[Program/Microsoft
SQL
Server/Enterprise Manager]. In the pop-up window, right
4-12
Installation Manual

N2000 on Windows
click the databases for backup, and select [All Tasks/Backup

Database].
2)
Unpack the patch under a certain directory.
3)
Enter the above directory. Double click setup.bat file to

start the install wizard.
4)
Please restart after installing SQL Server 2000 is prompted.

Confirm to restart. Click <Next>.
5)
In the Welcome dialog box, click <Next>.
6)
In the License Agreement dialog box, read the agreement

carefully and confirm it. Click <Yes>.
7)
In the Instance Name dialog box, keep the default setting.

Click <Next>.
8)
In the Connect to Server dialog box, select SQL Server Sa

Login Information (SQL Server Certification). Enter the sa
password. Click <Next>.
Note:
If the operating system and database have been pre-installed before delivery, see the
sa password set by default in Table 1-1 Default usernames and passwords for
iManager N2000 pre-installing the operating system and database in Chapter 1.
9)
In the compatibility list, select Upgrade Microsoft Search

and apply SQL Server 2000 SP3. Click <Continue>.
10) In the Error Report dialog box, do not select Automatically

send vital error to Microsoft. Click <OK>.
4-13
Installation Manual

N2000 on Windows
11) In the Copying Files dialog box, confirm to keep the setting.
Click <Next>.
12) The install process is started. A prompt will be given after it
is completed. Select to restart computer. Click <Finish>.
II. Check patch version

1)
Select [Program/Microsoft SQL Server/Enterprise Manager]

from the [Start] menu.
2)
In the pop-up SQL Server Enterprise Manager window,

select the computer from in SQL Server" group.
3)
Right click and select [Attribute] to pop up SQL Server

Properties dialog box.
4)
Click General tab. The patch information is shown in the

Product Version list, for example, 8.00.76 (SP03), which
indicates that the patch is installed successfully.
4.3.5 Configure Database Memory

In order to make good use of the NMS server memory, after
installing the database, set fix-sized database memory so as to ensure
the memory usage by SQL Server.
1)

from the [Start] menu. The SQL Server Enterprise
Manager dialog box pops up.
2)
In the SQL Server Group select the local computer. Right

click to select [Properties] to pop up the SQL Server
4-14
Installation Manual

N2000 on Windows
Properties dialog box. Click the Memory tab. as shown in

Figure 4-5:
Figure 4-5 SQL Server properties operation interface

Click the Use fixed-sized memory (MB) option, and drag the
slide bar to select a certain capacity. The values in Table 4-2 are
recommended. Click <OK> to complete the configuration of database
memory. Restart the database server to validate the configuration.
4-15
Installation Manual

N2000 on Windows
Table 4-2 Recommended memory allocation

Memory (MB)
256
512
1024
Fixed memory for database (MB)

40
80
160

Before installation, set the system time of workstation accurately
and make sure that the SQL Server is running normally.
Besides, sufficient space should be ensured for installing NMS
server. For space requirement, refer to Disk Partitioning Rules (for
Windows) in Appendix.
Note:
If the Standalone mode is selected, NMS client application will be also installed with
NMS server application.
1)
Log in to Windows 2000 Server OS as Administrator. Insert

iManager N2000 install disk in the CD drive. Double click the
setup.bat file. The initial installation interface appears, as
4-16
Installation Manual

N2000 on Windows

2)

4-7.
4-17
Installation Manual

N2000 on Windows
Figure 4-7 Installation license agreement

Read the license agreement carefully, and confirm the agreement.
Click the I accept the terms of the license agreement. radio button,
and then click <Next>.
3)
The directory selection dialog box appears, as shown in

Figure 4-8.
4-18
Installation Manual

N2000 on Windows
Figure 4-8 Select installation directory

The default installation directory is C:\N2000. Click <Browse> to
select any other directory. Then click <Next>.
Caution:
The installation directory is not allowed to contain blank or illegal characters such as
MBCS (Multi-byte Character Set).
4-19
Installation Manual
4)

N2000 on Windows
The installation mode selection dialog box appears, as

[!]
Figure 4-9 Select standalone installation mode

Click the Standalone as the installation mode of the NMS Server.
Click <Next>.
5)
The license selection dialog box appears, as shown in

Figure 4-10.
4-20
Installation Manual

N2000 on Windows
Figure 4-10 Select license file

Click <Browse> to locate a formal license file, which should have
been purchased.
By default, a temporary license file is available. Click <Next>. The
prompt box appears, as shown in Figure 4-11.
4-21
Installation Manual

N2000 on Windows

Click <OK>.
6)
The dialog box similar to Figure 4-12 appears. Select the

functional components to be installed.
Figure 4-12 Select functional components

4-22
[!]
Installation Manual

N2000 on Windows
Check the desired functional components. The component

Element Management Essence is compulsory while others are
optional. If the core component is not selected, the installation will not
proceed. However, if the core component has been installed
previously, you may install the components at will. After the selection,
click <Next>.
Then the installer checks the component dependency. If the
checking fails, the failure results will pop up. Click <Back> to select
components again. If the checking is succeeded and the components
are already installed, then come to next step.
[!]
Note:
In actual installation, the functional components might be different from those as
7)
The database configuration dialog box appears, as shown in

Figure 4-13.
[!]
4-23
Installation Manual

N2000 on Windows
Figure 4-13 Set database information

z
NMS Database User Name: The username used to connect

the NMS with the database. By default, it is N2000user. It
cannot be changed.
NMS Database User Password: The password of the DB

NMS user. It should be at least 6 characters long.
Password Confirm: Re-enter the DB NMS password.
Database sa Password: The password of the database

superuser. It must be completely the same as the password
4-24
Installation Manual

N2000 on Windows
for the database superuser (sa) during the database

installation.
z

server. It is N2000DBServer by default. It cannot be
changed.
ODBC Database Source Name: It is N2000DBServer by

default and cannot be changed.
Database Type: For Windows, it is SQL Server by default.
MDP IP: The IP address of the NMS Server. It is 127.0.0.1

by default.

8)
In the pop-up dialog box, click the Alias tab. Set the
network database, as shown in Figure 4-14.
Figure 4-14 Configure network database
4-25
[!]
Installation Manual

N2000 on Windows
In the dialog box, click <Add> to pop up the Add Network Library
Configuration dialog box, as shown in Figure 4-15.
Figure 4-15 Add network library configuration

In this dialog box, configure attributes of the network database.
The basic configuration information is as follows:
z
Server alias: Specify a unique name for the server that runs
the SQL Server instance. It must be set to N2000DBServer
so that it is consistent with the NMS database server
specified in the previous step.
Network libraries: Specify the network libraries used to

connect the server. Click the Multiprotocol option.
Server name: Specify the name of the database server.

Double click the
icon on the right of Windows task bar.
Then in the pop-up dialog box, copy the corresponding
4-26
Installation Manual

N2000 on Windows
content in the Server list, and paste it here. As shown in

Figure 4-16, copy N2000SERVER and paste it.
Figure 4-16 SQL Server manager

z
Additional parameters: Specify additional parameters for

Multiprotocol network libraries. The field is optional. It is null,
by default.
After the setting, click <OK>.

Then the installer automatically checks the system configuration,
including OS Version, Memory, Disk Free Space and Database
Version. If the checking fails, the failure results will pop up. Change the
configuration according to the current value and the requirement. If the
checking is succeeded, then come to next step.
4-27
Installation Manual

N2000 on Windows
Caution:
Click <OK> after setting the basic database information, the system will automatically
log in to the database server. If the login fails, check from the following aspects:
1) Whether the database server runs normally. Please refer to 4.3.3 II. Check if the
database is properly installed.
2) Whether the database sa password is correct.
3) Whether the database server alias and server name is correct.
9)

4-17.
4-28
Installation Manual

N2000 on Windows
Figure 4-17 Installation information confirmation

functional components, and the needed disk space. If there is no error,
click <Next> to start the installation. Otherwise click <Back> to return
10) The installation begins, and a progress bar appears, as
shown in Figure 4-18. It will cost about 4 minutes. Please
wait.
4-29
Installation Manual

N2000 on Windows
Figure 4-18 Installation progress

11) Then the installation script is executed, and the process bar
appears, as shown in Figure 4-19. It will cost about 6
minutes. Please wait.
4-30
Installation Manual

N2000 on Windows
Figure 4-19 Script execution progress

After the installation script is executed, the interface appears, as
4-31
Installation Manual

N2000 on Windows
Figure 4-20 Script execution completed

click <Next>.
12) The interface appears, as shown in Figure 4-21. Set the
NMS installation parameters.
4-32
Installation Manual

N2000 on Windows
Figure 4-21 Set installation parameters

By default, the current wallpaper and screen saver will be set as
those of the NMS. Click <Next>.
13) The installation summary appears, as shown in Figure 4-22.
4-33
Installation Manual

N2000 on Windows

After confirmation, click <Next>.
14) The restart prompt appears, as shown in Figure 4-23.
[!]
4-34
Installation Manual

N2000 on Windows
Figure 4-23 Restart prompt

Select to restart the system immediately or later, and click
<Finish> to complete the installation. The installer will automatically
create shortcuts for starting remote maintenance terminal and client
on the desktop and in the [Start] menu.
Caution:
After the installation, the operating system should be restart.
4-35
Installation Manual

N2000 on Windows

Start NMS server and NMS client and check if they are properly
installed.
I. Start NMS server

Restart the OS after installation. Log in as administrator. The
NMS server is automatically started as daemon. The user can operate
on it through System Monitor.
II. Start system monitor

1)
Select [Program/iManager N2000/N2000 SysMonitor] from

[Start], or double click the icon
on the desktop. The
Login dialog box then pops up.

2)
Enter the log-in password (N2000 by default). The system

monitor window then pops up to maintain daemons,
databases, system resources, hard disks, and system
version information.

1)
Select [Program/iManager N2000/N2000 Client] from [Start],

or double click the icon
on the desktop. The Login
dialog box then appears.

2)
Enter user name and password (the default password for the
user admin is N2000).
4-36
Installation Manual
3)

N2000 on Windows
The topology main interface of the NMS Client appears, as

Figure 4-24 Initial interface of NMS Client
Note:
The initial interface of the NMS client depends on the selected software. Its initial
menus may differentiate with different software installed.
4-37
Installation Manual

N2000 on Windows
IV. Start database backup tool

Select [Program/iManager N2000/DBBackup Client] from [Start]
menu, or double click the icon
on the CDE, to start the database
backup tool, which makes database backup and recovery easy.
Note:
For the setting of log-in user and log-in server, please refer to Start NMS Server and
Client in Chapter 2 Install iManager N2000 on Solaris.

Steps for client installation mode:
z
Install Operating System
Install NMS Client

Before the installation of NMS Client, make sure that the
Windows 2000 has been properly installed. For how to install it, please
refer to the installation guide attached to the install disk.
4-38
Installation Manual

N2000 on Windows
I. Installation requirements
z
Name of a computer can be English letters or a combination

of English letters and Arabic numerals. The host name must
begin with a letter, and no space should be contained.
The network attributes of the computer should be configured

in order to ensure the connectivity of the network.
It is recommended to set the display mode as 1024768

pixel, 256 colors or higher.
4.4.2 Installing NMS Client

The installation of NMS client is similar to the installation of NMS
server. Please refer to 4.3.6 Installing NMS Server.
1)
Log in to the OS and start the installer. It is recommended to

log in to the OS as the user name commonly used for the
NMS client. The default setting will become valid while client
installation.
2)
Confirm the installation license agreement.
3)
Select the installation directory.
4)
Select the Client installation mode to install the NMS client

only.
[!]
5)
Select the functional components.
6)
Confirm the functional components.
7)
The installation begins, and a progress indicator box shows

the installation progress.
8)
The installation summary appears. Click <Finish> to

complete the installation. The installer will automatically
4-39
Installation Manual

N2000 on Windows
create the shortcut for starting the NMS Client on the

desktop and in the [Start] menu.
II. Check if the NMS client is properly installed

After the NMS client is installed, you can start it to check if the
NMS client application is properly installed. For details, please see the
section 4.3.7 III. Start NMS client.
4-40
Installation Manual
Chapter 5 Frequently Asked

Questions
Chapter 5 Frequently Asked Questions

This chapter introduces FAQs in the installation and operation of
the workstation, database and the NMS.
5.1 Workstation
5.1.1 How to Set up Sun Workstation from CD Drive
(Sun/Solaris)?
If the SUN workstation has a built-in CD drive, the system will
automatically install the contents of the CD to the /cdrom directory. If
the CD is already in the drive, enter the /cdrom directory, to access
the content in the CD can be accessed.
If an external CD drive is used, connect the CD drive and the
workstation with Small Computer Systems Interface (SCSI) cable, and
switch on the CD drive before switching-on the workstation. When the
workstation is started, the contents in the CD will be automatically
installed the /cdrom directory.
I. How to eject CD?

1)
First, confirm that no program is using the CD drive, then exit

from the /cdrom directory and execute the following
command as a super user:
# eject
5-1
Installation Manual
2)

Questions
In case the system prompts Device busy and the CD

cannot be ejected, execute the following command as root
user to disable the CD drive.
# /etc/rc2.d/S92volmgt
stop
3)
Then press the eject button on the CD drive.
4)
To enable the CD drive again, execute the command:
# /etc/rc2.d/S92volmgt
start
II. How to boot up the system with CD?

1)
To install or start the system from the CD, insert a startup CD

in the CD drive. At the OK prompt, execute the following
command:
OK boot cdrom
2)
To check the connection between the SCSI devices and the

workstation, execute the command after the OK prompt.
OK probe-scsi
This method is often used to check the connection with the CD

drive.
5.1.2 How to Set IP Address of Sun Workstation

(Sun/Solaris)?
There are two methods to set IP address for SUN workstation:
5-2
Installation Manual

Questions
I. Specify IP address in the Configure Network field while

installing the OS.
II. Modify the files /etc/hosts and /etc/netmasks.
1)
Open the file /etc/hosts, and then modify the IP address of

the local host.
2)
Open the /etc/netmasks file, and then modify the network

mask of the local host. If there is no other option, add the
content with the command: IP address net mask, like
10.110.1.1 255.255.0.0.
3)
Restart the workstation.
5.1.3 How to Install Solaris from Remote Workstation

(Sun/Solaris)?
You can install Solaris operating system to a workstation that
does not have a CD drive from a remote workstation, provided that
these two workstations are in the same network segment.
Suppose the Solaris install disk is stored in the directory /cdrom
on Host 1. Host 2 is to be installed with the OS. Its IP address is
129.9.111.111, and MAC address is 08:20:30:8f:31:4c.
1)
Enter the directory /cdrom/cdrom0/s0/Solaris-2.6/Tools on

Host 1, and execute the following command.
#./add_install_client
-i
129.9.111.111
-e
08:20:30:8f:31:4c -s host1:/cdrom/cdrom0/s0 host2 sun4u
Herein, sun4u refers to Ultra workstation. For Sparc workstation,

please use sun4m.
2)
Enter the boot net at the OK prompt in Host2.

5-3
Installation Manual

Questions
Now, the installation of Solaris through the network is possible.
5.1.4 How to Modify Hostname of Sun Workstation

(Sun/Solaris)?
To modify the hostname, the following three files are involved:
z
/etc/hostname.hme0
/etc/hosts
/etc/nodename
You should:
1)
modify the original hostname in the above three files to the

desired host name.
2)
restart the workstation to validate the modification.
5.1.5 How to Configure DNS of Sun Workstation

(Sun/Solaris)?
I. Modify the file etc/nsswith
1)
Open the file /etc/nsswitch.conf"
#vi /etc/nsswitch.conf
2)
Find the line with hosts and add dns at the end of the line.
The result is as follows:
hosts files dns
II. Create the file /etc/resolv.conf

1)
Create and open the file /etc/resolv.conf
#vi /etc/resolv.conf
5-4
Installation Manual
2)

Questions
Add the domain name and IP address of the Domain Name

Server (DNS) into the file.
domain
huawei.com
nameserver
10.15.1.3
Herein,
z
domain
Domain name
nameserver
IP address of the DNS
5.1.6 How to Boot up from CD Drive (Sun/Solaris)?

1)
Switch-on the workstation.
2)
When the bootup logo appears, press <Stop+A>, then the

OK prompt appears.
3)
Place the install CD (Sun/Solaris) into the CD drive, key in

the command boot cdrom and press the <Enter> key,
then the workstation will boot from the CD drive.
5.1.7 How to Enable FTP?

For security reason, the FTP (File Transmission Protocol)
function is disabled after Solaris8 has been installed.
To enable the function, you should:
1)
log in as root user.
2)
search for root in the file /etc/ftpusers and mark the line
as reference, then save the file and exit.
3)
log in as root user, and the FTP function is available.
It is recommended to restore to the original settings after using

the FTP function.
5-5
Installation Manual

Questions
5.1.8 How to Enable Telnet?

For security reason, Telnet, FTP and Finger functions are
disabled after iManager N2000 has been installed on Solaris.
To enable the function, you should:
1)
Proceed to the following:
#cd /etc/inet
#cp inetd.conf inet.conf.bak
#cp inetd.conf.021204.034801.bak inetd.conf
Herein, the file name inetd.conf.021204.034801.bak should be

changed to the actual date and time.
2)
query the process of starting services to read the file again.
#ps -ef | grep inet

root 144 1 0 12 04
0:00 /usr/sbin/inetd -s
#kill -HUP 144
The function is enabled now. After use, disable it with the

following command:
#cp inet.conf.bak inetd.conf
#kill -HUP 144
5.1.9 File Size Changed after FTP Transmission

When a file is transmitted using FTP, if the file contains binary
contents (like the NMS installer, and the interfaces file of the
database), it must be transmitted in the binary format. Otherwise
errors will occur.
5-6
Installation Manual

Questions
ASCII is the default transmission mode of FTP. To transmit binary

contents, you must execute the bin command to change the
transmission mode.
5.1.10 Cannot Execute Program Files after FTP

Transmission
Sometimes, installation programs may become not executable
after being copied to local hard disk through FTP. In this case, you
should modify the attribute of the program files as executable.
Take the NMS setup file for example, execute the following
command:
# chmod +x setup.sh
To make all the files under a directory executable, execute the

command chmod -R +x (directory).
5.2 Database System

5.2.1 After Abnormally Shut down of SUN
Workstation (Sun/Solaris/Sybase)
Do not make frequent shutdown and restart on the workstation.
Incorrect operations, direct power-off, or power failure may damage
the file system.
If the SUN workstation is shut down abnormally, it is necessary to
restore the operating system and the database. The system will
automatically check and restore the file system at reboot. You can also
use the command fsck to manually check the file system.
5-7
Installation Manual
1)

Questions
Log in as root user and execute the fsck command.
# fsck -y
The system begins to correct the errors in the file system until the
completion of the correction.
2)
If the Sybase database does not start, delete the

/opt/sybase/N2000DBServer.krg
file
(herein,
N2000DBServer is the name of a database server).

3)
Execute the /usr/sbin/shutdown -y -g0 -i6 command to

restart the workstation.
5.2.2 How to Set the sa Password

(Sun/Solaris/Sybase)?
After the Sybase database is installed, the default sa password is
null. To set the password, for example, to set the sa password as
n2000n2000 for N2000DBServer, you should:
1)
do as follows:
#./isql SN2000DBServer -Usa P

1>sp_password null,n2000n2000
2>go
2)
then the following display appears:
Setting password succeeded!

(return status=0)
1>
3)
enter quit to exit.
The sa password cannot be changed to null after being set. So

you must remember the new password.
5-8
Installation Manual

Questions
5.2.3 How to Set the sa Password (Windows/SQL

Server)?
If the sa password is not configured during the installation of SQL
Server 2000, set it through the following methods after installation.
I. Method 1
1)

from the [Start] menu to pop up SQL Server Enterprise
Manager window.
2)
Unfold the directory tree on the left and locate the security
node.
3)
Click Login and double click sa on the right of the window.
4)
Set password in the pop-up "SQL Server Login Properties

dialog box.
II. Method 2
Modify the password through isql application. It is just the same
as the operations for Sybase. Refer to 5.2.2 How to Set the sa
Password (Sun/Solaris/Sybase).
5.2.4 Unable to Start Sybase

Check the shared memory in the /etc/system file for the
following contents (usually at the end of the file):
set shmsys:shminfo_shmmax = 131072000
Herein, 131072000 is calculated from the following formula on
the basis of a 128MB memory.
5-9
Installation Manual

Questions
Y=X*1024*1000 (where X is the physical memory in MB).

If the shared memory is smaller than the value calculated
according to the physical memory, the Sybase cannot start. In this
case, you should calculate and set the shared memory again. Then
restart the operating system.
5.2.5 How to Install Sybase11.9.2?

If the recommended Sybase 12.0 is unavailable, Sybase 11.9.2
can be installed for iManager N2000 V200R001. The installation
procedures of Sybase 11.9.2 are described in Installation Manual of
iManager N2000 V100R006. However, there are some differences
when installing this version for iManager N2000 V200R001.
1)
In the srvbuild -Select Servers to Build dialog box, set

Adaptive Server as N2000DBServer and Backup
Server as N2000DBServer_back.
2)
In the srvbuild-Server Attribute Editor dialog box, set

master device size as 120"MB and master database size
as 100MB.
3)
After the database is installed successfully, there is no need

to add environment parameters in the/etc/profile file. Enter
the following command in the terminal window:
#SYBASE=/opt/sybase
#export SYBASE
#DSQUERY=N2000DBServer
#export DSQUERY
5-10
Installation Manual
4)

Questions
Herein, /opt/Sybase is the installation path of the database.

N2000DBServer is the name of the master database
server.
5)
After setting the above parameters, use isql program to

connect with the database server. Make sure that the
database server is installed successfully, install the NMS
directly. There is no need to restart the workstation.
The rest procedures are the same. Refer to Installation Manual of

iManager N2000 V100R006 for more details.
5.2.6 Sybase 11.9.2 Dynamic Database Interface

Memory Leakage
Memory leakage may occur to Sybase 11.9.2 dynamic database
interface. To tackle this, you may install corresponding patch to the
database proceeding to the following steps:
I. Create a temporary directory, such as /opt/patch

#cd /opt
#mkdir patch

Copy or ftp Sybase11_9_2_patch.tgz to /opt/patch.
1)
Under the directory /opt/patch, to unpack the patch package,

execute the following commands:
#cd /opt/patch
#cd /opt/patch
5-11
Installation Manual

Questions
#gzip -d Sybase11_9_2_patch.tgz
2)
To further unpack the patch package, execute the followoing

commands:
#tar xvf Sybase11_9_2_patch.tar

3)
Close sybase database process, and log in as a root user to

set the sybase environment variables.
#SYBASE=/opt/sybase
#export SYBASE
#PATH=$PATH:$SYBASE/bin
#export
PATH
#LD_LIBRARY_PATH=$LD_LIBRARY_PATH:$SYBASE/lib
#export LD_LIBRARY_PATH
Then execute the following command:

#./syb119_ebf10491_install.sh
Prompt: To avoid that the files under the sybase directory belong
to root group after loading the patch, execute the following command
after the patch is installed:
Some system may have no sybase user, whereto the system will
prompt: chown unknown user ID: sybase when the execution is
5-12
Installation Manual

Questions
5.2.7 Sybase 12.0 Dynamic Database Interface

Memory Leakage
Memory leakage may occur in Sybase 12.0 dynamic database
interface. To tackle this, you may install corresponding patch on the
database proceeding to the following steps:
I. Create a temporary directory, such as: /opt/patch

#cd /opt
#mkdir patch

Copy or ftp Sybase12_0_patch.tgz to /opt/patch.
III. Under the directory /opt/patch, to unpack the patch

package, enter the following commands:
#cd /opt/patch
#gzip -d
Sybase12_0_patch.tgz
IV. To further unpack the patch package, enter the following

command:
#tar xvf Sybase12_0_patch.tar
5-13
Installation Manual

Questions
V. Close sybase database process, and log in as a root user.

To set sybase environment variables, execute the following
command:
#./ syb12_ebf11089_install.sh
Prompt: To avoid that the files under the sybase directory belong
to root group after loading the patch, execute the following command
after the patch is installed:
Some systems may have no sybase user, whereto the system will
prompt: chown unknown user ID: sybase. This is normal.
5.2.8 How to Add, Delete and Modify an Oracle

Instance (Oracle)
Use $ORACLE_HOME/bin/dbassist, which applies to the case
when the Oracle data file (such as the whole $QNMROOT directory) is
deleted by carelessness.
5.2.9 How to Modify the Maximum Number of Oracle

Connections (Oracle)
Method 1: Specify the maximum number of the connection as
500 when installing Oracle database.
Method 2: Modify PROCESS=500 in initSID.ora, then close and
restart Oracle database.
5-14
Installation Manual

Questions
5.2.10 Where to Put the Configuration Information

and Files after Oracle is Installed (Oracle)
$ORACLE_BASE/admin
For default server files. Herein,
initialized configuration files are saved in the sub-directory pfile.

$ORACLE_BASE/oradata
Oracle
database
file
executable
file
directory(where system files are saved).

$ORACLE_HOME/bin
Oracle
directory.
$ORACLE_HOME/dbs
Oracle server file directory,
part are connected with files from admin.

$ORACLE_HOME/rdbms/admin For scripts that create the
system database objects.
$ORACLE_HOME/network/admin
Oracle
network
configuration directory.
5.2.11 How to Uninstall Oracle Database Completely

(Oracle)
Delete Oracle install directory, /var/opt/oracle and temporary
directory under /tmp.
5.2.12 Unable to Start Oracle Database (Oracle)

This is because the port sense program of the database is not
started. Execute the following command:
$ORACLE_HOME/bin/lsnrctl
start
5-15
Installation Manual

Questions
to start it.
5.2.13 NMS Database Files Are Deleted by Mistake

and Fail to be Created When NMS Is Reinstalled
(Oracle)
If the data files in the NMS database are deleted by mistake, and
fail to be created when NMS is reinstalled, you may recover them
following the steps below:
1)
Start:
svrmgrl
2)
Log in to (herein, internal is the database super username,

and oracle is the password):
connect
3)
internal/oracle
If the database is in running status, execute:
shutdown immediate
4)
Start the database:
startup
5)
mount
Assume
the
deleted
/opt/iManager/db/oracle/dbf/dcnm.dbf,
file
execute
is
the
following command:
Alter database datafile
'/opt/iManager/db/oracle/dbf/dcnm.dbf' offline drop
(Repeat this step until all deleted datafile files change to offline
status)
Execute the following command:
Alter database
open
5-16
Installation Manual
6)

Questions
Execute the following command (similarly, other table space

of the database can be deleted).
Drop
7)
tablespace dcNMS including
contents
Reinstall the NMS
5.2.14 How to Modify Oracle SA system Password

(Oracle)
To modify oracle SA system password (manager by default), log
in to the operating system as an oracle user, and use the sqlplus
command to modify the password:
$ sqlplus
1>connect system/manager
2>alter user system identified by userdefine;
Remember the modified password.
5.3 Network Management System

5.3.1 Abnormal NMS Functions
Problem description: If the system time of the server is modified
while the NMS is running, some system functions (like the timed dump
of the security daemon) that are based on the timer principles might
become abnormal.
Solution: Shut down the NMS and the database system, and
then restart the operating system. Then the functions become normal.
5-17
Installation Manual

Questions
Suggestion: System time of the server should be set accurately

during the installation of the NMS. While the NMS is running, the
system time should not be modified.
To modify the system time, first exit the NMS, then modify the
system time and restart the NMS.
5.3.2 Unable to Install the NMS again

Problem description: SQL Server and NMS have been
uninstalled. Install again SQL Server database in the same directory.
The database system is already running normally. All the settings are
correct. However, it prompts error while installing NMS again.
Cause: NMS databases will not be deleted when SQL Server is
uninstalled. There are already databases in the directory if you install
again in the same directory. The system cannot create more
databases so the installation fails.
Solution: Before uninstalling SQL Server, backup the important
database files, and then delete all database files. Then install it again.
The NMS can be normally installed.
To delete the database files, you should:
1)

from [Start]. The SQL Server Enterprise Manager window
then appears.
2)
Select Database node of the server under SQL Server

Group.
3)
Delete all the databases, including TopoDB, FaultDB,

SecurityDB, PerfDB, LogDB, and ResourceDB.
5-18
Installation Manual

Questions
5.3.3 Illegal Characters

Cause: If the language setting of the operating system is different
from that of the NMS, illegal characters will appear after user login.
Solution: First log out, then select the language and log in again.
5.3.4 Unable to Log in to System Monitor

Cause:
Dynamic
Host
Configuration
Protocol
(DHCP)
configuration on the server may result in the change of IP address

after server restart. The host name cannot be found so you may fail to
log in to the system monitor.
Solution: Configure a fixed IP address for the server.
To install NMS on a DHCP server, please contact the technical
support engineers of Huawei.
5.3.5 Unable to Display File Names while Copying

This may happen when installing NMS on Windows operating
system. If the installation directory containing \n, for example,
C:\n2000, the names of files being copied may not be shown
normally on the progress bar. However, it does not matter. Do not
abort the installation.
5.3.6 No Response during Installation

Problem description: While installing NMS on Windows
operating system, the installation interface may stop refreshing as if
there is no response.
5-19
Installation Manual

Questions
Cause: The installation program is started with a .bat file and a

DOS window will pop up. If you click it accidentally during the
installation, the window will be activated and the above problem may
occur.
Solution: Click <Enter> in the DOS window and continue the
installation.
5.3.7 Cannot Install Normally After Uninstalling

Problem description: When the original NMS or client is
uninstalled and a new version is installed, between which, if the
computer is not restarted, the NMS will fail to be started after
installation.
Solution: The computer must be restarted after the original NMS
or client is uninstalled before the new version is installed. Otherwise,
install shield will delete files under the install directory in random,
resulting in NMS failing in starting. Follow the steps below:
Uninstall old version -> Restart computer -> Install new version ->
Restart computer
5.3.8 Installation Fails Due to Improper Password

Setting
Problem description: When N2000user password is set as
database, the NMS installation may fail when the install database
script reaches 50%.
5-20
Installation Manual

Questions
Solution: database is a keyword of the database, thus resulting

in the installation failure. Set N2000user password not using the
keyword.
5-21
Installation Manual
Appendix A Disk Partitioning

Rules
Appendix A Disk Partitioning Rules

A.1 For Solaris
A.1.1 Disk Partitioning Rules
File partitioning mode is generally adopted. The basic rules are
as follows.
1)
Allocate space for the / (primary partition) according to the

capacity of the hard disk. It should be no less than 3GB.
2)
Allocate space for the swap (swap partition). The partition

size should be 1~4 times of the memory size. Four times are
recommended. Too large swap partition may deteriorate the
system performance. For example, if the memory is 4GB, it
is enough to set the swap partition as 4GB. However, it
should be no less than 2GB.
3)
Allocate all the free space for the /opt partition. After
sufficient space is reserved for both the primary partition and
the swap partition, the opt partition can be allocated
accordingly. However, it should be no less than 6GB.
A.1.2 Disk Partitioning Plan

1)
Partitioning plan for 1*20GB disk/512MB memory, installing

Sybase
A-1
Installation Manual

Rules
Table A-1 Partitioning plan for 1*20GB disk/512MB memory

Slice
Partition
0
1
2
3
4
5
6
/
swap
overlap
Size
(MB)
17385
2048
19457
20
2)
Description
The primary partition.
The swap partition. 4 times of the memory size.
The total space of the disk. No modification is needed.
Raw partition /dev/rdsk/c0t0d0s7, reserved for disk

mirroring
Partitioning plan for 2*73GB disk/2GB memory, installing

Sybase
Table A-2 Partitioning plan for hard disk 1

Slice
Partition
0
1
2
3
4
5
6
/
swap
overlap
Size
(MB)
65502
4096
69618
20
Description

mirroring

Slice
Partition
0
1
/opt
Size
(MB)
69618
Description
All for /opt partition.
A-2
Installation Manual
Slice
Partition
2
3
4
5
6
7
overlap
3)
Size
(MB)
69618

Rules
Description
Partitioning plan for 2*36GB disk/2GB memory, installing

Sybase

Slice
Partition
0
1
2
3
4
5
6
/
swap
overlap
Size
(MB)
30610
4096
34730
20
Description

mirroring
/opt
Size
(MB)
34730
overlap
34730
Slice
Partition
0
1
2
3
4
5
6
Description
A-3
Installation Manual
Slice
Partition
Size
(MB)

Rules
Description
4)
Partitioning plan for 4*18.2GB disk/4GB memory, installing

Sybase

Slice
Partition
0
1
2
3
4
5
6
/
swap
overlap
Size
(MB)
13153
4096
17269
20
Description

mirroring
/opt
Size
(MB)
17269
overlap
17269
Slice
Partition
0
1
2
3
4
5
6
7
Description
A-4
Installation Manual

Rules

Slice
Partition
0
1
2
3
4
5
6
7
/export
/var
overlap
Size
(MB)
15269
2000
17269
Description

Slice
Partition
Size
(MB)
Description
0
1
2
overlap
17269
3
4
5
6
7
Note: Hard disk 4 is served as the disk mirroring of hard disk 1
A-5
Installation Manual

Rules
A.2 For Windows

A.2.1 Disk Partitioning Rules
Partition the disk in Windows NT File System (NTFS) format.
Redundant Array of Inexpensive Disks (RAID) is recommended for
arraying multiple hard disks to improve the system performance.
Disk partitioning rules:
1)
At least three partitions are required.
2)
The operating system and the application software (NMS

and database system) should be installed on different
partitions.
3)
The operating system should be installed on the primary

partition. The partition size should be no less then 5GB.
4)
The NMS and database system should be installed on the

same partition. Because log and alarm dumping will be
saved under the NMS directory, a rather large partition size
is required. The partition size should be no less than 6GB.
5)
Prepare a largest partition for NMS database backup. A

large amount of data will be saved on this partition.
A-6
Installation Manual

Rules
Note:
The purpose of applying RAID is to array multiple hard disks according to a certain
requirement and build a fast storage system of large capacity. Although data are
saved on different disks, all the disks can be operated as a whole, just like only one
disk. The processor can access the disks in parallel, thus minimizing the read/write
time consumed. Cyclic redundancy check technology is adopted to improve the
system reliability. There are several levels for RAID.
1) RAID 0: It consists of two or more hard disks with the total capacity of them. The
data are evenly written to these two disks. It is fast but without error tolerance.
2) RAID 1: (Hard Disk Mirroring). It consists of two hard disks with one as master and
the other as slave. The system saves any change of master disk to the slave disk. The
error tolerance is 100%. But only one disk space is in actual use.
3) RAID 3: It consists of at least 3 hard disks. One disk is used for saving the parity
information. The valid data are saving as bits or bytes on the other disks.
4) RAID 5: Like RAID3. But the parity information will be saved to every disk in
sequential access. RAID 5 is the commonly used data protection scheme.
A.2.2 Disk Partitioning Plan

Some disk partitioning plans are provided for your reference.
Table A-10 Partitioning plan for 40GB disk/1GB memory
Primary
Size
(GB)
10
Logic 1
10
Logic 2
20
Partition
Description
Installed with operating system.
Installed with database and iManager
N2000 NMS.
Saving NMS backup data.
A-7
Note
None.
Installation Manual

Rules
Table A-11 Partitioning plan for 36GB disk/4*256GB memory
Primary
Size
(GB)
10
Logic 1
10
Logic 2
16
Partition
Description
Installed with database and
iManager N2000 NMS.
Note
None.
Table A-12 Partitioning plan for 3*36GB disk/4*512GB memory

Partition
Size
(GB)
Description
Primary
10
Logic 1
20

iManager N2000 NMS.
Logic 2
42
Note
Adopt RAID 5.
2*36GB in actual use.
The left 36GB is
redundant disk for
saving parity check
data.
Table A-13 Partitioning plan for 5*36GB disk/4*1GB memory

Partition
Size
(GB)
Description
Primary
10
Logic 1
20

iManager N2000 NMS.
Logic 2
78
A-8
Note
Adopt
RAID5+HotSpare.
With 4 disks as
RAID5 and 1 disk as
backup.
4*36GB in actual
use. The left 36GB is
redundant disk for
saving parity check
data.
Installation Manual
Appendix B Database Space

Configuration

Configuration
Database space requirements are summarized here for your
reference when implementing hard disk partitioning. The initial sizes of
databases are automatically configured by the installation program.
B.1 For Solaris

Table B-1 Database spaces for Sybase
Database
Name
Device Name
File Name
Device Size
(MB)
Database
Size
(MB)
TopoDBdata
TopoDBdata.dat
30
30
TopoDBlog
TopoDBlog.dat
15
15
FaultDB
FaultDBdata
FaultDBdata.dat
300
300
FaultDB
FaultDBlog
FaultDBlog .dat
500
500
SecurityDBdata
SecurityDBdata.dat
SecurityDBlog
SecurityDBlog.dat
PerfDBdata
PerfDBdata.dat
40
40
PerfDBlog
PerfDBlog.dat
20
20
ResourceDBdata
ResourceDBdata.dat
30
30
ResourceDBlog
ResourceDBlog.dat
15
15
LogDBdata
LogDBdata.dat
150
150
LogDBlog
LogDBlog.dat
75
75
TopoDB
SecurityDB
PerfDB
ResourceD
B
LogDB
B-1
Installation Manual

Configuration
Table B-2 System database spaces for Sybase

Database
Name
Device Name
Device Size
File Name
Database
Size (MB)
(MB)
master
Master
master.dat
120
100
systemprocs
sysprocsdev
systemprocs.dat
100
100
systemdb
Systemdbdev
systemdb.dat
50
50
tempdb
tempdbdata
tempdbdata.dat
1000
1000
Note:
The database of tempdb will be created during the installation, while other system
databases are configured during the creation of the database server. The minimum
disk space reserved for the Sybase database is recommended as: 1182 + 1270 =
2452MB (3000MB is recommended, including the reserved space).
B.2 For Windows

Table B-3 Database spaces for SQL Server
Database
Name
TopoDB
Device Name
TopoDB_data
TopoDB_log
FaultDB
SecurityDB
FaultDB_data
FaultDB_log
SecurityDB_dat
a
Physical File
Name
TopoDB_data.
mdf
TopoDB_log.ldf
FaultDB_data.m
df
FaultDB_log.ldf
SecurityDB_dat
a.mdf
B-2
Initial
(MB)
Maximum
(MB)
Increased
by (MB)
10
30
10
15
100
300
50
100
500
50
Installation Manual
Database
Name
Device Name
SecurityDB
SecurityDB_log
PerfDB
ResourceD
B
LogDB
PerfDB_data
PerfDB_log
ResourceDB_d
ata
ResourceDB_lo
g
LogDB_data
LogDB_log

Configuration
Physical File
Name
SecurityDB_log.
ldf
PerfDB_data.m
df
PerfDB_log.ldf
ResourceDB_d
ata.mdf
ResourceDB_lo
g.ldf
LogDB_data.md
f
LogDB_log.ldf
Initial
(MB)
Maximum
(MB)
Increased
by (MB)
10
40
10
20
10
30
10
15
50
150
50
25
75
25
Note:
The initial size represents the database size after the first installation. The database
will expand with the increasing of the data saved in it until the size reaches the
maximum.
Table B-4 System database spaces for SQL Server

Database
Name
Device
Name
Physical File
Name
Initial
(MB)
Maximum
(MB)
Increased
by (MB)
master
master
master.mdf
No restriction
10
tempdb
tempdev
tempdb.mdf
No restriction
10
B-3
Installation Manual

Configuration
Note:
The minimum space for installing SQL server is recommended as: 1182MB+the
space reserved for the system database.
B-4
Installation Manual
Appendix C Uninstall NMS

C.1 For Solaris
C.1.1 Uninstalling NMS Server
1)
Preparations
Shut down NMS server and close all the clients before
uninstalling the NMS.
Through system monitor, shut down NMS server and exit all the
NMS clients. Before shutting down the server, ensure the operations
on the client are all completed. Otherwise, the operations will be
invalid due to communication broken between server and client.
Under Solaris, the database server need not restart before
uninstalling NMS server.
2)
Start uninstaller and open a terminal window. Execute the

following commands to switch over the super user:
$ su
Password:
Input super user password, and press <Enter>. Execute
thefollowing commends:
# . /n2kuser/.profile
#cd $N2000ROOT/uninstallscript
C-1
Installation Manual
# /uninstall.sh
3)
The initial uninstall window appears. Click <Next>.
4)
Confirm that you have made all the preparations before

uninstalling. Click <Next>.
5)
The system prompts the location of the components to be

uninstalled. Click <Next>.
6)
Execute the uninstall script. Wait till finish, click <Next>.
7)
Enter the uninstall process. The system will prompt you to

confirm whether or not to delete all the files. Wait till finish,
click <Next>.
8)
The uninstall summary appears. Click <Next>.
9)
The system prompts you to restart the operating system.

Select to restart instantly or later. Click <Finish>. The
uninstall process is completed.
C.1.2 Uninstalling NMS Client

1)
Start NMS uninstaller.
2)

uninstalled.
3)
Enter the uninstall process.
4)
The uninstall summary appears. Click <Finish>. The

C-2
Installation Manual
Note:
The procedures of uninstalling NMS client under Solaris are similar to C.1.1
Uninstalling NMS Server. Please refer to that section.
C.2 For Windows

C.2.1 Uninstalling NMS Server
1)
Preparations
Shut down NMS server, close all the clients, and restart
database server before uninstalling the NMS.
z
Shut down NMS server and close all the clients: Through
system monitor, shut down NMS server. Exit all the NMS
clients. Before server shutdown, ensure the operations on
the client are all completed. Otherwise, the operations will
be invalid due to communication broken between server
and client.
Restart database server: In the SQL Server Service

Manager dialog box, click <Stop> to close database
server. Then click <Start/Continue> to start database
server. This is to break the connection of the databases to
be uninstalled.
C-3
Installation Manual
2)
Start
NMS
installer.
Select
[Program/iManager
N2000/Uninstall N2000] from the [Start] menu. The initial

uninstall window appears. Click <Next>.
3)
Confirm that you have made all the preparations before

uninstalling. Click <Next>.
4)

uninstalled. Click <Next>.
5)
Execute the uninstall script. Wait till finish, click <Next>.
6)
Enter the uninstall process. The system will prompt you to

confirm whether or not to delete all the files. Wait till finish,
click <Next>.
7)
The uninstall summary appears. Click <Next>.
8)
The system prompts you to restart the operating system.

Select to restart instantly or later. Click <Finish>. The
C.2.2 Uninstalling NMS Client

The procedures of uninstalling NMS client under Windows are
similar to C.2.1
Uninstalling NMS Server. Please refer to that
section.
C-4
Installation Manual
Appendix D Install and Use

Tape Drive
Appendix D Install and Use Tape Drive

D.1 For Solaris
D.1.1 Installing and Uninstalling of Tape Drive
Taking SUN SG-XTAP4mm-011A(DDS-3) tape drive for example,
the following will guide you to install and uninstall tape drive.
I. Install tape drive

E450 is equipped with a build-in tape drive. You need not install it.
To install an external tape drive, for example, Ultra 60, please follow
the operations:
1)
Power off all peripherals.
2)
Set the tape drive ID as 4 or 5.
3)
There are IN and OUT ports on tape drive. If Small

Computer Systems Interface (SCSI) interface is adopted,
connect SCSI cable into the IN port of tape drive.
4)
Power on the peripheral and the computer. Boot the system.
II. Check tape drive status

Query the status of tape drive after system start by executing the
following command.
# mt f /dev/rmt/0mn status
D-1
Installation Manual

Tape Drive
The above command can be shortened as mt status. Different

prompts will be given.
HP DDS-3 4MM DAT tape drive:
sense key(0x6)= Unit Attention
file no= 0
residual= 0
retries= 0
block no= 0
It indicates that the tape drive is normal with tape in and rewound
to the header.
No such device or address
It indicates that there is no connection between tape drive and

workstation, or the connection is broken.
/dev/rmt/0n: no tape loaded or drive offline
It indicates that no tape is loaded or tape drive is offline.

/dev/rmt/0n: No such file or directory
It indicates the tape drive is not connected. Log in as root,

execute the following commands:
#drvconfig
#tapes
Insert tape into the drive. Beware the direction and query the
drive status by executing the following commands:
# mt status
III. Indicators
There are two indicates on the front panel of the tape drive.
z
tape: Green. Off when there is no tape in the drive. On with

tape in. Flash when reading/writing tape.
D-2
Installation Manual
z

Tape Drive
clean: Off in normal status. On when the tape header need

cleaning.
IV. Uninstall tape drive

If the tape drive is of no use, directly plug off the connector to
uninstall it.
D.1.2 Commands
I. Naming rules
In the /dev/rmt/ subdirectory, there is a group of tape drive files.
The naming rules are as follows:
/dev/rmt/XAn
Herein,
z
X represents the serial No. of a tape drive. It is 0 if there is

only one tape drive.
A represents the density of a tape drive. m represents

medium. If no density is specified, the tape drive will write
the tape at the highest density supported by the drive.
n represents no rewinding and stopping at the current

position. If there is no n parameter, the tape will rewind to
the initial position after any operation on it.
D-3
Installation Manual

Tape Drive
II. tar command

With the tar command, multiple files can be saved as an archive
into tape or disk. The files can be extracted from the archive. The
command format is as follows:
$ tar
[function option[modifier]]
[files]
The command option of tar includes function option and

modifier. The function option is used to set the action of "tar, such as
read or write. The modifier is to modify the action of tar.
Function option:
z
r is to append files to the archive.
x is to extract files from the archive. The subdirectory in a

directory file will also be extracted.
c is to create a new archive.
g is to add files from the beginning of the archive.
Modifier:
z
v is to start view mode. The name of the file in processing

will be shown.
w is to start confirm mode. The user should confirm before

processing.
"f represents file. If it is omitted, the operation object will

be the preset tape or disk.
Examples:
z
tar cvf B.tar A
//File or directory A will be packed
to the B.tar file. A or B can be with an absolute path.

z
tar xvf A.tar //If the A.tar file is created in an absolute

path, it will be extracted to the same path. The path will be
D-4
Installation Manual

Tape Drive
automatically created when it does not exist. If the "A.tar file

is created in a relative path, it will be extracted to the current
path.
z
tar rvf /dev/rmt/0n A
// File or directory A will be
appended to the tape. The tape will not rewind.

z
tar cvf /dev/rmt/0 A
// File or directory A will be coped
to the tape. The original files on the tape will be overwritten.

The tape will rewind.
z
tar tvf /dev/rmt/0
//The files saved by tar in the tape
will be listed in a table.
III. Other commands

z
mt status
//Query the status of tape drive.
mt rewind
//Rewind the tape to initial position.
mt offline //Before ejecting the tape, execute the command.

Otherwise, the tape will automatically rewind to the header
and then exit.
D.2 For Windows

D.2.1 Installing and Uninstalling Tape Drive
Taking Dell PowerVault 100T DDS4 TAPE DRIVE for example,
the following will guide you to install and uninstall tape drive under
Windows 2000 Server.
I. Install tape drive

1)
Power off the computer. Install an SCSI card 39160, a PCI

of 64 bit. But it can work in a 32-bit PCI slot.
D-5
Installation Manual
2)

Tape Drive
Connect the tape drive to the computer with connection

cables. Set tape drive ID as 6 (the default value). If the other
SCSI interface is of no use, mount it with the isolated
connector.
3)
Power on the computer and tape drive. The computer will

automatically
recognize
the
tape
drive.
Select
[Program/Management Tool/Computer Management] from

the [Start] menu. In the pop-up Computer Management
dialog box, select Device Manager node and query
whether the status of Tape Manager is normal.
II. Uninstall tape drive

If the tape drive is of no use, directly plug off the connector to
uninstall it.
III. Indicators
There are four LEDs on the front panel of the tape drive. One is
the power indicator, the other three indicators can prompt the normal
or error status. Facing the front panel, the four indicators are
described from the left to the right as follows.
z
Power LED: On when power on.
Clean LED: Green. Indicating the clean condition of the tape

drive. On when the drive need cleaning. Use the qualified
clean tape to clean the drive. Flash slowly when the tape
exceeds the preset software error threshold. This is the only
alarm signal. The lost data will not be shown. Once the
signal occurs, eject the tape as soon as possible and use the
qualified DDS clean tape to clean the drive header. After
D-6
Installation Manual

Tape Drive
cleaning, insert the original data tape again. If the Clean

LED still flashes, change a new tape and retry. The clean
LED turns off when the drive needs no cleaning.
z
Media LED: Green. Indicating the tape status in the drive.

On when the DDS tape is inserted and the drive runs
normally. Flash quickly when the write operation failed. The
drive cannot write data into the tape because the written
data reaches the maximum. Use the qualified DDS clean
tape to clean the drive header. After cleaning, insert the
original data tape again. If the Clean LED still flashes,
change a new tape and retry.
Drive LED: Amber. Indicating the tape drive status. On when

reading/writing tape. If the tape is ejected when the LED is
ON, the data may be lost. If the SCSI Protect Media
command is executed, the tape eject button is prohibited
when the LED is ON, thus to avoid mal-operation. Flash
quickly when an error occurs to the hardware. Press the
eject button on the front panel. If the tape does not go out in
2 minutes, press and hold the button for 5 seconds, the tape
will pop out in 40 seconds.
IV. Eject tape box

Press the eject button to pop out the tape box when the Drive
LED turns off. Otherwise, the data may be lost. It may take several
minutes from the button down to the tape out. During the period, do
not power off the tape drive or the computer.
D-7
Installation Manual

Tape Drive
V. When to clean tape header

The tape drive may not be able to read or write the tape due to
dust on tape header or bad tape media. To avoid the situation, clean
the tape header of PowerVault 100T DDS4 tape drive at the following
conditions.
z
DDS1 or DDS 2 reading/writing for 25 hours
DDS3 or DDS 4 reading/writing for 50 hours
Clean LED On or Flash
Media LED Flash
If the LED still flashes, change a new tape and retry.
VI. How to clean tape header

Be sure to use the qualified DDS clean tape, for example, Dell
P/N 89XJC. Do not use the unqualified clean tape, including that for
DAT (Digital Audio Tape) drive. Otherwise, the drive may be damaged.
After the clean tape is inserted, the drive will detect and recognize
it. It will take 30 seconds to load and run the tape. When the cleaning
work is completed, the tape box will be popped out. The next time you
load the clean tape, it will start from the unused part without rewinding.
The tape will run out after about 30 times of usage.
D-8
Installation Manual
Appendix E Abbreviations
Abbreviations
Full Name
ACL
Access Control List
ADSL
Asymmetric Digital Subscriber Line
AMG
Access Media Gateway
ATM
Asynchronous Transfer Mode
BAS
Broadband Access Server
BMS
Broadband Management System
CDE
Common Desktop Environment
CNM
Client Network Management
DHCP
Dynamic Host Configuration Protocol
EMF
Element Management Framework
EML
Element Management Layer
EMS
Element Management System
FTP
File Transfer Protocol
GUI
Graphic User Interface
IAD
Integrated Access Device
IADMS
Integrated Access Device Management System
LCT
Local Configuration Terminal
MG
Media Gateway
MGCP
Media Gateway Control Protocol
MIB
Management Information Base
MML
Man Machine Language
MTBF
Mean Time Between Failures
MTTR
Mean Time To Recovery

E-1
Installation Manual
Abbreviations
Full Name
NGN
Next Generation Network
NML
Network Management Layer
NMS
Network Management System
OAM
Operations, Administration and Maintenance
ODBC
Open Database Connectivity
OSS
Operation Support System
RAID
Redundant Array of Inexpensive Disks
SCSI
Small Computer Systems Interface
SNMP
Simple Network Management Protocol
TMN
Telecommunications Management Network
UMS
U-SYS Management System
VPN
Virtual Private Network
XML
Extensible Mark-up Language
E-2

31040812-N2000 Installation Manual

Hochgeladen von

Dokumentinformationen

Copyright

Verfügbare Formate

Dieses Dokument teilen

Dokument teilen oder einbetten

Freigabeoptionen

Stufen Sie dieses Dokument als nützlich ein?

Sind diese Inhalte unangemessen?

Copyright:

Verfügbare Formate

31040812-N2000 Installation Manual

Hochgeladen von

Copyright:

Verfügbare Formate

HUAWEI

HUAWEI iManager N2000 Fixed Network

HUAWEI iManager N2000 Fixed Network Integrated

Manual Version T2-100412-20030924-C-2.20

comprehensive technical support and service. Please feel free to

Huawei Technologies Co., Ltd.

2003 Huawei Technologies Co., Ltd.

All Rights Reserved

, HUAWEI, C&C08, EAST8000, HONET,

ETS, DMC, TELLIN, InfoLink, Netkey, Quidway, SYNLOCK, Radium,

About This Manual

Chapter 1 System Overview introduces the system features and

Chapter 2 Installing iManager N2000 on Solaris + Sybase

Chapter 3 Installing iManager N2000 on Solaris + Oracle

Chapter 4 Installing iManager N2000 on Windows describes

Chapter 5 Frequently Asked Questions collects the FAQ

Appendix describes disk partitioning rules, database space

Network design & management personnel

Network maintenance personnel

Engineer for iManager N2000 Integrated Network Management

Normal paragraphs are in Arial.

Warnings, cautions, notes and tips are in Arial Narrow.

Headings, Command, Command Description are in boldface.

Terminal Display is in Courier New; message input by the

II. GUI conventions

Message entered via the terminal is within angle brackets.

Multi-level menus are separated by forward slashes (/). For

III. Keyboard operation

Press the key with key name expressed with a pointed

Press the keys concurrently; e.g. <Ctrl+Alt+A> means the

The item with a square bracket indicates the menu option,

Multi-level menu options, e.g. [System/Option/Color setup]

IV. Mouse operation

Press the left button twice continuously and quickly.

Press and hold the left button and drag it to a certain

Caution: Means reader be extremely careful during the

2.4.1 Installing Operating System ..................................2-59

5.1.1 How to Set up Sun Workstation from CD Drive

5.2.9 How to Modify the Maximum Number of Oracle

B.2 For Windows..................................................................... B-2

Chapter 1 System Overview

Chapter 1 System Overview

management and network management.

Chapter 1 System Overview

The client/server architecture means that multiple clients are

architecture, as shown in Figure 1-1.

Chapter 1 System Overview

Figure 1-1 Standard client/server architecture of iManager N2000

II. Multiple client/server architecture

Chapter 1 System Overview

Figure 1-2 Multiple client/server architecture of iManager N2000

1.1.2 Software Architecture

Chapter 1 System Overview

Java Virtual Machine

Java Virtual Machine

Figure 1-3 Software architecture of iManager N2000

1.2 About Installation

Chapter 1 System Overview

1.2.2 Installation Flow

Figure 1-4 Installation flow

Chapter 1 System Overview

shows the default user names and passwords for pre-installed

SQL Server 2000

1.3 Configuration Requirements