- About antonis_sp
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
antonis_sp
Building a reputation
Member since Jan 29, 2018
3 weeks ago
Community Record
78
Posts
66
Kudos
6
Solutions
Badges
01-13-2021
07:41 AM
1 Kudo
ok. Did some tests. Create a new network (wireless network type) and bind it to a combined network template. I cannot add a sensor to the network -> "A bound combined network may only contain bound networks" Create a new network (combined network type) and bind it to a combined network template. I can add a sensor without problems. Check the network type in the network list inside the template. If it is combined there as well, it should work (or it works on my machine only 😋 ). If not, create a new combined network, bind it to your template, and if you can add the sensor, transfer the rest of the equipment to the new network.
... View more
01-13-2021
06:28 AM
1 Kudo
I agree that templates are usefull. There are still things that are working on single networks (in my use cases), but not on templated ones. I will try to do some tests on my lab later, to see if I can replicate this as well. I guess some patience is needed since the sensors are kind of new.
... View more
01-13-2021
01:52 AM
1 Kudo
The problem with creating a new template by copying settings from an old one, is that it keeps the Network type from the original template. So, you cannot create a combined template, using a wireless one for the original settings. What you need to to is Create a new template with copying settings from your current template (let's say "wireless") Create a new template with default settings (which will be "combined" by default) Split the new combined template (will create an "appliance", "wireless" etc template"). Delete the template type that matches the one created on step 1. Combine the rest of templates with the template created in step 1. At least that's how I do it. Maybe there is an easier way (maybe support can change the template to combined?)
... View more
01-13-2021
01:33 AM
I agree. I can only compare the MT10 sensor to other enviroment monitors I have (consumer ones). It seems that the humidity at least is largely affected by small changes in temperature. This is with a balcony door briefly opened in a room. Also as far as accuracy goes, temperature matches other sensors, but four humidity sensors in the same room, all show differnet values (most within +/- 5 of each other). None of my other sensors though is as quick to register changes as the MT10, which is good I guess?
... View more
11-25-2020
12:59 AM
1 Kudo
Cool that we are discussing fridges here I guess... 🆒 While looking for graphs from other sensors in fridges I saw similar results. So problably the 10min period is the fridge's cooling cycle...
... View more
11-24-2020
01:56 AM
Νο, not using vIP (at least while testing).
... View more
11-23-2020
12:41 PM
Yes, I've done a few myself. This is a fresh problem for me and I am trying to understand why the MX reverts to IP 1.1.1.1 when this issue occurs. My setup includes a MS switch between the uplinks and the ISP. The switchport connected to the primary MX uplink, will see a mac address cc:03:d9:9b:XX:XX while the MX boots up, which corresponds to the mac the MX pair uses in it's inside LAN and this confuses me even further... This seems to be go away while deploying the devices in their final setup, s o I'm starting to think that there seems to be something odd happening with the setup I'm using for preconfiguring the devices. I'll have to further look into it.
... View more
11-23-2020
09:20 AM
I am recently hitting an interesting problem with MXs on HA pairs. Procedure to replicatie problem: Setup a HA pair with static IPs for the uplinks. Test everything to be working ok. Reboot or remove power from one of the MX devices. The device may never join the dashboard. Further troubleshooting (pcap from a switch), shows that the problematic MX has booted with an uplink IP of 1.1.1.1 and is looking for 1.1.1.2 . Only way to solve this, seems to be factory resetting the MX and reconfiguring it, or suppling a DHCP on it's uplink. I've seen this on MX68 & 84 on 14.53. I have an open case with support on this, but I was wondering if someone else has seen this behaviour.
... View more
11-05-2020
11:16 PM
Check your log for the security appliance. You can even filter the specific device's mac.
... View more
11-02-2020
12:19 AM
1 Kudo
Blank for me as well... Feeling happy as I had hit the wish button requesting this 😁
... View more
09-25-2020
10:16 AM
Do you have any firewall rules? Make sure user traffic to udp port 53 is allowed.
... View more
08-19-2020
03:19 AM
I've heard other Meraki APs emitting coil whine during high throughput.
... View more
08-02-2020
11:08 PM
That would be an option. But we are talking about a current deployment. Another workaround I found was using tags on APs along with scheduled availability on the SSID, but still.. not as convenient as a "Disable AP" option. Time for the wish button I guess.
... View more
07-30-2020
11:35 PM
1 Kudo
This actually happens. Once Chrome autofilled my account password in the SSID WPA2 psk passphrase. What fun that was, changing the psk key on a country-wide deployment... Just disable form and pass autofill on the dashboard page (browser setting). I don't think it's the dashboard implementation that is the problem, rather than the browser filling in info where it shouldn't.
... View more
07-30-2020
11:26 PM
You think you can, but this is available only for 2.4GHz. Not possible to turn off 5. (At least on MR33s)
... View more
07-30-2020
05:43 AM
Hello all, I'm having an interesting request, were I need to disable the radios on an AP. I see no way around doing this. I cannot cut PoE, since an injector is used. I cannot disable the SSIDs since this AP belongs to a network assigned to a template. I can only find two workarounds move the AP to a new network with disabled SSIDs shut switch port and disable meshing capabilities on the network. Though I feel there should be an option of disabling both radios on an AP basis.
... View more
06-05-2020
12:24 AM
1 Kudo
I think CMNA is still available (I did it last year). As long as you refresh it every 3 years (virtual class), your license/support is extended. If this is valid https://community.meraki.com/t5/FAQ-and-other-resources/CMNA-Refresh/ba-p/38015 once you first refresh your CMNA your license will automatically extend. There is no note for equipmnet replacement, but I suspect EoL equipment will be replaced with newer models when it fails, through an RMA.
... View more
06-01-2020
04:03 AM
1 Kudo
Sometimes, you may need to open a case to support for this problem (provided your uplink doesn't block anything).
... View more
05-22-2020
01:26 PM
@NolanHerring I’ve seen it a lot on PSK SSIDs on MR33. Can’t remember since when, but after wireless health was released, I was trying to investigate the Authentication errors. Issue was seen on a lot of clients, even those who never changed their psk password. Obviously false positives, giving misinformation in the reports. @PawelG i don’t thing it is roaming. I’ve seen it on single AP networks with static clients.
... View more
05-22-2020
08:00 AM
Meraki and Umbrella integration goes beyond simply directing users to Umbrellas DNS servers. You will not need to block access to other DNS services, as this is done by the MR itself. You can read more below. https://documentation.meraki.com/MR/Other_Topics/Manually_Integrating_Cisco_Umbrella_with_Meraki_Networks#DNS_Traffic_Flow It works really well. With MR only or with MX. However, if you do not to go into that deep of an integration (or using other DNS servers for filtering) you could simply block other DNS servers on the firewall).
... View more
05-21-2020
11:46 PM
Testing it on my home lab for now... At least false authentication errors " Client entered wrong password." seem to have been resolved.
... View more
05-21-2020
03:23 AM
Unless something has changed since this https://nolanwifi.com/2017/02/06/merakis-mesh-mess/ Mesh beacon and (probably) network, is not affected by minimum bitrates (if you are thinking bitrates set on SSIDs).
... View more
05-21-2020
02:40 AM
1 Kudo
Keep in mind that the mesh documentation does not recommend using a chain of repeaters. https://documentation.meraki.com/MR/Deployment_Guides/Mesh_Deployment_Guide#Maximum_mesh_hops The meshing algorith probably prefers a direct connection to the root AP if possible.
... View more
05-21-2020
02:29 AM
2 Kudos
Usually on bad cabling, ethernet connections fall back to 10mbit half-duplex, which causes a lot of collisions on transmitted traffic.
... View more
My Accepted Solutions
| Subject | Views | Posted |
|---|---|---|
| 329 | 01-13-2021 01:52 AM | |
| 1648 | 05-19-2020 05:57 AM | |
| 6639 | 01-23-2020 07:46 AM | |
| 641 | 01-16-2020 03:06 AM | |
| 1013 | 01-16-2020 12:10 AM | |
| 377 | 12-02-2019 10:08 AM |
My Top Kudoed Posts
| Subject | Kudos | Views |
|---|---|---|
| 6 | 6639 | |
| 4 | 1178 | |
| 3 | 948 | |
| 3 | 454 | |
| 2 | 677 |
