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).
Deployment Design

Deployment Design

The small-sized AMI solution is used when there are at most 20,000 smart meters. The small-sized AMI solution supports remote disaster recovery. It supports server and VM deployment. In each deployment mode, the remote disaster recovery solution can be deployed in the single-node system or cluster mode. If remote disaster recovery is deployed, only server deployment is supported. The requirements for each component and load balancing are as follows:
  • The third-party application system can be CIS or EPMS. The CIS provides the same functions as the EPMS. Both the CIS and EPMS can be deployed independently or in a cluster. You can select the CIS or EPMS as needed.
  • For VM deployment, the solution supports Hyper-V, VMware, and FusionSphere. The VM operating system is selected as required. You can install the Linux or Windows operating system.
  • For VM deployment, if the Oracle database is selected and Oracle HA is deployed to ensure database reliability through the failover mechanism, the Oracle database server and shared storage server must use the VMs that have Windows Server 2008 operating system installed.
  • For cluster deployment, software load balancing is recommended to reduce costs. The third-party application system and EEM use the Nginx to implement Layer 7 load balancing, and the DCP uses the LVS to implement device-side load balancing.
  • If remote disaster recovery is deployed, only server deployment can be used. The remote disaster recovery solution does not support software load balancing. When application systems of the production center and disaster recovery center use the cluster mode, only the F5 load balancer can be used.
Table 1-4 describes the deployment design.
Table 1-4  Deployment design

Deployment Mode

Deployment Solution

Number of Connected Smart Meters

Application System Selection

Database Deployment

Load Balancing Configuration

Remote Disaster Recovery

Operating System

Description

Server deployment

Single-node system

0-20000

  • Third-party application system (CIS or EPMS)
  • EEM
  • DCP
  • Database of the EEM and DCP: MySQL database in the single-node system
  • Database of the third-party application system: Oracle database in the single-node system

-

Remote disaster recovery is supported. For details, see Remote Disaster Recovery Design.

Server operating system: Linux

The EEM and DCP use the same MySQL or Oracle database, and the third-party application system uses the Oracle database. All application systems and databases use the single-node system, and can be deployed on the same device or separately. Load balancing does not need to be configured. Different deployment modes correspond to different server configurations. For details about the server configuration, see the hardware configuration of each application system.

  • Database of the EEM and DCP: Oracle database in the single-node system
  • Database of the third-party application system: Oracle database in the single-node system

-

Cluster deployment

  • Third-party application system (CIS or EPMS)
  • EEM
  • DCP
  • Database of the EEM and DCP: MySQL HA
  • Database of the third-party application system: Oracle RAC
  • Software load balancing
  • F5 load balancer
  • When software load balancing is used, remote disaster recovery is not supported.
  • When the F5 load balancer is used, remote disaster recovery is supported. For details, see Remote Disaster Recovery Design.

The EEM and DCP use the same MySQL or Oracle database, and the third-party application system uses the Oracle database. The application systems and databases use the cluster or active/standby mode. The application systems need to be configured with load balancing and support software load balancing and F5 load balancer. A small number of devices are deployed, so software load balancing is recommended to save costs. If remote disaster recovery is deployed, only the F5 load balancer can be used to implement load balancing of application systems.

  • Database of the EEM and DCP: Oracle RAC
  • Database of the third-party application system: Oracle RAC

VM deployment

Single-node system

0-20000

  • Third-party application system (CIS or EPMS)
  • EEM
  • DCP
  • Database of the EEM and DCP: MySQL database in the single-node system
  • Database of the third-party application system: Oracle database in the single-node system

-

Remote disaster recovery is not supported.

  • Server operating system: Windows
  • VM operating system: Linux

The EEM and DCP use the same MySQL or Oracle database, and the third-party application system uses the Oracle database. All application systems and databases use the single-node system, and can be deployed on the same device or separately. Load balancing does not need to be configured. Different deployment modes correspond to different server configurations. For details about the server configuration, see the hardware configuration of each application system.

  • Database of the EEM and DCP: Oracle database in the single-node system
  • Database of the third-party application system: Oracle database in the single-node system

-

Cluster deployment

  • Third-party application system (CIS or EPMS)
  • EEM
  • DCP
  • Database of the EEM and DCP: MySQL HA
  • Database of the third-party application system: Oracle RAC or Oracle HA

Software load balancing

  • Server operating system: Windows
  • VM operating system
    • When MySQL HA or Oracle RAC is used, all VMs are configured with the Linux operating system and all application systems and databases.
    • When Oracle HA is used, the VM where the Oracle HA is deployed needs to have Windows Server 2008 installed and other VMs are configured with the Linux operating system.

The EEM and DCP use the same MySQL or Oracle database, and the third-party application system uses the Oracle database. The application systems and databases use the cluster or active/standby mode. The application systems need to be configured with software load balancing, and the DCP uses the LVS to implement Layer 4 load balancing.

  • Database of the EEM and DCP: Oracle RAC or Oracle HA
  • Database of the third-party application system: Oracle RAC or Oracle HA
Translation
Download
Updated: 2019-03-07

Document ID: EDOC1100069579

Views: 8492

Downloads: 14

Average rating:
This Document Applies to these Products

Related Version

Related Documents

Share
Previous Next