There are two main scenarios for using the agentcmd utility:
The command line syntax of agentcmd is:
For example, to get basic system information from an agent running on the server Solaris1, type the following command:
The agent will return output similar to the following:
SYSNAME=Solaris1 DOMAIN=myDomain.com ARCH="SunOS Solaris1 5.9 Generic_118558-03 sun4u sparc SUNW,Ultra-Enterprise" OSVER=5.9 NUMCPUS=4 MEMSIZE=1048576 PAGESIZE=8192 SWAPSIZE=1021624 GPGSLO=25 VXVM="" SDS="YES" HOSTID="808cf673" CPU0=" 0 - - 168 - UltraSPARC - " CPU1=" 1 - - 168 - UltraSPARC - " CPU4=" 4 - - 168 - UltraSPARC - " CPU5=" 5 - - 168 - UltraSPARC - " NET0=lo0=127.0.0.1 NET1=hme0=10.0.0.010
As with netcat, agentcmd is typically used in a script on the monitoring station to perform the following tasks:
The following example illustrates how to run agentcmd in an agent side script:
/usr/local/uptime4/scripts/agentcmd [-s/+s] -p [agent port] [agent hostname] rexec [password] [path]
If you use netcat in your scripts, see the following Knowledge Base articles for information on replacing netcat with agentcmd:
In 7.2 the agentcmd has extra logging enabled you are able to remove some of these logs by adding switches to the agentcmd command but the first line is always there:2013-09-19 12:50:03,704 -...
By: uptime Support | Date Created: 9-19-2013 | Last Modified: 3-15-2014 | Index: 600
The format of options for WMI based agent-less monitoring include the following fields in addition to the standard element fields: WMI Domain (optional) WMI Username WMI Password For example:...
By: uptime Support | Date Created: 9-25-2010 | Last Modified: 8-12-2011 | Index: 513
This article explains the DataStore export and import utilities.
By: uptime Support | Date Created: 2-13-2007 | Last Modified: 12-19-2012 | Index: 140