7 EVA Release Notes

This document describes the changes made to the EVA application.

7.1 EVA - Event and Alarm Handler v2.0.2

7.1.1 Improvements and New Features

• A duplicated entry in a case-statement, i.e., a few lines of unused code, has been removed.
  

7.1.2 Fixed Bugs and Malfunctions

-

7.1.3 Incompatibilities With Event and Alarm handler v2.0.1

-

7.1.4 Known Bugs and Problems

-

7.2 EVA 2.0.1

7.2.1 Reported Fixed Bugs and Malfunctions

• The configuration parameter use_snmpea_log didn't work.
  Own Id: OTP-2117
  
• The SNMP trap alarmCleared in OTP-EVA-MIB was erroneously defined and sent. The currentAlarmEventIndex is sent in the trap now.
  Own Id: OTP-2118
  
• The MODULE-IDENTITY was erroneously named in OTP-EVA-MIB. It is now corrected to otpEvaModule.
  Own Id: OTP-2136
  

7.3 EVA 2.0.0

7.3.1 Improvements and new features

• The log functionality is made generic. Any log in the system can be controlled by the log service in eva.
  
• Any log can be filtered and formatted and transferred with FTP to a remote host.
  
• A timestamp is added to each event.
  
• The fault id for an alarm does not have to be generated by eva:get_fault_id/0.
  
• The default log argument in eva_log:start_link/1, eva_sup:start_link_log/1, eva_sup:start_link_log_snmp/3 and eva_log_sup:start_link/1,3 is now a 2-tuple {Name, WrapTime}. If the, old style is used, WrapTime defaults to 86400 seconds (i.e. 24 h)
  

7.3.2 Reported Fixed Bugs and Malfunctions

• The source code in the examples directory now compile!
  Own Id: OTP-1766
  
• Errors in logging was not handled correctly; the operational status was not updated.
  Own Id: OTP-1769
  

7.3.3 Incompatibilities with 1.0

• The generic log functionality is moved from the module eva_log to the module log.
  
• The generic SNMP log functionality is moved from OTP-EVA-LOG-MIB to OTP-LOG-MIB.
  

7.4 EVA 1.0

New application.