Please enter search query.
Search <book_title>...
Veritas Access Installation Guide
Last Published:
2019-09-30
Product(s):
Access (7.4.2)
Platform: Linux
- Licensing in Veritas Access
- System requirements
- Important release information
- System requirements
- Linux requirements
- Software requirements for installing Veritas Access in a VMware ESXi environment
- Hardware requirements for installing Veritas Access virtual machines
- Management Server Web browser support
- Required NetBackup versions
- Required OpenStack versions
- Required Oracle versions and host operating systems
- Required IP version 6 Internet standard protocol
- Network and firewall requirements
- Maximum configuration limits
- Preparing to install Veritas Access
- Deploying virtual machines in VMware ESXi for Veritas Access installation
- Installing and configuring a cluster
- Installation overview
- Summary of the installation steps
- Before you install
- Installing the operating system on each node of the cluster
- Installing Veritas Access on the target cluster nodes
- About managing the NICs, bonds, and VLAN devices
- About VLAN tagging
- Replacing an Ethernet interface card
- Configuring I/O fencing
- About configuring Veritas NetBackup
- About enabling kdump during an Veritas Access configuration
- Reconfiguring the Veritas Access cluster name and network
- Configuring a KMS server on the Veritas Access cluster
- Automating Veritas Access installation and configuration using response files
- Displaying and adding nodes to a cluster
- Upgrading the operating system and Veritas Access
- Performing a rolling upgrade
- Uninstalling Veritas Access
- Appendix A. Installation reference
- Appendix B. Configuring the secure shell for communications
- Appendix C. Manual deployment of Veritas Access
About enabling kdump during an Veritas Access configuration
During the Veritas Access configuration, the Veritas Access installer tries to enable kdump on your cluster node. To meet the Veritas Access software requirements, the installer modifies the /etc/kdump.conf and /boot/grub/grub.conf files by using the following options:
/boot/grub/grub.conf crashkernel = 512M-2G:64M, 2G-:256M
/etc/kdump.conf path /opt/VRTSsnas/core/kernel/ core_collector makedumpfile -c --message-level 1 -d 31