Call Home
By default, in the NetConf protocol (RFC 6241), a NetConf client application initiates the connection towards the NetConf server in the network element (OcNOS device). However, for certain use cases such as in the presence of firewalls or NAT, it is useful to have “call home” functionality where the connection process is reversed and the NetConf server initiates the connection to the NetConf client. This process, as shown in Figure 15-2, is standardized by IETF in RFC 8071.
RFC 8071 NetConf call home functionality
OcNOS supports call home feature (only for SSH) at the NetConf server side. You can use any standard NetConf client application which supports call home functionality. (Call home support in the NetConf client application [Yangcli] is not supported.)
Call home is generally useful for both the initial deployment and ongoing management of networking elements.
Note: Call Home allows for a maximum of 5 Call Home servers, with a single NETCONF session per server.
Configuration
To configure the call home server and other required metadata, use the ipi-management-server module. The Yang tree below lists the related attributes.
module: ipi-management-server
+--rw netconf-server
+--rw callhome!
| +--rw feature-enabled empty
| +--rw management-port? string
| +--rw netconf-client* [name]
| | +--rw name string
| | +--rw address string
| | +--rw port? inet:port-number
| +--rw reconnect!
| +--rw enable empty
| +--rw retry-max-attempts? uint8
| +--rw retry-interval? uint32
+--rw debug
+--rw callhome-debug? empty
For details, see the NetConf Command Reference.