getOrganizationApplianceVpnStatuses is messy

[RaphaelL]

Hi ,

I have multiple issues with this endpoint + it's dashboard counterpart. 

1- It is a "status" endpoint but it is returning a list of exportedSubnets which are config related. Bit confusing. 

2- We have a list of merakiVpnPeers with their status. 2 major problems.

• The list is returned in a alphabetical order instead of the priority order from the dashboard.Pretty much can't trust that info at all 💀
• We don't have the uplink info related. Which uplink was used to determine that info ? Wan1 ? Wan2 ? Who knows ! 😍

3- We don't have the info or any other endpoint to get the status of the VPN registry. However this info is somewhat available on the dashboard (this MX has WAN1,WAN2,Cellular up and running 😞 

• once again , can't figure out if both WANs are ok or not.
• Sometimes you get funky messages when there's an error. I will try to find a screenshot. The message is useless because it doesn't contain any info usefull for troubleshooting. EDITED with the screenshot
• 

I have serious doubt on how large enterprises are monitoring their VPN Status + VPN registry status. It seems impossible at the moment and it has been like that for years. Really curious to see if I'm missing something obvious.

Snipet of what is returned via the API : 

{
    "networkId": "xxxxxxx",
    "networkName": "xxxxxxxx",
    "deviceSerial": "xxxx-xxxx-xxxx",
    "deviceStatus": "online",
    "uplinks": [
      {
        "interface": "wan1",
        "publicIp": "xx.xx.xx.xx"
      },
      {
        "interface": "wan2",
        "publicIp": "xx.xx.xx.xx"
      },
      {
        "interface": "wan3",
        "publicIp": "xx.xx.xx.xx"
      }
    ],
    "vpnMode": "spoke",
    "exportedSubnets": [
       redacted ###
    ],
    "merakiVpnPeers": [
      {
        "networkId": "xxxxxxxx",
        "networkName": "HUBAAAA",
        "reachability": "reachable"
      },
      {
        "networkId": "xxxxxxxxxx",
        "networkName": "HUBAAAB",
        "reachability": "reachable"
      },
      {
        "networkId": "xxxxxxxx",
        "networkName": "HUBAAAC",
        "reachability": "reachable"
      },
      {
        "networkId": "xxxxxxxxx",
        "networkName": "HUBAAAD",
        "reachability": "reachable"
      }
    ],
    "thirdPartyVpnPeers": []
  }

Montly rant

[ww]

I agree.

For vpn status i think its better to look at this api and use a low time range. 

https://developer.cisco.com/meraki/api-v1/get-organization-appliance-vpn-stats/

Then check for example if Mos is not 0 or a certain loss %.

[RaphaelL]

Yes ! Good point , this endpoint does have WAN granularity ( if that's the proper word for that lol )

However , same issue from #2.A. Peers are in alphabetical order which is annoying.

[Oren]

Thanks for the feedback, @RaphaelL.
This operations is still in beta and not widely used yet, which means we can still influence and enhance it to address your comments.
I'll make sure the relevant team takes your feedback into consideration.

[RaphaelL]

Oh !  I didn't know ! 

When I looked at the API index , it didn't mention beta like I'm used to : 

[Oren]

I might have mixed it with a similar operation. Let me take the feedback with the team, and we'll try to find a way to address it.