No relevant resource is found in the selected language.

This site uses cookies. By continuing to browse the site you are agreeing to our use of cookies. Read our privacy policy>Search

Reminder

To have a better experience, please upgrade your IE browser.

upgrade

eSight V300R009C00 Single-Node System Software Installation Guide (SUSE Linux) 09

Rate and give feedback :
Huawei uses machine translation combined with human proofreading to translate this document to different languages in order to help you better understand the content of this document. Note: Even the most advanced machine translation cannot match the quality of professional translators. Huawei shall not bear any responsibility for translation accuracy and it is recommended that you refer to the English document (a link for which has been provided).
eSight Server Installation Plan

eSight Server Installation Plan

This topic describes how to plan installation information, such as the IP address, host name, and password, to help correctly install eSight.

Host Name Planning

Table 5-2 Host name list

Item

Example

Description

eSight server host name

eSightServer

To ensure that eSight can run properly, host name planning must comply with the following rules and restrictions:

  • Be unique on the live network.
  • Contain letters (A to Z, or a to z), digits (0 to 9), or hyphens (-) and start with a letter.
  • Be case-sensitive.
  • Contain at least two characters.
  • Contain no more than 24 characters.

Network Port Planning

Table 5-3 Network port list

Item

Example

Description

2288H V5 server

  • Network port 1: eSight server's service network port used to connect managed devices and the web client.
  • Network port 2/3/4 and extended network port: standby service network ports, for example, used to separate the southbound and northbound services.
  • Mgmt: Huawei server's iMana/iBMC maintenance network port
NOTE:
  • The network port numbers shown in this figure may be different from those displayed in the operating system. After the server is powered on, disconnect network cables and check the virtual network ports whose network connections are lost to determine the mapping between physical network ports on the server and network ports displayed in the operating system.
  • The eSight management server requires two service network ports: one used for basic management and stateless computing and the other used for configuration.
  • If eSight needs to manage devices in several subnets, multiple service network ports are required to connect eSight to these subnets. After the eSight installation is complete, (Optional) Configuring Multi-Subnet Management.

RH5885H V3 server

NOTE:

If eSight is to be installed on a virtual machine, you do not need to plan the network port.

IP Address Planning

The IP address type can be IPv4 or IPv6 or dual-stack. The IPv4 address is used as an example.

Table 5-4 IP address list

Item

Example

Description

System IP address

Network port 1

  • IP address: 192.168.1.100
  • Subnet mask: 255.255.255.0
  • Default gateway: 192.168.1.1
  • The static IP address must be used.
  • The IP address must be unique on the live network.
  • You can plan only one IP address for one network port. It is not allowed to plan or set multiple IP addresses for the same network port.
  • When eSight is to be installed on a virtual machine, you just need to plan the system IP address. Only one IP address is supported.
  • If the eSight server has multiple IP addresses in several network segments, use the IP address that resides in the same network segment as the managed device's IP address or (Optional) Configuring Multi-Subnet Management. If neither of the two conditions is met, eSight cannot manage devices with IP addresses in different network segments from its own.
  • The eSight server can communicate with managed devices.
  • The eSight server can communicate with Web clients.
  • The iMana/iBMC IP address and system IP address can be located either on the same network segment or on different network segments.
  • If extended network ports are used to separate the southbound and northbound services, the IP address for separating the southbound and northbound services must be in a network segment different from the IP address planned for network port 1.

Network port 2/3/4 and extended network port

Use extended ports(Network port 2) to separate the southbound and northbound services:

  • IP address: 192.168.2.100
  • Subnet mask: 2255.255.240.0
  • Default gateway: 192.168.2.1

iMana/iBMC IP address

  • IP address: 10.137.62.20
  • Subnet mask: 255.255.255.0
  • Default gateway: 10.137.62.1

Installation Path Planning

Table 5-5 Installation path list

Item

Example

Description

eSight installation path

/opt/eSight

  • The eSight software cannot be installed in the root directory.
  • The eSight installation directory and its absolute path must contain only letters, digits, hyphens (-), and underscores (_) and must begin with a letter or underscore (_). The absolute path contains a maximum of 50 characters.

Oracle database installation path

/opt/oracle

Data files must not be stored in the eSight installation path.

Oracle data file storage path

/opt/eSightData

  • The size of data files increases during eSight operation, so it is recommended that data files be not saved to the system partition.
  • Data files must not be stored in the eSight installation path.

User Name and Password Planning

You must remember eSight user passwords. If you forget them, you may have to reinstall eSight.

Table 5-6 User and password list

Item

Default Password

Description

SUSE Linux administrator user root

The password is configured during SUSE Linux installation.

root is a default Linux OS user. It has the highest operation rights of the OS. The root user can control all OS resources, create users, assign rights to the users, and use all the functions provided by the OS. In addition, the root user can install or uninstall the eSight server application.

SUSE Linux network management user ossuser

Changeme_123

The ossuser account, automatically created by eSight, performs routine operation and maintenance (O&M) for the eSight server. The ossuser user can remotely log in to the server through SSH and upload or download files through SFTP. In the distributed deployment scenario, the ossuser user is an administrator account used to monitor and maintain distributed servers. It can be also used to back up and restore data on the slave node through the maintenance tool.

SUSE Linux user oracle

Changeme123

The oracle user is used to maintain the Oracle database, for example, installing the Oracle database, creating database instances, and starting or stopping the database. The oracle user can remotely log in to the server through SSH and upload or download files through SFTP.

Oracle database administrator user system

The password is configured during Oracle installation.

The system user is a default user provided by the Oracle. It is the system administrator of the Oracle. The system user can control all database resources, create other users, assign rights to other users, and perform all operations provided by the Oracle. During the eSight installation, the system user is used to create NMS database and NMS database users.

Oracle database administrator user sys

The password is configured during Oracle installation.

The sys user is a default user provided by the Oracle. It is the system administrator of the Oracle and has all rights of the database.

Oracle database network management user commonuser

Changeme_123

The commonuser user is a database user of the NMS.

MySQL database administrator user dbadmin

The password is configured during eSight installation.

The dbadmin user is a default user provided by the MySQL. It is the system administrator of the MySQL and has all rights of the database. The dbadmin user can control all database resources, create other users, assign rights to other users, and perform all operations provided by the MySQL. During the eSight installation, the dbadmin user is used to create NMS database and NMS database users.

MySQL database network management user commonuser

Changeme_123

The commonuser user is a database user of the NMS.

Application Manager MySQL database network management user commonuser

Changeme_123

The commonuser user is a database user of the Application Manager. The password of the commonuser user is the same as that for the eSight Platform database commonuser user.

Infrastructure Manager MySQL database network management user sysuser

Changeme_123

The sysuser user is a default user provided by the MySQL of Infrastructure Manager. It is the system administrator of the MySQL and has all rights of the database.

eSight administrator user admin

Changeme123

The admin user is the administrator provided by eSight. The admin user has the management rights of all devices and operation rights of all eSight clients.

Maintenance tool user sys

Changeme123

The sys user is the unique user of the maintenance tool. The sys user can manage the eSight server and perform all operations on the maintenance tool.

eSight infrastructure management maintenance tool user admin

Changeme_123

The admin user is the unique user of the eSight infrastructure management maintenance tool. The sys user can manage the eSight Infrastructure Manager and perform all operations on the eSight infrastructure management maintenance tool.

NOTE:

Each user must have a unique password.

The password setting must comply with the following rules:

  • The password cannot contain the user name in normal or reverse order.
  • The password ranges from 8 to 32 characters.
  • No character can exceed 3 occurrences in the password.
  • The password must contain at least one uppercase letter (A to Z), lowercase letter (a to z) and digit (0 to 9).
  • The password of Oracle database administrator user system and sys can contain only the following characters: uppercase letters, lowercase letters, digits, and ~ # ^ ( ) - _ + . ?

Database Planning

Table 5-7 Database parameter list

Item

Example

Description

Oracle database listener name

ESIGHTLISTENER

-

Oracle database listening port

31521

-

Oracle database instance

esight

-

Oracle database service name

esight

-

Oracle database maximum connections

500

eSight requires the maximum number of Oracle database connections to be greater than or equal to 500.

Database Character Set

AL32UTF8

-

Time Zone and Time Planning

Table 5-8 Time zone and time list

Item

Example

Description

Time zone

UTC+08:00

-

Time

14:00

-

Port Planning

Refer to the eSight Communication Matrix to know the port numbers used by eSight.

If unrelated software is installed on the eSight server, port conflicts may occur, preventing the normal eSight operation.

On SUSE Linux, eSight automatically creates mappings for ports shown in Table 5-9 during installation, which increases system compatibility. Before eSight installation, ensure that these ports are not mapped.

Table 5-9 Port mappings

Source Port

Mapped Port

Port Function

21

31921

FTP port

69

32182

TFTP port

162

10162

Alarm port

514

32185

syslog port

NOTE:

You can run the following command to check the port mappings:

# iptables -t nat -L

If ports 31921, 32182, 10162, and 32185 are contained in the following information, the ports are mapped. Otherwise, the ports are not mapped.

Chain PREROUTING (policy ACCEPT)
target     prot opt source               destination
REDIRECT   tcp  --  anywhere             anywhere            tcp dpt:ftp redir ports 31921
REDIRECT   udp  --  anywhere             anywhere            udp dpt:tftp redir ports 32182
REDIRECT   udp  --  anywhere             anywhere            udp dpt:snmptrap redir ports 10162
REDIRECT   udp  --  anywhere             anywhere            udp dpt:shell redir ports 32185
DNAT       udp  --  anywhere             anywhere            udp dpt:bootps ADDRTYPE match dst-type BROADCAST to:255.255.255.255:44367

RAID Planning for Servers

  • If the server is not the default one delivered for eSight, select a proper RAID type based on the number of hard disks configured on the server and Table 5-10. For details about how to plan and configure the RAID, see the server guide.
    Table 5-10 RAID configuration rules

    Disk Quantity

    Configure

    2

    RAID 1

    3~7

    RAID 5

    8

    RAID 5 + HotSpare

  • The following describes the RAID planning for standard RH5885H V3 servers and 2288H V5 servers:

    Two disks are configured for standard Huawei 2288H V5 servers.

    Eight disks are configured for standard Huawei RH5885H V3 servers.

    Table 5-11 RAID planning for standard eSight servers

    Server Type

    Disk

    RAID

    2288H V5

    0 and 1

    RAID 1

    RH5885H V3

    0~6

    RAID 5

    7

    HotSpare

Disk Planning for Server

Table 5-12 Server disk partition list

Partition Type

Partition Name

File System

Size (GB)

Description

Primary partition

/

Ext3

50

Root directory for installing the operating system.

Primary partition

swap

Swap

32

Swap partition.

Primary partition

/boot/efi

FAT

1 GB

Boot partition.

Logical partition

/tmp

Ext3

10 GB

Partition for storing temporary files.

Logical partition

/home

Ext3

1 GB

Home directory of the operating system user.

Logical partition

/var

Ext3

20 GB

Partition for storing the dynamic data of the daemon process and other system service processes.

Logical partition

/var/log

Ext3

10 GB

Partition for storing system logs.

Logical partition

/var/log/audit

Ext3

10 GB

Partition for storing auditd logs.

Logical partition

/opt

Ext3

Remaining disk space

Partition for installing the Oracle database and eSight.

Download
Updated: 2019-05-17

Document ID: EDOC1100011860

Views: 92372

Downloads: 138

Average rating:
This Document Applies to these Products
Related Documents
Related Version
Share
Previous Next