Avoid Conversion of Parent Network into "Network Container" upon Subnet Creation

Posts: 1
2860     0



We have 2 use cases of creating either any available network(which works perfectly) or user-specified subnet.

Use Case 1(Creation of next available free subnet)

Lets say, we need to create next free /29 under the exisitng /23 Network Container. For this we use below mentioned API. And it works perfectly. 

Step 1:

We get the Network Container _ref by calling below API


This returns lets say _ref = networkcontainer/ZG5zLm5ld:

Step 2:

Request for next available /29 subnet under the Network Container specified by _ref


This returns lets say:


Use Case 2(Creation of user-specified subnet):

Considering I already hold a subnet whose hosts are yet to be used, but should not get modified as its considered reserved.

This is a case, where user specified subnet as : and user sends the request to create subnet as:



        "network": ""


This creates a subnet as, but converts from subnet to a Network Container which we don';t expect it to, as its a Subnet overlap.

Please suggest how can we avoid this overlap or is there any other API or attributes we should send in the POST request to avoid this further.


So, in this case case we typically do not want to get created, rather it should throw back an error, saying that already we have a /28 as a subnet (which is not a network container).

Re: Avoid Conversion of Parent Network into "Network Container" upon Subnet Creation

Posts: 136
2860     0

Thanks Sameer82 for sharing. I moved it to API & Integration. forum.

Check out our new Tech docs website for latest documentation on Infoblox products.
Showing results for 
Search instead for 
Did you mean: 

Recommended for You