Docstoc

Bridge Port Extension using PBB TE using PBB-TE

Document Sample
Bridge Port Extension using PBB TE using PBB-TE Powered By Docstoc
					Bridge Port Extension
      PBB-TE
using PBB TE
Paul Bottorff
Ben Mack-Crane
David Martin
Panagiotis Saltsidis


   See contribution bh-bottorff-pbbte-pe-draft-0711-v1 for further details
 Comparison between
    E-TAG d PBB-TE Port E   d
    E TAG and PBB TE P Extenders
                                                        E-TAG PEs   PBB-TE PEs
Scalability
Failure detection and status reporting
EVB synergy
Compatibility with existing 802.1Q Bridge relay
No new components
N new t
No    tags
Optional support for CFM, protection and multipathing
Optional support for congestion notification
Optional support for ETS and PFC
Optional support for EVB & VEPA
Lowest overhead octets


 2    7/14/2011   Bridge Port Extension Using PBB-TE
Extended Bridge built from BEBs
                Controlling Bridge
                C t lli B id                           Extended Bridge                      BEB (Port Extender)
              T-Comps                                                                                                          ES
                               CB BEB                        BEB (Port Extender)            B-Comp

          C-VLAN                                                                                                               ES
                                         B-Comp
          Aware                                              B-Comp
           Comp                                                                             BEB (Port Extender)     EP Leafs
                                                                                            B-Comp
                                                                                                                               ES
                                                                       T-Comps C-Comps

                                                                                                                               ES
                                                                                             CBPs    PIP
                                                                                                     PIPs    VIPs
                                                             BEB (Port Extender) EP Leafs
                                                             B-Comp
                                                                                                                               ES
                                                                                                                               ES
                                             p
                                        B-Comp

                                                         CBPs         PIPs   VIPs
                                                                                                                               ES
               EP Roots VIPs PIPs CBPs                       Cascade Port           Upstream Port      Extended Port

•                     g      g        p                         p                 p
    The EVB Controlling Bridge is composed of a BEB with a B-component and a T-component
    per VIP coupled to the primary C-VLAN aware component (or S-VLAN aware component)
     − Each Cascade Port is just an exterior facing PNP of the BEB
     − The VIP’s of the CB-BEB are modified to form the B-DA and B-SA based on information passed from the C-Component
•                               p          primary B-component and a T-component p EP
    A Port Extender is a BEB composed of a p     y      p                 p      per
     − The VIPs of the Port Extender BEBs use standard T-Components
     − An optional 2-Port C-Comp on each leaf Extended Port is used for C-TAG manipulations

3     7/14/2011         Bridge Port Extension Using PBB-TE
Port Extender PBBN
                                                                                          BEB (Port Extender)
            T-Comps           CB BEB                       BEB (Port Extender)            B-Comp

                                       B-Comp

                                                           B-Comp
                                                                                          BEB (Port Extender)     EP Leafs
                                                                                          B-Comp

                                                                     T-Comps


                                                                                           CBPs    PIPs
                                                                                                   PIP     VIPs
                                                           BEB (Port Extender) EP Leafs
                                                           B-Comp




                                            p
                                       B-Comp

                                                       CBPs         PIPs   VIPs

             EP Roots VIPs PIPs CBPs                       Cascade Port           Upstream Port      Extended Port



  The
• Th    P tE t d                t f th Controlling
        Port Extender components of the C t lli
    Bridge along with the external Port Extenders
    make a complete PBBN which can support PBB-TE
      a e co p e e       N w c ca suppo
    forwarding
4    7/14/2011        Bridge Port Extension Using PBB-TE
What is the same as PBB/PBB-TE?
                                 Controlling Bridge             d d d
                                                           Extended Bridge                  Port Extender
                                                                                                      d

                                              CB BEB                                                                ES
                                                                  Port Extender
                           C-VLAN                                                                                   ES
                           Aware
                            Comp                                                            Port Extender

                                                                                                                    ES

                                                                                                                    ES
                                                                  Port Extender

                                                                                                                    ES
                                                                                                                    ES


                                                                                                                    ES
                                                                Cascade Port      Upstream Port     Extended Port



•   Just an application of PBB-TE with a limited topology and component organization,
    therefore the Controlling B id and P t E t d can b PBB/PBB TE with Extended
    th f      th C t lli Bridge d Port Extender             be PBB/PBB-TE, ith E t d d
    Bridge feature additions.
     − Each leaf EP is connected to a CB-BEB VIP with a point-to-point TESI
     − Each UP is connected to a CB-BEB VIP with a point-to-point TESI
             replication gro p”                               CB BEB           point-to-multipoint
     − Each “replication group or EP set is connected from a CB-BEB VIP with a point to m ltipoint ESP
•   The Controlling Bridge’s primary component is modified as in 802.1Qbh
•   The Port Extenders forward along configured TESIs
     − Each EP is attached to single VIP and PIP on a T-Comp
     − The PIP associated with an EP is identified by a unique B-MAC , which may be constructed using the E-PID



5    7/14/2011        Bridge Port Extension Using PBB-TE
What is different from PBB/PBB-TE?
                                        Controlling Bridge        Extended Bridge                  Port Extender

                                                     CB BEB                                                                ES
                                                                         Port Extender
                                  C-VLAN                                                                                   ES
                                  Aware
                                   Comp                                                            Port Extender

                                                                                                                           ES

                                                                                                                           ES
                                                                         Port Extender

                                                                                                                           ES
                                                                                                                           ES


                                                                                                                           ES
                                                                       Cascade Port      Upstream Port     Extended Port

•   The forwarding state for the CB-BEB and Port Extenders is configured using the Port Extender Control
    and Status Protocol
•                 p          y              q     primitive for each frame to be forwarded via the PE
    The C-VLAN component relay issues one request p
     −    The connection_identifier parameter carries a port map indicating the ports associated with EPs to which the frame should be forwarded
     −    If the related indication primitive was received from the PE the request primitive is sent on the port from which the indication was received
     −    If the related indication was not received from the PE, the request is sent on one of the ports indicated in the connection_identifier
•   The CB-BEB PIPs assign B-MAC addresses selecting the ESP for each primitive according to modified
    rules for Port Extension
     −    For “remote replication groups” the PIP selects a B-DA (E-PID) identifying a point-to-multipoint TESI (as currently in Qbh)
     −    If the PIP’s corresponding EP is not in the connection_identifier port map, the frame is marked for echo cancellation
•   Echo cancellation is performed at the PIP associated with an EP, whenever the B-SA is equal to the
    corresponding root EP’s CB-BEB echo cancellation B-MAC
     −    Subclause paragraph 6.10.1f) is extended to provide a parameter for the B-SA which is cancelled. This parameter is set to the
          associated root EP


6        7/14/2011           Bridge Port Extension Using PBB-TE
802.1Qbh/BR Leverage

• Port Extender Control and Status Protocol from
               h      h            d      h
  802.1BR with perhaps some modest changes in the    h
  E-PID field definitions
  The          d bj t t i
• Th managed object extensions f       the Controlling
                                   for th C t lli
  Bridge MIB
               extension
• The PE LLDP e tension TLVs for the Controlling
  Bridge and Port Extender




7   7/14/2011   Bridge Port Extension Using PBB-TE
PBB Encoding Transform from E-TAG
                     MACs
                     MAC                                                      E TAG
                                                                              E-TAG
                 1                13      15                 16            17             18              19         20
    PE
E-Tagged




                                         E-PCP
                                                 E-DEI
                 C-DA     C-SA     ET                    Ingress_E-PID                  E-PID                     Reserved




                                                                          Res
  Frame
                                        8 65                             1 87 6                       1




                                   B-MACs                                       B-TAG                             I-TAG
                 1                               7                       13     15       16      17       19               23
    PE
I-Tagged




                                                                                B-PCP
                                                                                B-DEI




                                                                                                          I-PCP
                          B-DA                            B-SA            ET                      ET               I-SID     C-DA   C-SA




                                                                                                          I-DEI
                                                                                        B-VID




                                                                                                            Res
  Frame
  F
                                         18                          1 8 18 65                  1 8 18 6
                                                                                                1



•   The Ingress PE Port is identified by the B-SA rather than an Ingress_E-
    PID,                                                                 B-
    PID while the PE Destination (group or unicast) is identified by the B
    DA rather than an E-PID.
•   The E-PCP and E-DEI are carried in I-PCP, I-DEI.
•   The I-SID is t    df            li ti
    Th I SID i not used for a PE application.

8    7/14/2011       Bridge Port Extension Using PBB-TE
Controlling Bridge Baggy Pants Diagram
                      C-Comp                              T-Comp                         B-Comp
                           MC &VLAN                             D-Relay
                             Relay
                                                                                    Virtual
                                                                                   Instance
                   Clause
                  8.5,6.9,
                                  Clause
                                 8.5,6.9,
                                                                       Clause
                                                                        6.10,        Port
                    9.5a           9.5a                               9.5c, 8.5

                     ISS              ISS                                   ISS
                                                                                             S-VLAN
                                                                                              Relay
                                                                                     Clause              Clause
                   Clause        Clause                Clause             Clause     6.11, 8.5
                                                                                     6 11 8 5          8.5,6.9,
                                                                                                       8569
                     6.7          6.14                  6.14,              6.14,     9.5c, 9.5b            9.5b
    C-VLAN                                               8.5                8.5          ISS            ISS

    Bridge
                                                                                       Clause
                                                                                      6.14, 8.5
                                                                                                      Clause
                                                                                                        6.7
                                                                                                                  Cascade
      Port                                                                                                          Port

                               C-VLAN                Root   Provider               Customer
                               Bridge              Extended Instance               Backbone
                                 Port                 Port    Port                   Port


•   No new relays, components, ports, or tags
•   Yellow indicates subclauses requiring feature additions, other
      b l               difi d
    subclauses are unmodified

9     7/14/2011   Bridge Port Extension Using PBB-TE
Port Extender Baggy Pants Diagram
                        B-Comp                               T Comp
                                                             T-Comp                    (2-Port C-Comp)
                                                                                       (2 Port C Comp)
                                                                  D-Relay                          VLAN
                                                                                                   Relay



                                                         Clause                          Clause             Clause
                                                          6.10,                         8.5,6.9,           8.5,6.9,
                                                        9.5c, 8.5                         9.5a               9.5a
                                                          ISS                             ISS                ISS
                             S-VLAN
                              Relay
                  Clause              Clause
                  8.5,6.9,         6.11, 8.5             Clause             Clause      Clause             Clause
                  9.5b            9 5c 9.5b
                                  9.5c, 9 5b              6.14,
                                                          6. ,               6.14,,      6.
                                                                                         6.14                6.7
                      ISS            ISS                   8.5                8.5
                    Clause         Clause
                       6.7        6.14, 8.5
Uplink                                                                                                                  Leaf
 Port                                                                                                                 Extended
                               Customer                Provider               Leaf     C-VLAN
                                                                                       C VLAN                            Port
                               Backbone                Instance             Extended   Bridge
                                 Port                    Port                  Port      Port

•    U   difi d         t form th PE relay
     Unmodified components f   the     l
•    One “real” filtering database at the B-Comp
•         p                   p                 gg g      gg g
     The optional 2-Port C-component allows C-tagging/untagging
•    The control plane is replaced with the PE CSP
10    7/14/2011   Bridge Port Extension Using PBB-TE
   Extended Bridge component peering

           C-Comp              T-Comp                B-Comp                     B-Comp             T-Comp      (2-Port C-Comp)


           ISS       ISS                                                                                          ISS     ISS




                                       ISS                                                        ISS




C-VLAN                                                                                                                             Leaff
Bridge                                               ISS        ISS             ISS      ISS                                     Extended
  Port                                                                 Uplink                                                       Port
                                                                        Port

                 C-VLAN      Root   Provider Customer                                 Customer Provider Leaf C-VLAN
                 Bridge    Extended Instance Backbone                 Cascade         Backbone Instance Extended Bridge
                   Port       Port    Port     Port                     Port            Port     Port      Port    Port




   •    VIPs in T-Components terminate Backbone Service Instance over Port
        Extender network
   •                              g     g
        C-Components in Controlling Bridge and Port Extender terminate port
        extensions

   11    7/14/2011         Bridge Port Extension Using PBB-TE
Extended Bridge BSIs
    Backbone Service Instances
              Controlling Bridge                        Extended Bridge                        BEB (Port Extender)
            T-Comps                                                                                                         ES
                             CB BEB                            BEB (Port Extender)             B-Comp

         C-VLAN                                                                                                             ES
                                          B-Comp
                                          BC
         Aware                                                 B-Comp
          Comp                                                                                 BEB (Port Extender)
                                                                                               B-Comp
                                                                                                                                ES
                                                                         T-Comps C-Comps

                                                                                                                                ES
                                                                                               CBPs     PIPs    VIPs EP Leafs
                                                               BEB (Port Extender)
                                                               B-Comp
                                                                                                                                ES
                                                                                                                                ES
                                          B-Comp

                                                             CBPs       PIPs   VIPs EP Leafs
                                                                                                                                ES
                 EP Roots VIPs PIPs CBPs                       Cascade Port           p
                                                                                     Upstream Port        Extended Port


• All the VIPs of a connected PE “tree” are members of the same Backbone
  Service Instance (BSI) and therefore use the same I-SID value.
                                            trees                           I SID
• In the example above we have two PE “trees” and each with a different I-SID
  value indicated by the yellow and pink marks
• Note that a VIP for BSI termination exists above the Uplink Port LLC layer
12   7/14/2011          Bridge Port Extension Using PBB-TE
Extended Bridge TESIs
    Traffic Engineered Service Instances
              g
                Controlling Bridge                     Extended Bridge                    BEB (Port Extender)
              T-Comps                                                                                                ES
                               CB BEB                       BEB (Port Extender)           B-Comp

           C-VLAN                                                                                                    ES
           Aware                                            B-Comp
            Comp                                                                          BEB (Port Extender)
                                                                                          B-Comp
                                                                                                                     ES

                                                                                                                     ES
                                         B-Comp
                                                            BEB (Port Extender)
                                                            B-Comp
                                                                                                                     ES
                                                                                                                     ES
                                         B-Comp


                                                                                                                     ES
                                                            Cascade Port           p
                                                                                  Upstream Port      Extended Port

•    Tan lines in the diagram show the attachments of point-to-point TESIs
•    One pt-pt TESI couples a Root EP’s VIP to the Uplink Port’s LLC on each Port Extender
•        p                                    pt-mpt
     Purple lines indicate the attachments of p p TESIs within the Port Extender “trees”
•    Though a single pt-mpt TESI attaching a Root EP’s VIP to all Leaf EPs VIPs of the PE “tree”
     is shown, additional pt-mpt TESIs attaching to limited groups of Leaf EPs are possible
13     7/14/2011       Bridge Port Extension Using PBB-TE
Port Extension B-VIDs
                   Path Selection
• Without  redundant links the Port Extender can use
        l default
  a single d f l B-VID
• By using multiple B-VIDs to engineer alternate ESPs
        ld b       ibl to        t t d d features
  it would be possible t support extended f t
     − The B-VID can be used to enhance the Port Extenders
       with protection support
     − The B-VID can be used to enhance the Port Extenders
       with multi-pathing support




14   7/14/2011   Bridge Port Extension Using PBB-TE
Frame forwarding from Leaf EP
                     Controlling Bridge

               C-VLAN               CB BEB                                 PE BEB
                                                                  B-Comp
                aware                                                                                   C             ES
                                             B-Comp
                                             BC
                comp
                                                                                                        C             ES
    C                                        B-Comp

                                                                                                            DA   SA   C-TAG


                                                                B-DA   B-SA   I-TAG   DA   SA   C-TAG             1
                DA    SA   C-TAG         3                                     2
•    Before frame transmission the PIP of the T-component is programmed using PE CSP with:
        −   It’s          l f    dd           t t df     the E-PID
            It’ SA as a leaf EP address constructed from th E PID
        −   It’s Default Backbone Destination parameter set to a root EP address constructed from the E-PID
        −   The enableConnectionIdentifier parameter is set to FALSE
        −   The I-SID parameter is set to default value
1 A frame is transmitted from the ES attached to an Extended Port with DA/SA/C TAG
•                                                                       DA/SA/C-TAG
2 The frame is received at a leaf PE of a T-component within the Port Extender who delivers
•
  it over the VIP-ISS to the PIP. The PIP builds a frame with B-DA = root EP and B-SA = leaf
  EP sending it to the CBP of the B-Comp who forwards it along the TESI
3 Th frame is d
• The f                      l d      h        f h T-component within the CB-BEB and
                de-encapsulated at the PIP of the T                h h CB BEB d
  delivered over the internal LAN to an internal port of the C-VLAN aware component

15      7/14/2011          Bridge Port Extension Using PBB-TE
 Frame forwarding from the root EP
                B DAs
     Individual B-DAs
                      Controlling Bridge

               C-VLAN                CB BEB                               PE BEB
                                                                 B-Comp
                aware                                                                                C                  S
                                                                                                                       ES
                                              B Comp
                                              B-Comp
                comp
                                                                                                     C                 ES
     C                                        B-Comp                                                      3
                                                                                                          SA   C-TAG
                                                            2
                                                                                                     DA
1
                                                          B-DA   B-SA     I-TAG    DA   SA   C-TAG
DA       SA   C-TAG




•                                                          p         programmed with:
      Before frame transmission the PIP of the CB-BEB T-component is p g
         − It’s SA as a root EP address constructed from the E-PID
         − It’s Default Backbone Destination parameter set to a leaf EP address constructed from the E-PID
         − The I-SID parameter is set to identify the PE “Tree”
1 A frame is sent from a C-Comp Port to a root EP of the CB-BEB with DA/SA/C-TAG
 •                            p                                        / /
2 The frame is received at a root EP of the T-component within the CB-BEB and delivered
 •
   over the VIP-ISS to the PIP. The PIP builds a frame with B-DA = leaf EP and B-SA = root EP
   sending it to the CBP of the B-Comp who forwards it along the TESI
                 de encapsulated                   T component
3 The frame is de-encapsulated at the PIP of a T-component of an EP and delivered to a
 •
   LAN

 16       7/14/2011         Bridge Port Extension Using PBB-TE
    Frame forwarding from the root EP
        Group B-DAs no Echo Cancellation
             p
                                Controlling Bridge
                                                                                                          DA   SA    C-TAG

                          C-VLAN               CB BEB                      PE BEB
                                                                           B-Comp                     3
                           aware                                                                                C                     ES
                                                        B-Comp
                           comp
                                                                                                                C                     ES
         C                                              B-Comp                                                           3
                                                                                                                         SA   C-TAG
                                                                      2
                                                                                                                    DA
 1
                                                                    B-DA
                                                                    B DA   B SA
                                                                           B-SA     I TAG
                                                                                    I-TAG   DA   SA   C TAG
                                                                                                      C-TAG
    DA           SA     C-TAG



•    Before frame transmission the PIP of the CB-BEB T-component is programmed:
         − Is programmed as in the Individual address case
         − The T-component supports passing a connection_identifier containing a destination port map
         − The PIP is modified to use the connection_identifier to select a B-DA using the destination port map
1 A frame is sent from a C-Comp Port to a root EP of the CB-BEB with DA/SA/C-TAG
•
             •        The frame was sent from outside the “replication group” and so the connection_identifier contains a destination port map
                        hi h includes the CB-BEB       d to forward th f
                      which i l d th CB BEB PIP used t f           d the frame (only a single request is sent t th “ li ti group”).
                                                                               ( l      i l         ti      t to the “replication    ”)
2 The frame is received at a root EP of the T-component within the CB-BEB and delivered to the
•
     PIP. The PIP builds a frame and sends it to the CBP of the B-Comp who forwards it along a TESI
             •        B-DA is selected based on the connection_identifier destination port map
             •        B SA = root EP B MAC without E h C
                      B-SA       t                              ll ti (since th source i outside th replication group)
                                      B-MAC ith t Echo Cancellation ( i        the        is t id the  li ti         )
3 The frame is replicated over the TESI and de-encapsulated at the PIPs of the T-components,
•
     delivered to the leaf EPs and then the attached LANs
     17          7/14/2011            Bridge Port Extension Using PBB-TE
    Frame forwarding from the root EP
        Group B-DAs with Echo Cancellation
             p
                                 Controlling Bridge
                                                                                                            DA     SA   C-TAG
                                                                             PE BEB
                          C-VLAN                 CB BEB
                                                                             B-Comp                     3
                           aware                                                                                    C                   ES
                                                          B-Comp
                           comp
                                                                                                                    C                   ES
         C                                                B-Comp                                        3
                                                                        2                                        Discarded Frame
    1
                                                                      B-DA   B-SA     I-TAG   DA   SA   C-TAG
    DA           SA     C-TAG
•    The PIP of the CB-BEB T-component is programmed:
         −       Is programmed as in the Individual address case
         −       The T-component supports passing a connection_identifier containing a destination port map
         −       The PIP is modified to use the connection_identifier to select a B-DA using the destination port map
         −       The    is  difi d to
                 Th PIP i modified t use th connection_identifier t select th B SA using b th th d ti ti port map and source port
                                         the      ti   id tifi to l t the B-SA i both the destination       t       d           t
− The PIP of all Leaf EPs are modified to filter out frames matching a B-SA filter parameter (6.10f)
         −       Each root EP has two B-MACs one echo cancelled and one not. The B-SA filter parameter of the each leaf EP PIP is set to the echo
                 cancelled B-MAC of it’s root EP
•                                   p                                        / /
        A frame is sent from a C-Comp Port to a root EP of the CB-BEB with DA/SA/C-TAG
1
             •        The frame was sent from within the “replication group” and so the connection_identifier contains a destination port map which
                      excludes the CB-BEB PIP used to forward the frame (only a single request is sent to the “replication group”).
•       The frame is received at a root EP of the T-component within the CB-BEB and delivered to the PIP. The PIP
2       builds a frame and sends it to the CBP of the B-Comp who forwards it along a TESI
             •        B DA is selected based on the connection identifier destination port map
                      B-DA                          connection_identifier
             •        B-SA = root EP B-MAC with Echo Cancellation of the source port from the connection_identifier (should be this root EP port)

3
•       The frame is de-encapsulated at the PIPs of the T-components of the PEs and delivered to the LANs which are
        not echo cancelled.
     18          7/14/2011              Bridge Port Extension Using PBB-TE
What needs to be specified

• Contribution bh-bottorff-pbbte-pe-draft-0711-v1.pdf
  provides a complete proposed draft (or course needs
  review)
• Move clause 8, 7.12-7.14 (PE CSP) of 802.1BR into a new
  802.1Qbh clause 45 using 7.12-7.14 as part of the
  protocol introduction.
• Port Extender can be defined by a new conformance
  subclause specifying a Port Extender as a specific type of
  BEB and including the PE CSP
  The C t lli B id            be defined i the
• Th Controlling Bridge can b d fi d using th current    t
  conformance statement from 802.1Qbh replacing the PE
  requirements with the requirements defining a CB-BEB


19   7/14/2011   Bridge Port Extension Using PBB-TE
Scaling: EtherSlam application with up
   16,666
to 16 666 Extended Ports per PE tree




• Each   100 GE Cascade Port may support up to
     16,666 Extended Ports at 6 Mbit each (100G/6M)
20    7/14/2011   Bridge Port Extension Using PBB-TE
16K EP load refinements




• In the data center each external frame typically would
  generate 10 DCN frames (10x expansion)
• However the aggregate throughput from the 6 Mbit DSL lines
    ill be           l  the li     t i i      total        t
  will b 1/100 or less th line rate giving a t t l aggregate
  bandwidth of 1 G rather than 100 G
                           g          g
• 16K VM interfaced through the single 100 GE link would then
  run at about 10% utilization giving headroom for bursting
21   7/14/2011   Bridge Port Extension Using PBB-TE
Scaling a PBB-TE Controlling Bridge
                                                        Controlling Bridge

                                                  C-VLAN                     B-Comp
                                                   Aware                                B-Comp

                          C-VLAN                   Comp
                          Aware                   4K Ports
                           Comp

                                                  C-VLAN                     B-Comp
                                                   Aware
                                                   Comp
                                                  4K Ports


                                                  C-VLAN                     B-Comp
                                                   Aware
                                                   Comp
                                                  4K Ports

                           C-Comp Complex                              CB-BEB Complex


•                               g     g        py         g
    To Scale a PBB-TE Controlling Bridge we simply add stages
•   E-channels can be identified by the pair <B-DA,B-SA>
     − Total number of filtering table entries per CB Cascade port is 2 x Number of Extended
       Ports + Number of Group Destinations
     − For example if we have 16K Extended Ports and 16K Group Addresses then we have 2
       x 16K + 16K = 36K filtering table entries
22    7/14/2011    Bridge Port Extension Using PBB-TE
PBB-TE filtering database allows the NIC
state table to be independent from the CB
                         Controlling Bridge                                                   NIC with Extended Ports
                   C-VLAN
                   C VLAN                      B-Comp
                                                                      BEB (Port Extender)        BEB (Port Extender)
                    Aware                                  B-Comp




                    Comp
      C-VLAN
      Aware
                   4K Ports
                                                                                                                              ES
       Comp
                                                                      B-Comp
                                                                                               B-Comp
                   C-VLAN
                    Aware
                                               B-Comp


                                                                                                                              ES
                    Comp
                      Ports
                   4K P




                   C-VLAN

                                                                                            Filtering tables here are sized
                                               B-Comp




                    Aware
                    Comp
                   4K Ports
                                                                                            for EPs and MCs supported
       C Comp Complex
       C-Comp                             CB BEB Complex
                                          CB-BEB
                                                                                            by th           t the
                                                                                            b the NIC not th CB

•    Filtering tables at the edges of the PE network need to be large enough
     to hold the E-channels actually passing through
•    For instance a NIC with 128 ports and 128 group requires 2*128 +
     128 = 384 filtering table entries (note if additional multicast sources
     pass through NIC then these also need filtering entries)
•    The NIC filter table size requirement is independent from the CB filter
     table size requirement
23     7/14/2011                 Bridge Port Extension Using PBB-TE
 PBB-TE PEs easily scale to 16K Extended Ports
        hil  i i i i     t t   d table i
      while minimizing state and t bl size
 •   PBB-TE PE uses existing filtering DB tables without any size increases
      − For Controlling Bridge10K-100K filtering entries are common and sufficient
          • For a CB-BEB supporting 16K Extended Ports we would need a total of 36K filtering entries
            providing:
                 − Source and Destination for each Extended Port
                 − 16K group addresses
          • Allows component cascading for Controlling Bridge port expansion
      − For Port Extenders we don’t need the as many filtering entries
          • In an adapter we need two entries for each Extended Port plus the number
            required for multicast
          • NIC filter table size is independent from CB filter table size
 •                                          E-TAG Ingress_E-CID
     Number of Extended Ports is limited by E TAG Ingress E CID and by
     the E-CID table size
      − Requires new tables for switches and chips
                              E-TAG
      − Changes in proposed E TAG size to support 16K Extended Ports
      − Both Port Extenders and Controlling Bridge must support full sized tables
24   7/14/2011        Bridge Port Extension Using PBB-TE
MSP: MAC operational propagation
both up and down from a break




•A   break between two port extenders should be
  reflected in MAC operational status at both the
  Controlling Bridge and Network Interface Port
  Extenders
• PE CSP has no connectivity to the station Port
  Extenders during a break and so can’t control the
               ti  l t t from th C t lli
  MAC operational status f     the Controlling
  Bridge
25   7/14/2011   Bridge Port Extension Using PBB-TE
One CC MEP pair per Port Extender
                                                                    MSS
           MSS
                 CC 1
                                                             CC 3
                                                      CC 2




• Here the break is detected by CFM using CC flows
  b         h          ll    d      d            d
  between the Controlling Bridge and Port Extenders
• Both the Controlling Bridge and all affected Port Extenders
  receive indications form CFM
• Once a break is detected by CFM the MSS on both ends
  can be used to set MAC_operational status on individual
    ff t d    t
  affected ports

26   7/14/2011   Bridge Port Extension Using PBB-TE
Mid-span failure detection and reporting
    solved using CFM and MSP
 • CFM           used to detect mid-span breaks to PEs
     − Required since we don’t have RSTP or SPB
     − Run CCs over the control E-channel to each Port Extender
           failure will b reported b h to the CB and to the Port
     − Any f l       ll be       d both      h      d    h
       Extender affected
                           mid span
     − The CB will see all mid-span failures
 • Each  Port Extender can set MAC enable based on
   the connectivity state to the CB
                  y
 • The MSP protocol co-ordinates MAC_operational
   state between each external Extended Port and
       h        l      d d
   each internal Extended Port
27   7/14/2011     Bridge Port Extension Using PBB-TE
PBB-TE PE and EVB synergy
    integrated Edge R l
    i t    t d Ed Relay




  PE-PBBN
• PE PBBN         d                               T
             provides transparent extension using T-
     components between an EVB Bridge and a 2-Port
     Edge Relay

28    7/14/2011   Bridge Port Extension Using PBB-TE
PBB-TE PE and EVB synergy
    S-channel
    S channel compatibility




•         PBB TE    B component       S VLAN
     Each PBB-TE PE B-component is an S-VLAN component
•    All S-VLANs are available except the one used for Port Extension
•    S-channel service couples the B-comps direct to C-VLAN comp and ER
•    C f            fS h      l         l          d        h
     Configuration of S-channels is easily automated using the existing LLDP
     exchanges
29     7/14/2011   Bridge Port Extension Using PBB-TE
     PE CSP for PBB-TE (a fringe benefit)

 • The  PE CSP protocol could be expanded as a
   control protocol for provisioning PBB-TE networks
 • To do this it would be desirable to expand PE CSP
   to support generalized TESID programming
                p                   y         protocol
 • This would provide broader utility for the p




30    7/14/2011   Bridge Port Extension Using PBB-TE
 Comparison between
    E-TAG d PBB-TE Port E   d
    E TAG and PBB TE P Extenders
                                                        E-TAG PEs   PBB-TE PEs
Scalability
Failure detection and status reporting
EVB synergy
Compatibility with existing 802.1Q Bridge relay
No new components
N new t
No    tags
Optional support for CFM, protection and multipathing
Optional support for congestion notification
Optional support for ETS and PFC
Optional support for EVB & VEPA
Lowest overhead octets


 31   7/14/2011   Bridge Port Extension Using PBB-TE
     BACKUP SLIDES


32   7/14/2011   Bridge Port Extension Using PBB-TE
Constructed B-MACs
                                  1                                4            5            6
       Individual B-MAC                                  OUI + I          Res(8 b)    E-PID (14 bits)




                                                                   Root
                                                                   Can
                                                                   87           7 6
                                  1                                4            5            6
       Group B-MAC
                                                         OUI + G    Res(10 bits)      E-PID (14 bits)
       Subclause 26.4
                                                                   8            7 6


•    Globally assigned B-MACs also could be used by simply increasing the E-PID size to a
     full TESI address.
•    C t t d i di id l B MAC use the R t indicator to diff
     Constructed individual B-MACs                                      ti t between th CB
                                          th Root i di t t differentiate b t          the CB-
     PIPs and the PE-PIPs
•    Constructed addresses use the Can indicator to differentiate frames which can be echo
     cancelled and those which can not
•    Constructed group B-MACs could use the Backbone Service Instance Group Address OUI
•    Since the Controlling Bridge is co-ordinating the selection of E-PIDs the assignments
     would be locally unique
•               B MACs don’t
     Since the B-MACs don t extend beyond a single PE mesh they would never interact with
     a general purpose system

33     7/14/2011    Bridge Port Extension Using PBB-TE

				
DOCUMENT INFO