User manual

The OneCommand Manager User Manual Page 23
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 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 script starts this daemon, while the
stop_weblaunch stops it.
Starting the OneCommand Manager Application Web Launch Interface
After the OneCommand Manager application Web Launch Interface software is installed and the Web
Launch server is initialized, you can launch the OneCommand Manager application directly with your
Web browser.
To launch the OneCommand Manager application with your Web browser:
1. Open your web browser. Linux and Solaris users must log on as ‘root’.
2. Enter the URL of the ocmanager.jnlp file. Make sure that the URL specifies a remote server
which has the OneCommand Manager application Web Launch Interface software installed and
running.
http://IP_ADDR:PORT_NUM/ocmanager.jnlp
where IP_ADDR is the IP address of the host on which you installed the OneCommand Manager
Web Launch Service, and PORT_NUM is the TCP port number of the listening hosts' Web
server. If the port number is omitted, the default port 80 is used. The standard OneCommand
Manager application user interface is displayed.
Managing Files when Running the OneCommand Manager Application Web
Launch Interface
When running the OneCommand Manager application Web Launch Interface, all files (log files, driver
parameter files, firmware files, etc.) are located on the browser launch host, which is not necessarily the
same as the remote host that is specified in the Web Launch address.
Note: Only the OneCommand Manager application GUI is exported to the requesting client.
All adapter discovery and remote management operations are performed by
resources running on the remote host that served the GUI component. Therefore, the
SAN view displayed by the GUI is not from the client running the GUI, but rather from
the host from which this GUI was retrieved.