I apologize if this is a little off-topic, but it does relate to Xen and using
NPIV on Xen, so I think this is an appropriate forum for the question. I've
recently begun using NPIV for a couple of Xen PV domUs rather than traditional
disk passthrough. My reasons are primarily for performance - I'm hoping that
NPIV has lower overhead and lower reliance on the resources of dom0 so that the
performance in the domU is better. In any case, I did a firmware update on my
SAN controllers last evening, an upgrade that was not supposed to impact
connectivity to the SAN, as I have redundant SAN controllers and the upgrade
reset the controllers in sequence so that hosts would still be able to talk to
the SAN. This worked perfectly for all of my physical machines and virtual
machines, except for the ones using NPIV, which crashed miserably. I ended up
having to reboot my dom0/host to get it to see the disks correctly. I'm
wondering if anyone has any experience with this, or any hints on configuring
NPIV correctly for a fail-over situation? My disk configuration is as follows:
As you can see, I'm attaching one disk via passthrough (my system disk), and
the other three via npiv (data volumes). The fourth and final set of hex
numbers there is the WWN of one of the FC ports on one of my SAN controllers.
I'm still a little fuzzy on how my SAN handles the failover, but I'm wondering
if the fact that I'm pointing at a specific WWN is causing problems?
Any help/advice would be appreciated!
This e-mail may contain confidential and privileged material for the sole use
of the intended recipient. If this email is not intended for you, or you are
not responsible for the delivery of this message to the intended recipient,
please note that this message may contain SEAKR Engineering (SEAKR)
Privileged/Proprietary Information. In such a case, you are strictly
prohibited from downloading, photocopying, distributing or otherwise using this
message, its contents or attachments in any way. If you have received this
message in error, please notify us immediately by replying to this e-mail and
delete the message from your mailbox. Information contained in this message
that does not relate to the business of SEAKR is neither endorsed by nor
attributable to SEAKR.
Xen-users mailing list