Reboot of host fails Accross SAN env.

[ecorban]

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:

[Steven E. Protter]

Could you intervene at the 10 second prompt and do the following.

sea

Report the output.

Check the lights on the fabric card as well.

Report what you see.

Look at the console of the storage device and see if it indicates a connection from your machine. This interface varies between the various brands of Storage Arrays.

SEP

[Ming Zhao]

The root cause for this problem is: some SAN-attached tape libarary driver or disk LUNs have hardware problem. Until you fix the problem, the server won't boot up.

Troubleshooting procedures:
1. dis-connect all FC cables connected to the server, and reboot the server. It will be successful.
2. compare the ioscan output before and after. Try to find out which H/W have problem.
3. Check domain ID in each FC switch. make sure no conflict.
4. Check FC cable, FC switches and GBIC.

Regards,

[Pete Randall]

What happens if you hit "A" to acknowledge the entry? Does boot proceed?


Pete

[Massimo Bianchi]

Hi,
look at this:

: 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


vmunix is found, pdc is in progress, the panic is "Software failure".

I suppose there may be some kernel issue. Is this the first boot ?

Try booting in maintenance or single user

From ISL:


hpux -lm
for maintenance

hpux -is
for single user

Massimo

[Enrico P.]

Hi,
try to go in GSP mode with ctrl^b and read the error log for put off the led.
ctrl^b
sl
e
n

Therefor try to boot even.

Enrico.

[Eugeny Brychkov]

Which FC card is installed? Did you check if it supports booting over SAN? When booting capabilities of initial driver (IODC) are dependant on its version (PDC version). Thus please also check if PDC is the latest and supports booting
Eugeny

[ecorban]

The host needed to get the PDC upgraded to 42.06. Now that its upgraded it was supposed to be fixed and boot over a fabric.

The host is a HPUX 11.00 host connected through a 6795A hba with HWE1100 MArch 03 to an FC10 disk in nl mode. This shouldn't matter.
HP supports a dump device of 7GB and an install device of at least 18GB size. We meet all there requirements here

The problem seems to be a kernel problem as the prev respondent recognised that vmunix is loaded and it fails after that. Now it seems the kernel just doesnt like the swap size or default partitions size which is causing it to fail to boot.

If you ACK the message it resets and fails
again.

If you disconect the f port it boots of an internal disk, not really an valid option or test as we want to test this feature of booting accross a fabric.

This is not a h/w realted problem. the host login at pdc as loop, gbics switch cables are all fine, switch indicates this. FC10 device was trashed before using it as a boot disk so the disk is ok, in fact a previous disk was used for remote dump accross a SAN so theres no problem here with any HW.....

This seems to be kernel related............

Booting in single user or maintenance mode
have no effect....

What i want to know is how do i turn off/clear/delete the ALERTS/Error messages in the PDC or GSP area so none of these messages are logged any more. Please respond if you know how to do this!