service meraki connect source interface ?

[thomasthomsen]

How can you define the source interface of "service meraki connect" on a Catalyst switch you want to use for cloud monitor (Or cloud managed device config or what ever its called today).
Its easy if you have a access switch with just one L3 interface and a 0.0.0.0 route.

But what about a core switch that might have multiple L3 interfaces, that might not all be allowed towards the internet ?

[alemabrahao]

I think this is not possible because the source interface is automatically selected based on the routing table and the availability of a default route.

[thomasthomsen]

Well there is a route, learned from a dynamic routing protocol, but its still not all the IP interfaces on the switch that have internet access.
The usual management interface (the one that has internet access) is of course not the ones that are used for the routing (if that makes sense).

[Brash]

My understanding from the doc is that this sets the source interface for the cloud communication:

To resolve DNS names and communicate with the Meraki Dashboard, the Catalyst switch will need the following configuration.

• "internet bound" vlan configured as http client source-interface 
  

https://documentation.meraki.com/MS/Cloud_Management_with_IOS_XE/Migration_from_CLI-managed_Catalyst...

That said, I haven't tested it myself so I can't say 100%.

[thomasthomsen]

Ill try, and let you know. Thanks.