Managing Event Histories and trapd.log

Pre-NNM 6.0 behavior would be to log all events to $OV_LOG/ trapd.log and to roll that to $OV_LOG/trapd.log.old when the file reached a predefined limit. That limit is set in $OV_LRF/pmd.lrf in the form of the parameter -$OV_EVENT;t;lsize, where l is the letter lowercase L and size is the rollover value in megabytes. When xnmevents starts, it scans both files. xnmevents also retains a separate log of events for each user in a file named xnmevents.username. This supports individual user event acknowledgement.

NNM 6.0 behavior differs remarkably from its ancestors. Events are not saved in trapd.log by default, but instead are stored in an event database. Fortunately, the logging to trapd.log can be reenabled ...

Get OpenView Network Node Manager: Designing and Implementing an Enterprise Solution now with the O’Reilly learning platform.

O’Reilly members experience books, live events, courses curated by job role, and more from O’Reilly and nearly 200 top publishers.