I agree with you but at the same time, it is quite common that the VLAN in which the LWAPs communicate with the WLC is kept separate from the VLANs associated with diverse SSIDs. In that case, kakados2000 would need not only to configure the switchport towards the WLC as a trunk port, but also the entire switched infrastructure between the LWAPs and the WLC would need to support multiple VLANs. It really depends on how the lightweight AP infrastructure is deployed here.
The WiSM 1/2 or WLC will always have mutltiple VLANs (Management, AP-Manager, Dynamic Interfaces). So you need to configure the switchport(s) and the WLC with 802.1q trunking. It would even be recommended if you bond these physical connections into an etherchannel/LAG.
As for your WAPs, if they are controller-based IOS then the WAPs should be configured as an ordinary access port. If you have autonomous WAPs then these have to be configured as 802.1q trunking.
We are pleased to announce availability of Beta software for 16.6.3.
16.6.3 will be the second rebuild on the 16.6 release train targeted
towards Catalyst 9500/9400/9300/3850/3650 switching platforms. We are
looking for early feedback from customers befor...
Introduction Featured Speakers Luis Espejel is the Telecommunications
Manager of IENova, an Oil & Gas company. Currently he works with Cisco
IOS® and Cisco IOS XE platforms, and NX to some extent. He has also
worked as a Senior Engineer with the Routing P...
In this session you can learn more about Layer 3 multicast and the best
practices to identify possible threats and take security measures. It
provides an overview of basic multicast, the best security practices for
use of this technology, and recommendati...