are so helpful!
Jason Liang
- Original Message -
From: Dan Foster [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Tuesday, September 17, 2002 11:37 PM
Subject: Re: Help for 2108 failure
The other possibility is that since the 2108 was replaced, there may
be a small chance the /dev/rmtX
Hi TSMers,
My environment is
Fiber SCSI
RS/6000(TSM Server) 2108 SAN Gateway - 3584 LTO library.
The TSM server worked perfectly until yesterday. The tape drives all went
offline and the problem turned out to be the hardware failure of 2108.
IBM
Sounds like the SCSI ID order may have been changed on the 2108 (easy to
do).
rmt0 sounds OK as that is where the library changer path is.
The changer may be loading it the correct drive but the SCSI for the
other drives may be set in a different order.
Have you done a visual confirmation of
I have similar config except have McData switches instead of
2108. Did you reconnect 3584 drives in same config on new 2108
as old one? I suspect that what TSM thinks is DRIVE1 is say DRIVE3.
etc.
Do you have an lsdev -Cc tape from before 2108 replacement?
David Longo
[EMAIL PROTECTED]
The other possibility is that since the 2108 was replaced, there may
be a small chance the /dev/rmtX mapping no longer matches what the
previously assigned rmtX-to-element ID mapping was.
Which conceivably could produce this sort of error, if TSM and
the library disagreed about what
Jason Liang wrote:
Hi TSMers,
My environment is
Fiber SCSI
RS/6000(TSM Server) 2108 SAN Gateway - 3584 LTO library.
The TSM server worked perfectly until yesterday. The tape drives all went
offline and the problem turned out to be the
