NetIQ Sentinel Readme

April 2013

This hotfix resolves specific previous issues. This document outlines why you should install this hotfix.

Many of these improvements were made in direct response to suggestions from our customers. We thank you for your time and valuable inputs. We hope you continue to help us ensure our products meet all your needs. You can post feedback in the Sentinel Community Support Forums, our community Web site that also includes product notifications, blogs, and product user groups.

For more information about this hotfix and for the latest readme, see the Sentinel Documentation Web site. To download this hotfix, visit the Novell Patch Finder Web site.

1.0 What’s New?

The following sections outline the key features and functions provided by this version, as well as issues resolved in this release:

1.1 Update to Java 7

Sentinel upgrades the Java Runtime Environment from version to version 1.7.0_17 because Oracle no longer supports version 1.6.

1.2 Removal of Event Source Overview Sync Report Data Definition

With Sentinel and later, Sentinel replaces the Event Source Overview Sync Report Data Definition (RDD) with Source Summary RDD. The Source Summary RDD stores only relevant events and therefore improves the reports performance.

Sentinel includes Sentinel Core Solution Pack 2011.1r4, which automatically replaces the RDD for reports created using the Event Source Overview Sync RDD with the Source Summary RDD. If you have custom reports that use the Event Source Overview Sync RDD, you need to update those reports to use the Source Summary RDD.

1.3 Plug-Ins Upgrade

Sentinel upgrades the following Actions, Integrators, and Solution Pack plug-ins. These versions include the latest software fixes, documentation updates, and enhancements for the plug‐in. For more information, refer to the specific plug-in documentation.


  • Event Forwarder 2011.1r1

  • Execute a Command 2011.1r1

  • Send E-mail 2011.1r2

  • Sentinel Link 2011.1r2

  • Send SMS 2011.1r1


  • File Integrator 6.1r3

  • Sentinel Link Integrator 2011.1r2

  • SMTP 2011.1r1

  • SNMP 2011.1r2

  • Syslog 6.1r4

Solution Pack

  • Sentinel Core Solution Pack 2011.1r4

1.4 Software Fixes

Sentinel provides software fixes for the following issues. For the list of software fixes and enhancements in previous releases, see the Sentinel Documentation Web site.

Sentinel Runs Out of Memory When a Large Number of Actions are Triggered

Issue: Sentinel runs out of memory when the actions trigger rate is more than the action execution rate. This issue occurs because there is no limit for the number of actions to queue up, which eventually causes actions to consume all of the system memory. (BUG 807834)

Fix: Sentinel now sets a limit for the number of actions that can be in queue. Sentinel also allows you to configure the number of threads that should simultaneously process actions. This number specifies the action execution rate. You can change the default values as necessary. The higher the value, the more memory is consumed.

To change the default values:

  1. Log in to the system as the root user.

  2. Open the /etc/opt/novell/sentinel/config/ file.

  3. Edit the sentinel.actions.executor.queue.size property to specify the desired value. This value specifies the number of actions allowed to be in the queue. The default value is 10000.

  4. Edit the sentinel.actions.executor.thread.size to specify the desired value. This value specifies the number of threads that should process the actions. The default value is 4.

  5. Restart the Sentinel server.

Sentinel Deletes or Overwrites Some System Files When the Disk Space is Full

Issue: If the Sentinel server is restarted when the disk space is full or when there are too many open files, Sentinel might delete or overwrite the and files. Deletion or modifications to these files alters the unique IDs contained in these files. (BUG 810854)

Fix: Sentinel now handles out of disk space and open files issues, and does not delete or overwrite these system files.

Sentinel Logs a Success Audit Event Even When the Action Fails to Execute

Issue: Sentinel generates an audit event flagged as Success even when the Execute Command action associated to a correlation rule fails to execute. (BUG 812522)

Fix: Sentinel now flags the audit event as Failed when the Execute Command actions fails to execute.

Sentinel Logs an Exception When you Modify a Scheduled Report

Issue: When you edit the schedule of a scheduled report, Sentinel logs the NullPointerException in the server log even though Sentinel edits the report schedule. (BUG 808990)

Fix: Sentinel no longer logs the exception when you edit a scheduled report.

2.0 System Requirements

You can upgrade to Sentinel from Sentinel 7.0 or later.

For information on hardware requirements, supported operating systems, and browsers, see Meeting System Requirements in the NetIQ Sentinel 7.0.1 Installation and Configuration Guide.

3.0 Upgrading to Sentinel

Download the hotfix from the Novell Patch Finder Web site. For information on upgrading to Sentinel, see “Upgrading Sentinel” in the NetIQ Sentinel 7.0.1 Installation and Configuration Guide.

If you upgrade Sentinel from 7.0 to, perform the following post-upgrade procedure:

If you installed Sentinel in a non-default location, you must run the following commands as the novell user:

ln -s

where $RPM_INSTALLATION_PREFIX is the location of the Sentinel installation.

3.1 Appliance Upgrade

If you are upgrading the appliance from Sentinel 7.0.1 or earlier, the upgrade fails in WebYaST because the vendor name for the patch has changed from Novell to NetIQ. You need to upgrade the appliance by using the zypper patch.

To upgrade the appliance by using the zypper patch:

  1. Back up your configuration, then create an ESM export. For more information, see Backing Up and Restoring the Data in the NetIQ Sentinel 7.0.1 Administration Guide.

  2. Log in to the appliance console as the root user.

  3. Run the following command:

    /usr/bin/zypper patch
  4. Enter 1 to accept the vendor change from Novell to NetIQ.

  5. Enter Y to proceed.

  6. Enter yes to accept the license agreement.

  7. Restart the Sentinel appliance.

4.0 Known Issue

NetIQ Corporation strives to ensure our products provide quality solutions for your enterprise software needs. The following issue is currently being researched. If you need further assistance with any issue, please contact Technical Support.

Issue: The Cisco SDEE Connector version 6r3 is not compatible with Sentinel and later because of the Java 7 update. (BUG 808312)

Workaround: The Cisco SDEE Connector version 2011.1r1 resolves the Java 7 incompatibility issue and will be available soon on the Sentinel Pre-release Plug-ins Web site. If this Connector is required in your environment, please verify the availability of the Connector update prior to applying this hotfix.

5.0 Contact Information

Our goal is to provide documentation that meets your needs. If you have suggestions for improvements, please email We value your input and look forward to hearing from you.

For detailed contact information, see the Support Contact Information Web site.

For general corporate and product information, see the NetIQ Corporate Web site.

For interactive conversations with your peers and NetIQ experts, become an active member of Qmunity, our community Web site that offers product forums, product notifications, blogs, and product user groups.