About cmr

cmr

@TommyYap if you have some managed switches then you can at least start to divide traffic into separate VLANs by having one of them directly connected to the MX. You could then have the unmanaged switches hanging off that in their own zones.

cmr

Congratulations everyone and @ww welcome to the club 🍾

cmr

What mode is the wireless in, bridge mode, layer-3 roaming or something else?

cmr

@TommyYap You can only have one VLAN on an unmanaged switch, so where an unmanaged switch is connected to the MS350 you would set that port to access mode (single untagged VLAN). I would configure the port on the MS350 and have that do the routing with it connected via a single VLAN to the MX250. In my example if you set a port to VLAN2 then yes you will need to change the static IP address on the device connected to it to be in the 172.18.0.0/16 range. I would create a second DCHP pool on your existing server and set the helper address on VLAN2 on the switch to point to the server. Alternatively you can use the switch as a DHCP server itself for VLAN2 (or indeed VLAN 1 as well if you wished to).

cmr

I'd put a cable tester on the cable, you could have one pin shorted to another or oxidation on one of the pins, either way different devices will react differently. The MR could have dropped down to 100Mb/s (dark green on core switch port in dashboard), but the MS might not be set to allow negotiation down below 1Gb/s. I recently had an issue with some cabling I did where I had a short between pin 3 (B, so the positive data signal for one direction) and the shield that allowed an IP phone or AP to work, but only at 100Mb/s...

cmr

@mikeset116 reduce the max power, for some phones 17dB is as much as they can transmit. If that leaves blackspots try steps down from your current max of 25 to find the best compomise.

cmr

@Newbie99 there are essentially only two options for SD_WAN over MPLS remote sites connect a WAN port to the MPLS and central site is in VPN concentrator mode remove sites connect a WAN port to the MPLS, central site connects a WAN port to the MPLS and MPLS has internet breakout. This is because the Meraki datacentres need to see traffic from all of the WAN ports coming from the same public IP address to enable the forming of the SD-WAN connections using the private IP addresses. Any deviation from this will lead to hair-pinning from one public IP address to another if it works at all.

cmr

The main requirement is that the switch connected to the MX needs to be in routing mode, an MS210, MS225 or any MS3/4 should do.

cmr

@BlakeRichardson yes, absolutely right, we have lots and only some gets recognised and the rest fills most of the rest of the top 10...

cmr

Is there a known reason why most of the RSTP traffic is correctly recognised, but a good chunk is not? Is there anything I can do to make it recognise all of the traffic?

cmr

Go to Network-wide / Clients and in the Status column the green icon shows that the client is online.

cmr

@SCCSD do you mean admin logins, devices on the LAN or users via a splash page / other authentication method?

cmr

Thanks for the quick reply @BrandonS I logged out all sessions for my user and functionality in the browser and app is all restored...

cmr

This afternoon I have lost the ability to switch Orgs. In the web browser I can go to each separate shard (184 and 199) and login to both Orgs separately, but the link between them seems broken. In the app I can log in and it shows both Orgs, but once I have gone into one, I cannot switch to the other and have to sign out in from the app settings to get the choice again. I did enable Google Authenticator for my user today, in place of SMS, has anyone else had the same problem or is that a coincidence?

cmr

Round here banks often block you if you DO have up to date software, IE11 only... 🤦‍ ♂️

cmr

@scarfman4 you have the port set up correctly by the sound of it. I'd agree with @PhilipDAth that it sounds like the other end isn't sending all of the replies back properly. They might need to adjust the routing table air firewall at their end. If you can ping all of the IP addresses that you need to connect to, but cannot get traffic to flow then it is most likely the firewall settings.

cmr

@PhilipDAth, yes this org is in per device mode, my other is in co-term like yours, so I'm not sure if it is just me or a general bug.

cmr

@NickHortonit will be between 0.5Mbps and 8Mbps with it being above 1Mbps unless you turn it down to the lowest quality (720p) or frame rate (8 fps), see below for an MV72X:

cmr

@DanielP9if all of your P-link switches support 802.1Q VLANs then you should be absolutely fine using them with Meraki MRs and the MX. Just make sure that you have the same VLANs on each end of the link when trunking, with the same native VLAN.

cmr

Has anyone else seen this, in the Licensing & Inventory page on the Licenses tab I have this: The above is completely correct, however if I switch to the Expiration Dates tab I have this: Not only is the partial day rounded differently, but the MT license has become an MR one... Somewhat confusing!

cmr

@mikeset116 yes keeping both but turning off band steering should improve things

cmr

It just means there was a very low level of traffic, or do you think there was a large amount of traffic to/from that device in the timeframe at the top of the page?

cmr

@mikeset116 don't use band steering, it causes devices to jump about between 2.4GHz and 5GHz, for voice we use 5GHz only to ensure smaller cells with less variable coverage within a cell.

cmr

@TommyYap the idea of VLANs is to separate the network into logical zones as I think you wish to do. Initially if you enable VLANs but leave everything in VLAN 1 then all your existing devices should continue to work as they do now. If you create a second VLAN then you will need to create a VLAN interface in both the original VLAN1 and the new VLAN. This allows devices in each VLAN to talk to each other. As an example the IP addressing could be as below: Original network: 192.168.0.0/24 New VLAN1: 192.168.0.0/24 <- the same as above New VLAN1 interface IP: 192.168.0.1 New VLAN2: 172.18.0.0/16 New VLAN2 interface IP: 172.18.0.1 Default route of 0.0.0.0/0 192.168.0.254 (IP address on MX in VLAN1) A device on VLAN1 would have an IP address of 192.168.0.n with a subnet mask of 255.255.255.0 and a gateway of 192.168.0.1 A device on VLAN2 would have an IP address of 172.18.n.n with a subnet mask of 255.255.0.0 and a gateway of 172.18.0.1 To access the internet a device on VLAN2 would go to the L3 device (MS) and then onto VLAN1 and out through the MX.

cmr

@PeaceLuth you'd normally have them the other way round and have the MX do the DHCP. The cable modem (if it is a modem) needs to connect directly to the cable connection.

cmr

Community Record

Badges