AssociateVpcCidrBlock
Description
call AssociateVpcCidrBlock to add additional IPv4 network segments to VPC.
Request Method
POST
Request Path
/apsara/route/Vpc/AssociateVpcCidrBlock
Request Parameters Common Parameters
| Name | Location | Type | Required | Sample value | Description |
|---|---|---|---|---|---|
| SecondaryCidrBlock | BODY | string | No | 192.168.0.0/16 | additional IPv4 network segment to be added. 3 can use 192.168.0.0/16, 172.16.0.0/12, and 10.0.0.0/8 standard network segments and their subnets as additional IPv4 network segments for VPC. If you need to use the public address segment as the additional IPv4 network segment of the VPC, please submit a work order. when adding additional IPv4 network segments, the following principles should be followed: cannot start with 0, and the effective range of mask length is 8~24 bits. The additional network segment must not overlap with the VPC main network segment and the added additional network segment. |
| VpcId | BODY | string | Yes | vpc-o6wrloqsdqc9io3mg**** | to add the ID of the VPC with an additional IPv4 network segment. |
| regionId | BODY | string | Yes | No sample value for this parameter. | region id |
| RegionId | BODY | string | Yes | ch-qingdao-env17-d01 | to add the region ID of the VPC with the additional IPv4 network segment. You can obtain the region ID by calling the DescribeRegions interface. |
| version | BODY | string | No | 2016-01-01 | version of api |
Return data
| Name | Type | Sample value | Description |
|---|---|---|---|
| RequestID | string | 1E3D5A1E0-67CA-43DA-24BC-EAF2D5A1E4DC | Request id |
Example
Successful Response example
{
"RequestID":"1E3D5A1E0-67CA-43DA-24BC-EAF2D5A1E4DC"
}
Failed Response example
{
"errorSample":
{
"resultCode":-1,
"resultMsg":"system error",
"result":null
}
}