Upgradation of SMC Server

Dear All,

We are running a SMC server with version 3.5.1 in a Solaris 8 machine in our setup which is monitoring our more than 60-70 servers which are also running 3.5.1 agents. Now as because of some problems, we have to replace our Old SMC server to a new server.

Now my question is that if we will install Solaris 10 in the new Server and install from the scratch the same SMC server version 3.5.1 in this system, will it be compatible with all the other agents which was being monitored earlier by old Server, or what are we supposed to do to make it work.

The second question is that if I will install SMC server version 3.6 , will it be able to monitor agents with version 3.5..

And is it possible to install 3.5.1 on Solaris 10 machine.

Thanks in advance for your answers.

Message was edited by:

Sysops

[861 byte] By [Sysopsa] at [2007-11-26 22:34:35]
# 1

Hi Sysops,

> Now my question is that if we will install Solaris 10

> in the new Server and install from the scratch the

> same SMC server version 3.5.1 in this system, will it

> be compatible with all the other agents which was

> being monitored earlier by old Server, or what are we

> supposed to do to make it work.

Yes it will work. You es-backup your current config.. install SunMC 3.5.x on the Sol10 system, then es-restore into it. There's a couple extra steps if the IP will change, but it's covered in the migration guide:

http://www.sun.com/software/whitepapers/solaris9/sunmc_datamigration.pdf

> The second question is that if I will install SMC

> server version 3.6 , will it be able to monitor

> agents with version 3.5..

Yes, all SunMC Servers are backwards-compatible with all older Agents. Your Server could be 3.6.1 and the Agents 3.0 and it work fine.

> And is it possible to install 3.5.1 on Solaris 10 machine.

3.5.1b will work, but if you're going to upgrade I recommend you go straight to 3.6.1. It has better support for Solaris 10, and many fixes not present in 3.5.x or 3.6. Also, you can run a 3.6.1 SunMC Server inside a Sol10 whole-root local zone.... which makes it very convenient if you ever want to also use your new Sol10 box for other things... since SunMC is already happily walled off in it's own little partition. 3.5.x Servers won't install or run in a local zone.

You can also es-backup your 3.5.1 Sol8 system and upgrade it to 3.6.1 first if you want. That way you'll see that it is backwards compatible... then use the migration guide to put that 3.6.1 Sol8 Server on the Sol 10 box (or in a zone on it). Some customers prefer to do things in 2 stages like that... it's a bit more work... but you keep the upgrade and migration steps separate and distinct. It makes troubleshooting easier if things go wrong.

Regards,

Mike.Kirk@HalcyonInc.com

http://www.HalcyonInc.com

Aroneka at 2007-7-10 11:42:51 > top of Java-index,Administration Tools,Sun Management Center...
# 2

Hi,

Thanks for the reply. But one more doubt I have, This is a new machine whiere I will install 3.6.1 and as rest of the clinets are alreadu installed with 3.5.1 and was under monitoring initially with 3.5.1 server. So what are the changes I need to at the clinet side and at the server side if we will install frsh 3.6.1 without taking anybackup from old 3.5.1 server.

Thanks & regards,

Sysopsa at 2007-7-10 11:42:51 > top of Java-index,Administration Tools,Sun Management Center...
# 3

If the new machine has a different hostname than the old server, you'll have to edit every client to make sure to point to the new SunMC server. Otherwise you'll only get a read-only view of the clients on the SunMC Server.

We had problems with our 15K domains (3.5.1) when adding to a 3.6.1 server. Make sure you have all the supplements.

Quiksilvera at 2007-7-10 11:42:51 > top of Java-index,Administration Tools,Sun Management Center...