Activates a router interface that is in the Inactive state.
Operation description
After you call the ActivateRouterInterface operation, the router interface enters the Activating state. After the activation succeeds, the router interface enters the Active state.
Before you call this operation, the router interface must be in the Inactive state. The initial state of a newly created router interface is Idle. In non-express connect mode, you can call CreateRouterInterface to create both ends of the connection, call ModifyRouterInterfaceAttribute to configure peer information for each end, and then call ConnectRouterInterface to establish the connection. When the interface is in the Active state, you can call DeactivateRouterInterface to change it to the Inactive state, and then call this operation to reactivate it. You can call DescribeRouterInterfaceAttribute to query the current state.
You cannot activate a router interface that has an overdue payment.
Try it now
Test
RAM authorization
|
Action |
Access level |
Resource type |
Condition key |
Dependent action |
|
vpc:ActivateRouterInterface |
update |
*RouterInterface
|
None | None |
Request parameters
|
Parameter |
Type |
Required |
Description |
Example |
| RegionId |
string |
Yes |
The region ID of the router interface. You can call the DescribeRegions operation to query region IDs. |
cn-hangzhou |
| RouterInterfaceId |
string |
Yes |
The ID of the router interface. Note
The ID of the router interface. This operation supports only interfaces in the Inactive state. If the state does not match, the IncorrectRIStatus error is returned. Newly created interfaces are not in the Inactive state and cannot be directly activated: interfaces created in express connect mode are automatically connected and in the Active state. You must first call DeactivateRouterInterface to change them to the Inactive state. Interfaces created in non-express connect mode are in the Idle state. You must first configure peer information and call ConnectRouterInterface to establish the connection to the Active state, and then call DeactivateRouterInterface. State transition: Active --DeactivateRouterInterface--> Inactive --ActivateRouterInterface--> Active. If the interface is in an intermediate state such as Connecting, Activating, or Deactivating, poll DescribeRouterInterfaceAttribute until the state stabilizes. |
ri-2zeo3xzyf38r4urz**** |
Response elements
|
Element |
Type |
Description |
Example |
|
object |
The response parameters. |
||
| RequestId |
string |
The request ID. |
079874CD-AEC1-43E6-AC03-ADD96B6E4907 |
Examples
Success response
JSON format
{
"RequestId": "079874CD-AEC1-43E6-AC03-ADD96B6E4907"
}
Error codes
|
HTTP status code |
Error code |
Error message |
Description |
|---|---|---|---|
| 400 | IncorrectRIStatus | RouterInterface can be operated by this action only when it's status is Inactive. | You can perform the operation only when the router interface is in the Inactive state. |
| 400 | Forbidden.FinancialLocked | This RouterInterface is financiel locked because of bills outstanding. | |
| 400 | OperationFailed.PconnTrafficNotEnable | The operation is failed because of PconnTrafficNotEnable. | Billing for outbound data transfer is disabled. |
| 400 | Forbbiden | The router does not belong to your account. | The router does not belong to your account. |
| 400 | NotSupportLinkrole | This RouterInterface is not a vlan interface for connection. | The router interface is not a virtual interface for connection. |
| 400 | OppositeRouterInterfaceIsDeleted | The opposite router interface is already deleted. | The opposite router interface has been deleted |
| 400 | InvalidRegionId.NotFound | The specified RegionId does not exist. | The specified region does not exist. |
| 404 | InvalidRegionId.NotFound | The specified RegionId does not exist in our records. | |
| 404 | InvalidRouterInterfaceId.NotFound | The specified RouterInterfaceId does not exist in our records. |
See Error Codes for a complete list.
Release notes
See Release Notes for a complete list.