@alicloud/vpc20160428 7.2.4 → 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.
- package/dist/client.d.ts +232 -228
- package/dist/client.js +263 -255
- package/dist/client.js.map +1 -1
- package/dist/models/ActivateRouterInterfaceRequest.d.ts +1 -1
- package/dist/models/AssociateMacSecKeyRequest.d.ts +3 -3
- package/dist/models/AssociatePhysicalConnectionToVirtualBorderRouterRequest.d.ts +5 -7
- package/dist/models/AssociatePhysicalConnectionToVirtualBorderRouterRequest.js.map +1 -1
- package/dist/models/AssociateVpnGatewayWithCertificateRequest.d.ts +3 -3
- package/dist/models/AttachVbrToVpconnRequest.d.ts +3 -3
- package/dist/models/CancelPhysicalConnectionRequest.d.ts +1 -1
- package/dist/models/CheckVpnBgpEnabledRequest.d.ts +1 -1
- package/dist/models/CompletePhysicalConnectionLoarequest.d.ts +4 -4
- package/dist/models/CreateCustomerGatewayRequest.d.ts +4 -4
- package/dist/models/CreateCustomerGatewayResponseBody.d.ts +2 -2
- package/dist/models/CreateFailoverTestJobRequest.d.ts +5 -5
- package/dist/models/CreateIpsecServerRequest.d.ts +2 -2
- package/dist/models/CreatePhysicalConnectionRequest.d.ts +13 -11
- package/dist/models/CreatePhysicalConnectionRequest.js.map +1 -1
- package/dist/models/CreatePhysicalConnectionSetupOrderRequest.d.ts +10 -8
- package/dist/models/CreatePhysicalConnectionSetupOrderRequest.js.map +1 -1
- package/dist/models/CreateSslVpnServerRequest.d.ts +11 -11
- package/dist/models/CreateVbrHaRequest.d.ts +5 -5
- package/dist/models/CreateVbrHaResponseBody.d.ts +1 -1
- package/dist/models/CreateVcoRouteEntryRequest.d.ts +2 -2
- package/dist/models/CreateVcoRouteEntryResponseBody.d.ts +1 -1
- package/dist/models/CreateVpconnFromVbrRequest.d.ts +2 -2
- package/dist/models/CreateVpnAttachmentRequest.d.ts +73 -133
- package/dist/models/CreateVpnAttachmentRequest.js.map +1 -1
- package/dist/models/CreateVpnAttachmentResponseBody.d.ts +3 -3
- package/dist/models/CreateVpnConnectionRequest.d.ts +95 -131
- package/dist/models/CreateVpnConnectionRequest.js.map +1 -1
- package/dist/models/CreateVpnConnectionResponseBody.d.ts +1 -1
- package/dist/models/CreateVpnGatewayRequest.d.ts +17 -17
- package/dist/models/CreateVpnGatewayResponseBody.d.ts +2 -2
- package/dist/models/CreateVpnPbrRouteEntryRequest.d.ts +13 -13
- package/dist/models/CreateVpnPbrRouteEntryResponseBody.d.ts +6 -6
- package/dist/models/CreateVswitchCidrReservationRequest.d.ts +15 -7
- package/dist/models/CreateVswitchCidrReservationRequest.js +2 -0
- package/dist/models/CreateVswitchCidrReservationRequest.js.map +1 -1
- package/dist/models/CreateVswitchRequest.d.ts +9 -9
- package/dist/models/DeleteBgpGroupRequest.d.ts +2 -2
- package/dist/models/DeleteFailoverTestJobRequest.d.ts +4 -4
- package/dist/models/DeleteIpsecServerRequest.d.ts +4 -4
- package/dist/models/DeleteNatGatewayRequest.d.ts +4 -4
- package/dist/models/DeleteVbrHaRequest.d.ts +3 -3
- package/dist/models/DeleteVpnGatewayRequest.d.ts +3 -3
- package/dist/models/DeleteVpnRouteEntryRequest.d.ts +2 -2
- package/dist/models/DescribeCustomerGatewayRequest.d.ts +1 -1
- package/dist/models/DescribeCustomerGatewayResponseBody.d.ts +2 -2
- package/dist/models/DescribeCustomerGatewaysRequest.d.ts +1 -1
- package/dist/models/DescribeEipAddressesRequest.d.ts +7 -75
- package/dist/models/DescribeEipAddressesRequest.js.map +1 -1
- package/dist/models/DescribeExpressConnectTrafficQosQueueRequest.d.ts +5 -3
- package/dist/models/DescribeExpressConnectTrafficQosQueueRequest.js.map +1 -1
- package/dist/models/DescribeExpressConnectTrafficQosQueueResponseBody.d.ts +12 -12
- package/dist/models/DescribeExpressConnectTrafficQosRuleRequest.d.ts +10 -6
- package/dist/models/DescribeExpressConnectTrafficQosRuleRequest.js.map +1 -1
- package/dist/models/DescribeExpressConnectTrafficQosRuleResponseBody.d.ts +16 -16
- package/dist/models/DescribeFailoverTestJobRequest.d.ts +2 -2
- package/dist/models/DescribeFailoverTestJobResponseBody.d.ts +6 -6
- package/dist/models/DescribeFailoverTestJobsRequest.d.ts +8 -8
- package/dist/models/DescribeFailoverTestJobsResponseBody.d.ts +14 -14
- package/dist/models/DescribePhysicalConnectionLoarequest.d.ts +1 -1
- package/dist/models/DescribePhysicalConnectionLoaresponseBody.d.ts +8 -4
- package/dist/models/DescribePhysicalConnectionLoaresponseBody.js.map +1 -1
- package/dist/models/DescribePhysicalConnectionsRequest.d.ts +4 -0
- package/dist/models/DescribePhysicalConnectionsRequest.js.map +1 -1
- package/dist/models/DescribeRouterInterfaceAttributeResponseBody.d.ts +22 -22
- package/dist/models/DescribeSslVpnClientCertRequest.d.ts +1 -1
- package/dist/models/DescribeSslVpnClientCertResponseBody.d.ts +3 -3
- package/dist/models/DescribeSslVpnServersRequest.d.ts +1 -1
- package/dist/models/DescribeSslVpnServersResponseBody.d.ts +1 -1
- package/dist/models/DescribeTagKeysForExpressConnectRequest.d.ts +2 -0
- package/dist/models/DescribeTagKeysForExpressConnectRequest.js.map +1 -1
- package/dist/models/DescribeVbrHaRequest.d.ts +6 -6
- package/dist/models/DescribeVbrHaResponseBody.d.ts +2 -2
- package/dist/models/DescribeVcoRouteEntriesResponseBody.d.ts +10 -10
- package/dist/models/DescribeVirtualBorderRoutersRequest.d.ts +6 -26
- package/dist/models/DescribeVirtualBorderRoutersRequest.js.map +1 -1
- package/dist/models/DescribeVirtualBorderRoutersResponseBody.d.ts +2 -2
- package/dist/models/DescribeVpcsRequest.d.ts +4 -4
- package/dist/models/DescribeVpcsResponseBody.d.ts +1 -1
- package/dist/models/DescribeVpnAttachmentsRequest.d.ts +4 -4
- package/dist/models/DescribeVpnAttachmentsResponseBody.d.ts +9 -9
- package/dist/models/DescribeVpnConnectionLogsRequest.d.ts +2 -2
- package/dist/models/DescribeVpnConnectionLogsResponseBody.d.ts +1 -1
- package/dist/models/DescribeVpnConnectionRequest.d.ts +1 -1
- package/dist/models/DescribeVpnConnectionResponseBody.d.ts +21 -72
- package/dist/models/DescribeVpnConnectionResponseBody.js.map +1 -1
- package/dist/models/DescribeVpnConnectionsRequest.d.ts +6 -8
- package/dist/models/DescribeVpnConnectionsRequest.js.map +1 -1
- package/dist/models/DescribeVpnCrossAccountAuthorizationsRequest.d.ts +2 -2
- package/dist/models/DescribeVpnCrossAccountAuthorizationsResponseBody.d.ts +5 -5
- package/dist/models/DescribeVpnGatewayResponseBody.d.ts +8 -8
- package/dist/models/DescribeVpnGatewaysRequest.d.ts +2 -2
- package/dist/models/DescribeVpnGatewaysResponseBody.d.ts +1 -1
- package/dist/models/DescribeVpnPbrRouteEntriesRequest.d.ts +1 -1
- package/dist/models/DescribeVpnPbrRouteEntriesResponseBody.d.ts +1 -1
- package/dist/models/DescribeVpnSslServerLogsRequest.d.ts +2 -2
- package/dist/models/DescribeVswitchesRequest.d.ts +7 -7
- package/dist/models/DescribeVswitchesResponseBody.d.ts +1 -1
- package/dist/models/DiagnoseVpnGatewayRequest.d.ts +1 -1
- package/dist/models/DiagnoseVpnGatewayResponseBody.d.ts +2 -2
- package/dist/models/DisassociateMacSecKeyRequest.d.ts +2 -2
- package/dist/models/DissociateVpnGatewayWithCertificateRequest.d.ts +2 -2
- package/dist/models/DownloadVpnConnectionConfigResponseBody.d.ts +11 -11
- package/dist/models/GetVpnGatewayDiagnoseResultRequest.d.ts +3 -3
- package/dist/models/GetVpnGatewayDiagnoseResultResponseBody.d.ts +12 -12
- package/dist/models/GrantInstanceToVbrRequest.d.ts +8 -8
- package/dist/models/GrantInstanceToVbrShrinkRequest.d.ts +8 -8
- package/dist/models/ListBusinessAccessPointsResponseBody.d.ts +40 -2
- package/dist/models/ListBusinessAccessPointsResponseBody.js.map +1 -1
- package/dist/models/ListIpsecServerLogsRequest.d.ts +2 -2
- package/dist/models/ListIpsecServerLogsResponseBody.d.ts +1 -1
- package/dist/models/ListIpsecServersRequest.d.ts +3 -3
- package/dist/models/ListIpsecServersResponseBody.d.ts +7 -7
- package/dist/models/ListVpnCertificateAssociationsRequest.d.ts +3 -3
- package/dist/models/ListVpnCertificateAssociationsResponseBody.d.ts +2 -2
- package/dist/models/ModifyCustomerGatewayAttributeRequest.d.ts +1 -1
- package/dist/models/ModifySslVpnServerRequest.d.ts +11 -11
- package/dist/models/ModifySslVpnServerResponseBody.d.ts +1 -1
- package/dist/models/ModifyVcoRouteEntryWeightRequest.d.ts +4 -4
- package/dist/models/ModifyVpnAttachmentAttributeRequest.d.ts +57 -133
- package/dist/models/ModifyVpnAttachmentAttributeRequest.js.map +1 -1
- package/dist/models/ModifyVpnAttachmentAttributeResponseBody.d.ts +54 -96
- package/dist/models/ModifyVpnAttachmentAttributeResponseBody.js.map +1 -1
- package/dist/models/ModifyVpnConnectionAttributeRequest.d.ts +77 -148
- package/dist/models/ModifyVpnConnectionAttributeRequest.js.map +1 -1
- package/dist/models/ModifyVpnConnectionAttributeResponseBody.d.ts +25 -52
- package/dist/models/ModifyVpnConnectionAttributeResponseBody.js.map +1 -1
- package/dist/models/ModifyVpnGatewayAttributeRequest.d.ts +5 -5
- package/dist/models/ModifyVpnPbrRouteEntryPriorityRequest.d.ts +5 -5
- package/dist/models/ModifyVpnRouteEntryWeightRequest.d.ts +2 -2
- package/dist/models/MoveVpnResourceGroupRequest.d.ts +2 -2
- package/dist/models/UpdateIpsecServerRequest.d.ts +1 -1
- package/package.json +1 -1
- package/src/client.ts +264 -255
- package/src/models/ActivateRouterInterfaceRequest.ts +1 -1
- package/src/models/AssociateMacSecKeyRequest.ts +3 -3
- package/src/models/AssociatePhysicalConnectionToVirtualBorderRouterRequest.ts +5 -7
- package/src/models/AssociateVpnGatewayWithCertificateRequest.ts +3 -3
- package/src/models/AttachVbrToVpconnRequest.ts +3 -3
- package/src/models/CancelPhysicalConnectionRequest.ts +1 -1
- package/src/models/CheckVpnBgpEnabledRequest.ts +1 -1
- package/src/models/CompletePhysicalConnectionLoarequest.ts +4 -4
- package/src/models/CreateCustomerGatewayRequest.ts +4 -4
- package/src/models/CreateCustomerGatewayResponseBody.ts +2 -2
- package/src/models/CreateFailoverTestJobRequest.ts +5 -5
- package/src/models/CreateIpsecServerRequest.ts +2 -2
- package/src/models/CreatePhysicalConnectionRequest.ts +13 -11
- package/src/models/CreatePhysicalConnectionSetupOrderRequest.ts +10 -8
- package/src/models/CreateSslVpnServerRequest.ts +11 -11
- package/src/models/CreateVbrHaRequest.ts +5 -5
- package/src/models/CreateVbrHaResponseBody.ts +1 -1
- package/src/models/CreateVcoRouteEntryRequest.ts +2 -2
- package/src/models/CreateVcoRouteEntryResponseBody.ts +1 -1
- package/src/models/CreateVpconnFromVbrRequest.ts +2 -2
- package/src/models/CreateVpnAttachmentRequest.ts +75 -135
- package/src/models/CreateVpnAttachmentResponseBody.ts +3 -3
- package/src/models/CreateVpnConnectionRequest.ts +99 -135
- package/src/models/CreateVpnConnectionResponseBody.ts +1 -1
- package/src/models/CreateVpnGatewayRequest.ts +17 -17
- package/src/models/CreateVpnGatewayResponseBody.ts +2 -2
- package/src/models/CreateVpnPbrRouteEntryRequest.ts +13 -13
- package/src/models/CreateVpnPbrRouteEntryResponseBody.ts +6 -6
- package/src/models/CreateVswitchCidrReservationRequest.ts +17 -7
- package/src/models/CreateVswitchRequest.ts +9 -9
- package/src/models/DeleteBgpGroupRequest.ts +2 -2
- package/src/models/DeleteFailoverTestJobRequest.ts +4 -4
- package/src/models/DeleteIpsecServerRequest.ts +4 -4
- package/src/models/DeleteNatGatewayRequest.ts +4 -4
- package/src/models/DeleteVbrHaRequest.ts +3 -3
- package/src/models/DeleteVpnGatewayRequest.ts +3 -3
- package/src/models/DeleteVpnRouteEntryRequest.ts +2 -2
- package/src/models/DescribeCustomerGatewayRequest.ts +1 -1
- package/src/models/DescribeCustomerGatewayResponseBody.ts +2 -2
- package/src/models/DescribeCustomerGatewaysRequest.ts +1 -1
- package/src/models/DescribeEipAddressesRequest.ts +8 -76
- package/src/models/DescribeExpressConnectTrafficQosQueueRequest.ts +5 -3
- package/src/models/DescribeExpressConnectTrafficQosQueueResponseBody.ts +12 -12
- package/src/models/DescribeExpressConnectTrafficQosRuleRequest.ts +10 -6
- package/src/models/DescribeExpressConnectTrafficQosRuleResponseBody.ts +16 -16
- package/src/models/DescribeFailoverTestJobRequest.ts +2 -2
- package/src/models/DescribeFailoverTestJobResponseBody.ts +6 -6
- package/src/models/DescribeFailoverTestJobsRequest.ts +8 -8
- package/src/models/DescribeFailoverTestJobsResponseBody.ts +14 -14
- package/src/models/DescribePhysicalConnectionLoarequest.ts +1 -1
- package/src/models/DescribePhysicalConnectionLoaresponseBody.ts +8 -4
- package/src/models/DescribePhysicalConnectionsRequest.ts +4 -0
- package/src/models/DescribeRouterInterfaceAttributeResponseBody.ts +22 -22
- package/src/models/DescribeSslVpnClientCertRequest.ts +1 -1
- package/src/models/DescribeSslVpnClientCertResponseBody.ts +3 -3
- package/src/models/DescribeSslVpnServersRequest.ts +1 -1
- package/src/models/DescribeSslVpnServersResponseBody.ts +1 -1
- package/src/models/DescribeTagKeysForExpressConnectRequest.ts +2 -0
- package/src/models/DescribeVbrHaRequest.ts +6 -6
- package/src/models/DescribeVbrHaResponseBody.ts +2 -2
- package/src/models/DescribeVcoRouteEntriesResponseBody.ts +10 -10
- package/src/models/DescribeVirtualBorderRoutersRequest.ts +6 -26
- package/src/models/DescribeVirtualBorderRoutersResponseBody.ts +2 -2
- package/src/models/DescribeVpcsRequest.ts +4 -4
- package/src/models/DescribeVpcsResponseBody.ts +1 -1
- package/src/models/DescribeVpnAttachmentsRequest.ts +4 -4
- package/src/models/DescribeVpnAttachmentsResponseBody.ts +9 -9
- package/src/models/DescribeVpnConnectionLogsRequest.ts +2 -2
- package/src/models/DescribeVpnConnectionLogsResponseBody.ts +1 -1
- package/src/models/DescribeVpnConnectionRequest.ts +2 -2
- package/src/models/DescribeVpnConnectionResponseBody.ts +21 -72
- package/src/models/DescribeVpnConnectionsRequest.ts +7 -9
- package/src/models/DescribeVpnCrossAccountAuthorizationsRequest.ts +2 -2
- package/src/models/DescribeVpnCrossAccountAuthorizationsResponseBody.ts +5 -5
- package/src/models/DescribeVpnGatewayResponseBody.ts +8 -8
- package/src/models/DescribeVpnGatewaysRequest.ts +2 -2
- package/src/models/DescribeVpnGatewaysResponseBody.ts +1 -1
- package/src/models/DescribeVpnPbrRouteEntriesRequest.ts +1 -1
- package/src/models/DescribeVpnPbrRouteEntriesResponseBody.ts +1 -1
- package/src/models/DescribeVpnSslServerLogsRequest.ts +2 -2
- package/src/models/DescribeVswitchesRequest.ts +7 -7
- package/src/models/DescribeVswitchesResponseBody.ts +1 -1
- package/src/models/DiagnoseVpnGatewayRequest.ts +1 -1
- package/src/models/DiagnoseVpnGatewayResponseBody.ts +2 -2
- package/src/models/DisassociateMacSecKeyRequest.ts +2 -2
- package/src/models/DissociateVpnGatewayWithCertificateRequest.ts +2 -2
- package/src/models/DownloadVpnConnectionConfigResponseBody.ts +11 -11
- package/src/models/GetVpnGatewayDiagnoseResultRequest.ts +3 -3
- package/src/models/GetVpnGatewayDiagnoseResultResponseBody.ts +12 -12
- package/src/models/GrantInstanceToVbrRequest.ts +8 -8
- package/src/models/GrantInstanceToVbrShrinkRequest.ts +8 -8
- package/src/models/ListBusinessAccessPointsResponseBody.ts +40 -2
- package/src/models/ListIpsecServerLogsRequest.ts +2 -2
- package/src/models/ListIpsecServerLogsResponseBody.ts +1 -1
- package/src/models/ListIpsecServersRequest.ts +3 -3
- package/src/models/ListIpsecServersResponseBody.ts +7 -7
- package/src/models/ListVpnCertificateAssociationsRequest.ts +3 -3
- package/src/models/ListVpnCertificateAssociationsResponseBody.ts +2 -2
- package/src/models/ModifyCustomerGatewayAttributeRequest.ts +1 -1
- package/src/models/ModifySslVpnServerRequest.ts +11 -11
- package/src/models/ModifySslVpnServerResponseBody.ts +1 -1
- package/src/models/ModifyVcoRouteEntryWeightRequest.ts +4 -4
- package/src/models/ModifyVpnAttachmentAttributeRequest.ts +57 -133
- package/src/models/ModifyVpnAttachmentAttributeResponseBody.ts +55 -97
- package/src/models/ModifyVpnConnectionAttributeRequest.ts +84 -155
- package/src/models/ModifyVpnConnectionAttributeResponseBody.ts +26 -53
- package/src/models/ModifyVpnGatewayAttributeRequest.ts +5 -5
- package/src/models/ModifyVpnPbrRouteEntryPriorityRequest.ts +5 -5
- package/src/models/ModifyVpnRouteEntryWeightRequest.ts +2 -2
- package/src/models/MoveVpnResourceGroupRequest.ts +2 -2
- package/src/models/UpdateIpsecServerRequest.ts +1 -1
package/dist/client.d.ts
CHANGED
|
@@ -12,7 +12,8 @@ export default class Client extends OpenApi {
|
|
|
12
12
|
* Activates a router interface that is in the Inactive state.
|
|
13
13
|
*
|
|
14
14
|
* @remarks
|
|
15
|
-
* After you call the ActivateRouterInterface operation, the router interface enters the **Activating** state
|
|
15
|
+
* After you call the ActivateRouterInterface operation, the router interface enters the **Activating** state and then enters the **Active** state after activation succeeds.
|
|
16
|
+
* 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.
|
|
16
17
|
* > You cannot activate a router interface that has an overdue payment.
|
|
17
18
|
*
|
|
18
19
|
* @param request - ActivateRouterInterfaceRequest
|
|
@@ -24,7 +25,8 @@ export default class Client extends OpenApi {
|
|
|
24
25
|
* Activates a router interface that is in the Inactive state.
|
|
25
26
|
*
|
|
26
27
|
* @remarks
|
|
27
|
-
* After you call the ActivateRouterInterface operation, the router interface enters the **Activating** state
|
|
28
|
+
* After you call the ActivateRouterInterface operation, the router interface enters the **Activating** state and then enters the **Active** state after activation succeeds.
|
|
29
|
+
* 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.
|
|
28
30
|
* > You cannot activate a router interface that has an overdue payment.
|
|
29
31
|
*
|
|
30
32
|
* @param request - ActivateRouterInterfaceRequest
|
|
@@ -506,7 +508,7 @@ export default class Client extends OpenApi {
|
|
|
506
508
|
*/
|
|
507
509
|
associateHaVip(request: $_model.AssociateHaVipRequest): Promise<$_model.AssociateHaVipResponse>;
|
|
508
510
|
/**
|
|
509
|
-
* 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
|
|
511
|
+
* 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.
|
|
510
512
|
*
|
|
511
513
|
* @remarks
|
|
512
514
|
* To use this feature, the following conditions must be met:
|
|
@@ -515,7 +517,7 @@ export default class Client extends OpenApi {
|
|
|
515
517
|
* - Only dedicated Express Connect circuits are supported.
|
|
516
518
|
* Other notes:
|
|
517
519
|
* - A maximum of three CKN and CAK pairs can be configured.
|
|
518
|
-
* - Associating a key that is currently in the Disassociated state
|
|
520
|
+
* - Associating a key that is currently in the Disassociated state disassociates the previously active key.
|
|
519
521
|
* - Associating a key that is currently in the AssociatedFailed state triggers the device to renegotiate the session.
|
|
520
522
|
*
|
|
521
523
|
* @param request - AssociateMacSecKeyRequest
|
|
@@ -524,7 +526,7 @@ export default class Client extends OpenApi {
|
|
|
524
526
|
*/
|
|
525
527
|
associateMacSecKeyWithOptions(request: $_model.AssociateMacSecKeyRequest, runtime: $dara.RuntimeOptions): Promise<$_model.AssociateMacSecKeyResponse>;
|
|
526
528
|
/**
|
|
527
|
-
* 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
|
|
529
|
+
* 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.
|
|
528
530
|
*
|
|
529
531
|
* @remarks
|
|
530
532
|
* To use this feature, the following conditions must be met:
|
|
@@ -533,7 +535,7 @@ export default class Client extends OpenApi {
|
|
|
533
535
|
* - Only dedicated Express Connect circuits are supported.
|
|
534
536
|
* Other notes:
|
|
535
537
|
* - A maximum of three CKN and CAK pairs can be configured.
|
|
536
|
-
* - Associating a key that is currently in the Disassociated state
|
|
538
|
+
* - Associating a key that is currently in the Disassociated state disassociates the previously active key.
|
|
537
539
|
* - Associating a key that is currently in the AssociatedFailed state triggers the device to renegotiate the session.
|
|
538
540
|
*
|
|
539
541
|
* @param request - AssociateMacSecKeyRequest
|
|
@@ -694,18 +696,18 @@ export default class Client extends OpenApi {
|
|
|
694
696
|
* Associates a certificate with a VPN gateway by calling the AssociateVpnGatewayWithCertificate operation.
|
|
695
697
|
*
|
|
696
698
|
* @remarks
|
|
697
|
-
* Before you
|
|
698
|
-
* - Only
|
|
699
|
-
* - The SSL certificates must use
|
|
699
|
+
* Before you associate a VPN gateway with an SSL certificate, take note of the following information:
|
|
700
|
+
* - 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.
|
|
701
|
+
* - The SSL certificates must use SM algorithms.
|
|
700
702
|
* - You cannot specify the same SSL certificate as both the encryption certificate and the signing certificate for the same VPN gateway instance.
|
|
701
703
|
* <props="china">
|
|
702
|
-
* - 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).
|
|
703
|
-
* - 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
|
|
704
|
+
* - 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).
|
|
705
|
+
* - 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:
|
|
704
706
|
* - If the VPN gateway is in the **updating** state, the SSL certificate is being attached.
|
|
705
707
|
* - If the VPN gateway is in the **active** state, the SSL certificate is attached.
|
|
706
|
-
* - The **AssociateVpnGatewayWithCertificate** operation does not support concurrent SSL certificate
|
|
708
|
+
* - The **AssociateVpnGatewayWithCertificate** operation does not support concurrent SSL certificate binding requests for the same VPN gateway.
|
|
707
709
|
* ### Before you begin
|
|
708
|
-
* Make sure that you have two SSL certificates that use
|
|
710
|
+
* 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).
|
|
709
711
|
*
|
|
710
712
|
* @param request - AssociateVpnGatewayWithCertificateRequest
|
|
711
713
|
* @param runtime - runtime options for this request RuntimeOptions
|
|
@@ -716,18 +718,18 @@ export default class Client extends OpenApi {
|
|
|
716
718
|
* Associates a certificate with a VPN gateway by calling the AssociateVpnGatewayWithCertificate operation.
|
|
717
719
|
*
|
|
718
720
|
* @remarks
|
|
719
|
-
* Before you
|
|
720
|
-
* - Only
|
|
721
|
-
* - The SSL certificates must use
|
|
721
|
+
* Before you associate a VPN gateway with an SSL certificate, take note of the following information:
|
|
722
|
+
* - 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.
|
|
723
|
+
* - The SSL certificates must use SM algorithms.
|
|
722
724
|
* - You cannot specify the same SSL certificate as both the encryption certificate and the signing certificate for the same VPN gateway instance.
|
|
723
725
|
* <props="china">
|
|
724
|
-
* - 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).
|
|
725
|
-
* - 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
|
|
726
|
+
* - 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).
|
|
727
|
+
* - 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:
|
|
726
728
|
* - If the VPN gateway is in the **updating** state, the SSL certificate is being attached.
|
|
727
729
|
* - If the VPN gateway is in the **active** state, the SSL certificate is attached.
|
|
728
|
-
* - The **AssociateVpnGatewayWithCertificate** operation does not support concurrent SSL certificate
|
|
730
|
+
* - The **AssociateVpnGatewayWithCertificate** operation does not support concurrent SSL certificate binding requests for the same VPN gateway.
|
|
729
731
|
* ### Before you begin
|
|
730
|
-
* Make sure that you have two SSL certificates that use
|
|
732
|
+
* 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).
|
|
731
733
|
*
|
|
732
734
|
* @param request - AssociateVpnGatewayWithCertificateRequest
|
|
733
735
|
* @returns AssociateVpnGatewayWithCertificateResponse
|
|
@@ -801,10 +803,10 @@ export default class Client extends OpenApi {
|
|
|
801
803
|
*/
|
|
802
804
|
cancelCommonBandwidthPackageIpBandwidth(request: $_model.CancelCommonBandwidthPackageIpBandwidthRequest): Promise<$_model.CancelCommonBandwidthPackageIpBandwidthResponse>;
|
|
803
805
|
/**
|
|
804
|
-
* Cancels access
|
|
806
|
+
* Cancels the access of an Express Connect circuit. After the cancellation, the Express Connect circuit enters the Canceled state.
|
|
805
807
|
*
|
|
806
808
|
* @remarks
|
|
807
|
-
* You can cancel access
|
|
809
|
+
* 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**.
|
|
808
810
|
*
|
|
809
811
|
* @param request - CancelPhysicalConnectionRequest
|
|
810
812
|
* @param runtime - runtime options for this request RuntimeOptions
|
|
@@ -812,10 +814,10 @@ export default class Client extends OpenApi {
|
|
|
812
814
|
*/
|
|
813
815
|
cancelPhysicalConnectionWithOptions(request: $_model.CancelPhysicalConnectionRequest, runtime: $dara.RuntimeOptions): Promise<$_model.CancelPhysicalConnectionResponse>;
|
|
814
816
|
/**
|
|
815
|
-
* Cancels access
|
|
817
|
+
* Cancels the access of an Express Connect circuit. After the cancellation, the Express Connect circuit enters the Canceled state.
|
|
816
818
|
*
|
|
817
819
|
* @remarks
|
|
818
|
-
* You can cancel access
|
|
820
|
+
* 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**.
|
|
819
821
|
*
|
|
820
822
|
* @param request - CancelPhysicalConnectionRequest
|
|
821
823
|
* @returns CancelPhysicalConnectionResponse
|
|
@@ -864,7 +866,7 @@ export default class Client extends OpenApi {
|
|
|
864
866
|
*/
|
|
865
867
|
checkCanAllocateVpcPrivateIpAddress(request: $_model.CheckCanAllocateVpcPrivateIpAddressRequest): Promise<$_model.CheckCanAllocateVpcPrivateIpAddressResponse>;
|
|
866
868
|
/**
|
|
867
|
-
* Calls the CheckVpnBgpEnabled operation to query whether the region
|
|
869
|
+
* Calls the CheckVpnBgpEnabled operation to query whether the region to which an IPsec-VPN connection belongs supports the BGP feature.
|
|
868
870
|
*
|
|
869
871
|
* @param request - CheckVpnBgpEnabledRequest
|
|
870
872
|
* @param runtime - runtime options for this request RuntimeOptions
|
|
@@ -872,14 +874,17 @@ export default class Client extends OpenApi {
|
|
|
872
874
|
*/
|
|
873
875
|
checkVpnBgpEnabledWithOptions(request: $_model.CheckVpnBgpEnabledRequest, runtime: $dara.RuntimeOptions): Promise<$_model.CheckVpnBgpEnabledResponse>;
|
|
874
876
|
/**
|
|
875
|
-
* Calls the CheckVpnBgpEnabled operation to query whether the region
|
|
877
|
+
* Calls the CheckVpnBgpEnabled operation to query whether the region to which an IPsec-VPN connection belongs supports the BGP feature.
|
|
876
878
|
*
|
|
877
879
|
* @param request - CheckVpnBgpEnabledRequest
|
|
878
880
|
* @returns CheckVpnBgpEnabledResponse
|
|
879
881
|
*/
|
|
880
882
|
checkVpnBgpEnabled(request: $_model.CheckVpnBgpEnabledRequest): Promise<$_model.CheckVpnBgpEnabledResponse>;
|
|
881
883
|
/**
|
|
882
|
-
*
|
|
884
|
+
* Completes the construction acceptance for an Express Connect circuit.
|
|
885
|
+
*
|
|
886
|
+
* @remarks
|
|
887
|
+
* 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**.
|
|
883
888
|
*
|
|
884
889
|
* @param request - CompletePhysicalConnectionLOARequest
|
|
885
890
|
* @param runtime - runtime options for this request RuntimeOptions
|
|
@@ -887,7 +892,10 @@ export default class Client extends OpenApi {
|
|
|
887
892
|
*/
|
|
888
893
|
completePhysicalConnectionLOAWithOptions(request: $_model.CompletePhysicalConnectionLOARequest, runtime: $dara.RuntimeOptions): Promise<$_model.CompletePhysicalConnectionLOAResponse>;
|
|
889
894
|
/**
|
|
890
|
-
*
|
|
895
|
+
* Completes the construction acceptance for an Express Connect circuit.
|
|
896
|
+
*
|
|
897
|
+
* @remarks
|
|
898
|
+
* 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**.
|
|
891
899
|
*
|
|
892
900
|
* @param request - CompletePhysicalConnectionLOARequest
|
|
893
901
|
* @returns CompletePhysicalConnectionLOAResponse
|
|
@@ -1279,7 +1287,7 @@ export default class Client extends OpenApi {
|
|
|
1279
1287
|
*
|
|
1280
1288
|
* @remarks
|
|
1281
1289
|
* You cannot create a failover test job in the following scenarios:
|
|
1282
|
-
* - A failover test job is already running in the current region
|
|
1290
|
+
* - 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.
|
|
1283
1291
|
* - The Express Connect circuit instance or shared Express Connect circuit instance has not been paid for or has an overdue payment.
|
|
1284
1292
|
* - The Express Connect circuit instance or shared Express Connect circuit instance is already in another running failover test job.
|
|
1285
1293
|
*
|
|
@@ -1298,7 +1306,7 @@ export default class Client extends OpenApi {
|
|
|
1298
1306
|
*
|
|
1299
1307
|
* @remarks
|
|
1300
1308
|
* You cannot create a failover test job in the following scenarios:
|
|
1301
|
-
* - A failover test job is already running in the current region
|
|
1309
|
+
* - 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.
|
|
1302
1310
|
* - The Express Connect circuit instance or shared Express Connect circuit instance has not been paid for or has an overdue payment.
|
|
1303
1311
|
* - The Express Connect circuit instance or shared Express Connect circuit instance is already in another running failover test job.
|
|
1304
1312
|
*
|
|
@@ -2135,7 +2143,7 @@ export default class Client extends OpenApi {
|
|
|
2135
2143
|
* Creates an SSL-VPN server.
|
|
2136
2144
|
*
|
|
2137
2145
|
* @remarks
|
|
2138
|
-
* - **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
|
|
2146
|
+
* - **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:
|
|
2139
2147
|
* - If the VPN gateway instance is in the **updating** state, the SSL-VPN server is being created.
|
|
2140
2148
|
* - If the VPN gateway instance is in the **active** state, the SSL-VPN server is created.
|
|
2141
2149
|
* - **CreateSslVpnServer** does not support concurrent creation of SSL-VPN servers under the same VPN gateway.
|
|
@@ -2152,7 +2160,7 @@ export default class Client extends OpenApi {
|
|
|
2152
2160
|
* Creates an SSL-VPN server.
|
|
2153
2161
|
*
|
|
2154
2162
|
* @remarks
|
|
2155
|
-
* - **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
|
|
2163
|
+
* - **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:
|
|
2156
2164
|
* - If the VPN gateway instance is in the **updating** state, the SSL-VPN server is being created.
|
|
2157
2165
|
* - If the VPN gateway instance is in the **active** state, the SSL-VPN server is created.
|
|
2158
2166
|
* - **CreateSslVpnServer** does not support concurrent creation of SSL-VPN servers under the same VPN gateway.
|
|
@@ -2245,18 +2253,18 @@ export default class Client extends OpenApi {
|
|
|
2245
2253
|
* Creates a vSwitch.
|
|
2246
2254
|
*
|
|
2247
2255
|
* @remarks
|
|
2248
|
-
*
|
|
2256
|
+
* When you call this operation to create a vSwitch, take note of the following items:
|
|
2249
2257
|
* - The number of vSwitches in each VPC cannot exceed 150.
|
|
2250
|
-
* - 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.
|
|
2258
|
+
* - 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.
|
|
2251
2259
|
* - 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).
|
|
2252
2260
|
* - A cloud service instance can belong to only one vSwitch.
|
|
2253
2261
|
* - vSwitches do not support multicast or broadcast.
|
|
2254
2262
|
* - After a vSwitch is created, you cannot modify its CIDR block.
|
|
2255
|
-
* - The **CreateVSwitch** operation is asynchronous. After you send a request, the system returns an instance ID
|
|
2256
|
-
* -
|
|
2257
|
-
* -
|
|
2263
|
+
* - 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:
|
|
2264
|
+
* - When the vSwitch is in the **Pending** state, the vSwitch is being configured.
|
|
2265
|
+
* - When the vSwitch is in the **Available** state, the vSwitch is available.
|
|
2258
2266
|
* - The **CreateVSwitch** operation does not support concurrent creation of vSwitches in the same VPC.
|
|
2259
|
-
* -
|
|
2267
|
+
* - 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.
|
|
2260
2268
|
*
|
|
2261
2269
|
* @param request - CreateVSwitchRequest
|
|
2262
2270
|
* @param runtime - runtime options for this request RuntimeOptions
|
|
@@ -2267,18 +2275,18 @@ export default class Client extends OpenApi {
|
|
|
2267
2275
|
* Creates a vSwitch.
|
|
2268
2276
|
*
|
|
2269
2277
|
* @remarks
|
|
2270
|
-
*
|
|
2278
|
+
* When you call this operation to create a vSwitch, take note of the following items:
|
|
2271
2279
|
* - The number of vSwitches in each VPC cannot exceed 150.
|
|
2272
|
-
* - 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.
|
|
2280
|
+
* - 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.
|
|
2273
2281
|
* - 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).
|
|
2274
2282
|
* - A cloud service instance can belong to only one vSwitch.
|
|
2275
2283
|
* - vSwitches do not support multicast or broadcast.
|
|
2276
2284
|
* - After a vSwitch is created, you cannot modify its CIDR block.
|
|
2277
|
-
* - The **CreateVSwitch** operation is asynchronous. After you send a request, the system returns an instance ID
|
|
2278
|
-
* -
|
|
2279
|
-
* -
|
|
2285
|
+
* - 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:
|
|
2286
|
+
* - When the vSwitch is in the **Pending** state, the vSwitch is being configured.
|
|
2287
|
+
* - When the vSwitch is in the **Available** state, the vSwitch is available.
|
|
2280
2288
|
* - The **CreateVSwitch** operation does not support concurrent creation of vSwitches in the same VPC.
|
|
2281
|
-
* -
|
|
2289
|
+
* - 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.
|
|
2282
2290
|
*
|
|
2283
2291
|
* @param request - CreateVSwitchRequest
|
|
2284
2292
|
* @returns CreateVSwitchResponse
|
|
@@ -2293,7 +2301,7 @@ export default class Client extends OpenApi {
|
|
|
2293
2301
|
* - A reserved CIDR block cannot contain the system reserved IP addresses of the vSwitch to which it belongs.
|
|
2294
2302
|
* - IPv4 CIDR block: The first and last three IP addresses of the vSwitch are system reserved IP addresses.
|
|
2295
2303
|
* - IPv6 CIDR block: The first and last nine IP addresses of the vSwitch are system reserved IP addresses.
|
|
2296
|
-
* - 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
|
|
2304
|
+
* - 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:
|
|
2297
2305
|
* - If the reserved CIDR block for a vSwitch is in the **Assigning** state, the reserved CIDR block for a vSwitch is being allocated.
|
|
2298
2306
|
* - If the reserved CIDR block for a vSwitch is in the **Assigned** state, the reserved CIDR block for a vSwitch has been allocated.
|
|
2299
2307
|
*
|
|
@@ -2311,7 +2319,7 @@ export default class Client extends OpenApi {
|
|
|
2311
2319
|
* - A reserved CIDR block cannot contain the system reserved IP addresses of the vSwitch to which it belongs.
|
|
2312
2320
|
* - IPv4 CIDR block: The first and last three IP addresses of the vSwitch are system reserved IP addresses.
|
|
2313
2321
|
* - IPv6 CIDR block: The first and last nine IP addresses of the vSwitch are system reserved IP addresses.
|
|
2314
|
-
* - 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
|
|
2322
|
+
* - 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:
|
|
2315
2323
|
* - If the reserved CIDR block for a vSwitch is in the **Assigning** state, the reserved CIDR block for a vSwitch is being allocated.
|
|
2316
2324
|
* - If the reserved CIDR block for a vSwitch is in the **Assigned** state, the reserved CIDR block for a vSwitch has been allocated.
|
|
2317
2325
|
*
|
|
@@ -2320,7 +2328,7 @@ export default class Client extends OpenApi {
|
|
|
2320
2328
|
*/
|
|
2321
2329
|
createVSwitchCidrReservation(request: $_model.CreateVSwitchCidrReservationRequest): Promise<$_model.CreateVSwitchCidrReservationResponse>;
|
|
2322
2330
|
/**
|
|
2323
|
-
* Creates a VBR failover group
|
|
2331
|
+
* Creates a VBR failover group.
|
|
2324
2332
|
*
|
|
2325
2333
|
* @param request - CreateVbrHaRequest
|
|
2326
2334
|
* @param runtime - runtime options for this request RuntimeOptions
|
|
@@ -2328,7 +2336,7 @@ export default class Client extends OpenApi {
|
|
|
2328
2336
|
*/
|
|
2329
2337
|
createVbrHaWithOptions(request: $_model.CreateVbrHaRequest, runtime: $dara.RuntimeOptions): Promise<$_model.CreateVbrHaResponse>;
|
|
2330
2338
|
/**
|
|
2331
|
-
* Creates a VBR failover group
|
|
2339
|
+
* Creates a VBR failover group.
|
|
2332
2340
|
*
|
|
2333
2341
|
* @param request - CreateVbrHaRequest
|
|
2334
2342
|
* @returns CreateVbrHaResponse
|
|
@@ -2340,11 +2348,11 @@ export default class Client extends OpenApi {
|
|
|
2340
2348
|
* @remarks
|
|
2341
2349
|
* - 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).
|
|
2342
2350
|
* - Adding a destination route with a destination CIDR block of 0.0.0.0/0 is not supported.
|
|
2343
|
-
* - Do not add a destination route
|
|
2351
|
+
* - 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.
|
|
2344
2352
|
* - **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:
|
|
2345
2353
|
* - If the IPsec-VPN connection is in the **updating** state, the destination route entry is being created.
|
|
2346
2354
|
* - If the IPsec-VPN connection is in the **attached** state, the destination route entry is created.
|
|
2347
|
-
* - **CreateVcoRouteEntry** does not support concurrent creation of destination route entries for the same IPsec-VPN connection.
|
|
2355
|
+
* - The **CreateVcoRouteEntry** operation does not support concurrent creation of destination route entries for the same IPsec-VPN connection.
|
|
2348
2356
|
*
|
|
2349
2357
|
* @param request - CreateVcoRouteEntryRequest
|
|
2350
2358
|
* @param runtime - runtime options for this request RuntimeOptions
|
|
@@ -2357,11 +2365,11 @@ export default class Client extends OpenApi {
|
|
|
2357
2365
|
* @remarks
|
|
2358
2366
|
* - 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).
|
|
2359
2367
|
* - Adding a destination route with a destination CIDR block of 0.0.0.0/0 is not supported.
|
|
2360
|
-
* - Do not add a destination route
|
|
2368
|
+
* - 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.
|
|
2361
2369
|
* - **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:
|
|
2362
2370
|
* - If the IPsec-VPN connection is in the **updating** state, the destination route entry is being created.
|
|
2363
2371
|
* - If the IPsec-VPN connection is in the **attached** state, the destination route entry is created.
|
|
2364
|
-
* - **CreateVcoRouteEntry** does not support concurrent creation of destination route entries for the same IPsec-VPN connection.
|
|
2372
|
+
* - The **CreateVcoRouteEntry** operation does not support concurrent creation of destination route entries for the same IPsec-VPN connection.
|
|
2365
2373
|
*
|
|
2366
2374
|
* @param request - CreateVcoRouteEntryRequest
|
|
2367
2375
|
* @returns CreateVcoRouteEntryResponse
|
|
@@ -2501,13 +2509,13 @@ export default class Client extends OpenApi {
|
|
|
2501
2509
|
*/
|
|
2502
2510
|
createVpcPrefixList(request: $_model.CreateVpcPrefixListRequest): Promise<$_model.CreateVpcPrefixListResponse>;
|
|
2503
2511
|
/**
|
|
2504
|
-
* Transforms the
|
|
2512
|
+
* Transforms the routing mode of shared Express Connect circuits from cross-account Virtual Border Router (VBR) push to cross-account shared port push.
|
|
2505
2513
|
*
|
|
2506
2514
|
* @remarks
|
|
2507
|
-
* By invoking the CreateVpconnFromVbr operation, a partner can transform the
|
|
2508
|
-
* Before you execute the transform:
|
|
2515
|
+
* 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.
|
|
2516
|
+
* Before you execute the transform procedure:
|
|
2509
2517
|
* 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).
|
|
2510
|
-
* After the transform is complete:
|
|
2518
|
+
* After the transform procedure is complete:
|
|
2511
2519
|
* 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.
|
|
2512
2520
|
* 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.
|
|
2513
2521
|
*
|
|
@@ -2517,13 +2525,13 @@ export default class Client extends OpenApi {
|
|
|
2517
2525
|
*/
|
|
2518
2526
|
createVpconnFromVbrWithOptions(request: $_model.CreateVpconnFromVbrRequest, runtime: $dara.RuntimeOptions): Promise<$_model.CreateVpconnFromVbrResponse>;
|
|
2519
2527
|
/**
|
|
2520
|
-
* Transforms the
|
|
2528
|
+
* Transforms the routing mode of shared Express Connect circuits from cross-account Virtual Border Router (VBR) push to cross-account shared port push.
|
|
2521
2529
|
*
|
|
2522
2530
|
* @remarks
|
|
2523
|
-
* By invoking the CreateVpconnFromVbr operation, a partner can transform the
|
|
2524
|
-
* Before you execute the transform:
|
|
2531
|
+
* 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.
|
|
2532
|
+
* Before you execute the transform procedure:
|
|
2525
2533
|
* 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).
|
|
2526
|
-
* After the transform is complete:
|
|
2534
|
+
* After the transform procedure is complete:
|
|
2527
2535
|
* 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.
|
|
2528
2536
|
* 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.
|
|
2529
2537
|
*
|
|
@@ -2532,16 +2540,11 @@ export default class Client extends OpenApi {
|
|
|
2532
2540
|
*/
|
|
2533
2541
|
createVpconnFromVbr(request: $_model.CreateVpconnFromVbrRequest): Promise<$_model.CreateVpconnFromVbrResponse>;
|
|
2534
2542
|
/**
|
|
2535
|
-
* Creates an IPsec-VPN connection
|
|
2543
|
+
* Creates an IPsec-VPN connection to be associated with a transit router instance by calling the CreateVpnAttachment operation.
|
|
2536
2544
|
*
|
|
2537
2545
|
* @remarks
|
|
2538
2546
|
* >Notice:
|
|
2539
|
-
*
|
|
2540
|
-
* - 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.
|
|
2541
|
-
* ### Before you begin
|
|
2542
|
-
* 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).
|
|
2543
|
-
*
|
|
2544
|
-
* 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.
|
|
2547
|
+
* ### Before you begin.
|
|
2545
2548
|
*
|
|
2546
2549
|
* @param request - CreateVpnAttachmentRequest
|
|
2547
2550
|
* @param runtime - runtime options for this request RuntimeOptions
|
|
@@ -2549,16 +2552,11 @@ export default class Client extends OpenApi {
|
|
|
2549
2552
|
*/
|
|
2550
2553
|
createVpnAttachmentWithOptions(request: $_model.CreateVpnAttachmentRequest, runtime: $dara.RuntimeOptions): Promise<$_model.CreateVpnAttachmentResponse>;
|
|
2551
2554
|
/**
|
|
2552
|
-
* Creates an IPsec-VPN connection
|
|
2555
|
+
* Creates an IPsec-VPN connection to be associated with a transit router instance by calling the CreateVpnAttachment operation.
|
|
2553
2556
|
*
|
|
2554
2557
|
* @remarks
|
|
2555
2558
|
* >Notice:
|
|
2556
|
-
*
|
|
2557
|
-
* - 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.
|
|
2558
|
-
* ### Before you begin
|
|
2559
|
-
* 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).
|
|
2560
|
-
*
|
|
2561
|
-
* 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.
|
|
2559
|
+
* ### Before you begin.
|
|
2562
2560
|
*
|
|
2563
2561
|
* @param request - CreateVpnAttachmentRequest
|
|
2564
2562
|
* @returns CreateVpnAttachmentResponse
|
|
@@ -2571,11 +2569,8 @@ export default class Client extends OpenApi {
|
|
|
2571
2569
|
* - 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:
|
|
2572
2570
|
* **ClientToken**, **Name**, **EffectImmediately**, **AutoConfigRoute**, **Tags** array, **TunnelOptionsSpecification** array, and **EnableTunnelsBgp**.
|
|
2573
2571
|
* 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).
|
|
2574
|
-
* - 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:
|
|
2575
2572
|
* **ClientToken**, **CustomerGatewayId**, **Name**, **EffectImmediately**, **IkeConfig**, **IpsecConfig**, **HealthCheckConfig**, **AutoConfigRoute**, **EnableDpd**, **EnableNatTraversal**, **BgpConfig**, **RemoteCaCertificate**, and **Tags** array.
|
|
2576
|
-
* - 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
|
|
2577
|
-
* - If the VPN gateway instance is in the **updating** state, the IPsec-VPN connection is being created.
|
|
2578
|
-
* - If the VPN gateway instance is in the **active** state, the IPsec-VPN connection is created.
|
|
2573
|
+
* - 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.
|
|
2579
2574
|
* - The **CreateVpnConnection** operation does not support concurrent creation of IPsec-VPN connections under the same VPN gateway.
|
|
2580
2575
|
*
|
|
2581
2576
|
* @param request - CreateVpnConnectionRequest
|
|
@@ -2590,11 +2585,8 @@ export default class Client extends OpenApi {
|
|
|
2590
2585
|
* - 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:
|
|
2591
2586
|
* **ClientToken**, **Name**, **EffectImmediately**, **AutoConfigRoute**, **Tags** array, **TunnelOptionsSpecification** array, and **EnableTunnelsBgp**.
|
|
2592
2587
|
* 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).
|
|
2593
|
-
* - 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:
|
|
2594
2588
|
* **ClientToken**, **CustomerGatewayId**, **Name**, **EffectImmediately**, **IkeConfig**, **IpsecConfig**, **HealthCheckConfig**, **AutoConfigRoute**, **EnableDpd**, **EnableNatTraversal**, **BgpConfig**, **RemoteCaCertificate**, and **Tags** array.
|
|
2595
|
-
* - 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
|
|
2596
|
-
* - If the VPN gateway instance is in the **updating** state, the IPsec-VPN connection is being created.
|
|
2597
|
-
* - If the VPN gateway instance is in the **active** state, the IPsec-VPN connection is created.
|
|
2589
|
+
* - 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.
|
|
2598
2590
|
* - The **CreateVpnConnection** operation does not support concurrent creation of IPsec-VPN connections under the same VPN gateway.
|
|
2599
2591
|
*
|
|
2600
2592
|
* @param request - CreateVpnConnectionRequest
|
|
@@ -2605,8 +2597,8 @@ export default class Client extends OpenApi {
|
|
|
2605
2597
|
* Creates a VPN gateway.
|
|
2606
2598
|
*
|
|
2607
2599
|
* @remarks
|
|
2608
|
-
* - 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).
|
|
2609
|
-
* - 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).
|
|
2600
|
+
* - 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).
|
|
2601
|
+
* - 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).
|
|
2610
2602
|
* - 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:
|
|
2611
2603
|
*
|
|
2612
2604
|
* - If the VPN gateway is in the **provisioning** state, the VPN gateway is being created.
|
|
@@ -2621,8 +2613,8 @@ export default class Client extends OpenApi {
|
|
|
2621
2613
|
* Creates a VPN gateway.
|
|
2622
2614
|
*
|
|
2623
2615
|
* @remarks
|
|
2624
|
-
* - 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).
|
|
2625
|
-
* - 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).
|
|
2616
|
+
* - 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).
|
|
2617
|
+
* - 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).
|
|
2626
2618
|
* - 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:
|
|
2627
2619
|
*
|
|
2628
2620
|
* - If the VPN gateway is in the **provisioning** state, the VPN gateway is being created.
|
|
@@ -2633,18 +2625,18 @@ export default class Client extends OpenApi {
|
|
|
2633
2625
|
*/
|
|
2634
2626
|
createVpnGateway(request: $_model.CreateVpnGatewayRequest): Promise<$_model.CreateVpnGatewayResponse>;
|
|
2635
2627
|
/**
|
|
2636
|
-
* Creates a policy-based route
|
|
2628
|
+
* Creates a VPN policy-based route by calling the CreateVpnPbrRouteEntry operation.
|
|
2637
2629
|
*
|
|
2638
2630
|
* @remarks
|
|
2639
2631
|
* ### Before you begin
|
|
2640
|
-
* - Before
|
|
2641
|
-
* - Before
|
|
2632
|
+
* - 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).
|
|
2633
|
+
* - 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).
|
|
2642
2634
|
* ### Limits
|
|
2643
|
-
* -
|
|
2644
|
-
* - Do not add
|
|
2645
|
-
* - The **CreateVpnPbrRouteEntry** operation is asynchronous. After you
|
|
2635
|
+
* - Policy-based routes whose destination CIDR block is 0.0.0.0/0 are not supported.
|
|
2636
|
+
* - 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.
|
|
2637
|
+
* - 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:
|
|
2646
2638
|
* - If the VPN gateway instance is in the **updating** state, the policy-based route is being created.
|
|
2647
|
-
* - If the VPN gateway instance is in the **active** state, the policy-based route
|
|
2639
|
+
* - If the VPN gateway instance is in the **active** state, the policy-based route is created.
|
|
2648
2640
|
* - The **CreateVpnPbrRouteEntry** operation does not support concurrent creation of policy-based routes for the same VPN gateway instance.
|
|
2649
2641
|
*
|
|
2650
2642
|
* @param request - CreateVpnPbrRouteEntryRequest
|
|
@@ -2653,18 +2645,18 @@ export default class Client extends OpenApi {
|
|
|
2653
2645
|
*/
|
|
2654
2646
|
createVpnPbrRouteEntryWithOptions(request: $_model.CreateVpnPbrRouteEntryRequest, runtime: $dara.RuntimeOptions): Promise<$_model.CreateVpnPbrRouteEntryResponse>;
|
|
2655
2647
|
/**
|
|
2656
|
-
* Creates a policy-based route
|
|
2648
|
+
* Creates a VPN policy-based route by calling the CreateVpnPbrRouteEntry operation.
|
|
2657
2649
|
*
|
|
2658
2650
|
* @remarks
|
|
2659
2651
|
* ### Before you begin
|
|
2660
|
-
* - Before
|
|
2661
|
-
* - Before
|
|
2652
|
+
* - 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).
|
|
2653
|
+
* - 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).
|
|
2662
2654
|
* ### Limits
|
|
2663
|
-
* -
|
|
2664
|
-
* - Do not add
|
|
2665
|
-
* - The **CreateVpnPbrRouteEntry** operation is asynchronous. After you
|
|
2655
|
+
* - Policy-based routes whose destination CIDR block is 0.0.0.0/0 are not supported.
|
|
2656
|
+
* - 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.
|
|
2657
|
+
* - 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:
|
|
2666
2658
|
* - If the VPN gateway instance is in the **updating** state, the policy-based route is being created.
|
|
2667
|
-
* - If the VPN gateway instance is in the **active** state, the policy-based route
|
|
2659
|
+
* - If the VPN gateway instance is in the **active** state, the policy-based route is created.
|
|
2668
2660
|
* - The **CreateVpnPbrRouteEntry** operation does not support concurrent creation of policy-based routes for the same VPN gateway instance.
|
|
2669
2661
|
*
|
|
2670
2662
|
* @param request - CreateVpnPbrRouteEntryRequest
|
|
@@ -2753,7 +2745,7 @@ export default class Client extends OpenApi {
|
|
|
2753
2745
|
*/
|
|
2754
2746
|
deactiveFlowLog(request: $_model.DeactiveFlowLogRequest): Promise<$_model.DeactiveFlowLogResponse>;
|
|
2755
2747
|
/**
|
|
2756
|
-
* Deletes a specified
|
|
2748
|
+
* Deletes a specified BGP group.
|
|
2757
2749
|
*
|
|
2758
2750
|
* @param request - DeleteBgpGroupRequest
|
|
2759
2751
|
* @param runtime - runtime options for this request RuntimeOptions
|
|
@@ -2761,7 +2753,7 @@ export default class Client extends OpenApi {
|
|
|
2761
2753
|
*/
|
|
2762
2754
|
deleteBgpGroupWithOptions(request: $_model.DeleteBgpGroupRequest, runtime: $dara.RuntimeOptions): Promise<$_model.DeleteBgpGroupResponse>;
|
|
2763
2755
|
/**
|
|
2764
|
-
* Deletes a specified
|
|
2756
|
+
* Deletes a specified BGP group.
|
|
2765
2757
|
*
|
|
2766
2758
|
* @param request - DeleteBgpGroupRequest
|
|
2767
2759
|
* @returns DeleteBgpGroupResponse
|
|
@@ -2954,10 +2946,10 @@ export default class Client extends OpenApi {
|
|
|
2954
2946
|
*/
|
|
2955
2947
|
deleteExpressConnectTrafficQosRule(request: $_model.DeleteExpressConnectTrafficQosRuleRequest): Promise<$_model.DeleteExpressConnectTrafficQosRuleResponse>;
|
|
2956
2948
|
/**
|
|
2957
|
-
* Deletes an Express Connect failover test job.
|
|
2949
|
+
* Deletes an Express Connect failover test job by calling the DeleteFailoverTestJob operation.
|
|
2958
2950
|
*
|
|
2959
2951
|
* @remarks
|
|
2960
|
-
* Only failover test jobs in the **Pending** or **Completed** state can be deleted.
|
|
2952
|
+
* 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**.
|
|
2961
2953
|
*
|
|
2962
2954
|
* @param request - DeleteFailoverTestJobRequest
|
|
2963
2955
|
* @param runtime - runtime options for this request RuntimeOptions
|
|
@@ -2965,10 +2957,10 @@ export default class Client extends OpenApi {
|
|
|
2965
2957
|
*/
|
|
2966
2958
|
deleteFailoverTestJobWithOptions(request: $_model.DeleteFailoverTestJobRequest, runtime: $dara.RuntimeOptions): Promise<$_model.DeleteFailoverTestJobResponse>;
|
|
2967
2959
|
/**
|
|
2968
|
-
* Deletes an Express Connect failover test job.
|
|
2960
|
+
* Deletes an Express Connect failover test job by calling the DeleteFailoverTestJob operation.
|
|
2969
2961
|
*
|
|
2970
2962
|
* @remarks
|
|
2971
|
-
* Only failover test jobs in the **Pending** or **Completed** state can be deleted.
|
|
2963
|
+
* 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**.
|
|
2972
2964
|
*
|
|
2973
2965
|
* @param request - DeleteFailoverTestJobRequest
|
|
2974
2966
|
* @returns DeleteFailoverTestJobResponse
|
|
@@ -3172,7 +3164,7 @@ export default class Client extends OpenApi {
|
|
|
3172
3164
|
* Deletes an IPsec server.
|
|
3173
3165
|
*
|
|
3174
3166
|
* @remarks
|
|
3175
|
-
* - **DeleteIpsecServer** is an asynchronous operation. After you send a request, the system returns a request ID
|
|
3167
|
+
* - **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:
|
|
3176
3168
|
* - If the VPN gateway instance is in the **updating** state, the IPsec server is being deleted.
|
|
3177
3169
|
* - If the VPN gateway instance is in the **active** state, the IPsec server is deleted.
|
|
3178
3170
|
* - **DeleteIpsecServer** does not support concurrent deletion of IPsec servers under the same VPN gateway.
|
|
@@ -3186,7 +3178,7 @@ export default class Client extends OpenApi {
|
|
|
3186
3178
|
* Deletes an IPsec server.
|
|
3187
3179
|
*
|
|
3188
3180
|
* @remarks
|
|
3189
|
-
* - **DeleteIpsecServer** is an asynchronous operation. After you send a request, the system returns a request ID
|
|
3181
|
+
* - **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:
|
|
3190
3182
|
* - If the VPN gateway instance is in the **updating** state, the IPsec server is being deleted.
|
|
3191
3183
|
* - If the VPN gateway instance is in the **active** state, the IPsec server is deleted.
|
|
3192
3184
|
* - **DeleteIpsecServer** does not support concurrent deletion of IPsec servers under the same VPN gateway.
|
|
@@ -3305,12 +3297,12 @@ export default class Client extends OpenApi {
|
|
|
3305
3297
|
* Deletes a specified Internet NAT gateway.
|
|
3306
3298
|
*
|
|
3307
3299
|
* @remarks
|
|
3308
|
-
* *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://
|
|
3300
|
+
* *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:
|
|
3309
3301
|
*
|
|
3310
3302
|
* - If the NAT gateway is in the **Deleting** state, the NAT gateway is being deleted. In this state, you can only perform query operations.
|
|
3311
3303
|
* - If the NAT gateway cannot be found, the NAT gateway is deleted.
|
|
3312
3304
|
*
|
|
3313
|
-
* >
|
|
3305
|
+
* > Deleting a NAT gateway is irreversible. Proceed with caution.
|
|
3314
3306
|
*
|
|
3315
3307
|
* @param request - DeleteNatGatewayRequest
|
|
3316
3308
|
* @param runtime - runtime options for this request RuntimeOptions
|
|
@@ -3321,12 +3313,12 @@ export default class Client extends OpenApi {
|
|
|
3321
3313
|
* Deletes a specified Internet NAT gateway.
|
|
3322
3314
|
*
|
|
3323
3315
|
* @remarks
|
|
3324
|
-
* *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://
|
|
3316
|
+
* *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:
|
|
3325
3317
|
*
|
|
3326
3318
|
* - If the NAT gateway is in the **Deleting** state, the NAT gateway is being deleted. In this state, you can only perform query operations.
|
|
3327
3319
|
* - If the NAT gateway cannot be found, the NAT gateway is deleted.
|
|
3328
3320
|
*
|
|
3329
|
-
* >
|
|
3321
|
+
* > Deleting a NAT gateway is irreversible. Proceed with caution.
|
|
3330
3322
|
*
|
|
3331
3323
|
* @param request - DeleteNatGatewayRequest
|
|
3332
3324
|
* @returns DeleteNatGatewayResponse
|
|
@@ -3687,10 +3679,10 @@ export default class Client extends OpenApi {
|
|
|
3687
3679
|
* 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.
|
|
3688
3680
|
*
|
|
3689
3681
|
* @remarks
|
|
3690
|
-
* - **DeleteSslVpnServer** is
|
|
3682
|
+
* - 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:
|
|
3691
3683
|
* - If the VPN gateway instance is in the **updating** state, the SSL server is being deleted.
|
|
3692
3684
|
* - If the VPN gateway instance is in the **active** state, the SSL server is deleted.
|
|
3693
|
-
* - **DeleteSslVpnServer** does not support concurrent deletion of SSL
|
|
3685
|
+
* - The **DeleteSslVpnServer** operation does not support concurrent deletion of SSL servers under the same VPN gateway.
|
|
3694
3686
|
*
|
|
3695
3687
|
* @param request - DeleteSslVpnServerRequest
|
|
3696
3688
|
* @param runtime - runtime options for this request RuntimeOptions
|
|
@@ -3701,10 +3693,10 @@ export default class Client extends OpenApi {
|
|
|
3701
3693
|
* 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.
|
|
3702
3694
|
*
|
|
3703
3695
|
* @remarks
|
|
3704
|
-
* - **DeleteSslVpnServer** is
|
|
3696
|
+
* - 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:
|
|
3705
3697
|
* - If the VPN gateway instance is in the **updating** state, the SSL server is being deleted.
|
|
3706
3698
|
* - If the VPN gateway instance is in the **active** state, the SSL server is deleted.
|
|
3707
|
-
* - **DeleteSslVpnServer** does not support concurrent deletion of SSL
|
|
3699
|
+
* - The **DeleteSslVpnServer** operation does not support concurrent deletion of SSL servers under the same VPN gateway.
|
|
3708
3700
|
*
|
|
3709
3701
|
* @param request - DeleteSslVpnServerRequest
|
|
3710
3702
|
* @returns DeleteSslVpnServerResponse
|
|
@@ -3854,7 +3846,7 @@ export default class Client extends OpenApi {
|
|
|
3854
3846
|
*/
|
|
3855
3847
|
deleteVSwitchCidrReservation(request: $_model.DeleteVSwitchCidrReservationRequest): Promise<$_model.DeleteVSwitchCidrReservationResponse>;
|
|
3856
3848
|
/**
|
|
3857
|
-
*
|
|
3849
|
+
* Calls DeleteVbrHa to delete a VBR failover group.
|
|
3858
3850
|
*
|
|
3859
3851
|
* @param request - DeleteVbrHaRequest
|
|
3860
3852
|
* @param runtime - runtime options for this request RuntimeOptions
|
|
@@ -3862,7 +3854,7 @@ export default class Client extends OpenApi {
|
|
|
3862
3854
|
*/
|
|
3863
3855
|
deleteVbrHaWithOptions(request: $_model.DeleteVbrHaRequest, runtime: $dara.RuntimeOptions): Promise<$_model.DeleteVbrHaResponse>;
|
|
3864
3856
|
/**
|
|
3865
|
-
*
|
|
3857
|
+
* Calls DeleteVbrHa to delete a VBR failover group.
|
|
3866
3858
|
*
|
|
3867
3859
|
* @param request - DeleteVbrHaRequest
|
|
3868
3860
|
* @returns DeleteVbrHaResponse
|
|
@@ -3872,7 +3864,7 @@ export default class Client extends OpenApi {
|
|
|
3872
3864
|
* Deletes a destination route entry from an IPsec-VPN connection.
|
|
3873
3865
|
*
|
|
3874
3866
|
* @remarks
|
|
3875
|
-
* - **DeleteVcoRouteEntry** is an asynchronous operation. After you send a request, the system returns a request ID, but the destination route entry
|
|
3867
|
+
* - **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:
|
|
3876
3868
|
* - If the IPsec-VPN connection is in the **updating** state, the destination route entry is being deleted.
|
|
3877
3869
|
* - If the IPsec-VPN connection is in the **attached** state, the destination route entry is deleted.
|
|
3878
3870
|
* - **DeleteVcoRouteEntry** does not support concurrent deletion of destination route entries for the same IPsec-VPN connection.
|
|
@@ -3886,7 +3878,7 @@ export default class Client extends OpenApi {
|
|
|
3886
3878
|
* Deletes a destination route entry from an IPsec-VPN connection.
|
|
3887
3879
|
*
|
|
3888
3880
|
* @remarks
|
|
3889
|
-
* - **DeleteVcoRouteEntry** is an asynchronous operation. After you send a request, the system returns a request ID, but the destination route entry
|
|
3881
|
+
* - **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:
|
|
3890
3882
|
* - If the IPsec-VPN connection is in the **updating** state, the destination route entry is being deleted.
|
|
3891
3883
|
* - If the IPsec-VPN connection is in the **attached** state, the destination route entry is deleted.
|
|
3892
3884
|
* - **DeleteVcoRouteEntry** does not support concurrent deletion of destination route entries for the same IPsec-VPN connection.
|
|
@@ -3994,11 +3986,11 @@ export default class Client extends OpenApi {
|
|
|
3994
3986
|
*/
|
|
3995
3987
|
deleteVpcPrefixList(request: $_model.DeleteVpcPrefixListRequest): Promise<$_model.DeleteVpcPrefixListResponse>;
|
|
3996
3988
|
/**
|
|
3997
|
-
* Deletes an IPsec-VPN connection
|
|
3989
|
+
* Deletes an IPsec-VPN connection.
|
|
3998
3990
|
*
|
|
3999
3991
|
* @remarks
|
|
4000
|
-
* - If the IPsec-VPN connection is
|
|
4001
|
-
* - If the IPsec-VPN connection is not
|
|
3992
|
+
* - 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).
|
|
3993
|
+
* - If the IPsec-VPN connection is not bindded to any resource, you can call the `DeleteVpnAttachment` operation to directly delete the IPsec-VPN connection.
|
|
4002
3994
|
*
|
|
4003
3995
|
* @param request - DeleteVpnAttachmentRequest
|
|
4004
3996
|
* @param runtime - runtime options for this request RuntimeOptions
|
|
@@ -4006,11 +3998,11 @@ export default class Client extends OpenApi {
|
|
|
4006
3998
|
*/
|
|
4007
3999
|
deleteVpnAttachmentWithOptions(request: $_model.DeleteVpnAttachmentRequest, runtime: $dara.RuntimeOptions): Promise<$_model.DeleteVpnAttachmentResponse>;
|
|
4008
4000
|
/**
|
|
4009
|
-
* Deletes an IPsec-VPN connection
|
|
4001
|
+
* Deletes an IPsec-VPN connection.
|
|
4010
4002
|
*
|
|
4011
4003
|
* @remarks
|
|
4012
|
-
* - If the IPsec-VPN connection is
|
|
4013
|
-
* - If the IPsec-VPN connection is not
|
|
4004
|
+
* - 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).
|
|
4005
|
+
* - If the IPsec-VPN connection is not bindded to any resource, you can call the `DeleteVpnAttachment` operation to directly delete the IPsec-VPN connection.
|
|
4014
4006
|
*
|
|
4015
4007
|
* @param request - DeleteVpnAttachmentRequest
|
|
4016
4008
|
* @returns DeleteVpnAttachmentResponse
|
|
@@ -4020,7 +4012,7 @@ export default class Client extends OpenApi {
|
|
|
4020
4012
|
* Deletes a specified IPsec-VPN connection.
|
|
4021
4013
|
*
|
|
4022
4014
|
* @remarks
|
|
4023
|
-
* - **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
|
|
4015
|
+
* - **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:
|
|
4024
4016
|
* - If the VPN gateway instance is in the **updating** state, the IPsec-VPN connection is being deleted.
|
|
4025
4017
|
* - If the VPN gateway instance is in the **active** state, the IPsec-VPN connection is deleted.
|
|
4026
4018
|
* - **DeleteVpnConnection** does not support concurrent deletion of IPsec-VPN connections under the same VPN gateway.
|
|
@@ -4035,7 +4027,7 @@ export default class Client extends OpenApi {
|
|
|
4035
4027
|
* Deletes a specified IPsec-VPN connection.
|
|
4036
4028
|
*
|
|
4037
4029
|
* @remarks
|
|
4038
|
-
* - **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
|
|
4030
|
+
* - **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:
|
|
4039
4031
|
* - If the VPN gateway instance is in the **updating** state, the IPsec-VPN connection is being deleted.
|
|
4040
4032
|
* - If the VPN gateway instance is in the **active** state, the IPsec-VPN connection is deleted.
|
|
4041
4033
|
* - **DeleteVpnConnection** does not support concurrent deletion of IPsec-VPN connections under the same VPN gateway.
|
|
@@ -4049,7 +4041,7 @@ export default class Client extends OpenApi {
|
|
|
4049
4041
|
* Deletes a specified VPN gateway.
|
|
4050
4042
|
*
|
|
4051
4043
|
* @remarks
|
|
4052
|
-
* > You cannot delete a VPN gateway that has
|
|
4044
|
+
* > You cannot delete a VPN gateway that has IPsec-VPN connections.
|
|
4053
4045
|
*
|
|
4054
4046
|
* @param request - DeleteVpnGatewayRequest
|
|
4055
4047
|
* @param runtime - runtime options for this request RuntimeOptions
|
|
@@ -4060,7 +4052,7 @@ export default class Client extends OpenApi {
|
|
|
4060
4052
|
* Deletes a specified VPN gateway.
|
|
4061
4053
|
*
|
|
4062
4054
|
* @remarks
|
|
4063
|
-
* > You cannot delete a VPN gateway that has
|
|
4055
|
+
* > You cannot delete a VPN gateway that has IPsec-VPN connections.
|
|
4064
4056
|
*
|
|
4065
4057
|
* @param request - DeleteVpnGatewayRequest
|
|
4066
4058
|
* @returns DeleteVpnGatewayResponse
|
|
@@ -4097,7 +4089,7 @@ export default class Client extends OpenApi {
|
|
|
4097
4089
|
* Deletes a VPN destination route by calling the DeleteVpnRouteEntry operation.
|
|
4098
4090
|
*
|
|
4099
4091
|
* @remarks
|
|
4100
|
-
* - **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:
|
|
4092
|
+
* - **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:
|
|
4101
4093
|
* - If the VPN gateway instance is in the **updating** state, the VPN destination route is being deleted.
|
|
4102
4094
|
* - If the VPN gateway instance is in the **active** state, the VPN destination route is deleted.
|
|
4103
4095
|
* - **DeleteVpnRouteEntry** does not support concurrent deletion of VPN destination routes for the same VPN gateway.
|
|
@@ -4111,7 +4103,7 @@ export default class Client extends OpenApi {
|
|
|
4111
4103
|
* Deletes a VPN destination route by calling the DeleteVpnRouteEntry operation.
|
|
4112
4104
|
*
|
|
4113
4105
|
* @remarks
|
|
4114
|
-
* - **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:
|
|
4106
|
+
* - **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:
|
|
4115
4107
|
* - If the VPN gateway instance is in the **updating** state, the VPN destination route is being deleted.
|
|
4116
4108
|
* - If the VPN gateway instance is in the **active** state, the VPN destination route is deleted.
|
|
4117
4109
|
* - **DeleteVpnRouteEntry** does not support concurrent deletion of VPN destination routes for the same VPN gateway.
|
|
@@ -4279,10 +4271,10 @@ export default class Client extends OpenApi {
|
|
|
4279
4271
|
*/
|
|
4280
4272
|
describeEcGrantRelation(request: $_model.DescribeEcGrantRelationRequest): Promise<$_model.DescribeEcGrantRelationResponse>;
|
|
4281
4273
|
/**
|
|
4282
|
-
* Queries
|
|
4274
|
+
* Queries elastic IP addresses (EIPs) created in a specified region.
|
|
4283
4275
|
*
|
|
4284
4276
|
* @remarks
|
|
4285
|
-
*
|
|
4277
|
+
* 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.
|
|
4286
4278
|
*
|
|
4287
4279
|
* @param request - DescribeEipAddressesRequest
|
|
4288
4280
|
* @param runtime - runtime options for this request RuntimeOptions
|
|
@@ -4290,10 +4282,10 @@ export default class Client extends OpenApi {
|
|
|
4290
4282
|
*/
|
|
4291
4283
|
describeEipAddressesWithOptions(request: $_model.DescribeEipAddressesRequest, runtime: $dara.RuntimeOptions): Promise<$_model.DescribeEipAddressesResponse>;
|
|
4292
4284
|
/**
|
|
4293
|
-
* Queries
|
|
4285
|
+
* Queries elastic IP addresses (EIPs) created in a specified region.
|
|
4294
4286
|
*
|
|
4295
4287
|
* @remarks
|
|
4296
|
-
*
|
|
4288
|
+
* 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.
|
|
4297
4289
|
*
|
|
4298
4290
|
* @param request - DescribeEipAddressesRequest
|
|
4299
4291
|
* @returns DescribeEipAddressesResponse
|
|
@@ -4374,6 +4366,9 @@ export default class Client extends OpenApi {
|
|
|
4374
4366
|
/**
|
|
4375
4367
|
* Queries Express Connect QoS queues.
|
|
4376
4368
|
*
|
|
4369
|
+
* @remarks
|
|
4370
|
+
* Before you call this operation, call CreateExpressConnectTrafficQos to create a QoS policy and obtain the **QosId**.
|
|
4371
|
+
*
|
|
4377
4372
|
* @param request - DescribeExpressConnectTrafficQosQueueRequest
|
|
4378
4373
|
* @param runtime - runtime options for this request RuntimeOptions
|
|
4379
4374
|
* @returns DescribeExpressConnectTrafficQosQueueResponse
|
|
@@ -4382,6 +4377,9 @@ export default class Client extends OpenApi {
|
|
|
4382
4377
|
/**
|
|
4383
4378
|
* Queries Express Connect QoS queues.
|
|
4384
4379
|
*
|
|
4380
|
+
* @remarks
|
|
4381
|
+
* Before you call this operation, call CreateExpressConnectTrafficQos to create a QoS policy and obtain the **QosId**.
|
|
4382
|
+
*
|
|
4385
4383
|
* @param request - DescribeExpressConnectTrafficQosQueueRequest
|
|
4386
4384
|
* @returns DescribeExpressConnectTrafficQosQueueResponse
|
|
4387
4385
|
*/
|
|
@@ -4402,7 +4400,7 @@ export default class Client extends OpenApi {
|
|
|
4402
4400
|
*/
|
|
4403
4401
|
describeExpressConnectTrafficQosRule(request: $_model.DescribeExpressConnectTrafficQosRuleRequest): Promise<$_model.DescribeExpressConnectTrafficQosRuleResponse>;
|
|
4404
4402
|
/**
|
|
4405
|
-
* Queries the details of an Express Connect failover test job
|
|
4403
|
+
* Queries the details of an Express Connect failover test job.
|
|
4406
4404
|
*
|
|
4407
4405
|
* @param request - DescribeFailoverTestJobRequest
|
|
4408
4406
|
* @param runtime - runtime options for this request RuntimeOptions
|
|
@@ -4410,14 +4408,14 @@ export default class Client extends OpenApi {
|
|
|
4410
4408
|
*/
|
|
4411
4409
|
describeFailoverTestJobWithOptions(request: $_model.DescribeFailoverTestJobRequest, runtime: $dara.RuntimeOptions): Promise<$_model.DescribeFailoverTestJobResponse>;
|
|
4412
4410
|
/**
|
|
4413
|
-
* Queries the details of an Express Connect failover test job
|
|
4411
|
+
* Queries the details of an Express Connect failover test job.
|
|
4414
4412
|
*
|
|
4415
4413
|
* @param request - DescribeFailoverTestJobRequest
|
|
4416
4414
|
* @returns DescribeFailoverTestJobResponse
|
|
4417
4415
|
*/
|
|
4418
4416
|
describeFailoverTestJob(request: $_model.DescribeFailoverTestJobRequest): Promise<$_model.DescribeFailoverTestJobResponse>;
|
|
4419
4417
|
/**
|
|
4420
|
-
* Queries failover test jobs
|
|
4418
|
+
* Queries Express Connect failover test jobs in batches.
|
|
4421
4419
|
*
|
|
4422
4420
|
* @param request - DescribeFailoverTestJobsRequest
|
|
4423
4421
|
* @param runtime - runtime options for this request RuntimeOptions
|
|
@@ -4425,7 +4423,7 @@ export default class Client extends OpenApi {
|
|
|
4425
4423
|
*/
|
|
4426
4424
|
describeFailoverTestJobsWithOptions(request: $_model.DescribeFailoverTestJobsRequest, runtime: $dara.RuntimeOptions): Promise<$_model.DescribeFailoverTestJobsResponse>;
|
|
4427
4425
|
/**
|
|
4428
|
-
* Queries failover test jobs
|
|
4426
|
+
* Queries Express Connect failover test jobs in batches.
|
|
4429
4427
|
*
|
|
4430
4428
|
* @param request - DescribeFailoverTestJobsRequest
|
|
4431
4429
|
* @returns DescribeFailoverTestJobsResponse
|
|
@@ -4753,7 +4751,7 @@ export default class Client extends OpenApi {
|
|
|
4753
4751
|
* Queries information about Express Connect circuits in a specified region.
|
|
4754
4752
|
*
|
|
4755
4753
|
* @remarks
|
|
4756
|
-
* 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 filter options
|
|
4754
|
+
* 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.
|
|
4757
4755
|
*
|
|
4758
4756
|
* @param request - DescribePhysicalConnectionsRequest
|
|
4759
4757
|
* @param runtime - runtime options for this request RuntimeOptions
|
|
@@ -4764,7 +4762,7 @@ export default class Client extends OpenApi {
|
|
|
4764
4762
|
* Queries information about Express Connect circuits in a specified region.
|
|
4765
4763
|
*
|
|
4766
4764
|
* @remarks
|
|
4767
|
-
* 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 filter options
|
|
4765
|
+
* 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.
|
|
4768
4766
|
*
|
|
4769
4767
|
* @param request - DescribePhysicalConnectionsRequest
|
|
4770
4768
|
* @returns DescribePhysicalConnectionsResponse
|
|
@@ -5011,7 +5009,7 @@ export default class Client extends OpenApi {
|
|
|
5011
5009
|
*/
|
|
5012
5010
|
describeTagKeys(request: $_model.DescribeTagKeysRequest): Promise<$_model.DescribeTagKeysResponse>;
|
|
5013
5011
|
/**
|
|
5014
|
-
*
|
|
5012
|
+
* Queries the tag list of Express Connect resources by calling the DescribeTagKeysForExpressConnect operation.
|
|
5015
5013
|
*
|
|
5016
5014
|
* @param request - DescribeTagKeysForExpressConnectRequest
|
|
5017
5015
|
* @param runtime - runtime options for this request RuntimeOptions
|
|
@@ -5019,7 +5017,7 @@ export default class Client extends OpenApi {
|
|
|
5019
5017
|
*/
|
|
5020
5018
|
describeTagKeysForExpressConnectWithOptions(request: $_model.DescribeTagKeysForExpressConnectRequest, runtime: $dara.RuntimeOptions): Promise<$_model.DescribeTagKeysForExpressConnectResponse>;
|
|
5021
5019
|
/**
|
|
5022
|
-
*
|
|
5020
|
+
* Queries the tag list of Express Connect resources by calling the DescribeTagKeysForExpressConnect operation.
|
|
5023
5021
|
*
|
|
5024
5022
|
* @param request - DescribeTagKeysForExpressConnectRequest
|
|
5025
5023
|
* @returns DescribeTagKeysForExpressConnectResponse
|
|
@@ -5085,6 +5083,9 @@ export default class Client extends OpenApi {
|
|
|
5085
5083
|
/**
|
|
5086
5084
|
* Queries networkable information. Internal networking is performed by vSwitch.
|
|
5087
5085
|
*
|
|
5086
|
+
* @remarks
|
|
5087
|
+
* 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.
|
|
5088
|
+
*
|
|
5088
5089
|
* @param request - DescribeVSwitchesRequest
|
|
5089
5090
|
* @param runtime - runtime options for this request RuntimeOptions
|
|
5090
5091
|
* @returns DescribeVSwitchesResponse
|
|
@@ -5093,6 +5094,9 @@ export default class Client extends OpenApi {
|
|
|
5093
5094
|
/**
|
|
5094
5095
|
* Queries networkable information. Internal networking is performed by vSwitch.
|
|
5095
5096
|
*
|
|
5097
|
+
* @remarks
|
|
5098
|
+
* 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.
|
|
5099
|
+
*
|
|
5096
5100
|
* @param request - DescribeVSwitchesRequest
|
|
5097
5101
|
* @returns DescribeVSwitchesResponse
|
|
5098
5102
|
*/
|
|
@@ -5128,7 +5132,7 @@ export default class Client extends OpenApi {
|
|
|
5128
5132
|
*/
|
|
5129
5133
|
describeVcoRouteEntries(request: $_model.DescribeVcoRouteEntriesRequest): Promise<$_model.DescribeVcoRouteEntriesResponse>;
|
|
5130
5134
|
/**
|
|
5131
|
-
* Queries
|
|
5135
|
+
* Queries Virtual Border Routers (VBRs) that are created.
|
|
5132
5136
|
*
|
|
5133
5137
|
* @param request - DescribeVirtualBorderRoutersRequest
|
|
5134
5138
|
* @param runtime - runtime options for this request RuntimeOptions
|
|
@@ -5136,7 +5140,7 @@ export default class Client extends OpenApi {
|
|
|
5136
5140
|
*/
|
|
5137
5141
|
describeVirtualBorderRoutersWithOptions(request: $_model.DescribeVirtualBorderRoutersRequest, runtime: $dara.RuntimeOptions): Promise<$_model.DescribeVirtualBorderRoutersResponse>;
|
|
5138
5142
|
/**
|
|
5139
|
-
* Queries
|
|
5143
|
+
* Queries Virtual Border Routers (VBRs) that are created.
|
|
5140
5144
|
*
|
|
5141
5145
|
* @param request - DescribeVirtualBorderRoutersRequest
|
|
5142
5146
|
* @returns DescribeVirtualBorderRoutersResponse
|
|
@@ -5190,6 +5194,9 @@ export default class Client extends OpenApi {
|
|
|
5190
5194
|
/**
|
|
5191
5195
|
* Queries created VPCs.
|
|
5192
5196
|
*
|
|
5197
|
+
* @remarks
|
|
5198
|
+
* The **DescribeVpcs** operation may return the **Throttling.DeepPageSkip** error code during frequent deep paging operations. Reduce the query frequency or use sequential paging.
|
|
5199
|
+
*
|
|
5193
5200
|
* @param request - DescribeVpcsRequest
|
|
5194
5201
|
* @param runtime - runtime options for this request RuntimeOptions
|
|
5195
5202
|
* @returns DescribeVpcsResponse
|
|
@@ -5198,6 +5205,9 @@ export default class Client extends OpenApi {
|
|
|
5198
5205
|
/**
|
|
5199
5206
|
* Queries created VPCs.
|
|
5200
5207
|
*
|
|
5208
|
+
* @remarks
|
|
5209
|
+
* The **DescribeVpcs** operation may return the **Throttling.DeepPageSkip** error code during frequent deep paging operations. Reduce the query frequency or use sequential paging.
|
|
5210
|
+
*
|
|
5201
5211
|
* @param request - DescribeVpcsRequest
|
|
5202
5212
|
* @returns DescribeVpcsResponse
|
|
5203
5213
|
*/
|
|
@@ -5353,7 +5363,7 @@ export default class Client extends OpenApi {
|
|
|
5353
5363
|
*/
|
|
5354
5364
|
describeVpnRouteEntries(request: $_model.DescribeVpnRouteEntriesRequest): Promise<$_model.DescribeVpnRouteEntriesResponse>;
|
|
5355
5365
|
/**
|
|
5356
|
-
* Queries the logs of an SSL server
|
|
5366
|
+
* Queries the logs of an SSL server.
|
|
5357
5367
|
*
|
|
5358
5368
|
* @param request - DescribeVpnSslServerLogsRequest
|
|
5359
5369
|
* @param runtime - runtime options for this request RuntimeOptions
|
|
@@ -5361,7 +5371,7 @@ export default class Client extends OpenApi {
|
|
|
5361
5371
|
*/
|
|
5362
5372
|
describeVpnSslServerLogsWithOptions(request: $_model.DescribeVpnSslServerLogsRequest, runtime: $dara.RuntimeOptions): Promise<$_model.DescribeVpnSslServerLogsResponse>;
|
|
5363
5373
|
/**
|
|
5364
|
-
* Queries the logs of an SSL server
|
|
5374
|
+
* Queries the logs of an SSL server.
|
|
5365
5375
|
*
|
|
5366
5376
|
* @param request - DescribeVpnSslServerLogsRequest
|
|
5367
5377
|
* @returns DescribeVpnSslServerLogsResponse
|
|
@@ -5435,10 +5445,10 @@ export default class Client extends OpenApi {
|
|
|
5435
5445
|
*/
|
|
5436
5446
|
diagnoseVpnConnections(request: $_model.DiagnoseVpnConnectionsRequest): Promise<$_model.DiagnoseVpnConnectionsResponse>;
|
|
5437
5447
|
/**
|
|
5438
|
-
*
|
|
5448
|
+
* Calls the DiagnoseVpnGateway operation to perform a one-click diagnosis on a specified VPN gateway instance.
|
|
5439
5449
|
*
|
|
5440
5450
|
* @remarks
|
|
5441
|
-
* Only VPN gateway instances in specific regions support the one-click
|
|
5451
|
+
* 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).
|
|
5442
5452
|
*
|
|
5443
5453
|
* @param request - DiagnoseVpnGatewayRequest
|
|
5444
5454
|
* @param runtime - runtime options for this request RuntimeOptions
|
|
@@ -5446,10 +5456,10 @@ export default class Client extends OpenApi {
|
|
|
5446
5456
|
*/
|
|
5447
5457
|
diagnoseVpnGatewayWithOptions(request: $_model.DiagnoseVpnGatewayRequest, runtime: $dara.RuntimeOptions): Promise<$_model.DiagnoseVpnGatewayResponse>;
|
|
5448
5458
|
/**
|
|
5449
|
-
*
|
|
5459
|
+
* Calls the DiagnoseVpnGateway operation to perform a one-click diagnosis on a specified VPN gateway instance.
|
|
5450
5460
|
*
|
|
5451
5461
|
* @remarks
|
|
5452
|
-
* Only VPN gateway instances in specific regions support the one-click
|
|
5462
|
+
* 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).
|
|
5453
5463
|
*
|
|
5454
5464
|
* @param request - DiagnoseVpnGatewayRequest
|
|
5455
5465
|
* @returns DiagnoseVpnGatewayResponse
|
|
@@ -5531,10 +5541,10 @@ export default class Client extends OpenApi {
|
|
|
5531
5541
|
* Dissociates a VPN gateway from a certificate.
|
|
5532
5542
|
*
|
|
5533
5543
|
* @remarks
|
|
5534
|
-
* - **DissociateVpnGatewayWithCertificate** is an asynchronous operation. After a request is sent, the system returns a request ID
|
|
5544
|
+
* - **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:
|
|
5535
5545
|
* - If the VPN gateway is in the **updating** state, the SSL certificate is being dissociated.
|
|
5536
5546
|
* - If the VPN gateway is in the **active** state, the SSL certificate is dissociated.
|
|
5537
|
-
* - **DissociateVpnGatewayWithCertificate** does not support concurrent SSL
|
|
5547
|
+
* - **DissociateVpnGatewayWithCertificate** does not support concurrent dissociation of SSL certificates from the same VPN gateway.
|
|
5538
5548
|
*
|
|
5539
5549
|
* @param request - DissociateVpnGatewayWithCertificateRequest
|
|
5540
5550
|
* @param runtime - runtime options for this request RuntimeOptions
|
|
@@ -5545,10 +5555,10 @@ export default class Client extends OpenApi {
|
|
|
5545
5555
|
* Dissociates a VPN gateway from a certificate.
|
|
5546
5556
|
*
|
|
5547
5557
|
* @remarks
|
|
5548
|
-
* - **DissociateVpnGatewayWithCertificate** is an asynchronous operation. After a request is sent, the system returns a request ID
|
|
5558
|
+
* - **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:
|
|
5549
5559
|
* - If the VPN gateway is in the **updating** state, the SSL certificate is being dissociated.
|
|
5550
5560
|
* - If the VPN gateway is in the **active** state, the SSL certificate is dissociated.
|
|
5551
|
-
* - **DissociateVpnGatewayWithCertificate** does not support concurrent SSL
|
|
5561
|
+
* - **DissociateVpnGatewayWithCertificate** does not support concurrent dissociation of SSL certificates from the same VPN gateway.
|
|
5552
5562
|
*
|
|
5553
5563
|
* @param request - DissociateVpnGatewayWithCertificateRequest
|
|
5554
5564
|
* @returns DissociateVpnGatewayWithCertificateResponse
|
|
@@ -5860,10 +5870,10 @@ export default class Client extends OpenApi {
|
|
|
5860
5870
|
*/
|
|
5861
5871
|
getVpcRouteEntrySummary(request: $_model.GetVpcRouteEntrySummaryRequest): Promise<$_model.GetVpcRouteEntrySummaryResponse>;
|
|
5862
5872
|
/**
|
|
5863
|
-
* Queries the one-click
|
|
5873
|
+
* Queries the one-click diagnosis result of a VPN gateway instance.
|
|
5864
5874
|
*
|
|
5865
5875
|
* @remarks
|
|
5866
|
-
* When you call the **GetVpnGatewayDiagnoseResult** operation, you must specify at least one of the **DiagnoseId** and **VpnGatewayId** parameters
|
|
5876
|
+
* When you call the **GetVpnGatewayDiagnoseResult** operation, in addition to the required parameters, you must specify at least one of the **DiagnoseId** and **VpnGatewayId** parameters.
|
|
5867
5877
|
*
|
|
5868
5878
|
* @param request - GetVpnGatewayDiagnoseResultRequest
|
|
5869
5879
|
* @param runtime - runtime options for this request RuntimeOptions
|
|
@@ -5871,10 +5881,10 @@ export default class Client extends OpenApi {
|
|
|
5871
5881
|
*/
|
|
5872
5882
|
getVpnGatewayDiagnoseResultWithOptions(request: $_model.GetVpnGatewayDiagnoseResultRequest, runtime: $dara.RuntimeOptions): Promise<$_model.GetVpnGatewayDiagnoseResultResponse>;
|
|
5873
5883
|
/**
|
|
5874
|
-
* Queries the one-click
|
|
5884
|
+
* Queries the one-click diagnosis result of a VPN gateway instance.
|
|
5875
5885
|
*
|
|
5876
5886
|
* @remarks
|
|
5877
|
-
* When you call the **GetVpnGatewayDiagnoseResult** operation, you must specify at least one of the **DiagnoseId** and **VpnGatewayId** parameters
|
|
5887
|
+
* When you call the **GetVpnGatewayDiagnoseResult** operation, in addition to the required parameters, you must specify at least one of the **DiagnoseId** and **VpnGatewayId** parameters.
|
|
5878
5888
|
*
|
|
5879
5889
|
* @param request - GetVpnGatewayDiagnoseResultRequest
|
|
5880
5890
|
* @returns GetVpnGatewayDiagnoseResultResponse
|
|
@@ -5927,7 +5937,7 @@ export default class Client extends OpenApi {
|
|
|
5927
5937
|
*/
|
|
5928
5938
|
grantInstanceToVbr(request: $_model.GrantInstanceToVbrRequest): Promise<$_model.GrantInstanceToVbrResponse>;
|
|
5929
5939
|
/**
|
|
5930
|
-
*
|
|
5940
|
+
* Queries the access point information of Express Connect circuits by calling the ListBusinessAccessPoints operation.
|
|
5931
5941
|
*
|
|
5932
5942
|
* @param request - ListBusinessAccessPointsRequest
|
|
5933
5943
|
* @param runtime - runtime options for this request RuntimeOptions
|
|
@@ -5935,7 +5945,7 @@ export default class Client extends OpenApi {
|
|
|
5935
5945
|
*/
|
|
5936
5946
|
listBusinessAccessPointsWithOptions(request: $_model.ListBusinessAccessPointsRequest, runtime: $dara.RuntimeOptions): Promise<$_model.ListBusinessAccessPointsResponse>;
|
|
5937
5947
|
/**
|
|
5938
|
-
*
|
|
5948
|
+
* Queries the access point information of Express Connect circuits by calling the ListBusinessAccessPoints operation.
|
|
5939
5949
|
*
|
|
5940
5950
|
* @param request - ListBusinessAccessPointsRequest
|
|
5941
5951
|
* @returns ListBusinessAccessPointsResponse
|
|
@@ -6355,7 +6365,7 @@ export default class Client extends OpenApi {
|
|
|
6355
6365
|
* @remarks
|
|
6356
6366
|
* When you call **ListVpnCertificateAssociations**:
|
|
6357
6367
|
* - If you specify only the **RegionId** parameter, all associations between VPN gateway instances and SSL certificates in the specified region are queried.
|
|
6358
|
-
* - If you specify the **RegionId** and **CertificateType** parameters, the associations between VPN gateway instances and SSL certificates of the specified
|
|
6368
|
+
* - 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.
|
|
6359
6369
|
* - 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.
|
|
6360
6370
|
* - 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.
|
|
6361
6371
|
*
|
|
@@ -6370,7 +6380,7 @@ export default class Client extends OpenApi {
|
|
|
6370
6380
|
* @remarks
|
|
6371
6381
|
* When you call **ListVpnCertificateAssociations**:
|
|
6372
6382
|
* - If you specify only the **RegionId** parameter, all associations between VPN gateway instances and SSL certificates in the specified region are queried.
|
|
6373
|
-
* - If you specify the **RegionId** and **CertificateType** parameters, the associations between VPN gateway instances and SSL certificates of the specified
|
|
6383
|
+
* - 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.
|
|
6374
6384
|
* - 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.
|
|
6375
6385
|
* - 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.
|
|
6376
6386
|
*
|
|
@@ -6484,7 +6494,7 @@ export default class Client extends OpenApi {
|
|
|
6484
6494
|
*/
|
|
6485
6495
|
modifyCommonBandwidthPackageSpec(request: $_model.ModifyCommonBandwidthPackageSpecRequest): Promise<$_model.ModifyCommonBandwidthPackageSpecResponse>;
|
|
6486
6496
|
/**
|
|
6487
|
-
* Modifies the configuration of a customer gateway
|
|
6497
|
+
* Modifies the configuration of a customer gateway.
|
|
6488
6498
|
*
|
|
6489
6499
|
* @remarks
|
|
6490
6500
|
* - 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:
|
|
@@ -6499,7 +6509,7 @@ export default class Client extends OpenApi {
|
|
|
6499
6509
|
*/
|
|
6500
6510
|
modifyCustomerGatewayAttributeWithOptions(request: $_model.ModifyCustomerGatewayAttributeRequest, runtime: $dara.RuntimeOptions): Promise<$_model.ModifyCustomerGatewayAttributeResponse>;
|
|
6501
6511
|
/**
|
|
6502
|
-
* Modifies the configuration of a customer gateway
|
|
6512
|
+
* Modifies the configuration of a customer gateway.
|
|
6503
6513
|
*
|
|
6504
6514
|
* @remarks
|
|
6505
6515
|
* - 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:
|
|
@@ -6573,12 +6583,12 @@ export default class Client extends OpenApi {
|
|
|
6573
6583
|
*/
|
|
6574
6584
|
modifyExpressCloudConnectionBandwidth(request: $_model.ModifyExpressCloudConnectionBandwidthRequest): Promise<$_model.ModifyExpressCloudConnectionBandwidthResponse>;
|
|
6575
6585
|
/**
|
|
6576
|
-
*
|
|
6586
|
+
* Modifies an Express Connect Quality of Service (QoS) policy. You can also use this operation to associate dedicated Express Connect circuits with the policy.
|
|
6577
6587
|
*
|
|
6578
6588
|
* @remarks
|
|
6579
6589
|
* - 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.
|
|
6580
|
-
* - When associating dedicated Express Connect circuits, only full
|
|
6581
|
-
* - If a dedicated Express Connect circuit has shared Express Connect circuits or cross-account VBRs, you must
|
|
6590
|
+
* - When associating dedicated Express Connect circuits, only full replacement is supported. To disassociate all circuits, pass an empty string.
|
|
6591
|
+
* - 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.
|
|
6582
6592
|
* - The device on which the dedicated Express Connect circuit resides must support the QoS feature before association.
|
|
6583
6593
|
* - 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.
|
|
6584
6594
|
*
|
|
@@ -6588,12 +6598,12 @@ export default class Client extends OpenApi {
|
|
|
6588
6598
|
*/
|
|
6589
6599
|
modifyExpressConnectTrafficQosWithOptions(request: $_model.ModifyExpressConnectTrafficQosRequest, runtime: $dara.RuntimeOptions): Promise<$_model.ModifyExpressConnectTrafficQosResponse>;
|
|
6590
6600
|
/**
|
|
6591
|
-
*
|
|
6601
|
+
* Modifies an Express Connect Quality of Service (QoS) policy. You can also use this operation to associate dedicated Express Connect circuits with the policy.
|
|
6592
6602
|
*
|
|
6593
6603
|
* @remarks
|
|
6594
6604
|
* - 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.
|
|
6595
|
-
* - When associating dedicated Express Connect circuits, only full
|
|
6596
|
-
* - If a dedicated Express Connect circuit has shared Express Connect circuits or cross-account VBRs, you must
|
|
6605
|
+
* - When associating dedicated Express Connect circuits, only full replacement is supported. To disassociate all circuits, pass an empty string.
|
|
6606
|
+
* - 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.
|
|
6597
6607
|
* - The device on which the dedicated Express Connect circuit resides must support the QoS feature before association.
|
|
6598
6608
|
* - 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.
|
|
6599
6609
|
*
|
|
@@ -7182,15 +7192,15 @@ export default class Client extends OpenApi {
|
|
|
7182
7192
|
*/
|
|
7183
7193
|
modifySslVpnClientCert(request: $_model.ModifySslVpnClientCertRequest): Promise<$_model.ModifySslVpnClientCertResponse>;
|
|
7184
7194
|
/**
|
|
7185
|
-
* Modifies the configuration of an SSL-VPN server.
|
|
7195
|
+
* Modifies the configuration of an SSL-VPN server by calling the ModifySslVpnServer operation.
|
|
7186
7196
|
*
|
|
7187
7197
|
* @remarks
|
|
7188
|
-
* - If you want to enable two-factor
|
|
7189
|
-
* - When you modify only the **Name** of the SSL-VPN server, this operation is synchronous. If you modify
|
|
7190
|
-
* - When **ModifySslVpnServer** is asynchronous, the system returns a request ID
|
|
7198
|
+
* - 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).
|
|
7199
|
+
* - 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.
|
|
7200
|
+
* - 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:
|
|
7191
7201
|
* - If the VPN gateway instance is in the **updating** state, the configuration of the SSL-VPN server is being modified.
|
|
7192
7202
|
* - If the VPN gateway instance is in the **active** state, the configuration of the SSL-VPN server has been modified.
|
|
7193
|
-
* - The **ModifySslVpnServer** operation does not support concurrent modifications to the
|
|
7203
|
+
* - The **ModifySslVpnServer** operation does not support concurrent modifications to the SSL-VPN server configuration under the same VPN gateway.
|
|
7194
7204
|
*
|
|
7195
7205
|
* @param request - ModifySslVpnServerRequest
|
|
7196
7206
|
* @param runtime - runtime options for this request RuntimeOptions
|
|
@@ -7198,15 +7208,15 @@ export default class Client extends OpenApi {
|
|
|
7198
7208
|
*/
|
|
7199
7209
|
modifySslVpnServerWithOptions(request: $_model.ModifySslVpnServerRequest, runtime: $dara.RuntimeOptions): Promise<$_model.ModifySslVpnServerResponse>;
|
|
7200
7210
|
/**
|
|
7201
|
-
* Modifies the configuration of an SSL-VPN server.
|
|
7211
|
+
* Modifies the configuration of an SSL-VPN server by calling the ModifySslVpnServer operation.
|
|
7202
7212
|
*
|
|
7203
7213
|
* @remarks
|
|
7204
|
-
* - If you want to enable two-factor
|
|
7205
|
-
* - When you modify only the **Name** of the SSL-VPN server, this operation is synchronous. If you modify
|
|
7206
|
-
* - When **ModifySslVpnServer** is asynchronous, the system returns a request ID
|
|
7214
|
+
* - 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).
|
|
7215
|
+
* - 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.
|
|
7216
|
+
* - 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:
|
|
7207
7217
|
* - If the VPN gateway instance is in the **updating** state, the configuration of the SSL-VPN server is being modified.
|
|
7208
7218
|
* - If the VPN gateway instance is in the **active** state, the configuration of the SSL-VPN server has been modified.
|
|
7209
|
-
* - The **ModifySslVpnServer** operation does not support concurrent modifications to the
|
|
7219
|
+
* - The **ModifySslVpnServer** operation does not support concurrent modifications to the SSL-VPN server configuration under the same VPN gateway.
|
|
7210
7220
|
*
|
|
7211
7221
|
* @param request - ModifySslVpnServerRequest
|
|
7212
7222
|
* @returns ModifySslVpnServerResponse
|
|
@@ -7302,7 +7312,7 @@ export default class Client extends OpenApi {
|
|
|
7302
7312
|
* @remarks
|
|
7303
7313
|
* - **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:
|
|
7304
7314
|
* - If the IPsec-VPN connection is in the **updating** state, the weight of the destination route entry is being modified.
|
|
7305
|
-
* - If the IPsec-VPN connection is in the **attached** state, the weight of the destination route entry
|
|
7315
|
+
* - If the IPsec-VPN connection is in the **attached** state, the weight of the destination route entry is modified.
|
|
7306
7316
|
* - **ModifyVcoRouteEntryWeight** does not support concurrent modifications of destination route entry weights for the same IPsec-VPN connection.
|
|
7307
7317
|
*
|
|
7308
7318
|
* @param request - ModifyVcoRouteEntryWeightRequest
|
|
@@ -7316,7 +7326,7 @@ export default class Client extends OpenApi {
|
|
|
7316
7326
|
* @remarks
|
|
7317
7327
|
* - **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:
|
|
7318
7328
|
* - If the IPsec-VPN connection is in the **updating** state, the weight of the destination route entry is being modified.
|
|
7319
|
-
* - If the IPsec-VPN connection is in the **attached** state, the weight of the destination route entry
|
|
7329
|
+
* - If the IPsec-VPN connection is in the **attached** state, the weight of the destination route entry is modified.
|
|
7320
7330
|
* - **ModifyVcoRouteEntryWeight** does not support concurrent modifications of destination route entry weights for the same IPsec-VPN connection.
|
|
7321
7331
|
*
|
|
7322
7332
|
* @param request - ModifyVcoRouteEntryWeightRequest
|
|
@@ -7410,13 +7420,13 @@ export default class Client extends OpenApi {
|
|
|
7410
7420
|
* Modifies the configuration of an IPsec-VPN connection.
|
|
7411
7421
|
*
|
|
7412
7422
|
* @remarks
|
|
7413
|
-
* - When you modify a dual-tunnel IPsec-VPN connection, in addition to the required parameters,
|
|
7414
|
-
* - When you modify a single-tunnel IPsec-VPN connection, in addition to the required parameters,
|
|
7415
|
-
* - **ModifyVpnAttachmentAttribute** is
|
|
7423
|
+
* - 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**.
|
|
7424
|
+
* - 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**.
|
|
7425
|
+
* - 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:
|
|
7416
7426
|
* - If the IPsec-VPN connection is in the **updating** state, the configuration is being modified.
|
|
7417
7427
|
* - If the IPsec-VPN connection is in the **attached** state, the configuration has been modified.
|
|
7418
|
-
* - **ModifyVpnAttachmentAttribute** does not support concurrent
|
|
7419
|
-
* - When you call **ModifyVpnAttachmentAttribute
|
|
7428
|
+
* - The **ModifyVpnAttachmentAttribute** operation does not support concurrent modifications to the IPsec-VPN connection configuration.
|
|
7429
|
+
* - When you call the **ModifyVpnAttachmentAttribute** operation, you cannot modify the gateway type of the IPsec-VPN connection.
|
|
7420
7430
|
*
|
|
7421
7431
|
* @param request - ModifyVpnAttachmentAttributeRequest
|
|
7422
7432
|
* @param runtime - runtime options for this request RuntimeOptions
|
|
@@ -7427,13 +7437,13 @@ export default class Client extends OpenApi {
|
|
|
7427
7437
|
* Modifies the configuration of an IPsec-VPN connection.
|
|
7428
7438
|
*
|
|
7429
7439
|
* @remarks
|
|
7430
|
-
* - When you modify a dual-tunnel IPsec-VPN connection, in addition to the required parameters,
|
|
7431
|
-
* - When you modify a single-tunnel IPsec-VPN connection, in addition to the required parameters,
|
|
7432
|
-
* - **ModifyVpnAttachmentAttribute** is
|
|
7440
|
+
* - 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**.
|
|
7441
|
+
* - 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**.
|
|
7442
|
+
* - 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:
|
|
7433
7443
|
* - If the IPsec-VPN connection is in the **updating** state, the configuration is being modified.
|
|
7434
7444
|
* - If the IPsec-VPN connection is in the **attached** state, the configuration has been modified.
|
|
7435
|
-
* - **ModifyVpnAttachmentAttribute** does not support concurrent
|
|
7436
|
-
* - When you call **ModifyVpnAttachmentAttribute
|
|
7445
|
+
* - The **ModifyVpnAttachmentAttribute** operation does not support concurrent modifications to the IPsec-VPN connection configuration.
|
|
7446
|
+
* - When you call the **ModifyVpnAttachmentAttribute** operation, you cannot modify the gateway type of the IPsec-VPN connection.
|
|
7437
7447
|
*
|
|
7438
7448
|
* @param request - ModifyVpnAttachmentAttributeRequest
|
|
7439
7449
|
* @returns ModifyVpnAttachmentAttributeResponse
|
|
@@ -7443,14 +7453,11 @@ export default class Client extends OpenApi {
|
|
|
7443
7453
|
* Modifies the configuration of an IPsec-VPN connection.
|
|
7444
7454
|
*
|
|
7445
7455
|
* @remarks
|
|
7446
|
-
* - To modify a dual-tunnel IPsec-VPN connection, the `ModifyVpnConnectionAttribute` operation supports the following request parameters in addition to the required parameters:
|
|
7456
|
+
* - To modify a dual-tunnel mode IPsec-VPN connection, the `ModifyVpnConnectionAttribute` operation supports the following request parameters in addition to the required parameters:
|
|
7447
7457
|
* **ClientToken**, **Name**, **LocalSubnet**, **RemoteSubnet**, **EffectImmediately**, **AutoConfigRoute**, **TunnelOptionsSpecification** array, and **EnableTunnelsBgp**.
|
|
7448
|
-
* - To modify a single-tunnel IPsec-VPN connection, the `ModifyVpnConnectionAttribute` operation supports the following request parameters in addition to the required parameters:
|
|
7458
|
+
* - To modify a single-tunnel mode IPsec-VPN connection, the `ModifyVpnConnectionAttribute` operation supports the following request parameters in addition to the required parameters:
|
|
7449
7459
|
* **ClientToken**, **Name**, **LocalSubnet**, **RemoteSubnet**, **EffectImmediately**, **IkeConfig**, **IpsecConfig**, **HealthCheckConfig**, **AutoConfigRoute**, **EnableDpd**, **EnableNatTraversal**, **BgpConfig**, and **RemoteCaCertificate**.
|
|
7450
|
-
* - The **ModifyVpnConnectionAttribute** operation is asynchronous. After a request is sent, the system returns a request ID
|
|
7451
|
-
* - If the VPN gateway instance is in the **updating** state, the configuration of the IPsec-VPN connection is being modified.
|
|
7452
|
-
* - If the VPN gateway instance is in the **active** state, the configuration of the IPsec-VPN connection is modified.
|
|
7453
|
-
* - The **ModifyVpnConnectionAttribute** operation does not support concurrent modifications to IPsec-VPN connection configurations under the same VPN gateway.
|
|
7460
|
+
* - 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:
|
|
7454
7461
|
*
|
|
7455
7462
|
* @param request - ModifyVpnConnectionAttributeRequest
|
|
7456
7463
|
* @param runtime - runtime options for this request RuntimeOptions
|
|
@@ -7461,14 +7468,11 @@ export default class Client extends OpenApi {
|
|
|
7461
7468
|
* Modifies the configuration of an IPsec-VPN connection.
|
|
7462
7469
|
*
|
|
7463
7470
|
* @remarks
|
|
7464
|
-
* - To modify a dual-tunnel IPsec-VPN connection, the `ModifyVpnConnectionAttribute` operation supports the following request parameters in addition to the required parameters:
|
|
7471
|
+
* - To modify a dual-tunnel mode IPsec-VPN connection, the `ModifyVpnConnectionAttribute` operation supports the following request parameters in addition to the required parameters:
|
|
7465
7472
|
* **ClientToken**, **Name**, **LocalSubnet**, **RemoteSubnet**, **EffectImmediately**, **AutoConfigRoute**, **TunnelOptionsSpecification** array, and **EnableTunnelsBgp**.
|
|
7466
|
-
* - To modify a single-tunnel IPsec-VPN connection, the `ModifyVpnConnectionAttribute` operation supports the following request parameters in addition to the required parameters:
|
|
7473
|
+
* - To modify a single-tunnel mode IPsec-VPN connection, the `ModifyVpnConnectionAttribute` operation supports the following request parameters in addition to the required parameters:
|
|
7467
7474
|
* **ClientToken**, **Name**, **LocalSubnet**, **RemoteSubnet**, **EffectImmediately**, **IkeConfig**, **IpsecConfig**, **HealthCheckConfig**, **AutoConfigRoute**, **EnableDpd**, **EnableNatTraversal**, **BgpConfig**, and **RemoteCaCertificate**.
|
|
7468
|
-
* - The **ModifyVpnConnectionAttribute** operation is asynchronous. After a request is sent, the system returns a request ID
|
|
7469
|
-
* - If the VPN gateway instance is in the **updating** state, the configuration of the IPsec-VPN connection is being modified.
|
|
7470
|
-
* - If the VPN gateway instance is in the **active** state, the configuration of the IPsec-VPN connection is modified.
|
|
7471
|
-
* - The **ModifyVpnConnectionAttribute** operation does not support concurrent modifications to IPsec-VPN connection configurations under the same VPN gateway.
|
|
7475
|
+
* - 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:
|
|
7472
7476
|
*
|
|
7473
7477
|
* @param request - ModifyVpnConnectionAttributeRequest
|
|
7474
7478
|
* @returns ModifyVpnConnectionAttributeResponse
|
|
@@ -7478,7 +7482,7 @@ export default class Client extends OpenApi {
|
|
|
7478
7482
|
* Invokes the ModifyVpnGatewayAttribute operation to modify the name, description, or routing automatic propagation feature of a VPN gateway.
|
|
7479
7483
|
*
|
|
7480
7484
|
* @remarks
|
|
7481
|
-
* - **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:
|
|
7485
|
+
* - **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:
|
|
7482
7486
|
* - If the VPN gateway is in the **updating** state, the configuration is being modified.
|
|
7483
7487
|
* - If the VPN gateway is in the **active** state, the configuration has been modified.
|
|
7484
7488
|
* - **ModifyVpnGatewayAttribute** does not support concurrent modifications to the configuration of the same VPN gateway.
|
|
@@ -7492,7 +7496,7 @@ export default class Client extends OpenApi {
|
|
|
7492
7496
|
* Invokes the ModifyVpnGatewayAttribute operation to modify the name, description, or routing automatic propagation feature of a VPN gateway.
|
|
7493
7497
|
*
|
|
7494
7498
|
* @remarks
|
|
7495
|
-
* - **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:
|
|
7499
|
+
* - **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:
|
|
7496
7500
|
* - If the VPN gateway is in the **updating** state, the configuration is being modified.
|
|
7497
7501
|
* - If the VPN gateway is in the **active** state, the configuration has been modified.
|
|
7498
7502
|
* - **ModifyVpnGatewayAttribute** does not support concurrent modifications to the configuration of the same VPN gateway.
|
|
@@ -7539,13 +7543,13 @@ export default class Client extends OpenApi {
|
|
|
7539
7543
|
*/
|
|
7540
7544
|
modifyVpnPbrRouteEntryAttribute(request: $_model.ModifyVpnPbrRouteEntryAttributeRequest): Promise<$_model.ModifyVpnPbrRouteEntryAttributeResponse>;
|
|
7541
7545
|
/**
|
|
7542
|
-
* Invokes the ModifyVpnPbrRouteEntryPriority operation to modify the policy priority of a policy-based routing
|
|
7546
|
+
* Invokes the ModifyVpnPbrRouteEntryPriority operation to modify the policy priority of a policy-based routing.
|
|
7543
7547
|
*
|
|
7544
7548
|
* @remarks
|
|
7545
|
-
* - **ModifyVpnPbrRouteEntryPriority** is an asynchronous operation. After you send a request, the system returns a request ID,
|
|
7546
|
-
* - If the VPN gateway instance is in the **updating** state, the policy-based routing
|
|
7547
|
-
* - If the VPN gateway instance is in the **active** state, the policy-based routing
|
|
7548
|
-
* - **ModifyVpnPbrRouteEntryPriority** does not support concurrent modifications of policy-based routing
|
|
7549
|
+
* - **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:
|
|
7550
|
+
* - If the VPN gateway instance is in the **updating** state, the policy-based routing is being modified.
|
|
7551
|
+
* - If the VPN gateway instance is in the **active** state, the policy-based routing has been modified.
|
|
7552
|
+
* - **ModifyVpnPbrRouteEntryPriority** does not support concurrent modifications of policy-based routing on the same VPN gateway instance.
|
|
7549
7553
|
*
|
|
7550
7554
|
* @param request - ModifyVpnPbrRouteEntryPriorityRequest
|
|
7551
7555
|
* @param runtime - runtime options for this request RuntimeOptions
|
|
@@ -7553,13 +7557,13 @@ export default class Client extends OpenApi {
|
|
|
7553
7557
|
*/
|
|
7554
7558
|
modifyVpnPbrRouteEntryPriorityWithOptions(request: $_model.ModifyVpnPbrRouteEntryPriorityRequest, runtime: $dara.RuntimeOptions): Promise<$_model.ModifyVpnPbrRouteEntryPriorityResponse>;
|
|
7555
7559
|
/**
|
|
7556
|
-
* Invokes the ModifyVpnPbrRouteEntryPriority operation to modify the policy priority of a policy-based routing
|
|
7560
|
+
* Invokes the ModifyVpnPbrRouteEntryPriority operation to modify the policy priority of a policy-based routing.
|
|
7557
7561
|
*
|
|
7558
7562
|
* @remarks
|
|
7559
|
-
* - **ModifyVpnPbrRouteEntryPriority** is an asynchronous operation. After you send a request, the system returns a request ID,
|
|
7560
|
-
* - If the VPN gateway instance is in the **updating** state, the policy-based routing
|
|
7561
|
-
* - If the VPN gateway instance is in the **active** state, the policy-based routing
|
|
7562
|
-
* - **ModifyVpnPbrRouteEntryPriority** does not support concurrent modifications of policy-based routing
|
|
7563
|
+
* - **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:
|
|
7564
|
+
* - If the VPN gateway instance is in the **updating** state, the policy-based routing is being modified.
|
|
7565
|
+
* - If the VPN gateway instance is in the **active** state, the policy-based routing has been modified.
|
|
7566
|
+
* - **ModifyVpnPbrRouteEntryPriority** does not support concurrent modifications of policy-based routing on the same VPN gateway instance.
|
|
7563
7567
|
*
|
|
7564
7568
|
* @param request - ModifyVpnPbrRouteEntryPriorityRequest
|
|
7565
7569
|
* @returns ModifyVpnPbrRouteEntryPriorityResponse
|
|
@@ -7600,12 +7604,12 @@ export default class Client extends OpenApi {
|
|
|
7600
7604
|
* Modifies the weight of a destination route by calling the ModifyVpnRouteEntryWeight operation.
|
|
7601
7605
|
*
|
|
7602
7606
|
* @remarks
|
|
7603
|
-
* > 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
|
|
7607
|
+
* > 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.
|
|
7604
7608
|
* - 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).
|
|
7605
|
-
* -
|
|
7609
|
+
* - **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:
|
|
7606
7610
|
* - If the VPN destination route is in the **updating** state, the weight is being modified.
|
|
7607
|
-
* - If the VPN destination route is in the **active** state, the weight
|
|
7608
|
-
* -
|
|
7611
|
+
* - If the VPN destination route is in the **active** state, the weight has been modified.
|
|
7612
|
+
* - **ModifyVpnRouteEntryWeight** does not support concurrent modification of destination route weights on the same VPN gateway.
|
|
7609
7613
|
*
|
|
7610
7614
|
* @param request - ModifyVpnRouteEntryWeightRequest
|
|
7611
7615
|
* @param runtime - runtime options for this request RuntimeOptions
|
|
@@ -7616,12 +7620,12 @@ export default class Client extends OpenApi {
|
|
|
7616
7620
|
* Modifies the weight of a destination route by calling the ModifyVpnRouteEntryWeight operation.
|
|
7617
7621
|
*
|
|
7618
7622
|
* @remarks
|
|
7619
|
-
* > 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
|
|
7623
|
+
* > 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.
|
|
7620
7624
|
* - 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).
|
|
7621
|
-
* -
|
|
7625
|
+
* - **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:
|
|
7622
7626
|
* - If the VPN destination route is in the **updating** state, the weight is being modified.
|
|
7623
|
-
* - If the VPN destination route is in the **active** state, the weight
|
|
7624
|
-
* -
|
|
7627
|
+
* - If the VPN destination route is in the **active** state, the weight has been modified.
|
|
7628
|
+
* - **ModifyVpnRouteEntryWeight** does not support concurrent modification of destination route weights on the same VPN gateway.
|
|
7625
7629
|
*
|
|
7626
7630
|
* @param request - ModifyVpnRouteEntryWeightRequest
|
|
7627
7631
|
* @returns ModifyVpnRouteEntryWeightResponse
|
|
@@ -8590,7 +8594,7 @@ export default class Client extends OpenApi {
|
|
|
8590
8594
|
*/
|
|
8591
8595
|
updateGatewayRouteTableEntryAttribute(request: $_model.UpdateGatewayRouteTableEntryAttributeRequest): Promise<$_model.UpdateGatewayRouteTableEntryAttributeResponse>;
|
|
8592
8596
|
/**
|
|
8593
|
-
*
|
|
8597
|
+
* Calls the UpdateIpsecServer operation to update the configuration of an IPsec server.
|
|
8594
8598
|
*
|
|
8595
8599
|
* @remarks
|
|
8596
8600
|
* - 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.
|
|
@@ -8605,7 +8609,7 @@ export default class Client extends OpenApi {
|
|
|
8605
8609
|
*/
|
|
8606
8610
|
updateIpsecServerWithOptions(request: $_model.UpdateIpsecServerRequest, runtime: $dara.RuntimeOptions): Promise<$_model.UpdateIpsecServerResponse>;
|
|
8607
8611
|
/**
|
|
8608
|
-
*
|
|
8612
|
+
* Calls the UpdateIpsecServer operation to update the configuration of an IPsec server.
|
|
8609
8613
|
*
|
|
8610
8614
|
* @remarks
|
|
8611
8615
|
* - 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.
|