There is a MIB file in the repository (tools/snmp/PROVISION-MIB.mib). It contains the description of the OID numbers provided by ProVision.
In order to test, you must first install snmpd:
apt-get install snmpd snmp-mibs-downloader |
On CentOS7, use the following command: yum install net-snmp net-snmp-utils |
Add the following lines in /etc/snmp/snmpd.conf:
view all included .1.3.6.1.4.1.36009 pass .1.3.6.1.4.1.36009 /usr/bin/php /var/www/html/[/var/www/html/[$ProVisionDir]/tools, etc]/tools/snmp/Provision.php |
Add the MIB file to the shared mib library:
ln -s /var/www/html/[/var/www/html/[$ProVisionDir]/tools/snmp/PROVISION-MIB.mib /usr/share/snmp/mibs/PROVISION-MIB.txt |
Restart the webserver:
systemctl restart snmpd |
Verify the SNMP is working:
snmpwalk -v 2c -m +PROVISION-MIB -c public 127.0.0.1 provisionStats |

|
|
These are OID numbers from which SNMP clients can gather information. They are directly provided by the OS:
NOTE: If the MySQL maximum connections limit is reached, then ProVision will not be able to respond to the SNMP Daemon, as it will not be able to connect to MySQL. Please keep this in mind when setting alert thresholds. |
ProVision SNMP KPIs can be configured to send trap events for the ProVision application. For the host system KPIs (CPU, RAM, etc.) the monitoring tool will need to be configured to poll the KPIs and then set the alert thresholds accordingly.
|