changes made and saved go back to default in days

[brdn]

Can any one tell me why I change the number of license in smit to a different number and days later it will default back to 32 and my change is gone? Operating on Aix 5.1L

 

[sushveer]

Hi brdn

Can u run the follwing command and let me know whether your
floating license is enabled/disabled

#lslicense

sushveer
IBM certified specialist-p-series AIX5L System Administration
AIX/SOLARIS/WEBSPHERE-MQ/TIVOLI Administrator

 

[sushveer]

Hi

Did u reboot the system after changing number of fixed licenses regardless of floating licenses..

Without rebooting for couple of days you will see your new/changed value but again it defaults to old value.

My advice is now you can change with the follwing command
and reboot the system...also check for monitord daemon for existence...

#chlicense -u <fixed_license_number> -f on
The f flag enables/disable floating license,Here it enables
but for disbaling use -f off

sushveer
IBM certified specialist-p-series AIX5L System Administration
AIX/SOLARIS/WEBSPHERE-MQ/TIVOLI Administrator

 

[brdn]

Thanks for the reply.
Right now the lslicense command says max is 100 and floating license is enabled. The machine reboots every night so far it has been 2 days since we made the change and it has not gone back to default. It could be today, the next day or next week before it goes back to default. We have made this change to 100 several times and it always goes back to 32 in a matter of time.

 

[sushveer]

Hi

Let me test/monitor that on my aix node for 3 days and
will be back to forum

sushveer
IBM certified specialist-p-series AIX5L System Administration
AIX/SOLARIS/WEBSPHERE-MQ/TIVOLI Administrator

 

[brdn]

chlicense -u worked for about 2 weeks and now it has defaulted back to 32 license. Have chage it several times to off and on and it keeps reverting back. Any more suggestions?

 

[sushveer]

Hi brdn

Aafter changing with chlicense command ,also edit the file
/etc/security/login.cfg for the parameter
maxlogins = 32 ...Then reboot.
Please ensure that your login.cfg file has new number...
and let me know if not resolved...

sushveer
IBM certified specialist-p-series AIX5L System Administration
AIX/SOLARIS/WEBSPHERE-MQ/TIVOLI Administrator

 

[brdn]

sushveer,
Thanks for the info. Have made the changes and checked the maxlogin file and it all look good. Will wait and see what happens.

 

[sushveer]

Hi brdn

I too followed the same procedure on one of the nodes for testing purpose.I monitored for 4 days so far but changes are effective. Inotherwords no problem of defaulting to...
what is your experience...still u r monitoring the node..?!.
Let me know...

sushveer
IBM certified specialist-p-series AIX5L System Administration
AIX/SOLARIS/WEBSPHERE-MQ/TIVOLI Administrator

 

[brdn]

The last time we changed it was on the 19th and so far so good. The time before that it lasted about 2 weeks before it went back to default. Will keep a eye on it and hopefully this will slove problem.
Thanks

 

[brdn]

Well,
It's taken from the 19th of Aug. till the 9th of Sept. to change back to the default setting of 32 license, but it did change back. Got any more suggestions? Thanks.

 

[bi]

What maintenance level are you at?

 

[brdn]

4.3.1, in process of upgrading to 5.1l

 

[bi]

I thought your first post said the system already was at 5.1. I'm just wondering if a new maintenance level would have fixed the problem. But they aren't making MLs for 4.3.1 anymore.