@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/src/client.ts CHANGED
@@ -287,12 +287,12 @@ export default class Client extends OpenApi {
287
287
  * Adds an elastic IP address (EIP) to an Internet Shared Bandwidth instance.
288
288
  *
289
289
  * @remarks
290
- * Before invoking this operation, note the following:
290
+ * Before you invoke this operation, take note of the following items:
291
291
  * - When you invoke this operation to add an EIP to an Internet Shared Bandwidth instance, the EIP must meet the following conditions:
292
- * - The EIP uses the pay-as-you-go billing method.
292
+ * - The billing method of the EIP is pay-as-you-go.
293
293
  * - The EIP is in the same region as the Internet Shared Bandwidth instance.
294
294
  * - The line type of the EIP is the same as that of the Internet Shared Bandwidth instance.
295
- * - 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.
295
+ * - 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.
296
296
  * - 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.
297
297
  * - If the association status is **BINDED**, the Internet Shared Bandwidth instance is associated with the EIP.
298
298
  *
@@ -364,12 +364,12 @@ export default class Client extends OpenApi {
364
364
  * Adds an elastic IP address (EIP) to an Internet Shared Bandwidth instance.
365
365
  *
366
366
  * @remarks
367
- * Before invoking this operation, note the following:
367
+ * Before you invoke this operation, take note of the following items:
368
368
  * - When you invoke this operation to add an EIP to an Internet Shared Bandwidth instance, the EIP must meet the following conditions:
369
- * - The EIP uses the pay-as-you-go billing method.
369
+ * - The billing method of the EIP is pay-as-you-go.
370
370
  * - The EIP is in the same region as the Internet Shared Bandwidth instance.
371
371
  * - The line type of the EIP is the same as that of the Internet Shared Bandwidth instance.
372
- * - 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.
372
+ * - 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.
373
373
  * - 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.
374
374
  * - If the association status is **BINDED**, the Internet Shared Bandwidth instance is associated with the EIP.
375
375
  *
@@ -4015,7 +4015,7 @@ export default class Client extends OpenApi {
4015
4015
  * @remarks
4016
4016
  * - **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:
4017
4017
  * - If the vSwitch is in the **Pending** state, the DHCP options set is being configured.
4018
- * - If the vSwitch is in the **Available** state, the DHCP options set is active.
4018
+ * - If the vSwitch is in the **Active** state, the DHCP options set is active.
4019
4019
  *
4020
4020
  * @param request - CreateDhcpOptionsSetRequest
4021
4021
  * @param runtime - runtime options for this request RuntimeOptions
@@ -4107,7 +4107,7 @@ export default class Client extends OpenApi {
4107
4107
  * @remarks
4108
4108
  * - **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:
4109
4109
  * - If the vSwitch is in the **Pending** state, the DHCP options set is being configured.
4110
- * - If the vSwitch is in the **Available** state, the DHCP options set is active.
4110
+ * - If the vSwitch is in the **Active** state, the DHCP options set is active.
4111
4111
  *
4112
4112
  * @param request - CreateDhcpOptionsSetRequest
4113
4113
  * @returns CreateDhcpOptionsSetResponse
@@ -4769,7 +4769,7 @@ export default class Client extends OpenApi {
4769
4769
  * Creates a flow log.
4770
4770
  *
4771
4771
  * @remarks
4772
- * *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:
4772
+ * *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:
4773
4773
  * - If the flow log is in the **Activating** state, the flow log is being created.
4774
4774
  * - If the flow log is in the **Active** state, the flow log is created and activated.
4775
4775
  *
@@ -4873,7 +4873,7 @@ export default class Client extends OpenApi {
4873
4873
  * Creates a flow log.
4874
4874
  *
4875
4875
  * @remarks
4876
- * *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:
4876
+ * *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:
4877
4877
  * - If the flow log is in the **Activating** state, the flow log is being created.
4878
4878
  * - If the flow log is in the **Active** state, the flow log is created and activated.
4879
4879
  *
@@ -6994,17 +6994,17 @@ export default class Client extends OpenApi {
6994
6994
  }
6995
6995
 
6996
6996
  /**
6997
- * Creates custom route entries in a route table of a VPC vRouter in a batch.
6997
+ * Creates custom route entries in a route table of a vRouter in bulk.
6998
6998
  *
6999
6999
  * @remarks
7000
- * - **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:
7001
- * - If the route is in the **Creating** state, the route is being created.
7002
- * - If the route is in the **Created** state, the route is created.
7003
- * - **CreateRouteEntries** does not support concurrent batch creation of custom route entries in the same VPC.
7004
- * **Before you add custom route entries to a route table of a VPC vRouter, take note of the following items:**
7000
+ * - **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:
7001
+ * - If the custom route entry is in the **Creating** state, the custom route entry is being created.
7002
+ * - If the custom route entry is in the **Created** state, the custom route entry has been created.
7003
+ * - **CreateRouteEntries** does not support concurrent bulk creation of custom route entries in the same VPC.
7004
+ * **When you use this operation to add custom route entries to a route table of a vRouter, take note of the following items:**
7005
7005
  * - A route table can contain a maximum of 200 custom route entries.
7006
7006
  * - 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.
7007
- * - The destination CIDR block (**DstCidrBlock**) of a custom route entry cannot point to or be contained by 100.64.0.0/10.
7007
+ * - 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.
7008
7008
  * - The destination CIDR blocks (**DstCidrBlock**) of route entries in the same route table must be unique.
7009
7009
  * - If the specified destination CIDR block (**DstCidrBlock**) is an IP address, the system processes it with a 32-bit mask.
7010
7010
  * - Multiple custom route entries can point to the same next hop (**NextHop**).
@@ -7067,17 +7067,17 @@ export default class Client extends OpenApi {
7067
7067
  }
7068
7068
 
7069
7069
  /**
7070
- * Creates custom route entries in a route table of a VPC vRouter in a batch.
7070
+ * Creates custom route entries in a route table of a vRouter in bulk.
7071
7071
  *
7072
7072
  * @remarks
7073
- * - **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:
7074
- * - If the route is in the **Creating** state, the route is being created.
7075
- * - If the route is in the **Created** state, the route is created.
7076
- * - **CreateRouteEntries** does not support concurrent batch creation of custom route entries in the same VPC.
7077
- * **Before you add custom route entries to a route table of a VPC vRouter, take note of the following items:**
7073
+ * - **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:
7074
+ * - If the custom route entry is in the **Creating** state, the custom route entry is being created.
7075
+ * - If the custom route entry is in the **Created** state, the custom route entry has been created.
7076
+ * - **CreateRouteEntries** does not support concurrent bulk creation of custom route entries in the same VPC.
7077
+ * **When you use this operation to add custom route entries to a route table of a vRouter, take note of the following items:**
7078
7078
  * - A route table can contain a maximum of 200 custom route entries.
7079
7079
  * - 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.
7080
- * - The destination CIDR block (**DstCidrBlock**) of a custom route entry cannot point to or be contained by 100.64.0.0/10.
7080
+ * - 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.
7081
7081
  * - The destination CIDR blocks (**DstCidrBlock**) of route entries in the same route table must be unique.
7082
7082
  * - If the specified destination CIDR block (**DstCidrBlock**) is an IP address, the system processes it with a 32-bit mask.
7083
7083
  * - Multiple custom route entries can point to the same next hop (**NextHop**).
@@ -7095,44 +7095,44 @@ export default class Client extends OpenApi {
7095
7095
  * Creates a custom route entry on a vRouter or Virtual Border Router (VBR).
7096
7096
  *
7097
7097
  * @remarks
7098
- * - **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:
7099
- * - If the route is in the **Creating** state, the route is being created.
7100
- * - If the route is in the **Created** state, the route has been created.
7101
- * - **CreateRouteEntry** does not support concurrent creation of custom route entries in the same VPC or the same VBR.
7102
- * - **CreateRouteEntry** may return the **TaskConflict** error code in concurrent scenarios. Retry the operation as needed.
7103
- * **When you use this operation to add a custom route entry to a route table of a vRouter, take note of the following items:**
7104
- * > 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.
7105
- * - A route table can contain up to 200 custom route entries.
7106
- * - 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.
7107
- * - 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.
7098
+ * - 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:
7099
+ * - If the custom route entry is in the **Creating** state, the custom route entry is being added.
7100
+ * - If the custom route entry is in the **Created** state, the custom route entry has been added.
7101
+ * - The **CreateRouteEntry** operation does not support concurrent addition of custom route entries in the same VPC or the same VBR.
7102
+ * - The **CreateRouteEntry** operation may return the **TaskConflict** error code in concurrent scenarios. Retry the request as appropriate.
7103
+ * **When you use this operation to add custom route entries to a route table of a vRouter, take note of the following items:**
7104
+ * > 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.
7105
+ * - A route table can contain a maximum of 200 custom route entries.
7106
+ * - 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.
7107
+ * - 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.
7108
7108
  * <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>
7109
- * - The destination CIDR blocks (**DestinationCidrBlock**) of route entries in the same route table must be unique.
7110
- * - If the specified destination CIDR block (**DestinationCidrBlock**) is an IP address, it is treated as a CIDR block with a 32-bit mask.
7109
+ * - Route entries in the same route table cannot have the same destination CIDR block (**DestinationCidrBlock**).
7110
+ * - If the specified destination CIDR block (**DestinationCidrBlock**) is an IP address, the system processes it with a 32-bit mask.
7111
7111
  * - Multiple custom route entries can point to the same next hop (**NextHopId**).
7112
7112
  * - The next hop (**NextHopId**) of a custom route entry must be in the same VPC as the route table.
7113
7113
  * - You can configure ECMP routing by using the **NextHopList** parameter settings:
7114
7114
  * * To add a non-ECMP custom route, specify the **DestinationCidrBlock**, **NextHopType**, and **NextHopId** parameters. Do not specify the **NextHopList** parameter.
7115
7115
  *
7116
7116
  * * To add an ECMP route, specify the **DestinationCidrBlock** and **NextHopList** parameters. Do not specify the **NextHopType** or **NextHopId** parameter.
7117
- * **When you use this operation to add a custom route entry to a route table of a VBR, take note of the following items:**
7118
- * - A route table can contain up to 200 custom route entries.
7117
+ * **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:**
7118
+ * - A route table can contain a maximum of 200 custom route entries.
7119
7119
  *
7120
7120
  * - The **NextHopList** parameter is not supported.
7121
7121
  *
7122
- * - 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.
7122
+ * - 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.
7123
7123
  * <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>
7124
7124
  *
7125
- * - The destination CIDR blocks (**DestinationCidrBlock**) of route entries in the same route table must be unique.
7125
+ * - Route entries in the same route table cannot have the same destination CIDR block (**DestinationCidrBlock**).
7126
7126
  *
7127
- * - If the specified destination CIDR block (**DestinationCidrBlock**) is an IP address, it is treated as a CIDR block with a 32-bit mask.
7127
+ * - If the specified destination CIDR block (**DestinationCidrBlock**) is an IP address, the system processes it with a 32-bit mask.
7128
7128
  *
7129
7129
  * - Multiple custom route entries can point to the same next hop (**NextHopId**).
7130
7130
  *
7131
- * - The next hop (**NextHopId**) of a custom route entry must be a vRouter interface associated with the VBR.
7131
+ * - The next hop (**NextHopId**) of a custom route entry must be the vRouter interface associated with the VBR.
7132
7132
  *
7133
- * - 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.
7133
+ * - 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.
7134
7134
  *
7135
- * - Only Normal (non-ECMP) routes are supported. Specify the **DestinationCidrBlock**, **NextHopType**, and **NextHopId** parameters. Do not specify the **NextHopList** parameter.
7135
+ * - Only non-ECMP route entries are supported. Specify the **DestinationCidrBlock**, **NextHopType**, and **NextHopId** parameters. Do not specify the **NextHopList** parameter.
7136
7136
  *
7137
7137
  * @param request - CreateRouteEntryRequest
7138
7138
  * @param runtime - runtime options for this request RuntimeOptions
@@ -7218,44 +7218,44 @@ export default class Client extends OpenApi {
7218
7218
  * Creates a custom route entry on a vRouter or Virtual Border Router (VBR).
7219
7219
  *
7220
7220
  * @remarks
7221
- * - **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:
7222
- * - If the route is in the **Creating** state, the route is being created.
7223
- * - If the route is in the **Created** state, the route has been created.
7224
- * - **CreateRouteEntry** does not support concurrent creation of custom route entries in the same VPC or the same VBR.
7225
- * - **CreateRouteEntry** may return the **TaskConflict** error code in concurrent scenarios. Retry the operation as needed.
7226
- * **When you use this operation to add a custom route entry to a route table of a vRouter, take note of the following items:**
7227
- * > 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.
7228
- * - A route table can contain up to 200 custom route entries.
7229
- * - 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.
7230
- * - 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.
7221
+ * - 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:
7222
+ * - If the custom route entry is in the **Creating** state, the custom route entry is being added.
7223
+ * - If the custom route entry is in the **Created** state, the custom route entry has been added.
7224
+ * - The **CreateRouteEntry** operation does not support concurrent addition of custom route entries in the same VPC or the same VBR.
7225
+ * - The **CreateRouteEntry** operation may return the **TaskConflict** error code in concurrent scenarios. Retry the request as appropriate.
7226
+ * **When you use this operation to add custom route entries to a route table of a vRouter, take note of the following items:**
7227
+ * > 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.
7228
+ * - A route table can contain a maximum of 200 custom route entries.
7229
+ * - 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.
7230
+ * - 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.
7231
7231
  * <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>
7232
- * - The destination CIDR blocks (**DestinationCidrBlock**) of route entries in the same route table must be unique.
7233
- * - If the specified destination CIDR block (**DestinationCidrBlock**) is an IP address, it is treated as a CIDR block with a 32-bit mask.
7232
+ * - Route entries in the same route table cannot have the same destination CIDR block (**DestinationCidrBlock**).
7233
+ * - If the specified destination CIDR block (**DestinationCidrBlock**) is an IP address, the system processes it with a 32-bit mask.
7234
7234
  * - Multiple custom route entries can point to the same next hop (**NextHopId**).
7235
7235
  * - The next hop (**NextHopId**) of a custom route entry must be in the same VPC as the route table.
7236
7236
  * - You can configure ECMP routing by using the **NextHopList** parameter settings:
7237
7237
  * * To add a non-ECMP custom route, specify the **DestinationCidrBlock**, **NextHopType**, and **NextHopId** parameters. Do not specify the **NextHopList** parameter.
7238
7238
  *
7239
7239
  * * To add an ECMP route, specify the **DestinationCidrBlock** and **NextHopList** parameters. Do not specify the **NextHopType** or **NextHopId** parameter.
7240
- * **When you use this operation to add a custom route entry to a route table of a VBR, take note of the following items:**
7241
- * - A route table can contain up to 200 custom route entries.
7240
+ * **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:**
7241
+ * - A route table can contain a maximum of 200 custom route entries.
7242
7242
  *
7243
7243
  * - The **NextHopList** parameter is not supported.
7244
7244
  *
7245
- * - 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.
7245
+ * - 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.
7246
7246
  * <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>
7247
7247
  *
7248
- * - The destination CIDR blocks (**DestinationCidrBlock**) of route entries in the same route table must be unique.
7248
+ * - Route entries in the same route table cannot have the same destination CIDR block (**DestinationCidrBlock**).
7249
7249
  *
7250
- * - If the specified destination CIDR block (**DestinationCidrBlock**) is an IP address, it is treated as a CIDR block with a 32-bit mask.
7250
+ * - If the specified destination CIDR block (**DestinationCidrBlock**) is an IP address, the system processes it with a 32-bit mask.
7251
7251
  *
7252
7252
  * - Multiple custom route entries can point to the same next hop (**NextHopId**).
7253
7253
  *
7254
- * - The next hop (**NextHopId**) of a custom route entry must be a vRouter interface associated with the VBR.
7254
+ * - The next hop (**NextHopId**) of a custom route entry must be the vRouter interface associated with the VBR.
7255
7255
  *
7256
- * - 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.
7256
+ * - 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.
7257
7257
  *
7258
- * - Only Normal (non-ECMP) routes are supported. Specify the **DestinationCidrBlock**, **NextHopType**, and **NextHopId** parameters. Do not specify the **NextHopList** parameter.
7258
+ * - Only non-ECMP route entries are supported. Specify the **DestinationCidrBlock**, **NextHopType**, and **NextHopId** parameters. Do not specify the **NextHopList** parameter.
7259
7259
  *
7260
7260
  * @param request - CreateRouteEntryRequest
7261
7261
  * @returns CreateRouteEntryResponse
@@ -8404,15 +8404,15 @@ export default class Client extends OpenApi {
8404
8404
  }
8405
8405
 
8406
8406
  /**
8407
- * Creates a reserved CIDR block for a vSwitch.
8407
+ * Creates a reserved CIDR block for a vSwitch by calling the CreateVSwitchCidrReservation operation.
8408
8408
  *
8409
8409
  * @remarks
8410
8410
  * When you invoke this operation to create a reserved CIDR block for a vSwitch, take note of the following items:
8411
- * - The maximum number of reserved IPv4 and IPv6 CIDR blocks in a VPC is 100 each.
8411
+ * - The maximum number of reserved IPv4 CIDR blocks and reserved IPv6 CIDR blocks in a VPC is 100 each.
8412
8412
  * - A reserved CIDR block cannot contain the system reserved IP addresses of the vSwitch to which it belongs.
8413
- * - IPv4 CIDR block: The first and last three IP addresses of the vSwitch are system reserved IP addresses.
8414
- * - IPv6 CIDR block: The first and last nine IP addresses of the vSwitch are system reserved IP addresses.
8415
- * - 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:
8413
+ * - IPv4 CIDR block: The first IP address and the last three IP addresses of the vSwitch are system reserved IP addresses.
8414
+ * - IPv6 CIDR block: The first IP address and the last nine IP addresses of the vSwitch are system reserved IP addresses.
8415
+ * - 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:
8416
8416
  * - If the reserved CIDR block for a vSwitch is in the **Assigning** state, the reserved CIDR block for a vSwitch is being allocated.
8417
8417
  * - If the reserved CIDR block for a vSwitch is in the **Assigned** state, the reserved CIDR block for a vSwitch has been allocated.
8418
8418
  *
@@ -8505,15 +8505,15 @@ export default class Client extends OpenApi {
8505
8505
  }
8506
8506
 
8507
8507
  /**
8508
- * Creates a reserved CIDR block for a vSwitch.
8508
+ * Creates a reserved CIDR block for a vSwitch by calling the CreateVSwitchCidrReservation operation.
8509
8509
  *
8510
8510
  * @remarks
8511
8511
  * When you invoke this operation to create a reserved CIDR block for a vSwitch, take note of the following items:
8512
- * - The maximum number of reserved IPv4 and IPv6 CIDR blocks in a VPC is 100 each.
8512
+ * - The maximum number of reserved IPv4 CIDR blocks and reserved IPv6 CIDR blocks in a VPC is 100 each.
8513
8513
  * - A reserved CIDR block cannot contain the system reserved IP addresses of the vSwitch to which it belongs.
8514
- * - IPv4 CIDR block: The first and last three IP addresses of the vSwitch are system reserved IP addresses.
8515
- * - IPv6 CIDR block: The first and last nine IP addresses of the vSwitch are system reserved IP addresses.
8516
- * - 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:
8514
+ * - IPv4 CIDR block: The first IP address and the last three IP addresses of the vSwitch are system reserved IP addresses.
8515
+ * - IPv6 CIDR block: The first IP address and the last nine IP addresses of the vSwitch are system reserved IP addresses.
8516
+ * - 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:
8517
8517
  * - If the reserved CIDR block for a vSwitch is in the **Assigning** state, the reserved CIDR block for a vSwitch is being allocated.
8518
8518
  * - If the reserved CIDR block for a vSwitch is in the **Assigned** state, the reserved CIDR block for a vSwitch has been allocated.
8519
8519
  *
@@ -9839,9 +9839,10 @@ export default class Client extends OpenApi {
9839
9839
  * - 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).
9840
9840
  * - 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).
9841
9841
  * ### Limits
9842
- * - Policy-based routes whose destination CIDR block is 0.0.0.0/0 are not supported.
9843
- * - 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.
9844
- * - 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:
9842
+ * - For single-tunnel VPN gateways:
9843
+ * - 0.0.0.0/0 is not supported as the destination CIDR block of a policy-based route.
9844
+ * - 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.
9845
+ * - **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:
9845
9846
  * - If the VPN gateway instance is in the **updating** state, the policy-based route is being created.
9846
9847
  * - If the VPN gateway instance is in the **active** state, the policy-based route is created.
9847
9848
  * - The **CreateVpnPbrRouteEntry** operation does not support concurrent creation of policy-based routes for the same VPN gateway instance.
@@ -9942,9 +9943,10 @@ export default class Client extends OpenApi {
9942
9943
  * - 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).
9943
9944
  * - 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).
9944
9945
  * ### Limits
9945
- * - Policy-based routes whose destination CIDR block is 0.0.0.0/0 are not supported.
9946
- * - 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.
9947
- * - 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:
9946
+ * - For single-tunnel VPN gateways:
9947
+ * - 0.0.0.0/0 is not supported as the destination CIDR block of a policy-based route.
9948
+ * - 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.
9949
+ * - **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:
9948
9950
  * - If the VPN gateway instance is in the **updating** state, the policy-based route is being created.
9949
9951
  * - If the VPN gateway instance is in the **active** state, the policy-based route is created.
9950
9952
  * - The **CreateVpnPbrRouteEntry** operation does not support concurrent creation of policy-based routes for the same VPN gateway instance.
@@ -9958,16 +9960,16 @@ export default class Client extends OpenApi {
9958
9960
  }
9959
9961
 
9960
9962
  /**
9961
- * 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.
9963
+ * 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.
9962
9964
  *
9963
9965
  * @remarks
9964
9966
  * ### Before you begin
9965
9967
  * - 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).
9966
9968
  * - 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).
9967
9969
  * ### Limits
9968
- * - Destination routes whose destination CIDR block is 0.0.0.0/0 are not supported.
9969
- * - 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.
9970
- * - 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:
9970
+ * - 0.0.0.0/0 is not supported as the destination CIDR block of a destination route.
9971
+ * - 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.
9972
+ * - 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:
9971
9973
  * - If the VPN gateway instance is in the **updating** state, the destination route is being created.
9972
9974
  * - If the VPN gateway instance is in the **active** state, the destination route is created.
9973
9975
  * - The **CreateVpnRouteEntry** operation does not support concurrent creation of destination routes for the same VPN gateway.
@@ -10053,16 +10055,16 @@ export default class Client extends OpenApi {
10053
10055
  }
10054
10056
 
10055
10057
  /**
10056
- * 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.
10058
+ * 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.
10057
10059
  *
10058
10060
  * @remarks
10059
10061
  * ### Before you begin
10060
10062
  * - 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).
10061
10063
  * - 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).
10062
10064
  * ### Limits
10063
- * - Destination routes whose destination CIDR block is 0.0.0.0/0 are not supported.
10064
- * - 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.
10065
- * - 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:
10065
+ * - 0.0.0.0/0 is not supported as the destination CIDR block of a destination route.
10066
+ * - 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.
10067
+ * - 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:
10066
10068
  * - If the VPN gateway instance is in the **updating** state, the destination route is being created.
10067
10069
  * - If the VPN gateway instance is in the **active** state, the destination route is created.
10068
10070
  * - The **CreateVpnRouteEntry** operation does not support concurrent creation of destination routes for the same VPN gateway.
@@ -12680,16 +12682,16 @@ export default class Client extends OpenApi {
12680
12682
  }
12681
12683
 
12682
12684
  /**
12683
- * Calls DeleteRouteEntries to batch delete custom route entries.
12685
+ * Deletes custom route entries in a batch.
12684
12686
  *
12685
12687
  * @remarks
12686
- * When you call this operation to delete routing entries, note the following items:
12687
- * - Only routing entries in the **Available** state can be deleted.
12688
- * - Routing entries cannot be deleted if the VPC that contains the route table is creating or deleting a vSwitch or routing entry.
12689
- * - 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:
12690
- * - If the routing entry is in the **Deleting** state, the routing entry is being deleted.
12691
- * - If the specified routing entry cannot be found, the routing entry is deleted.
12692
- * - The **DeleteRouteEntries** operation does not support concurrent batch deletion of routing entries in route tables within the same VPC.
12688
+ * When you call this operation to delete route entries, take note of the following items:
12689
+ * - Only route entries in the **Available** state can be deleted.
12690
+ * - Route entries cannot be deleted if the VPC to which the route table belongs has a vSwitch or route entry being created or deleted.
12691
+ * - 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:
12692
+ * - If the route entry is in the **Deleting** state, the route entry is being deleted.
12693
+ * - If the specified route entry cannot be found, the route entry is deleted.
12694
+ * - The **DeleteRouteEntries** operation does not support concurrent batch deletion of route entries from route tables in the same VPC.
12693
12695
  *
12694
12696
  * @param request - DeleteRouteEntriesRequest
12695
12697
  * @param runtime - runtime options for this request RuntimeOptions
@@ -12748,16 +12750,16 @@ export default class Client extends OpenApi {
12748
12750
  }
12749
12751
 
12750
12752
  /**
12751
- * Calls DeleteRouteEntries to batch delete custom route entries.
12753
+ * Deletes custom route entries in a batch.
12752
12754
  *
12753
12755
  * @remarks
12754
- * When you call this operation to delete routing entries, note the following items:
12755
- * - Only routing entries in the **Available** state can be deleted.
12756
- * - Routing entries cannot be deleted if the VPC that contains the route table is creating or deleting a vSwitch or routing entry.
12757
- * - 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:
12758
- * - If the routing entry is in the **Deleting** state, the routing entry is being deleted.
12759
- * - If the specified routing entry cannot be found, the routing entry is deleted.
12760
- * - The **DeleteRouteEntries** operation does not support concurrent batch deletion of routing entries in route tables within the same VPC.
12756
+ * When you call this operation to delete route entries, take note of the following items:
12757
+ * - Only route entries in the **Available** state can be deleted.
12758
+ * - Route entries cannot be deleted if the VPC to which the route table belongs has a vSwitch or route entry being created or deleted.
12759
+ * - 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:
12760
+ * - If the route entry is in the **Deleting** state, the route entry is being deleted.
12761
+ * - If the specified route entry cannot be found, the route entry is deleted.
12762
+ * - The **DeleteRouteEntries** operation does not support concurrent batch deletion of route entries from route tables in the same VPC.
12761
12763
  *
12762
12764
  * @param request - DeleteRouteEntriesRequest
12763
12765
  * @returns DeleteRouteEntriesResponse
@@ -12768,14 +12770,14 @@ export default class Client extends OpenApi {
12768
12770
  }
12769
12771
 
12770
12772
  /**
12771
- * Invokes the DeleteRouteEntry operation to delete a route from the route table of a VPC vRouter or Virtual Border Router (VBR).
12773
+ * Invokes the DeleteRouteEntry operation to delete a route from the route table of a vRouter or Virtual Border Router (VBR).
12772
12774
  *
12773
12775
  * @remarks
12774
- * When you call this operation to delete a route, note the following items:
12776
+ * When you call this operation to delete a route, take note of the following items:
12775
12777
  * - Only routes in the **Available** state can be deleted.
12776
- * - A route cannot be deleted if the VPC that contains the route table is creating or deleting a vSwitch or route entry.
12778
+ * - A route cannot be deleted while the VPC that contains the route table is creating or deleting a vSwitch or route.
12777
12779
  * - 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.
12778
- * - 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:
12780
+ * - 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:
12779
12781
  * - If the route is in the **Deleting** state, the route is being deleted.
12780
12782
  * - If the specified route cannot be found, the route is deleted.
12781
12783
  * - The **DeleteRouteEntry** operation does not support concurrent deletion of routes from the route table within the same VPC or VBR.
@@ -12849,14 +12851,14 @@ export default class Client extends OpenApi {
12849
12851
  }
12850
12852
 
12851
12853
  /**
12852
- * Invokes the DeleteRouteEntry operation to delete a route from the route table of a VPC vRouter or Virtual Border Router (VBR).
12854
+ * Invokes the DeleteRouteEntry operation to delete a route from the route table of a vRouter or Virtual Border Router (VBR).
12853
12855
  *
12854
12856
  * @remarks
12855
- * When you call this operation to delete a route, note the following items:
12857
+ * When you call this operation to delete a route, take note of the following items:
12856
12858
  * - Only routes in the **Available** state can be deleted.
12857
- * - A route cannot be deleted if the VPC that contains the route table is creating or deleting a vSwitch or route entry.
12859
+ * - A route cannot be deleted while the VPC that contains the route table is creating or deleting a vSwitch or route.
12858
12860
  * - 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.
12859
- * - 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:
12861
+ * - 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:
12860
12862
  * - If the route is in the **Deleting** state, the route is being deleted.
12861
12863
  * - If the specified route cannot be found, the route is deleted.
12862
12864
  * - The **DeleteRouteEntry** operation does not support concurrent deletion of routes from the route table within the same VPC or VBR.
@@ -28075,7 +28077,7 @@ export default class Client extends OpenApi {
28075
28077
  }
28076
28078
 
28077
28079
  /**
28078
- * Invokes the ModifyRouteEntry operation to modify custom route entry name, description, and route next hop.
28080
+ * Calls the ModifyRouteEntry operation to modify the name, description, and next hop of a custom route entry.
28079
28081
  *
28080
28082
  * @remarks
28081
28083
  * - The **ModifyRouteEntry** operation does not support concurrent modifications to the name and description of the same custom route entry.
@@ -28158,7 +28160,7 @@ export default class Client extends OpenApi {
28158
28160
  }
28159
28161
 
28160
28162
  /**
28161
- * Invokes the ModifyRouteEntry operation to modify custom route entry name, description, and route next hop.
28163
+ * Calls the ModifyRouteEntry operation to modify the name, description, and next hop of a custom route entry.
28162
28164
  *
28163
28165
  * @remarks
28164
28166
  * - The **ModifyRouteEntry** operation does not support concurrent modifications to the name and description of the same custom route entry.
@@ -31757,17 +31759,17 @@ export default class Client extends OpenApi {
31757
31759
  }
31758
31760
 
31759
31761
  /**
31760
- * Retries the delivery of the latest prefix list by calling the RetryVpcPrefixListAssociation operation.
31762
+ * Redeploys the latest prefix list by calling the RetryVpcPrefixListAssociation operation.
31761
31763
  *
31762
31764
  * @remarks
31763
- * - 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.
31764
- * - 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:
31765
- * - If the delivery status is **Modifying**, the latest prefix list instance is being redelivered.
31766
- * - If the delivery status is **ModifyFailed**, the latest prefix list instance failed to be redelivered.
31767
- * - If the delivery status is **Created**, the latest prefix list instance is redelivered.
31768
- * - The **RetryVpcPrefixListAssociation** operation does not support concurrent retry delivery of the latest prefix list instance for the same prefix list.
31765
+ * - 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.
31766
+ * - 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:
31767
+ * - If the deployment status of the prefix list instance is **Modifying**, the latest prefix list instance is being redeployed.
31768
+ * - If the deployment status of the prefix list instance is **ModifyFailed**, the latest prefix list instance failed to be redeployed.
31769
+ * - If the deployment status of the prefix list instance is **Created**, the latest prefix list instance is redeployed.
31770
+ * - The **RetryVpcPrefixListAssociation** operation does not support concurrent retry of redeploying the latest prefix list instance for the same prefix list.
31769
31771
  * ## Scenarios
31770
- * 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.
31772
+ * 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.
31771
31773
  *
31772
31774
  * @param request - RetryVpcPrefixListAssociationRequest
31773
31775
  * @param runtime - runtime options for this request RuntimeOptions
@@ -31834,17 +31836,17 @@ export default class Client extends OpenApi {
31834
31836
  }
31835
31837
 
31836
31838
  /**
31837
- * Retries the delivery of the latest prefix list by calling the RetryVpcPrefixListAssociation operation.
31839
+ * Redeploys the latest prefix list by calling the RetryVpcPrefixListAssociation operation.
31838
31840
  *
31839
31841
  * @remarks
31840
- * - 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.
31841
- * - 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:
31842
- * - If the delivery status is **Modifying**, the latest prefix list instance is being redelivered.
31843
- * - If the delivery status is **ModifyFailed**, the latest prefix list instance failed to be redelivered.
31844
- * - If the delivery status is **Created**, the latest prefix list instance is redelivered.
31845
- * - The **RetryVpcPrefixListAssociation** operation does not support concurrent retry delivery of the latest prefix list instance for the same prefix list.
31842
+ * - 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.
31843
+ * - 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:
31844
+ * - If the deployment status of the prefix list instance is **Modifying**, the latest prefix list instance is being redeployed.
31845
+ * - If the deployment status of the prefix list instance is **ModifyFailed**, the latest prefix list instance failed to be redeployed.
31846
+ * - If the deployment status of the prefix list instance is **Created**, the latest prefix list instance is redeployed.
31847
+ * - The **RetryVpcPrefixListAssociation** operation does not support concurrent retry of redeploying the latest prefix list instance for the same prefix list.
31846
31848
  * ## Scenarios
31847
- * 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.
31849
+ * 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.
31848
31850
  *
31849
31851
  * @param request - RetryVpcPrefixListAssociationRequest
31850
31852
  * @returns RetryVpcPrefixListAssociationResponse