DHCP Pool Percent In Use


Recommended Posts

  • 1 month later...
  • 2 weeks later...
  • LogicMonitor Staff

Hey @WillFulmer,

The two official DHCP datasources are now available from the repository, so you can check for them through Settings-> LogicModules-> DataSources-> Add-> From LogicMonitor Repository.

Alternatively, here are the names and locator codes:

  • Microsoft_DHCP_IPv4Server - K9AN49
  • Microsoft_DHCP_IPv4Scopes - 3LWA7T

Cheers,

Kerry

Edited by Kerry DeVilbiss
extra word
Link to post
Share on other sites
  • LogicMonitor Staff
On 1/9/2018 at 11:22 AM, mkerfoot said:

7EMGDK

I have modified the script so that it monitors all DHCP pools on Windows Server 2012 R2. It should work on any Windows machine with PowerShell v5+ though.

PoolUsagePercentage threshold = >=90,95,98

 

good reuse of code.

Would anyone else find what @mkqai created useful ? @WillFulmer @sawyer.lef @jamiemurphyit

If yes, I'll go ahead and file a ticket to get additional monitoring for Windows DHCP.

 

Link to post
Share on other sites
  • LogicMonitor Staff
1 minute ago, WillFulmer said:

Will DHCP servers be automatically discovered or must the Windows_DHCP be tagged on these specific devices?

 

@WillFulmer there's a PropertySource in our core repository called 'addCategory_Microsoft_DHCPServer' which will automatically add the categories.

You can also import it by locatorID GF2K94

Link to post
Share on other sites

I wasn't happy with the idea that this would only work on Server 2012, so I updated it to run on the collector instead of the monitored DHCP server. this also removes the need to add psconfig properties. The only catch is that all of your collectors must be running Server 2012 with DHCP management tools installed. The script will check and if necessary install the DHCP tools at first discovery. Let me know your thoughts. Solved a lot of issues for me.

DHCP_Scope: 4P2WKM

DHCP_Server_Stats: MT7GPT

Edited by Justin
Link to post
Share on other sites
  • LogicMonitor Staff
1 hour ago, Justin said:

I wasn't happy with the idea that this would only work on Server 2012, so I updated it to run on the collector instead of the monitored DHCP server. this also removes the need to add psconfig properties. The only catch is that all of your collectors must be running Server 2012 with DHCP management tools installed. The script will check and if necessary install the DHCP tools at first discovery. Let me know your thoughts. Solved a lot of issues for me.

DHCP_Scope: 4P2WKM

DHCP_Server_Stats: MT7GPT

 

@Justin the DHCP DataSources in core work for 2012 and newer, not just 2012. Not sure where you got that information. 

The reason we use the PropertySource is to identify a host and to apply appropriate categories prior to attempting to discover any instances. This removes a significant amount of load off the collector.

Link to post
Share on other sites
  • 1 month later...

I found the same thing and also elected to install the necessary module on our collectors rather than remote PS via WMI as the LM version uses.  I also found the published DS does not account for superscopes, so I did my own (based on code I found, which is credited :).  Sadly, there is no way to place linebreaks in the instance labels so superscopes labels tend to run off the edge of the column.

9AMZCD

Link to post
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.