Getting Meraki device's Ipv6

[anto_franklin]

In Catalyst Center,we are using the API 'https://api.meraki.com:443/api/v1/organizations/<orgId>/devices'  to get all device details. From the API response we are getting the device  ip address . The existing attributes 'lanIp', 'wan1Ip' and 'wan2Ip'  having ipv4 only. How to get the IPv6 configured in the Meraki device ? we have the lanIpv6 configured in the meraki device.

[sungod]

I'm not sue https://developer.cisco.com/meraki/api-v1/get-organization-devices/ gives IPv6 details.

You don't say what type of Meraki device, but sounds like it may be MX.

These API calls get/update MX WAN interface settings, including IPv6...

https://developer.cisco.com/meraki/api-v1/get-device-appliance-uplinks-settings/

https://developer.cisco.com/meraki/api-v1/update-device-appliance-uplinks-settings/

Can't help with Catalyst Center itself, but back when it was called DNA it did not support many Meraki features, it might be you cannot do everything you want from CC.

[anto_franklin]

@sungod Thanks for the response. we are looking for all type of meraki devices (MS, MR and MX). Currently we are showing meraki device with IPv4  in the catalyst center IPv6  setup. Is there any plan to add ipv6 in the get organizations devices API ?

[sungod]

That'd be a new feature request, you can try suggesting it via the feedback button in Dashboard.

As things are, you'll need to look at device-family specific calls to get the info.

[anto_franklin]

Sure ! will raise a feature request . Do we have the device specific  API calls for all the meraki device types ?

[sungod]

Yep, loads of API calls...

https://developer.cisco.com/meraki/api-v1/api-index/

[anto_franklin]

Do we have any APIs that provide the IPv6 configuration on Meraki devices? I can see the API for appliances only, and it is not working for other Meraki devices

[sungod]

You'd need to go through the API documentation in detail and see what's there, possibly also experiment.

Overall I think there's not yet full support for IPv6 across the API, it may be you won't find all you need (which then takes you back to making feature requests.)