Messages are logged in different formats depending on the output targets such as local log, e-mail notification, SNMP traps, and UDP notification.
All error messages log the component name on which the error is generated. To troubleshoot the error, refer to the component’s Reference Guide.
Example 1: Error related to Policy Management.
[DEBUG] [7/22/2007 3:42:45 PM]  [PolicyManager]  [Name = RM_dev, Guid = 271414163524d000190dbc6fa94272aa, Type = remote management policy, Version = 2]  .
To troubleshoot this error, see the ZENworks 10 Configuration Management Policy Management Reference.
Example 2: Error related to Remote Management.
[ERROR] [15-07-2007 12:44:16]  [Remote Management] [RemoteManagement.VNCEVENT_CANNOT_OPEN_EVENT] [Unable to open the <ZRMUserLoginEvent> event]  .
To troubleshoot this error, see the ZENworks 10 Configuration Management Remote Management Reference.
Messages are logged on the managed device and ZENworks Server in the following format:
[severity] [loggingTime] [userGUID] [componentName] [MessageID] [MessageString] [additionalInfo] [RelatedGUID].
For example, [DEBUG] [1/22/2007 12:09:15 PM]  [ZMD]  [refreshing QuickTaskRefresh(GeneralRefresh)]  .
An e-mail message consists of the message header and the message body:
The subject field in the e-mail can be customized as required by using keyword substitution macros:
Severity of the message.
Name of the component.
ID of the device at which the message is generated.
Time of the message generation.
Alias name of the device where the message is generated.
For example, if you want the subject line to display as “ERROR occurred on device Testifies at 4/1/07 5:31:01 PM”, then specify “%s occurred on device %a at %t” in the field.
The message body consists of the following fields:
Device Alias: Name of the device where the message is generated.
Device IP Address: IP Address of the device where the message is generated.
Error: [Date] Component name Message ID localized message string.
Additional Information: (Optional) Any additional information.
The SNMP messages consists of the following two parts:
The following fields are contained in the header:
Version Number: Specifies the version of SNMP used. ZENworks 10 Configuration Management uses SNMPv1.
Community String: Defines an access environment for a group of network-management systems (NMS).
The following fields are contained in the PDU:
Enterprise: Identifies the type of managed object generating the trap. ZENworks 10 Configuration Management uses 18.104.22.168.22.214.171.124.80.100.
Agent Address: Provides the IP address of the machine where the trap was generated.
GenerIc Trap Type: Contains the integer value 6. Type 6 is an enterprise-specific trap type, which has no standard interpretation in SNMP. The interpretation of the trap depends upon the value in the specific trap type field, which is defined by the Message Logger MIB.
Specific Trap Code: For enterprise-specific traps generated by ZENworks 10 Configuration Management, the values in the specific trap type fields are as follows:
For a severity level of MessageLogger.ERROR, the specific trap is 1.
For a severity level of MessageLogger.WARN, the specific trap is 2.
For a severity level of MessageLogger.INFO, the specific trap is 3.
Time Stamp: The time stamp indicating when the trap occurred.
Variable Bindings: Provides additional information pertaining to the trap. This field consists of the following name/value pairs:
For trap ID 126.96.36.199.188.8.131.52.184.108.40.206, the value is the device GUID.
For trap ID 220.127.116.11.18.104.22.168.22.214.171.124, the value is the device name.
For trap ID 126.96.36.199.188.8.131.52.184.108.40.206, the value is the component name.
For trap ID 220.127.116.11.18.104.22.168.22.214.171.124, the value is the time when the message was logged.
For trap ID 126.96.36.199.188.8.131.52.184.108.40.206, the value is the message ID.
For trap ID 220.127.116.11.18.104.22.168.22.214.171.124, the value is the probable cause.
The payload is a byte array with null-terminated delimiters such as \0 or 0 x 00 (hexadecimal) for each element. Each element’s data is presented as UTF-8 encoded strings and is explained below:
The first element is the ZENworks version information. For example, 10.
The second element is the value of severity of the message. The severity values are 4 for Informational, 6 for Warning, and 8 for Debug messages.
The third element is the message date. The date is not locally specific and is represented as a UTF-8 string. For example, 09-Mar-2008 14:15:44.
The fourth element is the user ID.
The fifth element is the component name.
The sixth element is the non-localized message ID.
The seventh element is the localized message string.
The eighth element is the additional information.
The ninth element is the probable cause URL.
The tenth element is the related GUID objects separated by commas.
NOTE:If the element does not have any data, it is represented as \0\0.