Adding a Secondary CIDR Block to a VPC
Function
The IPv4 CIDR block you specify when you create a VPC is the primary one. The primary CIDR block cannot be changed after the VPC is created. If IP addresses in the primary CIDR block are insufficient, you can call this API to add a secondary CIDR block to a VPC.
Calling Method
For details, see Calling APIs.
URI
PUT /v3/{project_id}/vpc/vpcs/{vpc_id}/add-extend-cidr
|
Parameter |
Mandatory |
Type |
Description |
|---|---|---|---|
|
project_id |
Yes |
String |
|
|
vpc_id |
Yes |
String |
|
Request Parameters
|
Parameter |
Mandatory |
Type |
Description |
|---|---|---|---|
|
dry_run |
No |
Boolean |
|
|
vpc |
Yes |
AddExtendCidrOption object |
|
|
Parameter |
Mandatory |
Type |
Description |
|---|---|---|---|
|
extend_cidrs |
Yes |
Array of strings |
|
Response Parameters
Status code: 200
|
Parameter |
Type |
Description |
|---|---|---|
|
request_id |
String |
|
|
vpc |
Vpc object |
|
|
Parameter |
Type |
Description |
|---|---|---|
|
id |
String |
|
|
name |
String |
|
|
description |
String |
|
|
cidr |
String |
|
|
extend_cidrs |
Array of strings |
|
|
status |
String |
|
|
project_id |
String |
|
|
enterprise_project_id |
String |
|
|
created_at |
String |
|
|
updated_at |
String |
|
|
cloud_resources |
Array of CloudResource objects |
|
|
tags |
Array of ResponseTag objects |
|
|
Parameter |
Type |
Description |
|---|---|---|
|
resource_type |
String |
|
|
resource_count |
Integer |
|
|
Parameter |
Type |
Description |
|---|---|---|
|
key |
String |
Definition: Tag key. Range:
|
|
value |
String |
Definition: Tag value. Range:
|
Status code: 202
|
Parameter |
Type |
Description |
|---|---|---|
|
request_id |
String |
|
|
error_msg |
String |
|
|
error_code |
String |
|
Example Requests
Add the secondary CIDR block 23.8.0.0/16 to the VPC whose ID is 0552091e-b83a-49dd-88a7-4a5c86fd9ec3.
PUT https://{Endpoint}/v3/{project_id}/vpc/vpcs/0552091e-b83a-49dd-88a7-4a5c86fd9ec3/add-extend-cidr
{
"vpc" : {
"extend_cidrs" : [ "23.8.0.0/16" ]
}
}
Example Responses
Status code: 200
Normal response to the PUT operation. For more status codes, see Status Code.
{
"request_id" : "84eb4f775d66dd916db121768ec55626",
"vpc" : {
"id" : "0552091e-b83a-49dd-88a7-4a5c86fd9ec3",
"name" : "vpc1",
"description" : "test1",
"cidr" : "192.168.0.0/16",
"extend_cidrs" : [ "23.8.0.0/16" ],
"enterprise_project_id" : "0",
"tags" : [ {
"key" : "key",
"value" : "value"
} ],
"cloud_resources" : [ {
"resource_type" : "routetable",
"resource_count" : 1
} ],
"status" : "ACTIVE",
"project_id" : "060576782980d5762f9ec014dd2f1148",
"created_at" : "2018-03-23T09:26:08",
"updated_at" : "2018-08-24T08:49:53"
}
}
Status code: 202
Normal response to the specified preflight request of API V3. For more status codes, see Status Code.
{
"error_msg" : "Request validation has been passed with dry run...",
"error_code" : "SYS.0202",
"request_id" : "cfd81aea3f59eac7128dba4b36d516c8"
}
Status Codes
|
Status Code |
Description |
|---|---|
|
200 |
Normal response to the PUT operation. For more status codes, see Status Code. |
|
202 |
Normal response to the specified preflight request of API V3. For more status codes, see Status Code. |
Error Codes
See Error Codes.
Feedback
Was this page helpful?
Provide feedbackThank you very much for your feedback. We will continue working to improve the documentation.