4 LAP1522, WLC 2112, 15dB antenna

Hy,
I have a problem with low power signal receive on antenna.
If I stay near to antenna the signal power is to 50%.
It's ok?
I have 1 WLC Controller 2112, the TX signal power is set to 1.
It's possible to miss some configuration on WLC?

Make sure the AP has enough power. Lower power on the AP results in lower signal strength, which decreases the throughput.

Similar Messages

  • WLC 2112 & MacBook or Apple Devices ???

    Dear All,
    Last week i succesfully configured the WLC 2112 with 12 AP ofcourse :)  with 3 SSIDs
    the issue i am facing is that users with MacBooks & Ipad's are having issues connecting to new wireless setup. where as all other Brand Laptops and PDAs are getting connected just fine.
    When i am trying to connect a MacBook to a SSID and when i enter the password after 10 or 15 sec the MacBook self assigns an IP address to itself intead of getting the password from WLC's DHCP.
    i have set  Authentication level is basic WEP key protection.
    Channel set to overlapping channel 10.
    Experts i need your Experties. will appriciate if i can get a Quick Response.

    Hi,
    Are the Mac and Apple devices configured to get a dynamic dhcp ? What is the Subnet from which these devices getting IP from ?
    Could you disable Aironet extenstions under wlan > advanced section and test as this enhances the third party clients to be able to connect to Cisco device.
    Regards,
    Madhuri

  • WLC 2112 with LAP 1042N

    Hi Guys.
    we are trying to configure WLC 2112 with LAP 1042 but getting following erros on LAP1042.
    It show the Ap is not supported in controller version 6.0.199.4
    *Jan  5 16:52:13.397: %CAPWAP-5-DTLSREQSUCC: DTLS connection created sucessfully peer_ip: 192.168.2.101 peer_port: 5246
    *Jan  5 16:52:13.398: %CAPWAP-5-SENDJOIN: sending Join Request to 192.168.2.101
    *Jan  5 16:52:13.399: %CAPWAP-5-CHANGED: CAPWAP changed state to JOIN
    *Jan  5 16:52:13.410: %CAPWAP-3-ERRORLOG: This AP is not supported in controller version 6.0.199.4
    *Jan  5 16:52:13.495: %CAPWAP-5-CHANGED: CAPWAP changed state to CFG
    *Jan  5 16:52:13.496: %DTLS-5-SEND_ALERT: Send FATAL : Close notify Alert to 192.168.2.101:5246
    *Jan  5 16:52:13.497: %CAPWAP-5-CHANGED: CAPWAP changed state to DISCOVERY
    *Jan  5 16:52:13.498: %CAPWAP-5-CHANGED: CAPWAP changed state to DISCOVERY
    *Jan  5 16:52:19.552: %CAPWAP-3-ERRORLOG: Dropping dtls packet since session is not established.
    *Jan  5 16:52:29.551: %CAPWAP-3-ERRORLOG: Go join a capwap controller
    WLC 2112 software version 6.0.199.4
    LAP 1042 image version 7.0.94.21
    If any one can help me out then it wolud be great.
    Thanks in advance for all.

    You should upgrade your controller to 7.0.116.0 or 7.0.220.0
    Sent from Cisco Technical Support iPhone App

  • WLC 2112 and WLC 2504

    This might be a really stupid question but I need to ask just so that I get a definitive answer. I have a customer that is using a WLC 2112 and has maxed out the licenses for the WLC. I have suggested for him to purchase a 2504 with 30 or 40 licenses to replace the existing 2112. He doesn't want to purchase 30 to 40 licenses and doesn't want to remove the 2112 from the network environment. He would rather purchase a WLC 2504 with 15 licenses and just add that into the network.
    My question is, will there be a problem running a 2504 and a 2112 on the same network? Or can I just make one a primary and one a secondary?

    That should be fine. Just make sure the WLCs are running the same code version and everything should work fine. This is required for APs failover from one WLC to another. You don't want the APs upgrading or downgrading code versions every time the ap moves from the primary to the secondary WLC.
    Sent from Cisco Technical Support iPhone App

  • WLC 2112 is not accessable

    Hello Experts,
    I have a problem with my Cisco WLC 2112.
    Problems:
    1. I can not reach this WLC via GUI or CLI.
    2. Can not access via Console.
    3. Status LED is Dark Orange or Red.
    Can anybody help.
    Regards

    Hi,
    Status LED is Amber(ORANGE/RED)— Means Problem encountered during boot.
    http://www.cisco.com/en/US/docs/wireless/controller/2100/quick/guide/ctrl206q.html#wp39363
    Did u tried with these settings:
    9600 baud
    8 data bits
    No flow control
    1 stop bit
    No parity
    If the console is not responsive, then its a hardware failure and you should contact the TAC or You should RMA'd it.
    Be aware: WLC 2100 Series are EOL/EOS.
    http://www.cisco.com/en/US/prod/collateral/wireless/ps6302/ps8322/ps7206/ps7221/end_of_life_notice_c51-691053.html
    Regards
    Dont forget to rate helpful posts

  • WLC 2112 with 1042 Mesh APs

    Hello everybody,
    I have a Mesh architecture with 2112 WLC and 1042 APs
    I want just to know if I can connect one 1310 AP to the ethernet port of a mesh 1042 AP with ethernet bridging enabled.
    thanks

    Hello benhamzagi,
    Thank you for contacting the Sales Acceleration Center (SAC) regarding your recent inquiry, Case Number 80931
    Case Description:
    WLC 2112 with 1042 Mesh APs
    Case Solution:
    Here is the compatibility Matrix link
    http://www.cisco.com/en/US/docs/wireless/controller/5500/tech_notes/Wireless_Software_Compatibility_Matrix.html#wp118661
    Or the attach tables will help you base on Release, Controller, Mesh and AP
    Table 3 Controller Software Release and Controller Model Support Matrix
    Controller Model
    First Support
    Last Support
    2100
    4.2.x
    7.0.x
    2500
    7.0.x
    Cat3850
    3.2.0SE
    4400
    4.2.x
    7.0.x
    5500
    6.0.x
    5700
    3.2.0SE
    7500
    7.0.x
    8500
    7.3.x
    Virtual Controller
    7.3.x
    WiSM
    4.2.x
    7.0.x
    WiSM2 (1 DP)
    7.0.x
    WiSM2 (2 DP)
    7.2.x
    SRE
    7.0.x
    Table 4 Mesh and Controller Software Releases and the Supported APs
    Mesh and Controller Releases
    Supported Access Points
    7.4.x
    1522, 1524PS, 1524SB, 1552E, 1552H, 1552I, 1552C, 1552EU, 1552CU, 1552S, 1130, 1240, 1250, 1260, 1600, 2600, 3500e, 3500i, 3500p, 3600e, 3600i, 1140, 600 OEAP, AP801, AP802
    7.3.x
    1522, 1524PS, 1524SB, 1552E, 1552H, 1552I, 1552C, 1552EU, 1552CU, 1552S, 1130, 1240, 1250, 1260, 2600, 3500e, 3500i, 3600e, 3600i, 3500p, 1140, 600 OEAP, AP801, AP802
    7.2.11x.x
    1522, 1524PS, 1524SB, 1552E, 1552H, 1552I, 1552C, 1552S, 1130, 1240, 1250, 1260, 2600, 3500e, 3500i, 3500p, 3600e, 3600i, 1140, 600 OEAP, AP801, AP802
    7.2.10x.x
    1522, 1524PS, 1524SB, 1552E, 1552H, 1552I, 1552C, 1552S, 1130, 1240, 1250, 1260, 3500e, 3500i, 3600e, 3500p, 3600i, 1140, 600 OEAP, AP801, AP802
    7.0.2x.x
    1522, 1524PS, 1524SB, 1552E, 1552H, 1552I, 1552C, 1130, 1240, 1250, 1260, 3500e, 3500i, 3500p, 1140, 600 OEAP, AP801, AP802
    7.0.116.0
    1522, 1524PS, 1524SB, 1552E, 1552H, 1552I, 1552C, 1130, 1240, 1250, 1260, 3500e, 3500i, 3500p, 1140, 600 OEAP, AP801, AP802
    7.0.98.x
    1522, 1524PS, 1524SB, 1130, 1240
    6.0.202.0
    1522, 1524PS, 1524SB, 1130, 1240
    5.2.193.0
    1522, 1524PS, 1130, 1240
    4.1.192.35M (Mesh Release 3)
    1505, 1510, 1522, 1524PS, 1130, 1240
    4.1.191.24M (Mesh Release 2)
    1505, 1510, 1522 (US, Canada, and RoW), 1130, 1240
    4.1.190.5 (Mesh Release 1)
    1505, 1510, 1522 (US and Canada)
    As per your confirmation, I am going to close the case for this specific inquiry. We strive to provide you with excellent service. Please feel free to reach out to me or any member of the SAC team if we can be of any further assistance or if you have any other related questions in the future. We value your input and look forward to serving you moving forward.

  • WLC 2112 - APs disassociating

    I've found some discussion on this, but nothing that's helped resolve so I'm hoping someone can help. We recently purchased a 2112 WLC, running version 6.0.199.4. I have everything running through a single port on the controller, which is connected to a trunk port on our 3750 stack. Our management VLAN is vlan 40, and AP is plugged into another port on the same switch which is an access port in vlan 40. APs appear in the controller ok, receive an IP address, but we aren't able to connect to any of the WLANs and periodically the APs will disassociate with the following messages:
    0
    Thu Mar 22 09:47:51 2012
    AP 'AP003a.99eb.702d', MAC: b8:62:1f:45:95:b0 disassociated previously due to AP Reset. Uptime: 0 days, 00 h 35 m 52 s . Last reset reason: operator changed 11g mode
    1
    Thu Mar 22 09:47:39 2012
    AP Disassociated. Base Radio MAC:b8:62:1f:45:95:b0
    2
    Thu Mar 22 09:47:39 2012
    AP's Interface:0(802.11b) Operation State Down: Base Radio MAC:b8:62:1f:45:95:b0 Cause=New Discovery
    I'm not sure if that's related to why we can't connect to the WLANs or not...
    Another wrinkle is that if we plug in the AP directly to one of the PoE ports on the controller, it all works perfectly. Any ideas? I'm guessing its something switch-related since the only difference is that we're not going through the switch when it works.
    Thanks in advance,
    Matt

    Both APs in the same switch and in different switches do the same thing. They don't reboot, just disassociate. Here is the status on one of them:
    UP time: 2 hours+
    Controller Associated Time: 6 minutes
    Controller Association Latency: 14 seconds
    They associate as soon as they come up, but then disassociate and reassociate. They have this message:
    AP's Interface:0(802.11b) Operation State Down: Base Radio MAC:b8:62:1f:45:95:b0 Cause=New Discovery
    in addition to sometimes showing a Heartbeat Timeout cause for the disassociation. In addition, sometimes it shows the cause being Max Retransmissions. I thought it was just the AP, but it happens with the second AP as well. Here are my switch port configs:
    For AP:
    interface GigabitEthernet7/0/14
    description Test AP
    switchport access vlan 40
    switchport mode access
    spanning-tree portfast
    For WLC:
    interface GigabitEthernet7/0/2
    description WLC Management Port
    switchport trunk encapsulation dot1q
    switchport trunk allowed vlan 40,55,82,94
    switchport mode trunk
    spanning-tree portfast trunk
    It is detecting Rogue APs (these are the existing APs that we want to replace with this system). Could that be causing issues? I don't think so since it works just fine when plugged directly in to the WLC.
    Could it be WLC software version?

  • DHCP setup help on AIR-WLC-2112 with LAP1042N

    I am new to wireless.  I would like to statically assign ip addresses for my controller(AIR_WLC-2112) and my access point (LAP1042N).  I would then like the controller to distribute dhcp addresses for users.  What is the best way in doing this? 

    Hi Mark,
    You can certainly setup your network for 2 VLANs for different wireless networks. You will only need to setup the switchports to the WLC as trunks. In other words, the APs will simply reside in the vlan you define (access switchports) and they will tunnel all traffic back to the controller, regardless of client vlan. The WLC will then determine which vlan the traffic needs to go on.
    You have 2 ways of setting your AP IP addresses as static -- you can statically assign them through the console during initial installation:
    capwap ap ip address
    capwap ap ip default-gateway
    capwap ap controller ip
    Or, you can simply let the APs start by using DHCP, and auto discovery of the WLCs via DNS lookup of "cisco-capwap-controller", or DHCP option 43. Once they join the controller you can assign them static addresses in the WLC AP settings.
    Now, onto the last question regarding your WAN sites. We do have options for you there as well -- the feature we're looking at would be H-REAP. Traditionally the APs tunnel all wireless traffic back to the controller. However, in H-REAP mode, you can specify the APs to put traffic on the network right at the local switch, so it wouldn't have to get tunneled across your WAN (depending on WAN bandwidth). You still configure the AP and manage it centrally. For more information on this feature, please check out the H-REAP deployment guide:
    http://www.cisco.com/en/US/products/ps10315/products_tech_note09186a0080736123.shtml
    -Patrick Croak
    Wireless TAC

  • WLC 2112 GUI Connection problem

    I am not able to connect to the GUI on the Cisco Wireless Controller 2112.  I noticed from the interface summary that the "GU" (GUI?) are all "No" on both the management and ap-manager interfaces.  How to set them to "Yes" from the console (CLI)?
    Thanks.
    <<<<System Info>>>>
    (Cisco Controller) >show interface summary
    Interface Name         Port Vlan Id  IP Address       Type     Ap Mgr Gu
    est
    ap-manager         1     untagged 10.1.4.62  Static  Yes     No
    management         1     untagged 10.1.4.61  Static  No      No
    virtual        N/A  N/A       1.1.1.1      Static  No      No
    (Cisco Controller) > show network summary
    RF-Network Name............................. RFGroup
    Web Mode.................................... Enable
    Secure Web Mode............................. Enable
    Secure Web Mode Cipher-Option High.......... Disable
    Secure Web Mode Cipher-Option SSLv2......... Enable
    Secure Shell (ssh).......................... Enable
    Telnet...................................... Enable
    Ethernet Multicast Mode..................... Disable
    Ethernet Broadcast Mode..................... Disable
    AP Multicast Mode........................... Multicast   Address : 0.0.0.0
    IGMP snooping............................... Disabled
    IGMP timeout................................ 60 seconds
    User Idle Timeout........................... 300 seconds
    ARP Idle Timeout............................ 300 seconds
    Cisco AP Default Master..................... Disable
    AP Join Priority............................ Disable
    Mgmt Via Wireless Interface................. Disable
    Mgmt Via Dynamic Interface.................. Enable
    Bridge MAC filter Config.................... Enable
    Bridge Security Mode........................ EAP
    Mesh Full Sector DFS........................ Enable
    --More-- or (q)uit
    Over The Air Provisioning of AP's........... Disable
    AP Fallback ................................ Enable
    Web Auth Redirect Ports .................... 80
    Fast SSID Change ........................... Disabled
    (Cisco Controller) > show run-config
    Interface Configuration
    Interface Name................................... ap-manager
    MAC Address...................................... 70:81:05:af:1d:20
    IP Address....................................... 10.1.4.62
    IP Netmask....................................... 255.255.252.0
    IP Gateway....................................... 10.1.2.1
    VLAN............................................. untagged 
    Physical Port.................................... 1
    Primary DHCP Server.............................. 10.1.2.1
    Secondary DHCP Server............................ Unconfigured
    DHCP Option 82................................... Disabled
    ACL.............................................. Unconfigured
    AP Manager....................................... Yes
    Guest Interface.................................. No
    Interface Name................................... management
    MAC Address...................................... 70:81:05:af:1d:20
    IP Address....................................... 10.1.4.61
    IP Netmask....................................... 255.255.252.0
    IP Gateway....................................... 10.1.2.1
    VLAN............................................. untagged 
    Quarantine-vlan.................................. 0
    Physical Port.................................... 1
    Primary DHCP Server.............................. 10.1.2.1
    Secondary DHCP Server............................ Unconfigured
    DHCP Option 82................................... Disabled
    ACL.............................................. Unconfigured
    AP Manager....................................... No
    Guest Interface.................................. No
    Interface Name................................... virtual
    MAC Address...................................... 70:81:05:af:1d:20
    IP Address....................................... 1.1.1.1
    DHCP Option 82................................... Disabled
    Virtual DNS Host Name............................ Disabled
    AP Manager....................................... No
    Guest Interface.................................. No

    Port 30 detail Info:
    GigabitEthernet0/30 is up, line protocol is up (connected)
      Hardware is Gigabit Ethernet, address is 0c85.25d4.a91e (bia 0c85.25d4.a91e)
      MTU 1500 bytes, BW 100000 Kbit, DLY 100 usec,
         reliability 255/255, txload 1/255, rxload 1/255
      Encapsulation ARPA, loopback not set
      Keepalive set (10 sec)
      Full-duplex, 100Mb/s, media type is 10/100/1000BaseTX
      input flow-control is off, output flow-control is unsupported
      ARP type: ARPA, ARP Timeout 04:00:00
      Last input 00:00:31, output 00:00:00, output hang never
      Last clearing of "show interface" counters never
      Input queue: 0/75/0/0 (size/max/drops/flushes); Total output drops: 0
      Queueing strategy: fifo
      Output queue: 0/0 (size/max)
      5 minute input rate 0 bits/sec, 0 packets/sec
      5 minute output rate 0 bits/sec, 0 packets/sec
         6841 packets input, 2789942 bytes, 0 no buffer
         Received 3461 broadcasts (3042 multicasts)
         18549 runts, 0 giants, 0 throttles
         18549 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored
         0 watchdog, 3042 multicast, 0 pause input
         0 input packets with dribble condition detected
         383015 packets output, 66928405 bytes, 0 underruns
         0 output errors, 0 collisions, 5 interface resets
         0 babbles, 0 late collision, 0 deferred
         0 lost carrier, 0 no carrier, 0 PAUSE output
         0 output buffer failures, 0 output buffers swapped out
    Interface summary
    *: interface is up
    IHQ: pkts in input hold queue     IQD: pkts dropped from input queue
    OHQ: pkts in output hold queue    OQD: pkts dropped from output queue
    RXBS: rx rate (bits/sec)          RXPS: rx rate (pkts/sec)
    TXBS: tx rate (bits/sec)          TXPS: tx rate (pkts/sec)
    TRTL: throttle count
      Interface               IHQ   IQD  OHQ   OQD  RXBS RXPS  TXBS TXPS TRTL
    * Vlan1                    0 12861    0     0     0    0     0    0    0
      GigabitEthernet0/1       0     0    0     0     0    0     0    0    0
    * GigabitEthernet0/2       0     0    0     0     0    0  2000    1    0
      GigabitEthernet0/3       0     0    0     0     0    0     0    0    0
      GigabitEthernet0/4       0     0    0     0     0    0     0    0    0
      GigabitEthernet0/5       0     0    0     0     0    0     0    0    0
      GigabitEthernet0/6       0     0    0     0     0    0     0    0    0
      GigabitEthernet0/7       0     0    0     0     0    0     0    0    0
      GigabitEthernet0/8       0     0    0     0     0    0     0    0    0
      GigabitEthernet0/9       0     0    0     0     0    0     0    0    0
      GigabitEthernet0/10      0     0    0     0     0    0     0    0    0
      GigabitEthernet0/11      0     0    0     0     0    0     0    0    0
      GigabitEthernet0/12      0     0    0     0     0    0     0    0    0
      GigabitEthernet0/13      0     0    0     0     0    0     0    0    0
      GigabitEthernet0/14      0     0    0     0     0    0     0    0    0
      GigabitEthernet0/15      0     0    0     0     0    0     0    0    0
      GigabitEthernet0/16      0     0    0 7219768     0    0     0    0    0
      GigabitEthernet0/17      0     0    0     0     0    0     0    0    0
      GigabitEthernet0/18      0     0    0     0     0    0     0    0    0
      GigabitEthernet0/19      0     0    0     0     0    0     0    0    0
      GigabitEthernet0/20      0     0    0     0     0    0     0    0    0
      GigabitEthernet0/21      0     0    0     0     0    0     0    0    0
      GigabitEthernet0/22      0     0    0     0     0    0     0    0    0
      GigabitEthernet0/23      0     0    0     0     0    0     0    0    0
      GigabitEthernet0/24      0     0    0     0     0    0     0    0    0
      GigabitEthernet0/25      0     0    0     0     0    0     0    0    0
      GigabitEthernet0/26      0     0    0     0     0    0     0    0    0
      GigabitEthernet0/27      0     0    0     0     0    0     0    0    0
      GigabitEthernet0/28      0     0    0     0     0    0     0    0    0
      GigabitEthernet0/29      0     0    0     0     0    0     0    0    0
    * GigabitEthernet0/30      0     0    0     0     0    0  2000    2    0
      GigabitEthernet0/31      0     0    0     0     0    0     0    0    0
      GigabitEthernet0/32      0     0    0     0     0    0     0    0    0
      GigabitEthernet0/33      0     0    0     0     0    0     0    0    0
      GigabitEthernet0/34      0     0    0     0     0    0     0    0    0
      GigabitEthernet0/35      0     0    0     0     0    0     0    0    0
      GigabitEthernet0/36      0     0    0     0     0    0     0    0    0
      GigabitEthernet0/37      0     0    0 4997649     0    0     0    0    0
      GigabitEthernet0/38      0     0    0     0     0    0     0    0    0
      GigabitEthernet0/39      0     0    0     0     0    0     0    0    0
      GigabitEthernet0/40      0     0    0     0     0    0     0    0    0
      GigabitEthernet0/41      0     0    0     0     0    0     0    0    0
      GigabitEthernet0/42      0     0    0     0     0    0     0    0    0
      GigabitEthernet0/43      0     0    0     0     0    0     0    0    0
      GigabitEthernet0/44      0     0    0     0     0    0     0    0    0
      GigabitEthernet0/45      0     0    0     0     0    0     0    0    0
      GigabitEthernet0/46      0     0    0     0     0    0     0    0    0
    * GigabitEthernet0/47      0     0    0 5011848     0    0  2000    2    0
      Interface               IHQ   IQD  OHQ   OQD  RXBS RXPS  TXBS TXPS TRTL
      GigabitEthernet0/48      0     0    0     0     0    0     0    0    0
      GigabitEthernet0/49      0     0    0     0     0    0     0    0    0
      GigabitEthernet0/50      0     0    0     0     0    0     0    0    0
    * GigabitEthernet0/51      0     0    0     0  3000    3  1000    1    0
      GigabitEthernet0/52      0     0    0     0     0    0     0    0    0

  • WLC 2112

    Hi all,
    Just 2 quick question.
    1. Is this controller able to support admin access authentication via Cisco ACS?
    2. The wireless user going to use 802.1x authentication. If the user connected to the network via wired connection, do they need to reauthenticate when they swing to wireless?
    Thanks.
    Best regards,
    Ethan

    1. Is this controller able to support admin access authentication via Cisco ACS?
    >> Yes... we need t oconfigure the radius server settings in the security AAA section on the WLC
    2.  The wireless user going to use 802.1x authentication. If the user  connected to the network via wired connection, do they need to  reauthenticate when they swing to wireless?
    >> Yes you are right.. they do need to re-authenticate.
    Regards
    Surendra

  • 2112 wlc + lap 1262 problem

    Hello
    After connecting an AIR-LAP 1262 N to a WLC 2112 (shipped this week) i get a periodic disconnect from AP, heres the log output (debug)
    Nov 20 13:35:08 192.168.0.32 Cisco_62:bf:00: *Nov 19 13:25:14.126: %DTLS-5-ESTABLISHED_TO_PEER: openssl_dtls.c:559 DTLS connection established to 192.168.0.149
    Nov 20 13:35:08 192.168.0.32 Cisco_62:bf:00: *Nov 19 13:25:14.129: %CAPWAP-3-DUP_AP_NAME: capwap_ac_decode.c:1077 AP with same name AP588d.0937.c0f9 exist. Using default name AP588d.0937.c0f9 for this AP.
    Nov 20 13:35:09 192.168.0.32 Cisco_62:bf:00: *Nov 19 13:25:14.224: %DTLS-5-PEER_DISCONNECT: openssl_dtls.c:659 DTLS peer 192.168.0.149 has closed connection.
    WLC:
    Controller Summary
    Management IP Address
    192.168.0.32
    Software Version
    6.0.199.4
    Emergency Image Version
    System Name
    Cisco_62:bf:00
    Can someone give us any clue ?
    TIA
    Gianluca

    Hello,
    First of all Thanks a lot. In fact i suspected that a version 7 shipped with 1262 AP was not matching the 6.0.199.... and so on. I already tried before posting here to download that version.
                                                                     BUT
    (we are new to Cisco procedures) it seems that to download that fw version we MUST be entitled to some Tech Support Agreement (= PAY ?)
    Is that true ? (Isnt kind of strange that 2 very expensive / born to work togheter pieces like that does not work out of the box and we cant even get a fw upgrade ?)
    Maybe i am missing something ?
    Thanks again
    Gianluca

  • Connecting AP 1130ag to 2112 port

    I have been through the guides but cannot figure out this one.
    I have an 1130ag AP (LWAPP) connected into port 7 (Poe) and trying to get it to associate with the WLC 2112. It never does. Do I need to configure that port to allow the APs to access the WLC through it? Maybe DHCP is not being passed to the AP so it is not getting an address to communicate over network?
    When I connect the AP to my switch I have connected to port 1 (management port) of the 2112 it associates fine.
    I am wondering if I am missing a step somewhere.... The quick start guide shows it easy as 1,2,3 but not for me....
    Thanks,
    Ed

    Thanks for the reply!
    I did try what you suggested on your first post with creating a new Management interface on port 7 and assigning an IP to it, but it kept telling me that the IP conflicted with another interface. From what I gather you cannot assign an IP in the same subnet to the other ports. With the project I am building everything is just your typical small office network with one subnet and VLAN.
    I do have both required interfaces setup. The Managment Interface and the AP-Manager Interface. They each have their own IP assigned.
    The AP I was using had already been registered with the WLC through a remote switch connected to Port 1 of the WLC and came up fine but as soon as I connect it to the 2112 on port 7 it just sits there and goes through the normal startup procedure over and over. I also does this connected to any other normal non-PoE port on the 2112 as well using power brick on the AP. The link lights are green and the AP is definitely powered up.
    I went into the console and tried to watch for any LWAPP events with the debug option but nothing ever reports it as even trying.
    Thanks for the reply though.... This is frustrating me because according to the docs I have found you should be able to just plug it in and it should work. I thought maybe the controller wasn't passing DHCP through the 2112 ports that are not assigned to anything so that might be why why the AP is not communicating but I cannot seem to find anything related to that. From my understanding the remaining ports should act as a switch.
    Thanks again,
    Ed

  • WLC 2100 series Guest LAN not found

    Hi there
    I am unable to configure Guest LAN as in this link
    http://www.cisco.com/en/US/tech/tk722/tk809/technologies_configuration_example09186a00808ed026.shtml
    because my Cisco WLC 2112 version 7.0.240.0 does not have the option for Guest LAN. Is Guest LAN supported for WLC 2100 series? Any workarounds or suggestions?
    Thanks for your help
    DIego

    Diego,
    Wired guest access is not supported on WLC2106.
    Reference:
    http://www.cisco.com/en/US/tech/tk722/tk809/technologies_configuration_example09186a00808ed026.shtml#configs
    consider using a WISM, WLC4400, 3750 integrated WLC or a WLC5500

  • Design Help.... WLCs / HREAP?

    Here is my scenario...
    We have two offices and the each have a WLC 2112 and 1130ag APs.
    SITE A (Main Office):
    1 - WLC 2112
    4 - 1130ag APs
    IP: 192.168.0.x/24 (VLAN1)
    IP: 192.168.100.x/24 (VLAN10)
    VLAN10 is setup for the Guest wireless network using Web Auth and ACLs etc...
    SITE B (Branch Office):
    1 - WLC 2112
    2 - 1130ag APs
    IP: 192.168.1.x/24 (VLAN1)
    SITE A connected to SITE B via Private T1
    Each site also has their own internet...
    Okay, so what I want to do is basically setup each controller to back the other one up in case of a failure at either end.
    I tested HREAP and it worked great except SITE B clients receive an IP address that is on SITE A's network. They could surf the internet but it was going through SITE A's internet etc...
    I can't have that and the clients need to use the internet based out of their location and be assigned an IP from their local network.
    Is there a way to do this?
    Each site obviously had the same SSID which is fine or they can be different. It doesn't matter... I just want to make sure if one of the WLCs go off the air, the other one picks up the APs and the clients do not notice a difference nor do they receive an IP from the site that would be remote to them.
    Also I do not want each site to see the other's SSID if using different SSID's. I only want the SSID to be seen by clients at their respective site. They can use the same SSID and in fact i would like to do that, but not sure if that would work in this scenario.
    If this is unclear, please let me know. i am trying to describe this as best as possible...
    Thanks,
    Ed

    This is what you need to do. First of all, make sure the wlan ssid is set to local switching and that you use the same vlan on both sites. On the ap, I figured you already changed the ap from local to h-reap.... if not, then that is what you hvae to do. Then after the ap reboots and is back up, click on the ap and you will have a tab named h-reap. Click that and check the native vlan. Now the ap will be trunked so you need to make sure the ip of the ap is on a seperate vlan than the ssid's. The vlan the ap belongs to would be configured as native vlan on the trunk. On th eh-reap ap, set the vlan that will be the native vlan. exit out of that screen and go back to the h-reap tab. Now you will see the wlans that you specifed as local switching with a box in which you can specify the local vlan in which the user will get an ip address locally and will reside on. You will also see wlans that will not have the entry box, since you don't have local switching enabled. This means the traffic will tunnel back to the wlc it's joined with. This is why you fail one wlc and the ap goes to the other site... failover works, but users are getting address from the new site, which means you are not locally switched.
    Example
    Site A
    Management/AP Manager vlan 100 (native) 192.168.100.x
    H-REAP AP vlan 100 (native) 192.168.100.x
    * AP can be on a different vlan if you want
    Internal Users vlan 110 192.168.110.x
    Guest Users vlan 120 192.168.120.x
    Site B
    Management/AP Manager vlan 100 (native) 192.168.200.x
    H-REAP AP vlan 100 (native) 192.168.200.x
    * AP can be on a different vlan if you want
    Internal Users vlan 110 192.168.210.x
    Guest Users vlan 120 192.168.220.x

  • Hooking an external wifi antenna to a new mini?

    I am looking at putting a mac mini in my new camper, my old camper had a G4 tower witch I installed a PCI card that I could hook an external (outside) high gain (15db) antenna) to so that I could get internet in the camper. The new camper has a very small desk and I want to get the 23" LED display mount it to the wall and hang the new mini on the wall next to it so that I have plenty of desk space, how would I connect an external antenna to it? USB? Thank you, Mike

    Wouldn't it be simpler to get a router that accepts antennas rather than cutting a hole in the mini case and soldering wires?
    My old SMC barricade had detachable antennas, I removed one of them and plugged in a signal booster and high gain omnidirectional antenna.

Maybe you are looking for

  • DVD Drive problem

    Is it just me or are people having a lot of problems with there DVD Drives. I had mine replaced back in April, barely used the drive, went to use it tonight and its ejecting discs again. Surely it can't be gone again. Can anyone give me any ideas at

  • Payment advice mailing

    hi to all, help me in this issue, how to use this bte SAMPLE_PROCESS_00002040 for sending mails to vendors how to activate this bte and change the code. thanks in advance kiran reddy Message was edited by:         kiran reddy

  • A question about JList (URGENT)

    I have a jtextfield that you can write anything on, another jtextfield that only accepts integers that are greater than 0 , a Jbutton, and a JList. I wanna add a listener for the JButton so that whenever it is pressed, the String in the first textfie

  • IPod Photo 30GB: Screen flickers white light & No display.

    The screen of my sister's ipod keeps on flickering with a plain white light, and there is still no display even though you plug it in an outlet or connect it to a pc. Could this be a problem regarding the ipod's battery? Or something to do with the i

  • Fetching but never finishing while trying to rebuild

    have tried to tried to rebuild my mailbox (mailbox was getting populated with multiple duplicate emails), but now, as I run "activity" it's fetching my mail--some 14000 messages, but it's getting hung up around half way through. and then just startin