Network-wide -> Monitor -> Clients

Solved
CatalinD
Here to help

Network-wide -> Monitor -> Clients

Hello,

 

We have noticed an issue with monitoring our clients connected to the network.

We have multiple hosts connected via cable and/or wirelessly through some FortiAPs.

Despite this, we are currently seeing only 2 hosts in Network-wide -> Monitor -> Clients.

 

I would like to mention that everything was working normally until 08.04.2025.

This is unusual, and we cannot associate it with any specific change or event, as we are still seeing only 2 clients in this tab.

If we change the graph to a one-month view, we can see even the APs' MAC addresses, etc.

CatalinD_0-1746523767941.png

CatalinD_1-1746523986671.png

 

We are running some C9300L-48P-4X on CS 17.2.1 firmware. n292

 

We have tried other browsers and clearing the cache.

1 Accepted Solution
BrandonD
Meraki Employee
Meraki Employee

Hi @CatalinD,

 

Do you mind confirming your L3 routing topology (mainly curious if this is handled by Meraki/Cisco L3 switching or a non-Meraki device)?

 

I wanted to provide the following article that plays a major role in how clients are tracked and depending on the topology there are a few example use cases.

 

 

Its also important to note if either of these scenarios apply as the C9300/L is known to have issues with client tracking:

 

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

2. Link Aggregation ports

If you found this post helpful, please give it kudos. If my answer solved your problem, click "accept as solution" so that others can benefit from it.

View solution in original post

8 Replies 8
alemabrahao
Kind of a big deal

Have you done any firmware updates recently? This could be a bug, you might want to open a support case.

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.
CatalinD
Here to help

We updated the firmware on 07.04, but we have the same firmware on other equipment on a different network, where we are able to see the clients.

 

I have opened a support case.

BrandonD
Meraki Employee
Meraki Employee

Hi @CatalinD,

 

Do you mind confirming your L3 routing topology (mainly curious if this is handled by Meraki/Cisco L3 switching or a non-Meraki device)?

 

I wanted to provide the following article that plays a major role in how clients are tracked and depending on the topology there are a few example use cases.

 

 

Its also important to note if either of these scenarios apply as the C9300/L is known to have issues with client tracking:

 

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

2. Link Aggregation ports

If you found this post helpful, please give it kudos. If my answer solved your problem, click "accept as solution" so that others can benefit from it.
CatalinD
Here to help

Hello @BrandonD,

 

We are doing Layer 3 routing on a FortiGate firewall.

On another C9300L, which is located in a different network, we are able to see the clients connected along with their associated MAC addresses.

It is true that there we also have Meraki APs instead of FortiAPs.

Is there any known issue with client tracking on the CS 17.2.1 firmware?

 

BrandonD
Meraki Employee
Meraki Employee

Hi @CatalinD 


I tend to agree with @BlakeRichardson in that a Support case may be the best next step here given the inconsistencies.

 

Ref: https://documentation.meraki.com/General_Administration/Support/Ways_to_Contact_Meraki_Support

If you found this post helpful, please give it kudos. If my answer solved your problem, click "accept as solution" so that others can benefit from it.
BlakeRichardson
Kind of a big deal
Kind of a big deal

I would open a support ticket, it doesn't matter what vendor of AP's or firewall you are using because you have a cloud managed switch in the mix that is what captures your client information. 

 

I suspect it's a firmware issue because it was working before you applied the new firmware. 

If you found this post helpful, please give it Kudos. If my answer solves your problem, please click Accept as Solution so others can benefit from it.
CatalinD
Here to help

Thanks for the support guys!

@BlakeRichardson, that's what I initially thought, but it's strange that we have other switches in separate networks that work without issues. Also, there are two hosts that appear on the Monitor -> Clients page.

I have already opened a support ticket and am waiting for a resolution. I will update this thread if I find anything.

CatalinD
Here to help

Hello everyone,

 

 

The issue was solved. As @BrandonD mentioned, clients will not be visible on trunk ports.

The issue with customers connected to access ports not appearing in Monitor -> Clients was caused by the CS 17.2.1 firmware. After upgrading to CS 17.2.1.1, this issue was resolved.

 

Thank you for your support!

Get notified when there are additional replies to this discussion.