NAME
mxnode - add, modify, identify, remove, or list nodes in Systems
Insight Manager
SYNOPSIS
mxnode -a hostname(s)|ipaddress(es) [-w] Add and Identify node(s)
mxnode -a -f filename [-w] Add and Identify node(s)
from XML file
mxnode -a -m -f filename [-w] Add and/or Modify node(s)
from XML file
mxnode -m [-p] -f filename [-w] Modify and/or Identify
node(s) from XML file (accepts addition or modification of any/all MPO
data in XML)
mxnode -r nodename(s)|hostname(s)|ipaddress(es)Remove node(s)
mxnode -r -f filename Remove node(s) from XML
file
mxnode -ln [systemname(s)] List system name(s) from
the repository
mxnode -ld [systemname(s)] List system(s) from the
repository in detailed format
mxnode -lt [systemname(s)] List system(s) from the
repository in tabular format
mxnode -lf [systemname(s)] [-b encoding] List system(s) from the
repository in XML format
mxnode -lmpo [-b encoding] List system(s) from the
repository with any/all associated MPOs
DESCRIPTION
The mxnode command allows the user to add, modify, remove or list
systems in Systems Insight Manager.
When a system is added to the Systems Insight Manager repository with
the -a option, mxnode stores the system name, the fully-qualified
network hostname (if such a name exists), and an IP address as
attributes of the system.
Then the system will also be "identified",meaning that it will be
examined via the SNMP and/or the WBEM management protocols to
determine the device type, the operating system type and revision, and
other information needed to correctly determine which tools may be
appropriate to use with a given system. Like the system name,
hostname and IP address, the information collected during system
identification will also be stored in system attributes. Since it can
take some time to gather this information, it could take up to 30
seconds for a system to appear in a list results.
Successful system identification will depend upon system access
credentials which must be set prior to running mxnode. See
mxnodesecurity(1M) for details about how to specify system access
credentials.
Systems may be specified either on the command line or in XML
(filename may be either a file name or "-", which means the standard
input). The -a option requires either a hostname or an IP address,
since it has to do with systems that have not yet been added to the
Systems Insight Manager repository. Other options that operate on
systems that have already been added, such as -m, require the system
name rather than the hostname or IP address (though mxnode can look up
the system name if either the hostname or the IP address is provided
in XML input). One option, -r, requires that the system name be
explicitly specified, either on the command line or in XML, as a
safeguard to make sure that only the intended systems are removed.
The XML format is documented in mxnode(4). To see an example, enter
"mxnode -lf mysystem", substituting one of your system names for
"mysystem".
The -r option allows the user to remove a system from the Systems
Insight Manager repository. The system to be removed may be specified
by its system name, its hostname or IP address. Removing a system only
removes its context from the Systems Insight Manager repository. The
CMS itself cannot be remove, nor can non-empty container systems.
During the removal process, the system is removed from all Systems
Insight Manager system groups. All Systems Insight Manager
authorizations (see mxauth(1M)) for the system are also removed.
It is not an error to remove a system from the Systems Insight Manager
repository while an Systems Insight Manager task is running on the
system. The Systems Insight Manager does not terminate the task on the
system; task results and status are sent to the Systems Insight
Manager when the task completes.
As with adding, modifying or listing systems, systems may be specified
on the command line or in a file.
The -l* forms of this command allow Systems Insight Manager system
information to be listed. Specifying no options with this command
provides a listing of system names with no other information. This
listing is the same as the -l option with the n qualifier. The -l
option with the d qualifier provides a detailed screen-viewable
listing of the systems. The -l option with the t qualifier provides a
tabular listing of systems with detailed information. The -l option
with the mpo qualifier provides name listing of only those systems
that may have one or more associated MPOs (also known a Management
Path Objects, Management Paths or CIMOMs). Two types of MPOs may or
may not exist on a system. One type of MPO is a MAO, or Managment
Agent, and defines an actual Agent residing on the system. The other
MPO type is a MRO, or Management Route, which specifies the routing
information to an associated MAO, which may reside on this same system
or some other system. One or more MPOs may reside on a system. The
-l option with the f qualifier provides an XML listing of the systems.
When listing systems in the XML format, the user may optionally
specify the character encoding of the XML file. The value for the
character encoding must match a valid character encoding. If no
encoding is specified, the system attempts to write the file in the
encoding currently defined for the given system. The list of valid
character encodings is maintained at the following web site.
http://www.iana.org/assignments/character-sets
Only Systems Insight Manager full rights users may use mxnode to add,
modify or remove systems. Any Systems Insight Manager user may
display Systems Insight Manager system information.
The -m -f option allows the user to modify the attributes of an
existing system residing in he Systems Insight Manager repository.
The system attributes to be modified for a particular system(s) must
reside within a specified MxNode XML file. See mxnode(4) for details
and examples regarding the XML format, including (1) a list of all
valid pre-defined system attributes that may be modified and locked,
(2) information regarding setting of the 'suspend/resume monitoring'
feature via XML, and (3) information regarding the setting of the
'attributes lock' feature.
Pre-defined system attributes/properties
The following is the complete list of system attributes (or
properties) that are pre-defined and recognized by Systems Insight
Manager. Invoking mxnode with either the -ld or -lf options on a
particular existing system or node will allow you to view the current
values for some or all of the attributes shown below.
System name The system name is by default the same as the
hostname, if a hostname exists, or else the IP
address. The system name may be anything as long
as it is unique among all the systems in the
repository, and it may be changed.
Host name The hostname available from gethostbyname(1). It
may have embedded spaces and its maximum length is
16 characters. Hostnames are not case sensitive
and are represented internally as fully-qualified
names.
IP address The IP address corresponding to the hostname.
OS name This is the name of the operating system on the
managed system.
OS revision This is the revision level of the operating
system.
OS revision text
This is the operating system revision with
vendor-specific descriptive information.
OS vendor This is the operating system vendor.
Protocols These are the management protocols supported by
the managed system, with the revision level of
each protocol.
GUID The GUID is a unique identifier assigned to a
system in the repository.
Hardware device ID
The hardware device ID is another unique
identifier assigned to the hardware-specific
portion of a system in the repository.
Device type This is the major type of the device.
Device subtype This is a subtype of the device within the major
type.
Model This is the device model.
Added By This is the login of the Systems Insight Manager
user who added the system.
Added Date This is the date and time the system was added.
Preferred Node Name
This attribute defines an alternate system/node
name of your choosing which may make it easier for
you to identify, find or organize systems/nodes
residing in the Systems Insight Manager
repository.
System Description
This is a description of the system.
Serial Number This is the serial number of the system.
Asset Number This is the asset number of the system.
OS Description This is the description of the system's operating
system.
Contact This is the person to contact in case of system
maintenance.
Location This is the location where the system physically
resides.
System attributes that may be locked
The following is the complete list of system attributes (or
properties) that may be modified and locked via the 'mxnode -m -f
<filename>' command. Locking an attribute prevents that attribute
from being over written by any possible Discovery and Identification
processes. Note that the attribute name that's enclosed in
parenthesis is the actual attribute name that would be used in the
mxnode XML file.
As reference, these same attributes may be modified through the "Edit
System Properties" page of the Systems Insight Manager GUI. However,
note that there is some difference in the wording between the
attribute name as required in the XML file, and the attribute label as
displayed in the GUI. The following list may be used as a cross
reference:
XML Attribute Name GUI Attribute Label
PreferredNodeName Preferred display name:
DeviceType System type:
DeviceSubType System subtype:
Model Product model:
SysDescription Hardware description:
SerialNumber Serial number:
AssetNumber Asset number:
OSDescription Operating System description:
OSName Operating System for tool filtering:
OSRevision Operating System version:
Contact Contact:
Location Location:
Also note that system attributes are categorized into two distinct
groups, hardware and software attributes, and that when specifying an
attribute to be modified within an mxnode XML file, the correct
attribute modifier must be used.
For example, the Device Type attribute is considered a 'hardware'
attribute and would be specified as follows within the XML file by
using the 'hw-attribute' modifier.
<hw-attribute name="DeviceType">Device Type here</hw-attribute>
The OS Name is considered a 'sofware' attribute and would be specified
as follows within the XML file by using the 'sw-attribute' modifier.
<sw-attribute name="OSName">Your OS name here</sw-attribute>
Again, only the following system attributes may be locked:
Preferred Node Name (software attribute)
(PreferredNodeName) This attribute defines an
alternate system/node name of your choosing which
may make it easier for you to identify, find or
organize systems/nodes residing in the Systems
Insight Manager repository.
Device Type (hardware attribute)
(DeviceType) This attribute is the major type of
the device. Note that only the following pre-
defined valid device types may be used as values
for device type.
Unknown, Unmanaged, Server, Desktop, Workstation, Portable,
Router, Cluster, Printer, Switch, Hub, RAS, MgmtProc, Rack,
Enclosure, KVM, UPS, PDU, Env, Complex, Handheld, Partition,
PowerSupply, ThinClient, Storage.
Device Subtype (hardware attribute)
(DeviceSubType) This attribute is a subtype within the
device's major type. Note that only the following pre-
defined valid device subtypes may be used as values for a
device subtype.
None, PowerEnc, ServerEnc, HPVectra, HPNetServer, HPProLiant,
HPIntegrity, HPKayak, HPVisualize, VMGuest, NSCUW7, TCR_PS, Dell,
HPOmnibook, VMHost, MSCS, OVMS, TruCluster, RAC, HP Serviceguard.
Model (hardware attribute)
(Model) This attribute describes the device model. Any
displayable text may be used as a value for this attribute.
System Description (software attribute)
(SystemDescription) This attribute describes the device.
Any displayable text may be used as a value for this
attribute.
Serial Number (hardware attribute)
(SerialNumber) This attribute is the device's serial number.
Any displayable text may be used as a value for this
attribute.
Asset Number (software attribute)
(AssetNumber) This attribute is the device's asset number.
Any displayable text may be used as a value for this
attribute.
OS Description (software attribute)
(OSDescription) This attribute describes the device's
Operating System. Any displayable text may be used as a
value for this attribute.
OS Name (software attribute)
(OSName) This attribute defines the name of the Operating
System. Note that only the following pre-defined valid
values may be used as values for this attribute.
HPUX, WINNT, LINUX, NOVEL, Tru64.
OS Revision (software attribute)
(OSRevision) This attribute defined the Operating System
revision or version. Any displayable text may be used as a
value for this attribute.
Contact (software attribute)
(Contact) This attribute is used to define a contact person
for this device. Any displayable text may be used as a
value for this attribute.
Location (software attribute)
(Location) This attribute is used to define a physical
location for this device. Any displayable text may be used
as a value for this attribute.
In addition to the above predefined options, Systems Insight Manager
plug-in extension applications may define their own system attributes.
Options
mxnode recognizes the following options:
-a hostname(s)|ipaddress(es)
Indicates that one or more Systems Insight Manager
systems are to be added. The operand for this
option may be either a hostname or an IP address.
Hostnames may or may not be fully qualified, and
will be resolved internally by Systems Insight
Manager. Identification will also run.
-m systemname(s)
Indicates that one or more Systems Insight Manager
systems are to be modified and re-identified. The
operand for this option may be a system name, if
used in conjunction with -i, or an XML file name
must also be specified via -f. Note that this is
the only option that allows for any MPO data
residing within the XML to be recognized and
evaluated. MPO data evaluation within the XML is
not avaiable with the Add -a option as a system
must first exist before the MPO data associated
with a system can be added or modified.
-f filename Indicates that systems to be added, modified,
removed or listed are specified in filename. The
contents of this file are described in "XML
format", below.
-w The 'wait' option may be used when adding or
modifying nodes. If forces mxnode to wait until
the specified node(s) have been actually added to
the Systems Insight Manager's respository
(database). Note that the use of this option will
ensure that any subsequent operations related to
the node(s) just added will indeed be successful
as the node(s) are now guaranteed to be residing
in the respository. Also note that using the
'wait' option will cause the mxnode add or modify
operation to take up to several minutes or longer,
depending on the total number of nodes being
added, and thus the mxnode CLI will take longer to
return control to the user or caller.
-p The 'prune' option must be used in conjunction
with the -m option when it is desired to remove
one or more existing MPOs from a system via input
XML. Any system's existing MPO(s) that is omitted
from the XML MPO section will be removed from the
system, thus the pruning operation. When using
the -p prune option to remove MPOs, the command
line format and order is important and should look
as follows. -m -p -f xmlfilename
-l d systemname(s)
Displays a detailed listing of Systems Insight
Manager system attributes for the specified system
or all systems.
-l n systemname(s)
Displays a simple listing of Systems Insight
Manager system names for the specified system or
all systems.
-l t systemname(s)
Displays a tabular listing of Systems Insight
Manager system attributes for the specified system
or all systems.
-l mpo Displays a name listing of only those systems that
may have one or more associated MPOs (also known a
Management Path Objects, Management Paths or
CIMOMs). Two types of MPOs may or may not exist
on a system. One type of MPO is a MAO, or
Managment Agent, and defines an actual Agent
residing on the system. The other MPO type is a
MRO, or Management Route, which specifies the
routing information to an associated MAO, which
may reside on this same system or some other
system. One or more MPOs may reside on a system.
-l f systemname(s)
Displays an XML listing of Systems Insight Manager
system attributes for the specified system or all
systems. The output from this option produces a
format suitable for use as the contents of the
filename for the -f option. This format is
described in sections below.
-r Indicates that Systems Insight Manager systems are
to be removed.
-b encoding Specifies the character encoding of the XML file
when used in conjunction with the -lf option.
EXTERNAL INFLUENCES
For HP-UX or Linux, LANG determines the default encoding that the
system will use to output XML data if no encoding is specified on the
command line. If LANG is not specified or null or LANG does not
correspond to a recognized encoding, it defaults to C (see lang (5)).
In this case, the user should use the -b option to specify the desired
encoding of the XML data.
RETURN VALUE
mxnode returns one of the following values:
0 Successful completion.
1 Command line syntax error.
2 Error in a file operation.
3 Undefined system error.
5 Duplicate system error.
6 Nonexistent user error.
7 System is locked error.
8 Nonexistent system group error.
21 Invalid name.
31 Unknown network host.
33 Missing mxnode plug-in identification collector.
38 Undefined node name.
50 Unauthorized user.
102 Systems Insight Manager Repository error.
221 Authentication failure.
222 Central Management Server (CMS) is not
initialized.
224 System installation error.
249 Unable to connect to the session manager.
250 Remote exception.
252 File input parsing error.
253 Duplicate name.
254 Systems Insight Manager Properties file error.
EXAMPLES
This example indicates that the nodes defined in the file
"new_nodes.xml" are to be identified and added.
mxnode -a -f new_nodes.xml
The contents of the file "new_nodes.xml" might look like:
<?xml version="1.0" encoding="UTF-8"?>
<node-list>
<node name="abc" host-name="abc.mycompany.com" />
<node>
<sw-attribute name="IPAddress">192.1.1.1</sw-attribute>
</node>
<node name="maple" />
</node-list>
This example removes node "abc" from the repository.
mxnode -r abc
This example lists, in detailed format, all attributes for Systems
Insight Manager node "abc".
mxnode -ld abc
The output might look like the following:
Node name: abc
Host name: abc.mycompany.com
IP addresses: 192.1.2.3
OS name: HPUX
OS revision: 11.00
OS revision text: 11.00
OS vendor: HP
Protocols: SNMP:1.0
GUID: 00000000864162de0f07e31d86c00000
Hardware device ID: 00000000864162de0f07e31d86b00000
Device type: UnixWorkstation
Device subtype: HP9000
Model: 9000/785
Added by: root
Added on: Sep 24, 2002 4:15:46 PM
Monitoring: Not suspended
OS description:
Preferred node name: LABabc
System description: Hardware: x86 Family
Contact: ph: 555-1234
Location: Bldg 6,Room123
Attributes locked: No
This example lists, in a tabular format, a subset of Systems Insight
Manager node attributes for all nodes in the repository.
mxnode -lt
The output might look like the following:
NAME HOST NAME OS NAME ADDED ON IP
ADDRESSES
abc abc.mycompany.com HPUX Sep 24, 2002 4:15:46 PM 192.1.2.3
verde verde.mycompany.com Linux Sep 24, 2002 4:15:47 PM
192.1.2.4
This example lists a node in XML format:
mxnode -lf abc
The output might look like the following:
<?xml version="1.0" encoding="UTF-8"?>
<node-list>
<node name="abc" guid="..." host-name="abc.mycompany.com">
<hw-attribute name="DeviceType">UnixWorkstation</hw-attribute>
<hw-attribute name="DeviceSubType">HP9000</hw-attribute>
<hw-attribute name="Model">9000/785</hw-attribute>
<hw-attribute name="ProcessorFamily">pa-risc</hw-attribute>
<sw-attribute name="OSName">HPUX</sw-attribute>
<sw-attribute name="OSVendor">HP</sw-attribute>
<sw-attribute name="OSRevision">11.00</sw-attribute>
<sw-attribute name="IPAddress">192.1.2.3</sw-attribute>
<sw-attribute name="ProtocolSupport">SNMP:1.0</sw-attribute>
<sw-attribute name="Description">HP-UX phoenix</sw-attribute>
<sw-attribute name="SystemName">abc.mycompany.com</sw-attribute>
<managementpath-list />
</node>
</node-list>
The following example lists a node in XML format and includes all
pre-defined system attributes for reference, including those that may
be modified and/or locked. One method for modifying a particular
system/node would be to use the 'mxnode -lf >filename' command to
output the XML data to an external output file. The output file could
then be manually edited so as to change/add those attributes that need
to be modified and/or locked. After the file is edited, then use the
'mxnode -m -f <filename>' command to actually modify the system/node,
specifying the file just edited as the input file for the command.
Note that the XML below also includes the method for locking those
attributes that are lockable. If the desire is to keep certain
attributes from being over-written (locked) by the Discovery or
Identification process, then ALL THREE of the attribute lock flags
(see example XML) must be set to a 'false' value, as shown below.
Else, all three attributes must be set to 'true'.
<sw-attribute name="DefaultProtoSettings">false</sw-attribute>
<sw-attribute name="DefaultAttributeSettings">false</sw-attribute>
<sw-attribute name="DefaultSystemName">false</sw-attribute>
As reference, these same three attribute lock flags may be modified
through the "Edit System Properties" page of the Systems Insight
Manager GUI. Checking or Unchecking the the "Prevent the Discovery
and Identification processes from changing these system attributes"
checkbox is the same as setting the three attribute lock flags to
either true or false. Checking the checkbox is the same as setting
all 3 flags to 'false'. Unchecking the checkbox is the same as
setting all 3 flags to 'true'.
Note that the XML also includes the 'monitoring' feature attribute
within the node element. This feature allows the user to control the
monitoring of the system/node by Systems Insight Manager. In normal
operation, the system is continously monitored (includes Discovery and
Identification) by Systems Insight Manager. Monitoring of the system
may be suspended for a pre-defined time value, or monitoring may be
suspended indefinately. If the 'monitoring' attribute is not included
in the XML file for a '-m -f' command, then the current monitoring
state for the node is left as is.
As reference, this same 'monitoring' feature may be modified through
the "Suspend/Resume Monitoring" page of the Systems Insight Manager
GUI.
Valid values for the 'monitoring' attribute are as follows.
monitoring="resume" Do not suspend monitoring
monitoring="suspend" Suspend monitoring indefinitely
monitoring="suspend.5m" Suspend monitoring for 5 minutes
monitoring="suspend.15m" Suspend monitoring for 15 minutes
monitoring="suspend.1h" Suspend monitoring for 1 hour
monitoring="suspend.1d" Suspend monitoring for 1 day
For your reference, all attributes that may be modified and locked are
prepended (marked) with an 'L'. Those attributes that may be modified
and locked, but require a pre-defined value are marked with an
asterisk character. See preceding sections that list the valid values
for the 'DeviceType', 'Device Subtype' and 'OS Name' attributes. And
again, be aware of those attributes that are categorized as hardware
versus software attributes. The three attribute lock flags are
prepended with an 'LF' marker.
Sample XML file showing all system attribute formats and syntax:
<?xml version="1.0" encoding="windows-1252"?>
<node-list>
<node name="systemName" host-name="hostName" monitoring="resume">
L* <hw-attribute name="DeviceType">your data here</hw-attribute>
L* <hw-attribute name="DeviceSubType">your data here</hw-attribute>
L <hw-attribute name="Model">your data here</hw-attribute>
L <hw-attribute name="SerialNumber">your data here</hw-attribute>
<hw-attribute name="OverallStatus">10</hw-attribute>
<hw-attribute name="ProductID">12345</hw-attribute>
L* <sw-attribute name="OSName">your data here</sw-attribute>
L <sw-attribute name="OSRevision">your data here</sw-attribute>
<sw-attribute name="OSRevisionText">info here</sw-attribute>
<sw-attribute name="TrustStatus">false</sw-attribute>
L <sw-attribute name="AssetNumber">your data here</sw-attribute>
L <sw-attribute name="Contact">your data here</sw-attribute>
L <sw-attribute name="Location">your data here</sw-attribute>
L <sw-attribute name="PreferredNodeName">your data here</sw-attribute>
L <sw-attribute name="SysDescription">your data here</sw-attribute>
L <sw-attribute name="OSDescription">your data here</sw-attribute>
<sw-attribute name="OSNameStr">OS name str</sw-attribute>
<sw-attribute name="OSVendor">OS vendor info</sw-attribute>
<sw-attribute name="IPAddress">0.0.0.0</sw-attribute>
<sw-attribute name="ProtocolSupport">SNMP:1.0</sw-attribute>
<sw-attribute name="discovery.source">Ping</sw-attribute>
LF <sw-attribute name="DefaultProtoSettings">false</sw-attribute>
LF <sw-attribute name="DefaultAttributeSettings">false</sw-attribute>
LF <sw-attribute name="DefaultSystemName">false</sw-attribute>
<managementpath-list />
</node>
</node-list>
As an example, let's say you wanted to change the 'PreferredNodeName'
attribute for a particular system/node via the mxnode CLI. You want
to change the system name from "abc" to "LABabc" to signify that this
system is a Lab system. You would first dump the XML for the node via
a 'mxnode -lf >filename' command. You could then manually edit the
output file. You could either leave all the current attributes as is
in the file, or remove all attributes except for the
'PreferredNodeName' attribute (if it does not exist, you will need to
add it). The following example shows what the XML file could look
like if you wanted to change the PreferredNodeName attribute for node
abc. You could then use the XML file as the input for the 'mxnode -m
-f filename' node modify command. Note that the example XML also has
set all 3 attribute lock flags to 'false' as we want the
PreferredNodeName attribute to not be over written by the Discovery or
Identification process. This same process could be used to change any
of the other attributes, or change and lock any of the lockable
attributes.
<?xml version="1.0" encoding="windows-1252"?>
<node-list>
<node name="abc">
<sw-attribute name="PreferredNodeName">LABabc</sw-attribute>
<sw-attribute name="DefaultProtoSettings">false</sw-attribute>
<sw-attribute name="DefaultAttributeSettings">false</sw-attribute>
<sw-attribute name="DefaultSystemName">false</sw-attribute>
<managementpath-list />
</node>
</node-list>
NODE PROXY/MANAGEMENT PATHS (MPO)
A node may have zero or more management paths associated with it.
Node management paths (MPOs - Management Path Objects) are created to
assist WBEM CIMOM protocol identification as well as other 'proxy'
type based 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 will be 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 where a server is
in a DMZ with the iLO on a managment network.
The two types of MPOs that may possibly reside on a node are a
Managment Agent (MAO), and Management Route (MRO).
The purpose of the MAO is to define and support a management agent
such as a CIMOM on SNMP agent. The MAO contains information specific
to accessing the agent, which includes attributes such as agent type,
port number and IP address by which it was accessed.
The purpose of the MRO is to provide information required to access an
agent (MAO). An MRO will always have an associated MAO included
within its overall information. A MRO residing on a given node will
either point to a MAO residing on the same node, or may point to a MAO
residing on some other node.
MPO = Management Path Object
MRO = Management Route Object
MAO = Management Agent Object
The following example XML listing shows a node with one MAO and one
MRO residing on the node. A node's MPOs will be included in the XML
within the <managementpath-list> block. Within this list block, each
MPO will be included in its own <managementpath> block, whereby a
'mpotype' atribute will define either a MRO type MPO, or a MAO type
MPO. Note that the MRO in the following sample XML has an associated
MAO that resides on some other system.
Note that adding, modifying or removing MPO data for a given node is
available only via the mxnode CLI 'modify' option whereby the MPO data
is provided via XML input. See the "mxnode(4)" manpage for more
details regarding adding or modifying MPO data for a given node via
XML.
<?xml version="1.0" encoding="windows-1252"?>
<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>
<proxytype>WBEM_CIMOM</proxytype>
<portnumber>nnnn</portnumber>
<ipaddress>nn.nn.nnn.nn</ipaddress>
<protocol>https</protocol>
<maoluid>nnnnnnnnnnn</maoluid>
<interopnamespace>interop</interopnamespace>
<profilelist>
<profilename>Array</profilename>
<profilename>Server</profilename>
</profilelist>
<functionalprofilelist>
<profilename>Basic Read</profilename>
<profilename>Basic Write</profilename>
</functionalprofilelist>
</managementpath>
<managementpath mpotype="MRO" mpoversion="1.0">
<catagoryname>hpmxCimomMro</catagoryname>
<mroluid>nnnnnnnnnnn</mroluid>
<profilelist>
<profilename>Switch</profilename>
</profilelist>
<namespace>root</namespace>
<cimcspath>....</cimcspath>
<associatedmaoguid>nn...nn</associatedmaoguid>
<associatedmaoluid>nnnnnnnnnnn</associatedmaoluid>
<managementagent mpotype="MAO" maotype="WBEM_CIMOM" location="OnOtherNode">
<nodeguid>nn...nn</nodeguid>
<nodename>dpiwin5</nodename>
<proxytype>WBEM_CIMOM</proxytype>
<portnumber>nnnn</portnumber>
<ipaddress>nn.nn.nnn.nn</ipaddress>
<protocol>https</protocol>
<maoluid>nnnnnnnnnnn</maoluid>
<interopnamespace>interop</interopnamespace>
<profilelist />
<functionalprofilelist />
</managementagent>
</managementpath>
</managementpath-list>
</node>
</node-list>
NOTES
(1) When modifying a node via the -m -f <filename> command, you only
need to include those attributes that you wish to modify within the
XML file. However, you must always include the 3 attribute lock flags
and set all 3 attribute lock flags to either 'true' or 'false'. Most
likely, you'll want the latter setting (false) so that the lockable
attributes will not be over written whenever the Discovery and
Identification processes run on the particular system/node.
(2) The only way to clear a particular system/node attribute using the
mxnode -m -f <filename> command, is to include that attribute in the
XML file and provide a value for that attribute of 1 space character.
(3) Although any system/node attribute may be modified via an XML
file, only a limited set of all pre-defined system attributes may be
additionally locked or protected from being over written by the
Discovery or Identification processes. See preceding documentation for
a complete list of those system attributes that may be modified AND
locked.
LIMITATIONS
This command may only be run on the CMS.
FILE PROCESSING
If Systems Insight Manager detects a formatting error while processing
an input file, the Systems Insight Manager will not make any changes
to the Systems Insight Manager domain based on the input file. Systems
Insight Manager will interrupt processing and issue an error message
describing the formatting error.
AUTHOR
mxnode was developed by the Hewlett-Packard Company.
SEE ALSO for HP-UX
mxnode(8).
SEE ALSO for Linux
mxnode(4).
SEE ALSO for HP-UX
mxngroup(1M), mxauth(1M), mxuser(1M), mxinitconfig(1M),
mxnodesecurity(1M), mxnode(4).
SEE ALSO for Linux
mxngroup(8), mxauth(8), mxuser(8), mxinitconfig(8), mxnodesecurity(8),
mxnode(8).