Meraki

RWelch

If possible, assign unique subnets to each remote site to simplify VPN configuration. If you must use overlapping subnets, configure VPN subnet translation (NAT) for each site. There is no alternative built-in method to avoid this complexity if you must connect multiple sites with overlapping subnets. The best practice is to ensure each site uses a unique subnet, but if that's not possible, VPN subnet translation is the supported solution. Note: VPN subnet translation (NAT) is only available for Meraki Auto VPN peers and is not supported for IPsec VPN peers. To ensure successful VPN connectivity, each site must use a unique subnet. If overlapping subnets cannot be avoided, you will need to redesign your addressing scheme or use external NAT solutions outside of Meraki.

RWelch

If you haven't done so already, you might Give your feedback (previously Make a Wish) and layout the use case for your request and how it'd benefit you/your organization.

RWelch

You can check Organization > Monitor > Change Log for any recent changes to the switch's management interface - not sure if you were wanting to find out the "why" part of the equation or what caused this to occur. This normally happens when there have been manual configuration changes (e.g., an admin set the switch to use DHCP for management), or a configuration rollback, or firmware upgrade or device reboot that did not regain the static IP setting. Assigning a Static IP Address

RWelch

I recall reading about the trial period being 90 days, with the option to extend twice for 30 days each, for a total of up to 150 days duration but can't find exactly where I read this. You might check with your sales rep or preferred partner for the specific trial duration details.

RWelch

yes.

RWelch

If this were my project, I'd probably open a support case to find out if they are truly not working....if that is in fact the case, they can start the RMA process simultaneously. Ways to Contact Meraki Support

RWelch

Awesome! Thank you much.

RWelch

Feedback submitted - apparently the Energy Management page FEEDBACK button doesn't function. Yes, I can submit feedback on other pages except Energy Management. And I was able submit my feedback on a different page.

RWelch

I've not had problems in the past with submitting feedback however today it's quite problematic in trying to provide feedback with the error seen above. My feedback was fairly short with no special characters, nothing pasted. Same error regardless of browser.

RWelch

The SFP modules at each end must match. Example, if your Meraki only allows 1Gig SFP modules then to connect to your C9300 series you would need it to also be 1Gig SFP module. If you want to use the C9300 at 10Gig - both ends (each SFP modules needs to be 10Gig SFP+). It's as easy as this - 1Gig at each end or 10Gig at each end, if that makes sense.

RWelch

You are correct—current documentation does not explicitly reference "host translation" or "VPN port forwarding rules" as new features within the expanded VPN NAT solutions. If you are looking for documentation on these specific new features, it appears they have not yet been published or updated in the knowledge base. You may want to check back for updates or contact Meraki support for the latest information.

RWelch

Using Site-to-site VPN Translation

RWelch

In my test organization, I upgraded 3 networks using MX105, MX75 and MX68W from MX 26.1.1 to MX26.1.2. All seemed to upgrade fine but perhaps cosmetic issues linger with MX 26.1.2 for the MX75. Security & SD-WAN > Monitor > Appliance Status > Summary Tab (above) shows: Single WAN on the MX75 shows 1 WAN uplink - it's correct, perfect. Security & SD-WAN > Monitor > Appliance Status > Uplink Tab (above) shows: Single WAN 1 uplink but also shows INACTIVE WAN 3. I had all 3 WAN uplinks active quite a long time ago but nothing recent - so I think something is still a bit odd about MX 26.1.2.

RWelch

After unbinding, the network loses access to the template's VLAN object mapping, so the Dashboard replaces the object with the actual subnet. This is expected behavior and can make management more challenging, as object-based rules are easier to maintain at scale.

RWelch

Congratulations to all contributors and many thanks for your participation / willingness to assist others!

RWelch

3288 critical networks and 1 warning to be concise.

RWelch

Squeeze the hand gently. Confirm with Meraki Support before proceeding, as this workaround is not officially documented and may have unforeseen consequences (prepare to do manual configs if plan goes south, have renewal licenses readily available).

RWelch

Again - it's not a change that is ready for production (introduction) yet here we are taking 3 steps backwards (takes longer to do a simple task and is more complex than previously was). SMH.

RWelch

Indeed - perhaps a year or so from now we will see it fixed (fingers crossed).

RWelch

Thanks @cmr - not exactly the same issue per se. I am aware of how to change from one to the other but the issue is that "when doing so" there is partial information from the previous setting that remains such as IP address in the VLAN field when going back to DHCP. It appears to definitely be a GUI BUG IMO. Why does the IP address info linger? In order to SAVE this - one has to manually DELETE this info (data) before being able to SAVE it. Causes additional steps which is problematic when doing this to a network with say 15 or more meraki devices (APs). Just give me back the OLD view and I'll zip it and be happy 😃

RWelch

If you need different port configurations for each switch in the stack, you can create separate templates and bind each switch individually. After the initial setup, you can unbind the switches from the template to make manual changes, and the port configurations will remain unless you override them.

RWelch

Templates for Switching Best Practices Guidelines and Limitations 1. STP bridge priority cannot be changed on switch stacks using templates. In a network template, switch templates can be assigned STP bridge priority values from Switching > Configure > Switch settings > STP configuration. A value assigned to a switch template, however, will only propagate to the standalone switches bound to that template; switch stacks will retain the default STP priority of 32768. If an MS switch stack must be the root bridge of an STP domain that has at least one other MS switch stack, it should be placed in a Dashboard network that is not bound to a network template for the STP priority value configured on it to take effect. The following diagram shows the relationship between network templates and switch templates:

RWelch

MX Warm Spare - High-Availability Pair Do I need duplicate licenses to cover my security appliance in a warm spare configuration? No, security appliances (MX) in a warm spare/HA configuration require only one license for the two devices. Meraki Licensing FAQs

RWelch

In the dashboard go to Organization > Monitor > Firmware Upgrades there you can see: Stable Release (tab) Stable Release Candidate (tab) Beta (tab) Other Available Version (tab) Under each you will see RELEASE NOTES.

RWelch

Meraki MX appliances do not run LACP or any link aggregation protocols (intentionally by design). If you wanted to make it a request you can Give your feedback (previously Make a Wish)

About RWelch

RWelch

Community Record

Badges