netconf event notifications n.
Download
Skip this Video
Loading SlideShow in 5 Seconds..
Netconf Event Notifications PowerPoint Presentation
Download Presentation
Netconf Event Notifications

Loading in 2 Seconds...

play fullscreen
1 / 14

Netconf Event Notifications

0 Views Download Presentation
Download Presentation

Netconf Event Notifications

- - - - - - - - - - - - - - - - - - - - - - - - - - - E N D - - - - - - - - - - - - - - - - - - - - - - - - - - -
Presentation Transcript

  1. Netconf Event Notifications IETF 66 Sharon Chisholm schishol@nortel.com Hector Trevino htrevino@cisco.com

  2. Outline • Key Features • Architecture • Requirements • Issues • Bugs

  3. Key Features • Clean subscribe/unsubscribe to notifications of interest • Modification of subscription without loss of notifications • Event Classes to enable ‘big bucket’ filtering • Ability to carry Netconf-content

  4. Netconf Layers Layer Example +-------------+ +----------------------------------------+ | Content | | Configuration data | +-------------+ +----------------------------------------+ | | +-------------+ +-------------------------------------------+ | Operations | | <get-config>, <edit-config> <notification>| +-------------+ +-------------------------------------------+ | | | +-------------+ +-----------------------------+ | | RPC | | <rpc>, <rpc-reply> | | +-------------+ +-----------------------------+ | | | | +-------------+ +------------------------------------------+ | Application | | BEEP, SSH, SSL, console | | Protocol | | | +-------------+ +------------------------------------------+

  5. An Architecture .... ---------------------------------------------- | Network Element | | ------------ | | | Alarm | | | | Management | -------------- | -------------- | ------------ |--->|Netconf Stack |<---------->| Netconf | | | | | | | | | | | | -------------- | --->| Client | | V | | | -------------- | ------------ | | | | | Event |--->| ------------------ | | | | Management | | |Other Protocols | | | | ------------ |--->| | | | | ------------------ | | |--------------------------------------------- | | ---------------------------------------------- | | Network Element | | | ------------ | | | | Alarm | | | | | Management | -------------- | | | ------------ |--->|Netconf Stack |<-------| | | | | | | | | | -------------- | | V | | | ------------ | | | | Event |--->| ------------------ | | | Management | | |Other Protocols | | | ------------ |--->| | | | ------------------ | |--------------------------------------------

  6. Message Flow C S | | | capability exchange | |-------------------------->| |<------------------------->| | | | <create-subscription> | |-------------------------->| |<--------------------------| | | | <notification> | |<--------------------------| | | | <notification> | |<--------------------------| | | | <modify-subscription> | |-------------------------->| (buffered) | <notification> | |<--------------------------| | <rpc-reply> | |<--------------------------|

  7. Message Format ___________________________________________________________________ || Notification Header || Data | ||__________________________________________________________||______| || subscriptionId| eventClasses| sequenceNumber| dateAndTime|| | ||_______________|_____________|_______________|____________||______|

  8. Requirements

  9. Requirements

  10. Requirements

  11. Requirements

  12. Issues - Big • Endless RPC versus Notifications • Syslog Tunnelling versus Notification Framework

  13. Issues – Less Big • Best way to have initial set up event classes while allowing extensibility • Create separate Event Class document? • More details of callHomeNotifications

  14. Bugs • Missing ‘data’ element from Notification XSD definition