I have never used this but I hate to see you have to pull out the Prozac :) The example certainly seems to support WPA/PSK.
Configuring WPA Migration Mode
WPA migration mode allows these client device types to associate to the access point using the same SSID:
â¢WPA clients capable of TKIP and authenticated key management
â¢802.1X-2001 clients (such as legacy LEAP clients and clients using TLS) capable of authenticated key management but not TKIP
â¢Static-WEP clients not capable of TKIP or authenticated key management
If all three client types associate using the same SSID, the multicast cipher suite for the SSID must be WEP. If only the first two types of clients use the same SSID the multicast key can be dynamic, but if the static-WEP clients use the SSID, the key must be static. The access point can switch automatically between a static and a dynamic group key to accommodate associated client devices. To support all three types of clients on the same SSID, you must configure the static key in key slots 2 or 3.
To set up an SSID for WPA migration mode, configure these settings:
â¢A cipher suite containing TKIP and 40-bit or 128-bit WEP
â¢A static WEP key in key slot 2 or 3
This example sets the SSID migrate for WPA migration mode:
As I said, I have never tried this before and sadly can't test this for you as we run Lightweight now. It seems from your first post that you were very close to having this working :) It would be most helpful to see what the "migration mode" config looked like. To me, it seems like this line may have been missing;
AP SSID is also set for "Authenticated key management- WPA- Optional". As noted by Darren from Cisco.
I am currently having the same issue as you did above. When configuring for transition (TKIP + WEP 128 bit) mode my WPA client can connect but my original WEP client cannot. Was a resolution ever found?