Integrate Wireless LAN Controller with Windows IAS

I would like to have internal users authenticate to Wireless LAN Controller Module using Windows IAS server. What option are there for me to present to users? Do they get a separate domain username/password box? Can it pass thru their existing domain login credentials if they already logged into Windows domain? Does any additional client/laptop software need to be installed?

What you should do is configure PEAP and use the IAS so users can authenticate with their AD credentials.
This should help you:
http://www.cisco.com/en/US/products/ps6366/products_configuration_example09186a0080921f67.shtml

Similar Messages

  • User names from Wireless LAN Controller

    Hi all
    I'm trying to get a report out of a Cisco 4402 Wireless LAN controller, showing all the current clients on a particular WLAN profile, with their user name.
    The Monitor -> Clients screen shows me all the MAC addreses, and I can filter by WLAN Profile Name to home in on the clients I'm interested in.  When I click on a MAC address for more detail, I can see the correctly populated User Name on the Client Properties screen - so the WLC definitely knows all the detail I need...
    Ideally I want spreadheet with a list of usernames of currently connected users (or even better, users that have connected over a time period).  I can't see any way to export this data without doing it manually (and I have 270ish clients at any one time).
    I've tried at the command line, with a "show clients summary", which at least gives me a table I can copy and paste into a spreadsheet, but again the username detail is only displayed with a "show clients detail MACADDRESS" - and the MACADDRESS field won't take a wildcard.
    I've also tried examining the log files, and setting up SysLog to a syslog server - but I haven't observed user names in any of the logs I've seen.
    The WLC is on version 4.2.176.0 - and doing an upgrade isn't very convenient at present - although I might consider taking the pain if a later release provides the funcationaility I need.
    Does anyone have any ideas on this one?
    Thanks!

    Dear Scott,
           I have some points to get clarified for step by step approach that has to be carried out during our downtime, or which is best option for this migration.
    Is that the WLC running different code will be able to join Mobility Group.  i.e. irrespective of Model and Code ?
    1. Do i have to create a mobility group and include the existing WLC and new 3 numbers of WLC , thus when i remove the Existing WLC from the Group the Ap will try to get assosiated with other WLC in the group.
    2. In WCS changing the Access point template configuring primary, secondary , tertiary Wireless LAN controller with New wireless LAN controller, during the down time this activity will be performed.
    Which method or way to proceed during the downtime. Looking for your expert view.
    Thanks .... Arun

  • Software Version Upgrade for Cisco 4402 Wireless Lan Controller

    Hi,
    We have Cisco 4402 Wireless Lan Controller with Software Version 3.2.171.6 and we want to upgrade it to latest version.
    So can anyone please let me know the latest version to upgrade the WLC?
    Also since WLC is running on very lower version is it possible to upgrade to the latest version directly or we have to move it step by step to upgrade this to latest version?
    Thanks

    Take a look at the compatibility matrix below:
    http://www.cisco.com/en/US/docs/wireless/controller/5500/tech_notes/Wireless_Software_Compatibility_Matrix.html
    7.0.235 is the latest that you can go to:
    http://www.cisco.com/en/US/docs/wireless/controller/release/notes/crn7_0_235_0.html
    The release notes outline the upgrade process.
    "Upgrade to 4.0.206.0 or later 4.0 release, then upgrade to 4.2.176.0, before upgrading to 7.0.235.0."

  • Can cisco CAP2702i connect to Cisco3850 switch with wireless LAN controller license via another switch ?

    If i connect cisco AP - CAP2702i to another switch, and use trunk port between Cisco3850 and the other switch , can the AP able to register with Cisco3850 with wireless LAN controller  ?   or the AP has to directly connect to Cisco3850 in order to register?

    The AP and 3850 wireless management are in same Vlan( vlan202). The AP is new unit and did not join MC before. 
    What i did on 3850 :
    input command - wireless management interface vlan 202
                              - ap cdp
                              - wireless mobility controller
    Is there any config i miss out on 3850 and any config need to be set on AP ?
    From Ap console output show me "could not discover WLC using dhcp ip". Is it due to AP dont have IP address? If AP register with WLC through layer 2 , i believe there is no related with IP.Correct me if i'm wrong.
    Due to the 3850 is not a POE, the AP unable directly connect to 3850  . I guess have to use power adapter to power on the AP.

  • Cisco Wireless Control System need wireless Lan Controller ?

    Cisco Wireless Control System need wireless Lan Controller , for Rogue detection

    Hi Joao,
    The WCS is used in conjuntion with the WLC (Wireless Lan Controller) for Rogue Detection. It is not a must for this function but more of an add-on :)
    The Cisco WCS is an optional network component that works in conjunction with Cisco Aironet Lightweight Access Points, Cisco wireless LAN controllers and the Cisco Wireless Location Appliance.
    From this doc;
    http://www.cisco.com/en/US/products/ps6305/index.html
    Overview of WCS
    The Cisco Wireless Control System (WCS) is a Cisco Unified Wireless Network Solution management tool that adds to the capabilities of the web user interface and command line interface (CLI), moving from individual controllers to a network of controllers. WCS includes the same configuration, performance monitoring, security, fault management, and accounting options used at the controller level and adds a graphical view of multiple controllers and managed access points.
    WCS runs on Windows 2003 and Red Hat Enterprise Linux ES 4.0 and AS 4.0 servers. On both Windows and Linux, WCS can run as a normal application or as a service, which runs continuously and resumes running after a reboot.
    The WCS user interface enables operators to control all permitted Cisco Unified Wireless Network Solution configuration, monitoring, and control functions through Internet Explorer 6.0 or later. Operator permissions are defined by the administrator using the WCS user interface Administration menu, which enables the administrator to manage user accounts and schedule periodic maintenance tasks.
    WCS simplifies controller configuration and monitoring while reducing data entry errors with the Cisco Unified Wireless Network Controller autodiscovery algorithm. WCS uses the industry-standard SNMP protocol to communicate with the controllers.
    From this good doc;
    http://www.cisco.com/en/US/products/ps6305/products_configuration_guide_chapter09186a00806b7270.html#wp1131195
    Detect and Locate Rogue Access Points
    From this WCS doc;
    http://www.cisco.com/en/US/tech/tk722/tk809/technologies_tech_note09186a00806f070a.shtml#new5
    Rogue Detection under Unified Wireless Networks
    http://www.cisco.com/en/US/tech/tk722/tk809/technologies_white_paper09186a0080722d8c.shtml
    Hope this helps!
    Rob

  • Getting existing wireless solution working with Windows 7 client

    A bit new to this so need some help
    I have been asked to do some innovation around an existing operational wireless solution.
    Setup is;
    1. Wireless client - running Juniper Odyssey client. This authenticates user on logon to Windows using username / SecurID token / pin. Configuration via WAP / TKIP
    2. Cisco Aironet Wireless Access Point
    3. Cisco 4402 Wireless LAN controller
    4. Cisco ACS v4.1 - configured as RADIUS server with connection to external RSA Authentication Manager 6.1
    As part of a transformation programme I have been asked to investigate whether this existing wireless infrsatructure will work with Windows 7 as the client operating system. Also to look whether the wireless functions in Windows 7 will allow the Odyssey client to be removed.
    I am unsure what client if any I need to install on the Windows 7 client in order to try and get this working. Do I need the VPN client from Cisco, the RSA EAP client or will Win 7 allow me to do this.
    Any help appreciated.

    I am still struggling with this concept of suplicants
    I have tried to set this up with the wireless capabilities in Windows 7 to no avail. I see that Windows 7 only supports certin EAP types - how can I find out what my EAP type is on the ACS server?

  • Is it possible run a Wireless LAN controller without a WCS?

    is it possible run a Wireless LAN controller without a WCS?
    How Can I configure the Wireless Lan controller?
    Thanks

    Hi Alfred,
    The WLC can be completly configured and operated without the WCS. The WCS is a nice addition for the management especially when running multiple WLC's but is not required.
    Info on WLC (with Video);
    http://www.cisco.com/en/US/products/ps6366/index.html
    Info on the WCS;
    http://www.cisco.com/en/US/products/ps6305/index.html
    Hope this helps!
    Rob

  • How to replace the certificate of Cisco 2106 wireless LAN controller for CAPWAP ?

    I have interested in CAPWAP feature and I download the open capwap project to make Access Controller (AC) and Wireless Terminal Point (WTP). I had built the AC which used PC and WTP which used Atheros AP. The CAPWAP feature work well when I enabled the CAPWAP that used my own AC  and WTP. When I got the Cisco 2106 wireless LAN controller (Cisco WLC), I configured the Cisco WLC to instead my own AC but I got the authorize fail in Cisco WLC side. It seem the Cisco WLC could not recognize the CAPWAP message which sent form my own WTP. I think this issue just need to synchronize the certificate between Cisco WLC and WTP.So I need to replace the Cisco WLC's certificate manually. Does anyone know how to replace the certificate manually with Cisco WLC ?
    Best Regards,
    Alan

    Unfortunately this Support Community is for Cisco Small Business & Small Business Pro product offerings.  The WLC2106 is a traditional Cisco product.  You can find this type of support on the Cisco NetPro Forum for all traditional Cisco products.
    Best Regards,
    Glenn

  • Cisco Wireless LAN Controller Always disconnect

    Dear All,
    Please help to assist my issue.I used Cisco Wireless LAN Controller model: 5508 with version 7.0.98.0 and I got issue with connection always disconnect ping always loss or some time client can't get DHCP from Controller. 
    - I configure as Internal DHCP Server with 1 SSID.
    http://www.cisco.com/c/en/us/support/docs/wireless/4400-series-wireless-lan-controllers/110865-dhcp-wlc.html
    - DHCP least is not full and I also try to clear-lease all but still not work.

    1. Config dhcp proxy enable
    2. In case of internal Dhcp, try debug for clients
     using,
    debug client <MAC ADDRESS OF CLIENT>

  • Wireless Lan Controller Issue

    Hi All,
    We have a Wireless Lan Controller 4402 with software version 4.0.155.5. On Friday we experience a problem where our clients wouldn't get redirected to the internal webpage for authentication. It would just come up with page not found. We know the page was working fine becasue we could manually type in the
    https://1.1.1.1/login.html and the
    page would come up and you could login successfully. The users who were already connected to the controller were not affected and continued to operate. We have 2 other WLC's at the same software revision and they were not affected so I don't think it has anything to to with software level. Its like the webserver in the wlc failed to work. We failed over the AP's to the 3rd WLC and rebooted WLC1. After the WLC1 restarted we failed one of the previous non-working AP's back to it and it works again.
    I know "now" there is debug commands to run at the time when the WLC wasn't working, but unfortunately I didn't know at the time. The WLC is running again fine and I was wondering if anybody has seen this issue before.
    Any ideas on a fix or reason would be greatly appreciated.
    Thanks,

    We are running WiSM 4.1.185.0 and we just had the similar problem with one controller. The other three controllers were fine when it happened. The exactly issue was the nslookup failed(timed out) from the client, so the web login page won't show when people lunch the browser. A reboot of the controller fixed the problem. We have been running Cisco LWAPP for more than a year (from 4.0.155.5 to 4.1.185.0) and it is the first time we see this problem. TAC is still investigating the cause.
    Zhenning

  • Wireless LAN Controller not broadcasting network to Access points

    Good Day Team,
    I am working with a 2100 series WLC controller and 1100 series access point.
    I noticed that the wireless lan controller is working. Also the access point is working.
    The issue is that there is no internet connection on the access point.
    What could be the error?
    Kindly advice

    Try do diagnose your problem following this steps:
    1) Connect to the wireless network
    2) Check your IP address with "ifconfig"
    3) Check if your gateway is set correctly with "route -n"
    4) Try to ping your gateway. Is it working?
    5) Try to ping an internet IP like google: "ping 74.125.234.115"
    6) Try to resolve names with "nslookup www.google.com" for example.
    7) Try to traceroute to an IP or name on internet. Check the result to see the last hop you reached.
    8) If you passed all those tests, try this: "telnet www.google.com 80"
    If everything works, but not the test #8, your problem could be related to some proxy configuration.

  • AIR-CAP3501I access point not joining the Cisco 2100 Wireless Lan controller.

    Hello All,
    I am installing a new LAP (AIR-CAP3501I ) through the wireless lan controller (AIR-WLC2112-K9) with software version 7.0. I have an external ADSL modem which will act as the DHCP server for the wireless clients and the LAP.
    Please find my network setup as below:
    The ISP ADSL modem , WLC and LAP are connected to a unmanaged POE switch. The LAP gets its power through the POE switch. When i connect the LAP and the WLC to the switch along with the ADSL modem, the LAPs are getting the ip address from the ADSL modem, however they are not joining the WLC for further process.
    ADSL Modem ip address: 192.168.1.254
    Management ip address on the LAP: 192.168.1.1 ( Assigned to port 1, untagged Vlan).
    Ap Manager ip address: 192.168.1.1 ( Assigned to the same port i.e port1, Untagged Vlan).
    The LAP is getting an IP address from the ADSL modem in the range of the DHCP scope.
    I will paste the logs very soon.
    Please let me know if i am doing anything wrong oe what will be the issue.
    Thanks in advance,
    Mohammed Ameen

    Hello All,
    Please find the logs for  "debug capwap event" from the WLC below:
    *spamReceiveTask: Sep 26 19:44:59.196: e8:04:62:0a:3f:10 Join Version: = 117465600
    *spamReceiveTask: Sep 26 19:44:59.197: e8:04:62:0a:3f:10 Join resp: CAPWAP Maximum Msg element len = 92
    *spamReceiveTask: Sep 26 19:44:59.197: e8:04:62:0a:3f:10 Join Response sent to 192.168.1.156:45510
    *spamReceiveTask: Sep 26 19:44:59.197: e8:04:62:0a:3f:10 CAPWAP State: Join
    *spamReceiveTask: Sep 26 19:44:59.197: e8:04:62:0a:3f:10 capwap_ac_platform.c:1216 - Operation State 0 ===> 4
    *apfReceiveTask: Sep 26 19:44:59.198: e8:04:62:0a:3f:10 Register LWAPP event for AP e8:04:62:0a:3f:10 slot 0
    *spamReceiveTask: Sep 26 19:44:59.341: e8:04:62:0a:d1:20 DTLS connection not found, creating new connection for 192:168:1:158 (45644) 192:168:1:2 (5246)
    *spamReceiveTask: Sep 26 19:45:00.119: e8:04:62:0a:d1:20 DTLS Session established server (192.168.1.2:5246), client (192.168.1.158:45644)
    *spamReceiveTask: Sep 26 19:45:00.119: e8:04:62:0a:d1:20 Starting wait join timer for AP: 192.168.1.158:45644
    *spamReceiveTask: Sep 26 19:45:00.121: e8:04:62:0a:d1:20 Join Request from 192.168.1.158:45644
    *spamReceiveTask: Sep 26 19:45:00.123: e8:04:62:0a:d1:20 Join Version: = 117465600
    *spamReceiveTask: Sep 26 19:45:00.123: e8:04:62:0a:d1:20 Join resp: CAPWAP Maximum Msg element len = 92
    *spamReceiveTask: Sep 26 19:45:00.124: e8:04:62:0a:d1:20 Join Response sent to 192.168.1.158:45644
    *spamReceiveTask: Sep 26 19:45:00.124: e8:04:62:0a:d1:20 CAPWAP State: Join
    *spamReceiveTask: Sep 26 19:45:00.124: e8:04:62:0a:d1:20 capwap_ac_platform.c:1216 - Operation State 0 ===> 4
    *apfReceiveTask: Sep 26 19:45:00.125: e8:04:62:0a:d1:20 Register LWAPP event for AP e8:04:62:0a:d1:20 slot 0
    *spamReceiveTask: Sep 26 19:45:00.273: e8:04:62:0a:d1:20 Configuration Status from 192.168.1.158:45644
    *spamReceiveTask: Sep 26 19:45:00.273: e8:04:62:0a:d1:20 CAPWAP State: Configure
    *spamReceiveTask: Sep 26 19:45:00.273: Invalid channel 1 spacified for the AP APf866.f2ab.24b6, slotId = 0
    *spamReceiveTask: Sep 26 19:45:00.274: e8:04:62:0a:d1:20 Updating IP info for AP e8:04:62:0a:d1:20 -- static 0, 192.168.1.158/255.255.255.0, gtw 192.168.1.254
    *spamReceiveTask: Sep 26 19:45:00.274: e8:04:62:0a:d1:20 Updating IP 192.168.1.158 ===> 192.168.1.158 for AP e8:04:62:0a:d1:20
    *spamReceiveTask: Sep 26 19:45:00.274: e8:04:62:0a:d1:20 Setting MTU to 1485
    *spamReceiveTask: Sep 26 19:45:00.274: e8:04:62:0a:d1:20 Finding DTLS connection to delete for AP (192:168:1:158/45644)
    *spamReceiveTask: Sep 26 19:45:00.274: e8:04:62:0a:d1:20 Disconnecting DTLS Capwap-Ctrl session 0xa06d6a4 for AP (192:168:1:158/45644)
    *spamReceiveTask: Sep 26 19:45:00.274: e8:04:62:0a:d1:20 CAPWAP State: Dtls tear down
    *spamReceiveTask: Sep 26 19:45:00.277: spamProcessGlobalPathMtuUpdate: Changing Global LRAD MTU to 576
    *spamReceiveTask: Sep 26 19:45:00.277: e8:04:62:0a:d1:20 DTLS connection closed event receivedserver (192:168:1:2/5246) client 192:168:1:158/45644).
    The Acess point joins the Controller for 2-3 seconds and then unjoins again. I am not sure what i am doing wrong here. The access points are getting the IPs from the ADSL modem through the switch, then it talks to the WLC, however it does not join the controller for further process.
    Note:
    The Managemnet interface and the AP manager interface are assigned to the same port 1 with unassigned Vlan as mention above.

  • Ise 1.1.1 missing Wireless LAN Controller (WLC) in Auth Profile

    Anyone else not seeing the Wireless LAN Controller tick box in Authorization Profile?
    Clean install of 1.1.1. with ISE Version 1.1.1.268—Cumulative Patch 1 applied
    EVAL license
    All the documentation says it should still be there in 1.1.1 unless im missing a trick?

    If you are referring to the ACL for the wireless lan controller that has change to the "Airespace ACL Name".
    This looks like a documentation bug.
    Tarik Admani
    *Please rate helpful posts*

  • Password Recovery for Wireless Lan controller

    Hi, I am new to Wireless Lan Controller.
    I just wanted to reset the password for the Controller. Can anybody help me with this. link/procedure anything will be appreciated.
    Thanks & Regards,
    Jvalin

    I think they mean that they can not type "reset system" since they can't log in in the first place.
    The key point to be made is that you need to restart the controller. So power it off if you can't login. Then console in to the controller and type "Recover-Config" as the username. This will default the configuration and allow you to start over with a new username/password.
    There is no other password "recovery".

  • Wireless lan Controller 4402 / ping dynamic interface failed

    hi,
    i've a problem with a Wireless Lan Controller 4402.
    When i configure the dynamic interface on the my network , with wired lan
    i don't reach (i use the ping command) the ip address of the WLC.
    In my case (wired):
    On my pc i've a ip 10.1.78.1 255.255.0.0 and dgw 10.1.1.1 (vlan721)
    The lan WLC have a ip of management 10.12.2.4 /24 (vlan799) [dgw 10.12.2.1]
    dynamic vlan 792 ip add 10.12.78.100 / 22 (vlan792) [dgw 10.12.68.1]
    i ping these interfaces (10.12.2.4 and 10.12.78.100) and the ping is ok.
    When i create a dynamic interface vlan 721 starting the problem:
    dynamic vlan 791 ip address 10.1.1.240 / 16 (vlan721)
    After this ......the ping on 10.12.2.4 and 10.12.78.100 don't respond very well
    and i lose the 80-90% of the ping packages.
    through the wi-fi instead I do not have problems.
    the problem exist only via wired (cable).
    Can you help me?
    Thanks
    FCostalunga

    Hello,
    Pinging the dynamic interface is officially not supported. The reason why is because the controller places a very low priority on ICMP traffic. Typically, you will not have an issue with doing so on your wireless network because this interface is basically a gateway for the client. However, from the wired network - the only interface designed to respond to pings 100% of the time is the management interface. Hope this helps!
    -Mark

Maybe you are looking for