Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Call home to loopback IP is failing #1611

Open
svashok opened this issue Jul 19, 2024 · 4 comments
Open

Call home to loopback IP is failing #1611

svashok opened this issue Jul 19, 2024 · 4 comments
Labels
is:question Issue is actually a question.

Comments

@svashok
Copy link

svashok commented Jul 19, 2024

Hi Michal,

When we try to run a sample netconf client in the same VM where netconf server is hosted, we get the following error during call home.

local call home failing at
sysrepocfg error: Invalid leafref value "default-ssh" - no target instance "/ncs:netconf-server/ncs:listen/ncs:endpoints/ncs:endpoint/ncs:name" with the same value. (path "/ietf-netconf-server:netconf-server/call-home/netconf-client[name='default-ssh']/endpoints/endpoint[name='local']/ssh/ssh-server-parameters/client-authentication/libnetconf2-netconf-server:endpoint-reference") (Validation failed)

Any suggestions please?

@svashok
Copy link
Author

svashok commented Jul 19, 2024

Basically I use the loopback IP for call home and this is the XML used:

image

@michalvasko
Copy link
Member

The XML you posted includes only a listen endpoint. You need to merge the Call Home configuration into this one, if you want to reference the listen endpoint authentication settings from a call-home endpoint.

@michalvasko michalvasko added the is:question Issue is actually a question. label Jul 19, 2024
@svashok
Copy link
Author

svashok commented Jul 22, 2024

After adding the call home configuration and IETF keystore in the same XML, call home is working. Thanks.

I have a follow up question please. Can a Netconf server dynamically initiate call home to an additional client without restarting the server, when it is already running and connected with a few clients? One option is to use configured-client-info, but that has to be sent by an existing client. The existing clients will not have the information about the new client.

@michalvasko
Copy link
Member

You can modify netopeer2-server configuration in run-time, so just normally add another client and the server should adjust itself accordingly.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
is:question Issue is actually a question.
Projects
None yet
Development

No branches or pull requests

2 participants