Yes, I have read about that. Another company not me installed and configured the SAN system in my company. I have been trying to resolve a dozen of problems for several months. I had a kind of reasearch to solve persistant binding issue due to many problems, I suspect caused by the lack of persistent binding. The system is not going to grow for at least 2 years.
Firstly, Yes there is problem with HBA. One HBA is with one target which is supossed to be with pesistent binding, but no path is included - it is empty. No automapping as well. On servers which can operate with a jukebox, the path are included to
Well, persistent path naming seems to be OK. I have come accross several white papers from emc and MS as well. At the end of reading some of them I was completely confused. The installed drivers were native, and I did as well for IBM Ultrium for new server nodes (There is only one device driver for Tape1 in Device Manager). "The company" did poor job in installation and administration of SAM system in my company. I do not have power and authority to change what they have done.
Tape Drivers in Device Manager are (for all severs) Tape0 and Tape1:
ibmtp2k3.sys ibmtpft2k3.sys ntutil.exe (what is that?)
For new server: only Tape0 (driver detail same, I mean driver files). I have to install driver for IBM Ultrium TD3.
I am guessing here. But it's sounding like this server has 2 HBA's. One of the HBA's has 1 drive zoned and the other one has the other tape drive zoned. Which is wise. Gives redundancy in some aspects. Except for when the HBA that goes bad is the on the Tape Drive with the controller patrh for the library.
So, here is my simple little test if in fact each drive is zoned to a different HBA. The HBA with the drive that is working, zone the drive that isn't working to that HBA and see if it appears correctly then.
The problem was in "hardware" nature and that was obvios when I have look at target apping at the first oo emulex adapter, which was set with attribuite "Automapping" to No. I am bit cautiuos to change automapping to disable. I do not know what is the meaning of od D_ID and SCSI_ID. What is use of refresh button? I a having problem undestanding what HBA is and how to function. What I mean very basic.
pereubu
86 Posts
0
October 6th, 2009 04:00
Firstly, Yes there is problem with HBA. One HBA is with one target which is supossed to be with pesistent binding, but no path is included - it is empty. No automapping as well. On servers which can operate with a jukebox, the path are included to
Well, persistent path naming seems to be OK. I have come accross several white papers from emc and MS as well. At the end of reading some of them I was completely confused. The installed drivers were native, and I did as well for IBM Ultrium for new server nodes (There is only one device driver for Tape1 in Device Manager). "The company" did poor job in installation and administration of SAM system in my company. I do not have power and authority to change what they have done.
Tape Drivers in Device Manager are (for all severs) Tape0 and Tape1:
ibmtp2k3.sys
ibmtpft2k3.sys
ntutil.exe (what is that?)
For new server: only Tape0 (driver detail same, I mean driver files). I have to install driver for IBM Ultrium TD3.
Message was edited by:
DoleBludger
HacknDos1
66 Posts
0
October 6th, 2009 08:00
So, here is my simple little test if in fact each drive is zoned to a different HBA. The HBA with the drive that is working, zone the drive that isn't working to that HBA and see if it appears correctly then.
pereubu
86 Posts
0
November 30th, 2009 03:00