Who This Is For
This checklist is for network engineers and IT managers responsible for deploying Extreme Networks access points—specifically the Extreme Networks Wi-Fi 6E Access Point Indoor units—and the associated router and jack infrastructure. If you're staring at a deployment plan or about to open that first box, this is your playbook.
I've been handling network infrastructure orders for 8 years. I've personally made (and documented) 14 significant mistakes, totaling roughly $12,400 in wasted budget. Now I maintain our team's pre-deployment checklist to prevent others from repeating my errors. This particular list has caught 47 potential issues in the last 18 months.
The 12-Point Pre-Flight Checklist
Step 1: Verify AP Model & Region Code (The 'Are You Sure?' Check)
This sounds insultingly simple, but it was my first major error. In September 2022, I ordered 24 Extreme Networks Wi-Fi 6E access points for a new office build-out. It wasn't until they arrived that I realized I'd ordered the 5 GHz model, not the 6E version we needed for our new spectrum strategy.
Check this:
- Does the part number match the purchase order (PO) line item? Don't trust the description—verify the SKU against the datasheet.
- Is the region code correct? A US model (e.g., AP3965i-FCC) won't work in an EU (ETSI) environment, and vice versa. This gets overlooked constantly.
- Does the included bracket match your mounting surface (ceiling tile vs. hard drop)? We once had to delay a deployment by 2 days because we needed special adapter plates (ugh).
My rule: I don't sign off on the receiving report until I've visually confirmed the model number and region code on at least one unit from the shipment.
Step 2: Review the Network Jack & Cable Spec Sheet (The 'Hidden Cost' Trap)
This is where most people get tripped up. You've got the APs. You've got the router. But what about the jack in the wall? The network jack and its termination matter immensely for a 6E deployment.
I only believed in checking this after ignoring a vendor's warning and eating a $890 mistake. I'd ordered Cat6a patch cables for the APs. They looked fine on paper. But the existing wall jacks in the building were wired with Cat5e. The result: we could only negotiate a partial 6E link rate because the cabling couldn't sustain the frequency.
Your pre-flight check:
- Verify every planned AP drop has a corresponding Cat6a (or better) jack. Not just the cable in the ceiling—the termination point at the wall plate.
- Ask your facilities team for a certification report. If they don't have one, budget for a fluke test (this gets into electrical engineering territory, which isn't my expertise—I'd recommend consulting your structured cabling partner).
Step 3: Check the PoE Budget Against the AP's Power Draw
APs are power-hungry, especially 6E models with all radios turned on. A standard PoE+ (802.3at) switch port provides 30W. An Extreme Networks AP with 4x4 scanning might draw 28W. That leaves almost no headroom for things like USB-powered IoT sensors.
Here's where the checklist gets specific:
- Calculate total PoE draw per switch: Add every AP's max power draw (not the average). The spec sheet lists it.
- Does your switch have a PoE budget that exceeds this total by at least 20%? If not, you'll see APs randomly rebooting when the office kicks in at 9 AM.
- (Mental note: I really should document the PoE headroom on our network diagram—it saves troubleshooting hours.)
Step 4: Validate Router Configuration for SD-WAN & Cloud Management
Most people think the router is just a gateway to the internet. In a modern Extreme Networks deployment, it's the control point for your SD-WAN tunnels and cloud management (e.g., ExtremeCloud IQ).
My experience is based on about 35 router deployments, primarily the VX-N series. If you're using a different model (say, a legacy VDX), your mileage may vary. But the principle holds:
- Is the router's WAN interface configured for your ISP's MTU? We once saw 30% throughput drop because the MTU was set to 1500 but our ISP used 1492 (PPPoE).
- Are the SD-WAN tunnels pointing to the correct cloud controller IPs? This sounds basic, but I've seen a checklist failure where a junior engineer hardcoded the wrong IP address. The APs couldn't phone home.
- Have you configured a secondary management path? If the primary WAN goes down, can the router still reach the cloud? This is one of those 'prevention over cure' moments. 5 minutes of verification beats 5 days of truck rolls.
Step 5: Site Survey & Channel Plan (The 'Visual vs. Real' Gap)
Everyone thinks their site is empty. Then they deploy 24 APs in a single floor, and the co-channel interference is deafening. I once did a 40-unit deployment in a high-density classroom building. We used a predictive survey. The density map looked perfect on screen. But the real RF environment was a mess because we hadn't accounted for the metal filing cabinets in the walls (ugh).
This is where the checklist differs from theory:
- Do a manual walk-test with a spectrum analyzer. Don't trust the predictive tool alone. (I'm not an RF specialist, so I can't speak to the nuances of modulation—I focus on the practical deployment outcome.)
- Define your channel plan before you power on the APs. Use DFS channels if possible. If you're in range of an airport radar, avoid them. (Source: regulatory requirements from FCC Part 15; verify current regulations at fcc.gov.)
- Set a minimum RSSI threshold for client roaming. I've saved countless support calls by setting this to -72 dBm on our Extreme Networks controller. It prevents clients from sticking to a weak signal.
The Forgotten Step (Step 5b): Validating the CVS Blood Pressure Monitor Integration
Okay, this is the curveball. You see 'jack, cvs blood pressure monitor' in the title. In a healthcare or wellness setting, you might need to integrate a CVS blood pressure monitor (or similar medical IoT device) onto your network. These devices often use 2.4 GHz only. They don't roam well. They may not support WPA3.
What to check before deployment:
- Is there a dedicated SSID for the medical devices? Don't mix them with corporate traffic. We did this once, and the monitor kept disconnecting because the AP tried to push it to a 5 GHz band (it couldn't use it).
- Have you checked the device's receiver sensitivity? Some older monitors (circa 2020) have poor radios. If your APs are mounted in the ceiling, the signal might be weak at waist height. This requires a deliberate RSSI test at the patient location.
- Does your network policy allow the device to connect? We had a scenario where the hospital's NAC policy blocked the MAC address of the monitor. 2 days of troubleshooting for a simple fix (note to self: document this in the onboarding checklist).
Common Mistakes to Avoid
- Not testing in a non-production environment. We once deployed a new Extreme Networks AP firmware across 20 APs. It broke the 6E radio on half of them. Test on one AP first (circa Q4 2024, this rule is still pounded into my head).
- Forgetting the physical security. A $1,200 AP is a target. Ensure your jacks are either secured behind a lock or in the ceiling. I've seen this in a public library—three APs disappeared over a weekend.
- Relying on 'auto-sense' for everything. Your router's auto-MDI/X setting might not work with a substandard patch cable. Always use a cable tester before deployment.
Final Thought
The 12-point checklist above (technically 5 + 1 bonus) is not exhaustive. I've only worked with Extreme Networks gear for about 200 orders. If you're using a different vendor, your experience might differ. But the core principle holds: prevention over cure. That 10-minute check before installation saves you a 2-day rework.
Prices as of early 2025—verify current pricing with your Extreme Networks distributor.