1 / 13

EVB Basic Architecture

EVB Basic Architecture. v5 February 18, 2010. EVB VSI Co-ordination Overview. Station Feature Database. Bridge Feature Database. Station. Link or Channel. Bridge. TLV. VSI Discovery. VSI Discovery. Dig. TLV. TLV. 1. 2. TLV. 3. Dig. Other TLV-based Feature.

tana-marshall
Download Presentation

EVB Basic Architecture

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. EVB Basic Architecture v5 February 18, 2010

  2. EVB VSI Co-ordination Overview Station Feature Database Bridge Feature Database Station Link or Channel Bridge TLV VSIDiscovery VSIDiscovery Dig. TLV TLV 1 2 TLV 3 Dig. OtherTLV-basedFeature OtherTLV-basedFeature TLV TLV Dig. TLV TLV T3PR TLV TLV Exchange digests to determine if the database contents need to be retransmitted to ensure consistency. Station FeatureDB Digests DB Changes Bridge FeatureDB Digests T3P T3P • Virtual Service Instance Discovery and Configuration Protocol (VDCP) co-ordinates network resources for Virtual Machines (VMs) • Feature Databases (FD) stores and updates active VSI (up to 1000s) • Database Synchronization Protocol (digest, DSP) provides guaranteed database synchronization between the station and bridge • Trivial TLV Transport Protocol (T3P) provides reliable delivery of TLVs between the station and bridge 2 3/2/2010 EVB Group EVB

  3. VSI Implementation • There is one state mahcine per VSI. The VSI D&C handles all VSI state transitions. It sends and exchanges signals with the DBA. • There is one VDBA per database. The VDBA handles all TLV updates, keeps running digest totals, filters duplicate TLVs, removes void TLVs, and maintains synchronization between the local and remote DBs. The DBA exchanges TLVs over T3P and exchanges signals or TLVs with the VDCM. • There is one T3P per channel. It provides reliable TLV delivery for TLVs which are placed in its reserved transmit and receive queues by the DBAs operating over the network. It also delivers TLVs to the appropriate DBA. Database Signals Other Feature VSI D&C (VDCM) Other Feature VSI Database Update Agent (VDBA) Other Database Update Agent (DBA) Other Database Update Agent (DBA) TLV Exchanges T3P T3P T3P EVB

  4. EVB Stack Architecture Sublayer Service Interfaces • T3P may be connected direct a LAN through a MAC, to a Channel, or to a VEB/VEPA internal bridge port • If MC is present then two levels of LLDP databases exist, one at the LAN and one at the Channel • All TLVs pass from T3P to DBA which control all updates to the TLV DB Optional MC (S-Comp) MAC/PHY AP(VM) ULPSS ULP DBs LLCSS ULP LLC ISS DBA T3PRSS T3PR LLDP LLDP Optional VEB/VEPA (C-Comp) LLCSS LLC Channel Level Remote LLDP DB LAN Level Remote LLDP DB LAN Level Local LLDP DB Channel Level Local LLDP DB LLC ISS LLC ISS EVB

  5. EVB Stack Architecture Sublayer Service Interfaces MAC/PHY ULP Optional MC (S-Comp) AP(VM) TLV DB LLCSS LLC T3PRSS Optional VEB/VEPA (C-Comp) LLCSS DBA LLC ISS LLDP T3P LAN Level Remote LLDP DB Channel Level Remote LLDP DB Channel Level Local LLDP DB LAN Level Local LLDP DB ISS • MAC: Media Access Control 802 2001 subclause 6.2.3 and 802.1Q Rev 2010 subclause 6.1 • ISS: Internal Sublayer Service 802.1Q Rev 2010 subclause 6.6 • LLC: Link Layer Control Protocol see 802 2001 subclause 6.2.2 and 802.2 ( note: see 802.1AB 2009 subclause 6.7 ) • LLCSS: Link Layer Control Protocol Sublayer Service 802.1AB-Rev 2009 subclause 6.7 • T3PR: Trivial TLV Transport Protocol new link layer protocol • T3PRSS: Trivial TLV Transport Protocol Sublayer Service new service interface for T3PR to ULP • S-Comp: S-VLAN Component 802.1Q Rev 2010 subclause 5.6 • C-Comp: C-VLAN Component 802.1Q Rev 2010 subclause 5.5 5 3/2/2010 EVB EVB

  6. Bridge “Baggy Pants” Model • Station uses a dual relay. The outside relay is an S-VLAN aware Component called an E-Comp. The inside relay is a C-VLAN Component with options for VEB or VEPA • Multichannel is implemented using the peered E-Comps. An LLDP database exists on each exterior facing leg of the E-Comp • The VEB or VEPA has an LLDP database on it’s exterior facing legs Bridge Station ISS ISS ISS ISS ISS ISS ISS ISS ISS ISS MS EISS EISS EISS EISS EISS EISS EISS EISS LLDP LLDP AP Control Protocols, EVB Cfg, MCh Cfg, VSI Cfg Control Protocols, EVB Cfg, MCh Cfg, VSI Cfg DBA T3P DBA T3P LLDP LLCSS LLC LLC DBA T3P LLC LLC MAC Relay MAC Relay LLDP DBA T3P LLC LLC LLC LLC LLC Clause 8.5,6.9, 9.5a Clause 8.5,6.9, 9.5a Clause 8.5,6.9, 9.5a Clause 8.5,6.9, 9.5a LLDP Clause 6.7 MAC Relay MAC Relay Clause 6.9, 6.20b Clause 6.9, 6.20b Clause 8.5,6.9, 9.5b Clause 8.5,6.9, 9.5b Clause 8.5,6.9, 9.5b Clause 8.5,6.9, 9.5b Clause 6.7 Clause 6.7 Clause 6.7 Clause 6.7 Clause 6.7 Clause 6.7 Clause 6.7 Clause 6.7 V-Comp E-Comp C-Comp E-Comp EVB

  7. Service interfaces for T3PSS • Parameters: • List of TLVs (7 bit ULP type, 9 bit length, tlv-list) • TLV list contains TLVs from a single ULP • Signals: None • Primatives: • T3P_UNITDATA.request (ulptype, ulptlv-list ) • T3P_UNITDATA.indicate (ulptype, ulptlv-list ) • Probably use same service interface for both T3PR and DBA since both could be TLV interfaces. EVB

  8. Multi-Channel Stack Architecture MAC/PHY ULP Optional MC (S-Comp) Sublayer Service Interfaces AP(VM) VDCSS VSI TLV DB LLCSS LLC DBA T3PSS LLDP T3P Optional VEB/VEPA (C-Comp) LAN Level Remote LLDP DB Channel Level Remote LLDP DB Channel Level Local LLDP DB LAN Level Local LLDP DB LLCSS LLC ISS ISS EVB

  9. Multi-Channel Components C S C C C C C C C EVB Station EVB Bridge • S-VLAN aware component used to implement MultiChannel • Disable spanning tree and MAC learning • Relationship between CNP and C-Comp Bridge Ports is 1-1 S-VLAN S-VLAN aware 5.6 C-VLAN aware 5.5 S-VLAN aware 5.6 C-VLAN aware 5.5 LAN C-VLAN aware 5.5 Provider Network Ports (PNP 6.13) Customer Network Ports (CNP 6.13) Customer Network Ports (CNP 6.13) Internal LANs Internal LANs EVB

  10. Thoughts on Naming? • LAN – the interface between station and bridge • S-TAG – the tag used to implement multichannel • E-Comp – a S-VLAN aware bridge component used to implement multichannel • E-VLAN – a channel, implemented as an S-VLAN • Edge Network Port (ENP) – a PNP used between a station and bridge to implement E-VLANs • Edge Edge Port (EEP) – a CNP used to terminate an E-VLAN in a station • Network Network Port (NNP) – a CNP used to terminate an E-VLAN in a bridge EVB

  11. Multi-Channel E-BridgeComponents C C C C C C C S C EVB Station EVB Bridge E-VLAN C-Comp E-Comp E-Comp C-Comp LAN C-Comp Edge Network Ports (ENP) same as PNP Network Network Ports (NNP) same as CNP Edge Edge Ports (EEP) same as CNP • EEP, ENP and NNP are same definitions as CNP and PNP • S-TAG remains unchanged and with same name • E-VLAN is an S-VLAN used as a channel • E-Comp is a new S-VLAN aware component profile (new 5.x clause) 11 3/2/2010 EVB EVB

  12. Summary • EVB Layer Model • S-Comp profile for Multichannel • VEB/VEPA bridges • T3P client of LLC (like LLDP) • TLV service interface between T3P, DBA, ULPs • Multichannel implementation • Each channel is a VLAN • A channel terminates at a CNP • The interface between Station and Bridge is a PNP EVB

  13. Backup Slides EVB

More Related