| SNMP Traps
|Domain Time II Server|
Domain Time II Server can send notifications of its status to Network Management Systems and other SNMP-capable monitoring devices using SNMP Traps.
Note: If you see the Group Policy applied indicator in the lower-left corner of the applet,
there are settings on this page that are being overridden by an Active Directory Group Policy. Settings controlled by policy may be greyed-out or you may be otherwise prevented from making a change here.
See the Active Directory page for more information on using Group Policies.
Important: SNMP support depends upon wsnmp32.dll being present in the OS. All Windows versions except the initial release of Windows Server 2016 Nano Server have this
installed by default. To install Domain Time on Nano Server, you must install the SNMP trap support .dll before installing Domain Time.
See the Nano Server FAQ for more information.
Use this section to enable SNMP Traps.
Enter the SNMP community name and password used by your Network Management System (NMS), as well as its DNS name or IP address. Your community name and password must match the one in use by the receiving system.
As of v5.2.b.20190331, you may also specify a port number to which SNMP traps are sent in the Server field. Examples:
snmp.mydomain.com:1214 or [2002:410:1:1:2a0:69ff:fe01:b0f4]:2444. If the port number is not specified, the default SNMP trap port of 162 will be used.
Best Practices for SNMP include using a unique community name and hard-to-guess password on production systems.
The default community public should only be used for initial testing. Although Domain Time only sends outgoing trap information and is therefore
not susceptible to SNMP remote control vulnerabilities, you should still be mindful of SNMP security for the benefit of your other SNMP devices.
The settings in this section select which SNMP traps are sent by Domain Time.
SNMP v2 traps are generated whenever the selected event occurs. Keep in mind that SNMP Traps are sent via UDP, and are therefore not guaranteed to be delivered
by the network.
Although useful for raising performance alarms or other monitoring functions, you should not depend upon the SNMP trap data for critical logging of time synchronization events, particularly
if your logging is necessary for regulatory compliance. Use a product designed for more robust data collection, such as Domain Time Audit Server instead.
The Domain Time MIB File