This is possible, with or without WoL configured on the port.
It's also possible with or without the "switchport access vlan XXX" command. But FYI, if you remove that command, then you effectively have an implicit "switchport access vlan 1" command. That's OK though, since a port is in no VLAN until 802.1X completes on the port, so if you dynamically assign the VLAN via RADIUS, it'll work fine.
We've seen some customers attempt to use VLAN-1 in this manner for an extra security blanket, since standing best-practices of not trunking/routing/using VLAN-1 may already apply.
In fact when you type "switchport access vlan 69" on a interface and "dot1x control-direction in" and all other command to activate 802.1X, you can use Wake on Lan on the machine connect to the interface and it's work fine.
However when you disable "Switchport access vlan 69" to let ACS attribute VLAN69 for interface who are connect to the PC, the Wake On Lan don't work Fine.
I say that if you use VMPS, the Wake On Lan don't work and perhaps it's the same idea.
In fact i have read on doc and test that Wake on Lan Work with 802.1X and Static assign VLAN but i want to say if it work with 802.1X and Dynamic assign VLAN
Please feel free to share details, or a TAC case .. b/c this sounds like a software bug. From an 802.1X and/or WoL perspective, there should be no difference in VLAN1 vs. VLAN69, which is effectively what your decription dictates.
Transferring Crash file from standby: Login to the Active WLC in HA.
From CLI: (Cisco Controller) >transfer upload datatype crash (Cisco
Controller) >transfer upload filename (Cisco
Controller) >transfer upload mode tftp (Cisco Controller) >transfer
This is the start of a display filter cross reference between Wireshark
and OmniPeek. The 1st installment is a table of advanced filters. More
filters will be added as time allows. It is a living doc, so check back
for changes every so often Please feel f...