Owner manual
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
The initial command to register the file uses the .cfg extension, but all subsequent commands
refer to the file by its .mib extension.
IMPORTANT: mxmib is order sensitive. While the command enables you to compile MIBs whose
dependencies have not been compiled, for optimal results, HP recommends that you register MIBs
with HP SIM in order of dependency. If you do not compile MIBs in order of dependency, HP SIM
might not properly resolve varbind data for incoming traps from MIB X when a varbind has been
imported from MIB Y that was not registered prior to registering MIB X. MIB dependencies are
typically identified at the top of MIB files in the IMPORTS section ad are discussed in the mcompile
section. Note that failing to compile imported MIBs properly does not block reception of traps; it
only limits the data captured for some traps.
mxmib MIB keyword customization
After using mcompile to parse and validate the source MIB, you can customize the resulting CFG
file for support in HP SIM. Specifically, there are special keywords that can be defined on a per-trap
basis. At the conclusion of this section, there is a full example. The keywords and their usage are
as follows.
--#TYPE
The TYPE keyword provides a way to add a short description of the trap to HP SIM. This short
description can be used when sending a paging message. This enhances the ability to transmit
information without being verbose. This keyword does not provide any functional purpose; however,
it does represent the primary display string for the trap when it is displayed in HP SIM. Note that
while the TYPE field does not need to be unique, but HP recommends that the combination of TYPE
and CATEGORY fields form a unique pair so that this event can be effectively searched for using
the Event by Category/Type search criteria.
--#SEVERITY
The SEVERITY keyword can be used to alter the severity of a trap. The vendor who created the
MIB might have decided that the trap, under most circumstances, only warrants a severity level of
informational. However, you might need to escalate the trap's severity based on operational
importance. Therefore, this keyword overrides default severity. The allowable severity levels are
shown below. Many vendors have different severities specified in their MIBs such as Normal,
Warning, Degraded, Broken, and so on. These severities must be changed in the base MIB or
CFG to one that matches HP SIM. For example, Degraded can be mapped to Minor or Major,
depending on the degradation. Editing the MIB or CFG and doing a search/replace on the
severities is the easiest way to tweak the MIB. HP SIM also provides a GUI to change the SEVERITY
after MIB compilation.
• INFORMATIONAL Events of this type require no attention. They are provided as useful
information.
• MINOR Events of this type indicate a warning condition that can escalate into a more serious
problem.
• MAJOR Events of this type indicate an impending failure.
• CRITICAL Events of this type indicate a failure and signal the need for immediate attention.
--#ENABLE
The ENABLE flag can be set to TRUE or FALSE and can effectively enable or disable a trap from
being processed by HP SIM. The usage for the keyword is either TRUE to indicate that the trap
should be processed or FALSE to indicate that this trap should not be processed. By default, this
keyword is TRUE and should only be explicitly overwritten on an exception basis.
--#CATEGORY
This provides a categorization of the trap for ease of viewing and use in forming HP SIM lists. You
can use predefined categories or, if none of these fit your need, you can create a category befitting
166 Compiling and customizing MIBs