ModifyCenRouteMap

The operation that you want to perform. Set the value to ModifyCenRouteMap.

The ID of the Cloud Enterprise Network (CEN) instance.

The region where the CEN instance is deployed. You can call the DescribeRegions operation to query region IDs.

The behavior after all conditions are matched. Valid values:

• Permit: Allows the routes that are matched.
• Deny: Rejects the routes that are matched.

The priority of the route map. Valid values: 1 to 100. A lower number indicates a higher priority.

The ID of the route map.

The priority of the next associated route map. Valid values: 1 to 100.

• If the priority is not set, no next route map is associated with the current route map.
• If the priority is set to 1, the next route map is associated with the current route map.
• If the priority is set and the value is not 1. The priority of the associated route map must be higher than that of the current route map.

Only when the MapResult parameter is set to Permit, the matched routes continue to match the next associated route maps.

The description of the route map.

Match statements are used to match source region IDs of the routes. You can enter at most 32 region IDs.

Match statements are used to match source instance IDs of the routes.

You can enter instance IDs of the following types: virtual private cloud (VPC), virtual border router (VBR), Cloud Connect Network (CCN) in mainland China, Smart Access Gateway (SAG). You can enter at most 32 instance IDs.

The IDs of source instances to be advertised do not support match statements. Valid values:

• false (default value): If the source instance ID is in the SourceInstanceIds field, the match is successful.
• true: If the source instance ID is not in the SourceInstanceIds field, the match is successful.

Match statements are used to match the destination instance IDs.

You can enter instance IDs of the following types: VPC, VBR, CCN in mainland China, and SAG. You can enter at most 32 instance IDs.

The IDs of destination instances to be advertised do not support match statements. Valid values:

• false(default value): If the ID of the destination instance to be advertised is in the DestinationInstanceIds field, the match is successful.
• true: If the ID of the destination instance to be advertised is not in the DestinationInstanceIds filed, the match is successful.

Match statements are used to match source route table IDs of the routes. You can enter at most 32 route table IDs.

Match statements are used to match the IDs of the destination route tables. You can enter at most 32 route table IDs.

Match statements are used to match source instance types of the routes. Valid values:

• VPC: VPCs.
• VBR: VBRs.
• CCN: CCN instances in mainland China.

Match statements are used to match the destination instance types. Valid values:

• VPC: VPCs.
• VBR: VBRs.
• CCN: CCN instances in mainland China.

Match statements are used to match the routing prefixes. The CIDR format is used. You can enter at most 32 CIDR blocks.

Match statements are used to match the prefixes. Valid values:

• Include: uses fuzzy match. If the routing prefix in the condition contains the routing prefix of the route, the match is successful.

  For example, the 1.1.0.0/16 policy can match the 1.1.1.0/24 route.

• Complete: uses exact match. Only when the routing prefix in the condition is the same as the routing prefix of the route, the match is successful.

  For example, the 1.1.0.0/16 policy can match the 1.1.0.0/16 route.

Match statements are used to match the route types. Valid values:

• System: system routes that are generated by the system.
• Custom: custom routes that are created by users.
• BGP: Border Gateway Protocol (BGP) routes that are advertised to BGP.

You can enter multiple types.

Match statements are used to match AS paths of the routes. An AS path is a mandatory attribute, which describes the AS number through which a BGP route passes when the BGP route is advertised.

Only the AS-SEQUENCE parameter is supported. The AS-SET, AS-CONFED-SEQUENCE, and AS-CONFED-SET parameters are not supported. Specifically, only the AS number list is supported. Sets and sub-lists are not supported.

Match statements are used to match the AS paths. Valid values:

• Include: uses fuzzy match. If the AS path in the condition overlaps with the AS path in the route, the match is successful.
• Complete: uses exact match. Only when the AS path in the condition is the same as the AS path in the route, the match is successful.

Match statements are used to match the Communities. Enter each Community in the format of nn:nn. Valid values of nn: 1 to 65535. You can enter at most 32 Communities. Each Community must comply with RFC 1997. RFC 8092 is not supported.

Match statements are used to match the Communities. Valid values:

• Include: uses fuzzy match. If the Community in the condition overlaps with the Community of the route, the match is successful.
• Complete: uses exact match. Only when the Community in the condition is the same as the Community of the route, the match is successful.

Action statements are used to operate the Communities. Valid values:

• Additive: adds.
• Replace: replaces.

Action statements are used to operate the Communities. Valid values: Enter each Community in the format of nn:nn. Valid values of nn: 1 to 65535. You can enter at most 32 Communities. Each Community must comply with RFC 1997. RFC 8092 is not supported.

Action statements are used to modify route priorities. Valid values: 1 to 100. Default value: 50. A smaller number indicates a higher priority.

AS paths are attached when regional gateways receive or advertise routes.

For route maps that are applied in different directions, the requirements for AS paths to be attached are different:

• For the inbound direction: You must specify the list of source instance IDs and the source region in the condition to be matched. The source region must be the same as the region where the route map is applied.
• For the outbound direction: You must specify the list of destination instance IDs in the condition to be matched.