Hi Everyone,
We have a AIX server that boots from a NetApp (IBM nSeries) for which we need to upgrade AIX. The AIX Admins want me to allocate a alt_boot lun, which they will make the new boot lun after upgrading.
Currently the server has two luns:
lun show -m LUN path Mapped to LUN ID Protocol ----------------------------------------------------------------------- /vol/v_rsxxxx_boot/q_rsxxxx_boot/lun0_boot rsxxxx 0 FCP /vol/v_rsxxxx_boot/q_rsxxxx_boot/lun1_boot rsxxxx 1 FCP
lun 0 = rootvg boot lun lun 1 = non-rootvg lun with paging space
If I create a new lun at id 2, we cut over to it and I delete the old boot vol at id 0, I then have a lun id gap - no lun 0.
Is this a problem with NetApp storage?
(I know we have problems with EMC VNX storage with LUNZ devices if no lun id at 0.)
Rick
----------------------------------------- The information contained in this message is intended only for the personal and confidential use of the recipient(s) named above. If the reader of this message is not the intended recipient or an agent responsible for delivering it to the intended recipient, you are hereby notified that you have received this document in error and that any review, dissemination, distribution, or copying of this message is strictly prohibited. If you have received this communication in error, please notify us immediately, and delete the original message.