If I set both interfaces to VLAN 1, I was able by some moments to get http access to the WLC from the network, but one AP on tests was unable to join with the controller (I saw messages indicating LWAPP was receiving requests through unsoported VLAN 0)
If I set both interfaces as untagged (I understand it means VLAN 0) the AP was able to join, but I can't get access to the WLC from the network.
Another history is with APs, I have two 1242 connected through switches, they get IP address by DHCP from the router and eventually they are registered with the WLC, while another AP attached directly to WLC never get IP address and obviously never is registered.
I can't ping any device (router, switches) from the WLC, also any device can ping continuosly to the WLC (I just get some few answers -somebody told me that for the WLC it is normal behavior for security reasons-)
Can somebody give me some tips to identify what Iam doing wrong?
Vlan 1 in a switch environment is untagged, to on the WLC management and ap-manager, the vlan should be set to '0'.... this means that there will be no tagging.... not vlan '0'. What you did wrong here is on the switch, native vlan is 1 unless specified different. Also native vlan is not tagged unless you specify that all vlans will be tagged. So when you configured the wlc management interface to vlan 1, it is looking for a vlan tag of 1 in which you get the error you were seeing.
I never liked connecting the ap to the wlc.... connect it to a switch and be done with that issues.
You should be able to ping, check again the subnet mask and the gateway configured on the wlc management and ap-manager interface. It is normal behavior not to be able to ping any dynamic interfaces on the wlc.
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...