MS-390, when is it ready for action?

MarcelTempelman
Getting noticed

MS-390, when is it ready for action?

Hi,

 

we were considering the MS-390 in a design for a customer but after looking at the release notes (even the beta software) we're not really convinced that this switchis ready for action yet.

 

This is a list from the relase notes and I say it's quite long:

 

  •   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
  •   Stacked MS390 series switches do not report traffic/client analytics correctly in all cases
  •   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 may not display link state on links at mGig speeds (2.5G, 5G)
  •   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, RADIUS CoA, QoS, Power Supply State, PoE power status/usage, Loop Detection, UDLD, MAC Flap Detection

 

Is there an ETA when this list is implemented / fixed ?

 

It's also a bit confusing ; we designed a redundant core solution with a warm spare. The datasheet says the MS-390 supports warm spare but the realse notes say VRRP is not supported yet. Are we talking about VRRP with other brands (Warm spare is based on VRRP with Meraki switches) or is this VRRP in general ? 

 

with kind regards,

 

Marcel Tempelman

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