I am used to configured Aironet Series AP and find it very difficult when I tried to configure Controller and LWAPP-based AP. I hope that you may help me with my predicament.
What is the importance and functionality of a physical port number that we define when we create the interface name in the controller?
Management is tied port 1 and when I created a new interface for VLAN ID 90 and I still tie it to port 1 and yet my AP is connected to port 2. Shouldn't that the new interface VLAN ID 90 tie to port 2 instead of 1?
I am so confused about the definition of the physical port no in the controller? When I connect the AP to a switch that connects to port 1, the AP is not able to register with the Controller. Must the switchport connected to port 1 be configured as a trunk? If so, how can I configure the port 1 on the controller to be trunk? I find no options in the controller to do so.
The Cisco Wireless LAN Controller Module eliminates the need to individually configure, manage, and monitor each access point. In conjunction with Lightweight Access Point Protocol (LWAPP)-enabled Cisco Aironet access points and the Cisco Wireless Control System (WCS), the module minimizes deployment and operational costs, allowing businesses with limited IT staff to easily deploy and manage wireless networks across hundreds of remote sites.
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...