HPE 6600 design of square topology with DT-lacp with VRRP AND IPV6 ROUTING


As the title states we need to implement dt-lacp for our vsphere servers, iscsi will be in use to our msa2040 san as well so jumbo frames all around.

So far this is all straight forward.

The kicker here is we also want to implement a switch pair to function as the routing for our core. we run a dual homed network with ipv4 and ipv6 routing. dt-lacp does not work with v6 so how would the links to the route pair support high availability? STP seems to be the only way? is there a more novel approach i'm missing?
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

N. SpearsSr.Net.EngCommented:
I'm confused by your question. It's my understanding that dt-lacp is another flavor of Virtual Port Channels like in Nexus correct? That stated, why would you need them to support ipv6 or ip at all since they are layer 2 connections?  Are you trying to do layer 2 high availability or layer 3 or both?
masteritlionAuthor Commented:
I'm trying to do both.

this switch pair is doing ipv4 L3. however dt-lacp restricts L3 ipv6.
so the issue is how would you do HA for v6 while still maintaining HA for v4?

the plan is to have l2 and l3 HA.
Andrew Hancock (VMware vExpert / EE MVE^2)VMware and Virtualization ConsultantCommented:
what design do you have in place for your vSphere Servers ?

how many hosts ?
Maximize Customer Retention with Superior Service

The IT Service Excellence Tool Kit delivers expert advice for technology solution providers. Get your free copy for valuable how-to assets including sample agreements, checklists, flowcharts, and more to help build customer satisfaction and retention.

masteritlionAuthor Commented:
Shared storage for vmotion. fault tolerance, LACP on the dswitch for vm's. iscsi for shared storage with mpio via separate links and dswitches for those.

my question mainly pertains to creating a highly available L2/L3 core. i'd prefer if our HA of vsphere is kept separate from this solution. i.e it is already highly available as much as it can be.  the network has many client devices which need to be able to failover in case one switch went down as well. routing is done at the core, not at the aggregate or edge switches.
N. SpearsSr.Net.EngCommented:
At the core you want to run  HSRP or VRRP depending on the vendor switches that you have. For layer two fault tolerance you want to implement port-channels/LAGs between the switches. Depending on the vendor switch you have you can implement mult-ichassis link aggregation or port-channeling. This will work for IPV4 or IPV6.
masteritlionAuthor Commented:
that's the jist of it. it's the vendor nuances that i'm trying to figure out. the last piece of the puzzle is LACP to the servers. we're wanting to implement dt-lacp which would be a multi-chassis lag.
with HPE, dt-lacp can't be enabled while ipv6 L3 routing is enabled on the switches. which is a problem as we need all these pieces to coexist.
we can add an additional pair of switches to accommodate this if needed.
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today

From novice to tech pro — start learning today.