Product Information
- Model: Cambium XV2-21X
- Deployment: Multiple APs managed under the same WLAN
- Switch: Cisco Catalyst C1300-24FP-4G (PoE+)
- Current Firmware: 6.6.2-r4
- Affected APs: Child Room and Master Bed
Problem Summary
We are experiencing unexpected reboots on two XV2-21X access points running firmware 6.6.2-r4.
The APs reboot without any manual intervention. Prior to the reboot, the wireless services appear to stop functioning and the radios become unavailable.
The issue has been observed on multiple APs, not just a single device.
Observed Symptoms
The AP logs repeatedly show:
Connect failure while connecting to wifidservice wmd has not checked in yetservice rfmd has not checked in yetRadio0 is disabledRadio1 is disabled- Continuous attempts to reconnect to
wifid - Unexpected reboot afterwards
Example log messages:
Connect failure while connecting to wifidservice wmd has not checked in yetservice rfmd has not checked in yetRadio0 is disabledRadio1 is disabled
Network Environment
- Cisco Catalyst C1300-24FP-4G PoE Switch
- Multiple XV2-21X APs
- Same SSID across all APs
- Roaming enabled
- Only two APs have experienced the reboot issue so far.
PoE Verification
The AP reports:
Platform Requirements:
- Minimum boot power: 6.00 W
- Maximum power draw: 12.95 W
Power status:
- Physical Layer: 802.3at (PoE+)
- Available power: 25.55–30.00 W
- LLDP negotiated power: 12.90 W supplied
Cisco switch power status:
- Total PoE Budget: 375 W
- Current usage: approximately 31 W
- No PoE overloads or power budget exhaustion observed.
Event Log Observations
Additional events observed include:
- Client roaming events
- Occasional ARP flood detection
- No indication that these events directly trigger the reboot
The reboot is consistently preceded by wireless service failures (wifid, wmd, and rfmd).
Current Firmware
Most APs:
- 6.6.2-r4
One AP:
- 6.5-b6 (not affected by this issue so far)
Troubleshooting Performed
- Verified PoE budget on Cisco Catalyst switch.
- Verified AP power negotiation.
- Confirmed switch is not overloaded.
- Checked AP event logs.
- Confirmed the issue occurs on more than one AP.
- No obvious cabling or PoE faults identified.
