2020. 2. 14. 13:36ㆍ카테고리 없음
Hp 3par storeserv hp storageworks msl2024 concepts guide os 3. There are Hp storageworks msl2024 warranties, implied or otherwise, with regard to this information or its use. About this product Product Storagewofks The HP StorageWorks MSL Tape Library is the ideal entry-level tape library that provides tape library storagewoks and extensive.
Hi I have DL380G5 8TB storage server. This has SC11Xe HBA fitted to which is connected a MSL2024 LTO-4 Ultrium 1840 SCSI Drive Library. All firmware and drivers are latest versions. Backup software is CA BrightStor 11.5 SP3 When running a backup it fails with the CA software reporting unknown hardware SCSI error, but the Server and Tape library show no hardware errors.
Rebuilt system with recovery DVD and installed CA BrightStor 12 and got same error. Replaced server and library hardware completely with new and got same error with CA 11.5 and 12. Rebuilt with DVD and installed Backup Exec v 12 and got same error!!! However, Backup exec forum said thet the HP Management Agents were know to cause this problem. Rebuilt original hardware, disabled HP Agents and installed CA 11.5 SP3 and backups now run fine. 1.2TB in 4.5 hours.
HP LaserJet Pro P1606 Driver Download. HP LaserJet Pro P1606 Driver Software Download for Windows 10, 8, 8.1, 7, Vista, XP and Mac OS HP LaserJet Pro P1606 has a stunning print capability, this printer is able to print with sharp. HP StorageWorks MSL2024 - Tape library - LTO Ultrium - max drives: 2 - rack-mountable - 2U - bar code reader - for ProLiant DL120 G7, DL120 G7 Base, DL120 G7 Entry, DL120 G7 Performance The HP StorageWorks MSL2024 Tape Library is the ideal entry-level tape library that provides tape library capacity and extensive tape library features in the compact form of a tape autoloader.
So, how do I get round this as I want to remote monitor server with Agents. Anyone seen this before? I've heard good results for working around this problem by changing a registry entry for the StorPort Driver. See for details. An excerpt from that document for the registry entry that needs changed: HKEYLOCALMACHINE System CurrentControlSet Enum SCSI DeviceParameters Storport Value - BusyRetryCount Type - DWORD Data - 20 Decimal (default) Range - number of retries I don't know what the magic value is that works but 20 was probably just a guess for a good retry value. I would recommend you change it to 32 or 64.
We have been experiencing the same exact problems with the following setup: DL320s G1 server, SC44Ge HBA connected to MSL2024 library with 2 SAS LTO-3 Ultrium 920 drives. All firmware is up to date. I just updated the Storport driver to 5.2.3790.4021, but don't see the option in the registry to change the BusyRetryCount. I also just updated the Insight agents from 7.80 to 8.10. Hopefully this resolves the issue.
Hp Msl4048 Firmware
I don't want to disable the HP agents, that is not a valid workaround in my opinion. Some other thoughts: we only see the issue when both tape drives are powered on.
If I disabled one, backups are successful. When both are enabled, it doesn't matter if they are both actively being used, it will fail with a Bus reset. Crossing fingers for tonight's backups. HP support recommended that I increase the BusyRetryCount to 75 and test again. I will post the results.
Here are the errors for LSISAS: Event Type: Error Event Source: Lsisas Event Category: None Event ID: 11 Date: 7/30/2008 Time: 11:52:40 PM User: N/A Computer: KSTLON0AP002 Description: The driver detected a controller error on Device RaidPort1. For more information, see Help and Support Center at Data: 0000: 0018000f 0060000 c004000b 0010: ad0000 000: 000000 000: 00000000 c004000b 0000000 Then this error saying the drive went offline: Event Type: Error Event Source: Storage Agents Event Category: Events Event ID: 1223 Date: 7/30/2008 Time: 11:52:40 PM User: N/A Computer: KSTLON0AP002 Description: SAS Tape Drive Status Change. The tape drive in Slot 1, Device 6 with serial number 'HU10726KDG', has a new status of 3. Very interesting data in the LSI SAS event log entry. The data looks good with a valid LSI header but the error code doesn't look like any I have ever seen with this card. The error code is at byte 10 and in this data is 0xad010030 but LSI SAS errors should always start with a 0x30,0x31, or 0x32. I suspect that this may have been set at some higher level in the LSI driver and I don't have the specs for all the layers.
I'll have to dig a bit and see if I can come up with something. Do all of the LSI SAS event entries have the same data starting at offset 0x10?
If there are any 0x3. Values that would be useful. They all seem to be similar. Here is the error when both tapes drives went offline: Event Type: Error Event Source: Lsisas Event Category: None Event ID: 11 Date: 7/30/2008 Time: 4:24:39 PM User: N/A Computer: KSTLON0AP002 Description: The driver detected a controller error on Device RaidPort1. For more information, see Help and Support Center at Data: 0000: 0018000f 0060000 c004000b 0010: 311000 000: 000000 000: 00000000 c004000b 0000000.
Hp Msl2024 Firmware
I just re-read your message, so I believe that is the error you were used to seeing. I seem to get both of those sometimes. They also appear with this error: Event Type: Warning Event Source: Lsisas Event Category: None Event ID: 129 Date: 7/28/2008 Time: 11:44:30 PM User: N/A Computer: KSTLON0AP002 Description: Reset to device, Device RaidPort1, was issued. For more information, see Help and Support Center at Data: 0000: 0010000f 006001 0010: 000000 000: 000000 000: 0000081. Yes it's very possible that there is a problem with the controller or the software/driver stack. The two drives are entirely independent from the library perspective so I can't think of anything that could happen to cause problems with having both drives running at once. I've had a lot more than two drives running at once connected to that HBA.
Even from the HBA perspective the drives should be almost completely independent but they would share the same PCIe link and there is some shared hardware on the HBA. I would start by making certain that the application was configured properly to use both drives at once. It sounds to me like there may be some hardware that isn't quite right somewhere in the system though. If you haven't already I would suggest you try getting a different SAS cable. If you have a standard SAS cable laying around with IB to mini-SAS ends you can connect it to one drive and see if that solves your communication issues.
I'm not convinced the cable is the issue however as that cable is actually 4 cables bundled into one casing but physically completely independent so when there are cable issues it is usually just one link that is bad and switching to a different cable end at the library will make the problem go away. We have had very similar issues to the above, DL380 G5 also with the SC44Ge, 920 drives in an MSL2024. We get the LSISAS events 11 and 129 when the backup jobs fail. Our system seems to run for longer with only a single drive when we switch one off (but still fails occassionally). All the firmware, BIOS, drivers are up to date and we have had a drive and SAS card and cable swapped out by support. L&TT reports healthy drives.
Still the problem continues, so it looks to be a driver or inherent hardware fault related to 'high' loads. Does anyone have futher updates on this at HP? Seems like a serious issue for many people. Just an update for all of you. We have had a difficult time with HP trying to resolve this. HP tried to blame the CA BrightStor software for a few months but all testing proved there was an issue with the SCSI HW or drivers. We switched to fibre channel drives in the MSL2024, for testing, and all problems dissapeared!
The trouble is that HP have tried to shed all responsibility for this trouble and to date have yet to agree a way forward to finally fix this isue. My company is so disgusted with HP that I am now in talks with Dell to replace all 107 HP servers we use as well as the 1400 desktops.