Source Alternate L3 Interface For Traffic Destined For Internet

[Badger-Fi]

I want to be able to source an alternate L3 interface for traffic destined for the internet, specifically for checking in with the Smart Licensing Portal and Meraki dashboard, sourced from a Catalyst 9300 that has non-routable addresses configured for /31 P2P WAN links.  Right now I am unable to send traffic from the switch because it chooses to source the traffic from the non-"internet" routable IP addresses on either of the two /31 P2P WAN links.  Is there a way to source this specific traffic from another interface that has an IP address that can access the internet?  I am thinking PBR but can't put it together.

[MHM Cisco World]

MHM

[Badger-Fi]

I see where you are going with this.  Thanks!  The problem is that the traffic isn't destined for a single host.

[MHM Cisco World]

MHM

[Georg Pauwen]

Hello,

post the running configuration of your Catalyst 9300, and indicate which interface you want traffic for the Internet to be sourced from...

[Badger-Fi]

I would prefer to use SVI 35 because that is our management, but any SVI would work because they can reach the internet.  The only L3 interfaces that can't reach the internet are the two WAN connections Tw 1/0/47 and Tw 1/0/48, which is where my problem lies because these two interfaces are used to source the traffic. 

[balaji.bandi]

Smart Licensing Portal and Meraki dashboard

This was not clear to me that, why does the switch initiate the connection to above mentioned portals ? is the for smart License ?

or is the switch in the transit clients like to connect to "Smart Licensing Portal and Meraki dashboard" using that public address.

if the switch initiating connecting for smart license you can use source interface :

ip http client source-interface interface-type interface-number

as asked you need also provide configuration bit to look and suggest - if above mentioned solution not correct.

[Badger-Fi]

"This was not clear to me that, why does the switch initiate the connection to above mentioned portals ? is the for smart License ?"

yes, that is correct

Also, yes, I have heard of the "ip http client source-interface...".  Does this include both 80 and 443?  I imagine I need both to access the Meraki dashboard and tools.cisco for licensing.

[Badger-Fi · Accepted solution]

I figured it out.  I found the command @balaji.bandi was talking about, last night, and I applied it this morning.  Applying that command fixed the switch reporting to Cisco Software Central but DID NOT fix the switch reporting to Meraki.  When running the onboarding prechecks with the Cloud Monitoring for Catalyst tool, the switch would fail precheck testing connection via 443.  A little research turned up that it uses telnet across 443 to make this happen.  I had to add transport output telnet to my VTY lines which was only half of the solution.  I then checked to see if there was something similar to "ip http client source-interface" for telnet specifically, and there was.  I added "ip telnet source-interface <interface>" which solved the Meraki problem.

So the solution to my problem was adding the following commands:

ip http client source-interface <interface>

ip telnet source-interface <interface>

[balaji.bandi]

glad the suggestion works for smart license, since that is the way to configure.

I have not tried using Meraki Dashboard - but looking at the document it used same http client source interface to contact meraki dahsboard:

https://documentation.meraki.com/MS/Deployment_Guides/Getting_started%3A_Cisco_Catalyst_9300_Management_with_Meraki_Dashboard