Help Center> Enterprise Router> Service Overview> Notes and Constraints
Updated on 2024-04-19 GMT+08:00
View PDF

Notes and Constraints

Quotas

Table 1 lists the quotas about enterprise router resources. Some default quotas can be increased.

You can log in to the console to view default quotas. For details, see Viewing Quotas.

Table 1 Enterprise router resource quotas

Item

Adjustable

Maximum number of enterprise routers that can concurrently connect to a VPC

No

Maximum number of VPCs that can be attached to an enterprise router

Yes

Maximum number of peering connections that can be attached to an enterprise router

Yes

Maximum number of virtual gateways that can be attached to an enterprise router

Yes

Maximum number of VPN gateways that can be attached to an enterprise router

Yes

Maximum number of route tables allowed on each enterprise router

No

Maximum number of routes allowed on each enterprise router

No

Maximum number of static routes allowed in each route table

Yes

Maximum number of flow logs that can be created by each account

No

Specifications

Table 2 lists the specifications of the enterprise router.

Table 2 Enterprise router specifications

Item

Default Setting

Adjustable

Maximum number of enterprise routers that can be created by each account

1

Yes

Maximum forwarding capability supported by each enterprise router

100 Gbit/s

Yes

Constraints

There are some constraints on using enterprise routers, as described in Table 3. You can follow our suggestions to handle these issues.

Table 3 Constraints on enterprise routers

Constraint

Suggestion

If a service VPC is being used by ELB, VPC Endpoint, NAT Gateway (private NAT gateway), Distributed Cache Service (DCS), or hybrid DNS, this VPC cannot be attached to an enterprise router.

NOTICE:

If you attach a service VPC to an enterprise router when Elastic Load Balance (ELB), VPC Endpoint, or DCS is being used together with Enterprise Router, persistent connections may be intermittently interrupted during service reliability assurance, such as a DR switchover, an upgrade, or elastic scaling. Ensure that the clients are capable of automatic reconnection in case of intermittent disconnection.

Submit a service ticket to confirm the service compatibility and preferentially use a transit VPC for networking. For details, see scheme 2 in Selecting a Networking Scheme.
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 the ELB (either dedicated or shared load balancers), NAT Gateway, VPCEP, and DCS services.

If a VPC attached to an enterprise router has a NAT gateway associated and Scenario of the SNAT or DNAT rules is set to Direct Connect/Cloud Connect, the network from the on-premises data center to the VPC is disconnected.

Use a transit VPC for networking. For details, see scheme 2 in Selecting a Networking Scheme.