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

eLog V200R007C10 Installation Guide

Describes the installation process of product software. Includes plans, environmental requirements, and procedures for installation, as well as commissioning procedures.
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).
High Availability Planning

High Availability Planning

This section describes how to plan high availability (HA) for the eLog analyzer or collector.

HA Solution Overview

The eLog supports HA management for distributed analyzers and collectors. However, HA management is not supported for centralized deployment scenarios. You can create multiple HA groups, each of which consists of two analyzers or collectors for hot standby.

The two analyzers or collectors in hot standby mode provide individual analyzer or collector services externally through the virtual IP address. One of the two collectors or analyzers is in active state, and the other in standby state. When the active one is abnormal, the standby one takes over, without interrupting services. The active and standby analyzers or collectors monitor the operating status of the peer and synchronize configuration information from the peer through the private network (heartbeat link). To prevent synchronization failures due to heartbeat link faults, connecting two heartbeat links between the active and standby collectors or analyzers is recommended.

In this solution, Huawei-proprietary eLog HA software is used for HA management. For the two devices in hot standby mode, their resources and storage are independent, featuring simplicity and capability to satisfy geographical redundancy. It is required that the hardware configurations, software versions, installation paths, and storage space of the two devices be the same.

You shall plan the following types of IP addresses for the HA system:

IP address

Description

IP address of the management port (iBMC port)

This port is used for remotely connecting to and managing server hardware.

Service local IP address

The collector communicates with the virtual IP address of the analyzer through the service local IP address. When the analyzer queries data, it queries data only from the collector in active state.Therefore, it is required that the collector service local IP address be reachable to the analyzer service virtual IP address.

The analyzer service local IP address is used only for HA group creation, and the service virtual IP address is used for communication with the collector.

Service virtual IP address

The service local IP addresses of the active and standby devices are added to the same HA group for setting the service virtual IP address.

The virtual IP address of the analyzer is used for communication with the collector, and the virtual IP address of the collector is used for collecting logs reported by the log source.

Web access local IP address

This address is used for the active or standby analyzer to provide web services externally for user access.

Web access virtual IP address

The web access local IP addresses of the active and standby analyzers are added to the same HA group for setting the web access virtual IP address. You can access the eLog web UI through the virtual IP address. Web access is not affected after active/standby switchover.

Heartbeat IP address

This address is used for detecting the network connection status and synchronizing data between the active and standby servers.

NOTE:

If the analyzer does not need to physically isolate the web access interface and service interface, set the access IP address and service IP address to be the same and set only one virtual IP address.

Figure 2-3 IP address planning for analyzers in hot standby deployment (with one virtual IP address)
Figure 2-4 IP address planning for analyzers in hot standby deployment (with two virtual IP addresses)
Figure 2-5 IP address planning for collectors in hot standby deployment

IP Address Planning Example 1: Analyzers in Hot Standby Mode (Requiring No Physical Isolation of Web Access and Service Interfaces)

  • Configure the web access and service IP addresses for eth0.
  • Configure heartbeat IP address IP1 for eth3 and heartbeat IP address IP2 for eth4.
  • The web access/service IP address and heartbeat IP address shall reside on different network segments.
  • The analyzer service virtual IP address and the collector service local IP address must be reachable to each other.

Node

Item

Example

Active node server

Web access/service local IP address

  • 192.168.1.101/255.255.255.0/192.168.1.1
  • Network interface: eth0

Web access/service virtual IP address

  • 192.168.1.100
  • Network interface: eth0

Heartbeat IP address 1

  • 172.16.1.101/255.255.255.0/172.16.1.1
  • Network interface: eth3

Heartbeat IP address 2

  • 172.16.2.101/255.255.255.0/172.16.2.1
  • Network interface: eth4

Standby node server

Web access/service local IP address

  • 192.168.1.102/255.255.255.0/192.168.1.1
  • Network interface: eth0

Web access/service virtual IP address

  • 192.168.1.100
  • Network interface: eth0

Heartbeat IP address 1

  • 172.16.1.102/255.255.255.0/172.16.1.1
  • Network interface: eth3

Heartbeat IP address 2

  • 172.16.2.102/255.255.255.0/172.16.2.1
  • Network interface: eth4

IP Address Planning Example 2: Analyzers in Hot Standby Mode (Requiring Physical Isolation of Web Access and Service Interfaces)

  • Configure the web access IP address for eth0.
  • Configure the service IP address for eth1.
  • Configure heartbeat IP address IP1 for eth3 and heartbeat IP address IP2 for eth4.
  • The web access/service IP address and heartbeat IP address shall reside on different network segments.
  • The analyzer service floating IP address and the collector service local IP address must be reachable to each other.

Node

Item

Example

Active node server

Web access local IP address

  • 10.168.1.101/255.255.255.0/10.168.1.1
  • Network interface: eth0

Web access virtual IP address

  • 10.168.1.100/255.255.255.0/10.168.1.1
  • Network interface: eth0

Service local IP address

  • 192.168.1.101/255.255.255.0/192.168.1.1
  • Network interface: eth1

Service virtual IP address

  • 192.168.1.100/255.255.255.0/192.168.1.1
  • Network interface: eth1

Heartbeat IP address 1

  • 172.16.1.101/255.255.255.0/172.16.1.1
  • Network interface: eth3

Heartbeat IP address 2

  • 172.16.2.101/255.255.255.0/172.16.2.1
  • Network interface: eth4

Standby node server

Web access local IP address

  • 10.168.1.102/255.255.255.0/10.168.1.1
  • Network interface: eth0

Web access virtual IP address

  • 10.168.1.100/255.255.255.0/10.168.1.1
  • Network interface: eth0

Service local IP address

  • 192.168.1.102/255.255.255.0/192.168.1.1
  • Network interface: eth1

Service virtual IP address

  • 192.168.1.100/255.255.255.0/192.168.1.1
  • Network interface: eth1

Heartbeat IP address 1

  • 172.16.1.102/255.255.255.0/172.16.1.1
  • Network interface: eth3

Heartbeat IP address 2

  • 172.16.2.102/255.255.255.0/172.16.2.1
  • Network interface: eth4

IP Address Planning Example 3: Collectors in Hot Standby Mode

  • Configure the service IP address for eth0.
  • Configure heartbeat IP address IP1 for eth3 and heartbeat IP address IP2 for eth4.
  • The service IP address and heartbeat IP address shall reside on different network segments.

Node

Item

Example

Active node server

Service local IP address

  • 192.168.1.101/255.255.255.0/192.168.1.1
  • Network interface: eth0

Service virtual IP address

  • 192.168.1.100
  • Network interface: eth0

Heartbeat IP address 1

  • 172.16.1.101/255.255.255.0/172.16.1.1
  • Network interface: eth3

Heartbeat IP address 2

  • 172.16.2.101/255.255.255.0/172.16.2.1
  • Network interface: eth4

Standby node server

Service local IP address

  • 192.168.1.102/255.255.255.0/192.168.1.1
  • Network interface: eth0

Service virtual IP address

  • 192.168.1.100
  • Network interface: eth0

Heartbeat IP address 1

  • 172.16.1.102/255.255.255.0/172.16.1.1
  • Network interface: eth3

Heartbeat IP address 2

  • 172.16.2.102/255.255.255.0/172.16.2.1
  • Network interface: eth4

License Planning

In an HA scenario, use the ESNs of the two servers in the HA group to apply for licenses. In addition, you need to purchase a license for both the active and standby hosts.

Translation
Download
Updated: 2019-04-01

Document ID: EDOC1100073937

Views: 7849

Downloads: 16

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