Is see that some disks have a failed path on fscsi2. Other disks are just running fine with a path over fscsi2.
May I conclude that the hardware is working and that ther is a problem with the zoning of the SAN? Or could HW still be a problemen? All LUNS are provided from the same SAN storage box meaning that if hdisk23 is available on all paths, the cables between the SAN box and the server are correct.
you get each disk over 2 fc adapters to the vio server, and each fc adapter is zoned to two storage controllers
depending on the san design, this may be due to a temporary problem with the fc adapter, or a san switch
first I would try to get the paths online manually
smitty mpio -> MPIO Path Management -> Enable Paths -> Enable Selected or All Paths
and choose all paths, then run the lspath command again
depending on the storage subsystem you may have to work with the device drivers (sddpcm) for example
if this happens more often, you may want to open an ibm call, but first talk to your storage/san admins
Have you always had each of your fibercards zoned to two different storage controllers? When we had dual fibercards and we had a one-to-one mapping between our fibercards and the storage controllers. Then we used MPIO to put the 2 paths (instead of 4) together. I didn't even know doing it the way you are was even possible.
it's been a while when I was working with rdac, but afaik each lun is presented by one storage controller, and in case the adapter zoned to this controller fails, the storage moves the lun to the other controller, which leads to a few seconds of time where the lun is not accessible
but our zoning was different, each adapter just saw one controller, maybe this has changed in the meantime