I am trying to find out the answer to this issue. I have version 5.5.1 running on a VVX 411 and am able to authenticate the phone against my RADIUS server using EAP-MSCAPv2 authentication.
The RADIUS server is setup to auto assign the VLAN ID back to the Avaya Switch. I have ran multiple traces and can confirm that the phone is authenticated and placed into the correct vlan.
All devices start in a static VLAN and if they fail authentication they can be remediated from there. I don't even see the MAC of the phone show up in the 'staging' DHCP scope.
The DHCP server never receives the DHCP request after the EAP portion is complete. I have also plugged in a Windows 10 laptop into the PC port on the phone and it will authenticate correct and does obtain an IP address.
I have no DHCP issues if I disable EAPoL autentication on the switch and manually place the phone in the VLAN.
During my research I found out that the supplicant on the phone is 802.1x-2004, and older code revs from Avaya only supported 802.1x-2001.
The code rev I have running on my ERS 5632 is 6.6.3 and has 2004 support.
Any idea why the phone is unable to obtain a DHCP IP after it is flipped into a new VLAN?