WLC 2125 - Lab setup

Good Afternoon,
I'm trying to setup a WLC lab here at work and I'm having a few issues. I'm trying to plug an AP directly into the WLC and I'm having issues with the AP getting an IP using the Internal DHCP server option.
Is this setup not going to work without a switch involved? Unfortunately, I don't have a switch available for use, but I'm trying to find anyway to setup this controller to have DHCP that can serve my AP an IP address to join the controller.
Any advice or help will be grateful. I can also provide my management and ap-manager information if needed. Also, I do have DHCP proxy enabled.
Matt Cooper

Hi.
the internal DHCP server is for clients. it can provide IPs to clients that connect over wireless. It does not provide IPs to anything on the wired side. So, its not going to work with your situation.
If you can't set up a switch and configure it with a DHCP pool to serve the APs what you can do is to configure a static ip on the AP.
check here: http://goo.gl/tEOdAa
Note: in the commands in the above link, if the keyord "lwapp" didn't work with you you try using the keyword "capwap". (using of either keywords depends on your AP model).
Regards,
Amjad

Similar Messages

  • Lab setup multiple SIP domains for federation

    I have been setting up multiple Lync 2013 lab environments and have a question about my external DNS environment. I have installed server 2012R2 on the host running the lab with its own domain (contoso.local). I have this server which hosts a separate domain,
    Hyper-V and a CA, this is what I am using for my external environment. The network IP is 10.0.0.0/16.
    I set up a server called vRouter that has 3 NICs. In Hyper-v I have 3 virtual switches configured. One for the External environment - 10.0.0.0/16 (not necessary for lab, setup to transfer needed files from internet to VMs), one for 192.168.1.0/24, and one
    with 192.168.2.0/24. The virtual router has RRAS installed and can route traffic between 192.168.1.0/24 and 192.168.2.0/24.
    My VMs for the lab are as follows.
    1test.local
    AD1.1test.local -192.168.1.100
    FE1.1test.local - 192.168.1.200
    Edge1 - 192.168.1.210int, 10.0.5.10ext
    2test.local
    AD2.1test.local -192.168.1.100
    FE2.1test.local - 192.168.1.200
    Edge2.1test.local - 192.168.1.210int, 10.0.6.10ext
    Both environments have users that can log into lync and message each other.
    When installing the Edge servers I used the same FQDN and IP for the external interface since all ports are open and firewalls have been disabled internally. I installed the internal certificate from the AD server which has CA role in each environment. On
    the external device I used the Host's CA to get certificates for both Edge servers. The Edge servers have 2 NICs one on their expected internal environment with no Gateway. And one on the external environment. These servers are not part of any domain. however
    I did add the contoso.local to the primary DNS suffix when domain membership changes under system properties. I then created the two following A records on the host computer (10.0.0.0\16 network, contoso.local) to be able to see router their external traffic.
    Edge1.contoso.local 10.0.5.10
    Edge2.contoso.local 10.0.6.10
    Both of these FQDNs are what is in my topology for the Access Edge service, Web Conferencing Edge Service, and A/v Edge Service with the same IP using different ports in both environments.
    Both environments are set up to support the other SIP domain. However when I try to add a user from the other domain I cannot communicate with that user nor see their presence.
    I looked over my external DNS settings and realized that I had not set a SRV record on the 10.0.0.0\16 network(external).
    I then realized that if I try to add the traditional _sipfederationtls._tcp.contoso.local I will have 2 conflicting entries.
    One for:
    _sipfederationtls._tcp.contoso.local - 10.0.5.10 (1test.local edge)
    and one for:
    _sipfederationtls._tcp.contoso.local - 10.0.6.10 (2test.local edge)
    Should I spin up another VM and make that a DC with a CA and trust it to the host computer, set up conditional forwarders. Something like Trust.local and correct the DNS, topology builder FQDN, and certificates on the second edge server?
    Edge2.trust.local
    Or can I add a new zone to my host computer then correct the DNS, topology builder FQDN, Certificates?
    Or am I missing another external DNS record on my contoso.local environment?
    Can I set up a CNAME entry that will mask the second edge server?
    Any input would be appreciated.
    Thanks

    If contoso.com is not a sip domain, then you won't need that DNS record at all.  Those records are autodiscover records that Lync uses based upon the sip domain. 
    So you'd need
    _sipfederationtls._tcp.1test.local
    and
    _sipfederationtls._tcp.2test.local
    What effectively happens, is when someone on the outside tries to IM
    [email protected], their Lync edge server will see the 1test.local and query the appropriate above record for it so it knows where to communicate.
    Please remember, if you see a post that helped you please click "Vote As Helpful" and if it answered your question please click "Mark As Answer".
    SWC Unified Communications

  • Exchange Server 2013 - Lab setup with internal emails only

    Hi,
    I'm new to Exchange Server 2013. I've started a POC on the product by setting up a Lab environment with one 1 AD server and 1 Exchange server (Both Windows 2012 R2). As this is a POC I just need the internal email communication. I don't want the mails to
    go over the internet. 
    I've completed the installation part and just started to configure Send/Receive connectors and got stuck with the question whether the connectors are required or not.
    Could someone please help me out in configuring internal email setup for Exchange 2013 lab setup.
    Regards,
    Nithin

    Hi,
    You need not to configure send/receive connectors for internal email.
    The following article for your reference:
    http://technet.microsoft.com/en-us//library/aa996395(v=exchg.150).aspx
    Default Receive connectors created during setup
    Certain Receive connectors are created by default when you install the Mailbox server role.
    Default Receive connectors created on a Mailbox server running the Transport service
    When you install a Mailbox server running the Transport service, two Receive connectors are created. No additional Receive connectors are needed for typical operation, and in most cases the default Receive connectors don't require a configuration change.
    These connectors are the following:
    Default <server name>   Accepts connections from Mailbox servers running the Transport service and from Edge servers.
    Client Proxy <server name>   Accepts connections from front-end servers. Typically, messages are sent to a front-end server over SMTP.
    Each connector is assigned a TransportRole value. You can use it to determine the role the connector is running in. This can be helpful in cases where you are running multiple roles on a single server. In the case of each Receive connector previously
    mentioned, their TransportRole value is HubTransport.
    To view the default Receive connectors and their parameter values, you can use the
    Get-ReceiveConnector cmdlet.
    Default Receive connectors created on a Front End Transport server
    During installation, three Receive connectors are created on the Front End transport, or Client Access server. The default Front End Receive connector is configured to accept SMTP communications from all IP address ranges. Additionally, there is a Receive
    connector that can act as an outbound proxy for messages sent to the front-end server from Mailbox servers. Finally, there is a secure Receive connector configured to accept messages encrypted with Transport Layer Security (TLS). These connectors are the following:
    Default FrontEnd <server name>   Accepts connections from SMTP senders over port 25. This is the common messaging entry point into your organization.
    Outbound Proxy Frontend <server name>   Accepts messages from a Send Connector on a back-end server, with front-end proxy enabled.
    Client Frontend <server name>   Accepts secure connections, with Transport Layer Security (TLS) applied.
    In a typical installation, no additional Receive connectors are required.
    Niko Cheng
    TechNet Community Support

  • WLC 2125 Upgrade

    Hi guys, I have a customer with a WLC 2125, with the version 6.0.199.4 and I will now upgrade to the version 7.0.250.0 but i wondering if it´s possible to make a backup for the old image, (i already download the configuration, but not the image) It´s is possible via console or web?
    Or it´s safety do the upgrade directly?
    Thanks
    Gonzalo

    Hi,
    As per my knowledge you can download old image from wlc. To get the same imgae its better to download from cisco.
    Here is the link:
    http://software.cisco.com/download/release.html?mdfid=282210723&flowid=7011&softwareid=280926587&release=7.0.250.0&relind=AVAILABLE&rellifecycle=ED&reltype=latest
    Regards
    Dont forget to rate helpful posts

  • WLC 2125 Rebooting

    Hi guys, we are having some trouble with a WLC 2125 with only 6 APs, but like 40 clients trying to associate.
    Version: 5.1.151.0
    The issue here is that the WLC reboots every 6 or 8 hours for no apparent reason. CPU is always at 0% - 1% and mem usage is at 35% - 40%. I've heard in this forums that this kind of WLC is not recommended for more than 20 clients.. so I don't know if we are over using the box.
    Maybe is an issue of software version or something, but in cisco.com there is only one version for this model of controller.
    I'm adding an attachment with the crash file:
    thanks!

    Reboots usually occur to one of three reasons on a 2100 series controller. First is power. The power supply is very susceptible to power spikes and brownouts. If the power spikes, the controller will reboot. Second, memory leaks on the controller. When using Web Auth the controllers CPU and memory resources are consumed fairly quickly. If the code does not effectively release those resources the system will eventually crash. There will be a record of this in the Tech Support section under management on the controller. Third and lastly, thermal issues around the controller. This will show in the event logs as a warning that the controller has exceeded it temperature threshold. If it gets too hot it will shut down completely.
    We are just completing the largest single deployment of 2100 series controllers in Cisco's history deploying of 200 2125s and a number of other 2100 series controllers and these are the major reboot issues we have seen.

  • CCNP Lab setup

    Hi Guys,
    I've to propose a cisco equipment list to setup a complete lab  for "CCNP R&S" course, this lab setup should be able to simulate the entire course contents/theories of the three modules including route, swithc and Tshoot).
    So what is the recommended lab setup to met the above requirment? Further we are looking forward to purchase new equipment, rather than considering the re-purbished equipments. Please advise.
    Regards,
    Suthakar

    Depends on your budget, of course.
    To cover the switch portion, you would want two 3560 models (3560, 3560G, 3560E, 3560X, depending on how much money you have to burn) and two 2960 models (again, G, PoE, etc) depending on what you're after.
    For routers, I haven't finished building my lab yet, but I'd want 1841's or 19xx's. Something that can run 15.x code. I think to really run anything, you'd want at least 4 routers, plus serial WIC-1T cards, serial crossover (DB-60) cables, and at least a 4 port serial module for one router. I'd probably want at least one big router, like a 3845 or 39xx.
    I'd probably want 4 18xx/19xx remote site routers, and 1 38xx/39xx hq site router. You can use GNS3 to simulate the routers though really, so most of my focus has been on switches.
    Good luck!
    Andy

  • Cmexpress7 lab setup

    what could be your suggestion of a lab setup for learning cm7 express..
    router=
    switch=
    phones=

    Hello,
    I have my CUCME 7x running on a 2801 router, with an AIM-CUE daughtercard for voicemail. I have a 3560 switch with PoE, and you can use any phone that the system supports. In my lab I have a couple of 7931's, some 7961's, and 7942's. It works like a charm.
    Hope that helped, if so please rate.

  • AAA Authorization Fail between WLC 2125 & LWAP 1042n

    In my Wireless environment, WLC 2125 is connected to a LWAP 1042n. The WLC is succesfully providing DHCP IP to the AP but is unable to discover it. All are connected. During debug mode following error message is encountered in WLC 2125, "AAA Authorization Fail....".
    Please suggest what to do.

    Here is a good doc that explains different errors:
    http://www.cisco.com/en/US/products/ps6366/products_tech_note09186a00808f8599.shtml

  • Lab setup- 2911/CME, aironet AP, and 7926

    I need to setup a lab for testing / demo 2 7926 phones to call each other.
    Do you have a simple sample CME config to accomplish this (ie, ephone command, realtive show commands to prove it connected or not)?
    Can I plug my AP directly into the ethernet port on the 2911? If not will any switch do?
    Also, there will be a VMXL server added later, where does this get connected physically?
    Let me know on this sample config what else I would need to setup the phones. Thanks so much.

    You have to plug your AP to PoE switch port configured as trunk port (assuming multiple vlan trunk to wireless network) if you are using it standalone mode (without WLC). If your switch is not POE then you need power injector to power the AP.
    Then you have to configure necessary SSIDs to phones to join via wirelessly & register to your CME. In DHCP scope for the phones you need to provide option 150 which is CME IP address.
    Do not know about VMXL server connetion.
    HTH
    Rasika

  • Cisco WLC 2125 configuration help

    So in a nutshell, from My computer I can ping all VLANS - everything seems to in workding order.
    when telnet to the HP 5406zl core routing switch I can ping all VLANs and other parts of the network
    But when logged into the Cisco wireless Lan Controller I cant ping VLAN 108 gateway IP (172.24.156.2 ) from the neighbour switch or other services on this VLAN
    for example cant ping the DHCP on this vlan from WLC.
    The neighbour switch can ping IP of the management interface created on the WLC
    WLC cant ping VLAN 108
    WLC can ping all other VLAN 102,104,106
    Not sure where the problem is ??
    Configure Dynamic Interfaces on the WLC for the Guest and Internal Users - DONE
    Create WLANs for the Guest and Internal Users - DONE
    Configure the 5406zl Layer 2/3 Switch Port that Connects to the WLC as Trunk Port allowing the relevant vlans i.e. management vlan, vlan 102 and Vlan 108 - DONE
    Configure the Switch Port that Connects to the AP to VLAN 102 - DONE
    configure virtual interface IP 1.1.1.1 - DONE
    Configure the Router for the WLANs - DONE
    LAP is registered to the WLC - DONE
    WLAN and SSID broadcast - OK

    Not at present it is not, the port on the 5406zl that the WLC is connected was setup as a trunk group and All VLAN tagged.  When I tried this I lost all connectivity to the WLC.  Is there something on the WLC that need changing also?.

  • WLC 2125 with 2x 1520 Mesh Points - Ethernet Bridging

    Hi - I'm looking for assistance with a new Mesh set up we are deploying, the solutions consists of:
    1x Wireless LAN Controller 2125
    2x 1520 AP/Mesh Points
    What we are trying to achieve is to bridge two networks together, I have followed the Cisco configuration guide and I simply can't get the traffic to cross from one side to the other. The WLC can see both 1520's on either side of the mesh network and I appear to have set it up right.
    Here is how everything is set up:
    - Local network (Class B, 10.0.0.0/16) connected to Port 1 on the WLC.
    - 1520 is connected to Port 2 on the WLC via g0/0 with an IP address of 10.0.3.110 (management network, 10.0.3.111 for the wlan-management network) - this is set up as the RootAP, with ethernet bridging enabled and the bridging group set to rsqmesh.
    - 2nd 1520 is around 800ft away set up as a MeshAP with ethernet bridging enabled and the bridging group set to rsqmesh. Small 5-port switch (non-cisco) connect to g0/0 on this 1520 with a device attached which has the IP of 10.0.3.37.
    All help is appreciated.
    Thanks,
    Craig.

    Bridging will not work if the RAP is directly connected to the controller. But CSCsk15792 is filed on this issue. If you put a switch between the controller and RAP traffic should start flowing.

  • Virtual WLC in LAB environment

    Hi!
    I have just installed a Virtual WLC at home for lab purpose. Now i want to connect one accesspoint to my wlc, but for now the WLC says "0 access points supported". 
    Can i somehow still use the evaluation licens and connect a accesspoint to the wlc? 
    /Lajja1234

    Hi Lajja,
    You have to enable the evaluation license in order to allow the AP to join.
    How to do it, please check here:
    http://www.cisco.com/c/en/us/support/docs/wireless/virtual-wireless-controller/113677-virtual-wlan-dg-00.html
    Hope it helps.
    Regards
    Dont forget to rate helpful posts

  • Pre-requisite for lab setup for database administration track.

    Hi, does anybody know what setup is required to participate in Lab for database administration track on Feb 11?

    The code you have in the rules file looks like it is incorrect. PCon would not be defined automatically and would therefore return zero. I think what you are actually looking for is something like:
    Call Hs.Con ("",HS.Node.PCon(""),"")
    Note that you can determine if the consolidation rules are used from you metadata under AppSettings. Look for the setting called ConsolidationRules. If you set this to Y, it uses the rules under Sub Consolidate(), if you set it N, it will automatically consolidate even if you have nothing under Sub Consolidate().
    Further, you can affect what gets consolidated in the metadata. Some of your accounts etc. may not be set correctly. Some things to check:
    For Accounts, make sure that IsConsolidated is checked and the AccountType is correct
    Also for Accounts, ensure that EnableCustom1Aggr ... is checked
    Finally, if the Entities have different currencies, check if you are getting data up to [Parent Total]. If not, the problem is your translation and not your consolidation.

  • UCCE 9.0.1 Lab Setup Sprawler

    Hi,
    I am trying to setup ucce 9.x lab as a Sprawler meachine. But when I try to run the UCCE Web admin page, I need to selct a deployment model. It doesn't let me select anything other than PCCE Lab only, which will cut down the configuration options in my lab. Anyone know if I want to use complete UCCE(not PCCE) in lab as a sprawler meachine, how can i do it?
    Thanks

    Hi Alejandro,
    This error will normally come if u try open domain manager without installing the base setup of ICM. try installing ICM base setup first and then run Domain manager. You should not see that issue.
    Hope this helps.
    Thanks,
    Ganapathi.S

  • Standalone ASA Lab setup context disabled

                       I've built a lab with two standalone ASA with no failover unit in firewall router and multiple context mode with failover active setup on each to make them act as primary and to simulate two separate Data Centers and DMZs. When I do a show failover on a context I get the message that shows the context disabled. What do I need to do make the context active on each standalone unit? 
    asalab03# sho fail      
    Failover Off
    Failover unit Primary
    Failover LAN Interface: not Configured
    Unit Poll frequency 1 seconds, holdtime 15 seconds
    Interface Poll frequency 15 seconds
    Interface Policy 1
    Monitored Interfaces 0 of 250 maximum
    asalab03# changeto con C
    asalab03/C# sho fail
    Failover Off
    Last Failover at: 12:56:49 UTC May 18 2012
            This context: Disabled
                    Active time: 0 (sec)

    Hellom
    Have you already assigned a  context to one of the failover groups?
    hostname(config)#failover group 1
    hostname(config-fover-group)#primary
    hostname(config-fover-group)#exit
    hostname(config)#failover group 2
    hostname(config-fover-group)#secondary
    hostname(config-fover-group)#exit
    hostname(config)#context context_name
    hostname(config-context)#join-failover-group {1 | 2}
    hostname(config-context)#exit
    You can share the configuration if this step is already done.
    Regards.
    Do rate all the helpful posts
    Julio
    Cisco Security Engineer

Maybe you are looking for