Professional Documents
Culture Documents
Npiv - Vug 12-18-2008
Npiv - Vug 12-18-2008
October 2008
NPIV Overview
N_Port ID Virtualization (NPIV) is a fibre channel industry standard
so a physical fibre channel HBA can be shared across multiple guest operating systems in a virtual environment.
On POWER, NPIV allows logical partitions (LPARs) to have
dedicated N_Port IDs, giving the OS a unique identity to the SAN, just as if it had a dedicated physical HBA(s).
NPIV specifics
PowerVM VIOS 2.1 - GA Nov 14 NPIV support now has planned GA of Dec 19 Required software levels
VIOS Fix Pack 20.1 AIX 5.3 TL9 SP2 AIX 6.1 TL2 SP2 HMC 7.3.4 FW Ex340_036 Linux and IBM i planned for 2009
Required HW
POWER6 520,550,560,570 only at this time, Blade planned for 2009 5735 PCIe 8Gb Fibre Channel Adapter
unique WWPN generation (allocated in pairs)*** Each virtual FC HBA has a unique and persistent identity Compatible with LPM (live partition mobility) VIOS can support NPIV and vSCSI simultaneously Each physical NPIV capable FC HBA will support 64 virtual ports HMC-managed and IVM-managed servers
Storage Virtualisation
VIO client Generic SCSI disk Virtual SCSI Adapters SCSI SAS vSCSI VIOS Note Path code And Devices difference
VI O With NPIV S
VIO client EMC 5000 LUN Virtual FC Adapters
2. 1
VIOS
FC Adapters
FC Adapters
Storage Virtualiser
HMC 7.3.4
AIX 5.3 TL09, AIX 6.1 TL02, SLES 10 SP2, RHEL 4.7, RHEL 5.2 New EL340 Firmware (disruptive) VIOS 2.1
POWER6 only
VIO client EMC 5000 LUN
VI O S
Virtual FC Adapters
2. 1
VIOS
FC Adapters
New PCIe 8Gbit Fibre Channel adapters (can run 2 or 4 Gbit) Entry SAN switch must be NPIV capable Disk Sub-System does not need to be NPIV capable SAN Fabric can be 2, 4 or 8 Gbit (not 1 Gbit)
IBM 4700 LUN
VI O S
NPIV What you do?
2. 1
1.
VI O S
NPIV What you do?
2. 1
2.
Once Created: LPAR Config Manage Profiles Edit click FC Adapter Properties and the WWPN is available
VI O S
NPIV What you do?
$ ioslevel 2.1.0.0 $ lsdev | grep FC fcs0 Available FC Adapter fscsi0 Available FC SCSI I/O Controller Protocol Device vfchost0 Available Virtual FC Server Adapter $ vfcmap -vadapter vfchost0 -fcp fcs0 vfchost0 changed $
3.
2. 1
4.
SAN Zoning
To allow the LPAR access to the LUN via the new WWPN Allow both WWPN and on any Partition Mobility target.
NPIV benefits
NPIV allows storage administrators to used existing tools
NPIV implementation
Install the correct levels of VIOS, firmware, HMC,8G HBAs,
client VFC
Server and Client VFCs are mapped one-to-one with the
available for use with the prefix in the vital product data on the managed system.
The hypervisor does not reuse the WWPNs that are assigned to the virtual
Things to consider
WWPN pair is generated EACH time you create a VFC. NEVER is re-created or re-used. Just like a real HBA. If you create a new VFC, you get a NEW pair of WWPNs. Save the partition profile with VFCs in it. Make a copy, dont delete a profile with a VFCin it. Make sure the partition profile is backed up for local and disaster recovery! Otherwise youll have to create new VFCs and map to them during a recovery. Target Storage SUBSYSTEM must be zoned and visible from source and destination systems for LPM to work. Active/Passive storage controllers must BOTH be in the SAN zone for LPM to work Do NOT include the VIOS physical 8G adapter WWPNs in the zone You should NOT see any NPIV LUNs in the VIOS Load multi-path code in the client LPAR, NOT in the VIOS Monitor VIOS CPU and Memory NPIV impact is unclear to me at this time No passthru tunables in VIOS
switch.
lscfg -vl fcsx In A(X client lpar, shows virtual fibre channel properties
NPIV resources
Redbooks:
SG24-7590-01 PowerVM Virtualization on IBM Power Systems (Volume 2): Managing and Monitoring SG24-7460-01 IBM PowerVM Live Partition Mobility
Questions
OM3 - multimode 50/125 micron fibre, 2000 MHz*km bandwidth 2Gb (.5 500m) 4Gb (.5 380m) 8Gb (,5 150m) OM2 - multimode 50/125 micron fibre, 500 MHz*km bandwidth 2Gb (.5 150m) 4Gb (.5 70m) 8Gb (,5 21m) OM1 - multimode 62.5/125 micron fibre, 200 MHz*km bandwidth 2Gb (.5 300m) 4Gb (.5 150m) 8Gb (,5 50m)
Virtual SCSI
client LPAR (ie virtual machine) is the SCSI initiator, VIOS is the SCSI Target server LPAR owns physical I/O resources client LPAR sees standard SCSI devices, accesses LUNs via a virtual SCSI adapter VIOS is a standard storage subsystem transport layer is the interpartition communication channel provided by PHYP (reliable msg transport) SRP(SCSI Remote DMA Protocol) LRDMA(logical redirected DMA)
I/O client
I/O client
I/O client
PHYP
vSCSI
vio client generic scsi disk SCSI
VIOS VIOS VIOS
NPIV
vio client EMC EMC FCP
VIOS
IBM 2105
FC HBAs
FC HBAs
FC HBAs
FC HBAs
SAN
SAN
EMC
IBM 2105
EMC
IBM 2105
The vSCSI model for sharing storage resources is storage virtualizer. Heterogeneous storage is pooled by the VIOS into a homogeneous pool of block storage and then allocated to client LPARs in the form of generic SCSI LUNs. The VIOS performs SCSI emulation and acts as the SCSI Target.
With NPIV, the VIOS's role is fundamentally different. The VIOS facilitates adapter sharing only, there is no device level abstraction or emulation. Rather than a storage virtualizer, the VIOS serving NPIV is a passthru, providing an FCP connection from the client to the SAN.
vSCSI
VIOS AIX VIOS
LVM multipathing
LVM
LVM multipathing
Disk Driver
VSCSI target
VSCSI HBA
VSCSI HBA
VSCSI target
SAN
NPIV
VIOS AIX VIOS
LVM
multipathing
VFC HBA VFC HBA VFC HBA VFC HBA VFC HBA PHYP VFC HBA VFC HBA VFC HBA
Disk Driver
passthru module
VFC HBA
VFC HBA
passthru module
SAN
vio client
N P I V
WWPN
vio client
WWPN
N P I V
WWPN WWPN
vio client
WWPN
vio client
VIOS
VIOS
WWPN
vio client
N P I V
WWPN
N P I V
vio client
WWPN
WWPN
vio client
WWPN
vio client
WWPN WWPN
N P I V
WWPN WWPN
vio client
vio client
WWPN
WWPN
vio client
VIOS
VIOS
IBM System p
Heterogeneous multipathing
VIOS#1 Passthru module
AIX
A
NPIV
NPIV
Fibre HBA
POWER Hypervisor
Storage Controller
SAN Switch SAN Switch
Fibre HBA
D C D
POWER Server
passthru module
LPARs
block virtualization
filesystems LVM multi-pathing disk | optical physical adapters FC/NPIV | SCSI | iSCSI | SAS | USB | SATA
virtual devices back by a file virtual devices backed by a logical volume virtual devices backed by a pathing device virtual devices physical peripheral device virtual tape NPIV
physical storage
POWER Server
physical storage
Fibre channel, iSCSI, SAS, SCSI, USB, SATA
a1 b1
b6
b3 b2 b1
b5
b4
a2
c1: /dev/fscsi0
e1
vSCSI Target
PHYP
vscsi client
data buffer
Da ta
vscsi initiator vscsi target
I/O server
physical adapter driver
(L RD M
control
A)
phyp
pci adapter
I/O Server
AIX client
MPIO
I/O Server
disk driver
vscsi target
vscsi initiator
vscsi initiator
vscsi target
PHYP
SAN
data buffer
Da ta
phyp
FC HBA
SCSI Initiator
VIOS
data buffer
Da ta
VFC client
passthru module
phyp
FC HBA
SCSI Initiator
Testing VIOS
physical fibre chan HBA
POWER5 Server
Linux AIX
VIOS
v S C S I
AIX
AIX
AIX
AIX
A1 A2 A3 A4 A5 A6
A7 A8
Virtual SCSI
POWER Hypervisor
physical physical fibre chan fibre chan HBA HBA
A1 A2 A3 A4 A5 A6 A7 A8
Available via optional Advanced POWER Virtualization or POWER Hypervisor and VIOS features.
OM3 - multimode 50/125 micron fibre, 2000 MHz*km bandwidth 2Gb (.5 500m) 4Gb (.5 380m) 8Gb (,5 150m) OM2 - multimode 50/125 micron fibre, 500 MHz*km bandwidth 2Gb (.5 150m) 4Gb (.5 70m) 8Gb (,5 21m) OM1 - multimode 62.5/125 micron fibre, 200 MHz*km bandwidth 2Gb (.5 300m) 4Gb (.5 150m) 8Gb (,5 50m)
Questions
Special notices
This document was developed for IBM offerings in the United States as of the date of publication. IBM may not make these offerings available in other countries, and the information is subject to change without notice. Consult your local IBM business contact for information on the IBM offerings available in your area. Information in this document concerning non-IBM products was obtained from the suppliers of these products or other public sources. Questions on the capabilities of non-IBM products should be addressed to the suppliers of those products. IBM may have patents or pending patent applications covering subject matter in this document. The furnishing of this document does not give you any license to these patents. Send license inquires, in writing, to IBM Director of Licensing, IBM Corporation, New Castle Drive, Armonk, NY 10504-1785 USA. All statements regarding IBM future direction and intent are subject to change or withdrawal without notice, and represent goals and objectives only. The information contained in this document has not been submitted to any formal IBM test and is provided "AS IS" with no warranties or guarantees either expressed or implied. All examples cited or described in this document are presented as illustrations of the manner in which some IBM products can be used and the results that may be achieved. Actual environmental costs and performance characteristics will vary depending on individual client configurations and conditions. IBM Global Financing offerings are provided through IBM Credit Corporation in the United States and other IBM subsidiaries and divisions worldwide to qualified commercial and government clients. Rates are based on a client's credit rating, financing terms, offering type, equipment type and options, and may vary by country. Other restrictions may apply. Rates and offerings are subject to change, extension or withdrawal without notice. IBM is not responsible for printing errors in this document that result in pricing or information inaccuracies. All prices shown are IBM's United States suggested list prices and are subject to change without notice; reseller prices may vary. IBM hardware products are manufactured from new parts, or new and serviceable used parts. Regardless, our warranty terms apply. Any performance data contained in this document was determined in a controlled environment. Actual results may vary significantly and are dependent on many factors including system hardware configuration and software design and configuration. Some measurements quoted in this document may have been made on development-level systems. There is no guarantee these measurements will be the same on generallyavailable systems. Some measurements quoted in this document may have been estimated through extrapolation. Users of this document should verify the applicable data for their specific environment.