enterprise-router/umn/source/service_overview/notes_and_constraints.rst
proposalbot 5f54580f4f Changes to er_umn from docs/doc-exports#680 (ER UMN 20230324 version
first uplo

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>
2023-12-06 13:27:37 +00:00

2.1 KiB

original_name

er_01_0006.html

Notes and Constraints

Specifications

Table 1 <er_01_0006__table591864733813> lists the specifications of the enterprise router.

Table 1 Enterprise router specifications
Item Default Setting Adjustable
Maximum number of enterprise routers that can be created by each account 1 Contact customer service.
Maximum forwarding capability supported by each enterprise router 100 Gbit/s Contact customer service.

Constraints

  • Enterprise routers cannot be used together with virtual IP addresses of VPCs. If virtual IP addresses are used, contact customer service.

  • Traffic cannot be forwarded from a VPC to the enterprise router that it attached to if you set the destination of a route whose next hop is the enterprise router to 0.0.0.0/0 in the VPC route table and if:

    • An ECS in the VPC has an EIP bound.
    • The VPC is being used by ELB, NAT Gateway, VPC Endpoint, or Distributed Cache Service (DCS).

    To solve this problem, refer to Why Traffic Can't Be Forwarded from a VPC with a Route Destination of 0.0.0.0/0 to Its Enterprise Router? <er_01_0121>

  • The VPC route table does not allow you to add a route whose destination address is 100.64.x.x and next hop is an enterprise router.

    To solve this problem, refer to How Do I Route Traffic to 100.64.x.x Through an Enterprise Router? <er_01_0122>