Ignite-ux :-


— Creating golden image of a client to install several other clients –
(Clear example can be found on the link – http://www.hpuxtips.es/?q=node/180 )

On the client side, we will be having a script called /opt/ignite/data/scripts/make_sys_image. Copy this script temporarily onto /tmp to create golden image and change the permissions of it i.e. make_sys_image to executable.

#chown 755 /tmp/make_sys_image
#./tmp/make_sys_image -s local -d <nfs-directory shared from ignite server(ensure enough space exists to hold the golden image)> -u -n Golden-image-local-server -v
Note: ensure that the golden system is listed in /.rhosts file on ignite server

Once the golden image is created, on the ignite ux server need to do little bit configuration to build new golden image configuration for use

# mkdir -p /var/opt/ignite/data/HP-UX_B.11.31_DCOE – creating a config directory
# cd /var/opt/ignite/data/HP-UX_B.11.31_DCOE

#cp /opt/ignite/data/examples/core11.cfg ./core_archive_cfg — copying temp config file

#/opt/ignite/lbinia/archive_impact -t -g golden-11.31-1009-DCOE impacts.txt

#cat /var/opt/ignite/data/HP-UX_B.11.31_DCOE/core_archive_cfg — edit the respective parameters for the new config ex: nfs_source & impacts for filesystems

# /opt/ignite/data/instl_adm -T -f /var/opt/ignite/data/HP-UX_B.11.31_DCOE/core_archive_cfg  — checking the integrity of your new config
Some additional commands related to Ignite-UX –

#/opt/ignite/data/instl_adm — available configs

# cat /var/opt/ignite/INDEX — current available configurations

– taken ignite backup of the server is available under the /var/opt/ignite/clients/<server-name>/
#/opt/ignite/bin/make_net_recovery -x inc_entire=vg00 -x inc_entire=vg01 -s <Ignite_server>


Adding a new client to ignite-ux server :-
– first add the ignite ux server entry to /etc/hosts file on the client and then run the below command :

#add_new_client -s <ignite servername>


#showmount -e <server-name> — list of exported filesystems


Major differences between 11.11 & 11.23 & 11.31 Operating Systems –
– hyperthreading can be enabled only in 11.31

– commands are enhanced in 11.31 like kmtune got changed to kctune

– built in virtualization and management software available in 11.31

  1. in 11iv2 – /etc/exports
  2. in 11iv3 – /etc/dfs/dfstab
  3. share – command to share nfs mount in 11iv3
  4. exportfs -av – command to export nfs mounts in 11iv2
    —————————————————————————————————–6. /etc/rc.config.d/nfsconf

    Network configuration in HP-UX –

    Configuration File :

/etc/rc.config.d/netconf        –  Contains the hostname, ip address, default route
/etc/hosts                            –  Contains the hsotname to IP address mapping
/etc/resolv.conf                   –  Contains DNS server details
/etc/inetd.conf                     – Internet daemon configuration file

Configuration Files used for DNS Client:

Scripts :
/sbin/init.d/net start  – To start network services
/sbin/init.d/net stop  – To stop network services

Commands :

1. To set the hostname :
# set_parms hostname

2. To set primary ip address :
# set_parms ip_address

3.  To set the default gateway, DNS/NIS server details :
# set_parms addl_netwrk

4.  To restart inetd daemon :
# inetd -c

5. To display the ip address configuration details :
# netstat -i

6. To set the IP details of lan0 :
# ifconfig lan0

7. To display all the network adapters :
# lanscan

8. To display routing table :
# netstat -rn

9. To add a route :
# route add default 1

10. To enable a network interface :
# ifconfig lan0 up

11. To disable a network interface :
# ifconfig lan0 down

12. To change NIC settings like speed, duplex,..
# lanadmin

Managing vPars in Superdome-2

  1. To start a vpar from MON> prompt,MON> vparload -p vPar_name

    2. To boot a vpar from command line,

    # vparboot -p vPar_name

    3. To show vpar info from MO> prompt,

    MON> vparinfo

    4. To show vpar status from command prompt,
    # vparstatus

 – Backup & Restore :
I’d worked in EMC networker so far but not in depth there. we had seperate backup team available for it.
: to backup a filesytem to the tape

# fbackup -f /dev/rmt/0m -i /home
: to list the contents of the tape media

# frecover -l /tmp/index_list -f /dev/rmt/0m
# frecover -rvf /dev/rmt/0m – recover all the files from the tape media 0m
# mt -f /dev/rmt/0mnb status – tape drive status
#mt -f /dev/rmt/0mnb offline – taking the tape drive to offline
#mt -f /dev/rmt/0mnb rewind – rewind the tape drive


– Printers
#lpstat – printer job status
#lpstat -t <printer-name/ip> – check the functionality of the printer
#lpstat -o – requests ids of all printers
#cancel job# – to cancel a particular print job
# /etc/rc.config.d/lp – printer configuration file
# lpshut – stopping spooler
#lpstart – start spooler
#accept <printername> – accept print requests
#reject -r <alternate printer for future print requests > <printer name>
#lpstat -o <printer-name> – to view jobs in print queue
#lpmove printer-A printer-B


 – root disk replacement
#pvchange -a N /dev/rdsk/ctd – stop I/O’s before removing that particular disk
# ioscan -fnCdisk – after replacement, disk should be in CLAIMED state.
# diskinfo /dev/rdsk/ctd
# pvcreate -B /dev/rdsk/ctd – to make our raw disk bootable
# mkboot -l /dev/rdsk/ctd – placing the boot utilities
# mkboot -a “hpux -lq” /dev/rdsk/ctd – setting low quorum
#vgcfgrestore -n vg00 /dev/rdsk/ctd
#vgchange -a y vg00
# lvsync /dev/vg00/lvol1

#vgsync vg00
#setboot – verify primary/alternate boot paths
#lvlnboot -R – update BDRA
#lvlnboot -v
#cat /stand/bootconf – verify both boot disks

What is BDRA & VGRA ?

– BDRA is boot data reserved area – fix with lvlnboot

– VGRA is volume group reserved area – fix with vgcfgrestore


Persistent device files –

– persistent device files are available in hp-ux 11iv3
– #ioscan -m dsf — listing persisting device files with legacy device file information

– itanium root disk replacement(SAS drive-rx2660)

#vgdisplay -v vg00 – verify the disk which is failed
#ioscan -m lun
#ioscan -fnH 0/2 – find legacy device file
Is the disk IR volume or JBOD (look for disk WWID ending with …ee41, then it’s jbod. When we replace jbod disk new legacy& persistent device file gets created )
#sasmgr get_info -D /dev/sasd0 -q raid
#pvchange -a N /dev/rdisk/ – halt LVM access
– blow the led for failed disk

#sasmgr set_attr -D /dev/sasd0 -q lun=<raw device file> -q locate_led=on
#sasmgr get_info -D /dev/sasd0 -q lun=all -q lun_locate
– replace disk
– check for newly created device files
#ioscan -fnH 0/2 – legacy device file
#sasmgr -D /dev/sasd0 -q raid – newly created device file
#ioscan -m dsf – newly created device file
#ioscan -m lun – newly created lun
#diskinfo /dev/rdisk/disk# – disk size
– stop the LED blow

#sasmgr get_info -D /dev/sasd0 -q lun=all -q lun_locate
#sasmgr set_attr -D /dev/sasd0 -q lun=<raw device file> -q locate_led=off
– create ia64 partitioning scheme to the new boot disk
#vi /tmp/partitiontable



HPUX 100%

# idisk -wf /tmp/partitiontable /dev/rdisk/disk#
# insf -eCdisk – install the special device files for newly created disk partitions i.e. disk#_p1,_p2,_p3
#ioscan -fnH 0/2
#ioscan -m lun
#ioscan -m dsf
– redirect the i/o from the new device to the old device file
# sasmgr replace_tgt -D /dev/sasd0 -q old_dev=/dev/dsk/ctd -q new_tgt_hwpath=<hwpath>
#io_redirect_dsf -d /dev/disk/disk3 -n /dev/disk/disk5 – this removes disk5 special files
#ioscan -fnH 0/2
#ioscan -m dsf
#ioscan -m lun
– initialize the EFI FAT partition and fill the boot areas :

# efi_fsinit -d /dev/rdisk/disk3_p1
– Use mkboot to copy the boot utilities i.e. this formats the EFI partition(s1) and populate it with the EFI files below /usr/lib/efi/ and to format the LIF volume (s2) and populate it with the LIF files(ISL,AUTO,HPUX,LABEL) below /usr/lib/uxbootlf.
# mkboot -e -l /dev/rdisk/disk3
# efi_ls -d /dev/rdisk/disk3_p1
#lifls -l /dev/rdisk/disk3_p2
– Check the content of AUTO file on the original boot disks EFI partition:

#efi_cp -d /dev/rdisk/disk3_p1 -u /EFI/HPUX/AUTO /tmp/x
#mkboot -a “boot vmunix -lq” /dev/rdisk/<primary boot disk>
#mkboot -a “boot vmunix -lq” /dev/rdisk/<secondary boot disk>
– Copy the HP service partition :

# dd if=/dev/rdisk/disk2_p3 of=/dev/rdisk/disk3_p3 bs=1023k
– Restore LVM configuration

OS partition-p2

#vgcfgrestore -n vg00 /dev/rdisk/disk#_p2
# vgchange-a y /dev/vg00
#nohup vgsync /dev/vg00 &
– initialize or check the boot information on the new disk

:check if content of the LABEL file(i.e. root,boot,swap and dump device definition) has been initialized(done by lvextend) on mirrored disk

#lvlnboot -v

if not then set it using lvlnboot –

#lvlnboot -r /dev/vg00/lvol3

#lvlnboot -b /dev/vg00/lvol1

#lvlnboot -s /dev/vg00/lvol2

#lvlnboot -d /dev/vg00/lvol2
– update EFI boot configuration to recognize the new disk

#setboot – to check the primary/alternate boot path/disks

#setboot -h <>

#setboot -a <>

the above will add the new entries into the EFI boot menu in the below order

# Primary Path

# HA alternate path

# Alternate Path

Scenario- Unexpected server reboots- oracle RAC

– Oracle RAC software will reboot the server automatically upon private interconnect outages, san outages, or some network outages.

Virtual Connect/Chassis/Enclosure patching which was done last night can cause this.


#scsictl -a /dev/rdsk/c?t?d? — displays the control parameter information about the disk device
#scsictl -a -m queue_depth=4 /dev/rdsk/c?t?d? – setting the queue depth value to 4

*queue depth will increase the i/o performance

*queue depth, in storage, is the number of pending input/output requests for a volume


HP hardware information –


–  HP servers based on PA-RISC(The HP-9000 model line) – D class, K class, L class (rp5400,rp5405, rp5430, rp5450, rp5470 ), N class (rp7400(4-sockets, 4-core), rp7405, rp7410, rp7420, rp7440), rp3410,rp3440,rp4410,rp4440(4-sockets, 8-core)

– HP stopped selling PA-RISC servers starting dec-31 2008
– HP servers based on itanium (The “integrity” model line) – rx2600(2-sockets, 2-cores; used for workstation; high end audio and video cards integrated ), zx6000(2, 4; used for workstations), rx2620(2,4; usually seen this single core, can be upgraded to dual core), rx2660(2,4; SAS attached; ), rx4640(4 sockets, 8 core)


 LVM –

root volume – lvol3

swap volume – lvol2

stand volume – lvol1

– vgcfgbackup is used to take backup of volume group metadata (/etc/lvm/backup/<vg-name>)

– default vg configuration backups are available under /etc/lvmconf/vg#.conf

# vgcfgbackup -u /dev/vg00 – update volume group information to the configuration i.e. /etc/lvmconf/vg00.conf

#vgcfgbackup -f /tmp/vg00_date.conf /dev/vg00 — backing up the configuration to /tmp/vg00_date.conf file

– replacing hot swappable scsi root disk


# lvlnboot -v  — boot definitions for root volume group: vg00

#pvdisplay -v /dev/disk/disk3

#lvdisplay -v /dev/vg00/lvol1


# ioscan -m lun /dev/disk/disk14

#pvhange -a N /dev/disk/disk14

**replace disk**

#scsimgr replace_wwid -D /dev/disk/disk14 — this command allows the storage subsystem to replace the old disk’s LUN WWID with the new disk’s LUN WWID. This storage subsystem creates the new LUN instance and device files for this new disk

If new lun instance is created then we need to assign the old lun instance to this new lun instance of replaced disk

#io_redirect_dsf -d /dev/disk/disk14 -n /dev/disk/disk28

**restore lvm configuration**

#vgcfgrestore -n /dev/vg00 /dev/rdisk/disk14

#pvchange -a y /dev/disk/disk14

#vgchange -a y /dev/vg00

#vgsync /dev/vg00

———————————————————————————————————— Basic failover commands for VCS & Service Guard 
#hastart -all

#hastatus -sum

#hagrp -switch <group-name> -to <backup-system-name>

#hastop -all

Service Guard

#cmviewcl -v

#cmruncl -v

#cmrunpkg -n <node-name> <package-name>

#cmhaltpkg <package-name>

#cmmodpkg -e <package-name >  — enable package fail-over

#cmhaltcl -v