To install the secondary server
For example, on a 64-bit Red Hat Linux, run:
# cd server/linux-x86_64
# rpm –-install qpm-server-*.rpm
NOTE: The Solaris server has a filename that starts with QSFTpmsrv.
When you install the qpm-server package, it installs all three Privilege Manager components on that host:
You can only join a PM Agent host to a Privilege Manager policy server or a Sudo Plugin host to a sudo policy server. See Security policy types for more information about policy types.
You use the pmsrvconfig -s <primary_policy_server> command to configure a secondary server. See pmsrvconfig for more information about the pmsrvconfig command options.
To configure the secondary server
# pmsrvconfig –s <primary_policy_server>
where <primary_policy_server> is the hostname of your primary policy server.
pmsrvconfig prompts you for the "Join" password from the primary policy server, exchanges ssh keys for the pmpolicy service user, and updates the new secondary policy server with a copy of the master (production) policy.
Once you have installed and configured a secondary server, you are ready to join the PM Agent to it. See Join hosts to policy group for details.
Privilege Manager generates log files containing event timestamps based on the local clock of the authorizing policy server.
To synchronize all policy servers in the policy group, use Network Time Protocol (NTP) or a similar method of your choice.
Once you have installed and configured the primary policy server, you are ready to install a PM Agent on a remote host.