Meraki

rhbirkelund · ‎Mar 18 2023

What you are probably looking for is the C++ equivalent to a destructor. Assuming that the meraki.DashboardAPI() object has a __del__() method, you can simply use del dashboard. Example: dashboardObj = meraki.DashboardAPI() del dashboardObj

rhbirkelund · ‎Mar 15 2023

But it still doesn't change the fact the there is still no documentation on the Meraki proprietory reason codes, as well as detailed information on what they mean/are caused. 🙂

rhbirkelund · ‎Mar 15 2023

If you clear your browser cache, does the tag button show up again? Perhaps you can check the Change Log, to see if permissions have changed?

rhbirkelund · ‎Mar 14 2023

I can't exactly say what Reason 103 is, but according to StackExchange , it could have something to do with the re-keying process, where the client is sending an M2 with what the AP considers a MIC error. Reducing the EAPoL timeourt might do the trick.

rhbirkelund · ‎Mar 5 2023

Hm.. Thanks for clearing that up! 😄

rhbirkelund · ‎Mar 5 2023

I'm not that too ashamed to admit when I'm mistaken. I hate it when it happens, but it does so happen. So by all means, correct me if I'm wrong. If Spoke A is configure with Hub A and no other, and Spoke B is configured with Hub B, and no other in the list, is Spoke A still able to reach Spoke B? Will Spoke A routingtable be populated with Spoke B subnets via Hub A -> Hub B?

rhbirkelund · ‎Mar 4 2023

You can not configure a site as a Spoke, without also setting a Hub Site. And yes, unless there is some routing between the two Hub sites, each Spoke need to connect to the same Hub, for traffic to move between spoke sites.

rhbirkelund · ‎Mar 2 2023

I had some spare time these last few weeks, and I like to take up an API challenge or two on occasions. Doubt I'll ever make it to the AllStars. 😉 Congratulations to every one, making MoTM. 🙂

rhbirkelund · ‎Mar 2 2023

Paging Dr. @JohnIngram 🙂

rhbirkelund · ‎Mar 1 2023

I'm wondering if it was intended by Meraki-side that the other specialist exams would recertify the Meraki Cert, taken the Meraki FAQ into consideration. Perhaps there's miscommunication, seeing as it wasn't untill now CMSS recertifications were going to happen?

rhbirkelund · ‎Mar 1 2023

All EoL Products and their dates are listes on https://documentation.meraki.com/General_Administration/Other_Topics/Meraki_End-of-Life_(EOL)_Products_and_Dates As mentioned, there is not API for this (but perhaps you could submit a feature request for this), however, perhaps you could look into web scraping with a python script of the above page? There's a tutorial on Web Scraping with Python here; https://www.freecodecamp.org/news/web-scraping-python-tutorial-how-to-scrape-data-from-a-website/

rhbirkelund · ‎Mar 1 2023

Yeah, well.. As soon as the traffic leaves the MX, it's out of your hands. I might want to work with the voice provider in order to exactly determine what requirements are for the Voice application. Also you can try an work with your internet provider to see if there's something they can do. Besides having the MX continously ping 8.8.8.8, I have a habit of also configuring my ISP next hop address (ISP Default Gateway), as well. If pings are choppy there, maybe it's the Provider edge that has a problem.

rhbirkelund · ‎Mar 1 2023

Following the best practices guidance on https://documentation.meraki.com/Architectures_and_Best_Practices/Cisco_Meraki_Best_Practice_Design/Best_Practice_Design_-_MR_Wireless/Wireless_VoIP_QoS_Best_Practices Try: * On the SSID, set Trafficshaping rules for "All VoIP and video conferencing" Ignore SSID per client limit PCP 6 / DSCP tag 46 (EF) * On the Switch Settings Page under Quality of Service section, set the Voice VLAN Protocol to Any DSCP: Trust Incoming DSCP. * On the MX, create a Group policy, and assign that to the VLAN interface on the MX * In said Group Policy, configure same traffic shaping rules as those on the SSID Type: "All VoIP ..." Limit: "Ignore Network per-client limit" PCP: 6 DSCP 46 (EF) Try and see how this works for you...

rhbirkelund · ‎Mar 1 2023

Yeah... I'm guessing some Dev is cutting corners or doing something "clever" in binary conversion.. 😉 I'd love to see the patch on that one tnough!

rhbirkelund · ‎Mar 1 2023

Corrected an issue that resulted in client traffic being will be dropped by MX65(W), MX67(C,W), and MX68(W,CW) appliances when 1) The client was connected to a LAN port with 802.1X authentication enabled and 2) The VLAN ID of the port was configured to 16, 32, 48, 64, 80, 96, 112, 128, 144, 160, 176, 192, 208, 224, or 240. That's been there for a while. 😄

rhbirkelund · ‎Mar 1 2023

According to my dashboard on Certmetrics, no.

rhbirkelund · ‎Mar 1 2023

To my knowledge no. I passed ENCOR exam about a year ago, and that didn't seem to extend my CMSS either.

rhbirkelund · ‎Feb 27 2023

You can do just whatever you like - put it all in a single VLAN, or create VLANs for every type of device. You can also have as many Access Points in a Network as you want. They will all broadcast the same SSIDs.

rhbirkelund · ‎Feb 27 2023

@Ryan_Milesout of curiousity, what are your thoughts on models as WAN Breakout switch? I usually see customers opting for the small 8-ports MS120 switch, but seeing as it will be handling "raw" internet traffic? A customer I have, which has just been through this maneuver used an MS410.

rhbirkelund · ‎Feb 27 2023

You can definitely break them out into a network of their own, but I'm not sure if that will make you clear of the public addresses in the Clients page etc. Bit I'd love to here the result. But still the other point stand, although you can better schedule the WAN switch firmware upgrade, in the sense that it won't happen at the same time as your downstream LAN.

rhbirkelund · ‎Feb 27 2023

I've done this a couple of times, and while it's not really the most optimal way of doing it, it's certainly a possibility. There are some caveats with using Meraki Switches as WAN breakout switches. One aspect that you need to have in mind is that Meraki needs to have an IP address on it's Management. And that's whether you're using it on the LAN or in a WAN breakout setup. So you need a connecting from the WAN switch and back to the LAN side of MX, for it to obtain an address for it's Management. In terms of when you configure the switches, just remember, that it is imperative that the LAN side VLANs are not mixed with the WAN side i.e. do not trunk the WAN side VLANs into your LAN side. Another issue is that fact that during maintenance windows where you perform firmware upgrades, you'll experience that your entire Meraki organization will go offline at least twice; once during MX upgrade, and second during MS upgrades. The WAN breakout switches will upgrade at the same time as the rest for your switching infrastructure, unless you define upgrade groups for staged upgrades. And in the end, you can never guarantee that something doesn't go wrong during Firmware upgrades, that end up causing a Loop between you LAN side and WAN side. The third caveat is that, your Network Clients page will also contain publicly routed addresses, and you'll end up seeing some odd statistics in the Applications details. All this being said, as long as you are aware of what you are doing, this is certainly a possible setup. Like I said, I've done it a couple times, but mainly out of necessity, rather than opportunity. But these are just my two cents.. 🙂

rhbirkelund · ‎Feb 26 2023

I think there are some concepts regarding Meraki you'd might need to research. The Meraki Dashboard is not some system that is hosted locally on the Meraki devices themselves. The Meraki Dashboard is hosted centrally in the "The Cloud", and is available at https://dashboard.meraki.com. When you buy your first Meraki product you browse to the Meraki Dashboard, where you create an account, and claim your Meraki Device by serial and a License by serial. Often times both Hardware and license is shipped togoether, bundled in a Meraki Order No. Typically, that number starts with 5S, nowadays. After claiming your devices and adding them to a Meraki Network, you are more or less ready to go. What's next is to ensure that your Meraki device can contact the Meraki Cloud Registry, by any means possible using the internet. If you have an internet connection, you can connect your Meraki device to that, and it will attempt to contact Meraki Cloud by itself. You don't need to know anything about how it connects to the Meraki Cloud Registry. In terms of basic configuration, you don't necessarily need to do any; as long as the Meraki Device can achieve an IP address through DHCP and there is a internet connection. It is imperative, that Meraki has internet connectivity. Otherwise, you Meraki Device won't work. This is also one of the reasons that Meraki is considered Cloud-based and Cloud-managed networking. I'd suggest perhaps you watch this videon on YouTube.

rhbirkelund · ‎Feb 26 2023

Unless you can get Sensibo to improve their product, or give you some tools to manage their devices, I'm afraid there might not be much to do. It is the device that determines what AP to connect to and when it's time to roam.Had it been e.g. a Windows Client with Intel Wireless, you'd most likely have to options on the Wireless NIC to set roaming aggressiveness, making the device more prone to roam to better APs, based on the current RF environment. So if you'd want to have your Sensibo device to connect to a specific AP, you'll have to look into making that single AP look more favorable from an RF point of view, than the other APs. The adverse effect would be that it would make all other wireless clients try to favor that AP in stead of the rest of the infrastructure. Alternatively. you could create an Facility SSID called, say, HVAC, and have that SSID only broadcasted on tagged APs. In your case that specific AP in the computer room. Another possible reason could be that the AP in the Computer room is loaded, in terms of clients. Perhaps, it owuld help to disable Client Balancing on the Radio Profile. However, with that being said, is it really an issue that the Sensibo device is connecting to a different AP than intended? Does it have a poor connection on the "wrong" AP?

rhbirkelund · ‎Feb 24 2023

You can't use the "Postman Lite" on the Meraki API Documentation for configuring multiple ports at a time. The "postman lite" on meraki.io only serves as a demo/quick test of the API Endpoint. If you need to configure multiple ports at a time, you either need to look into scripting using e.g. Python, or install Postman locally on your machine. I'm told you can make loops in Postman, so you can configure more than one port at a time, but I have no experience with Postman, so you'll most likely be on your own, or ask somebody else for help.

rhbirkelund · ‎Feb 24 2023

Could it be that your $url statement is set somewhere else aswell, and it's that statement that's being used? According to your error message, if failing on the endpoint ressource /devices/{serial}/switch/ports/{portId}, but the ressource for cycling the port is /devices/{serial}/switch/ports/cycle as you've also stated yourself. So I'm assuming that $url is being set somewhere to /devices/{serial}/switch/ports/{portId} I haven't worked with PHP for a long time, but I think it looks correct.

About rhbirkelund

rhbirkelund

Community Record

Badges