Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations derfloh on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

URGENT!! TSM server lost communication with tape library

Status
Not open for further replies.

JulesInglewood

Technical User
Joined
Nov 14, 2006
Messages
3
Location
SE
I have a really big problem. After a firmware upgrade of my IBM 3584 Tape Library. The communication with the TSM server stopped. I have tried to start the TSM Device Drivers but keeps getting the following error:

"Unable to start TSM Device Driver
Reason: The system cannot find the device specified"

I have tried to restart the TSM server as well as the Tape Library, with no luck.


Please, if you want more information just let me know.

This is going to be a looooong night.....

Please help! :cry: :cry: :cry:
 
Just in looking - Is there any chance that that is still the problem?
 
Can you reboot the entire server?

Sorry... just grasping at straws here, I know... I'm an AIX dude...
I just feel your pain
 
Yes the entire server has been rebooted several times, without any luck.

No I don´t think so, because the TSM DD is still a service in 2000.

I really appriciate your concern.
 
Well the only other thing I can think of is:
1) backlevel the firmware
2) reinstall the library from scratch...

Neither are very nice... Especially in a prod env. - I know..

Any TSM on Windows guys out here???

Good luck JI
 
Hi

What version of TSM? I see you're using the Management Console, so I'm guessing 5.2.x ?

Anyway, the correct device driver to use in your setup would be the IBM Ultrium device driver, *not* the TSM Device Driver.

Go to and search for the following reference: S4000097

This page will provide you with links to download the correct drivers, and the Installation & User Guide for the software. BTW - check also that the "RSM (Remote Storage Management) service is not running, as this can cause device contention at boot.

Final point - if your drives are fibre-connected, do you have any mechanism installed to ensure that the same drives always pick up the same SCSI LUN ID at boot time? We had to install a bit of software from Qlogic on our Windows 2000 server to stop Windows device detection process breaking our tape drive connections at every reboot :)

HTH

Kind Regards,
Matthew Bourne
"Find a job you love and never do a day's work in your life.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top