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

Networking Design

Networking Design for Server Deployment

When server deployment is used, the standard AMI solution supports remote disaster recovery in the single-node system and cluster. The networking varies depending on the deployment solution. The CIS or EPMS needs to be deployed at the application layer. When cluster deployment is used, application systems need to be configured with load balancing. The application systems support software load balancing and F5 load balancer. The remote disaster recovery solution does not support software load balancing. In cluster mode, only the F5 load balancer can be used to implement load balancing of application systems.

Single-Node System Deployment Solution
When the single-node system is used, application systems and databases use the single-node system, and can be deployed on the same device or separately. For details about the server configuration in different solutions, see the system design. For the single-node system deployment solution, load balancing does not need to be configured. Figure 1-8 shows the networking.
Figure 1-8  Networking for single-node system deployment
Cluster Deployment Solution
When the cluster mode is used, application systems share the database. All application systems and database use the cluster or active/standby mode, and can be deployed on the same device or separately. For details about the server configuration in different solutions, see the system design. When cluster deployment is used, load balancing needs to be configured. The standard AMI solution supports the software load balancer and F5 load balancer.
  • Software load balancing

    The third-party application system and EEM use the Nginx to implement Layer 7 load balancing, and the DCP uses the LVS to implement Layer 4 load balancing. Figure 1-9 shows the networking.

    Figure 1-9  Networking when the cluster mode and software load balancer are used
  • F5 load balancer

    The EEM uses the Nginx to implement Layer 7 load balancing, and the DCP uses the F5 load balancer to implement load balancing. The third-party application system can use the F5 load balancer. Figure 1-10 shows the networking.

    Figure 1-10  Networking when the cluster mode and F5 load balancer are used
Remote Disaster Recovery Solution

The remote disaster recovery solution can be deployed in the single-node system or cluster mode. When the cluster mode is used, each application system supports only the F5 load balancer. For the networking design, see Networking of the Remote Disaster Recovery Solution.

Networking Design for VM Deployment

For VM deployment, the third-party application system, EEM, DCP, and database are deployed on VMs, and can be deployed in the single-node system or cluster mode. When the cluster deployment solution is used, load balancing needs to be configured. Only software load balancing can be used, and the CIS or EPMS needs to be deployed.

The AMI solution supports Hyper-V, VMware, and FusionSphere VMs. The third-party application system, EEM, and DCP are deployed on VMs running Linux operating system. The operating system of the database is selected based on the deployment mode. For example, the MySQL database, Oracle in the single-node system, and Oracle RAC can be deployed on the VMs running the Linux operating system, whereas Oracle HA needs to be installed on the VM running Windows Server 2008 operating system.

Single-Node System Deployment Solution
All application systems and databases use the single-node system, and can be deployed on the same device or separately. Server and VM configurations are different when different deployment solutions are used. For details, see the system design. For the single-node system deployment solution, load balancing does not need to be configured. Figure 1-11 shows the networking.
Figure 1-11  Networking when single-node system deployment is used
Cluster Deployment Solution
When the cluster mode is used, all application systems and databases use the cluster or active/standby mode. Server and VM configurations are different when different deployment solutions are used. For details, see the system design. When cluster deployment is used, load balancing needs to be configured. The VM deployment solution supports only the LVS. The third-party application system and EEM use the Nginx to implement Layer 7 load balancing, and the DCP uses the LVS to implement Layer 4 load balancing. Figure 1-12 shows the networking. The VM deployment solution supports only MySQL HA, Oracle RAC, and Oracle HA. The database is selected as required. For details about selection principles, see Deployment Design. Here, Oracle HA is used.
Figure 1-12  Networking when cluster deployment is used
Translation
Download
Updated: 2019-03-07

Document ID: EDOC1100069579

Views: 6016

Downloads: 9

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