1 / 7

Directory Assisted TRILL Encapsulation on non-TRILL nodes (Directory Reliant Smart End Node)

Directory Assisted TRILL Encapsulation on non-TRILL nodes (Directory Reliant Smart End Node). Linda Dunbar Donald Eastlake Radia Perlman Igor Gashinsky. History. 2011: stripped from “ draft- dunbar -trill-directory-assisted-edge ” March 2013:

nen
Download Presentation

Directory Assisted TRILL Encapsulation on non-TRILL nodes (Directory Reliant Smart End Node)

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Directory Assisted TRILL Encapsulation on non-TRILL nodes(Directory Reliant Smart End Node) Linda Dunbar Donald Eastlake Radia Perlman Igor Gashinsky

  2. History • 2011: stripped from “draft-dunbar-trill-directory-assisted-edge” • March 2013: • revised to reflect progress made by “draft-ietf-trill-directory-framework” and “draft-dunbar-trill-scheme-for-directory-assist”

  3. Motivation • Reduce the amount of MAC&VLAN <-> RBridgeEdge mapping maintained by RBridge edge. • ToR with 40 servers: 40*20VMs=800 hosts, Worst case: 800 VLANs 800 *200 (hosts/VLAN) = 160000 entries • Allow all ports connected to a Bridged LAN to forward TRILL traffic • Today: Unknown DA frames are flooded to both TRILL domain and Ethernet domain TRILL Campus Virtual Switch

  4. Detailed Mechanism • All hosts under RBridge use RBridge’s nickname • Ingress RBridge: forward TRILL encapsulated frames to TRILL campus. Native Ethernet frames stay locally (or pull directory for unknown DA) • Egress RBridge: normal processing TRILL campus vSwitch gets mapping from Directory Service DA = Egress RBridge (Pseudo node) SA = IngreessRBridge

  5. Local Decision • Directory: • End node attached to {R1, R2, R3, R4} TRILL Campus Choose any of directly attached Edge RBridge as Ingress SA (local decision, same as ECMP)

  6. Benefits • Simplified processing on Ingress RBridge • Utilize directory service on virtual switches • No change to edge RBridge processing • Allow all ports to forward TRILL frames (i.e. no need to designate one port as AF port)

  7. Next Step • Need more comments from WG • WG adoption?

More Related