HP Systems Insight Manager 7.0 User Guide
Table Of Contents
- Systems Insight Manager 7.0 User Guide
- Table of Contents
- Part I Introduction
- Part II Setting up HP SIM
- 3 Setting up managed systems
- 4 Credentials
- 5 WMI Mapper Proxy
- 6 Discovery
- 7 Manage Communications
- 8 Automatic event handling
- 9 Users and Authorizations
- 10 Managed environment
- Part III HP SIM basic features
- 11 Basic and advanced searches
- 12 Monitoring systems
- 13 Event management
- 14 Reporting in HP SIM
- 15 HP SIM tools
- Part IV HP SIM advanced features
- 16 Collections in HP SIM
- 17 HP SIM custom tools
- 18 Federated Search
- 19 CMS reconfigure tools
- 20 Understanding HP SIM security
- 21 Privilege elevation
- 22 Contract and warranty
- 23 License Manager
- 24 Storage integration using SMI-S
- 25 Managing MSCS clusters
- 26 HP SIM Audit log
- 27 HP Version Control and HP SIM
- 28 Compiling and customizing MIBs
- A Important Notes
- System and object names must be unique
- Setting the Primary DNS Suffix for the CMS
- Distributed Systems Administration Utilities menu options not available
- Virtual machine guest memory reservation size
- Insight Remote Support Advanced compatibility
- Database firewall settings
- Annotating the portal UI
- Security bulletins
- Validating RPM signatures
- Central Management Server
- Complex systems displaying inconsistency with the number of nPars within the complex
- Configure or Repair Agents
- Data collection reports
- B Troubleshooting
- Authentication
- Browser
- Central Management Server
- Complex
- Configure or Repair Agents
- Container View
- Credentials
- Data Collection
- Database
- Discovery
- iLO
- Linux servers
- Event
- Host name
- HP Insight Control power management
- Insight Control virtual machine management
- HP Smart Update Manager
- Systems Insight Manager
- Identification
- Installation
- License Manager
- Locale
- Managed Environment
- HP MIBs
- Onboard Administrator
- OpenSSH
- Performance
- Ports used by HP SIM.
- Privilege elevation
- Property pages
- Reporting
- Security
- Sign-in
- SNMP settings
- SSH communication
- System Page
- System status
- Target selection wizard
- Tasks
- Tools
- Upgrade
- UUID
- Virtual identifiers
- Virtual machines
- VMware
- WBEM
- WBEM indications
- WMI Mapper
- C Protocols used by HP SIM
- D Data Collection
- E Default system tasks
- Biweekly Data Collection
- System Identification
- Old Noisy Events
- Events Older Than 90 Days
- Status Polling for Non Servers
- Status Polling for Servers
- Status Polling for Systems No Longer Disabled
- Hardware Status Polling for Superdome 2 Onboard Administrator
- Data Collection
- Hardware Status Polling
- Version Status Polling
- Version Status Polling for Systems no Longer Disabled
- Check Event Configuration
- Status polling
- F Host file extensions
- G System Type Manager rules
- H Custom tool definition files
- I Out-of-the-box MIB support in HP SIM
- J Support and other resources
- Glossary
- Index

H Custom tool definition files
Custom tool definition files are XML files that describe how HP SIM should run tasks based on a
program, script, or UTL added by the user. This appendix describes the wuyntax of these tool
definition files (tdef).
Tool type-specific requirements
SSA-specific attributes
An SSA tool executes on a selected target and is only aware of the target system environment. In
executing an SSA tool, the HP SIM Distributed Task Facility (DTF) of the CMS uses SSH to send
one or more files to the target system, which then executes the tool. An example of an SSA tool
would be a tool that wraps a common Unix command such as ls. cat, or cp.
Table H-1 SSA-specific attributes
Description
Syntax
1
Attribute
You should specify only one command
or copy-block or both; however, you
may specify up to 16 multiple
copy-blocks can be specified. After the
command and/or copy-blocks, one may
specify the parameters for the command
and/or copy-block.
<ssa-block> (command/copy-block
attributes) </ssa-block>
ssa-block
Specifies the command for an SSA tool.
If the command accepts parameters,
you must specify the command as a
“Parameterized strings”. This element
may have two attributes: command-type
and log.
<command> (parameters)
</command>
command
Specifies a source file path and a
destination file path for a copy
operation. The source element specifies
the source file path for a copy
operation. The destination element
specifies the destination file path for a
copy operation. The default permission
of the copied block is 755. The chmod
command is required to set a custom
permission.
<copy-block> (attribute data)
</copy-block>
copy-block
1 Replace italicized text between start and stop tags with actual attribute/value/data. Non-italicized text represents valid
entry option. You must specify values for attributes; there are no default values.
MSA-specific attributes
An MSA tool executes typically on the CMS and can work with multiple target systems. When
launched, the MSA process is created once and then passed to all targets on the list. An XWindows
tool is an example of an MSA tool.
MSA command tools must specify a command and the system on which the command will execute.
Tool type-specific requirements 219