Dell Emulex Family of Adapters - Manual (Page 75)

OneCommand™ Manager Application P010066-01A Rev. A
3. Starting and Stopping the OneCommand Manager Application
In Windows
75
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. If Secure Management is enabled, you are
prompted for your user name and password. See “Using OneCommand Manager
Secure Management” on page 83 for more information.
To stop the OneCommand Manager application, from the OneCommand Manager
application menu bar 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
If Secure Management is enabled, you are prompted for your user name and password
when starting the OneCommand Manager application. See “Using OneCommand
Manager Secure Management” on page 83 for more information.
There are three basic daemon processes included with OneCommand Manager
application installations that are affected by these scripts. They are:

elxhbamgrd – Remote management daemon that services requests from
OneCommand Manager application 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 application clients running
on the local machine.
elxhbamgrd and mili2d start at system boot time. elxdiscoveryd starts whenever the
OneCommand Manager application GUI process first runs on the host machine.
Additionally, if the Web Launch component of OneCommand Manager application is
installed, the daemon process rmiserver starts at system boot time. The
start_weblaunch script starts this daemon, while the stop_weblaunch stops it.
Changing MILI TCP/IP Port
The MILI service/daemon listens on TCP/IP port number 4001 for requests from the
MILI library to service MILI commands. For some installations, another application