portland: a scalable fault- tolerant layer 2 data center network fabric b97703099 財金三...
Post on 15-Dec-2015
224 Views
Preview:
TRANSCRIPT
3
Introduction
• LAN insufficiency • Requirement Network in datacenter :– VM Migration without IP change– Needn’t config switch before deployment– Host in datacenter efficiently communicate– No forwarding loop– Fault-tolerant and recovery
4
Introduction• Layer 2 kind fabric– Layer 3 not workable• VM migration with IP change• Config switches of subnet and DHCP synchronite
• TTL method: prevent forwarding loop• Prevent routing broadcast
5
Background:DatacenterNetwork• Topology• Forwarding– Layer 3 : IP assigned hierachically• Broadcast (Failure avoidance, overhead )• Config switch subnet & DHCP syncro. Fault• VM migration unable
– Layer 2 : MAC• Single spanning tree problem (not shortest way)• Broadcast entire fabric
– VLAN : • Source pre-assignment (decrease flex. & scal.)• Switch need to maintain VLAN’s state
6
• End host Virtualization– Layer 3 setting : not work– ARP to solute ?
Background:DatacenterNetwork
7
Fat Tree Network
• Multi-rooted• Stage : edge, aggregation, core• K-port swithes:– k3/4 end hosts– 5k2/4 individual k-port switches– k individual pods– each pod : k2/4 hosts
9
Design : Fabric Manager
• Centralized Manager• Fuction :– Mantain soft state network config (ex.topology)– Responsible for • ARP resolution• Fault tolerance• Multi-cast
• Only soft state (no hard state, ex.#of switch)
10
Design : Pseudo MAC
• Assigned to end hosts• Information include:– Location : same pod, same prefix– Pod number→ position numer
• End host with their own AMAC• LDP (location discovery protocol)– employed to assign– Pod.position.port.vmid
12
Design : Proxy-based ARP
• Ethernet : B-cast to all host(same layer2)• Used for communication in datacenter• If FM not available for IP-PMAC mapping
→bcat to core(O(k) state )• VM migration supporting– FM sending invalidation message to old pos.– If contact with this message
→ new PMAC address in the host’s cache
14
Design : Distributed Location Discovery
• Location Discovery Protocol (LDP)• No administative config (no manul set)• Location Discovery Message:– Sent by switches– Several information – Edge got from aggregation, learned
→Aggregation learned →Core learned
15
Design : Distributed Location Discovery
• Location Discovery Message:– Position number acquisition:• Randomly chosen number• Verified by aggregation
– Pod number acquisition:• FM assignment to aggregation
– Exception : non-existence• LDM not correct• Disable suspicious port
17
Design : Fault Tolerance
• Unicast Fault Detection and Action• Multicast Fault Detection and Action
top related