MS 18.1.4 RC Out, Only Fixes for MS150s

[Mloraditch]

Important fixes for MS150s! and some new known issues

Important notes

• This firmware release only includes updates for MS150 switches. All other MS switches on MS 18.1.4 will run firmware identical to MS 18.1.3.1.

New feature highlights

• Group Policy ACL on MS130 & MS150
• Maximum MAC support in MAC Allowlists
• 802.1x limited access mode with pre-auth GPACL
• Local Status Page connectivity diagnostics enhancements
• Layer 2 multicast live tool
• Traffic Mirroring: RSPAN & VLAN Based SPAN

Fixed issues

Ms150 fixed issues

• Fixed a bug that caused MS150 switches to incorrectly remove or update SGT tags when no policy or VLAN mapping was defined
• Resolved an issue that caused some SFP and QSFP modules to experience intermittent flapping
• Fixed a bug that caused some MS150 switches in stack configurations to lose connectivity while reporting redundant uplinks as blocked
• Resolved a bug that caused some 48 port MS150 switches connected to MX gateways to experience reductions in uplink throughput if the uplink was connected to any port in the 41-48 range

Known issues

General known issues

• MS130 and MS150 switches may not properly display IPv6 RA packets in dashboard packet captures
• 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.
• Some switches may encounter an error, "incompatible configuration for attributes: allowed_vlans" when attempting to aggregate ports regardless of allowed VLANs configured in Dashboard

Ms120 known issues

• Switches may fail to provide PoE power to legacy access points (always present)
• Cable tests may report incorrect cable lengths

Ms130 known issues

• Switches may incorrectly remove or update SGT tags when no policy or VLAN mapping is defined. Until a firmware fix is available, correct SGT tags can be preserved by defining a policy for the SGT group in Adaptive Policies, and binding the SGT group to a VLAN using VLAN profiles.
• MS130X mGig ports may fail to establish a link when both sides are forced to 100 Mbps full-duplex. If either side of the connection uses auto-negotiation the link will be established normally

Ms150 known issues

• When a stacking cable is disconnected from MS150 switches in stack configurations the disconnected port will incorrectly continue to be marked as connected while the still-connected stacking port will incorrectly be marked as disconnected
• In rare circumstances MS150 switches in stack configurations may experience a software crash following a stack member reboot, resulting in an unexpected active member election
• In rare circumstances MS150 switches in stack configurations may experience a software crash following a stack member reboot, resulting in a multicast storm and possible interruption of connectivity until the stack has been rebooted
• MS150 switches incorrectly advertise 60-watt PoE++ on all ports. PoE++ is only available on mGig ports; ports 17-24 on MS150 24MP-4X switches, and ports 33-48 on MS150 48MP-4x switches.
• In certain circumstances, MS150 switches using cross-stack LACP may place a port into a discarding state after a stack member reboot, with the affected port failing to transmit LACPDUs until the LAG group is recreated.
• MS150 switches may intermittently negotiate USB-C Ethernet adapters at 10 Mbps half-duplex instead of the expected speed for the switchport, requiring a physical reseat to correct the issue.

Ms350x known issues

• Switches may experience an unexpected reboot (present since MS 15)

Ms355 known issues

• Switches in stack configuration may experience some ports failing to reconnect after a firmware upgrade

Ms410 known issues

• Some MS410 switches may encounter alerts for fan failures that will eventually self-resolve

Ms425 known issues

• In rare circumstances MS425 switches may encounter a software crash that results in a reboot

[JGill]

LAB testing confirms this issue is not fix for MX uplinks.   

Resolved a bug that caused some 48 port MS150 switches connected to MX gateways to experience reductions in uplink throughput if the uplink was connected to any port in the 41-48 range

If your MX uplinks are in a MS150 MGig port move them to a standard ethernet port.  You're customers will thank you!  

Also don't use MS18.1.4 if you have SFP's in the switch.  They will start to flap.  TAC case for that is back to development and they are talking mid January.