New MS 14.32 stable release - fixes 802.1x and PoE issues
Switch firmware versions MS 14.32 changelog
Alerts
MS390 upgrades from MS 14.29 or later will result in minimal impact to client traffic
Branch additions
Syslog support for MS390 series switches
SNMP support for MS390s
RADIUS accounting support for MS390s
Alternate Management Interface support for MS210/MS225/MS250/MS350/MS355/MS410/MS425/MS450 series switches
QoS support for MS390s
CoA support for MS390s
STP anomaly detection events for non-MS390 series switches
Adaptive policy support for MS390 series switches
SecureConnect support for MS210/MS225/MS250/MS350/MS355/MS410/MS425/MS450 series switches
NAC enhancements for MS120/125/210/225/250/350/355/425/450 series switches
Critical/failed auth VLAN support for MS120/125/210/225/250/350/355/425/450 series switches
Bug fixes
Voice VLAN clients cannot pass traffic on ports that have MAC allowlists enabled (present since MS 14.28)
Clients on a RADIUS authenticated port that ages out of the MAC table due to inactivity will fail to be relearned until a port bounce has occurred (present since MS 14.28)
MS120s may show PoE usage on the incorrect port
If RADIUS authentication begins close enough to boot, the NAS-IP in Access-Request packets will be incorrect
Clients connected to a MS390 trunk port on the native VLAN will show "native" for the VLAN information rather than the native VLAN ID
Known issues
In rare instances, DAI inspection may fail to snoop DHCP transactions on stacks leading to those clients being in a blocked state
If a combined network has Umbrella integration, changes cannot be made to the group policy page (present since MS 14.5)
Networks containing a large number of switches may encounter issues saving changes on the Switch Settings page
The list of switches to clone from fails to load when cloning a switch in an organization with a large number of switches and 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)
Stacking
Stack members are not being marked to update their configuration when changes are made on other members
In rare instances, a stack member may go offline until rebooted (present since MS 12)
In rare instances, non-390 stack members will reboot (present since 12.29+)
MS120
MS120 in rare instances will not be able to perform packet captures until rebooted (predates MS 12.28)
MS120s on rare occasions will reboot (present since MS 11)
Links being established on a MS120 can result in neighboring ports to flap (present since MS 11)
MS120s switchports with MAB authentication may randomly deauthenticate clients. In order to resume client authentication on that port, a switch reboot is required (present since MS 12)
MS35X
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. Example, MS355 switchports 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)
MS390
MS390s may experience control plane resets which could impact dashboard connectivity. This does not affect data plane traffic.
MS390 ports are limited to the lowest link speed since boot if QoS is enabled
MS390s may experience a brief 1-2 minute control plane outage. The data plane will not experience issues during this time.
Packet loss is observed when pinging the MS390 management IP
Stackpower is not enabled on MS390s by default
MS390 - Port Up/Down Events Shown Across All Members
MS390 series switches do not support SM sentry
MS390 series switches do not support Meraki authentication
MS390 series switches do not support URL redirection
MS390 series switches do not support MAC whitelists
MS390 series switches do not support loop detection
MS390 series switches do not support warm spare/VRRP
MS390 series switches do not support UDLD
Rebooting any MS390 stack member via the UI will result in the entire stack rebooting
If my answer solves your problem please click Accept as Solution so others can benefit from it.
