Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Register or Sign in
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
About Ilya_Kisel
Community Record
8
Posts
1
Kudos
1
Solution
Badges
4 weeks ago
Hi Meraki developers, I noticed that API GET: /organizations/{organizationId}/policyObjects?perPage=100 response header "Link" is always empty. I have 200 policy objects. Via paginated request I can receive only the first N (for example 100) entries, "Link" response header is empty and I consider that there are no more objects. Request: curl -L --request GET \ --url https://api.meraki.com/api/v1/organizations/xxx/policyObjects?perPage=100 \ --header 'Authorization: Bearer xxx' \ --header 'Accept: application/json'
... View more
Mar 2 2023
11:12 PM
1 Kudo
The best solution is: 1) Fetch all clients via GET /networks/{networkId}/clients| 2) Put the fetched clients into a hashtable (Map) with client.id as a key and client as a value. 3) Fetch all clients with group policies via GET /networks/{networkId}/policies/byClient 4) Match clients with policies to clients by client.id, using the Map from step 2. In the end, you will have all clients with their corresponding group policies collected in 2 requests to Meraki API. Both getClients and getNetworkPoliciesByClient requests support pagination with page size up to 1000.
... View more
Mar 2 2023
11:12 PM
The best solution is: 1) Fetch all clients via GET /networks/{networkId}/clients| 2) Put the fetched clients into a hashtable (Map) with client.id as a key and client as a value. 3) Fetch all clients with group policies via GET /networks/{networkId}/policies/byClient 4) Match clients with policies to clients by client.id, using the Map from step 2. In the end, you will have all clients with their corresponding group policies collected in 2 requests to Meraki API. Both getClients and getNetworkPoliciesByClient requests support pagination with page size up to 1000.
... View more
Feb 16 2023
1:16 AM
Hi rbnielsen, thank you. Adding parallelism will definitely reduce the time to collect all client policies by about 5 times (5 because of Meraki rate limiter which allows ~5 requests per second). Anyway, the overall complexity is still O(N), because O(N/5) = O(N) In the topic, I wonder if it is possible to reduce complexity to constant O(1), which is 1 or 2 requests to fetch all data. For example, via https://developer.cisco.com/meraki/api-v1/#!get-network-policies-by-client
... View more
Feb 15 2023
1:11 AM
Hi rbnielsen, thanks for your time, but your solution is the same as my current. Read please the question one more time.
... View more
Feb 14 2023
6:43 AM
Hello Meraki team! I need to map all clients to the corresponding group policies using API, could you please suggest the best endpoint to do it? 1. I found that GET /networks/{networkId}/clients response contains "groupPolicy8021x" for each client. Can you confirm that the client's "groupPolicy8021x" is the client's group policy id? Can you confirm that if "groupPolicy8021x" is null, then the client is not assigned to any group policy? 2. I found an API which looks like an ideal solution: GET /networks/{networkId}/policies/byClient Can you confirm that getNetworkPoliciesByClient endpoint returns a list of all clients and their group policy Ids? 3. My current solution (the same as in https://community.meraki.com/t5/Developers-APIs/Get-all-clients-in-a-group-policy/m-p/83163😞 1) Get all clients in a network: GET /networks/{networkId}/clients 2) For each client retrieve it's policy - GET /networks/{networkId}/clients/{clientId}/policy The current approach requires N + 1 requests in order to load policies for N clients. I have 36000 clients connected to one Meraki network, and it takes 8 hours to carry out 36000 requests to map all clients to the corresponding group policy. Thank you, Ilya
... View more
Jul 28 2022
1:57 AM
Hi, @BreckanM ! Just found that https://developer.cisco.com/meraki/api-v1/#!get-network-appliance-settings GET /networks/{network_id}/appliance/settings response contains information regarding deployment mode, although it is not present in the official documentation. { "clientTrackingMethod": "MAC address", "deploymentMode": "routed" } { "clientTrackingMethod": "MAC address", "deploymentMode": "passthrough" } @Seshu , could you please approve that "GET /networks/{network_id}/appliance/settings" response is a reliable option to retrieve deployment mode? If yes, I suppose you need to update the response example on https://developer.cisco.com/meraki/api-v1/#!get-network-appliance-settings page 🙂 Best regards, Ilya
... View more
My Accepted Solutions
| Subject | Views | Posted |
|---|---|---|
| 645 | Mar 2 2023 11:12 PM |
My Top Kudoed Posts
| Subject | Kudos | Views |
|---|---|---|
| 1 | 767 |
© 2024 Cisco Systems, Inc.
