Sentinel 8.2 SP2 resolves several previous issues.
Many of these improvements were made in direct response to suggestions from our customers. We thank you for your time and valuable input. We hope you continue to help us ensure that our products meet all your needs. You can post feedback in the Sentinel forum, our online community that also includes product information, blogs, and links to helpful resources. You can also share your ideas for improving the product in the Ideas Portal.
The documentation for this product is available in HTML and PDF formats on a page that does not require you to log in. If you have suggestions for documentation improvements, click the comment icon on any page in the HTML version of the documentation posted at the Sentinel Documentation page. To download this product, see the Product Download website.
The following sections outline the key features provided by this version, as well as issues resolved in this release:
Sentinel is now certified on the following platforms:
SUSE Linux Enterprise Server (SLES) 12 SP4 64-bit (traditional and appliance installation)
Red Hat Enterprise Linux Server 7.6 64-bit (traditional installation)
SLES 12 SP3 is now deprecated since SUSE will be removing support for SLES 12 SP3. Therefore, fresh installations of Sentinel 8.2 SP2 appliance now includes SLES 12 SP4.
Sentinel 8.2 SP2 includes software fixes that resolve the following issues:
Issue: In the (Bug 1118162)page, you can paste a password to the following fields: , , and .
Fix: You cannot paste to the following fields:, , and . This fix restricts users from pasting the current password in the field.
Sentinel server sets browser security headers in the server response. (Bug 1118173)
Issue: When you configure custom certificates for the (Bug 1125116)connector, there is no option to select a required certificate and import it.
Fix: Use Syslog Connector 2019.1r1 or later to select the alias such as webserver, intermediate, or root. This fix is available only when you configure custom certificates in > > . This fix is not available when you configure certificates using .
Sentinel REST API document now includes the explanation for possible state and status values of Data Collection methods. (Bug 1129261)
The Alert REST API displays the required alerts without displaying an exception. (Bug 1117842)
Issue: The Alert REST API does not consider the field parameter. When the Alert REST API includes the names of fields whose values need to be returned, the API does not display the field values. (Bug 1118799)
Fix: The Alert REST API displays the values of the specified fields for the required alerts.
The (Bug 1126506)button is now enabled only after an alert is assigned to the owner. Therefore, you cannot modify an alert without assigning it to the owner.
Issue: Java thread count of Sentinel and Collector Manager increases over time because the Java threads do not terminate after a task has been completed. (Bug 1128183)
Fix: Java threads of Sentinel and Collector Manager terminate as soon as a task is completed.
Issue: Event Visualization dashboard does not display events because the data type of two event fields (Bug 1131318)and do not match the mapping template of the Elasticsearch index. The section does not display the filters (BeginTime) and (EndTime).
Fix: The Event Visualization dashboard displays events. Thesection displays the filters (BeginTime) and (EndTime).
Issue: Events forwarded to syslog devices from Sentinel display only the first word of thename when:
Sentinel forwards events to syslog devices through Syslog Integrator in CEF.
name has two or more words.
Fix: Events forwarded to syslog devices through Syslog Integrator display the complete name of the device vendor.
For more information about hardware requirements, supported operating systems, and browsers, see the Technical Information for Sentinel page.
For information about installing Sentinel 8.2 SP2, see the Sentinel Installation and Configuration Guide.
You can upgrade to Sentinel 8.2 SP2 from Sentinel 8.2 or later.
IMPORTANT:If you have already upgraded to SLES 12 SP3 and run the post-upgrade utility, you must download the latest version of the post upgrade utility and run it again. This is important to ensure that upgrade to 8.2 SP2 and later works fine.
Download and run the latest utility from Micro Focus Patch Finder website.in the
NOTE:If you have installed Sentinel 8.2 appliance in high availability mode, the Sentinel installation does not contain the folders to launch the Sentinel Appliance Management Console. For more information about launching the Sentinel Appliance Management Console in high availability mode, see Upgrading to Sentinel 8.2 Patch Update 1 or Later.
WARNING:If you upgrade from Sentinel 8.2 or 8.2 P1 to 8.2 SP2, you must manually assign thepermission to non-administrator users who send events or attachments to Sentinel. Unless you assign this permission, Sentinel will no longer receive events and attachments from Change Guardian and Secure Configuration Manager.
You need not reassign this permission if you are upgrading from 8.2 SP1 to 8.2 SP2.
For information about upgrading to Sentinel 8.2 SP2, see the Sentinel Installation and Configuration Guide.
Micro Focus strives to ensure our products provide quality solutions for your enterprise software needs. The following known issues are currently being researched. If you need further assistance with any issue, please contact Technical Support.
The Java 8 update included in Sentinel might impact the following plug-ins:
Cisco SDEE Connector
SAP (XAL) Connector
For any issues with these plug-ins, we will prioritize and fix the issues according to standard defect-handling policies. For more information about support polices, see Support Policies.
Issue: The installer halts at the installation in progress screen and does not display the login screen even though the installation is complete.
Workaround: Reboot the virtual machine and launch Sentinel, Collector Manager, or Correlation Engine. (Bug 1134657)
Issue: In Hyper-V Server 2016, Sentinel appliance does not start when you reboot it and displays the following message:
A start job is running for dev-disk-by\..
This issue occurs because the operating system modifies the disk UUID during installation. Therefore, during reboot it cannot find the disk.
Workaround: Manually modify the disk UUID. For more information, see Knowledge Base Article 7023143.
Issue: When you upgrade to Sentinel 8.2 HA appliance, Sentinel displays the following error:
Installation of novell-SentinelSI-db-126.96.36.199-<version> failed: with --nodeps --force) Error: Subprocess failed. Error: RPM failed: Command exited with status 1. Abort, retry, ignore? [a/r/i] (a):
Workaround: Before you respond to the above prompt, perform the following:
Start another session using PuTTY or similar software to the host where you are running the upgrade.
Add the following entry in the /etc/csync2/csync2.cfg file:
Remove the sentinel folder from /var/opt/novell:
rm -rf /var/opt/novell/sentinel
Return to the session where you had initiated the upgrade and enter r to proceed with the upgrade.
Issue: Installation of Collector Manager and Correlation Engine appliance fails in MFA mode if the operating system language is other than English. (Bug 1045967)
Workaround: Install Collector Manager and Correlation Engine appliances in English. After the installation is complete, change the language as needed.
Workaround: Use a different browser to view or modify the visualization dashboard. (Bug 981308)
Issue: Theand buttons in the appliance installation screens do not appear or are disabled in some cases, such as the following:
When you clickfrom the Sentinel precheck screen to edit or review the information in the Sentinel Server Appliance Network Settings screen, there is no button to proceed with the installation. The button allows you to only edit the specified information.
If you have specified incorrect network settings, the Sentinel Precheck screen indicates that you cannot proceed with the installation due to incorrect network information. There is nobutton to go the previous screen to modify the network settings.
Workaround: Restart the appliance installation.
Issue: Sentinel displays the following message during start up in the server.log file:
Value for attribute rv43 is too long
Workaround: Ignore the exception. Although the message is displayed, Sentinel works as expected.
Issue: When there is a large number of events whose retention period has expired and SSDM tries to delete those events from Elasticsearch, the following exception is displayed in the server.log file:
java.net.SocketTimeoutException: Read timed out
Workaround: Ignore the exception. This exception occurs due to the time taken to delete the large amount of data. Although the exception is displayed, SSDM successfully deletes the events from Elasticsearch.
Issue: If you manually install and enable time synchronization in open-vm-tools, they periodically synchronize time between the Sentinel appliance (guest) and the VMware ESX server (host). These time synchronizations can result in moving the guest clock either behind or ahead of the ESX server time. Until the time is synchronized between the Sentinel appliance (guest) and the ESX server (host), Sentinel does not process events. As a result, a large number of events are queued up in the Collector Manager, which may eventually drop events once it reaches its threshold. To avoid this issue, Sentinel disables time synchronization by default in the open-vm-tools version available in Sentinel. (Bug 1099341)
Workaround: Disable time synchronization. For more information about disabling time synchronization, see Disabling Time Synchronization.
Issue: When FIPS 140-2 mode is enabled in Sentinel, using Windows authentication for Agent Manager causes synchronization with the Agent Manager database to fail. (Bug 814452)
Workaround: Use SQL authentication for Agent Manager.
Issue: The Sentinel High Availability installation in non-FIPS 140-2 mode completes successfully but displays the following error twice:
/opt/novell/sentinel/setup/configure.sh: line 1045: [: too many arguments
Workaround: The error is expected and you can safely ignore it. Although the installer displays the error, the Sentinel High Availability configuration works successfully in non-FIPS 140-2 mode.
Issue: In Internet Explorer 11, when you launch the dashboards:
Alert and Threat Hunting dashboard redirects to.
User Activity dashboard displays an error.
This issue occurs due to the URL length limitation in Internet Explorer 11. (Bug 1068418)
Workaround: Perform the following:
Launch Event Visualization dashboard.
Set the value of true.to
Issue: While using Keytool command, the following warning is displayed: The JKS keystore uses a proprietary format. It is recommended to migrate to PKCS12which is an industry standard format using "keytool -importkeystore -srckeystore /<sentinel_install_directory>/etc/opt/novell/sentinel/config/.webserverkeystore.jks -destkeystore /<sentinel_install_directory>/etc/opt/novell/sentinel/config/.webserverkeystore.jks -deststoretype pkcs12". (Bug 1086612)
Workaround: The warning is expected and you can safely ignore it. Although the warning is displayed, Keytool command works as expected.
Issue: In FIPS mode, when processing out-of-the-box threat Intelligence feeds from URLs, Sentinel displays the following error: Received fatal alert: protocol_version. This issue occurs because the out-of-the-box threat feeds now support only TLS 1.2, which does not work in FIPS mode. (Bug 1086631)
Workaround: Perform the following:
Click> > .
Edit each URL to change the protocol from http to https.
Issue: In multi-factor authentication mode, if you log out of (Bug 1087856)you do not get logged out of Sentinel dashboards and vice versa. This is due to an issue in the Advanced Authentication Framework.
Workaround: Until a fix is available in the Advanced Authentication Framework, refresh the screen to view the login screen.
For specific product issues, contact Micro Focus Support at https://www.microfocus.com/support-and-services/.
Additional technical information or advice is available from several sources:
© Copyright 2001-2019 Micro Focus or one of its affiliates.
The only warranties for products and services of Micro Focus and its affiliates and licensors (“Micro Focus”) are set forth in the express warranty statements accompanying such products and services. Nothing herein should be construed as constituting an additional warranty. Micro Focus shall not be liable for technical or editorial errors or omissions contained herein. The information contained herein is subject to change without notice.
For additional information, such as certification-related notices and trademarks, see http://www.microfocus.com/about/legal/.