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
In this example, TRAP-TYPE and sysName are readily resolved as in the example above.
hpSwitchBladeType2-Mgmt is resolved by mcompile checking HP-SWITCH-PL.MIB. agSlotNumber
is resolved from BLADETYPE2-SWITCH.MIB and ipCurCfgGwIndex is resolved from
BLADETYPE2-NETWORK.MIB.
To illustrate further how imports are resolved — the following procedure is how mcompile would
attempt to resolve the import for hpSwitchBladeType2-Mgmt:
Procedure 28-1 How MIB imports are resolved
1. Search for a file named HP-SWITCH-PL-MIB.mib (module name, uppercase).
2. Search for a file named HP-SWITCH-PL.mib (module name without -MIB, uppercase).
3. Search for hp-switch-pl.mib (convert name to lowercase for case sensitivity in
Linux/HP-UX).
4. Search for hp-switch-pl.mib.mib (convert name to lowercase for case sensitivity in
Linux/HPUX).
5. Report an error indicating that the imported MIB could not be found.
A major consideration when importing MIBs is locating variables from other third-party MIBs. In
many cases, MIBs are named to match module names. However, in some circumstances it might
be necessary to rename MIB files to match the module names prior to compilation. For example,
some vendors might provide MIB files with different extensions such as .my. In this case, before
using mcompile, the mibfile.my file must be renamed to mibfile.mib.
mxmib
The mxmib tools registers MIBs into the HP SIM database by using their corresponding CFG files.
This tool has the capability to list all registered MIBs, to display a list of traps contained in each
individually registered MIB, and to unregister MIBs that you or the system have previously registered.
IMPORTANT: While it is possible to unregister MIBs currently registered in the HP SIM database,
HP strongly advises you do not unregister any files that have been registered by default. Doing so
can impair HP SIM's ability to correctly process traps from other HP systems on the network.
If you unregister a MIB from HP SIM, the corresponding received events in HP SIM are automatically
deleted.
mxmib expects to find all files located in the <BASE>\mibs directory. Usage for mxmib is as
follows:
mxmib -a <myfile.cfg>
mxmib -f <mylist.list>
mxmib -l
mxmib -t <myfile.mib>
mxmib -d <myfile.mib>
The switches work as follows:
• -a registers a new CFG, <myfile.cfg>, or replaces the data of a previously registered MIB.
• -f reads and processes a list of CFGs from a file, <mylist.list (one mibname per line)>, to
register with HP SIM. This file must reside in the <BASE>\mibs directory and the full CFG
filename must be listed on individual lines. Each line in the file is processed as it would be by
running the mxmib -a command individually on each individual MIB file.
• -l lists all the MIBs registered in HP SIM. Supplying no arguments to mxmib defaults to running
mxmib -l.
• -t lists the traps in the specified MIB <myfile.cfg>.
• -d unregisters a MIB, <myfile.cfg>, from the HP SIM database.
MIB management tools 165