Migration & Installation of New or Replacement
Meraki Access Points: What Actually Works
Wireless access point refreshes sound simple on paper: buy new hardware, swap it in, done. In practice, your Meraki AP migrations will likely turn up a few real-world wrinkles. Here is a process you should follow to get everything cut over cleanly with zero extended downtime for your end users.
Before You Touch Anything!
You will need a few things in hand before your Meraki AP migration starts:
Admin Access To The Meraki Dashboard: Not just any login. You need rights to add hardware and licenses to the specific organization and network you will be working in.
Cloud ID Information: Every Meraki device has a Cloud ID (order number) tied to it, and you will need it to claim the device into the dashboard. You can find this in the purchase confirmation email. If that's not handy, the Cloud ID is also printed directly on the device itself and on a sticker attached to the unit, so you can pull it straight off the hardware. You should photograph each label before mounting the AP, so you aren't standing on a ladder squinting at a barcode later.
The Correct Network Selected: Before adding anything, you must confirm you are logged into the dashboard and pointed at the correct network. Adding a device to the wrong network is an easy mistake and an annoying one for you to unwind.
Once you have those three things, you will add the access points through the dashboard's access point management section, entering the Cloud ID for each device you are bringing onto the network.
Adding New APs & Licensing to Portal
With the correct network selected, you should add the new access points through the dashboard's Add APs function (found under Wireless > Monitor > Access points, or the Organization-level "Add devices" flow). You will enter the Cloud ID (order/serial info) for each device one at a time. This is the step where you actually claim the hardware into the organization and network, utilizing the Cloud ID information you gathered earlier.
You should treat licensing as its own distinct step rather than assuming it happens automatically. Before you claim the new hardware, ensure you add the licenses for the new APs to the license management in the dashboard. This ensures that once you claim each device, it has a license ready to attach to it. If you skip this, or if you do not have enough license capacity for your new APs, the devices will be held up from coming fully online even if you claimed them correctly.
The Power Problem (And How You Can Fix It)
If you are installing newer access points like the Meraki CW9166 units (tri-radio Wi-Fi 7 APs), you will face real power requirements. You may find that your existing switch doesn't have enough PoE budget to fully power the new APs. The result will be flapping: your APs will boot, lose power, and drop again mid-setup.
To fix this, you should use a compatible PoE++ switch or use 90W PoE injectors; making sure you wire any injectors in the right order:
Connect the LAN cable from the switch into the injectors' data-in port.
Connect a cable from the injector's power-out port to the already-run cable heading to the AP's mounted location.
Once you have the injectors in place, your power problem will be resolved. Your APs will come up clean and stay up, with no further flapping or brownouts.
Stage Everything Before You Cut Anything Over
Rather than pulling an old AP and hoping the new one comes up, you should connect, claim into the dashboard, and set to the correct network every new access point first—all before you touch any old hardware. You should verify each new AP is online and passing traffic while it sits next to (not yet replacing) its old counterpart.
One thing you must plan for: a newly claimed AP can take 10 to 15 minutes before it shows as active and online in the dashboard. You will see this delay normally, especially on first boot when the unit is pulling down firmware.
It's not a sign something is wrong. You just need some patience.
The Cutover: One AP at a Time
With all your new APs staged and verified, you should perform the actual swap one access point at a time:
Physically replace the old AP with the new one at that location.
Wait for the new AP to come online in the dashboard (again, expect 10-15 minutes) and confirm the firmware has finished updating.
Confirm the correct SSIDs are broadcasting with correct VLAN tagging at that location.
Verify clients can connect and pass traffic (DHCP, internet access, and correct network segmentation) through that AP.
Confirm stable PoE power delivery with no flapping or link errors on the switch port before you move on.
Only then should you move on to the next AP.
By going one at a time, rather than pulling every old AP first, you ensure that if something goes sideways at one location, the rest of your wireless network remains untouched and still serving clients.
Closing Out: Documentation & Licensing
Before you remove any old access point from the dashboard, you must record its hardware information:
Associated Cloud IDs
You need these records for two reasons: to document exactly what you decommissioned for your files, and to tie back to the Meraki licensing for that device. Once you confirm every new AP is stable and passing traffic, you can remove the old APs from the dashboard and close out the visit with full documentation of what you replaced.
Future Planning Note: You should keep an eye on the switch's total PoE budget before adding any further PoE-powered devices. If you have more high-draw hardware on your roadmap (additional Wi-Fi 6E/7 APs, PoE cameras, and the like), you will want to consider a switch upgrade before power limits become an issue mid-install again.
The Takeaway
The Meraki dashboard makes access point management straightforward once you claim your devices. However, the steps you take around the dashboard (having the right paperwork, solving power delivery before it becomes a mid-install problem, staging new hardware fully before cutover, and documenting what comes out) are what will separate your smooth migrations from stressful ones. None of it is complicated, but you will easily find out the hard way what happens when you skip one of these steps.
Troubleshooting Notes
You may run into a few issues along the way, so here is what you should watch out for during this kind of migration:
AP flapping or failing to fully power on: This usually means your switch's PoE budget is insufficient for the AP's power class. Newer tri-radio APs draw more power than older single or dual-radio models. You will need a PoE injector rated for the AP's actual power requirement to solve this. Do not assume an older or lower-wattage injector you have on hand will work.
Injector wired in the wrong direction: The injector has a data-in side (toward the switch) and a power-outside (toward the AP). If you get this backwards, it will keep the AP from powering up correctly. You should double-check the port labeling before connecting.
AP not showing online right away: Give it 10-15 minutes before you begin troubleshooting further. You will find this is typical, especially on first activation.
Added to the wrong network: You must confirm the target network in the dashboard before claiming any device. If you end up putting a device in the wrong network, you can move it, but it's simpler for you to get it right the first time.
Missing Cloud ID / no purchase email on hand: Check the device itself and the sticker on the unit. Both carry the Cloud ID you need to claim it.
New AP claimed but not fully active: Check your license capacity in the dashboard. If you don't have enough licenses to cover the new devices, your claimed AP may sit unlicensed even though you added it successfully. You should add license capacity before or immediately after claiming.
License didn't seem to transfer after removing the old AP: Your experience will depend on the licensing model. Co-term licensing typically frees up automatically once you remove the old device, since the replacement is already claimed on the network. Per-device licensing may require you to manually reassign the license from the old AP to the new one, so you should check this before assuming it's automatic.
Created & Maintained by Pacific Northwest Computers
📞 Pacific Northwest Computers offers Remote & Onsite Support Across:
SW Washington including Vancouver WA, Battle Ground WA, Camas WA, Washougal WA, Longview WA, Kelso WA, and Portland OR
No comments:
Post a Comment