I have a strange problem. I just installed a 1242 LWAPP on a 4506 switch. If I set the port to trunk I can't ping the AP and WCS "looses" it. Clients still see the signal, but if I set the switchport to access WCS can see the device and I can ping it, but no clients can pass traffic on it. Is this a limitation of the switch IOS?
I don't think setting the port as trunk will cause any issue. When you have multiple VLANs you have to configure the ports connecting the WLC as a trunk port. However, the port on which the LAP is connected to need not be configured as trunk.
if you are installing LWAPP APs you are not supposed to set the port to Trunk mode because this isnt necessary. The APs (assuming you are using Layer 3 mode in your controller) get an IP address and use layer 3 to communicate to the controller but everything else is encapsulated via LWAPP. This means all VLANing is controlled on and by the controller.
This isnt a limitation of the switch IOS. I would look further into your configuration of your controller and go from there. Make sure the ports the controller are connecting into the switch are trunked and the native VLANs are set.
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...
I have created a Powershell script to automatically add a Wireless Guest
User on Cisco WLCs. (tested on 2500 Series) The script should be
completely self explanatory. Prerequisites: Powershell SNMP Module
(Install-Module -Name SNMP) SNMP Write Access to y...