Meraki

Alex_3dEYE · ‎Jan 10 2024

The connection works at first for a few days or even weeks but then all of a sudden the camera stops working and when I start tracing back what is going on I discover that both camera and cloud box are working well but cannot talk to each other. I tried pinging the camera from the cloud box but the ping request is not getting through. At the same time a lot of other cameras are working fine on the same cloud box. The weird part is that a 3rd device on the same network can easily reach both camera and cloud box, this further suggests that the network configuration of all devices is appropriate and the issue is only in the link between cloud box and camera. I'm not sure I understand this question though: Are you on the latest code for all devices involved? What code do you refer to? Thank you for the feedback and suggestions.

GIdenJoe · ‎Dec 14 2023

That's weird and shouldn't officially work.

John_on_API · ‎Dec 12 2023

@MartinS wrote: Fantastic, getAdministeredIdentitiesMe is exactly what I'm looking for, thanks very much @John_on_API ! Just as a side point, is there a best practice guide on how managed services organisations should use accounts and generate API keys when integrating with 3rd party systems like Highlight? I ask because generating API keys on user accounts associated with individuals is dangerous because if that individual leaves the MSP, their account gets suspended and that kills the key (we've seen this happen several times). I'm guessing the right thing to do is have a key associated with a non-personal api@serviceprovider.com account where the credentials are carefully managed and not widely known, but where emails to api@serviceprovider.com do get delivered somewhere? I'd recommend that approach in most scenarios for now. The email should be something that's clearly named and helps identify who manages the key/credentials, e.g. serviceaccount@partnerdomain.com. As the partner, you should not share these credentials (password or API key) with the customer. Customers who want to revoke partner access would simply delete the given admin from their admins list. The customer would never have the API key for that identity.

alemabrahao · ‎Dec 12 2023

I suggest you open a support case, but have you tried with other browsers?

GIdenJoe · ‎Dec 11 2023

As long as you don't have a circle of switches the outage should be quite minor. RSTP reconverges by blocking the links between two switches while sending a proposal BPDU and the other switch should immediately send a response if it agrees. If you have a good star topology the outage should be minimal (less than 2 seconds). If you have a circle you could experience a count to infinity issue where you go down for a while before the topology can resolve itself.

noobnetwizard · ‎Dec 7 2023

I did not mean to make anyone bow! You were right from start to end according to official documentation.(Now I kinda feel like a J*rk) I just wanted to make sure we all are on same page... ... ... and depending on my lab result ...All (me included) bow to @Ryan_Miles ...:D

Capt_Caaaveman · ‎Dec 6 2023

Im using this https://developer.cisco.com/meraki/build/meraki-postman-collection-getting-started/introduction/#basics thanks

RaphaelL · ‎Dec 6 2023

Annnnnd make sure that your licence are not expired ! Been there.

GreenMan · ‎Dec 6 2023

This generally isn't possible, I'm afraid. For limited duration testing / PoC, Meraki offer free trials, which can be claimed into a separate Dashboard Organization. Bear in mind that some architectures pretty much require a common Organization to be used: i.e. if you wanted a test SD-WAN branch, you'd really need it to be in the same Org as the Hub MXs to which the branch MX would inter-connect. For Cisco partners, purchase of similar equipment can be done on a Not for Resale basis, with appropriate discounts.

GreenMan · ‎Dec 6 2023

In which case I refer my honourable friend to my earlier reply... A common set of MR36 APs should be a good starting point. You may want to survey to ensure you're covering the areas you require.

GreenMan · ‎Dec 6 2023

While OSPF is supported, as per the documentation linked previously by @Badr-eddine, note the phrase 'to advertise remote VPN subnets'. You can't use OSPF to learn the subnets on your local LAN (from a Layer 3 switch, for example) and/or advertise the default route to it. You would need to use static routing for this - perhaps between Virtual IPs, if you want a degree of resilience.

RicardoD · ‎Dec 5 2023

Even if you're using a Trial account and Trial products, you still can use our full API toolset including Postman. You just need to enable your API Key (https://developer.cisco.com/meraki/api-v1/authorization/#authorization) and then use the Postman Collection (https://developer.cisco.com/meraki/build/meraki-postman-collection-getting-started/introduction/#dashboard-api-and-postman)

alemabrahao · ‎Dec 4 2023

Strange, I always converted without needing to get in touch with anyone.

PhilipDAth · ‎Nov 30 2023

Note that while you can apply traffic priorities to outbound traffic, nothing is applied to inbound traffic (only your ISP can decide the priority here as they are the ones sending it). A guest could send a 100 byte request to download 10GB of data. You can apply the priority to the 100 bytes. You can't assign a priority to that 10GB that gets downloaded. As already mentioned, SSID bandwidth limits are often a better option for this case. A hard limit of how much bandwidth that can be used. https://documentation.meraki.com/MR/Firewall_and_Traffic_Shaping/Traffic_and_Bandwidth_Shaping Also note you can apply both a per-user limit and an SSID limit. Using the per-user limit as well prevents one person from making the performance suck for every other user.

Abhay1267 · ‎Nov 29 2023

I can change DHCP from switch to MX, but this is not the solution. Will try this on weekend

PhilipDAth · ‎Nov 27 2023

The change log mentioned by @alemabrahao will give the most precise details of what happened.

BlakeRichardson · ‎Nov 26 2023

Webex is not really the place to public forums. You have the community here and there is an unofficial one on Reddit. There is a massive chance that most Meraki customers and MSP don't even use Webex so even if there was the user base would be small. Support are available via email or phone.

thomasthomsen · ‎Nov 26 2023

Well the though was that when you utilize Guest VLAN, then the client would be put into that VLAN on an access-reject. And I would just like to return some more config to that Guest access. https://documentation.meraki.com/@api/deki/files/3974/MS_802.1X_auth_flow_chart.png?revision=1&size=bestfit&width=436&height=599

Schiller · ‎Nov 24 2023

Yes, I did thank you.

alemabrahao · ‎Nov 23 2023

😂

janos_szonyi · ‎Nov 22 2023

Thank you guys. I will open a case with support then.

Inderdeep · ‎Nov 20 2023

Cheer with Beer my dear @PhilipDAth

GreenMan · ‎Nov 20 2023

Yes - remember that those credentials are used to verify your IDP, not the individual user; that IDP will separately have to authenticate each user.

sledge121 · ‎Nov 20 2023

Using a dummy device is an interesting one but I currently don't have the time to invest in testing it. I've told the customer the feature isn't available and they need to reach out to their Meraki account team. Thanks.

rdominguez · ‎Nov 17 2023

Hello @rhamersley As @alemabrahao indicated, getting a packet capture and checking logs on your Radius server are good starting points. The packet captures can provide details in terms of whether or not the traffic is reaching the Radius server as well as the responses sent out by the server, if any. In addition to that, Meraki does have a guide for troubleshooting Radius issues. You can find it here: https://documentation.meraki.com/MR/Encryption_and_Authentication/RADIUS_Issue_Resolution_Guide

About GreenMan

GreenMan

Community Record

Badges