Disk Enclosures
cancel
Showing results for 
Search instead for 
Did you mean: 

MSA 2000fc direct connect

SOLVED
Go to solution
Max Sorokin
Regular Advisor

MSA 2000fc direct connect

Hi All,

We want to connect one server with 2 HBA to the MSA 2000fc using direct connect without fibre channel switches.
If there some problems or bugs when using direct connect?

BR,
Max
/Maxim
14 REPLIES
RM782
Trusted Contributor
Solution

Re: MSA 2000fc direct connect

Hi Max

One server, 2 * HBAs connect fibre cables to P0 on both controllers ( the ports on the left)
Max Sorokin
Regular Advisor

Re: MSA 2000fc direct connect

Is there any HBA settings when using direct connect?
/Maxim
RM782
Trusted Contributor

Re: MSA 2000fc direct connect

point to point
Max Sorokin
Regular Advisor

Re: MSA 2000fc direct connect

What about multipath drivers? Does it works in direct connect configuration?
/Maxim
Uwe Zessin
Honored Contributor

Re: MSA 2000fc direct connect

In the QLogic adapters, "point to point" refers to Fabric switch connectivity - you need to select 'loop' for FC_AL protocol.
.
Max Sorokin
Regular Advisor

Re: MSA 2000fc direct connect

I' confused about following: in MSA 2000fc cabling guide host must be connected to the P1 ports on each controller, but in the MSA 2000fc user guide host must be connected to the P0 ports on each controller and i don't know where is correct solution. (please see attachment for details)
/Maxim
Uwe Zessin
Honored Contributor

Re: MSA 2000fc direct connect

I'd say that both are 'correct' examples.

Can you give me the document and page numbers so that I can check the context, please?
.
Max Sorokin
Regular Advisor

Re: MSA 2000fc direct connect

HP StorageWorks MSA2312/2324fc Configuration Poster - Page 1

HP StorageWorks 2312fc and 2324fc Modular Smart Array user guide - Page 27
/Maxim
RM782
Trusted Contributor

Re: MSA 2000fc direct connect

Hi Max

Just checked my documents Uwe is correct on the Direct attach sorry for my error earlier.

My details say for the MSA2000fc Direct Attach via FC-AL or Private Loop.

Both cabling concepts are correct, my details are as follows:

One server, dual HBA use P0s

Two servers, first server use the P0s, second server use the P1s

for mulitple hosts single paths: (Max of 4 servers)
Server1 P0 Controller B, Server2 P0 Controller A, Server3 P1 Controller A and Server4 Controller B port1
Uwe Zessin
Honored Contributor

Re: MSA 2000fc direct connect

> via FC-AL or Private Loop.

Private Loop or Public Loop are both using Fibre Channel Arbitrated Loop (FC_AL) protocol. The first one uses 8-bit addresses. The second one uses 24-bit addresses with a Fabric Switch (FL_Port) as part of the loop.
.
Max Sorokin
Regular Advisor

Re: MSA 2000fc direct connect

Thanks for answers, but i need to know what about multipathin, did it work in direct connect? and how direct-conect works in real life, what about stability of this solution?
/Maxim
RM782
Trusted Contributor

Re: MSA 2000fc direct connect

Hi Max

Multipath installation is the same, and has an impact on event handling, request handling and device initialization.

Software can be download from:

http://www.hp.com/go/msa

Download the HP msa2000 mpio dsm package under software and drivers.

The drivers are installed under:
C;\program files\Hewlett-Packard\HP MPIO DSM\msa2000

dsmcli is the utility used to manage mpio

Bora Bozgeyik
Occasional Advisor

Re: MSA 2000fc direct connect

Hi,

I'd like to ask a question which may not be directly related to this thread but I couldn't find any other.

My problem is that I can't run any command in dsmcli. All of the commands fail with "command failed!" message.

My machine is
- DL380 G5
- DSM MPIO version is 2.2.0.22.
- Win2003 32-bits.
- Emulex HBAs

Best Regards,

Bora
ajbloor
Occasional Visitor

Re: MSA 2000fc direct connect

After reading this and looking at the documentation I am confused. I have what I believe are a couple of straightforward questions:

Environment.

1 x DL580 Server with 2 single port HBA's.
1 x HP MSA2000fc with dual controllers.
VMWare ESX 3.5 runing on server
Currently cabled HBA0 to CTLA Port 0, HBA1 to CTLB Port 0.

One Virtual Disk created
Two LUNs created
Each LUN presented to ALL hosts

ESX see's both LUNs on HBA0 but nothing on HBA1 (during normal operation - no failover testing performed to-date)


Questions:

1. I currently do not have PORT INTERCONNECT enabled - do I need this ?
2. Is the cabling correct, or should I have one HBA0 to CTLA Port 0 and HBA1 to CTLB Port 1 ?
3. Anything else I am missing ?

Thanks.