Routing Design
Design Description
- There are reachable routes between the CIS or EPMS server, EEM server, DCP server, and database server.
- There must be a reachable route from the CIS or EPMS server to the EEM cluster so that the CIS or EPMS server can synchronize data to the EEM.
- There must be a reachable route from the northbound interface of the DCP server to the EEM cluster so that the EEM can synchronize parameters or deliver commands to the DCP and the DCP can upload data to the EEM.
- There must be reachable routes from the CIS or EPMS server and DCP server to the load balancer.
- There must be a reachable route from the load balancer to the external network. If remote disaster recovery is deployed, only the F5 load balancer can be used to implement load balancing of application systems. Ensure that the F5 load balancer can communicate with application systems of the local data center and there are reachable routes between the F5 load balancer and external network so that users and terminals can exchange data with application systems.
- If remote disaster recovery is deployed, ensure that servers of application systems in the same data center can communicate and there are reachable routes between the data center and disaster recovery center so that data can be backed up.
Gateway's Routing Design
For route design on the egress gateway of the application layer and IoT gateway of the data perception layer, there must be reachable routes from the DCU to the load balancer and DCP cluster; otherwise, the DCU cannot find the required DCP for data transmission. There must be reachable routes between the egress gateway of the application layer and external network. This ensures reachability between the third-party application system and EEM server or between the third-party application system cluster and EEM cluster so that external users can log in to the CIS, EPMS, and EEM through the web.