ZTE Netnumen N31 User

NetNumen N31 (V4.2.
0)
Network Management System (General)
User Manual (Volume I)
Version 4.2.0
ZTE CORPORATION
ZTE Plaza, Keji Road South,
Hi-Tech Industrial Park,
Nanshan District, Shenzhen,
P. R. China
518057
Tel: (86) 755 26771900 800-9830-9830
Fax: (86) 755 26772236
URL: http://support.zte.com.cn
E-mail: doc@zte.com.cn
LEGAL INFORMATION
Copyright © 2006 ZTE CORPORATION.
The contents of this document are protected by copyright laws and international treaties. Any reproduction or
distribution of this document or any portion of this document, in any form by any means, without the prior written
consent of ZTE CORPORATION is prohibited. Additionally, the contents of this document are protected by
contractual confidentiality obligations.
All company, brand and product names are trade or service marks, or registered trade or service marks, of ZTE
CORPORATION or of their respective owners.
This document is provided “as is”, and all express, implied, or statutory warranties, representations or conditions
are disclaimed, including without limitation any implied warranty of merchantability, fitness for a particular purpose,
title or non-infringement. ZTE CORPORATION and its licensors shall not be liable for damages resulting from the
use of or reliance on the information contained herein.
ZTE CORPORATION or its licensors may have current or pending intellectual property rights or applications
covering the subject matter of this document. Except as expressly provided in any written license between ZTE
CORPORATION and its licensee, the user of this document shall not acquire any license to the subject matter
herein.
ZTE CORPORATION reserves the right to upgrade or make technical change to this product without further notice.
Users may visit ZTE technical support website http://ensupport.zte.com.cn to inquire related information.
The ultimate right to interpret this product resides in ZTE CORPORATION.
Revision History
Date Revision No. Serial No. Reason for Issue

Feb. 10, 2007 R1.0 Sjzl20072644 First edition
ZTE CORPORATION
Values Your Comments & Suggestions!
Your opinion is of great value and will help us improve the quality of our product
documentation and offer better services to our customers.
Please fax to (86) 755-26772236 or mail to Documentation R&D Department, ZTE
CORPORATION, ZTE Plaza, A Wing, Keji Road South, Hi-Tech Industrial Park,
Shenzhen, P. R. China 518057.
Thank you for your cooperation!
Document
NetNumen N31 (V4.2.0) Network Management System (General) User Manual (Volume I)
Name
Document Revision
Product Version V4.2.0 R1.0
Number
Equipment
Serial No. Sjzl20072644
Installation Date
Presentation:
(Introductions, Procedures, Illustrations, Completeness, Level of Detail, Organization,
Appearance)
Good Fair Average Poor Bad N/A
Your evaluation Accessibility:

of this
(Contents, Index, Headings, Numbering, Glossary)
documentation
Intelligibility:
(Language, Vocabulary, Readability & Clarity, Technical Accuracy, Content)
Please check the suggestions which you feel can improve this documentation:
Improve the overview/introduction Make it more concise/brief
Improve the Contents Add more step-by-step procedures/tutorials
Improve the organization Add more troubleshooting information
Include more figures Make it less technical
Your Add more examples Add more/better quick reference aids
suggestions for Add more detail Improve the index
improvement of
this Other suggestions
documentation __________________________________________________________________________
__________________________________________________________________________
__________________________________________________________________________
__________________________________________________________________________
__________________________________________________________________________
# Please feel free to write any comments on an attached sheet.
If you wish to be contacted regarding your comments, please complete the following:
Name Company
Postcode Address
Telephone E-mail
This page is intentionally blank.
Contents
About This Manual ............................................................ i

Purpose ................................................................................ i
Intended Audience ................................................................. i
Prerequisite Skill and Knowledge .............................................. i
What Is in This Manual ........................................................... i
Related Documentation.......................................................... ii
Conventions ......................................................................... ii
How to Get in Touch............................................................. iii
Declaration of RoHS Compliance..................................... v
Chapter 1.......................................................................... 1
Installation Overview ...................................................... 1

Network Analysis ............................................................1
Software Requirements....................................................2
Hardware Requirements...................................................2
Single System Requirements for Windows ................................ 3
Single System Requirements for UNIX ..................................... 4
Dual System Requirements for Windows................................... 6
Dual System Requirements for UNIX........................................ 7
Hardware Firewall ................................................................. 9
Chapter 2........................................................................ 11
Database Installation .................................................... 11

Oracle Database Installation ........................................... 11
Hardware Requirements....................................................... 11
Software Requirements........................................................ 12
Installation Preparation........................................................ 13
Installing Oracle 9i .............................................................. 20
Oracle 9i Post Installation Check ........................................... 22
Configuring Database .......................................................... 23
Installing Oracle9i Service Pack............................................. 25
SQL Server Database Installation .................................... 31
Chapter 3........................................................................ 41
NMS Installation ............................................................ 41

Overview ..................................................................... 41
Installing NMS for Windows ............................................ 42
Installing NMS Client and Server ...........................................42
Installing NMS Client............................................................44
Configuring NMS Config Center..............................................47
Installing NMS for UNIX ................................................. 78
Installing NMS Client and Server ...........................................78
Installing NMS Client............................................................82
Configuring UNIX NMS Config Center .....................................85
Chapter 4......................................................................117
VCS4.3 for Windows ....................................................117

Overview ................................................................... 117
System Requirements.................................................. 118
Installation Preparations .............................................. 118
Hardware ......................................................................... 119
Hardware Connection......................................................... 119
Disk Array Connections ...................................................... 119
Installing Operating System.......................................... 121
Dividing Disk Array ............................................................ 122
Configuring Network .......................................................... 122
Configuring Domain ........................................................... 124
Installing VCS HA Software........................................... 131
Creating Disk Array Logical Partition..................................... 139
VCS Software Configuration - Create Cluster ......................... 146
Installing Sqlserver Database........................................ 154
Configure SQL Server Startup Type...................................... 155
Installing NMS .................................................................. 156
VCS Software Configuration – Create SqlServer Resource Group
...................................................................................... 157
VCS Software Configuration ................................................ 162
Test Dual System Hot Backup Software .......................... 182
Test Single System............................................................ 182
Test Dual Systems............................................................. 183
Test Rules for Local Dual Hot Backup System ........................ 183
Chapter 5...................................................................... 185
VCS4.0 for Unix ............................................................ 185

Overview ................................................................... 185
Dual Hot Backup Configuration Requirements........................ 185
System Installation ..................................................... 187
Solaris9 Operating System Installation ................................. 187
Disk Array Partition ........................................................... 191
Setting Network................................................................ 200
Installing Oracle Database.................................................. 203
Installing VCS4.0 .............................................................. 208
Configuring VCS System .............................................. 227
Starting VCS Cluster Manager ............................................. 227
Adding Oracle Resource Group ............................................ 229
Adding NM Resource Group ................................................ 237
NM Dual System Test Rules .......................................... 251
System Security ......................................................... 252
Appendix A ................................................................... 255
Handling Common VCS Problems in UNIX..................255

Modifying VCS Cluster Administrator Password ................ 255
Checking Heartbeat ..................................................... 256
Checking Running Status.............................................. 256
Starting VCS in Abnormal Status ................................... 256
Failed to Start Oracle Database after Switchover ............. 257
Faulty VCS Resource Group or Resource ......................... 258
Uninstalling VCS ......................................................... 259
Appendix B ................................................................... 261
Common UNIX Operation Commands.........................261

File System Operation Commands ................................. 261
System Commands ..................................................... 263
Pack/Unpack Command ............................................... 264
Important System Files ................................................ 264
Appendix C ................................................................... 267
Common Oracle Database Operations ........................267

Starting Oracle8i Database Service ................................ 267
Starting Oracle9i Database Service ................................ 268
Viewing Oracle Service Name........................................ 268
Viewing Database Table Space Name ............................. 268
Viewing Database User ................................................ 269
Oracle Database Backup .............................................. 269
Restoring Oracle Database ........................................... 269
Appendix D...................................................................271
Abbreviations ...............................................................271
Figures..........................................................................273
Tables ...........................................................................281
Index ............................................................................283
About This Manual
Purpose
This manual provides user systematic guidelines and procedures
for the operations of NetNumen N31 (V4.2.0) Network
Management System (General).
Intended Audience
This manual is intended for engineers and technicians who
perform operation activities on NetNumen N31 (V4.2.0) Network
Management System (General).
Prerequisite Skill and Knowledge

To use this manual effectively, users should have a general
understanding of Network Management System. User’s
knowledge in the following is helpful:
User interfaces on Network Management System (NMS)
Operating procedures on NMS
What Is in This Manual

This manual contains the following chapters:
TABLE 1 − CHAPTER SUMMARY
Chapter Summary
Chapter 1, Overview Introduces overall information of NMS,
requirements, and installation.
Chapter 2, Database Describes installation and configuration of
Installation oracle 9i for UNIX.
Chapter 3, NMS Describes installation and configuration of
Installation NMS client and server.
Confidential and Proprietary Information of ZTE CORPORATION i

Chapter Summary
Chapter 4, NM Dual Hot Describes the installation of NetNumen
Backup System N31 (V4.2.0) dual hot backup system
Installation (VCS4.3 for VCS4.3 in Windows operating system.
Windows)
Chapter 5, NM Dual Hot Describes the installation of NetNumen
Backup System N31 (V4.2.0) dual hot backup system
Installation (VCS4.0 for VCS4.0 in Solaris operating system
Unix)
Related Documentation
The following documentation is related to this manual:
NetNumen N31 (V4.2.0) Network Management System (Man-
Machine Interface)
NetNumen N31 (V4.2.0) User Manual
Conventions
Typographical ZTE documents employ the following typographical conventions.
Conventions
TABLE 2 − TYPOGRAPHIC AL CONVENTIONS
Typeface Meaning
Italics References to other Manuals and documents.
“Quotes” Links on screens.
Bold Menus, menu options, function names, input
fields, radio button names, check boxes, drop-
down lists, dialog box names, window names.
CAPS Keys on the keyboard and buttons on screens
and company name.
Constant width Text that you type, program code, files and
directory names, and function names.
[] Optional parameters.
{} Mandatory parameters.
| Select one of the parameters that are delimited
by it.
Note: Provides additional information about a
certain topic.
Checkpoint: Indicates that a particular step needs
to be checked before proceeding further.
Tip: Indicates a suggestion or hint to make things
easier or more productive for the reader.
ii Confidential and Proprietary Information of ZTE CORPORATION

About this Manual
Mouse TABLE 3 − MOUSE OPERATION CONVENTIONS

Operation
Typeface Meaning
Conventions
Click Refers to clicking the primary mouse button (usually
the left mouse button) once.
Double-click Refers to quickly clicking the primary mouse button
(usually the left mouse button) twice.
Right-click Refers to clicking the secondary mouse button
(usually the right mouse button) once.
Drag Refers to pressing and holding a mouse button and
moving the mouse.
How to Get in Touch

The following sections provide information on how to obtain
support for the documentation and the software.
Customer If you have problems, questions, comments, or suggestions
Support regarding your product, contact us by e-mail at
support@zte.com.cn. You can also call our customer support
center at (86) 755 26771900 and (86) 800-9830-9830.
Documentation ZTE welcomes your comments and suggestions on the quality
Support and usefulness of this document. For further questions,
comments, or suggestions on the documentation, you can
contact us by e-mail at doc@zte.com.cn; or you can fax your
comments and suggestions to (86) 755 26772236. You can also
browse our website at http://support.zte.com.cn, which contains
various interesting subjects like documentation, knowledge base,
forum and service request.
Confidential and Proprietary Information of ZTE CORPORATION iii

iv Confidential and Proprietary Information of ZTE CORPORATION

Declaration of RoHS
Compliance
To minimize the environmental impact and take more

responsibility to the earth we live, this document shall serve as
formal declaration that NetNumen N31 (V4.2.0) Network
Management System (General) manufactured by ZTE
CORPORATION are in compliance with the Directive 2002/95/EC
of the European Parliament - RoHS (Restriction of Hazardous
Substances) with respect to the following substances:
Lead (Pb)
Mercury (Hg)
Cadmium (Cd)
Hexavalent Chromium (Cr (VI))
PolyBrominated Biphenyls (PBB’s)
PolyBrominated Diphenyl Ethers (PBDE’s)
…
NetNumen N31 (V4.2.0) Network Management System

(General) manufactured by ZTE CORPORATION meet the
requirements of EU 2002/95/EC; however, some assemblies are
customized to client specifications. Addition of specialized,
customer-specified materials or processes which do not meet the
requirements of EU 2002/95/EC may negate RoHS compliance of
the assembly. To guarantee compliance of the assembly, the
need for compliant product must be communicated to ZTE
CORPORATION in written form.
This declaration is issued based on our current level of
knowledge. Since conditions of use are outside our control, ZTE
CORPORATION makes no warranties, express or implied, and
assumes no liability in connection with the use of this
information.
Confidential and Proprietary Information of ZTE CORPORATION v

vi Confidential and Proprietary Information of ZTE CORPORATION

Chapter 1
Installation Overview
This chapter covers the following topics:

Network Analysis
Software Requirements
Hardware Requirements
Network Analysis
Network NetNumen N31 (V4.2.0) supports different capacity networks.
Selection Select the appropriate Network Management System (NMS) type
according to number of Network Elements (NE) present on the
network.
The four different types of networks are listed in Table 4.
TABLE 4 – NETWORK TYPES
Type NE Capacity
NetNumenN31V4-EXX-S-1.0 (Small Scale < 300
Networks)
NetNumenN31V4-EXX-M-1.0 (Medium Scale 300 ~ 800
Networks)
NetNumenN31V4-EXX-L-1.0 (Large Scale 800 ~ 1500
Networks)
NetNumenN31V4-EXX-U-1.0 (Very Large Scale 1500 ~ 3000
Networks)
Network An equivalent NE stands for one managed object in NMS. The

Element NMS assigns the different functions to each managed object,
which acts as one unit. Different types of device have different
functions.
An equivalent NE example is listed in Table 5.
Confidential and Proprietary Information of ZTE CORPORATION 1

TABLE 5 − EQUIVALENT NE EXAMPLE
NE Equivalent NE
MSAG 5200 One Equivalent NE
Platform NetNumen (V 4.2.0) NMS supports MS Windows and UNIX
Support System platforms.
Windows MS Windows requirements are:

Requirements
MS Windows (2000, 2003 or XP) with latest service pack
SQL Server 2000 Database, SQL Server 2005 Database
Latest SQL server Database Patch (SQL Server SP4)
Sun Solaris Solaris requirements are:

Requirements
Sun Solaris (9 or above) with latest service pack
Oracle 9i database
Latest Oracle Database Patch
Note: Install SQL Server 2000, 2005 or Oracle 9i database prior

to NMS installation.
Platforms MS Windows and Sun Solaris operating systems are normally
used as platforms for NetNumen N31 (V4.2.0) NMS. These
operating systems need different hardware requirements on
server and client machines.
Requirements The following are the hardware requirements for NMS
installation:
Single System Requirements for Windows
Single System Requirements for UNIX
Dual System Requirements for Windows
Dual System Requirements for UNIX
Hardware Firewall
2 Confidential and Proprietary Information of ZTE CORPORATION

Chapter 1 Installation Overview
Single System Requirements for

Windows
Requirements Minimum requirements for windows single system platform for
NetNumen N31 (V4.2.0) are as follows:
Hardware Platform
Outsourcing Software
Accessories
Hardware Minimum requirements for the hardware platform are listed in
Platform Table 6.
TABLE 6 − NT SERVER CONFIGURATION
Name Configuration Requirements

Server Small One server recommended configuration: 1
Xeon 2.8G/2G/2﹡73G/, 2*10/100/1000M
Ethernet ports
Medium One server recommended configuration: 2
﹡ Xeon/4G/2 ﹡ 73G/, 2*10/100/1000M
Ethernet ports)
Large One server recommended configuration: 2
﹡ Xeon/6G/2 ﹡ 73G/, 2*10/100/1000M
Ethernet ports)
Huge One server recommended configuration: 4
﹡ Xeon or more /8G/2﹡73G/,
2*10/100/1000M Ethernet ports)
Client Number depends on the central office requirements
Interface Number: 1; it needs to provide 1 suit when SS1b,
Computer 9000 are connected to upper-level NM via CLI.
Configuration is the same as that for client.
Note: Server configuration is recommended therefore

select larger configuration depends upon actual (2﹡73G hard
disk as RAID)
Outsourcing Minimum requirements for the outsourcing software are listed in

Software Table 7.
TABLE 7 − OUTSOURCING SOFTWARE

SQL Server 2000 Number: 1
Standard Version


Windows Server 2003 Number: 1
Standard Version
Windows XP Number of packages must be equal to
number of client machines and interface
computer
Anti-virus Software Enterprise Version
Accessories Minimum requirements for the accessories are listed in Table 8.
TABLE 8 − ACCESSORIES

Server Shelf Configure the server on shelf if needed
Layer-2 Switch Number: 1; template does not supply
Layer- 2 switch; directly transfer it from
Data Division if necessary. Recommended
type: 2818S-LE AC power supply
Hardware Firewall Number: 1; selective; for option
instructions, refer “1.3.3 Hardware Firewall
Instruction”. The current type is: Juniper
SSG-520-001
Alarm Warning Box Number: 1
Single System Requirements for

UNIX
Requirements Minimum requirements for UNIX single system platform for
Hardware Platform
Accessories
Do not configure UNIX server unless central office requirements
are not completed.
Platform Table 9.
TABLE 9 − HARDWARE PLATFORM

Server Small Number: 1; SUN V240 (UltraSPARC IIIi
CPU 1.34 G/2 G memory/ 2*73 G hard
disk/ 4* Kilomega Ethernet port/ Solaris
9)


Medium Number: 1; SUN V240 (UltraSPARC IIIi
CPU 2*1.5G/ 4G memory/ 2*73 G hard
disk/ 4*Kilomega Ethernet port/ Solaris
9)
Large Number: 1; SUN V4901(UltraSPARC IV
CPU 2*1.35 G CPU/8 G memory/ 2*146G
harddisk/4* Kilomega Ethernet port/
Solaris 9)
Huge Number: 1; SUN V4901(UltraSPARC IV
CPU 4*1.35 G CPU/16 G memory/
2*146G optical interface harddisk/4*
Kilomega Ethernet port/ Solaris 9)
Client The number depends on central office
requirements
Interface Number: 1; selective, it is required to provide one
Computer suit when SS1b, 9000 are connected to upper-level
NM via CLI, its configuration is the same as for
client.
Outsourcing Minimum requirements for outsourcing software are listed in

Software Table 10.

Oracle 9i EE 9.2 Select one single-system CPU, two single-system
CPU, and four single-system CPU according to CPU
quantities.
Operating SUN built-in
System
Windows XP Number of packages equal to number of clients
and interface computer
Anti-virus Number: 1
Software

Layer-2 Switch Number: 1
Hardware Firewall Number: 1; selective
Instructions To improve system reliability and stability, NM server and NM

client must be installed in different computer platforms.

It demands higher and better hardware configuration if both

server and client are configured on the same computer.
Dual System Requirements for

Windows
Requirements Minimum requirements for windows dual system platform for
Hardware Platform
Accessories
Platform Table 12.
TABLE 12 − HARDW ARE PLATFORM
Name Configuration Instruction

2 Servers + 1 Disk Medium 2 Servers (Single system
Array recommended configuration +
disk array (5﹡73G)
Large 2 Servers (Single system

recommended configuration +
Huge 2 Servers (Single system

recommended configuration +
Network Card It needs four network interfaces while

configuring dual system. Normally, the server
network card is not enough.
Client Number of clients depends on central office
requirements
Interface Computer Number: 1; selective, it needs to provide one
suit when SS1b, 9000 are connected to
upper-level NM via CLI, its configuration is
the same as for client.
Outsourcing Minimum requirements for the outsourcing are listed in Table 13.
Software

SQL Server 2000, 2 SQL Server 2000, Standard version
suits
Windows Server Windows Server 2003, Standard version
2003


Windows XP Number of packages must be equal to
number of clients and interface computer

Layer-2 Switch Number: 1; template does not supply Layer-
2 switch; please directly transfer it from
Data Division if necessary. Recommended
type: 2818S-LE AC power supply
Hardware Firewall Number: 1; selective
Alarm Warning Box Depends on the central office demands
Dual System Requirements for UNIX

Requirements Minimum requirements for windows dual system platform for
Hardware Platform
Accessories
Platform Table 15.
TABLE 15 − HARDW ARE PLATFORM

2 Small Small 2* SUN V240 (Single system
Capacity recommended configuration:
Machine + 1 UltraSPARC IIIi CPU 1.34 G/2 G
Disk Array Memory/ 2*73 G hard disk/
4*Kilomega Ethernet port/ Solaris 9) +
1 Disk array
Medium 2* SUN V240 (Single system
recommended configuration:
UltraSPARC IIIi CPU 2*1.5G CPU/ 2G
Memory/ 2*73 G hard disk/ 4*
Kilomega Ethernet port/ Solaris 9) + 1
Disk array


Large 2* SUN V490 (Single system
UltraSPARC 1V CPU 2*1.35G CPU/ 8G
Memory/ 2*146G hard disk/ 4*
Kilomega Ethernet port/ Solaris 9) + 1
Disk array
Huge 2* SUN V490 (Single system
UltraSPARC 1V CPU 4*1.35G CPU/
16G Memory/ 2*146G optical interface
hard disk/ 4* Kilomega Ethernet port/
Solaris 9) + 1 Disk array
Client The number depends on central office requirements
Interface Number: 1; selective, it needs to provide 1 suit
computer when SS1b, 9000 are connected to upper-level NM
via CLI, its configuration is the same as for client.
Outsourcing Minimum requirements for the outsourcing are listed in Table

Software 16.
Name Configurations
Oracle 9i EE Select 2 dual-systems CPU, 4 single-systems CPU
9.2 and 8 dual-systems CPU according to CPU
quantities.
Operating SUN built-in
System
Windows XP Quantities equal to Client quantity + Interface
computer
Local VCS Small/ Medium( inner/out country) : local VCS
Software software for SUN 1A server, Number: 1
Large/ Huge (inner/out country): local VCS
software for SUN 1A server, Number: 1
Anti-virus Number: 2
Software
Name Configurations
Server Shelf Configure server on shelf if needed
Layer-2 Switch Number: 1
Hardware Number: 1; selective
Firewall

Hardware Firewall
Description Common firewalls are Cisco PIX515E, 525 or Juniper
Netscreen25, 50, 204, 208.
The requirements for the firewall are listed in Table 18.
TABLE 18 − FIREWALL
Cisco Juniper
Products
Items
515E 525 25 50 204 208
Throughput 188 M 360 M 100 M 170 M 400 M 550 M

(Dupl (Duple
ex) x)
Talk Quantity 130,0 380,0 32,000 64,00 128,00 128,00
00 00 0 0 0
Interface 2+4 2+6 4 4 4 8
Quantity FE/GE FE/GE
Security Failov Failov HALlite Master Master Master

Networking er er / / /
Slave Slave, Slave,
Master Master
/Maste /Maste
r r,
Master
/Maste
r
overall
networ
k
Instructions The hardware firewall instructions are described as follows:

PIX firewall with UR numbering is allowed to support the
maximum interfaces and memory. UR license supports
redundant hot backup and minimize the network down time.
PIX firewall with R numbering is limited to support interface
quantities and memory. It does not support redundant
networking.
PIX firewall with FO numbering linked with another firewall
with UR license provides hot redundant backup structure. FO
license provides fault tolerance function based on status,
which improves network structure performance.
PIX firewall with UR and FO numbering composed of failover
networking need the same type (515E or 525) and same
hardware configuration. Security protection between soft
switch and bearer network is suggested.

Note: R and FO numbering cannot work together
PIX firewall with R and UR numbering can be used separately.

PIX firewall with R and UR numbering are normally used for
security protection between soft switch and management
network such as DCN.
Juniper firewall port is consolidated. It usually adopts same
equipment to compose master/slave, master/master,
master/master safe full networking mode.
NOTE: N-25 networking mode only provides synchronized
configuration instead of synchronized talking and tunnel.
The dual system firewall adopts CISCO PIX to networking as
failover mode. It also can adopt two Juniper firewalls to build
up master/slave networking mode.
The single system firewall can use Cisco firewall with UR and
R numbering, or Juniper firewall. Cisco firewall usually
configures two Ethernet interfaces and increases the number
of interfaces as required.
Juniper firewall usually configures fastness port; therefore, it
only demands to select type number.

Chapter 2
Database Installation

Oracle Database Installation
SQL Server Database Installation
Oracle Database Installation

This section describes the hardware and software requirements
for Oracle 9i installation and configuration on Sun Solaris
operating system.
This section includes the following:
Installation Preparation
Installing Oracle 9i
Configuring Database
Installing Oracle 9i Service Pack
System Minimum system hardware requirements are as follows:
Requirements
CPU: SUN Blade1000 with a single CPU
RAM: 1GB
Hard disk: 70 GB
Swap Partition Minimum space for SWAP partition must be at least twice of the
physical memory.
Hard Disk Size Minimum free space for the system must be 10 GB.
Minimum free space for the user must be 60 GB.

Command The command used to check the available disk space for user
Description partition is shown in Figure 1.
FIGURE 1 – SPACE FOR USER P ARTITION
Operating Minimum software version must be Solaris 9 or higher.
System
Use the following command to view operating system
information:
# uname -a
SunOS nm1000 5.9 Generic_118558-38 sun4u sparc SUNW,
Sun-Blade-1000
PATCH Download and install latest patch “9_Recommend.zip” from
http://sunsolve.sun.com
Solaris must include the following core patches:
SUNWarc
SUNWbtool
SUNWhea
SUNWlibms
SUNWsprot
SUNWtoo
Use the following commands to view installed system PATCH:
# pkginfo –i [package_name]
system SUNWzlib The Zip compression library
system SUNWzlibx The Info-Zip compression library （64-bit）
system SUNWzsh Z shell （zsh）

Chapter 2 Database Installation
system TSBWvplr Toshiba platform links

system TSBWvplu Toshiba usr/platform links
system TSIpgx PGX32 (Raptor GFX) System Software Device Driver
Application TSIpgxw PGX32 （Raptor GFX） X-Window System Support
system TSIpgxx PGX32 （Raptor GFX） System Software/Device Driver （64-bit）
system TWSvplr TWS platform links

system TWSvplu TWS usr/platform links
Executive Files Make sure that the following execution files exist in the directory
/usr/ccs/bin:
Make
Ar
Ld
nm
X-Window The following command is used to verify X-Window system
System Run running status is normal.
# xclock
A graphic clock interface pop up implies a normal X-Windows
system. If no graphic clock interface pops up, it means an
abnormal X-Windows.
Installation Preparation
Purpose To provides pre-installation guidelines for the user.
Preliminary None
Setup
Steps To install oracle database, perform following pre-installation

steps:
1. Run Login as a ‘root’ user.
2. Click Files and Open Terminal in File Manager window as
shown in Figure 1 the Terminal window appears with
command prompt # sign. Input commands after # sign and
press enter key to execute. #su - root command is used to
switch the root user and enter password if prompted.
3. Configure UNIX core parameters for Oracle 9i.
i. Right click on desktop short cut menu appears, click
Folder and check File Manager – Home. File Manger
window appears as shown in Figure 6. Open etc folder
then run System file.
ii. Following are the additions or modifications in UNIX
system core parameters for Oracle 9i:
set semsys:seminfo_semmni=100
set semsys:seminfo_semmns=1024

set semsys:seminfo_semmsl=256
set shmsys:shminfo_shmmax=4294967295
set shmsys:shminfo_shmmin=1
set shmsys:shminfo_shmmni=100
set shmsys:shminfo_shmseg=10
iii. Save and close the file.
4. Create Oracle group.
i. Add three user groups ‘install’, ‘apchadm’ and ‘dba’ in
the system administration tools.
ii. Use the following command to open system
administration tools in the Terminal window:
# admintool
iii. From the main menu, click Browse and select the Group
from admin tool windows. Admintool: Group window
appears as shown in Figure 2.
FIGURE 2 – ADMIN TOOL: GROUPS
iv. From the main menu of Admin Tool: Group, click Edit
and Add, Admintool: Add Group window appears as
shown in Figure 3. Assign Group Name, Group ID,
Member List and click OK.

FIGURE 3 – ADMINTOOL: ADD GROUP
5. Create Oracle user

i. Add users oracle, apache and adm in the system
administration tools.
ii. Add a user oracle used for oracle database. From the
main menu of Admin Tool: Users, click Edit and Add.
Admintool: User window appears as shown in Figure 4.
FIGURE 4 – ADMINTOOL: ADD USER WINDOW

iii. Configure the following parameters (use the system

default values, if the following contents are not listed):
User Name: oracle
Primary Group: install
Secondary Groups: dba
Login Shell: Bourne
Password: Select Normal Password from Password
drop down list (Input the oracle user password in both
fields, oracle is recommended).
HOME DIRECTORY: Home directory route is the oracle
database required for installation. It can change
according to the different user.
Path: /export/home/Oracle (/export/home is supposed
to be the system user partition here)
iv. Add a user apache. It is used for oracle HTTP server.
From the main menu of Admin Tool: Users, click Edit
and Add, Admintool: User window appears as shown in
Figure 5.

FIGURE 5 – ADMINTOOL: ADD USER WINDOW
v. Configure the following parameters (use the system

default values, if the following contents are not listed):
User Name: apache
Primary Group: install
Secondary Groups: apchadm
Login Shell: Bourne
Password: Select Normal Password from Password
drop down list (Input the oracle user password in both
fields, Apache is recommended).
HOME DIRECTORY: Home directory route is the oracle
database required for installation. It can change
according to the different user.

Path: /export/home/apache (/export/home is supposed

to be the system user partition here.)
vi. Click OK to finish the operation.
Note: Make sure that installation path is under system

user’s partition directory. It is forbidden to install it under UNIX
system directory such as root directory/usr/var/tmp.
6. Operation for oracle user

i. Switch the previous root user to oracle user. Input $su–
oracle command in the Terminal. If it is successful, set
the environment variables of oracle user.
ii. Right click on desktop shortcut, click Files and File
Manager. File Manager window appears as shown in
Figure 6. Open the directory /export/home/oracle. Click
View and check Show Hidden Objects from the main
menu.
FIGURE 6 − SHOW HIDDEN OBJECTS
iii. Open the .profile file. Text Editor - .profile window


FIGURE 7 – TEXT EDITOR – .PROFILE WINDOW
iv. Configure the following environment variables if required:

umask 022;export umask
DISPLAY=Workstation_name:0.0;export DISPLAY
(Workstation_name is the machine name. If the
machine name is NM9000, DISPLAY=NM9000:0.0)
ORACLE_TERM=vt100; export ORACLE_TERM
ORACLE_BASE=/export/home/oracle;export
ORACLE_BASE
ORACLE_HOME=/export/home/oracle/product/9.2.0;
export RACLE_HOME (Set the installation path of
Oracle database system program.)
ORACLE_SID=uep; export ORACLE_SID (Set the
service name of Oracle database as uep.)
ORA_NLS33=$ORACLE_HOME/ocommon/nls/admin/data;
export ORA_NLS33 (Set the output character group
of Oracle database.)
LD_LIBRARY_PATH=$ORACLE_HOME/lib:/lib:usr/lib:$L
D_LIBRARY_PATH
export LD_LIBRARY_PATH
NLS_LANG=american_america.ZHS16GBK; export
NLS_LANG (Set the output character group of
Oracle database.)
TMPDIR=/tmp; export TMPDIR
PATH=$ORACLE_HOME/bin:/usr/ccs/bin:/usr/bin:/usr
/ucb:etc:/usr/openwin/bin:/usr/local/bin:
export PATH

Note: Information in small brackets () is only for user

comments; should not be modified in the file.
7. Switch back to the root user to finish the operations.

8. Use the following command in Terminal window to restart
the system:
# init 6
9. Login again as root user after system restarts.

END OF STEPS
Result Pre-installation steps are completed successfully.
Installing Oracle 9i
Purpose To install Oracle database.
Preliminary None
Steps
Steps To install Oracle 9.2.0.7 for Solaris, perform the following steps:
1. Execute runInstaller.sh file from the path
/export/home/oracle to start installation wizard. The
installation process begins automatically as shown in Figure
8.
FIGURE 8 − RUN WINDOW
2. The installation wizard prompts to extract all the zip files as

shown in Figure 9. Enter y to continue the installation
process.

FIGURE 9 − PROMPT WINDOW
3. The installation wizard starts extracting all the installation

files as shown in Figure 10.
FIGURE 10 − EXTRACTING FILES
Note: Wait for some time. Usually it takes few minutes to extract
all the installation files.
4. Oracle installation is finished successfully as shown in Figure

11.

FIGURE 11 − INSTALL ATION FINISHED
END OF STEPS
Results Oracle 9.2.0.7 database is installed successfully.
Oracle 9i Post Installation Check

Purpose To check Oracle database is running properly.
Preliminary None
Steps
Steps To check whether Oracle database is running properly, perform

the following steps:
1. Execute the following command to switch to Oracle user as

shown in Figure 12. The prompt changes to $.
#su - oracle
2. Execute the following command to start SQL Plus. The
prompt changes to SQL>.
$sqlplus /nolog
3. Execute the following command to connect to idle instance.
Enter user name and password.
SQL>connect as sysdba.
4. Execute the following command to start Oracle instance
process.
SQL>startup
5. Execute the following command to disconnect from oracle 9i.
SQL>exit

FIGURE 12 – TERMINAL WINDOW
6. Execute the following commands to start listening process as

shown in Figure 13.
$lsnrctl
LSNRCTL>start
FIGURE 13 – LISTENING PROCESS WINDOW
END OF STEPS
Results Oracle 9i database is running properly.
Configuring Database
Purpose To configure database.
Preliminary None
Steps
Steps To configure database, perform the following steps:

1. Confirm and modify parameters before executing oracle
scripts.

2. Check time format i-e YYYY-MM-DD HH24: MI: SS. Check

nls_date_format properties in the init.ora file to confirm. If
this parameter is not configured or format is wrong, perform
following steps:
For oracle8i:
i. Shut down the database first. Modify these two files:
<oracle_home>\admin\<sid>\pfile\init.orat and
<oracle_home>\ora817\sysman\
ifiles\def_<sid>_<ipaddr>.ora
ii. Add n l s _ d a t e _ f o r m a t = ' Y Y Y Y - M M - D D H H 2 4 : M I : S S '
in the files.
iii. Save the files and reboot the database.
For oracle9i:
i. Switch to ‘oracle’ user: ＃su – oracle
ii. Start SQL*PLUS: $sqlplus /nolog
iii. Log on as ‘sysdba’: SQL>connect system/manager as
sysdba
iv. Shutdown the database: SQL>shutdown
v. Export parameter file $ORACLE_HOME/dbs/inituep.ora (if
the export fails, delete the existing
$ORACLE_HOME/dbs/inituep.ora): SQL>create pfile
from spfile
vi. Add a line in $ORACLE_HOME/dbs/inituep.ora:
*.nls_date_format = 'YYYY-MM-DD HH24:MI:SS'
vii. Import into $ORACLE_HOME/dbs/spfileuep.ora (if the

import fails, shutdown the database and delete the
existing $ORACLE_HOME/dbs/spfileuep.ora)
viii.Create profile as SQL>create spfile from pfile
ix. Restart the database: SQL>startup and verify if
modification is correct:
SQL>show parameters nls_date_format
NAME TYPE VALUE
------------------------------------------------
nls_date_format string YYYY-MM-DD
HH24:MI:SS
3. Confirm that oracle’s character set is ZHS116GBK
i. Modify two parameters in ‘props$’ table of the ‘sys’
scheme:
NLS_CHARACTERSET= ZHS16GBK
NLS_NCHAR_CHARACTERSET=ZHS16GBK
ii. Shutdown the database and restart

4. For oracle8i, set ‘compatible’ in the startup scripts (init.ora

and initXXX.ora) to ‘8.1.0’. Otherwise, problem may occur.
END OF STEPS
Results Database is configured successfully.
Installing Oracle9i Service Pack

Purpose To install oracle database patch. This installation takes Oracle
9.2.0.7 version as an example.
Important 1. Confirm patches
Cautious Items
i. Oracle 9.2.0.7 database update patch packet includes 32-
bit and 64-bit software. Confirm the information before
installing.
ii. For 32-bit operating system, install 32-bit oracle software.
For 64-bit operating system, install both 32-bit and 64-bit
oracle software.
iii. 32-bit oracle software only can install 32-bit patch packet,
and 64-bit oracle software only can install 64-bit patch
packet.
f 32-bit patch packet is p4163445_92070_SOLARIS.zip
f 64-bit patch packet is p4163445_92070_SOLARIS64.zip
iv. Download the patch packet from
https://metalink.oracle.com.
v. Click login in metalink. Input user name and password
(Please ask NM Development Department for them).
After login, select patches & Updates page, then select
Simple Search link as shown in Figure 14.

FIGURE 14 − DOWNLOAD P ATCH
vi. Open Simple Search page and input patch number to

choose 32-bit or 64-bit oracle software as shown in
Figure 15.
FIGURE 15 − P ATCH SEARCHING
vii. Click Go to search patch result as shown in Figure 16.

Click Download to start downloading.

FIGURE 16 − P ATCH SEARCHING RESULT
2. To verify Oracle product is 32-bit or 64-bit:

Input commands under oracle user command (su – oracle):
sqlplus “/as sysdba”
The result is as follows:
# su - oracle
Sun Microsystems Inc. SunOS 5.8 Generic
Patch February 2004
$ sqlplus "/as sysdba"
SQL*Plus: Release 9.2.0.1.0 - Production on Mon Feb
20 13:19:28 2006
Copyright (c) 1982, 2002, Oracle Corporation. All
rights reserved.
Connected to:
Oracle9i Enterprise Edition Release 9.2.0.1.0 -
Production
With the Partitioning, OLAP and Oracle Data Mining
options
JServer Release 9.2.0.1.0 – Production
Among them, the third line is Connected to:. The fourth line
can be one of the following contents:
Oracle9i Enterprise Edition Release 9.2.0.1.0 – Production
Oracle9i Enterprise Edition Release 9.2.0.1.0 – 64bit
Production
If there is 64-bit before the last Production word, it means
oracle product is 64-bit, or it is 32-bit.

In addition, if execute “select * from v$version”

command in sqlplus, the same information may appear.
3. Requirements for oracle general installer version
This installation patch includes one oracle standard installer,
version 10.1.0.4. Use this installer instead of the installer in
9.2x version or that under oracle installation directory. This
patch is not complete software. Install it on a currently
existing Oracle9i version. In other words, it means that
former Oracle version 9.2.0.x.x is required.
4. Requirements for system
Operating systems are: Solaris 8, Solaris 9 or Solaris 10.
Oracle version is Oracle9i release 2 (9.2.0.1.0) or later.
The version after installation is 9.2.0.7.0.
Steps before Perform the following steps:
Patch
1. Download and decompress installation software.
Installation
i. Select download software according to the original
installation oracle bit.
f 32-bit patch pack is: p4163445_92070_SOLARIS.zip
f 64-bit patch pack is: p4163445_92070_SOLARIS64.zip
ii. Do not place the patch in the installation directory and
sub-directory. Create a new directory to place patch pack,
for example, Oracle_patch.
iii. The decompressed contents are saved in patch saving
directory.
$ unzip p4163445_9207_solaris64.zip
2. Guarantee the establishment of environment parameter
ORACLE_HOME and ORACLE_SID is correct.
Login the account as oracle. Confirm the environment
parameter set is correct, check result by executing env
command.
3. Stop oracle database and relevant process instances.
i. Shutdown the current normal and direct prior-level oracle
server instance. Stop all monitoring program, agency and
other programs in ORACLE_HOME.
ii. Shutdown oracle example in oracle user account. Run
sqlplus /nolog, and link by connect /as sysdba, then
execute shutdown command.
iii. Shutdown oracle monitoring method is: Start-up lsnrctl
as oracle account, and execute stop command.
4. Backup the system. (Selective)
Backup original oracle9i installation and database data before
patch installing.

Patch Patch installation steps including interactive and non-interactive

Installation installation.
Steps
Interactive installation: When installing patch in one version,
which is not Oracle9i version, installer prompts warning
dialog box including the following error message:
There are no patches that need to be applied from the
patch set oracle9i patch set 9.2.0.7.0.
Oracle general installer is not allowed to continue this
installation process, click OK on dialog, and then click
Cancel to exit.
Installation steps are as follows:
1. Login account as oracle.
2. To install patch from telnet installation mode via Xmanager,
perform the following actions:
Input the below commands to display direct X applications
in local system, and change local_host IP into Xmanager‘s
IP address.
% setenv DISPLAY local_host:0.0
3. Input the following commands to start-up installer, which is
under patch decompress directory.
cd Oracle_patch/Disk1
./runInstaller
4. Click Next on Welcome page, File Location window
appears.
5. On File Locations page, click Browse and select original file
near to Name field in source area.
6. Select products xml file of Disk1/stage under patch
decompress directory. For example, this file is:
Oracle_patch/Disk1/stage/products.xml.
7. In Name field of destination area of this page, select
Oracle Home directory that need to install patch from drop-
down list. Click Next to enter Summary page.
8. Summary page lists all relevant patches and original file.
Click Install.
9. Installation process is interrupted, use root account to
execute $ORACLE_HOME/root.sh. At the same time, start
another client to login using root account, execute root.sh
of $ORACLE_HOME.
10. On end page, click Exit, then click Yes to exit.
Steps after Perform the following steps after patch installation:

Patch
1. Check system table space: At least 10 M space is available.
Installation

2. Set two initialization parameters: SHARED_POOL_SIZE and

JAVA_POOL_SIZE.
Before executing the updated root version catpatch.sql,
confirm the two parameter values are not less than 150 MB.
Login as oracle, and start up database:
$ sqlplus “ /as sysdba”
SQL > STARTUP
Check the two parameters.
Note: The unit is byte. 1 MB is equal to 1048576 bytes.
SQL> SHOW PARAMETER SHARED_POOL_SIZE
SQL> SHOW PARAMETER JAVA_POOL_SIZE
If the value is less than 157286400, and system uses server
parameter file, execute the following commands to modify
value:
SQL> ALTER SYSTEM SET SHARED_POOL_SIZE='150M'
SCOPE=spfile;
SQL> ALTER SYSTEM SET JAVA_POOL_SIZE='150M'
SCOPE=spfile;
Shutdown database:
SQL >shutdown
3. Update database
Login as oracle.
Start up oracle monitor.
$ lsnrctl start
Use SQL*Plus and log in as SYS user.
$ sqlplus /nolog
SQL> CONNECT / AS SYSDBA
Execute the following commands. Use the full path of
ORACLE_HOME to replace the part of <?>.
Note: The process may last a long time. Do not terminate it.
The system saves this operation to patch.log.
SQL> STARTUP MIGRATE
SQL> SPOOL patch.log
SQL> @?/rdbms/admin/catpatch.sql
SQL> SPOOL OFF
Check patch.log file. It includes every server version and
status in database. If there is any mistake, modify and
update as above commands.
Reboot database:
SQL> SHUTDOWN

SQL> STARTUP
Run utlrp.sql root version, and re-edit all invalid PL/SQL
packets immediately.
Note: Replace ＜？＞ with ORACLE_HOME path.
SQL> @?/rdbms/admin/utlrp.sql
SQL Server Database

Installation
Purpose To install SQL server 2000 database.
Preliminary None
Steps
Steps To install SQL server database installation, perform the following

steps:
1. Insert the installation disk in CD-ROM. The installation wizard
automatically starts installation process as shown in Figure
17.
FIGURE 17 − SQL SERVER 2000 INSTALLATION SCREEN
Note: If the installation wizard does not start automatically,

explore installation CD and double-click Autorun.exe in root
directory.

2. Click SQL Server 2000 Components as shown in Figure 18.
FIGURE 18 − SQL SERVER 2000 INSTALLATION SCREEN
Result: Install Components window appears as shown in

Figure 19.
FIGURE 19 − INSTALL COMPONENTS WINDOW
3. Click Install Database Server to start database installation

as shown in Figure 20.

FIGURE 20 − INSTALL ATION PREPAR ATIONS WINDOW
Result: The wizard starts installation preparations. Wait while

the wizard completes preparation and Welcome window
FIGURE 21 − WELCOME WINDOW
4. Read the instructions carefully. Click Next and Computer

Name window appears as shown in Figure 22.
FIGURE 22 − COMPUTER NAME WINDOW

5. Select Local Computer to install database on local machine

and click Next.
6. Select Create a new instance of SQL Server, or install
Client Tools and click Next. Wizard also shows help for
selected option as shown in Figure 23.
FIGURE 23 − INSTALL ATION SELECTION WINDOW
7. Specify Name and Company details and click Next as

shown in Figure 24.
FIGURE 24 − USER INFORMATION WINDOW
8. Software License Agreement window appears as shown in

Figure 25. Click Yes to accept agreement and continue with
installation.

FIGURE 25 − SOFTWARE LICENSE AGREEMENT WINDOW
9. Choose Server and Client Tools and click Next as shown in

Figure 26.
FIGURE 26 − INSTALL ATION DEFINITION WINDOW
10. Make sure that Default is checked and click Next as shown
in Figure 27.

FIGURE 27 − INSTANCE N AME WINDOWS
11. Choose Typical (setup type) and click Browse to specify a

destination folder for SQL Server as shown in Figure 28.
FIGURE 28 − INSTALL ATION TYPES WINDOW
12. Select Use the same account for each service. Auto
start SQL Server Service. Under Service Settings select
Use the Local System account and click Next as shown in
Figure 29.

FIGURE 29 − SERVICE ACCOUNTS WINDOW
13. Choose Mixed Mode and provide a password. Click Next as

shown in Figure 30.
FIGURE 30 − AUTHENTICATION MODE WINDOW
14. Read the instructions and click Next as shown in Figure 31.

FIGURE 31 − START COPYING FILE WINDOW
15. Select Per Seat for licensing mode and input 10 for devices
FIGURE 32 − CHOOSE LICENSING MODE WINDOW
Tip: Wait until the installation completes.
16. Figure 33 shows installation progress.

FIGURE 33 − INST ALL ATION PROGRESS WINDOW
FIGURE 34 − STARTING SERVER WINDOW
FIGURE 35 − UPDATING SYSTEM WINDOW
17. Read the installation summary and click Finish to complete

the setup as shown in Figure 36.

FIGURE 36 − INSTALL ATION COMPLETE DIALOG BOX
END OF STEPS
Result SQL server installation is completed successfully.
NOTE: Install latest patch after SQL Server 2000 installation.

Chapter 3
NMS Installation

Overview
Installing NMS for Windows
Installing NMS for Unix
Overview
NMS provides eight management functions: Performance
Management, Report Management, Topology Management,
Security Management, Log Management, System Management,
Policy Management, and Fault Management.
Large Scale NetNumen N31 (V4.2.0) provides high flexibility to add new
Distributed servers while the system is running to meet the growing number
System of customer access. Provides fault tolerance capability, if one
server fails others can take over to ensure uninterrupted service.
Remote NetNumen N31 (V4.2.0) supports web based network

Management management capability via a secure control mechanism.
System Supports optimal access authority control and provide log

Security records to accomplish system security.
Installation NetNumen N31 (V4.2.0) supports following two types of

Modes installation modes:
Client and Server: Installs both client and server on same
machine. Choose this option for server machines.
Client only: Installs only client on machine. Choose this
option for client machines.

Installing NMS for Windows

Installing NMS Client and Server
Installing NMS Client
Installing NMS Config Center

Purpose To install NMS client and server.
Preliminary None
Setup
Steps To install client and server, perform the following steps:

1. Run the installation CD-ROM. Execute the file install.bat if
installing NMS for MS Windows and install.sh if installing for
Sun Solaris. The installer wizard prompts to select the
language for installation. Figure 37 shows NetNumen N31
installation progress in command prompt windows.
FIGURE 37 – NETNUMEN INSTALL ATION (WINDOWS)
2. Select 1 for English and press return key to start extracting


Chapter 3 NMS Installation
FIGURE 38 – SELECTING LANGU AGE – NETNUMEN
3. Specify target directory and press return key to start the

installation as shown in Figure 39.
FIGURE 39 – DIRECTORY SELECTION IN NETNUMEN
Important: If target directory is not selected then system

installs automatically in c:\netnumen directory
4. Select 2 for Client and Server installation and press return
key to extract platform.zip files as shown in Figure 40.

FIGURE 40 – EXTRACTING PLATFORM FILES
Important! Wait while unpacking platform.zip file, it takes

some time to complete unpacking process.
END OF STEPS
Result NMS Client and Sever is Installed successfully.

Purpose To install NMS client.
Preliminary None
Setup
Steps To install NMS client, perform the following steps:

1. Run the installation CD-ROM. Execute the file install.bat if
installing NMS for MS Windows and install.sh if installing for
Sun Solaris. The installer wizard prompts to select the
language for installation. Figure 41 shows NetNumen N31
installation progress in command prompt windows.

FIGURE 41 – NETNUMEN INSTALL – NMS CLIENT
2. Select 1 for English then press return key to start extracting

FIGURE 42 – SELECTING LANGU AGE - NMS CLIENT


FIGURE 43 – DIRECTORY SELECTION NMS CLIENT

4. Select 1 for Client installation and press return key to
extract platform.zip files as shown in Figure 44.
FIGURE 44 – EXTRACTING PLATFORM FILES NMS CLIENT

END OF STEPS
Result NMS client is installed successfully.

Configuring NMS Config Center

NMS configuration center is used to configure common
configurations, EPM parameters configuration and common
maintenance.
Running Config Center
Basic information
NE Module
Database
FTP Service
Client Update
Policy Configuration
System Log Information
NE Type
Shortcut
Other
Analog Input Parameters
Digital Input Parameters Configuration
Digital Output Parameters Configuration
Power Parameters Configuration
Import (Export) Configuration
Purpose To run the config center.

Preliminary NMS client and server must be installed.
Setup
Steps To run the config center, perform the following steps:

1. Click start then select Programs → NetNumen N31 →
Tools → NetNumen N31 Config Center as shown in Figure
45.

FIGURE 45 – RUNNING NMS CONFIG CENTER
2. NetNumen Config Center window is shown in Figure 46.
FIGURE 46 – NETNUMEN CONFIG CENTER WINDOW
END OF STEPS
Result Config center runs successfully.

Basic Information
Purpose To view the NMS basic information.

Setup
Steps To view the basic information, perform the following step:

Click on Basic Info under Common Config tree. Basic info
tab appears as shown in shown in Figure 47. Under Common
Configuration menu, Basic Information tab provides the
following information:
NMS Version
Platform Version
Operating System
JAVA Version
Database Information
NMS Language
NMS Logger Level
Total Threads
Server and Client Memory
Auto Optimize Facility
FIGURE 47 – BASIC INFORMATION TAB
END OF STEPS
Result Basic information is viewed successfully.

NE Module
Purpose To view information about installed and uninstalled devices.

Setup
Steps To view installed or uninstalled NE module information, perform

Click on NE Module under Common Config tree. NE Module
tab provides information about installed and uninstalled devices
FIGURE 48 – NE MODULE TAB
END OF STEPS
Result NE module is viewed successfully.
Database
Purpose To optimize and test connection with the database.

Setup
Steps To optimize and test the database, perform the following steps:
1. Click on Database under Common Config tree. DataBase
tab appears as shown in Figure 49.

FIGURE 49 – DAT AB ASE T AB
2. Data Type, DataBase Language, and OS information are

shown on right pane of DataBase tab. Click DataBase Type
drop-down list to select the type as shown in the Figure 50.
FIGURE 50 – DAT AB ASE D ATA TYPE TAB

3. Double click on Database System Administration Name

and set administrator name. Double click on Database
System Administration Password and set administrator
password as shown in Figure 51.
FIGURE 51 – DAT AB ASE SYSTEM ADMINISTRATION N AM E AND P ASSWORD
Important! Windows based systems normally use the

following two databases:
SQL Server Database: The default login username for
administrator is sa and password is netnumen. Login
username and password for Config Center and SQL server
database must be the same.
Oracle Database: The default login username for
administrator system and password is netnumen. Login
username and password for Config Center and Oracle
database must be the same.
4. Double click IP Address value to set IP address for dual
backup system configuration as shown in Figure 52.

FIGURE 52 – DAT AB ASE IP ADDRESS WINDOW
Important! For single system configuration default IP

address is used, but for dual backup system configuration
floating IP address is used.
5. Database file path (only for HA System)
To save data for single system configuration database, path
is not changed. But in dual system, set the path for saving
the database data file.
6. To test the database connectivity click on Test Connection.
Test connectively information is displayed in dialog box on
the top of Test Connection button as shown in Figure 53.

FIGURE 53 – TEST CONNECTION DAT AB ASE
7. To optimize database configuration on the network click

Optimize. Optimize database configuration on the network
is displayed in dialog box on the top of Optimize button as
shown in Figure 54.
FIGURE 54 – OPTIMIZE DATAB ASE

Note: Test Connection and Optimize the data operation

are used for SQL server database, but for Oracle database only
Test Connection operation is used.
END OF STEPS
Result Database is tested and optimized successfully.
FTP Service
Purpose To configure FTP service.

Setup
Steps To configure FTP service, perform the following steps:

1. Click on FTP User under Common Config tree. FTP User
tab appears as shown in Figure 55.
FIGURE 55 – FTP SERVICE TAB
2. To add FTP user click Add in FTP Service tab. Modify FTP
User window appears as shown in Figure 56. Click OK to add
user.

FIGURE 56 – ADD FTP USER WINDOW
3. To modify FTP user click Modify in FTP User tab. Modify

FTP User window appears as shown in Figure 57. Click OK
after modifying the user information.
FIGURE 57 – MODIFY FTP USER WINDOWS
4. To delete FTP user click Delete in FTP User tab.

i. Information dialog box appears as shown in Figure 58.
Click Yes to delete the user.

FIGURE 58 – INFORM ATION DIALOG BOX
ii. Information dialog box again appears to show that the

user is deleted successfully as shown in Figure 59.
END OF STEPS
Result FTP user is added, modified and deleted successfully.
Client Update
Purpose To update client data.

Setup
Steps To update client data, perform the following step:

Click on Client Update under Common Config tree Client
Update tab appears as shown in Figure 60.

FIGURE 60 – CLIENT UPDATE TAB
END OF STEPS
Result Client is updated successfully.
Purpose To configure policy.

Setup
Steps To configure the policy, perform the following steps:

Click on Policy Configuration under Common Config tree
Policy Configuration tab appears as shown in Figure 61.

FIGURE 61 – POLICY CONFIGURATION T AB
Resource Configure the following policies before using.

Introduction
NM database backup policy
NMS database backup should be saved regularly on time and
saved in path specified.
Alarm log management policy
This policy takes the backup of the alarms exceeding
threshold (time and quantity) in csv type on time and saves
them in the specified directory. The policy deletes the
exceeding threshold alarm records. The save path, time
threshold and quantity threshold is set in the configuration
file.
Alarm table for alarm policy includes CAF_HISTORYALARM,
CAF_BAKEHISALARM and CAF_INFORM, CAF_EVENT.
Operation log management policy
threshold and quantity threshold can be set in the
configuration file.
Log table for log policy includes Log_Sys_Table,
Log_Cmd_Table and Log_Scrt_Table.

Parameter The related policy parameters need to be configured in config

Instruction center as shown in Figure 61. The parameter instructions are as
follows:
1. BackupPath: Saving path of database backup file
For example,
BackupPath=d:/dbbackup or /export/home/oracle/backup
2. MysqlBinPath: abandon.
3. AlarmLogBackupPath_Table: Saving path of alarm and log
backup file.
For example, AlarmLogBackupPath_Table =d:/logbackup or
/export/home/logbackup
Notes: If the configured path does not exist, NM server
creates it automatically. (Recommended this method)
4. isSaveByTime: Whether NM only save log in certain time or
not. (Alarm log, operation log)
Default: true Recommended: true
When parameter value is true, the exceeding threshold log
decides whether to backup them to
AlarmLogBackupPath_Table according to
Lock_BackupAlarm configuration and then delete these
logs in NMS database.
5. The following parameters are used for appointing detailed
saving time.
HisAlarmSaveTime (day) Default: 90 Recommended: 30
LogSaveTime (day) Default: 90 Recommended: 60
6. The following parameters are used for whether backup
exceeding logs.
Lock_BackupAlarm: True (Backup)/False(Doesn’t backup)
Lock_ BackupLog: True (Backup)/False(Doesn’t backup)
isSaveByCount: Whether NM save certain quantity logs
( Alarm log, operation log)
saving time.
HisAlarmSaveCount: alarm quantity restriction.
Default: 300,000 Recommended: 300,000
LogSaveCount: Operation log quantity restriction.

8. The following parameters are used for backup exceeded logs.

Lock_BackupLog: True (Backup)/False (Doesn’t backup)
Lock_BackupAlarm: Whether backup alarms that meet
deleted conditions.
For those alarms that meet deleted conditions (Time
threshold and quantity threshold), backup before deleting
from database.
When the parameter value is true, backup the alarms before
deleting that meet the conditions. When the parameter value
is false, delete alarms directly without backup.
Lock_BackupLog： whether NM need to backup logs, which
meet deleted conditions.
For those logs that meet deleted conditions (Time threshold
and quantity threshold), backup before deleting from
database.
When the parameter is true, backup the logs before deleting
which meet conditions. When the parameter is false, delete
logs directly without backup.
After configuring relevant policy parameters, add these
policies in NM client, it saves the backup files to appointed
directory according to configured parameters.
Purpose To add, modify and delete system log information.

Setup
Steps To add, modify and delete system log information, perform the
following steps:
1. Click on Syslog Info under Common Config tree. Syslog
Info tab appears as shown in Figure 62.

FIGURE 62 – SYSLOG INFO TAB
2. To add a Syslog Server, click Add in Syslog Info tab. Add

Syslog Server window appears as shown in Figure 63.
FIGURE 63 – ADDING SYSLOG SERVER WINDOW
i. Click Add to add an NE Type as shown in Adding

Syslog Server window. Add NE Type window appears

FIGURE 64 – ADD NE TYPE
ii. Enter NE Type and click Confirm to add the NE.

iii. To modify NE type click Modify in Add Syslog Server
window. Modify NE Type window appears as shown in
Figure 65. Click Confirm after modifying the NE type.
FIGURE 65 – MODIFY NE TYPE
iv. To delete NE Type click Delete as shown in Figure 66.
FIGURE 66 – ADD SYSLOG SERVER
3. To modify system log server parameters click Modify in

Sylog Info tab. Modify Syslog Server window appears as
shown in Figure 67. Click Confirm after modifying the
required parameters.

FIGURE 67 – MODIFY SYSLOG SERVER
4. To delete system log server click Delete as shown in Figure

68.
FIGURE 68 – DELETE SYLOG SERVER
END OF STEPS
Result System log information is added, modified and deleted
successfully.

Shortcut
Purpose To view shortcut on desktop.

Setup
Steps To view shortcut on desktop, perform the following step:

Click on Short Cut under Common Config tree. Short Cut tab
appears as shown in Figure 69. Short Cut tab provides
information about shortcuts on desktop, in startup menu and
path description.
FIGURE 69 – SHORTCUT TAB
END OF STEPS
Result Shortcuts are viewed on desktop successfully.
Other
Purpose To view other tab.

Setup
Steps To view other tab, perform the following steps:

1. Click on Other under Common Config tree. Other tab
provides Basic tab appears as shown in Figure 70.

FIGURE 70 – OTHER TAB
2. Click Advance tab to view advance information as shown in

Figure 71.
Advance tab provides the information about different
platform as follows:
f UEP Plate Server
f NetNumen Server
f UEP Plate Client
f NetNumen Client

FIGURE 71 – ADVANCE TAB
3. To modify information double click on any parameter of

Value in Basic tab. In Advance tab put cursor on the value
and click one time, the value appears in Modify field. Click
Modify to modify as shown in Figure 72.
FIGURE 72 – S AVE OTHER INFORM ATION

4. To save advance and basic information click on Save. Info

dialog box appears as shown in Figure 73. Click OK to finish
successfully.
FIGURE 73 – INFO DIALOG BOX
END OF STEPS
Result Other tab is viewed successfully.
Analog Input Parameters Configuration
Purpose To configure analog input parameters.

Setup
Steps To configure analog input parameters, perform the following

steps:
1. Click on Analog Input Parameters Config under EPM
Parameters Config tree. Analog Input Parameters
Config window appears as shown in Figure 74.

FIGURE 74 – AN ALOG INPUT P AR AMETERS CONFIGURATION TAB
2. To add analog input parameter, click Add. Add window

FIGURE 75 – ADD AN ALOG P AR AMETERS
3. To modify the required parameters, click Modify in Analog

Input Parameters Config window and click OK after
modifying the parameters as shown in Figure 76.

FIGURE 76 – MODIFY AN ALOG INPUT P ARAMETERS CONFIGURATION TAB
4. To delete analog input parameters click Delete. Info window

appears as shown in Figure 77. Click Yes to confirm delete.
FIGURE 77 – INFO
END OF STEPS
Result Analog input parameters are configured successfully.
Purpose To configure digital input parameters.

Setup
Steps To configure digital input parameters, perform the following

steps:
1. Click on Digital Input Parameters Config under EPM
Parameters Config tree. Digital Input Parameters
Config window appears as shown Figure 78.

FIGURE 78 – DIGITAL INPUT P AR AMETERS CONFIGURATION TAB
2. Click Add to add digital input parameter. Add window

FIGURE 79 – ADD INPUT DIGITAL P AR AM ETERS WINDOW
3. To modify the required parameters, click Modify in Digital

Input Parameters Config window and click OK after
modifying the parameters as shown in Figure 80.

FIGURE 80 – MODIFY DIGITAL INPUT PARAMETERS WINDOW
4. To delete digital input device click Delete in Digital Input

Parameters Config window. Info dialog box appears, click
Yes to confirm delete as shown in Figure 81.
FIGURE 81 – DELETE DIGITAL INPUT PARAMETERS
END OF STEPS
Steps Digital input parameters are configured successfully.
Purpose To configure digital output parameters.

Setup
Steps To configure digital output parameters, perform the following

steps:
1. Click on Digital Output Parameters Config under EPM
Parameters Config tree. Digital Output Parameters
Config window appears as shown in Figure 82.

FIGURE 82 – DIGITAL OUTPUT P AR AMETERS CONFIGURATION T AB

appears as shown Figure 83.
FIGURE 83 – ADD OUTPUT DIGITAL P AR AMETERS WINDOW
3. Click Modify to change the desired parameters. Select

Device Name, as shown in Figure 84. Click OK to confirm
the changes.

FIGURE 84 – MODIFY DIGITAL OUTPUT PAR AMETERS CONFIGURATION
4. Click delete in Digital Output Parameters window. Info

dialog box appears click Yes to confirm delete as shown in
Figure 85.
FIGURE 85 – DELETE DIGITAL OUTPUT PARAMETERS
END OF STEPS
Result Digital output parameters are configured successfully.
Power Parameters Configurations
Purpose To configure power parameters.

Preliminary NMS client and server must be installed
Setup
Steps To configure power parameters, perform the following steps:

1. Click on Power Parameters Config under EPM
Parameters Config tree. Power Parameters Config
window appears as shown in Figure 86.

FIGURE 86 – POWER P ARAMETERS CONFIGURATION T AB
2. Click Add. Add window appears as shown in Figure 87.
FIGURE 87 – ADD POWER PARAMETERS WINDOW
3. Click Modify in Power Parameters Config window. Modify

window appears as shown in Figure 88. Click OK after
modifying the required parameters.

FIGURE 88 – MODIFY POWER P AR AMETERS CONFIGURATION
4. Click Delete in Power Parameters Config window. Info

dialog box appears, click Yes to confirm delete as shown in
Figure 89.
FIGURE 89 – DELETE POWER P AR AMETERS
END OF STEPS
Result Power parameters are configured successfully.
Import (Export) Configuration Data
Purpose To import and export configuration data.

Setup
Steps To import and export configuration data, perform the following

steps:
1. Click Import (Export) Configuration data under
Common Maintenance tree. Import (Export)
configuration data window appears as shown in Figure 90.

FIGURE 90 – IMPORT (EXPORT) CONFIGURATION DATA TAB
2. To import the data click Import Configuration Data radio

button then click Import. Save windows appears as shown
in Figure 91. Click Save to save the data.
FIGURE 91 – IMPORT DAT A WINDOW
3. To export the data click Export Configuration Data radio

button then click Export. Save windows appears as shown
in Figure 92.

FIGURE 92 – EXPORT DATA WINDOW
END OF STEPS
Result Data is imported and exported successfully.
Installing NMS for UNIX

Installing NMS Config Center

Purpose To install NMS client and server on UNIX system.
Preliminary None
Setup
Steps To install NMS client and server on UNIX system, perform the
following steps:
1. Run the installation CD-ROM. Execute the file install.sh if
installing NMS Client and Sever for UNIX system, as shown in
Figure 93.

FIGURE 93 – CONFIG CENTER.SH
2. After executing install.sh file the installer wizard prompts to

select the language for installation. NetNumen N31
installation progress in command prompt windows is shown
in Figure 94.
FIGURE 94 – NETNUMEN INSTALL
3. Select 1 for English, then press return key to start

extracting files as shown in Figure 38.



5. Select 1 for Client and Server installation and press return
key to extract platform.zip files as shown in Figure 97.


6. Wait for a while to start Config Center as shown in Figure
98.
FIGURE 98 – CONFIG CENTER STARTS
END OF STEPS
Result NMS client and sever is installed successfully.


Purpose To install NMS client on UNIX system.
Preliminary None
setup
Steps To install NMS client on UNIX system, perform the following

steps:
1. Run the installation CD-ROM. Execute the file install.sh if
installing NMS client for UNIX system, as shown in Figure 99.
FIGURE 99 – CONFIG CENTER.SH
2. After executing install.sh file the installer wizard prompts to

choose the language for installation. Figure 100 shows
NetNumen N31 installation progress in command prompt
windows.

3. Select 1 for English, then press return key to start

extracting files as shown in Figure 101.



5. Select 1 for Client installation and press return key to
continue extracting platform.zip file as shown in Figure 103.

some time to complete the unpacking process.
6. Wait for a while to start Config Center as shown in Figure
104.

FIGURE 104 – CONFIG CENTER STARTS
END OF STEPS
Result NMS Client is installed successfully.
Configuring UNIX NMS Config

Center
NMS configuration center is used to configure common
configurations, EPM parameters configuration and common
maintenance.
This topic includes the following:
Basic information
NE Module
Database
FTP Service
Client Update
NE Type
Shortcut
Other
Analog Input Parameters


Power Parameters Configuration
Import (Export) Configuration
Purpose To run the config center.

Setup
Steps To run the config center, perform the following steps:

1. Run configcentre.sh if installing NMS client for UNIX
system, as shown in Figure 105.
FIGURE 105 – CONFIGURATION CENTER.SH
2. NMS configuration center is used to configure common

configuration, EPM configuration and common maintenance

FIGURE 106 – NETNUMEN CONFIGURATION CENTER TAB
END OF STEPS
Result Config center runs successfully.
Basic Information
Purpose To view the NMS basic information.

Setup
Steps To view the basic information, perform the following step:

Click on Basic Info under Common Configuration tree. Basic
info tab appears as shown in shown in Figure 107. Under
Common Configuration menu, Basic Information tab
provides the following information:
NMS Version
Platform Version
Operating System
JAVA Version
Database Information
NMS Language
NMS Logger Level
Total Threads
Server and Client Memory
Auto Optimize Facility

FIGURE 107 – BASIC INFORM ATION TAB
END OF STEPS
Result Basic information is viewed successfully.
NE Module
Purpose To view information about installed and uninstalled devices.

Preliminary NMS client and server must be installed
Setup
Steps To view installed or uninstalled NE module information, perform

1. Click on NE Module under Common Configuration tree.
NE Module tab provides information about installed and
uninstalled devices as shown in Figure 108. Check the NE
module that is to be installed, click Save to complete the
configuration.

FIGURE 108 – NE MODULE TAB
2. Click Advance to deploy the NE module. Module Deploy

window appears as shown in Figure 109. Check the module
to be configured then click Save to save the configuration.
FIGURE 109 – MODULE DEPLOY
END OF STEPS
Result NE module is viewed successfully.
Database Configuration
Purpose To configure the database management.

Setup

Steps To configure the database management, perform the following

steps:
1. Click on Database Configuration under Common
Configuration tree. DataBase Configuration tab appears
FIGURE 110 – DAT AB ASE TAB
2. Data Type, DataBase and OS information are shown on

right pane of DataBase tab. Click DataBase Type drop-
down list to select the type as shown in the Figure 111.
FIGURE 111 – DAT AB ASE DAT A TYPE TAB

3. Double click Database System Administration Name and

set administrator name. Double click Database System
Administration Password and set administrator password
FI G U R E 1 1 2 – D AT AB AS E S Y S T E M AD M I N IS T R AT I O N N AM E AN D P AS S W O R D
Important! Oracle database: The default login username

for administrator is system and password is netnumen.
Login username and password for Config Center and
Oracle database must be the same.
4. Double click IP Address value to set IP address as shown in
Figure 113.

FIGURE 113 – DAT AB ASE IP ADDRESS WINDOW
Important! For single system configuration default IP

address is used, but for dual backup system configuration
floating IP address is used.
5. Database file path (only for HA System)
To save data for single system configuration database, path
is not changed. But in dual system, set the path for saving
the database data file. Normally the "/ export / home /
oracle / oradata path is used.
6. To test the database connectivity click on Test Connection.
Test connectively information is displayed in dialog box on
the top of Test Connection button as shown in Figure 114.

FIGURE 114 – TEST CONNECTION DAT ABASE
Note: Test Connection and Optimize the data operation

are used for SQL server database, but for Oracle database only
Test Connection operation is used.
END OF STEPS
Result Database is tested and optimized successfully.
FTP Service
Purpose To configure FTP service.

Setup
Steps To configure FTP service, perform the following steps:

1. Click on FTP User under Common Configuration tree. FTP
User tab appears as shown in Figure 115.

FIGURE 115 – FTP SERVICE TAB
2. To add FTP user click Add in FTP Service tab. Modify FTP
User window appears as shown in Figure 116. Click OK to
add the user.
FIGURE 116 – ADD FTP USER WINDOW
3. To modify FTP user click Modify in FTP User tab. Modify

FTP User window appears as shown in Figure 117. Click OK
after modifying the user information.

FIGURE 117 – MODIFY FTP USER WINDOWS
4. To delete FTP user click Delete in FTP User tab.

i. Information dialog box appears as shown in Figure 118.
Click Yes to delete the user.
ii. Information dialog box again appears to show that user

is deleted successfully as shown in Figure 119.
END OF STEPS
Result FTP user is added, modified and deleted successfully.

Client Update
Purpose To update client data.

Setup
Steps To update client data, perform the following step:

Click on Client Update under Common Configuration tree
Client Update tab appears as shown in Figure 120.
FIGURE 120 – CLIENT UPDATE TAB
END OF STEPS
Result Client is updated successfully.
Purpose To configure policy configuration.

Setup
Steps To configure the policy configuration, perform the following step:

Click on Policy Configuration under Common Configuration
tree Policy Configuration tab appears as shown in Figure 121.

FIGURE 121 – POLICY CONFIGURATION T AB
Resource Configure the following policies before using.

Introduction
NM database backup policy
NMS database backup should be saved regularly on time and
saved in path specified.
Alarm log management policy
threshold and quantity threshold is set in the configuration
file.
Alarm table for alarm policy includes CAF_HISTORYALARM,
CAF_BAKEHISALARM and CAF_INFORM, CAF_EVENT.
Operation log management policy
threshold and quantity threshold can be set in the
configuration file.
Log table for log policy includes Log_Sys_Table,
Log_Cmd_Table and Log_Scrt_Table.
Parameter The related policy parameters need to be configured in config

Instructions center as shown in Figure 61. The parameter instructions are as
follows:
1. BackupPath: Saving path of database backup file

For example,
BackupPath=d:/dbbackup or /export/home/oracle/backup
2. MysqlBinPath: abandon.
3. AlarmLogBackupPath_Table: Saving path of alarm and log
backup file.
For example, AlarmLogBackupPath_Table =d:/logbackup or
/export/home/logbackup
Notes: If the configured path does not exist, NM server
creates it automatically. (Recommended this method)
4. isSaveByTime: Whether NM only save log in certain time or
not. (Alarm log, operation log)
saving time.
HisAlarmSaveTime (day) Default: 90 Recommended: 30
LogSaveTime (day) Default: 90 Recommended: 60
6. The following parameters are used for whether backup
exceeding logs.
Lock_BackupAlarm: True (Backup)/False(Doesn’t backup)
Lock_ BackupLog: True (Backup)/False(Doesn’t backup)
isSaveByCount: Whether NM save certain quantity logs
( Alarm log, operation log)
saving time.
HisAlarmSaveCount: alarm quantity restriction.
LogSaveCount: Operation log quantity restriction.
8. The following parameters are used for backup exceeded logs.
Lock_BackupLog: True (Backup)/False (Doesn’t backup)
Lock_BackupAlarm: Whether backup alarms that meet
deleted conditions.


For those alarms that meet deleted conditions (Time
threshold and quantity threshold), backup before deleting
from database.
When the parameter value is true, backup the alarms before
deleting that meet the conditions. When the parameter value
is false, delete alarms directly without backup.
Lock_BackupLog： whether NM need to backup logs, which
meet deleted conditions.
For those logs that meet deleted conditions (Time threshold
and quantity threshold), backup before deleting from
database.
When the parameter is true, backup the logs before deleting
which meet conditions. When the parameter is false, delete
logs directly without backup.
After configuring relevant policy parameters, add these
policies in NM client, it saves the backup files to appointed
directory according to configured parameters.
Purpose To configure system log information.

Setup
Steps To configure system log information, perform the following steps:

1. Click on Syslog NBI Info under Common Configuration
tree. Syslog NBI Info tab appears as shown in Figure 122.

FIGURE 122 – SYSLOG NBI INFO TAB
2. To add a Syslog Server, click Add in Syslog NBI Info tab.

Add Syslog Server window appears as shown in Figure 123.
FIGURE 123 – ADDING SYSLOG SERVER WINDOW
i. Click Add to add an NE Type as shown in Adding

Syslog Server window. Add NE Type window appears
ii. Enter NE Type and click Confirm to add the NE as
shown in Figure 124.

FIGURE 124 – ADD NE TYPE
iii. To modify NE type click Modify in Add Syslog Server

window. Modify NE Type window appears as shown in
Figure 125. Click Confirm after modifying the NE type.
FIGURE 125 – MODIFY NE TYPE
iv. To delete NE Type click Delete as shown in Figure 126.
FIGURE 126 – ADD SYSLOG SERVER
3. To modify system log server parameters click Modify in

Sylog Info tab. Modify Syslog Server window appears as
shown in Figure 127. Click Confirm after modifying the
required parameters

FIGURE 127 – MODIFY SYSLOG SERVER
4. To delete system log server click Delete as shown in Figure

128.
FIGURE 128 – DELETE SYLOG SERVER
END OF STEPS
Result System log information is added, modified and deleted
successfully.

Short Cut
Purpose To view the shortcut on desktop.

Setup
Steps To view shortcut on desktop, perform the following step:

Click on Short Cut under Common Configuration tree. Short
Cut tab appears as shown in Figure 69. Short Cut tab provides
information about shortcuts on desktop, in startup menu and
path description.
FIGURE 129 – SHORT CUT TAB
END OF STEPS
Result Shortcuts are viewed successfully on desktop.
Other
Purpose To view other tab.

Setup
Steps To view other tab, perform the following steps:

1. Click on Other under Common Configuration tree. Other
tab provides Basic tab as shown in Figure 130.

FIGURE 130 – OTHER TAB
2. Click Advance tab to view advance information as shown in

Figure 131.
Advance tab provide different platform as follows:
UEP Plate Server
NetNumen Server
UEP Plate Client
NetNumen Client
FIGURE 131 – ADVANCE T AB

3. To modify information double click any parameter of Value

in Basic tab. In Advance tab put cursor on the value and
click for one time, then value appears in Modify field. Click
Modify to change the parameters as shown in Figure 132.
FIGURE 132 – S AVE OTHER INFORM ATION
4. To save advance and basic information click Save. Info

dialog box appears as shown in Figure 133. Click OK to finish
successfully.
FIGURE 133 – INFO DIALOG BOX
END OF STEPS
Result Other tab is viewed successfully.
Analog Input Parameters Configuration
Purpose To configure analog input parameters.

Setup

Steps To configure analog input parameters, perform the following

steps:
1. Click on Analog Input Configuration under EPM
Configuration tree. Analog Input Configuration tab
FIGURE 134 – AN ALOG INPUT P AR AMETERS CONFIGURATION TAB
2. To add analog input parameter, click Add in Analog Input

Configuration tab. Add window appears as shown in Figure
135.
FIGURE 135 – ADD AN ALOG P AR AMETERS

3. To modify the required parameters, click Modify in Analog

Input Configuration tab and click OK after modifying
parameters as shown in Figure 136.
FI G U R E 1 3 6 – M O D I F Y AN AL O G I N P U T P AR AM E T E R S C O N F I G U R AT I O N T AB
4. To delete analog input parameters click Delete.

Information dialog box appears as shown in Figure 137.
Click Yes to confirm delete.
FIGURE 137 – INFORM ATION
END OF STEPS
Result Analog input parameters are configured successfully.
Purpose To configure digital input parameters.

Setup

Steps To configure digital input parameters, perform the following

steps:
1. Click on Digital Input Configuration under EPM
Configuration tree. Digital Input Configuration tab
FIGURE 138 – DIGITAL INPUT P AR AMETERS CONFIGURATION TAB

FIGURE 139 – ADD INPUT DIGITAL P AR AM ETERS WINDOW

3. To modify the required parameters, click Modify in Digital

Input Configuration tab and click Save after modifying
parameters as shown in Figure 140.
FIGURE 140 – MODIFY DIGITAL INPUT P ARAMETERS WINDOW
4. To delete digital input device click Delete in Digital Input

Configuration window. Information dialog box appears,
click Yes to confirm delete as shown in Figure 141.
FIGURE 141 – DELETE DIGITAL INPUT P ARAMETERS
END OF STEPS
Steps Digital input parameters are configured successfully.
Purpose To configure digital output parameters.

Setup

Steps To configure digital output parameters, perform the following

steps:
1. Click on Digital Output Configuration under EPM
Configuration tree. Digital Output Configuration tab
appear as shown in Figure 142.
FIGURE 142 – DIGITAL OUTPUT P AR AMETERS CONFIGURATION TAB

FIGURE 143 – ADD OUTPUT DIGITAL P AR AMETERS WINDOW

3. Click Modify to change the desired parameters. Select

Device Name, as shown in Figure 144. Click OK to confirm
the changes.
FIGURE 144 – MODIFY DIGITAL OUTPUT P AR AMETERS CONFIGURATION
4. Click Delete in Digital Output Configuration window.

Information dialog box appears, click Yes to confirm delete
FIGURE 145 – DELETE DIGITAL OUTPUT P AR AMETERS
END OF STEPS
Result Digital output parameters are configured successfully.
Power Parameters Configurations
Purpose To configure power parameters.

Setup
Steps To configure power parameters, perform the following steps:

1. Click on Power Configuration under EPM Configuration

tree. Power Configuration tab appear as shown in Figure
146.
FIGURE 146 – POWER P AR AMETERS CONFIGURATION T AB
2. Click Add in Power Configuration tab. Add window

FIGURE 147 – ADD POWER P AR AMETERS WINDOW
3. Click Modify in Power Configuration. Modify window

appears as shown in Figure 148. Click Save after modifying
the required parameters.

FIGURE 148 – MODIFY POWER P AR AMETERS CONFIGURATION
4. Click Delete in Power Configuration tab. Information

dialog box appears, click Yes to confirm delete as shown in
Figure 89.
FIGURE 149 – DELETE POWER P AR AMETERS
END OF STEPS
Result Power parameters are configured successfully.
Import (Export) Configuration Data
Purpose To import and export configuration data.

Setup
Steps To import and export configuration data, perform the following

step:
1. Click Import (Export) Configuration under Common
Maintenance tree. Import (Export) Configuration Data
tab appear as shown in Figure 150.

FIGURE 150 – IMPORT (EXPORT) CONFIGURATION DATA TAB
2. To import the data, click Import Configuration Data radio

button then click Import. Save windows appears as shown
in Figure 151. Click Open to import the data.
FIGURE 151 – IMPORT DATA WINDOW
3. To export the data, click Export Configuration Data radio

button then click Export. Save windows appears as shown
in Figure 152. Click Save to export the data.

FIGURE 152 – EXPORT DATA WINDOW
END OF STEPS
Result Data is imported and exported successfully.


Chapter 4
VCS4.3 for Windows

Overview
System Requirements
Installation Preparations
Installation Operating System
Installing VCS HA Software
Test Dual System Hot Backup Software
Overview
The main purpose of this chapter is to introduce hardware and
software configurations required for dual hot backup NM system.
It also introduces the procedures for installing sqlserver2000
database and NM system, and tests on dual hot backup system.
This chapter covers DELL 2600 server and DELL 220 disk array
(five hard disks) as an example to introduce NM dual system
installation. If other servers and disk arrays are used, divide the
disk as needed. The software installation procedures are the
same.
Procedures of installing NM dual system are:
Configure Hardware
Install Operating System
Install Dual System Software
Install Database System
Install and Configure NM System
Configure and Test Dual System

System Requirements
Hardware The following are the hardware requirements:
Requirements
1. NM server:
The minimum configuration requirements for NM server are:
Memory: 512M
Three network interfaces. Two interfaces connect to heart
beat cable for mutual monitoring. The third one connects to
public network cable for providing NM service.
One disk array card for connecting disk array
2. Disk array:
Set the disk in RAID1+0 array. Divide the array into two
logical drivers with the same space. Five disks, at least four
disks, are required. Four disks are set in RAID1+0 array
mode. The fifth one is set to be hot spare, as the backup of
the other four disks.
Software The following are the software requirements:
Requirements
1. Operating system:
Windows operating system: Win200 Server, Win2003
standard
Patch: SP4 + latest security patch
2. Database system
Database system: SqlServer2000 / SqlServer2003 Enterprise
Database
Patch: SP3 and above
3. Dual system software
Dual system software: VCS4.3 for Windows
Patch: If there is the latest VCS4.3 patch, install the latest
patch.
4. NM server software
NetNumen N31（V4.2.0）NM server
Installation Preparations
Hardware
Hardware Connection
Connecting Disk Array

Chapter 4 VCS4.3 for Windows
Hardware
Two DELL 2600 servers
f NETNUMENCLUSTER1 (A): It works as master server
f NETNUMENCLUSTER2 (B): It works as slave server
Three network interface cards for each server
One SCSI array card for each server
One DELL220 disk array
It is configured with five hard disks. Each of them has the
capacity of 63 G.
Hardware Connection
Figure 153 shows hardware connection.
FIGURE 153 − DUAL HOT BACKUP NM SYSTEM
Disk Array Connections

Connection To connect disk array, perform the following steps:
Steps
1. Insert two array cards in PCI slots in system A and system B
respectively.
2. Connect SCSI array card to DELL220 disk array with SCSI
cable.
Disk Array V240 dual machine +SE3310 disk array:
Connection
SUN V240 dual machine (2*1.28G/2G/2*73G) + SE3310 disk
array (5*073G)
The hardware connection is shown in Figure 154.

FIGURE 154 – DISK ARR AY CONNECTIONS
Note: Ensure that CH0 and single bus cable is connected

properly. Generally, some devices have only one SCSI interface,
indicating the connection interface of disk array.
Explanation Thick cables are used for SCSI interface and thin cables are
used for Ethernet cables.
SUN V2404 has four network cards such as net0, net1, net2
and net3.
Generally, net2 and net3 are used for heartbeat therefore,
no need to configure IP addresses.
net0 is used to connect DCN network and net1 is used to
connect public network.

These cards communicate with each other through SUN

system inner protocols.
Installing Operating System

Purpose To install NM dual hot backup system VCS4.3 for windows.
Preliminary Before installing the operating system following preliminary
Setup setup needs to be configured:
1. Use DELL OPENMAMAGE SERVER ASSISTANT CD to make a
driver programme of disk array card.
2. Close disk array.
3. Insert Win2000 installation disk to install the operating
system. Insert disk array driver according to system prompt.
4. The operating system uses NTFS file system. It resides a
default directory of disk C.
5. Install the latest security patch of WINDOWS 2000 Server +
SP4 +.
6. Install operating systems on both computers. Install relevant
patches. Install network card driver.
Note: If the operating system is Windows 2003, install Windows

Server 2003 Standard. Some VCS Licenses do not support Windows
Server 2003 Enterprise.
Tips: Use the installation disk the factory provides to install the
operating system. For instance, use Smartstart to install the operating
system for HP computer. Follow prompts to install the operating system
and disk array start programme.

Dividing Disk Array
Setting Network
Setting Domain

Dividing Disk Array

Purpose To divide disk array.
Take DELL220 disk array (five disks) as an example.
Steps To divide the disk array, perform the following steps:
1. Configure disk array.
Enable disk array. Restart NETNUMENCLUSTER1. Press ctrl
+ m to enter BIOS configuration. Select SCSI array card 4/DC.
Select config/new config.
2. Divide disk array in RAID1+0 mode.
i. Divide four disks in RAID1+1 mode. Set the fifth disk to
be hot spare, which is the backup of other four disks.
ii. Configure RAID1+0 mode.
First, configure two of the four disks to be RAID1 mirror
mode. Then, configure them to be RAID0 mode.
3. Create two logical drivers on the disk array.
One is for sqlserver database file. The other is for NM server
programmes. Both logical drivers have the same space,
occupying half of the disk array.
4. Start NETNUMENCLUSTER2.
Press ctrl + m. Enter BIOS configuration. Select SCSI array
card 4/DC. Select config. Identify the disk array configuration
again. Then exit BIOS. Start the system.
Note: For disk arrays of other models, follow steps below

to divide the disk array.
Divide disk array in RAID1+0 mode.
Create two logical drivers on RAID1 + 0.
END OF STEPS
Result The disk array is divided successfully.
Configuring Network
Purpose To configure the network.
Introduction The public network card IP address for NETNUMENCLUSTER1 is
10.40.88.44 (the master DNS points to 127.0.0.1.). The public
network card IP address for NETNUMENCLUSTER2 is
10.40.88.139 (the master NDNS points to 10.40.88.44.).

Steps To configure the network, perform the following steps:

1. Configure service connection.
Create Public Connection in network and dialing connection
in control panel. Right click on Property. Enter TCP/IP
configuration. Set IP address and DNS.
2. Configure heartbeat connection.
Create Heartbeat Connection in network and dialing
connection in control panel. Right click on Property. Do not
select Client for Microsoft Network, File and Print
Sharing for Microsoft Networks and Internet Protocol
(TCP/IP) as shown in Figure 155.
FIGURE 155 − CONFIGURING HEARTBE AT CONNECTION
3. Configure host file

Add host names and IP addresses to host files of both
computers.
END OF STEPS
Result The network is connected.

Configuring Domain
Purpose To configure one computer as master domain server and the
other as the backup domain controller.
Main Domain
Configure NETNUMENCLUSTER1 to be master domain

controller.
Steps To configure the master domain, perform the following steps:
1. Open configuration server guide on NETNUMENCLUSTER1, as
shown in Figure 156 or execute dcpromo command. Create
Directory Tree or Child Domain window appears as shown
in Figure 157.
FIGURE 156 − CONFIGURATION SERVER GUIDE

FIGURE 157 − CREATING DIRECTORY TREE OR SUB-TREE
2. Select Create a new domain tree and click Next. New

Domain Name window appears as shown in Figure 158.
FIGURE 158 − SPECIFYING NEW DOM AIN NAME
3. Enter the full DNS domain name. Here, it is ZTEDOMAIN.

Click Next. Database and Log File Locations window

FIGURE 159 − SETTING DATAB ASE AND LOG FILE LOCATION
4. Select default values for database location and log location.

Click Next. Confirm DNS Configuration window appears
FIGURE 160 − CONFIRMING DNS CONFIGURATION
5. Click OK. Configure DNS window appears as shown in

Figure 161.

FIGURE 161 − CONFIGURING DNS
6. Select Yes, install and configure DNS on this computer

(recommended). Click Next. Permissions window
FIGURE 162 − PERMISSIONS
7. Select Permissions compatible with pre-Windows 2000

servers. Click Next. Specify Administrator Password

FIGURE 163 − SPECIFYING ADMINISTRATOR P ASSWORD
8. Input directory service resumption password. Click Next.

Configuring Active Directory… window appears as shown
in Figure 164.
FIGURE 164 − CONFIGURING ACTIVE DIRECTORY
9. When configuration is complete, the final window appears as


FIGURE 165 − COMPLETING THE ACTIVE DIRECTORY INSTALLATION WIZARD
10. Click Finish to close installation wizard. The system prompts

to restart windows as shown in Figure 166.
FIGURE 166 − PROMPT OF RESTARTING SYSTEM
11. Click Restart Now to restart Windows.
END OF STEPS
Result NETNUMENCLUSTER1 is updated to be master domain server.
Backup Domain
Configure NETNUMENCLUSTER1 as the backup domain

server.
Steps To configure the backup domain, perform the following steps:
1. Run the dcpromo command on NETNUMENCLUSTER2.
Welcome window appears as shown in Figure 167.

FIGURE 167 − WELCOME INTERFACE
2. Click Next. Domain Controller Type window appears as

FIGURE 168 − DOMAIN CONTROLLER TYPE
3. Select Additional domain controller for an existing

domain. Click Next. Network Credentials window appears

FIGURE 169 − NETWORK CREDENTIALS
4. Input the password. Click Next to add NETNUMENCLUSTER2

to the main domain controller.
END OF STEPS
Result NETNUMENCLUSTER2 is set to be backup domain controller.
Installing VCS HA Software

Purpose To install VCS HA software.
Steps To install VCS HA software, perform the following steps:
1. Insert VCS4.3 for Windows install disk. Select product to
install window appears as shown in Figure 170.

FIGURE 170 − SELECT PRODUCT TO INSTALL
2. Select Storage Foundation HA 4.3 for Windows. Select

install type window appears as shown in Figure 171.
FIGURE 171 − SELECT INSTALL TYPE
3. Select Complete/Custom. License window appears as


FIGURE 172 − LICENSE
4. Input license key. Click Add button. Then, click Next.

Options Selections 1 window appears as shown in Figure
173.
FIGURE 173 − OPTIONS SELECTIONS 1
If there is only one heartbeat network card on the computer,

select VxCache only.
If there are two heartbeat network cards on the computer,
select VxCache, DMP under Dynamic Multipathing as

FIGURE 174 − OPTIONS SELECTIONS 2 (WITH TWO HEARTBEAT NETWORK

CARDS)
Note: Sometimes, Dynamic Multipathing option is grayed due

to VCS licence limitation. Select VxCache only.
5. Click Next and Options Selections 3 window appears as


6. Select VERITAS Cluster Server Database for SQL. Click

Next and Options Selections 4 window appears as shown
in Figure 176.
7. Select VERITAS Storage Foundation HA 4.3 for

Windows (Client Components). Click Next and
Computer Selection window appears as shown in Figure
177.
FIGURE 177 − COMPUTER SELECTION

8. Select domain and computers for Cluster. Select install path

(Ensure that the install space is larger than 1 G.). Click Next.
Validation window appears as shown in Figure 178.
FIGURE 178 − V ALID ATION
9. Click Next. Install Report window appears as shown in

Figure 179.
FIGURE 179 − INSTALL REPORT
10. Click Install to start installation. Figure 180 shows

installation progress.

FIGURE 180 − INSTALL PROCESS
11. When the installation is completed, Install Summary

FIGURE 181 − INSTALL SUMM ARY
12. Click Next. Reboot Remote Computers window appears as


FIGURE 182 − REBOOT REMOTE COMPUTERS
13. Select ZTECLUSTER2. Click Reboot. The system gives a

prompt about reboot status as shown in Figure 183.
FIGURE 183 − REBOOT STATUS
14. Click Next. Thank you for using VERITAS Storage

Foundation HA 4.3 for Windows window appears as

F I G U R E 1 8 4 − T H A N K Y O U F O R U S I N G V E R I T AS S T O R A G E F O U N D A T I O N H A
4.3 FOR WINDOWS INTERFACE
15. Click Finish to complete the installation. The system gives a

prompt dialogue box, asking whether to reboot your local
computer now or not, as shown in Figure 185.
FIGURE 185 − PROMPT DIALOGUE BOX, ASKING WHETHER TO REBOOT YOUR

LOCAL COMPUTER OR NOT
16. Click Yes to reboot the local computer NETNUMENCLUSTER1.
END OF STEPS
Result VCS software installation on computers is complete.
Creating Disk Array Logical Partition

After installing VCS software, it is required to create disk groups
and volumes. That is to divide disk logically and format the disk.

Creating Disk Group
Purpose To create disk groups.

Create the disk group ‘sql-dskgrp’ for sqlserver database.
Steps To create the disk group, perform the following steps:
1. Turn OFF NETNUMENCLUSTER2. Divide the disk array of
NETNUMENCLUSTER1.
2. On NETNUMENCLUSTER1, open Start Æ VERITAS Æ
VERITAS Enterprise Administrator (VEA). VERITAS
Enterprise Administrator window appears as shown in
Figure 186.
F I G U R E 1 8 6 − V E R I T AS E N T E R P R I S E A D M I N I S T R A T O R
There are two new disks under localhost – Disks: Harddisk0

and Harddisk2. Both of them are in No signature state.
3. Select Harddisk0. Right click on it. Select Write Disk
Signature. Localhost-Write Disk Signature window

FIGURE 187 − LOCALHOST-WRITE DISK SIGNATURE
4. Select Harddisk0 and Harddisk2. Click OK. Finish writing a

signature for the two new disks.
5. Select Disk Group on the VERITAS Enterprise
Administrator interface as shown in Figure 186. Right click
on it. Select New Dynamic Disk Group. Localhost-New
Dynamic Disk Group Wizard 1 window appears as shown
in Figure 188. Create a new disk group sql-dskgrp, which is
used to store data files of sqlserver database.
FIGURE 188 − LOCALHOST-NEW DYNAMIC DISK GROUP WIZARD 1

6. Select disk-Harddisk0 in disk array. Click Add. Input the disk

group name sql-dskgrp. Click Next. Localhost-New
Dynamic Disk Group Wizard 2 window appears as shown
in Figure 189.
7. Click Next and Localhost-New Dynamic Disk Group

Wizard 3 window appears as shown in Figure 190.
8. Click Finish to finish creating the disk group sql-dskgrp.
END OF STEPS
Result The disk group ‘sql-dskgrp’ for sqlserver database is created.

Create the disk group ‘nms-dskgrp’ for NM program.

Steps To create disk group ‘nms-dskgrp’ for NM program, follow the
same steps used for creating sql-dskgrp.
Select Harddisk2. The name of the hard group is nms-dskgrp.
Result After hard disk groups of sql-dskgrp and nms-dskgrp are created,
the whole hard disk group is created, as shown in Figure 191.
FIGURE 191 − CREATING HARD DISK GROUP COMPLETED
Creating Volume
Purpose After creating disk groups, it is required to create volumes for

storing shared data, including sql-data for sql server and nms-
data for NM programme.
Create sql-data volume.
Steps To create volume, perform the following steps:
1. Select sql-dskgrp under Disk Groups. Right click on it.
Select New Volume to create a new logical volume.
Localhost-New Volume Wizard 1 window appears as

FIGURE 192 − LOCALHOST-NEW VOLUME WIZARD 1
2. Select sql-dskgrp. Click Next. Localhost-New Volume

Wizard 2 window appears as shown in Figure 193.
3. Input sql-data in the volume name text box and 136G in

the size box. Click Next. Localhost-New Volume Wizard 3

4. Select Assign a drive letter. It is S: here. Click Next.

5. Select NTFS for the file system. Select Perform a quick

format to format sql-data volume quickly. Click Next.

6. Click Finish to finish creating sql-data volume and format.
END OF STEPS
Result sql-server volume is created.
Create nms-data volume.

Steps To create and format nms-data volume, perform the same steps
used for creating sql-data volume.
Create nms-data volume on nms-dksgrp disk group. The volume
size is 140 G. The driver letter is N:.
VCS Software Configuration - Create

Cluster
Purpose After installing VCS software, it is required to create cluster for
both computers.
Steps To create clusters, perform the following steps:
1. Select Start Æ Programme Æ VERITAS Æ VERITAS
Cluster Server Æ VCS Configuration Wizard as shown in
Figure 197. Welcome window appears as shown in Figure
198.

FIGURE 197 − STARTING VCS CONFIGURATION WIZARD
FIGURE 198 − WELCOME INTERFACE
2. Click Next. Options window appears as shown in Figure 199.

FIGURE 199 − CONFIGURATION OPTIONS
3. Select Cluster Operations. Click Next. Domain Selection

1 window appears as shown in Figure 200.
FIGURE 200 − DOMAIN SELECTION 1
4. The system gives out current domains. Select the current

one. Click Next. Domain Selection 2 window appears as

FIGURE 201 − DOMAIN SELECTION 2
5. Select systems of NETNUMENCLUSTER1 and

NETNUMENCLUSTER2. Click Next to discover system, as
FIGURE 202 − DISCOVERING SYSTEM
6. VCW Options window appears as shown in Figure 203.

FIGURE 203 − VCW OPTIONS
7. Select Create New Cluster. Click Next. Cluster Details

FIGURE 204 − CLUSTER DETAILS
Cluster Name: Input zte-clu.

Cluster ID: Randomly
Operating System: Select the current operating system.
Select the system to create the cluster.
8. Click Next. Validate Systems window appears as shown in
Figure 205.

FIGURE 205 − V ALID ATE SYSTEMS
9. Click Next. NIC Selection window appears as shown in

Figure 206.
FIGURE 206 − NIC SELECTION
Select the relevant network card as heartbeat card. At least

two network cards are required. Use service network card as
heartbeat card. Set service network card to be low priority.
Select one service network card. Right click on it, as shown
in Figure 207.

FIGURE 207 − SET SERVICE NETWORK CARD TO BE LOW PRIORITY
10. Click Next. Service Account window appears as shown in

Figure 208.
FIGURE 208 − SERVICE ACCOUNT
11. Select Existing user. Select Administrator from the drop-

down list. Click Next. Input the domain administrator
password. Click OK. Security window appears as shown in
Figure 209.

FIGURE 209 − SECURITY
12. Use default values. User Name is admin and Password is

password. Click Next. Summary window appears as shown
in Figure 210.
FIGURE 210 − SUMM ARY
13. Click Configure. Use the selected node to create a new

cluster. After the new cluster is successfully created, the
Finish window appears as shown in Figure 211.

FIGURE 211 − FINISH
14. Click Finish to exit VERITAS Cluster Configuration

Wizard.
END OF STEPS
Result Cluster is successfully created.
Installing Sqlserver Database

Purpose It is required to install SQL Server 2000 Enterprise on both
NETNUMENCLUSTER1 and NETNUMENCLUSTER2.
Install SQL Server 2000 database on NETNUMENCLUSTER1.
Steps To install SQL Server 2000 database on NETNUMENCLUSTER1,
perform the following steps:
1. Click Start Æ VERITAS Æ VERITAS Enterprise
Administrator (VEA) menu. Select sql-dskdg disk group.
Right click on it and select Import Dynamic Disk Group.
Result: It is possible to access disk S:\ from Explorer of
NETNUMENCLUSTER1.
2. Create a sqldata directory in S:\ to locate data files of
sqlserver database.
If the Close Window prompt box pops up during sqlserver
database installation, open Computer Management Æ
Services to disable VERITAS Enterprise Administrator
Service.
3. Install SP3 patch or above

4. Uninstall S:\ from NETNUMENCLUSTER1. (Select ztedisk-dg

disk group. Right click on it and select Deport Dynamic
Disk Group.)
Result: After that, it is impossible to access disk S:\ from
Explorer of NETNUMENCLUSTER1.
END OF STEPS
Result SQL Server 2000 is installed on NETNUMENCLUSTER1.
Install SQL Server 2000 database on NETNUMENCLUSTER2.

Steps To install SQL Server 2000 database on NETNUMENCLUSTER2,
1. Click Start Æ VERITAS Æ VERITAS Enterprise
Administrator (VEA) menu on NETNUMENCLUSTER2.
Select sql-dskdg disk group. Right click on it and select
Import Dynamic Disk Group.
Result: After that, it is possible to access S:\sqldata from
Explorer of NETNUMENCLUSTER2.
2. Change sqldata directory to be sqldata_backup. Then, create
a new S:\sqldata. Put database file of NETNUMENCLUSTER2
into the new S:\sqldata directory.
3. Install SQL Server2000 Enterprise database on
NETNUMENCLUSTER2. Put sqlserver data files on disk array,
namely, S:\sqldata.
Installing SQL Server2000 Enterprise database on
NETNUMENCLUSTER2 is the same as that of installing on
NETNUMENCLUSTER1.
4. Install SP3 patch or above
5. Delete S:\sqldata_backup directory after installing database
and patch on NETNUMENCLUSTER2 successfully.
END OF STEPS
Result SQL Server 2000 is installed on NETNUMENCLUSTER2.
Configure SQL Server Startup Type

Purpose To configure SQL Server startup type to be manual on both
computers.
Steps To configure SQL Server startup type, perform the following
steps:
1. Double-click the sqlserver icon at the right corner of the
computer. SQL Server Server Manager window appears as

FIGURE 212 − SQL SERVER M AN AGER
2. Do not select Auto start service when OS starts as shown

in Figure 213.
FIGURE 213 − CHANGING SQL SERVER AUTOMATIC STARTUP TO BE M ANUAL

STARTUP
END OF STEPS
Result SQL startup type is configured successfully.
Installing NMS
Purpose Install the NMS on the share disk N, namely N:\NETNUMEN (It is
specified while creating volumes).
Principles Install NM program on both computers if NM installation
program modifies Windows registry.
Install NM program on either of two computers if NM
installation program does not modify Windows registry.

For NetNumen N31（V4.2.0） series NM programme, install

NM program on either of two computers if NM installation
program does not modify Windows registry.
Steps To install NMS on the share disk, perform the following steps:
1. Connect nms-dskgrp to VEA. Open VEA. Select nms-dskdg
disk group. Right click on it. Select Import Dynamic Disk
Group.
Result: It is possible to access N:\ from Explorer of
NETNUMENCLUSTER1.
2. Create a NETNUMEN directory on N:\ for NM server program.
3. Install NM server on NETNUMENCLUSTER1.
END OF STEPS
Result NetNumen N31（V4.2.0） NM program installation is completed.
VCS Software Configuration –

Create SqlServer Resource Group
Purpose To create a resource group in cluster for SQL Server,
implementing the changeover of SQL Server between the two
computers.
Steps To create a resource group in cluster, perform the following
steps:
1. Select Start Æ Programs Æ VERITAS - VERITAS Cluster
Server Æ Database Agent for SQL Æ SQL Configuration
Wizard as shown in Figure 214.
FIGURE 214 − STARTING VCS M AN AGEMENT
2. Start VCS management interface. Select Configuration

Option window appears as shown in Figure 215.

FIGURE 215 − SELECT CONFIGURATION OPTION
3. Select MS-SQL Server – Service Group Configuration.

Click Next. Service Group Configuration window appears
FIGURE 216 − SERVICE GROUP CONFIGURATION
4. Input sqlserver-grp in the Service Group Name text box.

Select both NETNUMENCLUSTER1 and NETNUMENCLUSTER2
in the Available Cluster Systems box. Click to add
them to the Systems in Priority Order box. Click Next.
SQL Server Instance Selection window appears as shown
in Figure 217.

FIGURE 217 − SQL SERVER INSTANCE SELECTION
5. Do not select Search option. Click Next. Detail Monitoring

Configuration window appears as shown in Figure 218.
FIGURE 218 − DETAIL MONITORING CONFIGURATION
6. Do not select any option. Click Next. Registry Replication

Path window appears as shown in Figure 219.

FIGURE 219 − REGISTRY REPLICATION P ATH
7. Input the registry replication path (Generally, the path

resides on sql-data volume. Here, it is disk S.). Click Next.
Virtual Server Configuration window appears as shown in
Figure 220.
FIGURE 220 − VIRTUAL SERVER CONFIGURATION
Input following parameters:

Virtual Server Name: It is random.
Virtual IP Address: It is an external virtual IP of SQL
server.
Subnet Mask

Specify the adapter to be used on each system.

8. Click Next. Service Group Summary window appears as
FIGURE 221 − SERVICE GROUP SUMM ARY
9. Click Next to create SqlServer resource group. When

configuration completes, Configuration Complete window
FIGURE 222 − CONFIGURATION COMPLETE
10. Click Finish.

END OF STEPS
Result Sqlserver resource group configuration in VCS is complete.

VCS Software Configuration

VCS software configuration includes:
Configure sqlserver resources
Configure NetNumen N31（V4.2.0） NM resources
Upgrade VCS license
Note: Remember to save all modifications after configuring VCS

software. Click the third icon on tool bar in the VERITAS Cluster
Manager - Java Console window to save the setting.
Configuring sqlserver Resources
Purpose To configure sqlserver resources.

Create SQL Server resource group (sqlserver-grp).
Steps To create SQL Server resource group (sqlserver-grp), perform
1. Select Start Æ Programs Æ VERITAS - VERITAS Cluster
Manager – Java Console as shown in Figure 223. Start the
VERITAS Cluster Manager – Java Console interface.
FIGURE 223 − STARTING VCS M AN AGEMENT
2. Select New Cluster in the interface. Connectivity

Configuration window appears as shown in Figure 224.

FIGURE 224 − CONNECTIVITY CONFIGURATION
3. Input 10.40.88.139 in the Host name text box. Click OK.

Login window appears as shown in Figure 225.
FIGURE 225 − LOGIN
4. Input admin as User name and password as password.

Click OK. Cluster Explorer window appears as shown in
Figure 226.
FIGURE 226 − CLUSTER EXPLORER
END OF STEPS
Result As shown in Figure 226, SQL Server service resource group of
sqlserver-grp has been added in VCS system.

Modify sqlserver-grp attributes, including:

f AutoStartList
f File system resource (MountV)
f AutoFileSystem Clean
AutoStartList The value of AutoStartList needs be NETNUMENCLUSETER2,
NETNUMENCLUSETER1 in sequence.
If the sequence is wrong, follow the given steps to modify it.
Steps Select sqlserver-grp. Click the Properties tab. Click button
behind AutoStartList. AutoStartList window appears as shown
in Figure 227. Click to add the item. Click to delete the

item. Modify the sequence to be as shown in Figure 227. Then,
click OK.
FIGURE 227 − AUTOSTARTLIST
Related AutoStartList attribute settings decide on which system the

Information sqlserver-grp resource group (namely, Sqlserver database) runs
in priority when both systems are restarted. In this instance, the
sqlserver-grp resource group runs on NETNUMENCLUSTER2 in
priority. The setting is contrary to AutoStartList attribute setting
of NM resource, ensuring that sqlserver database and NM server
run on different systems by default.
File System Set the attribute of file system resource (MountV) to be force
Resource unmount.
(MountV)
Steps In the Cluster Explorer window as shown in Figure 226, select

MountV. Click the Properties tab. Click the button on the
Force Unmount row. ForceUnmount window appears as

shown in Figure 228. Select All from the Scalar Value drop-
down list. Click OK.
FIGURE 228 − FORCEUNMOUNT
AutoFileSystem Modify AutoFileSystem Clean attribute to be true.

Clean
Figure 229 shows the window after modification.
FIGURE 229 − MODIFIED CONFIGURATION
END OF STEPS
Result sqlserver-grp attributes are modified successfully.
Configuring NetNumen N31 NM Resources
Purpose To configure NetNumen N31 NM resources.

Configure NM server
Prerequisite Sqlserver database is started normally on either of the two
computers.
If it is not started, perform as follows.

1. Open the VERITAS Cluster Manager - Java Console.

2. Select sqlserver-grp. Right click on it.
3. Select online - NETNUMENCLUSTER1.
4. Start Sqlserver database on NETNUMENCLUSTER1.
5. Mount the NM installation path N:\ NETNUMEN on
NETNUMENCLUSTER1. Then, start configuring NM server.
Steps To configure NM server, perform the following steps:
1. Initialize NM server database.
Run N:\NETNUMEN\ums-svr\docs\dbscript\install-
db\uep\install.bat to initialize NetNumen N31 NM server
database.
2. Perform system configurations on NM server.
For detailed configurations, refer to the Figure 230 section.
This section just introduces settings, which have influence on
NM server startup, including:
f NM server startup parameter
i. Run N:\NETNUMEN\ums-
svr\output\tools\configcenter\bin\ run.bat to start NM
configuration center tool, as shown in Figure 230.
FIGURE 230 − NETNUMEN NM CONFIGURATION CENTER
ii. Set database IP address connected to NM server. Here,

the IP is the floating IP and Sqlserver database,
10.40.88.14. Select test connection and optimization
configuration.
iii. Test connection: Test whether it is possible to connect
the database normally with current database parameters.
If parameters are wrong, the database is not enabled or
the database is faulty, the system reports error.

iv. Optimization configuration: Optimize the database

automatically (mainly for SQL Server database), including
set backup mode to be Simple, cleaning database log
and compressing log.
Note: Switch Sqlserver database over to NETNUMENCLUSTER2.

Start NM configuration center. Select optimization configuration to
optimize Sql server database attributes on NETNUMENCLUSTER2.
f Server multiple IP addresses setting

For dual systems, the server has multiple IP addresses. It
is required to perform the below settings:
Modify the following parameters in the ‘\ums-
svr\netnumen\ip\dsl\dsl-base.par\conf\IPMS_param.xml’
file.
<FTP_PARAMETERS
FTPIPAddress="localhost" />
Change FTPIPAddress="localhost to be the NM IP address
with which NE can use ftp.
END OF STEPS
Result It is successful to start NM server on both computers.
Follow-up Normally, it is successful to start NM server on
Action NETNUMENCLUSTER1. Close the NM server. Uninstall
N:\NETNUMEN from NETNUMENCLUSTER1. Mount N:\NETNUMEN
to NETNUMENCLUSTER2. It is also successful to start NM server
on NETNUMENCLUSTER2.
Add NM server resources in VCS.
Prerequisite Select Start Æ Programs Æ VERITAS Æ VERITAS Cluster
Manager Æ Java Console to open VCS management interface
Resources NM server-related resources contain:
NM server resource group (nms-grp)
Disk group resource (VMDg)
Share disk resource (MountV)
Network interface card resource
Virtual IP resource
NM program resource
Steps To add NM server resources in VCS, perform the following steps:
1. Create NM server resource group (nms-grp).

i. Right click on zte-clu as shown in Figure 226. Select Add

Service Group. Add Service Group window appears as
FIGURE 231 − ADD SERVICE GROUP
ii. Input nms-grp in the Service Group name text box.

Select NETNUMENCLUSTER1 and NETNUMENCLUSTER2.
Check Startup. Click OK. NM resource group (nms-grp)
is created as shown in Figure 232.
FIGURE 232 − CREATING NM RESOURCE GROUP (NMS-GRP)
iii. Make sure two points:

The sequence of AutoStartList of nms-grp is:

group nms-grp (AutoStartList = { NETNUMENCLUSTER1,

NETNUMENCLUSTER2})
Related AutoStartList decides on which system nms-grp runs in priority
Information when both systems are restarted. In this instance, nms-grp runs
on NETNUMENCLUSTER1 in priority. The setting is contrary to
AutoStartList for sqlserver-grp resource, ensuring that sqlserver
database and NM server run on different systems by default.
The value for AutoStart is true.
It indicates that when the system is started, nms-grp
enabled automatically.
2. Add VMDg resource to nms-grp.
Right click on nms-grp in Creating NM Resource Group
(nms-grp) interface as shown in Figure 232. Select Add
Resource. Add Resource window appears as shown in
Figure 233.
FIGURE 233 − ADD RESOURCE
Select VMDg for Resource Type. Input nms-grp-VMDg in

Resource Name. Set the value of DiskGroupName to be
nms-dskgrp. Set the value of DGGuid. Select Critical and
Enabled. Then, click OK.
DGGuid is the unique ID of disk group in disk array. It is
used to identify the disk group. The following steps help to
get DGGuid.
i. Select Start Æ Run. Input the cmd command in the
Running interface as shown in Figure 234.

FIGURE 234 − RUNNING
ii. Click OK to open the dos window. Execute the

vmgetdrive command in dos window. The
VMDriveInfo.txt file is created under the directory (here,
it is d:) as shown in Figure 235.
FIGURE 235 − CREATING VMDRIVEINFO.TXT FILE
iii. Open the d:\ VMDriveInfo.txt file as shown in Figure

236.

FIGURE 236 − D:\ VMDRIVEINFO.TXT
iv. Find the DiskGroup GUID value corresponding to

DiskGroup Name = nms-dskgrp disk group. Copy it to
nms-grp-VMDg resource as DGGuid value.
Result: The nms-grp-VMDg resource is shown in Figure
237.
FIGURE 237 − NMS-GRP-VMDG RESOURCE

3. Add share disk resource (MountV).

i. Right click on nms-grp in the nms-grp-VMDg
Resource interface as shown in Figure 237.
ii. Select Add Resource. Select MountV for source type.
Input nms-grp-MountV for resource name.
iii. Input share disk information of NM program as follows:
f MountPath = "N:"
f VolumeName = nms-data
f VMDGResName = nms-grp-VMDg
f ForceUnmount = ALL
f AutoFSClean = 1
iv. Click OK.
Result: nms-grp-MountV resource is added as shown in
Figure 238, nms-grp-MountV resource is in blue, indicating
normal running.
FIGURE 238 − NMS-GRP-MOUNTV RESOURCE
4. Add network interface card resource

Related Both NM programme and Sqlserver database share the same
Information network interface card. The network interface card resource is
added in sqlserver resource group. It is required to create a
proxy network interface card resource in nms-grp NM resource
group, pointing to sqlserver-grp-NIC. It indicates that NM
resource group also uses sqlserver-grp-NIC as own network
interface card resource.

i. Right click on nms-grp in the nms-grp-VMDg

Resource interface as shown in Figure 237.
ii. Select Add Resource.
iii. Select Proxy for resource type. The resource name is
proxy NIC. Select Enable. Edit TargetResName to be
sqlserver-grp-NIC, the NIC resource name in sqlserver-
grp.
iv. Click OK.
Result: Adding proxy_NIC resource is complete as shown in
Figure 239, proxy_NIC resource is in blue, indicating normal
running.
FIGURE 239 − PROXY_NIC RESOURCE
5. Add virtual IP resource.

Related This IP resides on the computer which provides NM service.
Information Whatever NM server runs, there is only one IP address.
i. Right click on nms-grp the nms-grp-VMDg Resource
interface as shown in Figure 237.
ii. Select Add Resource.
iii. Select IP for resource type.
iv. Input nms_IP for resource name. Property settings for
nms_IP are the same as those of sqlserver-grp-IP of
sqlserver-grp resource group. For subnet mask and MAC
address, refer to sqlserver-grp-IP property setting.
Modify IP to be 10.40.88.44, the virtual IP of NM server.
Select Enabled.
Properties for IP nms-IP are:
f Address = 10.40.88.44
f SubNetMask = 255.255.255.0
f MACAddress @NETNUMENCLUSTER1 = 00-13-21-B5-F5-
0E
f MACAddress @NETNUMENCLUSTER2 = 00-14-38-B8-EE-
2D
v. Click OK.

Result: Adding nms_IP resource is complete.
6. Add NM program resource.

Purpose To implement VCS monitoring and management on NM program,
it is required to add NM server to VCS resource group as
program resource.
Preliminary Make preparations below:
Setup
i. Configure required parameters. Ensure it is possible to
start NM system manually.
ii. Copy N:\NETNUMEN\ums-svr\output\tools\cluster to
C:\cluster\cluster. Copy N:\NETNUMEN\ums-
svr\output\jdk-windows to C:\cluster\jdk-windows.
iii. Modify NM-related scripts. Modify moni_win.bat and
offline_win.vbs under N:\NETNUMEN\ums-
svr\output\tools\cluster\ as needed.
For moni_win.bat, modify two paths. Copy jdk-windows
to C:\Cluster\jdk-windows. moni_win.bat is under
C:\Cluster\cluster. The absolute path for moni_win.bat is:
set JDK_HOME=C:\cluster\jdk-windows
set MONI_HOME=C:\cluster\cluster
For offline_win.vbs, modify NM platform startup absolute
path to be executable path. For instance, the NM
programme is in N:\NETNUMEN\ums-svr. Modify the path
to be:
if ps.executablepath = "N:\NETNUMEN\jdk-
windows\bin\java.exe" then
Script for moni_win.bat is:
@echo on
rem -----------------------------------------------------------
------------
rem monitor ums Script on cluster for Win32
rem -----------------------------------------------------------
-------------
set JDK_HOME=C:\cluster\jdk-windows
set MONI_HOME=C:\cluster\cluster
ECHO %MONI_HOME%
%JDK_HOME%\bin\java -classpath
%MONI_HOME%;%MONI_HOME%\uep-util-

consoleagent.jar;%MONI_HOME%\uep-psl-cluster.jar
com.zte.ums.uep.psl.cluster.ConsoleStatus
ECHO %ERRORLEVEL%
if %ERRORLEVEL% == 1 exit 110

if %ERRORLEVEL% == 0 exit 100
Script for offline_win.vbs is
for each ps in getobject _
("winmgmts:\\.\root\cimv2:win32_process").instances_
If ps.name = "java.exe" Then

if ps.executablepath = "N:\NETNUMEN\jdk-
windows\bin\java.exe" then
wscript.echo ps.terminate
end if
End If
'wscript.echo
ps.handle&vbtab&ps.name&vbtab&ps.executablepath
Next
iv. Set NM configuration file
For parameters in NM configuration file of ums-
svr\platform\psl\ext-
service\console\conf\maincontroller.xml, it is
recommended to set them to be 1. In this way, the
console interface may pop up, for viewing NM status
conveniently.
<! – Whether the console has interface or not. The
parameter is set to be an integer. 1 – With interface, 0 –
Without interface>
<client-type>1</client-type>
Run ums-svr\bin\ console.bat to start the console with
interface manually. Select Start automatically while
starting the console, as shown in Figure 240. Then, close
console. When VCS starts console, console will start NM
server automatically.

FIGURE 240 − UMS NM PLATFORM SERVER CONSOLE
v. Copy NM-related scripts to dual systems.

Perform operations below on both systems.
Create a cluster directory in C:\.
Copy N:\NETNUMEN\ums-svr\tools\cluster to
C:\cluster\cluster.
Copy N:\NETNUMEN\ums-svr\jdk-windows to
C:\cluster\jdk-windows.
vi. Add NM resource.
Right click on nms-grp in the nms-grp-VMDg Resource
interface as shown in Figure 237. Select Add Resource
to add NM resource. Select Process for resource type.
Input NETNUMEN for resource name as shown in Figure
241.
FIGURE 241 − ADD NM RESOURCE

InteractWithDesktop: Set InteractWithDesktop to be

True.
StartProgram: Set StartProgram to be absolute path of
NM starting file, for instance, N:\NETNUMEN\ums-
svr\bin\console.bat.
StopProgram: Set StopProgram. The stop script is VBS
file. It is required to set command line: cscript /H:Cscript
/NOLOGO C:\cluster\cluster\offline_win.vbs.
MonitorProgram: Set MonitorProgram. Monitor
programme monitors the absolute path of NM monitor
script. Here, it is C:\cluster\cluster\ moni_win.bat.
Select Process Æ show all attribute Æ restartlimit.
Set the restart limit to be 3. Start the current system for
three times. If it still fails, switch over to another system
FIGURE 242 − SET RESTARTLIMIT TO BE 3
Note: For VCS4,2 version, there is no restartlimit attribute.

Result: The configured NM program resource is shown in Figure

243.
FIGURE 243 − NM PROGRAMME RESOURCE
Follow-up Add relationship.

Action
Select nms-grp. Select the Resource tab. Click link to add
relations between resources. This relationship chart is very
important. VCS decides starting and exiting sequence
according to the chart as shown in Figure 244.
FIGURE 244 − ADDING RELATIONSHIP
Test nms-grp, including two items below:

Make sure all resource settings are available after resources
are added in nms-grp. If the resource is grey, select it. Right
click on it. Select Enable. Check all parameters, Ensure all
resources are in Enable status.
Select nm-grp resource. Right click on it. Select online -
NETNUMENCLUSTER1 or (NETNUMENCLUSTER2). The NM

system can run on NETNUMENCLUSTER1 (or

NETNUMENCLUSTER2). Select nm-grp resource. Right click
on it. Select switch to - NETNUMENCLUSTER2
(NETNUMENCLUSTER1). The NM system can switch to
another system.
END OF STEPS
Result NetNumen N31 NM group resources (nms-grp) configuration is
complete.
Establish relationship between sqlserver-grp and nms-grp.
Purpose To establish the relationship sqlserver-grp and nms-grp,
ensuring that NM server can start normally after NM-related
resources are started.
Steps To establish relationship between sqlserver-grp and nms-grp,
1. Select cluster: zte-clu in VCS management interface. Select
the Service Group tab as shown in Figure 245.
FIGURE 245 − SERVICE GROUP
2. Click link. Link Service Groups window appears as shown

in Figure 246.

FIGURE 246 − LINK SERVICE GROUPS
3. Select online global and firm. Click OK.

4. Save configurations.
NOTE: Create a connection line pointing from nms-grp to
sqlserver-grp. It indicates that NM resource group relies on
database resource group.
END OF STEPS
Result Configurations on all VCS resources are complete. Figure 247
shows the status when all resources are in normal startup.
FIGURE 247 − ALL VCS RESOURCES ARE STARTED NORM ALLY

Upgrading VCS License
Purpose To update VCS license.

Steps To update the VCS license, perform the following steps:
1. Open the control panel. Select Add/Delete Programs. Find
VFSW4.1(Server Components) as shown in Figure 248.
FIGURE 248 − FINDING PROGRAM
2. Click Modify. A window for modifying options appears as

FIGURE 249 − MODIFYING OPTIONS
3. Select License Management. Click Next. License window


FIGURE 250 − LICENSE INTERFACE
The License interface as shown in Figure 250 shows License

of current Cluster. Click the current License to display details
of the current license.
4. Input a new License in the Enter a license key: text box.
Click Update. The new license is updated. The new license
information is displayed.
5. Click Remove to delete the expired License. Click Finish to
end the update.
END OF STEPS
Result VCS license is updated successfully.
Test Dual System Hot

Backup Software
Test VCS dual system running status for ensuring normal
operation. This section includes the following:
Test Single System
Test Dual System
Test Rules for Local Dual Hot Backup System
Test Single System

Purpose To test a single system.

Steps To test a single system, perform the following steps:

1. Select nms-grp.
2. Right click on it.
3. Select online ZXNMO1CLUSTER1. Resource groups are
started in the sequence set in the relationship. Test the
running of NETNUMENCLUSTER1 and NETNUMENCLUSTER2.
END OF STEPS
Result Single system is tested successfully.
Test Dual Systems

Purpose To test dual systems.
Steps To test dual systems, perform the following steps:
1. Manual switchover
Run nms-grp on NETNUMENCLUSTER1. Select
NETNUMENCLUSTER1. Select the switchover operation. The
nms-grp is switched over to NETNUMENCLUSTER2.
2. Automatic switchover when the programme on running node
is faulty.
When the programme on node running with resource group
is faulty, the system monitors the fault and switches the
resource group to the backup node automatically. Simulate a
programme fault manually to have a test. For instance,
terminate the process of sqlserver database or shut down NM
server manually.
3. Automatic switchover when running node is closed.
When the node running with resource group has hardware
fault or power problem, the system switches over to backup
node automatically. Simulate such a fault manually. For
instance, shut down NETNUMENCLUSTER1 when resource
group is running on NETNUMENCLUSTER. The resource group
will switch over to NETNUMENCLUSTER2 automatically.
END OF STEPS
Result Dual system is tested successfully.
Test Rules for Local Dual Hot

Backup System
Test rules for local dual hot backup system include:
Switch over resource groups manually. It is possible for NM
server to have a switchover between two systems.

Automatic switchover in faulty status.

f Terminate database progress manually. Sqlserver
database is switched over to the NM server system. The
dual system and NM server works normally.
f Terminate NM progress manually. If NM fails to restart for
three times, NM is switched to the sql database system.
NM server works normally.
f Disconnect all service network interfaces manually. The
system detects the fault and switches the resource group
to another system.
f Close node1 which is running sqlserver database. The
resource group is switched over to node2 automatically.
f Close node1 which is running NM resource group. The
resource group is switched over to node2 automatically.
f When both systems are restarted simultaneously,
sqlserver database and NM server run in different system.
Note: VCS technical support phone: 800-810-9771.

Prepare product serial number, which is available on the product
certificate.

Chapter 5
VCS4.0 for UNIX

Overview
System Installation
Configuring VCS System
NM Dual System Test Rules
System Security
Overview
This chapter covers the detailed installation and configuration of
NetNumen N31（ V4.2.0） dual hot backup system VCS4.0 in
Solaris9 operating system. Related contents are as follows:
Solaris9 operating system installation
Configuration requirements of disk array
VCS4.0 installation and configuration
Oracle9.i database installation
NetNumen N31 （ V4.2.0 ） NM server installation and
configuration
Dual Hot Backup Configuration

Requirements
Hardware and software requirements for NetNumen N31 (V4.2.0)
dual hot backup system are as follows:

NM server
Two UNIX servers with the same model and configurations
are required. The minimum configuration requirements are:
f Memory: Not less than 1 G
f Swap partition equals to the twice of real physical
memory.
f Three network interfaces: Two interfaces connect to
heartbeat cable for mutual monitoring. The third one
connects to public network cable for providing NM service.
f One disk array card for connecting disk array.
Disk array
f Set the disk in RAID1+0 array mode. Five disks are
required. Four disks are set in RAID1+0 array mode and
the fifth one is set to be hot spare, as the backup of the
other four disks.
f Data on disk array: Data files of NM server and oracle
database, and backup files of NM.
f Configure four LUN r66655. Here, take a disk array with
146 G as an instance. Table 19 lists the division of disk.
TABLE 19 − DISK P ARTITION
LUN Mount Path Function Min. Value

No. Value
1 /export/home/ora Oracle database ≥40 G 45 G
cle/oradata data files
2 /netnumen Install NM system ≥15 G 20 G
server program
3 /export/home/ba Data file backup ≥15 G 20 G
ckup
4 /export/home/ftp Save traffic statistic ≥40 G 60 G
files
Note: The number of LUNs and size of each LUN depend

on system requirements. For example, both database file
partition and NM server file partition depend on the scale of on-
site NM and database scale.
If it is required to install other programmes, which is under VCS
management, it is possible to add the number of LUN. Confirm
the number of LUN as required.

Chapter 5 VCS4.0 for UNIX
Operating system software

f Solaris9
f Operating system patch: The latest 9_Recommended
Dual system backup software
f VCS4.0
f If there is the latest VCS patch, install the latest patch.
Database software
f Oracle9.2 + Oracle database patch
f Install Oracle database programme in home region, for
instance, /export/home/oracle.
f Put Oracle data file on disk array. The mount point is
/export/home/oracle/oradata, for share data resource.
NM system software
f Install NM server software on disk array. The mount point
is /netnumen.
f Put NM data backup directory on disk array. The mount
point is /export/home/backup.
System Installation
Installing NM dual hot backup system VCS4.0 for UNIX include
the following:
Solaris9 operating system installation
Disk array partition
Setting network
Oracle database installation
VCS4.0 installation
Solaris9 Operating System

Installation
Purpose To install Solaris9 operating system.
Preliminary Use local CD-ROM driver to Install Solaris software on SPARC-
Setup based single system. Graphic operating interfaces are available
during installation.

Install Solaris9 system on both hosts. Take host names as

netnumencluster1 and netnumencluster2.
Steps To install Solaris9 operating system, perform the following steps:
1. Power ON the host. Insert CD-ROM SOLARIS SOFTWARE 1
of 2. Enter OK status. (If Solaris is installed before, press
Stop + A while starting the system.).
2. Input the boot cdrom command after the DOS prompt. Press
Enter. The system is restarted automatically.
3. Select language: English
4. Select area: English
5. Solaris installation program. Continue.
6. Identify the system. Continue.
7. Select Online for Network connectivity. Continue.
8. Select No for DHCP. Continue.
9. Select the default for network interface. Generally, it is eri0.
Continue.
Note: The list changes with various built-in network card

types, such as eri, ce and hme. If eri0 exists in the list, there is
eri network card. If ce0 exists, there is ce network card. If hme0
exists, there is hme network card.
Record available network cards for later use.
10. Input netnumencluster1 as the first host name. Continue.

11. Input 10.61.94.3 as the IP address of netnumencluster1.
Continue.
12. Select Yes for Subnet Continue.
13. Input 255.255.255.0 as network mask. Continue.
14. Select None for IPV6. Continue.
15. Select None for default route. Continue.
16. Confirm information. Continue.
17. Select None for security policy. Continue.
19. Select None for name service. Continue.
21. Select time zone, continue.
22. Select country and region. Continue.
23. Set date and time. Continue.


25. Select Initial for Solaris interactive installation program.
26. Select Standard for installation mode of Solaris interactive
installation program.
27. Select geographical region. Continue.
28. Select Entire Distribution plus OEM support 64-bit for
software. Continue.
29. Select c1t0d0 for disk.
Select c1t0d0 for boot disk. Click OK.
Select Configure EEPROM again.
30. Do not select 'Save data’. Continue.
31. Auto format file system. Continue.
32. The File System and Disk Format interface pops up. Select
the disk. Divide the disk.
Table 20 lists the c1t0d0 disk. Here, take the disk of 60 G as
an example.
TABLE 20 − C1T0D0 DISK PARTITION
Partition No. Mount to Size (G)

0 / 15 G
1 swap Twice of host memory
Overlap indicates the size of the
2 overlap
whole disk. Do not modify it.
3 /var 5G
Reserve one partition and 500 M
4 - space for creating MetaDB while
disk mirror.
5 - -
6 - -
The rest space, approximately 44
7 /export/home
G
33. Do not install remote file system. Continue.

34. Summary table for confirming boot system, language and
hardware setting. Continue.
35. Alarm (It is a system prompt about disk space including
unused disk space. Leave it.). Click OK.
36. Select Auto Reboot to start installation.
37. Wait for system installation and reboot.
38. Set hyper user’s password (root password). Input nms@zte.
Press Enter. Input the password again for confirmation.

39. Select CD/DVD for medium. Click Next.

40. Insert the CD of SOLARIS 9 SOFTWARE 2 of 2. Click OK to
start installation.
41. Installation summary. Click Next.
42. Select CD/DVD for medium. Click Next.
43. Insert the CD of SOLARIS 9 LANGUAGES. Click OK.
44. Click Install to start installation.
45. Installation summary. Click Exit.
46. Click Reboot.
47. Reboot the system.
Note:
Select zh.GBK while logs on to Solaris.
Select CDE for the first login.
END OF STEPS
Result Solaris9 operating system is successfully installed.
Installing Latest Solaris9 Patch
Purpose To install the latest patch for Solaris9 system.

Preliminary Download the patch from the SUN company website or ask one
Setup from the provider.
Generally, the recommended patch is 9_Recommended.zip.
Steps To install the latest patch for Solaris9 system, perform the
following steps:
1. Upload Solaris9 patch.
i. Log on to SUN server as root user.
ii. If the patch file resides on a computer with Windows
operating system, transfer the file to SUN server in FTP.
Remember to use binary mode file transmission.
f Modify /etc/ftpd/ftpusers file on SUN server. Note the
root line with #, release the ftp right of root user.
f Run FTP command on Windows system.
f Input root user’s user name and password.
f Input bin behind the ftp> prompt. The transmission mode
is changed to be binary mode.
f Use the put command under ftp> prompt to transfer the
patch file to the root directory of SUN server.

2. Install Solaris9 patch: 9_Recommended

i. Decompress the patch file of 9_Recommended.zip on
SUN server.
f Ensure root user has the right of reading the file.
f Depress the patch # unzip 9_Recommended.zip as root
user. Press Enter. A directory with 9_Recommended will
be created after depression.
ii. Enter the directory of 9_Recommended. Press return key.
iii. Install the patch packet as root user: # ./install_cluster.
Press Enter.
NOTE: There is a point before /.
iv. When the system prompts “Whether to install or not”,
input y. Press Enter. The auto installation starts. The
installation may last for one to four hours.
Note: Generally, if SCSI disk array is used, install the

patch 9_Recommended.zip from SUN. If fiber array is used,
install SUNWsan patch additionally. The array CD contains the
patch.
END OF STEPS
Result Solaris9 patch is successfully installed.
Disk Array Partition

Disk array Partition includes the following:
Hardware Connection
Requirements
SUN 3310 Disk Array Partition
Dividing SUN A1000 Disk Array
Hardware Connection
Figure 251 shows hardware connection. Host A refers to

netnumencluster1. Host B refers to netnumencluste2.
Connect Host A and Host B with two crossover cables used as
heartbeat cables. Both hosts use heartbeat cables to monitor the
opposite status. Connect SCSI cables to connect disk arrays.
Both hosts access to Internet via network interface.

FIGURE 251 − DUAL HOT BACKUP NM SYSTEM
Requirements
Take SUNA1000 disk array as an example to divide disk array. If

disk arrays of other models are used, follow the below given
requirements to divide the disk array.
1. Divide disk array in RAID1+0 mode.
Divide four disks in RAID1+0 mode. Set the fifth disk to be
global hot spare, which is the backup of other four disks.
2. Establish four LUN on RAID1 + 0 array.
One LUN saves data file of oracle database. Second LUN
saves NM server program. Third LUN saves backup NM data.
The fourth one saves traffic files.
Divide disk spaces of four logical drivers as needed.
Table 21 lists the four LUN disk spaces. Take the disk space of
146 G as an instance.
TABLE 21 − DISK P ARTITION
LUN Mount to Function Min. Value

No. Value
1 /export/home/ora Oracle database ≥40 G 45 G

cle/oradata data files
2 /netnumen Install NM ≥15 G 20 G
system server
program
3 /export/home/bac Data file backup ≥15 G 20 G
kup
4 /export/home/ftp Save traffic ≥40 G 60 G
statistic files

Note:
The number of LUNs and size of each LUN depend on system
requirements. For example, both database file division and
NM server file division depend on the scale of on-site NM and
database scale.
If it is required to install other programmes, which is under
VCS management, it is possible to add the quantity of LUN.
Confirm the number of LUNs as required.
3. Format the space on disk array to be file system.
SUN 3310 Disk Array Partition
Purpose To divide SUN 3310 disk array. If other disk arrays are used,
please refer to the attached disk array management guide.
Steps To divide the disk array, perform the following steps:
1. Set scisi ID.
Usually, 3310 has a controller. The default configuration is
suggested. After rebooting computer, press Stop + A,
execute below commands to detect whether the system can
identify SCSI card.
OK> probe-scsi-all
If system identifies SCSI card successfully, it shows the
usage of disk array. If not, the system gives a prompt.
OK> printenv, display each equipment situation and SCSI ID
number.
After establishment, execute boot –r command in OK status.
Reboot the system; the disk array can start running if SCSI
is in normal status.
2. Configure disk array.
i. Connect disk array to host using the attached console
cable. Input tip hardwire. Select Terminal (VT100
Mode). Enter configuration interface.
ii. Configure disk array’s controller.
View and edit channels－select 1 and 3 in sequence －
view and edit scsi id. Add master or slave controller. Do
not use the same id. Configure each interface with one
master and one slave controller.
iii. Divide Disk Array.
View and edit logical drive－create logical drive. Select
four hard disks and divide them as RAID + 0.

View and edit drives－add global spare drive. The fifth

disk is set to be hot spare, as the backup of the other
four disks.
iv. Establish LUN.
View and edit logical drives－partition logical drive. Divide
disk space into 45 G, 20 G, 20 G, 60 G in sequence.
v. MAP Disk.
View and edit host luns, map four LUNs separately.
vi. Modify /kernel/drv/sd.conf file and the target (Use the
format command to view). For example, if disk array is
c2t2d0, add the following contents into the file:
name="sd" class="scsi" class_prop="atapi"
target=2 lun=1;
target=2 lun=2;
target=2 lun=3;
vii. Execute #reboot -- -r to reboot system.
NOTE: Use “esc” to confirm operation.
3. Format disk array.
i. After dividing disk array, execute the following
commands to identify the disk.
#drvconfig
#disks
Or #devfsadm –C
ii. Use the format command to view disk array.
It displays that c1t0d0 is a local disk. The other four are
four LUNs of disk array. In this instance, the available
space for disk array is 146 GB.
f 45 GB for c3t0d0, for saving data files of Oracle database
f 20 GB for c3t0d1, for saving NM server program
f 20 GB for c3t0d2, for saving NM backup data
f 60 GB for c3t0d3, for saving NM traffic statistics files
Input the following black commands.
oot@ zxnm01cluster1 # format

Searching for disks...done
AVAILABLE DISK SELECTIONS:
0. c1t0d0 <SUN146G cyl 14087 alt 2 hd 24 sec 848>
/pci@9,600000/SUNW,qlc@2/fp@0,0/ssd@w500000e0110ff591,0

1. c3t0d0 <Symbios-StorEDGEA1000-0301 cyl 3994 alt 2 hd 64 sec 64>

/pseudo/rdnexus@4/rdriver@5,0
Specify disk (enter its number): 1

selecting c3t0d0
[disk formatted]
Warning: Current Disk has mounted partitions.
FORMAT MENU:
disk - select a disk
type - select (define) a disk type
partition - select (define) a partition table
current - describe the current disk
format - format and analyze the disk
repair - repair a defective sector
label - write label to the disk
analyze - surface analysis
defect - defect list management
backup - search for backup labels
verify - read and display labels
save - save new disk/partition definitions
inquiry - show vendor, product and revision
volname - set 8-character volume name
!<cmd> - execute <cmd>, then return
quit
format> p
PARTITION MENU:
0 - change `0' partition


select - select a predefined table
modify - modify a predefined partition table
name - name the current table
print - display the current table
label - write partition map and label to the disk
quit
partition> p
Current partition table (original):
Total disk cylinders available: 19998 + 2 (reserved cylinders)
Part Tag Flag Cylinders Size Blocks

0 root wm 0 - 127 128.00MB (128/0/0) 262144
1 swap wu 128 - 255 128.00MB (128/0/0) 262144
2 backup wu 0 -4398 43.05GB (19998/0/0) 40955904
3 unassigned wm 0 0 (0/0/0) 0
6 usr wm 256 – 4398 43.03GB (19742/0/0) 40431616
iii. Use the newfs command to establish the format disk

array to be file system.
#newfs /dev/dsk/c3t0d0s2
newfs: construct a new file system /dev/ dsk / c3t0d0s2:
(y/n)? y
…..
Format the other three partitions (c3t0d1s2，c3t0d2s2，
c3t0d3s2 ) in the same way.
Disk array is available after formatting.

END OF STEPS
Result SUN 3310 disk array partition is done successfully.

Dividing SUN A1000 Disk Array
Introduction Take SUNA1000 disk array as an example to divide disk array. If

disk arrays of other models are used, the required disk array
management software and partition may be different from those
for SUNA100 disk array. Please refer to attached disk array
management guide.
Purpose To divide disk array.
Steps To divide disk array, perform the following steps:
1. Set scsi ID.
i. Connect hardware as shown in Figure 251 . Start up the
host. Set the serial number of SCSI card. Set one host
with default value 7 and the other to be 6. Restart both
hosts to validate the setting.
ii. Press Stop + A. Execute below commands to detect
whether the system can identify SCSI card.
OK> probe-scsi-all
If it is successful to identify SCSI card, the system shows
the usage of disk array. If not, the system gives a wrong
prompt.
OK> printenv, displaying system information and SCSI
ID.
If SCSI ID numbers of both hosts are in collision to each
other, use the command below to set SCSI ID.
OK>setenv scsi-initiator-id 6, setting SCSI ID to be
6.
iii. Use the boot –r command to reboot the system.
Result: The disk array can be in normal operation if SCSI is
normal.
2. Install disk management software – RAID MANAGER
RAID MANAGER is a kind of software for managing disk array,
developed by SUN. The function of RAID MANAER is to
perform configuration and management on disk array of
SCSI interface, such as A1000/D1000. For different disk
array, the management software is various. For disk arrays
with other models, refer to attached disk array management
software.
It is very easy to install RAID MANAGER. Key points are:
i. Use the #/usr/sbin/pkgadd –d
/cdrom/cdrom0/Product command to install RAID
MANAGER.
Follow system prompts to implement installation.
ii. Use #reboot -- -r command to restart the system.

3. Dividing Disk Array

Divide four disks in RAID1+0 mode. Set the fifth disk to be
global hot spare. Divide four LUN.
4. Format disk array.
i. Execute the #drvconfig and #disks commands to
identify the disk.
ii. Use the format command to view disk array.
It displays that c1t0d0 is local disk. The other four are
four LUN of disk array. In this instance, the available
space for disk array is 146 G.
f 45 G for c3t0d0, for saving data files of oracle database
f 20 G for c3t0d1, for saving NM server program
f 20 G for c3t0d2, for saving NM backup data
f 60 G for c3t0d3, for saving NM traffic statistics files
root@ netnumencluster1 # format
Searching for disks...done
AVAILABLE DISK SELECTIONS:
0. c1t0d0 <SUN146G cyl 14087 alt 2 hd 24 sec
848>
/pci@9,600000/SUNW,qlc@2/fp@0,0/ssd@w500000e0110
ff591,0
1. c3t0d0 <Symbios-StorEDGEA1000-0301 cyl 3994
alt 2 hd 64 sec 64>
alt 2 hd 64 sec 64>
alt 2 hd 64 sec 64>
alt 2 hd 64 sec 64>
Specify disk (enter its number) 1

selecting c3t0d0
[disk formatted]
Warning Current Disk has mounted partitions.
FORMAT MENU:

disk - select a disk

type - select (define) a disk type
partition - select (define) a partition table
current - describe the current disk
format - format and analyze the disk
repair - repair a defective sector
label - write label to the disk
analyze - surface analysis
defect - defect list management
backup - search for backup labels
verify - read and display labels
save - save new disk/partition definitions
inquiry - show vendor, product and revision
volname - set 8-character volume name
quit
format> p
PARTITION MENU:
select - select a predefined table
modify - modify a predefined partition table
name - name the current table
print - display the current table
label - write partition map and label to the
disk
quit
partition> p
Current partition table (original):
Total disk cylinders available: 19998 + 2
(reserved cylinders)

Part Tag Flag Cylinders Size

Blocks
0 root wm 0 - 127 128.00MB
(128/0/0) 262144
1 swap wu 128 - 255 128.00MB
(128/0/0) 262144
2 backup wu 0 -4398 43.05GB
(19998/0/0) 40955904
3 unassigned wm 0 0
(0/0/0) 0
4 unassigned wm 0 0
(0/0/0) 0
5 unassigned wm 0 0
(0/0/0) 0
6 usr wm 256 - 4398 43.03GB
(19742/0/0) 40431616
7 unassigned wm 0 0
(0/0/0) 0
iii. Use the newfs command to create the disk array to be
file system.
#newfs /dev/dsk/ c3t0d0s2
Newfs: construct a new file system /dev/ dsk /
c3t0d0s2: (y/n)? y
…..
END OF STEPS
Result The disk array is available.
Follow-up Format the other three partitions in the same way.
Action
Setting Network
Purpose To set the network.
Preliminary Use both hme0 and hme1 as heartbeat network interfaces. Use
Setup Eri0 as service network interface of public network.
Note: Perform this operation on both systems.
Steps To set the network, perform the following steps:

1. Modify the /etc/profile file.
Use ‘vi’ or text editor to add contents below at the end of the
‘/etc/profile’ file.
PATH=/sbin:/usr/sbin:/opt/VRTSvcs/bin:$PATH

export PATH (Press Enter to go to the next line.)

2. Hosts allocation
The host names are: netnumencluster1 and
netnumencluster2
3. Public network interface card’s IP address allocation
Use eri0 as public network interface card. Allocate IP
addresses as follow:
10.61.94.3: netnumencluster1
10.61.94.30: netnumencluster12
Floating IP address
To ensure that the same IP is used wherever oracle database
runs, it is recommended to use floating IP. In this way, it is
possible for oracle database to run transparently on dual
systems.
To ensure that the same IP is used wherever NM server runs,
it is recommended to use floating IP too. In this way, it is
possible to provide transparent services to NM client.
Floating IP is set on the network interface card of public
network because it need provide external services.
Floating IP address for oracle database is 10.61.94.253. The
server name is oracledbsvr.
Floating IP address for NM server is 10.61.94.254. The
server name is nmssvr.
4. Check and modify contents of the ‘/etc/hosts’ file.
After modification, the ‘/etc/hosts’ file of netnumencluster1
has following contents:
127.0.0.1 localhost
10.61.94.3 netnumencluster1 loghost
10.61.94.30 netnumencluster2 # (It is for
accessing the other host while installing VCS.)
10.61.94.253 oracledbsvr
10.61.94.254 nmssvr
After modification, the ‘/etc/hosts’ file of zxnm02cluster1 has
following contents:
127.0.0.1 localhost
10.61.94.30 netnumencluster2 loghost
10.61.94.3 netnumencluster1 # (It is for
accessing the other host while installing VCS.)
10.61.94.253 oracledbsvr
10.61.94.254 nmssvr

5. Edit contents of network interface card file

The logical name corresponding to network interface card
name may vary due to different location. Sometimes, it is
required to configure a temporary IP address to confirm the
logical name of network interface card.
Execute the prtdiag command to view whether contents of
hme, ce and eri exist. Confirm the network interface card
type of public network, such as hme, ce and eri. The file
names may various according to different external network
interface card type.
Solaris9 Operating System Installation section describes the
built-in network interface card type. If both built-in network
interface card and external network interface card are hme,
their file names are hostname, ce0 and hostname, ce1
respectively. If external network interface cards are eri, their
file names are hostname, eri0 and hostname, eri1
respectively. If network interface cards of other types are
used, change eri according to the relevant network interface
card types.
Network interface card file on netnumencluster1
f The /etc/hostname.eri0 on netnumencluster1 must
contain the contents as below:
netnumencluster1
Network interface card file on netnumencluster2
f The /etc/hostname.eri0 on netnumencluster2 must
contain the contents as below:
netnumencluster2
6. Edit contents of the ‘/.rhosts’ file
For the ‘/.rhosts’ file of both hosts, the content is the ‘+’
mark. If there the ‘/.rhosts’ file does not exist, create it.
+ (Press the Enter key to another line.)
7. Check the contents of the ‘/etc/netmasks’ file
The ‘/etc/netmasks’ file is the subnet mask of the host:
10.61.92.0 255.255.252.0
8. Check the contents of the ‘/etc/ defaultrouter’ file.
The ‘/etc/defaultrouter’ file is the gateway setting of the host.
Add the gateway on both hosts. If the ‘/etc/defaultrouter’ file
does not exist, create it.
root@ netnumencluster2 # cat /etc/defaultrouter
10.61.95.254
Use #route add default 10.61.95.254 command to add
the gateway.
9. Restart the system

Use root@ netnumencluster1# init 6 command to restart

netnumencluster1 and netnumencluster2.
END OF STEPS
Result Network is successfully set.
Follow-up Use commands below to check:
Action
Use #hostname command to check the host name.
Use #ifconfig –a command to check IP address. There
need be one IP address for hme0, hme1 and eri0
respectively.
Installing Oracle Database

Installing oracle database on both hosts include the following:
Preparations before Installation
Installing Oracle Database on netnumencluster1
Modifying Oracle Database Service IP as Floating IP
Preparations before Installation
1. Create Oracle database mount point, for saving data files of

database.
Create a /export/home/oradata directory as oracle user, for
saving data files of Oracle database.
#su – oracle
$ pwd
/export/home/oracle
$mkdir oradata
2. Mount the data partition of oracle database on disk array, for
saving oracle data file.
#mount /dev/dsk/c3t0d0s2
/export/home/oracle/oradata
Then, use tdf –k command to see the
/export/home/oracle/oradata directory on netnumencluster1.
NOTE: Perform operations described in this section only on
one host, such as netnumencluster1.

Purpose To install oracle database on netnumencluster1.

Steps To install oracle database on netnumencluster1, perform the
following steps:
1. Install oracle database.
Install oracle and relevant patches on netnumencluster1. For
details, refer Installing Oracle 9i section.
NOTE: Put oracle database file on disk array. That is to input
/export/home/oracle/oradata on the Database File
Location interface.
2. Oracle database backup
i. Uninstall oracle data files from disk array.
#umount/export/home/oracle/oradata
#cd/export/home
ii. Back up database /export/home/oracle
#tar –cvf oracle.tar /export/home/oracle
iii. Back up database /export/home/ apache
#tar –cvf apache.tar /export/home/ apache
END OF STEPS
Result Oracle database on netnumencluster1 is installed successfully.
Purpose To install oracle database on netnumencluster2.

It is unnecessary to re-install oracle database on
netnumencluster2. Actually, it is to perform relevant
configurations on netnumencluster2 and copy database files
from netnumencluster1 to netnumencluster2.
Steps To install oracle database on netnumencluster2, perform the
following steps.
1. Set UNIX core parameters on Oracle9i.
Right click on the desktop. Select File Æ File Management
Program on the right-key menu. Enter the etc directory.
Open system files. Add UNIX core parameters to files ending
with Oracle9i (There should be no blanks at the starting and
ending of the file). Then, save the file.
set semsys:seminfo_semmni=100
set semsys:seminfo_semmns=1024
set semsys:seminfo_semmsl=256
set shmsys:shminfo_shmmax=4294967295

set shmsys:shminfo_shmmin=1
set shmsys:shminfo_shmmni=100
set shmsys:shminfo_shmseg=10
2. Create user group and oracle user.
At terminal, use ＃ admintool command to open system
administrator tool.
i. Add three user groups such as install, dba and apchadm
in system administrator tool.
Select View Æ User Group from system administrator
tool. Select Edit Æ Add menu. Add User Group window
appears. Input install, dba and apchadm in Group
Name column. Select default values for other columns.
Click OK.
ii. Add a user oracle (for Oracle database).
Select View Æ User in system administrator tool. Select
Edit Æ Add menu. Add User window appears. Configure
parameters as given below. Select default values for
unlisted parameters. Click OK.
f User name: oracle
f Primary group: install
f Secondary group: dba
f Log in Shell: Bourne
f Password: Normal password (It is required to input oracle
password twice. It is recommended to use oracle.)
f Create the main directory: Check the item.
f Main directory path: /export/home/oracle (It is supposed
that /expert/home is user division.)
iii. Add user apache (for Oracle HTTP Server).
Select View Æ User in system administrator tool. Select
Edit Æ Add menu. Add User window appears. Configure
parameters as given below. Select default values for
unlisted parameters. Click OK.
f User name: apache
f Primary group: install
f Secondary group: apchadm
f Log in Shell: Bourne
f Password: Normal password (It is required to input oracle
password twice. It is recommended to use apache.)
f Create the main directory: Check the item.
f Main directory path: /export/home/apache (It is
supposed that /expert/home is user division.)

NOTE: If it fails to use above-mentioned admintool

normally, use commands below to add three user groups
of install, dba apchadm and two users of oracle and
apache.
＃groupadd install
＃groupadd dba
＃groupadd apchadm
＃ useradd –d /export/home/oracle –g install –G
dba –m oracle
＃ passwd oracle (It is required to input oracle
password twice.)
＃ useradd –d /export/home/apache –g install –G
apchadm –m apache
＃ passwd apache (It is required to input apache
password twice.)
3. Copy oracle database files from netnumencluster1 to
netnumencluster2.
root@ netnumencluster2# rcp –p
netnumencluster1:/export/home/oracle.tar
/export/home
netnumencluster1:/export/home/apache.tar
/export/home
root@ netnumencluster2# rcp –rp netnumencluster1:
/var/opt/oracle /var/opt
Note: Modify directory right:
root@ netnumencluster2# chmod –fR 777
/var/opt/oracle
4. Decompress oracle database file.
i. Decompress oracle database files of oracle.tar and
apache.tar to the local.
root@ netnumencluster2# cd /export/home
ii. Decompress oracle.tar
root@ netnumencluster2# tar –xvf oracle.tar
iii. Decompress apache.tar.
root@ netnumencluster2# tar –xvf apache.tar
5. Modify machine name-related files.
i. Modify $ORACLE_HOME/network/admin/ listener.ora file:
Modify host= netnumencluster2
ii. Modify $ORACLE_HOME/network/admin/ tnsnames.ora
file: Modify host= netnumencluster2
NOTE: Remember to save operations.

6. Confirm whether it is successful to copy Oracle database.

Enable/disable operations manually to check whether it is
successful to create oracle database on netnumencluster2.
Follow steps below:
i. Mount oracle database files on disk array.
#mount /dev/dsk/c3t0d0s2
ii. Enable oracle database.
If it is successful to install oracle database on
netnumencluster2, Oracle database can be started
normally.
END OF STEPS
Result Oracle database is successfully configured on netnumencluster2.
Follow-up Step Back up oracle data files on disk array.
Backup files are used to resume Oracle database in faulty
situation.
root@ netnumencluster2# cd /export/home/oracle
root@ netnumencluster2# tar –cvf oradata.tar
Modifying Oracle Database Service IP as

Floating IP
Purpose To modify oracle database service IP to be floating IP.

Preliminary Ensure both systems are installed with oracle database.
Setup
The float IP is 10.61.94.253.
Steps To modify service IP, perform the following steps:
1. Modify $ORACLE_HOME/network/admin/ listener.ora file:
Modify host=10.61.94. 253
2. Modify $ORACLE_HOME/network/admin/ tnsnames.ora file:
Modify host=10.61.94. 253
NOTE: Perform operations on both systems.
Note: The database does not start if the floating IP

10.61.94.253 is not bound to the current computer. Use the
ifconfig –a command to view computer IP address.
END OF STEPS
Result The oracle database service IP is modified to be floating IP
successfully.

Installing VCS4.0
Purpose To install dual hot backup system software VCS4.0
Installing VCS Software
Purpose To install VCS software.

NOTE: Install VCS software on either of both hosts, such as
netnumencluster1. The installation program will install VCS
software to the other host automatically.
Preliminary Insert VCS installation CD storage_solutions_4.0 to
Setup netnumencluster1.
Steps To install VCS software, execute the following commands:
1. root@ netnumencluster1# pwd
/cdrom/storage_solutions_4.0_cd1
2. root@ netnumencluster1# ./installer
VERITAS Storage Solutions 4.0
Copyright (c) 2004 VERITAS Software Corporation. All rights

reserved.
VERITAS, the VERITAS Logo and all other VERITAS product

names and slogans
are trademarks or registered trademarks of VERITAS Software
Corporation.
VERITAS and the VERITAS Logo Reg. U.S. Pat. & Tm. Off. Other
product names
and/or slogans mentioned herein may be trademarks or
registered trademarks
of their respective companies.
VERITAS Licensing utilities are not installed on this system
Selection Menu:

I) Install/Upgrade a Product C) Configure an Installed

Product
L) License a Product P) Perform a Preinstallation
Check
U) Uninstall a Product D) View a Product Description
Q) Quit ?) Help
3. Enter a Selection: [I,C,L,P,U,D,Q,?] i

Install/Upgrade a Product
1) VERITAS File System (FlashSnap Option)

2) VERITAS Volume Manager (FlashSnap Option, VVR Option)
3) VERITAS Volume Replicator
4) VERITAS Cluster Server
5) VERITAS Cluster Server Traffic Director
6) VERITAS Storage Foundation (QuickStart, Standard,
Standard HA,
Enterprise, Enterprise HA, and VVR Option)
7) VERITAS Storage Foundation for Oracle (Standard,
Enterprise,
Enterprise HA, VVR Option)
8) VERITAS Storage Foundation for DB2 (Standard,
Enterprise, Enterprise
HA, VVR Option)
9) VERITAS Storage Foundation for Sybase (HA, FlashSnap
Option, VVR
Option)
10) VERITAS SANPoint Control QuickStart
11) VERITAS Enterprise Administrator GUI
B) Back to previous menu
4. Select a product to install: [1-11,b,q] 4

VERITAS Cluster Server
VERITAS CLUSTER SERVER 4.0 INSTALLATION
PROGRAM

Copyright (c) 2004 VERITAS Software Corporation. All rights

reserved.
VERITAS, the VERITAS Logo and all other VERITAS product

names and slogans
are trademarks or registered trademarks of VERITAS Software
Corporation.
VERITAS and the VERITAS Logo Reg. U.S. Pat. & Tm. Off. Other
product names
and/or slogans mentioned herein may be trademarks or
registered trademarks
of their respective companies.
5. Enter the system names separated by spaces on which to

install VCS: netnumencluster1 netnumencluster2
Checking system communication:
Checking OS version on
netnumencluster1............................. SunOS 5.9
Checking VRTSvcs package ................................ not
installed
Verifying communication with netnumencluster2...................
ping successful
Attempting rsh with netnumencluster2.............................
rsh successful
Attempting rcp with netnumencluster2.............................
rcp successful
Checking OS version on
netnumencluster2............................... SunOS 5.8
installed
Creating log directory on
netnumencluster2................................. Done
Logs for installer are being created in

/var/tmp/installer1115142948.
Using /usr/bin/rsh and /usr/bin/rcp to communicate with remote

systems.
Initial system check completed successfully.

6. Press [Return] to continue:

PROGRAM
VERITAS Infrastructure package installation:
Installing VERITAS Infrastructure packages on netnumencluster1:
Checking VRTScpi package ................................ not

installed
Checking VRTSvlic package ............................... not
installed
Checking file system space ................ required space is
available
Installing VRTScpi 4.0.5 on
netnumencluster1............................. Done
Installing VRTSvlic 3.02.005d on
netnumencluster1........................ Done
Installing VERITAS Infrastructure packages on netnumencluster2:
Checking VRTScpi package ................................ not

installed
Checking VRTSvlic package ............................... not
installed
available
Copying VRTScpi package to
netnumencluster2................................ Done
Installing VRTScpi 4.0.5 on
netnumencluster2............................... Done
Copying VRTSvlic.tar.gz to
netnumencluster2................................ Done
Installing VRTSvlic 3.02.005d on
netnumencluster2.......................... Done
VERITAS Infrastructure packages installed successfully.


PROGRAM
Each system requires a VCS product license before installation.

License
keys for additional product features should also be added at this
time.
Some license keys are node locked and are unique per system.
Other license
keys, such as demo keys and site license keys, are registered on
all systems
and must be entered on the first system.
VCS Licensing Verification:
Checking VCS license key on netnumencluster1.....................

not licensed
Enter a VCS license key for netnumencluster1: [?] PZP9-WSXK-
JTK8-TSBW-8PRC
Registering VERITAS Cluster Server DEMO key on
netnumencluster1
8. Do you want to enter another license key for

netnumencluster1? [y,n,q,?] (n)
Registering PZP9-WSXK-JTK8-TSBW-8PRC on netnumencluster2

Checking VCS license key on netnumencluster2................
Cluster Server Demo
9. Do you want to enter another license key for

netnumencluster2? [y,n,q,?] (n)
VCS licensing completed successfully.

PROGRAM

installer can install the following optional VCS packages:
VRTSobgui VERITAS Enterprise Administrator

VRTSvxfen VERITAS I/O Fencing
VRTSvcsmn VERITAS Cluster Server Man Pages
VRTSvcsdc VERITAS Cluster Server Documentation
VRTScssim VERITAS Cluster Server Simulator
VRTScscm VERITAS Cluster Server Cluster Manager
1) Install all of the optional packages

2) Install none of the optional packages
3) View package descriptions and select optional packages
11. Select the optional packages to be installed on all systems?

[1-3,q,?] (1)
PROGRAM
installer will install the following VCS packages:
VRTSperl VERITAS Perl 5.8.0 Redistribution
VRTSob VERITAS Enterprise Administrator Service
VRTSmuob VERITAS Enterprise Administrator Service
Localized Package
VRTSobgui VERITAS Enterprise Administrator
VRTSllt VERITAS Low Latency Transport
VRTSgab VERITAS Group Membership and Atomic Broadcast
VRTSvxfen VERITAS I/O Fencing
VRTSvcs VERITAS Cluster Server
VRTSvcsmg VERITAS Cluster Server Message Catalogs
VRTSvcsag VERITAS Cluster Server Bundled Agents
VRTSvcsmn VERITAS Cluster Server Man Pages
VRTScspro VERITAS Cluster Server VEA Provider
VRTSvcsdc VERITAS Cluster Server Documentation
VRTSjre VERITAS Java Runtime Environment Redistribution
VRTScutil VERITAS Cluster Utilities
VRTScssim VERITAS Cluster Server Simulator
VRTScscw VERITAS Cluster Server Configuration Wizards
VRTSweb VERITAS Java Web Server

VRTSvcsw VERITAS Cluster Manager (Web Console)

...continued:
VRTScscm VERITAS Cluster Server Cluster Manager

PROGRAM
Checking system installation requirements:
Checking VCS installation requirements on netnumencluster1:
Checking VRTSperl package ............................... not

installed
Checking VRTSob package ................................. not
installed
Checking VRTSmuob package ............................... not
installed
Checking VRTSobgui package .............................. not
installed
Checking VRTSllt package ................................ not
installed
Checking VRTSgab package ................................ not
installed
Checking VRTSvxfen package .............................. not
installed
installed
Checking VRTSvcsmg package .............................. not
installed
Checking VRTSvcsag package .............................. not
installed
Checking VRTSvcsmn package .............................. not
installed
Checking VRTScspro package .............................. not
installed
Checking VRTSvcsdc package .............................. not
installed

Checking VRTSjre package ................................ not

installed
Checking VRTScutil package .............................. not
installed
Checking VRTScssim package .............................. not
installed
Checking VRTScscw package ............................... not
installed
Checking VRTSweb package ................................ not
installed
Checking VRTSvcsw package ............................... not
installed
Checking VRTScscm package ............................... not
installed
Checking VERITAS patch 115209 ........................... not
installed
installed
installed
Checking for any Solaris patch issues ............................
None
available
Checking VRTSweb process .................................. not
running
Checking had process ...................................... not running
Checking hashadow process ................................. not
running
Checking CmdServer process ................................ not
running
Checking notifier process ................................. not running
Checking vxsvc process .................................... not
running
Checking vxfen driver ..................................... not running
Checking gab driver ....................................... not running
Checking llt driver ....................................... not running
Checking VCS installation requirements on netnumencluster2:
Checking VRTSperl package ............................... not

installed

Checking VRTSob package ................................. not

installed
Checking VRTSmuob package ............................... not
installed
Checking VRTSobgui package .............................. not
installed
Checking VRTSllt package ................................ not
installed
Checking VRTSgab package ................................ not
installed
Checking VRTSvxfen package .............................. not
installed
installed
Checking VRTSvcsmg package .............................. not
installed
Checking VRTSvcsag package .............................. not
installed
Checking VRTSvcsmn package .............................. not
installed
Checking VRTScspro package .............................. not
installed
Checking VRTSvcsdc package .............................. not
installed
Checking VRTSjre package ................................ not
installed
Checking VRTScutil package .............................. not
installed
Checking VRTScssim package .............................. not
installed
Checking VRTScscw package ............................... not
installed
Checking VRTSweb package ................................ not
installed
Checking VRTSvcsw package ............................... not
installed
Checking VRTScscm package ............................... not
installed
installed
installed
installed

Checking for any Solaris patch issues ............................

None
available
Checking VRTSweb process .................................. not
running
Checking had process ...................................... not running
Checking hashadow process ................................. not
running
Checking CmdServer process ................................ not
running
Checking notifier process ................................. not running
Checking vxsvc process .................................... not
running
Checking vxfen driver ..................................... not running
Checking gab driver ....................................... not running
Checking llt driver ....................................... not running
Installation requirement checks completed successfully.

PROGRAM

PROGRAM
It is possible to install VCS packages without performing

configuration.
VCS cannot be started without proper configuration.
It is optional to configure VCS now. If you choose to configure

VCS later,
you can either do so manually or run the installvcs -configure
command.
15. Are you ready to configure VCS? [y,n,q] (y)


PROGRAM
installer will now ask sets of VCS configuration-related questions.
When a [b] is presented after a question, 'b' may be entered to

go back to
the first question of the configuration set.
When a [?] is presented after a question, '?' may be entered for

help or
additional information about the question.
Following each set of questions, the information you have

entered will be
presented for confirmation. To repeat the set of questions and
correct any
previous errors, enter 'n' at the confirmation prompt.
No configuration changes are made to the systems until all

configuration
questions are completed and VCS is installed successfully.

PROGRAM
To configure VCS the following is required:
A unique Cluster name

A unique Cluster ID number between 0-255
Two or more NIC cards per system used for heartbeat links
One or more heartbeat links are configured as private links

One heartbeat link may be configured as a low priority link
All systems are being configured to create one cluster

17. Enter the unique cluster name: [?] ztevcs

18. Enter the unique Cluster ID number between 0-255: [b,?]
100
Discovering NICs on netnumencluster1.....................

discovered eri0 hme0 hme1
19. Enter the NIC for the first private heartbeat link on
netnumencluster1: [b,?] hme0
hme0 is currently active as a public NIC on netnumencluster1
20. Are you sure you want to use hme0 for the first private
heartbeat link? [y,n,q,b,?] (n) y
21. Would you like to configure a second private heartbeat link?
[y,n,q,b,?] (y) y
22. Enter the NIC for the second private heartbeat link on
hlrdbsrv1: [b,?] hme1
23. Would you like to configure a third private heartbeat link?
[y,n,q,b,?] (y) n
24. Do you want to configure an additional low priority heartbeat
link? [y,n,q,b,?] (n) y
25. Enter the NIC for the low priority heartbeat link on
netnumencluster1: [b,?] (eri0) eri0
26. Are you using the same NICs for private heartbeat links on
all systems? [y,n,q,b,?] (y) y

PROGRAM
Cluster information verification:
Cluster Name: ztevcs

Cluster ID Number: 100
Private Heartbeat NICs for netnumencluster1: link1=hme0
Second Private Heartbeat NICs for netnumencluster1:
link1=hme1
Low Priority Heartbeat NIC for netnumencluster1: link-
lowpri=eri0
Private Heartbeat NICs for netnumencluster2: link1=hme0
Second Private Heartbeat NICs for netnumencluster2:
link1=hme1

Low Priority Heartbeat NIC for netnumencluster2: link-

lowpri=eri0
Is this information correct? [y,n,q] (y) y

PROGRAM
The following information is required to configure Cluster

Manager:
A public NIC used by each system in the cluster

A Virtual IP address and netmask for Cluster Manager
27. Do you want to configure Cluster Manager (Web Console)

[y,n,q] (y) n

PROGRAM
The following information is required to configure SMTP

notification:
The domain-based hostname of the SMTP server

The email address of each SMTP recipient
A minimum severity level of messages to send to each
recipient
28. Do you want to configure SMTP notification? [y,n,q] (y) n

PROGRAM
The following information is required to configure SNMP

notification:
System names of SNMP consoles to receive VCS trap

messages
SNMP trap daemon port numbers for each console

A minimum severity level of messages to send to each

console
29. Do you want to configure SNMP notification? [y,n,q] (y) n

PROGRAM
VCS packages can be installed on systems consecutively or

simultaneously.
Installing packages on systems consecutively takes more time
but allows for
better error handling.
30. Would you like to install Cluster Server packages on all

systems simultaneously? [y,n,q,?] (y) y
Installing Cluster Server 4.0 on all systems simultaneously:
Copying VRTSperl.tar.gz to netnumencluster2..................

Done 1 of 69 steps
Installing VRTSperl 4.0.2 on netnumencluster2................
Done 2 of 69 steps
Installing VRTSperl 4.0.2 on netnumencluster1 ..............
Done 3 of 69 steps
Copying VRTSob.tar.gz to netnumencluster2....................
Done 4 of 69 steps
Installing VRTSob 3.2.514.0 on netnumencluster2..............
Done 5 of 69 steps
Copying VRTSmuob.tar.gz to netnumencluster2..................
Done 6 of 69 steps
Installing VRTSmuob 3.2.514.0 on netnumencluster2............
Done 7 of 69 steps
Installing VRTSob 3.2.514.0 on netnumencluster1 ............
Done 8 of 69 steps
Copying VRTSobgui.tar.gz to netnumencluster2.................
Done 9 of 69 steps
Installing VRTSmuob 3.2.514.0 on netnumencluster1 .........
Done 10 of 69 steps
Installing VRTSobgui 3.2.514.0 on netnumencluster2..........
Done 11 of 69 steps

Copying VRTSllt.tar.gz to netnumencluster2..................

Done 12 of 69 steps
Installing VRTSllt 4.0 on netnumencluster2.................. Done
13 of 69 steps
Installing VRTSobgui 3.2.514.0 on netnumencluster1 ........
Done 14 of 69 steps
Copying VRTSgab.tar.gz to netnumencluster2..................
Done 15 of 69 steps
Installing VRTSllt 4.0 on netnumencluster1 ................ Done
16 of 69 steps
Installing VRTSgab 4.0 on netnumencluster2..................
Done 17 of 69 steps
Copying VRTSvxfen.tar.gz to netnumencluster2................
Done 18 of 69 steps
Installing VRTSgab 4.0 on netnumencluster1 ................
Done 19 of 69 steps
Installing VRTSvxfen 4.0 on netnumencluster2................
Done 20 of 69 steps
Installing VRTSvxfen 4.0 on netnumencluster1 ..............
Done 21 of 69 steps
Copying VRTSvcs.tar.gz to netnumencluster2..................
Done 22 of 69 steps
Installing VRTSvcs 4.0 on netnumencluster2..................
Done 23 of 69 steps
Copying VRTSvcsmg.tar.gz to netnumencluster2................
Done 24 of 69 steps
Installing VRTSvcsmg 4.0 on netnumencluster2................
Done 25 of 69 steps
Copying VRTSvcsag.tar.gz to netnumencluster2................
Done 26 of 69 steps
Installing VRTSvcs 4.0 on netnumencluster1 ................ Done
27 of 69 steps
Installing VRTSvcsmg 4.0 on netnumencluster1 ..............
Done 28 of 69 steps
Installing VRTSvcsag 4.0 on netnumencluster2 ................
Done 29 of 69 steps
Installing VRTSvcsag 4.0 on netnumencluster1 ..............
Done 30 of 69 steps
Copying VRTSvcsmn.tar.gz to netnumencluster2 ................
Done 31 of 69 steps
Installing VRTSvcsmn 4.0 on netnumencluster1 ..............
Done 32 of 69 steps
Installing VRTSvcsmn 4.0 on netnumencluster2 ................
Done 33 of 69 steps

Installing VRTScspro 4.0 on netnumencluster1 ..............

Done 34 of 69 steps
Copying VRTScspro.tar.gz to netnumencluster2 ................
Done 35 of 69 steps
Installing VRTSvcsdc 4.0 on netnumencluster1 ..............
Done 36 of 69 steps
Installing VRTScspro 4.0 on netnumencluster2 ................
Done 37 of 69 steps
Copying VRTSvcsdc.tar.gz to netnumencluster2 ................
Done 38 of 69 steps
Installing VRTSvcsdc 4.0 on netnumencluster2 ................
Done 39 of 69 steps
Copying VRTSjre.tar.gz to netnumencluster2 ..................
Done 40 of 69 steps
Installing VRTSjre 1.4 on netnumencluster1 ................ Done
41 of 69 steps
Installing VRTSjre 1.4 on netnumencluster2 ..................
Done 42 of 69 steps
Installing VRTScutil 4.0 on netnumencluster1 .............. Done
43 of 69 steps
Copying VRTScutil.tar.gz to netnumencluster2 ................
Done 44 of 69 steps
Installing VRTScssim 4.0 on netnumencluster1 ..............
Done 45 of 69 steps
Installing VRTScscw 4.0 on netnumencluster1 ...............
Done 46 of 69 steps
Installing VRTScutil 4.0 on netnumencluster2 ................
Done 47 of 69 steps
Copying VRTScssim.tar.gz to netnumencluster2 ................
Done 48 of 69 steps
Installing VRTSweb 4.0 on netnumencluster1 ................
Done 49 of 69 steps
Installing VRTScssim 4.0 on netnumencluster2 ................
Done 50 of 69 steps
Installing VRTSvcsw 4.0 on netnumencluster1 ...............
Done 51 of 69 steps
Copying VRTScscw.tar.gz to netnumencluster2 .................
Done 52 of 69 steps
Installing VRTScscw 4.0 on netnumencluster2 .................
Done 53 of 69 steps
Installing VRTScscm 4.0 on netnumencluster1 ...............
Done 54 of 69 steps
Copying VRTSweb.tar.gz to netnumencluster2 ..................
Done 55 of 69 steps

Installing VRTSweb 4.0 on netnumencluster2 ..................

Done 56 of 69 steps
Copying VRTSvcsw.tar.gz to netnumencluster2 .................
Done 57 of 69 steps
Installing VRTSvcsw 4.0 on netnumencluster2 .................
Done 58 of 69 steps
Copying VRTScscm.tar.gz to netnumencluster2 .................
Done 59 of 69 steps
Adding patch 115209-05 on netnumencluster1 ................
Done 60 of 69 steps
Installing VRTScscm 4.0 on netnumencluster2 .................
Done 61 of 69 steps
Copying 115209-05.tar.gz to netnumencluster2 ................
Done 62 of 69 steps
Done 63 of 69 steps
Done 64 of 69 steps
Adding patch 115209-05 on netnumencluster2 ..................
Done 65 of 69 steps
Done 66 of 69 steps
Done 67 of 69 steps
Done 68 of 69 steps
Done 69 of 69 steps
Cluster Server installation completed successfully.

PROGRAM
Configuring Cluster Server:
Creating Cluster Server configuration files ......................

Done
Copying configuration files to
netnumencluster1 .......................... Done

Copying configuration files to

netnumencluster2 ............................ Done
Cluster Server configured successfully.

PROGRAM
33. Do you want to start Cluster Server processes now? [y,n,q]

(y)
Starting Cluster Server:
Starting LLT on netnumencluster1 ......................................

Started
Starting LLT on
netnumencluster2 ........................................ Started
Starting GAB on netnumencluster1 ......................................
Started
Starting GAB on
netnumencluster2 ........................................ Started
Starting Cluster Server on
netnumencluster1 ........................... Started
Starting Cluster Server on
netnumencluster2 ............................. Started
Confirming Cluster Server startup ................... 2 systems
RUNNING
Cluster Server was started successfully.

PROGRAM
Installation of Cluster Server 4.0 has completed successfully.

The installation summary is saved at:

/opt/VRTS/install/logs/installer1115142948.summary
The installer log is saved at:
/opt/VRTS/install/logs/installer1115142948.log
The installation response file is saved at:

/opt/VRTS/install/logs/installer1115142948.response
END OF STEPS
Result VCS is successfully installed.
Note: Installation procedures are various with different

VCS versions.
Installing VCS Patch
Install the latest VCS patch if there is one.
Installing VCS Oracle Agent Software
Purpose To install VCS oracle agent software.

Steps To install VCS oracle agent software, perform the following step:
root@ netnumencluster1 # pwd
/cdrom/cdrom0/storage_solutions_4.0_cd1/cluster_server
_agents/oracle_agent/pkgs
root@ netnumencluster1 # pkgadd –d.
NOTE: There is a ‘.’ mark at the end of –d. Do not forget it.
Select Complete Install.
NOTE: Perform operations on both systems.
END OF STEPS
Result VCS oracle agent software is installed successfully.

Configuring VCS System

Remember to save all settings before exiting VCS management
interface. Otherwise, all settings may be lost. If the system is
restarted without saving settings, it may fail to login to VCS.
Click the third icon in the tool bar on the VCS Cluster
Administrator interface. If the setting is not saved, the icon is
bright. If the setting is saved, the icon is dimmed.
Starting VCS Cluster Manager

Purpose To start VCS cluster manager.
Steps To start VCS cluster manager, perform the following steps:
1. Logon VCS Cluster Manager interface on netnumencluster1
root@ netnumencluster1 # hagui &
FIGURE 252 − OPENING VCS CLUSTER MANAGER INTERFACE
2. Select File Æ New Cluster. Input netnumencluster1 in

Host Name text box. Select default values for other
parameters. Click OK as shown in Figure 253.
FIGURE 253 − CREATING A NEW CLUSTER

3. After creating a new VCS, the interface is shown in Figure

254. Click the new cluster to pop up the login interface.
FIGURE 254 − CLUSTER MONITOR INTERFACE AFTER VCS IS CREATED
4. Input user name and password. By default, the user name is

admin. The password is password. Click OK. VCS Cluster
Administrator window appears as shown in Figure 255.
Change the user name and password after debugging.
FIGURE 255 − VCS CLUSTER ADMINISTRATOR INTERFACE
END OF STEPS
Result VCS cluster manager is started up successfully.

Adding Oracle Resource Group

Purpose To add oracle resource group.
Importing Oracle Type
Purpose To import oracle type.

Steps 1. Select File Æ Import Type in the VCS Cluster
Administrator window as shown in Figure 255. Import
Type window appears as shown in Figure 256.
FIGURE 256 − IMPORTING ORACLE TYPE
2. Select /etc/VRTSvcs/conf/OracleTypes.cf.
END OF STEPS
Result Oracle type is imported successfully.
Creating Oracle Resource Group
Purpose To create oracle resource group.

Steps 1. Select Edit Æ Add Æ Service Group in VCS Cluster
Administrator window as shown in Figure 255. Add
Service Group window appears as shown in Figure 257.

FIGURE 257 − ADDING ORACLE RESOURCE GROUP
2. Input oracle in the Oracle Service Group text box. Select

systems for service group in sequence: netnumencluster2
and netnumencluster1. Select Startup. Click Templates…
button. Select Templates as shown on the left pane. Select
OracleGroup. Click OK.
Figure 258 shows relationship of resources and resource
groups containing in oracle resource group.
FIGURE 258 − RELATIONSHIP BETWEEN ORACLE RESOURCE GROUP AND

RESOURCES
END OF STEPS
Result Oracle resource group is created successfully.

Configuring Resources in Oracle Resource

Group
Purpose To configure resources in oracle resource group.

Steps To configure resources, perform the following steps:
1. Adding/modifying/deleting resource
NOTE: Take IP resource as an example.
Adding resource
i. Select Oracle resource group in the Relationship
between Oracle Resource Group and Resources
window as shown in Figure 258. Right click on it. Select
Add Resource menu. Add Resource window appears as
FIGURE 259 − ADDING RESOURCE
ii. Input Ora_IP in the Resource name text box. Select IP

for Resource Type. Adding different resources is to
select various resource types. Check Enabled check box.
Click OK. IP resource is added.
iii. Click the third icon in the tool bar on the

Relationship between Oracle Resource Group and
Resources window as shown in Figure 258 to save
settings.
Modifying resource property
i. Select one resource, for instance, Ora_IP, in the
Resources window as shown in Figure 258. Select

Properties tab, which displays properties of Ora_IP

resource. Select one property. Modify it.
ii. Click the third icon in the tool bar on the

Resources window as shown in Figure 258 to save
settings.
Delete resource
Select one resource, for instance, Ora_IP, in the
Resources window as shown in Figure 258. Right click on it.
Select delete to delete this resource.
2. Verify AutoStartList resource
i. Select one resource group, for instance, oracle, in the
Properties tab. View AuotStartList property as shown in
Figure 260.
FIGURE 260 − AUTOSTARTLIST PROPERTY
ii. If the sequence is wrong, select an oracle resource group

in Relationship between Oracle Resource Group and
Properties tab.
iii. Click Edit button for AutoStartList property. Edit
Attribute window appears as shown in Figure 261.
iv. Click to add. Click to delete. Change the

sequence as shown in Figure 261.

FI G U R E 2 6 1 − E D I T AT T R I B U T E
NOTE: AutoStartList property configuration decides on which

system oracle resource group (namely, oracle database) runs
in priority when both systems are restarted. In this instance,
it runs on NETNUMENCLUSTER2 in priority. The configuration
is contrary to AutoStartList property setting of NM resource.
NM server runs on netnumencluster1 in priority. Oracle
database and NM server can run on different systems by
default, ensuring loadings of both systems are equal.
3. IP resource Ora_IP
Use Ora_IP to specify IP address, subnet mask and NIC type
of Oracle database.
NOTE: The IP address here is the floating IP address of
oracle database. For cluster system, on which system oracle
runs, the floating IP is switched to this system, ensuring
oracle database provides transparent database service
externally.
Modify IP resources based on properties below:
f Device = eri0
f Address = "10.61.94.253"
f SubNetMask = "255.255.252.0"
4. DiskReservation resource oracle_diskRes
i. DiskReservation resources ensure that only one system
can access disk array. If heartbeat cable is disconnected,
both systems may access disk array. Data or file system
may be damaged.

ii. Presently, hard disks for disk array are SCSI, SCSI or
fiber disk. DiskReservation resources support all of them.
iii. Set Disks property of DiskReservation to be logical device
name of Oracle database disk array resource. Select
Global. Input one logical device name.
DiskReservation oracle_diskRes (
Disks = { c3t0d0s2}
FailFast = 1
)
iv. Setting FailFast as 1 (true) indicates that when VCS
detects access collision occurs on partition under the
management of DiskReservation resource, resource fail
will be faster. By default, the value for FailFast is 0 (false).
v. For VCS4.0forSolaris, a problem exists after
DiskReservation is added to resource group. That is, it
can fail to start resource group automatically when both
systems are rebooted at the same time. Set resource
group online manually to solve the problem. Use init 6
command to reboot the system to avoid the problem.
Note: While taking dual system test, if the system uses

DiskReservation resource, it is required to use init 6 command
to reboot the system, instead of reboot command.
5. MOUNT resource Ora_Mnt_Data

Use MOUNT resource to specify file resource of oracle
database, mount point on the system and relevant system
directory of mount point.
Mount point is /export/home/oracle/oradata.
Mount Ora_Mnt_Data (
MountPoint = " /export/home/oracle/oradata"
BlockDevice = "/dev/dsk/ c3t0d0s2"
FSType = ufs
FsckOpt = "-y"
)
6. NIC resource Ora_NIC
Use NIC resource Ora_NIC to specify network interface
offering oracle service externally. Network interface
information for both systems is the same. In this instance,
port is eri0. Port type is ether.
NIC Ora_NIC (

Device = eri0
NetworkType = ether
)
Note: Configure eri0 according to on-site network interface

card.
7. Oracle database resource Ora_Oracle

Use Oracle database resource Ora_Oracle to specify oracle
database information. Contents below show configurations.
Oracle Ora_oracle (
Sid = uep
Owner = oracle
Home = "/export/home/oracle/product/9.2.0"
Pfile =
"/export/home/oracle/product/9.2.0/dbs/inituep.ora"
MonScript = "./bin/Oracle/SqlTest.pl" )
8. Oracle database monitoring resource Ora_Netlsnr
Use oracle database monitoring resource Ora_Netlsnr to
specify oracle database monitoring resource information.
Contents below show configurations.
Netlsnr Ora_Netlsnr (
Owner = oracle
Home = "/export/home/oracle/product/9.2.0"
TnsAdmin =
"/export/home/oracle/product/9.2.0/network/admin"
Listener = LISTENER
MonScript = "./bin/Netlsnr/LsnrTest.pl"
)
END OF STEPS
Result The resources in oracle resource group are configured
successfully.
Follow-up Create relationship of resources in Oracle resource group.
Action
Relationship of resources in Oracle resource group indicates
the sequence of starting resources while starting oracle
resource group. Refer Relationship between Oracle
Resource Group and Resources window as shown in
Figure 258.

Select an oracle resource group. Select Resource tab. Click

button to link resources.
Method of connecting resources is:
1. Click the button. Select Ora_IP resource. Move the

mouse, pointing to Ora_NIC. The relationship shown in
Figure 262 is created. Create other relationships in this way.
FIGURE 262 − CREATING RESOURCE RELATIONSHIP
2. Resource relationship indicates the sequence of

starting/stopping resources in oracle resource group. It is the
foundation of ensuring resources normal running.
The sequence of starting resources is: Start resources from
the bottom up.
The sequence of stopping resources is: Stop resources from
the top down.
Testing Oracle Resource Group
Purpose To test oracle resource group to verify whether oracle resource

group is configured correctly.
Preliminary Oracle resource group must be configured.
Setup
Steps To test oracle resource group, perform the following steps:

1. Select Oracle Resource in Relationship between Oracle
Resource Group and Resources window as shown in
Figure 258. Right click on it. Select online Æ
netnumencluster1. Oracle database is started on
netnumencluster1 automatically.
2. Select oracle resource. Right click on it. Select switch to Æ
netnumencluster2. Oracle database is switched over to
netnumencluster2.
END OF STEPS
Result Oracle resource group is tested successfully.

Adding NM Resource Group

Purpose To add NM resource group.
Installing NM Program
Purpose To install NM program.

Steps To install NM program, perform the following steps:
1. Create required directories for NM server.
Create the ‘netnumen’ directory as root user, which is the
installation directory for NM server.
# cd /
# mkdir netnumen
Create the ‘/export/home/ backup’ directory as root user,
which is a directory for saving NM backup files. .
#cd/export/home
# mkdir backup
NOTE: Perform the first operation on both systems.
2. Mount on disk array and install NM server program on disk
array.
i. Install NetNumen N31 NM program on disk array,
ensuring that NM server data is consistent.
ii. If oracle database is running, mount disk array on the
system. If Oracle database is not running, mount disk
array on any system. Here, it is supposed that oracle
database is running on netnumencluster1, mount disk
array on netnumencluster1.
iii. For instance, mount NM partition on disk array to
netnumen directory on netnumencluster1.
root@ netnumencluster1 # mount /dev/dsk/
c3t0d1s2 /netnumen
Result: It is possible to view the ‘/netnumen’ directory on
netnumencluster1.
3. Run NM installation program to install NM program.
Run install.sh to install NM server to the ‘/netnumen’
directory.
END OF STEPS
Result NM program is installed successfully.
Follow-up Perform step 2 and 3 on one system.
Action

Configuring NetNumen N31 Program
Purpose To configure NetNumen N31 program.

NOTE: Perform operations below only on one system.
Preliminary Ensure NM server runs normally.
Setup
Steps To configure NetNumen N31 program, perform the following

steps:
1. Ensure oracle database is running.
i. Ensure oracle database is started normally before
configuring NM server. Generally, oracle database is
started normally after oracle database resource is
configured. If not, start oracle database on the system
mounted with NM program. Open VCS management
interface. Perform the following operation to start
database:
ii. Select oracle resource group in Relationship between
Oracle Resource Group and Resources window as
shown in Figure 258. Right click on it. Select Online Æ
netnumencluster1. Start Oracle database on
netnumencluster1.
2. Modify NM database configuration script install-db-conf.sh.
The script file is /netnumen/ums-svr/docs/dbscript/install-
db/uep/unix/ install-db-conf.sh. Modify system password of
oracle database.
##### database system user and password
SYSTEM_USER=system
SYSTEM_PWD=manager
NOTE: Modify the password as required.
3. Modify NM database script.
Create specified NM database space on disk array.
Since two systems need share NM data in the database, it is
required to create NM database on share disk space. Modify
the script files below. The specified NM database space
resides at /export/home/oracle/oradata. For English
operating system, modify the script under relevant dbscript-
en.
//../ums-svr/docs/dbscript/dbscript-zh is script for English
operating system.
i. Modify UEP table location.
\\..\\ums-svr\docs\dbscript\dbscript-
zh\oracle\uep\common\jms-createdb-ora.sql
Original script:

s := 'create tablespace uep datafile "uep.dbf" size 500

M REUSE AUTOEXTEND ON NEXT 1M ONLINE
PERMANENT'
Modified script:
s:= 'create tablespace uep datafile
"/export/home/oracle/oradata/uep.dbf" size 500 M
REUSE AUTOEXTEND ON NEXT 1M ONLINE PERMANENT'
ii. Modify UEP table location.
zh\oracle\uep\common\uep-createdb-ora.sql
Original script: datafile 'uep.dbf' size 500M REUSE
Modified script: datafile
'/export/home/oracle/oradata/uep.dbf' size 500 M
REUSE
iii. Modify UEP _PM table location.
zh\oracle\uep\pal\pm\uep-pal-pm-createdb-ora.sql
Original script: datafile 'UEP_PM.dbf' size 100M REUSE
'/export/home/oracle/oradata/uep.dbf' size 500M REUSE
iv. Modify UEP _ CAT_FM table location
zh\oracle\uep\pal\fm\uep-pal-fm-createdb-ora.sql
Original script: datafile 'UEP_CAF_FM.dbf' size 100M
REUSE
'/export/home/oracle/oradata/UEP_CAF_FM.dbf'
size 100M REUSE
NOTE: Save modifications.
4. Create NM database.
After modifying NM database script, run NM database script
to create NM database. Perform operations on the system
which is running Oracle database and mounted with NM
program.
i. Switch to oracle user.
root@ netnumencluster1#su - oracle
ii. Enter NM database script installation directory.
root@ netnumencluster1$cd / netnumen/ums-
svr/docs/dbscript/install-db/uep/unix
iii. Run database script.
root@ netnumencluster1# ./install.sh

Note: If oracle user is failed to access install.sh file or

install.sh is not executable, perform following operations as root
user:
#cd / netnumen/ums-svr/docs
Change all files in the / netnumen/ums-svr/docs/ dbscript
directory to be executable and accessible files.
#chmod –R 777 dbscript
After modification, repeat steps 1, 2 and 3 to create NM
database.
5. Verify whether NM database is created in the correct

directory.
Perform following operations to verify whether NM database
is created in the correct directory. The right path is
/export/home/oracle/oradata.
i. Switch to oracle user.
ii. Logon to the database.
root@ netnumencluster1$ sqlplus /nollog
SQL> sqlplus /as sysdba
iii. Query NM database table space location.
If the NM database table space location is
/export/home/oracle/product/9.2.0/dbs or others, instead
of /export/home/oracle/oradata, there is error to create
NM database location. Enter the fault processing flow.
Note: If UEP_CAF_FM.dbf, UEP_PM.dbf, and UEP.dbf are in

/export/home/oracle/product/9.2.0/dbs or other directories,
instead of /export/home/oracle/oradata, there is error to create
NM database location. Do not switch the database to another
system. Otherwise, the database cannot start. Delete NM
database table space immediately.
iv. Switch to oracle user.

v. Log on to database.
root@ netnumencluster1$ sqlplus /nollog
SQL> sqlplus /as sysdba
vi. Delete NM database table space.
f Delete uep table space.

SQL> DROP TABLESPACE uep INCLUDING CONTENTS

CASCADE CONSTRAINTS
f Delete UEP_PM table space.
SQL> DROP TABLESPACE UEP_PM INCLUDING CONTENTS
CASCADE CONSTRAINTS,
f Delete UEP_CAF_FM table space.
SQL> DROP TABLESPACE UEP_CAF_FM INCLUDING
CONTENTS CASCADE CONSTRAINTS,
Commit above operations.
SQL>commit
vii. Verify that NM database table space is deleted.
SQL> select tablespace_name from dba_tablespaces
where tablespace_name like ‘UEP%’;;
Run sql statement. If the NM database table space is
successfully deleted, no UEP, UEP_PM, or UEP_CAF_FM
exists.
viii.Repeat steps 3, 4 and 5 to create NM database. Create
NM database to disk array again.
Check step 3, ensuring that specified NM database table
space is created on disk array. Modify NM database script,
ensuring that specified NM database table space is
created on disk array. Recreate NM database space,
ensuring that NM database table space is created in the
specified directory.
6. Configure database IP in NM configuration center.
Run the /netnumen/tools/configcenter/bin/run.sh file to start
NM configuration center. Select database service. Set IP
address to be the floating IP of oracle database:
10.61.94.253. Test database connection. Figure 263 shows
the normal connection.
FIGURE 263 − NETNUMEN NM CONFIGURATION CENTER

Complete FTP Service configuration by referring to ‘UNIX NM

Configuration Center’ section. Click Save to save the
configurations.
Then, check whether the /netnumen/ums-svr/deploy/deploy
properties file is modified. Refer to configurations below:
# Datasource configuration for ZXSS performance manager
zxss-osf-pm.zxss-osf-pm.ds.ip=10.61.94.253
zxss-osf-pm.zxss-osf-pm.ds.databasename=uep
7. Complete other NM server configurations.
Complete other NM server configurations. NM server is
multiple IP environment. Perform multiple IP NM server
configuration.
Modify the following parameters of the file ‘\ums-
svr\netnumen\ip\dsl\dsl-base.par\conf\IPMS_param.xml’
<FTP_PARAMETERS
FTPIPAddress="localhost" />
Change FTPIPAddress="localhost to be the NM IP address
with which NE can use ftp.
END OF STEPS
Result NetNumen N31 program is successfully configured.
NM Program Running Test
Purpose To test whether NM is running normally.

Steps To test whether NM is running normally, perform the following
steps:
1. Start /netnumen/ums-svr/bin/console.sh manually. Check
Start upon startup of UMS Console check box on the right
corner, as shown in Figure 264. When VCS starts, NM server
starts automatically.

FIGURE 264 − STARTING NM SERVER TEST
2. Start NM server. Test whether NM server can be started

normally and run.
3. Logon NM client. Check whether NM server works normally.
NOTE: If NM server can be started normally and run, close
console. Modify the /netnumen/ums-svr/platform/psl/ext-
service/console/conf/maincontroller.xml file. UNIX operating
system does not display console interface when console is
started via VCS.
maincontroller.xml
……
<! – Whether the console has interface or not. The
parameter is set to be an integer. 1 – With interface, 0 –
Without interface>
<client-type>0</client-type>
…….
END OF STEPS
Result NM program is running successfully.
Note: Save the modification after maincontroller.xml file is

modified.
Creating NM Server Resource Group
Purpose To create NM server resource group.

NOTE: Perform operations below only on one system.

Steps To create NM server resource group, perform the following steps:

1. Create NM resource group (nms-grp) in VCS.
i. Select Edit Æ add Æ service group in VCS Cluster
Administrator window as shown in Figure 255. Add
Service Group window appears as shown in Figure 265.
FIGURE 265 − ADDING NM SERVER RESOURCE GROUP NMS-GRP
ii. Input nms-grp in Service Group Name text box. Select

systems for service group in the sequence of
netnumencluster1 and netnumencluster2 (the sequence
is the same as that for AutoStartList). Check Startup.
Click OK. The resource group nms-grp is created.
Figure 266 shows relationship of resources and resources
containing in NM resource group.
FIGURE 266 − RELATIONSHIP OF RESOURCES IN NM RESOURCE GROUP
2. Verify AutoStartList property in nms-grp.

The sequence of AutoStartList in nms-grp should be:

group nms-grp (
AutoStartList = {netnumencluster1, netnumencluster2}
)
NOTE: AutoStartList attribute setting decides on which
system the nms-grp resource group runs in priority when
both systems are restarted. In this instance, the nms-grp
resource group runs on NETNUMENCLUSTER1 in priority. The
setting is contrary to AutoStartList attribute setting of oracle
resource group, ensuring that oracle database and NM server
run on different systems by default.
3. IP resource nms_IP.
i. Use nms_IP to specify IP address, subnet mask and NIC
type of NM server.
ii. IP address here is the floating IP address of NM server.
For cluster system, on which system NM server runs, the
floating IP is switched to this system, ensuring NM server
providing transparent database service externally.
iii. Select Add Resource in Relationship of Resources in
NM Resource Group window as shown in Figure 266.
The window for adding resource pops up. Select IP for
Resource Type. Input nms_IP in the Resource Name text
box. Select Enable. Set other attributes as follows:
IP nms_IP (
Device = eri0
Address = "10.61.94.254"
SubNetMask = "255.255.252.0"
)
4. DiskReservation resource nms_diskRes and
nms_backup_diskRes.
DiskReservation resources ensure that only one system can
access disk array. If heartbeat cable is disconnected, both
systems may access disk array. Data or file system may be
damaged.
Set disk property of DiskReservation to be logical device
name of NM server disk array resource. Select Global. Input
one logical device name.
Select nms-grp in Relationship of Resources in NM
Resource Group window as shown in Figure 266. Select
Add Resource. The window for adding resource pops up.
Select DiskReservation for Resource Type. Input
nms_diskRes and nms_backup_diskRes in Resource
Name text box. Select Enable. Set other attributes as
follows:
i. DiskReservation resource nms_diskRes.

Use nms_diskRes to manage disk array partition of NM

server.
DiskReservation nms_diskRes (
Disks = { c3t0d1s2}
FailFast = 1
)
Setting FailFast as 1 (true) indicates that when VCS
detects access collision occurs on partition under the
management of DiskReservation resource, resource fail is
faster. By default, the value for FailFast is 0 (false).
ii. DiskReservation resource nms_backup_diskRes.
Use nms_backup_diskRes to manage disk array partition
of NM backup data.
DiskReservation nms_ backup _diskRes (
Disks = { c3t0d2s2}
FailFast = 1
)
For VCS4.0forSolaris, a problem exists after
DiskReservation is added to resource group. That is, it
may fail to start resource group automatically when both
systems are rebooted at the same time. Set resource
group online manually to solve the problem. Using init
6 command to reboot the system can avoid the problem.
Note: While taking dual system test, if the system uses

DiskReservation resource, it is required to use the init 6
command to reboot the system, instead of reboot command.
5. MOUNT resources nms_Mnt_Data and

nms_backup_Mnt_Data.
Use MOUNT resource to specify relationship between NM
server and NM backup data’s directories and disk array file
systems.
The directory for NM server is /netnumen. The file system of
relevant disk array is /dev/dsk/c3t0d1s2.
The directory for NM backup data is /export/home/backup.
The file system of relevant disk array is /dev/dsk/c3t0d2s2.
Select Add Resource in Relationship of Resources in NM
Resource Group window as shown in Figure 266. The
window for adding resource pops up. Select Mount for
Resource Type. Input nms_Mnt_Data and
nms_backup_Mnt_Data in the Resource Name text box.
Select Enable. Set other attributes as follows:

i. Mount resource for NM server: nms_Mnt_Data

ii. Mount resource for NM backup file:
nms_backup_Mnt_Data
6. NIC resource Proxy resource nms_NIC.
Both NM programme and Oracle database share the same
network interface card. The network interface card resource
is added in oracle resource group. It is required to create a
proxy network interface card resource in nms-grp NM
resource group, pointing to Ora_NIC. It indicates that NM
resource group also uses Ora_NIC as its own network
interface card resource.
Right click on nms-grp in Relationship of Resources in
NM Resource Group window as shown in Figure 266. Select
Add Resource. Select Proxy for resource type. The
resource name is nms_NIC. Select Enable. Edit
TargetResName to be Ora_NIC, the NIC resource name in
oracle resource group.
Proxy nms_NIC (
TargetResName =Ora_NIC
)
7. Preparations for adding Application resource netnumen.
i. Configure required parameters. Ensure it is possible to
start NM system manually.
ii. Follow steps introduced in this file. It is recommended to
refer to the /netnumen/tools/cluster/readme.txt file.
iii. Copy the / netnumen/tools/cluster, jdk-solairs file in NM
server version to the /export/home/cluster of
netnumencluster1.
f cp -r /netnumen/tools/cluster /export/home
f cp -r /netnumen/ jdk-solaris /export/home/cluster
iv. Modify script according to the real path of NM server and
script.
Here, the NM server path is /netnumen, the NM script
path is /export/home/cluster, the script JAVA path is
/export/home/cluster/ jdk-solaris.
f Modify the /export/home/ cluster/ moni_sol.sh file.
Modify MONI_HOME location according to real directory
MONI_HOME="/export/home/cluster"
Modify JAVA location according to real directory
JAVA="/export/home/cluster/jdk-
solaris/bin/java"
f Modify the /export/home/ cluster/ offline_sol.sh file.

Set PROCESSPATH below based on the started java

process.
PROCESSPATH="/netnumen"
v. Ensure that both moni_sol.sh and offline_sol.sh have the
execution rights of root user.
Select moni_sol.sh file. Right click on it. Select Modify
Right. Check whether there is execution right. If there is
no right, execute commands below to give rights to the
script.
root@ netnumencluster1# chmod –R 777 cluster
vi. Copy the script directory of /export/home/cluster to the
same directory of netnumencluster2.
Execute the command below on netnumencluster2. Copy
the modified script directory.
netnumencluster1:/export/home/cluster
/export/home
Authorize relevant files in script directory with execution
right as root user.
root@ netnumencluster2# chmod –R 777 cluster
8. Add Application resource netnumen.
Add Resource. The window for adding resource pops up.
Select Application for Resource Type. Input netnumen in
Resource Name text box. Select Enable. Set other
attributes as follows:
Application netnumen (
StartProgram = "/netnumen/ums-svr/bin/console.sh"
StopProgram = "/export/home/cluster/offline_sol.sh"
MonitorProgram = "/export/home/cluster/moni_sol.sh"
)
9. Create Relationship of Resources in nms-grp.
Resource Group window as shown in Figure 266. Select the
Resource tab. Create relationship of resources according to
relationship of resources in nms-grp. The relationship
displays the sequence of starting or stopping resource. It is
the foundation of ensuring normal running of resources.
The sequence of starting resources is: Start resources from
the bottom up.

The sequence of stopping resources is: Stop resources from

the top down.
10. Test nms-grp.
Test whether nms-grp is normal. Make sure database
resource group oracle is in enabled status.
i. Select nms-grp in Relationship of Resources in NM
online Æ netnumencluster1. Observe whether nsm-
grp resources and NM server is started normally. Start
one NM client to verify whether NM server works
normally.
ii. Verify whether nms-grp is switched normally. Select
nms-grp in Relationship of Resources in NM
switch to Æ netnumencluster2. The resource group
nms-grp stops on netnumencluster1 in sequence and
then starts on netnumencluster2.
UNIX operating system does not display console interface
when console is started via VCS. View NM server log or
run NM client to verify whether NM server runs normally.
Establishing Relationship between Database

Resource Group and NM Resource Group
Purpose To establish relationship between database resource group and

NM resource group.
Preliminary After configuring oracle database resource group and nmsgrpIt,
Setup it is required to establish the relationship between them,
ensuring that NM server can start normally after database is
started.
Steps To establish relationship between database resource group and
NM resource group, perform following steps:
1. Select ztevcs in VCS Cluster Administrator Interface
window as shown in Figure 255. Select Service Groups tab.
Click button to create a line pointing from nms-grp to
oracle resource group (Select nms and drag to oracle), as
shown in Figure 267. It indicates that nms-grp relies on
oracle database resource group.

FIGURE 267 − RELATIONSHIP BETWEEN DAT AB ASE RESOURCE GROUP

ORACLE AND NM RESOURCE GROUP NMS-GRP
2. Link Service Groups window appears as shown in Figure

268.
FIGURE 268 − LINK SERVICE GROUPS
Select online global for Relationship, indicating that

relationship between resources is global (whatever system
the resource group runs on).
Select firm for Dependency Type, indicating to start oracle
resource group firstly, then, nms-grp resource group.
3. Save all VCS Modifications.
END OF STEPS
Result Relationship between database resource group and NM resource
group is established successfully.

Follow-up Take tests on NM dual system based on test rules.

Action
NM Dual System Test Rules

Purpose To verify NM dual system is working normally.
Steps To verify NM dual system is working normally, perform the
following steps:
1. Switch over resource groups manually. It is possible for
resource group to have a switchover between two systems.
2. Stop oracle database process manually. Switch oracle
resource groups.
i. Instances about oracle database
Perform the following operations on the host running
oracle database.
#ps –ef | grep ora_smon or #ps –ef | grep
ora_pmon
View oracle smon process or process number of prom
process.
#kill –9 ora_smon or #kill –9 ora_pmon
Stop oracle smon process or pmon process. Oracle
database switching between two systems is successful.
ii. Monitoring instances about oracle database
Perform the following operations on the host running
oracle database.
#ps –ef | grep tnslsnr
View oracle monitoring process
#kill –9 oracle
Stop oracle monitoring process. Oracle database
switching between two systems is successful.
3. Stop NM process manually. Switch over nms-grp between
two systems automatically.
#ps –ef | grep java
#kill –9
Note: There is more than one java process. The process

under the /netnumen/…./java path is the java process related to
NM server. Stop all NM processes with the /netnumen/…./java
path.

Stop NM server java process. After a while, the dual system

has a fault. Oracle database switching between two systems
is successful.
4. Disconnect the network interface of the public network
manually. Switch over resource.
5. Close the host running resource group. The resource group
switch over to the other host automatically. After
netnumencluster1 (netnumencluster2) is resumed, resource
group is not switched over.
6. If the host running resource group is powered down, the
resource group switches over to the other host automatically.
After netnumencluster1 (netnumencluster2) is resumed,
resource group is not switched over.
END OF STEPS
Result NM dual system is working normally.
System Security
While NM system is running on Solaris operating system, it may
be attacked. To enhance the security of NM system, it is
required to do some settings and modifications on system.
Security Rules General rules for system security are:
Install the latest system patch.
Close unnecessary services.
Delete unnecessary tools or modify rights.
Operation The following suggestions are used to enhance the system
Suggestions security:
Delete the /.rhost file from both systems.
The /.rhost file is required for installing dual system. Delete
this file after installing and debugging dual system. It may
bring hidden trouble to safety.
Cancel the telnet right of root user.
Cancel the telnet right of root user after testing.
Ensure that it is set that root user is not permitted to login
via telnet.
Edit /etc/default/login.
#vi /etc/default/login.
# If CONSOLE is set, root can only login on that device.
# Comment this line out to allow remote login by root.
#
CONSOLE=/dev/console

Set not to use ftp user list.

Forbid relevant users to perform ftp operations after testing.
Edit /etc/ftpusers（Solaris 9 is /etc/ftp/ftpusers）
#vi /etc/ftpusers
Add oracle, daemon, bin, sys, adm, lp, uucp, nuucp, listen,
nobody, noaccess, and nobody4. Note that there is one
separate line for each user name.
If oracle is the database user, perform the relevant
modifications according to different database. If ftp
operations are not required for NM-related user, disable ftp
operations.
Close unnecessary services.
Close services below if NM system does not require them.
NOTE: Restart the system to validate operations.
f sendmail
#mv /etc/rc2.d/S88sendmail
/etc/rc2.d/_S88sendmail
f Print
#mv /etc/rc2.d/S80lp /etc/rc2.d/_S80lp
#mv /etc/rc2.d/S80spc /etc/rc2.d/_S80spc
f DMI
#mv /etc/rc3.d/S77dmi /etc/rc3.d/_S77dmi
Forbid dynamic route.
Forbid dynamic route if it is necessary.
#touch /etc/notroute
Technical If hardware or software problems occur while installing dual
Support system, contact the manufacturer for technical support:
SUN hotline technical support number: 800-810-3786. It is
required to provide service number. The service number is
on the back or side of the equipment. The format is S/N:
FN******
Veritas (VCS) technical support number: 800-810-9771. The
attached product certificate covers the service number.


Appendix A
Handling Common VCS

Problems in UNIX
This appendix covers the following topics:

Modifying VCS Cluster Administrator Password
Checking Heartbeat
Checking Running Status
Starting VCS in Abnormal Status
Failed to Start Oracle Database after Switchover
Faulty VCS Resource Group or Resource
Uninstalling VCS
Modifying VCS Cluster

Administrator Password
Purpose To modify VCS cluster administrator interface password.
Steps To modify VCS cluster administrator interface password, perform
1. Select File Æ User Manager on VCS Cluster
Administrator window as shown in Figure 255. Select
Change Password. Input the new password. Click OK.
2. Click the third icon in the tool bar to save the setting.
END OF STEPS
Result VCS cluster password is modified successfully.

Checking Heartbeat
Purpose To check VCS heartbeat.
Example Check VCS heartbeat as follows.
#lltstat –n
LLT node information：
Node State Links
0 netnumencluster1 OPEN 2
* 1 netnumencluster2 OPEN 2
Result The above information shows that the heartbeat LLT of both
hosts is normal. ‘*’ indicates that it is lltstat command sent
from netnumencluster2.
Example #gabconfig –a
GAB Port Memberships
========================================
Port a gen 179d03 membership 01
Port h gen 179d05 membership 01
Result ‘1’ indicates that GAB broadcast of two hosts heartbeat is normal.
Checking Running Status

Purpose To check VCS running status.
Example Check VCS running status as follows.
# hastatus -sum
-- SYSTEM STATE
-- System State Frozen
A netnumencluster1 RUNNING 0
A netnumencluster2 RUNNING 0
Result It shows that both hosts are in normal running status.
Starting VCS in Abnormal

Status
Purpose To start VCS in abnormal status.
Introduction VCS can fail to start under the following conditions:

Appendix A Handling Common VCS Problems in UNIX
Restart the system after doing some settings on VCS cluster

administrator interface while not saving settings. For
instance, close VCS cluster administrator interface without
save configurations. Or, terminate VCS process.
Modify main.cf file manually. Restart the system while the
syntax is wrong. Or, terminate VCS process.
Solutions The following are the different solutions available:
Forget to save VCS configurations:
Execute the #hasys –force host name command on either
host to make VCS works in normal running status.
It is better to execute this command on the host which has
some settings done while without saving the settings.
Take netnumencluster1 as an example. The command is:
#hasys –force netnumencluster1
Then, execute the hagui command to start VCS cluster
administrator interface.
The syntax for main.cf is wrong.
Modify main.cf. Execute the command below to verify
whether the syntax for main.cf is correct.
#hacf –verify /etc/VRTSvcs/conf/config
Start VCS cluster administrator interface after modifying
main.cf syntax.
Failed to Start Oracle

Database after Switchover
Purpose To provide solutions while it is failed to start oracle database
after switchover.
Error If it is failed to start oracle database on one host after
Information switchover, the error information is:
ORA-01157:Cannot identify/lock data file 11 -see DBWR
trace file
ORA-01110: data file 11:
'/export/home/oracle/product/9.2.0/dbs/uep.dbf
Problem It is failed to identify the uep.dbf file, which is the NM database
file created by the user.
Cause The possible reason is that NM database is created on the local
disk of one host (netnumencluster1, for instance), not on the
shared disk array. When oracle database is switched over to
netnumencluster2, it cannot read database data on
netnumencluster1. Consequently, it is failed to start oracle
database on netnumencluster2.

Solutions The following instance provides the solutions:

NOTE: In this instance, oracle database is started successfully
on netnumencluster1 and failed on netnumencluster2.
1. Switch oracle database to the host to start the database.
Here, switch oracle database to netnumencluster1.
2. Delete database table space from local disk of
netnumencluster1.
3. Make sure NM database script is correctly modified.
4. Create NM database to the shared disk array.
For detailed procedures, refer to the fifth step in the Configuring
NetNumen N31 Program section.
Faulty VCS Resource Group

or Resource
Purpose To provide solutions while VCS resource group or resource is
faulty.
Error If one resource is faulty, there is a red cross on it.
Solutions Delete most faulty resources manually. VCS system only
removes a few faulty resources automatically, such as NIC
resource error.
Method Method of removing faulty resource is:
Select the faulty resource. Right click on it. Select Clear Fault
Æ Auto.
Hidden Trouble If faulty resources are not removed from the host, it fails to
enable Ora_Oracle resource on this host.
Example Oracle resource is switched over to netnumencluster2 when
Ora_Oracle resource on netnumencluster1 is faulty. When
netnumencluster2 is faulty, it is required to switch Ora_Oracle
resource back to netnumencluster1. However, it fails to start
oracle resource group on netnumencluster1 because the faulty
Ora_Oracle resource on netnumencluster1 is not removed.
Therefore, it is required to remove faulty resource manually.
Figure 269 shows that oracle resource group is faulty on
netnumencluster 2. Then, it is switched over to
netnumencluster1 and works normally on it.
NOTE: Remove the faulty resource from netnumencluster2 in
time.

Appendix A Handling Common VCS Problems in UNIX
FIGURE 269 − ORACLE RESOURCE GROUP IS SWITCHED OVER TO

NETNUMENCLUSTER1 AND WORKS NORM ALLY.
Uninstalling VCS
Purpose To uninstall VCS.
Prerequisite Save /etc/VRTSvcs/conf/config/main.cf file before
uninstalling VCS. If types.cf file is modified, save it too.
Steps To uninstall VCS, perform the following steps:
NOTE: Uninstall VCS from any host, for instance,
netnumencluster1.
1. Terminate VCS process on all servers.
#./hastop -all –force
2. Uninstall server software and oracle agent software.
Logon to the system as root user. Execute commands below:
#cd /opt/VRTSvcs/install
#./uninstallvcs
Or, insert VCS CD into either host. Logon to the system as
root user. Execute commands below:
#cd /cdrom/cdrom0/cluster_server
#./uninstallvcs
The system displays prompts as follows:
Enter the system names separated by spaces on which
to uninstall VCS: netnumencluster1
netnumencluster2
Press [Return] to continue:
Do you want to uninstall package VRTSvcsor from
netnumencluster1 which is dependent on package
VRTSvcs? [y,n,q,?] (y) y
Do you want to uninstall package VRTSvcsor from
netnumencluster2 which is dependent on package
VRTSvcs? [y,n,q,?] (y) y

Are you sure you want to uninstall VCS packages?

[y,n,q] (y) y
Uninstallation of Cluster Server has completed
successfully.
END OF STEPS
Result VCS uninstalling is complete.
NOTE: While VCS server software and Oracle agent software are
uninstalled from netnumencluster1, the VCS server software and
Oracle agent software are uninstalled from netnumencluster2
automatically too.

Appendix B
Common UNIX Operation

Commands

File System Operation Commands
System Commands
Pack/unpack Commands
Important System Files
File System Operation

Commands
File system operation commands are listed in Table 22
TABLE 22 − FILE SYSTEM OPERATION COMM AND TABLE
Command Description Application

cd Modify directory -
ls Display directory and file -
information, similar to DOS
command dir
mount Mount one device (such as a #mount
disk) to a directory /dev/dsk/c0t0d0s1
/test
more View files -
cat View files or combine # cat file1 file2 >file3
multiple files to one file
ln Create connection # ln file1 file2


rm Delete one file; delete one -
directory and all contents in
the directory where the
parameter –R(r) exists
rmdir Delete one blank directory -
mkdir Create a directory -
cp Copy files -
mv Change the file name. Move -
one file or directory to
another location
chgrp Modify the file group chgrp file (or
directory name)
parameter –R
recurrence
chmod Modify file right chmod 755 file
chmod u+w file
chmod g+w file
chmod o+w
Parameter –R
recurrence
chown Modify the file user -
wc Count bytes, characters and -
lines
pwd Display current directory -
find Find specified file find / -name filename
-print & Find the
specified file based on
name at root
directory. Execute the
command on
background and
display the result on
terminal.
tail Display file tail information tail -3 file Display
from the last three
lines; tail +3 file
Display from the first
three lines
ftp Enable ftp function -

Appendix B Common UNIX Operation Commands
System Commands
System commands are listed in Table 23.
TABLE 23 − SYSTEM COMMAND

pkginfo View system patch pkginfo –i
df Show disk usage -
du Show file system; Show file -
size
uname View system information -
ps View process information -
kill Stop a process kill -9 120
kill -HUP 120 Kill the
process and restart it.
pkill Stop the process according to pkill httpd
process name
netstat View network status -
ifconfig Configure or view network ifconfig –a View
interface parameters ifconfig eri0
136.1.56.170
Configure interface
address (For nm7000)
ifconfig eri0
up(down)
ifconfig eri0 add
if IP address add a
logical address.
admintool System administration tool -
hostname View host name -
who View login user -
date View or set system time -
env View system environment -
eject Eject CD driver -
clear Clear terminal screen -
information
| Pipe operator more inetd.conf|grep
ftp
last View login and logout -


route add Add route route add default
136.1.0.1 1
Add default gateway.
If the
/etc/defaultrouter file
exists, the system will
set IP address in this
file to be its gateway
when system startup.
Pack/Unpack Command
Pack/unpack commands are listed in Table 24.
TABLE 24 − PACK/UNPACK COMM AND

tar - tar -xvf *.tar Unpack
tar -cvf a.tar a Pack
a to be a.tar.
pack Pack file with the suffix -
of .z
unpack Unpack the file. -
gunzip Unpack the file with the -
suffix of .gz
gzip Unpack the file with the -
suffix of .gz
compress compress -
uncompress uncompress -
zip zip -
unzip unzip unzip a.zip
Important System Files

Import system files are listed in Table 25.
TABLE 25 − IMPORTANT SYSTEM FILES
File or directory Description Application

/etc/rc2.d Multi-user mode start -
file
/etc/rc0.d Close script -

Appendix B Common UNIX Operation Commands
File or directory Description Application

/etc/inetd.conf Network service -
configuration file
etc/default/login Login by telnet after
commenting out
CONSOLE=/dev/cons
ole
/etc/hosts and Save host information. -
/etc/nodename
/etc/defaultdomai Save domain -
n information.
/var/spool/cron/cr User-related cron -
ontabs information
/etc/resolv.conf Domain name server IP. -
nslookup cannot be
used unless the file
exists.
/etc/passwd and User password file -
/etc/shadow
/etc/motd Prompt information -

after login
/etc/adm/sulog Record conversion -
between common user
and root user.
/dev/null Null device. Cleaning up cat /dev/null > file
a file is the typical cat /dev/null file
application.
It is the best way to
clean up a file. This
operation does not
have any influence
on other processes
whatever the file is
open or not.
Note: The first letter for UNIX command is small letter.


Appendix C
Common Oracle Database

Operations

Starting Oracle8i Database Service
Starting Oracle9i Database Service
Viewing Oracle Service Name
Viewing Database Table Space Name
Viewing Database User
Oracle Database Backup
Restoring Oracle Database
Starting Oracle8i Database

Service
Commands Table 26 lists oracle8i database service commands.
TABLE 26 − STARTING ORACLE8I DAT ABASE SERVICE COMM ANDS
Command Description
# su – oracle Switch user to oracle; the password is
oracle
$ svrmgrl Start oracle server manager
SVRMGR> connect Connect to oracle manager
internal
SVRMGR> startup Start oracle service
SVRMGR> exit Exit manager
$ lsnrctl Enter service monitoring management
LSNRCTL> start Start service monitoring

Command Description
LSNRCTL> exit Exit manager
Starting Oracle9i Database

Service
Commands Table 28 lists Oracle9i database service commands.
TABLE 27 − STARTING ORACLE9I DAT ABASE SERVICE COMM ANDS
Command Description
# su – oracle Switch user to oracle; the password is
oracle
$ lsnrctl start Start service monitoring
$ sqlplus /nolog Start sqlplus
> connect /as Logon to sqlplus
sysdba
> startup Start oracle database
> exit Exit sqlplus
Viewing Oracle Service

Name
Command The following example shows how to switch to oracle user. The
command is executed as follows:
$ set
The environment variant for Oracle user, ORACLE_SID, is Oracle
service name.
Viewing Database Table

Space Name
Generally, the NM database table space name is WEBNMSDB.
Commands Table 28 lists the commands to view NM database table space
name:

Appendix C Common Oracle Database Operations
TABLE 28 − VIEWING DAT ABASE TABLE SPACE N AME COMM ANDS
Command Description
# su – oracle Switch user to oracle; the
password is oracle
$ sqlplus system/** password for system user
SQL> select tablespace_name from Query
user_tablespaces
Viewing Database User

Commands Table 29 lists the commands to view database user:
TABLE 29 − VIEWING DAT ABASE USER COMM ANDS
Command Description
# su – oracle Switch user to oracle; the
password is oracle
$ sqlplus system/** password for system user
SQL> select username from Query
dba_users
Oracle Database Backup

Commands To take the backup oracle database execute the following
command
# su – oracle: Switch user to oracle. (Password: oracle)
$ exp : Export database.
NOTE: The system asks some questions. Use default values for
them except user name and password for database. Put the
backup file to installation directory, such as /export/home/oracle.
Restoring Oracle Database

To restore oracle database use imp command.


Appendix D
Abbreviations
Abbreviation Full Name

ACL Access Control List
ADSL Asymmetric Digital Subscriber Line
ATM Asynchronous Transfer Mode
CPU Central Processing Unit
DSL Digital Subscriber Line
DSLAM Digital Subscriber Line Access Multiplexer
HTML Hyper-Text Markup Language
HTTP Hypertext Transfer Protocol
IP Internet Protocol
LAN Local Area Network
MAC Media Access Control
MODEM Modulator-Demodulator
PC Personal Computer
PPP Point-to-Point Protocol
PVC Permanent Virtual Circuit
QoS Quality of Service
RAID Redundant Array of Independent Disks
RAM Random Access Memory
RMI Remote Method Invocation
RMON Remote Network Monitoring
SNMP Simple Network Management Protocol
SQL Structured Query Language
TFTP Trivial File Transfer Protocol
VCI Virtual Channel Identifier
VLAN Virtual Local Area Network
VPI Virtual Path Identifier


Figures
Figure 1 – Space For User Partition ..................................... 12

Figure 2 – Admin Tool: Groups ........................................... 14
Figure 3 – Admintool: Add Group........................................ 15
Figure 4 – Admintool: Add User Window .............................. 15
Figure 5 – Admintool: Add User Window .............................. 17
Figure 6 − Show Hidden Objects......................................... 18
Figure 7 – Text Editor – .profile Window .............................. 19
Figure 8 − Run Window ..................................................... 20
Figure 9 − Prompt Window ................................................ 21
Figure 10 − Extracting Files ............................................... 21
Figure 11 − Installation Finished......................................... 22
Figure 12 – Terminal Window ............................................. 23
Figure 13 – Listening Process Window ................................. 23
Figure 14 − Download Patch .............................................. 26
Figure 15 − PATCH Searching ............................................ 26
Figure 16 − Patch Searching Result..................................... 27
Figure 17 − SQL Server 2000 Installation Screen .................. 31
Figure 18 − SQL Server 2000 Installation Screen .................. 32
Figure 19 − Install Components Window .............................. 32
Figure 20 − Installation Preparations Window ....................... 33
Figure 21 − Welcome Window ............................................ 33
Figure 22 − Computer Name Window .................................. 33
Figure 23 − Installation Selection Window............................ 34
Figure 24 − User Information Window ................................. 34
Figure 25 − Software License Agreement Window ................. 35
Figure 26 − Installation Definition Window ........................... 35
Figure 27 − Instance Name Windows .................................. 36
Figure 28 − Installation Types Window ................................ 36
Figure 29 − Service Accounts Window ................................. 37

Figure 30 − Authentication Mode Window ............................ 37

Figure 31 − Start Copying File Window ................................ 38
Figure 32 − Choose Licensing Mode Window......................... 38
Figure 33 − INSTALLATION Progress Window ....................... 39
Figure 34 − Starting Server Window ................................... 39
Figure 35 − Updating System Window ................................. 39
Figure 36 − Installation Complete Dialog Box ....................... 40
Figure 37 – NetNumen Installation (Windows) ...................... 42
Figure 38 – Selecting Language – NetNumen........................ 43
Figure 39 – Directory Selection in NetNumen........................ 43
Figure 40 – Extracting Platform Files ................................... 44
Figure 41 – NetNumen Install – NMS Client .......................... 45
Figure 42 – Selecting Language - NMS Client........................ 45
Figure 43 – Directory Selection NMS Client........................... 46
Figure 44 – Extracting Platform Files NMS Client ................... 46
Figure 45 – Running NMS Config Center .............................. 48
Figure 46 – NetNumen Config Center Window....................... 48
Figure 47 – Basic Information Tab ...................................... 49
Figure 48 – NE Module Tab ................................................ 50
Figure 49 – Database Tab.................................................. 51
Figure 50 – Database Data Type Tab................................... 51
Figure 51 – Database System Administration Name And
Password ........................................................................ 52
Figure 52 – Database IP Address Window ............................ 53
Figure 53 – Test Connection Database................................. 54
Figure 54 – Optimize Database........................................... 54
Figure 55 – FTP Service Tab............................................... 55
Figure 56 – Add FTP User Window....................................... 56
Figure 57 – Modify FTP User Windows ................................. 56
Figure 58 – Information Dialog Box..................................... 57
Figure 59 – Information Dialog Box..................................... 57
Figure 60 – Client Update Tab ............................................ 58
Figure 61 – Policy Configuration Tab ................................... 59
Figure 62 – Syslog Info Tab ............................................... 62
Figure 63 – Adding Syslog Server Window ........................... 62
Figure 64 – Add NE Type ................................................... 63
Figure 65 – Modify NE Type ............................................... 63

Figures
Figure 66 – Add Syslog Server ........................................... 63

Figure 67 – Modify Syslog Server........................................ 64
Figure 68 – Delete Sylog Server ......................................... 64
Figure 69 – Shortcut Tab ................................................... 65
Figure 70 – Other Tab ....................................................... 66
Figure 71 – Advance Tab ................................................... 67
Figure 72 – Save Other Information .................................... 67
Figure 73 – Info Dialog Box................................................ 68
Figure 74 – Analog Input Parameters Configuration Tab ......... 69
Figure 75 – Add Analog Parameters .................................... 69
Figure 76 – Modify Analog Input Parameters Configuration Tab70
Figure 77 – Info ............................................................... 70
Figure 78 – Digital Input Parameters Configuration Tab.......... 71
Figure 79 – Add Input Digital Parameters Window ................. 71
Figure 80 – Modify Digital Input Parameters Window ............. 72
Figure 81 – Delete Digital Input Parameters ......................... 72
Figure 82 – Digital Output Parameters Configuration Tab ....... 73
Figure 83 – Add Output Digital Parameters Window ............... 73
Figure 84 – Modify Digital Output Parameters Configuration.... 74
Figure 85 – Delete Digital Output Parameters ....................... 74
Figure 86 – Power Parameters Configuration Tab .................. 75
Figure 87 – Add Power Parameters Window.......................... 75
Figure 88 – Modify Power Parameters Configuration .............. 76
Figure 89 – Delete Power Parameters .................................. 76
Figure 90 – Import (Export) Configuration Data Tab .............. 77
Figure 91 – Import Data Window ........................................ 77
Figure 92 – Export Data Window......................................... 78
Figure 93 – Config Center.sh.............................................. 79
Figure 94 – NetNumen Install............................................. 79
Figure 98 – Config Center Starts......................................... 81
Figure 99 – Config Center.sh.............................................. 82
Figure 100 – NetNumen Install ........................................... 83


Figure 104 – Config Center Starts ....................................... 85
Figure 105 – Configuration Center.sh .................................. 86
Figure 106 – NetNumen Configuration Center Tab ................. 87
Figure 107 – Basic Information Tab..................................... 88
Figure 108 – NE Module Tab .............................................. 89
Figure 109 – Module Deploy............................................... 89
Figure 110 – Database Tab ................................................ 90
Figure 111 – Database Data Type Tab ................................. 90
Figure 112 – Database System Administration Name And
Password ........................................................................ 91
Figure 113 – Database IP Address Window........................... 92
Figure 114 – Test Connection Database ............................... 93
Figure 115 – FTP Service Tab ............................................. 94
Figure 116 – Add FTP User Window ..................................... 94
Figure 117 – Modify FTP User Windows................................ 95
Figure 118 – Information Dialog Box ................................... 95
Figure 119 – Information Dialog Box ................................... 95
Figure 120 – Client Update Tab .......................................... 96
Figure 121 – Policy Configuration Tab.................................. 97
Figure 122 – Syslog NBI Info Tab ..................................... 100
Figure 123 – Adding Syslog Server Window........................ 100
Figure 124 – Add NE Type ............................................... 101
Figure 125 – Modify NE Type............................................ 101
Figure 126 – Add Syslog Server........................................ 101
Figure 127 – Modify Syslog Server .................................... 102
Figure 128 – Delete Sylog Server ..................................... 102
Figure 129 – Short Cut Tab.............................................. 103
Figure 130 – Other Tab ................................................... 104
Figure 131 – Advance Tab ............................................... 104
Figure 132 – Save Other Information ................................ 105
Figure 133 – Info Dialog Box............................................ 105
Figure 134 – Analog Input Parameters Configuration Tab ..... 106
Figure 135 – Add Analog Parameters................................. 106
Figure 136 – Modify Analog Input Parameters Configuration Tab
................................................................................... 107

Figures
Figure 137 – Information................................................. 107

Figure 138 – Digital Input Parameters Configuration Tab ...... 108
Figure 139 – Add Input Digital Parameters Window ............. 108
Figure 140 – Modify Digital Input Parameters Window.......... 109
Figure 141 – Delete Digital Input Parameters ..................... 109
Figure 142 – Digital Output Parameters Configuration Tab.... 110
Figure 143 – Add Output Digital Parameters Window ........... 110
Figure 144 – Modify Digital Output Parameters Configuration 111
Figure 145 – Delete Digital Output Parameters ................... 111
Figure 146 – Power Parameters Configuration Tab............... 112
Figure 147 – Add Power Parameters Window ...................... 112
Figure 148 – Modify Power Parameters Configuration........... 113
Figure 149 – Delete Power Parameters .............................. 113
Figure 150 – Import (Export) Configuration Data Tab .......... 114
Figure 151 – Import Data Window .................................... 114
Figure 152 – Export Data Window ..................................... 115
Figure 153 − Dual Hot Backup NM System ......................... 119
Figure 154 – Disk Array Connections ................................. 120
Figure 155 − Configuring Heartbeat Connection .................. 123
Figure 156 − Configuration Server Guide ........................... 124
Figure 157 − Creating Directory Tree or Sub-tree ............... 125
Figure 158 − Specifying New Domain Name ....................... 125
Figure 159 − Setting Database and Log File Location ........... 126
Figure 160 − Confirming DNS Configuration ....................... 126
Figure 161 − Configuring DNS.......................................... 127
Figure 162 − Permissions ................................................ 127
Figure 163 − Specifying Administrator Password ................. 128
Figure 164 − Configuring Active Directory .......................... 128
Figure 165 − Completing the Active Directory Installation Wizard
................................................................................... 129
Figure 166 − Prompt of Restarting System......................... 129
Figure 167 − Welcome Interface....................................... 130
Figure 168 − Domain Controller Type ................................ 130
Figure 169 − Network Credentials..................................... 131
Figure 170 − Select Product to Install................................ 132
Figure 171 − Select Install Type ....................................... 132
Figure 172 − License ...................................................... 133

Figure 173 − Options Selections 1 .................................... 133

Figure 174 − Options Selections 2 (with two heartbeat network
cards)........................................................................... 134
Figure 177 − Computer Selection ..................................... 135
Figure 178 − Validation ................................................... 136
Figure 179 − Install Report .............................................. 136
Figure 180 − Install Process............................................. 137
Figure 181 − Install Summary.......................................... 137
Figure 182 − Reboot Remote Computers ........................... 138
Figure 183 − Reboot Status ............................................. 138
Figure 184 − Thank you for using VERITAS Storage Foundation
HA 4.3 for Windows Interface........................................... 139
Figure 185 − Prompt Dialogue Box, Asking Whether to reboot
your local computer or not............................................... 139
Figure 186 − VERITAS Enterprise Administrator.................. 140
Figure 187 − localhost-Write Disk Signature....................... 141
Figure 188 − localhost-New Dynamic Disk Group Wizard 1 ... 141
Figure 191 − Creating Hard disk Group Completed .............. 143
Figure 192 − localhost-New Volume Wizard 1 ..................... 144
Figure 197 − Starting VCS Configuration Wizard ................. 147
Figure 198 − Welcome Interface....................................... 147
Figure 199 − Configuration Options .................................. 148
Figure 200 − Domain Selection 1...................................... 148
Figure 201 − Domain Selection 2...................................... 149
Figure 202 − Discovering System ..................................... 149
Figure 203 − VCW Options .............................................. 150
Figure 204 − Cluster Details ............................................ 150
Figure 205 − Validate Systems......................................... 151
Figure 206 − NIC Selection .............................................. 151

Figures
Figure 207 − Set Service Network Card to be Low Priority .... 152
Figure 208 − Service Account........................................... 152
Figure 209 − Security ..................................................... 153
Figure 210 − Summary ................................................... 153
Figure 211 − Finish......................................................... 154
Figure 212 − SQL Server Manager .................................... 156
Figure 213 − Changing SQL Server Automatic Startup to be
Manual Startup .............................................................. 156
Figure 214 − Starting VCS Management ............................ 157
Figure 215 − Select Configuration Option........................... 158
Figure 216 − Service Group Configuration.......................... 158
Figure 217 − SQL Server Instance Selection....................... 159
Figure 218 − Detail Monitoring Configuration...................... 159
Figure 219 − Registry Replication Path .............................. 160
Figure 220 − Virtual Server Configuration .......................... 160
Figure 221 − Servie Group Summary ................................ 161
Figure 222 − Configuration Complete ................................ 161
Figure 223 − Starting VCS Management ............................ 162
Figure 224 − Connectivity Configuration ............................ 163
Figure 225 − Login ......................................................... 163
Figure 226 − Cluster Explorer .......................................... 163
Figure 227 − AutoStartList............................................... 164
Figure 228 − ForceUnmount ............................................ 165
Figure 229 − Modified Configuration.................................. 165
Figure 230 − NetNumen NM Configuration Center ............... 166
Figure 231 − Add Service Group ....................................... 168
Figure 232 − Creating NM Resource Group (nms-grp).......... 168
Figure 233 − Add Resource.............................................. 169
Figure 234 − Running ..................................................... 170
Figure 235 − Creating VMDriveInfo.txt File......................... 170
Figure 236 − d:\ VMDriveInfo.txt...................................... 171
Figure 237 − nms-grp-VMDg Resource .............................. 171
Figure 238 − nms-grp-MountV Resource............................ 172
Figure 239 − proxy_NIC Resource .................................... 173
Figure 240 − UMS NM Platform Server Console................... 176
Figure 241 − Add NM Resource ........................................ 176
Figure 242 − Set RestartLimit to be 3................................ 177

Figure 243 − NM Programme Resource.............................. 178

Figure 244 − Adding Relationship ..................................... 178
Figure 245 − Service Group ............................................. 179
Figure 246 − Link Service Groups ..................................... 180
Figure 247 − All VCS Resources are Started Normally.......... 180
Figure 248 − Finding Program .......................................... 181
Figure 249 − Modifying Options........................................ 181
Figure 250 − License Interface ......................................... 182
Figure 251 − Dual Hot Backup NM System ......................... 192
Figure 252 − Opening VCS Cluster Manager Interface.......... 227
Figure 253 − Creating a New Cluster................................. 227
Figure 254 − Cluster Monitor Interface After VCS is Created . 228
Figure 255 − VCS Cluster Administrator Interface ............... 228
Figure 256 − Importing Oracle Type ................................. 229
Figure 257 − Adding Oracle Resource Group ...................... 230
Figure 258 − Relationship between Oracle Resource Group and
Resources ..................................................................... 230
Figure 259 − Adding Resource ......................................... 231
Figure 260 − AutoStartList Property .................................. 232
Figure 261 − Edit Attribute .............................................. 233
Figure 262 − Creating Resource Relationship...................... 236
Figure 263 − NetNumen NM Configuration Center ............... 241
Figure 264 − Starting NM Server Test ............................... 243
Figure 265 − Adding NM Server Resource Group nms-grp .... 244
Figure 266 − Relationship of Resources in NM Resource Group
................................................................................... 244
Figure 267 − Relationship between Database Resource Group
Oracle and NM Resource Group nms-grp............................ 250
Figure 268 − Link Service Groups ..................................... 250
Figure 269 − Oracle resource group is switched over to
netnumencluster1 and works normally. ............................. 259

Tables
Table 1 − Chapter Summary .................................................i

Table 2 − Typographical Conventions .................................... ii
Table 3 − Mouse Operation Conventions ............................... iii
Table 4 – Network Types .....................................................1
Table 5 − Equivalent NE Example .........................................2
Table 6 − NT Server Configuration ........................................3
Table 7 − Outsourcing Software ...........................................3
Table 8 − Accessories .........................................................4
Table 9 − Hardware Platform ...............................................4
Table 10 − Outsourcing Software..........................................5
Table 11 − Accessories........................................................5
Table 12 − Hardware Platform..............................................6
Table 15 − Hardware Platform..............................................7
Table 18 − Firewall .............................................................9
Table 19 − Disk Partition ................................................. 186
Table 20 − c1t0d0 Disk Partition....................................... 189
Table 21 − Disk Partition ................................................. 192
Table 22 − File System Operation Command Table.............. 261
Table 23 − System Command .......................................... 263
Table 24 − Pack/Unpack Command................................... 264
Table 25 − Important System Files ................................... 264
Table 26 − Starting Oracle8i Database Service Commands ... 267
Table 27 − Starting Oracle9i Database Service Commands ... 268
Table 28 − Viewing Database Table Space Name Commands 269
Table 29 − Viewing Database User Commands ................... 269


Index
Adding Oracle Resource Group Hardware Requirements 11, 186

.................................. 229 Import (Export) Configuration
Analog Input Parameters Data....................... 76, 113
Configuration ...........68, 105 Importing Oracle Type ....... 229
Backup Domain................. 129 Installation Preparation........ 13
Basic Information.......... 49, 87 Installing Latest Solaris9 Patch
Client Update ............... 57, 96 .................................. 190
Configure SQL Server Startup Installing NM Program ....... 237
Type............................ 155 Installing NMS .................. 156
Configuring Database .......... 23 Installing NMS Client ......44, 82
Configuring Domain........... 124 Installing NMS Client and
Configuring NetNumen N31 NM Server ......................42, 78
Resources .................... 165 Installing Oracle 9i .............. 20
Configuring NetNumen N31 Installing Oracle Database on
Program....................... 238 netnumencluster1 ......... 204
Configuring Network .......... 122 Installing Oracle Database on
Configuring NMS Config Center netnumencluster2 ......... 204
.................................... 47 Installing Oracle9i Service Pack
Configuring Resources in Oracle .................................... 25
Resource Group ............ 231 Installing VCS Oracle Agent
Configuring sqlserver Resources Software ...................... 226
.................................. 162 Installing VCS Patch .......... 226
Creating Disk Array Logical Installing VCS Software ..... 208
Partition ....................... 139 Installing VCS4.0 .............. 208
Creating Disk Group .......... 140 Main Domain.................... 124
Creating NM Server Resource Modifying Service IP of Oracle
Group .......................... 243 Database as Floating IP.. 207
Creating Oracle Resource Group NE Module ....................50, 88
.................................. 229 NM Program Running Test.. 242
Creating Volume ............... 143 NM Resource Group........... 237
Database i, 50, 51, 54, 89, 117, Oracle 9i Post Installation
125, 154, 203, 249 Check............................ 22
Digital Input Parameters Other ..................... 3, 65, 103
Configuration ...........70, 107 Policy Configuration .......58, 96
Digital Output Parameters Power Parameters
Configuration ...........72, 109 Configurations ......... 74, 111
Disk Array Connections ...... 119 Preparations before Installation
Disk Array Partition ........... 191 .................................. 203
Dividing Disk Array............ 122 Requirements for Disk Array
Dividing SUN A1000 Disk Array Partition....................... 192
.................................. 197 Running Config Center....47, 86
Dual Hot Backup Configuration Setting Network ............... 200
Requirements ............... 185 Short Cut......................... 103
Dual System Requirements for Shortcut ............................ 65
UNIX ...............................7 Single System Requirements for
Dual System Requirements for UNIX ............................... 4
Windows ..........................6 Single System Requirements for
FTP Service .................. 55, 93 Windows .......................... 3
Hardware......................... 119 Software Requirements. 12, 187
Hardware Connection.. 119, 191 Solaris9 Oerating System
Hardware Firewall .................9 Installation................... 187

Starting VCS Cluster Manager Testing Oracle Resource Group

...................................227 .................................. 236
SUN 3310 Disk Array Partition Upgrading VCS License ...... 181
...................................193 VCS License ..................... 181
System Log Information . 61, 99 VCS Software Configuration 162
Test Dual Systems.............183 VCS Software Configuration -
Test Rules for Local Dual Hot Create Cluster............... 146
Backup System..............183 VCS Software Configuration –
Test Single System ............182 Create SqlServer Resource
Group .......................... 157

ZTE Netnumen N31 User

Загружено:

Сведения о документе

Авторское право

Доступные форматы

Поделиться этим документом

Поделиться или встроить документ

Параметры публикации

Этот документ был вам полезен?

Это неприемлемый материал?

Авторское право:

Доступные форматы

ZTE Netnumen N31 User

Загружено:

Авторское право:

Доступные форматы

NetNumen N31 (V4.2.

Copyright © 2006 ZTE CORPORATION.

The ultimate right to interpret this product resides in ZTE CORPORATION.

Date Revision No. Serial No. Reason for Issue

Your evaluation Accessibility:

About This Manual ............................................................ i

Declaration of RoHS Compliance..................................... v

Installation Overview ...................................................... 1

Database Installation .................................................... 11

NMS Installation ............................................................ 41

VCS4.3 for Windows ....................................................117

VCS4.0 for Unix ............................................................ 185

Appendix A ................................................................... 255

Handling Common VCS Problems in UNIX..................255

Appendix B ................................................................... 261

Common UNIX Operation Commands.........................261

Appendix C ................................................................... 267

Common Oracle Database Operations ........................267

Prerequisite Skill and Knowledge

What Is in This Manual

TABLE 1 − CHAPTER SUMMARY

Confidential and Proprietary Information of ZTE CORPORATION i

ii Confidential and Proprietary Information of ZTE CORPORATION

Mouse TABLE 3 − MOUSE OPERATION CONVENTIONS

How to Get in Touch

Confidential and Proprietary Information of ZTE CORPORATION iii

This page is intentionally blank.

iv Confidential and Proprietary Information of ZTE CORPORATION

To minimize the environmental impact and take more

NetNumen N31 (V4.2.0) Network Management System

Confidential and Proprietary Information of ZTE CORPORATION v

This page is intentionally blank.

vi Confidential and Proprietary Information of ZTE CORPORATION

This chapter covers the following topics:

TABLE 4 – NETWORK TYPES

Network An equivalent NE stands for one managed object in NMS. The

Confidential and Proprietary Information of ZTE CORPORATION 1

TABLE 5 − EQUIVALENT NE EXAMPLE

Windows MS Windows requirements are:

Sun Solaris Solaris requirements are:

Note: Install SQL Server 2000, 2005 or Oracle 9i database prior

2 Confidential and Proprietary Information of ZTE CORPORATION

Single System Requirements for

TABLE 6 − NT SERVER CONFIGURATION

Name Configuration Requirements

Note: Server configuration is recommended therefore

Outsourcing Minimum requirements for the outsourcing software are listed in

TABLE 7 − OUTSOURCING SOFTWARE

Name Configuration Requirements

Confidential and Proprietary Information of ZTE CORPORATION 3

Name Configuration Requirements

Accessories Minimum requirements for the accessories are listed in Table 8.

Name Configuration Requirements

Single System Requirements for

TABLE 9 − HARDWARE PLATFORM

Name Configuration Requirements

4 Confidential and Proprietary Information of ZTE CORPORATION

Name Configuration Requirements

Outsourcing Minimum requirements for outsourcing software are listed in

TABLE 10 − OUTSOURCING SOFTWARE

Name Configuration Requirements

Name Configuration Requirements

Instructions To improve system reliability and stability, NM server and NM

Confidential and Proprietary Information of ZTE CORPORATION 5

PIX firewall with R and UR numbering can be used separately.