none
Blue exclamation icon (againsts IPV4) - what does it mean? RRS feed

  • Question

  • Blue exclamation icon

    Our DHCP server is on windows 2012 R2. I am seeing this 'blue exclamation' icon on IPV4. What does it mean? Microsoft documentations say "DHCP server alert. No addresses are available from server scopes because the maximum (100 percent) of the addresses allocated for use are currently leased. This represents a failure of the DHCP server on the network because it is not able to lease or service clients." (https://technet.microsoft.com/en-us/library/gg722802(v=ws.10).aspx#BKMK_1) . However, we have enough free ip addresses. (In use only 3 % and available 97 %). Also the above reference from MS is for Server icon.

    I am not sure whether mine is a server icon OR 'IPV4' icon. However, I could not get anything else from internet. Can someone tell me what this icon means pls?



    Thursday, November 2, 2017 4:29 AM

All replies

  • Do you have partner server configured for DHCP? Check the scope options are enabled on both servers and got replicated with each other.

    Regards, MC Manikandan

    Thursday, November 2, 2017 5:13 AM
  • HI Manikandan

    First thanks :-)

    Yes there is a partner. And the scopes are enabled and I replicate manually once a while (just in case). But even after a manual replication (Right click IPV4 and choose 'Replicate failover scopes"), I  still have the same 'icon'.

    Do I miss anything?

    Thursday, November 2, 2017 10:42 PM
  • Hi,

    Seems the DHCP server announce a incorrect alert, this might cause by the DHCP database crashed:

    1. Check if "Reconcile" the scopes could work, right click the DHCP scope, click "Reconcile";

    2. Check DHCP log in event viewer, see if there are related errors;

    3. Does the DHCP multihomed? Also check if clients could get IP address from the DHCP server.

    Best Regards,

    Frank


    Please remember to mark the replies as answers if they help and unmark them if they provide no help.
    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.

    Friday, November 3, 2017 10:19 AM
  • Compare the scope options for each scope on both servers. I believe the scope options in some scope is not enabled on one server which is triggering this alert. 

    Regards, MC Manikandan

    Friday, November 3, 2017 12:18 PM
  • Hi,
    Just checking in to see if the information provided was helpful. Please let us know if you would like further assistance.

    Best Regards,

    Frank

    Please remember to mark the replies as answers if they help and unmark them if they provide no help.
    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.

    Monday, November 6, 2017 2:07 AM
  • Hi Frank

    Sorry, hooked up with other projects. and so I could not come quickly.

    (1) Reconcile 'refuses' to work. I guess that could be a reason for this issue?.

    When I say 'refuses' to work, it means.

    I choose to reconcile all scopes. It would give the inconsistent records and would give an option to reconcile. But if I reconcile again, (expecting to see an empty list), I get the same ip addresses again. Tried multiple times, but results is the same.

    (2) Eventvwr has notbing interesting except the below. However this error was still there from ages ago.

    A BINDING-ACK message with transaction id: 9752 was received for IP address: 10.20.1.70 with reject reason:  (Reject Reason Unknown ) from partner server: unwrap21.fbu.com for failover relationship: unwpap21.fbu.com-unwrap21.fbu.com.

    DHCP server logs also do not contain any useful info. (of course as far as I can see)

    (3) No,. Just a single NIC and a single IPV4 ip address (statically assigned as you would expect)

    Monday, November 6, 2017 3:57 AM
  • HI Manikandan

    Did you mean the scope itself as disabled? (Few unused scopes are disabled, but I do not think it can cause it, what do you think?)

    I do not know how to disable a scope option. (So it may not have been done since it is a new DHCP server)

    Monday, November 6, 2017 4:00 AM
  • As above :-)
    Monday, November 6, 2017 4:00 AM
  • Hi,

    You could check the scope if it is active.

    Best Regards,

    Frank


    Please remember to mark the replies as answers if they help and unmark them if they provide no help.
    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.

    Monday, November 6, 2017 10:06 AM
  • Frank

    Should all scopes be activated? We have a few scopes 'deactivated' as per design. They are catered by a local DHCP server at remote sites. If the remote site server is not alive for any reason, then we will activate those corresponding scopes..

    Other point is that even when the scopes were 'activated' the blue exclamation mark was there.. (If you need some background; This is a new DHCP server. I am migrating the scopes from another DHCP server. We decided to do scope by scope migration since this DHCP server will replace many 'scattered' DHCP servers belonging to different business units).

    Tuesday, November 7, 2017 1:37 AM
  • Hi Frank,

    I know what is 'actvated' or deactivated scopes :-).  Manikandan mentioned about 'disabled scope options' which I asked for clarifications.

    Also I know what is a deactivated 'policy' is..

    I am afraid we are losing the focus and going sideways..

    Cheers


    Tuesday, November 7, 2017 1:45 AM
  • Hi,

    On both DHCP servers, would you please expand IPv4 tab and post the screenshot about all the scopes?

    Is the icon also showing on partner server?

    Best Regards,

    Frank



    Please remember to mark the replies as answers if they help and unmark them if they provide no help.
    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.


    Wednesday, November 8, 2017 9:08 AM
  • (1) PROD

    Thursday, November 9, 2017 3:06 AM
  • DR(failover partner)

    Thursday, November 9, 2017 3:06 AM
  • Hi,

    I noticed some scopes are not activated, and that is the cause of the blue icon.

    The icon is an alert indicating something happened(in our case, it is about the scopes which are not activated), so that we could safely ignore it.


    Best Regards,

    Frank


    Please remember to mark the replies as answers if they help and unmark them if they provide no help.
    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.

    Thursday, November 9, 2017 8:28 AM
  • Hi Frank

    Two things (though different)

    (1) I had this blue icon even when all the scopes were active. (I is a new DHCP server and I am migrating scope by scope from few different DHCP servers belonging to different biz units).

    (2) And even when I accept this happens when we deactivate at least one scope.. We have a requirement to keep some scopes deactivated. (Reason being that there are still remote sites with its own DHCP servers. They will not be migrated since they are on slow links. We only activate this scope when the local DHCP server is not available for any reason)

    So it looks like we have no way of 'escaping' this blue icon?

    ------------------

    Also Microsoft icon reference gives a pretty much serious reason for this blue icon.

    "DHCP server alert. No addresses are available from server scopes because the maximum (100 percent) of the addresses allocated for use are currently leased. This represents a failure of the DHCP server on the network because it is not able to lease or service clients." (https://technet.microsoft.com/en-us/library/gg722802(v=ws.10).aspx#BKMK_1)

    https://technet.microsoft.com/en-us/library/gg722802(v=ws.10).aspx#BKMK_1

    Friday, November 10, 2017 12:14 AM
  • Hi

    The article applies to Server 2008  R2. On Server 2012 R2, I’m not able to find any related documents about the explanation of the blue icon.

    When all the scopes are activated, have you checked if any scope is running out of address? If everything is OK, the icon could be safely ignored.

    And based on my test, the blue icon would show if there is deactivated scope. So that on your server, we could not escape the icon.

    Best Regards,
    Frank


    Please remember to mark the replies as answers if they help and unmark them if they provide no help.
    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.

    Friday, November 10, 2017 2:52 AM
  • Hi,
    Just checking in to see if the information provided was helpful. Please let us know if you would like further assistance.

    Best Regards,

    Frank

    Please remember to mark the replies as answers if they help and unmark them if they provide no help.
    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.

    Monday, November 13, 2017 9:25 AM
  • Hi,

    Was your issue resolved? 

    If you resolved it using our solution, please "mark it as answer" to help other community members find the helpful reply quickly.
    If you resolve it using your own solution, please share your experience and solution here. It will be very beneficial for other community members who have similar questions.
    If no, please reply and tell us the current situation in order to provide further help.

    Best Regards,
    Frank

    Please remember to mark the replies as answers if they help and unmark them if they provide no help.
    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.

    Wednesday, November 15, 2017 9:41 AM
  • I have the same problem

    i have several scopes that have exclamation mark and 1 without (good).

    server 2012 r2

    any help ?

    Tuesday, October 9, 2018 12:00 PM