SunMC 3.6.1 and zones monitoring

Hi People.

I have just installed SunMC 3.6.1 on a test server. The installation included all add-on packages.

I have also configured a couple of zones on the server. One a sparsezone and the second a wholeroot zone.

Now here comes my question/concern.

I configured the modules for the host object, to include full kernel reader, and the likes. Only about 6 modules loaded.

I understand zones are being montiored under the Kernel > Zones container. But I dont seem to be able to set alarms for specifics. I want to be able to alarm when a zone is not in a running state. The attribute editor for all fields in the "zones" section under Kernel Reader does not allow or have available an alarms tab.

How do you monitor sparsezones then ?(ill come back to wholeroot in a moment...)

The Kenel Reader on the physical host seems pretty useless if you cannot configure aany items in the zones section. I mean why include it in the first place if thats the case ?

The SunMC agent can only be installed successfully into a wholeroot zone, and provide monitoring similar to that of a normal host. - Thats one work around to monitor this type of zone, but when you use sparsezones, SunMC doesnt seem to provide the monitoring one would require to know the state of their zones. I mean what happens If I have a zone that falls over, or reboots itself. I see feature to allow myself to monitor this level of detail, even though the fields relating to the state of the zone is present in the kernel reader.

If someone knows how to monitor your zones correctly with SunMC 3.6.1 I'd be really thankful to hear.

[1658 byte] By [katsal] at [2007-11-26 9:23:21]
# 1

HI

here is a procedure for installing the Agent in a subzone.

Install Agent in Global zone as usual.

# es-setup -z SubZoneName

# mkdir /../SubZoneName/root/opt/SUNWsymon

# tar cvf - /opt/SUNWsymon/ | (cd /.../SubZoneName/root; tar xvf -)

tip to help Find out which zones have SUNMC running.

# ps -eo zone,pid,ppid,time,args|grep esd

Warning: You can't easily remove the agents from the zones. If anyone knows a good way then let me know.

We've desided that we'll only do it when there is a spec procedure to monitor in the Server. Everything else should be monitored from the Global.

Have you solved the problem with monitoring the zone status?

kona_kunst at 2007-7-6 23:57:44 > top of Java-index,Administration Tools,Sun Management Center...
# 2

> Install Agent in Global zone as usual.

> # es-setup -z SubZoneName

> # mkdir /../SubZoneName/root/opt/SUNWsymon

> # tar cvf - /opt/SUNWsymon/ | (cd

> /.../SubZoneName/root; tar xvf -)

>

when you inherit /opt/SUNWsymon you can just do an es-setup in the local zone after the es-setup -z in the global zone.

to remove an agent after that you'll only have to do an es-uninst

Quiksilver at 2007-7-6 23:57:44 > top of Java-index,Administration Tools,Sun Management Center...
# 3
We have issued an rfe in which we asked for an alarm on the state of a zone.
peternl at 2007-7-6 23:57:44 > top of Java-index,Administration Tools,Sun Management Center...
# 4
Last status on this is that we have to install the Solaris Container Manager :-\ which to my opinion can only be a workaround but definitely no solution.
peternl at 2007-7-6 23:57:44 > top of Java-index,Administration Tools,Sun Management Center...
# 5
Have a look at the blog blogs.sun.com/stevewilson.This talks about an upcoming patch release which will allow the users to go configure zone state alarms.
achit at 2007-7-6 23:57:44 > top of Java-index,Administration Tools,Sun Management Center...