Cloud Enterprise Network:ModifyCenRouteMap

The ID of the CEN instance.

The ID of the region in which the routing policy is applied.

You can call the DescribeChildInstanceRegions operation to query the most recent region list.

The ID of the routing policy.

The description of the routing policy.

The description cannot start with http:// or https://. It must start with a letter and can contain letters, digits, hyphens (-), periods (.), and underscores (_).

The action to be performed on a route that meets all match conditions. Valid values:

• Permit: the route is permitted.
• Deny: the route is denied.

The priority of the routing policy that you want to associate with the current one.

• This parameter takes effect only when the MapResult parameter is set to Permit. This way, the permitted route is matched against the next routing policy.
• The region and direction of the routing policy to be associated must be the same as those of the current routing policy.
• The priority of the routing policy to be associated must be lower than the priority of the current routing policy.

The match method that is used to match routes against the prefix list. Valid values:

• Include: fuzzy match. A route is a match if the route prefix is included in the match conditions.

  For example, if you set the match condition to 10.10.0.0/16 and fuzzy match is enabled, the route whose prefix is 10.10.1.0/24 is a match.

• Complete: exact match. A route is a match only if the route prefix is the same as the prefix specified in the match condition.

  For example, if you set the match condition to 10.10.0.0/16 and exact match is enabled, a route is a match only if the prefix is 10.10.0.0/16.

The match method that is used to match routes against the AS paths. Valid values:

• Include: fuzzy match. A route meets the match condition if the AS path of the route overlaps with the AS paths specified in the match condition.
• Complete: exact match. A route is a match only if the AS path of the route is the same as an AS path specified in the match condition.

The match method that is sed to match routes based on the community. Valid values:

• Include: fuzzy match. A route meets the match condition if the community of the route overlaps with the community specified in the match condition.
• Complete: exact match. A route meets the match condition only if the community of the route is the same as the community specified in the match condition.

The action that is performed on the community. Valid values:

• Additive: adds the community to the route.
• Replace: replaces the original community of the route.

This parameter specifies the action to be performed when a route meets the match condition.

The new priority of the route.

Valid values: 1 to 100. The default priority is 50. A smaller value indicates a higher priority.

This parameter specifies the action to be performed when a route meets the match condition.

The priority of the routing policy. Valid values: 1 to 100. A smaller value indicates a higher priority.

Specifies whether to exclude the source network instance IDs. Valid values:

• false (default value): A route is a match if its source network instance ID is in the list specified by SourceInstanceIds.N.
• true: A route is a match if its source network instance ID is not in the list specified by SourceInstanceIds.N.

Specifies whether to exclude the destination network instance IDs. Valid values:

• false (default value): A route is a match if its destination network instance ID is in the list specified by DestinationInstanceIds.N.
• true: A route meets the match condition if its destination network instance ID is not in the list specified by DestinationInstanceIds.N.

The type of IP address in the match condition. Valid values:

• IPv4: IPv4 address
• IPv6: IPv6 address

This parameter can be empty. If no value is specified, all types of IP address are a match.

The IDs of the source network instances to which the routes belong. The following network instance types are supported:

• Virtual private cloud (VPC)
• Virtual border router (VBR)
• Cloud Connect Network (CCN) instance
• Smart Access Gateway (SAG) instance
• The ID of the IPsec-VPN connection.

You can enter at most 32 IDs.

The IDs of the destination network instances to which the routes belong. The following network instance types are supported:

• VPC
• VBR
• CCN instance
• SAG instance
• The ID of the IPsec-VPN connection.

You can enter at most 32 IDs.

The IDs of the source route tables to which the routes belong. You can enter at most 32 route table IDs.

The IDs of the destination route tables to which the routes belong. You can enter at most 32 route table IDs.

The IDs of the source regions to which the routes belong. You can enter at most 32 region IDs.

You can call the DescribeChildInstanceRegions operation to query the most recent region list.

The types of source network instance to which the routes belong. The following types of network instances are supported:

• VPC: VPC

• VBR: VBR

• CCN: CCN instance

• VPN :VPN gateway or IPsec-VPN connection

  • If the IPsec-VPN connection or SSL client is associated with a VPN gateway, the VPC associated with the VPN gateway must be connected to a transit router, and the VPN gateway must use Border Gateway Protocol (BGP) dynamic routing. Otherwise, this parameter cannot take effect.
  • This parameter takes effect if the IPsec connection is directly connected to a transit router.

The types of destination network instance to which the routes belong. The following types of network instances are supported:

• VPC: VPC

• VBR: VBR

• CCN: CCN instance

• VPN: IPsec connection

  Note This parameter does not take effect if the IPsec-VPN connection or SSL client is associated with a transit router through a VPN gateway and a VPC. This parameter takes effect only if the IPsec connection is directly connected to the transit router.

The destination network instance types are valid only if the routing policy is applied to scenarios where routes are advertised from the gateway in the current region to network instances in the current region.

The prefix list against which routes are matched.

You must specify the IP addresses in CIDR notation. You can enter at most 32 CIDR blocks.

The type of route to be matched against the match condition. The following route types are supported:

• System: system routes that are automatically generated by the system.
• Custom: custom routes that are manually added.
• BGP: routes that are advertised over BGP.

The AS paths against which routes are matched.

The community against which routes are matched.

Specify the community in the format of n:m. Valid values of n and m: 1 to 65535. Each community must comply with the RFC 1997 standard. The RFC 8092 standard that defines BGP large communities is not supported.

You can specify at most 32 communities.

The community set on which actions are performed.

Specify the community in the format of n:m. Valid values of n and m: 1 to 65535. Each community must comply with RFC 1997. The RFC 8092 standard that defines BGP large communities is not supported.

You can specify at most 32 communities.

The AS paths that are prepended by using an action statement when regional gateways receive or advertise routes.

The AS paths vary based on the direction in which the routing policy is applied:

• If AS paths are prepended to a routing policy that is applied in the inbound direction, you must specify source network instance IDs and the source region in the match condition. In addition, the source region must be the same as the region where the routing policy is applied.
• If AS paths are prepended to a routing policy that is applied in the outbound direction, you must specify destination network instance IDs in the match condition.

This parameter specifies the action to be performed when a route meets the match condition.