Modifies the weight of a destination-based route for an IPsec-VPN connection.
Operation description
-
ModifyVcoRouteEntryWeight is an asynchronous operation. After you send a request, the system returns a request ID and runs the task in the background. You can call the DescribeVpnConnection operation to query the status of the IPsec-VPN connection and check whether the weight of the destination-based route is modified.
-
If the IPsec-VPN connection is in the updating state, the weight of the destination-based route is being modified.
-
If the IPsec-VPN connection is in the attached state, the weight of the destination-based route is modified.
-
-
Do not repeatedly call the ModifyVcoRouteEntryWeight operation on the same IPsec-VPN connection within a short period of time.
Try it now
Test
RAM authorization
Request parameters
|
Parameter |
Type |
Required |
Description |
Example |
| RegionId |
string |
Yes |
The region ID of the IPsec-VPN connection. You can call the DescribeRegions operation to query the most recent list of regions. |
cn-hangzhou |
| VpnConnectionId |
string |
Yes |
The ID of the IPsec-VPN connection. |
vco-p0w2jpkhi2eeop6q6**** |
| RouteDest |
string |
Yes |
The destination CIDR block of the destination-based route to modify. |
192.168.10.0/24 |
| Weight |
integer |
Yes |
The current weight of the destination-based route. Valid values:
|
100 |
| NewWeight |
integer |
Yes |
The new weight to assign to the destination-based route. Valid values:
|
0 |
| NextHop |
string |
Yes |
The next hop of the destination-based route to modify. |
vco-p0w2jpkhi2eeop6q6**** |
| OverlayMode |
string |
No |
The tunneling protocol. Set the value to Ipsec (IPsec tunneling protocol). |
Ipsec |
| ClientToken |
string |
No |
The client token used to ensure the idempotence of the request. You can use the client to generate the token, but you must ensure that the token is unique across 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. |
123e4567-e89b-12d3-a456-4266**** |
Response elements
|
Element |
Type |
Description |
Example |
|
object |
The response parameters. |
||
| RequestId |
string |
The request ID. |
9496F8A-82F4-3130-A51A-2266ACC799B4 |
Examples
Success response
JSON format
{
"RequestId": "9496F8A-82F4-3130-A51A-2266ACC799B4"
}Error codes
|
HTTP status code |
Error code |
Error message |
Description |
|---|---|---|---|
| 400 | Resource.QuotaFull | The quota of resource is full | |
| 400 | VpnConnection.Configuring | The specified service is configuring. | The service is being configured. Try again later. |
| 400 | VpnConnection.FinancialLocked | The specified service is financial locked. | The error message returned because the service is locked due to overdue payments. |
| 400 | VpnRouteEntry.AlreadyExists | The specified route entry is already exist. | The route already exists. |
| 400 | VpnRouteEntry.Conflict | The specified route entry has conflict. | Route conflicts exist. |
| 400 | TaskConflict | The operation is too frequent, please wait a moment and try again. | Your requests are too frequent. Try again later. |
| 403 | Forbbiden.SubUser | User not authorized to operate on the specified resource as your account is created by another user. | |
| 403 | Forbidden | User not authorized to operate on the specified resource. | You do not have the permissions to manage the specified resource. Apply for the permissions and try again. |
| 404 | InvalidVpnConnectionInstanceId.NotFound | The specified vpn connection instance id does not exist. | The specified vpn connection instance id does not exist. |
See Error Codes for a complete list.
Release notes
See Release Notes for a complete list.