Solved

HP P2000G3 MSA iSCSI redundancy for VMWare ESXi

Posted on 2011-02-16
4
1,783 Views
Last Modified: 2012-05-11
I'm looking to set up a 1Gb iSCSI P2000G3 hard disc enclosure, and want a redundant config for VMWare ESXi.  I already have two switches, and there'll be two controllers in the storage.  I understand that each controller should be connected to both switches - the wiring is very well explained on HP and DotHill's websites.

What I don't understand is the IP configuration.  I need to configure 4 ports, and they all ned different IP addresses.  Do they need to be on different subnets?  HP say yes, and then give a clear example of different addresses on the same subnet (255.0.0.0 netmask!).

My current iSCSI storage is on 172.17.1.0/24 - can I establish the new storage on that one class-c subnet?  Should I put both port-0s on that subnet and both port-1s on a different subnet?  Should the subnets be routable?  (My router is only 100Mb...)  Should I put subnet A on one switch and subnet B on the other?

I know that's a lot of questions - a link to a decent HowTo would be fantastic! :)

Cheers!
0
Comment
Question by:Filthy_Defiler
  • 2
  • 2
4 Comments
 
LVL 55

Accepted Solution

by:
andyalder earned 500 total points
ID: 34910376
They have to be on different subnets assuming you are not connecting the switches together. If they were on the same subnet the server might try to talk to the controller's IP address on an HBA port it isn't connected to.

See "Two servers/two switches" in http://h20000.www2.hp.com/bc/docs/support/SupportManual/c02520793/c02520793.pdf for example, Server 1 may try to talk to bottom controller left hand port through its top NIC which hasn't got a path to it if everything was on one subnet.

(what the heck "Four servers/multiple switches/SAN fabric" is meant to show I have no idea, we don't know how to wire it up so we'll cover it with a cloud?)

>My current iSCSI storage is on 172.17.1.0/24
You could cut that subnet in half or just use another one, the two switches don't need interconnect and don't need to route between them.

Do you have a current iSCSI storage box that has to have all ports on a single subnet though? That would complicate matters.
0
 

Author Comment

by:Filthy_Defiler
ID: 34914572
So what we're saying then is that (on the diagram you referenced) you have two networks:

1) Port 0 on both MSA controllers, Switch A, and the lower port on both servers.
2) Port 1 on both MSA controllers, Switch B, and the upper port on both servers.

The "Best Practices" whitepaper form HP says the following:

IP Address scheme for the controller pair
The P2000 FC/iSCSI combo G3 MSA (for iSCSI traffic) and P2000 G3 10GbE iSCSI MSA use port 0 of each controller as one failover pair, and port 1 of each controller as a second failover pair. Therefore, port 0 of each controller must be in the same subnet, and port 1 of each controller should be in a second subnet.
For example (with a netmask of 255.0.0.0):
· Controller A port 0: 10.10.10.100
· Controller A port 1: 10.99.10.120
· Controller B port 0: 10.10.10.110
· Controller B port 1: 10.99.10.130

This is what left me confused, because with that netmask they're still on the same subnet :-/
That said, anyone who chops up a Class-A like this should really be relegated to drawing clouds on diagrams instead of actual data paths.  Hmm.

Anyway, I think that's all I was looking for - just a bit of clarity.  Both switches are wired together, but I'll be setting up VLANs, which don't need to be carried across the fibre.  And the existing iSCSI is not fault-tolerant, so it'll just get slung into one of the VLANs until it's retired.

Thanks - now I just need to wait for a big box of stuff to arrive!
0
 
LVL 55

Expert Comment

by:andyalder
ID: 34914680
I'll try to get that rectified, you're right, they typed the netmask in wrong.
0
 

Author Comment

by:Filthy_Defiler
ID: 34914783
Heh - glad I'm not just being stupid.  I was laying out wiring diagrams for most of the day and then I faced that once my mind was mush.  Couldn't fathom it at all!
0

Featured Post

PRTG Network Monitor: Intuitive Network Monitoring

Network Monitoring is essential to ensure that computer systems and network devices are running. Use PRTG to monitor LANs, servers, websites, applications and devices, bandwidth, virtual environments, remote systems, IoT, and many more. PRTG is easy to set up & use.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Suggested Solutions

When converting a physical machine to a virtual machine using VMware vCenter Converter Standalone or vCenter Converter Enterprise, if an adapter type is not selected during the initial customization the resulting virtual machine may contain an IDE d…
Each year, investment in cloud platforms grows more than 20% (https://www.immun.io/hubfs/Immunio_2016/Content/Marketing/Cloud-Security-Report-2016.pdf?submissionGuid=a8d80a00-6fee-4b85-81db-a4e28f681762) as an increasing number of companies begin to…
Teach the user how to use vSphere Update Manager to update the VMware Tools and virtual machine hardware version Open vSphere Client: Review manual processes for updating VMware Tools and virtual hardware versions: Create a new baseline group in vSp…
This tutorial will walk an individual through the process of installing the necessary services and then configuring a Windows Server 2012 system as an iSCSI target. To install the necessary roles, go to Server Manager, and select Add Roles and Featu…

821 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question