× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.


  1.  Home
  2. MIDRANGE-L
  3. April 2016

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

BRMS AUTO DUP LTO7 drives, no mixture, finished without issue

I will be sharing the LTO5 / LTO7 performance numbers under a new thread, results are amazing, better than expected.

Paul

-----Original Message-----
From: MIDRANGE-L [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Steinmetz, Paul
Sent: Wednesday, April 06, 2016 9:19 AM
To: 'Midrange Systems Technical Discussion'
Subject: RE: Is there an issue mixing LTO5 HH and LTO7 HH FC drives in the same 3573 library?

What was interesting, was 3 saves using 1 LTO7 drive all completed without issue.

All 3 BRMS AUTODUPS, which each needed two LTO7 drives, all failed after 1 to 2 hours of running.



I don't totally understand the control path concept nor the FC switch zoning.

Below are notes from the FC switch zoning given to me by IBM for our network team to configure the FC switch.



SYSA IOPA Port1 sees both PORT5 TAPE1 and PORT6 TAPE2

SYSA IOPA Port2 sees both PORT7 TAPE3 and PORT8 TAPE4



SYSB IOPB Port1 sees both PORT5 TAPE1 and Port6 TAPE2

SYSB IOPB Port2 sees both PORT7 TAPE3 and Port8 TAPE4



then each system will see all 4 drives ... 2 drives per port of the IOA

you could leave all 4 drives with control paths ... or have only

TAPE1 and TAPE3 as the control path drives ... one per port minimum.



Library configured to Random mode

1 logical library - We share media across LPARS without any manual intervention.

Path Failover not configured, I believe this is an optional chargeable feature.

Encryption - none



Library is configured as follows for each drive.

LTO7 firmware - FA11

Power On and Control Path both enabled

Speed - Automatic

Topology - N-Port

FC-AL Loop ID - Automatic



Paul



-----Original Message-----
From: MIDRANGE-L [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of DrFranken
Sent: Wednesday, April 06, 2016 8:59 AM
To: Midrange Systems Technical Discussion
Subject: Re: Is there an issue mixing LTO5 HH and LTO7 HH FC drives in the same 3573 library?



Excellent. All will be muchhhhh happier now!



- Larry "DrFranken" Bolhuis



www.Frankeni.com<http://www.Frankeni.com>

www.iDevCloud.com<http://www.iDevCloud.com> - Personal Development IBM i timeshare service.

www.iInTheCloud.com<http://www.iInTheCloud.com> - Commercial IBM i Cloud Hosting.



On 4/6/2016 8:54 AM, Steinmetz, Paul wrote:

I swapped the remaining two LTO5 for LTO7 this morning.

No more mixture.

Everything appears "happy"

Drives all appear the same as they did with the LTO5 config.

Waiting for results of DUPMEDBRM to finish.



TAPMLB01 ACTIVE

TAP31 OPERATIONAL UNPROTECTED

TAP32 OPERATIONAL UNPROTECTED

TAP33 ACTIVE UNPROTECTED BRMS

TAP23 ACTIVE UNPROTECTED BRMS



Paul



-----Original Message-----

From: MIDRANGE-L [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of

DrFranken

Sent: Wednesday, April 06, 2016 8:43 AM

To: Midrange Systems Technical Discussion

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



So you are on the right 'Path' then :-)



Yes the mixing of the drive types on the same control path am not good and can make a mess. I've had to force DLPAR cards away then delete everything in SST and DLPAR them back in to make it happy again.



So split them if you still need too or just unhook the LTO5s perhaps until the LTO7s are all in place.



Do be sure to get the firmware the same on all the LTO7s!





- Larry "DrFranken" Bolhuis



www.Frankeni.com<http://www.Frankeni.com>

www.iDevCloud.com<http://www.iDevCloud.com> - Personal Development IBM i timeshare service.

www.iInTheCloud.com<http://www.iInTheCloud.com> - Commercial IBM i Cloud Hosting.



On 4/5/2016 10:00 PM, Steinmetz, Paul wrote:



Larry,



This is what I needed to know.

The current 2 LTO5 + 2 LTO7 config is temporary.

By end of day tomorrow, all 4 should be LTO7.



Currently, I may have multiple drive types on the same control path, which could be a reason for the failure.



Paul



-----Original Message-----

From: MIDRANGE-L [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf

Of DrFranken

Sent: Tuesday, April 05, 2016 9:57 PM

To: Midrange Systems Technical Discussion

Subject: 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<http://www.Frankeni.com>

www.iDevCloud.com<http://www.iDevCloud.com> - Personal Development IBM i timeshare service.

www.iInTheCloud.com<http://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<mailto:psteinmetz@xxxxxxxxxx>

http://www.pencor.com/





--

This is the Midrange Systems Technical Discussion (MIDRANGE-L)

mailing list To post a message email:
MIDRANGE-L@xxxxxxxxxxxx<mailto:MIDRANGE-L@xxxxxxxxxxxx> To

subscribe, unsubscribe, or change list options,

visit: http://lists.midrange.com/mailman/listinfo/midrange-l

or email: MIDRANGE-L-request@xxxxxxxxxxxx<mailto:MIDRANGE-L-request@xxxxxxxxxxxx> Before posting, please take a moment to review the archives at http://archive.midrange.com/midrange-l.



Please contact support@xxxxxxxxxxxx<mailto:support@xxxxxxxxxxxx> for any subscription related questions.



--

This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing

list To post a message email:
MIDRANGE-L@xxxxxxxxxxxx<mailto:MIDRANGE-L@xxxxxxxxxxxx> To subscribe,

unsubscribe, or change list options,

visit: http://lists.midrange.com/mailman/listinfo/midrange-l

or email: MIDRANGE-L-request@xxxxxxxxxxxx<mailto:MIDRANGE-L-request@xxxxxxxxxxxx> Before posting, please take a moment to review the archives at http://archive.midrange.com/midrange-l.



Please contact support@xxxxxxxxxxxx<mailto:support@xxxxxxxxxxxx> for any subscription related questions.



--

This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list To post a message email: MIDRANGE-L@xxxxxxxxxxxx<mailto:MIDRANGE-L@xxxxxxxxxxxx> To subscribe, unsubscribe, or change list options,

visit: http://lists.midrange.com/mailman/listinfo/midrange-l

or email: MIDRANGE-L-request@xxxxxxxxxxxx<mailto:MIDRANGE-L-request@xxxxxxxxxxxx> Before posting, please take a moment to review the archives at http://archive.midrange.com/midrange-l.



Please contact support@xxxxxxxxxxxx<mailto:support@xxxxxxxxxxxx> for any subscription related questions.
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list To post a message email: MIDRANGE-L@xxxxxxxxxxxx To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting, please take a moment to review the archives at http://archive.midrange.com/midrange-l.

Please contact support@xxxxxxxxxxxx for any subscription related questions.

As an Amazon Associate we earn from qualifying purchases.

This thread ...
Replies:
Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.