Infrastructure management using the HP SIM command line interface (436331-002, January 2009)

ManualsBrandsHP ManualsSoftwareHP Systems Insight Manager for Windows

Infrastructure management using the HP SIM

command line interface

Introduction......................................................................................................................................... 2

HP-UX............................................................................................................................................. 2

Linux............................................................................................................................................... 2

Windows ........................................................................................................................................ 2

Inventory management ......................................................................................................................... 2

Configuring HP SIM ......................................................................................................................... 2

Running discovery............................................................................................................................ 4

Running reports................................................................................................................................6

Third-party device management ......................................................................................................... 7

Managing collections........................................................................................................................... 8

Event management............................................................................................................................. 14

Configuring HP SIM ....................................................................................................................... 14

WBEM.......................................................................................................................................... 14

SNMP .......................................................................................................................................... 14

Managing HP SIM tasks ..................................................................................................................... 15

Managed server setup .................................................................................................................... 15

Managing tasks ............................................................................................................................. 16

Managing task execution................................................................................................................ 18

Managing users and authorizations ..................................................................................................... 19

Managing users............................................................................................................................. 20

Managing system groups................................................................................................................ 20

Managing toolboxes ...................................................................................................................... 22

Adding tools to toolboxes ............................................................................................................... 23

Managing authorizations................................................................................................................ 23

HP SIM configuration ......................................................................................................................... 24

HP SIM initialization....................................................................................................................... 24

HP SIM services ............................................................................................................................. 25

HP SIM log.................................................................................................................................... 25

HP SIM information ........................................................................................................................ 26

HP SIM settings.............................................................................................................................. 26

HP SIM Server certificate................................................................................................................. 27

HP SIM passwords ......................................................................................................................... 27

Appendix ......................................................................................................................................... 29

Summary of content (29 pages)

PAGE 1
Infrastructure management using the HP SIM command line interface Introduction......................................................................................................................................... 2 HP-UX ............................................................................................................................................. 2 Linux..........................................................................................................................................
PAGE 2
Introduction HP Systems Insight Manager (HP SIM) is a robust, full-featured infrastructure management tool. You can access HP SIM functionality through the web-based GUI or through the set of command line interfaces (CLI) provided. This paper discusses how to use the HP SIM CLI for managing your infrastructure. The use of CLI is described in terms of the CLIs required to perform specific tasks, such as inventory management, and event management. A list of all CLIs is provided in the Appendix.
PAGE 3
accordingly. You must run these commands must before running discovery in order for protocol authentication on the managed systems to be accepted. For details on using the CLI, see the man pages mxglobalprotocolsettings and mxnodesecurity. For XML formatting details, see the man pages mxglobalprotocolsettings(4) and mxnodesecurity(4). To change a specific global protocol setting, use the following command: # mxglobalprotocolsettings –s enable snmp =true The enable-snmp setting is one of many available.
PAGE 4
The mxnodesecurity command is useful when there are more credentials in use than the mxglobalprotocolsettings command allows, and in environments where each s
PAGE 5
# mxnode –m –f nodes.xml The -m option only accepts system names. The -a option accepts system names and IP addresses. To remove systems, use the -r option. The -r option accepts system names, host names, or IP addresses, or in conjunction with the -f option, the name of an XML file containing the names or IP addresses of the nodes to remove. For example: # mxnode –r nodeName1 ipAddress1 nodeName2 # mxnode –r –f nodes.
PAGE 6
# mxtask –cf autodisco.xml If you enabled periodic execution in the field, the task automatically runs at the time and frequency you entered. If you did not enable periodic execution, you must manually execute the task by entering the following command: # mxtask –e TaskName Where TaskName is the name of the task entered in the field of the XML file. The mxtask command has a built-in help option that describes the command, parameters, and usage examples.
PAGE 7
If you define a report in the XML file using the name of an existing report , the duplicate report is not processed. The mxreport command does not support a modify option. Therefore, to modify a report, you must delete the existing report, and then create the modified report. To delete an existing report: # mxreport –d report-name You can only delete a report that you created, or that you have permission to delete. You cannot delete system-defined reports and report categories.
PAGE 8
To add a new system type definition, use one of the following commands: # mxstm –a –n product-name –p protocol (–x attribute=value)+ # mxstm –a –f stmfile.xml • 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.
PAGE 9
The mxcollection command enables you to add, modify, remove, or list collections, or members within a collection in HP SIM. 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.
PAGE 10
• contains • ends with • does not end with • is equal to • is not equal to • starts with Because CriteriaByNameComparison is a text criteria, and the operators apply to text fields in the database only. Other criteria are selection criteria, and their operators are is and is not, since selection criteria are the specific values being compared, not free-form text. In the example, CriteriaByNameComparison is a text criteria and does not have any values.
PAGE 11
SWStatus: 12 DeviceName: tincup DeviceType: 1 DeviceAddress: 15.1.53.133 ProductName: ia64 OSName: HP-UX DeviceAddress: deviceKey: 591 fullDNSName: tincup.fc.hp.com associatedDeviceKey: AssociatedType: 0 AssociatedName: associatedDeviceKey: 0 timeStamp: 1144308295806 The mxcollection command enables you to manage the HP SIM collections and help organize query collections.
PAGE 12
To display the members of each collection, use the –lf collname option instead of the –ln option, where collname is the name of the collection. For example: # mxcollection –lf Shared displays the following output: PAGE 13
PAGE 14
Event management You can use HP SIM to manage alerts from the systems you are managing. HP SIM accepts SNMP traps and WBEM indications. This section discusses how to use the CLI to manage traps and indications. For this discussion, the term event refers to either an SNMP trap or a WBEM indication.
PAGE 15
compiles the mibfile.mib file into an intermediate file, called mibfile.cfg. If you provide the -d option, the mibfile.mib must reside in the directory mibdir. If the MIB file contains IMPORTS from other MIB files, those MIB files must reside in the same directory as the mibfile.mib file. The cfg file is placed in the same directory as the mibfile.mib file. After compiling the MIBs, the mxmib command enables you to process the cfg file.
PAGE 16
• The –u and –p options specify the account on the systems identified with the –n option. If you do not specify the –p option, then the command prompts you for the password of the user specified in the -u option. • The –o option enables you to choose host-based authentication, -o host, or user key-based authentication, -o user. If you do not specify the –o option, host-based authentication is used.
PAGE 17
You must use the following options when the sched parameter tasktype is schedule: • I are the values that you can define in minutes (runs every X minutes), hours (runs every X hours), days (runs every X days at the specified time), weeks (runs every X weeks at the specified day and time), months (runs every X months at the specified day and time), daily (at the specified time), or runonce (at the specified date and time). Here, X is defined by the P option below.
PAGE 18
# mxtask –lt The output is a table that displays the task name, the name of the tool associated with the task, the time the task was last run, and the schedule for the task.
PAGE 19
The mxexec command verifies that the user executing the command is authorized to run the selected tool on the target systems. If not, a message is logged in the HP SIM audit log (/var/opt/mx/logs/mx.log), sent to stderr, and the job is aborted. To cancel a specific job, enter: # mxexec –c [–k] –j job_ID This command cancels the job with ID job_ID. The effects of job cancellation depend on the state of the job. A job can be in one of four states: • Pending—Nothing has started.
PAGE 20
Managing users The mxuser command enables you to add, modify, remove, or list users in HP SIM. A full description for mxuser exists in the mxuser man page, and a full description of the XML syntax required to manage users with an XML file exists in the mxuser(4) man page. The mxuser –a user command adds the user with the login name of user to HP SIM. The user must exist as a user on the operating system to log in to HP SIM, but does not need to exist to be added to HP SIM.
PAGE 21
Managing authorizations. If a user is only managing a few systems, create the authorizations on a system-by-system basis. The mxngroup command enables you to create, remove, modify, and list system groups in HP SIM. For a complete description of mxngroup, see the mxngroup man page. For a complete description of the XML syntax for managing system groups from an XML file, see the mxngroup(4) man page.
PAGE 22
Using XML syntax to modify a group is more reliable, especially when the group contains many members. To modify a group that is described in a file called grp.xml, enter: # mxngroup –m –f grp.xml The same rules apply when replacing systems using XML syntax. To remove a system group, or several system groups, use one of the following commands: # mxngroup –r –g grp ; remove group “grp” # mxngroup –r –f grprm.xml ; remove groups listed in XML file “grprm.
PAGE 23
• The -d description displays a description of the toolbox. In the modify toolbox example, N newtbname renames the toolbox from tbname to newtbname. Both -d and -N are optional parameters. • The –e [t|f] switch is an optional parameter used to enable or disable a toolbox. Toolbox names are limited to a length of 16 characters, and must start with an alphanumeric character and can contain alphanumeric characters, embedded spaces, underscores (_), or hyphens (-).
PAGE 24
The first example creates a node authorization that enables username to use the tools in toolboxname to manage system nodename. The second example creates a group authorization that enables username to use the tools in toolboxname to manage all the systems in system group groupname. The third example creates authorizations as defined in the XML file authfile.xml. The following example shows what an XML file would look like when creating three system authorizations:
PAGE 25
If you are using an Oracle database, run the mxoracleconfig command before running mxinitconfig, because mxinitconfig initializes the database and the database must be in place before initialization. To configure the database, use the following command: # mxoracleconfig –h host [–n port] –d db –u 6 –p pw [–j jar] [–f ] • The -h host specifies the host name where the Oracle database is installed. • The –d db specifies the instance name of the database HP SIM will use.
PAGE 26
• The -o object option is the type of object or application that is making the log entry. If this option is not used, the default value of TYPE_NONE will be used. Valid values include APPLICATION, GUI, and TYPE_NONE. • The -r result option is the result of the event that occurred. If this option is not used, the default value of SUCCESS will be used. Value values include IN_PROGRESS, SUCCESS, FAILURE, SOME_FALURES, CANCELED, KILLED, and RESULT_NONE.
PAGE 27
The –s option sets or creates entries in the globalsettings.props file. If setting exits in the file, then it is changed to the specified value. If setting is not in the file, then mxglobalsettings prompts for confirmation to create a new entry. • If confirmed, the entry is created and sets the initial data to the value you specify in value. • The –f option forces creation of the new entry, bypassing the confirmation process.
PAGE 28
To remove existing passwords, enter: # mxpassword –r –x key1 [–x key2 …] To list existing passwords, enter: # mxpassword –l [–x key …] If you provide specific keys using the –x option, the passwords for those keys display. Otherwise, all known passwords appear. The mxpassword command uses the follow options: • The –g option launches a GUI. • The -c option checks for the existence of a key store. • The –n option creates a new server certificate.
PAGE 29
Appendix • mcompile—Compiles SNMP MIB files for registration. • mxagentconfig—Configures SSH on a managed system. • mxauth—Manages HP SIM authorizations. • mxcert—Manages server and trusted certificates. • mxcollection—Manages collections. • mxdtf—Starts the mxtdf daemon. • mxexec—Executes an HP SIM tool. • mxgetdbinfo—Displays information about the HP SIM database. • mxgethostname—Displays the name of the local host. • mxglobalprotocolsettings—Configures global protocol settings.