Known Issues and Limitations

The known issues addressed in the JSA 7.5.0 Update Package 4 are listed below:

• It is possible for autoupdates to revert to a previous version of autoupdates after upgrading. This will cause autoupdate to not work as intended.

  After you upgrade to JSA 7.5.0 or later, type the following command to check your autoupdate version:

  /opt/qradar/bin/UpdateConfs.pl -v

• Docker services fail to start on JSA appliances that were originally installed at JSA release 2014.8 or earlier, then upgraded to 7.5.0 Update Package 2 Interim Fix 02 or 7.5.0 Update Package 3.

  Before you upgrade to JSA 7.5.0 Update Package 2 Interim Fix 02 run the following command from the JSA Console:

  xfs_info /store | grep ftype

  Review the output to confirm the ftype setting. If the output setting displays "ftype=0", do not proceed with the upgrade to 7.5.0 Update Package 2 Interim Fix 02 or 7.5.0 Update Package 3.

  See KB69793 for additional details.

• If your network connection is behind a firewall, the App Host is unable to communicate with your Console.

  To workaround this issue, remove encryption from the App Host and open the following ports on any firewall between your App Host and Console: 514, 443, 5000, 9000.

• After you install JSA 7.5.0, your applications might go down temporarily while they are being upgraded to the latest base image.

• When adding a Data Node to a cluster, they must either all be encrypted, or all be unencrypted. You cannot add both encrypted and unencrypted Data Nodes to the same cluster.

• Installing High Availability (HA) using JSA 7.5.0 GA can cause the partition layout to be built incorrectly. If you need to rebuild, reinstall, or install an HA appliance, do not use the JSA 7.5.0 GA ISO file. You can download and use the JSA 7.5.0 Update Package 3 ISO, or contact https://support.juniper.net/support/.

• After you install the kernel and the reboot is complete, the installer hangs on a hardware check involving Myver and MegaCli.