NetApp 2040 Initial Configuration

[#1]

Hi all, I can say that we're completely new to NetApp - and we're in a really long queue to get Arrow in to do the install for the box.  Since we're in the queue for another 8 days and really need to start working with the storage we need help.  Tech support won't touch us since we're not "break/fix" - so, I thought we'd hit up the community and ask here.

So what we're trying to do...  We have 2 HP DL380 Servers, both with 2 HBA Cards for ISCSI and SD Cards for their boot device - We're loaded them with Vmware 5.0 and licensed them.  We've assigned the HBA's ip addresses in the 192.168.50.x block.  We have a new 2040, just out of the box.  About the only thing we've been able to do successfully to it is assign 192.168.50.x addresses to e0a, e0b and a reachable network address for e0P on both controllers.

Goal - directly connect the storage via iSCSI, setup a Lun and get Vmware to find the storage so we can work with it.

Vmware1-(10.25.17.100)

HBA 192.168.50.101   direct connect----> NetappBottom e0a 192.168.50.1

HBA 192.168.50.111  direct connect---->  NetappTop e0a 192.168.50.11

Vmware2-(10.25.17.100)

HBA 192.168.50.102  direct connect---> NetappBottom e0b 192.168.50.2

HBA 192.168.50.112 direct connect---> NetappTop e0b 192.168.50.12

Netapp with onTap 7.36

Bottom e0P 10.25.17.10

Top e0P 10.25.17.11

Netapps disks are owned the two controllers, kind of randomly.  vol0 is with aggr0, and aggr0 has 3 disks associated with it.

The good news is we have access to the console and figured out onCommand system manager.

We'd like this configuration to be able to failover and like to use as many of the 500gb disks as possible for our vm's with one spare available for all.

Anything you can do to direct us in the right direction would be hugely helpful.  A guide for dummies would be brilliant, Thanks!

[#2]

In your configuration NetApp likely won't be able to access one of Vmware servers (each controller possibly different server). It has nothing to do with NetApp specifically, but simply how TCP/IP communication works. Use different subnets for different adapters.

[#3]

Hi, are you suggesting to use:

Vmware1-(10.25.17.100)

HBA 192.168.51.101   direct connect----> NetappBottom e0a 192.168.51.1

HBA 192.168.52.111  direct connect---->  NetappTop e0a 192.168.52.11

Vmware2-(10.25.17.101)

HBA 192.168.61.101  direct connect---> NetappBottom e0b 192.168.61.1

HBA 192.168.62.111 direct connect---> NetappTop e0b 192.168.62.11

After I get the network configured correctly, what can i do about the disks to get the max size avail for vm hosts?

[#4]

Yes, something like that.

There are really plenty of discussions about what to do on small filers to maximize available space. Just try search

[#5]

Do the search results come with a magic decoder ring?

[#6]

Where to start

should be fairly easy

* open ssh or local tech on the ESXi and try to vmkping to the iscsi ip address of your netapp see if the connection is there

* I would recommend using a switch or even two for fully redundancy and future grow with more ESX to come and not direct connect

* If you can install vcenter on local drives (not sure you got the space) and install VSC(virtual storage console) you can use it to create attach and much more via vCenter to the netapp (recommended way)

* Creating Vif from the two card is also recommended use single if your using unmanaged switches with trunked cable to work out the VLANS

hope that helps