Infoblox’s global team of threat hunters uncovers a DNS operation with the ability to bypass traditional security measures and control the Great Firewall of China. Read about “Muddling Meerkat” and the many other threat actors discovered by Infoblox Threat Intel here.

API & Integration, DevOps,NetOps,SecOps

Reply

Grid Version via API

New Member
Posts: 2
3560     0

Hello,

 

Does anyone know where to get the grid and/or member versions via the api?   I would have thought its in member node_info, but it doesn't seem to be there.  Also, tried to grab it via upgradestatus, but I can't get the current_version field to return.  Not seeing any other place in the wapidoc that lists the version.

 

Thank you

Chase Manz

Re: Grid Version via API

Moderator
Moderator
Posts: 298
3561     0

Try this for grid:

 

curl -k1 -u admin:infoblox -X GET 'https://192.168.1.2/wapi/v2.10/upgradestatus?type=GRID&_return_fields%2b=current_version_summary'

and this for individual members, such as during an upgrade window:

 

curl -k1 -u admin:infoblox -X GET 'https://192.168.1.2/wapi/v2.10/upgradestatus?type=VNODE'

Re: Grid Version via API

New Member
Posts: 2
3561     0

Thank you for your help, I had tried that, but it turned out to be a wapi version issue and I had to use a slightly newer version like 2.10 which worked.  

Re: Grid Version via API

Moderator
Moderator
Posts: 298
3561     0

Aha!  I always try to use the highest WAPI version from the oldest currently supported NIOS version.  That way my examples are pretty much up-to-date without being bleeding edge.  Today that would be NIOS 8.4.x and WAPI 2.10.

 

If you do a lot of automation, you can also adjust your toolkits to ask for the supported WAPI versions, using the schema query, and then use the highest version listed.

 

curl -k1 -u admin:infoblox -X GET 'https://192.168.1.2/wapi/v1.0/?_schema'

 

 

Showing results for 
Search instead for 
Did you mean: 

Recommended for You