Disables an Express Connect circuit after it is enabled.
Operation description
After you call this operation, the specified Express Connect circuit changes to the Terminating state. After the Express Connect circuit is disabled, it changes to the Terminated state. When you call this operation, take note of the following limits:
- You can only disable an Express Connect circuit that is in the Enabled state.
- Before you disable an Express Connect circuit, you must delete the virtual border routers (VBRs) associated with it.
Debugging
Authorization information
The following table shows the authorization information corresponding to the API. The authorization information can be used in the Action policy element to grant a RAM user or RAM role the permissions to call this API operation. Description:
- Operation: the value that you can use in the Action element to specify the operation on a resource.
- Access level: the access level of each operation. The levels are read, write, and list.
- Resource type: the type of the resource on which you can authorize the RAM user or the RAM role to perform the operation. Take note of the following items:
- The required resource types are displayed in bold characters.
- If the permissions cannot be granted at the resource level,
All Resourcesis used in the Resource type column of the operation.
- Condition Key: the condition key that is defined by the cloud service.
- Associated operation: other operations that the RAM user or the RAM role must have permissions to perform to complete the operation. To complete the operation, the RAM user or the RAM role must have the permissions to perform the associated operations.
| Operation | Access level | Resource type | Condition key | Associated operation |
|---|---|---|---|---|
| vpc:TerminatePhysicalConnection | update | *PhysicalConnection acs:vpc:{#regionId}:{#accountId}:physicalconnection/{#PhysicalConnectionId} |
| none |
Request parameters
| Parameter | Type | Required | Description | Example |
|---|---|---|---|---|
| RegionId | string | Yes | The region ID of the Express Connect circuit. You can call the DescribeRegions operation to query the most recent region list. | cn-hangzhou |
| PhysicalConnectionId | string | Yes | The ID of the Express Connect circuit. | pc-119mfjzm**** |
| ClientToken | string | No | The client token that is used to ensure the idempotence of the request. You can use the client to generate the token, but you must make sure that the token is unique among different requests. The client token can contain only ASCII characters. Note
If you do not specify this parameter, the system automatically uses the request ID as the client token. The request ID may be different for each request.
| 02fb3da4-130e-11e9-8e44-0016e04115b |
Response parameters
Examples
Sample success responses
JSONformat
{
"RequestId": "4EC47282-1B74-4534-BD0E-403F3EE64CAF"
}Error codes
| HTTP status code | Error code | Error message | Description |
|---|---|---|---|
| 400 | Forbidden.NotAllowedInState | The request does not allow in this state. | The operation cannot be performed when the Express Connect circuit in the current state. |
| 400 | Forbidden.VbrAttached | Cannot terminate physical connection when virtual border routers are still attached. | Failed to disable the Express Connect circuit because the Express Connect circuit is associated with a VBR. |
| 400 | OperationFailed.VpconnAttached | Cannot terminate physical connection when vpconn are still attached. | The shared port still exists and the physical port cannot be disabled. |
| 404 | InvalidRegionId.NotFound | The RegionId provided does not exist in our records. | The RegionId parameter is set to an invalid value. Specify a valid value and try again. |
| 404 | InvalidPhysicalConnectionId.NotFound | The PhysicalConnectionId provided does not exist in our records. | The Express Connect circuit does not exist. |
For a list of error codes, visit the Service error codes.