Hi All
Here are the details of a problem that we are experiencing.
We are implementing a TSM solution in a SAN environment as follows:
SAN Fabric - 2 X 2109 F16 switches
Library - 3494-D14 with 2 3590-E1A drives and an A60 Escon attached to a O/S390.
3494-L12 with 2 3590-E1A drives FC attached to the SAN
Library Manager LAN attached.
Drive firmware F26E
2105-F20 - attached to SAN
TSM Server - IBM Netvista 6349-74G running Windows2000 SP2 build 2195
- Qlogic QL2200 HBA Driver version 8.1.5.12 Firmware 2.02.03
BIOS 1.72
- TSM Server Ver 5.1.1.1
- TSM Device driver 5.1.1.7
- 3590 Device driver version 5.0.3.2
- Remote Storage Manager disabled.
- IBM ATL service configured and running.
- TSM device drivers enabled and managing drives.
Problem discription.
Windows Device Manager does not detect any media changer or
library device.
Windows Device Manager does detect the two 3590 drives as
MT0.0.0.2 and MT2.0.0.2
TSM Device Driver Wizard does not detect any library.
TSM Device Driver Wizard does detect drives and takes control of
them.
If the Drives are configured (in TSM) as part of a 3494 library,
label libv hangs device driver reports error ASC02 ASCQ04 (drive not ready error).
If drives are configured as Manual drives, and a tape is manually
loaded, the label libv is successful.
Also, if the TSM drivers and the IBMATL service are disabled (ie
using native drivers), then NTUTIL diags run on drives. MTLIB utility does not run.
Cannot find special filename for library.
I have seen mention of FC9212 (Windows attach) for 3494's in several publications, but
no detail of what it is exactly. Does this feature have something to do with the
connectivity of the media changer and the fibre attachment via one or both of the
3590's. How can I verify that this feature has been installed in the 3494?
Can anyone help?
Regards
Steve Hartland
Durban Metro
South Africa
