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

AMI Smart Meter Reading Solution V200R010C10 Planning and Design Guide

This document describes the overall and detailed design of functions and services in the AMI Smart Meter Reading Solution.
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).
DCP Reliability Design

DCP Reliability Design

A DCP cluster is deployed to ensure reliability. In this case, load balancing also needs to be configured. That is, the reliability of the DCP involves its reliability and load balancing reliability.

DCP Reliability

A DCP cluster can be deployed and the DCP load balances services of its downstream terminals. The DCP cluster ensures system reliability, and load balancing ensures service reliability.

Terminals do not detect DCP nodes. All DCUs and GPRS meters connect to DCPs through a load balancer and detect only the IP address of the load balancer. When a DCP node in the cluster becomes faulty or has a high resource usage, the load balancer automatically switches services from this DCP to another DCP. DCUs and smart meters are unaware of this switchover process.

The EEM can monitor and manage DCP nodes and the DCP cluster. In the EEM, you can view the online status of DCP nodes and the DCP cluster, running status as well as resource usage of DCP nodes. When the resource usage of a DCP node exceeds the configured threshold, an alarm is reported. When a DCP node requests many resources or has a high resource usage, the load balancer switches services from this DCP node to another lightly-loaded node to improve task execution efficiency. Terminals are unaware of this service switchover.

Downstream devices of the DCP cluster use the load balancer for load balancing. The load balancer checks whether a DCP can return requested data and determines whether failures occur on the DCP server, for example, the DCP server stops working or crashes. If such failures occur on the DCP server, the load balancer allocates access requests to another working DCP server to ensure nonstop user access. When the faulty DCP server recovers, the load balancer automatically checks whether this DCP server can respond to access requests. If so, the load balancer allocates task requests to the DCP server again to resume the service processing function on the DCP node. Terminals are unaware of changes to DCP nodes.

Reliability of Load Balancing

The DCP supports the F5 load balancer and Linux Virtual Server (LVS) that is the load balancing software. The LVS and F5 load balancer use the active/standby mode to ensure service reliability.

Reliability of the LVS

The LVS provides a virtual server cluster. It uses IP load balancing and content-based request distribution technologies to evenly transfer requests to different servers. It automatically shields faulty servers and builds virtual servers with high performance and availability. It analyzes the IP layer and TCP/UDP layer information and load balances Layer 4 traffic. It supports multiple load balancing policies. The AMI solution uses the weighted least connection algorithm to implement load balancing.

The LVS can be deployed independently or deployed on the same device as other applications. In the AMI solution, the LVS and DCP are deployed on the same device. The LVS supports a maximum of 5 DCP nodes. Any two DCP servers have the LVS installed and work in active/standby mode. The LVSs in active/standby mode implement reliability through Keepalived. Keepalived is deployed on the same device as the LVS and responsible for selecting active and standby LVSs, binding the virtual IP address, detecting the heartbeat, and performing an active/standby switchover.

After the LVS is deployed, Keepalived selects the active LVS, binds the virtual IP address to the active LVS, and configures the default gateway address of DCP servers as the virtual IP address of the LVS. Keepalived virtualizes the DCP servers into a combination of an IP address and a port number and checks the health status of the DCP servers through DCP. Servers are not assigned to the faulty DCP server. When the faulty DCP server recovers, original servers of the DCP server are allocated to the DCP server again. The active and standby LVSs perform heartbeat detection through Keepalived and VRRP instances. If the heartbeat connection is terminated, the active/standby switchover is performed. After the standby LVS becomes the active LVS, all services are switched to the standby LVS. After the active LVS recovers, services are not switched.

Reliability of the F5 Load Balancer

In the AMI solution, F5 load balancers in active/standby mode are configured to ensure reliability. The active and standby F5 load balancers detect the status of each other through the heartbeat IP address. When the active F5 load balancer fails, all services are switched to the standby F5 load balancer. External devices exchange data with F5 load balancers. The virtual IP address corresponds to the active F5 load balancer. When the active F5 load balancer fails, the virtual IP address is switched to the standby F5 load balancer and all services are switched to the standby F5 load balancer.

The F5 load balancer supports multiple load balancing policies. The AMI solution uses the weighted least connection algorithm to implement load balancing. The F5 load balancer can detect the DCP node status. When a DCP node fails, tasks are not assigned to the DCP node. After the faulty DCP node recovers, original services are still assigned to the DCP node.

Translation
Download
Updated: 2019-03-07

Document ID: EDOC1100069579

Views: 5481

Downloads: 8

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