I have couple of sites using AIR-AP1242AG-A-K9 with 4400 WLC and 3750WLC. As a part of expansion we bought some more LAP but mistakenly bought AIR-AP1242AG-E-K9 instead of AIR-AP1242AG-A-K9. and of course this new AP's are not working with the none of WLCs. Its obtaining the IP using discovery but won't come online. Is there a way to use this 'E' (I hope its European) AP's with current environment? Any help on this would be greatly appreciated.
Operationally, you can't get the "-E" AP to join a WLC with "-A" regulatory domain enabled.
Some people would like to recommend that you enable the "-E" alongside the "-A" regulatory domain but some of us DO NOT recommend you do this. You see, when you enable "-E" and "-A", it not only contrevene telecommunications regulations but, operationally, you'll get more trouble.
802.11 wireless regulation for "-A" and "-E" are in conflict. This means half of your radios will go into "Adminstrative disable" because only COMMON regulatory rules will be enabled. Regulatory rules which are in conflict with each other, like 802.11a/n, will be disabled.
The real options you've got is to run your "-E" AP in autonomous mode or talk to the reseller and ask them (nicely) to take the old APs back.
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...