Unfortunately, succeeding in your installation seems to be just the first step:
I use RedHat 9.0 and the Aironet PCM352 seems to be correctly installed, but I cannot associate to the AP, while the same ACU version on a RedHat 8.0 works well.
The only difference I could notice so far in the ACU configurations is that the "Using short Radio Headers" in the status window shows Yes on RH8.0 while it says No on RH9.0, although I flagged it in "Edit Properties/RF Network".
Maybe a kernel issue?
I use 2.4.20-8.
Anybody out there succesfully using RH9.0 + AIR-PCM352?
I tried compiling a new kernel, 2.4.22, but nothing changed: still not associating to the AP.
[if you want to re/compile the kernel you need to check the
"Network Device Support > Wireless LAN (non hamradio) > Wireless LAN + Cisco Aironet PCMCIA" options, otherwise you'll get a "No Radio Found" Error when launching ACU]
Then I deselected the "Cisco Compliant TKIP features" on the AP, and I could succesfully associate to it!
A colleague using RH8.0 with a personalized kernel can associate using the same ACU, the same configuration, the same PCMCIA card, an OLDER kernel version (2.4.20.*) and TKIP Features enabled on the AP.
We decided to go without TKIP Features, so for now I cannot investigate further (e.g. installing his same kernel).
With regards to your PCMCIA issue, did you install ACU using the pcmcia_cs sources, as the installation procedure requires? Did you try reinstalling ACU after upgrading to RH8.0?
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...