Wlc interface

I created an interface (from Controller > Interface) assign an ip address on /24 subnet. Tested and it works fine. Now here's the confusion.
I remove the routing for that subnet. I can't ping the ip address of the interface created above, but I can still connect to the ssid. Any idea why? What is the purpose of using this interface?

Interfaces on WLC are Layer-2 and you need external L3 device for routing.
it is like SVI on switch but no Layer3(however it does some L3 for out of band management using static route config on wlc). With atleast one configured tagged vlan on WLC to its connected switch physical interface should always be trunked.
every active ssid(layer-1) needs to have interface/vlan(layer-2) mapped to it, without that it is an switch port with no vlan(including native) attached to it, however WLC mandate to select interface for all wlan created(default is management).
you should be able to ping the WLC interface ip, if the w.less client(with ip) connected wlan has same interface mapped to it or other interface with inter-vlan/L3 access.
Purpose of management interface is to carry AP traffic(that includes all wlan traffic), wlans can also be mapped to management interface(should avoid for security reasons), Dynamic interfaces mapped to wlans uses that subnet/vlan to talk to wired infrastructure from WLC to its connected switch using dynamic interface mapped physical interface. there is no wlan's mapped vlan id between wireless client until ingress physical port of WLC via AP, it is only wlc that tags the packet before forwarding to its upstream infrastruture device.

Similar Messages

Multiple WLANs pointing to same WLC interface

I would like to have a guest Web auth based WLAN that points to an Interface that I also have configured for a separate 802.1X authentication that allows access to my private network. I should note that I already have web auth configured for Guest access that only allows Internet access via separate WALN/VLAN. This would allow me to setup access for a vendor that is on-site using the Lobby Ambassador .
Is this possible and what do I need to do? I have created the seperate WLAN with Web auth and pointed it to the same WLC interface that I use for the 802.1X and this does not seem to work.

This has been resolved. I found I had AP groups setup and had not added the WALN to the correct group.

Which WLC interface should be resolved from cisco-lwapp-controller.domain

Hi,
we use several 4402 wlc and want the aps connect to connect to them via dns discovery.
It would be fine if somebody could tell me to which ip address (in our dns database) I have to add an alias for cisco-lwapp-controller.<domain>.
Is it the management interface, the ap manager interface or one/all dynamic interface(s)?
Is there any hint concerning this in the documentation?
Best Regards,
Thorsten

You use the management interface of the WLC.
Here is a good link also if you have issues:
http://www.cisco.com/en/US/products/ps6366/products_tech_note09186a00808f8599.shtml#backinfo

5508 WLC Interface Groups

We have not configured or used interface groups in our wireless deployments, and I am just curious if there are any issues or caveats experienced with using these? We have a few instances where we have setup a /23 network for a specific wlan. I undertsand this increases broadcasts. Would interface groups be preferred over using a /23 or even maybe a /22 to accomodate addressing?

By default, the WLC will not forward broadcast. There are pro's an con's to interface groups... if your doing multicast, that can be an issue unless you specify an multicast vlan. I have used interface groups because customer standardize on /24, so I would combine a bunch of /24's to create an interface group. I have customers with /23 and /23 and others with no issues... but I look at it as on the wired side. You okay with /23 and or /22 on the wired side?
Thanks,
Scott
*****Help out other by using the rating system and marking answered questions as "Answered"*****

VLAN for WLC interface (ISE Policies Based on SSID)

I have ISE 1.1 and WLC 2504
I used this link http://www.cisco.com/en/US/products/ps11640/products_configuration_example09186a0080bed902.shtml
But I am confuse on the WLC configuration
If I have only one ESSID for corporate user(and many DATA vlan because each AD group is assosiated to one specific VLAN)
I have already created Management interface associated with management Vlan
Wich interface interface should I associate on the corparate WAN ( WLAN -->General --->Interface/interface group) ?
Should I create another interface ? wich Vlan ID should I associate to this interface
or should I use Management interface
Please advise

check the following links , they are very helpful:
http://www.cisco.com/en/US/products/ps6366/products_configuration_example09186a00808c9bd1.shtml
http://www.cisco.com/en/US/products/ps10315/products_configuration_example09186a0080bc8129.shtml
http://www.cisco.com/en/US/tech/tk722/tk809/technologies_configuration_example09186a008076317c.shtml
Please make sure to rate correct answers

Clarification regarding WLC 's interfaces

Hi Netpros,
I am about to deploy WLC and LWAPP solution. I have only done Autonomous set up in the past and so would appreciated some clarification regardig the below points:
1.- switch port connected to LWAPP access points must be an access port (not trunk) correct ?
2.- switch port connected to WLC 44+ must be a trunk (assuming I need to map SSID to different vlans) correct ?
3.- WLC 44+ port can only be connected to a gigabit port .. so I can't change its speed in order to connect it to a fastethernet port .. correct ?
4.- What exactly is Management interface, service port, AP manager ..etc so many names I am getting confused.
5.- What is layer 2 and layer 3 mode .. I am also confused here.
6.- If I want all my LWAPP access points on vlan 10 (for argument sake) .. which WLC's interface do I need to place on vlan 10 in order for the access points to register ? I want to have LWAPP and WLC on the same vlan but with so many inteface names I don't know which one I have to use (AP manager ? perhaps )
7.- If I want SSID 1 (vlan 11), SSID 2 (VLAN 22). How do I configure the WLC interfaces (which one do I need to use .. create ..?) so that clients using SSID 1 can communicate on its respective VLAN 11
8.- Microsoft IAS and PEAP .. do I need to set up every access point as radius client ? or do I only need to configure the WLC as radius client .. and if so which WLC interface's IP address do I need to use on the radius server (IAS)
I apologize for so many questions and really appreciate your feedback which - as always - I am sure will make things clear.
Cheers,

1.- switch port connected to LWAPP access points must be an access port (not trunk) correct ?
(A) Correct, Cisco recommends no more then 70 or so APs per VLAN. You can do more then 70 and in fact put all of your APs in the same VLAN. But if the controller ever goes dark it could take a bit longer for the APs to join.
2.- switch port connected to WLC 44+ must be a trunk (assuming I need to map SSID to different vlans) correct ?
(A) Yup yup. You can truck the switch or Echannel it and use LAG on the controller.
3.- WLC 44+ port can only be connected to a gigabit port .. so I can't change its speed in order to connect it to a fastethernet port .. correct ?
(A) Yup yup. again. GIG only. Wont connect otherwise.
4.- What exactly is Management interface, service port, AP manager ..etc so many names I am getting confused.
(A)
Manager is the IP address you will use to manage the controller. Its the way the controller see's the world.
AP Manger is used for the APs to phone home to. This interface is not pingable. Nothing special with this interface.
Service Port ... think about out of service management for the WLC. Suppose you lose network connection to the WLC manager interface. You can jack right into the service port. I have also put this on the network before so you can still access the WLC remotely.
5.- What is layer 2 and layer 3 mode .. I am also confused here.
(A)
Layer 2 --- Think about deploying your entire WLAN on one subet. So your APs and WLC are all in the same subnet.
Layer 3 -- This is used when you have your APs on other subnets ect..
You can actually console into the LWAPP ap during the join process. you will see the AP send a 255.255.255.255. This is a join attempt by the AP to find a controller on its subnet.
6.- If I want all my LWAPP access points on vlan 10 (for argument sake) .. which WLC's interface do I need to place on vlan 10 in order for the access points to register ? I want to have LWAPP and WLC on the same vlan but with so many inteface names I don't know which one I have to use (AP manager ? perhaps )
(A) The beauty of the WLC is you dont have to have the APs on the same VLAN as the controller, unless u are layer 2. The access layer teh APs are on just need to be routable to the AP interface.
7.- If I want SSID 1 (vlan 11), SSID 2 (VLAN 22). How do I configure the WLC interfaces (which one do I need to use .. create ..?) so that clients using SSID 1 can communicate on its respective VLAN 11
(A)
You map the SSID to VLAN under the WLANs tab. You Create the wired side info (VLANS) under the controller tab
8.- Microsoft IAS and PEAP .. do I need to set up every access point as radius client ? or do I only need to configure the WLC as radius client .. and if so which WLC interface's IP address do I need to use on the radius server (IAS)
(A) Advantage of the WLC, you use the WLC as the client to a Raduis server. The management address..
I apologize for so many questions and really appreciate your feedback which - as always - I am sure will make things clear.
Cheers,

WLC Virtual interface listening on ports 25 and 110

I'm securing my guest WLAN and have WLC ACL's in place and the network is segmented from everything else but I decided to run a port scan against the virtual WLC interface (1.1.1.1 for me) and ports 25 and 110 are listening. I connected to 25 and it connects but you can't do any SMTP commands.
Anyone know why these would be open and any concern?

It is always recommended to have the ACLs configured on the wired side of the network rather than the wireless side of the network.can you provide the ACL configuration so that we can understand the configuration and find the modification to be done in the same to rectify the issue.

Dynamic VLAN assignment with WLC and ACS for

Currently, using our autonomous APs and ACS, our users get separate VLANs per building based on their security level (students or staff). Basically, the student VLAN in one building is different from that of the student VLANs in other buildings on campus. Currently, we do this by filling the Tunnel-Private-Group-ID IETF RADIUS attribute with the VLAN name. This all works because each individual AP can map VLAN names to different VLANs like this:
dot11 vlan-name STUDENT vlan 2903
dot11 vlan-name FACSTAF vlan 2905
As we are working on our WiSM deployment, we see that the document below shows how to do the dynamic VLAN assignment on our WLAN controllers:
http://www.cisco.com/en/US/customer/products/sw/secursw/ps2086/products_configuration_example09186a00808c9bd1.shtml
However, we haven't figured out if it's possible to still provide our users with different VLANs for each building they're in.
With the instructions above, it looks like ACS uses a Cisco RADIUS Attribute to indicate the Air-Interface-Name, mapping an ACS/AD group to a single WLC interface which can only have one VLAN/subnet associated with it.
Does anybody know if what we're trying to accomplish is possible, or if we're really stuck with only one VLAN/subnet per mapped ACS group?

We only have the one WiSM for all of campus, so it's handling everything. This Cisco docs do indicate how to put differnet users in different Vlans, but we don't currently see a way to also put them in different subnets per building.
This being the case, any suggestions on how best to handle more than a Class C subnet's worth of users? Should we just subnet larger than Class C, or is there a more elegant way of handling this?

WLC and AAA - one SSID and more VLANs

hi,
i have an ACS 4.1, AP1242, WLC4404 and Catalyst 3750, and an Win2003 DHCP Server
Switch Interface Config:
interface Vlan10
ip address 10.70.170.1 255.255.255.0
ip helper-address 192.168.12.10
interface Vlan20
ip address 10.70.171.1 255.255.255.0
ip helper-address 192.168.12.10
at the WLC i have configured one SSID with
- Allow AAA Override
- Layer2 Sec: [WPA1,TKIP+WPA2,AES]
- ACS 4.1 AAA
- Key Management: 802.1x
one SSID mapped to the management interface. and 2 VLANS with different interfaces:
VLAN-ID1: 10
Interface-1:
IP Address 10.70.170.2
Netmask 255.255.255.0
Gateway 10.70.170.1
DHCP: 192.168.12.10
VLAN-ID2: 20
Interface-2:
IP Address 10.70.171.2
Netmask 255.255.255.0
Gateway 10.70.171.1
DHCP: 192.168.12.10
at the acs i have 2 users and two groups. Group1-User1 and Group2-User2 with the aaa attributes to change the vlan on login.
[006] Service-Type: Authenticate only
[064] Tunnel-Type: VLAN
[065] Tunnel-Medium-Type: 802
[081] Tunnel-Private-Group-ID: <VLAN-ID-1> or <VLAN-ID-2>
my problem is, that the user will authenticate successfully, and also the Vlan and Interface assignment is correct,
but the ip-address that the user will get is always the IP-Range from Interface2 (VLAN20). So when the USER2 authenticates, he get the VLAN2,
and the right interface and the right IP Adress and the communication is right.
but the USER1 gets the interface1 and VLAN10, but the IP from Interface2 (VLAN20).
what can it be?
thx

FYI - If you're using ACS v4.1, you can also achieve this using the Airespace Attributes, by specifying the WLC interface name in the appropriate section.

I can't join LAP to WLC 5508 in difference subnet

i can't join LAP to WLC in difference subnet now i create 2 interface [management / ap-manager]
management : 192.168.1.1 / 24
ap-manager : 192.168.1.2 / 24 vlan 10
ap-manager2 : 192.168.2.2 / 24 vlan 11
ap-manager3 : 192.168.3.2 / 24 vlan 12
connect with core switch 3 interface [access port vlan same wlc]
or how create wlc interface for join with LAP please advise me or send capture screen for me to create all interface
Thank you for best support.

I created a video actually how to configure option 43 on my site.
http://www.my80211.com/cisco-wlc-labs/2009/7/4/cisco-dhcp-option-43-configuration-nugget.html
So when you fire up an AP it goes through a few steps to find the controller.
1) It does a broadcast and if your APs are on the same VLAN as your apmangers/managment then she will connect
2) If it isnt on the sanme vlan it will attempt to reslove CISCO-LWAPP-CONTROLLER or CISCO-CAPWAP-CONTROLLER. This is where you would need to create an A-record in your DNS server and reslove it to your MANAGEMENT controller IP address
3) Also Option43. When your AP gets an IP address, you can add option 43 to the scope. Option 43 again tells the AP where to find the controller.
Now you can do a manual prime to these as well. Extend your managment vlan to a switch and have the APs join. Once they take the download and config they will know the controllers ip address. And then you can deploy them on different vlans and they will join ...
Does this make sense?

Using WLC in Small business

Hello,
Let me first start out by saying I am new to configuring WLC's.
Our small business (5-15 wireless devices + 15ish wired) is trying to use a hand-me-down WLC and AP for our office wifi.
We have a WLC2106 directly connected to a 1231G-A-K9 via the WLC's port 8 POE. I am aware Cisco does not recommend this method, but we do not have a configurable switch at our disposal. We do not need separate VLAN's therefore I have left everything untagged. The AP has a static IP setup to allow communication to the WLC since it did not pull one from the WLC. The AP is getting the correct network information and is showing up on the WLC monitoring page. I am able to connect to the new wireless network and able to ping between devices connected to the same AP. Now here is my question/issue. I cannot get communication from the WLC/AP to the rest of our network via an unconfigurable Netgear switch (FS605v3). After connecting an open switch port from the Netgear switch to port 4 on the WLC, I am lost. I tried giving port 4 on the WLC an address on the office network, but I receive an error stating "the IP information conflicts with another device". ANY help would be greatly appreciated.
Here is what I have setup on WLC
Virtual - 1.1.1.1
MNG IP-192.168.10.10
AP MNG Ip- 192.168.10.11
Subnet - /24
Gateway - 192.168.10.1
DHCP - 192.168.10.250
DNS - 192.168.10.250
Static Address on the AP's fa0-192.168.10.15
Attempted port 4 setup on WLC
VLAN identifier 0
IP- 192.168.10.25
Mask - /24
Gateway - 192.168.10.1
Port - 4
Our office network setup:
Subnet - /24
Gateway-192.168.10.1
DHCP - 192.168.10.250
DNS - 192.168.10.250

Plug one WLC interface (lets say Port 1) in to your netgear switch and configure the WLC as;
Management Interface - Port 1, 192.168.10.10, 255.255.255.0 GW=.1 VLAN=0, DHCP Server = 192.168.10.250
AP Manager Interface - 192.168.10.11, 255.255.255.0 GW=.1 VLAN=0
Virtual Interface 192.0.2.1 (or 1.1.1.1 will be fine, but it is a routable address these days)
Make sure these addresses aren't in use and are not part of your DHCP IP Address pools. Delete any other interfaces you have created during your play time with the WLC.
Plug the AP in to your netgear switch and configure it as;
192.168.10.12 /24
Configure the WLAN on your WLC to use the "Management" Interface
At this point, you should be in business
If not, Telnet/SSH to the WLC and grab a "show run" output... Post it on here and somebody will help.
Richard

WLC Guest Setup thru Palo Alto Firewall

We currently have a Guest wireless setup at my company, instead of using a anchor controller we have dual contorllers with each having one interface connecting out into our dmz and then going out. it's a pure L2 connection and exits out to the internet via a DMZ interface on our ASA. We recently purchased a PA-200 Palo Alto firewall to use for this Guest network, and configured everything exactly how it's all ready setup on our dmz switch and asa with the same ip addresses. When we connect the outside interfaces from the controller to a L2 switch that's connected to the Palo Alto firewall we can't get dhcp requests thru and have no connectivity, even if we set a static IP on our client we still have no connectivity and it won't redirect us. We use Web-Auth for our authenication with this network and I know once you get an IP address it will only allow dns to redirect to the virtual IP for authenication before it allows anything else but it is the exact same setup as we had before just with a different firewall so I'm stuck. Also if I plug directly into the switch via ethernet cable I can get an IP address and get out to the internet. Is there anyone who has experience with this type of setup, or might know what I need to allow on the firewall for it to work? I've attached a diagram of the basic topology we have setup.
Thanks

Hi Rod
You WLC interface and PA interface config look correct. I assume you have policies rules on the PA to permit traffic from your guest zone to the destination. You will also require a policy on the PA to permit traffic from the guest zone to the guest zone as the default route for the subnet is on the PA and any traffic to the IP is filtered by the policies.
I have my WLC doing DHCP for my guest subnet as your guest SSID/vlan is probably central switched on the WLC its the easiest way to do this. The PA has no DHCP helper function as far as I am aware and I've never tried passing DHCP requests through a PA via a centrally switched SSID. I assume 10.118.6.112 is the management IP of your controller? if its not try changing the IP to your controller management IP if your not getting DHCP
I'm not sure how your guest system works but I have an SSID which has a web-auth policy fowarding the guest auth to an authentication server with a webconsole which the passes a radius auth session back to the WLC.
Do you have any other SSID's configured to use that physical port on the WLC? Even if there HREAP and not using the interface.
Do you also have the web policy configured correctly on the SSID? I assume you want the browser to redirect to the guest web login page when they connect to the SSID. Are you using an external server for this or the WLC?

Wlc 5508 webauth subnet mask change issue

Recenly l changed the network subnet for a particular wlc interface and scope and also an upstream router and for some reason it would only allow me to use a /24 Host mask as my plan was to go to a /22 mask to allow for over 1000 hosts within this scope.
The Upstream Router which is a ( RV042 ) had the following original config :
     192.168.1.1
     255.255.255.0
I have noticed this device will not let me change the mask from a /24 to a /22 as you can only change from a pre-defined list of masks and you cannot manually add any either..
New Config
     10.10.0.10
     255.255.255.0
WLC 5508 Controller Interface
     Original Config
      192.168.1.25
     255.255.255.0
     192.168.1.1
     New Config
     10.10.0.25
     255.255.252.0
     Scope
     Range : 10.10.1.10 - 10.10.3.254
     Mask : 255.255.252.0
     Network : 10.0.0.0
     Router : 10.10.0.10
When l reconfigure to this addressing the wireless clients connect and get the new dhcp scope details but following this the webauth screen doesn't appear not allowing them to connect meaning there is no routing of traffic / internet access.
If l modify the above interface and scope masks back to a /24 - 255.255.255.0 the the wireless clients connect and webauth appears to prompt them to accept the terms and conditions and connect thus giving them internet access.
It looks like an issue with the mask ? The main reason l am trying to change the subnet addressing is because the standard /24 mask is not providing enough dhcp addresses and we have had times were the scope has been exhausted due to the public connecting and disconnecting as the lease perod of 2 hours holds onto the address before expiring meaning there is not enough available addresses for people to connect.
I would of thought that the upstream router ( RV042 ) even though it is only a /24 mask would still route the traffic coming from a WLC Controller interface with a /22 mask ?
Hopefully someone can suggest a solution ?
Thanks Simon

Hey Scott just getting back to this issue..   If for instance l can modify the wlc interface and Scope to have a /22 mask ( 1022 Hosts ) and my upstream Router ( Cisco RV042 ) can only provide a /24 or higher mask then does that mean l am still limited to a range of 254 hosts ( /24 Mask ) ? Would this mean l need to look into replacing my upstream Cisco RV042 VPN Router ?

WLC2504 - Dynamic interface problem

Hi,
I have problem with my WLC2504. My WLC is connected through two ports (1 and 2 of four) to my distro switch, where I have dot1q trunks configured. WLC is configured with Management interface (IP address 192.168.255.9/24), over which my LAPs are correctly joined. However, once I'm trying to add additional Dynamic WLC interface, which has VLAN TAG 10 and which I'd like to associate with my WLANS, my WLC stop responding through GUI and SSH, but pings on the management and dynamic interface IP addresses are sucesfull. Just as a note, dynamic AP management is not enabled on mentioned dynamic interface. In a case when I enable dynamic AP management on the dynamic interface (activated also on management interface), GUI and SSH work, but I can not associated WLAN to the dynamic interface, only to the management one
Thanks for soon answer
palo73

The management interface is the default interface for in-band management of the controller and connectivity to enterprise services such as AAA servers. The management interface is also used for communications between the controller and APs. The management Interface is the only consistently "pingable" in-band interface IP address on the controller. The management interface will act like an AP manager interface by default.
The dynamic interface with the “Dynamic AP Management” option enabled on it is used as the tunnel source for packets from the controller to the AP, and as the destination for CAPWAP packets from the AP to the controller. The dynamic interfaces for AP manager must have a unique IP address. Typically, this is configured on the same subnet as the management interface, but this is not necessarily a requirement. In the case of the Cisco 2500 Series Wireless Controller, a single dynamic AP manager can support any number of APs. However, as a best practice, it is suggested to have 4 separate dynamic AP manager interfaces and associate them to the 4 Gigabit interfaces. By default, the management interface acts like an AP-manager interface as well and it is associated to one Gigabit interface. As a result, if you are using the management interface, you need to create only 3 more dynamic AP manager interfaces and associate them to the remaining 3 Gigabit interfaces.
The virtual interface is used to support mobility management, DHCP relay, and embedded layer 3 security like guest web authentication and VPN termination. The virtual interface must be configured with an unassigned and unused gateway IP address. A typical virtual interface is 1.1.1.1. The virtual interface address is not pingable and should not exist in any routing table in your network.
Dynamic interfaces are created by users and are designed to be analogous to VLANs for wireless LAN client device. The Cisco 2500 Series Wireless Controller will support up to 16 dynamic interfaces. Dynamic interfaces must be configured on a unique IP network and VLAN. Each dynamic interface acts as a DHCP relay for wireless clients associated to wireless LANs (WLANs) mapped to the interface. A WLAN associates an SSID to an interface and is configured with security, QoS, radio policies, and other wireless network parameters. There can be up to 16 WLANs configured per controller.
Guidelines for Deploying the Cisco 2500 Wireless Controller
Ethernet ports on Cisco 2500 Series Wireless Controllers do not work as Switch ports (that is, 2 machines directly connected to these ports will not be able to communicate with each other). You should not connect servers like DHCP, TFTP etc. on these ports and expect Wireless Clients and APs to receive an IP address from this DHCP server.
Ethernet ports on the Cisco 2500 Series Wireless Controller should only be used to connect/uplink to an infrastructure network configured as a data interface (management interface and dynamic interfaces) or an AP-managers interface.
If multiple Ethernet ports on a Cisco 2500 Series Wireless Controller are uplinked to an infrastructure switch, you should make sure data interfaces (management or dynamic interfaces) or AP-managers interfaces are configured for these uplinked physical ports. Physical Ethernet ports which are used as an uplink to an infra switch should not be left un-configured. This may result in unexpected behaviors.
Multicast unicast is not a supported configuration on Cisco 2500 Series Wireless Controller. As a result, HREAP APs are not able to receive multicast traffic because HREAP APs only work with multicast unicast.
For more information you can refer to the link -
http://www.cisco.com/en/US/products/ps11630/products_tech_note09186a0080b8450c.shtml

WLC 4402 setup

I'm trying to create a testing wlan and here's my scenario. I could successfully test my wlan using just the basic setup and all worked out well. I could connect WLC on WCS and connected ap1232g on the available port and all ran smooth as planned just by playing safe in same subnet and without creating any vlans or using switches.
My problem started when I brought out my WLC box and connected on c2950 switch. The switch itself seemed to be fine and already configured with ports assigned to separate vlans. But no matter how I tried/reset, I noticed that neither WLC box nor the switch doesn't have link status light come up on the assigned port. Now, I'm stuck at that point that wlc won't even get connected to switch and have a feeling I'm not even supposed to be putting/using WLC box on c2950 or I need to configure those boxes other way around.
should it be like this?
wlc-interfaces (VLAN) ---trunk--> c2950 ---> network ---> APs
I will be waiting for your reply and please let me know if you need more info for the setup.
Thanks in advance.
Zwe

Hi Ankur,
I'm using a regular port with RJ45 from 2950 to my controller. I notieced there's a fiber connection on the switch but I have no gbic adapter at the moment. I think what you told me could be the problem. Because on my first set up, I used my wall jack which is a gig port and connected to wlc and it worked out fine though I did play around with a few settings on autonegotite and speed but didn't see any difference.
So, as you said, I must have at least a gig connection on the switch for my wlc port.
My another question is would it be possible to use the vlan we already created on our core switch and use them on WLC or I will have to create new vlans on the controller and trunk them back to other switches??
Thanks for your help.
Zwe

Wlc interface

Similar Messages

Maybe you are looking for