On Fri, Apr 14, 2023 at 05:45:32PM +0000, Luis Alberto Rojas Kramer via IBM Community wrote:
> Does somebody know how to avoid this problem happen?
I do not recommend boot from SAN with anything other than IBM storage
with a native AIX driver (ie: MPIO in base OS).
I've had very poor experiences booting from SAN using PowerPath in the
past, and EMC storage. Typically it took a mksysb restore to new LUNs
to fix. Migratepv of rootvg wasn't bootable.
> We thought that maybe a vscsi disk from VIOS to LPARs could help,
> but, I can't believe every customer with EMC Systems should live
> with that problem.
In the case of a customer environment with a non-IBM SAN where boot
from SAN is desired, VSCSI is the proper solution. The SCSI drivers
are native to AIX, and the VIO server can manage the SAN storage and
paths.
It's not as complex as it sounds. Give your LPAR two VSCSI disks for
boot via SAN LUNs mapped through VIO, and then give the LPAR NPIV
adapters for data LUNs. The newer HMC GUI makes mapping VSCSI disks
easy.
You want two boot LUNs so that you have a second drive for
alt_disk_copy and maintenance. Not for mirroring. Remember to set the
queue depth on the client to match the SAN LUN.
That also means you boot VIO locally, and not from SAN.
Good luck.
------------------------------------------------------------------
Russell Adams
Russell.Adams@AdamsSystems.nlPrincipal Consultant Adams Systems Consultancy
https://adamssystems.nl/
Original Message:
Sent: 4/14/2023 1:46:00 PM
From: Luis Alberto Rojas Kramer
Subject: Error 554 with DELL (EMC) SAN Storage boot disk.
Hi experts..
We have an issue here at AIX booting time with EMC (Dell) SAN Storage System due path lost.
After seeing Kernel Starting message, suddenly stops at 554 LED code because booting process can't find the path from it had been accessing the IPL disk.
EMC told us we should reduce to just one path only from Storage to Server to avoid use other path which the Storage System is not offer the active path to these boot disk.
But doing that, is a problem and represent a task which takes SysAdmin time and could incur in risks by human errors every time an LPAR needs to be booted; like unmap virtual FibreChannel adapters or unconfigure SAN Switches zoning or delete WWPN from the host attachment config at Storage System.
Does somebody know how to avoid this problem happen?
We thought that maybe a vscsi disk from VIOS to LPARs could help, but, I can't believe every customer with EMC Systems should live with that problem.
Regards
------------------------------
Luis Alberto Rojas Kramer
------------------------------