It's pretty well detailed here: 
https://social.technet.microsoft.com/Forums/windowsserver/en-US/73c00321-496a-4898-ad5b-5ceb909610c7/snmp-oid-to-get-dhcp-scopes-from-2012-server


But I'm wondering if anyone has found a fix/solution to this.?  Basically, the 
proper SNMP OIDs don't seem to be registered after the 2012 R2 server gets 
rebooted.  When you use SNMPWALK.exe, the OIDs aren't there as expected...  If 
you uninstall SNMP, reboot the server, install SNMP again, then you can once 
against query the proper SNMP OIDs using SNMPWALK and it's perfectly fine.   
Very frustrating.   I can't seem to find a fix for it in google searches, just 
that it's a known issue others have encountered as well.  We use a monitoring 
tool to pull in information about our DHCP scopes using SNMP, but rebooting the 
server seems to break things, arg.   If you've stumbled across this yourself, 
or found a workaround/fix, let me know, thanks!


J






Reply via email to