The following list contains the notes and the known issues that apply for the Flex Appliance 8.0 software:

• Hostname in filename not masked during sosreport obfuscation

  A binary configuration file collected in the sosreport tarball is named <hostname>.binconfig. DCv2 obfuscation does not rename this filename, so the hostname remains unmasked in the collected sosreport, even though data masking is enabled. This is by design in the underlying Red Hat sos report --clean utility, which does not rename filenames within binary configuration directories.

• On Intel-based Flex 5x6x appliances, the BMC may fail to read the IPMI Sensor Data Record (SDR) repository.

  When this happens, SDR reads time out (for example, Get SDR 0000 command failed: Timeout), and the Redfish chassis data for fans, temperatures, power supplies, and CMOS battery voltage is incomplete. Hardware monitoring may show the CMOS battery as Failed, or fans, temperatures, and power supplies as Pending or Awaiting Data. These statuses mean that the sensor data is unavailable. They do not mean that the hardware has failed. The appliance does not send Call Home, SMTP, or SNMP alerts for this condition.

• MPA requests remain in Pending review after the instance is deleted

  If you delete an application instance that has pending multi-person authorization (MPA) requests, such as requests to edit or delete the NAC service, the requests remain in the Pending review state in Request Management. If these requests are later approved, they fail because the instance no longer exists.

  Before you delete an instance, cancel or reject its pending MPA requests. If you have already deleted the instance, cancel or reject the remaining requests in Request Management.

• Incorrect note when an SSO user reviews a request to remove their own group

  When an SSO user reviews a multi-person authorization (MPA) request to remove a group that the user belongs to, the request preview shows the following note:

  You can't remove the group you belong to.

  This note is incorrect. After the required approvals, the request completes with the Done status and the group is removed.

• Shrinking MSDP storage for an application instance may only partially complete

  When you reduce the MSDP storage size of an application instance, the resize may complete for some MSDP volumes but fail for others. The instance ends up with a storage size between the original size and the new size. The appliance logs show an error similar to the following:

  ERROR: V-3-20343: cannot shrink /dev/vx/rdsk/vxosdg/<volume> - 
  blocks are currently in use.

  This issue occurs intermittently, even when the volume has enough free space for the new size.

  To fix this issue, retry the storage resize operation. If the resize fails again, contact Cohesity Technical Support.

• Active Directory domains with mismatched NetBIOS and domain names

  Flex Appliance requires the domain's NetBIOS name to correspond to its Active Directory domain name. If the NetBIOS name has been manually configured to differ from the domain name, Flex Appliance may not be able to resolve users and groups specified in the NETBIOS\username format. This limitation can affect user import, authentication, nested group resolution, and cross-domain lookups.

  For example:

  Domain name: primeforest.local

  NetBIOS name: PRIMEFOREST1

  In this configuration, Flex Appliance may not be able to determine that PRIMEFOREST1\username belongs to the primeforest.local domain when performing lookups.

  To fix this issue, configure Active Directory domains using the default naming convention where the NetBIOS name corresponds to the domain name.

  Note:

  This limitation applies only to environments where the NetBIOS name and domain name do not match. Environments using the default Active Directory configuration are not affected.

• Call Home proxy NTLM authentication not supported

  NTLM proxy authentication for Call Home has not been supported on Flex Appliance since 6.2 release. Flex Appliance 8.0 removes the legacy NTLM code from Call Home.

  Use HTTP Basic authentication or a proxy without authentication. Reconfigure NTLM-only proxies before upgrading.

• Response codes returned by DELETE API operations have changed

  The HTTP response codes that are returned by DELETE API operations have been corrected in Flex Appliance 8.0. DELETE operations that complete successfully without returning a response body now return 204. DELETE operations that start an asynchronous task now return 202, with a task ID in the response body that you can use to monitor progress. Some of these operations returned 200 in earlier releases.

  If your scripts or automation check for specific HTTP response codes from DELETE operations, they may fail after you upgrade. Update them to expect the corrected response codes. The API documentation, available from the Knowledge Base page on SORT, is updated with the response codes that apply to each operation.

• After an abrupt power cycle, the Flex Appliance Console may display a "Bad Gateway" error.

  To fix this issue:

  • Log in to the Flex Appliance Shell.

  • Run the support elevate command.

  • Verify the container status using the docker ps command.

  • If the peer-pod-peer container is in unhealthy state, restart the peer service using the systemctl restart peer command.

  • Verify that the container is in a healthy state using the docker ps command.

  • Log in to the Flex Appliance Console.

• When a VLAN tag that is created on a physical network interface is deleted, the associated network configuration is removed successfully but the corresponding VLAN tag entry may continue to be displayed in the Flex Web Console UI.

  This occurs because Flex Appliance consolidates network interfaces from multiple sources, which can cause a stale VLAN entry to remain visible on the Console after deletion. This behavior is not observed when the VLAN tag is created on a bonded interface.

  Wait for up to 15 minutes and refresh the Flex Appliance Console. The stale VLAN tag entry will be automatically removed.

• When the appliance turns on, you may receive the following false alerts if the services take longer than usual to start:

  V-475-130-30007: The metrics-node service is not in an optimal state.

  V-475-130-30009: The metrics-storage service is not in an optimal state.

  If you have not received a second alert after four hours, you can safely ignore these alerts.

• If you have more than 10 VLAN tags configured with an IPv6 network, instances may not start cleanly. To avoid this issue, do not configure more than 10 VLAN tags with an IPv6 network.

• If a server communicates with the appliance with a domain name that is not in the appliance hosts file, the server name is not masked in the logs.

• If you generate a Data Collect log package with data masking enabled, the private_map file that is included uses the same key value for multiple entries.

• Alerts are not currently sent for the metrics that can be set with the set alerts hardware-threshold command.

• During a firmware update, an issue can occur with the storage shelf controller that causes an update failure message to appear. If you see a failure message, it may have appeared in error, and the update may still have worked. Run the following command to confirm the firmware version:

  show hardware-health primaryshelf component=controller

• When you install application add-ons on an instance, the Flex Appliance Console lets you select different versions of the same OST plug-in. However, this configuration is not supported, and if you select more than one version of the same plug-in, the Install add-ons page shows duplicate entries. Only install one version of each OST plug-in on an instance. If you need to change the version of an OST plug-in that is already installed, first uninstall it, and then install the new version.