HP Systems Insight Manager 7.0 Command Line Interface Guide

</node-list>
NOTE: In this example, all three attribute lock flags are set to false so the PreferredNodeName
attribute will not be overwritten by the Discovery or Identification process.
Node proxy/management paths (MPO)
A node can have zero or more associated management paths. Node management paths (MPOs
- Management Path Objects) are created to assist WBEM CIMOM protocol identification as well
as other proxy type management. When dealing with CIMOMs and the other sources of
management data that may not come directly from a node itself, a proxy type MPO is added to
the node by identification. This MPO must be able to define and handle the WMI mapper and
SMI-S based CIMOMs as proxies to a storage device that does not support a network connection.
The MPO must also be able to support defining a path to obtain SNMP data for a server via an
iLO for cases in which a server is in a DMZ with the iLO on a management network.
The two types of MPOs that might reside on a node are a Management Agent (MAO) and a
Management Route (MRO).
An MAO defines and supports a management agent such as a CIMOM or SNMP agent. The MAO
contains information specific to accessing the agent, which includes attributes such as agent type,
port number, and the IP address by which it was accessed.
An MRO provides the information required to access an agent (MAO). An MRO always has an
associated MAO included in its overall information. An MRO on a node points to an MAO residing
on the same node, or another node.
The following sample XML list shows a node with one MAO and one MRO residing on the node.
A node's MPOs are included in the XML within the <managementpath-list> block. Within
this list block, each MPO is included in its own <managementpath> block, where an mpotype
attribute defines an MRO, MPO, or MAO type. The MRO in the following sample has an associated
MAO that resides on another system. Adding, modifying, or removing MPO data for a node is
available only through the mxnode CLI modify option which requires the MPO data to be provided
via XML input. See the mxnode(4) manpage for more information about using an XML file to add
or modify a node's MPO data.
<node-list>
<node name="abc" guid="..." host-name="..." monitoring="resume">
<hw-attribute name="DeviceType">Server</hw-attribute>
<sw-attribute name="PreferredNodeName">abc</sw-attribute>
<sw-attribute name="OverallStatus">NORMAL</sw-attribute>
<sw-attribute name="IPAddress">nn.nn.nnn.nn</sw-attribute>
<sw-attribute name="ProtocolSupport">WBEM:1.0</sw-attribute>
<sw-attribute name="ProtocolSupport">SNMP:1.0</sw-attribute>
<sw-attribute name="discovery.source">Ping</sw-attribute>
<sw-attribute name="DefaultProtoSettings">true</sw-attribute>
<sw-attribute name="DefaultAttributeSettings">true</sw-attribute>
<sw-attribute name="DefaultSystemName">true</sw-attribute>
<managementpath-list totalmpos="2">
<managementpath mpotype="MAO" mpoversion="1.0" maotype="WBEM_CIMOM"
location="OnThisNode">
<nodeguid>nn...nn</nodeguid>
<nodename>abc</nodename>
mxnode 75