# Integrate NETCONF to old system

**URL:** <https://dmap-community.ductus.global/t/integrate-netconf-to-old-system/908>\
**Category:** General\
**Created:** [December 29, 2016, 4:09am UTC](https://dmap-community.ductus.global/t/integrate-netconf-to-old-system/908 "2016-12-29T04:09:05Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![so61pi](https://avatars.discourse-cdn.com/v4/letter/s/94ad74/32.png) [@so61pi](https://dmap-community.ductus.global/u/so61pi)\
**Post date:** [December 29, 2016, 4:09am UTC](https://dmap-community.ductus.global/t/integrate-netconf-to-old-system/908/1 "2016-12-29T04:09:05Z")

</div>

Hi all,

I’m trying to integrating NETCONF to my old system which has its own way to manage configuration. My question is can I use tail-f product as a higher layer of my system so I can call my old system APIs (that mean I don’t have to change change my old system too much)? If so, is there any example for that?

---

<div class="post-metadata">

**Author:** ![mnovak](https://yyz2.discourse-cdn.com/flex010/user_avatar/dmap-community.ductus.global/mnovak/32/183_2.png) [@mnovak](https://dmap-community.ductus.global/u/mnovak)\
**Post date:** [January 2, 2017, 9:16am UTC](https://dmap-community.ductus.global/t/integrate-netconf-to-old-system/908/2 "2017-01-02T09:16:42Z")

</div>

Hello,

yes, this is one of the typical use cases for ConfD. There are several approaches.

Usually you have to do:

- create `yang` data model describing your old system (configuration and state)

- implement `subscriber` to push configuration from ConfD (CDB database) to your old system (using your old API). To handle trasactionality, you can use two phase subscriber; see chapter 5.6. and `cdb_subscribe2` API in the ConfD User Guide and subscription examples

- implement data provider to fetch state data from your old system to be displayed in Netcong `<get>` messages; see chapter 6. in the ConfD User Guide and data provider examples.