Logging in ClockWatch
Logs provide a detailed, permanent record of ClockWatch activity.
Date: Identifying source icon and date and time in yy-mm-dd hh:nn:ss format.
Source: Internet time setting, ClockCard setting, BIOS clock setting , GPS time setting (Star Sync), WWVB time setting (Radio Sync), client time requests (Client/Server) and unauthorized clock changing attempts (Sentry, Server, Client), are all included in the Action log.
Status: – result of the action.
Time Difference (seconds): – if clock was changed shows the number of seconds time setting. For clock locking shows the attempted time change.
Accuracy (sec/day): – for clock setting, shows the accuracy in terms of seconds/day.
Tip: You can resort by any column by clicking the column header.
The Clock Setting log provides a record of all the settings made on the system. If logging is enabled, a record is written every time server is contacted. The Clock Setting log provides a record that can be useful in a variety of ways:
Sample Clock Setting Log:
Synchronization Log 11/10/06 2:00:46 PM
Difference Accuracy Status Server
Client Logs (ClockWatch Server, ServerMP, Star Sync, Cell Sync)
ClockWatch Server records all ClockWatch Client requests for time synchronization in the Client Log. There are two client logs available: the Detail Log and the Summary Log.
Client Detail Log
The Client Detail Log shows the individual time requests from clients. The log shows every time a client asks the server for the time. the log shows the date of the request (Y-M-D), the time of the request, the time zone used (UTC is GMT), the time on the client (if available), the difference in seconds between the client and the server, and the IP address of the client making the request.
Client Summary Log:
The Client Summary Log reports a head count on all users (clients) accessing the ClockWatch Server, reporting their IP address, number of accesses, and the last time each of the clients accessed the ClockWatch server. Totals are also shown since the ClockWatch Server was last started. The Client Log file is available in the main ClockWatch program directory, under the name ClientLog.txt.
ClockWatch includes a detailed trace mode that provides detailed information about connection and communication information. This feature may be useful in debugging communication problems. You can run ClockWatch in the trace mode, which provides a detailed log to pinpoint problems, by simply adding the debug option to the command line when starting ClockWatch. Following these steps will allow your to run ClockWatch in the trace mode and view the resulting trace log file, DebugFile.txt.
Sample Trace Log:
Syslog (ClockWatch Client/Server)
ClockWatch Server and ClockWatch Enterprise can send events to a remote syslog server. Syslog servers, common in UNIX and Linux networks, gather messages from a variety of sources such as routers, switches, and any other syslog enabled application or device. The syslog server filters, stores, displays and forwards messages gathered locally and from the network.
SNMP (ClockWatch Client/Server)
ClockWatch can send trap events to a Simple Network Management Protocol (SNMP) manager such as HP’s OpenLook or IBM’s NetView. SNMP managers, common in some larger networks, poll and receive messages (traps) from a variety of sources such as routers, switches, and any other SNMP enabled application or device.A trap is an asynchronous message generated by ClockWatch and sent to the manager. To use the SNMP traps in ClockWatch you must define the address of the receiving manager, plus a community string that will be sent with the trap. Most SNMP managers ignore traps that don’t have the appropriate community string. The OID identifies the object's position in a global object registration tree . This is the ‘branch locator’ that identifies the ClockWatch application to the manger.
Agent tab – specify the SNMP agent settings.
Agent: Enter the name or IP address of the management system that will receive notification message from the SNMP agent acting on behalf of the specified community name. The selected SNMP management system is sent all the messages generated by ClockWatch.
Community: Enter the community name shared by the SNMP management system you are using as trap destination. A community mane acts as password that is shared by one or more SNMP hosts. The agent can only send trap messages to hosts with a known community name.
OID: Enter object identifier (.220.127.116.11….) to identify ClockWatch to the network management subsystem. Use a OID value known by the management system. All messages sent from ClockWatch will be sent with this OID.
· The Windows SNMP service must be installed and running for ClockWatch to send traps.
The logs provide a record of all the
time settings and significant events in ClockWatch.