Caps connected to Caps-Man with RADIUS (NPS) authorization has a problem with obtaining an IP address. Although the authorization is successful and the device is visible on the list of connected devices.
In the logs in the DHCP server (the same device with CAPS-MAN), we have failed attempts to forward the addressing.
Turning off the WLAN and turning it back on on the CAP solves the problem (without restarting the device).
All devices are using the latest firmware
CAPs - cAP ac - 6.48.3
CAPsMAN and DHCP-SRV - CCR1036-8G-2S+ - 6.48.3
Aug 17, 2021 @ 13: 13: 52.000 ROUTER-CAPSMAN wifi <46> Aug 17 13:13:52 ROUTER-CAPSMAN wifi: 50: 2F: 9B: XX: XX: XX @ 5G-XX-AP-XX-XX -29-1 disconnected, registered to other interface
Aug 17, 2021 @ 13: 13: 52.000 ROUTER-CAPSMAN wifi <46> Aug 17 13:13:52 ROUTER-CAPSMAN wifi: 50: 2F: 9B: XX: XX: XX @ 5G-XX-AP-XX-XX -20-1 connected, signal strength -60
Aug 17, 2021 @ 13:12: 38.000 ROUTER-CAPSMAN dhcp <46> Aug 17 13:12:38 ROUTER-CAPSMAN dhcp: dhcp-vlanXXX assigned XX.XX.XX.204 to 50: 2F: 9B: XX: XX ; XX
Aug 17, 2021 @ 13: 12: 33.000 ROUTER-CAPSMAN wifi <46> Aug 17 13:12:33 ROUTER-CAPSMAN wifi: 50: 2F: 9B: XX: XX: XX @ 5G-XX-AP-XX-XX -20-1 disconnected, registered to other interface
Aug 17, 2021 @ 13: 12: 33.000 ROUTER-CAPSMAN wifi <46> Aug 17 13:12:33 ROUTER-CAPSMAN wifi: 50: 2F: 9B: XX: XX: XX @ 5G-XX-AP-XX-XX -29-1 connected, signal strength -66
Aug 17, 2021 @ 13: 09: 10.000 ROUTER-CAPSMAN warning <44> Aug 17 13:09:10 ROUTER-CAPSMAN warning: dhcp-vlanXXX offering lease XX.XX.XX.204 for 50: 2F: 9B: XX: XX; XX without success