NetCrunch does many things automatically, but in some places it needs your input. It is necessary to provide passwords to monitor the operating systems, and to enter SNMP communities or passwords.
Here are a few tips that will help NetCrunch do what you expect from it:
Monitoring issues are tasks that require your attention – in most cases they are related to wrong or missing passwords. Please resolve them, so that NetCrunch can do its job.
It is important to set proper device types, because NetCrunch uses them for binding the devices to Automatic Monitoring Packs, and for the icon assignment on the network maps. For example, if the device type is Linux, NetCrunch automatically starts monitoring parameters of Linux OS.
In most cases, NetCrunch determines the device type automatically, based on information from Active Directory or SNMP. For other devices (those displayed as the "unknown device type") - you need to set their device type manually.
If you set up nodes monitoring one by one, you can easily lose control of those settings later on. To avoid this, we recommend using Monitoring Packs for tracking the same set of parameters on multiple devices. You can use existing predefined Monitoring Packs or create your own.
In the similar way, you can create a network view and set all monitoring parameters (alerts & reports) that will be automatically shared by every node in this view.
Please check the Settings page to see what is enabled or disabled in your monitoring configuration, for example enable monitoring of the Physical Segments or NetFlow.
