forked from docs/enterprise-router
37 lines
1.8 KiB
ReStructuredText
37 lines
1.8 KiB
ReStructuredText
:original_name: er_01_0006.html
|
|
|
|
.. _er_01_0006:
|
|
|
|
Notes and Constraints
|
|
=====================
|
|
|
|
Specifications
|
|
--------------
|
|
|
|
:ref:`Table 1 <er_01_0006__table591864733813>` lists the specifications of the enterprise router.
|
|
|
|
.. _er_01_0006__table591864733813:
|
|
|
|
.. table:: **Table 1** Enterprise router specifications
|
|
|
|
+--------------------------------------------------------------------------+------------------------+---------------------------+
|
|
| Item | Default Specifications | 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. |
|
|
+--------------------------------------------------------------------------+------------------------+---------------------------+
|
|
|
|
|
|
Notes and 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 its attached enterprise router if you set the destination of a route in the VPC route table to 0.0.0.0/0 and:
|
|
|
|
- An ECS in the VPC has an EIP bound.
|
|
- The VPC is being used by ELB, NAT Gateway, or VPC Endpoint.
|
|
|
|
To solve this problem, refer to :ref:`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>`
|