Catalyst cloud monitoring: IP routing required?

cparishjr
Comes here often

Catalyst cloud monitoring: IP routing required?

Why is IP Routing required on a switch for cloud monitoring?  The switch is able to access cisco for licensing using the interfaces' default route (front panel). 

 

1/27/2023, 9:32:02 AM Device is not eligible for onboarding. Reason: IP Routing must be enabled.
10 Replies 10
alemabrahao
Kind of a big deal
Kind of a big deal

  • HTTPS proxies to access the API endpoint and the TLS gateway are not currently supported. If necessary, ensure rules are in place to allow direct HTTPS connections to each.
  • Connectivity must be via a front-panel port (not the management interface).
  • Only the default VRF is supported.
  • Ensure routes are in place to reach external addresses including a default route (use of ip default-gateway is not supported).
  • IP routing (ip routing) must be enabled on the switch or will be enabled as part of onboarding.
  • Ensure DNS is enabled on the switch (ip name-server {DNS server IP} configured).
  • Ensure DNS lookup is enabled (ip domain lookup).
  • NTP needs to be enabled on the switch (ntp server {address}), and the switch clock must reflect the correct time.
  • AAA on the switch must be configured using aaa new-model.
  • SSH access to the switch CLI must be enabled and accessible via the computer used for onboarding.
  • The user account for onboarding must have privilege-15 level access on the switch.
I am not a Cisco Meraki employee. My suggestions are based on documentation of Meraki best practices and day-to-day experience.

Please, if this post was useful, leave your kudos and mark it as solved.

It's a requirement, maybe it would be better for Meraki.

I am not a Cisco Meraki employee. My suggestions are based on documentation of Meraki best practices and day-to-day experience.

Please, if this post was useful, leave your kudos and mark it as solved.

I know it is a requirement.  ( I said so in my message)   The question is why is it a requirement? 

Ask Meraki support.

I am not a Cisco Meraki employee. My suggestions are based on documentation of Meraki best practices and day-to-day experience.

Please, if this post was useful, leave your kudos and mark it as solved.

I don't know the answer.

 

I'm going to guess it is a restriction in IOS-XE when running containers.

It does not run in a container. 

 

I am new here but do both of you comment just to run up your numbers even if you don't know the answer?   

No, I'm just explaining that you should ask for support, as they'll likely have a more plausible explanation. We are here as much to help as to learn. 😉

I am not a Cisco Meraki employee. My suggestions are based on documentation of Meraki best practices and day-to-day experience.

Please, if this post was useful, leave your kudos and mark it as solved.

By the way, the IP routing is necessary because of ip default-gateway is not supported. I don't know why, but Meraki team support probably has the answer.

I am not a Cisco Meraki employee. My suggestions are based on documentation of Meraki best practices and day-to-day experience.

Please, if this post was useful, leave your kudos and mark it as solved.

Yes it does.  The Meraki management layer is not "baked in" to IOS-XE, but runs as a container on top of it.

 

Under the hood it uses KVM from Linux.  You (or anyone else) can use the same system to run code on top of IOS-XE.  It's the official way to extend functionality.

 

https://developer.cisco.com/docs/ios-xe/#!application-hosting-quick-start-guide

The question is about Meraki MONITORING, not management.   Meraki monitoring is compatible with the 9200 catalyst switches which can't run applications.  That tells me that Meraki MONITORING does not run as a container.      

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