# Netconf Notification capabilities

**URL:** <https://dmap-community.ductus.global/t/netconf-notification-capabilities/364>\
**Category:** Other Northbound Interfaces\
**Created:** [January 25, 2016, 8:24pm UTC](https://dmap-community.ductus.global/t/netconf-notification-capabilities/364 "2016-01-25T20:24:27Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![pavanfds](https://avatars.discourse-cdn.com/v4/letter/p/a88e57/32.png) [@pavanfds](https://dmap-community.ductus.global/u/pavanfds)\
**Post date:** [January 25, 2016, 8:24pm UTC](https://dmap-community.ductus.global/t/netconf-notification-capabilities/364/1 "2016-01-25T20:24:27Z")

</div>

i would like to know how many notifications streams can a northbound application subscribe to in one netconf session.

By default, the northbound application registers to the  
NETCONF stream that is provided by the ietf-netconf-notifications schema (RFC  
6470) [0].

Then, when I try to register to the overheat(some other stream)stream, I’m returned "A subscription is already active for this session”.

So that lead me to try the following: register first the stream overheat and then the stream NETCONF. and i get the same error.

So i wanted to know the limitation in Confd and if there is a way to subscribe to multiple streams.

---

<div class="post-metadata">

**Author:** ![jlawitzke](https://yyz2.discourse-cdn.com/flex010/user_avatar/dmap-community.ductus.global/jlawitzke/32/54_2.png) [@jlawitzke](https://dmap-community.ductus.global/u/jlawitzke)\
**Post date:** [January 25, 2016, 10:56pm UTC](https://dmap-community.ductus.global/t/netconf-notification-capabilities/364/2 "2016-01-25T22:56:08Z")

</div>

Reclassified to the Northbound Interfaces category.

---

<div class="post-metadata">

**Author:** ![waitai](https://yyz2.discourse-cdn.com/flex010/user_avatar/dmap-community.ductus.global/waitai/32/436_2.png) [@waitai](https://dmap-community.ductus.global/u/waitai)\
**Post date:** [January 25, 2016, 11:35pm UTC](https://dmap-community.ductus.global/t/netconf-notification-capabilities/364/3 "2016-01-25T23:35:42Z")

</div>

Only a single subscription is supported per NETCONF session as per section 6.5 of the NETCONF Event Notifications RFC (5277). A subscription is bound to a single stream as per section 2.1 of the NETCONF Event Notifications RFC (5277).

---

<div class="post-metadata">

**Author:** ![pavanfds](https://avatars.discourse-cdn.com/v4/letter/p/a88e57/32.png) [@pavanfds](https://dmap-community.ductus.global/u/pavanfds)\
**Post date:** [January 26, 2016, 5:59pm UTC](https://dmap-community.ductus.global/t/netconf-notification-capabilities/364/4 "2016-01-26T17:59:09Z")

</div>

thanks for that.  
To add on to that

1. Can there be multiple notifications(with different XML formats) in one stream
2. Can the notification be triggered by calling a send\_notification from the confd client, and will this be propagated forward. or does the confd server monitor the yang model for triggering this. (i want to send a notification northbound from the confd client independent of any leaf in the yang model )

---

<div class="post-metadata">

**Author:** ![waitai](https://yyz2.discourse-cdn.com/flex010/user_avatar/dmap-community.ductus.global/waitai/32/436_2.png) [@waitai](https://dmap-community.ductus.global/u/waitai)\
**Post date:** [January 26, 2016, 7:04pm UTC](https://dmap-community.ductus.global/t/netconf-notification-capabilities/364/5 "2016-01-26T19:04:41Z")

</div>

1. You can use subtree or XPath filtering to specify the subset of all possible events that is part of the same stream, as per the Event Stream Definition in RFC 5277, to be sent. Only a single stream can be specified per session as was stated in my previous response.

2. Other than the default NETCONF stream, all other streams are to be triggered by the ConfD client applications using the confd\_notification\_send( ) API call as described in the ConfD User Guide.