HPUX Managing CPU resource with PRM


Process Resource Manager (PRM) is a resource management tool used to control the amount of resources that processes use during peak system load (at 100% CPU resource or 100% memory resource). PRM can guarantee a minimum allocation of system resources available to a group of processes through the use of PRM groups.
A PRM group is a collection of users and applications that are joined together and assigned certain amounts of CPU and memory resource. The two types of PRM groups are FSS PRM groups and PSET PRM groups. An FSS PRM group is the traditional PRM group, whose CPU entitlement is specified in shares. This group uses the Fair Share Scheduler (FSS) in the HP-UX kernel within the system’s default processor set (PSET). A PSET PRM group is a PRM group whose CPU entitlement is specified by assigning it a subset of the system’s cores (PSET). (A core is the actual data-processing engine within a processor. A single processor might have multiple cores. A core might support multiple execution threads.) Processes in a PSET have equal access to CPU cycles on their assigned cores through the HP-UX standard scheduler.

Continue reading “HPUX Managing CPU resource with PRM”

hpux: How Do I configure routing or add route?

You can use route command to configure routing. Syntax is as follows:

route add net {network-address} netmask {subnet} {router-address}

Let us assume your router address is and network ID is, then you can type route command as follows:

# route add net netmask


To add a default route:

# route add default

Verify that (display) routing table is updated (display routing table):

# netstat -nr

Test it i.e. try to ping or send nslookup request:

# ping mycorp.com

To flush all routing entries use command [quite handy to clean your gordian knot ;)] :

# route -f

However if I reboot HPUX box then above routing entries gets removed. To pick up your setting upon each reboot your need to configure Routes in HPUX networking configuration file – /etc/rc.config.d/netconf. To add default router/gateway

# vi /etc/rc.config.d/netconf
Add or modify following entries


managing hpvm

Start a VM

hpvmstart -P vmname

Stop a VM

hpvmstop -P vmname

List VM status


List individual VM status

hpvmstatus -P vmname

Assign a Host LV to a VM

hpvmmodify -P vmname -a disk:scsi:lv:/dev/vg_vm/rlv_vm01

Assign a Host scsi disk to a VM

hpvmmodify -P vmname -a disk:scsi:lv:/dev/rdsk/c0t0s0

Assign a Host tape drive to VM

hpvmmodiy -P vmname -a tape:scsi:attach:/dev/rscsi/c5t3d0

Remove allocated resource from VM

hpvmmodify -P vmname -d disk:scsi:lv:/dev/rdsk/c0t0s0

what is vglock?

A vg used as cluster lock is generally called vglock. cluster lock refer to a tie breaker short of thing which is generally used in a two node service guard cluster. In the event of failure of communication between two nodes whoever takes control of lock first will continue to run cluster and other node will be halted.

Hence the purpose of this is to ensure both nodes independently form two seperate clusters in the even of failure of communication among them.