Meraki

alemabrahao

It appears to be a version bug (I've seen similar reports), try downgrading to see if it will resolve the issue.

alemabrahao

I see two potential downtimes here. First, routing all internet traffic through the VMX could impact performance, especially if the device is handling a significant amount of traffic. Second, if the VMX fails, both SD-WAN and internet connectivity could be affected.

alemabrahao

It depends a lot on the scenario in general, but I particularly like to segment the VLANs by floor, so you don't have to leave all users in the same broadcast domain.

alemabrahao

Are you running the latest firmware version? Does the connection only work when LACP is configured? Have you tested on a Trunk port without LACP configured?

alemabrahao

In fact, the best option I see is to update the switch and perform a packet capture at the time the problem is occurring. You will hardly be able to identify the root cause without reproducing the problem again.

alemabrahao

If they are only Meraki switches then it is not necessary, this recommendation is only for when you have non-Meraki switches connected.

alemabrahao

It's probably a firmware bug, but just out of curiosity, what model is it and are you running the most up-to-date version on your Axis cameras?

alemabrahao

Do you have a patch panel before these connections? The only problem I can think of is a physical problem or a hardware problem. Are you running the latest firmware? Have you done any cable testing? I would also recommend opening a support case. https://documentation.meraki.com/MS/Monitoring_and_Reporting/Using_the_Cable_Test_Live_tool

alemabrahao

If you want to prevent this type of situation you can use another more secure authentication method, such as 802.1x or even MAB. https://documentation.meraki.com/MR/Encryption_and_Authentication/Meraki_Local_Authentication_-_MR_802.1X https://documentation.meraki.com/MR/Encryption_and_Authentication/Enabling_MAC-based_access_control_on_an_SSID

alemabrahao

Unfortunately, as of now, there isn't a direct setting in SM to prevent students from viewing the SSID password on their iPads.

alemabrahao

Yes, it needs to be included in the hybrid network, as Meraki recommends. In other words, it needs to be included in non-Meraki devices as well.

alemabrahao

You can enable features like 802.1X Authentication, MAC Address Throttling, and Port Security, and enable alerts. MS Switch Access Policies (802.1X) - Cisco Meraki Documentation How to Configure Port Security on Meraki Switches - Stratus Information Systems Dashboard Alerts - Configuration Issues - Cisco Meraki Documentation Network Alerts and Notifications - Cisco Meraki Documentation

alemabrahao

Yes, it is totally possible, if you feel more comfortable you can configure a new VLAN for this purpose, and activate DHCP in it, so you don't need to fix the IP, or you can also make an IP reservation in DHCP, but Meraki is super simple, you just need to have an IP that can communicate with the internet and the rest is basically configuration in the network on the dashboard.

alemabrahao

It was a pleasure to help you. Guys, just to let you know that I was helping @mcoomber closely, one of the things that was missing was to create VLAN 30 on a 3850 switch that was between the MX and the MS. In addition, not all APs had the switch port configured for trunk, which was also causing the problem (this was confirmed by Meraki). So in short, it wasn't just about allowing VLAN 30 in the SSID and configuring trunk on the ports, it was still necessary to configure the VLAN on the Catalyst switch.

alemabrahao

Maybe it will help you. Network Alerts and Notifications - Cisco Meraki Documentation Integrate the Cisco Meraki API with the Twilio API - Pipedream

alemabrahao

It would be a good idea to call Meraki, I think their service will be faster. https://documentation.meraki.com/General_Administration/Support/Ways_to_Contact_Meraki_Support#Contact_Support_by_Phone

alemabrahao

You can see some graphs in Security & SD-WAN > Device Status in the Meraki dashboard. You can also see some in Network > Monitor > Clients. This page shows detailed usage data by client, including application breakdowns. Organization > Summary Report provides an overview of device usage, including the MX device. And you can do more detailed traffic analysis by going to Network > Traffic Analysis. Clients Usage Page Overview - Cisco Meraki Documentation Device Utilization - Cisco Meraki Documentation

alemabrahao

I sent you a private message.

alemabrahao

Using Secure Connect to configure your cloud firewall can be beneficial, but it does require some consideration. I think it would be a good idea to consult a Meraki SE to help you define the best design for your environment.

alemabrahao

Yes, the MR28 would be an option, but it would be interesting for you to consult your Sales Manager Maraki to help you choose an access point. It goes far beyond the technical specifications in the data sheet, so it would be good to talk to this person to raise all the possible needs you may have.

alemabrahao

When you configure High Availability (HA) on Meraki MX devices, including the MX85, the devices use the VRRP to send heartbeat messages. MX Warm Spare - High-Availability Pair - Cisco Meraki Documentation

alemabrahao

SmartPort Automation may sometimes fail to apply the correct configuration, leading to issues like the one you are experiencing. There may be conflicts or misconfigurations when using named VLANs with dynamic assignment capabilities. Make sure that the VLAN names and IDs are mapped correctly and are consistent across your network. In your case, I would suggest opening a support case with Meraki. I believe they will be able to assist you further.

alemabrahao

Have you checked that the RPC service is running and set to Automatic on both domain controllers? "error: 1726. The remote procedure call failed" errror message on - Microsoft Community

alemabrahao

You are using Co-Term or Per-Device Licensing. The definition is that the devices will literally stop working, that is, your network will become inoperable. I have seen some cases where with Per-Device Licensing, even after the grace period expired, it continued to work, but let's face it, even if it is a bug, I believe that you should have the good sense to renew the licenses, right? I think it is a question of trust.

alemabrahao

From what I understand, you are trying to configure the tunnel only with the correct HUB? In practice, it should work, there are no limitations. Have you managed to capture packets on the WAN interface of the MX? See the troubleshooting guide. https://documentation.meraki.com/MX/Site-to-site_VPN/Troubleshooting_Non-Meraki_Site-to-site_VPN_Peers

About alemabrahao

alemabrahao

Alessandro Abrahao

Community Record

Badges