About SVTWeb

Jeff-L

Yes, the tunnel can be shut/no shut in the "crypto tls-tunnel MERAKI-PRIMARY" section of the configuration.

PhilipDAth

I have a native IPv6 connection - and when I do a DNS lookup against that DNS name I only get an IPv4 address returned. I suspect it might be giving out an IPv6 address in error.

DarrenOC

You mean like ports showing the correct status 🙂

markki · ‎02-08-2023

Hi folks, just wanted to post an update on what happened. On Tuesday, February 7 at 3:51 AM PT the Cloud Monitoring for Catalyst service experienced a service disruption mainly in North America that prevented some of our backend APIs from communicating with Dashboard services. This affected Dashboard’s ability to onboard additional Catalyst switches and incorrectly display the status and statistics of Cisco Catalyst switches. This did NOT affect the functionality of the switch itself. Service was partially restored at 11:24 AM the same day, and fully restored as of February 8, 8:56 AM. Precautions are being put into place to avoid similar issues in the future. Meraki devices or other Dashboard services were not affected by this disruption. We sincerely apologize for the alarm, confusion, and productivity impact this might have caused. We will do better!

SVTWeb · ‎02-07-2023

Everything just came back to life and I was able to onboard another site. All is good with the world again.

SVTWeb · ‎02-07-2023

IT'S ALIVE!!!!!!!! Just came back to life!

rhbirkelund · ‎02-06-2023

The Single Pane of Glass management is still possible with CW916x AP. As long as it's in the Meraki persona, it will function like any other Meraki MR Access Point.

alemabrahao · ‎02-03-2023

Yes, it is possible:

SVTWeb · ‎01-24-2023

We have a fiarly large enterprise of Meraki with some legacy Cisco switches. Our current landscape is intermixed with older Cisco products that are being migrate to Meraki and mnore recent Cisco Catalyst 9000 series switches that still have depreciation on the books so they are grandfathered into the new landscape, to be replaced when they are fully depreciated. As we have started to do a PoC on the Cisco Catalyst 9000's we are finding that Port Channels from Core to access layer report incorrectly in the dashboard. We have also found that those switches will often reboot on their own from rougue processes. Has anyone else seen strange behavior on the 9000's. What IOSXE have we collectively found as the most stable when trying to onboard and monitor these devices in the Meraki Dashboard?

DevOps_RC · ‎10-31-2022

I've had that issue with a couple of stacked switches. I've re-ran the on-boarding process with one of the affected stacks and now both switches are showing in the dashboard. There is no need to remove the affected switch from the dashboard before re-running the on-boarding process. I couldn't find any reason why they didn't on-board the first time, versions and stack configurations are the same as other stacks that have successfully on-boarded without issues.

SVTWeb

Cloud Monitoring for Catalyst - Early Availability Group

Community Record

Badges

Re: Switches loosing contact with Meraki Cloud

Re: Anyone else seeing the telnet us.tlsgw.meraki.com 443 fail with an IPV6...

Re: Port status not right

Re: No Telemetry in Americas - 02/08/2023

Re: One minute they are there, next minute they aren't

Re: Catalyst Crash - 17.9.x after onboard

Re: Upgrading Meraki equipment - need help deciding between MR or Catalyst

Re: Using 1GB Copper SFP on MX425-32?

Catalyst Integration Unstable on access layer with port channels

Re: Cloud Monitoring only shows first member of the Stack

Re: Port status not right

Re: No Telemetry in Americas - 02/08/2023

Re: Catalyst Crash - 17.9.x after onboard

Re: One minute they are there, next minute they aren't

One minute they are there, next minute they aren't