Revised February 15, 1999
The Essentials 2.0 SyslogAnalyzer is incorrectly parsing the timestamp field of syslog messages. Syslog messages generated on mm/dd/1999 are stored in the database with a mm/dd/1998 timestamp. There is an exception for the Essential 2.0 users who have enabled service timestamp in their routers; service timestamp produces a year field in the timestamp.
SyslogAnalyzer uses a date formatter library from the JDK, and it is defaulting to 1998 (or the year that SyslogAnalyzer was started).
This defect has Cisco bug ID CSCdk79897 (registered customers only) . If you are a registered CCO user and you have logged in, you can view the bug details.
All the SyslogAnalyzer reports will be empty for 1999. This affects all the messages that have been processed since the beginning of 1999.
The available workaround at this time is to restart SyslogAnalyzer via the GUI interface or via the command line. Instructions for both methods are presented below:
To restart SyslogAnalyzer via the GUI interface, complete the steps below:
Login, go to Admin, and select System Admin.
Select Stop Process to stop SyslogAnalyzer.
After SyslogAnalyzer has stopped, go to Admin, and select System Admin.
Select Start Process to start SyslogAnalyzer.
To restart SyslogAnalyzer via the command line, issue the commands below:
> pdterm SyslogAnalyzer
> pdexec SyslogAnalyzer
A maintenance release of CiscoWorks 2000 will be available in early April 1999. At that time, the problem will be fixed.
For More Information
If you require further assistance, or if you have any further questions regarding this field notice, please contact the Cisco Systems Technical Assistance Center (TAC) by one of the following methods:
Receive Email Notification For New Field Notices
Product Alert Tool - Set up a profile to receive email updates about reliability, safety, network security, and end-of-sale issues for the Cisco products you specify.