@alicloud/vpc20160428 7.3.0 → 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 (82) hide show
  1. package/dist/client.d.ts +144 -142
  2. package/dist/client.js +153 -178
  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/CreateRouteTargetGroupRequest.d.ts +5 -6
  13. package/dist/models/CreateRouteTargetGroupRequest.js.map +1 -1
  14. package/dist/models/CreateVpnPbrRouteEntryRequest.d.ts +15 -15
  15. package/dist/models/CreateVpnPbrRouteEntryResponseBody.d.ts +3 -3
  16. package/dist/models/CreateVpnRouteEntryRequest.d.ts +7 -7
  17. package/dist/models/CreateVpnRouteEntryResponseBody.d.ts +2 -2
  18. package/dist/models/CreateVswitchCidrReservationRequest.d.ts +11 -11
  19. package/dist/models/CreateVswitchRequest.d.ts +26 -9
  20. package/dist/models/CreateVswitchRequest.js +4 -0
  21. package/dist/models/CreateVswitchRequest.js.map +1 -1
  22. package/dist/models/DeleteRouteEntriesRequest.d.ts +3 -3
  23. package/dist/models/DeleteRouteEntriesResponseBody.d.ts +3 -3
  24. package/dist/models/DeleteRouteEntryRequest.d.ts +3 -3
  25. package/dist/models/DescribeRouteEntryListRequest.d.ts +6 -6
  26. package/dist/models/DescribeRouteEntryListResponseBody.d.ts +3 -2
  27. package/dist/models/DescribeRouteEntryListResponseBody.js +2 -0
  28. package/dist/models/DescribeRouteEntryListResponseBody.js.map +1 -1
  29. package/dist/models/DescribeVswitchAttributesRequest.d.ts +2 -2
  30. package/dist/models/DescribeVswitchAttributesResponseBody.d.ts +1 -1
  31. package/dist/models/GetDhcpOptionsSetRequest.d.ts +1 -1
  32. package/dist/models/GetDhcpOptionsSetResponseBody.d.ts +1 -1
  33. package/dist/models/GetVpcPrefixListAssociationsRequest.d.ts +3 -3
  34. package/dist/models/GetVpcPrefixListAssociationsResponseBody.d.ts +17 -9
  35. package/dist/models/GetVpcPrefixListAssociationsResponseBody.js +2 -0
  36. package/dist/models/GetVpcPrefixListAssociationsResponseBody.js.map +1 -1
  37. package/dist/models/GetVpcRouteEntrySummaryRequest.d.ts +7 -7
  38. package/dist/models/GetVpcRouteEntrySummaryResponseBody.d.ts +8 -8
  39. package/dist/models/ModifyRouteEntryRequest.d.ts +4 -4
  40. package/dist/models/ModifyVswitchAttributeRequest.d.ts +13 -3
  41. package/dist/models/ModifyVswitchAttributeRequest.js +2 -0
  42. package/dist/models/ModifyVswitchAttributeRequest.js.map +1 -1
  43. package/dist/models/RemoveCommonBandwidthPackageIpRequest.d.ts +8 -4
  44. package/dist/models/RemoveCommonBandwidthPackageIpRequest.js.map +1 -1
  45. package/dist/models/RetryVpcPrefixListAssociationRequest.d.ts +7 -7
  46. package/dist/models/SwitchActiveRouteTargetRequest.d.ts +3 -3
  47. package/dist/models/UpdateDhcpOptionsSetAttributeRequest.d.ts +10 -10
  48. package/package.json +1 -1
  49. package/src/client.ts +156 -178
  50. package/src/models/AddCommonBandwidthPackageIpRequest.ts +4 -4
  51. package/src/models/CreateCommonBandwidthPackageRequest.ts +15 -15
  52. package/src/models/CreateDhcpOptionsSetRequest.ts +7 -7
  53. package/src/models/CreateFlowLogRequest.ts +17 -9
  54. package/src/models/CreateRouteEntriesRequest.ts +17 -17
  55. package/src/models/CreateRouteEntriesResponseBody.ts +3 -3
  56. package/src/models/CreateRouteEntryRequest.ts +8 -8
  57. package/src/models/CreateRouteTargetGroupRequest.ts +5 -6
  58. package/src/models/CreateVpnPbrRouteEntryRequest.ts +15 -15
  59. package/src/models/CreateVpnPbrRouteEntryResponseBody.ts +3 -3
  60. package/src/models/CreateVpnRouteEntryRequest.ts +7 -7
  61. package/src/models/CreateVpnRouteEntryResponseBody.ts +2 -2
  62. package/src/models/CreateVswitchCidrReservationRequest.ts +11 -11
  63. package/src/models/CreateVswitchRequest.ts +30 -9
  64. package/src/models/DeleteRouteEntriesRequest.ts +3 -3
  65. package/src/models/DeleteRouteEntriesResponseBody.ts +3 -3
  66. package/src/models/DeleteRouteEntryRequest.ts +3 -3
  67. package/src/models/DescribeRouteEntryListRequest.ts +6 -6
  68. package/src/models/DescribeRouteEntryListResponseBody.ts +5 -2
  69. package/src/models/DescribeVswitchAttributesRequest.ts +2 -2
  70. package/src/models/DescribeVswitchAttributesResponseBody.ts +1 -1
  71. package/src/models/GetDhcpOptionsSetRequest.ts +1 -1
  72. package/src/models/GetDhcpOptionsSetResponseBody.ts +1 -1
  73. package/src/models/GetVpcPrefixListAssociationsRequest.ts +3 -3
  74. package/src/models/GetVpcPrefixListAssociationsResponseBody.ts +19 -9
  75. package/src/models/GetVpcRouteEntrySummaryRequest.ts +7 -7
  76. package/src/models/GetVpcRouteEntrySummaryResponseBody.ts +8 -8
  77. package/src/models/ModifyRouteEntryRequest.ts +4 -4
  78. package/src/models/ModifyVswitchAttributeRequest.ts +15 -3
  79. package/src/models/RemoveCommonBandwidthPackageIpRequest.ts +8 -4
  80. package/src/models/RetryVpcPrefixListAssociationRequest.ts +7 -7
  81. package/src/models/SwitchActiveRouteTargetRequest.ts +3 -3
  82. package/src/models/UpdateDhcpOptionsSetAttributeRequest.ts +10 -10
package/dist/client.d.ts CHANGED
@@ -79,12 +79,12 @@ export default class Client extends OpenApi {
79
79
  * Adds an elastic IP address (EIP) to an Internet Shared Bandwidth instance.
80
80
  *
81
81
  * @remarks
82
- * Before invoking this operation, note the following:
82
+ * Before you invoke this operation, take note of the following items:
83
83
  * - When you invoke this operation to add an EIP to an Internet Shared Bandwidth instance, the EIP must meet the following conditions:
84
- * - The EIP uses the pay-as-you-go billing method.
84
+ * - The billing method of the EIP is pay-as-you-go.
85
85
  * - The EIP is in the same region as the Internet Shared Bandwidth instance.
86
86
  * - The line type of the EIP is the same as that of the Internet Shared Bandwidth instance.
87
- * - 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.
87
+ * - 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.
88
88
  * - 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.
89
89
  * - If the association status is **BINDED**, the Internet Shared Bandwidth instance is associated with the EIP.
90
90
  *
@@ -97,12 +97,12 @@ export default class Client extends OpenApi {
97
97
  * Adds an elastic IP address (EIP) to an Internet Shared Bandwidth instance.
98
98
  *
99
99
  * @remarks
100
- * Before invoking this operation, note the following:
100
+ * Before you invoke this operation, take note of the following items:
101
101
  * - When you invoke this operation to add an EIP to an Internet Shared Bandwidth instance, the EIP must meet the following conditions:
102
- * - The EIP uses the pay-as-you-go billing method.
102
+ * - The billing method of the EIP is pay-as-you-go.
103
103
  * - The EIP is in the same region as the Internet Shared Bandwidth instance.
104
104
  * - The line type of the EIP is the same as that of the Internet Shared Bandwidth instance.
105
- * - 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.
105
+ * - 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.
106
106
  * - 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.
107
107
  * - If the association status is **BINDED**, the Internet Shared Bandwidth instance is associated with the EIP.
108
108
  *
@@ -1150,7 +1150,7 @@ export default class Client extends OpenApi {
1150
1150
  * @remarks
1151
1151
  * - **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:
1152
1152
  * - If the vSwitch is in the **Pending** state, the DHCP options set is being configured.
1153
- * - If the vSwitch is in the **Available** state, the DHCP options set is active.
1153
+ * - If the vSwitch is in the **Active** state, the DHCP options set is active.
1154
1154
  *
1155
1155
  * @param request - CreateDhcpOptionsSetRequest
1156
1156
  * @param runtime - runtime options for this request RuntimeOptions
@@ -1163,7 +1163,7 @@ export default class Client extends OpenApi {
1163
1163
  * @remarks
1164
1164
  * - **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:
1165
1165
  * - If the vSwitch is in the **Pending** state, the DHCP options set is being configured.
1166
- * - If the vSwitch is in the **Available** state, the DHCP options set is active.
1166
+ * - If the vSwitch is in the **Active** state, the DHCP options set is active.
1167
1167
  *
1168
1168
  * @param request - CreateDhcpOptionsSetRequest
1169
1169
  * @returns CreateDhcpOptionsSetResponse
@@ -1347,7 +1347,7 @@ export default class Client extends OpenApi {
1347
1347
  * Creates a flow log.
1348
1348
  *
1349
1349
  * @remarks
1350
- * *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:
1350
+ * *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:
1351
1351
  * - If the flow log is in the **Activating** state, the flow log is being created.
1352
1352
  * - If the flow log is in the **Active** state, the flow log is created and activated.
1353
1353
  *
@@ -1360,7 +1360,7 @@ export default class Client extends OpenApi {
1360
1360
  * Creates a flow log.
1361
1361
  *
1362
1362
  * @remarks
1363
- * *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:
1363
+ * *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:
1364
1364
  * - If the flow log is in the **Activating** state, the flow log is being created.
1365
1365
  * - If the flow log is in the **Active** state, the flow log is created and activated.
1366
1366
  *
@@ -1875,17 +1875,17 @@ export default class Client extends OpenApi {
1875
1875
  */
1876
1876
  createPublicIpAddressPool(request: $_model.CreatePublicIpAddressPoolRequest): Promise<$_model.CreatePublicIpAddressPoolResponse>;
1877
1877
  /**
1878
- * Creates custom route entries in a route table of a VPC vRouter in a batch.
1878
+ * Creates custom route entries in a route table of a vRouter in bulk.
1879
1879
  *
1880
1880
  * @remarks
1881
- * - **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:
1882
- * - If the route is in the **Creating** state, the route is being created.
1883
- * - If the route is in the **Created** state, the route is created.
1884
- * - **CreateRouteEntries** does not support concurrent batch creation of custom route entries in the same VPC.
1885
- * **Before you add custom route entries to a route table of a VPC vRouter, take note of the following items:**
1881
+ * - **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:
1882
+ * - If the custom route entry is in the **Creating** state, the custom route entry is being created.
1883
+ * - If the custom route entry is in the **Created** state, the custom route entry has been created.
1884
+ * - **CreateRouteEntries** does not support concurrent bulk creation of custom route entries in the same VPC.
1885
+ * **When you use this operation to add custom route entries to a route table of a vRouter, take note of the following items:**
1886
1886
  * - A route table can contain a maximum of 200 custom route entries.
1887
1887
  * - 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.
1888
- * - The destination CIDR block (**DstCidrBlock**) of a custom route entry cannot point to or be contained by 100.64.0.0/10.
1888
+ * - 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.
1889
1889
  * - The destination CIDR blocks (**DstCidrBlock**) of route entries in the same route table must be unique.
1890
1890
  * - If the specified destination CIDR block (**DstCidrBlock**) is an IP address, the system processes it with a 32-bit mask.
1891
1891
  * - Multiple custom route entries can point to the same next hop (**NextHop**).
@@ -1897,17 +1897,17 @@ export default class Client extends OpenApi {
1897
1897
  */
1898
1898
  createRouteEntriesWithOptions(request: $_model.CreateRouteEntriesRequest, runtime: $dara.RuntimeOptions): Promise<$_model.CreateRouteEntriesResponse>;
1899
1899
  /**
1900
- * Creates custom route entries in a route table of a VPC vRouter in a batch.
1900
+ * Creates custom route entries in a route table of a vRouter in bulk.
1901
1901
  *
1902
1902
  * @remarks
1903
- * - **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:
1904
- * - If the route is in the **Creating** state, the route is being created.
1905
- * - If the route is in the **Created** state, the route is created.
1906
- * - **CreateRouteEntries** does not support concurrent batch creation of custom route entries in the same VPC.
1907
- * **Before you add custom route entries to a route table of a VPC vRouter, take note of the following items:**
1903
+ * - **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:
1904
+ * - If the custom route entry is in the **Creating** state, the custom route entry is being created.
1905
+ * - If the custom route entry is in the **Created** state, the custom route entry has been created.
1906
+ * - **CreateRouteEntries** does not support concurrent bulk creation of custom route entries in the same VPC.
1907
+ * **When you use this operation to add custom route entries to a route table of a vRouter, take note of the following items:**
1908
1908
  * - A route table can contain a maximum of 200 custom route entries.
1909
1909
  * - 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.
1910
- * - The destination CIDR block (**DstCidrBlock**) of a custom route entry cannot point to or be contained by 100.64.0.0/10.
1910
+ * - 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.
1911
1911
  * - The destination CIDR blocks (**DstCidrBlock**) of route entries in the same route table must be unique.
1912
1912
  * - If the specified destination CIDR block (**DstCidrBlock**) is an IP address, the system processes it with a 32-bit mask.
1913
1913
  * - Multiple custom route entries can point to the same next hop (**NextHop**).
@@ -1921,44 +1921,44 @@ export default class Client extends OpenApi {
1921
1921
  * Creates a custom route entry on a vRouter or Virtual Border Router (VBR).
1922
1922
  *
1923
1923
  * @remarks
1924
- * - **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:
1925
- * - If the route is in the **Creating** state, the route is being created.
1926
- * - If the route is in the **Created** state, the route has been created.
1927
- * - **CreateRouteEntry** does not support concurrent creation of custom route entries in the same VPC or the same VBR.
1928
- * - **CreateRouteEntry** may return the **TaskConflict** error code in concurrent scenarios. Retry the operation as needed.
1929
- * **When you use this operation to add a custom route entry to a route table of a vRouter, take note of the following items:**
1930
- * > 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.
1931
- * - A route table can contain up to 200 custom route entries.
1932
- * - 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.
1933
- * - 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.
1924
+ * - 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:
1925
+ * - If the custom route entry is in the **Creating** state, the custom route entry is being added.
1926
+ * - If the custom route entry is in the **Created** state, the custom route entry has been added.
1927
+ * - The **CreateRouteEntry** operation does not support concurrent addition of custom route entries in the same VPC or the same VBR.
1928
+ * - The **CreateRouteEntry** operation may return the **TaskConflict** error code in concurrent scenarios. Retry the request as appropriate.
1929
+ * **When you use this operation to add custom route entries to a route table of a vRouter, take note of the following items:**
1930
+ * > 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.
1931
+ * - A route table can contain a maximum of 200 custom route entries.
1932
+ * - 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.
1933
+ * - 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.
1934
1934
  * <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>
1935
- * - The destination CIDR blocks (**DestinationCidrBlock**) of route entries in the same route table must be unique.
1936
- * - If the specified destination CIDR block (**DestinationCidrBlock**) is an IP address, it is treated as a CIDR block with a 32-bit mask.
1935
+ * - Route entries in the same route table cannot have the same destination CIDR block (**DestinationCidrBlock**).
1936
+ * - If the specified destination CIDR block (**DestinationCidrBlock**) is an IP address, the system processes it with a 32-bit mask.
1937
1937
  * - Multiple custom route entries can point to the same next hop (**NextHopId**).
1938
1938
  * - The next hop (**NextHopId**) of a custom route entry must be in the same VPC as the route table.
1939
1939
  * - You can configure ECMP routing by using the **NextHopList** parameter settings:
1940
1940
  * * To add a non-ECMP custom route, specify the **DestinationCidrBlock**, **NextHopType**, and **NextHopId** parameters. Do not specify the **NextHopList** parameter.
1941
1941
  *
1942
1942
  * * To add an ECMP route, specify the **DestinationCidrBlock** and **NextHopList** parameters. Do not specify the **NextHopType** or **NextHopId** parameter.
1943
- * **When you use this operation to add a custom route entry to a route table of a VBR, take note of the following items:**
1944
- * - A route table can contain up to 200 custom route entries.
1943
+ * **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:**
1944
+ * - A route table can contain a maximum of 200 custom route entries.
1945
1945
  *
1946
1946
  * - The **NextHopList** parameter is not supported.
1947
1947
  *
1948
- * - 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.
1948
+ * - 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.
1949
1949
  * <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>
1950
1950
  *
1951
- * - The destination CIDR blocks (**DestinationCidrBlock**) of route entries in the same route table must be unique.
1951
+ * - Route entries in the same route table cannot have the same destination CIDR block (**DestinationCidrBlock**).
1952
1952
  *
1953
- * - If the specified destination CIDR block (**DestinationCidrBlock**) is an IP address, it is treated as a CIDR block with a 32-bit mask.
1953
+ * - If the specified destination CIDR block (**DestinationCidrBlock**) is an IP address, the system processes it with a 32-bit mask.
1954
1954
  *
1955
1955
  * - Multiple custom route entries can point to the same next hop (**NextHopId**).
1956
1956
  *
1957
- * - The next hop (**NextHopId**) of a custom route entry must be a vRouter interface associated with the VBR.
1957
+ * - The next hop (**NextHopId**) of a custom route entry must be the vRouter interface associated with the VBR.
1958
1958
  *
1959
- * - 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.
1959
+ * - 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.
1960
1960
  *
1961
- * - Only Normal (non-ECMP) routes are supported. Specify the **DestinationCidrBlock**, **NextHopType**, and **NextHopId** parameters. Do not specify the **NextHopList** parameter.
1961
+ * - Only non-ECMP route entries are supported. Specify the **DestinationCidrBlock**, **NextHopType**, and **NextHopId** parameters. Do not specify the **NextHopList** parameter.
1962
1962
  *
1963
1963
  * @param request - CreateRouteEntryRequest
1964
1964
  * @param runtime - runtime options for this request RuntimeOptions
@@ -1969,44 +1969,44 @@ export default class Client extends OpenApi {
1969
1969
  * Creates a custom route entry on a vRouter or Virtual Border Router (VBR).
1970
1970
  *
1971
1971
  * @remarks
1972
- * - **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:
1973
- * - If the route is in the **Creating** state, the route is being created.
1974
- * - If the route is in the **Created** state, the route has been created.
1975
- * - **CreateRouteEntry** does not support concurrent creation of custom route entries in the same VPC or the same VBR.
1976
- * - **CreateRouteEntry** may return the **TaskConflict** error code in concurrent scenarios. Retry the operation as needed.
1977
- * **When you use this operation to add a custom route entry to a route table of a vRouter, take note of the following items:**
1978
- * > 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.
1979
- * - A route table can contain up to 200 custom route entries.
1980
- * - 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.
1981
- * - 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.
1972
+ * - 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:
1973
+ * - If the custom route entry is in the **Creating** state, the custom route entry is being added.
1974
+ * - If the custom route entry is in the **Created** state, the custom route entry has been added.
1975
+ * - The **CreateRouteEntry** operation does not support concurrent addition of custom route entries in the same VPC or the same VBR.
1976
+ * - The **CreateRouteEntry** operation may return the **TaskConflict** error code in concurrent scenarios. Retry the request as appropriate.
1977
+ * **When you use this operation to add custom route entries to a route table of a vRouter, take note of the following items:**
1978
+ * > 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.
1979
+ * - A route table can contain a maximum of 200 custom route entries.
1980
+ * - 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.
1981
+ * - 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.
1982
1982
  * <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>
1983
- * - The destination CIDR blocks (**DestinationCidrBlock**) of route entries in the same route table must be unique.
1984
- * - If the specified destination CIDR block (**DestinationCidrBlock**) is an IP address, it is treated as a CIDR block with a 32-bit mask.
1983
+ * - Route entries in the same route table cannot have the same destination CIDR block (**DestinationCidrBlock**).
1984
+ * - If the specified destination CIDR block (**DestinationCidrBlock**) is an IP address, the system processes it with a 32-bit mask.
1985
1985
  * - Multiple custom route entries can point to the same next hop (**NextHopId**).
1986
1986
  * - The next hop (**NextHopId**) of a custom route entry must be in the same VPC as the route table.
1987
1987
  * - You can configure ECMP routing by using the **NextHopList** parameter settings:
1988
1988
  * * To add a non-ECMP custom route, specify the **DestinationCidrBlock**, **NextHopType**, and **NextHopId** parameters. Do not specify the **NextHopList** parameter.
1989
1989
  *
1990
1990
  * * To add an ECMP route, specify the **DestinationCidrBlock** and **NextHopList** parameters. Do not specify the **NextHopType** or **NextHopId** parameter.
1991
- * **When you use this operation to add a custom route entry to a route table of a VBR, take note of the following items:**
1992
- * - A route table can contain up to 200 custom route entries.
1991
+ * **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:**
1992
+ * - A route table can contain a maximum of 200 custom route entries.
1993
1993
  *
1994
1994
  * - The **NextHopList** parameter is not supported.
1995
1995
  *
1996
- * - 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.
1996
+ * - 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.
1997
1997
  * <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>
1998
1998
  *
1999
- * - The destination CIDR blocks (**DestinationCidrBlock**) of route entries in the same route table must be unique.
1999
+ * - Route entries in the same route table cannot have the same destination CIDR block (**DestinationCidrBlock**).
2000
2000
  *
2001
- * - If the specified destination CIDR block (**DestinationCidrBlock**) is an IP address, it is treated as a CIDR block with a 32-bit mask.
2001
+ * - If the specified destination CIDR block (**DestinationCidrBlock**) is an IP address, the system processes it with a 32-bit mask.
2002
2002
  *
2003
2003
  * - Multiple custom route entries can point to the same next hop (**NextHopId**).
2004
2004
  *
2005
- * - The next hop (**NextHopId**) of a custom route entry must be a vRouter interface associated with the VBR.
2005
+ * - The next hop (**NextHopId**) of a custom route entry must be the vRouter interface associated with the VBR.
2006
2006
  *
2007
- * - 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.
2007
+ * - 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.
2008
2008
  *
2009
- * - Only Normal (non-ECMP) routes are supported. Specify the **DestinationCidrBlock**, **NextHopType**, and **NextHopId** parameters. Do not specify the **NextHopList** parameter.
2009
+ * - Only non-ECMP route entries are supported. Specify the **DestinationCidrBlock**, **NextHopType**, and **NextHopId** parameters. Do not specify the **NextHopList** parameter.
2010
2010
  *
2011
2011
  * @param request - CreateRouteEntryRequest
2012
2012
  * @returns CreateRouteEntryResponse
@@ -2043,12 +2043,12 @@ export default class Client extends OpenApi {
2043
2043
  * Creates a route target group instance.
2044
2044
  *
2045
2045
  * @remarks
2046
- * - **CreateRouteTargetGroup** is an asynchronous operation. After you invoke this operation, the system returns an instance ID, but the routing target group instance is not yet created. The creation node continues in the background. You can invoke **ListRouteTargetGroup** to query the creation status of the routing target group:
2046
+ * - **CreateRouteTargetGroup** is an asynchronous operation. After you invoke this operation, the system returns an instance ID, but the routing target group instance is not yet created. The creation task continues in the background. You can invoke **ListRouteTargetGroup** to query the creation status of the routing target group:
2047
2047
  * - If the routing target group is in the **Pending** state, the routing target group is being created.
2048
2048
  * - If the routing target group is in the **Available**, **Unavailable**, **Switched**, or **Abnormal** state, the routing target group is created.
2049
- * - **Active/standby pattern**: When you create a routing target group, you must configure primary and secondary instances that are in different zones and of the same type.
2050
- * - **Primary instance**: The weight is 100. The primary instance carries all traffic under normal conditions and takes effect when health checks are successful.
2051
- * - **Secondary instance**: The weight is 0. The secondary instance takes over traffic after the primary instance fails and serves as disaster recovery and backup.
2049
+ * - **Active/standby mode**: When you create a routing target group, configure primary and secondary instances that are in different zones and of the same type.
2050
+ * - **Primary instance**: The weight is 100. The primary instance handles all traffic under normal conditions and takes effect when health checks are successful.
2051
+ * - **Secondary instance**: The weight is 0. The secondary instance takes over traffic when the primary instance fails, serving as disaster recovery and backup.
2052
2052
  *
2053
2053
  * @param request - CreateRouteTargetGroupRequest
2054
2054
  * @param runtime - runtime options for this request RuntimeOptions
@@ -2059,12 +2059,12 @@ export default class Client extends OpenApi {
2059
2059
  * Creates a route target group instance.
2060
2060
  *
2061
2061
  * @remarks
2062
- * - **CreateRouteTargetGroup** is an asynchronous operation. After you invoke this operation, the system returns an instance ID, but the routing target group instance is not yet created. The creation node continues in the background. You can invoke **ListRouteTargetGroup** to query the creation status of the routing target group:
2062
+ * - **CreateRouteTargetGroup** is an asynchronous operation. After you invoke this operation, the system returns an instance ID, but the routing target group instance is not yet created. The creation task continues in the background. You can invoke **ListRouteTargetGroup** to query the creation status of the routing target group:
2063
2063
  * - If the routing target group is in the **Pending** state, the routing target group is being created.
2064
2064
  * - If the routing target group is in the **Available**, **Unavailable**, **Switched**, or **Abnormal** state, the routing target group is created.
2065
- * - **Active/standby pattern**: When you create a routing target group, you must configure primary and secondary instances that are in different zones and of the same type.
2066
- * - **Primary instance**: The weight is 100. The primary instance carries all traffic under normal conditions and takes effect when health checks are successful.
2067
- * - **Secondary instance**: The weight is 0. The secondary instance takes over traffic after the primary instance fails and serves as disaster recovery and backup.
2065
+ * - **Active/standby mode**: When you create a routing target group, configure primary and secondary instances that are in different zones and of the same type.
2066
+ * - **Primary instance**: The weight is 100. The primary instance handles all traffic under normal conditions and takes effect when health checks are successful.
2067
+ * - **Secondary instance**: The weight is 0. The secondary instance takes over traffic when the primary instance fails, serving as disaster recovery and backup.
2068
2068
  *
2069
2069
  * @param request - CreateRouteTargetGroupRequest
2070
2070
  * @returns CreateRouteTargetGroupResponse
@@ -2279,7 +2279,7 @@ export default class Client extends OpenApi {
2279
2279
  * @remarks
2280
2280
  * When you call this operation to create a vSwitch, take note of the following items:
2281
2281
  * - The number of vSwitches in each VPC cannot exceed 150.
2282
- * - The first IP address and the last three IP addresses of each vSwitch CIDR block are reserved by the system. For example, the system reserved IP addresses of 192.168.1.0/24 are 192.168.1.0, 192.168.1.253, 192.168.1.254, and 192.168.1.255.
2282
+ * - The first and last three IP addresses of each vSwitch CIDR block are reserved by the system. For example, the system reserved IP addresses of 192.168.1.0/24 are 192.168.1.0, 192.168.1.253, 192.168.1.254, and 192.168.1.255.
2283
2283
  * - The number of cloud service instances in a vSwitch cannot exceed the remaining available cloud service instances in the VPC (15,000 minus the current number of cloud service instances).
2284
2284
  * - A cloud service instance can belong to only one vSwitch.
2285
2285
  * - vSwitches do not support multicast or broadcast.
@@ -2301,7 +2301,7 @@ export default class Client extends OpenApi {
2301
2301
  * @remarks
2302
2302
  * When you call this operation to create a vSwitch, take note of the following items:
2303
2303
  * - The number of vSwitches in each VPC cannot exceed 150.
2304
- * - The first IP address and the last three IP addresses of each vSwitch CIDR block are reserved by the system. For example, the system reserved IP addresses of 192.168.1.0/24 are 192.168.1.0, 192.168.1.253, 192.168.1.254, and 192.168.1.255.
2304
+ * - The first and last three IP addresses of each vSwitch CIDR block are reserved by the system. For example, the system reserved IP addresses of 192.168.1.0/24 are 192.168.1.0, 192.168.1.253, 192.168.1.254, and 192.168.1.255.
2305
2305
  * - The number of cloud service instances in a vSwitch cannot exceed the remaining available cloud service instances in the VPC (15,000 minus the current number of cloud service instances).
2306
2306
  * - A cloud service instance can belong to only one vSwitch.
2307
2307
  * - vSwitches do not support multicast or broadcast.
@@ -2317,15 +2317,15 @@ export default class Client extends OpenApi {
2317
2317
  */
2318
2318
  createVSwitch(request: $_model.CreateVSwitchRequest): Promise<$_model.CreateVSwitchResponse>;
2319
2319
  /**
2320
- * Creates a reserved CIDR block for a vSwitch.
2320
+ * Creates a reserved CIDR block for a vSwitch by calling the CreateVSwitchCidrReservation operation.
2321
2321
  *
2322
2322
  * @remarks
2323
2323
  * When you invoke this operation to create a reserved CIDR block for a vSwitch, take note of the following items:
2324
- * - The maximum number of reserved IPv4 and IPv6 CIDR blocks in a VPC is 100 each.
2324
+ * - The maximum number of reserved IPv4 CIDR blocks and reserved IPv6 CIDR blocks in a VPC is 100 each.
2325
2325
  * - A reserved CIDR block cannot contain the system reserved IP addresses of the vSwitch to which it belongs.
2326
- * - IPv4 CIDR block: The first and last three IP addresses of the vSwitch are system reserved IP addresses.
2327
- * - IPv6 CIDR block: The first and last nine IP addresses of the vSwitch are system reserved IP addresses.
2328
- * - 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:
2326
+ * - IPv4 CIDR block: The first IP address and the last three IP addresses of the vSwitch are system reserved IP addresses.
2327
+ * - IPv6 CIDR block: The first IP address and the last nine IP addresses of the vSwitch are system reserved IP addresses.
2328
+ * - 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:
2329
2329
  * - If the reserved CIDR block for a vSwitch is in the **Assigning** state, the reserved CIDR block for a vSwitch is being allocated.
2330
2330
  * - If the reserved CIDR block for a vSwitch is in the **Assigned** state, the reserved CIDR block for a vSwitch has been allocated.
2331
2331
  *
@@ -2335,15 +2335,15 @@ export default class Client extends OpenApi {
2335
2335
  */
2336
2336
  createVSwitchCidrReservationWithOptions(request: $_model.CreateVSwitchCidrReservationRequest, runtime: $dara.RuntimeOptions): Promise<$_model.CreateVSwitchCidrReservationResponse>;
2337
2337
  /**
2338
- * Creates a reserved CIDR block for a vSwitch.
2338
+ * Creates a reserved CIDR block for a vSwitch by calling the CreateVSwitchCidrReservation operation.
2339
2339
  *
2340
2340
  * @remarks
2341
2341
  * When you invoke this operation to create a reserved CIDR block for a vSwitch, take note of the following items:
2342
- * - The maximum number of reserved IPv4 and IPv6 CIDR blocks in a VPC is 100 each.
2342
+ * - The maximum number of reserved IPv4 CIDR blocks and reserved IPv6 CIDR blocks in a VPC is 100 each.
2343
2343
  * - A reserved CIDR block cannot contain the system reserved IP addresses of the vSwitch to which it belongs.
2344
- * - IPv4 CIDR block: The first and last three IP addresses of the vSwitch are system reserved IP addresses.
2345
- * - IPv6 CIDR block: The first and last nine IP addresses of the vSwitch are system reserved IP addresses.
2346
- * - 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:
2344
+ * - IPv4 CIDR block: The first IP address and the last three IP addresses of the vSwitch are system reserved IP addresses.
2345
+ * - IPv6 CIDR block: The first IP address and the last nine IP addresses of the vSwitch are system reserved IP addresses.
2346
+ * - 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:
2347
2347
  * - If the reserved CIDR block for a vSwitch is in the **Assigning** state, the reserved CIDR block for a vSwitch is being allocated.
2348
2348
  * - If the reserved CIDR block for a vSwitch is in the **Assigned** state, the reserved CIDR block for a vSwitch has been allocated.
2349
2349
  *
@@ -2678,9 +2678,10 @@ export default class Client extends OpenApi {
2678
2678
  * - 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).
2679
2679
  * - 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).
2680
2680
  * ### Limits
2681
- * - Policy-based routes whose destination CIDR block is 0.0.0.0/0 are not supported.
2682
- * - 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.
2683
- * - 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:
2681
+ * - For single-tunnel VPN gateways:
2682
+ * - 0.0.0.0/0 is not supported as the destination CIDR block of a policy-based route.
2683
+ * - 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.
2684
+ * - **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:
2684
2685
  * - If the VPN gateway instance is in the **updating** state, the policy-based route is being created.
2685
2686
  * - If the VPN gateway instance is in the **active** state, the policy-based route is created.
2686
2687
  * - The **CreateVpnPbrRouteEntry** operation does not support concurrent creation of policy-based routes for the same VPN gateway instance.
@@ -2698,9 +2699,10 @@ export default class Client extends OpenApi {
2698
2699
  * - 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).
2699
2700
  * - 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).
2700
2701
  * ### Limits
2701
- * - Policy-based routes whose destination CIDR block is 0.0.0.0/0 are not supported.
2702
- * - 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.
2703
- * - 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:
2702
+ * - For single-tunnel VPN gateways:
2703
+ * - 0.0.0.0/0 is not supported as the destination CIDR block of a policy-based route.
2704
+ * - 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.
2705
+ * - **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:
2704
2706
  * - If the VPN gateway instance is in the **updating** state, the policy-based route is being created.
2705
2707
  * - If the VPN gateway instance is in the **active** state, the policy-based route is created.
2706
2708
  * - The **CreateVpnPbrRouteEntry** operation does not support concurrent creation of policy-based routes for the same VPN gateway instance.
@@ -2710,16 +2712,16 @@ export default class Client extends OpenApi {
2710
2712
  */
2711
2713
  createVpnPbrRouteEntry(request: $_model.CreateVpnPbrRouteEntryRequest): Promise<$_model.CreateVpnPbrRouteEntryResponse>;
2712
2714
  /**
2713
- * 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.
2715
+ * 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.
2714
2716
  *
2715
2717
  * @remarks
2716
2718
  * ### Before you begin
2717
2719
  * - 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).
2718
2720
  * - 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).
2719
2721
  * ### Limits
2720
- * - Destination routes whose destination CIDR block is 0.0.0.0/0 are not supported.
2721
- * - 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.
2722
- * - 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:
2722
+ * - 0.0.0.0/0 is not supported as the destination CIDR block of a destination route.
2723
+ * - 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.
2724
+ * - 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:
2723
2725
  * - If the VPN gateway instance is in the **updating** state, the destination route is being created.
2724
2726
  * - If the VPN gateway instance is in the **active** state, the destination route is created.
2725
2727
  * - The **CreateVpnRouteEntry** operation does not support concurrent creation of destination routes for the same VPN gateway.
@@ -2730,16 +2732,16 @@ export default class Client extends OpenApi {
2730
2732
  */
2731
2733
  createVpnRouteEntryWithOptions(request: $_model.CreateVpnRouteEntryRequest, runtime: $dara.RuntimeOptions): Promise<$_model.CreateVpnRouteEntryResponse>;
2732
2734
  /**
2733
- * 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.
2735
+ * 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.
2734
2736
  *
2735
2737
  * @remarks
2736
2738
  * ### Before you begin
2737
2739
  * - 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).
2738
2740
  * - 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).
2739
2741
  * ### Limits
2740
- * - Destination routes whose destination CIDR block is 0.0.0.0/0 are not supported.
2741
- * - 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.
2742
- * - 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:
2742
+ * - 0.0.0.0/0 is not supported as the destination CIDR block of a destination route.
2743
+ * - 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.
2744
+ * - 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:
2743
2745
  * - If the VPN gateway instance is in the **updating** state, the destination route is being created.
2744
2746
  * - If the VPN gateway instance is in the **active** state, the destination route is created.
2745
2747
  * - The **CreateVpnRouteEntry** operation does not support concurrent creation of destination routes for the same VPN gateway.
@@ -3521,16 +3523,16 @@ export default class Client extends OpenApi {
3521
3523
  */
3522
3524
  deletePublicIpAddressPoolCidrBlock(request: $_model.DeletePublicIpAddressPoolCidrBlockRequest): Promise<$_model.DeletePublicIpAddressPoolCidrBlockResponse>;
3523
3525
  /**
3524
- * Calls DeleteRouteEntries to batch delete custom route entries.
3526
+ * Deletes custom route entries in a batch.
3525
3527
  *
3526
3528
  * @remarks
3527
- * When you call this operation to delete routing entries, note the following items:
3528
- * - Only routing entries in the **Available** state can be deleted.
3529
- * - Routing entries cannot be deleted if the VPC that contains the route table is creating or deleting a vSwitch or routing entry.
3530
- * - 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:
3531
- * - If the routing entry is in the **Deleting** state, the routing entry is being deleted.
3532
- * - If the specified routing entry cannot be found, the routing entry is deleted.
3533
- * - The **DeleteRouteEntries** operation does not support concurrent batch deletion of routing entries in route tables within the same VPC.
3529
+ * When you call this operation to delete route entries, take note of the following items:
3530
+ * - Only route entries in the **Available** state can be deleted.
3531
+ * - Route entries cannot be deleted if the VPC to which the route table belongs has a vSwitch or route entry being created or deleted.
3532
+ * - 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:
3533
+ * - If the route entry is in the **Deleting** state, the route entry is being deleted.
3534
+ * - If the specified route entry cannot be found, the route entry is deleted.
3535
+ * - The **DeleteRouteEntries** operation does not support concurrent batch deletion of route entries from route tables in the same VPC.
3534
3536
  *
3535
3537
  * @param request - DeleteRouteEntriesRequest
3536
3538
  * @param runtime - runtime options for this request RuntimeOptions
@@ -3538,30 +3540,30 @@ export default class Client extends OpenApi {
3538
3540
  */
3539
3541
  deleteRouteEntriesWithOptions(request: $_model.DeleteRouteEntriesRequest, runtime: $dara.RuntimeOptions): Promise<$_model.DeleteRouteEntriesResponse>;
3540
3542
  /**
3541
- * Calls DeleteRouteEntries to batch delete custom route entries.
3543
+ * Deletes custom route entries in a batch.
3542
3544
  *
3543
3545
  * @remarks
3544
- * When you call this operation to delete routing entries, note the following items:
3545
- * - Only routing entries in the **Available** state can be deleted.
3546
- * - Routing entries cannot be deleted if the VPC that contains the route table is creating or deleting a vSwitch or routing entry.
3547
- * - 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:
3548
- * - If the routing entry is in the **Deleting** state, the routing entry is being deleted.
3549
- * - If the specified routing entry cannot be found, the routing entry is deleted.
3550
- * - The **DeleteRouteEntries** operation does not support concurrent batch deletion of routing entries in route tables within the same VPC.
3546
+ * When you call this operation to delete route entries, take note of the following items:
3547
+ * - Only route entries in the **Available** state can be deleted.
3548
+ * - Route entries cannot be deleted if the VPC to which the route table belongs has a vSwitch or route entry being created or deleted.
3549
+ * - 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:
3550
+ * - If the route entry is in the **Deleting** state, the route entry is being deleted.
3551
+ * - If the specified route entry cannot be found, the route entry is deleted.
3552
+ * - The **DeleteRouteEntries** operation does not support concurrent batch deletion of route entries from route tables in the same VPC.
3551
3553
  *
3552
3554
  * @param request - DeleteRouteEntriesRequest
3553
3555
  * @returns DeleteRouteEntriesResponse
3554
3556
  */
3555
3557
  deleteRouteEntries(request: $_model.DeleteRouteEntriesRequest): Promise<$_model.DeleteRouteEntriesResponse>;
3556
3558
  /**
3557
- * Invokes the DeleteRouteEntry operation to delete a route from the route table of a VPC vRouter or Virtual Border Router (VBR).
3559
+ * Invokes the DeleteRouteEntry operation to delete a route from the route table of a vRouter or Virtual Border Router (VBR).
3558
3560
  *
3559
3561
  * @remarks
3560
- * When you call this operation to delete a route, note the following items:
3562
+ * When you call this operation to delete a route, take note of the following items:
3561
3563
  * - Only routes in the **Available** state can be deleted.
3562
- * - A route cannot be deleted if the VPC that contains the route table is creating or deleting a vSwitch or route entry.
3564
+ * - A route cannot be deleted while the VPC that contains the route table is creating or deleting a vSwitch or route.
3563
3565
  * - 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.
3564
- * - 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:
3566
+ * - 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:
3565
3567
  * - If the route is in the **Deleting** state, the route is being deleted.
3566
3568
  * - If the specified route cannot be found, the route is deleted.
3567
3569
  * - The **DeleteRouteEntry** operation does not support concurrent deletion of routes from the route table within the same VPC or VBR.
@@ -3572,14 +3574,14 @@ export default class Client extends OpenApi {
3572
3574
  */
3573
3575
  deleteRouteEntryWithOptions(request: $_model.DeleteRouteEntryRequest, runtime: $dara.RuntimeOptions): Promise<$_model.DeleteRouteEntryResponse>;
3574
3576
  /**
3575
- * Invokes the DeleteRouteEntry operation to delete a route from the route table of a VPC vRouter or Virtual Border Router (VBR).
3577
+ * Invokes the DeleteRouteEntry operation to delete a route from the route table of a vRouter or Virtual Border Router (VBR).
3576
3578
  *
3577
3579
  * @remarks
3578
- * When you call this operation to delete a route, note the following items:
3580
+ * When you call this operation to delete a route, take note of the following items:
3579
3581
  * - Only routes in the **Available** state can be deleted.
3580
- * - A route cannot be deleted if the VPC that contains the route table is creating or deleting a vSwitch or route entry.
3582
+ * - A route cannot be deleted while the VPC that contains the route table is creating or deleting a vSwitch or route.
3581
3583
  * - 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.
3582
- * - 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:
3584
+ * - 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:
3583
3585
  * - If the route is in the **Deleting** state, the route is being deleted.
3584
3586
  * - If the specified route cannot be found, the route is deleted.
3585
3587
  * - The **DeleteRouteEntry** operation does not support concurrent deletion of routes from the route table within the same VPC or VBR.
@@ -7134,7 +7136,7 @@ export default class Client extends OpenApi {
7134
7136
  */
7135
7137
  modifyPhysicalConnectionAttribute(request: $_model.ModifyPhysicalConnectionAttributeRequest): Promise<$_model.ModifyPhysicalConnectionAttributeResponse>;
7136
7138
  /**
7137
- * Invokes the ModifyRouteEntry operation to modify custom route entry name, description, and route next hop.
7139
+ * Calls the ModifyRouteEntry operation to modify the name, description, and next hop of a custom route entry.
7138
7140
  *
7139
7141
  * @remarks
7140
7142
  * - The **ModifyRouteEntry** operation does not support concurrent modifications to the name and description of the same custom route entry.
@@ -7146,7 +7148,7 @@ export default class Client extends OpenApi {
7146
7148
  */
7147
7149
  modifyRouteEntryWithOptions(request: $_model.ModifyRouteEntryRequest, runtime: $dara.RuntimeOptions): Promise<$_model.ModifyRouteEntryResponse>;
7148
7150
  /**
7149
- * Invokes the ModifyRouteEntry operation to modify custom route entry name, description, and route next hop.
7151
+ * Calls the ModifyRouteEntry operation to modify the name, description, and next hop of a custom route entry.
7150
7152
  *
7151
7153
  * @remarks
7152
7154
  * - The **ModifyRouteEntry** operation does not support concurrent modifications to the name and description of the same custom route entry.
@@ -8107,17 +8109,17 @@ export default class Client extends OpenApi {
8107
8109
  */
8108
8110
  replaceVpcDhcpOptionsSet(request: $_model.ReplaceVpcDhcpOptionsSetRequest): Promise<$_model.ReplaceVpcDhcpOptionsSetResponse>;
8109
8111
  /**
8110
- * Retries the delivery of the latest prefix list by calling the RetryVpcPrefixListAssociation operation.
8112
+ * Redeploys the latest prefix list by calling the RetryVpcPrefixListAssociation operation.
8111
8113
  *
8112
8114
  * @remarks
8113
- * - 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.
8114
- * - 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:
8115
- * - If the delivery status is **Modifying**, the latest prefix list instance is being redelivered.
8116
- * - If the delivery status is **ModifyFailed**, the latest prefix list instance failed to be redelivered.
8117
- * - If the delivery status is **Created**, the latest prefix list instance is redelivered.
8118
- * - The **RetryVpcPrefixListAssociation** operation does not support concurrent retry delivery of the latest prefix list instance for the same prefix list.
8115
+ * - 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.
8116
+ * - 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:
8117
+ * - If the deployment status of the prefix list instance is **Modifying**, the latest prefix list instance is being redeployed.
8118
+ * - If the deployment status of the prefix list instance is **ModifyFailed**, the latest prefix list instance failed to be redeployed.
8119
+ * - If the deployment status of the prefix list instance is **Created**, the latest prefix list instance is redeployed.
8120
+ * - The **RetryVpcPrefixListAssociation** operation does not support concurrent retry of redeploying the latest prefix list instance for the same prefix list.
8119
8121
  * ## Scenarios
8120
- * 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.
8122
+ * 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.
8121
8123
  *
8122
8124
  * @param request - RetryVpcPrefixListAssociationRequest
8123
8125
  * @param runtime - runtime options for this request RuntimeOptions
@@ -8125,17 +8127,17 @@ export default class Client extends OpenApi {
8125
8127
  */
8126
8128
  retryVpcPrefixListAssociationWithOptions(request: $_model.RetryVpcPrefixListAssociationRequest, runtime: $dara.RuntimeOptions): Promise<$_model.RetryVpcPrefixListAssociationResponse>;
8127
8129
  /**
8128
- * Retries the delivery of the latest prefix list by calling the RetryVpcPrefixListAssociation operation.
8130
+ * Redeploys the latest prefix list by calling the RetryVpcPrefixListAssociation operation.
8129
8131
  *
8130
8132
  * @remarks
8131
- * - 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.
8132
- * - 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:
8133
- * - If the delivery status is **Modifying**, the latest prefix list instance is being redelivered.
8134
- * - If the delivery status is **ModifyFailed**, the latest prefix list instance failed to be redelivered.
8135
- * - If the delivery status is **Created**, the latest prefix list instance is redelivered.
8136
- * - The **RetryVpcPrefixListAssociation** operation does not support concurrent retry delivery of the latest prefix list instance for the same prefix list.
8133
+ * - 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.
8134
+ * - 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:
8135
+ * - If the deployment status of the prefix list instance is **Modifying**, the latest prefix list instance is being redeployed.
8136
+ * - If the deployment status of the prefix list instance is **ModifyFailed**, the latest prefix list instance failed to be redeployed.
8137
+ * - If the deployment status of the prefix list instance is **Created**, the latest prefix list instance is redeployed.
8138
+ * - The **RetryVpcPrefixListAssociation** operation does not support concurrent retry of redeploying the latest prefix list instance for the same prefix list.
8137
8139
  * ## Scenarios
8138
- * 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.
8140
+ * 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.
8139
8141
  *
8140
8142
  * @param request - RetryVpcPrefixListAssociationRequest
8141
8143
  * @returns RetryVpcPrefixListAssociationResponse
@@ -8607,7 +8609,7 @@ export default class Client extends OpenApi {
8607
8609
  */
8608
8610
  untagResourcesForExpressConnect(request: $_model.UntagResourcesForExpressConnectRequest): Promise<$_model.UntagResourcesForExpressConnectResponse>;
8609
8611
  /**
8610
- * Modifies the configuration of a DHCP options set.
8612
+ * Modifies the configuration of a DHCP options set by calling the UpdateDhcpOptionsSetAttribute operation.
8611
8613
  *
8612
8614
  * @param request - UpdateDhcpOptionsSetAttributeRequest
8613
8615
  * @param runtime - runtime options for this request RuntimeOptions
@@ -8615,7 +8617,7 @@ export default class Client extends OpenApi {
8615
8617
  */
8616
8618
  updateDhcpOptionsSetAttributeWithOptions(request: $_model.UpdateDhcpOptionsSetAttributeRequest, runtime: $dara.RuntimeOptions): Promise<$_model.UpdateDhcpOptionsSetAttributeResponse>;
8617
8619
  /**
8618
- * Modifies the configuration of a DHCP options set.
8620
+ * Modifies the configuration of a DHCP options set by calling the UpdateDhcpOptionsSetAttribute operation.
8619
8621
  *
8620
8622
  * @param request - UpdateDhcpOptionsSetAttributeRequest
8621
8623
  * @returns UpdateDhcpOptionsSetAttributeResponse