
OneCommand™ Manager Application P007997-01A Rev. B
3. Starting and Stopping the OneCommand Manager Application
In Windows
31
3. Starting and Stopping the OneCommand
Manager Application
In Windows
To start the OneCommand Manager application, from the Windows desktop, select
Start>All Programs>Emulex>OCManager.
To stop the OneCommand Manager application, from the OneCommand Manager
application select File>Exit.
In Linux and Solaris
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 that 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 script starts
this daemon, while the stop_weblaunch stops it.
Kommentare zu diesen Handbüchern