Veritas InfoScale™ 8.0.2 Installation Guide - Linux
- Section I. Planning and preparation
- Introducing Veritas InfoScale
- Licensing Veritas InfoScale
- System requirements
- Preparing to install
- Mounting the ISO image
- Setting up ssh or rsh for inter-system communications
- Obtaining installer patches
- Disabling external network connection attempts
- Verifying the systems before installation
- Setting up the private network
- Setting up shared storage
- Synchronizing time settings on cluster nodes
- Setting the kernel.hung_task_panic tunable
- Planning the installation setup for SF Oracle RAC systems
- Preparing for deployment in a Secure Boot environment
- Section II. Installation of Veritas InfoScale
- Installing Veritas InfoScale using the installer
- Installing Veritas InfoScale using response files
- Installing Veritas Infoscale using operating system-specific methods
- Completing the post installation tasks
- Section III. Uninstallation of Veritas InfoScale
- Section IV. Installation reference
- Appendix A. Installation scripts
- Appendix B. Tunable files for installation
- About setting tunable parameters using the installer or a response file
- Setting tunables for an installation, configuration, or upgrade
- Setting tunables with no other installer-related operations
- Setting tunables with an un-integrated response file
- Preparing the tunables file
- Setting parameters for the tunables file
- Tunables value parameter definitions
- Appendix C. Troubleshooting installation issues
- Appendix D. Managing InfoScale digital signatures (Secure Boot environment)
Considerations for working with InfoScale in a Secure Boot environment
Consider the following while working with InfoScale software packages that contain digitally signed kernel modules in a Secure Boot enabled environment:
This feature is designed for environments that have Secure Boot enabled. If your systems do not use Secure Boot, you do not have to download and enroll the public keys and perform any additional steps.
Even if the kernel modules included in the InfoScale packages are digitally signed, there is no change in the InfoScale deployment process if Secure Boot is disabled.
In case of upgrades, for upgrades from an InfoScale version that does not support Secure Boot, you can proceed with the upgrades directly. No additional steps are required, presuming that you do not want to enable Secure Boot on your systems.
If you want to use Secure Boot in such an environment, then you must first upgrade InfoScale to the latest version. You can then enable the Secure Boot feature on all the systems. Once Secure Boot is enabled, you must download and enroll the InfoScale public key on each system.
This feature is supported on Linux platform only. The supported operating systems are RHEL 8, RHEL 9, and SLES 15.
The InfoScale public keys are valid for 2 years. Key expiry does not hamper any existing functionality in your production environment. However, you cannot install any new additional InfoScale packages that include signed kernel modules after the keys have expired. To do so, you must obtain new keys from the Veritas website and enroll them on your InfoScale systems.
InfoScale installation fails if Secure Boot is enabled but the InfoScale public key is not enrolled on the systems.
Similarly, after a successful InfoScale installation, if the InfoScale public key is deleted from the system, the InfoScale kernel modules fail to load and display a daemon error.
For example, the following error appears on the terminal when you try to load the
vxvmmodule:VxVM vxdisk ERROR V-5-1-684 IPC failure: Configuration daemon is not accessible