- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Scheduled Maintenance Alert: On June 6, 2024 at 23:00 to June 7, 2024 at 01:00 UTC Order and Device?
Maybe I am missing it, but when I looked at the FAQ on this aouncment I really didn't see what the gain or end result would be after this maintenance is completed. I have lots of detail saying we will not be about to work in the inventory portion of the dashboard, but no real info on what new benefit or fix that is being addressed.
Scheduled Maintenance Alert: On June 6, 2024, at 23:00 to June 7, 2024, at 01:00 UTC, we will conduct routine maintenance affecting order and device claiming processes on the Meraki Dashboard During this period, please note that you cannot claim or unclaim devices. All other dashboard activities will remain unaffected, and the operation of connected Meraki devices will function as expected. For detailed information and a comprehensive FAQ, please visit [Maintenance Details and FAQ]
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I don't know the details for this particular announcement, but they often relate to Meraki infrastructure upgrades. Sometimes Cisco Meraki do shard splits.
The exact details are not divulged as they are an internal operational matter for Meraki.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
What is a shard split?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
When you log in you'll notice the URL starts with something like https://n100.meraki.com/.
The "100" is your shard number. When a shard ends up with too many customers on it a shard split is sometimes done to reduce the load. After that you'll have a new shard number.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
This scheduled maintenance aims to improve the reliability and performance of the order and device-claiming functionalities. The result will be a more reliable and streamlined experience when handling device and order claims, reducing the likelihood of errors and downtime in the future.
