Configuration Tips
Read what configuration problems you should fix to make sure everything works fine.
NetCrunch does many things automatically, but it needs your input in some places. For instance, it's necessary to provide proper credentials to access operating systems and valid SNMP profiles.
Resolve the Monitoring Issues
Monitoring Issues are problems related to the monitoring process. They require your attention. In most cases, they are related to invalid or missing credentials.
Fix Missing Device Types
NetCrunch uses Device Types to implement automatic monitoring. For example, if a device is not set to be a Windows type, Windows monitoring will not start or even be accessible for the node.
Open a network map and look for icons with a question mark, which indicates that they are missing a device type. NetCrunch automatically detects device vendors, which can help set the device type.
Only Windows (and other systems if added to Active Directory) and SNMP devices should have their device type set automatically. You must manually set their device type for other devices (those displayed as the "unknown device type").
Review the Settings page
Please check the Settings page to see what is enabled or disabled in your monitoring configuration.
For example, you can enable monitoring of the Physical Segments or NetFlow here.
Adding Custom Root Certificates to NetCrunch
NetCrunch uses node.js for secure SSL/TLS & HTTPS connection. Some of the certificate authorities might be not included. You can add additional root certificates to the external\Root Certificates folder in the NetCrunch Server data directory.
The certificate must be in PEM format.