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 EEM

Software and Hardware Configurations of the EEM

The EEM involves server and VM deployment. Each deployment mode supports the single-node system and cluster. The deployment scenario depends on the number of terminals. The server type and quantity are also different. You can select configurations according to the actual situation. The EEM cluster contains three servers. If VM deployment is used, three VMs running Linux operating system need to be deployed.

In server deployment mode, the EEM supports remote disaster recovery. The remote disaster recovery solution can be deployed in the single-node system or cluster mode. The production center and disaster recovery center need to be configured with the same application systems and databases. That is, the software and hardware configurations of application systems in the disaster recovery center must be consistent with those in the production center. Databases in the remote disaster recovery solution need to be configured with Data Guard (DG) to implement data backup and recovery. The remote disaster recovery solution does not support software load balancing. In cluster mode, the third-party application system and DCP need to use the F5 load balancer to implement load balancing.

The EEM supports the MySQL database and Oracle database. The MySQL database is deployed when there are no more than 100,000 terminals.
  • In the AMR solution, only the EEM and DCP are deployed at the application layer. You can select the database based on the number of terminals and requirements. The EEM and DCP use the same database.
  • In the small-sized AMI solution and standard AMI solution, the third-party application system needs to be deployed at the application layer. The third-party application system supports only the Oracle database and uses an independent Oracle database. In this case, two databases are deployed. One database is used by the EEM and DCP, and the other database is used by the third-party application system.

In the remote disaster recovery solution, the networking and configuration of the EEM and the EEM server configuration in the disaster recovery center are similar to those of the production center. The production center is used as an example to describe the software and hardware configurations of the EEM. The software and hardware configurations of the EEM in the disaster recovery center are similar to those of the production center, and are not described here.

EEM Software Configuration

Table 2-9 describes the EEM software configuration.
Table 2-9  EEM 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 EEM software is deployed in the Linux SUSE operating system. In server deployment mode, remote disaster recovery is supported.

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.

Remote disaster recovery is supported. When there are more than 100,000 devices, Oracle RAC is recommended to ensure reliability.

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. In server deployment mode, remote disaster recovery is supported.

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.

In server deployment mode, remote disaster recovery is supported. When there are more than 100,000 devices, Oracle RAC is recommended to ensure reliability.

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

The EEM supports login through a browser. You must use Chrome 26 or later.

EEM Hardware Configuration

Table 2-10 describes the EEM hardware configuration.
Table 2-10  EEM hardware configuration

Number of Managed Devices

Solution Selection

Deployment Mode

Deployment Solution

Remote Disaster Recovery

Recommended Configuration

Description

0 to 20,000

Small-sized AMI solution

Server deployment

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

Remote disaster recovery is supported.

  • Production center: PC12C64G*1
  • Disaster recovery center: PC12C64G*1

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

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

The EEM cluster is used and deployed separately with other application systems in cluster or active/standby mode and database.

  • Production center: PC12C64G*3
  • Disaster recovery center: PC12C64G*3

The EEM cluster contains three EEM node and the LVS needs to be configured.

VM deployment

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

Remote disaster recovery is not supported.

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

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

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

The EEM cluster is used and deployed separately with other application systems in cluster or active/standby mode and database.

The EEM cluster is deployed on the VM running Linux operating system, and the LVS is configured.

0 to 6,000,000

  • AMR solution
  • Standard AMI solution

Server deployment

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

Remote disaster recovery is supported.

  • Production center: PC12C64G*1
  • Disaster recovery center: PC12C64G*1

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

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

  • Production center: PC12C64G*1
  • Disaster recovery center: PC12C64G*1

The EEM cluster is used and deployed separately with other application systems in cluster or active/standby mode and database.

  • Production center: PC12C64G*3
  • Disaster recovery center: PC12C64G*3

The EEM cluster contains three EEM node and the LVS needs to be configured.

Standard AMI solution

VM deployment

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

Remote disaster recovery is not supported.

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

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

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

The EEM cluster is used and deployed separately with other application systems in cluster or active/standby mode and database.

The EEM cluster is deployed on the VM running Linux operating system, and the LVS is configured.

Translation
Download
Updated: 2019-03-07

Document ID: EDOC1100069579

Views: 8536

Downloads: 14

Average rating:
This Document Applies to these Products

Related Version

Related Documents

Share
Previous Next