Use this article when a Cisco Meraki network, a location, or an access point (AP) does not appear in the Cloudi-Fi admin console, or when an AP is attached to the wrong location.
The Meraki integration synchronizes with Cloudi-Fi every two hours. The synchronization imports Meraki networks as Cloudi-Fi locations and uses the MAC addresses of the APs to identify each location.
Which case applies?
- A network or location is missing: steps 1, 2, and 3.
- An AP is missing, or attached to the wrong location after a move or replacement: steps 3 and 4.
- The setup does not use the API integration: step 5.
Prerequisites
Before starting, ensure that you have the following prerequisites:
- Access to Cloudi-Fi's admin console
- Access to the Cisco Meraki dashboard
1. Check the integration status
In the Cloudi-Fi admin console, go to "Configuration" > "Integrations" > "Meraki". The integration has three states:
- Green, in sync. All configured data is synchronized.
- Orange, pending. An action is required before the integration can continue. Open the integration and complete the pending actions, such as selecting detected networks.
- Red, failure. The last synchronization failed. Check the API key rights in step 3.
2. Check the synchronization settings
Open the integration settings and check each parameter:
- Meraki cloud: World or China. It must match the cloud of the Meraki organization.
- Create locations: from networks, or from AP tags. Locations are created from the selected option only.
- Import: MR and MX, only MX, or only MR. Devices of an excluded type are not imported.
- Scan: everywhere, or only some networks or network tags. With a selective scan, new networks appear in the integration as detected but are not imported until selected. Select the missing network.
Save the integration. Saving starts a synchronization.
3. Check the API key rights
The API key is linked to the Meraki administrator who generated it. The role and scope of this administrator define what Cloudi-Fi can see.
- In the Meraki dashboard, go to "Organization" > "Configure" > "Administrators".
- Find the administrator who generated the key and check the role. "Observer" is enough to synchronize networks and AP MAC addresses. "Full access" is required only if Cloudi-Fi must also push the SSID configuration.
- Check the scope. An organization-level scope is recommended. A scope limited to some networks hides the other networks from Cloudi-Fi. Limited access roles are not compatible.
- Confirm that the administrator account is still active and that the key was not deleted or regenerated. If needed, generate a new key in "Organization" > "API & Webhooks" and update it in the Cloudi-Fi integration. An administrator can have two API keys at most.
- If access to the Meraki API is restricted by IP address, ask Cloudi-Fi support for the current source addresses to allow.
For more detail, see Meraki API Permissions.
4. Check the APs in the location
- In the Cloudi-Fi admin console, open "Locations" and edit the affected location.
- Open the "Network Parameters" tab. The MAC addresses of the APs are listed there after a successful synchronization.
- Compare them with the APs in the Meraki dashboard, under "Wireless" > "Monitor" > "Access points".
- If an AP was moved to another network, or replaced, save the integration to force a synchronization, or wait for the next one. A replaced AP has a new MAC address.
Do not delete and recreate locations, and do not save the integration repeatedly. Both can make the mismatch harder to diagnose.
5. Check a setup without the API integration
If the Meraki API integration is not used, Cloudi-Fi does not import APs. Add the name and the MAC address of every AP in the "Network Parameters" tab of each location. Write MAC addresses in lowercase. Add the new MAC address each time an AP is replaced.
Contact your support
If the information is still missing or wrong, contact the Cloudi-Fi support team and share the following information:
- The name of the Cloudi-Fi location and of the Meraki network
- The serial number or MAC address of the AP, and the date it was moved or replaced
- The status of the integration and a screenshot of its settings, with the API key hidden
- The role and scope of the administrator who generated the key
Never send the API key itself.