Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Become a member of the Cisco Meraki Community today
Get answers from our community of experts in record time.
Join now- About K-V
About K-V
K-V
Here to help
Member since Jul 30, 2025
Wednesday
Community Record
7
Posts
3
Kudos
0
Solutions
Badges
Tuesday
1 Kudo
Just wanted to feedback to everyone here. We never found the exact issue, however, we suspect it to have something to do with setup procedure. We eventually just did everything from scratch. Deleted the API key, removed the syslog entries, and deleted the Forescout config. (When we originally started this, we created the API key, and loaded it onto Forescout where it registered. Only then did we change syslog details on the Meraki network.) Then did it all again. New API key, syslog config and Forescout Meraki plugin load and config. This time, we created the API key, configured the syslog events on Meraki network and only then loaded the API key on Forescout (once all the Meraki setup steps were done) I can't imagine how the procedure would make a difference, but at least worth noting the steps I guess. We are now facing a 10 min window, instead of 12 hours like before. VAST improvement. Still not near instant as when using postman, but much better. We will be playing with timers on Forescout to see if this can be improved as well. If we manage to improve this, I'll feedback here. Almost wish we can reproduce the 12 hour issue now to find the actual problem...
... View more
a week ago
yup - checked the API dashboard page. no rate limits hit. however, I do see a ton of successful calls made. not sure if this is normal. still looking at various options to test this further.
... View more
a week ago
postman works without issue. no delay. curious about your suspicion. will DM for some more info
... View more
2 weeks ago
Has anyone actually got the Forescout API working to change Meraki MS switchport VLAN settings based on Forescout configurations? We are trying to get this working, but are getting extremely long times between the Forescout sending the API PUT call, till the switch actually receives it and makes the change. Sometimes in excess of 12 hours. Obviously, this is not going to be a great help for dynamic VLAN changes when a device is plugged into a port...12 hours is not a great wait time. We have a network switch, setup with no complex configs - basic VLAN for access, and trunk port. This is registered to the cloud no issues and can ping the Forescout appliance. We have the Forescout appliance loaded with the Meraki plugin and configured with the API key. It all seems to be going OK. Until we want to start using this on Meraki access switches. The Forescout gets the syslog event message, and generates the API call and sends the PUT msg. But then the switch doesnt do anything - no API call received or anything until an average 12 hours later. only then does it apply. What we need to do is change a VLAN, based on the user's group when they connect up. We have load the API key, and configured the syslog server on the Meraki network. The Meraki plugin on the Forescout appliance seems to be working, and it can discover the switch. I can't help but feel like were missing something obvious, but I dont know where to look. I'm not super familiar with Forescout (we have another engineer taking care of this part), but I have full access on the Meraki stack. Has anyone actually gotten this to work using API calls? is there anything else i need to do to make this to work, other than the API key, and syslog configuration?
... View more
Jul 30 2025
9:02 AM
2 Kudos
Thank you so much for this. This worked! I'll alert the support team to this too. logged a ticket and everything for this
... View more
Jul 30 2025
5:15 AM
I'll try the new API key thing tonight (currently in use by monitoring settings) no, our networks are not using a template. going to try some other methods as well. hoping to find a fix soon. I really wanted to roll this out to other networks for our POC.
... View more
Jul 30 2025
4:05 AM
I'm currently working on testing Meraki Access manager. so far, it is working quite well. Very easy to setup and manage. I have implemented this on 2 different networks already on physical switch ports. however, today, when I tried to create a new SSID on another network within Org, it doesnt work when selecting Access manager for its access control method. I can create set other access control methods, just not Access Manager. the error states "There were errors in saving this configuration: ["{\"error\":\"Expected Valid Dashboard or API Token\"}"] We have a valid API key for this dashboard. Also not sure how this is related, as the API key has nothing to do with Access Manager as far as I know. Anyone else experiencing the same thing? or at least have it working on 2 different SSIDs, at 2 different locations/networks?
... View more
Labels:
- Labels:
-
Administrators
-
Other
My Top Kudoed Posts
© 2025 Cisco Systems, Inc.
