Hub/Switch Installation Guide

Chapter 7 HPSS User Interface Configuration
448 September 2002 HPSS Installation Guide
Release 4.5, Revision 2
$HPSS_PATH_BIN/hdm_admin -k $key -s $id -v $var tcp \
disable >/dev/null 2>&1
done
exit 0
The post_stop_dfs script is executed once it has completed detaching the DFS aggregates and
shutting down DFS. The script stops any HDMs that are still running.
Here is a sample for post_stop_dfs:
#!/bin/ksh
export HPSS_PATH_BIN=/opt/hpss/bin
# Stop any hdm's that are still running
for id in 0 1; do
key=`expr 3788 + $id`
var=/var/hpss/hdm/hdm$id
$HPSS_PATH_BIN/hdm_admin -k $key -s $id -v $var ps >/dev/null 2>&1
if [ $? = 0 ]; then
echo " stopping hdm$id"
$HPSS_PATH_BIN/hdm_admin -k $key -s $id -v $var \
-y stop >/dev/null 2>&1
fi
done
exit 0
To startand stopDFS,besure to use the commands start.dfs and stop.dfs. In particular, do not
stop DFS using dfs.clean, since it does not handle HDM correctly.
7.6.3.3 Configuring an HDM Server (DFS & XFS)
The HDM server is configured with five configuration files, usually kept in /var/hpss/hdm/
hdm<id>. Although any directory can be used, all five files must be kept together. By convention,
theevent andmessagelogsarealsokeptinthissamedirectory. Thenames ofthe configurationfiles
are:
config.dat basic configuration file
filesys.dat description of file systems and filesets
gateways.dat gateways permitted to access HDM
policy.dat migration and purge policies
security.dat configuration for Security Server (DFS systems only)
nshandle.dat Name Server handle data (XFS systems only)
Fourofthe files(config.dat, gateways.dat,policy.dat,andsecurity.dat)maybe createdusing a text
editor. The format of these files is described below. The files must be present before HDM can be
started. If anyoneof these filesis edited, HDM must berestarted before the change willtake effect.