netopeer2 icon indicating copy to clipboard operation
netopeer2 copied to clipboard

Capabilities of Netopeer2 for Managing Call Home Retry Attempts

Open lalahdab opened this issue 2 months ago • 3 comments

Does the current version of Netopeer2 support tracking the number of failed Call Home attempts? Additionally, is there a parameter available that allows users to control the frequency of Call Home retries, such as initiating a new attempt every x seconds?

lalahdab avatar Oct 14 '25 12:10 lalahdab

You can configure all the Call Home parameters in the YANG module.

michalvasko avatar Oct 15 '25 10:10 michalvasko

thx for ur reply but apparently there is no way to know whether the current attempt is failed, right ?

2- it is mentioned that : Max wait: Specifies the amount of time in seconds after which, if the connection is not established, an endpoint connection attempt is considered unsuccessful. well it means it the time interval between each attempt for the same endpoint right ?

can I kill the session and then use the reconnect strategy? thx in advance

lalahdab avatar Oct 16 '25 15:10 lalahdab

thx for ur reply but apparently there is no way to know whether the current attempt is failed, right ?

No, it is managed automatically.

well it means it the time interval between each attempt for the same endpoint right ?

Yes, I believe that is correct.

can I kill the session and then use the reconnect strategy?

Yes, if the Call Home session is terminated for any reason, the configured reconnect strategy is used.

michalvasko avatar Oct 17 '25 06:10 michalvasko

Do you think a notification from the netconf-server whenever a max attempt is reached for a specific endpoint could be considered to be added ?

It could be nice to have the apps that configured the netconf's server being notified about the failure. Unless you know some other way to check this from the outside of the netconf server ?

Krisscut avatar Dec 18 '25 10:12 Krisscut