dadrobna/enterprise-router
1
0
Fork 0
forked from docs/enterprise-router
Code Pull Requests Activity
enterprise-router/umn/source/service_overview/when_to_use_enterprise_routers.rst
proposalbot 5b1d5d43ce Changes to er_umn from docs/doc-exports#1048 (ER UMN 20240206 version 
For detai

Reviewed-by: Sarda, Priya <prsarda@noreply.gitea.eco.tsi-dev.otc-service.com>
Co-authored-by: proposalbot <proposalbot@otc-service.com>
Co-committed-by: proposalbot <proposalbot@otc-service.com>
2024-02-23 15:39:27 +00:00

11 KiB
Raw Blame History

original_name

er_01_0004.html

When to Use Enterprise Routers

You can use enterprise routers to build cloud, on-premises, or hybrid networks. Here are some typical application scenarios:

  • Scenario 1: Multiple VPCs communicating or not communicating with each other on the cloud, but communicating with the on-premises data center through a Direct Connect connection <er_01_0004__section16111115210>
  • Scenario 2: Dynamic switchover between multiple Direct Connect connections <er_01_0004__section12577403566>

Scenario 1: Multiple VPCs communicating or not communicating with each other on the cloud, but communicating with the on-premises data center through a Direct Connect connection

Figure 1 Diagram for scenario 1
Table 1 Using enterprise routers in scenario 1
Customer Requirements Multiple service networks communicate or do not communicate with each other on the cloud but communicate with the on-premises data center. Suppose you require three VPCs for running the workloads on the public cloud, and the three VPCs (services A, B, and C) need to access public services in VPC 4 and your on-premises data center.
Pain Points
  • VPC peering connections are required for communications among these VPCs, but they will complicate the network topology and make the network hard to manage.
  • VPC peering connections and routes are required for the public service VPC to communicate with each VPC. However, VPC peering connections do not fit in large-scale networks because of the following limitations:
    • A maximum of 50 VPC peering connections can be created in one region.
    • A VPC route table can have a maximum of 200 routes.
  • Direct Connect connections are required for each VPC to communicate with the on-premises data center, but they will incur high costs.
Benefits of Using Enterprise Routers
  • VPCs can be associated with different route tables on the enterprise router to enable communication or isolation. The network topology is simple and easy to manage.
  • Enterprise routers can route traffic among all the connected VPCs without the need to configure a large number of VPC peering connections.
    • Each enterprise router can have a maximum of 2,000 routes in each route table, making it ideal for large-scale complex networks.
  • Multiple VPCs can access the on-premises data center over a Direct Connect connection, eliminating the need to configure multiple Direct Connect connections and reducing the costs.

Scenario 2: Dynamic switchover between multiple Direct Connect connections

Figure 2 Diagram for scenario 2
Table 2 Using enterprise routers in scenario 2
Customer Requirements Some services run on the public cloud and some in the on-premises data center. Two independent high-bandwidth Direct Connect connections are deployed between the public cloud and the data center to enable communication between them.
Pain Points Two Direct Connect connections are independent of each other and cannot work in load-sharing or active/standby mode.
Benefits of Using Enterprise Routers

Direct Connect connections are connected to the enterprise router.

  • Two Direct Connect connections can work in load-sharing mode to ensure high bandwidth and reliability.
  • Two Direct Connect connections can also work in active/standby mode. If one of the connections becomes unavailable, services are switched over to the other available connection within seconds, preventing service interruptions.