Avocent MERGEPOINT 53XX SP MANAGER, Installer/User Manual

Page: 87 / 204

73
C H A P T E R
5
Accessing Target Devices Using
DirectCommand or Native IP
You can connect directly to native applications on the target device through either the
DirectCommand or the Native IP features. These applications are proprietary interfaces or
command lines provided by the service processor vendor; examples include HP InSight, IBM
Director and Dell Open Manage
®
.
With DirectCommand, users can gain access to native applications, integrated web servers and
other proprietary interfaces that are available over TCP/IP. You can use the MergePoint web
interface to launch a browser, vKVM or virtual media (vMedia) session on a service processor.
DirectCommand only provides native access to pre-defined TCP ports on a service processor through
a mapped local address. Alternatively, Native IP (MergePoint SP5324/SP5340 appliances only)
allows access to native applications using the native IP address of the service processor. Once
enabled and configured, Native IP allows external user traffic to selectively pass through the
MergePoint SP5324/SP5340 appliance and directly connect to a service processor on the internal
server network. To configure Native IP, enable Selective mode, which creates an open trust, or define
Native IP trusts with specific IP addresses that are permitted to establish Native IP connections.
Examples of cases where Native IP should be used instead of DirectCommand:
• If you want an application like HP Systems Insight Manager (SIM) or IBM Director to connect
to the native IP address of a service processor connected to the MergePoint SP5324/SP5340
appliance, use Native IP. The Native IP feature allows access to the related programmatic
interface and network protocols, where as DirectCommand only allows interaction with the
configured TCP ports of a service processor through a mapped local loopback address (such as
127.x.x.x).
• If you want to expose SNMP traps coming from a service processor to an SNMP trap agent on
the user network, so that they can be collected directly by the SNMP agent, use Native IP. This
applies to any other network protocol that needs to selectively pass to/from the service
processor, through the MergePoint SP5324/SP5340 appliance, and to/from trusted hosts in the
user network. Another example of this type of protocol is Active Directory (AD), which may
be needed if you want to authenticate iLOs with AD credentials instead of with local
credentials.
• If you want to provide direct user access to a service processor that has hard-coded IP
addresses, use Native IP. (DirectCommand would automatically translate the hard-coded IP
address to a local loopback address, which would prevent a successful connection).