MS390 stacks on rare occasions will require a manual reboot after the upgrade has completed
MS390 upgrades from MS 14.13 or later will result in minimal impact to client traffic
MS390 client authentication may fail closed if RADIUS server passes unsupported AVPs
Auth session state on RADIUS server may be stale following an MS390 CoA update until RADIUS Accounting is supported
MS210/225/250 switches cannot forward IPv6 Router Advertisement and Neighbor Solicitation packets when flood unknown multicast is disabled (has always been true)
Additions
STP event log enhancements for Root bridge transition and BPDU packet delays
Bug fixes
With DAI enabled on a stack, there was a chance that a client would become incorrectly blocked
Known issues
MS390 stack members may not report client-level detail
MS390 series switches Max MTU is limited to 9198 bytes
MS390 series switches will not display packet details in the DHCP Servers page
MS390 series switches do not support the 'next-server' or 'bootfile' parameters in DHCP messages
Rebooting a single switch in an MS390 stack will reboot the entire stack
LLDP frames from MS390 series switches will use a single system name instead of the Dashboard given name
MS390 series switches will not display the advertising router ID for OSPF
MS390 series switches with OSPF enabled will default to an IP MTU of 1500 bytes on every OSPF enabled interface
MS390 series switches do not support the multicast routing livetool
MS390 series switches do not support tagged traffic bypass for voice on ports with a Multi-Auth access policy
Dynamic VLAN assignment from a RADIUS server on MS390 series switches must already be an allowed VLAN on the port for it to function
MS390 series switches do not currently support the following features: VRRP, SM Sentry, Syslog server, SNMP, Traceroute, IPv6 connectivity to dashboard, Meraki Auth, URL Redirection, MAC Whitelisting, RADIUS Accounting, Loop Detection, UDLD, MAC Flap Detection
SM Sentry does not support Windows based clients (predates MS 10.x)
MS425 series switches do not forward frames larger than 9416 bytes (predates MS 10.x)
MS350-24X and MS355 series switches do not negotiate UPoE over LLDP correctly (predates MS 10.x)
MS355 stacks upon reboot have a chance that the uplink port will go into STP blocking state (predates 12.X)
Switches on 12.28+ will sporadically drop DHCP Offers when a relay is in use
L3 switch stacks with multicast routing may fail to route streams through all members
MS120s can experience packet loss when forwarding from a 1Gbps to 100Mbps port
MS320s may experiences reboots when in large L2 domains (predates 12.X)
//
//
LITHIUM.InformationBox({"updateFeedbackEvent":"LITHIUM:updateAjaxFeedback","componentSelector":"#informationbox_f0396f00e6000","feedbackSelector":".InfoMessage"});
LITHIUM.InformationBox({"updateFeedbackEvent":"LITHIUM:updateAjaxFeedback","componentSelector":"#informationbox_f0396f00e6000_0","feedbackSelector":".InfoMessage"});
LITHIUM.InformationBox({"updateFeedbackEvent":"LITHIUM:updateAjaxFeedback","componentSelector":"#informationbox_f0396f00e6000_1","feedbackSelector":".InfoMessage"});
LITHIUM.InformationBox({"updateFeedbackEvent":"LITHIUM:updateAjaxFeedback","componentSelector":"#informationbox_f0396f00e6000_2","feedbackSelector":".InfoMessage"});
LITHIUM.AutoComplete({"options":{"autosuggestionAvailableInstructionText":"Auto-suggestions available. Use Up and Down arrow keys to navigate.","triggerTextLength":4,"autocompleteInstructionsSelector":"#autocompleteInstructionsText_f0396e63d27af","updateInputOnSelect":true,"loadingText":"Searching...","emptyText":"No Matches","successText":"Results:","defaultText":"Enter a search word","autosuggestionUnavailableInstructionText":"No suggestions available","disabled":false,"footerContent":[{"scripts":"\n\n;(function($){LITHIUM.Link=function(params){var $doc=$(document);function handler(event){var $link=$(this);var token=$link.data('lia-action-token');if($link.data('lia-ajax')!==true&&token!==undefined){if(event.isPropagationStopped()===false&&event.isImmediatePropagationStopped()===false&&event.isDefaultPrevented()===false){event.stop();var $form=$('