Local High Availability System (SUSE Linux+GaussDB+OMMHA+Physical Machine)
This section describes how to plan installation parameters for the local HA system (SUSE Linux+GaussDB+OMMHA).
Operating System Host Name Planning
Table 8-101 describes the planning of the operating system host names.
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:
|
Standby eSight server |
Host name of an operating system |
Secmaster |
Network Port 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, a network port 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.
Item |
Example |
NIC |
Description |
---|---|---|---|
2288H V5 server |
Network port 1: eth0 Network port 2: eth1 Network port 3: eth2 Network port 4: eth3 |
NOTE:
The network port numbers shown in this figure may be different from those displayed on the operating system. After the server is powered on, you are advised to disconnect and connect network cables to check the mapping between physical network ports on the server and network ports displayed in the operating system. |
|
2288X V5 server |
Network port 1: eth7 Network port 2: eth6 Network port 3: eth5 Network port 4: eth4 NOTE:
The 2288X V5 server has two onboard network ports and two unavailable network ports. Therefore, the NIC names start from eth4. |
Item |
Function |
Server |
Network Port |
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 |
Network port 1 (eth0; eth 7 for 2288X servers) |
The system IP addresses of the active and standby servers and system floating IP address belong to the same network plane. |
|
Standby server |
Network port 1 (eth0; eth 7 for 2288X servers) |
|
|||
System floating IP address |
Used by eSight to provide services. The IP address is used for communications between the eSight server and web client. NOTE:
Do not use the floating IP address to access the server. |
Active and standby servers |
Network port 1 (eth0; eth 7 for 2288X servers) |
|
|
Heartbeat and replication IP address |
Used to detect the status of the network connection and replicate data between the active and standby eSight servers. |
Active server |
Network port 2 (eth1; eth 6 for 2288X servers) |
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 belong to the same network plane. |
|
Standby server |
Network port 2 (eth1; eth 6 for 2288X servers) |
|
|||
Southbound IP address |
Used for communications between the eSight server and devices. |
Active server |
Network port 3 (eth2; eth 5 for 2288X servers) |
|
|
Standby server |
Network port 3 (eth2; eth 5 for 2288X servers) |
|
|||
Southbound floating IP address |
Used for communications between the eSight server and devices. |
Active and standby servers |
Network port 3 (eth2; eth 5 for 2288X servers) |
|
The system IP address and heartbeat and replication IP address must belong to different network planes.
Item |
Function |
Server |
Network Port |
Network Plane |
Example |
---|---|---|---|---|---|
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 |
Network port 1 (eth0; eth 7 for 2288X servers) |
The system IP addresses of the active and standby servers and system floating IP address belong to the same network plane. |
|
Standby server |
Network port 1 (eth0; eth 7 for 2288X servers) |
|
|||
System floating IP address |
Used for communications between the eSight server and client as well as between the eSight server and devices. |
Active and standby servers |
Network port 1 (eth0; eth 7 for 2288X servers) |
|
|
Heartbeat and replication IP address |
Used to detect the status of the network connection and replicate data between the active and standby eSight servers. |
Active server |
Network port 2 (eth1; eth 6 for 2288X servers) |
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 belong to the same network plane. |
|
Standby server |
Network port 2 (eth1; eth 6 for 2288X servers) |
|
Installation Path Planning
Item |
Example |
Description |
---|---|---|
eSight |
/opt/eSight |
|
User Name and Password Planning
Item |
Default Password |
Description |
---|---|---|
SUSE operating system administrator user root |
The password is configured during SUSE Linux installation. |
The root user is the default Linux operating system user. It has the highest operation rights of the Linux operating system. This user can control all operating system resources, create other users, assign rights to the users, and use all the functions provided by the operating system. The installation and uninstallation of the eSight server application software must be performed by the root user. |
eSight user ossuser on the SUSE operating system |
Changeme_123 |
The ossuser account, automatically created by eSight, performs routine operation and maintenance (O&M) for the eSight server. This user can remotely log in to the server through SSH and upload or download files through SFTP. |
GaussDB database administrator user sys |
Changeme123 |
The sys user is a default user provided by the database. It is the system administrator of the database and has the highest rights of the database. |
eSight database user commonuser of the GaussDB |
Changeme_123 |
The commonuser user is a database user of the NMS. |
eSight administrator user admin NOTE:
The user login address is https://IP address:31943. |
Changeme123 NOTE:
You need to change the password at your first login. |
The admin user is the default administrator provided by eSight. This user has the management rights of all devices and operation rights of all eSight clients. |
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 at your first login. |
The sys user is the unique user of the maintenance tool. This user can manage the eSight server and perform all operations on the maintenance tool. |
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).
Time Zone and Time Planning
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-108 during installation, which improves system compatibility.
Server RAID Planning
- 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 8-109. For details about how to plan and configure the RAID, see the server guide.
- The 2288H V5 servers delivered for eSight have two types: standard-configuration servers and high-configuration servers.
Table 8-110 RAID planning for 2288H V5 servers
Server Type
Number of Disks
Disk
RAID
One-node system 2288H V5 server with standard configurations
4
First to third disks
RAID 5
Fourth disk
HotSpare
One-node system 2288H V5 server with high configurations
6
First to fifth disks
RAID 5
Sixth disk
HotSpare
- The 2288X V5 servers delivered for eSight have two types: standard-configuration servers and high-configuration servers.
Table 8-111 RAID planning for 2288X V5 servers
Server Type
Number of Disks
Disk
RAID
One-node system 2288X V5 server with standard configurations
2
First and second disks
RAID 1
One-node system 2288X V5 server with high configurations
6
First to fifth disks
RAID 5
Sixth disk
HotSpare
Disk Partition Planning
Partition |
Capacity |
File System |
Description |
---|---|---|---|
/ |
50 GB |
Ext4 |
Root directory for installing the operating system. |
swap |
16 GB |
Swap |
Swap directory. |
/boot/efi |
1 GB |
FAT |
Boot 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 |
Ext4 |
Directory for installing eSight. |