31040812-N2000 Installation Manual

8/10/2019 31040812-N2000 Installation Manual

1/244

HUAWEI

HUAWEI iManager N2000 Fixed NetworkIntegrated Management System

Installation Manual

V200R002


2/244

HUAWEIiManager N2000 Fixed Network IntegratedManagement System

Installation Manual

Manual Version T2-100412-20030924-C-2.20

Product Version V200R002

BOM 31040812

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: [email protected]


3/244

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, andrecommendations in this document don't constitute the warranty of

any kind, express or implied.


4/244

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:

Chapter 1 System Overviewintroduces 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 Windowsdescribes

the installation of SQL Server database system and iManager

N2000 on Windows.


5/244

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:

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 DisplayTerminal Display is in Courier New; message input by theuser via the terminal is in boldface.


6/244

II. GUI conventions

Convention Description

< > Message entered via the terminal is within angle brackets.

[ ]MMIs, menu items, data table and field names are insidesquare brackets [ ].

/Multi-level menus are separated by forward slashes (/). Forexample, [File/Create/Folder].

III. Keyboard operation

Format Description

Press the key with key name expressed with a pointedbracket, e.g. , , , or.

Press the keys concurrently; e.g. means thethree keys should be pressed concurrently.

Press the keys in turn, e.g. means the two keysshould 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 apointed bracket indicates the functional button option, e.g. 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 Description

ClickPress the left button or right button quickly (left button by

default).


7/244

Action Description

Double Click Press the left button twice continuously and quickly.

Drag Press and hold the left button and drag it to a certainposition.

V. Symbols

Eye-catching symbols are also used in this document to highlight the

points worthy of special attention during the operation. They aredefined 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.


8/244

Installation ManualHUAWEI iManager N2000 Fixed NetworkIntegrated Management System Table of Contents

i

Table of Contents

Chapter 1 System Overview .........................................................1-1

1.1Architecture........................................................................1-2

1.1.1 Hardware Architecture.............................................1-2

1.1.2 Software Architecture ..............................................1-4

1.2About Installation................................................................1-5

1.2.1 Installation Mode .....................................................1-5

1.2.2 Installation Flow.......................................................1-6

1.3Configuration Requirements ..............................................1-7

1.3.1 Server ......................................................................1-7

1.3.2 Client .......................................................................1-9

1.4About 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.1Introduction ........................................................................2-1

2.2Preparations for Installation ...............................................2-1

2.3Standalone 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.4Client Installation Mode....................................................2-59


9/244


ii

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.1Introduction ........................................................................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.1Introduction ........................................................................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.1Workstation ........................................................................5-1


10/244


iii

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 FTPTransmission.................................................................5-7

5.2Database 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


11/244


iv

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.3Network 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.1For Solaris ........................................................................ A-1

A.1.1 Disk Partitioning Rules........................................... A-1

A.1.2 Disk Partitioning Plan............................................. A-1

A.2For 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.1For Solaris ........................................................................ B-1


12/244


v

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

Appendix C Uninstall NMS .......................................................... C-1

C.1For Solaris ........................................................................C-1

C.1.1 Uninstalling NMS Server........................................ C-1

C.1.2 Uninstalling NMS Client ......................................... C-2

C.2For 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.1For Solaris ........................................................................D-1

D.1.1 Installing and Uninstalling of Tape Drive ............... D-1

D.1.2 Commands............................................................. D-3

D.2For Windows..................................................................... D-5

D.2.1 Installing and Uninstalling Tape Drive ...................D-5

Appendix E Abbreviations........................................................... E-1


13/244

Installation ManualHUAWEI iManager N2000 Fixed NetworkIntegrated Management System Chapter 1 System Overview

1-1

Chapter 1 System Overview

iManager N2000 is a network management system (NMS)

developed by Huawei, which provides unified management and

maintenance of switching & access products, and data

communication equipment. It implements network elementmanagement 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:


14/244


1-2

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 the standard client/server

architecture, as shown in Figure 1-1.


15/244


1-3

iManager N2000Server

iManager N2000Client 1

ATM/IP

Client NiManager N2000

Client N

Figure 1-1Standard 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:


16/244


1-4

iManager N2000Server 1

iManager N2000Client 1

ATM/IP

iManager N2000Client M

iManager N2000Server N

ATM/IP

iManager N2000Server 2

ATM/IP

Figure 1-2Multiple 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.


17/244


1-5

Server Application

Sybase/SQL Server

Solaris/Windows

Server

Java Virtual Machine

Client Application

Solaris/Windows

Client 1 Client N

Client Application

Java Virtual Machine

Solaris/Windows

Figure 1-3Software 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.


18/244


1-6

1.2.2 Installation Flow

Figure 1-4 shows the installation flow of NMS installation.

Herein, the NMS includes client application and server application.

End

Start

Preparation

Install Database

Install NMS

Install OS

InstallationMode

ClientStandalone

Figure 1-4Installation 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


19/244


1-7

shows the default user names and passwords for pre-installed

operating system and database:

Table 1-1List of default usernames and passwords

System configuration Super username Password

Solaris root rootSolaris+Sybase

Sybase sa sa

Solaris root root

sys change_on_installSolaris+OracleOracle

system manager

Windows 2000 administrator adminWindows 2000 +SQL Server 2000 SQL Server 2000 sa sa

1.3 Configuration Requirements

1.3.1 Server

I. Hardware configuration

Table 1-2iManager N2000 server hardware (Windows)

Configuration Item Typical System Requirements

Host PC server

CPU 1.8G Hz

RAM 1GB

Hard Disk 36GB

CD Drive 48X

Network Adapter Integrated

Sound Card Integrated


20/244


1-8

Table 1-3iManager N2000 server hardware (Solaris)

Configuration Item Typical System Requirments

Workstation Blade 2000

CPU 900MHz

RAM 1GB

Hard Disk 2*73GB

CD Drive DVD



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-4iManager N2000 server software (Windows)

Software Name Software Version

OS Windows 2000 Server

Database Microsoft SQL Server 2000

NMSiManager N2000 Fixed Network Integrated Management SystemServer and Client

Table 1-5iManager N2000 server software (Solaris + Syabse)


OS Solaris 8 for SPARC

Database Sybase 12.0 for Solaris (SPARC)


21/244


1-9


NMS iManager N2000 Fixed Network Integrated Management SystemServer and Client

Table 1-6iManager N2000 server software (Solaris + Oracle)

SoftwareName

Software Version

OS Solaris 8 for SPARCDatabase Oracle 8.1.7.0.0 for Solaris

NMSiManager N2000 Fixed Network Integrated Management System Server andClient

1.3.2 Client

I. Hardware configuration

Table 1-7iManager N2000 client hardware (Windows)


Host Desktop Computer

CPU 1.8GHz

RAM 512MB

Hard Disk 20GB

CD Drive 48XNetwork Adapter Integrated


Either a PC or a workstation can be adopted as the client,

whose typical configuration is as follows:


22/244


1-10

Table 1-8iManager N2000 client hardware (Solaris)


Workstation Blade 150

CPU 500M Hz

RAM 512MB

Hard Disk 20GB

CD Drive Original



II. Software configuration

Table 1-9iManager N2000 client software (Windows)


OS Windows 2000 Professional

NMS iManager N2000 Fixed Network Integrated Management SystemClient

Table 1-10iManager N2000 client software (Solaris)


OS Solaris 8 for SPARC

NMS

iManager N2000 Fixed Network Integrated Management System

Client


23/244


1-11

1.4 About Licensing

1.4.1 Why Licensing Needed

With license, iManager N2000 can be controlled from the

following aspects:

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.


24/244


1-12

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.


25/244

Installation ManualHUAWEI iManager N2000 Fixed NetworkIntegrated Management System

Chapter 2 Installing iManagerN2000 on Solaris + Sybase

2-1

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:

Keyboard


26/244



2-2

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-1Software checklist

Installation Mode Software

Solaris 8 for SPARC Install Disk

Sybase12 Install Disk and LicenseStandalone

iManager N2000 Install Disk and License

Solaris 8 for SPARC Install DiskClient

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.


27/244



2-3

III. Collect information

Before the installation, collect the following information.

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:

Installing operating system

Installing operating system patch

Installing database system

Installing NMS server and client


28/244



2-4

2.3.1 Installing Operating System

Before installation, you can query the Solaris version through

showrevcommand. 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). Forthe 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

(that is, hold on , which is on the upper left of the

Sun keyboard, and press at the same time.).

3) When OK is prompted, enter boot cdrom, press ,

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.


29/244



2-5

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:fpoints 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. [!]


30/244



2-6

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 severalsections. 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 .

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 .

8) The Network Connectivity dialog box appears.

Select Networked: [Yes]. Click .

9) The DHCP dialog box appears.

Select Use DHCP: [No]. Click . To ensure the

stability and security of system running, do not use DHCP.


31/244



2-7

10) The Main Network Interface dialog box appears. Click

.

11) The Host Name dialog box appears. [!]

Enter the host name, like N2000Server.Click .

12) The IP Address dialog box appears. [!]

Input the IP address set to the workstation, e.g. 10.11.106.46.

Click .

13) The Subnets dialog box appears.

System part of a subnet: [Yes]. Click .

14) The Netmask dialog box appears. [!]

Netmask: e.g. 255.255.255.248. Click .

15) The IPv6 dialog box appears.

Enable IPv6: [No]. Click .

16) The Confirm Information dialog box appears.

Click if there is nothing wrong.

17) The Configure Security Policy dialog box appears.

Configure Kerberos security: [No]. Click .

18) The Confirm Information dialog box appears.Click if there is nothing wrong.

19) The Name Service dialog box appears.

Name service: [None]. Click .


Click if there is nothing wrong.

21) The Time Zone dialog box appears.


32/244



2-8

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

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

.

23) The Date and Time dialog box appears. [!]

Set an accurate time, and click .

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 . The Solaris Install Console displays:

System identification is completed.

25) The Solaris Interactive Installation dialog box appears.

Click .


33/244



2-9

Note:

With a new computer on which no operating system is installed, no button is

available, you need click to proceed.

26) The Solaris Interactive Installation dialog box appears.

Click .

27) The Select Geographic Regions dialog box appears.

Select the region. Click .

28) The Select Software dialog box appears.

29) Select software group Entire Distribution plus OEM

support. Click . [!]

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 .

31) The Preserve Data? dialog box appears.

Click .

32) The Automatically Layout File Systems? dialog box

appears.

Click .

33) The File System and Disk Layout dialog box appears.

Click .

34) The Customize Disks dialog box appears. [!]


34/244



2-10

Specify the sizes of different partitions. Please refer to the

partition rules in theAppendix. Click .

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 .

36) The Mount Remote File Systems? dialog box appears.

Click .

37) The Profile dialog box appears.

Click .

38) The prompt dialog box appears.

Click .

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.


35/244



2-11

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 .

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

.

The installation may take 20 minutes.

43) After the installation is finished, the Installation Summary

dialog box appears.

Click .

44) The original CD is automatically ejected, and the Rebootdialog box appears. Click .

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.


36/244



2-12


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


37/244



2-13

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 between61.128.78.0 and 61.128.89.93 can access the workstation. Be sure

to press 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:


38/244



2-14

#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 PartitioningRules (for Solaris)inAppendix.


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:


39/244



2-15

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 LANG [!]

3) 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.


40/244



2-16

Figure 2-1Initial installation interface

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

installation type.


41/244



2-17

Figure 2-2 Installation type dialog box

Click to select Customized Install, and click .

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

installation directory.

Figure 2-3Installation directory selection dialog box


42/244



2-18

The installation directory is /opt/sybase, click .

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

Figure 2-4 Component selection dialog box

Click .



43/244



2-19

Figure 2-5Summary dialog box

Click .


Figure 2-6Directory creation dialog box


44/244



2-20

Click .

9) The installation process appears, as shown in Figure 2-7.

Figure 2-7Installation progress dialog box

10) When the installation is completed, the dialog box appears,

as shown in Figure 2-8.

Figure 2-8Sybase license management dialog box

Click .



45/244



2-21

Figure 2-9License information setting dialog box

Fill in license information, which is available in the license paper

document delivered with Sybase install disk. Click .12) The dialog box appears, as shown in Figure 2-10.

Figure 2-10Sybase installer dialog box

Click .

13) The dialog box appears, as shown in Figure 2-11. [!]


46/244



2-22

Figure 2-11ASE 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 .



47/244



2-23

Figure 2-12Srvbuild - 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 .



48/244



2-24

Figure 2-13Srvbuild - 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 path:

/opt/sybase/data/systemprocs.dat.


49/244



2-25

Sybsystemprocs device size (MB): 100.

Sybsystemprocs database size (MB): 100.

For other parameters, accept the default value.

Click .

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.



50/244



2-26

Figure 2-14Srvbuild - server attribute editor dialog box

Click .

17) Next comes the building of the database system. The

dialog box appears, as shown in Figure 2-15.


51/244



2-27

Figure 2-15Srvbuild status output dialog box


Figure 2-16Srvbuild question dialog box


52/244



2-28

Click .


Figure 2-17Srvbuild status output dialog box

Click .


Figure 2-18Srvbuild question dialog box

Click .


53/244



2-29


Figure 2-19ASE Setup & Configuration dialog box

Click .


Figure 2-20Prompt dialog box


54/244



2-30

Click .

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:


55/244



2-31

#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-21Database 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 ofthe 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/


56/244



2-32

#./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 andthe 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 isrecommended 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>


57/244



2-33

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

null after being set. In addition, the password of sashould 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 wheninstalling 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.


58/244



2-34

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.


59/244



2-35

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.

syb12_ebf11089_install.sh should be executable.

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


60/244



2-36

IX. To further unpack the package, enter the following

command:

#tar xvf Sybase12_0_patch.tar

An ebf11089 directory will be added to /opt/patch.

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:#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.

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:


61/244



2-37

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:


62/244



2-38

1>

enter the following command:

1>sp_who

Run sp_whoto 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 isrunning normally.

Besides, sufficient space should be ensured for installing NMS

server. For space requirement, refer to Disk Partitioning Rules (for

Solaris)inAppendix.

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


63/244



2-39

The initial installation interface appears, as shown in Figure

2-22.

Figure 2-22Initial installation interface

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

the installation license.


64/244



2-40

Figure 2-23Software 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 .

3) The dialog box appears, as shown in Figure 2-24. Select

the installation directory.


65/244



2-41

Figure 2-24Installation directory selection dialog box

The default installation directory is /opt/n2000. Click

to select any other directory. Then click .

Caution:

The installation directory is not allowed to contain blank or illegal characters such as

MBCS (Multi-byte Character Set).


66/244



2-42


Figure 2-25Standalone installation mode selection dialog box

Select the "Standalone as the installation mode of the NMS

Server. Click .

5) The license selection dialog box appears, as shown in

Figure 2-26.


67/244



2-43

Figure 2-26License file selection dialog box

Click to select a normal license file, which should

have been purchased.

By default, a temporary license file is available. Click .

The prompt box appears, as shown in Figure 2-27.


68/244



2-44

Figure 2-27Temporary license prompt

Click .

6) The dialog box similar to Figure 2-28 appears. Select the

functional components to be installed. [!]

Figure 2-28Functional components selection dialog box


69/244



2-45

Check and select the desired functional components. The

component Element Management Essence is mandatory while

others are optional. After the selection, click .

Then the installer checks the component dependency. If the

checking fails, the failure results will pop up. Click 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.

[!]


70/244



2-46

Figure 2-29Database 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

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.


71/244



2-47

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 . [!]

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


72/244



2-48

Caution:

After setting the basic database information, click , 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 Figure2-30.


73/244



2-49

Figure 2-30Installation 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 to start the installation. Otherwise click 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.


74/244



2-50

Figure 2-31Installation 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.


75/244



2-51

Figure 2-32Script execution progress dialog box

After the installation script is executed, the interface appears, as



76/244



2-52

Figure 2-33Script execution completion dialog box

Click .

11) The interface appears, as shown in Figure 2-34. Set the

NMS security for root user.


77/244



2-53

Figure 2-34Installation parameter setting dialog box

Select the check box. Click . [!]

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 Telnetin Chapter 4 Frequently Asked Questions.


78/244



2-54

12) The installation summary appears, as shown in Figure

2-35.

Figure 2-35Installation summary

Click 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 . 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.


79/244



2-55

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 thesystem 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.


80/244



2-56

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-36User login

Enter the password (N2000 by default). Then the system

monitor window appears, as shown in Figure 2-37:


81/244



2-57

Figure 2-37Initial 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.


82/244



2-58

Figure 2-38Server setting

III. Start NMS client

Right click on the CDE, and select [Applications/iManager

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.


83/244



2-59

Figure 2-39Initial interface of NMS Client

2.4 Client Installation Mode

Steps for client installation mode:

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


84/244



2-60

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 to

complete the installation. The installer will automaticallycreate 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.


85/244


Chapter 3 Installing iManagerN2000 on Solaris + Oracle

3-1

Chapter 3 Installing iManager N2000

on Solaris + Oracle

3.1 Introduction

This chapter describes the installation of iManager N2000 on

Solaris operating system + Oracle database, including standalone

installation mode and client installation mode, as well as installation

of Solaris operating system and Oracle.

3.2 Preparations for Installation

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:

Keyboard

Mouse


86/244



3-2

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.

Table 3-1Software checklist

Installation Mode Software

Solaris 8 for SPARC Install Disk and CD-KEY

Oracle 8.1.7.0.0 (or later) Install Disk and LicenseStandalone

iManager N2000 Install Disk and License

Solaris 8 for SPARC Install Disk and CD-KEY

Client iManager N2000 Install Disk

Note:

iManager N2000 software can only be installed locally instead of remotely.


87/244



3-3

III. Collect information

Before the installation, collect the following information.

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) Single server: N2000Server

2) Multiple clients and servers

Server: N2000Server-X

Client: N2000Client-X

Here, X represents the serial number.

3.3 Standalone Installation Mode

Main steps for standalone installation mode:

Installing operating system

Installing operating system patch

Installing database system

Installing NMS server and client


88/244



3-4


Refer to Section 2.3.1.

3.3.2 Installing Operating System Patch

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 theOracle 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 than300MB).

1) Start the workstation and log in as a root user (super user).

2) Use the admintool to create the user group oinstall.


89/244



3-5

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


90/244



3-6

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 vicommand 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


91/244



3-7

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-1Error dialog box

7) Enter the installation interface, as sho

31040812-N2000 Installation Manual

Documents

Transcript of 31040812-N2000 Installation Manual