Chat now with support
Chat mit Support

Privilege Manager for Unix 7.1.1 - Administration Guide

Introducing Privilege Manager for Unix Planning Deployment Installation and Configuration Upgrade Privilege Manager for Unix System Administration Managing Security Policy The Privilege Manager for Unix Security Policy Advanced Privilege Manager for Unix Configuration Administering Log and Keystroke Files InTrust Plug-in for Privilege Manager for Unix Troubleshooting Privilege Manager for Unix Policy File Components Privilege Manager for Unix Variables
Variable names Variable scope Global input variables Global output variables Global event log variables PM settings variables
Privilege Manager for Unix Flow Control Statements Privilege Manager for Unix Built-in Functions and Procedures
Environment functions Hash table functions Input and output functions LDAP functions LDAP API example List functions Miscellaneous functions Password functions Remote access functions String functions User information functions Authentication Services functions
Privilege Manager for Unix programs Installation Packages

Checking the status of the master policy

The "master" copy of the policy file resides in a repository on the primary policy server. Each primary and secondary policy server maintains a "production" copy of the policy file or files. Use the pmpolicy utility to verify that the production copy is current with the master policy.

To compare the production policy file against the master policy on the primary server

  1. From the command line, enter: 
    # pmpolicy masterstatus

    If the files are in sync, the Current Revision number will match the Latest Trunk Revision number. If someone hand-edited the local copy without using pmpolicy utility commands to commit the changes, "Locally modified" will indicate "YES".

    If the production policy is not current with the master policy you can update the production policy with pmpolicy sync.

Related Topics

pmpolicy

Checking the policy server

When the policy server is not working as expected, use the pmsrvcheck command to determine the state of the server and its configuration.

To verify the policy server is running

  1. From the command line, enter: 
    # pmsrvcheck

    This command returns output similar to this:

    testing policy server [ Pass ]

    If the policy server is working properly, the output returns 'pass', otherwise it returns, 'fail'.

Related Topics

pmsrvcheck

Checking policy server status

The primary and secondary policy servers need to communicate with each other. Run the pmloadcheck command on a policy server host to verify that it can communicate with other policy servers in the policy group.

To determine if there any issues with policy servers in the policy group

From the Privilege Manager for Unix host command line, enter:

# pmloadcheck -r

This command has output similar to this:

[0][root@sol10-x86 /]# pmloadcheck -r 
** Reporting current availability of each configured master... 
   * Host:myhost1.example.com (172.16.1.129) ... [ OK ] 
** Based on this data, the server list is currently ordered as: 
1.	myhosts.example.com
Related Topics

pmloadcheck

Checking the PM Agent configuration status

To check the PM Agent configuration status

  1. From the command line, enter: 
    # pmclientinfo

    This command returns output similar to this:

    # pmclientinfo 
   - Joined to a policy group               : YES 
   - Name of policy group                   : MyPolicyGroup 
   - Hostname of primary policy server      : myhost.example.com 
   - Policy type configured on policy group : pmpolicy

    If the PM Agent has been properly configured, it will say ‘Joined to a Policy Group: YES’ and give the policy group name and primary policy server’s hostname.

Related Topics

pmclientinfo

Verwandte Dokumente

The document was helpful.

Bewertung auswählen

I easily found the information I needed.

Bewertung auswählen