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
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.
Revision History
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
Intelligibility:
(Language, Vocabulary, Readability & Clarity, Technical Accuracy, Content)
Good
Fair
Average
Poor
Bad
N/A
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
Chapter 1.......................................................................... 1
Chapter 2........................................................................ 11
Chapter 3........................................................................ 41
Chapter 4......................................................................117
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).
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.
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.
Installation Overview
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.
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)
NE Equivalent NE
MSAG 5200 One Equivalent NE
Software Requirements
Platform NetNumen (V 4.2.0) NMS supports MS Windows and UNIX
Support System platforms.
Hardware Requirements
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
TABLE 8 − ACCESSORIES
Accessories Minimum requirements for the accessories are listed in Table 11.
TABLE 11 − ACCESSORIES
Outsourcing Minimum requirements for the outsourcing are listed in Table 13.
Software
TABLE 13 − OUTSOURCING SOFTWARE
Accessories Minimum requirements for the accessories are listed in Table 14.
TABLE 14 − ACCESSORIES
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
Accessories Minimum requirements for the accessories are listed in Table 17.
TABLE 17 − ACCESSORIES
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
Database Installation
Hardware Requirements
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.
Software Requirements
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
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
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.
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.
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.
Note: Wait for some time. Usually it takes few minutes to extract
all the installation files.
END OF STEPS
Results Oracle 9.2.0.7 database is installed successfully.
END OF STEPS
Results Oracle 9i database is running properly.
Configuring Database
Purpose To configure database.
Preliminary None
Steps
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
10. Make sure that Default is checked and click Next as shown
in Figure 27.
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.
14. Read the instructions and click Next as shown in Figure 31.
15. Select Per Seat for licensing mode and input 10 for devices
as shown in Figure 32.
END OF STEPS
Result SQL server installation is completed successfully.
NOTE: Install latest patch after SQL Server 2000 installation.
NMS Installation
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.
END OF STEPS
Result Config center runs successfully.
Basic Information
END OF STEPS
Result Basic information is viewed successfully.
NE Module
END OF STEPS
Result NE module is viewed successfully.
Database
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.
END OF STEPS
Result Database is tested and optimized successfully.
FTP Service
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.
END OF STEPS
Result FTP user is added, modified and deleted successfully.
Client Update
END OF STEPS
Result Client is updated successfully.
Policy Configuration
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.
END OF STEPS
Result System log information is added, modified and deleted
successfully.
Shortcut
END OF STEPS
Result Shortcuts are viewed on desktop successfully.
Other
END OF STEPS
Result Other tab is viewed successfully.
FIGURE 77 – INFO
END OF STEPS
Result Analog input parameters are configured successfully.
END OF STEPS
Steps Digital input parameters are configured successfully.
END OF STEPS
Result Digital output parameters are configured successfully.
END OF STEPS
Result Power parameters are configured successfully.
END OF STEPS
Result Data is imported and exported successfully.
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.
END OF STEPS
Result NMS client and sever is installed successfully.
END OF STEPS
Result NMS Client is installed successfully.
END OF STEPS
Result Config center runs successfully.
Basic Information
END OF STEPS
Result Basic information is viewed successfully.
NE Module
END OF STEPS
Result NE module is viewed successfully.
Database Configuration
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
END OF STEPS
Result Database is tested and optimized successfully.
FTP Service
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.
END OF STEPS
Result FTP user is added, modified and deleted successfully.
Client Update
END OF STEPS
Result Client is updated successfully.
Policy Configuration
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)
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.
7. The following parameters are used for appointing detailed
saving time.
HisAlarmSaveCount: alarm quantity restriction.
Default: 300,000 Recommended: 300,000
LogSaveCount: Operation log quantity restriction.
Default: 100,000 Recommended: 100,000
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.
END OF STEPS
Result System log information is added, modified and deleted
successfully.
Short Cut
END OF STEPS
Result Shortcuts are viewed successfully on desktop.
Other
END OF STEPS
Result Other tab is viewed successfully.
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
END OF STEPS
Result Analog input parameters are configured successfully.
END OF STEPS
Steps Digital input parameters are configured successfully.
END OF STEPS
Result Digital output parameters are configured successfully.
END OF STEPS
Result Power parameters are configured successfully.
END OF STEPS
Result Data is imported and exported successfully.
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
This section includes the following:
Hardware
Hardware Connection
Connecting Disk Array
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.
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.
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.
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.).
Configuring Domain
Purpose To configure one computer as master domain server and the
other as the backup domain controller.
Main Domain
END OF STEPS
Result NETNUMENCLUSTER1 is updated to be master domain server.
Backup Domain
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
END OF STEPS
Result VCS software installation on computers is complete.
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
END OF STEPS
Result The disk group ‘sql-dskgrp’ for sqlserver database is created.
Creating Volume
END OF STEPS
Result sql-server volume is created.
END OF STEPS
Result Cluster is successfully created.
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.
END OF STEPS
Result As shown in Figure 226, SQL Server service resource group of
sqlserver-grp has been added in VCS system.
shown in Figure 228. Select All from the Scalar Value drop-
down list. Click OK.
END OF STEPS
Result sqlserver-grp attributes are modified successfully.
@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%
'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.
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
Hardware Requirements
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.
Software Requirements
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
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.
END OF STEPS
Result Solaris9 patch is successfully installed.
Hardware Connection
Requirements
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.
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.
/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>
/pseudo/rdnexus@4/rdriver@5,0
2. c3t0d1 <Symbios-StorEDGEA1000-0301 cyl 19998
alt 2 hd 64 sec 64>
/pseudo/rdnexus@4/rdriver@5,0
3. c3t0d2 <Symbios-StorEDGEA1000-0301 cyl 49749
alt 2 hd 64 sec 64>
/pseudo/rdnexus@4/rdriver@5,0
4. c3t0d3 <Symbios-StorEDGEA1000-0301 cyl 59712
alt 2 hd 64 sec 64>
/pseudo/rdnexus@4/rdriver@5,0
FORMAT MENU:
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.
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.)
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
Selection Menu:
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
Checking VRTSvcs package ................................ not
installed
Creating log directory on
netnumencluster2................................. Done
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.
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
/opt/VRTS/install/logs/installer1115142948.summary
/opt/VRTS/install/logs/installer1115142948.log
END OF STEPS
Result VCS is successfully installed.
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.
END OF STEPS
Result VCS cluster manager is started up successfully.
2. Select /etc/VRTSvcs/conf/OracleTypes.cf.
END OF STEPS
Result Oracle type is imported successfully.
END OF STEPS
Result Oracle resource group is created successfully.
FI G U R E 2 6 1 − E D I T AT T R I B U T E
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.
Device = eri0
NetworkType = ether
)
Installing NM Program
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
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.
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
System Commands
System commands are listed in Table 23.
Pack/Unpack Command
Pack/unpack commands are listed in Table 24.
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
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
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
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
Abbreviations
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