ID: 1890
Title: cisco_temperature: Replaces cisco_temp_perf and cisco_temp_sensor
Component: Checks & Agents
Level: 1
Class: Bug Fix
Version: 1.2.7i1
This fixes an old issue with certain sensors not being detected on some
Cisco devices.
All services of cisco_temp_perf and cisco_temp_sensor will go unknown,
these hosts will need to be re-inventorized. Rules set to configure
cisco_temp_sensor will no longer apply to cisco_temperature, so these
services will need to be reconfigured.
ID: 1947
Title: agent_ucs_bladecenter: Monitors UCS Bladecenter via Web-API
Component: Checks & Agents
Level: 2
Class: New Feature
Version: 1.2.7i1
The new agent_ucs_bladecenter allows you to collect data from a
UCS Bladecenter via its web-API.
The following checks are currently supported
<table>
<tr><th>Check</th><th>Description</th></tr>
<tr><td>ucs_bladecenter_fans</td><td>Operate status of fans</td></tr>
<tr><td>ucs_bladecenter_fans.temp</td><td>Temperature at fans sensors</td></tr>
<tr><td>ucs_bladecenter_fans.temp</td><td>Temperature at chassis sensors</td></tr>
<tr><td>ucs_bladecenter_psu</td><td>Chassis voltage levels</td></tr>
<tr><td>ucs_bladecenter_psu.switch_power</td><td>Switch Voltage, Current and Power.</td></tr>
<tr><td>ucs_bladecenter_if</td><td>Traffic and bandwidth for Ethernet, Interconnect and Fibrechannel Ports.
Automatically groups portchannel interfaces.</td></tr>
</table>
Note: Portchannels for fibrechannel interfaces are not supported yet. It will be available soon.
ID: 2017
Title: Solaris-Agent: Prevent hanging agent in uptime section
Component: Checks & Agents
Level: 1
Class: Bug Fix
Version: 1.2.7i1
It happened running on a Solaris 8 zone, on a Solaris 10 LDOM, on Sun/Oracle T5
that the agent hung while processing the <tt>uptime</tt> section of the agent.
Many hanging truss and nawk processes were found, which can lead to a unresponsive
and/or crashed system.
The uptime section generating code has been changed and replaced by another mechanism.
Thanks to Clint Squires for analyzing the problem and providing a fix!
ID: 2016
Title: Fixed service discovery / monitoring on hosts which have only piggyback data (e.g. ESX VMs)
Component: Core & Setup
Level: 1
Class: Bug Fix
Version: 1.2.7i1
When having hosts configured which have no agent on their own ("No agent" configured via WATO),
but get piggyback data from another host, could not be inventorized. This has been fixed now.
So if you have, for example, an ESX server with several VMs, you configured each VM as host
in WATO and set <i>Agent type</i> to <i>No Agent</i>, you can now discover the services
based on the piggyback data again.
ID: 2015
Title: Fixed sending notifications for services with umlauts in names
Component: Notifications
Level: 1
Class: Bug Fix
Version: 1.2.7i1
Previous versions were unable to send notifications for services with
umlauts in their service descriptions. This issue has been fixed now.
If you miss notifications, take a look at the notification log at
<tt>var/log/notify.log</tt> (in your OMD sites) and search for
exception tracebacks.