No relevant resource is found in the selected language.
MENU
Support Documentation
eSight V300R010C00SPC600 Planning Guide 13
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).
Remote High Availability System (EulerOS + GaussDB + OMMHA + VM)

Remote High Availability System (EulerOS + GaussDB + OMMHA + VM)

This section describes how to plan installation parameters for the remote HA system (EulerOS + GaussDB + OMMHA).

Operating System Host Name Planning

Table 8-92 describes the planning of the operating system host names.

Table 8-92 Operating system host name plan

Server

Item

Example

Description

Active eSight server

Host name of an operating system

Primaster

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

  • The host name of the eSight server must be unique on the network.
  • The host name must be a string of no more than 24 characters, including only letters (A to Z, a to z), digits (0 to 9), and hyphens (-).
  • The host name must begin with a letter and do not end with a hyphen (-).
  • The host name cannot contain consecutive hyphens (--).
  • The host name is case sensitive.
  • The host name cannot contain any space character.
  • The host name must contain at least two characters.

Standby eSight server

Host name of an operating system

Secmaster

Network and IP Address Planning

eSight supports the scenario where southbound services are isolated from northbound services and the scenario where southbound services are not isolated from northbound services. The network port and IP address planning is different for the two scenarios. It is recommended that the scenario where southbound services are isolated from northbound services be used.

  • The static IP address must be used.
  • The IP address must be unique on the live network.
  • The server can communicate with clients.
  • You can plan and configure only one IP address for one network port.
  • In different deployment scenarios, the IP addresses belong to different networks. You need to plan the network plane to which the IP addresses belong based on the network planning table and ensure that the network planes exist.
  • The IP address type can be IPv4 or IPv6, but not dual-stack.
    In the scenario where southbound services are isolated from northbound services, an NIC and IP address planning example is as follows.
    • The system IP address, heartbeat and replication IP address, and southbound IP address must belong to different network planes.
    • The active and standby servers can communicate with each other but do not need to be deployed in the same network segment.
Table 8-93 Network port and IP address planning when southbound services are isolated from northbound services

Item

Function

Server

NIC

Network Plane

Example (IPv4)

System IP address

IP address of the operating system. You can use it to log in to the server to manage and maintain the operating system.

Active server

eth0

The system IP addresses of the active and standby servers can communicate with each other.
  • 10.10.10.1/255.255.255.0/10.10.10.254
  • Network port: eth0

Standby server

eth0
  • 10.10.10.2/255.255.255.0/10.10.10.254
  • Network port: eth0

Heartbeat and replication IP address

Used to detect status of the network connection and replicate data between the active and standby eSight servers.

NOTE:

In the full image installation scenario where eSight is installed using the FusionSphere OpenStack OM, the heartbeat and replication IP address is automatically allocated and does not need to be planned by users.

Active server

eth1

The network to which the heartbeat and replication IP address belongs is independent of the network plane of the service network and O&M network. In addition, the heartbeat and replication network cannot communicate with the network where devices are located. The heartbeat and replication IP addresses of the active and standby servers can communicate with each other.
  • 192.168.100.10/255.255.255.0/192.168.100.254
  • Network port: eth1

Standby server

eth1
  • 192.168.100.20/255.255.255.0/192.168.100.254
  • Network port: eth1

Southbound IP address

Used for communications between the eSight server and devices.

Active server

eth2
  • The southbound IP addresses of the active and standby servers can communicate with each other.
  • The network plane where the southbound IP address is located must communicate with the network plane where the devices are located.
  • 10.10.11.1/255.255.255.0/10.10.11.254
  • Network port: eth2

Standby server

eth2
  • 10.10.11.2/255.255.255.0/10.10.11.254
  • Network port: eth2
In the scenario where southbound services are not isolated from northbound services, an NIC and IP address planning example is as follows.
  • The system IP address and heartbeat and replication IP address must belong to different network planes.
  • The active and standby servers can communicate with each other but do not need to be deployed in the same network segment.
Table 8-94 Network port and IP address planning when southbound services are not isolated from northbound services

Item

Function

Server

NIC

Network Plane

Example (IPv4)

System IP address

IP address of the operating system. You can use it to log in to the server to manage and maintain the operating system. Used for communications between the eSight server and devices.

Active server

eth0

The system IP addresses of the active and standby servers can communicate with each other.
  • 10.10.10.1/255.255.255.0/10.10.10.254
  • Network port: eth0

Standby server

eth0
  • 10.10.10.2/255.255.255.0/10.10.10.254
  • Network port: eth0

Heartbeat and replication IP address

Used to detect status of the network connection and replicate data between the active and standby eSight servers.

NOTE:

In the full image installation scenario where eSight is installed using the FusionSphere OpenStack OM, the heartbeat and replication IP address is automatically allocated and does not need to be planned by users.

Active server

eth1

The network to which the heartbeat and replication IP address belongs is independent of the network plane of the service network and O&M network. In addition, the heartbeat and replication network cannot communicate with the network where devices are located. The heartbeat and replication IP addresses of the active and standby servers can communicate with each other.
  • 192.168.100.10/255.255.255.0/192.168.100.254
  • Network port: eth1

Standby server

eth1
  • 192.168.100.20/255.255.255.0/192.168.100.254
  • Network port: eth1

Installation Path Planning

Table 8-95 Installation path plan

Item

Example

Description

eSight

/opt/eSight
  • The eSight software cannot be installed in the root directory.
  • To ensure successful eSight installation, ensure that the eSight installation path is empty before the installation.
  • 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.

User Name and Password Planning

To ensure user password security, use user passwords that meet password complexity requirements and change passwords periodically. This can prevent the user password from being stolen and prevent the HA system from being accessed without authorization. The passwords planned in this document are only examples.

Table 8-96 User and password list

User

Default Password

Description

EulerOS user root

Changeme_123

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.
  • The same character can be used at most three times.
  • The password must contain at least one uppercase letter (A to Z), one lowercase letter (a to z), and one digit (0 to 9).

EulerOS user ossuser

Changeme_123

GaussDB database administrator user sys

Changeme123

eSight database user commonuser of the GaussDB

Changeme_123

eSight login user admin

NOTE:

The user login address is https://IP address:31943.

Changeme123

NOTE:

You need to change the password upon first login.

Maintenance tool user sys

NOTE:

The login address of the management plane is https://IP address:31945.

Changeme123

NOTE:

You need to change the password upon first login.

Time Zone and Time Planning

Table 8-97 Time zone and time list

Item

Example

Description

Time zone

UTC+08:00

The times and time zones of the active and standby servers must be the same.

Time

14:00

Port Planning

  • For details about eSight server port planning, see eSight Communication Matrix.
    • If unrelated software is installed on the eSight server, port conflicts may occur and eSight may be unavailable.
    • Strictly follow instructions in eSight Communication Matrix to ensure that the operating system is secure and stable and eSight can be used properly.
    • After eSight is upgraded or a patch is installed, perform operations on ports by referring to eSight Communication Matrix.
  • In the EulerOS, eSight automatically creates mappings for ports listed in Table 8-98 during installation, which improves system compatibility.
    Table 8-98 Port mappings

    Source Port

    Mapped Port

    Port Function

    21

    31921

    FTP port

    69

    32182

    TFTP port

    162

    10162

    Alarm port

    514

    32185

    Syslog port

Disk Partition Planning

In manual installation scenarios, the default startup mode is UEFI.

Table 8-99 Disk partition plan

Partition

Capacity

File System

Description

/

50 GB

Ext4

Root directory for installing the operating system.

swap

16 GB

Swap

Swap partition.

/boot/efi

1 GB

FAT

Boot partition.

/tmp

10 GB

Ext4

Directory for storing temporary files.

/var/tmp

5 GB

Ext4

Directory for storing temporary files.

/home

1 GB

Ext4

Home directory of the operating system user.

/var

20 GB

Ext4

Directory for storing dynamic data about the daemon process and other system service processes.

/var/log

10 GB

Ext4

Directory for storing system log data.

/var/log/audit

10 GB

Ext4

Directory for storing audit log data.

/opt

Total remaining space

Ext4

Directory for installing eSight.

In mirror installation scenarios, the default startup mode is BIOS.

Table 8-100 Disk partition plan

Partition

Capacity

File System

Description

biosboot

2 MB

biosboot

Boot directory.

/

50 GB

Ext4

Root directory for installing the operating system.

swap

16 GB

Swap

Swap directory.

/tmp

10 GB

Ext4

Directory for storing temporary files.

/var/tmp

5 GB

Ext4

Directory for storing temporary files.

/home

1 GB

Ext4

Home directory of the operating system user.

/var

20 GB

Ext4

Directory for storing dynamic data about the daemon process and other system service processes.

/var/log

10 GB

Ext4

Directory for storing system log data.

/var/log/audit

10 GB

Ext4

Directory for storing audit log data.

/opt

Total remaining space

NOTE:

The hard disk space of the VM created by eSight using the image is fixed to 500 GB. The space of the "/opt" directory is about 378 GB.

Ext4

Directory for installing eSight.
Translation
简体中文
Download
Updated: 2021-01-18

Document ID: EDOC1100107088

Views: 5694

Downloads: 203

Average rating:
This Document Applies to these Products

Related Version

Related Documents

Digital Signature File

Digital Signature Authentication Mode
Share
Previous Next
Enterprise APP

Copyright © 2021 Huawei Technologies Co., Ltd. All rights reserved.

You are going to visit :