New MS 18.1.3 Firmware out as RC - Few fixes

Mloraditch
Kind of a big deal
Kind of a big deal

New MS 18.1.3 Firmware out as RC - Few fixes

Just a few fixes:

 

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

General fixed issues

  • Fixed a bug that sometimes caused switches in stack configurations to fail to remove older entries from the MAC forwarding table

Ms150 fixed issues

  • Fixed a bug that sometimes caused MS150s to experience transmission errors and lose connectivity until they were rebooted

Ms425 fixed issues

  • Resolved an issue that caused clients authenticating via 802.1X with an access policy using hybrid authentication to not correctly log their RADIUS sessions
  • Fixed an issue that caused some switches in stack configurations to experience high CPU utilization in multicast scenarios that sometimes resulted in network instability

Known issues

General known issues

  • MS130 and MS150 switches may not properly display IPv6 RA packets in dashboard packet captures
  • MS130 and MS150 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.
  • 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

Ms150 known issues

  • Wireless clients may lose connectivity when roaming between access points connected to different members of the same switch stack

Ms225 known issues

  • MS225 switches may infrequently stop forwarding client traffic until the switch is rebooted

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
If you found this post helpful, please give it Kudos. If my answer solves your problem please click Accept as Solution so others can benefit from it.
2 Replies 2
RaphaelL
Kind of a big deal
Kind of a big deal

Real diff between MS 18.1.3 and MS 18.1.2 :

4 fixes : 

General fixed issues

  • Fixed a bug that sometimes caused switches in stack configurations to fail to remove older entries from the MAC forwarding table

Ms150 fixed issues

  • Fixed a bug that sometimes caused MS150s to experience transmission errors and lose connectivity until they were rebooted

Ms425 fixed issues

  • Resolved an issue that caused clients authenticating via 802.1X with an access policy using hybrid authentication to not correctly log their RADIUS sessions
  • Fixed an issue that caused some switches in stack configurations to experience high CPU utilization in multicast scenarios that sometimes resulted in network instability

 

2 new issues : 

 

  • MS130 and MS150 switches may not properly display IPv6 RA packets in dashboard packet captures
  • Ms150 known issues

    • Wireless clients may lose connectivity when roaming between access points connected to different members of the same switch stack

 

1 removed ( with no listed fix ) : 

  • LACP links may take an extended time to come back up when the Active Member of a stack reboots
PhilipDAth
Kind of a big deal
Kind of a big deal

>Fixed a bug that sometimes caused switches in stack configurations to fail to remove older entries from the MAC forwarding table

 

How are we still getting basic packet forwarding bugs at this point in time.

Get notified when there are additional replies to this discussion.
Welcome to the Meraki Community!
To start contributing, simply sign in with your Cisco ID. If you don't yet have a Cisco ID, you can sign up.
Labels