If your application for a Letter of Authorization (LOA) by calling the ApplyPhysicalConnectionLOA operation is denied, you can call this operation to apply again.
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:SecondApplyPhysicalConnectionLOA | none |
|
| none |
Request parameters
| Parameter | Type | Required | Description | Example |
|---|---|---|---|---|
| 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. 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.
| 123e4567-e89b-12d3-a456-426655440000 |
| RegionId | string | Yes | The region where the Express Connect circuit is deployed. You can call the DescribeRegions operation to query the most recent region list. | cn-hangzhou |
| Bandwidth | integer | No | The bandwidth of the Express Connect circuit. Unit: Mbit/s. Valid values: 2 to 10240. | 3 |
| PeerLocation | string | No | The geographic location where the Express Connect circuit is deployed. | XX Number, XX Road, XX Town, XX District, Hangzhou City, Zhejiang Province. |
| InstanceId | string | Yes | The ID of the Express Connect circuit. | pc-bp1qrb3044eqi**** |
| CompanyName | string | Yes | The name of the customer company that requires the Express Connect circuit. | company |
| LineType | string | Yes | The type of Express Connect circuit. Valid values:
| FIBRE |
| Si | string | Yes | The construction company. | company |
| ConstructionTime | string | Yes | The time when construction started. Specify the time in the ISO 8601 standard in the YYYY-MM-DDThh:mm:ssZ format. The time is displayed in UTC. | 2022-02-28T16:00:00Z |
| PMInfo | array<object> | No | The information about the construction engineer. | |
| object | Yes | |||
| PMCertificateNo | string | Yes | The ID number of the construction engineer. You can specify the ID number of an ID card or an international passport. You can configure information for up to 16 construction engineers. | 5****************9 |
| PMName | string | Yes | The name of the construction engineer. | Zhangsan |
| PMCertificateType | string | Yes | The type of the identity document of the construction engineer. Valid values:
| IDCard |
| PMGender | string | Yes | The gender of the construction engineer. | Male |
| PMContactInfo | string | Yes | The contact information about the construction engineer. | 1390000**** |
Response parameters
Examples
Sample success responses
JSONformat
{
"RequestId": "A47BD386-7FDE-42C4-8D22-C6223D18AA1C\t\n"
}Error codes
| HTTP status code | Error code | Error message | Description |
|---|---|---|---|
| 400 | OperationFailed.PconnTrafficNotEnable | The operation is failed because of PconnTrafficNotEnable. | Billing for outbound data transfer is disabled. |
| 400 | IllegalParam.Bandwidth | Invalid Bandwidth. | The bandwidth of the Express Connect circuit is invalid. |
| 400 | IllegalParam.CompanyLocalizedName | Invalid CompanyLocalizedName. | The localized name of the company is invalid. |
| 400 | IllegalParam.CompanyName | Invalid CompanyName. | The company name is invalid. |
| 400 | IllegalParam.LineType | Invalid LineType. | The Express Connect circuit type is invalid. |
| 400 | IllegalParam.PeerLocation | Invalid PeerLocation. | The location of the Express Connect circuit is invalid. |
| 400 | IllegalParam.PmCertificateType | Invalid PmCertificateType. | The certificate type of the engineer is invalid. |
| 400 | IllegalParam.PmCertificateNo | Invalid PmCertificateNo. | The certificate number of the engineer is invalid. |
| 400 | IllegalParam.PmContactInfo | Invalid PmContactInfo. | The contact information about the engineer is invalid. |
| 400 | IllegalParam.PmGender | Invalid PmGender. | The engineer gender is invalid. |
| 400 | IllegalParam.PmName | Invalid PmName. | The engineer name is invalid. |
| 400 | IllegalParam.Si | Invalid Si. | The construction company is invalid. |
| 400 | InvalidInstanceId.NotFound | InstanceId is not found. | The Express Connect circuit ID is invalid. |
| 400 | IncorrectStatus.PhysicalConnection | Invalid physical connection status. | The Express Connect circuit is in an invalid state. |
| 400 | IncorrectStatus.PhysicalConnectionLOA | Invalid Express Connect circuit LOA status. | The construction status of the Express Connect circuit is invalid. |
| 400 | OperationDenied.LOAForVirtualPhysicalConnection | The operation is not allowed because of LOAForVirtualPhysicalConnection. | The shared Express Connect circuit does not allow construction. |
| 400 | MissingParam.InstanceId | The parameter InstanceId is mandatory. | You must specify the Express Connect circuit ID. |
| 400 | MissingParam.ConstructionTime | The parameter ConstructionTime is mandatory. | You must specify the start time. |
| 400 | MissingParam.PMInfo | The parameter PMInfo is mandatory. | You must specify the engineer information. |
For a list of error codes, visit the Service error codes.
Change history
| Change time | Summary of changes | Operation |
|---|