StoreEver Tape Storage
cancel
Showing results for 
Search instead for 
Did you mean: 

cabling msl5052 4 drive to old Compaq MDR

SOLVED
Go to solution
Vincon Daniele
Frequent Advisor

cabling msl5052 4 drive to old Compaq MDR

Anyone know how to cabling MSL5052 with 4 SDLT to old compaq?
My customer have a lot of problem with NSRE1200 and now i try to use the old MDR.

Thank's

20 REPLIES
Steven Clementi
Honored Contributor

Re: cabling msl5052 4 drive to old Compaq MDR

Well... the cabling is basically the same or at the very least similar.

Perhaps we should review your current cabling with the NSR first to see if we can resolve those problems...

Can you post a diagram or some additional information about the config?

Info about the NSR... as well as the MDR. Since you have a 5052, can I assume you have 2 NSR's in the back with 1 robotic controller card?

Whats the backup software your customer is using?


Steven
Steven Clementi
HP Master ASE, Storage and Clustering
MCSE (NT 4.0, W2K, W2K3)
VCP (ESX2, Vi3, vSphere4, vSphere5)
RHCE
NPP3 (Nutanix Platform Professional)
Vincon Daniele
Frequent Advisor

Re: cabling msl5052 4 drive to old Compaq MDR

hi..
the cabling is standard cabling for msl5052 with 1 NSR not 2.

Probably i must disconnect the 2 vhdci cable from library to NSR and connect to MDR.
My mdr have 4 port LVD and 2 port HVD (used by old TL891 dismissed).

i try o find cabling schema

thank's
David Ruska
Honored Contributor

Re: cabling msl5052 4 drive to old Compaq MDR

I would like to understand what issues you hare having with the NSR, since it's a considerably newer router than the MDR (which was discontinued some time ago).

Are you running the latest firmware in the NSR (5.6.69)?

Are you in a supported configuration (listed in the EBS compatability matrix - www.hp.com/go/ebs) and on the latest driver & hba firmware revisions?

Have you disabled windows RSM?
If you are on Windows 2003, have you disabled the plug & play polling?
Have you disabled Insight Manager polling?
Is there anything else in your SAN that could be polling the library/drives?

Do you have any event logs from the NSR we could review?
The journey IS the reward.
Vincon Daniele
Frequent Advisor

Re: cabling msl5052 4 drive to old Compaq MDR

I've last firmware in all object:
NSR,Library,FCHBA
and last drivers for all server in san.
I don't know how to disable in windows 2003 san polling,but all windows 2000 have RSM disable.
The configuration is supported.
I've attached a log with some error.

Sorry for my english!

Bye
David Ruska
Honored Contributor
Solution

Re: cabling msl5052 4 drive to old Compaq MDR

> I don't know how to disable in windows 2003 san polling

Here's the document:
http://h20000.www2.hp.com/bizsupport/TechSupport/Document.jsp?objectID=PSD_OT040301_CW01

The event log you provided showed a lot of DSA errors, but they were immediately after a write error (SK/ASC/ASCQ = 0x3,0x0C,0x00), and I would therefore ignore those. There is one assertion the next day. I believe there's an assertion trace you can collect that might help. Has this assertion happened before?
The journey IS the reward.
Steven Clementi
Honored Contributor

Re: cabling msl5052 4 drive to old Compaq MDR

Can you also attach or tell us what the Device mappings are? (from the NSR).


Steven
Steven Clementi
HP Master ASE, Storage and Clustering
MCSE (NT 4.0, W2K, W2K3)
VCP (ESX2, Vi3, vSphere4, vSphere5)
RHCE
NPP3 (Nutanix Platform Professional)
Vincon Daniele
Frequent Advisor

Re: cabling msl5052 4 drive to old Compaq MDR

I make a static mapping with library and all host in the san, not auto assign.

Yesterday the library goes off line after another Assertion error, in last months i've a lot of problem and the backup jobs hang.

this is NSR number 3 i've changed but the problem is the same.
HP support have schedule a visit for my customer next week.

thank's
Marino Meloni_1
Honored Contributor

Re: cabling msl5052 4 drive to old Compaq MDR

Assertions on NSR are usualy caused by external factors, could you collect a full report, select print view and capture and attach it here, analysis of the traces could help in finding the route cause of the problem

Marino
Vincon Daniele
Frequent Advisor

Re: cabling msl5052 4 drive to old Compaq MDR

This is the last log of NSR, tonight all backup job are ok.

Vincon Daniele
Frequent Advisor

Re: cabling msl5052 4 drive to old Compaq MDR

Marino wrote: could you collect a full report....

I Marino, what type of report you need? trace log and scsi command?

In monday i visit my customer and i send all trace log.

Thank's
Marino Meloni_1
Honored Contributor

Re: cabling msl5052 4 drive to old Compaq MDR

I'm seeing several HW errors on the scsi bus, related to both drives, (diconnections,bus reset and write errors) these do not seems strictly related to the assestion, but need to be investigate.
I also see that more than one host is issuing commant to the drives. Have you a zone just for backup in your san? have you several servers that can see the library? in this case you need to apply rules to all the servers (TUR disabled, Agent 7.2 or higher with FC agent disabled, RSM stopped....

For the assertion, I would be nice to have the complete report, (not only the log) including configuration and assert traces.

answering your last question: everything in the report


Vincon Daniele
Frequent Advisor

Re: cabling msl5052 4 drive to old Compaq MDR

Goodmorning ! in attachment all trace and report of my customer.

We have 2 SAN, one at 1 Gb with MA8000 and other at 2Gb with EVA3000.
But the problem is the same, Assert error and random reboot of NSR.

In all SAN are Zoning (port zoning) and the firmware & Drivers are update.

Thank's
Marino Meloni_1
Honored Contributor

Re: cabling msl5052 4 drive to old Compaq MDR

Could you tell me what HBA you have?
and if it is a emulex or KPGSA, have you the parameter ResetTPRLO set equal 2 in the registery parameter?
Vincon Daniele
Frequent Advisor

Re: cabling msl5052 4 drive to old Compaq MDR

Yes the parameter ResetTPRLO is set to 2 in every HBA ,
On 1Gb SAN we have LP8000
On 2 Gb SAN we have LP952

Thank's
David Ruska
Honored Contributor

Re: cabling msl5052 4 drive to old Compaq MDR

Vincon,

Marino did an excellent job reviewing the event log.

I spoke with the division engineering team to get their comments on the event log as well.

First, as Marino mentions, there are multiple host IDs attempting to communicate to the library, most likey doing some type of polling. You can see log sense commands in particular. The host(s) sending these commands are most likely using a very short timeout, and then attempt to abort the command and eventually sends a bus reset. This is bad news when the library controller is on a shared bus with a drive - it could kill an I/O that is pending with the drive.

So I would suggest that you look for and disable any polling applications that could be communicating to the library, or alternately change the zoning and/or NSR mapping so only the host controlling the robot has access to the library controller lun.

Second, there are multiple DSA errors after a write error, and eventually an assertion.

The sequence matches a problem we've identified as a possible issue in 5.6.69 (and likely earlier) firmware and are working on a fix. If you can open an elevation with HP support, and have it raised to tier 3 we can provide you with the fix when it is available.

The workaround for this issue is to eliminate the cause of the write errors (e.g. by filtering media, running drive assessment tests, etc).
The journey IS the reward.
Marino Meloni_1
Honored Contributor

Re: cabling msl5052 4 drive to old Compaq MDR

I reviewed the traces, and cannot found a root cause on it, the traces are a very shoort snapshot about the activity, and it is not easy to capture what is needed.
Anyway I would start the troubleshooting perfoming the suggested list of actions, this should start to give you some results, and I my opinion is better than trying to install a MDR

marino
Marino Meloni_1
Honored Contributor

Re: cabling msl5052 4 drive to old Compaq MDR

Also, it may be time to call HP support ;)
David Ruska
Honored Contributor

Re: cabling msl5052 4 drive to old Compaq MDR

Just to be clear, this sequence in the trace:

62. 08/12/2005 21:13:25 2d04h40m35.12s SCSI port 1 invalid DSA
63. 08/12/2005 21:13:25 2d04h40m35.12s SCSI port 1 invalid DSA
64. 08/14/2005 04:25:04 3d11h52m14.75s Assertion failed: 0, file ../ps_driver.c, line 3119
65. 08/14/2005 04:25:04 3d11h52m14.75s Assertion failed (continued): 3119

It does match an issue we (HP engineering) are working on and should have a solution available soon. It is an error condition that's triggered by a write error, so reducing those is a workaround.

Please open a case with HP if need early access to the fix for the above.
The journey IS the reward.
Vincon Daniele
Frequent Advisor

Re: cabling msl5052 4 drive to old Compaq MDR

David Ruska:
Please open a case with HP if need early access to the fix for the above.


I'm in contact with HP support people and we are investigate in all components of SAN
I inform you if resolve the problem.

Thank's
David Ruska
Honored Contributor

Re: cabling msl5052 4 drive to old Compaq MDR

>> Here's the document:
>> http://h20000.www2.hp.com/bizsupport/TechSupport/Document.jsp?objectID=PSD_OT040301_CW01

 

That link is no longer active. Here's a current one:

 

http://h20000.www2.hp.com/bizsupport/TechSupport/Document.jsp?lang=en&cc=us&objectID=c01204790

Removable Storage Manager (RSM) in Windows Server 2003 is not Disabling Properly Which Causes Performance Issues in Enterprise Backup Solutions (EBS).
The journey IS the reward.