ListPhysicalConnectionFeatures - Virtual Private Cloud - Alibaba Cloud Documentation Center

Queries he connection features supported by a Express Connect circuit.

Debugging

You can run this interface directly in OpenAPI Explorer, saving you the trouble of calculating signatures. After running successfully, OpenAPI Explorer can automatically generate SDK code samples.

Debug

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:
- For mandatory resource types, indicate with a prefix of * .
- If the permissions cannot be granted at the resource level, All Resources is 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:ListPhysicalConnectionFeatures	list	*PhysicalConnection `acs:vpc:{#regionId}:{#AccountId}:physicalconnection/{#PhysicalConnectionId}`	none	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 region list.	cn-hangzhou
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 token can contain only ASCII characters. Note If you do not specify this parameter, the system automatically uses the RequestId as the ClientToken. The RequestId may be different.	123e4567-e89b-12d3-a456-426655440000
PhysicalConnectionId	string	Yes	The ID of the Express Connect circuit.	pc-bp1qrb3044eqixog****

Response parameters

Parameter	Type	Description	Example
	object	The request ID.
RequestId	string	The request ID.	A599D38F-3618-18FD-9427-108FB9B5BD26
PhysicalConnectionFeatures	array<object>	The list of Express Connect circuit features.
PhysicalConnectionFeature	object	The list of Express Connect circuit features.
FeatureValue	string	The feature value of the Express Connect circuit. Valid values: OK: Supported NOK: Not supported	OK
FeatureKey	string	The feature key of the Express Connect circuit. Valid values: SubifRateLimit: subinterface throttling BFD Capability: Bidirectional Forwarding Detection (BFD) DualStack: Dual stack CEN: When a virtual border router (VBR) is attached to a Cloud Enterprise Network (CEN) instance and BGP routes are advertised on the user side, attributes such as as-path and community are carried. CENv6: When a VBR is attached to an IPv6 CEN instance and BGP routes are advertised on the user side, attributes such as as-path and community are carried. QOS: The device supports configuring QOS policies on physical ports. MSHA: The device supports fast switching groups between two VBRs. MULTI_MS_HA: The device supports a maximum of eight VBRs that can be added to the same ECR.	SubifRateLimit

Examples

Sample success responses

JSONformat

{
  "RequestId": "A599D38F-3618-18FD-9427-108FB9B5BD26",
  "PhysicalConnectionFeatures": [
    {
      "FeatureValue": "OK",
      "FeatureKey": "SubifRateLimit"
    }
  ]
}

Error codes

HTTP status code	Error code	Error message	Description
400	MissingParam.PhysicalConnectionId	The PhysicalConnectionId is missing.	-
400	MissingParam.RegionNo	The RegionId is missing.	-
400	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.