1 / 9

Softwire Mesh MIB draft-cui-softwire-mesh-mib-04

Softwire Mesh MIB draft-cui-softwire-mesh-mib-04. Peng Wu, Tsinghua Univ. IETF 83, Paris. Background. The WG publishes RFC5565 for Softwire Mesh CNGI deployment in China China’s Next Generation Internet 4-over-6 mesh in CERNET2 100 PE routers support softwire mesh AFBR functions

loman
Télécharger la présentation

Softwire Mesh MIB draft-cui-softwire-mesh-mib-04

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. Softwire Mesh MIBdraft-cui-softwire-mesh-mib-04 Peng Wu, Tsinghua Univ. IETF 83, Paris

  2. Background • The WG publishes RFC5565 for Softwire Mesh • CNGI deployment in China • China’s Next Generation Internet • 4-over-6 mesh in CERNET2 • 100 PE routers support softwire mesh AFBR functions • Vendor support on AFBR • Management requirements • Status monitoring, traffic statistics, tunnel management, etc. • Softwire Mesh MIB for RFC5565

  3. Relationship with Other MIBs • Leverage IP Tunnel MIB(RFC4087) • IP Tunnel MIB includes common tunnel objects • Further objects required by Softwire Mesh • Supported tunnel types of the AFBR • Encapsulation table • Leverage BGP MIB(RFC4273) • Softwire Mesh leverages extended MP-BGP • BGP MIB is adopted as well • Further objects required by Softwire Mesh • List of BGP neighbors which runs Softwire Mesh • Encapsulation method negotiated with these neighbors

  4. Softwire mesh MIB structure • swmMIB ::= {transmission xxx} • swmTunnelTypeTable ::= {swmMIB 1} • swmEncapTable ::= {swmMIB 2} • swmBGPNeighborInfo ::= {swmMIB 3} • swmMIBConformance ::= {swmMIB 4}

  5. swmTunnelTypeTable::= {swmMIB 1} • Softwire Mesh Tunnel Type Table • Encapsulation methods which An AFBR supports • Indexed by ifIndex & swmTunnelType • RFC5565 encapsulation method set: {IP-IP, GRE, L2TPv3 (RFC5512), IPsec(RFC5566)}

  6. swmEncapTable::= {swmMIB 2} • Softwire Mesh Encapsulation Table • Encapsulation rule: (E-IP prefix, I-IP dstaddr) binding • Cover both IPv4-over-IPv6 and IPv6-over-IPv4 • Indexed by ifIndex & swmEncapsEIPDst & swmEncapsEIPMask An IPv4-over-IPv6 example

  7. swmBGPNeighborInfo::= {swmMIB 3} • Softwire Mesh BGP Neighbor Information • Neighbor I-IP address • Encapsulation method(s) negotiated between AFBR and the neighbor • Indexed by ifIndex & swmBGPNeighborAddress 4over6 BGP neighbor info example

  8. Next step • This document is in the Softwire Milestone • Nov 2011 Adopt Mesh topology MIB module document as a Working Group document • Nov 2012 Submit Mesh topology MIB module document for Proposed Standard • We’ve addressed the issues raised in past meetings and mailing list • The MIB structure & content are quite clear now • So, request for WG adoption?

  9. Backup slidesManagement requirements • Technical requirements • Monitor the status of PEs’ mesh functions • When broken, analyze information like BGP connectivity, NLRI-NH to find what & where is the problem • Collect each PE’s traffic information, find the bottleneck, etc. • Manage a large number of PEs • Produced by different vendors • Managed by different campus networks • Unified management is indeed necessary

More Related