16.3. Monitoring via SNMP

Under Services > Monitoring > SNMP it is possible to configure whether and how the Intra2net system should provide data for monitoring via SNMP. This data can then be accessed and evaluated by a central SNMP monitoring service.

The Intra2net system does not offer information using the insecure SNMP versions 1 and 2, but only using the newer, secured version 3. User name, password and authentication protocol (MD5 or SHA1) must be specified for the authentication of the monitoring service with the Intra2net system.

It is sensible to have the monitoring service not only log on to the Intra2net system, but also encrypt all transmitted data. To do this, select an encryption password and an encryption method (AES or DES). It is recommended to use the secure AES if the monitoring service supports this. If Only encrypted data transmission is then enabled, the monitoring service must encrypt correctly in order to access the data of the Intra2net system.

If the Intra2net system is to be monitored from the local network, the firewall settings for the computer with the monitoring service must allow this. For example, a simple computer profile can be created and an additional service snmp can be added to it. If the Intra2net system is to be monitored over the Internet, set up a VPN connection between the monitoring server and the Intra2net system. The data can then be queried using these.

The Intra2net system uses SNMP to provide various information about CPU and memory usage, I/O load, hard disk usage, network utilization, number of error messages, Intra2net software version, and status of the RAID array. In order for this information to be usefully evaluated by a monitoring program, a description of the data is usually required as Management Information Base (short MIB). These are linked in the online help of the Services > Monitoring > SNMP page.