Hi all,
We are experiencing LTO4 timeouts in our windows 2008 R2 server environment using IBM driver IBMTAPEx64_w08_6231 (and 6226) that causes windows to drop the HBA port or for TSM to drop the connectivity to the library.
We have been through a range of tests and can pinpoint this to whenever we zone in the LTO4 drives.
If we use only LTO5 there is no timeout or problem.
Symptoms of this are that a TSMDLST is very slow to poll (incremental slower with increased number of drives) and a windows boot increases in time upwards of 30 minutes, then eventually the HBA will drop the port and log to the event log.
To troubleshoot further we attempted to rollback to the previous driver IBMTAPEx64_6217 which does not install correctly on windows 2008 R2
We have a hardware (and software) case open currently for investigation but I am curious if anyone else has experienced this issue before / recently and have any suggestions?
As we are in the process of migrating from TSM 5.5 to 6.3 on new hardware with new LTO5 drives, it's not an ideal situation to be faced with (Due to the size and complexity of our environment we need to maintain the existing LTO4s until migration is complete)
The hardware we are running on is as follows:
IBM 3584 firmware: B570
20 x LTO5 drive firmware: C7R2
28 x LTO4 drive firmware: A23D
Attached to HP proliant DL380 Gen8's with 16gb Emulex sn1000e dual port cards. (FW: 1.0.11.110 STORPORT DRIVER: 7.2.70.019)
A rough environment snapshot:
1. 1 x Library master + configuration master
2. 5 x library clients (DB ranging from 10gb - 445gb yes you read that right, yes thats scary, yes we want away asap)
3. Fibre connected to IBM 3584 + LTO4 drives only
4. Combination of windows 2003 / 2008 R2 server hosts
5. Approx 500 - 600 nodes
Any help much appreciated - even if it's just a suggestion we haven't thought of :)
We are experiencing LTO4 timeouts in our windows 2008 R2 server environment using IBM driver IBMTAPEx64_w08_6231 (and 6226) that causes windows to drop the HBA port or for TSM to drop the connectivity to the library.
We have been through a range of tests and can pinpoint this to whenever we zone in the LTO4 drives.
If we use only LTO5 there is no timeout or problem.
Symptoms of this are that a TSMDLST is very slow to poll (incremental slower with increased number of drives) and a windows boot increases in time upwards of 30 minutes, then eventually the HBA will drop the port and log to the event log.
To troubleshoot further we attempted to rollback to the previous driver IBMTAPEx64_6217 which does not install correctly on windows 2008 R2
We have a hardware (and software) case open currently for investigation but I am curious if anyone else has experienced this issue before / recently and have any suggestions?
As we are in the process of migrating from TSM 5.5 to 6.3 on new hardware with new LTO5 drives, it's not an ideal situation to be faced with (Due to the size and complexity of our environment we need to maintain the existing LTO4s until migration is complete)
The hardware we are running on is as follows:
IBM 3584 firmware: B570
20 x LTO5 drive firmware: C7R2
28 x LTO4 drive firmware: A23D
Attached to HP proliant DL380 Gen8's with 16gb Emulex sn1000e dual port cards. (FW: 1.0.11.110 STORPORT DRIVER: 7.2.70.019)
A rough environment snapshot:
1. 1 x Library master + configuration master
2. 5 x library clients (DB ranging from 10gb - 445gb yes you read that right, yes thats scary, yes we want away asap)
3. Fibre connected to IBM 3584 + LTO4 drives only
4. Combination of windows 2003 / 2008 R2 server hosts
5. Approx 500 - 600 nodes
Any help much appreciated - even if it's just a suggestion we haven't thought of :)