HP Systems Insight Manager 7.
© Copyright 2010, 2012 Hewlett-Packard Development Company, L.P. Legal Notices Confidential computer software. Valid license from HP required for possession, use or copying. Consistent with FAR 12.211 and 12.212, Commercial Computer Software, Computer Software Documentation, and Technical Data for Commercial Items are licensed to the U.S. Government under vendor's standard commercial license. The information contained herein is subject to change without notice.
Table of Contents 1 About the HP Systems Insight Manager command line interface......................11 Introduction............................................................................................................................11 Commands............................................................................................................................11 manpages (manual pages)..................................................................................................
mxcipher...............................................................................................................................29 Synopsis...........................................................................................................................30 Options............................................................................................................................30 Return values.............................................................................................
Return values.....................................................................................................................47 Examples..........................................................................................................................47 See also...........................................................................................................................48 mxglobalsettings................................................................................................
Description........................................................................................................................63 XML file support.................................................................................................................69 Options............................................................................................................................69 External influences.............................................................................................
mxstatus................................................................................................................................99 Synopsis...........................................................................................................................99 Description........................................................................................................................99 Options..................................................................................................
External influences...........................................................................................................125 Return values...................................................................................................................125 Examples........................................................................................................................125 Limitations...........................................................................................................
Related documents................................................................................................................158 Documentation and support..............................................................................................158 HP Systems Insight Manager documentation........................................................................158 Index.......................................................................................................
1 About the HP Systems Insight Manager command line interface Introduction Systems Insight Manager provides a command line interface (CLI) in addition to the graphical user interface (GUI). Many functions available in the GUI are also available in the CLI.
Command list The following table lists the Systems Insight Manager CLI commands. For more details about each command, see Command descriptions or the manpage for each command. NOTE: The manpage section numbers for CLI command line usage manpages are different for each operating system. The CLI command line usage manpage section number is 1M for HP-UX and Windows operating systems, and 8 for Linux operating systems. The CLI XML usage manpage section number is 4 for all operating systems.
Command Functionality Available manpages mxinitconfig Performs initial configuration for the CMS. mxinitconfig(1M, 8) NOTE: For best performance, running mxinitconf is not recommended after Systems Insight Manager is configured. mxlog Logs an entry to the log file or standard out. mxlog(1M, 8) mxmib Adds, deletes, and processes a list of MIBs for Systems Insight Manager and lists registered MIBs and traps for a specific registered MIB.
Logging in to the CLI Access the Systems Insight Manager CLI directly on the CMS or from any network client using SSH client software. Logging in directly on the CMS 1. Log in to the CMS using a valid user name and password (SSH system name ). Systems Insight Manager grants authorizations based on your operating system login. 2. Open a terminal window or a command prompt window to execute Systems Insight Manager commands.
• • • • • • • • • • • • • mxlog mxmib mxngroup mxnode mxnodesecurity mxquery mxreport mxstm mxtask mxtool mxtoolbox mxuser mxwbemsub On a Windows CMS, if you are not a member of the local Administrators group, add the options --user username and --pass password when running any of the listed commands. For example, to list information about one or more authorizations in compact or table form, enter mxauth [-lt] --user username --pass password.
2 Command descriptions This chapter describes the commands in the Systems Insight Manager CLI. The commands in this chapter use the following conventions: • Optional items are enclosed in square brackets [ ]. • Required parameters are in italics. • The | character indicates a choice between options. • Curly brackets { } indicate an option that requires one or more values. mcompile Compiles SNMP mib files into intermediate format (.cfg) files.
HP Systems Insight Manager Mib Compiler, Version 1.0 Copyright (c) 2003 Hewlett Packard Corporation Compiling cpqHost.mib Processing import file: RFC1155-SMI.mib Processing import file: RFC1155-SMI.mib Processing import file: rfc1213.mib Processing import file: RFC-1212.mib Processing import file: RFC-1215.mib Processing import file: rfc1213.mib Mib Compilation completed successfully. See also mxmib(1) mxagentconfig Configures the agent to work with a CMS.
NOTE: Be careful when entering passwords in the CLI. This makes them available in the command history, the process list during execution, and the audit log if the command is executed as part of a task. Be sure to clear your command history or use alternate methods for specifying passwords, for example, a prompt or input file. This command can accept multiple host names. The user account and password must be the same for all host names entered in a single command.
iLO4 configuration [-B Trap Destination 1] [-C Trap Destination 2] [-D Trap destination 3] Setting the iLO embedded SNMP trap destinations [-J OS Traps ] Enable host operating system traps [-K RIB Traps ] Enable iLO4-specific hardware traps [-R SNMP Read Only Comm String 1] [-G SNMP Read Only Comm String 2] [-H SNMP Read Only Comm String 3] Setting read-only community strings for iLO4 embedded SNMP stack [-S SNMP < EALERT | PASSTHRU >] iLO4 Ealert is enabled embedded health and alerting, passthru
Managed node: • • • ~/.ssh/..dtfSshKey.pub ~/.ssh/authorized_keys2 ~/.ssh/authorized_keys2.bak Example 1 To copy the SSH-generated public key from the CMS to the node node1 with the username root and password password, enter mxagentconfig -a -n node1 -u root -p password. Example 2 To remove the host from the known host list but still be able to run the SSH commands for an hour after the last SSH command was executed, enter mxagentconfig –r –n node name.
mxauth Adds, removes, or lists authorizations in Systems Insight Manager. Synopsis mxauth -a|r -u username | -U usergroupname -R toolboxname -n nodename mxauth -a|r -u username | -U usergroupname -R toolboxname -g groupname mxauth -a|r -f filename mxauth [-l t] mxauth -l f [-b encoding ] Description The mxauth command is used to manage authorizations. These associations between users, user group name, toolboxes, and nodes or node groups can be added or removed only by administrative rights users.
When you use -l t, mxauth lists all authorizations in a table with column headings identifying each field. For Systems Insight Manager 5.1 and later, the enabled/disabled state of the Auto Update feature is displayed for node group authorizations. Auto Update enables you to configure authorizations that can be automatically updated (systems added or removed from the associated node group list) in the background at a configurable interval, for example, every five minutes.
Add authorizations. The wildcard character (*) is supported for nodename and groupname . -r Remove authorizations. The wildcard character (*) is supported for nodename and groupname . -f filename Specify a file that contains the list of authorizations to add or remove. -l t List all authorizations in tabular format. -l f List authorization information in XML format. The resulting file can be edited and used to add or remove authorizations with -f. -b encoding Specify the character encoding for the XML file.
Return values Value Meaning 0 Successful completion. 1 Command line syntax error. 2 Error in a file operation. 3 Nonexistent user, toolbox, node, or node group error. 21 Invalid name. 102 Database error. 222 The CMS is not initialized. 249 Unable to connect to the session manager. Examples Example 1 To add the authorizations in the file my_auths.xml, enter mxauth -a -f my_auths.xml. The contents of my_auths.xml might look like:
Example 5 To use the wildcard character to remove the node authorizations that allow user wilma to execute any tools assigned to the webadmin toolbox on all configured nodes at the time the command is executed, enter mxauth -r -u wilma -R webadmin -n "*". Example 6 To add the node group authorization to allow user sue to execute any tools assigned to the webadmin toolbox on nodegroup webGroup, enter mxauth -a -u sue -R webadmin -g webGroup.
mxcert Manages certificates in Systems Insight Manager.
Import the signed server certificate from the specified file. -t [ -f [filespec] ] Import the trusted certificate from the specified file. -i Import the signed server certificate from stanard input.While giving input from standard input Please enter OS specific End of input characters after input is complete (ENTER ^Z ENTER for windows,ENTER CTRL-D ENTER for Unix) to confirm certificate input is complete. -t Import the trusted certificate from the standard input.
Create a new WBEM server certificate with the provided details, where CN=common_name, OU=organizational_unit, O=organization_name, L=locality_name, ST=state, and C=country-code. -O Create a new 1,024-bit SSO server certificiate. -o Create a new 1,024-bit SSO servver certificate. [CN=x] [OU=x] [O=x] [L=x] [ST=x] [C=x] Create a new SSO server certificate (1,024-bit) with the provided certificate details.
Synopsis mxcipher -e 1|0 mxcipher -d Options -e 1 Enforce stronger cipher suites for Systems Insight Manager SSL web server and partner application SOAP servers. This is the default setting of Systems Insight Manager. This does not enforce stronger cipher suites for the WBEM indication receiver. Systems Insight Manager must be restarted after you run this command. 0 Enables both strong and weak cipher suites for Systems Insight Manager SSL web server and partner application SOAP servers.
mxcollection -lf existcollname [-b encoding ] mxcollection -mv existcollname -from fromparentcollname -to toparentcollname [-branch sysbranch|evbranch ] mxcollection -cp existcollname -name newcollname -to toparentcollname [-branch sysbranch|evbranch ] mxcollection -a combo newcombocollname -syscoll systemcollname -evcoll eventcollname -parent toparentcollname [-branch sysbranch|evbranch ] Description The mxcollection command enables you to add, list, modify, copy or delete collections.
• mxcollection -mv existcollname -from fromparentcollname -to toparentcollname [-branch sysbranch|evbranch ] This command moves an existing collection from its current parent collection to another parent collection. The -branch option lets you specify whether the new parent collection is in the Systems or Events list in the System and Event Collections panel. NOTE: You can move collections within the Systems list or the Events list, but you cannot move collections from one list to another.
-b encoding Specify the character encoding for the XML file. This is used with -lf. -mv existcollname Move an existing collection from one parent collection to another. -from fromparentcollname Specify the from parent collection when moving a collection from one parent to another. -to toparentcollname Specify an existing collection to be the new parent collection. This option is used with -mv, and -cp. -cp existcollname Copy an existing collection.
Examples Example 1 To add the collections cupertino site and building 45, each with two members, enter: mxcollection -a -f my_collections.xml . The contents of my_collections.xml might look like: PAGE 35Description The mxconfigrepo command enables you to recreate the database (init), merge in updated SQL files for an upgrade, or search for corrupted records or database inconsistencies. The tool will search the database for any known issues and verify or fix the database to enable Systems Insight Manager to start without requiring a re-install. • mxconfigrepo –c This command enables you to detect and log errors. Run this command from the lbin directory.
Description The mxexec command executes an Systems Insight Manager tool with associated arguments on specific managed nodes and node groups. A tool and its arguments, specified to run on one or more nodes, is called a task. An instance of the task running at a particular time is called a job. • mxexec -t toolname [-A argvalue... ] [-h|-O filename|-o directory ] [-n target...|-q queryname... ] This command enables you to run Systems Insight Manager tools.
Default target node influence on tool The value of the default targets tool attribute defTargets enables different tool execution behaviors if no targets are specified on the command line. The following table describes the behavior of tool execution for all values of defTargets if no target list is specified on the command line: ALL Use all of the user's authorized nodes as the target list. CMS The CMS is the only node in the target list. [empty] Error. A target list must be specified.
• • • Pending. The job has not started on this node. This state is used when there are a large number of target nodes and the CMS DTF is only able to run a job in parallel on a smaller number of nodes. Copying files. Any files that need to be copied are transmitted to the target, and the target writes the files and sets their ownership and permissions. The maximum number of files that can be copied is 16. Running tool.
• will start immediately, and the remaining targets will wait in the Pending state until earlier targets finish execution. The agent has a limit of four simultaneous job executions. If four jobs are executing on a target, and a new job is started that references that target, when the DTF contacts the agent on that target to run the new job, it gets an agent busy exception. The DTF will continue contacting any other referenced targets until the only ones remaining are those that are busy.
Specify the name of an existing query on which to execute the tool. -i task_name [task_name...] Specify the existing tasks on which to perform a specified operation. -j jobID [jobID...] Specify the currently running job on which to perform a specified operation. -d date List the jobs completed after a specific date. Enter the date in the format: month/day/year hour:minute AM|PM.
See lang (5), environ (5), and local (1) for additional information. Return values Value Meaning 0 Successful completion. 2 Command line syntax error. 3 Nonexistent tool error. 6 Nonexistent user error. 7 Nonexistent node error. 8 Nonexistent node group error. 9 Nonexistent job ID or task name error. 21 Invalid name. 27 Invalid operation. 28 Invalid tool. 29 Invalid runnable tool. 50 Unauthorized user. 51 Unauthorized or disabled toolbox. 52 Unauthorized node.
/dev/vg00/lvol5 786432 604051 171001 78% /dev/vg00/lvol7 524288 76726 419856 15% /dev/vg00/lvol8 339968 291563 45670 86% /dev/vg00/lvol6 131072 2507 120594 2% Node : db3.myco.com Status : Failed Exit Code : 0 EXCEPTION : Exec failure - Not enough memory Node : db2.myco.
NOTE: Even though the command executed on machine2.myco.com failed (exit code of 1), mxexec considers it complete because the command executed without any errors associated with mxexec or the agent on machine2.myco.com. There is no reliable way to determine if a failure has occurred based solely upon the return value of the command. Limitations This command can only be run on the CMS.
4. 5. All Jobs and tasks must be completed. Ensure there are no running discovery, identification or deployment tasks by viewing the task list in Systems Insight Manager GUI. Determine if enough disk space is available on the server. The required disk space is dependent on the size of the database. Return values No return value. Note: This tool continues even if an HP Insight Control software fails during export.
mxgetdbinfo Obtains information about the Systems Insight Manager database settings. Synopsis mxgetdbinfo mxgetdbinfo [-a|-h|-p|-d|-u|-t|-r|-b] Description mxgetdbinfo displays Systems Insight Manager database information such as the hostname of the database server, the TCP/IP port, database name, username, and database type. Options -a Display the hostname, port number, database name, username, and database type as key/value pairs.
Examples Example 1 Enter mxgetdbinfo to display the hostname, port number, database name, username, and database type. The output might look like: host=127.0.0.1 port=1433 dbname=Insight_v1_0 user=sa dbtype=SQLServer Example 2 Enter mxgetdbinfo -d to display the database name. The output might look like: Insight_v1_0. mxgethostname Prints the name of the local host in Systems Insight Manager.
Synopsis mxglobalprotocolsettings -s [-f file-name|- ] mxglobalprotocolsettings -s {setting=value}... mxglobalprotocolsettings [-ld] mxglobalprotocolsettings -lf [-b encoding ] Description mxglobalprotocolsettings is used to manage Systems Insight Manager's global protocol settings. Options -s [-f file-name|- ] Set global protocol settings from a specified XML file or standard input. See the mxglobalprotocolsettings(4) manpage for XML file format details. -s {setting=value}...
Example 2 To list the global protocol settings in XML format, enter mxglobalprotocolsettings -lf. The output might look like: PAGE 49Return values Value Meaning 0 Successful completion. 2 Command line syntax error. -1 An error occurred during operation. Files /etc/opt/mx/config/globalsettings.props Examples Example 1 To list all the settings from the globalsettings.props file, enter mxglobalsettings -ld. The output might look like: AllowAltIpForTrap = enabled CMSDeviceKey = 2 CMSLocale = en_US CertificateExpirationCriticalStart = 0 CertificateExpirationMajorStart = 10 CertificateExpirationMinorStart = 30 ...
Prerequisites 1. 2. 3. 4. 5. 6. You must be a member of the local Windows Administrators group. The server has HP Insight Control Suite 6.0 or later installed, which includes HP SIM 6.0 or later. All HP Insight Control software that were installed on source server must be installed on target server as well. Stop the Systems Insight Manager service and all other HP Insight Control software before running import function. The CMS must be a clean installation and have no prior configurations.
mximport -p d&e128Pa Example 3 To import data by specifying a filename, enter mximport -f c:\data\Products.zip Example 4 To import data by specifying a filename and a password, enter mximport -f c:\data\Products.zip -p d&e128Pa SQL Server database settings 1. 2. The target CMS and the remote SQL database server must be in the same domain. The folder configdata-import under [HPSIM]\data on the target server must be shared and granted with full permissions.
A ReadWrite string will be created automatically on Windows systems. 4. Configure secure shell (SSH) access authentication: XML Property name : argument_ssh Default value : host Other allowed values : user Host-based authentication: All users from this instance of Systems Insight Manager will be authenticated on the managed system. User-based authentication: Each user must be authenticated on the managed system. 5.
Debug settings By default, the debug log is disabled for migration. To turn on the debug log, open the file migration.props under [HPSIM]\config\debugsettings, and modify the value of the property GlobalEnable to true and set the log level to 20 or above for finest logging. This property file will be created on the first run of export of import operation. The debug log file will be created under [HPSIM]\logs with name migration_log4j.log. A backup log file will be created with name migration_log4j_backup.
-r Unconfigure the server -l List the current configuration status. Return values Value Meaning 0 Successful completion. >0 An error occurred during operation. Files HP-UX and Linux operating systems • • /var/opt/mx/logs/initconfig.log /etc/opt/mx/config/initconfig.properties Windows operating systems • • \HP SIM directory\logs\initconfig.log \HP SIM directory\config\initconfig.properties Examples Example 1 To configure the server, enter mxinitconfig -a.
• mxlog -l [-r result ] [-a action ] [-o object_type ] [-n object_name ] [-u user ] [-s sessionID ] [-t transactionID ] [-v verbosity ] [-m message ] This command logs the indicated entry to the log file. • mxlog -p [-r result ] [-a action ] [-o object_type ] [-n object_name ] [-u user ] [-s sessionID ] [-t transactionID ] [-v verbosity ] [-m message ] This command saves the log entry to standard out. Options -l Log an entry to the log file. This will not print the entry to stdout.
-t transactionID Enter the transaction ID in string form. You must specify a value if -t is used. If -t is not used, there is no value for this field. -u user Specify the user that submitted this log entry. You must specify a value if -u is used. If -u is not used, the default is the user name of the user running the command (usually root). This option is typically used to specify the name of the application logging a message rather than the run-as user of the application.
Synopsis mxmib mxmib –a CFG filename mxmib -d mib filename mxmib -l mxmib -f filespec mxmib -t mib Description The mxmib command enables you to register and unregister a mib, register a list of mibs from a file, list mibs registered in Systems Insight Manager, and list a registered mib's traps. Options -a CFG filename Register a new CFG, file ( filename.cfg ), or replace the data of a registered mib. -d mib filename Unregister a mib, ( filename.mib ).
Example 3 To update a MIB file in Systems Insight Manager, complete the following steps: 1. 2. Download the new mib and copy it into the mibs directory. Run mcompile to update the existing .cfg file. NOTE: 3. If the existing .cfg file had any customizations, these must be reapplied. Run mxmib -a updatedfile.cfg to update the MIB data in the Systems Insight Manager database. mxngroup Adds, modifies, removes, or lists system groups in Systems Insight Manager.
updates the authorization information for any authorizations associated with the modified system group. • mxngroup -r -g groupname mxngroup -r -f filename These commands allow you to remove a system group. You can specify an individual system group or an XML file containing multiple system groups. The file must be formatted as described in the mxngroup(4) manpage. When an Systems Insight Manager administrative rights user removes a system group, the authorizations associated with the group are removed.
Options -a Add a group. -m Modify a group. -r Remove a group. -l d Display a detailed screen-viewable list of system group information. -l f Display a file-formatted list of system group information (see mxngroup(4) ). -l m Display the member systems of the system group. -l n Display the names of the system groups. -f filename Specify the path and name of the input file for an add, modify, or remove operation. -g groupname Specify the name of the group to be added, modified, removed, or listed.
NOTE: When duplicate options are specified, the last instance of the option is used. For example, if you enter -f file1 -f file2, mxauth uses file2. 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)).
Example 6 To list the member systems of group group1 enter mxngroup -l m -g group1. Example 7 To list the names of all system groups that contain the member systemb, enter mxngroup -l n -n systemb. Example 8 To use the XML file test.xml to define a system group named group1 with a description and two member systems, system1.corp.com and system2.corp.com, enter mxngroup -a -f test.xml The test.xml file might look like:
mxnode -a -f filename [-w] [-v] mxnode -a -m -f filename [-w] [-v] mxnode -m [-p] -f filename [-w] [-v] mxnode -m systemname(s) mxnode -r nodename(s)|hostname(s)|ipaddr(es) [-x force] [-v] mxnode -r -f filename [-x force] [-v] mxnode -ln [ systemname(s) ] mxnode -ld [ systemname(s) ] mxnode -lt [ systemname(s) ] mxnode -lf [ systemname(s) ] [-b encoding ] mxnode -lmpo [-b encoding ] Description The mxnode command enables you to add, modify, remove or list Systems Insight Manager systems.
• • its context from the database. The CMS itself and non-empty container systems cannot be removed. During the removal process, the system is removed from all system groups and all authorizations (see mxauth(1M)) for the system are removed. It is not an error to remove a system from the database while a task is running on the system. Systems Insight Manager does not terminate the task on the system; task results and status are sent to Systems Insight Manager when the task is complete.
• • • • • • • • • • • • • • • • • • • • • • • name can be anything as long as it is unique among all the systems in the database, and it can be changed. Host name . The hostname is available from gethostbyname(1). It can 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 . The name of the operating system on the managed system.
as required in the XML file, and the attribute label displayed in the GUI.
• • • OS Revision (OSRevision) . The revision level of the operating system. Any displayable text can be used as a value for this attribute. Contact (Contact) . The person to contact if system maintenance is needed. Any displayable text can be used as a value for this attribute. Location (Location) . The physical location of the system. Any displayable text can be used as a value for this attribute. Hardware attributes • Device Type (DeviceType) . The major type of the device.
• 68 GUI name mxnode attribute name Resource Partition RESPAR Application Application Device Subtype (DeviceSubType) . The subtype of the device within the major type. Only the following predefined valid device subtypes can be used as values for a device subtype.
GUI name mxnode attribute name HP 9000 Superdome HP9000Superdome HP Integrity HPIntegrity HP Alpha Station HPAlphaStation Virtual Machine Host VMHost HP Serviceguard HP Serviceguard High Availability Cluster HighAvailabilityCluster nPar nPar HP Deskpro HPDeskpro HP Integrity Superdome HPSuperdome MSCS MSCS HP Integrity Workstation HPIntegrityWorkStation High Availability Array HighAvailabilityArray HP Integrity Virtual Machine HPVMHost Host HP Integrity Virtual Machine HPVMGuest Gu
This is the only option that enables MPO or Contract and Warranty data residing in an XML file to be recognized and evaluated. MPO and Contract and Warranty data within the XML is not available with -a because a system must first exist before the MPO or Contract and Warranty data can be added or modified. MPO or Contract and Warranty data for a system can be added, modified or removed only through the use of an external XML file.
-v Display verbose progress information. External influences For HP-UX or Linux, LANG determines the default encoding 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, use the -b option to specify the encoding of the XML data. Return values Value Meaning 0 Successful completion. 2 Command line syntax error.
192.1.1.1 Example 2 To remove node abc from the database, enter mxnode -r abc. Example 3 To list, in detailed format, all attributes for the node abc, enter mxnode -ld abc. The output might look like: 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.
HP-UX phoenix abc.mycompany.com Example 6 The sample XML file below lists a node in XML format and includes all predefined system attributes for reference, including those that can be modified or locked. One method for modifying a system is to use the mxnode -lf > filename command to output the XML data to an external output file.
The attributes that can be modified and locked, but require a predefined value, are marked with an asterisk. See the System attributes that can be locked section for the valid values for the DeviceType, DeviceSubType and OSName attributes. Ensure that the correct category is used for each attribute (hardware or software). The three attribute lock flags are marked with an LF marker. Sample XML file with all system attribute formats and syntax:
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.
WBEM_CIMOM nnnn nn.nn.nnn.nn https nnnnnnnnnnn interop Array Server Basic Read Basic Write PAGE 77MyAddress1 MyAddress2 MyCity MyState MyCountry MyPCode MyTimezone Mr.
Synopsis mxnodesecurity -a -p protocol -c username:password [-t on or off ] [-n nodename ] Add or modify node/system credential. mxnodesecurity -a -p wbem -c username:password [-t on or off ] -n nodename [ :Port# ] Add or modify WBEM node/system credential. mxnodesecurity -a -p snmp -c username:password [-t on or off ] [-n nodename:Port#] Add or modify VME (protool - vcenter, scvmm or rhevm) node/system credential.
Description The mxnodesecurity command enables a CMS user to add, modify, list, or remove default/global and node/system credentials in the CMS. The difference between default and node type credentials should be noted. All type credentials are stored in the Systems Insight Manager database.
If you attempt to remove a global credential that is currently in use, the CLI displays an error message, indicating that the credential was not removed and describing the two methods ([-x]) that can be used to forcefully remove the credential. — To forcefully remove a global credential without copying the credential, use the -x option with the following argument: mxnodesecurity -r -p protoName [-x {forceDelete | fd}] This option can cause loss of communications with some systems.
credential is a protocol independent credential used to sign into the managed system. The mxnodesecurity command also accepts any name for a protocol name. -c username:password Specify a user name and password for a WBEM credential. This option is used with -a -p wbem -a -p vme:protocol. NOTE: Be careful when entering passwords in the CLI. This makes them available in the command history, the process list during execution, and the audit log if the command is executed as part of a task.
Return values Value Meaning 0 Required configuration files were updated correctly. 1 Command line syntax error. 2 Error in a file operation or parsing a file. 21 Invalid name. 250 Remote exception. Examples Example 1 To add a WBEM credential to the Systems Insight Manager credentials database for the node mycomputer.ak.hp.com, enter mxnodesecurity -a -p wbem -c username:password -n mycomputer.ak.hp.com. The username and password are defined uniquely for specified node.
Example 4 The command below adds a VME node/system type credential to the Systems Insight Manager credentials database for the VME protocol vCenter and specified node named mycomputer.ak.hp.com and for a specified port number of 5990. Only VME and WBEM type node credentials allow for a port number to be specified along with the nodename in the form of nodename:port#. Since port# is not specified by user, default ports are used. (vCenter-443, scvmm - 7999).
Example 9 The command below would modify the user name and password of an existing default/global credential with a specified protocol type of SSH and a specified nodename of @default3@default3. The nodename reference used in the command below would be acquired from an mxnodesecurity list (-l) command. Note that when listing default/global credentials, the node names are in the form of @defaultN, where N is an auto-assigned numerical value indicating usage precedence.
Example 18 The command below displays a list of all credentials (default and node) of type WBEM protocol. mxnodesecurity -l -p wbem Example 19 The command below displays a list of all credentials (node) of type VME protocol scvmm (can also be - vCenter, rhevm). mxnodesecurity -l -p vme:scvmm Example 20 The command below displays all node/system credential(s) for the specified node mycomputer.ak.hp.com. mxnodesecurity -l -n mycomputer.ak.hp.
nodeName3 ws-man user2 ******** No estNode4 abc user4 ******** Yes mycomputer2.ak.hp.com wbem user1 ******** No mycomputer2:7999 scvmm user1 ******** No mycomputer2:666 vCenter user1 ******** No Limitations • • • This command can only be run on the CMS. Systems Insight Manager must be running For an HP-UX or Linux CMS, this command can be run only by the root user.
-p password Enter the password. -j jar file Specify the location of the jar file containing the Oracle thin jdbc driver. The driver is typically named ojdbc14.jar. -f Force re-run. Typically, mxoracleconfig should be run only once. Use the force flag if you need to re-run this command. Return values Value Meaning 0 Required configuration files were updated correctly.. -1 An error occurred during operation.
Description The mxpassword enables you to add, remove, modify, and list the passwords stored for use with Systems Insight Manager. The passwords are displayed in clear text for readability. CAUTION: To prevent clear text passwords from being exposed to unintended eyes, close the command window after executing this command. Options -a Add a new password. -m Modify an existing password. -r Remove an existing password. -l List the passwords stored by Systems Insight Manager. -g Start the mxpassword GUI.
Examples Example 1 To list all the passwords stored by Systems Insight Manager, enter mxpassword -l. Example 2 To change the current SSH password to scoobydoo2, enter mxpassword -m -x MxSshKeyPassword=scoobydoo2. Example 3 To change the current database password to rocketboy2, enter mxpassword -m -x MxDBUserPassword=rocketboy2. Example 4 To remove the current SSH password, enter mxpassword -r -x MxSshKeyPassword. Example 5 To remove the current database password, enter mxpassword -r -x MxDBUserPassword.
Description The mxquery command enables you to add, list, modify or remove queries in Systems Insight Manager. IMPORTANT: Using mxcollection is preferred over using category with mxquery. Using cat will still work for mxquery, but you should switch to mxcollection for creating and manipulating collections (previously known as categories). • mxquery -a -f filename [-x force] This command enables you to add queries.
mxquery gives a tabular listing showing some attributes of all registered queries. You can limit the query information by specifying one or more query names. • mxquery -lf [-b encoding] [-x query [queryname...] ] This command writes a complete definition (see mxquery(4)) for each query to stdout . Optionally, you can specify the character encoding of the XML file. The value for the character encoding must match a valid character encoding.
-l n List the names of Systems Insight Manager queries. -l t Display a tabular list of queries and query attributes. -l cat Display a list of query categories to which you can add queries. -l crit Display a list of criteria with which you can construct queries. -l mode Display a list of operation modes or operators that can be used in association with a specified criteria. -l val Display a list of defined values associated with a specified criteria.
Return values Value Meaning 0 Successful completion. 2 Command line syntax error. 3 Invalid object. 21 Invalid name. 102 Systems Insight Manager repository error. 222 The CMS is not initialized. 249 Unable to connect to the session manager. 250 Remote exception. Examples Example 1 To add the queries defined in the query definition file /home/user1/defs/myquerydef, enter mxquery -a -f /home/user1/defs/myquerydef.
Example 11 To display the defined criteria values for the criteria CriteriaByProductType, enter mxquery -lval CriteriaByProductType. Limitations This command can only be run on the CMS. See also HP-UX mxauth(1M), mxquery(4) Linux mxauth(8), mxquery(4) mxreport Adds, deletes, runs, lists reports and report categories in Systems Insight Manager.
• mxreport -r existing-report-category-name This command enables you to remove a report category. Only an administrative rights user or the report owner can remove a report category. Systems Insight Manager notifies you if you specify a nonexistent report category name. • mxreport -c -f fully-qualified-file-name This command enables you to create a new report category. The category is defined in an XML file. You must have the REPORT_MODIFICATION_PRIVILEGE to create a new report category.
Options -a -f Add one or more reports specified in a report definition file. -d Remove the specified report. -r Remove the specified report category. -c -f Add the category specified in the listed file. -e Run the specified report. -S Replace the system collection in the specified report with the listed system collection. -n Indicate that a comma-separated list of system names is used with -S instead of a collection name. -E Filter the specified report by the listed query.
reportname Specify the name of a report. Specifying an invalid report name results in an invalid name return value. If the report name contains spaces, enclose it in quotation marks. categoryname Specify the name of a report category. Specifying an invalid report category name results in an invalid name return value. If the category name contains spaces, enclose it in quotation marks.
Example 5 To run the report Catapult Launchers and format the output as CSV, enter mxreport -e "Catapult Launchers" -x CSV. Example 6 To list all reports, enter mxreport -l -x report. Example 7 To list the contents of the report Islands of Phoenix, enter mxreport -l -x report -n "Islands of Phoenix". Example 8 To list all report categories, enter mxreport -l -x category. Example 9 To list the contents of the report category White Noise, enter mxreport -l -x category -n "White Noise".
Return values Value Meaning 0 Systems Insight Manager and TomCat started correctly. >0 An error occurred during startup. Example To start the Systems Insight Manager daemons, enter mxstart.
immediately to the calling application with the current Systems Insight Manager ready/not-ready state. -t The TIMEOUT option may be used to specify a safety timeout period that will be utilized when the -w Wait option is used. The safety timeout provides a way for the command to return to the calling application in case Systems Insight Manager never reaches a ready state. For example, Systems Insight Manager is actually not running.
Example 4 To check the current Systems Insight Manager ready/not-ready state in NOWAIT mode with verbose mode enabled, mxstatus -v. Example 5 To check the current Systems Insight Manager ready/not-ready state in WAIT mode with verbose mode enabled, mxstatus -w -v. Example 6 To check the current Systems Insight Manager ready/not-ready state in WAIT mode with a specified timeout value of 3 minutes with verbose mode enabled, enter mxstatus -w -t 3 -v.
-r Remove an existing rule. Optionally, use -f to delete one or more rules from an XML file. The XML file must be encoded in UTF-8 and must be declared with encoding="UTF-8" -l List system type manager rules. • Use -n to provide a product name and list rule details. • Use the -f option to output rules to an XML file. The XML file is encoded in UTF-8. Optionally, specify a protocol to selectively output rules matching that protocol. The XML file output by this command is valid input for -a and -r.
Examples Example 1 To add a rule for a Digital LN07 printer using an XML file named printer-rule.xml, create printer-rule.xml with the following contents: Printer None Digital LN07 1 1.3.6.1.4.1.108.1.1.
Example To stop the Systems Insight Manager daemons, enter mxstop. See also HP-UX mxstart(1M) Linux mxstart(8) mxtask Lists, executes, removes, creates tasks, or changes task ownership in Systems Insight Manager.
This command lists the specified task in task-specific XML format. Output from this command is written to stdout, and can be redirected (with >) to an external file. The output file can be modified and used as the XML input file when creating a new task with -cf. Using the all keyword forces mxtask to list all tasks in XML format. See the mxtask(4) manpage for a detailed description of the task-specific XML format. Optionally, you can specify the character encoding of the XML file.
Display an XML file listing for a specified task. This output can be redirected (>) to a file and used as input to the -f option when creating a new task. For example, -lf taskname >filename. -lf all Display an xml format list of all Systems Insight Manager tasks. This output can be redirected to a file and used as input to -f when creating a new task. -r taskname Remove a specified task immediately. -rf taskxmlfile Indicates that the specified Systems Insight Manager task(s) is to be removed.
double quote characters, each double quote character must be preceded by the backslash character. This option is used with -c. -f toolparmsfile Specify the parameter data for a tool that requires user parameters. The tool parameters for -f are provided in a specified XML file that contains the tool parameters. This option is used with -c. (Create task)or –r (remove task). -o taskowner Specify a task owner for the new task that will be created.
etc. If the interval type is months, the valid day value is a numeric value in the range of 1-31. If the Interval type is runonce, the valid date value is mm/dd/yy. • • • Tschedule.Iweeks.Pn.Dfriday Tschedule.Imonths.Pn.D1 Tschedule.Irunonce.Dmm/dd/yy The M parameter signifies a time value and is required for all valid interval types except minutes and hours. This parameter defines the time at which the task will run and is specified in 24 hour format as follows. Tschedule.Iweeks.P2.Dfriday.
Example 2 To list all scheduled tasks in tabular format, including the task name, associated tool name, last run time and schedule information, enter mxtask -lt. Example 3 To list the details for the task test_task, enter mxtask -ld test_task. Example 4 To list descriptive data for the task test_task in XML format, enter mxtask -lf test_task. Output from this command can be used to create a new task requiring the same tool, with similar tool (user) parameters.
In this example, there are no tool (user) parameters required for the tool being specified, so -A and -f are not required. Example 12 To create task1, which runs every 12 hours, with the associated query query1 and tool toolexample that already exists in the database, with the task type schedule, enter mxtask -c task1 -q query1 -t toolexample -w Tschedule.Ihours.P12. In this example, there are no tool (user) parameters required for the tool being specified, so -A and -f are not required.
Tool parameters are specified with -f. The filename specifies the path and name of a file that contains the tool (user) parameter data for the specified tool. The tool parameter data contained in this file must be of the exact same XML format as stored in the Systems Insight Manager database.
mxtool Adds, lists, modifies, or removes tools in Systems Insight Manager. Synopsis mxtool -a -f filename mxtool -m [-i] -f filename [-x force] mxtool -s -f filename mxtool -r [-f filename|-c category|-t toolname ] [-x force] mxtool -l d|f|n|t [-c category...|-t toolname... ] mxtool -lf [-b encoding ] [-c category...|-t toolname... ] mxtool Description The mxtool enables you to add, list, modify or remove tools. • mxtool -a -f filename This command enables you to add tools.
You cannot add tools with the modify option. If there is a tool in the tool definition file that does not exist, Systems Insight Manager will notify you and then modify the existing tools specified in the tool definition file. Skipping undefined tools does not affect the return value. During the modify operation, you cannot remove the All Tools toolbox from any tool. Only an administrative rights user can add or modify a tool that is multiple-system aware, such as Ignite.
-r Remove one or more tools. -m Replace one or more tool definitions with the definitions in the specified tool definition file. -i Ignore changes to toolboxes in the tool definitions. This option is only valid with -m. -s Scan the specified tool definition file for syntax errors without performing any other operations. -c category Specify a tool category. Specifying an undefined category name causes mxtool to return an empty tool list and a return value of SUCCESS.
This option forces a tool into the system when used with -m -f, and specifies the forced removal of a tool when used with -r -f. NOTE: When duplicate options are specified, the last instance of the option is used. For example, if you enter -f file1 -f file2, mxauth uses file2. 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.
Linux mxexec(8), mxtool(4). mxtoolbox Adds, modifies, removes, or lists toolboxes in Systems Insight Manager.
• mxtoolbox -r toolboxname This command enables a full rights user to remove a single toolbox from the database. • mxtoolbox -r -f filename This command enables a full rights user to remove multiple toolboxes based on information provided in a file. The file must be formatted in the XML format defined for toolboxes. See mxtoolbox(4) for additional information.
Add a toolbox. -d description Specify a toolbox description. -e t|f Specify the toolbox enablement (t is enabled and f is disabled). -f filename Specify the filename that contains information about users to be added, modified or removed (see mxuser(4)). -l n Display a columnar list of the names of all enabled and disabled toolboxes. This produces the same result as not specifying any options. -l t Display a tabular list of toolbox attributes for all toolboxes.
Value Meaning 26 Unsupported operation. 50 Unauthorized user. 102 Systems Insight Manager repository error. 222 The CMS is not initialized. 249 Unable to connect to the session manager. 250 Remote exception. 253 Duplicate name. Examples Example 1 To add toolboxes from the file toolboxlist.xml, enter mxtoolbox -a -f toolboxlist.xml. Example 2 To disable the HP ASE toolbox, enter mxtoolbox -m "HP ASE" -e f. Example 3 To modify the toolboxes in the file toolboxlist.
Example 8 To list all toolboxes in an XML file, enter mxtoolbox -lf The output might look like the following: WEB Server Administrator Master ToolBox added by Systems Insight Manager.
Synopsis mxuser -a username [-d description ] [-p CMSSecurity ||none|+T|-T] [-C authorization_source_user ] mxuser -a -g usergroupname [-d description ] [-p CMSSecurity ||none|+T| -T] [-C authorization_source_user ] mxuser -a -f filename mxuser -a -gf -f filename mxuser -m username [-d description ] [-p CMSSecurity ||none|+T|-T] mxuser -m -g usergroupname [-d description ] [-p CMSSecurity ||none|+T|-T] mxuser -m -f filename mxuser -m -gf -f filename mxuser -r username mxuser -r -g usergroupname mxuser -r -f
rights, users are only allowed access to the listing options of Systems Insight Manager commands. In addition to listing, limited configuration rights users can create tools with mxtool (1M). If you do not specify full rights or CMSSecurity rights for a new user or user group, the default setting is limited configuration rights. Additionally, this command enables a full rights user or CMSSecurity rights user to assign the authorizations of an existing user or group to the new user or group.
Optionally, you can 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 on the system. See http:// www.iana.org/assignments/character-sets for the list of valid character sets. NOTE: For backward compatibility with Service Control Manager 3.0, the -p option also supports the Trusted and Untrusted User +T and -T options.
-l n Display a list of user names (with no details). -l t Display a tabular list of users and user attributes. -l d Display a detailed screen-viewable list of users and user attributes. -l fg Display an XML list of user groups and attributes (see mxuser(4)). -l ng Display a list of user group names (with no details). -l tg Display a tabular list of users groups and attributes. -l dg Display a detailed screen-viewable list of user groups and attributes. username... Specify the user names to list with -l.
NOTE: When duplicate options are specified, the last instance of the option is used. For example, if you enter -f file1 -f file2, mxauth uses file2. 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)).
Example 5 To remove fred from the list of users, enter mxuser -r fred. Example 6 To add the list of users in the local file updates.xml, enter mxuser -a -f updates.xml. Example 7 To display the list of user names, enter mxuser -l. Example 8 To display a detailed screen-viewable list of the users, enter mxuser -l d. Example 9 To display a tabular list of users, enter mxuser -l t.
Description The mxwbemsub command enables you to: • • Add, delete, list, or move WBEM event subscriptions from nodes managed by the CMS. Add or remove health lifecycle event subscriptions for HP NonStop Kernel servers. If you subscribe to health lifecycle events for a NonStop Kernel server, when the server's status changes, notification is sent to Systems Insight Manager and the server status is updated immediately in the GUI instead of waiting for the next status collection.
-l List the WBEM subscriptions for the specified CMS. If a destination is not specified, the default is to list subscriptions to the CMS on which the command is run. -m Move WBEM subscriptions from one CMS to another. If the current CMS is not specified the default is the CMS on which the command is run. The new destination CMS is required. -n nodenames Specify a list of node names. This option is used with -a, -r, -l and -m. -f filename Specify a list of node names with a file.
Example 5 To list WBEM event subscriptions from the nodes mycomputer, and yourcomputer, enter mxwbemsub -l -n mycomputer yourcomputer. This command lists subscriptions whose destination is the CMS on which the command is running. Example 6 To list subscriptions with the destination destinationcms from the nodes mycomputer, and yourcomputer, enter mxwbemsub -l destinationcms -n mycomputer.ak.hp.com yourcomputer.ak.hp.com. Example 7 To move WBEM event subscriptions from the nodes mycomputer.ak.hp.
Linux mxnodesecurity(8) 130 Command descriptions
3 Infrastructure management using CLI Inventory management Configuring Systems Insight Manager Before adding systems to Systems Insight Manager, you must set up and configure the protocols that communicate with the managed systems. The mxglobalprotocolsettings command enables you to set most of the available Systems Insight Manager protocol settings. The mxnodesecurity command enables you to set Sign-in, WBEM, SSH, WS-MAN, and SNMP credentials on a per-system basis.
You must provide the -p and -c parameters. The -n parameter is optional. If you provide the –n option, the credential applies only to the selected system. If not provided, the WBEM credential is added as Default/global credential for sign-in protocol in the global protocol settings. You can also use an XML file with the mxnodesecurity command to add the credentials for WBEM and SNMP for a list of systems. For example: # mxnodesecurity –a –f credential.xml The credential.
The syntax to modify and re-identify systems is: # mxnode –m nodeName1 nodeName2 # 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, 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.
# 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.
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. There are many predefined report categories in Systems Insight Manager. A report category contains a logical grouping of reportable items. The mxreport command enables you to define your own report categories. Run the following command to define your own report categories: # mxreport –c –f categories.xml Where categories.
• • • 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.
In earlier releases of Systems Insight Manager, you could not create or alter categories using the mxquery command. Beginning with Systems Insight Manager 5.0, collections are an extension of categories, you can manage with the mxcollection command. The mxcollection command enables you to select members individually by name. You must continue to use the mxquery command to the search attributes when creating and managing queries.
# mxquery –l val ProductByName There are two additional options for the mxquery –l command. • The n option displays a list of all the query collections in Systems Insight Manager. • The t option displays all the query collections in a tabular format, showing the query ID, query name, query type, and query owner. To create a new query collection in Systems Insight Manager, first create a file that contains the XML definition for the query collection.
The mxcollection command enables you to manage the Systems Insight Manager collections and help organize query collections. To display all the collections in a hierarchical tree, use the following command: # mxcollection –ln The hierarchy shown at the beginning of this section is the output of the above command.
As shown in the hierarchy above, both the Systems and Events collections contain a sub-collection called Shared. The items shown for the Shared collection are the same as what is shown above in the hierarchy list, with one notable exception.
remove the collection itself, use the –d CollName option, where CollName is the name of the collection you want to remove. The following example creates a new collection called Test Collection with two members, the Test Query collection and one server. The collection is placed under Systems by Type in the hierarchy. PAGE 142command also enables you to move WBEM subscriptions from one CMS to another. The command syntax is: # mxwbemsub –m [currentCMS] newCMS –n nodenames # mxwbemsub –m [currentCMS] newCMS –f nodefile.txt This command moves the WBEM subscription from currentCMS to newCMS for the systems on the command line (using –n), or for the systems in the text file (using –f). The parameter currentCMS is optional, and if omitted the WBEM subscription is moved from the current system to newCMS.
then appends the key to the authenticated keys file. The user identified in the mxagentconfig command, must be a valid user on the managed servers. Also, you must execute this authentication process on the CMS so that the DTF can execute the tools on the CMS. The following command pushes the SSH public key to the identified user on one or more managed servers: # mxagentconfig –a [–n host] –u login [–o host | user] [–p password] # mxagentconfig –a [–n host] –u login [–o host | user] [–p password] [–f file.
Manager. If the tool toolname requires any parameters, then you must use one of the –A or –f options. — Use the –A option to list the task parameters, tparams, on the command line. — Use the –f tpf.xml if the parameters defined in the tpf.xml file. As the file name implies, the parameters are defined in XML format as defined in the man page mxtask(4). If you use the –o towner parameter, the new task is owned by towner. The default owner is the user that is running the mxtask command.
To remove an existing task, enter: # mxtask –r taskname Where taskname is the name of the task you want to remove. To run an existing task immediately, enter: # mxtask –e taskname To change the owner of a task, use the –o option, for example: # mxtask –o taskname newowner In this example, newowner, an existing user in Systems Insight Manager, becomes the owner of the task taskname. To execute this command, you must have the authorization to change task ownership (see “Managing users and authorizations”).
• • • The –h option suppresses the job information headers and sends job output directly to stdout and stderr as appropriate. The –O option directs all stdout and stderr output to the file. If the command cannot create the file in the specified path location, Systems Insight Manager attempts to open the file in /var/ tmp. If that fails, all tool output is sent to stdout. The –o option creates one result file for each target system in the directory dir.
— — Use the –i option to display the data for any job associated with for one or more task names. Use the –j option to display information for one or more job IDs. The -j option is not needed in conjunction with -l n, because the -l n option only displays job IDs. • Use the –d date option to limit displaying information to those jobs that completed after the date parameter.
and –r options, replacing the user name or user group name with –f file. Another benefit to using a file is that you can define more characteristics for the users and groups. For example, you can specify e-mail and phone contact information for each user. For details on the XML syntax, see the mxuser(4) man page. There are several ways to display user information on the screen. You can also save user information in an XML-formatted file.
# mxngroup –m –g grpname [–d description] [–n [member1 member2 â ¦]] [–u [t|f]] If you do not provide both the optional –d and –n parameters, then the group is not modified. • Using the –d parameter replaces the existing group description with the one you provide. • Using the –n option is only recommended for groups that have very few entries because you must list the systems in the same order as they were added, with new system names in the place of the systems they are replacing.
operatng systems. This enables HP-UX and Windows administrators using Systems Insight Manager to only see the tools they need. Systems Insight Manager has four predefined toolboxes, All Tools, Monitor Tools, Full Rights, and Limited Rights. • All Tools contains all the predefined tools, and cannot be modified. • Monitor Tools contains tools that monitor, display, view, and report information, and can be modified. • Full Rights toolbox contains all the tools in the Central Management Server.
Do not add tools to the Monitor Tools toolbox that provide root or administrator level functionality. This toolbox is assigned to the operator and user templates, and these tools run with root or administrator access on the CMS. Managing authorizations The mxauth command enables you to add, remove, or list authorizations in Systems Insight Manager. For a complete description of mxauth, see mxauth man page.
• • • The mxinitconfig, or mxinitconfig –l commands display the configuration status, including kernel parameter checks, database setup, web server setup, and thirteen other items. The –a parameter configures Systems Insight Manager starting the web services and Systems Insight Manager services, and initializes the database. The –r parameter removes all configuration information from Systems Insight Manager by stopping all services and removing the database.
• • • • • • • • • The –a action option displays the action that occurred. If this option is not used, the action START is used by default. Valid values include ACTION_NONE, ADD, MODIFY, DELETE, RUN, LIST, ENABLE, DISABLE, RESTORE, SAVE, SETUP, UNSETUP, START, and DONE. The –m message option is the specific message to be logged. This message will appear on the line after the log entry in the log file. The –n appl option is the name of the object or application that is making the log entry.
Systems Insight Manager settings The mxglobalsettings command sets and displays global settings stored in the file /etc/ opt/mx/config/globalsettings.props on HP-UX and Linux, or in the Systems Insight Manager installation directory under config\globalsettings.props on Windows. This file is a text file that contains configuration data and their default values.
# mxpassword –a –x key1=value1 [–x key2=value â ¦] # mxpassword –a –f file • • The –x option assigns password value to password key name key. There can be multiple key and value pairs provided to the add command. The –f option adds the passwords defined in the file. This is a more secure option because the passwords are not available for viewing on the terminal screen, or in the command line history.
4 Support and other resources Information to collect before contacting HP Be sure to have the following information available before you contact HP: • • • • • • Software product name Hardware product model number Operating system type and version Applicable error message Third-party hardware or software Technical support registration number (if applicable) How to contact HP Use the following methods to contact HP technical support: • In the United States, see the Customer Service / Contact HP United Stat
Typographic conventions Book Title Title of a book or other document. Linked Title Title that is a hyperlink to a book or other document. http:// www.hp.com A Web site address that is a hyperlink to the site. Command Command name or qualified command phrase. user input Commands and other text that you type. computer output Text displayed by the computer. Enter The name of a keyboard key. Note that Return and Enter both refer to the same key.
Index A about the CLI, 11 authorizations systems, 147 tools, 147 user, 147 C CLI command descriptions, 17 logging in on the CMS, 14 logging in remotely, 14 signing out, 15 collections criterias, 136 private, 136 shared, 136 commands install locations, 11 summary, 12 configure Systems Insight Manager, 151 credentials, 131 configure, 141 D devices third-party, 135 discovery task, 132 Distributed Task Facility, 142 E event management alerts, 141 I initialize Systems Insight Manager, 151 install location co
Systems Insight Manager, 152 SNMP managed systems, 142 support, 158 system group, 148 create, 148 System Type Manager, 135 T tasks create, 142 manage, 143 schedule, 142 toolboxes, 149 add, 150 modify, 150 remove, 150 U users managing, 147 V viewing manpages, 11 W WBEM managed systems, 141 System Fault Management, 141 160 Index
