0% found this document useful (0 votes)

93 views79 pages

RCView (V2.3) Installation Guide (Rel - 04)

Raisecom RCView Installation Guide

Uploaded by

woitas74

We take content rights seriously. If you suspect this is your content, claim it here.

Available Formats

Download as PDF, TXT or read online on Scribd

0% found this document useful (0 votes)

93 views79 pages

RCView (V2.3) Installation Guide (Rel - 04)

Raisecom RCView Installation Guide

Uploaded by

woitas74

We take content rights seriously. If you suspect this is your content, claim it here.

Available Formats

Download as PDF, TXT or read online on Scribd

You are on page 1/ 79

www.raisecom.

com

RCView (V2.3)
Installation Guide
(Rel_04)
Raisecom Technology Co., Ltd. provides customers with comprehensive technical support and services. For any
assistance, please contact our local office or company headquarters.
Website: http://www.raisecom.com
Tel: 8610-82883305
Fax: 8610-82883056
Email: [email protected]
Address: Raisecom Building, No. 11, East Area, No. 10 Block, East Xibeiwang Road, Haidian District, Beijing,
P.R.China
Postal code: 100094

-----------------------------------------------------------------------------------------------------------------------------------------

Notice
Copyright ©2024
Raisecom
All rights reserved.
No part of this publication may be excerpted, reproduced, translated, or utilized in any form or by any means,
electronic or mechanical, including photocopying and microfilm, without permission in Writing from Raisecom
Technology Co., Ltd.

is the trademark of Raisecom Technology Co., Ltd.

All other trademarks and trade names mentioned in this document are the property of their respective holders.
The information in this document is subject to change without notice. Every effort has been made in the
preparation of this document to ensure accuracy of the contents, but all statements, information, and
recommendations in this document do not constitute a warranty of any kind, express or implied.
Raisecom
RCView (V2.3) Installation Guide Preface

Preface

Objectives
This document describes the preparation, process, steps, and precautions for installing the
RCView.
This document helps you install the RCView correctly. Read it carefully before installation.

Versions
The following table lists the RCView version related to this document.

Name Version

RCView V2.3

Conventions
Symbol conventions
The symbols that may be found in this document are defined below.

Symbol Description
Indicate a hazard with a medium or low level of risk, which, if
not avoided, could result in minor or moderate injury.

Indicate a potentially hazardous situation that, if not avoided,

could cause equipment damage, data loss, and performance
degradation, or unexpected results.
Provide additional information to emphasize or supplement the
important points of the main text.

Indicate a tip that may help you solve a problem or save time.

Raisecom Proprietary and Confidential i

General conventions
Convention Description
Times New Roman Normal paragraphs are in Times New Roman.
Arial Paragraphs in Warning, Caution, Notes, and Tip are in Arial.
Boldface Buttons and navigation paths are in Boldface.
Italic Book titles are in italics.
Lucida Console Terminal display is in Lucida Console.
Book Antiqua Heading 1, Heading 2, Heading 3, and Block are in Book
Antiqua.

Keyboard operation
Format Description
Key Press the key. For example, press Enter and press Tab.
Key 1+Key 2 Press the keys concurrently. For example, pressing Ctrl+C
means the two keys should be pressed concurrently.
Key 1, Key 2 Press the keys in turn. For example, pressing Alt, A means the
two keys should be pressed in turn.

Mouse operation
Action Description
Click Select and release the primary mouse button without moving
the pointer.
Double-click Press the primary mouse button twice continuously and quickly
without moving the pointer.
Right-click Press the right mouse button to pop up a menu for later
selection.
Drag Press and hold the primary mouse button and move the pointer
to a certain position.

Change history
Updates between document versions are cumulative. Therefore, the latest document version
contains all updates made to previous versions.

Raisecom Proprietary and Confidential ii

Issue 04 (2024-06-01)
Fourth commercial release
 Updated the description of the running environment and FAQs.

Issue 03 (2024-05-01)
Third commercial release
 Updated the FAQs.

Issue 02 (2023-09-01)
Second commercial release
 Updated the supported operating systems.

Issue 01 (2023-06-01)
Initial commercial release

Raisecom Proprietary and Confidential iii

Contents

1 Preparing for installation ............................................................................................................ 1

1.1 Overview .......................................................................................................................................................... 1
1.1.1 Installation features ................................................................................................................................. 1
1.1.2 Deployment mode ................................................................................................................................... 2
1.1.3 Installation process .................................................................................................................................. 8
1.1.4 Installation files ..................................................................................................................................... 10
1.2 Running environment ..................................................................................................................................... 11
1.2.1 Hardware environment .......................................................................................................................... 11
1.2.2 Software environment ........................................................................................................................... 14
1.2.3 Browser requirement ............................................................................................................................. 16
1.2.4 Interface requirements ........................................................................................................................... 17
1.2.5 Communication requirements ............................................................................................................... 17
1.2.6 Requirements on IP addresses ............................................................................................................... 17
1.2.7 Other limitations and requirements ....................................................................................................... 18

2 Installation and deployment ..................................................................................................... 20

2.1 Uploading installation files ............................................................................................................................ 20
2.2 Installing system............................................................................................................................................. 20
2.2.1 Initial steps ............................................................................................................................................ 21
2.2.2 Steps for configuring deployment parameters....................................................................................... 23
2.2.3 Steps for confirming and executing installation .................................................................................... 30
2.2.4 Example for installation and deployment.............................................................................................. 31
2.3 Checking installation status ............................................................................................................................ 37
2.4 Upgrading the RCView system through installation program ........................................................................ 38

3 Uninstallation .............................................................................................................................. 41
3.1 Uninstalling system ........................................................................................................................................ 41
3.2 Checking uninstallation status ........................................................................................................................ 43

4 Appendix ...................................................................................................................................... 44
4.1 FAQs for the OS ............................................................................................................................................. 44
4.1.1 No idle hard disk is detected in installing the OS ................................................................................. 44
4.1.2 How to check the space of the directory ............................................................................................... 46
4.1.3 How to configure the size of the partitions of the directory space ........................................................ 47

Raisecom Proprietary and Confidential i

4.1.4 How to disable SELinux ....................................................................................................................... 48

4.1.5 How to configure the static IP address and firewall for the server ........................................................ 48
4.1.6 How to modify the IP address of the CentOS 7 server .......................................................................... 53
4.1.7 How to modify the IP address of the CentOS 9 Stream server ............................................................. 55
4.1.8 How to enable remote SSH on CentOS 9 and logging in with the root user name and password ........ 56
4.1.9 How to configure the OS time .............................................................................................................. 57
4.1.10 How to show the OS language and MAC address information ........................................................... 57
4.1.11 How to configure the passive interface on the FTP server .................................................................. 58
4.2 FAQs for the RCView .................................................................................................................................... 59
4.2.1 Installation fails due to lack of the third-party component.................................................................... 59
4.2.2 The Web client fails to connect to the server. ........................................................................................ 60
4.2.3 SNMP trap alarms sent by NE devices cannot be received. .................................................................. 60
4.2.4 The server program cannot be uninstalled or cannot be re-installed after uninstallation. ..................... 61
4.2.5 How to update the License .................................................................................................................... 61
4.2.6 How to show log files in the RCView system ....................................................................................... 62
4.3 FAQs for the Nmstools tool............................................................................................................................ 63
4.3.1 The Nmstools is a tool software equipped with the RCView system, and it is used for maintaining and
debugging the RCView system.Modifying the host name of the RCView server.......................................... 63
4.3.2 How to modify the IP address, user name, and password of the RCView system ................................ 64
4.3.3 Modifying IP address of the RCView system in small-scale deployment mode ................................... 64
4.3.4 How to stop or start all components of the RCView system ................................................................. 68
4.4 Terms .............................................................................................................................................................. 69
4.5 Acronyms and abbreviations .......................................................................................................................... 70

Raisecom Proprietary and Confidential ii

1 Preparing for installation

This chapter describes the features and preparations that need to be understood before
installing the RCView.
 Overview
 Running environment

1.1 Overview
The RCView, designed and developed by Raisecom, is oriented toward multiple networks and
services. It features rich functions and comprehensive applications. By providing
comprehensive solutions with integrated management and visualized operation and
maintenance, it can improve management efficiency and operation stability, optimize capital
expenditure utilization ratio, and lower operation costs.

1.1.1 Installation features

The RCView adopts the Browser/Server (B/S) architecture and the client uses a web browser.
You only need to install the server. The installation process is simple and convenient, easy to
implement and deploy, and has the following installation features:
 Support flexible deployment.
– Support the deployment modes for two network scales: small-scale network (< 50000
equivalent NEs) and medium-scale network (< 200000 equivalent NEs).
– Each deployment mode supports High Availability (HA) deployment.
– Each deployment mode supports deploying the database with the system. Each
deployment mode supports installing the system database, so you do not need to
prepare a database separately.
– Support pre-deploying the database. The pre-deployed database is classified into the
existing database for pre-deployment and inexistent database for pre-deployment. It
is applicable to the scenario where the database is separately prepared, and is
applicable to the simple distributed standalone deployment and simple distributed
HA deployment.
– Support Web client accessing the server through browser and network.
 Support quick installation. One installation operation supports deploying related
programs of the server.

Raisecom Proprietary and Confidential 1

 Support independent installation program file. One installer file includes all programs on
the system server.
 Support stable system running environment.
– The operating environment of the server program and its components support the
Linux operating system.
– Run the system server program, database, and its components on the operating
system.
 Support showing echo information during installation. Support showing detailed
installation information during the installation process.
 After one version of the RCView system is installed, a later version can be installed to
upgrade the RCView system.
– The normal RCView system of different deployment modes can be upgraded through
installation programs.
– When the installation program is ongoing, the RCView system will be unavailable.

1.1.2 Deployment mode

Introduction
Table 1-1 compares the deployment modes.

Table 1-1 Comparison of deployment modes

Deployme Numbe Number of IP Number of VIP Total
nt mode r of addresses addresses number of
servers IP and VIP
addresses
 At least one
Small-scale 1 Not used At least one
 One independent IP
deployment
address is required
when the independent
IP address of the
southbound IP interface
is used.
 One independent IP

address is required
when the independent
IP address of the
northbound IP interface
is used.

Raisecom Proprietary and Confidential 2

Deployme Numbe Number of IP Number of VIP Total

nt mode r of addresses addresses number of
servers IP and VIP
addresses
 At least one for each  At least one for
Small-scale 2 At least
deployment server each server three
 Two independent IP  One independent
with HA
addresses are required VIP address is
when the independent required when the
IP addresses of the independent VIP
southbound IP interface address of the
are used (one for each southbound IP
server). interface is used.
 Two independent IP  One independent

addresses are required VIP address is

when the independent required when the
IP addresses of the independent VIP
northbound IP interface address of the
are used (one for each northbound IP
server). interface is used.
 At least one for each
Medium- 2 Not used At least two
scale server
 One independent IP
deployment
(comprehen addresses is required
sive when the independent
service/PM/ IP address of the
EMS server southbound IP interface
+ database is used (one for the
server) comprehensive server).
 One independent IP

addresses is required
when the independent
IP address of the
northbound IP interface
is used (one for the
comprehensive server).
 At least one for each
Medium- 1 Not used At least one
scale server
 One independent IP
deployment
(comprehen address is required for
sive the comprehensive
service/PM/ server when the
EMS server independent IP address
+ pre- of the southbound IP
deployed interface is used.
 One independent IP
database
server) address is required for
the comprehensive
server when the
independent IP address
of the northbound IP
interface is used.

Raisecom Proprietary and Confidential 3

Deployme Numbe Number of IP Number of VIP Total

nt mode r of addresses addresses number of
servers IP and VIP
addresses
 At least one for each  At least one for
Medium- 4 At least five
scale server each server
 Two independent IP  One independent
deployment
with HA addresses are required VIP address is
(comprehen when the independent required when the
sive IP addresses of the independent VIP
service/PM/ southbound IP interface address of the
EMS server are used (one for each southbound IP
+ database comprehensive server). interface is used.
 Two independent IP  One independent
server)
addresses are required VIP address is
when the independent required when the
IP addresses of the independent VIP
northbound IP interface address of the
are used (one for each northbound IP
comprehensive server). interface is used.
 At least one for each  At least one for
Medium- 2 At least
scale server each server three
 Two independent IP  One independent
deployment
with HA addresses are required VIP address is
(comprehen when the independent required when the
sive IP addresses of the independent VIP
service/PM/ southbound IP interface address of the
EMS server are used (one for each southbound IP
+ pre- comprehensive server). interface is used.
 Two independent IP  One independent
deployed
database addresses are required VIP address is
server) when the independent required when the
IP addresses of the independent VIP
northbound IP interface address of the
are used (one for each northbound IP
comprehensive server). interface is used.

The system deployment modes support the following features:

 The server used by the RCView can be physical or virtual and supports the IPv4 address
and IPv6 address. The deployment mode is controlled by the License, so contact
technical support for the License before deployment.
 HA deployment supports two or four servers to form active/standby protection.
– Support Automatic Protection Switching (APS) to improve reliability.
– Support manual protection switching to facilitate operation, maintenance, and
debugging.
 IP addresses are used for communication.
− IP addresses of servers: used for network communication among the Web client,
network device, and server, or used for binding with the VIP address in HA
deployment. The IP address accessed by the system client is called the
comprehensive service IP address.

Raisecom Proprietary and Confidential 4

− Southbound IP address and northbound IP address: configured according to network

planning, and used to isolate data of different networks. The northbound IP address of
the IP address of the RCView northbound interface. The southbound IP address of the
IP address of the RCView southbound interface. If there is no network planning, such
as data isolation, you can use IP addresses of servers as the southbound IP address
and northbound IP address.
− For requirements on IP addresses, see section 1.2.6 Requirements on IP addresses.
 The VIP address is used to provide services for HA deployment.
– The IP addresses of both the master server and slave service are bound with the VIP
address.
– The client can use the VIP address to access the RCView in case of change of the IP
address due to protection switching.

The IP address accessed by the system client is called the comprehensive service IP
address. The following IP addresses can be the comprehensive service IP addresses:
 IP address of the server for small-scale deployment
 IP address of the server for comprehensive services of medium-scale deployment
 IP address of the server for small-scale deployment
 VIP address of the server for comprehensive services of medium-scale
deployment

Deployment examples
The typical networking applications of small-scale deployment and medium-scale deployment
are shown in Figure 1-1 and Figure 1-2.
 The system server communicates with Network Elements (NEs) through the RCView.
 The web client communicates with the system server through the network.
 Multiple network interfaces on the system server can be optionally configured with the
IP address of the southbound interface and that of the northbound interface and be used
for accessing the device and the upper-layer system.

Raisecom Proprietary and Confidential 5

Figure 1-1 Example for small-scale deployment

Web client Web client

Comprehensive services
Network

Database
EMS
PM
System server

Management
Network
Browser/Server
NE NE communication
Communication between
NE the RCView and controller

Figure 1-2 Example for medium-scale deployment

Network

Web client Web client

Comprehensive services

Database
EMS
PM

System server

Management
Network
Browser/Server
NE NE communication
Communication between
NE the RCView and controller

HA deployment mode
The typical networking applications of HA deployment are shown in Figure 1-3 and Figure 1-
4.
 The device and Web client communicate with the VIP address.
 If the device network, Web client network, and server network support accessing each
other, each server needs a Network Interface Card (NIC). Each NIC is bound with a VIP
address and communicate with different networks with multiple VIP addresses.
 If the device network, Web client network, and server network are isolated from each
other, each server needs multiple NICs. Each NIC is bound with a VIP address and
communicate with different networks with multiple VIP addresses.

Raisecom Proprietary and Confidential 6

 In the scenario with pre-deployed database, no database is installed inside the system;
instead the system accesses the IP address of an independent database to install the
database.

Figure 1-3 Example for small-scale HA deployment

Web client Web client

Network
System server
Comprehensive

Database

Comprehensive
VIP

Database
EMS
service

EMS
service
PM

PM
Communication
Management between browser and
Network server
Communication
NE NE between RCView and
control
Communication
NE between servers

Figure 1-4 Example for medium-scale HA deployment

Web client Network Web client

System server

Comprehensive Database
Comprehensiv

Comprehensiv

Database

service VIP IP
e service

e service
EMS

EMS
EMS

Communication
Management between browser and
Network server
Communication
NE NE between RCView and
control
Communication
NE between servers

 The Web client network and device network are usually configured as different
networks to enhance security. Or the northbound interface and southbound
interface of the RCView system are configured for different networks to enhance

Raisecom Proprietary and Confidential 7

security. The system server uses multiple VIP addresses to support these
applications.
 Each server can use one NIC, which is applicable when the Web client and
network device belong to the same network.

Web client deployment

 The web client manages the network by accessing and logging in to the system server,
which is also applicable to different geographical locations.
 Through the establishment of different user accounts, operation rights and management
domains, classification, decentralization, and domain division can be implemented.
 Support using Web clients on multiple computers.

Related functions
After the server is deployed in different deployment modes, database backup, database
restoration, and system upgrade are different as below:
 Non-HA deployment: database backup, database restoration, and system upgrade are
implemented on the server for comprehensive services.
 HA deployment: database backup and database restoration are implemented on the
master server, and system upgrade is implemented on all servers.

1.1.3 Installation process

 After installation is completed, the operating system will automatically start the relevant
components of the system. Afterward, as long as the system server is started, the relevant
components of the system will be automatically started with the operating system.
 The server must be configured with an IP address before being installed. For
requirements on IP addresses, see section 1.2.6 Requirements on IP addresses.
 The installation modes include local installation and remote installation.
– Local installation is executing the installation script on the RCView server and
installing the RCView software to a local computer based on a local IP address.
Figure 1-5 shows the networking for local installation.
– Remote installation is executing the installation script on a Linux computer and
remotely installing the RCView software to the specified server based on the IP
address of the server. Figure 1-6 shows the networking for remote installation.
 For the deployment mode with multiple servers, the connection between them must be
available to distribute related programs. You can execute installation on only one server,
and the other server will automatically implement installation.
The installation package includes the installation script, which supports installation through
command lines. Figure 1-5 shows the networking diagram of the command line installation.
Step 1 Upload the entire nms_install directory in the installation file package to a directory of one
server, for example, /usr/local.
 Or decompress the installation file Tar package on one server, and use the upload
software to upload the decompressed nms_install directory as a whole to the server.
 Or use the upload software to upload the installation file compressed package to the
server, and then decompress it through the tar –xvf package file name command to
generate the nms_install directory.

Raisecom Proprietary and Confidential 8

Step 2 Upload the License file to a directory of the server, such as usr/local, for later installation. The
License controls the deployment mode, HA deployment mode, system functions, and NE and
service types, so contact technical support for it according to actual situations.
Step 3 Execute the sh instal.sh command in the nms_install directory of the server as a root-level
user or general user with sudo right. According to the information prompted by the command
line, configure the language, time zone, NTP server IP address, server IP address, root-level
user or sudo-right user and its password, SSH communication port and other installation
information. If the SSH port of the server is modified, you need to use the modified SSH port
for installation.
Step 4 After completing configurations, confirm the entered installation parameters to execute the
installation process.
Step 5 After completing installation, access the IP address of the comprehensive server or the VIP
address of HA deployment mode in a browser to enter the Web interface of the RCView.

Figure 1-5 Local installation through commands

Host A (Windows
or Linux)
installation file,
License file, and Network
configuration file

System server IP address

(Linux)

Management
Network

Communication for
NE NE uploading files
NE

Raisecom Proprietary and Confidential 9

Figure 1-6 Remote installation through commands

Host A (Linux)
installation file,
License file, and Network
configuration file

System server IP address

(Linux)

Management
Network
Communication for
uploading files and
NE NE
installing software
NE

1.1.4 Installation files

File description
The system installation files and license files are used together as listed in Table 1-2.

Table 1-2 Installation files

Type File name format Example
System installation Product RCView_install_2.1.0_20220617183747
program type_date_version.tar .tar
 RCView: product type
 2.1.0: version
 20220617183747: date and time

System License file File name.xml license.xml

Acquisition method
Contact Raisecom technical support for installation files.

Raisecom Proprietary and Confidential 10

1.2 Running environment

1.2.1 Hardware environment

Physical host
0 and Table 1-4 list recommended hardware configurations of physical hosts or virtual
machines.

Table 1-3 Recommended server configurations for 100000 equivalent NEs

Server role Service Indicator Description
configuration
 Comprehensive  CPU: 8 core Number of 50000
server  Memory: 16 GB equivalent
 EMS service  Hard disk: 1 TB
NEs
 PM service  Management

software of 50000 devices in

batches: (50000/20) * time
for upgrading the software of
a single device
 Time for backing up
Configuration
backup and configurations of a single
restoration device: device backup time +
10s (NMS taken time)
 Total time for backing up

configurations of 50000
devices in batches:
(50000/20) * time for
backing up configurations of
a single device

Raisecom Proprietary and Confidential 11

Server role Service Indicator Description

configuration
Total number 500
of users
Number of 100
online users
Number of 50
concurrent
users
SNMP alarm 100 alarms per second
throughput
Burst 150 alarms per second (power
processing of supply fails on batch devices)
SNMP
alarms
 CPU: 4 cores
Database Performance  Gather statistics about data
 Memory: 16 GB collection on 200,000 interfaces every
 Hard disk: 500
5min
GB
 Gather statistics about data
 Applicable to the

medium-scale on 600,000 interfaces every

SNMP network 15min
management Saving The time for saving
performance performance data is no more
data than 7 days.

Table 1-4 Recommended server configurations for 100000 equivalent NEs

Server role Service Indicator Description
configuration
 Comprehensive  CPU: 8 core Number of 100000
server  Memory: 32 GB equivalent
 EMS service  Hard disk: 1 TB
NEs
 PM service  Management

Raisecom Proprietary and Confidential 12

Server role Service Indicator Description

configuration
Operation log 500000
Online status Poll 50000 devices every
monitoring 5min.
 Time for upgrading the
Device
software software of a single device:
upgrade device software upgrade time
+ device restart time + 10s
 Total time for upgrading

software of 50000 devices in

configurations of 50000
devices in batches:
(50000/20) * time for
backing up configurations of
a single device
Total number 500
of users
Number of 100
online users
Number of 50
concurrent
users
SNMP alarm 100 alarms per second
throughput
Burst 150 alarms per second (power
processing of supply fails on batch devices)
SNMP
alarms
 CPU: 8 cores
Database Performance  Gather statistics about data
 Memory: 16 GB collection on 200,000 interfaces every
 Hard disk: 500
5min
GB
 Gather statistics about data
 Applicable to the

medium-scale on 600,000 interfaces every

SNMP network 15min
management Saving The time for saving
performance performance data is no more
data than 7 days.

Raisecom Proprietary and Confidential 13

 The network scale is represented by the number of equivalent NEs, which is the
NE type multiplied by the equivalent NE factor. Table 1-5 lists the relation between
the common NE type and equivalent NE factor.
 Hardware configuration refers to hardware resources occupied by the RCView
during its running period.
 Use the RECC or ECC memory, RAID hard disk, high-quality RAID controller card,
hot-swappable driver suite, hot-swappable power supply, and high-quality UPS to
avoid data loss due to hard disk failure and server power failure.
 Each server needs at least one NIC. It usually needs at least 2 NIC cards to
isolate Web clients and the network device network to enhance security.

Table 1-5 Relation between the common NE type and equivalent factor
NE type Equivalent NE factor
iTN8800-E 20
iTN8600-A 15
iTN185 2
iTN167 1
RAX711-C-R 3
RAX721 10
RAX711-R 2
RAX711-L 1
RAX701 1

1.2.2 Software environment

Supported operating system

Table 1-6 lists the supported operating system.

Table 1-6 Supported operating system

Classification Operating system
 CentOS 7.9
System server
 CentOS Stream 8 and 9
 Rocky Linux 8.5, 8.7, and 9.1

The operating system can be only in Chinese and English. Do not install the software
in the operating system of the Spanish, Portuguese and other language versions. If

Raisecom Proprietary and Confidential 14

you install the English software in the operating system in other languages, problems
such as failure to uninstall, garbled characters on the interface, and inaccurate
display may occur. Unknown problems may also occur in subsequent upgrades.

Permission requirements of operating system users

Table 1-7 shows the permission requirements of operating system users who install, upgrade,
and start system-related programs.

Table 1-7 Permission requirements of operating system users

Classification Permission requirement

System server It must be run as a root user or a general user with the sudo right.

Requirements on space of directory

The root directory should be at least 35 GB, with 100 GB preferred. The space for
subdirectories is as below:
 The available space of the /home directory should be at least 20 GB, with 50 GB
preferred.
 The available space of the /usr/local directory should be at least 4 times the size of
installation files, namely, at least 15 GB usually, with 50 GB preferred.
 Take the hard disk of 1 TB space for example. The recommended SWAP space is 32 GB,
the recommended /home space is 68 GB, and the recommended / space is 900 GB.
 There are two types of Operating System (OS) partitioning methods, and we recommend
method two.
– Method one: allocate sufficient space to the root partition, and install both network
management applications and databases in this partition.
– Method 2 (recommended): create a new /var mount point that requires sufficient
space allocation. Use this mount point for network management databases, logs, and
backup directories. When installing the OS, create mount points, and then adjust the
partition size according to Table 1-8. We recommend allocating all remaining space
to the /var partition after leaving enough space for other partitions. The specific
required space varies from 100 GB to 10 TB, depending on the management device
capacity. If there are a large number of devices on the current network and
performance needs to be collected, insufficient space will cause the RCView to be
unable to work properly.

Table 1-8 Description of adjusting the partition size

Partition File system Mount point Partition size Description
Boot /dev/sda1 /boot 1GB Generally, there is no
need to resize. This
stores Linux kernel
codes.
Swap - / Configure it to Virtual memory, up to
twice the 64 GB
memory.

Raisecom Proprietary and Confidential 15

Partition File system Mount point Partition size Description

Root /dev/mapper/c / 50–100 GB If the mount point
entos-root directory is not
specified, this partition
will be shared.
Home /dev/mapper/c /home About 100 GB Used to store user
entos-home data. There is no need
to configure too large
size in the production
environment.
Var (new) /dev/mapper/c /var > 100 GB Network management
entos-var data files (storing
databases, logs, and
backup files). The
larger, the better.

Related software requirements

The software requirements for the system server host are shown in Table 1-9. CentOS 7.2
usually supports the SSH server by default and the firewall also allows SSH communication
by default.

Table 1-9 Software requirements

Software Description
 SSH server software, such as OPENSSH-server and its dependent
SSH server
software, must be installed.
 The SSH server software must be allowed to be accessed through the
port. The SSH service port is usually 22.
 Use the ps -e |grep sshd command on the server to display the sshd
process.

1.2.3 Browser requirement

Table 1-10 lists browser requirements for Web client and Web installation.

Table 1-10 Browser requirements

Software Description
Chrome Version 85 or later
Firefox Version 64 or later

Raisecom Proprietary and Confidential 16

1.2.4 Interface requirements

You need to consider the requirements of program ports when installing and deploying the
system. When using the system, make sure that the system can open and use these ports for
communication. These ports cannot be blocked or occupied by firewalls or other software.

 When accessing the server through a browser, you must open ports 80 and 15675
on the server for the firewall.
 Different applications may use different components. Some components or
functions support configuration and modification of communication ports.
Therefore, it is necessary to confirm the relevant port requirements according to
the specific situation.
 CentOS supports firewall services by default and prohibits all port communication,
so you need to configure the function of allowing port communication. Or in the
case of an external firewall, you can also turn off the CentOS firewall service
according to the actual situation.

1.2.5 Communication requirements

The RCView must occupy a certain communication bandwidth to work normally. At the same
time, we recommend that the network provide a certain delay guarantee. Related requirements
are listed Table 1-11.
If the bandwidth is too small, communication will be abnormal, and network management
functions will not be provided normally (for example, the client interface response is very
slow; the operation is stuck or delayed; the function is abnormal).

Table 1-11 Communication requirements

Classification Recommended requirements

Web client and system server The bandwidth of each client is greater than 2 Mbit/s.
System server and NE 100 Mbit/s

When opening the client interface for the first time or using the browser's refresh
function, you need to download the cached program for the browser, so there may be
a waiting time, but other subsequent operations will not lag.

1.2.6 Requirements on IP addresses

 The deployment modes of the RCView system support installation based on the IPv4 or
IPv6 address.
– Plan the corresponding number of IP addresses and VIP addresses in advance, and
configure the IP addresses of the relevant computers before installation.
– Confirm in advance the connectivity of the system IP address and VIP address with
the device network, web client network, northbound/southbound interface network,
and network gateway.

Raisecom Proprietary and Confidential 17

– The server must be configured with an IP address before installation.

– If the pre-deployed database is used, one database IP address needs to be specified
during the installation process.
 In HA deployment mode, the RCView system is installed and monitored based on VIP
address and gateway IP address. Confirm the following conditions before installation;
otherwise, it may cause abnormal problems, such as installation failure and HA
switching failure after installation, and then, the RCView system needs to be re-installed.
– The IP addresses of the master/slave servers (where the comprehensive service is
located) must be in the same IP network segment.
– The IP addresses of the master/slave database servers must be in the same IP network
segment.
– The IP addresses of the master/slave servers and master/slave databases must be in
the same IP network segment.
– Each VIP address must correspond to an IP address, and the VIP address must be in
the same IP network segment as the corresponding IP address and gateway IP
address.
− When the master/slave servers (where the comprehensive service is located) use
multiple VIP addresses, multiple VIP addresses can be in the same or different
network segments, but each VIP address and its corresponding IP address and
gateway IP address must be in the same IP network segment.
− The VIP must be an unused IP address on the server network. In the RCView system,
there cannot be any other IP address that overlaps with the VIP address, and the
server cannot be preconfigured with the VIP address.
− The VIP address and gateway IP address must be routed and connected.
− Both northbound VIP address and southbound VIP address cannot be the same IP
address as the IP address of the VIP gateway.
− All IP addresses, VIP addresses, and gateway IP addresses involved in RCView can
be in the same network segment for easy planning and installation.
− The VIP address used in the system refers to the VIP address for internal
communication within the server. In the entire system, there must be only one
internal communication VIP address, and the internal communication VIP address
cannot be the same as the southbound VIP address.

1.2.7 Other limitations and requirements

 No other network management software is installed on the server.
 When the system involves multiple servers, their host names must be different.
– Modify their host names before installation. Use the hostnamectl set-hostname
name command and reboot command to modify the host name.
– The host name cannot contain the period (.).
 Keep the License file properly and use it for installation and maintenance.
 The License file controls both the non-HA deployment mode and HA deployment mode.
Confirm the deployment mode before installation, and contact technical support
personnel to apply for the License file.
 The trial version license can be used on any server, while the official version license will
be bound to the MAC address used to apply for the license.
 If you update the License, the new License file will overwrite the old one on the server
host. Back up the old one before updating. The default path for the License file is
"/var/local/nms/comp/service/webapp/config/license/license.xml".

Raisecom Proprietary and Confidential 18

 Before installation, temporarily close all anti-virus software, Guards, Trojan firewalls
and other security defense software. Security defense software may cause installation
failure.
 During the installation process:
– If there is a network interruption or unexpected restart, execute the uninstall
command on the server, and then re-install the system.
– If residual data of the old version is detected in the directory, the installation script
will prompt and exit the installation. In this case, you need to manually delete all files
of the old version before executing the installation.

 For the number of IP addresses and VIP addresses that need to be planned for
each deployment mode, see section 1.1.2 Deployment mode.
 For the operation of configuring IP addresses, see section 4.1.5 How to configure
the static IP address and firewall for the server.
 If the NMS is installed and the host name needs to be modified, see section 4.3.1
Modifying the host name of the RCView server
 For the operation of disabling the firewall in the OS, see section 4.1.5 Configuring
firewall.
 For the operation of disabling SELinx can be found in "4.1.4 How to disable
SELinx".

Raisecom Proprietary and Confidential 19

2 Installation and deployment

This chapter describes how to install the RCView in details, including the following sections:
 Uploading installation files
 Installing system
 Checking installation status
 Upgrading the RCView system through installation program

2.1 Uploading installation files

The RCView supports installation on CLI. You only need to upload installation files to one
server and execute installation once.
 In local installation mode, upload files to the RCView server. In remote installation mode,
install files to a Linux computer.
 Upload the entire nms_install directory in the installation file package to a directory of
the server, for example, /usr/local. Execute the command in the nms_install directory of
the server as a root-level user or the general user with the sudo right.
– Or decompress the installation file Tar package on one computer, and use the upload
software to upload the entirely decompressed nms_install directory to the server.
– Or use the upload software to upload the installation file compressed package to the
server, and then decompress it through the tar –xvf package file name command to
generate the nms_install directory.
– The installation file directory nms_install is in the /usr/local, /root, /home, other
directories, but the RCView installation directory must be in the /usr/local directory.
 Upload the License file to a directory of the server, such as /usr/local. Specify the
directory and name of the License file during later installation.

2.2 Installing system

 Do not install components repeatedly, otherwise related functions may be restored

to default conditions, data may be lost, or the system may malfunction.

Raisecom Proprietary and Confidential 20

 Keep the License carefully, which is used during installation and maintenance.
 The License file determines the non-HA deployment mode and HA deployment
mode. Before installation, confirm the deployment mode and then contact
technical support personnel for applying the License file.
 The trial License can be used on any server. The formal License is bound with the
MAC address upon application.
 When you update the License, the new one will override the old one on the server;
thus back up the old one before update. The default directory of the License file is
/usr/local/nms/comp/service/webapp/config/license/license.xml.
 If network interruption, abnormal restore, or other events occur during installation,
use the uninstallation command on each server, and then re-install the RCView
software.
 When the system involves multiple servers, their host names must be different.
Modify their host names before installation. Use the hostnamectl set-hostname
name command and reboot command to modify the host name. The host name
cannot contain the period (.).

2.2.1 Initial steps

Step 1 Log in to the server as a root-level user or the general user with the sudo right, and enter the
directory of the installation file, such as /usr/local/nms_install.

localhost login: root

password:
Last login: Thu Jul 12 02:55:35 2021 from 172.16.125.129
[root@localhost /]# cd /usr/local/nms_install

Step 2 Run the installation script. When you run the installation script, the RCView will decompress
the installation files. You can use the sh install_en.sh command to install the RCView system.
The install_en.sh script shows the English information only, and its other functions are the
same with the install.sh.

[root@localhost nms_install]# sh ./install.sh

Preparing the runtime environment...

Step 3 Configure the system language which will be used by the browser interface during installation
and system usage, or enter the number for language selection and press Enter, or use Chinese
by pressing Enter.

Select a language (1:English/2: Chinese (default)):

Step 4 Configure the directory of the License file. The file name and size should meet actual
conditions. Take /usr/locallicense.xml for example. In HA mode, the license will show "ha".

input license path(/usr/local/license.xml):/usr/local/license_ha.xml

Raisecom Proprietary and Confidential 21

input install path(/usr/local/nms):^C[root@localhost nms_install]#

Step 5 (Optional) the NETCONF component of the RCView is an independent component package,
which is applicable to the devices that can be managed by the NETCONF NMS. To use the
NETCONF component, contact the technical support personnel to obtain it and upload it to
the /usr/local/ path. If the license authorizes you with the NETCONF component but you do
not want to use it, press y to proceed.

input license path(/usr/local/license.xml):/usr/local/license_one.xml

Netconf has been authorized,/usr/local/netconf.tar.gz is not exists
Continue(y/n)?:
y
input install path(/usr/local/nms):

Step 6 Configure the system installation path. Or enter a complete directory and then press Enter or
press Enter to enter the /usr/local/nms directory.

Input install path (/usr/local/nms):

Step 7 Configure the system time zone. Enter the number to select the time zone of the server and
press Enter.

Select a time zone(GTM+8):

1:GTM Europe/London
2:GTM+1 Europe/Paris
3:GTM+2 Africa/Cairo
4:GTM+3 Europe/Moscow
5:GTM+4 Asia/Dubai
6:GTM+5 Indian/Maldives
7:GTM+6 Asia/Rangoon
8:GTM+7 Asia/Bangkok
9:GTM+8 Asia/Shanghai
10:GTM+9 Asia/Tokyo
11:GTM+10 Australia/Sydney
12:GTM+11 Asia/Srednekolymsk
13:GTM+12 Pacific/Auckland
14:GTM-1 Atlantic/Azores
15:GTM-2 Atlantic/South_Georgia
16:GTM-3 America/Argentina/Buenos_Aires
17:GTM-4 America/Guyana
18:GTM-5 America/New_York
19:GTM-6 America/Chicago
20:GTM-7 America/Phoenix
21:GTM-8 America/Los_Angeles
22:GTM-9 America/Anchorage
23:GTM-10 Pacific/Honolulu
24:GTM-11 Pacific/Niue

Raisecom Proprietary and Confidential 22

input number:9

Step 8 Configure the IP address of the third-party NTP server for system time synchronization. Enter
the IP address and press Enter. It can be configured. It can also be left empty, which indicates
that the NTP server is not configured. It cannot be the same as the IP address or virtual IP
address of the RCView server.

configure NTP service

ntp IP:

2.2.2 Steps for configuring deployment parameters

After finishing initial steps, configure deployment parameters.
 The installation script prompts for deployment parameters, or click Enter after entering
the corresponding information, or click Enter to use the default parameters in brackets.
 The installation script shows the relevant parameters of the non-HA deployment mode or
the HA deployment mode according to the license.
 At present, the large-scale deployment mode is not supported.

Example for configuring small-scale deployment

Step 1 Configure the server. The installation script shows related parameters according to the
License.

[root@localhost nms_install]# sh install_en.sh

Preparing the runtime environment...
(select language)(1:English/2:Chinese): 1
input license path(/usr/local/license.xml):/usr/local/license_one.xml
input install path(/usr/local/nms):
select timezone(GTM+8):
1:GTM Europe/London
2:GTM+1 Europe/Paris
3:GTM+2 Africa/Cairo
4:GTM+3 Europe/Moscow
5:GTM+4 Asia/Dubai
6:GTM+5 Indian/Maldives
7:GTM+6 Asia/Rangoon
8:GTM+7 Asia/Bangkok
9:GTM+8 Asia/Shanghai
10:GTM+9 Asia/Tokyo
11:GTM+10 Australia/Sydney
12:GTM+11 Asia/Srednekolymsk
13:GTM+12 Pacific/Auckland
14:GTM-1 Atlantic/Azores
15:GTM-2 Atlantic/South_Georgia
16:GTM-3 America/Argentina/Buenos_Aires
17:GTM-4 America/Guyana
18:GTM-5 America/New_York

Raisecom Proprietary and Confidential 23

19:GTM-6 America/Chicago
20:GTM-7 America/Phoenix
21:GTM-8 America/Los_Angeles
22:GTM-9 America/Anchorage
23:GTM-10 Pacific/Honolulu
24:GTM-11 Pacific/Niue
input number: 9
config the NTP server
input ntp ip:
scale of input servers:
1.small scale 2.medium scale 3.large scale
1
common server:
input server(inner) IP : 172.16.125.210
input north IP(172.16.125.210):
input south IP(172.16.125.210):
input SSH port of ssh(22) :
input SSH username : root
input SSH password :

input preview
lang : English
license : /usr/local/license_one.xml
cluster : no ha
install to : /usr/local/nms
ntpserver :
timezone : Asia/Shanghai

common server:
server(inner) IP :172.16.125.210
north IP :172.16.125.210
south IP :172.16.125.210
SSH port :22
SSH username:root
SSH password:*****
Yes (Y/n):

 The northbound IP address refers to the IP address of the northbound interface of

the RCView.
 The southbound IP address refers to the IP address of the southbound interface
of the RCView.
 When configuring the northbound IP address or southbound IP address, you can
enter the specified IP address of the NIC of the RCView server or press Enter to
use the IP address in brackets. Press Enter directly if there is no specific
requirement.
 Confirm in advance the connectivity of the system IP address and VIP address
with the device network, web client network, northbound/southbound interface
network, and network gateway.
 For detailed requirements on IP addresses, see section 1.2.6 Requirements on IP
addresses.

Raisecom Proprietary and Confidential 24

Example for configuring medium-scale deployment

Step 1 Configure the comprehensive service server. The related IP addresses of the comprehensive
service server are used by the client, northbound interface, and southbound interface. The
installation script shows related parameters according to the License of the standalone
deployment mode.

scale of input servers:

1.small scale 2.medium scale 3.large scale
2
common server:
input server(inner) IP : 172.16.125.210
input north IP(172.16.125.210):
input south IP(172.16.125.210):
input SSH port of ssh(22) :
input SSH username : root
input SSH password :

use prepare database(y/N):n

database server:
input server(inner) IP : 172.16.125.211
input SSH port of ssh(22) :
input SSH username : root
input SSH password :

PM server:
please select the install node[1, 172.16.125.210, 2, 172.16.125.211]:
please input number(2):2

Step 2 Configure the pre-deployment database, which is applicable to the use of an independent
database in construction and planning. The pre-deployment database is provided by other
server or vendors to work as the database of the RCView system, but it is not controlled by
the RCView, so its normal operation is ensured by its provider.
 The following example does not use the pre-deployment database. The database is
installed as the RCView system is installed.

use prepare database(y/N):n

database server
input server(inner) IP : 172.16.125.211
input SSH port of ssh(22) :
input SSH username : root
input SSH password :

 The following example uses the pre-deployment database, which contains 2 database
instances for the RCView system and PM service respectively. The default ports are
23306 and 23308 respectively.

use prepare database(y/N):y

Raisecom Proprietary and Confidential 25

Pre-deployed database:
input database IP : 172.16.125.220
input port of database(23306) :
input database username :root
input database password :
input port of pmdb database(23308) :
input pmdb database username :root
input pmdb database password :

Step 3 Configure the PM server. By selecting the SN of the deployment node, you can select the
server with the PM. Select the PM server to be the same as the comprehensive server.
 The following example shows how to deploy the PM server without using the pre-
deployment database.

PM server:
please select the install node[1, 172.16.125.210, 2, 172.16.125.211]:
please input number(2):1

 The following example shows how to deploy the PM server to be the same with the
comprehensive server when the pre-deployment database is used.

PM server:
please select the install node[1, 172.16.125.210, 2, other server]:
please input number:1

Example for configuring small-scale HA deployment

Step 1 Configure the comprehensive service server and VIP address. The installation script shows
related parameters according to the License of the HA deployment mode.

scale of input servers:

1.small scale 2.medium scale 3.large scale
1
primary common server:
input server(inner) IP : 172.16.125.210
input north IP(172.16.125.210):
input south IP(172.16.125.210):
input SSH port of ssh(22) :
input SSH username : root
input SSH password :

secondary common server:

input server(inner) IP : 172.16.125.211
input north IP(172.16.125.211):
input south IP(172.16.125.211):
input SSH port of ssh(22) :

Raisecom Proprietary and Confidential 26

input SSH username : root

input SSH password :

select vip type

1:create new vip
2:cancel
1
input virtual ip :172.16.125.230
bind primary ip (172.16.125.210):
bind secondary ip (172.16.125.211):
subnet mask(1~31) :24
gateway :172.16.125.231
virtual ip desc :vip1
select vip type
1:create new vip
2:cancel
1
input virtual ip :172.16.125.240
bind primary ip (172.16.125.210):
bind secondary ip (172.16.125.211):
subnet mask(1~31) :24
gateway :172.16.125.241
virtual ip desc :vip2
select vip type
1:create new vip
2:cancel
2
input inner vip:
inner use vip:
[ 1,172.16.125.230 2,172.16.125.240 ]
please input number:2

 The internally used VIP address is the VIP address used for communication inside
the server.
 In the entire RCView system, there must be one and only one internal
communication VIP address, and the internal communication VIP address cannot
be the same as the southbound VIP address.
 The northbound VIP address and southbound VIP address cannot be the same as
the IP address of the VIP gateway.
 The VIP must be the IP that is not used on the server network.
 Confirm in advance the connectivity of the system IP address and VIP address
with the device network, web client network, northbound/southbound interface
network, and network gateway.
 For detailed requirements on IP addresses, see section 1.2.6 Requirements on IP
addresses.
Step 2 (Applicable when the northbound VIP and southbound VIP are used) after configuring the
VIP address, specify the configured VIP address to be used by the southbound interface or
northbound interface of the RCView.

Raisecom Proprietary and Confidential 27

config north vip?(y/N):y

use vip:[ 1, 172.16.125.230 2, 172.16.125.240 ]
please input number:1
config south vip?(y/N):y
use vip:[ 1, 172.16.125.230 2, 172.16.125.240 ]
please input number:1

Example for configuring medium-scale HA deployment

Step 1 Configure the comprehensive service server. The installation script shows related parameters
according to the License of the HA deployment mode.

scale of input servers:

1.small scale 2.medium scale 3.large scale
2
primary common server:
input server(inner) IP : 172.16.125.210
input north IP(172.16.125.210):
input south IP(172.16.125.210):
input SSH port of ssh(22) :
input SSH username : root
input SSH password :

secondary common server:

input server(inner) IP : 172.16.125.211
input north IP(172.16.125.211):
input south IP(172.16.125.211):
input SSH port of ssh(22) :
input SSH username : root
input SSH password :

use prepare database(y/N):n

primary database server:
input server(inner) IP : 172.16.125.212
input SSH port of ssh(22) :
input SSH username : root
input SSH password :

secondary database server:

input server(inner) IP : 172.16.125.213
input SSH port of ssh(22) :
input SSH username : root

Raisecom Proprietary and Confidential 28

input SSH password :

 The following example uses the pre-deployment database, which contains 2 database
instances for the RCView system and PM service respectively. The default ports are
23306 and 23308 respectively.

use prepare database(y/N):y

Pre-deployed database:
input database IP : 172.16.125.220
input port of database(23306) :
input database username :admin
input database password :
input port of pmdb database(23308) :
input pmdb database username :admin
input pmdb database password

PM server:
please select the install node[1,(172.16.125.210,172.16.125.211),
2,(172.16.125.212,172.16.125.213):
please input number(2):2

 The following example shows how to deploy the PM server to be the same with the
comprehensive server when the pre-deployment database is used.

PM server:
please select the install node[1,(172.16.125.210,172.16.125.211), 2,other
erver]:
please input number:1

Step 4 Configure the VIP address.

select vip type

1:create new vip
2:cancel
1
input virtual ip :172.16.125.230
bind primary ip (172.16.125.210):
bind secondary ip (172.16.125.211):
subnet mask(1~31) :24

Raisecom Proprietary and Confidential 29

gateway :172.16.125.231
virtual ip desc :vip1
select vip type
1:create new vip
2:cancel
1
input virtual ip :172.16.125.240
bind primary ip (172.16.125.210):
bind secondary ip (172.16.125.211):
subnet mask(1~31) :24
gateway :172.16.125.241
virtual ip desc :vip2
select vip type
1:create new vip
2:cancel
2
input inner vip:
inner use vip:
[ 1,172.16.125.230 2,172.16.125.240 ]
please input number:2

Step 5 After configuring the VIP address, specify the configured VIP address to be used by the
southbound interface or northbound interface of the RCView.

config north vip?(y/N):y

use vip:[ 1,172.16.125.230 2,172.16.125.240 ]
please input number:1
config south vip?(y/N):y
use vip:[ 1,172.16.125.230 2,172.16.125.240 ]
please input number:1

2.2.3 Steps for confirming and executing installation

Step 1 After configuring parameters of the deployment mode, press Enter to show entered and to-
be-confirmed installation parameters. After confirmation, type "y", and press Enter to
execute the installation. If you type "n" and press Enter, you will exit the installation script.
The following section takes small-scale deployment for example. For the confirmation
information, other deployment modes are similar.

input preview
lang : English
license : /usr/local/license_one.xml
cluster : no ha
install to : /usr/local/nms
ntpserver :
timezone : Asia/Shanghai

common server:
server(inner) IP :172.16.125.210
north IP :172.16.125.210

Raisecom Proprietary and Confidential 30

south IP :172.16.125.210
SSH port :22
SSH username:root
SSH password: *****

Yes (Y/n):

Step 2 The RCView starts checking and executing all installation steps.

Installation will start

start check server status
172.16.125.210 ssh connect success
172.16.125.210 check sudo
172.16.125.210 check other ip
172.16.125.210 check /var/install_mark.json
172.16.125.210 check installpath/usr/local/nms
172.16.125.210 check process uninstall
…

If the residual data of the old version is detected in the directory, the installation script
will pop up a prompt and exit the installation. In this case, you need to manually
delete all the files of the old version before installation.

2.2.4 Example for installation and deployment

Networking requirements
Four servers are used to implement medium-size HA deployment, as shown in Figure 2-1.
 Deploy the comprehensive service/PM/EMS server and database server respectively.
 Configure the 188.105.180.214/29 as VIP address 1, configure the gateway address to
188.105.180.209/29, and configure the RCView to support Web. The user accesses the
RCView system through VIP address 1 on the Web browser. The vNIC0 Ethernet
interfaces on server 1 and server 2 are bound with VIP address 1.
 Configure 188.105.180.220/29 as VIP address 2, configure 188.105.180.217/29 as the
gateway address, and allow the gateway to be connected with devices. After the device is
configured with VIP address 2 as the Trap target address and the IP address of the
RCView system, the RCView system can receive alarms and configure NEs. The
Ethernet interfaces vNIC1 on server 1 and server 2 are bound with VIP address 2.
 Divide VIP address 1 and VIP address 2 into different subnets to implement data
isolation.
 There is no need to configure the independent northbound IP/VIP address and
southbound IP/VIP address.
 Deploy with virtual machines, with the relevant configurations shown in Table 2-1. The
vNIC0 IP address of each server and its corresponding VIP address 1 and gateway IP
address are in the same network segment. The vNIC1 IP address and its corresponding
VIP address 2 and gateway IP address of each server are in the same network segment.

Raisecom Proprietary and Confidential 31

Figure 2-1 Networking connection

Web client

Web client Management Management

network network gateway
System server

VIP1 Database

Database

Database
Comprehensiv

Comprehensiv
E P E P IP
e service

e service
M M M M
S VIP2 S

Server Communication between

network browser and server
Communication between
NE Serv RCView and device
Network Communication
between servers
NE Gateway Communication between
server and gateway

Table 2-1 Server planning table

VM name vCPU Memo Syste Data vNIC Logic network IPv4 address
ry m disk interfac name
(GB) disk (GB) e name
(GB)
NFV- 8 16 50 1000 vNIC0 NFV-XXX-Mgmt- 188.105.180.210/29
XXX-VM1 DCN
vNIC1 NFV-XXX-Serv- 188.105.180.218/29
DCN
NFV- 8 16 50 1000 vNIC0 NFV-XXX-Mgmt- 188.105.180.211/29
XXX-VM2 DCN
vNIC1 NFV-XXX-Serv- 188.105.180.219/29
DCN
NFV- 8 16 50 500 vNIC0 NFV-XXX-Mgmt- 188.105.180.212/29
XXX-VM3 DCN
NFV- 8 16 50 500 vNIC0 NFV-XXX-Mgmt- 188.105.180.213/29
XXX-VM4 DCN

Configuration steps - initial steps

Step 1 Log in to the server as a root-level user or general user with the sudo right. Enter the directory
with the installation files. In this example, the directory is /usr/local/nms_install.

Raisecom Proprietary and Confidential 32

localhost login: root

password:
Last login: Thu Jul 12 02:55:35 2021 from 188.105.180.21
[root@localhost /]# cd /usr/local/nms_install

Step 2 Run the installation script. When running the installation script for the first time, the system
decompress some installation files. Use the sh install_en.sh command to install the system.
The install_en.sh shows the English information only while its other functions are the same
with those of the install.sh script.

[root@localhost nms_install]# sh install.sh

Preparing the runtime environment...

Step 3 Configure the system language, which will be used in the installation process and on the
browser interface in using the system. To choose English, type "1".

(select language)(1:English/2:Chinese): 1

Step 4 Configure the License path. The file name and size must comply with the actual situations.
Take /usr/local/license.xml for example. If the HA mode is used, the system prompts "HA"/

input license path(/usr/local/license.xml):/usr/local/license_one.xml

Step 5 In this example, the License authorizes NETCONF component, but does not need the
component. Type "y" to continue.

Netconf has been authorized,/usr/local/netconf.tar.gz is not exists

Continue(y/n)?:
y

Step 6 Configure the installation path of the system. In this example, press Enter to use the
usr/local/nms path.

input install path(/usr/local/nms):

Step 7 Configure the system time zone. Enter the number of the time zone for the server, and press
Enter. Take "9:GTM+8 Asia/Shanghai" for example.

Select a time zone(GTM+8):

Raisecom Proprietary and Confidential 33

Step 8 In this example, this step is left null. Press Enter to skip configuring the NTP server.

configure NTP service

ntp IP:

Configuration steps for installation and planning

Step 1 Configure the comprehensive server. The installation script shows related parameters
according to the License of the HA deployment mode.

scale of input servers:

1.small scale 2.medium scale 3.large scale
2
common server:
input server(inner) IP : 188.105.180.210
input north IP(188.105.180.210):
input south IP(188.105.180.210):
input SSH port of ssh(22) :
input SSH username : root
input SSH password :

use prepare database(y/N):n

database server:

Raisecom Proprietary and Confidential 34

input server(inner) IP : 188.105.180.211

input SSH port of ssh(22) :
input SSH username : root
input SSH password :

Step 2 Configure the database information. In this example, the database is installed as the RCView
system is installed.

use prepare database(y/N):n

primary database server:
input server(inner) IP : 188.105.180.212
input SSH port of ssh(22) :
input SSH username : root
input SSH password :

secondary database server:

input server(inner) IP : 188.105.180.213
input SSH port of ssh(22) :
input SSH username : root
input SSH password :

Step 3 Configure the PM server. By selecting the sequence number of the deployment node, you can
select the PM server, which should be the same server as the comprehensive server.

PM server:
please select the install node[1, (188.105.180.210, 188.105.180.211), 2,
(188.105.180.212, 188.105.180.213] ]:
please input number:1

Step 4 Configure the VIP information. Bind the vNIC0 Ethernet interfaces on server 1 and server 2
with VIP address 1. Bind the vNIC1 Ethernet interfaces on server 1 and server 2 with VIP
address 2.

select vip type

1:create new vip
2:cancel
1
input virtual ip :188.105.180.214
bind primary ip (188.105.180.210):
bind secondary ip (188.105.180.211):
subnet mask(1~31) :29
gateway :188.105.180.209
virtual ip desc :vip1
select vip type
1:create new vip
2:cancel
1

Raisecom Proprietary and Confidential 35

input virtual ip :188.105.180.220

bind primary ip (188.105.180.218):
bind secondary ip (188.105.180.219):
subnet mask(1~31) :29
gateway :188.105.180.217
virtual ip desc :vip2
select vip type
1:create new vip
2:cancel
2
input inner vip:
inner use vip:
[ 1,188.105.180.230 2,188.105.180.220 ]
please input number:1

Step 5 This example does not use the northbound VIP address and southbound VIP address.

config north vip?(y/N):y

config south vip?(y/N):y

Configuration steps for confirming and executing installation

Step 1 After confirmation, type "y", and press Enter to start installation.

input preview
lang : English
license : /usr/local/license_one.xml
cluster : ha
install to : /usr/local/nms
ntpserver :
timezone : Asia/Shanghai
…
Yes (Y/n):y

Step 2 The system starts checking and automatically executing all installation steps.

Installation will start

Raisecom Proprietary and Confidential 36

all check success

172.16.68.209 ssh connect ok
172.16.68.209 /usr/local/msp/ have create finish ,start install modules
...
172 .16.68.209[install](50/50 )otne2e
172.16.68.209install finish
Configure apigateway
Configure database
install success

Checking results
 The user accesses the RCView system through VIP address 1 on the Web browser.
 After the device is configured with VIP address 2 as the Trap target address and the IP
address of the RCView system, the RCView system can receive alarms and configure
NEs.

2.3 Checking installation status

Step 1 Access the IP address of the server with the comprehensive service through a browser, and the
login interface should be displayed.
Step 2 Enter the default user name "administrator", password "Rw@2025#" and verification code to
log in to the system.
Step 3 Choose System in the top navigation bar, and then choose System > System Mgmt >
Components in the navigation tree on the left. Select the Application tab. Check whether the
Running Status of a started component is "Normal", as shown in the figure below. Some
components are in Stopped status; to start them, click .

Step 4 Select the Basic Services tab. Check whether the Running Status of a started component is
"Running", as shown in the figure below.

Raisecom Proprietary and Confidential 37

2.4 Upgrading the RCView system through installation

program
After one version of the RCView system is installed, a later version can be installed to
upgrade the RCView system.
 The normal RCView system of different deployment modes can be upgraded through
installation programs.
 When the installation program is ongoing, the RCView system will be unavailable.
Step 1 Check the current RCView system. Ensure that it is working properly before being upgraded
through the installation program.
Step 2 Decompress the installation package of the later version to the /root/ directory.
Step 3 Use the cd nms_install command to enter the new directory after decompression.
Step 4 Run the installation script. When you run the installation script, the RCView will decompress
the installation files. You can use the sh install_en.sh command to install the RCView system.
The install_en.sh script shows the English information only, and its other functions are the
same with the install.sh.

[root@host1721668112 nms_install]# sh install_en.sh

Preparing the runtime environment...

Step 5 Type "1" to configure the upgrade.

please select(1:upgrade/2:uninstall)1

Raisecom Proprietary and Confidential 38

Step 6 After confirming the upgrade option, type "y", and press Enter to execute the installation.

upgrade message
lang : English
cluster : no ha
install to : /usr/local/nms
ip :172.16.68.158
sshport :22
user :root
install version:
systemversion: 20230811183453
platform: 2.3.0
WDM: 3.1.0
TRANS: 3.2.2
SWITCH: 2.3.0
PON: 2.3.0
PM2000: 2.3.0
MSG: 2.3.0
upgrade version:
systemversion: 20230814100748
platform: 2.3.0
WDM: 3.1.0
TRANS: 3.2.2
SWITCH: 2.3.0
PON: 2.3.0
PM2000: 2.3.0
MSG: 2.3.0
Yes (Y/n):

Step 7 The RCView system starts checking and automatically executes all installation procedures.

Installation will start

start check server status
172.16.68.209 ssh connect success
172.16.68.209 check sudo
172.16.68.209 check other ip
172.16.68.209 check /var/install_mark.json
172.16.68.209 check installpath/usr/local/nms
172.16.68.209 check process uninstall
172.16.68.209 check database data file
172.16.68.209 check disk space
172.16.68.209 check success
all check success
172.16.68.209 ssh connect ok
172.16.68.209 /usr/local/msp/ have create finish ,start install modules
...
172 .16.68.209[install](50/50 )otne2e
172.16.68.209install finish
Configure apigateway
Configure database
install success

Raisecom Proprietary and Confidential 39

Step 8 Type "n", and press Enter. This indicates the completion of the upgrade and no rollback.
(Optional) type "y" to roll back to the previous version.

Preparing…
rollback?(y/n):
n

Raisecom Proprietary and Confidential 40

3 Uninstallation

This chapter describes how to uninstall the system server, including the following sections:
 Uninstalling system
 Checking uninstallation status

3.1 Uninstalling system

After the RCView system is uninstalled, it and its data cannot be restored. Use this
operation with caution according to actual situations.
When uninstalling the RCView, you can choose whether to delete data files. The deleted files
cannot be recovered, choose according to the actual situation.

Uninstalling system on single server

Step 1 Log in to the server as a root-level user or the general user with the sudo right, and enter the
system directory, such as /usr/local/nms/.

login as: root

[email protected]'s password:
Last login: Sat Jan 28 22:07:21 2020
[root@host17216125210 ~]# cd ..
[root@host17216125210 /]# cd /usr/local/nms/

Step 2 Run the uninstallation script.

[root@host17216125210 nms]# sh ./uninstall.sh

Raisecom Proprietary and Confidential 41

Step 3 Type "y" and press Enter to uninstall. The uninstallation process displays related information,
such as stopped components and successful uninstallation

Are you sure want to uninstall?:(y/N):y

stop daemon_run
stop and uninstall commonserver
stop and uninstall tiap-ems-wdm-mgt
stop and uninstall netconf
...

Step 4 (Optional) type "y" and press Enter to delete the system data.

delete mysql data file /var/db/nms(y/n):y

Step 5 Type "y" and press Enter to restart the RCView and complete uninstallation.

uninstall finish must reboot !

Reboot now?(y/N):y

Uninstalling system on multiple servers

Execute the script on the master server. Installing the system on multiple servers at a time is
supported.
Step 1 Log in to the server as a root-level user or the general user with the sudo right, and enter the
system directory, such as /usr/local/nms/.

login as: root

[email protected]'s password:
Last login: Sat Jan 28 22:07:21 2020
[root@host17216125210 ~]# cd ..
[root@host17216125210 /]# cd /usr/local/nms/

Step 2 Run the uninstallation script.

[root@host17216125210 nms]# sh uninstall.sh group

Step 3 Type "y" and press Enter to uninstall.

server 1:

Raisecom Proprietary and Confidential 42

ip :172.16.125.210
sshport :22
user :root
pass :******

server :
ip :172.16.125.211
sshport :22
user :root
pass :******

uninstall all server?:(y/N):y

Step 4 (Optional) type "y", and press Enter to delete the system data.

delete mysql data path /var/db/nms?(Y/n):y

Step 5 The uninstallation process shows the stopped components and prompt of successful
uninstallation.

start uninstall ...

172.16.125.210 connect success
172.16.125.210 [root@host17216125210 ~]#
172.16.125.210 stop daemon_run
172.16.125.210 stop and uninstall commonserver
…
172.16.125.210 uninstall finish must reboot !
172.16.125.210 true
172.16.125.210 uninstall success
172.16.125.210 clear system file

Step 6 Type "y" and press Enter. Restart the RCView and complete uninstallation.

Reboot now?(y/N):y

3.2 Checking uninstallation status

Step 1 Access the IP address of the server with the comprehensive service. It should be inaccessible.
Step 2 Use the sudo ss -lnp |grep 3000 command on the server, and no information about the
process should be echoed.
Step 3 Check the system directory of the server, such as the /usr/local directory. There should be no
nms directory in this directory.

Raisecom Proprietary and Confidential 43

4 Appendix

This chapter includes the following sections:

 FAQs for the OS
 FAQs for the RCView
 FAQs for the Nmstools tool
 Terms
 Acronyms and abbreviations

4.1 FAQs for the OS

4.1.1 No idle hard disk is detected in installing the OS
Step 1 Click Installation Destination, as shown below.

Raisecom Proprietary and Confidential 44

Step 2 Choose a hard disk for installing the CentOS, such as sdb1 (similar to disk C), as shown
below.

Step 3 Click Delete. You can see the size to be recycled.

Step 4 Click Reclaim Space to recycle the space of the sdb1 disk.
Step 5 Return to the previous menu. Choose the disk to be installed with CentOS. Click Configure
Partition. Click Finish. You can see that the space has been enlarged.

Raisecom Proprietary and Confidential 45

4.1.2 How to check the space of the directory

Check the space of the directory to learn the space usage.
Step 1 Check the space of the directory.

login as: root

/*log in as a Root-level user*/
[email protected]'s password:
Last login: Wed Aug 1 21:01:36 2018 from bogon
[root@bogon ~]# df -h
Filesystem Size Used Avail Use% Mounted on
/dev/mapper/centos-root 270G 90.0G 180G 34% /
/*check the root directory for the total space, used space, available
space, utilization, and mounting directories. */
/dev/sda1 1014M 142M 873M 14% /boot

Step 2 Check the /usr/local directory. Refer to the following example.

[root@bogon ~]# cd /usr/local

[root@bogon local]# du -sh *
252K bin
108K etc
0 games
0 include
0 lib
0 lib64
0 libexec
12K license01.xml
12K license02.xml
4.6G nms
/*space used by RCView system programs*/
3.3G nms_install
/* space used by RCView installation programs */
1.4M sbin
220K share
0 src

Step 3 Check the /home directory. Refer to the following example.

[root@bogon ~]# cd /home

[root@bogon home]# du -sh *
12K admin1

Raisecom Proprietary and Confidential 46

4.1.3 How to configure the size of the partitions of the directory

space
Step 1 Use the df -h command to show the partition size. It is found that the /home space is too large
while the root space is too small. Take the 400G space for example.

Step 2 Use the mount grep root or mount rep home command to show the system type of the file
partition.
Step 3 If the type is ext2/ext3/ext4, use the following command to adjust the size.

-------the command for adjusting the ext2/ext3/ext4 file system is

resize2fs (supporting increasing or decreasing).
lvreduce -L -400G /dev/mapper/centos-home //decrease the home space by
400G.
resize2fs /dev/mapper/centos-home //execute adjustment.
lvextend -L +400G /dev/mapper/centos-root //increase the root space by
400G.
resize2fs /dev/mapper/centos-boot //execute adjustment.

Step 4 If the type is xfs, only increasing is supported, and the partition needs to be unloaded in
advance (also clearing all data in the partition).

-------the command for adjusting the xfs file system is xfs_growfs (only
increasing is supported).
-------if needed, back up data in the home partition to other partitions.
cp –R /home/* /var/back
-------unload the home partition.
umount /home/
-------if the system prompts that the home partition is busy, it executes
fuser, and then it execute umount /home/.
fuser -km /home/

lvreduce -L -400G /dev/mapper/centos-home // decrease the home space

by 400G.
xfs_growfs /dev/mapper/centos-home // execute adjustment.
mkfs.xfs /dev/mapper/centos-home -f //format the home partition.
mount /dev/mapper/centos-home /home/ //load to the home partition
again.
lvextend -L +400G /dev/mapper/centos-root //increase the root
partition by 400G.
xfs_growfs /dev/mapper/centos-root // execute adjustment.

Raisecom Proprietary and Confidential 47

Step 5 Use the df -h command to show the partition size, and check whether the adjustment is
successful.

4.1.4 How to disable SELinux

To install the RCView in CentOS 7/8/9, disable SELinux in advance.
Step 1 Modify the SELINUX to disabled in the configuration file in the /etc/selinux/config path, as
shown below.

Step 2 Press Esc to exit editing. Type ":wq!", and press Enter to save configurations.
Step 3 Restart the RCView server. Use the sestatus command to check whether the SELinux status
is disabled, as shown below.

4.1.5 How to configure the static IP address and firewall for the
server
After installing the operating system, you should first configure the IP address locally on the
server, configure the firewall and restart the server host, and then install the RCView.

Configuring IP address on graphical interface

Nmtui is the network interface configuration function of CentOS on the graphical interface.
Take the static IP address of 172.16.125.210/24, the gateway 172.16.125.1, and the DNS
172.16.8.8 as examples. The configuration commands are as follows.
Step 1 Start the Nmtui.

login as: root

/*log in as a root user */
[email protected]'s password:
Last login: Wed Aug 1 21:01:36 2018 from bogon
[root@bogon ~]# nmtui

Raisecom Proprietary and Confidential 48

Step 2 Use the arrow keys to select Edit a connection, and press Enter to show the network interface,
as shown in the figure below.

Raisecom Proprietary and Confidential 49

Step 3 Press Enter to select the network interface, enter the interface to configure the network
interface as Manual mode, static IP address and gateway address, as shown in the figure
below.

Step 4 Use the arrow keys to select OK. Press Enter to complete the configuration and return to the
network interface selection interface. Use the arrow keys to select Quit and press Enter to
exit the program, as shown in the figure below.

Raisecom Proprietary and Confidential 50

Configuring IP address in CLI

Take the static IP address 172.16.125.210/24, gateway 172.16.125.1, and DNS 172.16.8.8 as
an example, the configuration commands are as follows:

login as: root

/*login as a root user */
[email protected]'s password:
Last login: Wed Aug 1 21:01:36 2018 from bogon
[root@bogon ~]# ip link show
/*check information about the network card. */
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN mode
DEFAULT group default qlen 1000
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
2: ens33: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast
state UP mode DEFAULT group default qlen 1000
link/ether 00:0c:29:d8:f8:89 brd ff:ff:ff:ff:ff:ff

Raisecom Proprietary and Confidential 51

/*check the network card which is ens33 in this example. Select a network
card according to the actual situation.*/
[root@bogon ~]# sed -i '/^ONBOOT=/c\ONBOOT=yes' /etc/sysconfig/network-
scripts/ifcfg-ens33
/*configure starting the network card once the device is started.*/
[root@bogon ~]# sed -i '/^BOOTPROTO=/c\BOOTPROTO=static'
/etc/sysconfig/network-scripts/ifcfg-ens33
/*configure the IP address of the network card to static.*/
[root@bogon ~]# echo 'IPADDR=172.16.125.210' >> /etc/sysconfig/network-
scripts/ifcfg-ens33
/*configure the static IP address of the network card.*/
[root@bogon ~]# echo 'PREFIX=24' >> /etc/sysconfig/network-scripts/ifcfg-
ens33
/*configure the static IP address mask of the network card.*/
[root@bogon ~]# echo 'GATEWAY=172.16.125.1' >> /etc/sysconfig/network-
scripts/ifcfg-ens33
/*configure the gateway IP address of the network card.*/
[root@bogon ~]# echo 'DNS1=172.16.8.8' >> /etc/sysconfig/network-
scripts/ifcfg-ens33
/*configure the DNS address of the network card.*/
[root@bogon ~]# cat /etc/sysconfig/network-scripts/ifcfg-ens33
/*check configurations of the network card.*/
TYPE=Ethernet
PROXY_METHOD=none
BROWSER_ONLY=no
BOOTPROTO=static
DEFROUTE=yes
IPV4_FAILURE_FATAL=no
IPV6INIT=yes
IPV6_AUTOCONF=yes
IPV6_DEFROUTE=yes
IPV6_FAILURE_FATAL=no
IPV6_ADDR_GEN_MODE=stable-privacy
NAME=ens33
UUID=fab5c0a9-69d6-40e5-8f19-aac579c1277b
DEVICE=ens33
ONBOOT=yes
IPADDR=172.16.125.210
PREFIX=24
GATEWAY=172.16.125.1
DNS1=172.16.8.8

Configuring firewall
Take the firewall in the OS with the standalone deployment for example. The configuration
commands are as follows.

The firewall-cmd is a firewall tool in the OS. If there is a third-party firewall, you can
use the systemctl stop firewalld command to disable the system firewall.
You can install the tool by using the yum install firewalld firewalld-config
command. The parameters of the firewall-cmd command are described as below:

Raisecom Proprietary and Confidential 52

 -zone=public: add the port to the area (by default, interfaces are in the public
area).
 --add-port: identify the added port.
 --remove-port: identify the deleted interface.
 --permanent: configure the period to permanent.
 --reload: restart the firewall (after configurations are modified, the firewall needs to
be restarted).

Step 1 Use the systemctl start firewalld command to enable the firewall in the OS.
Step 2 Use the following command to enable ports.

[root@bogon ~]# firewall-cmd --zone=public --add-port=8008/tcp --

permanent
success
[root@bogon ~]# firewall-cmd --zone=public --add-port=2121/tcp --
permanent
success
[root@bogon ~]# firewall-cmd --zone=public --add-port=20/tcp --
permanent
success
[root@bogon ~]# firewall-cmd --zone=public --add-port=21/tcp --
permanent
success
[root@bogon ~]# firewall-cmd --zone=public --add-port=80/tcp --
permanent
success
[root@bogon ~]# firewall-cmd --zone=public --add-port=65500-65510/tcp –
permanent
success
[root@bogon ~]# firewall-cmd --zone=public --add-port=69/udp --add-
port=123/udp --add-port=162/udp --permanent
success

Step 3 Use the firewall-cmd --reload command to make access rule take effect.
Step 4 Use the firewall-cmd --list-all command to show the firewall rule.

4.1.6 How to modify the IP address of the CentOS 7 server

Modifying the IPv4 address of the server

Step 1 Use the cd /etc/sysconfig/network-scripts command to enter the network configuration file
directory.
Step 2 Use the ll command to show the name of the NIC.

[root@host1721646223 network-scripts]# ll
total 232
-rw-r--r--. 1 root root 367 4 Apr 22 23:05 ifcfg-enp0s31f6

Raisecom Proprietary and Confidential 53

-rw-r--r--. 1 root root 254 5 May 22 2020 ifcfg-lo

…

Step 3 Use the vi ifcfg-enp0s3f6 command to edit the network configuration file.
Step 4 Use the i command to edit the file.

Step 5 Press ESC to exit editing. Use the :wq! command to save configurations.
Step 6 Use the service network restart command to restart the server to make configurations take
effect.

Modifying the IPv6 address of the server

Step 1 Use the cd /etc/sysconfig/network-scripts command to enter the network configuration file
directory.
Step 2 Use the ll command to show the name of the NIC.

[root@host1721646223 network-scripts]# ll
total 232
-rw-r--r--. 1 root root 367 4 Apr 22 23:05 ifcfg-enp0s3f6
-rw-r--r--. 1 root root 254 5 May 22 2020 ifcfg-lo
…

Step 3 Use the vi ifcfg-ens33 command to edit the network configuration file.
Step 4 Use the i command to edit the file.

Raisecom Proprietary and Confidential 54

Step 5 Press ESC to exit editing. Use the :wq! command to save configurations.
Use the service network restart command to restart the server to make configurations take
effect.

4.1.7 How to modify the IP address of the CentOS 9 Stream server

Step 1 Use the cd /etc/NetworkManager/system-connections command to enter the network
configuration file directory.
Step 2 Use the ll command to show the name of the NIC.

[root@localhost system-connections]# ll
total 4
-rw-------. 1 root root 262 5 May 11 2023 ens33.nmconnection

Step 3 Use the vi ens33.nmconnection command to edit the network configuration file.
Step 4 Use the i command to edit the file.

Raisecom Proprietary and Confidential 55

Step 5 Press ESC to exit editing. Use the :wq! command to save configurations.
Step 6 Use the service network restart command to restart the server to make configurations take
effect.

[root@localhost ~]# nmcli c reload

[root@localhost ~]# nmcli c up ens33

4.1.8 How to enable remote SSH on CentOS 9 and logging in with

the root user name and password
Enable remote SSH on CentOS 9 and log in with the root user name and password as below:
Step 1 Use the vi /etc/ssh/sshd_config command as the root user.
Step 2 Configure both the PermitRootLogin and PasswordAuthentication to yes.
#LoginGraceTime 2m
#PermitRootLogin prohibit-password
PermitRootLogin yes
#StrictModes yes
#MaxAuthTries 6
#MaxSessions 10
PasswordAuthentication yes

Step 3 Press ESC to exit editing. Use the :wq! command to save configurations.
Step 4 Use the systemctl restart sshd command to restart the SSH service.

Raisecom Proprietary and Confidential 56

4.1.9 How to configure the OS time

Showing the OS time

Step 1 Use the timedatectl command to show the OS time.

Showing the time zone list of the OS

Step 1 Use the timedatectl list-timezones|grep Asia command to show the time zone list of the OS.

Manually specifying the system time

Step 1 Use the timedatectl set-ntp false command to modify the disable the network time service.
Step 2 Use the timedatectl set-time '2022-11-11 11:11:11' command to modify the system time.
Step 3 Use the timedatectl set-timezone Asia/Shanghai command to modify the system time zone.
Step 4 Use the systemctl restart systemd-timedated.service command to restart the time zone
service.
Step 5 Use the reboot-now command to manually restart the OS and to check the time modification.
Step 6 Use the timedatectl command to show the system time.

Using the NTP network time

Step 1 Use the timedatectl set-ntp true command to enable the network time service.
Step 2 Use the timedatectl set-timezone Asia/Shanghai command to modify the system time zone.
Step 3 Use the systemctl restart systemd-timedated.service command to restart the time zone
service.
Step 4 Use the reboot-now command to manually restart the OS and to check the time modification.
Step 5 Use the timedatectl command to show the system time.

4.1.10 How to show the OS language and MAC address information

Step 1 Use the echo $LANG command to show the current system language.

Raisecom Proprietary and Confidential 57

Step 2 Use the ifconfig command to show the MAC address of the host.

4.1.11 How to configure the passive interface on the FTP server

The passive mode (PASV) of the FTP server is that the client initiates the command
connection and data connection to prevent the data in the ingress direction from the server to
the client from being filtered by the firewall. The ports are described as below.

Step 1 Use the vi /usr/local/nms/comp/service/vsftpd/config/ftp/ftpd.xml command to modify the

port range.
Step 2 Use the I command to edit the text and to configure the port range of data.

Raisecom Proprietary and Confidential 58

Step 3 Press ESC to exit editing. Use the :wq! command to save configurations.
Step 4 Use the cd /usr/local/nms/comp/service/vsftpd command to enter the directory. Use
the ./stop.sh and ./run.sh commands to restart the FTP service.

4.2 FAQs for the RCView

4.2.1 Installation fails due to lack of the third-party component
During the process of installing the RCView system, the prompt of failure in installing the
RCView system appears due to lack of the third-party component, as shown below. In this
case, manually decompress the third-party component.

Step 1 Use the tar xf rcview_xxx.tar command to decompress the RCView system installation
package.
Step 2 Use the cd nms_install/nms/runtime command to enter the third-party component directory
of the RCView system.

Raisecom Proprietary and Confidential 59

Step 3 Use the tar-zxf sysenv.tar.gz command to decompress the third-party component that is
embedded with the RCView system installation program.
Step 4 Use the cd sysenv/ command to enter the third-party component file directory in the RCView
system.
Step 5 Use the install.sh command to install the third-party component that depends on the RCView
system.
Step 6 Use the cd nms_install/ command to enter the root directory of the RCView installation
program.
Step 7 Log in to the server as a root-level user or a general user with the sudo right, and enter the
installation file directory, such as/etc/local/nms_install.
Step 8 Run the installation script by using the sh install.sh command.

4.2.2 The Web client fails to connect to the server.

 Check whether the server is up and running normally.
 Check the server IP address.
 Check whether system user "access control" is enabled. If yes, configure the user's
security parameters on the local client to allow the IP address of the remote client.
 Check whether the firewall is turned on the client computer. Turning on the firewall may
cause connection failure. Turn off the firewall or add rules before connection.
– Use the systemctl status firewalld command to show the enabling status of the OS
firewall.
– Use the systemctl stop firewall command to disable the OS firewall, and then try to
connect to determine whether the cause is the firewall.
– Use the systemctl disable firewalld.service command to disable firewall startup.
– If the cause is not the firewall, use the systemctl start firewall command to enable
the OS firewall.
 Check network conditions such as the connectivity of the Web client and server.

4.2.3 SNMP trap alarms sent by NE devices cannot be received.

To ensure that the alarm can be received and displayed correctly by the system, the following
items must be met. If the system cannot receive SNMP Trap alarms, you should check the
following items first. In some specific application environments, technicians may also be
required to check other conditions by capturing messages and viewing logs.
 The network device has been correctly configured with a Trap target address, SNMP, and
other parameters.
– The alarm Trap target address of the network device must be correctly configured to
the IP address of the host where the system server is located.
– The Trap target port number of the network device is the same as the port number
monitored by the SNMP Trap receiving service in the system (the default is 162).
 All managed network devices and the computer where the system is located must be
correctly connected to the network and maintain normal link communication between
each other (for example, they can ping each other, allowing UDP, component ports, and
other network communication).

Raisecom Proprietary and Confidential 60

– In an application environment based on security requirements, all network devices

may be hidden behind the firewall. In this case, it is necessary to ensure that Trap
packets can pass through the firewall.
– The network device must be connected to the system and have a corresponding
record in the asset network element list. Otherwise, it will be treated as an unknown
alarm.
 Port 162 of the computer where the alarm component of the system is located cannot be
occupied by other programs, and the "SNMP Trap alarm receiving service" must be
activated.
 Trap messages must match the corresponding alarm types of the system. Otherwise, they
will be treated as unknown alarms.
 The alarms that match the alarm filter conditions are not displayed in the current alarm
list and are processed according to the alarm filter rules.
 The alarm will be displayed only if the user's security permission is met.
– Security permissions will not affect the system receiving alarms, but only authorized
users can view the alarms.
– The currently logged-in system user must have the authority and be able to manage
the related network elements of the alarm, that is, the user management domain must
include the related network elements. Otherwise, the alarm will not be displayed.
– Super administrators can view all alarms.

4.2.4 The server program cannot be uninstalled or cannot be re-

installed after uninstallation.
 Check the network connectivity.
 Check the IP address of the server.
 Check the root-level user and its password. For example, you can use the sudo ps -e
|grep sshd command and enter the password for verification.
 Check the SSH function of the server. For example, you can use the sudo ps -e |grep
sshd command and check if there is any sshd process information in the echo.
 Uninstall the server program again.
 Re-install the operating system.

4.2.5 How to update the License

The RCView system provides relevant functions based on the license and supports obtaining
relevant functions by updating the license file. For more detailed license management
operations, see RCView Operation Guide.

 When updating the license, pay attention to the matching relationship between the
license and features.
 Contact technical support personnel to obtain the corresponding License file.
 If you update the License, the new License file will overwrite the new one on the
server host. Back up the old one before updating. The license file path is
"/var/local/nms/comp/service/webapp/config/license/license. xml".

Raisecom Proprietary and Confidential 61

 After the license is successfully uploaded, the system will force the user to log out
within 1 minute, and then the user can log in again to use the system based on
the updated license.
Step 1 From the top navigation bar, choose System > System Mgmt > License. Click Import
License, as shown below.
Step 2 Click Upload License. A dialog box appears. Choose a local file, and click Open. The
RCView automatically verifies the License file.
Step 3 After the RCView successfully verifies the License file, click Login to log in based on the
new license file.

Table 4-1 Parameters of the License

Parameter Value Description
Server – Show information about the server for
Characteristic authorizing with licenses.
Information
 Valid
License Status Show the license status.
 Invalid
License Valid – Show the valid period of the license.
Period

4.2.6 How to show log files in the RCView system

Step 1 Log in to the RCView system on a Web browser.
Step 2 Type "https://IP address of the RCView system/nms/logfiles/", as shown below.
Step 3 Click a link to download the log file.

Raisecom Proprietary and Confidential 62

4.3 FAQs for the Nmstools tool

4.3.1 The Nmstools is a tool software equipped with the RCView
system, and it is used for maintaining and debugging the RCView
system.Modifying the host name of the RCView server
When multiple servers are used in the HA deployment mode and other modes, configure their
host names to different values to prevent the RCView system from failing to work or be
installed.
Step 1 Use the hostnamectl set-hostname xxx command to modify the host name of the RCView
server. To ensure unique host names, we recommend modifying the host name in the format
of host + IP address. The host name cannot contain periods. For example, the IP address of
the RCView server is 192.168.18.158, so you can configure the host name to
host19216818158. The host name cannot contain the period (.).
Step 2 Use the hostname command to check whether the new host name has taken effect.
Step 3 If the RCView system is installed, use the nmstools hostname command to enter the network
management tool CLI, and update the new host name.

[root@host172161240 ~]# nmstools hostname

Press Enter to skip modification.
server IP172.16.1.240
server Hostname:aaa

server :172.16.1.240
add :aaa
input preview(Y/n):

Step 4 Use the reboot now command to restart the RCView server.

Raisecom Proprietary and Confidential 63

4.3.2 How to modify the IP address, user name, and password of

the RCView system
After the IP address, user name, or password of the operating system is modified, use the
nmstools command to modify these parameters of the RCView system so that RCView
system can work properly.

Preparing for configurations

Step 1 Ensure that the IP address, user name, or password is modified.
Step 2 If the user is a non-root user, ensure that it has the sudo right.

Modifying the internal IP address of the RCView system

Step 1 Use the nmstools ip command to the internal IP address of the RCView system.

[root@host172161240 ~]# nmstools ip

Press Enter to skip modification.
Old Server IP:172.16.1.240
New Server IP:127.0.0.2

Step 2 Use the reboot now command to restart the server.

Modifying the SSH user name and password of the RCView system
Step 1 Use the nmstools user command to modify the SSH user name and password of the RCView
system.

[root@host172161240 ~]# nmstools user

Press Enter to skip modification.
server IP172.16.1.240
New Server User Name:aaa
New Server Password:

Step 2 Use the reboot now command to restart the server.

4.3.3 Modifying IP address of the RCView system in small-scale

deployment mode

 This section is applicable to small-scale deployment only.

 After the IP address of the RCView system is modified, use the nmstools
command to modify parameters of the RCView system. For details, see section
4.3.2 How to modify the IP address, user name, and password of the RCView
system.

Raisecom Proprietary and Confidential 64

 The IP address of the RCView system (RCView IP address) is the IP address for a
browser to access the RCView system, for devices to report alarms, and for the
components in the RCView to access each other.
 After installing and running the RCView system, to modify its IP address due to
planning or debugging, you need to modify the IP address of the NIC of the RCView
server and execute the modification script.
– If you modify the SSH user name and password of the RCView server according to
network planning, you can execute the modification script by referring to this section
and modify these parameters.
– When you modify the IP address of the RCView system, you can modify it within the
same type; in other word, you can modify an IPv4 address to a new IPv4 address
only and an IPv6 address to a new IPv6 address only.

Prerequisites
 Execute operations as a root-level user or the general user with the sudo right.
 Before modifying the password, confirm that the password is already modified to avoid
modifying the password by mistake, and then execute the modification operation as the
general user with the sudo right.

Modification flow
Step 1 According to the network type, choose to modify the IPv4 or IPv6 address.
Step 2 Execute the modification script.

(Applicable to IPv4 network) modifying IPv4 address of the RCView server

Step 1 Enter the network configuration file directory.

[root@host17216125210 ~]# cd /etc/sysconfig/network-scripts

[root@host17216125210 network-scripts]#

Step 2 Show the name of the NIC. It is ifcfg-ens33 in this example.

[root@host17216125210 network-scripts]# ll
total 224
-rw-r--r--. 1 root root 365 Dec 30 01:24 ifcfg-ens33
-rw-r--r--. 1 root root 254 May 3 2017 ifcfg-lo
...

Step 3 Edit the network configuration file. Type "i" to enter the editing status. Edit the following text.
The major parameters are marked by "#".

[root@host17216125210 network-scripts]# vi ifcfg-ens33

TYPE=Ethernet
PROXY_METHOD=none

Raisecom Proprietary and Confidential 65

BROWSER_ONLY=no
#BOOTPROTO=dhcp
BOOTPROTO=static #enable the static IP address.
DEFROUTE=yes
IPV4_FAILURE_FATAL=no
IPV6INIT=yes
IPV6_AUTOCONF=yes
IPV6_DEFROUTE=yes
IPV6_FAILURE_FATAL=no
IPV6_ADDR_GEN_MODE=stable-privacy
NAME=ens33
UUID=8c38cda4-c8c7-4207-bb34-951e7148ed78
DEVICE=ens33
#ONBOOT=no
ONBOOT=yes #enable the function of automatically enabling network
connection.
IPADDR0=172.16.125.200 #new IP address
PREFIXO0=255.255.255.0 #new IP address mask
GATEWAY0=172.16.125.1 #new gateway IP address
DNS1=172.16.8.8 #new DNS address

Step 4 Press ESC to exit editing. Type ":wq!", and press Enter to save configurations.
Step 5 Restart the network to make configurations take effect.

[root@host17216125210 network-scripts]# service network restart

(Applicable to IPv4 network) modifying IPv6 address of the RCView server

Step 1 Enter the network configuration file directory.

[root@host200110100000205 ~]# cd /etc/sysconfig/network-scripts

[root@host200110100000205 network-scripts]#

Step 2 Show the name of the NIC. It is ifcfg-enp0s3f6 in this example.

[root@host200110100000205 network-scripts]# ll
total 224
-rw-r--r--. 1 root root 365 Dec 30 01:24 ifcfg-enp0s3f6
-rw-r--r--. 1 root root 254 May 3 2017 ifcfg-lo
...

Step 3 Edit the network configuration file. Type "i" to enter the editing status. Edit the following text.
The major parameters are marked by "#".

Raisecom Proprietary and Confidential 66

[root@host200110100000205 network-scripts]# vi ifcfg-enp0s3f6

HWADDR=50:7B:9D:72:32:4C
TYPE=Ethernet
PROXY_METHOD=none
BROWSER_ONLY=no
BOOTPROTO=none
IPADDR=172.16.125.210
PREFIX=24
GATEWAY0=172.16.125.1
DNS1=172.16.8.8
DEFROUTE=yes
IPV4_FAILURE_FATAL=no
NAME=enp0s3f6
UUID=8c38cda4-c8c7-4207-bb34-951e7148ed78
ONBOOT=yes #enable the function of automatically enabling network
connection.
IPV6INIT=yes
IPV6_AUTOCONF=yes
IPV6_DEFROUTE=yes
IPV6_FAILURE_FATAL=no
IPV6_ADDR_GEN_MODE=stable-privacy
IPV6_PRIVACY=no
IPV6ADDR=2001:101::200/64 # new IP address and prefix length
IPV6_DEFAULTGW=2001:101::1 # new gateway IP address
IPV6_PEERROUTES=no

Step 4 Press ESC to exit editing. Type ":wq!", and press Enter to save configurations.
Step 5 Restart the network to make configurations take effect. If the network address is modified,
restart the network, and reconnect the new IP address of the RCView server.

[root@host200110100000205 network-scripts]# service network restart

Executing modification script

Step 1 Enter the script directory.
[root@host17216125210 ~]# cd /usr/local/nms/comp/service/mysql/
[root@host17216125210 mysql]#

Step 2 Execute the modification script. Configure the parameters for modification, and confirm them.
Type "y", and press Enter to execute the modification.

 Example for modifying the IP address of the RCView server

Press Enter to skip modification.

Old Server IP:172.16.125.210

Raisecom Proprietary and Confidential 67

New Server IP:172.16.125.200

server :172.16.125.210
IP :before :172.16.125.210 after :172.16.125.200
input preview(Y/n):y

 Example for modifying the SSH user name and password of the RCView server.

Press Enter to skip modification.

Old Server IP:172.16.125.210

New Server User Name:root1

New Server Password:

server :172.16.125.210

user :before :root after :root1

input preview(Y/n):

Step 3 Wait until the script is executed. Type "y", and press Enter to restart the server and make
configurations take effect.

login success:172.16.125.211
login check finish
update database
login success:172.16.125.211
login success:172.16.125.211
finish
system need reboot, now reboot(Y/n):y

If the RCView server is not immediately restarted, use the reboot-now command to
manually restart the RCView server and make configurations take effect.

4.3.4 How to stop or start all components of the RCView system

If required for operation and maintenance, stop or start components of the RCView system as
below:
Step 1 Use the nmstools stopNMS command to stop components of the RCView system.
Step 2 Use the nmstools runNMS command to start components of the RCView system.

Raisecom Proprietary and Confidential 68

4.4 Terms
A
Alarm Information reported when the device or RCView detects a fault
The RCView does not receive those reported alarms that comply with
Alarm Filter
filtering rules.

C
Current The current alarm is defined according to the operation status of the
Alarm alarm. All uncleared or unfiltered alarms are called current alarms.
Customer Customer uses device provided service; the customer information can
associate with NE, alarm and can only be stored in the network
management system.

D
The data center provides backup, upgrade, version maintenance, and
Data Center
other functions for system software and configuration files of devices.
The management domain is a resource set that can be operated by the
Domain
user based on the minimum granularity of NEs.

I
Inventory Various resources in the RCView

L
License file of the RCView, which specifies system functions available
License
to the user

N
Network
A network device to be managed by the RCView as a network element
Element
Node A joint name for the subnet, NE, and symbol in an RCView
O
Operate right Right for operating and managing the RCView and its resources

P
Performance The RCView collects and displays performance data of the device, such
Monitor as traffic and packet loss rate.

Raisecom Proprietary and Confidential 69

R
Managed objects in the RCView, including devices, chassis, cards, and
Resource
interfaces.

S
Southbound The RCView communicates with the device through the southbound
Interface interface.
The subnet is the logical partition of the network topology in the NMS,
Subnet helping clearly show the topology structure of the network elements. The
subnet includes topology nodes, such as subnet, NE, symbol, and link.
The topology symbol is a schematic symbol. It cannot be managed but
Symbol
can better show the structure on the network as a visualized symbol.

T
It refers to a way of sending alarms to the RCView. Alarms are reported
Trap
to the system through SNMP packets.

U
RCView client user. The union set of the management domain and
User operation rights of the user and user group determines system functions
available to the user.

4.5 Acronyms and abbreviations

C
CPU Central Processing Unit

F
FTP File Transfer Protocol

G
GUI Graphical User Interface

I
IP Internet Protocol

Raisecom Proprietary and Confidential 70

M
MIB Management Information Base

S
SNMP Simple Network Management Protocol

T
TFTP Trivial File Transfer Protocol

U
UDP User Datagram Protocol

Raisecom Proprietary and Confidential 71

Copyright © Raisecom Technology Co., Ltd.
Address: Raisecom Building, No. 11, East Area, No. 10 Block, East Xibeiwang Road, Haidian
District, Beijing, P.R.China Postal code: 100094 Tel: +86-10-82883305
Fax: 8610-82883056 http: //www.raisecom.com Email: [email protected]

Raisecom ISCOM5508 Configuration Guide (Rel - 01) - 2
100% (1)
Raisecom ISCOM5508 Configuration Guide (Rel - 01) - 2
390 pages
ISCOM5508 Configuration Guide (Rel - 02)
No ratings yet
ISCOM5508 Configuration Guide (Rel - 02)
401 pages
Mini Tennis Coaching Manual
100% (5)
Mini Tennis Coaching Manual
110 pages
Ruggedcom Rs400 Manual de Usuario
No ratings yet
Ruggedcom Rs400 Manual de Usuario
275 pages
Naked Power-The Phallus As An Apotropaic Symbol in The Images and Texts of Roman Italy
100% (1)
Naked Power-The Phallus As An Apotropaic Symbol in The Images and Texts of Roman Italy
132 pages
Andrew Spencer, Robert Henley - Maths and English For Electrical - Functional Skills-Cengage Learning EMEA (2013)
100% (1)
Andrew Spencer, Robert Henley - Maths and English For Electrical - Functional Skills-Cengage Learning EMEA (2013)
97 pages
A Triumph of Surgery - Explanation +glossary
0% (1)
A Triumph of Surgery - Explanation +glossary
3 pages
ISCOM2924GF-4GE - 4C Configuration Guide (A - 01) PDF
No ratings yet
ISCOM2924GF-4GE - 4C Configuration Guide (A - 01) PDF
337 pages
ISCOM S2600 (A) Series Configuration Guide (CLI) (Rel - 02)
No ratings yet
ISCOM S2600 (A) Series Configuration Guide (CLI) (Rel - 02)
498 pages
Payslip For The Month of May 2023
No ratings yet
Payslip For The Month of May 2023
1 page
NView NNM (V5) Operation Guide (Rel - 48)
No ratings yet
NView NNM (V5) Operation Guide (Rel - 48)
438 pages
Instrument Technician Resume 24
No ratings yet
Instrument Technician Resume 24
5 pages
ISCOM2828F Configuration Guide 20090619 PDF
No ratings yet
ISCOM2828F Configuration Guide 20090619 PDF
413 pages
ISCOM2924GF-4GE - 4C Configuration Guide
No ratings yet
ISCOM2924GF-4GE - 4C Configuration Guide
337 pages
ISCOM2924GF-4GE - 4C Configuration Guide (A - 01) PDF
No ratings yet
ISCOM2924GF-4GE - 4C Configuration Guide (A - 01) PDF
337 pages
Review Data
No ratings yet
Review Data
745 pages
Iscom2900 Series Configuration Guide (Rel 10) PDF
No ratings yet
Iscom2900 Series Configuration Guide (Rel 10) PDF
526 pages
Bencao Gangmu 12
No ratings yet
Bencao Gangmu 12
4 pages
ISCOM2900 Series Configuration Guide (Rel - 03) PDF
No ratings yet
ISCOM2900 Series Configuration Guide (Rel - 03) PDF
527 pages
ISCOM2600 (B) Series Configuration Guide (CLI) (Rel - 03)
No ratings yet
ISCOM2600 (B) Series Configuration Guide (CLI) (Rel - 03)
734 pages
Iscom2828f Configuration Guide Rel - 01 PDF
No ratings yet
Iscom2828f Configuration Guide Rel - 01 PDF
383 pages
ISCOM S2600 (A) Series Configuration Guide (CLI) (Rel - 01)
No ratings yet
ISCOM S2600 (A) Series Configuration Guide (CLI) (Rel - 01)
456 pages
The Arson Betrayal Walkthrough
No ratings yet
The Arson Betrayal Walkthrough
18 pages
Raisecom ROS Switch Configuration Guide Version 4.0
100% (1)
Raisecom ROS Switch Configuration Guide Version 4.0
289 pages
(PPT) Environmental Impacts of Dam
100% (2)
(PPT) Environmental Impacts of Dam
17 pages
FSM 1989 Tracker 00 General Information
No ratings yet
FSM 1989 Tracker 00 General Information
24 pages
RCMS2903-4E1-4GE (A) Configuration Guide (Rel - 02)
100% (1)
RCMS2903-4E1-4GE (A) Configuration Guide (Rel - 02)
70 pages
Raisecom Nview NNM V5.0 User Manual
No ratings yet
Raisecom Nview NNM V5.0 User Manual
215 pages
ISCOM2600G (A) Series Configuration Guide (CLI) (Rel - 12)
No ratings yet
ISCOM2600G (A) Series Configuration Guide (CLI) (Rel - 12)
604 pages
OPCOM3105&3107 Configuration Guide 200711
100% (1)
OPCOM3105&3107 Configuration Guide 200711
41 pages
Ap Spanish Language - Syllabus Spanish 4
No ratings yet
Ap Spanish Language - Syllabus Spanish 4
9 pages
RC953 Gestm1
No ratings yet
RC953 Gestm1
197 pages
Manual Raisecom
No ratings yet
Manual Raisecom
369 pages
The Control Handbook Control System Fundamentals 2ed Edition Levine W.S. (Ed.) - The Ebook Is Now Available, Just One Click To Start Reading
No ratings yet
The Control Handbook Control System Fundamentals 2ed Edition Levine W.S. (Ed.) - The Ebook Is Now Available, Just One Click To Start Reading
83 pages
Bulking of Sand
No ratings yet
Bulking of Sand
10 pages
ISCOM21xx Configuration Guide (Rel - 04)
No ratings yet
ISCOM21xx Configuration Guide (Rel - 04)
396 pages
Updated List Convocation
No ratings yet
Updated List Convocation
216 pages
NView NNM (V5 - 40) Operation Guide 201208
No ratings yet
NView NNM (V5 - 40) Operation Guide 201208
358 pages
ISCOM21xx Configuration Guide (Rel - 02)
No ratings yet
ISCOM21xx Configuration Guide (Rel - 02)
397 pages
ISCOM2924GF-4C (R) Configuration Guide (CLI) (Rel - 01)
No ratings yet
ISCOM2924GF-4C (R) Configuration Guide (CLI) (Rel - 01)
322 pages
Rockwell Software RSLinx Enterprise en 0811
No ratings yet
Rockwell Software RSLinx Enterprise en 0811
52 pages
NView NNM (V5) Upgrade Guide (Rel - 47)
No ratings yet
NView NNM (V5) Upgrade Guide (Rel - 47)
61 pages
RC 3000
No ratings yet
RC 3000
105 pages
09-Ingl - Mouse Manta Apego Plana-Sascha
No ratings yet
09-Ingl - Mouse Manta Apego Plana-Sascha
3 pages
RC002-SNMP Agent Commands Notebook 201002
No ratings yet
RC002-SNMP Agent Commands Notebook 201002
68 pages
RSView SEInstall
No ratings yet
RSView SEInstall
56 pages
Getting Results With Rslinx Classic
No ratings yet
Getting Results With Rslinx Classic
60 pages
Rcms2903-4e1-4ge (Rev A) User Manual 201111
No ratings yet
Rcms2903-4e1-4ge (Rev A) User Manual 201111
21 pages
RC002 Config Tool User Manual
No ratings yet
RC002 Config Tool User Manual
25 pages
Regions Bank Statement
No ratings yet
Regions Bank Statement
2 pages
ISCOM3000G (B) Series Product Description (Rel - 05)
No ratings yet
ISCOM3000G (B) Series Product Description (Rel - 05)
99 pages
rc551 Ge User - Manual PDF
No ratings yet
rc551 Ge User - Manual PDF
18 pages
RCMS2801-240FE (-BL) (REV.A) User Manual 200706
No ratings yet
RCMS2801-240FE (-BL) (REV.A) User Manual 200706
46 pages
UGBS 105 Lecture 1 - 4 Updated
No ratings yet
UGBS 105 Lecture 1 - 4 Updated
28 pages
ISCOM5508-GP (A) Installation Guide (Rel - 02)
No ratings yet
ISCOM5508-GP (A) Installation Guide (Rel - 02)
60 pages
Rc3000e28rev.a29 User Manual 201005 PDF
No ratings yet
Rc3000e28rev.a29 User Manual 201005 PDF
37 pages
02 - Commands Line Configuration Guide
No ratings yet
02 - Commands Line Configuration Guide
10 pages
ISCOM2924GF-4GE - 4C Hardware Description (A - 01)
No ratings yet
ISCOM2924GF-4GE - 4C Hardware Description (A - 01)
37 pages
RC002-SNMP Agent Configuration Guide 200906
No ratings yet
RC002-SNMP Agent Configuration Guide 200906
22 pages
RSL in X Classic GRG
No ratings yet
RSL in X Classic GRG
58 pages
Nview NNM v5.0 Installation and Deployment Manual
No ratings yet
Nview NNM v5.0 Installation and Deployment Manual
40 pages
Linx Enterprise: Getting Results Guide
No ratings yet
Linx Enterprise: Getting Results Guide
56 pages
Manual Raisecom Rc552fe
No ratings yet
Manual Raisecom Rc552fe
25 pages
Rcms 2811
No ratings yet
Rcms 2811
29 pages
ISCOM Series Switch Test Guide
No ratings yet
ISCOM Series Switch Test Guide
36 pages
ISCOM2109F Hardware Installation User Manual 20060228
No ratings yet
ISCOM2109F Hardware Installation User Manual 20060228
18 pages
Rcms2901-120fe (Rev.a) User Manual 201110
No ratings yet
Rcms2901-120fe (Rev.a) User Manual 201110
27 pages
PHYS 121 - Curriculum - Huy
No ratings yet
PHYS 121 - Curriculum - Huy
4 pages
RC552-FE (A) User Manual 20060824
No ratings yet
RC552-FE (A) User Manual 20060824
25 pages
OSI Security Architecture
No ratings yet
OSI Security Architecture
5 pages
ISCOM2824G (REV.A) User Manual 200904
No ratings yet
ISCOM2824G (REV.A) User Manual 200904
17 pages
ISCOM2016 Hardware Installation User Manual 200608
No ratings yet
ISCOM2016 Hardware Installation User Manual 200608
17 pages
Opcom200-2gem (Rev.a) User Manual
No ratings yet
Opcom200-2gem (Rev.a) User Manual
20 pages
45 Colonialism As A Profession Mudassar Khan
No ratings yet
45 Colonialism As A Profession Mudassar Khan
11 pages
Dragonborn Warlock 3rd Level
No ratings yet
Dragonborn Warlock 3rd Level
3 pages
5 Ways To Improve User Experience
No ratings yet
5 Ways To Improve User Experience
10 pages
CV Donny Prasetyo Utomo
No ratings yet
CV Donny Prasetyo Utomo
5 pages
Science 7th Paper
No ratings yet
Science 7th Paper
2 pages
10 Communication Skills For Your Life and Career Success
No ratings yet
10 Communication Skills For Your Life and Career Success
1 page
35 City of Manila Vs Chinese Community
No ratings yet
35 City of Manila Vs Chinese Community
2 pages
Eee Lab-3
No ratings yet
Eee Lab-3
4 pages
English Test Grade 10 (L2)
No ratings yet
English Test Grade 10 (L2)
2 pages
MUSTAFA TAREK. Public Accountant
No ratings yet
MUSTAFA TAREK. Public Accountant
2 pages
Computer Programming In C Language
From Everand
Computer Programming In C Language
Jitendra Patel
4/5 (15)
CompTIA Security+ SY0-601 Exam Practice Tests
From Everand
CompTIA Security+ SY0-601 Exam Practice Tests
CertSquad Professional Trainers
No ratings yet
CNC Router Essentials: The Basics for Mastering the Most Innovative Tool in Your Workshop
From Everand
CNC Router Essentials: The Basics for Mastering the Most Innovative Tool in Your Workshop
Randy Johnson
5/5 (3)
Solving the Riddle of Microsoft and Your Computer: 2Nd Edition
From Everand
Solving the Riddle of Microsoft and Your Computer: 2Nd Edition
Mark Riddle
No ratings yet
Advanced Multiplayer Game Development with Ureal Engine 5: A Comprehensive Guide to C++ Scripting
From Everand
Advanced Multiplayer Game Development with Ureal Engine 5: A Comprehensive Guide to C++ Scripting
Vladimir Kiselev
No ratings yet
Autodesk Inventor 2014 Tutorial Book
From Everand
Autodesk Inventor 2014 Tutorial Book
John G Ronald
No ratings yet
Software Quality for Managers: 8 Essential Software Quality KPIs Every Manager Should Know!
From Everand
Software Quality for Managers: 8 Essential Software Quality KPIs Every Manager Should Know!
Repo Security
No ratings yet

RCView (V2.3) Installation Guide (Rel - 04)

Uploaded by

RCView (V2.3) Installation Guide (Rel - 04)

Uploaded by

www.raisecom.

is the trademark of Raisecom Technology Co., Ltd.

Indicate a potentially hazardous situation that, if not avoided,

Raisecom Proprietary and Confidential i

Raisecom Proprietary and Confidential ii

Raisecom Proprietary and Confidential iii

1 Preparing for installation ............................................................................................................ 1

2 Installation and deployment ..................................................................................................... 20

Raisecom Proprietary and Confidential i

4.1.4 How to disable SELinux ....................................................................................................................... 48

Raisecom Proprietary and Confidential ii

1 Preparing for installation

1.1.1 Installation features

Raisecom Proprietary and Confidential 1

1.1.2 Deployment mode

Table 1-1 Comparison of deployment modes

Raisecom Proprietary and Confidential 2

Deployme Numbe Number of IP Number of VIP Total

addresses are required VIP address is

Raisecom Proprietary and Confidential 3

Deployme Numbe Number of IP Number of VIP Total

The system deployment modes support the following features:

Raisecom Proprietary and Confidential 4

− Southbound IP address and northbound IP address: configured according to network

Raisecom Proprietary and Confidential 5

Figure 1-1 Example for small-scale deployment

Web client Web client

Figure 1-2 Example for medium-scale deployment

Web client Web client

Raisecom Proprietary and Confidential 6

Figure 1-3 Example for small-scale HA deployment

Web client Web client

Figure 1-4 Example for medium-scale HA deployment

Web client Network Web client

Raisecom Proprietary and Confidential 7

Web client deployment

1.1.3 Installation process

Raisecom Proprietary and Confidential 8

Figure 1-5 Local installation through commands

System server IP address

Raisecom Proprietary and Confidential 9

Figure 1-6 Remote installation through commands

System server IP address

1.1.4 Installation files

Table 1-2 Installation files

System License file File name.xml license.xml

Raisecom Proprietary and Confidential 10

1.2 Running environment

Table 1-3 Recommended server configurations for 100000 equivalent NEs

channel Number of 500000

software of 50000 devices in

Raisecom Proprietary and Confidential 11

Server role Service Indicator Description

medium-scale on 600,000 interfaces every

Table 1-4 Recommended server configurations for 100000 equivalent NEs

channel Number of 500000

Raisecom Proprietary and Confidential 12

Server role Service Indicator Description

software of 50000 devices in

medium-scale on 600,000 interfaces every

Raisecom Proprietary and Confidential 13

1.2.2 Software environment

Supported operating system

Table 1-6 Supported operating system

Raisecom Proprietary and Confidential 14

Permission requirements of operating system users

Table 1-7 Permission requirements of operating system users

Classification Permission requirement

Requirements on space of directory

Table 1-8 Description of adjusting the partition size

Raisecom Proprietary and Confidential 15

Partition File system Mount point Partition size Description

Related software requirements

Table 1-9 Software requirements

1.2.3 Browser requirement

Table 1-10 Browser requirements