COUGARXR71997
ADSM.ORG Member
I have an Overland NEO 4000 series library which is connected via fiber channel to the server.
TSM runs on a windows 2003 server.
So far , it has been verified that the fiber switch and card on the server are functioning properly, however, tsm cannot communicate with the library. The TSM errors are:
ANR8310E An I/O error occurred while accessing library NEO.
ANR8441E Initialization failed for SCSI library NEO.
The removable storage service is disabled, but if i enable it, i get the following error
Configuration for device changer0 failed.
However, if i turn the library off, windows notifies me that the 2 HP lto1 drives and the changer have gone offline. And then it notifies me that they are back online when i power the library on.
HP tools gives errors when trying to find the drives.
VS tools cant communicate with the library.
Overland support is stumped, I am stumped, I have tried everything with tsm I know how to do. Anyone have any suggestions on what might be going on ?
My biggest question in all of this: is it a tsm problem? or is it an hardware problem with the library?
Thanks
TSM runs on a windows 2003 server.
So far , it has been verified that the fiber switch and card on the server are functioning properly, however, tsm cannot communicate with the library. The TSM errors are:
ANR8310E An I/O error occurred while accessing library NEO.
ANR8441E Initialization failed for SCSI library NEO.
The removable storage service is disabled, but if i enable it, i get the following error
Configuration for device changer0 failed.
However, if i turn the library off, windows notifies me that the 2 HP lto1 drives and the changer have gone offline. And then it notifies me that they are back online when i power the library on.
HP tools gives errors when trying to find the drives.
VS tools cant communicate with the library.
Overland support is stumped, I am stumped, I have tried everything with tsm I know how to do. Anyone have any suggestions on what might be going on ?
My biggest question in all of this: is it a tsm problem? or is it an hardware problem with the library?
Thanks