cancel
Showing results for 
Search instead for 
Did you mean: 

Meraki Dashboard Reporting: How can I get a csv of All Clients on ALL networks in an organization?

Highlighted
Comes here often

Meraki Dashboard Reporting: How can I get a csv of All Clients on ALL networks in an organization?

I'm administrating a decent size Meraki Organization, it currently has ~650 networks with every network consisting of a single MX65 and 1-3 MR33's.

 

Is there a Meraki Dashboard report that I can run that will give me a listing of all Clients connected to all networks in that organization? I'd like it to be in an .csv and sorted by Network name.

 

I think I can probably do it via API, but it'd be nicer if I could use something that already exists.

 

Thanks!

5 REPLIES 5
Kind of a big deal

Re: Meraki Dashboard Reporting: How can I get a csv of All Clients on ALL networks in an organizatio

There isn't anything that I know of to do this in the Dashboard. API is your friend here, though even that route means you have to get a list of clients per device, so you're making a call to get every device in the org, then a call for each device to get the clients. 

Comes here often

Re: Meraki Dashboard Reporting: How can I get a csv of All Clients on ALL networks in an organizatio

Hmm that was what I was afraid of.

 

I already wrote a script that cycles through the 650 networks and checks for new Meraki hardware at each site. If new hardware is found, it gets a few tags added as well as gets a physical address (and moves the pin on the map) from a external csv file.

 

So doing this won't be too much different, a lot of the logic is already in place.

 

Thanks for the prompt response.

Getting noticed

Re: Meraki Dashboard Reporting: How can I get a csv of All Clients on ALL networks in an organizatio

Not the best option but we put all of out APs and Switches in their own Network so we could do just that, see all the devices connected across our whole network.
Kind of a big deal

Re: Meraki Dashboard Reporting: How can I get a csv of All Clients on ALL networks in an organizatio


@Willie_McDonald wrote:

Hmm that was what I was afraid of.

 

I already wrote a script that cycles through the 650 networks and checks for new Meraki hardware at each site. If new hardware is found, it gets a few tags added as well as gets a physical address (and moves the pin on the map) from a external csv file.

 


You can get all devices in an Org with a single call instead of going through each network:

 

https://api.meraki.com/api_docs#return-the-inventory-for-an-organization

 

Not sure if that'll work for you, but it DRAMATICALLY reduces the time on my scripts to iterate through my Orgs to get individual devices. 

Meraki Employee

Re: Meraki Dashboard Reporting: How can I get a csv of All Clients on ALL networks in an organizatio

@Cmiller putting all APs into a single network *might* be fine for your deployment, but could also go against a common best practice, but again it depends on your deployment.  Each wireless network is meant to be more of a single site or physical location, like a single branch office, or a corporate office building or group of buildings, or a single school (or perhaps a middle + high school on a common campus, or a single college or university campus for example.  The point is that each of these is a single contiguous AutoRF domain for which all of the APs make their RF decisions about channels and power.

 

I usually use the example of a K12 school district as an example, you would not want to have a single district-wide wireless network across every school. That would be a single large AutoRF domain for buildings that are miles apart, way out of RF range from one another, but they all have to run the same instance of an AutoRF algorithm.  You could potentially have APs in a high school making RF adjustments based off of changes that stemmed from a different school miles away.  That doesn't tend to happen, and RF adjustments tend to remain localized, but it's possible, and inefficient since the majority of the computations involving other schools are unnecessary algorithmic noise.

 

I've seen K12 districts run district-wide wireless networks just fine, but it's definitely less than ideal, and the best practice is to divide up the RF domains into a network-per-site so dozens or hundreds or even thousands of APs don't all have to run the same instance of an algorithm when they're way out of range anyway.

 

Even in the university campus example I gave above, some decide to do a network-per building approach, like for large dorm buildings, versus a single campus-wide network, while others have separate campus-wide networks broken out for dorms, academic buildings, and general outdoor and common areas, while still others do have a single campus-wide deployment (less common).  Just rules of thumb, lots of variables and of course every deployment's different.

 

The switch network is another story, there it might be more common to have a campus or district-wide switching network but with wireless networks broken out site by site.  Only thing there is you wouldn't have site-by-site combined MS+MR networks in Dashboard, likely not a big deal, but it depends.

 

Welcome to the Meraki Community!
To start contributing, simply sign in with your Cisco account. If you don't yet have a Cisco account, you can sign up.