config Dump to be on remote disk in SAN and boot over SAN

[ecorban]

2 part question/problem.

What is the procedure to setup a host so that if i force a dump on the TOC GSP on the console it populates that remote disk in the fabric. I have setup a remote disk and configured a lvol (vxfs FS type)and mount it but when i try and change the lvlnboot -d to be this new device it fails with the error "the disk must be contiguous"

@nd question;

After i install a hpux 11.00 host successfully accross a brocade fabric, when i try and reboot the host after the installation it fails on the console with the following error
messages;
How can i fix the fabric host to boot off the FC10 disk connects in nl mode in the fabric
10 seconds expired.
Proceeding...

Trying Primary Boot Path
------------------------
Booting...
Boot IO Dependent Code (IODC) revision 2


HARD Booted.

ISL Revision A.00.38 OCT 26, 1994

ISL booting hpux

Boot
: disk(0/4/0/0.146.11.255.7.6.0;0)/stand/vmunix
6610944 + 856176 + 757768 start 0x21ac68


alloc_pdc_pages: Relocating PDC from 0xf0f0000000 to 0x1faab000.
gate64: sysvec_vaddr = 0xc0002000 for 1 pages
NOTICE: nfs3_link(): File system was registered at index 3.
NOTICE: autofs_link(): File system was registered at index 6.

System Console is on the Built-In Serial Interface
Swap device table: (start & size given in 512-byte blocks)

************* SYSTEM ALERT **************
SYSTEM NAME: cp074116
DATE: 07/29/2003 TIME: 23:16:38
ALERT LEVEL: 12 = Software failure

REASON FOR ALERT
SOURCE: 1 = processor
SOURCE DETAIL: 1 = processor general SOURCE ID: 0
PROBLEM DETAIL: 0 = no problem detail

LEDs: RUN ATTENTION FAULT REMOTE POWER
FLASH FLASH OFF ON ON
LED State: Running non-OS code. Non-critical error detected. Check Chassis and Console Logs for error messages.

0xF8E000C01100B800 00000000 0000B800 - type 31 = legacy PA HEX chassis-code 0x58E008C01100B800 00006706 1D171026 - type 11 = Timestamp 07/29/2003 23:16:38
A: ack read of this entry - X: Disable all future alert messages Anything else skip redisplay the log entry
->Choice:

[Tim Adamson_1]

Hi Eddie,

If you are using a Logical Volume for your dump device the following rules apply:

??? Each logical volume to be used as a dump device must be part of the root volume group (vg00). For details on configuring logical volumes as kernel dump devices, see the lvlnboot (1M) manpage.
??? The logical volumes to be used as dump devices must be contiguous (no disk striping, or bad-block reallocation is permitted for dump
logical volumes)
??? The logical volume cannot be used for file system storage, because the whole logical volume will be used.

So, is the dump volume a logical volume and if so, does it meet the above requirements?

To create a contiguous lvol and ensure bad block relocation is off, you need to use the "-C y -r n" options to lvcreate.


As for your second part of the question, I am not sure it is supported. When you boot, can you do a "SEA" to search for bootable devices? Does the disk show up?


Cheers!!