Installation Manual

HP StorageWorks File System Extender Software installation guide for Linux 39
Use the rpm -V command to check whether the software installation is corrupt. Note that applied FSE hot
fixes change individual binaries and other files making it difficult to determine whether or not the
installation is corrupt. Proceed as follows:
1. Change the current directory to one with the FSE installation packages and reinstall the packages:
2. Verify the reinstalled packages using the following command:
If all FSE release or FSE system maintenance release files were correctly updated, the command output
is empty.
Preparing the environment for the first startup of the FSE implementation
Preparing the environment consists of modifying environment variables, updating the FSE backup
configuration files, and configuring the FSE interprocess communication.
Modifying the PATH environment variable
To be able to execute FSE commands, FSE tools, the omninames command, and start the FSE
Management Console client from any location, change the search path as follows:
You can permanently extend the executable search path by adding the above line to your .bashrc shell
startup file. The changes in .bashrc become effective after your next logon to the system as root.
Modifying the LD_LIBRARY_PATH environment variable
To enable Log Analyzer to run, set the variable for paths to shared libraries as follows:
You can permanently extend the executable search path by adding the above line to your .bashrc shell
startup file. The changes in .bashrc become effective after your next logon to the system as root.
Modifying the MANPATH environment variable
To read the FSE man pages, extend the search path for man pages as follows:
You can permanently extend the man page search path by adding the above line to your .bashrc shell
startup file. The changes in .bashrc become effective after your next logon to the system as root.
Preparing the FSE backup configuration file
Configure the parameter SNAPSHOT_PCT in the backup configuration file
/etc/opt/fse/backup.cfg.
The line from backup.cfg with SNAPSHOT_PCT configured with its default value is the following:
For details, see the FSE user guide, chapter ”Backup, restore, and recovery”, section ”Backup”, subsection
”How it works?”.
Configuring the FSE interprocess communication
FSE interprocess communication is configured according to the FSE implementation (consolidated,
distributed, or mixed FSE implementation) and the network type used for FSE interprocess communication
(ordinary LAN, private network). In this context, the term ordinary LAN means the common company LAN
to which systems are attached using their primary network adapters, and the term private network means a
dedicated network to which systems are attached using their secondary network adapters.
# cd PathToFSEPackageDirectory
# rpm -F --force fse*.rpm
# rpm -V `rpm -qa | grep fse`
# export PATH=$PATH:/opt/fse/sbin:/opt/fse/sbin/tools:/opt/fse/bin
# export LD_LIBRARY_PATH=/usr/local/lib
# export MANPATH=$MANPATH:/opt/fse/man
SNAPSHOT_PCT=10