Networker Server on Hyper-V Virtual Machine.

Question

Hi,

I have IBM Server with Windows Server 2012 R2 OS on it and i have enabled Hyper-V feature. The server has 4 NIC card's, one NIC card is dedicated for Physical server, one NIC card is dedicated for Networker Server which is a VM and remaining 2 NIC card's for other 4 VM's

I have created a VM with Windows Server 2012 R2 OS on the Hyper-V and installed Networker Server in the same Hyper-V VM.

Also, i have created another 4 Hyper-V VM's on the IBM Machine.

The issue here is after installing Networker Client on the Physical machine i'm not able to register the client with networker server. I'm getting the error as "Server 'TMB-NETWORKER': Program not registered".

The Hyper-V machine is making use of multiple IP address for communication to networker server.

PS C:\> nsradmin -s tmb-networker -p nsrexecd
NetWorker administration program.
Use the "help" command for help, "visual" for full-screen mode.
nsradmin> p nsrla
type: NSRLA;
name: win-dc-dc-srvr;
nsrmmd version: ;
nsrsnmd version: ;
NW instance info operations: ;
NW instance info file: ;
installed products: ;
auth methods: "0.0.0.0/0,nsrauth/oldauth";
max auth attempts: 8;
administrator: Administrators,
"group=Administrators,host=win-dc-dc-srvr";
arch: Windows Server 2012 R2 Datacenter;
kernel arch: AMD_X8664;
CPU type: AMD_X8664;
machine type: server;
OS: Windows Server 2012 R2 Datacenter 6.3;
NetWorker version: 9.0.0.2.Build.448;
client OS type: Windows NT Server on Intel;
CPUs: 40;
MB used: 2168804;
IP address: 10.30.2.225, "fe80::5906:ef36:addf:ad52",
10.30.1.171, 10.30.29.5, 10.30.34.3,
169.254.95.120;

If i check with another Server using the same command i'm getting the output with single IP which is Networker IP.

I need to know why i could not able to register the client with Networker Server and why it is searching all IP's present in the Physical Server.

This type of configuration is possible or not supported configuration.

Please any one can help me out in this issue.

Thanks,

Yuvaraj.

l.walid · Answer

Hi,

This configuration is supported, and is what is called a multihomed conf, please check the rwlated part in the NetWorker administration guide.

The issue is related to the network, there is also a good part on troubleshooting network issue.

Follow those step, and give us your feedback.

Good luck

YuvarajV · Answer

Hi Largou,

Thanks for your valuable comments.

Actually, here we have only one Networker Server and one Storage Node. Multihomed configuration is for multiple networker server and storage nodes, so Multihomed configuration will not work here.

While using NSRLA command from client side it should connect to Networker IP only, but here it is checking all the IP's present in the Physical Server (Client). We don't know how to restrict it and also we tried with static routing but no change.

We tried disabling all the NIC's expect networker server NIC and Client NIC, still NSRLA command shows all IP's present in Physical Server.

Thanks,

Yuvaraj.

ble1 · Answer

NSRLA will always show all IPs on the system (actually all at the time when NSRLA resource has been created).  That list has nothing to do with connections.  Connections are set and ruled by your configuration and routing.

YuvarajV · Answer

Hi Hrvoje Crvelin, Thanks for your comments. Configuration and routing are set at Networker Server side or Windows Network Side. Please suggest me. Thanks. Yuvaraj

bingo.1 · Answer

You should begin with the basics and run nsrlookup for both, forward and reverse directions. Most important: Always check your hosts files just to make sure that there is no 'forgotten' entry.

ble1 · Answer

program not registered means communication could not be established. Here we assume, for now, that network configuration might be blocked. Reasons might be some blocks like firewall and of course routing. Other culprints might be client not installed. Now, we know service is running due to nsradmin output.

Now, communication issue might in one direction too, eg. from server to client. You need to establish that. I do not know which interface you use, but I will use front-end so I will use those names. If that is not the case, then replace those with desired ones.

server name is tmb-networker and client name is win-dc-dc-srvr. Go on server and run following command:

echo p | nsradmin -p 390113 -i - -s win-dc-dc-srvr (this will test nsrexecd communication from server to client)

Next, go to client and from there run following client:

echo p | nsradmin -p 390113 -i - -s tmb-networker (this will test nsrexecd communication from client to server)

Both of these should work. If not, something blocking the communication at basic level.

I assume you you wizard and that's where it fails. If above tests are ok, define manually client without wizard.

In case you do not use front-end (primary) name for client, then use following rules:

- define client with name assigned to interface which can communicate with server (eg. client-vlanxxx.domain)

- in storage node field of the client, use name which client can use in communication with storage node (sn-vlanxxx.domain)

- in backup server interface of the client, use name which client can use in communication with server

NetWorker

Networker Server on Hyper-V Virtual Machine.

Was this post helpful?