@alicloud/vpc20160428 7.2.3 → 7.2.5

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 (266) hide show
  1. package/dist/client.d.ts +250 -246
  2. package/dist/client.js +284 -273
  3. package/dist/client.js.map +1 -1
  4. package/dist/models/ActivateRouterInterfaceRequest.d.ts +1 -1
  5. package/dist/models/AssociateMacSecKeyRequest.d.ts +3 -3
  6. package/dist/models/AssociatePhysicalConnectionToVirtualBorderRouterRequest.d.ts +5 -7
  7. package/dist/models/AssociatePhysicalConnectionToVirtualBorderRouterRequest.js.map +1 -1
  8. package/dist/models/AssociateVpnGatewayWithCertificateRequest.d.ts +3 -3
  9. package/dist/models/AttachVbrToVpconnRequest.d.ts +3 -3
  10. package/dist/models/CancelPhysicalConnectionRequest.d.ts +1 -1
  11. package/dist/models/CheckVpnBgpEnabledRequest.d.ts +1 -1
  12. package/dist/models/CompletePhysicalConnectionLoarequest.d.ts +4 -4
  13. package/dist/models/CreateCustomerGatewayRequest.d.ts +4 -4
  14. package/dist/models/CreateCustomerGatewayResponseBody.d.ts +2 -2
  15. package/dist/models/CreateFailoverTestJobRequest.d.ts +5 -5
  16. package/dist/models/CreateFlowLogRequest.d.ts +4 -4
  17. package/dist/models/CreateHighReliablePhysicalConnectionRequest.d.ts +21 -21
  18. package/dist/models/CreateIpsecServerRequest.d.ts +2 -2
  19. package/dist/models/CreatePhysicalConnectionRequest.d.ts +16 -14
  20. package/dist/models/CreatePhysicalConnectionRequest.js.map +1 -1
  21. package/dist/models/CreatePhysicalConnectionSetupOrderRequest.d.ts +10 -8
  22. package/dist/models/CreatePhysicalConnectionSetupOrderRequest.js.map +1 -1
  23. package/dist/models/CreateSslVpnServerRequest.d.ts +11 -11
  24. package/dist/models/CreateVbrHaRequest.d.ts +5 -5
  25. package/dist/models/CreateVbrHaResponseBody.d.ts +1 -1
  26. package/dist/models/CreateVcoRouteEntryRequest.d.ts +2 -2
  27. package/dist/models/CreateVcoRouteEntryResponseBody.d.ts +1 -1
  28. package/dist/models/CreateVpconnFromVbrRequest.d.ts +2 -2
  29. package/dist/models/CreateVpnAttachmentRequest.d.ts +73 -133
  30. package/dist/models/CreateVpnAttachmentRequest.js.map +1 -1
  31. package/dist/models/CreateVpnAttachmentResponseBody.d.ts +3 -3
  32. package/dist/models/CreateVpnConnectionRequest.d.ts +95 -131
  33. package/dist/models/CreateVpnConnectionRequest.js.map +1 -1
  34. package/dist/models/CreateVpnConnectionResponseBody.d.ts +1 -1
  35. package/dist/models/CreateVpnGatewayRequest.d.ts +17 -17
  36. package/dist/models/CreateVpnGatewayResponseBody.d.ts +2 -2
  37. package/dist/models/CreateVpnPbrRouteEntryRequest.d.ts +13 -13
  38. package/dist/models/CreateVpnPbrRouteEntryResponseBody.d.ts +6 -6
  39. package/dist/models/CreateVswitchCidrReservationRequest.d.ts +15 -7
  40. package/dist/models/CreateVswitchCidrReservationRequest.js +2 -0
  41. package/dist/models/CreateVswitchCidrReservationRequest.js.map +1 -1
  42. package/dist/models/CreateVswitchRequest.d.ts +9 -9
  43. package/dist/models/DeleteBgpGroupRequest.d.ts +2 -2
  44. package/dist/models/DeleteFailoverTestJobRequest.d.ts +4 -4
  45. package/dist/models/DeleteIpsecServerRequest.d.ts +4 -4
  46. package/dist/models/DeleteNatGatewayRequest.d.ts +4 -4
  47. package/dist/models/DeleteVbrHaRequest.d.ts +3 -3
  48. package/dist/models/DeleteVpnGatewayRequest.d.ts +3 -3
  49. package/dist/models/DeleteVpnRouteEntryRequest.d.ts +2 -2
  50. package/dist/models/DescribeCustomerGatewayRequest.d.ts +1 -1
  51. package/dist/models/DescribeCustomerGatewayResponseBody.d.ts +2 -2
  52. package/dist/models/DescribeCustomerGatewaysRequest.d.ts +1 -1
  53. package/dist/models/DescribeEipAddressesRequest.d.ts +7 -75
  54. package/dist/models/DescribeEipAddressesRequest.js.map +1 -1
  55. package/dist/models/DescribeExpressConnectTrafficQosQueueRequest.d.ts +5 -3
  56. package/dist/models/DescribeExpressConnectTrafficQosQueueRequest.js.map +1 -1
  57. package/dist/models/DescribeExpressConnectTrafficQosQueueResponseBody.d.ts +12 -12
  58. package/dist/models/DescribeExpressConnectTrafficQosRuleRequest.d.ts +10 -6
  59. package/dist/models/DescribeExpressConnectTrafficQosRuleRequest.js.map +1 -1
  60. package/dist/models/DescribeExpressConnectTrafficQosRuleResponseBody.d.ts +16 -16
  61. package/dist/models/DescribeFailoverTestJobRequest.d.ts +2 -2
  62. package/dist/models/DescribeFailoverTestJobResponseBody.d.ts +6 -6
  63. package/dist/models/DescribeFailoverTestJobsRequest.d.ts +8 -8
  64. package/dist/models/DescribeFailoverTestJobsResponseBody.d.ts +14 -14
  65. package/dist/models/DescribeFlowLogsRequest.d.ts +9 -9
  66. package/dist/models/DescribeFlowLogsResponseBody.d.ts +1 -1
  67. package/dist/models/DescribePhysicalConnectionLoarequest.d.ts +1 -1
  68. package/dist/models/DescribePhysicalConnectionLoaresponseBody.d.ts +8 -4
  69. package/dist/models/DescribePhysicalConnectionLoaresponseBody.js.map +1 -1
  70. package/dist/models/DescribePhysicalConnectionsRequest.d.ts +2 -53
  71. package/dist/models/DescribePhysicalConnectionsRequest.js.map +1 -1
  72. package/dist/models/DescribePhysicalConnectionsResponseBody.d.ts +2 -0
  73. package/dist/models/DescribePhysicalConnectionsResponseBody.js +4 -0
  74. package/dist/models/DescribePhysicalConnectionsResponseBody.js.map +1 -1
  75. package/dist/models/DescribeRouterInterfaceAttributeResponseBody.d.ts +22 -22
  76. package/dist/models/DescribeSslVpnClientCertRequest.d.ts +1 -1
  77. package/dist/models/DescribeSslVpnClientCertResponseBody.d.ts +3 -3
  78. package/dist/models/DescribeSslVpnServersRequest.d.ts +1 -1
  79. package/dist/models/DescribeSslVpnServersResponseBody.d.ts +1 -1
  80. package/dist/models/DescribeTagKeysForExpressConnectRequest.d.ts +2 -0
  81. package/dist/models/DescribeTagKeysForExpressConnectRequest.js.map +1 -1
  82. package/dist/models/DescribeVbrHaRequest.d.ts +6 -6
  83. package/dist/models/DescribeVbrHaResponseBody.d.ts +2 -2
  84. package/dist/models/DescribeVcoRouteEntriesResponseBody.d.ts +10 -10
  85. package/dist/models/DescribeVirtualBorderRoutersRequest.d.ts +6 -26
  86. package/dist/models/DescribeVirtualBorderRoutersRequest.js.map +1 -1
  87. package/dist/models/DescribeVirtualBorderRoutersResponseBody.d.ts +2 -2
  88. package/dist/models/DescribeVpcsRequest.d.ts +4 -4
  89. package/dist/models/DescribeVpcsResponseBody.d.ts +1 -1
  90. package/dist/models/DescribeVpnAttachmentsRequest.d.ts +4 -4
  91. package/dist/models/DescribeVpnAttachmentsResponseBody.d.ts +9 -9
  92. package/dist/models/DescribeVpnConnectionLogsRequest.d.ts +2 -2
  93. package/dist/models/DescribeVpnConnectionLogsResponseBody.d.ts +1 -1
  94. package/dist/models/DescribeVpnConnectionRequest.d.ts +1 -1
  95. package/dist/models/DescribeVpnConnectionResponseBody.d.ts +21 -72
  96. package/dist/models/DescribeVpnConnectionResponseBody.js.map +1 -1
  97. package/dist/models/DescribeVpnConnectionsRequest.d.ts +6 -8
  98. package/dist/models/DescribeVpnConnectionsRequest.js.map +1 -1
  99. package/dist/models/DescribeVpnCrossAccountAuthorizationsRequest.d.ts +2 -2
  100. package/dist/models/DescribeVpnCrossAccountAuthorizationsResponseBody.d.ts +5 -5
  101. package/dist/models/DescribeVpnGatewayResponseBody.d.ts +8 -8
  102. package/dist/models/DescribeVpnGatewaysRequest.d.ts +2 -2
  103. package/dist/models/DescribeVpnGatewaysResponseBody.d.ts +1 -1
  104. package/dist/models/DescribeVpnPbrRouteEntriesRequest.d.ts +1 -1
  105. package/dist/models/DescribeVpnPbrRouteEntriesResponseBody.d.ts +1 -1
  106. package/dist/models/DescribeVpnSslServerLogsRequest.d.ts +2 -2
  107. package/dist/models/DescribeVswitchesRequest.d.ts +7 -7
  108. package/dist/models/DescribeVswitchesResponseBody.d.ts +1 -1
  109. package/dist/models/DiagnoseVpnGatewayRequest.d.ts +1 -1
  110. package/dist/models/DiagnoseVpnGatewayResponseBody.d.ts +2 -2
  111. package/dist/models/DisassociateMacSecKeyRequest.d.ts +2 -2
  112. package/dist/models/DissociateVpnGatewayWithCertificateRequest.d.ts +2 -2
  113. package/dist/models/DownloadVpnConnectionConfigResponseBody.d.ts +11 -11
  114. package/dist/models/GetVpnGatewayDiagnoseResultRequest.d.ts +3 -3
  115. package/dist/models/GetVpnGatewayDiagnoseResultResponseBody.d.ts +12 -12
  116. package/dist/models/GrantInstanceToVbrRequest.d.ts +8 -8
  117. package/dist/models/GrantInstanceToVbrShrinkRequest.d.ts +8 -8
  118. package/dist/models/ListBusinessAccessPointsResponseBody.d.ts +40 -2
  119. package/dist/models/ListBusinessAccessPointsResponseBody.js.map +1 -1
  120. package/dist/models/ListIpsecServerLogsRequest.d.ts +2 -2
  121. package/dist/models/ListIpsecServerLogsResponseBody.d.ts +1 -1
  122. package/dist/models/ListIpsecServersRequest.d.ts +3 -3
  123. package/dist/models/ListIpsecServersResponseBody.d.ts +7 -7
  124. package/dist/models/ListVpnCertificateAssociationsRequest.d.ts +3 -3
  125. package/dist/models/ListVpnCertificateAssociationsResponseBody.d.ts +2 -2
  126. package/dist/models/ModifyCustomerGatewayAttributeRequest.d.ts +1 -1
  127. package/dist/models/ModifyFlowLogAttributeRequest.d.ts +1 -1
  128. package/dist/models/ModifyPhysicalConnectionAttributeRequest.d.ts +16 -15
  129. package/dist/models/ModifyPhysicalConnectionAttributeRequest.js +2 -0
  130. package/dist/models/ModifyPhysicalConnectionAttributeRequest.js.map +1 -1
  131. package/dist/models/ModifySslVpnServerRequest.d.ts +11 -11
  132. package/dist/models/ModifySslVpnServerResponseBody.d.ts +1 -1
  133. package/dist/models/ModifyVcoRouteEntryWeightRequest.d.ts +4 -4
  134. package/dist/models/ModifyVpnAttachmentAttributeRequest.d.ts +57 -133
  135. package/dist/models/ModifyVpnAttachmentAttributeRequest.js.map +1 -1
  136. package/dist/models/ModifyVpnAttachmentAttributeResponseBody.d.ts +54 -96
  137. package/dist/models/ModifyVpnAttachmentAttributeResponseBody.js.map +1 -1
  138. package/dist/models/ModifyVpnConnectionAttributeRequest.d.ts +77 -148
  139. package/dist/models/ModifyVpnConnectionAttributeRequest.js.map +1 -1
  140. package/dist/models/ModifyVpnConnectionAttributeResponseBody.d.ts +25 -52
  141. package/dist/models/ModifyVpnConnectionAttributeResponseBody.js.map +1 -1
  142. package/dist/models/ModifyVpnGatewayAttributeRequest.d.ts +5 -5
  143. package/dist/models/ModifyVpnPbrRouteEntryPriorityRequest.d.ts +5 -5
  144. package/dist/models/ModifyVpnRouteEntryWeightRequest.d.ts +2 -2
  145. package/dist/models/MoveVpnResourceGroupRequest.d.ts +2 -2
  146. package/dist/models/UpdateIpsecServerRequest.d.ts +1 -1
  147. package/package.json +1 -1
  148. package/src/client.ts +286 -273
  149. package/src/models/ActivateRouterInterfaceRequest.ts +1 -1
  150. package/src/models/AssociateMacSecKeyRequest.ts +3 -3
  151. package/src/models/AssociatePhysicalConnectionToVirtualBorderRouterRequest.ts +5 -7
  152. package/src/models/AssociateVpnGatewayWithCertificateRequest.ts +3 -3
  153. package/src/models/AttachVbrToVpconnRequest.ts +3 -3
  154. package/src/models/CancelPhysicalConnectionRequest.ts +1 -1
  155. package/src/models/CheckVpnBgpEnabledRequest.ts +1 -1
  156. package/src/models/CompletePhysicalConnectionLoarequest.ts +4 -4
  157. package/src/models/CreateCustomerGatewayRequest.ts +4 -4
  158. package/src/models/CreateCustomerGatewayResponseBody.ts +2 -2
  159. package/src/models/CreateFailoverTestJobRequest.ts +5 -5
  160. package/src/models/CreateFlowLogRequest.ts +4 -4
  161. package/src/models/CreateHighReliablePhysicalConnectionRequest.ts +21 -21
  162. package/src/models/CreateIpsecServerRequest.ts +2 -2
  163. package/src/models/CreatePhysicalConnectionRequest.ts +16 -14
  164. package/src/models/CreatePhysicalConnectionSetupOrderRequest.ts +10 -8
  165. package/src/models/CreateSslVpnServerRequest.ts +11 -11
  166. package/src/models/CreateVbrHaRequest.ts +5 -5
  167. package/src/models/CreateVbrHaResponseBody.ts +1 -1
  168. package/src/models/CreateVcoRouteEntryRequest.ts +2 -2
  169. package/src/models/CreateVcoRouteEntryResponseBody.ts +1 -1
  170. package/src/models/CreateVpconnFromVbrRequest.ts +2 -2
  171. package/src/models/CreateVpnAttachmentRequest.ts +75 -135
  172. package/src/models/CreateVpnAttachmentResponseBody.ts +3 -3
  173. package/src/models/CreateVpnConnectionRequest.ts +99 -135
  174. package/src/models/CreateVpnConnectionResponseBody.ts +1 -1
  175. package/src/models/CreateVpnGatewayRequest.ts +17 -17
  176. package/src/models/CreateVpnGatewayResponseBody.ts +2 -2
  177. package/src/models/CreateVpnPbrRouteEntryRequest.ts +13 -13
  178. package/src/models/CreateVpnPbrRouteEntryResponseBody.ts +6 -6
  179. package/src/models/CreateVswitchCidrReservationRequest.ts +17 -7
  180. package/src/models/CreateVswitchRequest.ts +9 -9
  181. package/src/models/DeleteBgpGroupRequest.ts +2 -2
  182. package/src/models/DeleteFailoverTestJobRequest.ts +4 -4
  183. package/src/models/DeleteIpsecServerRequest.ts +4 -4
  184. package/src/models/DeleteNatGatewayRequest.ts +4 -4
  185. package/src/models/DeleteVbrHaRequest.ts +3 -3
  186. package/src/models/DeleteVpnGatewayRequest.ts +3 -3
  187. package/src/models/DeleteVpnRouteEntryRequest.ts +2 -2
  188. package/src/models/DescribeCustomerGatewayRequest.ts +1 -1
  189. package/src/models/DescribeCustomerGatewayResponseBody.ts +2 -2
  190. package/src/models/DescribeCustomerGatewaysRequest.ts +1 -1
  191. package/src/models/DescribeEipAddressesRequest.ts +8 -76
  192. package/src/models/DescribeExpressConnectTrafficQosQueueRequest.ts +5 -3
  193. package/src/models/DescribeExpressConnectTrafficQosQueueResponseBody.ts +12 -12
  194. package/src/models/DescribeExpressConnectTrafficQosRuleRequest.ts +10 -6
  195. package/src/models/DescribeExpressConnectTrafficQosRuleResponseBody.ts +16 -16
  196. package/src/models/DescribeFailoverTestJobRequest.ts +2 -2
  197. package/src/models/DescribeFailoverTestJobResponseBody.ts +6 -6
  198. package/src/models/DescribeFailoverTestJobsRequest.ts +8 -8
  199. package/src/models/DescribeFailoverTestJobsResponseBody.ts +14 -14
  200. package/src/models/DescribeFlowLogsRequest.ts +9 -9
  201. package/src/models/DescribeFlowLogsResponseBody.ts +1 -1
  202. package/src/models/DescribePhysicalConnectionLoarequest.ts +1 -1
  203. package/src/models/DescribePhysicalConnectionLoaresponseBody.ts +8 -4
  204. package/src/models/DescribePhysicalConnectionsRequest.ts +3 -54
  205. package/src/models/DescribePhysicalConnectionsResponseBody.ts +6 -0
  206. package/src/models/DescribeRouterInterfaceAttributeResponseBody.ts +22 -22
  207. package/src/models/DescribeSslVpnClientCertRequest.ts +1 -1
  208. package/src/models/DescribeSslVpnClientCertResponseBody.ts +3 -3
  209. package/src/models/DescribeSslVpnServersRequest.ts +1 -1
  210. package/src/models/DescribeSslVpnServersResponseBody.ts +1 -1
  211. package/src/models/DescribeTagKeysForExpressConnectRequest.ts +2 -0
  212. package/src/models/DescribeVbrHaRequest.ts +6 -6
  213. package/src/models/DescribeVbrHaResponseBody.ts +2 -2
  214. package/src/models/DescribeVcoRouteEntriesResponseBody.ts +10 -10
  215. package/src/models/DescribeVirtualBorderRoutersRequest.ts +6 -26
  216. package/src/models/DescribeVirtualBorderRoutersResponseBody.ts +2 -2
  217. package/src/models/DescribeVpcsRequest.ts +4 -4
  218. package/src/models/DescribeVpcsResponseBody.ts +1 -1
  219. package/src/models/DescribeVpnAttachmentsRequest.ts +4 -4
  220. package/src/models/DescribeVpnAttachmentsResponseBody.ts +9 -9
  221. package/src/models/DescribeVpnConnectionLogsRequest.ts +2 -2
  222. package/src/models/DescribeVpnConnectionLogsResponseBody.ts +1 -1
  223. package/src/models/DescribeVpnConnectionRequest.ts +2 -2
  224. package/src/models/DescribeVpnConnectionResponseBody.ts +21 -72
  225. package/src/models/DescribeVpnConnectionsRequest.ts +7 -9
  226. package/src/models/DescribeVpnCrossAccountAuthorizationsRequest.ts +2 -2
  227. package/src/models/DescribeVpnCrossAccountAuthorizationsResponseBody.ts +5 -5
  228. package/src/models/DescribeVpnGatewayResponseBody.ts +8 -8
  229. package/src/models/DescribeVpnGatewaysRequest.ts +2 -2
  230. package/src/models/DescribeVpnGatewaysResponseBody.ts +1 -1
  231. package/src/models/DescribeVpnPbrRouteEntriesRequest.ts +1 -1
  232. package/src/models/DescribeVpnPbrRouteEntriesResponseBody.ts +1 -1
  233. package/src/models/DescribeVpnSslServerLogsRequest.ts +2 -2
  234. package/src/models/DescribeVswitchesRequest.ts +7 -7
  235. package/src/models/DescribeVswitchesResponseBody.ts +1 -1
  236. package/src/models/DiagnoseVpnGatewayRequest.ts +1 -1
  237. package/src/models/DiagnoseVpnGatewayResponseBody.ts +2 -2
  238. package/src/models/DisassociateMacSecKeyRequest.ts +2 -2
  239. package/src/models/DissociateVpnGatewayWithCertificateRequest.ts +2 -2
  240. package/src/models/DownloadVpnConnectionConfigResponseBody.ts +11 -11
  241. package/src/models/GetVpnGatewayDiagnoseResultRequest.ts +3 -3
  242. package/src/models/GetVpnGatewayDiagnoseResultResponseBody.ts +12 -12
  243. package/src/models/GrantInstanceToVbrRequest.ts +8 -8
  244. package/src/models/GrantInstanceToVbrShrinkRequest.ts +8 -8
  245. package/src/models/ListBusinessAccessPointsResponseBody.ts +40 -2
  246. package/src/models/ListIpsecServerLogsRequest.ts +2 -2
  247. package/src/models/ListIpsecServerLogsResponseBody.ts +1 -1
  248. package/src/models/ListIpsecServersRequest.ts +3 -3
  249. package/src/models/ListIpsecServersResponseBody.ts +7 -7
  250. package/src/models/ListVpnCertificateAssociationsRequest.ts +3 -3
  251. package/src/models/ListVpnCertificateAssociationsResponseBody.ts +2 -2
  252. package/src/models/ModifyCustomerGatewayAttributeRequest.ts +1 -1
  253. package/src/models/ModifyFlowLogAttributeRequest.ts +1 -1
  254. package/src/models/ModifyPhysicalConnectionAttributeRequest.ts +18 -15
  255. package/src/models/ModifySslVpnServerRequest.ts +11 -11
  256. package/src/models/ModifySslVpnServerResponseBody.ts +1 -1
  257. package/src/models/ModifyVcoRouteEntryWeightRequest.ts +4 -4
  258. package/src/models/ModifyVpnAttachmentAttributeRequest.ts +57 -133
  259. package/src/models/ModifyVpnAttachmentAttributeResponseBody.ts +55 -97
  260. package/src/models/ModifyVpnConnectionAttributeRequest.ts +84 -155
  261. package/src/models/ModifyVpnConnectionAttributeResponseBody.ts +26 -53
  262. package/src/models/ModifyVpnGatewayAttributeRequest.ts +5 -5
  263. package/src/models/ModifyVpnPbrRouteEntryPriorityRequest.ts +5 -5
  264. package/src/models/ModifyVpnRouteEntryWeightRequest.ts +2 -2
  265. package/src/models/MoveVpnResourceGroupRequest.ts +2 -2
  266. package/src/models/UpdateIpsecServerRequest.ts +1 -1
package/src/client.ts CHANGED
@@ -49,41 +49,42 @@ 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
- 'us-west-1': "vpc.us-west-1.aliyuncs.com",
53
- 'us-southeast-1': "vpc.us-southeast-1.aliyuncs.com",
54
- 'us-east-1': "vpc.us-east-1.aliyuncs.com",
55
- 'na-south-1': "vpc.na-south-1.aliyuncs.com",
56
- 'me-east-1': "vpc.me-east-1.aliyuncs.com",
57
- 'me-central-1': "vpc.me-central-1.aliyuncs.com",
58
- 'eu-west-2': "vpc.eu-west-2.aliyuncs.com",
59
- 'eu-west-1': "vpc.eu-west-1.aliyuncs.com",
60
- 'eu-central-1': "vpc.eu-central-1.aliyuncs.com",
61
- 'cn-zhongwei': "vpc.cn-zhongwei.aliyuncs.com",
62
- 'cn-zhengzhou-jva': "vpc.cn-zhengzhou-jva.aliyuncs.com",
52
+ 'cn-beijing': "vpc.cn-beijing.aliyuncs.com",
53
+ 'cn-heyuan': "vpc.cn-heyuan.aliyuncs.com",
63
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
64
  'cn-wulanchabu': "vpc.cn-wulanchabu.aliyuncs.com",
65
+ 'cn-qingdao': "vpc.cn-qingdao.aliyuncs.com",
65
66
  'cn-wuhan-lr': "vpc.cn-wuhan-lr.aliyuncs.com",
66
- 'cn-shenzhen': "vpc.cn-shenzhen.aliyuncs.com",
67
67
  'cn-shanghai': "vpc.cn-shanghai.aliyuncs.com",
68
- 'cn-qingdao': "vpc.cn-qingdao.aliyuncs.com",
69
- 'cn-nanjing': "vpc.cn-nanjing.aliyuncs.com",
70
- 'cn-huhehaote': "vpc.cn-huhehaote.aliyuncs.com",
71
68
  'cn-hongkong': "vpc.cn-hongkong.aliyuncs.com",
72
- 'cn-heyuan-acdr-1': "vpc.cn-heyuan-acdr-1.aliyuncs.com",
73
- 'cn-heyuan': "vpc.cn-heyuan.aliyuncs.com",
74
- 'cn-guangzhou': "vpc.cn-guangzhou.aliyuncs.com",
69
+ 'cn-shenzhen': "vpc.cn-shenzhen.aliyuncs.com",
70
+ 'cn-nanjing': "vpc.cn-nanjing.aliyuncs.com",
75
71
  'cn-fuzhou': "vpc.cn-fuzhou.aliyuncs.com",
76
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",
77
85
  'cn-beijing-finance-1': "vpc.cn-beijing-finance-1.aliyuncs.com",
78
- 'cn-beijing': "vpc.cn-beijing.aliyuncs.com",
79
- 'ap-southeast-8': "vpc.ap-southeast-8.aliyuncs.com",
80
- 'ap-southeast-7': "vpc.ap-southeast-7.aliyuncs.com",
81
- 'ap-southeast-6': "vpc.ap-southeast-6.aliyuncs.com",
82
- 'ap-southeast-5': "vpc.ap-southeast-5.aliyuncs.com",
83
- 'ap-southeast-3': "vpc.ap-southeast-3.aliyuncs.com",
84
- 'ap-southeast-1': "vpc.ap-southeast-1.aliyuncs.com",
85
- 'ap-northeast-2': "vpc.ap-northeast-2.aliyuncs.com",
86
- 'ap-northeast-1': "vpc.ap-northeast-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",
87
88
  };
88
89
  this.checkConfig(config);
89
90
  this._endpoint = this.getEndpoint("vpc", this._regionId, this._endpointRule, this._network, this._suffix, this._endpointMap, this._endpoint);
@@ -106,7 +107,8 @@ export default class Client extends OpenApi {
106
107
  * Activates a router interface that is in the Inactive state.
107
108
  *
108
109
  * @remarks
109
- * After you call the ActivateRouterInterface operation, the router interface enters the **Activating** state. After the router interface is activated, it enters the **Active** state.
110
+ * After you call the ActivateRouterInterface operation, the router interface enters the **Activating** state and then enters the **Active** state after activation succeeds.
111
+ * Before you call this operation, the router interface must be in the **Inactive** state. The initial state of a newly created router interface is **Idle**. In non-express connect mode, you can call CreateRouterInterface to create both ends of the connection, call ModifyRouterInterfaceAttribute to configure peer information for each end, and then call ConnectRouterInterface to establish the connection. When the interface is in the **Active** state, you can call DeactivateRouterInterface to change it to the **Inactive** state, and then call this operation to reactivate it. You can call DescribeRouterInterfaceAttribute to query the current state.
110
112
  * > You cannot activate a router interface that has an overdue payment.
111
113
  *
112
114
  * @param request - ActivateRouterInterfaceRequest
@@ -157,7 +159,8 @@ export default class Client extends OpenApi {
157
159
  * Activates a router interface that is in the Inactive state.
158
160
  *
159
161
  * @remarks
160
- * After you call the ActivateRouterInterface operation, the router interface enters the **Activating** state. After the router interface is activated, it enters the **Active** state.
162
+ * After you call the ActivateRouterInterface operation, the router interface enters the **Activating** state and then enters the **Active** state after activation succeeds.
163
+ * Before you call this operation, the router interface must be in the **Inactive** state. The initial state of a newly created router interface is **Idle**. In non-express connect mode, you can call CreateRouterInterface to create both ends of the connection, call ModifyRouterInterfaceAttribute to configure peer information for each end, and then call ConnectRouterInterface to establish the connection. When the interface is in the **Active** state, you can call DeactivateRouterInterface to change it to the **Inactive** state, and then call this operation to reactivate it. You can call DescribeRouterInterfaceAttribute to query the current state.
161
164
  * > You cannot activate a router interface that has an overdue payment.
162
165
  *
163
166
  * @param request - ActivateRouterInterfaceRequest
@@ -1899,7 +1902,7 @@ export default class Client extends OpenApi {
1899
1902
  }
1900
1903
 
1901
1904
  /**
1902
- * Associates a MACsec key with a dedicated Express Connect circuit port. MACsec uses dedicated encryption chips (such as NICs or switches) to implement low-latency encryption and decryption, directly encrypting physical links (such as optical fiber or Ethernet) to cover all traffic from sender to receiver.
1905
+ * Associates a MACsec key with a dedicated Express Connect circuit port. MACsec uses dedicated encryption chips (such as NICs or switches) to implement low-latency encryption and decryption, directly encrypting physical links (such as optical fibers or Ethernet) to cover all traffic from the sender to the receiver.
1903
1906
  *
1904
1907
  * @remarks
1905
1908
  * To use this feature, the following conditions must be met:
@@ -1908,7 +1911,7 @@ export default class Client extends OpenApi {
1908
1911
  * - Only dedicated Express Connect circuits are supported.
1909
1912
  * Other notes:
1910
1913
  * - A maximum of three CKN and CAK pairs can be configured.
1911
- * - Associating a key that is currently in the Disassociated state cancels the previously associated key.
1914
+ * - Associating a key that is currently in the Disassociated state disassociates the previously active key.
1912
1915
  * - Associating a key that is currently in the AssociatedFailed state triggers the device to renegotiate the session.
1913
1916
  *
1914
1917
  * @param request - AssociateMacSecKeyRequest
@@ -1956,7 +1959,7 @@ export default class Client extends OpenApi {
1956
1959
  }
1957
1960
 
1958
1961
  /**
1959
- * Associates a MACsec key with a dedicated Express Connect circuit port. MACsec uses dedicated encryption chips (such as NICs or switches) to implement low-latency encryption and decryption, directly encrypting physical links (such as optical fiber or Ethernet) to cover all traffic from sender to receiver.
1962
+ * Associates a MACsec key with a dedicated Express Connect circuit port. MACsec uses dedicated encryption chips (such as NICs or switches) to implement low-latency encryption and decryption, directly encrypting physical links (such as optical fibers or Ethernet) to cover all traffic from the sender to the receiver.
1960
1963
  *
1961
1964
  * @remarks
1962
1965
  * To use this feature, the following conditions must be met:
@@ -1965,7 +1968,7 @@ export default class Client extends OpenApi {
1965
1968
  * - Only dedicated Express Connect circuits are supported.
1966
1969
  * Other notes:
1967
1970
  * - A maximum of three CKN and CAK pairs can be configured.
1968
- * - Associating a key that is currently in the Disassociated state cancels the previously associated key.
1971
+ * - Associating a key that is currently in the Disassociated state disassociates the previously active key.
1969
1972
  * - Associating a key that is currently in the AssociatedFailed state triggers the device to renegotiate the session.
1970
1973
  *
1971
1974
  * @param request - AssociateMacSecKeyRequest
@@ -2548,18 +2551,18 @@ export default class Client extends OpenApi {
2548
2551
  * Associates a certificate with a VPN gateway by calling the AssociateVpnGatewayWithCertificate operation.
2549
2552
  *
2550
2553
  * @remarks
2551
- * Before you attach a VPN gateway to an SSL certificate, take note of the following information:
2552
- * - Only Chinese SM VPN gateways support SSL certificate attachment. You must attach two SSL certificates to a Chinese SM VPN gateway: one as the encryption certificate and the other as the signing certificate.
2553
- * - The SSL certificates must use Chinese SM algorithms.
2554
+ * Before you associate a VPN gateway with an SSL certificate, take note of the following information:
2555
+ * - Only ShangMi (SM) VPN gateways support SSL certificate binding. You must attach two SSL certificates to an SM VPN gateway: one as the encryption certificate and the other as the signing certificate.
2556
+ * - The SSL certificates must use SM algorithms.
2554
2557
  * - You cannot specify the same SSL certificate as both the encryption certificate and the signing certificate for the same VPN gateway instance.
2555
2558
  * <props="china">
2556
- * - When you attach a VPN gateway to an SSL certificate for the first time, the system performs automatic creation of a service-linked role named AliyunServiceRoleForVPNCertificate and adds the access policy AliyunServiceRolePolicyForVPNCertificate to the role. This grants the VPN gateway permissions to access other cloud resources. For more information, see [AliyunServiceRoleForVPNCertificate](https://help.aliyun.com/document_detail/203323.html).
2557
- * - The **AssociateVpnGatewayWithCertificate** operation is asynchronous. After you send a request, the system returns a request ID, but the SSL certificate is not yet attached to the VPN gateway. The attachment node continues to run in the background. You can invoke the [DescribeVpnGateway](https://help.aliyun.com/document_detail/73720.html) operation to query the attachment status of the SSL certificate:
2559
+ * - When you attach a VPN gateway to an SSL certificate for the first time, the system performs automatic creation of a service-linked role named AliyunServiceRoleForVPNCertificate and adds the access policy named AliyunServiceRolePolicyForVPNCertificate to the role. This grants the VPN gateway permissions to access other cloud resources. For more information, see [AliyunServiceRoleForVPNCertificate](https://help.aliyun.com/document_detail/203323.html).
2560
+ * - The **AssociateVpnGatewayWithCertificate** operation is asynchronous. After you send a request, the system returns a request ID, but the SSL certificate is not yet attached to the VPN gateway. The binding node continues to run in the background. You can invoke the [DescribeVpnGateway](https://help.aliyun.com/document_detail/73720.html) operation to query the binding status of the SSL certificate:
2558
2561
  * - If the VPN gateway is in the **updating** state, the SSL certificate is being attached.
2559
2562
  * - If the VPN gateway is in the **active** state, the SSL certificate is attached.
2560
- * - The **AssociateVpnGatewayWithCertificate** operation does not support concurrent SSL certificate attachment for the same VPN gateway.
2563
+ * - The **AssociateVpnGatewayWithCertificate** operation does not support concurrent SSL certificate binding requests for the same VPN gateway.
2561
2564
  * ### Before you begin
2562
- * Make sure that you have two SSL certificates that use Chinese SM algorithms in the Alibaba Cloud Certificate Management Service console. For more information about SSL certificates, see [What is Certificate Management Service?](https://help.aliyun.com/document_detail/28535.html).
2565
+ * Make sure that you have two SSL certificates that use SM algorithms in the Alibaba Cloud Certificate Management Service console. For more information about SSL certificates, see [What is Certificate Management Service?](https://help.aliyun.com/document_detail/28535.html).
2563
2566
  *
2564
2567
  * @param request - AssociateVpnGatewayWithCertificateRequest
2565
2568
  * @param runtime - runtime options for this request RuntimeOptions
@@ -2613,18 +2616,18 @@ export default class Client extends OpenApi {
2613
2616
  * Associates a certificate with a VPN gateway by calling the AssociateVpnGatewayWithCertificate operation.
2614
2617
  *
2615
2618
  * @remarks
2616
- * Before you attach a VPN gateway to an SSL certificate, take note of the following information:
2617
- * - Only Chinese SM VPN gateways support SSL certificate attachment. You must attach two SSL certificates to a Chinese SM VPN gateway: one as the encryption certificate and the other as the signing certificate.
2618
- * - The SSL certificates must use Chinese SM algorithms.
2619
+ * Before you associate a VPN gateway with an SSL certificate, take note of the following information:
2620
+ * - Only ShangMi (SM) VPN gateways support SSL certificate binding. You must attach two SSL certificates to an SM VPN gateway: one as the encryption certificate and the other as the signing certificate.
2621
+ * - The SSL certificates must use SM algorithms.
2619
2622
  * - You cannot specify the same SSL certificate as both the encryption certificate and the signing certificate for the same VPN gateway instance.
2620
2623
  * <props="china">
2621
- * - When you attach a VPN gateway to an SSL certificate for the first time, the system performs automatic creation of a service-linked role named AliyunServiceRoleForVPNCertificate and adds the access policy AliyunServiceRolePolicyForVPNCertificate to the role. This grants the VPN gateway permissions to access other cloud resources. For more information, see [AliyunServiceRoleForVPNCertificate](https://help.aliyun.com/document_detail/203323.html).
2622
- * - The **AssociateVpnGatewayWithCertificate** operation is asynchronous. After you send a request, the system returns a request ID, but the SSL certificate is not yet attached to the VPN gateway. The attachment node continues to run in the background. You can invoke the [DescribeVpnGateway](https://help.aliyun.com/document_detail/73720.html) operation to query the attachment status of the SSL certificate:
2624
+ * - When you attach a VPN gateway to an SSL certificate for the first time, the system performs automatic creation of a service-linked role named AliyunServiceRoleForVPNCertificate and adds the access policy named AliyunServiceRolePolicyForVPNCertificate to the role. This grants the VPN gateway permissions to access other cloud resources. For more information, see [AliyunServiceRoleForVPNCertificate](https://help.aliyun.com/document_detail/203323.html).
2625
+ * - The **AssociateVpnGatewayWithCertificate** operation is asynchronous. After you send a request, the system returns a request ID, but the SSL certificate is not yet attached to the VPN gateway. The binding node continues to run in the background. You can invoke the [DescribeVpnGateway](https://help.aliyun.com/document_detail/73720.html) operation to query the binding status of the SSL certificate:
2623
2626
  * - If the VPN gateway is in the **updating** state, the SSL certificate is being attached.
2624
2627
  * - If the VPN gateway is in the **active** state, the SSL certificate is attached.
2625
- * - The **AssociateVpnGatewayWithCertificate** operation does not support concurrent SSL certificate attachment for the same VPN gateway.
2628
+ * - The **AssociateVpnGatewayWithCertificate** operation does not support concurrent SSL certificate binding requests for the same VPN gateway.
2626
2629
  * ### Before you begin
2627
- * Make sure that you have two SSL certificates that use Chinese SM algorithms in the Alibaba Cloud Certificate Management Service console. For more information about SSL certificates, see [What is Certificate Management Service?](https://help.aliyun.com/document_detail/28535.html).
2630
+ * Make sure that you have two SSL certificates that use SM algorithms in the Alibaba Cloud Certificate Management Service console. For more information about SSL certificates, see [What is Certificate Management Service?](https://help.aliyun.com/document_detail/28535.html).
2628
2631
  *
2629
2632
  * @param request - AssociateVpnGatewayWithCertificateRequest
2630
2633
  * @returns AssociateVpnGatewayWithCertificateResponse
@@ -2855,10 +2858,10 @@ export default class Client extends OpenApi {
2855
2858
  }
2856
2859
 
2857
2860
  /**
2858
- * Cancels access to an Express Connect circuit. After the cancellation, the Express Connect circuit enters the Canceled state.
2861
+ * Cancels the access of an Express Connect circuit. After the cancellation, the Express Connect circuit enters the Canceled state.
2859
2862
  *
2860
2863
  * @remarks
2861
- * You can cancel access only for Express Connect circuits in the **Initial**, **Approved**, **Allocated**, or **Confirmed** state (not yet activated).
2864
+ * You can cancel the access of an Express Connect circuit only when it is in the **Initial**, **Approved**, **Allocated**, or **Confirmed** state (not enabled). After an Express Connect circuit is created by calling CreatePhysicalConnection, it may briefly be in the **Allocating** state, during which it cannot be canceled. Poll the status by calling DescribePhysicalConnections and call this operation after the state changes to **Allocated**.
2862
2865
  *
2863
2866
  * @param request - CancelPhysicalConnectionRequest
2864
2867
  * @param runtime - runtime options for this request RuntimeOptions
@@ -2913,10 +2916,10 @@ export default class Client extends OpenApi {
2913
2916
  }
2914
2917
 
2915
2918
  /**
2916
- * Cancels access to an Express Connect circuit. After the cancellation, the Express Connect circuit enters the Canceled state.
2919
+ * Cancels the access of an Express Connect circuit. After the cancellation, the Express Connect circuit enters the Canceled state.
2917
2920
  *
2918
2921
  * @remarks
2919
- * You can cancel access only for Express Connect circuits in the **Initial**, **Approved**, **Allocated**, or **Confirmed** state (not yet activated).
2922
+ * You can cancel the access of an Express Connect circuit only when it is in the **Initial**, **Approved**, **Allocated**, or **Confirmed** state (not enabled). After an Express Connect circuit is created by calling CreatePhysicalConnection, it may briefly be in the **Allocating** state, during which it cannot be canceled. Poll the status by calling DescribePhysicalConnections and call this operation after the state changes to **Allocated**.
2920
2923
  *
2921
2924
  * @param request - CancelPhysicalConnectionRequest
2922
2925
  * @returns CancelPhysicalConnectionResponse
@@ -3063,7 +3066,7 @@ export default class Client extends OpenApi {
3063
3066
  }
3064
3067
 
3065
3068
  /**
3066
- * Calls the CheckVpnBgpEnabled operation to query whether the region of an IPsec-VPN connection supports the BGP feature.
3069
+ * Calls the CheckVpnBgpEnabled operation to query whether the region to which an IPsec-VPN connection belongs supports the BGP feature.
3067
3070
  *
3068
3071
  * @param request - CheckVpnBgpEnabledRequest
3069
3072
  * @param runtime - runtime options for this request RuntimeOptions
@@ -3110,7 +3113,7 @@ export default class Client extends OpenApi {
3110
3113
  }
3111
3114
 
3112
3115
  /**
3113
- * Calls the CheckVpnBgpEnabled operation to query whether the region of an IPsec-VPN connection supports the BGP feature.
3116
+ * Calls the CheckVpnBgpEnabled operation to query whether the region to which an IPsec-VPN connection belongs supports the BGP feature.
3114
3117
  *
3115
3118
  * @param request - CheckVpnBgpEnabledRequest
3116
3119
  * @returns CheckVpnBgpEnabledResponse
@@ -3121,7 +3124,10 @@ export default class Client extends OpenApi {
3121
3124
  }
3122
3125
 
3123
3126
  /**
3124
- * Calls CompletePhysicalConnectionLOA to complete the construction.
3127
+ * Completes the construction acceptance for an Express Connect circuit.
3128
+ *
3129
+ * @remarks
3130
+ * Completes the construction acceptance by calling the CompletePhysicalConnectionLOA operation. Before calling this operation, call DescribePhysicalConnectionLOA to query the LOA status. This operation can be called only when the status is **Available** or **Complete**. After an LOA application is submitted, the status changes to **Applying**. After the application is approved, the status changes to **Available**. If the application is rejected, the status changes to **Rejected**. For a rejected application, call SecondApplyPhysicalConnectionLOA to resubmit the application. After the construction acceptance is completed, the LOA status changes to **Complete**.
3125
3131
  *
3126
3132
  * @param request - CompletePhysicalConnectionLOARequest
3127
3133
  * @param runtime - runtime options for this request RuntimeOptions
@@ -3200,7 +3206,10 @@ export default class Client extends OpenApi {
3200
3206
  }
3201
3207
 
3202
3208
  /**
3203
- * Calls CompletePhysicalConnectionLOA to complete the construction.
3209
+ * Completes the construction acceptance for an Express Connect circuit.
3210
+ *
3211
+ * @remarks
3212
+ * Completes the construction acceptance by calling the CompletePhysicalConnectionLOA operation. Before calling this operation, call DescribePhysicalConnectionLOA to query the LOA status. This operation can be called only when the status is **Available** or **Complete**. After an LOA application is submitted, the status changes to **Applying**. After the application is approved, the status changes to **Available**. If the application is rejected, the status changes to **Rejected**. For a rejected application, call SecondApplyPhysicalConnectionLOA to resubmit the application. After the construction acceptance is completed, the LOA status changes to **Complete**.
3204
3213
  *
3205
3214
  * @param request - CompletePhysicalConnectionLOARequest
3206
3215
  * @returns CompletePhysicalConnectionLOAResponse
@@ -4661,7 +4670,7 @@ export default class Client extends OpenApi {
4661
4670
  *
4662
4671
  * @remarks
4663
4672
  * You cannot create a failover test job in the following scenarios:
4664
- * - A failover test job is already running in the current region, and the job type of the new failover test job is set to StartNow.
4673
+ * - A failover test job is already running in the current region and the job type of the new failover test job is set to StartNow.
4665
4674
  * - The Express Connect circuit instance or shared Express Connect circuit instance has not been paid for or has an overdue payment.
4666
4675
  * - The Express Connect circuit instance or shared Express Connect circuit instance is already in another running failover test job.
4667
4676
  *
@@ -4751,7 +4760,7 @@ export default class Client extends OpenApi {
4751
4760
  *
4752
4761
  * @remarks
4753
4762
  * You cannot create a failover test job in the following scenarios:
4754
- * - A failover test job is already running in the current region, and the job type of the new failover test job is set to StartNow.
4763
+ * - A failover test job is already running in the current region and the job type of the new failover test job is set to StartNow.
4755
4764
  * - The Express Connect circuit instance or shared Express Connect circuit instance has not been paid for or has an overdue payment.
4756
4765
  * - The Express Connect circuit instance or shared Express Connect circuit instance is already in another running failover test job.
4757
4766
  *
@@ -4772,7 +4781,7 @@ export default class Client extends OpenApi {
4772
4781
  * Creates a flow log.
4773
4782
  *
4774
4783
  * @remarks
4775
- * *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 continues in the background. You can invoke [DescribeFlowLogs](https://help.aliyun.com/document_detail/448670.html) to query the creation status of the flow log:
4784
+ * *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:
4776
4785
  * - If the flow log is in the **Activating** state, the flow log is being created.
4777
4786
  * - If the flow log is in the **Active** state, the flow log is created and activated.
4778
4787
  *
@@ -4876,7 +4885,7 @@ export default class Client extends OpenApi {
4876
4885
  * Creates a flow log.
4877
4886
  *
4878
4887
  * @remarks
4879
- * *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 continues in the background. You can invoke [DescribeFlowLogs](https://help.aliyun.com/document_detail/448670.html) to query the creation status of the flow log:
4888
+ * *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:
4880
4889
  * - If the flow log is in the **Activating** state, the flow log is being created.
4881
4890
  * - If the flow log is in the **Active** state, the flow log is created and activated.
4882
4891
  *
@@ -5322,10 +5331,10 @@ export default class Client extends OpenApi {
5322
5331
  }
5323
5332
 
5324
5333
  /**
5325
- * Creates Express Connect circuits in zone redundancy mode to ensure service stability through multi-line access to Alibaba Cloud and to avoid service disruption caused by single-line failures through multi-line disaster recovery.
5334
+ * Creates Express Connect circuits in zone redundancy mode to ensure service stability through multi-line access to Alibaba Cloud and to prevent service disruptions caused by single-line failures through multi-line disaster recovery.
5326
5335
  *
5327
5336
  * @remarks
5328
- * When you purchase ports, you can select one of the following combination types to provide disaster recovery capabilities for your business or workloads.
5337
+ * When you purchase ports, you can select one of the following three combination types to provide disaster recovery capabilities for your business or workloads.
5329
5338
  * - Maximum disaster recovery: You apply for resources in two access points and establish four independent Express Connect circuit connections. The SLA availability for maximum disaster recovery is no less than 99.99%.
5330
5339
  * - Enhanced disaster recovery: You apply for resources in two access points and establish two independent Express Connect circuit connections. The SLA availability for enhanced disaster recovery is no less than 99.95%.
5331
5340
  * - Development and testing: You apply for resources in one access point and establish two independent Express Connect circuit connections.
@@ -5415,10 +5424,10 @@ export default class Client extends OpenApi {
5415
5424
  }
5416
5425
 
5417
5426
  /**
5418
- * Creates Express Connect circuits in zone redundancy mode to ensure service stability through multi-line access to Alibaba Cloud and to avoid service disruption caused by single-line failures through multi-line disaster recovery.
5427
+ * Creates Express Connect circuits in zone redundancy mode to ensure service stability through multi-line access to Alibaba Cloud and to prevent service disruptions caused by single-line failures through multi-line disaster recovery.
5419
5428
  *
5420
5429
  * @remarks
5421
- * When you purchase ports, you can select one of the following combination types to provide disaster recovery capabilities for your business or workloads.
5430
+ * When you purchase ports, you can select one of the following three combination types to provide disaster recovery capabilities for your business or workloads.
5422
5431
  * - Maximum disaster recovery: You apply for resources in two access points and establish four independent Express Connect circuit connections. The SLA availability for maximum disaster recovery is no less than 99.99%.
5423
5432
  * - Enhanced disaster recovery: You apply for resources in two access points and establish two independent Express Connect circuit connections. The SLA availability for enhanced disaster recovery is no less than 99.95%.
5424
5433
  * - Development and testing: You apply for resources in one access point and establish two independent Express Connect circuit connections.
@@ -7830,7 +7839,7 @@ export default class Client extends OpenApi {
7830
7839
  * Creates an SSL-VPN server.
7831
7840
  *
7832
7841
  * @remarks
7833
- * - **CreateSslVpnServer** is an asynchronous operation. After you call this operation, the system returns an instance ID but the SSL-VPN server is not yet created. The creation task is still running in the background. You can call [DescribeVpnGateway](https://help.aliyun.com/document_detail/2794055.html) to query the status of the VPN gateway instance to determine the creation status of the SSL-VPN server:
7842
+ * - **CreateSslVpnServer** is an asynchronous operation. After you call this operation, the system returns an instance ID but the SSL-VPN server is not yet created. The creation task continues in the background. You can call [DescribeVpnGateway](https://help.aliyun.com/document_detail/2794055.html) to query the status of the VPN gateway instance to determine the creation status of the SSL-VPN server:
7834
7843
  * - If the VPN gateway instance is in the **updating** state, the SSL-VPN server is being created.
7835
7844
  * - If the VPN gateway instance is in the **active** state, the SSL-VPN server is created.
7836
7845
  * - **CreateSslVpnServer** does not support concurrent creation of SSL-VPN servers under the same VPN gateway.
@@ -7946,7 +7955,7 @@ export default class Client extends OpenApi {
7946
7955
  * Creates an SSL-VPN server.
7947
7956
  *
7948
7957
  * @remarks
7949
- * - **CreateSslVpnServer** is an asynchronous operation. After you call this operation, the system returns an instance ID but the SSL-VPN server is not yet created. The creation task is still running in the background. You can call [DescribeVpnGateway](https://help.aliyun.com/document_detail/2794055.html) to query the status of the VPN gateway instance to determine the creation status of the SSL-VPN server:
7958
+ * - **CreateSslVpnServer** is an asynchronous operation. After you call this operation, the system returns an instance ID but the SSL-VPN server is not yet created. The creation task continues in the background. You can call [DescribeVpnGateway](https://help.aliyun.com/document_detail/2794055.html) to query the status of the VPN gateway instance to determine the creation status of the SSL-VPN server:
7950
7959
  * - If the VPN gateway instance is in the **updating** state, the SSL-VPN server is being created.
7951
7960
  * - If the VPN gateway instance is in the **active** state, the SSL-VPN server is created.
7952
7961
  * - **CreateSslVpnServer** does not support concurrent creation of SSL-VPN servers under the same VPN gateway.
@@ -8280,18 +8289,18 @@ export default class Client extends OpenApi {
8280
8289
  * Creates a vSwitch.
8281
8290
  *
8282
8291
  * @remarks
8283
- * Before you begin:
8292
+ * When you call this operation to create a vSwitch, take note of the following items:
8284
8293
  * - The number of vSwitches in each VPC cannot exceed 150.
8285
- * - 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.
8294
+ * - 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.
8286
8295
  * - 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).
8287
8296
  * - A cloud service instance can belong to only one vSwitch.
8288
8297
  * - vSwitches do not support multicast or broadcast.
8289
8298
  * - After a vSwitch is created, you cannot modify its CIDR block.
8290
- * - The **CreateVSwitch** operation is asynchronous. After you send a request, the system returns an instance ID, but the vSwitch is not yet created. The background node is still in progress. You can invoke [DescribeVSwitchAttributes](https://help.aliyun.com/document_detail/94567.html) to query the creation status of the vSwitch:
8291
- * - If the vSwitch is in the **Pending** state, the vSwitch is being configured.
8292
- * - If the vSwitch is in the **Available** state, the vSwitch is active.
8299
+ * - The **CreateVSwitch** operation is asynchronous. After you send a request, the system returns an instance ID but the vSwitch is not yet created. The background task is still in progress. You can call [DescribeVSwitchAttributes](https://help.aliyun.com/document_detail/94567.html) to query the creation status of the vSwitch:
8300
+ * - When the vSwitch is in the **Pending** state, the vSwitch is being configured.
8301
+ * - When the vSwitch is in the **Available** state, the vSwitch is available.
8293
8302
  * - The **CreateVSwitch** operation does not support concurrent creation of vSwitches in the same VPC.
8294
- * - The **CreateVSwitch** operation does not support creating vSwitches with the CIDR block 100.64.0.0/10 or its subnets.
8303
+ * - When you call the **CreateVSwitch** operation, the CIDR block of the vSwitch cannot be within the following reserved address ranges: 100.64.0.0/10, 127.0.0.0/8, 169.254.0.0/16, or 224.0.0.0/4.
8295
8304
  *
8296
8305
  * @param request - CreateVSwitchRequest
8297
8306
  * @param runtime - runtime options for this request RuntimeOptions
@@ -8377,18 +8386,18 @@ export default class Client extends OpenApi {
8377
8386
  * Creates a vSwitch.
8378
8387
  *
8379
8388
  * @remarks
8380
- * Before you begin:
8389
+ * When you call this operation to create a vSwitch, take note of the following items:
8381
8390
  * - The number of vSwitches in each VPC cannot exceed 150.
8382
- * - 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.
8391
+ * - 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.
8383
8392
  * - 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).
8384
8393
  * - A cloud service instance can belong to only one vSwitch.
8385
8394
  * - vSwitches do not support multicast or broadcast.
8386
8395
  * - After a vSwitch is created, you cannot modify its CIDR block.
8387
- * - The **CreateVSwitch** operation is asynchronous. After you send a request, the system returns an instance ID, but the vSwitch is not yet created. The background node is still in progress. You can invoke [DescribeVSwitchAttributes](https://help.aliyun.com/document_detail/94567.html) to query the creation status of the vSwitch:
8388
- * - If the vSwitch is in the **Pending** state, the vSwitch is being configured.
8389
- * - If the vSwitch is in the **Available** state, the vSwitch is active.
8396
+ * - The **CreateVSwitch** operation is asynchronous. After you send a request, the system returns an instance ID but the vSwitch is not yet created. The background task is still in progress. You can call [DescribeVSwitchAttributes](https://help.aliyun.com/document_detail/94567.html) to query the creation status of the vSwitch:
8397
+ * - When the vSwitch is in the **Pending** state, the vSwitch is being configured.
8398
+ * - When the vSwitch is in the **Available** state, the vSwitch is available.
8390
8399
  * - The **CreateVSwitch** operation does not support concurrent creation of vSwitches in the same VPC.
8391
- * - The **CreateVSwitch** operation does not support creating vSwitches with the CIDR block 100.64.0.0/10 or its subnets.
8400
+ * - When you call the **CreateVSwitch** operation, the CIDR block of the vSwitch cannot be within the following reserved address ranges: 100.64.0.0/10, 127.0.0.0/8, 169.254.0.0/16, or 224.0.0.0/4.
8392
8401
  *
8393
8402
  * @param request - CreateVSwitchRequest
8394
8403
  * @returns CreateVSwitchResponse
@@ -8407,7 +8416,7 @@ export default class Client extends OpenApi {
8407
8416
  * - A reserved CIDR block cannot contain the system reserved IP addresses of the vSwitch to which it belongs.
8408
8417
  * - IPv4 CIDR block: The first and last three IP addresses of the vSwitch are system reserved IP addresses.
8409
8418
  * - IPv6 CIDR block: The first and last nine IP addresses of the vSwitch are system reserved IP addresses.
8410
- * - 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:
8419
+ * - 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:
8411
8420
  * - If the reserved CIDR block for a vSwitch is in the **Assigning** state, the reserved CIDR block for a vSwitch is being allocated.
8412
8421
  * - If the reserved CIDR block for a vSwitch is in the **Assigned** state, the reserved CIDR block for a vSwitch has been allocated.
8413
8422
  *
@@ -8426,6 +8435,10 @@ export default class Client extends OpenApi {
8426
8435
  query["DryRun"] = request.dryRun;
8427
8436
  }
8428
8437
 
8438
+ if (!$dara.isNull(request.ipPrefixNumber)) {
8439
+ query["IpPrefixNumber"] = request.ipPrefixNumber;
8440
+ }
8441
+
8429
8442
  if (!$dara.isNull(request.ipVersion)) {
8430
8443
  query["IpVersion"] = request.ipVersion;
8431
8444
  }
@@ -8504,7 +8517,7 @@ export default class Client extends OpenApi {
8504
8517
  * - A reserved CIDR block cannot contain the system reserved IP addresses of the vSwitch to which it belongs.
8505
8518
  * - IPv4 CIDR block: The first and last three IP addresses of the vSwitch are system reserved IP addresses.
8506
8519
  * - IPv6 CIDR block: The first and last nine IP addresses of the vSwitch are system reserved IP addresses.
8507
- * - 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:
8520
+ * - 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:
8508
8521
  * - If the reserved CIDR block for a vSwitch is in the **Assigning** state, the reserved CIDR block for a vSwitch is being allocated.
8509
8522
  * - If the reserved CIDR block for a vSwitch is in the **Assigned** state, the reserved CIDR block for a vSwitch has been allocated.
8510
8523
  *
@@ -8517,7 +8530,7 @@ export default class Client extends OpenApi {
8517
8530
  }
8518
8531
 
8519
8532
  /**
8520
- * Creates a VBR failover group by calling the CreateVbrHa operation.
8533
+ * Creates a VBR failover group.
8521
8534
  *
8522
8535
  * @param request - CreateVbrHaRequest
8523
8536
  * @param runtime - runtime options for this request RuntimeOptions
@@ -8588,7 +8601,7 @@ export default class Client extends OpenApi {
8588
8601
  }
8589
8602
 
8590
8603
  /**
8591
- * Creates a VBR failover group by calling the CreateVbrHa operation.
8604
+ * Creates a VBR failover group.
8592
8605
  *
8593
8606
  * @param request - CreateVbrHaRequest
8594
8607
  * @returns CreateVbrHaResponse
@@ -8604,11 +8617,11 @@ export default class Client extends OpenApi {
8604
8617
  * @remarks
8605
8618
  * - The IPsec-VPN connection must be associated with a transit router instance. For more information, see [CreateTransitRouterVpnAttachment](https://help.aliyun.com/document_detail/468249.html).
8606
8619
  * - Adding a destination route with a destination CIDR block of 0.0.0.0/0 is not supported.
8607
- * - Do not add a destination route with a destination CIDR block of 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 route entries cause the console to fail to display the status of the IPsec-VPN connection or cause IPsec negotiation to fail.
8620
+ * - Do not add a destination route 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 route entries cause the console to fail to display the status of the IPsec-VPN connection or cause IPsec negotiation to fail.
8608
8621
  * - **CreateVcoRouteEntry** is an asynchronous operation. After you send a request, the system returns an instance ID but the destination route entry is not yet created. The creation task is still running in the background. You can call [DescribeVpnConnection](https://help.aliyun.com/document_detail/53046.html) to query the creation status of the destination route entry:
8609
8622
  * - If the IPsec-VPN connection is in the **updating** state, the destination route entry is being created.
8610
8623
  * - If the IPsec-VPN connection is in the **attached** state, the destination route entry is created.
8611
- * - **CreateVcoRouteEntry** does not support concurrent creation of destination route entries for the same IPsec-VPN connection.
8624
+ * - The **CreateVcoRouteEntry** operation does not support concurrent creation of destination route entries for the same IPsec-VPN connection.
8612
8625
  *
8613
8626
  * @param request - CreateVcoRouteEntryRequest
8614
8627
  * @param runtime - runtime options for this request RuntimeOptions
@@ -8688,11 +8701,11 @@ export default class Client extends OpenApi {
8688
8701
  * @remarks
8689
8702
  * - The IPsec-VPN connection must be associated with a transit router instance. For more information, see [CreateTransitRouterVpnAttachment](https://help.aliyun.com/document_detail/468249.html).
8690
8703
  * - Adding a destination route with a destination CIDR block of 0.0.0.0/0 is not supported.
8691
- * - Do not add a destination route with a destination CIDR block of 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 route entries cause the console to fail to display the status of the IPsec-VPN connection or cause IPsec negotiation to fail.
8704
+ * - Do not add a destination route 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 route entries cause the console to fail to display the status of the IPsec-VPN connection or cause IPsec negotiation to fail.
8692
8705
  * - **CreateVcoRouteEntry** is an asynchronous operation. After you send a request, the system returns an instance ID but the destination route entry is not yet created. The creation task is still running in the background. You can call [DescribeVpnConnection](https://help.aliyun.com/document_detail/53046.html) to query the creation status of the destination route entry:
8693
8706
  * - If the IPsec-VPN connection is in the **updating** state, the destination route entry is being created.
8694
8707
  * - If the IPsec-VPN connection is in the **attached** state, the destination route entry is created.
8695
- * - **CreateVcoRouteEntry** does not support concurrent creation of destination route entries for the same IPsec-VPN connection.
8708
+ * - The **CreateVcoRouteEntry** operation does not support concurrent creation of destination route entries for the same IPsec-VPN connection.
8696
8709
  *
8697
8710
  * @param request - CreateVcoRouteEntryRequest
8698
8711
  * @returns CreateVcoRouteEntryResponse
@@ -9283,13 +9296,13 @@ export default class Client extends OpenApi {
9283
9296
  }
9284
9297
 
9285
9298
  /**
9286
- * Transforms the sharing mode of shared Express Connect circuits from cross-account Virtual Border Router (VBR) routing push to cross-account shared port push.
9299
+ * Transforms the routing mode of shared Express Connect circuits from cross-account Virtual Border Router (VBR) push to cross-account shared port push.
9287
9300
  *
9288
9301
  * @remarks
9289
- * By invoking the CreateVpconnFromVbr operation, a partner can transform the sharing mode of shared Express Connect circuits used by a tenant from cross-account VBR push to cross-account shared port push. The transform procedure does not affect the tenant\\"s services.
9290
- * Before you execute the transform:
9302
+ * By invoking the CreateVpconnFromVbr operation, a partner can transform the routing mode of shared Express Connect circuits used by a tenant from cross-account VBR push to cross-account shared port push. The transform procedure does not affect the tenant\\"s services.
9303
+ * Before you execute the transform procedure:
9291
9304
  * The partner must notify the tenant about the service upgrade in advance and ensure that the tenant has enabled outbound traffic billing. For information about how to enable outbound traffic billing, see [Enable outbound traffic billing](https://help.aliyun.com/document_detail/274385.html).
9292
- * After the transform is complete:
9305
+ * After the transform procedure is complete:
9293
9306
  * 1. A shared port is added to the tenant\\"s account. The tenant must invoke the [ConfirmPhysicalConnection](https://help.aliyun.com/document_detail/324198.html) operation to accept the shared port.
9294
9307
  * 2. After the tenant accepts the shared port, the partner must invoke the [AttachVbrToVpconn](https://help.aliyun.com/document_detail/324191.html) operation to associate the VBR instance with the tenant\\"s shared Express Connect circuits instance.
9295
9308
  *
@@ -9338,13 +9351,13 @@ export default class Client extends OpenApi {
9338
9351
  }
9339
9352
 
9340
9353
  /**
9341
- * Transforms the sharing mode of shared Express Connect circuits from cross-account Virtual Border Router (VBR) routing push to cross-account shared port push.
9354
+ * Transforms the routing mode of shared Express Connect circuits from cross-account Virtual Border Router (VBR) push to cross-account shared port push.
9342
9355
  *
9343
9356
  * @remarks
9344
- * By invoking the CreateVpconnFromVbr operation, a partner can transform the sharing mode of shared Express Connect circuits used by a tenant from cross-account VBR push to cross-account shared port push. The transform procedure does not affect the tenant\\"s services.
9345
- * Before you execute the transform:
9357
+ * By invoking the CreateVpconnFromVbr operation, a partner can transform the routing mode of shared Express Connect circuits used by a tenant from cross-account VBR push to cross-account shared port push. The transform procedure does not affect the tenant\\"s services.
9358
+ * Before you execute the transform procedure:
9346
9359
  * The partner must notify the tenant about the service upgrade in advance and ensure that the tenant has enabled outbound traffic billing. For information about how to enable outbound traffic billing, see [Enable outbound traffic billing](https://help.aliyun.com/document_detail/274385.html).
9347
- * After the transform is complete:
9360
+ * After the transform procedure is complete:
9348
9361
  * 1. A shared port is added to the tenant\\"s account. The tenant must invoke the [ConfirmPhysicalConnection](https://help.aliyun.com/document_detail/324198.html) operation to accept the shared port.
9349
9362
  * 2. After the tenant accepts the shared port, the partner must invoke the [AttachVbrToVpconn](https://help.aliyun.com/document_detail/324191.html) operation to associate the VBR instance with the tenant\\"s shared Express Connect circuits instance.
9350
9363
  *
@@ -9357,16 +9370,11 @@ export default class Client extends OpenApi {
9357
9370
  }
9358
9371
 
9359
9372
  /**
9360
- * Creates an IPsec-VPN connection for bindng to a transit router instance by calling the CreateVpnAttachment operation.
9373
+ * Creates an IPsec-VPN connection to be associated with a transit router instance by calling the CreateVpnAttachment operation.
9361
9374
  *
9362
9375
  * @remarks
9363
9376
  * >Notice:
9364
- * - In the transit router binding scenario, IPsec-VPN connections have been upgraded to dual-tunnel mode. When you create an IPsec-VPN connection, in addition to the required request parameters, only the following dual-tunnel mode-related request parameters are supported: **ClientToken**, **Name**, **NetworkType**, **EffectImmediately**, **Tags** array, **ResourceGroupId**, **TunnelOptionsSpecification** array, and **EnableTunnelsBgp**. For more information, see [Dual-tunnel IPsec-VPN connections bound to transit routers](https://help.aliyun.com/document_detail/2853535.html).
9365
- * - An IPsec-VPN connection created by calling the `CreateVpnAttachment` operation is not bound to any resource by default. You can call the [CreateTransitRouterVpnAttachment](https://help.aliyun.com/document_detail/443993.html) operation to bind the IPsec-VPN connection to a transit router instance. After the IPsec-VPN connection is bound to a transit router instance, the system allocates a gateway IP address to the IPsec-VPN connection. You can call the [DescribeVpnConnection](https://help.aliyun.com/document_detail/2526951.html) operation to view the gateway IP address.
9366
- * ### Before you begin
9367
- * Before you create an IPsec-VPN connection, make sure that you have created a customer gateway in the region where the IPsec-VPN connection resides. For more information, see [CreateCustomerGateway](https://help.aliyun.com/document_detail/120368.html).
9368
- *
9369
- * If you want to add BGP configurations to the IPsec-VPN connection, make sure that an autonomous system number has been added to the customer gateway.
9377
+ * ### Before you begin.
9370
9378
  *
9371
9379
  * @param request - CreateVpnAttachmentRequest
9372
9380
  * @param runtime - runtime options for this request RuntimeOptions
@@ -9500,16 +9508,11 @@ export default class Client extends OpenApi {
9500
9508
  }
9501
9509
 
9502
9510
  /**
9503
- * Creates an IPsec-VPN connection for bindng to a transit router instance by calling the CreateVpnAttachment operation.
9511
+ * Creates an IPsec-VPN connection to be associated with a transit router instance by calling the CreateVpnAttachment operation.
9504
9512
  *
9505
9513
  * @remarks
9506
9514
  * >Notice:
9507
- * - In the transit router binding scenario, IPsec-VPN connections have been upgraded to dual-tunnel mode. When you create an IPsec-VPN connection, in addition to the required request parameters, only the following dual-tunnel mode-related request parameters are supported: **ClientToken**, **Name**, **NetworkType**, **EffectImmediately**, **Tags** array, **ResourceGroupId**, **TunnelOptionsSpecification** array, and **EnableTunnelsBgp**. For more information, see [Dual-tunnel IPsec-VPN connections bound to transit routers](https://help.aliyun.com/document_detail/2853535.html).
9508
- * - An IPsec-VPN connection created by calling the `CreateVpnAttachment` operation is not bound to any resource by default. You can call the [CreateTransitRouterVpnAttachment](https://help.aliyun.com/document_detail/443993.html) operation to bind the IPsec-VPN connection to a transit router instance. After the IPsec-VPN connection is bound to a transit router instance, the system allocates a gateway IP address to the IPsec-VPN connection. You can call the [DescribeVpnConnection](https://help.aliyun.com/document_detail/2526951.html) operation to view the gateway IP address.
9509
- * ### Before you begin
9510
- * Before you create an IPsec-VPN connection, make sure that you have created a customer gateway in the region where the IPsec-VPN connection resides. For more information, see [CreateCustomerGateway](https://help.aliyun.com/document_detail/120368.html).
9511
- *
9512
- * If you want to add BGP configurations to the IPsec-VPN connection, make sure that an autonomous system number has been added to the customer gateway.
9515
+ * ### Before you begin.
9513
9516
  *
9514
9517
  * @param request - CreateVpnAttachmentRequest
9515
9518
  * @returns CreateVpnAttachmentResponse
@@ -9526,11 +9529,8 @@ export default class Client extends OpenApi {
9526
9529
  * - If the VPN gateway instance supports creating IPsec-VPN connections in dual-tunnel mode, you can configure the following request parameters in addition to the required parameters when you call the `CreateVpnConnection` operation:
9527
9530
  * **ClientToken**, **Name**, **EffectImmediately**, **AutoConfigRoute**, **Tags** array, **TunnelOptionsSpecification** array, and **EnableTunnelsBgp**.
9528
9531
  * For information about the regions and zones that support IPsec-VPN connections in dual-tunnel mode, see [Upgrade an IPsec-VPN connection to dual-tunnel mode](https://help.aliyun.com/document_detail/2358946.html).
9529
- * - If the VPN gateway instance supports only creating IPsec-VPN connections in single-tunnel mode, you can configure the following request parameters in addition to the required parameters when you call the `CreateVpnConnection` operation:
9530
9532
  * **ClientToken**, **CustomerGatewayId**, **Name**, **EffectImmediately**, **IkeConfig**, **IpsecConfig**, **HealthCheckConfig**, **AutoConfigRoute**, **EnableDpd**, **EnableNatTraversal**, **BgpConfig**, **RemoteCaCertificate**, and **Tags** array.
9531
- * - The **CreateVpnConnection** operation is asynchronous. After you send a request, the system returns an instance ID, but the IPsec-VPN connection is not yet created. The creation task is still running in the background. You can call [DescribeVpnGateway](https://help.aliyun.com/document_detail/73720.html) to query the status of the VPN gateway instance to determine the creation status of the IPsec-VPN connection:
9532
- * - If the VPN gateway instance is in the **updating** state, the IPsec-VPN connection is being created.
9533
- * - If the VPN gateway instance is in the **active** state, the IPsec-VPN connection is created.
9533
+ * - The **CreateVpnConnection** operation is asynchronous. After you send a request, the system returns an instance ID, but the IPsec-VPN connection is not yet created. The creation task is still running in the background. You can call [DescribeVpnGateway](https://help.aliyun.com/document_detail/73720.html) to query the status of the VPN gateway instance to determine the creation status of the IPsec-VPN connection.
9534
9534
  * - The **CreateVpnConnection** operation does not support concurrent creation of IPsec-VPN connections under the same VPN gateway.
9535
9535
  *
9536
9536
  * @param request - CreateVpnConnectionRequest
@@ -9667,11 +9667,8 @@ export default class Client extends OpenApi {
9667
9667
  * - If the VPN gateway instance supports creating IPsec-VPN connections in dual-tunnel mode, you can configure the following request parameters in addition to the required parameters when you call the `CreateVpnConnection` operation:
9668
9668
  * **ClientToken**, **Name**, **EffectImmediately**, **AutoConfigRoute**, **Tags** array, **TunnelOptionsSpecification** array, and **EnableTunnelsBgp**.
9669
9669
  * For information about the regions and zones that support IPsec-VPN connections in dual-tunnel mode, see [Upgrade an IPsec-VPN connection to dual-tunnel mode](https://help.aliyun.com/document_detail/2358946.html).
9670
- * - If the VPN gateway instance supports only creating IPsec-VPN connections in single-tunnel mode, you can configure the following request parameters in addition to the required parameters when you call the `CreateVpnConnection` operation:
9671
9670
  * **ClientToken**, **CustomerGatewayId**, **Name**, **EffectImmediately**, **IkeConfig**, **IpsecConfig**, **HealthCheckConfig**, **AutoConfigRoute**, **EnableDpd**, **EnableNatTraversal**, **BgpConfig**, **RemoteCaCertificate**, and **Tags** array.
9672
- * - The **CreateVpnConnection** operation is asynchronous. After you send a request, the system returns an instance ID, but the IPsec-VPN connection is not yet created. The creation task is still running in the background. You can call [DescribeVpnGateway](https://help.aliyun.com/document_detail/73720.html) to query the status of the VPN gateway instance to determine the creation status of the IPsec-VPN connection:
9673
- * - If the VPN gateway instance is in the **updating** state, the IPsec-VPN connection is being created.
9674
- * - If the VPN gateway instance is in the **active** state, the IPsec-VPN connection is created.
9671
+ * - The **CreateVpnConnection** operation is asynchronous. After you send a request, the system returns an instance ID, but the IPsec-VPN connection is not yet created. The creation task is still running in the background. You can call [DescribeVpnGateway](https://help.aliyun.com/document_detail/73720.html) to query the status of the VPN gateway instance to determine the creation status of the IPsec-VPN connection.
9675
9672
  * - The **CreateVpnConnection** operation does not support concurrent creation of IPsec-VPN connections under the same VPN gateway.
9676
9673
  *
9677
9674
  * @param request - CreateVpnConnectionRequest
@@ -9686,8 +9683,8 @@ export default class Client extends OpenApi {
9686
9683
  * Creates a VPN gateway.
9687
9684
  *
9688
9685
  * @remarks
9689
- * - Before you create a VPN gateway, familiarize yourself with the limits of VPN gateways. For more information, see [VPN gateway limits](https://help.aliyun.com/document_detail/65290.html).
9690
- * - VPN gateway instances in some regions support only dual-tunnel IPsec-VPN connections by default. When you call the `CreateVpnGateway` operation to create a VPN gateway instance in these regions, you must specify the **VSwitchId** and **DisasterRecoveryVSwitchId** parameters in addition to the required parameters. For information about the regions and zones that support dual-tunnel IPsec-VPN connections, see [Upgrade an IPsec-VPN connection to dual-tunnel mode](https://help.aliyun.com/document_detail/2358946.html).
9686
+ * - Before you create a VPN gateway, we recommend that you familiarize yourself with the limits of VPN gateways. For more information, see [VPN gateway limits](https://help.aliyun.com/document_detail/65290.html).
9687
+ * - VPN gateway instances in some regions support only dual-tunnel mode IPsec-VPN connections by default. When you call the `CreateVpnGateway` operation to create a VPN gateway instance in these regions, you must specify the **VSwitchId** and **DisasterRecoveryVSwitchId** parameters in addition to the required parameters. For information about the regions and zones that support dual-tunnel mode IPsec-VPN connections, see [Upgrade an IPsec-VPN connection to dual-tunnel mode](https://help.aliyun.com/document_detail/2358946.html).
9691
9688
  * - The **CreateVpnGateway** operation is asynchronous. After you call this operation, the system returns an instance ID, but the VPN gateway is not yet created. The creation task is still running in the background. You can call [DescribeVpnGateway](https://help.aliyun.com/document_detail/73720.html) to query the creation status of the VPN gateway:
9692
9689
  *
9693
9690
  * - If the VPN gateway is in the **provisioning** state, the VPN gateway is being created.
@@ -9801,8 +9798,8 @@ export default class Client extends OpenApi {
9801
9798
  * Creates a VPN gateway.
9802
9799
  *
9803
9800
  * @remarks
9804
- * - Before you create a VPN gateway, familiarize yourself with the limits of VPN gateways. For more information, see [VPN gateway limits](https://help.aliyun.com/document_detail/65290.html).
9805
- * - VPN gateway instances in some regions support only dual-tunnel IPsec-VPN connections by default. When you call the `CreateVpnGateway` operation to create a VPN gateway instance in these regions, you must specify the **VSwitchId** and **DisasterRecoveryVSwitchId** parameters in addition to the required parameters. For information about the regions and zones that support dual-tunnel IPsec-VPN connections, see [Upgrade an IPsec-VPN connection to dual-tunnel mode](https://help.aliyun.com/document_detail/2358946.html).
9801
+ * - Before you create a VPN gateway, we recommend that you familiarize yourself with the limits of VPN gateways. For more information, see [VPN gateway limits](https://help.aliyun.com/document_detail/65290.html).
9802
+ * - VPN gateway instances in some regions support only dual-tunnel mode IPsec-VPN connections by default. When you call the `CreateVpnGateway` operation to create a VPN gateway instance in these regions, you must specify the **VSwitchId** and **DisasterRecoveryVSwitchId** parameters in addition to the required parameters. For information about the regions and zones that support dual-tunnel mode IPsec-VPN connections, see [Upgrade an IPsec-VPN connection to dual-tunnel mode](https://help.aliyun.com/document_detail/2358946.html).
9806
9803
  * - The **CreateVpnGateway** operation is asynchronous. After you call this operation, the system returns an instance ID, but the VPN gateway is not yet created. The creation task is still running in the background. You can call [DescribeVpnGateway](https://help.aliyun.com/document_detail/73720.html) to query the creation status of the VPN gateway:
9807
9804
  *
9808
9805
  * - If the VPN gateway is in the **provisioning** state, the VPN gateway is being created.
@@ -9817,18 +9814,18 @@ export default class Client extends OpenApi {
9817
9814
  }
9818
9815
 
9819
9816
  /**
9820
- * Creates a policy-based route for a VPN gateway by calling the CreateVpnPbrRouteEntry operation.
9817
+ * Creates a VPN policy-based route by calling the CreateVpnPbrRouteEntry operation.
9821
9818
  *
9822
9819
  * @remarks
9823
9820
  * ### Before you begin
9824
- * - Before creating 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).
9825
- * - Before creating a policy-based route, we recommend that you understand 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).
9821
+ * - 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).
9822
+ * - 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).
9826
9823
  * ### Limits
9827
- * - Adding a policy-based route whose destination CIDR block is 0.0.0.0/0 is not supported.
9828
- * - Do not add a policy-based route 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 cause the console to fail to display instance status of the IPsec-VPN connection or cause IPsec-VPN connection negotiation failures.
9829
- * - The **CreateVpnPbrRouteEntry** operation is asynchronous. After you call this operation, the system returns the information about the policy-based route, but the route has not been created yet. The system creates the route in the background. You can call 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:
9824
+ * - Policy-based routes whose destination CIDR block is 0.0.0.0/0 are not supported.
9825
+ * - 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.
9826
+ * - 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:
9830
9827
  * - If the VPN gateway instance is in the **updating** state, the policy-based route is being created.
9831
- * - If the VPN gateway instance is in the **active** state, the policy-based route has been created.
9828
+ * - If the VPN gateway instance is in the **active** state, the policy-based route is created.
9832
9829
  * - The **CreateVpnPbrRouteEntry** operation does not support concurrent creation of policy-based routes for the same VPN gateway instance.
9833
9830
  *
9834
9831
  * @param request - CreateVpnPbrRouteEntryRequest
@@ -9920,18 +9917,18 @@ export default class Client extends OpenApi {
9920
9917
  }
9921
9918
 
9922
9919
  /**
9923
- * Creates a policy-based route for a VPN gateway by calling the CreateVpnPbrRouteEntry operation.
9920
+ * Creates a VPN policy-based route by calling the CreateVpnPbrRouteEntry operation.
9924
9921
  *
9925
9922
  * @remarks
9926
9923
  * ### Before you begin
9927
- * - Before creating 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).
9928
- * - Before creating a policy-based route, we recommend that you understand 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).
9924
+ * - 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).
9925
+ * - 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).
9929
9926
  * ### Limits
9930
- * - Adding a policy-based route whose destination CIDR block is 0.0.0.0/0 is not supported.
9931
- * - Do not add a policy-based route 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 cause the console to fail to display instance status of the IPsec-VPN connection or cause IPsec-VPN connection negotiation failures.
9932
- * - The **CreateVpnPbrRouteEntry** operation is asynchronous. After you call this operation, the system returns the information about the policy-based route, but the route has not been created yet. The system creates the route in the background. You can call 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:
9927
+ * - Policy-based routes whose destination CIDR block is 0.0.0.0/0 are not supported.
9928
+ * - 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.
9929
+ * - 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:
9933
9930
  * - If the VPN gateway instance is in the **updating** state, the policy-based route is being created.
9934
- * - If the VPN gateway instance is in the **active** state, the policy-based route has been created.
9931
+ * - If the VPN gateway instance is in the **active** state, the policy-based route is created.
9935
9932
  * - The **CreateVpnPbrRouteEntry** operation does not support concurrent creation of policy-based routes for the same VPN gateway instance.
9936
9933
  *
9937
9934
  * @param request - CreateVpnPbrRouteEntryRequest
@@ -10193,7 +10190,7 @@ export default class Client extends OpenApi {
10193
10190
  }
10194
10191
 
10195
10192
  /**
10196
- * Deletes a specified Border Gateway Protocol (BGP) group.
10193
+ * Deletes a specified BGP group.
10197
10194
  *
10198
10195
  * @param request - DeleteBgpGroupRequest
10199
10196
  * @param runtime - runtime options for this request RuntimeOptions
@@ -10248,7 +10245,7 @@ export default class Client extends OpenApi {
10248
10245
  }
10249
10246
 
10250
10247
  /**
10251
- * Deletes a specified Border Gateway Protocol (BGP) group.
10248
+ * Deletes a specified BGP group.
10252
10249
  *
10253
10250
  * @param request - DeleteBgpGroupRequest
10254
10251
  * @returns DeleteBgpGroupResponse
@@ -10979,10 +10976,10 @@ export default class Client extends OpenApi {
10979
10976
  }
10980
10977
 
10981
10978
  /**
10982
- * Deletes an Express Connect failover test job.
10979
+ * Deletes an Express Connect failover test job by calling the DeleteFailoverTestJob operation.
10983
10980
  *
10984
10981
  * @remarks
10985
- * Only failover test jobs in the **Pending** or **Completed** state can be deleted.
10982
+ * Only failover test jobs in the **Pending** or **Completed** state can be deleted. Before calling this operation, create a failover test job by calling CreateFailoverTestJob and obtain the **JobId**. If the test resource is an Express Connect circuit, the circuit must be in the **Enabled** state and its business status must be **Normal**.
10986
10983
  *
10987
10984
  * @param request - DeleteFailoverTestJobRequest
10988
10985
  * @param runtime - runtime options for this request RuntimeOptions
@@ -11037,10 +11034,10 @@ export default class Client extends OpenApi {
11037
11034
  }
11038
11035
 
11039
11036
  /**
11040
- * Deletes an Express Connect failover test job.
11037
+ * Deletes an Express Connect failover test job by calling the DeleteFailoverTestJob operation.
11041
11038
  *
11042
11039
  * @remarks
11043
- * Only failover test jobs in the **Pending** or **Completed** state can be deleted.
11040
+ * Only failover test jobs in the **Pending** or **Completed** state can be deleted. Before calling this operation, create a failover test job by calling CreateFailoverTestJob and obtain the **JobId**. If the test resource is an Express Connect circuit, the circuit must be in the **Enabled** state and its business status must be **Normal**.
11044
11041
  *
11045
11042
  * @param request - DeleteFailoverTestJobRequest
11046
11043
  * @returns DeleteFailoverTestJobResponse
@@ -11666,7 +11663,7 @@ export default class Client extends OpenApi {
11666
11663
  * Deletes an IPsec server.
11667
11664
  *
11668
11665
  * @remarks
11669
- * - **DeleteIpsecServer** is an asynchronous operation. After you send a request, the system returns a request ID. However, the IPsec server is not yet deleted. The deletion node is still running in the background. You can invoke [DescribeVpnGateway](https://help.aliyun.com/document_detail/2794055.html) to query the instance status of the VPN gateway and determine the deletion status of the IPsec server:
11666
+ * - **DeleteIpsecServer** is an asynchronous operation. After you send a request, the system returns a request ID, but the IPsec server is not yet deleted. The deletion node continues to run in the background. You can invoke [DescribeVpnGateway](https://help.aliyun.com/document_detail/2794055.html) to query the instance status of the VPN gateway to determine the deletion status of the IPsec server:
11670
11667
  * - If the VPN gateway instance is in the **updating** state, the IPsec server is being deleted.
11671
11668
  * - If the VPN gateway instance is in the **active** state, the IPsec server is deleted.
11672
11669
  * - **DeleteIpsecServer** does not support concurrent deletion of IPsec servers under the same VPN gateway.
@@ -11715,7 +11712,7 @@ export default class Client extends OpenApi {
11715
11712
  * Deletes an IPsec server.
11716
11713
  *
11717
11714
  * @remarks
11718
- * - **DeleteIpsecServer** is an asynchronous operation. After you send a request, the system returns a request ID. However, the IPsec server is not yet deleted. The deletion node is still running in the background. You can invoke [DescribeVpnGateway](https://help.aliyun.com/document_detail/2794055.html) to query the instance status of the VPN gateway and determine the deletion status of the IPsec server:
11715
+ * - **DeleteIpsecServer** is an asynchronous operation. After you send a request, the system returns a request ID, but the IPsec server is not yet deleted. The deletion node continues to run in the background. You can invoke [DescribeVpnGateway](https://help.aliyun.com/document_detail/2794055.html) to query the instance status of the VPN gateway to determine the deletion status of the IPsec server:
11719
11716
  * - If the VPN gateway instance is in the **updating** state, the IPsec server is being deleted.
11720
11717
  * - If the VPN gateway instance is in the **active** state, the IPsec server is deleted.
11721
11718
  * - **DeleteIpsecServer** does not support concurrent deletion of IPsec servers under the same VPN gateway.
@@ -12082,12 +12079,12 @@ export default class Client extends OpenApi {
12082
12079
  * Deletes a specified Internet NAT gateway.
12083
12080
  *
12084
12081
  * @remarks
12085
- * *DeleteNatGateway** is an asynchronous operation. After you send a request, the system returns a request ID. However, the NAT gateway is not immediately deleted. The deletion task runs in the background. You can call [DescribeNatGateways](https://help.aliyun.com/document_detail/36054.html) to query the status of the NAT gateway:
12082
+ * *DeleteNatGateway** is an asynchronous operation. After you send a request, the system returns a request ID. However, the NAT gateway is not immediately deleted. The deletion task runs in the background. You can call [DescribeNatGateways](https://www.alibabacloud.com/help/en/nat-gateway/developer-reference/api-vpc-2016-04-28-describenatgateways-natgws) to query the status of the NAT gateway:
12086
12083
  *
12087
12084
  * - If the NAT gateway is in the **Deleting** state, the NAT gateway is being deleted. In this state, you can only perform query operations.
12088
12085
  * - If the NAT gateway cannot be found, the NAT gateway is deleted.
12089
12086
  *
12090
- * > The deletion of a NAT gateway is irreversible. Proceed with caution.
12087
+ * > Deleting a NAT gateway is irreversible. Proceed with caution.
12091
12088
  *
12092
12089
  * @param request - DeleteNatGatewayRequest
12093
12090
  * @param runtime - runtime options for this request RuntimeOptions
@@ -12145,12 +12142,12 @@ export default class Client extends OpenApi {
12145
12142
  * Deletes a specified Internet NAT gateway.
12146
12143
  *
12147
12144
  * @remarks
12148
- * *DeleteNatGateway** is an asynchronous operation. After you send a request, the system returns a request ID. However, the NAT gateway is not immediately deleted. The deletion task runs in the background. You can call [DescribeNatGateways](https://help.aliyun.com/document_detail/36054.html) to query the status of the NAT gateway:
12145
+ * *DeleteNatGateway** is an asynchronous operation. After you send a request, the system returns a request ID. However, the NAT gateway is not immediately deleted. The deletion task runs in the background. You can call [DescribeNatGateways](https://www.alibabacloud.com/help/en/nat-gateway/developer-reference/api-vpc-2016-04-28-describenatgateways-natgws) to query the status of the NAT gateway:
12149
12146
  *
12150
12147
  * - If the NAT gateway is in the **Deleting** state, the NAT gateway is being deleted. In this state, you can only perform query operations.
12151
12148
  * - If the NAT gateway cannot be found, the NAT gateway is deleted.
12152
12149
  *
12153
- * > The deletion of a NAT gateway is irreversible. Proceed with caution.
12150
+ * > Deleting a NAT gateway is irreversible. Proceed with caution.
12154
12151
  *
12155
12152
  * @param request - DeleteNatGatewayRequest
12156
12153
  * @returns DeleteNatGatewayResponse
@@ -12411,10 +12408,10 @@ export default class Client extends OpenApi {
12411
12408
  }
12412
12409
 
12413
12410
  /**
12414
- * Deletes an Express Connect circuit connection.
12411
+ * Deletes an Express Connect circuit.
12415
12412
  *
12416
12413
  * @remarks
12417
- * You can delete only Express Connect circuit connections that are in the **Allocated**, **Confirmed**, **Rejected**, **Canceled**, **AllocationFailed**, or **Terminated** state.
12414
+ * You can delete only Express Connect circuits that are in the **Allocated**, **Confirmed**, **Rejected**, **Canceled**, **AllocationFailed**, or **Terminated** state.
12418
12415
  *
12419
12416
  * @param request - DeletePhysicalConnectionRequest
12420
12417
  * @param runtime - runtime options for this request RuntimeOptions
@@ -12469,10 +12466,10 @@ export default class Client extends OpenApi {
12469
12466
  }
12470
12467
 
12471
12468
  /**
12472
- * Deletes an Express Connect circuit connection.
12469
+ * Deletes an Express Connect circuit.
12473
12470
  *
12474
12471
  * @remarks
12475
- * You can delete only Express Connect circuit connections that are in the **Allocated**, **Confirmed**, **Rejected**, **Canceled**, **AllocationFailed**, or **Terminated** state.
12472
+ * You can delete only Express Connect circuits that are in the **Allocated**, **Confirmed**, **Rejected**, **Canceled**, **AllocationFailed**, or **Terminated** state.
12476
12473
  *
12477
12474
  * @param request - DeletePhysicalConnectionRequest
12478
12475
  * @returns DeletePhysicalConnectionResponse
@@ -13242,10 +13239,10 @@ export default class Client extends OpenApi {
13242
13239
  * Deletes an SSL server. After the SSL server is deleted, the system automatically deletes all SSL client certificates associated with the SSL server, and clients that have installed these SSL client certificates are automatically disconnected from the SSL-VPN connection.
13243
13240
  *
13244
13241
  * @remarks
13245
- * - **DeleteSslVpnServer** is an asynchronous operation. After you send a request, the system returns a request ID, but the SSL server has not yet been deleted. The deletion task continues to run in the background. You can call [DescribeVpnGateway](https://help.aliyun.com/document_detail/2794055.html) to query the status of the VPN gateway instance to determine the deletion status of the SSL server:
13242
+ * - The **DeleteSslVpnServer** operation is asynchronous. After you send a request, the system returns a request ID. However, the SSL server is not yet deleted. The deletion task is still running in the background. You can call [DescribeVpnGateway](https://help.aliyun.com/document_detail/2794055.html) to query the status of the VPN gateway instance to determine the deletion status of the SSL server:
13246
13243
  * - If the VPN gateway instance is in the **updating** state, the SSL server is being deleted.
13247
13244
  * - If the VPN gateway instance is in the **active** state, the SSL server is deleted.
13248
- * - **DeleteSslVpnServer** does not support concurrent deletion of SSL server instances under the same VPN gateway.
13245
+ * - The **DeleteSslVpnServer** operation does not support concurrent deletion of SSL servers under the same VPN gateway.
13249
13246
  *
13250
13247
  * @param request - DeleteSslVpnServerRequest
13251
13248
  * @param runtime - runtime options for this request RuntimeOptions
@@ -13303,10 +13300,10 @@ export default class Client extends OpenApi {
13303
13300
  * Deletes an SSL server. After the SSL server is deleted, the system automatically deletes all SSL client certificates associated with the SSL server, and clients that have installed these SSL client certificates are automatically disconnected from the SSL-VPN connection.
13304
13301
  *
13305
13302
  * @remarks
13306
- * - **DeleteSslVpnServer** is an asynchronous operation. After you send a request, the system returns a request ID, but the SSL server has not yet been deleted. The deletion task continues to run in the background. You can call [DescribeVpnGateway](https://help.aliyun.com/document_detail/2794055.html) to query the status of the VPN gateway instance to determine the deletion status of the SSL server:
13303
+ * - The **DeleteSslVpnServer** operation is asynchronous. After you send a request, the system returns a request ID. However, the SSL server is not yet deleted. The deletion task is still running in the background. You can call [DescribeVpnGateway](https://help.aliyun.com/document_detail/2794055.html) to query the status of the VPN gateway instance to determine the deletion status of the SSL server:
13307
13304
  * - If the VPN gateway instance is in the **updating** state, the SSL server is being deleted.
13308
13305
  * - If the VPN gateway instance is in the **active** state, the SSL server is deleted.
13309
- * - **DeleteSslVpnServer** does not support concurrent deletion of SSL server instances under the same VPN gateway.
13306
+ * - The **DeleteSslVpnServer** operation does not support concurrent deletion of SSL servers under the same VPN gateway.
13310
13307
  *
13311
13308
  * @param request - DeleteSslVpnServerRequest
13312
13309
  * @returns DeleteSslVpnServerResponse
@@ -13735,7 +13732,7 @@ export default class Client extends OpenApi {
13735
13732
  }
13736
13733
 
13737
13734
  /**
13738
- * Deletes a VBR failover group.
13735
+ * Calls DeleteVbrHa to delete a VBR failover group.
13739
13736
  *
13740
13737
  * @param request - DeleteVbrHaRequest
13741
13738
  * @param runtime - runtime options for this request RuntimeOptions
@@ -13790,7 +13787,7 @@ export default class Client extends OpenApi {
13790
13787
  }
13791
13788
 
13792
13789
  /**
13793
- * Deletes a VBR failover group.
13790
+ * Calls DeleteVbrHa to delete a VBR failover group.
13794
13791
  *
13795
13792
  * @param request - DeleteVbrHaRequest
13796
13793
  * @returns DeleteVbrHaResponse
@@ -13804,7 +13801,7 @@ export default class Client extends OpenApi {
13804
13801
  * Deletes a destination route entry from an IPsec-VPN connection.
13805
13802
  *
13806
13803
  * @remarks
13807
- * - **DeleteVcoRouteEntry** is an asynchronous operation. After you send a request, the system returns a request ID, but the destination route entry has not been deleted yet. The deletion task is still running in the background. You can call [DescribeVpnConnection](https://help.aliyun.com/document_detail/53046.html) to query the deletion status of the destination route entry:
13804
+ * - **DeleteVcoRouteEntry** is an asynchronous operation. After you send a request, the system returns a request ID, but the destination route entry is not yet deleted. The deletion task continues to run in the background. You can call [DescribeVpnConnection](https://help.aliyun.com/document_detail/53046.html) to query the deletion status of the destination route entry:
13808
13805
  * - If the IPsec-VPN connection is in the **updating** state, the destination route entry is being deleted.
13809
13806
  * - If the IPsec-VPN connection is in the **attached** state, the destination route entry is deleted.
13810
13807
  * - **DeleteVcoRouteEntry** does not support concurrent deletion of destination route entries for the same IPsec-VPN connection.
@@ -13877,7 +13874,7 @@ export default class Client extends OpenApi {
13877
13874
  * Deletes a destination route entry from an IPsec-VPN connection.
13878
13875
  *
13879
13876
  * @remarks
13880
- * - **DeleteVcoRouteEntry** is an asynchronous operation. After you send a request, the system returns a request ID, but the destination route entry has not been deleted yet. The deletion task is still running in the background. You can call [DescribeVpnConnection](https://help.aliyun.com/document_detail/53046.html) to query the deletion status of the destination route entry:
13877
+ * - **DeleteVcoRouteEntry** is an asynchronous operation. After you send a request, the system returns a request ID, but the destination route entry is not yet deleted. The deletion task continues to run in the background. You can call [DescribeVpnConnection](https://help.aliyun.com/document_detail/53046.html) to query the deletion status of the destination route entry:
13881
13878
  * - If the IPsec-VPN connection is in the **updating** state, the destination route entry is being deleted.
13882
13879
  * - If the IPsec-VPN connection is in the **attached** state, the destination route entry is deleted.
13883
13880
  * - **DeleteVcoRouteEntry** does not support concurrent deletion of destination route entries for the same IPsec-VPN connection.
@@ -14209,11 +14206,11 @@ export default class Client extends OpenApi {
14209
14206
  }
14210
14207
 
14211
14208
  /**
14212
- * Deletes an IPsec-VPN connection by calling the DeleteVpnAttachment operation.
14209
+ * Deletes an IPsec-VPN connection.
14213
14210
  *
14214
14211
  * @remarks
14215
- * - If the IPsec-VPN connection is associated with a transit router instance, disassociate the IPsec-VPN connection from the transit router instance before you delete the IPsec-VPN connection. For more information, see [DeleteTransitRouterVpnAttachment](https://help.aliyun.com/document_detail/468251.html).
14216
- * - If the IPsec-VPN connection is not associated with any resource, you can call the `DeleteVpnAttachment` operation to directly delete the IPsec-VPN connection.
14212
+ * - If the IPsec-VPN connection is bindded to a transit router instance, disassociate the IPsec-VPN connection from the transit router instance before you delete the IPsec-VPN connection. For more information, see [DeleteTransitRouterVpnAttachment](https://help.aliyun.com/document_detail/468251.html).
14213
+ * - If the IPsec-VPN connection is not bindded to any resource, you can call the `DeleteVpnAttachment` operation to directly delete the IPsec-VPN connection.
14217
14214
  *
14218
14215
  * @param request - DeleteVpnAttachmentRequest
14219
14216
  * @param runtime - runtime options for this request RuntimeOptions
@@ -14264,11 +14261,11 @@ export default class Client extends OpenApi {
14264
14261
  }
14265
14262
 
14266
14263
  /**
14267
- * Deletes an IPsec-VPN connection by calling the DeleteVpnAttachment operation.
14264
+ * Deletes an IPsec-VPN connection.
14268
14265
  *
14269
14266
  * @remarks
14270
- * - If the IPsec-VPN connection is associated with a transit router instance, disassociate the IPsec-VPN connection from the transit router instance before you delete the IPsec-VPN connection. For more information, see [DeleteTransitRouterVpnAttachment](https://help.aliyun.com/document_detail/468251.html).
14271
- * - If the IPsec-VPN connection is not associated with any resource, you can call the `DeleteVpnAttachment` operation to directly delete the IPsec-VPN connection.
14267
+ * - If the IPsec-VPN connection is bindded to a transit router instance, disassociate the IPsec-VPN connection from the transit router instance before you delete the IPsec-VPN connection. For more information, see [DeleteTransitRouterVpnAttachment](https://help.aliyun.com/document_detail/468251.html).
14268
+ * - If the IPsec-VPN connection is not bindded to any resource, you can call the `DeleteVpnAttachment` operation to directly delete the IPsec-VPN connection.
14272
14269
  *
14273
14270
  * @param request - DeleteVpnAttachmentRequest
14274
14271
  * @returns DeleteVpnAttachmentResponse
@@ -14282,7 +14279,7 @@ export default class Client extends OpenApi {
14282
14279
  * Deletes a specified IPsec-VPN connection.
14283
14280
  *
14284
14281
  * @remarks
14285
- * - **DeleteVpnConnection** is an asynchronous operation. After you send a request, the system returns a request ID, but the IPsec-VPN connection is not yet deleted. The deletion task continues to run in the background. You can call [DescribeVpnGateway](https://help.aliyun.com/document_detail/73720.html) to query the status of the VPN gateway instance and determine the deletion status of the IPsec-VPN connection:
14282
+ * - **DeleteVpnConnection** is an asynchronous operation. After you send a request, the system returns a request ID, but the IPsec-VPN connection is not yet deleted. The deletion task continues to run in the background. You can call [DescribeVpnGateway](https://help.aliyun.com/document_detail/73720.html) to query the status of the VPN gateway instance to determine the deletion status of the IPsec-VPN connection:
14286
14283
  * - If the VPN gateway instance is in the **updating** state, the IPsec-VPN connection is being deleted.
14287
14284
  * - If the VPN gateway instance is in the **active** state, the IPsec-VPN connection is deleted.
14288
14285
  * - **DeleteVpnConnection** does not support concurrent deletion of IPsec-VPN connections under the same VPN gateway.
@@ -14344,7 +14341,7 @@ export default class Client extends OpenApi {
14344
14341
  * Deletes a specified IPsec-VPN connection.
14345
14342
  *
14346
14343
  * @remarks
14347
- * - **DeleteVpnConnection** is an asynchronous operation. After you send a request, the system returns a request ID, but the IPsec-VPN connection is not yet deleted. The deletion task continues to run in the background. You can call [DescribeVpnGateway](https://help.aliyun.com/document_detail/73720.html) to query the status of the VPN gateway instance and determine the deletion status of the IPsec-VPN connection:
14344
+ * - **DeleteVpnConnection** is an asynchronous operation. After you send a request, the system returns a request ID, but the IPsec-VPN connection is not yet deleted. The deletion task continues to run in the background. You can call [DescribeVpnGateway](https://help.aliyun.com/document_detail/73720.html) to query the status of the VPN gateway instance to determine the deletion status of the IPsec-VPN connection:
14348
14345
  * - If the VPN gateway instance is in the **updating** state, the IPsec-VPN connection is being deleted.
14349
14346
  * - If the VPN gateway instance is in the **active** state, the IPsec-VPN connection is deleted.
14350
14347
  * - **DeleteVpnConnection** does not support concurrent deletion of IPsec-VPN connections under the same VPN gateway.
@@ -14362,7 +14359,7 @@ export default class Client extends OpenApi {
14362
14359
  * Deletes a specified VPN gateway.
14363
14360
  *
14364
14361
  * @remarks
14365
- * > You cannot delete a VPN gateway that has existing IPsec-VPN connections.
14362
+ * > You cannot delete a VPN gateway that has IPsec-VPN connections.
14366
14363
  *
14367
14364
  * @param request - DeleteVpnGatewayRequest
14368
14365
  * @param runtime - runtime options for this request RuntimeOptions
@@ -14420,7 +14417,7 @@ export default class Client extends OpenApi {
14420
14417
  * Deletes a specified VPN gateway.
14421
14418
  *
14422
14419
  * @remarks
14423
- * > You cannot delete a VPN gateway that has existing IPsec-VPN connections.
14420
+ * > You cannot delete a VPN gateway that has IPsec-VPN connections.
14424
14421
  *
14425
14422
  * @param request - DeleteVpnGatewayRequest
14426
14423
  * @returns DeleteVpnGatewayResponse
@@ -14536,7 +14533,7 @@ export default class Client extends OpenApi {
14536
14533
  * Deletes a VPN destination route by calling the DeleteVpnRouteEntry operation.
14537
14534
  *
14538
14535
  * @remarks
14539
- * - **DeleteVpnRouteEntry** is an asynchronous operation. After you send a request, the system returns a request ID. However, the VPN destination route is not yet deleted, and the deletion node is still running in the background. You can invoke [DescribeVpnGateway](https://help.aliyun.com/document_detail/73720.html) to query the instance status of the VPN gateway and determine the deletion status of the VPN destination routing:
14536
+ * - **DeleteVpnRouteEntry** is an asynchronous operation. After you send a request, the system returns a request ID. However, the VPN destination route is not yet deleted, and the deletion node is still running in the background. You can invoke [DescribeVpnGateway](https://help.aliyun.com/document_detail/73720.html) to query the instance status of the VPN gateway, and determine the deletion status of the VPN destination routing:
14540
14537
  * - If the VPN gateway instance is in the **updating** state, the VPN destination route is being deleted.
14541
14538
  * - If the VPN gateway instance is in the **active** state, the VPN destination route is deleted.
14542
14539
  * - **DeleteVpnRouteEntry** does not support concurrent deletion of VPN destination routes for the same VPN gateway.
@@ -14613,7 +14610,7 @@ export default class Client extends OpenApi {
14613
14610
  * Deletes a VPN destination route by calling the DeleteVpnRouteEntry operation.
14614
14611
  *
14615
14612
  * @remarks
14616
- * - **DeleteVpnRouteEntry** is an asynchronous operation. After you send a request, the system returns a request ID. However, the VPN destination route is not yet deleted, and the deletion node is still running in the background. You can invoke [DescribeVpnGateway](https://help.aliyun.com/document_detail/73720.html) to query the instance status of the VPN gateway and determine the deletion status of the VPN destination routing:
14613
+ * - **DeleteVpnRouteEntry** is an asynchronous operation. After you send a request, the system returns a request ID. However, the VPN destination route is not yet deleted, and the deletion node is still running in the background. You can invoke [DescribeVpnGateway](https://help.aliyun.com/document_detail/73720.html) to query the instance status of the VPN gateway, and determine the deletion status of the VPN destination routing:
14617
14614
  * - If the VPN gateway instance is in the **updating** state, the VPN destination route is being deleted.
14618
14615
  * - If the VPN gateway instance is in the **active** state, the VPN destination route is deleted.
14619
14616
  * - **DeleteVpnRouteEntry** does not support concurrent deletion of VPN destination routes for the same VPN gateway.
@@ -15367,10 +15364,10 @@ export default class Client extends OpenApi {
15367
15364
  }
15368
15365
 
15369
15366
  /**
15370
- * Queries Elastic IP Addresses (EIPs) created in a specified region.
15367
+ * Queries elastic IP addresses (EIPs) created in a specified region.
15371
15368
  *
15372
15369
  * @remarks
15373
- * Queries information about EIPs created in a specified region, including the bandwidth peak, billing method, and the type of instance currently attached with each EIP.
15370
+ * This operation queries information about EIPs created in a specified region, including the maximum bandwidth, billing method, and the type of instance currently attached to each EIP. If you frequently perform deep paging or page skipping, the **Throttling.DeepPageSkip** error code may be returned. Reduce the query frequency or use sequential pagination.
15374
15371
  *
15375
15372
  * @param request - DescribeEipAddressesRequest
15376
15373
  * @param runtime - runtime options for this request RuntimeOptions
@@ -15497,10 +15494,10 @@ export default class Client extends OpenApi {
15497
15494
  }
15498
15495
 
15499
15496
  /**
15500
- * Queries Elastic IP Addresses (EIPs) created in a specified region.
15497
+ * Queries elastic IP addresses (EIPs) created in a specified region.
15501
15498
  *
15502
15499
  * @remarks
15503
- * Queries information about EIPs created in a specified region, including the bandwidth peak, billing method, and the type of instance currently attached with each EIP.
15500
+ * This operation queries information about EIPs created in a specified region, including the maximum bandwidth, billing method, and the type of instance currently attached to each EIP. If you frequently perform deep paging or page skipping, the **Throttling.DeepPageSkip** error code may be returned. Reduce the query frequency or use sequential pagination.
15504
15501
  *
15505
15502
  * @param request - DescribeEipAddressesRequest
15506
15503
  * @returns DescribeEipAddressesResponse
@@ -15825,6 +15822,9 @@ export default class Client extends OpenApi {
15825
15822
  /**
15826
15823
  * Queries Express Connect QoS queues.
15827
15824
  *
15825
+ * @remarks
15826
+ * Before you call this operation, call CreateExpressConnectTrafficQos to create a QoS policy and obtain the **QosId**.
15827
+ *
15828
15828
  * @param request - DescribeExpressConnectTrafficQosQueueRequest
15829
15829
  * @param runtime - runtime options for this request RuntimeOptions
15830
15830
  * @returns DescribeExpressConnectTrafficQosQueueResponse
@@ -15888,6 +15888,9 @@ export default class Client extends OpenApi {
15888
15888
  /**
15889
15889
  * Queries Express Connect QoS queues.
15890
15890
  *
15891
+ * @remarks
15892
+ * Before you call this operation, call CreateExpressConnectTrafficQos to create a QoS policy and obtain the **QosId**.
15893
+ *
15891
15894
  * @param request - DescribeExpressConnectTrafficQosQueueRequest
15892
15895
  * @returns DescribeExpressConnectTrafficQosQueueResponse
15893
15896
  */
@@ -15975,7 +15978,7 @@ export default class Client extends OpenApi {
15975
15978
  }
15976
15979
 
15977
15980
  /**
15978
- * Queries the details of an Express Connect failover test job by calling the DescribeFailoverTestJob operation.
15981
+ * Queries the details of an Express Connect failover test job.
15979
15982
  *
15980
15983
  * @param request - DescribeFailoverTestJobRequest
15981
15984
  * @param runtime - runtime options for this request RuntimeOptions
@@ -16030,7 +16033,7 @@ export default class Client extends OpenApi {
16030
16033
  }
16031
16034
 
16032
16035
  /**
16033
- * Queries the details of an Express Connect failover test job by calling the DescribeFailoverTestJob operation.
16036
+ * Queries the details of an Express Connect failover test job.
16034
16037
  *
16035
16038
  * @param request - DescribeFailoverTestJobRequest
16036
16039
  * @returns DescribeFailoverTestJobResponse
@@ -16041,7 +16044,7 @@ export default class Client extends OpenApi {
16041
16044
  }
16042
16045
 
16043
16046
  /**
16044
- * Queries failover test jobs of Express Connect in batches.
16047
+ * Queries Express Connect failover test jobs in batches.
16045
16048
  *
16046
16049
  * @param request - DescribeFailoverTestJobsRequest
16047
16050
  * @param runtime - runtime options for this request RuntimeOptions
@@ -16104,7 +16107,7 @@ export default class Client extends OpenApi {
16104
16107
  }
16105
16108
 
16106
16109
  /**
16107
- * Queries failover test jobs of Express Connect in batches.
16110
+ * Queries Express Connect failover test jobs in batches.
16108
16111
  *
16109
16112
  * @param request - DescribeFailoverTestJobsRequest
16110
16113
  * @returns DescribeFailoverTestJobsResponse
@@ -16115,7 +16118,7 @@ export default class Client extends OpenApi {
16115
16118
  }
16116
16119
 
16117
16120
  /**
16118
- * Queries flow logs by calling the DescribeFlowLogs operation.
16121
+ * Queries flow logs.
16119
16122
  *
16120
16123
  * @param request - DescribeFlowLogsRequest
16121
16124
  * @param runtime - runtime options for this request RuntimeOptions
@@ -16218,7 +16221,7 @@ export default class Client extends OpenApi {
16218
16221
  }
16219
16222
 
16220
16223
  /**
16221
- * Queries flow logs by calling the DescribeFlowLogs operation.
16224
+ * Queries flow logs.
16222
16225
  *
16223
16226
  * @param request - DescribeFlowLogsRequest
16224
16227
  * @returns DescribeFlowLogsResponse
@@ -17911,7 +17914,7 @@ export default class Client extends OpenApi {
17911
17914
  * Queries information about Express Connect circuits in a specified region.
17912
17915
  *
17913
17916
  * @remarks
17914
- * By default, the system queries information about all Express Connect circuits in the specified region. You can use the filter options provided by the **DescribePhysicalConnections** operation to query information about specific Express Connect circuits. For supported filter options, see the description of **Key** in the **request parameters** section of this topic.
17917
+ * By default, the system queries information about all Express Connect circuits in the specified region. You can use the filter options provided by the **DescribePhysicalConnections** operation to query information about specific Express Connect circuits. For the supported filter options, refer to the description of **Key** in the **request parameters** section of this topic.
17915
17918
  *
17916
17919
  * @param request - DescribePhysicalConnectionsRequest
17917
17920
  * @param runtime - runtime options for this request RuntimeOptions
@@ -17989,7 +17992,7 @@ export default class Client extends OpenApi {
17989
17992
  * Queries information about Express Connect circuits in a specified region.
17990
17993
  *
17991
17994
  * @remarks
17992
- * By default, the system queries information about all Express Connect circuits in the specified region. You can use the filter options provided by the **DescribePhysicalConnections** operation to query information about specific Express Connect circuits. For supported filter options, see the description of **Key** in the **request parameters** section of this topic.
17995
+ * By default, the system queries information about all Express Connect circuits in the specified region. You can use the filter options provided by the **DescribePhysicalConnections** operation to query information about specific Express Connect circuits. For the supported filter options, refer to the description of **Key** in the **request parameters** section of this topic.
17993
17996
  *
17994
17997
  * @param request - DescribePhysicalConnectionsRequest
17995
17998
  * @returns DescribePhysicalConnectionsResponse
@@ -19143,7 +19146,7 @@ export default class Client extends OpenApi {
19143
19146
  }
19144
19147
 
19145
19148
  /**
19146
- * Calls the DescribeTagKeysForExpressConnect operation to return the tag list of Express Connect.
19149
+ * Queries the tag list of Express Connect resources by calling the DescribeTagKeysForExpressConnect operation.
19147
19150
  *
19148
19151
  * @param request - DescribeTagKeysForExpressConnectRequest
19149
19152
  * @param runtime - runtime options for this request RuntimeOptions
@@ -19210,7 +19213,7 @@ export default class Client extends OpenApi {
19210
19213
  }
19211
19214
 
19212
19215
  /**
19213
- * Calls the DescribeTagKeysForExpressConnect operation to return the tag list of Express Connect.
19216
+ * Queries the tag list of Express Connect resources by calling the DescribeTagKeysForExpressConnect operation.
19214
19217
  *
19215
19218
  * @param request - DescribeTagKeysForExpressConnectRequest
19216
19219
  * @returns DescribeTagKeysForExpressConnectResponse
@@ -19449,6 +19452,9 @@ export default class Client extends OpenApi {
19449
19452
  /**
19450
19453
  * Queries networkable information. Internal networking is performed by vSwitch.
19451
19454
  *
19455
+ * @remarks
19456
+ * The **DescribeVSwitches** operation may return the **Throttling.DeepPageSkip** error code during frequent deep paging or page skipping. Reduce the query frequency or use sequential paging.
19457
+ *
19452
19458
  * @param request - DescribeVSwitchesRequest
19453
19459
  * @param runtime - runtime options for this request RuntimeOptions
19454
19460
  * @returns DescribeVSwitchesResponse
@@ -19548,6 +19554,9 @@ export default class Client extends OpenApi {
19548
19554
  /**
19549
19555
  * Queries networkable information. Internal networking is performed by vSwitch.
19550
19556
  *
19557
+ * @remarks
19558
+ * The **DescribeVSwitches** operation may return the **Throttling.DeepPageSkip** error code during frequent deep paging or page skipping. Reduce the query frequency or use sequential paging.
19559
+ *
19551
19560
  * @param request - DescribeVSwitchesRequest
19552
19561
  * @returns DescribeVSwitchesResponse
19553
19562
  */
@@ -19705,7 +19714,7 @@ export default class Client extends OpenApi {
19705
19714
  }
19706
19715
 
19707
19716
  /**
19708
- * Queries the Virtual Border Routers (VBRs) that you have created.
19717
+ * Queries Virtual Border Routers (VBRs) that are created.
19709
19718
  *
19710
19719
  * @param request - DescribeVirtualBorderRoutersRequest
19711
19720
  * @param runtime - runtime options for this request RuntimeOptions
@@ -19772,7 +19781,7 @@ export default class Client extends OpenApi {
19772
19781
  }
19773
19782
 
19774
19783
  /**
19775
- * Queries the Virtual Border Routers (VBRs) that you have created.
19784
+ * Queries Virtual Border Routers (VBRs) that are created.
19776
19785
  *
19777
19786
  * @param request - DescribeVirtualBorderRoutersRequest
19778
19787
  * @returns DescribeVirtualBorderRoutersResponse
@@ -20015,6 +20024,9 @@ export default class Client extends OpenApi {
20015
20024
  /**
20016
20025
  * Queries created VPCs.
20017
20026
  *
20027
+ * @remarks
20028
+ * The **DescribeVpcs** operation may return the **Throttling.DeepPageSkip** error code during frequent deep paging operations. Reduce the query frequency or use sequential paging.
20029
+ *
20018
20030
  * @param request - DescribeVpcsRequest
20019
20031
  * @param runtime - runtime options for this request RuntimeOptions
20020
20032
  * @returns DescribeVpcsResponse
@@ -20106,6 +20118,9 @@ export default class Client extends OpenApi {
20106
20118
  /**
20107
20119
  * Queries created VPCs.
20108
20120
  *
20121
+ * @remarks
20122
+ * The **DescribeVpcs** operation may return the **Throttling.DeepPageSkip** error code during frequent deep paging operations. Reduce the query frequency or use sequential paging.
20123
+ *
20109
20124
  * @param request - DescribeVpcsRequest
20110
20125
  * @returns DescribeVpcsResponse
20111
20126
  */
@@ -20839,7 +20854,7 @@ export default class Client extends OpenApi {
20839
20854
  }
20840
20855
 
20841
20856
  /**
20842
- * Queries the logs of an SSL server by calling the DescribeVpnSslServerLogs operation.
20857
+ * Queries the logs of an SSL server.
20843
20858
  *
20844
20859
  * @param request - DescribeVpnSslServerLogsRequest
20845
20860
  * @param runtime - runtime options for this request RuntimeOptions
@@ -20914,7 +20929,7 @@ export default class Client extends OpenApi {
20914
20929
  }
20915
20930
 
20916
20931
  /**
20917
- * Queries the logs of an SSL server by calling the DescribeVpnSslServerLogs operation.
20932
+ * Queries the logs of an SSL server.
20918
20933
  *
20919
20934
  * @param request - DescribeVpnSslServerLogsRequest
20920
20935
  * @returns DescribeVpnSslServerLogsResponse
@@ -21153,10 +21168,10 @@ export default class Client extends OpenApi {
21153
21168
  }
21154
21169
 
21155
21170
  /**
21156
- * Diagnoses a specified VPN gateway instance with one click by calling the DiagnoseVpnGateway operation.
21171
+ * Calls the DiagnoseVpnGateway operation to perform a one-click diagnosis on a specified VPN gateway instance.
21157
21172
  *
21158
21173
  * @remarks
21159
- * Only VPN gateway instances in specific regions support the one-click diagnostics feature. For more information about regions, see [Regions that support VPN Gateway features](https://help.aliyun.com/document_detail/430697.html).
21174
+ * Only VPN gateway instances in specific regions support the one-click diagnosis feature. For more information about regions, see [Regions that support VPN Gateway features](https://help.aliyun.com/document_detail/430697.html).
21160
21175
  *
21161
21176
  * @param request - DiagnoseVpnGatewayRequest
21162
21177
  * @param runtime - runtime options for this request RuntimeOptions
@@ -21207,10 +21222,10 @@ export default class Client extends OpenApi {
21207
21222
  }
21208
21223
 
21209
21224
  /**
21210
- * Diagnoses a specified VPN gateway instance with one click by calling the DiagnoseVpnGateway operation.
21225
+ * Calls the DiagnoseVpnGateway operation to perform a one-click diagnosis on a specified VPN gateway instance.
21211
21226
  *
21212
21227
  * @remarks
21213
- * Only VPN gateway instances in specific regions support the one-click diagnostics feature. For more information about regions, see [Regions that support VPN Gateway features](https://help.aliyun.com/document_detail/430697.html).
21228
+ * Only VPN gateway instances in specific regions support the one-click diagnosis feature. For more information about regions, see [Regions that support VPN Gateway features](https://help.aliyun.com/document_detail/430697.html).
21214
21229
  *
21215
21230
  * @param request - DiagnoseVpnGatewayRequest
21216
21231
  * @returns DiagnoseVpnGatewayResponse
@@ -21509,10 +21524,10 @@ export default class Client extends OpenApi {
21509
21524
  * Dissociates a VPN gateway from a certificate.
21510
21525
  *
21511
21526
  * @remarks
21512
- * - **DissociateVpnGatewayWithCertificate** is an asynchronous operation. After a request is sent, the system returns a request ID. However, the VPN gateway is not yet dissociated from the SSL certificate, and the dissociation task is still running in the background. You can call the [DescribeVpnGateway](https://help.aliyun.com/document_detail/73720.html) operation to query the status of the VPN gateway instance and check the dissociation status of the SSL certificate:
21527
+ * - **DissociateVpnGatewayWithCertificate** is an asynchronous operation. After a request is sent, the system returns a request ID, but the VPN gateway has not yet been dissociated from the SSL certificate. The dissociation task is still running in the background. You can call the [DescribeVpnGateway](https://help.aliyun.com/document_detail/73720.html) operation to query the status of the VPN gateway instance and confirm the dissociation status of the SSL certificate:
21513
21528
  * - If the VPN gateway is in the **updating** state, the SSL certificate is being dissociated.
21514
21529
  * - If the VPN gateway is in the **active** state, the SSL certificate is dissociated.
21515
- * - **DissociateVpnGatewayWithCertificate** does not support concurrent SSL certificate dissociation for the same VPN gateway.
21530
+ * - **DissociateVpnGatewayWithCertificate** does not support concurrent dissociation of SSL certificates from the same VPN gateway.
21516
21531
  *
21517
21532
  * @param request - DissociateVpnGatewayWithCertificateRequest
21518
21533
  * @param runtime - runtime options for this request RuntimeOptions
@@ -21566,10 +21581,10 @@ export default class Client extends OpenApi {
21566
21581
  * Dissociates a VPN gateway from a certificate.
21567
21582
  *
21568
21583
  * @remarks
21569
- * - **DissociateVpnGatewayWithCertificate** is an asynchronous operation. After a request is sent, the system returns a request ID. However, the VPN gateway is not yet dissociated from the SSL certificate, and the dissociation task is still running in the background. You can call the [DescribeVpnGateway](https://help.aliyun.com/document_detail/73720.html) operation to query the status of the VPN gateway instance and check the dissociation status of the SSL certificate:
21584
+ * - **DissociateVpnGatewayWithCertificate** is an asynchronous operation. After a request is sent, the system returns a request ID, but the VPN gateway has not yet been dissociated from the SSL certificate. The dissociation task is still running in the background. You can call the [DescribeVpnGateway](https://help.aliyun.com/document_detail/73720.html) operation to query the status of the VPN gateway instance and confirm the dissociation status of the SSL certificate:
21570
21585
  * - If the VPN gateway is in the **updating** state, the SSL certificate is being dissociated.
21571
21586
  * - If the VPN gateway is in the **active** state, the SSL certificate is dissociated.
21572
- * - **DissociateVpnGatewayWithCertificate** does not support concurrent SSL certificate dissociation for the same VPN gateway.
21587
+ * - **DissociateVpnGatewayWithCertificate** does not support concurrent dissociation of SSL certificates from the same VPN gateway.
21573
21588
  *
21574
21589
  * @param request - DissociateVpnGatewayWithCertificateRequest
21575
21590
  * @returns DissociateVpnGatewayWithCertificateResponse
@@ -22753,10 +22768,10 @@ export default class Client extends OpenApi {
22753
22768
  }
22754
22769
 
22755
22770
  /**
22756
- * Queries the one-click diagnostic result of a VPN gateway instance by calling the GetVpnGatewayDiagnoseResult operation.
22771
+ * Queries the one-click diagnosis result of a VPN gateway instance.
22757
22772
  *
22758
22773
  * @remarks
22759
- * When you call the **GetVpnGatewayDiagnoseResult** operation, you must specify at least one of the **DiagnoseId** and **VpnGatewayId** parameters in addition to the required parameters.
22774
+ * When you call the **GetVpnGatewayDiagnoseResult** operation, in addition to the required parameters, you must specify at least one of the **DiagnoseId** and **VpnGatewayId** parameters.
22760
22775
  *
22761
22776
  * @param request - GetVpnGatewayDiagnoseResultRequest
22762
22777
  * @param runtime - runtime options for this request RuntimeOptions
@@ -22799,10 +22814,10 @@ export default class Client extends OpenApi {
22799
22814
  }
22800
22815
 
22801
22816
  /**
22802
- * Queries the one-click diagnostic result of a VPN gateway instance by calling the GetVpnGatewayDiagnoseResult operation.
22817
+ * Queries the one-click diagnosis result of a VPN gateway instance.
22803
22818
  *
22804
22819
  * @remarks
22805
- * When you call the **GetVpnGatewayDiagnoseResult** operation, you must specify at least one of the **DiagnoseId** and **VpnGatewayId** parameters in addition to the required parameters.
22820
+ * When you call the **GetVpnGatewayDiagnoseResult** operation, in addition to the required parameters, you must specify at least one of the **DiagnoseId** and **VpnGatewayId** parameters.
22806
22821
  *
22807
22822
  * @param request - GetVpnGatewayDiagnoseResultRequest
22808
22823
  * @returns GetVpnGatewayDiagnoseResultResponse
@@ -22975,7 +22990,7 @@ export default class Client extends OpenApi {
22975
22990
  }
22976
22991
 
22977
22992
  /**
22978
- * Calls the ListBusinessAccessPoints operation to query access point information for Express Connect circuits.
22993
+ * Queries the access point information of Express Connect circuits by calling the ListBusinessAccessPoints operation.
22979
22994
  *
22980
22995
  * @param request - ListBusinessAccessPointsRequest
22981
22996
  * @param runtime - runtime options for this request RuntimeOptions
@@ -23010,7 +23025,7 @@ export default class Client extends OpenApi {
23010
23025
  }
23011
23026
 
23012
23027
  /**
23013
- * Calls the ListBusinessAccessPoints operation to query access point information for Express Connect circuits.
23028
+ * Queries the access point information of Express Connect circuits by calling the ListBusinessAccessPoints operation.
23014
23029
  *
23015
23030
  * @param request - ListBusinessAccessPointsRequest
23016
23031
  * @returns ListBusinessAccessPointsResponse
@@ -25057,7 +25072,7 @@ export default class Client extends OpenApi {
25057
25072
  * @remarks
25058
25073
  * When you call **ListVpnCertificateAssociations**:
25059
25074
  * - If you specify only the **RegionId** parameter, all associations between VPN gateway instances and SSL certificates in the specified region are queried.
25060
- * - If you specify the **RegionId** and **CertificateType** parameters, the associations between VPN gateway instances and SSL certificates of the specified certificate type in the specified region are queried.
25075
+ * - If you specify the **RegionId** and **CertificateType** parameters, the associations between VPN gateway instances and SSL certificates of the specified type in the specified region are queried.
25061
25076
  * - If you specify the **RegionId** and **VpnGatewayId** parameters, the associations between the specified VPN gateway instances and SSL certificates in the specified region are queried.
25062
25077
  * - If you specify the **RegionId** and **CertificateId** parameters, the associations between the specified SSL certificates and VPN gateway instances in the specified region are queried.
25063
25078
  *
@@ -25115,7 +25130,7 @@ export default class Client extends OpenApi {
25115
25130
  * @remarks
25116
25131
  * When you call **ListVpnCertificateAssociations**:
25117
25132
  * - If you specify only the **RegionId** parameter, all associations between VPN gateway instances and SSL certificates in the specified region are queried.
25118
- * - If you specify the **RegionId** and **CertificateType** parameters, the associations between VPN gateway instances and SSL certificates of the specified certificate type in the specified region are queried.
25133
+ * - If you specify the **RegionId** and **CertificateType** parameters, the associations between VPN gateway instances and SSL certificates of the specified type in the specified region are queried.
25119
25134
  * - If you specify the **RegionId** and **VpnGatewayId** parameters, the associations between the specified VPN gateway instances and SSL certificates in the specified region are queried.
25120
25135
  * - If you specify the **RegionId** and **CertificateId** parameters, the associations between the specified SSL certificates and VPN gateway instances in the specified region are queried.
25121
25136
  *
@@ -25544,7 +25559,7 @@ export default class Client extends OpenApi {
25544
25559
  }
25545
25560
 
25546
25561
  /**
25547
- * Modifies the configuration of a customer gateway by calling the ModifyCustomerGatewayAttribute operation.
25562
+ * Modifies the configuration of a customer gateway.
25548
25563
  *
25549
25564
  * @remarks
25550
25565
  * - When you call the **ModifyCustomerGatewayAttribute** operation, if the **AuthKey** parameter is not empty, this operation is asynchronous. The system returns the customer gateway information first, but the configuration has not been modified yet because the modification task is still running in the background. You can call [DescribeVpnGateway](https://help.aliyun.com/document_detail/73720.html) to query the modification status of the customer gateway configuration:
@@ -25618,7 +25633,7 @@ export default class Client extends OpenApi {
25618
25633
  }
25619
25634
 
25620
25635
  /**
25621
- * Modifies the configuration of a customer gateway by calling the ModifyCustomerGatewayAttribute operation.
25636
+ * Modifies the configuration of a customer gateway.
25622
25637
  *
25623
25638
  * @remarks
25624
25639
  * - When you call the **ModifyCustomerGatewayAttribute** operation, if the **AuthKey** parameter is not empty, this operation is asynchronous. The system returns the customer gateway information first, but the configuration has not been modified yet because the modification task is still running in the background. You can call [DescribeVpnGateway](https://help.aliyun.com/document_detail/73720.html) to query the modification status of the customer gateway configuration:
@@ -25928,12 +25943,12 @@ export default class Client extends OpenApi {
25928
25943
  }
25929
25944
 
25930
25945
  /**
25931
- * Calls the ModifyExpressConnectTrafficQos operation to modify an Express Connect Quality of Service (QoS) policy. You can also use this operation to associate dedicated Express Connect circuits.
25946
+ * Modifies an Express Connect Quality of Service (QoS) policy. You can also use this operation to associate dedicated Express Connect circuits with the policy.
25932
25947
  *
25933
25948
  * @remarks
25934
25949
  * - Only dedicated Express Connect circuits that are in the Normal state and do not have overdue payments can be associated. Shared Express Connect circuit ports and Virtual Border Router (VBR) instances are not supported.
25935
- * - When associating dedicated Express Connect circuits, only full operations are supported. To dissociate all circuits, pass an empty string.
25936
- * - If a dedicated Express Connect circuit has shared Express Connect circuits or cross-account VBRs, you must apply for a whitelist before you can associate it.
25950
+ * - When associating dedicated Express Connect circuits, only full replacement is supported. To disassociate all circuits, pass an empty string.
25951
+ * - If a dedicated Express Connect circuit has shared Express Connect circuits or cross-account VBRs, you must be added to the whitelist before you can associate it.
25937
25952
  * - The device on which the dedicated Express Connect circuit resides must support the QoS feature before association.
25938
25953
  * - If a single VBR is associated with multiple Express Connect circuits, you must associate all Express Connect circuits of the VBR at the same time.
25939
25954
  *
@@ -26006,12 +26021,12 @@ export default class Client extends OpenApi {
26006
26021
  }
26007
26022
 
26008
26023
  /**
26009
- * Calls the ModifyExpressConnectTrafficQos operation to modify an Express Connect Quality of Service (QoS) policy. You can also use this operation to associate dedicated Express Connect circuits.
26024
+ * Modifies an Express Connect Quality of Service (QoS) policy. You can also use this operation to associate dedicated Express Connect circuits with the policy.
26010
26025
  *
26011
26026
  * @remarks
26012
26027
  * - Only dedicated Express Connect circuits that are in the Normal state and do not have overdue payments can be associated. Shared Express Connect circuit ports and Virtual Border Router (VBR) instances are not supported.
26013
- * - When associating dedicated Express Connect circuits, only full operations are supported. To dissociate all circuits, pass an empty string.
26014
- * - If a dedicated Express Connect circuit has shared Express Connect circuits or cross-account VBRs, you must apply for a whitelist before you can associate it.
26028
+ * - When associating dedicated Express Connect circuits, only full replacement is supported. To disassociate all circuits, pass an empty string.
26029
+ * - If a dedicated Express Connect circuit has shared Express Connect circuits or cross-account VBRs, you must be added to the whitelist before you can associate it.
26015
26030
  * - The device on which the dedicated Express Connect circuit resides must support the QoS feature before association.
26016
26031
  * - If a single VBR is associated with multiple Express Connect circuits, you must associate all Express Connect circuits of the VBR at the same time.
26017
26032
  *
@@ -26231,7 +26246,7 @@ export default class Client extends OpenApi {
26231
26246
  * Calls the ModifyFlowLogAttribute operation to modify the name and description of a flow log.
26232
26247
  *
26233
26248
  * @remarks
26234
- * - **ModifyFlowLogAttribute** is an asynchronous operation. After you send a request, the system returns a request ID, but the flow log has not been modified yet. The modification task is still running in the background. You can call [DescribeFlowLogs](https://help.aliyun.com/document_detail/87923.html) to query the modification status of the flow log:
26249
+ * - **ModifyFlowLogAttribute** is an asynchronous operation. After you send a request, the system returns a request ID. However, the flow log has not been modified yet because the modification task is still running in the background. You can call [DescribeFlowLogs](https://help.aliyun.com/document_detail/87923.html) to query the modification status of the flow log:
26235
26250
  * - If the flow log is in the **Modifying** state, the flow log is being modified.
26236
26251
  * - If the flow log is in the **Active** or **Inactive** state, the flow log has been modified.
26237
26252
  * - **ModifyFlowLogAttribute** does not support concurrent modifications to the same flow log.
@@ -26308,7 +26323,7 @@ export default class Client extends OpenApi {
26308
26323
  * Calls the ModifyFlowLogAttribute operation to modify the name and description of a flow log.
26309
26324
  *
26310
26325
  * @remarks
26311
- * - **ModifyFlowLogAttribute** is an asynchronous operation. After you send a request, the system returns a request ID, but the flow log has not been modified yet. The modification task is still running in the background. You can call [DescribeFlowLogs](https://help.aliyun.com/document_detail/87923.html) to query the modification status of the flow log:
26326
+ * - **ModifyFlowLogAttribute** is an asynchronous operation. After you send a request, the system returns a request ID. However, the flow log has not been modified yet because the modification task is still running in the background. You can call [DescribeFlowLogs](https://help.aliyun.com/document_detail/87923.html) to query the modification status of the flow log:
26312
26327
  * - If the flow log is in the **Modifying** state, the flow log is being modified.
26313
26328
  * - If the flow log is in the **Active** or **Inactive** state, the flow log has been modified.
26314
26329
  * - **ModifyFlowLogAttribute** does not support concurrent modifications to the same flow log.
@@ -27894,10 +27909,10 @@ export default class Client extends OpenApi {
27894
27909
  }
27895
27910
 
27896
27911
  /**
27897
- * Modifies the configurations of an Express Connect circuit.
27912
+ * Modifies the configuration of an Express Connect circuit.
27898
27913
  *
27899
27914
  * @remarks
27900
- * When you call this operation, take note of the following items:
27915
+ * When you call this operation, note the following items:
27901
27916
  * - You can modify the specifications and redundant circuit ID only for Express Connect circuits in the **Initial**, **Enabled**, or **Rejected** state.
27902
27917
  * - You cannot modify Express Connect circuits in the **Canceled**, **Allocating**, **AllocationFailed**, or **Terminated** state.
27903
27918
  * - An Express Connect circuit in the **Rejected** state enters the **Initial** state after it is modified.
@@ -27925,6 +27940,10 @@ export default class Client extends OpenApi {
27925
27940
  query["Description"] = request.description;
27926
27941
  }
27927
27942
 
27943
+ if (!$dara.isNull(request.downDelayTime)) {
27944
+ query["DownDelayTime"] = request.downDelayTime;
27945
+ }
27946
+
27928
27947
  if (!$dara.isNull(request.lineOperator)) {
27929
27948
  query["LineOperator"] = request.lineOperator;
27930
27949
  }
@@ -27991,10 +28010,10 @@ export default class Client extends OpenApi {
27991
28010
  }
27992
28011
 
27993
28012
  /**
27994
- * Modifies the configurations of an Express Connect circuit.
28013
+ * Modifies the configuration of an Express Connect circuit.
27995
28014
  *
27996
28015
  * @remarks
27997
- * When you call this operation, take note of the following items:
28016
+ * When you call this operation, note the following items:
27998
28017
  * - You can modify the specifications and redundant circuit ID only for Express Connect circuits in the **Initial**, **Enabled**, or **Rejected** state.
27999
28018
  * - You cannot modify Express Connect circuits in the **Canceled**, **Allocating**, **AllocationFailed**, or **Terminated** state.
28000
28019
  * - An Express Connect circuit in the **Rejected** state enters the **Initial** state after it is modified.
@@ -28548,15 +28567,15 @@ export default class Client extends OpenApi {
28548
28567
  }
28549
28568
 
28550
28569
  /**
28551
- * Modifies the configuration of an SSL-VPN server.
28570
+ * Modifies the configuration of an SSL-VPN server by calling the ModifySslVpnServer operation.
28552
28571
  *
28553
28572
  * @remarks
28554
- * - If you want to enable two-factor identity authentication for the SSL server, make sure that the VPN gateway instance supports this feature. You may need to upgrade the VPN gateway instance. For more information, see [SSL-VPN two-factor authentication supports IDaaS EIAM 2.0](https://help.aliyun.com/document_detail/2785320.html).
28555
- * - When you modify only the **Name** of the SSL-VPN server, this operation is synchronous. If you modify any configuration other than **Name**, this operation is asynchronous.
28556
- * - When **ModifySslVpnServer** is asynchronous, the system returns a request ID first, but the configuration of the SSL-VPN server has not been modified yet. The modification task continues in the background. You can call the [DescribeVpnGateway](https://help.aliyun.com/document_detail/2794055.html) operation to query the status of the VPN gateway instance associated with the SSL-VPN server to check the modification status:
28573
+ * - If you want to enable two-factor authentication for the SSL server, make sure that the VPN gateway instance supports this feature. You may need to upgrade the VPN gateway instance. For more information, see [SSL-VPN two-factor authentication supports IDaaS EIAM 2.0](https://help.aliyun.com/document_detail/2785320.html).
28574
+ * - When you modify only the **Name** of the SSL-VPN server, this operation is synchronous. If you modify configurations other than **Name**, this operation is asynchronous.
28575
+ * - When the **ModifySslVpnServer** operation is asynchronous, the system returns a request ID but the configuration of the SSL-VPN server has not been modified. The modification task is still running in the background. You can call the [DescribeVpnGateway](https://help.aliyun.com/document_detail/2794055.html) operation to query the status of the VPN gateway instance associated with the SSL-VPN server to check the modification status:
28557
28576
  * - If the VPN gateway instance is in the **updating** state, the configuration of the SSL-VPN server is being modified.
28558
28577
  * - If the VPN gateway instance is in the **active** state, the configuration of the SSL-VPN server has been modified.
28559
- * - The **ModifySslVpnServer** operation does not support concurrent modifications to the configuration of SSL-VPN servers under the same VPN gateway.
28578
+ * - The **ModifySslVpnServer** operation does not support concurrent modifications to the SSL-VPN server configuration under the same VPN gateway.
28560
28579
  *
28561
28580
  * @param request - ModifySslVpnServerRequest
28562
28581
  * @param runtime - runtime options for this request RuntimeOptions
@@ -28663,15 +28682,15 @@ export default class Client extends OpenApi {
28663
28682
  }
28664
28683
 
28665
28684
  /**
28666
- * Modifies the configuration of an SSL-VPN server.
28685
+ * Modifies the configuration of an SSL-VPN server by calling the ModifySslVpnServer operation.
28667
28686
  *
28668
28687
  * @remarks
28669
- * - If you want to enable two-factor identity authentication for the SSL server, make sure that the VPN gateway instance supports this feature. You may need to upgrade the VPN gateway instance. For more information, see [SSL-VPN two-factor authentication supports IDaaS EIAM 2.0](https://help.aliyun.com/document_detail/2785320.html).
28670
- * - When you modify only the **Name** of the SSL-VPN server, this operation is synchronous. If you modify any configuration other than **Name**, this operation is asynchronous.
28671
- * - When **ModifySslVpnServer** is asynchronous, the system returns a request ID first, but the configuration of the SSL-VPN server has not been modified yet. The modification task continues in the background. You can call the [DescribeVpnGateway](https://help.aliyun.com/document_detail/2794055.html) operation to query the status of the VPN gateway instance associated with the SSL-VPN server to check the modification status:
28688
+ * - If you want to enable two-factor authentication for the SSL server, make sure that the VPN gateway instance supports this feature. You may need to upgrade the VPN gateway instance. For more information, see [SSL-VPN two-factor authentication supports IDaaS EIAM 2.0](https://help.aliyun.com/document_detail/2785320.html).
28689
+ * - When you modify only the **Name** of the SSL-VPN server, this operation is synchronous. If you modify configurations other than **Name**, this operation is asynchronous.
28690
+ * - When the **ModifySslVpnServer** operation is asynchronous, the system returns a request ID but the configuration of the SSL-VPN server has not been modified. The modification task is still running in the background. You can call the [DescribeVpnGateway](https://help.aliyun.com/document_detail/2794055.html) operation to query the status of the VPN gateway instance associated with the SSL-VPN server to check the modification status:
28672
28691
  * - If the VPN gateway instance is in the **updating** state, the configuration of the SSL-VPN server is being modified.
28673
28692
  * - If the VPN gateway instance is in the **active** state, the configuration of the SSL-VPN server has been modified.
28674
- * - The **ModifySslVpnServer** operation does not support concurrent modifications to the configuration of SSL-VPN servers under the same VPN gateway.
28693
+ * - The **ModifySslVpnServer** operation does not support concurrent modifications to the SSL-VPN server configuration under the same VPN gateway.
28675
28694
  *
28676
28695
  * @param request - ModifySslVpnServerRequest
28677
28696
  * @returns ModifySslVpnServerResponse
@@ -29015,7 +29034,7 @@ export default class Client extends OpenApi {
29015
29034
  * @remarks
29016
29035
  * - **ModifyVcoRouteEntryWeight** is an asynchronous operation. After a request is sent, the system returns a request ID, but the weight of the destination route entry has not been modified yet. The modification task is still running in the background. You can call [DescribeVpnConnection](https://help.aliyun.com/document_detail/53046.html) to query the modification status of the destination route entry weight:
29017
29036
  * - If the IPsec-VPN connection is in the **updating** state, the weight of the destination route entry is being modified.
29018
- * - If the IPsec-VPN connection is in the **attached** state, the weight of the destination route entry has been modified.
29037
+ * - If the IPsec-VPN connection is in the **attached** state, the weight of the destination route entry is modified.
29019
29038
  * - **ModifyVcoRouteEntryWeight** does not support concurrent modifications of destination route entry weights for the same IPsec-VPN connection.
29020
29039
  *
29021
29040
  * @param request - ModifyVcoRouteEntryWeightRequest
@@ -29092,7 +29111,7 @@ export default class Client extends OpenApi {
29092
29111
  * @remarks
29093
29112
  * - **ModifyVcoRouteEntryWeight** is an asynchronous operation. After a request is sent, the system returns a request ID, but the weight of the destination route entry has not been modified yet. The modification task is still running in the background. You can call [DescribeVpnConnection](https://help.aliyun.com/document_detail/53046.html) to query the modification status of the destination route entry weight:
29094
29113
  * - If the IPsec-VPN connection is in the **updating** state, the weight of the destination route entry is being modified.
29095
- * - If the IPsec-VPN connection is in the **attached** state, the weight of the destination route entry has been modified.
29114
+ * - If the IPsec-VPN connection is in the **attached** state, the weight of the destination route entry is modified.
29096
29115
  * - **ModifyVcoRouteEntryWeight** does not support concurrent modifications of destination route entry weights for the same IPsec-VPN connection.
29097
29116
  *
29098
29117
  * @param request - ModifyVcoRouteEntryWeightRequest
@@ -29463,13 +29482,13 @@ export default class Client extends OpenApi {
29463
29482
  * Modifies the configuration of an IPsec-VPN connection.
29464
29483
  *
29465
29484
  * @remarks
29466
- * - When you modify a dual-tunnel IPsec-VPN connection, in addition to the required parameters, you can configure the following request parameters: **ClientToken**, **Name**, **LocalSubnet**, **RemoteSubnet**, **EffectImmediately**, the **TunnelOptionsSpecification** array, and **EnableTunnelsBgp**.
29467
- * - When you modify a single-tunnel IPsec-VPN connection, in addition to the required parameters, you can configure the following request parameters: **ClientToken**, **Name**, **LocalSubnet**, **RemoteSubnet**, **EffectImmediately**, **IkeConfig**, **IpsecConfig**, **HealthCheckConfig**, **EnableDpd**, **EnableNatTraversal**, **BgpConfig**, and **CustomerGatewayId**.
29468
- * - **ModifyVpnAttachmentAttribute** is an asynchronous operation. After a request is sent, the system returns a request ID. However, the operation is still being performed in the system background. You can call [DescribeVpnConnection](https://help.aliyun.com/document_detail/53046.html) to query the modification status of the IPsec-VPN connection:
29485
+ * - When you modify a dual-tunnel IPsec-VPN connection, in addition to the required parameters, the following request parameters are supported: **ClientToken**, **Name**, **LocalSubnet**, **RemoteSubnet**, **EffectImmediately**, the **TunnelOptionsSpecification** array, and **EnableTunnelsBgp**.
29486
+ * - When you modify a single-tunnel IPsec-VPN connection, in addition to the required parameters, the following request parameters are supported: **ClientToken**, **Name**, **LocalSubnet**, **RemoteSubnet**, **EffectImmediately**, **IkeConfig**, **IpsecConfig**, **HealthCheckConfig**, **EnableDpd**, **EnableNatTraversal**, **BgpConfig**, and **CustomerGatewayId**.
29487
+ * - The **ModifyVpnAttachmentAttribute** operation is asynchronous. After a request is sent, the system returns a request ID. However, the IPsec-VPN connection configuration has not been modified. The modification task is still running in the background. You can call [DescribeVpnConnection](https://help.aliyun.com/document_detail/53046.html) to query the modification status of the IPsec-VPN connection configuration:
29469
29488
  * - If the IPsec-VPN connection is in the **updating** state, the configuration is being modified.
29470
29489
  * - If the IPsec-VPN connection is in the **attached** state, the configuration has been modified.
29471
- * - **ModifyVpnAttachmentAttribute** does not support concurrent modification of the IPsec-VPN connection configuration.
29472
- * - When you call **ModifyVpnAttachmentAttribute**, you cannot modify the gateway type of the IPsec-VPN connection.
29490
+ * - The **ModifyVpnAttachmentAttribute** operation does not support concurrent modifications to the IPsec-VPN connection configuration.
29491
+ * - When you call the **ModifyVpnAttachmentAttribute** operation, you cannot modify the gateway type of the IPsec-VPN connection.
29473
29492
  *
29474
29493
  * @param request - ModifyVpnAttachmentAttributeRequest
29475
29494
  * @param runtime - runtime options for this request RuntimeOptions
@@ -29594,13 +29613,13 @@ export default class Client extends OpenApi {
29594
29613
  * Modifies the configuration of an IPsec-VPN connection.
29595
29614
  *
29596
29615
  * @remarks
29597
- * - When you modify a dual-tunnel IPsec-VPN connection, in addition to the required parameters, you can configure the following request parameters: **ClientToken**, **Name**, **LocalSubnet**, **RemoteSubnet**, **EffectImmediately**, the **TunnelOptionsSpecification** array, and **EnableTunnelsBgp**.
29598
- * - When you modify a single-tunnel IPsec-VPN connection, in addition to the required parameters, you can configure the following request parameters: **ClientToken**, **Name**, **LocalSubnet**, **RemoteSubnet**, **EffectImmediately**, **IkeConfig**, **IpsecConfig**, **HealthCheckConfig**, **EnableDpd**, **EnableNatTraversal**, **BgpConfig**, and **CustomerGatewayId**.
29599
- * - **ModifyVpnAttachmentAttribute** is an asynchronous operation. After a request is sent, the system returns a request ID. However, the operation is still being performed in the system background. You can call [DescribeVpnConnection](https://help.aliyun.com/document_detail/53046.html) to query the modification status of the IPsec-VPN connection:
29616
+ * - When you modify a dual-tunnel IPsec-VPN connection, in addition to the required parameters, the following request parameters are supported: **ClientToken**, **Name**, **LocalSubnet**, **RemoteSubnet**, **EffectImmediately**, the **TunnelOptionsSpecification** array, and **EnableTunnelsBgp**.
29617
+ * - When you modify a single-tunnel IPsec-VPN connection, in addition to the required parameters, the following request parameters are supported: **ClientToken**, **Name**, **LocalSubnet**, **RemoteSubnet**, **EffectImmediately**, **IkeConfig**, **IpsecConfig**, **HealthCheckConfig**, **EnableDpd**, **EnableNatTraversal**, **BgpConfig**, and **CustomerGatewayId**.
29618
+ * - The **ModifyVpnAttachmentAttribute** operation is asynchronous. After a request is sent, the system returns a request ID. However, the IPsec-VPN connection configuration has not been modified. The modification task is still running in the background. You can call [DescribeVpnConnection](https://help.aliyun.com/document_detail/53046.html) to query the modification status of the IPsec-VPN connection configuration:
29600
29619
  * - If the IPsec-VPN connection is in the **updating** state, the configuration is being modified.
29601
29620
  * - If the IPsec-VPN connection is in the **attached** state, the configuration has been modified.
29602
- * - **ModifyVpnAttachmentAttribute** does not support concurrent modification of the IPsec-VPN connection configuration.
29603
- * - When you call **ModifyVpnAttachmentAttribute**, you cannot modify the gateway type of the IPsec-VPN connection.
29621
+ * - The **ModifyVpnAttachmentAttribute** operation does not support concurrent modifications to the IPsec-VPN connection configuration.
29622
+ * - When you call the **ModifyVpnAttachmentAttribute** operation, you cannot modify the gateway type of the IPsec-VPN connection.
29604
29623
  *
29605
29624
  * @param request - ModifyVpnAttachmentAttributeRequest
29606
29625
  * @returns ModifyVpnAttachmentAttributeResponse
@@ -29614,14 +29633,11 @@ export default class Client extends OpenApi {
29614
29633
  * Modifies the configuration of an IPsec-VPN connection.
29615
29634
  *
29616
29635
  * @remarks
29617
- * - To modify a dual-tunnel IPsec-VPN connection, the `ModifyVpnConnectionAttribute` operation supports the following request parameters in addition to the required parameters:
29636
+ * - To modify a dual-tunnel mode IPsec-VPN connection, the `ModifyVpnConnectionAttribute` operation supports the following request parameters in addition to the required parameters:
29618
29637
  * **ClientToken**, **Name**, **LocalSubnet**, **RemoteSubnet**, **EffectImmediately**, **AutoConfigRoute**, **TunnelOptionsSpecification** array, and **EnableTunnelsBgp**.
29619
- * - To modify a single-tunnel IPsec-VPN connection, the `ModifyVpnConnectionAttribute` operation supports the following request parameters in addition to the required parameters:
29638
+ * - To modify a single-tunnel mode IPsec-VPN connection, the `ModifyVpnConnectionAttribute` operation supports the following request parameters in addition to the required parameters:
29620
29639
  * **ClientToken**, **Name**, **LocalSubnet**, **RemoteSubnet**, **EffectImmediately**, **IkeConfig**, **IpsecConfig**, **HealthCheckConfig**, **AutoConfigRoute**, **EnableDpd**, **EnableNatTraversal**, **BgpConfig**, and **RemoteCaCertificate**.
29621
- * - The **ModifyVpnConnectionAttribute** operation is asynchronous. After a request is sent, the system returns a request ID. However, the configuration of the IPsec-VPN connection is not yet modified. The modification node runs in the background. You can invoke [DescribeVpnGateway](https://help.aliyun.com/document_detail/73720.html) to query the instance status of the VPN gateway to determine the modification status of the IPsec-VPN connection configuration:
29622
- * - If the VPN gateway instance is in the **updating** state, the configuration of the IPsec-VPN connection is being modified.
29623
- * - If the VPN gateway instance is in the **active** state, the configuration of the IPsec-VPN connection is modified.
29624
- * - The **ModifyVpnConnectionAttribute** operation does not support concurrent modifications to IPsec-VPN connection configurations under the same VPN gateway.
29640
+ * - The **ModifyVpnConnectionAttribute** operation is asynchronous. After a request is sent, the system returns a request ID, but the configuration of the IPsec-VPN connection has not been modified yet. The modification node is still running in the background. You can invoke [DescribeVpnGateway](https://help.aliyun.com/document_detail/73720.html) to query the instance status of the VPN gateway to determine the modification status of the IPsec-VPN connection configuration:
29625
29641
  *
29626
29642
  * @param request - ModifyVpnConnectionAttributeRequest
29627
29643
  * @param runtime - runtime options for this request RuntimeOptions
@@ -29742,14 +29758,11 @@ export default class Client extends OpenApi {
29742
29758
  * Modifies the configuration of an IPsec-VPN connection.
29743
29759
  *
29744
29760
  * @remarks
29745
- * - To modify a dual-tunnel IPsec-VPN connection, the `ModifyVpnConnectionAttribute` operation supports the following request parameters in addition to the required parameters:
29761
+ * - To modify a dual-tunnel mode IPsec-VPN connection, the `ModifyVpnConnectionAttribute` operation supports the following request parameters in addition to the required parameters:
29746
29762
  * **ClientToken**, **Name**, **LocalSubnet**, **RemoteSubnet**, **EffectImmediately**, **AutoConfigRoute**, **TunnelOptionsSpecification** array, and **EnableTunnelsBgp**.
29747
- * - To modify a single-tunnel IPsec-VPN connection, the `ModifyVpnConnectionAttribute` operation supports the following request parameters in addition to the required parameters:
29763
+ * - To modify a single-tunnel mode IPsec-VPN connection, the `ModifyVpnConnectionAttribute` operation supports the following request parameters in addition to the required parameters:
29748
29764
  * **ClientToken**, **Name**, **LocalSubnet**, **RemoteSubnet**, **EffectImmediately**, **IkeConfig**, **IpsecConfig**, **HealthCheckConfig**, **AutoConfigRoute**, **EnableDpd**, **EnableNatTraversal**, **BgpConfig**, and **RemoteCaCertificate**.
29749
- * - The **ModifyVpnConnectionAttribute** operation is asynchronous. After a request is sent, the system returns a request ID. However, the configuration of the IPsec-VPN connection is not yet modified. The modification node runs in the background. You can invoke [DescribeVpnGateway](https://help.aliyun.com/document_detail/73720.html) to query the instance status of the VPN gateway to determine the modification status of the IPsec-VPN connection configuration:
29750
- * - If the VPN gateway instance is in the **updating** state, the configuration of the IPsec-VPN connection is being modified.
29751
- * - If the VPN gateway instance is in the **active** state, the configuration of the IPsec-VPN connection is modified.
29752
- * - The **ModifyVpnConnectionAttribute** operation does not support concurrent modifications to IPsec-VPN connection configurations under the same VPN gateway.
29765
+ * - The **ModifyVpnConnectionAttribute** operation is asynchronous. After a request is sent, the system returns a request ID, but the configuration of the IPsec-VPN connection has not been modified yet. The modification node is still running in the background. You can invoke [DescribeVpnGateway](https://help.aliyun.com/document_detail/73720.html) to query the instance status of the VPN gateway to determine the modification status of the IPsec-VPN connection configuration:
29753
29766
  *
29754
29767
  * @param request - ModifyVpnConnectionAttributeRequest
29755
29768
  * @returns ModifyVpnConnectionAttributeResponse
@@ -29763,7 +29776,7 @@ export default class Client extends OpenApi {
29763
29776
  * Invokes the ModifyVpnGatewayAttribute operation to modify the name, description, or routing automatic propagation feature of a VPN gateway.
29764
29777
  *
29765
29778
  * @remarks
29766
- * - **ModifyVpnGatewayAttribute** is an asynchronous operation. After you call this operation, the system returns the VPN gateway information, but the configuration has not been modified yet. The modification task is still running in the background. You can call [DescribeVpnGateway](https://help.aliyun.com/document_detail/73720.html) to query the modification status of the VPN gateway configuration:
29779
+ * - **ModifyVpnGatewayAttribute** is an asynchronous operation. After you call this operation, the system returns the VPN gateway information, but the configuration of the VPN gateway has not been modified yet. The modification task is still running in the background. You can call [DescribeVpnGateway](https://help.aliyun.com/document_detail/73720.html) to query the modification status of the VPN gateway configuration:
29767
29780
  * - If the VPN gateway is in the **updating** state, the configuration is being modified.
29768
29781
  * - If the VPN gateway is in the **active** state, the configuration has been modified.
29769
29782
  * - **ModifyVpnGatewayAttribute** does not support concurrent modifications to the configuration of the same VPN gateway.
@@ -29836,7 +29849,7 @@ export default class Client extends OpenApi {
29836
29849
  * Invokes the ModifyVpnGatewayAttribute operation to modify the name, description, or routing automatic propagation feature of a VPN gateway.
29837
29850
  *
29838
29851
  * @remarks
29839
- * - **ModifyVpnGatewayAttribute** is an asynchronous operation. After you call this operation, the system returns the VPN gateway information, but the configuration has not been modified yet. The modification task is still running in the background. You can call [DescribeVpnGateway](https://help.aliyun.com/document_detail/73720.html) to query the modification status of the VPN gateway configuration:
29852
+ * - **ModifyVpnGatewayAttribute** is an asynchronous operation. After you call this operation, the system returns the VPN gateway information, but the configuration of the VPN gateway has not been modified yet. The modification task is still running in the background. You can call [DescribeVpnGateway](https://help.aliyun.com/document_detail/73720.html) to query the modification status of the VPN gateway configuration:
29840
29853
  * - If the VPN gateway is in the **updating** state, the configuration is being modified.
29841
29854
  * - If the VPN gateway is in the **active** state, the configuration has been modified.
29842
29855
  * - **ModifyVpnGatewayAttribute** does not support concurrent modifications to the configuration of the same VPN gateway.
@@ -29966,13 +29979,13 @@ export default class Client extends OpenApi {
29966
29979
  }
29967
29980
 
29968
29981
  /**
29969
- * Invokes the ModifyVpnPbrRouteEntryPriority operation to modify the policy priority of a policy-based routing entry.
29982
+ * Invokes the ModifyVpnPbrRouteEntryPriority operation to modify the policy priority of a policy-based routing.
29970
29983
  *
29971
29984
  * @remarks
29972
- * - **ModifyVpnPbrRouteEntryPriority** is an asynchronous operation. After you send a request, the system returns a request ID, but the policy-based routing entry has not been modified yet. The modification node is still running 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 modification status of the policy-based routing entry:
29973
- * - If the VPN gateway instance is in the **updating** state, the policy-based routing entry is being modified.
29974
- * - If the VPN gateway instance is in the **active** state, the policy-based routing entry has been modified.
29975
- * - **ModifyVpnPbrRouteEntryPriority** does not support concurrent modifications of policy-based routing entries on the same VPN gateway instance.
29985
+ * - **ModifyVpnPbrRouteEntryPriority** is an asynchronous operation. After you send a request, the system returns a request ID. However, the policy-based routing has not been modified yet because the modification node is still running 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 and determine the modification status of the policy-based routing:
29986
+ * - If the VPN gateway instance is in the **updating** state, the policy-based routing is being modified.
29987
+ * - If the VPN gateway instance is in the **active** state, the policy-based routing has been modified.
29988
+ * - **ModifyVpnPbrRouteEntryPriority** does not support concurrent modifications of policy-based routing on the same VPN gateway instance.
29976
29989
  *
29977
29990
  * @param request - ModifyVpnPbrRouteEntryPriorityRequest
29978
29991
  * @param runtime - runtime options for this request RuntimeOptions
@@ -30051,13 +30064,13 @@ export default class Client extends OpenApi {
30051
30064
  }
30052
30065
 
30053
30066
  /**
30054
- * Invokes the ModifyVpnPbrRouteEntryPriority operation to modify the policy priority of a policy-based routing entry.
30067
+ * Invokes the ModifyVpnPbrRouteEntryPriority operation to modify the policy priority of a policy-based routing.
30055
30068
  *
30056
30069
  * @remarks
30057
- * - **ModifyVpnPbrRouteEntryPriority** is an asynchronous operation. After you send a request, the system returns a request ID, but the policy-based routing entry has not been modified yet. The modification node is still running 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 modification status of the policy-based routing entry:
30058
- * - If the VPN gateway instance is in the **updating** state, the policy-based routing entry is being modified.
30059
- * - If the VPN gateway instance is in the **active** state, the policy-based routing entry has been modified.
30060
- * - **ModifyVpnPbrRouteEntryPriority** does not support concurrent modifications of policy-based routing entries on the same VPN gateway instance.
30070
+ * - **ModifyVpnPbrRouteEntryPriority** is an asynchronous operation. After you send a request, the system returns a request ID. However, the policy-based routing has not been modified yet because the modification node is still running 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 and determine the modification status of the policy-based routing:
30071
+ * - If the VPN gateway instance is in the **updating** state, the policy-based routing is being modified.
30072
+ * - If the VPN gateway instance is in the **active** state, the policy-based routing has been modified.
30073
+ * - **ModifyVpnPbrRouteEntryPriority** does not support concurrent modifications of policy-based routing on the same VPN gateway instance.
30061
30074
  *
30062
30075
  * @param request - ModifyVpnPbrRouteEntryPriorityRequest
30063
30076
  * @returns ModifyVpnPbrRouteEntryPriorityResponse
@@ -30181,12 +30194,12 @@ export default class Client extends OpenApi {
30181
30194
  * Modifies the weight of a destination route by calling the ModifyVpnRouteEntryWeight operation.
30182
30195
  *
30183
30196
  * @remarks
30184
- * > This operation is applicable only to VPN gateway instances that support IPsec-VPN connections in single-tunnel mode. For VPN gateway instances that support IPsec-VPN connections in dual-tunnel mode, the weight does not take effect even if you successfully modify it by calling this operation.
30197
+ * > This operation is applicable only to VPN gateway instances that support IPsec-VPN connections in single-tunnel mode. For VPN gateway instances that support IPsec-VPN connections in dual-tunnel mode, the weight does not take effect even if it is modified by calling this operation.
30185
30198
  * - If active/standby destination routes exist on a VPN gateway instance and you want to modify the weight of the active destination route, delete the standby destination route first. After the active destination route is modified, reconfigure the standby destination route. If you want to modify the weight of the standby destination route, delete the active destination route first. After the standby destination route is modified, reconfigure the active destination route. To delete a destination route, see [DeleteVpnRouteEntry](https://help.aliyun.com/document_detail/2526961.html).
30186
- * - The **ModifyVpnRouteEntryWeight** operation is asynchronous. After a request is sent, the system returns a request ID. However, the weight of the VPN destination route is not yet modified, and the modification task is still running in the background. You can call [DescribeVpnGateway](https://help.aliyun.com/document_detail/73720.html) to query the modification status of the weight:
30199
+ * - **ModifyVpnRouteEntryWeight** is an asynchronous operation. After a request is sent, the system returns a request ID. However, the weight of the VPN destination route has not been modified yet because the modification task is still running in the background. You can call [DescribeVpnGateway](https://help.aliyun.com/document_detail/73720.html) to query the modification status of the weight:
30187
30200
  * - If the VPN destination route is in the **updating** state, the weight is being modified.
30188
- * - If the VPN destination route is in the **active** state, the weight is modified.
30189
- * - The **ModifyVpnRouteEntryWeight** operation does not support concurrent weight modifications for destination routes on the same VPN gateway.
30201
+ * - If the VPN destination route is in the **active** state, the weight has been modified.
30202
+ * - **ModifyVpnRouteEntryWeight** does not support concurrent modification of destination route weights on the same VPN gateway.
30190
30203
  *
30191
30204
  * @param request - ModifyVpnRouteEntryWeightRequest
30192
30205
  * @param runtime - runtime options for this request RuntimeOptions
@@ -30264,12 +30277,12 @@ export default class Client extends OpenApi {
30264
30277
  * Modifies the weight of a destination route by calling the ModifyVpnRouteEntryWeight operation.
30265
30278
  *
30266
30279
  * @remarks
30267
- * > This operation is applicable only to VPN gateway instances that support IPsec-VPN connections in single-tunnel mode. For VPN gateway instances that support IPsec-VPN connections in dual-tunnel mode, the weight does not take effect even if you successfully modify it by calling this operation.
30280
+ * > This operation is applicable only to VPN gateway instances that support IPsec-VPN connections in single-tunnel mode. For VPN gateway instances that support IPsec-VPN connections in dual-tunnel mode, the weight does not take effect even if it is modified by calling this operation.
30268
30281
  * - If active/standby destination routes exist on a VPN gateway instance and you want to modify the weight of the active destination route, delete the standby destination route first. After the active destination route is modified, reconfigure the standby destination route. If you want to modify the weight of the standby destination route, delete the active destination route first. After the standby destination route is modified, reconfigure the active destination route. To delete a destination route, see [DeleteVpnRouteEntry](https://help.aliyun.com/document_detail/2526961.html).
30269
- * - The **ModifyVpnRouteEntryWeight** operation is asynchronous. After a request is sent, the system returns a request ID. However, the weight of the VPN destination route is not yet modified, and the modification task is still running in the background. You can call [DescribeVpnGateway](https://help.aliyun.com/document_detail/73720.html) to query the modification status of the weight:
30282
+ * - **ModifyVpnRouteEntryWeight** is an asynchronous operation. After a request is sent, the system returns a request ID. However, the weight of the VPN destination route has not been modified yet because the modification task is still running in the background. You can call [DescribeVpnGateway](https://help.aliyun.com/document_detail/73720.html) to query the modification status of the weight:
30270
30283
  * - If the VPN destination route is in the **updating** state, the weight is being modified.
30271
- * - If the VPN destination route is in the **active** state, the weight is modified.
30272
- * - The **ModifyVpnRouteEntryWeight** operation does not support concurrent weight modifications for destination routes on the same VPN gateway.
30284
+ * - If the VPN destination route is in the **active** state, the weight has been modified.
30285
+ * - **ModifyVpnRouteEntryWeight** does not support concurrent modification of destination route weights on the same VPN gateway.
30273
30286
  *
30274
30287
  * @param request - ModifyVpnRouteEntryWeightRequest
30275
30288
  * @returns ModifyVpnRouteEntryWeightResponse
@@ -33760,7 +33773,7 @@ export default class Client extends OpenApi {
33760
33773
  }
33761
33774
 
33762
33775
  /**
33763
- * Updates the configuration of an IPsec server by calling the UpdateIpsecServer operation.
33776
+ * Calls the UpdateIpsecServer operation to update the configuration of an IPsec server.
33764
33777
  *
33765
33778
  * @remarks
33766
33779
  * - If you modify only the **IpsecServerName** of the IPsec server, this operation is synchronous. If you modify configurations other than **IpsecServerName**, this operation is asynchronous.
@@ -33842,7 +33855,7 @@ export default class Client extends OpenApi {
33842
33855
  }
33843
33856
 
33844
33857
  /**
33845
- * Updates the configuration of an IPsec server by calling the UpdateIpsecServer operation.
33858
+ * Calls the UpdateIpsecServer operation to update the configuration of an IPsec server.
33846
33859
  *
33847
33860
  * @remarks
33848
33861
  * - If you modify only the **IpsecServerName** of the IPsec server, this operation is synchronous. If you modify configurations other than **IpsecServerName**, this operation is asynchronous.