Network Configuration Management with NETCONF and YANG - IETF

More documents

Recommendations

Info

Summary and Advice. . . ⊲ If you are working on configuration of something, consider NETCONF seriously before rolling your own protocol ⊲ NETCONF is based on years of experience ⊲ NETCONF over BEEP or SOAP may disappear ⊲ There are solid (open source) implementations ⊲ Writing data models in YANG can actually be fun ⊲ There are very good (open source) tools around ⊲ Review existing YANG modules to see how your model fits into the core set of data models being defined ⊲ Check RFC 6087: Guidelines for Authors and Reviewers ⊲ Ask YANG doctors for help as needed 86 / 90
Reading Material I [1] J. Schönwälder, M. Björklund, and P. Shafer. Network Configuration Management Using NETCONF and YANG. IEEE Communications Magazine, 48(9):166–173, September 2010. [2] P. Shafer. An Architecture for Network Management Using NETCONF and YANG. RFC 6244, Juniper Networks, June 2011. [3] J. Schönwälder. Overview of the 2002 IAB Network Management Workshop. RFC 3535, International University Bremen, May 2003. [4] L. Sanchez, K. McCloghrie, and J. Saperia. Requirements for Configuration Management of IP-based Networks. RFC 3139, Megisto, Cisco, JDS Consultant, June 2001. [5] M. Ersue and B. Claise. An Overview of the IETF Network Management Standards. RFC 6632, Nokia Siemens Networks, Cisco Systems, June 2012. [6] M. Bjorklund. YANG - A Data Modeling Language for the Network Configuration Protocol (NETCONF). RFC 6020, Tail-f Systems, October 2010. [7] J. Schönwälder. Common YANG Data Types. RFC 6021, Jacobs University, October 2010. [8] A. Bierman. Guidelines for Authors and Reviewers of YANG Data Model Documents. RFC 6087, Brocade, January 2011. 87 / 90
Page 1 and 2:
Network Configuration Management wi
Page 3 and 4:
Today’s Menu . . . NETCONF The Ne
Page 5 and 6:
“The Network is the Record” Pol
Page 7 and 8:
Configuration Management Requiremen
Page 9 and 10:
Page 11 and 12:
Page 13 and 14:
Page 15 and 16:
Page 17 and 18:
NETCONF and YANG Timeline Date Mile
Page 19 and 20:
NETCONF RFCs (as of today) RFC Stat
Page 21 and 22:
Layering Model (RFC6241) Layer Exam
Page 23 and 24:
Transaction Models (RFC6241) Direct
Page 25 and 26:
Remote Procedure Calls (RFC6241) Th
Page 27 and 28:
NETCONF Operations (RFC6241) ⊲ ge
Page 29 and 30:
NETCONF Operations (RFC6241) ⊲ ge
Page 31 and 32:
More NETCONF Operations (RFC5717, R
Page 33 and 34:
Editing (Patching) Configuration Ex
Page 35 and 36: Subtree Filtering (cont.) ⊲ conta
Page 37 and 38: NETCONF over SSH (RFC6242) Motivati
Page 39 and 40: NETCONF over SSH: End-of-Message Fr
Page 41 and 42: NETCONF over SSH: Chunked Framing S
Page 43 and 44: YANG RFCs (as of today) RFC Status
Page 45 and 46: Modules and submodules import inclu
Page 47 and 48: Built-in Data Types Category Types
Page 49 and 50: Data Nodes: Leafs, Leaf-lists, Cont
Page 51 and 52: Example: container container system
Page 53 and 54: Augment, Must, When, Presence ⊲ a
Page 55 and 56: Example: augment and must augment /
Page 57 and 58: Grouping, Choice, Notification, RPC
Page 59 and 60: Example: choice container transfer
Page 61 and 62: Example: rpc rpc activate-software-
Page 63 and 64: Core Interfaces Data Model +--rw in
Page 65 and 66: Core IP Interfaces Data Model +--rw
Page 67 and 68: Core IP Routing Data Model (ietf-ro
Page 69 and 70: Core System Data Model: System Iden
Page 71 and 72: Core System Data Model: User Authen
Page 73 and 74: Implementations, Tools, and Usage [
Page 75 and 76: NETCONF in Devices Device Vendors (
Page 77 and 78: YANG Data Models IETF (not necessar
Page 79 and 80: YANG Mapping to JSON The mapping de
Page 81 and 82: YANG to JSON Example (XML) eth0 e
Page 83 and 84: RESTful API for YANG Example C: GET
Page 85: Discussion [20 min] 1 Configuration
Page 89 and 90: Reading Material III [17] S. Chisho
show all

Network Configuration Management with NETCONF and YANG - IETF

You also want an ePaper? Increase the reach of your titles

Delete template?

Save as template?