@alicloud/vpc20160428 7.3.1 → 7.3.2

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
Files changed (67) hide show
  1. package/dist/client.d.ts +132 -130
  2. package/dist/client.js +132 -130
  3. package/dist/client.js.map +1 -1
  4. package/dist/models/AddCommonBandwidthPackageIpRequest.d.ts +4 -4
  5. package/dist/models/CreateCommonBandwidthPackageRequest.d.ts +15 -15
  6. package/dist/models/CreateDhcpOptionsSetRequest.d.ts +7 -7
  7. package/dist/models/CreateFlowLogRequest.d.ts +17 -9
  8. package/dist/models/CreateFlowLogRequest.js.map +1 -1
  9. package/dist/models/CreateRouteEntriesRequest.d.ts +17 -17
  10. package/dist/models/CreateRouteEntriesResponseBody.d.ts +3 -3
  11. package/dist/models/CreateRouteEntryRequest.d.ts +8 -8
  12. package/dist/models/CreateVpnPbrRouteEntryRequest.d.ts +15 -15
  13. package/dist/models/CreateVpnPbrRouteEntryResponseBody.d.ts +3 -3
  14. package/dist/models/CreateVpnRouteEntryRequest.d.ts +7 -7
  15. package/dist/models/CreateVpnRouteEntryResponseBody.d.ts +2 -2
  16. package/dist/models/CreateVswitchCidrReservationRequest.d.ts +11 -11
  17. package/dist/models/DeleteRouteEntriesRequest.d.ts +3 -3
  18. package/dist/models/DeleteRouteEntriesResponseBody.d.ts +3 -3
  19. package/dist/models/DeleteRouteEntryRequest.d.ts +3 -3
  20. package/dist/models/DescribeRouteEntryListRequest.d.ts +6 -6
  21. package/dist/models/DescribeRouteEntryListResponseBody.d.ts +3 -2
  22. package/dist/models/DescribeRouteEntryListResponseBody.js +2 -0
  23. package/dist/models/DescribeRouteEntryListResponseBody.js.map +1 -1
  24. package/dist/models/DescribeVswitchAttributesRequest.d.ts +2 -2
  25. package/dist/models/DescribeVswitchAttributesResponseBody.d.ts +1 -1
  26. package/dist/models/GetDhcpOptionsSetRequest.d.ts +1 -1
  27. package/dist/models/GetDhcpOptionsSetResponseBody.d.ts +1 -1
  28. package/dist/models/GetVpcPrefixListAssociationsResponseBody.d.ts +8 -0
  29. package/dist/models/GetVpcPrefixListAssociationsResponseBody.js +2 -0
  30. package/dist/models/GetVpcPrefixListAssociationsResponseBody.js.map +1 -1
  31. package/dist/models/GetVpcRouteEntrySummaryRequest.d.ts +7 -7
  32. package/dist/models/GetVpcRouteEntrySummaryResponseBody.d.ts +8 -8
  33. package/dist/models/ModifyRouteEntryRequest.d.ts +4 -4
  34. package/dist/models/RemoveCommonBandwidthPackageIpRequest.d.ts +8 -4
  35. package/dist/models/RemoveCommonBandwidthPackageIpRequest.js.map +1 -1
  36. package/dist/models/RetryVpcPrefixListAssociationRequest.d.ts +7 -7
  37. package/dist/models/SwitchActiveRouteTargetRequest.d.ts +3 -3
  38. package/package.json +1 -1
  39. package/src/client.ts +132 -130
  40. package/src/models/AddCommonBandwidthPackageIpRequest.ts +4 -4
  41. package/src/models/CreateCommonBandwidthPackageRequest.ts +15 -15
  42. package/src/models/CreateDhcpOptionsSetRequest.ts +7 -7
  43. package/src/models/CreateFlowLogRequest.ts +17 -9
  44. package/src/models/CreateRouteEntriesRequest.ts +17 -17
  45. package/src/models/CreateRouteEntriesResponseBody.ts +3 -3
  46. package/src/models/CreateRouteEntryRequest.ts +8 -8
  47. package/src/models/CreateVpnPbrRouteEntryRequest.ts +15 -15
  48. package/src/models/CreateVpnPbrRouteEntryResponseBody.ts +3 -3
  49. package/src/models/CreateVpnRouteEntryRequest.ts +7 -7
  50. package/src/models/CreateVpnRouteEntryResponseBody.ts +2 -2
  51. package/src/models/CreateVswitchCidrReservationRequest.ts +11 -11
  52. package/src/models/DeleteRouteEntriesRequest.ts +3 -3
  53. package/src/models/DeleteRouteEntriesResponseBody.ts +3 -3
  54. package/src/models/DeleteRouteEntryRequest.ts +3 -3
  55. package/src/models/DescribeRouteEntryListRequest.ts +6 -6
  56. package/src/models/DescribeRouteEntryListResponseBody.ts +5 -2
  57. package/src/models/DescribeVswitchAttributesRequest.ts +2 -2
  58. package/src/models/DescribeVswitchAttributesResponseBody.ts +1 -1
  59. package/src/models/GetDhcpOptionsSetRequest.ts +1 -1
  60. package/src/models/GetDhcpOptionsSetResponseBody.ts +1 -1
  61. package/src/models/GetVpcPrefixListAssociationsResponseBody.ts +10 -0
  62. package/src/models/GetVpcRouteEntrySummaryRequest.ts +7 -7
  63. package/src/models/GetVpcRouteEntrySummaryResponseBody.ts +8 -8
  64. package/src/models/ModifyRouteEntryRequest.ts +4 -4
  65. package/src/models/RemoveCommonBandwidthPackageIpRequest.ts +8 -4
  66. package/src/models/RetryVpcPrefixListAssociationRequest.ts +7 -7
  67. package/src/models/SwitchActiveRouteTargetRequest.ts +3 -3
package/dist/client.js CHANGED
@@ -293,12 +293,12 @@ class Client extends openapi_core_1.default {
293
293
  * Adds an elastic IP address (EIP) to an Internet Shared Bandwidth instance.
294
294
  *
295
295
  * @remarks
296
- * Before invoking this operation, note the following:
296
+ * Before you invoke this operation, take note of the following items:
297
297
  * - When you invoke this operation to add an EIP to an Internet Shared Bandwidth instance, the EIP must meet the following conditions:
298
- * - The EIP uses the pay-as-you-go billing method.
298
+ * - The billing method of the EIP is pay-as-you-go.
299
299
  * - The EIP is in the same region as the Internet Shared Bandwidth instance.
300
300
  * - The line type of the EIP is the same as that of the Internet Shared Bandwidth instance.
301
- * - The **AddCommonBandwidthPackageIp** operation is asynchronous. After you send a request, the system returns a request ID, but the EIP is not yet added to the Internet Shared Bandwidth instance. The addition task is still running in the background. You can invoke [DescribeCommonBandwidthPackages](https://help.aliyun.com/document_detail/120309.html) to query the association status between the Internet Shared Bandwidth instance and the EIP.
301
+ * - The **AddCommonBandwidthPackageIp** operation is asynchronous. After you send a request, the system returns a request ID. However, the EIP is not yet added to the Internet Shared Bandwidth instance. The addition node is still running in the background. You can invoke [DescribeCommonBandwidthPackages](https://help.aliyun.com/document_detail/120309.html) to query the association status between the Internet Shared Bandwidth instance and the EIP.
302
302
  * - If the association status is **BINDING**, the Internet Shared Bandwidth instance is being associated with the EIP. In this state, you can only execute query operations.
303
303
  * - If the association status is **BINDED**, the Internet Shared Bandwidth instance is associated with the EIP.
304
304
  *
@@ -359,12 +359,12 @@ class Client extends openapi_core_1.default {
359
359
  * Adds an elastic IP address (EIP) to an Internet Shared Bandwidth instance.
360
360
  *
361
361
  * @remarks
362
- * Before invoking this operation, note the following:
362
+ * Before you invoke this operation, take note of the following items:
363
363
  * - When you invoke this operation to add an EIP to an Internet Shared Bandwidth instance, the EIP must meet the following conditions:
364
- * - The EIP uses the pay-as-you-go billing method.
364
+ * - The billing method of the EIP is pay-as-you-go.
365
365
  * - The EIP is in the same region as the Internet Shared Bandwidth instance.
366
366
  * - The line type of the EIP is the same as that of the Internet Shared Bandwidth instance.
367
- * - The **AddCommonBandwidthPackageIp** operation is asynchronous. After you send a request, the system returns a request ID, but the EIP is not yet added to the Internet Shared Bandwidth instance. The addition task is still running in the background. You can invoke [DescribeCommonBandwidthPackages](https://help.aliyun.com/document_detail/120309.html) to query the association status between the Internet Shared Bandwidth instance and the EIP.
367
+ * - The **AddCommonBandwidthPackageIp** operation is asynchronous. After you send a request, the system returns a request ID. However, the EIP is not yet added to the Internet Shared Bandwidth instance. The addition node is still running in the background. You can invoke [DescribeCommonBandwidthPackages](https://help.aliyun.com/document_detail/120309.html) to query the association status between the Internet Shared Bandwidth instance and the EIP.
368
368
  * - If the association status is **BINDING**, the Internet Shared Bandwidth instance is being associated with the EIP. In this state, you can only execute query operations.
369
369
  * - If the association status is **BINDED**, the Internet Shared Bandwidth instance is associated with the EIP.
370
370
  *
@@ -3511,7 +3511,7 @@ class Client extends openapi_core_1.default {
3511
3511
  * @remarks
3512
3512
  * - **CreateDhcpOptionsSet** is an asynchronous operation. After you invoke this operation, the system returns an instance ID but the DHCP options set is not yet created. The background node is still in progress. You can invoke [GetDhcpOptionsSet](https://help.aliyun.com/document_detail/448820.html) to query the creation status of the DHCP options set:
3513
3513
  * - If the vSwitch is in the **Pending** state, the DHCP options set is being configured.
3514
- * - If the vSwitch is in the **Available** state, the DHCP options set is active.
3514
+ * - If the vSwitch is in the **Active** state, the DHCP options set is active.
3515
3515
  *
3516
3516
  * @param request - CreateDhcpOptionsSetRequest
3517
3517
  * @param runtime - runtime options for this request RuntimeOptions
@@ -3587,7 +3587,7 @@ class Client extends openapi_core_1.default {
3587
3587
  * @remarks
3588
3588
  * - **CreateDhcpOptionsSet** is an asynchronous operation. After you invoke this operation, the system returns an instance ID but the DHCP options set is not yet created. The background node is still in progress. You can invoke [GetDhcpOptionsSet](https://help.aliyun.com/document_detail/448820.html) to query the creation status of the DHCP options set:
3589
3589
  * - If the vSwitch is in the **Pending** state, the DHCP options set is being configured.
3590
- * - If the vSwitch is in the **Available** state, the DHCP options set is active.
3590
+ * - If the vSwitch is in the **Active** state, the DHCP options set is active.
3591
3591
  *
3592
3592
  * @param request - CreateDhcpOptionsSetRequest
3593
3593
  * @returns CreateDhcpOptionsSetResponse
@@ -4152,7 +4152,7 @@ class Client extends openapi_core_1.default {
4152
4152
  * Creates a flow log.
4153
4153
  *
4154
4154
  * @remarks
4155
- * *CreateFlowLog** is an asynchronous operation. After you invoke this operation, the system returns an instance ID, but the flow log is not yet created. The creation node is still running in the background. You can invoke [DescribeFlowLogs](https://help.aliyun.com/document_detail/448670.html) to query the creation status of the flow log:
4155
+ * *CreateFlowLog** is an asynchronous operation. After you call this operation, the system returns an instance ID, but the flow log has not been created yet. The creation task is still running in the background. You can call [DescribeFlowLogs](https://help.aliyun.com/document_detail/448670.html) to query the creation status of the flow log:
4156
4156
  * - If the flow log is in the **Activating** state, the flow log is being created.
4157
4157
  * - If the flow log is in the **Active** state, the flow log is created and activated.
4158
4158
  *
@@ -4237,7 +4237,7 @@ class Client extends openapi_core_1.default {
4237
4237
  * Creates a flow log.
4238
4238
  *
4239
4239
  * @remarks
4240
- * *CreateFlowLog** is an asynchronous operation. After you invoke this operation, the system returns an instance ID, but the flow log is not yet created. The creation node is still running in the background. You can invoke [DescribeFlowLogs](https://help.aliyun.com/document_detail/448670.html) to query the creation status of the flow log:
4240
+ * *CreateFlowLog** is an asynchronous operation. After you call this operation, the system returns an instance ID, but the flow log has not been created yet. The creation task is still running in the background. You can call [DescribeFlowLogs](https://help.aliyun.com/document_detail/448670.html) to query the creation status of the flow log:
4241
4241
  * - If the flow log is in the **Activating** state, the flow log is being created.
4242
4242
  * - If the flow log is in the **Active** state, the flow log is created and activated.
4243
4243
  *
@@ -6033,17 +6033,17 @@ class Client extends openapi_core_1.default {
6033
6033
  return await this.createPublicIpAddressPoolWithOptions(request, runtime);
6034
6034
  }
6035
6035
  /**
6036
- * Creates custom route entries in a route table of a VPC vRouter in a batch.
6036
+ * Creates custom route entries in a route table of a vRouter in bulk.
6037
6037
  *
6038
6038
  * @remarks
6039
- * - **CreateRouteEntries** is an asynchronous operation. After you invoke this operation, the system returns an instance ID, but the route has not been created yet. The system continues to run the task in the background. You can invoke [DescribeRouteEntryList](https://help.aliyun.com/document_detail/138148.html) to query the creation status of the route:
6040
- * - If the route is in the **Creating** state, the route is being created.
6041
- * - If the route is in the **Created** state, the route is created.
6042
- * - **CreateRouteEntries** does not support concurrent batch creation of custom route entries in the same VPC.
6043
- * **Before you add custom route entries to a route table of a VPC vRouter, take note of the following items:**
6039
+ * - **CreateRouteEntries** is an asynchronous operation. After you invoke this operation, the system returns an instance ID, but the custom route entry has not been created yet. The system is still running the task in the background. You can invoke [DescribeRouteEntryList](https://help.aliyun.com/document_detail/138148.html) to query the creation status of the custom route entry:
6040
+ * - If the custom route entry is in the **Creating** state, the custom route entry is being created.
6041
+ * - If the custom route entry is in the **Created** state, the custom route entry has been created.
6042
+ * - **CreateRouteEntries** does not support concurrent bulk creation of custom route entries in the same VPC.
6043
+ * **When you use this operation to add custom route entries to a route table of a vRouter, take note of the following items:**
6044
6044
  * - A route table can contain a maximum of 200 custom route entries.
6045
6045
  * - The destination CIDR block (**DstCidrBlock**) of a custom route entry cannot be the same as, contain, or be contained by the CIDR block of a vSwitch in the VPC.
6046
- * - The destination CIDR block (**DstCidrBlock**) of a custom route entry cannot point to or be contained by 100.64.0.0/10.
6046
+ * - The destination CIDR block (**DstCidrBlock**) of a custom route entry cannot point to 100.64.0.0/10 or be contained by 100.64.0.0/10.
6047
6047
  * - The destination CIDR blocks (**DstCidrBlock**) of route entries in the same route table must be unique.
6048
6048
  * - If the specified destination CIDR block (**DstCidrBlock**) is an IP address, the system processes it with a 32-bit mask.
6049
6049
  * - Multiple custom route entries can point to the same next hop (**NextHop**).
@@ -6097,17 +6097,17 @@ class Client extends openapi_core_1.default {
6097
6097
  return $dara.cast(await this.callApi(params, req, runtime), new $_model.CreateRouteEntriesResponse({}));
6098
6098
  }
6099
6099
  /**
6100
- * Creates custom route entries in a route table of a VPC vRouter in a batch.
6100
+ * Creates custom route entries in a route table of a vRouter in bulk.
6101
6101
  *
6102
6102
  * @remarks
6103
- * - **CreateRouteEntries** is an asynchronous operation. After you invoke this operation, the system returns an instance ID, but the route has not been created yet. The system continues to run the task in the background. You can invoke [DescribeRouteEntryList](https://help.aliyun.com/document_detail/138148.html) to query the creation status of the route:
6104
- * - If the route is in the **Creating** state, the route is being created.
6105
- * - If the route is in the **Created** state, the route is created.
6106
- * - **CreateRouteEntries** does not support concurrent batch creation of custom route entries in the same VPC.
6107
- * **Before you add custom route entries to a route table of a VPC vRouter, take note of the following items:**
6103
+ * - **CreateRouteEntries** is an asynchronous operation. After you invoke this operation, the system returns an instance ID, but the custom route entry has not been created yet. The system is still running the task in the background. You can invoke [DescribeRouteEntryList](https://help.aliyun.com/document_detail/138148.html) to query the creation status of the custom route entry:
6104
+ * - If the custom route entry is in the **Creating** state, the custom route entry is being created.
6105
+ * - If the custom route entry is in the **Created** state, the custom route entry has been created.
6106
+ * - **CreateRouteEntries** does not support concurrent bulk creation of custom route entries in the same VPC.
6107
+ * **When you use this operation to add custom route entries to a route table of a vRouter, take note of the following items:**
6108
6108
  * - A route table can contain a maximum of 200 custom route entries.
6109
6109
  * - The destination CIDR block (**DstCidrBlock**) of a custom route entry cannot be the same as, contain, or be contained by the CIDR block of a vSwitch in the VPC.
6110
- * - The destination CIDR block (**DstCidrBlock**) of a custom route entry cannot point to or be contained by 100.64.0.0/10.
6110
+ * - The destination CIDR block (**DstCidrBlock**) of a custom route entry cannot point to 100.64.0.0/10 or be contained by 100.64.0.0/10.
6111
6111
  * - The destination CIDR blocks (**DstCidrBlock**) of route entries in the same route table must be unique.
6112
6112
  * - If the specified destination CIDR block (**DstCidrBlock**) is an IP address, the system processes it with a 32-bit mask.
6113
6113
  * - Multiple custom route entries can point to the same next hop (**NextHop**).
@@ -6124,44 +6124,44 @@ class Client extends openapi_core_1.default {
6124
6124
  * Creates a custom route entry on a vRouter or Virtual Border Router (VBR).
6125
6125
  *
6126
6126
  * @remarks
6127
- * - **CreateRouteEntry** is an asynchronous operation. After you invoke this operation, the system returns an instance ID, but the route has not been created yet. The system is still running the task in the background. You can invoke [DescribeRouteEntryList](https://help.aliyun.com/document_detail/138148.html) to query the route creation status:
6128
- * - If the route is in the **Creating** state, the route is being created.
6129
- * - If the route is in the **Created** state, the route has been created.
6130
- * - **CreateRouteEntry** does not support concurrent creation of custom route entries in the same VPC or the same VBR.
6131
- * - **CreateRouteEntry** may return the **TaskConflict** error code in concurrent scenarios. Retry the operation as needed.
6132
- * **When you use this operation to add a custom route entry to a route table of a vRouter, take note of the following items:**
6133
- * > When the route to be added is a prefix list route, the route quota is calculated based on the sum of existing routes and the maximum number of entries in the prefix list route. The sum cannot exceed the route quota.
6134
- * - A route table can contain up to 200 custom route entries.
6135
- * - The destination CIDR block (**DestinationCidrBlock**) of a custom route entry cannot be the same as a vSwitch CIDR block in the VPC. It can contain a vSwitch CIDR block but cannot be contained by a vSwitch CIDR block.
6136
- * - The destination CIDR block (**DestinationCidrBlock**) of a custom route entry can be a more specific CIDR block than the cloud service system route CIDR block `100.64.0.0/10`, but cannot be the same as this CIDR block.
6127
+ * - The **CreateRouteEntry** operation is asynchronous. After you send a request, the system returns an instance ID while the custom route entry is still being added in the background. You can invoke [DescribeRouteEntryList](https://help.aliyun.com/document_detail/138148.html) to query the status of the custom route entry:
6128
+ * - If the custom route entry is in the **Creating** state, the custom route entry is being added.
6129
+ * - If the custom route entry is in the **Created** state, the custom route entry has been added.
6130
+ * - The **CreateRouteEntry** operation does not support concurrent addition of custom route entries in the same VPC or the same VBR.
6131
+ * - The **CreateRouteEntry** operation may return the **TaskConflict** error code in concurrent scenarios. Retry the request as appropriate.
6132
+ * **When you use this operation to add custom route entries to a route table of a vRouter, take note of the following items:**
6133
+ * > When the route to be added is a prefix list route, the route quota is calculated based on the sum of existing routes and the maximum number of route entries in the prefix list route. The sum cannot exceed the route quota limit.
6134
+ * - A route table can contain a maximum of 200 custom route entries.
6135
+ * - The destination CIDR block (**DestinationCidrBlock**) of a custom route entry cannot be the same as the CIDR block of a vSwitch in the VPC. The destination CIDR block can contain the CIDR block of a vSwitch but cannot be contained by the CIDR block of a vSwitch.
6136
+ * - The destination CIDR block (**DestinationCidrBlock**) of a custom route entry can be a more specific CIDR block than the system route CIDR block `100.64.0.0/10` used by cloud services, but cannot be the same as this CIDR block.
6137
6137
  * <notice>The system route with the destination CIDR block `100.64.0.0/10` is used for communication among cloud services within the VPC. Exercise caution when you configure a more specific route. Incorrect configurations may cause cloud services to become inaccessible.</notice>
6138
- * - The destination CIDR blocks (**DestinationCidrBlock**) of route entries in the same route table must be unique.
6139
- * - If the specified destination CIDR block (**DestinationCidrBlock**) is an IP address, it is treated as a CIDR block with a 32-bit mask.
6138
+ * - Route entries in the same route table cannot have the same destination CIDR block (**DestinationCidrBlock**).
6139
+ * - If the specified destination CIDR block (**DestinationCidrBlock**) is an IP address, the system processes it with a 32-bit mask.
6140
6140
  * - Multiple custom route entries can point to the same next hop (**NextHopId**).
6141
6141
  * - The next hop (**NextHopId**) of a custom route entry must be in the same VPC as the route table.
6142
6142
  * - You can configure ECMP routing by using the **NextHopList** parameter settings:
6143
6143
  * * To add a non-ECMP custom route, specify the **DestinationCidrBlock**, **NextHopType**, and **NextHopId** parameters. Do not specify the **NextHopList** parameter.
6144
6144
  *
6145
6145
  * * To add an ECMP route, specify the **DestinationCidrBlock** and **NextHopList** parameters. Do not specify the **NextHopType** or **NextHopId** parameter.
6146
- * **When you use this operation to add a custom route entry to a route table of a VBR, take note of the following items:**
6147
- * - A route table can contain up to 200 custom route entries.
6146
+ * **When you use this operation to add custom route entries to a route table of a Virtual Border Router (VBR), take note of the following items:**
6147
+ * - A route table can contain a maximum of 200 custom route entries.
6148
6148
  *
6149
6149
  * - The **NextHopList** parameter is not supported.
6150
6150
  *
6151
- * - The destination CIDR block (**DestinationCidrBlock**) of a custom route entry can be a more specific CIDR block than the cloud service system route CIDR block `100.64.0.0/10`, but cannot be the same as this CIDR block.
6151
+ * - The destination CIDR block (**DestinationCidrBlock**) of a custom route entry can be a more specific CIDR block than the system route CIDR block `100.64.0.0/10` used by cloud services, but cannot be the same as this CIDR block.
6152
6152
  * <notice>The system route with the destination CIDR block `100.64.0.0/10` is used for communication among cloud services within the VPC. Exercise caution when you configure a more specific route. Incorrect configurations may cause cloud services to become inaccessible.</notice>
6153
6153
  *
6154
- * - The destination CIDR blocks (**DestinationCidrBlock**) of route entries in the same route table must be unique.
6154
+ * - Route entries in the same route table cannot have the same destination CIDR block (**DestinationCidrBlock**).
6155
6155
  *
6156
- * - If the specified destination CIDR block (**DestinationCidrBlock**) is an IP address, it is treated as a CIDR block with a 32-bit mask.
6156
+ * - If the specified destination CIDR block (**DestinationCidrBlock**) is an IP address, the system processes it with a 32-bit mask.
6157
6157
  *
6158
6158
  * - Multiple custom route entries can point to the same next hop (**NextHopId**).
6159
6159
  *
6160
- * - The next hop (**NextHopId**) of a custom route entry must be a vRouter interface associated with the VBR.
6160
+ * - The next hop (**NextHopId**) of a custom route entry must be the vRouter interface associated with the VBR.
6161
6161
  *
6162
- * - You can create route entries on a VBR only when the VBR is in the **Active** state, the corresponding Express Connect circuit is in the **Enabled** state, and the circuit is not locked due to overdue payment.
6162
+ * - You can add route entries to a VBR only when the VBR is in the **Active** state, the corresponding Express Connect circuit is in the **Enabled** state, and the circuit is not locked due to overdue payment.
6163
6163
  *
6164
- * - Only Normal (non-ECMP) routes are supported. Specify the **DestinationCidrBlock**, **NextHopType**, and **NextHopId** parameters. Do not specify the **NextHopList** parameter.
6164
+ * - Only non-ECMP route entries are supported. Specify the **DestinationCidrBlock**, **NextHopType**, and **NextHopId** parameters. Do not specify the **NextHopList** parameter.
6165
6165
  *
6166
6166
  * @param request - CreateRouteEntryRequest
6167
6167
  * @param runtime - runtime options for this request RuntimeOptions
@@ -6232,44 +6232,44 @@ class Client extends openapi_core_1.default {
6232
6232
  * Creates a custom route entry on a vRouter or Virtual Border Router (VBR).
6233
6233
  *
6234
6234
  * @remarks
6235
- * - **CreateRouteEntry** is an asynchronous operation. After you invoke this operation, the system returns an instance ID, but the route has not been created yet. The system is still running the task in the background. You can invoke [DescribeRouteEntryList](https://help.aliyun.com/document_detail/138148.html) to query the route creation status:
6236
- * - If the route is in the **Creating** state, the route is being created.
6237
- * - If the route is in the **Created** state, the route has been created.
6238
- * - **CreateRouteEntry** does not support concurrent creation of custom route entries in the same VPC or the same VBR.
6239
- * - **CreateRouteEntry** may return the **TaskConflict** error code in concurrent scenarios. Retry the operation as needed.
6240
- * **When you use this operation to add a custom route entry to a route table of a vRouter, take note of the following items:**
6241
- * > When the route to be added is a prefix list route, the route quota is calculated based on the sum of existing routes and the maximum number of entries in the prefix list route. The sum cannot exceed the route quota.
6242
- * - A route table can contain up to 200 custom route entries.
6243
- * - The destination CIDR block (**DestinationCidrBlock**) of a custom route entry cannot be the same as a vSwitch CIDR block in the VPC. It can contain a vSwitch CIDR block but cannot be contained by a vSwitch CIDR block.
6244
- * - The destination CIDR block (**DestinationCidrBlock**) of a custom route entry can be a more specific CIDR block than the cloud service system route CIDR block `100.64.0.0/10`, but cannot be the same as this CIDR block.
6235
+ * - The **CreateRouteEntry** operation is asynchronous. After you send a request, the system returns an instance ID while the custom route entry is still being added in the background. You can invoke [DescribeRouteEntryList](https://help.aliyun.com/document_detail/138148.html) to query the status of the custom route entry:
6236
+ * - If the custom route entry is in the **Creating** state, the custom route entry is being added.
6237
+ * - If the custom route entry is in the **Created** state, the custom route entry has been added.
6238
+ * - The **CreateRouteEntry** operation does not support concurrent addition of custom route entries in the same VPC or the same VBR.
6239
+ * - The **CreateRouteEntry** operation may return the **TaskConflict** error code in concurrent scenarios. Retry the request as appropriate.
6240
+ * **When you use this operation to add custom route entries to a route table of a vRouter, take note of the following items:**
6241
+ * > When the route to be added is a prefix list route, the route quota is calculated based on the sum of existing routes and the maximum number of route entries in the prefix list route. The sum cannot exceed the route quota limit.
6242
+ * - A route table can contain a maximum of 200 custom route entries.
6243
+ * - The destination CIDR block (**DestinationCidrBlock**) of a custom route entry cannot be the same as the CIDR block of a vSwitch in the VPC. The destination CIDR block can contain the CIDR block of a vSwitch but cannot be contained by the CIDR block of a vSwitch.
6244
+ * - The destination CIDR block (**DestinationCidrBlock**) of a custom route entry can be a more specific CIDR block than the system route CIDR block `100.64.0.0/10` used by cloud services, but cannot be the same as this CIDR block.
6245
6245
  * <notice>The system route with the destination CIDR block `100.64.0.0/10` is used for communication among cloud services within the VPC. Exercise caution when you configure a more specific route. Incorrect configurations may cause cloud services to become inaccessible.</notice>
6246
- * - The destination CIDR blocks (**DestinationCidrBlock**) of route entries in the same route table must be unique.
6247
- * - If the specified destination CIDR block (**DestinationCidrBlock**) is an IP address, it is treated as a CIDR block with a 32-bit mask.
6246
+ * - Route entries in the same route table cannot have the same destination CIDR block (**DestinationCidrBlock**).
6247
+ * - If the specified destination CIDR block (**DestinationCidrBlock**) is an IP address, the system processes it with a 32-bit mask.
6248
6248
  * - Multiple custom route entries can point to the same next hop (**NextHopId**).
6249
6249
  * - The next hop (**NextHopId**) of a custom route entry must be in the same VPC as the route table.
6250
6250
  * - You can configure ECMP routing by using the **NextHopList** parameter settings:
6251
6251
  * * To add a non-ECMP custom route, specify the **DestinationCidrBlock**, **NextHopType**, and **NextHopId** parameters. Do not specify the **NextHopList** parameter.
6252
6252
  *
6253
6253
  * * To add an ECMP route, specify the **DestinationCidrBlock** and **NextHopList** parameters. Do not specify the **NextHopType** or **NextHopId** parameter.
6254
- * **When you use this operation to add a custom route entry to a route table of a VBR, take note of the following items:**
6255
- * - A route table can contain up to 200 custom route entries.
6254
+ * **When you use this operation to add custom route entries to a route table of a Virtual Border Router (VBR), take note of the following items:**
6255
+ * - A route table can contain a maximum of 200 custom route entries.
6256
6256
  *
6257
6257
  * - The **NextHopList** parameter is not supported.
6258
6258
  *
6259
- * - The destination CIDR block (**DestinationCidrBlock**) of a custom route entry can be a more specific CIDR block than the cloud service system route CIDR block `100.64.0.0/10`, but cannot be the same as this CIDR block.
6259
+ * - The destination CIDR block (**DestinationCidrBlock**) of a custom route entry can be a more specific CIDR block than the system route CIDR block `100.64.0.0/10` used by cloud services, but cannot be the same as this CIDR block.
6260
6260
  * <notice>The system route with the destination CIDR block `100.64.0.0/10` is used for communication among cloud services within the VPC. Exercise caution when you configure a more specific route. Incorrect configurations may cause cloud services to become inaccessible.</notice>
6261
6261
  *
6262
- * - The destination CIDR blocks (**DestinationCidrBlock**) of route entries in the same route table must be unique.
6262
+ * - Route entries in the same route table cannot have the same destination CIDR block (**DestinationCidrBlock**).
6263
6263
  *
6264
- * - If the specified destination CIDR block (**DestinationCidrBlock**) is an IP address, it is treated as a CIDR block with a 32-bit mask.
6264
+ * - If the specified destination CIDR block (**DestinationCidrBlock**) is an IP address, the system processes it with a 32-bit mask.
6265
6265
  *
6266
6266
  * - Multiple custom route entries can point to the same next hop (**NextHopId**).
6267
6267
  *
6268
- * - The next hop (**NextHopId**) of a custom route entry must be a vRouter interface associated with the VBR.
6268
+ * - The next hop (**NextHopId**) of a custom route entry must be the vRouter interface associated with the VBR.
6269
6269
  *
6270
- * - You can create route entries on a VBR only when the VBR is in the **Active** state, the corresponding Express Connect circuit is in the **Enabled** state, and the circuit is not locked due to overdue payment.
6270
+ * - You can add route entries to a VBR only when the VBR is in the **Active** state, the corresponding Express Connect circuit is in the **Enabled** state, and the circuit is not locked due to overdue payment.
6271
6271
  *
6272
- * - Only Normal (non-ECMP) routes are supported. Specify the **DestinationCidrBlock**, **NextHopType**, and **NextHopId** parameters. Do not specify the **NextHopList** parameter.
6272
+ * - Only non-ECMP route entries are supported. Specify the **DestinationCidrBlock**, **NextHopType**, and **NextHopId** parameters. Do not specify the **NextHopList** parameter.
6273
6273
  *
6274
6274
  * @param request - CreateRouteEntryRequest
6275
6275
  * @returns CreateRouteEntryResponse
@@ -7246,15 +7246,15 @@ class Client extends openapi_core_1.default {
7246
7246
  return await this.createVSwitchWithOptions(request, runtime);
7247
7247
  }
7248
7248
  /**
7249
- * Creates a reserved CIDR block for a vSwitch.
7249
+ * Creates a reserved CIDR block for a vSwitch by calling the CreateVSwitchCidrReservation operation.
7250
7250
  *
7251
7251
  * @remarks
7252
7252
  * When you invoke this operation to create a reserved CIDR block for a vSwitch, take note of the following items:
7253
- * - The maximum number of reserved IPv4 and IPv6 CIDR blocks in a VPC is 100 each.
7253
+ * - The maximum number of reserved IPv4 CIDR blocks and reserved IPv6 CIDR blocks in a VPC is 100 each.
7254
7254
  * - A reserved CIDR block cannot contain the system reserved IP addresses of the vSwitch to which it belongs.
7255
- * - IPv4 CIDR block: The first and last three IP addresses of the vSwitch are system reserved IP addresses.
7256
- * - IPv6 CIDR block: The first and last nine IP addresses of the vSwitch are system reserved IP addresses.
7257
- * - The **CreateVSwitchCidrReservation** operation is asynchronous. After you send a request, the system returns an instance ID, but the reserved CIDR block for a vSwitch has not been created. The background node is still in progress. You can invoke [ListVSwitchCidrReservations](https://help.aliyun.com/document_detail/610155.html) to query the creation status of the reserved CIDR block for a vSwitch:
7255
+ * - IPv4 CIDR block: The first IP address and the last three IP addresses of the vSwitch are system reserved IP addresses.
7256
+ * - IPv6 CIDR block: The first IP address and the last nine IP addresses of the vSwitch are system reserved IP addresses.
7257
+ * - The **CreateVSwitchCidrReservation** operation is asynchronous. After you send a request, the system returns an instance ID, but the reserved CIDR block for a vSwitch has not been created. The system continues to run the background node. You can invoke [ListVSwitchCidrReservations](https://help.aliyun.com/document_detail/610155.html) to query the creation status of the reserved CIDR block for a vSwitch:
7258
7258
  * - If the reserved CIDR block for a vSwitch is in the **Assigning** state, the reserved CIDR block for a vSwitch is being allocated.
7259
7259
  * - If the reserved CIDR block for a vSwitch is in the **Assigned** state, the reserved CIDR block for a vSwitch has been allocated.
7260
7260
  *
@@ -7330,15 +7330,15 @@ class Client extends openapi_core_1.default {
7330
7330
  return $dara.cast(await this.callApi(params, req, runtime), new $_model.CreateVSwitchCidrReservationResponse({}));
7331
7331
  }
7332
7332
  /**
7333
- * Creates a reserved CIDR block for a vSwitch.
7333
+ * Creates a reserved CIDR block for a vSwitch by calling the CreateVSwitchCidrReservation operation.
7334
7334
  *
7335
7335
  * @remarks
7336
7336
  * When you invoke this operation to create a reserved CIDR block for a vSwitch, take note of the following items:
7337
- * - The maximum number of reserved IPv4 and IPv6 CIDR blocks in a VPC is 100 each.
7337
+ * - The maximum number of reserved IPv4 CIDR blocks and reserved IPv6 CIDR blocks in a VPC is 100 each.
7338
7338
  * - A reserved CIDR block cannot contain the system reserved IP addresses of the vSwitch to which it belongs.
7339
- * - IPv4 CIDR block: The first and last three IP addresses of the vSwitch are system reserved IP addresses.
7340
- * - IPv6 CIDR block: The first and last nine IP addresses of the vSwitch are system reserved IP addresses.
7341
- * - The **CreateVSwitchCidrReservation** operation is asynchronous. After you send a request, the system returns an instance ID, but the reserved CIDR block for a vSwitch has not been created. The background node is still in progress. You can invoke [ListVSwitchCidrReservations](https://help.aliyun.com/document_detail/610155.html) to query the creation status of the reserved CIDR block for a vSwitch:
7339
+ * - IPv4 CIDR block: The first IP address and the last three IP addresses of the vSwitch are system reserved IP addresses.
7340
+ * - IPv6 CIDR block: The first IP address and the last nine IP addresses of the vSwitch are system reserved IP addresses.
7341
+ * - The **CreateVSwitchCidrReservation** operation is asynchronous. After you send a request, the system returns an instance ID, but the reserved CIDR block for a vSwitch has not been created. The system continues to run the background node. You can invoke [ListVSwitchCidrReservations](https://help.aliyun.com/document_detail/610155.html) to query the creation status of the reserved CIDR block for a vSwitch:
7342
7342
  * - If the reserved CIDR block for a vSwitch is in the **Assigning** state, the reserved CIDR block for a vSwitch is being allocated.
7343
7343
  * - If the reserved CIDR block for a vSwitch is in the **Assigned** state, the reserved CIDR block for a vSwitch has been allocated.
7344
7344
  *
@@ -8455,9 +8455,10 @@ class Client extends openapi_core_1.default {
8455
8455
  * - Before you create a policy-based route, make sure that you have created an IPsec-VPN connection. For more information, see [CreateVpnConnection](https://help.aliyun.com/document_detail/120391.html).
8456
8456
  * - Before you create a policy-based route, we recommend that you familiarize yourself with the limits and matching rules of policy-based routes. For more information, see [Use policy-based routes](https://help.aliyun.com/document_detail/110777.html).
8457
8457
  * ### Limits
8458
- * - Policy-based routes whose destination CIDR block is 0.0.0.0/0 are not supported.
8459
- * - Do not add policy-based routes whose destination CIDR block is 100.64.0.0/10, a subnet of 100.64.0.0/10, or a CIDR block that contains 100.64.0.0/10. Such policy-based routes may cause the console to fail to display instance status of IPsec-VPN connections or cause IPsec-VPN connection negotiation to be failed.
8460
- * - The **CreateVpnPbrRouteEntry** operation is asynchronous. After you invoke this operation, the system returns the information about the policy-based route, but the routing has not been created. The creation node is still running in the background. You can invoke the [DescribeVpnGateway](https://help.aliyun.com/document_detail/73720.html) operation to query instance status of the VPN gateway instance to determine the creation status of the policy-based route:
8458
+ * - For single-tunnel VPN gateways:
8459
+ * - 0.0.0.0/0 is not supported as the destination CIDR block of a policy-based route.
8460
+ * - CIDR blocks that overlap with 100.64.0.0/10 (including 100.64.0.0/10 itself, its subnets, and parent CIDR blocks that contain it) are not supported as the destination CIDR block of a policy-based route.
8461
+ * - **CreateVpnPbrRouteEntry** is an asynchronous operation. After you send a request, the system returns the policy-based route information, but the route has not been created yet. The system continues to create the route in the background. You can invoke the [DescribeVpnGateway](https://help.aliyun.com/document_detail/73720.html) operation to query the instance status of the VPN gateway to determine the creation status of the policy-based routing node:
8461
8462
  * - If the VPN gateway instance is in the **updating** state, the policy-based route is being created.
8462
8463
  * - If the VPN gateway instance is in the **active** state, the policy-based route is created.
8463
8464
  * - The **CreateVpnPbrRouteEntry** operation does not support concurrent creation of policy-based routes for the same VPN gateway instance.
@@ -8541,9 +8542,10 @@ class Client extends openapi_core_1.default {
8541
8542
  * - Before you create a policy-based route, make sure that you have created an IPsec-VPN connection. For more information, see [CreateVpnConnection](https://help.aliyun.com/document_detail/120391.html).
8542
8543
  * - Before you create a policy-based route, we recommend that you familiarize yourself with the limits and matching rules of policy-based routes. For more information, see [Use policy-based routes](https://help.aliyun.com/document_detail/110777.html).
8543
8544
  * ### Limits
8544
- * - Policy-based routes whose destination CIDR block is 0.0.0.0/0 are not supported.
8545
- * - Do not add policy-based routes whose destination CIDR block is 100.64.0.0/10, a subnet of 100.64.0.0/10, or a CIDR block that contains 100.64.0.0/10. Such policy-based routes may cause the console to fail to display instance status of IPsec-VPN connections or cause IPsec-VPN connection negotiation to be failed.
8546
- * - The **CreateVpnPbrRouteEntry** operation is asynchronous. After you invoke this operation, the system returns the information about the policy-based route, but the routing has not been created. The creation node is still running in the background. You can invoke the [DescribeVpnGateway](https://help.aliyun.com/document_detail/73720.html) operation to query instance status of the VPN gateway instance to determine the creation status of the policy-based route:
8545
+ * - For single-tunnel VPN gateways:
8546
+ * - 0.0.0.0/0 is not supported as the destination CIDR block of a policy-based route.
8547
+ * - CIDR blocks that overlap with 100.64.0.0/10 (including 100.64.0.0/10 itself, its subnets, and parent CIDR blocks that contain it) are not supported as the destination CIDR block of a policy-based route.
8548
+ * - **CreateVpnPbrRouteEntry** is an asynchronous operation. After you send a request, the system returns the policy-based route information, but the route has not been created yet. The system continues to create the route in the background. You can invoke the [DescribeVpnGateway](https://help.aliyun.com/document_detail/73720.html) operation to query the instance status of the VPN gateway to determine the creation status of the policy-based routing node:
8547
8549
  * - If the VPN gateway instance is in the **updating** state, the policy-based route is being created.
8548
8550
  * - If the VPN gateway instance is in the **active** state, the policy-based route is created.
8549
8551
  * - The **CreateVpnPbrRouteEntry** operation does not support concurrent creation of policy-based routes for the same VPN gateway instance.
@@ -8556,16 +8558,16 @@ class Client extends openapi_core_1.default {
8556
8558
  return await this.createVpnPbrRouteEntryWithOptions(request, runtime);
8557
8559
  }
8558
8560
  /**
8559
- * Creates a destination route for a VPN gateway instance by calling the CreateVpnRouteEntry operation. After a destination route is created, the VPN gateway instance matches the destination route based on the destination IP address of the traffic and then forwards the traffic based on the matched destination route.
8561
+ * Creates a destination route for a VPN gateway instance. After the destination route is created, the VPN gateway instance matches the destination route based on the destination IP address of the traffic and then forwards the traffic based on the matched destination route.
8560
8562
  *
8561
8563
  * @remarks
8562
8564
  * ### Before you begin
8563
8565
  * - Before you create a destination route, make sure that you have created an IPsec-VPN connection. For more information, see [CreateVpnConnection](https://help.aliyun.com/document_detail/2526947.html).
8564
8566
  * - Before you create a destination route, we recommend that you understand the matching rules of destination routes. For more information, see [Configure destination routes](https://help.aliyun.com/document_detail/112476.html).
8565
8567
  * ### Limits
8566
- * - Destination routes whose destination CIDR block is 0.0.0.0/0 are not supported.
8567
- * - Do not add destination routes whose destination CIDR block is 100.64.0.0/10, a subnet of 100.64.0.0/10, or a CIDR block that contains 100.64.0.0/10. These routes may cause the console to fail to display the status of IPsec-VPN connections or cause IPsec-VPN connection negotiation to be failed.
8568
- * - The **CreateVpnRouteEntry** operation is asynchronous. After you send a request, the system returns the destination route configuration but the destination route is not yet created. The creation node is still running in the background. You can invoke [DescribeVpnGateway](https://help.aliyun.com/document_detail/73720.html) to query the creation status of the destination route:
8568
+ * - 0.0.0.0/0 is not supported as the destination CIDR block of a destination route.
8569
+ * - For single-tunnel VPN gateways, CIDR blocks that overlap with 100.64.0.0/10 (including 100.64.0.0/10 itself, its subnets, and parent CIDR blocks that contain it) are not supported as the destination CIDR block of a destination route.
8570
+ * - The **CreateVpnRouteEntry** operation is asynchronous. After you send a request, the system returns the destination routing configuration but the destination route is not yet created. The creation node is still running in the background. You can invoke [DescribeVpnGateway](https://help.aliyun.com/document_detail/73720.html) to query the creation status of the destination route:
8569
8571
  * - If the VPN gateway instance is in the **updating** state, the destination route is being created.
8570
8572
  * - If the VPN gateway instance is in the **active** state, the destination route is created.
8571
8573
  * - The **CreateVpnRouteEntry** operation does not support concurrent creation of destination routes for the same VPN gateway.
@@ -8636,16 +8638,16 @@ class Client extends openapi_core_1.default {
8636
8638
  return $dara.cast(await this.callApi(params, req, runtime), new $_model.CreateVpnRouteEntryResponse({}));
8637
8639
  }
8638
8640
  /**
8639
- * Creates a destination route for a VPN gateway instance by calling the CreateVpnRouteEntry operation. After a destination route is created, the VPN gateway instance matches the destination route based on the destination IP address of the traffic and then forwards the traffic based on the matched destination route.
8641
+ * Creates a destination route for a VPN gateway instance. After the destination route is created, the VPN gateway instance matches the destination route based on the destination IP address of the traffic and then forwards the traffic based on the matched destination route.
8640
8642
  *
8641
8643
  * @remarks
8642
8644
  * ### Before you begin
8643
8645
  * - Before you create a destination route, make sure that you have created an IPsec-VPN connection. For more information, see [CreateVpnConnection](https://help.aliyun.com/document_detail/2526947.html).
8644
8646
  * - Before you create a destination route, we recommend that you understand the matching rules of destination routes. For more information, see [Configure destination routes](https://help.aliyun.com/document_detail/112476.html).
8645
8647
  * ### Limits
8646
- * - Destination routes whose destination CIDR block is 0.0.0.0/0 are not supported.
8647
- * - Do not add destination routes whose destination CIDR block is 100.64.0.0/10, a subnet of 100.64.0.0/10, or a CIDR block that contains 100.64.0.0/10. These routes may cause the console to fail to display the status of IPsec-VPN connections or cause IPsec-VPN connection negotiation to be failed.
8648
- * - The **CreateVpnRouteEntry** operation is asynchronous. After you send a request, the system returns the destination route configuration but the destination route is not yet created. The creation node is still running in the background. You can invoke [DescribeVpnGateway](https://help.aliyun.com/document_detail/73720.html) to query the creation status of the destination route:
8648
+ * - 0.0.0.0/0 is not supported as the destination CIDR block of a destination route.
8649
+ * - For single-tunnel VPN gateways, CIDR blocks that overlap with 100.64.0.0/10 (including 100.64.0.0/10 itself, its subnets, and parent CIDR blocks that contain it) are not supported as the destination CIDR block of a destination route.
8650
+ * - The **CreateVpnRouteEntry** operation is asynchronous. After you send a request, the system returns the destination routing configuration but the destination route is not yet created. The creation node is still running in the background. You can invoke [DescribeVpnGateway](https://help.aliyun.com/document_detail/73720.html) to query the creation status of the destination route:
8649
8651
  * - If the VPN gateway instance is in the **updating** state, the destination route is being created.
8650
8652
  * - If the VPN gateway instance is in the **active** state, the destination route is created.
8651
8653
  * - The **CreateVpnRouteEntry** operation does not support concurrent creation of destination routes for the same VPN gateway.
@@ -10932,16 +10934,16 @@ class Client extends openapi_core_1.default {
10932
10934
  return await this.deletePublicIpAddressPoolCidrBlockWithOptions(request, runtime);
10933
10935
  }
10934
10936
  /**
10935
- * Calls DeleteRouteEntries to batch delete custom route entries.
10937
+ * Deletes custom route entries in a batch.
10936
10938
  *
10937
10939
  * @remarks
10938
- * When you call this operation to delete routing entries, note the following items:
10939
- * - Only routing entries in the **Available** state can be deleted.
10940
- * - Routing entries cannot be deleted if the VPC that contains the route table is creating or deleting a vSwitch or routing entry.
10941
- * - The **DeleteRouteEntries** operation is asynchronous. After you send a request, the system returns a request ID, but the routing entry is not yet deleted. The deletion task is still running in the background. You can call [DescribeRouteEntryList](https://help.aliyun.com/document_detail/138148.html) to query the deletion status of the routing entry:
10942
- * - If the routing entry is in the **Deleting** state, the routing entry is being deleted.
10943
- * - If the specified routing entry cannot be found, the routing entry is deleted.
10944
- * - The **DeleteRouteEntries** operation does not support concurrent batch deletion of routing entries in route tables within the same VPC.
10940
+ * When you call this operation to delete route entries, take note of the following items:
10941
+ * - Only route entries in the **Available** state can be deleted.
10942
+ * - Route entries cannot be deleted if the VPC to which the route table belongs has a vSwitch or route entry being created or deleted.
10943
+ * - The **DeleteRouteEntries** operation is asynchronous. After you send a request, the system returns a request ID. However, the route entry is not yet deleted. The deletion task runs in the background. You can call [DescribeRouteEntryList](https://help.aliyun.com/document_detail/138148.html) to query the deletion status of the route entry:
10944
+ * - If the route entry is in the **Deleting** state, the route entry is being deleted.
10945
+ * - If the specified route entry cannot be found, the route entry is deleted.
10946
+ * - The **DeleteRouteEntries** operation does not support concurrent batch deletion of route entries from route tables in the same VPC.
10945
10947
  *
10946
10948
  * @param request - DeleteRouteEntriesRequest
10947
10949
  * @param runtime - runtime options for this request RuntimeOptions
@@ -10991,16 +10993,16 @@ class Client extends openapi_core_1.default {
10991
10993
  return $dara.cast(await this.callApi(params, req, runtime), new $_model.DeleteRouteEntriesResponse({}));
10992
10994
  }
10993
10995
  /**
10994
- * Calls DeleteRouteEntries to batch delete custom route entries.
10996
+ * Deletes custom route entries in a batch.
10995
10997
  *
10996
10998
  * @remarks
10997
- * When you call this operation to delete routing entries, note the following items:
10998
- * - Only routing entries in the **Available** state can be deleted.
10999
- * - Routing entries cannot be deleted if the VPC that contains the route table is creating or deleting a vSwitch or routing entry.
11000
- * - The **DeleteRouteEntries** operation is asynchronous. After you send a request, the system returns a request ID, but the routing entry is not yet deleted. The deletion task is still running in the background. You can call [DescribeRouteEntryList](https://help.aliyun.com/document_detail/138148.html) to query the deletion status of the routing entry:
11001
- * - If the routing entry is in the **Deleting** state, the routing entry is being deleted.
11002
- * - If the specified routing entry cannot be found, the routing entry is deleted.
11003
- * - The **DeleteRouteEntries** operation does not support concurrent batch deletion of routing entries in route tables within the same VPC.
10999
+ * When you call this operation to delete route entries, take note of the following items:
11000
+ * - Only route entries in the **Available** state can be deleted.
11001
+ * - Route entries cannot be deleted if the VPC to which the route table belongs has a vSwitch or route entry being created or deleted.
11002
+ * - The **DeleteRouteEntries** operation is asynchronous. After you send a request, the system returns a request ID. However, the route entry is not yet deleted. The deletion task runs in the background. You can call [DescribeRouteEntryList](https://help.aliyun.com/document_detail/138148.html) to query the deletion status of the route entry:
11003
+ * - If the route entry is in the **Deleting** state, the route entry is being deleted.
11004
+ * - If the specified route entry cannot be found, the route entry is deleted.
11005
+ * - The **DeleteRouteEntries** operation does not support concurrent batch deletion of route entries from route tables in the same VPC.
11004
11006
  *
11005
11007
  * @param request - DeleteRouteEntriesRequest
11006
11008
  * @returns DeleteRouteEntriesResponse
@@ -11010,14 +11012,14 @@ class Client extends openapi_core_1.default {
11010
11012
  return await this.deleteRouteEntriesWithOptions(request, runtime);
11011
11013
  }
11012
11014
  /**
11013
- * Invokes the DeleteRouteEntry operation to delete a route from the route table of a VPC vRouter or Virtual Border Router (VBR).
11015
+ * Invokes the DeleteRouteEntry operation to delete a route from the route table of a vRouter or Virtual Border Router (VBR).
11014
11016
  *
11015
11017
  * @remarks
11016
- * When you call this operation to delete a route, note the following items:
11018
+ * When you call this operation to delete a route, take note of the following items:
11017
11019
  * - Only routes in the **Available** state can be deleted.
11018
- * - A route cannot be deleted if the VPC that contains the route table is creating or deleting a vSwitch or route entry.
11020
+ * - A route cannot be deleted while the VPC that contains the route table is creating or deleting a vSwitch or route.
11019
11021
  * - To delete a route from the route table of a VBR, call the [DescribeRouteEntryList](https://help.aliyun.com/document_detail/138148.html) operation to query the **NextHopId** of the route that you want to delete, and then call this operation to delete the route.
11020
- * - The **DeleteRouteEntry** operation is asynchronous. After you send a request, the system returns a request ID, but the route has not been deleted yet. The deletion task is still running in the background. You can call [DescribeRouteEntryList](https://help.aliyun.com/document_detail/138148.html) to query the deletion status of the route:
11022
+ * - The **DeleteRouteEntry** operation is asynchronous. After you send a request, the system returns a request ID, but the route has not been deleted yet. The deletion task runs in the background. You can call [DescribeRouteEntryList](https://help.aliyun.com/document_detail/138148.html) to query the deletion status of the route:
11021
11023
  * - If the route is in the **Deleting** state, the route is being deleted.
11022
11024
  * - If the specified route cannot be found, the route is deleted.
11023
11025
  * - The **DeleteRouteEntry** operation does not support concurrent deletion of routes from the route table within the same VPC or VBR.
@@ -11079,14 +11081,14 @@ class Client extends openapi_core_1.default {
11079
11081
  return $dara.cast(await this.callApi(params, req, runtime), new $_model.DeleteRouteEntryResponse({}));
11080
11082
  }
11081
11083
  /**
11082
- * Invokes the DeleteRouteEntry operation to delete a route from the route table of a VPC vRouter or Virtual Border Router (VBR).
11084
+ * Invokes the DeleteRouteEntry operation to delete a route from the route table of a vRouter or Virtual Border Router (VBR).
11083
11085
  *
11084
11086
  * @remarks
11085
- * When you call this operation to delete a route, note the following items:
11087
+ * When you call this operation to delete a route, take note of the following items:
11086
11088
  * - Only routes in the **Available** state can be deleted.
11087
- * - A route cannot be deleted if the VPC that contains the route table is creating or deleting a vSwitch or route entry.
11089
+ * - A route cannot be deleted while the VPC that contains the route table is creating or deleting a vSwitch or route.
11088
11090
  * - To delete a route from the route table of a VBR, call the [DescribeRouteEntryList](https://help.aliyun.com/document_detail/138148.html) operation to query the **NextHopId** of the route that you want to delete, and then call this operation to delete the route.
11089
- * - The **DeleteRouteEntry** operation is asynchronous. After you send a request, the system returns a request ID, but the route has not been deleted yet. The deletion task is still running in the background. You can call [DescribeRouteEntryList](https://help.aliyun.com/document_detail/138148.html) to query the deletion status of the route:
11091
+ * - The **DeleteRouteEntry** operation is asynchronous. After you send a request, the system returns a request ID, but the route has not been deleted yet. The deletion task runs in the background. You can call [DescribeRouteEntryList](https://help.aliyun.com/document_detail/138148.html) to query the deletion status of the route:
11090
11092
  * - If the route is in the **Deleting** state, the route is being deleted.
11091
11093
  * - If the specified route cannot be found, the route is deleted.
11092
11094
  * - The **DeleteRouteEntry** operation does not support concurrent deletion of routes from the route table within the same VPC or VBR.
@@ -24096,7 +24098,7 @@ class Client extends openapi_core_1.default {
24096
24098
  return await this.modifyPhysicalConnectionAttributeWithOptions(request, runtime);
24097
24099
  }
24098
24100
  /**
24099
- * Invokes the ModifyRouteEntry operation to modify custom route entry name, description, and route next hop.
24101
+ * Calls the ModifyRouteEntry operation to modify the name, description, and next hop of a custom route entry.
24100
24102
  *
24101
24103
  * @remarks
24102
24104
  * - The **ModifyRouteEntry** operation does not support concurrent modifications to the name and description of the same custom route entry.
@@ -24165,7 +24167,7 @@ class Client extends openapi_core_1.default {
24165
24167
  return $dara.cast(await this.callApi(params, req, runtime), new $_model.ModifyRouteEntryResponse({}));
24166
24168
  }
24167
24169
  /**
24168
- * Invokes the ModifyRouteEntry operation to modify custom route entry name, description, and route next hop.
24170
+ * Calls the ModifyRouteEntry operation to modify the name, description, and next hop of a custom route entry.
24169
24171
  *
24170
24172
  * @remarks
24171
24173
  * - The **ModifyRouteEntry** operation does not support concurrent modifications to the name and description of the same custom route entry.
@@ -27252,17 +27254,17 @@ class Client extends openapi_core_1.default {
27252
27254
  return await this.replaceVpcDhcpOptionsSetWithOptions(request, runtime);
27253
27255
  }
27254
27256
  /**
27255
- * Retries the delivery of the latest prefix list by calling the RetryVpcPrefixListAssociation operation.
27257
+ * Redeploys the latest prefix list by calling the RetryVpcPrefixListAssociation operation.
27256
27258
  *
27257
27259
  * @remarks
27258
- * - After you modify the information of a prefix list instance, if the route table associated with the prefix list instance does not automatically update the prefix list instance information, you can call this operation to redeliver the latest prefix list instance to the associated route table.
27259
- * - The **RetryVpcPrefixListAssociation** operation is asynchronous. After you send a request, the system returns a request ID, but the latest prefix list instance has not been redelivered yet. The redelivery task is still running in the background. You can call [GetVpcPrefixListAssociations](https://help.aliyun.com/document_detail/445478.html) to query the latest delivery status of the prefix list instance:
27260
- * - If the delivery status is **Modifying**, the latest prefix list instance is being redelivered.
27261
- * - If the delivery status is **ModifyFailed**, the latest prefix list instance failed to be redelivered.
27262
- * - If the delivery status is **Created**, the latest prefix list instance is redelivered.
27263
- * - The **RetryVpcPrefixListAssociation** operation does not support concurrent retry delivery of the latest prefix list instance for the same prefix list.
27260
+ * - After you modify the information of a prefix list instance, if the route table associated with the prefix list instance does not automatically update the prefix list instance information, you can call this operation to redeploy the latest prefix list instance to the associated route table.
27261
+ * - The **RetryVpcPrefixListAssociation** operation is asynchronous. After you send a request, the system returns a request ID. However, the latest prefix list instance is not yet redeployed, and the redeployment task is still running in the background. You can call [GetVpcPrefixListAssociations](https://help.aliyun.com/document_detail/445478.html) to query the latest deployment status of the prefix list instance:
27262
+ * - If the deployment status of the prefix list instance is **Modifying**, the latest prefix list instance is being redeployed.
27263
+ * - If the deployment status of the prefix list instance is **ModifyFailed**, the latest prefix list instance failed to be redeployed.
27264
+ * - If the deployment status of the prefix list instance is **Created**, the latest prefix list instance is redeployed.
27265
+ * - The **RetryVpcPrefixListAssociation** operation does not support concurrent retry of redeploying the latest prefix list instance for the same prefix list.
27264
27266
  * ## Scenarios
27265
- * When you modify a prefix list instance, the modification succeeds as long as the CIDR blocks are valid, no conflicting CIDR blocks exist, and the maximum number of entries for the prefix list instance is not exceeded. However, the reference may fail due to issues on the referencing side, such as quota limits or a route conflict with existing routing entries. After you resolve the failed issue on the referencing side, invoke the **RetryVpcPrefixListAssociation** operation to redeliver the latest prefix list instance.
27267
+ * When you modify a prefix list instance, the modification succeeds as long as the CIDR blocks are valid, no conflicting CIDR blocks exist, and the maximum number of entries for the prefix list instance is not exceeded. However, the reference may fail due to issues on the referencing side, such as quota limits or a route conflict with existing routing entries. After you resolve the issue on the referencing side, call the **RetryVpcPrefixListAssociation** operation to redeploy the latest prefix list instance.
27266
27268
  *
27267
27269
  * @param request - RetryVpcPrefixListAssociationRequest
27268
27270
  * @param runtime - runtime options for this request RuntimeOptions
@@ -27318,17 +27320,17 @@ class Client extends openapi_core_1.default {
27318
27320
  return $dara.cast(await this.callApi(params, req, runtime), new $_model.RetryVpcPrefixListAssociationResponse({}));
27319
27321
  }
27320
27322
  /**
27321
- * Retries the delivery of the latest prefix list by calling the RetryVpcPrefixListAssociation operation.
27323
+ * Redeploys the latest prefix list by calling the RetryVpcPrefixListAssociation operation.
27322
27324
  *
27323
27325
  * @remarks
27324
- * - After you modify the information of a prefix list instance, if the route table associated with the prefix list instance does not automatically update the prefix list instance information, you can call this operation to redeliver the latest prefix list instance to the associated route table.
27325
- * - The **RetryVpcPrefixListAssociation** operation is asynchronous. After you send a request, the system returns a request ID, but the latest prefix list instance has not been redelivered yet. The redelivery task is still running in the background. You can call [GetVpcPrefixListAssociations](https://help.aliyun.com/document_detail/445478.html) to query the latest delivery status of the prefix list instance:
27326
- * - If the delivery status is **Modifying**, the latest prefix list instance is being redelivered.
27327
- * - If the delivery status is **ModifyFailed**, the latest prefix list instance failed to be redelivered.
27328
- * - If the delivery status is **Created**, the latest prefix list instance is redelivered.
27329
- * - The **RetryVpcPrefixListAssociation** operation does not support concurrent retry delivery of the latest prefix list instance for the same prefix list.
27326
+ * - After you modify the information of a prefix list instance, if the route table associated with the prefix list instance does not automatically update the prefix list instance information, you can call this operation to redeploy the latest prefix list instance to the associated route table.
27327
+ * - The **RetryVpcPrefixListAssociation** operation is asynchronous. After you send a request, the system returns a request ID. However, the latest prefix list instance is not yet redeployed, and the redeployment task is still running in the background. You can call [GetVpcPrefixListAssociations](https://help.aliyun.com/document_detail/445478.html) to query the latest deployment status of the prefix list instance:
27328
+ * - If the deployment status of the prefix list instance is **Modifying**, the latest prefix list instance is being redeployed.
27329
+ * - If the deployment status of the prefix list instance is **ModifyFailed**, the latest prefix list instance failed to be redeployed.
27330
+ * - If the deployment status of the prefix list instance is **Created**, the latest prefix list instance is redeployed.
27331
+ * - The **RetryVpcPrefixListAssociation** operation does not support concurrent retry of redeploying the latest prefix list instance for the same prefix list.
27330
27332
  * ## Scenarios
27331
- * When you modify a prefix list instance, the modification succeeds as long as the CIDR blocks are valid, no conflicting CIDR blocks exist, and the maximum number of entries for the prefix list instance is not exceeded. However, the reference may fail due to issues on the referencing side, such as quota limits or a route conflict with existing routing entries. After you resolve the failed issue on the referencing side, invoke the **RetryVpcPrefixListAssociation** operation to redeliver the latest prefix list instance.
27333
+ * When you modify a prefix list instance, the modification succeeds as long as the CIDR blocks are valid, no conflicting CIDR blocks exist, and the maximum number of entries for the prefix list instance is not exceeded. However, the reference may fail due to issues on the referencing side, such as quota limits or a route conflict with existing routing entries. After you resolve the issue on the referencing side, call the **RetryVpcPrefixListAssociation** operation to redeploy the latest prefix list instance.
27332
27334
  *
27333
27335
  * @param request - RetryVpcPrefixListAssociationRequest
27334
27336
  * @returns RetryVpcPrefixListAssociationResponse