Heads Up :
The post you are writing will appear in a public forum. Please ensure all content is appropriate for public consumption. Review the employee guidelines for the community here.
I have Cisco LAP1522 configured as a Root Mesh AP - it needs to support multiple vlans across the mesh. The G0 port is configured for trunk with VLAN 310 as native and VLAN 590 added as an allowed vlan.The AP is directly connect to a Cisco 3750G and...
Vlan pooling, recovery file options, AP code preload - all great features until the very basic operations of a WLAN controller stop being functional. Has anyone else encountered this? We are also having issues communicating with anchor controllers ...
I have a few APs that will not complete the code upgrade process after the controller was taken to 5.2.193.0 When watching the debugs, the AP starts the image data process, reaches the data transfer done point and then the AP heartbeat expires. The ...
Has a release date been given for the new 4.2 versions of the Cisco Lightweight software for the controllers and WCS that was reported in the Webcast from yesterday?
I am really tired of this - Cisco upgrades their software products and breaks half of the features in the process. Please, somebody tell me how/where to properly configure FTP and HTTP as an option for software distribution in Prime 2.1. I see wher...
Yep, tried messing with that too, all different native vlan settings on both the trunk port config on the switch and the native vlan on the MAP. Same result. I'm wondering if this would work using a 1552 as the root AP....
Yeah, I thought of that too. Cable tested with Fluke meter passed with flying colors. LIke I said, configured as an access point, AP works great - configure port as trunk and the link goes belly up.
Yeah, I've tried that - the second I do, all communication to the AP ceases. The port remains connected, a "sh int trunk" indicates the trunk is active but the port doesn't even report a MAC to the switch.
