1 / 11

VLAN Mapping and TRILL

VLAN Mapping and TRILL. Radia Perlman Radia.Perlman@sun.com. Issue. Bridges currently do VLAN mapping. Issue. Bridges currently do VLAN mapping Intentionally, even. Why?. Merge two clouds VLAN “A” in one cloud means something different from VLAN “A” in another cloud

lore
Download Presentation

VLAN Mapping and TRILL

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. VLAN Mapping and TRILL Radia Perlman Radia.Perlman@sun.com

  2. Issue • Bridges currently do VLAN mapping

  3. Issue • Bridges currently do VLAN mapping • Intentionally, even

  4. Why? • Merge two clouds • VLAN “A” in one cloud means something different from VLAN “A” in another cloud • VLAN “A” in one cloud should be the same as VLAN “B” in the other cloud • Separate a community • (perhaps) make VLAN “A” into two communities (topology has to be cooperative)

  5. What we want • We want only RBridges connecting the two clouds to have any notion this is going on

  6. RB1 RB2 west east RB3

  7. Configure ports RB1 RB2 west east RB3

  8. RB1, RB2, and RB3 know: (East, VLAN A) = (West, VLAN B) RB1 RB2 west east RB3 When forwarding data between East and West, change the (inner) VLAN tag

  9. Other nits • ESADI about VLAN A endnodes tagged by using (inner) VLAN tag=A • So VLAN A ESADI turns into VLAN B ESADI as it is forwarded from East to West • To detect misconfiguration cut set RBridge MAY announce its mappings in its LSP

  10. Other nits, cont’d • If RB1 is configured to map (East, VLAN A) to (West, VLAN B), then RB1 MUST announce (in RB1’s LSP) that RB1 is attached to both VLAN A and VLAN B (regardless of whether RB1 is appointed forwarder for anything) • The reason for this is so that, e.g., multicast for VLAN A originating in West will get to RB1

  11. Multicast groups • RB1 MUST do one of the following: • Enumerate all (East, VLAN A) groups as being VLAN B groups attached to RB1 (in RB1’s LSP) • Announce that RB1 has an IPv4 and IPv6 multicast router in VLAN B attached to RB1 (in RB1’s LSP)

More Related