Ms12x important notes MS 16 introduced DAI on MS100 series platforms. If you are upgrading to a current release from MS 15 or earlier please ensure trusted ports and/or DAI-allow lists are configured prior to upgrading. New feature highlights DOM (Digital Optical Monitoring) Intelligent Capture SmartPorts Automation New ms130x feature highlights Adaptive Policy on MS130X/R models New ms150 feature highlights Static routing on all MS150 models General fixed issues Fixed an issue that caused switch stacks to learn MAC addresses from ports in the STP blocking state, triggering MAC flap messages in the event log Fixed a bug that caused an unexpected LACP discarding state when connected to third party firewalls Resolved an issue that sometimes prevented communication between VLANs on switches in stack configurations Resolved a bug that caused the Ping tool in the Client details page to fail to display data on Dashboard for wired clients Resolved a bug that occasionally caused switches in stack configurations to crash and reboot Ms120 fixed issues Resolved an issue that sometimes caused MS120 switches to unexpectedly reboot after upgrading to MS 17.2.1 Ms130 fixed issues Fixed a bug that sometimes caused switches to fail to deliver PoE, and could cause all ports to display as disconnected in Dashboard Ms220 fixed issues Resolved an issue that caused MS220 switches to reboot after updating to MS 17 Ms355 fixed issues Fixed a bug that sometimes caused SFP ports to fail to connect after a firmware upgrade Resolved a bug that sometimes caused a stack member to go offline when a stacking cable was disconnected and reconnected Ms425 fixed issues Resolved a bug that occasionally caused MS425 switches in stack configurations to unexpectedly reboot Fixed a bug that sometimes caused fail to collect reporting data on all SFP ports, or to only report data on port 1 General known issues Clients authenticating via 802.1X with an access policy using hybrid authentication may not correctly log their RADIUS sessions Clients that fail to pass RADIUS authentication and are connected to ports using access policies may get stuck in an authentication loop, possibly resulting in a switch reboot In rare circumstances switches may experience uplink instability when IPv6 link-local addresses are enabled. If this issue is encountered it can be resolved by enabling IPv6 RA Guard to block ICMPv6 neighbor discovery messages. LACP links may take an extended time to come back up when the Active Member of a stack reboots Some switches may encounter an error, "incompatible configuration for attributes: allowed_vlans" when attempting to aggregate ports regardless of allowed VLANs configured in Dashboard On MS250 and MS350 switches, MAC addresses learned via AGGR are not removed when LAG ports are disabled. Mac addresses will be removed correctly within 5 minutes of reenabling LAG ports. Ms120 known issues Switches may fail to provide PoE power to legacy access points (always present) Cable tests may report incorrect cable lengths Ms220 known issues Client devices connected to ports 24-48 on MS220-48LP switches may have their DHCP offers and ARP replies erroneously dropped Ms225 known issues MS225 switches may infrequently stop forwarding client traffic until the switch is rebooted In rare circumstances, switches in stack configurations may experience a software crash that results in a reboot Ms250 known issues Switchport with Multi-Domain Hybrid auth access policy randomly goes into a port not forwarding state Ms350x known issues Switches may experience an unexpected reboot (present since MS 15) Ms355 known issues In rare instances, stack ports fail to initialize after an upgrade (always present) Ms410 known issues Some MS410 switches may encounter alerts for fan failures that will eventually self-resolve Ms425 known issues Frequent notifications about new DHCP servers that have mismatched VLANs/subnets In rare circumstances MS425 switches may encounter a software crash that results in a reboot Powering off the active switch in a MS425 stack may result in up to 5 minutes of downtime while the stack reconverges Switches in stack configurations may experience high CPU utilization in multicast scenarios that may result in network instability Other 17 introduces a change to the default login credentials for the device local status page, using "admin" as the username, and the device serial number (upper case with dashes) as the password
... View more