Unsolved
1 Message
0
1276
Failing to add new Hyper-V as client to Networker. Microsoft module - Hyper-V
Hi,
Trying to add client to Networker failing with error message below. However there is no issue if I choose FileServer role, fails only on Hyper-V role. I am trying to add Hyper-V node to backup VM's.
nsr_render_log -S "today 17:15:00" -E "today 17:22:00" /nsr/logs/daemon.raw
Was not helpful and logs on Hyper-V node which I am trying to add as client. Logs
nsrnmmmhyperva haven't found anything that could help in there as well.Windows Event log - Application log only informational messages
Networker ver.: 19.2.1.0
Anyone has any ideas? Thanks for help in advance.
crazyrov
4 Operator
4 Operator
•
1.3K Posts
0
February 5th, 2021 23:00
@picodo, Please check the pre-requisites and complete those after installing the NMM on the HyperV server.
uvarovnick
27 Posts
0
October 6th, 2021 04:00
Hi!
I have the same problem. I need to create a client for a Hyper-V cluster. Clients for four nodes have been successfully created. The nodes are running on Windows Server 2012 R2 Datacenter. At the same step, the wizard hangs. Then the message timeout appears. What should I do? NetWorker 19.1.
crazyrov
4 Operator
4 Operator
•
1.3K Posts
0
October 6th, 2021 06:00
@uvarovnick, Have you tried checking the communication between the NetWorker server and the Hyper-V nodes using nsrrpcinfo -p client_name?
uvarovnick
27 Posts
0
October 7th, 2021 23:00
crazyrov,
Yes, here is the output of the command
# nsrrpcinfo -p clst02-hypv.xxxxxxxxxxxxxxxx
PROGRAM VERSION PROTOCOL PORT SERVICE
100000 2 tcp 7938 nsrportmapper Port Mapper
100000 2 udp 7938 nsrportmapper Port Mapper
390436 1 tcp 8367 nsrexecd GSS Authentication
390435 1 tcp 8065 nsrexecd Resource Mirror
390440 1 tcp 9877 nsrexecd_nsrfa Remote File Access
390113 1 tcp 7937 nsrexecd Remote Execution
390408 1 tcp 9567 nsrpsd Snapshot Management
390409 1 tcp 8815 nsrsnapckd Snapshot Management
390450 1 tcp 9411 nsrnmmra NMM Remote Agent
crazyrov
4 Operator
4 Operator
•
1.3K Posts
0
October 8th, 2021 06:00
OK, you might also check it all the nodes of that cluster not just the Cluster name. Also, do you see anything relevant in the daemon.raw when you attempt to add the client ? Can you share those details as well ?
Oster775
6 Posts
0
March 20th, 2022 00:00
Did you found a solution for this issue?