HP Systems Insight Manager 7.0 Command Line Interface Guide

• The –n product-name option specifies the product name of the product you want to add. For
example, HP rx1600 is a product name.
• The –p protocol option selects the protocol to use for data collection, and should be set to
SNMP.
• The –x option provides the definitions for one or more attributes for the system. Examples of
SNMP attributes are the system OID, product type, product subtype, and operating system
name.
The second form of the add command enables you to provide the system type definitions in XML
format. In the example above, the –f stmfile.xml command tells Systems Insight Manager to get the
system type definitions from the file stmfile.xml. For a complete description of the required
XML format, see the file /opt/mx/dtd/stmrules.dtd.
To remove system type definitions, use one of the following commands:
# mxstm –r –n product-name
# mxstm –r –f stmdel.xml
The first command removes the system type with the product name product-name. The second
command removes all of the system types defined in the XML file stmdel.xml.
To see a listing of existing system type definitions, use one of the following commands:
# mxstm –l [–n product-name]
# mxstm –l –f stmout.xml
The first command lists all of the product names for all of the system type definitions in Systems
Insight Manager. The –n product-name option displays the full definition of the product
product-name, and other information such as protocol, OID data, product type, and vendor. The
second command produces the full definition for every system type in Systems Insight Manager in
XML format, saving the data in the file stmout.xml.
Managing collections
Systems Insight Manager enables you to create groupings of systems or events called collections.
Each collection is a query into the Systems Insight Manager database. Systems Insight Manager
users can create two types of collections, shared collections and private collections. Share collections
are available to all Systems Insight Manager users. Private collections are only to the user who
created the collection. Collections enable you to define a hierarchical organization of collections.
For example, the following hierarchy exists in the Systems Insight Manager predefined collections:
Systems
Private
Shared
Systems by Operating System
HP-UX
Microsoft Windows Server 2003
The items Systems, Shared, and Systems by Operating System are collections that contain other
collections as their members. The items HP-UX and Windows Server 2003 are also collections,
but they also define a query that is performed on the Systems Insight Manager database. In this
section, the term query collection will be used to refer to collections that define a query on the
Systems Insight Manager database.
The mxcollection command enables you to add, modify, remove, or list collections, or members
within a collection in Systems Insight Manager. A full description for mxcollection exists in the
mxcollection man page, and a full description of the XML syntax required to manage collections
through an XML file exists in the mxcollection(4) man page. Use the mxquery command to
add, modify, list, remove, and execute query collections. Full descriptions of the command and
the XML format for query collections are available in the mxquery and mxquery(4) man pages,
respectively.
136 Infrastructure management using CLI