Uninstall console and server components
Hi again,
Previous posts didn't quite answer this question. I need to remove the server and console portions of SMC from a machine since I decided to use a different machine for these functions. The es-unist script only seems to tackle removing the agent and the add ons. At no point did it ask me if I wanted to remove the server or console segments? I'd prefer to avoid having to uninstall everything and re-install the agent. Is the only other recourse to manually remove the server and console packages?
Many thanks,
[541 byte] By [
flgal3] at [2007-11-26 8:10:54]
# 1
Hi flgal3,
> Is the only other recourse to manually remove
> the server and console packages?
You could only start and use the Agent process if you wanted (es-start|stop -a), but to get the disk space back then yes, you'll have to perform an uninstall and reinstall. Note that as long as you _don't_ run the uninstall script with the "-X" flag it will leave your Agent config (modules, thresholds etc) intact so it gets picked up when you install again. You could also point the existing Agent to your new Server and use a config task to snapshot it if you're paranoid and want a second backup.
Regards,
Mike.Kirk@HalcyonInc.com
http://www.HalcyonInc.com
# 2
Hi Mike,
> You could
> also point the existing Agent to your new Server
I actually just tried to do this. But, I'm never asked the server confirmation question when I run the es-setup command on the old server. It seems that if the server modules are found, than the setup command assumes the local host will be the server. :-(
For now, I guess I'll just do as you suggest and shutdown all the non agent components. Eventually I will have to do the uninstall and install to prevent the server and console bits starting up on reboot.
Thank you.
# 3
> It seems that if the server modules are found, than the setup command
> assumes the local host will be the server. :-(
1) Stop all SunMC processes:
/opt/SUNWsymon/sbin/es-stop -A
2) Edit this file and change the trap and event sections so that their hostname/IP's point to your new Server:
/var/opt/SUNWsymon/cfg/domain-config.x
3) Run this command to generate new keys for your Agent:
/opt/SUNWsymon/sbin/es-run base-usm-seed.sh -s SEED -c agent
(replacing SEED with the seed value used with your new Server)
4) Start just the Agent:
/opt/SUNWsymon/sbin/es-start -a
5) Login to your new Server, make an icon for the Agent you just started, then double-click into it and disable/enable a random module to make sure the security is correct.
6) ...
7) Profit!
Regards,
Mike.Kirk@HalcyonInc.com
http://www.HalcyonInc.com
# 4
Your instructions did the trick! Thank you!
Also, moving /etc/rc3.d/S82es_server to /etc/rc3.d/s82es_server has worked nicely to prevent the start of the server components at boot time. It is a nice little bandaid until I can get around to uninstalling everything and re-installing the agent only components.
Thanks again.
