zeealee wrote:If the local zone is "whole root" (as the script seems to imply) then there's no need to use any special steps to install in the zone (i.e. "es-setup -z"). Install the Agent the same way you would in the global zone (i.e. es-inst/es-setup or agent-update.bin).
I am trying to configure my non-global zones for Sun MC4.0 monitoring. The command es-setup -z (zonename) is giving me the following error
This option is not a valid for whole root zone.
Does anybody know the fix for this.
zeealee wrote:If your global zone and local zone are sharing the same CPUs (i.e. the zones have not been assigned to a dedicated CPU pool) then you will see the same graphs (since the CPUs are the same %-busy). To get "prstat -Z"-type numbers you need to look in the [Solaris Container Manager|http://www.sun.com/software/products/container_mgr] part of SunMC, or look at another tool like [Ops Center|http://wikis.sun.com/display/OC2dot5/Charts] for those metrics.
I have tried it. I have installed the SUN mc agent on the global zone and non-global zone. Everything seems to be fine but the issue that I am facing is that the graphs that I generate using SUN MC java console are all the same. That is if I graph the Global-zone or if I graph the non-global zones all of the graphs are the same. But if I use the prstat -z command I have different information. So, I am looking for a cure to create the correct and accurate graphs for my zones. Any ideas folks?