1 / 6

Link Aggregation sublayer block diagram with DAS

Link Aggregation sublayer block diagram with DAS. Ting Ao (ao.ting@zte.com.cn). Proposal in July meeting. http://www.ieee802.org/1/files/public/docs2011/ axbq-tinga-link-aggregation-sublayer-0711-v00.pptx. Service Gateway. Action: Is configured by Gateway selection.

wendi
Download Presentation

Link Aggregation sublayer block diagram with DAS

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. Link Aggregation sublayer block diagram with DAS Ting Ao (ao.ting@zte.com.cn)

  2. Proposal in July meeting • http://www.ieee802.org/1/files/public/docs2011/axbq-tinga-link-aggregation-sublayer-0711-v00.pptx

  3. Service Gateway • Action: • Is configured by Gateway selection. • Check the frames into/out of my network. • Judge whether the frame belong to this device. • With this function entity, so that: • Make the function entities in DAS sublayer clearer and more understandable without importing complexity. • Leave the Frame Collector and Dstributorunchanged AFAP. • In 802.1AX, Frame collector is forbidden to transmit frame to Frame distributor. The rule should not be violated in DRNI. • Only Service Gateway need to know to which Intra-das link the frame transmitted.

  4. Virutal Aggregator Multiplexer • Action: • Is created according to the aggregated links information from other nodes by DLIC. • Forward the traffic to other node in the same portal • Purpose: • For every device in the portal, their aggregator looks like to be same. It’s also a consistent with the Figure 7-2 in D0.3 • Distributor can see all the aggregation links, so that link selection negotiation is getting easier. • We should not aggregate the Intra-das link into DLAG directly.

  5. DLAG Internal Coordination • Separate from LACP entity as a new function entity. • Reason: • Information need to coordinate is different with LACP’s • We can’t aggregate the intra-das link into DLAG. Otherwise, may need to change the LACP a lot? • LACP in DRNI is network to network, while DLIC in Portal is within my network. • LACPDU is transmitted on every aggregated links, while DLICPDU is transmitted only on Intra-das link.

  6. Thanks!

More Related