- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Updated Onboarding and Migration Process for Hybrid (Cloud Monitored)
I just switched the one 9200 I have that happened to already be on 17.15.3 to Hybrid in 5 minutes . New onboarding is super simple:
This is in the Latest IOS-XE Release notes but I thought deserved a separate call out as it's not really the same thing.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Interesting, I see no mention of a requirement for ip routing command to be used vs ip default-gateway, as was the case for Cloud Monitoring for Catalyst (even for Monitored mode) - can anyone verify it's not required?
IP routing not included in the Hybrid Operating Mode Switches Configuration list either
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
My switch was configured with ip-routing, so I cannot verify this. But I had to configure aaa new-model. After onboarding, the dashbard showed an alert "aaa new-model is not acitivated". I configured it, and after a few minutes the configuration was completed by the dashboard.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I've got already several switches running on version 17.15.2 and will be upgrading them to 17.15.3.
The new Cloud Monitoring is indeed much simpler then before. I need to upgrade all of them to do it the correct way. 🙂
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Just updated a c9200-48P from 17.12.3 to 17.15.3 the following way
- Removed it from the Meraki Dashboard
- Updated the firmware
- Added it to the Meraki Dashboard
The following issue arose. I didn't get a question about the credentials for Hybrid mode. Now it's added as a Meraki cloud managed switch. The configuration was lost so I had to recreate the configuration. Luckily only AP's where connected who all had the same config.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
It's a 9200 not 9200L??? Those are not supposed to work in cloud managed mode yet... interesting if it's otherwise working but you want to check with support as you could end up in a sketchy situation.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
This could be indeed a sketchy situation. For now it's working and accepting changes in the configuration. I already mailed my Cisco Account manager for it.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Had contact with someone from Meraki Support. The person claimed it was supported.
So also send the case to my Account manager because I don't think it's true. But on the other hand. Another switch shows this with the same firmware version and running in Hybrid mode already.
===========================================================================================
Meraki Cloud Monitoring: Compatible
===========================================================================================
Meraki Cloud Management:
Compatibility Check Status
-------------------------------------------------------------------------------------------
Boot Mode INSTALL - Compatible
----------------------------------------------------------------------------------------------
Switch# SKU Bootloader Version Network Modules
----------------------------------------------------------------------------------------------
2 C9200-48P - Compatible 17.15.1r - Compatible C9200-NM-4X - Compatible
Compatible SKUs: C9200-24P, C9200-24T, C9200-48P, C9200-48T, C9200-24PXG, C9200-48PXG, C9200-48PL
Compatible NMs : C9200-NM-4G, C9200-NM-4X, C9200-NM-2Y, C9200-NM-2Q
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
My gut feeling is the IOS XE code is ready for the 9200s but some difference in the Ls vs not Ls is significant enough the back end is not officially ready.
Curious what they end up telling you because Id love to be able to be selling 9200s in Meraki mode.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
We've got a whole bunch of 9200s that would love to have in Meraki mode. I want to wait what Cisco gives me back on this before I go forward moving all 9200s from the old Cloud-Monitored mode to Hybrid mode, because if it failes more I would seriously have a problem. Now I've got enough spares to swap this one.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Had a similar issue with a 9300LM (Not L-M) where it tried and failed to convert to Meraki mode since that SKU line isn't supported yet. I also got no prompt for Hybrid or Managed mode when adding via the dashboard either and it appears to default to managed mode so I've got a case open for that. I also have no MAC or Cloud ID now in Show Meraki on the switch and get a SUDI error when trying to register again so I need to reboot the switch to fix that as well, so that's fun.
Edit:
What's interesting is things worked fine in the Beta via Stomio on 17.15.2 but when I removed and upgraded to add the switch back on 17.15.3 that's where the issues started.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
According to my Cisco Account manager this shouldn't be possible. They want me to contact support again to see what is happening.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
For clarification, hybrid mode is being rolled out in phases and is not available to everyone yet. If you do not see the option to select hybrid mode, please check back again soon.
Any switches added to organizations where hybrid mode is not yet available will be added to cloud operating (fully managed) mode.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
@Jeff-Lthe thing is, Our organization was enrolled in the private beta testing this before. So I already have several switches in this Org running in Hybrid mode. That is why in my understanding it was already working in my org.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Same here regarding the private beta.
@Jeff-L It would be nice if the "defaults to fully managed" was called out explicitly while this is rolling out. I can definitely see people getting into trouble like @JeroenVercoulen experienced if they don't know that.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Documentation was updated last week to reflect this caveat. At this time, hybrid mode is available to everyone, so this should no longer be a concern. Let us know if you do not see the option at this time.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
As an update, hybrid mode is now available to all organizations. If you do not see the choice to onboard in hybrid mode, please reach out to Support for assistance.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Migrating back to Cat9k mode took about 7 minutes. Than you have a factory default switch you need to reconfigure. Re-configuring is easy when you have a backup config
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I've got Hybrid mode now available for my org. I migrated a stack of 4 switches to hybrid mode from cloud-monitoring mode. First of all it's a very easy process. as stated I added only the active member (in my opinion the stack master) to the network. But then the other switches aren't added at all. Does anybody know how this works? I tried to add a stack member later, but it failed to add and gave some ssh errors.
Also the device tracking and monitoring commands aren't added to the stack member switches.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
You can try removing the one switch from the network and then selecting all stack members to add them at the same time.
