1 OS_MON Release Notes

This document describes the changes made to the OS_MON application.

1.1 OS_MON 1.3.1

1.1.1 Fixed Bugs and malfunctions

• Failover/takeover of the SNMP agent administering the MIB did not work, since the old implementation tried to delete a Mnesia table on a node which was not up and running (which always is the case at failover). Now the SNMP related Mnesia table is defined to have the local_content property.
  Own Id: OTP-2146
  Aux Id: seq1
  

1.2 OS_MON 1.3

1.2.1 Improvements and new features

• The disksup and memsup parts of os_mon is now supported on the WIN32 platform.
  Own Id: OTP-1670, OTP-1671
  
• The memsup part of os_mon is now supported on the VxWorks platform.
  

1.2.2 Fixed Bugs and malfunctions

• The problem that disksup sometimes could hang the entire node during startup is solved.
  Own Id: OTP-1658
  

1.2.3 Incompatibilities with OS_MON 1.2

• The SNMP Mib OS-MON-MIB has changed its name to OTP-OS-MON-MIB.
  

1.3 OS_MON 1.2

1.3.1 Improvements and new features

• Added the attribute loadCpuLoad in the SNMP MIB OS-MON-MIB, in the loadTable. It uses cpu_sup to fetch the load.
  Own Id: OTP-1190
  Aux Id: PH3-OTP-3:7
  
• Added new module cpu_sup. It supervises the CPU load in the operating system.
  Own Id: OTP-1191
  

1.4 OS_MON 1.1.1

1.4.1 Improvements and new features

• Adapted new application resource file possibility, i.e. module version is not specified any longer.
  

1.5 OS_MON 1.1

1.5.1 Improvements and new features

• Added os_sup, a solaris syslog facility.
  
• Added the OS-MON-MIB for SNMP monitoring of os_mon.
  
• Added functions for inspection of configuration parameters for disksup and memsup.
  

1.5.2 Fixed Bugs and malfunctions

-

1.5.3 Incompatibilities with OTP P1G

• Changed the output format from disksup:get_disk_data/0.
  

1.5.4 Known bugs and problems

-