Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Register or Sign in
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
- About MarcelTempelman
About MarcelTempelman
MarcelTempelman
Getting noticed
Member since Jul 10, 2019
Feb 23 2024
Community Record
51
Posts
14
Kudos
0
Solutions
Badges
Feb 13 2024
11:54 PM
Good to hear and it was a pleasure to help!
... View more
Dec 18 2023
12:56 AM
2 Kudos
Hi, when I was playing with the new AP Neighbor option I saw that AutoRF makes strange choices when it comes to channel planning: We're mostly using 40Mhz channels on 5Ghz and what I see is: - Some channels have the lower channel as primary channel, others have the upper channel as primary - AutoRF does not avoid overlap : I see often secondary channels overlapping due to this - AutoRF thinks that Channel 64/100 is also a perfect pair (have never seen this before with other vendors). Although this might technically all work fine (have had no complaints) but I'd like to see a bit more predictability ( In critical environments I opt for a static channel plan) : so no overlap and being able what to use as primary channel.
... View more
Jun 28 2023
12:21 PM
1 Kudo
9m is just above the recommended height for the 3-D antenna. It might work but you might experience some problems at the ground level. The 3-E is more suited for that. The antenna portfolio is still the same. Must say after doing a few Cisco jobs again, Meraki has a better antenna portfolio than Cisco.... (more choice). A chat or call is no problem.
... View more
Jun 26 2023
2:45 AM
Be sure spanning-tree is working properly between the MS390 and the HP Procurve switch. A wrong config might block traffic in VLANs between the switches (MS390 runs MST (i believe) and the Procurve can run this as well (default spanning-tree is disabled on a procurve).
... View more
Apr 19 2023
5:33 AM
2 Kudos
Found this thread after PRTG discovered a SNTP service on a MX. I've tried to configure a MX as a NTP-server on a Catalyst switch..... and it works !
... View more
Nov 22 2022
11:41 PM
Thank you. We've reinstated the ASA for Anyconnect and we're going to look for a suitable solution.
... View more
Nov 8 2022
4:45 AM
1 Kudo
Hello, we have a few customers who require users to use a VPN client to access to other local VLANs also when they are at the office or workplace (so not at a remote site). Normally these users only have access to a few local resources and the Internet but with an established VPN connection they have access to more resources/VLANs. Question: Does the MX support Client VPN and/or AnyConnections from LAN-clients? It seems it does not support it with AnyConnect. If so we need to keep the old ASA up and running. With kind regards, Marcel Tempelman.
... View more
Jul 13 2022
12:29 AM
I have tried setting the power manually but even then the dashboard keeps telling me the max output power is lower than expected. I haven't done any measurement tests to see if the measured output power increases when setting it manually higher. If so the dashboard is not reporting it right but considering the explanation that this is "working as designed" I doubt there will be any difference between the dashboard and the actual output power of the AP.
... View more
Jun 21 2022
5:20 AM
I'm trying to wrap my head around this how we should consider this in a design: Let's say I design a VoWLAN network with every AP (MR46) at 14 dBm EIRP (@ 5Ghz). This means I set the AP in the dashboard at 8dBm (as far as I know that's always the AP output power without the antenna) and with the antenna gain I end up at 14dBm EIRP. Does the beam forming gain only add up when I allow more output power than 14 dBm?This could result in sticky clients. When beam forming kicks in does the output power of the AP go back to 2 dBm to compensate the 6 dBm gain to keep the max at 14 dBm? I'd like to hear Meraki explaining this because if the behavior is unclear you can end up with pretty wonky designs.
... View more
Jun 20 2022
4:58 AM
Just checking my case notes : my test on channel 100 (20mhz) saw the output power max out at 13dBm. The 3F gain is almost 11 dBm so 13+11=24 dBm which is 6 dBm below the regulatory 30 dBm. This makes sense if beamforming takes 6 dBm... (why isn't this in the datasheet ?).
... View more
Jun 20 2022
4:21 AM
1 Kudo
I have a customer with MR46E with MA-ANT-3F antennas and it's impossible to get the output power above 6dBm on UNII-1 and UNII-2e (max EIRP 17dBm instead of the expected max 23 dBm). It allows 12 dBm on UNII-2e channels. On 2.4Ghz 3 dBm is the max output power. Support could not give me an answer (like above) why the settings are lower than the MR42E (MR42Es do not have these limitations or uses the 3dBm margin, they are 3x3:3). All in all the dashboard is a bit confusing when it comes to output power and EIRP values. Edit : customer is in ETSI region also.
... View more
May 24 2022
11:42 PM
1 Kudo
I often use MA-ANT-3-E6 antennes to cover ground areas if the ceiling is above 8m (in designs). Below that I'd advise you to use a downtilt omni antenna. Main advantage of the 3-E is that you get a smaller coverage cell than with an omni so if roaming is required this will give you a more predictable wireless environment. This is a MR42E with a 3-E antennes at approx 11m in a warehouse. 3-F antennes are used for getting the signal between the racks (also mounted at 11m) and standard APs at the docks (mounted at 3m).
... View more
May 24 2022
7:48 AM
MX 16.16.2 promises fixes for some models: Fixed an issue on MX67(C,W), MX68(W,CW), MX75, and MX85 appliances that could cause ports to occasionally disconnect and reconnect (“flap”) when connected to some devices.
... View more
May 10 2022
8:24 AM
The Meraki example which I posted was during a MS Teams call from my iPhone 8 (started at 15:16 and took 6 minutes). The call was quite good (some glitches). The experience with the Gigaset smartphone was quite horrible but that's because it's crap hardware (sticking to APs up to -90+ dBm.......). But that aside when I look at the iPhone roaming the number do not make any sense to me. When I look at your example it seems to make sense.
... View more
May 10 2022
7:03 AM
Yesterday I did some testing with a Android smartphone from Gigaset. These phones are horrible when it comes to roaming. So I made a round with my iPhone 8. If I look at the timeline from a wireless troubleshooting perspective then this is a useless tool. The reporting is not consistent (sometimes the time to connect is missing) and the reported time values are nowhere near what you want to see when checking requirements. For example if you check Voice over WLAN requirements you want to see if the device roams within 150ms. Do not know who developed this but this is developed without any knowledge about wireless troubleshooting. This is useful information (Cisco Wireless Debug Analyzer):
... View more
May 9 2022
2:21 AM
Thanks for the update! This afternoon I'll be going on site and will try to collect some data about roaming (there are issues with a Gigaset android devices) with different devices and see if it corresponds with what the dashboard is telling me.
... View more
May 9 2022
2:11 AM
Any news on ths topic ? I still see 'time to connect' values between 2000-4500ms when roaming. Which is quite bad considering this is on a Voice SSID.I think I'll open a case as well.
... View more
May 9 2022
12:34 AM
Looking at the VRRP is certainly important because it tells you if the problems are caused on the WAN or the LAN side. Losing uplinks will give you another VRRP status then a losing the connection between the MXs on the LAN-side.
... View more
May 2 2022
2:38 AM
Are these interfaces connected to the uplink ports or are these connected to the LAN-side of the MXs? If you're seeing a lot of VRRP events keep an eye on the priority status. If you see prio 75 (primary) or prio 55 (spare) then you have issues with your uplinks. https://documentation.meraki.com/MX/Networks_and_Routing/Routed_HA_Failover_Behavior
... View more
May 2 2022
1:46 AM
Thanks for adding the info. At this moment it is still hard to point out a specific situation or hardware type except that it happens with HA-pairs. Update: changing to SFPs on our MX85s did nothing with the dropping uplinks. Advice from Meraki support was upgrading to 16.16.1 which includes a fix for the MX100 but they expect it to work for these as well. In case of the MX450s I had a chat with the customer and they are using a Aruba switch as WAN-switch and I have yet to rule out any spanning-tree causes. The odd thing is that VRRP is using prio 105 when the uplink drops. I haven't found any reference to that status. https://documentation.meraki.com/MX/Networks_and_Routing/Routed_HA_Failover_Behavior For those interested. This is the kind of behavior we're seeing : Depending on the role the FW is dropping to the VRRP-prio associated with failing uplinks (75 on the primary and 55 on the spare MX). On the WAN-switch we only see the status of the ports change Designated -> Down -> Disabled -> Down -> Designated. This occurs repeatedly and coincides with the VRRP events. I'll keep you updated.
... View more
Apr 28 2022
7:15 AM
Hi all, I see several MX firewalls (in HA setup) having problems with their uplink ports: - We have MX85s which dropped their uplink connections. We first heard it could possibly be caused by a Energy Efficient Ethernet but neither devices we connected the MX to supported this. Now we got the advice to use Copper SFPs instead of the normal ethernet ports on the MX (this got me thinking that a static speed/duplex setting also might work, not that I favor such settings....). - A customer with 2 MX 450s (HA) sees a lot VRRP changes related to Uplinks falling away. They are using 10G DAC-cables connected to a MS250 which functions as a WAN-switch. - In the release notes I see that the MX100 also has an uplink issue. - Another customer with MX250s seems to have the same issues Most of the time when the spare is shut down, things stay stable. Most issues seem to arise after an upgrade to 16.x (in case of the 450s issues started when upgrading to the last 14.x version, 16.x seemed to stabilize but the problems returned). What's going on here and why are there so many different models affected suddenly? It's not my point to discuss every issue separately, I was just wondering why there is such a flood of issues with uplinks on (mostly) HA-pairs. With kind regards, Marcel Tempelman
... View more
Mar 10 2022
2:32 AM
Hello all, We're troubleshooting some roaming issues at a customer site and the timeline shows this: What does the Time to Connect indicate? If that's the time needed to roam then it's ridiculously high and way too high for VoWLAN roaming. I cannot imagine this is the roaming time (everything above 150ms should be marked red) because even for data a 4 second roam is way too slow . This is a SSID with WPA2/PSK encryption and layer 2 roaming so there's no external influence on the roaming speed. I'm accustomed to sub 10ms roaming in Cisco Enterprise with a PSK or 802.1X with .11r enabled. Can someone clarify that number ? With kind regards, Marcel Tempelman.
... View more
Jan 14 2021
2:56 AM
Cisco has some Excelsheets for range calculation. It is based on Cisco APs and antennas but it might give you an estimate: See this thread on the Cisco Community forums https://community.cisco.com/t5/wireless/calculating-coverage-area-using-directional-antennae/m-p/2742050/highlight/true
... View more
Nov 24 2020
2:05 AM
Hi, I've noticed this strange behavior: - AP is registered in the dashboard - Is set to Survey Mode - All settings are adjustable - Power down the AP - Power up : 5Ghz SSID is gone and also the channel and power settings. I've seen this on MR33 and MR42E access points. Only workaround is reset the AP, let it register to the dashboard and start over. Not always it loses it settings. Currently using a MR33 with 27.5
... View more
My Top Kudoed Posts
| Subject | Kudos | Views |
|---|---|---|
| 3 | 13163 | |
| 2 | 435 | |
| 2 | 7757 | |
| 2 | 30551 | |
| 1 | 3530 |
© 2024 Cisco Systems, Inc.
