User's Guide

The OneCommand Manager User Manual Page 31
Figure 11: Discovery Information
Remote SAN Management Using TCP/IP Access Protocol
You can discover adapters on IPv4 and IPv6 TCP/IP hosts and on hosts configured to support the CIM
interface that have the OneCommand Manager application installed. Remote SAN management over
TCP/IP sends remote management requests using TCP/IP access protocol to remote hosts. TCP/IP
access enables you to access adapters via their host IP-address or by the name of the host on which
they reside. Since adapters can exist on a host, but not be a part of an FC network or are zoned on the
switch to be hidden to other adapters, they do not appear during normal FC discovery. Thus, TCP/IP
access enlarges the number of adapters that can be discovered and managed.
The principle differences between FC and TCP/IP access are:
• A TCP/IP host with or without an adapter installed does not need to connect to a fabric to
manage other hosts.
• A TCP/IP management host can manage all of the adapters in a remote host, not just the ones
connected to the same fabric. FC can only manage adapters connected to the same fabric.
• You can manage many more hosts since TCP/IP access is not constrained by the boundaries of
a fabric or zoning.
• True board status (e.g. link down) is available since the FC path is not necessary to send a
status request to the remote host.
• Adapter security in a TCP/IP environment is much more important since many more hosts are
available for management and TCP/IP access is not affected by fabrics or zoning.
• Discovery of hosts in a TCP/IP environment is not automatic like FC discovery. You must add
the hosts to be managed.
Note: In Windows, if you are running a firewall you may need to add the OneCommand
Manager application remote server to the firewall’s exception list. This remote
server’s path is:
\Program Files\Emulex\Util\Common\rmserver.exe
On an Itanium 64 host the path is:
\Program Files (x86)\Emulex\Util\Common\rmserver.exe