Skip to content

6.1.1 NETCONF Broker

Jump to bottom
rodmichael edited this page Aug 15, 2019 · 2 revisions

c_

In order to avoid scaling issues in regards to all different applications establishing a NETCONF connection to network devices, the NETCONF Broker is used. It is basically in charge of maintaining permanent NETCONF over SSH connection to every network device and handling RPC requests/replies. Its workflow is summarized as:

  1. Gets the network device inventory from Inventory API.
  2. Opens a NETCONF over SSH connection to every network device within the inventory (except to route reflectors).
  3. Creates one queue in the Rabbitmq for every single network device and subscribes to it.
  4. When a new message (RPC-like) is received on a queue it is handed over to its network device and waits for corresponding RPC reply.
  5. Once RPC reply is received, it sends it to the queue declared by the client (any other application making use of the NETCONF Broker) while publishing.

Detailed information in repo

Clone this wiki locally