Sentinel 8.5.1.1 addresses some of the customer bugs as well as some existing Sentinel product bugs.
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.
No new features for this release.
Sentinel 8.5.1.1 includes software fixes that resolve the following issues:
Issue: Some modules of Sentinel API Reference documentation are truncated.
Fix: Now all of the Sentinel API Reference documentation modules are displayed at Help > APIs > API Reference.
Issue: Issues while authorizing any other Sentinel server version previous to 8.5.1.0 as data source on Sentinel 8.5.1.0.
Fix: Sentinel 8.5.1.1 now supports authorizing all Sentinel versions as data source.
Issue: Sentinel collector manager produces a core dump when ArcEventID value is 2147483647 and thus data collection stops during NetFlow data connection.
Fix: The data type for ArcEventID field is updated to BIGINT to hold values greater than 2147483647. This was done as part of a fix to avoid core dump generated by collector manager. If there is an existing datasync policy enabled with ArcEventID field, once you upgrade to 8.5.1.1 or later from the previous version then you must run the following command:
ALTER TABLE <tablename> ALTER COLUMN <Columnname> TYPE bigint;
The value of <Columnname> is arceventid, in this case.
For more information about hardware requirements, supported operating systems, and browsers, see the Sentinel System Requirements.
To purchase an enterprise license or upgrade your existing license, call 1-800-529-3400, email info@microfocus.com or visit https://www.microfocus.com/en-us/products/netiq-sentinel/contact.
For information about installing Sentinel 8.5.1.1, see the Sentinel Installation and Configuration Guide.
NOTE:All the hosts used for the Sentinel server and its components must be set up in two way DNS resolvable environment (Hostname to IP and IP to Hostname).
You can directly upgrade to Sentinel 8.5.1.1 from 8.3.1.0 and later versions of Sentinel. If you have a version older than Sentinel 8.3.1.0, then you must first upgrade to Sentinel 8.3.1.0 and then to Sentinel 8.5.1.1.
After upgrading to 8.5.1.1, the new Elasticsearch will not have any older data. If you have enabled the event visualization option, then upgrading from Sentinel 8.5.1.0 to Sentinel 8.5.1.1 does not require data migration for older Elasticsearch data. However, if you are upgrading from Sentinel 8.5.0.1 or lower versions, then to get the older data to Elasticsearch you must perform data migration. If you want to migrate the older data to Elasticsearch you can do it by using the data uploader tool. It can be done after the connection between all the nodes is made and both Elasticsearch and Kibana are running. For more information, see Migrating Data.
NOTE:To configure LDAP and SDK, you must use resolvable hostname instead of IP address.
WARNING:If you are upgrading from versions prior to Sentinel 8.3.0.0, you must manually assign the Send events and attachments permission 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.
For Traditional installation, see Upgrading the Operating System in 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, contact Technical Support.
The Java 8 update included in Sentinel might impact the following plug-ins:
Cisco SDEE Connector
SAP (XAL) Connector
Remedy Integrator
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 policies, see Support Policies.
Issue: After converting non-FIPS to FIPS mode in a specific case, while executing launcher_controlcenter.exe the SCC is not launching. It waits for a single sign-on authentication page and displays the message Lost Connection.
Workaround: Reboot the system.
Issue: In Sentinel Main > Storage > Health, the Storage Capacity Forecasting chart is not available. This is because Zulu OpenJDK does not include the necessary fonts.
Workaround: Use the following commands to install the fonts:
yum install fontconfig
yum install dejavu
Issue: Launching a Kibana dashboard displays the following message: No default index pattern. You must select or create one to continue.
Workaround: To set a Kibana index pattern as the default index pattern:
Select any of the following:
alerts.alerts
security.events.normalized_*
Click Set as Default.
Issue: The Select All <number of alerts> Alerts > Copy Alert Link option does not work in Firefox and Edge.
Workaround: Perform the following steps:
Manually select all the alerts on each page of the alert view using the check box that allows you to select all the alerts.
Click Copy Alert Link.
Paste it in the desired application.
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.
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-8.2.0.0-<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:
/etc/opt/novell/sentinel/config/configuration.properties
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.
Workaround: Install Collector Manager and Correlation Engine appliances in English. After the installation is complete, change the language as needed.
Issue: The Next and Back buttons in the appliance installation screens do not appear or are disabled in some cases, such as the following:
When you click Back from the Sentinel precheck screen to edit or review the information in the Sentinel Server Appliance Network Settings screen, there is no Next button to proceed with the installation. The Configure 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 no Back button to go to the previous screen to modify the network settings.
Workaround: Restart the appliance installation.
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.
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.
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: 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_installation_path>/etc/opt/novell/sentinel/config/.webserverkeystore.jks -destkeystore /<sentinel_installation_path>/etc/opt/novell/sentinel/config/.webserverkeystore.jks -deststoretype pkcs12".
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.
Workaround: Perform the following:
Click Sentinel Main > Integration > Threat Intelligence Sources.
Edit each URL to change the protocol from http to https.
Issue: In multi-factor authentication mode, if you log out of Sentinel Main 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.
Issue: The Kibana custom dashboard is not displayed when you upgrade from Sentinel 8.3 or earlier to Sentinel 8.3.1.
Workaround: Ensure that you re-create the custom dashboard after upgrading Sentinel.
Issue: After installing or upgrading Sentinel and when you launch Kibana for the first time, the conflict error message is displayed.
Workaround: Ignore the conflict error message as there is no functionality impact.
Issue: After upgrading to Sentinel 8.3, when you try to open Sentinel Appliance Management Console of the CE (Correlation Engine) or CM (Collector Manager) of HA (High Availability) servers, an error message Error 404 - Not found is displayed.
Workaround: For more information, refer to Micro Focus Knowledge Base document.
Issue: After upgrading to Sentinel 8.4, users with hide management permission of visualization still can see the Management tab on the Kibana page, but cannot access the features of the Management tab.
Issue: Existing users are unable to see any alerts on the Kibana page immediately, although permission is updated by the admin to see the alerts.
Workaround: You need to logout and login again when the user permission is updated.
Issue: When a non-default tenant user launches the visualization dashboard, an error message Forbidden is displayed. This error message is displayed, whenever the dashboard is launched by the non-default tenant user who has View-only permission for the Management option and there is no user with Edit permission for the Management option under that tenant.
Workaround: Ignore the error message as there is no functionality impact.
Issue: Remote Collector Manager (RCM) and Remote Correlation Engine (RCE) are not able to connect to the server when CRL is enabled, in RHEL.
Workaround: Upgrade the cURL version on the machine to 7.60 or above.
Issue: In the fresh installation of distributed setup, after enabling the Event Visualization, the FIPS, and the CRL services, the Remote Collector Manager (RCM) is not forwarding the events to the Sentinel Server.
Workaround: If either the Event Visualization and FIPS or the Event Visualization and CRL are enabled, then RCM forwards the events to the Sentinel server.
Issue: When you are upgrading the Operating System, from an older version to the latest version, incident reports fail with exceptions.
Issue: An exception is logged when the re-index operation runs for the first time.
Issue: When the system administrator runs convert_to_fips.sh in Sentinel 8.5 RCM/RCE appliance build, after providing correct credentials of the users in a continuous loop, the following error message is displayed:
ERROR: Failed to connect to <Sentinel server IP>: Failed to retrieve token for communication channel.
Workaround: Perform the following steps:
Exit from the script execution.
Go to <Sentinel RCM/RCE installation>/etc/opt/novell/sentinel/config/configuration.properties
Set the value of rest.endpoint.port to corresponding webserver port.
For example, rest.endpoint.port=8443
Rerun the convert_to_fips.sh
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:
Product documentation, Knowledge Base articles, and videos: https://www.microfocus.com/support-and-services/
The Micro Focus Community pages: https://www.microfocus.com/communities/
© Copyright 2001-2023 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 https://www.microfocus.com/about/legal.