WLC 2106 redundancy uplinks / LAG

Hi to all,
We've a WLC2106 connected to a Distribution switch composed by a stack and 6x APs dislocated on the Access switches.
All the APs are in H-REAP mode so the WLANs are mapped to the WLC's management interface instead of a dynamic one.
How can I add redundancy on the connection from the WLC to the Distribution switch since the WLC2106 doesn't support LAG/Channel (implemented on all the WLC4400/5500 installed until yet) nor AP-Manager secondary interfaces???
Many thanks
Saluti
Omar

Hi Leolaohoo,
thnx but I want to been able to have a redundacy on network connections from the WLC to the Distribution switches and not having a WLC's redundancy...
based on your answer I suppose that no network connections redundancy are available on the 2100 models (channel, AP manager secondary interface,...) are available...
Omar

Similar Messages

  • WLC 5508 / 3750 Switch LAG Problems

    Hello Forum,
    for presenting to the client (customer wants to buy any Cisco) I have built up in our laboratory a WLAN environment.
    The structure is composed of: - WLC5508 HA cluster (7.6.110.0) - Some AP2602i - C3750E (12.2 (55) SE3)
    Which reminds me strange behavior with LAG noticed that I can not explain?
    The ports of the WLCs are in the LAG mode each WLC are connected with two cables at the switch. On the switch a port-channel are configured (no LACP = channel-group 8 mode on).
    Failure scenario:
    Deducted on the primary controller the cable from port 1 (it goes down), the port LED turns from green to orange >>>> no impact on the system, everything remains as it is and the system continues to operate. Deducted on the primary controller the cable from port 2 (goes down), the port LED remains green. HA >>>> the backup controller takes over? Primary controller boots?
    That can not be true that here changes the system to the redundant WLC. The system should, as yet just keep working at switch-switch LAG?
    Is this a configuration error or a BUG? Upon request, I can gladly send the WLC and Switch configuration.
    Best Regards, Alexander Weitzel 

    The HA kicks in when the primary looses gateway, do a small test, keep a continuous ping to WLC  from its gateway as source and break one of the link in the LAG and see if you drop any packet ?

  • WLC-2106 and multiple interfaces on the same network

    Hi there,
    I recently created a TAC request to the Cisco support regarding our WLC-2106, but they could not help me. Basically I just learned that you can create new interfaces for the wireless LAN controller and then dedicate them to a given wireless network (SSID). This way I could more effectively utilize network bandwidth also. Problem is that all of the interfaces have to be in a different network segment in order to work, which is not what I want. I specifically want to have several interfaces on the same network segment.
    Has anyone tried to accomplish the same?

    Basically what I've misunderstood is that all the traffic generated by our wireless clients have been going through the single 100Mbit/s ethernet port on the wireless LAN controller (management interface), and to mitigate this I thought I could create new interfaces (ports) and dedicate those to given WLAN networks.. I see now that this is not supported. Not inside the same network at least.
    So, by reading further and consulting my best friend Google I learned about a setting called "AP Mode". Changing that from Local (the default) to H-REAP the APs should not route their traffic anymore through the management interface on the wireless controller, but instead route all the client traffic directly to the local LAN. This way you effectively remove the 100Mbit/s bottle-neck when all the APs were using the management interface both for configuration and client data traffic.
    It seems you also have to enable H-REAP Local switching from a given WLAN network in addition to changing the AP Mode of your access points to H-REAP. I'm still in the testing phase here so should anyone have any insight to this, I'd be greatful to hear more.

  • AP 1140 and WLC 2106

    Does someone know if WLC 2106 support AP 1140 ? I read that AP 1140 is CAPWAP only and I don't know if WLC 2106 supports CAPWAP.
    Thanks

    Yes it does, you may have to upgrade your controller software to get 802.11n and CAPWAP, use the latest code 6.0.182.
    CAPWAP was supported from code 5.2.157
    The max throughput on the 2106 though is only 100mbps so yo wont see the highest speeds

  • WLC 2106 problem

    Hello,
    I have problem with new one WLC 2106 controller. I make this basic configuration (after reset):
    (Cisco Controller) >show interface summary
    Interface Name                   Port Vlan Id  IP Address      Type    Ap Mgr Guest
    ap-manager                       1    10       10.10.10.21     Static  Yes    No
    management                       1    10       10.10.10.20     Static  No     No
    virtual                          N/A  N/A      1.1.1.1         Static  No     No
    At this point, everything works OK. Controller is accesible via HTTPS, AP (one 1130) is connected too. But next I need create new WLAN and another interface VLAN - named ak-lan
    config interface create ak-lan
    config interface port ak-lan 1
    HTTPS acces is still working, but when I configure IP adress:
    config interface address dynamic-interface ak-lan 10.10.11.10 255.255.255.0 10.10.11.1
    HTTPS acces stops. In fact, it seem like HTTPS starts on new interface - it's accesible via 10.10.11.10, but (after certificate warning) shows only empty page (Page is not accesible..)
    I dont have an idea why. I tray downgrade software (originaly comes with 7.0.98.0) to 6.0.196.0, whitch I use on another same controller, but the behavior is the same. Now I use software 6.0.199.4. Again the same behavior.
    "show interface summary" says:
    (Cisco Controller) >show interface summary
    Interface Name                   Port Vlan Id  IP Address      Type    Ap Mgr Guest
    ak-lan                           1    11       10.10.11.10     Dynamic No     No
    ap-manager                       1    10       10.10.10.21     Static  Yes    No
    management                       1    10       10.10.10.20     Static  No     No
    virtual                          N/A  N/A      1.1.1.1         Static  No     No
    (Cisco Controller) >
    All interfaces (excluding virtual) matched to ping. All ïnterfaces have netmask 255.255.255.0.
    There was another strange thing - "show sysinfo" says that I use sw 6.0.199.4 and emergency is 7.0.98.0, but "show boot" says:
    (Cisco Controller) >show boot
    Primary Boot Image............................... 6.0.199.4 (active)
    Backup Boot Image................................ 6.0.196.0
    (Cisco Controller) >
    (Cisco Controller) >show sysinfo
    Manufacturer's Name.............................. Cisco Systems Inc.
    Product Name..................................... Cisco Controller
    Product Version.................................. 6.0.199.4
    RTOS Version..................................... 6.0.199.4
    Bootloader Version............................... 4.0.191.0
    Emergency Image Version.......................... 7.0.98.0
    Build Type....................................... DATA + WPS
    System Name...................................... ak-wlc
    System Location..................................
    System Contact...................................
    System ObjectID.................................. 1.3.6.1.4.1.9.1.828
    IP Address....................................... 10.10.10.20
    System Up Time................................... 0 days 0 hrs 46 mins 35 secs
    System Timezone Location.........................
    Configured Country............................... DE  - Germany
    Operating Environment............................ Commercial (0 to 40 C)
    Internal Temp Alarm Limits....................... 0 to 65 C
    Internal Temperature............................. +55 C
    State of 802.11b Network......................... Enabled
    State of 802.11a Network......................... Enabled
    Number of WLANs.................................. 0
    3rd Party Access Point Support................... Disabled
    Number of Active Clients......................... 0
    Burned-in MAC Address............................ E0:5F:B9:63:7B:00

    Switch is C2960, port Gi0/2:
    Gi0/2     T wlc              connected    trunk      a-full  a-100 10/100/1000BaseTX
    interface GigabitEthernet0/2
    description T wlc
    switchport trunk allowed vlan 10,11,100
    switchport mode trunk
    end
    VLANs are set properly. Router is ASA 5510, and routing is fine. Morever, interfaces on WLC is accesible via ping (I dot't try telnet or ssh).

  • AP1522 with WLC 2106

    Hi.
    I want to know how to join the AP1522 to a WLC 2106.
    The Controller and the AP are in the network, but the AP can't be joined to the controller. What is missing?

    First of all make sure that the APs can communicate and get IP address from DHCP server (it might be an external DHCP or internal pool running on WLC).
    Are your APs on the same subnet as controller?

  • WLC 2106 and Linksys Bridge WET610N works with 7.0.116.0 release?

    Hi all,
    i'm having troubles with WLC 2106 controller and several wireless bridges, so i'd like to know if i can fix it in some way.
    My environment is as follows:
    1 WLC 2106 with 2 Aironet 1240G
    I have a production appliance that needs an ethernet port to work, so i bought a Linksys Bridge WET610N to make it works via wireless.
    The Linksys bridge connects to the 1240G as a client and works well, but the appliance connected to the ethernet port of the bridge is unreachable.
    Searching for the problem, i found that the wlc act as a proxy arp for the wireless clients and being the ethernet appliance a "passive" client, the controller isn't aware of it.
    My WLC is running the 7.0.98.0 firmware. In the release notes for the 7.0.116.0, in the "Non-Cisco WGB Support" seems to state that now also non cisco bridges can work using the passive client feature. I've already enabled it on my controller but this didn't solve my problem.
    Can anyone tell me if the upgrade to the 7.0.116.0 can fix it?
    Thanks in advance
    Riccardo Coppola

    I'm not sure what (cheap) devices can do the wgb feature that is inter-brand compatible.
    The thing is that the WLC enforces the rule "1 wireless client = 1 client". Meaning you can't bridge multiple clients behind a wireless clients, that just screws up roaming mechanisms etc ...
    Cisco WGBs have the IAPP protocol to tell the WLC "listen, I'm a WGB wireless client and those are the wired clients connected to me, allow them on the network".
    What does "universal WGB" feature does is that the WGB forwards the traffic of the client (only 1 client supported in this case !) to the infrastructure AP but the WGB never sends anything with its own mac address. It uses the client mac address as source.
    This means that the WLC has no way of knowing that there is more than 1 device. It just thinks that your wired client is a wireless client.
    So it's more than mac cloning since the WgB has to be the one authenticating to the infrastructure (Wpa/wpa2 whatsoever) by spoofing the client mac. The WGB is still in charge of roaming decisions and so on and so on...
    I hope it clarifies the situation ?

  • Want to configure wpa2 enterprise in wlc 2106

    Hi,
    I want to configure the wlc 2106 with wpa2 enterprise .... i reckon that iI need ACS server ( Radius Server ) with server certificate as well client certificate.
    how do i configure the redius server to get access through wpa2 enterprise .. If i am wrong , what are all things required to enable wpa2 enterprise with AES encryption .
    Is it possible to get the evalution copy of acs server with certificate ?
    how to go ahead for the same .
    It would be great help me to get the proper answer  for configuration of wpa2 enterprise with AES ...

    The below link may help you..
    http://www.cisco.com/en/US/products/ps6366/products_configuration_example09186a008095382f.shtml
    Regards
    Surendra

  • WLC 2106 and iPhones

    Just recently I am having issues with my WLC 2106 WiFi network and iPhones.  For the past week, the iPhones have been locking up the network much like as it was described with the ARP issues with the exception that what I have been reading, this issue did not effect the 2100 series.
    I've done searches but have not found anything applicable to what is happening now.
    Any help will be GREATLY appreciated.

    It's running on v. 4.0.217.0.  Right now I'm controlling who is accessing the wifi via MAC filter to prevent anyone with an iphone to log on but that just doesn't cut it since there's a lot of visitors coming in to use the wifi.
    I won't be able to go in and do more testing for a week or two to get that debug log.
    But this seems to be a common issue with at least the 2106s.  As soon as anyone logs in with an iphone, the controller locks up and the only thing to do is reboot.  It only fairly recently started happening so maybe it's only with the newer iphones?

  • WLC 2106 question

    Hello,
    What is the recomended way to connect  5 APs 1242 to a wlc 2106?
    Connect directly the 5 APs to the wlc and use one port for the management interface and connection to the switch or to connect the APs to a switch and use one connection for the wlc?
    Thanks in advance.

    Depends on the AP.
    One FastEthernet connection to the switch doens't "really" create a bottleneck.  Your AP might.  If you, say, you have 1130 or older then I'd say no significant bottleneck because the APs are also FastEthernet.
    If you use the newer ones, like the 1250 and newer, which has GigEthernet and/or higher throughput (if you enable 802.11n) the yes.  The switch AND the WLC 2100 are both the bottleneck.

  • WLC 2106 Configuration steps

    I have WLC 2106,And 5 LWAP, 3 Cat3560 Switches.and my 2851 CME router providing DHCP for Data VLAN 1 nad Voice VLAN 100
    any one can please help me how to do the basic configuration
    when i configure Managment and AP manager on WLC 2106 on untaged VLAN 0 i can able to ping but when i cahnged the VLAN to 1 im not able to communicate to WLC from switch or any port from WLC
    please help me to configure the WLC
    Thanks & Regards
    PRajoth

    The software guide states "A zero value for the VLAN identifier (on the Controller > Interfaces page) means that the interface is untagged.
    The default (untagged) native VLAN on Cisco switches is VLAN 1. When controller interfaces are configured as tagged (meaning that the VLAN identifier is set to a non-zero value), the VLAN must be allowed on the 802.1Q trunk configuration on the neighbor switch and not be the native untagged VLAN.
    Cisco recommends that only tagged VLANs be used on the controller. You should also allow only relevant VLANs on the neighbor switch's 802.1Q trunk connections to controller ports. All other VLANs should be disallowed or pruned in the switch port trunk configuration. This practice is extremely important for optimal performance of the controller.
    Note Cisco recommends that you assign one set of VLANs for WLANs and a different set of VLANs for management interfaces to ensure that controllers properly route VLAN traffic"
    Can you supply a screen shot of the interfaces page from your WLC and supply the WLC switch port configuration also? Just to sanity check what you have so far?

  • Microsoft Server 2003 / PEAP / WLC 2106

    Has anyone ever had a certificate vanishing issue on an M$ Server 2003?  For some strange reason the certificate under my IAS RAS policy keeps disappearing after an undetermined amount of time?  The server is the only DC / CA root / IAS in the forest.  I'm not sure why the self-signed cert. will not remain in the cert. store?
    Current config.:
    (2) WLC 2106 (both RADIUS clients on DC/IAS)
    (5) 1141 LAPs
    Authentication: PEAP/MS-CHAPv2
    Encryption: TKIP/AES
    Any ideas?  Thanks.

    In 4.1, disabling DHCP proxy did just that, it disabled the "proxy". If you ever look at your dhcp lease of a wireless client, it comes from a dhcp server of 1.1.1.1 (virtual IP of the controller). With proxy disabled, the address will no longer be masked.
    In 4.2 and beyond, disabling dhcp proxy actually disables the DHCP Relay that is the process of the controller sending the dhcp requests to a specified server.
    So if in 4.1, you had "dhcp proxy" disabled, in 4.2 and beyond, you are actually disabling the relay as well.
    If this is indeed the case, enable dhcp proxy, or add an IP Helper adress to your router for this vlan, just like you would normally do for Wired clients.

  • WLC 2504 redundancy set up

    WLC: 2504
    Firmware: 7.6.100
    Hello,
    I'm getting very confused in how to set up redundancy with WLC 2504. Some sources talk about Client SSO, some about N+1.
    But it seems that although I should use Client SSO with firmware 7.6, the WLC 2504 doesn't support it.
    When I type config redundancy, I have no choice
    >config redundancy ?
    unit           Configure redundancy unit [primary | secondary]
    So I typed "config redundancy unit primary" on my 2504 and "config redundancy unit secondary" on my 2504-HA
    And when I issue this command I have very little information
    >show redundancy summary
    Type of the Unit = Primary
    Does someone has guidelines for redundancy with WLC 2504 on firmware 7.6 ?
    Thank you

    Hello,
    Thank you both for your answers.
    Something I didn't understand in the documentation is this.
    Is there a replication of configuration between the WLC primary and the HA ? I did read that they should have different network settings (IP addresses) so I understand that there is not a total replication, what about the rest of the configuration ?
    The only result I have when I issue a command on the WLC-HA is this
    >show redundancy summary
    Type of the Unit = Secondary
    It doesn't look exactly what I see in the documentation.
    Thank you

  • Wlc 2106 problem ( cant connect to 2 lwapp ( 1242 & 1131 ) need advice

    Dear All,
    could you give me some advice to configure wlc with 2 lwapp,
    i did try to used 1 lwapp ( 1242 ag ) and it's work, but when i try to connect with 2 lwapp ( 1242 & 1131 ), i can't associated with lwapp 1131 ag, i did used same configuration for both,
    need youd advice and reference guide for this issue.
    thanks and regards

    Hi Heru,
    If both are lwapp aps then they should be able to join 2106 controller. Can you confirm if 1130 is also connected to same subnet where 1242 is connected? Is management subnet/vlan different from the vlan you are connecting your LWAPP APs.
    Hope this link should help
    http://www.cisco.com/en/US/docs/wireless/controller/4.2/configuration/guide/c42lwap.html#wp1104685
    HTH
    Ankur
    *Pls rate all helpfull post

  • WLC Best Practice - split LAG?

    Hi
    Reading "Wireless LAN Controller Configuration Best Practices" document from Cisco I see this:
    "Do not configure a LAG connection that spans across multiple switches. When you use LAG, it must be with all ports that belong to the same EtherChannel that goes to the same physical switch."
    My question: Is it considered good or bad design to split the WLC LAG across multiple physical switches also when using virtual switches like VSS in 6500? Or to connect the LAG to different 3750 stack-members in the same stack?
    Br Jimmy

    As leolaohoo wrote, a 3750 stack or 6500 VSS are considered as  one logical switch, and you will not have any problem connect a LAG to  diffrent switches within the stack or VSS.

Maybe you are looking for