Home.... | log in.... | Pub my question! | Sign-up....
Java-index >> Administration Tools >> Sun Management Center

3.6.1 server compatible with 3.51b agent?

Can the new 3.6.1 server support the older agents? And is there any loss of functionality if older agents are used?
[122 byte] By [watweng] at [2007-11-26 8:32:30]
«« how to log out using BASIC authentication
»» Solaris 10 Jumpstart
# 1

In document 187-7958 write:

TABLE 4 1 Sun Management Center Prior Version Compatibility by Base Product

Console |Server| Agent

3.0 | 3.0|2.0.1, 2.1, 2.1.1, 3.0

3.5 | 3.5|2.0.1, 2.1, 2.1.1, 3.0, 3.5

3.6 | 3.6|2.0.1, 2.1, 2.1.1, 3.0, 3.5, 3.6

Uncompatable only server and consile layers.

ssergeyev at 2007-7-6 21:56:40 > top of Java-index,Administration Tools,Sun Management Center...
# 2
If you have a Sun Fire 10K 12K, 15K 20K or 25K in your server farm you have a problem when you install 3.6.1 on your server. The only solution sofar is installing 3.6.1 on the concerning system controllers and domains.
peternl at 2007-7-6 21:56:40 > top of Java-index,Administration Tools,Sun Management Center...
# 3
Do you have any more details on what kind of problem you get with those large servers running the 3.5 agents and a 3.6.1 console?-johnj
johnmclaughlin at 2007-7-6 21:56:40 > top of Java-index,Administration Tools,Sun Management Center...
# 4
The high end servers showed up as blue folders on the SunMC 3.6.1 console while showing up correctly on the 3.5.1 console.
Quiksilver at 2007-7-6 21:56:40 > top of Java-index,Administration Tools,Sun Management Center...
# 5
Does that happen with the "High End Systems" addon in the 3.6 SunMC Server? I also see that there is some Add-On Software for Legacy Sun Enterprise Servers - but that is for the 3000 to the 10000 Sun Enterprise Servers.-johnj
johnmclaughlin at 2007-7-6 21:56:40 > top of Java-index,Administration Tools,Sun Management Center...
# 6

Yes.

This is what we finally had as an answer from Sun:

[quote]

SunMC 3.6.1 server layers are backwards compatible all the way back to SunMC 3.0

agents. What is not compatible are version of modules. Specifically in your

case you had maybe Sun Fire Highend addon Version 4 installed (es-validate or

pkginfo -xc symon) and SunMC 3.6.1 comes with version 5. Note you did not have

upgrade SunMC to see this issue. You could have downloaded the v5 addon

separately on sun.com and installed it on the system controllers. The folder

would be blue until you updated the SunMC server layer with the same version of

the module.

You could file a documentation bug against the release notes. This issue is

never going to change. People normally never notice it. The issue that

triggered this change was the fact Sun re-released the sf12k/sf15k as the

e20k/e25k. So the module's family type need to be updated. Thus the blue

folder until you upgrade the SunMC server layer to match the system controllers.

It seems that you are in a unique situation.

Filing a bug or RFE against Release Notes or software will not be fixed.

[/quote]

We were quite disappointed because we had to upgrade our system controllers and domains now -_-

Quiksilver at 2007-7-6 21:56:40 > top of Java-index,Administration Tools,Sun Management Center...
Administration Tools
Sun Management Center

Administration Tools New Topic

Administration Tools Hot Topic

Administration Tools

All Classified