SunMC Agent on a V490

Hi,
today we got our first V490 with US- IV CPUs and I was wondering if I can install a SunMC Agent 3.5.1b on this platform. Obviously I'm not able to do so or I'm lacking the correct Config Reader package.
Can anybody tell me if there is a 3.5.1b supplement for a V490 (and V890) or is there no support within SunMC 3.5.1b?
Is a SunMC 3.6 agent installable and maybe usable with a SunMC 3.5.1b server?
Looking forward for any hints!
Regards,
Peter

Yes, the SunMC 3.5.1b media has the SunMC config-reader for the V490:
SUNWeswha Sun Management Center Workgroup Server Agent Support
Don't forget to make sure you also installed the Workgroup Server Server tier packages (Addon) on the SunMC server layer as well.
And a SunMC 3.6 server layer can support previous versions of the agents but not the other way around. The upgrade process is to start by upgrading your server layer, then console layer, and then over time at your leisure the agent layer.
Thanks,
Mike

Similar Messages

SunMC Agent 3.6.1 and ZFS

Hello,
I was wondering if a SunMC agent is able to recognize a ZFS filesystem? I've tried it on one of our test servers there is no category under Kernel Reader-Filesystem Usage for ZFS...only ufs and vxfs

I was wondering if a SunMC agent is able to recognize
a ZFS filesystem? I've tried it on one of our test
servers there is no category under Kernel
Reader-Filesystem Usage for ZFS...only ufs and vxfsNot quite yet. In fact a SunMC Server will refuse to even install on a ZFS partition without some minor changes to its setup utils. But the next release should be fully ZFS aware and compatible.
Regards,
[email protected]
http://www.HalcyonInc.com

Problem using agent-update.bin to roll out SunMC agents

Greetings,
I want to use agent-update.bin to roll out SUNMC agents to solaris 9 and 10 hosts. I use the es-agentupdate.sh tool to create the installation package and the seed file on the SunMC server in /var/opt/SUNWsymon/agentupdate.
I copy the binary /opt/SUNWsymon/base/bin/agent-update.bin to the root on a test server.
I run the following commands - each fails - unable to find the seed file. Can anyone suggest an -f argument which might work as I need the rollout to occur without user intervention to enter secrets.
./agent-update.bin -s oranc1 -r 8080 -p DPI_BasicAgent -f seed-file
or
./agent-update.bin -s oranc1 -r 8080 -p DPI_BasicAgent -f ./seed-file
or
./agent-update.bin -s oranc1 -r 8080 -p DPI_BasicAgent -f /var/opt/SUNWsymon/agentupdate/seed-file
Standard out from the last of these commands is as follows:
sbin_archive downloaded
SUNWessmu package installed
Running InstallClient : /tmp/agentupdate/DPI_BasicAgent/bin/sparc-sun-solaris/InstallClient -s oranc1 -p 8080 -u DPI_BasicAgent/upgrade-policy_sparc.xml -f /var/opt/SUNWsymon/agentupdate/seed-file
InstallClient started
upgrade policy downloaded
Argument file /var/opt/SUNWsymon/agentupdate/seed-file absent. Exiting...
Error: running InstallClient
Error: running InstallClient with error code 1
ERROR: information for "SUNWescom" was not found
ERROR: information for "SUNWescom" was not found
On the SUNMC server:
root@oranc1# pwd
/var/opt/SUNWsymon/agentupdate
root@oranc1# ls -l
total 6
drwxr-xr-x 4 root root 512 Feb 5 13:59 DPI_BasicAgent
-rw------- 1 root root 54 Nov 23 13:44 seed-file
drwxr-xr-x 4 root root 1024 Nov 23 12:46 SunMC36_Generic
I have also tried
-r-------- 1 root root 54 Nov 23 13:44 seed-file
Thanks in advance for your help
Tony

Greetings Mike,
I copied the seed-file from my SUNMC server to the host being updated and put it in the same directory as agent-update.bin. Ran the following:
./agent-update.bin -s oranc1 -r 8080 -p DPI_BasicAgent -s ./seed-file
The result is:
Error: getting sbin_archive
Web server is listening on port 8080 and accessible through a browser. Agent package directory name and seedfile name are OK.
any additonal help appreciated.
Regards
Tony

Time on SUNMC agents complicated!!! and interesting

Hi,
Some of our machines (SUNMC agents) are on a different timezone. Whenever I create graphs the time on the red spots is I dont know what. Any ides n how to change the time of the graphs according to what the time is on the agent. For example = the time on the agent is 3:00 am in the morning and the client or the java applet time is 1 pm than it shows 1 pm time rather showing me the agent time.
any fix?

I figured it out. The time showing up on the windows is the time of the machine running the java applet. So I fixed the time on the client running the applet and the time was fixed on the PRM window.

Does SunMC agent need SNMP packages

I'm configuring JASS (Security Toolkit) to run on newly jumpstarted machines and wanted to run the finish script: disable-snmp, but wasn't sure if SunMC needed to have these packages installed in order to run. I currently am at 3.0 but will be upgrading to 3.5. I have not run JASS on our current SunMC agents yet, but they do have these installed? How can I find out what packages SunMC needs?
SUNWsacom
SUNWmibii
SUNWsasnm
SUNWsasnx

I'm configuring JASS (Security Toolkit) to run on
newly jumpstarted machines and wanted to run the
finish script: disable-snmp, but wasn't sure if SunMC
needed to have these packages installed in order to
run. I currently am at 3.0 but will be upgrading to
3.5. I have not run JASS on our current SunMC agents
yet, but they do have these installed? How can I find
out what packages SunMC needs?SunMC 3.0 and 3.5 do not need any existing Solaris SNMP packages. SunMC comes with its own SNMP Agents (ps -ef | grep esd | grep agent). In fact most people disable the SNMP daemon that comes with current versions of Solaris ("snmpdx" process) and disable its start script (/etc/rc3.d/S76snmpdx) .. so that SunMC can take over the default SNMP port (161).
Are you removing packages for security reasons? Is your environment critical enough you cannot simply disable unused services (like snmpdx)?
Regards,
Aronek
Standard disclaimer: I am an employee of Halcyon (www.HalcyonInc.com)

Problems starting SunMC Agent 3.6 under Solaris 10

Hi folks,
I just did a test installation of the new SunMC 3.6 Server which worked fine. Afterwards, I did a fresh install of the 3.6 agent on a Sun Enterprise 420R running Solaris 10. I installed the agent in the global zone.
At the end of the setup, when the system asks me if I want to start the agent, which I affirmed. But this didn't work, system says just laconically "Could not start agent". Unfortunately, I can't even find the logs, since there is no log subdirectory under /var/opt/SUNWsymon. Have they moved this under Solaris 10?
Any ideas somebody how to dig into this?
Regards,
Peter

Hi Mike,
This sounds a lot like a post just a few days ago:
http://forum.sun.com/thread.jspa?threadID=27785&tstart=0Well, yes and no...I read this thread and I found some similarities but it's not the same problem. Besides, this was Solaris 8, I've 10 and my guess is that it has something to do with Sol10.
What do you see when you start the Agent with this command:
/opt/SUNWsymon/sbin/es-start -aiNo error...I end up in a prompt:
bash-3.00# /opt/SUNWsymon/sbin/es-start -ai
info Dec 05 17:48:19 agent Sun Management Center Version: 3.6, Build: 18, H491, (c) 2003 Sun Microsystems, Inc.
info Dec 05 17:48:19 agent registering import actions
info Dec 05 17:48:19 agent loading standard services
info Dec 05 17:48:19 agent standard services load complete
info Dec 05 17:48:19 agent agent host and port: cngaer:1161
info Dec 05 17:48:19 agent trap handler destination host and port: SunMC_server:162
info Dec 05 17:48:19 agent event trap destination host and port: SunMC_server:163
agent:>
I've really no idea what to enter at this prompt. A simple "help" doesn't give me anything but I got something from "ls"
agent:> ls
classes templates _config config services iso shadow contexts rules

SunMC agent core dump but has a limit of zero and wont actually core dump

Greetings,
Before I put a call in with Sun, I thought I would find if anyone else has a similiar problem. I have SunMC 3.5.1 running on a number of platforms and generally it is quite stable. I do have a number of SunFire 1280's (Netra T-12 to SunMC) each with 3 system boards with 96 GB of RAM. These systems are worked pretty hard and about every day or so, each agent on each system crashes. The problem is that there is a limit of zero for the agent core dump and it wont produce a core dump. Other processes dump with no problems. I gather they may be some limit in one of the SunMC config files but I don't know where to look. Without a core dump, it makes life hard to work out what causes it. I am only running the basic module monitoring so nothing else is loaded. If the basic module wont stay up, then why spend money to but in advanced monitoring????
Any info would be appreciated. I have worked with the fabulous Sun team regarding SunMC and I find months waiting for an answer somewhat frustrating.
Regards
Stephen

Hi Ian,
Thanks for the info. I will have a look at the patches. I noticed 3.5.1b has been released but as per usual, Sun does not really put much effort into saying what is good about it and why we should make the effort for upgrading. I could not wait to move from version 3 to 3.5 as it was so hard to manage patchwise.
One other thing that annoys me no end is the SunRay integration (/opt/SUNWut/sbin/utsunmc) alarms that appear. Once or twice, when I try to acknowledge the alarm, it just hangs. The event log says that I am trying to acknowledge an event that does not exist.
But then again, it has to be good because it does not cost anything other than time and the millions of dollars we spend on Sun equipment so we can use SunMC. That much money is better spend on hardware then on Tivoli right?? I think I can get a base model 25k for less than implementing Tivoli.
Regards
Stephen

(SunMC agent: Mx000)Insufficient security privilege to load console info!!!

I create a user "smcuser" on SMC server, it is in group "platadmn" and "dom0adm",
In SMC console, it can monitor a M4000 agent, but it cannot monitor M5000 agent.
PS: i have created "smcuser" on XSCF of M4000/M5000 server.
When i click "Platform View", there is a error info "Insufficient security privilege to load console info!!!"

This is usually caused by incorrectly seeding the agents or when a user does not have the appropriate access to the system.
Was the agent seeded with the same seed value used on the Sun MC server?
Is the smcid userid in the /var/opt/SUNWsymon/cfg/esuers file and part of the esadm group?
Can you create a esmaster user account in UNIX and try logging in using that userid. Note: this is the Sun MC superuser account.
regards,
bobby
www.HalcyonInc.com
forums.HalcyonInc.com

SunMC 3.6.1 Agent and zones

Hi folks,
I'm wondering how to handle zones with SunMC 3.6.1. We're planning to use zones in the future, mostly whole root zones. As far as I understood, I need to install the agent in the global zone and in the local zone afterwards. Is this correct?
Thanks in advance

1. How does the container manager link with SunMC.
Does monitor info go to the sunMC server ?SCM is one of the optional components you're prompted to add when you're installing SunMC Server and Agents. The way it works on the Server is that SCM adds an extra web interface, and it relies on the SunMC for host lists and a place to store it's data (i.e the graphs shown in the SCM web interface are actually coming from the SunMC Oracle database).
On the Agent side, all that happens when you say "y"es to SCM during install is that it adds a hidden module to the Agent that collects container/zone-type data, and can do the bidding of the SCM web interface (i.e. make/destroy Zones, alter CPU pools and container shares etc)
Do you only have to install the container manager
on the global zone ?Yes, it's only required for the SunMC Agent in each global zone. It's that Agent that can "see everything" about the containers and zones that are running.
Regards,
[email protected]
http://www.HalcyonInc.com

Problem getting krUFS values from SunMC 4.0 on Sunfire X2100

If I use the snmpget command to ask the SunMC agent for the krUFS oids I'm interested in (Mount point, SystemSize, PctUsedSpace), I get no error, but I get no data either (i.e. returned value is "" for all).
I'm able to get this data for T1000 and Sun Blade 2500's w/ no problem.

Hi Arutherford,
Arutherford wrote:
If I use the snmpget command to ask the SunMC agent for the krUFS oids I'm interested in (Mount point, SystemSize, PctUsedSpace), I get no error, but I get no data either (i.e. returned value is "" for all).
I'm able to get this data for T1000 and Sun Blade 2500's w/ no problem.So, you're getting numbers from SPARC systems, but not x86? Is it possible some of your systems have the "Kernel Reader" module and other have "Kernel Reader Simple" loaded? Or is the X2100 maybe using ZFS (which SunMC doesn't track, you'd need SystemMonitor)
Regards,
[email protected]
http://www.HalcyonInc.com

The Database of SunMc 4.0 didn't start, on Solaris 10 X86

Hello, happy new year, i am installing the three layers of SunMC 4.0 (server, agent and console), under Solaris 10 X86.
But, after setting the Web Server Security Key, the Web Server Port Selection, snmp Port,etc, the installation fails to start the DB used by the SunMC 4.0
This is the Log
The system memory to be compared has mapped to : 512
Skipping the Disable SNMP panel as a port other than 161 is specified as the agent port
The web server organization is given as : elektra
The web server location is given as : unefon
The Setup script will be executed as : /var/opt/SUNWsymon/install/guibased-setup.1199486648293.sh
SYMON_JAVAHOME is set to: /usr/java
JDK version is: "1.5.0_12-b04"
This script will help you to setup Sun Management Center 4.0.
Following layer[s] are installed:SERVER,AGENT,CONSOLE
None of the layers is setup.
Following layer[s] will get setup: SERVER,AGENT,CONSOLE.
Database will be setup.
Following Addon[s] are installed:
Advanced System Monitoring,Service Availability Manager,Performance Reporting Manager,Solaris Container Manager,System Reliability Manager,Generic X86/X64 Config Reader.
Checking memory available...
Configuring Sun Management Center DB...
Initializing SunMC database.
Successfully enabled service sunmc-database
Successfully disabled service sunmc-database
Initiating setup for Sun Management Center Server Component.
This part of the setup process does the Sun Management Center Server Component setup.
Creating the group esadm that contains Sun Management Center Admin Users.
Creating the group esdomadm that contains Sun Management Center Domain Admin Users.
Creating the group esops that contains Sun Management Center Operator Users.
You need to setup a user as a Sun Management Center administrator.
This person will be added to the esadm and esdomadm groups.
You must enter a valid username: : root
Generating server security keys.
Setting up web server...
An encrypted security key is needed for the Sun Management Center web server.
The key is generated based on the organization and location you provide.
Enter the name of your organization : : elektra
Enter the geographical location of this host : : unefon
Configure Sun Management Center web server port. Default port is 8080
Press RETURN to force default port.
Enter port you would like to use [ 1100 to 65535 ]: : 8080
The sunmcweb web application has been successfully deployed.
Using /var/opt/SUNWsymon/cfg/console-tools.cfg
/var/opt/SUNWsymon/cfg/tools-extension-j.x updated.
Starting Java Webstart based Sun Management Center
Java Console setup. This will take 2 minutes. Please wait...
Completing Sun Management Center Server Component setup.
Initiating setup for Sun Management Center Agent Component.
This part of the setup process does the Sun Management Center Agent Component setup.
Copying snmpd.conf file into /var/opt/SUNWsymon/cfg
Server component also installed locally.
Using this machine as the Sun Management Center server.
WARNING It appears that agent.snmpPort 161 is already in use.
Sun Management Center 4.0 agent may not be able to run due to this conflict.
There are two ways to correct this conflict:
1. Reconfigure the port that Sun Management Center 4.0 uses.
2. Stop the process that is using the port.
Press RETURN to force default port.
Enter port you would like to use [ 1100 to 65535 ]: : 1161
Updating /var/opt/SUNWsymon/cfg/domain-config.x with new port number.
Generating agent security keys.
PKCS11 Utilities package(SUNWcsl) was found.
Encrypted SNMP Communication is supported.
Setup of Agent component is successful.
**Starting Sun Management Center database setup...**
**verifyDatabaseDown: instance is not executing**
**Database consistency information missing.**
**Configuring database initialization parameter file**
**Stopping metadata component**
**Stopping cfgserver component**
**Stopping topology component**
**Stopping event component**
**Stopping grouping service**
**Stopping trap component**
**Stopping java server**
**Stopping webserver**
**Stopping agent component**
**Stopping platform component**
**Failed to enable service sunmc-database**
**Database setup failed : db-start failed**
**Updating registry...**
**As database is not setup, Marking server setup as failed in Registry.**
**None of the base layers are setup.**
**No Addon is setup.**
**Following Addons are not yet setup: Advanced System Monitoring,Service Availability Manager,Performance Reporting Manager,Solaris Container Manager,System Reliability Manager,Generic X86/X64 Config Reader**
**Could not finish requested task.**
**stty: : Invalid argument**
**stty: : Invalid argument**
**stty: : Invalid argument**
**stty: : Invalid argument**
**stty: : Invalid argument**
**opping agent component**
**Successfully disabled service sunmc-agent**
**Stopping platform component**
**Successfully disabled service sunmc-platform**
**verifyDatabaseDown: instance is not executing**
**Failed to enable service sunmc-database**
**Database setup failed : db-start failed**
**Updating registry...**
**As database is not setup, Marking server setup as failed in Registry.**
**None of the base layers are setup.**
**No Addon is setup.**
**Following Addons are not yet setup: Advanced System Monitoring,Service Availability Manager,Performance Reporting Manager,Solaris Container Manager,System Reliability Manager,Generic X86/X64 Config Reader**
**Could not finish requested task.**
The lay-out of my FileSystems is:
root@petersteiner install $ df -h
Filesystem size used avail capacity Mounted on
/dev/dsk/c0d0s0 4.2G 3.5G 721M 84% /
/devices 0K 0K 0K 0% /devices
ctfs 0K 0K 0K 0% /system/contract
proc 0K 0K 0K 0% /proc
mnttab 0K 0K 0K 0% /etc/mnttab
swap 780M 856K 779M 1% /etc/svc/volatile
objfs 0K 0K 0K 0% /system/object
/usr/lib/libc/libc_hwcap1.so.1
4.2G 3.5G 721M 84% /lib/libc.so.1
fd 0K 0K 0K 0% /dev/fd
swap 780M 396K 779M 1% /tmp
swap 779M 36K 779M 1% /var/run
/dev/dsk/c0d0s7 10G 10M 9.9G 1% /export/home
I hope, that someone can help me. pLZ

... and ... before running es-inst you have to add the PostgreSQL packages from the Solaris Media (5.10 U5 in my case)
Step order again:
- kill all postmaster processes (PostgreSQL Procs)
- if applicable svcadm disable all sunmc services
- /opt/SUNWsymon/sbin/es-uninst -X
- remove all SUNWpostgr* and SUNWpg* packages
- install these Packages - to be downloaded from http://www.sunfreeware.com/indexsparc10.html:
libgcc-3.4.6-sol10-sparc-local.gz , zlib-1.2.3-sol10-sparc-local.gz , readline-5.2-sol10-sparc-local.gz
or - the x64 respectively
- edit /etc/project to have this line for "default" : default:3::::project.max-shm-memory=(priv,2684354456,deny)
the value have to be calculated by one third of your physical memory.
- add the original postgreSQL packages from the Solaris install media :
SUNWpostgr-libs
SUNWpostgr
SUNWpostgr-contrib
SUNWpostgr-devel
SUNWpostgr-server-data
SUNWpostgr-server
SUNWpostgr-jdbc
SUNWpostgr-pl
SUNWpostgr-tcl
SUNWpostgr-docs
- run es-inst again from your install image path

Alarms not appearing for events - Agent Not Responding

Hi
I'm hoping someone may be able to help with a frustrating issue.
I have a setup with SunMC 4.0 monitoring approx 15 SunMC agents. The problem is some of these agents are not displaying alarms for events that occur.
E.g. if I trigger an alarm on a host by say filling up a filesystem, on some hosts an alarm will appear in the Alarm tab as exepcted, but on other hosts no alarm appears and hence I cannot acknowledge the alarm.
After doing a bit of digging I have found the following:
1) When the event is triggered on the client the trap is sent to the server
2) The server then tries to communicate with the agent on the client and I see this error in the event.log
[012578fd 0086 ]info Jul 28 14:59:06 event eventmgr: sending snmp collection request to XXXX 1161 XXXX for startline 0...................................................................
[012578ff 0098 ]error Jul 28 14:59:06 event eventmgr: event collection failed for XXXX 1161 XXXX line 0 - error {} {Agent Not Responding}.................................................
3) If I snoop between the 2 servers I can see communication between the server and the client on port 1161 so dont believe it is a network issue
4) I have tried uninstalling and reinstalling the agent. This strangely cured it on one server with the problem, but on another server the problem persists even after reinstalling the agent multiple times
5) I have logged into the postgress database and can see that events are not being logged in the events table (hence not being displayed in the Sun MC console).
6) I have tried reseeding the agent and that makes no difference
7) I have ensured the agent is listening on one network interface by adding snmpBindAnyAddr = "0" to the agent section of the domain-config.x file
I am not sure where else to look for pointers as to what is going on. What beats me is that the servers which the agents are running on all have identical builds built from jumpstart and are on the same network, yet some work and some dont!
Any help from anyone greatly received...
thanks

Hi there,
I found a solution to get the alarmflow going again:
1. Delete the node from SunMC Java Console
2. Stop the agent
3. Remove all logfiles in /var/opt/SUNWsymon/log
4. Start the agent
5. Wait 2 minutes and add the node in SunMC Java Console
After these steps I can see alarms coming through and when adjusting thresholds I can trigger new alarms which show up on the Hostview Alarms tab.
Unfortunately, this only seems to be a temporary solution, at least for some nodes.
Anyway, I figured I'd share this info with everyone. Maybe it will help with your investigation and if someone finds a permanent solution please feel free to post it here ;-)
Best Regards,
Emerald

Setting Agent timeout

Hi,
in one of my other posts, I mention solving most of my problems except for the fact that all my alarms have disappeared (eventManager problem?!)
and that some of my slower systems frequently timeout their SunMC agent even though it is all working fine. I think the default Agent timeout is too short for me.
It appears to be only a few seconds at most. I would like to be able to extend the timeout to about 15 or 20 seconds for the unresponsive systems. This seems
to be a magic number that never produces a false alarm for me.
So if such a value is possible, could I please be informed as how to set it? I figured it is yet another value in domain-config.x ?
If so, is there also a list of all the possible values that can be set in SunMC or at least this file?
Thanks!
rachel

bump - because "someone" must have done this in the past. Please assist! My system is running great except my
boss says "why is host x, y & z always failing? They're not - they just take longer than the default timeout to respond.
All I need is the magic timeout value and my world is good.
rachel

Managing Multiple SunFires on an agent system.

Greetings,
In a previous lifetime, I managed one 6800 from the SunMC server, but now, I am trying to manage multiple 6800's from an agent system. To give you an idea, I have the SunMC server that can communicate with a SunMC agent system that has a private network to the system controllers. If I add one Sunfire, I am able to look at it on the SunMC console. However, when I go through the drama of adding multiple system controllers on the agent system, things go pear shaped. I do an es-platform -a system controller a, b, c ,etc, etc. I then do the es-setup.sh -I a, b, c (in the right directory) , then do the es-start -y a, b, c, etc. etc..
When I add the platform to the SunMC server, I don't get a SunFire, I get a simple node. I cant see the platform components (Domains, etc).
I have read the doco but it lacks clear guidelines on how to do this at an agent level. Obviously, if I could attach straight to the system controllers from the SunMC management system, I doubt I would have these problems. Also at the agent level, it seems to lack some abilities, such as DR I think..
Should I keep mucking about with this agent idea or convince our network people to let me change the network so I have direct access to the system controllers from the SunMC server and to hell with those agents.
Or have I simply done something stupid?
Regards
Stephen

Good to hear its work'in. Were you using this doc as a reference?
http://docs.sun.com/app/docs/doc/817-3626
.. change that 817-3626 to 816-7381 .. and you are out of date.
IMHO, there should always be a static link to the latest.
Currently the web site default for SunMC docs takes you to 3.5 docs:
http://docs.sun.com/app/docs/coll/810.2
The 3.5 Update 1 list below is newer and more complete:
http://docs.sun.com/app/docs/coll/810.3
and has the bits from the latest collections.
Might as well note the remaining repos too, though there is not much there beyond release notes and docs on specific functionality added in those releases (Solaris 10 support and SCM):
810.5 (3.5 Update 1a Release Notes - Solaris 10)
810.6 (3.5 Update 1b Release Notes - SCM)
810.4 (Upcoming 3.6 doc placeholder)
iMac.

SunMC 3.6.1 : Install in cluster

Hi All,
Do you have an idea on how to install SunMC agent linked to a logical resource (resource in cluster) ?
Thanks for ideas and feedback !
Quentin.
Message was edited by:
Quentin_Savary

Hi Quentin,
Do you have an idea on how to install SunMC agent
linked to a logical resource (resource in cluster) ?I don't really know Cluster terminology that well. Do you mean you want a SunMC Agent to watched a clustered resource (i.e. tell you about failover etc?)
If so, then Sun Cluster comes with a module for SunMC:
http://docs.sun.com/app/docs/doc/819-0420/6n2rlnnag?a=view
It will let your Agents peek inside Cluster to see what's going on, and tell you when problems occur.
Regards,
[email protected]
http://www.HalcyonInc.com

SunMC Agent on a V490

Similar Messages

Maybe you are looking for