What is NPIV and why is it important?

What is NPIV and why is it important?

What is NPIV and why is it important? What are the considerations for using NPIV in a virtualized environment?

    Requires Free Membership to View

    When you register, my team of editors will also send you the latest expert resources covering all areas of server virtualization, such as platforms, architectures and strategies, server hardware, managing virtual environments, application issues and more.

    Cathleen A. Gagne, Senior Editorial Director

    By submitting your registration information to SearchServerVirtualization.com you agree to receive email communications from TechTarget and TechTarget partners. We encourage you to read our Privacy Policy which contains important disclosures about how we collect and use your registration and other information. If you reside outside of the United States, by submitting this registration information you consent to having your personal data transferred to and processed in the United States. Your use of SearchServerVirtualization.com is governed by our Terms of Use. You may contact us at webmaster@TechTarget.com.

NPIV is an extension to a standard already defined in the fibre channel protocols that allows one to get past single initiator/single target design limitations. In order for you to take advantage of this, both the HBA (in the host and the storage array) and the switch must support NPIV to generate and publish (allow) an additional world wide port name (WWPN) in a virtual fashion. There is an inevitable collision of ideals going on here, in that virtual server environments want to use virtual storage environments. With the HBA, the switch and the storage array having the ability to create the "virtual" fabric, it will allow for single use connections, similar to VPNs or VLANs or other technologies that want a "dedicated" and secure path from the virtual server to the virtual LUN, with LUN masking and communications intact from point-to-point. This allows for traffic segregation and addresses a host of other potential storage area network issues.

This was first published in May 2007