- Community Home
- >
- Storage
- >
- Entry Storage Systems
- >
- MSA Storage
- >
- Re: HP MSA 1500 SAN and Windows Server 2003
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
тАО12-08-2004 12:10 AM
тАО12-08-2004 12:10 AM
Re: HP MSA 1500 SAN and Windows Server 2003
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО12-08-2004 12:23 AM
тАО12-08-2004 12:23 AM
Re: HP MSA 1500 SAN and Windows Server 2003
To use SSP, once you figure out which server is which, you enable LUN access by just checking the checkbox under the Logical Drive number at the top. Ultimately, you should have something like this...
Hosts Lun 1 2 3 4
Host 1........X
Host 2...........X
Host 3..............X
Host 4.................X
You can use the hba utilities to find your WWID's. LPutilnt (for Emulex) or HBAnywhere. or physically as the id should be stamped on the card somewhere.
Steven
HP Master ASE, Storage, Servers, and Clustering
MCSE (NT 4.0, W2K, W2K3)
VCP (ESX2, Vi3, vSphere4, vSphere5, vSphere 6.x)
RHCE
NPP3 (Nutanix Platform Professional)
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО12-08-2004 01:42 AM
тАО12-08-2004 01:42 AM
Re: HP MSA 1500 SAN and Windows Server 2003
the MSA1000 /1500 always presents a non-disk SCSI LUN at address #0. That way, you always have management access to the array, even if that particular server does not have a logical disk mapped.
Think about it: when you started, the array did not have any logical disks. How could the server talk to the array? -- Via LUN 0!
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО12-08-2004 06:36 AM
тАО12-08-2004 06:36 AM
Re: HP MSA 1500 SAN and Windows Server 2003
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО12-09-2004 01:27 AM
тАО12-09-2004 01:27 AM
Re: HP MSA 1500 SAN and Windows Server 2003
for the MSA, it's normal to have some adapters "offline". This is because the MSA controllers work in active/passive failover mode. The HBA that is connected to the switch where the passive controller is located will show as offline until a failover occurs. In the SSP setup of ACU, you will see the adapters listed as Local (the server which is running ACU) or remote, and online or offline.
Do you currently have 2 servers with 2 HBAs each connected to the MSA? I would guess that your three connections are described in the SSP section as "Local/Online", "Local/Offline" and "Remote/Online". The WWN of the MSA itself does not show up in this list, only WWNs of attached HBAs. It won't see the 2nd HBA in any "remote" server until you either run ACU locally on that server (close ACU on the first server beforehand), or a controller failover occurs. It's an annoying problem with the MSA, but I haven't found any other way around it.
Regards,
Stephen
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО12-09-2004 01:35 AM
тАО12-09-2004 01:35 AM
Re: HP MSA 1500 SAN and Windows Server 2003
Stephen
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО12-09-2004 01:41 AM
тАО12-09-2004 01:41 AM
Re: HP MSA 1500 SAN and Windows Server 2003
Reminds me a bit about the online/offline field on the HSG which sometimes doesn't properly reflect the situation, either.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО12-09-2004 03:26 AM
тАО12-09-2004 03:26 AM
Re: HP MSA 1500 SAN and Windows Server 2003
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО12-09-2004 03:29 AM
тАО12-09-2004 03:29 AM
Re: HP MSA 1500 SAN and Windows Server 2003
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО12-09-2004 03:50 AM
тАО12-09-2004 03:50 AM
Re: HP MSA 1500 SAN and Windows Server 2003
Yes.
On the blades, the utility HBAnywhere should help you out. (or any server with a QLogic HBA)
Any server with an Emulex hba, the utility LPUtilnt would be helpful.
Additionally, if you have the 8port MSA switch, then I believe you can look at the name server to see the WWID's of all attached devices, including the MSA. You should also be able to "View More Information" on the controiller screen in the ACU and the WWID should be there. (I think).
Steven
HP Master ASE, Storage, Servers, and Clustering
MCSE (NT 4.0, W2K, W2K3)
VCP (ESX2, Vi3, vSphere4, vSphere5, vSphere 6.x)
RHCE
NPP3 (Nutanix Platform Professional)