Insufiicient Security Privilege
After installing SMC 3.0 with platform update 4, I can add the host object in the SMC console however, when I try to modify the agent or add/remove a module I receive the "Insufiicient Security Privilege" message at the bootom of the window. I think It may be the security seed. When running es-setup for this host I normally accept the default seed however on this instance I was only prompted to enter my own seed, no default to choose. I entered what I believe is the deafult "maplesyr" Any help would be appricated.
[526 byte] By [
kcomber] at [2007-11-26 5:56:33]
# 1
Hello kcomber,
> After installing SMC 3.0 with platform update 4, I
> can add the host object in the SMC console however,
> when I try to modify the agent or add/remove a module
> I receive the "Insufiicient Security Privilege"
> message at the bootom of the window. I think It may be
> the security seed. When running es-setup for this host
> I normally accept the default seed however on this
> instance I was only prompted to enter my own seed, no
> default to choose. I entered what I believe is the
> deafult "maplesyr" Any help would be appricated.
On your SunMC Server make sure your username is in the "esadm" group in /etc/group. You are probably only in the "esdomadm" group. It doesn't sound like a seed problem because if it was you shouldn't have been able to make an icon for your Agent.
Recent patches of SunMC no longer provide you with the default "maplesyr" seed. Are you running different patch versions on your Agent and Server? The most recent as of today is the "-13" Jumbo Patch.
Regards,
Aronek
Standard disclaimer: I am an employee of Halcyon (www.HalcyonInc.com)
# 2
I have my account in groups: esadm,esdomadm,esops and ,esscrusers on the SMC server. Should there be something on the agent that needs to be changed? I thought it had to do with the security of snmp v2 that the agent uses to talk to the server
# 4
After a lot of trial and error I have found the following very easy and helpful to these security issues and server to client connections.
Apply the latest jumbo patch set on client and server
Rename the cfg dir (/var/opt/SUNWsymon/cfg)
Re-run es-setup and answer the questions "maintaining the correect seed"
Restart the agent then WAIT!!!!. It takes time to register the agent to the server. Not waiting will drive you nuts with incorrect errors.
Then add the agent obect in the console. For every agent I had problems with the above steps fixed.
