Re: Is there an issue mixing LTO5 HH and LTO7 HH FC drives in the same 3573 library?

The rule is that only the same type drives can be on the same control path. So the two LTO7s will be on one (one with control path and the other 'rides along') and the LTO5s the same.

So configure it as two libraries and you'll be set to go. Split the slot count as you find the need.

- Larry "DrFranken" Bolhuis

www.Frankeni.com
www.iDevCloud.com - Personal Development IBM i timeshare service.
www.iInTheCloud.com - Commercial IBM i Cloud Hosting.

On 4/5/2016 7:39 PM, Steinmetz, Paul wrote:

Is there an issue mixing LTO5 and LTO7 HH FC drives in the same 3573 library?

Power7-740-E6C.
Latest CUM and TR11.
All latest tape PTFs
Library is 3573
Latest library firmware - D.00 / 3.20e
LTO5 firmware - F991
LTO7 firmware - FA11

I received 4 new LTO7 HH FC drives.
Swapped 2 LTO5 with 2 LTO7 drives.
IPL IOP - 577D
INZBRM *Device
Library saw the 2 new LTO7 drives with no issue.
iSeries auto created two new 3580-997 resources.
Varied on fine
Added 6 new LTO7 volumes, no issue.
Tested BRMS control group save, no issue.
Near the end of the Auto Dup, received the below error, drive went to failed status.

Message ID . . . . . . : CPF471E Severity . . . . . . . : 40
Message type . . . . . : Information
Date sent . . . . . . : 04/05/16 Time sent . . . . . . : 16:22:15

Message . . . . : Timeout on device TAPMLB01.
Cause . . . . . : A timeout occurred on device TAPMLB01. The timeout origin
was either the Input/Output Processor (IOP) or the device.
Recovery . . . : Obtain the error information from the QSYSOPR message
queue. Fix the problem and attempt the command again.

Last week, our CE experienced a very similar issue at another site with 3573, LTO3 and LTO5 being swapped.
CE stated they reconfigured the library resolved the issue, not sure why.


Thank You
_____
Paul Steinmetz
IBM i Systems Administrator

Pencor Services, Inc.
462 Delaware Ave
Palmerton Pa 18071

610-826-9117 work
610-826-9188 fax
610-349-0913 cell
610-377-6012 home

psteinmetz@xxxxxxxxxx
http://www.pencor.com/