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).
Software and Hardware Configurations of the DCP

Software and Hardware Configurations of the DCP

You can deploy the Data Collection Platform (DCP) in the single-node system or DCP cluster depending on the number of connected terminals. The requirements for load balancing are different, and the server type and quantity are also different. You can select configurations according to the actual situation.

The DCP supports both Oracle and MySQL databases. The DCP and EEM share the database, and the database type and deployment mode of the DCP are the same as those of the EEM.

When a DCP cluster is deployed, the DCP cluster allows a maximum of 20 DCP nodes. Load balancing needs to be deployed. The DCP supports the F5 load balancer and Linux Virtual Server (LVS) that is the load balancing software. Different load balancing modes have different requirements for the hardware.

In server deployment mode, the DCP supports remote disaster recovery. The remote disaster recovery solution does not support software load balancing. In cluster mode, the DCP can only use the F5 load balancer. In the remote disaster recovery solution, the networking and deployment of the DCP and DCP server configuration in the disaster recovery center are similar to those in the production center. The DCP configuration in the production center is used as an example. For details about the software and hardware configuration of the standalone DCP in the disaster recovery center, see the software and hardware configuration of the DCP in server deployment mode. For the software and hardware configuration of the DCP cluster, see the software and hardware configuration of the DCP in server deployment mode when the F5 load balancer is used.

DCP Software Configuration

Table 2-15 describes the DCP software configuration.
Table 2-15  DCP software configuration

Item

Solution Selection

Number of Managed Devices

Deployment Mode

Recommended Configuration

Description

Operating system

AMR solution

0 to 6,000,000

Server deployment

Novell SuSE LINUX Enterprise Server 11.3

The DCP software is deployed in the Linux SUSE operating system.

Small-sized AMI solution

0 to 20,000

  • Server deployment
  • VM deployment

Standard AMI solution

0 to 6,000,000

Database

AMR solution

0 to 100,000

Server deployment

  • MySQL database in the single-node system
  • MySQL HA
  • Oracle database in the single-node system
  • Oracle RAC

The AMR solution supports only server deployment. When the number of connected terminals is within 100,000 and the MySQL database is supported, you can deploy the MySQL database in the single-node system or MySQL HA.

100,000 to 6,000,000

  • Oracle database in the single-node system
  • Oracle RAC

Small-sized AMI solution

0 to 20,000

Server deployment

  • MySQL database in the single-node system
  • MySQL HA
  • Oracle database in the single-node system
  • Oracle RAC

The small-sized AMI solution supports server and VM deployment. When VM deployment is used, Oracle HA is supported. Oracle HA needs to be deployed on the VM running Windows Server 2008 operating system.

VM deployment

  • MySQL database in the single-node system
  • MySQL HA
  • Oracle database in the single-node system
  • Oracle RAC
  • Oracle HA

Standard AMI solution

0 to 100,000

Server deployment

  • MySQL database in the single-node system
  • MySQL HA
  • Oracle database in the single-node system
  • Oracle RAC

The standard AMI solution supports server and VM deployment. For VM deployment, Oracle HA is used and deployed on the VM running Windows Server 2008 operating system.

When the number of connected terminals is within 100,000, the MySQL database is supported. You can deploy the MySQL database in the single-node system or MySQL HA.

VM deployment

  • MySQL database in the single-node system
  • MySQL HA
  • Oracle database in the single-node system
  • Oracle RAC
  • Oracle HA

100,000 to 6,000,000

Server deployment

  • Oracle database in the single-node system
  • Oracle RAC

VM deployment

  • Oracle database in the single-node system
  • Oracle RAC
  • Oracle HA

Browser

  • AMR solution
  • Small-sized AMI solution
  • Standard AMI solution

0 to 6,000,000

  • Server deployment
  • VM deployment

Chrome 26 or later

-

DCP Hardware Configuration

Table 2-16 describes the DCP hardware configuration.
Table 2-16  DCP hardware configuration

Number of Managed Devices

Solution Selection

Deployment Mode

Deployment Solution

Load Balancing

Recommended Configuration

Description

0 to 20,000

Small-sized AMI solution

Server deployment

The DCP is deployed on the same device as other application systems in the single-node system and database.

-

PC12C64G*1

When the DCP in the single-node system is deployed, load balancing does not need to be configured.

The DCP in the single-node system, other application systems in the single-node system, and database are deployed separately.

Cluster

LVS

PC12C64G*3

There are few connected terminals. To ensure reliability, deploy the cluster and load balancing. The LVS is used to reduce costs. The LVS and DCP are deployed on the same device. The LVS is deployed on any two DCP servers of the DCP cluster, and the LVS in active/standby mode is configured.

VM deployment

The DCP is deployed on the same device as other application systems in the single-node system and database.

-

  • VM configuration:
    • Memory: 72 GB or more
    • Hard disk: 1200 GB or more
  • Physical server configuration
    • PC14C72G

The DCP in the single-node system is installed on the VM running Linux operating system, and load balancing does not need to be configured.

The DCP in the single-node system, other application systems in the single-node system, and database are deployed separately.

Cluster

LVS

The DCP cluster is deployed on the VM running Linux operating system, and the LVS is configured. The LVS and DCP are deployed on the same device. The LVS is deployed on any two DCP servers of the DCP cluster, and the LVS in active/standby mode is configured.

0 to 6,000,000

  • AMR solution
  • Standard AMI solution

Server deployment

The DCP is deployed on the same device as other application systems in the single-node system and database.

-

PC12C64G*1

When the DCP in the single-node system is deployed, load balancing does not need to be configured.

The DCP in the single-node system, other application systems in the single-node system, and database are deployed separately.

Cluster

LVS

A maximum of five servers that contain at least one PC12C64G server

When the LVS is used, the DCP cluster allows a maximum of five DCP nodes and two DCP servers among the servers are used as active and standby LVSs. The LVS saves costs, and active and standby LVSs ensure reliability.

F5 load balancer

  • A maximum of 20 servers that contain at least one PC12C64G server
  • F5 load balancer

The DCP cluster allows a maximum of 20 DCP nodes, and the F5 load balancer needs to be deployed. This deployment has high costs, but the F5 load balancer has high reliability and supports the active/standby mode.

Standard AMI solution

VM deployment

The DCP is deployed on the same device as other application systems in the single-node system and database.

-

  • VM configuration:
    • Memory: 72 GB or more
    • Hard disk: 1200 GB or more
  • Physical server configuration
    • PC14C72G

The DCP in the single-node system is installed on the VM running Linux operating system, and load balancing does not need to be configured.

The DCP in the single-node system, other application systems in the single-node system, and database are deployed separately.

Cluster

LVS

The DCP cluster is deployed on the VM running Linux operating system, and the LVS is configured. The LVS and DCP are deployed on the same device. The LVS is deployed on any two DCP servers of the DCP cluster, and the LVS in active/standby mode is configured.

Translation
Download
Updated: 2019-03-07

Document ID: EDOC1100069579

Views: 6028

Downloads: 9

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