what the blog?

Tagged: hpux RSS

• 

  levin 3:16 am on March 2, 2010 Permalink | Reply
  Tags: hpux, prm   

  HPUX Managing CPU resource with PRM 

  Overview

  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.

  (More …)

   

  Reply Cancel reply

  Required fields are marked *

  Name *

  Email *

  Website

  

  

  

  
  

  CAPTCHA Code *

  

• 

  levin 11:31 pm on November 11, 2009 Permalink | Reply
  Tags: hpux   

  howto add ip alias on HPUX 

  Lunch SAM -> [Networking and Communications] -> [Network Interface Cards] -> highlight  ”lan N”

  Then select [Actions]-> [Add IP Logical Interface]

   
• 

  levin 4:31 pm on September 20, 2009 Permalink | Reply
  Tags: hpux   

  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 192.168.1.254 and network ID is 192.168.1.0/24, then you can type route command as follows:

  # route add net 192.168.1.0 netmask 255.255.255.0 192.168.1.254

  OR

  To add a default route:

  # route add default 192.168.1.254

  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 192.168.1.254:

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

  ROUTE_DESTINATION[0]="default"
  ROUTE_MASK[0]=""
  ROUTE_GATEWAY[0]="192.168.1.254"
  ROUTE_COUNT[0]="1"
  ROUTE_ARGS[0]=""

   
• 

  levin 4:29 pm on September 20, 2009 Permalink | Reply
  Tags: hpux   

  managing hpvm 

  Start a VM

  hpvmstart -P vmname

  Stop a VM

  hpvmstop -P vmname

  List VM status

  hpvmstatus

  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

  levin, and Steve are discussing. Toggle Comments

   
  • 

    Steve 9:05 pm on October 13, 2009 Permalink | Reply

    How do you change the “memory required to start VM” dynamically? I know the command “hpvmmodify -P VMname -r 2G”. I know you need to install HPVM-guest, I know you need to enable dynamic_memory_control=1. But it doesn’t work.

  • 

    levin 10:21 pm on October 13, 2009 Permalink | Reply

    Since lack of information from your question, please try to verify the following point.

    1. Did you installed guest-tool properly on your guest vm?
    2. hpvmstatus -V -P VMname , did you see dynamic memory section is enabled?
    3. Did you create your VM with -x ram_dyn_type=any -x ran_dyn_min=M -x ran_dyn_max=M -x ram_dyn_target_start=M ?
    4. hpvmmgmt -l ram , on guest, does it show memory settings properly?

    Try to re-read the manual carefully again.
    http://docs.hp.com/en/T2767-90105/ch09s06.html

    good luck!

  • 

    Steve 3:54 pm on October 14, 2009 Permalink | Reply

    Hello,

    1) HPVM-Guest is installed
    [VMname:root]/root # swlist HPVM-Guest
    # Initializing…
    # Contacting target “VMname”…
    #
    # Target: VMname:/
    #

    # HPVM-Guest B.04.00 Integrity VM Guest
    HPVM-Guest.vmTools B.04.00 Integrity VM Tools

    2)[Dynamic Memory Information]
    Type : driver
    Minimum memory : 1024 MB
    Target memory : 2042 MB
    Maximum memory : 2048 MB
    Current memory : 2042 MB
    Comfortable minimum : 890 MB
    Boot memory : 2042 MB
    Free memory : 1180 MB
    Available memory : 206 MB
    Memory pressure : 0
    Memory chunksize : 65536 KB
    Driver Mode(s) : STARTED ENABLED GUESTCTL

    3) hpvmcreate -P VMname -O hpux -c 1 -e 25 -r 2g -B auto \
    -a network:lan:vswitch:vsw-lo \
    -a network:avio_lan:vswitch:vsw-l901 \
    -a dvd:scsi::null:/var/opt/hpvm/ISO-images/hpux \
    -a disk:avio_stor::disk:/dev/rdisk/disk8 \
    -xram_dyn_type=any:ram_dyn_min=1g:ram_dyn_max=2g:ram_dyn_target_start=2g
    PS: There is space between -x and ram

    4) [VMname:root]/root # hpvmmgmt -l ram

    [Dynamic Memory Information]
    =======================================
    Type : driver
    Target memory : 2042 MB
    Current memory : 2042 MB
    Comfortable minimum : 890 MB

    The command I did to change the memory is

    [host:root] # hpvmmodify -P VMname -r 3g
    hpvmmodify: Unable to dynamically set the memory information.
    hpvmmodify: Guest needs to be restarted for all changes to take effect.

    You can see that I need to restart the guest.

    Thanks.

  • 

    Steve 5:01 pm on October 14, 2009 Permalink | Reply

    Hello,

    I think I found why. Because I didn’t create the VM with
    dynamic_memory_control=1, I have to add the option when change memory.

    hpvmmodify -P VMname -r 4g \
    -x dynamic_memory_control=1

    This command worked. But my additional issue is: I can’t
    see the changes from hpmvstatus command.

  • 

    levin 6:21 pm on October 14, 2009 Permalink | Reply

    Hi Steve, using dynamic memory on HPVM can be set between ram_dyn_min and ram_dyn_max. The ram_target specify the guest VM memory size, enable dynamic_memory_control is allowing the dynamic memory management on guest vm.

    you should set ram_dyn_max to a higher value, and then use ram_target to limit on each guest VM.

• 

  levin 4:23 pm on September 20, 2009 Permalink | Reply
  Tags: hpux   

  howto fix/etc/ioconfig /stand/ioconfig inconsistent 

  Boot into single mode

  mv /etc/ioconfig /etc/ioconfig.bak

  mv /stand/ioconfig /stand/ioconfig.bak

  issue “ioinit -c”

  reboot

  lett is discussing. Toggle Comments

   
  • 

    lett 9:21 pm on September 11, 2010 Permalink | Reply

    good stuff…thx

• 

  levin 4:14 pm on September 20, 2009 Permalink | Reply
  Tags: hpux   

  hpux: how to boot into single mode 

  interrupt the boot prompt and then enter “hpux -iS”

   
• 

  levin 4:46 am on December 18, 2008 Permalink | Reply
  Tags: hpux   

  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.