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.

[thomasthomsen]

Did not work 😕

The error does not make any sense, we are not using IPv6, and we have even tried to disable all IPv6 on the switch.

We can easily telnet to fx eu.tlsgw.meraki.com and we get the right IPv4 address resolved.

So my conclusion is that I guess this does not work for a switch that does not have a static 0.0.0.0 route in its configuration 😞
(the 0.0.0.0 route is learned via OSPF).

Meraki Device Registration
------------------------------------
url: https://catalyst.meraki.com/nodes/register
Device Number: 2
PID: C9300-24T
Serial Number: abcdefghij
Cloud ID: N/A
Mac Address: aa:bb:cc:dd:ee:ff
Status: Failed
Error: IPv6 DNS resolution failed for catalyst.meraki.com. Retrying.
Timestamp(UTC): 2025-09-25 10:13:44

[GIdenJoe]

Does it work the same way managed switches work with the UAC process?  So it can select any kind of interface that CAN reach the internet dynamically?

[oliviaaaaa]

Already on the main Catalyst switch, you define the outbound interface for Meraki cloud services. By configuring a dedicated L3 interface that has a route to the Internet and passes through any firewalls, ensuring that traffic will use this interface rather than relying on the default route.