enterprise-router/umn/source/propagations/propagation_overview.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

6.0 KiB

original_name

er_01_0035.html

Propagation Overview

You can create a propagation for each attachment to propagate routes to one or more route tables on an enterprise router.

If you do not want to create a propagation, you can manually add static routes for attachments to the route tables.

Figure 1 Propagated routes and static routes
Table 1 Propagation description
Attachment Type Propagated Info Way to Create Propagation Description
VPC VPC CIDR blocks
  • Auto creation: If Default Route Table Propagation is enabled and the default propagation route table is specified, attachments automatically propagate routes to the default propagation route table.
    • If you want to enable this function when you create an enterprise router, refer to Creating an Enterprise Router <er_01_0069>.
    • If you want to enable this function after an enterprise router is created, refer to Modifying an Enterprise Router <er_01_0013>.
  • Manual creation: You can select a route table and create a propagation for an attachment in the route table. For details, see Creating a Propagation for an Attachment in the Route Table <er_01_0036>.

An attachment can be propagated to different route tables. You can create propagations for attachments in Figure 1 <er_01_0035__fig16423163124017> as follows:

  • Auto creation: Propagations are automatically created for the attachments, such as VPC 1, VPC 2, and virtual gateway 1 attachments, in the default propagation route table of the enterprise router.
  • Manual creation: You need to manually create propagations in the custom route table of the enterprise router for attachments, such as VPC 1, virtual gateway 1, and virtual gateway 2 attachments.
  • No propagation: If you do not want to use propagated routes, you need to manually add static routes to the custom route table of the enterprise router for attachments, such as VPC 3 and VPC 4 attachments.
Virtual gateway All routes