THE GAME HAS CHANGED

Introducing Infoblox Universal DDI ManagementTM

Watch the launch to discover the new era of management for critical network services. Watch Now

API & Integration, DevOps,NetOps,SecOps

Reply

Does the "next_available_ip" function accept a collection of ipv6networks as the input parameter

New Member
Posts: 9
2134     0

I'm tring to create ipv6fixedaddress with "next_available_ip" function.

My question is ——

Does the "next_available_ip" function accept a collection of ipv6networks as the input parameter

so that when the first network is exhausted, it can still allocate in the second network

 

My request as following:
POST ${iburl}/wapi/v2.12/ipv6fixedaddress

 

{
"duid": "00:00:00:00:00:00:00:00:00:00:00:00:00:01",
"ipv6addr":{
"_object_function": "next_available_ip",
"_object": "ipv6network",
"_object_parameters": {
"network": "2402:2500::1/64,2402:2500::2/64"
},
"_result_field": "ips"
}
}

Re: Does the "next_available_ip" function accept a collection of ipv6networks as the input

[ Edited ]
New Member
Posts: 1
2135     0

@vegachowHealthCareGov wrote:

I'm tring to create ipv6fixedaddress with "next_available_ip" function.

My question is ——

Does the "next_available_ip" function accept a collection of ipv6networks as the input parameter

so that when the first network is exhausted, it can still allocate in the second network

 

My request as following:
POST ${iburl}/wapi/v2.12/ipv6fixedaddress

 

{
"duid": "00:00:00:00:00:00:00:00:00:00:00:00:00:01",
"ipv6addr":{
"_object_function": "next_available_ip",
"_object": "ipv6network",
"_object_parameters": {
"network": "2402:2500::1/64,2402:2500::2/64"
},
"_result_field": "ips"
}
}

Hello,

 

No, the "_object_parameters" field in your request likely doesn't accept a collection of ipv6networks directly for "next_available_ip".

 

This function typically works with a single network as input.

 

Here are two possible approaches:

 

Sequential allocation:

Try allocating from the first network (2402:2500::1/64).

If allocation fails (due to exhaustion), handle the error and attempt allocation from the second network (2402:2500::2/64) in a separate request.

External logic:

Implement logic outside the API request to track available IPs across both networks.
Based on your tracking, choose the appropriate network and include it in the "_object_parameters" field during the API call.

I hope the information may help you. 

 

 

 

 

Showing results for 
Search instead for 
Did you mean: 

Recommended for You