Using Event Logs

If the NNM system itself is misbehaving, the process of troubleshooting requires you to collect data about the problem, and NNM may have clues about itself tucked away in the event logs. This means you should take advantage of the event log browser (for relatively recent events), archived trapd.log files (for pre-NNM6.0), or the event database as appropriate. If there’s not enough history, increase the size of the event database or trapd.log. Also check netmon.trace and snmpCol.trace.

If the NNM system is a management station, visit some of the collection stations to see if related information is available. If the NNM system is a collection station, visit its management station for related information, and check with other collection stations to see if they are having similar problems. This strategy is a component of the Kepner-Tregoe (K-T) troubleshooting methodology, which teaches you to collect additional information by looking where the problem does or does not exist.