Modifies the specification of a router interface.
Usage notes
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
Request parameters
Parameter | Type | Required | Example | Description |
---|---|---|---|---|
RegionId | String | Yes | cn-hangzhou |
The ID of the region where the router interface is deployed. You can call the DescribeRegions operation to query the most recent region list. |
RouterInterfaceId | String | Yes | ri-2zeo3xzyf38r4urzd**** |
The ID of the router interface. |
Spec | String | Yes | Small.1 |
The specification of the router interface. Valid specifications and bandwidth values:
Note When Role is set to AcceptingSide (acceptor), Spec is set to Negative.
|
Action | String | Yes | ModifyRouterInterfaceSpec |
The operation that you want to perform. Set the value to ModifyRouterInterfaceSpec. |
ClientToken | String | No | 02fb3da4-130e-11e9-8e44-0016e04115b |
The client token that is used to ensure the idempotence of the request. You can use the client to generate the value, but you must make sure that it is unique among different requests. The client token can contain only ASCII characters. Note If you do not set this parameter, the system automatically uses RequestId as ClientToken. RequestId may be different for each API request.
|
Response parameters
Parameter | Type | Example | Description |
---|---|---|---|
Spec | String | Small.1 |
The specification of the router interface. Valid values:
|
RequestId | String | 4EC47282-1B74-4534-BD0E-403F3EE64CAF |
The ID of the request. |
Examples
Sample requests
http(s)://[Endpoint]/?RegionId=cn-hangzhou
&RouterInterfaceId=ri-2zeo3xzyf38r4urzd****
&Spec=Small.1
&Action=ModifyRouterInterfaceSpec
&ClientToken=02fb3da4-130e-11e9-8e44-0016e04115b
&Common request parameters
Sample success responses
XML
format
HTTP/1.1 200 OK
Content-Type:application/xml
<ModifyRouterInterfaceSpecResponse>
<Spec>Small.1</Spec>
<RequestId>4EC47282-1B74-4534-BD0E-403F3EE64CAF</RequestId>
</ModifyRouterInterfaceSpecResponse>
JSON
format
HTTP/1.1 200 OK
Content-Type:application/json
{
"Spec" : "Small.1",
"RequestId" : "4EC47282-1B74-4534-BD0E-403F3EE64CAF"
}
Error codes
HttpCode | Error code | Error message | Description |
---|---|---|---|
400 | InvalidInstanceOwner.Error | The router instance owner error. | The error message returned because the instance owner information is invalid. |
400 | InvalidRouterInterfaceSpec.Malformed | Specified RouterInterface spec is not valid. | The error message returned because the RouterInterface Spec parameter is set to an invalid value. |
400 | InvalidSpec.ValueNotSupported | The specified Spec is not supported. | The error message returned because the specification of the router interface is invalid. |
400 | InvalidInstance.StatusError | The router instance status error. | The error message returned because the instance is in an invalid state. |
400 | InvalidOpposite.NotFound | The opposite does not exit. | The error message returned because the peer does not exist. |
404 | InvalidRouterInterfaceId.NotFound | The specified RouterInterfaceId does not exist in our record. | The error message returned because the specified router interface does not exist. Check whether the specified router interface is valid. |
For a list of error codes, see Service error codes.