Sysdump on local disk

Hello Team,

Our p740 systems are booting up from SAN. We would like to configure the local disk\(which is not part of rootvg\) as a primary dump device.  I have assigned the same too. But in the errpt throwing the below error. Please help me on this.
---------------------------------------------------------------------------
LABEL:          DMPCHK_NODUMPACCESS
IDENTIFIER:     6D87B1C0

Date/Time:       Sun Oct 21 15:00:13 GMT+03:00 2012
Sequence Number: 68138
Machine Id:      00F69DD24C00
Node Id:         hostname
Class:           O
Type:            UNKN
WPAR:            Global
Resource Name:   dumpcheck

Description
The dump device can not be accessed

Probable Causes
The access to the dump device is currently unavailable

        Recommended Actions
        Check the dump device access and configuration.

Detail Data
Dump Device
hdisk0
root@[/home/root]# sysdumpdev -l
primary              /dev/hdisk0
secondary            /dev/sysdumpnull
copy directory       /var/adm/ras
forced copy flag     TRUE
always allow dump    TRUE
dump compression     ON
type of dump         traditional
root@[/home/root]#  sysdumpdev -e
0453-041 Estimated dump size in bytes: 873254092
root@[/home/root]# bootinfo -s hdisk0
25600
root@[/home/root]#lsdev -Cc disk | grep hdisk0
hdisk0      Available          Virtual SCSI Disk Drive
root@[/home/root]# lspv | grep hdisk0
hdisk0          00f69dd24640c289                    dumpvg          active
root@[/home/root]#lsvg -l rootvg  | grep dump
livedump            jfs2       4       4       1    open/syncd    /var/adm/ras/livedump
pridump             sysdump    10      10      1    closed/syncd  N/A


:wall:
Regards,
Gowtham.G

I have never even attempted this, so i can't definitely say if it is possible or not, but it feels wrong from the start - even if it might work somehow. You need the dump device for immediate access during the boot process and you have only the designated boot disk(s) in this step of the process available. Varying on the rootvg / mounting its filesystems and only then varying on the other VGs comes relatively late (and definitely later than the access to the boot disk is needed).

So, even if you might get this to work (what i doubt) this would be more like a bug in the AIX boot process than a feature and should be corrected.

Btw., "booting from SAN" is not enough information: booting from LUNs managed by a VIO-Server is fundamentally different from booting from NPIV devices. In this case, it doesn't make a difference because for reasons stated above the idea is wrong regardless of which media you boot from - LUNs, local disks, whatever.

I hope this helps.

bakunin

1 Like