UNSOLVED

Tubs1

updated

13 years ago

T

Tubs1

11 Posts

0

1374

July 10th, 2013 05:00

Aggregate Links?

I'm currently in the process of install a VNXe 3150, and wondering if anyone could offer advice on if links should be aggregated.  (teamed, trunked)

On the server side, Microsoft recommend that for iSCSI access, that link should use MPIO rather than being aggregated/teamed/trunked.

I'm currently running one iSCSI server on SPA which has ETH10 & ETH11 aggregated.  (10GB Links)

I've not seen anything specific in the VNXe 3150 documentation that advice either way regarding iSCSI.

What also would be the better configuration when using CIFS/SMB, as I'm intending to use ETH1 & ETH2 (1GB Links) for CIFS/SMB access.

Any Advice or comments?

  • Tubs1

    11 Posts

    476

    0

    Posted July 10th, 2013 06:00

    Ah, sorry I should explain a bit more.

    ETH10 & ETH11 on SPA & SPB are aggregated already - I can't do one without the other.

    SPA ETH10&ETH11 are trunked on the switch as Trunk11, and SPBETH10&11 are trunked as Trunk13.  This all seems to be working correctly.

    My question, isn't how I do the trunking, but rather if I should do trunking in this way.  This is to be combined with Server 2012 and Hyper-V, with iSCSI for system drives, and possibly some SMB3 storage.

  • LeeGoodwin

    19 Posts

    476

    0

    Posted July 10th, 2013 06:00

    There is some information out there H8178 detailed storage view that will detail

    When you set the LACP on the VNXe for all the 4 ports it is bound for both SPA and SPB ,

    LACP for VNXe will only span the 4 Ports for the Storage Processor (SPA or SPB) which you have selected at the creation time

    Example - You have created a Shared Folder Server on SPA , then it will use the 4 Eth ports on SPA for LACP , again you have created  on SPA create a second identical on SPB .

    On the switch you will have to create 2 port groups for each SP with 4 eth ports. This is necessary for failover to work correctly.

    either use a single IP per link or multiple IP's

  • LeeGoodwin

    19 Posts

    476

    0

    Posted July 10th, 2013 07:00


    There is a detailed document.whitepaper just type SMB3.0 and VNXe on Support.com and there is loads of decent tips help and information on configuration

  • Tubs1

    11 Posts

    476

    0

    Posted July 10th, 2013 07:00

    I have the "CIFS dcoument "EMC VNXe Series Using VNXe System with CIFS shared Folders", printed out and on my desk. It tells me how to do things, but not in what scenario it would be most useful or pointless.

    Your search terms return very little of any value, indeed, this question is the number one search response.

    Thanks for you help, anyway.

  • kaustubh1

    12 Posts

    476

    0

    Posted July 22nd, 2013 20:00

    Here we will have to understand the Use of CIFS Shares first.

    If its intended to be used by servers for File Access.  I would suggest keep it simple(Without Aggregation) as Aggregating ports On VNXe does not really offers more Bandwidth.

    Instead If its use by End Users for their Day to day activity. I would suggest to use 2 IP address configured on one Share folder server.

    This will allow Manual load balancing and Can use 2 Links efficiently for file sharing. We can Create home Directory With  with In Domain Controller and Utilize those two Path Very effectively.

    Let me know if you are really wants to know more on How can we configure this in Real environment.