WLC dhcp scope issue

Hi,
We are facing this problem
we are using guest SSID with captive portal authentication.
We are using below step to conect to network
1) User will click on guest SSID & get IP from DHCP scope
2) User will open google.com & then it will redirect to authentication page - we need to provide userid/pass & then we will able to access internet
Problem
Assume user only do Step -1 , Then My dhcp scope is utilizing
How can we restrict the same to 'geneuine' user, any option/workaround ?
br/subhojit

I have to agree with e. Shortening theeaae will help.
But the kny way to keep people off the WLAN would be to use a PSK so that only authorized users can get on.
HTH
Steve

Similar Messages

  • Cisco WLC DHCP upgrade issues

    Hi,
    I've discovered an issue with our WLC 4400 series controllers when we do firmware upgrades (recently moved to 6.0.199) it seems to reset the dhcp server on the controller but the Access points still retain their old IP until the lease runs out (48hrs). This means that any AP's requesting a new lease often get an IP conflict for the first 48hrs after the upgrade and we experienced areas where AP's wouldnt connect.
    Is this a common issue and is there anyway to get the AP's to request a new address from the controller?
    thanks,
    Matt

    Hi Matt,
    When you do a WLC upgrade, a WLC reboot is required, this results in the DHCP lease table getting restarted as well.
    Solution:
    1-Setup an external DHCP Server to overcome this.
    2- Restart the access points, so they request a new IP address.
    This is mentioned on WLC release notes 6.0.199.0 that you are running, it is for clients, for the rule still applies:
    Link
    http://www.cisco.com/en/US/docs/wireless/controller/release/notes/crn6_0_199.html#wp581125
    Internal DHCP Server
    When clients use the controller's internal DHCP server, IP addresses are  not preserved across reboots. As a result, multiple clients can be  assigned the same IP address. To resolve any IP address conflicts,  clients must release their existing IP address and request a new one.
    The same also applies on newer releases such as 6.0.199.4 and 7.0.
    Have a good day.
    Serge

  • WLC DHCP & VLAN issue

    Hello,
    I configured on my WLC 5508 a new Interface & VLAN . The WLC act as DHCP Proxy.
    I enabled also Flex Connect local switching . Then I removed on my Switch under the
    VLAN settings the IP helper because as I know the WLC act as  IP helper.
    What is still not clear for me is where I have to insert the DHCP server adress
    on my WLC controller. Must I insert the DHCP server IP under my management Interface
    or where I have to enter the DHCP server IP.
    I tested this with the new VLAN interface and added the DHCP server IP but without success.
    Thanks for help.
    Regards

    Hi,
    I addedd an IP helper under the L3 configuration without success. Same, WLAN clients don´t get an IP .
    I configured following:
    add a new VLAN into the switch with layer 3 and addedd IP helper on the L3 switch.
    add the VLAN into the WLC controller wth a new SSID and Interface for this VLAN.
    Enabled Flex Connect under the SSID.
    Done a test with a wired client direct on a switch without problems.
    If I try to connect over the WLAN then the client don´t get an IP.
    Regards

  • WLC 5508 Internal DHCP server issues

    Hi,
    I am hoping to get your feedback around the dhcp issues I am facing with Two Centrally Switched Wireless LANs. I have tried to explain the setup and the problems below and would appreciate it if anyone can suggest a solution for the problems I am facing:
    The setup is as follows:
    - I have a WLC 5508 which has been configured with 4 SSIDs, out of which 2 are using Central Authentication and Switching.
    - I have an LWAP connected to the WLC in HREAP mode.
    - WLC is configured as the DHCP server for clients connecting to the SSID 'Guest'. For the rest, I am using external dhcp server.
    - Only one scope for Guest Interface is setup on the WLC. 
    Problems:
    1. As far as I know, for WLC to act as internal dhcp server, it is mandatory to have the proxy enabled, but the Clients connecting to SSID 'Internet' are
    unable to get an ip address from the external dhcp server, if dhcp proxy is enabled on the WLC. If i disable the proxy, it all works fine.
    2. DHCP does not release the ip addresses assigned to clients even after they are logged out.
    3. If a machine which was earlier connected to 'Guest' SSID connects to the 'Internet' SSID, it requests the same ip it was assigned by the WLC which it was assigned under 'Guest', but gets tagged with the Vlan configured on the management interface.  
    ************Output from the Controller********************
    (Cisco Controller) >show sysinfo
    Manufacturer's Name.............................. Cisco Systems Inc.
    Product Name..................................... Cisco Controller
    Product Version.................................. 7.0.116.0
    Bootloader Version............................... 1.0.1
    Field Recovery Image Version..................... 6.0.182.0
    Firmware Version................................. FPGA 1.3, Env 1.6, USB console 1.27
    Build Type....................................... DATA + WPS + LDPE
    (Cisco Controller) >show interface summary
    Interface Name                   Port Vlan Id  IP Address         Type        Ap Mgr        Gu                                                                            
    est
    guest                                        1    301      10.255.255.30    Dynamic   No              No                                                                            
    management                          1    100      172.17.1.30        Static          Yes            No                                                          
    service-port                              N/A  N/A      192.168.0.1       Static         No               No                                                                            
    virtual                                        N/A   N/A      10.0.0.1              Static         No               No                                                                            
    (Cisco Controller) >show wlan summary
    Number of WLANs.................................. 4
    WLAN ID  WLAN Profile Name / SSID               Status    Interface Name
    1        LAN                                    Enabled   management
    2        Internet                               Enabled   management
    3        Managment Assets          Enabled   management
    4        Guest                                  Enabled   guest
    (Cisco Controller) >show dhcp detailed guest
    Scope: guest
    Enabled.......................................... Yes
    Lease Time....................................... 86400 (1 day )
    Pool Start....................................... 10.255.255.31
    Pool End......................................... 10.255.255.254
    Network.......................................... 10.255.255.0
    Netmask.......................................... 255.255.255.0
    Default Routers.................................. 10.255.255.1  0.0.0.0  0.0.0.0
    DNS Domain.......................................
    DNS.............................................. 8.8.8.8  8.8.4.4  0.0.0.0
    Netbios Name Servers............................. 0.0.0.0  0.0.0.0  0.0.0.0
    (Cisco Controller) >show interface detailed management
    Interface Name................................... management
    MAC Address...................................... e8:b7:48:9b:84:20
    IP Address....................................... 172.17.1.30
    IP Netmask....................................... 255.255.255.0
    IP Gateway....................................... 172.17.1.1
    External NAT IP State............................ Disabled
    External NAT IP Address.......................... 0.0.0.0
    VLAN............................................. 100
    Quarantine-vlan.................................. 0
    Active Physical Port............................. 1
    Primary Physical Port............................ 1
    Backup Physical Port............................. Unconfigured
    Primary DHCP Server.............................. 172.30.50.1
    Secondary DHCP Server............................ Unconfigured
    DHCP Option 82................................... Disabled
    ACL.............................................. Unconfigured
    AP Manager....................................... Yes
    Guest Interface.................................. No
    L2 Multicast..................................... Enabled
    (Cisco Controller) >show interface detailed guest
    Interface Name................................... guest
    MAC Address...................................... e8:b7:48:9b:84:24
    IP Address....................................... 10.255.255.30
    IP Netmask....................................... 255.255.255.0
    IP Gateway....................................... 10.255.255.1
    External NAT IP State............................ Disabled
    External NAT IP Address.......................... 0.0.0.0
    VLAN............................................. 301
    Quarantine-vlan.................................. 0
    Active Physical Port............................. 1
    Primary Physical Port............................ 1
    Backup Physical Port............................. Unconfigured
    Primary DHCP Server.............................. Unconfigured
    Secondary DHCP Server............................ Unconfigured
    DHCP Option 82................................... Disabled
    ACL.............................................. Unconfigured
    AP Manager....................................... No
    Guest Interface.................................. No
    L2 Multicast..................................... Enabled
    (Cisco Controller) >show dhcp leases
           MAC                IP         Lease Time Remaining
    00:21:6a:9c:03:04    10.255.255.46    23 hours 52 minutes 42 seconds        <<<<<<< lease remains even when the client is disconnected.
    *********Example of Client connected to the right Vlan with an ip address from the incorrect interface. *************
    (Cisco Controller) >show client detail 00:21:6a:9c:03:04
    Client MAC Address............................... 00:21:6a:9c:03:04
    Client Username ................................. N/A
    AP MAC Address................................... a0:cf:5b:00:49:c0
    AP Name.......................................... mel
    Client State..................................... Associated
    Client NAC OOB State............................. Access
    Wireless LAN Id.................................. 2                 <<<<<<<<   'Internet' SSID
    BSSID............................................ a0:cf:5b:00:49:ce
    Connected For ................................... 319 secs
    Channel.......................................... 36
    IP Address....................................... 10.255.255.46      <<<<<<< IP address assigned from the 'Guest' Interface or dhcp scope on the WLC
    Association Id................................... 1
    Authentication Algorithm......................... Open System
    Reason Code...................................... 1
    Status Code...................................... 0
    Session Timeout.................................. 1800
    Client CCX version............................... 4
    Client E2E version............................... 1
    QoS Level........................................ Silver
    802.1P Priority Tag.............................. disabled
    WMM Support...................................... Enabled
    Power Save....................................... OFF
    Mobility State................................... Local
    Mobility Move Count.............................. 0
    Security Policy Completed........................ Yes
    Policy Manager State............................. RUN
    Policy Manager Rule Created...................... Yes
    ACL Name......................................... none
    ACL Applied Status............................... Unavailable
    Policy Type...................................... N/A
    Encryption Cipher................................ None
    Management Frame Protection...................... No
    EAP Type......................................... Unknown
    H-REAP Data Switching............................ Central       <<<<<<<<<
    H-REAP Authentication............................ Central       <<<<<<<<<<
    Interface........................................ management
    VLAN............................................. 100           <<<<<<<<<<< right Vlan
    Quarantine VLAN.................................. 0
    Access VLAN...................................... 100

    Hi All,
    I have a similar issue where Wireless clients are not receiving automatic addressing from an internal DHCP server. I have multiple interfaces configured on the WLC which are connected to separate VLANS. The manually specified DHCP primary server entry is the same on all interfaces. Some clients are able to authenticate and receive automatic IP configuration but some clients are failing the address assignment process. I have checked connectivity between the WLC and DHCP server, this is confirmed as working. When I carry out a "debug dhcp packet enable", I get the following outputs which seems as if the DHCP discover request from the client is skipped. Your thoughts and inputs on this are appreciated.
    DHCP Socket Task: Nov 07 11:16:09.174: 00:22:fb:7b:37:32 DHCP option len (including the magic cookie) 76
    *DHCP Socket Task: Nov 07 11:16:09.174: 00:22:fb:7b:37:32 DHCP option: message type = DHCP DISCOVER
    *DHCP Socket Task: Nov 07 11:16:09.174: 00:22:fb:7b:37:32 DHCP option: 116 (len 1) - skipping
    *DHCP Socket Task: Nov 07 11:16:09.174: 00:22:fb:7b:37:32 DHCP option: 61 (len 7) - skipping
    *DHCP Socket Task: Nov 07 11:16:09.174: 00:22:fb:7b:37:32 DHCP option: requested ip = 169.254.223.5
    *DHCP Socket Task: Nov 07 11:16:09.174: 00:22:fb:7b:37:32 DHCP option: 12 (len 13) - skipping
    *DHCP Socket Task: Nov 07 11:16:09.174: 00:22:fb:7b:37:32 DHCP option: vendor class id = MSFT 5.0 (len 8)
    *DHCP Socket Task: Nov 07 11:16:09.174: 00:22:fb:7b:37:32 DHCP option: 55 (len 11) - skipping
    *DHCP Socket Task: Nov 07 11:16:09.174: 00:22:fb:7b:37:32 DHCP option: 43 (len 2) - skipping
    *DHCP Socket Task: Nov 07 11:16:09.174: 00:22:fb:7b:37:32 DHCP options end, len 76, actual 68
    *DHCP Socket Task: Nov 07 11:16:09.174: 00:22:fb:7b:37:32 DHCP Forwarding DHCP packet (332 octets) packet DHCP Socket Task: Nov 07 11:16:09.174: 00:22:fb:7b:37:32 DHCP option len (including the magic cookie) 76
    Thanks,
    Raj Sandhu

  • Internal DHCP scope for AP on WLC 7.0 (on diff subnet)

    hi All,
    I would like to know if it is possible to assign dhcp pool on a different subnet to the WLC management interface?
    Eg: Management Interface is on 172.16.4.100 /24
    I would like to use the WLC Internal DHCP to assign IP to my APs on the a different range 172.16.2.x /24
    Is that possible?
    I  have tried assigning dhcp scope for the AP within the same subnet as  the management interface and it works. But that is not my requirement
    Apparently i need my AP to be sitting on a different vlan
    please advise

    No its not possible.. this works only if the AP and the WLC management interface is in the same subnet!! to ur issue we use something called as DHCP OPTION 43, google search DHCP OPTION 43 + cisco, the first link that u get wil help you!!
    Please dont forget to rate the usefull posts!!
    Regards
    Surendra

  • Multiple DHCP scopes on WLC 5508 (not showing leases?)

    I have 2 DHCP scopes set up on a wlc 5508, one for the AP's and another for a wlan, the leases for the AP's scope show up, but the one that the clients on the WLAN are on do not show up in the "show leases" is that a bug? normal? 

    Customers using Cisco Unified Wireless solutions have been reporting issues with the DHCP support provided on the Wireless LAN Controller (WLC). Some of these issues are software bugs or debugability problems. Others are due to lack of proper understanding on the DHCP implementation.
    This document describes the different DHCP operations on the wireless controller, which provides consistent and accurate information to customers in an effort to reduce the related customer issues and TAC cases.
    Please refer to the following link: http://www.cisco.com/c/en/us/support/docs/wireless/4400-series-wireless-lan-controllers/110865-dhcp-wlc.html

  • Monitoring DHCP scope on WLC 5508

    Hi,
    I have DHCP configured on the anchor controller but I don't know when DHCP scope is full on it. Do you have any idea or experience how to monitoring exhausted DHCP scope on WLC 5508?
    Regarding

    Ok but WLC can send syslog messages and base on this we can create an alarm. When DHCP scope is full on the WLC then controller inform us about this:
    DHCP Server: Nov 13 11:34:56.321: %DHCP-3-SEND_OFFER_FAIL: dhcpd.c:278 Unable to send DHCP offer. Could not allocate appropriate ip address from the scope
    *DHCP Server: Nov 13 11:34:56.321: %DHCP-4-ADDR_NOT_ALLOCATED: serverpacket.c:205 No IP addresses to give -- OFFER abandoned -- packet dropped
    *DHCP Server: Nov 13 11:34:52.416: %DHCP-3-SEND_OFFER_FAIL: dhcpd.c:278 Unable to send DHCP offer. Could not allocate appropriate ip address from the scope
    *DHCP Server: Nov 13 11:34:52.416: %DHCP-4-ADDR_NOT_ALLOCATED: serverpacket.c:205 No IP addresses to give -- OFFER abandoned -- packet dropped
    so If only I could detect this sentence from the syslog messages than I could create an alarm.

  • DHCP scope in WLC.

    hi all,
    please any one confirm ,is it possible to configure the DHCP scope for APs in WLC ?
    i am having 5508 controller connected to L3 switch..if it is possible what need to be done for that.
    thanks in advance.
    venkat

    Hi Venkat,
    WLC can lease IPs to APs only if we configure the pool in the same subnet as that of management interface.. having said that, its no possible to assign diff pool for AP which resides in diff subnet on the WLC.. We need to go for either Pool on the Layer 3 device or DHCP server.
    IP MAC binding is already enabled on the WLC by default.. AFAIK, this is more usefull for PASSIVE clients rather to active
    Lemme know if this answered ur question and please dont forget to rate the usefull posts
    Regards
    Surendra

  • DHCP scope increase and changes in wlc

    hi,
    i am using wlc 4402 with a mgt ip 172.26.150.x/24 and ap manager ip 172.26.150.x/24, my all ap get the ip address from dhcp . currently in dhcp server 172.26.150.3 to 254 dhcp scope is configured. at mysite some devices are configured like ipad,iphone or galaxy tab with mac binding in dhcp server. now this pool is almost full. i have a policy configured for these devices for mac binding is done in DHCP. to increase pool what are the changes i need to do in wlc. what are the changes i need to do in dhcp server . is policy made for mac binding in dhcp server will get affected by this ?
    regards
    rajat                  

    Hi Rajat,
    Use a /23 range ip address rather than using 172.26.150.x/24. So at first this change need to be carried out on the L3 device (which will the default gateway of the WLC managment interface). Accordingly the AP managment ip and ap manager ip's subnet mask is going to change from /24 to /23.
    Then ensure that on the dhcp server you expand the scope from /24 to /23. This is will not affect the MAC bindings as long as you are using the same ip range with a different subnet mask.
    Hope that helps
    Regards
    Najaf
    Please rate when applicable or helpful !!!

  • WLC DHCP issue with 6500

    Hi,
    I configured WLC as DHCP server and is working fine when connected to 3750 core switch. The AP's and clients are getting IP address.
    When the same WLC is connected to 6500 , the DHCP is not working from WLC . The same port of 6500 switch  is verified by connecting a 3750 switch as dhcp server and AP as well as clients are getting IP.
    DHCP snooping and port security is not enabled in the 6500 and the configuration is simple. The WLC is untagged and the 6500 port is a trunk port with 242 as native VLAN.
    Please help

    Dear Surendra,
    Please see the answers in line.
    1.As per your previous post, if we connect WLC to 3750 core everything works fine.. so in this case, i assume that we have INTERFACE VLAN on the switch and then the management interafce on the WLC are in the same subnet?? correct??
    "Yes , All are in the same Vlan . Interface VLAN and management interface are in same subnet."
    2. Similarly, if we swap the 3750 with 6500, it doesnt work.. in this case.. have you created the interface vlan on the 6500 in the same subnet as that of management interface of the WLC??
    " Yes, the 6500 has vlan interface without IP. The same way we configured 3750 "
    Or
    3.are we not swapping the 6500 and we are connecting the WLC to the WLC to the 6500 and then this 6500 to the 3750??
    "We connected WLC LAP to 3750 and the dhcp of wlc is working fine.. When WLC & AP connected to 6500 , the WLC DHCP is not working. We verified the 6500 port by coonecting 3750 as DHCP server and WLC is connected to 3750 and all were working fine. When WLC is directly connected to 6500 , the LAP is not joing to WLC. When static IP is given to LAP, the LAP joined WLC but the clients were not getting IP."
    4.Layer 2 means... interface VLAN on the switch and the WLC management and the AP DHCP pool are all in the same subnet. correct?
    "Yes all are in the same subnet"
    Thanks for your efforts.
    Regards,
    Savad

  • Windows 2008 R2 DHCP scope change - Netsh Exec not working

    OK, there seems to be a disconnect between Netsh documentation and how it actually works.  We are in the process of re-addressing ALL our DHCP scopes (joys of a buy-out) and using the steps outlined in numerous MS articles and Blogs etc... we should
    be able to use "Netsh dhcp server scope 192.168.1.0 dump > scope1.cfg"  then modify the cfg file with the new scope address (i.e. change all 192.168.1. to lets say 10.10.5.).  Then use netsh exec scope1.cfg (yes, the file modified) to
    create the new scope which would contain all the "stuff" the current scope has (reservations, options, etc).  
    Well, all we get is the response "The following command was not found:   |".  
    Environment is as follows:
    Account is a domain admin
    working on a RDP session on the DHCP server
    Server is Windows 2008 R2 (current functioning DHCP server)
    Using administrative CMD (elevated)
    have tried changing context into Netsh | DHCP | Server and default CMD - all "no go"
    supporting link from MS: http://technet.microsoft.com/en-us/library/cc772372(v=ws.10).aspx#BKMK_1
    There's a lot of discussions around this, but I haven't seen any response that says how to actually do it.  export/import won't work for us since we have to update the scope info.  With almost 100 scopes to update, we really need this functionality!
    (or similar method)
    Any assistance would be greatly appreciated.

    OK...  It seems the issue is with the dump file.  I actually got exec to run once with a dump file which wasn't modified.  The stupid part is it only ran one time, I could not duplicate it.   Since
    I've beat this thing to death and no one could offer any assistance (Hello MS?), I'm not wasting any more time on it.   Luckily, I was able to figure out an alternate method.  
    Looking at the dump file I realized all the lines are just a straight NetSh commands, which means all I needed to do is grab the lines and preface them with NetSh.  Like this...
    for /f "tokens=*" %a in ('type scope.cfg ^| find /i "dhcp"') do NetSh %a
    where scope.cfg is your dump file.   This runs perfect and seems to be the exact thing that exec should be doing.  I did flip the "SET STATE 1" to "0" so the scope was deactivated  (Don't forget to run it in an elevated
    prompt).
    Hope this helps someone else so they aren't spending days for nothing!

  • Client Authentication/Authorization via ISE & AD, Posture Registry Key, and mapped to specific DHCP scope by AD membership

    Hi Team,
    I'm currently working on a configuration entailing WLC and ISE where the customer wants a single SSID,and wants his wireless clients to authenticate successfully if they pass a registry key compliance.  Additionally, they want clients to received a different IP address or get mapped to a different DHCP scope based on the Microsoft AD group they belong too. for example:
    Client authenticating with registry key and in AD group ABC that passes authentication gets IP address or subnet for AD group ABC.
    Client authenticating with registry key and in AD group XXX that passes authentication gets IP address or subnet for AD group XXX.
    Clients---->WLC------>ISE-----> MS AD ( groups ABC, XXXX, YYY )
    currently using EAP-PEAP/MSCHAPv2
    Does anyone have any idea or pointers or can refer me somewhere that I can read on how to accomplish this?  Not sure on how to do the registry compliance check nor what attributes will allow me to map the client to a DHCP Scope based on this AD group membership? 
    Thanks...

    Do check cisco how to guides you will get step by step configuration of the current requirement
     

  • Is there a way for internal DHCP Scope to release scope addresses when the wifi client has disconnected?

    DHCP scope is configured on a WLC 5508.
    I'm checking if there' a way for WLC to clear the dhcp leasing when a user is diconnected from wireless?

    Unless the client sends a DHCP Release upon disconnect, which is not mandaded in the protocol, the lease will simply remain until it has expired.  If you're concerned with running out of leases, you only have 2 options. 
    1. reduce the lease time of your dhcp scope
    2. increase the network size to accomodate more usable addresses.
    There isn't a way to force a DHCP address lease to be "cleared" from the WLC simply because the client was disconnected.

  • How DHCP scope will work between two Wireless contoller

    Dear All,
                 I would like to inform you that we are going to deploy Wireless Network with redundancy of Wireless LAN Controller and we need to figure out how DHCP scope would work during fail over  any one of Wireless LAN controller and DHCP Server .I have two site where Two Differenet DHCP Server would be palced with different DHCP socpe.So My query is that if Site-A(according to attached diagram) DHCP Server and controller fails how Wireless  client will take the DHCP scope from Site-B(according to attached diagram) DHCP Server as it has been configured different DHCP Scope.Can any one tell me whether i can configure same DHCP Scope at Both Site's DHCP Server.
    Is there any way to configure same DHCP Scope for two sites.For your infromation client wants two Different DHCP Server with different scope for Two Site and how redundancy would be ensured if any one WLC or DHCP goes down.
    I am eagerly waiting for your reply as early as possible.Please help to figure out the solution.
    I am going to attached Sample Design for your reference.
    Thanks and regards
    Erfan

    Erfan:
    My query was that if one wireless client already associated
    WLC-A with one IP block of Location-A (DHCP Server) using SSID named TEST. If DHCP-A or WLC-A goes down then how that same client would associate with WLC-B and get the IP Block from Location-B (DHCP Server) using same SSID name TEST.
    In this case the clinets connected to the APs in location A will disconnect (if the WLC went down) and they have to connect again when the APs join WLC-B. They will get IP address from location B block then.
    If DHCP went down when new clinets try to connect the primary DHCP is down so they are referred to the secondary DHCP. connected clinets will disconnect only when their DHCP lease times out. They will try to renew but the DHCP server is not available. They will disconnect then and connect again and getting IP from B site.
    1. How we will create same policy for that two different block using same SSID.
    what policy? where?..etc?
    2. client would be connected with Access point but they will get the IP through VLAN interface of the Controller and we have to assign IP helper address in the interface vlan.So how the the client would get the IP block if we assign two IP helper address in the interface vlan in case of failure of DHCP and WLC of one location.
    3. If we assign two IP helper address then which DHCP Server will release the IP for client and we can make delay between two DHCP Server to release the IP address.
    If two IP helpers are configured the switch will send them both the client's request and they client receives two offers. The clients chooses one of the offers. Usually the clinet will accept the faster DHCP server to respond.
    If you are using the DHCP on the WLC then it is different. The WLC will always try to reach the primary DHCP server as long as it is reachable. If the primary DHCP is not reachable then it falls back to the secondary DHCP server.
    Note that when you use IP helper then you usually disable DHCP Proxy feature on the controller. Do you have it disabled?

  • How to check whether DHCP scope is fully leased/ exhausted on CUCM Publisher?

    Hi All,
    we have few new 7942 phones deployed and they are not registering.
    we suspect that dhcp scope configured on cucm pub do not have any free ips to assign.
    we need to know a way to confirm DHCP indeed is the issue.
    Any suggestions will be very helpful.
    Thank you

    Hi,
    I do not have any customers who run DHCP on CUCM servers but I would suggest that you look at using RTMT to collect log files from the DHCPMON service.
    You could also check out the blog below:
    http://bhatkoti.com/2009/02/16/how-to-check-call-manager-6x-5x-7x-dhcp-lease/
    The solution proposed is kind of neat but may not be something that you would be comfortable with.
    Hope this helps

Maybe you are looking for