Upgrade VXFS Online

update version 3 veritas JFS file system to version 4

vxupgrade -n 4 /mount_point

vxfsconvert -- offline version or to convert an HFS
     




lock / unlock account user id on HP-UX trusted Systems: How to ?

  

/usr/lbin/getprpw useraccount

unlock / enable / reactivate:
/usr/lbin/modprpw -k useraccount

lock / expire password:
/usr/lbin/modprpw -e useraccount

Note : Do not use a capital E, as it will expire the password on all user accounts.


     




Disable password age in HP UX ?



HPUX password aging disable:

passwd -x -1 user_id

for i in user1 user2 user3
do
passwd -x -1 $i
done


     




dbprofile - in HP UX Itanium servers

At EFI shell:
display dbprofile:
dbprofile

add/update profile named "ignite" providing only one parameter: dhcp
dbprofile -dn ignite -dhcp

when modifying the profile, only the parameters that are changing need to be listed; you don't need to re-do the entire syntax

three ways that work: first two only work if the ignite server and client are in the same ethernet broadcast domain (subnet).
  - last option gives fast boot time, first and second options requires less administration.

1. dbprofile -dn ignite -dhcp
2. dbprofile -dn ignite -dhcp -b "/opt/ignite/boot/nbp.efi"
3. dbprofile -dn ignite -sip IGNITE.IP.ADDRESS -cip CLIENT.IP.ADDRESS -gip GATEWAY.IP.ADDRESS -m NETMASK -b "/opt/ignite/boot/nbp.efi"

example - ignite IP 192.168.1.2,  client IP 192.168.0.2, gateway/router IP 192.168.0.1, netmask 255.255.255.0
dbprofile -dn ignite -sip 192.168.1.2 -cip 192.168.0.2 -gip 192.168.0.1 -m 255.255.255.0 -b "/opt/ignite/boot/nbp.efi"

to actually use the dbprofile:
lanboot -dn ignite
or to pick a specific NIC to boot from: lanboot select -dn ignite

to find list of NICs, run:
lanaddress

sometimes on NPARS, not all NICs show up, so do the following to re-connect the EFI drivers:
reconnect -r

LVM2 in HPUX 11.31

  

LVM2 found in HPUX 11.31 has lifted a lot of burdensome limits on volume groups.  vgcreate automatically creates the  device group file; VGs are only limited by the MAX VG size you specify when creating the VG, using the -S option; hitting the max VG size is the only case where a backup/recreate/restore is needed.  Here's a list of helpful commands:

LVMP_CONF_PATH_NON_BOOT  found in /etc/lvmrc  (in March 2010 release)  allows lvm2 vg configuration file backups to an alternate location because of the large size of VG 2.X backups

lvmadm - (-t) displays limits of LVM1 and LVM2 VG 1.0 and VG 2.0 and up;  (-l) also lists the contents of /etc/lvmtab and lvmtab_p

lvmadm -l
--- Version 1.0 volume groups ---
VG Name /dev/vg00
PV Name /dev/disk/disk3_p2
        /dev/disk/disk2_p2

--- Version 2.1 volume groups ---
VG Name /dev/vgXX
PV Name /dev/disk/diskXXX


convert from legacy to persistent DSF: use vgdsf
/usr/contrib/bin/vgdsf –c vgXX

vgcreate using the new LVM2 VG2.0+ notation:
vgcreate -V 2.1 -s 16 -S 4t vgXXX /dev/disk/diskxxx /dev/disk/diskxxx

convert from VG1.0 to VG2.0+
The -r does a "review" to make sure the VG can be converted.
vgversion -V 2.1 -r vgXX

before the convert will run the VG has to be deactivated:
vgchange -a n vgXX
vgversion -V 2.1 vgXX


ioscan new options for persistent dsfs:
ioscan -m dsf /dev/disk/disk127
Persistent DSF           Legacy DSF(s)
========================================
/dev/disk/disk127        /dev/dsk/c5t5d0
                         /dev/dsk/c6t5d0


     




ULIMIT value in HP UX

uni1. ulimit -a   - Display all configured values.
2. ulimit -c  -  Sets core file size
3. ulimit -d  -  Sets data seg size
4. ulimit -n  -  Sets Open Files
5. ulimit -s  -  Sets stack size
6. ulimit -u  -  Sets max user processes
7. ulimit -t   -  Sets cpu time
8. ulimit -v  -  Sets virtual memory
9. ulimit -p  - Sets pipe size
  




     




Set up a Package to Use EMS Resource : How to ?

1.Use the resls command to identify the EMS resource name.


2.Edit the package configuration file and add the resource definition
vi /etc/cmcluster/package/pkg.conf
 RESOURCE_NAME    /system/filesystem/availMb/home
 RESOURCE_POLLING_INTERVAL   30
 RESOURCE_UP_VALUE    >= 5


3.Halt the cluster. (This is required for the cmcld daemon to register the resource)
4.Reapply the package configuration file.
5.Restart the cluster



     




Blogger Tips and TricksLatest Tips And TricksBlogger Tricks