netconf role in the network management system draft atarashi netconfmodel architecture 03
Download
Skip this Video
Download Presentation
NETCONF role in the Network Management System ( draft-atarashi-netconfmodel-architecture-03)

Loading in 2 Seconds...

play fullscreen
1 / 10

NETCONF role in the Network Management System ( draft-atarashi-netconfmodel-architecture-03) - PowerPoint PPT Presentation


  • 75 Views
  • Uploaded on

66 th IETF meeting netconf WG. NETCONF role in the Network Management System ( draft-atarashi-netconfmodel-architecture-03). Friday, July 14, 2006 Hideki Okita (Hitachi Central Research Lab) Ray S. Atarashi (IIJ) Yoshifumi Atarashi (Alaxala Networks) Elisa Boschi (Hitachi Europe).

loader
I am the owner, or an agent authorized to act on behalf of the owner, of the copyrighted work described.
capcha
Download Presentation

PowerPoint Slideshow about ' NETCONF role in the Network Management System ( draft-atarashi-netconfmodel-architecture-03)' - leda


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.While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server.


- - - - - - - - - - - - - - - - - - - - - - - - - - E N D - - - - - - - - - - - - - - - - - - - - - - - - - -
Presentation Transcript
netconf role in the network management system draft atarashi netconfmodel architecture 03

66th IETF meeting netconf WG

NETCONF role in theNetwork Management System (draft-atarashi-netconfmodel-architecture-03)

Friday, July 14, 2006

Hideki Okita (Hitachi Central Research Lab)

Ray S. Atarashi (IIJ)

Yoshifumi Atarashi (Alaxala Networks)

Elisa Boschi (Hitachi Europe)

starting point
Starting Point
  • The new integrated network management architecture is required for the broadband network.
    • MIBs are 90’s design.
      • It is hard to implement.
      • Because tree design is too large, today.
      • Its administration is very hard.
      • It is not familiar with applications and services (i.e. other area).
    • CLI is 80’s UNIX design base.
      • Routers are designed based on BSD unix workstation.
modern technologies
Modern Technologies
  • Now we can use 21th century computer technology.
    • Operators have to manage both network and computers because many services are hosted on the computers.
    • We can design upper layer convert mechanism using XML technologies. (ex. XSLT)
    • Apache/web services programmer can make application services.
    • Java allows programmers to develop machine independent code at short time.
layer divide problem
Layer Divide Problem
  • Network has been originally developed ”for applications”.
    • But any network layer people doesn’t read Application area documents.
    • We call it “Layer divide problem”.
  • Application layer people can’t use new Network full features.
    • IPv6, QoS, multicast etc.
  • Applications always use ad-hoc technique.
    • Application layer re-transmissions, etc.
  • Inter-Layer collaboration is required.
    • We can use XML technology.
    • Network and operation also be going to next step.
protocol v s api
Protocol V.S. API?
  • Application programmers don’t know protocol on Network.
  • They need API and SDK.
  • Netconf is good approach to start new generation mechanisms.
  • We have to design new protocol/API definitions.
api trial
API Trial
  • We are trying to implement API for the network management system.
    • Using Java and Web-Services.
  • We have some experiences.
    • Example
      • SSH is not good choice for implementing.
        • SSH is not best security solution for programmer.
        • SSL is better than SSH.
        • Because Apache doesn’t support SSH.
      • Easy to implement using Apache and libraries.
      • Apache has already supported SOAP over SSL.
contents of architecture draft
Objectives

To clarify the role of the NETCONF system in a network service

To provide a reference architecture

To provide an example of NETCONF system usage

Give feedback to the WG

Contents of Architecture draft

Applications,

operators

XML

DB

NETCONF Manager

Current

NMS

NETCONF

Configuration

/Notification

SNMP, Syslog, IPFIX, etc…

Network

event notification concern
Event Notification Concern
  • There are multiple notification methods
    • NETCONF, SNMP, Syslog, IPFIX, etc…
    • What is the right/suitable usage of NETCONF-based notification?
  • Comparison of each methods
    • Rapidness
    • Flexibility of data model
    • Relation with applications
  • Characteristics of NETCONF notification
    • Not so rapid compared to other UDP based protocols
      • UDP based asynchronous protocol is lighter and faster than an RPC based one
    • Good flexibility of data model
    • Easy to construct relationship using application programming technologies (e.g. apache and libraries)
netconf system demonstration interop2006 tokyo
NETCONF System Demonstration(Interop2006 Tokyo)

operator

  • We demonstrated a intelligent network management system using NETCONF.
  • Summary of the demo
    • Manager configures network devices via NETCONF
    • NETCONF-based VLAN configuration
  • Plans to contribute an implementation report / implementation guide

VLAN

re-assign

XML

DB

NETCONF Manager

System overview

Our operators :-)

conclusions
Conclusions
  • Lessons learned from our implementation
    • Wide deployment of Web-based XML application
    • Application layer and network layer would collaborate more closely.
      • Automation scenarios are given by the application layer.
      • XML-based protocols are familiar with the application programmers.
  • We should consider new network management architecture
    • OPS area people have to use application programming technology and structured data model.
      • Syslog is flat data model.
      • Java is structured model based language.
      • XML can define any model.
      • But we have to think “structured”.
      • Meta-data engine/XML DB can use structured data.
    • We can make XML base protocol instead of signaling.
  • APP/RAI/OPS area should work together and need to collaborate
    • WGs using XML technology should take care each other
    • Ex. XCAP (RAI/simple) and NETCONF
ad