Ansible Playbook stopped on recently arrived MS120-24P

[a12288]

We have received a number of MS120-24P somehow my Ansible Playbook used to provision them stopped working, seems like to complain the "wrong" API key. While my Playbook still works on the previous Meraki switches, and I can use Postman to re-produce this problem, which using the same API key to access previous Meraki switches somehow it just does not work on the newly arrived switch. Any thoughts on this? Thanks. Leo

[PhilipDAth]

Are the new MS120 switches located in the same Meraki network as the existing ones (in the Dashboard) where the play book works?

If not, you may not have access to where they have been claimed to.

[a12288]

Yes, the new MS120 switches will be on the same network as current working MS120, I claimed the new ones and assigned them to the production network and I can see the new MS120 in the dashboard and can manually configure them but just the Ansible Playbook won't work, even a the simple Postman call does not work while all work at the previous MS120 switches.

It took almost 1 year for these MS120 to arrive and the last time I provision MS120 was almost 1 year ago. Feel like I missed something here.

[alemabrahao · Accepted solution]

Just create a new API key and try again.