Re: 3573 tape drives issues

Hi, Kirk:

I was only saying that the cable appears to be good. We used the 3570 to
transfer the system backup from the AS/400 Model 720 to the iSeries Model
520, and that tape library worked fine with both systems. To do that we
disconnected the cable at the AS/400 card end and attached it to an iSeries
card *specified for the 3570*. It is NOT the same point at which we attach
the 3573.

Darrell

Darrell A. Martin - 630-754-2141
Manager, Computer Operations
dmartin@xxxxxxxxxxxxx

midrange-l-bounces@xxxxxxxxxxxx wrote on 04/30/2007 05:13:44 PM:

I think I see a problem... I believe the 3573 ( TS3xxxx) drives all ONLY

use a LVD interface (FC57xx). The 3570 uses a HVD Interface (typically a
2749). The Connection at the system end is completely different for these

to types of cards, So the cable for the 3570 might fit on the 3573 but

not

the correct card in the system. Double check what card you have attached
the 3573 to.


--

Kirk Goins
Systems Engineer, Manage Inc.
IBM Certified in i5 Solution Sales,
i5 Technical Solutions Expert V5R4,
iSeries Multiple Systems Administrator V5R3,
Systems Expert - i5 LPAR Technical Solutions V5R3

Office 503-353-1721 x106 Cell 503-577-9519
kirkg@xxxxxxxxxxxxx www.manageinc.com

Email Response Times:
Same Day Maybe, Next Day Probably



Darrell A Martin <DMartin@xxxxxxxxxxxxx>
Sent by: midrange-l-bounces@xxxxxxxxxxxx
04/30/2007 12:28 PM
Please respond to
Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>


To
Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>
cc

Subject
3573 tape drives issues







Rob:

Interesting. We have a brand-spanking new 3573 L2U, connected to our
equally new i520, that has never autoconfigured. Yes, I have IPL'ed,

among

other things including swapping the cable and terminator on the drive. No

joy.

I now have within reach a new cable, new terminator, new drive, and new
chassis. (Do I detect a pattern here -- throw replacement parts at the
problem in hopes that one of them, or the process of installing it, will
accidentally do the trick?)

I don't think it's the cable (it connected to our 3570 successfully) and
the terminator is an unlikely suspect. Most bets are on the drive itself.

If swapping the drive doesn't work dark and early tomorrow morning, then

I

move through the progression cable, terminator, chassis. We'll see. I'm
interested in how it works out with you and the person who replied to you

(Davidson?).

Darrell

Darrell A. Martin - 630-754-2141
Manager, Computer Operations
dmartin@xxxxxxxxxxxxx

[snip]

I have a new 3573-L2U that has only successfully completed
1 backup. Tried to do second backup and IBM has now sent
me replacement drive, cable and terminator. Can't get the
replacement to even vary on. Used concurrent maintenance
to reboot 5702 card and now the drive is non reporting.
IBM says IPL and even claims there is a better than 90%
chance that would work even when concurrent maintenance
wouldn't. Personally I think he's full of excrement but I
am in the process now of bringing that lpar to a
restricted state... 11TFNS2.

Rob Berendt

Rob, you are not suffering alone on this one... I have
been trying to get straight answers from IBM on a
3573-L2U with 5736-PCI-X (SCSI) attach and not getting
much satisfaction. The RMU is a slick interface but it
just doesn't seem like it is in synch with the microcode.

This e-mail, including attachments, may contain information that is
confidential and/or proprietary, and may only be used by the person to
whom this email is addressed. If the recipient of this e-mail is not the
intended recipient or an authorized agent, the reader is hereby notified
that any dissemination, distribution, or copying of this e-mail is
prohibited. If this e-mail has been delivered to you in error, please
notify the sender by replying to this message and deleting this e-mail
immediately.
--

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.


--

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.

This e-mail, including attachments, may contain information that is
confidential and/or proprietary, and may only be used by the person to whom
this email is addressed. If the recipient of this e-mail is not the intended
recipient or an authorized agent, the reader is hereby notified that any
dissemination, distribution, or copying of this e-mail is prohibited. If this
e-mail has been delivered to you in error, please notify the sender by replying
to this message and deleting this e-mail immediately.