This post is more than 5 years old
44 Posts
0
1690
Same locking id for different servers on external NMC
Experts,
I'm using three networker servers (two production, one test). I'm using an external NMC on a seperate Windows Server. Production is running on AIX.
For licensing purposes I need to get different locking IDs from each of the networker servers.
The NMC shows the same locking id for two different servers. Moreover, our testserver has inherited this locking id from our 1st server (it has only recently been added). The first server has got now a different locking id.
Has anyone else seen similar behaviour? How to overcome this behaviour?
Best regards
Christian
ble1
14.3K Posts
0
September 30th, 2013 03:00
If cluster, make sure you do use NSR_HOSTIDS (or /nsr/res/hostids).
ble1
14.3K Posts
0
September 28th, 2013 13:00
Have you been playing with NSR_HOSTIDS?
chrygel
44 Posts
0
September 30th, 2013 00:00
No, I haven't
ble1
14.3K Posts
0
September 30th, 2013 01:00
There used to be an issue in the past with earlier NW7 code where two (or more) servers on LPAR, but within same physical machine, would get same hostid. Are these two LPARs on the same box? If not, did you try to use resources from PRD for TST machines.
chrygel
44 Posts
0
September 30th, 2013 02:00
Yes, all NetWorker Instances are running on the same Hosts (Clustered).
What puzzles me the most is the fact that the newly added server has got the locking ID from the old one.
Christian
chrygel
44 Posts
0
September 30th, 2013 03:00
We aren't using NSR_HOSTIDS (or /nsr/res/hostids).
$ ls -la /nsr/res/
total 32
drwxr-xr-x 5 root system 256 Sep 17 14:41 .
drwxr-xr-x 13 root system 4096 Sep 04 13:34 ..
-rw-r--r-- 1 root system 9 Sep 17 14:41 .nsr
drwx------ 2 root system 256 Sep 04 09:15 jobsdb
drwx------ 12 root system 4096 Sep 04 09:15 nsrdb
drwx------ 12 root system 4096 Sep 04 09:15 nsrladb
-rw-r--r-- 1 root system 0 Sep 03 17:52 servers
ble1
14.3K Posts
0
September 30th, 2013 04:00
I know, you said that. And I said you should start using it.