Enables an Express Connect circuit that is in the Confirmed state. After the circuit is enabled, it enters the Enabled state.
Operation description
When you invoke this operation, note the following items:
You can enable only an Express Connect circuit that is in the Confirmed state. After the circuit is enabled, it enters the Enabled state. To reach the Confirmed state, complete the following steps in sequence: call CreatePhysicalConnection to create a circuit (Initial → Allocating), wait for resource allocation to complete (Allocating → Allocated), and then call ConfirmPhysicalConnection after construction is complete (Allocated → Confirmed).
A billing activation step occurs between the Confirmed and Enabled states. By default (if ByPassSp is not specified or ByPassSp is set to false), the system automatically creates a billing order in the sales and billing system when you invoke this operation. The circuit is enabled only after the order is created. To skip the billing order flow and directly enable the circuit, set ByPassSp to true. This capability is available only to whitelist accounts. For more information, see the ByPassSp parameter description.
The EnablePhysicalConnection operation is asynchronous. The system returns a success response, but the Express Connect circuit is not yet fully enabled because the backend enablement task is still in progress. You can invoke DescribePhysicalConnections to query the enablement status of the Express Connect circuit.
The EnablePhysicalConnection operation does not support concurrent enablement of the same Express Connect circuit that is in the Confirmed state. Concurrent invocations return an error. If the Express Connect circuit is already in the Enabled state, invoking this operation again returns a success response (idempotent).
Try it now
Test
RAM authorization
|
Action |
Access level |
Resource type |
Condition key |
Dependent action |
|
vpc:EnablePhysicalConnection |
update |
*PhysicalConnection
|
None | None |
Request parameters
|
Parameter |
Type |
Required |
Description |
Example |
| RegionId |
string |
Yes |
The region where the Express Connect circuit resides. You can call the DescribeRegions operation to query region IDs. |
cn-shanghai |
| PhysicalConnectionId |
string |
Yes |
The ID of the Express Connect circuit. |
pc-2zeoaxkq3x**** |
| ClientToken |
string |
No |
The client token that is used to ensure the idempotence of the request. The client generates the value of this parameter. The value must be unique among different requests and cannot exceed 64 ASCII characters in length. |
02fb3da4-130e-11e9-8e44-0016e04115b |
| ByPassSp |
boolean |
No |
Specifies whether to skip the SP (sales and billing system) billing order flow and directly enable the Express Connect circuit. Valid values:
|
false |
Response elements
|
Element |
Type |
Description |
Example |
|
object |
|||
| RequestId |
string |
The request ID. |
20365164-5b0d-460a-83c2-2189972b3349 |
Examples
Success response
JSON format
{
"RequestId": "20365164-5b0d-460a-83c2-2189972b3349"
}
Error codes
|
HTTP status code |
Error code |
Error message |
Description |
|---|---|---|---|
| 400 | Forbidden.NotAllowedInState | The request does not allow in this state. | |
| 400 | INSTANCE.STATUS.NOT.ALLOW | Instance status not allow | The instance in the current state does not support the operation. |
| 400 | ALIUID.NOT.ALLOW.WITHOUT.SP | AliUid not allow direct enable physical connection | You are not allowed to use a physical port when you use an Alibaba Cloud UID. |
| 400 | ACCESS.DEVICE.NOT.ALLOW.WITHOUT.SP | Access device not allow direct enable physical connection | The access device is not allowed to use a physical port. |
| 404 | InvalidRegionId.NotFound | The RegionId provided does not exist in our records. | |
| 404 | InvalidPhysicalConnectionId.NotFound | The PhysicalConnectionId provided does not exist in our records. |
See Error Codes for a complete list.
Release notes
See Release Notes for a complete list.