Modifies the specification of a router interface.
Operation description
After you call this operation, the router interface enters the Activating state. After the router interface is activated, the router interface enters the Active state.
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 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:ModifyRouterInterfaceSpec | update |
|
| none |
Request parameters
Parameter | Type | Required | Description | Example |
---|---|---|---|---|
RegionId | string | Yes | The ID of the region where the router interface is deployed. You can call the DescribeRegions operation to query the most recent region list. | cn-hangzhou |
RouterInterfaceId | string | Yes | The ID of the router interface. | ri-2zeo3xzyf38r4urzd**** |
Spec | string | Yes | The specification of the router interface. Valid specifications and bandwidth values:
Note
When Role is set to AcceptingSide, set Spec to Negative.
| Small.1 |
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
JSON
format
{
"Spec": "Small.1",
"RequestId": "4EC47282-1B74-4534-BD0E-403F3EE64CAF"
}
Error codes
HTTP status code | Error code | Error message | Description |
---|---|---|---|
400 | Forbidden.FinancialLocked | RouterInterface can not be operated by this action when it?s FinancialLocked. | - |
400 | InvalidParam.NotFound | Parameter must not be null,uid, bid,regionNo, remoteRegionNo or routerId | - |
400 | InvalidOppositeRegionId.NotFound | The OppositeRegionId provided does not exist in our records. | The peer region does not exist. |
400 | InvalidInstanceOwner.Error | The router instance owner error. | The instance owner information is invalid. |
400 | InvalidRouterInterfaceSpec.Malformed | Specified RouterInterface spec is not valid. | The RouterInterface Spec parameter is set to an invalid value. |
400 | IllegalParam.chargeType | RouterInterface chargeType different. | - |
400 | ResourceQueryError | The specified resource is queried error. | An error occurred while querying the specified resource. |
400 | InvalidSpec.ValueNotSupported | The specified Spec is not supported. | - |
400 | InvalidSpec.ValueNotSupported | The specified Spec is not supported. | - |
400 | InvalidInstance.StatusError | The router instance status error. | The status of the instance is invalid. |
400 | InvalidOpposite.NotFound | The opposite does not exist. | The peer does not exist. |
404 | InvalidRouterInterfaceId.NotFound | The specified RouterInterfaceId does not exist in our record. | The specified router interface does not exist. |
For a list of error codes, visit the Service error codes.
Change history
Change time | Summary of changes | Operation |
---|---|---|
2023-12-21 | API Description Update. The API operation is not deprecated.. The Error code has changed | View Change Details |
2021-11-17 | The Error code has changed | View Change Details |
2021-11-17 | The Error code has changed | View Change Details |