AsyncClient (alibabacloud-cbn20170912 1.0.29 API)

所有超级接口:

AutoCloseable, com.aliyun.core.utils.SdkAutoCloseable

所有已知实现类:

DefaultAsyncClient
```
public interface AsyncClient
extends com.aliyun.core.utils.SdkAutoCloseable
```

方法概要

所有方法静态方法实例方法抽象方法默认方法已过时的方法
限定符和类型	方法和说明
`CompletableFuture<ActiveFlowLogResponse>`	`activeFlowLog(ActiveFlowLogRequest request)` description : After you create a flow log, it is enabled by default.
`CompletableFuture<AddTrafficMatchRuleToTrafficMarkingPolicyResponse>`	`addTrafficMatchRuleToTrafficMarkingPolicy(AddTrafficMatchRuleToTrafficMarkingPolicyRequest request)` description : AddTrafficMatchRuleToTrafficMarkingPolicy* is an asynchronous operation.
`CompletableFuture<AddTraficMatchRuleToTrafficMarkingPolicyResponse>`	`addTraficMatchRuleToTrafficMarkingPolicy(AddTraficMatchRuleToTrafficMarkingPolicyRequest request)` 已过时。 OpenAPI AddTraficMatchRuleToTrafficMarkingPolicy is deprecated, please use Cbn::2017-09-12::AddTrafficMatchRuleToTrafficMarkingPolicy instead. * @description ### Usage notes The AddTraficMatchRuleToTrafficMarkingPolicy operation is deprecated and will be discontinued soon. If you need to add a traffic classification rule to a traffic marking policy, call the [AddTrafficMatchRuleToTrafficMarkingPolicy](https://help.aliyun.com/document_detail/427602.html) operation.
`CompletableFuture<AssociateCenBandwidthPackageResponse>`	`associateCenBandwidthPackage(AssociateCenBandwidthPackageRequest request)` description : You can associate multiple bandwidth plans with a CEN instance.
`CompletableFuture<AssociateTransitRouterAttachmentWithRouteTableResponse>`	`associateTransitRouterAttachmentWithRouteTable(AssociateTransitRouterAttachmentWithRouteTableRequest request)` description : After you create a network instance connection on a transit router, you can configure an associated forwarding correlation to associate the network instance connection with the route table of an Enterprise Edition transit router.
`CompletableFuture<AssociateTransitRouterMulticastDomainResponse>`	`associateTransitRouterMulticastDomain(AssociateTransitRouterMulticastDomainRequest request)` description : A vSwitch can be associated with only one multicast domain.
`CompletableFuture<AttachCenChildInstanceResponse>`	`attachCenChildInstance(AttachCenChildInstanceRequest request)` description : CEN allows you to attach a network instance that belongs to another Alibaba Cloud account to your CEN instance.
`static DefaultAsyncClientBuilder`	`builder()`
`CompletableFuture<CheckTransitRouterServiceResponse>`	`checkTransitRouterService(CheckTransitRouterServiceRequest request)`
`static AsyncClient`	`create()`
`CompletableFuture<CreateCenResponse>`	`createCen(CreateCenRequest request)` description : CreateCen* is an asynchronous operation.
`CompletableFuture<CreateCenBandwidthPackageResponse>`	`createCenBandwidthPackage(CreateCenBandwidthPackageRequest request)` description : You must specify the areas to be connected when you create a bandwidth plan.
`CompletableFuture<CreateCenChildInstanceRouteEntryToAttachmentResponse>`	`createCenChildInstanceRouteEntryToAttachment(CreateCenChildInstanceRouteEntryToAttachmentRequest request)` description : You can add routes only to virtual private clouds (VPCs) or virtual border routers (VBRs) that are connected to an Enterprise Edition transit router.
`CompletableFuture<CreateCenChildInstanceRouteEntryToCenResponse>`	`createCenChildInstanceRouteEntryToCen(CreateCenChildInstanceRouteEntryToCenRequest request)` description : Limits By default, the CreateCenChildInstanceRouteEntryToCen operation is unavailable.
`CompletableFuture<CreateCenInterRegionTrafficQosPolicyResponse>`	`createCenInterRegionTrafficQosPolicy(CreateCenInterRegionTrafficQosPolicyRequest request)` description : Only inter-region connections created on Enterprise Edition transit routers support QoS policies.
`CompletableFuture<CreateCenInterRegionTrafficQosQueueResponse>`	`createCenInterRegionTrafficQosQueue(CreateCenInterRegionTrafficQosQueueRequest request)` description : The CreateCenInterRegionTrafficQosQueue operation is an asynchronous operation.
`CompletableFuture<CreateCenRouteMapResponse>`	`createCenRouteMap(CreateCenRouteMapRequest request)` description : Routing policies are sorted by priority.
`CompletableFuture<CreateFlowlogResponse>`	`createFlowlog(CreateFlowlogRequest request)` description : Flow logs can be used to capture traffic information about transit routers and network instance connections, including inter-region connections, virtual private cloud (VPC) connections, VPN connections, Express Connect Router (ECR) connections, and virtual border router (VBR) connections.
`CompletableFuture<CreateTrafficMarkingPolicyResponse>`	`createTrafficMarkingPolicy(CreateTrafficMarkingPolicyRequest request)` description : Only Enterprise Edition transit routers support traffic marking policies.
`CompletableFuture<CreateTransitRouterResponse>`	`createTransitRouter(CreateTransitRouterRequest request)` description : You can call CreateTransitRouter to create an Enterprise Edition transit router.
`CompletableFuture<CreateTransitRouterCidrResponse>`	`createTransitRouterCidr(CreateTransitRouterCidrRequest request)` description : You can specify a CIDR block for a transit router.
`CompletableFuture<CreateTransitRouterEcrAttachmentResponse>`	`createTransitRouterEcrAttachment(CreateTransitRouterEcrAttachmentRequest request)` description : Only Enterprise Edition transit routers support ECR connections.
`CompletableFuture<CreateTransitRouterMulticastDomainResponse>`	`createTransitRouterMulticastDomain(CreateTransitRouterMulticastDomainRequest request)` description : Before you call this operation, read the following rules: Make sure that an Enterprise Edition transit router is deployed in the region where you want to create the multicast domain, and the multicast feature is enabled for the Enterprise Edition transit router.
`CompletableFuture<CreateTransitRouterPeerAttachmentResponse>`	`createTransitRouterPeerAttachment(CreateTransitRouterPeerAttachmentRequest request)` description : Enterprise Edition transit routers allow you to allocate bandwidth resources to inter-region connections by using the following methods: * Allocate bandwidth resources from a bandwidth plan: You must purchase a bandwidth plan, and then allocate bandwidth resources from the bandwidth plan to inter-region connections.
`CompletableFuture<CreateTransitRouterPrefixListAssociationResponse>`	`createTransitRouterPrefixListAssociation(CreateTransitRouterPrefixListAssociationRequest request)` description : To associate an Enterprise Edition transit router with a route prefix, you must meet the following requirements: You are familiar with the limits and route compatibility notes of prefix lists.
`CompletableFuture<CreateTransitRouterRouteEntryResponse>`	`createTransitRouterRouteEntry(CreateTransitRouterRouteEntryRequest request)` description : CreateTransitRouterRouteEntry* is an asynchronous operation.
`CompletableFuture<CreateTransitRouterRouteTableResponse>`	`createTransitRouterRouteTable(CreateTransitRouterRouteTableRequest request)` description : Only Enterprise Edition transit routers support custom route tables.
`CompletableFuture<CreateTransitRouterVbrAttachmentResponse>`	`createTransitRouterVbrAttachment(CreateTransitRouterVbrAttachmentRequest request)` description : For more information about the regions and zones that support Enterprise Edition transit routers, see What is CEN?
`CompletableFuture<CreateTransitRouterVpcAttachmentResponse>`	`createTransitRouterVpcAttachment(CreateTransitRouterVpcAttachmentRequest request)` description : You can use the following methods to create a VPC connection from an Enterprise Edition transit router: * If an Enterprise Edition transit router is already created in the region where you want to create a VPC connection, configure the VpcId, ZoneMappings.N.VSwitchId, ZoneMappings.N.ZoneId, TransitRouterId, and RegionId parameters
`CompletableFuture<CreateTransitRouterVpnAttachmentResponse>`	`createTransitRouterVpnAttachment(CreateTransitRouterVpnAttachmentRequest request)` description : By default, route learning and associated forwarding are disabled between transit router route tables and IPsec-VPN attachments.
`CompletableFuture<CreateTransitRouteTableAggregationResponse>`	`createTransitRouteTableAggregation(CreateTransitRouteTableAggregationRequest request)` description : After you add an aggregate route to a route table of an Enterprise Edition transit router, the transit router advertises its routes only to route tables of associated virtual private clouds (VPCs) and have route synchronization enabled.
`CompletableFuture<DeactiveFlowLogResponse>`	`deactiveFlowLog(DeactiveFlowLogRequest request)` description : `DeactiveFlowLog` is an asynchronous operation.
`CompletableFuture<DeleteCenResponse>`	`deleteCen(DeleteCenRequest request)` description : DeleteCen* is an asynchronous operation.
`CompletableFuture<DeleteCenBandwidthPackageResponse>`	`deleteCenBandwidthPackage(DeleteCenBandwidthPackageRequest request)`
`CompletableFuture<DeleteCenChildInstanceRouteEntryToAttachmentResponse>`	`deleteCenChildInstanceRouteEntryToAttachment(DeleteCenChildInstanceRouteEntryToAttachmentRequest request)` description : You can delete routes only from virtual private clouds (VPCs) and virtual border routers (VBRs) whose next hop is an Enterprise Edition transit router connection, which is the connection to the network instance.
`CompletableFuture<DeleteCenChildInstanceRouteEntryToCenResponse>`	`deleteCenChildInstanceRouteEntryToCen(DeleteCenChildInstanceRouteEntryToCenRequest request)` description : Limits By default, the DeleteCenChildInstanceRouteEntryToCen operation is unavailable.
`CompletableFuture<DeleteCenInterRegionTrafficQosPolicyResponse>`	`deleteCenInterRegionTrafficQosPolicy(DeleteCenInterRegionTrafficQosPolicyRequest request)` description : Before you delete a QoS policy, you must delete all queues in the QoS policy except the default queue.
`CompletableFuture<DeleteCenInterRegionTrafficQosQueueResponse>`	`deleteCenInterRegionTrafficQosQueue(DeleteCenInterRegionTrafficQosQueueRequest request)` description : You cannot delete the default queue.
`CompletableFuture<DeleteCenRouteMapResponse>`	`deleteCenRouteMap(DeleteCenRouteMapRequest request)` description : `DeleteCenRouteMap` is an asynchronous operation.
`CompletableFuture<DeleteFlowlogResponse>`	`deleteFlowlog(DeleteFlowlogRequest request)` description : `DeleteFlowlog` is an asynchronous operation.
`CompletableFuture<DeleteRouteServiceInCenResponse>`	`deleteRouteServiceInCen(DeleteRouteServiceInCenRequest request)` description : DeleteRouteServiceInCen* is an asynchronous operation.
`CompletableFuture<DeleteTrafficMarkingPolicyResponse>`	`deleteTrafficMarkingPolicy(DeleteTrafficMarkingPolicyRequest request)` description : DeleteTrafficMarkingPolicy is an asynchronous operation.
`CompletableFuture<DeleteTransitRouterResponse>`	`deleteTransitRouter(DeleteTransitRouterRequest request)` description : DeleteTransitRouter* is an asynchronous operation.
`CompletableFuture<DeleteTransitRouterCidrResponse>`	`deleteTransitRouterCidr(DeleteTransitRouterCidrRequest request)` description : If IP addresses within the CIDR block have been allocated to network instances, the CIDR block cannot be deleted.
`CompletableFuture<DeleteTransitRouterEcrAttachmentResponse>`	`deleteTransitRouterEcrAttachment(DeleteTransitRouterEcrAttachmentRequest request)` description : DeleteTransitRouterEcrAttachment is an asynchronous operation.
`CompletableFuture<DeleteTransitRouterMulticastDomainResponse>`	`deleteTransitRouterMulticastDomain(DeleteTransitRouterMulticastDomainRequest request)` description : Before you delete a multicast domain, make sure that the following requirements are met: The multicast domain is disassociated from all vSwitches.
`CompletableFuture<DeleteTransitRouterPeerAttachmentResponse>`	`deleteTransitRouterPeerAttachment(DeleteTransitRouterPeerAttachmentRequest request)` description : DeleteTransitRouterPeerAttachment* is an asynchronous operation.
`CompletableFuture<DeleteTransitRouterPrefixListAssociationResponse>`	`deleteTransitRouterPrefixListAssociation(DeleteTransitRouterPrefixListAssociationRequest request)` description : After you disassociate a route table of an Enterprise Edition transit router from a prefix list, the routes that point to the CIDR blocks in the prefix list are automatically withdrawn from the route table.
`CompletableFuture<DeleteTransitRouterRouteEntryResponse>`	`deleteTransitRouterRouteEntry(DeleteTransitRouterRouteEntryRequest request)` description : Before you call this operation, take note of the following items: If you specify the TransitRouterRouteEntryId parameter to delete a specific route, you do not need to configure the TransitRouterRouteTableId or TransitRouterRouteEntryDestinationCidrBlock.
`CompletableFuture<DeleteTransitRouterRouteTableResponse>`	`deleteTransitRouterRouteTable(DeleteTransitRouterRouteTableRequest request)` description : You cannot delete the default route table of an Enterprise Edition transit router.
`CompletableFuture<DeleteTransitRouterVbrAttachmentResponse>`	`deleteTransitRouterVbrAttachment(DeleteTransitRouterVbrAttachmentRequest request)` description : DeleteTransitRouterVbrAttachment* is an asynchronous operation.
`CompletableFuture<DeleteTransitRouterVpcAttachmentResponse>`	`deleteTransitRouterVpcAttachment(DeleteTransitRouterVpcAttachmentRequest request)` description : DeleteTransitRouterVpcAttachment* is an asynchronous operation.
`CompletableFuture<DeleteTransitRouterVpnAttachmentResponse>`	`deleteTransitRouterVpnAttachment(DeleteTransitRouterVpnAttachmentRequest request)` description : Before you call the DeleteTransitRouterVpnAttachment operation, make sure that all request parameters are valid.
`CompletableFuture<DeleteTransitRouteTableAggregationResponse>`	`deleteTransitRouteTableAggregation(DeleteTransitRouteTableAggregationRequest request)` description : Before you delete an aggregate route, make sure that your network has a redundant route to prevent service interruptions.
`CompletableFuture<DeregisterTransitRouterMulticastGroupMembersResponse>`	`deregisterTransitRouterMulticastGroupMembers(DeregisterTransitRouterMulticastGroupMembersRequest request)` description : `DeregisterTransitRouterMulticastGroupMembers` is an asynchronous operation.
`CompletableFuture<DeregisterTransitRouterMulticastGroupSourcesResponse>`	`deregisterTransitRouterMulticastGroupSources(DeregisterTransitRouterMulticastGroupSourcesRequest request)` description : `DeregisterTransitRouterMulticastGroupSources` is an asynchronous operation.
`CompletableFuture<DescribeCenAttachedChildInstanceAttributeResponse>`	`describeCenAttachedChildInstanceAttribute(DescribeCenAttachedChildInstanceAttributeRequest request)`
`CompletableFuture<DescribeCenAttachedChildInstancesResponse>`	`describeCenAttachedChildInstances(DescribeCenAttachedChildInstancesRequest request)` description : You can use one of the following methods to query the information about the network instances that are attached to a CEN instance: You can query all the network instances that are attached to a CEN instance by setting the `CenId` parameter.
`CompletableFuture<DescribeCenBandwidthPackagesResponse>`	`describeCenBandwidthPackages(DescribeCenBandwidthPackagesRequest request)`
`CompletableFuture<DescribeCenChildInstanceRouteEntriesResponse>`	`describeCenChildInstanceRouteEntries(DescribeCenChildInstanceRouteEntriesRequest request)`
`CompletableFuture<DescribeCenGeographicSpanRemainingBandwidthResponse>`	`describeCenGeographicSpanRemainingBandwidth(DescribeCenGeographicSpanRemainingBandwidthRequest request)`
`CompletableFuture<DescribeCenGeographicSpansResponse>`	`describeCenGeographicSpans(DescribeCenGeographicSpansRequest request)`
`CompletableFuture<DescribeCenInterRegionBandwidthLimitsResponse>`	`describeCenInterRegionBandwidthLimits(DescribeCenInterRegionBandwidthLimitsRequest request)`
`CompletableFuture<DescribeCenPrivateZoneRoutesResponse>`	`describeCenPrivateZoneRoutes(DescribeCenPrivateZoneRoutesRequest request)`
`CompletableFuture<DescribeCenRegionDomainRouteEntriesResponse>`	`describeCenRegionDomainRouteEntries(DescribeCenRegionDomainRouteEntriesRequest request)`
`CompletableFuture<DescribeCenRouteMapsResponse>`	`describeCenRouteMaps(DescribeCenRouteMapsRequest request)`
`CompletableFuture<DescribeCensResponse>`	`describeCens(DescribeCensRequest request)`
`CompletableFuture<DescribeCenVbrHealthCheckResponse>`	`describeCenVbrHealthCheck(DescribeCenVbrHealthCheckRequest request)`
`CompletableFuture<DescribeChildInstanceRegionsResponse>`	`describeChildInstanceRegions(DescribeChildInstanceRegionsRequest request)` description : The regions that support CEN vary based on the network instance type.
`CompletableFuture<DescribeFlowlogsResponse>`	`describeFlowlogs(DescribeFlowlogsRequest request)`
`CompletableFuture<DescribeGeographicRegionMembershipResponse>`	`describeGeographicRegionMembership(DescribeGeographicRegionMembershipRequest request)`
`CompletableFuture<DescribeGrantRulesToCenResponse>`	`describeGrantRulesToCen(DescribeGrantRulesToCenRequest request)` description : Before you call the DescribeGrantRulesToCen operation, make sure that all request parameters are valid.
`CompletableFuture<DescribeGrantRulesToResourceResponse>`	`describeGrantRulesToResource(DescribeGrantRulesToResourceRequest request)`
`CompletableFuture<DescribePublishedRouteEntriesResponse>`	`describePublishedRouteEntries(DescribePublishedRouteEntriesRequest request)`
`CompletableFuture<DescribeRouteConflictResponse>`	`describeRouteConflict(DescribeRouteConflictRequest request)`
`CompletableFuture<DescribeRouteServicesInCenResponse>`	`describeRouteServicesInCen(DescribeRouteServicesInCenRequest request)`
`CompletableFuture<DescribeTransitRouteTableAggregationResponse>`	`describeTransitRouteTableAggregation(DescribeTransitRouteTableAggregationRequest request)` description : You can specify the values of the TransitRouteTableId and TransitRouteTableAggregationCidr parameters to query a specified aggregate route.
`CompletableFuture<DescribeTransitRouteTableAggregationDetailResponse>`	`describeTransitRouteTableAggregationDetail(DescribeTransitRouteTableAggregationDetailRequest request)`
`CompletableFuture<DetachCenChildInstanceResponse>`	`detachCenChildInstance(DetachCenChildInstanceRequest request)`
`CompletableFuture<DisableCenVbrHealthCheckResponse>`	`disableCenVbrHealthCheck(DisableCenVbrHealthCheckRequest request)` description : DisableCenVbrHealthCheck* is an asynchronous operation.
`CompletableFuture<DisableTransitRouterRouteTablePropagationResponse>`	`disableTransitRouterRouteTablePropagation(DisableTransitRouterRouteTablePropagationRequest request)` description : DisableTransitRouterRouteTablePropagation* is an synchronous operation.
`CompletableFuture<DisassociateTransitRouterMulticastDomainResponse>`	`disassociateTransitRouterMulticastDomain(DisassociateTransitRouterMulticastDomainRequest request)` description : Before you delete a vSwitch from a multicast domain, make sure that the vSwitch does not contain a multicast source or a multicast member.
`CompletableFuture<DissociateTransitRouterAttachmentFromRouteTableResponse>`	`dissociateTransitRouterAttachmentFromRouteTable(DissociateTransitRouterAttachmentFromRouteTableRequest request)` description : DissociateTransitRouterAttachmentFromRouteTable* is an asynchronous operation.
`CompletableFuture<EnableCenVbrHealthCheckResponse>`	`enableCenVbrHealthCheck(EnableCenVbrHealthCheckRequest request)` description : You can enable the health check feature for a VBR to monitor the Express Connect circuit between your data center and Alibaba Cloud.
`CompletableFuture<EnableTransitRouterRouteTablePropagationResponse>`	`enableTransitRouterRouteTablePropagation(EnableTransitRouterRouteTablePropagationRequest request)` description : After you establish a network instance connection on a transit router, you can create a route learning correlation for the network instance connection.
`CompletableFuture<GrantInstanceToTransitRouterResponse>`	`grantInstanceToTransitRouter(GrantInstanceToTransitRouterRequest request)` description : The `GrantInstanceToTransitRouter` operation can be used to grant transit routers permissions on network instances that belong to other Alibaba Cloud accounts, including virtual private clouds (VPCs), virtual border routers (VBRs), IPsec-VPN connections, and Express Connect Router (ECRs).
`CompletableFuture<ListCenChildInstanceRouteEntriesToAttachmentResponse>`	`listCenChildInstanceRouteEntriesToAttachment(ListCenChildInstanceRouteEntriesToAttachmentRequest request)` description : Before you call the ListCenChildInstanceRouteEntriesToAttachment operation, make sure that all request parameter values are valid.
`CompletableFuture<ListCenInterRegionTrafficQosPoliciesResponse>`	`listCenInterRegionTrafficQosPolicies(ListCenInterRegionTrafficQosPoliciesRequest request)` description : Before you call the ListCenInterRegionTrafficQosPolicies operation, take note of the following information: You must specify at least one of the TransitRouterId and TrafficQosPolicyId parameters.
`CompletableFuture<ListCenInterRegionTrafficQosQueuesResponse>`	`listCenInterRegionTrafficQosQueues(ListCenInterRegionTrafficQosQueuesRequest request)` description : You must specify at least one of the TransitRouterId, TrafficQosPolicyId, and TrafficQosQueueId parameters.
`CompletableFuture<ListGrantVSwitchEnisResponse>`	`listGrantVSwitchEnis(ListGrantVSwitchEnisRequest request)` description : Before you call `ListGrantVSwitchEnis`, make sure that the VPC is attached to a Cloud Enterprise Network (CEN) instance.
`CompletableFuture<ListGrantVSwitchesToCenResponse>`	`listGrantVSwitchesToCen(ListGrantVSwitchesToCenRequest request)` description : Before you call the `ListGrantVSwitchesToCen` operation, make sure that the following requirements are met: The permissions on the VPC are granted to the CEN instance.
`CompletableFuture<ListTagResourcesResponse>`	`listTagResources(ListTagResourcesRequest request)` description : To call this operation, you must set at least one of ResourceId.N and Tag.N.Key.
`CompletableFuture<ListTrafficMarkingPoliciesResponse>`	`listTrafficMarkingPolicies(ListTrafficMarkingPoliciesRequest request)` description : Before you call the ListTrafficMarkingPolicies operation, take note of the following limits: Specify at least one of the TransitRouterId and TrafficMarkingPolicyId parameters.
`CompletableFuture<ListTransitRouterAvailableResourceResponse>`	`listTransitRouterAvailableResource(ListTransitRouterAvailableResourceRequest request)` description : You can call the ListTransitRouterAvailableResource operation to query the zones that support Enterprise Edition transit routers in a specified region
`CompletableFuture<ListTransitRouterCidrResponse>`	`listTransitRouterCidr(ListTransitRouterCidrRequest request)`
`CompletableFuture<ListTransitRouterCidrAllocationResponse>`	`listTransitRouterCidrAllocation(ListTransitRouterCidrAllocationRequest request)`
`CompletableFuture<ListTransitRouterEcrAttachmentsResponse>`	`listTransitRouterEcrAttachments(ListTransitRouterEcrAttachmentsRequest request)` description : You can use the following methods to query ECR connection information: Specify the ID of an Enterprise Edition transit router.
`CompletableFuture<ListTransitRouterMulticastDomainAssociationsResponse>`	`listTransitRouterMulticastDomainAssociations(ListTransitRouterMulticastDomainAssociationsRequest request)` description : You must set at least TransitRouterMulticastDomainId and TransitRouterAttachmentId.
`CompletableFuture<ListTransitRouterMulticastDomainsResponse>`	`listTransitRouterMulticastDomains(ListTransitRouterMulticastDomainsRequest request)` description : If you configure one of the RegionId and CenId parameters, you must configure the other parameter.
`CompletableFuture<ListTransitRouterMulticastDomainVSwitchesResponse>`	`listTransitRouterMulticastDomainVSwitches(ListTransitRouterMulticastDomainVSwitchesRequest request)`
`CompletableFuture<ListTransitRouterMulticastGroupsResponse>`	`listTransitRouterMulticastGroups(ListTransitRouterMulticastGroupsRequest request)` description : You can call the `ListTransitRouterMulticastGroups` operation to query the multicast sources and members in a multicast domain.
`CompletableFuture<ListTransitRouterPeerAttachmentsResponse>`	`listTransitRouterPeerAttachments(ListTransitRouterPeerAttachmentsRequest request)` description : You can use the following methods to query inter-region connections on an Enterprise Edition transit router: Query all inter-region connections on an Enterprise Edition transit router by specifying the ID of the Enterprise Edition transit router.
`CompletableFuture<ListTransitRouterPrefixListAssociationResponse>`	`listTransitRouterPrefixListAssociation(ListTransitRouterPrefixListAssociationRequest request)`
`CompletableFuture<ListTransitRouterRouteEntriesResponse>`	`listTransitRouterRouteEntries(ListTransitRouterRouteEntriesRequest request)`
`CompletableFuture<ListTransitRouterRouteTableAssociationsResponse>`	`listTransitRouterRouteTableAssociations(ListTransitRouterRouteTableAssociationsRequest request)` description : When you call ListTransitRouterRouteTableAssociations, you must set at least one of TransitRouterRouteTableId and TransitRouterAttachmentId.
`CompletableFuture<ListTransitRouterRouteTablePropagationsResponse>`	`listTransitRouterRouteTablePropagations(ListTransitRouterRouteTablePropagationsRequest request)`
`CompletableFuture<ListTransitRouterRouteTablesResponse>`	`listTransitRouterRouteTables(ListTransitRouterRouteTablesRequest request)`
`CompletableFuture<ListTransitRoutersResponse>`	`listTransitRouters(ListTransitRoutersRequest request)` description : You can set the RegionId and TransitRouterId parameters based on your requirements.
`CompletableFuture<ListTransitRouterVbrAttachmentsResponse>`	`listTransitRouterVbrAttachments(ListTransitRouterVbrAttachmentsRequest request)` description : You can use the following methods to query VBR connections on an Enterprise Edition transit router: Specify the ID of the Enterprise Edition transit router.
`CompletableFuture<ListTransitRouterVpcAttachmentsResponse>`	`listTransitRouterVpcAttachments(ListTransitRouterVpcAttachmentsRequest request)` description : You can use the following methods to query VPC connections on an Enterprise Edition transit router: Specify the ID of the Enterprise Edition transit router.
`CompletableFuture<ListTransitRouterVpnAttachmentsResponse>`	`listTransitRouterVpnAttachments(ListTransitRouterVpnAttachmentsRequest request)` description : You can use the following methods to call the ListTransitRouterVpnAttachments operation: Specify only the TransitRouterAttachmentId parameter to query the information about a VPN attachment.
`CompletableFuture<ModifyCenAttributeResponse>`	`modifyCenAttribute(ModifyCenAttributeRequest request)` description : ModifyCenAttribute* is an asynchronous operation.
`CompletableFuture<ModifyCenBandwidthPackageAttributeResponse>`	`modifyCenBandwidthPackageAttribute(ModifyCenBandwidthPackageAttributeRequest request)`
`CompletableFuture<ModifyCenBandwidthPackageSpecResponse>`	`modifyCenBandwidthPackageSpec(ModifyCenBandwidthPackageSpecRequest request)`
`CompletableFuture<ModifyCenRouteMapResponse>`	`modifyCenRouteMap(ModifyCenRouteMapRequest request)` description : `ModifyCenRouteMap` is an asynchronous operation.
`CompletableFuture<ModifyFlowLogAttributeResponse>`	`modifyFlowLogAttribute(ModifyFlowLogAttributeRequest request)` description : `ModifyFlowLogAttribute` is an asynchronous operation.
`CompletableFuture<ModifyTrafficMatchRuleToTrafficMarkingPolicyResponse>`	`modifyTrafficMatchRuleToTrafficMarkingPolicy(ModifyTrafficMatchRuleToTrafficMarkingPolicyRequest request)`
`CompletableFuture<ModifyTransitRouterCidrResponse>`	`modifyTransitRouterCidr(ModifyTransitRouterCidrRequest request)` description : Before you modify the CIDR block of a transit router, we recommend that you read the limits on transit router CIDR blocks.
`CompletableFuture<ModifyTransitRouterMulticastDomainResponse>`	`modifyTransitRouterMulticastDomain(ModifyTransitRouterMulticastDomainRequest request)`
`CompletableFuture<ModifyTransitRouteTableAggregationResponse>`	`modifyTransitRouteTableAggregation(ModifyTransitRouteTableAggregationRequest request)`
`CompletableFuture<MoveResourceGroupResponse>`	`moveResourceGroup(MoveResourceGroupRequest request)` description : By default, CEN instances and bandwidth plans are in the default resource group.
`CompletableFuture<OpenTransitRouterServiceResponse>`	`openTransitRouterService(OpenTransitRouterServiceRequest request)` description : You can call the `OpenTransitRouterService` operation to activate the transit router feature free of charge.
`CompletableFuture<PublishRouteEntriesResponse>`	`publishRouteEntries(PublishRouteEntriesRequest request)` description : The following table describes whether routes of different types are advertised to CEN by default.
`CompletableFuture<RefreshTransitRouteTableAggregationResponse>`	`refreshTransitRouteTableAggregation(RefreshTransitRouteTableAggregationRequest request)`
`CompletableFuture<RegisterTransitRouterMulticastGroupMembersResponse>`	`registerTransitRouterMulticastGroupMembers(RegisterTransitRouterMulticastGroupMembersRequest request)` description : Enterprise Edition transit routers support only elastic network interfaces (ENIs) as multicast members.
`CompletableFuture<RegisterTransitRouterMulticastGroupSourcesResponse>`	`registerTransitRouterMulticastGroupSources(RegisterTransitRouterMulticastGroupSourcesRequest request)` description : You can specify only elastic network interfaces (ENIs) as multicast sources.
`CompletableFuture<RemoveTrafficMatchRuleFromTrafficMarkingPolicyResponse>`	`removeTrafficMatchRuleFromTrafficMarkingPolicy(RemoveTrafficMatchRuleFromTrafficMarkingPolicyRequest request)` description : When you call RemoveTrafficMatchRuleFromTrafficMarkingPolicy, take note of the following rules: * If you specify the ID of a traffic classification rule in the TrafficMarkRuleIds parameter, the specified traffic classification rule is deleted
`CompletableFuture<RemoveTraficMatchRuleFromTrafficMarkingPolicyResponse>`	`removeTraficMatchRuleFromTrafficMarkingPolicy(RemoveTraficMatchRuleFromTrafficMarkingPolicyRequest request)` 已过时。 OpenAPI RemoveTraficMatchRuleFromTrafficMarkingPolicy is deprecated, please use Cbn::2017-09-12::RemoveTrafficMatchRuleFromTrafficMarkingPolicy instead. * @description ### [](#)Precautions The RemoveTraficMatchRuleFromTrafficMarkingPolicy operation is deprecated and will be discontinued soon. To delete a traffic classification rule, call the [RemoveTrafficMatchRuleFromTrafficMarkingPolicy](https://help.aliyun.com/document_detail/452726.html) operation. Maintenance on this document has stopped.
`CompletableFuture<ReplaceTransitRouterRouteTableAssociationResponse>`	`replaceTransitRouterRouteTableAssociation(ReplaceTransitRouterRouteTableAssociationRequest request)`
`CompletableFuture<ResolveAndRouteServiceInCenResponse>`	`resolveAndRouteServiceInCen(ResolveAndRouteServiceInCenRequest request)` description : Cloud services refer to Alibaba Cloud services that use the 100.64.0.0/10 CIDR block to provide services.
`CompletableFuture<RevokeInstanceFromTransitRouterResponse>`	`revokeInstanceFromTransitRouter(RevokeInstanceFromTransitRouterRequest request)` description : `RevokeInstanceFromTransitRouter` can be used to revoke permissions on virtual private clouds (VPCs), virtual border routers (VBRs), IPsec-VPN connections, and Express Connect Router (ECRs) that belong to another Alibaba Cloud account.
`CompletableFuture<RoutePrivateZoneInCenToVpcResponse>`	`routePrivateZoneInCenToVpc(RoutePrivateZoneInCenToVpcRequest request)` description : Alibaba Cloud DNS PrivateZone (PrivateZone) is an Alibaba Cloud private domain name resolution and management service based on Virtual Private Cloud (VPC).
`CompletableFuture<SetCenInterRegionBandwidthLimitResponse>`	`setCenInterRegionBandwidthLimit(SetCenInterRegionBandwidthLimitRequest request)` description : This operation is used to manage bandwidth of inter-region connections only for Basic Edition transit routers.
`CompletableFuture<TagResourcesResponse>`	`tagResources(TagResourcesRequest request)` description : Each tag consists of a tag key and a tag value.
`CompletableFuture<TempUpgradeCenBandwidthPackageSpecResponse>`	`tempUpgradeCenBandwidthPackageSpec(TempUpgradeCenBandwidthPackageSpecRequest request)`
`CompletableFuture<UnassociateCenBandwidthPackageResponse>`	`unassociateCenBandwidthPackage(UnassociateCenBandwidthPackageRequest request)` description : No inter-region connections are configured in the bandwidth plan.
`CompletableFuture<UnroutePrivateZoneInCenToVpcResponse>`	`unroutePrivateZoneInCenToVpc(UnroutePrivateZoneInCenToVpcRequest request)`
`CompletableFuture<UntagResourcesResponse>`	`untagResources(UntagResourcesRequest request)`
`CompletableFuture<UpdateCenInterRegionTrafficQosPolicyAttributeResponse>`	`updateCenInterRegionTrafficQosPolicyAttribute(UpdateCenInterRegionTrafficQosPolicyAttributeRequest request)`
`CompletableFuture<UpdateCenInterRegionTrafficQosQueueAttributeResponse>`	`updateCenInterRegionTrafficQosQueueAttribute(UpdateCenInterRegionTrafficQosQueueAttributeRequest request)`
`CompletableFuture<UpdateTrafficMarkingPolicyAttributeResponse>`	`updateTrafficMarkingPolicyAttribute(UpdateTrafficMarkingPolicyAttributeRequest request)`
`CompletableFuture<UpdateTransitRouterResponse>`	`updateTransitRouter(UpdateTransitRouterRequest request)` description : UpdateTransitRouter* is an asynchronous operation.
`CompletableFuture<UpdateTransitRouterEcrAttachmentAttributeResponse>`	`updateTransitRouterEcrAttachmentAttribute(UpdateTransitRouterEcrAttachmentAttributeRequest request)` description : UpdateTransitRouterEcrAttachmentAttribute is an asynchronous operation.
`CompletableFuture<UpdateTransitRouterPeerAttachmentAttributeResponse>`	`updateTransitRouterPeerAttachmentAttribute(UpdateTransitRouterPeerAttachmentAttributeRequest request)` description : UpdateTransitRouterPeerAttachmentAttribute* is an asynchronous operation.
`CompletableFuture<UpdateTransitRouterRouteEntryResponse>`	`updateTransitRouterRouteEntry(UpdateTransitRouterRouteEntryRequest request)`
`CompletableFuture<UpdateTransitRouterRouteTableResponse>`	`updateTransitRouterRouteTable(UpdateTransitRouterRouteTableRequest request)`
`CompletableFuture<UpdateTransitRouterVbrAttachmentAttributeResponse>`	`updateTransitRouterVbrAttachmentAttribute(UpdateTransitRouterVbrAttachmentAttributeRequest request)` description : UpdateTransitRouterVbrAttachmentAttribute* is an asynchronous operation.
`CompletableFuture<UpdateTransitRouterVpcAttachmentAttributeResponse>`	`updateTransitRouterVpcAttachmentAttribute(UpdateTransitRouterVpcAttachmentAttributeRequest request)` description : UpdateTransitRouterVpcAttachmentAttribute* is an asynchronous operation.
`CompletableFuture<UpdateTransitRouterVpcAttachmentZonesResponse>`	`updateTransitRouterVpcAttachmentZones(UpdateTransitRouterVpcAttachmentZonesRequest request)` description : When you add a zone and a vSwitch for a VPC connection, make sure that the vSwitch has at least one idle IP address.
`CompletableFuture<UpdateTransitRouterVpnAttachmentAttributeResponse>`	`updateTransitRouterVpnAttachmentAttribute(UpdateTransitRouterVpnAttachmentAttributeRequest request)`
`CompletableFuture<WithdrawPublishedRouteEntriesResponse>`	`withdrawPublishedRouteEntries(WithdrawPublishedRouteEntriesRequest request)`

从接口继承的方法 com.aliyun.core.utils.SdkAutoCloseable
close

方法详细资料

builder

static DefaultAsyncClientBuilder builder()

create
```
static AsyncClient create()
```

activeFlowLog
```
CompletableFuture<ActiveFlowLogResponse> activeFlowLog(ActiveFlowLogRequest request)
```
description :
After you create a flow log, it is enabled by default. You can call this operation to enable a disabled flow log.
- ActiveFlowLog is an asynchronous operation. After you send a request, the system returns a request ID and runs the task in the background. You can call the DescribeFlowlogs operation to query the status of a flow log.
  - If a flow log is in the Modifying state, the flow log is being enabled. In this case, you can query the flow log but cannot perform other operations.
  - If a flow log is in the Active state, the flow log is enabled.
参数:

request - the request parameters of ActiveFlowLog ActiveFlowLogRequest

返回:

ActiveFlowLogResponse

addTrafficMatchRuleToTrafficMarkingPolicy
```
CompletableFuture<AddTrafficMatchRuleToTrafficMarkingPolicyResponse> addTrafficMatchRuleToTrafficMarkingPolicy(AddTrafficMatchRuleToTrafficMarkingPolicyRequest request)
```
description :
AddTrafficMatchRuleToTrafficMarkingPolicy* is an asynchronous operation. After you send a request, the system returns a request ID and runs the task in the background. You can call the ListTrafficMarkingPolicies operation to query the status of a traffic classification rule.
- If a traffic classification rule is in the Creating state, the traffic classification rule is being created. In this case, you can query the traffic classification rule but cannot perform other operations.
- If a traffic classification rule is in the Active state, the traffic classification rule is added to the traffic marking policy.
参数:

request - the request parameters of AddTrafficMatchRuleToTrafficMarkingPolicy AddTrafficMatchRuleToTrafficMarkingPolicyRequest

返回:

AddTrafficMatchRuleToTrafficMarkingPolicyResponse

addTraficMatchRuleToTrafficMarkingPolicy
```
@Deprecated
CompletableFuture<AddTraficMatchRuleToTrafficMarkingPolicyResponse> addTraficMatchRuleToTrafficMarkingPolicy(AddTraficMatchRuleToTrafficMarkingPolicyRequest request)
```
已过时。 OpenAPI AddTraficMatchRuleToTrafficMarkingPolicy is deprecated, please use Cbn::2017-09-12::AddTrafficMatchRuleToTrafficMarkingPolicy instead. * @description ### Usage notes The **AddTraficMatchRuleToTrafficMarkingPolicy** operation is deprecated and will be discontinued soon. If you need to add a traffic classification rule to a traffic marking policy, call the [AddTrafficMatchRuleToTrafficMarkingPolicy](https://help.aliyun.com/document_detail/427602.html) operation.

参数:

request - the request parameters of AddTraficMatchRuleToTrafficMarkingPolicy AddTraficMatchRuleToTrafficMarkingPolicyRequest

返回:

AddTraficMatchRuleToTrafficMarkingPolicyResponse

associateCenBandwidthPackage
```
CompletableFuture<AssociateCenBandwidthPackageResponse> associateCenBandwidthPackage(AssociateCenBandwidthPackageRequest request)
```
description :
You can associate multiple bandwidth plans with a CEN instance. However, the pair of areas connected by each bandwidth plan must be unique. For example, if a CEN instance is associated with a bandwidth plan that connects networks in the Chinese mainland, you cannot associate another bandwidth plan that also connects networks in the Chinese mainland with the CEN instance. However, you can associate a bandwidth plan that connects the Chinese mainland to North America with the CEN instance.

参数:

request - the request parameters of AssociateCenBandwidthPackage AssociateCenBandwidthPackageRequest

返回:

AssociateCenBandwidthPackageResponse

associateTransitRouterAttachmentWithRouteTable
```
CompletableFuture<AssociateTransitRouterAttachmentWithRouteTableResponse> associateTransitRouterAttachmentWithRouteTable(AssociateTransitRouterAttachmentWithRouteTableRequest request)
```
description :
After you create a network instance connection on a transit router, you can configure an associated forwarding correlation to associate the network instance connection with the route table of an Enterprise Edition transit router. The Enterprise Edition transit router forwards traffic for the network instance based on the routes in the route table. Before you begin, we recommend that you take note of the following rules:
- Only route tables of Enterprise Edition transit routers support associated forwarding correlations. For more information about the regions and zones that support Enterprise Edition transit routers, see What is CEN?
- Each network instance connection can have an associated forwarding correlation with only one route table of only one Enterprise Edition transit router.
- AssociateTransitRouterAttachmentWithRouteTable is an asynchronous operation. After a request is sent, the system returns a request ID and runs the task in the background. You can call the ListTransitRouterRouteTableAssociations operation to query the status of an associated forwarding correlation.
  - If an associated forwarding correlation is in the Associating state, the associated forwarding correlation is being created. You can query the associated forwarding correlation but cannot perform other operations.
  - If an associated forwarding correlation is in the Active state, the associated forwarding correlation is created.
参数:

request - the request parameters of AssociateTransitRouterAttachmentWithRouteTable AssociateTransitRouterAttachmentWithRouteTableRequest

返回:

AssociateTransitRouterAttachmentWithRouteTableResponse

associateTransitRouterMulticastDomain
```
CompletableFuture<AssociateTransitRouterMulticastDomainResponse> associateTransitRouterMulticastDomain(AssociateTransitRouterMulticastDomainRequest request)
```
description :
- A vSwitch can be associated with only one multicast domain. Make sure that the vSwitch is not associated with other multicast domains. For more information about how to disassociate a vSwitch from a multicast domain, see DisassociateTransitRouterMulticastDomain.
- AssociateTransitRouterMulticastDomain is an asynchronous operation. After a request is sent, the system returns a request ID and runs the task in the background. You can call the ListTransitRouterMulticastDomainAssociations operation to query whether a vSwitch is associated with the specified multicast domain.
  - If the status is Associating, it indicates that the vSwitch is being associated with the specified multicast domain. You can query the vSwitch but cannot perform other operations on the vSwitch.
  - If the status is Associated, the vSwitch is associated with the specified multicast domain.
- The VPC of the vSwitch must be associated with an Enterprise Edition transit router. For more information about how to associate a VPC with an Enterprise Edition transit router, see CreateTransitRouterVpcAttachment.
参数:

request - the request parameters of AssociateTransitRouterMulticastDomain AssociateTransitRouterMulticastDomainRequest

返回:

AssociateTransitRouterMulticastDomainResponse

attachCenChildInstance
```
CompletableFuture<AttachCenChildInstanceResponse> attachCenChildInstance(AttachCenChildInstanceRequest request)
```
description :
CEN allows you to attach a network instance that belongs to another Alibaba Cloud account to your CEN instance. Before you attach the network instance, CEN must acquire permissions to access the network instance that belongs to another Alibaba Cloud account.
- For more information about how to grant CEN permissions on virtual private clouds (VPCs) that belong to another Alibaba Cloud account, see GrantInstanceToCen.
- For more information about how to grant CEN permissions on Cloud Connect Network (CCN) instances that belong to another Alibaba Cloud account, see GrantInstanceToCbn.
- By default, you cannot grant permissions on virtual border routers (VBRs) that belong to another Alibaba Cloud account to a CEN instance. If you need to use this feature, contact your account manager.
参数:

request - the request parameters of AttachCenChildInstance AttachCenChildInstanceRequest

返回:

AttachCenChildInstanceResponse

checkTransitRouterService
```
CompletableFuture<CheckTransitRouterServiceResponse> checkTransitRouterService(CheckTransitRouterServiceRequest request)
```
参数:

request - the request parameters of CheckTransitRouterService CheckTransitRouterServiceRequest

返回:

CheckTransitRouterServiceResponse

createCen
```
CompletableFuture<CreateCenResponse> createCen(CreateCenRequest request)
```
description :
CreateCen* is an asynchronous operation. After you a request is sent, the system returns a request ID and runs the task in the background. You can call DescribeCens to query the status of the task.
- If a CEN instance is in the Creating state, the CEN instance is being created. You can query the CEN instance but cannot perform other operations.
- If a CEN instance is in the Active state, the CEN instance is created.
参数:

request - the request parameters of CreateCen CreateCenRequest

返回:

CreateCenResponse

createCenBandwidthPackage
```
CompletableFuture<CreateCenBandwidthPackageResponse> createCenBandwidthPackage(CreateCenBandwidthPackageRequest request)
```
description :
You must specify the areas to be connected when you create a bandwidth plan. An area contains one or more Alibaba Cloud regions. When you select areas for a bandwidth plan, make sure that the areas contain the regions that you want to connect. For more information about the supported areas and regions, see Purchase a bandwidth plan.
- For more information about the billing rules, see Billing.
- CreateCenBandwidthPackage is an asynchronous operation. After you send a request, the system returns a bandwidth plan instance ID and runs the task in the background. You can call the DescribeCenBandwidthPackages operation to query the status of a bandwidth plan. If a bandwidth plan is in the Idle or InUse state, the bandwidth plan is created.
参数:

request - the request parameters of CreateCenBandwidthPackage CreateCenBandwidthPackageRequest

返回:

CreateCenBandwidthPackageResponse

createCenChildInstanceRouteEntryToAttachment
```
CompletableFuture<CreateCenChildInstanceRouteEntryToAttachmentResponse> createCenChildInstanceRouteEntryToAttachment(CreateCenChildInstanceRouteEntryToAttachmentRequest request)
```
description :
You can add routes only to virtual private clouds (VPCs) or virtual border routers (VBRs) that are connected to an Enterprise Edition transit router.
- By default, the next hop of the routes is the transit router connection, which is the connection between the VBR and the Enterprise Edition transit router. You cannot modify the next hop.
- CreateCenChildInstanceRouteEntryToAttachment is an asynchronous operation. After you send a request, the system returns a request ID and runs the task in the background. You can call the DescribeRouteEntryList operation to query the status of a route.
  - If a route is in the Pending state, the route is being created. You can query the route but cannot perform other operations.
  - If a route is in the Available state, the route is created.
参数:

request - the request parameters of CreateCenChildInstanceRouteEntryToAttachment CreateCenChildInstanceRouteEntryToAttachmentRequest

返回:

CreateCenChildInstanceRouteEntryToAttachmentResponse

createCenChildInstanceRouteEntryToCen
```
CompletableFuture<CreateCenChildInstanceRouteEntryToCenResponse> createCenChildInstanceRouteEntryToCen(CreateCenChildInstanceRouteEntryToCenRequest request)
```
description :
Limits
- By default, the CreateCenChildInstanceRouteEntryToCen operation is unavailable. To call this operation,submit a ticket.
- You cannot add a route entry to an Enterprise Edition transit router by calling the CreateCenChildInstanceRouteEntryToCen operation.
- By default, the next hop of the route entry is the regional gateway of the Cloud Enterprise Network (CEN) instance. You cannot modify the next hop.
参数:

request - the request parameters of CreateCenChildInstanceRouteEntryToCen CreateCenChildInstanceRouteEntryToCenRequest

返回:

CreateCenChildInstanceRouteEntryToCenResponse

createCenInterRegionTrafficQosPolicy
```
CompletableFuture<CreateCenInterRegionTrafficQosPolicyResponse> createCenInterRegionTrafficQosPolicy(CreateCenInterRegionTrafficQosPolicyRequest request)
```
description :
Only inter-region connections created on Enterprise Edition transit routers support QoS policies.
- Traffic scheduling applies only to outbound traffic on Enterprise Edition transit routers. For example, you create an inter-region connection between the China (Hangzhou) and China (Qingdao) regions, and create a QoS policy for the transit router in the China (Hangzhou) region. In this case, the QoS policy can ensure bandwidth for network traffic from the China (Hangzhou) region to the China (Qingdao) region. However, the QoS policy does not apply to network traffic from the China (Qingdao) region to the China (Hangzhou) region.
- CreateCenInterRegionTrafficQosPolicy is an asynchronous operation. After a request is sent, the system returns a request ID and runs the task in the background. You can call the ListCenInterRegionTrafficQosPolicies operation to query the status of the task.
  - If the QoS policy is in the Creating state, the QoS policy is being created. You can query the QoS policy but cannot perform other operations on the QoS policy.
  - If the QoS policy is in the Active state, the QoS policy is created.
Prerequisites

Before you call the CreateCenInterRegionTrafficQosPolicy operation, make sure that the following requirements are met:
- An inter-region connection is created. For more information, see CreateTransitRouterPeerAttachment.
- A traffic marking policy is created. For more information, see CreateTrafficMarkingPolicy.
参数:

request - the request parameters of CreateCenInterRegionTrafficQosPolicy CreateCenInterRegionTrafficQosPolicyRequest

返回:

CreateCenInterRegionTrafficQosPolicyResponse

createCenInterRegionTrafficQosQueue
```
CompletableFuture<CreateCenInterRegionTrafficQosQueueResponse> createCenInterRegionTrafficQosQueue(CreateCenInterRegionTrafficQosQueueRequest request)
```
description :
The CreateCenInterRegionTrafficQosQueue operation is an asynchronous operation. After you send a request, the system returns a request ID and runs the task in the background. You can call the ListCenInterRegionTrafficQosPolicies operation to query the status of the QoS policy to determine the status of the queue. When you call this operation, you must set the TrafficQosPolicyId parameter.
- If a QoS policy is in the Modifying state, the queue is being created. In this case, you can query the QoS policy and queue but cannot perform other operations.
- If a QoS policy is in the Active state, the queue is created.
参数:

request - the request parameters of CreateCenInterRegionTrafficQosQueue CreateCenInterRegionTrafficQosQueueRequest

返回:

CreateCenInterRegionTrafficQosQueueResponse

createCenRouteMap
```
CompletableFuture<CreateCenRouteMapResponse> createCenRouteMap(CreateCenRouteMapRequest request)
```
description :
Routing policies are sorted by priority. A smaller value indicates a higher priority. Each routing policy is a collection of conditional statements and execution statements. Starting from the routing policy with the highest priority, the system matches routes against the match conditions specified by routing policies. If a route meets all the match conditions of a routing policy, the system permits or denies the route based on the action specified in the routing policy. You can also modify the attributes of permitted routes. By default, the system permits routes that meet none of the match conditions. For more information, see Routing policy overview. CreateCenRouteMap is an asynchronous operation. After you send a request, the routing policy ID is returned but the operation is still being performed in the system background. You can call DescribeCenRouteMaps to query the status of a routing policy.
- If a routing policy is in the Creating state, the routing policy is being created. In this case, you can query the routing policy but cannot perform other operations.
- If a routing policy is in the Active state, the routing policy is created.
参数:

request - the request parameters of CreateCenRouteMap CreateCenRouteMapRequest

返回:

CreateCenRouteMapResponse

createFlowlog
```
CompletableFuture<CreateFlowlogResponse> createFlowlog(CreateFlowlogRequest request)
```
description :
Flow logs can be used to capture traffic information about transit routers and network instance connections, including inter-region connections, virtual private cloud (VPC) connections, VPN connections, Express Connect Router (ECR) connections, and virtual border router (VBR) connections. Before you create a flow log, take note of the following items:
- Flow logs are supported only by Enterprise Edition transit routers.
- Flow logs are used to capture information about outbound traffic on transit routers. Information about inbound traffic on transit routers is not captured. For example, an Elastic Compute Service (ECS) instance in the US (Silicon Valley) region accesses an ECS instance in the US (Virginia) region through Cloud Enterprise Network (CEN). After you enable the flow log feature for the transit router in the US (Virginia) region, you can check the log entries about packets sent from the ECS instance in the US (Virginia) region to the ECS instance in the US (Silicon Valley) region. However, packets sent from the ECS instance in the US (Silicon Valley) region to the ECS instance in the US (Virginia) region are not recorded. If you want to record the packets sent from the ECS instance in the US (Silicon Valley) region to the ECS instance in the US (Virginia) region, you must also enable the flow log feature on the transit router that is in the US (Silicon Valley) region.
- If you use a flow log to capture traffic information about VPC connections, the flow log captures information only about traffic on the elastic network interface (ENI) of the transit router. For more information about how to view traffic information about other ENIs in the VPC, see VPC flow log overview.
- CreateFlowLog is an asynchronous operation. After a request is sent, the system returns a request ID and runs the task in the background. You can call the DescribeFlowlogs operation to query the status of a flow log.
  - If the flow log is in the Creating state, the flow log is being created. In this case, you can query the flow log but cannot perform other operations.
  - If the flow log is in the Active state, the flow log is created.
Prerequisites

Required resources are created. For more information about how to create resources, see the following topics:
参数:

request - the request parameters of CreateFlowlog CreateFlowlogRequest

返回:

CreateFlowlogResponse

createTrafficMarkingPolicy
```
CompletableFuture<CreateTrafficMarkingPolicyResponse> createTrafficMarkingPolicy(CreateTrafficMarkingPolicyRequest request)
```
description :
Only Enterprise Edition transit routers support traffic marking policies.
- CreateTrafficMarkingPolicy is an asynchronous operation. After you send a request, the system returns a traffic marking policy ID and runs the task in the background. You can call the ListTrafficMarkingPolicies operation to query the status of a traffic marking policy.
  - If a traffic marking policy is in the Creating state, the traffic marking policy is being created. You can query the traffic marking policy but cannot perform other operations.
  - If a traffic marking policy is in the Active state, the traffic marking policy is created.
参数:

request - the request parameters of CreateTrafficMarkingPolicy CreateTrafficMarkingPolicyRequest

返回:

CreateTrafficMarkingPolicyResponse

createTransitRouteTableAggregation
```
CompletableFuture<CreateTransitRouteTableAggregationResponse> createTransitRouteTableAggregation(CreateTransitRouteTableAggregationRequest request)
```
description :
After you add an aggregate route to a route table of an Enterprise Edition transit router, the transit router advertises its routes only to route tables of associated virtual private clouds (VPCs) and have route synchronization enabled. Perform the following operations before you create an aggregate route. Otherwise, the Enterprise Edition transit router does not advertise routes to VPC route tables:
- Associated forwarding is enabled between the VPCs and the Enterprise Edition transit router. For more information, see AssociateTransitRouterAttachmentWithRouteTable.
- Route synchronization is enabled for the VPCs. For more information, see CreateTransitRouterVpcAttachment.
参数:

request - the request parameters of CreateTransitRouteTableAggregation CreateTransitRouteTableAggregationRequest

返回:

CreateTransitRouteTableAggregationResponse

createTransitRouter
```
CompletableFuture<CreateTransitRouterResponse> createTransitRouter(CreateTransitRouterRequest request)
```
description :
You can call CreateTransitRouter to create an Enterprise Edition transit router. For more information about the regions that support Enterprise Edition transit routers, see What is CEN?
- CreateTransitRouter is an asynchronous operation. After you send a request, the transit router ID is returned but the operation is still being performed in the system background. You can call ListTransitRouters to query the status of an Enterprise Edition transit router.
  - If an Enterprise Edition transit router is in the Creating state, the Enterprise Edition transit router is being created. In this case, you can query the Enterprise Edition transit router but cannot perform other operations.
  - If an Enterprise Edition transit router is in the Active state, the Enterprise Edition transit router is created.
参数:

request - the request parameters of CreateTransitRouter CreateTransitRouterRequest

返回:

CreateTransitRouterResponse

createTransitRouterCidr
```
CompletableFuture<CreateTransitRouterCidrResponse> createTransitRouterCidr(CreateTransitRouterCidrRequest request)
```
description :
You can specify a CIDR block for a transit router. The CIDR block works in a similar way as the CIDR block of the loopback interface on a router. IP addresses within the CIDR block can be assigned to IPsec-VPN connections. For more information, see Transit router CIDR blocks. The CreateTransitRouterCidr operation can be used to create a CIDR block only after you create a transit router. The CIDR block must meet the following requirements:
- Only Enterprise Edition transit routers support custom CIDR blocks.
- For more information, see Limits in transit router CIDR blocks.
- Each transit router supports at most five CIDR blocks. The subnet mask of a CIDR block must be 16 bits to 24 bits in length.
- The following CIDR blocks and their subnets are not supported: 100.64.0.0/10, 224.0.0.0/4, 127.0.0.0/8, and 169.254.0.0/16.
- The CIDR block cannot overlap with the CIDR blocks of the network instances that communicate with each other by using the CEN instance.
- On the same CEN instance, each transit router CIDR block must be unique.
- When you create the first VPN connection after you add a CIDR block for a transit router, three CIDR blocks within the CIDR block are reserved. An IP address is allocated from the remaining CIDR blocks to the IPsec-VPN connection. You can call the ListTransitRouterCidrAllocation operation to query reserved CIDR blocks and IP addresses allocated to network connections.
参数:

request - the request parameters of CreateTransitRouterCidr CreateTransitRouterCidrRequest

返回:

CreateTransitRouterCidrResponse

createTransitRouterEcrAttachment
```
CompletableFuture<CreateTransitRouterEcrAttachmentResponse> createTransitRouterEcrAttachment(CreateTransitRouterEcrAttachmentRequest request)
```
description :
Only Enterprise Edition transit routers support ECR connections.
- The following methods describe how to attach an ECR connection to an Enterprise Edition transit router:
  - If an Enterprise Edition transit router is created in the region, specify the EcrId, RegionId, and TransitRouterId parameters.
  - If no Enterprise Edition transit router is created in the region, specify the EcrId, CenId, and RegionId parameters. An Enterprise Edition transit router is automatically created when you create an ECR connection.
- CreateTransitRouterEcrAttachment is an asynchronous operation. After a request is sent, the system returns a request ID and runs the task in the background. You can call the ListTransitRouterEcrAttachments operation to query the status of an ECR connection.
  - If the ECR connection is in the Attaching state, the ECR connection is being created. In this case, you can query the ECR connection but cannot perform other operations on the ECR connection.
  - If the ECR connection is in the Attached state, the ECR connection is created.
- After you create an ECR connection, the ECR connection is not in route learning or associated forwarding relationships with Enterprise Edition transit routers. After you enable route learning between the ECR connection and an Enterprise Edition transit router, the routes of the ECR are automatically advertised to the route tables of the Enterprise Edition transit router.
- After you create an ECR connection, the routes in the route tables of the Enterprise Edition transit router to which the ECR connection is attached are automatically advertised to the route table of the ECR.
Prerequisite
- The Alibaba Cloud account of the Enterprise Edition transit router and the Alibaba Cloud account of the ECR belong to the same enterprise.
- The Enterprise Edition transit router and ECR can belong to the same Alibaba Cloud account or different Alibaba Cloud accounts. If the Enterprise Edition transit router and ECR belong to different Alibaba Cloud accounts, grant the transit router permissions on the ECR before you can attach the ECR to the transit router. For more information, see Acquire permissions to connect to a network instance that belongs to another account.
- Before you call this operation to attach an ECR connection to an Enterprise Edition transit router, you must call the CreateExpressConnectRouterAssociation operation to create an association between the ECR and transit router. If you call the DeleteTransitRouterEcrAttachment operation to forcefully delete an ECR connection, the association between the ECR connection and Enterprise Edition transit router is deleted.
参数:

request - the request parameters of CreateTransitRouterEcrAttachment CreateTransitRouterEcrAttachmentRequest

返回:

CreateTransitRouterEcrAttachmentResponse

createTransitRouterMulticastDomain
```
CompletableFuture<CreateTransitRouterMulticastDomainResponse> createTransitRouterMulticastDomain(CreateTransitRouterMulticastDomainRequest request)
```
description :
Before you call this operation, read the following rules:
- Make sure that an Enterprise Edition transit router is deployed in the region where you want to create the multicast domain, and the multicast feature is enabled for the Enterprise Edition transit router. For more information, see CreateTransitRouter. If an Enterprise Edition transit router was created before you apply for multicast resources, the transit router does not support multicast. You can delete the transit router and create a new one. For more information about how to delete an Enterprise Edition transit router, see DeleteTransitRouter.
- When you call CreateTransitRouterMulticastDomain, if you set CenId and RegionId, you do not need to set TransitRouterId. If you set TransitRouterId, you do not need to set CenId or RegionId.
参数:

request - the request parameters of CreateTransitRouterMulticastDomain CreateTransitRouterMulticastDomainRequest

返回:

CreateTransitRouterMulticastDomainResponse

createTransitRouterPeerAttachment
```
CompletableFuture<CreateTransitRouterPeerAttachmentResponse> createTransitRouterPeerAttachment(CreateTransitRouterPeerAttachmentRequest request)
```
description :
Enterprise Edition transit routers allow you to allocate bandwidth resources to inter-region connections by using the following methods: * Allocate bandwidth resources from a bandwidth plan: You must purchase a bandwidth plan, and then allocate bandwidth resources from the bandwidth plan to inter-region connections. For more information about how to purchase a bandwidth plan, see CreateCenBandwidthPackage. * Use pay-by-data-transfer bandwidth resources: You can set a maximum bandwidth value for an inter-region connection. Then, you are charged for the amount of data transfer over the connection. For more information, see Inter-region data transfer.
- CreateTransitRouterPeerAttachment is an asynchronous operation. After a request is sent, the system returns a request ID and runs the task in the background. You can call the ListTransitRouterPeerAttachments operation to query the status of an inter-region connection.
  - If the inter-region connection is in the Attaching state, the inter-region connection is being created. In this case, you can query the connection but cannot perform other operations on the connection.
  - If the inter-region connection is in the Attached state, the inter-region connection is created.
参数:

request - the request parameters of CreateTransitRouterPeerAttachment CreateTransitRouterPeerAttachmentRequest

返回:

CreateTransitRouterPeerAttachmentResponse

createTransitRouterPrefixListAssociation
```
CompletableFuture<CreateTransitRouterPrefixListAssociationResponse> createTransitRouterPrefixListAssociation(CreateTransitRouterPrefixListAssociationRequest request)
```
description :
To associate an Enterprise Edition transit router with a route prefix, you must meet the following requirements:
- You are familiar with the limits and route compatibility notes of prefix lists. For more information, see Prefix lists.
- A prefix list is created. For more information, see CreateVpcPrefixList.
- If the prefix list and the Enterprise Edition transit router belong to different Alibaba Cloud accounts, the prefix list is shared with the Alibaba Cloud account that owns the Enterprise Edition transit router. For more information, see Resource sharing and API references for resource sharing.
参数:

request - the request parameters of CreateTransitRouterPrefixListAssociation CreateTransitRouterPrefixListAssociationRequest

返回:

CreateTransitRouterPrefixListAssociationResponse

createTransitRouterRouteEntry
```
CompletableFuture<CreateTransitRouterRouteEntryResponse> createTransitRouterRouteEntry(CreateTransitRouterRouteEntryRequest request)
```
description :
CreateTransitRouterRouteEntry* is an asynchronous operation. After you send a request, the route ID is returned but the operation is still being performed in the system background. You can call ListTransitRouterRouteEntries to query the status of a route.
- If a route is in the Creating state, the route is being created. In this case, you can query the route but cannot perform other operations.
- If a route is in the Active state, the route is created.
参数:

request - the request parameters of CreateTransitRouterRouteEntry CreateTransitRouterRouteEntryRequest

返回:

CreateTransitRouterRouteEntryResponse

createTransitRouterRouteTable
```
CompletableFuture<CreateTransitRouterRouteTableResponse> createTransitRouterRouteTable(CreateTransitRouterRouteTableRequest request)
```
description :
Only Enterprise Edition transit routers support custom route tables. For more information about the regions and zones that support Enterprise Edition transit routers, see What is CEN?
- CreateTransitRouterRouteTable is an asynchronous operation. After you send a request, the route table ID is returned but the operation is still being performed in the system background. You can call ListTransitRouterRouteTables to query the status of a route table.
  - If a route table is in the Creating state, the route table is being created. In this case, you can query the route table but cannot perform other operations.
  - If a route table is in the Active state, the route table is created.
参数:

request - the request parameters of CreateTransitRouterRouteTable CreateTransitRouterRouteTableRequest

返回:

CreateTransitRouterRouteTableResponse

createTransitRouterVbrAttachment
```
CompletableFuture<CreateTransitRouterVbrAttachmentResponse> createTransitRouterVbrAttachment(CreateTransitRouterVbrAttachmentRequest request)
```
description :
For more information about the regions and zones that support Enterprise Edition transit routers, see What is CEN?
- You can use the following methods to create a VBR connection on an Enterprise Edition transit router:
  - If an Enterprise Edition transit router is already created in the region, specify the VbrId, RegionId, and TransitRouterId parameters to create a VBR connection.
  - If no Enterprise Edition transit router is already created in the region, specify the VbrId, CenId, and RegionId parameters to create a VBR connection. When you create a VBR connection, the system automatically creates an Enterprise Edition transit router in the specified region.
- CreateTransitRouterVbrAttachment is an asynchronous operation. After a request is sent, the system returns a request ID and runs the task in the background. You can call ListTransitRouterVbrAttachments to query the status of a VBR connection.
  - If the VBR connection is in the Attaching state, the VBR connection is being created. In this case, you can query the VBR connection but cannot perform other operations.
  - If the VBR connection is in the Attached state, the VBR connection is created.
- The transit router and the VBR must belong to the same Alibaba Cloud account.
- Transit routers can connect to VBRs that belong to the same or a different Alibaba Cloud account. To connect a transit router to a VBR that belongs to a different Alibaba Cloud account, grant permissions on the VBR to the transit router. For more information, see Grant a transit router permissions on a network instance that belongs to another Alibaba Cloud account.
- After you create a VBR connection, it is not in route learning or associated forwarding relationship with transit router route tables by default.
参数:

request - the request parameters of CreateTransitRouterVbrAttachment CreateTransitRouterVbrAttachmentRequest

返回:

CreateTransitRouterVbrAttachmentResponse

createTransitRouterVpcAttachment
```
CompletableFuture<CreateTransitRouterVpcAttachmentResponse> createTransitRouterVpcAttachment(CreateTransitRouterVpcAttachmentRequest request)
```
description :
You can use the following methods to create a VPC connection from an Enterprise Edition transit router: * If an Enterprise Edition transit router is already created in the region where you want to create a VPC connection, configure the VpcId, ZoneMappings.N.VSwitchId, ZoneMappings.N.ZoneId, TransitRouterId, and RegionId parameters. * If no Enterprise Edition transit router is created in the region where you want to create a VPC connection, configure the VpcId, ZoneMappings.N.VSwitchId, ZoneMappings.N.ZoneId, CenId, and RegionId parameters. Then, the system automatically creates an Enterprise Edition transit router in the specified region.
- CreateTransitRouterVpcAttachment is an asynchronous operation. After a request is sent, the system returns a request ID and runs the task in the background. You can call the ListTransitRouterVpcAttachments operation to query the status of a VPC connection.
  - If the VPC connection is in the Attaching state, the VPC connection is being created. You can query the VPC connection but cannot perform other operations.
  - If the VPC connection is in the Attached state, the VPC connection is created.
- By default, route learning and associated forwarding are disabled between transit router route tables and VPC connections.
Prerequisites

Before you call this operation, make sure that the following requirements are met:
- The VPC in the zones of the Enterprise Edition transit router contains at least one vSwitch. Each vSwitch must have at least one idle IP address. For more information, see Regions and zones supported by Enterprise Edition transit routers.
- To connect to a network instance that belongs to another Alibaba Cloud account, you must first acquire the permissions from the account. For more information, see Acquire permissions to connect to a network instance that belongs to another account.
- VPC connections incur fees. Make sure that you understand the billing rules of VPC connections before you create a VPC connection. For more information, see Billing.
参数:

request - the request parameters of CreateTransitRouterVpcAttachment CreateTransitRouterVpcAttachmentRequest

返回:

CreateTransitRouterVpcAttachmentResponse

createTransitRouterVpnAttachment
```
CompletableFuture<CreateTransitRouterVpnAttachmentResponse> createTransitRouterVpnAttachment(CreateTransitRouterVpnAttachmentRequest request)
```
description :
By default, route learning and associated forwarding are disabled between transit router route tables and IPsec-VPN attachments.
- When you call CreateTransitRouterVpnAttachment, if you set CenId and RegionId, you do not need to set TransitRouterId. If you set TransitRouterId and RegionId, you do not need to set CenId.
Prerequisites
- Before you attach an IPsec-VPN connection to a transit router, make sure that at least one IPsec-VPN connection is created in the region where the transit router is deployed. Make sure the IPsec-VPN connection is not associated with a resource. For more information, see CreateVpnAttachment.
- If the IPsec-VPN connection to be attached to the transit router belongs to a different Alibaba Cloud account, make sure that the transit router has obtained the required permissions from the IPsec-VPN connection. For more information, see GrantInstanceToTransitRouter.
参数:

request - the request parameters of CreateTransitRouterVpnAttachment CreateTransitRouterVpnAttachmentRequest

返回:

CreateTransitRouterVpnAttachmentResponse

deactiveFlowLog
```
CompletableFuture<DeactiveFlowLogResponse> deactiveFlowLog(DeactiveFlowLogRequest request)
```
description :
DeactiveFlowLog is an asynchronous operation. After you send a request, the system returns a request ID and runs the task in the background. You can call the DescribeFlowlogs operation to query the status of a flow log.
- If a flow log is in the Modifying state, the flow log is being disabled. You can query the flow log but cannot perform other operations.
- If a flow log is in the Inactive state, the flow log is disabled.
参数:

request - the request parameters of DeactiveFlowLog DeactiveFlowLogRequest

返回:

DeactiveFlowLogResponse

deleteCen
```
CompletableFuture<DeleteCenResponse> deleteCen(DeleteCenRequest request)
```
description :
DeleteCen* is an asynchronous operation. After a request is sent, the system returns a request ID and runs the task in the background. You can call DescribeCens to query the status of a CEN instance.
- If the CEN instance is in the Deleting state, the CEN instance is being deleted. In this case, you can query the CEN instance but cannot perform other operations.
- If the CEN instance cannot be found, the CEN instance is deleted.
Prerequisites

The CEN instance that you want to delete is not associated with a bandwidth plan, and the transit router associated with the CEN instance does not have a network instance connection or a custom route table.
- For more information about how to detach a network instance, see the following topics:
  - DeleteTransitRouterVpcAttachment
  - DeleteTransitRouterVbrAttachment
  - DeleteTransitRouterVpnAttachment
  - DeleteTransitRouterPeerAttachment
    
    For more information about how to detach network instances from a Basic Edition transit router, see DetachCenChildInstance.
- For more information about how to delete custom route tables from an Enterprise Edition transit router, see DeleteTransitRouterRouteTable.
- For more information about how to disassociate a bandwidth plan from a CEN instance, see UnassociateCenBandwidthPackage.
参数:

request - the request parameters of DeleteCen DeleteCenRequest

返回:

DeleteCenResponse

deleteCenBandwidthPackage
```
CompletableFuture<DeleteCenBandwidthPackageResponse> deleteCenBandwidthPackage(DeleteCenBandwidthPackageRequest request)
```
参数:

request - the request parameters of DeleteCenBandwidthPackage DeleteCenBandwidthPackageRequest

返回:

DeleteCenBandwidthPackageResponse

deleteCenChildInstanceRouteEntryToAttachment
```
CompletableFuture<DeleteCenChildInstanceRouteEntryToAttachmentResponse> deleteCenChildInstanceRouteEntryToAttachment(DeleteCenChildInstanceRouteEntryToAttachmentRequest request)
```
description :
You can delete routes only from virtual private clouds (VPCs) and virtual border routers (VBRs) whose next hop is an Enterprise Edition transit router connection, which is the connection to the network instance.
- DeleteCenChildInstanceRouteEntryToAttachment is an asynchronous operation. After you send a request, the system returns a request ID and runs the task in the background. You can call the DescribeRouteEntryList operation to query the status of a route.
  - If a route is in the Deleting state, the route is being deleted. You can query the route but cannot perform other operations.
  - If a route cannot be found, the route is deleted.
参数:

request - the request parameters of DeleteCenChildInstanceRouteEntryToAttachment DeleteCenChildInstanceRouteEntryToAttachmentRequest

返回:

DeleteCenChildInstanceRouteEntryToAttachmentResponse

deleteCenChildInstanceRouteEntryToCen
```
CompletableFuture<DeleteCenChildInstanceRouteEntryToCenResponse> deleteCenChildInstanceRouteEntryToCen(DeleteCenChildInstanceRouteEntryToCenRequest request)
```
description :
Limits
- By default, the DeleteCenChildInstanceRouteEntryToCen operation is unavailable. To call this operation, submit a ticket.
- You cannot delete a route entry from an Enterprise Edition transit router by calling the DeleteCenChildInstanceRouteEntryToCen operation.
参数:

request - the request parameters of DeleteCenChildInstanceRouteEntryToCen DeleteCenChildInstanceRouteEntryToCenRequest

返回:

DeleteCenChildInstanceRouteEntryToCenResponse

deleteCenInterRegionTrafficQosPolicy
```
CompletableFuture<DeleteCenInterRegionTrafficQosPolicyResponse> deleteCenInterRegionTrafficQosPolicy(DeleteCenInterRegionTrafficQosPolicyRequest request)
```
description :
Before you delete a QoS policy, you must delete all queues in the QoS policy except the default queue. For more information, see DeleteCenInterRegionTrafficQosQueue.
- DeleteCenInterRegionTrafficQosPolicy is an asynchronous operation. After you send a request, the system returns a request ID and runs the task in the background. You can call the ListCenInterRegionTrafficQosPolicies operation to query the status of a QoS policy.
  - If a QoS policy is in the Deleting state, the QoS policy is being deleted. You can query the QoS policy but cannot perform other operations.
  - If a QoS policy cannot be found, the QoS policy is deleted.
参数:

request - the request parameters of DeleteCenInterRegionTrafficQosPolicy DeleteCenInterRegionTrafficQosPolicyRequest

返回:

DeleteCenInterRegionTrafficQosPolicyResponse

deleteCenInterRegionTrafficQosQueue
```
CompletableFuture<DeleteCenInterRegionTrafficQosQueueResponse> deleteCenInterRegionTrafficQosQueue(DeleteCenInterRegionTrafficQosQueueRequest request)
```
description :
You cannot delete the default queue.
- DeleteCenInterRegionTrafficQosQueue is an asynchronous operation. After you send a request, the system returns a request ID and runs the task in the background. You can call the ListCenInterRegionTrafficQosPolicies operation to query the status of a queue. If a queue cannot be found, the queue is deleted.
参数:

request - the request parameters of DeleteCenInterRegionTrafficQosQueue DeleteCenInterRegionTrafficQosQueueRequest

返回:

DeleteCenInterRegionTrafficQosQueueResponse

deleteCenRouteMap
```
CompletableFuture<DeleteCenRouteMapResponse> deleteCenRouteMap(DeleteCenRouteMapRequest request)
```
description :
DeleteCenRouteMap is an asynchronous operation. After you send a request, the system returns a request ID and runs the task in the background. You can call the DescribeCenRouteMaps operation to query the status of a routing policy.
- If a routing policy is in the Deleting state, the routing policy is being deleted. You can query the routing policy but cannot perform other operations.
- If a routing policy cannot be found, it is deleted.
参数:

request - the request parameters of DeleteCenRouteMap DeleteCenRouteMapRequest

返回:

DeleteCenRouteMapResponse

deleteFlowlog
```
CompletableFuture<DeleteFlowlogResponse> deleteFlowlog(DeleteFlowlogRequest request)
```
description :
DeleteFlowlog is an asynchronous operation. After you send a request, the system returns a request ID and runs the task in the background. You can call the DescribeFlowlogs operation to query the status of a flow log.
- If a flow log is in the Deleting state, the flow log is being deleted. In this case, you can query the flow log but cannot perform other operations.
- If a flow log cannot be found, the flow log is deleted.
参数:

request - the request parameters of DeleteFlowlog DeleteFlowlogRequest

返回:

DeleteFlowlogResponse

deleteRouteServiceInCen
```
CompletableFuture<DeleteRouteServiceInCenResponse> deleteRouteServiceInCen(DeleteRouteServiceInCenRequest request)
```
description :
DeleteRouteServiceInCen* is an asynchronous operation. After a request is sent, the system returns a request ID and runs the task in the background. If the request parameters are invalid, the system returns a request ID, but the cloud service configuration is not deleted. You can call DescribeRouteServicesInCen to query the status of the task.
- If a cloud service is in the Deleting state, the cloud service configuration is being deleted. In this case, you can only query the cloud service configuration and cannot perform other operations.
- If the specified cloud service configuration cannot be found, the cloud service configuration is deleted.
参数:

request - the request parameters of DeleteRouteServiceInCen DeleteRouteServiceInCenRequest

返回:

DeleteRouteServiceInCenResponse

deleteTrafficMarkingPolicy
```
CompletableFuture<DeleteTrafficMarkingPolicyResponse> deleteTrafficMarkingPolicy(DeleteTrafficMarkingPolicyRequest request)
```
description :
DeleteTrafficMarkingPolicy is an asynchronous operation. After a request is sent, the system returns a request ID and runs the task in the background. You can call the ListTrafficMarkingPolicies operation to query the status of a traffic marking policy. * If a traffic marking policy is in the Deleting state, the traffic marking policy is being deleted. You can query the traffic marking policy but cannot perform other operations. * If a traffic marking policy cannot be found, the traffic marking policy is deleted.
- Before you delete a traffic marking policy, you must delete all traffic classification rules from the policy. For more information, see RemoveTrafficMatchRuleFromTrafficMarkingPolicy.
参数:

request - the request parameters of DeleteTrafficMarkingPolicy DeleteTrafficMarkingPolicyRequest

返回:

DeleteTrafficMarkingPolicyResponse

deleteTransitRouteTableAggregation
```
CompletableFuture<DeleteTransitRouteTableAggregationResponse> deleteTransitRouteTableAggregation(DeleteTransitRouteTableAggregationRequest request)
```
description :
Before you delete an aggregate route, make sure that your network has a redundant route to prevent service interruptions.
- After an aggregate route is deleted, the aggregate route is automatically withdrawn from virtual private clouds (VPCs). Specific routes that fall within the aggregate route are advertised to the VPCs.
参数:

request - the request parameters of DeleteTransitRouteTableAggregation DeleteTransitRouteTableAggregationRequest

返回:

DeleteTransitRouteTableAggregationResponse

deleteTransitRouter
```
CompletableFuture<DeleteTransitRouterResponse> deleteTransitRouter(DeleteTransitRouterRequest request)
```
description :
DeleteTransitRouter* is an asynchronous operation. After you send a request, the request ID is returned but the operation is still being performed in the system background. You can call ListTransitRouters to query the status of a transit router.
- If a transit router is in the Deleting state, the transit router is being deleted. In this case, you can query the transit router but cannot perform other operations.
- If a transit router cannot be found, the transit router is deleted.
Prerequisites

Before you delete a transit router, make sure that the following prerequisites are met:
- No network instance connections are created on the transit router.
  - For more information about how to delete a virtual private cloud (VPC) connection, see DeleteTransitRouterVpcAttachment.
  - For more information about how to delete a virtual border router (VBR) connection, see DeleteTransitRouterVbrAttachment.
  - For more information about how to delete a Cloud Connect Network (CCN) connection, see DetachCenChildInstance.
  - For more information about how to delete a VPN connection, see DeleteTransitRouterVpnAttachment.
  - For more information about how to delete an inter-region connection, see DeleteTransitRouterPeerAttachment.
- No custom route tables are created on the transit router. For more information about how to delete a custom route table, see DeleteTransitRouterRouteTable.
参数:

request - the request parameters of DeleteTransitRouter DeleteTransitRouterRequest

返回:

DeleteTransitRouterResponse

deleteTransitRouterCidr
```
CompletableFuture<DeleteTransitRouterCidrResponse> deleteTransitRouterCidr(DeleteTransitRouterCidrRequest request)
```
description :
If IP addresses within the CIDR block have been allocated to network instances, the CIDR block cannot be deleted.

参数:

request - the request parameters of DeleteTransitRouterCidr DeleteTransitRouterCidrRequest

返回:

DeleteTransitRouterCidrResponse

deleteTransitRouterEcrAttachment
```
CompletableFuture<DeleteTransitRouterEcrAttachmentResponse> deleteTransitRouterEcrAttachment(DeleteTransitRouterEcrAttachmentRequest request)
```
description :
DeleteTransitRouterEcrAttachment is an asynchronous operation. After a request is sent, the system returns a request ID and runs the task in the background. You can call the ListTransitRouterEcrAttachments operation to query the status of an ECR connection. If the ECR connection is in the Detaching state, the ECR connection is being deleted. In this case, you can query the ECR connection but cannot perform other operations on the ECR connection. If the ECR connection cannot be found, the ECR connection is deleted. Before you call the DeleteTransitRouterEcrAttachment operation, make sure that all request parameters are valid. If a request is invalid, a request ID is returned but the ECR connection is not deleted.

参数:

request - the request parameters of DeleteTransitRouterEcrAttachment DeleteTransitRouterEcrAttachmentRequest

返回:

DeleteTransitRouterEcrAttachmentResponse

deleteTransitRouterMulticastDomain
```
CompletableFuture<DeleteTransitRouterMulticastDomainResponse> deleteTransitRouterMulticastDomain(DeleteTransitRouterMulticastDomainRequest request)
```
description :
Before you delete a multicast domain, make sure that the following requirements are met:
- The multicast domain is disassociated from all vSwitches. For more information, see DisassociateTransitRouterMulticastDomain.
- All multicast sources and members are removed from the multicast domain. For more information, see DeregisterTransitRouterMulticastGroupSources and DeregisterTransitRouterMulticastGroupMembers.
- The multicast domain is not added to other multicast domains as a multicast member. If the multicast domain is added to another multicast domain as a multicast member, you must remove the multicast domain from the other multicast domain. For more information, see DeregisterTransitRouterMulticastGroupMembers.
- Make sure all the request parameters are valid. If a request parameter is invalid, a request ID is returned after you call the operation, but the multicast domain is not deleted.
参数:

request - the request parameters of DeleteTransitRouterMulticastDomain DeleteTransitRouterMulticastDomainRequest

返回:

DeleteTransitRouterMulticastDomainResponse

deleteTransitRouterPeerAttachment
```
CompletableFuture<DeleteTransitRouterPeerAttachmentResponse> deleteTransitRouterPeerAttachment(DeleteTransitRouterPeerAttachmentRequest request)
```
description :
DeleteTransitRouterPeerAttachment* is an asynchronous operation. After you send a request, the system returns a request ID and runs the task in the background. You can call ListTransitRouterPeerAttachments to query the status of an inter-region connection.
- If an inter-region connection is in the Detaching state, the inter-region connection is being deleted. You can query the inter-region connection but cannot perform other operations.
- If an inter-region connection cannot be found, the inter-region connection is deleted.
Prerequisites

Before you begin, make sure that the Enterprise Edition transit router that you use to create inter-region connections meets the following prerequisites:
- No associated forwarding correlation is established between the inter-region connection and the route tables of the Enterprise Edition transit router. For more information about how to delete an associated forwarding correlation, see DissociateTransitRouterAttachmentFromRouteTable.
- No route learning correlation is established between the inter-region connection and the route tables of the Enterprise Edition transit router. For more information about how to delete a route learning correlation, see DisableTransitRouterRouteTablePropagation.
- The route tables of the Enterprise Edition transit router do not contain a custom route entry whose next hop is the network instance connection. For more information about how to delete custom routes from route tables of Enterprise Edition transit routers, see DeleteTransitRouterRouteEntry.
- The route table does not contain a route whose next hop is the inter-region connection and that is generated from a prefix list. You can delete routes from a route table by disassociating the route table from the prefix list. For more information, see DeleteTransitRouterPrefixListAssociation.
- No quality of service (QoS) policy is configured for the inter-region connection. For more information about how to delete QoS policies, see DeleteCenInterRegionTrafficQosPolicy.
参数:

request - the request parameters of DeleteTransitRouterPeerAttachment DeleteTransitRouterPeerAttachmentRequest

返回:

DeleteTransitRouterPeerAttachmentResponse

deleteTransitRouterPrefixListAssociation
```
CompletableFuture<DeleteTransitRouterPrefixListAssociationResponse> deleteTransitRouterPrefixListAssociation(DeleteTransitRouterPrefixListAssociationRequest request)
```
description :
After you disassociate a route table of an Enterprise Edition transit router from a prefix list, the routes that point to the CIDR blocks in the prefix list are automatically withdrawn from the route table. Before you disassociate the route table of an Enterprise Edition transit router from a prefix list, you must migrate workloads that use the routes in case services are interrupted.

参数:

request - the request parameters of DeleteTransitRouterPrefixListAssociation DeleteTransitRouterPrefixListAssociationRequest

返回:

DeleteTransitRouterPrefixListAssociationResponse

deleteTransitRouterRouteEntry
```
CompletableFuture<DeleteTransitRouterRouteEntryResponse> deleteTransitRouterRouteEntry(DeleteTransitRouterRouteEntryRequest request)
```
description :
Before you call this operation, take note of the following items:
- If you specify the TransitRouterRouteEntryId parameter to delete a specific route, you do not need to configure the TransitRouterRouteTableId or TransitRouterRouteEntryDestinationCidrBlock. Otherwise, parameter conflicts occur.
- If you do not specify the TransitRouterRouteEntryId parameter, configure the following parameters based on the next hop type of the route that you want to delete:
  - To delete a blackhole route, configure the following parameters: TransitRouterRouteTableId, TransitRouterRouteEntryDestinationCidrBlock, and TransitRouterRouteEntryNextHopType.
  - To delete routes other than blackhole routes, configure the following parameters: TransitRouterRouteTableId, TransitRouterRouteEntryDestinationCidrBlock, TransitRouterRouteEntryNextHopType, and TransitRouterRouteEntryNextHopId.
- DeleteTransitRouterRouteEntry is an asynchronous operation. After a request is sent, the system returns a request ID and runs the task in the background. You can call the ListTransitRouterRouteEntries operation to query the status of a route entry.
  - If the route entry is in the Deleting state, the route entry is being deleted. In this case, you can query the route entry but cannot perform other operations.
  - If a route entry cannot be found, it is deleted.
Limits

You can call this operation to delete only static routes. Automatically learned routes are not supported. You can call the ListTransitRouterRouteEntries operation to query route types.
参数:

request - the request parameters of DeleteTransitRouterRouteEntry DeleteTransitRouterRouteEntryRequest

返回:

DeleteTransitRouterRouteEntryResponse

deleteTransitRouterRouteTable
```
CompletableFuture<DeleteTransitRouterRouteTableResponse> deleteTransitRouterRouteTable(DeleteTransitRouterRouteTableRequest request)
```
description :
You cannot delete the default route table of an Enterprise Edition transit router.
- DeleteTransitRouterRouteTable is an asynchronous operation. After you send a request, the system returns a request ID and runs the task in the background. You can call the ListTransitRouterRouteTables operation to query the status of a custom route table.
  - If a custom route table is in the Deleting state, the custom route table is being deleted. In this case, you can query the custom route table but cannot perform other operations.
  - If a custom route table cannot be found, the custom route table is deleted.
参数:

request - the request parameters of DeleteTransitRouterRouteTable DeleteTransitRouterRouteTableRequest

返回:

DeleteTransitRouterRouteTableResponse

deleteTransitRouterVbrAttachment
```
CompletableFuture<DeleteTransitRouterVbrAttachmentResponse> deleteTransitRouterVbrAttachment(DeleteTransitRouterVbrAttachmentRequest request)
```
description :
DeleteTransitRouterVbrAttachment* is an asynchronous operation. After you send a request, the system returns a request ID and runs the task in the background. You can call the ListTransitRouterVbrAttachments operation to query the status of a VBR connection.
- If a VBR connection is in the Detaching state, the VBR connection is being deleted. You can query the VBR connection but cannot perform other operations.
- If a VBR connection cannot be found, the VBR connection is deleted.
Prerequisites

Before you delete a VBR connection for an Enterprise Edition transit router, make sure that the following requirements are met:
- No associated forwarding correlation is established between the VBR connection and the route tables of the Enterprise Edition transit router. For more information about how to delete an associated forwarding correlation, see DissociateTransitRouterAttachmentFromRouteTable.
- No route learning correlation is established between the VBR connection and the route tables of the Enterprise Edition transit router. For more information about how to delete a route learning correlation, see DisableTransitRouterRouteTablePropagation.
- The route tables of the Enterprise Edition transit router do not contain a custom route entry whose next hop is the network instance connection. For more information about how to delete custom route entries, see DeleteTransitRouterRouteEntry.
- The route tables of the Enterprise Edition transit router do not contain a route whose next hop is the VBR connection and that is generated from a prefix list. You can delete such routes by disassociating the route table from the prefix list. For more information, see DeleteTransitRouterPrefixListAssociation.
参数:

request - the request parameters of DeleteTransitRouterVbrAttachment DeleteTransitRouterVbrAttachmentRequest

返回:

DeleteTransitRouterVbrAttachmentResponse

deleteTransitRouterVpcAttachment
```
CompletableFuture<DeleteTransitRouterVpcAttachmentResponse> deleteTransitRouterVpcAttachment(DeleteTransitRouterVpcAttachmentRequest request)
```
description :
DeleteTransitRouterVpcAttachment* is an asynchronous operation. After you send a request, the system returns a request ID and runs the task in the background. You can call the ListTransitRouterVpcAttachments operation to query the status of a VPC connection.
- If a VPC connection is in the Detaching state, the VPC connection is being deleted. You can query the VPC connection but cannot perform other operations.
- If a VPC connection cannot be found, it is deleted.
Prerequisites

Before you delete a VPC connection, make sure that the following requirements are met:
- No associated forwarding correlation is established between the VPC connection and the route tables of the Enterprise Edition transit router. For more information about how to delete an associated forwarding correlation, see DissociateTransitRouterAttachmentFromRouteTable.
- No route learning correlation is established between the VPC connection and the route tables of the Enterprise Edition transit router. For more information about how to delete a route learning correlation, see DisableTransitRouterRouteTablePropagation.
- The route table of the VPC does not contain routes that point to the VPC connection. For more information about how to delete routes from a VPC route table, see DeleteRouteEntry.
- The route tables of the Enterprise Edition transit router do not contain a custom route entry whose next hop is the network instance connection. For more information about how to delete custom routes from the route tables of an Enterprise Edition transit router, see DeleteTransitRouterRouteEntry.
- The route tables of the Enterprise Edition transit router do not contain a route that is generated from a prefix list and the next hop is the VPC connection. You can delete such routes by disassociating the route table from the prefix list. For more information, see DeleteTransitRouterPrefixListAssociation.
参数:

request - the request parameters of DeleteTransitRouterVpcAttachment DeleteTransitRouterVpcAttachmentRequest

返回:

DeleteTransitRouterVpcAttachmentResponse

deleteTransitRouterVpnAttachment
```
CompletableFuture<DeleteTransitRouterVpnAttachmentResponse> deleteTransitRouterVpnAttachment(DeleteTransitRouterVpnAttachmentRequest request)
```
description :
Before you call the DeleteTransitRouterVpnAttachment operation, make sure that all request parameters are valid. If a request parameter is invalid, a request ID is returned, but the VPN attachment is not deleted.

参数:

request - the request parameters of DeleteTransitRouterVpnAttachment DeleteTransitRouterVpnAttachmentRequest

返回:

DeleteTransitRouterVpnAttachmentResponse

deregisterTransitRouterMulticastGroupMembers
```
CompletableFuture<DeregisterTransitRouterMulticastGroupMembersResponse> deregisterTransitRouterMulticastGroupMembers(DeregisterTransitRouterMulticastGroupMembersRequest request)
```
description :
DeregisterTransitRouterMulticastGroupMembers is an asynchronous operation. After a request is sent, the system returns a request ID and runs the task in the background. You can call the ListTransitRouterMulticastGroups operation to query the status of a multicast member.
- If the multicast member is in the Deregistering state, the multicast member is being removed. In this case, you can query the multicast member but cannot perform other operations on the multicast member.
- If a multicast member cannot be found, the multicast member is removed from the multicast group.`` Before you call the DeregisterTransitRouterMulticastGroupMembers operation, make sure that all request parameters are valid. If a request parameter is invalid, a request ID is returned but the multicast member is not removed.
参数:

request - the request parameters of DeregisterTransitRouterMulticastGroupMembers DeregisterTransitRouterMulticastGroupMembersRequest

返回:

DeregisterTransitRouterMulticastGroupMembersResponse

deregisterTransitRouterMulticastGroupSources
```
CompletableFuture<DeregisterTransitRouterMulticastGroupSourcesResponse> deregisterTransitRouterMulticastGroupSources(DeregisterTransitRouterMulticastGroupSourcesRequest request)
```
description :
DeregisterTransitRouterMulticastGroupSources is an asynchronous operation. After a request a sent, the system returns a request ID and runs the task in the background. You can call the ListTransitRouterMulticastGroups operation to query the status of a multicast source.
- If a multicast source is in the Deregistering state, the multicast source is being deleted. You can query the multicast source but cannot perform other operations.
- If a multicast source cannot be found, the multicast source is deleted. Before you call DeregisterTransitRouterMulticastGroupSources, make sure that all the request parameters are valid. If a request parameter is invalid, a request ID is returned but the multicast source is not deleted.
参数:

request - the request parameters of DeregisterTransitRouterMulticastGroupSources DeregisterTransitRouterMulticastGroupSourcesRequest

返回:

DeregisterTransitRouterMulticastGroupSourcesResponse

describeCenAttachedChildInstanceAttribute
```
CompletableFuture<DescribeCenAttachedChildInstanceAttributeResponse> describeCenAttachedChildInstanceAttribute(DescribeCenAttachedChildInstanceAttributeRequest request)
```
参数:

request - the request parameters of DescribeCenAttachedChildInstanceAttribute DescribeCenAttachedChildInstanceAttributeRequest

返回:

DescribeCenAttachedChildInstanceAttributeResponse

describeCenAttachedChildInstances
```
CompletableFuture<DescribeCenAttachedChildInstancesResponse> describeCenAttachedChildInstances(DescribeCenAttachedChildInstancesRequest request)
```
description :
You can use one of the following methods to query the information about the network instances that are attached to a CEN instance:
- You can query all the network instances that are attached to a CEN instance by setting the CenId parameter.
- You can query the network instances that are attached to a CEN instance in a specified region by setting the CenId and ChildInstanceRegionId parameters.
- You can query a specified type of network instances that are attached to a CEN instance by setting the CenId and ChildInstanceType parameters.
参数:

request - the request parameters of DescribeCenAttachedChildInstances DescribeCenAttachedChildInstancesRequest

返回:

DescribeCenAttachedChildInstancesResponse

describeCenBandwidthPackages
```
CompletableFuture<DescribeCenBandwidthPackagesResponse> describeCenBandwidthPackages(DescribeCenBandwidthPackagesRequest request)
```
参数:

request - the request parameters of DescribeCenBandwidthPackages DescribeCenBandwidthPackagesRequest

返回:

DescribeCenBandwidthPackagesResponse

describeCenChildInstanceRouteEntries
```
CompletableFuture<DescribeCenChildInstanceRouteEntriesResponse> describeCenChildInstanceRouteEntries(DescribeCenChildInstanceRouteEntriesRequest request)
```
参数:

request - the request parameters of DescribeCenChildInstanceRouteEntries DescribeCenChildInstanceRouteEntriesRequest

返回:

DescribeCenChildInstanceRouteEntriesResponse

describeCenGeographicSpanRemainingBandwidth
```
CompletableFuture<DescribeCenGeographicSpanRemainingBandwidthResponse> describeCenGeographicSpanRemainingBandwidth(DescribeCenGeographicSpanRemainingBandwidthRequest request)
```
参数:

request - the request parameters of DescribeCenGeographicSpanRemainingBandwidth DescribeCenGeographicSpanRemainingBandwidthRequest

返回:

DescribeCenGeographicSpanRemainingBandwidthResponse

describeCenGeographicSpans
```
CompletableFuture<DescribeCenGeographicSpansResponse> describeCenGeographicSpans(DescribeCenGeographicSpansRequest request)
```
参数:

request - the request parameters of DescribeCenGeographicSpans DescribeCenGeographicSpansRequest

返回:

DescribeCenGeographicSpansResponse

describeCenInterRegionBandwidthLimits
```
CompletableFuture<DescribeCenInterRegionBandwidthLimitsResponse> describeCenInterRegionBandwidthLimits(DescribeCenInterRegionBandwidthLimitsRequest request)
```
参数:

request - the request parameters of DescribeCenInterRegionBandwidthLimits DescribeCenInterRegionBandwidthLimitsRequest

返回:

DescribeCenInterRegionBandwidthLimitsResponse

describeCenPrivateZoneRoutes
```
CompletableFuture<DescribeCenPrivateZoneRoutesResponse> describeCenPrivateZoneRoutes(DescribeCenPrivateZoneRoutesRequest request)
```
参数:

request - the request parameters of DescribeCenPrivateZoneRoutes DescribeCenPrivateZoneRoutesRequest

返回:

DescribeCenPrivateZoneRoutesResponse

describeCenRegionDomainRouteEntries
```
CompletableFuture<DescribeCenRegionDomainRouteEntriesResponse> describeCenRegionDomainRouteEntries(DescribeCenRegionDomainRouteEntriesRequest request)
```
参数:

request - the request parameters of DescribeCenRegionDomainRouteEntries DescribeCenRegionDomainRouteEntriesRequest

返回:

DescribeCenRegionDomainRouteEntriesResponse

describeCenRouteMaps
```
CompletableFuture<DescribeCenRouteMapsResponse> describeCenRouteMaps(DescribeCenRouteMapsRequest request)
```
参数:

request - the request parameters of DescribeCenRouteMaps DescribeCenRouteMapsRequest

返回:

DescribeCenRouteMapsResponse

describeCenVbrHealthCheck
```
CompletableFuture<DescribeCenVbrHealthCheckResponse> describeCenVbrHealthCheck(DescribeCenVbrHealthCheckRequest request)
```
参数:

request - the request parameters of DescribeCenVbrHealthCheck DescribeCenVbrHealthCheckRequest

返回:

DescribeCenVbrHealthCheckResponse

describeCens
```
CompletableFuture<DescribeCensResponse> describeCens(DescribeCensRequest request)
```
参数:

request - the request parameters of DescribeCens DescribeCensRequest

返回:

DescribeCensResponse

describeChildInstanceRegions
```
CompletableFuture<DescribeChildInstanceRegionsResponse> describeChildInstanceRegions(DescribeChildInstanceRegionsRequest request)
```
description :
The regions that support CEN vary based on the network instance type. To query the regions where you can attach a specified type of network instance to CEN, set the ProductType parameter. If you do not set the ProductType parameter, the system queries all regions in which you can attach network instances to CEN, regardless of the network instance type.

参数:

request - the request parameters of DescribeChildInstanceRegions DescribeChildInstanceRegionsRequest

返回:

DescribeChildInstanceRegionsResponse

describeFlowlogs
```
CompletableFuture<DescribeFlowlogsResponse> describeFlowlogs(DescribeFlowlogsRequest request)
```
参数:

request - the request parameters of DescribeFlowlogs DescribeFlowlogsRequest

返回:

DescribeFlowlogsResponse

describeGeographicRegionMembership
```
CompletableFuture<DescribeGeographicRegionMembershipResponse> describeGeographicRegionMembership(DescribeGeographicRegionMembershipRequest request)
```
参数:

request - the request parameters of DescribeGeographicRegionMembership DescribeGeographicRegionMembershipRequest

返回:

DescribeGeographicRegionMembershipResponse

describeGrantRulesToCen
```
CompletableFuture<DescribeGrantRulesToCenResponse> describeGrantRulesToCen(DescribeGrantRulesToCenRequest request)
```
description :
Before you call the DescribeGrantRulesToCen operation, make sure that all request parameters are valid. If a request parameter is invalid, a request ID is returned, but the network instances are not returned.

参数:

request - the request parameters of DescribeGrantRulesToCen DescribeGrantRulesToCenRequest

返回:

DescribeGrantRulesToCenResponse

describeGrantRulesToResource
```
CompletableFuture<DescribeGrantRulesToResourceResponse> describeGrantRulesToResource(DescribeGrantRulesToResourceRequest request)
```
参数:

request - the request parameters of DescribeGrantRulesToResource DescribeGrantRulesToResourceRequest

返回:

DescribeGrantRulesToResourceResponse

describePublishedRouteEntries
```
CompletableFuture<DescribePublishedRouteEntriesResponse> describePublishedRouteEntries(DescribePublishedRouteEntriesRequest request)
```
参数:

request - the request parameters of DescribePublishedRouteEntries DescribePublishedRouteEntriesRequest

返回:

DescribePublishedRouteEntriesResponse

describeRouteConflict
```
CompletableFuture<DescribeRouteConflictResponse> describeRouteConflict(DescribeRouteConflictRequest request)
```
参数:

request - the request parameters of DescribeRouteConflict DescribeRouteConflictRequest

返回:

DescribeRouteConflictResponse

describeRouteServicesInCen
```
CompletableFuture<DescribeRouteServicesInCenResponse> describeRouteServicesInCen(DescribeRouteServicesInCenRequest request)
```
参数:

request - the request parameters of DescribeRouteServicesInCen DescribeRouteServicesInCenRequest

返回:

DescribeRouteServicesInCenResponse

describeTransitRouteTableAggregation
```
CompletableFuture<DescribeTransitRouteTableAggregationResponse> describeTransitRouteTableAggregation(DescribeTransitRouteTableAggregationRequest request)
```
description :
You can specify the values of the TransitRouteTableId and TransitRouteTableAggregationCidr parameters to query a specified aggregate route. If you specify only the TransitRouteTableId parameter, all aggregated routes in the route table are queried.

参数:

request - the request parameters of DescribeTransitRouteTableAggregation DescribeTransitRouteTableAggregationRequest

返回:

DescribeTransitRouteTableAggregationResponse

describeTransitRouteTableAggregationDetail
```
CompletableFuture<DescribeTransitRouteTableAggregationDetailResponse> describeTransitRouteTableAggregationDetail(DescribeTransitRouteTableAggregationDetailRequest request)
```
参数:

request - the request parameters of DescribeTransitRouteTableAggregationDetail DescribeTransitRouteTableAggregationDetailRequest

返回:

DescribeTransitRouteTableAggregationDetailResponse

detachCenChildInstance
```
CompletableFuture<DetachCenChildInstanceResponse> detachCenChildInstance(DetachCenChildInstanceRequest request)
```
参数:

request - the request parameters of DetachCenChildInstance DetachCenChildInstanceRequest

返回:

DetachCenChildInstanceResponse

disableCenVbrHealthCheck
```
CompletableFuture<DisableCenVbrHealthCheckResponse> disableCenVbrHealthCheck(DisableCenVbrHealthCheckRequest request)
```
description :
DisableCenVbrHealthCheck* is an asynchronous operation. After you send a request, the system returns a request ID and runs the task in the background. You can call the DescribeCenVbrHealthCheck operation to query the status of health check configurations. If the health check configurations cannot be found, the health check configurations are deleted.

参数:

request - the request parameters of DisableCenVbrHealthCheck DisableCenVbrHealthCheckRequest

返回:

DisableCenVbrHealthCheckResponse

disableTransitRouterRouteTablePropagation
```
CompletableFuture<DisableTransitRouterRouteTablePropagationResponse> disableTransitRouterRouteTablePropagation(DisableTransitRouterRouteTablePropagationRequest request)
```
description :
DisableTransitRouterRouteTablePropagation* is an synchronous operation. After you send a request, the system returns a request ID and runs the task in the background. You can call the ListTransitRouterRouteTablePropagations operation to query the status of a route learning correlation.
- If a route learning correlation is in the Disabling state, the route learning correlation is being deleted. You can query the route learning correlation but cannot perform other operations.
- If a route learning correlation cannot be found, the route learning correlation is deleted.
参数:

request - the request parameters of DisableTransitRouterRouteTablePropagation DisableTransitRouterRouteTablePropagationRequest

返回:

DisableTransitRouterRouteTablePropagationResponse

disassociateTransitRouterMulticastDomain
```
CompletableFuture<DisassociateTransitRouterMulticastDomainResponse> disassociateTransitRouterMulticastDomain(DisassociateTransitRouterMulticastDomainRequest request)
```
description :
Before you delete a vSwitch from a multicast domain, make sure that the vSwitch does not contain a multicast source or a multicast member. For more information about how to remove a multicast source or member from a vSwitch, see DeregisterTransitRouterMulticastGroupSources and DeregisterTransitRouterMulticastGroupMembers.
- If a request parameter is invalid, the system returns a request ID but does not disassociate the vSwitch from the multicast domain.
- DisassociateTransitRouterMulticastDomain is an asynchronous operation. After a request is sent, the system returns a request ID and runs the task in the background. You can call the ListTransitRouterMulticastDomainAssociations operation to query whether a vSwitch is disassociated from the specified multicast domain.
  - If the status is Dissociating, it indicates that the vSwitch is being disassociated from the specified multicast domain. You can query the vSwitch but cannot perform other operations on the vSwitch.
  - If the vSwitch cannot be found, the vSwitch is disassociated from the multicast domain.
参数:

request - the request parameters of DisassociateTransitRouterMulticastDomain DisassociateTransitRouterMulticastDomainRequest

返回:

DisassociateTransitRouterMulticastDomainResponse

dissociateTransitRouterAttachmentFromRouteTable
```
CompletableFuture<DissociateTransitRouterAttachmentFromRouteTableResponse> dissociateTransitRouterAttachmentFromRouteTable(DissociateTransitRouterAttachmentFromRouteTableRequest request)
```
description :
DissociateTransitRouterAttachmentFromRouteTable* is an asynchronous operation. After you send a request, the system returns a request ID and runs the task in the background. You can call the ListTransitRouterRouteTableAssociations operation to query an associated forwarding correlation between a network instance connection and a route table.
- If an associated forwarding correlation is in the Dissociating state, the associated forwarding correlation is being deleted. You can query the associated forwarding correlation but cannot perform other operations.
- If an associated forwarding correlation cannot be found, the associated forwarding correlation is deleted.
参数:

request - the request parameters of DissociateTransitRouterAttachmentFromRouteTable DissociateTransitRouterAttachmentFromRouteTableRequest

返回:

DissociateTransitRouterAttachmentFromRouteTableResponse

enableCenVbrHealthCheck
```
CompletableFuture<EnableCenVbrHealthCheckResponse> enableCenVbrHealthCheck(EnableCenVbrHealthCheckRequest request)
```
description :
You can enable the health check feature for a VBR to monitor the Express Connect circuit between your data center and Alibaba Cloud. This helps you detect connection issues in a timely manner. Before you use the health check feature, take note of the following information:
- If your VBR uses static routing, you must add a static route for the data center that is connected to the VBR after you configure the health check feature. Set the destination CIDR block to the source IP address of health checks, set the mask length to 32, and set the next hop to the IP address of the VBR on the Alibaba Cloud side.
- If your VBR uses dynamic Border Gateway Protocol (BGP) routing, you do not need to add routes for the data center.
- EnableCenVbrHealthCheck is an asynchronous operation. After you send a request, the system returns a request ID and runs the task in the background. You can call the DescribeCenVbrHealthCheck operation to query the status of health check configurations. If health check configurations are returned, health check is configured or modified.
参数:

request - the request parameters of EnableCenVbrHealthCheck EnableCenVbrHealthCheckRequest

返回:

EnableCenVbrHealthCheckResponse

enableTransitRouterRouteTablePropagation
```
CompletableFuture<EnableTransitRouterRouteTablePropagationResponse> enableTransitRouterRouteTablePropagation(EnableTransitRouterRouteTablePropagationRequest request)
```
description :
After you establish a network instance connection on a transit router, you can create a route learning correlation for the network instance connection. Then, the routes of the connected network instance are automatically advertised to the route table of the transit router. Before you begin, we recommend that you take note of the following rules:
- You can create route learning correlations only on Enterprise Edition transit routers. For more information about the regions and zones that support Enterprise Edition transit routers, see What is CEN?
- EnableTransitRouterRouteTablePropagation is an asynchronous operation. After you send a request, the system returns a request ID and runs the task in the background. You can call the ListTransitRouterRouteTablePropagations operation to query the route learning status between a network instance connection and a route table.
  - Enabling indicates that a route learning correlation is being created between the network instance connection and route table. You can query the route learning correlation but cannot perform other operations.
  - Active indicates that the route learning correlation is created between the network instance connection and route table.
参数:

request - the request parameters of EnableTransitRouterRouteTablePropagation EnableTransitRouterRouteTablePropagationRequest

返回:

EnableTransitRouterRouteTablePropagationResponse

grantInstanceToTransitRouter
```
CompletableFuture<GrantInstanceToTransitRouterResponse> grantInstanceToTransitRouter(GrantInstanceToTransitRouterRequest request)
```
description :
The GrantInstanceToTransitRouter operation can be used to grant transit routers permissions on network instances that belong to other Alibaba Cloud accounts, including virtual private clouds (VPCs), virtual border routers (VBRs), IPsec-VPN connections, and Express Connect Router (ECRs). To grant transit routers permissions on Cloud Connect Network (CCN) instances, call the GrantInstanceToCbn operation.
- Before you call GrantInstanceToTransitRouter, take note of the billing rules, permission limits, and prerequisites on permission management of transit routers. For more information, see Acquire permissions to connect to a network instance that belongs to another account.
- Before you grant a transit router permissions on a network instance, make sure that the following requirements are met: The account to which the network instance belongs and the account to which the transit router belongs are of the same type. The ID of the Alibaba Cloud account to which the transit router belongs is obtained. The ID of the Cloud Enterprise Network (CEN) instance to which the Enterprise Edition transit router belongs is obtained. Before you grant a transit router permissions on a VBR, contact your account manager to acquire permissions on the VBR. Before you grant a transit router permissions on an IPsec-VPN connection, make sure that the IPsec-VPN connection is not associated with a resource. If the IPsec-VPN connection is attached to a VPN gateway, the IPsec-VPN connection cannot be attached to transit routers within the same account or different accounts. If the IPsec-VPN connection is attached to a transit router, detach the IPsec-VPN connection from the transit router. For more information, see Delete a network instance connection.
参数:

request - the request parameters of GrantInstanceToTransitRouter GrantInstanceToTransitRouterRequest

返回:

GrantInstanceToTransitRouterResponse

listCenChildInstanceRouteEntriesToAttachment
```
CompletableFuture<ListCenChildInstanceRouteEntriesToAttachmentResponse> listCenChildInstanceRouteEntriesToAttachment(ListCenChildInstanceRouteEntriesToAttachmentRequest request)
```
description :
Before you call the ListCenChildInstanceRouteEntriesToAttachment operation, make sure that all request parameter values are valid. If a parameter is set to an invalid value, a request ID is returned, but the routes to the network instance are not returned.

参数:

request - the request parameters of ListCenChildInstanceRouteEntriesToAttachment ListCenChildInstanceRouteEntriesToAttachmentRequest

返回:

ListCenChildInstanceRouteEntriesToAttachmentResponse

listCenInterRegionTrafficQosPolicies
```
CompletableFuture<ListCenInterRegionTrafficQosPoliciesResponse> listCenInterRegionTrafficQosPolicies(ListCenInterRegionTrafficQosPoliciesRequest request)
```
description :
Before you call the ListCenInterRegionTrafficQosPolicies operation, take note of the following information:
- You must specify at least one of the TransitRouterId and TrafficQosPolicyId parameters.
- If you do not specify a QoS policy ID (TrafficQosPolicyId), the system returns information based on the values of the TransitRouterId, TransitRouterAttachmentId, TrafficQosPolicyName, and TrafficQosPolicyDescription parameters. The information about the queues in the QoS policies is not returned. In this case, the TrafficQosQueues parameter is not included in the response.
- If you specify a QoS policy ID (TrafficQosPolicyId), the system returns the information about the QoS policy and queues in the QoS policy. In this case, the TrafficQosQueues parameter is included in the response. If the value of the TrafficQosQueues parameter is an empty string, it indicates that the QoS policy contains only the default queue.
- Make sure that all the request parameters are valid. If a request parameter is invalid, a request ID is returned but the information about the QoS policy is not returned.
参数:

request - the request parameters of ListCenInterRegionTrafficQosPolicies ListCenInterRegionTrafficQosPoliciesRequest

返回:

ListCenInterRegionTrafficQosPoliciesResponse

listCenInterRegionTrafficQosQueues
```
CompletableFuture<ListCenInterRegionTrafficQosQueuesResponse> listCenInterRegionTrafficQosQueues(ListCenInterRegionTrafficQosQueuesRequest request)
```
description :
You must specify at least one of the TransitRouterId, TrafficQosPolicyId, and TrafficQosQueueId parameters. Make sure that all the request parameters are valid. If a request parameter is invalid, a request ID is returned but the QoS queue information is not returned.

参数:

request - the request parameters of ListCenInterRegionTrafficQosQueues ListCenInterRegionTrafficQosQueuesRequest

返回:

ListCenInterRegionTrafficQosQueuesResponse

listGrantVSwitchEnis
```
CompletableFuture<ListGrantVSwitchEnisResponse> listGrantVSwitchEnis(ListGrantVSwitchEnisRequest request)
```
description :
Before you call ListGrantVSwitchEnis, make sure that the VPC is attached to a Cloud Enterprise Network (CEN) instance. For more information, see CreateTransitRouterVpcAttachment.

参数:

request - the request parameters of ListGrantVSwitchEnis ListGrantVSwitchEnisRequest

返回:

ListGrantVSwitchEnisResponse

listGrantVSwitchesToCen
```
CompletableFuture<ListGrantVSwitchesToCenResponse> listGrantVSwitchesToCen(ListGrantVSwitchesToCenRequest request)
```
description :
Before you call the ListGrantVSwitchesToCen operation, make sure that the following requirements are met:
- The permissions on the VPC are granted to the CEN instance. For more information, see GrantInstanceToCen.
- The VPC is attached to the CEN instance.
  - For more information about how to connect an Enterprise Edition transit router to a VPC, see CreateTransitRouterVpcAttachment.
  - For more information about how to connect a Basic Edition transit router to a VPC, see AttachCenChildInstance.
参数:

request - the request parameters of ListGrantVSwitchesToCen ListGrantVSwitchesToCenRequest

返回:

ListGrantVSwitchesToCenResponse

listTagResources
```
CompletableFuture<ListTagResourcesResponse> listTagResources(ListTagResourcesRequest request)
```
description :
To call this operation, you must set at least one of ResourceId.N and Tag.N.Key.
- If you set only ResourceId.N, the tags that are added to the specified CEN instances are returned.
- If you set only Tag.N.Key, the CEN instances that have the specified tags are returned.
- If you set both ResourceId.N and Tag.N.Key, the specified tags that are added to the specified CEN instances are returned.
  - Make sure that the CEN instance specified by ResourceId.N has the tag specified by Tag.N.Key. Otherwise, the response returns null.
  - If multiple tag keys are specified, the logical operator among these tag keys is AND.
参数:

request - the request parameters of ListTagResources ListTagResourcesRequest

返回:

ListTagResourcesResponse

listTrafficMarkingPolicies
```
CompletableFuture<ListTrafficMarkingPoliciesResponse> listTrafficMarkingPolicies(ListTrafficMarkingPoliciesRequest request)
```
description :
Before you call the ListTrafficMarkingPolicies operation, take note of the following limits:
- Specify at least one of the TransitRouterId and TrafficMarkingPolicyId parameters.
- If you do not specify a traffic marking policy ID (TrafficMarkingPolicyId), the operation queries only the information about the traffic marking policy based on the TransitRouterId, TrafficMarkingPolicyName, and TrafficMarkingPolicyDescription parameters. The TrafficMatchRules parameter that contains the information about the traffic classification rules is not returned.
- If you specify a traffic marking policy ID (TrafficMarkingPolicyId), the operation queries the information about the traffic marking policy and traffic classification rules. The TrafficMatchRules parameter is returned in the response. If the value of the TrafficMatchRules parameter is an empty array, the traffic marking policy does not contain a traffic classification rule.
参数:

request - the request parameters of ListTrafficMarkingPolicies ListTrafficMarkingPoliciesRequest

返回:

ListTrafficMarkingPoliciesResponse

listTransitRouterAvailableResource
```
CompletableFuture<ListTransitRouterAvailableResourceResponse> listTransitRouterAvailableResource(ListTransitRouterAvailableResourceRequest request)
```
description :
You can call the ListTransitRouterAvailableResource operation to query the zones that support Enterprise Edition transit routers in a specified region. * If you do not set SupportMulticast to true, general-purpose zones that support Enterprise Edition transit routers are queried. * If you set SupportMulticast to true, zones in which Enterprise Edition transit routers support multicast are queried.
- On May 31, 2022, VPC-connected Enterprise Edition transit routers were optimized. Optimized Enterprise Edition transit routers do not require you to specify the primary and secondary zones when you connect VPCs to the Enterprise Edition transit routers. You can specify one or more zones.
  - If your Enterprise Edition transit router has not been optimized, you must specify the primary and secondary zones when you connect a VPC to your Enterprise Edition transit router. After you call ListTransitRouterAvailableResource, you can call MasterZones and SlaveZones to query the primary and secondary zones.
  - If your Enterprise Edition transit router has been optimized, you can specify a zone as needed when you connect a VPC to your Enterprise Edition transit router. After you call ListTransitRouterAvailableResource, you can call AvailableZones to query the zones. For more information about the optimization, see Announcement: Optimization on VPC-connected Enterprise Edition transit routers.
参数:

request - the request parameters of ListTransitRouterAvailableResource ListTransitRouterAvailableResourceRequest

返回:

ListTransitRouterAvailableResourceResponse

listTransitRouterCidr
```
CompletableFuture<ListTransitRouterCidrResponse> listTransitRouterCidr(ListTransitRouterCidrRequest request)
```
参数:

request - the request parameters of ListTransitRouterCidr ListTransitRouterCidrRequest

返回:

ListTransitRouterCidrResponse

listTransitRouterCidrAllocation
```
CompletableFuture<ListTransitRouterCidrAllocationResponse> listTransitRouterCidrAllocation(ListTransitRouterCidrAllocationRequest request)
```
参数:

request - the request parameters of ListTransitRouterCidrAllocation ListTransitRouterCidrAllocationRequest

返回:

ListTransitRouterCidrAllocationResponse

listTransitRouterEcrAttachments
```
CompletableFuture<ListTransitRouterEcrAttachmentsResponse> listTransitRouterEcrAttachments(ListTransitRouterEcrAttachmentsRequest request)
```
description :
You can use the following methods to query ECR connection information:
- Specify the ID of an Enterprise Edition transit router.
- Specify the ID of an Enterprise Edition transit router and the ID of the region in which the Enterprise Edition transit router is deployed.
- Configure the TransitRouterAttachmentId parameter to specify the ECR connection that you want to query.
参数:

request - the request parameters of ListTransitRouterEcrAttachments ListTransitRouterEcrAttachmentsRequest

返回:

ListTransitRouterEcrAttachmentsResponse

listTransitRouterMulticastDomainAssociations
```
CompletableFuture<ListTransitRouterMulticastDomainAssociationsResponse> listTransitRouterMulticastDomainAssociations(ListTransitRouterMulticastDomainAssociationsRequest request)
```
description :
You must set at least TransitRouterMulticastDomainId and TransitRouterAttachmentId. If you set TransitRouterAttachmentId, the information about the vSwitches in a virtual private cloud (VPC) that are associated with a multicast domain is returned. If you set TransitRouterMulticastDomainId, the information about the vSwitches that are associated with a multicast domain is returned.
- Before you call ListTransitRouterMulticastDomainAssociations, make sure that all the request parameters are valid. If a request parameter is invalid, the system returns a request ID but does not return the vSwitches that are associated with the multicast domain.
参数:

request - the request parameters of ListTransitRouterMulticastDomainAssociations ListTransitRouterMulticastDomainAssociationsRequest

返回:

ListTransitRouterMulticastDomainAssociationsResponse

listTransitRouterMulticastDomainVSwitches
```
CompletableFuture<ListTransitRouterMulticastDomainVSwitchesResponse> listTransitRouterMulticastDomainVSwitches(ListTransitRouterMulticastDomainVSwitchesRequest request)
```
参数:

request - the request parameters of ListTransitRouterMulticastDomainVSwitches ListTransitRouterMulticastDomainVSwitchesRequest

返回:

ListTransitRouterMulticastDomainVSwitchesResponse

listTransitRouterMulticastDomains
```
CompletableFuture<ListTransitRouterMulticastDomainsResponse> listTransitRouterMulticastDomains(ListTransitRouterMulticastDomainsRequest request)
```
description :
If you configure one of the RegionId and CenId parameters, you must configure the other parameter. Otherwise, no information about the multicast domain is returned. You can configure only one of the TransitRouterId and TransitRouterMulticastDomainId parameters.
- Make sure that all the request parameters are valid. If a request parameter is invalid, a request ID is returned but the information about the multicast domain is not returned.
参数:

request - the request parameters of ListTransitRouterMulticastDomains ListTransitRouterMulticastDomainsRequest

返回:

ListTransitRouterMulticastDomainsResponse

listTransitRouterMulticastGroups
```
CompletableFuture<ListTransitRouterMulticastGroupsResponse> listTransitRouterMulticastGroups(ListTransitRouterMulticastGroupsRequest request)
```
description :
You can call the ListTransitRouterMulticastGroups operation to query the multicast sources and members in a multicast domain. Multicast sources and members are also known as multicast resources.
- If you set GroupIpAddress, the system queries multicast resources in the multicast domain by multicast group.
- If you set VSwitchIds, the system queries multicast resources in the multicast domain by vSwitch.
- If you set PeerTransitRouterMulticastDomains, the system queries multicast resources that are also deployed in a different region.
- If you set ResourceType, the system queries the multicast resources of the specified type in the multicast domain.
- If you set ResourceId, the system queries multicast resources by resource.
- If you set only TransitRouterMulticastDomainId, the system queries all the multicast resources in the multicast domain.
参数:

request - the request parameters of ListTransitRouterMulticastGroups ListTransitRouterMulticastGroupsRequest

返回:

ListTransitRouterMulticastGroupsResponse

listTransitRouterPeerAttachments
```
CompletableFuture<ListTransitRouterPeerAttachmentsResponse> listTransitRouterPeerAttachments(ListTransitRouterPeerAttachmentsRequest request)
```
description :
You can use the following methods to query inter-region connections on an Enterprise Edition transit router:
- Query all inter-region connections on an Enterprise Edition transit router by specifying the ID of the Enterprise Edition transit router.
- Query all inter-region connections on an Enterprise Edition transit router by specifying the ID of the Cloud Enterprise Network (CEN) instance and the ID of the region where the transit router is deployed.
参数:

request - the request parameters of ListTransitRouterPeerAttachments ListTransitRouterPeerAttachmentsRequest

返回:

ListTransitRouterPeerAttachmentsResponse

listTransitRouterPrefixListAssociation
```
CompletableFuture<ListTransitRouterPrefixListAssociationResponse> listTransitRouterPrefixListAssociation(ListTransitRouterPrefixListAssociationRequest request)
```
参数:

request - the request parameters of ListTransitRouterPrefixListAssociation ListTransitRouterPrefixListAssociationRequest

返回:

ListTransitRouterPrefixListAssociationResponse

listTransitRouterRouteEntries
```
CompletableFuture<ListTransitRouterRouteEntriesResponse> listTransitRouterRouteEntries(ListTransitRouterRouteEntriesRequest request)
```
参数:

request - the request parameters of ListTransitRouterRouteEntries ListTransitRouterRouteEntriesRequest

返回:

ListTransitRouterRouteEntriesResponse

listTransitRouterRouteTableAssociations
```
CompletableFuture<ListTransitRouterRouteTableAssociationsResponse> listTransitRouterRouteTableAssociations(ListTransitRouterRouteTableAssociationsRequest request)
```
description :
When you call ListTransitRouterRouteTableAssociations, you must set at least one of TransitRouterRouteTableId and TransitRouterAttachmentId.
- If you set only TransitRouterRouteTableId, the network instance connections that are in associated forwarding correlation with a route table of an Enterprise Edition transit router are queried.
- If you set only TransitRouterAttachmentId, the route table of an Enterprise Edition transit router that is in associated forwarding correlation with a network instance connection is queried.
- If you set both TransitRouterRouteTableId and TransitRouterAttachmentId, the associated forwarding correlations between a specified network instance connection and a specified route table of an Enterprise Edition transit router are queried.
  - If an associated forwarding correlation is created between the network instance connection and the route table of the Enterprise Edition transit router, the information about the associated forwarding correlation is returned.
  - If no associated forwarding correlation is created between the network instance connection and the route table of the Enterprise Edition transit router, TransitRouterAssociations in the response is empty.
参数:

request - the request parameters of ListTransitRouterRouteTableAssociations ListTransitRouterRouteTableAssociationsRequest

返回:

ListTransitRouterRouteTableAssociationsResponse

listTransitRouterRouteTablePropagations
```
CompletableFuture<ListTransitRouterRouteTablePropagationsResponse> listTransitRouterRouteTablePropagations(ListTransitRouterRouteTablePropagationsRequest request)
```
参数:

request - the request parameters of ListTransitRouterRouteTablePropagations ListTransitRouterRouteTablePropagationsRequest

返回:

ListTransitRouterRouteTablePropagationsResponse

listTransitRouterRouteTables
```
CompletableFuture<ListTransitRouterRouteTablesResponse> listTransitRouterRouteTables(ListTransitRouterRouteTablesRequest request)
```
参数:

request - the request parameters of ListTransitRouterRouteTables ListTransitRouterRouteTablesRequest

返回:

ListTransitRouterRouteTablesResponse

listTransitRouterVbrAttachments
```
CompletableFuture<ListTransitRouterVbrAttachmentsResponse> listTransitRouterVbrAttachments(ListTransitRouterVbrAttachmentsRequest request)
```
description :
You can use the following methods to query VBR connections on an Enterprise Edition transit router:
- Specify the ID of the Enterprise Edition transit router.
- Specify the ID of the relevant Cloud Enterprise Network (CEN) instance and the region ID of the Enterprise Edition transit router.
参数:

request - the request parameters of ListTransitRouterVbrAttachments ListTransitRouterVbrAttachmentsRequest

返回:

ListTransitRouterVbrAttachmentsResponse

listTransitRouterVpcAttachments
```
CompletableFuture<ListTransitRouterVpcAttachmentsResponse> listTransitRouterVpcAttachments(ListTransitRouterVpcAttachmentsRequest request)
```
description :
You can use the following methods to query VPC connections on an Enterprise Edition transit router:
- Specify the ID of the Enterprise Edition transit router.
- Specify the ID of the relevant Cloud Enterprise Network (CEN) instance and the region ID of the Enterprise Edition transit router.
- Specify the ID of the region where the Enterprise Edition transit router is deployed.
参数:

request - the request parameters of ListTransitRouterVpcAttachments ListTransitRouterVpcAttachmentsRequest

返回:

ListTransitRouterVpcAttachmentsResponse

listTransitRouterVpnAttachments
```
CompletableFuture<ListTransitRouterVpnAttachmentsResponse> listTransitRouterVpnAttachments(ListTransitRouterVpnAttachmentsRequest request)
```
description :
You can use the following methods to call the ListTransitRouterVpnAttachments operation:
- Specify only the TransitRouterAttachmentId parameter to query the information about a VPN attachment.
- Specify only the TransitRouterId parameter to query the information about all VPN attachments on a transit router.
- Specify the CenId and RegionId parameter to query the information about VPN attachments in a specified region. Before you call the ListTransitRouterVpnAttachments operation, make sure that all request parameters are valid. If a request parameter is invalid, a request ID is returned, but the information about the VPN attachments is not returned.
参数:

request - the request parameters of ListTransitRouterVpnAttachments ListTransitRouterVpnAttachmentsRequest

返回:

ListTransitRouterVpnAttachmentsResponse

listTransitRouters
```
CompletableFuture<ListTransitRoutersResponse> listTransitRouters(ListTransitRoutersRequest request)
```
description :
You can set the RegionId and TransitRouterId parameters based on your requirements.
- If you do not set RegionId or TransitRouterId, the system queries all transit routers that are connected to the specified CEN instance.
- If you set only RegionId, the system queries transit routers that are deployed in the specified region.
- If you set only TransitRouterId, the system queries the specified transit router.
- If you set both RegionId and TransitRouterId, the system queries the specified transit router in the specified region.
参数:

request - the request parameters of ListTransitRouters ListTransitRoutersRequest

返回:

ListTransitRoutersResponse

modifyCenAttribute
```
CompletableFuture<ModifyCenAttributeResponse> modifyCenAttribute(ModifyCenAttributeRequest request)
```
description :
ModifyCenAttribute* is an asynchronous operation. After you send a request, the system returns the request ID but the operation is still being performed in the system background. You can call DescribeCens to query the status of a CEN instance.
- If a CEN instance is in the Modifying state, the CEN instance is being modified. You can query the CEN instance but cannot perform other operations.
- If a CEN instance is in the Active state, the CEN instance is modified.
参数:

request - the request parameters of ModifyCenAttribute ModifyCenAttributeRequest

返回:

ModifyCenAttributeResponse

modifyCenBandwidthPackageAttribute
```
CompletableFuture<ModifyCenBandwidthPackageAttributeResponse> modifyCenBandwidthPackageAttribute(ModifyCenBandwidthPackageAttributeRequest request)
```
参数:

request - the request parameters of ModifyCenBandwidthPackageAttribute ModifyCenBandwidthPackageAttributeRequest

返回:

ModifyCenBandwidthPackageAttributeResponse

modifyCenBandwidthPackageSpec
```
CompletableFuture<ModifyCenBandwidthPackageSpecResponse> modifyCenBandwidthPackageSpec(ModifyCenBandwidthPackageSpecRequest request)
```
参数:

request - the request parameters of ModifyCenBandwidthPackageSpec ModifyCenBandwidthPackageSpecRequest

返回:

ModifyCenBandwidthPackageSpecResponse

modifyCenRouteMap
```
CompletableFuture<ModifyCenRouteMapResponse> modifyCenRouteMap(ModifyCenRouteMapRequest request)
```
description :
ModifyCenRouteMap is an asynchronous operation. After you send a request, the system returns a request ID and runs the task in the background. You can call the DescribeCenRouteMaps operation to query the status of a routing policy.
- Modifying: indicates that the system is modifying the routing policy. You can only query the routing policy, but cannot perform other operations.
- Active: indicates that the routing policy is modified.
参数:

request - the request parameters of ModifyCenRouteMap ModifyCenRouteMapRequest

返回:

ModifyCenRouteMapResponse

modifyFlowLogAttribute
```
CompletableFuture<ModifyFlowLogAttributeResponse> modifyFlowLogAttribute(ModifyFlowLogAttributeRequest request)
```
description :
ModifyFlowLogAttribute is an asynchronous operation. After you send a request, the system returns a request ID and runs the task in the background. You can call the DescribeFlowlogs operation to query the status of a flow log.
- If a flow log is in the Modifying state, the flow log is being modified. In this case, you can query the flow log but cannot perform other operations.
- If a flow log is in the Active state, the flow log is modified.
参数:

request - the request parameters of ModifyFlowLogAttribute ModifyFlowLogAttributeRequest

返回:

ModifyFlowLogAttributeResponse

modifyTrafficMatchRuleToTrafficMarkingPolicy
```
CompletableFuture<ModifyTrafficMatchRuleToTrafficMarkingPolicyResponse> modifyTrafficMatchRuleToTrafficMarkingPolicy(ModifyTrafficMatchRuleToTrafficMarkingPolicyRequest request)
```
参数:

request - the request parameters of ModifyTrafficMatchRuleToTrafficMarkingPolicy ModifyTrafficMatchRuleToTrafficMarkingPolicyRequest

返回:

ModifyTrafficMatchRuleToTrafficMarkingPolicyResponse

modifyTransitRouteTableAggregation
```
CompletableFuture<ModifyTransitRouteTableAggregationResponse> modifyTransitRouteTableAggregation(ModifyTransitRouteTableAggregationRequest request)
```
参数:

request - the request parameters of ModifyTransitRouteTableAggregation ModifyTransitRouteTableAggregationRequest

返回:

ModifyTransitRouteTableAggregationResponse

modifyTransitRouterCidr
```
CompletableFuture<ModifyTransitRouterCidrResponse> modifyTransitRouterCidr(ModifyTransitRouterCidrRequest request)
```
description :
Before you modify the CIDR block of a transit router, we recommend that you read the limits on transit router CIDR blocks.
- If IP addresses within the CIDR block have been allocated to network instances, you cannot modify the CIDR block.
- When you call ModifyTransitRouterCidr, if no parameter of the PublishCidrRoute operation is modified, ModifyTransitRouterCidr is a synchronous operation. After you call the operation, the new settings are immediately applied.
- If a parameter of the PublishCidrRoute operation is modified, ModifyTransitRouterCidr is an asynchronous operation. After you call the operation, the request ID (RequestId) is returned but the operation is still being performed in the system background. You can call ListTransitRouterCidr to query the status of the CIDR block of the transit router.
  - If the CIDR block of the transit router remains unchanged, the CIDR block is still being modified.
  - If the CIDR block of the transit router is changed to the one that you specify in the request, the CIDR block has been modified.
参数:

request - the request parameters of ModifyTransitRouterCidr ModifyTransitRouterCidrRequest

返回:

ModifyTransitRouterCidrResponse

modifyTransitRouterMulticastDomain
```
CompletableFuture<ModifyTransitRouterMulticastDomainResponse> modifyTransitRouterMulticastDomain(ModifyTransitRouterMulticastDomainRequest request)
```
参数:

request - the request parameters of ModifyTransitRouterMulticastDomain ModifyTransitRouterMulticastDomainRequest

返回:

ModifyTransitRouterMulticastDomainResponse

moveResourceGroup
```
CompletableFuture<MoveResourceGroupResponse> moveResourceGroup(MoveResourceGroupRequest request)
```
description :
By default, CEN instances and bandwidth plans are in the default resource group. You can call the MoveResourceGroup operation to move CEN instances or bandwidth plans to another resource group.

参数:

request - the request parameters of MoveResourceGroup MoveResourceGroupRequest

返回:

MoveResourceGroupResponse

openTransitRouterService
```
CompletableFuture<OpenTransitRouterServiceResponse> openTransitRouterService(OpenTransitRouterServiceRequest request)
```
description :
You can call the OpenTransitRouterService operation to activate the transit router feature free of charge. After the OpenTransitRouterService operation succeeds, an order is automatically generated. You can use the returned order ID to query the order information in Alibaba Cloud User Center.

参数:

request - the request parameters of OpenTransitRouterService OpenTransitRouterServiceRequest

返回:

OpenTransitRouterServiceResponse

publishRouteEntries

CompletableFuture<PublishRouteEntriesResponse> publishRouteEntries(PublishRouteEntriesRequest request)

description :

The following table describes whether routes of different types are advertised to CEN by default. You can call the PublishRouteEntries operation to advertise routes to CEN.

Route	Network instance	Advertised to CEN by default
Routes that route network traffic to Elastic Compute Service (ECS) instances	VPC	No
Routes that route network traffic to VPN gateways	VPC	No
Routes that route network traffic to high-availability virtual IP addresses (HAVIPs)	VPC	No
Routes that route network traffic to router interfaces	VPC	No
Routes that route network traffic to elastic network interfaces (ENIs)	VPC	No
Routes that route network traffic to IPv6 gateways	VPC	No
Routes that route network traffic to NAT gateways	VPC	No
System routes of VPCs	VPC	Yes
Routes that route network traffic to data centers	VBR	Yes
Border Gateway Protocol (BGP) routes	VBR	Yes

参数:: request - the request parameters of PublishRouteEntries PublishRouteEntriesRequest
返回:: PublishRouteEntriesResponse

refreshTransitRouteTableAggregation
```
CompletableFuture<RefreshTransitRouteTableAggregationResponse> refreshTransitRouteTableAggregation(RefreshTransitRouteTableAggregationRequest request)
```
参数:

request - the request parameters of RefreshTransitRouteTableAggregation RefreshTransitRouteTableAggregationRequest

返回:

RefreshTransitRouteTableAggregationResponse

registerTransitRouterMulticastGroupMembers
```
CompletableFuture<RegisterTransitRouterMulticastGroupMembersResponse> registerTransitRouterMulticastGroupMembers(RegisterTransitRouterMulticastGroupMembersRequest request)
```
description :
Enterprise Edition transit routers support only elastic network interfaces (ENIs) as multicast members. You can call the RegisterTransitRouterMulticastGroupMembers operation to specify an ENI in the current region or a different region as a multicast member.
- If you specify a value for the NetworkInterfaceIds parameter, an ENI in the current region is to be specified as a multicast member. Make sure that the ENI and vSwitch are associated with the multicast group. For more information, see AssociateTransitRouterMulticastDomain.
- If you specify a value for the PeerTransitRouterMulticastDomains, a multicast member in a multicast group that belongs to another region but has the same IP address as the current multicast group is to be specified as a multicast member for the current multicast group. Make sure that an inter-region connection is established between the regions. For more information, see CreateTransitRouterPeerAttachment. For example, you created Multicast Group 1 in Multicast Domain 1, which is in the China (Hangzhou) region. You created Multicast Group 2 in Multicast Domain 2, which is in the China (Shanghai) region. Multicast Group 1 and Multicast Group 2 use the same multicast IP address, and Multicast Member 2 is in Multicast Group 2 in the China (Shanghai) region. If you call the RegisterTransitRouterMulticastGroupMembers operation to add multicast members to Multicast Group 1 in the China (Hangzhou) region and set PeerTransitRouterMulticastDomains to the ID of Multicast Group 2, which is in the China (Shanghai) region, Multicast Member 2, which is in Multicast Domain 2 in the China (Shanghai) region is added to Multicast Group 1 in the China (Hangzhou) region.
- RegisterTransitRouterMulticastGroupMembers is an asynchronous operation. After a request is sent, the system returns a request ID and runs the task in the background. You can call the ListTransitRouterMulticastGroups operation to query the status of a multicast member.
  - If the multicast member is in the Registering, the multicast member is being created. In this case, you can query the multicast member but cannot perform other operations on the multicast member.
  - If the multicast member is in the Registered state, the multicast member is created.
参数:

request - the request parameters of RegisterTransitRouterMulticastGroupMembers RegisterTransitRouterMulticastGroupMembersRequest

返回:

RegisterTransitRouterMulticastGroupMembersResponse

registerTransitRouterMulticastGroupSources
```
CompletableFuture<RegisterTransitRouterMulticastGroupSourcesResponse> registerTransitRouterMulticastGroupSources(RegisterTransitRouterMulticastGroupSourcesRequest request)
```
description :
You can specify only elastic network interfaces (ENIs) as multicast sources.
- RegisterTransitRouterMulticastGroupSources is an asynchronous operation. After a request is sent, the system returns a request ID and runs the task in the background. You can call the ListTransitRouterMulticastGroups operation to query the status of a multicast source.
  - If a multicast source is in the Registering state, the multicast source is being created. You can query the multicast source but cannot perform other operations on the multicast source.
  - If a multicast source is in the Registered state, the multicast source is created.
Prerequisite

Before you call RegisterTransitRouterMulticastGroupSources, make sure that the vSwitch on which the ENI is created is associated with the multicast domain. For more information, see AssociateTransitRouterMulticastDomain.
参数:

request - the request parameters of RegisterTransitRouterMulticastGroupSources RegisterTransitRouterMulticastGroupSourcesRequest

返回:

RegisterTransitRouterMulticastGroupSourcesResponse

removeTrafficMatchRuleFromTrafficMarkingPolicy
```
CompletableFuture<RemoveTrafficMatchRuleFromTrafficMarkingPolicyResponse> removeTrafficMatchRuleFromTrafficMarkingPolicy(RemoveTrafficMatchRuleFromTrafficMarkingPolicyRequest request)
```
description :
When you call RemoveTrafficMatchRuleFromTrafficMarkingPolicy, take note of the following rules: * If you specify the ID of a traffic classification rule in the TrafficMarkRuleIds parameter, the specified traffic classification rule is deleted. * If you do not specify a traffic classification rule ID in the TrafficMarkRuleIds parameter, no operation is performed after you call this operation. If you want to delete a traffic classification rule, you must specify the rule ID before you call this operation.
- RemoveTrafficMatchRuleFromTrafficMarkingPolicy is an asynchronous operation. After you send a request, the system returns a request ID and runs the task in the background. You can call the ListTrafficMarkingPolicies operation to query the status of a traffic classification rule.
  - If a traffic classification rule is in the Deleting state, the traffic classification rule is being deleted. In this case, you can query the traffic classification rule but cannot perform other operations.
  - If a traffic classification rule cannot be found, the traffic classification rule is deleted.
参数:

request - the request parameters of RemoveTrafficMatchRuleFromTrafficMarkingPolicy RemoveTrafficMatchRuleFromTrafficMarkingPolicyRequest

返回:

RemoveTrafficMatchRuleFromTrafficMarkingPolicyResponse

removeTraficMatchRuleFromTrafficMarkingPolicy
```
@Deprecated
CompletableFuture<RemoveTraficMatchRuleFromTrafficMarkingPolicyResponse> removeTraficMatchRuleFromTrafficMarkingPolicy(RemoveTraficMatchRuleFromTrafficMarkingPolicyRequest request)
```
已过时。 OpenAPI RemoveTraficMatchRuleFromTrafficMarkingPolicy is deprecated, please use Cbn::2017-09-12::RemoveTrafficMatchRuleFromTrafficMarkingPolicy instead. * @description ### [](#)Precautions The **RemoveTraficMatchRuleFromTrafficMarkingPolicy** operation is deprecated and will be discontinued soon. To delete a traffic classification rule, call the [RemoveTrafficMatchRuleFromTrafficMarkingPolicy](https://help.aliyun.com/document_detail/452726.html) operation. Maintenance on this document has stopped.

参数:

request - the request parameters of RemoveTraficMatchRuleFromTrafficMarkingPolicy RemoveTraficMatchRuleFromTrafficMarkingPolicyRequest

返回:

RemoveTraficMatchRuleFromTrafficMarkingPolicyResponse

replaceTransitRouterRouteTableAssociation
```
CompletableFuture<ReplaceTransitRouterRouteTableAssociationResponse> replaceTransitRouterRouteTableAssociation(ReplaceTransitRouterRouteTableAssociationRequest request)
```
参数:

request - the request parameters of ReplaceTransitRouterRouteTableAssociation ReplaceTransitRouterRouteTableAssociationRequest

返回:

ReplaceTransitRouterRouteTableAssociationResponse

resolveAndRouteServiceInCen
```
CompletableFuture<ResolveAndRouteServiceInCenResponse> resolveAndRouteServiceInCen(ResolveAndRouteServiceInCenRequest request)
```
description :
Cloud services refer to Alibaba Cloud services that use the 100.64.0.0/10 CIDR block to provide services. These cloud services include Object Storage Service (OSS), Simple Log Service (SLS), and Data Transmission Service (DTS). If your on-premises network needs to access a cloud service, you must attach the virtual border router (VBR) or Cloud Connect Network (CCN) instance that is connected to your on-premises network to a Cloud Enterprise Network (CEN) instance. In addition, you must attach a virtual private cloud (VPC) that is deployed in the same region as the cloud service to the CEN instance. This way, your on-premises network can connect to the VPC that is deployed in the same region as the cloud service and access the cloud service through the VPC.
- This operation is supported only by Basic Edition transit routers. An on-premises network associated with a VBR can use CEN to access only a cloud service that is deployed in the same region. For example, if cloud services are deployed in the China (Beijing) region, only on-premises networks connected to VBRs in the China (Beijing) region can access the cloud services.
- ResolveAndRouteServiceInCen is an asynchronous operation. After a request is sent, the system returns a request ID and runs the task in the background. You can call DescribeRouteServicesInCen to query the status of a cloud service.
  - If the cloud service is in the Creating state, the connection to the cloud service is being created. In this case, you can query the cloud service but cannot perform other operations.
  - If the cloud service is in the Active state, the connection to the cloud service is created.
  - If the cloud service is in the Failed state, the connection to the cloud service failed.
Prerequisites

Before you call this operation, make sure that the following conditions are met:
- The VBR or CCN instance to which your on-premises network is connected is attached to a CEN instance.
- A VPC that is deployed in the same region as the cloud service is attached to the CEN instance. For more information, see AttachCenChildInstance.
参数:

request - the request parameters of ResolveAndRouteServiceInCen ResolveAndRouteServiceInCenRequest

返回:

ResolveAndRouteServiceInCenResponse

revokeInstanceFromTransitRouter
```
CompletableFuture<RevokeInstanceFromTransitRouterResponse> revokeInstanceFromTransitRouter(RevokeInstanceFromTransitRouterRequest request)
```
description :
RevokeInstanceFromTransitRouter can be used to revoke permissions on virtual private clouds (VPCs), virtual border routers (VBRs), IPsec-VPN connections, and Express Connect Router (ECRs) that belong to another Alibaba Cloud account. To revoke permissions on Cloud Connect Network (CCN) instances that belong to another Alibaba Cloud account, call the RevokeInstanceFromCbn operation.

Prerequisites

Before you call RevokeInstanceFromTransitRouter, you must detach the network instances from the transit router.
- For more information about how to detach VPCs from Enterprise Edition transit routers, see DeleteTransitRouterVpcAttachment.
- For more information about how to detach VBRs from Enterprise Edition transit routers, see DeleteTransitRouterVbrAttachment.
- For more information about how to detach IPsec-VPN connections from Enterprise Edition transit routers, see DeleteTransitRouterVpnAttachment.
- For more information about how to detach ECRs from Enterprise Edition transit routers, see DeleteTransitRouterEcrAttachment.
- For more information about how to detach network instances from Basic Edition transit routers, see DetachCenChildInstance.
参数:

request - the request parameters of RevokeInstanceFromTransitRouter RevokeInstanceFromTransitRouterRequest

返回:

RevokeInstanceFromTransitRouterResponse

routePrivateZoneInCenToVpc
```
CompletableFuture<RoutePrivateZoneInCenToVpcResponse> routePrivateZoneInCenToVpc(RoutePrivateZoneInCenToVpcRequest request)
```
description :
Alibaba Cloud DNS PrivateZone (PrivateZone) is an Alibaba Cloud private domain name resolution and management service based on Virtual Private Cloud (VPC). After you attach virtual border routers (VBRs) and Cloud Connect Network (CCN) instances to a Cloud Enterprise Network (CEN) instance, you can enable the on-premises networks connected to the VBRs and CCN instances to access PrivateZone through the CEN instance.

Usage notes
- The on-premises networks connected to VBRs or CCN instances must be deployed in the same region as the PrivateZone service. For example, if the PrivateZone service is deployed in the China (Beijing) region, only on-premises networks connected to VBRs or CCN instances in the China (Beijing) region can access the PrivateZone service.
- RoutePrivateZoneInCenToVpc is an asynchronous operation. After you send a request, the request ID is returned but the operation is still being performed in the system background. You can call DescribeCenPrivateZoneRoutes to query the status of PrivateZone.
  - If PrivateZone is in the Creating state, access to PrivateZone is being configured. In this case, you can query PrivateZone configurations but cannot perform other operations.
  - If PrivateZone is in the Active state, access to PrivateZone is enabled.
  - If PrivateZone is in the Failed state, configurations of access to PrivateZone failed.
Prerequisites

Before you call RoutePrivateZoneInCenToVpc, make sure that the following conditions are met:
- PrivateZone is deployed. For more information, see PrivateZone quick start.
- The following network instances are attached to the same CEN instance: the VPC that is associated with the PrivateZone service, and the VBR and CCN instance that want to access the PrivateZone service. For more information, see AttachCenChildInstance.
- If your on-premises network uses a CCN instance to connect to Alibaba Cloud and the account that owns the CCN instance is different from the account that owns the VPC or CEN instance, you must grant the CCN instance required permissions. For more information, see Grant permissions to CCN.
参数:

request - the request parameters of RoutePrivateZoneInCenToVpc RoutePrivateZoneInCenToVpcRequest

返回:

RoutePrivateZoneInCenToVpcResponse

setCenInterRegionBandwidthLimit
```
CompletableFuture<SetCenInterRegionBandwidthLimitResponse> setCenInterRegionBandwidthLimit(SetCenInterRegionBandwidthLimitRequest request)
```
description :
This operation is used to manage bandwidth of inter-region connections only for Basic Edition transit routers.

Prerequisites

The Cloud Enterprise Network (CEN) instance is associated with a bandwidth plan. For more information, see CreateCenBandwidthPackage and AssociateCenBandwidthPackage. You can call the SetCenInterRegionBandwidthLimit operation to configure, change, or remove the bandwidth limit of an inter-region connection.
- If you set BandwidthLimit to a value other than 0, the bandwidth of the inter-region connection is set to the specified value.
- If you set BandwidthLimit to 0, the bandwidth of the inter-region connection is no longer limited.
Limits
- The bandwidth limit of an inter-region connection cannot exceed the bandwidth limit of the associated bandwidth plan.
- The sum of bandwidth limits of all inter-region connections cannot exceed the bandwidth limit of the associated bandwidth plan.
- If bandwidth multiplexing is enabled for an inter-region connection, you cannot change the bandwidth of the inter-region connection.
- The SetCenInterRegionBandwidthLimit operation can be used to configure, modify, or delete the bandwidth of inter-region connections only for Basic Edition transit routers. To configure, modify, or delete the bandwidth of inter-region connections for Enterprise Edition transit routers, call the CreateTransitRouterPeerAttachment, UpdateTransitRouterPeerAttachmentAttribute, or DeleteTransitRouterPeerAttachment operation.
参数:

request - the request parameters of SetCenInterRegionBandwidthLimit SetCenInterRegionBandwidthLimitRequest

返回:

SetCenInterRegionBandwidthLimitResponse

tagResources
```
CompletableFuture<TagResourcesResponse> tagResources(TagResourcesRequest request)
```
description :
Each tag consists of a tag key and a tag value. When you add a tag, you must specify the tag key and tag value.
- If you want to add multiple tags to a Cloud Enterprise Network (CEN) instance, each tag key must be unique.
- You can add at most 20 tags to a CEN instance.
参数:

request - the request parameters of TagResources TagResourcesRequest

返回:

TagResourcesResponse

tempUpgradeCenBandwidthPackageSpec
```
CompletableFuture<TempUpgradeCenBandwidthPackageSpecResponse> tempUpgradeCenBandwidthPackageSpec(TempUpgradeCenBandwidthPackageSpecRequest request)
```
参数:

request - the request parameters of TempUpgradeCenBandwidthPackageSpec TempUpgradeCenBandwidthPackageSpecRequest

返回:

TempUpgradeCenBandwidthPackageSpecResponse

unassociateCenBandwidthPackage
```
CompletableFuture<UnassociateCenBandwidthPackageResponse> unassociateCenBandwidthPackage(UnassociateCenBandwidthPackageRequest request)
```
description :
No inter-region connections are configured in the bandwidth plan. For more information about how to delete inter-region connections, see SetCenInterRegionBandwidthLimit.

参数:

request - the request parameters of UnassociateCenBandwidthPackage UnassociateCenBandwidthPackageRequest

返回:

UnassociateCenBandwidthPackageResponse

unroutePrivateZoneInCenToVpc
```
CompletableFuture<UnroutePrivateZoneInCenToVpcResponse> unroutePrivateZoneInCenToVpc(UnroutePrivateZoneInCenToVpcRequest request)
```
参数:

request - the request parameters of UnroutePrivateZoneInCenToVpc UnroutePrivateZoneInCenToVpcRequest

返回:

UnroutePrivateZoneInCenToVpcResponse

untagResources
```
CompletableFuture<UntagResourcesResponse> untagResources(UntagResourcesRequest request)
```
参数:

request - the request parameters of UntagResources UntagResourcesRequest

返回:

UntagResourcesResponse

updateCenInterRegionTrafficQosPolicyAttribute
```
CompletableFuture<UpdateCenInterRegionTrafficQosPolicyAttributeResponse> updateCenInterRegionTrafficQosPolicyAttribute(UpdateCenInterRegionTrafficQosPolicyAttributeRequest request)
```
参数:

request - the request parameters of UpdateCenInterRegionTrafficQosPolicyAttribute UpdateCenInterRegionTrafficQosPolicyAttributeRequest

返回:

UpdateCenInterRegionTrafficQosPolicyAttributeResponse

updateCenInterRegionTrafficQosQueueAttribute
```
CompletableFuture<UpdateCenInterRegionTrafficQosQueueAttributeResponse> updateCenInterRegionTrafficQosQueueAttribute(UpdateCenInterRegionTrafficQosQueueAttributeRequest request)
```
参数:

request - the request parameters of UpdateCenInterRegionTrafficQosQueueAttribute UpdateCenInterRegionTrafficQosQueueAttributeRequest

返回:

UpdateCenInterRegionTrafficQosQueueAttributeResponse

updateTrafficMarkingPolicyAttribute
```
CompletableFuture<UpdateTrafficMarkingPolicyAttributeResponse> updateTrafficMarkingPolicyAttribute(UpdateTrafficMarkingPolicyAttributeRequest request)
```
参数:

request - the request parameters of UpdateTrafficMarkingPolicyAttribute UpdateTrafficMarkingPolicyAttributeRequest

返回:

UpdateTrafficMarkingPolicyAttributeResponse

updateTransitRouter
```
CompletableFuture<UpdateTransitRouterResponse> updateTransitRouter(UpdateTransitRouterRequest request)
```
description :
UpdateTransitRouter* is an asynchronous operation. After a request is sent, the system returns a request ID and runs the task in the background. You can call the ListTransitRouters operation to query the status of a transit router.
- If a transit router is in the Modifying state, the configuration of the transit router is being modified. You can query the transit router but cannot perform other operations.
- If a transit router is in the Active state, the configuration of the transit router is modified.
参数:

request - the request parameters of UpdateTransitRouter UpdateTransitRouterRequest

返回:

UpdateTransitRouterResponse

updateTransitRouterEcrAttachmentAttribute
```
CompletableFuture<UpdateTransitRouterEcrAttachmentAttributeResponse> updateTransitRouterEcrAttachmentAttribute(UpdateTransitRouterEcrAttachmentAttributeRequest request)
```
description :
UpdateTransitRouterEcrAttachmentAttribute is an asynchronous operation. After a request is sent, the system returns a request ID and runs the task in the background. You can call the ListTransitRouterEcrAttachments operation to query the status of an ECR connection. If an ECR connection is in the Modifying state, the ECR connection is being modified. In this case, you can query the ECR connection but cannot perform other operations on the ECR connection. If an ECR connection is in the Attached state, the ECR connection is modified.

参数:

request - the request parameters of UpdateTransitRouterEcrAttachmentAttribute UpdateTransitRouterEcrAttachmentAttributeRequest

返回:

UpdateTransitRouterEcrAttachmentAttributeResponse

updateTransitRouterPeerAttachmentAttribute
```
CompletableFuture<UpdateTransitRouterPeerAttachmentAttributeResponse> updateTransitRouterPeerAttachmentAttribute(UpdateTransitRouterPeerAttachmentAttributeRequest request)
```
description :
UpdateTransitRouterPeerAttachmentAttribute* is an asynchronous operation. After you send a request, the system returns a request ID and runs the task in the background. You can call the ListTransitRouterPeerAttachments operation to query the status of an inter-region connection.
- If an inter-region connection is in the Modifying state, the inter-region connection is being modified. You can query the inter-region connection but cannot perform other operations.
- If an inter-region connection is in the Attached state, the inter-region connection is modified.
参数:

request - the request parameters of UpdateTransitRouterPeerAttachmentAttribute UpdateTransitRouterPeerAttachmentAttributeRequest

返回:

UpdateTransitRouterPeerAttachmentAttributeResponse

updateTransitRouterRouteEntry
```
CompletableFuture<UpdateTransitRouterRouteEntryResponse> updateTransitRouterRouteEntry(UpdateTransitRouterRouteEntryRequest request)
```
参数:

request - the request parameters of UpdateTransitRouterRouteEntry UpdateTransitRouterRouteEntryRequest

返回:

UpdateTransitRouterRouteEntryResponse

updateTransitRouterRouteTable
```
CompletableFuture<UpdateTransitRouterRouteTableResponse> updateTransitRouterRouteTable(UpdateTransitRouterRouteTableRequest request)
```
参数:

request - the request parameters of UpdateTransitRouterRouteTable UpdateTransitRouterRouteTableRequest

返回:

UpdateTransitRouterRouteTableResponse

updateTransitRouterVbrAttachmentAttribute
```
CompletableFuture<UpdateTransitRouterVbrAttachmentAttributeResponse> updateTransitRouterVbrAttachmentAttribute(UpdateTransitRouterVbrAttachmentAttributeRequest request)
```
description :
UpdateTransitRouterVbrAttachmentAttribute* is an asynchronous operation. After a request is sent, the system returns a request ID and runs the task in the background. You can call the ListTransitRouterVbrAttachments operation to query the status of a VBR connection.
- If a VBR connection is in the Modifying state, the VBR connection is being modified. You can query the VBR connection but cannot perform other operations.
- If the VBR connection is in the Attached state, the VBR connection is modified.
参数:

request - the request parameters of UpdateTransitRouterVbrAttachmentAttribute UpdateTransitRouterVbrAttachmentAttributeRequest

返回:

UpdateTransitRouterVbrAttachmentAttributeResponse

updateTransitRouterVpcAttachmentAttribute
```
CompletableFuture<UpdateTransitRouterVpcAttachmentAttributeResponse> updateTransitRouterVpcAttachmentAttribute(UpdateTransitRouterVpcAttachmentAttributeRequest request)
```
description :
UpdateTransitRouterVpcAttachmentAttribute* is an asynchronous operation. After you send a request, the system returns a request ID and runs the task in the background. You can call the ListTransitRouterVpcAttachments operation to query the status of a VPC connection.
- If a VPC connection is in the Modifying state, the VPC connection is being modified. You can query the VPC connection but cannot perform other operations.
- If a VPC connection is in the Attached state, the VPC connection is modified.
参数:

request - the request parameters of UpdateTransitRouterVpcAttachmentAttribute UpdateTransitRouterVpcAttachmentAttributeRequest

返回:

UpdateTransitRouterVpcAttachmentAttributeResponse

updateTransitRouterVpcAttachmentZones
```
CompletableFuture<UpdateTransitRouterVpcAttachmentZonesResponse> updateTransitRouterVpcAttachmentZones(UpdateTransitRouterVpcAttachmentZonesRequest request)
```
description :
When you add a zone and a vSwitch for a VPC connection, make sure that the vSwitch has at least one idle IP address. When you modify the zones and vSwitches of a VPC connection, the Enterprise Edition transit router creates an elastic network interface (ENI) in the vSwitch. The ENI occupies one IP address in the vSwitch. The ENI forwards traffic between the VPC and the Enterprise Edition transit router.
- UpdateTransitRouterVpcAttachmentZones is an asynchronous operation. After you send a request, the system returns a request ID and runs the task in the background. You can call the ListTransitRouterVpcAttachments operation to query the status of a VPC connection.
  - If a VPC connection is in the Modifying state, the VPC connection is being modified. You can query the VPC connection but cannot perform other operations.
  - If a VPC connection is in the Attached state, the VPC connection is modified.
参数:

request - the request parameters of UpdateTransitRouterVpcAttachmentZones UpdateTransitRouterVpcAttachmentZonesRequest

返回:

UpdateTransitRouterVpcAttachmentZonesResponse

updateTransitRouterVpnAttachmentAttribute
```
CompletableFuture<UpdateTransitRouterVpnAttachmentAttributeResponse> updateTransitRouterVpnAttachmentAttribute(UpdateTransitRouterVpnAttachmentAttributeRequest request)
```
参数:

request - the request parameters of UpdateTransitRouterVpnAttachmentAttribute UpdateTransitRouterVpnAttachmentAttributeRequest

返回:

UpdateTransitRouterVpnAttachmentAttributeResponse

withdrawPublishedRouteEntries
```
CompletableFuture<WithdrawPublishedRouteEntriesResponse> withdrawPublishedRouteEntries(WithdrawPublishedRouteEntriesRequest request)
```
参数:

request - the request parameters of WithdrawPublishedRouteEntries WithdrawPublishedRouteEntriesRequest

返回:

WithdrawPublishedRouteEntriesResponse

接口 AsyncClient

方法概要

从接口继承的方法 com.aliyun.core.utils.SdkAutoCloseable

方法详细资料

builder

create

activeFlowLog

addTrafficMatchRuleToTrafficMarkingPolicy

addTraficMatchRuleToTrafficMarkingPolicy

associateCenBandwidthPackage

associateTransitRouterAttachmentWithRouteTable

associateTransitRouterMulticastDomain

attachCenChildInstance

checkTransitRouterService

createCen

createCenBandwidthPackage

createCenChildInstanceRouteEntryToAttachment

createCenChildInstanceRouteEntryToCen

Limits

createCenInterRegionTrafficQosPolicy

Prerequisites

createCenInterRegionTrafficQosQueue

createCenRouteMap

createFlowlog

Prerequisites

createTrafficMarkingPolicy

createTransitRouteTableAggregation

createTransitRouter

createTransitRouterCidr

createTransitRouterEcrAttachment

Prerequisite

createTransitRouterMulticastDomain

createTransitRouterPeerAttachment

createTransitRouterPrefixListAssociation

createTransitRouterRouteEntry

createTransitRouterRouteTable

createTransitRouterVbrAttachment

createTransitRouterVpcAttachment

Prerequisites

createTransitRouterVpnAttachment

Prerequisites

deactiveFlowLog

deleteCen

Prerequisites

deleteCenBandwidthPackage

deleteCenChildInstanceRouteEntryToAttachment

deleteCenChildInstanceRouteEntryToCen

Limits

deleteCenInterRegionTrafficQosPolicy

deleteCenInterRegionTrafficQosQueue

deleteCenRouteMap

deleteFlowlog

deleteRouteServiceInCen

deleteTrafficMarkingPolicy

deleteTransitRouteTableAggregation

deleteTransitRouter

Prerequisites

deleteTransitRouterCidr

deleteTransitRouterEcrAttachment

deleteTransitRouterMulticastDomain

deleteTransitRouterPeerAttachment

Prerequisites

deleteTransitRouterPrefixListAssociation

deleteTransitRouterRouteEntry

Limits

deleteTransitRouterRouteTable

deleteTransitRouterVbrAttachment

Prerequisites

deleteTransitRouterVpcAttachment

Prerequisites

deleteTransitRouterVpnAttachment

deregisterTransitRouterMulticastGroupMembers

deregisterTransitRouterMulticastGroupSources

describeCenAttachedChildInstanceAttribute

describeCenAttachedChildInstances

describeCenBandwidthPackages

describeCenChildInstanceRouteEntries

describeCenGeographicSpanRemainingBandwidth

describeCenGeographicSpans

describeCenInterRegionBandwidthLimits