Ditto that.
Lee H. Badman
Wireless/Network Engineer, ITS
Adjunct Instructor, iSchool
Syracuse University
315.443.3003
From: The EDUCAUSE Wireless Issues Constituent Group Listserv
[WIRELESS-LAN@LISTSERV.EDUCAUSE.EDU] on behalf of Jeffrey Sessler
[j...@scrippsco
As Lee mentions, the communication between the AP and the controller is via a
standard access port. There should be no need to have trunking or and other
configuration on the port for the AP. Even if the AP has multiple SSIDs and
VLANs, all of that traffic is encapsulated within CAPWAP.
Every
Hi Shayne,
I would agree with Mike King. I would call your local rep or Cisco Team to
resolve this issue quickly. Thanks for sharing just in case we run into a
similar issue.
Thanks,
Steve
Stephen G. Lotho | Roosevelt University | Director, Network Services |
312-341-6996 | 430 S. Michiga
I would suggest further reducing switch concerns out by fixing a test port or
two to "switchport mode access" and switchport access vlan " (whatever
appropriate) for a couple of APs that are acting up, along with making sure
your switch uplinks are clearly set up with proper trunking and no
Lee,
I've read multiple documents and all say different things on setup. We
have an internal registration system that we register each AP's mac
address and it's updated (yes we're still using VMPS) in the vmps.cfg
file. So currently we have each port setup like this:
interface GigabitEthernet0
