UNSOLVED

duhaas1

updated

15 years ago

D

duhaas1

2 Intern

•

227 Posts

0

2292

April 27th, 2012 15:00

VNXe 3100 NFS Network Layout (non stacked switches)

Just looking for some validation of the following setup.  I've read over the HA guide, and although the guide goes over the majority of configs, unless I'm blind it seems to assume you have stacked switchs, in my case I dontL

Here are the swtichs in which I'll be using for storeage connectivity, these are Ciscio 2960G

http://img1.uploadscreenshot.com/images/orig/4/11709064017-orig.png

Here is a layout of my VNXe3100 and the corresponding ports:

http://img1.uploadscreenshot.com/images/orig/4/1170907459-orig.png

Since my switchs are not stacked, and I want to leverage the redundant switchs I'm planning the following layout as you can see the mappings.  This would end up giving me four distinct IP's in the end for the NFS mounts. 

Or should I setup a LACP pair on Swith 1 from SPB and a LACP pair on Switch 2 from SPA just making sure they are on the same subnet so that FSN works properly in the event of a SP failure.  Any suggestions/recommendations anyone has would be great.

The other thing I should note is vsphere 5 (2 hosts) will be on the other side of the VNXe

  • RM-Hsp

    15 Posts

    554

    0

    Posted May 3rd, 2012 03:00

    I guess you can still stack the network switches:- https://supportforums.cisco.com/thread/2111692

    You're 2 ports) & LACP-2 (SPB-4 & 5) - will be better.

  • duhaas1

    2 Intern

    •

    227 Posts

    554

    0

    Posted May 3rd, 2012 05:00

    Thanks for the feedback.  Just to confirm, with the LACP creation on each of the two switchs, the channel needs to be configured for the same vlan is that correct in order for FSN to function properly?

  • chrislogo

    98 Posts

    554

    1

    Posted May 3rd, 2012 21:00

    Since your switches are not stacked your LACP configuration between SPA eth2(port4) and SPA eth3(port5)  which goes to different switches would not work as per the HA guide.

    For this to work the switches should be stacked.

  • duhaas1

    2 Intern

    •

    227 Posts

    554

    0

    Posted May 7th, 2012 14:00

    Thanks everyone for the feedback.  So, just so I'm clear, because the two switchs are not stacked, Is setting up each interface with its own IP the best route to go? 

    SPB Port 2 - Switch 1 Vlan100

    SPB Port 3 - Switch 2 Vlan101

    SPA Port 2 - Switch 1 Vlan100

    SPA Port 3 - Switch 2 Vlan101

    Then creating a shared NFS folder on each of the four interfaces, giving me 4 NFS mounts in vsphere.

  • 554

    1

    Posted May 9th, 2012 07:00

    You could do the following:

    1. Create LACP pair of eth2 and eth3. Port 1 and 2 goes to first switch and 4 and 5 goes to the second switch.
    2. You could create 2 shared folder servers (one on each SP).

    This way, your FSN would kick-in in case of a failure.

    Is there reason to go with NFS? Because, if you can use iscsi, you could make use of multipathing to provide redundant paths to ESX server.

  • duhaas1

    2 Intern

    •

    227 Posts

    554

    0

    Posted May 9th, 2012 13:00

    Your assuming correct that each of the LACP pairs are on the same subnet correct, in order for FSN to operate properly?  The issue I have with that in using NFS is that I need to have my two destinations on different networks in order to utilize multiple paths on the ESX side.  ISCSI might be the better route to take in this case.  Thoughts?

  • 554

    1

    Posted May 10th, 2012 06:00

    Yes they have to be on the same subnet for the SP failover case to work. If you are looking for multipath, iscsi would be a better option.