Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
About Holli69
Holli69
Getting noticed
Member since May 1, 2020
Nov 20 2024
Community Record
70
Posts
43
Kudos
2
Solutions
Badges
Nov 19 2024
11:56 PM
4 Kudos
Hi, try this documentation: https://documentation.meraki.com/MX/Site-to-site_VPN/Primary_and_Secondary_IPsec_VPN_Tunnels
... View more
Nov 1 2024
3:28 AM
4 Kudos
Running 19.1.5 since 24 hours ago on MX95 without any issue
... View more
Hi, look at this document: https://documentation.meraki.com/General_Administration/Tools_and_Troubleshooting/Using_the_Cisco_Meraki_Device_Local_Status_Page
... View more
Oct 13 2024
5:37 AM
4 Kudos
The Roaming decision ist done by the Wireless Device and depends ON the manufacture of the device
... View more
Oct 12 2024
12:53 AM
Is it possible to update the devices firmware via the mobile Android or IOS App ?
... View more
I've 7 C9300X Switches and all running well since about July 2024. Crossing fingers 🙂
... View more
Sep 12 2024
6:43 AM
2 Kudos
@cmr Thanks, but all Management AP's (about 70) are set to DHCP auto without VLAN in Meraki Dashboard, only all Switch ports where the AP's are connected as a trunk port have native VLAN 99 and allowed VLAN 20,30,99 configured.
... View more
Sep 12 2024
6:06 AM
With the above constellation, I have the problem, that all AP's CW9164 don't connect to the Meraki Cloud / Dashboard. All Layer 2 Switches also connect only, if I connect to the management Port and statically assign the Management IP address. If I connect with the Management SSID of an AP and set statically all IP information with the default Gateway of the DHCP Server in VLAN 99 (10.10.253.1 on the MX, primary DNS 10.10.253.1, secondary DNS 8.8.8.8), nothing happens. Usually, from my understanding, the AP's will send a DHCP discover (Broadcast), which should received by the DHCP Server of the MX in the same VLAN 99, the DHCP will send a DHCP offer message with the dedicated IP of the AP which has fixed IP assignment by MAC address on the MX DHCP Server and so on. The Access Points should receive there information from the DHCP Server, but it does not. Is there a mistake, do I have forget something ?
... View more
Labels:
- Labels:
-
Installation
-
Other
Aug 29 2024
6:52 AM
Hi Tony, a) MX port connecting to C9300 in an access Transfer VLAN 10 with 2 IP's MX has 10.105.10.254, C9300 has 10.105.10.253 in a subnet of 10.105.10.252/30. b) there is only one 10G Fiber connection between those 2 devices, configured as an access port on both ends, both in VLAN 10 (transfer net). The C9300 takes care of the management VLAN 20, but either the MX nor the C9300 has a management IP from VLAN 20. With MS250-24 instead of C9300 exactly this config works fine in all other locations. I can ping from MX to C9300, but I can't ping from C9300 to MX and I can't ping to 8.8.8.8, but the C9300 is reachable from the Meraki Cloud and is online. So, I assume there is something different between C9300 and MS250 or other "legacy" Meraki Switches.
... View more
Aug 28 2024
9:17 AM
1 Kudo
Hello again, strange behaviour, from MX I can ping L3 Switch, but from L3 Switch (IP: 10.105.10.253) I can't ping IP of MX (IP: 10.105.10.254) or 8.8.8.8 (100% loss). Nothing is blocked by ACL or Firewall.
... View more
Aug 28 2024
12:21 AM
Hello everyone, we have a Transit VLAN 10 (10.105.10.252/30) between MX105 and C9300-24Y-M, MX IP is 10.105.10.254, C9300 (Layer3) IP is 10.105.10.253. The C9300 takes care of all L3 Routing, all SVI's are configured on this Switch. Also the Mgmt VLAN 20 for all Meraki Layer 2 Switches and Meraki Access Points (10.105.20.0/24) with fixed IP Assignments on the L3 DHCP Server. This is the first time we have used C9300 as a Layer 3 Switch, before we used MS250-24 as Layer 3 Switch and everything works fine for us.
... View more
Aug 27 2024
9:56 AM
Hi, We've an office with MX105 as Firewall, C9300-24Y-M as the Core L3 Switch with Routing, and a few MS225-48-FP/LP as Access Switches. I can see MX105 in Meraki Dashboard online and C9300-24Y-M with a Transfernet to MX105 is online as well. We have about 10 Subnets on C9300 configured, each MS225 Switch connected via SFP+ to core Switch C9300 doesn't come online on the Management VLAN and get no reserved IP from the DHCP Server (C9300). So all MS225 switches are marked as red (LED and Dashboard). With a MS250-24 as Layer 3 switch everything works fine. Question: Is there a way to force the routing function on the C9300 ? It seems routing isn't working on the device
... View more
Aug 14 2024
8:49 AM
Hi, I would suggest STP Guard here to BPDU Guard. Non-Meraki Wi-Fi Access Point with VLANs Type = Trunk
STP Guard = Root Guard
UDLD = Alert Only
... View more
Hi, it depends on your site survey. Usually, a good recommendation is a minimum Bitate set to 12 Mbit/s for 2,4G and 5G. Power Transmit Power for 2,4G should be between 8 and 14 dBm. Power Transmit Power for 5G should be between 11 and 17 dbm. Give it a try, but think about your Site Survey (e.g. with Ekahau AI Pro and Sidekick)
... View more
Apr 19 2024
12:49 PM
Hi all, we have an MX95 in our branch office with 2 different ISPs. One on WAN 1, and the other on WAN 2. We build a 3rd party VPN with 3 Subnets to our Data Center (MX450 as a VPN Concentrator which is in another Organization) over the WAN 1 primary Connection. So far, so good, everything works fine. We want in case of a failover (WAN 1 is down), the same 3 Subnets should go via 3rd party tunnel on WAN 2 to the VPN Concentrator (MX450). Both ISPs (WAN 1 + WAN 2) have fixed public IPs. On the VPN Concentrator MX450, I can't put the same Subnet to the other public IP of WAN 2 to build a second VPN tunnel. How could I solve the problem or is it only possible for AutoVPN ?
... View more
Labels:
- Labels:
-
3rd Party VPN
Apr 6 2024
10:32 AM
2 Kudos
I've installed the 18.210 in many Organizations, and most of them are okay, a few I had to go back to the 18.107.9 version, due to some VPN issues.
... View more
Feb 23 2024
5:27 AM
Here is the documentation: https://documentation.meraki.com/MS/Monitoring_and_Reporting/Enhanced_Topology
... View more
Feb 23 2024
2:17 AM
2 Kudos
The new Topology view looks aewsome !!
... View more
Labels:
- Labels:
-
Topology
Feb 19 2024
12:01 AM
HI tcanty, at the moment we use VPN only at primary WAN Connection, secondary is in use for other traffic. We couldn't send any data as well. Hopefully in 18.209 or 18.210 it will be fixed.
... View more
Feb 16 2024
2:08 AM
3 Kudos
a few weeks ago I tried 18.207, but is was very buggy and not working for me, because our servers in the DC are not reachable anymore (3rd party VPN between 2 MX's in different Orgs), switched back to 18.107.8 and everything works fine anymore. In 18.207 AND 18.208 the 3rd party VPN tunnel is shown as up in both locations, but no server is reachable via ping. MX18.208 has the same issues. I rolled back again to 18.107.8 and everything is fine again for me (MX85,MX95,MX100->VPN Concentrator MX450)
... View more
Feb 16 2024
2:08 AM
1 Kudo
a few weeks ago I tried 18.207, but is was very buggy and not working for me, because our servers in the DC are not reachable anymore (3rd party VPN between 2 MX's in different Orgs), switched back to 18.107.8 and everything works fine anymore. In 18.207 AND 18.208 the 3rd party VPN tunnel is shown as up in both locations, but no server is reachable via ping. MX18.208 has the same issues. I rolled back again to 18.107.8 and everything is fine again for me (MX85,MX95,MX100->VPN Concentrator MX450)
... View more
Feb 13 2024
12:03 PM
2 Kudos
Hi, on CiscoLive! 2024 in Amsterdam, MS17.xxx is on the way with new features. Also, MR31.xxx will introduce new features in a few weeks.
... View more
Feb 9 2024
8:47 AM
For this function, you must have a System Manager license. I would like to see more granular privilege management in the future. For example, a read-only or monitor-only privilege for a specific user only for MX and Wireless, but not for switching and others. For example a read-only or full privilege for MX and no access to all others menus.
... View more
Jan 17 2024
11:48 AM
We have also problems with 3rd party VPN connections (different Orgs) from all of our Branch Offices (MX85, MX95, MX105) to the Data Center VPN Concentrator MX450 all using FW 18.207. Rolling back to 18.107.7 solves the problem. Waiting for a better 18.2xx Firmware, where the VPN connection problem doesn't exist anymore.
... View more
My Accepted Solutions
| Subject | Views | Posted |
|---|---|---|
| 406 | Nov 19 2024 11:56 PM | |
| 3729 | Nov 24 2021 1:35 AM |
My Top Kudoed Posts
| Subject | Kudos | Views |
|---|---|---|
| 7 | 1365 | |
| 4 | 406 | |
| 4 | 2900 | |
| 4 | 435 | |
| 3 | 2674 |
© 2024 Cisco Systems, Inc.
