About cmr

cmr

Indeed, I do now have 5 licensed and now 5 free MT licenses. I only have 5 MT devices...

cmr

In the 15.4 release notes there is this note that I think relates to your issue: Known issues If the voice VLAN authenticates before the data VLAN, the voice VLAN will stop working after the data VLAN authenticates (present since MS 14.28)

cmr

@MK2 what devices are you wanting to manage the temperature on? The only ones we find that are at all accurate are server intake temperatures or UPSes and even those aren't great, hence we now deploy an MT into our important server rooms / wiring closets.

cmr

Apologies, internal traffic is included. If the cameras and NVR are not directly connected to the MX, nor the traffic routed through it, then at the top left choose the appliance network instead of entire organisation to see the MX only traffic.

cmr

I wish the Meraki devices configured with local DNS servers would use them to look up the names of the clients. I really don't understand why they cannot do this?

cmr

Are they either being viewed remotely or storing the video data in the cloud? A basic camera stream is 2Mbps

cmr

@PacerX if you have no APs left in the network then it will still have a firmware set. The simplest way to fix this is to split the network, delete the wireless network and then re-combine the others. You will not lose any configuration doing this.

cmr

@jay_b I don't know for sure, but I'd be willing to bet that this has carried forward and is only not noted due to it not being a new feature.

cmr

@js7 you can look at the network summary report for load before and after. If you need more details then the CPU load is available by contacting support.

cmr

@Noa-M does it not work, it should do, even if it technically is not supported...

cmr

@jashcraft that looks like a realtek card, try the Lenovo 2023... drivers referenced in the thread about E480s

cmr

@Greenberet apparently it is only for RADIUS server use at the moment...

cmr

@Eric123 still showing up here for an appliance on 16.12:

cmr

We tend not to use band steering and at most sites stick to 20MHz but I just checked and one of our busiest sites does have band steering on the SSID used for laptops where the performance would be most quickly noticed. Otherwise the same as you.

cmr

@zzzthumpI have an MR56 that hasn't been rebooted in a while and haven't seen this issue. We also have a lot og MR42/52 models and also haven't had the kind of issues experienced here. I wonder if there is a particular combination of configurations that cause it? What authentication do you use? What channel width? Access lists on APs? Band steering? There has to be something!

cmr

@Holli69 which firmwares are you using? Is there a pattern as to which ports work and which don't?

cmr

@360Solutions are the 3x MS225s on each floor stacked? They support stacking with the QSFP+ ports on the back and work better that way than as separate switches. What MX and MS firmware are you running, I had STP issues with dual connection on firmwares less than 14.30.

cmr

It isn't connected to a different SSID, it is just that Windows has created a second profile for the connection. You will probably find a remembered network of Hello on the same PC. Delete both and reconnect to make it display Hello instead of Hello 2.

cmr

Put a UPS on the MX67 to power it and the MR33 (assuming it is PoE from the MX), you won't need a large expensive one.

cmr

Switch firmware versions MS 15.4 changelog Alerts HTTP proxy is no longer supported on MS 15+. Nodes that use HTTP proxy without any other means to connect to dashboard may fail to connect. SecureConnect fails on MS355 series switches MS390 ports are not disabled when configured to do so by dashboard Moving or re-provisioning an MS390 stack in dashboard can cause at least one member to stay offline until rebooted (this only affects control plane traffic). MS390 upgrades to this version will experience a full system reload MS390s that have SecureConnect configured may lose uplink connectivity and would require a factory reset to recover If SecureConnect is enabled on the network, MS390 access ports will not be a part of STP or receive broadcast traffic MS390 upgrades to this version will result in a full system reload Branch additions IPv6 static routing support for MS390 series switches Additional client analytics added for MS390 series switches Meraki authentication support for MS390 series switches Alternate Management Interface (AMI) support for MS390 series switches UDLD support for MS390 series switches Group policy ACL support for MS390 series switches IPv6 management interface support URL redirect support for MS390 series switches UPoE (802.3bt) support for MS390 series switches Netflow export for Adaptive Policy Critical/failed authentication support for MS390 series switches Multi-auth with voice VLAN bypass support MAC flap detection support for MS390 series switches Named VLAN support for MS120/125/210/225/250/350/355/390 series switches Stack power is supported by default for MS390 series switches Netflow support for MS390 series switches Bug fixes DHCP traffic is dropped on the voice VLAN if MAC allow list is configured In rare instances, DAI inspection may fail to snoop DHCP transactions on stacks leading to those clients being in a blocked state MS250 switches in rare instances could experience a crash when configuring LACP (predates MS 12) MS210/225/250/350/355/410/425 series switches may be unable to initialize 1Gbps SFP modules. Current, only some MA-SFP-1GB-SX modules are in scope (present since MS 15.0) MS390 Rebooting a MS390 switch in a stack via the UI will result in the entire stack rebooting MS390 group policy ACL port ranges are not applied MS390 ports are limited to the lowest link speed since boot if QoS is enabled MS390 ports that have MAC allow list configured will not change between access and trunk once configured in dashboard Known issues If the voice VLAN authenticates before the data VLAN, the voice VLAN will stop working after the data VLAN authenticates (present since MS 14.28) In rare circumstances, changes made to SVIs may result in connectivity loss for one or more SVIs until reboot (predates MS 12) When applying an access policy to a port, voice VLAN clients will not be updated in the MAC table without bouncing the port (present since MS 14.28) Connecting a stacking cable to a stack that is online may result in a stack member going offline (present since MS 12) In rare instances, a stack member may go offline until rebooted (present since MS 12) Networks containing a large number of switches may encounter issues saving changes on the Switch Settings page Stack members may experience delays in updating their configuration for up to an hour after a config change (present since MS 9) The "clone from" list may fail to load when cloning a switch in an organization with 1,000+ switches or networks Broadcast types of traffic can leak into the Guest VLAN if a port that fails authentication has a voice VLAN configured, and dashboard has a Guest VLAN defined (present since MS 11) AMI IP addresses do not send gratuitous ARP packets which can lead to packet loss if the AMI address has aged out in the network Meraki authentication does not work with guest VLAN MS120 Links being established on an MS120 can result in neighbouring ports to flap (present since MS 11) In rare instances, MS120 series switches may have empty packet captures until they are rebooted MS120s switch ports with MAB authentication may randomly de-authenticate clients. In order to resume client authentication on that port, a switch reboot is required (present since MS 12) MS35X/4XX Enabling Combined Power on MS350/355 switches results in events being logged once per minute (present since MS 11) mGig switches will have an amber light for all physical ports that do not negotiate to the highest supported speed. Dashboard will continue showing a light green status for all ports above 100Mbps. For example, MS355 switch ports will incorrectly show an amber light for 1G, 2.5G, and 5G, but will show a green light for 10G. MS350-24X and MS355 series switches do not negotiate UPoE over LLDP correctly (predates MS 10) SecureConnect fails on MS355 series switches (present since MS 15) Ports with an odd-numbered MTU value fail to initialize for MS120/125 series switches (predates MS 11) When an SFP module is inserted/removed on MS420/425 series switches, BPDUs can be delayed leading to STP transitions in the network (predates MS 12) MS350/450 series switches in a stack configuration will lose dashboard connectivity if a "Deny Any Any" ACL is added without having higher "Allow" rules in place for dashboard connectivity (predates MS 12) MS390 Packet loss is observed when pinging the MS390 management IP (present since MS 12) In rare circumstances, MS390 series switches may disconnect from dashboard until rebooted. Data plane traffic is not impacted unless RADIUS authentication is used (present since MS 14.28) MS390 "Port Up/Down" events will be shown across all members MS390 control plane may experience brief outages which will show as red lines on the connectivity bar in dashboard. These events do not affect data plane traffic. MS390 series switches do not support loop detection MS390 series switches do not support warm spare/VRRP Moving or re-provisioning an MS390 stack in dashboard can cause at least one member to stay offline until rebooted (this only affects control plane traffic). MS390 ports are not disabled when configured to do so by dashboard MS390 series switches will go offline if a "Deny Any Any" ACL is added without having higher "Allow" rules in place for dashboard connectivity MS390s that have SecureConnect configured may lose uplink connectivity and would require a factory reset to recover If SecureConnect is enabled on the network, MS390 access ports will not be a part of STP or receive broadcast traffic

cmr

Thanks @Saralyn 1080P at 25 fps+ is enough for us at the moment. The reason for the fps request is that it is common for the regulators to require a minimum framerate for our camera coverage. In South Africa we need 25fps and in the USA we need 30fps. In the UK we operate most cameras at 25fps to capture enough frames to accurately trap fast movements.

cmr

Thanks @rymiles I was not aware of that rather useful adapter 😎

cmr

@Jon_Cole Meraki switches don't support the QSFP(+/28) breakout cables so the ports are a single 40Gbps connection, you cannot get a 10Gbps SFP+ connection. You'll need some switches from lower in the range that have QSFP+ uplinks and SFP+ downlinks like the MS425 models

cmr

@Saralyn to me the most important feature is that the MV52 can run higher framerates up to 30fps, this is only shown on the downloadable datasheet, whereas elsewhere it says 15fps, I hope the PDF is the correct one... Also the web datasheet lists the Ethernet port twice...

cmr

The release is now marked as stable, something which I would totally agree with.

cmr

Community Record

Badges