Upgrade W2k 6.1.1 > 6.1.2 problems

[tontan]

Hi!
I tried to upgrade W2k from 6.1.1 to 6.1.2 yesterday.
Everything worked out fine until i ran a backup off virtual cluster nodes.
The error message "Save:RAP error Unable to grant NT CLUSTER CLIENT
license: To many clients. Maximum is 2"

I have a Compaq Proliant DL760 W2k Networker server with SP3
2 W2k cluster nodes whith 4 virtual clients. And several other clients.
1 Changer ESL9326D with 3 SDLT
Sanswitch/8 and a MDR


I did not have this problems before upgrade and nsrlic -v didn´t report
anything strange either before or after the upgrade.
I´m not sure if this is a bug or if someone had this error, but I can not
find anything about it in tech dialog or any NetWorker forums.

I deleted and put back the cluster licenses "didn´t work"
I tried to put in more cluster licenses "didn´t work
I deleted the virtual clients and put them back "didn´t work"
I tried to put back my 6.1.1 nsr.res file "didn´t work"
And lots of other troubleshooting

The solution was to rollback to 6.1.1 again and it worked fine.

Any suggestions to make this work or is it somone who had similar
problems???

regards

Tony Hordin
Systems Engineer

 

[tontan]

Seems that i´m the only one who had this problem??
Any suggestions?

\\ Tony

 

[wallace88]

How many clusters in your environment?

How many physical nodes do you have?
How many virtual nodes?

How many cluster licenses?

You need one cluster license for each physical node in your cluster(s). However, it could be that NetWorker thinks the virtual node is a physical node.

 

[tontan]

As I said erlier "above"....
2 W2k cluster physical nodes whith 4 virtual nodes.
2 W2k/NT cluster licenses. Witch should be enough.

It could maby be some corruption to the cluster licenses
after the upgrade to NW 6.1.2.... and I think that I could not be the only guy who had this problem. Or i´m I???? :-(

\\ Tony

 

[wallace88]

In the Media kit there are a bunch of temporary enabler codes. Use one that is for 4 or more cluster client connections for Windows NT and see if the problem goes away.

If it does, then it is a bug with the software with 6.1.2 not properly detecting cluster nodes properly.