What MX client tracking method would you use with a 9300L-M core?

[steakandeggs]

We've got 9300L's in the core do routing for all our subnets, and a pair of MX's in front of them with a transit subnet between. I've usually done unique client identifier with such a design, but only when it was MS switches. We have had intermittent problems with some client traffic through the firewall randomly and occasionally failing. This is consistent with behavior I've seen in the past where we had to split the network into separate switching and routing and track via IP address. Only did that when the core was non-Meraki though. 

[RWelch · Accepted solution]

> What MX client tracking method would you use with a 9300L-M core? Unique Client Identifier

Client-Tracking Options
Onboarding a Catalyst 9000 series switch for Cloud Monitoring will automatically enforce "Unique Client Identifier" as the tracking method for the network. 

See Cloud Monitoring for Catalyst Onboarding for additional details.

This is also the case for Meraki Managed C9300 switches on firmware version A2 (IOS XE firmware).

Also Noted:
Note: Only the MX Security Appliance has the option to use Unique Client Identifier or track clients by IP. All other Cisco Meraki devices will only distinguish clients based on MAC addresses.

Note: The following ports don't support Client Tracking features on MS390 & C9300/L/X-M.

1. Ports with supported max speeds 25G, 40G, 100G.

2. Link Aggregation ports