Tail-f Systems ConfD is a data-model driven network configuration and management system. It provides a core engine that supports multiple protocols like NETCONF, SNMP, REST, and CLIs. ConfD uses YANG data models to automatically render management interfaces and data stores. It also provides transactional configuration, validation, rollback management, and monitoring of operational data. ConfD aims to make network devices more manageable, programmable, and standards-compliant using model-driven development.

1. Tail-f Systems ConfD Overview

2. The network
is a federated
database
The NetworkAPI is here
NETCONFCisco CLI, SNMP, REST, …
End-to-end
Transactional
Integrity
Network CLI Network WebUI
Service Application
e.g. VPN-provisioning
Device Setup
e.g. Templates, Scripts
Transactional Network API
Service Management + Device Management

3. 3
Data-Model Driven
Any protocol
SNMP Agent
CLI Engine
NETCONF Server
…
How is ConfD Different?
Protocol Focused Agents
Protocol Focused Agents ConfD
All protocols
No feature lag
Core engine
Stove-pipe
Feature-lag
Just the protocol layer

4. 4
ConfD Overview
Network
Element
CDB
DATABASE
External
Database
Core Engine
NETCONF SNMP REST CLI WEB
UI
Management Agent API
Data Provider API
Managed Object API Operational
Data
MO MOMOMOMO
EMS/OSS
NCS

5. 5
ConfD Overview
Network
Element
CDB
DATABASE
External
Database
Core Engine
NETCONF SNMP REST CLI WEB
UI
Management Agent API
Data Provider API
Managed Object API Operational
Data
MO MOMOMOMO
EMS/OSS
NCS
YANG
Data Models
Auto-rendered management interfaces and data store schema

6. 6
ConfD Overview
Authentication
API
Operational
DataAPI
Operational
Data
Radius
PAM
TACACS
Others
MO MO MO
MO MO
ConfD
NETCONF SNMP REST CLI Web UI
ConfD Core Engine
CDB
Database
Transaction Management
Session Management / Authentication
Role-based Access Control
Redundancy / Replication
Event Logging / Audit Trailing
Validation (syntactic and semantic)
Rollback Management
Upgrades and Downgrades
External Data Provider API Managed Object API
Management Agent API
External
Database
Operational
Data
Counters
Alarms
Statistics

7. 7
ConfD Overview
IPC (Sockets)
Application Blades
App
API lib
App
API lib
NETCONF
CLI
Web
SNMP
REST
App
API lib
App
API lib
ConfD
Management Blade
Unix/Linux process

8. 8
Why ConfD ?
Make your customer happy Save time

9. 9
Why ConfD ?
Make your device
• Manageable
• Programmable
• Standards -compliant
Make your customer happy Save time

10. 10
Why ConfD ?
Make your device
• Manageable
• Programmable
• Standards -compliant
SDN
Ready
Make your customer happy Save time

11. 11
Why ConfD ?
Make your device
• Manageable
• Programmable
• Standards -compliant
SDN
Ready
• WebUI, CLI, REST, SNMP, NETCONF
• Transactions and Rollbacks
• Validations
• Configuration and Monitoring
• No feature lag
Make your customer happy Save time

12. 12
Why ConfD ?
Make your device
• Manageable
• Programmable
• Standards -compliant
SDN
Ready
• WebUI, CLI, REST, SNMP, NETCONF
• Transactions and Rollbacks
• Validations
• Configuration and Monitoring
• No feature lag
Make your customer happy
• Render Management interfaces
• Model-driven
• Iterative development
Save time

13. 13
Make your device
• Manageable
• Programmable
• Standards -compliant
Why ConfD ?
Make your customer happy
SDN
Ready
• WebUI, CLI, REST, SNMP, NETCONF
• Transactions and Rollbacks
• Validations
• Configuration and Monitoring
• No feature lag
• Core components
• Embedded database
• Domain-specific functions
• Rich APIs
• Well-tested, 70+ customers
• Render Management interfaces
• Model-driven
• Iterative development
Make your customer happy Save time

14. 14
QuaggaDemo Setup
Laptop
Getting Started with ConfD
• Data model driven
• Transactions
• Validation
• Rollbacks
Auto rending of APIs and interfaces
• Auto-rendered and Customizable
• Monitoring
Operational status monitoring
• Array of management interfaces
• Concurrent sessions
• Conflict resolution
ConfD
Config,
stats, …
Quagga
Data model
Web
browser
Terminal
ConfD
Quagga

15. 15
Demo Playlist
• Demo scenario
• Getting started with ConfD
• Auto rending of APIs and interfaces
• Operational status monitoring
• YANG Models

16. Thank you for watching
www.tail-f.com