Updating snmp

28-Mar-2019 12:08

Note that this data maybe a megabyte or more per day, so think about keeping only a few days worth, and only enabling statistics collection when needed as the number of writes to the SD card flash memory is limited.

To view the results from a Windows PC (so that you can run my NTP Plotter program or use the Meinberg NTP Monitor) you need to install and configure a package called SAMBA, which allows a UNIX file system to be seen by a Windows network client.

I used /usr/local/bin but I don't know Linux well enough to know whether that's the most appropriate directory.

One system had a whole lot of what appeared to be messages about unfound data, but all three systems work correctly and can be accessed remotely for monitoring the CPU temperature.

I could then use the Meinberg Time Server Monitor by adding \Ras Pi-1\ntp to the known nodes list within the program.

Later, I found that you can edit the DHCP configuration file, uncomment the first send host-name command, edit in your own wanted name, and comment out the default name: Notes based on: How do I monitor and/or control the temperature of the So C?

I do wonder what other variables you could monitor, as plotting NTP rate of change versus board or chip temperature would be an interesting exercise.I note that there are some values which record "85", which I recall is the maximum from this sensor.Ideally, the script would treat those values as an error, and perhaps try again until a more reasonable value is found, or report the value as zero. #--------------------------------------------------------------- # Raspberry Pi 4 - CPU temperature #--------------------------------------------------------------- Target[raspi4-CPU-temp]: .1.3.6.1.2.1.25.1.7.0&.1.3.6.1.2.1.25.1.8:[email protected] Max Bytes[raspi4-CPU-temp]: 100000 Max Bytes2[raspi4-CPU-temp]: 100000 Title[raspi4-CPU-temp]: CPU temperature on Raspberry Pi 4 Options[raspi4-CPU-temp]: gauge, nopercent, growright, unknaszero, noi YLegend[raspi4-CPU-temp]: Temperature C Short Legend[raspi4-CPU-temp]: C k MG[raspi4-CPU-temp]: , Factor[raspi4-CPU-temp]: 0.001 Legend2[raspi4-CPU-temp]: CPU temperature in C Legend O[raspi4-CPU-temp]: CPU temperature Page Top[raspi4-CPU-temp]: #--------------------------------------------------------------- If you are using a read-only file system, such as that employed by the excellent Pi-Star software (for amateur radio digital voice hotspot control), you may find that "pass" commands such as the above don't work, and you get a message to the effect that there is nothing at the OID when you check with snmpget.The configuration below allows anyone to read the SNMP data - you may want a more secure configuration.The changes below may not be ideal, but they are what I found to be necessary to get it working: For monitoring with MRTG, you can get the results shown here if you have a remote system running MRTG, with an include script something like this zip archive.

I do wonder what other variables you could monitor, as plotting NTP rate of change versus board or chip temperature would be an interesting exercise.I note that there are some values which record "85", which I recall is the maximum from this sensor.Ideally, the script would treat those values as an error, and perhaps try again until a more reasonable value is found, or report the value as zero. #--------------------------------------------------------------- # Raspberry Pi 4 - CPU temperature #--------------------------------------------------------------- Target[raspi4-CPU-temp]: .1.3.6.1.2.1.25.1.7.0&.1.3.6.1.2.1.25.1.8:[email protected] Max Bytes[raspi4-CPU-temp]: 100000 Max Bytes2[raspi4-CPU-temp]: 100000 Title[raspi4-CPU-temp]: CPU temperature on Raspberry Pi 4 Options[raspi4-CPU-temp]: gauge, nopercent, growright, unknaszero, noi YLegend[raspi4-CPU-temp]: Temperature C Short Legend[raspi4-CPU-temp]: C k MG[raspi4-CPU-temp]: , Factor[raspi4-CPU-temp]: 0.001 Legend2[raspi4-CPU-temp]: CPU temperature in C Legend O[raspi4-CPU-temp]: CPU temperature Page Top[raspi4-CPU-temp]: #--------------------------------------------------------------- If you are using a read-only file system, such as that employed by the excellent Pi-Star software (for amateur radio digital voice hotspot control), you may find that "pass" commands such as the above don't work, and you get a message to the effect that there is nothing at the OID when you check with snmpget.The configuration below allows anyone to read the SNMP data - you may want a more secure configuration.The changes below may not be ideal, but they are what I found to be necessary to get it working: For monitoring with MRTG, you can get the results shown here if you have a remote system running MRTG, with an include script something like this zip archive.The following steps are based in information from: If you want write access, replace "read only" with "writeable" as in the second example above.