HP Systems Insight Manager Online Help

HP Systems Insight Manager Online Help
HP Systems Insight Manager Online Help
Abstract
Help is intended to be used by technical professionals who manage multiple HP BladeSystem enclosures and use HP Virtual
Connect Manager to control network connectivity. HP assumes that you have installed Virtual Connect, are familiar with the
embedded VCM web console, and have read the HP Virtual Connect for c-Class BladeSystem User Guide and understand its
concepts
Legal notices
For copyright and legal information, see “Legal notices” (page 20).
HP Part Number: 356920-405
© Copyright 2003, 2013 Hewlett-Packard Development Company, L.P.
Contents
1 Legal notices............................................................................................20
Copyright notice.....................................................................................................................20
Warranty..............................................................................................................................20
Restricted rights legend............................................................................................................20
Acknowledgments...................................................................................................................20
2 Online help.............................................................................................21
HP SIM help categories...........................................................................................................21
3 Product overview......................................................................................22
Introduction............................................................................................................................22
HP SIM features......................................................................................................................22
Security............................................................................................................................23
Installation........................................................................................................................23
Discovery..........................................................................................................................23
Custom tools.....................................................................................................................23
Reporting..........................................................................................................................23
Product architecture.................................................................................................................24
Central management server.................................................................................................24
Managed systems..............................................................................................................24
Web-browser clients...........................................................................................................24
Security.................................................................................................................................24
Sign-in and accounts..........................................................................................................25
Single Sign On, Replicate Agent Settings, and Install Software and Firmware............................25
Certificates........................................................................................................................25
Credentials.......................................................................................................................26
Privilege elevation..............................................................................................................26
License Manager....................................................................................................................26
CLI mxlmkeyconfig.............................................................................................................27
HP SIM command line tools.....................................................................................................28
Command line interface......................................................................................................28
Custom tools..........................................................................................................................28
4 Initial setup..............................................................................................29
Setting language locale...........................................................................................................29
Setting the web browser language or locale..........................................................................30
Configuring the language or locale settings on Windows operating systems..............................30
Configuring HP-UX and Linux language settings.....................................................................31
Configuring HP SIM...........................................................................................................31
CMS locale..................................................................................................................32
Target locale................................................................................................................32
Signing in..............................................................................................................................33
Signing in to the GUI.........................................................................................................33
Manually signing in to HP SIM........................................................................................34
Automatically signing in.................................................................................................34
Signing in using SSL......................................................................................................36
Logging in to the CLI..........................................................................................................36
Logging in to the CMS directly........................................................................................37
Logging in to the CMS remotely using an SSH client..........................................................37
Single Sign On......................................................................................................................37
Signing in..............................................................................................................................38
Sign-in authentication on Linux and HP-UX.................................................................................38
Configuring PAM on a Linux system......................................................................................39
Contents
3
Configuring PAM on an HP-UX system...................................................................................39
Authenticating Windows AD Users from Linux CMS...........................................................39
Signing out............................................................................................................................40
Signing out from the GUI....................................................................................................40
Logging out from the CLI.....................................................................................................40
Product registration.................................................................................................................40
First Time Wizard...................................................................................................................41
Managed Environment.......................................................................................................42
Discovery - FTW................................................................................................................43
Configuring System Automatic Discovery task sign in credentials..............................................43
Configuring managed systems.............................................................................................43
Configuring the WMI Mapper Proxy....................................................................................44
Configuring privilege elevation on HP-UX..............................................................................45
Configuring e-mail settings..................................................................................................45
Additional e-mail settings...............................................................................................45
Summary..........................................................................................................................47
Finishing the First Time Wizard............................................................................................47
First Time Wizard related topics...........................................................................................47
Performing Initial setup............................................................................................................48
Initial setup process............................................................................................................48
Setting up managed systems....................................................................................................48
Setting up remote Linux systems from a Linux CMS..................................................................49
Setting up remote HP-UX systems from an HP-UX CMS.............................................................49
Example: Setting up remote HP-UX systems from an HP-UX CMS..........................................49
Setting up Windows managed systems manually...................................................................49
Setting up managed systems related topics............................................................................49
Related procedures........................................................................................................49
Related topics...............................................................................................................49
Setting up systems using the HP Insight managed system setup wizard...........................................50
Monitoring feature.............................................................................................................50
Configuration...............................................................................................................50
Inventory feature................................................................................................................50
Configuration...............................................................................................................50
WBEM........................................................................................................................51
Remote Command Execution feature.....................................................................................52
Configuration...............................................................................................................52
Single Sign On feature.......................................................................................................53
Events feature....................................................................................................................53
Configuration...............................................................................................................53
Version Control feature.......................................................................................................53
HP Insight managed system setup wizard - Protocol Preferences................................................53
SNMP.........................................................................................................................53
WBEM........................................................................................................................54
Editing preferences........................................................................................................55
HP Insight managed system setup wizard - SSH authentication.................................................56
HP Insight managed system setup wizard - SSH user name for public key..................................56
HP Insight managed system setup wizard - HP Integrated Lights-Out 2 Advanced........................56
Description...................................................................................................................56
Configuration information...............................................................................................56
Advanced setup.....................................................................................................................57
Configuring browser timeout options....................................................................................57
Changing the HP SIM default SSL port..................................................................................58
Managing server certificates...............................................................................................58
Replicating trusted certificates..............................................................................................59
Using the Replicate Agent Settings feature........................................................................60
4
Contents
Configuring the presentation of SNMP traps in HP SIM...........................................................61
5 Screens and product layout........................................................................62
Home page...........................................................................................................................64
Graphical user interface features..........................................................................................64
Navigating the System and Event Collections panel.....................................................................65
Tree controls and customization............................................................................................66
Overviews........................................................................................................................67
Systems............................................................................................................................67
Events..............................................................................................................................67
Users and user groups.............................................................................................................67
Users authorization templates..............................................................................................68
Users tab...............................................................................................................................69
Toolboxes tab........................................................................................................................70
Authorizations tab...................................................................................................................71
Navigating the system table view page.....................................................................................72
Tabs.................................................................................................................................73
Quick Launch....................................................................................................................73
View as............................................................................................................................73
Table information...............................................................................................................73
System view columns..........................................................................................................73
System table view page buttons...........................................................................................79
Customizing the view.........................................................................................................79
Navigating the cluster table view page......................................................................................79
Tabs.................................................................................................................................80
View as............................................................................................................................81
Quick Launch....................................................................................................................81
Cluster status summary.......................................................................................................81
Cluster collection columns...................................................................................................81
Buttons.............................................................................................................................83
Customizing......................................................................................................................83
Navigating the event table view page.......................................................................................83
Tabs.................................................................................................................................87
Quick Launch....................................................................................................................88
Event status summary..........................................................................................................88
Event collection columns.....................................................................................................88
Selection......................................................................................................................89
State...........................................................................................................................89
Severity........................................................................................................................89
Event Type....................................................................................................................89
System Name...............................................................................................................90
Event Time....................................................................................................................90
Assign To.....................................................................................................................90
Comments....................................................................................................................90
System Type..................................................................................................................90
Rack Name..................................................................................................................90
Enclosure Name...........................................................................................................90
Case Status..................................................................................................................90
Case ID.......................................................................................................................91
Table information...............................................................................................................91
Navigating the tree view.........................................................................................................91
Tabs.................................................................................................................................92
View as............................................................................................................................92
Quick Launch....................................................................................................................92
Expanding the tree view.....................................................................................................92
Contents
5
Tree view hierarchy............................................................................................................93
Selection in the tree view................................................................................................93
Available drilldowns......................................................................................................93
Selection states for collections.........................................................................................94
Tree view buttons...............................................................................................................94
Navigating the icon view.........................................................................................................95
Tabs.................................................................................................................................96
Quick Launch....................................................................................................................96
View as............................................................................................................................96
System health status summary..............................................................................................96
Icon view buttons...............................................................................................................96
Navigating the picture view page.............................................................................................97
Rack name........................................................................................................................98
Tabs.................................................................................................................................98
Quick Launch....................................................................................................................98
View as............................................................................................................................98
Selection in the icon view....................................................................................................98
Front and rear picture views................................................................................................99
Enclosure details..............................................................................................................102
Rack Details....................................................................................................................103
Picture view buttons..........................................................................................................103
Updated timestamp..........................................................................................................103
Viewing racks......................................................................................................................104
Viewing enclosures...............................................................................................................104
Viewing an enclosure.......................................................................................................107
Viewing p-Class enclosures....................................................................................................107
Viewing e-Class enclosures....................................................................................................108
Viewing c-Class enclosures.....................................................................................................108
Customizing system and cluster collections...............................................................................110
Displaying collection type.................................................................................................111
Expanding or collapsing collections...................................................................................111
Customize collections table................................................................................................111
Available buttons.............................................................................................................111
Customizing event collections.................................................................................................112
Displaying collection type.................................................................................................112
Expanding or collapsing collections...................................................................................112
Customize collections table................................................................................................113
Collection buttons............................................................................................................113
Command line interface....................................................................................................113
Managing event handling tasks..............................................................................................113
System Type Manager page...................................................................................................114
System type.....................................................................................................................114
Columns.........................................................................................................................114
Total...............................................................................................................................114
Available buttons.............................................................................................................115
WMI Mapper Proxy..............................................................................................................115
System page........................................................................................................................115
System tab for servers.......................................................................................................116
System Status..............................................................................................................116
More Information........................................................................................................117
Identification...............................................................................................................117
Firmware and Software Revision....................................................................................119
Product Description......................................................................................................119
HP Insight Control power management..........................................................................120
Contact Information.....................................................................................................120
6
Contents
Entitlement Information.................................................................................................121
Asset Information........................................................................................................121
Management Processor................................................................................................121
Host Server................................................................................................................121
Storage Server............................................................................................................121
Associations...............................................................................................................122
Role..........................................................................................................................122
Virtual Connect Domain...............................................................................................122
Location.....................................................................................................................123
System tab for blade servers..............................................................................................123
Role..........................................................................................................................123
Virtual Connect Domains..............................................................................................123
System tab for management processors...............................................................................125
System Status..............................................................................................................125
More Information........................................................................................................125
Identification...............................................................................................................126
Product Description......................................................................................................126
Associations...............................................................................................................127
Role..........................................................................................................................127
Managed Systems.......................................................................................................128
System tab for clusters.......................................................................................................128
Health Status..............................................................................................................128
Identification...............................................................................................................128
Product Description......................................................................................................128
System tab for a complex..................................................................................................129
Health Status..............................................................................................................129
More Information........................................................................................................129
Product Description......................................................................................................129
Summary of Components.............................................................................................130
System tab for partitions....................................................................................................131
Identification...............................................................................................................131
Product Description......................................................................................................131
Summary of Components.............................................................................................131
Associations...............................................................................................................132
System tab for storage host................................................................................................132
Product Description......................................................................................................132
Host Bus Adapters.......................................................................................................132
LUNs.........................................................................................................................134
System tab for a storage switch..........................................................................................135
Product Description......................................................................................................135
Ports..........................................................................................................................136
Status Summary..........................................................................................................136
System tab for a storage array...........................................................................................136
Product Description......................................................................................................137
Ports..........................................................................................................................137
Storage Volumes.........................................................................................................138
Capacity Information...................................................................................................139
System tab for a tape library.............................................................................................140
Product Description......................................................................................................140
Ports..........................................................................................................................141
Media Access Devices.................................................................................................142
Changer Devices.........................................................................................................142
Tools & Links tab..............................................................................................................142
Management Pages.....................................................................................................143
Web Application Pages...............................................................................................143
Contents
7
HP Systems Insight Manager Pages................................................................................143
Essentials tab...................................................................................................................144
Performance tab for blades...............................................................................................144
Port mapping tab for blades..............................................................................................145
Managing contacts..........................................................................................................145
Managing site information................................................................................................146
WBEM-based tools...............................................................................................................146
HP SIM Property pages.....................................................................................................146
System Fault Management overview...................................................................................147
WBEM Management Providers overview.............................................................................147
Process Resource Manager (HP PRM).................................................................................148
Reasons to use PRM.....................................................................................................149
Accessing Process Resource Manager from HP SIM.........................................................149
Managing SSH keys.........................................................................................................149
Related information.....................................................................................................150
Cluster monitor.....................................................................................................................150
Cluster tab......................................................................................................................150
Nodes tab......................................................................................................................151
Network tab....................................................................................................................151
Resources tab..................................................................................................................152
Managing Communications...................................................................................................153
Communication status.......................................................................................................153
Manage Communications table columns.............................................................................153
Manage Communications main page buttons......................................................................155
Manage Communications tabs..........................................................................................156
Related information..........................................................................................................157
Related procedures......................................................................................................157
Related topics.............................................................................................................157
Managing with tasks.............................................................................................................157
Viewing task instance results..............................................................................................157
Viewing task instance results.........................................................................................157
Viewing target details .................................................................................................158
Navigating the All Scheduled Tasks page...........................................................................159
User privileges............................................................................................................159
Run now....................................................................................................................159
Edit...........................................................................................................................159
Delete........................................................................................................................160
Enabling and disabling tasks........................................................................................160
Viewing task results.....................................................................................................160
License Manager..................................................................................................................160
Licensed System(s)............................................................................................................161
Add Licenses...................................................................................................................161
Manage Licenses.............................................................................................................162
Collect Remote License Info................................................................................................164
Assign License(s)..............................................................................................................164
Un-Assign Licenses...........................................................................................................165
Apply Licenses.................................................................................................................165
Product License Information table...................................................................................165
License Collection Results table......................................................................................166
Add License page.......................................................................................................168
Key details page.........................................................................................................168
License not added.......................................................................................................169
Keys from file:.............................................................................................................169
CLI mxlmkeyconfig.......................................................................................................169
Assigning or Applying Licenses page.............................................................................170
8
Contents
License unlicensed systems (optional) page.....................................................................171
License types..............................................................................................................172
Related information.....................................................................................................173
Reporting........................................................................................................................173
New Report................................................................................................................173
Manage Reports.........................................................................................................173
Snapshot comparison..................................................................................................175
Enhanced Reports.......................................................................................................175
Federated CMS Search tool..........................................................................................176
Reports by Product page..............................................................................................177
Reports by Product page buttons...................................................................................178
Select data to be displayed in the report:.......................................................................179
Related information.....................................................................................................180
Remote Support Configuration and Services........................................................................180
Remote Support Configuration and Services overview......................................................180
Configuring Remote Support Configuration and Services settings.......................................181
Using the Entitlement tab..............................................................................................181
Accessing Remote Support Configuration Services On-Line Help........................................183
6 Operations............................................................................................184
Customizing the Home page..................................................................................................184
Customizing the system status panel........................................................................................184
Enlarging the System Status panel...........................................................................................185
Utilizing RSS capabilities..................................................................................................186
Setting up managed systems from a Linux CMS........................................................................186
Installing the ProLiant Support Pack on a Linux system for the first time.....................................187
Configuring the managed system software..........................................................................187
Setting up Linux managed systems manually........................................................................187
Setting up managed systems from a Windows CMS..................................................................187
Configuring the managed system software using the Configure or Repair Agents feature from the
CMS..............................................................................................................................187
Setting up managed systems from an HP-UX CMS.....................................................................188
Discovery in HP SIM.............................................................................................................189
Automatic discovery.........................................................................................................189
Internet Protocol..........................................................................................................189
Event-based automatic discovery...................................................................................189
First discovery..................................................................................................................190
Subsequent discoveries.....................................................................................................190
Hosts files.......................................................................................................................190
Options for adding a single system................................................................................191
Configuring automatic discovery........................................................................................191
For all automatic discoveries section..............................................................................192
Actions to take after running discovery section................................................................192
Discovery page buttons................................................................................................192
Configuring automatic discovery settings of VM guests..........................................................193
Configuring discovery general settings................................................................................193
Creating a new discovery task...........................................................................................195
Creating an automatic discovery task using the command line interface.............................197
Configuring credentials for discovery tasks..........................................................................197
Creating and editing discovery credentials for a single system..........................................197
Creating and editing discovery credentials for a group....................................................199
Related topics.............................................................................................................200
Configuring Configure or Repair Agents for discovery tasks..............................................200
Configuring system types for discovery tasks...................................................................201
Editing a discovery task...............................................................................................202
Contents
9
Disabling or enabling an existing discovery task.............................................................203
Deleting a discovery task.............................................................................................203
Running a discovery task..............................................................................................203
Discovery related information........................................................................................204
Discovery filters...............................................................................................................204
Managing Hosts files........................................................................................................205
Creating a new hosts file..............................................................................................205
Editing a hosts file.......................................................................................................206
Deleting a hosts file.....................................................................................................207
Adding systems in a hosts file to the HP SIM database.....................................................207
Identification overview.................................................................................................207
Managing system types................................................................................................208
Creating STM rules......................................................................................................209
Editing STM rules........................................................................................................211
Deleting STM rules......................................................................................................211
Related information.....................................................................................................211
Users and authorizations.......................................................................................................212
User authorization templates..............................................................................................213
Creating new authorizations..............................................................................................213
Command line interface...............................................................................................216
Creating new toolboxes....................................................................................................216
Command line interface...............................................................................................217
Creating new users..........................................................................................................217
Command line interface...............................................................................................218
Updating authorizations....................................................................................................218
Command line interface...............................................................................................219
Editing toolboxes.............................................................................................................219
Command line interface...............................................................................................219
Creating new user groups.................................................................................................220
Command line interface...............................................................................................221
Deleting authorizations.....................................................................................................221
Command line interface...............................................................................................221
Deleting toolboxes...........................................................................................................221
Command line interface...............................................................................................222
Editing users and user groups............................................................................................222
Command line interface...............................................................................................223
Authorization reports........................................................................................................224
Command line interface...............................................................................................224
Toolbox reports................................................................................................................224
Command line interface...............................................................................................225
Deleting users and user groups..........................................................................................225
Command line interface...............................................................................................225
System groups (CLI)..........................................................................................................226
Managing system groups from the GUI..........................................................................226
Managing system groups from the CLI using mxngroup....................................................226
User and user group reports..............................................................................................227
Command line interface...............................................................................................227
Users and authorizations related information.......................................................................227
Directory Services.................................................................................................................228
Configuring directory servers.............................................................................................228
Configuring directory groups.............................................................................................229
Related information..........................................................................................................229
Related procedures......................................................................................................229
Related topic..............................................................................................................229
Global credentials................................................................................................................229
10
Contents
Related topics..................................................................................................................230
System credentials................................................................................................................230
Columns in the "Credentials that are in use" table................................................................231
Viewing, editing, and deleting system credentials.................................................................231
Sign-in credentials............................................................................................................233
Single sign on credentials.................................................................................................234
SNMP credentials............................................................................................................234
SNMPv3 credentials.........................................................................................................235
SSH credentials...............................................................................................................236
WBEM credentials...........................................................................................................237
WS-Man credentials.........................................................................................................238
VME credentials..............................................................................................................238
Related information..........................................................................................................239
Security...............................................................................................................................240
Creating a server certificate..............................................................................................240
Editing a server certificate.................................................................................................242
Importing a server certificate.............................................................................................243
Exporting a server certificate.............................................................................................243
Creating a certificate signing request..................................................................................244
Submitting a certificate signing request...............................................................................244
Importing a CA-signed certificate.......................................................................................244
Synchronizing certificates..................................................................................................245
Configuring the system link................................................................................................245
Configuring sign-in events.................................................................................................246
Privilege elevation............................................................................................................246
Changing the authentication mechanism.............................................................................247
Configuring Two Factor Authentication................................................................................247
Certificate Revocation Check Configuration.........................................................................247
Security related information...............................................................................................248
Trusted certificates................................................................................................................248
Importing trusted certificates..............................................................................................249
Exporting trusted certificates..............................................................................................249
Deleting trusted certificates................................................................................................250
Requiring trusted certificates..............................................................................................251
Configuring SSH key security.............................................................................................251
Importing an SSH key.......................................................................................................252
Exporting an SSH key.......................................................................................................252
Deleting an SSH key........................................................................................................253
Related information..........................................................................................................253
Viewing the audit log............................................................................................................253
Log content.....................................................................................................................253
Configuring the audit log.......................................................................................................254
Configuring the audit log..................................................................................................254
Monitoring systems and events...............................................................................................255
Creating system and cluster collections................................................................................255
Command line interface...............................................................................................257
Editing system and cluster collections..................................................................................257
Command line interface...............................................................................................259
Moving system and cluster collections.................................................................................259
Command line interface...............................................................................................259
Copying system and cluster collections................................................................................260
Command line interface...............................................................................................260
Deleting system and cluster collections................................................................................260
Command line interface...............................................................................................261
Setting properties for system and cluster collections...............................................................261
Contents
11
Command line interface...............................................................................................261
Creating event collections.................................................................................................262
Command line interface...............................................................................................264
Editing event collections....................................................................................................264
Command line interface...............................................................................................266
Moving event collections...................................................................................................266
Command line interface...............................................................................................266
Copying event collections..................................................................................................266
Command line interface...............................................................................................267
Deleting event collections..................................................................................................267
Command line interface...............................................................................................267
Setting event properties....................................................................................................267
Command line interface...............................................................................................268
System table view page....................................................................................................268
Customizing the system table view page.............................................................................268
Deleting systems from the HP SIM database.........................................................................269
Printing a system collection view........................................................................................269
Cluster table view page....................................................................................................270
Tabs..........................................................................................................................270
Customizing the cluster table view page..............................................................................271
Deleting clusters from the HP SIM database.........................................................................271
Printing a cluster collection view.........................................................................................271
Event table view page......................................................................................................272
Customizing the event table view page...............................................................................272
Clearing events from the collection.....................................................................................273
Deleting events from the HP SIM database..........................................................................273
Assigning events to users..................................................................................................273
Printing an event collection view........................................................................................274
Entering comments to events..............................................................................................274
Saving collections............................................................................................................274
Related information..........................................................................................................275
Quick Launch menu..............................................................................................................276
Performing a basic search......................................................................................................276
Performing an advanced search for systems..............................................................................277
Deleting system search results from a search view.................................................................278
Printing system search results.............................................................................................278
Performing an advanced search for clusters..............................................................................278
Deleting cluster search results from a search view.................................................................279
Printing cluster search results..............................................................................................280
Performing an advanced search for events...............................................................................280
Deleting event search results from a search view...................................................................281
Printing event search results...............................................................................................281
Tool search..........................................................................................................................282
Searching for tools...........................................................................................................282
Related information for searches.............................................................................................282
Configuring events................................................................................................................283
Editing automatic event handling tasks....................................................................................283
Copying automatic event handling tasks..................................................................................283
Viewing task definitions for automatic event handling tasks........................................................284
Viewing event task results.......................................................................................................284
Enabling and disabling event handling tasks............................................................................285
Configuring e-mail settings.....................................................................................................285
Additional e-mail settings..................................................................................................285
EmailPrefixUserSubject.................................................................................................285
EmailKeywords...........................................................................................................286
12
Contents
Configuring modem settings for paging on Windows systems.....................................................287
Clearing events....................................................................................................................287
Deleting events.....................................................................................................................287
Configuring event filters for registered SNMP traps....................................................................287
Configuring SNMP traps........................................................................................................288
SNMP trap fields.............................................................................................................288
Modifying traps...............................................................................................................288
Configuring status change events............................................................................................289
Subscribing to WBEM indications...........................................................................................289
Unsubscribing to WBEM indications........................................................................................289
Subscribing to health lifecycle events.......................................................................................290
Creating an automatic event handling task...............................................................................290
Related information...............................................................................................................294
Protocol settings...................................................................................................................294
Setting protocols and credentials for a system or group of systems..........................................296
Setting protocols for a single system...................................................................................296
Adding a WMI Mapper Proxy...........................................................................................297
Deleting a WMI Mapper Proxy..........................................................................................297
Editing a WMI Mapper Proxy............................................................................................298
Viewing and editing ESXi subcomponents...........................................................................298
Software status polling..........................................................................................................298
Hardware status polling.........................................................................................................299
Data collection.....................................................................................................................300
Command line interface....................................................................................................300
Adobe Flash Detection..........................................................................................................300
System Properties..................................................................................................................300
Editing system properties for a single system........................................................................301
Entering new contact information.......................................................................................304
Editing contact information................................................................................................305
Deleting contact information..............................................................................................305
Entering new site information.............................................................................................305
Editing site information.....................................................................................................306
Deleting site information...................................................................................................307
Editing system properties for multiple systems.......................................................................307
Suspending or resuming system monitoring for a single system...............................................309
Suspending or resuming system monitoring for multiple systems..............................................309
Related information..........................................................................................................310
Configuring WBEM health inclusion status...............................................................................310
Specifying a Version Control Repository...................................................................................311
Configuring software/firmware global settings..........................................................................312
Reporting............................................................................................................................312
New reports....................................................................................................................314
Selecting the sort order................................................................................................315
Printing the report.......................................................................................................315
Running managed reports.................................................................................................315
Running an existing report in HTML format.....................................................................315
Viewing an existing report in XML format.......................................................................315
Viewing an existing report in CSV format.......................................................................315
Selecting the sort order................................................................................................316
Printing an existing report.............................................................................................316
Copying managed reports................................................................................................316
Editing managed reports...................................................................................................316
Deleting managed reports.................................................................................................317
Running predefined reports...............................................................................................317
Adding a report..............................................................................................................320
Contents
13
Creating a report........................................................................................................320
Printing the report.......................................................................................................327
Editing a report...............................................................................................................327
Deleting a report.............................................................................................................328
Running a report..............................................................................................................328
Running an existing report in HTML format.....................................................................328
Viewing an existing report in PDF format........................................................................328
Viewing an existing report in CSV format.......................................................................328
Printing an existing report.............................................................................................329
Emailing reports..............................................................................................................329
Periodically................................................................................................................330
Once.........................................................................................................................330
Insight Control reports......................................................................................................331
Showing SQL..................................................................................................................332
Snapshot comparison reporting.........................................................................................332
Federated CMS Search Tool..............................................................................................333
Search Tab.................................................................................................................333
Federated Search Advanced Search Tab........................................................................334
Connections Tab.........................................................................................................336
Federated CMS Search Configuration.................................................................................337
Managing with tasks.............................................................................................................338
Creating a task................................................................................................................338
Scheduling a task............................................................................................................341
Viewing all scheduled tasks..........................................................................................342
Applying a time filter........................................................................................................342
Running a scheduled task..................................................................................................343
Editing a scheduled task...................................................................................................343
Deleting a scheduled task.................................................................................................343
Printing reports................................................................................................................344
Stopping a task...............................................................................................................344
Configuring task results settings..........................................................................................344
Deleting task results..........................................................................................................345
Task results list.................................................................................................................345
Managing with tasks related information.............................................................................346
Using Cluster Monitor...........................................................................................................347
Configuring cluster resource settings...................................................................................347
Configuring node resource settings.....................................................................................348
Command line tools..............................................................................................................348
Configuring managed systems from a Windows CMS...............................................................349
Configuring or repairing the agents....................................................................................350
Related Topics.................................................................................................................352
Configuring target system settings......................................................................................353
Configuring credentials.....................................................................................................357
Configuring managed systems from a Linux CMS......................................................................358
Configuring or repairing the agents....................................................................................359
Related Topics.................................................................................................................359
Configuring target system settings......................................................................................360
Configuring credentials.....................................................................................................363
Configuring managed systems from an HP-UX CMS...................................................................365
Overview........................................................................................................................365
Configuring or repairing the agents....................................................................................366
Related Topics.................................................................................................................366
Configuring target system settings......................................................................................367
Configuring credentials.....................................................................................................370
Custom tools........................................................................................................................372
14
Contents
Menu placement..............................................................................................................374
Managing custom tools....................................................................................................374
New..........................................................................................................................374
Edit...........................................................................................................................374
View tool definition.....................................................................................................374
Run Now/Schedule.....................................................................................................374
Delete........................................................................................................................374
Creating a remote tool......................................................................................................375
Editing a remote tool........................................................................................................376
Creating a CMS tool........................................................................................................377
Editing a CMS tool..........................................................................................................378
Creating a web page tool.................................................................................................379
Editing a web page tool...................................................................................................380
Viewing a tool definition...................................................................................................380
Deleting a custom tool......................................................................................................380
Removing and restoring custom tools..................................................................................381
Restoring a tool...............................................................................................................381
Related information...............................................................................................................381
Setting disk thresholds...........................................................................................................381
Creating a task to delete disk thresholds..................................................................................382
License manager..................................................................................................................383
Viewing licensed systems..................................................................................................384
Managing licenses...........................................................................................................384
Adding licenses individually..............................................................................................385
Adding licenses from a file................................................................................................385
Creating a license file..................................................................................................386
Assigning a license or Apply a license................................................................................387
Un-assigning a license......................................................................................................387
mxlmkeyconfig CLI...........................................................................................................388
Management processor tools.................................................................................................388
Controlling system power options through management processors.........................................389
Controlling the system locator LED through management processors........................................389
Creating new users on management processors...................................................................390
Editing management processor users..................................................................................390
Deleting management processor users................................................................................391
Configuring LAN access on management processors............................................................391
Configuring LDAP settings on management processors..........................................................392
Executing internal control actions through management processors.........................................392
Upgrading management processor firmware.......................................................................393
Deploying SSH public keys to management processors.........................................................393
Cycling on the power on an HP ProLiant management processor............................................393
Powering on a system managed by an HP ProLiant management processor..............................394
Powering off a system managed by an HP ProLiant management processor..............................394
Turning on the UID for a system managed by an HP ProLiant management processor................394
Turning off the UID for a system managed by an HP ProLiant management processor................394
Related information..........................................................................................................394
Managing Communications...................................................................................................395
Manage communications quick repair................................................................................396
Identification tab..............................................................................................................396
Events tab.......................................................................................................................396
Run Tools tab...................................................................................................................397
Version Control tab..........................................................................................................397
Repairing managed system settings....................................................................................397
Updating communication statuses......................................................................................403
Printing Manage Communications table..............................................................................403
Contents
15
Managing MIBs...................................................................................................................404
Viewing a MIB................................................................................................................404
Viewing a MIB file on a Windows operating system:........................................................404
Viewing a MIB file on a Linux or HP-UX operating system:.................................................404
Editing a MIB..................................................................................................................405
Compiling a MIB.............................................................................................................405
Registering a MIB............................................................................................................406
Registering a MIB in HP SIM.........................................................................................407
Updating a MIB..........................................................................................................407
Service trap and service MIB information........................................................................407
Unregistering a MIB.........................................................................................................407
Related information..........................................................................................................407
Installing OpenSSH...............................................................................................................408
Creating an OpenSSH task through the CLI.........................................................................408
Creating an OpenSSH task..........................................................................................408
Creating an OpenSSH task from the command line with an XML file..................................410
Creating an OpenSSH task from the command line without an XML file..............................410
Replicate Agent Settings........................................................................................................410
Creating a Replicate Agent Settings task.............................................................................411
RPM Package Manager.........................................................................................................411
Installing RPM..................................................................................................................412
Uninstalling RPM..............................................................................................................412
Querying RPM.................................................................................................................412
Verifying RPM..................................................................................................................412
HP Server Migration Pack - Universal Edition............................................................................412
Adding an server migration license....................................................................................413
Adding an SMP Universal license.......................................................................................413
Accessing the HP Server Migration Pack.............................................................................413
HP System Management Homepage.......................................................................................413
Accessing HP System Management Homepage....................................................................414
Version Control.....................................................................................................................414
Accessing the Version Control Agent..................................................................................414
Logging in to the HP VCA............................................................................................415
Accessing the Version Control Repository Manager..............................................................415
Accessing HP VCRM from HP SIM.................................................................................415
Accessing HP VCRM In-Place........................................................................................415
Managing Software/Firmware Baselines.............................................................................415
Executing Software and Firmware task................................................................................416
Adding systems to baseline from the Managing Software/Firmware Baselines page.................417
Tracking Software/Firmware Baselines................................................................................417
Adding systems to the baseline from the Tracking Software/Firmware Baslines page.................417
Installing Software and Firmware through baselines...................................................................417
Installing Software and Firmware task......................................................................................418
Installing software and firmware:........................................................................................418
Firmware deployment to switches.......................................................................................420
Installing ROM firmware updates............................................................................................420
Version Control status icons....................................................................................................421
Version Control status.......................................................................................................421
Device ping.........................................................................................................................422
7 Reference..............................................................................................423
Recommended discovery tasks...............................................................................................424
Search criteria......................................................................................................................425
Software and firmware criteria...........................................................................................427
Cleared state criterion......................................................................................................428
16
Contents
Server role criteria............................................................................................................428
Assignee criteria..............................................................................................................429
Event type criteria............................................................................................................429
Memory range criteria......................................................................................................430
Entering IP ranges in discovery tasks.......................................................................................430
Operating-system-specific collections, reports, and tools.............................................................431
Operating-system-specific reports.......................................................................................432
Operating-system-specific tools...........................................................................................432
Windows...................................................................................................................432
Linux.........................................................................................................................432
HP-UX........................................................................................................................432
Other........................................................................................................................433
System status types................................................................................................................433
Setting up trust relationships...................................................................................................434
Configuration of the managed system.................................................................................434
Importing the HP SIM certificate over the network.................................................................435
Importing the HP SIM certificate from a file..........................................................................436
Setting up the managed server running Management HTTP Server.........................................436
Importing the HP SIM certificate....................................................................................436
Requesting the HP SIM certificate..................................................................................436
Onboard Administrator configuration.............................................................................436
HP StorageWorks Command View EVA configuration......................................................437
HP SIM configuration...................................................................................................437
Suppressing browser warning messages.............................................................................437
Configure or Repair Agents Learn More links............................................................................438
Setting the administrator password for Insight Management Agents........................................438
Installing the WBEM/WMI provider for Windows................................................................438
Configuring WBEM/WMI.................................................................................................439
Monitoring systems, clusters, and events..............................................................................439
About collections.........................................................................................................439
Types of collections......................................................................................................440
Locked collections.......................................................................................................440
Installing the SNMP provider for Windows..........................................................................440
Configuring SNMP...........................................................................................................441
Installing OpenSSH from CRA...........................................................................................442
Installing Linux PSP or ESX Agents from CRA........................................................................442
Installing the Version Control Agent....................................................................................442
HP VCA.....................................................................................................................442
HP Version Control Repository Manager.........................................................................443
Configuring VCA.............................................................................................................443
Configuring a non-administrative account for HP SIM to access WMI data..............................443
Configuring SSH..............................................................................................................443
Manage communications Learn More links...............................................................................444
HP SIM and firewalls........................................................................................................444
Ports used by HP SIM that might need to be configured in a firewall...................................444
Configuring HP SIM SNMP Ports...................................................................................445
Configuring the firewall................................................................................................445
Installing and configuring protocols....................................................................................447
Trusted certificates............................................................................................................449
Importing trusted certificates.........................................................................................449
Setting trust relationships...................................................................................................449
Configuration of the managed system............................................................................449
Importing the HP SIM certificate over the network............................................................450
Importing the HP SIM certificate from a file.....................................................................451
Configuring WMI Mapper Proxy........................................................................................451
Contents
17
Installing and configuring SNMP agent...............................................................................452
Installing the SNMP agent............................................................................................452
Configuring SNMP to send test traps..............................................................................453
Web-Based Enterprise Management..............................................................................454
Subscribing to WBEM indications.................................................................................454
WBEM and HP SIM.........................................................................................................456
Subscribing to WBEM indications.................................................................................457
WBEM indications...........................................................................................................458
Subscribing to WBEM indications.................................................................................458
Secure Shell and HP SIM..................................................................................................459
WMI Mapper and HP SIM................................................................................................460
Adding a WMI Mapper Proxy......................................................................................460
Pinging managed systems.................................................................................................460
Installing the HP ProLiant Support Pack................................................................................460
System Type Manager rules...............................................................................................460
Installing and configuring Version Control...........................................................................462
HP Version Control Repository Manager.........................................................................463
Version control repository.............................................................................................463
Credentials used in HP SIM....................................................................................................464
Credentials related information...............................................................................................465
Port types............................................................................................................................465
Replicate Agent Settings........................................................................................................466
Determining a trust relationship..........................................................................................466
Changing a trust relationship.............................................................................................466
Wake on LAN feature......................................................................................................466
Replicate Agent Settings events..........................................................................................466
Cluster Monitor resources and associated settings.....................................................................466
Configure or repair agents results log......................................................................................467
Available MSA tools.............................................................................................................469
Custom tools reference..........................................................................................................469
Tool types.......................................................................................................................469
Parameterized strings........................................................................................................470
Parameterized strings substitution table...........................................................................470
Tool filtering....................................................................................................................471
Version numbers..............................................................................................................474
Other requirements..........................................................................................................474
Document type definition..................................................................................................474
Custom tool environment variables.....................................................................................485
Examples of using parameter strings in custom tools.............................................................487
8 Support and other resources....................................................................489
Information to collect before contacting HP...............................................................................489
How to contact HP................................................................................................................489
Registering for software technical support and update service.....................................................489
How to use your software technical support and update service.............................................489
Warranty information.......................................................................................................490
HP authorized resellers..........................................................................................................490
Typographic conventions.......................................................................................................490
Documentation feedback.......................................................................................................491
9 Assistance.............................................................................................492
Glossary..................................................................................................493
Index.......................................................................................................505
1 Search..................................................................................................521
18
Contents
..........................................................................................................................................522
Contents
19
1 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. The only warranties for HP
products and services are set forth in the express warranty statements accompanying such products
and services. Nothing herein should be construed as constituting an additional warranty. HP shall
not be liable for technical or editorial errors or omissions contained herein.
Copyright notice
© Copyright 2003, 2013 Hewlett-Packard Development Company, L.P.
Warranty
A copy of the specific warranty terms applicable to your HP product and replacement parts can
be obtained from your local Sales and Service Office.
Restricted rights legend
Use, duplication, or disclosure by the U.S. Government is subject to restrictions as set forth in
subparagraph (c) (1) (ii) of the Rights in Technical Data and Computer Software clause at DFARS
252.227-7013 for DOD agencies, and subparagraphs (c) (1) and (c) (2) of the Commercial
Computer Software Restricted Rights clause at FAR 52.227-19 for other agencies.
HEWLETT-PACKARD COMPANY
3000 Hanover Street
Palo Alto, California 94304 U.S.A.
Use of this documentation and any supporting software media supplied for this pack is restricted
to this product only. Additional copies of the programs may be made for security and backup
purposes only. Resale of the programs, in their present form or with alterations, is expressly
prohibited.
Acknowledgments
HP-UX Release 10.20 and later and HP-UX Release 11.00 and later (in both 32- and 64-bit
configurations) on all HP 9000 computers are Open Group UNIX 95-branded products.
Intel, Celeron, Itanium, Pentium, and Xeon are trademarks or registered trademarks of Intel
Corporation or its subsidiaries in the United States and other countries.
Java is a U.S. trademark of Sun Microsystems, Inc.
Microsoft, Windows, and Windows NT are U.S. registered trademarks of Microsoft Corporation.
Oracle is a registered U.S. trademark of Oracle Corporation, Redwood City, California.
UNIX is a registered trademark of The Open Group.
20
Legal notices
2 Online help
HP SIM provides an online help system that helps you understand management features. To view
the online help, click the question mark icon on any page or use the Help menu to view the online
help.
HP SIM help categories
•
Overview
Describes the features in HP SIM.
•
Initial setup
Describes procedures for how to begin using and administering HP SIM.
•
Screens and product layout
Describes how to navigate HP SIM menu pages.
•
Operations
Describes procedures for monitoring and managing HP SIM, including security, users and
authorizations, and discovery.
•
Reference
Includes information on how to set up security trust relationships,system types, custom tools,
and Microsoft® Windows NT® error log messages.
•
Support and other resources
Includes document and support information and links to the HP SIM forum and documentation.
•
Assistance
Includes additional resources, technical support, and technical FAQs.
HP SIM help categories
21
3 Product overview
The Overview section includes a brief introduction to some of the major features of HP Systems
Insight Manager. High-level information on command-line tools, custom tools, discovery, and license
manager are some of the features discussed.
Introduction
HP SIM is the foundation for the HP unified server-storage management strategy. HP SIM is a
hardware-level management product that supports multiple operating systems on HP ProLiant,
Integrity and HP 9000 servers, HP StorageWorks MSA, EVA, XP arrays, and third-party arrays.
Through a single management view of Microsoft® Windows®, HP-UX 11iv1, HP-UX 11iv2, HP-UX
11iv3, and Red Hat, and SuSE Linux, HP SIM provides the basic management features of:
•
System discovery and identification
•
Single-event view
•
Inventory data collection
•
Reporting
The core HP SIM software uses WBEM to deliver the essential capabilities required to manage all
HP server platforms.
HP SIM can provide systems management with plug-ins for HP clients, storage, power, and printer
products. Using HP Integrity Essentials you can choose plug-in applications that deliver complete
lifecycle management for your hardware assets:
•
Workload management
•
Capacity management
•
Virtual machine management
•
Partition management
HP SIM features
•
Fault management and event handling
HP SIM provides proactive notification of actual or impending component failure alerts.
Automatic Event Handling enables you to configure actions to notify appropriate users of
failures through e-mail, and enables automatic execution of scripts or event forwarding to
enterprise platforms such as HP OpenView Network Node Manager or HP OpenVMS Systems.
•
Consistent multisystem management
HP SIM initiates a task on multiple systems or nodes from a single command on the CMS. This
functionality eliminates the need for tedious, one-at-a-time operations performed on each
system.
•
Two user interfaces
HP SIM provides the option of a browser-based GUI or a CLI that enables you to incorporate
HP SIM into your existing management processes.
•
WBEM indications for HP-UX, Linux, and SMI-S devices
HP SIM enables you to use the GUI or CLI to subscribe and unsubscribe to WBEM indications.
22
Product overview
Security
•
Role-based security
HP SIM enables effective delegation of management responsibilities by giving system
administrators granular control over which users can perform specific management operations
on specific systems.
•
Configure or Repair Agents
This feature enables you to repair credentials for SNMP settings, HP System Management
Homepage, or Management HTTP Server trust relationships on Windows, Linux, and HP-UX
systems supported by HP SIM. See “Configuring managed systems from a Windows CMS”
(page 349) for more information.
Installation
•
Easy and rapid installation.
You can install HP SIM quickly and easily, on HP-UX 11i v1, HP-UX 11i v2, or HP-UX 11i v3
on PA-RISC/Integrity server platforms, or on ProLiant platforms running Windows or Linux.
•
First Time Wizard
HP SIM provides you with step-by-step, online instructions for performing the initial configuration
of HP SIM. The wizard helps you configure basic HP SIM settings on the CMS.
Discovery
HP SIM can automatically discover and identify systems attached to the network. Discovery filters
enable you to limit discovery to specific network segments or IP address ranges. Use discovery
filters to prevent discovery of unwanted system types.
Custom tools
HP SIM defines tools using simple XML documents that enable you to integrate off-the-shelf or custom
tools. These tools can be command line tools, web-based applications, or scripts. Role-based
security governs access to these integrated tools.
Reporting
•
Data collection and inventory reports
HP SIM performs comprehensive system data collection and enables you to quickly produce
detailed inventory reports for managed systems. Reports can be generated in HTML, XML, or
CSV format. Data collection and reporting has been added for HP Superdome systems and
other cellular complexes. You can collect information about:
◦
Enclosures
◦
Cabinets
◦
Cell Blade
◦
Memory
◦
Fan and Power
◦
Integrity virtual machines
◦
Non-Integrity virtual machines
HP SIM features
23
•
◦
Virtual partitions (vPars)
◦
Hard partitions (nPars)
Snapshot comparisons
HP SIM enables you to compare configuration snapshots of up to four different servers, or
compare configuration snapshots of a single server over a period of time. You can use snapshot
comparisons to save a picture of a standard configuration for comparisons to other systems.
•
Federated CMS Search
Federated CMS Search is a web-based HP SIM plug-in that allows you to search quickly across
a number of Systems Insight Manager CMS systems.
Product architecture
HP SIM leverages a distributed architecture that has three types of systems: CMS, managed systems,
and web-browser clients.
The CMS with the managed systems together are called the HP SIM management domain.
Central management server
Each management domain has a single CMS. The CMS is the system in the management domain
that executes the HP SIM software and initiates all central operations within the domain. In addition
to the HP SIM software, the CMS maintains a database for storage of persistent objects that can
reside locally or on a separate system. Typically, applications for the MSA tools also reside on the
CMS. However, these applications are not required to reside on the CMS. They can reside anywhere
on the network.
Because the CMS is a system within the management environment, it manages itself as part of the
domain. You can add the CMS as a managed system within another management domain if you
want to manage the domain using a separate CMS.
Managed systems
Systems that comprise a management domain are called managed systems. A system can be any
device on the network that can communicate with HP SIM, including servers, desktops, laptops,
printers, workstations, hubs, storage systems, SANs, and routers. In most cases, these devices have
an IP address associated with them. A managed system can be managed by more than one CMS,
if desired.
Managed systems to be managed must have one or more Insight Management Advisor installed.
There is a wide variety of agents, such as the HP Insight Management Agents based on SNMP,
or the WMI for Windows systems, or WBEM providers, and System Fault Management providers
for HP-UX. These agents provide management information and alerts (indications) to the CMS. The
SSH agent (service) then enables the HP SIM CMS to log in to the managed system to execute
commands through scripts.
Web-browser clients
You can access HP SIM from any supported browser client. The network client can be part of the
management domain. However, you must run a compatible browser to access the GUI or an SSH
client application to securely access the CLI. You can restrict access to the web server on the CMS
to specific IP address ranges for specific users.
Security
SSL is used between the browser and HP SIM to ensure data integrity and privacy. An integral
part of SSL is a certificate, which is a public document used to identify the HP SIM server. When
24
Product overview
HP SIM is installed, it creates a self-signed certificate. Your browser might initially display a security
alert when you browse to HP SIM, describing the certificate as untrusted. This designation occurs
because the certificate is self-signed (signed by the HP SIM server) and the signer is not in the
browser list of CAs. By securely importing the HP SIM server certificate into the browser, the browser
can authenticate the HP SIM server to which you are browsing.
HP SIM also supports the ability to use a certificate from a third-party CA or your own internal CA
or PKI. In this case, you can import the CA certificate into your browser. For more information, see
Importing a CA-signed certificate.
Sign-in and accounts
A user name, domain name (for Windows CMS), and password are required before you can
access any feature of HP SIM. HP SIM uses the user authorizations of the underlying operating
system (Windows, Linux, or HP-UX) and relies on the operating system to authenticate users.
The user that is installing HP SIM must be either a system administrator (for Windows) or root user
(for Linux and HP-UX). This user has administrative access to HP SIM.
After signing in with this account, create additional accounts for other users. Each account can
have different configuration rights and authorizations. You can restrict the IP addresses from which
each account can sign-in. For more information, see Users and authorizations.
Audit settings can be configured to log a notice for different types of security events, including
sign-in and sign-out events. For more information, see Configuring sign-in events.
Single Sign On, Replicate Agent Settings, and Install Software and Firmware
To take advantage of Single Sign On or to execute Replicate Agent Settings or Install Software
and Firmware tasks on the managed systems, set up a trust relationship between HP SIM and the
desired managed systems. A trust relationship enables the managed system to specify which HP
SIM servers can issue commands to the system. Without an established trust relationship, these
commands fail.
Setting up a trust relationship on the managed system requires that you browse to the system, set
the trust mode, and add HP SIM to the Trusted System Certificates list. Managed systems can also
be set up with an appropriate certificate during deployment. At the HP SIM server, you must also
specify the user authorization for the managed system and have executed a System Identification
task. If you have enabled the Require option on the Trusted System Certificates page, you must
import the certificates of trusted managed systems into HP SIM, or a root CA certificate.
Certificates
HP SIM allows secure and authorized management from the CMS. User authorizations for managed
systems and the CMS can be configured, helping ensure that only authorized users perform
state-changing operations. Communication between the CMS, managed systems, and the browser
is secured using SSL and certificates, helping to authenticate systems and protect user credentials
and management data.
A new SSL certificate is created during CMS initialization that is used as a client credential in
WBEM requests (instead of the CMS certificate). To authenticate using the WBEM certificate, select
Use certificate instead in the WBEM settings section of the System Protocol Settings page. See
Setting protocols and credentials for a system or group of systems for more information. To configure
the WBEM certificate, use the Configure or Repair Agents task. See Configuring managed systems
from a Windows CMS for more information.
NOTE: The WBEM client certificate authentication feature is supported only on HP-UX systems,
that have WBEM Services 2.5 installed for HP SIM.
Security
25
Credentials
In HP SIM, there are three different types of credentials:
•
System credentials
Credentials used by identification to access managed systems. These credentials include
WBEM, WS-MAN, and SSH credentials, Sign-in, SNMP community string, and Single Sign-On
credentials. For more information, see System credentials.
•
Discovery task credentials
Credentials used by a discovery task that apply to all systems discovered by that task. For
more information, see Configuring credentials for discovery tasks.
•
Global Credentials
Global credentials are system credentials that apply to all systems. For more information, see
Global credentials.
Related information
Privilege elevation
Privilege elevation enables you to sign in as an unprivileged user and elevate the privilege to run
a tool and support running tools on operating systems, such as AIX and Solaris.
License Manager
License Manager enables you to view and manage product licenses within the HP SIM user interface.
To access additional information about Updates and Upgrades and Technical support, contact
your HP services or HP partner representative or access the IT Resource Center (ITRC) at
www.itrc.hp.com.
NOTE: To run License Manager, you must have administrative rights on the CMS (to set, select
Options+Security→Users and Authorizations→User) and choose the Configure CMS Security option,
and the All Tools toolbox (to set, select Options+Security→Users and Authorizations→User) on the
managed systems that you want to license.
You can view and assign licenses to specified target systems discovered by HP SIM. A product
may use artificial systems to contain licenses. Therefore, you may see names of non-existent systems.
System licenses can be reviewed by product. Licenses can be associated with specific systems.
Licenses can be collected and deployed to management processors. New licenses can be added
individually or in bulk from a file.License Manager database tables are updated and synchronized
daily at midnight or at HP SIM startup, and expired license information is sent to registered plug-ins.
For some products, License Manager only permits users to review system licenses, available licenses,
and add licenses. For other products, License Manager allows association of licenses with systems
selected by the user. The association of the license is dependent on the particular product. For
some products, licenses can be freely associated with selected systems and those associations can
be changed. However, in most cases the license is locked to the system once it is used with the
product. Once locked, associations can no longer be changed. For other products, the product
association is permanent once made in License Manager. Finally, some products allow License
Manager to manage their licenses entirely such that selection and licensing systems is final. The
distinction between these latter modes is that associations may be changed if the user options
include Assign / Unassign and are final if there is one option, Apply.
License Manager includes functionality to collect and deploy licenses with most management
processors. The License Manager core establishes and maintains a secure communication channel
for license deployment with the management processor through two options provided by HP SIM,
Secure Sockets Layer (SSL) and Secure Shell (SSH). Both, SSL and SSH meet the requirements for
a secure channel. If the target systems are management processors, the management processor
26
Product overview
must support SSH and you must provide the required credentials. An SSH based solution uses CLP.
All management processor firmware releases include support for SSH/CLP. ProLiant SSH/CLP
support is included in v1.70 or later of the management processor firmware. Integrity SSH/CLP
support is included in management processor firmware. All management processors can be updated
to this version or later. The license collection uses an HTTP based mechanism and operates without
credentials. Management processor firmware in many instances allows the user to define if license
information is available on demand using this mechanism.
Table 1 Supported hardware for Integrity management processor license collections
Hardware
Product name
Server type
Firmware support
rx2660
Merlion
Rack
F.02.19 or greater
rx3600
Ruby
Rack
F.02.19 or greater
rx6600
Sapphire
Rack
F.02.19 or greater
BL860c
Tahiti
Blade
T.03.07 or greater
BL870c
Borabora
Blade
T.03.07 or greater
NOTE: The new management processor license collection is supported on management processor
and management processor devices. Deployment is supported on management processor and
management processors with newer firmware versions.
In some instances, licenses are managed and controlled by the licensed system (remote licensing).
In this case, License Manager provides the facility to collect and deploy licenses to those systems.
For non-management processor systems, communication used is a Microsoft DCOM mechanism.
For some products, the license is stored in a licensing structure in the Windows registry on the
licensed system. License Manager employs Microsoft's remote registry API over the DCOM protocol
to assign licenses to and collect license information from those remote systems. License information
is duplicated in the HP SIM database, but licenses are managed remotely and must be periodically
collected to keep this information current. Authentication credentials for the specified systems are
needed when licenses are sent to the specified system. If WBEM authentication credentials have
been provided for a specific target, these credentials are used. If specific credentials have not
been provided, each set of WBEM credentials provided as global credentials are used in turn. If
no credentials are provided, the connection is attempted using the default credentials of the HP
SIM server. The remote registry service must be started and run on candidate target systems for
key collection or assignment.
NOTE: Management processors have used two key formats (key format v0 and the current v1).
The original v0 license key has limited support in License Manager. License input using a v0 key
fails. However, it is rare that you will encounter a v0 key license. All v1 key licenses work. Both
v0 and v1 keys can be collected, but only v1 keys can be deployed.
NOTE:
Automatic collection of management processor licenses is not supported.
NOTE: You do not have support or upgrade options by default. After July 9, 2007, all license
keys are included in one year of 24 x 7 Software Technical Support and Update Service. The
License Manager informs you which license keys are "support and update enabled" and which
license keys require the purchase of future updates and upgrades.
CLI mxlmkeyconfig
The CLI mxlmkeyconfig allows you to combine all the License Manager key files into one file instead
of having to execute multiple files. Combining these files into a single file makes it easier when
adding keys from a file through the License Manager graphical user interface (GUI).
The mxlmkeyconfig command takes all the keys and related information and places it in the resulting
key file. The CLI program will not allow duplicates. If there are duplicate <keystring> values, a
License Manager
27
warning message appears and only the first value is placed in the resulting key file. If badly
formatted files are encountered, warning messages appear.
The key file is created when CLI mxlmkeyconfig is executed. If the resulting key file already exists,
then the previous keys remain and the information from the source key files are added to the
resulting key file.
HP SIM command line tools
Use the CLItools to execute basic UNIX and Windows commands remotely on one or more systems.
NOTE: For additional information about the individual commands, see the associated manpage
on an HP-UX, ESX (non-embedded), Solaris, IBM, and Linux system or the Windows command line
help where the command tool is installed.
NOTE: Command line tools provided by HP-UX and Linux, such as the ls and df commands,
are run as root by default. For security reasons, you might want them to run as a specific user to
avoid permitting unintended capabilities to a user.
Procedure 1 Launching a command line tool
1.
Choose one of the following:
•
Select Tools→Command Line Tools→UNIX/Linux for Linux or UNIX command line tools.
•
Select Tools→Command Line Tools→Windows for Windows command line tools.
2.
Select the command line tool that you want to run, and follow the steps to launch the tool. For
assistance with the steps, see Managing with tasks.
3.
4.
5.
Click Run Now to launch the tool.
In the Parameters field, enter the parameters for the tool.
If applicable, enter the privilege elevation password.
Command line interface
Use the mxexec command to launch these command line tools on one or more systems from the
command line interface. For assistance with this command, see the HP Systems Insight Manager
Command Line Interface Guide, at http://www.hp.com/go/insightmanagement/sim/docs.
Custom tools
Custom tools are executed on the CMS and on target systems. They can be scripts, batch files, or
executables that can reference environment variables set by the tool in order to access system or
event information. For example, creating a custom tool to launch Notepad. You can create or
launch SSA, MSA, and WLA tools. You can create the following types of custom tools:
•
Remote tool
A tool that runs on selected target systems. It might copy files to the target systems or run
specific X-Window applications on the target systems. You can schedule this tool.
•
CMS tool
A tool that runs on the CMS. It is usually a script or batch file and can pass in environment
variables. Using Automatic Event Handling, you can configure this tool to run when events
are received. You can schedule this tool.
•
Web page tool
A tool that launches a web URL. The URL is launched in a separate browser window on the
CMS. You cannot schedule this tool.
For more information on custom tools, see Custom tools.
28
Product overview
4 Initial setup
The initial setup involves setting up managed systems, configuring discovery, configuring event
handling, adding users, and defining authorizations. It assumes that you just completed the
installation of your CMS. If you bypassed or canceled the First Time Wizard, the following steps
assist you in setting up your environment to run HP SIM.
NOTE: The First Time Wizard starts the first time a user with administrative rights signs in to HP
SIM. If the wizard is canceled before completion, it restarts each time a user with administrative
rights signs in. You can cancel and disable the wizard from automatically starting by selecting the
Do not automatically show this wizard again checkbox. You can manually start the wizard by
selecting Options→First Time Wizard.
If you are a new administrator of an existing management domain, it might be useful for you to
familiarize yourself with these steps, even though your CMS has already been through the initial
setup. The steps in this process are common tasks that HP SIM administrators perform on a regular
basis.
Table 2 Initial setup
Name
Product registration
Description
Access
When the HP SIM software is
Product registration
registered with HP, registration inclues:
• Software update notification
• Product support alerts
• Optional newsletters with tips and
tricks for using your HP SIM
product
Performing Initial setup
• Setup managed systems
Performing Initial setup
• Configure storage systems
• Configure protocol settings
• Configure discovery
• Add new users
• Configure e-mail settings
• Configure paging settings
• Set up automatic event handling
Signing in
Sign in through the GUI or the CLI.
Signing in
Signing out
Sign out through the GUI or the CLI.
Signing out
Setting language locale
Sets the language or locale in your
Setting language locale
operating system, in a command shell,
or in your web browser to English or
Japanese.
First Time Wizard
Provides step-by-step instructions for
First Time Wizard
performing the initial configuration of
HP SIM.
Setting language locale
You can set the language or locale in your operating system, in a command shell, or in your web
browser to English or Japanese and run HP SIM. Both the CMS and the managed systems must
support all the desired languages. The language presents all the labels, menus, and status and
error messages in HP SIM in the requested language. The GUI shown in your browser appears in
Setting language locale
29
the preferred language of the web browser. Also, tools and tasks executed interactively through
the CMS have the same language as the language the tool command line is executed with on the
target system. This enables your web browser to run tools, create scheduled tasks, and manually
run scheduled tasks in the preferred language. Likewise, the language setting of your command
shell is forwarded through the mxexec and mxtask command line commands to set the language
for executing a tool, manually executing a task, or creating a scheduled task when the command
line for the tool is executed on the target systems.
The CMS has another locale independent from any user session the CMS Locale. Some features
inherit this locale, such as logging files and e-mail messages sent by Automatic Event Handling,
which are neutral from any session.
Setting the web browser language or locale
When you configure your web browser and select the language you prefer, the HP SIM GUI
displays the date and time in the language requested by the browser, although the overall HP SIM
GUI appears in English or Japanese. The browser locale also sets the language and encoding in
the Secure Shell (SSH) command shell in which the tool command executes. The browser locale is
saved on a scheduled task when it is created and used to set the language and encoding on the
target system for SSA tools and on the execution system for MSA tools. When you manually execute
a task, the current browser locale overrides the locale set in the scheduled task for this single
manual execution of the task (for SSA and MSA tools).
Procedure 2 Configuring the language settings in Internet Explorer for Japanese
1.
2.
3.
4.
5.
6.
Select Tools→Internet Options→[Languages]. The Language Preference window appears.
Click Add. The Add Language window appears.
Select Japanese from the list.
Click OK to add it to the language preference list.
Select Japanese in the language preference list, and click Move Up until it is at the top of the
list, or select and remove any other languages listed here.
Click OK. Continue to click OK until you have closed all windows.
Procedure 3 Configuring the language settings in Mozilla for Japanese
1.
2.
3.
4.
5.
6.
Select Tools→Options→Contents and click Choose in the languages section. The Language
window appears.
Open the navigator dropdown from Select language to add option.
Select Japanese from the list.
Click Add to add it to the language preferences list.
Select Japanese in the language preferences list, and click Move Up until it is at the top of the
list, or select and remove any other languages listed here.
Click OK to save preferences, and close the window.
Configuring the language or locale settings on Windows operating systems
To install and run HP SIM in Japanese mode, you must first set the Locale for the current user to
Japanese. After you have completed these steps, install HP SIM and it will run in Japanese language
mode. For more information about installing HP SIM, see the HP SIM installation guides located
at http://www.hp.com/go/insightmanagement/sim/docs, and then select the appropriate guide
for your operating system.
The HP SIM CLI commands use the Code page to determine what locale and encoding to output,
as do the Command Prompt commands, such as dir.
Procedure 4 Configuring Windows XP language settings for Japanese
1.
2.
3.
30
Select Start→Settings→Control Panel→Regional and Language Options→Advanced.
Under Language to use for non-unicode programs, select Japanese.
Click Apply to apply changes.
Initial setup
4.
5.
6.
Reboot the system.
Open a command prompt window.
Execute the chcp 932 (Japanese) and chcp 437 (English) commands to toggle between
the two languages.
Procedure 5 Configuring Windows 2000 locale settings for Japanese
1.
2.
3.
4.
5.
6.
7.
8.
Select Start→Settings→Control Panel→Regional Options→General.
Click Set default. The Select System Locale window appears.
From the dropdown list, select Japanese.
Click OK.
Click Apply.
Reboot the system.
Open a command prompt window.
Execute the chcp 932 (Japanese) and chcp 437 (English) commands to toggle between
the two languages.
Configuring HP-UX and Linux language settings
Procedure 6 Configuring HP-UX and Linux language settings
1.
2.
Ensure that support for the desired languages and character map encodings are installed on
the managed systems (for SSA tools) and execution systems (for MSA tools, usually the CMS).
To verify the language settings and see if the language and character map encodings you
need are listed, execute:
locale -a
3.
To run command tools of the x-window command type, ensure that the X Display you select
to display the X-window application has been configured to use the font lists required for that
application and the requested language. For Motif X Window applications (X clients), it might
be enough to have the Common Desktop Environment (CDE) configured for the language you
want to display. It should have all the X11 resource file properties for X11 Motif or Gnome
widget set font lists configured with fonts that support the language and encoding you want
to use (for example, Japanese and SJIS), or you must configure the X resource file of your X
clients to set the specific font lists you want to use for each application. To find out what fonts
are installed, knowing what languages the X application supports, seeing how the application
sets fonts in its app-default file, run:
xlsfonts
4.
Edit the X Resource file properties on the X clients to configure the application font list properties.
Configuring HP SIM
HP SIM has a configuration file that you can be modify to override locale settings that control:
•
CMS locale
The locale of the CMS, which affects the language used in the CMS logs and e-mails sent by
Automatic Event Handling tasks
•
Target locale
The locale, character map encoding, code page, and LANG variables used when executing
a command on a remote system through SSH
Setting language locale
31
This configuration file is globalsettings.props and is located on the following operating
systems:
•
On Windows
C:\Program Files\HP\Systems Insight Manager\config\
globalsettings.props.
•
On HP-UX and Linux
/etc/opt/mx/config/globalsettings.props.
CMS locale
By default, the CMS Locale is determined by the environment. On an HP-UX CMS, it looks for
"LANG=" in "/etc/rc.config.d/LANG" and uses that setting. On a Linux CMS, it looks for
"LANG=" in "/etc/sysconfig/i18n" and "/etc/sysconfig/language" and uses
that setting. On a Windows CMS, it uses the default locale setting of the Java™ Virtual Machine,
which is based on the locale setting of the user account used to install HP SIM.
If the locale used by the CMS is not the desired locale, you can manually edit
globalsettings.props and add a line, such as CMSLocale=en_US, or whatever locale you
want to override the CMS locale.
Target locale
For HP SIM, the character map encoding for a locale might be different for each target operating
system and each language. To enable HP SIM to select the encoding to use for each target system
(for SSA tools) or each execution system (for MSA tools, usually the CMS), HP has defined the
format of some properties you can add to the globalsettings.props file. These properties
provide the character map encoding to use for each language on each operating system, what
Code Page code to use for each language on a Windows target and execution system, and the
string that defines that encoding in the LANG environment variable on a Linux or HP-UX system.
Also, some properties define what to use for unsupported languages on each operating system.
The format of the property names are:
"TargetCharacterMapEncoding_" + language + "_" + os_name + "=" + encoding
"TargetCodePage_" + language or encoding + "_" + os_name + "=" +
code page number "TargetLangEncoding" + encoding + "_" + os_name +
"=" + encoding string
where language is the two-character code for a language, os_name is the uppercase keyword
for the supported operating system (for example, LINUX, HPUX, WINNT), and encoding is the
canonical name for character map encoding for that language on the operating system. The
supported names can be found in column 2 of the web page http://java.sun.com/j2se/1.4.2/
docs/guide/intl/encoding.doc.html.
The entries appear similar to the following:
TargetCharacterMapEncoding_ja_LINUX=EUC_JP
TargetCharacterMapEncoding_??_LINUX=ISO8859_1TargetCharacterMapEncoding_ja_HPUX=SJIS
TargetCharacterMapEncoding_??_HPUX=ISO8859_1
TargetCharacterMapEncoding_ja_WINNT=SJIS
TargetCharacterMapEncoding_??_WINNT=ISO8859_1
TargetCodePage_ja_WINNT=932
TargetCodePage_??_WINNT=437
32
Initial setup
For the Windows target and execution systems, use these properties to choose the chcp command
to execute in the SSH command prompt shell, to force the language and encoding to set to execute
the Windows command line command. For example:
chcp 932 (forces the language to Japanese Shift-JIS)
chcp 437 (forces the language to US English with at least ISO-8859-1 support)
For Linux and HP-UX target and execution systems, use the encoding with the locale to define the
LANG environment variable to be defined in the SSH environment on the target and execution
systems. Example values can be found by executing the locale -a command on these operating
systems. For example:
LANG=en_US.iso88591
(US English language, ISO-8859-1 encoding on HP-UX)
LANG=ja_JP.SJIS
(Japanese language, Shift-JIS encoding on HP-UX)
LANG=ja_JP.eucjp
(Japanese language, EUC-JP encoding on Linux)
LANG=en_US.utf8
(US English language, UTF-8 encoding on Linux)
Signing in
Access the GUI using a web browser or the CLI using a SSH client.
When you first sign in to HP SIM, the First Time Wizard window appears. The First Time Wizard
provides information and procedures for getting started with HP SIM. Click Close to exit the window.
If you do not want this window to appear each time you sign in to HP SIM, select Do not
automatically show this wizard again, and then click Close. See the First Time Wizard for more
information.
Signing in to the GUI
You can access the HP SIM GUI from any network client using a web browser. For information
about which browsers are supported, see the HP SIM installation guides located at HP Systems
Insight Manager User Guide, at http://www.hp.com/go/insightmanagement/sim/docs, and then
select the appropriate guide for your operating system.
NOTE: After accessing HP SIM, if you open additional windows in the same browser using the
same HP SIM URL, you do not need to sign in to HP SIM. Any time you start a new instance of the
browser and navigate to HP SIM, you must sign in.
If you sign in to HP SIM and then navigate to a different website, your HP SIM session times out.
If you use the same browser process to return to HP SIM within 20 minutes, you are not required
to sign in.
Signing in
33
Manually signing in to HP SIM
There are several reasons to manually sign in to HP SIM.
•
If automatic sign-in fails, the sign-in page appears
This might occur if the user is logged in to the operating system using an account that is not
an HP SIM account.
•
If automatic sign-in is not attempted
This might occur if the browser is not properly configured for automatic sign-in, or the feature
is disabled in HP SIM.
•
If you click Sign Out from HP SIM
This enables you to specify another user account if you are logged in to the operating system
with a different account.
Procedure 7 Manually sign in to HP SIM
1.
Open a supported web browser on any network client, and enter the address for the sign-in
page by navigating to http://hostname:280/, where hostname is the host name of the
CMS.
NOTE: If you are signing in directly on a Windows CMS, you can use the HP SIM desktop
icon to access the sign-in page, or you can select Start→Programs→HP Systems Insight
Manager→HP Systems Insight Manager.
2.
Enter your user name, password, domain, and time zone if requested.
NOTE: If the browser can determine its time zone with certainty, then the Time zone selection
field does not appear.
3.
Click Sign-in.
Automatically signing in
You can sign in to HP SIM using the same account with which you are logged in on your desktop,
bypassing the HP SIM sign-in page. If user groups are configured for HP SIM, membership in these
groups is accepted and treated the same as if you manually signed in.
Configuring the CMS
•
HP SIM must be running on a Windows CMS that is a member of a Windows domain. The
browsing system must be a member of the same domain.
•
The HP SIM service account must be a domain account; local accounts can not be used.
•
The CMS must be registered with an SPN in the domain, which requires a domain administrator
to configure. From any system that is a member of the domain, the domain administrator can
run the setspn.exe utility from the Windows Support Tools. For example:
setspn -a HTTP/<cms_fqdn> <sim_service_account>
Where HTTP is in all capital letters, <cms_fqdn> is the FQDN of the CMS, and
<sim_service_account> is the domain account under which HP SIM service runs.
IMPORTANT: Automatic sign-in fails if the SPN registered more than once. If you change
the name of the HP SIM service account, you must first delete the SPN associated with the old
service account name, and then register the new service account name:
setspn –d HTTP/<cms_fqdn> <old_sim_service_account>
setspn –a HTTP/<cms_fqdn> <new_sim_service_account>
34
Initial setup
NOTE: Local accounts cannot be used for HP SIM service account if automatic sign-in is
desired.
•
The automatic sign-in feature must be enabled in HP SIM in the globalsettings.props
file. You can use the mxglobalsettings command, or directly modify the file. Set the value
for the AutomaticSignIn property to 1. Restarting HP SIM is not necessary.
Configuring the browser
•
Supported in Internet Explorer 7 and Firefox. Internet Explorer 6 is not supported.
•
The browsing system must be remote; browsing locally from the CMS does not perform
automatic sign-in.
•
The browsing system and the CMS must be members of the same Windows domain.
•
You must be logged in to the browsing system with a domain account that is configured as a
user account in HP SIM, or is a member of a user group configured in HP SIM.
•
There must be no proxy servers between the browser and the CMS. Use the proxy bypass list
in the browser, or use no proxy at all.
•
The browser must be configured to support automatic sign-in.
Procedure 8 Configuring the browser in Internet Explorer
1.
2.
3.
4.
In Internet Explorer, enable Integrated Windows Authentication under Tools→Internet
Options→Advanced tab.
The CMS must be in the Local Intranet or Trusted Sites zone, which can be configured under
the Tools→Internet Options→Security tab.
(Optional) If the CMS is in the Internet Explorer Local Intranet zone, select Automatic Logon
only in Intranet zone.
(Optional) If the CMS is in the Internet Explorer Trusted Sites zone, select Automatic logon
with current user name and password.
In Firefox:
Firefox must be configured with a list of sites (for example, the CMS) where automatic sign-in can
be performed, and should be restricted to local intranet sites. This list can be configured by entering
about:config in the Firefox address bar. From the list of Preference Names, select
network.negotiate-auth.trusted-uris and either double-click or right-click, and select Modify. Here,
you can specify a comma-separated list of URLs or domains, enter the list of URLs used to access
HP SIM. For example:https://cms_fqdn, where cms_fqdn is the FQDN of the CMS.
Behavior
When automatic sign-in occurs, an intermediate sign-in page appears. If you click Cancel from this
page, the manual sign-in page appears. You might want to cancel automatic sign-in if any
unexpected network or domain errors occur. If any browser configuration errors are detected,
automatic sign-in is cancelled and the manual sign-in page appears along with the configuration
error.
Failures encountered during automatic sign-in are logged as normal sign-in failures in both the
audit log and the event log. If automatic sign-in is not attempted, no failure is detected or logged
by HP SIM.
Signing in
35
If automatic sign-in is configured, you can manually sign in to HP SIM.
•
If automatic sign-in fails, the manual sign-in page appears
This might occur if you are logged in to the operating system using an account that is not an
HP SIM account.
•
If automatic sign-in is not attempted
This might occur if the browser is not properly configured for automatic sign-in, or the feature
is disabled in HP SIM.
•
If you click Sign Out from HP SIM
This enables you to specify another user account to use if you are signed in to the operating
system with a different account.
Signing in using SSL
CAUTION: If you are not certain that the HP SIM system to which you are browsing to is actually
the HP SIM system you think it is, do not select either of the last two SSL options. You might give
your sign-in credentials to a rogue system disguised as your HP SIM system, or you might import
a certificate from a rogue system disguised as your HP SIM system and give your sign-in credentials
to that rogue system.
If your browser is not configured with the SSL system certificate of the HP SIM system, a security
alert regarding a certificate of untrusted origin might appear when first browsing to HP SIM using
SSL. If a security alert appears, perform one of the following procedures:
•
Use the browser to import the certificate into your browser. View the certificate by
double-clicking the lock icon (
), and then installing the certificate.
•
Export the HP SIM system certificate to a file by first browsing from a local browser on the HP
SIM system, and then manually importing it into the remote browser.
•
Sign in to the HP SIM system this time without a trusted certificate, but be sure to import the
certificate later. Your data is still encrypted.
After you have an SSL session established with HP SIM, all communications between the browser
and HP SIM are secure through SSL.
Logging in to the CLI
You can access the HP SIM CLI directly from the CMS or from any network client using SSH client
software.
On an HP-UX or Linux CMS, you can log in to the operating system as any valid HP SIM user and
use the CLI. Not all CLI functionality is available to all users; some functions are only available to
users with administrative rights or operator rights on the CMS. On a Windows CMS, some
commands require that the user be a member of the local Administrators group. These commands
include:
36
•
mxagentconfig
•
mxauth
•
mxcert
•
mxcollection
•
mxexec
•
mxglobalprotocolsettings
•
mxglobalsettings
Initial setup
•
mxlog
•
mxmib
•
mxngroup
•
mxnode
•
mxquery
•
mxreport
•
mxstm
•
mxtask
•
mxtool
•
mxtoolbox
•
mxuser
•
mxwbemsub
Logging in to the CMS directly
Procedure 9 Logging in to the CMS directly
1.
Log in to the CMS using a valid user name and password ( SSH system name ).
HP SIM grants authorizations based on your operating system user login.
2.
Open a terminal window or a command prompt window to execute HP SIM commands.
Logging in to the CMS remotely using an SSH client
Procedure 10 Logging in remotely using an SSH client
1.
2.
Open an SSH client application on any network client.
Log in to the CMS through the SSH client software, using a valid user name and password.
HP SIM grants authorizations based on your operating system user login.
Single Sign On
Single Sign On allows a link within an HP SIM page to establish an authenticated browser session
to a managed system that supports Single Sign On without requiring users to re-enter their user
names and passwords. However, if you are trying to establish an authenticated browser session
with another instance of HP SIM running on another system, you must re-enter your user name and
password. Single Sign On links exist wherever there is a link to another system.
NOTE: HP SIM is the initial point of authentication. You must browse to another managed system
from within HP SIM.
If you browse to a managed system using any method other than the links within HP SIM, Single
Sign On is not supported, and you must enter the appropriate user name and password for each
managed system. You must set up managed systems to trust an HP SIM system before accepting
a Single Sign On command. Trust is set up at the system by importing the HP SIM system certificate
into the Trusted Management Servers List of the system. See Setting up trust relationships for more
information.
NOTE: Single Sign On does not work on a Virtual Cluster system. However, it does work on the
physical systems which compose the cluster.
Single Sign On
37
Signing in
Signing in to HP SIM allows access to HP SIM and determines what authorizations you have in
HP SIM. Browsing to HP SIM using SSL encrypts all information between the browser and HP SIM,
including sign in credentials. SSL securely encrypts the password and helps prevent someone from
capturing and replaying a valid sign-in sequence.
The sign-in page has three fields:
•
User Name. The name of the user.
•
Password. The password for the user name.
•
Domain Name. The Windows domain of the user. This field appears in Windows environments
only.
NOTE: In a Windows environment, administrators are selected from the operating system during
the HP SIM installation. To sign in to HP SIM, enter the appropriate information for the account in
the fields provided. The User Name field specifies the user name, and the Domain Name specifies
the Windows domain. These fields are required in a Windows environment.
After the credentials are securely received by HP SIM, HP SIM validates the account, verifies that
the IP address is valid, and authenticates the credentials against the Windows domain. See Users
and authorizations for details about accounts.
Some sign in failures are caused by failure in the operating system, and some are caused by failure
within HP SIM. Use the operating system User Management tools to address these potential login
failures:
•
Sign in credentials are not entered correctly. Passwords are case-sensitive.
•
The account has been deleted, disabled, or locked out.
•
The password for the account has expired or must be changed.
The following reasons for sign-in failure within HP SIM can be addressed on the HP SIM Users and
Authorizations pages:
•
The account is not an account for HP SIM.
•
You attempt to sign in from an IP address that is not valid for the specified account. The browser
systems can also cause sign-in failures.
•
The browser is not configured to accept cookies.
NOTE: For more information, go to http://h18013.www1.hp.com/products/servers/
management/hpsim/infolibrary.html, and select the appropriate guide for your operating
system.
•
A cookie blocker is installed.
NOTE: HP SIM can be configured to log an event in the HP SIM Event Database when a sign-in
attempt fails or succeeds and when a sign-out occurs.
Sign-in authentication on Linux and HP-UX
HP SIM uses PAM to authenticate users who sign in to the web server interface on Linux and HP-UX.
38
Initial setup
Configuring PAM on a Linux system
The administrator of a Linux CMS can customize the PAM that HP SIM uses. The /etc/pam.d/
mxpamauthrealm file contains the authentication steps for the HP SIM web server interface. The
defaults for this file are:
•
#%PAM-1.0
•
auth required /lib/security/pam_unix.so
•
account required /lib/security/pam_unix.so
•
session required /lib/security/pam_unix.so
This default setup directs PAM to use the standard UNIX authentication module to authenticate
users attempting to sign in to the HP SIM web server interface. Standard calls from the system
libraries access account information usually read from /etc/password or /etc/shadow.
The administrator of the system can adjust these requirements to conform to the security requirements
of the system. For example, if the security policy on the system is time dependent and /etc/
security/time.conf is configured, you could adjust mxpamauthrealm to:
•
#%PAM-1.0
•
auth required /lib/security/pam_unix.so
•
account required /lib/security/pam_unix.so
•
session required /lib/security/pam_unix.so
Configuring PAM on an HP-UX system
Customizing PAM security on HP-UX is similar. All of the PAM configurations are stored in /etc/
pam.conf.
The lines for HP SIM on HP-UX 11i are:
•
mxpamauthrealm auth required /usr/lib/security/libpam_unix.1
•
mxpamauthrealm account required /usr/lib/security/libpam_unix.1
•
mxpamauthrealm session required /usr/lib/security/libpam_unix.1
The lines for HP SIM on HP-UX 11i v2 are:
•
mxpamauthrealm auth required /usr/lib/security/$ISA/libpam_unix.1
•
mxpamauthrealm account required /usr/lib/security/$ISA/libpam_unix.1
•
mxpamauthrealm session required /usr/lib/security/$ISA/libpam_unix.1
If you want the HP SIM web server login model to match what is configured for your other login
methods (telnet, rlogin, login, ssh, and so on), configure the same plug-in modules that are used
by these other login methods. These modules must be defined by the login service name in the
/etc/pam.conf file or the /etc/pam.d/login file.
Authenticating Windows AD Users from Linux CMS
It is presumed that the Linux CMS has already been joined as a member of the LDAP server such
as Windows AD. By joining the Linux server to AD yield the benefit of making Active Directory’s
authentication process available to the Linux. The Linux user name and password can be
authenticated using mechanisms such as Kerberos 5 network authentication. Authenticating Windows
AD users from the Linux CMS requires changes in the /etc/pam.d/mxpamauthrealm file. By
doing so, it does not require domain name prefix to be passed for the username during login to
HP SIM. Configuring authentication through Kerberos authentication mechanism
auth required /lib/security/pam_unix.so
auth sufficient /lib/security/pam_krb5.so try_first_pass
Sign-in authentication on Linux and HP-UX
39
account required /lib/security/pam_unix.so
account sufficient /lib/security/pam_krb5.so try_first_pass
session required /lib/security/pam_limits.so
session required /lib/security/pam_unix.so
session optional /lib/security/pam_krb5.so
The configuration would change based on the underlying authentication mechanism (Kerberos,
LDAP etc) that is followed to join the Linux CMS to AD. Appropriate authentication modules such
as pam_krb5.so or pam_ldap.so should be specified in the mxpamauthrealm file.
The configuration files of other services such as login can be referenced to modify
mxpamauthrealm. HP recommends you restart the CMS incase of any changes made to this file.
For more information on:
•
Joining Linux to Windows AD based on Kerberos authentication mechanism, please check
the link uhttp://www.packetwatch.net/documents/guides/2010021501.php
•
PAM configuration for LDAP client systems, please check the link http://
directory.fedoraproject.org/wiki/Howto:PAM
Signing out
Be sure to sign out from HP SIM to prevent unauthorized access to your active session while you
are away.
If you are monitoring HP SIM, your session remains active and continually refreshes, unless you
close the browser or navigate to another website. If you navigate to another browser, HP SIM
signs you out after 20 minutes.
As long as you are actively working in HP SIM, your session stays active. If the session is inactive
for more than 20 minutes, HP SIM ends the session and signs you out after 20 minutes of inactivity.
See Configuring browser timeout options for more information about keeping sessions active.
Signing out from the GUI
Procedure 11 Signing out from the GUI
1.
2.
From the HP SIM banner, click Sign Out.
Close the web browser.
Logging out from the CLI
Log off of the CMS or the SSH client application.
Product registration
You can register your HP SIM software with HP. Registration includes the following benefits:
•
Software update notification
•
Product support alerts
•
Optional newsletters with tips and tricks for using your HP SIM product
NOTE:
You must be connected to the Internet to register HP SIM.
NOTE: After you upgrade or complete a fresh installation of HP SIM, you are reminded to register
each time you sign in. You are reminded once per day only, and only if you have not previously
registered or applied a product license.
Procedure 12 Registering HP SIM
1.
40
If the Registration window is not already open, select Options→Registration.
Initial setup
2.
3.
Click Register Now. The User sign-in page appears.
If you are already a member, enter your e-mail address and password under Existing users.
Click Sign-In and the Product Selection page appears. If not:
a. Enter your e-mail address and password under First time users. Click Sign-In. The User
profile page appears.
b. Enter the requested information. Items marked with an asterisk are required.
4.
5.
6.
7.
8.
Click Next. The Product Selection page appears.
Click Next. The Enablement key request page appears.
Click Next. The Transaction summary page appears.
Click Next. The License certificate page appears.
Your password certificates and license key/password file are sent to the e-mail address you
provided. Click Save license key/password file for HPSIMREG to save the license key/password
file to your system.
9. Select and copy the License Key number.
10. In the Registration window, position the cursor in any of the five fields forming the input box,
and press the Ctrl + V keys to paste the license key. You can also right-click to paste.
The license key appears with five characters in each field.
11. Click Submit. HP SIM notifies you that the license key was added successfully. Close the
Registration window.
First Time Wizard
The First Time Wizard helps you configure the following settings on the CMS. After configuring a
setting, click Next to continue the First Time Wizard setup procedure. The First Time Wizard does
not apply any changes until you click Finish on the Summary page.
NOTE: The default settings in Firefox block the First Time Wizard. You must disable the pop-up
blocker in Firefox to see the First Time Wizard.
The First Time Wizard includes the following options:
•
Introduction
Describes the purpose of the First Time Wizard. You can cancel the First Time Wizard and
disable the wizard from automatically starting when an administrative user signs in.
•
Managed Environment
Specifies all operating systems managed by the CMS. The selections made here configure HP
SIM to show collections, tools, and reports only for managed environments that are selected.
This page also collects required details for each TDEF selection, such as IP address of the
Ignite server, sign in credential information, and so on.
•
Discovery
Use the wizard to enable discovery, set up the discovery schedule, and enter the IP address
ranges or host names of the systems you want to discover. Discovery is the process HP SIM
uses to find and identify systems on your network and populate the database with that
information. A system must be discovered to collect data and track system health status.
•
Credentials: System Automatic Discovery
Use the wizard to set the sign-in credentials and the SNMP credentials for the System Automatic
Discovery task.
•
Configure Managed Systems
Configure managed systems as they are discovered, by configuring WBEM and WMI, SNMP,
SSH access, and trust relationship.
First Time Wizard
41
•
WBEM/WMI Mapper Proxy
To retrieve managed system information on Windows systems, enter the mapper proxy system
host name and port number.
NOTE:
•
This page only appears if you selected to manage a Windows system.
Privilege Elevation
Enable privilege elevation if, on HP-UX, Linux, and ESX managed systems, you are required
to sign in as a non-root user and then request privilege elevation to run root-level tools.
•
E-mail
Enter the e-mail settings that the CMS will use to send e-mail notifications. You can set up
Automatic Event Handling tasks that prompt HP SIM to send e-mails when the CMS receives
a specific event.
•
Summary
Displays all First Time Wizard settings with the option to modify settings or to finish the First
Time Wizard.
The First Time Wizard configures only the basic settings of HP SIM. See the HP SIM installation
guides located at http://www.hp.com/go/insightmanagement/sim/docs, and the First Time
Wizard related topics for more information.
Managed Environment
From this page, select the operating systems that the CMS will manage. There are four options:
Windows, Linux, HP-UX, and Other. The selections made here configure HP SIM to hide collections,
tools, and reports for operating systems you do not manage. By default the CMS operating system
is selected on this page.
NOTE:
These settings can be verified or changed at any time, and the hidden collections, tools,
and reports can be made visible again. To change these settings from the HP SIM menu, select
Options→ Managed Environment.
Procedure 13 Configuring HP SIM to hide collections, tools, and reports
1.
Select the operating systems for the CMS to manage.
If you select Linux or HP-UX, select menu items, and provide required information. The HP-UX
menu items are for handling Integrity Extensions on a Windows or Linux CMS and are not
available on an HP-UX CMS.
If both Linux and HP-UX are selected on Managed Environment page, the same user name
must be specified for GlancePlus in both the places. Root user is used if no user name is
specified.
2.
Click Next to go to the next First Time Wizard step, or click Previous to return to the previous
step.
If you selected Linux or HP-UX, the system attempts to verify the prerequisites. For example,
for Ignite-UX, the system tries to connect to the Ignite server. If it is unable to do so, an error
message appears. After closing the error message box, you are return to the Managed
Environment First Time Wizard page until you provide valid information or cancel the selection.
The minor version of the tool inside the TDEF file changes each time a tool is re-registered, if a
later version is available.
First Time Wizard related topics
42
Initial setup
Discovery - FTW
HP SIM uses automatic discovery to find and identify systems on the network. The System Automatic
Discovery task is the default discovery task and is disabled by default. You can enable and configure
the System Automatic Discovery task by selecting to have it run immediately when First Time Wizard
finishes, or by selecting Options→Discovery from the HP SIM menu. You can create multiple
automatic discovery tasks from the Discovery page. See Configuring automatic discovery.
Procedure 14 Creating multiple automatic discovery tasks
1.
2.
3.
4.
5.
Select Run discovery once after wizard finishes to have the System Automatic Discovery task
run immediately after First Time Wizard finishes.
To schedule the task to run at a specific time, select Schedule.
To configure the System Automatic Discovery task to run on a regular schedule, enter how
often the task should run. The default frequency is once per day. If you clear the Automatically
execute discovery every option, the task is disabled after it is created.
In the Ping inclusion ranges, system (hosts) names, and/or hosts files field, specify the IP
addresses. If you want to use this task to discover SMI-S storage systems, include the IP address
of each SMI CIMOM. You can also enter Simple or FQDN host names. However, you cannot
enter a range of host names. To use an existing hosts file, enter the hosts file name in the
following format: $HostsFileName .
To go to the next First Time Wizard step, click Next, or to return to the previous step, click
Previous.
First Time Wizard related topics
Configuring System Automatic Discovery task sign in credentials
From this page, you can set sign in and SNMP credentials for the System Automatic Discovery
task. This window is skipped if did not configure discovery in the First Time Wizard Discovery
window.
Procedure 15 Set sign in and SNMP credentials for the System Automatic Discovery task
1.
To set the sign-in credentials for the System Automatic Discovery task, enter the user name
and password.
To add additional sign-in credentials, click Add. To delete existing sign-in credentials, click
Delete beside the credentials that you want to delete.
2.
3.
To have HP SIM try other credentials if the entered credentials fail, select If these credentials
fail, try other credentials that may apply....
Enter read community strings for SNMP credentials for the System Automatic Discovery task.
To add additional SNMP credentials, click Add. To delete existing SNMP credentials, click
Delete beside the credentials that you want to delete.
4.
5.
To have HP SIM try other credentials if the entered credentials fail, select If these credentials
fail, try other credentials that may apply....
To go to the next First Time Wizard step, click Next, or to return to the previous step, click
Previous.
First Time Wizard related topics
Configuring managed systems
The Configure Managed Systems page in the First Time Wizard enables you to configure managed
systems as they are discovered and to specify parameters for running Configure or Repair Agents.
This step is skipped if you did not configure discovery on the First Time Wizard Discovery page.
All steps are optional and can be configured from the HP SIM Options menu at a later time. To
skip this step, click Next to go to the next First Time Wizard step.
First Time Wizard
43
Procedure 16 Configure managed systems from the First Time Wizard
1.
2.
Select Configure newly managed systems when they are first discovered..
To specify credentials to configure the managed system for WBEM / WMI, SNMP, and SSH,
select from the following:
•
Use sign in credentials
This account must be an account with administrative privileges.
•
Use these credentials
Select this option to use another user name and password pair other than the one entered
into HP SIM.
3.
4.
Under Configure WBEM / WMI, select from the following:
•
Create subscriptions to WBEM events
•
Send a test WBEM / WMI indication to this instance of Systems Insight Manager to make
sure that events appear in Systems Insight Manager events lists
•
Use an HP SIM WBEM certificate (good for 10 years) rather than username/password to
manage the system
Under Configure SNMP, select from the following:
•
Set read community string
•
Set traps to refer to this instance of HP SIM
A read/write SNMP community string is automatically created on a managed Windows
system’s SNMP settings.
•
5.
Send a test SNMP trap to this instance of Systems Insight Manager to make sure events
appear in the HP SIM event lists
Under Configure secure shell (SSH) access, select from the following:
•
Host based authentication
All users from this instance of HP SIM are authenticated on the managed system.
•
Each user has to be authenticated on the managed system
Each user must be authenticated on the managed system.
6.
7.
Select Set trust relationship to "Trust by Certificate" to set a trust relationship between managed
systems and the CMS. This enables HP SIM users to connect to HP SMH, Onboard
Administrator, management processors, and Version Control Agent using the HP SIM certificate
for authentication.
To go to the next First Time Wizard step, click Next, or to return to the previous step, click
Previous.
Configuring the WMI Mapper Proxy
WBEM is used by HP SIM to identify and communicate with managed systems. Therefore, on
Windows systems, a WMI Mapper Proxy must be configured for this communication to take place.
Procedure 17 Configuring WMI Mapper Proxy
1.
2.
Enter the WMI Mapper Proxy host name and port number. The user name and password
credentials must be entered on the First Time Wizard Configure Managed Systems page.
To go to the next First Time Wizard step, click Next, or to return to the previous step, click
Previous.
First Time Wizard related topics
44
Initial setup
Configuring privilege elevation on HP-UX
From this page, you can enable privilege elevation for Linux, HP-UX, and ESX managed systems.
This enables you to sign in as an unprivileged user and elevate the privilege to run on these
operating systems.
You can also configure privilege elevation from the HP SIM menu by selecting
Options→Security→Privilege Elevation.
Procedure 18 Configure privilege elevation for ESX systems
1.
Select Enable privilege elevation for VMware ESX.
To configure privilege elevation for Linux and HP-UX systems, select Enable privilege elevation
for Linux & HP-UX.
2.
Select the elevation tool type from the menu.
If a password is required for the tool, select A password is required for this privilege elevation
tool.
3.
4.
5.
Optional: Edit the Privilege elevation tool command.
Select the user to sign in to the managed system:
•
Same as HP SIM signed-in user
•
Specify at run time
•
Use this user and enter the user name
To go to the next First Time Wizard step, click Next, or to return to the previous step, click
Previous.
First Time Wizard related topics
Configuring e-mail settings
Procedure 19 Email settings
1.
2.
3.
Enter the SMTP host name. The SMTP host is the outgoing e-mail server that the CMS uses to
send e-mail notifications.
In the Sender's e-mail address box, enter the e-mail address that the management server uses
when sending e-mail notifications.
Optional: Select Send test email and enter recipients e-mail address.
Click Send test email now.
4.
5.
To authenticate your SMTP server, select Server Requires Authentication.
Enter the account user name and password in the corresponding boxes.
NOTE: If you did not enter a valid SMTP host, HP SIM display an error message: The email
could not be sent: Could not connect to the SMTP host.
If you are changing the e-mail settings from the Options→Events→Automatic Event
Handling→Email Settings page, click OK to save changes.
NOTE: If you did not enter a valid SMTP host, HP SIM display an error message: The email could
not be sent: Could not connect to the SMTP host.
NOTE: If the Server Requires Authentication option is selected, and you enter incorrect account
information, an The email could not be sent: Authentication error message displays.
Additional e-mail settings
The globalsettings.props contains properties that can be set for additional information to
be included in e-mail messages.
First Time Wizard
45
EmailPrefixUserSubject
To have user defined information (from the e-mail information on the Actions page) displayed first
on the subject line of an e-mail, you must change the EmailPrefixUserSubject property in the
globalsettings.props file to True. Otherwise, HP SIM defined information appears first. The
globalsettings.props file is located at:
•
On Windows
It is typically located at C:\Program Files\HP\Systems Insight Manager\config\
globalsettings.props.
•
On HP-UX and Linux
It is located at /etc/opt/mx/config/globalsettings.props.
Restart the HP SIM service after the flag is set. To restart:
•
If EmailPrefixUserSubject = false
The format of the subject line is Device Name: Short Description from Alert: User's Defined
Subject.
•
If EmailPrefixUserSubject = true
The format of the e-mail subject line is User's Defined Subject: Device Name: Short Description
from Alert.
IMPORTANT:
This property does not need to be configured for the e-mail feature to work. This
property is automatically set to false in the globalsettings.props file and does not need to
be changed unless you want user defined text to appear before the HP SIM text in the subject line.
EmailKeywords
To include event information in an e-mail message, edit the EmailKeywords property in the
globalsettings.props file.
IMPORTANT:
Restart the HP SIM service if any of the keywords change.
Table 3 Keywords supported in the EmailKeywords property
46
Keyword
Description
TID
Trap ID
TDESC
Trap description
TSDESC
Short description about trap
TNAME
Trap name
TNOTENUM
Trap notice number
TRCVD
Trap received time
TADDR
Trap source address
TENTOID
Enterprise trap OID
TNOTSEV
Trap severity
TASSIGNTO
Trap assigned to
TCOMMENT
Trap comments
DNAME
Device name
DDISCOV
Device discovered time
Initial setup
Table 3 Keywords supported in the EmailKeywords property (continued)
Keyword
Description
DURL
Device URL
HDR
Header which can be used to format message
Related information
Summary
When you are finished entering information in the HP SIM First Time Wizard, review your selections
on the Summary Page, and then click Finish to save them.
If you selected HP-UX on the Managed Environment page, all selected menu items appear.
If you enabled automatic discovery or initiated Run discovery after the wizard finishes, discovery
runs when you exit the First Time Wizard. If you did not enable automatic discovery or the Run
discovery once after the wizard finishes, discovery does not take place until you select
Options→Discovery from the HP SIM menu, and enable a discovery task or select a task and click
Run Now. See Configuring automatic discovery for more information.
First Time Wizard related topics
Finishing the First Time Wizard
When you click Finish in the First Time Wizard, the Finish page appears with a message stating
Your settings are being applied, please do not close the window. For HP-UX
systems, TDEF files are updated, and the minor version of HP-UX tools is upgraded. If you selected
Run discovery once after wizard finishes on the Discovery page, you are notified that discovery is
running and where to go in the HP SIM to monitor the progress of discovery. Also included on this
page is information on where to go to see discovered systems that you are managing and where
to go to better manage these systems. To close the First Time Wizard, click Close.
After the First Time Wizard is finished, automatic discovery on the Ignite server is triggered if
Ignite-UX and Software Distributor (HP-UX) is selected and an IP address or host name is placed
in the Ignite and Software Distributor Server UI field. A check is made to verify if the system is
present and, if it is not, automatic discovery for that system is triggered.
SSH configuration is also completed on Ignite Server if Ignite-UX and Software Distributor (HP-UX)
and Configure secure shell (SSH) access are selected and the host name or IP address, SSH and
user name and password are given to ensure the Ignite Server is trusted. If not, SSH configuration
runs.
First Time Wizard related topics
First Time Wizard related topics
Related procedures
Managed Environment
Configuring System Automatic Discovery task sign in credentials
Configuring managed systems
Configuring the WMI Mapper Proxy
Configuring privilege elevation on HP-UX
Configuring e-mail settings
Configuring automatic discovery
Related topics
First Time Wizard
Summary
Finishing the First Time Wizard
Operating-system-specific collections, reports, and tools
First Time Wizard
47
Discovery in HP SIM
Configuring discovery general settings
Performing Initial setup
Initial setup process
1.
Set up managed systems
To set up managed systems, install the required management agents and configure HP SIM
software. See Setting up managed systems for more information.
2.
Configure storage systems
If you have storage systems on your network, you must install and configure their SMI-S
providers before HP SIM can discover them.
3.
Configure protocol settings
Configuring the protocol settings defines what systems are added to HP SIM using discovery
in the next step. See Protocol settings for more information.
If you ran the First Time Wizard, the protocol settings might already be configured.
IMPORTANT: If you have storage systems on your network, you must add the user name
and password for each SMI CIMOM to the Default WBEM settings section of the Global
Protocol Settings page. If you do not add this information, your storage systems are not
discovered.
4.
Configure discovery
Discovery is the process that HP SIM uses to find and identify the systems on your network
and populate the database with that information. A system must first be discovered to collect
data and track system health status. Automatic discovery searches the network for systems
running specific protocols. It runs automatically every 24 hours, but the process can be manually
executed or scheduled to execute at other times. See Configuring automatic discovery for
information about automatic discovery.
If you ran the First Time Wizard, discovery might be completed.
IMPORTANT: If you have storage systems on your network, you must add each SMI CIMOM
IP address to a discovery task. If an SMI CIMOM IP address is not included in a discovery
task, the associated storage system is not discovered.
5.
Add new users
You can add any user with a valid network login to HP SIM.
If you ran the First Time Wizard, new users might already be added.
6.
Configure e-mail settings
you can configure e-mail settings so that users receive e-mail notification of certain events.
See Configuring e-mail settings for information about e-mail settings.
7.
Set up automatic event handling
Automatic event handling enables you to define an action that HP SIM performs when an
event is received. You can set up automatic event handling to use the e-mail and paging
settings that you specified in the previous sections. See Creating an automatic event handling
task for more information.
Setting up managed systems
Setting up managed systems involves installing the required software and configuring the supported
protocols to communicate with the HP SIM software.
48
Initial setup
For steps to set up managed systems from the CMS see the following:
•
Setting up managed systems from a Linux CMS
•
Setting up managed systems from an HP-UX CMS
•
Setting up managed systems from a Windows CMS
Setting up managed systems related topics
Setting up remote Linux systems from a Linux CMS
Procedure 20 Example: Setting up remote Linux systems from a Linux CMS
1.
2.
3.
4.
5.
Sign in to the HP SIM on the Linux CMS with full CMS administrative privileges.
Run the First Time Wizard.
Run discovery. See Running a discovery task for more information.
Preconfigure the HP System Management Homepage and HP Version Control Repository
Manager components. For more information about preconfiguring the HP SMH component,
see HP System Management Homepage Installation and Configuration Guide and for HP
VCRM, see http://h18013.www1.hp.com/products/servers/management/agents/
documentation.html.
Run the Configure or Repair Agents feature. For more information, see Configuring the managed
system software.
Setting up managed systems related topics
Setting up remote HP-UX systems from an HP-UX CMS
Example: Setting up remote HP-UX systems from an HP-UX CMS
Procedure 21 Example: Setting up remote HP-UX systems from an HP-UX CMS
1.
2.
3.
4.
5.
Sign in to HP SIM on the HP-UX with full CMS administrative privileges.
Run the First Time Wizard if you have not already. See Running a discovery task for more
information.
Run discovery if you have not already.
Ensure the managed system software is installed.
Run the Configure or Repair Agents feature to configure the managed system. For more
information, see
Setting up managed systems related topics
Setting up Windows managed systems manually
Setting up managed systems related topics
Setting up managed systems related topics
Related procedures
Setting up managed systems from an HP-UX CMS
Setting up managed systems from a Linux CMS
Setting up managed systems from a Windows CMS
Related topics
Setting
Setting
Setting
Setting
up
up
up
up
managed systems
remote HP-UX systems from an HP-UX CMS
remote Linux systems from a Linux CMS
Windows managed systems manually
Setting up managed systems
49
Setting up systems using the HP Insight managed system setup wizard
Insight managed system setup wizard enables you to configure systems to be managed with HP
SIM and its plug-in applications. After you successfully complete this wizard, the selected managed
systems are set up with the necessary agents, licenses, and configuration steps for the management
features you specify.
You can re-run this wizard at any time to change the configuration or management features of
your systems. This wizard can also be used to diagnose configuration issues with your systems.
For HP SIM, you can configure:
•
Protocol preferences by selecting WBEM, SNMP, or both
•
SSH public authentication by selecting between User based authentication and Host based
authentication
•
SSH user name for public key authentication check and setup
Monitoring feature
The Monitoring feature enables HP SIM to discovery and identify systems with basic information
and monitor them through ping status. Basic information includes model system type, subtype,
serial number, UUID, and so on of the managed systems. This feature is supported on all servers,
management processors, switches, and Unknown or Unmanaged systems and can run without
installing any of the HP agents or providers. The Central Management Server (CMS) must be
preconfigured, including credentials, global protocol settings, WMI Mapper Proxy and so on. For
additional information on configuring these features quickly, see First Time Wizard.
Configuration
To configure global credentials, see Global credentials.
To configure system credentials, see System credentials.
To configure global protocol settings, see Protocol settings.
To configure WMI Mapper Proxy settings, see Adding a WMI Mapper Proxy.
The Monitoring feature checks for HP SIM discovery and identification errors, which appear on
the Analyze Systems page.
When you receive errors from the monitoring feature, check credentials, protocol settings, and
other Central Management Server (CMS) configuration, including firewall configuration on the
managed systems.
For more detailed information on errors received, run HP SIM identification and review the
identification task results.
Inventory feature
HP SIM inventory collects inventory data from managed systems. To successfully do so, HP SIM
depends on SNMP agents and WBEM providers. The Insight managed system setup wizard
Inventory feature is supported on HP servers with Linux, HP-UX, and Windows operating systems
and ESX and Citrix VM Hosts with Hypervisor operating systems.
The inventory feature is dependent on the monitoring feature of HP SIM with the same protocol.
Configuration
To configure discovery, see Discovery in HP SIM.
To edit system properties for a single system, see Editing system properties for a single system.
You can install WBEM/WMI providers and SNMP agents from the Choose Options page in Insight
managed system setup wizard. For all other servers, you must manually install providers agents.
50
Initial setup
To manually set up managed systems on HP-UX and Linux, see Setting up remote HP-UX systems
from an HP-UX CMS and Setting up remote Linux systems from a Linux CMS
WBEM
WBEM is one of the newest management protocols. This protocol leverages the industry-standard
CIM as defined by the DMTF. HP SIM can communicate to systems directly using the WBEM
protocol or to the Windows WMI systems using the WMI Mapper Proxy. HP SIM uses WBEM to
communicate with storage system SMI-S WBEM providers. HP has been leading this effort through
its association with the Distributed Management Task Force (DMTF). WBEM is an initiative supported
by HP, Microsoft, Intel, BMC, Cisco, and 120 other platform, operating system, and application
software suppliers.
When WBEM is enabled, the management console can obtain information from any system that
supports WBEM. For WBEM to work, you must provide the correct user name and password for
the given system. WBEM enables a larger set of server and storage manageability data to be
collected and displayed on the System Page and in reports. The presence of WBEM enables the
Properties pages and enables WBEM indications (events) to be displayed in event collections.
Without HTTPS enabled, HP SIM does not discover any web-based features on a system. Support
for non-HP systems has been expanded beginning with HP SIM 6.0.
NOTE:
HP SIM supports WBEM over HTTPS to ensure user supplied WBEM name and password
pairs are protected.
NOTE:
•
OpenWBEM is not supported.
WBEM
This industry initiative provides management of systems, networks, users, and applications
across multiple vendor environments. WBEM simplifies system management, providing better
access to software and hardware data that is readable by WBEM client applications.
For HP-UX, WBEM is included in the operating system install. For Linux Itanium Processor
Family (IPF), if WBEM is not installed, it must be manually installed. Go to the HP Software
Depot (http://www.software.hp.com/) to download. The WBEM download from the
openPegasus website does not include the hardware specific data for HP SIM to manage
Linux x86 systems.
NOTE:
WMI is the implementation of WBEM from Microsoft.
NOTE:
The WBEM providers cannot be installed on Linux or HP-UX systems.
NOTE: A CIMOM acts as the interface for communication between WBEM providers and
management applications such as HP SIM.
The CMS must have the correct credentials to authenticate to WBEM and WMI. There are
two ways to authenticate client certificates:
•
◦
Basic authentication to WBEM Services or WMI using user name and password.
◦
Using the CMS certificate for authentication is available only for HP-UX WBEM Services
2.05 or greater, which supports client certificate authentication. Use the Configure or
Repair Agents Use an Systems Insight Manager WBEM certificate (good for 10 years)
rather than username/password to manage the system option to deploy a WBEM
certificate to the managed system and is valid only for HP-UX systems.
WMI
An API in the Windows operating system that enables you to manage and control systems in
a network.
The WMI Mapper Proxy is a configuration setting for WMI. The WMI Mapper receives client
CIM/XML WBEM requests and converts the requests to WMI requests. The WMI results are
Setting up systems using the HP Insight managed system setup wizard
51
converted to CIM/XML format and returned to the CMS. The discovery and Identification task
uses the proxies in the WMI Mapper Proxy list to discover whether a system is a WMI-enabled
system. If the system is WMI-enabled, then the identification information for that system is
returned.
The WMI Mapper makes it possible to retrieve WMI instrumented data on a Windows machine
through WBEM requests. The Windows version of Systems Insight Manager installs this WMI
Mapper locally so that it can make WMI requests across the network to the systems without
the need to install the WMI Mapper on the managed Windows systems.
The WMI Mapper is included in a Typical installation of the Systems Insight Manager on a
Windows CMS (optional in a Custom installation) . For HP-UX and Linux-based systems, the
WMI Mapper is not available.
Remote Command Execution feature
The Remote Command Execution feature enables HP SIM tools to run remotely on managed systems
though SSH.
SSH is installed as a part of UNIX and most operating systems other than Windows. IF SSH is not
installed on a Windows system, Insight managed system setup wizard on a Windows Central
Management Server (CMS) supports installing Open SSH on a Windows managed system. If you
are running from a Linux or HP UX CMS, be sure that OpenSSH is installed manually on the system.
See Installing OpenSSH.
Configuration
Configuring SSH involves setting up Public key-based authentication between HP SIM CMS and
the managed system. This establishes a trust relationship between HP SIM CMS and the managed
system. This is a prerequisite for the HP SIM's Distributed Task Facility (DTF) to execute tasks, or
commands on managed systems. This feature is also used by other features in the Insight managed
system setup wizard for remote configurations on the managed system.
SSH key-based authentication copies the HP SIM CMS public key to the users SSH key directory
on the managed system. The HP SIM CMS public key is appended to the authenticated keys file
in the managed system. If host-based authentication is configured, then all valid users on the
managed system can execute tasks from HP SIM. If user-based authentication is configured, then
you must configure SSH keys for each user that needs to execute an HP SIM tool or task. The user
must be a valid SSH user on the managed system. This feature is supported on most managed
servers with non-embedded operating systems. It is also supported on iLOs.
If no SSH user name is entered and user-based authentication is selected, HP SIM verifies there is
a working SSH credential set for the system. SSH credential can be password-based, user-based
or host-based.
If a user name is entered with the user-based authentication, then password-based authentication
is included while verifying that a user can log in to the remote system. HP SIM can successfully
login into the remote system using SSH if either password or host-based/user-based is configured
correctly.
NOTE: Host-based in Windows is configured only for the user that configures SSH. To enable
other users to use the host-based key, you must add entries to the psswd file on a managed system.
You can use the sshuser utility. This utility is available in the managed system if you installed
OpenSSH through HP SIM. If not, this utility is available in the lbin directory of HP SIM CMS
Run sshuser -u <username> -d <domain_name> -f <location of passwd file>
on the managed system. For example, the following command permits SSH access for user joe in
the Windows domain MyDomain:
sshuser joe MyDomain f "C:\Program Files\OpenSSH\etc\passwd"
52
Initial setup
Single Sign On feature
SSO grants permission to an authenticated user browsing to HP SIM to browse to any of the
managed systems from within HP SIM without re-authenticating to the managed system. This enables
HP SIM users to browse to HP System Management Homepage (HP SMH), Management Processors,
Onboard Administrator, HP Version Control Agent, and so on. HP SIM is the initial point of
authentication, and browsing to another managed system must be from within HP SIM.
SSO sets the trust mode to \Trust by Certificate\ in the system and by copying the HP SIM system
certificate to the managed system's trusted certificate directory. Setting a trust relationship enables
the managed system to specify which HP SIM servers can issue commands to the system. Without
an established trust relationship, these commands fail. This is also a prerequisite if you want to
execute Replicate Agent Settings or Install Software and Firmware tasks on the managed systems.
To install HP SMH on a Windows managed system from Windows CMS, select the Inventory
feature in the Insight managed system setup wizard.
To install HP SMH on a Linux managed system from Windows or Linux CMS, select the Inventory
feature, and then select the SNMP protocol as the preferred protocol. HP SIM does not support
installing HP SMH on a HP-UX managed system.
For information on setting up managed systems from HP-UX, Linux, and Windows, see the following:
Setting up remote HP-UX systems from an HP-UX CMS, Setting up remote Linux systems from a
Linux CMS, and Setting up Windows managed systems manually.
This feature is supported on all HP Servers with HP SMH installed or on all iLOs, iLO2s, iLo3s, and
ProLiant OA's.
NOTE:
Checking trust status on HP iLO systems is not supported.
Events feature
The Events feature configures HP SIM to receive WBEM and SNMP events from managed sytems.
WBEM indications and SNMP trap events can be configured.
Configuration
To configure SNMP agents, subscribe to WBEM indications, and configure SNMP traps, see
Installing and configuring SNMP agent.
For more information on manually installing providers, see Installing and configuring protocols.
For more information on manually installing SNMP agents, see Installing the SNMP provider for
Windows.
Version Control feature
The Version Control feature enables you to configure the managed systems to use HP Version
Control Repository Manager. This feature is available for all ProLiant Windows servers. HP Version
Control Repository Manager must be installed on the Central Management Server (CMS).
This feature will let you install VCA on the managed systems and configure it to use the VCRM in
HP SIM. If you do not have a VCRM in HP SIM, then, to configure HP Version Control Agent, see
Installing and configuring Version Control.
To configure HP VCRM, see Specifying a Version Control Repository.
HP Insight managed system setup wizard - Protocol Preferences
SNMP
The IETF, the standards-rating body for the worldwide Internet, has defined a management protocol,
SNMP, which has accumulated a major share of the market and has the support of over 20,000
different products. SNMP has its roots in the Internet community. The complexity of large international
Setting up systems using the HP Insight managed system setup wizard
53
TCP/IP networks has provided the necessary incentive to develop a standard method of managing
devices on the network.
Within the SNMP framework, manageable network devices (routers, bridges, servers, and so on)
contain a software component called a management agent. The agent monitors the various
subsystems of the network element and stores this information in a MIB. The agents enable the
device to generate traps, which can be sent to a trap destination server that is running HP SIM.
Conceptually, the MIB is a database that can be written to and read by a management application
using the SNMP protocol.
To obtain SNMP:
For Windows systems, if SNMP is not installed during the operating system installation, you can
install it from the Windows CD using Add or Remove Windows Component feature.
To install the HP Insight SNMP agents for ProLiant systems running on Linux x86 operating system,
go to http://www.software.hp.com/ and select the ProLiant Support Pack 7.90.
NOTE:
The HP Insight SNMP agents cannot be installed on HP-UX systems.
To configure the read community string on the CMS, or to set the SNMPv3 Authentication and/or
Privacy (Encryption) parameters on the CMS, select Options→Protocol Settings→System Protocol
Settings from the HP SIM menu and click on the System credentials page to set the read community
string or to set the security name, security level, and SNMPv3 specific security parameters for a
particular server. To configure the read community string and SNMPv3 user details for multiple
systems, select Options→Protocol Settings→Global Protocol Settings and set the read community
string and/or set the SNMPv3 Authentication and/or Privacy (Encryption) parameters.
WBEM
WBEM is one of the newest management protocols. This protocol leverages the industry-standard
CIM as defined by the DMTF. HP SIM can communicate to systems directly using the WBEM
protocol or to the Windows WMI systems using the WMI Mapper Proxy. HP SIM uses WBEM to
communicate with storage system SMI-S WBEM providers. HP has been leading this effort through
its association with the Distributed Management Task Force (DMTF). WBEM is an initiative supported
by HP, Microsoft, Intel, BMC, Cisco, and 120 other platform, operating system, and application
software suppliers.
When WBEM is enabled, the management console can obtain information from any system that
supports WBEM. For WBEM to work, you must provide the correct user name and password for
the given system. WBEM enables a larger set of server and storage manageability data to be
collected and displayed on the System Page and in reports. The presence of WBEM enables the
Properties pages and enables WBEM indications (events) to be displayed in event collections.
Without HTTPS enabled, HP SIM does not discover any web-based features on a system. Support
for non-HP systems has been expanded beginning with HP SIM 6.0.
NOTE:
HP SIM supports WBEM over HTTPS to ensure user supplied WBEM name and password
pairs are protected.
NOTE:
•
OpenWBEM is not supported.
WBEM
This industry initiative provides management of systems, networks, users, and applications
across multiple vendor environments. WBEM simplifies system management, providing better
access to software and hardware data that is readable by WBEM client applications.
For HP-UX, WBEM is included in the operating system install. For Linux Itanium Processor
Family (IPF), if WBEM is not installed, it must be manually installed. Go to the HP Software
Depot (http://www.software.hp.com/) to download. The WBEM download from the
openPegasus website does not include the hardware specific data for Systems Insight Manager
to manage Linux x86 systems.
54
Initial setup
NOTE:
WMI is the implementation of WBEM from Microsoft.
NOTE:
The WBEM providers cannot be installed on Linux or HP-UX systems.
NOTE: A CIMOM acts as the interface for communication between WBEM providers and
management applications such as HP SIM.
The CMS must have the correct credentials to authenticate to WBEM and WMI. There are
two ways to authenticate client certificates:
•
◦
Basic authentication to WBEM Services or WMI using user name and password.
◦
Using the CMS certificate for authentication is available only for HP-UX WBEM Services
2.05 or greater, which supports client certificate authentication. Use the Configure or
Repair Agents Use an Systems Insight Manager WBEM certificate (good for 10 years)
rather than username/password to manage the system option to deploy a WBEM
certificate to the managed system and is valid only for HP-UX systems.
WMI
An API in the Windows operating system that enables you to manage and control systems in
a network.
The WMI Mapper Proxy is a configuration setting for WMI. The WMI Mapper receives client
CIM/XML WBEM requests and converts the requests to WMI requests. The WMI results are
converted to CIM/XML format and returned to the CMS. The discovery and Identification task
uses the proxies in the WMI Mapper Proxy list to discover whether a system is a WMI-enabled
system. If the system is WMI-enabled, then the identification information for that system is
returned.
The WMI Mapper makes it possible to retrieve WMI instrumented data on a Windows machine
through WBEM requests. The Windows version of Systems Insight Manager installs this WMI
Mapper locally so that it can make WMI requests across the network to the systems without
the need to install the WMI Mapper on the managed Windows systems.
The WMI Mapper is included in a Typical installation of the Systems Insight Manager on a
Windows CMS (optional in a Custom installation) . For HP-UX and Linux-based systems, the
WMI Mapper is not available.
Editing preferences
The option selected is used for all systems. To enter information for groups of systems, select the
systems, and then click Edit Individually.
Procedure 22 Individually editing protocol preferences
1.
2.
3.
4.
Select the way systems are displayed for editing by selecting one of the following from the
Show systems by dropdown list:
•
Operating System
•
System Name
•
System Type (Hardware-centric)
•
System Type (VM-centric)
•
Model
Select the systems to edit and select your protocol preferences.
To edit multiple systems with the same protocol preferences, select the systems, and then click
Edit Multiple Systems. Enter your protocol preferences.
To save changes, click OK.
Setting up systems using the HP Insight managed system setup wizard
55
HP Insight managed system setup wizard - SSH authentication
The option selected is used for all systems. To enter information for groups of systems, select the
systems, and then click Edit Individually.
Host based authentication. All users from this instance of Systems Insight Manager are authenticated
on the managed system.
User based authentication. Each user must be authenticated on the managed system.
Procedure 23 Individually editing SSH public authentication
1.
2.
Select the systems to edit and select your SSH authentication preferences. Select either
Userbased or Hostbased. For more information, see HP Insight managed system setup wizard
- Protocol Preferences.
To edit multiple systems with the same SSH authentication preferences, select the systems, and
then click Edit Multiple Systems. Select the SSH authentication.
HP Insight managed system setup wizard - SSH user name for public key
The option selected is used for all systems. To enter information for groups of systems, select the
systems, and then click Edit Individually.
Procedure 24 Individually editing SSH user name for public key authentication
1.
2.
3.
4.
Select the way systems are displayed for editing by selecting one of the following from the
Show systems by dropdown list:
•
Operating System
•
System Name
•
System Type (Hardware-centric)
•
System Type (VM-centric)
•
Model
Select the systems to edit and enter user name information. For more information, see HP
Insight managed system setup wizard - SSH user name for public key.
To edit multiple systems with the same user name information, select the systems, and then
click Edit Multiple Systems. Enter the user name information.
To save changes, click OK.
HP Insight managed system setup wizard - HP Integrated Lights-Out 2 Advanced
Description
HP iLO 2 provides an extension to the core functionality of the standard iLO management tools.
iLO 2 includes a remote graphical console for your system, power consumption management, and
other features specific to either ProLiant or Integrity systems.
Configuration information
You can configure all features of an iLO for iLO 2 except for scanning for and applying a license
if none are found on the iLO.
For more detailed information about iLO 2, you can log into the iLO and access the online help
available there. To log into the system from HP Systems Insight Manager, go to the System page
for the iLO and click the Integrated Lights-Out 2 (iLO 2) link. The iLO Web Administration tool
appears.
56
Initial setup
Advanced setup
The following are advanced setup procedures for HP SIM:
•
Configuring browser timeout options
•
Changing the HP SIM default SSL port
•
Managing server certificates
•
Replicating trusted certificates
•
Configuring the presentation of SNMP traps in HP SIM
Security related information
Configuring browser timeout options
HP SIM enables you to configure the browser timeout settings to one of the following. These settings
affect the browser session while signed in to the HP SIM GUI.
Monitor
When the timeout option is configured to monitor, the HP SIM session remains alive and is
continually refreshed unless you close the browser or navigate to another site. If you close the
browser, the session is immediately closed. If you navigate to another site, HP SIM signs you out
after 20 minutes. This option is the default and appears in the globalsettings.props file as
EnableSessionKeepAlive=true.
Active
When the timeout option is configured to remain active, the HP SIM session remains alive as long
as you are actively working in HP SIM. However, HP SIM ends your session and signs you out
after 20 minutes of inactivity.
You can change the timeout settings to monitor or active by editing the globalsettings.props
file.
Procedure 25 Configuring timeout setting to active
1.
2.
3.
Open the globalsettings.props file.
•
On a Windows operating system, the globalsettings.props file is located in the
C:\Program Files\HP\Systems Insight Manager\config folder.
•
On an HP-UX or Linux operating system, the globalsettings.props file is located
in the /etc/opt/mx/config directory.
Change EnableSessionKeepAlive=true to EnableSessionKeepAlive=false.
Select File→Save.
The updates are saved.
4.
Close the globalsettings.props file.
Procedure 26 Changing the default timeout
1.
From the HP SIM directory, navigate to:
Windows:
C:\Program Files\HP\Systems Insight Manager\jboss\server\hpsim\
deploy\jboss-web.deployer\conf\web.xml
Linux and HP-UX:
/opt/mx/jboss/server/hpsim/deploy/jboss-web.deployer/conf/web.xml
2.
Edit the <session-timeout> value from the default of 20 minutes to the number of minutes you
want.
Advanced setup
57
3.
Save the globalsettings.props and the web.xml files.
The updates are saved.
4.
Close the web.xml file.
Security related information
Changing the HP SIM default SSL port
If the HP SIM Secure Sockets Layer (SSL) port conflicts with an application, you can change the
default port number. For a list of ports in use, see the HP Systems Insight Manager User Guide, at
http://www.hp.com/go/insightmanagement/sim/docs.
1. In the server.xml file (located in the %programfiles%\HP\Systems Insight
Manager\jboss\server\hpsim\deploy\jboss-web.deployer directory), change
the two occurrences of 50000 to the desired port.
maxSpareThreads=15 enableLookups=false redirectPort=50000
acceptCount=10 debug=0 connectionTimeout=60 000 />
2.
For the first port entry, enter the following and replace 50000 with the port of your choice:
<Connector port=280 scheme=http protocol=HTTP/1.1 maxThreads=50
minSpareThreads=5 maxSpareThreads=15 enableLookups=false
acceptCount=10 debug=0 redirectPort=50000 connectionTimeout=60000
/>
3.
For the second port entry, enter the following and replace 50000 with the port of your choice:
<Connector port=50000 scheme=https secure=true protocol=HTTP/1.1
SSLEnabled=true maxThreads=200 minSpareThreads=10 maxSpareThreads=25
enableLookups=false acceptCount=10 debug=5 clientAuth=false
URIEncoding=utf-8 useBodyEncodingForURI=true compression=on
compressableMimeType=text/html,text/xml,text/plain,text/javascript,text/css
keystoreFile=C:\Program Files\HP\Systems Insight
Manager\config\certstor\hp.keystore keystorePass=HaWDwrKZTrxUYOSBr1RW
/>
4.
For the third port entry, enter the following text and replace 50000 with the port of your choice:
Connector port=50000 scheme=https secure=true protocol=HTTP/1.1
SSLEnabled=true maxThreads=200 minSpareThreads=10 maxSpareThreads=25
enableLookups=false acceptCount=10 debug=5 clientAuth=false
URIEncoding=utf-8 useBodyEncodingForURI=true compression=on
keystoreFile=C:\Program Files\HP\Systems Insight
Manager\config\certst or\hp.keystore
keystorePass=pBHQs0Mty09f4kO6NVJz sslProtocol=TLS/>.
Security related information
Managing server certificates
The Server Certificate page enables you to view and manage the SSL server certificate of the CMS.
HP SIM supports two types of certificates; self-signed and CA-signed. While a self-signed certificate
is created by default during installation, enabling you to browse to HP SIM, both the self-signed
and CA-signed certificates can be created after installation. The CA-signed certificate requires an
internal certificate server or an external CA to sign the certificate.
58
Initial setup
HP SIM provides the following security certificate options:
•
Export server certificate
Select Options→Security→HP Systems Insight Manager Server Certificate, and then click
Export.
•
Edit server certificate
Select Options→Security→HP Systems Insight Manager Server Certificates, and then click Edit.
•
Create new server certificate
Select Options→Security→HP Systems Insight Manager Server Certificates, and then click
New.
•
Import server certificate
Select Options→Security→HP Systems Insight Manager Server Certificates, and then click
Import.
Security related information
Replicating trusted certificates
System administrators that have the HP SIM Require or First Time Accept features enabled can
replicate the trusted certificates list to other HP SIM systems. If you do not use the Require or First
Time Accept features of HP SIM as a two-way trust solution, this procedure is not necessary.
Two options are available to migrate the trusted certificates from a source CMS to a target CMS.
The first option can be used when the source CMS has many trusted certificates and the second
option can be used when a source CMS has fewer of trusted certificates.
WARNING! When migrating certificates, you lose the existing SSL Server Key and certificate on
the target CMS and must reestablish the trust relationship with any agents configured to trust the
target CMS. See Step 13.
Procedure 27 Migrate a trusted certificate from a source to a target CMS with many trusted
certificates
1.
2.
3.
4.
Log in with administrative rights HP SIM on the source CMS system.
Go to C\Program Files\HP\Systems Insight Manager\config\certstor.
Copy the files named hp.keystore and keyfile.3.
Log in with administrative privileges to the target CMS system.
Advanced setup
59
5.
6.
7.
8.
Go to the <HPSIM Install folder>\Systems Insight Manager\config\certstor
directory.
Replace the hp.keystore and keyfile.3 files with the files copied in step 3.
On the target CMS system, select Start→Settings→Control Panel→Administrative
Tools→Services.
Restart the HP SIM service.
NOTE: You might see a browser warning indicating that the name in the certificate does
not match the name of the site. This result is expected because you are temporarily using the
certificate from the source CMS, but you can view the certificate displayed by the browser to
ensure its authenticity before signing in.
9.
10.
11.
12.
13.
Sign in with administrative rights to HP SIM on the target CMS. Select Options→Security→HP
Systems Insight Manager Server Certificate.
To create a new server certificate, click New.
On the target CMS system, select Start→Settings→Control Panel→Administrative
Tools→Services.
Restart the HP SIM service.
Install the new server certificate on the required managed systems using the Replicate Agent
Settings feature. For more information, see “Using the Replicate Agent Settings feature” (page
60).
Procedure 28 Migrating certificates when the source CMS has a lower number of trusted certificates
1.
2.
3.
4.
5.
6.
7.
8.
9.
10.
11.
12.
Log in to the source CMS system with administrative privileges.
Select Options→Security→Credentials→Trusted Systems.
Select a certificate, and then click Export.
Save the certificate locally.
Repeat steps 2 and 3 for all certificates listed on the Trusted System Certificates page.
Copy all exported certificates to the target CMS system.
Sign in with administrative rights to HP SIM on the target CMS.
Select Options→Security→Credentials→Trusted Systems
Click Import.
Click Browse, and then select a certificate.
Click OK.
Repeat steps 9 through 11 for all certificates.
Using the Replicate Agent Settings feature
NOTE:
This section assumes agents are already configured to trust the source CMS.
NOTE: This process configures the agents to trust only the new target CMS. If trust for the original
source CMS is still necessary, perform steps 5, 6, and 13 (or 16) using the source CMS.
Procedure 29 Configuring agents to trust only the new target CMS
1.
2.
3.
4.
5.
6.
7.
8.
60
Log in to the HP SMH on the target CMS.
Select Settings→Security→Trust Mode.
Select Trust by Certificate, and then click Save Configuration.
Select Settings→Security→Trusted Management Servers.
Enter the IP address of the target CMS in the field adjacent to Add Certificate From Server.
Click Add Certificate From Server.
Sign in with administrative rights to HP SIM on the source CMS.
Select Configure→Replicate Agent Settings.
Initial setup
9.
From the Select Target Systems page, select all managed systems that are configured to trust
the source CMS.
10. Click Apply Selections, and then click Next.
11. Select the target CMS as source and click Next.
NOTE:
If the source system does not have HP SIM installed, proceed to step 15.
12. In the source configuration settings page, click HP System Management
Homepage→Settings→Configuration Options Properties, and then select Trust Mode.
13. Click HP System Management Homepage→Settings→Trusted Certificate Properties, and then
select Trusted Certificate for the target CMS.
14. To select the trust mode, select HP System Management Homepage→Settings→Configuration
Options Properties.
15. To select the trusted certificates, select HP System Management Homepage→Settings→Trusted
Certificate Properties for the target CMS.
16. Click Run Now. The CMS certificates are replicated on the selected managed systems.
Security related information
Configuring the presentation of SNMP traps in HP SIM
You can map a severity from a varbind to the event severity displayed in the event view. The
mechanism uses two keywords annotated as comments in the trap definition VARBINDSEVERITY
and SEVERITYMAP. The following is an example of a trap definition:
sanEventTrap TRAP-TYPE
ENTERPRISE sanEvent
VARIABLES { sanEventEventCofde, sanEventIPAddress,
sanEventSeverity, sanEventCategory,
sanEventGroup, sanEventSourceType,
sanEventSourceSubtype, sanEventURL,
sanEventDesc }
--#SEVERITY INFORMATIONAL
--#TYPE "Rack power supply inserted"
--#VARBINDSEVERITY 3
--#SEVERITYMAP "Unknown = INFORMATIONAL,
Other = INFORMATIONAL,
Information = INFORMATIONAL,
Warning = INFORMATIONAL,
Minor = MINOR, Major = MAJOR,
Critical = CRITICAL,
Fatal = CRITICAL"
--#ENABLE true
--#CATEGORY "San Event Events"
DESCRIPTION
"This trap signals (using SNMP) an event
has been received"
The VARBINDSEVERITY points to a varbind, which contains a severity. A varbind starts at the
count of 1 and in the example above, sanEventSeverity is the third varbind pointed to by
--#VARBINDSEVERITY 3. The severity for the varbind must be defined as an enumeration.
SEVERITYMAP is a mapping of agent severity to the HP SIM-supported severity. HP SIM supports
Critical, Major, Minor, Warning, and Informational severities. Therefore, all mappings must resolve
to one of these severities. In the example above, you can see a mapping of Fatal to CRITICAL
("Fatal = CRITICAL"). When you receive in the varbind Fatal, it is translated to the HP SIM severity
of Critical. The varbind value and the severity might vary by the agent as conditions change so
when a trap is received in HP SIM, the severity displayed is set by the agent when a trap was sent.
Related information
Advanced setup
61
5 Screens and product layout
Table 4 Screen and menus
Name
Description
Home page
Graphical user interface features
Navigating the System and Event Collections panel
Selecting a collection displays a view of its contents.
Users and user groups
Enables you to configure authorizations for specific users
or user groups.
Navigating the system table view page
The default view for an attribute-based system collection
and displays a list of systems that meet common criteria.
Navigating the cluster table view page
Clicking the name of the cluster in the Cluster Name column
or cluster status icon in the CS column displays the System
Page for that cluster.
Navigating the event table view page
The view for an event collection and lists of events that
meet common criteria.
Navigating the tree view
Provides an automatically populated representation of the
actual physical hierarchy of blade components.
Navigating the icon view
Lists the system name of all discovered systems, as well as
the system health status for each system.
Navigating the picture view page
Contains a picture view of the discovered systems in the
rack or enclosure if available.
Viewing racks
Displays the following tabs:
• System tab for blade servers
• Navigating the event table view page
62
Viewing enclosures
Contains a diagram of the discovered systems in the
enclosure if available.
Viewing p-Class enclosures
Forms a rack if a set of enclosures are networked in the
hardware level and hosts the ProLiant BL p-Class server
types.
Viewing e-Class enclosures
Includes the Consolidated Client Infrastructure blade PC
Enclosures which host 20 PC blades including
bc1000/bc1500 and bc2000/bc2500 PC blade types,
and the e-Class BL10e server blades.
Viewing c-Class enclosures
Consists of the HP BladeSystem c7000 and c3000
Enclosures, HP ProLiant BL c-Class server blades, network
interconnect components, ProLiant Onboard Administrator,
and management tools that enable adaptive computing,
optimized for rapid deployment.
Customizing system and cluster collections
Contains a Systems collection and the Systems collection
contains additional system, cluster, and System Functions
collections.
Customizing event collections
Contains an Events collection. This collection contains
collections of different types of events.
Managing event handling tasks
Includes a table that shows all automatic event handling
tasks and how the task was set up.
System Type Manager page
Lists rules currently defined in HP SIM.
WMI Mapper Proxy
Receives client CIM/XML WBEM requests and converts the
requests to WMI requests.
Screens and product layout
Table 4 Screen and menus (continued)
Name
System page
Description
Enables viewing information related to a specific system.
• System tab for servers
• System tab for blade servers
• System tab for management processors
• System tab for clusters
• System tab for a complex
• System tab for partitions
• System tab for storage host
• System tab for a storage switch
• System tab for a storage array
• System tab for a tape library
• Tools & Links tab
• Essentials tab
• Performance tab for blades
• Port mapping tab for blades
• Managing contacts
• Managing site information
Managing SSH keys
Enables viewing and managing public SSH keys, stored
in the known_hosts file, from the CMS.
Cluster monitor
Displays the following tabs:
• Cluster tab
• Nodes tab
• Network tab
• Resources tab
Managing Communications
Troubleshoots communication problems between the CMS
and targeted systems.
Managing with tasks
Managing tasks:
• Viewing task instance results
• Navigating the All Scheduled Tasks page
License Manager
Displays licenses by product.
Reporting
Enables viewing diverse configurations such as:
• Creating user defined reports
• Viewing predefined reports
• Viewing Snapshot comparisons
NOTE: All user defined, predefined, and snapshot
comparison reports can be run in HTML, CSV, and XML
format.
• Viewing Enhanced Reports - allows you to execute
graphical reports for detailed analysis.
NOTE: All Enhanced reports can be run in HTML, PDF,
CSV, and XML format.
• Searching multiple CMSs and CMS systems
Remote Support Configuration and Services
Facilitates the collection of enterprise events and
configuration data from monitored systems and establishes
63
Table 4 Screen and menus (continued)
Name
Description
remote connectivity back to HP for reactive support in a
timeframe determined by warranty or contract level.
Home page
Graphical user interface features
The GUI includes the following six regions:
1. Banner area
Provides a link to the Home page, a link to Sign Out of Systems Insight Manager, and displays
the user that is currently signed in. Click the minimize icon in the top right corner to minimize
the banner. To maximize the banner, click the maximize icon.
2.
System Status panel
Provides uncleared event status, system health status information, and an alarm to notify you
about certain events or statuses. You can customize the System Status panel for your
environment. If you do not need to view this panel at all times, you can collapse it by clicking
the minus sign ( ) in the top right corner of the panel. To expand the panel, click the plus sign
( ). If the System Status panel is collapsed and an alarm is received, the panel expands to
show the alarm. You can enlarge the panel clicking the Open in new window icon ( ) to
display a separate large window that you can resize and view from across a room without
sitting at the HP SIM terminal. For more information, see Enlarging the System Status panel.
3.
Search panel
Enables you to search for matches by system name and common system attributes. You can
also perform an advanced search for matches based on selected criteria. To speed the search
process, as you enter system information in the search box, a dropdown list appears listing
systems that begin with the text you are entering. You can select from the dropdown list or
continue to enter the information. For information about search criteris, see the HP Systems
Insight Manager User Guide, at http://www.hp.com/go/insightmanagement/sim/docs. If
you do not need to view this panel at all times, you can collapse it by clicking the minus sign
( ) in the top right corner of the panel. To expand the panel, click the plus sign ( ).
64
Screens and product layout
4.
System and Event Collections panel
Enables you to view all known systems and events in a specific management environment. A
collection can be private, visible only to its creator, or shared, visible to all users. HP SIM
ships with default shared collections only. For information about customizing and reating new
collections, see the HP Systems Insight Manager User Guide, at http://www.hp.com/go/
insightmanagement/sim/docs.
5.
HP SIM menus
Provides access to tools, logs, software options, and online help. The Options menu is primarily
for users who administer the HP SIM software. If you lack authorization to use these tools, you
might not be able to access certain menus.
6.
HP SIM workspace
Displays the results of your latest request. It can contain a collection, tool, or report. Some
tools launch a separate browser window or X Window terminal instead of displaying in the
workspace. This area contains the Home page when you sign in to HP SIM. By default, the
introductory page is the Home page. The introductory page provides information and tips
about HP SIM and links to frequently used features. You can customize HP SIM to display a
different page as the Home page. For information about selecting a different introductory
page, see Customizing the Home page.
NOTE: To maximize the workspace, click the Maximize link next to the Help icon (
restore the workspace to its original size, click Restore Size.
). To
The default sections on the introductory page include the following:
•
Do this now to finish the installation:
Appears only if the following conditions are met:
•
◦
You have administrative rights.
◦
You have not disabled this section from the Home Page Settings page.
Monitor
Provides links to common monitoring tasks, including locating and tracking systems and events.
•
Manage
Provides links to frequently used tools and features available from the menus above the
workspace. These links provide access to inventory reports, software and firmware deployment,
discovery, event handling, integrating custom tools, and authorizations.
•
Did You Know You Can...?
Provides useful tips and shortcuts, including where you can learn more about HP products,
service offerings, and software.
This section appears if you have not disabled it from the Home Page Settings page.
Navigating the System and Event Collections panel
Selecting a collection displays a view of its contents. From the System and Event Collections panel,
you can launch several types of collection view pages. Select one of the pages in the following
list to view more information about the types of views available:
In the System and Event Collections panel, the Private and Shared collections are created by default.
Any HP SIM user can view shared collections. However, only users with administrative rights can
edit or delete these collections and their contents. Private collections can only be viewed, edited,
or deleted by the user that created the collection. Collections can be placed in Private or Shared
collections. To place a collection in the Shared collection, you must have administrative rights.
Navigating the System and Event Collections panel
65
Private collections can be placed into a shared collection, but shared collections cannot be placed
into a private collection.
If a collection is placed in both Shared and Private, any user that has administrative rights can
modify the collection stored in the Shared collection. When the collection is modified in one place,
changes are reflected in the other collection. If the user who created the collection has his or her
user rights reduced from administrative rights to operator rights, he or she can no longer modify
the collection that is located in the Shared collection, and can only edit the collection located in
the Private collection, which is not reflected in the collection located in the Shared collection.
Collections and members of collections can be set to hidden in the user interface. You might want
to do this to remove the clutter of unused collections from the System and Event Collections panel.
See Setting properties for system and cluster collections and Setting event properties for more
information.
Tree controls and customization
To navigate the tree view in the System and Event Collections panel use the following controls:
Expands all branches of the tree
Collapses all branches of the tree to first-level branches
Expands a branch of the tree
Collapses a branch of the tree
The Customize link in the System and Event Collections panel enables you to customize the System
and Event Collections panel tree to your own preferences. Any user can customize his or her
Systems, Events, and Private collections, but only a user with administrative rights can customize
the shared Systems and Events collections. To display the Customize Collections section, click
Customize.
66
Screens and product layout
Overviews
The System and Event Collections panel includes:
•
All Systems
Displays the All Systems page. See Navigating the system table view page for information
about the system table view page.
•
All Events
Displays the All Events page. See Navigating the event table view page for information about
the event table view page.
Systems
A system collection logically groups systems into a group based on information in the HP SIM
database. After a collection is defined, you can display the results in the workspace or associate
it with a management task.
In addition to using the collections provided by HP SIM, you can create, edit, or delete your own
collections. Collections must follow specific naming conventions. See the HP Systems Insight Manager
User Guide, at http://www.hp.com/go/insightmanagement/sim/docs, for more information about
naming collections.
Collections can be used to organize large numbers of systems into smaller, more meaningful groups.
For example, your organization might have five system administrators who are responsible for
100 different systems in 6 different buildings. You can create a collection for each administrator
that includes only his or her systems, or you can create a collection for each building that includes
only the systems located in a particular building.
Events
An event collection logically groups multiple event collections into a single collection based on
information in the HP SIM database. After a collection is defined, you can display the results in
the workspace or associate it with a management task.
Related information
Users and user groups
NOTE: Users that have been added to the Central Management Server (CMS) cannot view or
manage systems until authorizations have been configured for them.
NOTE: Command line tools provided by HP-UX and Linux (such as ls and df) are run as root
by default. For security reasons, you might want them to run as a specific user to avoid inadvertently
allowing unauthorized access to a user.
Users and user groups
67
HP SIM enables you to configure authorizations for specific users or user groups. Authorizations
give the user access to view and manage systems. Each authorization specifies a user or user
group, a toolbox, and a system or system group. The specific set of tools that can be run on a
system that is specified in the assigned toolbox.
It is important that you plan which systems each user will manage and which specific set of tools
each user is authorized to execute on managed systems. A user with no toolbox authorizations on
a particular system cannot view or manage that system.
Authorizations are cumulative. If a user is authorized for Toolbox1 and Toolbox2 on the same
system, the user is authorized for all tools in both Toolbox1 and Toolbox2 on that system. Similarly,
a user authorized for the All Tools toolbox on a system requires no other toolbox authorizations
on that system because the All Tools toolbox always includes all tools.
See the following guidelines for setting up user names and authorizations in the following sections:
•
Configuring automatic discovery
•
Creating new users
•
Creating new user groups
•
Creating new toolboxes
•
Creating new authorizations
Users authorization templates
The Users and Authorizations tabs offer the following options:
•
Add, edit, and delete users and user groups, and view and print user reports. Select
Options→Security→Users and Authorizations→Users.
•
Add, edit, and delete toolboxes, and view and print toolbox reports. Select
Options→Security→Users and Authorizations→Toolboxes.
•
Add, update, and delete authorizations, and view and print authorization reports. Select
Options→Security→Users and Authorizations→Authorizations.
Users and authorizations related information
68
Screens and product layout
Users tab
Administering users involves adding, editing, deleting, and reporting. After you have added a
user or user group, you can assign predefined authorizations from the Authorizations tab.
Users and user groups must exist in the operating system. For Microsof Windows ®, this includes
Active Directory. When a user group is configured in HP SIM, any user that is a member of the
user group in the operating system can sign-in to HP SIM without having to be configured as a
user in HP SIM. The user can subsequently create tasks and run tools based on the user group's
authorizations and configuration rights as configured in HP SIM.
The Users tab displays a table with the following information:
•
User/User Group
This column includes all users and user groups. A user group appears in bold type, while
group-based user accounts (members of a configured user group) appear in italics.
•
Configuration CMS Security
This column indicates if the user has been given the right to configure CMS security. This
option is set when you select or clear the User can configure CMS security access such as
creating, modifying or removing other users checkbox when creating or editing users. The
column displays either Yes or No.
•
Pager Configured
This column indicates if the user has a pager configured (Yes or No.) and is blank for user
groups.
•
IP Sign-In Restrictions
This column indicates if there are any IP restrictions applied to the user or user group.
•
Full Name
This column displays the full name of the user or group if this information was entered during
the creation of the user or user group.
The Users tab provides the following options:
•
Creating new users.
Select Options→Security→Users and Authorizations→Users, and then click New. The New
User section appears.
•
Creating new user groups.
Select Options→Security→Users and Authorizations→Users, and then click New Group. The
New User Group section appears.
Users tab
69
•
Editing existing users or user groups.
Select Options→Security→Users and Authorizations→Users, and then select a user or user
group. Click Edit. The Edit User or Edit User Group section appears. You can edit group-based
(in italics) users to convert them to individually configured users.
•
Deleting users or user groups.
Select Options→Security→Users and Authorizations→Users, and then select users or user
groups. Click Delete. A confirmation box appears. to delete the users or user groups, click
OK, or to cancel the deletion, click Cancel.
•
Viewing and printing user reports.
Select Options→Security→Users and Authorizations→Users, and then click Report. The Users
Report window appears. To print the report, select File→Print.
NOTE:
To sort the information in ascending or descending order, click the appropriate
column heading. The column heading that includes the arrow is the column by which the list
is sorted. If the arrow is pointing up, the list is sorted in ascending order. If the arrow is pointing
down, the list is sorted in descending order.
Toolboxes tab
The Toolboxes section enables you to configure groups of tools. The following toolboxes are created
during the installation process::
•
The All Tools toolbox contains all tools in the CMS.
•
The Monitor Tools toolbox contains tools that display the state of the managed systems but not
tools that change the state of the managed systems. For example, the Monitor Tools toolbox
permits viewing installed software but does not permit installing software.
•
The Full Rights toolbox contains all tools in the CMS.
•
The Limited Rights toolbox contains only the create and edit both reports and tools.
The Toolboxes tab provides the following options:
•
Creating new toolboxes.
Select Options→Security→Users and Authorizations→Toolboxes, and then click New. The
New Toolbox section appears.
•
Editing existing toolbox.
Select a toolbox to edit, select Options→Security→Users and Authorizations→Toolboxes, and
then, click Edit. The Edit Toolbox section appears.
•
Deleting toolboxes.
Select toolboxes to delete, and then select Options→Security→Users and
Authorizations→Toolboxes. A confirmation box appears. To delete the toolboxes, click OK,
or to cancel the deletion, click Cancel.
•
Viewing and printing toolbox reports.
Select Options→Security→Users and Authorizations→Toolboxes, and then click Report. The
Toolboxes Report appears. To print the report, select File→Print.
NOTE: To sort information in ascending or descending order, click the appropriate column
heading. The column heading that includes the arrow is the column by which the list is sorted.
If the arrow is pointing up, the list is sorted in ascending order. If the arrow is pointing down,
the list is sorted in descending order.
70
Screens and product layout
Authorizations tab
Authorizations give users access to view and manage systems. An authorization is composed of
users, toolboxes, and discovered systems. When you first access the Authorizations tab, a table
appears listing all authorizations and includes the following information:
•
User/User Group
This column includes all valid users and user groups. A user group appears in bold type.
Group-based users are not displayed in this table. However, they are listed in the authorizations
for users table and appear in italics.
•
Toolbox
This column displays the toolboxes assigned to the user or user group for each authorization.
•
System
This column displays the systems on which the user or user group has authorizations. A system
group appears in bold type.
•
Auto
This column displays Auto if the authorization is set to automatically update when the collections
that the authorization is based upon are updated.
A system group is a group of systems based on a system collection that is used for authorizations.
Authorizations that use system groups are updated automatically when a change is made to the
system collection that the system group is based upon. For authorizations to be updated
automatically, the option, Do not track changes. If this collection changes, the authorization will
not change must not be selected.
You can view all authorizations, or you can view filtered authorizations for users, user groups,
toolboxes, system groups, and individual systems. Select the option from the Authorizations for
box, and then select the name from the Select name box.
The Authorizations tab provides the following options:
•
Creating new authorizations
Select Options→Security→Users and Authorizations→Authorizations, and then click New.
The New Authorizations section appears. This option is not available for group-based users.
Instead, create authorizations for the user group of the group-based user.
•
Updating authorizations
Select Options→Security→Users and Authorizations→Authorizations, select an authorization
using a system group based on a collection, and then click Update. The Update Authorizations
section appears.
Authorizations tab
71
NOTE:
To sort the information in ascending or descending order, click the appropriate
column heading. The column heading that includes the arrow is the column by which the list
is sorted. If the arrow is pointing up, the list is sorted in ascending order. If the arrow is pointing
down, the list is sorted in descending order.
•
Deleting authorizations
Select Options→Security→Users and Authorizations→Authorizations, select authorizations to
delete, and then click Delete. A dialog box appears. To delete the authorizations, click OK,
or to cancel the deletion, click Cancel. This option is not available for group-based users.
Instead, delete authorizations for the user groups of the group-based user.
•
Viewing and printing authorization reports
Select Options→Security→Users and Authorizations→Authorizations, and then click Report.
The Authorizations Report window appears. To print the report, select File→Print.
Navigating the system table view page
The system table view page is the default view for an attribute-based system collection and displays
a list of systems that meet common criteria.
From this page, you can view systems in a list, table, or tree, and save system collections, delete
systems, and print the system collection.
If a collection includes more than 200 members, the first 200 members appear on the first page.
Systems selected on one page remain selected as you navigate to a different page in the collection.
When a column is selected as the column to sort by, the entire collection is sorted, not just the items
on the currently viewed page.
72
Screens and product layout
Tabs
The system table view page contains the following tabs:
•
System(s)
Lists all systems in the collection.
•
Events
Displays the events for all systems included under the System(s) tab. From this tab, you can
apply additional filters to modify the event table display.
When switching between the System(s) tab and the Events tab, the Events tab "remembers" the
selected events and event filter (if viewing a system collection). The System(s) tab remembers the
selected systems, view type (table, tree, or icon), and the selected system filter (if viewing an event
collection). However, the selections on each page are independent of each other.
Quick Launch
The Quick Launch hyperlink links to a short list of frequently used tools. Place your cursor over the
link to expand the menu and view the tools available for selected systems. Selecting a tool from
this list bypasses the target verification page of the Task Wizard. You cannot schedule tools
launched from this menu. Customize this menu by clicking the Customize link in the Quick Launch
menu.
View as
The View as dropdown list is used to select either table, which displays the system results in a table
form, icons, which displays only the HS status icon and the System Name for each system, and
tree, which displays the HS status icon and the System Name for each system in a tree format.
This icon takes you to Onboard Administrator when clicked:
•
An Enclosure in a rack managed by a management processor
•
A complex managed by a management processor
•
A cell blade in an enclosure
For more detailed information about the tree view, see Navigating the tree view. For more
information about the icon view, see Navigating the icon view.
Table information
To access a systems view or picture view of a system, click a link in the System Name column.
Typically, the System Page appears when a system is clicked. However, racks link to the rack
picture view page, and enclosures link to the enclosure picture view page. These links are both
types of container views.
The summary shows how many systems in the view have a status of: Critical, Major, Minor, Normal,
Disabled, and Unknown. For more information, see the HP Systems Insight Manager User Guide,
at http://www.hp.com/go/insightmanagement/sim/docs.
System view columns
Sort columns by clicking the column header to switch between ascending and descending order.
The column that the table is sorted by includes an up or down arrow in the column heading. Place
your cursor over a column name to display a brief description of the column. The columns are not
available when you select the icons, picture, or tree views. The following columns are available
on the system view page:
Navigating the system table view page
73
For more information about customizing columns, see Customizing the system table view page.
•
Selection
Select the checkbox in this column to select a system. You can select more than one system.
This option is available in the table view, tree view, and icon view. Select the checkbox in
the column heading or select Select "collection name" itself to select or clear all displayed
systems.
•
Health status
The HS column displays the overall system health status, which is determined by the default
Hardware Status Polling task and is a roll up of all the status sources, which can be SNMP,
WBEM, HTTP, and cluster status.
Place your cursor over the status icon to display status details. The status values are dependent
on what agents are installed on the target system (WBEM or SNMP). The system name and
overall status appears at the top of the flyover box. All Critical, Major, Minor, or Warning
status types with informational text appear following the system name. Both the system name
and overall status icons drill down to the appropriate system overview page. The System status
details also takes you to the system overview page. The WBEM status icon represents the
status of the system as a whole. This status is not simply a rollup of the worst of the subsystems.
Instead, each subsystem that participates in the overall status calculates a status that contributes
to the overall status. Since it is possible for a subsystem to be in a failed state but the server
to remain functional, the statuses might not match. For a system that does not have the SNMP
agent installed, the flyover includes HTTP, Ping, Serviceguard, and SNMP statuses only. Ping
appears for both WBEM and SNMP. If the HTTP protocol is supported on the system, the HTTP
status appears as a link. Ping and HTTP statuses do not appear for management processors.
If the system is a container (rack, enclosure, complex, or cluster), the status value is the status
of the container itself and does not include the status of the children. If the status components
that make up the overall hardware status are not known, the status of the container itself
appears (complexes and clusters). There is a status for the management processor and a status
for the server for an management processor with an SNMP pass-through. The flyover displays
which status type is causing the problem in the server. To close the box, click Close in the
upper right corner.
By clicking the status icon in this column, the HP Management Agents or the HP Instant Toptools
for Servers page appears. If the system does not have Web Agents or Instant Toptools installed,
the System Page appears. For more information on the system status types, see the HP Systems
Insight Manager User Guide, at http://www.hp.com/go/insightmanagement/sim/docs.
The health status that appears for container systems, such as Serviceguard or a complex, is
the actual hardware status for the container itself. For clusters, the health status is the ping
status.
NOTE: The status of a complex is collected only when VSE Manager is registered with HP
SIM. In addition, the status update is collected every 30 minutes from the nPar or Complex
outside of HP SIM.
•
Management processor
The MP column displays the status icon of the management processor if the system has an
management processor board installed. Otherwise, the Informational icon appears. Clicking
the status icon displays the management processor login page.
74
Screens and product layout
•
Software status
The SW column indicates both the availability of software updates and if they are critical. For
more information on the software status types, see the HP Systems Insight Manager User Guide,
at http://www.hp.com/go/insightmanagement/sim/docs.
If you click the software status, HP SIM displays the Track Software and Firmware versions
page.
•
HP Insight Control performance management
If performance management is installed, this column (indicated by PF) displays the cumulative
performance status of all monitored subsystems for the system. By clicking the status icon in
this column, the performance management page for the selected system appears, providing
more detailed performance information.
The status is considered Unknown if one of the following conditions are met:
◦
performance management is not licensed.
◦
performance management is licensed but is not monitoring a server.
◦
If licensing and monitoring are started, but there are insufficient samples.
If you click the status link, performance management displays a page with information about
purchasing a license to monitor that system or shows notification that performance management
monitoring is not supported on that system.
NOTE: For the PF column, status appears for all systems from the All Servers list. If the status
cannot be determined for some reason, the status appears as Unknown.
•
HP Insight Vulnerability and Patch Manager software
If installed, HP Insight Vulnerability and Patch Manager software vulnerability information
appears in the VPM column of the HP SIM console. Initially, the icon in the column indicates
HP Insight Vulnerability and Patch Manager software eligibility information for the target
system in the row. After target servers are licensed and a vulnerability scan is performed, the
column displays the combined status of the last vulnerability scan on the target system (patch
status does not appear in the column). Click the icon to display detailed information about
the system status about HP Insight Vulnerability and Patch Manager software. Clicking the
Normal, Minor, or Major icons opens a new informational page from which you can access
the last scan results for the system. You can also launch a new scan from this page. Clicking
the Unknown icon for a system displays an explanatory page listing possible reasons why HP
Insight Vulnerability and Patch Manager software is inaccessible and offers possible solutions
to correct the problem.
NOTE: If the HP Insight Vulnerability and Patch Manager software is not installed on the HP
SIM system, the Informational icon appears in the VPM column on the system table view page.
Clicking this icon displays information about installing the HP Insight Vulnerability and Patch
Manager software and purchase licenses.
If the system is not licensed, or has not yet been scanned by the HP Insight Vulnerability and
Patch Manager software, the Informational icon appears in the VPM column. Clicking this
icon displays details about licensing the target system, a link to the HP SIM License Manager
or information about vulnerability scanning, and a link to scan for patch vulnerabilities on the
target system.
•
HP Insight Control virtual machine management
If virt is installed, the VM status column displays the cumulative status of all virtual machine
hosts and virtual machine guests. Clicking the status icon on the VM status column displays in
Navigating the system table view page
75
the Insight Control virtual machine management page for the selected system, providing more
information about the status of the virtual machine.
For systems with Server type and Virtual Machine Host or Virtual Machine Guest subtype, HP
SIM populates the VM status column with the appropriate status icons.
•
Contract and Warranty status
The CW column is available when a Windows CMS and the HP Insight Remote Support Pack
are installed. To view the Contract and Warranty Status page for a system, click the CW status
icon. For more information on the contract ans warranty status types, see the HP Systems
Insight Manager User Guide, at http://www.hp.com/go/insightmanagement/sim/docs.
NOTE: There is no status icon in this column for management processors. Instead see the
contract and warranty status for the server where the management processor is physically
located.
•
Aggregate Event status
The ES column is a summary of all uncleared events. This status is updated whenever an event
is added, updated, or removed. To view all events for a system, including cleared events,
click the ES status icon.
•
System Name
This column contains the actual system name of all discovered systems. Systems appear as a
single system or as a system in a container. When you place the cursor over the system name,
the full system DNS name appears, which helps differentiate between two or more systems
that share the same system name. If you click the system name link, the System Page appears.
For more information, see System page. If you click a system that is a container (rack or
enclosure), the picture view for that object appears. For more information, see Navigating the
picture view page. For more information about racks and enclosures, see the HP Systems
Insight Manager User Guide, at http://www.hp.com/go/insightmanagement/sim/docs.
The System Name column displays systems and associated devices. The following associations
are available in HP SIM:
◦
Management processor to server
◦
Management processor to server for nPar
◦
Management processor to complex
NOTE: After upgrading HP SIM, for this association to be displayed, you must rediscover
the complex if you have appropriate XML, WBEM, and SNMP instrumentation on the
management processor and partition-able cells.
NOTE: For a high-end HP Integrity Superdome server, rerunning discovery works only
if you have an sx2000 Superdome and the latest firmware. Mid-range servers must have
either sx1000 or sx2000 chipsets and the latest firmware.
76
◦
Management processor to enclosure
◦
Server to enclosure
◦
Enclosure to rack
◦
Switch to enclosure
◦
System to cluster
◦
Logical server to server
Screens and product layout
◦
Integrity c-class blade to NonStop ComputerSystem
◦
Host to VME
◦
Active rack manager to rack
◦
Standby rack manager to rack
◦
Server to rack
◦
Server to active rack manager
◦
PDU to rack
◦
PDU to active rack manager
◦
VC Domain to rack
◦
VC Domain to active rack manager
◦
Virtual Machine to Host association
◦
Enclosure Manager system in Encl.
◦
IO module system in Encl.
◦
Blade system in Encl.
◦
iLO 4 system in Host
◦
Associate Segment Server to Fusion Manager
◦
Associate Segment Server to Enclosure
◦
Associate iLO to Segment Server
◦
Associate MSA system to Fusion Manager
The following system types are containers:
◦
Rack
◦
Enclosure
◦
Cluster
When servers and management processors in racks and enclosures are discovered and
identified, associations are made between the systems and the racks and enclosures where
systems reside. This association appears in the System Name column on the system table view
page by showing name in system typecontainer name. The following are examples of the
different associations available:
◦
When switches in blade enclosures are discovered and identified, associations are made
between the switches and the enclosures where they reside. This association appears in
the System Name column on the system table view page by showing switch_name in
Encl. enclosure_name. The System Type column displays Switch as the system type. For
HP SIM to identify and manage the HP ProLiant p-Class server blades correctly, Insight
Management Advisor 5.50 or later must be installed on the blades to make associations
work and event correlation function properly. Clicking an enclosure name in the System
Navigating the system table view page
77
Name column displays a list of all discovered systems in the selected enclosure. The status
for both racks and enclosures is always Unknown.
◦
When a server blade is identified through another system in the same rack or enclosure,
associations are made between the management processor and the enclosures where
they reside. This association appears in the System Name column on the system table
view page by showing the system serial number prepended with Server_ in Encl.
enclosure_name. For example, Server_C349KJP5D876 in Encl. Encl4. The system address,
product name, and operating system do not appear for these systems.
◦
When a NonStop computer system is identified, all c-Class blades that are associated
with this system are identified and the association made. These blades have two
associations, one is associated with the enclosure and the other association is associated
with the NonStop computer system.
◦
When an iLO 4 is discovered, the association between the iLO 4 and the host is made
and the host will appear on the system list page.
You can launch HP Serviceguard Manager to manage a server belonging to an HP
Serviceguard cluster. To do so, ensure that:
•
◦
HP Serviceguard Manager is installed and registered with HP SIM.
◦
The system selected is an HP-UX or Linux server that belongs to an HP Serviceguard cluster.
System Type
This column displays the system type (for example, Server or Desktop). The system type
Unmanaged indicates systems that have no management protocol that HP SIM can detect (for
example, no SNMP, WBEM, or SSH). The system type Unknown indicates systems that have
some management protocol but have not matched any identification rule in HP SIM. For more
information about the different system types, see the HP Systems Insight Manager User Guide,
at http://www.hp.com/go/insightmanagement/sim/docs.
NOTE: Unmanaged systems might indicate that the credentials were not set correctly to
communicate with the system. If you know that there are Insight Management Advisors installed,
verify the credentials.
•
System Address
This column displays the primary IP address of the system that HP SIM uses to communicate
with the system. all systems have an IP address, including HP Serviceguard clusters.
•
Product Name
This column displays the product name of the system.
•
Operating system name
The OS Name column displays the systems operating system. For a Serviceguard cluster, this
column displays HP Serviceguard if the cluster is of type HP-UX, or HP Serviceguard for Linux
if the cluster is of type Linux. HP Serviceguard and HP Serviceguard for Linux under the OS
Name column in the virtual cluster system column do not represent the actual operating system
name and type. This field alerts you that the servers that comprise the cluster are of HP-UX or
Linux type, respectively.
78
Screens and product layout
System table view page buttons
Three buttons at the bottom of the system table view page are available to users with administrative
rights. These buttons are not available when using a tool and selecting an individual target system.
•
Save As Collection
When a system is highlighted, the Save As Collection button is used to save the selection with
a new name. Changes are saved on a per-user basis. If you click Save As Collection, the
collection is saved as a combination of the system and event collections.
•
Delete
This button is used to delete one or more systems from the database. Select the systems to be
deleted, and then click Delete. A dialog box appears. Click OK to continue with the deletion,
or click Cancel to cancel the operation.
NOTE: If you delete a virtual machine host, you can access it through the virt console. The
operations that you can be perform on a virtual machine host are not affected by the fact that
the HP SIM system has been deleted. The virt console continues to show the HP SIM status.
•
Print
This button is used to create a printer-friendly version of the list in a new window. From the
table view page, select File→Print from the browser menu to print the report.
Because certain print options are not supported in HP SIM, you cannot perform the following
tasks:
◦
Change the Orientation to Landscape in the Print dialog box.
◦
Cancel printing after the print job has been executed; however, you can access the
operating systems print queue and cancel the print job
◦
Print to a file
◦
Print specific selections; you can print the entire list only
◦
Print the table view page if you close the browser immediately after issuing a print request
Buttons are disabled if you do not have appropriate rights. However, the Print button appears for
all users.
Customizing the view
The Customize link is located in the upper right corner of the system table view page. Click this
link to configure where columns appear and in what order. When you modify the columns to
display on the system table view page and select Apply to all system table views, these columns
become the default set of columns displayed for any system collection selected if the collection
does not already have customized columns defined. For more information, see Customizing the
system table view page.
Related information
Navigating the cluster table view page
A cluster collection logically groups clusters into a collection based on information in the HP SIM
database. For all other clusters, excluding HP Serviceguard clusters, clicking the name of the cluster
in the Cluster Name column or cluster status icon in the CS column displays the System Page for
Navigating the cluster table view page
79
that cluster. Cluster Monitor can be launched from the cluster table view page in the following
ways:
•
Click the name of a MSCS cluster in the Cluster Name column
•
Click the cluster status icon for a MSCS cluster in the CS column
From this page, you can save a subset of the collection with a new name, delete one or more
clusters from the collection, customize the view, and print the cluster collection view. In a multiuser
environment, only one user at a time can edit a collection. If another user tries to edit the same
collection, a List Edit Warning box appears. The user can cancel the editing request or edit the
collection and save it as a new collection.
NOTE: Not all users can view all clusters. The results of the collection depend on the clusters that
were assigned to the user who created the collection. Each user can only view the clusters that are
assigned to him or her by a user with administrative rights. A user with administrative rights assigns
managed clusters using user authorizations. See Creating new authorizations for more information.
1.
2.
3.
4.
5.
6.
7.
Tabs
View as
Quick Launch
Cluster status summary
Customizing
Cluster collection columns
Buttons
Tabs
The cluster table view page contains the following tabs:
•
System(s)
Lists all systems in the collection.
•
Events
Displays the events for all systems included under the System(s) tab. From this tab, you can
apply additional filters to modify the event table display.
When switching between the System(s) tab and the Events tab, the Events tab "remembers" the
selected events and event filter (if viewing a system collection). The System(s) tab remembers the
80
Screens and product layout
selected systems, view type (table, tree, or icon), and the selected system filter (if viewing an event
collection). However, the selections on each page are independent of each other.
View as
The View as dropdown list is used to select either table, which displays all of the clusters in the
collection in a tree form. See Navigating the tree view for more information about navigating the
tree view.
Quick Launch
The Quick Launch hyperlink links to a short list of frequently used tools. Place your cursor over the
link to expand the menu and view the tools available for selected systems. Selecting a tool from
this list bypasses the target verification page of the Task Wizard. You cannot schedule tools
launched from this menu. Customize this menu by clicking the Customize link in the Quick Launch
menu.
Cluster status summary
The status summary shows how many clusters in the view have a status of: Critical, Major, Minor,
Normal, Disabled, and Unknown, with a total showing how many clusters are in the view.
Cluster collection columns
Sort columns by clicking the column header for ascending or descending order. Place your cursor
over a column name for a brief description of the column. See Customizing the cluster table view
page for more information about customizing columns. The following columns appear on the cluster
view page:
•
Selection
•
Cluster Name
•
Cluster Address
•
Cluster Type
•
Cluster Description
•
Selection
Select the checkbox in this column to select a cluster. You can select more than one cluster.
This option is available in both the table view and the tree view. Select the checkbox in the
column heading or select Select "collection name" itself to select all displayed clusters.
Navigating the cluster table view page
81
NOTE: To display a cluster status that includes only MSCS clusters, and show the true health
of the cluster, you can edit the globalsettings.props file and change the
ClusterStatusWithThresholds property to false. For non-MSCS clusters (OpenVMS, TruClusters,
and Novell NetWare), excluding HP Serviceguard clusters, the cluster status appears as
Unknown.
Procedure 30 Editing the globalsettings.props file
1.
Open the globalsettings.props file located at:
◦
Windows
Typically located at C:\Program Files\HP\Systems Insight Manager\
config\globalsettings.props.
◦
HP-UX and Linux
Located at /etc/opt/mx/config/globalsettings.props
2.
3.
•
Set the ClusterStatusWithThresholds property to false.
Save the file.
Cluster Name
The Cluster Name column contains the cluster name. When you place the cursor over the
cluster name, the full system DNS name is shown. If you click an MSCS cluster name, the
Cluster Monitor page appears. See Using Cluster Monitor for more information. If the cluster
selected is an HP Serviceguard cluster, a new cluster table view page appears, showing the
servers in the cluster. From this list, click a server name to access the System Page for that
server. If the cluster is of any other type, the System Page for that cluster appears. See System
tab for clusters for more information.
•
Cluster Address
The Cluster Address column contains the IP address for the cluster.
NOTE: HP Serviceguard clusters do not have an IP address. Therefore, this column is blank
for this type of cluster.
•
Cluster Type
The Cluster Type column shows the cluster type. Some of the cluster types supported include:
•
◦
HP Serviceguard
◦
MSCS
◦
OpenVMS
◦
TruCluster Production server
◦
TruCluster Server
Cluster Description
The Cluster Description column contains a description of the cluster type. HP Serviceguard
clusters have a description of HP Serviceguard cluster.
82
Screens and product layout
Buttons
The following buttons at the bottom of the page are available to users with administrative rights:
•
Save As Collection. When clusters are selected, you can save the selection with a new name.
Changes are saved on a per-user. See Saving collections for more information.
•
Delete. This button is used to delete clusters from the database. Select clusters to delete from
the database, and then click Delete. A confirmation box appears. to delete the clusters, click
OK, or to cancel the deletion, click Cancel. See Deleting clusters from the HP SIM database
for more information.
•
Print. This button is used to create a printer-friendly version of the list in a new window. From
the cluster view page, select File→Print from the browser menu to print the report.
Because certain print options are not supported in Systems Insight Manager, you cannot
perform the following tasks:
◦
Change the Orientation to Landscape in the Print dialog box.
◦
Cancel printing after the print job has been executed; however, you can access the
operating systems print queue and cancel the print job
◦
Print to a file
◦
Print specific selections; you can print the entire list only
◦
Print the table view page if you close the browser immediately after issuing a print request
Buttons are disabled if you do not have appropriate rights. However, the Print button appears
for all users.
Customizing
The Customize link is located in the upper right corner of the cluster table view page. Click this
button to configure which columns appear and in what order. When you modify the columns to
display on the cluster table view page and select Apply to all cluster table views, these columns
become the default columns displayed for any cluster collection selected if that collection does not
already have customized columns defined. See Customizing the cluster table view page for more
information.
Related information
Navigating the event table view page
The event table view page is the view for an event collection and lists of events that meet common
criteria. For c-Class racks or enclosures, all current systems or events in the enclosure or rack
appear.
iLO 4 and host events both appear because the iLO 4 sends traps on behalf of both the host and
the iLO 4 for Active Health embedded systems.
From this page, you can clear, delete, and assign events, enter comments on the event, and view
printable reports.
Navigating the event table view page
83
1.
•
System(s)
Lists all systems in the collection.
•
Events
Displays the events for all systems included under the System(s) tab. From this tab, you
can apply additional filters to modify the event table display.
When switching between the System(s) tab and the Events tab, the Events tab "remembers"
the selected events and event filter (if viewing a system collection). The System(s) tab remembers
the selected systems, view type (table, tree, or icon), and the selected system filter (if viewing
an event collection). However, the selections on each page are independent of each other.
84
2.
The Quick Launch hyperlink links to a short list of frequently used tools. Place your cursor over
the link to expand the menu and view the tools available for selected systems. Selecting a tool
from this list bypasses the target verification page of the Task Wizard. You cannot schedule
tools launched from this menu. Customize this menu by clicking the Customize link in the Quick
Launch menu.
3.
This summary shows how many events in the view have a status of Critical, Major, Minor,
Normal, and Informational. For more information about event status types, see the HP Systems
Insight Manager User Guide, at http://www.hp.com/go/insightmanagement/sim/docs.
4.
To sort collection results by a particular column, click the column header for ascending or
descending order. Place your cursor over a column name for a brief description of the column.
The following columns appear on the event table view page:
•
Select the checkbox in this column to select an event. You can select more than one event.
Select the checkbox in the column heading or select Select "collection name" itself
to select or clear all displayed events.
•
This column displays whether the event is in the Cleared or Not Cleared state. Events
start in the Not Cleared state. A Cleared state means the user is no longer interested in
this event. Event states also include In Progress, which indicates that not all the data for
the event has been logged. You cannot remove or clear In Progress events. Pending state
events are changed to Not Cleared when the CMS is restarted.
Screens and product layout
•
This column displays the event status icon to indicate the severity of a problem represented
by the event. For more information on event severity types, see the HP Systems Insight
Manager User Guide, at http://www.hp.com/go/insightmanagement/sim/docs.
•
This column displays the type of an event. Some examples of event types include: SNMP
traps, login failures, or the replicate agent settings tool. Select an event type from the list
to view the Event Details section. The information displayed varies depending on the
event. If you cannot see the entire event type in the column, place your cursor over this
field, and a window appears showing the entire event type. For more information abut
event details, see the HP Systems Insight Manager User Guide, at http://www.hp.com/
go/insightmanagement/sim/docs.
•
This column displays the system name on which the event occurred. Clicking a link in this
column displays the System Page for the selected system.
When an event occurs that affects an entire rack or enclosure, it is possible for several
systems in that rack or enclosure to generate a trap for that event. These container traps
are filtered such that only one event is logged per rack or enclosure trap. Also, even
though the source of the trap is a server blade or management processor, HP SIM sets
the Event Source and Associated System for the logged event to the rack or enclosure, as
appropriate. For more information on racks and enclosures, see the HP Systems Insight
Manager User Guide, at http://www.hp.com/go/insightmanagement/sim/docs.
•
This column displays the time stamp when the CMS received the event, which includes
the date and time. If the client is in a different time zone than the event time (CMS time),
the event time is converted to the client time zone.
•
To assign responsibility for an event to a user, select the event, and then click Assign to
at the bottom of the page. The Assign to section appears, which enables you to select a
new assignee or use an existing assignee. If you select to use an existing assignee, you
can select only one user name from the list. This name does not have to be a user with
privileges on the system or a name that can be used to log in to the CMS. This field is
free-form text. For more information about assigning an event to a user, see Assigning
events to users.
•
This column displays the comments for this event or is blank if no comments have been
entered. Comments are truncated in the column. Click the event type to view the entire
comment if needed, or place your cursor over a comment field to display a window that
shows the entire comment to appear. For more information, see Entering comments to
events.
•
This column displays system types such as enclosure or rack, if the system type filter was
selected for the event list display.
•
This column displays the rack name
This column appears when the system is a rack or enclosure and the rack or enclosure
system filter is selected.
•
This column displays the enclosure name.
This column appears when the system is a rack or enclosure and the rack or enclosure
system filter is selected.
•
When you install HP Insight Remote Support Pack and HP SIM together on a Windows
CMS, support case status updates are provided by the Remote Support Pack. The Case
Status column is available when you view the All HP Service Events collection or select
the event search criteria for service case status.
•
When the Remote Support Pack and HP SIM are installed together on a Windows CMS,
the support case ID is provided by the Remote Support Pack. The Case ID column is
Navigating the event table view page
85
available when you view the All HP Service Events collection or select the event search
criteria for service case status. Click the link in the Event Type column to view additional
details about an event.
Selection
Select the checkbox in this column to select an event. You can select more than one event.
Select the checkbox in the column heading or select Select "collection name" itself to
select or clear all displayed events.
State
This column displays whether the event is in the Cleared or Not Cleared state. Events start in
the Not Cleared state. A Cleared state means the user is no longer interested in this event.
Event states also include In Progress, which indicates that not all the data for the event has
been logged. You cannot remove or clear In Progress events. Pending state events are changed
to Not Cleared when the CMS is restarted.
Severity
This column displays the event status icon to indicate the severity of a problem represented
by the event. For more information on event severity types, see the HP Systems Insight Manager
User Guide, at http://www.hp.com/go/insightmanagement/sim/docs.
Event Type
This column displays the type of an event. Some examples of event types include: SNMP traps,
login failures, or the replicate agent settings tool. Select an event type from the list to view the
Event Details section. The information displayed varies depending on the event. If you cannot
see the entire event type in the column, place your cursor over this field, and a window appears
showing the entire event type. For more information abut event details, see the HP Systems
Insight Manager User Guide, at http://www.hp.com/go/insightmanagement/sim/docs.
System Name
This column displays the system name on which the event occurred. Clicking a link in this
column displays the System Page for the selected system.
When an event occurs that affects an entire rack or enclosure, it is possible for several systems
in that rack or enclosure to generate a trap for that event. These container traps are filtered
such that only one event is logged per rack or enclosure trap. Also, even though the source
of the trap is a server blade or management processor, HP SIM sets the Event Source and
Associated System for the logged event to the rack or enclosure, as appropriate. For more
information on racks and enclosures, see the HP Systems Insight Manager User Guide, at
http://www.hp.com/go/insightmanagement/sim/docs.
Event Time
This column displays the time stamp when the CMS received the event, which includes the
date and time. If the client is in a different time zone than the event time (CMS time), the event
time is converted to the client time zone.
Assign To
To assign responsibility for an event to a user, select the event, and then click Assign to at the
bottom of the page. The Assign to section appears, which enables you to select a new assignee
or use an existing assignee. If you select to use an existing assignee, you can select only one
user name from the list. This name does not have to be a user with privileges on the system
or a name that can be used to log in to the CMS. This field is free-form text. For more
information about assigning an event to a user, see Assigning events to users.
86
Screens and product layout
Comments
This column displays the comments for this event or is blank if no comments have been entered.
Comments are truncated in the column. Click the event type to view the entire comment if
needed, or place your cursor over a comment field to display a window that shows the entire
comment to appear. For more information, see Entering comments to events.
System Type
This column displays system types such as enclosure or rack, if the system type filter was
selected for the event list display.
Rack Name
This column displays the rack name
This column appears when the system is a rack or enclosure and the rack or enclosure system
filter is selected.
Enclosure Name
This column displays the enclosure name.
This column appears when the system is a rack or enclosure and the rack or enclosure system
filter is selected.
Case Status
When you install HP Insight Remote Support Pack and HP SIM together on a Windows CMS,
support case status updates are provided by the Remote Support Pack. The Case Status column
is available when you view the All HP Service Events collection or select the event search
criteria for service case status.
Case ID
When the Remote Support Pack and HP SIM are installed together on a Windows CMS, the
support case ID is provided by the Remote Support Pack. The Case ID column is available
when you view the All HP Service Events collection or select the event search criteria for service
case status. Click the link in the Event Type column to view additional details about an event.
5.
The area includes information about the systems or events. An event collection can be displayed
by clicking one of the following:
•
An event collection from the System and Event Collections panel
•
An event status icon in the System Status panel
•
The Events tag from the System Page
•
A private event collection
Event collections are filtered based on authorizations. Users can only view events on systems
for which they have the appropriate authorization.
Tabs
•
System(s)
Lists all systems in the collection.
•
Events
Displays the events for all systems included under the System(s) tab. From this tab, you can
apply additional filters to modify the event table display.
Navigating the event table view page
87
When switching between the System(s) tab and the Events tab, the Events tab "remembers" the
selected events and event filter (if viewing a system collection). The System(s) tab remembers the
selected systems, view type (table, tree, or icon), and the selected system filter (if viewing an event
collection). However, the selections on each page are independent of each other.
Quick Launch
The Quick Launch hyperlink links to a short list of frequently used tools. Place your cursor over the
link to expand the menu and view the tools available for selected systems. Selecting a tool from
this list bypasses the target verification page of the Task Wizard. You cannot schedule tools
launched from this menu. Customize this menu by clicking the Customize link in the Quick Launch
menu.
Event status summary
This summary shows how many events in the view have a status of Critical, Major, Minor, Normal,
and Informational. For more information about event status types, see the HP Systems Insight
Manager User Guide, at http://www.hp.com/go/insightmanagement/sim/docs.
Event collection columns
To sort collection results by a particular column, click the column header for ascending or descending
order. Place your cursor over a column name for a brief description of the column. The following
columns appear on the event table view page:
•
Select the checkbox in this column to select an event. You can select more than one event.
Select the checkbox in the column heading or select Select "collection name" itself to
select or clear all displayed events.
•
This column displays whether the event is in the Cleared or Not Cleared state. Events start in
the Not Cleared state. A Cleared state means the user is no longer interested in this event.
Event states also include In Progress, which indicates that not all the data for the event has
been logged. You cannot remove or clear In Progress events. Pending state events are changed
to Not Cleared when the CMS is restarted.
•
This column displays the event status icon to indicate the severity of a problem represented
by the event. For more information on event severity types, see the HP Systems Insight Manager
User Guide, at http://www.hp.com/go/insightmanagement/sim/docs.
•
This column displays the type of an event. Some examples of event types include: SNMP traps,
login failures, or the replicate agent settings tool. Select an event type from the list to view the
Event Details section. The information displayed varies depending on the event. If you cannot
see the entire event type in the column, place your cursor over this field, and a window appears
showing the entire event type. For more information abut event details, see the HP Systems
Insight Manager User Guide, at http://www.hp.com/go/insightmanagement/sim/docs.
•
This column displays the system name on which the event occurred. Clicking a link in this
column displays the System Page for the selected system.
When an event occurs that affects an entire rack or enclosure, it is possible for several systems
in that rack or enclosure to generate a trap for that event. These container traps are filtered
such that only one event is logged per rack or enclosure trap. Also, even though the source
of the trap is a server blade or management processor, HP SIM sets the Event Source and
Associated System for the logged event to the rack or enclosure, as appropriate. For more
information on racks and enclosures, see the HP Systems Insight Manager User Guide, at
http://www.hp.com/go/insightmanagement/sim/docs.
•
88
This column displays the time stamp when the CMS received the event, which includes the
date and time. If the client is in a different time zone than the event time (CMS time), the event
time is converted to the client time zone.
Screens and product layout
•
To assign responsibility for an event to a user, select the event, and then click Assign to at the
bottom of the page. The Assign to section appears, which enables you to select a new assignee
or use an existing assignee. If you select to use an existing assignee, you can select only one
user name from the list. This name does not have to be a user with privileges on the system
or a name that can be used to log in to the CMS. This field is free-form text. For more
information about assigning an event to a user, see Assigning events to users.
•
This column displays the comments for this event or is blank if no comments have been entered.
Comments are truncated in the column. Click the event type to view the entire comment if
needed, or place your cursor over a comment field to display a window that shows the entire
comment to appear. For more information, see Entering comments to events.
•
This column displays system types such as enclosure or rack, if the system type filter was
selected for the event list display.
•
This column displays the rack name
This column appears when the system is a rack or enclosure and the rack or enclosure system
filter is selected.
•
This column displays the enclosure name.
This column appears when the system is a rack or enclosure and the rack or enclosure system
filter is selected.
•
When you install HP Insight Remote Support Pack and HP SIM together on a Windows CMS,
support case status updates are provided by the Remote Support Pack. The Case Status column
is available when you view the All HP Service Events collection or select the event search
criteria for service case status.
•
When the Remote Support Pack and HP SIM are installed together on a Windows CMS, the
support case ID is provided by the Remote Support Pack. The Case ID column is available
when you view the All HP Service Events collection or select the event search criteria for service
case status. Click the link in the Event Type column to view additional details about an event.
Selection
Select the checkbox in this column to select an event. You can select more than one event. Select
the checkbox in the column heading or select Select "collection name" itself to select or clear
all displayed events.
State
This column displays whether the event is in the Cleared or Not Cleared state. Events start in the
Not Cleared state. A Cleared state means the user is no longer interested in this event. Event states
also include In Progress, which indicates that not all the data for the event has been logged. You
cannot remove or clear In Progress events. Pending state events are changed to Not Cleared when
the CMS is restarted.
Severity
This column displays the event status icon to indicate the severity of a problem represented by the
event. For more information on event severity types, see the HP Systems Insight Manager User
Guide, at http://www.hp.com/go/insightmanagement/sim/docs.
Event Type
This column displays the type of an event. Some examples of event types include: SNMP traps,
login failures, or the replicate agent settings tool. Select an event type from the list to view the Event
Details section. The information displayed varies depending on the event. If you cannot see the
entire event type in the column, place your cursor over this field, and a window appears showing
Navigating the event table view page
89
the entire event type. For more information abut event details, see the HP Systems Insight Manager
User Guide, at http://www.hp.com/go/insightmanagement/sim/docs.
System Name
This column displays the system name on which the event occurred. Clicking a link in this column
displays the System Page for the selected system.
When an event occurs that affects an entire rack or enclosure, it is possible for several systems in
that rack or enclosure to generate a trap for that event. These container traps are filtered such that
only one event is logged per rack or enclosure trap. Also, even though the source of the trap is a
server blade or management processor, HP SIM sets the Event Source and Associated System for
the logged event to the rack or enclosure, as appropriate. For more information on racks and
enclosures, see the HP Systems Insight Manager User Guide, at http://www.hp.com/go/
insightmanagement/sim/docs.
Event Time
This column displays the time stamp when the CMS received the event, which includes the date
and time. If the client is in a different time zone than the event time (CMS time), the event time is
converted to the client time zone.
Assign To
To assign responsibility for an event to a user, select the event, and then click Assign to at the
bottom of the page. The Assign to section appears, which enables you to select a new assignee
or use an existing assignee. If you select to use an existing assignee, you can select only one user
name from the list. This name does not have to be a user with privileges on the system or a name
that can be used to log in to the CMS. This field is free-form text. For more information about
assigning an event to a user, see Assigning events to users.
Comments
This column displays the comments for this event or is blank if no comments have been entered.
Comments are truncated in the column. Click the event type to view the entire comment if needed,
or place your cursor over a comment field to display a window that shows the entire comment to
appear. For more information, see Entering comments to events.
System Type
This column displays system types such as enclosure or rack, if the system type filter was selected
for the event list display.
Rack Name
This column displays the rack name
This column appears when the system is a rack or enclosure and the rack or enclosure system filter
is selected.
Enclosure Name
This column displays the enclosure name.
This column appears when the system is a rack or enclosure and the rack or enclosure system filter
is selected.
Case Status
When you install HP Insight Remote Support Pack and HP SIM together on a Windows CMS,
support case status updates are provided by the Remote Support Pack. The Case Status column is
available when you view the All HP Service Events collection or select the event search criteria for
service case status.
90
Screens and product layout
Case ID
When the Remote Support Pack and HP SIM are installed together on a Windows CMS, the support
case ID is provided by the Remote Support Pack. The Case ID column is available when you view
the All HP Service Events collection or select the event search criteria for service case status. Click
the link in the Event Type column to view additional details about an event.
Table information
The area includes information about the systems or events. An event collection can be displayed
by clicking one of the following:
•
An event collection from the System and Event Collections panel
•
An event status icon in the System Status panel
•
The Events tag from the System Page
•
A private event collection
Event collections are filtered based on authorizations. Users can only view events on systems for
which they have the appropriate authorization.
Navigating the tree view
The tree view provides an automatically populated representation of the actual physical hierarchy
of blade components. For example, blades within enclosures within racks and is a good place to
create and utilize collections of components.
When a collection is selected that was created based on individual members, the tree view appears
in the workspace. The tree view is initially collapsed. Systems might appear in multiple locations
because they can be in multiple containers. Users can view only systems that they are authorized
to view. Therefore, if a user is not authorized to view a particular system in the tree, that branch
does not appear. The following sections are available on the tree view page:
1. Tabs
2. View as
3. Quick Launch
4. Expanding the tree view
5. Selection states for collections
6. Tree view buttons
Navigating the tree view
91
Tabs
The tree view page contains the following tabs:
•
System(s)
Lists all systems in the collection.
•
Events
Displays the events for all systems included under the System(s) tab. From this tab, you can
apply additional filters to modify the event table display.
When switching between the System(s) tab and the Events tab, the Events tab "remembers" the
selected events and event filter (if viewing a system collection). The System(s) tab remembers the
selected systems, view type (table, tree, or icon), and the selected system filter (if viewing an event
collection). However, the selections on each page are independent of each other.
View as
This dropdown list is used to select table, which displays the results in a table form, icons, which
displays only the HS status icon and the System Name for each system, and tree, which displays
the HS status icon and the system name for each system in a tree format. See Navigating the icon
view for more information about the icon view.
Quick Launch
The Quick Launch hyperlink links to a short list of frequently used tools. Place your cursor over the
link to expand the menu and view the tools available for selected systems. Selecting a tool from
this list bypasses the target verification page of the Task Wizard. You cannot schedule tools
launched from this menu. Customize this menu by clicking the Customize link in the Quick Launch
menu.
Expanding the tree view
Branch nodes can be expanded by clicking the toggling expansion icon. However, the system
name is not an expansion control, but a hyperlink to a page that displays more information about
that particular system. When a branch is collapsed, the icon appears as
92
Screens and product layout
. When clicked, the
branch expands to show the child systems, and the icon toggles to
collapses the branch and toggles the icon.
. Clicking the icon again
NOTE: The expansion state persists only for the page session. When the page is reloaded or
navigated to again, a fresh tree is loaded to ensure that all newly discovered systems are added
to the view.
A paging mechanism is provided in the branches. When a branch is expanded, the first 100
systems appear. To view additional systems, click next...of.... Clicking this link displays either the
remaining systems or the next 100 system.
At the top of each tree view there are two expansion buttons. To expand all branches of the tree,
click
. To collapse all branches of the tree to first-level branches, click
. If there are too
many systems to load into the expand all page, a message appears, advising you that there are
too many systems in the tree and the function cannot be performed.
Tree view hierarchy
The tree view displays status data for each system. The status icon is located in the left of the tree
view next to the selection checkbox. If the status of the system is Unknown, no status icon appears.
If the systems are containers, the status to the left of the container name appears as the most critical
status of the systems in the container, including the container status itself. The status of the actual
container appears to the right of the system name and a system type label. Place your cursor over
the status icon to display the status of the container (appears to the right of the system name) and
the status that is a rollup of the container status and status value of the children. If the status of the
container is Unknown, no icon appears.
Selection in the tree view
When a container is selected independently of its contents, the selection control for the tree view
cycles through four states using the following check icons:
•
First, or initial state; nothing selected.
•
Second state; both the container and the contents are selected. If the contents are not already
expanded, the next level of children is expanded to show the selection.
•
Third state; all contents are recursively selected. The children are expanded to show they are
selected. Only the next level is expanded.
•
Fourth state; only the container is selected.
NOTE: If a collection is selected and the collection selects its own contents, the checkboxes are
disabled.
Available drilldowns
The tree view contains hyperlinks for the system name and status icon drilldowns. When you click
a system name, the System Page for that particular system appears. The status icons drill-down to
the status URL for that system, unless the status icon is the status icon to the left of a container.
Clicking the roll-up status of a branch loads a table view of all systems in that branch that match
the roll-up status. Therefore, you are presented with all the systems that contribute to the severity
Navigating the tree view
93
of the roll-up status. For example, if the status icon to the left of the rack is Critical, and you click
the icon, a table view of all systems in the rack with the status of Critical appear.
Selection states for collections
In the tree view, you cannot simultaneously select a collection and members of the same collection.
When a collection is selected, the members appear and their selection boxes are disabled. The
selection states for a collection are as follows:
•
The initial state; nothing is selected.
•
The collection itself is selected; the contents of the collection are disabled.
•
.
The members of the collection are selected; the collection itself is unselected
Additionally, a checkbox at the top of the tree enables you to select the collection that is viewed.
When the checkbox is selected, all the checkboxes under the collection are cleared and disabled.
When a checkbox is cleared, the checkboxes under the collection become selectable.
Tree view buttons
The following buttons at the bottom of the tree view page are available to users with administrative
rights:
•
Save As Collection
When a system or group of systems is selected, this button is used to save the selection with
a new name. Changes are saved on a per-user basis. See Saving collections for more
information.
•
Delete
This button is used to delete one or more systems from the database. Select the systems to be
deleted, and then click Delete. A dialog box appears. Click OK to continue with the deletion,
or click Cancel to cancel the operation. The tree view is refreshed.
NOTE: Only systems can be deleted from the tree view. If you select a collection, the Delete
button is disabled. Collections must be deleted through the Customize Collections page. See
Deleting system and cluster collections for more information about deleting collections.
NOTE: If you delete a virtual machine host, you can still access it through the virt console,
and the operations that can be performed on a virtual machine host are not affected by the
deletion of the HP SIM system. The virt console continues to show the HP SIM status.
NOTE: If you select a collection by selecting Select "collection name" itself, the Delete
button is disabled. To delete collections, go to the Customize Collections page. See Deleting
system and cluster collections or Deleting event collections for more information.
•
Print
This button is used to create a printer-friendly version of the list in a new window. From the
table view page, select File→Print from the browser menu to print the report.
Buttons are disabled if you do not have appropriate rights. However, the Print button appears for
all users.
Related information
94
Screens and product layout
Navigating the icon view
The icon view lists the system name of all discovered systems, as well as the system health status
for each system. The legend shows how many systems in the view are Critical, Major, Minor,
Normal, Disabled, and Unknown. Select the checkbox next to system name to select a system. You
can select more than one system, or to select an entire collection, select the checkbox, Select
"collection name" itself.
Place your cursor over the status icon to display status details. The status values are dependent on
what agents are installed on the target system (WBEM or SNMP). The system name and overall
status appears at the top of the flyover box. All Critical, Major, Minor, or Warning status types
with informational text appear following the system name. Both the system name and overall status
icons drill down to the appropriate system overview page. The System status details also takes
you to the system overview page. The WBEM status icon represents the status of the system as a
whole. This status is not simply a rollup of the worst of the subsystems. Instead, each subsystem
that participates in the overall status calculates a status that contributes to the overall status. Since
it is possible for a subsystem to be in a failed state but the server to remain functional, the statuses
might not match. For a system that does not have the SNMP agent installed, the flyover includes
HTTP, Ping, Serviceguard, and SNMP statuses only. Ping appears for both WBEM and SNMP. If
the HTTP protocol is supported on the system, the HTTP status appears as a link. Ping and HTTP
statuses do not appear for management processors. If the system is a container (rack, enclosure,
complex, or cluster), the status value is the status of the container itself and does not include the
status of the children. If the status components that make up the overall hardware status are not
known, the status of the container itself appears (complexes and clusters). There is a status for the
management processor and a status for the server for an management processor with an SNMP
pass-through. The flyover displays which status type is causing the problem in the server. To close
the box, click Close in the upper right corner.
This
1.
2.
3.
4.
5.
page includes the following sections:
Tabs
Quick Launch
View as
System health status summary
Icon view buttons
Navigating the icon view
95
Tabs
The icon view page contains the following tabs:
•
System(s)
Lists all systems in the collection.
•
Events
Displays the events for all systems included under the System(s) tab. From this tab, you can
apply additional filters to modify the event table display.
When switching between the System(s) tab and the Events tab, the Events tab "remembers" the
selected events and event filter (if viewing a system collection). The System(s) tab remembers the
selected systems, view type (table, tree, or icon), and the selected system filter (if viewing an event
collection). However, the selections on each page are independent of each other.
Quick Launch
The Quick Launch hyperlink links to a short list of frequently used tools. Place your cursor over the
link to expand the menu and view the tools available for selected systems. Selecting a tool from
this list bypasses the target verification page of the Task Wizard. You cannot schedule tools
launched from this menu. Customize this menu by clicking the Customize link in the Quick Launch
menu.
View as
The View as dropdown list is used to select either table, which displays the results in a table form,
icons, which displays only the HS status icon and the System Name for each system, and tree,
which displays the HS status icon and the System Name for each system in a tree format. See
Navigating the tree view for more detailed information on the tree view. See Navigating the system
table view page for more information about the system table view.
System health status summary
This summary shows how many systems in the view have a status of Critical, Major, Minor, Normal,
Disabled, and Unknown. See the HP Systems Insight Manager User Guide, at http://www.hp.com/
go/insightmanagement/sim/docs, for more information about system status types.
Icon view buttons
The following buttons at the bottom of the icon view page are available to users with administrative
rights.
•
Save As Collection
When you select a system or group of systems, this button is used to save the selection with
a new name. Changes are saved on a per-user basis. See Saving collections for more
information.
•
Delete
This button is used to delete one or more systems from the database. See Deleting systems
from the HP SIM database for more information.
96
Screens and product layout
NOTE: If you delete a virtual machine host, you can still access it through the virt console,
and the operations that can be performed on a virtual machine host are not affected by the
deletion of the HP SIM system. The virt console continues to show the HP SIM status.
NOTE: If you select a collection by selecting Select "collection name" itself, the Delete
button is disabled. See Deleting system and cluster collections or Deleting event collections
for more information.
•
Print
This button is used to create a printer-friendly version of the list in a new window. From the
icon view page, select File→Print from the browser menu to print the report.
Related information
Navigating the picture view page
The picture view page for racks and enclosures contains a picture view of the discovered systems
in the rack or enclosure if available. The rack name appears along with a picture view, table view,
or iconic view of the rack. While signed in to HP SIM, placing your cursor over a server shown in
the view, displays information on that particular server, including server blade name, slot number,
and the enclosure in which the server is located. You can also click a component name to display
detailed information about the component. The System Page appears.
Navigating the picture view page
97
Rack name
The system name is displayed with the system type in parenthesis.
Tabs
The picture view page contains the following tabs:
•
System(s)
Lists all systems in the collection.
•
Events
Displays the events for all systems included under the System(s) tab. From this tab, you can
apply additional filters to modify the event table display.
When switching between the System(s) tab and the Events tab, the Events tab "remembers" the
selected events and event filter (if viewing a system collection). The System(s) tab remembers the
selected systems, view type (table, tree, or icon), and the selected system filter (if viewing an event
collection). However, the selections on each page are independent of each other.
Quick Launch
The Quick Launch hyperlink links to a short list of frequently used tools. Place your cursor over the
link to expand the menu and view the tools available for selected systems. Selecting a tool from
this list bypasses the target verification page of the Task Wizard. You cannot schedule tools
launched from this menu. Customize this menu by clicking the Customize link in the Quick Launch
menu.
View as
You can change the way the picture view page appears. Click the down arrow on the View as
dropdown list, and select table, icon, or picture view. However, the picture view is only available
if you have already drilled down to a rack or enclosure by clicking the rack or enclosure name on
the system table view page and then switching back to a tabular or iconic view. Drilling down into
a rack or enclosure restricts the systems to only those that pertain to the rack or enclosure. You can
then switch between the other view types.
Select from the following views:
•
Table.
•
Tree.
•
Icons.
•
Picture.
Selection in the icon view
Select the system type based on the following:
98
•
All Blades
•
All Interconnect Switches
•
All Onboard Administrators
•
All Enclosures
Screens and product layout
Front and rear picture views
Displays realistic front and rear picture views which include:
•
A collapsible tray for each enclosure in the rack, with the enclosure status and name in the
title bar
•
Selection checkboxes on all selectable items
•
Status icons on all items with status
•
Each blade or switch hyperlinks to that system's System Page
While logged in to HP BladeSystem, placing your cursor over a component shown in the view,
displays information on that particular component, including slot number/bay number, blade server
name/IP address, and product model. If the bay is empty it displays as an empty bay. If the
Firmware of the power enclosure is less than 1.80, a question mark is displayed for each bay of
the enclosure. When the cursor is moved over that bay, it suggests to upgrade the Firmware to
1.80 or higher. You can also click a component to display information about that component. The
System Page appears. For more information, see System tab for blade servers.
To view details about p-Class or e-Class systems that support SNMP or HTTP, position your cursor
over the system and a tool tip appears.
Navigating the picture view page
99
NOTE:
If the system does not support SNMP or HTTP query, Not Available appears.
NOTE: For p-Class and e-Class servers, the IPv6 Address is displayed in the tool tip only when
IPv6 is enabled on the server.
100 Screens and product layout
•
The picture view tool tip displays the following information for p-Class servers:
◦
Bay
◦
Name
◦
IP Address
◦
Serial Number
◦
Model
◦
Operating System
◦
System ROM Version
◦
Insight Management Version
◦
Management Processor IP
◦
Management Processor Firmware Version
◦
The picture view tool tip displays the following information for p-Class and e-Class switches:
◦
–
Bay
–
Name
–
IP Address
–
Serial Number
–
Model
–
Firmware Version
–
The running status for VC switches
The picture view tool tip displays the following information for c-Class servers:
NOTE:
For p-Class or e-Class systems, the Mezzanine slot labels are not shown.
–
Bay
–
Name
–
IP Address
Both the IPv4 and IPv6 addresses are displayed for management processors.
–
Serial Number
–
Serial Number (Logical)
–
UUID (Logical)
NOTE: The Serial Number (Logical) and UUID (Logical) are shown for the synergized
server environment only.
–
Model
–
Operating System
–
System ROM Version
–
Insight Management Version
–
Management Processor IP
–
Management Processor Firmware Version
Navigating the picture view page
101
–
Mezzanine Slot X
NOTE: The X refers to the slot number of the Mezzanine card. If the c-Class server
does not have any Mezzanine cards, this option is not shown.
Starting in HP SIM 5.2 and forward, HP ProLiant BL680c servers are also supported.
◦
The picture view tool tip displays the following information for e-Class servers:
NOTE:
The e-Class server and desktop tool tip shows only the information listed below.
–
Bay
–
Name
–
IP Address
–
IPv6 Address
Both the IPv4 and IPv6 addresses are displayed for management processors.
◦
◦
–
Serial Number
–
Model
–
Operating System
The picture view tool tip displays the following information for e-Class switches:
–
Name
–
IP Address
–
Serial Number
–
Model
The picture view tool tip displays the following information for bare metal blades:
NOTE: The bare metal blade tool tip shows only the information listed below. Any
information in addition to the items listed are displayed as Not Available.
–
Bay
–
Name
–
Serial Number
–
Model
–
System ROM Version
–
Management Processor IP
–
Management Processor Firmware
Enclosure details
Enclosure details to the right of the picture views include:
•
Enclosure Name. Click Enclosure Name to display the picture view of the enclosure.
•
Serial number. Displays the serial number of the system.
•
UUID. Of enclosure
•
Unit ID (LED). Indicates whether the Unit ID is on or off.
102 Screens and product layout
•
Onboard Administrator. Name of the Onboard Administrator is displayed
•
Health Status. Indicates the health status of the enclosure.
The details such as Data Center ID, Data Center Location, Row Number and Position in Row are
visible only when you create a new rack or when you edit an existing rack.
Rack Details
•
Rack Name. Displays the name of the rack.
•
Health Status. Indicates the health status of the rack.
•
Data Center ID. Indicates the identification number of the data center which the rack is part
of.
•
Data Center Location. Indicates the location of the data center which the rack is part of.
•
Row Number. Indicates the row number of the rack.
•
Position in Row. Indicates the position of the rack in the row.
Picture view buttons
Four buttons at the bottom of the System(s) tab (picture view) are available to users with
administrative rights.
•
Save As Collection. When a system is highlighted, this button is used to save the selection with
a new name. Changes are saved on a per-user, per-collection basis.
•
Delete. This button is used to delete one or more systems from the database. Select the systems
to be deleted, and click Delete. A dialog box appears. Click OK to continue with the deletion
or click Cancel to cancel the operation.
•
Edit Rack. This button is used to edit rack information. Select the rack to be edited and click
Edit Rack.
•
Print. When the report is displayed, select File→Print from the browser menu to print the report.
NOTE: Because certain print options are not supported in Systems Insight Manager, you
cannot:
◦
Change the Orientation to Landscape in the Print dialog box (see Printing Problems in
the Troubleshooting section of Systems Insight Manager Technical Reference Guide for
a workaround to this issue)
◦
Cancel printing after the print job has been executed, but you can access the operating
systems print queue and cancel the print job
◦
Print to a file
◦
Print selected systems, only entire list of systems
◦
Print the system table view page if you close the browser immediately after issuing a print
request
Buttons are disabled if you do not have appropriate rights. However, the Print button appears for
all users.
Updated timestamp
The updated field automatically refreshes and displays the last updated timestamp. This reflects
the Central Management Server time and not the client time.
Related information
Navigating the picture view page 103
Viewing racks
NOTE: For c-Class systems (blades and switches in an enclosure) to appear in BladeSystem
Integrated Manager tree or picture view, at least one Onboard Administrator in that enclosure
must be discovered before or after the devices. The systems can be discovered in HP SIM but do
not appear in BladeSystem Integrated Manager tree or picture view if none of the Onboard
Administrators are discovered.
NOTE: Any change in the physical configuration of the c-Class enclosure, such as moving the
systems from one slot to another or removing a system, requires re-identification of the Onboard
Administrator.
Viewing enclosures
The picture view page for enclosures contains a diagram of the discovered systems in the enclosure
if available. The enclosure name appears along with a picture view, table view, or iconic view of
the enclosure. While signed in to Systems Insight Manager (HP SIM), placing your cursor over a
server shown in the view, displays information on that particular server, including server blade
name, andslot number You can also click a server name to display information about the server.
The System Page appears.
The following systems are displayed in the picture view for racks and enclosures:
•
Servers, desktops and workstation blades
•
Interconnect modules
Slots that have no server or desktop identified and no interconnect switch identified are also
displayed in the picture view for enclosures.
The following sections are displayed in the picture view for racks and enclosures:
•
System Status
◦
•
Health Status icon. Represents the health of a system including Critical, Major, Minor, or
Normal.
Identification
◦
Serial Number. Displays the serial number of the enclosure.
◦
UUID. A unique identifier from the agent or other instrumentation on the system.
◦
Rack Name. Click to display the rack in picture view.
◦
Unit ID (LED). Indicates whether the Unit ID is on or off.
◦
Onboard Administrator - Click the Onboard Administrator link to display the Onboard
Administrator home page.
NOTE:
◦
Virtual Connect Manager. Displays the IP address to the HP Virtual Connect Enterprise
Manager. You can click the IP address to access the VCEM system.
NOTE:
◦
The Onboard Administrator link appears only for c-Class enclosures.
This option appears only when a Virtual Connect is available.
Virtual Connect Manager Domain Name. Displays the VCEM domain name. Click the
domain name to view the System page of the VC Domain.
104 Screens and product layout
•
For c-Class enclosures:
◦
Power and Thermal section
–
Power Redundancy. Displays Power Redundancy status. Click Power Redundancy
to display the Onboard Administrator home page.
–
Fan Redundancy. Displays Fan Redundancy status. Click Fan Redundancy to display
the Onboard Administrator home page.
–
Enclosure Ambient Temperature. Displays the following:
–
◦
–
Status. Displays the current status in icon form.
–
C/F. Displays the current temperature in degrees Celsius and Fahrenheit.
–
Graph. Displays a graph depicting the temperature.
The following information displays for each power unit present in the enclosure:
–
Bay Number. Displays the number assigned to the bay.
–
Firmware Revision. Displays the firmware revision number.
–
A/C Input. Indicates the health status of the power unit.
–
Phase. Displays the phase.
–
Serial Number. Displays the serial number of the power unit.
–
Part Number. Displays the part number for the power unit.
–
Power Consumption. Displays the power consumption in watts to include:
–
Output/Capacity. Displays the current output verses the capacity.
–
Graph. Displays a graph depicting the output verses the capacity.
Fans section
–
Bay. Displays the bay number.
–
Health Status. Displays the health status of the enclosure.
–
Part Number. Displays the part number for the fan.
–
Power Used (Watts). Displays the amount of watts currently used.
–
Speed (RPM). Displays the current speed in RPMs.
Viewing enclosures 105
NOTE: From this page, you can also view the enclosure details in a separate window. Select
the enclosure name on the page and click Printable Enclosure details. A new window displays
the details of the enclosure.
•
For p-Class enclosures:
◦
Power and Thermal section
The following items are displayed on the Enclosure View for a Power Enclosure if at least
one management processor in the rack using that power enclosure has firmware version
of 1.80 or higher.
–
Load Balanced Cable. Indicates whether the load balanced cable is present.
–
Power Redundancy. Displays Power Redundancy status.
–
Temperature A. Displays overall temperature in the left section of the power enclosure.
–
Center Temperature. Displays overall temperature in the center section of the power
enclosure.
–
Temperature B. Displays overall temperature in the right section of the power
enclosure.
–
The following information displays for each power unit present in the enclosure:
–
Bay Number. Displays the number assigned to the bay.
–
Firmware Revision Displays the firmware revision number.
–
A/C Input. Indicates the health status of the power unit.
–
Input Temperature. Displays the following:
–
–
Status. Displays the status of the input temperature.
–
C/F. Displays the current temperature in degrees Celsius and Fahrenheit.
–
Graph. Displays a graph depicting the Trip temperature verses Fail
temperature.
Output Temperature. Displays the following:
–
Status. Displays the status of the output temperature.
–
C/F. Displays the current temperature in degrees Celsius and Fahrenheit.
–
Graph. Displays a graph depicting the Trip temperature verses Fail
temperature.
While logged in to HP BladeSystem placing your cursor over a component shown in the view,
displays information on that particular component, including slot number/bay number, server blade
name or IP address, product model, and the enclosure in which the server is located. If the bay is
empty it displays it as an empty bay. If the Firmware of the power enclosure is less than 1.80, a
question mark is displayed for each bay of the enclosure. When the cursor is moved over that bay,
it suggests to upgrade the Firmware. You can click a component in the picture view to display
information about that component. The System Page appears. However, if you click the status icon
that is displayed on the component in the picture view, you remain on the Enclosure View page.
The buttons at the bottom of the picture view page are available to users with administrative rights.
•
Save As Collection. When a system or group of systems is selected, this button is used to save
the selection with a new name. Changes are saved on a per-user.
•
Delete. This button is used to delete one or more systems from the database. Select the systems
to be deleted, and click Delete. A dialog box appears. Click OK to continue with the deletion
or click Cancel to cancel the operation. The picture view is refreshed.
106 Screens and product layout
NOTE:
Only systems can be deleted from the picture view. If a collection is selected, the
Delete button becomes disabled. Collections must be deleted through the Customize Collections
page.
NOTE:
If a VM Host is deleted, it can still be accessed through the virt console, and the
operations that can be performed on a VM Host are not affected by the deletion of the Systems
Insight Manager (HP SIM) system. The virt console continues to show the HP SIM status.
NOTE:
If you select a collection by checking Select "collection name" collection itself, the
Delete button is disabled. To delete collections, go to the Customize Collections page.
•
Print. Click Print to display a printable version of the picture. Print the picture from the browser
by clicking File→Print.
Print is available regardless of your rights, however the other options are only enabled if you
have appropriate rights.
Viewing an enclosure
To view an enclosure or power enclosure, click an enclosure collection in picture view or click
Enclosure Name in the Rack view. The Enclosure View page is displayed in picture view. The
picture view page for enclosures contains an image of the discovered enclosure with the discovered
servers residing in the enclosure.
Viewing p-Class enclosures
p-Class enclosures together form a rack if a set of enclosures are networked in the hardware level.
A p-class enclosure hosts the ProLiant BL p-Class server types.
To view a p-Class enclosure:
1. From the Systems Insight Manager Home page, expand the HP BladeSystem collection in the
Systems and Events panel.
2. Expand the All p-Class Enclosures. The p-Class enclosures tree expands.
3. Click the enclosure name that you want to view. The enclosure appears in the Enclosure View
page.
Viewing p-Class enclosures 107
NOTE: The p-Class power enclosure and power redundancy information appears only when
the firmware of at least one of the management processors is greater or equal to 1.82.
4.
To change the view from the tree view default, select table or icons from the View as dropdown
list. The page reappears displaying the new view.
Viewing e-Class enclosures
The e-Class collections include the Consolidated Client Infrastructure blade PC Enclosures which
host 20 PC blades including bc1000/bc1500 and bc2000/bc2500 PC blade types, and the
e-Class BL10e server blades.
To access all e-Class Enclosures:
1. From the Systems Insight Manager Home page, expand the HP BladeSystem collection in the
Systems and Events panel.
2. Expand the All e-Class Enclosures collection. The All e-Class Enclosures tree expands.
3. Click the enclosure name that you want to view. The enclosure appears in the Enclosure View
page.
4. To change the view from the tree view default, select table or icons from the View as dropdown
list. The page reappears displaying the new view.
Viewing c-Class enclosures
c-Class collections consist of the HP BladeSystem c7000 and c3000 Enclosures, HP ProLiant BL
c-Class server blades, network interconnect components, Onboard Administrator, and management
tools that enable adaptive computing, optimized for rapid deployment.
108 Screens and product layout
To view a c-Class enclosure:
1. From the Systems Insight Manager Home page, click All c-Class Enclosures in the Systems and
Events panel. You can also expand the toggling expansion control to expand the c-Class
Enclosures collection. The c-Class enclosures appear.
NOTE: In addition to displaying details such as servers, storage, the picture view of the
c-class enclosures also shows the PCI expansion blade that is associated with the enclosure.
2.
3.
Click on the enclosure that you want to view. The Enclosure View page appears.
To change the view from the tree view default, select table or icons from the View as dropdown
list. The page reappears displaying the new view.
To view a c3000 class enclosure:
1. From the Systems Insight Manager Home page, click All c-Class Enclosures in the Systems and
Events panel. You can also expand the toggling expansion control to expand the c-Class
Enclosures collection. The c-Class enclosures appear.
2. Click on the enclosure that you want to view. The Enclosure View page appears.
3. To change the view from the tree view default, select table or icons from the View as dropdown
list. The page reappears displaying the new view.
Viewing c-Class enclosures 109
Starting with this release, you can view the DVD connection status of the c-class c3000 Rack and
c3000 Tower model enclosures. The picture view of the enclosure displays the DVD image for the
enclosure. Click on the DVD image of the enclosure to log in to the Onboard Administrator and
view the connection status.
NOTE:
Redundant Onboard Administrator is not supported in c3000 Enclosure.
NOTE: If the enclosure is managed by Virtual Connect Manager, the picture view also displays
the Virtual Connect Domain name and the IP address.
Customizing system and cluster collections
The System and Event Collections panel contains a Systems collection. The Systems collection
contains additional system, cluster, and System Functions collections.
NOTE:
Cluster collections are created only by attributes, not by members.
Collections can be private or shared. Shared collections are visible to all users, while private
collections are personal collections you create that only you can view. HP SIM includes several
predefined shared collections. For example, Systems by Status is a default shared collection is
included with HP SIM. For information about default shared collections, see the HP Systems Insight
Manager User Guide, at http://www.hp.com/go/insightmanagement/sim/docs.
To customize system collections, click Customize in the System and Event Collections panel. The
Customize Collections page appears, and includes the following options:
1. “Displaying collection type” (page 111)
2. “Expanding or collapsing collections” (page 111)
3. “Customize collections table” (page 111)
4. “Available buttons” (page 111)
110
Screens and product layout
Displaying collection type
Select the type of collection you want to customize by selecting Systems from the Show collections
of dropdown box.
Expanding or collapsing collections
You can select to view all collections included in the Shared or Private collections, or to view only
the Shared or Private collection titles. Click
table, or click
to expand all system and cluster collections in the
to collapse all system and cluster collections in the table.
Customize collections table
When the Customize Collections page appears, if the collection and system status appears in the
System and Event Collections panel, a table appears that includes the names of all the collections.
Available buttons
On the Customize Collections page, the following buttons are available:
•
New
This enables you to create a new system or cluster collection. If you have administrative rights,
you can save the new collection as a shared collection. Otherwise, you can save it only as a
private collection. For more information about creating a system collection by attributes, see
Performing an advanced search for systems.
•
Edit
This enables you to modify an existing collection name and its contents. This button is disabled
if a locked collection is selected.
•
Move
This enables you to move collections from one collection to another.
•
Copy
This enables you to copy a collection as another collection.
Customizing system and cluster collections
111
•
Delete
This enables you to delete an existing system or cluster collection, or system and event
combination collections. Only empty system collections can be deleted. If you have
administrative rights, you can delete a shared system or cluster collection. This button is disabled
if a locked collection is selected.
•
Set Properties
This enables you to set the display status, collection visibility, and the default view.
Related information
Customizing event collections
The System and Event Collections panel contains an Events collection. This collection contains
collections of different types of events.
Collections can be private or shared. Shared collections are visible to all users, while private
collections are personal collections you create that only you can view. HP SIM includes several
predefined shared collections. For example, Events by Severity is a default shared collection
included with HP SIM. See the HP Systems Insight Manager User Guide, at http://www.hp.com/
go/insightmanagement/sim/docs, for more information about default shared collections.
To customize system collections, click Customize in the System and Event Collections panel. The
Customize Collections page appears and includes the following options:
1. “Displaying collection type” (page 112)
2. “Expanding or collapsing collections” (page 112)
3. “Customize collections table” (page 113)
4. “Collection buttons” (page 113)
Displaying collection type
Select Events from the Show collections of dropdown box to customize event collections.
Expanding or collapsing collections
You can select to view all collections included in the Shared and Private collections, or to view
only the Shared and Private collection titles. Click
in the table, or click
112
Screens and product layout
to expand all system and cluster collections
to collapse all system and cluster collections in the table.
Customize collections table
When the Customize Collections page appears, if the collection and system status appears in the
System and Event Collections panel, a table appears that includes the names of all the collections.
Collection buttons
The following options are available on the Customize Collections page for events:
•
New
This enables you to create a new event collection. If you have administrative rights, you can
save the new collection as a shared collection. Otherwise, you can save it only as a private
collection. See Performing an advanced search for events for more information about creating
an event collection by attributes.
•
Edit
This enables you to modify an existing collection name and its contents.
•
Move
This enables you to move collections from one collection to another, either from a private to
a shared collection, or from a shared to a private collection.
•
Copy
This enables you to copy a collection as another collection.
•
Delete
This enables you to delete an existing event collection or system and event combination
collections. If you have administrative rights, you can delete a shared event collection. Only
empty event collections can be deleted.
•
Set Properties
This enables you to set the visibility of the collection and its members.
Command line interface
Users with administrative rights can use the mxcollection command to set properties for
collections from the CLI.
See the HP Systems Insight Manager User Guide, at http://www.hp.com/go/insightmanagement/
sim/docs, for more information about accessing the manpage, which includes detailed information
for this command.
Related information
Managing event handling tasks
CAUTION: If you delete an automatic event handling task, the task is permanently deleted, and
you cannot restore it.
The Automatic Event Handling - Manage Tasks page includes a table that shows all automatic
event handling tasks and how the task was set up.
From this page, you can:
•
Create a new automatic event handling task. See Creating an automatic event handling task
for more information.
•
Edit a task. When you select a task and click edit, the edit wizard appears, which is similar
to the page for creating a new automatic event handling task, but the fields are prepopulated
with the current settings for the task. An additional field is available to reassign the task owner.
See Editing automatic event handling tasks for more information.
Managing event handling tasks
113
•
Replicate the configuration details of an existing task. A Copy Task page appears below the
task list. Specify a new task name in the Task name box. Click OK, and a new and separate
task is created. See Copying automatic event handling tasks for more information.
•
View the task definition for the selected task. The entire configuration for the selected task,
such as task name, owner, time filter, event, system criteria, actions, modem settings, and
e-mail settings, appears. See Viewing task definitions for automatic event handling tasks for
more information.
•
View the task result details for a selected task below the list. See Viewing event task results
for more information.
•
Disable a task. See Enabling and disabling event handling tasks for more information.
•
Delete tasks. A confirmation box appears. Click OK to delete, or click Cancel to cancel the
deletion. See Deleting events for more information.
Related information
System Type Manager page
The Manage System Types page lists rules currently defined in HP SIM.
To access the Manage System Types page, select Options→Manage System Types.
System type
You can filter the list on the Manage System Types page by system type by selecting a type from
the System Type dropdown list. Click the down arrow, and then select a system type.
Columns
The following columns appear on the Manage System Types page:
•
Product Model
•
System Type
•
Subtype
•
Protocol
•
Priority
•
System Object Identifier
Click a column heading to sort the column in ascending or descending order.
Total
The Total field displays the total number of systems that meet the System type criteria selected in
the System type dropdown list.
114
Screens and product layout
Available buttons
The following buttons are available on the Manage System Types page:
•
New. Used to create a new rule.
•
Edit. Used to edit existing rules. Select the rules to edit, and then click Edit.
•
Delete. Used to delete an existing SNMP rule. Select the rule, and then click Delete. In the
confirmation box, click OK to delete the rule, or Cancel, to return to the Manage System Types
page without deleting the rule.
WMI Mapper Proxy
The WMI Mapper Proxy is a configuration setting for WMI. The WMI Mapper receives client
CIM/XML WBEM requests and converts the requests to WMI requests. The WMI results are converted
to CIM/XML format and returned to the CMS. The discovery and Identification task uses the proxies
in the WMI Mapper Proxy list to discover whether a system is a WMI-enabled system. If the system
is WMI-enabled, then the identification information for that system is returned.
The WMI Mapper Proxy feature enables you to perform the following tasks:
•
Add a WMI Mapper Proxy.
Select Options→Protocol Settings→WMI Mapper Proxy→[New]. The Add WMI Mapper Proxy
section appears.
•
Edit a WMI Mapper Proxy.
Select Options→Protocol Settings→WMI Mapper Proxy. Select the proxy to edit, and then
click [Edit]. The Edit WMI Mapper Proxy section appears.
•
Delete a WMI Mapper Proxy.
Select Options→Protocol Settings→WMI Mapper Proxy. Select the systems to delete, and then
click Delete. A confirmation box appears. Click OK to delete the systems, or click Cancel to
cancel the deletion.
NOTE:
Sort any column by clicking the column heading.
Related procedures
Adding a WMI Mapper Proxy
Editing a WMI Mapper Proxy
Deleting a WMI Mapper Proxy
System page
Use the System Page to view information related to a specific system. This page shows the following
tabs:
•
System. Includes general system and status information.
•
Tools & Links. Includes links to System Management pages, HP SIM pages, and other useful
links.
•
Events. Displays the event table view page for the system.
•
Performance. Is available only when virtual machine hosts and guests are discovered, and
displays performance information.
•
Performance/Utilization. Includes general information about the performance of the system.
WMI Mapper Proxy
115
•
Port Mapping/Mezzanine Cards. Displays port mappings for c-Class blades and switches
only.
•
Essentials. Is available only for systems that might support other HP SIM partner applications
and provides a description of available software and a link to the HP website. You must have
administrative or operator rights to view this tab.
You can access the System Page one of the following ways:
•
Select Tools→System Information→System Page, and then select a target system.
•
Click a system name in the System Name column on one of the system view pages.
NOTE:
To quickly view the CMS System Page, select Options→View CMS System Page.
System tab for servers
On the System tab, a status icon indicates the overall health status stored in the database. If a
system is suspended, a disabled icon appears in place of the hardware status icon and software
status icon.
When the health status of an HP Enclosure Manager is set, the health status for the HP Enclosure
Manager, enclosure, blade, and I/O module must all be set.
The System Status section contains more information on the system status.
The Quick Launch hyperlink links to a short list of frequently used tools. Place your cursor over the
link to expand the menu and view the tools available for selected systems. Selecting a tool from
this list bypasses the target verification page of the Task Wizard. You cannot schedule tools
launched from this menu. Customize this menu by clicking the Customize link in the Quick Launch
menu.
System Status
Table 5 System status section
Field
116
Description
Health Status
The overall status for a system. It is obtained from WBEM,
SNMP, Ping, Out-of-Band (OOB), and the HTTP protocols
with the most critical status displayed. WBEM, SNMP, and
OOB status can have sub statuses that are used for the
calculation of their upper status. A ping (ICMP or TCP
reachable check) is always made. The link for Health Status
will not be present if it has sub status. Otherwise, click the
Health Status link to access the HP SMH, if it is present. If
HP SMH is not present, the link accesses the Property Page
Status page. If no option is available, the Health Status
link is not present. When the WBEM status is expanded,
the statuses are sorted alphabetically and displayed
vertically. If a status source does not have a value, that
status does not appear. When you place your cursor over
a status text, a flyover appears displaying information
explaining the status. When the status is Disabled, the
system could be off-line or unreachable or the system is
suspended from monitoring. For a cluster, the rollup status
of all its components appears.
Management Processor Status
The management processor status (if available) links to a
web server on the management processor.
Software Status
The software status icon links to the system software Version
Control Agent if available.
Disabled Status
A system that is suspended has a disabled icon in the HW
and SW columns on the system table view page.
Screens and product layout
Table 5 System status section (continued)
Field
Description
Vulnerability Status
The vulnerability status of a system is the indicator
summation of security and configuration weaknesses as
determined by an external security scan of the system.
Contract and Warranty Status
The Contract and Warranty Status is available when you
have a Windows CMS, and the HP Insight Remote Support
Pack is installed. You can view Contract and Warranty
status updates for HP systems that have contract and
warranty data collection enabled. Click the Contract and
Warranty Status icon to view the Contract and Warranty
Details page for the system.
Aggregate Event Status
The Aggregate Event Status is a summary of uncleared
events. This status is updated when an event is added,
updated, or removed. To view the System Page Events tab
for a system, click the Aggregate Event Status icon. For iLO
4 systems, this status reflects both the iLO 4 and host event
state. For Active Health enabled systems, iLO 4 is launched
when you click this link.
If a system is in a suspended mode, the System Page displays a disclaimer under System Status,
stating Monitoring of the system is suspended until, and gives a date and time for
monitoring to resume.
Partner applications might have their own status registered with the CMS. If so, these statuses
appear under Health Status and as status columns on the system table view page. For example,
the System Security Vulnerability Status links to information about system status regarding HP Insight
Vulnerability and Patch Manager software.
More Information
This section provides more detailed information about the system and lists available information
tools. Possible links include:
•
HP System Management Homepage
•
Property Page
•
Partition Manager View
•
Virtual Manager Host View
•
BladeSystem XXXXX Onboard Administrator
•
Superdome 2 Onboard Administrator
Identification
This section expands whenever you access the System Page the first time.
System page
117
NOTE: For H3C switches, the following attributes cannot be discovered through HP SIM discovery
and identification:
•
Serial Number
•
UUID
NOTE:
This field is blank for a Windows 2008 and Windows 2003 based CMS's.
•
Operating System Name
•
Operating System Type
•
Vendor
Table 6 Identification section
Field
Description
Address
The IP (including IPV6) address discovered for the system.
Preferred System Name
The name shown for the system. When available, it defaults
to the host name from DNS. You can override this setting
through the Edit System Properties link under the Tools &
Links tab.
Network Name
The fully qualified DNS name, if available. Reverse DNS
lookups by IP address must be enabled and match a
forward lookup.
UUID
A unique identifier from the agent or other instrumentation
on the system.
Serial Number
The serial number of the system.
Product number
The product Number of the system
This appears for Virtual Connect switches
Orphan systems
An orphan system is a system detected by HP SIM that has had its IP address and name reallocated
to another system. Occasionally, this reallocation can happen through simultaneous DHCP address
assignment changes and a system rename. Other causes can include a move of the operating
system from one blade to another through different virtualization mechanisms such as a
physical-to-physical system move or replacement of a system board that has not be configured the
same as the original system board.
Table 7 Orphan system names
Possible system names
118
Description
<serialNumber>
Where <serialNumber> is replaced with the serial number
of the system.
<serialNumber>-<devKey>-<oldName>
Where <serialNumber> is replaced with the serial number
of the system, <devKey> is replaced with the devKey on
the system, and oldName> is replaced with the old system
name.
<devKey>
Where <devKey> is replaced with the devKey on the
system.
Screens and product layout
Firmware and Software Revision
NOTE: For an MSA having dual controllers, this section will always include information for both
of the controllers.
Table 8 Firmware and Software Revision section
Field
Description
Executable
The name of the executable.
Manufacturer
The vendor of the installed firmware.
Version
The version string for the installed firmware. The version
can include major, minor, revision, and build information.
Build Number
The build number of the software.
State
The client application uses the InstallState from the bundle,
and the InstallSoftwareIdentity association from the bundle's
components to determine which Software Identity objects
in the bundle are installed and which are missing. This
field can contain the values: Installed, Partial, or None.
Classification
The classification field provides a means to describe the
software. For example, the field might contain Firmware
or Application Software among other descriptive strings.
Firmware Category
The firmware category field displays values related to the
category of software, such as NIC driver, NIC firmware,
System Management Software, and so on.
Product Description
Table 9 Product description section
Field
Description
Product ID
The identification number that, when added to the serial
number of the server, enables HP Support to uniquely
identify HP systems
System Type
The basic system type returned from identification
System Subtype
The system subtype returned from identification.
If the system is a T or F series storage server, this will be
set to Storage.
If the system is an HP Enclosure Manager, which is
identified as a management processor, this will be set to
HP Enclosure Manager.
Product Model
The product model (name) defined by the manufacturer
Hardware Description
The description of the hardware obtained from the Edit
System Properties page
OS Name
The operating system name for the system used for filtering
OS For Tool Filtering
The short name of the operating system used for tool filter
definition files
OS Description
The detailed description of the operating system
OS Version
The numerical representation of the operating system
version
System page
119
Table 9 Product description section (continued)
Field
Management Protocols
Description
The management protocols that have responded when
attempting to identify the system.
NOTE: If more protocols are expected, verify the
credentials configured on the System Protocol Settings
page.
Server Role
The user-specified server role from the ProLiant agents that
can be set from the HP SMH
Comments
The user-specified comments from the SNMP or other agents
Current Running Applications
A list of applications running on the system
Trusted Platform Module
This informs you of TPM status and can be set as absent,
disabled, enabled, not present, or present but disabled.
Embedded Remote Support
Displays if embedded remote support is enabled on the
iLO
HP Insight Control power management
Table 10 HP Insight Control power management section
Field
Description
System Requires Redundant Power
Indicates if the system is intended to have redundant power
supplied to it.
Height
The height of the system occupied in a rack (in U slots).
Maximum Power Consumption (Watts)
The possible maximum power consumption of the system
in Watts.
Minimum Power (Watts)
The minimum power consumption of the system when
powered on in Watts.
Peak Observed Power Consumption (Watts)
The peak observed power consumption of the device
throughout all collected power history.
To configure/edit the System Properties of the system, click Configure.
Contact Information
Table 11 Contact Information section
Field
Description
Location
A user-specified field from the agents for the physical
location of the system
Contact
The user-specified contact of the system from the agents
Many fields in the Contact Information and Product Description sections can be overridden locally
on the CMS through the Edit System Properties pages. For more information, see “Editing system
properties for a single system” (page 301).
120 Screens and product layout
Entitlement Information
Table 12 Entitlement Information section
Field
Description
Start Date
The starting date of the contract or warranty
End Date
The end date of the contract or warranty
Type
The contract type, if a service contract exists
Status
The current contract or warranty status
Last Collection
The date that contract and warranty data was last collected
Asset Information
This section includes Asset Number, which is the asset number of the system.
Management Processor
This section appears only if a management processor is available.
Table 13 Management Processor section
Field
Description
Name
The display name (Preferred Name) of the management
processor used to manage the system
Address
The IP address of the management processor used to
manage the system
Management Processor Homepage
This link takes you to the home page of the management
processor
Model
The model name of the management processor for this
system
Host Server
Table 14 Host server section
Field
Description
Name
The host server name with a link to the host server's System
page
Slot
The slot number of the host server
Model
The product model of the host server
Storage Server
This section includes the following information for servers that have a storage server associated:
Table 15 Storage Server section
Field
Description
Name
The storage server name with a link to the storage server
System Page
Slot
The slot number of the storage server System Page
Model
The product model of the storage server
System page
121
Associations
This section includes:
Table 16 Associations section
Field
Description
Enclosure Name
The name of the enclosure, if the system is in an enclosure
Rack Name
The name of the rack to which the PDU is associated, if the
enclosure is in a rack that can be discovered
Rack Manager name
Name of the rack manager which manages the PDU
Slot
The slot number where the system is positioned within the
enclosure
Bay
The bay where the system is positioned within the enclosure
This appears Virtual Connect switches
Server Dimensions
The dimensions in millimeters of the system
Switch Dimensions
The dimensions in millimeters of the system
Virtual Connect Domain
The name shown for the VCD. When available, it defaults
to the host name from DNS
Role
Table 17 Role section
Field
Description
Role
Role of the management processor
Running status
The running status of the switch
This appears for Virtual Connect switches
Virtual Connect Domain
Table 18 Virtual Connect Domain section
Field
122
Description
Virtual Connect Domain Name
The name shown for the system, and when available,
defaults to the host name from DNS
Primary Virtual Connect Ethernet Module
Name of IP address of the Virtual Connect switch
Configuration Status
Gives the status of the domain
Firmware Version
Firmware version of the Virtual Connect switch
Primary Enclosure
Enclosure in which the Primary Virtual Connect Ethernet
Module is configured
Remote Enclosures
Lists remote enclosures that are present
Interconnect Bay
Bay where the Virtual Connect switch is present
Screens and product layout
Location
Table 19 Location section
Field
Description
Height
Height of the server Rack or enclosure (in "U" units)
Position
Position of the server enclosure (in "U" units)
System tab for blade servers
Table 20 Identification section
Field
Description
Address
The IP (including IPv6) address discovered for the system.
Preferred System Name
The name shown for the system. When available, it defaults
to the host name from DNS. You can override this setting
through the Edit System Properties link under the Tools &
Links tab.
Network Name
The fully qualified DNS name, if available. Reverse DNS
lookups by IP address must be enabled and match a
forward lookup.
UUID
A unique identifier from the agent or other instrumentation
on the system.
Serial Number
The serial number of the system.
Product number
The product Number of the system
This appears for Virtual Connect switches
Role
This section indicates whether the Onboard Administrator is active or inactive and appears on
Onboard Administrator system page.
Virtual Connect Domains
This option displays the following information of the Virtual Connect Domain and appears on a
Virtual connect domain system page:
•
Virtual Connect Domain Name
•
Primary Virtual Connect Ethernet Module
•
Configuration Status
•
Firmware Version
•
Rack
•
Enclosure
•
Interconnect Bay
System page
123
To access the All Virtual Connect Domain discovered in your system, go to the System and Event
Collections panel, click Shared→Systems by Type→All Virtual Connect Domains. The All Virtual
Connect Domains option is visible in the left navigation pane when the Onboard Administrator is
discovered.
NOTE:
Switch.
124
There is a different system page for Virtual Connect Domain and Master Virtual Connect
Screens and product layout
System tab for management processors
On the System tab, a status icon indicates the overall health status stored in the database. If a
system is suspended, a disabled icon appears in place of the hardware status icon.
The Quick Launch hyperlink links to a short list of frequently used tools. Place your cursor over the
link to expand the menu and view the tools available for selected systems. Selecting a tool from
this list bypasses the target verification page of the Task Wizard. You cannot schedule tools
launched from this menu. Customize this menu by clicking the Customize link in the Quick Launch
menu.
NOTE:
Expand the following sections by clicking
. Collapse them by clicking
.
System Status
Table 21 System status section
Field
Description
Health Status
The overall status for a system. It is obtained from WBEM,
SNMP, Ping, Out-of-Band (OOB), and the HTTP protocols
with the most critical status displayed. WBEM, SNMP, and
OOB status can have sub statuses that are used for the
calculation of their upper status. A ping (ICMP or TCP
reachable check) is always made. The link for Health Status
will not be present if it has sub status. Otherwise, click the
Health Status link to access the HP SMH, if it is present. If
HP SMH is not present, the link accesses the Property Page
Status page. If no option is available, the Health Status
link is not present. When the WBEM status is expanded,
the statuses are sorted alphabetically and displayed
vertically. If a status source does not have a value, that
status does not appear. When you place your cursor over
a status text, a flyover appears displaying information
explaining the status. When the status is Disabled, the
system could be off-line or unreachable or the system is
suspended from monitoring. For a cluster, the rollup status
of all its components appears.
Contract and Warranty Status
The Contract and Warranty Status is available when you
have a Windows CMS, and the HP Insight Remote Support
Pack is installed. You can view Contract and Warranty
status updates for HP systems that have contract and
warranty data collection enabled. Click the Contract and
Warranty Status icon to view the Contract and Warranty
Details page for the system.
Aggregate Event Status
The Aggregate Event Status is a summary of uncleared
events. This status is updated when an event is added,
updated, or removed. To view the System Page Events tab
for a system, click the Aggregate Event Status icon.
More Information
This section provides more detailed information about the system and lists available information
tools. Possible links include:
•
HP System Management Homepage
•
Property Page
•
Partition Manager View
•
Virtual Manager Host View
•
BladeSystem XXXXX Onboard Administrator
System page
125
•
Superdome 2 Onboard Administrator
•
HP iLO 4
Identification
Table 22 Identification section
Field
Description
Address
The IP (including IPV6) address discovered for the system.
Preferred System Name
The name shown for the system. When available, it defaults
to the host name from DNS. You can override this setting
through the Edit System Properties link under the Tools &
Links tab.
Network Name
The fully qualified DNS name, if available. Reverse DNS
lookups by IP address must be enabled and match a
forward lookup.
UUID
A unique identifier from the agent or other instrumentation
on the system.
Serial Number
The serial number of the system.
Product number
The product Number of the system
This appears for Onboard Administrator
Address
The IP address of the discovered system.
Preferred system name
The name shown for the system. When available, it defaults
to the host name from DNS. You can override this setting
through the Edit System Properties link under the Tools &
Links tab.
Product Description
Table 23 Product description section
Field
Description
System Type
The basic system type returned from identification
Product Model
The product model (name) defined by the manufacturer
Hardware Description
The description of the hardware obtained from the Edit
System Properties page
Management Protocols
The management protocols that have responded when
attempting to identify the system.
NOTE: If more protocols are expected, verify the
credentials configured on the System Protocol Settings
page.
System Subtype
The system subtype returned from identification
This appears for Onboard Administrator
OS Name
Displays embedded operating system
This appears for Onboard Administrator
OS Type
Displays embedded operating system
This appears for Onboard Administrator
OS Version
126
Screens and product layout
Displays embedded operating system version
Table 23 Product description section (continued)
Field
Description
This appears for Onboard Administrator
Embedded Remote Support
Displays if embedded remote support is enabled on the
iLO
Entitlement Information
Table 24 Entitlement Information section
Field
Description
Start Date
The starting date of the contract or warranty
End Date
The end date of the contract or warranty
Type
The contract type, if a service contract exists
Status
The current contract or warranty status
Last Collection
The date that contract and warranty data was last collected
Associations
Table 25 Associations section
Field
Description
Server name
Name of the servers that are managed by the rack
manager.
Enclosure Name
The name of the enclosure, if the system is in an enclosure
Not available for rack managers
Rack Name
The name of the rack, if the enclosure is in a rack that can
be discovered
Virtual Connect Domain
The name shown for the VCD and when available, defaults
to the host name from DNS
Not available for rack managers
Bay
The bay where the system is positioned within the enclosure
This appears for Onboard Administrator
Management Processor Dimension
The dimensions in millimeters of the system
This appears for Onboard Administrator
Role
Table 26 Role section
Field
Role
Description
Role of the management processor or rack manager
Role of the management processor
This appears for Onboard Administrator
System page
127
Managed Systems
Table 27 Managed systems section
Field
Description
Server Name
The server name obtained during discovery and
identification.
Model
The model number of the system.
System tab for clusters
Based on the type of cluster provider and the version of cluster providers, not all properties are
available at all times. If a property does not have a value, the property does not appear on this
page. This page is for all clusters except for MSCS clusters. They are monitored using Cluster
Monitor.
The Quick Launch hyperlink links to a short list of frequently used tools. Place your cursor over the
link to expand the menu and view the tools available for selected systems. Selecting a tool from
this list bypasses the target verification page of the Task Wizard. You cannot schedule tools
launched from this menu. Customize this menu by clicking the Customize link in the Quick Launch
menu.
Health Status
Each link for a cluster member under Health Status links to the System Page of a cluster member.
The cluster status is a combination of cluster member statuses in the cluster and cluster status itself.
The most critical status is shown.
Identification
•
Address
The IP address of the cluster.
•
Preferred System Name
The name shown for the system. When available, it defaults to the host name from DNS. You
can override this through the Edit System Properties link under the Tools & Links tab.
•
Network Name
The fully qualified DNS name. Reverse DNS lookups by IP address must be enabled and match
a forward lookup.
Product Description
NOTE:
•
Expand this section by clicking
. Collapse it by clicking
Cluster Name
The name of the cluster
•
System Type
The basic system type returned from identification.
•
Cluster Type
The basic cluster type returned from identification
128
Screens and product layout
.
System tab for a complex
A complex is a container type system and contains nPartitions. Additional links are available on
the System Page to access information when you select a complex system. Included are areas that
are unique to a complex.
The Quick Launch hyperlink links to a short list of frequently used tools. Place your cursor over the
link to expand the menu and view the tools available for selected systems. Selecting a tool from
this list bypasses the target verification page of the Task Wizard. You cannot schedule tools
launched from this menu. Customize this menu by clicking the Customize link in the Quick Launch
menu.
Health Status
Each link for a partition member under Health Status links to the System Page of a partition. For a
Superdome 2 complex, the health status of a complex is a combination of all the health statuses
of each partition included in the complex. For a Superdome 2 complex, the health status is
determined from the status of all partitions and the status of the complex. The status of the complex
is determined from the OOB status. The most critical status is displayed.
More Information
This section provides more detailed information about the system and lists available information
tools. Possible links include:
Superdome 2 Onboard Administrator
This link takes you to the Onboard Administrator page.
Product Description
NOTE:
Expand this section by clicking
. Collapse it by clicking
.
This section includes:
•
Complex Name
The name of the complex returned from identification
•
Complex Type
The HP SIM managed system type
•
Complex Subtype
This field describes the additional roles of the complex.
•
Product Name
The product name as defined by the manufacturer
•
Serial Number
The serial number of the complex returned from identification
•
Product Number - Current
•
Product Number - Original
•
Complex Profile Revision
•
Active Service Processor Location
System page
129
Summary of Components
For a complex participating in iCOD:
•
Computer Cabinets
•
I/O Cabinets
The Superdome's hardware box that contains the cells, GSP, internal I/O chassis, I/O fans,
cabinet fans, and power supplies.
•
nPartitions
The partition of an HP server, comprising a group of cells (containing CPUs and memory) and
I/O chassis (containing I/O systems)
•
Authorized iCAP Cells
•
Unlicensed iCAP Cells
•
Authorized iCAP Processors
•
Unlicensed/iCOD Processors
•
DIMMs
The DIMM memory chips installed
•
Licensed Memory (GB)
•
Unlicensed/ICOD Memory (GB)
•
Chassis
•
I/O Cards
•
ICOD
•
ICOD Balance
•
Enclosures
•
IOX Enclosures
•
Blades
•
Cores
•
Memory (MB)
•
I/O Chassis
For a Complex Not Participating in iCOD:
•
Computer Cabinets
•
I/O Cabinets
•
nPartitions
•
Cells
•
CPUs
•
DIMMs
•
Memory (GB)
130 Screens and product layout
•
I/O Chassis
•
I/O Cards
•
iCOD
System tab for partitions
The System Page for a partition follows the same layout as a server System Page. However, it is
extended to include unique information that applies to partitions only.
The Quick Launch hyperlink links to a short list of frequently used tools. Place your cursor over the
link to expand the menu and view the tools available for selected systems. Selecting a tool from
this list bypasses the target verification page of the Task Wizard. You cannot schedule tools
launched from this menu. Customize this menu by clicking the Customize link in the Quick Launch
menu.
The following sections include only the unique information for a partition.
Identification
The Identification section expands when you access the System Page for the first time. The items
available under this section include:
•
nPartition Name
•
nPartition Number
•
Host Name
Product Description
NOTE:
Expand this section by clicking
. Collapse it by clicking
.
This section includes:
•
CPU Architecture
•
Cell Compatibility
•
Firmware Revision
•
Primary Boot Path
•
HA Alternate Boot Path
•
Alternate Boot Path
Summary of Components
This section includes:
•
Active Cells
•
Inactive Cells
•
Active Processors
•
Inactive Processors
•
Number of Licensed Processors (for partitions that participate in Instant Capacity)
•
DIMMs
System page
131
•
Memory (GB)
•
I/O Chassis
•
I/O Cards
Associations
•
Complex Name
•
Managed By
System tab for storage host
A storage host is a server, desktop, or workstation connected by an HBA to a SAN. Additional
links are available on the System Page to access detailed information when a storage host is
selected. Included are areas that are unique to storage hosts. HP SIM displays data supplied by
each HBA SMI-S provider. If an HBA SMI-S provider does not supply data for a property, the
property does not appear on this page.
NOTE: To get Storage Port Controller and LUNs information on the System Page, you must install
FC HBA providers (providers which implements Storage Networking Industry Association Fiber
Channel Host Bus Adapter (SNIA FC HBA) profile) on the host where HBA resides. Without these
providers cannot obtain Storage Port Controller and LUNs information even though it is available
in other management applications like HP SMH. If you install HP Insight Management WBEM
Providers for Windows Server 2003 or Windows Server 2008 on a Windows host, then only
Storage Port Controller information is available. You cannot obtain LUNs information with HP
Insight Management WBEM Providers for Windows Server 2003 or Windows Server 2008 x64
Editions. There are no providers available for an HP UX host to obtain LUNs information.
The Host Bus Adapters section shows the date, time, and duration of the last data collection task.
To update the data, click the Last Update link, and schedule or run a Data Collection task.
The Quick Launch hyperlink links to a short list of frequently used tools. Place your cursor over the
link to expand the menu and view the tools available for selected systems. Selecting a tool from
this list bypasses the target verification page of the Task Wizard. You cannot schedule tools
launched from this menu. Customize this menu by clicking the Customize link in the Quick Launch
menu.
Product Description
NOTE:
Expand this section by clicking
. Collapse it by clicking
.
In addition to the Product Description information on the System tab for storage host, this section
can include:
System Subtype
Storage systems use the following subtypes:
•
Storage. A system identified as part of the storage infrastructure
•
SMI. A system discovered through an SMI-S provider
Host Bus Adapters
NOTE:
132
Expand this section by clicking
Screens and product layout
. Collapse it by clicking
.
This section lists the installed Fibre Channel HBAs.
•
Element Name
The name of the HBA.
•
WWN
The node world wide name of the HBA.
•
Status
The HBA WBEM operational status.
NOTE:
Click
to view HBA property and port information.
Properties
NOTE:
•
Expand this section by clicking
. Collapse it by clicking
.
Product Name
The product name for the HBA (for example, a model number)
•
Product Vendor
The HBA vendor
•
Product Identifying Number
A unique identifier for the HBA (for example, a serial number)
•
Product Version
The HBA product version
•
Driver Version
The installed HBA driver version
•
Driver Manufacturer
The manufacturer of the HBA driver
•
Firmware Version
The installed HBA firmware version
•
Firmware Manufacturer
The HBA firmware manufacturer
•
BIOS/FCode Version
The installed BIOS/FCode version
•
BIOS/FCode Manufacturer
The BIOS/FCode manufacturer
System page
133
Ports
NOTE:
•
Expand this section by clicking
. Collapse it by clicking
.
. Collapse it by clicking
.
Element Name
The port number.
•
WWN
The port's World Wide Name
•
Port Type
The port type
•
Status
The port's WBEM operational status
LUNs
NOTE:
Expand this section by clicking
This section lists the LUNs in use by the host.
•
LUN Name
The name of a LUN in use by the selected host.
•
LUN Number
The number by which the LUN (as seen through this port) is known to the storage host.
•
Storage Device
The name of the storage device that contains the listed LUN. Click the storage device name
to view the storage device System Page.
A link from a LUN to a storage device appears in this column only if the LUN meets the
following conditions:
◦
It is reported by the SMI-S provider of the storage array where the LUN resides.
◦
It has the same Name property used by the HBA SMI-S provider.
If these conditions are not met but the HBA SMI-S provider reports the LUN the LUN storage
device is listed as Unknown.
•
HBA Name
The name of the HBA that connects the host to the LUN.
•
Port WWN
The port number through which the host connects to the LUN.
•
LUN Size
The usable size of the LUN.
•
RAID Level
The LUN RAID level. RAID level information is available only if a LUN is matched up to a
volume on a storage device.
134
Screens and product layout
System tab for a storage switch
A storage switch is a Fibre Channel switch connected to a SAN. Additional links are available on
the System Page to access detailed information when a storage switch is selected. Included are
areas unique to storage switches. HP SIM displays data supplied by the switch's SMI-S provider.
If the SMI-S provider does not supply data for a property, the property does not appear on this
page.
The Ports and Status Summary sections show the date, time, and duration of the last data collection
task. To update the data, click the Last Update link and schedule or run a Data Collection task.
The Quick Launch hyperlink links to a short list of frequently used tools. Place your cursor over the
link to expand the menu and view the tools available for selected systems. Selecting a tool from
this list bypasses the target verification page of the Task Wizard. You cannot schedule tools
launched from this menu. Customize this menu by clicking the Customize link in the Quick Launch
menu.
Product Description
NOTE:
Expand this section by clicking
. Collapse it by clicking
.
In addition to the Product Description information on the System tab for servers, this section includes
the following information:
•
System Subtype
One of the following subtypes:
•
◦
Storage. A system identified as part of the storage infrastructure
◦
SMI. A system discovered through an SMI-S provider
Product Name
The product name for the switch (for example, a model number)
•
Product Vendor
The switch vendor
•
Product Identifying Number
A unique identifier for the switch (for example, a serial number)
•
Product Version
The switch product version
•
Firmware Version
The installed firmware version
•
Firmware Manufacturer
The firmware manufacturer
•
BIOS/FCode Version
The installed BIOS/FCode version
•
BIOS/FCode Manufacturer
The BIOS/FCode manufacturer
•
Management Proxies
The servers that manage the switch through a management protocol
System page
135
•
Software Version
The version of the software installed on this system
•
Software Manufacturer
The manufacturer of the software installed on this system
NOTE: Some vendors enter firmware details in the Software Version and Software Manufacturer
fields instead of the Firmware Version and Firmware Manufacturer fields. These fields might display
data about software related to the system.
Ports
NOTE:
•
Expand this section by clicking
. Collapsed it by clicking
.
Port Number
The port number
•
WWN
The port's World Wide Name
•
Port Type
The port type
•
Status
The port's WBEM operational status
Status Summary
NOTE:
Expand this section by clicking
. Collapse it by clicking
.
This section summarizes the status information in the Ports section.
•
Status
The WBEM operational status
•
Count
The number of ports with the listed status
System tab for a storage array
A storage array is a disk array that uses a Fibre Channel controller to connect to a SAN. Additional
links are available on the System Page to access information when a storage array is selected.
Included are the areas that are unique to storage arrays. HP SIM displays data supplied by the
array's SMI-S provider. If the SMI-S provider does not supply data for a particular property, the
property does not appear on this page.
The Ports, Storage Volumes, and Capacity Information sections show the date, time, and duration
of the last data collection task. To update the data, click the Last Update link, and schedule or run
a Data Collection task.
The Quick Launch hyperlink links to a short list of frequently used tools. Place your cursor over the
link to expand the menu and view the tools available for selected systems. Selecting a tool from
this list bypasses the target verification page of the Task Wizard. You cannot schedule tools
launched from this menu. Customize this menu by clicking the Customize link in the Quick Launch
menu.
136
Screens and product layout
Product Description
NOTE:
Expand this section by clicking
. Collapse it by clicking
.
In addition to the Product Description information in System tab for servers, this section can include
the following information:
•
System Subtype
Includes the following subtypes:
•
◦
Storage Device. A system as part of the storage infrastructure
◦
SMI. A system discovered through an SMI-S provider
Product Name
The product name for the array (for example, a model number)
•
Product Vendor
The storage array vendor
•
Product Identifying Number
A unique identifier for the storage array (for example, a serial number)
•
Product Version
The array product version
•
Firmware Version
The installed firmware version
•
Firmware Manufacturer
The firmware manufacturer
•
BIOS/FCode Version
The installed BIOS/FCode version
•
BIOS/FCode Manufacturer
The BIOS/FCode manufacturer
•
Management Proxies
The servers that manage the selected array through a management protocol
•
Software Version
The version of the software installed on this system
•
Software Manufacturer
The manufacturer of the software installed on this system
NOTE: Some vendors enter firmware details in the Software Version and Software Manufacturer
fields instead of the Firmware Version and Firmware Manufacturer fields. These fields might display
data about software related to the system.
Ports
NOTE:
Expand this section by clicking
. Collapse it by clicking
.
If HP SIM discovers controllers that manage this array's ports, they appear as expandable elements
in the Ports table. If no controllers were discovered, the table lists only port details.
System page
137
Controller Details
•
Element Name
The name of the controller
•
LUN Count
The number of connections made through this controller
•
Status
The controller's WBEM operational status
NOTE:
Click
to view specific port details.
Port Details
•
Element Name
The port name
•
WWN
The port's World Wide Name
•
Port Type
The port type
•
LUN Count
The number of connections made through this port
•
Status
The port's WBEM operational status
Storage Volumes
NOTE:
Expand this section by clicking
. Collapse it by clicking
.
This section lists the array's storage volumes. Storage volumes are logical volumes on an array .
•
Volume Name
The storage volume name.
•
Visible to Host(s)
The storage volume accessible to the listed hosts.
•
Block Size
The storage volume's block size in bytes.
•
Number of Blocks
The total number of blocks on the storage volume.
138
Screens and product layout
•
Total Size
The storage volume's total size.
•
RAID Level
The RAID level of the storage volume. Typically, this value is supplied by the array's SMI-S
provider. If the SMI-S provider does not supply a value, HP SIM calculates the RAID level
based on the values for Package Redundancy and Data Redundancy as follows:
Package redundancy
Data redundancy
RAID level
0
1
RAID 0
1
1
RAID 5
1
2
RAID 1
2
1
RAID 6
2
2
RAID 15/51
If the RAID value is calculated by HP SIM, an asterisk is added to the RAID value (for example
RAID 5*).
Capacity Information
NOTE:
Expand this section by clicking
. Collapse it by clicking
.
The Capacity Information table lists available capacity metrics for storage arrays in the Metric
column and the corresponding disk space value in the Size column. For each metric, the disk space
value is expressed as a percentage of the array's total capacity. The metrics in the Capacity
Information table also appear as percentages in a pie chart below the table. If a value in the table
shows an Undetermined value, the pie chart does not appear.
HP SIM discovers external LUs (a feature of External Storage XP) on XP arrays that are managed
by Command View XP Advanced Edition. When an XP array has external LUs, the Total Capacity
System page
139
value is higher than the total capacity of all of the disks in that XP array because it includes the
capacity from the external LUs.
•
Total Capacity
The total capacity of the array and it can be used in the following ways:
◦
Raw
Space configured for a specific purpose.
◦
Assigned
Space that is assigned to pools of storage that can be configured into storage volumes
(LUNs).
◦
Allocated
Space configured as storage volumes, but not connected through ports. An application
cannot access an allocated space until it is assigned to a port.
◦
Exposed
Space configured as storage volumes that is connected through ports. Applications can
access this space.
◦
RAID Overhead
Space on the array that is not directly usable because it is being used to provide
redundancy. For example, if 100 GB is allocated for a RAID 1 (mirrored) storage volume,
50 GB are directly usable (Allocated or Exposed), and 50 GB is RAID Overhead to
provide the mirrored copy of the data.
◦
Other
Space not accounted for by previously listed categories. Other space is typically used
for metadata.
System tab for a tape library
A tape library is a tape drive connected to a SAN. Additional links are available on the System
Page to access information when a tape library is selected. Included here are areas that are unique
to tape libraries. HP SIM displays data supplied by the tape library's SMI-S provider. If the SMI-S
provider does not supply data for a particular property, the property does not appear on this page.
The Ports, Media Access Devices, and Changer Devices sections show the date, time, and duration
of the last data collection task. To update the data, click the Last Update link, and schedule or run
a Data Collection task.
The Quick Launch hyperlink links to a short list of frequently used tools. Place your cursor over the
link to expand the menu and view the tools available for selected systems. Selecting a tool from
this list bypasses the target verification page of the Task Wizard. You cannot schedule tools
launched from this menu. Customize this menu by clicking the Customize link in the Quick Launch
menu.
Product Description
NOTE:
Expand this section by clicking
140 Screens and product layout
. Collapse it by clicking
.
In addition to the Product Description information on the System tab for servers, this section includes
the following information:
•
System Subtype
The following subtypes:
•
◦
Storage. A system identified as part of the storage infrastructure
◦
SMI. A system discovered through an SMI-S provider
Product Name
The product name for the tape library
•
Product Vendor
The tape library vendor
•
Product Identifying Number
A unique identifier for the tape library
•
Product Version
The tape library product version
•
Firmware Version
The installed firmware version
•
Firmware Manufacturer
The firmware manufacturer
•
BIOS/FCode Version
The installed BIOS/FCode version
•
BIOS/FCode Manufacturer
The BIOS/FCode manufacturer
•
Management Proxies
The servers that manage the selected tape library through a management protocol
•
Software Version
The version of the software installed on this system
•
Software Manufacturer
The manufacturer of the software installed on this system
NOTE: Some vendors enter firmware details in the Software Version and Software Manufacturer
fields instead of the Firmware Version and Firmware Manufacturer fields. These fields might display
data about any software related to the system.
Ports
NOTE:
Expand this section by clicking
. Collapse it by clicking
.
System page
141
This section lists the tape library's Fibre Channel ports.
•
Element Name
A user-friendly name for the port
•
WWN
The port's World Wide Name
•
Port Type
The port type
•
Status
The port's WBEM operational status
Media Access Devices
NOTE:
Expand this section by clicking
. Collapse it by clicking
.
This section lists the following information about the tape library's storage media:
•
Name
The name of the storage media
•
Status
The media access device's WBEM operational status
•
Firmware Version
The installed firmware version
Changer Devices
NOTE:
This section can be expanded by clicking
or collapsed by clicking
.
This section lists the tape library's changer devices.
•
Name
The name of the changer device
•
Status
The changer device's WBEM operational status
•
Firmware Version
The installed firmware version
Tools & Links tab
The system links you can view depend on the Discovery configuration, the correct installation of
agents and protocols, and the polling tasks that interrogate the system.
NOTE: Depending on the DNS configurations, you might need to use the IP address or a FQDN
name to make the links work appropriately.
142
Screens and product layout
Management Pages
This section includes links that are provided by the HTTP Web Management on the system. These
links are for system management and status. If the system does not have Insight Management
Agent, this section does not appear. Some of the available links include the following:
•
HP Version Control Agent
•
HP Version Control Repository Manager
•
Insight Management Advisor
•
HP Intelligent PDU Management
Web Application Pages
This section includes a list of web applications hosted by the system. Some of the available links
include:
•
VMware Management Interface
•
Default Web Server
•
HP SIM
•
Integrated Lights-Out 4
•
HP Integrated Lights-Out
HP Systems Insight Manager Pages
This section contains links that are generated by HP SIM. Available links include:
•
The Data Collection Report link displays the data collection report for the system in a separate
report results window.
NOTE: The storage tables in the HP SIM data collection reports are not populated with data
because the HP SIM SMI-S data collection is disabled.
NOTE:
The data collection report is not available for clusters.
•
The System Protocol Settings link points to the Protocol Settings page, where you can set
protocol settings for this system.
•
The System Credentials link points to the System Credentials page, where you can view or
edit system credentials or create protocol-independent and protocol-specific credentials.
•
The Configure Automatic Discovery Settings of VM Guest(s) launches the Configure Automatic
Discovery Settings of VM Guest(s) page. From this page, you can control the horizontal
discovery of VM guests at the system level.
•
The Edit System Properties link enables users with administrative rights to reconfigure some
system properties for a single system through its system page. This link is not available if you
do not have administrative rights.
•
The Suspend/Resume Monitoring link enables you to set the timer for suspending monitoring,
which enables a system to be excluded from the status polling, identification, data collection,
and automatic event handling in HP SIM. Available suspend lengths include the predetermined
increments of 5 minutes, 15 minutes, 1 hour, and 1 day. The suspend feature can be turned
on indefinitely. This link is only available to users with administrative rights.
•
The Add or Edit VME Credentials to add or edit VME credentials.
•
The WBEM Health Inclusion Status appears for ESXi systems. The link takes you to the WBEM
Health Inclusion Status page that lists the status information for the sub-components of the
system.
System page
143
Essentials tab
The Essentials tab is available on the System Page of systems that might support other HP SIM
partner applications. This tab provides a description of available software and a link to the HP
website where you can get further details. Only administrative rights and operator rights users can
view the Essentials tab.
When new information is available on the Essentials tab, the tab is highlighted with an Informational
icon: . After you view the Essentials tab, the icon is removed until new information is available.
Performance tab for blades
NOTE: The HP Insight Control virtual machine management VM Performance tab is available
only when virtual machine management is installed and the selected host is registered with virtual
machine management and virtual machine management supports performance data for the selected
virtualization layer.
The VM Performance tab displays information about selected blade performance, and is displayed
for bare metal blades without any data. The VM Performance tab includes the following information:
•
Updated: (Timestamp). Automatically refreshes and displays the last updated timestamp for
the CMS.
•
Processor
•
•
•
◦
Index. Displays the processor index number.
◦
Type. Displays the processor type.
◦
Utilization. Displays the processor utilization.
Logical Disk
◦
Name. Displays the name of the logical disk.
◦
Size (MB). Displays the size of the logical disk in megabytes.
◦
Usage (%). Displays the percentage of disk space used.
Physical Memory
◦
Size (MB). Displays the size of the physical memory in megabytes.
◦
Free (MB). Displays the size of free physical memory in megabytes.
◦
Paging Size (MB). Displays the paging size in megabytes.
◦
Paging Free (MB). Displays the amount of free paging in megabytes.
Server Fan. Displays for all p-Class and e-Class blades.
◦
Index. Displays the index number.
◦
Locale. Displays the locale.
◦
Redundant Partner. Displays the number of the redundant partner.
◦
Speed. Displays the status of the server fan.
◦
Condition. Displays the condition of the server fan.
◦
Hot Plug. Displays the type of hot plug.
144 Screens and product layout
•
•
Temperature
◦
Index. Displays the index number.
◦
Locale. Displays the locale.
◦
Celsius (C). Displays the temperature in Celsius.
◦
Threshold (C). Displays the threshold number.
◦
Condition. Displays the condition status.
◦
Threshold Type. Displays the threshold type status.
Performance Management
NOTE: if the system is licensed for performance management, this section displays the
performance management links. Otherwise, this section displays Learn about performance
management which is a link to the HP Insight Control performance management home page.
Port mapping tab for blades
The PortMapping tab displays only for c-Class blades and switches.
The PortMapping tab includes the following information:
•
Updated: (Timestamp) link Displays the CMS time.
•
For blades:
•
•
◦
Mezzanine Slot. Displays the Mezzanine slot number.
◦
Mezzanine Device. Displays the Mezzanine device name or No card present.
◦
Mezzanine Device port. Displays the Mezzanine port name or number.
◦
Port Status. Displays the status of the port.
◦
Interconnect Bay. Displays the bay number.
◦
Interconnect Bay Port. Displays the bay port number.
◦
Device ID. Displays the device identification number.
◦
O.S. Interface Name. Displays the name of the network interface in the operating system.
For switches:
◦
Interconnect Bay Port. Displays the bay port number.
◦
Port Status. Indicates the status of the port.
◦
Server Bay. Displays the server bay.
◦
Mezzanine Port. Displays the Mezzanine port number.
For more details on the switch port mapping for this system, click here to access the Onboard
Administrator. Click Onboard Administrator to display the Onboard Administrator Home
page.
Managing contacts
The Manage Contacts section includes a table listing customer contact information that has been
set. The table includes Customer Name, Phone, and Email Address. You can also create, edit, or
delete contact information from this section. Select the checkbox in the table heading to select all
System page
145
contacts, or select individual contacts by selecting the checkbox next to the contact name. You can
sort the table by clicking a field in the table heading.
Related information
Managing site information
The Manage Sites section includes at table listing all site names that have been set. Select the
checkbox in the table heading to select all sites, or select individual sites by selecting the checkbox
next to the site name. You can sort the table by clicking the Site Name heading.
Related information
WBEM-based tools
Several WBEM-based tools are available in HP SIM, including the following:
•
Property pages
•
System Fault Management
If System Fault Management is not installed, HP SIM cannot recognize WBEM indications.
•
WBEM providers
HP SIM Property pages
Use Property pages to view WBEM properties on remote target systems (HP-UX, HP-UX IPF, Linux
IPF, Linux x86, Windows, and Dec Alpha). OpenWBEM is not supported.
The WBEM name and password pairs entered under Options→Protocol Settings→Global Protocol
Settings control the amount of data that appears on the Property pages. If the root name and
password pair are not available, many properties are omitted because target system providers
require root access.
You can access Property pages in the following ways:
•
From the System Page on the System tab, click Properties. The Property pages appear for the
target system.
•
Select Tools→System Information→Properties, select the target system, and click Run now.
The Property pages display for the target system.
The Property pages open in a new window if launched from the Systems Page or from the Tools
& Links menu. The Property pages include three tabs:
146
•
Identity. Displays WBEM properties that help describe the target system including location,
local time, operating system characteristics, and owner information. The computer system
status is based on the status returned from the WBEM Computer System provider.
•
Status. Displays WBEM properties that help determine the status of the target system, such as
determining memory status and process status. Depending on the target system installation of
WBEM, you might be able to determine status on all major computer subsystems. A status
icon for each component appears next to each status property. Computer system status is
determined by information collected through the WBEM protocol and the information provided
by the WMI provider.
Screens and product layout
NOTE: When you click the FC HBA link on the Property Pages Status tab, you will receive
an error message. Even though FC control is not present on the system, the FC HBA hyperlink
might appear on the Status tab. For an FC HBA, HP SIM cannot anticipate if there are instances
present and might display this link. If there are instances present, the CIM Client connection
might have timed out.
•
Configuration. Displays an inventory of the target system based on WBEM properties, including
operating system information, but possibly information about CPUs, disk drives, file systems,
motherboards, software installations, and networks.
NOTE:
NOTE:
The date and time displayed on Property pages indicates the time on the target system.
OpenWBEM is not supported.
System Fault Management overview
System Fault Management (SFM) is a suite of advanced hardware fault technologies that protects
hardware from failures and reports predictive information and corrective action events. SFM is
available for HP 9000 systems running v2 update 2, and Integrity servers running HP-UX 11i v2
update 2.
SFM integrates into HP SIM using industry-standard WBEM instrumentation.
Integration among standards-compliant system management applications, as with HP SIM, provides
a holistic and comprehensive view of HP 9000 system and HP Integrity server health.
SFM uses industry standard DMTF WBEM to provide advanced system level monitoring capabilities
to protect hardware against failures that might interrupt system operation.
SFM allows for configuration of notification thresholds for reporting predictive information and
corrective action events. Configurable thresholds enable system administrators to customize
notifications to match availability service level.
SFM includes providers to gather and model information and deliver it to the network management
application through an industry standard interface.
The CPU Instance Provider gathers information about the central processors in an HP 9000 server.
The Memory Instance Provider gathers information about the memory configuration of an HP 9000
server.
The EMS Wrapper Provider translates hardware events from EMS hardware monitors into a form
that is compatible with WBEM.
SFM is available in HP SIM by selecting a system with SFM installed and selecting Tools→System
Information→System Page.
See http://h20293.www2.hp.com/portal/swdepot/ displayInstallInfo.do?
productNumber=SysFaultMgmt&jumpid=reg_R1002_USEN for additional information about SFM.
WBEM Management Providers overview
Use HP WBEM Management Providers to remotely monitor system configuration and status.
Management Providers report information about the system they are used on. Information is provided
using WBEM industry standard protocol. A CMS using HP SIM gathers, organizes, and displays
the information in reports enabling you to monitor system use and troubleshoot problems.
The management provider package contains a set of provider modules that plug in to the HP
WBEM Services package. The modules extend the basic functions of the HP WBEM Services
package by providing additional information about the hardware and operating system.
WBEM-based tools
147
The provider package can supply the following categories of information in response to WBEM
queries. For more information see the HP WBEM Provider Data Sheets available separately.
•
Power supplies: Name, ID, description, status, and availability
•
Disk SMART sensors: System and state (online, failed/asserted, or unknown)
•
Disk drives: ID, capabilities, size, and block size
•
Disk partitions, logical systems, and logical disks: ID, bootable, and type
•
Physical memory: Description, bank label, capacity, and memory type
•
Physical memory statistical information: Single-bit errors, double-bit errors, and predictive
failure indicator
•
Network adapters: Address, speed, maximum speed, duplex indicator, and count of octets
transmitted and received
•
PCI systems: ID, vendor, grant time, and latency
•
Physical media: Name, hot swap capability, capacity, manufacturer, model, serial number,
version, and other information
•
SCSI controllers: ID, name, description, and protocol
HP WBEM Management Providers are available from the Linux link at http://www.software.hp.com.
WBEM providers for other HP equipment and operating systems are also available separately.
WBEM is a replacement for the SNMP network management protocol. WBEM providers perform
a similar role to SNMP agents of publishing information about a managed system. HP Integrity
servers can also be remotely managed using the HP SNMP Agents, which are available separately
from http://www.software.hp.com.
For additional information about WBEM Providers for Linux, see http://h71028.www7.hp.com/
enterprise/cache/13219-0-0-225-121.html.
Process Resource Manager (HP PRM)
Process Resource Manager (HP PRM) enables you to focus the appropriate amount of system
resources exactly where you need them. This powerful resource management tool runs as in addition
to HP-UX. When PRM is enabled, groups of users or applications are guaranteed a specified
portion of the total system CPU processing cycles, of the available real memory resources, and of
the disk bandwidth to logical volume-managed (LVM) systems.
HP PRM is a resource management tool used to control the amount of resources that processes use
during peak system load (at 100% CPU, 100% memory, or 100% disk bandwidth utilization).
PRM can guarantee a minimum allocation of system resources available to a group of processes
through the use of PRM groups.
An HP PRM group is a collection of users and applications that are joined together and assigned
certain amounts of CPU, memory, and disk bandwidth. There are two types of PRM groups:
•
FSS PRM groups
An FSS PRM group is a traditional PRM group, whose CPU entitlement is specified in shares.
This group uses the Fair Share Scheduler (FSS) in the HP-UX kernel within the system's default
processor set (PSET).
•
PSET PRM groups
A PSET PRM group is a PRM group whose CPU entitlement is specified by assigning it a subset
of the system's processors (PSET). Processes in a PSET have equal access to CPU cycles on
their assigned CPUs through the HP-UX standard scheduler.
148
Screens and product layout
Reasons to use PRM
•
Improve the response time for critical users and applications.
•
Set and manage user expectations for performance.
•
Allocate shared servers based on budgeting.
•
Ensure that an application package in a Serviceguard cluster has sufficient resources on an
active standby system in the event of a failover.
•
Ensure that critical users or applications have sufficient CPU, memory, and disk bandwidth
resources.
Users who at times run critical applications might at other times engage in relatively trivial
tasks. These trivial tasks can compete in the users' PRM group with critical applications for
available CPU and real memory. For this reason, it is often useful to separate applications
into different PRM groups or create alternate groups for a user. You can assign a critical
application its own PRM group to ensure that the application gets the needed share of
resources.
•
Restrict the CPU, real memory, and disk bandwidth resources available to relatively low-priority
users and applications during times of heavy demand.
For example, mail readers can consume significant disk bandwidth when users first come into
work or return from lunch. Therefore, you might want to assign a mail application to a PRM
group with small resource allocations and restrict the amount of resources mail can use during
such times of heavy demand on the system.
•
Monitor resource consumption by users or applications.
Assigning a group of users or applications to separate PRM groups can be a good way to
track the resources they are using.
Accessing Process Resource Manager from HP SIM
To access PRM:
1. From HP SIM, select Optimize→Process Resource Manager.
2. Choose from the following options:
•
Display Resource Usage
•
List Resource Availability
If the system has the PRMSIMTools bundle installed, the available options are:
3.
•
Monitor PRM Groups
•
Configure PRM Groups
•
Display Resource Usage
•
List Resource Availability
Go to: http://www.hp.com/go/prm for more information about PRM.
Managing SSH keys
The SSH Keys feature enables you to view and manage the public SSH keys, stored in the
known_hosts file, from the CMS. SSH keys enable the CMS and a managed system to authenticate
a secure connection.
WBEM-based tools
149
HP SIM provides the following SSH key configuration options:
•
Select secure shell public keys security level
Select Options→Security→Credentials→Trusted Systems.
•
Importing SSH keys
Select Options→Security→Credentials→Trusted Systems, select the SSH Key to be imported,
and then click Import.
•
ExportingSSH keys
Select Options→Security→Credentials→Trusted Systems, select the SSH Key to be exported,
and then click Export.
•
Deleting SSH keys
Select Options→Security→Credentials→Trusted Systems, select the SSH Key to be deleted,
and then click Delete.
The mxcert command enables you to manage the server certificate and the trusted certificates
in the HP SIM Keystore. With this feature, a new option is introduced ‘-k’ for initiating the
re-generation of SSH keys.
mxcert –k enables user to re-generate the SSH keys. mxcert –k creates the following SSH
key files in <SIM Installation>/config/sshtools/ directory. If the creation of SSH
keys is successful, the following message appears, SSH keys generation successful
in console.
Related information
Related information
Related procedures
Importing an SSH key
Exporting an SSH key
Deleting an SSH key
Configuring SSH key security
Related topics
Managing SSH keys
Cluster monitor
Cluster Monitor adds the ability to monitor and manage multi-node clusters. Cluster Monitor also
manages multiple cluster platforms in a heterogeneous environment.
Cluster tab
Use the Cluster Monitor Cluster tab to view the following information for MSCS clusters:
•
Status
The cluster status (Critical, Major, Minor, Normal, or Unknown). For more information about
status types, see the HP Systems Insight Manager Command Line Interface Guide, at http://
www.hp.com/go/insightmanagement/sim/docs.
•
Name
The cluster name or alias.
150
Screens and product layout
•
IP Address
The IP address of the cluster alias.
•
Quorum
The resource that maintains essential cluster data and guarantees that all nodes have access
to the most recent database changes.
By clicking a column heading, you can sort information by that column in ascending or descending
order.
The Problem Info section displays information on a cluster status other than Normal.
Nodes tab
Procedure 31 Configuring node CMX settings
1.
2.
3.
4.
5.
Select Options→Cluster Monitor→Node Resource Settings. The Cluster Monitor - Node Resource
Settings page appears.
From the Cluster list at the top of the page, select the cluster, and then select All to configure
a resource in the same way for all clusters. To set polling values for CPU utilization or disk
capacity, set the cluster choice to All.
From the Node list, select the node, and then select All to configure a resource in the same
way for all nodes in the selected cluster. As in step 2, you can set some resource attributes
only once for all nodes. As a result, you must select all clusters and nodes. For more information,
see the individual attribute descriptions for a particular resource.
To display buttons for resource-configurable parameters, select the resource from the Resource
list.
Specify resource options.
HP recommends setting the polling rate to no less than 5 minutes.
If you select All from the Cluster list and select CPU or Disk from the Resource list, you can set
polling or threshold values. If you select Polling, set the value, then select Thresholds, set the
values, and then select Polling again. The new polling values appear. Regardless of when
you click OK after setting the polling or thresholds values, these values are saved and do not
reset to the original value, which is the same when setting thresholds.
6.
Click OK to save the changes.
Related procedures
Configuring cluster resource settings
Related topics
Using Cluster Monitor
Network tab
Use the Cluster Monitor Network tab to view the following information for MSCS clusters:
•
Status
The network status (Critical, Major, Minor, Normal, Disabled, or Unknown).
•
Name
The server cluster object that carries internal communication between nodes and provides
client access to cluster resources.
•
Mask
The subnet mask associated with the network within the cluster.
Cluster monitor
151
•
State
The state of the network:
◦
Normal
The network state is online or available.
◦
Degraded
The network is partitioned.
◦
Failed
The network state is offline.
◦
Other
The network state indicates that an error occurred and the state of the network could not
be determined, or the network state is unavailable.
•
Role
The role the network name plays in the cluster: network name for the cluster, network name
for computer systems in the cluster, or network name for groups in the cluster.
•
Description
The description of the network.
To sort information, click a column heading. This sorts information by that column in ascending or
descending order.
The Problem Info section displays information on a network status other than Normal.
Related topics
Using Cluster Monitor
Cluster tab
Nodes tab
Resources tab
Resources tab
Use the Cluster Monitor Resources tab to view the following information for MSCS clusters:
•
Status
The resource status (Critical, Major, Monitor, Normal, and Unknown).
•
Name
The physical or logical entity capable of being owned by a node, brought online and taken
offline, moved between nodes, and managed as a server cluster object.
•
IP
The IP address of the cluster.
•
State
The state of the resource:
◦
Normal
The resource state is online.
◦
Degraded
The resource state is Unavailable, Offline, Online, Pending, or Offline Pending.
152
Screens and product layout
◦
Failed
The resource state is failed.
◦
Other
The resource state is undetermined.
•
Group
A collection of resources managed as a single server cluster object.
A group must have a network name and an IP address associated with it to access group
resources. A group can be owned by any node in the cluster and can be moved by users with
administrative rights for load balancing and other administrative purposes. When a failure
takes place, the entire group fails over, prompting the cluster software to transfer all group
resources and data to a different node in the cluster. The resources and data in a transferred
(failed-over) group are still accessible under the same network name and IP address, even
after they are moved to a different node.
•
OwnerNode
The node where a resource resides.
•
Type
The server cluster object used to categorize and manage resources that have similar
characteristics.
•
Drive
The disk or drive where the resource resides.
The Last update field displays the date and time of the last update of information on the tab. The
Problem Info section includes information on resource problems reported.
The Problem Info section displays information on a resource status other than Normal.
Related topics
Using Cluster Monitor
Cluster tab
Nodes tab
Managing Communications
Use the Manage Communications feature to troubleshoot communication problems between the
CMS and targeted systems. For each failed communication function, troubleshooting information
is available. You can reconfigure communication settings, launch agents, and push certificates to
target systems. This feature is available by selecting Configure→Manage Communications.
Communication status
The communication status between the CMS and the targeted systems appear in the table. Placing
your mouse over a status icon displays available information explaining the status. If you click the
status icon, the Advise and Repair section appears with the corresponding tab open. For example,
if you click a status icon in the Run Tools column, the Run Tools tab is open in the Advise and Repair
section instead of the default Identification tab.
Manage Communications table columns
Columns display the status of an operation between the CMS and it's systems.
Managing Communications
153
1
2
3
Selection. Select the
checkbox in this column to
select a system. You can
select more than one system.
Select the checkbox in the
column heading to select or
deselect all displayed
systems.
System Name. Displays
systems along with their
associations.
Identification. Includes status
information on the state of
an identification process .
Identification attempts to
determine what the system
type is, what management
protocol a system supports,
using credentials from the
Global Protocol Settings
page, and attempts to
determine the operating
system and version loaded,
along with other basic
attributes about the system.
Finally, it determines if the
system is associated with
another system. The status in
this column is a roll-up of the
status of all available
protocols. The statuses are
analyzed based on status,
system type, system
operating system, and
instrumentation options.
There are no status icons for
systems that cannot have a
status, such as complexes,
enclosures, and racks. The
identification status is
updated each time an
identification task runs.
4
Events. Indicates if the CMS
can receive events from the
target systems. This status
considers the setting of
SNMP traps and WBEM
indications.
7
For HP-UX, if sending a
package to test if the CMS
name or IP address exists on
the managed systems does
not work, then testing
sending trap destinations is
not supported.
5
6
The informational icon
appears if the Daily Check
Event Configuration task has
not run or if the system does
not support events.
Run Tools. Indicates if the
CMS can run tools locally on
target systems. For example,
HP SMH. Communication
issues in this column usually
relate to security and trust
relationships.
Version Control. Indicates
the availability of software
and firmware inventory data
for target systems. The status
is collected and stored
during data collection.
8
System Type Displays the
system type (for example,
Server or Desktop). The
Unmanaged system type
indicates systems that have
no management protocol that
HP SIM can detect, for
example, no SNMP, WBEM,
or SSH. The Unknown system
type indicates that none of the
built-in or System Type
Manager-based tasks could
identify the system. However,
some management protocol
was detected on the system.
For more information about
System Type Manager tasks,
see Managing system types.
OS Name The operating
system of the target systems.
NOTE:
Systems that do not have an IP address (enclosures, racks, clusters, complex, and storage
devices) have no status displayed.
154 Screens and product layout
Manage Communications main page buttons
1
Advise and Repair...
2
Displays the Advise and
Repair section and includes
a tabbed interface with a
tab for each functional
column (Identification,
Events, Run Tools, and
Version Control). Each tab
displays the diagnostic
results and includes
troubleshooting tips and
advise for fixing
communication problems.
For more detailed
information, see Manage
communications quick
repair.
Quick Repair...
3
Update
Runs to get an updated
communication status.
During the update process,
the status icon first changes
to the icon. As data
becomes available, the
correct status icon appears.
4
Print
Creates a printer-friendly
version of the list in a new
window. Within the window,
select File→Print from the
browser menu to print the
report. For more detailed
information, see Printing
Manage Communications
table.
Launches the Configure and
Repair Agents tool.
Configure or Repair Agents
enables you to quickly and
optimally configure systems
for manageability. For more
detailed information, see
Repairing managed system
settings.
Managing Communications
155
Manage Communications tabs
1
Identification
The Advise and Repair
Identification tab is launched
by default when you click
Advise and Repair... from
the Manage Communications
page. It is also launched
when you click a status icon
in the Identification column
in the table on the Manage
Communications page.
This tab displays
identification errors and
recommendations for fixing
the errors. Identification
communication status and
errors are generated based
on system type, the
operating system that the
managed system is running,
the availability of
management protocols on
the managed systems, and
if the protocol has a higher
weight than other protocols.
You can expand each
Causes and
Recommendations section.
2
See Identification tab.
Events
Includes detailed error
messages and
recommendations for
generating and receiving
156
Screens and product layout
3
Run Tools
Includes error messages and
recommendations for
problems that a CMS has for
executing a tool on a
managed system. These
problems often relate to
security and trust. You can
expand each Causes and
Recommendations section.
See Run Tools tab.
4
Version Control
Includes error messages and
recommendations for
problems that a CMS has
when trying to collect
software and firmware
inventory from managed
systems. You can expand
each Causes and
Recommendations section can
be expanded for each error.
See Version Control tab.
events. The event error codes
are captured and stored
during data collection,
identification, and status
polling. For HP SIM to
receive events from
managed systems, a WBEM
subscription must be
created, or the CMS IP
address must be in the
SNMP trap destination list
on the managed system. You
can expand each Causes
and Recommendations
section.
See Events tab.
Related information
Related information
Related procedures
Events tab
Manage communications quick repair
Run Tools tab
Version Control tab
Identification tab
Printing Manage Communications table
Repairing managed system settings
Updating communication statuses
Related topics
Managing Communications
Managing Communications
Managing with tasks
Systems Insight Manager enables you to manage systems and events by scheduling and executing
tasks. Tasks are actions performed using an Systems Insight Manager tool. Task instances are an
executed single instance of a task.
Managing with tasks related information
Viewing task instance results
Procedure 32 Viewing scheduled task results list
1.
2.
3.
4.
From the menu, select Tasks & Logs→View Task Results.
Select a task.
To stop or delete a task instance, select a task instance from the View Task Results page.
Click Stop or Delete.
The Task Results page displays a list of task instances created by all tasks.
Viewing task instance results
From the Task Results page, select a task instance by selecting a row from the Task Instances list.
Managing with tasks
157
The Task Instance list displays the following information:
•
Status
This field displays the status of the task.
•
ID
This field displays the task job ID number.
•
Task Name
This field displays the name of the task that was executed.
•
Tool
This field displays the name of the tool that was used.
•
Owner
This field displays the user name that currently owns the task.
•
Command
This field displays the command used to run the task.
•
Summary Status
This field displays the summary status and indicates the status of some tasks.
•
Target
This field displays the name of the target collection or individual systems where the task
executed. If you run a custom tool or a MSA tool, this field displays the CMS system name.
With MSA commands, the command resides on the CMS and runs from the CMS for a remote
system or list of systems. Therefore, the target for this type of command always shows as the
CMS.
•
Executed As
This field displays the user context where the tools were executed from.
•
Start Time
This field displays the time when the task was started.
•
End Time
This field displays the time when the task was completed or cancelled.
•
Duration
This field displays the amount of time it took to run the task.
NOTE: The list of task instances is based on user privileges and access levels. Users with
administrative rights can view all task instances known to the system.
Viewing target details
NOTE:
This section appears for SSA tools only.
Target details include the following:
•
Target Name
This field displays the name of the target.
•
Status
This field displays the status of the target.
158
Screens and product layout
•
Exit Code
This field represents the success or failure of an executable program. Typically, if the return
value is zero or positive, the executable ran successfully. If a negative value is returned, the
executable failed.
•
The Stdout tab
This tab displays the output text information.
•
The Stderr tab
This tab displays information if the executable experienced an error.
This tab does not appear for discovery task results.
•
Files Copied tab
This tab displays what files are in the process of being copied or have been copied to the
target system. This tab is not present for tools that do not perform any file copies to their target
systems.
To view target details:
Procedure 33 View target details
1.
From the Task Instance Results section, select a target system from the table below the Summary
Status.
A window appears.
2.
View the target details.
Navigating the All Scheduled Tasks page
The All Scheduled Tasks page displays the tasks scheduled to run at periodic times or based on
event criteria. A scheduled task can also have a schedule of not scheduled, which means that the
task is listed but runs only when manually executed by a user.
To see task information, select Tasks & Logs→View All Scheduled Tasks, and then select a task by
clicking the task row.
User privileges
The list of tasks that a user can see is based on the user's privileges. All users can edit, delete, and
view the tasks they have created. With administrative rights, a user can edit, delete, and view
tasks other users have created.
Run now
Run a task to initiate a task instance. (Running a task executes a tool on specific systems or events.
For more information, see Running a scheduled task.
Edit
Procedure 34 Editing tasks
1.
2.
Select Tasks & Logs→View All Scheduled Tasks.
Select a task, and click Edit.
The previously configured task information appears.
3.
Edit the task, and then click Done.
For more information, see Editing a scheduled task.
Managing with tasks
159
Delete
Procedure 35 Deleting tasks
1.
2.
Select Tasks & Logs→View All Scheduled Tasks.
Select a task, and click Delete.
For more information, see Deleting a scheduled task.
Enabling and disabling tasks
If the selected task is currently enabled, this button reads Disable and clicking it disables the task.
If the selected task is currently disabled, this button reads Enable and clicking it enables the task.
Viewing task results
When you view task results, you see information similar to the following:
•
The tasks schedule
•
The tool used by the task
•
The command the task executes
•
A list of task instances created by the task
•
Summary status, the target systems list, and target details
For more information, see Viewing task instance results.
License Manager
NOTE: To run License Manager, you must have administrative rights on the CMS (to set, select
Options+Security→Users and Authorizations→User) and choose the Configure CMS Security option,
and the All Tools toolbox (to set, select Options+Security→Users and Authorizations→User) on the
managed systems that you want to license.
To access License Manager, select Deploy→License Manager.... The Product License Information
table appears.
Table 28 License Manager options
Name
Description
Related Information
Procedure
Licensed System(s)...
HP SIM enables you to view “Licensed System(s)...”
a list of systems licensed for (page 161)
the selected product.
Add Licenses...
HP SIM enables you to add “Add Licenses...” (page 161) See Adding licenses
individual license keys to the
individually.
License Manager database.
Manage Licenses...
The Manage Licenses feature “Manage Licenses...” (page See Managing licenses
enables you to manage
162)
licenses for the product
selected in the Product
License Information table.
Licenses can originate from
direct user input or from
license information collected
using Collect Remote License
Info....
Collect Remote License
Info...
Collect Remote License Info “Collect Remote License
(for management processors) Info...” (page 164)
collects licenses using an
HTTP based protocol which
does not require credentials.
160 Screens and product layout
See Viewing licensed
systems.
See “Collect Remote License
Info...” (page 164)
Table 28 License Manager options (continued)
Name
Description
Related Information
Procedure
Assign License(s)...
HP SIM enables you to
“Assign License(s)...” (page
assign and un-assign
164)
product licenses for plug-ins,
if applicable for that plug-in,
and to assign licenses to
remote target systems when
licenses are managed
remotely. For plug-ins, when
assigning licenses, note the
following for
non-management processor
targets:
See Assigning a license or
Apply a license
Un-Assign Licenses...
An assigned license can be “Un-Assign Licenses...”
unassigned from one system (page 165)
and assigned to another
system, as long as the
product enabled by the
license has not consumed
the license. When a product
has been used on a system,
the license is locked to that
system permanently. Licenses
delivered directly to the
actual target system cannot
be unassigned. There is no
penalty for having these
licenses remain on those
systems because they are
consumed on an as-needed
basis. The remaining
licenses can be used
elsewhere.
See Un-assigning a license
Apply Licenses
Apply a license to a system
must be treated as
irreversible. The license is
locked to the specified
system.
“Apply Licenses” (page 165) See Assigning a license or
Apply a license.
CLI mxlmkeyconfig
The CLI mxlmkeyconfig
allows you to combine all
the License Manager key
files into one file instead of
having to execute multiple
files. Combining these files
into a single file makes it
easier when adding keys
from a file through the
License Manager graphical
user interface (GUI).
“CLI mxlmkeyconfig” (page
169)
See mxlmkeyconfig CLI.
Licensed System(s)...
HP SIM enables you to view a list of systems licensed for the selected product.
Although a target can be licensed to use a product, the product license might not appear in the
interface or report. Products can elect to not display all or some licensing details.
See Viewing licensed systems.
Add Licenses...
HP SIM enables you to add individual license keys to the License Manager database.
License Manager
161
HP iLO product license keys can be added into the database because they can be deployed directly
to management processors.
See Adding licenses individually.
Manage Licenses...
The Manage Licenses feature enables you to manage licenses for the product selected in the Product
License Information table. Licenses can originate from direct user input or from license information
collected using Collect Remote License Info....
Manage Licenses:Licenses currently available for Virtual Machine Management page.
NOTE:
Only available license are displayed.
1
License Category
2
The type of license. All
permanent, paid licenses
appear as a single
category, even though
you might have purchased
several separate licenses.
License Manager does not
consider the purchase
date.
Licenses Available
3
The total number of
licenses available to
assign to systems.
Licenses Assigned
4
The total number of
licenses of the selected
type assigned to systems.
Licenses Used
The total number of
licenses used by systems.
A license is not used until
the product is used on a
system. This total includes
previously used licenses
that have expired.
162
Screens and product layout
5
Days permitted
6
The total number of days
authorized for use by this
license (for time-specific
licenses). For BETA
licenses, this is the number
of days from the date the
license was issued. For
subscription licenses, this
is the number of days
since the license was first
used on any target. For all
others, it is the number of
days from when the
license was first used on
the selected target. All
uses of this license after
the first use have the same
number of days remaining
as the target first licensed.
Days remaining
The number of days
before the license expires.
Some licenses will show
Days remaining as the
same as Days permitted
because the time to expire
is determined when the
license is applied to a
target and relates only to
that target. Others show
an equal or lesser number
8
Status
9
The status of the use of this
license on the named
system.
Updates and Upgrades
10
Reports level of service
associated with this license.
Technical Support
Reports level of service
associated with this license.
7
as the time to expire is
based on the first
application of the license
or based on when the
licenses was issued for
these types of license.
With a BETA license, the
Days remaining is always
less than the Days
permitted even if the
license has not been used
on a target.
License Source
The source of the
corresponding license.
This can be:
•
Purchased. The
license was
purchased as part of
a license agreement.
•
Free Trial. The license
was supplied free of
charge.
Status messages include:
•
OK. The license is valid and in compliance.
•
Key not in use. The license is valid but not used.
•
No expire date. The license is valid but not used.
•
License is fully subscribed. The license key is in full use on this system and
consequently, if used elsewhere as well, might be over subscribed in total.
•
License is over subscribed. The license key is overused on this system.
•
License trial period has expired. The time limit on a time-limited key has been
exceeded.
•
License subscription period has expired. The subscription key has expired.
•
Wrong host equipment. The serial number of the target on which this key was found does
not match the serial number contained in the key information retrieved from this machine.
The Manage Licenses table shows the license categories that can be used. License categories with
all licenses consumed are not listed in this table. Adding the number of licenses in all categories
in the Manage Licenses table might result in a total less than the number shown in the Licenses
column of the Product License Information table.
In the Manage Licenses table, the total number of Licenses Assigned plus Licenses Used might exceed
the number of licenses shown in the Product License Information table. Systems with assigned
licenses from this category might fail to be automatically licensed when used with the corresponding
product. This can occur when a category of license is assigned to a collection of systems, and then
later, the same category is applied to a different set of systems such that the total exceeds the
number of licenses in that category. Un-assign the licenses assigned to these systems. Assigned
licenses are not locked to systems, and licenses are used on a first-applied basis.
See Managing licenses
License Manager 163
Collect Remote License Info...
Collect Remote License Info (for management processors) collects licenses using an HTTP based
protocol which does not require credentials.
When collecting remote licenses, be aware of the following:
•
Automatic collection of management processor licenses is not supported.
•
You do not have support or upgrade options by default. After July 9, 2007, all license keys
are included in one year of 24 x 7 Software Technical Support and Update Service. The
License Manager informs you which license keys are "support and update enabled" and which
license keys require the purchase of future updates and upgrades.
Collect Remote License Info (for servers) collects license details from selected targets. If licenses are
stored on the selected system (for details, see the specific product information), the selected machine
must be running a variant of Microsoft Windows.
Assign License(s)...
HP SIM enables you to assign and un-assign product licenses for plug-ins, if applicable for that
plug-in, and to assign licenses to remote target systems when licenses are managed remotely. For
plug-ins, when assigning licenses, note the following for non-management processor targets:
•
When a license is assigned to a system, it is not locked or consumed until the product operates
on that system.
•
A system can be licensed with a demo key just once. If the license expires, the only option to
continue to use the system with that product is to purchase a license. A system licensed by a
demo key can be relicensed at any time with a paid license.
•
An assigned license can be unassigned from one system and assigned to another system, as
long as the product enabled by the license has not consumed the license. When a product
has been used on a system, the license is locked to that system permanently. Licenses delivered
directly to the actual target system cannot be unassigned. There is no penalty for having these
licenses remain on those systems because they are consumed on an as-needed basis. The
remaining licenses can be used elsewhere.
Some products limit the use of the License Manager interface because target filtering and other
factors must be considered and these are not known to the HP SIM License Manager. Consequently,
Manage Licenses... may be selected, however Assign/Un-assign might be disabled.
For management processor targets:
•
When a license is assigned to a management processor, a license record is created and
stored in the License Manager database.
•
If the selected management processor is already licensed, you cannot replace that license
with a new license from License Manager. You must first delete the existing license at the
management processor console and then insert the new license (directly or using License
Manger). However, Integrity MP does replace a demo key with a permanent license. If a
permanent key is already present, Integrity MP displays a message such as License already
Installed.
•
An assigned license cannot be unassigned from one management processor and assigned to
another management processor. Licenses delivered directly to the actual target system cannot
be unassigned because the behavior of the product operating with that license is outside the
scope of License Manager.
When assigning licenses to management processor targets, the SSH credentials for each target
must be known. When deploying licenses to remote servers, the access credentials must be known.
For more information, see Protocol settings.
See Assigning a license or Apply a license
164 Screens and product layout
Un-Assign Licenses...
HP SIM enables you to assign and un-assign product licenses for plug-ins, if applicable for that
plug-in, and to assign licenses to remote target systems when licenses are managed remotely. For
plug-ins, when assigning licenses, note the following for non-management processor targets:
An assigned license can be unassigned from one system and assigned to another system, as long
as the product enabled by the license has not consumed the license. When a product has been
used on a system, the license is locked to that system permanently. Licenses delivered directly to
the actual target system cannot be unassigned. There is no penalty for having these licenses remain
on those systems because they are consumed on an as-needed basis. The remaining licenses can
be used elsewhere.
Some products limit the use of the License Manager interface because target filtering and other
factors must be considered and these are not known to the HP SIM License Manager. Consequently,
Manage Licenses... may be selected, however Assign/Un-assign might be disabled.
See Un-assigning a license
Apply Licenses
Apply a license to a system must be treated as irreversible. The license is locked to the specified
system.
See Assigning a license or Apply a license.
Product License Information table
•
Provides sorting capability.
•
Displays a maximum of 10 rows. If there are more than ten product license, use the scroll bar
on the right side of the table to view additional licenses.
Product License Information buttons
1
Licensed System(s)...
2
Allows you to view a list of
systems licensed. Remains
deactivated until a product
is selected.
Add License...
3
Manage Licenses...
4
Allows you to manage
licenses for the product
selected. Remains
deactivated until a product
is selected.
Allows you the option of
entering licensing
information independently.
Collect Remote License
Info...
Gathers licenses information
from Integrity and ProLiant
management processors and
the selected target systems for
products which operate under
the Remote License
Management scheme.
When there are no licenses available, the following table appears.
License Manager
165
1
Product
2
The name of the product.
License Version
The license version of the
product.
3
Licenses Locked
4
The number of licenses
consumed.
Licenses Assigned
5
Licenses Available
6
The number of licenses
available.
Total Licenses
The number of licenses
assigned.
Total number of license
available for the product.
When one or more license is available, the following table appears.
Add Licenses... remains active and you can add licenses to HP SIM in one of two ways:
•
Add Licenses
Enter an individual license key. For more information, see Adding licenses individually.
•
Adding Licenses from File
Enter license keys from a specially formatted key file. For more information, see Adding licenses
from a file.
Collect Remote License Info... remains active and you can collect license information. See “Collect
Remote License Info...” (page 164).
License Collection Results table
166 Screens and product layout
1
2
•
System Name. The names of
the systems where the task
was executed.
Key. The license keys
received from the target
systems. Each key retrieved
from a system is on a
separate line. Some products
have more than one license
key. License details are
contained in the key, and
each key might enable more
than one product.
3
Product. The name of the
product associated with the
use of this key.
4
Response Status. The status of
the request for license data
for the selected system.
Successful task
A. Licensing information from the remote system.
B. Licensing information from the target system.
NOTE: This response status displays for systems running Windows variant OS and has
license stored in the registry.
•
Unsuccessful task
A. Connection to device failed. Possible reasons could be device
not reachable or device is an older firmware version of management
processor.
This
a.
b.
c.
B.
happens due to the following reasons:
Network error - Connection Refused.
Network error - Connection timed out.
The system you are trying to connect has firmware version that is older or not
supported.
Device not found.
Failure in pinging the system.
C.
D.
E.
F.
G.
H.
I.
J.
License Key overused. Please refer to the license agreement to
avoid any violations.
No valid licensing information found on the remote system.
No licensing information on the remote system.
Problem collecting licensing information.
Failed to contact this system. Network path not found or similar
error.
Specified system is no longer in the database.
Target system is not running Microsoft Windows as required.
Keys cannot be collected from a system of this type.
NOTE: This displays if the system is of a different type such as; a switch, a printer, a
cluster, a complex, or a system not running a Windows OS.
K.
Cannot collect keys stored on this node. HP SIM host and specified
system must be running Microsoft Windows.
License Manager
167
NOTE: This happens when, for example CMS or a remote system is not running a
Windows variant operating system.
L.
License Manager does not know how to assign licenses for this
product. License Manager has no information about this product.
Install the HP Systems Insight Manager plug-in that uses this
license or collect license information from a system running this
product first.
Add License page
1
Select the complete key
string and press Ctrl + C to
copy it.
2
Enter the full path and file
name in the Specify a file
name and path field.
3
Position the cursor in any of
the five fields forming the
input box and press Ctrl + V,
or right-click your mouse to
paste the license key. If the
Add License function was
selected after you copied the
key, press Ctrl + V to paste
the key.
Click Browse.
a. The Choose file dialog
box appears.
b. Navigate to the file that
contains the licenses to
be added.
c. When a file has been
located, click Process.
The license key displays with
five characters in each field.
NOTE:
When pasting in the complete key, the key can be in the normal format of five groups
of five characters, with each separated by a hyphen (-), (for example,
12345-67890-54321-09876-12345). There are no spaces between the characters and the
hyphens.
Key details page
Click Process to display the license details.
1
Product
2
The name of the product.
License Version
The license version of the
product.
168 Screens and product layout
4
Licenses Purchased
The number of licenses
purchased for a product.
6
Back
Returns to the Add License
page.
3
Licenses Type
The type of license for
example, Demo, Beta,
Duration, Site, and
Maintenance.
5
Days Max
The maximum number of
days the licenses can be
used.
7
Add Licenses Now
Adds the keys to the
database.
License not added
Keys from file:
The Status column displays the status of the product license key. Status messages are as follows.
•
For a valid Key:
OK
•
Key cannot be added to HP SIM:
License Manager already has this license.
Invalid Key.
License Key provided is not valid for user input.
NOTE:
When a license key cannot be added, the row remains deactivated.
CLI mxlmkeyconfig
The CLI mxlmkeyconfig allows you to combine all the License Manager key files into one file instead
of having to execute multiple files. Combining these files into a single file makes it easier when
adding keys from a file through the License Manager graphical user interface (GUI).
The mxlmkeyconfig command takes all the keys and related information and places it in the resulting
key file. The CLI program will not allow duplicates. If there are duplicate <keystring> values, a
warning message appears and only the first value is placed in the resulting key file. If badly
formatted files are encountered, warning messages appear.
License Manager
169
The key file is created when CLI mxlmkeyconfig is executed. If the resulting key file already exists,
then the previous keys remain and the information from the source key files are added to the
resulting key file.
See mxlmkeyconfig CLI.
Assigning or Applying Licenses page
1
System Name
2
The name of the system
where the task was
executed.
Serial Number
3
A number the licensing
product chooses to identify
remote systems. (Check
product information for
specific details).
Unique Identifier
A unique string that further
identifies a system. Systems
can be licensed by any
combination of system
name, serial number, or
unique identifier.
4
Status
5
The status of the use of the
license on the named
system.
Operating System
6
The name and edition of the
operating system installed
on the product.
System Type
7
System IP Address
8
The IP Address of the licensed
system.
All Features Supported
The type of system licensed,
for example, server, storage,
or unmanaged.
9
A 'Yes' or 'No' value.
Systems can be licensed with
a bundle license. The Yes in
this column implies that all
products licensed by bundle
license fully support the
system indicated. No,
indicates that some licenses
do not support this system.
You must determine which
products do not support the
selected system.
License advisories and
warnings resulting from last
licensign activity:
Table that indicates other
licenses which are required
to be in place on indicated
system to fully comply with the
selected product license.
170
Screens and product layout
License unlicensed systems (optional) page
1
2
System license status
Displays the status of system
licenses, such as Not
licensed, or assigned
duration license.
System selected to be
licensed
System Name
15.146.233.1 is selected to
have a license assigned to
it.
3
4
Licenses currently
available
Displays all of the currently
available licenses to be
assigned.
License selected
5
Apply license
Applies the selected license
to the selected system.
A license is selected to be
assigned to system
15.148.233.1.
Inline license page displaying the change to both the System license status table and the Licenses
currently available table after a node is licensed with DL license.
License Manager
171
1
System license status
System 15.146.233.1
displays the status as having
a assigned duration license.
2
Licenses currently
available
Displays that the Duration
license has been reduced by
the number of licenses
assigned to system
15.146.233.1.
License types
License Manager displays licenses by product. If a license authorizes multiple products, the number
of seats permitted by the license is applied in full to each authorized product. For example, a
license authorizing five seats and two products authorize five seats for each product.
Table 29 License types
License Type
Description
Flexible Quantity
Offers full, unlimited functionality for an unlimited time and
for a specific number of seats purchased, up to 50,000.
Activation Key Agreement
Offers full, unlimited functionality for an unlimited time.
This license represents an expected upper limit on the
number of seats, up to 50,000.
Demo (seats and time)
Offers full, unlimited functionality for a limited time and a
specific number of seats. The license determines the number
of days the key enables the product to function. The days
begin counting from the day of first use. The key can permit
more than one instance of the product to run. Demo keys
can authorize up to 255 seats for up to 255 days.
Demo (time)
Offers full, unlimited functionality for a limited time. The
license determines the number of days the key allows the
product to function. The days begin counting from the day
of first use. The key can permit more than one instance of
the product to run. Demo keys can authorize use for up to
65,535 days.
Beta
Offers full, unlimited functionality for a limited time. The
license determines the number of days the key enables the
product to function. The days begin counting from the day
the key is created. The key can permit more than one
instance of the product to run. Demo keys can authorize
use for up to 65,535 days.
Duration
Offers time limited, full functionality license. The license
can be re-applied to the same node as needed at any time
as long as unused licenses are available with this key. For
example, when the current license is expired. The basic
time unit encoded in the key is one month.
You can authorize up to 255 sets of Duration licenses for
up to 255 days.
Subscription
NOTE:
172
A time-limited, full-functionality license. The key can indicate
unlimited use for a specified period of time or a limited
number of seats for that same period of time. The basic
time unit encoded in the key is 30 days.
HP SIM considers one month equal to 30 days.
Screens and product layout
Table 30 License types reported by management processor products
License Type
Description
Intrinsic
Offers full, unlimited functionality and represents a
single-use key for the product. This license type is specific
to management processors.
Individual
Offers full, unlimited functionality and represents a
single-use key for the product. This license type is specific
to management processors.
Permanent
Offers full, unlimited functionality.
Demo (time)
Offers full, unlimited functionality for a limited time. The
license determines the number of days the key allows the
product to function. The days begin counting from the day
of first use. The key can permit more than one instance of
the product to run. Demo keys can authorize use for up to
65,535 days.
Some products provide licenses to enable other products. The license keys generated by these
products cannot be manually added.
Related information
Managing licenses
Assigning a license or Apply a license
Viewing licensed systems
Adding licenses individually
Un-assigning a license
Related topics
License Manager
License manager
License Manager
Reporting
New Report...
A report configuration is a customer-defined set of preferences that pulls specified criteria from the
database tables and places it in a report in the specified format. The report configurations can be
saved and used to run a report at a later date with live data.
You must have administrative or operator rights to create, save, edit, copy, or delete report
configurations. Users with user rights can run the authorized report configurations only.
If User 1 with administrative rights generates a report and a private collection, then User 2 with
administrative rights can generate a report using the report configuration and private collection
that User 1 created. User 2 is allowed to edit, save, and delete the report configuration but cannot
delete the private collection created by User 1.
The create new report wizard helps you to create a new report and add it to HP SIM reports. This
option is only available for HP SIM.
You can save the report configuration for future use or generate a one-time report.
Select Reports→New Report....
See New reports.
Manage Reports...
Select Reports→Manage Reports.... The Manage Reports page appears.
License Manager
173
Users with sign-in access to HP SIM can generate reports.
The Manage Reports feature provides you with the following options:
•
Run Report
A generated report provides you with the following information:
◦
Report name
◦
Associated system collection
NOTE: The Associated system collection information does not appear if there is no
collection selected to run the report.
◦
Report run date and time
Format for generated report:
◦
HTML (Recommended for viewing)
Enables viewing an existing report in HTML format.
◦
XML
Enables viewing an existing report in XML format.
◦
CSV
Enables viewing an existing report in CSV format.
See Running managed reports
•
Copy...
HP SIM enables you to copy report configurations from an existing report configuration. You
can edit the newly copied configurations to create a new report.
NOTE: You must be signed in to HP SIM with administrative rights or operator rights to copy
report configurations. If you are not signed in with administrative or operator rights, the copy
option is not available.
See Copying managed reports
•
New...
Enables you to create a new report and add it to HP SIM reports. This option is only available
for HP SIM.
You can save the report configuration for future use or generate a one-time report.
See New reports.
•
Edit...
HP SIM enables you to edit existing report configurations. You can save these updated report
configurations over the existing report configuration, or you can save it as a new report
configuration.
NOTE: You must have administrative rights or operator rights to create, save, edit, copy, or
delete report configurations. Users with user rights cannot edit the report configurations.
See Editing managed reports
174
Screens and product layout
•
Delete
You can permanently delete a report configuration from the Manage Reports page.
See Deleting managed reports
•
Showing SQL Queries.
Enables viewing SQL queries.
Select Reports→Manage Reports.... The Manage Reports page appears. Select the report for
which you want to view the SQL details, select Run Report, and then on the report itself, click
Show SQL queries.
Snapshot comparison...
Snapshot comparisons enable you to compare up to four systems (with the same operating system)
to each other or to compare a single system to itself and observe changes over time.
To view a snapshot comparison, select Reports→Snapshot Comparison.... The Snapshot Comparison
page appears. Select target systems, and then click Next.
See Snapshot comparison reporting. .
Enhanced Reports
Select Reports→Enhanced Reports....
The Enhanced Reports feature offers the following options:
•
Predefined Reports
Predefined Reports are shipped with HP SIM. The reports are based on common user scenarios
and do not need any additional configuration or enablement. The Predefined Reports feature
is installed, configured, and available for use as soon as HP SIM is installed and configured.
Predefined Reports are tied to existing systems collection in HP SIM, for instance, "All Systems"
or "All Servers" with the exception of Event trends by severity or type for a system collection
where you have to select the collection or system(s) of your choice. Report results appear
based on logged in user authorization of nodes.
Select Reports→Enhanced Reports.... The Enhanced Reports, Reports by Product page appears.
See Running predefined reports
•
Creating New Reports from the Enhanced Reports Page.
Select Reports→Enhanced Reports.... The Enhanced Reports, Reports by Product page appears.
Click New.... The New ReportStep 1: Select Target Systems page appears.
See Adding a report.
•
Editing Reports.
Select Reports→Enhanced Reports.... The Enhanced Reports, Reports by Product page appears.
Select the report that you want to edit, and then click Edit.... The Add details to report: Step
3: Specify Parameters page appears.
See Editing a report.
•
Running Reports.
Select Reports→Enhanced Reports.... The Enhanced Reports page appears. Select the report
that you want to run. Click Run Report.
See Running a report.
License Manager
175
•
Email Report.
Enables a report to be emailed at a later specified time.
Select Reports→Enhanced Reports.... The Enhanced Reports, Reports by Product page appears.
Select the report that you want to schedule, and then click Email Report....
See Emailing reports.
•
Deleting Reports.
Enables a user defined report to be deleted.
Select Reports→Enhanced Reports.... The Enhanced Reports, Reports by Product page appears.
See Deleting a report.
Federated CMS Search tool
Select Reports→Federated Search....
Federated CMS Search is a web-based HP SIM plug-in that allows you to search quickly across a
number of Systems Insight Manager CMS systems. Federated Search finds systems using basic
system criteria such as name, system type, subtype, and OS. The search tool can also search
software inventory information to find, for example, firmware versions across all Windows systems.
From the search results, you can drill down into specific systems on specific CMSs, accessing all
features on those CMSs and you can have the results exported to CSV, a comma-separated value,
format.
How it works
•
System administrators log into the host CMS running the Federated CMS Search tool and
launch the tool from the HP SIM Reports menu.
•
A list of searchable CMSs appears with their respective connection status, version information,
and system counts.
NOTE:
Federated Search must be configured before a search can be performed.
•
Submit search criteria (name, status, system type/subtype, product, OS) and the Federated
CMS Search UI searches other CMSs through their respective HP SIM web service APIs.
•
Other CMSs in the organization returns the individual search results in a single table.
Search Tab
Search criteria:
176
•
All fields operate on a contains basis. Boolean operators and wildcards are not supported.
•
All fields are case-insensitive.
•
Matches occur when all provided criteria are met.
•
Fields that accept text input also have a dropdown list of suggestions.
Screens and product layout
1
2
Search Initiates the search.
Reset Fields Clears all search
fields.
3
4
Expand All Expands to
display information
available under each
hyperlink in the table.
Collapse All. Collapses
information displaying under
each hyperlink in the table.
5
6
Hyperlink System names from
the search results. When
clicked, the hyperlink displays
a browser window that shows
the Systems Insight Manager
System Page for that system,
as delivered by the CMS on
which the system was found.
Export to CSV Exports the
search results table in CSV
format.
See Federated CMS Search Tool.
Connections Tab
The connections tab displays the status of an attempted connection to each secondary CMS. If
Federated CMS Search fails to connect to a CMS, that CMS is excluded from subsequent searches.
After successful connection and if you have suitable authorizations locally on the secondary CMS,
the secondary HP SIM version, operating system, and system count are displayed.
1
Credential preferences
By default, all connections
made to secondary CMSs
are made as the currently
signed-in user. To connect
as another user, you can
specify full credentials for
that user. The credentials are
securely encrypted and
stored on the main CMS
privately for the current user.
2
Refresh Connections
CMS connections are
established once and
maintained in the current
instance of the UI. If a CMS
is rebooted or comes online
after starting Federated
Search, you must refresh
connections to establish a
connection to the newly
online CMS.
3
Go to Federated CMS
Configuration
The Federated CMS
Configuration is used to
configure the list of secondary
CMSs. In order for the main
CMS to be included in
operations such as search, it
must be added to the
secondary list and display a
successful configuration
status.
NOTE: Setting up the CMS
list can be done only by a
full-rights user.
See Connections Tab for more information about the Connections tab.
See Federated CMS Search Configuration for more information about configuring the Federated
Search tool.
Reports by Product page
The reporting engine main page contains the Reports by Product table that displays the products
registered with HP SIM along with the available reports.
License Manager 177
1
2
3
Expand icon. Reveals
product details.
Minimize icon. Hides
product details.
Product/Report Name.
Displays the name of the
products along with the total
number of reports in
parenthesis registered with
HP SIM for reports. When
the product item is
expanded by clicking the
expand icon, the available
reports are displayed under
the product section along
with report details
Description, Target Systems
and Report Type.
4
5
Report Type. Displays the
type of report such as; Table,
Bar, Pie, Line, or a collection
of all three types in any
combination..
Target Systems. Displays the
target selection in which the
report is executed.
6
7
Report Description. Displays
a short description of the
report.
Expand/Minimize icon.
Displays/hides details of all
available reports under the
registered product.
NOTE: The Reports by Product table displays reports for HP SIM by default. Only products that
have been registered with HP SIM have Predefined reports displayed.
NOTE:
If links are not visible for some or all Enhanced Reports, use the following workaround:
Procedure 36 CMS installed on Windows
1.
2.
Open the reports.xml located in <HP SIM installation
directory>/config/preload/62/addfiles/reports.xml and change the timestamp.
You can do this by entering a space at the end of the file and resaving it.
Execute the mxconfigrefresh command at the command prompt.
Procedure 37 CMS installed on HP-UX or Linux
1.
2.
Open the reports.xml located in /etc/opt/mx/config/preload/62/addfiles/
reports.xml and change the timestamp. You can do this by entering a space at the end
of the file and resaving it.
Execute the mxconfigrefresh command at the command prompt.
After completing the procedure, the links to reports appear in the user interface.
Reports by Product page buttons
All buttons remain disabled until a product is selected.
178
Screens and product layout
1
2
New.... Creates a new
report. Only enabled for HP
SIM reports.
Edit... Edits a selected
report. Only enabled for
user created/defined reports
under HP SIM. Remains
disabled for Predefined
reports.
3
4
Run Report Executes a
report.
Email Report... Enables users
to email a report.
5
Moves a selected items
position up in the Selected
Members: list.
Moves a selected items
position down in the
Selected Members: list.
Click to return to the
previous page.
8
Delete Deletes a selected
report. Only user
created/defined reports can
be deleted.
Select data to be displayed in the report:
1
2
3
4
Select data from the
Available Data: list to be
included in the report.
Click to add selected data
from the Available Data:
list to the Selected Data:
list.
List of items to be included
in the report.
Removes a selected item
from the Selected
Members: list.
5
6
7
9
10
Click to run the report with
the selected data.
Click to save the report
with the selected data.
Click to email the report
with the selected data.
Related information
License Manager
179
Related information
Related procedures
Reporting
New reports
Running managed reports
Copying managed reports
Editing managed reports
Deleting managed reports
Running a report
Adding a report
Editing a report
Running predefined reports
Deleting a report
Emailing reports
Snapshot comparison reporting
Related topics
Printing a cluster collection view
Printing an event collection view
Printing reports
User and user group reports
Toolbox reports
Authorization reports
Reporting
Snapshot comparison reporting
Reporting
Remote Support Configuration and Services
Remote Support Configuration and Services overview
The Remote Support Configuration and Services option facilitates the collection of enterprise events
and configuration data from monitored systems and establishes remote connectivity back to HP for
reactive support in a timeframe determined by warranty or contract level.
The following subsections provide a brief overview of the Remote Support components configured
through the Remote Support Configuration and Services option.
Remote Support Client
The HP Remote Support Client is the underlying component that enables the communication of
hardware event information collected on the CMS to the HP Support Center. This component is
configured in the Remote Support Configuration and Services option in HP SIM and is critical to
providing remote support of your systems.
Remote Support Configuration Collector (RSCC)
The Remote Support Configuration Collector (RSCC) schedules and consolidates configuration,
performance, and availability collections from entitled server systems through the Advanced
Configuration Collector component installed on each managed server, or directly from SAN and
storage devices for proactive support purposes. The RSCC is updated regularly to extend support
for new products as they become available.
Remote Support Configuration Collector Extension
This component is designed to extend the capabilities of the Remote Support Configuration Collector
when SAN support is required.
180 Screens and product layout
Advanced Configuration Collector Commands and Rules
This component is hosted on the CMS and can be updated through Remote Support Software
Manager (RSSWM) to specify what configuration, performance, or availability data will be collected
from each supported device type.
Remote Support System List
The Remote Support System List identifies devices that are eligible for remote support services
including remote-phone-home-monitoring. This list is updated on a regular basis to add new device
support to this service automatically.
Configuring Remote Support Configuration and Services settings
Procedure 38 Configuring Remote Support Configuration and Services settings
1.
Enter your CMS information in the following sections:
•
CMS Location Information
•
CMS Administrator Contact Information
•
Additional CMS Administrator Contact Information
•
HP Account or Service Provider Contact Information
NOTE:
•
Additional HP Account Contact Information
•
Proxy Server Information
NOTE:
2.
3.
4.
5.
6.
This information should only be entered by HP or a Service Provider.
In each of these sections, an * denotes a required field.
(Optional) Configure your email event settings. You can select any, none, or all of the following
options:
•
Incident has been received at HP
•
Incident has been escalated to HP workflow
•
Incident has been closed at HP
(Optional) In the System enablement section, select Enable systems for Remote Support Services
upon discovery.
(Optional) In the Privacy Information section, read the HP Worldwide Privacy Statement and
select HP may use the collected information to provide recommendations that may improve
your environment..
Click Submit Updates.
(Optional) To verify the connectivity to HP using the Remote Support client, click Test Data
Submittal. This test does not create a Service Event in HP SIM.
Using the Entitlement tab
The Remote Support Configuration and Services Entitlement tab allows you to enable or disable
remote support for any and all Remote Support eligible and supportable systems in your enterprise.
The Remote Support System List displays the status of and provides access to the Remote Support
Entitlement Check (RSEC) for individual eligible systems. If a system is supportable but does not
meet a support obligation, events submitted to HP by HP Remote Support may be closed without
action.
License Manager
181
About the Remote Support System List
The Remote Support System List available through the Remote Support Entitlement tab displays
details for systems that are eligible for Remote Support. This list is part of a table that provides the
following categories (columns) per system (rows) in your enterprise.
•
The Transport Enabled (TE) column indicates whether or not entitlement checks and events can
be submitted for each system listed.
•
The Entitlement (ENT) column displays the entitlement status for each of the listed Remote
Support eligible systems in your enterprise. The status is denoted by an icon, for example, a
green symbol with a white check mark indicates the Remote Support Entitlement Check (RSEC)
was successful and returned a valid entitlement for that system. Tooltips describe the significance
of each status icon. You can also click on the icon to display more details on a system's
entitlement status in a separate Remote Support Entitlement Details window. Entitled systems
are part of the Remote Support Enabled Group in HP SIM. NO events will be submitted to HP
unless the system is entitled.
•
The Remote Support Ready (RS) column indicates either that entitlement, location, and/or
contact information has or has not been properly configured. It does not tell you which of the
three may be misconfigured.
•
The Contract Package (CP) column displays the contract package type associated with each
of your systems.
•
The System Name column identifies a particular system in your enterprise.
•
The Serial # column displays a system's serial number (if available).
•
The Product # column displays a system's product identifier (if available).
•
The Country Code (CC) column displays the country code associated with a particular system.
•
The Ent Type column displays the entitlement type associated with a particular system.
•
The Ent ID column displays a system's entitlement identifier.
•
The Obligation ID (OID) column displays the HP obligation ID associated with a particular
system.
Enabling Systems for Remote Monitoring
To ensure that the Remote Support System list is current you can synchronize it to make sure that
all eligible active systems display.
The Remote Support Entitlement tab allows you to manage systems with regard to Remote Support,
that is, enable and disable them with regard to Remote Support services and perform entitlement
checks for single, multiple, or all systems in your enterprise.
If, when you registered your enterprise for Remote Support in the Remote Support Settings tab,
and you did not select the option Enable Remote Support Devices upon Discovery, then you may
have multiple eligible systems that are not yet listed as available for remote monitoring.
If you selected Enable Remote Support Devices upon Discovery, then you may see systems listed
that you would prefer to disable.
You can use one of the Transport Enablement options available from the Action List drop-down list
to manage remote monitoring for the listed systems. You can enable or disable all systems, or
manage one or more systems by selecting their associated checkbox and running an action from
the Action List drop-down list against the selected systems. For example, you may choose to not
monitor your test systems, even if they are eligible and supportable through warranties. Additionally,
when you have enterprise-wide maintenance tasks or expected downtime, you may choose to use
the Disable All option to temporarily discontinue remote monitoring in your enterprise.
NOTE:
182
Enabling monitoring may require 3-5 seconds per system.
Screens and product layout
Synchronizing the Remote Support System List
To ensure that the Remote Support System list is current, and lists all Remote Support Eligible systems
in your enterprise, you can use the Synchronize RSE available at the bottom right of the Entitlement
page.
NOTE:
Synchronizing the Remote Support System list can take a long time in large enterprises.
Updates on the status of the synchronization are displayed at the top of the page. You must refresh
the page to view the results of the synchronization.
Accessing Remote Support Configuration Services On-Line Help
To open Remote Support Configuration Services specific help, click the
the RSCS tabbed pages (excluding the Settings and Entitlement tabs.
link available on all of
The Help page opens in a separate window that you can move or resize. To open a topic, select
the topic from the table of contents on the left side of the frame.
The Browsing for More Information> option enables you to select topics from the table of contents
or the index.
License Manager 183
6 Operations
Complete the following procedures to monitor and manage systems in HP SIM.
Customizing the Home page
Procedure 39 Customizing the Home page
1.
2.
To display the Home in the workspace click Home in the banner.
Click Customize in the upper-right corner of the introductory page.
If the Home page has been set to something other than the default introductory page, you can
access the Home Page Settings page by selecting Options→Home Page Settings.
3.
Specify which page you want to use as Home page:
•
Introductory page (default)
•
Plug-in (if installed) page
Some HP SIM partner applications use this option to point to their home page. However,
if no partner application is using this, selecting this option displays the HP SIM default
introductory page.
•
Any specific system, cluster, or event collection view
The default introductory page is available only when it is set as the Home page. If you want
to view this page when it is not set as your home page, reselect it as the Home page.
4.
5.
Optional: If the introductory page is selected as your home page, customize the content on
the page by selecting or clearing the following options:
•
Show "Do this now to finish the install" frame. If selected, this section appears on the
Home page.
•
Show the "Did You Know?" image. If selected, the image in the bottom right corner of
the Home page appears.
Optional: If you selected This collection, select a collection from the dropdown list, and then
select Automatically maximize workspace to automatically maximize the workspace when
this collection appears as the home page.
Customizing the system status panel
NOTE: Customized System Status panel appear in the system status pop-up window. To minimize
the System Status panel, click the minimize icon ( ) in the upper right corner of the panel title bar.
To maximize the System Status panel, click the maximize icon ( ) in the upper right corner of the
panel title bar. To open the System Status panel in a new window, click the Open in New Window
icon.
Customize the System Status panel to display the following status information:
•
Uncleared Event Status
A count that indicates the number of uncleared event statuses that are Critical, Major, Minor,
and Normal for any given system collection. Each number is a hyperlink to a detailed list of
events with that particular status. When you click the number, an event collection appears
with those particular events and their corresponding systems.
•
Health Status
A count that indicates the number of systems, in a given system collection, that have a system
health status that is Critical, Major, Minor, and Normal. Each number is a hyperlink to a
detailed list of systems with that particular status. When you click the number, a system
184 Operations
collection appears with those particular systems. Health status is not shown by default but can
be configured to appear.
NOTE: The system health status information appears only when it is customized to display
the system health status.
•
Alarm
You can customize an alarm to appear for specific criteria for any given system collection.
The alarm alerts you that a particular criterion has been met by one or more systems in that
collection. For example, you might receive an alarm that a storage system has a critical
uncleared event or critical health status. Because the System Status panel is continually updated,
the alarm appears until the event is cleared, the system is removed from the collection, or the
alarm customization is changed so that it no longer applies. If the System Status panel is
collapsed, and an alarm occurs, it opens automatically so that the alarm is visible. You can
collapse the panel, but it continues to open as long as the alarm is relevant. To have the panel
remain collapsed, you must clear the offending event or system status or reconfigure the status
display to no longer display alarms.
•
Legend of status icons
To display a list of status icons, click Legend in the System Status panel. Legend information
appears in a separate window and remains open until you close it.
NOTE: If the System Status panel is customized to have no status displayed, the timestamp does
not display.
Procedure 40 Customizing the System Status panel
1.
2.
Click Customize in the upper-right corner of the System Status panel. The Customize System
Status page appears.
Select the first Show summary of, and then select uncleared event status or health status.
a. Select the system collection All Systems, or select another system collection from the
dropdown list.
b. Edit the Label if desired.
3.
Select the second Show summary of, and then select uncleared event status or health status.
a. Select the system collection All Systems, or select another system collection from the
dropdown list.
b. Edit the Label if desired.
4.
Select to Show an alarm when any system meets the condition.
a. Select the Condition.
b. Select the system collection All Systems, or select another system collection from the
dropdown list.
c. Edit the Label if desired.
5.
Click OK to save changes.
NOTE: Clicking Restore Defaults returns the customization screen to its default condition:
only the uncleared event status appears in the banner. Health status and the alarm are disabled.
All personalized information is removed.
Enlarging the System Status panel
You can enlarge the System Status panel to monitor system and event statuses. Click the Open in
New Window icon on the System Status panel title bar and the status panel pop-up window
appears. To resize the window, click and drag the sides of the window. To close the window
Enlarging the System Status panel 185
manually, click the Close Window icon. Otherwise, the window is closed if the HP SIM window
is closed or refreshed, or you sign out of HP SIM.
The enlarged status panel window mimics the System Status panel. Whenever a status changes,
the pop-up window is updated. Click one of the status values to bring up the main HP SIM window
and display the corresponding collection. For example, if you click the Major status value, the All
Major Systems table view page appears. You can customize this window using the options for
customizing the System Status panel. See Customizing the system status panel for more information.
The following error messages might appear:
•
Systems Insight Manager is not configured to display any status.
To resolve this issue, close the window, customize the display of the System Status panel, and
then relaunch.
•
This window does not have a connection with the main Systems Insight
Manager window.
To resolve this issue, close the window.
NOTE: The status panel pop-up window might not appear if you have a pop-up blocker configured
and running on your system. You must disable the pop-up blocker or configure it to allow the HP
SIM application to use pop-up windows.
NOTE: If you HP SIM configure to enable session timeout, the status pop-up window no longer
displays the status when the session expires.
Utilizing RSS capabilities
RSS is a data format based on XML that can be used by applications and websites to provide
content to other applications. HP SIM uses RSS to publish System Status panel information that can
be viewed in newsfeed programs.
RSS capabilities can be enabled in HP SIM by adding the key name rssFeedEnabled = true in the
globalsettings.props. By changing this value, you can view the System Status panel
information in newsreaders and applications
Procedure 41 Enabling RSS
1.
2.
Stop the HP SIM service.
In the globalsettings.props file, add rssFeedEnabled=true. The file is located at:
•
On Windows
It is typically located at C:\Program Files\HP\Systems Insight Manager\
config\globalsettings.props.
•
On HP-UX and Linux
It is located at /etc/opt/mx/config/globalsettings.props.
3.
4.
Restart the HP SIM service.
Browse to http://server_name:280/RSS to view the XML output for the current HP SIM
status values.
The URL in step 4 can be used in RSS readers to view the same data.
Setting up managed systems from a Linux CMS
Use the following checklist to assist you with setting up managed systems from a Linux Central
Management Server (CMS).
IMPORTANT: Run discovery before setting up managed systems. For more information, see
Running a discovery task. Configuring automatic discovery is also part of the First Time Wizard.
186 Operations
Procedure 42 Setting up managed systems from a Linux CMS
1.
2.
3.
4.
Ensure that HP SIM is installed on the CMS.
Ensure the First Time Wizard has been completed on the CMS.
Install the ProLiant Support Pack on the CMS. See Installing the ProLiant Support Pack on a
Linux system for the first time.
Configure the managed system software. See Configuring the managed system software.
Installing the ProLiant Support Pack on a Linux system for the first time
For Linux systems, use the Linux Deployment Utility to install the latest support pack with the
preconfigured components to the local system. For more information regarding installing a support
pack using the Linux Deployment Utility, see http://www.hp.com/servers/psp.
Configuring the managed system software
The HP SIM Configure or Repair Agents tool configures Linux, HP-UX, and Windows managed
systems to communicate with HP SIM from a Linux CMS.
To run Configure or Repair Agents remotely against multiple systems simultaneously, you must:
•
Have authorizations to run the Configure or Repair Agents tool.
•
Have full CMS administrative rights to modify the HP SIM community strings in the node security
file.
•
Enter root or administrator level user credentials for the target system.
To configure agents remotely using Configure or Repair Agents, see Configuring managed systems
from a Linux CMS.
Setting up Linux managed systems manually
Setting up managed systems related topics
Setting up managed systems from a Windows CMS
Procedure 43 Setting up managed systems
1.
2.
Ensure that HP SIM is installed on the CMS.
Ensure the First Time Wizard has been completed on the CMS.
IMPORTANT: You must run discovery before setting up managed systems. For more
information, see Running a discovery task for more information. Configuring automatic discovery
is part of the First Time Wizard.
3.
Configure the managed system software. For more information, see Configuring the managed
system software using the Configure or Repair Agents feature from the CMS.
Configuring the managed system software using the Configure or Repair Agents
feature from the CMS
The HP SIM Configure or Repair Agents tool is a quick and easy way to configure Windows, Linux,
and HP-UX managed systems to communicate with HP SIM from a Windows CMS.
To run Configure or Repair Agents remotely against multiple systems simultaneously, you must have
authorizations to run the Configure or Repair Agents tool.
You must have full CMS administrative privileges to modify the HP SIM community strings in the
system security file. In addition, you must enter administrator-level user credentials for the target
system.
To configure agents remotely.
Setting up managed systems related topics
Setting up managed systems from a Windows CMS
187
Setting up managed systems from an HP-UX CMS
Procedure 44 Setting up managed systems from an HP-UX Central Management ServerCMS
1.
Understand the basic managed system software for HP-UX.
For HP-UX, the following software, shown with minimum recommended versions, is required
for essential HP SIM functionality to operate. This software is installed by default as part of
the latest HP-UX 11i v2 operating environments, but you might have to install or update it on
HP-UX 11i v1 or older HP-UX 11i v2 environments.
•
T1471AA HP-UX Secure Shell
•
B8465BA HP WBEM Services for HP-UX
The iCAP properties for cells and processors for a complex is collected and displayed, using
HP-UX WBEM. For HP-UX, the following software is required for essential HP SIM functionality
to operate. This software is installed by default as part of the latest HP-UX 11i v3 (11.31), HPUX 11i v2 (11.23), which can be installed on HP 9000 or HP Integrity servers, and HP-UX
11i v1 (11.11), which can only be installed on HP 9000 servers.
•
B9073BA version 08.01.01 iCAP for HP-UX
NOTE:
WBEM providers is only collected under the WBEM.
This WBEM Services bundle contains basic system instrumentation displayed in the HP SIM
Property pages, supporting collection and reporting by HP SIM inventory functionality. To
maximize the value of HP SIM for properties, inventory, and events, see http://www.hp.com/
go/hpsim/providers for the latest WBEM Services bundle.
For the latest WBEM Services bundle, go to http://www.hp.com/go/hpsim/providers.
2.
Ensure the managed system software is installed.
To verify that the minimum required software is installed, log in to the remote system, and run
the following command:
$ swlist –l bundle T1471AA B8465BA OpenSSL
To verify that the optional providers and HP System Management Homepage are installed,
run commands such as:
$ swlist –l bundle LVMProvider WBEMP-LAN-00 SysMgmtWeb SysFaultMgmt
OnlineDiag
3.
Acquire and install the managed system software if not previously installed.
The SSH and WBEM bundles are included on the HP-UX Operating Environment and
Application Release media, as well as part of the HP SIM HP-UX depot downloaded from
http://h18013.www1.hp.com/products/servers/management/hpsim/dl_hpux.html.
For the WBEM providers, see http://h18013.www1.hp.com/products/servers/management/
hpsim/dl_hpux.html .
After you have obtained the depots containing the software, you can install then from the
managed system:
$ swinstall –s <depot_location> OpenSSL
NOTE: B8465BA and B9073BA version 08.01.01 depends on OpenSSL, so you must install
OpenSSL first.
$ swinstall –s <depot_location> T1471AA
$ swinstall –s <depot_location> B8465BA
$ swinstall –s <depot_location> <names of WBEM providers being
installed>
188 Operations
Discovery in HP SIM
Discovery is the process of finding systems in the management domain so that they can be managed
from the CMS by HP SIM.
You can perform discovery only if you have administrative rights.
Automatic discovery
The process that HP SIM uses to find and identify systems on your network and populate the
database with that information. A system must first be discovered to collect data and track system
health status. The primary source for automatic discovery is ping sweeps configured in the automatic
discovery tasks page. Other sources might include receiving events from unknown systems or from
a management processor that has information about a server. Identification automatically runs on
discovered systems.
The option Automatically discover a system when an event is received from it is disabled by default,
but can be enabled by selecting it in the General Settings for All Discoveries section. For discovery
to run, you must enable the default System Automatic Discovery task by selecting Options→Discovery,
selecting the default task, and then clicking Enable. HP recommends editing this task to ensure that
the IP range is correct.
NOTE: Discovery templates do not exist in HP SIM 5.3 or later. Therefore, after upgrading to
HP SIM, 5.3 or later, a disabled discovery task is created for each existing template.
To access the General Settings for All Discoveries section, select Options→Discovery, and then
click Configure general settings. In the section, Do this now to finish the installation, on the
introductory page, click Configure discovery and credentials, or from the Manage section of the
Homepage, click discovery.
Alternatively, you can click Edit, instead of Enable, to edit and save the task. In the Schedule section,
select Automatically execute discovery every, and then set the discovery time. If you disable
automatic discovery, no new automatic discovery is performed until you enable automatic discovery
by visiting the Discovery page and making your selections. For more information about scheduling
automatic discovery, see Configuring automatic discovery.
HP SIM performs automatic discovery using the IP.
Internet Protocol
HP SIM discovers systems running IP when it pings systems in a listed range of addresses. It defaults
to the local subnet, a range that corresponds to the IP addresses assigned to the system where HP
SIM is running. You can change the address list to indicate other systems or segments of the network
that you want HP SIM to discover.
Web Agents are not discovered unless HTTP is enabled on the Global Protocol Settings page in
the HTTP settings section. To enable HTTP, see Protocol settings for information. To ensure that
clusters are discovered in automatic discovery, the cluster IP address and all node addresses must
be listed in the section, Ping inclusion ranges, system (hosts) names, and/or hosts files. To access
this section, click New for a new discovery task, or click Edit to edit an existing discovery task.
HP SIM uses a globally unique system identifier obtained from the system to help identify HP systems
with multiple IP addresses. If no unique identifier can be obtained, the fully qualified DNS names
of the systems are used for each IP. To ensure systems are resolved, for each IP address, the FQDN
names must match.
Event-based automatic discovery
Event-based automatic discovery is disabled by default. You can enable this feature by selecting
Automatically discover a system when an event is received from it. Event-based automatic discovery
adds any systems that send SNMPtraps, WBEM indications, or other events to HP SIM that do not
have a matching IP address in the database. The option, Ping exclusion ranges, and/or hosts files
Discovery in HP SIM 189
(in the General Settings for All Discoveries section), allows the entry of any IP addresses that you
want excluded from event-based automatic discovery. If SNMP is disabled on the Global Protocols
Settings page under Options→Protocol Settings→Global Protocol Settings, then SNMP traps are
ignored. If WBEM is disabled, WBEM indications are also ignored.
NOTE: With the exception of the SNMP Authentication Failure trap, all traps trigger an automatic
discovery.
First discovery
You can start a discovery in the following ways:
•
Execute discovery immediately from the Discovery page, select the System Automatic Discovery
task, click Edit to configure the task for your environment, and then click Run Now. The discovery
process starts immediately. The discovery progress is updated as the systems are discovered,
until the discovery process is complete.
•
Allow sufficient time for a complete discovery and identification to be performed. Times vary,
depending on your network, bandwidth, and discovery settings. In most cases, the discovery
process finds all systems by pinging the network.
Subsequent discoveries
You can run discovery any time from the Discovery page. For subsequent discoveries, you can
specify the subnets or systems to interrogate and the schedule to follow.
For the most comprehensive discovery and identification, select SNMP, WBEM, and HTTP as the
protocols on the Options→Protocol Settings→Global Protocol Settings page. Configure default
community strings and WBEM passwords on the Global Credentials page.
Status indicators let you know when discovery is running, and the column, Last Run, displays
running, the percentage of completion, the number of pings attempted, and the systems processed.
A processed system is one in which the IP address has been either identified or found unresponsive.
However, a processed system is not always added to the database.
Hosts files
Hosts files are used to manually add multiple systems to the HP SIM database, and are usually
used only one time to import systems. You can use an existing hosts file, a file created from the HP
SIM database, or an HP SIM exported hosts file as the basis for adding systems. Typically, the file
contains a listing of the names of systems, system IP addresses, and any alias names that are used
for the system.
Importing the hosts file bypasses the need for immediate discovery. For example, in the case of a
catastrophic system failure, you could import a backup hosts file as the basis for reconfiguring your
management environment and automatically repopulating the database. Adding the systems using
the hosts file utility does not replace systems in the database. For example, if a system listed in the
hosts file has the same IP address as an existing system, the duplicate is ignored. Any systems that
previously existed in the database are not modified.
You can import hosts files from the following sources:
•
The HP SIM database, which imports the system data, creates a hosts file, and sorts the data
types according to your selection
•
Another system that has an existing hosts file
To create and manage hosts files, click Manage hosts files on the Discovery page.
190 Operations
Options for adding a single system
•
Know the IP address or host name of the system. If you know at least one of these, HP SIM
can find the other by validating the information with the Domain Name Service (DNS) for the
network.
•
To add a cluster and nodes, enter each IP address separately.
•
Decide if you want to set the system type, subtypes, or WBEM credentials as well as the
product model.
•
Specify the WBEM settings for the system on the System Protocol Settings page. You can
override the default user name and passwords by selecting use values specified below and
entering appropriate user names and passwords.
•
Specify the SNMP settings for this system to be unique or match the global discovery settings.
The current system default settings appear. If you override the default and specify a different
value, that community string must be supported on the system. If it is not and one of the defaults
is supported, HP SIM reverts back to the default value. When manually adding a single system,
you can modify the following settings:
timeout
The amount of time HP SIM waits for an SNMP response
when it sends a request to the system. The default timeout
value appears. If a response is not received within time
interval, HP SIM might determine that the system does not
support SNMP. Decreasing this value can cause increased
network traffic because the rate of retry attempts is
increased. Use caution when changing this value. A value
of three seconds usually works for a LAN. However, if
systems are connected through a WAN, try a higher value,
for example, 10 seconds.
retries
The number of additional times after the first attempt is
made to communicate with a system before the attempts
stop.
community strings
A community string sets up authentication that enables or
prohibits communication between the managed system
and the CMS. The CMS community string of the must match
the community string of the managed system. Use the
read-only community string to read variables. Use the write
community string to modify variables. Although only one
community is valid for a communication attempt, a system
can belong to multiple communities. However, HP SIM uses
only one community string when communicating with a
system.
NOTE: If an IP address is used to manually add a single system, it must be properly resolved to
a system name for the name to be displayed in the GUI.
Discovery related information
Configuring automatic discovery
When you access the Discovery page, a table displays a list of all available discovery tasks. You
can configure multiple instances of discovery with each instance having its own schedule and set
of inclusion ranges. When a discovery task is executed, the Last Run column is updated to display
its progress, including the percentage of completion.
Automatic discovery and completion percentages are calculated by weighting two factors: the
ping sweep (performed on each host) is 10% of the process; the system identification is 90% of
the process. If no host is found on an IP address, the system identification is considered complete.
For example, you have 100 hosts in your discovery range. If 50 hosts have been pinged, but only
Discovery in HP SIM
191
10 identified, you have: 50/100 * .10 = 0.05 (ping sweep) 10/100 * .90 = 0.09 (identification)
0.05 + 0.09 = 0.14 * 100 = 14% (total completed percentage).
NOTE: You can run only one discovery task at a time. If you select to run more than one discovery
task, the percentage in the Last Run column remains at 0% until the currently running task is complete.
For all automatic discoveries section
The following options are available:
•
Configure general settings
Select this option to configure settings that apply to all discovery tasks. For more information,
see Configuring discovery general settings.
•
Manage hosts files
Select this option to manage hosts files. For more information, see Managing Hosts files.
•
Configure global protocol settings
Select this option to configure global protocol settings. For more information, see Protocol
settings.
NOTE: To discover clusters correctly, you must enable SNMP with the correct security settings
on HP SIM on the target systems.
Actions to take after running discovery section
This section is available only when Insight managed system setup wizard or HP Insight Control
virtual machine management is installed and the available options include:
•
Run the managed system setup wizard
This option is available when Insight managed system setup wizard is installed and takes you
to the Insight managed system setup wizard page to configure managed systems.
Discovery page buttons
From the Discovery page, you can also:
•
Create a new discovery task
Click New and the New Discovery section appears. For more information, see Creating a
new discovery task. For HP recommended discovery tasks, see Recommended discovery tasks.
•
Edit an existing discovery task
Select a task from the table, and click Edit. The Edit Discovery section appears. For more
information, see Editing a discovery task.
•
Enable or disable a discovery task
Select a task and click Disable to disable the schedule of an enabled task. If a task is disabled,
the button changes to Enable. To resume automatic execution of the task, click Enable. For
more information, see Disabling or enabling an existing discovery task.
•
Delete an existing discovery task
Select a task from the table and click Delete. For more information, see Deleting a discovery
task.
•
View Task Results
Displays the task results for the current discovery task.
192 Operations
•
Run a discovery task
Select the task you want to run and click Run Now. When a task is running, the Run Now
button changes to a Stop button. For more information, see Running a discovery task.
•
Stop a discovery task from running
Select the running task and click Stop. For more information, see Running a discovery task.
Discovery related information
Configuring automatic discovery settings of VM guests
If a host and its associated guests are already discovered and the host is licensed with Matrix
Operating Environment, you cannot disable the horizontal flag at the system level.
1. Select Automatically discovery VM Guest(s) when this host is identified.
2. Click Save to save this setting and trigger identification, or click Cancel to save changes.
•
If host IP is included in the horizontal discovery global exclusion range, guest systems will not
be discovered.
•
If host IP is included in the horizontal discovery global exclusion range and is licenses by
Matrix Operating Environment, guest systems will be discovered.
•
If host IP is not included in the horizontal discovery global exclusion range, automatic discovery
of guest systems is enabled at the global level.
•
If host IP is included in the horizontal discovery global exclusion range, and the Automatically
discover VM Guest(s) when this host is identified option on the Discovery - General Settingsti
page, discovery of the guest system is enabled at the global level.
Configuring discovery general settings
Procedure 45 Configuring automatic discovery
1.
2.
In the For all automatic discoveries section, select Configure general settings. The General
Settings for All Discoveries section appears.
Select from the following options:
•
Automatically discover a system when an event is received from it. Enables systems to be
discovered when a trap or some other supported event is received by HP SIM. It uses the
discovery filters and IP address exclusion ranges for additional filtering of these events.
This option is not selected by default.
•
Automatically discover a server when its Integrated Lights Out management processor is
identified. Adds server blades when the server’s management processor is discovered.
The discovered servers are identified as Disabled on the system table view page. The
following information is displayed: server model name, UUID, serial number, server name
and protocols, DeviceType and SubTypes and so on. If the management processor is in
a c-Class enclosure, the option, Discover systems in an enclosure when ProLiant Onboard
Administrator is discovered must be enabled.
•
Automatically discover systems in an enclosure when Onboard Administrator is discovered.
Adds systems identified by the Onboard Administrator even if the systems are not in the
configured discovery range. This option is selected by default.
NOTE: You must select this option to create a VCDomain node and enable virtual
connect functionality.
This option must be selected to add a newly inserted server blade (one that does not exist
in HP SIM database) as a bare metal managed system in the HP SIM database after
receiving the Server Blade Inserted trap. If this option is not selected, the Server Blade
Inserted trap is logged only and the blade is not automatically added to the enclosure.
Discovery in HP SIM
193
•
Automatically discover VM guest(s) when the host is identified. Adds all VM guest systems
to the HP SIM database when the VM host (HPVM VMWare ESX or Microsoft Hyper-V)
system is discovered and identified. This option is selected by default.
If this option is not selected when a VMWare ESX or Microsoft Hyper-V host is discovered,
then guests are not discovered automatically. However, if one of its guests is moved to
another before being discovered in HP SIM and if that guest is discovered later, it is
associated with the old host. To avoid this, either the old host or new host must be identified
before guest is discovered
For automatic identification of virtual machine guests running on a virtual machine host,
the IP address of the guest is required. To acquire the IP address from WBEM Providers,
VMWare tools must be installed on the virtual machine guests.
3.
•
Automatically discover other virtual partitions within the same vPar Monitor when one of
the virtual partitions is identified. This option is selected by default.
•
Automatically discover all nPars within the same complex when one of the nPars is
identified. This option is selected by default.
•
Automatically discover Vmware ESX host server in lockdown enabled mode
In the Ping exclusion ranges, templates and/or hosts files field, specify the IP addresses,
templates, or hosts files containing IP addresses to exclude from the automatic discovery
process. You can also enter Simple or FQDN host names. However, you cannot enter a range
of host names. This field applies to both range-pinging and event-based automatic discovery.
See HP Systems Insight Manager User Guide for more information on entering IP ranges.
IMPORTANT: When discovering clusters, the ping inclusion range must include the IP
addresses of the cluster and the cluster members.
4.
5.
To select the types of systems HP SIM discovers, select Enable discovery filters. For more
information, see Discovery filters for more information.
In the section, Discover the following system types, select the type of systems to be discovered.
When discovering clusters, you must include the server system type, so that the cluster members
are not filtered out.
This option is available only when you select Enable discovery filters.
6.
In the Limit discovery to systems which meet the following criteria section, select from the
following:
•
Any system that matches the above filter
•
All manageable systems (WBEM, SNMP, WMI, WS-MAN, SSH, or HTTP support)
•
Manageable systems with HP agents only
The option, Limit discovery to systems which meet the following criteria is available only when
you select Enable discovery filters.
7.
(Optional) Enter VM hosts IP range that you do not want to include in the automatic discovery
of VM guests.
IP exclusion ranges can consist of the following:
194
•
Single IP address
•
Multiple IP addresses separated by semi-colon
•
Range of IP addresses separated by dash
Operations
8.
To save settings, click OK, or to close the General Settings for All Discoveries section without
saving changes, click Cancel.
If you click OK when discovery filters are enabled but have not selected any system types, the
following error message appears:
You must make at least one system type selection when enabling
filters.
9.
Select System Automatic Discovery. Click one of the following options to schedule it for ongoing
operations or to make other changes: Edit, Enable, View Task Results, or Run Now. If you
would like to create other discovery tasks, click New.
The Discovery page General Settings for All Discoveries section is not protected from multiple users
accessing the page at the same time. The last user to save the settings has his or her settings take
affect. If discovery is in progress and the settings are applied by a different user or the same user,
any remaining systems to be processed have the new settings applied.
Discovery related information
Creating a new discovery task
HP SIM ships includes one default discovery task (System Automatic Discovery). However, you can
create a new discovery task to discover specific systems. For example, if you want to discover
systems in a specific IP address range. You can set the task to run at scheduled times using specific
ping inclusion ranges, templates, or hosts files. For HP recommended discovery tasks, see
Recommended discovery tasks.
Discovery in HP SIM 195
Procedure 46 Creating a discovery task
1.
Select from the following:
•
Discover a group of systems
Default: Select this option to discover more than one system.
a. Required: In the Name field, enter a name for the task.
b. In the Schedule section, select Automatically execute discovery every, and then enter
how often the task runs. The default frequency is once per day. If you clear the
Automatically execute discovery every option, the task is disabled after you create
it.
c. In the Ping inclusion ranges, IPv6 address, system (hosts) names, templates, and/or
hosts files field, specify the IP and IPv6 addresses. However, you cannot include IPv6
address ranges. If you want to use this task to discover SMI-S storage systems, include
the IP address of each SMI CIMOM. You can also enter Simple or FQDN host names.
However, you cannot enter a range of host names. See the HP Systems Insight
Manager User Guide, at http://www.hp.com/go/insightmanagement/sim/docs,
for more information about entering IP ranges. To use an existing hosts file, enter the
hosts file name in the following format: $HostsFileName .
If a hosts file is used, only systems that are accessible and match the discovery filter
criteria are added to the database.
d.
•
Enter comments in the Comments field. Comments entered here are displayed in the
discovery table on the Discovery page.
Discover a single system
Select this option to discover one system. Single system discovery address the system to
the HP SIM database regardless of network accessibility, unless it is not DNS resolvable.
a. Required: In the Name field, enter a name for the task.
b. In the Schedule section, select Automatically execute discovery every, and then enter
how often the task runs. The default frequency is once per day. If you clear the
Automatically execute discovery every option, the task is disabled after you create
it.
c. Enter the system name or IP address in the Enter the system's name or IP address.
d. Enter comments in the Comments field. Comments entered here are displayed in the
discovery table on the Discovery page.
2.
3.
4.
To set system credentials, click Credentials. For more information, see Configuring credentials
for discovery tasks.
To create an associated Configure or Repair Agents task, click Configure/Repair. For more
information, see Configuring Configure or Repair Agents for discovery tasks.
To configure system types, click System Types. For more information, see Configuring system
types for discovery tasks.
NOTE:
5.
System Types is only available when you discover a single system.
To set the criticality of task, click Criticality. Select Critical (default) or Non-Critical.
Click OK.
6.
To save the task, click Save, or to close the New Discovery section and not save any settings,
click Cancel.
NOTE: If you have selected many systems, the following message appears, stating The
automatic discovery task is configured with a large number of
addresses: [NUM]. Click OK to continue, or click Cancel to change the IP address range.
196
Operations
Creating an automatic discovery task using the command line interface
Users with administrative rights can use the mxtask command to create an automatic discovery
task from the CLI.
For information about accessing the manpage, see the HP Systems Insight Manager Command
Line Interface Guide, at http://www.hp.com/go/insightmanagement/sim/docs.
Discovery related information
Configuring credentials for discovery tasks
Discovery task credentials can apply to all systems in the associated discovery task and enable
you to configure default credentials for a subset of your environment.
Sign-in credentials apply to multiple protocols and enable HP SIM to access the managed system.
SNMP credentials enable you to set global-level read community strings. SNMPv3, WBEM/WMI
and WS-MAN are protocol specific credentials.
During the identification process (done automatically during discovery), credentials are tried,
starting with System Credentials. If they do not work, and the Try Others setting is chosen for them,
then Discovery credentials are used. Similarly, if those do not work and the Try Others setting is
chosen, then Global Credentials are tried. As soon as a credential is found that works, Systems
Insight Manager notes that credential as working and continues to use it for regular communications
with the managed system as long as it continues to work. If it should fail, then the process is
repeated the next time identification is run. To see the working credentials for any managed system,
go to the System Credentials page (Options→Security→Credentials→System Credentials). These
working credentials appear in the Credentials that are in use table.
This procedure enables you to set credentials attempted during a discovery task. Perform these
steps from the New Discovery Task or the Edit Discovery Task sections of the Discovery page.
Credentials are applied in the following order:
1. Working (might reference system, discovery, or global credentials)
2. System level protocol specific
3. System level Sign-in
4. Discovery level protocol specific
5. Discovery level protocol Sign-in
6. Global Sign-in
Creating and editing discovery credentials for a single system
NOTE: When configuring credentials for a single system discovery, you are configuring system
credentials for that system, not discovery credentials for the task.
Discovery in HP SIM
197
Procedure 47 Creating and editing discovery credentials for a single system
1.
The following tabs are available in the credentials section:
•
Sign in
This tab enables you to set one credential for all protocols.
•
SNMP
This tab enables you to set one SNMP community string.
For advanced and protocol-specific settings, click Show advanced protocol credentials to
the right of the tabs. The following additional tabs appear.
•
SNMPv3
This tab enables you to set SNMPv3 credentials.
This is not applicable for Windows systems.
•
WBEM/WMI
This tab enables you to set WBEM credentials.
•
WS-MAN
This tab enables you to set WS-MAN credentials.
•
VME
This tab enables you to set VME credentials that were configured on the VMWare vCenter
Server Web Services page during VMWare vCenter Server installation. This is not
available when creating a discovery task until after the VMWare vCenter servers are
discovered.
2.
3.
4.
For each setting on the Sign In, SNMP, SNMPv3, WBEM, / WMI, and WS-MAN tabs, there
is a checkbox that, when checked, indicates to HP SIM that if these credentials should fail for
some reason, then others should be tried in accordance with the numbered list above. For
example, if the Sign-in credential entered here was invalid, and the checkbox was checked,
then the discovery level credentials (if any) would be then tried. This control gives you flexibility
where your credentials are specified, but also carries a risk in performance and might trigger
a security event if many credentials are tried to find one that works.
Click OK, to have data from all the tabs saved for the current session. Depending on the
number of systems, this can take several minutes. The progress of this task can be monitored
by clicking the View Task Results button. Once the task is complete, the System Credentials
page (Options→Security→Credentials→System Credentials) will show the new working
credentials.
To save changes, click Save. Otherwise, the credentials will only be saved for the current
session.
Procedure 48 Deleting system credentials individually
1.
2.
3.
Make all of the credential information for the system blank.
To delete cleared credentials for your current session, click OK. The next time discovery is run,
the working credentials will be redetermined, as described above.
In the next window, for the credentials to be deleted permanently, click Save. Otherwise, the
credentials will only be saved for the current session.
198 Operations
Creating and editing discovery credentials for a group
Procedure 49 Creating and editing discovery credentials for a group
1.
The following tabs are available in the credentials section:
•
Sign in
Enter the user name and password pairs.
Enter as many default user names and password pairs as needed by clicking Add. To
delete user name and password pairs, click Delete beside the pair you want to delete.
Note: HP SIM tries each set of credentials until it finds a set that works, which can cause
server sign-in failures and possibly trigger a security event based on your local security
policy. For example, three failed sign-in attempts can trigger an account lock-out.
•
SNMP
Enter the default read community strings. Click Add to add additional strings or click
Delete to delete existing strings.
For advanced and protocol-specific settings, click Show advanced protocol credentials to
the right of the tabs. The following additional tabs appear.
•
SNMPv3
This tab enables you to set SNMPv3 credentials.
This is not applicable for Windows systems.
•
WBEM/WMI
This tab enables you to set WBEM credentials.
•
WS-MAN
This tab enables you to set WS-MAN credentials.
•
VME
This tab enables you to set VME credentials that were configured on the VMWare vCenter
Server Web Services page during VMWare vCenter Server installation. This is not
available when creating a discovery task until after the VMWare vCenter servers are
discovered.
2.
3.
For each setting on the Sign In, SNMP, SNMPv3, WBEM / WMI, WS-MAN, and VME tabs,
there is a checkbox that, when checked, indicates to HP SIM that if these credentials should
fail for some reason, then others should be tried in accordance with the numbered list above.
For example, if the Sign-in credential entered here was invalid, and the checkbox was checked,
then the global level credentials (if any) would be then tried. This control gives you flexibility
where your credentials are specified, but also carries a risk in performance and might trigger
a security event if many credentials are tried to find one that works.
When you click OK, data from all the tabs is collected and stored so that when discovery is
run, the new credentials can take effect. Depending on the number of systems, this can take
several minutes. The progress of this task can be monitored by clicking the View Task Results
button. Once the task is complete, the System Credentials page
(Options→Security→Credentials→System Credentials) will show the new working credentials.
This will be in affect for the current session only. To have the settings saved to the discovery
task permanently, complete the following step.
4.
In the next window, for changes to be permanent and saved to the discovery task, click Save.
Otherwise, the credentials will only be saved for the current session.
Procedure 50 Deleting discovery credentials for a group
1.
Click Delete beside the credential that you want to delete.
Discovery in HP SIM 199
2.
3.
4.
When a discovery credential is found to work for a system, a working credential is created
for the system that references the discovery credential. If you selected to delete a discovery
credential, select how you want to delete any working references to the discovery credentials.
•
Delete the discovery credentials and any working references to them. This prevents HP
SIM from using the credential to communicate with the system.
•
Copy the credentials to all systems referencing them, and then delete the discovery
credentials. This creates a copy of the discovery credentials as system credentials for any
systems with a working reference to the discovery credentials, enabling HP SIM to continue
to use the credentials to communicate with the system.
To delete cleared credentials, click OK. The next time discovery is run, the working credentials
will be redetermined, as described above.
In the next window, for the credentials to be deleted permanently, click Save. Otherwise, the
credentials will only be saved for the current session.
Related topics
Global credentials
System credentials
Sign-in credentials
SNMP credentials
SNMPv3 credentials
WS-Man credentials
Single sign on credentials
SSH credentials
WBEM credentials
Configuring Configure or Repair Agents for discovery tasks
This procedure enables you to configure Configure or Repair Agents settings when creating or
editing a discovery task for a single system. Perform these steps from the New Discovery Task or
the Edit Discovery Task sections of the Discovery page.
200 Operations
Procedure 51 Creating a Configure or Repair Agents task
1.
To disable the Configure or Repair Agents task, select Configure newly managed systems
when they are first discovered in the Configure Managed Systems section. For more information,
see Configuring managed systems.
a. Select Configure newly managed systems when they are first discovered..
b. To specify credentials to configure the managed system for WBEM / WMI, SNMP, and
SSH, select from the following:
•
Use sign in credentials
This account must be an account with administrative privileges.
•
Use these credentials
Select this option to use another user name and password pair other than the one
entered into HP SIM.
c.
d.
Under Configure WBEM / WMI, select from the following:
•
Create subscriptions to WBEM events
•
Send a test WBEM / WMI indication to this instance of Systems Insight Manager to
make sure that events appear in Systems Insight Manager events lists
•
Use an HP SIM WBEM certificate (good for 10 years) rather than
username/password to manage the system
Under Configure SNMP, select from the following:
•
Set read community string
•
Set traps to refer to this instance of HP SIM
A read/write SNMP community string is automatically created on a managed
Windows system’s SNMP settings.
•
e.
Send a test SNMP trap to this instance of Systems Insight Manager to make sure
events appear in the HP SIM event lists
Under Configure secure shell (SSH) access, select from the following:
•
Host based authentication
All users from this instance of HP SIM are authenticated on the managed system.
•
Each user has to be authenticated on the managed system
Each user must be authenticated on the managed system.
f.
2.
3.
Select Set trust relationship to "Trust by Certificate" to set a trust relationship between
managed systems and the CMS. This enables HP SIM users to connect to HP SMH,
Onboard Administrator, management processors, and Version Control Agent using the
HP SIM certificate for authentication.
Click OK to have data saved for the current session.
To save changes, click Save. Otherwise, the credentials will only be saved for the current
session.
Discovery related information
Configuring system types for discovery tasks
This procedure enables you to configure system types when creating or editing a discovery task
for a single system. Perform these steps from the New Discovery Task or the Edit Discovery Task
sections of the Discovery page.
Discovery in HP SIM 201
Procedure 52 Configuring system types
1.
2.
3.
4.
Enter the System Type.
Enter up the System subtype. You can enter to up to eight subtypes.
Enter the Product model.
Click OK.
Discovery related information
Editing a discovery task
Procedure 53 Editing a discovery task
1.
Select from the following:
•
Discover a group of systems
Default: Select this option to discover more than one system.
a. Required: In the Name field, enter a name for the task.
b. In the Schedule section, select Automatically execute discovery every, and then enter
how often the task runs. The default frequency is once per day. If you clear the
Automatically execute discovery every option, the task is disabled after you create
it.
c. In the Ping inclusion ranges, system (hosts) names, and/or hosts files field, specify
the IP addresses. If you want to use this task to discover SMI-S storage systems,
include the IP address of each SMI CIMOM. You can also enter Simple or FQDN
host names. However, you cannot enter a range of host names. See HP Systems
Insight Manager User Guide, at http://www.hp.com/go/insightmanagement/sim/
docs, for more information about entering IP ranges. To use an existing hosts file,
enter the hosts file name in the following format: $HostsFileName .
If a hosts file is used, only systems that are accessible and match the discovery filter
criteria are added to the database.
d.
•
Enter comments in the Comments field. Comments entered here are displayed in the
discovery table on the Discovery page.
Discover a single system
Select this option to discover one system. Single system discovery address the system to
the HP SIM database regardless of network accessibility, unless it is not DNS resolvable.
a. Required: In the Name field, enter a name for the task.
b. In the Schedule section, select Automatically execute discovery every, and then enter
how often the task runs. The default frequency is once per day. If you clear the
Automatically execute discovery every option, the task is disabled after you create
it.
c. Enter the system name or IP address in the Enter the system's name or IP address.
d. Enter comments in the Comments field. Comments entered here are displayed in the
discovery table on the Discovery page.
2.
3.
4.
To set system credentials, click Credentials. For more information, see Configuring credentials
for discovery tasks.
To create an associated Configure or Repair Agents task, click Configure/Repair. For more
information, see Configuring Configure or Repair Agents for discovery tasks.
To configure system types, click System Types. For more information, see Configuring system
types for discovery tasks.
NOTE:
202 Operations
System Types is only available when you discover a single system.
5.
To save the task, click Save, to run the task immediately, click Run Now, or to close the New
Discovery section and not save any settings, click Cancel.
NOTE: If you have selected many systems, the following message appears, stating The
automatic discovery task is configured with a large number of
addresses: [NUM]. Click OK to continue, or click Cancel to change the IP address range.
Discovery related information
Disabling or enabling an existing discovery task
You can disable or enable an existing discovery task. If you disable a task, the Schedule column
displays a message that the task is disabled. You might want to disable a task if you know your
network is not going to change, or if you want to limit network traffic. If a task is enabled, the
Schedule column displays the schedule for the task.
NOTE: Manually running a disabled task by selecting the task and then clicking Run Now does
not enable the task for future discoveries.
Procedure 54 Disabling or enabling discovery tasks
1.
2.
Select the task you want to disable or enable.
Click Disable to disable a task, or if the task is already disabled, click Enable to resume the
automatic execution of a task.
Discovery related information
Deleting a discovery task
You can delete discovery tasks that are no longer necessary. You cannot delete the System Automatic
Discovery task. If you select this task, the Delete button is disabled.
Procedure 55 Deleting discovery tasks
1.
2.
Select Options→Discovery. The Discovery page appears.
Select tasks, and then click Delete. A confirmation box appears.
If you selected to delete a discovery task for a group of systems and it has user name and
password credentials set, select how you want to delete them. Select from the following:
3.
•
Delete the credentials and any working references to them
•
First copy the credentials to all systems referencing them, then delete the global credentials
To delete this task, click OK, or to cancel the deletion process, click Cancel.
Discovery related information
Running a discovery task
You can manually select and run any existing discovery task at any time. For example, if you add
a new system that has not been discovered, you can manually run a discovery task to discover
and manage the system. You can also stop a task that is running.
Procedure 56 Running a discovery task
•
Select the discovery task that you want to run, and then click Run Now. The task runs
immediately. The View Tasks Results section appears below the list of discovery tasks so that
the progress and results of the running tasks can be monitored.
The Run Now button changes to Stop when a task is running. To stop a task, select the task and
click Stop.
Discovery related information
Discovery in HP SIM 203
Discovery related information
Related procedures
Configuring automatic discovery
Configuring automatic discovery settings of VM guests
Configuring discovery general settings
Creating a new discovery task
Configuring credentials for discovery tasks
Configuring Configure or Repair Agents for discovery tasks
Editing a discovery task
Disabling or enabling an existing discovery task
Deleting a discovery task
Running a discovery task
Creating a new hosts file
Editing a hosts file
Deleting a hosts file
Adding systems in a hosts file to the HP SIM database
Related topics
Recommended discovery tasks
Identification overview
Discovery filters
Data collection
Discovery filters
Discovery filters prevent or enable certain system types from being added to the database through
automatic discovery. When you want to discover systems of a certain type, using filters is much
easier than specifying the IP addresses of each individual system. Discovery filters do not apply to
manually added systems.
You can access discovery filters in one of the following ways:
•
From the Discovery page, select Options→Discovery. From the Automatic tab, click Configure
general settings, and then select Enable discovery filters.
•
From the Home page, in the Manage section, click Tune and filter discovery. The Discovery
page appears. In the For all automatic discoveries section, select Configure general settings,
and then select Enable discovery filters.
•
From the introductory page, in the Do this now to complete the installation section, click
Configure discovery and credentials. The Discovery page appears. Click Configure general
settings and then select Enable discovery filters.
To disable filters, clear the Enable discovery filters checkbox. To enable filters, select the Enable
discovery filters checkbox, and then select the system types that you want to discover.
To access and modify discovery filters, you must have administrative rights. If discovery filters are
enabled, only systems of the selected types are added to the database through automatic discovery.
Because all tasks operate on systems that exist in the database, tasks do not run on any system
until the filter criteria has been met and that system has been added to the database. Filters do
not affect any systems already discovered, even if the systems change to a type that no longer
matches the current filter. If discovery filters are disabled, automatic discovery discovers systems
according to the General Settings for All Discoveries section. See Configuring discovery general
settings for more information about configuring discovery filters.
If you do not discover the HP systems that you expect to find, ensure that the Insight Management
Advisors are installed and running correctly on the target systems. In addition, verify that the SNMP
Community Strings settings and WBEM user name and passwords in HP SIM and on the agents
for systems that are not discovered or configured correctly. See Protocol settings for more
information.
204 Operations
Discovery related information
Managing Hosts files
Hosts files are used to manually add multiple systems to the HP SIM database and are generally
used only one time to import systems.
To use a hosts file to specify systems for an automatic discovery, add the hosts file name to the
Ping inclusion ranges, system (hosts) names, and/or hosts files section of the Discovery page under
the Configure general settings section. Enter the following statement: $Hosts_filename where
Hosts_filename is the name of the hosts file that you want to use.
For more information about hosts files, see the "Hosts Files" section in the Discovery in HP SIM
section.
From the Hosts Files section, you can:
•
Create new hosts files
Click New. The New Hosts File section appears. For more information, see Creating a new
hosts file.
•
Edit a hosts file
Select the hosts file to edit, and then click Edit. The Edit Hosts File section appears. For more
information, see Editing a hosts file.
•
Delete a hosts file
Select the hosts file to delete, and then click Delete. A confirmation box appears. For more
information, see Deleting a hosts file.
•
Add a hosts file to the HP SIM database
Select the hosts file to add, and then click Add Systems Now. For more information, see Adding
systems in a hosts file to the HP SIM database.
Discovery related information
Creating a new hosts file
NOTE: For keywords that contain more than one word, such as "management processor," enclose
the full keyword in double quotation marks. Quotation marks are optional for single keywords,
like server.
NOTE:
For clusters, ensure that the cluster and its members are defined in the hosts file.
Procedure 57 Creating hosts files
1.
2.
3.
Required: In the Name field, enter a name for the new hosts file.
Under Initialize contents with, select one of the following:
•
Sample host file. This option loads the contents into the Contents window.
•
Systems loaded from the central management server, sorted by:. This option loads the
systems managed by HP SIM into the Contents window. From the dropdown list, select
one of the following: IP address, System name, System type and then by IP address, or
System type and then by system name.
•
Systems loaded from hosts file. This option reads the contents of the specified file and
displays it in the Contents window. Enter the file name and location (for example, c:\
doc.txt), or click Browse to locate the hosts file. Click Browse to search for a file.
If you did not select Sample hosts file, click Initialize Now to install the hosts file. Otherwise,
enter the contents of the hosts file in the Contents section. Simple or FQDN host names can
be entered in the hosts file. However, no range of host names is allowed.
Discovery in HP SIM 205
4.
To save the hosts file, click OK, or to cancel any changes you have made, click Cancel.
Hosts file format
The format for a valid hosts file line is:
IP_ADDRESS [DNS_NAME] SYSTEM_NAME
Where:
IP_ADDRESS.
Is a valid IP address.
DNS_NAME.
Specifies an optional DNS name parameter. DNS_NAME
consists of multiple parts, separated by dots. The right-most
part is a top-level domain (.com, .net, .etc) and the left parts
are subdomains. Some examples include:
mysystem.mydomain.com and
system1.cup.lab.net>.
SYSTEM_NAME.
Is the name of the system
With this format, the following hosts file lines are valid:
1.2.3.4 mySystem.mydomain.com mySystem
2.3.4.5 mySystem
The following lines are not valid:
1.2.3.4/
mySystem/
mySystem.mydomain.com/
Precede comment lines with the # character:
# This is a comment line
1.2.3.4 mySystem.mydomain.com mySystem
For more information about hosts file extensions, see the HP Systems Insight Manager User Guide,
at http://www.hp.com/go/insightmanagement/sim/docs.
Discovery related information
Editing a hosts file
Procedure 58 Editing hosts files
1.
2.
3.
Select hosts files.
Click Edit. The Edit Hosts File section appears.
In the Replace contents with section, select one of the following:
•
Sample host file. This option loads the contents into the Contents window.
•
Systems loaded from the central management server, sorted by:. This option loads the
systems managed by HP SIM into the Contents window. From the dropdown list, select
one of the following: IP address, System name, System type and then by IP address, or
System type and then by system name.
•
Systems loaded from hosts file. This option reads the contents of the specified file and
displays it in the Contents window. Enter the file name and location (for example, c:\
doc.txt), or click Browse to locate the hosts file. Click Browse to search for a file.
4.
Click Replace Now, or enter the changes in the Contents section.
5.
To save the hosts file, click OK, or to cancel any changes you have made, click Cancel.
Discovery related information
206 Operations
Deleting a hosts file
NOTE:
Delete hosts files only if you no longer need them or if you are creating a new hosts file.
Procedure 59 Deleting hosts files
1.
2.
3.
4.
Ensure that the selected hosts file is not in use. A hosts file is not in use when:
•
There are no references to it in the Ping exclusion ranges, templates and/or hosts files
section of the general settings page.
•
There are no references to it in the Ping inclusion ranges, templates, and/or hosts files
section of every existing discovery task.
Select hosts files.
Click Delete. A confirmation box appears.
Click OK to delete the hosts files, or click Cancel to cancel the delete process.
Discovery related information
Adding systems in a hosts file to the HP SIM database
Procedure 60 Adding hosts files
1.
2.
Select hosts files.
Click Add Systems Now.
HP SIM reads in the hosts file and adds the systems.
Discovery related information
Identification overview
The identification process follows automatic or manual system discovery and identifies the following
information about the discovered system:
•
Management protocol the system uses (for example, SNMP, WBEM, HTTP, SSH, or
WS-Management)
NOTE:
By default, HP SIM supports WS-Management identification on the standard SSL
port 443. The addition of WS-Management support does not affect existing identification or
discovery of a management processor using other protocols such as WBEM or SNMP.
WSMAN:1.0 appears as a Management Protocol along with all other supported management
protocols on the system page System tab of the System page.
•
Type of system (for example, server, client, management processor, storage, switch, router,
or cluster)
•
Product name of the system
•
Operating system name, type, and version
•
Associations, such as a management processor in server
During identification, remote enclosures have a generic name (format: Encl_SerialNumber) assigned
to them until one server from every enclosure is discovered and identified. Then, the enclosures
contain the name of the enclosure assigned to the enclosure.
HP SIM collects and recognizes the product ID and serial number, and most importantly, how to
handle the server-to-management processor associations using the UUID instead of the serial number.
The following processes occur sequentially for each system that is identified by HP SIM:
1. Identify the type of system, supported protocols, and limited attributes (such as the operating
system type).
2. Filter out systems that do not meet the filter criteria (if the system is new).
Discovery in HP SIM 207
3.
4.
Obtain additional data, such as license data or Web agents that might be written to the
database directly, and attributes that can be queried (such as CPU and memory data).
Run association algorithms based on system type identified in the first step.
For newly found automatically discovered systems, before the system is added to the database,
any discovery filters are applied. If a system does not match the discovery filter, it is not added to
the database, and no additional tasks or requests are made to that system. After the system passes
the filter, it is added to the database. At this time, the system is available to polling tasks, collections,
or other operations.
NOTE:
Discovery filters do not apply to manually discovered systems.
HP SIM performs initial hardware and software status polling and initial data collection on newly
added systems. See Hardware status polling, Software status polling, and Data collection for more
information about each task. The information about the systems is stored in the database.
The time to complete the discovery and identification processes varies with the network size and
resources. All necessary tasks are predefined in HP SIM. Predefined tasks cannot be removed from
the system, but they can be disabled if necessary. You can also create a new identification task
and schedule it to run when you want to update identification information from systems. See the
HP Systems Insight Manager User Guide, at http://www.hp.com/go/insightmanagement/sim/
docs, for information on managing default tasks.
By default, HP SIM runs the System Identification task once per day and when new systems are
discovered. Most users do not need to schedule identification tasks to run more than once per day.
If VMware tools are installed on the guest, the UUID, host name, and primary IP address of the
virtual machine host are collected. If VMware tools are not installed, only the UUID is collected. In
this case, the virtual machine guest is named as >VMHost_Name<_>Display Name<, where
VMHost_Name is the name of the guest host system, and Display Name is the display name of
the guest in VMware Virtual Infrastructure Client.
Initial identification
After a system is newly discovered or rediscovered, HP SIM attempts to identify it. The discovery
task is not 100% complete until all the systems have been identified.
Identifying systems
To identify systems between discoveries, select Options→Identify Systems. The Identify Systems
page appears. From this page, select target systems to add. See Creating a task for more information
about selecting targets.
Discovery related information
Managing system types
System Type Manager is a utility that modifies the default behavior of identification. System Type
Manager enables you to customize the type and product name of third-party systems using rules
based on responses to SNMP lists from systems on your network.
IMPORTANT: For most HP systems, the system type and product name cannot be modified.
Identification can be customized based on SNMP System OIDs for all other fields. Manufacturers
assign unique system OIDs to their SNMP-instrumented products. System Type Manager enables
you to customize identification by creating rules that map these system OIDs to product categories
and names. You must have administrative rights to use System Type Manager.
208 Operations
To access the Manage System Types page, select Options→Manage System Types. From this page,
you can:
•
Create a New Rule.
Click New. The New rule section appears. See Creating STM rules for more information.
•
Edit an Existing Rule.
Select the rule you want to edit, and then click Edit. See Editing STM rules for more information.
•
Delete an Existing Rule.
Click Delete. A confirmation box appears. to delete the rule, click OK, or to cancel the deleting
and return to the Manage System Types page, click Cancel. See Deleting STM rules for more
information.
Related information
Creating STM rules
Procedure 61 Creating a new SNMP rule
1.
(Required) Enter the System object identifier information. Retrieve the system object identifier
from a target system on your network by clicking Retrieve from system. The Retrieve from
system section appears. The System object identifier field is required.
a.
b.
c.
d.
e.
2.
In the Object identifier field, enter the object identifier.
In the Community string field, enter the community string if other than public, which is the
default. to retrieve data, the community string of the target system and the HP SIM server
must match to retrieve data.
In the Target hostname or IP address field, enter the IP address of the system you want
to search.
Click Get response to show the Response SNMP data type and the Response value.
To close the Retrieve from system section, click OK, and place the response value in the
System object identifier, or Object value fields, or both.
Enter the System object identifier compare rule. Click the down arrow and select the appropriate
rule. In most cases, this rule is match. You can set it to starts with if you know that a class of
systems has system object identifiers that start with the value you have entered.
Discovery in HP SIM 209
3.
Specify MIB variable object identifier by clicking Retrieve from MIB. The Retrieve from MIB
section appears.
You might need to perform this action if you have systems that return the same system object
identifier that you would like to classify as different products based on an SNMP variable that
returns a different value for each class. For example, if you have Windows NT servers from
different vendors that return the same Windows NT system object identifier, you can specify
rules using the Windows NT OID as the OID and a vendor-specific MIB variable and value
combination to create separate rules for each vendor.
a.
b.
c.
Click the down arrow in the MIB definition file name box to select the MIB definition file.
Click the down arrow in the MIB variable name box to select the MIB variable name.
To close the Retrieve from MIB section, click OK, and place the MIB variable object
identifier information in the field.
4.
Select the Object value by clicking Retrieve from system. The Retrieve from system section
appears.
a. Enter the Object identifier, Community string, and Target hostname or IP address.
b. Click Get response to view the Response SNMP data type and the Response value.
c. To close the Retrieve from MIB section, click OK, and place the information in the Object
value field.
5.
Select the Object valueData type by clicking the down arrow and selecting either string or
integer.
Select the Object valueCompare rule by clicking the down arrow.
Enter a Priority (applies only if there is more than one rule with the same system object
identifier).
(Required) In the System type field, click the down arrow, and then select the system type.
In the Subtype field, click the down arrow, and then select the system subtype.
(Required) In the Product model field, enter the product name for the new rule.
In the Custom management page field, enter a URL. The URL displays this web page as a
system link on the System Page of systems identified using this rule. Enter the special keywords
$ipaddress and $hostname anywhere in this URL. They are replaced by the actual IP
address or host name of the system when the link is placed on the System Page.
Click Launch to verify that you can browse to the URL.
To save the new rule, click OK, or to cancel all changes and close the New rule section, click
Cancel.
6.
7.
8.
9.
10.
11.
12.
13.
Command line interface
Use the mxstm command to add SNMP rules from the command line. For assistance with this
command, see the HP-UX or Linux manpage by entering man mxstm at the command line. See
the HP Systems Insight Manager Command Line Interface Guide, at http://www.hp.com/go/
insightmanagement/sim/docs, for more information about the command and how to access the
manpage.
210
Operations
Related information
Editing STM rules
Edit an existing SNMP rule using System Type Manager to change the priority, system type, subtype,
or custom management page.
NOTE: Changing the priority on this page reorders the priorities of all other rules with the same
OID such that all rules with the same system OID have a unique priority ranging from one to the
number of rules with the same system OID.
NOTE:
All steps are optional.
Procedure 62 Editing SNMP rules
1.
2.
3.
4.
5.
In the Priority field, change the priority.
In the System type field, click the down arrow to change the system type.
In the Subtype field, click the down arrow to change the subtype.
In the Custom management page field, change the URL. Click Launch to verify that you can
browse to the URL launch page.
To save changes and return to the Manage System Types page, click OK, or to return to the
Manage System Types page without saving any changes, click Cancel.
Command Line Interface
Use the mxstm command to edit SNMP rules from the command line. For assistance with this
command, see the HP-UX or Linux manpage by entering man mxstm at the command line. See
the HP Systems Insight Manager Command Line Interface Guide, at http://www.hp.com/go/
insightmanagement/sim/docs, for more information about the command and how to access the
manpage.
Related information
Deleting STM rules
1.
2.
3.
4.
Select Options→Manage System Types. The Manage System Types page appears.
Select the rule to delete.
Click Delete. A confirmation box appears.
Click OK to delete the rule, or click Cancel to cancel the deletion process.
Command Line Interface
Use the mxstm command to delete SNMP rules from the command line. For assistance with this
command, see the HP-UX or Linux manpage by entering man mxstm at the command line. See
the HP Systems Insight Manager Command Line Interface Guide, at http://www.hp.com/go/
insightmanagement/sim/docs, for more information about the command and how to access the
manpage.
Related information
Related information
Related procedures
Creating STM rules
Deleting STM rules
Editing STM rules
Related topic
Managing system types
Discovery in HP SIM
211
Users and authorizations
NOTE: Users that have been added to the Central Management Server (CMS) cannot view or
manage systems until authorizations have been configured for them.
NOTE: Command line tools provided by HP-UX and Linux (such as ls and df) are run as root
by default. For security reasons, you might want them to run as a specific user to avoid inadvertently
allowing unauthorized access to a user.
HP SIM enables you to configure authorizations for specific users or user groups. Authorizations
give the user access to view and manage systems. Each authorization specifies a user or user
group, a toolbox, and a system or system group. The specific set of tools that can be run on a
system that is specified in the assigned toolbox.
You must plan which systems each user will manage and which specific set of tools each user is
authorized to execute on managed systems. A user with no toolbox authorizations on a particular
system cannot view or manage that system.
Authorizations are cumulative. If a user is authorized for Toolbox1 and Toolbox2 on the same
system, the user is authorized for all tools in both Toolbox1 and Toolbox2 on that system. Similarly,
a user authorized for the All Tools toolbox on a system requires no other toolbox authorizations
on that system because the All Tools toolbox always includes all tools.
See the following guidelines for setting up user names and authorizations in the following sections:
212
•
Creating new users
•
Creating new user groups
•
Creating new toolboxes
•
Creating new authorizations
Operations
User authorization templates
The Users and Authorizations tabs offer the following options:
•
Add, edit, and delete users and user groups, and view and print user reports. Select
Options→Security→Users and Authorizations→Users.
•
Add, edit, and delete toolboxes, and view and print toolbox reports. Select
Options→Security→Users and Authorizations→Toolboxes.
•
Add, update, and delete authorizations, and view and print authorization reports. Select
Options→Security→Users and Authorizations→Authorizations.
NOTE: By default, users created in HP SIM can access HP Storage Essentials with limited read
privileges. You can change the permission settings by following the instructions and links on the
Users, Toolboxes, and Authorizations tabs.
Users and authorizations related information
Creating new authorizations
NOTE: To create authorizations with individual systems, be sure the systems have been discovered
and are accessible in the database.
NOTE:
You cannot directly create new authorizations for group-based users.
Procedure 63 Creating new authorizations
1.
2.
In the Select dropdown list, select User(s) or UserGroup(s), and then select the users or groups
in the box. This field is required.
In the Enter authorizations for the selected user(s) section, select one of the following options:
•
Copy all authorizations of this user or [template]
Select a user or template from the dropdown list.
•
Manually assign toolbox and system/system group authorizations
a. In the Select Toolbox(es) section, select the toolboxes to include.
Users and authorizations
213
b.
c.
In the Select Systems list box, the two default system groups (All Managed Systems
and CMS) appear. Select one of these groups, or to select systems for the
authorization, click Add to display the Add Systems section.
In the Add systems by selecting from section, select one of the following:
1) Collection
Select a collection, and click View contents.
If you want to use the entire collection as your selection, select Select
"collection name" itself. This option creates a system group based on the
currently displayed contents of the collection.
a. Optional: To enable the authorization to automatically be updated, without
user intervention when a collection is changed, select Automatically track
changes. If this collection changes, so does the authorization.
b. Optional: Select Do not track changes. If this collection changes, the
authorization will not change. If this option is selected, you must manually
update the authorization after a collection has changed by using the Update
button on the Authorizations tab.
214
Operations
NOTE: These two selections are only available if a collection of systems
is selected and the Select "collection name" itself option is selected.
You must select one option or the other. The default selection is based on
the DynamicAuthorizations_AutoUpdateDefaultValue property setting in the
globalsettings.props file. The default is set to Yes. This is reflected
in the Select Systems list box in the New Authorizations section with [Auto]
appended to the entry. For example, if you selected All Systems and chose
to have it automatically updated, All Systems 001 [Auto] would be displayed
in the Select Systems box.
You can continue to add systems and collections and can enable automatic
updates for each selected collection. Since automatic updates for any
authorization apply to all authorizations using the same selected collection,
changing the setting for one affects any other authorization using the same
collection. Therefore, during system selections, if you select a group already
associated with an automatically updating authorization, the option
Automatically track changes. If this collection changes, so does the
authorization is preselected. Likewise, if an authorization that does not
automatically update is associated with a collection, the option Do not track
changes. If this collection changes, the authorization will not change is
preselected.
c.
If you want to select all individual systems from the collection, select the
checkbox at the top of the table view in the column heading to select all
systems.
NOTE: This selection creates a separate authorization for each selected
system.
d.
To save system selections, click Apply, or to return to the New Authorizations
section without saving changes, click Cancel.
After clicking Apply, a message appears based on the options selections.
To return to the New Authorizations section, click OK.
2)
Search
Enter a system name and click Search, or select a system from the list, and then
click Search.
a. Select systems.
b. Click Apply, or to return to the New Authorizations section without saving
changes, click Cancel.
After clicking Apply, a message appears based on the options selections.
Click OK to return to the New Authorizations section.
A system group is a group of systems based on a system collection that is used for
authorizations. Authorizations that use system groups are updated automatically when a
change is made to the system collection that the system group is based upon. The option Do
not track changes. If this collection changes, the authorization will not change must not be
selected for the authorizations to be updated automatically.
If you selected individual systems of a collection, each selection populates the list box and is
selected for inclusion in the authorization. If you selected a collection and the collection has
been used previously in an authorization, a message appears stating that a system group for
the collection exists and will be updated with current source collection content. This condition
affects all authorizations associated with that collection. When a collection is used for the first
Users and authorizations
215
time, no message appears. A system group with the name of the collection followed by three
numbers, usually (001) appears in the Select Systems dropdown list and is selected.
3.
To save the new authorization and close the New Authorizations section, click OK, or, if you
do not want to create the authorization, click Cancel.
NOTE:
When you add CMS tools to any other system, a warning appears alerting you that the
authorization just added contains an HP SIM-based tool in the toolbox and that the CMS server
was not selected. The warning also states that the authorization was created but might not authorize
the user on all the selected tools. Some tools in HP SIM are used to manage HP SIM itself. For
example, discovery or viewing the HP SIM audit log. This error means that one or more of these
tools were in a selected toolbox and the CMS was not one of the selected systems. To correct this
error, select the CMS as one of the target systems.
NOTE:
When upgrading to HP SIM 5.x from any other version of HP SIM, any system groups
that the user created are migrated, but become top-level collections. To manage these system
groups, use the feature to edit a collection and update an authorization. For more detailed
information, see Editing system and cluster collections and Updating authorizations.
Command line interface
Users with administrative rights can use mxngroup to create and manage system groups from the
command line interface (CLI).
Users with administrative rights can use the mxauth command to add authorizations from the CLI.
NOTE:
Users must have the User can configure CMS security access such as creating, modifying
or removing other users option selected when their account is set up for them to be able to use the
mxngroup and mxauth commands.
For information about accessing the manpage, see the HP Systems Insight Manager Command
Line Interface Guide, at http://www.hp.com/go/insightmanagement/sim/docs.
Related information
Creating new toolboxes
Create a toolbox to configure a group of tools for each user who has access. Toolboxes are set
up so that some users can use certain tools but not others. For example, an administrator has access
to more tools than a user.
The HP SIM Tools category includes tools that are related to configuration rights on the HP SIM
server itself. In previous versions of HP SIM, these rights were only enabled to full configuration
rights users. With HP SIM 5.2 or later, any user can be granted these rights if needed based on
an authorization. These tools include: Delete Systems in HP SIM, Edit any user tasks in HP SIM,
Edit HP SIM Notification Settings, Edit HP SIM Reports, Edit Shared Collections in HP SIM, Edit
Systems in HP SIM, Modify HP SIM Events, Run HP SIM Discovery, and View HP SIM Audit Log.
NOTE: The toolbox name must start with an alphabetic character followed by alphanumeric
characters, embedded blank characters, underscore (_), or dash (-) and must be less than or equal
to 16 characters in length.
Procedure 64 Adding toolboxes
1.
2.
3.
216
In the Name field, enter a name for the new toolbox. This field is required.
In the Description field, enter a description for the toolbox.
To enable the toolbox and all authorizations created with this toolbox, select Toolbox is
enabled.
Operations
4.
To display a list of tools in the available tools list, in the Show tools in category field, select a
category. In the available tools list, select the tools to be assigned to this toolbox, and then
click
.
The selected tools appear in the Toolbox contents list. To remove a tool from the associated
tools list, you can select a tool displayed in the Toolbox contents list, and then click
.
NOTE: For users with operator rights and user rights to clear, delete, assign events, and
add comments to events, you must select Configuration Tool from the Show tools in category
dropdown list. Then, select Clear Events, Delete Events, Assign Events, and Comment Events
as necessary, and then click
5.
to add them to the Toolbox contents.
To save the new toolbox and close the New Toolbox Section, click OK. To save the settings
without closing the New Toolbox Section, click Apply, or to cancel the new toolbox creation
and return to the Toolboxes Section, click Cancel.
Command line interface
Users with administrative rights can use the mxtoolbox command to add toolboxes from the CLI.
To modify the contents of the toolbox, refer to the mxtool commands.
NOTE:
Users must have the User can configure CMS security access such as creating, modifying
or removing other users option selected when their account is set up for them to be able to use the
mxngroup and mxauth commands.
For information about accessing the manpage, see the HP Systems Insight Manager Command
Line Interface Guide, at http://www.hp.com/go/insightmanagement/sim/docs.
Users and authorizations related information
Creating new users
Create a new user account to sign-in to HP SIM. The account must be valid on the operating system
(including Active Directory on Windows) on the Central Management Server (CMS) and is
authenticated by the CMS. You must know the operating system user account name of the user
you are adding, but it is not necessary to know the password.
Procedure 65 Creating a new user
1.
Required: In the Sign-in name [on central management server(CMS)] field, enter the operating
system login account name to be used to sign in to HP SIM. This field is required.
NOTE: The user cannot sign-in to HP SIM if the account is not a valid login. The account is
not validated until the user attempts to sign-in to HP SIM.
2.
3.
4.
5.
6.
Optional: In the Full name field, enter the user's full name.
Optional: If you are using Windows, in the Phone field of the Pager Information Section, enter
the pager phone number. If the Phone number field is left blank, the paging information is not
saved. This field does not apply to user groups.
Optional: In the E-mail address field, enter the user's e-mail address.
In the Copy all authorizations of this user or [template] field, select a template
(administrator-template, operator-template, or user-template) or sign-in account that already
has the predefined authorizations that you want to assign to the sign-in account you are
creating.
For user accounts that must be able to create, modify, or delete other accounts in the Central
management server security configuration right Section, select User can configure CMS security
access such as creating, modifying or removing other users. If you selected an existing user
with administrative rights or the administrator template in the previous step, this option is
automatically selected.
Users and authorizations
217
7.
Under the Sign-In IP Address Restrictions Section, in the Inclusion ranges field, enter the IP
addresses of the systems you want this user to be able to use as a client browsing this CMS.
If you list multiple IP addresses, separate them with a semicolon (;). Each range is a single IP
address or two IP addresses separated by a dash (-). The IP addresses must be entered in the
standard dotted decimal notation, for example, 15.1.54.133. Any spaces surrounding the
semicolons or dashes are ignored. Spaces are not allowed within a single IP address in the
dotted decimal notation. Enter 0.0.0.0 to prevent a user from logging in through a remote
system.
IMPORTANT: If browsing from the CMS, ensure all IP addresses of the CMS are properly
included. If browsing to localhost, ensure the loopback address 127.0.0.1 is also included.
8.
In the Exclusion ranges field, enter the IP address of the systems that should be excluded from
management by this user or user group. Use the same format as in the previous step for
Inclusion ranges. Enter 0.0.0.0 to prevent a user from logging in through a remote system.
NOTE:
Ensure that your inclusion and exclusion ranges do not overlap.
9.
To override IP login restrictions of all other user groups with the current user group's IP login
restriction, select Override IP Login Inclusion/Exclusion Range.
10. To save and close the New User Section, click OK. The new user account is created. To save
and keep the New User Section open, click Apply, or to cancel the creation of this user, click
Cancel.
Command line interface
Users with administrative rights can use the mxuser command to create users from the command
line interface (CLI). To modify the contents of the toolbox, refer to the mxtool comands.
NOTE:
Users must have the User can configure CMS security access such as creating, modifying
or removing other users option selected when their account is set up for them to be able to use the
mxuser command.
See the HP Systems Insight Manager Command Line Interface Guide, at http://www.hp.com/go/
insightmanagement/sim/docs, for information about accessing the manpage.
Users and authorizations related information
Updating authorizations
This option is only available for authorizations using system groups based on a collection. It enables
the contents of a system group to be updated to the current contents of its source collection. All
authorizations using this system group (collection) are updated.
218
Operations
Procedure 66 Updating an authorization
1.
In the Show dropdown list, select changes, current contents, or updated contents.
•
changes
Describes the specific changes that occur to the system group if updated. Systems to Add
shows new systems to be added to the system group and added to all authorizations
based on the system group. Systems to Remove shows current systems to be removed
from the system and removed from all authorizations using the system group. Systems
Unchanged shows a list of systems that are unaffected by the update. They remain
unchanged in the system group and all authorizations based on the system group.
•
current contents
Displays the current contents of the system group.
•
updated contents
Displays what the contents of the system group will be after updating. This option applies
to authorizations based on this system group.
2.
To update the authorization, click Update Contents, or to cancel the update, click Cancel.
Command line interface
Users with administrative rights can use mxngroup to update system groups from the command
line interface (CLI). However, if there are edits to the system group from the CLI, there is no affect
on the source collection. To modify the contents of the toolbox, refer to the mxtool command.
NOTE:
Users must have the User can configure CMS security access such as creating, modifying
or removing other users option selected when their account is set up for them to be able to use the
mxngroup and mxauth commands.
For information about accessing the manpage, see the HP Systems Insight Manager Command
Line Interface Guide, at http://www.hp.com/go/insightmanagement/sim/docs.
Users and authorizations related information
Editing toolboxes
You can change toolboxes to modify the contents, name, and description of the toolbox.
NOTE: The All Tools toolbox cannot be edited. While, the Monitor Tools toolbox can be edited,
but only the set of tools contained in the toolbox can be changed.
Procedure 67 Editing a toolbox
1.
Change the appropriate setting. For more detailed information about each field, see Creating
new toolboxes.
NOTE:
2.
New custom tools are located under Tools→Custom Tools.
To save changes, click OK, or to cancel the changed, click Cancel.
Command line interface
Users with administrative rights can use the mxtoolbox command to modify toolboxes from the
CLI. To modify the contents of the toolbox, refer to the mxtool command.
NOTE:
Users must have the User can configure CMS security access such as creating, modifying
or removing other users option selected when their account is set up for them to be able to use the
mxtoolbox and mxtool commands.
Users and authorizations
219
For information about accessing the manpage, see the HP Systems Insight Manager Command
Line Interface Guide, at http://www.hp.com/go/insightmanagement/sim/docs.
Users and authorizations related information
Creating new user groups
User groups must exist in the operating system.Members of user groups in the operating system
can sign-in to HP SIM and inherit the group's attributes for configuration rights, sign in IP address
restrictions, and authorizations. When a group's configuration rights, sign in IP address restrictions,
or authorizations are changed, this change is immediately reflected for all current members of the
group.
With configuration rights, the user inherits the highest setting. With sign-in IP address restrictions,
the user inherits all entries. With authorizations, the user inherits all authorizations.
NOTE: A user's group membership is determined at sign-in. If a user's group membership changes
in the operating system, it is not reflected in HP SIM until the next time the user signs in to HP SIM.
By using nesting, you can add a group as a member of another group. Groups are nested together
to consolidate member accounts and reduce replication traffic. Refer to the HP Systems Insight
Manager User Guide, at http://www.hp.com/go/insightmanagement/sim/docs, for more detailed
information.
Procedure 68 Creating a new user group
1.
2.
3.
4.
5.
In the Group name (on central management server) field, enter the operating system group
name to be used for signing in to HP SIM. This field is required.
In the Full name field, enter the full name for the group. This name appears in the table under
the Users tab.
In the Copy all authorizations of this user or [template] field, select a template or sign in that
already has the predefined authorizations that you want to assign to the group you are creating.
For more information about default user templates, see the HP Systems Insight Manager User
Guide, at http://www.hp.com/go/insightmanagement/sim/docs.
For user accounts that must be able to create, modify, or delete other accounts in the Central
management server security configuration right Section, select User can configure CMS security
access such as creating, modifying or removing other users. If you selected an existing user
with administrative rights or the administrator template in the previous step, this option is
automatically selected.
Under the Sign-In IP Address Restrictions Section, in the Inclusion ranges field, enter the IP
addresses of the systems you want this user to be able to use as a client browsing this CMS.
If you list multiple IP addresses, separate them with a semicolon (;). Each range is a single IP
address or two IP addresses separated by a dash (-). The IP addresses must be entered in the
standard dotted decimal notation, for example, 15.1.54.133. Any spaces surrounding the
semicolons or dashes are ignored. Spaces are not allowed within a single IP address in the
dotted decimal notation. Enter 0.0.0.0 to prevent a user from logging in through a remote
system.
IMPORTANT: If browsing from the CMS, ensure all IP addresses of the CMS are properly
included. If browsing to localhost, ensure the loopback address 127.0.0.1 is also included.
6.
7.
In the Exclusion ranges field, enter the IP address of the systems that should be excluded from
management by this user or user group. Use the same format as in the previous step for
Inclusion ranges. Enter 0.0.0.0 to prevent a user from logging in through a remote system.
To save and close the New User Group Section, click OK. To save and keep the New User
Group Section open, click Apply, or to cancel to close the New User Group Section without
saving the new group, click Cancel .
220 Operations
Command line interface
Users with administrative rights can use the mxuser command to create a user group from the
command line interface (CLI). To modify the contents of the toolbox, refer to the mxtool command.
NOTE:
Users must have the User can configure CMS security access such as creating, modifying
or removing other users option selected when their account is set up for them to be able to use the
mxuser command.
For information about accessing the manpage, see the HP Systems Insight Manager Command
Line Interface Guide, at http://www.hp.com/go/insightmanagement/sim/docs.
Users and authorizations related information
Deleting authorizations
CAUTION: If all authorizations are deleted, no user, not even a user with administrative rights,
can view or manage any systems.
Procedure 69 Deleting authorizations
1.
2.
3.
Select the authorizations to be deleted.
Click Delete. A confirmation box appears.
To delete the authorizations, click OK, or to cancel the deletion process and return to the
Authorizations Section, click Cancel.
Authorizations cannot be directly deleted for group-based users. Instead, delete the
authorizations for the user group of the group-based user.
NOTE:
When deleting the last authorization using a system group, other than the default All
Managed Systems of CMS system groups, the system group is also deleted.
Command line interface
Users with administrative rights can use the mxngroup command to delete system groups using
the CLI. To modify the contents of the toolbox, refer to the mxtool command.
NOTE:
Users must have the User can configure CMS security access such as creating, modifying
or removing other users option selected when their account is set up for them to be able to use the
mxngroup and mxauth commands.
See the HP Systems Insight Manager Command Line Interface Guide, at http://www.hp.com/go/
insightmanagement/sim/docs, for information about accessing the manpage.
Users and authorizations related information
Deleting toolboxes
CAUTION:
NOTE:
When a toolbox is deleted, all of the associated authorizations are also deleted.
The All Tools toolbox and the Monitor Tools toolbox cannot be deleted.
Procedure 70 Deleting a toolbox
1.
2.
3.
Select the toolboxes to be deleted.
Click Delete. A confirmation box appears.
To delete the toolboxes, click OK, or to cancel the deletion process, click Cancel.
The toolbox and all associated authorizations are permanently deleted.
Users and authorizations 221
Command line interface
Users with administrative rights can use the mxtoolbox command to delete toolboxes from the
CLI. To modify the contents of the toolbox, refer to the mxtool command.
NOTE:
Users must have the User can configure CMS security access such as creating, modifying
or removing other users option selected when their account is set up for them to be able to use the
mxtoolbox and mxtool commands.
See the HP Systems Insight Manager Command Line Interface Guide, at http://www.hp.com/go/
insightmanagement/sim/docs, for information about accessing the manpage.
Users and authorizations related information
Editing users and user groups
In the event a user account or user group must be modified, you can edit it from the Users tab on
the Users and Authorizations page.
NOTE:
If a group's configuration rights or sign-in IP address restrictions are changed, these
changes are immediately applied to all current members of the group. If a group name is edited,
none of its current members are affected, other than displaying the new group name.
NOTE: A group-based user account can be edited only to convert to an individual user account
and is not reversible.
222 Operations
Procedure 71 Editing a user account or user group
1.
Change the appropriate setting.
a. Required: In the Sign-in name [on central management server(CMS)] field, enter the
operating system login account name to be used to sign in to Systems Insight Manager.
This field is required.
NOTE: The user cannot sign-in to Systems Insight Manager if the account is not a valid
login. The account is not validated until the user attempts to sign-in to Systems Insight
Manager.
b.
Optional: In the Domain (Windows® domain for sign-in name) field, enter the Windows
domain name for the login name if the CMS is running a Windows operating system. If
left blank, the CMS system name is used as the domain.
NOTE: If the user account was migrated from Insight Manager 7, the Domain (Windows®
domain for login name) field associates a placeholder domain with the user. If the user
receives pages, this field must be edited to include a valid domain on your network.
c.
d.
e.
Optional: In the Full name field, enter the user's full name.
For user accounts that must be able to create, modify, or delete other accounts in the
Central management server security configuration right Section, select User can configure
CMS security access such as creating, modifying or removing other users. If you selected
an existing user with administrative rights or the administrator template in the previous
step, this option is automatically selected.
Under the Sign-In IP Address Restrictions Section, in the Inclusion ranges field, enter the
IP addresses of the systems you want this user to be able to use as a client browsing this
CMS. If you list multiple IP addresses, separate them with a semicolon (;). Each range is
a single IP address or two IP addresses separated by a dash (-). The IP addresses must
be entered in the standard dotted decimal notation, for example, 15.1.54.133. Any
spaces surrounding the semicolons or dashes are ignored. Spaces are not allowed within
a single IP address in the dotted decimal notation. Enter 0.0.0.0 to prevent a user from
logging in through a remote system.
IMPORTANT: If browsing from the CMS, ensure all IP addresses of the CMS are properly
included. If browsing to localhost, ensure the loopback address 127.0.0.1 is also
included.
f.
2.
In the Exclusion ranges field, enter the IP address of the systems that should be excluded
from management by this user or user group. Use the same format as in the previous step
for Inclusion ranges. Enter 0.0.0.0 to prevent a user from logging in through a remote
system.
To save and close the Edit User Section, click OK. The new user account is created. To save
and keep the Edit User Section open, click Apply, or to cancel the modifications for this user,
click Cancel.
The user or group changes are saved.
Command line interface
Users with administrative rights can use the mxuser command to modify users or user groups from
the CLI.
NOTE:
Users must have the User can configure CMS security access such as creating, modifying
or removing other users option selected when their account is set up for them to be able to use the
mxuser command.
Users and authorizations 223
For more information about accessing the manpage, see the HP Systems Insight Manager Command
Line Interface Guide, at http://www.hp.com/go/insightmanagement/sim/docs.
Users and authorizations related information
Authorization reports
Generate an Authorizations Report to view and print authorizations. The Authorizations Report is
tailored to the current filtered view. For example, if user is selected in the Authorizations for box,
a report is generated for only for the user selected. If (none) is selected in the Select name dropdown
list, a report is generated for everything selected in the Authorizations box.
NOTE:
To sort the report information in ascending or descending order, click the appropriate
column heading. The column heading that includes the arrow is the column by which the report is
sorted. If the arrow is pointing up, the report is sorted in ascending order. If the arrow is pointing
down, the report is sorted in descending order.
The following information about authorizations appears in the Authorizations Report window,
along with the date and time of the report:
•
User/User Group
•
Toolbox
•
System
•
Auto
Procedure 72 Generating and printing an authorizations report
1.
2.
(Optional) Select a name from the Select name dropdown list.
To print the report, select File→Print.
The Authorizations Report is printed.
Command line interface
Users with administrative rights can use the mxngroup command to generate and run system
group reports from the CLI. to modify the contents of the toolbox, refer to the mxauth command.
NOTE:
Users must have the User can configure CMS security access such as creating, modifying
or removing other users option selected when their account is set up for them to be able to use the
mxngroup and mxauth commands.
See the HP Systems Insight Manager Command Line Interface Guide, at http://www.hp.com/go/
insightmanagement/sim/docs, for information about accessing the manpage.
Users and authorizations related information
Toolbox reports
For detailed information about a toolbox, you can generate and print a toolbox report.
NOTE:
To sort the report information in ascending or descending order, click the appropriate
column heading. The column heading that includes the arrow is the column by which the report is
sorted. If the arrow is pointing up, the report is sorted in ascending order. If the arrow is pointing
down, the report is sorted in descending order.
The following information about all toolboxes appears in the Toolboxes Report window, along
with the date and time of the report:
•
Toolbox
•
Enabled
224 Operations
•
Tools
•
Description
Procedure 73 Generating and printing a toolbox report
•
Select File→Print to print the report.
The toolbox report is printed.
Command line interface
Users with administrative rights can use the mxtoolbox command to generate and run reports
from the CLI. To modify the contents of the toolbox, refer to the mxtool command.
NOTE:
Users must have the User can configure CMS security access such as creating, modifying
or removing other users option selected when their account is set up for them to be able to use the
mxtoolbox and mxtool commands.
See the HP Systems Insight Manager Command Line Interface Guide, at http://www.hp.com/go/
insightmanagement/sim/docs, for information about accessing the manpage.
Users and authorizations related information
Deleting users and user groups
If an HP SIM user account or user group is deleted from the operating system, or disabled or locked
out, and the user is already signed in to HP SIM, the signed-in user is not affected. Therefore, to
remove a signed in user from HP SIM, the user account must be deleted from within HP SIM.
Deleting the user account from HP SIM forces the user to sign out if he or she is already signed in
to HP SIM.
When deleting a user group, all members of the group lose membership in that group, which
causes those users' authorizations, configuration rights, and login IP address restrictions to be
updated based on their new group memberships. Users that are no longer members of any user
group are deleted from HP SIM.
CAUTION: Deleting a user or user group prevents the user or group from signing-in and removes
all associated authorizations and tasks that are owned by that user or user group.
NOTE:
You cannot remove the last user account with administrative rights.
Procedure 74 Deleting user accounts or user groups
1.
2.
3.
Select the users or groups to be deleted.
Click Delete. A confirmation box appears.
to delete the selected users or user groups, click OK, or to cancel the deletion process and
return to the Users Section, click Cancel . Deleting a user group also deletes all members of
the group, and a second confirmation box appears, listing which users will be deleted. To
continue and delete all listed users, click OK, or to cancel the deletion process and return to
the Users Section, click Cancel.
The users, user groups, associated authorizations, and tasks are permanently deleted.
Command line interface
Users with administrative rights can use the mxuser command to modify users and user groups
from the CLI. To modify the contents of the toolbox, refer to the mxuser command.
NOTE:
Users must have the User can configure CMS security access such as creating, modifying
or removing other users option selected when their account is set up for them to be able to use the
mxuser command.
Users and authorizations 225
See the HP Systems Insight Manager Command Line Interface Guide, at http://www.hp.com/go/
insightmanagement/sim/docs, for information about accessing the manpage.
Users and authorizations related information
System groups (CLI)
A system group is a group of systems used solely for authorizations. System groups can be managed
directly from the CLI using the mxngroup command, or they can be managed indirectly through
the GUI.
Managing system groups from the GUI
A system group is created when an authorization is created using a system collection. This system
group is named after the collection with three digits appended, usually 001 (for example, All Racks
001). The system group contains the systems that were displayed during system selection and is
saved when the authorization is created.
NOTE: Any additional changes to the system collection do not affect the system group or
authorizations unless updated by one of the following options.
The content of the system group is updated with the current contents of the collection when:
•
Another authorization is created using the collection
•
An authorization using the system group is updated
•
Using mxngroup from the CLI
In the first two cases, the current contents of the collection appear for verification.
When deleting authorizations, a system group no longer used in any authorization is deleted.
Managing system groups from the CLI using mxngroup
System groups can be created directly using the mxngroup command. When system groups are
created using the CLI, a top-level collection is created and named after the system collection with
three digits appended, usually 001. The collection contains the systems in the system group only
when the system group is first added. Later modifications are not reflected in the collection.
NOTE:
Any additional changes to the system group or collection do not affect the other, unless
updated by one of the following options or by using the GUI as previously described. This means
that changes to the collection do not affect authorizations, and changes to the system group do
not affect the collection view unless specifically updated.
The content of the system group can be updated with the current contents of the collection when:
•
Another authorization is created using the collection.
•
An authorization using the system group is updated.
•
Using mxngroup from the CLI by entering:
mxngroup <groupname> -u
CAUTION:
This command does not display the systems in the collection. To display the updated
contents of the system group, use mxngroup -lm -g <groupname>.
CAUTION: Setting up a periodic task to dynamically update a system group is not recommended.
A collection based on system attributes can be compromised, adversely affecting authorizations
in HP SIM if those attributes are based on a nonsecure protocol (such as SNMP) or are maintained
by a user with user rights. Additionally, the collection itself can be modified by a user with user
rights, which also adversely affects authorizations.
When deleting authorizations, a system group no longer used in any authorizations is deleted.
226 Operations
Users and authorizations related information
User and user group reports
For detailed information about users and user groups, you can generate and print a report.
NOTE:
To sort information in ascending or descending order, click the appropriate column
heading. The column heading that includes the arrow is the column by which the report is sorted.
If the arrow is pointing up, the report is sorted in ascending order. If the arrow is pointing down,
the report is sorted in descending order.
The following summary of user information appears in the Users Report window, along with the
date and time of the report:
•
User/User Group
•
Configure CMS Security
•
Pager Configured
•
IP Sign-In Restrictions
•
Full Name
Procedure 75 Generating and printing a user account or user group report
•
To print the report, select File→Print.
The user report is printed.
Command line interface
Users with administrative rights can use the mxuser command to create user and user group
reports from the CLI. To modify the contents of the toolbox, refer to the mxuser command.
NOTE:
Users must have the User can configure CMS security access such as creating, modifying
or removing other users option selected when their account is set up for them to be able to use the
mxngroup and mxauth commands.
See the HP Systems Insight Manager Command Line Interface Guide, at http://www.hp.com/go/
insightmanagement/sim/docs, for information about accessing the manpage.
Users and authorizations related information
Users and authorizations related information
Related procedures
Creating new users
Creating new user groups
Creating new toolboxes
Creating new authorizations
Editing users and user groups
Editing toolboxes
Deleting users and user groups
Deleting toolboxes
Deleting authorizations
User and user group reports
Toolbox reports
Authorization reports
Updating authorizations
System groups (CLI)
Users and authorizations 227
Directory Services
The Directory Groups tool is used to determine a system's membership in a Windows domain,
organizational unit (OU), or group. Before using the Directory Groups tool, you must first configure
the directory server parameters on the Directory Server Configuration page. After you configure
the directory server, the Directory Groups tool must be configured with the distinguished name
(DN) of the desired container objects in the directory.
Table 31 Directory Services
Name
Directory Server Configuration
See Configuring directory servers.
Directory Groups
See Configuring directory groups.
Description
Access
Used to configure directory server
Select Options→Directory
settings, including the network name, Services→Directory Server
port, and credentials to access the
Configuration.
directory server.
Used to enter the complete
select Options→Directory
distinguished name (DN) of one or
Services→Directory Groups.
more containers, organizational units
(OU), or group objects in the
directory.
Related information
Configuring directory servers
Procedure 76 Configuring the Directory Service
1.
2.
Required: Enter the network name or IP address of the directory server in the Server Name
field. Multiple systems can be specified by separating each system with a semicolon (;). This
action enables a backup to be specified if a system cannot be contacted. For example, if the
first system cannot be contacted, the second system in the list is tried.
Select either Use SSL or Use Global Catalog for the Port Configuration setting.
The port configuration flag is preset to use SSL and to specify the default Lightweight Directory
Access Protocol (LDAP) SSL port of 636 in the Port field. The global catalog flag is cleared
by default. Selecting and clearing the SSL or global catalog flags changes the port number
to the default values.
The global catalog communicates through LDAP, but it does so over a different set of ports:
3368 and 3269 for SSL. The global catalog contains a read-only copy of all objects in the
Active Directory, spanning multiple domains, but only a small subset of object attributes.
Configuring a global catalog here can provide a simple solution for multidomain sites. You
can configure the directory attributes replicated to the global catalog, but the desired attributes
are enabled by default.
NOTE: HP recommends selecting Use SSL so that user name and password credentials are
encrypted. If this option is cleared, the directory server certificate is treated as a trusted system
certificate and can be imported using the existing HP SIM GUI or command line interface
(CLI).
3.
Required: Enter the port number of the directory server.
The port number is preset to use SSL in the Port Configuration field and to specify the default
LDAP SSL port of 636 in the Port field.
4.
5.
6.
7.
In the User Name field, enter the user name to authenticate to the directory server. Write
access for this account is not required. An empty field indicates that an anonymous connection
should be used. Any password entered is ignored.
In the Password field, enter the password for the user name specified.
In the Password Verify field, reenter the password for the user name specified.
Click Test connection to verify the connection is successful using current settings.
228 Operations
8.
Click OK to save the current settings.
After configuring the directory server parameters, you must configure the containers and groups
that contain the computer objects of interest. See Configuring directory servers for information
about configuring directory group parameters.
Related information
Configuring directory groups
After configuring the directory server parameters, you must configure the containers and groups
that contain the computer objects of interest.
Procedure 77 Configuring directory groups
1.
2.
3.
4.
5.
Enter the Distinguished Name (DN) for the Group 1.
Optional: If you want to search subtrees, select Search. This applies only to container and OU
objects, not directory group objects, and only to those OU objects that are more than one
level deep. If this option is selected, HP SIM searches the entire depth of the specified branch.
A match is based on the full DNS name of the system. If HP SIM does not have the full DNS
name of a system, a match is considered successful if the short system name matches (using
the CN attribute of the object) and no other partial match occurs. Systems having only an IP
address available as the system name will fail unless the IP address is the name in the directory
object.
Optional: To add additional groups, click Add. Repeat steps 4 through 6 for each group.
Optional: To delete a group, click Delete next to the group to be deleted.
Click Run Now.
Related information
Related information
Related procedures
Configuring directory servers
Configuring directory groups
Related topic
Directory Services
Global credentials
Global credentials can apply to all systems and enable you to configure default, environment-wide
credentials. Sign-in credentials apply to multiple protocols and enable HP SIM to access the
managed system. SNMP credentials enable you to set global level read community strings.
During the identification process (done automatically during discovery), credentials are tried,
starting with System Credentials. If they do not work, and the Try Others setting is chosen for them,
then Discovery credentials are used. Similarly, if those do not work and the Try Others setting is
chosen, then Global Credentials are tried. As soon as a credential is found that works, HP SIM
notes that credential as working and continues to use it for regular communications with the
managed system as long as it continues to work. If it should fail, then the process is repeated the
next time identification is run. To see the working credentials for any managed system, go to the
System Credentials page (Options→Security→Credentials→System Credentials). These working
credentials appear in the Credentials that are in use table.
Global credentials 229
Procedure 78 Configuring global sign-in credentials
1.
In the Sign-in Credentials Section, enter the user name and password pairs.
Enter as many default user names and passwords as needed by clicking Add. A maximum of
10 different usernames and passwords can be entered. To delete user name and password
pairs, click Delete beside the pair you want to delete.
NOTE: HP SIM tries each set of credentials until it finds a set that works, which can cause
server sign-in failures and possibly trigger a security event based on your local security policy.
For example, three failed sign in attempts can trigger an account lock-out.
2.
3.
4.
In the SNMP Credentials section, enter the default read community strings. Click Add to add
additional strings or click Delete to delete existing strings.
In the SNMPv3 Credentials section, enter SNMPv3 protocol specific properties. Security Name
and the Security level are required fields and based on the Security Level selected, the
Authentication protocol, and Authentication Passphrases and simmilarly, the Privacy Protocol
and the Privacy Passphrases must be populated. Optional properties include the Engine ID,
Context Engine ID, and Context Name.
Click OK to save changes.
Procedure 79 Deleting global credentials
1.
2.
Click Delete beside the credential that you want to delete.
When a global credential is found to work for a system, a working credential is created for
the system that references the global credential. If you selected to delete a global credential,
select how you want to delete any working references to the global credentials.
•
Delete the global credentials and any working references to them. This prevents HP SIM
from using the credential to communicate with the system.
•
Copy the credentials to all systems referencing them, and then delete the global credentials.
This creates a copy of the global credentials as system credentials for any systems with
a working reference to the global credentials, enabling HP SIM to continue to use the
credentials to communicate with the system.
Related topics
System credentials
Configuring credentials for discovery tasks
Credentials used in HP SIM
System credentials
The System Credentials page is launched as a tool and accesses the task wizard for system selection.
If you are not authorized to configure system credentials on the selected systems, you cannot run
the tool.
System Credentials is included in the Quick Launch menu by default. To customize the Quick Launch
menu, click Customize in the Quick Launch menu.
During the identification process (done automatically during discovery), credentials are tried,
starting with System Credentials. If they do not work, and the Try Others setting is chosen for them,
then Discovery credentials are used. Similarly, if those do not work and the Try Others setting is
chosen, then Global Credentials are tried. As soon as a credential is found that works, HP SIM
notes that credential as working and continues to use it for regular communications with the
managed system as long as it continues to work. If it should fail, then the process is repeated the
next time identification is run. To see the working credentials for any managed system, go to the
System Credentials page (Options→Security→Credentials→System Credentials). These working
credentials appear in the Credentials that are in use table.
Credentials are applied in the following order:
230 Operations
1.
2.
3.
4.
5.
6.
Working (might reference system, discovery, or global credentials)
System level protocol specific
System level Sign-in
Discovery level protocol specific
Discovery level protocol Sign-in
Global Sign-in
Columns in the "Credentials that are in use" table
•
System Name
Might be listed more than once if HP SIM is using more than one access type for the system.
•
Access Type
The way HP SIM is using the credential to access the managed system. If Access Type equals
None, then HP SIM has no working credential and cannot access the system. If a specific
protocol is listed, then HP SIM has a working credential for that protocol. If Access Type equals
Sign-in is listed, then HP SIM is using the Sign-in credential (for example, the user name and
password pair) to access the system, possibly for multiple protocols.
•
Credential
The user name of the user name and password pair that is the working credential or, Certificate
if the HP SIM authenticates itself to the system using a WBEM or WMI certificate. If more than
one user name is the same in Global or Discovery credentials, a number is appended to the
displayed user name in the table that indicates which it is in the series. This number is used
to distinguish the credentials for display purposes only.
•
Source
Where the credential was configured. System credentials are configured on the system level.
Global credentials are configured at the global level. Discovery credentials are configured at
the discovery task level and the name of the task is included. For example, Discovery: System
Automatic Discovery. Certificates list Systems Insight Manager as the source.
Viewing, editing, and deleting system credentials
Procedure 80 Viewing all potential system credentials for a system
For each system that was selected in the system credentials table, this table displays all credentials
that can be tried during identification.
• To view the credentials, select systems and click View all credentials.
If there are multiple credentials for a system, the credentials are listed in the order that they
will be tried. Also note that the rightmost column indicates if the system is configured to try
additional credentials if the configured credential fails. If it is not, then it is possible that a
correct credential might not be tried.
System credentials
231
Procedure 81 Editing system credentials either individually or as a group
1.
The following tabs are available on the Edit System Credentials page:
•
Sign in
This tab enables you to set one credential for all protocols.
•
SNMP
This tab enables you to set one SNMP community string.
For advanced, and protocol-specific settings, click Show advanced protocol credentials
to the right of the tabs. The following additional tabs appear.
•
SNMPv3
This tab enables you to set SNMPv3 specific security parameters.
•
WBEM/WMI
This tab enables you to set
•
WS-MAN
This tab enables you to set WS-MAN credentials.
•
SSH
This tab enables you to configure SSH credentials.
•
Single Sign On
This tab enables you to set the trust by certificate relationship.
•
VME
This tab enables you to set VME credentials that were configured on the VMWare vCenter
Server Web Services page during VMWare vCenter Server installation. This is not
available when creating a discovery task until after the VMWare vCenter servers are
discovered.
2.
3.
4.
5.
On each tab, you can either set credentials for all the selected systems, or set credentials for
protocols individually for each system by selecting the appropriate radio control. A maximum
of 10 systems can be edited individually at one time.
For each setting on the Sign-in, SNMP, WBEM / WMI, WS-MAN, and VME tabs, there is a
checkbox that when checked indicates to HP SIM that if these credentials should fail for some
reason, then others should be tried in accordance with the numbered list above. For example,
if the Sign-in credential entered here was invalid, and the checkbox was checked, then the
discovery level credentials (if any) would be then tried. This control gives you flexibility where
your credentials are specified, but also carries a risk in performance and might trigger a
security event if many credentials are tried to find one that works.
For some settings on the WBEM / WMI, SSH, and Single Sign-On tabs, HP SIM needs one-time
administrator or root access to the managed system to make the configuration update. In these
situations an extra Section appears underneath the tabbed box labeled Additional credentials
required to save the configurations for WBEM, SSH and/or Single Sign-On: If the Sign-in
credentials you have already entered have administrator or root capabilities, you need take
no additional action. But if they do not, then you must enter a special credential that has the
necessary access capabilities. This credential must be the same for all the affected systems.
When you click OK, data from all the tabs is collected and identification is run so that the
new credentials can take effect. Depending on the number of systems, this can take several
minutes. The progress of this task can be monitored at Tasks & Logs→View Task Results. When
the task is complete, the System Credentials page can be refreshed and the new working
credentials should appear in the table.
232 Operations
Procedure 82 Deleting system credentials
1.
The following tabs are available on the Edit System Credentials page:
•
Sign in
This tab enables you to set one credential for all protocols.
•
SNMP
This tab enables you to set one SNMP community string.
For advanced, and protocol-specific settings, click Show advanced protocol credentials
to the right of the tabs. The following additional tabs appear.
•
SNMPv3
This tab enables you to set SNMP3v specific security parameters.
•
WBEM/WMI
This tab enables you to set WBEM credentials.
•
WS-MAN
This tab enables you to set WS-MAN credentials.
•
SSH
This tab enables you to configure SSH credentials.
•
Single Sign On
This tab enables you to set the trust by certificate relationship.
•
VME
This tab enables you to set VME credentials that were configured on the VMWare vCenter
Server Web Services page during VMWare vCenter Server installation. This is not
available when creating a discovery task until after the VMWare vCenter servers are
discovered.
2.
3.
Make all of the credential information for the system blank. For multiple systems, you must
make all of the credentials for each system blank.
To delete cleared credentials, click OK.
Sign-in credentials
Sign-in credentials are protocol independent. For performance reasons, a maximum of 10 systems
can be edited individually at one time.
System credentials 233
Procedure 83 Configuring sign-in credentials for specific systems
1.
Choose one of the following options:
•
Replace each selected system sign-in credentials with the following
Use this option to replace sign-in credentials for selected systems.
a. Enter the user name and password.
b. To use other credentials if the assigned credentials fail, select If these credentials fail,
try other credentials that may apply. Click the Learn more link for additional
information. By default this box is not selected, unless you have upgraded HP SIM.
•
Replace the selected system's sign-in credentials individually as follows
Use this option to add new credentials, or to modify or delete existing credentials
individually for selected systems. This option is not available when a single system is
selected.
a. Enter the user name and password for the individual systems.
b. To use other credentials if the assigned credentials fail, check Try others. On new
installations, this is not selected by default. However, for upgrades, the box is selected
for migrated systems. This option appears for each password entered.
2.
To save changes and start identification in the background, click OK. To cancel changes, click
Cancel.
Related information
Single sign on credentials
The Single Sign On tab enables you to set the trust by certificate relationship to connect to the HP
SMH, Onboard Administrator, iLO management processor, and HP Version Control Agent using
the HP SIM certificate for authentication.
Procedure 84 Configuring Single Sign On credentials
1.
2.
3.
4.
Click Show advanced protocol credentials.
Select the Single Sign On tab.
Configure Single Sign-On for each selected system by selecting Set Trust relationships to "Trust
by Certificate". Requires additional credentials so that Configure or Repair Agents can be run
on the target systems.
(Optional) If you selected any system for Trust by Certificate, the Additional credentials required
to save the configurations for WBEM, SSH, and/or Single sign-On Section appears. Select
from:
a. Use sign-in credentials entered in HP SIM. These credentials must be for an account with
administrator or root access on the selected system.
b. Use the following credentials for all systems. Enter the user name, password,, and domain
credentials to use for all selected systems.
These Configure or Repair Agents credentials apply to the WBEM, SSH, and Single Sign
On protocols. You must enter them only once and they are pre-populated on each tab.
5.
To save changes and start the Configure or Repair Agents task (followed by identification) in
the background, click OK>. To cancel changes, click Cancel
Related information
SNMP credentials
One set of SNMP community strings can be applied to the set of selected systems or each system
can set its own community string.
234 Operations
Procedure 85 Configuring SNMP community strings for a specific systems
1.
2.
To set SNMP community strings, click the Configure SNMP checkbox. Here the second and
third read only community strings and Trap community strings are applicable only for iLO4.
Select from:
•
Replace each selected system's SNMP community string with the following
Use this option to replace sign-in credentials for selected systems.
a. Enter the Read community string.
b. To use other credentials if the assigned credentials fail, select If these credentials fail,
try other credentials that may apply. Click the Learn more link for additional
information. By default this box is not selected, unless you have upgraded Systems
Insight Manager.
•
Replace the selected system's SNMP community string) individually as follows
Use this option to specify sign-in credentials individually for selected systems.
a. Enter the Read community string for the individual systems.
b. To use other credentials if the assigned credentials fail, check Try others.
To delete SNMP credentials, you must leave the read community string blank.
3.
To enable the write community string, select Enable write and enter the Write community string.
This is disabled by default.
This option is not available from the New Discovery Task page.
4.
To save changes and start identification in the background, click OK. To cancel changes, click
Cancel.
Related information
SNMPv3 credentials
The SNMPv3 tab enables you to configure SNMPv3 protocol support. HP SIM must collect certain
SNMPv3 protocol specific properties and save them, so that HP SIM can identify the target systems
using these new fields.
SNMPv3 adds security and configuration enhancements to SNMP. It provides encryption mechanism
as compared to plain text transmission in SNMPv1 and authentication to validate the source versus
community string.
Procedure 86 Configuring SNMPv3 credentials
1.
2.
3.
4.
5.
Enter the Engine ID (Optional).
Enter the Context Engine ID (Optional).
Enter the Context Name (Optional).
Enter the Security Name.
Select the Security Level from the dropdown list.
•
NOAUTH-NOPRIV
If this security level is selected, the remaining fields are not configurable.
•
AUTH_NOPRIV
If this security level is selected, you can configure the following fields:
a. Select the Authentication Protocol from the dropdown list.
b. Enter and confirm the Authentication Passphrase.
•
AUTH_PRIV
If this security level is selected, you can configure the following fields:
System credentials 235
a.
b.
c.
d.
6.
7.
Select the Authentication Protocol from the dropdown list.
Enter and confirm the Authentication Passphrase.
Select the Privacy Protocol from the dropdown list.
Enter and confirm the Privacy Passphrase.
Select Keep the in-use protocol credentials even if the protocol fails to respond during discovery.
Click OK to save settings, or click Cancel to disregard changes.
Related information
SSH credentials
The SSH tab enables you to configure SSH access. It is required that Configure or Repair Agents
run after a credential is configured using host-based or user-based authentication. Host-based
authentication refers to the SSH key of the host that is trusted by the target system. User-based
authentication refers to the SSH key of the user that is trusted by the target system. In the list of
individual systems, if either the host-based or user-based authentication is selected, the user name
and password boxes are disabled. By default the specified user option appears first.
Procedure 87 Configuring SSH credentials
1.
2.
3.
Click Show advanced protocol credentials.
Select the SSH tab.
To configure SSH access authentication, select Configure Secure Shell (SSH) access
authentication. Select from:
•
Select Configure SSH for each selected system as follows, and then select from:
a. Host-based key authentication
Requires additional credentials so that Configure or Repair Agents can be run on
the target systems.
b.
User-based key authentication
Requires additional credentials so that Configure or Repair Agents can be run on
the systems.
Configures the managed systems to allow access to the specific user whose credentials
are provided.
c.
Password authentication
Enter the user name and password to connect to managed systems.
•
Select Configure SSH for the selected systems individually as follows to configure each
selected systems individually.
a. Host-based
Requires additional credentials so that Configure or Repair Agents can be run on
the target systems.
b.
User-based
Requires additional credentials so that Configure or Repair Agents can be run on
the target systems. Configures the managed systems to allow access to the specific
users whose credentials are provided.
c.
Password
Enter the user name and password.
4.
(Optional) If you selected Configure Secure Shell (SSH) access authentication User-based or
Host-based key authentication, the Additional credentials required to save the configurations
for WBEM, SSH, and/or Single Sign-On Section appears. Select from:
236 Operations
i.
Use sign-in credentials entered in Systems Insight Manager. These credentials must be for
an account with administrator or root access on the selected system
ii.
Use the following credentials for all systems
Enter the user name, password, and domain credentials to use for all selected systems.
These Configure or Repair Agents credentials apply to the WBEM, SSH, and Single Sign
On protocols. You need to enter them only once and they pre-populate on each tab.
5.
To save changes and start identification in the background, click OK. To cancel changes, click
Cancel.
Related information
WBEM credentials
One WBEM system credential or certificate can be applied to the set of selected systems or each
one can be set individually.
Procedure 88 Configuring WBEM credentials
1.
2.
3.
Click Show advanced protocol credentials.
To set WBEM system credentials, select the WBEM/WMI tab.
Select from the following:
•
Replace each selected system's WBEM / WMI credentials with the following
Use this option to replace WBEM and WMI credentials for selected systems.
a. Enter the user name and password.
b. To add additional port number, user name, and password sets, click Add. To delete
port number, user name, and password sets, click Delete beside the set you want to
delete.
HP SIM verifies that the port numbers entered are unique and valid port numbers.
By default, the port number is blank. Port numbers are not available on the discovery
task pages.
c.
d.
To use other credentials if the assigned credentials fail, select If these credentials fail,
try other credentials that may apply. Click the Learn more link for additional
information. By default this box is not selected, unless you have upgraded Systems
Insight Manager.
(Optional) To push the HP SIM certificate to HP-UX managed systems, select Push
HP SIM certificate to managed system. If this option is selected, Configure or Repair
Agents must run to push the certificate to the managed system. When this option is
selected, the Additional credentials required to save the configurations for WBEM,
SSH, and/or Single Sign-On Section is displayed. Select from:
i. Use sign-in credentials entered in HP SIM. These credentials must be for an
account with administrator or root access on the selected system
ii.
Use the following credentials for all systems
Enter the user name, password, and domain credentials to use for all selected
systems.
These Configure or Repair Agents credentials apply to the WBEM, SSH, and
Single Sign On protocols. You need to enter them only once and they
pre-populate on each tab.
•
Replace the selected system's WBEM/WMI credentials individually as following
Use this option to view and configure the list of systems individually.
System credentials 237
a.
Enter the port number, user name, and password. Port numbers must be unique.
To add additional port number, user name, and password sets, click Add. To delete
port number, user name, and password sets, click Delete by the set you want to
delete.
b.
4.
(Optional) To try additional port number, user name, and password sets, select Try
Others.
To save changes and start identification in the background, click OK. To cancel changes, click
Cancel.
Related information
WS-Man credentials
Procedure 89 Configuring WS-MAN credentials
1.
2.
3.
Click Show advanced protocol credentials.
To set WS-MAN credentials, select WS-MAN.
Select from:
•
Replace each system's WS-MAN credentials with the following
Use this option to set the user name and password pair for the WS-MAN credentials.
a. Enter the user name and password.
b. To use other credentials if the assigned credentials fail, select If these credentials fail,
try other credentials that may apply. Click the Learn more link for additional
information. By default this box is not selected, unless you have upgraded Systems
Insight Manager.
•
Replace WS-MAN credentials individually as follows
Use this option to specify sign-in credentials individually for selected systems.
a. Enter the user name and password for the individual systems.
b. To use other credentials if the assigned credentials fail, check Try others. On new
installations, this is not selected by default. However, for upgrades, the box is selected
for migrated systems. This option appears for each password entered.
4.
To save changes and start identification in the background, click OK. To cancel changes, click
Cancel.
Related information
VME credentials
This credential is protocol dependent and is used to manage various VME protocols (vCenter and
SCVMM) present in the virtual management environment. This tab is used to enter credentials that
were configured on the VME server web service page during VME server installation. When you
access the VME System Credentials page, the VME protocols supported by the CMS are listed.
There are several ways of accessing the VME System Credentials page:
•
Select Options→Security→Credentials→System Credentials, then click the VME tab.
•
Select Options→VME Options→Add or Edit VME Credentials. The Add or Edit VME Credentials
page appears.
•
Click the Quick Launch link, and then select Add or Edit VME Credentials. The Add or Edit VME
Credentials page appears.
•
From the System Page, click the Tools & Links tab. Then, click the Add or Edit VME Credentials
link under the HP Systems Insight Manager Pages heading.
238 Operations
Procedure 90 Configuring VME credentials
1.
2.
3.
Click Show advanced protocol credentials.
To set VME system credentials, select the VME tab.
Enter the following:
•
Protocol
Select the protocol from the dropdown list. The protocols listed are those being managed
under VME credentials. The list is based on the protocols that were registered by partner
applications. HP SIM can also register VME protocol types to be managed.
4.
5.
6.
•
Port #
•
User name
•
Password
•
Confirm Password
(Optional) To add additional VME credentials, click Add, and then repeat step 3 above.
(Optional) To enter VME credentials for multiple systems, select Replace the selected system's
VME credentials with the following. From here, you can enter credentials for each system
individually.
To save changes and start identification in the background, click OK. To cancel changes, click
Cancel.
After you click OK, the credentials are validated against the virtual environment. If they are
found to be valid, a message is displayed stating the credentials are saved. After credentials
are validated, with no errors, they will be stored in the HP SIM database. If credentials fail,
an error message is displayed. Click the link to display the cause of the issue.
NOTE:
When supplying credentials, you must follow the format below:
•
Domain account: DOMAIN\administrator
•
System name/address: Either the VME server host name or IP address
•
Ports: The VME server web service port
NOTE: Removing the VME credentials will unregister the hosts that are registered with Insight
Control and managed by VME.
Related information
Related information
Related procedures
Global credentials
Sign-in credentials
SNMP credentials
SNMPv3 credentials
WS-Man credentials
Single sign on credentials
SSH credentials
WBEM credentials
System credentials 239
Security
HP SIM provides the following security options:
•
User and Authorizations.
Select Options→Security→Users and Authorizations.
•
Server Certificate.
Select Options→Security→Systems Insight Manager Server Certificates.
•
Global Credentials.
Select Options→Security→Credentials→Global Credentials.
•
Systems Credentials.
Select Options→Security→Credentials→Systems Credentials.
•
Trusted Certificate
Select Options→Security→Credentials→Trust Systems.
•
SSH Host Keys
Select Options→Security→Trusted Systems, and then select the SSH Host Keys tab.
•
Sign-In Event Settings
Select Options→Security→Sign-In Event Settings.
•
Two-Factor Authentication Configuration
Select Options→Security→Two Factor Authentication→Two Factor Authentication Configuration.
•
Options→Security→Two Factor Authentication→Change Authentication Mechanism
•
System Link Configuration
Select Options→Security→System Link Configuration.
•
Privilege Elevation
Select Options→Security→Privilege Elevation.
•
Certificate Revocation Check Configuration
Select Options→Security→Certificate Revocation Check Configuration.
For more information, see Security.
Security related information
Creating a server certificate
Users with administrative rights can create a new self-signed certificate when they replace the HP
SIM SSL server certificate and private key in the following situations:
•
The integrity of the HP SIM server certificate private key is compromised.
•
The existing HP SIM server certificate expires,
This self-signed certificate is configured to expire 10 years from the date of creation.
Create a new self-signed certificate when you must replace the HP SIM SSL server certificate and
private key. The public key is included in the certificate that goes out to the client. The private key
is kept secure in the keystore database on the HP SIM server file system. The public and private
key pair of the local HP SMH (on the CMS) is overwritten with the new HP SIM public and private
key pair.
240 Operations
IMPORTANT: Replacing the SSL server certificate and private key invalidates the existing HP SIM
server certificate and the local HP SMH certificate wherever they might be imported, such as
browsers and the Trusted Management Servers List in other HP SMHs. Replace the previous server
certificate with the new server certificate in accordance with your security practices to return to the
same level of functionality you had before.
NOTE: On Windows and Linux, this process also affects the local HP System Management
Homepage certificate and private key on HP-UX systems, it affects the WBEM Services certificate
and private key.
NOTE: Valid characters for each of these fields include letters a through z (lowercase), A through
Z (uppercase), numbers 0 through 9, and the following special characters: "€ ( ) + , - . / : ?
space _ and ~. Each field must contain at least one non-white space character.
Procedure 91 Creating new system certificates
1.
(Optional) Change the following fields:
Table 32 Server certificates fields
Field
2.
Description
Common Name (CN)
The Common Name (CN) field holds the parameter that
the browser uses for name comparison when browsing
to the CMS. This field can be updated with other name
formats, such as fully qualified names, and can contain
up to 255 characters.
(Optional) Alternative Names
Enter multiple system names separated by a comma. If
a name identical to the CN is specified in the Alternative
Names field, it is not duplicated in the certificate.
Alternative names are case-sensitive. Therefore, if a
duplicate case-sensitive name is entered, it is not
duplicated in the certificate. For example, if SYS1, sys1,
and SYS1 are entered, SYS1 is only listed once in the
certificate. The alternative names might appear in a
different order from the order you enter them. However,
this does not affect their usage.
Organization (O)
Enter the name of your organization. This field can
contain up to 64 characters.
Organizational Unit (OU)
Enter the name of your department. This field can
contain up to 64 characters.
Locality (L)
Enter the name of your city. This field can contain up to
128 characters.
State (S)
Enter the name of your state. This field can contain up
to 128 characters.
Country (C)
Enter the name of your country. This field can contain
up to two alphanumeric characters, using the two-letter
country codes.
Click OK. If you click Cancel, you return to the Server Certificate page without creating a new
server certificate. A warning appears, reminding you about the effects of changing the
certificate and private key. If you click OK in the warning box to continue, a new 2,048-bit
key-pair and a new self-signed certificate are generated. The old key-pair and certificate are
not retrievable unless a backup was created manually before this process. The new certificate
and private key take effect the next time HP SIM is restarted.
Security
241
3.
Reboot the HP SIM server to ensure the new certificate is properly synchronized with the local
HP SMH and any applications or components using the certificate sharing directory.
Synchronizing the certificates prevents repeated browser security alerts when browsing to
Insight Management Advisor on the HP SIM server.
Security related information
Editing a server certificate
Edit a server certificate to change fields in an existing certificate. This modification might be required
if you submit a CSR to an external CA.
NOTE: On Windows and Linux, this process also affects the local System Management Homepage
certificate and private key on HP-UX systems, it affects the WBEM Services certificate and private
key.
NOTE: Valid characters for each of these fields include letters a through z (lowercase), A through
Z (uppercase), numbers 0 through 9, and the following special characters: "€ ( ) + , - . / : ?
space _ and ~. Each field must contain at least one non-white space character.
Procedure 92 Editing a server certificate
1.
Edit the following fields as necessary:
NOTE: The Common Name (CN) field and the key pair cannot be modified, so the trust
relationships with any HP System Management Homepages remain in tact. However, the
browser trust must be re-established by importing the modified certificate and deleting the old
certificate from the browser.
Table 33 Edit server certificates fields
Field
2.
Description
(Optional) Alternative Names
Enter multiple system names separated by a comma. If
a name identical to the CN is specified in the Alternative
Names field, it is not duplicated in the certificate.
Alternative names are case-sensitive. Therefore, if a
duplicate case-sensitive name is entered, it is not
duplicated in the certificate. For example, if SYS1, sys1,
and SYS1 are entered, SYS1 is only listed once in the
certificate. The alternative names might appear in a
different order from the order you enter them. However,
this does not affect their usage.
Organization (O)
Enter the name of your organization. This field can
contain up to 64 characters.
Organizational Unit (OU)
Enter the name of your department. This field can
contain up to 64 characters.
Locality (L)
Enter the name of your city. This field can contain up to
128 characters.
State (S)
Enter the name of your state. This field can contain up
to 128 characters.
Country (C)
Enter the name of your country. This field can contain
up to two alphanumeric characters, using the two-letter
country codes.
Click OK. A warning message appears, indicating that the certificate is about to be modified.
You can click Cancel to abort the modify operation.
Security related information
242 Operations
Importing a server certificate
Import a CA-signed server certificate to replace the existing server certificate in the following
situations:
•
You have installed HP SIM and want to replace the default self-signed certificate with a
certificate created by a third-party CA or your own internal CA.
•
The integrity of the HP SIM server certificate private key is compromised.
•
The existing HP SIM server certificate has expired.
CAUTION: Replacing the SSL server certificate and private key invalidates the existing server
certificate wherever it might be imported, such as browsers and the Trusted Management Servers
Lists of managed systems. Replace the previous server certificate with the new server certificate in
accordance with your security practices to return to the same level of functionality you had before.
NOTE: On Windows and Linux, this process also affects the local System Management Homepage
certificate and private key on HP-UX systems, it affects the WBEM Services certificate and private
key.
Procedure 93 Importing a server certificate
1.
2.
3.
Create a CSR. See Creating a certificate signing request for additional information. The CSR
uses parameters from the existing certificate, including any alternative names. If you want to
change those parameters, edit the server certificate (see Editing a server certificate) or create
a new server certificate (see Creating a server certificate).
Submit the request to a CA. See Submitting a certificate signing request for more information.
The CA returns a signed certificate.
Import the signed certificate reply into HP SIM. See Importing a CA-signed certificate for more
information.
Security related information
Exporting a server certificate
Export the HP SIM server certificate to a file to facilitate deployment of the certificate into your
browser, enabling the browser to properly identify the HP SIM server. This certificate is a public
document, so it does not need to be kept private. However, because the certificate is kept publicly
accessible, you must ensure that it cannot be modified.
Only HP SIM users with administrative rights can export the HP SIM system certificate from HP
SIM.
NOTE: The system certificate can be exported as a Base64 encoded certificate. The exported
certificate can be imported into a browser or a system's or the Trusted Management Systems List.
Procedure 94 Exporting the system certificate from HP SIM using Microsoft Internet Explorer
1.
2.
Select the location for the file to be saved.
Enter a file name and click Save to save the certificate as a Base64-encoded X.509 certificate.
This file can be imported into a browser or managed system for authentication of the CMS
during a SSL connection. You can click Cancel to cancel the save operation and return to the
System Certificate page.
Procedure 95 Exporting the system certificate from HP SIM using Mozilla
1.
2.
3.
4.
Display the certificate in a new browser window.
Select the entire contents of the browser window that includes the certificate.
Copy the selected text to the clipboard.
Paste the text into a text editor, and save the file with a .CER file extension.
Security 243
Procedure 96 Exporting the system certificate from the browser (Microsoft Internet Explorer only)
1.
View the HP SIM system certificate using one of the following methods:
•
From the Internet Explorer browser menu, select File→Properties→Certificates.
•
Double-click the Lock icon in the lower right portion of the browser.
The Certificate dialog box appears.
2.
Click the Details tab in the Certificate dialog box.
The Details tab appears.
3.
Click Copy to File.
The Certificate Export Wizard launches.
4.
Click Next.
The Export File Format dialog box appears.
5.
Select Base-64 encoded X.509 for the export file format. Click Next.
The File to Export dialog box appears.
6.
In the File name field, enter the file you want to export. Click Next.
The Completing the Certificate Export Wizard dialog box appears.
7.
Click Finish. You can click Back to return to the previous page or click Cancel to cancel the
export operation.
A message appears indicating that the export is completed.
8.
Click OK.
Related information
Creating a certificate signing request
Create a CSR in .p10 format, which can be submitted to a CA to be signed.
Submitting a certificate signing request
After creating the CSR, the CSR must be submitted to the desired CA for signing.
NOTE:
You must complete the CSR creation procedure before continuing with this procedure.
Importing a CA-signed certificate
After creating a CSR and having it signed by a CA, you can import the signed certificate.
The only importable certificate format is PKCS #7. If the certificate reply received from the CA is
a single certificate, then first import a self-signed root certificate from the issuing CA into the HP
SIM Trusted System Certificates List. After importing the CA root certificate, the certificate reply
can then be imported to serve as the HP SIM server certificate.
NOTE: On Windows and Linux, this process also affects the local System Management Homepage
certificate and private key on HP-UX systems, it affects the WBEM Services certificate and private
key.
NOTE:
less.
HP SIM supports only importing certificates that have a public key size of 2,048 bits or
Procedure 97 Importing a signed certificate reply from a CA
1.
Click more next to Import signed certificate reply from CA. The Import Signed Certificate Reply
Section follows the Import Server Certificate Section.
244 Operations
2.
Click Browse next to the Certificate filename field. The Choose file dialog box appears.
a. Navigate to the location where the signed certificate is stored.
b. Select the correct file name, and then click Open.
The file name appears in the Certificate filename field.
3.
Click Import. The signed certificate is imported.
After creating a CSR or importing the server certificate, reboot the HP SIM server for the HP
SIM server certificate to synchronize it with the HP System Management Homepage certificate
and the certificate sharing directory. Synchronizing the certificates prevents repeated browser
security alerts when browsing to Insight Management Advisor on the HP SIM server, which
enables HP SIM and the local HP System Management Homepage to update SSL server
certificates and private keys.
Security related information
Synchronizing certificates
When the HP SIM server certificate is created or modified, the public and private key-pair of the
local HP SMH certificate is overwritten with the HP SIM public and private key pair.
NOTE:
This feature is available in case the certificates become unsynchronized.
NOTE: For the certificate sharing feature to work in HP-UX, OpenSSL must be installed in the
/OPT/APACHE/SSL/BIN/ directory (default for HP-UX installations). For the certificate sharing
feature to work in Linux, OpenSSL must be installed in the /USR/BIN/ directory (default for Linux
installations).
Security related information
Configuring the system link
To choose the name format used when creating links to managed systems. The System Link
Configuration setting defines how HP SIM creates browser links to remote systems and how it
communicates with remote systems for certain requests.
NOTE: When you browse to systems using SSL, the browser may display a warning if the system
name does not match the name in the system certificate.
Procedure 98 Configuring the system link
1.
Select from the following options:
•
Use the system name. Select this option to use the system name.
•
Use the system IP address. Select this option to use the system IP address.
•
Use the system full DNS name. Select this option to use the system's full DNS name.
NOTE: On an HP-UX or Linux CMS, the default value is Use the system full DNS name on
new HP SIM installations. New installations on Windows defaults to Use the system name,
and upgrades maintain the existing setting regardless of the operating system.
NOTE: During discovery, the full system DNS name is used as the primary lookup key.
Otherwise, the IP address is used.
NOTE: In the case of systems with multiple network interfaces, selecting the Use the system
name provides only one link per destination to the system, whereas Use the system IP address
provides multiple links to the system.
2.
To save and apply the changes, click OK.
Security related information
Security 245
Configuring sign-in events
Configure sign-in events to create actionable events for sign-in and sign-out activities.
NOTE: Configuring sign-in events does not affect the HP SIM Audit Log. Sign-in events are always
logged in the HP SIM Audit Log.
Procedure 99 Configuring sign-in events
1.
2.
Select from the following options:
•
All sign-in and sign-out activities. Select this option to create events for all sign-in and
sign-out actions.
•
Only failed sign-in attempts. Select this option to create events only for sign-in attempts
that are unsuccessful.
•
None. Select this option if you do not want to create any events for sign-in or sign-out
activities.
To save and apply changes, click OK.
Security related information
Privilege elevation
From this page, you can enable privilege elevation for Linux, HP-UX, and ESX managed systems.
This enables you to sign in as an unprivileged user and elevate the privilege to run on these
operating systems.
Procedure 100 Configuring privilege elevation
1.
Select Enable privilege elevation for VMware ESX.
To configure privilege elevation for Linux and HP-UX systems, select Enable privilege elevation
for Linux & HP-UX.
2.
Select the elevation tool type from the menu.
If a password is required for the tool, select A password is required for this privilege elevation
tool.
3.
4.
5.
Optional: Edit the Privilege elevation tool command.
Select the user to sign in to the managed system:
•
Same as HP SIM signed-in user
•
Specify at run time
•
Use this user and enter the user name
To save changes, click OK.
NOTE: When "DISPLAY_LAST_LOGIN"=1 in HP-UX, even non-interactive logins, such as those
used by sudo, omit the Last login string. This extraneous data in stderr and stdout might affect tools.
This value can be changed using HP System Management Homepage in the Auditing and Security
Attributes Configuration Section on the HP SMH home page. This can be done either for the user
to which privileges will be elevated (typically, root) or for the system-wide default for all users. To
make the change, enter:
For an individual user:
/usr/sbin/userdbset -u <user> DISPLAY_LAST_LOGIN=0
For the system wide default:
/usr/sbin/ch_rc -a -p DISPLAY_LAST_LOGIN="0" /etc/default/security
Security related information
246 Operations
Changing the authentication mechanism
This option enables you to change the authentication settings.
NOTE: You must restart HP SIM for changes to take effect. All users must have a valid certificate
to login once Two Factor Authentication is enabled.
Procedure 101 Changing the two factor authentication mechanism
1.
2.
Select from the following:
•
Two Factor Authentication (Certificate based)
•
Form based Authentication (Username/Password based
Click OK.
Configuring Two Factor Authentication
Options with an asterisk are required.
Procedure 102 Configuring Two Factor Authentication
1.
Enter the following:
•
Server Name
The IP address or host name of the Directory Server
•
Port Configuration
To use non-SSL port, deselect Use SSL. This is selected by default.
•
Server Port
•
User Name
•
Password
•
Password (Verify)
•
Users DN
The distinquished name or the users group. For example, CN=Users, DC=HP, DC=Com.
HP SIM assumes that the users are configured in this distinguished name.
2.
3.
To test the connection, click Test Connection. If the test is successful, a message appears on
the screen stating that the connection using the current settings was successful.
To save and apply the changes, click OK.
You must manually restart the CMS for the changes to take affect.
Security related information
Certificate Revocation Check Configuration
Configure HP SIM to support revocation of certificates.
IMPORTANT:
Certificate Revocation Check is mandatory for Two Factor Authentication
Security 247
Procedure 103 Configuring Certificate Revocation Check
1.
Select certificates to enable certificate revocation:
•
Server Certificates
This option takes effect only if Require Trusted Certificates is enabled. To enable this
option, go to Options→Security→Crendials→Trusted Certificates→Trusted Certificates
•
Client Certificates
This option might result in validating every certificate in the certificate chain and may
lead to performance degradation.
2.
There are two modes to run Certificate Revocation Check:
•
Offline Mode
The CRL files should be placed in SIM’s data\CRL directory. The files should be regularly
updated for SIM to know the servers whose certificate has been revoked.
•
Online Mode
HP SIM will download the CRL files from the distribution point provided in the server
certificate and perform the CRL check.
This mode can be used with Offline Mode.
To diable online mode, select Disable online mode
To enable online mode, select The Certificate Authority (CA) is reachable from CMS without
Proxy settings.
3.
Click OK to save settings
Security related information
Related procedures
Exporting a server certificate
Editing a server certificate
Creating a server certificate
Synchronizing certificates
Creating a certificate signing request
Submitting a certificate signing request
Importing a CA-signed certificate
Configuring sign-in events
Configuring the system link
Managing server certificates
Replicating trusted certificates
Changing the HP SIM default SSL port
Configuring browser timeout options
Privilege elevation
Configuring Two Factor Authentication
Related topics
Installing OpenSSH
Managing SSH keys
Trusted certificates
Trusted certificates
Trusted certificates provide the highest level of security. Users with administrative rights can import
certificates from other systems into the HP SIM Trusted System Certificates List.
248 Operations
The purpose of the Trusted System Certificates List in HP SIM is to maintain a list of certificates in
the HP SIM keystore. Certificates include the HP SIM system certificate and the certificates of
managed systems that are trusted by the HP SIM system. These imported certificates are placed in
the keystore and appear in the Trusted System Certificates List.
The Trusted System Certificate List page includes the following options:
•
Always Accept
If Always Accept is selected, SSL always accepts the certificate presented by a system in the
SSL connection. This setting is the default and is vulnerable to man-in-the-middle attacks, but
it is the easiest option to use.
•
Require
If Require is selected, SSL connections succeed only for systems represented in the Trusted
System Certificate List, either by its certificate or its CA-signing certificate (if applicable). You
must set up the trust by manually installing the system's certificate or its CA-signing certificate,
(if applicable), into the HP SIM Trusted System Certificate List. This option is the most secure,
but it is the most difficult to implement.
HP SIM provides the following trusted certificate options:
•
Import trusted certificate.
Select Options→Security→Credentials→Trusted Systems, and then click Import.
•
Export certificate
Select Options→Security→Credentials→Trusted Systems, and then click Export.
•
Delete trusted certificate
Select Options→Security→Credentials→Trusted Systems, select the certificates to be deleted,
and then click Delete.
Related information
Importing trusted certificates
If you have selected Require on the Trusted System Certificates page, you must import certificates
that represent the managed systems you want to trust to the Trusted Certificates List. You can import
the certificate of the system itself on a per-system basis. You can also import the signing certificate
of the CA or intermediate CA used to sign and issue certificates for groups of systems, which
simplifies the maintenance of this list.
NOTE: Only users with administrative rights can import certificates into the HP SIM Trusted System
Certificates List.
NOTE:
less.
HP SIM supports only importing certificates that have public key sizes of 2,048 bits or
Procedure 104 Importing certificates into the Trusted System Certificates List
1.
Next to the Certificate filename field, click Browse.
The Choose file dialog box appears.
2.
Navigate to the location of the certificate to be imported, and then select the file name. Click
Open.
Related information
Exporting trusted certificates
Export the HP SIM server certificate to a file to facilitate deployment of the certificate into your
browser, enabling the browser to properly identify the HP SIM server. This certificate is a public
Trusted certificates 249
document, so it does not need to be kept private. However, because the certificate is kept publicly
accessible, you must ensure that it cannot be modified.
Only HP SIM users with administrative rights can export the HP SIM system certificate from HP
SIM.
NOTE: The system certificate can be exported as a Base64 encoded certificate. The exported
certificate can be imported into a browser or a system's or the Trusted Management Systems List.
Procedure 105 Exporting the system certificate from HP SIM using Microsoft Internet Explorer
1.
2.
Select the location for the file to be saved.
Enter a file name and click Save to save the certificate as a Base64-encoded X.509 certificate.
This file can be imported into a browser or managed system for authentication of the CMS
during a SSL connection. You can click Cancel to cancel the save operation and return to the
System Certificate page.
Procedure 106 Exporting the system certificate from HP SIM using Mozilla
1.
2.
3.
4.
Display the certificate in a new browser window.
Select the entire contents of the browser window that includes the certificate.
Copy the selected text to the clipboard.
Paste the text into a text editor, and save the file with a .CER file extension.
Procedure 107 Exporting the system certificate from the browser (Microsoft Internet Explorer only)
1.
View the HP SIM system certificate using one of the following methods:
•
From the Internet Explorer browser menu, select File→Properties→Certificates.
•
Double-click the Lock icon in the lower right portion of the browser.
The Certificate dialog box appears.
2.
Click the Details tab in the Certificate dialog box.
The Details tab appears.
3.
Click Copy to File.
The Certificate Export Wizard launches.
4.
Click Next.
The Export File Format dialog box appears.
5.
Select Base-64 encoded X.509 for the export file format. Click Next.
The File to Export dialog box appears.
6.
In the File name field, enter the file you want to export. Click Next.
The Completing the Certificate Export Wizard dialog box appears.
7.
Click Finish. You can click Back to return to the previous page or click Cancel to cancel the
export operation.
A message appears indicating that the export is completed.
8.
Click OK.
Related information
Deleting trusted certificates
CAUTION:
The delete process is irreversible. Use this feature with caution!
Procedure 108 Deleting certificates from the Trusted System Certificates List
1.
2.
Select Options→Security→Credentials→Trusted Systems.
Select the certificates to be deleted.
250 Operations
3.
4.
Click Delete. A dialog box appears.
To delete the certificates, click Yes, or to cancel the delete process and return to the Trusted
System Certificates page, click Cancel.
Related information
Requiring trusted certificates
Trusted system certificates are certificates that represent managed systems. Enabling the Trusted
System Certificate option enables HP SIM to authenticate the remote managed system. For ease
of use, this option is disabled; this scenario is typical and maintains a high level of security. For
maximum security, this option should be enabled, which requires extra configuration.
If Require is enabled, when HP SIM attempts to make an SSL connection to a managed system, a
certificate representing that system must be found in the HP SIM keystore or the SSL connection
and attempted operation fails. The certificate representing the system can be the system's SSL
system certificate or the CA level certificate that was used to sign the system's certificate. For large
numbers of systems, using having a handful of CA-level certificates to sign all the system certificates
can simplify the management and maintenance of the system certificates. However, this option
requires the presence of a certificate system in your environment, or the services of a third-party
security company.
CAUTION: If you select the Require option, a warning message appears, indicating that certain
features work only for systems whose certificates are represented in the Trusted Certificate List.
The HP SIM Trusted System Certificates List is only used when the Require option is enabled.
IMPORTANT: Changing the Require option can adversely affect the operation of HP SIM. Carefully
read and understand the warning described in this Section.
When using a CA-level certificate, any valid certificate signed by the CA-level certificate is accepted
by HP SIM, whether it is already issued or issued at some point in the future.
Procedure 109 Enabling the require trusted certificates option
1.
Select Require. This setting restricts the CMS from accepting any connections other than SSL
connections with managed systems. The managed systems must have a certificate in the
Certificate List. This option does not affect browsing to the CMS.
A warning message appears indicating that certain features work only for systems whose
certificates are represented in the Trusted System Certificates List.
2.
To require trusted certificates, click OK . To disable the Require option and return to the Trusted
System Certificates page, click Cancel.
Procedure 110 Disabling the Trusted System Certificates option
1.
Select Options→Security→Credentials→Trusted Systems.
The Trusted Certificates page appears.
2.
3.
Select another option.
Click OK, or to leave the Require option enabled and return to the Trusted System Certificates
page, click Cancel.
Related information
Configuring SSH key security
Configuring the SSH key security level enables you to specify the level of security on the CMS.
Trusted certificates
251
Procedure 111 Configuring the SSH key security level on the CMS
1.
Under Select managed systems SSH host key behavior, the following options are available:
•
The Central Management Server will save the SSH host key the first time an SSH connection
is made.
•
The CMS will accept an SSH connection with any host key, even if not in the list below.
This option is selected by default.
This option causes all connections to the host to be accepted, even when the SSH key
has changed. The known_hosts file is disabled and updated to reflect the new key.
NOTE:
•
This option provides no protection against man-in-middle attacks.
The CMS will accept an SSH connection only if the host key is in the list below
This option requires the SSH key to appear in the Managed Systems SSH Host Keys list.
NOTE:
2.
HP recommends this option because it is the most secure.
Click OK. The setting is saved.
NOTE: Alternately, you can set the property value for MX_SSH_ADD_UNKNOWN_HOSTS, in
mx.properties file, to either ALWAYS, NEVER, or FIRST TIME. Restart the HP SIM service for the
setting to take effect.
Related information
Importing an SSH key
Importing a SSH key list enables the CMS to authenticate a secure connection and execute
commands on managed systems. Multiple SSH keys are imported from one file, and each SSH
key appears on a line and is associated with a host system.
NOTE:
Only correctly formatted SSH keys can be imported into the Managed Systems SSH
public keys list.
See the HP Systems Insight Manager User Guide, at http://www.hp.com/go/insightmanagement/
sim/docs, for more information about the format of the SSH keys file.
Procedure 112 Importing SSH keys to the CMS
1.
2.
3.
Click Import. The Import SSH host Keys Section appears.
Click Browse to navigate to the file that contains the SSH keys to be imported.
Select the file and click Open to add the key to the Managed Systems SSH Public Keys list, or
click Cancel to abort the operation.
Related information
Exporting an SSH key
Exporting selected SSH keys saves the SSH keys to a file. This file can be used to import the SSH
keys into the SSH key list on other systems.
Procedure 113 Exporting SSH keys from the CMS to a file
1.
2.
3.
4.
5.
6.
From the Managed System SSH Host Keys list, select the SSH key to be exported.
Click Export. The Export SSH host Keys Section appears.
Right-click the link provided and select Save Target As. The Save As dialog box appears.
Navigate to the directory where you want to store the file.
Click Save. The key is exported.
Click OK.
252 Operations
Related information
Deleting an SSH key
Deleting SSH keys from the Managed System SSH Host Keys list enables you to remove SSH trusted
keys on the CMS.
Procedure 114 Deleting SSH keys from the CMS
1.
2.
3.
From the Managed System SSH Host Keys list, select the SSH key to be deleted.
Click Delete. A message appears, indicating you are about to delete SSH keys.
Click OK. The key is removed from the Managed Systems SSH Public Keys list.
Related information
Related information
Related procedures
Importing trusted certificates
Requiring trusted certificates
Configuring SSH key security
Importing an SSH key
Exporting an SSH key
Deleting an SSH key
Viewing the audit log
HP SIM logs all tasks performed by all HP SIM users on all systems. The information is stored in
the Audit Log file on the Central Management Server (CMS).
NOTE: You must be signed-in as root or administrator (or any user with administrative rights) to
read the Audit Log file directly.
Procedure 115 Viewing the HP SIM Audit Log
1.
2.
3.
Select Tasks & Logs→View HP Systems Insight Manager Audit Log. The Audit Log page appears.
Select the log entries you want to view by selecting one of the following options:
•
most recent 40 entries. Select this to view a selectable number of the most recent log
entries. The default is set to view the 40 most recent log entries.
•
from entry " " to entry " ". Select this option to view an indexed range of log entries.
Click View Now. The requested log entries appear.
Log content
The HP SIM Audit Log contains the following information in the order listed.
•
Time stamp date, time, and time zone
•
Category
•
Result
•
Action
•
Object type
•
Object type descriptor
•
Level
•
Session user login string
•
(Optional) Session ID
Viewing the audit log 253
•
(Optional) Transaction ID
•
(Optional) Session user full user name
These fields appear in one line. If messages or additional information about a log entry is present,
it appears in the next line.
Example of an HP SIM Audit Log:
2006-07-11 18:21:50 MDT,CONFIG,SUCCESS,ADD,TASK,Default Automatic
Discovery,SUMMARY,mxadmin,0,11,
2006-07-11 18:22:06 MDT,CONFIG,SUCCESS,MODIFY,TASK,Initial Hardware
Status Polling,SUMMARY,mxadmin,0,12,
2006-07-11 18:51:01
MDT,CONFIG,SUCCESS,ADD,AUTHORI,MX_AUTH,SUMMARY,jsmith,590,1186800129,
John Smith Added authorization for user djones with a toolbox of Monitor
Tools for All Managed Systems.
2006-02-23 13:15:43 CST, CONFIG, SUCCESS, ADD, AUTHORIZATION, NODE_GROUP,
SUMMARY, VIVO\djones, 6866, 351185188, Added automatically updating
authorization for user VIVO\djones with a toolbox of Monitor Tools for
All Storage Systems 001.
2006-02-23 13:15:43 CST, CONFIG, SUCCESS, ADD, NODE_GROUP, All Storage
Systems 001,SUMMARY,VIVO\djones,6866,351185185, Automatic update is
true/false.
2006-02-27 11:05:42 CST, CONFIG, SUCCESS, MODIFY, NODE_GROUP, All Storage
Systems 001,SUMMARY,VIVO\djones,6904,1029055411, Automatic update is
true/false.
2006-02-27 11:05:42 CST, CONFIG, SUCCESS, MODIFY, NODE_GROUP, All Storage
Systems 001,SUMMARY,VIVO\djones,6904,1029055411, Automatic update is
true/false.
2006-02-27 11:05:42 CST, CONFIG, SUCCESS, MODIFY, NODE_GROUP, All Storage
Systems 001,SUMMARY,VIVO\djones,6904,1029055411, Automatic update is
true/false. Added EVASAN01. Removed EVASAN99.
Configuring the audit log
Configuring the audit log
Configure the Audit Log file to reside in a user specific directory.
Procedure 116 Configuring the HP SIM Audit Log file location
1.
For Windows, create a file named path.properties under C:\Program Files\HP\
Systems Insight Manager\config.
For Linux and HP-UX, create a file named path.properties under /etc/opt/mx/config.
2.
For Windows, add the following entry in the path.properties file: LOG=\\Auditlog\\Logs
or LOG=C:/Auditlog/Logs.
For HP-UX, add the following entry in the path.properties file: LOG=/var/opt/mx/logs.
NOTE: C:\\Auditlog\\Log is listed here as an example for Windows. This path is user
defined.
NOTE:
254 Operations
/var/opt/mx/logs is listed here as an example for HP-UX. This path is user-defined.
3.
For Linux and HP-UX, click Restart the HP SIM daemons (mxstop and mxstart). For Windows
operating systems, restart the HP SIM service. After restarting the service, a new log file named
mx.log resides in the directory specified in path.properties file.
Five variables can be defined in the log.properties file:
•
MX_LOG_FILENAME for the file name. The default is "MX_LOG_FILENAME=mx".
•
MX_LOG_FILEEXT for the file extension. The default is "MX_LOG_FILEEXT=log".
•
MX_LOG_FILESIZE for the maximum file size. The default is "MX_LOG_FILESIZE=20".
•
MX_LOG_ROLLFILEEXT for the file extension of the roll-over name. The default is
"MX_LOG_ROLLFILEEXT=old".
•
MX_LOG_QUEUESIZE for the amount of memory allocated for queuing items to be written to
the Audit Log. The default is "MX_LOG_QUEUESIZE=300".
The maximum file size is set in megabytes.
When the Audit Log file reaches the maximum file size, the log is renamed with
MX_LOG_ROLLFILEEXT extension, and a new file is started. If a previous version of the file has
already been renamed with the MX_LOG_ROLLFILEEXT extension, it is an automatic roll-over of
an audit log file. A roll-over occurs after a task running is completed. However, after one hour
exceeding the maximum file size, if the task is not finished, the audit log file rolls over to another
file.
CAUTION: Change the queue size only with extreme care. If the queue is set too high, the log
manager consumes too much system memory.
Changes made to the log.properties file do not take effect until the log manager daemon is
restarted. For Windows, restart HP SIM service. For Linux and HP-UX, restart the log manager.
NOTE: By default, for Linux and HP-UX, the path for the log file is set to /var/opt/mx/logs.
This path can be configured by editing the LOG value in the /etc/opt/mx/config/
path.properties file. If this properties file does not exist, create it. For Windows, the default
location is the logs subdirectory of the directory where the product was installed.
Monitoring systems and events
Users with administrative rights can manage and monitor all shared collections. Users can also
manage their own private collections from this page.
Creating system and cluster collections
NOTE: Users with administrative rights can create a shared collection. Users with operator rights
can view shared collections, but can only create their own private collections.
Procedure 117 Creating a system collection
1.
2.
3.
In the System and Event Collections panel, click Customize. The Customize Collections page
appears.
In the Show collections of dropdown list, select Systems. All available system or cluster
collections appear.
Click New. The New Collection section appears.
Monitoring systems and events 255
4.
Select Choose members individually, Choose members by attributes, or Choose members from
existing system and event collections. For more information about the different collection types,
see Types of collections.
•
If you selected Choose members individually, complete the following steps:
a. In the Choose from dropdown list, select an individual collection.
NOTE: When select a collection from the dropdown list, the first-level members of
that collection appear in the Available Items box.
b.
From the Available Items box, select items to place in the collection by highlighting
c.
the item and clicking
. You can click the up and down arrows to change the
position of an item in the collection, or click Remove to remove items from the Selected
Items box.
Click one of the following:
◦
Save As Collection
To save the collection. For more information, see Saving collections.
◦
Cancel
To close the New Collection section without saving changes.
•
If you selected Choose members by attributes, complete the following steps:
a. In the Search for dropdown list, select systems or clusters.
b. Enter the search criteria for the collection. For more information about sytem search
criteria, see Performing an advanced search for systems, or for more information
about cluster search criteria, see Performing an advanced search for clusters.
c. Click one of the following:
◦
[View]
To run the search and display results immediately.
◦
Save As Collection
To save the collection. For more information about saving collections, see Saving
collections.
◦
Cancel
To close the New Collection section without saving changes.
•
If you selected Choose members from existing system and event collections, complete the
following steps:
a. In the Select system collection dropdown list, select a system collection.
NOTE:
b.
c.
Combination collections do not appear in the dropdown list.
In the Select event collections dropdown list, select an event collection.
Click one of the following:
◦
View
To run and display the search immediately.
◦
Save As Collection
To save the collection. See Saving collections for more information about saving
collections.
256 Operations
◦
Cancel
To close the New Collection section without saving changes.
NOTE: If you create a collection with a system collection and an event collection on the
Customize Collections page, the collection is saved as a system collection and is placed in the
Systems branch location that you specify.
Command line interface
Users with administrative rights can use the mxcollection command to create new collections
from the CLI.
Related information
Editing system and cluster collections
Users with administrative rights can edit a shared collection. Users with operator rights can view
shared collections, but can only edit their own private collections.
Procedure 118 Editing a system or cluster collection
1.
2.
In the System and Event Collections panel, click Customize. The Customize Collections page
appears.
In the Show collections of dropdown list, select Systems. All available system or cluster
collections appear.
Monitoring systems and events 257
3.
Select a system or cluster collection to edit, and then click Edit. The Edit Collection section
appears. Depending on how you created the collection, the following appears:
a. If you created the collection using the Choose members individually option, complete the
following steps:
a. In the Choose from dropdown list, select an individual collection.
NOTE: When select a collection from the dropdown list, the first-level members of
that collection appear in the Available Items box.
b.
From the Available Items box, select items to place in the collection by highlighting
c.
the item and clicking
. You can click the up and down arrows to change the
position of an item in the collection, or click Remove to remove items from the Selected
Items box.
Click one of the following:
•
Save As Collection
To save the collection. For more information, see Saving collections.
•
Cancel
To close the New Collection section without saving changes.
b.
If you created the collection using the Choose members by attributes option, complete
the following steps:
a. In the Choose from dropdown list, select an individual collection.
NOTE: When select a collection from the dropdown list, the first-level members of
that collection appear in the Available Items box.
b.
From the Available Items box, select items to place in the collection by highlighting
c.
the item and clicking
. You can click the up and down arrows to change the
position of an item in the collection, or click Remove to remove items from the Selected
Items box.
Click one of the following:
•
OK
To save the collection.
•
Cancel
To close the New Collection section without saving changes.
c.
If you selected Choose members by attributes, complete the following steps:
a. In the Search for dropdown list, select systems or clusters.
b. Enter the search criteria for the collection. For more information about sytem search
criteria, see Performing an advanced search for systems, or for more information
about cluster search criteria, see Performing an advanced search for clusters.
c. Click one of the following:
•
[View]
To run the search and display results immediately.
•
OK
To save the collection.
•
Cancel
To close the New Collection section without saving changes.
258 Operations
d.
If you created the collection using the Choose members from existing system and event
collections option, complete the following steps:
a. In the Select system collection dropdown list, select a system collection.
NOTE:
b.
c.
Combination collections do not appear in the dropdown list.
In the Select event collections dropdown list, select an event collection.
Click one of the following:
•
[View]
To run the search and display results immediately.
•
OK
To save the collection.
•
Cancel
To close the New Collection section without saving changes.
Command line interface
Users with administrative rights can use the mxcollection command to edit existing collections
from the CLI.
For more information about accessing the manpage, which includes detailed information for this
command, see the HP Systems Insight Manager User Guide, at http://www.hp.com/go/
insightmanagement/sim/docs.
Related information
Moving system and cluster collections
This procedure enables you to move a collection from one collection to another. Users with
administrative rights can move a shared collection.
Procedure 119 Moving a system collection
1.
2.
In the System and Event Collections panel, click Customize. The Customize Collections page
appears.
In the Show collections of dropdown list, select Systems. All available system or cluster
collections appear. Click
3.
4.
to expand all system and cluster collections in the table, or click
to collapse all system and cluster collections in the table.
Select the collection to move, and then click Move. The Move Collection section appears.
Under Move to, select one of the following:
•
Existing collection
Select an existing private or shared collection from the dropdown list. Click OK to save
the collection, or click Cancel to cancel the save operation.
Locked collections do not appear in the list.
•
New collection
Enter a name for the new collection and select an existing private or shared collection
from the dropdown list. Click OK to save the collection, or click Cancel to cancel the save
operation.
Command line interface
Users with administrative rights can use the mxcollection command to move existing collections
from the CLI.
Monitoring systems and events 259
NOTE: Users with administrative rights can move a shared collection. You cannot move shared
and private root collections, and you cannot move a shared collection into a private collection.
Related information
Copying system and cluster collections
You can copy a collection as a new collection. When you copy a collection that was created by
members, you copy the collection and its members into the new collection. If you edit the original
collection after you copy it to the new collection, the newly copied collection is not updated. For
example, if the original collection has two members, the same two members copy to the new
collection. If you edit the original collection to add another member after you copy it, the newly
copied collection is not modified.
When you copy a collection that was created based on attributes, you copy the collection attributes
into the new collection. If you edit the original collection after you copy it to the new collection,
the newly copied collection does not reflect these edits.
When you copy a combination collection, the newly created collection has the same system
collection and event collection. If you edit the original collection after you copy it to the new
collection, the newly copied collection is not updated. For more information about collections, see
the HP Systems Insight Manager User Guide, at http://www.hp.com/go/insightmanagement/
sim/docs.
Procedure 120 Copying system collections
1.
2.
3.
4.
5.
Click Customize in the System and Event Collections panel. The Customize Collections page
appears.
In the Show dropdown list, select Systems. All available system or cluster collections appear.
Click
to expand all system and cluster collections in the table, or click
to collapse
all system and cluster collections in the table.
Select the collection to copy, and then click Copy. The Copy Collection section appears.
In the Collection name field, enter a name for the new collection.
Under Place in, select a location to save the collection, and then, depending on the type of
collection, do one of the following:
•
Existing collection
Select an existing private or shared collection from the dropdown list. Click OK to save
the collection, or click Cancel to cancel the save operation.
Locked collections do not appear in the list.
•
New collection
Enter a name for the new collection and select an existing private or shared collection
from the dropdown list. Click OK to save the collection, or click Cancel to cancel the save
operation.
Command line interface
Users with administrative rights can use the mxcollection command to copy existing collections
from the CLI.
Related information
Deleting system and cluster collections
NOTE: Users with administrative rights can delete a shared collection. Users with operator rights
can view shared collections, but, can only delete their own private collection.
260 Operations
Procedure 121 Deleting system collections
1.
2.
3.
4.
Click Customize in the System and Event Collections panel. The Customize Collections page
appears.
In the Show dropdown list, select Systems. All available system or cluster collections appear.
Click
to expand all system and cluster collections in the table, or click
to collapse
all system and cluster collections in the table.
Select the collection to be deleted.
Click Delete. A dialog box appears. To continue with the deletion, click OK, or to cancel the
operation, click Cancel. If the selected collection is not empty or is in use by a task (such as
Home page, reports, and so on) an error message appears. However, if the collections contents
are based on attributes, you can delete the collection even if it is not empty.
Command line interface
Users with administrative rights can use the mxcollection command to delete existing collections
from the CLI.
Related information
Setting properties for system and cluster collections
You can use the System and Event Collections panel to set collection properties such as hiding or
showing collections, system status, and cluster status, and selecting the default view for a collection.
Procedure 122 Setting properties for system collections
1.
2.
Click Customize in the System and Event Collections panel. The Customize Collections page
appears.
In the Show collections of dropdown list, select Systems. All available system or cluster
collections are appear. Click
3.
4.
5.
to expand all system and cluster collections in the table,
or click
to collapse all system and cluster collections in the table.
Select a collection, and then click Set Properties. The Set Properties section appears.
Under Visible, select Yes, show collection and its members in the user interface or select No,
do not show collection and its members in the user interface . If you have collections that are
unused, you might want to select No, do not show collection and its members in the user
interface so that the collections do not clutter the System and Event Collections panel.
If you want to see the system health status, under Status Displayed, select Yes, show status in
System and Event Collections panel, or to keep the panel uncluttered, select No, do not show
the status in System and Event Collections panel.
NOTE: This option is available only for collections based on attributes and for combination
collections.
NOTE: For a collection, the most critical status of its members appears. If you open the
collection, the status for each member appears.
NOTE: To conserve system resources, try to limit the display of status to only those collections
that you view the most.
6.
In the Default View field, select the default view from the dropdown list.
Command line interface
Users with administrative rights can use the mxcollection command to set properties for
collections from the CLI.
Related information
Monitoring systems and events
261
Creating event collections
NOTE:
By default, all newly created collections are private.
NOTE: Users with administrative rights can create a new shared event collection. Users with
operator rights or user rights view shared collections, but can create only their own private
collections.
Procedure 123 Creating event collections
1.
2.
3.
Click Customize in the System and Event Collections panel. The Customize Collections page
appears.
In the Show collections of dropdown list, select Events. All available event collections appear.
Click New. The New Collection section appears.
262 Operations
4.
Select Choose members individually, Choose members by attributes, or Choose members from
existing event and system collections.
a. If you selected Choose members individually, complete the following steps:
i. In the Choose from dropdown list, select an individual collection.
NOTE: When a collection is selected from the dropdown list, the first-level members
of that collection appear in the Available Items box.
ii.
From the Available Items box, select items to place in the collection by highlighting
the item and clicking
. You can click the up and down arrow to change the position
of an item in the collection, or click Remove to remove items from the Selected Items
box.
iii. Click one of the following:
•
Save As Collection
To save the collection. See Saving collections for more information about saving
collections.
•
Cancel
To close the New Collection section without saving changes.
b.
If you selected Choose members by attributes, the New section appears. Complete the
following steps:
i. In the Search for dropdown list, select events.
ii. Enter the search criteria for the collection. See Performing an advanced search for
events for more information about event search criteria.
iii. Click one of the following:
•
View
To run the search and display the results immediately.
•
Save As Collection
To save the collection. See Saving collections for more information.
•
Cancel
To close the New Collection section without saving changes.
c.
If you selected Choose members from existing event and system collections, complete the
following steps:
i. In the Select event collection dropdown list, select an event collection.
NOTE:
Combination collections are not displayed in the dropdown list.
ii. In the Select system collections dropdown list, select a system collection.
iii. Click one of the following:
•
View
To run the search and display the results immediately.
•
Save As Collection
To save the collection. See Saving collections for more information about saving
collections.
•
Cancel
To close the New Collection section without saving changes.
Monitoring systems and events 263
Command line interface
Users with administrative rights can use the mxcollection command to create new collections
from the CLI.
Related information
Editing event collections
The Event Collections section enables you to add, delete, and reorder the position of members of
an existing collection. This section is similar to the New Collection section.
NOTE: Users with administrative rights can edit a shared collection. Users with operator rights
can edit only their own collections.
Procedure 124 Editing event collections
1.
2.
Click Customize in the System and Event Collections panel. The Customize Collections page
appears.
In the Show collections of dropdown list, select Events. All available event collections appear.
264 Operations
3.
Select the event collection to edit, and then click Edit. The Edit Collection section appears.
Depending on how the collection was created, the following appears:
a. If you created the collection with the Choose members individually option, complete the
following steps:
i. In the Choose from dropdown list, select an individual collection.
NOTE: When a collection is selected from the dropdown list, the first-level members
of that collection appear in the Available Items box.
ii.
From the Available Items box, select items to place in the collection by highlighting
the item and clicking
. You can click the up and down arrow to change the position
of an item in the collection, or click Remove to remove items from the Selected Items
box.
iii. Click one of the following:
•
OK
To save the collection.
•
Cancel
To close the New Collection section without saving changes.
b.
If you created the collection with the Choose members by attributes option, complete the
following steps:
i. In the Search for dropdown list, select events.
ii. Enter the search criteria for the collection. See Performing an advanced search for
events for more information about event search criteria.
iii. Click one of the following:
•
View
To run the search and display the results immediately.
•
OK
To save the collection.
•
Cancel
To close the New Collection section without saving changes.
c.
If you created the collection with the Choose members from existing system and event
collections option, complete the following steps:
i. In the Select event collection dropdown list, select an event collection.
NOTE:
Combination collections are not displayed in the dropdown list.
ii. In the Select system collections dropdown list, select a system collection.
iii. Click one of the following:
•
View
To run the search and display the results immediately.
•
OK
To save the collection.
•
Cancel
To close the New Collection section without saving changes.
Monitoring systems and events 265
Command line interface
Users with administrative rights can use the mxcollection command to edit existing collections
from the CLI.
For more information about accessing the manpage, which includes detailed information for this
command, see the HP Systems Insight Manager Command Line Interface Guide, at http://
www.hp.com/go/insightmanagement/sim/docs.
Related information
Moving event collections
This procedure enables you to move a collection from one collection to another. Users with
administrative rights can move a shared collection.
Procedure 125 Moving event collections
1.
2.
Click Customize in the System and Event Collections panel. The Customize Collections page
appears.
In the Show collections of dropdown list, select Events. All available event collections appear.
3.
4.
Click
to expand all event collections in the table, or click
to collapse all event
collections in the table.
Select the collection to move, and then click Move. The Move Collection section appears.
Under Move to, select one of the following:
•
Existing collection
Select an existing private or shared collection from the dropdown list. Click OK to save
the collection, or click Cancel to cancel the save operation.
Locked collections do not appear in the list.
•
New collection
Enter a name for the new collection and select an existing private or shared collection
from the dropdown list. Click OK to save the collection, or click Cancel to cancel the save
operation.
Command line interface
Users with administrative rights can use the mxcollection command to move existing collections
from the CLI.
Related information
Copying event collections
You can copy a collection as a new collection. When you copy a collection that was created by
members, you copy the collection and its members into the new collection. If you edit the original
collection after you copy it to the new collection, the newly copied collection is not updated. For
example, if the original collection has two members, the same two members copy to the new
collection. If you edit the original collection to add another member after you copy it, the newly
copied collection is not modified.
When you copy a collection that was created based on attributes, you copy the collection attributes
into the new collection. If you edit the original collection after you copy it to the new collection,
the newly copied collection does not reflect these edits.
When you copy a combination collection, the newly created collection has the same system
collection and event collection. If you edit the original collection after you copy it to the new
collection, the newly copied collection is not updated. For more information about collections, see
the HP Systems Insight Manager User Guide, at http://www.hp.com/go/insightmanagement/
sim/docs.
266 Operations
Procedure 126 Copying event collections
1.
Click Customize in the System and Event Collections panel. The Customize Collections page
appears.
2.
In the Show dropdown list, select Events. All available event collections appear. Click
3.
4.
5.
to expand all event collections in the table, or click
to collapse all event collections in
the table.
Select the collection to copy, and then click Copy. The Copy Collection section appears.
In the Collection name field, enter a name for the collection.
Under Place in, select a location to save the collection.
•
Existing collection
Select an existing private or shared collection from the dropdown list. Click OK to save
the collection, or click Cancel to cancel the save operation.
Locked collections do not appear in the list.
•
New collection
Enter a name for the new collection and select an existing private or shared collection
from the dropdown list. Click OK to save the collection, or click Cancel to cancel the save
operation.
Command line interface
Users with administrative rights can use the mxcollection command to copy existing collections
from the CLI.
Related information
Deleting event collections
NOTE: Users with administrative rights can delete a shared collection. Users with operator rights
or user rights can view shared collections, but can only delete their own private collections.
Procedure 127 Deleting event collections
1.
Click Customize in the System and Event Collections panel. The Customize Collections page
appears.
2.
In the Show dropdown list, select Events. All available event collections appear. Click
3.
4.
to expand all event collections in the table, or click
to collapse all event collections in
the table.
Select the collection to be deleted.
Click Delete. A dialog box appears. To continue with the deletion, click OK, or to cancel the
operation, click Cancel. If the selected collection is not empty or is in use by a task (such as
Home page, reports, and so on) an error message appears. However, if the collections contents
are based on attributes, you can delete the collection even if it is not empty.
Command line interface
Users with administrative rights can use the mxcollection command to delete existing collections
from the CLI.
Related information
Setting event properties
You can use the System and Event Collections panel to set event collection properties such as hiding
or showing collections.
Monitoring systems and events 267
Procedure 128 Setting properties for event collections
1.
2.
3.
4.
Click Customize in the System and Event Collections panel. The Customize Collections page
appears.
In the Show collection of dropdown list, select Events. All available event collections appear.
Click
to expand all event collections in the table, or click
to collapse all event
collections in the table.
Select a collection, and then click Set Properties. The Set Properties section appears.
Under Visible, select Yes, show collection and its members in the user interface or select No,
do not show collection and its members in the user interface . If you have collections that are
unused, you might want to select No, do not show collection and its members in the user
interface so that the collections do not clutter the System and Event Collections panel.
Command line interface
Users with administrative rights can use the mxcollection command to set properties for
collections from the CLI.
Related information
System table view page
Users with administrative rights can manage all shared system collections from the system table
view page. Users can also manage their own private collections from this page. They can:
•
Save selections
See Saving collections for more information.
•
Delete systems from the database
See Deleting systems from the HP SIM database for more information.
•
Print a system collection results
See Printing a system collection view for more information.
•
Customize the view
See Customizing the system table view page for more information.
The system table view page contains the following tabs:
•
System(s)
Lists all systems in the collection.
•
Events
Displays the events for all systems included under the System(s) tab. From this tab, you can
apply additional filters to modify the event table display.
When switching between the System(s) tab and the Events tab, the Events tab "remembers" the
selected events and event filter (if viewing a system collection). The System(s) tab remembers the
selected systems, view type (table, tree, or icon), and the selected system filter (if viewing an event
collection). However, the selections on each page are independent of each other.
Related information
Customizing the system table view page
The Customize link is located in the upper right corner of the system table view page. Click this
link to configure where columns appear and in what order. When you modify the columns to
display on the system table view page and select Apply to all system table views, these columns
become the default set of columns displayed for any system collection selected if the collection
268 Operations
does not already have customized columns defined. For more information, see Customizing the
system table view page.
Procedure 129 Customizing the system table view page
1.
On the system table view page, click Customize. The Customize Table View Appearance page
appears.
2.
3.
Select the columns you want displayed in the Available Columns box, and then click
to
add the columns to the Displayed Columns box.
To remove one or more columns from the display, select the columns in the Displayed Columns
4.
box, and then click
to move them to the Available Columns box.
To rearrange how the columns appear, select a column in the Displayed Columns box, and
5.
6.
7.
8.
then click
or .
To sort collection results by a particular column, select a column from the Sort by dropdown
list.
Select Ascending or Descending.
To apply the customization to all system collections, select Apply to all system collections.
To save selections and return to the system table view page, click OK, or to cancel all changes
and return to the system table view page, click Cancel.
Related information
Deleting systems from the HP SIM database
NOTE:
Deleting multiple systems from the database at one time can cause performance delays.
NOTE:
The CMS cannot be deleted.
NOTE: You cannot delete clusters that contain cluster members. To delete a cluster with its cluster
members, you must first go to the system table view page by selecting the All Systems collection
in the System and Event Collections panel. Then, select the cluster along with all of its members,
and then click Delete.
IMPORTANT:
If you do not add the IP addresses of the systems to the discovery exclusion list,
the systems are rediscovered and added again to the database.
Procedure 130 Deleting systems from the HP SIM database
1.
2.
3.
On the system table view page, select one or more systems to delete from the HP SIM database
by selecting them in the results display.
Click Delete. A dialog box appears, stating, Are you sure you want to delete
these systems?
To delete the systems, click OK, or to return to the system table view page without deleting
the events, click Cancel.
NOTE: Containers (for example, racks) must be empty before you can delete them. Selecting a
rack and all its contained systems work without error.
NOTE: You cannot remove some systems that host management proxies (such as the WMI Mapper
Proxy or an SMI-S provider) until you remove all dependant systems.
Printing a system collection view
Procedure 131 Printing systems from the system table view page
1.
2.
On the system table view page, click Print. A print window appears
When the report appears, select File→Print from the browser menu.
Monitoring systems and events 269
Because certain print options are not supported in Systems Insight Manager, you cannot perform
the following tasks:
•
Change the Orientation to Landscape in the Print dialog box.
•
Cancel printing after the print job has been executed; however, you can access the operating
systems print queue and cancel the print job
•
Print to a file
•
Print specific selections; you can print the entire list only
•
Print the table view page if you close the browser immediately after issuing a print request
Related information
Cluster table view page
To access Cluster collections in the System and Event Collections panel, click Systems and then
select one of the available cluster collections. Users with administrative rights can manage all
shared cluster collections from the cluster collection view. Users can manage their own private
collections from this page, as well as:
•
Save collections
Click Save As Collection from the cluster table view page.
•
Delete clusters
Click Delete from the cluster table view page. A confirmation box appears. To delete the
cluster, click OK, or to cancel the deletion, click Cancel.
NOTE:
Clusters that contain cluster members cannot be deleted. To delete a cluster with its
cluster members, select the All Systems collection in the System and Event Collections panel.
Then, select the cluster and all of its members, and then click Delete.
•
Print cluster collection view
Click Print to print the collection results.
•
Customize the view
Click Customize to customize which columns display and in what order.
Tabs
The cluster table view page contains the following tabs:
•
System(s)
Lists all systems in the collection.
•
Events
Displays the events for all systems included under the System(s) tab. From this tab, you can
apply additional filters to modify the event table display.
When switching between the System(s) tab and the Events tab, the Events tab "remembers" the
selected events and event filter (if viewing a system collection). The System(s) tab remembers the
selected systems, view type (table, tree, or icon), and the selected system filter (if viewing an event
collection). However, the selections on each page are independent of each other.
Related information
270 Operations
Customizing the cluster table view page
When you modify the columns to display on the cluster table view page and select Apply to all
cluster table views, these columns become the default columns displayed for any cluster collection
selected if that collection does not already have customized columns defined.
Procedure 132 Customizing the cluster table view page
1.
On the cluster table view page, click Customize. The Customize Table View Appearance page
appears.
2.
3.
Select the columns you want displayed in the Available Columns box, and then click
to
add the columns to the Displayed Columns box.
To remove one or more columns from the display, select the columns in the Displayed Columns
4.
box, and then click
to move them to the Available Columns box.
To rearrange how the columns appear, select a column in the Displayed Columns box, and
5.
6.
7.
8.
then click
or .
To sort the list by a particular column, select a column from the Sort by dropdown list.
Select Ascending or Descending.
If you want the customization to apply to all cluster collections, select Apply to all cluster table
views.
To save selections and return to the cluster table view page, click OK, or to cancel all changes
and return to the cluster table view page, click Cancel.
Related information
Deleting clusters from the HP SIM database
You cannot delete clusters that contain cluster members defined in HP SIM. To delete a cluster with
its cluster members, select the All Systems collection in the System and Event Collections panel.
Then, select the cluster and all of its members, and then click Delete.
IMPORTANT:
If you do not add the IP addresses of the deleted clusters to the discovery exclusion
list, the systems will be rediscovered and added again to the database.
Procedure 133 Deleting clusters
1.
2.
3.
On the cluster table view page, select one or more clusters to delete from the database by
highlighting them.
Click Delete. A dialog box appears, stating, Are you sure you want to delete
these systems?
To delete the clusters, click OK, or to return to the cluster table view page without deleting the
clusters, click Cancel.
Related information
Printing a cluster collection view
Procedure 134 Printing a list of clusters from the table view page
1.
2.
From the cluster table view page, click Print.
When the report appears, select File→Print in the browser menu.
Because certain print options are not supported in HP SIM, you cannot perform the following tasks:
•
Change the Orientation to Landscape in the Print dialog box.
•
Cancel printing after the print job has been executed; however, you can access the operating
systems print queue and cancel the print job
•
Print to a file
Monitoring systems and events
271
•
Print specific selections; you can print the entire list only
•
Print the table view page if you close the browser immediately after issuing a print request
Related information
Event table view page
To access event collections, click Events in the System and Event Collections panel. Users with
administrative rights can manage all shared event collections from the event table view page. All
users can manage their own private event collections from this page, and perform the following
tasks:
•
Clear events
Select one or more events to clear, and then click Clear.
•
Delete events
Select one or more events to delete, and then click Delete.
•
Assign events
Select one or more events to assign to specific users, and then click Assign to.
•
Add comments to events
Select one or more events to add comments to, and then click Enter Comment.
•
Print event collection results
Click Print to print the collection results.
•
Customize the view
Click Customize to customize which columns appear and in what order.
For users with operator rights and user rights to clear, delete, assign events, and add comments
to events, you must select Configuration Tool from the Show tools in category dropdown list. Then,
select Clear Events, Delete Events, Assign Events, and Comment Events as necessary, and then click
to add them to the Toolbox contents.
The event table view page contains the following tabs:
•
System(s)
Lists all systems in the collection.
•
Events
Displays the events for all systems included under the System(s) tab. From this tab, you can
apply additional filters to modify the event table display.
When switching between the System(s) tab and the Events tab, the Events tab "remembers" the
selected events and event filter (if viewing a system collection). The System(s) tab remembers the
selected systems, view type (table, tree, or icon), and the selected system filter (if viewing an event
collection). However, the selections on each page are independent of each other.
Related information
Customizing the event table view page
When you modify what columns display on the event table view page and select Apply to all event
table views, these columns become the default set of columns that appear for any cluster collection
selected if the collection does not already have customized columns defined.
Procedure 135 Modifying the event table view page
1.
On the event table view page, click Customize. The Customize Table View Appearance page
appears.
272 Operations
2.
3.
Select the columns you want displayed from the Available Columns box, and then click
to
add the columns to the Displayed Columns box.
To remove one or more columns from the display, select the columns in the Displayed Columns
4.
box, and then click
to move them to the Available Columns box, so they no longer appear.
To rearrange how the columns display, select a column in the Displayed Columns box, and
5.
6.
7.
8.
then click
or .
To sort the collection by column, select a column from the Sort by dropdown list.
Select Ascending or Descending.
To apply the customization to all event collections, select Apply to all event collections.
To save selections and return to the event table view page, click OK, to cancel all changes
and return to the event table view page or click Cancel.
Related information
Clearing events from the collection
You must have administrative rights to clear events.
NOTE:
For users with operator and user rights to clear events, they must have the Clear Events
tool selected in their toolbox categories. See Editing toolboxes for more information.
Procedure 136 Clearing events
1.
2.
On the event table view page, select the event that you want to clear.
Click Clear. For the events selected, the state changes from Not Cleared to Cleared in the
State column.
Related information
Deleting events from the HP SIM database
You must have administrative rights to delete events, including Discovery events. However, you
cannot delete pending events. For users with operator and user rights to delete events, they must
have the Delete Events tool selected in their toolbox categories. See Editing toolboxes for more
information.
Procedure 137 Deleting events
1.
2.
3.
On the event table view page, select the event you want to delete.
Click Delete. A confirmation box appears.
To delete the event, click OK, or to return to the event table view page, click Cancel.
Related information
Assigning events to users
You must have administrative rights to assign events from shared collections. For users with operator
and user rights to assign events, they must have the Assign Events tool selected in their toolbox
categories. For more information, see Editing toolboxes.
IMPORTANT:
Assigning events to certain users does not facilitate any tracking, and the user is
not notified of the event.
CAUTION: If selected events have previously been assigned, selecting a new assignee and
clicking OK overrides the previous assignment.
NOTE:
You can enter a maximum of 50 characters in the assignee field.
Monitoring systems and events 273
Procedure 138 Assigning events
1.
2.
3.
4.
On the event table view page, select the events you want to assign to a user.
Click Assign To. The Assign to section appears.
Select New assignee or Choose existing assignee. If you select Choose existing assignee, click
the down arrow, and then select an assignee from the dropdown list.
To update the database, click OK, or click Cancel.
Related information
Printing an event collection view
Procedure 139 Printing events from the event table view page
1.
2.
On the event view page, click Print. A printable window appears.
When the report appears, select File→Print in the browser menu.
Because certain print options are not supported in Systems Insight Manager, you cannot perform
the following tasks:
•
Change the Orientation to Landscape in the Print dialog box.
•
Cancel printing after the print job has been executed; however, you can access the operating
systems print queue and cancel the print job
•
Print to a file
•
Print specific selections; you can print the entire list only
•
Print the table view page if you close the browser immediately after issuing a print request
Related information
Entering comments to events
Use the following procedure to add comments to events. You must have administrative rights to
add comments to events.
CAUTION: If you add comments to events that already have comments, the previous comments
are replaced with the new comments in the database.
NOTE:
For users with operator and user rights to add comments to an event, they must have the
Comment Events tool selected in their toolbox categories. For more information, see Editing
toolboxes.
NOTE:
The maximum number of characters allowed for comments is 1,000.
Procedure 140 Adding comments to events
1.
2.
3.
4.
On the event table view page, select the events for which you want to enter comments.
Click Enter Comments. The Enter Comments section appears.
Enter the comments.
To update the database, click OK, or to return to the event table view page, click Cancel.
Related information
Saving collections
Perform the following procedure to save a system, event, or cluster collection with a new name or
to a specific location.
NOTE: For a system search, the name can contain no more than 40 characters (no special
characters) and must be unique so that a duplicate collection name cannot be assigned to the new
collection, and cannot include special characters.
274
Operations
Procedure 141 Saving collections
1.
2.
In the Name field, enter a name for the collection.
Under Place in, select one of the following options to save the collection:
•
Existing collection
Select an existing private or shared collection from the dropdown list. Click OK to save
the collection, or click Cancel to cancel the save operation.
Locked collections do not appear in the list.
•
New collection
Enter a name for the new collection and select an existing private or shared collection
from the dropdown list. Click OK to save the collection, or click Cancel to cancel the save
operation.
Related information
Related information
Related procedures
Editing system and cluster collections
Creating system and cluster collections
Deleting system and cluster collections
Setting properties for system and cluster collections
Editing event collections
Creating event collections
Deleting event collections
Moving event collections
Copying event collections
Setting event properties
Editing system and cluster collections
Creating system and cluster collections
Deleting system and cluster collections
Moving system and cluster collections
Copying system and cluster collections
Setting properties for system and cluster collections
Customizing the system table view page
Deleting systems from the HP SIM database
Printing a system collection view
Customizing the cluster table view page
Deleting clusters from the HP SIM database
Printing a cluster collection view
Customizing the event table view page
Deleting events from the HP SIM database
Printing an event collection view
Entering comments to events
Assigning events to users
Clearing events from the collection
Saving collections
Related topics
Quick Launch menu
Navigating the System and Event Collections panel
Customizing system and cluster collections
Customizing event collections
Navigating the cluster table view page
Monitoring systems and events 275
Navigating
Navigating
Navigating
Navigating
Navigating
the
the
the
the
the
event table view page
picture view page
icon view
system table view page
tree view
Quick Launch menu
The Quick Launch menu contains a short list of frequently used tools. Customizing the Quick Launch
menu enables you to select which tools appear in the menu. Tools appear only in the Quick Launch
menu if all the selected targets are valid for that tool. Customizations are on a per-user basis. The
Quick Launch menu is available from the following pages in HP SIM:
•
All views (table, tree, icon, or picture) of all collections
•
Search Results page
•
System Page
Procedure 142 Customizing the Quick Launch menu
1.
2.
Click Customize in the Quick Launch menu. The Customize Quick Launch page appears.
Select a menu category from the Available tools from dropdown list. All available tools from
that menu are listed.
3.
Select tools to add to the Selected tools list and click
.
To remove tools from the Selected tools list, highlight the tools to remove and click
Click
4.
or
.
to arrange tools in the list.
(Optional) Select Show original menu structure (and order) in the Quick Launch menu.
This displays the menu paths in the Quick Launch menu.
5.
Click OK to save changes, or click Restore Defaults to restore system defaults.
Performing a basic search
Perform this procedure to complete a basic system search by searching for matches in system name
and common system attributes.
Procedure 143 Performing a basic search
1.
Enter a system name or keyword in the Search panel.
As you type, a dropdown list displays systems with names that begin with the text entered.
The list includes up to 12 systems and shows the icon for the system health status. If more than
12 systems are found, an ellipsis (...) appears at the bottom of the list. Continue typing to
narrow the list further.
NOTE:
2.
Press Esc to hide the dropdown list.
•
To view the System Page for a single system, select it with the mouse or select it with the
up and down arrows on your keyboard, and then press Enter.
•
If you want to search for multiple systems or a system attribute, do not select a system in
the dropdown list. Press Enter or click Search. The Search Results page appears and lists
all matching systems.
To do an additional search from the Search Results page, enter the system name or attribute
in the Search again field, and then select system name or common system attributes in the
dropdown menu. Click View. The new Search Results appear.
276 Operations
NOTE: Common system attributes include Full DNS name, Device hostname, Serial number,
Operating System Type, Operating System Version, Operating System description, Operating
System name, Product model, System type, and IP address.
NOTE: Searching using common system attributes can be time-consuming if there are a large
number of systems because the search looks at several attributes in the database multiplied
by the number of discovered systems.
3.
(Optional) After the search results appear, you can do one of the following:
•
Save the search results. Click Save As Collection, enter a name for the search, and then
select where to save the collection. See Saving collections for more information. to save
the search, click OK, or to return to the Search Results page, click Cancel.
•
Perform a more advanced search. Click Advanced Search. The Advanced Search page
appears.
Related information
Performing an advanced search for systems
Use the following procedure to perform an advanced search for systems. The following image
shows the Advanced Search page for systems.
Procedure 144 Performing an advanced search for systems
1.
2.
3.
Click Advanced Search in the Search panel.
Select systems from the Search for dropdown list.
From the first selection box (criteria selection), click the down arrow, and then select the search
criteria.
NOTE: Some search criteria show no values until systems with values for that criteria have
been discovered. In this case, the criteria is not displayed until values are available.
4.
From the second selection box (comparison selection), click the down arrow, and then select
the comparison option.
NOTE: Different criteria support different comparisons. The comparison options change with
the criteria selected. For example, if you select operating system as criteria, the following
possible comparisons are available: is, is not, contains, starts with, and ends with. See the
HP Systems Insight Manager User Guide, at http://www.hp.com/go/insightmanagement/
sim/docs, for more information.
Performing an advanced search for systems 277
5.
6.
In the third selection box (value selection), select one of the available values for specific criteria
or comparison combination from the dropdown list, or enter the required information in the
input box.
To add additional criteria, click Add. To conduct the system search immediately, click View.
To delete search criteria, click Delete. To save the search as a collection, click Save As.
NOTE: Criteria are reordered after clicking View or Save As. If criteria types are the same,
they are placed together with "OR", if they are different, they are placed together with "AND".
7.
If you clicked View, search results appear. You can chose to delete or print the results. See
Deleting system search results from a search view for more information about deleting selections.
See Printing system search results for information about printing search results.
Related information
Deleting system search results from a search view
NOTE:
Deleting multiple systems from the list can cause performance delays.
Procedure 145 Deleting systems from a system advanced search
1.
2.
After the search results appear, select systems to delete from the search, and then click Delete.
A dialog box appears, stating, Are you sure you want to delete these systems?
To delete the systems, click OK, or to return to the Search Results page without deleting the
systems click Cancel.
NOTE: Containers (for example, racks) must be empty before they can be deleted. Selecting
a rack and all its contained systems works without error.
Related information
Printing system search results
Procedure 146 Printing system advanced search results
1.
2.
After the Search Results page appears, click View. The results appear.
Click Print.
The results are printed.
NOTE: The Print dialog box might be hidden. If so, go to the Windows Task Bar to display
the box.
Because the following print options are not supported in HP SIM, you cannot perform the
following tasks:
•
Change the Orientation to Landscape in the Print dialog box.
•
Cancel printing after the print job has been executed; however, you can access the
operating system's print queue and cancel the print job
•
Cancel printing to a file
•
Print selected systems; only the entire list of systems
•
Print the system search results if you close the browser immediately after issuing a print
request
Related information
Performing an advanced search for clusters
Use the following procedure to perform an advanced search for clusters. The following image
shows the Advanced Search page for clusters.
278 Operations
Procedure 147 Performing an advanced search for clusters
1.
2.
3.
Click Advanced Search in the Search panel.
Select clusters from the Search for dropdown list.
From the first selection box (criteria selection), click the down arrow, and then select the search
criteria.
NOTE: Some search criteria show no values until systems with values for that criteria have
been discovered. In this case, the criteria is not displayed until values are available.
4.
From the second selection box (comparison selection), click the down arrow, and then select
the comparison option.
NOTE: Different criteria support different comparisons. The comparison options change with
the criteria selected.
5.
6.
7.
In the third selection box (value selection), select one of the available values for a specific
criteria or comparison combination from the dropdown list, or enter the required information
in the input box.
To add additional criteria, click Add. To conduct the cluster search immediately, click View.
To delete search criteria, click Delete, or to save the search as a collection, click Save as
collection.
If you clicked View, the search results appear. You can choose to delete or print the results.
See Deleting system search results from a search view for more information about deleting
selections. See Printing system search results for information about printing search results.
Related information
Deleting cluster search results from a search view
NOTE:
Deleting multiple clusters from a collection can cause performance delays.
NOTE:
You cannot delete clusters that contain cluster members. To delete a cluster and its cluster
members, select the All Systems collection in the System and Event Collections panel. Then, select
the cluster and all of its members, and then click Delete.
Procedure 148 Deleting clusters from search results
1.
2.
After the search results appear, select clusters to delete from the search, and then click Delete.
A dialog box appears, stating, Are you sure you want to delete these systems?
To delete the systems, click OK, or to return to the Search Results page without deleting the
clusters, click Cancel.
Related information
Performing an advanced search for clusters 279
Printing cluster search results
Procedure 149 Printing cluster search results
1.
2.
After the Search Results appears, click View. The results appear.
Click Print.
The results are printed.
NOTE: The Print dialog box might be hidden. If so, go to the Windows Task Bar to display
the box.
Because the following print options are not supported in HP SIM, you cannot perform the
following tasks:
•
Change the Orientation to Landscape in the Print dialog box.
•
Cancel printing after the print job has been executed; however, you can access the
operating system's print queue and cancel the print job
•
Cancel printing to a file
•
Print selected clusters; only the entire search results
•
Print the cluster search results if you close the browser immediately after issuing a print
request
Related information
Performing an advanced search for events
Use the following procedure to perform an advanced search for events. The following image shows
the Advanced Search page for events.
NOTE: You can quickly display all service events of Any type by selecting
Systems→Events→Shared→Service Events→All HP Service Events from the System and Event
Collections panel.
Procedure 150 Performing an advanced search for events
1.
2.
3.
Click Advanced Search in the Search panel.
Select events from the Search for dropdown list.
From the first selection box (criteria selection), click the down arrow, and then select the search
criteria.
NOTE: If you selected event type, see the HP Systems Insight Manager User Guide, at http://
www.hp.com/go/insightmanagement/sim/docs, under "Search criteria" for more information.
NOTE: Some search criteria show no values until systems with values for that criteria have
been discovered. In this case, the criteria is not displayed until values are available.
280 Operations
4.
From the second selection box (comparison selection), click the down arrow, and then select
the comparison option.
NOTE: Different criteria support different comparisons. The comparison options change with
the criteria selected. For example, if you select operating system as criteria, the following
comparisons are available: is, is not, contains, starts with, and ends with.
5.
6.
7.
In the third selection box (value selection), select one of the values for a specific criteria or
comparison combination from the dropdown list, or enter the required information in the input
box.
To add additional criteria, click Add, or to conduct the event search immediately, click View.
to delete search criteria, click Delete, or to save the search as a list, click Save as collection.
If you clicked View, search results appear. You can choose to delete or print the results. See
Deleting system search results from a search view for more information about deleting selections.
See Printing system search results for information about printing search results.
NOTE: To search for new event types generated by HTTP events, select events by Event Category
Selection, and then select the event type from the and type is list.
Related information
Deleting event search results from a search view
NOTE:
Deleting multiple events from the list can cause performance delays.
Procedure 151 Deleting events from search results
1.
2.
After the search results appear, select events to delete from the search, and then click Delete.
A dialog box appears, stating, Are you sure you want to delete these systems?
To delete the events, click OK, or to return to the Search Results page without deleting the
events click Cancel.
Related information
Printing event search results
Procedure 152 Printing event search results
1.
2.
After the Search Results page appears, click View. The results appear.
Click Print.
The results are printed.
NOTE: The Print dialog box might be hidden. If so, go to the Windows Task Bar to display
the box.
Because the following print options are not supported in HP SIM, you cannot perform the
following tasks:
•
Change the Orientation to Landscape in the Print dialog box.
•
Cancel printing after the print job has been executed; however, you can access the
operating system's print queue and cancel the print job
•
Cancel printing to a file
•
Print selected events; only the entire search results
•
Print the event search results if you close the browser immediately after issuing a print
request
Related information
Performing an advanced search for events
281
Tool search
The Tool Search feature provides a quick way to search and filter textually, based on tool names,
tool locations in the HP SIM cascading menu structure, and tool descriptions.
•
The tool search feature searches, matches, and highlights as you enter information.
•
The tree structure of the menu is represented exactly. If no filter text is supplied, the menu is
rendered in a tree format for browsing.
•
Searches are not case sensitive.
•
Tools are hyperlinked and can be launched from the tree.
•
Tool names, menu paths, and descriptions are searched. If you are not authorized for a tool,
it is not included in the search.
•
As an example, when you search on SNMP using the following procedure, matching tools
include SNMP in their names but in their descriptions. By reading the short description, you
learn how SNMP applies to the tool, and you get a quick overview of the tool.
Related information
Searching for tools
Procedure 153 Performing a tool search
1.
2.
Click the
icon to expand the tree, or enter text in the Search for box.
After you locate a tool, click the tool link to be taken to the tool page.
Related information
Related information for searches
Related procedures
Deleting system search results from a search view
Printing system search results
Deleting cluster search results from a search view
Printing cluster search results
Saving collections
Deleting event search results from a search view
Printing event search results
Searching for tools
Related topics
Performing an advanced search for events
Performing an advanced search for clusters
Performing a basic search
282 Operations
Deleting cluster search results from a search view
Printing cluster search results
Tool search
Configuring events
Managing events in HP SIM includes the following tasks:
•
Automatic Event Handling which enables you to manage automatic event handling tasks,
create new automatic event handling tasks, and configure e-mail and modem settings.
•
Clearing Events which enables you to clear events.
•
Deleting Events which enables you to delete events from the database.
•
Event Filter Settings which enables you to filter SNMPtraps you receive from discovered systems.
The default setting is to accept all registered SNMP traps from all discovered systems. You
can specify the severity of the traps you want to see and use the IP address ranges to create
a subset of systems whose traps you can receive or ignore. For example, you can use event
filtering to ignore informational traps. This feature is available to users with administrative
rights.
•
SNMP Trap Settings which enables you to tailor trap messages to your specific network needs.
Trap messages can be cryptic, poorly written, and incomprehensible. You can modify the MIB
information in the database representation. You can also modify a .cfg file of the MIB. HP
recommends that you never modify an actual MIB.
•
Status Change Event Settings which enables you to configure the settings for sending status
change events for systems when hardware status changes.
•
Subscribing to WBEM Events which enables you to subscribe to WBEM events.
•
Unsubscribing to WBEM Events which enables you to unsubscribe to WBEM events.
Editing automatic event handling tasks
Two users cannot edit Automatic Event Handling tasks at the same time. The first user to click Finish
has their changes saved. The second user receives an error message, stating Unable to modify
task.
NOTE: After a task is selected on the Automatic Event Handling - Manage Tasks page, the task
summary appears when clicking View Definition.
Procedure 154 Editing events
•
Follow the on-screen instructions.
See Creating an automatic event handling task for more information about each of the steps.
NOTE: Select an event collection or an event combination collection. The event collection
is a collection that is made up of event attributes. If you select an event collection that contains
additional event collections, you will receive an error message.
Related information
Copying automatic event handling tasks
Procedure 155 Copying event handling tasks
1.
2.
In the Task name field, enter a name for the new task.
Click OK. The task is copied with a new name and placed in the list of Automatic Event
Handling tasks.
Related information
Configuring events 283
Viewing task definitions for automatic event handling tasks
Complete the following procedure to view the entire task configuration for a selected task. These
configuration options were set when creating the task.
Procedure 156 Viewing task definition details
1.
2.
Select Options→Events→Automatic Event Handling→Manage Task. The Automatic Event
Handling - Manage Tasks page appears.
Select a task, and then click View Definition. The View Definition section appears, displaying
the following information:
•
Task name
The name given to the task when it was created
•
Owner
The user who created the task
•
Time filters
The times that the task runs
•
Event collection
The event collection that was selected when the task was created
NOTE: This field appears if you selected an existing private or shared event collection.
If the collection was created using the Automatic Event Handling feature, this does not
appear.
•
Events
The event search criteria set for the task
•
Systems
The system collection selected for the task
•
Action(s)
The actions selected when the task was created
•
E-mail settings
The e-mail settings set when the task was created
See Creating an automatic event handling task for more information about each of the settings.
NOTE: If the task was created with no event or system information in the collection selected, the
Events or the Systems field will show None Defined. If you edit the task, you will be forced to select
the event or system information for the collection. Prior to HP SIM 5.1, if no system or event
information was included in the task, the All Systems and All Events collections were displayed
respectively.
Related information
Viewing event task results
Procedure 157 Viewing event task results
1.
2.
Select Options→Events→Automatic Event Handling→Manage Task. The Automatic Event
Handling - Manage Tasks page appears.
Select a task to view the task results, and then click Task Results. The Task details section
appears.
See Task results list for more information about the details displayed.
284 Operations
Related information
Enabling and disabling event handling tasks
NOTE: This option is especially useful for notification tasks imported from Insight Manager 7,
which are imported into HP SIM in a disabled state. You can edit these tasks, verify that the settings
are accurate, and then enable the tasks by clicking Enable.
NOTE:
The button label changes depending on if the task is enabled or disabled.
Procedure 158 Enabling or disabling event handling tasks
1.
2.
3.
Select Options→Events→Automatic Event Handling→Manage Task. The Automatic Event
Handling - Manage Tasks page appears.
Select a task to enable or disable.
If the task is enabled and you want to disable it, click Disable, or if the task is disabled and
you want to enable it, click Enable.
Related information
Configuring e-mail settings
Procedure 159 Configuring e-mail settings
1.
2.
3.
Enter the SMTP host name. The SMTP host is the outgoing e-mail server that the CMS uses to
send e-mail notifications.
In the Sender's e-mail address box, enter the e-mail address that the management server uses
when sending e-mail notifications.
Optional: Select Send test email and enter recipients e-mail address.
Click Send test email now.
4.
5.
To authenticate your SMTP server, select Server Requires Authentication.
Enter the account user name and password in the corresponding boxes.
NOTE: If you did not enter a valid SMTP host, HP SIM display an error message: The email
could not be sent: Could not connect to the SMTP host.
If you are changing the e-mail settings from the Options→Events→Automatic Event
Handling→Email Settings page, click OK to save changes.
NOTE: If the Server Requires Authentication option is selected, and you enter incorrect account
information, an The email could not be sent: Authentication error message displays.
Additional e-mail settings
The globalsettings.props contains properties that can be set for additional information to
be included in e-mail messages.
EmailPrefixUserSubject
To have user defined information (from the e-mail information on the Actions page) displayed first
on the subject line of an e-mail, you must change the EmailPrefixUserSubject property in the
Enabling and disabling event handling tasks 285
globalsettings.props file to True. Otherwise, HP SIM defined information appears first. The
globalsettings.props file is located at:
•
On Windows
It is typically located at C:\Program Files\HP\Systems Insight Manager\config\
globalsettings.props.
•
On HP-UX and Linux
It is located at /etc/opt/mx/config/globalsettings.props.
Restart the HP SIM service after the flag is set. To restart:
•
If EmailPrefixUserSubject = false
The format of the subject line is Device Name: Short Description from Alert: User's Defined
Subject.
•
If EmailPrefixUserSubject = true
The format of the e-mail subject line is User's Defined Subject: Device Name: Short Description
from Alert.
IMPORTANT:
This property does not need to be configured for the e-mail feature to work. This
property is automatically set to false in the globalsettings.props file and does not need to
be changed unless you want user defined text to appear before the HP SIM text in the subject line.
EmailKeywords
To include event information in an e-mail message, edit the EmailKeywords property in the
globalsettings.props file.
IMPORTANT:
Restart the HP SIM service if any of the keywords change.
Table 34 Keywords supported in the EmailKeywords property
Keyword
Description
TID
Trap ID
TDESC
Trap description
TSDESC
Short description about trap
TNAME
Trap name
TNOTENUM
Trap notice number
TRCVD
Trap received time
TADDR
Trap source address
TENTOID
Enterprise trap OID
TNOTSEV
Trap severity
TASSIGNTO
Trap assigned to
TCOMMENT
Trap comments
DNAME
Device name
DDISCOV
Device discovered time
DURL
Device URL
HDR
Header which can be used to format message
Related information
286 Operations
Configuring modem settings for paging on Windows systems
Perform the following procedure to specify the COM port used by the modem to send pager
messages.
NOTE:
You can configure modem settings only in Windows operating systems.
Procedure 160 Setting modem settings for paging
1.
2.
From the COM port field, select the appropriate COM port. See your modem documentation
for details.
Click OK to save the setting.
Related information
Clearing events
Procedure 161 Clearing events
1.
2.
3.
4.
Select Options→Events→Clear events. The Clear Events page appears.
Select the target events. See Creating a task for more information about selecting targets.
Click Apply.
Click Run Now to clear the events immediately and view the Task Results page, or click
Schedule to schedule the deletion. See Scheduling a task for more information about scheduling
the task to run.
Related information
Deleting events
Procedure 162 Deleting events
1.
2.
3.
4.
5.
Select Options→Events→Delete events. The Delete Events page appears.
Select the target events. See Creating a task for more information about selecting targets.
Click Apply.
(Optional) Click Modify Targets to add additional events to delete, or click Remove Targets
to remove events from the deletion process.
Click Run Now to delete the events immediately and view the Task Results page, or click
Schedule to schedule the deletion. See Scheduling a task for more information about scheduling
the task to run
Related information
Configuring event filters for registered SNMP traps
Related procedures
Creating an automatic event handling task
Copying automatic event handling tasks
Viewing task definitions for automatic event handling tasks
Viewing event task results
Deleting events
Configuring e-mail settings
Configuring modem settings for paging on Windows systems
Related topics
Managing event handling tasks
Managing SSH keys
Configuring modem settings for paging on Windows systems 287
Configuring SNMP traps
Procedure 163 Configuring SNMP Trap settings
1.
2.
3.
4.
5.
6.
7.
8.
Select the MIB name from the MIB Name dropdown list.
Select the trap name from the Trap Name dropdown list. The Event Type and Description
change according to the trap name selected.
Optional: Change the Event Type.
Optional: Edit the Description.
Select Yes or No in the Enable Trap Handling box.
Select the category from the Category dropdown list.
Select the severity from the Severity dropdown list. The available options are Informational,
Warning, Minor, Major, and Critical.
Click OK to save the settings.
SNMP trap fields
Field Names
Description
MIB Name
Select a MIB name from the dropdown list. All the
remaining fields change according to the MIB name
selected.
Trap Name
The default trap name is completed when a MIB name is
selected in the MIB Name field. However, you can modify
it by selecting a different trap name in the dropdown list.
Event Type
The type is a reflective form of the actual trap name.
Change the type if it does not adequately describe the
system for you.
Description
The description is vendor-supplied. Replace it with more
specific instructions, a precise reference source, or a
website referral.
Enable Trap Handling
Most traps are enabled. Trap handling gives you control
over the volume of messages. Turn off nuisance messages,
such as unnecessary informational messages, or repeated
trap messages for an event that has not been corrected.
Category
The category lists the HP SIM category types and Unknown.
Severity
Some vendors use the default Informational for all severity
levels. Change the severity to a level that reflects your
judgment of the problem. Alternatively, you can change a
Major or Critical severity for a trap message that is clearly
not a critical situation in your environment. Only you know
if this is the case. The only valid options for HP SIM are
Critical, Major, Minor, Warning, and Informational.
Modifying traps
To modify a specific trap, such as cpqIDELogicalDriveStatusChange, to have trap information
included in e-mail messages, you can edit the MIB cfg. You can add keywords to the
MSG_FORMATTER field, and then you must reregister the MIB, after making changes, by using
the mxmib -a cpqide.cfg command.
For example:
#MSG_FORMATTER "$V3V#Ide Controller Model: # $V4V#Controller Slot Number:
# $V5V#Controller Index: # $V6V#Ide Logical Drive Index: # $V7V#Logical
Drive Status: # $tid#Trap ID: # $tname#Trap Name: # $trcvd#Trap Received
Time: #
288 Operations
You can also edit the globalsettings.props file and modify the EmailKeywords property.
Configuring e-mail settings, in the "EmailSettings" section for additional information on changing
the EmailKeywords property.
For SNMP traps, the MIB cfg file is the default location that HP SIM looks for keywords. If keywords
are not defined here, then HP SIM looks at the EmailKeywords property in the
globalsettings.props file.
Related information
Configuring status change events
Perform the following procedure to configure the sending of status change events for systems when
hardware status changes to and from a Critical (unreachable) state only.
Procedure 164 Configuring status change events
1.
2.
Select one of the following options.
•
Enable creation of system status change events. This option sends a system unreachable
event whenever a system cannot be reached by a ping through the Hardware Status
Polling task. Enabling this option creates a system reachable event whenever the system
is reachable again.
•
Automatically clear unreachable system status change events when system is reachable.
If this option is enabled, when a system that was previously unreachable starts to respond,
the previous unreachable event is marked with a cleared state.
Click OK to apply changes.
Related information
Subscribing to WBEM indications
Procedure 165 Subscribing to WBEM indications
1.
2.
3.
4.
Select Options→Events→Subscribe to WBEM Events. The Step 1: Select Target Systems page
appears.
Select the target systems, and then click Apply. The Step 1: Verify Target Systems page appears.
Click Next. The Step 2: Task Confirmation page appears and provides details about the task
that was created.
Click Run Now to add subscriptions for WBEM events on the target systems. The Task Results
page appears.
Related information
Unsubscribing to WBEM indications
Procedure 166 Unsubscribing to WBEM indications
1.
2.
3.
4.
Select Options→Events→Unsubscribe to WBEM Events. The Step 1: Verify Target Systems page
lists all of the targets with subscriptions to WBEM indication events.
If you do not want to delete a target's WBEM indication events subscription, select the target
and click Remove Targets.
Click Next. The Step 2: Task Confirmation page appears and provides details about the task
that was created.
Click Run Now to remove subscriptions for WBEM indication events on the target systems.
The Task Results page appears.
Instead of clicking Run Now, you can click Schedule to schedule the task for a later time. See
Scheduling a task for more information.
Configuring status change events 289
NOTE: You can also list subscriptions and move subscriptions to a new destination through the
CLI using the mxwbemsub command. See the HP Systems Insight Manager Command Line Interface
Guide, at http://www.hp.com/go/insightmanagement/sim/docs, for more information.
Related information
Subscribing to health lifecycle events
HP SIM enables you to add and remove health lifecycle event subscriptions for HP NonStop Kernel
servers using the CLI. If you subscribe to health lifecycle events for an HP NonStop Kernel server,
when the server's status changes, notification is sent to HP SIM and the server status is updated
immediately in the GUI instead of waiting for the next status collection.
Procedure 167 Adding or removing health lifecycle event subscriptions
1.
2.
Sign into the CLI. See Signing in for instructions.
Enter one of the following commands:
•
To add a health lifecycle event subscription for one or more servers, enter:
mxwbemsub -a [destination] ( ( -n nodenames ) | ( -f filename ) )
health]
[-t
The target system (node) names can be entered through the command line or an input
file. Each system name, entered on the command line or in a file, can be the IP address,
hostname, or FQDN of the system. You can specify the destination CMS for the
subscriptions. If the destination is not included, the default is the CMS on which the
command is run.
•
To remove a health lifecycle event subscription for one or more servers, enter:
mxwbemsub -r [destination] ( ( -n nodenames ) | ( -f filename ) ) [-t
health]
The target system (node) names can be entered through the command line or an input
file. Each system name, entered on the command line or in a file, can be the IP address,
hostname, or FQDN of the system. This command can delete subscriptions from another
CMS. If a CMS is not specified, the default is to remove subscriptions from the CMS on
which the command is run.
NOTE: See the HP Systems Insight Manager Command Line Interface Guide, at http://
www.hp.com/go/insightmanagement/sim/docs, for detailed information about mxwbemsub.
Related information
Creating an automatic event handling task
Perform the following procedure to create a new automatic event handling task to define a response
to a specific event.
NOTE: If you create an automatic event handling task and you do not select a predefined
collection that has event and system information in it, and then you use the mxtask -lf command
to create an .XML file that can be used to create another task, the task and collection that are
associated with the task are placed in the .XML file. If you delete the task, the collection is deleted
along with the task. Therefore, the .XML file can no longer be used to create a new task with the
collection that is referenced in the .XML file. Any time you create an automatic event handling
task that includes selecting event information and then system information, that information is stored
in a hidden collection that is unavailable for use by any task other than the immediate task. For
more information, see the HP Systems Insight Manager Command Line Interface Guide, at http://
www.hp.com/go/insightmanagement/sim/docs.
290 Operations
Procedure 168 Creating new automatic event handling tasks
1.
2.
Enter a name in the Task name field, or accept the default, and then click Next. The Select
event collection page appears.
Select one of the following:
a. Use this event collection
i. Select an event collection from the dropdown list.
NOTE: Select an event collection. The event collection is defined by event attributes.
The event collection might be a combination collection containing system information.
If you select an event collection that contains additional event collections, an error
message appears.
ii.
Optional: Click View Definition to view the collection attributes that define the event
collection.
NOTE: The view definition field appears if you selected an existing private or
shared event collection. If the collection was created using the Automatic Event
Handling feature, the view definition does not appear.
iii. Click Next. The Select system collection page appears. If the event collection is a
combination collection, the select system collection process does not appear. Instead,
the Select actions page appears.
b.
Use event attributes that I will specify
i. Click Next. The Select events page appears.
ii. Select event search criteria for defining the task.
To add additional search criteria, click Add.
For more information about event searches, see Performing an advanced search for
events.
c.
3.
Click Next. The Select system collection page appears.
Select one of the following options:
•
Use this system collection
1. From the dropdown list, select a system collection.
2. Click View Definition to view the collection attributes or the members of the system
collection that is selected.
3. Click Next. The Select action page appears.
•
Use system attributes that I will specify
a. Click Next. The Select systems page appears.
b. Select system search criteria for defining the task:
◦
List criteria
◦
Comparison option
◦
Value for the criteria or comparison options selected
To add additional search criteria, click Add.
For more information about event searches, see Performing an advanced search for
events.
c.
4.
Click Next. The Select actions page appears.
Select from the following options:
•
Send page
Creating an automatic event handling task
291
1.
Add users to be paged from the dropdown list by clicking
. Click
to remove
selected users. The pager number for an HP SIM user is set on the Users and
Authorizations page. For more information, see Creating new users. If a user name
in the Users list is inactive, the pager information for the user has not been configured.
You can add the user to the list, but pager messages are not sent to this user until
the pager information is provided.
NOTE: If you select a user that does not have pager information set, the Pager
Information section expands where you can enter the information.
2.
Enter the paging information.
◦
Phone number
Enter the pager phone number of the user associated with this user account if
you are using a Windows operating system. If the Phone number field is left
blank, the paging information is not saved. This field does not apply to user
groups.
◦
PIN number
Enter the PIN number associated with the pager phone number.
◦
Message length
Select how many characters can be accepted in the paging message from the
dropdown list.
◦
Baud rate
Select the appropriate baud rate for the pager from the dropdown list.
◦
Data format
Select the appropriate data format for the pager from the dropdown list.
3.
•
292 Operations
Click Apply. A dialog box appears stating that the changes were successful. Click
OK to close the box.
Send e-mail
1. In the To field, enter the list of e-mail addresses that should receive the notification,
separating each entry with a comma.
2. In the CC field, enter any e-mail address that should receive a copy of the e-mail,
separating each entry with a comma.
3. In the Subject field, enter a note describing the subject of the e-mail.
4. In the Message Format field, select from the following formats based on the encoding
preference of the recipient:
◦
Standard. A default message format that sends a text e-mail message to the
recipients.
◦
Pager/SMS. An e-mail message format that sends a message to the recipients
with the same information and format as a pager message.
NOTE: Many cellular service providers offer SMS facility to their customers
via an email. For example, if your mobile phone number is 555-123-4567, an
email sent to 5551234567@yourserviceprovider.com is sent to your mobile
phone as an SMS page.
◦
5.
•
HTML. An e-mail message format that sends a message to the recipients that
looks like the HTML Event Details page.
In the Encoding field, select from the following formats:
◦
Western European (ISO-8859-1)
◦
Unicode (UTF-8)
◦
Japanese (ISO-2022-JP)
◦
Japanese (Shift_JIS)
◦
Japanese (EUC-JP)
◦
S-Chinese (GB18030)
◦
T-Chinese (Big5)
◦
Korean (EUC-KR)
Run custom tool
Select a custom tool from the Name dropdown list. Custom tools are created under the
Tools→Custom Tools→New Custom Tool option, and then select CMS tool. For more
information, see Creating a CMS tool.
•
Assign
Enter the name of the user to whom to assign the task. The event is assigned to this user
when received. Setting this field allows you to perform searches assigned to this person.
•
Forward as SNMPtrap
Enter a system name or IP address in the Name or IP field, and then click >> to add it to
the Trap recipients box.
Click Delete if you want to delete a recipient after selecting the name in the Trap recipients
box. Use the up and down arrows to scroll to the recipient to delete.
•
Write to system log
On Windows NT and Windows XP systems, the event details are written to the Application
Log, and the Source column of the Event Log is listed as HP SIM for the logged event. On
Linux and HP-UX systems, the event details are logged to the system log, which is usually
located in the file /var/log/messages on Linux and in /var/adm/syslog/
syslog.log on HP-UX.
•
Clear event
Received events are cleared based on the criteria selected when task executes.
5.
After you have made your selections, click Next. The Select time filter page appears.
Creating an automatic event handling task 293
6.
Select the Use time filter checkbox if you want to use time filters, and then select an option
from the dropdown list.
a. Click Manage Filters if you want to set user-defined filters. For more information, see
Applying a time filter.
b. Select the View time filter checkbox. A time filter window appears, showing the times
selected.
If the Use time filter checkbox is not selected, actions are triggered whenever the events
matching the selected criteria are received.
If the Use time filter checkbox is selected, actions are triggered only when they occur
during the days and times specified by the selected time filter.
c.
7.
When you have entered the information, click Next to continue with the next step. The
Review summary page appears. The task name, owner, time filters, event collections,
system collections, and actions information appears. If a paging or e-mail option was
selected, the modem and e-mail settings appear, along with buttons to change the settings.
Optional: Click Edit modem settings to edit the modem settings, or click Edit email Settings to
edit the SMTP settings. For more information, see Configuring modem settings for paging on
Windows systems or Configuring SNMP traps.
NOTE: The event and system search criteria appear at the bottom of the page. This
information can be extremely complex and long. Therefore, you might need to scroll down to
view all criteria.
8.
Click Finish to create the new task.
Related information
Related information
Related procedures
Creating an automatic event handling task
Copying automatic event handling tasks
Viewing task definitions for automatic event handling tasks
Viewing event task results
Deleting events
Configuring e-mail settings
Configuring modem settings for paging on Windows systems
Related topics
Managing event handling tasks
Managing SSH keys
Protocol settings
You can set default system-wide protocols settings. These defaults apply to all newly discovered
systems. For passwords or community strings, the default list is repeated until one string works (if
at all). HP recommends putting the most often used passwords or community strings first in the list.
In the following procedure, all sections are optional but highly recommended for proper management
of systems.
WARNING! If your environment's security policy includes account lockout after a specific number
of failed attempts, use system protocol settings instead of global protocol settings. You cannot
configure system protocol settings until discovery has been run once, making sure none of the
account lockout accounts are configured in the global protocol settings. For information on
configuring system protocol settings, see Setting protocols and credentials for a system or group
of systems.
294 Operations
Procedure 169 Setting global management protocol settings
IMPORTANT: Disabling protocols might adversely affect the operation of both HP SIM discovery
and plug-in applications.
1.
In the Ping settings section, choose from the following options:
•
HP recommends: Use the ICMP protocol for system reachability (ping) check. This setting
is the default.
•
Use the TCP protocol for system reachability (ping) check. TCP port number. Select this
setting if your company has disabled ICMP on the corporate network or if the corporate
policy mandates system firewall software to filter ICMP requests. Enter the port number.
Windows XP has this feature built in and can prevent systems from being automatically
discovered. This option enables you to run HP SIM and ping all available systems.
This option applies to only IP-based systems and is available for global, system-wide
settings that are used when managing all systems in HP SIM. It is used by automatic
discovery, hardware status polling, the ping tool, and any other tool that must verify
system availability. This option is not available on a single-system basis.
When HP SIM attempts a connection request to a system, that system does not need any
additional software running on it for this option to work. For example, HP does not require
that a web server be running on port 80. Some networking systems might not respond
to the TCP request, which is typically seen in low-end networking equipment. You can
make manual additions, if necessary. However, this system displays as Critical if hardware
status polling is run.
2.
3.
Set the Default timeout and the Default retries. If some systems are managed over a WAN or
satellite link, use a longer time-out (for example, five seconds) with at least one retry. For a
LAN, you can use a shorter time-out. You can configure this setting on a single-system basis.
See Setting protocols and credentials for a system or group of systems for more information
about setting single-system protocols.
In the WBEM settings section, verify that Enable WBEM (the default) is selected to allow WBEM
requests to be sent.
To access the Global Credentials page, if the WBEM credentials are the same as the Sign-in
credentials, select Go to the Global Credentials page to set global WBEM credentials.
OpenWBEM is not supported.
4.
5.
In the HTTP settings section, select Enable HTTP and HTTPS if you need web-based agents and
other HTTP port scans to be identified. HP recommends leaving this option enabled for proper
management and discovery of systems.
In the SNMP settings section, verify that Enable SNMP (the default) is selected and specify
values for Default time out and Default retries. For systems managed over a WAN or satellite
link, use a larger time-out (for example, five seconds) with at least one retry. For a LAN, a
shorter time-out can be used. You can configure these settings on a single-system basis.
To access the Global Credentials page, select Go to the Global Credentials page to set global
SNMP community strings.
6.
In the Read community string field, enter up to 10 read community strings. This value is
case-sensitive. The identification process attempts communication with a system, using each
of these communities in succession until a successful response is obtained. Future SNMP
requests then use the community string that provided a successful response.
If you have SNMP systems and no read community string that match the systems entered into
HP SIM through Global Protocol Settings or System Settings, the systems are not discovered.
7.
In the WS-MAN settings section, verify that WS-MAN is enabled and enter a Default identity
timeout.
Protocol settings 295
8.
9.
In the SSH settings section, select Enable SSH to enable SSH identification to run on managed
systems.
Click OK to accept the settings.
If you accessed this page from the Discovery page, click automatic discovery to return to the
Discovery page after making changes.
Setting protocols and credentials for a system or group of systems
Configure single-system protocol settings to fine-tune settings for individual systems or a group of
similar systems. This option is especially useful if some of your systems are accessed through a
LAN, while others are accessed through a WAN. Configure systems accessed through the WAN
with longer timeouts and increased retries.
If you selected a collection when first using this tool, you can click the collection link at the top of
the page. A window appears, showing all systems in the collection chosen. Click OK to close the
window. This link does not appear if you selected a single system.
NOTE:
Since the System Protocol Settings page is initially filled with default settings based on
the corresponding values from the Global Protocol Settings page. The initial settings might not
match current values from an individual system.
Procedure 170 Setting protocol settings for a single system or group of systems
1.
2.
3.
4.
Optional: To set system credentials, click System Credentials. The System Credentials page
appears.
In the Ping (ICMP) settings section, select Update values for this protocol to enable updating
the ICMP settings. If this is not selected, the settings are not updated. This option is disabled
by default. Select from the following:
•
Use global defaults.
•
Use values specified below. Enter the Timeout (seconds) and the Retries.
In the SNMP settings section, select Update values for this protocol to enable updating the
SNMP settings. If this is not selected, the settings are not updated. This option is disabled by
default. Select from the following:
•
Use global defaults.
•
Use values specified below. Enter the Timeout (seconds), Retries.
Click Previous to return to the previous screen without saving any changes, click Schedule to
schedule the task, or click Run Now to run the task immediately. See Scheduling a task for
more information about scheduling tasks.
NOTE: If the Schedule and Run Now buttons are disabled, look for bold red error messages
and correct all of the problematic entries, to enable these buttons.
Related procedures
Protocol settings
Setting protocols for a single system
Setting protocols for a single system
Configure single-system protocol settings to fine-tune settings for an individual system. This page
is accessed from the Tools & Links tab on the System Page.
Procedure 171 Setting protocol settings for a single system
1.
Go to System page→Tools and links, and then click System Protocol Settings. The System
Protocol Settings page appears.
296 Operations
2.
3.
4.
5.
In the Ping (ICMP) settings section, select Update values for this protocol to enable updating
the ICMP settings. If this is not selected, the settings are not updated. This option is disabled
by default. Select from the following:
•
Use global defaults.
•
Use values specified below. Enter the Timeout (seconds) and the Retries.
In the SNMP settings section, select Update values for this protocol to enable updating the
SNMP settings. If this is not selected, the settings are not updated. This option is disabled by
default. Select from the following:
•
Use global defaults.
•
Use values specified below. Enter the Timeout (seconds), Retries.
(Optional) To access the System Credentials page, select Go to the System Credentials page
to set system SNMP community strings.
Click OK to save the settings, or click Return to System Page to return to the System Page for
the system and not save changes.
NOTE: If the OK button is disabled, look for any bold red error messages and correct all
the problematic entries to enable that button.
Related procedures
Setting protocols and credentials for a system or group of systems
Protocol settings
Adding a WMI Mapper Proxy
HP SIM enables you to add a WMI Mapper Proxy to define a new proxy for HP SIM.
NOTE:
You must have administrative rights to add, edit, or delete a WMI Mapper proxy.
Procedure 172 Adding a WMI Mapper Proxy
1.
2.
3.
4.
Select Options→Protocol Settings→WMI Mapper Proxy→[New]. The Add WMI Mapper Proxy
section appears.
In the Host field, enter the full DNS name or IP address of the WMI Mapper Proxy.
In the Port number field, enter a port number. The WMI Mapper Proxy uses this port number
to communicate with the WMI client.
Click OK to save and close the Add WMI Mapper Proxy section, click Apply to save without
closing the Add WMI Mapper Proxy section, or click Cancel to abort the save operation.
Related procedures
Editing a WMI Mapper Proxy
Deleting a WMI Mapper Proxy
Deleting a WMI Mapper Proxy
HP SIM enables you to delete a WMI Mapper proxy. The delete option enables you to delete all
selected proxies. Delete is available only if one or more proxies are selected.
CAUTION: If you delete one or more WMI Mapper proxies, the deletion is permanent and the
proxies cannot be restored.
NOTE:
You must have administrative rights to add, modify, or delete the WMI Mapper Proxy.
Procedure 173 Deleting a WMI Mapper Proxy
1.
2.
Select Options→Protocol Settings→WMI Mapper Proxy.
Select the systems you want to delete.
Protocol settings 297
NOTE:
3.
4.
Sort by any column by clicking that column heading.
Click Delete. A message appears, asking you to confirm your intention to delete the WMI
Mapper Proxy.
Click OK to confirm your intention to delete the WMI Mapper Proxy, or click Cancel to cancel
the delete operation.
Related procedures
Adding a WMI Mapper Proxy
Editing a WMI Mapper Proxy
Editing a WMI Mapper Proxy
Edit a WMI Mapper proxy to update the proxy information. You can only edit one proxy at a time.
NOTE:
You must have administrative rights to add, modify, or delete the WMI Mapper Proxy.
Procedure 174 Editing a WMI Mapper Proxy
1.
2.
3.
4.
Select Options→Protocol Settings→WMI Mapper Proxy.
Select the proxy to edit, and then click Edit. The Edit WMI Mapper Proxy section appears.
In the Port number field, change the port number. The WMI Mapper Proxy uses this port
number to communicate with the WMI client.
Click OK to save, or click Cancel to abort the edit operation.
Related procedures
Adding a WMI Mapper Proxy
Deleting a WMI Mapper Proxy
Viewing and editing ESXi subcomponents
The WBEM Health Inclusion Status lists the status information for the subcomponents of an ESXi
system. HP SIM shows unused systems with a Major health status. To have HP SIM ignore these
systems when showing the health status of an ESXi system, use this page to ignore the components
that are not in use. This page shows the following information:
•
Component name
•
Description of the component
•
Propagation state
•
Health status
To include or ignore a component health status, complete the following:
1. To select components to include, select individual systems, and then click Include Status.
2. To select components to ignore, select individual systems, and then click Ignore Status. This
will exclude all selected components from being considered in calculations of the overall
system health status.
Software status polling
The following example describes how to set up a Software Version Status Polling Task that determines
whether managed systems have software that is out of date. This task uses the All Servers list as
the default list.
NOTE: One instance of this task is created by default when HP SIM is installed. It runs on a
weekly basis.
298 Operations
Procedure 175 Creating a software status polling task
1.
2.
3.
Select Options→Status Polling→Software Status Polling.
Select target systems from the All Systems collection. The default selected is All Systems. For
more information, see Creating a task for more information.
Click Schedule to schedule the task, or click Run Now to run the task immediately. For more
information about scheduling the task, see Scheduling a task.
Hardware status polling
HP SIM tracks system health status using a predefined hardware status polling task. This task polls
for updates on hardware status through the different protocols. The following example describes
how to set up a task to poll systems using hardware status polling.
NOTE: One instance of this task is created by default when HP SIM is installed. It runs when new
systems or events meet the search criteria.
Procedure 176 Creating a hardware status polling task
1.
2.
3.
4.
Select Options→Status Polling→Hardware Status Polling.
Select the target systems. For more information, see Creating a task.
Click Next. The Select Protocol Settings section appears.
Select from the following protocols:
•
HTTP
•
Ping
•
SNMP
•
WBEM
•
WS-MAN
NOTE: By default, all protocols are selected. If all protocols are clear, then the Schedule
and Run Now buttons are disabled. To limit polling to only determine whether a system is up
or down, you can select only Ping.
After all these conditions are met, the WBEM status is cleared.
5.
6.
7.
Select Timeout (in seconds):
•
Use default (currently "5")
•
Use custom. Timeout maximum is 120 seconds, with a minimum of one second.
Select the retry value:
•
Use default (currently "1")
•
Use custom. The retry maximum is 10 retries, with a minimum of 0 retries.
Select one of the following options to execute the task:
•
Schedule. Click Schedule to schedule when the task should run. For more information
about scheduling a task, see Creating a task.
•
Criticality. Select Critical (default) or Non-Critical.
Click OK.
•
Run Now. Click Run Now to run the task now. The Task Results Page appears. For more
information about the Task Results Page, see Task results list.
•
Previous. Click Previous to return to the previous page.
Related procedure
Hardware status polling 299
Software status polling
Data collection
Data collection performs system inventory data collection by gathering data that can be used for
reporting and to populate various fields in the user interface like the HP SIM System Page. Detailed
data can be collected to use for reporting or for comparing different systems with Snapshot
Comparisons, or less detailed data can be collected over time, which enables the use of Snapshot
Comparisons to view trends on a single system. To determine trends, HP SIM displays the difference
between the data available by the system at a specific time. For example, you want to determine
if a specific system was updated, or that certain components were removed. This can be determined
by running Data Collection task in HP SIM The report lists all details based on the data collected
at different times.
IMPORTANT: This should not be confused with HP Capacity Advisor data collection task. This
HP SIM menu item polls systems that are managed by HP SIM, to collect inventory data.
Procedure 177 Creating a data collection task
1.
2.
3.
4.
5.
Select Options→Data Collection. The Data Collection page appears.
Select target systems. See Creating a task for more information.
Click Next.
Specify how to save data by selecting:
•
Overwrite existing data set (for detailed analysis). Provides a network snapshot at a
certain time
•
Append new data set (for historical trend analysis). Provides trend and usage analysis
Select one of the following options to execute the task:
•
Click Schedule to schedule when the task should run. See Scheduling a task.
•
Click Run Now to run the task now. The Task Results Page appears.
•
Click Previous to return to the previous page.
View the task results by selecting the desired data collection task on the All Scheduled Tasks page.
Command line interface
Use the mxtask command to perform this task from the command line interface. For assistance
with this command, see the HP-UX or Linux manpage by entering mxtask at the command line or
the Windows command help.
For more information, see the Systems Insight Manager Command Line Guide.
Adobe Flash Detection
Adobe Flash Detection detects and reports Adobe Flash compatibility. Enables you to install a
required version of Adobe Flash player, upgrade to appropriate Adobe Flash version, or obtain
the latest version from the web.
System Properties
The Set System Properties tool enables administrative rights users to set system properties for a
single system or for multiple systems.
You have two options for setting system properties:
•
Edit system properties for a single system
•
Set system properties for multiple systems
300 Operations
The Suspend or Resume Monitoring tool enables you to suspend monitoring of a single system or
multiple systems, which enables systems to be excluded from status polling, identification, data
collection, and the automatic event handling features of HP SIM. The available suspend lengths
include the predetermined increments of 5 minutes, 15 minutes, 1 hour, 2 hours, 4 hours, 8 hours,
1 day, 2 days, 3 days, 4 days, 5 days, 6 days, and 7 days. You can turn on the suspend tool
indefinitely. Configuration changes take effect immediately. To view the new settings for a system,
click the System tab on the System Page. Changes made with this tool override previous settings.
A system that is suspended appears with a disabled icon throughout HP SIM.
You can suspend or resume monitoring for a single system or for multiply systems.
Editing system properties for a single system
The Edit System Properties link enables you to reconfigure system properties for a single system
from its System Page.
NOTE: You can change system properties for multiple systems if care is not taken. Read all
additional notes in this section to understand what precautions must be taken.
Procedure 178 Reconfiguring system properties for a single system from its System Page
1.
The information in the Identification section is obtained during discovery and identification.
Select from the following:
•
Preferred System Name
Specify how the system (including the CMS) appears in the HP SIM user interface. The
Restore Default Name button sets the displayed name back to the name originally
discovered by HP SIM.
To prevent discovery from overwriting the preferred system name, select Prevent the
Discovery, Identification and Data Collections processes from changing this system name.
NOTE:
If you change the preferred name, a warning message appears stating that
any lists referring to this system by name might no longer work, and any subsequent
discoveries of a system using the new name cause the system name change to be changed
back to the host (DNS) name.
•
Serial number
This is the serial number of the system. Any user-entered value is overwritten by
Identification, regardless of the checkbox setting described below. This field is read-only
if it is set by discovery. For Contract and Warranty data collection, if you want to override
the serial number obtained by discovery, enter a number in the Customer-Entered serial
number field.
•
Product number
This is the product number of the system and is retrieved through the Data Collection
process.
•
Primary IP
Select the Prevent the Discovery process from changing this IP address to prevent the
discovery process to change the IP address. However, if a new discovery discovers that
this IP address is reassigned to other system, discovery sets up a new primary IP address
and unlocks this flag. The list includes both IPv4 and IPv6 addresses.
If you do not want discovery to change the IP address for this system, check Prevent the
Discovery process from changing this IP address. However, if a new discovery finds this
IP address is reassigned to another system, discovery will set up a new primary IP address
and unlock this flag.
System Properties 301
2.
3.
4.
5.
In the Product Description section, select the properties you want to configure. The properties
include the following:
•
System type. This is the system type for the system, click the down arrow and select the
appropriate system type.
•
System subtype 1 - 8. This is the system subtype for the system, click the down arrow and
select the appropriate system subtype. You can provide up to eight different system
subtypes.
•
Product model. This is a free form field and you can enter the system model number here.
•
Hardware description. This is a free form field describing the hardware.
•
Operating system description. This is the name of operating system running on the system,
if any.
•
Operating system for tool filtering. This is the operating system for tool filtering, click the
down arrow and select the operating system.
•
Operating system version. This is a free form field and is the operating system version.
In the Contact information, enter the system contact and location information.
In the Asset Information section, enter the asset number of the system and is retrieved through
the Data Collection process.
In the Contract and Warranty Information section, under Entitlement Information, select the
properties you want to configure:
•
Customer-Entered serial number
This is the serial number of the system. Any user-entered value is overwritten by
Identification, regardless of the checkbox setting described below. This field is read-only
if it is set by discovery. For Contract and Warranty data collection, if you want to override
the serial number obtained by discovery, enter a number in the Customer-Entered serial
number field.
•
Customer-Entered product number
The user-entered product number of the system. Typically, the product number is the
number used to order a system. This number is usually in the format XXXXXX-XXX. HP SIM
tries obtain this number automatically.
•
System Country code
The International Organization for Standardization (ISO) code for your country. The
correct country code must be selected for proper reporting of contract and warranty data.
See http://www.iso.org//iso/en/prods-services/iso3166ma/ 02iso-3166-code-lists/
list-en1.html for the list of country codes.
•
Entitlement type
This option is required only if you have a service contract with HP. Choose from the
following:
302 Operations
◦
Customers with service contracts issued by Compaq before HP and Compaq merged
should select Compaq contract ID.
◦
Customers with service contracts issued by HP before HP and Compaq merged should
select System Handle.
◦
Customers recently issued a new service contract or migrated from an old pre-merger
company contract to a new HP contract should select SAID (Service Agreement ID).
◦
Customers who purchased an extended warranty at the time the device was purchased
must select HP Care pack Serial Number.
•
Entitlement ID
The ID of the contract, if you entered one. Depending on the selected contract type, the
following applies:
•
◦
For Compaq contract IDs, the contract identifier is on the contract itself.
◦
System Handles are on the contract. System Handles are case sensitive and generally
use uppercase letters.
◦
For SAIDs, the documentation provided with the contract explains where to find the
SAID. The SAID is a 12-digit number starting with 1. Although it might appear on
the contract as a sequence of three four-digit numbers, enter the number as a single
12 digit number without spaces.
◦
For the HP Care pack Serial Number, there is a separate support serial number that
is different than the serial number for the product itself. Enter the Carepack serial
number as the contract identifier.
Obligation ID
Platinum, Gold, or Silver pre-merger Compaq contracts provide a red access ID (also
called an obligation ID or software access number). Compaq Software Obligation IDs
were only issued in North America.
•
Custom Delivery ID
A free-form field to enter delivery ID information.
6.
In the System Site Information section, select the site information. To create, edit, or delete
site information, click Manage Sites. See Managing site information for more information.
NOTE: When you update the details for an existing company name, HP SIM automatically
updates the details for all systems with a matching company name. If you have multiple
addresses for a single company, use a unique company name for each one.
7.
The Customer Contact section includes information about the contact person responsible for
this system.
•
Primary customer contact
Click Manage Contacts to create, edit, or delete contact information. See Managing
contacts for more information.
•
Secondary customer contact
Select information from the menu.
•
Primary service contact
Select information from the menu.
8.
Click OK to save changes, or click Cancel to cancel changes.
Related information
System Properties 303
Entering new contact information
Procedure 179 Entering contact information
•
Enter the following information as needed.
Table 35 Contact information
Fields
Description
Salutation
The salutation of the contact person. Select from the
dropdown list.
Contact's first name
The first name of a contact that support can use to notify
at the customer site.
Contact's last name
The last name of a contact that support can use to notify
at the customer site. If you enter a first name, a last name
is required.
Contact job title
The contact person's job title. This is a free-form field.
Contact phone
The phone number of the contact person. Extension can
be included by entering ext. before the extension
number. For example, 555-123-4567 ext. 89.
Contact email
The contact person's e-mail address. This field is
alphanumeric and can contain only one e-mail address.
Contact language
The language to use for the contact person. This field is
alphanumeric and can contain only one e-mail address.
Hours of availability
The hours that the contact person is available. This field
is alphanumeric and can contain only one e-mail
address.
Contact other
This field is a free-form and can included information
such as availability of the contact person, language
preference, and so on.
NOTE: When you update the contact e-mail, phone number, or other information for an existing
contact, HP SIM automatically updates the details for all systems that use the same contact name.
Related information
304 Operations
Editing contact information
Procedure 180 Editing contact information
1.
Edit the following information as needed:
Table 36 Contact information
2.
Fields
Description
Salutation
The salutation of the contact person. Select from the
dropdown list.
Contact's first name
The first name of a contact that support can use to notify
at the customer site.
Contact's last name
The last name of a contact that support can use to notify
at the customer site. If you enter a first name, a last name
is required.
Contact job title
The contact person's job title. This is a free-form field.
Contact phone
The phone number of the contact person. Extension can
be included by entering ext. before the extension
number. For example, 555-123-4567 ext. 89.
Contact email
The contact person's e-mail address. This field is
alphanumeric and can contain only one e-mail address.
Contact language
The language to use for the contact person.
Hours of availability
The hours that the contact person is available.
Contact other
This field is a free-form and can included information
such as availability of the contact person, language
preference, and so on.
To save changes, click OK, or click Cancel to return to the Manage Contacts section without
saving changes.
Related information
Deleting contact information
Procedure 181 Deleting contact information
1.
2.
3.
4.
Go to Manage Contacts.
•
Click Manage Contacts from the Edit System Properties page. The Manage Contacts page
appears.
•
Select Options→System Properties→Manage Contacts.
Select the contacts to delete.
Click Delete. A confirmation box appears.
To delete the contact, click OK, or to cancel the deletion, click Cancel.
Entering new site information
The Edit System Properties link enables you to re-configure system properties for a single system
through its System Page which is made up of the following sections.
System Properties 305
Procedure 182 Entering site information
1.
2.
Fields
Description
Site Name
The company name that the system belongs to.
Address 1
The company address first line.
Address 2
The company address second line.
City
The name of the city that the system is located in.
State or province
The name of the state the system is located in. Select
state from the dropdown list.
Postal code
The city zip code. This can include the dash with
additional four digits.
Country or Region
The country or region name. Select a country or region
from the dropdown list.
Time zone
The time zone that the city is located in. Select the
appropriate time zone from the dropdown list.
After you have entered the text, click OK, Cancel, or Apply.
Related information
Editing site information
Procedure 183 Editing contact information
1.
Edit the following information as needed:
Table 37 Contact information
2.
Fields
Description
Salutation
The salutation of the contact person. Select from the
dropdown list.
Contact's first name
The first name of a contact that support can use to notify
at the customer site.
Contact's last name
The last name of a contact that support can use to notify
at the customer site. If you enter a first name, a last name
is required.
Contact job title
The contact person's job title. This is a free-form field.
Contact phone
The phone number of the contact person. Extension can
be included by entering ext. before the extension
number. For example, 555-123-4567 ext. 89.
Contact email
The contact person's e-mail address. This field is
alphanumeric and can contain only one e-mail address.
Contact language
The language to use for the contact person.
Hours of availability
The hours that the contact person is available.
Contact other
This field is a free-form and can included information
such as availability of the contact person, language
preference, and so on.
To save changes, click OK, or click Cancel to return to the Manage Contacts section without
saving changes.
Related information
306 Operations
Deleting site information
Procedure 184 Deleting site information
1.
Click Manage Sites from the Edit System Properties page. The Manage Sites page appears.
Alternately, select Options→System Properties→Manage Sites.
2.
3.
4.
Select the site names to delete.
Click Delete. A confirmation box appears.
To delete the site information, click OK, or to cancel the deletion, click Cancel.
Related information
Editing system properties for multiple systems
This tool enables you to edit system properties for multiple systems at one time. The Set System
Properties page for multiple systems is similar to the Edit System Properties page for a single system,
except that a checkbox appears next to each property. The checkboxes enable you to select the
properties you want to configure when the tool executes. Only the selected properties are saved
as a property for the target systems. If the value of the selected property is blank, that property is
not set for the systems All properties are optional.
NOTE: This tool can be used for a single system. However, some of the properties that are
available from the System Page are not available when selecting this option. For example, the
serial number is not available here, whereas it is available from the System Page.
Procedure 185 Editing system properties for multiple systems
1.
The information in the Identification section is obtained during discovery and identification.
Select from the following:
•
Restore the default system name
Select if you want to restore the default system name from identification.
•
Product number
This is the product number of the system and is retrieved through the Data Collection
process.
2.
In the Product Description section, select the System type from the dropdown list. This is the
system type for the system, click the down arrow and select the appropriate system type.
3. In the System Subtype section, select available subtypes to be added to the Selected subtypes
box.
4. Enter the Product model. This is a free form field and you can enter the system model number
here.
5. Enter the Hardware description. This is a free form field describing the hardware.
6. Enter the Operating system description. This is the name of operating system running on the
system, if any.
7. Enter the Operating system for tool filtering. This is the operating system for tool filtering, click
the down arrow and select the operating system.
8. Enter the Operating system version. This is a free form field and is the operating system version.
9. In the Contact information, enter the system contact and location information.
10. In the Entitlement Information section, enter the asset number.
11. In the System Property Lock section, select from:
•
Lock - Prevent the Discovery and Identification processes from changing the system
properties
•
Unlock - Allow the Discovery and Identification processes to change system properties
•
Ignore - Do not set the lock property of the target systems
System Properties 307
12. In the Contract and Warranty Information section, under Asset Information, select the properties
you want to configure:
•
Customer-Entered product number
The user-entered product number of the system. Typically, the product number is the
number used to order a system. This number is usually in the format XXXXXX-XXX. HP SIM
tries obtain this number automatically.
•
System Country code
The International Organization for Standardization (ISO) code for your country. The
correct country code must be selected for proper reporting of contract and warranty data.
See http://www.iso.org//iso/en/prods-services/iso3166ma/ 02iso-3166-code-lists/
list-en1.html for the list of country codes.
•
Entitlement type
This option is required only if you have a service contract with HP. Choose from the
following:
•
◦
Customers with service contracts issued by Compaq before HP and Compaq merged
should select Compaq contract ID.
◦
Customers with service contracts issued by HP before HP and Compaq merged should
select System Handle.
◦
Customers recently issued a new service contract or migrated from an old pre-merger
company contract to a new HP contract should select SAID (Service Agreement ID).
◦
Customers who purchased an extended warranty at the time the device was purchased
must select HP Care pack Serial Number.
Entitlement ID
The ID of the contract, if you entered one. Depending on the selected contract type, the
following applies:
•
◦
For Compaq contract IDs, the contract identifier is on the contract itself.
◦
System Handles are on the contract. System Handles are case sensitive and generally
use uppercase letters.
◦
For SAIDs, the documentation provided with the contract explains where to find the
SAID. The SAID is a 12-digit number starting with 1. Although it might appear on
the contract as a sequence of three four-digit numbers, enter the number as a single
12 digit number without spaces.
◦
For the HP Care pack Serial Number, there is a separate support serial number that
is different than the serial number for the product itself. Enter the Carepack serial
number as the contract identifier.
Obligation ID
Platinum, Gold, or Silver pre-merger Compaq contracts provide a red access ID (also
called an obligation ID or software access number). Compaq Software Obligation IDs
were only issued in North America.
•
Custom Delivery ID
A free-form field to enter delivery ID information.
13. In the System Site Information section, select the site information. To create, edit, or delete
site information, click Manage Sites. See Managing site information for more information.
308 Operations
NOTE: When you update the details for an existing company name, HP SIM automatically
updates the details for all systems with a matching company name. If you have multiple
addresses for a single company, use a unique company name for each one.
14. The Customer Contact section includes information about the contact person responsible for
this system.
•
Primary customer contact
Click Manage Contacts to create, edit, or delete contact information. See Managing
contacts for more information.
•
Secondary customer contact
Select information from the menu.
•
Primary service contact
Select information from the menu.
15. Click Previous to return to the previous section, click Schedule to schedule the task, or click
Run Now to run the task immediately. For more information on scheduling tasks, see Scheduling
a task.
Suspending or resuming system monitoring for a single system
The Suspend/Resume Monitoring link enables you to set the timer for suspending monitoring.
NOTE: To complete this procedure, you must be authorized to use the EDIT_SYSTEM_PROPERTIES
tool on the system you want to update.
Procedure 186 Suspending or resuming system monitoring on a single system
1.
Select one of the following options:
•
Enable monitoring of this system
Select this option if you no longer want the system to be suspended.
•
Suspend monitoring of this system for
Select this option if you want to suspend a system for a set amount of time. Set the time
by clicking the dropdown arrow and selecting an option.
•
Suspend monitoring of this system indefinitely
Select this option to suspend a system until it is set otherwise.
2.
3.
(Optional) Select Suspend monitoring of all associated VM Guest(s) of this VM Host. If this
option is enabled, status for all guest systems will be suspended.
Click OK to apply the changes or click Cancel to cancel changes. After clicking OK or Cancel
you are returned to the Tools & Links tab.
Related information
Suspending or resuming system monitoring for multiple systems
The Suspend or Resume Monitoring tool enables you to set the timer for suspending monitoring of
multiple systems.
System Properties 309
Procedure 187 Suspending or resuming monitoring for multiple systems
1.
Select one of the following options:
•
Enable monitoring of target systems
Select this option if you no longer want the target systems to be suspended.
•
Suspend monitoring of target systems for
Select this option if you want to suspend target systems for a set amount of time. Set the
time by clicking the dropdown arrow and selecting an option.
•
Suspend monitoring of target systems indefinitely
Select this option to suspend target systems until it is set otherwise.
2.
Click Previous to select different target systems, click Schedule to schedule the task, or click
Run Now to run the task immediately.
Related information
Related procedures
Editing system properties for a single system
Entering new contact information
Editing contact information
Deleting contact information
Editing site information
Deleting site information
Suspending or resuming system monitoring for a single system
Editing system properties for multiple systems
Suspending or resuming system monitoring for multiple systems
Related topics
System page
Essentials tab
System tab for blade servers
System tab for clusters
System tab for a complex
System tab for management processors
System tab for partitions
System tab for servers
System tab for a storage array
System tab for storage host
System tab for a storage switch
System tab for a tape library
Tools & Links tab
Performance tab for blades
Port mapping tab for blades
Port types
Configuring WBEM health inclusion status
On the System Page of an ESXi system, the Tools and Links tab will populate the WBEM Health
Inclusion Status link. This link takes you to the WBEM Health Inclusion Status page, lists the status
information for the subcomponents of an ESXi system. HP SIM shows unused systems with a Major
health status. To have HP SIM ignore these systems when showing the health status of an ESXi
310
Operations
system, use this page to ignore the components that are not in use. This page shows the following
information:
•
Component name
•
Description of the component
•
Propagation state
•
Health status
To include or ignore a component health status, complete the following:
1. To select components to include, select individual systems, and then click Include Status.
2. To select components to ignore, select individual systems, and then click Ignore Status. This
will exclude all selected components from being considered in calculations of the overall
system health status.
This feature is useful to disable disconnected NICs from reporting an error status (Major/Minor)
on the ESXi overall status.
After setting the ‘Include Status’ or ‘Ignore Status’ on the components, the change will not be
reflected until the Next scheduled Status Polling task runs. You can or manually run the Hardware
Status Polling to reflect these statuses immediately.
Specifying a Version Control Repository
HP SIM enables you to specify an HP Version Control Repository Manager. The HP VCRM stores
the latest ProLiant Support Packs providing the latest software. The HP VCRM selected, determines
which SPPs appear in the list for baseline tools.
Procedure 188 Specifying a Version Control Repository
1.
2.
Select Options→Software/Firmware→Version Control Repository. The Version Control
Repository page appears.
Under Select the system to use as the default Version Control Repository, select a system that
has the HP VCRM installed.
NOTE: A trust relationship must be established between HP SIM and the system that has the
HP VCRM installed. See Trusted certificates for more information regarding trust relationships.
After the trust relationship is established, click Last Update to update the Trusted? column to
Yes.
3.
Under Contents of selected version control repository, click the
the contents of the selected Version Control Repository.
NOTE:
To expand the tree to display all contents, click the
icon to drill down and view
icon, located in the upper-left
corner of the Contents of selected version control repository section. Click the
collapse the listings.
NOTE:
icon to
Click any column heading to sort by that column in ascending or descending order.
NOTE: This section displays systems that are authorized by the current user. If the current
user is not authorized to view any systems with the HP Version Control Repository Manager,
the system will not be listed in the Select the default Version Control Repository section. If there
are no discoveredsystems running the HP VCRM, a message appears, indicating that no
repository could be found.
4.
Click OK to apply your selection. A message appears, indicating if the repository setting was
successfully saved.
Specifying a Version Control Repository
311
Configuring software/firmware global settings
Run the following procedure to configure component and version matching options. These settings
determine how the software/firmware status icon values are determined.
Procedure 189 Configuring software/firmware global settings
1.
2.
3.
Under Version Matching, select one of the following:
•
Installed versions of software or firmware that are more recent than the baseline version
will appear as Normal status
•
The installed software or firmware must exactly match the version in the baseline
Under Component Matching, select one of the following:
•
Only software or firmware installed on the system will be used when comparing against
the selected baseline
•
All software or firmware in the baseline must be installed on the system
Click Done to save changes.
Reporting
The HP SIM Reporting feature enables you to generate reports, create customer-defined report
configurations, edit, copy, and delete report configurations. All users with sign-in access to HP SIM
can generate reports.
Table 38 Reporting menu items
Name
New...
Manage Reports Manage Reports
options
Description
Access
The create new report wizard helps
you to create a new report and add
it to Systems Insight Manager reports.
This option is only available for
Systems Insight Manager.
Select Reports→New.... The New
ReportStep 1: Select Target Systems
page appears.
• Running managed reports
Select Reports→Manage Reports.... The
Manage Reports page appears.
Copying managed reports
See New reports.
• Creating new reports
• Editing managed reports
• Deleting managed reports
Snapshot Comparison...
Snapshot comparisons enable you to Select Reports→Snapshot
compare up to four systems (with the Comparison....
same operating system) to each other See Snapshot comparison reporting.
or to compare a single system to itself
and observe changes over time.
Enhanced Reports Table 40 (page
313).
• Predefined Reports
• Creating New Reports from the
Enhanced Reports Page
Select Reports→Enhanced Reports....
The Enhanced Reports, Reports by
Product page appears.
• Editing Reports
• Running Reports
• Email Reports
• Deleting Reports
Federated Search...
312
Operations
Federated CMS Search is a
web-based HP SIM plug-in that allows
you to search quickly across a number
of Systems Insight Manager CMS
systems.
Select Reports→Federated Search....
The Federated CMS Search page
appears.
See Federated CMS Search Tool.
Table 39 Manage Reports options
Name
Description
Access
Running managed reports
A generated report provides you with
the report name, associated system
collection, and report run date and
time in the following formats.
Select Reports→Manage Reports.... The
Manage Reports, Reports by Product
page appears. Select the report that
you want to run. Select the HTML, XML,
• HTML (Recommended for viewing) or CSV report format. Click Run Report.
See “Running managed reports” (page
• XML
315)
• CSV
Copying managed reports
Enables copying report configurations Select Reports→Manage Reports.... The
from an existing report configuration. Manage Reports page appears. Select
the report you want to copy and then
click Copy....
See “Copying managed reports” (page
316)
Creating new reports
Enables creating a new report and
add it to HP SIM reports.
Select Reports→Manage Reports... The
Manage Reports, Reports by Product
page appears. Click New....
Editing managed reports
Enables you to edit existing report
configurations.
Select Reports→Manage Reports... The
Manage Reports, Reports by Product
page appears. Click Edit....
Deleting managed reports
Enables you to delete existing report
configurations from the Manage
Reports page.
Select Reports→Manage Reports... The
Manage Reports, Reports by Product
page appears. Click Delete.
See “Deleting managed reports” (page
317)
Table 40 Enhanced Reports options
Name
Predefined Reports
Description
Predefined Reports are shipped with
Systems Insight Manager.
Access
Select Reports→Enhanced Reports....
The Enhanced Reports, Reports by
Product page appears.
See Running predefined reports .
Creating New Reports from the
Enhanced Reports Page
The create new report wizard helps
you to create a new report and add
it to Systems Insight Manager reports.
This option is only available for
Systems Insight Manager.
Select Reports→Enhanced Reports....
The Enhanced Reports, Reports by
Product page appears. Click New....
The New ReportStep 1: Select Target
Systems page appears.
See Adding a report.
Editing Reports
Enables editing of user defined
reports.
Select Reports→Enhanced Reports....
The Enhanced Reports, Reports by
Product page appears. Select the report
that you want to edit, and then click
Edit.... The Add details to report: Step
3: Specify Parameters page appears.
See Editing a report.
Running Reports
Executes a report present in the
reporting engine.
Select Reports→Enhanced Reports....
The Enhanced Reports page appears.
Select the report that you want to run.
Click Run Report.
See Running a report.
Reporting
313
Table 40 Enhanced Reports options (continued)
Name
Email Reports
Description
Enables a report to be run at a later
specified time.
Access
Select Reports→Enhanced Reports....
The Enhanced Reports, Reports by
Product page appears. Select the report
that you want to schedule, and then
click Email Report....
See Emailing reports.
Deleting Reports
Enables a user defined report to be
deleted.
Select Reports→Enhanced Reports. The
Enhanced Reports, Reports by Product
page appears.
See Deleting a report.
Related information
New reports
Procedure 190 Creating a new report
1.
2.
From the HP SIM menu, select Reports and then, click New Report.... The New ReportStep 1:
Select Target Systems page appears.
Select the desired Target Systems. For more information, see Creating a task
The Step 1: Verify Target Systems page appears.
3.
If you want additional targets, click Add Targets....
If a device is not needed, select the targeted device, and then click Remove Target.
Click Next to verify the selected targets.
The Step 2: Specify Parameters page appears.
4.
In the Report Name: field, enter a name for the report.
NOTE: Report names cannot contain any of the following characters: < > ' & \ ` , # + | %
; / \\ ! ~ @ $ ^ * = { } [ ] " : and ?
5.
In the Select items to show in report: section, select all categories or items to include in the
report. You can click the
6.
icon to expand a category, and then select specific items or click
the
icon to collapse a category.
Under Layout for generated or saved report:, chose either of the following options.
•
Show all systems in the same table.
This option displays all categories and items selected in the Select items to show in report
section. The selected categories appear as tables, and the selected data items appear
as column headers in the report. All systems appear in the same table.
•
Show each system in a separate table.
This option displays all categories and items selected in the Select items to show in report
section. The selected categories appear as tables, and all the selected data items appear
as column headers. Each system appears in an individual table.
7.
8.
314
Under Format for generated report, select from the following options:
•
HTML (Recommended for viewing)
•
XML
•
CSV
To save the report configuration, click Save Report.
Operations
9.
Click Run Report.
The new report appears.
Selecting the sort order
The Reporting feature enables you to sort the data when it displays on the Report Results page.
•
Ascending Order.
Click the column heading you want to sort by once. The data requeries in ascending
alphabetical order.
•
Descending Order.
Click the column heading you want to sort by twice. The data requeries in descending
alphabetical order.
Printing the report
On the Report Results page, select File→[Print] from your browser.
Related information
Running managed reports
Select Reports→Manage Reports.... The Manage Reports, Reports by Product page appears. Select
the report that you want to run. Select the report format. Click Run Report.
You can run reports in the following formats:
•
HTML (Recommended for viewing)
•
XML
•
CSV
The default sort order is based on the system name.
You can click any column heading to sort in ascending or descending order.
You can also access the Manage Reports page from the Manage section of the HP SIM Home page
by clicking the Manage inventory reports link.
Running an existing report in HTML format
Procedure 191 Running a report in HTML format
1.
2.
3.
4.
Select Reports→Manage Reports.
Select the report you want to view.
Under Format for generated report, select HTML (Recommended for viewing).
Click Run Report. The report appears.
The HTML report enables you to Show SQL queries.
Viewing an existing report in XML format
Procedure 192 Running a report in XML format
1.
2.
3.
4.
Select Reports→Manage Reports.
Select the report you want to view.
Under Format for generated report, select XML.
Click Run Report. The XML report appears.
Viewing an existing report in CSV format
Procedure 193 Running a report in CSV format
1.
Select Reports→Manage Reports.
Reporting
315
2.
3.
4.
Under Report Name, select the report you want to view.
Under Format for generated report, select CSV.
Click Run Report. If the browser system has no application associated with .CSV files, then
the .CSV file appears in the browser window. If you have an application associated with
.CSV files, then the .CSV file appears in the specified application.
If you are using Internet Explorer and an application such as Excel is installed on the browser
system and the .CSV file extension is associated with that application, the Save As dialog
box appears. Click Save.
5.
Name the file, and in the Save as type field, select a format in which to save the file from the
dropdown list. Click Save. The report is saved.
Selecting the sort order
The Reporting feature enables you to sort the data after it appears in the Report Results page.
•
Ascending Order.
Click the column heading you want to sort by once. The data queries in ascending alphabetical
order.
•
Descending Order.
Click the column heading you want to sort by twice. The data queries in descending
alphabetical order.
Printing an existing report
From the Report Results page, select File→[Print] from your browser.
Related information
Copying managed reports
Procedure 194 Copying a report configuration
1.
2.
3.
Select Reports→Manage Reports. The Manage Reports window appears.
Select the report to copy, and then click Copy. The Copy report section appears.
In the Report Name field, enter a name for the new report configuration.
NOTE: Report names cannot contain any of the following characters: < > ' & \ ` , # + | %
; / \\ ! ~ @ $ ^ * = { } [ ] " : and ?
4.
Click OK.
The Copy report section closes, and the copied report configuration appears in the Manage
Reports section.
Related information
Editing managed reports
Procedure 195 Editing an existing report
1.
2.
3.
Select Reports→Manage Reports. The Manage Reports window appears.
Select the report to edit, and then click Edit. The Edit Report page displays.
Select the desired Target Systems. For more information, see Creating a task
The Step 1: Verify Target Systems page appears.
4.
If you want additional targets, click Add Targets....
If a device is not needed, select the targeted device, and then click Remove Target.
Click Next to verify the selected targets.
316
Operations
The Step 2: Specify Parameters page appears.
5.
In the Select items to show in report: section, select all categories or items to include in the
report. You can click the
6.
icon to expand a category, and then select specific items or click
the
icon to collapse a category.
Under Layout for generated or saved report: chose either of the following options.
•
Show all systems in the same table.
This option displays all categories and items selected in the Select items to show in report
section. The selected categories appear as tables, and the selected data items appear
as column headers in the report. All systems appear in the same table.
•
Show each system in a separate table.
This option displays all categories and items selected in the Select items to show in report
section. The selected categories appear as tables, and all the selected data items appear
as column headers. Each system appears in an individual table.
7.
8.
Under Format for current run of generated report (format not saved with report), select from
the following options:
•
HTML (Recommended for viewing)
•
XML
•
CSV
To save over the existing report configuration, click Save Report.
Note: To save an existing report as a report with a new name, enter a new report name in
the Report Name field, and then click Save Report. The new report is saved and added to the
report list on the Manage Reports page.
A dialog box appears, asking you to confirm your intention to save the report. Click OK to
save, or click Cancel to abort. If the report already exists, the overwrite report message
appears. Click Cancel if you do not want to overwrite the existing report.
9.
To view the report, click Run Report. You can click Previous to return to the target selection
page. You can click Cancel to abort the report creation process.
Related information
Deleting managed reports
Procedure 196 Deleting a report configuration
1.
2.
3.
4.
Select Reports→Manage Reports. The Manage Reports page appears.
Select the report configuration to be deleted.
Click Delete. A dialog box displays asking you to confirm your intention to delete the selected
report.
Click OK to permanently delete the report configuration. You can click Cancel to abort the
delete operation.
Related information
Running predefined reports
NOTE: Crystal Reports does not support Adobe Flash Player version 11. HP recommends you
use the supported flash version on the browsing machine to avoid issues. You can obtain the
supported version from the HP SIM installation by accessing:
https://<CMS_IP_ADDRESS>:50000/flash_install/flashInstall.jsp.
Reporting
317
Procedure 197 Running predefined reports
1.
Select Reports→Enhanced Reports.... The Enhanced Reports, Reports by Product page appears.
2.
Click the
to expand a product group to reveal available reports. Available reports appear
below the selected product group.
Select an available report to run.
Select a format for the generated report from Format for generated report:
3.
4.
5.
•
HTML (Recommended for viewing)
•
CSV
•
PDF
Click Run Report.
The Select Parameters page appears.
6.
Depending on the report selected, you might have to choose parameters before the report
displays. Some possible parameters are:
•
Date range
•
Group type
•
System type
•
Operating systems
1
7.
Parameters selections.
Click the left arrow to
expand the window
and display the
parameter options.
2
Selection buttons. The
three selection options
from the left:
•
Select all values
•
Select no values
•
Search the list of
values
3
Value pane. Displays
the available
parameters for the
current report.
Click OK to display the report. Click Reset to reset all parameters and make new selections.
HP SIM SmartMemory support is available for Gen8 systems with their DIMM updated SmartMemory
and below are additional attributes added in HP SIM Enhanced Reports to support SmartMemory:
•
SmartMemory
Indicates DIMM is updated with SmartMemory (DIMMS with Smart Memmory or DIMMS
without SmartMemory)
•
Maximum Frequency
Maximum frequency
318
Operations
•
Minimum Voltage
Minimum voltage needed to operate
•
Ranges
•
Memory Status
Good memory and not good memory (missing, not present, degraded, and so on)
•
Technology
Additional enumerated technology fields
1
Export icon. Exports the
current report in the
following formats:
•
Crystal Reports (RPT)
•
PDF
•
Microsoft Excel
(97-2003)
•
Microsoft Excel
(97-2003) Data-Only
•
Microsoft Excel
(97-2003) - Editable
•
2
3
Rich Text Format (RTF)
4
5
6
Group Tree. Displays/hides
a list of items that the report
is grouped by. You can
select an item from the
Group Tree and the selected
item is displayed in the
Report Viewer.
Page Selection. Go to page.
You can use the arrows on
either side of the text box to
move from one page to
another.
Zoom tool. Click here to
access Zoom options.
7
8
Search. Search for text within
the current report.
Main Report pane. Displays
available information of either
the parameters or the group
tree from the current report
depending on which option
is selected at the time. If you
choose to edit the parameter
list, you must then click Apply
in the Main Report pane for
the changes to display in the
current report.
•
Separated Values (CSV)
Print icon. Prints the current
report. The viewer must
export to PDF to print.
Choose the Print option from
the PDF reader application
once the document is
opened.
Parameters. Displays/hides
the available parameters for
the current report in the Main
Report panel. The available
parameters can then be
Reporting
319
selected and edited as
desired.
Related information
Adding a report
Creating a report
Creating a new report
Procedure 198 Creating a new report
1.
2.
From the HP SIM menu, select Reports→Enhanced reports and then, click New.... The New
Report Step 1: Select Target Systems page appears.
Select the desired Target Systems. For more information, see Creating a task
The Step 1: Verify Target Systems page appears.
3.
If you want additional targets, click Add Targets....
If a device is not needed, select the targeted device, and then click Remove Target.
Click Next to verify the selected targets.
The Step 2: Add Report Details page appears.
4.
In the Report Name: field, enter a name for the report.
NOTE: Report names cannot contain any of the following characters: < > ' & \ ` , # + | %
; / \\ ! ~ @ $ ^ * = { } [ ] " : and ?
5.
6.
7.
In the Report Description: field, enter a description of the report.
Beside Report Based on: select the information the report is to be based on from the following
list:
•
Events
•
Operating System Information
•
Processor
•
HP BladeSystem Rack
•
System License Information
Select the following options in any combination:
•
Include Chart. See “Chart report” (page 321).
Bar, Line (Trend), Pie
•
Include Table. See “Table report” (page 320).
Table report
The Step 3: Specify Parameters page appears.
Procedure 199 Adding Report Details for a Table report
1.
In the Report Name: field, enter a name for the report.
NOTE: Report names cannot contain any of the following characters: < > ' & \ ` , # + | %
; / \\ ! ~ @ $ ^ * = { } [ ] " : and ?
2.
In the Report Description: field, enter a description of the report.
320 Operations
3.
4.
5.
6.
7.
Select a format for the generated report from Format for generated report:
•
HTML (Recommended for viewing)
•
CSV
•
PDF
In the Select items to show in report section, select all categories or individual items to include
in the report. You can click the
icon to move items from Available Data: to Selected Data:.
Click the Next arrow to display the next page of the report.
To save the report configuration, click Save Report. If the report exists, the overwrite report
message appears. Click Cancel if you do not want to overwrite the existing report.
Click Run Report.
The new report appears in the Report Results page.
To print the report, see “Printing the report” (page 315).
Chart report
The Step 3: Specify Parameters page appears.
Reporting
321
Procedure 200 Adding Report Details for a Graphical report
322 Operations
1.
Select type of graph from the list:
NOTE: The Include Chart section dynamically changes to display the selection items that are
required to create the corresponding report.
•
Bar. .
•
Line (Trend). .
•
Pie. .
Procedure 201 Bar Graph
1.
Select an option to be used to create each bar of the Bar Chart.
Reporting 323
1
2.
324 Operations
Select options
to be used for
each bar of the
bar chart.
See Additional Details.
2
Additional
Details area
dynamically
changes
according to
the type chart
selected. This
information is
populated
depending on
selected
options. Any of
these fields can
be edited.
3
Chart Previewer
displays a
preview of the
selected options
in chart form.
Procedure 202 Line Graph
1.
Select options to be used to create the Line Chart.
1
Select options
to be used for
each line of the
line chart.
1
Chart Previewer
displays a
preview of the
selected options
in chart form.
2
Additional
Details
dynamically
changes
according to
the type chart
selected. This
information is
populated
depending on
selected
options. Any of
these fields can
be edited.
Reporting 325
2.
See Additional Details.
Procedure 203 Pie Graph
1.
Select options to be used to create the Pie Chart.
1
2.
Select options
to be used in
the pie chart.
2
Additional
Details
dynamically
changes
according to
the type chart
selected. This
information is
populated
depending on
selected
options. Any of
these fields can
be edited.
3
Chart Previewer
displays a
preview of the
selected options
in chart form.
See Additional Details.
2.
Under Additional details: complete the following:
a. In the Graph Title: field, enter the title for the graph, prompted for all chart types. Report
names cannot contain any of the following characters: < >' & \ ` , # + | % ; / \\ ! ~ @
$ ^ * = { } [ ] " : and ?
b. In the Footer: field, enter a footnote, prompted for all chart types.
c. In the Series Label (X axis): field, enter a label for the X axis, prompted for Bar and Line
chart types.
d. In the Series Label (Y axis): field, enter a label for the Y axis, prompted for Bar and Line
chart types.
3.
To save the report configuration, click Save Report. If the report exists, the overwrite report
message appears. Click Cancel if you do not want to overwrite the existing report.
326 Operations
4.
Click Run Report.
The new report appears in the Report Results page.
Printing the report
On the Report Results page, select File→[Print] from your browser.
Related information
Editing a report
Editing a report is allowed on the following items:
•
Report Name
•
Report Description
•
Chart Type under Include Chart Section
•
Selection parameters under Include Chart Section
•
Additional details under Include Chart Section
•
Include Table section
Procedure 204 Editing a selected report
1.
2.
Select Reports→Enhanced Reports.... The Enhanced Reports, Reports by Product page appears.
Select the report to edit, and then click Edit. The Step 2: Add Report Details page appears.
The details from the opened report are pre populated in the text fields.
NOTE:
3.
Only custom reports can be edited, default predefined reports cannot be edited.
Change any of the following fields:
•
Report Name
•
Report Description
•
Report Based on
•
Selection parameters
For more information, see Table report.
For a chart report, edits can be made to the following additional items:
•
Graph Title
•
Footer
•
X axis (Label)
•
Y axis (Label)
For more information, see Chart report
4.
To save over the existing report configuration, click Save Report.
NOTE: To save an existing report as a report with a new name, enter a new report name
in the Report Name field, and then click Save Report. The new report is saved and added to
the report list on the Enhanced Reports page.
A dialog box appears, asking you to confirm your intention to save the report. Click OK to
save, or click Cancel to abort.
5.
To view the report, click Run Report. Click Previous to return to the target selection page. Click
Cancel to abort the report creation process.
Related information
Reporting 327
Deleting a report
Procedure 205 Deleting a selected report
1.
2.
3.
4.
Select Reports→Enhanced Reports.... The Enhanced Reports, Reports by Product page appears.
Select the customized report configuration to be deleted.
Click Delete. A dialog box displays asking you to confirm your intention to delete the selected
report.
Click OK to permanently delete the report configuration. Click Cancel to abort the delete
operation.
A dialog box displays confirming that the report has been successfully deleted.
Related information
Running a report
A generated report provides the following information:
•
Report name
•
Associated system collection
NOTE: The Associated system collection information does not appear if there is no collection
selected to run the report.
•
Report run date and time
Reports can be run in the following formats:
•
HTML (Recommended for viewing)
•
PDF
•
CSV
The default sort order is based on the system name.
Click any column heading to sort in ascending or descending order.
The Manage Reports page can be accessed from the Manage section of the HP SIM Home page
by clicking the Manage inventory reports link.
Running an existing report in HTML format
Procedure 206 Report in HTML format
1.
2.
3.
4.
Select Reports→Enhanced Reports....
Select the report you want to view.
Under Format for generated report, select HTML (Recommended for viewing).
Click Run Report. The report appears in the Report Result page.
Viewing an existing report in PDF format
Procedure 207 Report in PDF format
1.
2.
3.
4.
Select Reports→Enhanced Reports....
Select the report you want to view.
Under Format for generated report, select PDF.
Click Run Report. The PDF report appears.
Viewing an existing report in CSV format
Procedure 208 Report in CSV format
1.
Select Reports→Enhanced Reports....
328 Operations
2.
3.
4.
Under Report Name, select the report you want to view.
Under Format for generated report, select CSV.
Click Run Report. If the browser system has no application associated with .CSV files, then
the .CSV file appears in the browser window. If you have an application associated with
.CSV files, then the .CSV file appears in the specified application.
If you are using Internet Explorer and an application such as Excel is installed on the browser
system and the .CSV file extension is associated with that application, the Save As dialog
box appears. Click Save.
5.
Name the file, and in the Save as type field, select a format in which to save the file from the
dropdown list. Click Save. The report is saved.
Printing an existing report
From the Report Results page, select File→Print from your browser.
Related information
Emailing reports
Procedure 209 Scheduling a selected report
1.
2.
3.
4.
Select Reports→Enhanced Reports.... The Enhanced Reports, Reports by Product page appears.
Select the report configuration to be emailed.
Click Email Report.... The Email Report page appears.
Under Send e-mail, enter the e-mail address of the person to be notified of the scheduled
report in the To: field.
NOTE:
Required field, information must be entered.
NOTE: If valid input is not supplied, an alert appears requesting valid input when Schedule
is selected.
5.
6.
In the CC: field, enter the e-mail addresses of any persons to be sent a courtesy copy of the
scheduled report.
In the Subject: field, enter the subject of the scheduled report.
Required field, information must be entered.
NOTE: If valid input is not supplied, an alert appears requesting valid input when Schedule
is selected.
7.
Click Previous to return to the Enhanced Report page.
Click Run Now to execute the selected report.
Click Schedule. The Step 3: Schedule Task page appears.
If the SMTP (Simple Mail Transfer Protocol) server settings are not present in the HP SIM, then
a message is displayed below the Email Report section informing you what needs to be done.
You must follow the steps provided under the note section to apply the valid settings otherwise
you will not get any email notifications.
8.
9.
In the Task name: field, enter a name for the task.
Under When would you like this task to run?, select one of the following options:
•
Periodically. See “Periodically” (page 330).
•
Once. See “Once” (page 330).
•
Not scheduled. Select this option if you do not want to schedule the task at this time.
Reporting 329
Periodically
Procedure 210 Scheduling a task periodically
1.
(Optional) Under In addition:, select from the following:
•
Select Run when the central management server is started if you want the task to run
when the central management server is started.
•
To run the task immediately, select Run now.
•
Select Disable this task if you want to disable this task at any time.
2.
Refine schedule:
3.
4 Enter the time of day
Enter an increment of
how often to run the
to run the report in the
report in the Every text
at text field and select
field.
AM or PM from the
2 Select day(s), week(s),
dropdown list.
5 Optional. Select Run
month(s), or year(s),
from the dropdown
until and enter the
list.
date to stop running
3 Select the day of the
the report in the text
week to run the report
field.
from the on dropdown
list.
Click Done to save the scheduled report.
1
6
7
Enter the time of day to
stop running the report
in the at text field and
select AM or PM from
the dropdown list.
Optional.. Select Run a
maximum of and enter
the maximum number
of times to run the
report in the times(s)
text box.
Click Previous to return to the Step 2: Schedule Report page.
Once
Procedure 211 Scheduling a task once
1.
2.
(Optional) Under In addition:, select from the following:
•
Select Run when the central management server is started if you want the task to run
when the central management server is started.
•
To run the task immediately, select Run now.
•
Select Disable this task if you want to disable this task at any time.
Refine schedule:
330 Operations
Enter the time of day
to start running the
report in the at text
field and select AM or
PM from the
dropdown list.
Click Done to save the scheduled report.
1
3.
Enter a date you want
to run the report in the
On text field.
2
Click Previous to return to the Step 2: Schedule Report page.
Insight Control reports
When HP Insight Control is installed, eleven predefined Insight Control reports are added to the
existing collection as Insight Control reports.
Reporting
331
NOTE:
If links are not visible for some or all Enhanced Reports, use the following workaround:
Procedure 212 CMS installed on Windows
1.
2.
Open the reports.xml located in <HP SIM installation
directory>/config/preload/62/addfiles/reports.xml and change the timestamp.
You can do this by entering a space at the end of the file and resaving it.
Execute the mxconfigrefresh command at the command prompt.
Procedure 213 CMS installed on HP-UX or Linux
1.
2.
Open the reports.xml located in /etc/opt/mx/config/preload/62/addfiles/
reports.xml and change the timestamp. You can do this by entering a space at the end
of the file and resaving it.
Execute the mxconfigrefresh command at the command prompt.
After completing the procedure, the links to reports appear in the user interface.
Showing SQL
Procedure 214 Showing SQL
1.
2.
3.
4.
Select Reports→Manage Reports. The Manage Reports... page appears.
Select the report for which you want to see the SQL details.
Click Run Report. The report appears.
Click the Show SQL queries link.
The SQL Queries page appears.
Related information
Snapshot comparison reporting
Procedure 215 Snapshot comparison report
1.
2.
3.
Select Reports→Snapshot Comparison.... The Snapshot Comparison window appears.
Select target systems. For more information, see Creating a task.
Click Next. Click Previous to return to the Target Selection page.
Select two to four snapshots for the systems from the Select Snapshots page.
The following warnings are possible:
•
Some system OS types are unknown.
•
More than one operating system type is selected.
•
Only one operating system type comparison is supported.
•
If one target is selected, this target must have at least two snapshots. You must select
between two and four snapshots to compare.
•
If more than one target is selected, you can select one snapshot for each system.
The target systems selected should be of the same operating system for the snapshot
comparison feature to work.
4.
5.
6.
7.
Click Next.
From the Select Categories and Baseline page, select the category. The Category Name column
displays the category, and the Description column displays a brief description of the category.
From the Select snapshot comparison baseline section, select an item against which to run the
comparison.
Click Run Reports. The View Snapshot Comparison Result page displays listing the results.
Related information
332 Operations
Federated CMS Search Tool
Search Tab
Search criteria:
•
All fields operate on a contains basis. Boolean operators and wildcards are not supported.
•
All fields are case-insensitive.
•
Matches occur when all provided criteria are met.
•
Fields that accept text input also have a dropdown list of suggestions.
Procedure 216 Setting search criteria:
1.
In the System filter box, enter or select the criteria to be used for the search.
NOTE:
1
2
You can use any combination or all of the fields for search criteria.
Enter the name of a
system or group of
systems to be
searched.
Enter or select the
status of the system
from the dropdown
list.
3
4
Enter or select the type
of system to be
searched.
Enter or select the
subtype of the system
to be searched.
5
6
Enter or select the
product to be
searched.
Enter or select the
Operating System to be
searched.
NOTE: Status icons shown in the results do not update over time. Status represented in the
results table is the status at the time of the search.
2.
Select Include software filter to add a software filter to the selection criteria. The Include
software filter criteria box is enabled.
1
Select the type
software from the
dropdown list.
2
Enter the version of
the software to be
searched.
3
Enter the description of
the software to be
searched.
Reporting 333
NOTE: If software filtering is activated, then only systems with software information are
displayed in the results. Depending on the criteria, the results may be further filtered.
NOTE:
3.
Searching software information depends on the following:
•
Only CMSs running Systems Insight Manager 6.0 and later make software information
searchable remotely.
•
Software information is collected only if the system has a WBEM agent running and the
CMS managing the system is configured with suitable WBEM credentials to access the
agent.
In the Options box, select the option to be used if a system is found on more than one CMS.
NOTE: There can be an overlap in the systems that different CMSs manage. If the same
system is found on multiple CMSs, the information from the CMS with the newest system
information is displayed. You can change this setting to show all matches and the same system
could display multiple times in the results table.
4.
5.
6.
7.
8.
Click Search once all search criteria has been selected or click Reset Fields to clear all search
fields and make new criteria selections.
The Software information: table is populated with all systems that meet the search criteria.
Click Expand All to expand all rows to display all information for each system.
Click Collapse All to collapse additional information.
Click the hyperlink for any of the system names in the Name field to drill down into results
and sign into a secondary CMS. The hyperlink displays a browser window that displays the
Systems Insight Manager System Page for that system, as delivered by the CMS on which the
system was found.
NOTE: To sign into a secondary CMS automatically without needing to sign in again, the
following requirements must be met:
9.
•
Your browser must have the secondary CMSs SSL certificate installed.
•
The browser must be configured to allow third-party cookies. Secondary CMSs are
considered third-party systems in this case.
(Optional) Click Export to CSV to export the table into a spreadsheet.
Federated Search Advanced Search Tab
•
Advanced search can be performed on systems or events
•
You can dynamically build a query by adding multiple criterion
•
If there are multiple criterion, like criterion are placed together with "OR", if they are different,
they are placed together with "AND".
•
All fields are case-insensitive
•
Matches occur when all provided criteria are met
334 Operations
NOTE: By default, if the same system is found on multiple CMSs, the information from the CMS
with the newest system information is displayed. You can change this setting to show ALL matches,
in which case, the same system can display multiple times in the search results.
Procedure 217 Performing an advanced search for systems
1.
2.
Select systems from the Search for dropdown list.
From the first selection box (criteria selection), click the down arrow, and then select the search
criteria.
NOTE: Some search criteria show no values until systems with values for that criteria have
been discovered. In this case, the criteria is not displayed until values are available.
3.
From the second selection box (comparison selection), click the down arrow, and then select
the comparison option.
NOTE: Different criteria support different comparisons. The comparison options change with
the criteria selected. For example, if you select operating system as criteria, the following
possible comparisons are available: is, is not, contains, starts with, and ends with. See the
HP Systems Insight Manager User Guide, at http://www.hp.com/go/insightmanagement/
sim/docs, for more information.
4.
5.
In the third selection box (value selection), select one of the available values for specific criteria
or comparison combination from the dropdown list, or enter the required information in the
input box.
To add additional criteria, click Add. To conduct the system search immediately, click View.
To delete search criteria, click Delete. To save the search as a collection, click Save As.
NOTE: Criteria are reordered after clicking View or Save As. If criteria types are the same,
they are placed together with "OR", if they are different, they are placed together with "AND".
6.
(Only available for system searches) In the Options box, select the option to be used if a system
is found on more than one CMS.
NOTE: There can be an overlap in the systems that different CMSs manage. If the same
system is found on multiple CMSs, the information from the CMS with the newest system
information is displayed. You can change this setting to show all matches and the same system
could display multiple times in the results table.
7.
8.
9.
10.
11.
Click Search once all search criteria has been selected.
The Software information: table is populated with all systems that meet the search criteria.
Click Expand All to expand all rows to display all information for each system.
Click Collapse All to collapse additional information.
Click the hyperlink for any of the system names in the Name field to drill down into results
and sign into a secondary CMS. The hyperlink displays a browser window that displays the
Systems Insight Manager System Page for that system, as delivered by the CMS on which the
system was found.
Reporting 335
NOTE: To sign into a secondary CMS automatically without needing to sign in again, the
following requirements must be met:
•
Your browser must have the secondary CMSs SSL certificate installed.
•
The browser must be configured to allow third-party cookies. Secondary CMSs are
considered third-party systems in this case.
12. (Optional) Click Export to CSV to export the table into a spreadsheet.
Connections Tab
The connections tab displays the status of an attempted connection to each secondary CMS. If
Federated CMS Search fails to connect to a CMS, that CMS is excluded from subsequent searches.
After successful connection and if you have suitable authorizations locally on the secondary CMS,
the secondary Systems Insight Manager version, operating system, and system count are displayed.
Credential preferences
By default, all connections made to secondary CMSs are made as the currently signed-in user. To
connect as another user, you can specify full credentials for that user. The credentials are securely
encrypted and stored on the main CMS privately for the current user.
Procedure 218 Setting CMS credential preferences
1.
Click Credential Preferences.... The CMS Credential Preferences page appears.
2.
Select one of the following options:
•
Use signed-in user
•
Use specific user:
You must add the HP SIM user name: and the Password:.
3.
Click OK to save the changes or Cancel to cancel the changes and return to the Connections
page.
Refreshing connections
CMS connections are established once and maintained in the current instance of the UI. If a CMS
is rebooted or comes online after starting Federated Search, you must refresh connections to
establish a connection to the newly online CMS.
The connections tab displays the status of an attempted connection to each secondary CMS. If
Federated Search fails to connect to a CMS, that CMS is excluded from subsequent searches. After
successful connection and if you have suitable authorizations locally on the secondary CMS, the
secondary HP SIM version, operating system, and system count are displayed.
Credential preferences
By default, all connections made to secondary CMSs are made as the currently signed-in user. To
connect as another user, you can specify full credentials for that user. The credentials are securely
encrypted and stored on the main CMS privately for the current user.
336 Operations
Procedure 219 Setting CMS credential preferences
1.
Click Credential Preferences.... The CMS Credential Preferences page appears.
2.
Select one of the following options:
•
Use signed-in user
•
Use specific user:
You must add the HP SIM user name: and the Password:.
3.
Click OK to save the changes or Cancel to cancel the changes and return to the Connections
page.
Refreshing connections
CMS connections are established once and maintained in the current instance of the UI. If a CMS
is rebooted or comes online after starting Federated Search, you must refresh connections to
establish a connection to the newly online CMS.
Federated CMS Search Configuration
The Federated CMS Configuration is used to configure the list of secondary CMSs. In order for
the main CMS to be included in operations such as search, it must be added to the secondary list
and display a successful configuration status.
The Federated CMS Configuration feature provides you with the following options:
•
Add CMS
A wizard guides you through the process of adding a CMS. See “Adding a CMS”
•
Deleting a CMS
A selected CMS can be removed from the list of CMSs. When the CMS is deleted, the trust
relationship that was set up between the main CMS and secondary CMS is also removed.
•
Refreshing the list
Refreshing the list re-checks the configurations from the CMS.
•
Fixing the configuration of a CMS
After the initial configuration of a CMS, changes in the CMS could break the Federated CMS
configuration. The CMS table displays the current configuration status since the last refresh.
If the configuration is broken, you must use Fix CMS Configuration to repair the configuration.
Procedure 220 Adding a CMS
1.
2.
3.
Click Add CMS. The Add CMS wizard appears.
Enter the name of the remote CMS using the host name or IP address.
Verify the SSL certificate from the remote CMS.
This step gets the SSL certificate from the secondary CMS and allows you to install it on the
main CMS. If the certificate is retrieved successfully, it is displayed. After viewing the certificate,
you can click Continue or Cancel the wizard. If you finish the wizard, the certificate is installed.
Reporting 337
NOTE: Any time communication with a secondary CMS is initiated, the certificate returned
must already be installed.
4.
Configure the remote CMS.
The main CMSs SSL certificate is exported to the secondary CMS, and the secondary CMS
is configured to trust the main CMS. To have this configuration performed, you must provide
credentials for a full-rights HP Systems Insight Manager user on the secondary CMS. The
credentials supplied are used for this one transaction and are not permanently stored.
NOTE: To avoid remote CMS connection errors, make sure a firewall is not blocking ports 50001
and 50002 on the remote CMS.
Managing with tasks
HP SIM enables you to manage systems and events by scheduling and executing tasks. Tasks are
actions performed using an HP SIM tool. Task instances are an executed single instance of a task.
Users can:
•
Create a task.
•
Schedule a task.
•
Modify a task.
•
Delete a task
•
Stop and start a task
•
Track task status
Task information is available by selecting one of the following:
•
Tasks & Logs→View All Scheduled Tasks
•
Tasks & Logs→View Task Results
HP SIM provides a number of pre-defined system-delivered (default) tasks. These tasks can be
disabled or have their schedules modified but they cannot be removed or reassigned to another
user. HP SIM requires these tasks to provide a complete picture of the systems being monitored.
For more information about user privileges and configuration rights, see Users and authorizations.
Managing with tasks related information
Creating a task
NOTE: Scheduled task results are retained for 30 days or a maximum of ten results for a given
task. Run Now task results are retained for 72 hours. These are default values. To customize these
values, see Configuring task results settings.
Procedure 221 Create tasks
1.
Select a tool from the HP SIM menu. The Select Target Systems page usually appears; however,
if targets are selected before selecting a tool, the Verify Target Systems page appears.
Some non-destructive tasks, like Ping, run directly when selected from the menu and you have
systems selected. Non-destructive tasks that require user parameters will skip directly to those
pages, bypassing the system selection and verification screens.
The OS column displays the first 40 characters of the operating system name, with an ellipse
at the end of the name if it is more than 40 characters long. Place your cursor over the name
to see the entire operating system name.
2.
Add multiple or single targets:
338 Operations
a.
To add targets, you can choose either the Collection option or the Search option, which
indicates the method of target selection, or click Cancel which results in no additions.
NOTE: You are not allowed to select individual events for targets or filters, so the ability
to search is not available when those selections are made. The two radio options are not
present in these cases.
b.
c.
Choosing the Collection option enables you to select targets from the drop-down selection
box.
If you choose the Search option, the drop-down selection box and View Contents button
is replaced with the Quick Search user interface. Type a Device Name into the Text Field
and then click Search.
NOTE: If there are Device Names that match the characters typed in the Text Field, a
dynamic list appears with those matches.
d.
If you select one of the Device Names displayed in the dynamic list, a System Table
containing the selected system appears below the Quick Search user interface. Items
displayed in the Search Results table are selected (checked) by default and the Apply
button is enabled as long as there is at least one item from the Search Results table
selected. Only items that are selected are added when you click Apply.
NOTE: The maximum number of Device Names displayed is six. If there are more
available matches a "..." is present at the bottom of the dynamic list. Clicking Search will
display all the matches in the table.
e.
If you click Search, a Basic Search using common attributes is performed using the
characters typed into the Text Field. The results appear in the Search Results table below
the Quick Search user interface.
While the search user interface remains open, the Task Wizard retains a reference to the
Query object created to perform the Dynamic Query generation used when performing
searches. Each new search term is added to this Query object and a new Dynamic Query
is generated. The Task Wizard releases its reference to the search Query when you close
the search user interface or by clicking Cancel or Apply.
NOTE:
A progress bar appears while Basic Search results load.
After you select the system to add, the Select <item> itself checkbox is selected by default and
the Apply button and View Contents button are enabled. You can choose to click Apply or
View Contents.
NOTE: If you choose to change the selected item in the drop-down selection box, the Select
<item> itself text reflects the change.
NOTE:
If the Select <item> itself checkbox is cleared, the Apply button is disabled.
Selecting View Contents displays the Table View or Tree View of the selected item and the
Apply button is disabled.
NOTE: When View Contents is selected, the Target Selection Page displays a barbershop
pole and the message "Loading Data..." while the Table View or Tree View loads.
After you select items from the displayed Table View or Tree View, the Apply button is enabled.
NOTE: If the Select <item> itself checkbox is selected while a Tree View appears, the Tree
View is closed and the Apply button is enabled. If you clear the Select <item> itself checkbox,
the Tree View does not reappear and Apply is disabled. You must click View Contents to have
the Tree View displayed again.
Managing with tasks 339
3.
Click Apply. The targets appear in the Verify Target Systems page.
NOTE: If selected targets are not compatible with the tool, the Tool Launch OK? column
provides a brief explanation of the problem.
To remove a target, select Remove Targets.
A sub-window opens below the row of buttons that displays a smaller table with the targets
currently chosen on the Target Selection Page.
a. Select the checkboxes for the items you want to remove from your current list of chosen
targets.
b. Click Apply to close the sub-window and redraw the Target Selection Page with the
updated list of targets.
NOTE: The Apply button is enabled when there is at least one item selected from the
Remove Targets table.
c.
Select Cancel if you choose not to remove any of the target selections. If you select Cancel,
the sub-window closes, and no items are removed.
NOTE: If the tool targets systems, any Filter selected is a single Event Collection. If the tool
targets events, the Target selected is a single Event Collection. When these cases arise, a table
does not appear. The item appears as a static text or a hyperlink following the same logic
when displaying the selected item in a table.
4.
To filter target selections, complete the following.
a. Click Add Event Filter.
b. From the Add filters by selecting from dropdown box, select an event filter. If no filters
are selected, Cancel is enabled.
c. Click Apply to apply the filter to the target systems (or, click Cancel to cancel adding a
filter). The selected filter is displayed below the selected target systems.
NOTE: If the target selections are events instead of systems, the button changes to Add
System Filter, and you can select from different system collections. Unlike event filters,
you can select multiple system filters.
5.
To modify an event filter, click Modify Event Filter.
NOTE: If the filters are systems, the Add System Filters and Remove Filters buttons appear.
If there is only one event filter, the Remove Filters button removes the single event filter. If you
have more than one event filter, the Remove Filters button opens a subpane that you can select
the event filters to remove.
a.
b.
From the Add filters by selecting from dropdown box, select an event filter.
Click Apply to change the event filter and apply the filter to the target systems, or click
Cancel to cancel editing the filter.
NOTE: If the target selections are events instead of systems, the button does not change
to Modify System Filter. You have the option to select either Add System Filters or Remove
Filters. It is possible to have one or more system and event combination collections already
selected. If there are combination collections selected, they provide filtering.
6.
7.
To remove a filter, select the filter(s) that you want to remove, and click Remove Filters.
Click Next and specify tool parameters. If the tool does not require parameters, Next is
replaced with Schedule and Run Now. The Schedule option is present if the tool can be
scheduled.
340 Operations
8.
Select one of the following options:
•
Click Previous to return to the previous screen.
•
Click Schedule to schedule when the task runs. For more information about scheduling
options, see Scheduling a task.
•
Click Run Now to run the task immediately.
Managing with tasks related information
Scheduling a task
Default time for scheduling a task is 60 minutes.
Procedure 222 Scheduling a task
1.
2.
3.
Select a tool from the menu. For more information, see Creating a task.
In the Task name field, enter a unique name for the task.
Under the When would you like this task to run? section, select one of the following options:
•
Periodically
Select from intervals of minutes, hours, days, weeks, or months. With periodic scheduling,
you can configure the task to run until a certain date and time or to execute only a set
number of times. Periodic scheduling allows time filters to be applied. These filters specify
the hours of the day when a scheduled task can operate. For more information about
time filters, see Applying a time filter.
NOTE: If you want to schedule a task to run once a month on the 31st of the month
and the month has only 30 days, the task will run on the 1st day of the following month.
•
Once
Specify the date and time the task is to run.
•
When new systems or events are added to the collection
This option is only available if you select a Collection of Systems or Events as your target.
The task runs only when new systems or events meet the collection criteria. You can also
apply a time filter to this type of scheduling. For more information about time filters, see
Applying a time filter.
•
When systems or events are removed form the collection
This option is almost identical to the previous option, except that the task runs only when
systems contained in the Collection of Systems or Events no longer meet the collection
criteria. A time filter can be applied to this type of scheduling. For more information about
time filters, see Applying a time filter.
•
Not Scheduled
This option specifies that the task runs only when manually executed by a user with
appropriate privileges. This task never runs automatically. Tasks can be manually run
from the All Scheduled Tasks page or the CLI
Managing with tasks 341
4.
Under In addition, select from the following options:
•
Run when the central management server is started
Select this option if you want the task to run every time the CMS is started.
•
Run now
Select this option to run the task immediately after it is saved.
•
Disable this task
Select this option to temporarily disable the task. This task is shown as Disabled on the
All Scheduled Tasks page.
5.
6.
After you select a scheduling option, refine the schedule in the Refine schedule section. The
available options vary depending on the scheduling option selected in step 3.
Click Done. The All Scheduled Tasks page appears. Click Previous to return to the previous
page. For more information about the All Scheduled Tasks page, see Navigating the All
Scheduled Tasks page.
Viewing all scheduled tasks
To view all scheduled tasks, select Tasks & Logs→View All Scheduled Tasks.
The list of tasks that a user can see is based on the user's privileges. All users are allowed to edit,
delete, and view the tasks they have created. With administrative rights, the user is allowed to
edit, delete, and view tasks other users have created.
Managing with tasks related information
Applying a time filter
Use time filters to decide when a task runs. You can create, copy, edit, and delete time filters.
Time filters can be created by any user and are accessible to all users.
Procedure 223 Applying a time filter to tasks
1.
2.
3.
Select a tool from the tool menu, follow the steps to get to the Schedule button, and then click
it. For more information, see Creating a task and Scheduling a task.
To apply a time filter to a task, select the Use Time Filter checkbox.
Below the Schedule Task section, click Manage Filters and choose from the following options:
•
New. The new time filter has the default name New Time Filter X, where X is a number
making the time filter name unique. Click OK or Apply to save the new time filter, or click
Cancel to cancel the new time filter changes.
•
Edit. Time filters can be edited. A time filter cannot be renamed, so if a time filter must
be renamed, copy the time filter and give the copy a new name. Changes made to a
time filter are saved after clicking OK or Apply. If the time filter to be edited is in use by
one or more tasks, a message appears, stating Editing the time filter could
have undesirable effects in the tasks currently using the time
filter. To eliminate this problem, copy the time filter and give the copy a new name.
•
Copy. Any user can copy a time filter. The copied time filter name appears with a number
appended to it (to make the name unique). To save changes made to the time filter, click
OK or Apply.
•
Delete. A user can delete a time filter that is created by another user. Select the time filter,
and then click Delete. If the time filter is in use by one or more tasks, a message appears,
stating The time filter cannot be deleted because it is in use by
one or more tasks.
Time filters are created and viewed in the time zone of the user creating the time filter. For example,
if the default time filter of business hours (8 a.m. to 5 p.m.) is used and the filter is viewed in the
342 Operations
same time zone as the CMS, it will appear from 8 a.m. to 5 p.m. If the CMS is in EST and a user
accesses it in PST, the time filter appears as 5 a.m. to 2 p.m. instead. Time filters created at
installation use the time zone of the CMS.
NOTE: If you want to schedule a task to run once a month on the 31st of the month and the
month has only 30 days, the task runs on the 1st day of the following month.
Managing with tasks related information
Running a scheduled task
Procedure 224 Running a task
1.
2.
From the tool menus, select Tasks & Logs→View All Scheduled Tasks. The All Scheduled Tasks
appear in the workspace.
Select a task from the list, and then click Run Now.
NOTE:
If an instance of the task is running, the Run Now button is disabled.
Managing with tasks related information
Editing a scheduled task
Procedure 225 Editing a scheduled task
1.
2.
3.
Select Tasks & Logs→View All Scheduled Tasks. The All Scheduled Tasks page appears.
From the All Scheduled Tasks page, select the task to be edited.
Click Edit.
The previously configured task information appears. Follow the same steps as if you are
creating the task. For more information, see Creating a task.
Because the task has a schedule associated with it, you must access the Schedule Task Page.
The Run Now button is not present (as it is when a task is being created). Users with
administrative rights can change the owner of the task.
If the new owner does not have access rights to the tool or to selected targets, an error message
appears when the user attempts to edit or save the task.
4.
After you edit the task, click Done, or to run the task immediately, select the Run Now checkbox
on the Schedule Task page before clicking Done.
This task is saved and appears on the All Schedule Task Page.
Managing with tasks related information
Deleting a scheduled task
Deleting a task removes the task and its associated task instances from the All Scheduled Tasks
page and the system.
CAUTION: If you delete a task, the task is permanently deleted from the database and cannot
be restored.
NOTE:
You cannot delete system delivered (default) tasks.
Procedure 226 Deleting task instances
1.
2.
Select Tasks & Logs→View All Scheduled Tasks.
Select a task from the All Scheduled Tasks list.
Managing with tasks 343
3.
Click Delete.
NOTE: If an instance of the task is running, a message appears stating that you must stop
the running task instance before the task can be deleted.
Managing with tasks related information
Printing reports
Procedure 227 Printing a task results report
1.
2.
From the menu, select Tasks & Logs→View Tasks Results.
Click View Printable Report.
A Print Report Question appears, asking to generate a report containing the selected target
system or all target systems associated with the task instance.
3.
4.
Select the report to print.
Click OK to print the report.
Managing with tasks related information
Stopping a task
Procedure 228 Stopping a task instance
1.
2.
From the menu, select Tasks & Logs→View Task Results, and then select a task instance from
the Task Results list.
Click Stop. If the task instance is in a terminal state, Stop is disabled. If the task can be stopped,
a dialog appears, asking if you want to cancel or kill the selected task instance. If the tool
does not signify that the task can be stopped, the dialog box asks you to confirm the
cancellation of the task instance. Stopping a task attempts to interrupt In Progress commands.
Canceling stops pending systems from starting and enables Running or In Progress commands
to complete.
Managing with tasks related information
Configuring task results settings
HP SIM removes old tasks and jobs created by those tasks. A job is the results of a task that ran,
either as a scheduled task or as a manually ran task. Tasks are removed according to the rules in
the following procedure. HP SIM keeps the maximum configured counts, whichever comes first.
Keep task results longer results in slower response time in HP SIM. For large installations (2000
or more systems), HP suggests reducing the scheduled task configurations by one half. For example,
5 tasks and 15 days.
Procedure 229 Configuring task results settings
1.
2.
Select Options→Task Results Settings. The Task Results Settings page appears.
To set the schedule for removing scheduled task results, enter:
•
Number of results
The default maximum number of results retained per scheduled task is 10.
•
Number of days
The default number of days scheduled tasks are retained is 30.
One job is always retained.
344 Operations
3.
To set a schedule removing run now tasks, enter:
•
Number of results
The default maximum number of task results retained for run now tasks is 750.
•
Number of hours
The default maximum number of hours task results are retained for run now tasks is 72.
4.
5.
6.
To run cleanup immediately, select Run cleanup now.
Click OK. A dialog box appears stating that the settings have been saved.
Click OK.
Managing with tasks related information
Deleting task results
NOTE: Scheduled task results are retained for 30 days or a maximum of ten results for a given
task. Run Now task results are retained for 72 hours. These are default values. To customize these
values, see Configuring task results settings.
Procedure 230 Deleting task results
1.
2.
Select Tasks & Logs→View Task Results and then select a task from the table.
Click Delete. The task instance is deleted from the database.
NOTE: If the task instance is running, a message appears, stating that you must stop the
running task instance before it can be deleted.
Managing with tasks related information
Task results list
Procedure 231 Viewing task information
1.
Click the task row and then select one of the following options:
•
Stop. Click Stop to stop a running task instance. For more information, see Stopping a
task.
•
Delete. Select a task instance, and then click Delete. For more information, see Deleting
task results.
NOTE: If a task instance is running, a message appears informing you to stop the task
instance before attempting to delete it.
Managing with tasks 345
2.
View the results of a task instance below the Task Results list.
The Task Instance Results section displays the following information:
•
Status. This field displays the status of the task. For more information about the different
status types, see the HP Systems Insight Manager User Guide, at http://www.hp.com/
go/insightmanagement/sim/docs.
•
ID. This field displays the task job ID number.
•
Task Name. This field displays the name of the task that was executed.
•
Tool. This field displays the name of the tool that was used.
•
Owner. This field displays the user name that owns the task.
•
Command. This field displays the command used to run the task.
•
Target. This field displays the name of the target collection or systems that the task executed
on. If you run a custom command tool or a MSA tool, this field displays the CMS system
name. With custom command and MSA tools, the executables reside on the CMS and
are run from the CMS to the remote system. Therefore, the Target for these types of
commands are always shown as the CMS.
The remaining tool types (SSA, Automation, and so on) have the actual targets the tool
ran on listed in the Target field. This value might be a single system, multiple systems
(comma-separated), or the name of the collection selected for the task. If the Target is a
collection or multiple systems, the target value becomes a hyperlink. Click the hyperlink
to display the contents of the collection or the complete list of systems if the Target field
displays a partial comma-separated list of the target systems.
•
Executed As. This field displays the user context where the tools were executed.
•
Start time. This field displays the time the task started.
•
End time. This field displays the time the task ended.
•
Duration. This field displays the time that the task took to run.
The list of task instances is based on user privileges and access levels. Users with administrative
rights can view all task instances known to the system.
Managing with tasks related information
Managing with tasks related information
Related procedures
Creating a task
Scheduling a task
Running a scheduled task
Stopping a task
Deleting task results
Printing reports
Editing a scheduled task
Deleting a scheduled task
Related topic
Applying a time filter
346 Operations
Using Cluster Monitor
Procedure 232 Cluster Monitor
1.
Access the Cluster Monitor page by using one of the following methods:
•
Method 1:
1. Select Tools→System Information→Cluster Monitor.
NOTE:
2.
•
If no MSCS clusters are discovered, Cluster Monitor is not listed in the menu.
Select a target MSCS cluster, and then click Run Now. See Creating a task for more
information about selecting a target cluster.
Method 2:
1. Locate a cluster by expanding Systems under the System and Event Collections panel
and selecting a cluster collection.
The appropriate cluster collection table appears in the workspace.
NOTE: Only MSCS clusters you are authorized to access appear on the cluster
table view page.
2.
Choose one of the following:
◦
In the Cluster Name column, click the name of the MSCS cluster.
◦
In the CS column on the cluster table view page, click the MSCS cluster status
icon.
The Cluster Monitor page appears for that cluster.
2.
Select from the following tabs available on the Cluster Monitor page. Every tab includes a
Problem Info section that provides details about problems reported on the tab. For example,
on the Cluster tab, this section includes status information if the cluster has a status of anything
other than Normal.
Each tab also includes a Last Updated field that displays the last time the information on the
tab was updated.
•
Cluster
Use to view cluster information such as the cluster status, name, IP address, and quorum.
•
Nodes
Use to view node information such as the node status, name, and IP address.
•
Network
Use to view network information such as the network status, name, mask, state, role, and
description.
•
Resources
Use to view MSCS Resource information for the cluster, including the status, name, IP
address, state, group, owner node, type, and drive of the resources.
Configuring cluster resource settings
Procedure 233 Configuring Custer Resource Settings
1.
2.
Configure MSCS clusters by selecting ALL (MSCS) from the Cluster Type list.
From the Resource list, select MSCS.
Using Cluster Monitor 347
3.
Select Polling and set the polling rate.
HP recommends setting the polling rate to no less than 5 minutes.
4.
Click OK to save the changes.
Related procedures
Configuring node resource settings
Related topic
Using Cluster Monitor
Configuring node resource settings
Procedure 234 Configuring Node Resource Settings
1.
2.
3.
4.
From the Cluster list at the top of the page, select the cluster, and then select All to configure
a resource in the same way for all clusters. To set polling values for CPU utilization or disk
capacity, set the cluster choice to All.
From the Node list, select the node, and then select All to configure a resource in the same
way for all nodes in the selected cluster. As in step 2, you can set some resource attributes
only once for all nodes. As a result, you must select all clusters and nodes. For more information,
see the individual attribute descriptions for a particular resource.
To display buttons for resource-configurable parameters, select the resource from the Resource
list.
Specify resource options.
HP recommends setting the polling rate to no less than 5 minutes.
If you select All from the Cluster list and select CPU or Disk from the Resource list, you can set
polling or threshold values. If you select Polling, set the value, then select Thresholds, set the
values, and then select Polling again. The new polling values appear. Regardless of when
you click OK after setting the polling or thresholds values, these values are saved and do not
reset to the original value, which is the same when setting thresholds.
5.
Click OK to save the changes.
Related procedures
Configuring cluster resource settings
Command line tools
A CMS tool usually runs on the CMS and is usually a script or batch file that can pass environment
variables. Using automatic event handling, you can configure this tool to run when specific events
are received. This tool can be scheduled and is selected by default when you access the New
Custom Tool page. For more information about the environment variables that can be passed, see
Custom tool environment variables. In previous releases of HP SIM, CMS tools were called custom
tools.
Procedure 235 Creating a CMS tool
1.
Under Tool Parameters, enter the following information:
a. In the Name field, enter the command name. Custom tool names must be at least one
character, and not more than 255 characters in length. The first character of the name
must be alphabetic. Subsequent characters can be letters, digits, spaces, or any of the
following: "-", ".", "(", ")" or "_".
b. In the Description field, enter the information for the tool.
c. In the Help comments field, enter comments for the tool.
d. In the Menu placement field, enter the full path (from the root of the HP SIM console) and
the file name of the tool (for example, c:\custom code\romflash.bat).
348 Operations
2.
Specify the user account on the target system by selecting one of the following options:
•
Logged-in user
The tool uses the user account that is logged in.
•
Special user
For UNIX and Linux systems, root; for Windows systems, Administrator. The tool does not
run on targets with an unknown operating system.
•
Specific user
The tool uses the specified user account.
3.
In the Command with parameters field, enter parameters.
The interface supports nine parameters. If you enter more than nine, the last parameter appears
as Zero(0) on the Task Results page.
4.
Optional: Enter the Environment variables for the tool and add or delete variables as needed.
For a list of variables available from HP SIM, see the HP Systems Insight Manager Command
Line Interface Guide, at http://www.hp.com/go/insightmanagement/sim/docs.
•
Optional: To delete a specified variable, click Delete.
•
Optional: To add additional variables, click Add.
DOS environment variables are supported in custom tool parameters and work as parameters
on the New Custom Tool page or the Manage Custom Tools page. Unless you use DOS
environment variables in a batch or script file, you must surround them with double percent
(%) signs. For example, to pass in the NOTICELABEL environment variable as a parameter on
the parameter line, enter %%NOTICELABEL%%. If you use DOS environment variables in a
batch file or script file, use only a single percent (%) sign before and after the environment
variable name. For a list of other substitutable environment variables, see the HP Systems
Insight Manager User Guide, at http://www.hp.com/go/insightmanagement/sim/docs.
5.
6.
If you can schedule the tool, select Tool can be scheduled.
Click OK to add the new tool to the Custom Tools menu and access the Manage Custom Tools
page, or click Previous to return to the previous page to select another type of custom tool.
NOTE:
New custom tool tools are located under Tools→Custom Tools.
Configuring managed systems from a Windows CMS
Managed systems must be able to communicate status to the HP SIM CMS in order to launch
commands to the managed systems. To configure the managed systems to communicate with the
CMS, you must configure common configurations and trust relationships. The Configure or Repair
Agents feature enables you to configure or repair agents in Windows, Linux, and HP-UX.
The Configure or Repair Agents tool enables you to repair Simple Network Management Protocol
settings and trust relationships that exist between HP Systems Insight Manager and target systems
if you have HP Insight Management Agents 7.2 or later installed. If you have HP Insight Management
Agents 7.1 or earlier installed, you can update Web Agent passwords on target systems.
This tool adds the security and trap community strings and trust settings to the target systems, but
it does not replace existing settings. To replace existing settings on target systems, use the Replicate
Agent Settings feature in HP SIM.
You can use Configure or Repair Agents tool to send test SNMP traps from Windows systems with
Insight Management Advisors and send test Web-Based Enterprise Management indications from
Windows and HP-UX systems with HP WBEM provider installed.
Configuring managed systems from a Windows CMS 349
The Configure or Repair Agents feature on a Windows CMS also enables you to install various
agents and providers on a ProLiant or Itanium-based system with Windows operating system. It
can install:
•
HP Insight Management WBEM Providers for Windows Server 2003 or Windows Server
2008
•
OpenSSH
•
Version Control Agent for Windows
•
Insight Management Advisors for Windows
Configuring or repairing the agents
You can install Insight Management Agents or providers, either WBEM or SNMP, on managed
systems so that HP SIM can collect inventory and status information from these systems and receive
event notifications from the systems. Installation is supported only on ProLiant or Itanium-based
servers with a Windows operating systems.
Procedure 236 Configuring or repairing the agents
1.
2.
3.
4.
5.
6.
Select Install Agentless Management Service (AMS) on HP ProLiant Gen8 servers running
Windows, Linux, or ESX to send all host operating system-specific data to the iLO 4 firmware.
Select Install Linux PSP or ESX Agents to install Linux PSP and ESX Agents which are a collection
of SNMP agents used by HP SIM to gather information from managed systems and send traps
to HP SIM.
Select Install WBEM / WMI Provider (HP Insight Management WBEM Provider) for Windows
to install WBEM or WMI providers on Windows managed systems.
Select Install SNMP Agent (Insight Management Advisor) for Windows to install the SNMP
agent on Windows managed systems. This Insight Management Agent allows network
monitoring and control.
Select Install OpenSSH to install OpenSSH on Windows managed systems.
Select Install the Version Control Agent for Windows (VCA) to install the HP VCA on Windows
managed systems. The HP VCA enables you to view the HP software installed on a system
and whether updates for the software are available in the repository.
Installs the HP VCA in conjunction with the Version Control Repository Manager and enables
management of the HP ProLiant software and firmware on the managed systems.
7.
Select Register VM Host for VMware ESX, Citrix XenServer, Microsoft Hyper-V, and Xen on
SLES and RHEL.
350 Operations
8.
For selected installs, perform the following steps:
a. If you are installing software that is earlier than or the same version currently installed,
select Force install the agents . This option is disabled by default.
b. If you want to reboot after the installation, select Reboot systems if necessary after
successful install option.
HP SIM determines the type of agent or provider to install based on the system type,
subtype, and operating system description of the system.
If you want to install a 64-bit agent or provider, be sure the target system is identified as
a 64-bit system in HP SIM.
If your system is not correctly identified, go to System Page→Tools & Links→Edit System
Properties. Select the correct system type, or subtype and enter the operating system
description manually.
Example: Installing Insight Management Agents on a ProLiant Windows 64-bit system:
a. Select System type: server.
b. Select System subtype 1: HP ProLiant.
c. Enter operating system description as Microsoft Windows Server 2003, x64 Enterprise
Edition Service Pack 1 or the correct operating system description of your system.
If you want to configure the agents after installation, select the force reboot option. This
allows the newly installed component to be completely initialized before you configure
it.
NOTE:
Installation with reboot typically takes about 8 minutes.
Configuring managed systems from a Windows CMS
351
9.
Click Next. The Step 3: Configure or Repair Agents Settings page appears.
NOTE: The Step 3: Configure or Repair Settings page changes to show the configuration
options available with the installed plug-ins.
Related Topics
Configuring
Configuring
Configuring
Configuring
352 Operations
target system settings
credentials
managed systems from a Linux CMS
managed systems from an HP-UX CMS
Configuring target system settings
Configuring managed systems from a Windows CMS 353
1.
Configure the target systems by selecting one of the following options:
•
Configure WBEM / WMI. This section enables you to configure the target Linux, Windows,
or HP-UX system to send WBEM indications or events to HP SIM.
For this section, consider the following:
◦
Create subscription to WBEM events so that WBEM events will be sent to the CMS
◦
Send a sample WBEM / WMI indication to this instance of HP SIM to test that events
appear in HP SIM in the Event List or All Event User Interface for the selected system
NOTE:
SIM.
This indication will appear as an Informational Event in the Event List of HP
NOTE: This indication is supported only on HP-UX and Windows targets with
WBEM provider installed.
◦
Use an HP SIM WBEM certificate (good for 10 years) rather than
username/password to manage the system
This option deploys a WBEM certificate to the managed system and is only valid for
HP-UX systems.
◦
Configure a non-administrative account for HP SIM to access WMI data
This option applies to Windows systems with HP WBEM providers. The configuration
of the managed system updates to allow the specified user to access WMI information
over the network. HP SIM uses this user to read inventory and configuration
information from the system and is configured as the WBEM user in the System
Credentials. If HP SIM is configured with a user with administration rights, this
configuration step is not necessary. HP SIM does not create this user. The user already
exists as either a domain user or one local to the managed system.
The user is added to the DCOM Users group on the managed system and has
read-only access to WMI information, and read-write permissions to the HPQ name
space. This user does not need to be an administrator of the managed system or
have sign-in rights. The domain administrator should create a special domain account.
To enter the credentials for HP SIM to use to access the managed systems:
1. In the User name field, enter a user name.
2. In the Password field, enter the password.
3. In the Password (Verify) field, re-enter the password exactly as it was entered
in the Password field.
4. In the Domain (Optional) field, if the target belongs to a Domain, enter the
Windows domain.
If configuration of a nonadministrative user is successful, then these credentials
are saved as the System Credentials for WBEM access in HP SIM.
NOTE:
•
HP VCA can also be connected to HP VCRM through the certificate option.
Configure SNMP
This section enables you to configure SNMP settings.
a. Select Set SNMP cmmunity strings to specify the Read Community string and the Trap
Community string. By default, the first HP SIM read community string that is not public
appears. If no community string exists in HP SIM, you must enter one.
354 Operations
NOTE: If you configure only HP-UX systems with default SNMP installations, you
do not need to set this option. HP-UX enables read by default (get-community-name
is set to public by default on HP-UX systems).
NOTE: If you select this option, the Read Only community string is added to the
target systems. If the target system is SuSE Linux or Microsoft Windows 2003, the
managed systems do not always enable SNMP communication between themselves
and a remote host. This setting is modified to enable the instance of the HP SIM
system to communicate using SNMP with these target systems.
NOTE:
You can enter a community string up to 255 characters.
NOTE: Repairing the SNMP settings adds a Read Write community string to the
target system only if one does not currently exist. This community string is unique for
each system, is composed of over 30 characters to include letters and numbers, and
is visible only to the user with administrator privileges for that system. This Read Write
community string is required by the Web Agent to perform certain threshold setting
capabilities. This community string is used locally only on the target system and is
not used by HP SIM over the network. Linux and HP-UX systems do not require a
Read Write community string. The Read Write community string is added on Windows
system's SNMP settings.
b.
Select Set traps to refer to this instance of HP Systems Insight Manager in the target
systems SNMP Trap Destination List. This setting enables the target systems to send
SNMP traps to this instance of HP SIM.
Select Set additional list of SNMP Trap Destinations for an iLO Management Engine
to set additional SNMP trap destinations. Enter the trap destination information in
the fields provided. This step is for an HP iLO 4 only.
c.
Select Send a sample SNMP trap to this instance of the HP SIM to test that events
appear in HP SIM event lists to verify that SNMP events appear in the HP SIM events
list.
To successfully send a test trap, you must configure target systems to send a trap to
this instance.
NOTE: You can send a test trap only from a managed system with an Insight
Management Advisor installed.
NOTE: The trap from Windows appears as a Generic Trap from the system and
is listed as a Major Event in the Event List of HP SIM. The trap received from Linux
and HP-UX targets appears as a Cold Trap and is listed as Informational Events in
the Event List of HP SIM.
1)
2)
3)
In the Configure SNMP for iLO Management Engine dropdown list, select either
Agentless Management or SNMP Pass-thru.
In the Forward Insight Management Agent SNMP Alerts dropdown list, select
either Enable or Disable.
In the iLO SNMP Alerts dropdown list, select either Enable or Disable.
Configuring managed systems from a Windows CMS 355
•
Configure secure shell (SSH) access
Select this option to configure SSH access on managed systems.
If you select this option, you must select one of the following options:
◦
Host based authentication for SSH
NOTE: For this option to work, the user name and password provided in Step 4:
Enter credentials must be an administrative level account. For Linux or HP-UX targets,
it must be the root account and password.
◦
Each user has to be authenticated on the managed system
NOTE: If you do not want all users that have sign-in access to HP SIM to run the
tool and you would like to control which users need to have access, this option is
more secure.
NOTE: You can configure SSH only if the OpenSSH service is running on the
managed systems.
•
Set Trust relationship to "Trust by Certificate"
Select this option to configure systems to use the Trust by Certificate trust relationship with
the HP SIM.
For HP SIM on the target systems, this option sets the trust mode to Trust by Certificate
and copies the HP SIM system certificate to the target system trusted certificate directory.
This option enables HP SIM users to connect to the HP SMH using the certificate for
authentication.
You can configure SSO to management processors for Onboard Administrator and for
remote management. To configure SSO, select Set Trust Relationship. After you configure
SSO, you are not continually prompted to supply the login credentials for the management
processor.
NOTE: For systems with Management HTTP Server 5.x and earlier, the Configure or
Repair Agents setting adds the Administrator password in the Management HTTP Server
store and modifies the SNMP settings, but it cannot change trust relationship information.
Select the checkbox beside Import Secure Sockets Layer (SSL) certificate for HP SIM to
trust the HP SMH of the managed system. This option is only valid for HP-UX and Linux
operating systems.
•
Configure HP Version Control Agent
Select this option to configure the HP VCA to point to the Version Control Repository
Manager, where the repository of software and firmware is located, enabling version
comparison and software updates. This option is available for Windows and Linux systems.
To configure HP VCA:
1. In the Select the system where the HP VCRM is installed field, select a server from the
dropdown list.
2. In the User Name field, enter the user name to access the HP VCRM. This user cannot
be the default administrator user, and must have administrative privileges.
3. In the Password field, enter the password to access the HP VCRM.
4. In the Password (verify) field, re-enter the password for the HP VCRM.
5. In the Domain (Optional) field, enter the domain for the HP VCA.
356 Operations
•
Set administrator password for Insight Management Agents 7.1 or earlier
Select this option to repair the administrator password on all Insight Management Agents
installed on the target systems as applicable for Windows and Linux systems.
NOTE: Do not set this option if you have Insight Management Agents 7.2 or later
installed.
NOTE: If the remote system is running HP-UX, this option is not executed on the remote
system because it is not applicable on HP-UX systems. If you are configuring only HP-UX
target systems, you do not need to set this option.
If you select this option, you must complete the following steps:
a. In the Password field, enter the new administrator password.
b. In the Password (verify) field, re-enter the new administrator password.
•
2.
Select Configure Embedded Remote Support Settings for iLO Management Engine to
configure ERS settings. Select one of the following options:
1. Select Connect this server to an Insight Remote Suppprt hosting server and enter the
Remote Support URL and port.
2. Select Disable the Embedded Remote Support connection.
Click Next. The Step 4: Enter credentials page appears.
Configuring credentials
The credentials specified on this page are for a privileged account on the target system.
1. Enter the following credentials.
The credentials used in this step must work for all selected target systems. HP recommends
using domain administrator credentials. Credentials entered here are not saved by HP SIM
except to run a scheduled task later.
If you select Configure secure shell (SSH) access for a Windows target system, the account you
specify must be a member of the local Administrators group. For Windows targets using a
domain account, the account is automatically added to this group.
a. Select one of the following options:
•
•
b.
c.
d.
e.
Use sign-in credentials These credentials must be a privileged account on the managed
system. The sign-in credentials option is available if the following options are selected:
◦
Install WBEM/WMI Provider (HP Insight Management WBEM Provider) for
Windows
◦
Install Simple Network Management Protocol Agent (HP Insight Management
Agents) for Windows
◦
Install Linux PSP or ESX Agents
◦
Install the Version Control Repository Manager for Windows
Use the following credentials for all systems.
In the User name field, enter the system administrator name.
In the Password field, enter the system administrator password.
In the Password (Verify) field, re-enter the system administrator password.
In the Domain (Optional) field, if you are using a domain account, enter the Windows
domain.
Configuring managed systems from a Windows CMS 357
2.
Click Run Now or click Schedule to run this task at a later time. The Task Results page appears.
If the Management HTTP Server is installed on target systems, the login credentials are updated
in the Management HTTP Server password file. As with other HP SIM tools, you can configure
the Configure or Repair Agents tool to run on a schedule or manually. Only one instance of
Configure or Repair Agents tool can run at a time.
The Configure or Repair Agents tool can update multiple target systems. The log results indicate
whether the repair attempt was successful. For Configure or Repair Agents, the Task Results
page displays the following information.
Table 41 CRA Task Results information
Field Name
Description
Status
This field displays the details for each target system
within a task instance.
Exit Code
This field represents the success or failure of an
executable program. If the return value is zero or a
positive value, the executable ran successfully. If a
negative value is returned, the executable failed. This
exit code does not indicate that all configuration
attempts were successful. It is possible for some to
succeed but some to fail.
Target Name
This field displays the name/IP address of the target.
The stdout tab
This tab displays the output text information.
The stderr tab
This tab displays information if the executable
experienced an error.
View Printable Report
You can print reports for the selected target system or
for all target systems associated with the task instance.
To print a report:
a. Click View Printable Report.
An Options Message box appears.
b. Select a report.
c. Click OK to display the report, or click Cancel to
return to the View Task Results page.
Configuring managed systems from a Linux CMS
Managed systems must be able to communicate status to the Systems Insight Manager CMS in
order to launch commands to the managed systems. To configure the managed systems to
communicate with the CMS, you must configure common configurations and trust relationships.
The Configure or Repair Agents feature enables you to configure or repair agents in Windows,
Linux, and HP-UX.
The Configure or Repair Agents tool enables you to repair Simple Network Management Protocol
settings and trust relationships that exist between HP SIM and target systems if you have Insight
Management Agents 7.2 or later installed. If you have Insight Management Agents 7.1 or earlier
installed, you can update Web Agent passwords on target systems.
This tool adds the security and trap community strings and trust settings to the target systems, but
it does not replace existing settings. To replace existing settings on target systems, use the Replicate
Agent Settings feature in Systems Insight Manager.
358 Operations
Configuring or repairing the agents
From a Linux CMS, this option supports installing only Linux PSP or ESX agents, which are a
collection of SNMP agents used by HP SIM to gather information from managed systems and send
traps to HP SIM.
1. For Linux systems, select Install Linux PSP or ESX Agents.
2. Click Next. The Step 3: Configure or Repair Agents page appears.
Related Topics
Configuring managed systems from a Windows CMS
Configuring managed systems from an HP-UX CMS
Configuring managed systems from a Linux CMS 359
Configuring target system settings
360 Operations
1.
Configure the target systems by selecting one of the following options:
•
Configure WBEM / WMI. This section enables you to configure the target Linux, Windows,
or HP-UX system to send WBEM indications or events to Systems Insight Manager.
For this section, consider the following:
◦
Create subscription to WBEM events so that WBEM events will be sent to the CMS
◦
Send a sample WBEM / WMI indication to this instance of Systems Insight Manager
to test that events appear in Systems Insight Manager in the Event List or All Event
User Interface for the selected system
NOTE: This indication will appear as an Informational Event in the Event List of
Systems Insight Manager.
NOTE: This indication is supported only on HP-UX and Windows targets with
WBEM provider installed.
◦
Use an Systems Insight Manager WBEM certificate (good for 10 years) rather than
username/password to manage the system
This option deploys a WBEM certificate to the managed system and is only valid for
HP-UX systems.
◦
Configure a nonadministrative account for HP SIM to access WMI data
This option applies to Windows systems with HP WBEM providers. The configuration
of the managed system updates to allow the specified user to access WMI information
over the network. HP SIM uses this user to read inventory and configuration
information from the system and is configured as the WBEM user in the System
Credentials. If HP SIM is configured with a user with administration rights, this
configuration step is not necessary. HP SIM does not create this user. The user already
exists as either a domain user or one local to the managed system.
The user is added to the DCOM Users group on the managed system and has
read-only access to WMI information, and read-write permissions to the HPQ name
space. This user does not need to be an administrator of the managed system or
have sign-in rights. The domain administrator should create a special domain account.
To enter the credentials for Systems Insight Manager to use to access the managed
systems:
1. In the User name field, enter a user name.
2. In the Password field, enter the password.
3. In the Password (Verify) field, re-enter the password exactly as it was entered
in the Password field.
4. In the Domain (Optional) field, if the target belongs to a Domain, enter the
Windows domain.
If configuration of a nonadministrative user is successful, then these credentials
are saved as the System Credentials for WBEM access in HP SIM.
•
Configure SNMP
This section enables you to configure SNMP settings.
NOTE: The second and third read only community string and trap community string are
only used for iLO 4.
a.
Select Set read public community string to specify a community string. By default,
the first Systems Insight Manager community string that is not public appears. If no
community string exists in HP SIM, you must enter one.
Configuring managed systems from a Linux CMS
361
NOTE: If you configure only HP-UX systems with default SNMP installations, you
do not need to set this option. HP-UX enables read by default (get-community-name
is set to public by default on HP-UX systems).
NOTE: If you select this option, the Read Only community string is added to the
target systems. If the target system is SuSE Linux or Microsoft Windows 2003, the
managed systems do not always enable SNMP communication between themselves
and a remote host. This setting is modified to enable the instance of the HP SIM
system to communicate using SNMP with these target systems.
NOTE:
You can enter a community string up to 255 characters.
NOTE: Repairing the SNMP settings adds a Read Write community string to the
target system only if one does not currently exist. This community string is unique for
each system, is composed of over 30 characters to include letters and numbers, and
is visible only to the user with administrator privileges for that system. This Read Write
community string is required by the Web Agent to perform certain threshold setting
capabilities. This community string is used locally only on the target system and is
not used by HP SIM over the network. Linux and HP-UX systems do not require a
Read Write community string. The Read Write community string is added on Windows
systems only.
b.
c.
Select Set traps to refer to this instance of HP Systems Insight Manager in the target
systems SNMP Trap Destination List. This setting enables the target systems to send
SNMP traps to this instance of HP SIM.
Select Send a sample SNMP trap to this instance of the HP SIM test that events appear
in HP SIM event lists to verify that SNMP events appear in the HP SIM events list.
To successfully send a test trap, you must configure target systems to send a trap to
this instance.
NOTE: You can send a test trap only from a managed system with an Insight
Management Agents installed.
NOTE: The trap from Windows appears as a Generic Trap from the system and
is listed as a Major Event in the Event List of Systems Insight Manager. The trap
received from Linux and HP-UX targets appears as a Cold Trap and is listed as
Informational Events in the Event List of HP SIM.
•
Configure secure shell (SSH) access
Select this option to configure SSH access on managed systems.
If you select this option, you must select one of the following options:
◦
Host based authentication for SSH
NOTE: For this option to work, the user name and password provided in Step 4:
Enter credentials must be an administrative level account. For Linux or HP-UX targets,
it must be the root account and password.
◦
Each user has to be authenticated on the managed system
NOTE: If you do not want all users that have sign-in access to Systems Insight
Manager to run the tool and you would like to control which users need to have
access, this option is more secure.
NOTE: You can configure SSH only if the OpenSSH service is running on the
managed systems.
362 Operations
•
Set Trust relationship to "Trust by Certificate"
Select this option to configure systems to use the Trust by Certificate trust relationship with
the Systems Insight Manager.
For Systems Insight Manager on the target systems, this option sets the trust mode to Trust
by Certificate and copies the Systems Insight Manager system certificate to the target
system trusted certificate directory. This option enables Systems Insight Manager users to
connect to the SMH using the certificate for authentication.
You can configure SSO to management processors for Onboard Administrator and for
remote management. To configure SSO, select Set Trust Relationship. After you configure
SSO, you are not continually prompted to supply the login credentials for the management
processor.
NOTE: For systems with Management HTTP Server 5.x and earlier, the Configure or
Repair Agents setting adds the Administrator password in the Management HTTP Server
store and modifies the SNMP settings, but it cannot change trust relationship information.
Select the checkbox beside Import Secure Sockets Layer (SSL) certificate for Systems Insight
Manager to trust the HP SMH of the managed system. This option is only valid for HP-UX
and Linux operating systems.
•
Configure HP Version Control Agent
Select this option to configure the VCA to point to the HP Version Control Repository
Manager, where the repository of software and firmware is located, enabling version
comparison and software updates. This option is available for Windows and Linux systems.
To configure VCA:
1. In the Select the system where the VCRM is installed field, select a server from the
dropdown list.
2. In the User Name field, enter the user name to access the VCRM. This user cannot
be the default administrator user, and must have administrative privileges.
3. In the Password field, enter the password to access the VCRM.
4. In the Password (verify) field, re-enter the password for the VCRM.
NOTE:
5.
•
HP VCA can also be connected to HP VCRM through the certificate option.
In the Domain (Optional) field, enter the domain for the HP VCA.
Set administrator password for Insight Management Agents 7.1 or earlier
Select this option to repair the administrator password on all Insight Management Agents
installed on the target systems as applicable for Windows and Linux systems.
NOTE: Do not set this option if you have Insight Management Agents 7.2 or later
installed.
NOTE: If the remote system is running HP-UX, this option is not executed on the remote
system because it is not applicable on HP-UX systems. If you are configuring only HP-UX
target systems, you do not need to set this option.
If you select this option, you must complete the following steps:
a. In the Password field, enter the new administrator password.
b. In the Password (verify) field, re-enter the new administrator password.
2.
Click Next. The Step 4: Enter credentials page appears.
Configuring credentials
The credentials specified on this page are for a privileged account on the target system.
Configuring managed systems from a Linux CMS 363
1.
Enter the following credentials.
The credentials used in this step must work for all selected target systems. HP recommends
using domain administrator credentials. Credentials entered here are not saved by Systems
Insight Manager except to run a scheduled task later.
If you select Configure secure shell (SSH) access for a Windows target system, the account you
specify must be a member of the local Administrators group. For Windows targets using a
domain account, the account is automatically added to this group.
a. Select one of the following options:
•
•
b.
c.
d.
e.
364 Operations
Use sign-in credentials These credentials must be a privileged account on the managed
system. The sign-in credentials option is available if the following options are selected:
◦
Install WBEM/WMI Provider (HP Insight Management WBEM Provider) for
Windows
◦
Install Simple Network Management Protocol Agent (HP Insight Management
Agents) for Windows
◦
Install Linux PSP or ESX Agents
◦
Install the HP Version Control for Windows
Use the following credentials for all systems.
In the User name field, enter the system administrator name.
In the Password field, enter the system administrator password.
In the Password (Verify) field, re-enter the system administrator password.
In the Domain (Optional) field, if you are using a domain account, enter the Windows
domain.
2.
Click Run Now or click Schedule to run this task at a later time. The Task Results page appears.
If the Management HTTP Server is installed on target systems, the login credentials are updated
in the Management HTTP Server password file. As with other HP SIM tools, you can configure
the Configure or Repair Agents tool to run on a schedule or manually. Only one instance of
Configure or Repair Agents tool can run at a time.
The Configure or Repair Agents tool can update multiple target systems. The log results indicate
whether the repair attempt was successful. For Configure or Repair Agents, the Task Results
page displays the following information.
Table 42 CRA Task Results information
Field Name
Description
Status
This field displays the details for each target system
within a task instance.
Exit Code
This field represents the success or failure of an
executable program. If the return value is zero or a
positive value, the executable ran successfully. If a
negative value is returned, the executable failed. This
exit code does not indicate that all configuration
attempts were successful. It is possible for some to
succeed but some to fail.
Target Name
This field displays the name/IP address of the target.
The stdout tab
This tab displays the output text information.
The stderr tab
This tab displays information if the executable
experienced an error.
View Printable Report
You can print reports for the selected target system or
for all target systems associated with the task instance.
To print a report:
a. Click View Printable Report.
An Options Message box appears.
b. Select a report.
c. Click OK to display the report, or click Cancel to
return to the View Task Results page.
Configuring managed systems from an HP-UX CMS
Overview
Managed systems must be able to communicate status to the HP SIM CMS in order to launch
commands to the managed systems. To configure the managed systems to communicate with the
CMS, you must configure common configurations and trust relationships. The Configure or Repair
Agents feature enables you to configure or repair agents in Windows, Linux, and HP-UX.
The Configure or Repair Agents tool enables you to repair Simple Network Management Protocol
settings and trust relationships that exist between HP Systems Insight Manager and target systems
if you have Insight Management Agents 7.2 or later installed. If you have Insight Management
Agents 7.1 or earlier installed, you can update Web Agent passwords on target systems.
This tool adds the security and trap community strings and trust settings to the target systems, but
it does not replace existing settings. To replace existing settings on target systems, use the Replicate
Agent Settings feature in HP SIM.
You can use Configure or Repair Agents tool to send test SNMP traps from Windows systems with
Insight Management Advisors and send test Web-Based Enterprise Management indications from
Windows and HP-UX systems with HP WBEM provider installed.
Configuring managed systems from an HP-UX CMS 365
You can also configure WBEM certificates for HP-UX systems.
Configuring or repairing the agents
To run Configure or Repair Agents remotely against a system, you must have authorizations to run
the Configure or Repair Agents tool. You must have root privileges on the Central Management
Server (CMS) to modify the HP SIM community strings in the CMS security file. In addition, you
must have root privileges for HP-UX on the target systems to configure or repair the agent settings.
Click Next to proceed to the Step 3: Configure or Repair Agents Settings page.
Related Topics
Configuring managed systems from a Windows CMS
Configuring managed systems from a Linux CMS
366 Operations
Configuring target system settings
Configuring managed systems from an HP-UX CMS 367
1.
Configure the target systems by selecting one of the following options:
•
Configure WBEM / WMI. This section enables you to configure the target Linux, Windows,
or HP-UX system to send WBEM indications or events to HP SIM.
For this section, consider the following:
◦
Create subscription to WBEM events so that WBEM events will be sent to the CMS
◦
Send a sample WBEM / WMI indication to this instance of HP SIM to test that events
appear in HP SIM in the Event List or All Event User Interface for the selected system
NOTE:
SIM.
This indication will appear as an Informational Event in the Event List of HP
NOTE: This indication is supported only on HP-UX and Windows targets with
WBEM provider installed.
◦
Use an HP SIM WBEM certificate (good for 10 years) rather than
username/password to manage the system
This option deploys a WBEM certificate to the managed system and is only valid for
HP-UX systems.
◦
Configure a nonadministrative account for HP SIM to access WMI data
This option applies to Windows systems with HP WBEM providers. The configuration
of the managed system updates to allow the specified user to access WMI information
over the network. HP SIM uses this user to read inventory and configuration
information from the system and is configured as the WBEM user in the System
Credentials. If HP SIM is configured with a user with administration rights, this
configuration step is not necessary. HP SIM does not create this user. The user already
exists as either a domain user or one local to the managed system.
The user is added to the DCOM Users group on the managed system and has
read-only access to WMI information, and read-write permissions to the HPQ name
space. This user does not need to be an administrator of the managed system or
have sign-in rights. The domain administrator should create a special domain account.
To enter the credentials for HP SIM to use to access the managed systems:
1. In the User name field, enter a user name.
2. In the Password field, enter the password.
3. In the Password (Verify) field, re-enter the password exactly as it was entered
in the Password field.
4. In the Domain (Optional) field, if the target belongs to a Domain, enter the
Windows domain.
If configuration of a nonadministrative user is successful, then these credentials
are saved as the System Credentials for WBEM access in HP SIM.
•
Configure SNMP
This section enables you to configure SNMP settings.
a. Select Set read public community string to specify a community string. By default,
the first HP SIM community string that is not public appears. If no community string
exists in HP SIM, you must enter one.
NOTE: If you configure only HP-UX systems with default SNMP installations, you
do not need to set this option. HP-UX enables read by default (get-community-name
is set to public by default on HP-UX systems).
368 Operations
NOTE: If you select this option, the Read Only community string is added to the
target systems. If the target system is SuSE Linux or Microsoft Windows 2003, the
managed systems do not always enable SNMP communication between themselves
and a remote host. This setting is modified to enable the instance of the HP SIM
system to communicate using SNMP with these target systems.
NOTE:
You can enter a community string up to 255 characters.
NOTE: Repairing the SNMP settings adds a Read Write community string to the
target system only if one does not currently exist. This community string is unique for
each system, is composed of over 30 characters to include letters and numbers, and
is visible only to the user with administrator privileges for that system. This Read Write
community string is required by the Web Agent to perform certain threshold setting
capabilities. This community string is used locally only on the target system and is
not used by HP SIM over the network. Linux and HP-UX systems do not require a
Read Write community string. The Read Write community string is added on Windows
systems only.
b.
c.
Select Set traps to refer to this instance of HP Systems Insight Manager in the target
systems SNMP Trap Destination List. This setting enables the target systems to send
SNMP traps to this instance of HP SIM.
Select Send a sample SNMP trap to this instance of the HP SIM to test that events
appear in HP SIM event lists to verify that SNMP events appear in the HP SIM events
list.
To successfully send a test trap, you must configure target systems to send a trap to
this instance.
NOTE: You can send a test trap only from a managed system with an Insight
Management Advisor installed.
NOTE: The trap from Windows appears as a Generic Trap from the system and
is listed as a Major Event in the Event List of HP SIM. The trap received from Linux
and HP-UX targets appears as a Cold Trap and is listed as Informational Events in
the Event List of HP SIM.
•
Configure secure shell (SSH) access
Select this option to configure SSH access on managed systems.
If you select this option, you must select one of the following options:
◦
Host based authentication for SSH
NOTE: For this option to work, the user name and password provided in Step 4:
Enter credentials must be an administrative level account. For Linux or HP-UX targets,
it must be the root account and password.
◦
Each user has to be authenticated on the managed system
NOTE: If you do not want all users that have sign-in access to HP SIM to run the
tool and you would like to control which users need to have access, this option is
more secure.
NOTE:
gure SSH only if the OpenSSH service is running on the managed systems.
Configuring managed systems from an HP-UX CMS 369
•
Set Trust relationship to "Trust by Certificate"
Select this option to configure systems to use the Trust by Certificate trust relationship with
the HP SIM.
For HP SIM on the target systems, this option sets the trust mode to Trust by Certificate
and copies the HP SIM system certificate to the target system trusted certificate directory.
This option enables HP SIM users to connect to the HP SMH using the certificate for
authentication.
You can configure SSO to management processors for Onboard Administrator and for
remote management. To configure SSO, select Set Trust Relationship. After you configure
SSO, you are not continually prompted to supply the login credentials for the management
processor.
NOTE: For systems with Management HTTP Server 5.x and earlier, the Configure or
Repair Agents setting adds the Administrator password in the Management HTTP Server
store and modifies the SNMP settings, but it cannot change trust relationship information.
Select the checkbox beside Import Secure Sockets Layer (SSL) certificate for HP SIM to
trust the HP SMH of the managed system. This option is only valid for HP-UX and Linux
operating systems.
•
Configure HP Version Control Agent
Select this option to configure the HP VCA to point to the Version Control Repository
Manager, where the repository of software and firmware is located, enabling version
comparison and software updates. This option is available for Windows and Linux systems.
To configure HP VCA:
1. In the Select the system where the HP VCRM is installed field, select a server from the
dropdown list.
2. In the User Name field, enter the user name to access the HP VCRM. This user cannot
be the default administrator user, and must have administrative privileges.
3. In the Password field, enter the password to access the HP VCRM.
4. In the Password (verify) field, re-enter the password for the HP VCRM.
•
Set administrator password for Insight Management Agents 7.1 or earlier
Select this option to repair the administrator password on all Insight Management Agents
installed on the target systems as applicable for Windows and Linux systems.
NOTE: Do not set this option if you have Insight Management Agents 7.2 or later
installed.
NOTE: If the remote system is running HP-UX, this option is not executed on the remote
system because it is not applicable on HP-UX systems. If you are configuring only HP-UX
target systems, you do not need to set this option.
If you select this option, you must complete the following steps:
a. In the Password field, enter the new administrator password.
b. In the Password (verify) field, re-enter the new administrator password.
2.
Click Next. The Step 4: Enter credentials page appears.
Configuring credentials
The credentials specified on this page are for a privileged account on the target system.
370 Operations
1.
Enter the following credentials.
The credentials used in this step must work for all selected target systems. HP recommends
using domain administrator credentials. Credentials entered here are not saved by HP SIM
except to run a scheduled task later.
If you select Configure secure shell (SSH) access for a Windows target system, the account you
specify must be a member of the local Administrators group. For Windows targets using a
domain account, the account is automatically added to this group.
a. Select one of the following options:
•
•
b.
c.
d.
e.
Use sign-in credentials These credentials must be a privileged account on the managed
system. The sign-in credentials option is available if the following options are selected:
◦
Install WBEM/WMI Provider (HP Insight Management WBEM Provider) for
Windows
◦
Install Simple Network Management Protocol Agent (HP Insight Management
Agents) for Windows
◦
Install Linux PSP or ESX Agents
◦
Install the Version Control Repository Manager for Windows
Use the following credentials for all systems.
In the User name field, enter the system administrator name.
In the Password field, enter the system administrator password.
In the Password (Verify) field, re-enter the system administrator password.
In the Domain (Optional) field, if you are using a domain account, enter the Windows
domain.
Configuring managed systems from an HP-UX CMS
371
2.
Click Run Now or click Schedule to run this task at a later time. The Task Results page appears.
If the Management HTTP Server is installed on target systems, the login credentials are updated
in the Management HTTP Server password file. As with other HP SIM tools, you can configure
the Configure or Repair Agents tool to run on a schedule or manually. Only one instance of
Configure or Repair Agents tool can run at a time.
The Configure or Repair Agents tool can update multiple target systems. The log results indicate
whether the repair attempt was successful. For Configure or Repair Agents, the Task Results
page displays the following information.
Table 43 CRA Task Results information
Field Name
Description
Status
This field displays the details for each target system
within a task instance.
Exit Code
This field represents the success or failure of an
executable program. If the return value is zero or a
positive value, the executable ran successfully. If a
negative value is returned, the executable failed. This
exit code does not indicate that all configuration
attempts were successful. It is possible for some to
succeed but some to fail.
Target Name
This field displays the name/IP address of the target.
The stdout tab
This tab displays the output text information.
The stderr tab
This tab displays information if the executable
experienced an error.
View Printable Report
You can print reports for the selected target system or
for all target systems associated with the task instance.
To print a report:
a. Click View Printable Report.
An Options Message box appears.
b. Select a report.
c. Click OK to display the report, or click Cancel to
return to the View Task Results page.
Custom tools
Custom tools are executed on the CMS and on target systems. They can be scripts, batch files, or
executables that can reference environment variables set by the tool in order to access system or
event information. For example, creating a custom tool to launch Notepad. You can create or
launch SSA, MSA, and WLA tools. You can create the following types of custom tools:
•
Remote tool
A tool that runs on selected target systems. It might copy files to the target systems or run
specific X-Window applications on the target systems. You can schedule this tool.
•
CMS tool
A tool that runs on the CMS. It is usually a script or batch file and can pass in environment
variables. Using Automatic Event Handling, you can configure this tool to run when events
are received. You can schedule this tool.
•
Web page tool
A tool that launches a web URL. The URL is launched in a separate browser window on the
CMS. You cannot schedule this tool.
372 Operations
Remote tools require environment variables, which are parameters passed to the launched
application to make it perform as expected. The launch command string includes system variables
and user-defined variables for your application. For example, you could pass an environment
variable that runs a script to check on the status of your mail server.
DOS environment variables are supported in custom tool parameters and work as parameters on
the New Custom Tool page or the Manage Custom Tools page. Unless you use DOS environment
variables in a batch or script file, you must surround them with double percent (%) signs. For
example, to pass in the NOTICELABEL environment variable as a parameter on the parameter line,
enter %%NOTICELABEL%%. If you use DOS environment variables in a batch file or script file, use
only a single percent (%) sign before and after the environment variable name. For a list of other
substitutable environment variables, see the HP Systems Insight Manager User Guide, at http://
www.hp.com/go/insightmanagement/sim/docs.
Custom tools you create appear under Tools→Custom Tools menu option.
You have multiple scheduling options. For more information about scheduling options, see
Scheduling a task.
IMPORTANT: The application must be able to execute in the security context provided to HP SIM
(the default is LocalSystem).
•
New Custom Tools
Select Tools→Custom Tools→New Custom Tool. The New Custom Tool page appears.
•
Manage Custom Tools
Select Tools→Custom Tools→Manage Custom Tools. The Manage Custom Tools page appears.
Use custom tools that run on target SSA systems create a temporary .XML tool definition file under
/var/tmp, the loads the tool with the mxtool -affilename. You enter only data in required
fields.
WARNING!
If you define a custom tool to run as root, any user authorized to run the tool might
gain full access to the managed system, depending on how you define the command, and what
its capabilities are. Otherwise, the tool runs as the HP SIM user and that user's SSH public key
must be configured on the managed system using the mxagentconfig command.
Custom tools 373
Menu placement
To place custom tools in the following menu locations, use a string in the form
base|submenu|subsubmenu.
Menu level
Example
top-level-menu
Tools
top-level-menu|first-level-cascade
Tools|Custom Tools
top-level-menu|first-level-cascade|second-level-cascade Tools|Custom Tools|My Tools
For example, place a tool under Tools→Custom Tools, place an entry in the Menu placement field
such as Tools|CustomTools.
By default, if the Menu placement field is left blank, the tools are placed in Tools→Custom Tools.
Managing custom tools
Use the Manage Custom Tools page to view and manage custom tools created through the New
Custom Tool feature. The Manage Custom Tools page displays a table listing the custom tools and
information on each tool. The table includes:
•
Selection column
•
Name
•
Description
•
Command
•
Run as user
•
Automatic Event Handling
New
Use create a custom tool and open the Select the tool to create page.
Edit
Use to edit an existing custom tool. Select the tool, and then click Edit. The Edit Custom Tool Details
section appears. You can edit all fields and add or delete environment variables.
View tool definition
Use to display the XML code for the tool. This tool is not enabled if you select more than one tool.
Run Now/Schedule
Use to run the tool immediately or to schedule the tool to run (if the tool can be scheduled). If the
tool can be run, the schedule a task page appears. You can schedule when and how often the
tool runs.
For more information, see Scheduling a task or Running a scheduled task.
Delete
Use to delete a tool. Deleting a tool removes it from the Manage Custom Tools page and from the
system. If a tool is dependent on a task, an alert appears with the list of tasks associated with the
tool.
374
Operations
Creating a remote tool
Procedure 237 Creating a remote tool
1.
Under Tool Parameters, enter the following information:
a. In the Name field, enter the command name. Custom tool names must be at least one
character, and not more than 255 characters in length. The first character of the name
must be alphabetic. Subsequent characters can be letters, digits, spaces, or any of the
following: "-", ".", "(", ")" or "_".
b. In the Description field, enter the information for the tool.
c. In the Help comments field, enter comments for the tool.
d. In the Menu placement field, enter the full path (from the root of the Systems Insight
Manager console) and the file name of the tool (for example, c:\custom code\
romflash.bat).
2.
Specify the user account on the target system by selecting one of the following options:
•
Logged-in user
The tool uses the user account that is logged in.
•
Special user
For UNIX and Linux systems, root; for Windows systems, Administrator. The tool does not
run on targets with an unknown operating system.
•
Specific user
The tool uses the specified user account.
3.
Specify the maximum number of targets that the tool can select when creating the task by
selecting from the following:
•
None
If you select None, the target selection page does not appear.
•
One
If you select One, the tool runs on only one target system.
•
Unlimited
If you select Unlimited, the tool can run on multiple target systems.
4.
Select Copy files to the target systems.
a. (Optional) To delete a specified file, select a file and click Delete.
b. (Optional) To add additional files, click Add.
5.
In the Command with parameters field, enter parameters.
The interface supports nine parameters. If you enter more than nine parameters, the last
parameter appears as Zero(0) on the Task Results page.
6.
Under Command output format, select from the following:
•
Standard output
•
X-Window
7.
To prompt the user for input when they choose this tool to be run or scheduled, enter up to
10 labels that can be used to ask for input. You can use the substitution parameters %1 through
%10 in your command line to access the values they enter.
a. (Optional) To require the user to enter data, select Required (user must enter data).
b. (Optional) To mask the user input, select Private (masks the data with *).
8.
Select if the tool can be scheduled.
Custom tools 375
9.
Click OK to add the tool to the Custom Tools menu and access the Manage Custom Tools
page, or click Previous to return to the previous page to select another type of custom tool.
NOTE:
New custom tool tools are located under Tools→Custom Tools.
Editing a remote tool
Procedure 238 Editing a remote tool
1.
Under Tool Parameters, enter the following information:
a. In the Name field, enter the command name. Custom tool names must be at least one
character, and not more than 255 characters in length. The first character of the name
must be alphabetic. Subsequent characters can be letters, digits, spaces, or any of the
following: "-", ".", "(", ")" or "_".
b. In the Description field, enter the information for the tool.
c. In the Help comments field, enter comments for the tool.
d. In the Menu placement field, enter the full path (from the root of the Systems Insight
Manager console) and the file name of the tool (for example, c:\custom code\
romflash.bat).
2.
Specify the user account on the target system by selecting one of the following options:
•
Logged-in user
The tool uses the user account that is logged in.
•
Special user
For UNIX and Linux systems, root; for Windows systems, Administrator. The tool does not
run on targets with an unknown operating system.
•
Specific user
The tool uses the specified user account.
3.
Specify the maximum number of targets that the tool can select when creating the task by
selecting from the following:
•
None
If you select None, the target selection page does not appear.
•
One
If you select One, the tool runs on only one target system.
•
Unlimited
If you select Unlimited, the tool can run on multiple target systems.
4.
Select Copy files to the target systems.
a. (Optional) To delete a specified file, select a file and click Delete.
b. (Optional) To add additional files, click Add.
5.
In the Command with parameters field, enter parameters.
The interface supports nine parameters. If you enter more than nine parameters, the last
parameter appears as Zero(0) on the Task Results page.
6.
Under Command output format, select from the following:
•
Standard output
•
X-Window
376 Operations
7.
To prompt the user for input when they choose this tool to be run or scheduled, enter up to
10 labels that can be used to ask for input. You can use the substitution parameters %1 through
%10 in your command line to access the values they enter.
a. (Optional) To require the user to enter data, select Required (user must enter data).
b. (Optional) To mask the user input, select Private (masks the data with *).
8.
9.
Select if the tool can be scheduled.
Click OK to add the tool to the Custom Tools menu and access the Manage Custom Tools
page, or click Previous to return to the previous page to select another type of custom tool.
NOTE:
New custom tool tools are located under Tools→Custom Tools.
Creating a CMS tool
Procedure 239 Editing a CMS tool
1.
Under Tool Parameters, enter the following information:
a. In the Name field, enter the command name. Custom tool names must be at least one
character, and not more than 255 characters in length. The first character of the name
must be alphabetic. Subsequent characters can be letters, digits, spaces, or any of the
following: "-", ".", "(", ")" or "_".
b. In the Description field, enter the information for the tool.
c. In the Help comments field, enter comments for the tool.
d. In the Menu placement field, enter the full path (from the root of the Systems Insight
Manager console) and the file name of the tool (for example, c:\custom code\
romflash.bat).
2.
Specify the user account on the target system by selecting one of the following options:
•
Logged-in user
The tool uses the user account that is logged in.
•
Special user
For UNIX and Linux systems, root; for Windows systems, Administrator. The tool does not
run on targets with an unknown operating system.
•
Specific user
The tool uses the specified user account.
3.
In the Command with parameters field, enter parameters.
The interface supports nine parameters. If you enter more than nine, the last parameter appears
as Zero(0) on the Task Results page.
4.
Optional: Enter the Environment variables for the tool and add or delete variables as needed.
For a list of variables available from Systems Insight Manager, see the HP SIM Command Line
Interface Reference Guide at http://www.hp.com/go/insightmanagement/sim/docs.
•
Optional: To delete a specified variable, click Delete.
•
Optional: To add additional variables, click Add.
DOS environment variables are supported in custom tool parameters and work as parameters
on the New Custom Tool page or the Manage Custom Tools page. Unless you use DOS
environment variables in a batch or script file, you must surround them with double percent
(%) signs. For example, to pass in the NOTICELABEL environment variable as a parameter on
the parameter line, enter %%NOTICELABEL%%. If you use DOS environment variables in a
batch file or script file, use only a single percent (%) sign before and after the environment
variable name. For a list of other substitutable environment variables, see the HP Systems
Insight Manager User Guide at http://www.hp.com/go/insightmanagement/sim/docs.
Custom tools 377
5.
6.
If you can schedule the tool, select Tool can be scheduled.
Click OK to add the new tool to the Custom Tools menu and access the Manage Custom Tools
page, or click Previous to return to the previous page to select another type of custom tool.
NOTE:
New custom tool tools are located under Tools→Custom Tools.
Editing a CMS tool
Procedure 240 Editing a CMS tool
1.
Under Tool Parameters, enter the following information:
a. In the Name field, enter the command name. Custom tool names must be at least one
character, and not more than 255 characters in length. The first character of the name
must be alphabetic. Subsequent characters can be letters, digits, spaces, or any of the
following: "-", ".", "(", ")" or "_".
b. In the Description field, enter the information for the tool.
c. In the Help comments field, enter comments for the tool.
d. In the Menu placement field, enter the full path (from the root of the Systems Insight
Manager console) and the file name of the tool (for example, c:\custom code\
romflash.bat).
2.
Specify the user account on the target system by selecting one of the following options:
•
Logged-in user
The tool uses the user account that is logged in.
•
Special user
For UNIX and Linux systems, root; for Windows systems, Administrator. The tool does not
run on targets with an unknown operating system.
•
Specific user
The tool uses the specified user account.
3.
In the Command with parameters field, enter parameters.
The interface supports nine parameters. If you enter more than nine, the last parameter appears
as Zero(0) on the Task Results page.
4.
Optional: Enter the Environment variables for the tool and add or delete variables as needed.
For a list of variables available from Systems Insight Manager, see the HP Systems Insight
Manager Command Line Interface Guide at http://www.hp.com/go/insightmanagement/
sim/docs.
•
Optional: To delete a specified variable, click Delete.
•
Optional: To add additional variables, click Add.
DOS environment variables are supported in custom tool parameters and work as parameters
on the New Custom Tool page or the Manage Custom Tools page. Unless you use DOS
environment variables in a batch or script file, you must surround them with double percent
(%) signs. For example, to pass in the NOTICELABEL environment variable as a parameter on
the parameter line, enter %%NOTICELABEL%%. If you use DOS environment variables in a
batch file or script file, use only a single percent (%) sign before and after the environment
variable name. For a list of other substitutable environment variables, see the HP Systems
Insight Manager User Guide at http://www.hp.com/go/insightmanagement/sim/docs.
5.
6.
If you can schedule the tool, select Tool can be scheduled.
Click OK to add the new tool to the Custom Tools menu and access the Manage Custom Tools
page, or click Previous to return to the previous page to select another type of custom tool.
NOTE:
378 Operations
New custom tool tools are located under Tools→Custom Tools.
Creating a web page tool
Use this tool to create a tool that integrates a web application or website. All tools are automatically
launched into a separate browser window. For example, to add a path to the HP website, add
the URL: http://hp.com. To add a link to the site on a selected system, add a URL such as:
https://%n:2381. The target system is substituted for the %n when the tool is launched. The
resulting command launches the HP SMH on the target system. This tool creates a temporary XML
tool definition file in /var/tmp and then loads it with the command mxtool -affilename. You
only need to enter data into the required fields.
Procedure 241 Creating a web page tool
The Describe how the new custom tool will work page enables you to define the tool type and a
provide a description of the tool.
1. Under Tool Parameters, enter the following information:
a. In the Name field, enter the command name. Custom tool names must be at least one
character, and not more than 255 characters in length. The first character of the name
must be alphabetic. Subsequent characters can be letters, digits, spaces, or any of the
following: "-", ".", "(", ")" or "_".
b. In the Description field, enter the information for the tool.
c. In the Help comments field, enter comments for the tool.
d. In the Menu placement field, enter the full path (from the root of the Systems Insight
Manager console) and the file name of the tool (for example, c:\custom code\
romflash.bat).
2.
Specify the user account on the target system by selecting one of the following options:
•
Logged-in user
The tool uses the user account that is logged in.
•
Special user
For UNIX and Linux systems, root; for Windows systems, Administrator. The tool does not
run on targets with an unknown operating system.
•
Specific user
The tool uses the specified user account.
3.
Specify the maximum number of targets the tool can select when creating the task. Select from
the following:
•
None
If you select None, the target selection page does not appear.
•
One
If you select One, the target selection page appears.
•
Unlimited
If you select Unlimited, the tool can be run on multiple target systems.
4.
5.
6.
Enter the URL to the site or application to launch.
Enter the format of how target systems are passed to the URL.
Click OK to add the new tool to the Custom Tools menu and access the Manage Custom Tools
page, or click Previous to return to the previous page to select another type of custom tool.
NOTE:
New custom tool tools are located under Tools→Custom Tools.
Custom tools 379
Editing a web page tool
Procedure 242 Editing a web page tool
1.
Under Tool Parameters, enter the following information:
a. In the Name field, enter the command name. Custom tool names must be at least one
character, and not more than 255 characters in length. The first character of the name
must be alphabetic. Subsequent characters can be letters, digits, spaces, or any of the
following: "-", ".", "(", ")" or "_".
b. In the Description field, enter the information for the tool.
c. In the Help comments field, enter comments for the tool.
d. In the Menu placement field, enter the full path (from the root of the Systems Insight
Manager console) and the file name of the tool (for example, c:\custom code\
romflash.bat).
2.
Specify the user account on the target system by selecting one of the following options:
•
Logged-in user
The tool uses the user account that is logged in.
•
Special user
For UNIX and Linux systems, root; for Windows systems, Administrator. The tool does not
run on targets with an unknown operating system.
•
Specific user
The tool uses the specified user account.
3.
Specify the maximum number of targets the tool can select when creating the task. Select from
the following:
•
None
If you select None, the target selection page does not appear.
•
One
If you select One, the target selection page appears.
•
Unlimited
If you select Unlimited, the tool can be run on multiple target systems.
4.
5.
6.
Enter the URL to the site or application to launch.
Click OK to add the new tool to the Custom Tools menu and access the Manage Custom Tools
page, or click Previous to return to the previous page to select another type of custom tool.
Enter the format of how target systems are passed to the URL.
NOTE:
New custom tool tools are located under Tools→Custom Tools.
Viewing a tool definition
Procedure 243 Viewing tool definition
1.
2.
Select Tools→Custom Tools→Manage Custom Tools. The Manage Custom Tools page appears.
Select a tool, and then click View Tool Definition The XML code appears.
Deleting a custom tool
Procedure 244 Deleting a custom tool
1.
2.
3.
Select Tools→Custom Tools→Manage Custom Tools. The Manage Custom Tools page appears.
Select a tool, and then click Delete. A confirmation box appears.
Click OK to delete the tool or click Cancel to cancel the deletion process.
380 Operations
Removing and restoring custom tools
Remove a Tool removes a tool from the menu for all users in HP SIM. The tool name must match
the name in the tool definition file.
CAUTION:
This tool can remove any tool, including tools supplied by HP.
Procedure 245 Removing a tool from HP SIM
1.
2.
Under Parameters, add information using standard tool parameters. Tool name is the only
required field.
Click Run Now to run the task immediately, or click Schedule to schedule when the task runs.
For more information about scheduling a task, see Scheduling a task.
To remove tools using the command line, enter
mxtool -r -t badtool
Replace badtool with the name of the tool you want to delete. For more information, see the
mxtool command in the HP Systems Insight Manager 7.2 Command Line Interface Guide, at http://
www.hp.com/go/insightmanagement/sim/docs.
Restoring a tool
To restore a tool using the command line, enter:
mxtool -a -f /home/user1/defs/mytooldef
Replace /home/user1/defs/ with the folder of the user restoring the tool and mytooldef with
the tool to be restored. For more information, see the mxtool command in the HP Systems Insight
Manager 7.2 Command Line Interface Guide, at http://www.hp.com/go/insightmanagement/
sim/docs.
Related information
Related procedures
Creating a CMS tool
Editing a CMS tool
Creating a remote tool
Editing a remote tool
Creating a web page tool
Editing a web page tool
Removing and restoring custom tools
Deleting a custom tool
Viewing a tool definition
Related topic
Custom tools
Setting disk thresholds
Procedure 246 Setting a disk threshold task
1.
2.
3.
Select Configure→Disk Thresholds→Set Disk Thresholds. The Set Disk Thresholds page appears.
Select target systems, and then click Next. For more information, see Creating a task.
In the Specify the disk thresholds to be set on target systems section, enter the following
information:
Related information 381
Table 44 Disk thresholds
Threshold
4.
Explanation
Critical Disk Percent Usage Threshold
This can never go higher than 99% or lower than a
warning threshold plus 3%. Therefore, if the warning
threshold is 85%, the valid range for the critical
threshold is 88% to 99%.
Reset Critical Disk Percent Usage Threshold
This must drop below the reset value before the threshold
is rearmed. This setting prevents the threshold from being
sent multiple times if the variable fluctuates near the
threshold value.
Warning Disk Percent Usage Threshold
This must be less than the critical threshold. A warning
threshold must drop below the reset value before the
warning threshold is rearmed. This setting prevents the
threshold from being sent multiple times if the variable
fluctuates near the threshold value. The minimum
difference between the value and the reset value must
be greater than or equal to 2%.
Reset Warning Disk Percent Usage Threshold
This can never be higher than the critical threshold minus
3%. For example, if the critical threshold is 95%, the
valid range for the warning threshold is 6% to 92%.
When you save the thresholds, disabled thresholds are
deleted.
Agent Polling Interval
This value is the polling interval in seconds that
determines how often the agents check if current values
exceed the threshold. A common value is 120 seconds.
Click Previous to return to the previous page, click Schedule to schedule when the task runs,
or click Run Now to run the task immediately. The Task Results page appears. See Scheduling
a task for more information about scheduling the task.
Related procedure
Creating a task to delete disk thresholds
Creating a task to delete disk thresholds
The following example describes the necessary steps to set up a task that removes all disk thresholds
from the HP SIM database monthly.
Procedure 247 Creating the task
1.
2.
3.
4.
5.
6.
7.
8.
9.
Select Configure→Disk Thresholds→Remove All Disk Thresholds. The Remove All Disk Thresholds
page appears.
From the Add targets by selecting dropdown list, select All Servers.
Select the Select "All Servers" itself checkbox.
Click Apply.
Click Schedule.
In the Task name field, enter a name for the task, such as Delete Disk Thresholds
Monthly.
Under When would you like this task to run? section, select Periodically.
In the Refine schedule section, select every month and then select a day for the task to run.
Click Done.
Related procedures
Setting disk thresholds
382 Operations
License manager
NOTE: To run License Manager, you must have administrative rights on the CMS (to set, select
Options+Security→Users and Authorizations→User) and choose the Configure CMS Security option,
and the All Tools toolbox (to set, select Options+Security→Users and Authorizations→User) on the
managed systems that you want to license.
To access License Manager, select Deploy→License Manager.... The Product License Information
table appears.
Table 45 License Manager options
Name
Description
Related Information
Procedure
Licensed System(s)...
Systems Insight Manager
Licensed System(s)...
enables you to view a list of
systems licensed for the
selected product.
Viewing licensed systems
Add Licenses...
Systems Insight Manager
Add Licenses...
enables you to add
individual license keys to the
License Manager database.
Adding licenses individually
Manage Licenses...
The Manage Licenses feature Manage Licenses...
enables you to manage
licenses for the product
selected in the Product
License Information table.
Licenses can originate from
direct user input or from
license information collected
using Collect Remote License
Info....
See Managing licenses
Collect Remote License
Info...
Collect Remote License
Info...
Assign License(s)...
Systems Insight Manager
Assign License(s)...
enables you to assign and
un-assign product licenses
for plug-ins, if applicable for
that plug-in, and to assign
licenses to remote target
systems when licenses are
managed remotely. For
plug-ins, when assigning
licenses, note the following
for non-management
processor targets:
See Assigning a license or
Apply a license
Un-Assign Licenses...
An assigned license can be Un-Assign Licenses...
unassigned from one system
and assigned to another
system, as long as the
product enabled by the
license has not consumed
the license. When a product
has been used on a system,
the license is locked to that
system permanently. Licenses
delivered directly to the
actual target system cannot
be unassigned. There is no
penalty for having these
licenses remain on those
systems because they are
See Un-assigning a license
See Collect Remote License
Info...
License manager 383
Table 45 License Manager options (continued)
Name
Description
Related Information
Procedure
consumed on an as-needed
basis. The remaining
licenses can be used
elsewhere.
Apply Licenses
Apply a license to a system
must be treated as
irreversible. The license is
locked to the specified
system.
Apply Licenses
CLI mxlmkeyconfig
The CLI mxlmkeyconfig
CLI mxlmkeyconfig
allows you to combine all
the License Manager key
files into one file instead of
having to execute multiple
files. Combining these files
into a single file makes it
easier when adding keys
from a file through the
License Manager Graphical
user interface (GUI).
See Assigning a license or
Apply a license.
See mxlmkeyconfig CLI.
Related information
Viewing licensed systems
HP Systems Insight Manager enables you to view a list of systems licensed for the selected product.
Although a target can be licensed to use a product, the product license might not appear in the
interface or report. Products can elect to not display all or some licensing details.
NOTE: To run License Manager, you must have administrative rights on the CMS (to set, select
Options+Security→Users and Authorizations→User) and choose the Configure CMS Security option,
and the All Tools toolbox (to set, select Options+Security→Users and Authorizations→User) on the
managed systems that you want to license.
Procedure 248 View licensed systems
1.
2.
3.
To access License Manager, select Deploy→License Manager.... The Product License Information
table appears.
Select a product from the Product License Information table.
Click Licensed Systems.... The License Collection Results page appears. For more information,
see License Collection Results table.
The list of licensed systems for the selected product is populated in the License Collection Results
page. You can click a column header to sort the list based on the entries in that column.
Related information
Managing licenses
Procedure 249 Manage Licenses
1.
2.
To access License Manager, select Deploy→License Manager.... The Product License Information
table appears.
From the Product License Information page, select a product.
384 Operations
3.
Click Manage Licenses.... The Manage Licenses:Licenses currently available for Virtual Machine
Management page appears.
The License Manager window is updated with information about the available licenses for the
selected product. For more information, see Manage Licenses...
4.
Select a license category, and then click one of the following buttons:
•
Assign Licenses...
Assign available licenses to systems. For more information, see Assigning a license or
Apply a license.
•
Un-Assign Licenses...
Un-assign licenses from systems. For more information, see Un-assigning a license.
To manage licenses,
NOTE: To run License Manager, you must have administrative rights on the CMS (to set, select
Options+Security→Users and Authorizations→User) and choose the Configure CMS Security option,
and the All Tools toolbox (to set, select Options+Security→Users and Authorizations→User) on the
managed systems that you want to license.
Related information
Adding licenses individually
NOTE: To run License Manager, you must have administrative rights on the CMS (to set, select
Options+Security→Users and Authorizations→User) and choose the Configure CMS Security option,
and the All Tools toolbox (to set, select Options+Security→Users and Authorizations→User) on the
managed systems that you want to license.
Procedure 250 Add license individually
1.
2.
3.
4.
5.
To access License Manager, select Deploy→License Manager.... The Product License Information
table appears.
Click Add Licenses.... The Add License: section appears.
Enter one of the following:
•
The key string by typing it into the five fields as individual characters (five per field). The
cursor advances to the next field when the current field is full as you enter the key code
starting from the left-most box.
•
The key by pasting the entire key into one of the five input fields. For example, if you
received a key as text in an e-mail.
Click Process. The Key details: page appears.
Click Add Licenses Now to add the new licenses to the database. If the licenses are added
successfully, they are listed in the Product License Information section. An error message
appears if the key is invalid, and that license information is not added to the database.
If the license addition is successful, a new page appears displaying the product the key belongs
to.
The table is refreshed with the newly added license row selected.
6.
Click Back if the licenses displayed is not the product license you wanted added. The Add
License section appears.
Adding licenses from a file
HP SIM enables you to add keys to the License Manager database by importing license keys that
are defined in an XML file with a .key extension.
License manager 385
Management processor product license keys can be added into the database because they can
be deployed directly to management processors.
NOTE:
You cannot enter some types of valid keys if the key already exists in the database.
NOTE: To run License Manager, you must have administrative rights on the CMS (to set, select
Options+Security→Users and Authorizations→User) and choose the Configure CMS Security option,
and the All Tools toolbox (to set, select Options+Security→Users and Authorizations→User) on the
managed systems that you want to license.
Procedure 251 Add license from a file
1.
2.
3.
4.
5.
6.
To access License Manager, select Deploy→License Manager.... The Product License Information
table appears.
Click Add License... The Add Licenses section appears at the bottom of the page. For more
information, see Add License page.
Choose one of the following:
•
Enter the full path and file name in the Specify a file name and path field.
•
Click Browse... to select the desired file. For more information, see Add License page.
When the full path and file name appear in the Specify a file name and path field, click Process
to open the file. The contents of the license key file appear. For more information, see Keys
from file:.
Select license(s) to be added.
Click Add Licenses Now to add the keys to the database.
The page is refreshed and any invalid keys are deactivated.
7.
Click Back if the licenses displayed is not the product license you wanted added. The Add
License section appears.
After successfully adding the keys to the database, the Product License Information table is
refreshed to display the updated license status in HP SIM.
Creating a license file
License keys are defined in an XML file with a .key extension. You can create these files. The
format is as follows.
<?xml version="1.0" encoding="UTF-8"?>
<KEYLIST>
<KEY>
<KEYSTRING>A2345-1B345-12C45-123D5-123E5</KEYSTRING>
</KEY>
<KEY>
<KEYSTRING>987RK-AB456-EW123-3489K-XQ555</KEYSTRING>
<PURCHASER>XYZ Company</PURCHASER>
<DATE>29 July 2006</DATE>
<PRODUCTNAME>Productname</PRODUCTNAME>
<PRODUCTVERSION>1.1</PRODUCTVERSION>
<DISP>1<DISP>
</KEY>
</KEYLIST>
The KEYLIST, KEY, and KEYSTRING values are required. The PURCHASER, DATE, PRODUCTNAME,
PRODUCTVERSION, and DISP fields are optional and are not needed if the only purpose is to
load multiple keys. If a key file is provided, the content should be left as is. A minimal file would
have a structure similar to the following, with at least one KEY tag:
<?xml version="1.0" encoding="UTF-8"?>
<KEYLIST>
386 Operations
<KEY>
<KEYSTRING>A2345-1B345-12C45-123D5-123E5</KEYSTRING>
</KEY>
<KEY>
<KEYSTRING>987RK-AB456-EW123-3489K-XQ555</KEYSTRING>
</KEY>
</KEYLIST>
Related information
Assigning a license or Apply a license
NOTE: To run License Manager, you must have administrative rights on the CMS (to set, select
Options+Security→Users and Authorizations→User) and choose the Configure CMS Security option,
and the All Tools toolbox (to set, select Options+Security→Users and Authorizations→User) on the
managed systems that you want to license.
Procedure 252 Assigning a license
1.
2.
3.
4.
To access License Manager, select Deploy→License Manager.... The Product License Information
table appears.
Select a product, and then click Manage Licenses... The Manage License page appears.
Select the License Category you want to assign, and then click Assign License(s).... The Assign
Licenses section appears.
Select target systems, and then click Assign License Now.
NOTE:
You can hold the SHIFT key to select multiple systems.
NOTE: A system presently or previously licensed with a demo key may not be re-licensed
with another demo key.
If a selected product has not been registered with License Manager, the following message
is displayed:
License Manager cannot process licenses for the selected product for one of two possible
reasons:
For products where licensing information is managed by HP SIM, the Assigning Licenses page
appears. Select one or more systems from this list and click Assign License Now. The page
refreshes and shows the updated license status. Select additional systems to make more
assignments, or reselect License Manager to refresh the page.
For products that require the license to be delivered to the actual target, the License Assignment
Results table appears and reports the status of the assignment process for each target. There
might be a delay in sending license data to some targets. You can continue with other HP SIM
activities during the license assignment process.
5.
To remove an assigned license, reselect Manage Licenses. The assigned licenses appear.
Select the license category you want to remove, and then select Un-Assign Licenses.
Un-assigning a license
NOTE: To run License Manager, you must have administrative rights on the CMS (to set, select
Options+Security→Users and Authorizations→User) and choose the Configure CMS Security option,
and the All Tools toolbox (to set, select Options+Security→Users and Authorizations→User) on the
managed systems that you want to license.
Procedure 253 Un-assigning a Duration license
1.
2.
To access License Manager, select Deploy→License Manager.... The Product License Information
table appears.
Select a product, and then click Manage Licenses.... The Manage Licenses section appears.
License manager 387
3.
Select the License Category you want to un-assign. If licenses were assigned using this category,
Un-assign Licenses is available. Click Un-assign Licenses. The Un-assign Licenses section
appears.
The Un-Assign Licenses table is refreshed and shows the updated status.
The Un-Assign License table displays certificates that are assigned (but not locked). If multiple
certificates are assigned for the same system, that is represented by multiple rows for each
assigned certificate.
Related information
mxlmkeyconfig CLI
The mxlmkeyconfig CLI needs the following information supplied:
•
The path of all key files.
NOTE:
•
The path can be relative or fully defined.
The name of the resulting key file.
NOTE:
Filenames must end with the .key extension.
The command line arguments are as follows:
mxlmkeyconfig -p pathname -f filename
Management processor tools
The HP management processor enables remote server management over the web regardless of
the system state. If the operating system is not running, you can access the management processor
to power cycle the server, view event and status logs, enable console redirection, and more.
The following items appear in HP SIM after management processors are discovered.
•
System Power
Use to control the power options on HP Integrity and HP 9000 management processor systems.
To access, select Tools→Management Processor→HP Integrity and HP 9000 iLO→System
Power.
•
System Locator
Use to control the locator LED on HP Integrity and HP 9000 management processor systems.
To access, select Tools→Management Processor→HP Integrity and HP 9000 iLO→System
Locator.
•
New User
Use to add a new user account to HP Integrity and HP 9000 management processor systems.
To access, select Configure→Management Processor→HP Integrity and HP 9000 iLO→New
User.
•
Modify User
Use to modify an existing user account on HP Integrity and HP 9000 management processor
systems. To access, select Configure→Management Processor→HP Integrity and HP 9000
iLO→Modify User.
•
Delete User
Use to remove an existing user account from HP Integrity and HP 9000 management processor
systems. To access, select Configure→Management Processor→HP Integrity and HP 9000
iLO→Delete User.
388 Operations
•
LAN Access
Use to modify LAN access settings on HP Integrity and HP 9000 management processor
systems. To access, select Configure→Management Processor→HP Integrity and HP 9000
iLO→LAN Access.
•
LDAP Settings
Use to configure the LDAP service on HP Integrity and HP 9000 management processor
systems. To access, select Configure→Management Processor→HP Integrity and HP 9000
iLO→LDAP Settings.
•
Management Processor Control
Use to execute internal control actions on HP Integrity and HP 9000 management processor
systems. To access, select Configure→Management Processor→HP Integrity and HP 9000
iLO→Management Processor Control.
•
Firmware Upgrade
Use to initiate a firmware upgrade through FTP on HP Integrity and HP 9000 management
processor systems. To access, select Configure→Management Processor→HP Integrity and
HP 9000 iLO→Firmware Upgrade.
•
Deploy SSH Public Key
Use to deploy the HP SIM SSH public key on HP Integrity and HP 9000 management processor
systems. To access, select Configure→Management Processor→HP Integrity and HP 9000
iLO→Deploy SSH Public Key.
Controlling system power options through management processors
Procedure 254 Powering on HP Integrity and HP 9000 management processor systems
1.
2.
Under System power control, select one of the following:
•
Power cycle
•
Power on
•
Power off
Click Run Now to run the task immediately, click Schedule to schedule the task to run at another
time, or click Previous to return to the previous System Power page. See Scheduling a task
for more information about scheduling a task.
Controlling the system locator LED through management processors
Procedure 255 Controlling the system locator
1.
2.
Under System locator/Unit Identification LED, select one of the following:
•
On
•
Off
Click Run Now to run the task immediately, click Schedule to schedule the task to run at another
time, or click Previous to return to the previous System Power page. For more information
about scheduling a task, see Scheduling a task.
Management processor tools 389
Creating new users on management processors
Procedure 256 Creating an HP Integrity and HP 9000 management processor new user
1.
Under Enter properties for a new user account, enter:
•
Login Id
(Mandatory) This is the name that must be used when logging into a management
processor. The maximum length for a Login Id is 25 characters.
•
Password
(Mandatory) This is the password used when logging into a management processor. The
password must be a minimum of 6 to 24 characters.
•
Password (Verify)
(Mandatory) The password must be provided a second time for verification.
•
User name
(Mandatory) This name appears in the management processor user list. It is not necessarily
the same as the login name. The maximum length is 25 characters.
2.
3.
Under Access Rights, select the access rights for the user. Usually, a user is granted the Console
Access right.
•
Console access
•
Power access
•
Management processor configuration
•
User administration
Click Run Now to run the task immediately. Click Previous to return to the previous New User
page.
Editing management processor users
Procedure 257 HP Integrity and HP 9000 management processor edit user
1.
2.
3.
4.
Select Configure→Management Processor→HP Integrity and HP 9000 iLO→Modify User. The
Modify User page appears.
Select the target management processors,, and then click Next. The Step 2: Enter properties
to modify an existing user account page appears.
Under Enter the login name of the user account you wish to modify, enter the Login Id to be
modified.
Under Select the properties you wish to modify for this user account, select from the following
to modify and enter the appropriate information:
•
Password
If you select to change the password, verify the password in the Password (Verify) field.
•
User name
Select this field to modify the user name. This is not necessarily the same as the login
name. The maximum allowed length is 25 characters.
•
Access rights
If you select to modify the access rights, select from Console access, Power access,
Management processor configuration, and User administration. To remove all access
rights for an account, select the Access rights checkbox and leave the Console access,
Power access, Management processor configuration, and User administration checkboxes
unselected.
390 Operations
5.
Click Run Now to run the task immediately or click Previous to return to the previous Modify
User page.
Related procedures
Creating new users on management processors
Deleting management processor users
Deleting management processor users
Procedure 258 HP Integrity and HP 9000 management processor delete user
1.
2.
3.
4.
Select Configure→Management Processor→HP Integrity and HP 9000 iLO→Delete User. The
Delete User page appears.
Select the target management processors, and then click Next. See Creating a task for
information about selecting targets. The Step 2: Enter properties to delete an existing user
account page appears.
Enter the Login Id to be deleted.
Click Run Now to run the task immediately or click Previous to return to the previous Delete
User page.
NOTE:
HP SIM uses the Admin account to execute management processor tools. If this account
is removed from remote management systems, the tools cannot access the remote management
systems unless tool execution is reconfigured.
Procedure 259 Configuring HP SIM tool execution on a different management processor account
1.
2.
3.
4.
5.
Select a user account to run tools on remote management systems. This user account must be
present on all managed remote management processors and must have all rights on the
management processor systems.
Navigate to the tools directory on the CMS and edit MpTools.xml.
Find each <execute-as-user> line in the XML file and change Admin to the user account
specified in step 1.
Run mxtool -m -f MpTools.xml -x force.
On the CMS, run mxagentconfig or the Deploy SSH Public Key tool to copy the
authentication keys for this user account to each managed remote management processor.
For more information about deploying the SSH public key, see Deploying SSH public keys to
management processors.
Configuring LAN access on management processors
Procedure 260 LAN access for HP Integrity and HP 9000 systems
1.
Under Select the settings you wish to configure and choose their values, select from:
•
Telnet access
Select Enable or Disable. This does not affect the IP configuration or the ability of the
management processor to perform upgrades over the LAN.
•
Web SSL
Select Enable or Disable.
•
Web console port
If you select this option, enter a valid port number. Valid port numbers are 23, 2000,
and 2400.
•
IPMI over LAN access
Select Enable or Disable.
Management processor tools
391
2.
Click Run Now to run the task immediately, click Schedule to schedule when the task runs, or
click Previous to return to the previous LAN access page. For information about scheduling a
task, see Scheduling a task
Configuring LDAP settings on management processors
Procedure 261 Configuring HP Integrity and HP 9000 management processor LDAP settings
1.
Under Select the settings you wish to configure and choose their values, select from the
following:
•
Local user accounts
Select Enable or Disable. If local user accounts are enabled, you can log in to a
management processor using locally stored user credentials. If local user accounts are
disabled, user access is limited to valid directory credentials only.
•
Directory authentication
Select Enable or Disable. If directory authentication is enabled and configured properly,
users can log into the management processor system using directory credentials. If this
is disabled, user credentials are not validated using the directory.
•
Directory server IP address
Enter the IP address of the directory server.
•
Directory server LDAP port
Enter the LDAP for secure LDAP service on the server. The default value is 636.
•
Distinguished name
Specifies where this management processor instance is listed in the directory tree (for
example: cn=MP Server.ou=Management Devices.o=hp).
•
User search context 1
Specify a contact to apply to the login name entered to access the management processor
system.
•
User search context 2
Specify a context to apply to the login name entered to access the management processor
system.
•
User search context 3
Specify a context to apply to the login name entered to access the management processor
system.
2.
Click Run Now to run the task immediately, click Schedule to schedule when the task runs, or
click Previous to return to the previous LDAP Settings page. For more information about
scheduling a task, see Scheduling a task.
Executing internal control actions through management processors
Procedure 262 HP Integrity and HP 9000 management processor Control
1.
On the Step 2: Select one or more actions page, select one or both options:
•
Clear event logs
Clears the system event logs.
•
Reset management processor
Executes a reset of the management processor.
392 Operations
2.
Click Run Now to run the task immediately, click Schedule to schedule when the task runs, or
click Previous to return to the previous Management Processor Control page. For more
information about scheduling a task, see Scheduling a task.
Upgrading management processor firmware
Procedure 263 Upgrading HP Integrity and HP 9000 management processor firmware
The Step 2: Specify firmware upgrade parameters page enables you to update or modify your HP
Integrity and HP 9000 management processor firmware upgrade settings.
1. To update your settings, enter the following information:
•
Source IP
The IP address of the FTP server.
•
Path name
The path to the directory (on the FTP server) where the upgrade files reside.
•
Login ID
The login ID used to log in to the FTP server.
•
Password
The password to the FTP server.
2.
Click Run Now to run the task immediately, click Schedule to schedule when the task runs or
click Previous to return to the previous Firmware Upgrade page. For more information about
scheduling a task, see Scheduling a task.
Deploying SSH public keys to management processors
To deploy the HP SIM SSH public key:
Procedure 264 Deploy the HP SIM SSH public key
1.
2.
3.
Select Configure→Management Processor→HP Integrity and HP 9000 iLO→Deploy SSH Public
Key. The Deploy SSH Public Key page appears.
Select the target management processors, and then click Next. The Step 2: Enter credentials
page appears.
Enter the following for the administrator account on the target management processors.
•
User name
This is an administrative account on the managed remote management processor. Usually
it is the Admin account.
•
Password
This is the administrative account password on the managed remote management
processors.
•
Password (Verify)
Verify the password.
4.
Click Run Now to run the task immediately, click Schedule to schedule when the task runs, or
click Previous to return to the previous Deploy SSH Public Key page.
Cycling on the power on an HP ProLiant management processor
Procedure 265 HP ProLiant management processor Power Cycle
1.
Select Tools→Management Processor→HP Integrity and HP 9000 iLO→Power Cycle. The
Power Cycle page appears.
Management processor tools 393
2.
3.
Select target system ,and click Next. For information about selecting a target, see Creating a
task. The Step 2: Task confirmation page appears.
Click Run Now to run the task immediately. Click Schedule to schedule the task to run at
another time, or click Previous to return to the previous Power Cycle page. For more information
about scheduling a task, see Scheduling a task.
Powering on a system managed by an HP ProLiant management processor
Procedure 266 Powering on an HP ProLiant management processor
1.
2.
3.
Select Tools→Management Processor→HP Integrity and HP 9000 iLO→Power On. The Power
On page appears.
Select target system, and then click Next. For information about selecting a target, see Creating
a task. The Step 2: Task confirmation page appears.
Click Run Now to run the task immediately, click Schedule to schedule the task to run at another
time, or click Previous to return to the previous Power On page. For more information about
scheduling a task, see Scheduling a task.
Powering off a system managed by an HP ProLiant management processor
Procedure 267 Powering off an HP ProLiant management processor
1.
2.
3.
Select Tools→Management Processor→HP ProLiant management processor→Power Off. The
Power Off page appears.
Select target system, and then click Next. For information about selecting a target, see Creating
a task. The Step 2: Task confirmation page appears.
Click Run Now to run the task immediately, click Schedule to schedule the task to run at another
time, or click Previous to return to the previous Power Off page. For more information about
scheduling a task, see Scheduling a task.
Turning on the UID for a system managed by an HP ProLiant management processor
Procedure 268 Turning on the HP ProLiant management processor unit ID light
1.
2.
3.
Select Tools→Management Processor→HP Integrity and HP 9000 iLO→Turn On Unit
Identification Light. The Turn On Unit Identification Light page appears.
Select target system, and then click Next. For information about selecting targets, see Creating
a task. The Step 2: Task confirmation page appears.
Click Run Now to run the task immediately, click Schedule to schedule the task to run at another
time, or click Previous to return to the previous Turn On Unit Identification Light page. For
more information about scheduling a task, see Scheduling a task.
Turning off the UID for a system managed by an HP ProLiant management processor
Procedure 269 Turning off the HP ProLiant management processor ID light
1.
2.
3.
Select Tools→Management Processor→HP Integrity and HP 9000 iLO→Turn Off Unit
Identification Light. The Turn Off Unit Identification Light page appears.
Select target system, and then click Next. For information about selecting targets, see Creating
a task. The Step 2: Task confirmation page appears.
Click Run Now to run the task immediately, click Schedule to schedule the task to run at another
time, or click Previous to return to the previous Turn Off Unit Identification Light page. For
more information about scheduling a task, see Scheduling a task.
Related information
Related procedures
Creating new users on management processors
Editing management processor users
394 Operations
Upgrading management processor firmware
Executing internal control actions through management processors
Cycling on the power on an HP ProLiant management processor
Powering off a system managed by an HP ProLiant management processor
Powering on a system managed by an HP ProLiant management processor
Turning off the UID for a system managed by an HP ProLiant management processor
Turning on the UID for a system managed by an HP ProLiant management processor
Configuring LAN access on management processors
Configuring LDAP settings on management processors
Controlling the system locator LED through management processors
Controlling system power options through management processors
Managing Communications
Use the Manage Communications feature to troubleshoot communication problems between the
CMS and targeted systems. For each failed communication function, troubleshooting information
is available. You can reconfigure communication settings, launch agents, and push certificates to
target systems. This feature is available from the Configure→Manage Communications menu and
includes the following information:
Table 46 Managing Communications
Name
Description
Access
Advising and repairing managed
system settings
Includes a tabbed interface with a tab Manage communications quick repair.
for each functional column
(Identification, Events, Run Tools, and
Version Control). Each tab displays
the diagnostic results and includes
troubleshooting tips and advise for
fixing communication problems.
Identification tab
Includes status information on the state Identification tab.
of an identification process.
Identification attempts to determine
what the system type is, what
management protocol a system
supports, using credentials from the
Global Protocol Settings page, and
attempts to determine the operating
system and version loaded, along with
other basic attributes about the system.
Finally, it determines if the system is
associated with another system.
Events tab
Indicates if the CMS can receive
events from the target systems. This
status considers the setting of SNMP
traps and WBEM indications.
Run Tools tab
Indicates if the CMS can run tools
Run Tools tab.
locally on target systems. For example,
HP SMH. Communication issues in this
column usually relate to security and
trust relationships.
Version Control tab
Indicates the availability of software Version Control tab.
and firmware inventory data for target
systems. The status is collected and
stored during data collection.
Repairing managed system settings
Launches the Configure or Repair
Agents tool. Configure or Repair
Agents enables you to quickly and
Events tab.
Repairing managed system settings.
Managing Communications 395
Table 46 Managing Communications (continued)
Name
Description
Access
optimally configure systems for
manageability.
Updating communication statuses
Executes to get an updated
communication status.
Updating communication statuses.
Printing Manage Communications
table
Creates a printer-friendly version of
the list in a new window.
Printing Manage Communications table.
Manage communications quick repair
Procedure 270 Manage communications quick repair
1.
2.
3.
4.
5.
Select Configure→Manage Communications. The Select Target Systems page appears.
Select target systems. See Creating a task.
Click Run Now. The System List appears.
Select the systems to be repaired.
Click Advise and Repair. The Advise and Repair section appears below the System List.
Related information
Identification tab
The Identification tab displays identification errors and recommendations for fixing the errors.
Identification communication status and errors are generated based on system type, the operating
system that the managed system is running, the availability of management protocols on the
managed systems, and if the protocol has a higher weight than other protocols. You can expand
each Causes and Recommendations section.
Procedure 271 Accessing the Identification tab
1.
2.
3.
4.
5.
6.
Select Configure→Manage Communications. The Select Target Systems page appears.
Click Run Now. The system list appears.
Select single or multiple systems from the systems list.
Select target systems. For more information, see Creating a task.
Click Advise and Repair. The Advise and Repair section appears.
Click the Identification tab.
Related information
Events tab
Includes detailed error messages and recommendtions for generating and receiving events. The
event error codes are captured and stored during data collection, identification, and status polling.
For HP Systems Insight Manager to receive events from managed systems, a WBEM subscription
must be created, or the CMS IP address must be in the SNMP trap destination list on the managed
system. You can expand each Causes and Recommendations section.
Procedure 272 Accessing the Events tab
1.
2.
3.
4.
5.
6.
Select Configure→Manage Communications. The Select Target Systems page appears.
Select target systems. For more information, see Creating a task.
Click Run Now. The system list appears.
Select single or multiple systems from the systems list.
Click Advise and Repair. The Advise and Repair section appears.
Click the Events tab.
Related information
396 Operations
Run Tools tab
The Run Tools tab includes error messages and recommendations for problems that a CMS has
for executing a tool on a managed system. These problems often relate to security and trust. You
can expand each Causes and Recommendations section.
Procedure 273 Accessing the Run Tools tab
1.
2.
3.
4.
Select Configure→Manage Communications. The Select Target Systems page appears.
Select target systems. For more information, see Creating a task.
Click Advise and Repair. The Advise and Repair section appears.
Click the Run Tools tab.
Related information
Version Control tab
The Version Control tab includes error messages and recommendations for problems that a CMS
has when trying to collect software and firmware inventory from managed systems. You can expand
each Causes and Recommendations section for each error.
Procedure 274 Accessing the Version Control tab
1.
2.
3.
4.
Select Configure→Manage Communications. The Select Target Systems page appears.
Select target systems. For more information, see Creating a task.
Click Advise and Repair. The Select Target Systems section appears.
Click the Version Control tab.
Related information
Repairing managed system settings
Procedure 275 Manage communications quick repair
1.
2.
3.
4.
5.
Select Configure→Manage Communications. The Select Target Systems page appears.
Select target systems. See Creating a task.
Click Run Now. The System List appears.
Select the systems to repair from the list.
Click Quick Repair. The Step 2: Install Providers and Agents (Optional) section appears. If the
agents or providers are already installed, skip this step and proceed to the configuration step.
NOTE:
CMS.
a.
b.
c.
d.
e.
The Install Providers and Agents page is only displayed for Windows and Linux
Select Install WBEM / WMI Provider (HP Insight Management WBEM Provider) for Windows
to install WBEM or WMI providers on Windows managed systems.
Select Install SNMP Agent (HP Insight Management Agents) for Windows to install the
SNMP agent on Windows managed systems. This Insight Management Agents allows
network monitoring and control.
Select Install OpenSSH to install OpenSSH on Windows managed systems.
Select Install Linux PSP or ESX Agents to install Linux PSP and ESX Agents which are a
collection of SNMP agents used by Systems Insight Manager to gather information from
managed systems and send traps to Systems Insight Manager.
Select Install the Version Control Agent for Windows (VCA) to install the VCA on Windows
managed systems. The VCA enables you to view the HP software installed on a system
and whether updates for the software are available in the repository.
Installs the VCA in conjunction with the Virtual Connect Enterprise Manager and enables
management of the HP ProLiant software and firmware on the managed systems.
Managing Communications 397
f.
For selected installs, perform the following steps:
i. If you are installing software that is earlier than or the same version currently installed,
select Force install the agents . This option is disabled by default.
ii. If you want to reboot after the installation, select Reboot systems if necessary after
successful install option.
Systems Insight Manager determines the type of agent or provider to install based
on the system type, subtype, and operating system description of the system.
If you want to install a 64-bit agent or provider, be sure the target system is identified
as a 64-bit system in Systems Insight Manager.
If your system is not correctly identified, go to Tools→System Page→Tools &
Links→Edit System Properties. Select the correct system type, or subtype and enter
the operating system description manually.
Example: Installing Insight Management Agents on a ProLiant Windows 64-bit system:
i. Select System type: server.
ii. Select System subtype 1: HP ProLiant.
iii. Enter operating system description as Microsoft Windows Server 2003, x64
Enterprise Edition Service Pack 1 or the correct operating system description of
your system.
If you want to configure the agents after installation, select the force reboot option.
This allows the newly installed component to be completely initialized before you
configure it.
NOTE:
6.
Installation with reboot typically takes about 8 minutes.
Click Next. The Step 3: Configure or Repair Settings section appears.
398 Operations
7.
Configure the target systems by selecting one of the following options:
•
Configure WBEM / WMI. This section enables you to configure the target Linux, Windows,
or HP-UX system to send WBEM indications or events to Systems Insight Manager.
For this section, consider the following:
◦
Create subscription to WBEM events so that WBEM events will be sent to the CMS
◦
Send a sample WBEM / WMI indication to this instance of Systems Insight Manager
to test that events appear in Systems Insight Manager in the Event List or All Event
User Interface for the selected system
NOTE: This indication will appear as an Informational Event in the Event List of
Systems Insight Manager.
NOTE: This indication is supported only on HP-UX and Windows targets with
WBEM provider installed.
◦
Use an Systems Insight Manager WBEM certificate (good for 10 years) rather than
username/password to manage the system
This option deploys a WBEM certificate to the managed system and is only valid for
HP-UX systems.
◦
Configure a nonadministrative account for Systems Insight Manager to access WMI
data
This option applies to Windows systems with HP WBEM providers. The configuration
of the managed system updates to allow the specified user to access WMI information
over the network. Systems Insight Manager uses this user to read inventory and
configuration information from the system and is configured as the WBEM user in
the System Credentials. If Systems Insight Manager is configured with a user with
administration rights, this configuration step is not necessary. Systems Insight Manager
does not create this user. The user already exists as either a domain user or one
local to the managed system.
The user is added to the DCOM Users group on the managed system and has
read-only access to WMI information, and read-write permissions to the HPQ name
space. This user does not need to be an administrator of the managed system or
have sign-in rights. The domain administrator should create a special domain account.
To enter the credentials for Systems Insight Manager to use to access the managed
systems:
1. In the User name field, enter a user name.
2. In the Password field, enter the password.
3. In the Password (Verify) field, re-enter the password exactly as it was entered
in the Password field.
4. In the Domain (Optional) field, if the target belongs to a Domain, enter the
Windows domain.
If configuration of a nonadministrative user is successful, then these credentials
are saved as the System Credentials for WBEM access in Systems Insight
Manager.
•
Configure SNMP
This section enables you to configure SNMP settings.
a. Select Set read public community string to specify a community string. By default,
the first Systems Insight Manager community string that is not public appears. If no
community string exists in Systems Insight Manager, you must enter one.
Managing Communications 399
NOTE: If you configure only HP-UX systems with default SNMP installations, you
do not need to set this option. HP-UX enables read by default (get-community-name
is set to public by default on HP-UX systems).
NOTE: If you select this option, the Read Only community string is added to the
target systems. If the target system is SuSE Linux or Microsoft Windows 2003, the
managed systems do not always enable SNMP communication between themselves
and a remote host. This setting is modified to enable the instance of the Systems
Insight Manager system to communicate using SNMP with these target systems.
NOTE:
You can enter a community string up to 255 characters.
NOTE: Repairing the SNMP settings adds a Read Write community string to the
target system only if one does not currently exist. This community string is unique for
each system, is composed of over 30 characters to include letters and numbers, and
is visible only to the user with administrator privileges for that system. This Read Write
community string is required by the Web Agent to perform certain threshold setting
capabilities. This community string is used locally only on the target system and is
not used by Systems Insight Manager over the network. Linux and HP-UX systems do
not require a Read Write community string. The Read Write community string is added
on Windows systems only.
b.
c.
Select Set traps to refer to this instance of HP Systems Insight Manager in the target
systems SNMP Trap Destination List. This setting enables the target systems to send
SNMP traps to this instance of Systems Insight Manager.
Select Send a sample SNMP trap to this instance of the Systems Insight Manager to
test that events appear in Systems Insight Manager event lists to verify that SNMP
events appear in the Systems Insight Manager events list.
To successfully send a test trap, you must configure target systems to send a trap to
this instance.
NOTE: You can send a test trap only from a managed system with an HP Insight
Management Agents installed.
NOTE: The trap from Windows appears as a Generic Trap from the system and
is listed as a Major Event in the Event List of Systems Insight Manager. The trap
received from Linux and HP-UX targets appears as a Cold Trap and is listed as
Informational Events in the Event List of Systems Insight Manager.
•
Configure secure shell (SSH) access
Select this option to configure SSH access on managed systems.
If you select this option, you must select one of the following options:
◦
Host based authentication for SSH
NOTE: For this option to work, the user name and password provided in Step 4:
Enter credentials must be an administrative level account. For Linux or HP-UX targets,
it must be the root account and password.
◦
400 Operations
Each user has to be authenticated on the managed system
NOTE: If you do not want all users that have sign-in access to Systems Insight
Manager to run the tool and you would like to control which users need to have
access, this option is more secure.
NOTE: You can configure SSH only if the OpenSSH service is running on the
managed systems. You can install OpenSSH on Windows systems by running the
Install Open SSH or by selecting the tool under Deploy→Deploy Drivers, Firmware
and Agents→Install Open SSH.
•
Set Trust relationship to "Trust by Certificate"
Select this option to configure systems to use the Trust by Certificate trust relationship with
the Systems Insight Manager.
For Systems Insight Manager on the target systems, this option sets the trust mode to Trust
by Certificate and copies the Systems Insight Manager system certificate to the target
system trusted certificate directory. This option enables Systems Insight Manager users to
connect to the SMH using the certificate for authentication.
You can configure SSO to management processors for Onboard Administrator and for
remote management. To configure SSO, select Set Trust Relationship. After you configure
SSO, you are not continually prompted to supply the login credentials for the management
processor.
NOTE: For systems with Management HTTP Server 5.x and earlier, the Configure or
Repair Agents setting adds the Administrator password in the Management HTTP Server
store and modifies the SNMP settings, but it cannot change trust relationship information.
Select the checkbox beside Import Secure Sockets Layer (SSL) certificate for Systems Insight
Manager to trust the HP SMH of the managed system. This option is only valid for HP-UX
and Linux operating systems.
•
Configure HP Version Control Agent
Select this option to configure the VCA to point to the HP Version Control Repository
Manager, where the repository of software and firmware is located, enabling version
comparison and software updates. This option is available for Windows and Linux systems.
To configure VCA:
1. In the Select the system where the VCRM is installed field, select a server from the
dropdown list.
2. In the User Name field, enter the user name to access the VCRM. This user cannot
be the default administrator user, and must have administrative privileges.
3. In the Password field, enter the password to access the VCRM.
4. In the Password (verify) field, re-enter the password for the VCRM.
•
Set administrator password for Insight Management Agents 7.1 or earlier
Select this option to repair the administrator password on all Insight Management Agents
installed on the target systems as applicable for Windows and Linux systems.
Managing Communications 401
NOTE: Do not set this option if you have Insight Management Agents 7.2 or later
installed.
NOTE: If the remote system is running HP-UX, this option is not executed on the remote
system because it is not applicable on HP-UX systems. If you are configuring only HP-UX
target systems, you do not need to set this option.
If you select this option, you must complete the following steps:
a. In the Password field, enter the new administrator password.
b. In the Password (verify) field, re-enter the new administrator password.
8.
9.
Click Next. The Step 4: Enter Credentials section appears.
Enter the following credentials.
The credentials used in this step must work for all selected target systems. HP recommends
using domain administrator credentials. Credentials entered here are not saved by Systems
Insight Manager except to run a scheduled task later.
If you select Configure secure shell (SSH) access for a Windows target system, the account you
specify must be a member of the local Administrators group. For Windows targets using a
domain account, the account is automatically added to this group.
a. Select one of the following options:
•
•
b.
c.
d.
e.
402 Operations
Use sign-in credentials These credentials must be a privileged account on the managed
system. The sign-in credentials option is available if the following options are selected:
◦
Install WBEM/WMI Provider (HP Insight Management WBEM Provider) for
Windows
◦
Install Simple Network Management Protocol Agent (HP Insight Management
Agents) for Windows
◦
Install Linux PSP or ESX Agents
◦
Install the HP Version Control for Windows
Use the following credentials for all systems.
In the User name field, enter the system administrator name.
In the Password field, enter the system administrator password.
In the Password (Verify) field, re-enter the system administrator password.
In the Domain (Optional) field, if you are using a domain account, enter the Windows
domain.
10. Click Run Now or click Schedule to run this task at a later time. The Task Results page appears.
If the Management HTTP Server is installed on target systems, the login credentials are updated
in the Management HTTP Server password file. As with other Systems Insight Manager tools,
you can configure the Configure or Repair Agents tool to run on a schedule or manually. Only
one instance of Configure or Repair Agents tool can run at a time.
The Configure or Repair Agents tool can update multiple target systems. The log results indicate
whether the repair attempt was successful. For Configure or Repair Agents, the Task Results
page displays the following information.
Table 47 CRA Task Results information
Field Name
Description
Status
This field displays the details for each target system
within a task instance.
Exit Code
This field represents the success or failure of an
executable program. If the return value is zero or a
positive value, the executable ran successfully. If a
negative value is returned, the executable failed. This
exit code does not indicate that all configuration
attempts were successful. It is possible for some to
succeed but some to fail.
Target Name
This field displays the name/IP address of the target.
The stdout tab
This tab displays the output text information.
The stderr tab
This tab displays information if the executable
experienced an error.
View Printable Report
You can print reports for the selected target system or
for all target systems associated with the task instance.
To print a report:
a. Click View Printable Report.
An Options Message box appears.
b. Select a report.
c. Click OK to display the report, or click Cancel to
return to the View Task Results page.
Related information
Updating communication statuses
Procedure 276 Manage communications Update
1.
2.
3.
4.
5.
Select Configure→Manage Communications. The Select Target Systems page appears.
Select target systems. See Creating a task.
Click Run Now. The system list appears.
Select single or multiple systems from the systems list.
Click Update.
Related information
Printing Manage Communications table
Procedure 277 Manage communications Printing
1.
2.
3.
4.
Select Configure→Manage Communications. The Select Target Systems page appears.
Select target systems. See Creating a task.
Click Print.
When the table appears, select File→Print from the browser menu.
Managing Communications 403
Because certain print options are not supported in Systems Insight Manager, you cannot perform
the following tasks:
•
Change the Orientation to Landscape in the Print dialog box.
•
Cancel printing after the print job has been executed; however, you can access the operating
systems print queue and cancel the print job
•
Print to a file
•
Print specific selections; you can print the entire list only
•
Print the table view page if you close the browser immediately after issuing a print request
Related information
Managing MIBs
A MIB is a file that contains information that enables you to correctly interpret specific information
from systems on your network and gives you a more precise view of the activity on your network.
To take advantage of this capability, the MIB must be registered to HP SIM. For more information,
see Registering a MIB.
HP MIBs enable you to take advantage of the rich management infrastructure that HP builds into
its products. HP MIBs are registered in the HP SIM database. You can find them in \hp\system
insight manager\mibs on a Windows CMS or in opt/mx/mibs on a UNIX or Linux CMS.
If you have third-party systems on your network, register them with HP SIM. For more information
regarding registering your MIBs, see Registering a MIB. Registration enables the MIBs to be
identified and traps to be interpreted to give you a more precise view of the activity on your
network. Always register the most recent version of a third-party MIB.
Related information
Viewing a MIB
After you register a MIB with HP SIM database, you can use additional mxmib options, such as
mxmib -l and mxmib -t can be used to view MIBs and their associated traps. For a MIB file
to be listed as registered, the MIB file must reside in the mibs directory.
CAUTION:
Do not rename, move, or delete MIB files from the directory after they are registered.
You can also use SNMP Trap Settings (Options→Events→SNMP Trap Settings) to display registered
MIBs and their associated traps. Use this screen to modify Event Type, Description, Enable Trap
Handling, Category, and Severity attributes to further customize the information collected on the
network. For more information regarding editing a MIB, see Editing a MIB.
NOTE: The following HP SIM directories are default directories. However, the directories can
vary depending on the directory specified during HP SIM installation.
Viewing a MIB file on a Windows operating system:
Procedure 278 Viewing a MIB file on a Windows operating system:
1.
2.
3.
Navigate to the MIB directory at c:/program files/hp/systems insight manager/
mibs.
Open the MIB file with an ASCII editor.
Enter write cpqhost.mib on the Windows command line.
Viewing a MIB file on a Linux or HP-UX operating system:
Procedure 279 Viewing a MIB file on a Linux or HP-UX operating system:
1.
2.
Enter cd opt/mx/mibs.
Run mxmib -l to view registered MIBs.
404 Operations
3.
Enter vi file.mib from a shell prompt.
Editing a MIB
The HP MIBs configuration (.cfg) file can be edited with trap specific information, such as:
•
TYPE. This is a simplified form of the actual trap name. Change the type if it does not describe
the device for you.
•
SEVERITY. Some vendors use the default INFORMATIONAL for severity levels. Change the
severity to a level that reflects your judgment of the problem. Alternatively, you can change
a Major or Critical severity for a trap message that is not a critical situation in your environment.
Only you know if this is the case. The only valid options for HP SIM include: Critical, Major,
Minor, Warning, and Informational.
•
MSG_FORMATTER. This string constructs enhanced messages that can be sent to a pager or
e-mail address. This string can be modified in the REV or the MIB.
•
ENABLE. By default, all traps are enabled. Trap handling gives you control over the volume
of messages. Disable nuisance messages, such as unnecessary informational messages or
repeated trap messages for an event that has not been corrected.
•
DESCRIPTION. This is vendor-supplied. Replace it with specific instructions, a precise reference
source, or a website referral.
•
CATEGORY. This lists the HP SIM category types and UNKNOWN.
Procedure 280 Editing the .cfg file
1.
2.
3.
Navigate to the MIB directory:
•
For Windows operating systems, navigate to \program files\hp\systems insight
manager\mibs.
•
For Linux or HP-UX operating systems, navigate to /opt/mx/mibs.
Run mcompile mymib.mib to create the .cfg file.
After the .cfg file is created, use an editor to edit the .cfg file.
Procedure 281 Editing trap-specific information in HP SIM
1.
From HP SIM, select Options→Events→SNMP Trap Settings.
The SNMP Trap Settings page appears.
2.
3.
4.
Select the MIB name.
Select the trap in the MIB.
Edit the file with your changes, and then click OK to save your changes.
The changes made through the SNMP Trap Settings page are saved to the HP SIM database
only. The .cfg and MIB files are not affected.
Related information
Compiling a MIB
The mcompile command enables you to compile an SNMP MIB file into an intermediate format
(.cfg) file that can be registered using the mxmib utility for use with HP SIM.
Observe the following tips:
•
•
To compile a MIB, you must copy the .MIB file to the default MIB directory.
Comment lines in MIB files start with "--" and end with a new line or the next occurrence of
"--." Beware of MIBs with "-" characters across the entire line. These lines are intended to be
comments. However, extra dashes cancel the first set of "--" characters.
Examples:
-- xyz comments out xyz
Managing MIBs 405
However:
-- -- xyz effectively uncomments xyz
•
mcompile expects the END keyword at the end of a module on a line by itself. Be sure there
is a new line in the MIB file after the END keyword.
Procedure 282 Compiling a MIB
1.
2.
Navigate to the HP SIM root directory and open an MS-DOS® window or UNIX shell.
Run mcompile to compile an SNMP MIB file into an intermediate format (.cfg).
mcompile recognizes the -d option. This option changes to the specified directory to locate
and process the MIB file. The MxMib expects the .cfg file to reside in MIBs directory. It is
convenient to have both files in that directory as the output of mcompile (.cfg) will be in the
directory where mcompile either compiles or is directed to compile in.
For example:
cd mibsdir
mcompile mymib.mib
or
if you are not running in the MIBs directory:
mcompile -d mibsdir mymib.mib
3.
Run mxmib to register the MIB with HP SIM.
For example:
MxMib -a mymib.cfg
Related information
Registering a MIB
HP SIM ships with HP MIBs that are registered at installation. In addition, many precompiled MIBs
are included in the form of .cfg files. You can register these MIBs at your convenience. Many
.cfg files have been edited. If the corresponding MIB is recompiled, those edits are lost.
To view a list of registered MIBs, including MIBs you have registered:
•
On a Windows operating system, enter dir "c:\program files\hp\systems insight
manager\MIBs\ *.MIB" at the command line.
•
On UNIX, enter ls /opt/mx/mibs/*.mib at the command line.
To view MIBs that are preloaded and registered during HP SIM installation:
•
On a Windows operating system, enter type "c:\program files\hp\systems
insight manager\MIBs\ cfglist?.list" at the command line.
•
On UNIX, enter cat /opt/mx/mibs/cfglist*.list at the command line.
These are the default directories. If you changed the install action directory during HP SIM
installation, these commands must use your path instead.
You can register HP MIBs using the CLI. The CLI is the same for all CMS types including Windows,
Linux, and HP-UX operating systems.
When registering a MIB, you do not need to run mcompile on the MIB, especially if the
corresponding .cfg file to that MIB exists. If you run mcompile on a MIB and a .cfg file exists,
a new .cfg is generated, which supersedes the old .cfg file and any changes in the old file. In
most cases with an existing .cfg file, edit the .cfg file to make changes unless a new MIB has
been furnished.
You can then register this .cfg file to the HP SIM database using the mxmib -a or mxmib -f
command.
406 Operations
Registering a MIB in HP SIM
Procedure 283 Registering a MIB in HP SIM
1.
2.
3.
Open an MS-DOS window or UNIX shell.
Use an editor to create a file containing a list of .cfg files to be registered, one .cfg per
line.
Run mxmib -f cfglist.list to import a list of MIBs into HP SIM. After the MIB is registered in
HP SIM, use mxmib to list the MIBs from HP SIM and to delete or unregister the MIBs, use
mxmib —d.
You can also use mxmib -amymib.cfg to register a single MIB.
The .cfg file must be in the default MIBs directory.
NOTE: MxMib requires the .cfg file to reside in the MIBS directory where all the .mib and
.cfg reside by default.
Updating a MIB
Procedure 284 Updating a MIB
1.
Download and copy MIBs and matching .cfg files to the mibs directory. The mibs directory
is typically located at c:\program files\hp\systems insight manager\mibs for
Windows and at /opt/mx/mibs for Linux and HP-UX.
If a .cfg file is available and no customizations have been made, proceed to step 2.
2.
Run mcompile to create and update .cfg files that exists.
If the old .cfg file had customizations, reapply them.
3.
Run mxmib -aupdatedfile.cfg to update the MIB data in the database.
Service trap and service MIB information
HP SIM ships with a version of the service MIB to support service traps sent by Open Service Event
Manager and WEBES. The service MIB is comprised of the cpqservice.mib and
cpqservice.cfg files. To obtain the service MIB separately, see http://h18023.www1.hp.com/
support/svctools/ and select Service MIB Zip file under WEBES or OSEM. The zip file contains the
.mib and .cfg files. Review the readme.txt file contained in the zip file for compatibility
instructions.
Beginning with Open Service Event Manager 1.3.6, you must configure the tool to generate the
new trap type by accessing Internal Settings for Open Service Event Manager: HP SIM trap revision.
WEBES sends the trap by default.
Related information
Unregistering a MIB
HP MIBs can be unregistered using the command line. The CLI is the same for all CMS types to
include Windows, Linux, and HP-UX.
Procedure 285 Unregistering a MIB from HP SIM
1.
2.
Open an MS-DOS window or UNIX shell.
Run mxmib -d file.mib to unregister the MIB in HP SIM.
Related information
Related procedures
Registering a MIB
Unregistering a MIB
Compiling a MIB
Managing MIBs 407
Editing a MIB
Installing OpenSSH
HP SIM custom and command line tools require that SSH be installed and configured on each
managed system to work properly. For more information about SSH and the features in HP SIM
that use SSH, see the HP Systems Insight Manager User Guide at http://www.hp.com/go/
insightmanagement/sim/docs.
The OpenSSH installation is run from the CMS. It installs the OpenSSH service on target Windows
systems and then runs the mxagentconfig command to complete the configuration.
NOTE:
To be sure that the install OpenSSH task runs successfully, sign in as a user with
administrative rights. If you are signed in as another user, be sure the user name does not contain
non-ASCII characters.
NOTE: You can easily install OpenSSH on Windows managed systems using the Configure or
Repair Agents feature. For more informat