RPC reply is not received at netconf client

Core Engine and APIs
1

Hi all,

I’ve 3 netconf clients with the following session ids: 15, 52, 53.
From netconf client with session-id=52, edit-config rpc is send & rpc-reply is received. Then, commit rpc is send but rpc-reply is not received at the netconf client.

From confd_netconf.log:

27-Aug-2020::08:43:30.387 Scale-NPT1300 confd[1205]: netconf id=52 got rpc: {urn:ietf:params:xml:ns:netconf:base:1.0}edit-config attrs: message-id=“16”
27-Aug-2020::08:43:30.844 Scale-NPT1300 confd[1205]: netconf id=52 edit-config target=candidate attrs: message-id=“16”
27-Aug-2020::08:43:31.652 Scale-NPT1300 confd[1205]: netconf id=52 sending rpc-reply, attrs: message-id=“16”
27-Aug-2020::08:44:08.970 Scale-NPT1300 confd[1205]: netconf id=52 got rpc: {urn:ietf:params:xml:ns:netconf:base:1.0}commit attrs: message-id=“17”
27-Aug-2020::08:44:08.971 Scale-NPT1300 confd[1205]: netconf id=52 commit attrs: message-id=“17”
27-Aug-2020::09:49:50.433 Scale-NPT1300 confd[1205]: netconf id=53 ssh transport closed

From confd_traces.log:

…
…
2020-08-27 09:58:29:848 TRACE CALL data get_next(thandle=61, /routing/mpls/interface, 3)2020-08-27 09:58:30:070 --> CONFD_OK
2020-08-27 09:58:30:071 TRACE CALL data delete(thandle=61,/interfaces/interface{lo0.40378})2020-08-27 09:58:30:071 --> CONFD_ACCUMULATE
2020-08-27 09:58:30:072 TRACE CALL data delete(thandle=61,/interfaces/interface{xe-ts5/1.9418})2020-08-27 09:58:30:073 --> CONFD_ACCUMULATE
2020-08-27 09:58:30:074 TRACE CALL data delete(thandle=61,/network-instances/network-instance{test_56-5416562630})2020-08-27 09:58:30:075 --> CONFD_ACCUMULATE
2020-08-27 09:58:30:076 TRACE CALL trans prepare(thandle=61)2020-08-27 09:58:54:398 TRACE Connected (maapi) to ConfD
2020-08-27 09:58:54:398 TRACE MAAPI_XPATH2HKP 2020-08-27 09:58:54:402 --> CONFD_OK
2020-08-27 09:58:54:406 TRACE Connected (maapi) to ConfD
2020-08-27 09:58:54:406 TRACE MAAPI_XPATH2HKP 2020-08-27 09:58:54:410 --> CONFD_OK
2020-08-27 09:58:54:414 TRACE Connected (maapi) to ConfD
2020-08-27 09:58:54:414 TRACE MAAPI_XPATH2HKP 2020-08-27 09:58:54:416 --> CONFD_OK
2020-08-27 09:59:00:329 --> CONFD_OK
2020-08-27 09:59:00:330 TRACE CALL trans commit(thandle=61)2020-08-27 09:59:00:331 --> CONFD_OK

As you can see from the logs, commit rpc was send at 27-Aug-2020::08:44:08.971 & commit callback was invoked at 27-Aug-2020 09:59:00:330 (there is a lot of config present, that is the reason why it is taking around 1 hour). But, finish callback is not invoked afterwards.

Can anyone assist what could be the reason why finish callback was not invoked?

NOTE: In between the callbacks for the commit rpc were getting invoked, the netconf client with session-id = 53 is made down. That is the reason for the log message ssh transport closed in confd_netconf.log

2

What NETCONF client do you use? Do you have any client logs that may indicate what is wrong.
From described scenario I understand the commit operation is taking too long time. Can it be that
NETCONF client with ID 52 closed connection as well? Is there any connection timeout at client side?
Did you try to test the scenario with shorter commit time - around seconds/minutes (less data to process)?

3

@mnovak
I was using MGSoft for session id 52. This issue is observed only once & I don’t have any client logs.

Update: There were no connection timeout at client side.

4

OK, it is hard to say. Did you also try with less data to process?
From logs it seems the connection was closed.

Would it be posible to try netconf-console instead od MG Soft to verify the behavior is the same?