Manage 2.7.1

This document provides the release notes for Manage version 2.7.1. It describes the new capabilities and notable changes relative to the previous production release version 2.7

For the full capabilities of Manage 2.7.x as compared with Manage 2.6.x, please read in combination with the What's new in Ver 2.7 document.

Upgrade from previous versions

Manage 2.7.1 is released as a system upgrade pack that contains new features, system-level changes, and patches released since the Manage 2.6 release.

Confirm your current Manage version before applying this upgrade pack. An existing installation of Manage 2.6 is required for this upgrade pack.

For customers running earlier versions, please contact the Gemini Support team via the Support Portal or contact support@geminidata.com for more information on upgrading to the latest version.

What’s New in Manage 2.7.1

  • Update the Azure API support to ensure compatibility.
  • Fix multiple issues since Manage V2.7
  • Fix multiple security vulnerabilities found and validated before Mar 25, 2020.

Fixed Issues

  • MGR-3342: Cannot add multiple nodes into an existing cluster
  • MGR-3386: Can’t add a route on Azure
  • MGR-3401: Unable to get the latest artifact by using “sbox agent” command
  • MGR-3426: Destroy a standalone Splunk will cause an error
  • MGR-3431: The Splunk password which contains special characters will cause an error
  • MGR-3432: It will fail when adding an agent node into an existing adopted search head cluster
  • MGR-3433: Splunk version is incorrect when adding a node into Manage created clusters consist of agent nodes
  • MGR-3434: The site info will be lost after adopted a search head cluster
  • MGR-3436: Unable to produce a cache file when creating and AD search bind resource
  • MGR-3437: Unable to add a node into a remote Splunk Environment thru GUI

Known Issues

  • The Splunk Environments dashboard will need to rebuilt following an upgrade. This is achieved using Manifest files created during the upgrade. Follow this procedure, but not until ALL the Manage Appliances have been upgraded:
    • Obtain the Manifest file created to replicate the original nodes, stored in the following location; /opt/sbox/tmp/upgrade-26-to-271.
    • Copy the Manifest file to your local workstation.
    • Login to the Management Center and navigate to the Splunk Environments dashboard. Use the Add nodes button to import the Manifest file.
    • The environments will appear in the Unassigned Nodes panel. Organize them as required using the Assign to Environment button.
  • If a failover group has been created, the IP address in the failover group will disappear and shows 'None' after the upgrade. However, the failover function is still operational.
  • VMware Appliance: If there are iSCSI devices mounted, the boot-up process will fail unless you unmount all iSCSI devices BEFORE running the upgrade process.
  • A scheduled job will run immediately after being created in a Gemini Cluster.
  • The upload time display of a license is not formatted.
  • Splunk upgrade may fail when it is running on entry-level Azure instances.

Deprecated and Removed features

Deprecated features

  • None.

Removed features

  • None.

Important Notes

1. A reboot is required after upgrade. Backup the system and ensure it is offline before an upgrade. For VMware Appliances, ensure all the iSCSI devices are unmounted.
2. The upgrade process will take 5-10 minutes. During the upgrade, all Manage services will be stopped, allowing no operation of Manage.
3. Under no circumstance should a manual reboot be conducted during the upgrade. This will cause unrecoverable damage. Gemini appliance will reboot automatically following a successful upgrade.

Disclaimer

All third-party products mentioned within this document are the property of their respective owners.