Dell Emulex Family of Adapters - Manual (Page 76)

OneCommand™ Manager Application P010066-01A Rev. A
3. Starting and Stopping the OneCommand Manager Application
Starting the OneCommand Manager Application Web Launch Interface
76
may be using the same port number causing a conflict between the MILI and the other
application. In this case, you can change the TCP/IP port number to run both OCM and
the other application on the same host.
The MILI TCP/IP port is changed by creating a file called "mili.conf". This file must be
created in the "/etc" directory on Linux and Solaris hosts and in the Window's
"System32" directory (%WINDIR%\System32) on Windows hosts.
In the mili.conf file, the first and only line of the file must have the following format:
MILI_TCP_PORT=xxxx
where xxxx is the port number (e.g. MILI_TCP_IP=27912). The port number must be in
the range between 1025 and 65535.
After creating the file or updating the port number in the file, the MILI daemon or
service must be restarted by rebooting the system for MILI to run on the new port
number.
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.
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.
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. 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.
3. 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 application 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.