HP PRM Version C.03.01 Release Notes for HP-UX 11i v1 and HP-UX 11i v2

PRM Release Notes
Compatibility information and installation requirements
Chapter 1 19
Compatibility with processor sets (PSETs)
PRM allows you to define PRM groups based on PSETs.
NOTE When you have PRM groups based on PSETs however, do not modify the PSETs
manually using the psrset command.
Compatibility with WLM
PRM and HP-UX Workload Manager (WLM) should not be used to manage the same system
at the same time. Using these products at the same time may cause inconsistent behavior and
undesirable performance.
Compatibility with gWLM
PRM and HP Global Workload Manager (gWLM) should not be used to manage the same
system at the same time. Using these products to control resources at the same time may
cause inconsistent behavior and undesirable performance.
Compatibility with long hostnames
PRM supports long hostnames. You must install the bundle NodeHostNameXpnd and
configure the feature first though. For more information, see the section “Installation
procedure” on page 14.
Compatibility with Bastille and firewalls
By default, xprm controls PRM on remote systems through port 9610 on the remote systems.
If your network or the remote systems use a firewall or if you are using the HP-UX Bastille
product on the remote systems, it is likely that communications on this port are being blocked.
To use xprm in your environment, your options include:
• Specifically allowing port 9610 or another port to be open to incoming connections. If you
use a port other than 9610, be sure to restart prm3d to listen on the new port on each
remote system; also, have xprm connect to the new port.
• Using SecureShell (ssh) to connect to the locked-down system and running xprm if you do
not want to open a port. (SecureShell must be installed on the system that you are on and
on the system to which you want to connect.)