This section describes installation known issues for UNIX endpoints.
Valid on AIX, and HP-UX
Symptom:
Uninstalling CA Access Control fails after I installed CA Access Control and UNAB using native installation and customized the installation directory to the same path on a nondefault location.
Solution:
Uninstalling CA Access Control corrupts and fails the UNAB installation. Uninstalling fails as both CA Access Control and UNAB have been installed on the same directory. While customizing native installation to a nondefault destination folder, we recommend that you concatenate the product name (AccessControl or AC) to the destination path CA Access Control installation.
When verifying RPM package installations you may receive some verification errors.
These errors do not indicate that there are issues with the functionality of the installed product and you can safely ignore them.
A client set up with non_ssl or all_modes cannot communicate with a server set up with fips_only communication mode.
The API libraries that CA Access Control supplies for Linux Z-series (s390x) are 32-bit.
CA Access Control does not supply 64-bit libraries for Linux Z-series (s390x).
On HP-UX, CA Access Control requires an updated patch level to install properly. We recommend the following OS patches:
PAM on Linux s390 and s390x does not work if the /lib64/libc.so.6 library on the host is older than the version CA Access Control PAM library was compiled with.
The library version should be 2.3.2 or later.
| Copyright © 2012 CA. All rights reserved. |
|