HPSystemsInsightManager6.
© Copyright 2010, 2011 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.
Contents 1 About the HP Systems Insight Manager command line interface......................10 Introduction............................................................................................................................10 Commands............................................................................................................................10 manpages (manual pages)..................................................................................................10 Command list.......
Options............................................................................................................................28 Return values.....................................................................................................................29 Examples..........................................................................................................................30 See also........................................................................................................
Files.................................................................................................................................45 Examples..........................................................................................................................45 mximport...............................................................................................................................45 Synopsis................................................................................................
Limitations.........................................................................................................................74 mxnodesecurity......................................................................................................................74 Synopsis...........................................................................................................................74 Description.................................................................................................
Dependencies...............................................................................................................92 Reconfigure SQL Redirect Command....................................................................................92 Name..........................................................................................................................92 Synopsis......................................................................................................................
Description......................................................................................................................112 Options..........................................................................................................................114 External influences...........................................................................................................115 Return values.......................................................................................................
Managing users and authorizations........................................................................................147 Managing users..............................................................................................................147 Managing system groups..................................................................................................148 Managing toolboxes........................................................................................................
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.
Command Functionality Available manpages mxuser Adds, modifies, removes, or lists users. mxuser also enables you to assign authorizations for created users and user groups. mxuser(1M, 8), mxuser(4) mxwbemsub Enables you to add, list, delete, or move WBEM event mxwbemsub(1M, 8) subscriptions from systems managed by the CMS. This command requires access to a file that enables only administrative rights user access.
configuration rights or limited configuration rights on the CMS).
To log out from the CLI, log off of the CMS or the Secure Shell (SSH) client application.
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 (.
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.
-c Check whether a managed system is configured for CMS access. -n hostname Specify the hostname of a system to manage. If this option is not specified, the default is the CMS. -o user|host Specify whether to configure the managed system with SSH host-based authentication or user key-based authentication. If this option is not specified, the default is host-based authentication. -u login Enter the user name to enable SSH execution. -p password Enter the password of the specified user on the managed system.
Managed system: • ~/.ssh/..dtfSshKey.pub • ~/.ssh/authorized_keys2 • ~/.ssh/authorized_keys2.bak Example To copy the SSH-generated public key from the CMS to the system system1 with the username root and password password, enter mxagentconfig -a -n system 1 -u root -p password. See also HP-UX mxexec(1M) Linux mxexec(8) NOTE: Care must be taken when specifying passwords on the command line.
Asterisks are supported for the groupname parameter. Systems Insight Manager recognizes the asterisk as a wildcard character to indicate adding the system group authorization for all currently configured system groups. When using the wildcard character on the command line, enclose it in quotation marks to prevent the shell interpreter from preprocessing it.
XML file support The mxauth command enables you to add or remove authorizations by specifying an XML file containing a list of authorizations. See the Examples section and the mxauth(4) manpage for more information. XML input files are processed in three passes: 1. The first pass attempts to parse the XML file and generate a list of authorizations to process. This pass ensures that the XML file is formatted correctly, and the authorization objects contain syntactically valid information.
-n nodename Specify the system name for the authorization. The wildcard character (*) is supported for nodename. -g groupname Specify the system group name for the authorization. The wildcard character (*) is supported for groupname. This option does not support user groups. 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.
The first section in my_auths.xml gives user1 the toolbox webadmin on node1.corp.com. The second section gives user2 the toolbox operator on node1.corp.com. The third section gives user3 the toolbox dbadmin on node2.corp.com. The fourth section gives user4 the toolbox All Tools for the node group All Managed Systems. Example 2 To add the system authorization allowing user bill to execute any tools assigned to the webadmin toolbox on system web01, enter mxauth -a -u bill -R webadmin -n web01.
Limitations • This command can only be run on the CMS. • You can remove an authorization that does not exist. This operation results in a return value of 0. • An authorization is nonexistent if all of its attributes (user name, toolbox name, system or system group name) are valid Systems Insight Manager objects, but they are not associated as an authorization. • It is not an error to add an authorization that already exists in Systems Insight Manager. This operation results in a return value of 0.
Create a new server certificate. -n [CN=x] [ALT=x] [OU=x] [O=x] [L=x] [ST=x] [C=x] -n [CN=x][ ALT=x] [OU=x] [O=x] [L=x] [ST=x] [C=x] Create a new server certificate with the provided details, where x represents CN=common_name, ALT=alternative name(s), OU=organizational_unit, O=organization_name, L=location, ST=state, and C=country-code. -i [ filespec ] Import a signed server certificate from the specified file.
Return values Value Meaning 0 Successful completion. 2 Command line syntax error. >0 An error occurred during operation. Examples Example 1 To create a new server certificate with the specified X.509 distinguished name, enter mxcert -n CN=Bob O=BobCo L=Anytown C=US A=alt . Example 2 To import a trusted certificate called sample.cert into the keystore, enter mxcert -t -f sample.cert. Example 3 To list the certificates in the keystore (short format), enter mxcert -ln.
NOTE: In earlier Systems Insight Manager releases, categories were created and manipulated with mxquery . In Systems Insight Manager 5.0 and later, collections are an extension of categories, and are managed with mxcollection, which enables you to choose members individually by name. You can continue using mxquery to manage collections that are created by specifying member attributes. • mxcollection -a -f filename This command enables you to add collections and collection members.
NOTE: You can move collections within the Systems list or the Events list, but you cannot move collections from one list to another. • mxcollection -cp existcollname -name newcollname -to toparentcollname [-branch sysbranch|evbranch ] This command copies an existing collection, renames it, and assigns it to an existing parent collection. Use -branch to specify whether the parent collection is in the Systems or Events list in the System and Event Collections panel.
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. -parent fromparentcollname Specify an existing collection to be the parent collection name. This option is used with -a como. -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 31Description 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 systems and system groups. A tool and its arguments, specified to run on one or more systems, is called a task. An instance of the task running at a particular time is called a job. The first form of the command enables you run Systems Insight Manager tools. The toolname is required by mxexec to run the tool.
NOTE: The default location of the log file is /var/opt/mx/logs/mx.log. A user is authorized to run a tool on a system if all the following are true: • The user is a valid Systems Insight Manager user (see mxuser(1M)). • The tool is assigned to a toolbox (see mxtool(1M)). • The user is authorized to have that toolbox on that system (see mxauth(1M)). Tool authorization is all or none, meaning that it will fail if the user is not authorized to run the tool on all systems in the target list.
• INIT_STATE • PATH A number of environment variables are set automatically by the POSIX shell (/usr/bin/sh). See the sh-posix(1) manpage for more information. Tool execution states For every target system, a job goes through the following states that track the progress of the job on each system: • Pending. The job has not started on this system. This state is used when there are a large number of target systems and the CMS DTF is only able to run a job in parallel on a smaller number of systems.
• The DTF has a limit of ten simultaneous job executions. If ten jobs are already executing and another is requested (via mxexec or the portal), the new job will pause until one of the currently executing jobs is finished. If the currently executing jobs take a long time to complete (they are doing lengthy tasks such as installing a large software package using SD, or creating a recovery image using I/UX), the new job could pause for a long time.
the output file cannot be created in the given path, Systems Insight Manager tries to write the file to the /var/tmp directory. If that fails, the output is sent to stdout. -o directory Save the stdout and stderr data produced by the tool execution, one results file per target system, in the specified directory . The name of each results file is in the format nodename.job_ID. -n target [target...] Specify the names of the managed systems and system groups on which to execute the tool.
External influences The language setting of the command shell in which you execute this command is used as the preferred language that you want the command line tool to execute with on the target systems. For Windows operating systems, the current Code Page setting of the Command Prompt window is used to determine the preferred language. For example, if the chcp command returns 932, the language is Japanese.
Examples Example 1 To check the disk space on the database system group, dbgroup, which includes the systems db1, db2, and db3, enter mxexec -t "bdf" -n g:dbgroup. The output might look like: Running tool bdf with job id 143 Job ID : 4 Tool Name : bdf Job State : Some Failures User Name : root Start Time : Wednesday, March 15, 2000 3:18:46 PM MST End Time : Wednesday, March 15, 2000 3:18:47 PM MST Elapsed Time : 500 milliseconds Node : db1.myco.
Status : Complete Exit Code : 1 STDOUT : ======= 09/15/99 16:19:56 MDT BEGIN swinstall SESSION (non-interactive) * Session started for user "bozo@machine2.myco.com". * Beginning Selection * Target connection failed for "depotsys.myco.com:/patches/PHCO_98765". * Selection had errors. ======= 09/15/99 16:19:56 MDT END swinstall SESSION (non- interactive) STDERR : ERROR: More information may be found in the daemon logfile on this target (default location is machine2.myco.com:/var/adm/sw/swagentd.log).
Specifies the password. Minimum allowed length is 8 characters. If password is not specified along with the command, you will be prompted to enter the password. This prevents the clear text password from being exposed to unintended eyes.The same password is needed to carry out import on another server in future. Prerequisites 1. 2. 3. 4. 5. You must be a member of the local Windows Administrators group. The source server has HP Insight Control Suite 3.
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.
Display the path to the PostgreSQL program directory (HP-UX only). Return values Value Meaning 0 Successful completion. >0 An error occurred during operation. 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.
Return values Value Meaning 0 Successful completion. >0 An error occurred during operation. Example To view information for the host rose.co.com, enter mxgethostname -n rose.co.com. mxglobalprotocolsettings Manages global protocol settings in Systems Insight Manager. Synopsis mxglobalprotocolsettings -s [-f file-name|- ] mxglobalprotocolsettings -s {setting=value}...
Examples Example 1 To list the global protocol settings in detailed format, enter mxglobalprotocolsettings -ld. The output might look like: Ping type = ICMP Default ping timeout (in seconds) = 5 Default ping retries = 2 Enable WBEM = true Enable HTTP and HTTPS = true Enable SNMP = true Default SNMP timeout (in seconds) = 5 Default SNMP retries = 1 Enable DMI = true Example 2 To list the global protocol settings in XML format, enter mxglobalprotocolsettings -lf. The output might look like:
Set one or more global settings on the command line. The setting is a key name in the globalsettings.props file, and the value is the value to assign to that setting. -f Use -f with -s, to force the creation of new settings in globalsettings.props without prompting for confirmation. Without this option, mxglobalsettings prompts you to confirm the assignment of values to previously undefined settings. -ld List global settings in name = value format.
mximport enables you to perform the data migration import functionality. This is used to import data from an installation of HP Insight Control Suite 3.0 or later to an installation of HP Insight Control Suite 6.0. This tool takes a zip file as input Options mximport recognizes the following options: • -f Specifies the name of the zip file. If a file name is not specified, the zip file will be read from Systems Insight Manager's installed location \data\configdata-import with name as Products.zip.
2. Homepage,iLO or Onboard Administrator for Single sign-on. See “Configure and repair agents” (page 47) for more details. After migrating to Systems Insight Manager 6.0, sign in to Systems Insight Manager, and run the Daily System Identification task to ensure that all your associations are updated correctly. To run the daily identification task: 1. 2. 3. Select Tasks & Logs→View All Scheduled Tasks. The All Scheduled Tasks page appears. Select the Daily Identification task. Click Run Now.
1. 2. Create subscription to WBEM events: XML Property name : argument_wbem Default value : yes Other allowed values : no Configure SNMP: Set read community string: XML Property name : argument_snmpread Default value : public Other allowed values : any allowed string This will also enable the SNMP communication between Systems Insight Manager CMS and the SNMP agent on the managed system. 3.
Note: If this property is set as false, you must configure the credentials separately. The credentials configured using this option are applied to all systems. The Configure or Repair Agents Query XML have the full DNS names or names of all the discovered managed systems. The value tag can be removed, added, or modified based on your choice. Note: If full DNS name is not present for a system, its system name must be specified. the IP address of the managed system is not allowed to specify for the value tag.
• mxinitconfig -a This command performs the initial configuration procedure. The following steps are performed during the initial configuration: • ◦ The initialization file and property file are set up. ◦ The database is configured. ◦ The server daemons are started. ◦ The local system is configured to allow management by the server. mxinitconfig -r This command removes the Systems Insight Manager configuration information. The following steps are performed: • ◦ The server daemons are stopped.
Examples Example 1 To configure the server, enter mxinitconfig -a. Example 2 To view the current configuration status, enter mxinitconfig -l. mxlog Logs or prints a log entry.
-n object_name Specify the name of the object or application that is making the logging call. You must specify a value if -n is used. If -n is not used, the default is NONE (which appears as a "<>" string). The value must be a string, and if it includes spaces, it must be enclosed in double quotation marks. If this option is not specified, the default is NONE. -o object_type Specify the type of object or application making this logging call. You must specify a value if -o is used.
Examples Example 1 If the user Fred is logged in to SuperApp, which runs as root, and SuperApp wants to log a WARNING message that a configuration file is missing, enter mxlog -l -v "WARNING" -o "APPLICATION" -n "SuperApp" -u "fred" -m "/opt/superapp/superapp.config file is missing.". The output will be: 2005-08-08 13:13:07 MDT APP fred START APP SuperApp START SUCCESS WARNING /opt/superapp/superapp.config file is missing.
-t mib List the traps in filename.mib . The filename is the name listed in Systems Insight Manager and can be viewed by entering mxmib -l. Return values Value Meaning 0 Successful completion. 2 Command line syntax error. >0 An error occurred during operation. Examples Example 1 To view the list of registered mibs, enter mxmib -l. Example 2 To register the mib testmib.cfg, enter mxmib -a testmib.cfg. Example 3 To update a MIB file in Systems Insight Manager, complete the following steps: 1. 2.
Manager. System groups can have overlapping memberships, so a single system can be a member of more than one group. The system grouping mechanism enables flexible partitioning of systems into logical collections that match their use model. When a system group is created, its attributes and membership can be specified. When it is modified, its attributes can be selectively modified, its membership can be reset, and it can be updated based on a collection.
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. XML file support The mxngroup command enables administrative rights users to add, modify, or remove system groups by specifying an XML file containing a list of system groups and system group attributes. See the Examples section and the mxngroup(4) manpage for more information. XML input files are processed in two passes: 1.
System group names must be 80 characters or less, and must start with an alphabetic character. After the first character, system group names can contain alphanumeric, underscore (_), dash (-), period (.), and embedded blank characters. -n member When used with -a or -m, this option specifies the complete membership of an added or modified group. When used in a list command (-l), this option indicates that the system groups to be listed contain the specified members.
Examples Example 1 To create the system group group1 containing systems systema, systemb, and systemc, enter mxngroup -a -g group1 -d "Example system group" -n systema systemb systemc. Example 2 To modify the system group group1 by replacing system systemc with system systemd, enter mxngroup -m -g group1 -n systema systemb systemd. Example 3 To update group group1 enter mxngroup -m -g group1 -u.
Limitations • This command can only be run on the CMS. • Only administrative rights users can use mxngroup to add, modify or remove system groups. Any user can list group information. See also HP-UX mxngroup(1M), mxuser(1M), mxnode(1M), mxauth(1M) Linux mxngroup(8), mxuser(8), mxnode(8), mxauth(8) mxnode Adds, modifies, identifies, removes, or lists systems in Systems Insight Manager.
• When a system is added to the database with the -a option, mxnode stores the system name, the fully-qualified network hostname (if it exists), and an IP address as system attributes. • The system is identified, meaning it is examined via the SNMP and WBEM management protocols to determine the device type, the operating system type and revision, and other information needed to determine which tools are appropriate for use with the system.
which may reside on this system or another system. One or more MPOs can reside on a system. • -lf provides an XML list of systems. 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.
• Preferred Node Name . An alternate system/node name of your choosing which can make it easier for you to identify, find, or organize systems/nodes in the database. • System Description . A description of the system. • Serial Number . The serial number of the system. • Asset Number . The asset number of the system. • OS Description . The description of the system's operating system. • Contact . The person to contact if system maintenance is needed. • Location .
System attributes are categorized into two groups, hardware and software. When specifying an attribute in an mxnode XML input file, the correct attribute modifier must be used. The following examples show the two attribute modifiers: • The Device Type attribute is a hardware attribute and is specified in the XML file by using the hw-attribute modifier: Device Type here.
• 64 GUI name mxnode attribute name Environmental Monitor Env Complex Complex Handheld Handheld Partition Partition Power Supply PowerSupply Thin Client ThinClient Storage Device Storage Server Server Desktop Desktop Workstation Workstation Notebook Portable Router Router Cluster Cluster Printer Printer Switch Switch Hub Hub Remote Access Device RAS Unknown Unknown Management Processor MgmtProc Tape Library TapeLibrary Shared Resource Domain SRD Resource Partiti
GUI name mxnode attribute name HP Omnibook HPOmnibook HP Visualize HPVisualize select HP Integrity Server HPIntegrityServer HP Virtual Partition vPar Unconfigured HP System HPUNCFG HP Alpha Server HPAlphaServer Virtual Machine Guest VMGuest HP BladeSystem p-Class p-Class HP BladeSystem e-Class/CCI e-Class SMI SMI HP Workstation HPWorkstation NonStop Server HPNonStop Blade Blade HP Evo HPEvo Storage Storage HP Server HPServer HP BladeSystem BladeSystem H
GUI name mxnode attribute name HP Integrity Virtual Machine HPVMGuest Guest HP Serviceguard Cluster Member HPSGCMember • Model (Model) . The device model. Any displayable text can be used as a value for this attribute. • Serial Number (SerialNumber) . The serial number of the system. Any displayable text can be used as a value for this attribute. In addition to the predefined options, Systems Insight Manager plug-in extension applications can define their own system attributes.
to take up to several minutes or longer, depending on the total number of systems being added. As a result, 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 you want to use XML input to remove one or more existing MPOs from a system. Any system's existing MPO that is omitted from the XML MPO section is removed from the system, thus the "pruning" operation.
Value Meaning 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 Database error. 221 Authentication failure. 222 The CMS is not initialized. 224 System installation error. 249 Unable to connect to the session manager. 250 Remote exception. 252 File input parsing error.
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 UUID: n...
attribute lock flags must be set to false, as shown below. Otherwise, all three attributes must be set to true. false false false NOTE: Attribute lock flags can also be modified through the Edit System Properties page of the GUI.
L your data here info here false L your data here L your data here L your data here L your data here L your data here L
An MAO defines and supports a management agent such as a CIMOM or SNMP agent. The MAO contains information specific to accessing the agent, which includes attributes such as agent type, port number, and the IP address by which it was accessed. An MRO provides the information required to access an agent (MAO). An MRO always has an associated MAO included in its overall information. An MRO on a system points to an MAO residing on the same system, or another system.
hpmxCimomMro nnnnnnnnnnn Switch root .... nn...nn nnnnnnnnnnn nn...
MyPhone MyEmail MyOther Notes • When modifying a system with the mxnode -m -f filename command, your XML file must include only the attributes you want to modify. You must always include the three attribute lock flags and set all three flags to true or false.
Description The mxnodesecurity command enables a CMS user to add, list, or remove default/global and node/system credentials in the CMS. All credentials are stored in the Systems Insight Manager database. The difference between default and system type credentials are: • Default (or Global) Credentials that apply to all managed systems. • Node (or System) Credentials that apply to specific managed systems.
credential in Systems Insight Manager database. If the credential exists in the database, the credential is deleted. 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. You can use [-x fd] to forcefully remove an in use credential. However, removing an in use credential might interrupt communications between the system and Systems Insight Manager.
Remove credentials from the Systems Insight Manager credentials database. This option must be used with -f or -p. -l List system security credentials on the screen. This option can be used with -p and -n options. -f filename Use an XML file to specify the credentials to add, modify, or remove. -p protocol Specify a protocol such as WBEM or SNMP. Credentials of the specified type are displayed on the screen. This option is used with -a, -r, and -l.
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 system 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 mycomputer.ak.hp.com.
and nodename), then a modify operation is automatically performed on the credential and the username and password are updated. NOTE: A system name is not specified when adding default or global credentials. Default credential names use the format @defaultN, where N is an automatically assigned numerical indicating usage. Example 6 To add a default SNMP protocol credential to the system security repository, enter mxnodesecurity -a -p snmp -c readname:writename.
Limitations • This command can only be run on the CMS. • For an HP-UX or Linux CMS, this command can be run only by the root user. See also HP-UX mxnodesecurity(4), mxngroup(1M), mxauth(1M), mxuser(1M), mxinitconfig(1M), mxnode(1M) Linux mxnodesecurity(4), mxngroup(8), mxauth(8), mxuser(8), mxinitconfig(8), mxnode(8) mxoracleconfig Configures Systems Insight Manager to use an Oracle database.
-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. See also HP-UX mxinitconfig(1M) Linux mxinitconfig(8) Example To configure Systems Insight Manager to use Oracle database hpsim50 on server oradbsrv11x with user id sim, password simpw, and the Oracle thin driver jar file ojdbc14.
-m Modify an existing password. -r Remove an existing password. -l List the passwords stored by Systems Insight Manager. -g Start the mxpassword GUI. IMPORTANT: An error might occur if you use -g in a non-graphical environment (such as a telnet session). -x key [ =value ] The key is the name of the password, and the value is the new value of the password in text format. -n Create a new server certificate.
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. Example 6 To add, modify or remove passwords using a graphical user interface, enter mxpassword -g. Example 7 To add the passwords myPw1 and myPw2 with the values myPw1Value and myPw2Value, enter mxpassword -a -x myPw1=myPw1Value -x myPw2=myPw2Value.
Optionally, you can specify the force flag, which instructs the system to add a query's criteria even if there is not a database entry corresponding to the criteria value. This affects only criteria values that are selected from a list of values stored in the database, such as system names. • mxquery -l val CriteriaByEventType This command enables you to view a list that includes sub categories for the event types when applicable.
• mxquery -l crit This command lists the names of criteria that can be specified for a query. Criteria specify the search values that Systems Insight Manager uses when executing a query. Some criteria have a list of defined values that must be used when specifying that given criteria. This command lists the criteria name and the query type in which the criteria can be specified. • mxquery -l mode criterianame This command lists the operation modes or operators that are valid for a specified criteria.
-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. criterianame Enter the name of an existing criteria for which you want additional information, such as operation modes or defined values. -x Specify an extended option value. This is used with the following keywords. force Force a query into the system when used in conjunction with -af / -mf.
Value Meaning 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 2 To modify queries based on the query definition file /home/user1/defs/myquerymods, enter mxquery -m -f /home/user1/defs/myquerymods. Example 3 To remove the query badquery, enter mxquery -r badquery.
See also HP-UX mxauth(1M), mxquery(4) Linux mxauth(8), mxquery(4) mxreconfig Name mxreconfig —m password Updates and changes the host CMS installation credentials, and prompts you for the old and new passwords. Synopsis mxreconfig -m password [-v] Options or Arguments -m Required option that prepares the mode to be set. password Specifies password mode. -v Specifies verbose output, which providves extra visual task progression output to the console.
• HP Insight Control server migration Application Service • HP Insight Control server migration Web Service • HP Insight Control virtual machine management • HP Insight Orchestration • HP Logical Server Automation • Systems Insight Manager • System Management Homepage • OpenSSH Server • Stored credentials IMPORTANT: Verify that all jobs related to Insight Software are finished before running this command. If the SMH is open, close it.
Reconfigure Host Command Name mxreconfig -m host Updates and changes CMS host and IP attributes. Synopsis mxreconfig -m host Options or Arguments -m Required option that prepares the mode to be set. host Opens host mode. Description This command enables you to realign the Systems Insight Manager host name and IP address with the operating system after the operating system host name or IP address has changed.
Dependencies All of the following must be true: • Systems Insight Manager is installed and configured on a Windows operating system host, using Microsoft SQL. • The hostname for the operating system was changed using standard Windows configuration tools. • The host is still in the same domain. • All credentials are known. • The new hostname can be resolved by the DNS server. • The new IP address is valid (assigned by DHCP if enabled on the CMS and is the IP address assigned to the CMS.
Option specifies verbose output, which provides extra visual task progression output to the console. Description The mxreconfig —m dbauth —a db-user-name command enables you to change the credentials Systems Insight Manager uses to access the CMS database. In other words, if the user name used to logon to the database associated with Systems Insight Manager must be changed, use this command to change the user name that Systems Insight Manager uses to access the database.
Synopsis mxreconfig {-m sqlredirect} { -s } {-b } [-p ] [-a] [-v] Options and Arguments -m Required option that prepares the mode to be set. sqlredirect Specifies database reconfiguration mode. -s Required option that indicates a database server name. The name of the server on which the new database resides. -b Required option that indicates the name of a new database The name of the new database.
NOTE: The parameters —s and —b and their arguments are required. The parameters —p and —a and their arguments are optional. Use the —a parameter and argument to set the credentials for access to the new database as different from the current user. IMPORTANT: This command is applicable to HP SIM only. This command does the following: • Stops all installed HP SIM partner services. • Redirects the CMS to use the new SQL database.
existing-event-collection-name ] [-x HTML|XML|CSV] [-o fully-qualified-file-name ] mxreport [-b encoding ] [-n valid-report-or-category-name ] -l -x [report|category] Description The mxreport command enables users with sufficient privileges to run reports, and to add, delete, and list reports and report categories. • mxreport -a -f fully-qualified-file-name This command enables you to add reports if you have sufficient privileges.
[-E existing-event-collection-name ] [-x HTML|XML|CSV] [-o fully-qualified-file-name ] This command runs a report from an existing category. • ◦ The category name is mandatory. ◦ -S is mandatory. If you want to enter a comma-separated list of system names instead of a collection for -S, enter -n before -S and type the names on the command line. ◦ Selecting an event query is optional. ◦ -x specifies the generated report file format. The default is XML. ◦ -o specifies the output file path.
-x Select the output type (HTML, XML, or CSV) for the -e option. -o Specify an output file for the -e option. -l -x List all predefined report names. report List all predefined report names with -l -x. category List all predefined report category names with -l -x. -b Specify the character encoding for reports and report categories listed with -l -x. -n valid report or category name Specify the name of an existing report or report category to list with -l -x.
Value Meaning 4 User/client does not have sufficient privileges to execute the command. 6 No valid licenses exist for the command. 7 Command has not completed execution. 8 Security token was not valid. 9 SessionID was invalid. Can only be returned from status() calls. Examples Example 1 To add the reports defined in the /home/user1/defs/myreportdef file, enter mxreport -a -f "/home/user1/defs/myreportdef".
Example 11 To run a report from the Inventory category with the system name list cmssystem,mycomputer and an event filter All Events, enter mxreport -eCat Inventory -S "cmssystem,mycomputer" -n -E "All Events" -x XML. Limitations This command can only be run on the CMS. See also HP-UX mxauth(1M), mxreport(4), mxcategoryitem(4) Linux mxauth(8), mxreport(4), mxcategoryitem(4) mxstart Starts Systems Insight Manager and the TomCat web server.
the standard command line interface which supports online usage help and a verbose mode to display operation progress. This command supports two main modes of operation. A WAIT mode and a NOWAIT mode. When used in WAIT mode, the command will not return to the caller until Systems Insight Manager is determined to be in a ready state or the internal safety timeout period has expired.
Return values Value Meaning 0 All Systems Insight Manager communications interfaces are in a ready or accessable state. 1 All or some Systems Insight Manager communications interfaces are not ready or accessable. Examples Example 1 To check the current Systems Insight Manager ready/not-ready state in NOWAIT mode, enter mxstatus. Example 2 To check the current Systems Insight Manager ready/not-ready state in WAIT mode, enter mxstatus -w.
Synopsis mxstm -a -n product name -p snmp (-x attribute=value)+ NOTE: Systems Insight Manager 6.0 no longer supports DMI. mxstm -r -n product name mxstm -a -f filespec mxstm -r -f filespec mxstm -l [-n product name ] mxstm -l [-p snmp [-f filespec ] ] Description The mxstm command enables you to add, remove, and list system type manager rules for use with Systems Insight Manager. Options -a Add a new rule. Optionally, use -f to import one or more rules from an XML file.
Rack, RESPAR, Router, Server, SRC, Storage, Switch, TapeLibrary, UPS, Unknown, Workstation, or other values as defined in the nodeTypesEnum table.
See also /opt/mx/dtd/stmrules.dtd mxstop Stops Systems Insight Manager and the TomCat web server. Synopsis mxstop Description The mxstop command stops the Systems Insight Manager daemons. Return values Value Meaning 0 Systems Insight Manager and TomCat stopped correctly. >0 An error occurred while attempting to stop Systems Insight Manager or TomCat. Example To stop the Systems Insight Manager daemons, enter mxstop.
mxtask -rf taskxmlfile Description The mxtask command enables you to list all tasks, list details for a particular task, list task parameters in XML format, execute a task, remove a task, change ownership for a task, and create a task from the command line or an XML file. • mxtask mxtask -lt These commands provide a tabular listing showing the major attributes of all tasks currently registered in the database.
• mxtask -cf taskxmlfile This command enables you to create a new task from information provided in an external task-specific XML definition file. You must be an administrative rights user to run this command. See the mxtask(4) manpage for a description of the task-specific XML format. • mxtask -rf taskxmlfile This command enables you to remove the specified task(s). The information regarding the task(s) is provided by an external task specific XML definition file.
Create a new task. All required task configuration information must be specified in an external file containing task-specific data in the predefined XML format. See the mxtask(4) manpage for a detailed description of the required XML format. -h Display extended help for mxtask. -q queryname Specify the name of an existing query. -w scheduleinfo Specify task schedule data. scheduleinfo is a parameterized string that defines the schedule data.
The T parameter signifies the task type and is required in all type/schedule parameterized strings. Valid [tasktype] values are add, remove, manual or schedule. These task type values determine what type source triggers the task to run. • Tadd. Task runs when systems or events meet the list criteria. • Tremove. Task runs when systems or events no longer meet the list criteria. • Tmanual. Task runs when manually invoked. • Tschedule. Task runs according to a periodic/day/time schedule.
If the OS on the target system does not support the language setting or encoding selected by the CMS, the command shell on the target system will use the default language and encoding for that target's OS. See lang (5), environ (5), and local (1) for additional information. Return values Value Meaning 0 Successful completion. 2 Command line syntax error. 21 Invalid name. 102 Systems Insight Manager repository error. 222 The CMS is not initialized. 249 Unable to connect to the session manager.
Example 8 To create a task named task1 with the associated query query1 and tool toolexample that already exists in the database, with the task type add, enter mxtask -c task1 -q query1 -t toolexample -w Tadd. In this example, there are no tool (user) parameters required for the tool being specified, so -A and -f are not required.
Example 15 To create task1, which runs every 7 days on Tuesday at 6:00 PM, 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.Idays.P7.Dtuesday.M18:00. In this example, there are no tool (user) parameters required for the tool being specified, so -A and -f are not required.
Example 21 To create a new task based on the XML contents of the file test_file.xml, enter mxtask -cf test_file.xml. All required task configuration information must be specified in a predefined task-specific XML format. See the mxtask(4) manpage for a detailed description of the required XML format. The general format is shown below.
If you are not an administrative rights user, Systems Insight Manager ignores the owner specification, sets the tool's owner field to your user ID, ignores the value of the toolbox enabled flag, and enables only the All Tools toolbox. When the owner field is specified, Systems Insight Manager ignores the toolbox enabled flag and disables the tool in all of the specified toolboxes with the exception of All Tools.
ignores the task dependencies of the tool and removes it. You can specify tools as a list of tool names, a list of categories, or a tool definition file. • mxtool -l d|f|n|t [-c category...|-t toolname... ] This command enables you to list tools or view specific tool definitions. • ◦ With no options or the n qualifier, the names of all registered tools are listed. ◦ With the d qualifier, a detailed screen-viewable list of tools is displayed.
-t toolname Specify the name of the tool to be removed or listed. Specifying an undefined tool name results in mxtool operating on zero tools and a return value of SUCCESS. Specifying a tool name that violates the rules for tool names (see mxtool(4)), results in an invalid name return value. -f filename Specify the path and name of a file that contains the definition of one or more tools to be added or modified. This option must be specified with the scan option, -s.
Value Meaning 222 The CMS is not initialized. 249 Unable to connect to the session manager. 250 Remote exception. Examples Example 1 To add the tools defined in the file /home/user1/defs/mytooldef, enter mxtool -a -f /home/user1/defs/mytooldef. Example 2 To modify tools based on the file /home/user1/defs/mytoolmods, enter mxtool -m -f /home/user1/defs/mytoolmods.
Description The mxtoolbox command enables you to add, rename, describe, disable, enable, remove, and list toolboxes. NOTE: The All Tools toolbox is a special toolbox added by the system, and cannot be modified. Only an administrative rights user can add, modify, or remove toolboxes. Any user can list toolbox information. • mxtoolbox -a toolboxname [-d description ] [-e t|f] This command enables you to add a single toolbox.
Optionally, a full rights user 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. Toolbox attributes The following attributes define an Systems Insight Manager toolbox: • toolboxname.
-l t Display a tabular list of toolbox attributes for all toolboxes. -lf Specify that the system should generate the toolbox information in XML format. -b encoding Specify the character encoding of an XML file when used with -lf. -m toolboxname Modify a specified toolbox. -N new_toolboxname Define a new toolbox name for the specified toolbox. -r Remove the specified toolbox.
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.xml, enter mxtoolbox -m -f toolboxlist.xml. Example 4 To remove the HP ASE toolbox, enter mxtoolbox -r "HP ASE". Example 5 To remove the toolboxes in the file toolboxlist.xml, enter mxtoolbox -r -f toolboxlist.xml. Example 6 To list the names of all toolboxes, enter mxtoolbox -ln.
Database Administrator LVM Administrator Limitations • Valid toolbox names cannot exceed 16 characters, but can be as short as a single character. The initial character of a toolbox name must be an uppercase or lowercase letter.
mxuser [-l dg|fg|ng|tg] [ usergroupname... ] mxuser -lf [-b encoding ] [ username... ] NOTE: The following commands are retained for backward compatibility.
the existing description for the user or group. Any modification of the user or group authorizations must be made with mxauth (1M). Users or groups to be modified can be specified on the command line or in an XML file. Use an XML file to modify multiple users or groups at the same time. See mxuser(4) for more information.
valid information. During the first pass, if an error is detected, the process is interrupted, an error message is issued, and the database is left unchanged. If the XML file is successfully processed in the first pass, Systems Insight Manager attempts to process the user list collected during the first pass.
-l dg Display a detailed screen-viewable list of user groups and attributes. username... Specify the user names to list with -l. usergroupname... Specify the user group names to list with -l. -b encoding Specify the character encoding of an XML file when used with -lf. -C authorization_source_user Specify an existing user or user group. This option copies the authorizations of the existing user or group to a new user or group during the add operation.
Value Meaning 5 Duplicate user error. 21 Invalid name. 26 Invalid 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. 252 File input parsing error. 253 Duplicate name. 254 Systems Insight Manager properties file error.
jane joe none none Database Administrator Backup Operator Limitations • Only full configuration or CMSSecurity rights users can add, remove, or modify users. Any user can list information. • Only a unique instance of any user name can be added. Attempting to add a user name that already exists results in an error. • Only existing users can be successfully removed. • This command can only be run on the CMS.
NOTE: • This command accesses a file that enables only privileged user access. mxwbemsub -a [ destination ] (-n node names|-f filename) [-t indication type ] This option enables you to create WBEM subscriptions on a set of systems. This option can specify the destination of the subscriptions. If the destination is not included, then the CMS on which the command is being run is used as the destination.
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 system names. This option is used with -a, -r, -l and -m. -f filename Specify a list of system names with a file. Each system name is entered on a separate line. This option is used with -a, -r, -l and -m. -t indicationtype Specify which type of indications to subscribe to. The only valid value is health.
Example 6 To list subscriptions with the destination destinationcms from the systems 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 systems mycomputer.ak.hp.com, and yourcomputer.ak.hp.com from the default CMS to newcms.ak.hp.com, enter mxwbemsub -m newcms.ak.hp.com -n mycomputer.ak.hp.com yourcomputer.ak.hp.com.
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 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.xml file might contain the following:
# 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 systems to remove. For example: # mxnode –r nodeName1 ipAddress1 nodeName2 # mxnode –r –f nodes.
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. To access help for this command, enter, mxtask –h.
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.xml contains the XML definitions of the categories. For the details on creating the report categories XML definitions, see the man page mxcategoryitem(4).
• 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.
In the example, CriteriaByNameComparison is a text criteria and does not have any values. However, the criteria ProductByName is a selection criteria. To find the values of this criteria, enter: # 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.
AssociatedName: associatedDeviceKey: 0 timeStamp: 1144308295806 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.
To remove members of collections, replace the –a option with –r. Using this option removes all of the members defined in the XML from the collection specified in the file testcoll.xml. To 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.
To list the subscriptions for systems, replace the –a option with the –l option. If you provide the destCMS parameter (optional), the subscriptions for CMS destCMS also appears. The mxwbemsub command 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.
Managed server setup The Distributed Task Facility (DTF) of Systems Insight Manager controls tool execution on managed servers. The DTF communicates with managed servers through SSH. The mxagentconfig command pushes the public key for the CMS to the users SSH key directory on the managed servers, and 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.
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.
• 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.
• The mxuser –r user and mxuser –r –g userGroup commands remove a user and a group, respectively, deleting all authorizations for the user and the group. • The –f file option enables you to add, modify, or remove multiple users and user groups. File contains XML syntax, allowing multiple entries to be processed. Use this option with –a, –m, and –r options, replacing the user name or user group name with –f file.
To modify existing system groups, the syntax is identical to that for adding system groups however, you replace the –a option with the –m: option, for example: # 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.
description of the XML syntax required to manage toolboxes using an XML file, see the mxtoolbox(4) man page. Toolboxes are an integral part of creating authorizations in Systems Insight Manager. A toolbox contains a set o fSystems Insight Manager tools that one or more users can run on the systems they are authorized to manage. An example of using toolboxes is to create a toolbox containing tools that apply only to HP-UX systems and a toolbox containing tools that apply only to Windows operatng systems.
This guide does not discuss the details of creating and managing tools. For more information, see the HP Systems Insight Manager 6.3 user guide on the www.hp.com. However, this guide discusses the highlights of toolboxes. The “Managing toolboxes” (page 149) section discussed how to create toolboxes used in creating authorizations.
Systems Insight Manager configuration There are many commands available to configure the Systems Insight Manager software after it is installed, including service start and stop, connecting to an Oracle database, initializing Systems Insight Manager, and managing trusted certificates. Systems Insight Manager initialization After installing the Systems Insight Manager software, you must initialize Systems Insight Manager. The mxinitconfig command initializes Systems Insight Manager.
Systems Insight Manager log The mxlog command enables you to create an entry in a log file, or to print a log entry to stdout. The basic forms of the command are: # mxlog –l [–r result] [–a action] [–o object_type] [–n object_name] [–u user] [–s sessionID] [–t transactionID] [–v verbosity] [–m message] # mxlog –p[–r result] [–a action] [–o object_type] [–n object_name] [–u user] [–s sessionID] [–t transactionID] [–v verbosity] [–m message] • The –l option logs the entry to the log file.
The mxgetdbinfo command displays information about the Systems Insight Manager database. Without any parameters, the database port, database name, user ID, database type, path to executables, and path to data appear. The following options are supported: • The –a option displays the same output as if you did not provide an option. • The –h option returns the host name of the server where the database is installed. • The –p option returns the TCP/IP port number used to connect to the database.
Where the value 3 requires the use of trusted certificates and the value 1 does not require using trusted certificates. To list the certificates in the key store, use either the –ln or –ld option. For example: # mxcert –ln | –ld • The –ln option lists basic information about the certificate. • The –ld option lists detailed information about the certificates, including certificate fingerprint data.
4 Support and other resources 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, 10 authorizations systems, 147 tools, 147 user, 147 C CLI command descriptions, 16 logging in on the CMS, 13 logging in remotely, 13 signing out, 14 collections criterias, 136 private, 136 shared, 136 commands install locations, 10 summary, 11 configure Systems Insight Manager, 152 credentials, 131 configure, 141 D devices third-party, 135 discovery task, 132 Distributed Task Facility, 143 E event management alerts, 141 I initialize Systems Insight Manager, 152 install location co
Systems Insight Manager, 152 SNMP managed systems, 142 support, 156 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, 10 W WBEM managed systems, 141 System Fault Management, 141 158 Index
