- Community Home
- >
- Storage
- >
- Entry Storage Systems
- >
- Disk Enclosures
- >
- Re: MSA 2000fc direct connect
Categories
Company
Local Language
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Discussions
Discussions
Forums
Forums
Discussions
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Community
Resources
Forums
Blogs
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО04-01-2009 03:11 AM
тАО04-01-2009 03:11 AM
Re: MSA 2000fc direct connect
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.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО04-01-2009 03:27 AM
тАО04-01-2009 03:27 AM
Re: MSA 2000fc direct connect
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО04-01-2009 03:53 AM
тАО04-01-2009 03:53 AM
Re: MSA 2000fc direct connect
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
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО05-13-2009 05:11 AM
тАО05-13-2009 05:11 AM
Re: MSA 2000fc direct connect
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
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО03-16-2010 02:02 AM
тАО03-16-2010 02:02 AM
Re: MSA 2000fc direct connect
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.
- « Previous
-
- 1
- 2
- Next »