Submit a ticketCall us

Webinar: Web Help Desk for HR, Facilities and Accounting Departments
This webinar will focus on use cases for HR, Facilities and Accounting.

Having a unified ticketing and asset management system for all the departments in your company can provide end-users with a seamless experience and make things easier for your IT team. Yet, with different business tasks and objectives, many departments don’t fully understand the capabilities of Web Help Desk and how the software can be customized for effective use in their departments.
Register Now.

Home > Success Center > Log & Event Manager (LEM) > LEM 5.3 Release Notes

LEM 5.3 Release Notes

Created by Caroline Juszczak, last modified by Caroline Juszczak on Mar 30, 2017

Views: 14 Votes: 0 Revisions: 4

 

Revised: October 25, 2011

Why Install this Version

Log & Event Manager Version 5.3 includes many improvements to first time evaluation and production users, support for Kiwi syslog server, updates to the Log & Event Manager Agent (including Java Runtime Environment), additional nDepth Export functionality, and many other improvements and updates.

 

Log & Event Manager Features and Improvements

Customers updating from Version 5.2 to 5.3 will note the following new features and improvements, organized by functional area:

  • Console
  • Manager
  • Appliance, CMC, and Upgrade
  • nDepth Log Storage/Search
  • Reports
  • Agent and USB-Defender
  • MSSQL Auditor

Console

 

  • Improved Console performance and reduced installation footprint.
  • Help accessed from SolarWinds.com rather than embedded in the Console.
  • Additional "Getting Started" and "Resource" widgets to assist with frequently accessed SolarWinds Resources and installation tasks.
  • For evaluation customers, integration of a Data Simulator to the Console.
  • Pausing filters could cause information leakage across filters.
  • ToolTips weren't always shown in nDepth dashboard widgets.
  • nDepth widgets did not support a versus field of Manager.
  • Extensive improvements to nDepth Export.
  • Configuring nDepth widgets with a large number of data points would result in unexpected behavior.
  • Flow Explorer was missing expected column headers.
  • License activation can be completed from the Console.
  • Non-Agent nodes display in the Console (and consume licenses).
  • Improvements to "Add Appliance" to streamline usability.
  • Added Rules to Alert Distribution Policy to filter alert types from being processed in rules.
  • Addition of a display icon for distinguishing multiple managers in nDepth result details.
  • Filters sometimes required sub-groupings where not expected.3

Manager

 

  • Licensing accounts for Non-Agent Nodes (i.e. remote data sources including syslog).
  • Improvements to the agent update infrastructure.
  • Improved support for DHCP IP address settings on the appliance.
  • Addition of SourceAccount field to WebTrafficAudit and HTTPClientAccess alert types.

Appliance, CMC, and Upgrade

 

  • Addition of appliance "product key" to encode support details.
  • Addition of virtual appliance boot screens and quick access to "Advanced Configuration" (CMC).
  • Improvement to CMC 'checklogs' command to view from end of log.
  • Resolved issues with several backup utilities with authentication.
  • Resolved nDepth backup issues.
  • Resolved issues with backup utilities detecting an existing backup already running even though it's not.

nDepth Log Storage/Search

 

  • Support for "NOT" in log search. 1

Reports

 

  • Additional categories for DISA STIGs and GPG13 added.
  • Resolved issues with environments with "DD/MM/YYYY" time displays.

Agent and USB-Defender

 

  • Addition of Linux 64-bit agent installer.
  • Update to agent startup scripts on non-Windows platforms. 2
  • Updated Java Runtime Environment on all platforms where a runtime is installed (everything except Mac OS X). Windows, Linux, and Solaris are 1.6.0_26; HPUX is 1.6.0_09; Solaris Intel is 1.6.0_15; AIX is an IBM-provided 1.6.0; Mac OS X uses the built-in installed JRE.
  • Updated Windows Event Log Reader DLL to address issues resolving user SIDs in some cases.
  • Integration with Kiwi syslog server to support agents reading Kiwi logs natively for all tools.
  • Addition of SourceAccount field to WebTrafficAudit and HTTPClientAccess alert types.

MSSQL Auditor

 

  • No changes from 5.2.

 

 

Installing and Upgrading SolarWinds Log & Event Manager

The following sections provide required information for installing and upgrading Log & Event Manager.

  • Installing Log & Event Manager
  • Supported Versions
  • Upgrading Log & Event Manager

Installing Log & Event Manager

SolarWinds Log & Event Manager consists of an appliance (referred to as "Manager" and "Appliance"), Console, and Reports Console. The LEM virtual appliance requires VMWare ESX/ESXi with vSphere 4.0 or later. The Log & Event Manager Console is an Adobe AIR application, compatible with Windows, Mac OS, and Linux. Log & Event Manager Reports is Crystal Reports-based and requires Windows.

For more information on installing Log & Event Manager, please refer to the Log & Event Manager Quick Start Guide and the Installation Guide.

 

Supported Versions

SolarWinds supports Log & Event Manager Versions 5.2 and 5.3, and legacy TriGeo SIM versions 5.0 and later.

 

Upgrading Log & Event Manager

The following sections provide general guidance for completing an upgrade to the latest version of Log & Event Manager, regardless of your current version.

Note: Detailed upgrade instructions are available in the Upgrade Instructions document in the Log & Event Manager software download on the SolarWinds Customer Portal.

General Upgrade Information

In general, you will need to download and unpack the Log & Event Manager software download(s), then continue by upgrading your appliances, Consoles, Reports, and other software as needed. To upgrade the Console, Reports Console, and other software, simply running the installers again will preserve your existing settings and upgrade to the latest compatible version. It's recommended to keep all your software on the latest version for compatibility and performance reasons. You can update your Log & Event Manager agents by running the appropriate installers, or upgrade Windows agents from the Log & Event Manager appliance remotely, configured in the Log & Event Manager Console.

You will need to provide your Log & Event Manager Appliance(s) with an accessible Windows network share or mounted DVD/CD media in order to upgrade. To run the appliance upgrade, log in to your appliance via the CMC at the appliance console or via SSH, then enter "manager" followed by "scriptupgrade" and follow the prompts to enable the appliance upgrade, then type "upgrade" and follow the prompts to begin the upgrade process.

Note: Upgrading your Appliance(s) to version 5.3 will take about 15 minutes, depending on resource capabilities. During this time your manager will be offline, agent/log data will continue to queue and be delivered after startup.

 

Other Known Log & Event Manager Issues

The following sections provide information related to previously unmentioned, known issues in Log & Event Manager.

  • Log & Event Manager Customers Must Install a New License
  • Uninstallation Errors After 5.3 Agent Upgrade
  • Issues Displaying IP/Hostnames from Agents

Log & Event Manager Customers Must Install a New License

This version of Log & Event Manager includes a new license for all LEM customers. Please access your activation key from the SolarWinds Customer Portal and activate from Manage > Appliance > License. If you receive an error ("Error retrieving license information") check your license key, network connection, or use the manual activation feature from the SolarWinds Customer Portal.

 

Agent Uninstallation Errors After 5.3 Agent Upgrade

Customers attempting to uninstall an agent that was originally installed on a previous version may receive one of two errors:

  • A popup with Exception "java.lang.IllegalArgumentException...": Resolved by using the remote installer rather than add/remove programs.
  • A JVM launcher error: Resolved by running the current agent installer, then uninstall.

Issues Displaying IP/Hostnames from Agents

Due to the changes in the Java Runtime Environment and licensing functionality, some agents may appear with a new IP and/or hostname combination. We've attempted to ensure this is the same IP/hostname that connects to the appliance, but there is the possibility on some platforms that this detection is less reliable. On Unix/Linux platforms, there is a known issue in the Java Runtime Environment that makes this detection even less reliable. A workaround is to place the expected/desired value in the /etc/hosts file, which will then be used and transmitted to the appliance.

 

Development and Support ID Fix Table

The following table provides the internal Development ID numbers and external support ID numbers for customer-reported issues resolved in this release.

Issue Link Support ID number Development ID number
1 00102734 MGR-243
2 00106440 AGENT-42
3 00104776 N/A

 

Legal

Copyright© 1995-2011 SolarWinds, Inc. all rights reserved worldwide. No part of this document may be reproduced by any means nor modified, decompiled, disassembled, published or distributed, in whole or in part, or translated to any electronic medium or other means without the written consent of SolarWinds All right, title and interest in and to the software and documentation are and shall remain the exclusive property of SolarWinds and its licensors. SolarWinds®, the SolarWinds logo, TriGeo®, ipMonitor®, LANsurveyor®, and Orion® are among the trademarks or registered trademarks of the company in the United States and/or other countries. All other trademarks contained in this document and in the Software are the property of their respective owners.

SOLARWINDS DISCLAIMS ALL WARRANTIES, CONDITIONS OR OTHER TERMS, EXPRESS OR IMPLIED, STATUTORY OR OTHERWISE, ON SOFTWARE AND DOCUMENTATION FURNISHED HEREUNDER INCLUDING WITHOUT LIMITATION THE WARRANTIES OF DESIGN, MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL SOLARWINDS, ITS SUPPLIERS OR ITS LICENSORS BE LIABLE FOR ANY DAMAGES, WHETHER ARISING IN TORT, CONTRACT OR ANY OTHER LEGAL THEORY EVEN IF SOLARWINDS HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES.

Microsoft®, and Windows 2000 Server®, Windows 2003 Server®, and Windows 2008 Server® are either registered trademarks or trademarks of Microsoft Corporation in the United States and/or other countries.

Last modified
10:40, 30 Mar 2017

Tags

Classifications

Public