Advertisements

Category Archives: HP Server Automation

Installing HP Server Automation client for Solaris

Installing HP Server Automation client for Solaris. For Solaris I included the flag –withrpm to have installation of software from Opsware enabled

root@solaris:/tmp # ./opsware-agent-34c.0.0.135-solaris-5.10 -s -o -c –loglevel info –logfile /var/tmp/log.txt –withrpm –opsw_gw_addr_list 148.95.133.132:3001 –force_new_device

[INFO] Log started.

[WARN] The command-line parameter –clean has been deprecated.
Will check the gateway list for connectivity
[INFO] Opsware Gateway (148.95.133.132:3001) available at ‘148.95.133.132:3001’.

[INFO] legacy config file ‘/var/lc/cogbot/etc/cogbot.args’ not found – skipping force –withrpm check.

UnZipSFX 5.42 of 14 January 2001, by Info-ZIP (Zip-Bugs@lists.wku.edu).
inflating: /tmp/~7119-1.WRK/opsware-agent
inflating: /tmp/~7119-1.WRK/opsware-agent-installer.py
creating: /tmp/~7119-1.WRK/crypto/agent/
inflating: /tmp/~7119-1.WRK/crypto/agent/agent.srv
inflating: /tmp/~7119-1.WRK/README
inflating: /tmp/~7119-1.WRK/install_opswagentrpm.sh
inflating: /tmp/~7119-1.WRK/install_rpm.sh
inflating: /tmp/~7119-1.WRK/install_syncbot.sh
inflating: /tmp/~7119-1.WRK/ISMsyncb0.pkg
inflating: /tmp/~7119-1.WRK/OPSWrpm-32h.0.0.2-1.pkg
inflating: /tmp/~7119-1.WRK/opswagentrpm.rpm
inflating: /tmp/~7119-1.WRK/opswagentrpm.sun4us.rpm

[INFO] Installing Opsware agent into ‘/opt/opsware/agent’.

[INFO] Agent uninstaller script copied successfully.

[INFO] Installation completed successfully.

[INFO] Checking for restorations at ‘/tmp/~7119-1.WRK/cog_extension’

[INFO] Registering server with the Opsware core.

[INFO] Writing no_full_hw_reg_requested file: /var/opt/opsware/agent/no_full_hw_reg_requested

[INFO] Successfully created no_full_hw_reg_requested file: /var/opt/opsware/agent/no_full_hw_reg_requested
INFO: Startup of initial hardware registration at ’05/26/10 11:09:59′
INFO: No crypto found, using bootstrap crypto.
TRACE: bootstrap crypto path: /var/opt/opsware/crypto/agent/bootstrap
TRACE: copy /var/opt/opsware/crypto/agent/bootstrap/agent.srv to /var/opt/opsware/crypto/agent/agent.srv
TRACE: flushing the certmaster cache
INFO: Checking with spin to see about clearing mid and/or crypto…
TRACE: check that ‘/etc/opt/opsware/agent/mid’ exists: 0
INFO: no mid file was found at: ‘/etc/opt/opsware/agent/mid’ assuming new install.
TRACE: bootstrap crypto path: /var/opt/opsware/crypto/agent/bootstrap
TRACE: remove: /var/opt/opsware/crypto/agent/agent.srv
TRACE: copy /var/opt/opsware/crypto/agent/bootstrap/agent.srv to /var/opt/opsware/crypto/agent/agent.srv
TRACE: flushing the certmaster cache
INFO: Initially registering hardware and operating system information…
Retrieved Machine ID is null.
Chassis ID: 847e3198
TRACE: Connecting to ‘https://spin:1004/spinrpc.py’…
Opsware machine ID : ‘415820499’
Received ‘agent-ca.crt’.
Received ‘opsware-ca.crt’.
Received ‘cogbot.srv’.
Storing ‘cogbot.srv’ contents as ‘agent.srv’
Received ‘admin-ca.crt’.

[INFO] Minimal server registration completed successfully.

[INFO] Registering Opsware agent with the Opsware core.

[INFO] Writing no_sw_reg_requested file: /var/opt/opsware/agent/no_sw_reg_requested

[INFO] Successfully created no_sw_reg_requested file: /var/opt/opsware/agent/no_sw_reg_requested

[INFO] Writing do_check_reachability file: /var/opt/opsware/agent/do_check_reachability

[INFO] Successfully created do_check_reachability file: /var/opt/opsware/agent/do_check_reachability

[INFO] Starting Opsware agent.
Starting agent
Daemonbot: Wed May 26 11:10:01 2010: Looks like nothing is listening on :1002
Daemonbot: Wed May 26 11:10:01 2010: Daemonbot confirms that nothing is listening on :1002
Daemonbot: Wed May 26 11:10:01 2010: Daemonbot will try and start a new shadowbot…
Daemonbot: Wed May 26 11:10:01 2010: Starting /opt/opsware/agent/pylibs/shadowbot/daemonbot.pyc…
Daemonbot: Wed May 26 11:10:01 2010: pidpath /var/opt/opsware/agent
Daemonbot: Wed May 26 11:10:01 2010: logpath /var/log/opsware/agent
Daemonbot: Wed May 26 11:10:01 2010: ports [‘1002’]
Daemonbot: Wed May 26 11:10:01 2010: Started process group 7160

[INFO] Opsware agent started.

[INFO] Log ended.

Advertisements

Checking which satellite HP SA is pointing to

To check which satellite the HP Server Automation (formely known as Opsware) is pointing to, check the file /etc/opt/opsware/agent/opswgw.args

root@solaris:/ # cat /etc/opt/opsware/agent/opswgw.args
opswgw.gw_list: 164.56.164.222:3001,164.56.164.221:3001

This server is pointing to two satellites

%d bloggers like this: