Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
About tech_monkey
tech_monkey
Conversationalist
Member since Feb 7, 2022
Apr 18 2022
Community Record
5
Posts
0
Kudos
0
Solutions
Badges
Apr 11 2022
2:05 PM
Hi ww, Thank you for the reply, I might be misunderstanding. The GET call functions fine and I can retrieve the VPN configuration and the subnets being advertised. When I try the update call I get the same error as above. I have been using the python sdk originally but here is a test snippet for what I'm doing: api_key = "apikey"
test_vmx = "vmx_network_id"
def manual():
import requests
url = f"https://api.meraki.cn/api/v1/networks/{test_vmx}/appliance/vpn/siteToSiteVpn"
payload = json.dumps({
"mode": "hub",
"hubs": [],
"subnets": [
{
"localSubnet": "192.168.1.0/24",
"useVpn": True
},
{
"localSubnet": "192.168.128.0/24",
"useVpn": True
}
]
})
headers = {"X-Cisco-Meraki-API-Key":api_key, "Content-Type":"application/json", "Accept":"application/json"}
response = requests.request("PUT", url, headers=headers, data=payload)
print(response.text)
manual() The above prints: {"errors":["Unrecognized subnet 192.168.1.0/24 for Passthrough MX - only Client VPN subnet(s) permitted"]} The expected behavior would be to replace any existing advertised local networks and replace them with the two 192.x networks. A separate discussion: it would be nice to be able to also include the name in this call. But I can live without that for now. Thanks, Chris
... View more
Apr 11 2022
1:01 PM
Hello, I'm working on automating the local routes that we advertise from our VPN concentrators. I can successfully pull a GET for the local networks being advertised into the Meraki VPN. Something along the lines of the following: [{'localSubnet': 'x.x.x.x/32', 'useVpn': True}, {'localSubnet': 'y.y.y.y/24', 'useVpn': True}] When I try to do an Update api call I get the following: Unrecognized subnet x.x.x.x/32 for Passthrough MX - only Client VPN subnet(s) permitted Which seemed odd. Even if I try to push the same exact configuration back up it fails. Looking at the documentation here I realized this endpoint is only for NAT networks. Is there another endpoint for updating the advertised routes from a concentrator/passthrough network? Or perhaps I'm using it incorrectly? Thanks, Chris
... View more
Feb 9 2022
5:04 PM
FWIW, currently when I pull this endpoint looking at a Z3 network I don't receive a response. When pulling all SSID's as well as each individual ssid number. Thanks
... View more
Feb 7 2022
6:07 PM
That is excellent news! That will give us something to work off of to update our tooling. Thank you
... View more
Feb 7 2022
2:50 PM
We currently use api v0 since it includes support for managing wireless on integrated devices such as Z1/Z3's. With the depreciation announcement we are starting to plan the replacement for this automation. However it appears there is no replacement for these endpoints. Specifically in v0: https://api.meraki.com/api/v0/networks/{{networkId}}/ssids/<ssid> When calling the wireless specific endpoints in v1 I see the following when calling with the python module. meraki.exceptions.APIError: wireless, getNetworkWirelessSsids - 400 Bad Request, {'errors': ['This endpoint only supports wireless networks']} Under the Appliance section of the api documentation I don't see any wireless management endpoints. Am I missing something? Or are there additional endpoints in the near term that are coming to make V1 a full replacement for the features built out in V0? There is discussion here still pointing to v0 endpoints as well.
... View more
© 2024 Cisco Systems, Inc.
