Emulex OneCommand Manager Command Line Interface User Manual (P006980-01A Version 5.2, August 2011)

OneCommand Manager Command Line Interface User Manual Page 7
Starting and Stopping Linux and Solaris Daemon Processes
On Linux and Solaris machines, you can stop and start the OneCommand Manager daemon processes
using the "stop_ocmanager" and "start_ocmanager" scripts respectively. These are found in the
following OneCommand Manager installation directory:
Linux - /usr/sbin/ocmanager
Solaris - /opt/ELXocm
There are three basic daemon processes, included with OneCommand Manager installations, that are
affected by these scripts. They are:
• elxhbamgrd - Remote management daemon which services requests from OneCommand
Manager clients running on remote host machines.
• mili2d - MILI daemon that routes major portions of the local OneCommand Manager client CNA
management requests.
• elxdiscoveryd - Discovery daemon responsible for maintaining all discovery data (remote and
local) for OneCommand Manager clients running on the local machine.
elxhbamgrd and mili2d start at system boot time. elxdiscoveryd starts whenever the OneCommand
Manager GUI process first runs on the host machine.
Additionally if the web-launch component of OneCommand Manager is installed, the daemon process,
rmiserver, starts at system boot time. The start_weblaunch and stop_weblaunch scripts start and stop
this daemon.
Uninstalling the OneCommand Manager CLI
In Windows
To uninstall the OneCommand Manager CLI in Windows:
1. In Windows 2003: Select Start > Control Panel > Add/Remove Programs.
or
In Windows 2008 and Windows 2008 R2: Select Start > Control Panel > Programs > Uninstall
a Program.
2. If present, select Emulex Common SAN Management [version] and click Remove or
Uninstall. Click Yes. The Emulex Common SAN Management components are removed from
the system.
3. Select Emulex OCManager CLI [version] and click Remove or Uninstall. The uninstallation is
complete.
In a VMware ESX Server
To uninstall the OneCommand Manager CLI in a VMware server:
1. Log in as ‘root.’
2. Type: rpm -e elxocmcore-esxNN-<version>
Where NN is 40 for an ESX 4.0 system and 41 for an ESX 4.1 system.