IBM I Removable Media Tape and Tape Library Devices - 29 Aug 2023
IBM I Removable Media Tape and Tape Library Devices - 29 Aug 2023
IBM I Removable Media Tape and Tape Library Devices - 29 Aug 2023
Library Devices
News
Abstract
This document contains information about the tape and tape library devices that IBM i supports.
Content
Native IOPless support for Fibre Channel, Serial Attached SCSI (SAS), and SCSI
LVD Tape
Fibre Channel Tape library devices attached by using N Port ID Virtualization
(NPIV) with VIOS
Client Virtual Tape Devices
Virtual IO Server (VIOS) partition owned SAS and USB Tape Drives
Considerations for attaching SAS tape and tape library devices to IBM i
ProtecTIER code levels for IBM i attachement
DSI VTL sizing
Alternate restart (D-IPL) device rules
Tape Media Libraries on IBM i
Reassigning cartridges when the system name changes
Note: For the LTO9 tape drives, media optimization is performed on the first load of each
piece of L9 or LZ media. Media optimization averages 40 minutes per first load of a cartridge
to a tape drive. Although most media optimizations complete within 60 minutes, some media
optimizations can take up to 2 hours. Do not use the tape drives during the media optimization
process.
SLR60 30 GB SCSI FC5753, 7207 330, 7212 with FC1107 (Not supported by release
IBM i 7.2, 7.3, 7.4, or 7.5)
SLR100 50 GB SCSI FC5754, 7212 with FC1108 (Not supported by release IBM i 7.2,
7.3, 7.4, or 7.5)
VXA-2 80 GB SCSI FC1889, 7206 VX2, 7212 with FC1104 (Not supported by release
IBM i 7.2, 7.3, 7.4, or 7.5)
VXA-320 160 GB SCSI FC6279, 7206 VX3, 7212 with FC1114 (Not supported by
release IBM i 7.2, 7.3, 7.4, or 7.5)
HH LTO-2 200 GB SCSI FC5755, 7212 with FC1109 (Not supported by release IBM i
7.2, 7.3, 7.4, or 7.5)
DAT72 36 GB SCSI FC6258, 7206 336, 7212 with FC1105 (Not supported by release
IBM i 7.2, 7.3, 7.4, or 7.5)
HH LTO-3 400 GB SCSI (TS2230) (Not supported by release IBM i 7.4 or 7.5)
DAT72 36 GB SAS FC5907, 7214 with FC1400 (Not supported by release IBM i 7.4 or
7.5)
DAT160 80 GB SAS FC5619, 7214 with FC1401 (Not supported by release IBM i 7.4 or
7.5)
HH LTO-4 800 GB SAS FC5746, 7214 with FC1404 (Not supported by release IBM i
7.5)
TS2240 LTO-4 HH SAS stand-alone Tape drive (Not supported by release IBM i 7.5)
TS2340 LTO-4 SAS stand-alone Tape drive (Not supported by release IBM i 7.5)
3572 (TS2900) with SAS LTO 4 drives (Not supported by release IBM i 7.5)
3573 (TS3100, TS3200) with SAS LTO4 drives and Fibre Channel LTO3 or LTO4
drives. (Only the Fibre Channel LTO4 drives are supported by release IBM i 7.5)
3576 (TS3310) with SAS LTO4 drives and Fibre Channel LTO3 or LTO4 drives. (Only
the Fibre Channel LTO4 drives are supported by release IBM i 7.5)
3577 (TS3400) with Fibre Channel 3592-E05 or 3592-E06 drives. (Not supported by
release IBM i 7.5)
3584 (TS3500) with Fibre Channel LTO2, LTO3, LTO4, 3592-J1A, 3592-E05 (TS1120),
and 3592-E06 (TS1130) drives (Only the LTO4 and TS1130 drives are supported by
release IBM i 7.5)
3592-J1A, 3592-E05(TS1120), and 3592-E06(TS1130) stand-alone drives. (Only the
TS1130 drives are supported by release IBM i 7.5)
DAT160 80 GB SAS 7226 with FC5619 (Not supported by release IBM i 7.4 or 7.5)
DAT320 160 GB SAS FC5661, 7214 with FC1402, 7216 with FC1402 (Not supported
by release IBM i 7.4 or 7.5)
HH LTO-5 1.5 TB SAS FC5638, 7216 with FC8247, 7226 with FC8247
HH LTO6 2.5 TB SAS FCEU11, 7226 with FC8341
TS2250 LTO-5 SAS HH stand-alone Tape drive
TS2350 LTO-5 SAS stand-alone Tape drive
TS2260 LTO-6 SAS HH stand-alone Tape drive
TS2360 LTO-6 SAS stand-alone Tape drive
FC 8248 HH-LTO5 FC in 7226 enclosure
FC8348 HH LTO6 Fibre Channel in 7226 enclosure
3572 (TS2900) with SAS LTO5 and LTO6 drives.
3573 (TS3100, TS3200) with SAS and Fibre Channel LTO5 and LTO6 drives
3576 (TS3310) with Fibre Channel LTO5 and LTO6 drives
3584 (TS3500) with Fibre Channel LTO5, LTO6, 3592-E07 (TS1140), and 3592-E08
(TS1150) drives.
3584 (TS4500) with Fibre Channel LTO5, LTO6, 3592-E07 (TS1140), and 3592-EH8
(TS1150) drives.
3592-E07(TS1140) stand-alone drives
Additional devices supported by release 7.4 TR8 and 7.5 TR2 or later and Power10 servers:
Notes:
1. IOPless attach of SAS and Fibre Channel devices requires POWER6 or later hardware.
2. If a SAS tape or library device is shared between partitions, an IPL of the adapter or
partition will disrupt any operation that uses the device from the other partition, even if
the device is assigned to the other partition
3. IOPless attach of SCSI tape libraries is not supported.
4. No internal SCSI tape devices are supported on POWER7 or later Systems.
5. A 63A03202 or 63A03400 PAL is logged when an unsupported device is attached.
6. 8Gb Fibre Channel tape drives can be directly attached to 8Gb Fibre channel adapters or
by using a SAN switch
7. LTO5, LTO6, LTO7, LTO8, LTO9, TS1140, TS1155, TS1160, and TS1170 drives are
NOT supported by the older IOP-based configurations.
8. With IBM i 7.5 TR8 or IBM i 7.5 TR2 or later an 8Gb Fibre channel tape drive can be
directly attached to adapter features EN1J/EN1K (CCIN 579C) on a Power10 server
without needing a SAN switch. If the tape drive is in a tape library device, the drive
ports must be configured to run Fibre Channel Arbitrated Loop (FC-AL).
3573 (TS3100/TS3200) with LTO3, LTO4, LTO5, LTO6, LTO7, and LTO8 tape drives (LTO3 not
supported by release IBM i 7.5)
3576 (TS3310) with LTO3, LTO4, LTO5, LTO6, LTO7, and LTO8 tape drives (LTO3 not supported by
release IBM i 7.5)
3577 (TS3400) with TS1120 and TS1130 tape drives (Not supported by release IBM i 7.5)
3584 (TS3500) with LTO3, LTO4, LTO5, LTO6, TS1120, TS1130, 3592-E07 (TS1140), 3592-E08
(TS1150), and 3592-J1A tape drives (LTO3 and TS1120 not supported by release IBM i 7.5)
3584 (TS4500) with Fibre Channel LTO5, LTO6, 3592-E07 (TS1140), and 3592-EH8 (TS1150)
drives
TS1130 and TS1140 stand-alone drives
FC 8248 HH-LTO5 FC in 7226 enclosure
FC 8348 HH-LTO6 FC in 7226 enclosure
Note: The devices cannot be directly attached. They much be attached through an NPIV capable
switch.
Note: Devices attached by using N Port ID Virtualization can be 20 to 35 percent slower than the
same devices attached in a native IOPless configuration.
FC EN1B 32 Gb 2-port low profile Fibre Channel adapter (Requires VIOS 2.2.6.21 or later)
o Power9 Systems: 9009-22A, 9223-22H
o Power9 Systems: 9080-M9S (requires VIOS 2.2.6.31 or later)
o Power10 Systems: 9080-HEX (requires VIOS 3.1.3.10 or later)
o Power10 Systems: 9105-22A, 9105-22B, 9786-22H (requires VIOS 3.1.3.21 or later)
FC EN1C 16 Gb 4-port Fibre Channel adapter (Requires VIOS 2.2.6.21 or later)
o Power9 Systems: 9009-22A, 9009-41A, 9009-42A, 9223-22H, 9223-42H
o Power9 Systems: 9080-M9S (requires VIOS 2.2.6.31 or later)
o Power9 Systems: 9009-22G, 9009-41G, 9009-42G (requires VIOS 2.2.6.65 or later)
o Power10 Systems: 9080-HEX (requires VIOS 3.1.3.10 or later)
o Power10 Systems: 9105-22A, 9105-22B, 9105-41B, 9105-42A, 9786-22H, 9786-42H
(requires VIOS 3.1.3.21 or later)
FC EN1D 16 Gb 4-port low profile Fibre Channel adapter (Requires VIOS 2.2.6.21 or later)
o Power9 Systems: 9009-22A, 9223-22H
o Power9 Systems: 9080-M9S (requires VIOS 2.2.6.31 or later)
o Power10 Systems: 9080-HEX (requires VIOS 3.1.3.10 or later)
o Power10 Systems: 9105-22A, 9105-22B, 9786-22H (requires VIOS 3.1.3.21 or later)
FC EN1E 16Gb 4-port Fibre Channel adapter (requires VIOS 3.1.2.20 or later)
o Power9 Systems: 9080-M9S
o Power9 Systems: 9009-22G, 9009-41G, 9009-42G
o Power10 Systems: 9080-HEX, 9105-22A, 9105-22B, 9105-41B, 9105-42A, 9786-22H,
9786-42H (requires VIOS 3.1.3.21 or later)
FC EN1F 16Gb 4-port low profile Fibre Channel adapter (requires VIOS 3.1.2.20 or later)
o Power9 Systems: 9080-M9S
o Power10 Systems: 9080-HEX (requires VIOS 3.1.3.10 or later)
o Power10 Systems: 9105-22A, 9105-22B, 9786-22H (requires VIOS 3.1.3.21 or later)
FC EN1J 32Gb 2-port Fibre Channel adapter (requires VIOS 3.1.2.20 or later)
o Power9 Systems: 9080-M9S
o Power9 Systems: 9009-22G, 9009-41G, 9009-42G
Power10 Systems: 9080-HEX, 9105-22A, 9105-22B, 9105-41B, 9105-42A, 9786-22H,
o
9786-42H (requires VIOS 3.1.3.21 or later)
FC EN1K 32Gb 2-port low profile Fibre Channel adapter (requires VIOS 3.1.2.20 or later)
o Power9 Systems: 9080-M9S
o Power10 Systems: 9080-HEX (requires VIOS 3.1.3.10 or later)
o Power10 Systems: 9080-HEX, 9105-22A, 9105-22B, 9786-22H (requires VIOS 3.1.3.21
or later)
FC EN1L 32Gb 4-port Fibre Channel adapter (requires VIOS 3.1.4.10 or later)
o Power10 Systems: 9080-HEX, 9105-22A, 9105-22B, 9105-41B, 9105-42A, 9786-22H,
9786-42H
FC EN1M 32Gb 4-port low profile Fibre Channel adapter (requires VIOS 3.1.4.10 or later)
o Power10 Systems: 9080-HEX
FC EN1N 64Gb 2-port Fibre Channel adapter (requires VIOS 3.1.4.10 or later)
o Power10 Systems: 9080-HEX, 9105-22A, 9105-22B, 9105-41B, 9105-42A, 9786-22H,
9786-42H
FC EN1P 64Gb 2-port low profile Fibre Channel adapter (requires VIOS 3.1.4.10 or later)
o Power10 Systems: 9080-HEX, 9105-22A, 9105-22B, 9786-22H
FC EN2A 16Gb 2-port Fibre Channel adapter (requires VIOS 3.1.0.50 or later)
o Power9 Systems: 9009-22A, 9009-41A, 9009-42A, 9223-22H, 9223-42H
o Power9 Systems: 9080-M9S
o Power9 Systems: 9009-22G, 9009-41G, 9009-42G
o Power10 Systems: 9080-HEX (requires VIOS 3.1.3.10 or later)
o Power10 Systems: 9105-22A, 9105-22B, 9105-41B, 9105-42A, 9786-22H, 9786-42H
(requires VIOS 3.1.3.21 or later)
FC EN2B 16Gb 2-port low profile Fibre Channel adapter (requires VIOS 3.1.0.50 or later)
o Power9 Systems: 9009-22A, 9223-22H, 9223-42H
o Power9 Systems: 9080-M9S
o Power10 Systems: 9080-HEX (requires VIOS 3.1.3.10 or later)
o Power10 Systems: 9105-22A, 9105-22B, 9786-22H (requires VIOS 3.1.3.21 or later)
FC EN2L 32Gb 4-port Fibre Channel adapter (requires VIOS 3.1.4.20 or later)
o Power10 Systems: 9080-HEX, 9105-22A, 9105-22B, 9105-41B, 9105-42A, 9786-22H,
9786-42H
FC EN2M 32Gb 4-port low profile Fibre Channel adapter (requires VIOS 3.1.4.20 or later)
o Power10 Systems: 9080-HEX
FC EN2N 64Gb 2-port Fibre Channel adapter (requires VIOS 3.1.4.20 or later)
o Power10 Systems: 9080-HEX, 9105-22A, 9105-22B, 9105-41B, 9105-42A, 9786-22H,
9786-42H
FC EN2P 64Gb 2-port low profile Fibre Channel adapter (requires VIOS 3.1.4.20 or later)
o Power10 Systems: 9080-HEX, 9105-22A, 9105-22B, 9786-22H
FC EN22 2-port FCoE adapter (Requires VIOS 2.2.2.1 or later and IBM i 7.1 TR5 or later)
o POWER7 Systems: 9119-FHB
FC EN23 2-Port 16 Gb Fibre Channel adapter. (Requires VIOS 2.2.2.1 or later and IBM i 7.1 TR5 or
later)
o POWER7 Systems: 9119-FHB
Back to Top
Client Virtual Tape Devices
Tape virtualization
Specific IOP-less attached physical tape and tape library devices supported in the host IBM i
LPAR can be virtualized to an IBM i client LPAR. An existing vSCSI connection can be used,
but creating a new vSCSI connection explicitly for tape I/O traffic is highly recommended. In
addition to the virtual SCSI connections, a Network Server Description (NWSD) is needed in the
IBM i server partition.
There is a maximum of 4 tape resources for each virtual adapter. The NWSD parameters
RSTDDEVRSC (Restricted device resources) and ALWDEVRSC (Allowed device resources)
can be used to restrict which virtualized devices the client partition can access. If you define
multiple Network Server descriptions, then you must use the RSTDDEVRSC or ALWDEVRSC
parameters to prevent the same device from appearing multiple times on the client partitions. The
RSTDDEVRSC and ALWDEVRSC parameters are limited to a maximum of 4 entries for tape.
Note: An existing virtual SCSI server adapter and NWSD in the IBM i server partition can be
used, but creating new ones to use for tape is recommended.
A virtualized tape or tape library device in the host partition can be used for a D-mode initial
program load (IPL) and for the installation of the client partition or its applications. The client
partition is able to write to the physical media in the drive. Only the server partition can update
the device firmware.
IBM i Internal Virtual Tape Devices that use image catalogs cannot be virtualized to an IBM i
client.
Note: Before IBM i 7.2 and the Tape Library Device Virtualization PTFs, tape library
devices are only supported when in sequential mode (no library functions). If both the
IBM i server and IBM i client partitions have the following PTFs applied then tape library
devices in random (library) mode can also be shared with IBM i client partitions.
IBM i 7.2 with PTFs MF64803, MF66855, MF66856, MF66835, MF66823, MF66838, MF67200,
MF67295, MF67392, SI70254, and SI73218.
IBM i 7.3 with PTFs MF64802, MF66858, MF66859, MF66836, MF66824, MF66839, MF67201,
MF67296, MF67393, SI70255, SI73219, and MF99208.
IBM i 7.4 with PTFs MF66863, MF66861, MF66862, MF66837, MF66825, MF66840, MF67202,
MF67297, MF67394, SI73220, and MF99302.
IBM i 7.5 - In base, no PTFs required
Additional devices supported by a server partition running release IBM i 7.4 TR8 or IBM i 7.5 TR2:
Note: SAS tape library devices are not supported, except for TS2900 in sequential mode, when
attached by using a VIOS partition.
TS2240 HH-LTO4 SAS (3580 H4V) (Not supported by release IBM i 7.5)
TS2900 in sequential mode with LTO4 or LTO5 SAS drives (LTO4 SAS not supported by
release IBM i 7.5)
FC 5746 HH-LTO4 SAS internal and in 7214 enclosure (Not supported by release IBM i 7.5)
FC 5638 HH-LTO5 SAS internal and FC8247 HH LTO5 SAS in 7216 or 7226 enclosure.
FC EU11 HH-LTO6 SAS internal and FCEU11 HH LTO6 SAS in 7226 enclosure
FC 5907 DAT72 SAS in 7214 enclosure (Not supported by release IBM i 7.5)
FC 5619 DAT160 SAS in 7214 enclosure (Not supported by release IBM i 7.5)
FC 5661 DAT320 SAS in 7216 enclosure (Not supported by release IBM i 7.5)
FC EU16 DAT160 USB in 7226 enclosure (Not supported by release IBM i 7.5)
VIOS 2.2.1.4 or later with client IBM i 6.1.1 or IBM i 7.1 TR4 or later
Supported on POWER7 Systems
FC 5912:
FC 2728:
Note: Tape devices are not supported by USB 3.0 adapters and VIOS
Note 2: DLPARing a SAS adapter between IBM i and VIOS partitions is not recommended.
Serving the VIOS owned tape drive to the IBM i client partitions is the recommended option.
Back to Top
SAS adapters: Each port on a SAS adapter can be used to attach a single tape drive to an IBM i
system
SAS Drives:
o Only 1 port on a SAS drive should be used.
Note: If a SAS tape or library device is shared between partitions, a re-IPL of the
adapter or partition will disrupt any operation that uses the device from the
other partition, even if the device is assigned to the other partition.
o No daisy chaining of tape drives
Multiple drive types in the same logical library are not supported on SAS adapters.
Use the shortest possible cable when connecting SAS tape media libraries or tape drives to the
IBM i.
There are 2 styles of SAS cables. The FC 5278, 5901, 5912, EJ1N, and EJ1P IOA uses the mini
SAS cables:
As a cable ordered as a feature of the Power System to which the tape device is being attached.
This cable is ordered against the host system as one of two features, both of which are called
AE-cables. These cables are 4x SAS cables and have cable labels that show customers how to
connect them to the device (even though the cables can be used in either direction):
o FC 3684 - (3 m) Mini-SAS to Mini-SAS 4x cable (P/N 44V4163).
o FC 3685 - (6 m) Mini-SAS to Mini-SAS 4x cable (P/N 44V4164).
As a cable ordered as a feature for the particular tape device or tape library being purchased.
For 3GbSAS adapter FC 5901, FC 5912, FC 5278, FC EJ1N, FC EJ1P, and blade FC 8246,
FC 8250
Note: If interface errors are encountered when connecting these tape media libraries or tape
drives to blade servers, 4X cables can be used.
Note: LTO4 technology drives are not supported by the 6 Gb SAS adapters
For the 7214-1U2, the following cables can be ordered. These are the same as the 4x SAS cables
that can be ordered for the Power System.
FC 9743 (3 m): 44V4163 (same cable as FC 3684 for Power 520, 550, and 570)
FC 9746 (6 m): 44V4164 (same cable as FC 3685 for Power 520, 550, and 570)
Back to Top
The following code levels have being tested on IBM i systems at V5R4M0 and later. Note: All
models of the ProtecTIER VTL are past the hardware End Of Service date, so support is
no longer available for using ProtecTIER with IBM i.
ProtecTIER Server Code level Red Hat Code level ProtecTIER Patch Required ProtecTIER Manager Code
ProtecTIER server code and ProtecTIER manager code can be downloaded from IBM Fix
Central
Notes:
1. Before upgrading any firmware on servers, refer to the ProtecTIER upgrade instructions.
2. There are different ProtecTIER server code packages for Gateway (TS7650), Appliance (TS7650)
and Express (TS7610 and TS7620) models. Ensure that the correct package is downloaded.
3. Interim releases of the ProtecTIER server code not listed, are not tested on the IBM i, but are
supported.
4. ProtecTIER attachment to IBM i is supported at V5R4M0 and later only
5. There is no BRMS or IBM i OS dependencies for the different ProtecTIER server code levels
6. IBM i supports TS7560G model DD3, DD4, and DD5 ProtecTIERs in VTL mode only.
7. IBM I supports TS7610 and TS7620 ProtecTIERs in VTL mode only.
8. With 3.4.0 firmware and later, DD6, DD5, and DD4 models can support up to 64 virtual tape
media libraries
ProtecTIER supports LTO3 with *ULTRIUM3 density only. The type of tape drive and density
has no bearing or effect on the performance of saves and restores. Support end of life (EOL) of
LTO3 physical drives will also not affect the support of LTO3 virtual drives in the ProtecTIER.
Back to Top
If you need sizing for a Dynamic Solutions International (DSI) VTL solution, send the following
information to [email protected]
1. Customer Name
2. What VTL/Tape drives are used today
3. The current deduplication ratio if you are using a VTL.
4. Data collected from one of the following actions
If using BRMS, load and apply 7.3 SI69390 7.2 SI69389 or superseding PTF and then run the
following commands on each LPAR and send the spool file. The spool files can be compressed
to make transfer easier.
PRTRPTBRM TYPE(*CTLGRPSTAT)
Send in the spool files in text (.txt) format. (Files need to be downloaded as .txt files and not as
pdf and converted) See this document on how to create text files BRMS-Report gathering.docx
Note: Both these commands need to run in the same job stream
If you have multiple systems in a BRMS network, you can use the following command on one of
the systems to run the reports for each of the other systems
Then, send in the spool files in text (.txt) format. (Files need to be downloaded as .txt files and
not as pdf and converted) BRMS-Report gathering.docx
Note: Both these commands need to run in the same job stream
If not using BRMS, send in the following for each LPAR. You can use RTVDSKINF and
PRTDSKINF to get library and IFS sizes.
Example
LPAR Name Type Of Backup Retention Period Amount of Data saved Start Time S M T W T F S
Back to Top
If all the following conditions are met, you can do an alternate IPL from a fibre or SAS-attached
tape drive:
Notes:
When there are multiple tape drives in the same zone on the fibre switch as the IOA, the IOA is
able to see all of the drives, and the system searches them for any installation media. If there is
installation media loaded on more than one drive, the system can find the wrong tape. It is
recommended to use either a direct-attached drive or create a zone on the fibre switch that has
only one drive in it for installing from Fibre Channel attached tape.
Alternate restart from USB attached tape drives, Flash drives, and Removable Mass Storage
devices requires an HMC-managed system, except for Power9 and Power10 Servers, which use
the System unit USB 3.0 ports for the default D-IPL search path.
The IBM ProtecTIER Virtual Tape Library is supported as an alternate IPL device.
If an IBM ProtecTIER or other VTL drive is going to be used for an alternate IPL device (D-mode),
there can be only one drive visible on the adapter as the alternate restart device. LUN masking
can be used to satisfy this requirement.
On non HMC-managed models 515, 520, 525, 550, or 570, the system will Alternate restart (D-
IPL) only from the internal DVD-ROM or tape drive. If you are using an external device, the Alt
Install device must first be selected. This is because the manufacturer sets the Alt IPL to the
internal SCSI controller on the system backplane and it cannot be changed.
On non HMC-managed Power8 Servers, the system will Alternate restart (D-IPL) only from the
internal DVD drive.
On non HMC-managed Power9 and Power10 Servers, the system will only Alternate restart (D-
IPL) from optical devices (DVD, Flash, RDX) attached to the USB 3.0 System unit ports or from
the System unit internal RDX drive.
In almost all cases, the HMC is used to select the device that is used for the alternate restart. If
the alternate restart device was not configured by using the HMC, or by a previous alternate
restart, then the following default search sequence is used.
Note:
On non HMC-managed models 515, 520, 525, 550, or 570, the system will only Alternate restart
from the internal DVD or tape drive. If you are using an external device, they must be selected
as an alternate installation device.
Once the system successfully performed an alternate restart, the Virtual Service Processor (VSP)
will remember the address of the device and use it for any subsequent alternate restarts until
either the HMC is used to select a different alternate restart device or the alternate restart fails.
Once an alternate restart fails the VSP goes back to using the default search sequence.
The following search sequence is used to search for an alternate restart device attached to the
IOA:
1. Device attached to SCSI bus 0 with a controller address of 7 (SCSI address 0).
2. Device attached to SCSI bus 0 with a controller address of 6 (SCSI address 1).
3. Device attached to SCSI bus 0 with a controller address of 5 (SCSI address 2).
If the system cannot find a device to use as the alternate restart device, it displays a reference
code on the control panel.
Back to Top
The IBM i partition needs to reserve a tape drive before it can use it. This reserve is held until
the IBM i partition releases the tape drive.
If the following conditions are met, a reserve can be held by a system that is powered off
When connecting tape media libraries to the IBM i, there are strict rules that apply. The
restrictions and requirements are as follows:
IOP-based IOAs
Maximum of 16 devices per IOP-based IOA
A control path drive counts as 2 devices (see note 1)
One control path drive per logical tape media library per IOA
No Alternate IPL support for Fibre Channel attached tape devices.
No control path failover
Maximum of 32 drives in a logical library (See note 4)
Multiple IOAs are required when there are different model tape drives in the same logical tape
media library.
Changing the configuration of the tape library requires an IPL of the IOP, power cycle of the IOA
or IPL of the System i. Changes include any of the following:
o Adding or removing storage slots
o Changing tape drive sled
o Adding or removing tape drives
o Changing the number of I/O slots
o Changing a control path drive
o Changing the tape library from sequential mode to random mode.
o Renaming resources
Note: If the recommended IPL or power cycle is not done after you make one of the preceding
changes, a CPF3698 message can be received indicating that a dump has been taken. If
WRKPRB is used to look at the problem log, the symptom string is 5761 F/QTADMPDV or
5722 F/QTADMPDV.
When there are multiple tape drives of the same model in the same logical tape library
connected to different IOAs, the resources are pooled under one tape library description. Up to
32 devices per TAPMLB device description.
Available densities that a cartridge can be initialized with are obtained from tape drive device
description and not tape library descriptions. Therefore, at least one tape drive description
needs to exist for every tape drive model type on the system, even though the tape drive
description might never be used.
Different model tape drives are not pooled under the same tape media library. If different
model tape drives are in the same logical tape library, at least one control path drive is required
for each model and like drives are pooled under their own tape library
The maximum number of elements (storage slots, plus drives, plus import export elements) in
one logical library is limited to 5000. The limit is increased to 15,000 storage elements with PTFs
MF55406 and MF50093 (IBM i 6.1.1) or MF55409 (IBM i 7.1). IBM i 7.2 and later releases have
large library support in the base code.
The maximum number of drives in the IBM i logical library (that is, the TAPMLBxx) remains 32.
Multiple drive types in the same logical library are not supported on SAS adapters.
Before release 7.2 TR2 tape library devices and tape drives cannot have multiple
connections to the same IBM i partition. See the Tape Multipath section for additional
detail.
Tape cartridges with a missing or unreadable bar code label are assigned a cartridge ID of
format UNKxxx or U@xxxx (where xxxx identifies the physical location). Before the
tape cartridge can be used for output operations, it must be reinitialized to change its
volume ID to match the assigned cartridge ID.
o BRMS does not allow @ in a BRMS volume name
When a tape library device is directly attached to the IOA (no SAN switch), the port topology on
the drive should be set to L-Port
TS4300, TS3200, TS3100, and TS2900 can be in random or sequential mode
It is not recommended to mix Disk and Tape on the same physical IOA port.
o Example 1:
IOP A - port 0 has DASD
- port 1 has tape
Before tape multi-path, a user would leave IOP B port 1 empty or attach
half the tape devices to IOP A and the other half to IOP B.
o Example 2
IOP A - port 0 has DASD
- port 1 has tape (half the tape device here)
IOP B - port 0 has DASD (same devices as on IOP A port 0)
- port 1 has tape (the other half of the tape devices here)
Considerations for tape libraries with release IBM i 6.1 and with release IBM i 6.1.1 when
MF50093 is not applied:
All cartridges contained within a tape library device must have a valid bar code label.
Manually moving a mounted cartridge within a tape library device by using the Remote
Maintenance Utility might render the cartridge unusable from System i. To recover from this
condition:
o De-allocate all of the tape library resources except the one that last contained the
manually moved cartridge.
o Issue a CHKTAP command from System i to cause a different tape cartridge to be
mounted in the tape resource.
There must be a control path drive from a logical library attached to each Fibre Channel or SAS
IOA. Attachment of multiple control path drives to the same IOA is not recommended.
Considerations for tape libraries with release IBM i 6.1.1 when MF50093 is applied and
with release IBM i 7.1:
There must be at least 1 control path drive from a logical library attached to each port for Fibre
Channel IOAs. There must be at least 1 control path drive from a logical library attached to a SAS
IOA (there does not need to be a control path drive for each port.)
A new resource name might be assigned for tape library devices attached to an IOPless adapter
when MF50093 is applied or IBM i 7.1 is installed.
Tape cartridges with a missing or unreadable bar code label are assigned a cartridge ID of format
UNKxxx or U@xxxx (where xxxx identifies the physical location). Before the tape cartridge can be
used for output operations, it must be reinitialized to change its volume ID to match the
assigned cartridge ID.
If a TS7610/TS7650 (ProtecTIER) or other VTL drive is going to be used for an alternate IPL device
(D-mode), there can be only one drive visible on the adapter as the alternate restart device. LUN
masking can be used to satisfy this requirement.
Use the following table to determine what Encryption Software you would need to perform
hardware encryption
Notes:
1. As only Library-Managed Encryption (LME) is supported on IBM i, tape drives must be in a tape
media library. (TS4500, TS4300, TS3500, 3494, TS3310, TS3200, TS3100, or TS2900).
When saving to a tape library, data flows across 2 channels: the data path and the control path.
The actual data travels along the data path. The tape library control commands "mount tape",
"eject tape", "inventory library" and so on, flow along the control path. In all libraries except the
3494, the control path and data path use the same cable.
IBM i supports control path failover on systems that are running IBM i 7.1 or higher and using
IOPless fibre cards for their tape or virtual tape. If a save is running and the IBM i detects a
problem with the control path it is using, it automatically starts sending the library commands
down another control path that is attached to the same fibre port and is associated with another
drive in the same tape library. The save continues without interruption. If multiple control paths
fail, the save continues to fail over until there are no more operational control paths. Note: This
function does not support failover to a control path on a different Fibre Channel port or a
different library.
Tape multi-path support is available for IBM i 7.2 and later releases. See Tape Multipath
Redundant tape connections (multi-path) are not supported on IBM i 7.1 and earlier
Many new tape libraries can have multiple tape drives in them. These tape libraries can also be
logically partitioned. If there are mixed tape drives (LTO1, LTO2, LTO3, LTO4, LTO5, LTO6,
LTO7, LTO8, LTO9, or 3592 J1A, TS1120, TS1130, TS1140, TS1150, TS1155, TS1160) in the
same physical tape library (TS2900, TS3100/3200, TS3310, TS3400, TS3500, TS4300,
TS4500), there must be at least one control path drive for each drive type.
Notes:
1. When using BRMS, each logical library needs to have a different location.
2. If using a single logical library with multiple IOAs, it is not possible to use higher density
cartridges in lower density drives (moves, ejects).
Notes:
1. This includes physical tape libraries (TS3500, TS3310) and virtual tape libraries (ProtecTIER)
2. The limit is 15,000 storage slots per logical tape library.
3. The total number of elements (Storage slots, I/O slots, drives, and pickers) cannot exceed
16,381.
4. If too many elements are configured, no media library resource is created
5. The following PTFs or the superseding PTF is required to enable this:
o V6R1M1 - MF55406 and MF50093
o IBM i 7.1 - MF55409
o IBM i 7.2 and later - in base
With the advent of Virtual Tape Libraries, it is possible to have a many logical tape drives
defined in a tape library. To allow more than 250 virtual tape drives in a single logical library,
ensure that the following PTFs are applied:
V6R1M1 - MF56115
IBM i 7.1 - MF56114
IBM i 7.2 and later - in base
Note: Even though more than 256 drives can exist in a logical tape library, there are restrictions
when you attach them to IBM i. The following restrictions still apply when you attach drive
resources in a tape media library to an IOA on IBM i:
A maximum of 32 drive resources defined in a tape library. If more than 32 drives are required
on a single LPAR, additional logical libraries must be created.
A maximum of 64 visible devices per IOPless IOA port (see note 1 & 3)
A maximum of 16 devices per IOP-based IOA (see note 3)
When you attach a tape media library to an IOP-based IOA, only 90 drives can be created or
exist in a single logical library (Using ProtecTIER LUN masking does not work around this limit)
When you attach a tape media library to an IOP-less IOA, a maximum of 512 drives can be
created or exist in a single logical library
Notes
1. LUN masking can be used on the ProtecTIER to mask tape drive resources from a particular host
IOA.
2. A maximum of 512 tape drive resources can be on a single ProtecTIER port.
3. Each robot (ProtecTIER) or tape drive with a Control Path and each drive counts as a device
If using BRMS, running WRKMLMBRM or WRKMLBBRM option 8, and there are more than
9999 cartridges in the tape library, the following message can be posted:
Message ID . . . . . . . . . : BRM3C90
Message . . . . : Maximum number of &5 entries exceeded.
To circumvent this use a generic value for the VOL parameter on the WRKMLMBRM
command:
For LTO tape drives, it depends on the model and library. For example, LTO5 tape drives have
dual ports in the larger libraries, but only single ports in the smaller libraries.
The following table lists the LTO drive, the tape library and whether it is single or dual ported
TS3500/TS4500
TS4300
TS3310
TS3200/TS3100
TS2900
Notes:
1. IBM i does not support attaching both ports to IOA ports from the same LPAR at IBM i 7.1 and
earlier.
2. SCSI ports are in/out ports. It is not possible to attach 2 hosts to the same SCSI drive
Back to Top
Reassigning cartridges when the system
name changes
If the system name is changed and you are using tape categories, you should reassign cartridges.
If you change your system name, you must move the cartridges from the categories that were
owned by the old system name to categories that are owned by the new system name. If you do
not do this, the cartridges do not appear in the inventory for the new system name.
For some library types, the cartridges might appear when you use the parameter CGY(*ALL
*ALL) for the Work with Tape Cartridges (WRKTAPCTG) or the Display Tape Cartridge
(DSPTAPCTG) command, but you cannot use the cartridges.
If you have already changed the system name and need to recover the cartridges, perform the
following steps:
1. DSPTAPCGY (the Display Tape Category command) to display all of the tape categories. Record
the names of the user-defined categories for use in step 3, and then exit.
2. Temporarily change the system name back to the previous name by using the Change Network
Attributes (CHGNETA) command.
o Do not restart the system
3. If you were using user-defined categories with the old system name, type CRTTAPCGY (the
Create Tape Category command) to create the same user-defined categories from step 1, for the
new system name.
4. Type WRKTAPCTG (the Work with Tape Cartridge command) to work with all of the categories
that are associated with the old system name.
o WRKTAPCTG DEV(mlb-name)
CGY(*ALL old_system_name)
5. Change the category system name to the new system name by selecting 2 Change with the
parameter CGY (*SAME new_system_name).
6. Type CHGNETA (Change Network Attributes) to return the system name to the new system
name.
Trademarks
Linear Tape-Open, LTO, the LTO Logo, Ultrium and the Ultrium Logo are registered trademarks of
Hewlett Packard Enterprise, International Business Machines Corporation and Quantum Corporation in
the United States and other countries.