Datasheet

Figure 3: Example of what the client partition sees as storage.

Storage spaces for an IBM i client partition do not have to match physical disk sizes; they can be

created from 160 MB to 1 TB in size, as long as there is available storage in the host. The 160

MB minimum size is a requirement from the storage management Licensed Internal Code (LIC)

on the client partition. For an IBM i client partition, up to 16 NWSSTGs can be linked to a single

NWSD, and therefore, to a single VSCSI connection. Up to 32 outstanding I/O operations from

the client to each storage space are supported for IBM i clients. Storage spaces can be created

in any existing auxiliary storage pool (ASP) on the host, including Independent ASPs. Through

the use of NWSSTGs, any physical storage supported in the IBM i host partition can be used to

provide virtual disk storage to a client partition.

For performance reasons, consider creating multiple storage spaces associated with multiple

NWSDs. The rule of thumb is six to eight storage spaces for each client partition at a minimum.

This implies that you are also creating multiple sets of VSCSI adapter pairs between the hosting

partition and the client partition. Associate each hosting partition’s server VSCSI adapter with a

separate NWSD by referencing the VSCSI adapter’s resource name in the NWSD. Then link

storage spaces to the NWSDs. This will supply multiple disk arms for the client partition to use.

2.1.2.2 Tape virtualization

Specific IOP-less attached physical tape devices supported in the host IBM i LPAR can be

virtualized to an IBM i client LPAR. See the links below for specific details. An existing VSCSI

connection can be used, or a new connection can be created explicitly for tape I/O traffic. By

default, if a VSCSI connection exists between the host and the client, all TAPxx drives supported

for virtualization by the host will be available to the client, where they will also be recognized as

TAPxx devices. The NWSD parameter Restricted device resources can be used to specify

which tape devices in the host a client partition cannot access.

A virtualized tape drive in the host partition can be used for a D-mode initial program load (IPL)

and for the install of the client partition or its applications. The client partition will be able to write

to the physical media in the drive. Although Virtual tape devices backed by image catalogs

(TAPVRTxx) cannot be virtualized to an IBM i client. These restrictions are documented in the

IBM i InfoCenter at:

http://publib.boulder.ibm.com/infocenter/iseries/v7r1m0/index.jsp?topic=%2Frzam4%2Frzam4clie

ntvirtdevices.htm

For the current list of supported tape libraries and associated operating system levels please refer

to the DevelopWorks web page for IBM Removable Media on IBM i:

https://www.ibm.com/developerworks/mydeveloperworks/wikis/home?lang=en#/wiki/IBM%20Rem

ovable%20Media%20on%20IBM%20i