@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/src/client.ts CHANGED
@@ -49,42 +49,6 @@ export default class Client extends OpenApi {
49
49
  'cn-zhengzhou-nebula-1': "vpc-nebula.cn-qingdao-nebula.aliyuncs.com",
50
50
  'eu-west-1-oxs': "vpc-nebula.cn-shenzhen-cloudstone.aliyuncs.com",
51
51
  'rus-west-1-pop': "vpc.aliyuncs.com",
52
- 'cn-beijing': "vpc.cn-beijing.aliyuncs.com",
53
- 'cn-heyuan': "vpc.cn-heyuan.aliyuncs.com",
54
- 'cn-zhangjiakou': "vpc.cn-zhangjiakou.aliyuncs.com",
55
- 'ap-northeast-2': "vpc.ap-northeast-2.aliyuncs.com",
56
- 'ap-northeast-1': "vpc.ap-northeast-1.aliyuncs.com",
57
- 'ap-southeast-1': "vpc.ap-southeast-1.aliyuncs.com",
58
- 'ap-southeast-3': "vpc.ap-southeast-3.aliyuncs.com",
59
- 'ap-southeast-5': "vpc.ap-southeast-5.aliyuncs.com",
60
- 'ap-southeast-6': "vpc.ap-southeast-6.aliyuncs.com",
61
- 'ap-southeast-7': "vpc.ap-southeast-7.aliyuncs.com",
62
- 'ap-southeast-8': "vpc.ap-southeast-8.aliyuncs.com",
63
- 'cn-zhongwei': "vpc.cn-zhongwei.aliyuncs.com",
64
- 'cn-wulanchabu': "vpc.cn-wulanchabu.aliyuncs.com",
65
- 'cn-qingdao': "vpc.cn-qingdao.aliyuncs.com",
66
- 'cn-wuhan-lr': "vpc.cn-wuhan-lr.aliyuncs.com",
67
- 'cn-shanghai': "vpc.cn-shanghai.aliyuncs.com",
68
- 'cn-hongkong': "vpc.cn-hongkong.aliyuncs.com",
69
- 'cn-shenzhen': "vpc.cn-shenzhen.aliyuncs.com",
70
- 'cn-nanjing': "vpc.cn-nanjing.aliyuncs.com",
71
- 'cn-fuzhou': "vpc.cn-fuzhou.aliyuncs.com",
72
- 'cn-chengdu': "vpc.cn-chengdu.aliyuncs.com",
73
- 'cn-guangzhou': "vpc.cn-guangzhou.aliyuncs.com",
74
- 'cn-huhehaote': "vpc.cn-huhehaote.aliyuncs.com",
75
- 'us-southeast-1': "vpc.us-southeast-1.aliyuncs.com",
76
- 'eu-west-1': "vpc.eu-west-1.aliyuncs.com",
77
- 'eu-west-2': "vpc.eu-west-2.aliyuncs.com",
78
- 'eu-central-1': "vpc.eu-central-1.aliyuncs.com",
79
- 'us-east-1': "vpc.us-east-1.aliyuncs.com",
80
- 'sa-east-1': "vpc.sa-east-1.aliyuncs.com",
81
- 'us-west-1': "vpc.us-west-1.aliyuncs.com",
82
- 'na-south-1': "vpc.na-south-1.aliyuncs.com",
83
- 'me-east-1': "vpc.me-east-1.aliyuncs.com",
84
- 'me-central-1': "vpc.me-central-1.aliyuncs.com",
85
- 'cn-beijing-finance-1': "vpc.cn-beijing-finance-1.aliyuncs.com",
86
- 'cn-heyuan-acdr-1': "vpc.cn-heyuan-acdr-1.aliyuncs.com",
87
- 'cn-wulanchabu-gic-1': "vpc.cn-wulanchabu-gic-1.aliyuncs.com",
88
52
  };
89
53
  this.checkConfig(config);
90
54
  this._endpoint = this.getEndpoint("vpc", this._regionId, this._endpointRule, this._network, this._suffix, this._endpointMap, this._endpoint);
@@ -323,12 +287,12 @@ export default class Client extends OpenApi {
323
287
  * Adds an elastic IP address (EIP) to an Internet Shared Bandwidth instance.
324
288
  *
325
289
  * @remarks
326
- * Before invoking this operation, note the following:
290
+ * Before you invoke this operation, take note of the following items:
327
291
  * - When you invoke this operation to add an EIP to an Internet Shared Bandwidth instance, the EIP must meet the following conditions:
328
- * - The EIP uses the pay-as-you-go billing method.
292
+ * - The billing method of the EIP is pay-as-you-go.
329
293
  * - The EIP is in the same region as the Internet Shared Bandwidth instance.
330
294
  * - The line type of the EIP is the same as that of the Internet Shared Bandwidth instance.
331
- * - 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.
332
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.
333
297
  * - If the association status is **BINDED**, the Internet Shared Bandwidth instance is associated with the EIP.
334
298
  *
@@ -400,12 +364,12 @@ export default class Client extends OpenApi {
400
364
  * Adds an elastic IP address (EIP) to an Internet Shared Bandwidth instance.
401
365
  *
402
366
  * @remarks
403
- * Before invoking this operation, note the following:
367
+ * Before you invoke this operation, take note of the following items:
404
368
  * - When you invoke this operation to add an EIP to an Internet Shared Bandwidth instance, the EIP must meet the following conditions:
405
- * - The EIP uses the pay-as-you-go billing method.
369
+ * - The billing method of the EIP is pay-as-you-go.
406
370
  * - The EIP is in the same region as the Internet Shared Bandwidth instance.
407
371
  * - The line type of the EIP is the same as that of the Internet Shared Bandwidth instance.
408
- * - 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.
409
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.
410
374
  * - If the association status is **BINDED**, the Internet Shared Bandwidth instance is associated with the EIP.
411
375
  *
@@ -4051,7 +4015,7 @@ export default class Client extends OpenApi {
4051
4015
  * @remarks
4052
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:
4053
4017
  * - If the vSwitch is in the **Pending** state, the DHCP options set is being configured.
4054
- * - 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.
4055
4019
  *
4056
4020
  * @param request - CreateDhcpOptionsSetRequest
4057
4021
  * @param runtime - runtime options for this request RuntimeOptions
@@ -4143,7 +4107,7 @@ export default class Client extends OpenApi {
4143
4107
  * @remarks
4144
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:
4145
4109
  * - If the vSwitch is in the **Pending** state, the DHCP options set is being configured.
4146
- * - 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.
4147
4111
  *
4148
4112
  * @param request - CreateDhcpOptionsSetRequest
4149
4113
  * @returns CreateDhcpOptionsSetResponse
@@ -4805,7 +4769,7 @@ export default class Client extends OpenApi {
4805
4769
  * Creates a flow log.
4806
4770
  *
4807
4771
  * @remarks
4808
- * *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:
4809
4773
  * - If the flow log is in the **Activating** state, the flow log is being created.
4810
4774
  * - If the flow log is in the **Active** state, the flow log is created and activated.
4811
4775
  *
@@ -4909,7 +4873,7 @@ export default class Client extends OpenApi {
4909
4873
  * Creates a flow log.
4910
4874
  *
4911
4875
  * @remarks
4912
- * *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:
4913
4877
  * - If the flow log is in the **Activating** state, the flow log is being created.
4914
4878
  * - If the flow log is in the **Active** state, the flow log is created and activated.
4915
4879
  *
@@ -7030,17 +6994,17 @@ export default class Client extends OpenApi {
7030
6994
  }
7031
6995
 
7032
6996
  /**
7033
- * 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.
7034
6998
  *
7035
6999
  * @remarks
7036
- * - **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:
7037
- * - If the route is in the **Creating** state, the route is being created.
7038
- * - If the route is in the **Created** state, the route is created.
7039
- * - **CreateRouteEntries** does not support concurrent batch creation of custom route entries in the same VPC.
7040
- * **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:**
7041
7005
  * - A route table can contain a maximum of 200 custom route entries.
7042
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.
7043
- * - 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.
7044
7008
  * - The destination CIDR blocks (**DstCidrBlock**) of route entries in the same route table must be unique.
7045
7009
  * - If the specified destination CIDR block (**DstCidrBlock**) is an IP address, the system processes it with a 32-bit mask.
7046
7010
  * - Multiple custom route entries can point to the same next hop (**NextHop**).
@@ -7103,17 +7067,17 @@ export default class Client extends OpenApi {
7103
7067
  }
7104
7068
 
7105
7069
  /**
7106
- * 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.
7107
7071
  *
7108
7072
  * @remarks
7109
- * - **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:
7110
- * - If the route is in the **Creating** state, the route is being created.
7111
- * - If the route is in the **Created** state, the route is created.
7112
- * - **CreateRouteEntries** does not support concurrent batch creation of custom route entries in the same VPC.
7113
- * **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:**
7114
7078
  * - A route table can contain a maximum of 200 custom route entries.
7115
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.
7116
- * - 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.
7117
7081
  * - The destination CIDR blocks (**DstCidrBlock**) of route entries in the same route table must be unique.
7118
7082
  * - If the specified destination CIDR block (**DstCidrBlock**) is an IP address, the system processes it with a 32-bit mask.
7119
7083
  * - Multiple custom route entries can point to the same next hop (**NextHop**).
@@ -7131,44 +7095,44 @@ export default class Client extends OpenApi {
7131
7095
  * Creates a custom route entry on a vRouter or Virtual Border Router (VBR).
7132
7096
  *
7133
7097
  * @remarks
7134
- * - **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:
7135
- * - If the route is in the **Creating** state, the route is being created.
7136
- * - If the route is in the **Created** state, the route has been created.
7137
- * - **CreateRouteEntry** does not support concurrent creation of custom route entries in the same VPC or the same VBR.
7138
- * - **CreateRouteEntry** may return the **TaskConflict** error code in concurrent scenarios. Retry the operation as needed.
7139
- * **When you use this operation to add a custom route entry to a route table of a vRouter, take note of the following items:**
7140
- * > 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.
7141
- * - A route table can contain up to 200 custom route entries.
7142
- * - 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.
7143
- * - 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.
7144
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>
7145
- * - The destination CIDR blocks (**DestinationCidrBlock**) of route entries in the same route table must be unique.
7146
- * - 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.
7147
7111
  * - Multiple custom route entries can point to the same next hop (**NextHopId**).
7148
7112
  * - The next hop (**NextHopId**) of a custom route entry must be in the same VPC as the route table.
7149
7113
  * - You can configure ECMP routing by using the **NextHopList** parameter settings:
7150
7114
  * * To add a non-ECMP custom route, specify the **DestinationCidrBlock**, **NextHopType**, and **NextHopId** parameters. Do not specify the **NextHopList** parameter.
7151
7115
  *
7152
7116
  * * To add an ECMP route, specify the **DestinationCidrBlock** and **NextHopList** parameters. Do not specify the **NextHopType** or **NextHopId** parameter.
7153
- * **When you use this operation to add a custom route entry to a route table of a VBR, take note of the following items:**
7154
- * - 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.
7155
7119
  *
7156
7120
  * - The **NextHopList** parameter is not supported.
7157
7121
  *
7158
- * - 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.
7159
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>
7160
7124
  *
7161
- * - 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**).
7162
7126
  *
7163
- * - 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.
7164
7128
  *
7165
7129
  * - Multiple custom route entries can point to the same next hop (**NextHopId**).
7166
7130
  *
7167
- * - 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.
7168
7132
  *
7169
- * - 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.
7170
7134
  *
7171
- * - 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.
7172
7136
  *
7173
7137
  * @param request - CreateRouteEntryRequest
7174
7138
  * @param runtime - runtime options for this request RuntimeOptions
@@ -7254,44 +7218,44 @@ export default class Client extends OpenApi {
7254
7218
  * Creates a custom route entry on a vRouter or Virtual Border Router (VBR).
7255
7219
  *
7256
7220
  * @remarks
7257
- * - **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:
7258
- * - If the route is in the **Creating** state, the route is being created.
7259
- * - If the route is in the **Created** state, the route has been created.
7260
- * - **CreateRouteEntry** does not support concurrent creation of custom route entries in the same VPC or the same VBR.
7261
- * - **CreateRouteEntry** may return the **TaskConflict** error code in concurrent scenarios. Retry the operation as needed.
7262
- * **When you use this operation to add a custom route entry to a route table of a vRouter, take note of the following items:**
7263
- * > 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.
7264
- * - A route table can contain up to 200 custom route entries.
7265
- * - 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.
7266
- * - 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.
7267
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>
7268
- * - The destination CIDR blocks (**DestinationCidrBlock**) of route entries in the same route table must be unique.
7269
- * - 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.
7270
7234
  * - Multiple custom route entries can point to the same next hop (**NextHopId**).
7271
7235
  * - The next hop (**NextHopId**) of a custom route entry must be in the same VPC as the route table.
7272
7236
  * - You can configure ECMP routing by using the **NextHopList** parameter settings:
7273
7237
  * * To add a non-ECMP custom route, specify the **DestinationCidrBlock**, **NextHopType**, and **NextHopId** parameters. Do not specify the **NextHopList** parameter.
7274
7238
  *
7275
7239
  * * To add an ECMP route, specify the **DestinationCidrBlock** and **NextHopList** parameters. Do not specify the **NextHopType** or **NextHopId** parameter.
7276
- * **When you use this operation to add a custom route entry to a route table of a VBR, take note of the following items:**
7277
- * - 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.
7278
7242
  *
7279
7243
  * - The **NextHopList** parameter is not supported.
7280
7244
  *
7281
- * - 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.
7282
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>
7283
7247
  *
7284
- * - 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**).
7285
7249
  *
7286
- * - 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.
7287
7251
  *
7288
7252
  * - Multiple custom route entries can point to the same next hop (**NextHopId**).
7289
7253
  *
7290
- * - 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.
7291
7255
  *
7292
- * - 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.
7293
7257
  *
7294
- * - 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.
7295
7259
  *
7296
7260
  * @param request - CreateRouteEntryRequest
7297
7261
  * @returns CreateRouteEntryResponse
@@ -7403,12 +7367,12 @@ export default class Client extends OpenApi {
7403
7367
  * Creates a route target group instance.
7404
7368
  *
7405
7369
  * @remarks
7406
- * - **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:
7370
+ * - **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:
7407
7371
  * - If the routing target group is in the **Pending** state, the routing target group is being created.
7408
7372
  * - If the routing target group is in the **Available**, **Unavailable**, **Switched**, or **Abnormal** state, the routing target group is created.
7409
- * - **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.
7410
- * - **Primary instance**: The weight is 100. The primary instance carries all traffic under normal conditions and takes effect when health checks are successful.
7411
- * - **Secondary instance**: The weight is 0. The secondary instance takes over traffic after the primary instance fails and serves as disaster recovery and backup.
7373
+ * - **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.
7374
+ * - **Primary instance**: The weight is 100. The primary instance handles all traffic under normal conditions and takes effect when health checks are successful.
7375
+ * - **Secondary instance**: The weight is 0. The secondary instance takes over traffic when the primary instance fails, serving as disaster recovery and backup.
7412
7376
  *
7413
7377
  * @param request - CreateRouteTargetGroupRequest
7414
7378
  * @param runtime - runtime options for this request RuntimeOptions
@@ -7474,12 +7438,12 @@ export default class Client extends OpenApi {
7474
7438
  * Creates a route target group instance.
7475
7439
  *
7476
7440
  * @remarks
7477
- * - **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:
7441
+ * - **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:
7478
7442
  * - If the routing target group is in the **Pending** state, the routing target group is being created.
7479
7443
  * - If the routing target group is in the **Available**, **Unavailable**, **Switched**, or **Abnormal** state, the routing target group is created.
7480
- * - **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.
7481
- * - **Primary instance**: The weight is 100. The primary instance carries all traffic under normal conditions and takes effect when health checks are successful.
7482
- * - **Secondary instance**: The weight is 0. The secondary instance takes over traffic after the primary instance fails and serves as disaster recovery and backup.
7444
+ * - **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.
7445
+ * - **Primary instance**: The weight is 100. The primary instance handles all traffic under normal conditions and takes effect when health checks are successful.
7446
+ * - **Secondary instance**: The weight is 0. The secondary instance takes over traffic when the primary instance fails, serving as disaster recovery and backup.
7483
7447
  *
7484
7448
  * @param request - CreateRouteTargetGroupRequest
7485
7449
  * @returns CreateRouteTargetGroupResponse
@@ -8315,7 +8279,7 @@ export default class Client extends OpenApi {
8315
8279
  * @remarks
8316
8280
  * When you call this operation to create a vSwitch, take note of the following items:
8317
8281
  * - The number of vSwitches in each VPC cannot exceed 150.
8318
- * - 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.
8282
+ * - 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.
8319
8283
  * - 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).
8320
8284
  * - A cloud service instance can belong to only one vSwitch.
8321
8285
  * - vSwitches do not support multicast or broadcast.
@@ -8337,6 +8301,10 @@ export default class Client extends OpenApi {
8337
8301
  query["CidrBlock"] = request.cidrBlock;
8338
8302
  }
8339
8303
 
8304
+ if (!$dara.isNull(request.cidrMask)) {
8305
+ query["CidrMask"] = request.cidrMask;
8306
+ }
8307
+
8340
8308
  if (!$dara.isNull(request.clientToken)) {
8341
8309
  query["ClientToken"] = request.clientToken;
8342
8310
  }
@@ -8349,6 +8317,10 @@ export default class Client extends OpenApi {
8349
8317
  query["Ipv6CidrBlock"] = request.ipv6CidrBlock;
8350
8318
  }
8351
8319
 
8320
+ if (!$dara.isNull(request.ipv6CidrMask)) {
8321
+ query["Ipv6CidrMask"] = request.ipv6CidrMask;
8322
+ }
8323
+
8352
8324
  if (!$dara.isNull(request.ownerAccount)) {
8353
8325
  query["OwnerAccount"] = request.ownerAccount;
8354
8326
  }
@@ -8412,7 +8384,7 @@ export default class Client extends OpenApi {
8412
8384
  * @remarks
8413
8385
  * When you call this operation to create a vSwitch, take note of the following items:
8414
8386
  * - The number of vSwitches in each VPC cannot exceed 150.
8415
- * - 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.
8387
+ * - 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.
8416
8388
  * - 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).
8417
8389
  * - A cloud service instance can belong to only one vSwitch.
8418
8390
  * - vSwitches do not support multicast or broadcast.
@@ -8432,15 +8404,15 @@ export default class Client extends OpenApi {
8432
8404
  }
8433
8405
 
8434
8406
  /**
8435
- * Creates a reserved CIDR block for a vSwitch.
8407
+ * Creates a reserved CIDR block for a vSwitch by calling the CreateVSwitchCidrReservation operation.
8436
8408
  *
8437
8409
  * @remarks
8438
8410
  * When you invoke this operation to create a reserved CIDR block for a vSwitch, take note of the following items:
8439
- * - 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.
8440
8412
  * - A reserved CIDR block cannot contain the system reserved IP addresses of the vSwitch to which it belongs.
8441
- * - IPv4 CIDR block: The first and last three IP addresses of the vSwitch are system reserved IP addresses.
8442
- * - IPv6 CIDR block: The first and last nine IP addresses of the vSwitch are system reserved IP addresses.
8443
- * - 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:
8444
8416
  * - If the reserved CIDR block for a vSwitch is in the **Assigning** state, the reserved CIDR block for a vSwitch is being allocated.
8445
8417
  * - If the reserved CIDR block for a vSwitch is in the **Assigned** state, the reserved CIDR block for a vSwitch has been allocated.
8446
8418
  *
@@ -8533,15 +8505,15 @@ export default class Client extends OpenApi {
8533
8505
  }
8534
8506
 
8535
8507
  /**
8536
- * Creates a reserved CIDR block for a vSwitch.
8508
+ * Creates a reserved CIDR block for a vSwitch by calling the CreateVSwitchCidrReservation operation.
8537
8509
  *
8538
8510
  * @remarks
8539
8511
  * When you invoke this operation to create a reserved CIDR block for a vSwitch, take note of the following items:
8540
- * - 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.
8541
8513
  * - A reserved CIDR block cannot contain the system reserved IP addresses of the vSwitch to which it belongs.
8542
- * - IPv4 CIDR block: The first and last three IP addresses of the vSwitch are system reserved IP addresses.
8543
- * - IPv6 CIDR block: The first and last nine IP addresses of the vSwitch are system reserved IP addresses.
8544
- * - 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:
8545
8517
  * - If the reserved CIDR block for a vSwitch is in the **Assigning** state, the reserved CIDR block for a vSwitch is being allocated.
8546
8518
  * - If the reserved CIDR block for a vSwitch is in the **Assigned** state, the reserved CIDR block for a vSwitch has been allocated.
8547
8519
  *
@@ -9867,9 +9839,10 @@ export default class Client extends OpenApi {
9867
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).
9868
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).
9869
9841
  * ### Limits
9870
- * - Policy-based routes whose destination CIDR block is 0.0.0.0/0 are not supported.
9871
- * - 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.
9872
- * - 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:
9873
9846
  * - If the VPN gateway instance is in the **updating** state, the policy-based route is being created.
9874
9847
  * - If the VPN gateway instance is in the **active** state, the policy-based route is created.
9875
9848
  * - The **CreateVpnPbrRouteEntry** operation does not support concurrent creation of policy-based routes for the same VPN gateway instance.
@@ -9970,9 +9943,10 @@ export default class Client extends OpenApi {
9970
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).
9971
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).
9972
9945
  * ### Limits
9973
- * - Policy-based routes whose destination CIDR block is 0.0.0.0/0 are not supported.
9974
- * - 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.
9975
- * - 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:
9976
9950
  * - If the VPN gateway instance is in the **updating** state, the policy-based route is being created.
9977
9951
  * - If the VPN gateway instance is in the **active** state, the policy-based route is created.
9978
9952
  * - The **CreateVpnPbrRouteEntry** operation does not support concurrent creation of policy-based routes for the same VPN gateway instance.
@@ -9986,16 +9960,16 @@ export default class Client extends OpenApi {
9986
9960
  }
9987
9961
 
9988
9962
  /**
9989
- * 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.
9990
9964
  *
9991
9965
  * @remarks
9992
9966
  * ### Before you begin
9993
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).
9994
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).
9995
9969
  * ### Limits
9996
- * - Destination routes whose destination CIDR block is 0.0.0.0/0 are not supported.
9997
- * - 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.
9998
- * - 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:
9999
9973
  * - If the VPN gateway instance is in the **updating** state, the destination route is being created.
10000
9974
  * - If the VPN gateway instance is in the **active** state, the destination route is created.
10001
9975
  * - The **CreateVpnRouteEntry** operation does not support concurrent creation of destination routes for the same VPN gateway.
@@ -10081,16 +10055,16 @@ export default class Client extends OpenApi {
10081
10055
  }
10082
10056
 
10083
10057
  /**
10084
- * 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.
10085
10059
  *
10086
10060
  * @remarks
10087
10061
  * ### Before you begin
10088
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).
10089
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).
10090
10064
  * ### Limits
10091
- * - Destination routes whose destination CIDR block is 0.0.0.0/0 are not supported.
10092
- * - 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.
10093
- * - 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:
10094
10068
  * - If the VPN gateway instance is in the **updating** state, the destination route is being created.
10095
10069
  * - If the VPN gateway instance is in the **active** state, the destination route is created.
10096
10070
  * - The **CreateVpnRouteEntry** operation does not support concurrent creation of destination routes for the same VPN gateway.
@@ -12708,16 +12682,16 @@ export default class Client extends OpenApi {
12708
12682
  }
12709
12683
 
12710
12684
  /**
12711
- * Calls DeleteRouteEntries to batch delete custom route entries.
12685
+ * Deletes custom route entries in a batch.
12712
12686
  *
12713
12687
  * @remarks
12714
- * When you call this operation to delete routing entries, note the following items:
12715
- * - Only routing entries in the **Available** state can be deleted.
12716
- * - Routing entries cannot be deleted if the VPC that contains the route table is creating or deleting a vSwitch or routing entry.
12717
- * - 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:
12718
- * - If the routing entry is in the **Deleting** state, the routing entry is being deleted.
12719
- * - If the specified routing entry cannot be found, the routing entry is deleted.
12720
- * - 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.
12721
12695
  *
12722
12696
  * @param request - DeleteRouteEntriesRequest
12723
12697
  * @param runtime - runtime options for this request RuntimeOptions
@@ -12776,16 +12750,16 @@ export default class Client extends OpenApi {
12776
12750
  }
12777
12751
 
12778
12752
  /**
12779
- * Calls DeleteRouteEntries to batch delete custom route entries.
12753
+ * Deletes custom route entries in a batch.
12780
12754
  *
12781
12755
  * @remarks
12782
- * When you call this operation to delete routing entries, note the following items:
12783
- * - Only routing entries in the **Available** state can be deleted.
12784
- * - Routing entries cannot be deleted if the VPC that contains the route table is creating or deleting a vSwitch or routing entry.
12785
- * - 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:
12786
- * - If the routing entry is in the **Deleting** state, the routing entry is being deleted.
12787
- * - If the specified routing entry cannot be found, the routing entry is deleted.
12788
- * - 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.
12789
12763
  *
12790
12764
  * @param request - DeleteRouteEntriesRequest
12791
12765
  * @returns DeleteRouteEntriesResponse
@@ -12796,14 +12770,14 @@ export default class Client extends OpenApi {
12796
12770
  }
12797
12771
 
12798
12772
  /**
12799
- * 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).
12800
12774
  *
12801
12775
  * @remarks
12802
- * 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:
12803
12777
  * - Only routes in the **Available** state can be deleted.
12804
- * - 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.
12805
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.
12806
- * - 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:
12807
12781
  * - If the route is in the **Deleting** state, the route is being deleted.
12808
12782
  * - If the specified route cannot be found, the route is deleted.
12809
12783
  * - The **DeleteRouteEntry** operation does not support concurrent deletion of routes from the route table within the same VPC or VBR.
@@ -12877,14 +12851,14 @@ export default class Client extends OpenApi {
12877
12851
  }
12878
12852
 
12879
12853
  /**
12880
- * 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).
12881
12855
  *
12882
12856
  * @remarks
12883
- * 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:
12884
12858
  * - Only routes in the **Available** state can be deleted.
12885
- * - 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.
12886
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.
12887
- * - 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:
12888
12862
  * - If the route is in the **Deleting** state, the route is being deleted.
12889
12863
  * - If the specified route cannot be found, the route is deleted.
12890
12864
  * - The **DeleteRouteEntry** operation does not support concurrent deletion of routes from the route table within the same VPC or VBR.
@@ -28103,7 +28077,7 @@ export default class Client extends OpenApi {
28103
28077
  }
28104
28078
 
28105
28079
  /**
28106
- * 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.
28107
28081
  *
28108
28082
  * @remarks
28109
28083
  * - The **ModifyRouteEntry** operation does not support concurrent modifications to the name and description of the same custom route entry.
@@ -28186,7 +28160,7 @@ export default class Client extends OpenApi {
28186
28160
  }
28187
28161
 
28188
28162
  /**
28189
- * 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.
28190
28164
  *
28191
28165
  * @remarks
28192
28166
  * - The **ModifyRouteEntry** operation does not support concurrent modifications to the name and description of the same custom route entry.
@@ -28954,6 +28928,10 @@ export default class Client extends OpenApi {
28954
28928
  query["Ipv6CidrBlock"] = request.ipv6CidrBlock;
28955
28929
  }
28956
28930
 
28931
+ if (!$dara.isNull(request.ipv6CidrMask)) {
28932
+ query["Ipv6CidrMask"] = request.ipv6CidrMask;
28933
+ }
28934
+
28957
28935
  if (!$dara.isNull(request.ownerAccount)) {
28958
28936
  query["OwnerAccount"] = request.ownerAccount;
28959
28937
  }
@@ -31781,17 +31759,17 @@ export default class Client extends OpenApi {
31781
31759
  }
31782
31760
 
31783
31761
  /**
31784
- * Retries the delivery of the latest prefix list by calling the RetryVpcPrefixListAssociation operation.
31762
+ * Redeploys the latest prefix list by calling the RetryVpcPrefixListAssociation operation.
31785
31763
  *
31786
31764
  * @remarks
31787
- * - 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.
31788
- * - 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:
31789
- * - If the delivery status is **Modifying**, the latest prefix list instance is being redelivered.
31790
- * - If the delivery status is **ModifyFailed**, the latest prefix list instance failed to be redelivered.
31791
- * - If the delivery status is **Created**, the latest prefix list instance is redelivered.
31792
- * - 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.
31793
31771
  * ## Scenarios
31794
- * 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.
31795
31773
  *
31796
31774
  * @param request - RetryVpcPrefixListAssociationRequest
31797
31775
  * @param runtime - runtime options for this request RuntimeOptions
@@ -31858,17 +31836,17 @@ export default class Client extends OpenApi {
31858
31836
  }
31859
31837
 
31860
31838
  /**
31861
- * Retries the delivery of the latest prefix list by calling the RetryVpcPrefixListAssociation operation.
31839
+ * Redeploys the latest prefix list by calling the RetryVpcPrefixListAssociation operation.
31862
31840
  *
31863
31841
  * @remarks
31864
- * - 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.
31865
- * - 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:
31866
- * - If the delivery status is **Modifying**, the latest prefix list instance is being redelivered.
31867
- * - If the delivery status is **ModifyFailed**, the latest prefix list instance failed to be redelivered.
31868
- * - If the delivery status is **Created**, the latest prefix list instance is redelivered.
31869
- * - 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.
31870
31848
  * ## Scenarios
31871
- * 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.
31872
31850
  *
31873
31851
  * @param request - RetryVpcPrefixListAssociationRequest
31874
31852
  * @returns RetryVpcPrefixListAssociationResponse
@@ -33537,7 +33515,7 @@ export default class Client extends OpenApi {
33537
33515
  }
33538
33516
 
33539
33517
  /**
33540
- * Modifies the configuration of a DHCP options set.
33518
+ * Modifies the configuration of a DHCP options set by calling the UpdateDhcpOptionsSetAttribute operation.
33541
33519
  *
33542
33520
  * @param request - UpdateDhcpOptionsSetAttributeRequest
33543
33521
  * @param runtime - runtime options for this request RuntimeOptions
@@ -33620,7 +33598,7 @@ export default class Client extends OpenApi {
33620
33598
  }
33621
33599
 
33622
33600
  /**
33623
- * Modifies the configuration of a DHCP options set.
33601
+ * Modifies the configuration of a DHCP options set by calling the UpdateDhcpOptionsSetAttribute operation.
33624
33602
  *
33625
33603
  * @param request - UpdateDhcpOptionsSetAttributeRequest
33626
33604
  * @returns UpdateDhcpOptionsSetAttributeResponse