IEEE 802.1ax – LACP: How to virtually tear down a DC using a Linux-Server

more than ten years later (IEEE 802.1ax-2008), but everybody calls it 802.3ad and serverguys still prefer static bonding with round-robin distribution [without telling network admins about that decision] to confuse (or tear down) ethernet-networks.

What a stupid default: default bond0 interface with balance round robin mode Awsome ūüôā

FWM-2-STM_LOOP_DETECT How a single server affects vMotion, SLB-VIP-Mobility, First-Hop Redundancy-Protocols (VRRP, HSRP you name it) in 2019.

I won’t expect technology like software-defined-networks to solve human ignorance.

Cisco HyperFlex Edge

  • 2/3/4-Node Cluster
  • no Fabric-Interconnects (FIs)
    • Edge-Servers connected to LAN-Switches
    • „back-to-Back“-Option for 2-Node Cluster
  • only „RF2“-redundancy

 

 

Cisco HyperFlex External Storage

Use-Case

Investment-Protection

VM-Migration

Fibre-Channel

 

Ethernet

iSCSI

FCoE

FC-Setup

VSAN

WWNN/WWPN-Pool

vHBA templates

FC-SAN Zoning / LUN-Masking

  • FC-Switch
  • Directly connected FC-Storage supported
    • zoning within UCS-FI

HyperFlex SAN Connectivity Policy

iSCSI Setup

VLAN

MAC-Pool/vNIC-Template(s)

HyperFlex LAN-Connectivity Policy