URGENT!! TSM server lost communication with tape library

[JulesInglewood]

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.

http://www.freezemugs.com/images/ScreenShot001.jpg

http://www.freezemugs.com/images/ScreenShot002.jpg

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

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

Please help!

 

[ProbablyDown]

Hmm... is your server win2k3?

I found this:

http://72.14.203.104/search?q=cache...rt+TSM+Device+Driver&hl=en&gl=ca&ct=clnk&cd=3

Is that the prob?

 

[JulesInglewood]

No it´s a Windows 2000 Server.

 

[ProbablyDown]

Just in looking - Is there any chance that that is still the problem?

 

[ProbablyDown]

Can you reboot the entire server?

Sorry... just grasping at straws here, I know... I'm an AIX dude...
I just feel your pain

 

[JulesInglewood]

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.

 

[ProbablyDown]

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

 

[mbourne2006]

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

http://www.ibm.com

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.