Modifies the configuration of an Express Connect circuit.

Limits

When you call this operation, take note of the following limits:

  • If an Express Connect circuit is in the Initial, Enabled, or Rejected state, you can modify the specifications of the Express Connect circuit and the ID of the redundant circuit.
  • If an Express Connect circuit is in the Canceled, Allocating, AllocationFailed, or Terminated state, you cannot modify the specifications of the Express Connect circuit.
  • After you modify the specifications of an Express Connect circuit that is in the Rejected state, the Express Connect circuit enters the Initial state.

Debugging

OpenAPI Explorer automatically calculates the signature value. For your convenience, we recommend that you call this operation in OpenAPI Explorer. OpenAPI Explorer dynamically generates the sample code of the operation for different SDKs.

Request parameters

Parameter Type Required Example Description
RegionId String Yes cn-shanghai

The region ID of the Express Connect circuit.

You can call the DescribeRegions operation to query the most recent region list.

PhysicalConnectionId String Yes pc-119mfjzm******

The ID of the Express Connect circuit.

LineOperator String No CT

The connectivity provider of the Express Connect circuit. Valid values:

  • CT: China Telecom
  • CU: China Unicom
  • CM: China Mobile
  • CO: other connectivity providers in the Chinese mainland
  • Equinix: Equinix
  • Other: other connectivity providers outside the Chinese Mainland
bandwidth Integer No 5

The bandwidth value for the connection over the Express Connect circuit. Unit: Mbit/s. Valid values: 2 to 10240.

PeerLocation String No Building XX, XX Avenue, XX District, Hangzhou, Zhejiang

The geographical location of the data center.

PortType String No 1000Base-LX

The port type of the Express Connect circuit. Valid values:

  • 100Base-T: 100 Mbit/s copper Ethernet port
  • 1000Base-T (default): 1,000 Mbit/s copper Ethernet port
  • 1000Base-LX: 1,000 Mbit/s single-mode optical port (10 kilometers)
  • 10GBase-T: 10,000 Mbit/s copper Ethernet port
  • 10GBase-LR: 10,000 Mbit/s single-mode optical port (10 kilometers)
  • 40GBase-LR: 40,000 Mbit/s single-mode optical port
  • 100GBase-LR: 100,000 Mbit/s single-mode optical port
Note If you want to use the 40GBase-LR or 100GBase-LR port for an Express Connect circuit, you must first contact your account manager to obtain information about resource supplies.
RedundantPhysicalConnectionId String No pc-119mfjzm7

The ID of the redundant Express Connect circuit. The redundant Express Connect circuit must be in the Allocated, Confirmed, or Enabled state.

Description String No Description

The description of the Express Connect circuit.

The description must be 2 to 256 characters in length. It must start with a letter but cannot start with http:// or https://.

Name String No Name

The name of the Express Connect circuit.

The name must be 2 to 128 characters in length and can contain letters, digits, periods (.), underscores (_), and hyphens (-). The name must start with a letter but cannot start with http:// or https://.

ClientToken String No efefe566754h The client token that is used to ensure the idempotence of the request. You can use the client to generate a token, but you must make sure that the token is unique among different requests. The token can contain only ASCII characters and cannot exceed 64 characters in length.
Action String Yes ModifyPhysicalConnectionAttribute

The operation that you want to perform. Set the value to ModifyPhysicalConnectionAttribute.

CircuitCode String No longtel001

The circuit code of the Express Connect circuit. The circuit code is provided by the connectivity provider.

Response parameters

Parameter Type Example Description
RequestId String 013EE132-A109-4247-91B0-099A8FF49AD7

The ID of the request.

Examples

Sample requests

http(s)://[Endpoint]/?RegionId=cn-shanghai
&PhysicalConnectionId=pc-119mfjzm******
&LineOperator=CT
&bandwidth=5
&PeerLocation=Building XX, XX Avenue, XX District, Hangzhou, Zhejiang
&PortType=1000Base-LX
&RedundantPhysicalConnectionId=pc-119mfjzm7
&Description=Description
&Name=Name
&ClientToken=efefe566754h
&Action=ModifyPhysicalConnectionAttribute
&CircuitCode=longtel001
&Common request parameters

Sample success responses

XML format 

HTTP/1.1 200 OK
Content-Type:application/xml

<ModifyPhysicalConnectionAttributeResponse>
    <RequestId>013EE132-A109-4247-91B0-099A8FF49AD7</RequestId>
</ModifyPhysicalConnectionAttributeResponse>

JSON format 

HTTP/1.1 200 OK
Content-Type:application/json

{
  "RequestId" : "013EE132-A109-4247-91B0-099A8FF49AD7"
}

Error codes

HTTP status code Error code Error message Description
400 InvalidLineOperator.Malformd The LineOperator provided was invalid. The error message returned because LineOperator is set to an invalid value.
400 InvalidPeerLocation.Malformd The PeerLocation provided was invalid. The error message returned because PeerLocation is set to an invalid value.
400 InvalidPortType.Malformd The PortType provided was invalid. The error message returned because the specified port type is invalid.
400 InvalidDescription.Malformed The specifid ?Description? is not valid. The error message returned because the specified description is invalid. The description must be 2 to 256 characters in length and cannot start with http:// or https://.
400 InvalidName.Malformed The specified ?Name? is not valid. The error message returned because the format of the name is invalid.
400 InvalidStatus invalid physical connection status. The error message returned because the Express Connect circuit is in an invalid state.
400 InvalidBandwidth invalid physical connection banwidth. The error message returned because the specified bandwidth value of the Express Connect circuit is invalid.
400 InvalidRedundantPhysicalConnection redundant physical connection doesn't belong to current user. The error message returned because the specified redundant Express Connect circuit does not belong to your Apsara Stack account.
400 InvalidRedundantPhysicalConnectionStatus invalid redundant physical connection status. The error message returned because the redundant Express Connect circuit is in an invalid state.
400 InvalidCircuitCode.Malformed circuitCode is illegal. The error message returned because CircuitCode is set to an invalid value.
404 InvalidPhysicalConnectionId.NotFound The PhysicalConnectionId provided does not exist in our records. The error message returned because the Express Connect circuit does not exist.

For a list of error codes, visit the API Error Center.