All Products
Search

This Product

    Cloud Enterprise Network:CreateTransitRouteTableAggregation

    Document Center

    Cloud Enterprise Network:CreateTransitRouteTableAggregation

    Last Updated:Mar 25, 2024

    Creates an aggregate route.

    Operation description

    After you add an aggregate route to a route table of an Enterprise Edition transit router, the Enterprise Edition transit router advertises its routes only to route tables of virtual private clouds (VPCs) that are associated with a route table of the Enterprise Edition transit router and have route synchronization enabled.

    Perform the following operations before you create an aggregate route. Otherwise, the Enterprise Edition transit router does not advertise routes to VPC route tables:

    Debugging

    OpenAPI Explorer automatically calculates the signature value. For your convenience, we recommend that you call this operation in OpenAPI Explorer.

    Authorization information

    The following table shows the authorization information corresponding to the API. The authorization information can be used in the Action policy element to grant a RAM user or RAM role the permissions to call this API operation. Description:

    • Operation: the value that you can use in the Action element to specify the operation on a resource.
    • Access level: the access level of each operation. The levels are read, write, and list.
    • Resource type: the type of the resource on which you can authorize the RAM user or the RAM role to perform the operation. Take note of the following items:
      • The required resource types are displayed in bold characters.
      • If the permissions cannot be granted at the resource level, All Resources is used in the Resource type column of the operation.
    • Condition Key: the condition key that is defined by the cloud service.
    • Associated operation: other operations that the RAM user or the RAM role must have permissions to perform to complete the operation. To complete the operation, the RAM user or the RAM role must have the permissions to perform the associated operations.
    OperationAccess levelResource typeCondition keyAssociated operation
    cen:CreateTransitRouteTableAggregationWrite
    • All Resources
      *
      none
    		none

    Request parameters

    ParameterTypeRequiredDescriptionExample
    TransitRouteTableIdstringYes

    The ID of the route table of the Enterprise Edition transit router.

    		vtb-iq8qgruq1ry8jc7vt****
    TransitRouteTableAggregationNamestringNo

    The name of the aggregate route.

    The name must be 1 to 128 characters in length, and can contain letters, digits, and the following special characters: , . ; / @ _ -. You can also leave the name empty.

    		nametest
    TransitRouteTableAggregationCidrstringYes

    The destination CIDR block of the aggregate route.

    Note The following CIDR blocks are not supported:
  • CIDR blocks that start with 0 or 100.64.
  • Multicast CIDR blocks, including 224.0.0.1 to 239.255.255.254.
    •
    		192.168.10.0/24
    TransitRouteTableAggregationScopestringYes

    The scope of networks that you want to advertise the aggregate route.

    Set the value to VPC, which specified that the aggregate route is advertised to VPCs that are in associated forwarding relationship with a route table of the Enterprise Edition transit router and have route synchronization enabled.

    		VPC
    TransitRouteTableAggregationDescriptionstringNo

    The description of the aggregate route.

    The description must be 0 to 256 characters in length, and can contain letters, digits, and the following special characters: , . ; / @ _ -.

    		desctest
    ClientTokenstringNo

    The client token that is used to ensure the idempotence of the request.

    You can use the client to generate the token, but you must make sure that the token is unique among different requests. The token can contain only ASCII characters.

    Note If you do not set this parameter, ClientToken is set to the value of RequestId. The value of RequestId for each API request may be different.
    		02fb3da4-130e-11e9-8e44-001****
    DryRunbooleanNo

    Specifies whether to perform a dry run. Valid values:

    • false (default): performs a dry run and sends the request.
    • true: performs a dry run. The system checks the required parameters and request syntax. If the request fails the dry run, an error message is returned. If the request passes the dry run, the DryRunOperation error code is returned.
    		false

    Response parameters

    ParameterTypeDescriptionExample
    object

    The response.

    RequestIdstring

    The ID of the request.

    		0C2EE7A8-74D4-4081-8236-CEBDE3BBCF50

    Examples

    Sample success responses

    JSONformat

    {
  "RequestId": "0C2EE7A8-74D4-4081-8236-CEBDE3BBCF50"
}

    Error codes

    HTTP status codeError codeError messageDescription
    400InvalidOperation.RegionNotSupportThe Operation is not Support in this region.The error message returned because this operation is not supported in the specified region.
    400InstanceExist.AggregationRouteThis aggregation route is already created.The error message returned because the aggregated route already exists.
    400InstanceNotExist.TransitRouteTableThe transitRouter route table is not exist.The error message returned because the specified transit router route table does not exist.
    400IncorrectStatus.TransitRouteTableThe transitRouter route table is not in a valid state for the operation.The error message returned because the status of the transit router route table does not support this operation. Try again later.
    400QuotaExceeded.AggregationRouteThe aggregation route count is over limit.The error message returned because the number of aggregated routes has reached the upper limit.
    400InstanceNotExist.TransitRouterThe aggregation route is not exist.The error message returned because the specified transit router does not exist.
    400OperationUnsupported.TransitRouterTypeThe operation is not supported because of the wrong transitRouter type.The error message returned because this operation is not supported by the specified type of transit router.
    400IncorrectStatus.TransitRouterThe status of transitRouter is invalid.The error message returned because the status of the transit router does not support this operation. Try again later.
    400OperationUnsupported.ServiceModeThe operation is not supported because of the wrong transitRouter service mode.The error message returned because the transit router mode does not support this operation.
    400InvalidCidrBlockThe cidr block is invalid.The error message returned because the specified CIDR block is invalid.
    400RouteConflictThe specified route already exists.The specified route already exists.
    400InvalidOperation.InstanceNotSupportIPv6RouteThe cen dose not support Ipv6 route.-
    400IllegalParam.TransitRouteTableAggregationCidrThe param TransitRouteTableAggregationCidr is illegal.-
    400InvalidParameterInvalid parameter.The error message returned because the parameter is set to an invalid value.
    400UnauthorizedThe AccessKeyId is unauthorized.The error message returned because you do not have the permissions to perform this operation.

    For a list of error codes, visit the Service error codes.

    Change history

    Change timeSummary of changesOperation
    2024-01-18The Error code has changedsee changesets
    Change itemChange content
    Error CodesThe Error code has changed.
      delete Error Codes: 400
    2023-03-21The Error code has changedsee changesets
    Change itemChange content
    Error CodesThe Error code has changed.
      Error Codes 400 change