Wired Intelligent Edge

Please advise on best programing and feasible solution to create an always on, non-loop, 
and redundant / load balancing solution, between the three datacenters, on layer 2. (preferably)

It will flow data back and forth between, DC A & B, likewise A & C. (and B & C)

Between B & C is optional in normal situation, but it is to be in case of "link loss/trafic stop".
Either at one of the datacenters.

•    To goal is to keep traffic flow at any time, not to block anything.

It is in a carrier MPLS network, so the lines are in two (or more) parts,  
meaning it may not be a link loss, if lines breaks between carriers MPLS switches.

(meaning traffic stops, and no link loss at transceivers on either sides)

There are multiple VLANS, (same), on all DC's, and the 3810 at DC B & C is back stacked

(one virtual switch); at DC A, a two way DT stack is in place (physikal 2 switches)

anyone ?

You could try switch meshing - one of the few proprietary protocols that goes back to ProCurve days. I am a bit doubtful it will work over the link types that you have - you probably need dark fibre.

• Switch meshing is a load-balancing technology that enhances reliability and performance in these ways:
  Provides significantly better bandwidth utilization than either Spanning Tree Protocol (MSTP) or standard port trunking.
• Uses redundant links that remain open to carry traffic, removing any single point of failure for disabling the network, and allowing quick responses to individual link failures. This also helps to maximize investments in ports and cabling.
• Unlike trunked ports, the ports in a switch mesh can be of different types and speeds (10 and 100 Mbps, gigabit, and 10 gigabit). For example, a 10Base-FL port and a 1GB port can be included in the same switch mesh.

See the manual: Aruba 3810 / 5400R Advanced Traffic Management Guide for AOS-S 16.11

Please advise on best programing and feasible solution to create an always on, non-loop, 
and redundant / load balancing solution, between the three datacenters, on layer 2. (preferably)

It will flow data back and forth between, DC A & B, likewise A & C. (and B & C)

Between B & C is optional in normal situation, but it is to be in case of "link loss/trafic stop".
Either at one of the datacenters.

•    To goal is to keep traffic flow at any time, not to block anything.

It is in a carrier MPLS network, so the lines are in two (or more) parts,  
meaning it may not be a link loss, if lines breaks between carriers MPLS switches.

(meaning traffic stops, and no link loss at transceivers on either sides)

There are multiple VLANS, (same), on all DC's, and the 3810 at DC B & C is back stacked

(one virtual switch); at DC A, a two way DT stack is in place (physikal 2 switches)

anyone ?

You could try switch meshing - one of the few proprietary protocols that goes back to ProCurve days. I am a bit doubtful it will work over the link types that you have - you probably need dark fibre.

• Switch meshing is a load-balancing technology that enhances reliability and performance in these ways:
  Provides significantly better bandwidth utilization than either Spanning Tree Protocol (MSTP) or standard port trunking.
• Uses redundant links that remain open to carry traffic, removing any single point of failure for disabling the network, and allowing quick responses to individual link failures. This also helps to maximize investments in ports and cabling.
• Unlike trunked ports, the ports in a switch mesh can be of different types and speeds (10 and 100 Mbps, gigabit, and 10 gigabit). For example, a 10Base-FL port and a 1GB port can be included in the same switch mesh.

See the manual: Aruba 3810 / 5400R Advanced Traffic Management Guide for AOS-S 16.11

Please advise on best programing and feasible solution to create an always on, non-loop, 
and redundant / load balancing solution, between the three datacenters, on layer 2. (preferably)

It will flow data back and forth between, DC A & B, likewise A & C. (and B & C)

Between B & C is optional in normal situation, but it is to be in case of "link loss/trafic stop".
Either at one of the datacenters.

•    To goal is to keep traffic flow at any time, not to block anything.

It is in a carrier MPLS network, so the lines are in two (or more) parts,  
meaning it may not be a link loss, if lines breaks between carriers MPLS switches.

(meaning traffic stops, and no link loss at transceivers on either sides)

There are multiple VLANS, (same), on all DC's, and the 3810 at DC B & C is back stacked

(one virtual switch); at DC A, a two way DT stack is in place (physikal 2 switches)

anyone ?

So this is all, one command ! :)

in all three switches...

Magic..

You could try switch meshing - one of the few proprietary protocols that goes back to ProCurve days. I am a bit doubtful it will work over the link types that you have - you probably need dark fibre.

• Switch meshing is a load-balancing technology that enhances reliability and performance in these ways:
  Provides significantly better bandwidth utilization than either Spanning Tree Protocol (MSTP) or standard port trunking.
• Uses redundant links that remain open to carry traffic, removing any single point of failure for disabling the network, and allowing quick responses to individual link failures. This also helps to maximize investments in ports and cabling.
• Unlike trunked ports, the ports in a switch mesh can be of different types and speeds (10 and 100 Mbps, gigabit, and 10 gigabit). For example, a 10Base-FL port and a 1GB port can be included in the same switch mesh.

See the manual: Aruba 3810 / 5400R Advanced Traffic Management Guide for AOS-S 16.11

Please advise on best programing and feasible solution to create an always on, non-loop, 
and redundant / load balancing solution, between the three datacenters, on layer 2. (preferably)

It will flow data back and forth between, DC A & B, likewise A & C. (and B & C)

Between B & C is optional in normal situation, but it is to be in case of "link loss/trafic stop".
Either at one of the datacenters.

•    To goal is to keep traffic flow at any time, not to block anything.

It is in a carrier MPLS network, so the lines are in two (or more) parts,  
meaning it may not be a link loss, if lines breaks between carriers MPLS switches.

(meaning traffic stops, and no link loss at transceivers on either sides)

There are multiple VLANS, (same), on all DC's, and the 3810 at DC B & C is back stacked

(one virtual switch); at DC A, a two way DT stack is in place (physikal 2 switches)

anyone ?