2100 Wireless LAN Controllers

Hi,
In the WLC 2112, I can connect Access Points in the available port.
For example:
WLC Port 1 --> Connected to Switch (802.1Q)
WLC Port 5 --> AP vlan 50 (access mode)
WLC Port 6 --> AP vlan 50 (access mode)
WLC Port 7 --> AP vlan 50 (access mode)
Thanks

Hi ,
Its works but not supported by TAC and not recommended as well.. please refer the doc authered by lee johnson..
https://supportforums.cisco.com/docs/DOC-11760
Lemme know if this answered ur question and please dont forget to rate the usefull posts!!
Regards
Surendra

Similar Messages

  • Voice over IP Roaming problems between 2 Wireless Lan Controllers.

    Hello,
    we have problems with Voice over IP roaming between 2 Wireless Lan Controllers, this problem is not always happening. I have attached the detailed configuration. We are using LWAPP 1242 & WLC 2106 Controllers.
    The phones they are using are Siemens Enterprise optiPoint WL2.
    Is there maybe something wrong with the configuration our can I try some different settings?
    Regards,
    Jordy Broekhuizen

    When a wireless client associates and authenticates to a WLC, it places an entry for that client in its client database. This entry includes the MAC and IP addresses of the client, security context and associations, quality of service (QoS) contexts, the WLAN, and the associated LAP. When a client roams to another LAP associated to the same WLC, it just updates the client database with the new LAP information so that the data can be forwarded appropriately to the client. When a client roams to a LAP associated with a different WLC, either in same or different subnets, it sends the information in the client database to the new WLC. This helps client to retain its IP address across roams and maintain uninterrupted TCP sessions. For more information on roaming in the WLC environment.
    For the further description following URL for the WLC may help you
    http://www.cisco.com/en/US/docs/wireless/controller/5.1/configuration/guide/c51ovrv.html

  • Memory on Wireless Lan Controllers

    Does anyone know anything about the wireless lan controllers regarding flash memory?
    I have found a command:
    show memory statistics
    It gives you the total DRAM in the device.
    I'm looking for the size of the FLASH memory device in the WLC controller.

    Nevermind....
    show sysinfo gives me the output desired.

  • 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.

  • Need to synch NTP on 2100 and 4400 Wireless LAN Controllers

    I have 5 WLC's (3-2100, 2-4400) and need to synch the NTP server ip addresses on them.  I know how to do this but have a question.  Using the gui, once I apply the change to the NTP ip address and save the changes, will the WLCs need to be rebooted for them to complete synchronization?

    No, you don't have to reboot the controllers.  They should sync right up.

  • 2100 wireless LAN controller intermittant DHCP issue does not respond to clients

    Hi everyone,
    I have been struggling with a difficult problem for some time now:
    The cisco 2100 wlan controller I have is configured with a dhcp scope in the same ip address range as its WLAN. The configuration works and on a good day I have up to 200 clients connecting with out issue. In the web interface they display as associated and authenticated
    On a bad day I find I will begin seeing about 50-80% of all new devices that attempt to join the WLAN show up as associated but not authenticated. These clients end up self assigning themselves a 169.254.0.0/16 (APIPA) address
    When my controller / WLAN enters into this state: if clients leave the WLAN they typically fail to get back on and successfully authenticate. By the end of a day around 80-90% of all devices are essentially without Internet access due to this issue.
    Rebooting the controller and or APs typically makes no difference or makes things worse – although sometimes it appears to resolve the issue. The same holds for disabling the entire wlan for about 10 minutes and then re enabling it.
    Im using 1130 cisco aironet APs with the controller. I have checked extensively for interference and congestion – I think I have congestion – some APs typically host 40 to 90 devices. However as mentioned on a good day the wlan will host 200 devices all day without any issue and some APs will host 50 to 70 devices without major issue.
    I can provide more specifics if anyone should need – eg firmware, IP addresses, exact model numbers etc.
    Please let me know if anyone has seen something like this before ?
    I believe the 2100 is rated to handle up to 350 devices and its recommended not to load a 1130 AP with more than 25 devices ??
    Regards
    Matthew

    Hi Amijad, Hi George:
    Thank you both for your time in considering my situation.
    I will think about implementing an independant DHCP server; im really wondering if the equipment is just overloaded
    - What software versoin the WLC uses?
    Product Version.................................. 6.0.199.4
    RTOS Version..................................... 6.0.199.4
    Bootloader Version............................... 4.0.191.0
    Emergency Image Version.......................... 6.0.199.4
    PID: AIR-WLC2106-K9, VID: V05
    - What ports of the WLC are connected to the neighbor swtich? one or more?
    2 ports connect to the neighbor switch on separate vlans
    - port 1 is vlan 0 and hosts the management and ap-management IPs for the wlan controller
    - port 2 is vlan 1 and hosts the wlan
    - the controller has one dhcp scope defined on port 2 for the WLAN
    - What is the security of your WLAN?
    WPA+WPA2
    AES
    PSK
    - Do you have "DHCP required" enabled on the WLAN?
    yes DHCP required is enabled in the WLAN
    please let me know if you have any additional advice.
    regards
    Matthew

  • Wireless LAN Controllers

    Hello --
    Do I need Cisco switches to use the controllers? Also, with multiple sites, do I need one controller at each site, then can I use WCS to manage them from a central location?
    Thanks,
    Ohamien

    Ohamien,
    You do not "need" to use Cisco switches to connect to the controllers, but it is always recommended =). As for remote sites, it would depend on how many AP's you would need per site. If you need less than 5 you could do HREAP with local switching, but if you needed more than that you would need to get a controller for that site, and then you could use WCS to manage all the controllers.

  • How to change RTS Threshold in Wireless LAN Controllers

    I've read some opinions that lowering the RTS threshold can help in some noisy wireless environments. I have found how this can be done on standalone APs but cant seem to implement the change on a WLC 2112. Does anyone know if this is possible and how to do it. Thanks in advance. 

    According to Cisco this feature does not exist in controller-based environments. This is what I get when I try to configure the RTS setting from the CLI:
    (Cisco Controller) config>slot 1 rts threshold 1024
    enable rts/cts only available for Mesh APs.
    I have submitted a feature request so we'll see what happens. Thanks for reading and please let me know if you have any pertinent information.

  • Virtual Wireless LAN Controllers

    Hi Guys,
    Are all APs supported by Physical WLC also supported by the Virtual WLC? or they support a selective few?
    Thanks in Advance
    Chandimal

    Hi Chandimal,
    Adding to Leo, vWLC only support FlexConnect mode AP.
    Here is the WLC compatibility matrix where you can find which AP model support under which version of WLC code.
    http://www.cisco.com/c/en/us/td/docs/wireless/compatibility/matrix/compatibility-matrix.html
    here is a vWLC deployment guide which may help you as well.
    http://www.cisco.com/c/en/us/support/docs/wireless/virtual-wireless-controller/113677-virtual-wlan-dg-00.html
    HTH
    Rasika
    **** Pls rate all useful responses ****

  • 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

  • Inline Posture between Cisco ISE and Wireless LAN Controller

    Hi,
    I was looking into Cisco ISE solution for deploying NAC.
    I have a question about the network topology.
    In  the user guide documents of cisco ISE, it is written that for Wireless  LAN Controllers (WLC) and VPN devices, an additional server, Inline Posture, is needed.
    However, in the following integration document, there is not an inline posture between WLC and Cisco ISE server.
    https://supportforums.cisco.com/docs/DOC-18121
    I  want to know if Inline Posture is a requirement, if not a  requirement, what are the benefits of having it between Cisco ISE Server  and WLC.
    Thanks & Regards
    Sinan

    Hello,
    Please go through below mentioned links which might be helpful for you.
    http://www.cisco.com/en/US/docs/security/ise/1.2/user_guide/ise_ipep_deploy.html
    http://www.cisco.com/en/US/docs/security/ise/1.2/installation_guide/ise_deploy.html
    Best Regards,

  • Best Practice for DHCP when Anchoring to a Guest Wireless LAN Controller

    Hi all,
    I'm interested in the communities opinion in relation to DHCP provisioning when using auto-anchor/guest tunneling.
    As far as I can tell, one cannot use the internal DHCP on the anchor controller when using auto-anchor due to incompatibility between the auto-anchor feature and DHCP Option 82.
    The scenario is as follows:
    Guest controller is the anchor which provides Internet access to guests.
    There is a foreign controller which is configured to anchor to the guest controller.
    The internal DHCP server is configured on the guest anchor controller, therefore DHCP proxy must be enabled for DHCP to work.
    DHCP proxy enables Option 82.
    The guidlines for guest tunneling state that DHCP Option 82 isn't supported. (Ref: Deploying and Troubleshooting Cisco Wireless LAN Controllers - Ch14)
    So, the internal DHCP server requires DHCP proxy to be enabled; this in turn enables Option 82, which stops DHCP leases being made to clients connected to the foreign controller.
    Given that a guest WLC would normally be placed in a DMZ, the internal DHCP server may often be the only DHCP solution available.
    I look forward to hearing your opinions.
    Thanks
    Rhodri Jenkins

    There are a couple of options here if you need to get proxy disabled
    1) pinhole with an ACL that allows dhcp to pass your internal servers
    2) run dhcp on a switch, router, or firewall in the dmz
    3) if you are using a cab,e modem or dsl for the guest users, you can let that do the dhcp
    In general I've seen most of these in play, but I like option 2 myself
    Sent from Cisco Technical Support iPad App

  • 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>

  • Error when installing webauth certificate virtual wireless LAN controller

    Hi there
    I am having issues installing web auth certificate for our virtual wirelesss LAN controller. 
    I am issuing a certificate from our own PKI in following format
    device cert for WLC > Intermediate > our root cert. 
    I have followed the discussion here
    https://supportforums.cisco.com/discussion/10890871/generating-csr-wlc-5508
    and the document here 
    http://www.cisco.com/c/en/us/support/docs/wireless/4400-series-wireless-lan-controllers/109597-csr-chained-certificates-wlc-00.html#support
    However I am still getting the following errors 
    *sshpmLscTask: Jun 30 17:18:26.443: sshpmLscTask: LSC Task received a message 4 
    *TransferTask: Jun 30 17:18:28.785: Memory overcommit policy changed from 0 to 1
    *TransferTask: Jun 30 17:18:28.785: RESULT_STRING: FTP Webauth cert transfer starting.
    *TransferTask: Jun 30 17:18:28.785: RESULT_CODE:1
    FTP Webauth cert transfer starting.
    *TransferTask: Jun 30 17:18:33.154: ftp operation returns 0
    *TransferTask: Jun 30 17:18:33.154: RESULT_STRING: FTP receive complete... Installing Certificate.
    FTP receive complete... Installing Certificate.
    *TransferTask: Jun 30 17:18:33.154: RESULT_CODE:13
    *TransferTask: Jun 30 17:18:37.159: Adding cert (8217 bytes) with certificate key password.
    *TransferTask: Jun 30 17:18:37.169: sshpmCheckWebauthCert: Verification return code: 1
    *TransferTask: Jun 30 17:18:37.169: Verification result text: ok
    *TransferTask: Jun 30 17:18:37.171: sshpmAddWebauthCert: Extracting private key from webauth cert and using bundled pkcs12 password.
    *TransferTask: Jun 30 17:18:37.361: sshpmDecodePrivateKey: calling ssh_skb_decode()...
    *TransferTask: Jun 30 17:18:37.493: sshpmDecodePrivateKey: SshPrivateKeyPtr after skb_decode: 0x2aaaacb51628
    *TransferTask: Jun 30 17:18:37.493: sshpmAddWebauthCert: got private key; extracting certificate...
    *TransferTask: Jun 30 17:18:37.494: sshpmAddWebauthCert: extracted binary cert; doing x509 decode
    *TransferTask: Jun 30 17:18:37.494: sshpmAddWebauthCert: doing x509 decode for 1594 byte certificate...
    *TransferTask: Jun 30 17:18:37.494: sshpmAddWebauthCert: failed to validate certificate...
    *TransferTask: Jun 30 17:18:37.494: RESULT_STRING: Error installing certificate.
    *TransferTask: Jun 30 17:18:37.495: RESULT_CODE:12
    *TransferTask: Jun 30 17:18:37.495: Memory overcommit policy restored from 1 to 0
    Error installing certificate.
    Any help is much appreciated

    Similar issue:
    https://supportforums.cisco.com/discussion/11043836/wism-42112-and-web-auth-certificate

  • 3504 Wireless Lan Controller and WCS

    Hi Pals,
    I need to know if any version of Cisco WCS supports 3504 Wireless lan controllers. The latest 3.2.4 doesn't seem to have 3504 listed in its release notes.
    Any help would be highly appreciated.
    Cheers,
    Rajesh

    Hi SmalKeric,
    Thnx for the reply. But was wondering why ? Would appreciate you can point me to some links which describe this.
    Cheers,
    Rajesh

Maybe you are looking for