Hello @newbiess,   Please note that the Help > Cases link option will not be visible in Organizations which have not yet claimed a device and have no Meraki Customer Number (MCN) associated with the organization (the MCN is viewable in dashboard by clicking on your account.) Locating the Meraki Customer Number (MCN): https://documentation.meraki.com/General_Administration/Support/Locating_the_Meraki_Customer_Number_or_Support_Passcode#Meraki_Customer_Number_(MCN) If a device has been claimed to the organization and a MCN has been assigned, please contact Meraki Support by phone for further assistance regarding this issue. The general Meraki Support number is +1 (415) 937-6671. A full list of region-specific phone numbers can be found in Dashboard under "?" > Get help > Still need help? > Call the Meraki Support team > View regional phone numbers, or on the Meraki Support home page. Best, Feli ... View more

Hello @timmy-zhou,   As PhilipDAth mentioned, this message regarding APNS certificate renewal can be safely disregarded if you no longer have need of this feature and no longer have any iOS or macOS devices enrolled in Systems Manager. However, if these devices are still enrolled and are required to be managed in Systems Manager, you will need to follow the steps in the documentation below to properly renew the APNS cert every 365 days: https://documentation.meraki.com/SM/Device_Enrollment/Apple_MDM_Push_Certificate#Renewing_an_Apple_MDM_Push_Certificate ... View more

Hello @Warren65,   As kYutobi mentioned, please ensure that the value of the roles match.  The "Assertion contains no role" error is reported when the role assertion is either completely missing in the POST or when the role assertion name is invalid. For the user that is experiencing the error, you can click on their login event and click Full XML to view the assertion information. An example of viewing and verifying the assertion passed in the XML is provided in the following SAML Login History Events documentation: https://documentation.meraki.com/General_Administration/Managing_Dashboard_Access/SAML_Login_History_Events#Assertion_contains_no_role Best, Feli ... View more

Hi @Richard-Tapp, Brash and cmr pretty much covered it! This Product End-of-Life (EOL) Policy page is another great reference 🙂   A product's EOL (End-of-Life) and EOST (End-of-Support) date are basically equivalents and reference the same date. When the device reaches EOL/EOST, the product's lifetime warranty period also ends (if it's a product covered by a lifetime warranty, which MS switches are.) Additionally, the device is no longer affirmatively supported by Cisco Meraki (please still feel free to open a Meraki Technical Support case on these devices if needed, but please be aware that this support will be on a best case effort basis and not guaranteed.) After the EOL/ EOST date, the changes that may occur will include the following: Cisco Meraki cannot guarantee that legacy hardware products will be able to connect to the management software indefinitely following the EOST Date; Cisco Meraki Technical Support may no longer troubleshoot the legacy hardware products; Cisco Meraki may no longer issue firmware updates or patches for the legacy products; and New software features available for the management software may not be compatible with the legacy hardware functionality or with the firmware running on the legacy hardware.   Best,  Feli   ... View more

Hello @Knowledge_gainr, What PhilipDAth said is correct - it's not supported to specify specific people/sponsors to receive the email within the domain (as any user with an email from the domain will be able to grant access to guests). However, the following workaround is suggested in this documentation and is recommended: If an organization requires only specific users to grant access to guests, these specific users will need to have their emails on a isolated domain that is only for these users. Then, you must specify this domain as the "sponsor email domain", which is a domain that contains only these few specific user email addresses. The below example is provided: "For example, if the specified domain is meraki.net, any employee with a username@meraki.net email will be able to sponsor the guests. If the administrators want only specific emails to have the authority, then the specified domain has to be a different domain; for example "@merakiguestsponsor.net" with only a few emails on that domain like username@merakiguestsponsor.net that can be specified by guests to grant access to them." Best, Feli ... View more

Hola @MarioOG, Por favor perdona mi español. ¿Los AP MR56 informan en el tablero que están funcionando en modo de bajo consumo (802.3at)? ¿Está habilitado LLDP en los puertos del switch Catalyst 9407 que suministran energía a los AP?   Varios puntos de acceso Meraki requieren que LLDP esté habilitado mientras negocian una potencia superior a 15,4 W, y algunos conmutadores Catalyst tienen CDP habilitado pero LLDP deshabilitado.   Consulte la siguiente documentación para asegurarse de que LLDP esté habilitado y disponible en el conmutador y puerto al que está conectado el AP: https://documentation.meraki.com/MR/Other_Topics/Low_Power_Mode_on_Cisco_Switches ... View more

Hello @Carlo99, This scenario will require a password reset. However, please note that password resets for MSP accounts will generally take some time to propagate and sync across the organizations. If after 30 minutes to 1 hour you've noticed the password hasn't yet synced across the organizations, please feel free to reach out to Meraki Support by creating an email case (or calling in to support as Darren mentioned). Best, Feli ... View more

Hi gijo, If using custom or internal DNS servers, would you be able to change the primary DNS to use Google (8.8.8.8 or 8.8.4.4 is recommended by Meraki)? Also, would it be possible to connect the switch to a network that has DHCP services available and then observe if the switch receives a valid DHCP IP address? If an MX appliance is upstream of the switch, DHCP services can be configured directly on the MX and DNS set to Google. By default, Meraki devices will attempt to find a valid IP via DHCP on any network or VLAN that's reachable where the default gateway is replying to ARP requests. This is an intended function to bring the device online and allow it to initially report to the dashboard. If the switch is able to initially connect to the dashboard, further troubleshooting can be performed regarding its static IP configuration and Local Status page access. ... View more

Hello @gijo, What error is seen in the browser when connecting to the front switch port and browsing to http://switch.meraki.com ? Is a DHCP server configured on the equipment upstream of the switch? If no, would you be able to configure DHCP services? If yes, is the switch seen in the ARP table? If the switch is receiving a valid LAN IP address via DHCP, you could try to browse to that IP address instead of 1.1.1.100. ... View more

Hello @RaphaelL, Great catch! Thank you 🙂 Your suggestions have been forwarded, and I'll provide an update once these adjustments are complete. ... View more

Hello @Chris-L, If the switch is going offline at regular intervals, it may be due a failed firmware upgrade. A failed firmware upgrade will cause a device to go offline at regular intervals while it continuously tries to complete the upgrade. Is the MS120 reporting "Not running configured version" under firmware, as seen in the example attached?     If the firmware appears up-to-date, it may be a DNS or IP conflict issue causing the switch to fail Connection Monitoring tests on the uplink. Providing the detailed configurations will help to scope the issue, as alemabrahao has mentioned. Best, Feli ... View more

Hello @DanielRobson, A wireless packet capture taken on one of the affected clients or on the access point can be filtered for EAPoL traffic to initially determine which of the EAPoL packets may be failing to be exchanged in the 4-way handshake, as this is one typical cause of EAPoL timeouts. To perform a wireless packet capture on the client device, please see the steps provided in the Capturing Wireless Traffic from a Client Machine documentation. To perform a wireless capture on the access point(s), please see the steps provided in the following documentations:  1. Access Point Tx Captures  2. Collect wireless captures when only Meraki APs are available For assistance with performing and/or analyzing these captures, please feel free to open a case with Meraki Support by navigating in the dashboard to Get help > Cases > New Case or by following the steps provided in the Contact Cisco Meraki Support document here. Best, Feli ... View more

Hi @BlakeRichardson, Sorry to hear about the session timeout and log out issues you're experiencing.  Is the issue seen across several different browsers and when using incognito or private browsing mode? To best help determine the root cause of the issue, would you be able to open a case with Meraki Support? -- As these types of issues generally require some investigation and data gathering (i.e. current dashboard settings and configurations, email address(es) of the administrator(s) affected, possibly gathering a HAR capture within the browser, etc.).  Additionally, if you're able to provide a timestamp of when the continue button last failed to extend your session along with the email address of the affected account, a support representative should be able to review if any specific error may have logged on the backend. To raise a case with Meraki Support, please navigate in the dashboard to Get help > Cases > New Case or by following the steps provided in the Contact Cisco Meraki Support document here. Best, Feli ... View more

Hi Thomas, Thank you for mentioning the ease of use features which you'd like to see implemented on the Catalyst switch (CS) platform. However, at this time, no further information is available regarding development of SecurePort or Switch Port Profiles on the CS platform.    SecurePort is currently supported on Catalyst wireless CW916x access points and the MS switch and MR access point models found in the SecurePort KB article here.   Switch Port Profiles are currently supported on the the MS120, MS125, MS130, MS130R, MS210, MS225, MS250, MS350, MS355, MS410, MS425 and MS450. * Please feel free to keep a watch on the Switch Port Profiles KB article regarding updates on supported models, as the MS130 and MS130R were recently added to the list.   Though these features are not currently supported on the CS platform, I highly encourage you to submit a request directly to the Meraki development team for future considerations. Your feedback is greatly appreciated and can be submitted via the “Give your feedback” button which is located at the bottom right corner of each dashboard page. Best, Feli ... View more

Hi @Moonlight, alemabrahao is correct. At this time, blocking access / disabling the Local Status Page is a global network-wide feature that will apply to the entire network. The feature is enabled/disabled under Network-wide > General > Device configuration and will affect the entire network instead of individualized VLANs. However, similar interests have been expressed regarding managing Local Status Page access on a per-VLAN basis. It's highly encouraged to submit this feedback request for future considerations via the “Give your feedback” button in dashboard -- located at the bottom right corner of each dashboard page. ... View more