10
Softwire Mesh MIB draft-cui-softwire-mesh-mib-02 Jiang Dong Tsinghua University 2011.7 IETF 81, Quebec city

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

  • Upload
    iona

  • View
    89

  • Download
    0

Embed Size (px)

DESCRIPTION

Softwire Mesh MIB draft-cui-softwire-mesh-mib-02. Jiang Dong Tsinghua University 2011.7 IETF 81, Quebec city. Background. The WG completes RFC4925/ RFC5565 for softwire mesh Supported by vendors China’s Next Generation Internets: 4over6 mesh deployment in CERNET2 - PowerPoint PPT Presentation

Citation preview

Page 1: Softwire Mesh MIB draft-cui-softwire-mesh-mib-02

Softwire Mesh MIBdraft-cui-softwire-mesh-mib-02

Jiang DongTsinghua University

2011.7IETF 81, Quebec city

Page 2: Softwire Mesh MIB draft-cui-softwire-mesh-mib-02

Background

• The WG completes RFC4925/ RFC5565 for softwire mesh

• Supported by vendors• China’s Next Generation

Internets: 4over6 mesh deployment in CERNET2– A large number of PEs/client

networks– Management requirements

Page 3: Softwire Mesh MIB draft-cui-softwire-mesh-mib-02

Management requirement• 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

Page 4: Softwire Mesh MIB draft-cui-softwire-mesh-mib-02

• BGP MIB(RFC4273)– Softwire mesh BGP peers need to negotiate tunnel type

• Need softwire mesh BGP neighbor table

• IP Tunnel MIB(RFC4087)– The IP Tunnel MIB includes softwire mesh tunnel– Need a new tunnelIfEncapsMethod “softwireMesh”– tunnelIfRemoteInetAddress must be set to 0.0.0.0 or ::– tunnelIfAddressType shows address type of I-IP– Softwire mesh tunnel is a point to multi-point tunnel

• Need softwire mesh encapsulation table

Relationship with Other MIBs

Page 5: Softwire Mesh MIB draft-cui-softwire-mesh-mib-02

Position softwire mesh MIB• swmMIB ::= {transmission xxx}

transmission(10)

tunnelMIB(131) swmMIB(xxx)

root

cci tt(0) i so(1) joint-cci tt-i so(2)

standard(0) registration authori ty(1)

member body(2)Identifi ed

organization(3)

dod(6)

internet(1)

di rectory(1) mgmt(2) experimental (3) private(4)

mib2(1)

system(1) i nterface(2)

……

……

…… ……

Page 6: Softwire Mesh MIB draft-cui-softwire-mesh-mib-02

Subtree of swmMIB• swmTunnelTypeTable : Supported tunnel Type

• swmEncapsTable : Information about encapsulation

• swmBGPNeighborTable : Information about mesh neighbors

• swmMIBConformance

swmMIB

swmTunnelTypeTable swmEncapsTable swmBGPNeighborTable swmMIBConformance

Page 7: Softwire Mesh MIB draft-cui-softwire-mesh-mib-02

swmTunnelTypeTable ::= {swmMIB 1}

• Shows what kind of tunnel type the softwire mesh tunnel supported– Indexed by ifIndex & swmTunnelType– Current softwire mesh tunnel supports IP-IP, GRE,

L2TPv3 (section 4 of RFC5512)swmTunnelTypeTable

swmTunnelTypeEntry

swmTunnelType

Page 8: Softwire Mesh MIB draft-cui-softwire-mesh-mib-02

swmEncapsTable ::= {swmMIB 2}• A encapsulation table of the softwire mesh tunnel, including IPv4-

over-IPv6 and IPv6-over-IPv4– Indexed by ifIndex & swmEncapsEIPDst & swmEncapsEIPMask– Address type is decided by tunnelIfAddressType in tunnelIfTable

• Objects – Destination (E-IP destination address + mask)– Encapsulation header (I-IP destination address)

swmEncapsTable

swmEncapsEntry

swmEncapsEIPDst swmEncapsEIPMask swmEncapsIIPDst

Page 9: Softwire Mesh MIB draft-cui-softwire-mesh-mib-02

swmBGPNeighborInfo ::= {swmMIB 3}• BGP neighbor information of the softwire mesh tunnel

– Indexed by ifIndex & swmBGPNeighborAddress• Objects

– BGP neighbor address– negotiated tunnel type with each neighbor

swmBGPNeighborTable

swmBGPNeighborEntry

swmBGPNeighborAddress swmBGPNeighborTunnelType

Page 10: Softwire Mesh MIB draft-cui-softwire-mesh-mib-02

Discussion

• Collaboration welcomed. Please jump in if you’re interested.

• Suggestions? Anything we miss?