Category: HP-UX

The LUN callback routine has failed the LUN destroy request as there are 1 active opens on the LUN

Node : hpux.setaoffice.com
Node Type : Itanium 64/32(HTTPS)
Severity : major
OM Server Time: 2016-02-16 14:45:48
Message : DMESG-UNCLASSIFIED: The LUN callback routine has failed the LUN destroy request as there are 1 active opens on the LUN (64000/0xfa00/0x5c).
Msg Group : OS
Application : HPUX_dmesg
Object : dmesg_UNCLASSIFIED
Event Type :
not_found

Instance Name :
not_found

Instruction : No

We found a LUN that we are unable to remove

root@hpux:~ # ioscan -fNC disk | grep NO_HW
disk 825 64000/0xfa00/0x5c esdisk NO_HW DEVICE offline HP OPEN-V

root@hpux:~ # ioscan -fNC disk | grep 825
disk 825 64000/0xfa00/0x5c esdisk NO_HW DEVICE offline HP OPEN-V
/dev/disk/disk825 /dev/rdisk/disk825

Edited file /var/opt/OV/conf/OpC/dmsg_mon.cfg to include the string 64000/0xfa00/0x5c to not trigger this alarm

Feb 16 17:58:13 hpux vmunix: The LUN callback routine has failed the LUN destroy request as there are 2 active opens on the LUN (64000/0xfa00/0x5c).
Feb 16 18:16:59 hpux vmunix: The LUN callback routine has failed the LUN destroy request as there are 1 active opens on the LUN (64000/0xfa00/0x5c).

HP Data Protector – [61:1002] The VBDA named “backuphost.setaoffice.com [/usr/software/ctmagent]” on host hpux.setaoffice.com reached its inactivity timeout of 28800 seconds.

[Major] From: BSM@backuphost.setaoffice.com “OS_FILES_GRP_BACKUPHOST_DAILY_1800_03_ESL” Time: 1/11/2016 7:11:54 AM
[61:1002] The VBDA named “backuphost.setaoffice.com [/usr/software/ctmagent]” on host hpux.setaoffice.com
reached its inactivity timeout of 28800 seconds.
The agent on host will be shutdown.

The error message says that Data Protector is not finishing before the timeout that was set.

Listing the files in the filesystem

ls -lR /usr/software/ctmagent

It is stopping in this directory

/usr/software/ctmagent/ctm/install/perl/5_8_4/lib/5.8.4/IA64.ARCHREV_0-thread-multi-LP64

DMESG-UNCLASSIFIED: ia64dsk: The disk for dev_t bc4e0100 appears to have grown since the partition t

Node : hpux.setaoffice.com
Node Type : Itanium 64/32(HTTPS)
Severity : major
OM Server Time: 2016-01-02 21:07:51
Message : DMESG-UNCLASSIFIED: ia64dsk: The disk for dev_t bc4e0100 appears to have grown since the partition table was written.
Msg Group : OS
Application : HPUX_dmesg
Object : dmesg_UNCLASSIFIED
Event Type :
not_found

Instance Name :
not_found

Instruction : No

Checking which disks are alarming

root@hpux:~ # dmesg | grep ia64dsk
ia64dsk: The disk for dev_t bc420100 appears to have grown since the partition table was written.
ia64dsk: The disk for dev_t bc420100 appears to have grown since the partition table was written.
ia64dsk: The disk for dev_t bc420100 appears to have grown since the partition table was written.
ia64dsk: The disk for dev_t bc420100 appears to have grown since the partition table was written.
ia64dsk: The disk for dev_t bc420100 appears to have grown since the partition table was written.
ia64dsk: The disk for dev_t bc420100 appears to have grown since the partition table was written.
ia64dsk: The disk for dev_t bc420100 appears to have grown since the partition table was written.
ia64dsk: The disk for dev_t bc420100 appears to have grown since the partition table was written.
ia64dsk: The disk for dev_t bc430100 appears to have grown since the partition table was written.
ia64dsk: The disk for dev_t bc430100 appears to have grown since the partition table was written.
ia64dsk: The disk for dev_t bc430100 appears to have grown since the partition table was written.
ia64dsk: The disk for dev_t bc430100 appears to have grown since the partition table was written.
ia64dsk: The disk for dev_t bc430100 appears to have grown since the partition table was written.
ia64dsk: The disk for dev_t bc430100 appears to have grown since the partition table was written.
ia64dsk: The disk for dev_t bc430100 appears to have grown since the partition table was written.
ia64dsk: The disk for dev_t bc430100 appears to have grown since the partition table was written.
ia64dsk: The disk for dev_t bc430100 appears to have grown since the partition table was written.

Checking system device

root@hpux:~ # ls -ltraR /dev | grep 420100
crw-r—– 1 bin sys 188 0x420100 Feb 12 2015 c66t0d1
brw-r—– 1 bin sys 31 0x420100 Feb 12 2015 c66t0d1

Checking hardware path

root@hpux:~ # ioscan -kfnC disk /dev/dsk/c66t0d1
Class I H/W Path Driver S/W State H/W Type Description
==================================================================
disk 48 0/2/1/1.10.234.64.0.0.1 sdisk CLAIMED DEVICE 3PARdataVV
/dev/dsk/c66t0d1 /dev/dsk/c66t0d1s2 /dev/rdsk/c66t0d1 /dev/rdsk/c66t0d1s2
/dev/dsk/c66t0d1s1 /dev/dsk/c66t0d1s3 /dev/rdsk/c66t0d1s1 /dev/rdsk/c66t0d1s3

root@hpux:~ # ioscan -m hwpath -H 0/2/1/1.10.234.64.0.0.1
Lun H/W Path Lunpath H/W Path Legacy H/W Path
====================================================================
64000/0xfa00/0x9a
0/2/1/1.0x21230002ac001673.0x4001000000000000 0/2/1/1.10.218.65.0.0.1
0/2/1/1.10.234.64.0.0.1

root@hpux:~ # scsimgr -f replace_wwid -H 64000/0xfa00/0x9a
scsimgr: Successfully validated binding of LUN paths with new LUN.

root@hpux:~ # ls -ltraR /dev | grep 430100
crw-r—– 1 bin sys 188 0x430100 Feb 12 2015 c67t0d1
brw-r—– 1 bin sys 31 0x430100 Feb 12 2015 c67t0d1

root@hpux:~ # ioscan -kfnC disk /dev/dsk/c67t0d1
Class I H/W Path Driver S/W State H/W Type Description
==================================================================
disk 59 0/5/1/0.20.218.64.0.0.1 sdisk CLAIMED DEVICE 3PARdataVV
/dev/dsk/c67t0d1 /dev/dsk/c67t0d1s2 /dev/rdsk/c67t0d1 /dev/rdsk/c67t0d1s2
/dev/dsk/c67t0d1s1 /dev/dsk/c67t0d1s3 /dev/rdsk/c67t0d1s1 /dev/rdsk/c67t0d1s3

root@hpux:~ # ioscan -m hwpath -H 0/5/1/0.20.218.64.0.0.1
Lun H/W Path Lunpath H/W Path Legacy H/W Path
====================================================================
64000/0xfa00/0x9a
0/5/1/0.0x20240002ac001673.0x4001000000000000 0/5/1/0.20.218.64.0.0.1

root@hpux:~ # scsimgr -f replace_wwid -H 64000/0xfa00/0x9a
scsimgr: Successfully validated binding of LUN paths with new LUN.

How to rotate logs on HP-UX – logrotate

HP-UX doesn’t have logrotate.

Write a shell script to run from cron.

Or go to http://hpux.connect.org.uk/ and download logrotate and dependencies

root@hp-ux:/root # cd /tmp/logrotate_hpux
root@hp-ux:/tmp/logrotate_hpux # gunzip *

Install with swinstall

root@hp-ux:/tmp/logrotate_hpux # swinstall -s /tmp/logrotate_hpux/gettext-0.19.5.1-ia64-11.31.depot
root@hp-ux:/tmp/logrotate_hpux # swinstall -s /tmp/logrotate_hpux/libiconv-1.14-ia64-11.31.depot
root@hp-ux:/tmp/logrotate_hpux # swinstall -s /tmp/logrotate_hpux/popt-1.16-ia64-11.31.depot
root@hp-ux:/tmp/logrotate_hpux # swinstall -s /tmp/logrotate_hpux/logrotate-3.9.1-ia64-11.31.depot

Contacting Onboard Administrator and accessing iLO for an HP Integrity through command line

Connect to Onboard Administrator

emerson@myhost:~ $ telnet 10.32.33.141
Trying 10.32.33.141…
Connected to 10.32.33.141 (10.32.33.141).
Escape character is ‘^]’.

—————————————————————————–
WARNING: This is a private system. Do not attempt to login unless you are an
authorized user. Any authorized or unauthorized access and use may be moni-
tored and can result in criminal or civil prosecution under applicable law.
—————————————————————————–
Firmware Version: 3.21
Built: 11/15/2010 @ 09:59
OA Bay Number: 1
OA Role: Active
OnboardAdministrator login: Administrator
Password:

Listing all the available server on the C7000 chassis. I need to know which bay is used by hp-uxnode5

HP BladeSystem Onboard Administrator
(C) Copyright 2006-2010 Hewlett-Packard Development Company, L.P.

Type ‘HELP’ to display a list of valid commands.
Type ‘HELP ‘ to display detailed information about a specific command.
Type ‘HELP HELP’ to display more detailed information about the help system.

OnboardAdministrator> show server list

Bay iLO Name iLO IP Address Status Power UID Partner
— —————————– ————— ——– ——- — ——-
1 hp-uxnode1 10.32.33.166 OK On Off
2 hp-uxnode2 10.32.33.167 OK On Off
3 hp-uxnode3 10.32.33.168 OK On Off
4 hp-uxnode4 10.32.33.169 OK On Off
5 hp-uxnode5 10.32.33.170 OK On Off
6 hp-uxnode6 10.32.33.171 OK On Off
7 hp-uxnode7 10.32.33.172 OK On Off
8 hp-uxnode8 10.32.33.173 OK On Off
9 [Subsumed]
10 [Subsumed]
11 [Subsumed]
12 [Subsumed]
13 [Subsumed]
14 [Subsumed]
15 [Subsumed]
16 [Absent]
Totals: 8 server blades installed, 8 powered on.

Connecting to bay 5

OnboardAdministrator> CONNECT SERVER 5

Connecting to bay 5 …

Hewlett-Packard Integrated Lights-Out 3

(C) Copyright 1999-2010 Hewlett-Packard Development Company, L.P.

MP Host Name: hp-uxnode5

Revision: 01.01.02

Thu Nov 12 19:45:30 2015

*************************************************************************
MP ACCESS IS NOT SECURE
A default MP user Admin/Admin is currently configured
with the default password and remote access is enabled. Modify the
default password or delete the default user (see UC command)
OR
Disable all types of remote access (see SA command)

*************************************************************************

MP MAIN MENU:

CO: Console
VFP: Virtual Front Panel
CM: Command Menu
CL: Console Log
SL: Show Event Logs
HE: Main Help Menu
X: Exit Connection

[hp-uxnode5]</> hpiLO->

Accessing console

[hp-uxnode5]</> hpiLO-> co

[Use Ctrl-B or ESC-( to return to MP main menu.]

– – – – – – – – – – Prior Console Output – – – – – – – – – –

Login incorrect

Wait for login retry: ..

login:
– – – – – – – – – – – – Live Console – – – – – – – – – – – –

Pressed CTRL+B to go back. Exiting

MP MAIN MENU:

CO: Console
VFP: Virtual Front Panel
CM: Command Menu
CL: Console Log
SL: Show Event Logs
HE: Main Help Menu
X: Exit Connection

[hp-uxnode5]</> hpiLO-> x

Connection terminated by server.
OnboardAdministrator> exit

Connection closed by foreign host.

The legacy lun path (b 32 – t 13 – l 0) registration failed because it has been re-mapped from its original LUN (default dev 0xb000018) to a different LUN (default dev 0xc0000bd).

Checking /var/adm/syslog/syslog.log I see that lunpath, instance 81 is showing an error message

root@hp-ux:~ # grep vmunix /var/adm/syslog/syslog.log | grep “Nov 9”
Nov 9 04:37:14 hp-ux vmunix: class : lunpath, instance 81
Nov 9 04:37:14 hp-ux vmunix: The legacy lun path (b 32 – t 13 – l 0)
Nov 9 04:37:14 hp-ux vmunix: registration failed because it has been
Nov 9 04:37:14 hp-ux vmunix: re-mapped from its original LUN (default dev 0xb000018)
Nov 9 04:37:14 hp-ux vmunix: to a different LUN (default dev 0xc0000bd).
Nov 9 04:37:14 hp-ux vmunix: The administrator has to close the original LUN and
Nov 9 04:37:14 hp-ux vmunix: then validate this LUN re-mapping using the scsimgr
Nov 9 04:37:14 hp-ux vmunix: command:
Nov 9 04:37:14 hp-ux vmunix: scsimgr [-f] replace_leg_dsf -D /dev/rdsk/cxtydz

(b 32 – t 13 – l 0)
scsimgr [-f] replace_leg_dsf -D /dev/rdsk/c32t13d0

Let’s discover the hardware path for this instance

root@hp-ux:~ # scsimgr -p get_attr -C lunpath -I 81 -a hw_path
0/2/0/0/0/1.0x5001438017928fe6.0x0

Pick the LUN H/W Path

root@hp-ux:~ # ioscan -m hwpath -H 0/2/0/0/0/1.0x5001438017928fe6.0x0
Lun H/W Path Lunpath H/W Path Legacy H/W Path
====================================================================
64000/0xfa00/0xbd
0/2/0/0/0/1.0x5001438017928fe6.0x0

And run the following command

root@hp-ux:~ # scsimgr -f replace_wwid -H 64000/0xfa00/0xbd
scsimgr: Successfully validated binding of LUN paths with new LUN.

In another case, there was a missing disk. I removed the disk

root@hp-ux:~ # ioscan -fnNC disk
Class I H/W Path Driver S/W State H/W Type Description
===================================================================
disk 2 64000/0xfa00/0x0 esdisk CLAIMED DEVICE HP EH0146FARUB
/dev/disk/disk2 /dev/rdisk/disk2
/dev/disk/disk2_p1 /dev/rdisk/disk2_p1
/dev/disk/disk2_p2 /dev/rdisk/disk2_p2
/dev/disk/disk2_p3 /dev/rdisk/disk2_p3
disk 3 64000/0xfa00/0x1 esdisk CLAIMED DEVICE HP EH0146FARUB
/dev/disk/disk3 /dev/rdisk/disk3
/dev/disk/disk3_p1 /dev/rdisk/disk3_p1
/dev/disk/disk3_p2 /dev/rdisk/disk3_p2
/dev/disk/disk3_p3 /dev/rdisk/disk3_p3
disk 5 64000/0xfa00/0x2 esdisk CLAIMED DEVICE TEAC DVD-ROM DW-224EV
/dev/disk/disk5 /dev/rdisk/disk5
disk 14 64000/0xfa00/0xa esdisk CLAIMED DEVICE HP HSV340
/dev/disk/disk14 /dev/rdisk/disk14
disk 19 64000/0xfa00/0x46 esdisk NO_HW DEVICE NETAPP LUN C-Mode
/dev/disk/disk19 /dev/rdisk/disk19

root@hp-ux:~ # rmsf -H 64000/0xfa00/0x46

DMESG-UNCLASSIFIED: to probe existing LUN id 0x0 failed with errno of 6.

DMESG-UNCLASSIFIED: to probe existing LUN id 0x0 failed with errno of 6.

Node : hp-ux.setaoffice.com
Node Type : Itanium 64/32(HTTPS)
Severity : major
OM Server Time: 2015-11-06 10:30:53
Message : DMESG-UNCLASSIFIED: to probe existing LUN id 0x0 failed with errno of 6.
Msg Group : OS
Application : HPUX_dmesg
Object : dmesg_UNCLASSIFIED
Event Type :
not_found

Instance Name :
not_found

Instruction : No

 

Message showing in dmesg and /var/adm/syslog/syslog.log

root@hp-ux:/root # dmesg | grep probe
An attempt to probe existing LUN id 0x0 failed with errno of 22.
An attempt to probe existing LUN id 0x0 failed with errno of 22.

root@hp-ux:/root # grep probe /var/adm/syslog/syslog.log | tail
Nov 4 16:08:31 vlunx012 vmunix: An attempt to probe existing LUN id 0x0 failed with errno of 6.
Nov 4 16:08:31 vlunx012 vmunix: An attempt to probe existing LUN id 0x0 failed with errno of 6.
Nov 4 16:08:33 vlunx012 vmunix: An attempt to probe existing LUN id 0x0 failed with errno of 22.

Scanning the hardware and it is shown that some tapes are in NO_HW status. Removed these tapes

root@hp-ux:/root # ioscan -fnkNC lunpath | grep NO_HW
lunpath 139 0/0/4/0.0xb.0x0 eslpt NO_HW LUN_PATH LUN path for tape95
lunpath 147 0/0/4/0.0×19.0x0 eslpt NO_HW LUN_PATH LUN path for tape99
lunpath 141 0/0/4/0.0x1a.0x0 eslpt NO_HW LUN_PATH LUN path for tape96
lunpath 144 0/0/4/0.0x1c.0x0 eslpt NO_HW LUN_PATH LUN path for tape97
lunpath 155 0/0/4/0.0x1d.0x0 eslpt NO_HW LUN_PATH LUN path for tape115
lunpath 150 0/0/4/0.0x1e.0x0 eslpt NO_HW LUN_PATH LUN path for tape47
lunpath 157 0/0/4/0.0×24.0x0 eslpt NO_HW LUN_PATH LUN path for tape98
lunpath 408 0/0/6/0.0×26.0x0 eslpt NO_HW LUN_PATH LUN path for tape199
lunpath 410 0/0/6/0.0×27.0x0 eslpt NO_HW LUN_PATH LUN path for tape203
lunpath 412 0/0/6/0.0×28.0x0 eslpt NO_HW LUN_PATH LUN path for tape200
lunpath 415 0/0/6/0.0×29.0x0 eslpt NO_HW LUN_PATH LUN path for tape201
lunpath 418 0/0/6/0.0x2a.0x0 eslpt NO_HW LUN_PATH LUN path for tape212
lunpath 423 0/0/6/0.0x2b.0x0 eslpt NO_HW LUN_PATH LUN path for tape204

root@hp-ux:/root # rmsf -H 0/0/4/0.0xb.0x0
root@hp-ux:/root # rmsf -H 0/0/4/0.0×19.0x0
root@hp-ux:/root # rmsf -H 0/0/4/0.0x1a.0x0
root@hp-ux:/root # rmsf -H 0/0/4/0.0x1c.0x0
root@hp-ux:/root # rmsf -H 0/0/4/0.0x1d.0x0
root@hp-ux:/root # rmsf -H 0/0/4/0.0x1e.0x0
root@hp-ux:/root # rmsf -H 0/0/4/0.0×24.0x0
root@hp-ux:/root # rmsf -H 0/0/6/0.0×26.0x0
root@hp-ux:/root # rmsf -H 0/0/6/0.0×27.0x0
root@hp-ux:/root # rmsf -H 0/0/6/0.0×28.0x0
root@hp-ux:/root # rmsf -H 0/0/6/0.0×29.0x0
root@hp-ux:/root # rmsf -H 0/0/6/0.0x2a.0x0
root@hp-ux:/root # rmsf -H 0/0/6/0.0x2b.0x0

root@hp-ux:/root # ioscan -fnkNC lunpath | grep NO_HW
root@hp-ux:/root #

dmesg output
class : lunpath, instance 139
An attempt to probe existing LUN id 0x0 failed with errno of 22.

class : lunpath, instance 147
An attempt to probe existing LUN id 0x0 failed with errno of 22.

class : lunpath, instance 141
An attempt to probe existing LUN id 0x0 failed with errno of 22.

class : lunpath, instance 144
An attempt to probe existing LUN id 0x0 failed with errno of 22.

class : lunpath, instance 155
An attempt to probe existing LUN id 0x0 failed with errno of 22.

class : lunpath, instance 150
An attempt to probe existing LUN id 0x0 failed with errno of 22.

class : lunpath, instance 157
An attempt to probe existing LUN id 0x0 failed with errno of 22.

class : lunpath, instance 408
An attempt to probe existing LUN id 0x0 failed with errno of 22.

class : lunpath, instance 410
An attempt to probe existing LUN id 0x0 failed with errno of 22.

class : lunpath, instance 412
An attempt to probe existing LUN id 0x0 failed with errno of 22.

class : lunpath, instance 415
An attempt to probe existing LUN id 0x0 failed with errno of 22.

class : lunpath, instance 418
An attempt to probe existing LUN id 0x0 failed with errno of 22.

class : lunpath, instance 423
An attempt to probe existing LUN id 0x0 failed with errno of 22.

class : lunpath, instance 139
An attempt to probe existing LUN id 0x0 failed with errno of 22.

class : lunpath, instance 147
An attempt to probe existing LUN id 0x0 failed with errno of 22.

class : lunpath, instance 141
An attempt to probe existing LUN id 0x0 failed with errno of 22.

class : lunpath, instance 144
An attempt to probe existing LUN id 0x0 failed with errno of 22.

class : lunpath, instance 155
An attempt to probe existing LUN id 0x0 failed with errno of 22.

class : lunpath, instance 150
An attempt to probe existing LUN id 0x0 failed with errno of 22.

class : lunpath, instance 157
An attempt to probe existing LUN id 0x0 failed with errno of 22.

class : lunpath, instance 412
An attempt to probe existing LUN id 0x0 failed with errno of 22.

class : lunpath, instance 408
An attempt to probe existing LUN id 0x0 failed with errno of 22.

class : lunpath, instance 410
An attempt to probe existing LUN id 0x0 failed with errno of 22.

class : lunpath, instance 415
An attempt to probe existing LUN id 0x0 failed with errno of 22.

class : lunpath, instance 418
An attempt to probe existing LUN id 0x0 failed with errno of 22.

class : lunpath, instance 423
An attempt to probe existing LUN id 0x0 failed with errno of 22.

DMESG-UNCLASSIFIED: class :Ttggpatha i stlnse tg

DMESG-UNCLASSIFIED: class :Ttggpatha i stlnse tg

Node : hp-ux.setaoffice.com
Node Type : Itanium 64/32(HTTPS)
Severity : major
OM Server Time: 2015-11-05 19:07:46
Message : DMESG-UNCLASSIFIED: class :Ttggpatha i stlnse tg
Msg Group : OS
Application : HPUX_dmesg
Object : dmesg_UNCLASSIFIED
Event Type :
not_found

Instance Name :
not_found

Instruction : No

This is a ticket from HPOM dmesg module.
I added string Ttggpatha to /var/opt/OV/conf/OpC/dmsg_mon.cfg

root@hp-ux:~ # cat /var/opt/OV/conf/OpC/dmsg_mon.cfg
no-rewind
tgtpath
tape, instance
option failed
tgtpath
Ttggpatha

DMESG-UNCLASSIFIED: th, instance 175

Node : hp-ux.setaoffice.com
Node Type : Itanium 64/32(HTTPS)
Severity : major
OM Server Time: 2015-11-06 09:34:49
Message : DMESG-UNCLASSIFIED: th, instance 175
Msg Group : OS
Application : HPUX_dmesg
Object : dmesg_UNCLASSIFIED
Event Type :
not_found

Instance Name :
not_found

Instruction : No

Node : hp-ux.setaoffice.com
Node Type : Itanium 64/32(HTTPS)
Severity : major
OM Server Time: 2015-11-06 09:52:57
Message : DMESG-UNCLASSIFIED: evice id = loop id, for private loop devices
Msg Group : OS
Application : HPUX_dmesg
Object : dmesg_UNCLASSIFIED
Event Type :
not_found

Instance Name :
not_found

Instruction : No

Resizing filesystem online on HP-UX

Resizing filesystem online on HP-UX

Check the volume group and logical volume being used by the filesystem

root@hp-ux:/root # bdf /example
Filesystem kbytes used avail %used Mounted on
/dev/vg01/lvol14 32768 2141 28720 7% /example

This logical volume has 32MB and uses 2 PE

root@hp-ux:/root# lvdisplay /dev/vg01/lvol14
— Logical volumes —
LV Name /dev/vg01/lvol14
VG Name /dev/vg01
LV Permission read/write
LV Status available/syncd
Mirror copies 0
Consistency Recovery MWC
Schedule parallel
LV Size (Mbytes) 32
Current LE 2
Allocated PE 2
Stripes 0
Stripe Size (Kbytes) 0
Bad block on
Allocation strict
IO Timeout (Seconds) default
Each PE has 16MB and there is 1047 available

root@hp-ux:/root# vgdisplay vg01
— Volume groups —
VG Name /dev/vg01
VG Write Access read/write
VG Status available
Max LV 255
Cur LV 16
Open LV 16
Max PV 40
Cur PV 2
Act PV 2
Max PE per PV 50000
VGDA 4
PE Size (Mbytes) 16
Total PE 12796
Alloc PE 11749
Free PE 1047
Total PVG 0
Total Spare PVs 0
Total Spare PVs in use 0
VG Version 1.0
VG Max Size 31250g
VG Max Extents 2000000

Checking if it is possible to resize online the filesystem. In some HP-UX versions, this feature is not available

root@hp-ux:/root# swlist -l product | grep -i jfs
AONLINEJFS B.05.01.02 OnlineJFS 5.0.1 Integration Product
JFS B.11.31 Base VxFS File System 4.1 for HP-UX
OnlineJFS01 5.0.31.6 Online features of the VxFS File System

Extending filesystem to 5120MB

root@hp-ux:/root# lvextend -L 5120 /dev/vg01/lvol14
Logical volume “/dev/vg01/lvol14” has been successfully extended.
Volume Group configuration for /dev/vg01 has been saved in /etc/lvmconf/vg01.conf

Increased logical volume to 320 PE adn 5120MB

root@hp-ux:/root# lvdisplay /dev/vg01/lvol14
— Logical volumes —
LV Name /dev/vg01/lvol14
VG Name /dev/vg01
LV Permission read/write
LV Status available/syncd
Mirror copies 0
Consistency Recovery MWC
Schedule parallel
LV Size (Mbytes) 5120
Current LE 320
Allocated PE 320
Stripes 0
Stripe Size (Kbytes) 0
Bad block on
Allocation strict
IO Timeout (Seconds) default

Now running fsadm to increase the filesystem

root@hp-ux:/root# fsadm -F vxfs -b 5120m /example
UX:vxfs fsadm: INFO: V-3-25942: /dev/vg01/rlvol14 size increased from 32768 sectors to 5242880 sectors

root@hp-ux:/root# bdf /example
Filesystem kbytes used avail %used Mounted on
/dev/vg01/lvol14 5242880 3417 4912004 0% /example

UXMON: Cluster lock device not up: node02: /dev/disk/disk182(STATUS:unknown) check with cmviewcl

Node : node01.setaoffice.com
Node Type : Itanium 64/32(HTTPS)
Severity : major
OM Server Time: 2015-10-18 05:39:52
Message : UXMON: Cluster lock device not up: node02: /dev/disk/disk182(STATUS:unknown) check with cmviewcl -v -l node
Msg Group : OS
Application : sgmon
Object : cmviewcl
Event Type :
not_found

Instance Name :
not_found

Instruction : check with cmviewcl -v -l node ;

Do not close this case before it is resolved.
As long as this EWM-case is not resolved or closed, monitoring is disabled

Check HP Service Guard status

root@node01:/root # cmviewcl -v

CLUSTER STATUS
cluster_hpux up

NODE STATUS STATE
node01 up running

Cluster_Lock_LVM:
VOLUME_GROUP PHYSICAL_VOLUME STATUS
/dev/vglock /dev/disk/disk75 up

Network_Parameters:
INTERFACE STATUS PATH NAME
PRIMARY up LinkAgg0 lan900
PRIMARY up LinkAgg1 lan901
PRIMARY up LinkAgg2 lan902
PRIMARY up LinkAgg3 lan903

PACKAGE STATUS STATE AUTO_RUN NODE
dbciSMP up running enabled vlunx014

Policy_Parameters:
POLICY_NAME CONFIGURED_VALUE
Failover configured_node
Failback manual

Script_Parameters:
ITEM STATUS MAX_RESTARTS RESTARTS NAME
Subnet up 142.40.81.0

Node_Switching_Parameters:
NODE_TYPE STATUS SWITCHING NAME
Primary up enabled node01 (current)
Alternate unknown node02

Other_Attributes:
ATTRIBUTE_NAME ATTRIBUTE_VALUE
Style legacy
Priority no_priority

NODE STATUS STATE
node02 down halted

Cluster_Lock_LVM:
VOLUME_GROUP PHYSICAL_VOLUME STATUS
/dev/vglock /dev/disk/disk182 unknown

Network_Parameters:
INTERFACE STATUS PATH NAME
PRIMARY unknown LinkAgg0 lan900
PRIMARY unknown LinkAgg1 lan901
PRIMARY unknown LinkAgg2 lan902
PRIMARY unknown LinkAgg3 lan903

In our case, we decomissioned a cluster node so node02 is always down. We added a configuration to HPOM to disable the cluster lock check

node01:/var/opt/OV/bin/instrumentation# cp sg_mon.cfg /var/opt/OV/conf/OpC
vi /var/opt/OV/conf/OpC/sg_mon.cfg
DISABLE_CLUSTER_LOCK_CHECK = yes