Meraki

alemabrahao · ‎Nov 3 2022

Nope.

alemabrahao · ‎Nov 3 2022

I have no idea.

alemabrahao · ‎Nov 2 2022

Well, I've never worked with unsupported transceivers, and as far as I can remember there is no specific configuration to support this. Probably if you open a case with Meraki they will recommend switching transceiver. What you can try to do is force duplex maybe.

alemabrahao · ‎Nov 2 2022

https://www.youtube.com/watch?v=V_xE_3RWOZ0

alemabrahao · ‎Nov 2 2022

Is your fiber multimode or singlemode? Have you checked if it is emitting a light signal? Have you tried reversing the fiber pair?

alemabrahao · ‎Nov 2 2022

Also, perform a test disabling 802.11w, disabling Band steering, changing channel Width for manual, and setting It to 40Mhz. Some legacy devices that do not support 802.11w may not be able to connect to an SSID even if in mixed mode. This may be due to the device improperly handling the advertised information contained within the beacons. In a high-density environment, a channel width of 20 MHz is a common recommendation to reduce the number of access points using the same channel. In certain cases, having dedicated SSID for each band is also recommended to better manage client distribution across bands and also removes the possibility of any compatibility issues that may arise. Band steering does not work with all clients. "If certain wireless clients are unable to detect the wireless network they may be using passive scanning. In these cases configure the network to use Dual band operation, not Dual band operation with Band Steering."

alemabrahao · ‎Nov 2 2022

Generally hiding SSID is not recommended. WLANs can operate "hiding" the SSID name, and only answer when a probe request has the explicit SSID included (client knows the name). By default, the SSID is included in the beacons, and APs will reply to null probe requests, providing the SSID name information, even if clients are not pre-configured with it. Hiding the SSID does not provide additional security, as it is always possible to obtain the SSID name by doing simple attacks, and it has secondary side effects, such as slower association for some client types (for example Apple IOS), or some clients can't work reliably at all in this mode. The only benefit is that it would prevent random association requests from devices trying to connect to it. It is recommended to enable Broadcast SSID option to have the best interoperability.

alemabrahao · ‎Nov 1 2022

Well done guys. 😃

alemabrahao · ‎Nov 1 2022

For that reason I like to use templates. 😅

alemabrahao · ‎Nov 1 2022

Well, you're going to have to have a script, which is also going to take some work, so I don't know what a certain advantage would be. https://developer.cisco.com/meraki/api-latest/#!update-organization-alerts-profile

alemabrahao · ‎Nov 1 2022

You can enable It on the dashboard:

alemabrahao · ‎Nov 1 2022

Have you tried this? If you don't have any rule blocking Inbound and outbound, probably It's not an MX issue. For me, It does not make sense, but you can try to create a Bonjour forwarding rule.

alemabrahao · ‎Nov 1 2022

By the way, have you tried to allow any port on your 1:1 NAT? Just for a test.

alemabrahao · ‎Nov 1 2022

If it is via public IP what is the role of OpenVPN? It's a little confusing.

alemabrahao · ‎Nov 1 2022

I didn't understand, is this communication via VPN or via public IP?

alemabrahao · ‎Nov 1 2022

Congrats guys. 🎉

alemabrahao · ‎Oct 31 2022

You can connect all MS switches to 1 MS switch that has an Internet connection. Remembering that anyway each switch needs to have an IP configured to access the internet.

alemabrahao · ‎Oct 31 2022

Well, You can configure IP on the local status page. If you connect your notebook to any interface you should receive an IP address so you can access the local status page. https://documentation.meraki.com/General_Administration/Tools_and_Troubleshooting/Using_the_Cisco_Meraki_Device_Local_Status_Page#MS_Series

alemabrahao · ‎Oct 31 2022

Quick-Start If you just want to get started without reading more in-depth information, follow these basic steps: Unpack and mount your switch (desktop or rack mount) and power it on. Plug any one of the Ethernet or fiber ports into an upstream device on your LAN. The uplink port should have access to a DHCP server and it will also need to be able to communicate with the internet. After powering on, your switch will download the latest software. While upgrading, the switch's power LED will flash green/white. Once the switch has checked into the dashboard, the LED will turn green/white. Note: A solid orange light indicates that the device has not checked in with the dashboard yet. Log in to http://dashboard.meraki.com (For any devices that are used in mainland China, please visit http://dashboard.meraki.cn and create a new network. If you do not yet have a dashboard account, choose "Create an Account") Type in the serial number of your switch (found on the back of the unit) or simply enter your order number. This will create a new switch network. Make your desired configuration changes under the Switch > Configure section of the dashboard. For additional switch installation information, please refer to the MS Installation Guides article.

alemabrahao · ‎Oct 31 2022

Hi, You just need to make sure they have internet access. Think of them as a host on your LAN.

alemabrahao · ‎Oct 31 2022

SFP+ ports often accept SFP optics but at a reduced speed of 1Gbps. But I'm not 100% sure.

alemabrahao · ‎Oct 31 2022

Ok, so I suggest opening a case with Meraki support.

alemabrahao · ‎Oct 31 2022

No, it's not a joke, It's just a question. I'm not suggesting that, you can perform Lab to test It.😉

alemabrahao · ‎Oct 31 2022

Have you tried to disable DFS channels?

alemabrahao · ‎Oct 30 2022

Strange, I have a client with over 700 spokes (the HUBs are MX450 too) and we haven't had any problems. The only difference is that we are not using BGP.

About alemabrahao

alemabrahao

Alessandro Abrahao

Community Record

Badges