Veritas InfoScale™ 7.4 Installation Guide - Solaris
- 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
- Creating a root user
- Configuring LLT interconnects to use Jumbo Frames
- Creating the /opt directory
- Planning the installation setup for SF Oracle RAC and SF Sybase CE systems
- Making the IPS publisher accessible
- Preparing zone environments
- 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
- Uninstalling Veritas InfoScale using the installer
- About removing Veritas InfoScale
- Removing the Replicated Data Set
- Uninstalling Veritas InfoScale packages using the installer
- Uninstalling Veritas InfoScale using the pkgrm or pkg uninstall command
- Manually uninstalling Veritas InfoScale packages on non-global zones on Solaris 11
- Removing the Storage Foundation for Databases (SFDB) repository
- Uninstalling Veritas InfoScale using response files
- Uninstalling Veritas InfoScale using the installer
- 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
Disabling the abort sequence on SPARC systems
The topic applies to VCS.
Most UNIX operating systems provide a method to perform a "break" or "console abort." The inherent problem when you abort a hung system is that it ceases to heartbeat in the cluster. When other cluster members believe that the aborted node is a failed node, these cluster members may begin corrective action.
Keep the following points in mind:
The only action that you must perform following a system abort is to reset the system to achieve the following:
Preserve data integrity
Prevent the cluster from taking additional corrective actions
Do not resume the processor as cluster membership may have changed and failover actions may already be in progress.
To remove this potential problem on SPARC systems, you should alias the go function in the OpenBoot eeprom to display a message.
To alias the go function to display a message
- At the ok prompt, enter:
nvedit
- Press Ctrl+L to display the current contents of the nvramrc buffer.
- Press Ctrl+N until the editor displays the last line of the buffer.
- Add the following lines exactly as shown. Press Enter after adding each line.
." Aliasing the OpenBoot 'go' command! " : go ." It is inadvisable to use the 'go' command in a clustered environment. " cr ." Please use the 'power-off' or 'reset-all' commands instead. " cr ." Thank you, from your friendly neighborhood sysadmin. " ;
- Press Ctrl+C to exit the nvramrc editor.
- To verify that no errors exist, type the nvrun command. You should see only the following text:
Aliasing the OpenBoot 'go' command!
- Type the nvstore command to commit your changes to the non-volatile RAM (NVRAM) for use in subsequent reboots.
- After you perform these commands, at reboot you see this output:
Aliasing the OpenBoot 'go' command! go isn't unique.