HPE 

Insight Remote Support

Software Version: 7.10

Monitored Devices Configuration Guide

Document Release Date: April 2019

Software Release Date: March 2019
 Legal Notices
Warranty
The only warranties for Hewlett Packard Enterprise 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. HPE shall not be liable for technical or editorial errors or omissions
contained herein.
The information contained herein is subject to change without notice.

Restricted Rights Legend

Confidential computer software. Valid license from HPE 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.

Copyright Notice
© Copyright 2019 Hewlett Packard Enterprise Development LP

Privacy Policy
www.hpe.com/us/en/privacy/master-policy.html

Trademark Notices
Microsoft® and Windows® are trademarks of the Microsoft group of companies.
UNIX® is a registered trademark of The Open Group.
Linux® is the registered trademark of Linus Torvalds in the U.S. and other countries.
Red Hat® is a registered trademark of Red Hat, Inc. in the United States and other countries.
Citrix® and XenDesktop® are registered trademarks of Citrix Systems, Inc. and/or one more of its
subsidiaries, and may be registered in the United States Patent and Trademark Office and in other countries.
Intel®, Itanium® and Intel® Xeon® are trademarks of Intel Corporation in the U.S. and other countries.
© 2012 Google Inc. All rights reserved. Chrome™ is a trademark of Google Inc.

HPE Insight Remote Support 7.10: Monitored Devices Configuration Guide Page 2 of 436
 Contents
Preface 23
Document purpose and audience 23
Product overview 23
Related documents 24
Document revision history 24
Sign up to receive Insight Remote Support communications 24
Support information 25

Chapter 1: Understanding monitored devices prerequisites 26

Identify required communication protocols and software components 26
Functionality not supported in Insight RS 7.10 38

Chapter 2: Configuring ProLiant Gen10 servers 39

Fulfill configuration requirements 39
Configure monitored devices 39
Install and configure software 40
Verify user permissions 41
Configure firewall and port settings 41
Add protocol credentials and start discovery 41
Create a RIBCL protocol credential in the Insight RS Console 41
Define discovery subnets if desired 42
Discover the ProLiant Gen10 server 42
Discovering the ProLiant server from the Insight RS Console 43
Enabling Insight Remote Support for a ProLiant server 43
Verify discovery and device status 44
Test communication from the ProLiant Gen10 server to Insight RS 44
Verify service event monitoring 44
Initiate a data collection 45
Initiating a data collection in the iLO 5 web interface 45
Initiating a data collection in Insight Remote Support 45
Send an Active Health System Report 45
Sending an Active Health System report from the iLO 5 web interface 46
Sending an Active Health System Report from Insight Remote Support 46
Maintenance and troubleshooting 46
Set Maintenance Mode 46
Disable monitoring of a ProLiant Gen10 server 47
ProLiant Gen10 Hosting Device discovery 47

Chapter 3: Configuring ProLiant Gen8 and Gen9 servers 48

Fulfill configuration requirements 48

HPE Insight Remote Support 7.10: Monitored Devices Configuration Guide Page 3 of 436
 Configure monitored devices 49
Verify user permissions 49
Configure firewall and port settings 50
Add protocol credentials and start discovery 50
Create a RIBCL protocol credential in the Insight RS Console 50
Define discovery subnets if desired 50
Discover the ProLiant Gen8 or Gen9 server 51
Discovering the ProLiant server from the Insight RS Console 52
Enabling Insight Remote Support for a ProLiant server 52
Verify discovery and device status 53
Test communication from the ProLiant Gen8 or Gen9 server to Insight RS 53
Verify service event monitoring 53
Initiate a data collection 55
Initiating a data collection in the iLO 4 web interface 55
Initiating a data collection in Insight Remote Support 56
Send an Active Health System Report 56
Sending an Active Health System report from the iLO 4 web interface 56
Sending an Active Health System Report from Insight Remote Support 56
Maintenance and troubleshooting 57
Set Maintenance Mode 57
Disable monitoring of a ProLiant Gen8 and Gen9 server 57
Missing IP address during discovery 58
Warranty and contract discrepancy in Insight Online 59

Chapter 4: Configuring ProLiant Windows servers 60

Configuring ProLiant Windows servers using WMI 60
Fulfill configuration requirements 60
Install and configure communication software on servers 61
Install and configure WMI 61
Install Service Pack for ProLiant 61
Install WMI 61
Install System Management Homepage 61
Disabling User Account Control in Windows Server 62
Configure firewall and port settings 62
Add protocol credentials and start discovery 63
Create a WMI protocol credential in the Insight RS Console 63
Discover the device in the Insight RS Console 64
Verify discovery and device status 64
Verify communication between monitored device and Insight RS 64
Send a WBEM test indication to the Hosting Device 64
Viewing test events in the Insight RS Console 65
Verify collections in the Insight RS Console 66
Maintenance and troubleshooting 66
Device health in Insight Remote Support 66
Configuring ProLiant Windows servers using SNMP 67

HPE Insight Remote Support 7.10: Monitored Devices Configuration Guide Page 4 of 436
 Fulfill configuration requirements 67
Install and configure communication software on servers 67
Install and Configure SNMP Agents 67
Install Service Pack for ProLiant 67
Install System Management Homepage 68
Configure SNMP 68
Configure firewall and port settings 72
Add protocol credentials and start discovery 73
Create an SNMP protocol credential in Insight RS Console 73
Discover the device in the Insight RS Console 73
Verify discovery and device status 74
Verify communication between monitored device and Insight RS 74
Send an SNMP test trap to the Hosting Device 74
Viewing test events in the Insight RS Console 74
Verify collections in the Insight RS Console 75

Chapter 5: Configuring ProLiant Linux servers 76

Fulfill configuration requirements 76
Install and configure communication software on servers 76
Install SNMP Agents 76
Configure SNMP 77
Configure firewall and port settings 79
Add protocol credentials and start discovery 80
Create an SNMP protocol credential in Insight RS Console 80
Discover the device in the Insight RS Console 80
Verify discovery and device status 80
Verify communication between monitored device and Insight RS 81
Verify connectivity by sending an SNMP test trap to the Hosting Device 81
Viewing test events in the Insight RS Console 81
Verify collections in the Insight RS Console 82

Chapter 6: Configuring ProLiant VMware ESX servers 83

Fulfill configuration requirements 83
Install and configure communication software on servers 83
Configure SNMP 83
Configure firewall and port settings 86
Verify communication between monitored device and Insight RS 87
Verify connectivity by sending an SNMP test trap to the Hosting Device 87
Viewing test events in the Insight RS Console 87
Verify collections in the Insight RS Console 88

Chapter 7: Configuring ProLiant VMware ESXi servers 89

Fulfill configuration requirements 89

HPE Insight Remote Support 7.10: Monitored Devices Configuration Guide Page 5 of 436
 Install and configure communication software on servers 89
Install an ESXi image 89
Obtain the HPE ESXi image 89
Obtain bundles to configure the VMware ESXi image 90
Configure firewall and port settings 90
Add protocol credentials and start discovery 90
Create a WBEM protocol credential in the Insight RS Console 90
Discover the device in the Insight RS Console 91
Verify discovery and device status 91
Verify communication between monitored device and Insight RS 91
Verify connectivity by sending a test event to the Hosting Device 91
Viewing test events in the Insight RS Console 92
Verify collections in the Insight RS Console 92

Chapter 8: Configuring ProLiant Citrix XenServers 93

Fulfill configuration requirements 93
Install and configure communication software on servers 93
Install SNMP Agents for Citrix XenServer 93
Configure SNMP 94
Configure firewall and port settings 96
Verify communication between monitored device and Insight RS 97
Verify connectivity by sending an SNMP test trap to the Hosting Device 98
Viewing test events in the Insight RS Console 98
Verify collections in the Insight RS Console 98

Chapter 9: Configuring Integrity Windows 2003 servers 100

Fulfill configuration requirements 100
Install and configure communication software on servers 100
Install the ELMC software package on the monitored device 100
Verify SNMP Agent prerequisites on the monitored device 101
Verify WBEM Provider prerequisites on the monitored device 101
Configure firewall and port settings 102
Add protocol credentials and start discovery 103
Create an ELMC protocol credential in the Insight RS Console 103
Create an SNMPv1 protocol credential in the Insight RS Console 103
Create a WMI protocol credential in the Insight RS Console 104
Discover the device in the Insight RS Console 104
Verify discovery and device status 104
Verify communication between monitored device and Insight RS 105
Verify connectivity by sending an SNMP test trap 105
Sending a WBEM test indication to verify connectivity 106
Viewing test events in the Insight RS Console 107
Verify collections in the Insight RS Console 108

HPE Insight Remote Support 7.10: Monitored Devices Configuration Guide Page 6 of 436
 Chapter 10: Configuring Integrity Windows 2008 servers 109
Fulfill configuration requirements 109
Install and configure communication software on servers 109
Install WBEM Providers on the monitored device 109
Configure firewall and port settings 110
Add protocol credentials and start discovery 110
Create a WBEM protocol credential in the Insight RS Console 110
Discover the device in the Insight RS Console 111
Verify discovery and device status 111
Verify communication between monitored device and Insight RS 111
Verify connectivity by sending a WBEM test indication 111
Viewing test events in the Insight RS Console 113
Verify collections in the Insight RS Console 113

Chapter 11: Configuring Integrity Linux servers 115

Fulfill configuration requirements 115
Install and configure communication software on servers 115
Verify HPE WBEM providers installed 115
Configure firewall and port settings 116
Add protocol credentials and start discovery 116
Create a WBEM protocol credential in the Insight RS Console 116
Discover the device in the Insight RS Console 116
Verify discovery and device status 117
Verify communication between monitored device and Insight RS 117
Send a test event to the Hosting Device 117
Viewing test events in the Insight RS Console 117
Verify collections in the Insight RS Console 118

Chapter 12: Configuring Integrity and HP 9000 HP-UX servers 119

Fulfill configuration requirements 119
Install and configure communication software on servers 119
Install System Fault Management 119
Meeting HP-UX Operating System, Software, and Patch Requirements 120
Fulfilling software and patch requirements for HP-UX 11i v1 (HP 9000 only) 120
Fulfilling software and patch requirements for HP-UX 11i v2 123
Fulfilling Software and Patch Requirements for HP-UX 11i v3 125
Verify System Fault Management is operational 127
Install vPar v5 Prerequsites (if required) 129
Create WBEM users 130
Creating non-privileged users with cimauth 130
Creating WBEM privileged users with WBEM A.02.09.08 or later 131
Configure firewall and port settings 132
Add protocol credentials and start discovery 132

HPE Insight Remote Support 7.10: Monitored Devices Configuration Guide Page 7 of 436
 Add the WBEM protocol to the Insight RS Console 133
Option 1: Authenticate Using Username and Password 133
Option 2: Authenticate to HP-UX WBEM using a certificate 133
Option 3: Authenticate to HP-UX WBEM using user defined certificate 135
Discover the device in the Insight RS Console 137
Verify discovery and device status 138
Verify communication between monitored device and Insight RS 138
Verify connectivity by sending a test trap to the Hosting Device 138
Verify collections in the Insight RS Console 138
Maintenance 139
Export certificates 139

Chapter 13: Configuring Integrity Superdome 2 servers 141

Fulfill configuration requirements 141
Install and configure communication software on servers 141
Superdome 2 OA configuration verification 141
Using Telnet or SSH 142
Using a web browser 142
Install vPar v5 Prerequsites (if required) 142
Configure firewall and port settings 142
Add protocol credentials and start discovery 143
Create a WBEM protocol credential in Insight RS Console 143
Create a WS-Man protocol credential in the Insight RS Console 144
Discover the Superdome 2 server in the Insight RS Console 144
Verify Superdome 2 discovery 144
Verify the Superdome 2 OA 145
Verify the Superdome 2 HP-UX partitions 145
Verify communication between monitored device and Insight RS 146
Generating test events 146
Verify collections in the Insight RS Console 146

Chapter 14: Configuring Integrity Superdome X servers 147

Fulfill configuration requirements 147
Configure communication software on servers 147
Configuring the OA 147
Integrity Superdome X OA configuration verification 147
Using Telnet or SSH 148
Using a web browser 148
Verify the OA can send OS events 148
Add operator-level user (if required) 148
Configuring Linux partitions 149
Install WBEM providers 149
Verify Linux Services after provider installation 149
Configure non-root users (if required) 150

HPE Insight Remote Support 7.10: Monitored Devices Configuration Guide Page 8 of 436
 Configuring Windows partitions 151
Install WBEM providers 151
Create a signed certificate 151
Configure non-administrator users (if required) 151
Configuring VMware vSphere partitions 152
Verify partition status 152
Configure firewall and port settings 153
Add protocol credentials and start discovery 154
Create a WS-Man protocol credential for the OA in the Insight RS Console 154
Create a WS-Man protocol credential for the Linux and Windows partitions in the Insight RS
Console 154
Create a WBEM protocol credential for the VMware vSphere partitions in the Insight RS
Console 155
Discover the Integrity Superdome X server and partitions in the Insight RS Console 155
Verify Integrity Superdome X discovery 155
Verify the Integrity Superdome X OA 156
Verify the Integrity Superdome X partitions 156
Verify communication between monitored device and Insight RS 156
Generating test events 157
Verify collections in the Insight RS Console 157
If desired, configure your Integrity Superdome X as a solution 158

Chapter 15: Configuring Superdome Flex servers 160

Fulfill configuration requirements 160
Configure monitored devices 160
Install and configure software 160
Configure firewall and port settings 161
Add protocol credentials and start discovery 161
Create an Embedded Support Automation Protocol (ESA) credential in the Insight RS Console 161
Discover the Superdome Flex server in the Insight RS Console 161
Verify Superdome Flex discovery 162
Verify communication between monitored device and Insight RS 162
Generating test events 163
Verify collections in the Insight RS Console 163

Chapter 16: Configuring HPE OpenVMS Integrity servers 164

Fulfill configuration requirements 164
Install and configure communication software on servers 164
Fulfill ELMC system requirements 164
Fulfilling hardware and software requirements 164
Fulfilling required permissions and access 165
Grant permissions required to install ELMC 165
Grant permissions required to run ELMC 166
Heterogeneous cluster instructions 166

HPE Insight Remote Support 7.10: Monitored Devices Configuration Guide Page 9 of 436
 Archiving and cleaning the error log 167
Confirm SYSMAN is functioning cluster-wide 167
How to remove ELMC 168
Install the ELMC HPE OpenVMS Software Package on the Monitored Device 168
WCCPROXY command verb reference 170
Install ELMC when a new system is added to an existing ELMC installation 170
Install and configure WBEM or SNMP 171
Option 1: Install the HPE OpenVMS WBEM Services and WBEM Providers 171
Confirm TCP/IP IP address and name resolution is functioning 172
Check if WBEM was previously configured 172
Install WBEMCIM and WBEMPROVIDERS for the first time 173
Upgrade WBEM 177
Option 2: Enable and configure SNMP 182
Confirm TCP/IP IP address and name resolution is functioning 182
Determine if the SNMP service is enabled 183
Enable SNMP 183
Configure read community string 183
Configure dynamic processor resilience 184
Configure firewall and port settings 185
Add protocol credentials and start discovery 185
Create a protocol credential in the Insight RS Console 186
Option 1: Create a WBEM protocol credential in Insight RS Console 186
Option 2: Create an SNMPv1 protocol credential in the Insight RS Console 186
Discover the device in the Insight RS Console 186
Verify discovery and device status 187
Configure SAN configuration collections 187
Verify communication between monitored device and Insight RS 189
Verify service event monitoring 189
Verify collections in the Insight RS Console 189
Optional post-configuration steps 191
Disable WBEM protocol 191
Disable SNMP protocol 191
Troubleshooting 191
WBEM protocol troubleshooting 191
SNMP protocol troubleshooting 193
ELMC protocol troubleshooting 195
SSH protocol troubleshooting 197
Telnet protocol troubleshooting 200
Entitlement troubleshooting 203

Chapter 17: Configuring VSI OpenVMS Integrity servers 204

Fulfill configuration requirements 204
Install and configure communication software on servers 204
Fulfill ELMC system requirements 204

HPE Insight Remote Support 7.10: Monitored Devices Configuration Guide Page 10 of 436
 Fulfilling hardware and software requirements 204
Fulfilling required permissions and access 205
Grant permissions required to install ELMC 205
Grant permissions required to run ELMC 206
Heterogeneous cluster instructions 206
Archiving and cleaning the error log 207
Confirm SYSMAN is functioning cluster-wide 207
How to remove ELMC 207
Install the ELMC VSI OpenVMS Software Package on the Monitored Device 208
WCCPROXY command verb reference 210
Install ELMC when a new system is added to an existing ELMC installation 210
Install the VSI OpenVMS WBEM Services and WBEM Providers 210
Confirm TCP/IP IP address and name resolution is functioning 211
Check if WBEM was previously configured 211
Install WBEMCIM and WBEMPROVIDERS for the first time 212
Upgrade WBEM 216
Configure dynamic processor resilience 221
Configure firewall and port settings 222
Add protocol credentials and start discovery 222
Create a WBEM protocol credential in Insight RS Console 222
Discover the device in the Insight RS Console 223
Verify discovery and device status 223
Verify communication between monitored device and Insight RS 224
Verify service event monitoring 224
Verify collections in the Insight RS Console 224
Optional post-configuration steps 225
Disable WBEM protocol 225
Troubleshooting 225
WBEM protocol troubleshooting 225
ELMC protocol troubleshooting 227
Entitlement troubleshooting 230

Chapter 18: Configuring HPE OpenVMS AlphaServers 231

Fulfill configuration requirements 231
Install and configure communication software on servers 231
Fulfill ELMC system requirements 231
Fulfilling hardware and software requirements 232
Fulfilling required permissions and access 232
Grant permissions required to install ELMC 232
Grant permissions required to run ELMC 233
Heterogeneous cluster instructions 233
Archiving and cleaning the error log 234
Confirm SYSMAN is functioning cluster-wide 234
How to remove ELMC 235
Verify serial number 235

HPE Insight Remote Support 7.10: Monitored Devices Configuration Guide Page 11 of 436
 Install the ELMC HPE OpenVMS Software Package on the Monitored Device 236
WCCPROXY command verb reference 237
Install ELMC when a new system is added to an existing ELMC installation 238
Enable and configure SNMP 238
Confirm TCP/IP IP address and name resolution is functioning 238
Determine if the SNMP service is enabled 238
Enable SNMP 239
Configure read community string 239
Configure firewall and port settings 240
Add protocol credentials and start discovery 240
Create an SNMPv1 protocol credential in the Insight RS Console 240
Discover the device in the Insight RS Console 241
Verify discovery and device status 241
Configure SAN configuration collections 241
Verify communication between monitored device and Insight RS 243
Verify service event monitoring 243
Verify collections in the Insight RS Console 244
Optional post-configuration steps 245
Disable SNMP service 245
Troubleshooting 245
SNMP protocol troubleshooting 245
ELMC protocol troubleshooting 247
SSH protocol troubleshooting 249
Telnet protocol troubleshooting 252
Entitlement troubleshooting 254

Chapter 19: Configuring Tru64 UNIX servers 256

Fulfill configuration requirements 256
Install and configure communication software on servers 256
Fulfill ELMC system requirements 256
Hardware and software requirements 256
Required permissions and access 257
Archiving and cleaning the error log 257
Tru64 UNIX version 4.0F 257
Tru64 UNIX version 4.0G 258
Tru64 UNIX version 5.A or higher 258
Verify the binary.errlog CDSL 258
Clear the log with binlogd running 259
Verify serial number 259
Installing the ELMC Tru64 UNIX software package 260
Add protocol credentials and start discovery 260
Create an ELMC protocol credential in the Insight RS Console 261
Discover the device in the Insight RS Console 261
Verify discovery and device status 261

HPE Insight Remote Support 7.10: Monitored Devices Configuration Guide Page 12 of 436
 Verify communication between monitored device and Insight RS 261
Verify collections in the Insight RS Console 262

Chapter 20: Configuring NonStop Servers 263

Chapter 21: Configuring IBM servers 264

Fulfill configuration requirements 264
Install and configure communication software on servers 264
Configure the Windows SNMP service 264
Install and configure SNMP 266
Installing IBM Director Agent 266
Configuring the Management Module of the IBM BladeCenter® Chassis 267
Install IBM device drivers and service processor firmware 270
Add protocol credentials and start discovery 271
Create an SNMPv1 protocol credential in the Insight RS Console 271
Discover the device in the Insight RS Console 272
Configure warranty and contract information 272
Verify discovery and device status 272

Chapter 22: Configuring Dell PowerEdge servers 273

Fulfill configuration requirements 273
Install and configure communication software on servers 273
Configure the Windows SNMP service 273
Install and configure SNMP 275
Installing Dell OpenManage Server Administrator 275
Configuring SNMP Traps in Dell OpenManage Server Administrator 276
Add protocol credentials and start discovery 277
Create an SNMPv1 protocol credential in the Insight RS Console 277
Discover the device in the Insight RS Console 277
Configure warranty and contract information 277
Verify discovery and device status 278

Chapter 23: Configuring BladeSystem c-Class Enclosures 279

Configuring BladeSystem c-Class Enclosures through the OA 280
Fulfill configuration requirements 280
Configure monitored devices 280
Configure firewall and port settings 281
Register the OA and verify discovery 281
Register Remote Support through the Onboard Administrator 281
Verify discovery and device status 282
Verify communication between monitored device and Insight RS 282
Sending a test event 283
Verify collections in the Insight RS Console 283
Maintenance and troubleshooting 283

HPE Insight Remote Support 7.10: Monitored Devices Configuration Guide Page 13 of 436
 Disable monitoring of a BladeSystem c-Class Enclosure 283
Configuring BladeSystem c-Class Enclosures using SNMP 284
Fulfill configuration requirements 285
Install and configure communication software on enclosures 285
Configure SNMP on the BladeSystem c-Class enclosure 285
Option 1: Configure SNMPv1 285
Option 2: Configure SNMPv3 286
Configure firewall and port settings 288
Add Protocol credentials and start discovery 288
Create an SNMP protocol credential in the Insight RS Console 288
Option 1: SNMPv1 288
Option 2: SNMPv3 289
Discover the device in the Insight RS Console 289
Verify discovery and device status 290
Verify communication between monitored device and Insight RS 290
Verify service event monitoring 290
Verify collections in the Insight RS Console 290
Maintenance and troubleshooting 291
Disable monitoring of a BladeSystem c-Class Enclosure 291

Chapter 24: Configuring Virtual Connect Modules 292

Fulfill configuration requirements 292
Configure Communication Software on Virtual Connect Modules 292
Configure SNMP on the Virtual Connect Module 292
Configure firewall and port settings 293
Add protocol credentials and start discovery 293
Create an SNMP protocol credential in Insight RS Console 293
Discover the device in the Insight RS Console 294
Verify discovery and device status 294
Verify communication between monitored device and Insight RS 294
Verify collections in the Insight RS Console 294

Chapter 25: Configuring P6000 and Enterprise Virtual Arrays 296

Configuring P6000 and Enterprise Virtual Arrays using Server Based Management 296
Fulfill configuration requirements 296
Install and configure communication software for arrays 297
Install and configure P6000 Command View 297
P6000 Command View management server system and access requirements 298
Option 1: Install P6000 Command View on a separate management server 298
Option 2: Install P6000 Command View on the Hosting Device 299
Change WMI Mapper port configuration 299
Change SIM ports (if using SIM) 300
Install ELMC on the P6000 Command View server 301
ELMC requirements 301
Clear the Event Log 302
Install ELMC 302

HPE Insight Remote Support 7.10: Monitored Devices Configuration Guide Page 14 of 436
 Configure firewall and port settings 303
Add protocol credentials and start discovery 304
Create a P6000 Command View protocol credential in the Insight RS Console 304
Create an ELMC protocol credential in the Insight RS Console 305
Create a protocol credential in the Insight RS Console for your management server 305
Discover the EVA in the Insight RS Console 305
Verify discovery and device status 306
Verify warranty and contract information 306
Verify communication between monitored device and Insight RS 306
Sending a test event 306
Verify collections in the Insight RS Console 307
Maintenance and troubleshooting 308
Enable User-Initiated Service Mode in P6000 Command View 308
Perform a remote service test in P6000 Command View 308
Insight RS did not discover the EVA 309
Verify the EVA is managed by P6000 Command View on the target server 309
Troubleshooting the ELMC installation 309
Configuring P6000 and Enterprise Virtual Arrays using Array Based Management 309
Fulfill configuration requirements 309
Configure monitored devices 310
Configure firewall and port settings 310
Add Protocol credentials and start discovery 310
Create a P6000 Command View protocol in the Insight RS Console 310
Discover the ABM in the Insight RS Console 311
Verify discovery and device status 311
Verify communication between monitored device and Insight RS 312
Verify collections in the Insight RS Console 312

Chapter 26: Configuring StoreVirtual P4000 Storage systems 313

Fulfill configuration requirements 313
Install and configure communication software on storage systems 313
Install and configure CMC on the Hosting Device 313
Upgrade LeftHand OS on the P4000 Storage systems 315
Understand best practices 316
Select the type of upgrade 317
Increase the size of the OS disk on the VSAs 317
Verify management group version 318
Check for patches 318
Configuring SNMP on the P4000 Storage System 319
Configure firewall and port settings 324
Add protocol credentials and start discovery 324
Add P4000 SAN Solution (SAN/iQ) protocol to the Insight RS Console 325
Discover the P4000 in the Insight RS Console 325
Verify discovery 326
Add warranty and contract information 326

HPE Insight Remote Support 7.10: Monitored Devices Configuration Guide Page 15 of 436
 Verify discovery and device status 326
Verify communication between monitored device and Insight RS 327
Send a test event 327
Verify collections in the Insight RS Console 327

Chapter 27: Configuring P2000 G3, MSA 1040/2040/2050 storage 329

Fulfill configuration requirements 329
Install and configure communication software on arrays 329
Configure SNMP on your MSA 329
About WBEM on the P2000 G3, MSA 1040/2040/2050 331
Add protocol credentials and start discovery 331
Create an SNMPv1 protocol credential in Insight RS Console 331
Create a WBEM protocol credential in Insight RS Console 332
Discover the device in the Insight RS Console 332
Verify discovery and device status 332
Verify communication between monitored device and Insight RS 333
Verify service event monitoring 333
Verify collections in the Insight RS Console 333

Chapter 28: Configuring StoreEasy Storage systems 334

Fulfill configuration requirements 334
Configure StoreEasy devices 334
Configure firewall 334
Add protocol credentials and start discovery 335
Create a WMI protocol credential in Insight RS Console 335
Discover the device in the Insight RS Console 335
Verify discovery and device status 336
Verify communication between monitored device and Insight RS 336
Send a WMI test indication to the Hosting Device 336
Viewing test events in the Insight RS Console 337
Verify collections 337

Chapter 29: Configuring StoreAll Storage systems 339

Fulfill configuration requirements 339
Install and configure communication software on storage systems 339
Configure SNMP on the file serving nodes 339
Start or restart Insight Management Agents 340
Add protocol credentials and start discovery 341
Create an SNMPv1 protocol credential in the Insight RS Console 341
Discover the device in the Insight RS Console 341
Configure warranty and contract information 341
Verify discovery and device status 342

HPE Insight Remote Support 7.10: Monitored Devices Configuration Guide Page 16 of 436
 Verify communication between monitored device and Insight RS 342
Send a test trap 342
Verify collections 343

Chapter 30: Configuring StoreOnce Backup (D2D) systems 344

Fulfill configuration requirements 344
Install and configure communication software on backup systems 344
Verify the firmware version 344
Configure SNMP on your StoreOnce Backup (D2D) systems 344
Configure SNMP for StoreOnce Gen2 Backup (D2D) systems 345
Configure SNMP for StoreOnce Gen3 B6200 and 2600/4200/4400 Backup systems 345
Add protocol credentials and start discovery 346
Create an SNMPv1 protocol credential in the Insight RS Console 346
Discover the device in the Insight RS Console 346
Verify discovery and device status 347

Chapter 31: Configuring Virtual Library Systems 348

Fulfill configuration requirements 348
Install and configure communication software on Virtual Library Systems 348
Configure SNMP on the Virtual Library System 348
Add protocol credentials and start discovery 349
Create an SNMPv1 protocol credential in the Insight RS Console 349
Discover the device in the Insight RS Console 349
Verify discovery and device status 349
Verify communication between monitored device and Insight RS 350
Send a test event to verify the configuration 350
Verify collections in the Insight RS Console 350

Chapter 32: Configuring StoreEver Tape Libraries 351

Fulfill configuration requirements 351
Install and configure communication software on Tape Libraries 351
Configure Command View TL TapeAssure 351
Configuring Command View TL 3.1 and above 352
Verifying Command View TL is monitoring your Tape Libraries 352
Configure SNMP on your Tape Libraries 353
Configure Enterprise Systems Library E-series and Enterprise Modular Library 353
Configure Enterprise Systems Library G3 series 354
Configure Modular Systems Library G3 series 356
Configure Modular Systems Library MSL6480 357
Configure firewall and port settings 358
Add protocol credentials and start discovery 359
Create an SNMPv1 protocol credential in the Insight RS Console 359
Create a WBEM protocol credential in Insight RS Console 359

HPE Insight Remote Support 7.10: Monitored Devices Configuration Guide Page 17 of 436
 Discover the Tape Libraries in Insight RS 359
Verify warranty and contract information 360
Verify discovery and device status 360
Verify communication between monitored device and Insight RS 360
Verify collections in the Insight RS Console 360

Chapter 33: Configuring StoreFabric B-Series switches 362

Fulfill configuration requirements 362
Install and configure communication software on SAN switches 362
Configure SNMP 362
Option 1: Configure SNMPv1 362
Option 2: Configure SNMPv3 365
Configure firewall and port settings 370
Add protocol credentials and start discovery 370
Create an SNMP protocol credential in the Insight RS Console 370
Option 1: SNMPv1 370
Option 2: SNMPv3 371
Discover the device in the Insight RS Console 371
Verify discovery and device status 372
Verify warranty and contract information 372
Verify communication between monitored device and Insight RS 372
Send a test event 372
Verify collections in the Insight RS Console 373

Chapter 34: Configuring StoreFabric C-Series switches 374

Fulfill configuration requirements 374
Install and configure communication software on SAN switches 374
Configure SNMP 374
Configure firewall and port settings 375
Add protocol credentials and start discovery 375
Create an SNMPv1 protocol credential in the Insight RS Console 375
Discover the device in the Insight RS Console 375
Verify discovery and device status 376
Verify warranty and contract information 376
Verify communication between monitored device and Insight RS 376
Send a test event 376
Verify collections in the Insight RS Console 377

Chapter 35: Configuring StoreFabric H-Series switches 378

Fulfill configuration requirements 378
Install and configure communication software on SAN switches 378
Configure SNMP 378
Configure firewall and port settings 378

HPE Insight Remote Support 7.10: Monitored Devices Configuration Guide Page 18 of 436
 Add protocol credentials and start discovery 379
Create an SNMPv1 protocol credential in the Insight RS Console 379
Discover the device in the Insight RS Console 379
Verify discovery and device status 380
Verify warranty and contract information 380
Verify communication between monitored device and Insight RS 380
Verify collections in the Insight RS Console 380

Chapter 36: Configuring ProVision-based networking switches 381

Fulfill configuration requirements 381
Install and configure communication software on switches 381
Create operator/manager passwords 381
Configure SSH 381
Generate the Public/Private key for SSH 381
Enable SSH 382
Verify Telnet/SSH Communication 382
Configure SNMPv1/v2 communication 382
Configure SSH public key authentication 383
Option 1: Using the Hosting Device certificate 383
Prerequisites 383
Copy the certificate to the switch 383
Create an SSH protocol credential in the Insight RS Console 384
Option 2: Using other certificates 385
Prerequisites 385
Copy the certificate to the switch 385
Create an SSH protocol credential in the Insight RS Console 385
Configure firewall and port settings 386
Add protocol credentials and start discovery 386
Create an SNMPv1/v2 protocol credential in the Insight RS Console 387
Discover the device in the Insight RS Console 387
Verify discovery and device status 387
Verify communication between monitored device and Insight RS 388
Verify collections in the Insight RS Console 388

Chapter 37: Configuring Altoline networking switches 389

Fulfill configuration requirements 389
Configure switch and communication software on switches 389
Configure network and SNMP communication 389
Option 1: Configure Pica8 389
Configure the L2/L3 mode IP address 390
Set the IP address of the management port 390
Configure SNMP 390
Option 2: Configure Cumulus Linux 390
Set the IP address of the management interface 391

HPE Insight Remote Support 7.10: Monitored Devices Configuration Guide Page 19 of 436
 Configure SNMP 391
Add protocol credentials and start discovery 393
Create an SNMP protocol credential in the Insight RS Console 393
Create an SNMPv1 protocol credential in the Insight RS Console 393
Discover the device in the Insight RS Console 394
Add warranty and contract information 394
Verify discovery and device status 394

Chapter 38: Configuring Comware-based networking switches 395

Intelligent Resilient Framework Support 395
Fulfill configuration requirements 395
Install and configure communication software on switches 396
Configure Telnet or SSH 396
Configuring Telnet 396
Configuring SSH version 2 397
Verifying Telnet/SSH communication 397
Setup SNMPv1 traps 398
Configure firewall and port settings 398
Add protocol credentials and start discovery 399
Create an SNMPv1 protocol credential in the Insight RS Console 399
Create a Telnet or SSH protocol in the Insight RS Console 399
Create a Telnet protocol in the Insight RS Console 399
Create an SSH protocol credential in the Insight RS Console 399
Discover the device in the Insight RS Console 400
Verify discovery and device status 400
Verify warranty and contract information 400
Verify communication between monitored device and Insight RS 401
Verifying SNMP communication 401
Verify collections in the Insight RS Console 401

Chapter 39: Configuring Mellanox InfiniBand Switches 402

Fulfill configuration requirements 402
Install and configure communication software on switches 402
Setup SNMP traps 402
Configure SNMPv1/v2 402
Configure SNMPv3 403
Configure firewall and port settings 404
Add protocol credentials and start discovery 404
Create an SNMP protocol credential in the Insight RS Console 404
Create an SNMPv1/v2 protocol credential in the Insight RS Console 404
Create an SNMPv3 protocol credential in the Insight RS Console 404
Discover the device in the Insight RS Console 405
Verify discovery and device status 405

HPE Insight Remote Support 7.10: Monitored Devices Configuration Guide Page 20 of 436
 Verify communication between monitored device and Insight RS 406
Verifying SNMP communication 406
Verify collections in the Insight RS Console 406

Chapter 40: Configuring Intel Omni-Path Switches 407

Fulfill configuration requirements 407
Configure communication on switches 407
Setup SNMP traps 407
Configure SNMP 407
Add protocol credentials and start discovery 407
Create an SNMP protocol credential in the Insight RS Console 407
Create an SNMP protocol credential in the Insight RS Console 408
Discover the device in the Insight RS Console 408
Verify discovery and device status 408
Verify communication between monitored device and Insight RS 409
Verify collections in the Insight RS Console 409

Chapter 41: Configuring Networking Routers 410

Fulfill configuration requirements 410
Install and configure communication software on routers 410
Configure Telnet or SSH 410
Configuring Telnet 410
Configuring SSH version 2 411
Verifying Telnet/SSH communication 411
Setup SNMP Traps 411
Configure SNMPv1/v2 411
Configure SNMPv3 412
Configure firewall and port settings 413
Add protocol credentials and start discovery 413
Create an SNMP protocol credential in the Insight RS Console 413
Create an SNMPv1/v2 protocol credential in the Insight RS Console 413
Create an SNMPv3 protocol credential in the Insight RS Console 414
Create a Telnet or SSH Protocol in the Insight RS Console 414
Create a Telnet protocol in the Insight RS Console 414
Create an SSH protocol credential in the Insight RS Console 414
Discover the device in the Insight RS Console 415
Verify discovery and device status 415
Verify warranty and contract information 415
Verify communication between monitored device and Insight RS 416
Verifying SNMP communication 416
Verify collections in the Insight RS Console 416

Chapter 42: Configuring CS250-HC StoreVirtual System 417

HPE Insight Remote Support 7.10: Monitored Devices Configuration Guide Page 21 of 436
 Create local user ID 417
Configure the iLO 417
Configure discovery 417
Add protocol credentials 417
Add the 250-HC as a Solution 418

Chapter 43: Configuring Uninterruptable Power Supplies 420

Configuring UPS Management Modules 420
Fulfill configuration requirements 420
Install and configure communication software on Management Modules 420
Configure SNMP 420
Configure firewall and port settings 421
Add protocol credentials and start discovery 421
Create an SNMPv1 protocol credential in the Insight RS Console 421
Discover the device in the Insight RS Console 422
Verify discovery and device status 422
Verify communication between monitored device and Insight RS 422
Send a test trap 422
Configuring UPS Network Modules 423
Fulfill configuration requirements 423
Install and configure communication software on Network Modules 423
Configure SNMP 423
Add protocol credentials and start discovery 425
Create an SNMPv1 protocol credential in the Insight RS Console 425
Discover the device in the Insight RS Console 425
Verify discovery and device status 426
Verify communication between monitored device and Insight RS 426
Send a test trap 426

Chapter 44: Configuring VMware vCenter servers 427

Fulfill configuration requirements 428
Add protocol credentials and start discovery 428
Create a VMware VirtualCenter Web Service Interface protocol credential in the Insight RS
Console 428
Discover the ProLiant vCenter server in the Insight RS Console 429
Verify the status of ProLiant vCenter server in the Insight RS Console 429
Verify communication between monitored device and Insight RS 429
Verify collections in the Insight RS Console 429

Glossary 431

Index 436

HPE Insight Remote Support 7.10: Monitored Devices Configuration Guide Page 22 of 436
 Preface
Document purpose and audience
This document provides the necessary information to configure your monitored devices before discovering the
devices with HPE Insight Remote Support (RS).
This document is for HPE Customers and HPE Support Personnel who are installing, configuring, and using
Insight RS.

Product overview
Insight RS is a software solution that enables reactive and proactive remote support to improve the availability
of supported servers, storage systems, and other devices in your data center. Insight RS relies on several
HPE components and communication between various software applications within the customer enterprise
and between the customer enterprise and HPE to deliver support services. Software components may be
installed on the Hosting Device or on monitored devices depending on their purpose.
For more information about Insight RS, go to: www.hpe.com/services/getconnected.

Important: To configure Insight RS correctly, it is essential that you read this document thoroughly
before proceeding with the installation of Insight RS.

HPE Insight Remote Support 7.10: Monitored Devices Configuration Guide Page 23 of 436
Preface

Related documents
For additional Insight RS documentation, go to: www.hpe.com/info/insightremotesupport/docs.

l HPE Insight Remote Support Release Notes

This document provides product details and information about which monitored devices and Hosting
Devices are supported for use with the Insight RS solution.
l HPE Insight Remote Support Quick Installation Guide
This document provides a checklist for installing and configuring Insight RS.
l HPE Insight Remote Support Installation and Configuration Guide
This document provides detailed information about installing and configuring Insight RS.
l HPE Insight Remote Support Monitored Devices Configuration Guide
This document provides information to configure the devices that will be monitored by Insight RS.
l HPE Insight Remote Support Security White Paper
This document provides an overview of the security features available in Insight RS.
l HPE Insight Remote Support Upgrade Guide
This document provides information about upgrading Insight RS to version 7.10.
l HPE Insight Online Getting Started Guide
This document provides information about the prerequisites for using HPE Insight Online, and explains how
to use Insight Online to manage your company’s HPE devices, contracts and warranties.

Document revision history

Edition Software Version Publication Date Change Summary

1.1 7.10 April 2019 Update ProLiant Gen10 server user permission
requirements.

1.0 7.10 March 2019 Initial release.

Sign up to receive Insight Remote Support

communications
The HPE Insight Remote Support product team uses HPE’s Support Communication process to
communicate important news such as Engineering Advisories, Customer Advisories, Engineering Notices,
and Customer Notices.
To sign up to receive Support Communications using HPE Subscribers Choice, go to:
www.hpe.com/software/swupdatealerts.

HPE Insight Remote Support 7.10: Monitored Devices Configuration Guide Page 24 of 436
Preface

When you subscribe, search for Insight Remote Support.

Support information
HPE recommends you consult the Insight RS documentation to resolve issues. The documentation is
designed to guide you through a successful installation and configuration. However, if you need further
support for Insight RS, help is available through HPE local Response Centers. For contact details, go to:
www.hpe.com/us/en/services/get-connected.html#tehnical.
Before contacting support, you can check if your issue has a solution available. Note that a valid contract and
HPE Passport log on is required to view issue solution documents.
To view Insight RS issue solutions, complete the following steps:
1. Go to www.hpe.com/support/hpesc.
2. In the search field, type Insight Remote Support and click the product name in the suggested results.
3. Click the Documents tab and use the filters to narrow the results to support information, advisories, and
notices.

HPE Insight Remote Support 7.10: Monitored Devices Configuration Guide Page 25 of 436
 Chapter 1: Understanding monitored devices prerequisites
To use Insight Remote Support (RS) you need at least two pieces of hardware: a supported Windows ProLiant server to be used as the Hosting Device
and one or more devices to be monitored by Insight RS. Use the table below to identify what protocols and software components are necessary for your
monitored devices and then go to the information for your specific devices for complete configuration details. Before you get started, verify Insight RS
supports your monitored devices by consulting the HPE Insight Remote Support Release Notes.
Insight RS checks every device’s warranty and contract to make sure it has a valid HPE warranty or contract. If a device has no HPE warranty or
contract, the monitoring health indicator in the Insight RS Console will be red. If this is red, then no service events will be analyzed or sent to HPE.

Identify required communication protocols and software components

Monitored devices can communicate with the Hosting Device using one or more of the following communication protocols and software components:
l Embedded Support Automation Protocol (ESA)
l Event Log Monitoring Collector (ELMC)
l HP P6000 Command View
l Hypertext Transfer Protocol Secure (https)
l Hypertext Transport Protocol (http)
l P4000 SAN Solution (SAN/iQ)
l REST Protocol
l Secure Shell (SSH)
l Simple Network Management Protocol Version 1, V2C (SNMPv1, SNMPv2C)
l Simple Network Management Protocol Version 3 (SNMPv3)

Important: Insight RS only supports SNMPv3 traps, and does not support SNMPv3 Informs. Insight RS listens on port 1162 for SNMPv3
traps, and your SNMPv3 passwords must be at least 8 characters long. Refer to your device's documentation to determine the versions of
SNMP your device supports.

l Telnet
l VMware VirtualCenter Web Service Interface
l Web Services Management Protocol (WS-Man)

HPE Insight Remote Support 7.10: Monitored Devices Configuration Guide Page 26 of 436
Chapter 1: Understanding monitored devices prerequisites

l Web-Based Enterprise Management (WBEM)

l Windows Management Instrumentation (WMI)
l iLO Remote Insight Board Command Language Protocol (RIBCL)
If you do not configure the required protocols and software for your monitored devices, the devices will not communicate with the Hosting Device and
your events and configuration collections will not be sent to HPE for support.

Important: Not only do you need to configure the protocol on the monitored device, you must also add the protocol within the Insight RS
Console so Insight Remote Support can access the device.

Important: If you change the username/password that Insight RS uses to connect to your monitored devices, or if the credentials expire as
part of your security policies, you must modify those corresponding credentials in the Insight RS Console to continue monitoring your
monitored devices.

Important: Insight RS requires administrator access to the monitored devices. Discovery and collections require privileged access in order to
retrieve information about the monitored devices.

The required protocols and software are determined by your monitored device type. Read the appropriate monitored device section to understand what
configuration is necessary for your specific monitored device. Some monitored device types can use multiple communication protocols. Which protocol
you choose depends on your security strategy and preferences.
In some cases more than one protocol will be required. Some protocols may be used by the Insight RS Console to discover monitored devices while
other protocols may be used to monitor hardware events or retrieve configuration collection information from the monitored devices. The following table
highlights the requirements, but read the section for your monitored device type for more detail.
Assign devices to SAN collections on the Collection Services → Collection Schedules tab of the Insight RS Console in the SAN Configuration
Collection Schedule. See the Help for more information about setting up your SAN collections.

HPE Insight Remote Support 7.10: Monitored Devices Configuration Guide Page 27 of 436
Chapter 1: Understanding monitored devices prerequisites

Table 1.1 Required monitored device communication protocols and components for Insight RS
Discovery Monitoring Basic SAN Notes
Collections Collections

HPE Servers

ProLiant Gen10 RIBCL RIBCL RIBCL See "Configuring ProLiant Gen10 servers" on page 39.

ProLiant Gen8 and RIBCL RIBCL RIBCL HPE ProLiant Gen8 and Gen9 servers can be monitored using one
Gen9 of two methods:
l Through the embedded Remote Support functionality available
through iLO 4 and Intelligent Provisioning.
See "Configuring ProLiant Gen8 and Gen9 servers" on page 48.
l Using a diagnostic agent installed on the operating system.
See the ProLiant server row below that corresponds to your
operating system for protocol requirements, however, make sure
you also configure RIBCL credentials in addition to the agent
credentials.
Important: RIBCL credentials are required for all ProLiant Gen8
and Gen9 servers even when the diagnostic agent are used.
Note: If you want to monitor attached devices you need to install the
HPE Service Pack for ProLiant as detailed in the ProLiant server
section that corresponds to the operating system below.

Edgeline EL1000 RIBCL RIBCL RIBCL HPE Edgeline EL1000 and EL4000 systems should be configuring
and EL4000 using the iLO 4 procedure for ProLiant Gen8 and Gen9 servers.
systems
See "Configuring ProLiant Gen8 and Gen9 servers" on page 48.

HPE Insight Remote Support 7.10: Monitored Devices Configuration Guide Page 28 of 436
Chapter 1: Understanding monitored devices prerequisites

Table 1.1 Required monitored device communication protocols and components for Insight RS, continued
Discovery Monitoring Basic SAN Notes
Collections Collections

Windows on SNMP SNMP SNMP You must install the HPE Service Pack for ProLiant and all providers
ProLiant or WMI or WMI or WMI that ship with it.
You can choose to use either SNMP or WMI, however to gather SAN
Collections for a ProLiant Windows server, you must use WMI.
Insight RS requires Insight Management WBEM Providers version
2.8 or later, but HPE recommends installing the most recent version
available for your device.

WMI Note: If your ProLiant server is Gen8 or later, RIBCL credentials are
required even when the diagnostic agent are used.
For configuring using WMI, see "Configuring ProLiant Windows
servers using WMI" on page 60.
For configuring using SNMP, see "Configuring ProLiant Windows
servers using SNMP" on page 67.

Linux on ProLiant SNMP SNMP SNMP Must install the HPE Service Pack for ProLiant and all providers that
ship with it.
Note: If your ProLiant server is Gen8 or later, RIBCL credentials are
Telnet or SSH required even when the diagnostic agent are used.
See "Configuring ProLiant Linux servers" on page 76.

VMware® ESX® on SNMP SNMP SNMP Note: If your ProLiant server is Gen8 or later, RIBCL credentials are
ProLiant required even when the diagnostic agent are used.
SSH See "Configuring ProLiant VMware ESX servers" on page 83.

VMware® ESXi™ WBEM WBEM WBEM WBEM Note: If your ProLiant server is Gen8 or later, RIBCL credentials are
on ProLiant required even when the diagnostic agent are used.
See "Configuring ProLiant VMware ESXi servers" on page 89.

Citrix Xen Server on SNMP SNMP SNMP Note: If your ProLiant server is Gen8 or later, RIBCL credentials are
ProLiant required even when the diagnostic agent are used.
Telnet or SSH See "Configuring ProLiant Citrix XenServers" on page 93.

HPE Insight Remote Support 7.10: Monitored Devices Configuration Guide Page 29 of 436
Chapter 1: Understanding monitored devices prerequisites

Table 1.1 Required monitored device communication protocols and components for Insight RS, continued
Discovery Monitoring Basic SAN Notes
Collections Collections

Hyper-V Server on SNMP SNMP Configuration collections are not supported on the Hyper-V guest.
ProLiant or WMI or WMI
For monitoring, follow the configuration instructions for a ProLiant
Windows server.
Note: If your ProLiant server is Gen8 or later, RIBCL credentials are
required even when the diagnostic agent are used.
See "Configuring ProLiant Windows servers" on page 60.

Windows 2003 on WMI WMI WMI WMI Must install the Integrity Support Pack and all providers that ship with
Integrity it. This includes the installation of SNMP and WMI.
SNMP SNMP SNMP
See "Configuring Integrity Windows 2003 servers" on page 100.
ELMC

Windows 2008 on WMI WMI WMI WMI Must install the HPE Integrity Support Pack and all providers that
Integrity ship with it.
See "Configuring Integrity Windows 2008 servers" on page 109.

Linux on Integrity WBEM WBEM Configuration collections are not supported, except when the server
is part of a SAN collection. You can choose to use either Telnet or
SSH to gather SAN collections for an Integrity Linux server.
Telnet or SSH
See "Configuring Integrity Linux servers" on page 115.

HP-UX on Integrity WBEM WBEM WBEM Install the proper WBEM providers on HP-UX. These generally are
part of the feature set of HP-UX and will update through patches and
software updates on the device as appropriate.
You can choose to use either Telnet or SSH to gather SAN
Telnet or SSH collections for an Integrity HP-UX server.
See "Configuring Integrity and HP 9000 HP-UX servers" on
page 119.

HPE Integrity WS-Man WS-Man WS-Man Discovery and collections use WS-Man. The OA is monitored using
Superdome 2 WS-Man, but the Superdome 2 partitions are monitored using
Onboard WBEM.
Administrator (OA)
See "Configuring Integrity Superdome 2 servers" on page 141.

HPE Insight Remote Support 7.10: Monitored Devices Configuration Guide Page 30 of 436
Chapter 1: Understanding monitored devices prerequisites

Table 1.1 Required monitored device communication protocols and components for Insight RS, continued
Discovery Monitoring Basic SAN Notes
Collections Collections

HPE Integrity WS-Man WS-Man WS-Man The partitions are monitored through the OA using WS-Man.
Superdome X
For collections, Insight RS communicates directly with the partition:
Onboard
Administrator (OA) l Linux partitions communicate using WS-Man.
l Windows partitions communicate using WinRM (WS-Man).
l VMware partitions communicate using WBEM.
See "Configuring Integrity Superdome X servers" on page 147.

HPE Superdome ESA ESA ESA See "Configuring Superdome Flex servers" on page 160.
Flex

HPE OpenVMS on WBEM or WBEM Must install the HPE OpenVMS WBEM provider.
Integrity SNMP
Configuration collections and discovery only works when the WBEM
ELMC providers are installed and the credentials are properly configured.

Telnet or SSH See "Configuring HPE OpenVMS Integrity servers" on page 164.

VSI OpenVMS on WBEM or WBEM Must install the VSI OpenVMS WBEM provider.
Integrity SNMP
Configuration collections and discovery only works when the WBEM
providers are installed and the credentials are properly configured.
ELMC
See "Configuring VSI OpenVMS Integrity servers" on page 204.

HPE OpenVMS on SNMP Configuration collections are not supported, except when the
AlphaServer OpenVMS server is part of a SAN collection.
ELMC
See "Configuring HPE OpenVMS AlphaServers" on page 231 and
Telnet or SSH the special note on support for this platform.

Tru64 UNIX on SNMP Configuration collections are not supported, except when the Tru64
AlphaServer server is part of a SAN collection.
ELMC You can choose to use either Telnet or SSH to gather SAN
Collections for a Tru64 Unix server.
Telnet or SSH See "Configuring Tru64 UNIX servers" on page 256 and the special
note on support for this platform.

HPE Insight Remote Support 7.10: Monitored Devices Configuration Guide Page 31 of 436
Chapter 1: Understanding monitored devices prerequisites

Table 1.1 Required monitored device communication protocols and components for Insight RS, continued
Discovery Monitoring Basic SAN Notes
Collections Collections

HP-UX on HP 9000 WBEM WBEM WBEM Install the proper WBEM providers on HP-UX. These generally are
part of the feature set of HP-UX and will update through patches and
software updates on the device as appropriate.
You can choose to use either Telnet or SSH to gather SAN
Telnet or SSH collections for an HP-UX server.
See "Configuring Integrity and HP 9000 HP-UX servers" on
page 119.

E5000 Messaging SNMP or WMI SNMP or WMI SNMP or WMI These devices should be configured the same as a Windows
Systems ProLiant server.

WMI You can choose to use SNMP or WMI, however to gather SAN
Collections, you must use WMI.
Configuration collections for the chassis connector use HTTP.
HTTP
See "Configuring ProLiant Windows servers" on page 60.

HPE NonStop (See Notes) For more details on how to install and configure Insight RS for use in
systems a NonStop environment, see the Insight Remote Support for
NonStop document available at www.hpe.com/info/nonstop-
serviceinfo.

Non-HPE Servers

Windows on IBM SNMP SNMP Configuration collections are not supported.

Servers
See "Configuring IBM servers" on page 264.

Windows on Dell SNMP SNMP Configuration collections are not supported.

PowerEdge
See "Configuring Dell PowerEdge servers" on page 273.

HPE Insight Remote Support 7.10: Monitored Devices Configuration Guide Page 32 of 436
Chapter 1: Understanding monitored devices prerequisites

Table 1.1 Required monitored device communication protocols and components for Insight RS, continued
Discovery Monitoring Basic SAN Notes
Collections Collections

HPE BladeSystems

HPE Onboard Registration Registration HPE BladeSystem c-Class Enclosures can be monitored using the
Administrator for c- through the through the embedded management capabilities in the HPE Onboard
Class Enclosures OA OA Administrator (OA) or by configuring SNMP in the OA.
or or See "Configuring BladeSystem c-Class Enclosures" on page 279.
SNMP SNMP For configuring the OA, see "Configuring BladeSystem c-Class
Enclosures through the OA" on page 280.
Registration
through the For configuring using SNMP, see "Configuring BladeSystem c-Class
OA Enclosures using SNMP" on page 284.

or
HTTPS

HPE ProLiant (See Notes) Supported ProLiant BladeSystem servers are monitored
BladeSystem independent of the c-Class Enclosure in which they are installed.
Servers ProLiant BladeSystem servers can be configured using the
instructions for ProLiant servers.
For configuration details, see the ProLiant server section that
corresponds to the operating system installed on the ProLiant
BladeSystem server.

HPE Integrity (See Notes) Supported Integrity BladeSystem servers are monitored independent
BladeSystem of the c-Class Enclosure in which they are installed. Integrity
Servers BladeSystem servers can be configured using the instructions for
Integrity servers.
For configuration details, see the Integrity server section that
corresponds to the operating system installed on the Integrity
BladeSystem server.

Storage Blades (See Notes) Configuration collections are not supported.

Storage Blades are monitored through the Storage Agents installed
on the partner server blade. The partner server blade is the adjacent
server blade connected directly to the storage blade.

HPE Insight Remote Support 7.10: Monitored Devices Configuration Guide Page 33 of 436
Chapter 1: Understanding monitored devices prerequisites

Table 1.1 Required monitored device communication protocols and components for Insight RS, continued
Discovery Monitoring Basic SAN Notes
Collections Collections

Tape Blades (See Notes) Configuration collections are not supported.

Tape Blades are monitored through the Storage Agents installed on
the partner server blade. The partner server blade is the adjacent
server blade connected directly to the tape blade.

Virtual Connect SNMP SNMP SNMP SNMP See "Configuring Virtual Connect Modules" on page 292.
Modules

HPE Disk Arrays

P6000 Enterprise HP P6000 HP P6000 HP P6000 HP P6000 For configuring with Server Based Management, see "Configuring
Virtual Arrays SBM Command Command Command Command P6000 and Enterprise Virtual Arrays using Server Based
View View View View Management" on page 296.

ELMC

P6000 Enterprise HP P6000 HP P6000 HP P6000 HP P6000 For configuring with Array Based Management, see "Configuring
Virtual Arrays ABM Command Command Command Command P6000 and Enterprise Virtual Arrays using Array Based
View View View View Management" on page 309.

HPE StoreVirtual SNMP SNMP See "Configuring StoreVirtual P4000 Storage systems" on page 313.
4xxx (formerly
P4000 SAN
Solutions/ LeftHand LeftHand OS LeftHand OS LeftHand OS
Storage)

HPE MSA 1040 SNMP SNMP Both SNMP and WBEM must be installed and configured.
HPE MSA 2040 See "Configuring P2000 G3, MSA 1040/2040/2050 storage" on
WBEM WBEM WBEM WBEM page 329.
HPE MSA 2050

HPE P2000 G3 SNMP SNMP Both SNMP and WBEM must be installed and configured.
MSA
See "Configuring P2000 G3, MSA 1040/2040/2050 storage" on
WBEM WBEM WBEM WBEM page 329.

StoreEasy Storage WMI WMI WMI WMI See "Configuring StoreEasy Storage systems" on page 334.

HPE Insight Remote Support 7.10: Monitored Devices Configuration Guide Page 34 of 436
Chapter 1: Understanding monitored devices prerequisites

Table 1.1 Required monitored device communication protocols and components for Insight RS, continued
Discovery Monitoring Basic SAN Notes
Collections Collections

HPE StoreAll SNMP SNMP SNMP See "Configuring StoreAll Storage systems" on page 339.
Network Storage
Systems (formerly
HPE IBRIX Storage)

HPE XP/P9000 (See Notes) For supported models, see HPE Insight Remote Support Release
Notes.
Registration with Insight RS occurs during the Truststore
configuration on the SVP. Note that XP/P9000 devices are not
serviceable by customers. Support on XP/P9000 devices is
delivered as part of your Mission Critical Support contract. Please
contact your local HPE account representative for help to implement
this solution.

Data Protection

HPE StoreOnce SNMP SNMP Configuration collections are not supported.

Backup (D2D)
See "Configuring StoreOnce Backup (D2D) systems" on page 344.

HPE Virtual Library SNMP SNMP Configuration collections are not supported, except when the VLS is
System (VLS) part of a SAN collection.
SSH See "Configuring Virtual Library Systems" on page 348.

HPE StoreEver SNMP SNMP SNMP See "Configuring StoreEver Tape Libraries" on page 351.
MSL (formerly
Modular Systems
Library)

HPE StoreEver ESL SNMP SNMP WBEM is supplied through Command View for Tape Libraries,
(formerly Enterprise installed on the server managing the tape libraries.
Systems Library) WBEM
See "Configuring StoreEver Tape Libraries" on page 351.
Telnet or SSH

HPE Insight Remote Support 7.10: Monitored Devices Configuration Guide Page 35 of 436
Chapter 1: Understanding monitored devices prerequisites

Table 1.1 Required monitored device communication protocols and components for Insight RS, continued
Discovery Monitoring Basic SAN Notes
Collections Collections

HPE StoreEver SNMP SNMP WBEM is supplied through Command View for Tape Libraries,
EML (formerly installed on the server managing the tape libraries.
Enterprise Modular WBEM
See "Configuring StoreEver Tape Libraries" on page 351.
Library) Telnet or SSH

HPE StoreFabric SAN Switches

B-Series SAN SNMP SNMP See "Configuring StoreFabric B-Series switches" on page 362.
Switches
Telnet or SSH Telnet or SSH

C-Series SAN SNMP SNMP SNMP SNMP See "Configuring StoreFabric C-Series switches" on page 374.
Switches

H-Series SAN SNMP SNMP SNMP SNMP See "Configuring StoreFabric H-Series switches" on page 378.
Switches

HPE Networking Switches and Routers

HPE ProVision- SNMP SNMP See "Configuring ProVision-based networking switches" on

based Switches page 381.
(formerly E- Telnet or SSH
Series/ProCurve)

Aruba 3810 (See Notes) Configure Aruba 3810 Switches using the ProVision-based Switch
Switches procedure.
See "Configuring ProVision-based networking switches" on
page 381.

Altoline Switches SNMP SNMP Configuration collections are not supported.

See "Configuring Altoline networking switches" on page 389.

HPE Insight Remote Support 7.10: Monitored Devices Configuration Guide Page 36 of 436
Chapter 1: Understanding monitored devices prerequisites

Table 1.1 Required monitored device communication protocols and components for Insight RS, continued
Discovery Monitoring Basic SAN Notes
Collections Collections

HPE ComWare- SNMP SNMP See "Configuring Comware-based networking switches" on

based Switches page 395.
(formerly A-Series
or H3C/3Com) Telnet or SSH

Mellanox InfiniBand SNMP SNMP SNMP SNMP See "Configuring Mellanox InfiniBand Switches" on page 402.
Switches

Intel Omni-Path SNMP SNMP See "Configuring Intel Omni-Path Switches" on page 407.
Switches

HPE Networking SNMP SNMP See "Configuring Networking Routers" on page 410.

Routers
Telnet or SSH

Rack and Power

HPE Rack- SNMP SNMP Configuration collections are not supported.

mountable and
If your UPS uses a Management Module, see "Configuring UPS
Tower UPS
Management Modules" on page 420.
If your UPS uses a Network Module, see "Configuring UPS Network
Modules" on page 423.

Applications

VMware® VMware VMware Gathers configuration collections on the ESX and ESXi virtual
vCenter™ Server VirtualCenter VirtualCenter machines in the VMware vCenter cluster.
on ProLiant Web Service Web Service
See "Configuring VMware vCenter servers" on page 427.
Interface Interface

HPE Insight Remote Support 7.10: Monitored Devices Configuration Guide Page 37 of 436
Chapter 1: Understanding monitored devices prerequisites

Functionality not supported in Insight RS 7.10

The following devices and functionality were supported in 5.x versions of Insight RS, but are not supported in version 7.10:
Table 1.2 Insight RS 5.x functionality not available in Insight RS 7.10
Functionality Details

Hosting Device l All Microsoft Windows 2003 operating system versions will not be supported on any Insight RS 7.x
versions.

Products that will not be supported by any 7.x l HPE Enterprise Secure Key Manager
version
l HPE Secure Key Manager
l HPE Dynamic Smart Cooling
l HPE SAN Virtualization Services Platform
l HPE Modular Array
l HPE Enterprise Modular Array
l HPE Raid Array
l HPE Enterprise Storage Array
l M-series Switches (McData)
l Carrier-grade Servers (cx2620, cc3310)
l HP 9000 rp2400 series (A-Class), rp5400 series (L-Class), and D,K,R,T,V (Class) servers
l PA-RISC versions of HP 9000 SD-A and SD-B servers
l HPE Neoview Systems
l IBM AIX servers
l Sun Solaris servers

Mission Critical Service Delivery Capabilities to deliver the following mission critical services:
(Insight RSA only)
l HP-UX System Health Check assessments (not available within Insight RS 7.x, but available as a
standalone client)
l TAM-S and CCMon Services
l Unreachable Device Notification

HPE Insight Remote Support 7.10: Monitored Devices Configuration Guide Page 38 of 436
 Chapter 2: Configuring ProLiant Gen10
servers
The Insight Remote Support (RS) feature available through the iLO 5 web interface provides intelligent event
diagnosis and automatic secure submission of event notifications to HPE and your HPE Authorized Channel
Partner through the Insight RS installation on the Hosting Device.

Note: When connecting to a ProLiant Gen10 server through the iLO, the iLO will maintain a
connection to Insight RS even when the operating system of the server has changed or after an
update to the iLO firmware.

For more information about ProLiant Gen10 servers, go to: www.hpe.com/info/proliantgen10-docs.

Fulfill configuration requirements

To configure your ProLiant Gen10 servers to be monitored by Insight RS, complete the following sections:
Table 2.1 ProLiant Gen10 configuration steps
Task Required/ Complete?
Optional

Make sure Insight RS supports your ProLiant server by checking the HPE Required
Insight Remote Support Release Notes.

Make sure the operating system on the ProLiant server is running. Required

Install and configure the Agentless Management Service (AMS) on the Optional
ProLiant server if you want your host name or IP displayed instead of the
device's serial number.

Verify a supported version of the iLO 5 firmware is installed on your ProLiant

server. HPE recommends version 1.15.

iLO 5 firmware version Feature details

1.15 Minimum version for Active Health Service

(AHS) data to be successfully processed by the
Active Health System Viewer.

You can download the latest firmware from the HPE website:
www.hpe.com/support/ilo5.

Add the RIBCL protocol to the Insight RS Console. Required

Discover the ProLiant server in the Insight RS Console. Required

Send a test event to verify connectivity between your ProLiant server and Required
Insight RS.

Configure monitored devices

To configure your monitored devices, complete the following section:

HPE Insight Remote Support 7.10: Monitored Devices Configuration Guide Page 39 of 436
Chapter 2: Configuring ProLiant Gen10 servers

Install and configure software

Ensure that you have the required files to set up or update a ProLiant server. Depending on your configuration,
you might need the following files:
l Service Pack for ProLiant (all supported OS except for Ubuntu)—The SPP includes the iLO firmware,
drivers, and AMS. You can also download the individual components separately. Download the SPP from
the following website: www.hpe.com/servers/spp.
l Management Component Pack (Ubuntu)—The MCP includes the iLO drivers and AMS but it does not
contain the iLO firmware. Download the MCP from the following website: www.hpe.com/support/SDR-
Linux.
l iLO firmware—Download the iLO firmware from the following website: www.hpe.com/support/ilo5.
l iLO 5 Channel Interface Driver—Download the iLO driver from the following website:
www.hpe.com/info/hpesc.
On Windows servers, install the iLO 5 Channel Interface Driver if it is not already installed. This driver is
installed automatically if you use the Intelligent Provisioning Recommended installation method for
Windows installation.
This driver ships standard with SuSE Linux Enterprise Server 11 and 12 and Red Hat Enterprise Linux 6
and 7. Verify the driver is loaded with the following command:
# modinfo hpilo
l Agentless Management Service (recommended)—AMS is installed automatically if you use the Intelligent
Provisioning Recommended installation method for Windows installation. Using AMS is one way in which
iLO can obtain the server name. If iLO cannot obtain the server name, the displayed server name in Insight
Online and Insight RS is derived from the server serial number.
For HPE Proactive Care services customers, AMS installation is required to receive the following
Proactive Care features: Proactive Scan Report and Firmware and Software Version Report.
Download AMS from the following websites:
l Hewlett Packard Enterprise Support Center (all supported OS except Ubuntu):
www.hpe.com/info/hpesc.
l Software Delivery Repository (Ubuntu): www.hpe.com/support/SDR-Linux.
If you did not install AMS, do one of the following to ensure that the server name is displayed correctly in
Insight Online and Insight RS:
l For Windows systems only, start the operating system. Insight Online and Insight RS will use the
Windows computer name to identify the server.
l Configure the Server Name on the Access Settings page in the iLO web interface.
To protect your privacy, do not use sensitive information in the server name. The server name is
displayed in Insight Online and Insight RS.
l Verify that the time zone is set in iLO. If the Time Zone value is incorrect, Insight Online will display
incorrect time stamps for events and data collections.
l Verify that a DNS server is configured in iLO. By default, iLO is set to use DHCP to configure DNS servers
and other network settings. The DNS server is required for communication between iLO and Insight Online.

HPE Insight Remote Support 7.10: Monitored Devices Configuration Guide Page 40 of 436
Chapter 2: Configuring ProLiant Gen10 servers

Verify user permissions

If you want to use a non-administrator user to discover and manage your ProLiant Gen10 server, the user
must have both the Login and Configure iLO Setting privileges.
The verify the user privileges, complete the following steps:
1. Log on to the iLO 5 web interface (https://<iLO hostname or IP address>).
2. Navigate to the Administration → User Administration.
The Local Users table shows the login names, user names, and assigned privileges of each configured
user. Verify the Login and Configure iLO Setting privileges are enabled. You can move the cursor
over an icon to see the privilege name.
For more information about configuring users, see the iLO 5 User Guide at: www.hpe.com/support/ilo-docs.

Configure firewall and port settings

Note: The below table shows the hardware requirements only; operating system port requirements
should also be configured.

Table 2.2 ProLiant Gen10 Connectivity - Firewall/Port Requirements

Protocol Ports Source Destination Function Optional

ICMP N/A Hosting Monitored Provides system reachability (ping) check during Required
Device Systems system discovery and before other operations.

TCP 443 Hosting Onboard RIBCL Event Listener. Required

Device Administrator

TCP 7906 Onboard Hosting Secure HTTP (HTTPS) port used by the listener Required
Administrator Device running on the Embedded Support Device. The
management device connects to the Hosting Device
iLO 5
on this port (e.g. https://<hostname>:7906).

Add protocol credentials and start discovery

To discover your monitored devices, complete the following sections:

Create a RIBCL protocol credential in the Insight RS

Console
Important: Insight RS requires RIBCL. Make sure the iLO RIBCL Interface is enabled in the iLO 5
UI on the Security → Access Settings screen.

To enable Insight RS to gather Active Health Service collections, you must set up the iLO Remote Insight
Board Command Language (RIBCL) protocol credentials in the Insight RS Console.
To configure RIBCL in the Insight RS Console, complete the following steps:

HPE Insight Remote Support 7.10: Monitored Devices Configuration Guide Page 41 of 436
Chapter 2: Configuring ProLiant Gen10 servers

1. In a web browser, log on to the Insight RS Console.

2. In the main menu, select Discovery and click the Credentials tab.
3. From the Select and Configure Protocol drop-down list, select iLO Remote Insight Board
Command Language Protocol (RIBCL).
4. Click New. The New Credential dialog box appears.
5. Fill in the required fields. Use the Username and Password of the iLO web interface on the ProLiant
server.
6. Click Add.
Add a RIBCL protocol credential for each unique username and password on your ProLiant servers.
Insight RS creates the protocol credential and it appears in the credentials table.

Define discovery subnets if desired

When discovering an iLO 5 that presents multiple server IP addresses, the default behavior of Insight RS is to
select one of the available IP addresses based on the following preferences:
"10.0.0.0/8,172.16.0.0/12,192.168.0.0/16,169.254.0.0/16,0.0.0.0/0" where 0.0.0.0/0
represents a non-private IP range and the 10. network has the highest preference. If multiple IP addresses
exist within any of the subnets the selection behavior within that subnet is random.
A configuration command has been added to allow you to redefine this preference order and to define it more
discreetly. The command takes the following form:
rsadmin config –set siteipv4subnet.preference=<ipv4>/<prefix>[,<ipv4>/<prefix>…]
where a multiple subnet preference can be defined.
You can use the command to define a more discreet preferred IPv4 subnet, for example: 10.2.x.x over
10.1.x.x.
Example:
rsadmin config –set siteipv4subnet.preference=10.2.0.0/16
You can choose to prefer 192.168.x.x subnet over all others.
Example:
rsadmin config –set siteipv4subnet.preference=192.168.0.0/16
You can also define two or more preferences.
Example:
rsadmin config –set siteipv4subnet.preference=10.2.0.0/16,10.1.0.0/16
If the device is not reachable on the preferred subnet, Insight RS will continue to search the preference list.
For example, if the iLO shows us a 10. network and Insight RS does not have a 10. connection, Insight RS
continues searching.

Discover the ProLiant Gen10 server

Enable the ProLiant Gen10 server for Insight Remote Support in one of two ways:

HPE Insight Remote Support 7.10: Monitored Devices Configuration Guide Page 42 of 436
Chapter 2: Configuring ProLiant Gen10 servers

l Discover the ProLiant server from the Insight RS Console.

See "Discovering the ProLiant server from the Insight RS Console" below.
l Register Remote Support from the ProLiant server iLO 5 web interface.
See "Enabling Insight Remote Support for a ProLiant server" below.
Discovering the ProLiant server from the Insight RS Console
To discover the ProLiant server from the Insight RS Console, complete the following steps:
1. In a web browser, log on to the Insight RS Console.
2. In the main menu, select Discovery and click the Sources tab.
3. Expand the IP Addresses section and add the IP address for your device:
a. Click New.
b. Select the Single Address, Address Range, or Address List option.
c. Type the IP address(es) of the devices to be discovered. Use the IP address of the iLO.
d. Click Add.
4. Click Start Discovery.
Enabling Insight Remote Support for a ProLiant server
With the HPE iLO Management Engine, no additional protocols need to be installed on the ProLiant server.
You only need to register the ProLiant server with your Hosting Device to enable Insight Remote Support. You
can register Insight Remote Support for a ProLiant server in the iLO 5 web interface.
Use the Remote Support → Registration screen to register and enable Remote Support. You must have the
Configure iLO Settings privilege to modify the Remote Support settings.
To enable a ProLiant server for Insight Remote Support, complete the following steps:
1. Log on to the iLO 5 web interface (https://<iLO hostname or IP address>).
2. In the navigation menu, click Remote Support → Registration. The Register and Enable Automated
Support screen appears.
3. Select Connect this server through an HPE remote support host server.
4. Complete the Hostname or IP address field.
5. In the Port field, type 7906.
6. Click Register. The iLO 5 web interface registers the device and a confirmation message appears.

Note: After registration, you may see both the ProLiant server and the iLO 5 web interface listed in
the Insight RS Console. The iLO 5 web interface will disappear if the ProLiant server and the RIBCL
credentials have been configured correctly.

Note: After discovery, the operating system for the ProLiant server will not appear in the Insight RS
Console. This is expected behavior.

HPE Insight Remote Support 7.10: Monitored Devices Configuration Guide Page 43 of 436
Chapter 2: Configuring ProLiant Gen10 servers

Verify discovery and device status

To verify the device was discovered correctly, complete the following steps:
1. In a web browser, log on to the Insight RS Console.
2. In the main menu, select Devices and click the Device Summary tab.

3. Make sure the Status column contains a success icon ( ).

If there is no success icon, determine which column has the problem and consult the Online Help for
troubleshooting information.

Test communication from the ProLiant Gen10

server to Insight RS
To verify communication between your monitored device and Insight RS, complete the following sections:

Verify service event monitoring

After registering the ProLiant server with Insight Remote Support, send a test event to confirm the connection.

Note: Sending SNMP test traps from the iLO 5 web interface Administration → Management
page is not supported in Insight Remote Support. To send a test event, do so from the Remote
Support → Service Events page as shown below.

To send a test event, complete the following steps:

1. Log on to the iLO 5 web interface (https://<iLO hostname or IP address>).
2. In the navigation menu, click Remote Support → Service Events. The Service Events screen appears.
3. Click Send Test Event. The following message appears:
Are you sure you want to send a test event?
4. Click OK to confirm that you want to send the test event. The following messages appear:
Test Service Event Transmission has been initiated
Service Event transmission in progress.
When the transmission is complete, the test event is listed in the Service Event Log and in the Insight
RS Console. If the test is successful, the Submit Status column displays the text No Error.
The Time Generated column in the Service Event Log shows the date and time based on the configured
iLO time zone.
5. Check the Insight RS Console to verify that the test event arrived:
a. Log on to the Insight RS Console.
b. In the main menu, select Devices.
c. Find the ProLiant server and click the device name.
d. Click the Service Events tab. All service events submitted against the system display in the
Service Events screen (even if you clear the Service Event Log).

HPE Insight Remote Support 7.10: Monitored Devices Configuration Guide Page 44 of 436
Chapter 2: Configuring ProLiant Gen10 servers

Insight RS converts the iLO service event Time Generated value to the time zone of the browser
used to access the Insight RS Console.

Note: Test events are automatically closed by HPE since no further actions are required.

To receive email alerts about system events, configure AlertMail. For information, see the iLO 5 User Guide at
www.hpe.com/support/ilo-docs.

Initiate a data collection

You can test your collections from the iLO 5 web interface or the Insight RS Console. Collections are not
automatically run after discovery. HPE recommends that you manually run a collection after discovery
completes in order to verify connectivity.

Note: Insight Remote Support will run a data collection when the ProLiant server is discovered. If
you manually generate a data collection using one of the methods described below, you will have
two data collections shown for the device in the Insight RS Console.

Initiating a data collection in the iLO 5 web interface

To initiate a data collection in the iLO 5 web interface, complete the following steps:
1. Log on to the iLO 5 web interface (https://<iLO hostname or IP address>).
2. Navigate to Remote Support → Data Collections. The Data Collections screen displays.
3. Click Send Data Collection.
4. Click OK to confirm the action. When the transmission completes, the Last Data Collection
Transmission date and time updates.
iLO sends the data collection to Insight RS. In the Insight RS Console you can view the results on the
Collection Services → Basic Collection Results screen.

Initiating a data collection in Insight Remote Support

To initiate a data collection from Insight Remote Support, complete the following steps:
1. Log on to the Insight RS Console.
2. Navigate to Collection Services → Collection Schedules.
3. In the List of Collection Schedules pane, select Server Basic Configuration Collection Schedule.
4. In the Schedule Information pane, click Run Now.
Insight Remote Support runs the schedule. You can view the results on the Basic Collection Results tab.

Send an Active Health System Report

Note: Insight Remote Support runs an Active Health System report when the ProLiant server is
discovered. If you send an Active Health System report using one of the methods described below,
two Active Health System reports appear for the device in the Insight RS Console.

HPE Insight Remote Support 7.10: Monitored Devices Configuration Guide Page 45 of 436
Chapter 2: Configuring ProLiant Gen10 servers

Sending an Active Health System report from the iLO 5 web interface
To send an Active Health System report from the iLO 5 web interface, complete the following steps:
1. Log on to the iLO web interface (https://<iLO hostname or IP address>).
2. Navigate to Remote Support → Data Collections. The Data Collections screen displays.
3. Click Send Active Health System Report.
4. Click OK to confirm the action. When the transmission completes, the Last Active Health System
Reporting Transmission date and time updates.
iLO sends the Active Health System report to Insight RS. In the Insight RS Console you can view the results
on the Collection Services → Basic Collection Results screen.

Sending an Active Health System Report from Insight Remote

Support
To send an Active Health System report from the Insight RS Console, complete the following steps:
1. Log on to the Insight RS Console.
2. Navigate to Collection Services → Collection Schedules.
3. In the List of Collection Schedules pane, select AHS Collection.
4. In the Schedule Information pane, click Run Now.
Insight Remote Support runs the schedule. You can view the results on the Basic Collection Results tab.

Maintenance and troubleshooting

The following maintenance tasks are available for ProLiant Gen10 servers:

Set Maintenance Mode

Make sure to turn Maintenance Mode on when performing maintenance work on the ProLiant server. When in
maintenance mode, any events or messages that are sent to Insight Remote Support are flagged to indicate
no action needs to be taken for the event.
To set maintenance mode, complete the following steps:
1. In the navigation menu, click Remote Support → Service Events. The Service Events screen displays.
2. In the Server Maintenance Mode section, select the Set Maintenance Mode check box. The Expires in
drop-down list appears.
3. In the Expires in drop-down list, select the length of time you will work on the ProLiant server.
4. Click Apply.

Note: Maintenance Mode ends once the specified time has elapsed. You can end maintenance
mode early by selecting the Clear Maintenance Mode check box and clicking Apply. A
confirmation message appears.

HPE Insight Remote Support 7.10: Monitored Devices Configuration Guide Page 46 of 436
Chapter 2: Configuring ProLiant Gen10 servers

Disable monitoring of a ProLiant Gen10 server

There may be a reason that you need to disconnect a ProLiant server so that is no longer recognized by
Insight Remote Support. For example, if the server's warranty has expired or if you have recently changed
your Hosting Device.
If you want to temporarily disable monitoring of your HPE ProLiant server, disable the device in the Insight RS
Console. If you want to permanently disable monitoring of your HPE ProLiant server, delete the device in the
Insight RS Console.
To temporarily disable monitoring, complete the following steps:

Note: Unregistering directly from the iLO 5 web interface is the same as temporarily disabling the
device in the Insight RS Console.

1. In the Insight RS Console, navigate to Devices → Device Summary.

2. Select the check box in the far left column for the devices you want to disable.
3. Click Actions → Disable Selected, and click OK in the confirmation dialog box.
To permanently disable monitoring, complete the following steps:
1. In the Insight RS Console, navigate to Devices → Device Summary.
2. Select the check box in the far left column for the devices you want to delete.
3. Click Actions → Delete Selected, and click OK in the confirmation dialog box.

ProLiant Gen10 Hosting Device discovery

ProLiant Gen10 servers ship with System Management Assistant (SMA) disabled by default. If you use a
ProLiant Gen10 server for your Hosting Device make sure that the iLO 5 is also discovered so that the
Hosting Device is monitored. Two scenarios can occur:
l If SMA is disabled, Insight RS only discovers the server and not the iLO 5. Add a RIBCL protocol and
discover the iLO 5.
l If SMA is enabled and SNMP is configured, when the ProLiant Gen10 server is discovered, the iLO 5 is
also discovered.

HPE Insight Remote Support 7.10: Monitored Devices Configuration Guide Page 47 of 436
 Chapter 3: Configuring ProLiant Gen8 and
Gen9 servers
The Insight Remote Support (RS) feature available through the iLO 4 web interface provides intelligent event
diagnosis and automatic secure submission of event notifications to HPE and your HPE Authorized Channel
Partner through the Insight RS installation on the Hosting Device.

Important: If you do not want to use the Remote Support functionality available through the iLO 4
web interface, you need to configure your ProLiant server using SNMP Agents or WBEM Providers.
Consult the information that corresponds to your operating system and follow the configuration
instructions (see "Understanding monitored devices prerequisites" on page 26). If you use SNMP
Agents or WBEM Providers you must still add RIBCL protocol credentials in the Insight RS
Console; RIBCL is required for AHS Collections and for Insight RS to monitor the server.

Note: When connecting to a ProLiant Gen8 or Gen9 server through the iLO, the iLO will maintain a
connection to Insight RS even when the operating system of the server has changed or after an
update to the iLO firmware.

For more information about ProLiant Gen8 servers, go to: www.hpe.com/info/proliantgen8/docs.

For more information about ProLiant Gen9 servers, go to: www.hpe.com/info/proliantgen9/docs.

Fulfill configuration requirements

To configure your ProLiant Gen8 and Gen9 servers to be monitored by Insight RS, complete the following
sections:
Table 3.1 ProLiant Gen8 and Gen9 configuration steps
Task Required/ Complete?
Optional

Make sure Insight RS supports your ProLiant server by checking the HPE Required
Insight Remote Support Release Notes.

Make sure the operating system on the ProLiant server is running. Required

Install and configure the Agentless Management Service (AMS) on the Optional
ProLiant server if you want your host name or IP displayed instead of the
device's serial number. For more information, see Known Issue "Missing IP
address during discovery" on page 58.

HPE Insight Remote Support 7.10: Monitored Devices Configuration Guide Page 48 of 436
Chapter 3: Configuring ProLiant Gen8 and Gen9 servers

Table 3.1 ProLiant Gen8 and Gen9 configuration steps, continued

Task Required/ Complete?
Optional

Verify a supported version of the iLO 4 firmware is installed on your ProLiant Required
server. HPE recommends version 2.60.

iLO 4 firmware version Feature details

2.60 Critical update. HPE requires users to update

to this version immediately. Install this update
to take advantage of significant improvements
to the write algorithm for the embedded 4 GB
non-volatile flash memory (also known as the
NAND). These improvements reduce wear and
increase the NAND lifespan.

2.30 Minimum version for Active Health Service

(AHS) data to be successfully processed by the
Active Health System Viewer.

2.03 Addresses third-party software vulnerabilities.

To access the iLO 4 2.03 or later web interface,
you must enable TLS in your browser. TLS is
the successor to Secure Sockets Layer (SSL).

1.10 (ProLiant Gen8) Minimum version required for remote support.

2.00 (ProLiant Gen9)

You can download the latest firmware from the HPE website:
www.hpe.com/support/ilo4.

Add the RIBCL protocol to the Insight RS Console. Required

Discover the ProLiant server in the Insight RS Console. Required

Send a test event to verify connectivity between your ProLiant server and Required
Insight RS.

Configure monitored devices

To configure your monitored devices, complete the following sections:

Verify user permissions

If you want to use a non-administrator user to discover and manage your ProLiant Gen8 or Gen9 server, the
user must have the Configure iLO Setting privilege.
The verify the user privileges, complete the following steps:
1. Log on to the iLO 4 web interface (https://<iLO hostname or IP address>).
2. Navigate to the Administration → User Administration.
The Local Users table shows the login names, user names, and assigned privileges of each configured
user. Verify the Configure iLO Setting privilege is enabled. You can move the cursor over an icon to
see the privilege name.
For more information about configuring users, see the iLO 4 User Guide at: www.hpe.com/info/ilo/docs.

HPE Insight Remote Support 7.10: Monitored Devices Configuration Guide Page 49 of 436
Chapter 3: Configuring ProLiant Gen8 and Gen9 servers

Configure firewall and port settings

Note: The below table shows the hardware requirements only; operating system port requirements
should also be configured.

Table 3.2 ProLiant Gen8/Gen9 Connectivity - Firewall/Port Requirements

Protocol Ports Source Destination Function Optional

ICMP N/A Hosting Monitored Provides system reachability (ping) check during Required
Device Systems system discovery and before other operations.

TCP 443 Hosting Onboard RIBCL Event Listener. Required

Device Administrator

TCP 7906 Onboard Hosting Secure HTTP (HTTPS) port used by the listener Required
Administrator Device running on the Embedded Support Device. The
management device connects to the Hosting Device
iLO 4
on this port (e.g. https://<hostname>:7906).

Add protocol credentials and start discovery

To discover your monitored devices, complete the following sections:

Create a RIBCL protocol credential in the Insight RS

Console
To enable Insight RS to gather Active Health Service collections, you must set up the iLO Remote Insight
Board Command Language (RIBCL) protocol credentials in the Insight RS Console.
To configure RIBCL in the Insight RS Console, complete the following steps:
1. In a web browser, log on to the Insight RS Console.
2. In the main menu, select Discovery and click the Credentials tab.
3. From the Select and Configure Protocol drop-down list, select iLO Remote Insight Board
Command Language Protocol (RIBCL).
4. Click New. The New Credential dialog box appears.
5. Fill in the required fields. Use the Username and Password of the iLO web interface on the ProLiant
server.
6. Click Add.
Add a RIBCL protocol credential for each unique username and password on your ProLiant servers.
Insight RS creates the protocol credential and it appears in the credentials table.

Define discovery subnets if desired

When discovering an iLO 4 that presents multiple server IP addresses, the default behavior of Insight RS is to
select one of the available IP addresses based on the following preferences:
"10.0.0.0/8,172.16.0.0/12,192.168.0.0/16,169.254.0.0/16,0.0.0.0/0" where 0.0.0.0/0

HPE Insight Remote Support 7.10: Monitored Devices Configuration Guide Page 50 of 436
Chapter 3: Configuring ProLiant Gen8 and Gen9 servers

represents a non-private IP range and the 10. network has the highest preference. If multiple IP addresses
exist within any of the subnets the selection behavior within that subnet is random.
A configuration command has been added to allow you to redefine this preference order and to define it more
discreetly. The command takes the following form:
rsadmin config –set siteipv4subnet.preference=<ipv4>/<prefix>[,<ipv4>/<prefix>…]
where a multiple subnet preference can be defined.
You can use the command to define a more discreet preferred IPv4 subnet, for example: 10.2.x.x over
10.1.x.x.
Example:
rsadmin config –set siteipv4subnet.preference=10.2.0.0/16
You can choose to prefer 192.168.x.x subnet over all others.
Example:
rsadmin config –set siteipv4subnet.preference=192.168.0.0/16
You can also define two or more preferences.
Example:
rsadmin config –set siteipv4subnet.preference=10.2.0.0/16,10.1.0.0/16
If the device is not reachable on the preferred subnet, Insight RS will continue to search the preference list.
For example, if the iLO shows us a 10. network and Insight RS does not have a 10. connection, Insight RS
continues searching.

Discover the ProLiant Gen8 or Gen9 server

Enable the ProLiant Gen8 or Gen9 server for Insight Remote Support in one of two ways:
l Discover the ProLiant server from the Insight RS Console.
See "Discovering the ProLiant server from the Insight RS Console" on the next page.
l Register Remote Support from the ProLiant server iLO 4 web interface.
See "Enabling Insight Remote Support for a ProLiant server" on the next page.

Note: You can also register for remote support through the Intelligent Provisioning interface. For
more information, see Insight Remote Support and Insight Online Setup Guide for ProLiant
Servers and BladeSystem c-Class Enclosures at:
www.hpe.com/info/insightremotesupport/docs.

Tip: You can use RIBCL XML scripts to register a group of servers. For more information, see the
iLO 4 Scripting and Command Line Guide at www.hpe.com/info/ilo/docs. You can also download
sample scripts for Windows and Linux.

If your device is connected through the iLO, Insight RS will detect if the iLO is registered with another remote
support application (HPE OneView, direct connect to Insight Online, or another Insight RS host). If Insight RS
detects the iLO registered to another remote support application, it will disable the server and not perform a

HPE Insight Remote Support 7.10: Monitored Devices Configuration Guide Page 51 of 436
Chapter 3: Configuring ProLiant Gen8 and Gen9 servers

RIBCL, WMI, WBEM or SNMP subscription. If you are using Agents/Providers and your iLO is not visible,
check to ensure the iLO is not registered to a different remote support application.

Discovering the ProLiant server from the Insight RS Console

To discover the ProLiant server from the Insight RS Console, complete the following steps:
1. In a web browser, log on to the Insight RS Console.
2. In the main menu, select Discovery and click the Sources tab.
3. Expand the IP Addresses section and add the IP address for your device:
a. Click New.
b. Select the Single Address, Address Range, or Address List option.
c. Type the IP address(es) of the devices to be discovered. Use the IP address of the iLO.
d. Click Add.
4. Click Start Discovery.

Note: After discovery, the operating system for the ProLiant server will not appear in the Insight RS
Console. This is expected behavior.

Enabling Insight Remote Support for a ProLiant server

With the HPE iLO Management Engine, no additional protocols need to be installed on the ProLiant server.
You only need to register the ProLiant server with your Hosting Device to enable Insight Remote Support. You
can register Insight Remote Support for a ProLiant server in the iLO 4 web interface.

Important: When setting up your iLO 4 web interface, it is important to set the time zone. If the time
zone is not set, events sent to Insight Remote Support are displayed with a GMT offset. In the iLO 4
web interface, browse to Administration → Network → SNTP Settings to set your time zone.

Use the Remote Support → Registration screen to register and enable Remote Support. You must have the
Configure iLO Settings privilege to modify the Remote Support settings.
To enable a ProLiant server for Insight Remote Support, complete the following steps:
1. Log on to the iLO 4 web interface (https://<iLO hostname or IP address>).
2. In the navigation menu, click Remote Support → Registration. The Register and Enable Automated
Support screen appears.
3. Complete the Hostname or IP address field.
4. In the Port field, type 7906.

HPE Insight Remote Support 7.10: Monitored Devices Configuration Guide Page 52 of 436
Chapter 3: Configuring ProLiant Gen8 and Gen9 servers

5. Click Register. The iLO 4 web interface registers the device and a confirmation message appears.

Note: After registration, you may see both the ProLiant server and the iLO 4 web interface listed in
the Insight RS Console. The iLO 4 web interface will disappear if the ProLiant server and the RIBCL
credentials have been configured correctly.

Note: After discovery, the operating system for the ProLiant server will not appear in the Insight RS
Console. This is expected behavior.

Verify discovery and device status

To verify the device was discovered correctly, complete the following steps:
1. In a web browser, log on to the Insight RS Console.
2. In the main menu, select Devices and click the Device Summary tab.

3. Make sure the Status column contains a success icon ( ).

If there is no success icon, determine which column has the problem and consult the Online Help for
troubleshooting information.

Test communication from the ProLiant Gen8 or

Gen9 server to Insight RS
To verify communication between your monitored device and Insight RS, complete the following sections:

Verify service event monitoring

After registering the ProLiant server with Insight Remote Support, send a test event to confirm the connection.

HPE Insight Remote Support 7.10: Monitored Devices Configuration Guide Page 53 of 436
Chapter 3: Configuring ProLiant Gen8 and Gen9 servers

Note: Sending SNMP test traps from the iLO 4 web interface Administration → Management
page is not supported in Insight Remote Support. To send a test event, do so from the Remote
Support → Service Events page as shown below.

To send a test event, complete the following steps:

1. Log on to the iLO 4 web interface (https://<iLO hostname or IP address>).
2. In the navigation menu, click Remote Support → Service Events. The Service Events screen appears.

3. Click Send Test Event. The following message appears:

Are you sure you want to send a test event?
4. Click OK to confirm that you want to send the test event. The following messages appear:
Test Service Event Transmission has been initiated
Service Event transmission in progress.
When the transmission is complete, the test event is listed in the Service Event Log and in the Insight
RS Console. If the test is successful, the Submit Status column displays the text No Error.
The Time Generated column in the Service Event Log shows the date and time based on the configured
iLO time zone.

HPE Insight Remote Support 7.10: Monitored Devices Configuration Guide Page 54 of 436
Chapter 3: Configuring ProLiant Gen8 and Gen9 servers

5. Check the Insight RS Console to verify that the test event arrived:
a. Log on to the Insight RS Console.
b. In the main menu, select Devices.
c. Find the ProLiant server and click the device name.
d. Click the Service Events tab. All service events submitted against the system display in the
Service Events screen (even if you clear the Service Event Log).
Insight RS converts the iLO service event Time Generated value to the time zone of the browser
used to access the Insight RS Console.

Note: Test events are automatically closed by HPE since no further actions are required.

Initiate a data collection

You can test your collections from the iLO 4 web interface or the Insight RS Console. Collections are not
automatically run after discovery. HPE recommends that you manually run a collection after discovery
completes in order to verify connectivity.

Note: Insight Remote Support will run a data collection when the ProLiant server is discovered. If
you manually generate a data collection using one of the methods described below, you will have
two data collections shown for the device in the Insight RS Console.

Initiating a data collection in the iLO 4 web interface

To initiate a data collection in the iLO 4 web interface, complete the following steps:
1. Log on to the iLO 4 web interface (https://<iLO hostname or IP address>).
2. Navigate to Remote Support → Data Collections. The Data Collections screen displays.

HPE Insight Remote Support 7.10: Monitored Devices Configuration Guide Page 55 of 436
Chapter 3: Configuring ProLiant Gen8 and Gen9 servers

3. Click Send Data Collection.

4. Click OK to confirm the action. When the transmission completes, the Last Data Collection
Transmission date and time updates.
iLO sends the data collection to Insight RS. In the Insight RS Console you can view the results on the
Collection Services → Basic Collection Results screen.

Initiating a data collection in Insight Remote Support

To initiate a data collection from Insight Remote Support, complete the following steps:
1. Log on to the Insight RS Console.
2. Navigate to Collection Services → Collection Schedules.
3. In the List of Collection Schedules pane, select Server Basic Configuration Collection Schedule.
4. In the Schedule Information pane, click Run Now.
Insight Remote Support runs the schedule. You can view the results on the Basic Collection Results tab.

Send an Active Health System Report

Note: Insight Remote Support runs an Active Health System report when the ProLiant server is
discovered. If you send an Active Health System report using one of the methods described below,
two Active Health System reports appear for the device in the Insight RS Console.

Sending an Active Health System report from the iLO 4 web interface
To send an Active Health System report from the iLO 4 web interface, complete the following steps:
1. Log on to the iLO web interface (https://<iLO hostname or IP address>).
2. Navigate to Remote Support → Data Collections. The Data Collections screen displays.
3. Click Send Active Health System Report.
4. Click OK to confirm the action. When the transmission completes, the Last Active Health System
Reporting Transmission date and time updates.
iLO sends the Active Health System report to Insight RS. In the Insight RS Console you can view the results
on the Collection Services → Basic Collection Results screen.

Sending an Active Health System Report from Insight Remote

Support
To send an Active Health System report from the Insight RS Console, complete the following steps:
1. Log on to the Insight RS Console.
2. Navigate to Collection Services → Collection Schedules.
3. In the List of Collection Schedules pane, select AHS Collection.
4. In the Schedule Information pane, click Run Now.
Insight Remote Support runs the schedule. You can view the results on the Basic Collection Results tab.

HPE Insight Remote Support 7.10: Monitored Devices Configuration Guide Page 56 of 436
Chapter 3: Configuring ProLiant Gen8 and Gen9 servers

Maintenance and troubleshooting

The following maintenance tasks are available for ProLiant Gen8 and Gen9 servers:

Set Maintenance Mode

Make sure to turn Maintenance Mode on when performing maintenance work on the ProLiant server. When in
maintenance mode, any events or messages that are sent to Insight Remote Support are flagged to indicate
no action needs to be taken for the event.
To set maintenance mode, complete the following steps:
1. In the navigation menu, click Remote Support → Service Events. The Service Events screen displays.
2. In the Server Maintenance Mode section, select the Set Maintenance Mode check box. The Expires in
drop-down list appears.

3. In the Expires in drop-down list, select the length of time you will work on the ProLiant server.
4. Click Apply.

Note: Maintenance Mode ends once the specified time has elapsed. You can end maintenance
mode early by selecting the Clear Maintenance Mode check box and clicking Apply. A
confirmation message appears.

Disable monitoring of a ProLiant Gen8 and Gen9 server

There may be a reason that you need to disconnect a ProLiant server so that is no longer recognized by
Insight Remote Support. For example, if the server's warranty has expired or if you have recently changed
your Hosting Device.
If you want to temporarily disable monitoring of your HPE ProLiant server, disable the device in the Insight RS
Console. If you want to permanently disable monitoring of your HPE ProLiant server, delete the device in the
Insight RS Console.
To temporarily disable monitoring, complete the following steps:

Note: Unregistering directly from the iLO 4 web interface is the same as temporarily disabling the
device in the Insight RS Console.

HPE Insight Remote Support 7.10: Monitored Devices Configuration Guide Page 57 of 436
Chapter 3: Configuring ProLiant Gen8 and Gen9 servers

1. In the Insight RS Console, navigate to Devices → Device Summary.

2. Select the check box in the far left column for the devices you want to disable.
3. Click Actions → Disable Selected, and click OK in the confirmation dialog box.
To permanently disable monitoring, complete the following steps:
1. In the Insight RS Console, navigate to Devices → Device Summary.
2. Select the check box in the far left column for the devices you want to delete.
3. Click Actions → Delete Selected, and click OK in the confirmation dialog box.

The following known issues apply to ProLiant Gen8 and Gen9 servers:

Missing IP address during discovery

After discovery of a ProLiant server through iLO 4, the server might identify itself by its serial number
(indicated by an S/N prefix) in the Insight RS Console Device Name column.
To display the ProLiant server by host name or IP address, complete the following steps:
1. Verify that the following prerequisites are met:
l iLO firmware
o For HPE ProLiant Gen8 servers: Version 1.10 or later is required.
o For HPE ProLiant Gen9 servers: Version 2.00 or later is required.

Note: The 2.60 iLO 4 firmware is a critical update. As such, HPE requires users to update
to this version immediately. Install this update to take advantage of significant
improvements to the write algorithm for the embedded 4 GB non-volatile flash memory (also
known as the NAND). These improvements reduce wear and increase the NAND lifespan.

Important: To address third-party software vulnerabilities, HPE recommends using iLO 4

2.03 or later. To access the iLO 4 2.03 or later web interface, you must enable TLS in your
browser. TLS is the successor to Secure Sockets Layer (SSL).

l AMS—The Agentless Management Service is enabled and the operating system is running.
l RIBCL—The iLO Remote Insight Board Common Language Protocol (RIBCL) credentials for the
server are configured in the Insight RS Console and are assigned to the ProLiant server.
2. Log on to the Insight RS Console.
3. Navigate to Devices → Device Summary.
4. Click the serial number in the Device Name column.
5. On the Device tab, expand the Status section and click Discover Device. When the device is
rediscovered host name or IP address is displayed.

Note: The DNS configuration determines whether the host name or IP address is displayed.

HPE Insight Remote Support 7.10: Monitored Devices Configuration Guide Page 58 of 436
Chapter 3: Configuring ProLiant Gen8 and Gen9 servers

Warranty and contract discrepancy in Insight Online

A discrepancy in Insight Online can occur between the Support Status in the Linked Warranties section and
the Support Status at the top of the screen. The ProLiant Serial Number used has a valid warranty, and the
Linked Warranty section confirms the warranty is Active. However the Support Status at the top of the
screen is listed as Expired.
This discrepancy occurs when the site address set during Insight Remote Support configuration is not a valid
address. Without a valid address, Insight Online is not able to determine the country code so it attempts to
obtain the country code from the HPE Passport profile to be used for entitlement. However, since the country
code is not a requirement in HPE Passport, it might be missing. In this case, when the country code is
missing during entitlement checking, a status of Expired is returned.
To resolve this issue, ensure that the customer address set in the Insight RS Console on the Company
Information → Sites tab is valid, with no abbreviations for street or city names, and make sure this site
information is applied to the device that is experiencing this discrepancy.

HPE Insight Remote Support 7.10: Monitored Devices Configuration Guide Page 59 of 436
 Chapter 4: Configuring ProLiant Windows
servers
Insight Remote Support (RS) must be able to communicate with your ProLiant server before it can be
monitored. Insight RS can communicate with ProLiant servers running Windows with either WMI or SNMP.
The following information describes how to install and configure the communication protocols and other
recommended software components so that it can be monitored by Insight RS.
Use these configuration instructions for Windows Server 2003, Windows Server 2008, and Windows Server
2012. Windows Server 2016 is supported on ProLiant Gen8 and later servers, but you may prefer to connect
them to Insight RS through the iLO. See "Configuring ProLiant Gen8 and Gen9 servers" on page 48.
If both SNMP and WMI are available on the ProLiant Windows monitored device it is recommend that one of
the protocols be disabled from monitoring in the Insight RS Console to prevent dual notification of a single
failing component. Disable SNMP if there are no smart detached storage devices such as MSAs attached to
the monitored device. If smart detached storage devices are installed then disable the WMI protocol in the
Insight RS Console. This is done by deleting the protocol for the monitored device in the Insight RS Console.

Important: To gather SAN Collections for a ProLiant Windows server, you must use WMI and
Service Pack for ProLiant version 2.8 or later.

To configure your ProLiant Windows server using WMI, see "Configuring ProLiant Windows servers using
WMI" below.
To configure your ProLiant Windows server using SNMP, see "Configuring ProLiant Windows servers using
SNMP" on page 67.

Configuring ProLiant Windows servers using WMI

Insight Remote Support (RS) must be able to communicate with your ProLiant server before it can be
monitored. Insight RS can communicate with ProLiant servers running Windows with WMI. The following
information describes how to install and configure WMI and other recommended software components so that
it can be monitored by Insight RS.
Use these configuration instructions for Windows Server 2003, Windows Server 2008, and Windows Server
2012. Windows Server 2016 is supported on ProLiant Gen8 and later servers, but you may prefer to connect
them to Insight RS through the iLO. See "Configuring ProLiant Gen8 and Gen9 servers" on page 48.

Fulfill configuration requirements

To configure your ProLiant Windows servers using WMI to be monitored by Insight RS, complete the
following sections:
Table 4.1 ProLiant Windows server using WMI configuration steps
Task Complete?

Check the HPE Insight Remote Support Release Notes to make sure your ProLiant Windows
server is supported.

Install WBEM/WMI on the ProLiant Windows server, available from the Service Pack for ProLiant
(SPP).

HPE Insight Remote Support 7.10: Monitored Devices Configuration Guide Page 60 of 436
Chapter 4: Configuring ProLiant Windows servers

Table 4.1 ProLiant Windows server using WMI configuration steps, continued
Task Complete?

Add the WMI protocol to the Insight RS Console.

Discover the ProLiant Windows server in the Insight RS Console.

Send a test event to verify connectivity between your ProLiant Windows server and Insight RS.

Install and configure communication software on servers

To configure your monitored devices, complete the following sections:

Install and configure WMI

Install Service Pack for ProLiant

The Service Pack for ProLiant (SPP) is a software bundle that includes drivers, utilities, and management
agents for ProLiant device(s). SPP is included on the HPE SmartStart CD that ships with every ProLiant. The
most current version is also available at: http://www.hpe.com/info/SPP/download.
HPE ProLiant systems running Microsoft Windows are supported by Insight Management Providers (IM
Providers for WBEM/WMI Mapper support). Both providers and agents are available through the same SPP
media.

Important: To gather SAN Collections for a ProLiant Windows server, you must use WMI and
Service Pack for ProLiant version 2.8 or later.

If SNMP is available on the ProLiant Windows monitored device it is recommend that it be disabled from
monitoring in the Insight RS Console to prevent dual notification of a single failing component. This is done by
deleting the SNMP protocol for the monitored device in the Insight RS Console.

Install WMI

IM Providers on the SmartStart CD and/or in the SPP version 8.1 and higher are supported for Insight Remote
Support.
See the HPE Insight Management WBEM Providers web site at: www.hpe.com/info/insight-wbem for more
information about WBEM providers, security, and credentials.
If you are using the Windows WBEM Providers (IM Providers), WBEM credentials must be set for each
monitored device within the Insight RS Console before it can be monitored. If you change your WBEM
credentials at any time, you must modify the entry for those credentials in the Insight RS Console.
The WBEM IM Providers are optional in the SPP install. Make sure you select them while installing SPP.

Install System Management Homepage

System Management Homepage (SMH) is also part of the SPP. It provides additional reporting capabilities on
the monitored device itself. While not mandatory for Insight Remote Support, SMH can be used to work with
the WBEM protocol such as sending test events.

HPE Insight Remote Support 7.10: Monitored Devices Configuration Guide Page 61 of 436
Chapter 4: Configuring ProLiant Windows servers

Disabling User Account Control in Windows Server

In Windows Server, WMI fails to connect to the namespace root\WMI if User Account Control (UAC) is
enabled. Use one of the following procedures to disable UAC, depending on which version of Windows Server
you are using. To perform this procedure, you must be logged on as a local administrator or provide the
credentials of a member of the local Administrators group.
To turn off UAC in Windows Server 2008, complete the following steps:
1. Click Start, and then click Control Panel.
2. In Control Panel, click User Accounts.
3. In the User Accounts window, click User Accounts.
4. In the User Accounts tasks window, click Turn User Account Control on or off.
5. If UAC is currently configured in Admin Approval Mode, the User Account Control message appears.
Click Continue.
6. Clear the Use User Account Control (UAC) to help protect your computer check box and click OK.
7. Click Restart Now to apply the change right away, or click Restart Later, then close the User Accounts
tasks window.
To turn off UAC in Windows Server 2008 R2, Windows Server 2012, and Windows Server 2016, complete the
following steps:
1. Click Start, and then click Control Panel.
2. In Control Panel, click User Accounts.
3. In the User Accounts window, click User Accounts.
4. In the User Accounts tasks window, click Change User Account Control settings.
5. If the User Account Control dialog box appears, make sure that the action it displays is what you want,
and then click Yes.
6. On the User Account Control Settings page, disable UAC: move the slider to Never notify and click OK.
7. Restart the server to apply the changes.

Configure firewall and port settings

Table 4.2 ProLiant Microsoft Windows and Hyper-V Connectivity - Firewall/Port
Requirements
Protocol Ports Source Destination Function Optional

ICMP N/A Hosting Monitored Provides system reachability (ping) check during Required
Device Systems system discovery and before other operations.

TCP 135 Monitored Hosting DCE endpoint resolution. Used by DCOM, and hence, Required
Systems Device Windows Management Interface (WMI) and Insight RS.

TCP 139 Monitored Hosting NETBIOS Session Service. Used by DCOM, and Required
Systems Device hence, Windows Management Interface (WMI) and
Insight RS.

HPE Insight Remote Support 7.10: Monitored Devices Configuration Guide Page 62 of 436
Chapter 4: Configuring ProLiant Windows servers

Table 4.2 ProLiant Microsoft Windows and Hyper-V Connectivity - Firewall/Port Require-
ments, continued
TCP 1024- Monitored Hosting Windows Server 2003 Windows Management Interface Required
65535 Systems Device (WMI) Communications DCOM dynamic port
assignment. Note that the Hosting Device can be
configured to limit this range. The source port will
always be 135.

TCP 5989 Hosting Monitored Secured WBEM CIMOM protocol over HTTPS/SOAP. Required
Device Systems This port is used to communicate with WBEM end point
nodes.

TCP 7905 Monitored Hosting Secure HTTP (HTTPS) port used by the listener Required
Systems Device running in the Director's Web Interface. The monitored
host connects to the Hosting Device on this port (e.g.
https://<hostname>:7905).

TCP 49152- Monitored Hosting Windows Server 2008/2012/2016 Windows Required

65535 Systems Device Management Interface (WMI) Communications DCOM
dynamic port assignment. Note that the Hosting Device
can be configured to limit this range. The source port
will always be 135.

UDP 137 Monitored Hosting NETBIOS Name Service. Used by DCOM, and hence, Required
Systems Device Windows Management Interface (WMI) and Insight RS.

UDP 138 Monitored Hosting NETBIOS Datagram Service. Used by DCOM, and Required
Systems Device hence, Windows Management Interface (WMI) and
Insight RS.

UDP 161 Hosting Monitored SNMP. This is the standard port used by SNMP agents Required
Device Systems on monitored systems. The Hosting Device sends
requests to devices on this port.

UDP 162 Monitored Hosting SNMP Trap. This is the port used by Insight RS to listen Required
Systems Device to SNMP traps.

UDP 445 Monitored Hosting Microsoft File Sharing. Used by DCOM, and hence, Required
Systems Device Windows Management Interface (WMI) and Insight RS.

Add protocol credentials and start discovery

To discover your monitored devices, complete the following sections:

Create a WMI protocol credential in the Insight RS Console

To configure WMI in the Insight RS Console, complete the following steps:
1. In a web browser, log on to the Insight RS Console.
2. In the main menu, select Discovery and click the Credentials tab.
3. From the Select and Configure Protocol drop-down list, select Windows Management
Instrumentation (WMI).
4. Click New. The New Credential dialog box appears.

HPE Insight Remote Support 7.10: Monitored Devices Configuration Guide Page 63 of 436
Chapter 4: Configuring ProLiant Windows servers

5. Type the Username and Password you have configured on your device.
6. Click Add.
Insight RS creates the protocol credential and it appears in the credentials table.

Discover the device in the Insight RS Console

To discover the device from the Insight RS Console, complete the following steps:
1. In a web browser, log on to the Insight RS Console.
2. In the main menu, select Discovery and click the Sources tab.
3. Expand the IP Addresses section and add the IP address for your device:
a. Click New.
b. Select the Single Address, Address Range, or Address List option.
c. Type the IP address(es) of the devices to be discovered.
d. Click Add.
4. Click Start Discovery.

Verify discovery and device status

To verify the device was discovered correctly, complete the following steps:
1. In a web browser, log on to the Insight RS Console.
2. In the main menu, select Devices and click the Device Summary tab.

3. Make sure the Status column contains a success icon ( ).

If there is no success icon, determine which column has the problem and consult the Online Help for
troubleshooting information.

Verify communication between monitored device and

Insight RS
To verify communication between your monitored device and Insight RS, complete the following sections:

Send a WBEM test indication to the Hosting Device

To verify connectivity from the monitored device to the Hosting Device, send a WBEM test indication to the
Hosting Device and then verify the test indication was received in the Insight RS Console.
1. In a web browser, access System Management Homepage (SMH) on the monitored device: https://
[ipaddress]:2381.
2. Log on using the administrator user name and password for the monitored device.
If you are not prompted for a logon, check the upper right corner of the SMH interface and click the Sign
In link. If you are not logged in as an administrator for the monitored device you will not have all of the
relevant configuration options.
3. In the top menu bar, click Settings.

HPE Insight Remote Support 7.10: Monitored Devices Configuration Guide Page 64 of 436
Chapter 4: Configuring ProLiant Windows servers

4. If you chose to install WBEM with SPP, it will be set as your Data Source. In the Test Indication pane,
click Send Test Indication.

5. In the Send Test Indication screen, select an Event ID type (any will work) and click Send.

Viewing test events in the Insight RS Console

Some monitored device types allow you to send a test event to Insight Remote Support. After you configure
your monitored device and send a test event, use the following process to verify the test event arrived.
1. Log on to the Insight RS Console.
2. In the main menu, select Service Events. If your monitored device is properly configured, the event will

HPE Insight Remote Support 7.10: Monitored Devices Configuration Guide Page 65 of 436
Chapter 4: Configuring ProLiant Windows servers

appear in the Service Events Information pane.

Verify collections in the Insight RS Console

Collections are not automatically run after discovery. HPE recommends that you manually run a collection
after discovery completes in order to verify connectivity. Run the collection schedule manually on the
Collection Services → Collection Schedules tab. For more information about scheduling collections, see the
Insight RS Help.
Verify that this collection ran successfully on the Collection Services → Basic Collection Results tab in the
Insight RS Console.
1. Log on to the Insight RS Console.
2. In the main menu, select Collection Services and then click the Basic Collection Results tab.
3. Expand the Server Basic Configuration Collection section.
4. Locate the entry for your device and check the Result column. If the collection was successful, a
success icon appears ( ). If it failed, an error icon appears ( ).

Maintenance and troubleshooting

The following troubleshooting tasks are available for ProLiant Windows servers that use WMI:

Device health in Insight Remote Support

If you are using SNMP to support your Windows server, and the server has the WMI service turned on, the
device health in the Insight RS Console can display an error icon ( ) if invalid WMI credentials have been
associated with the server in the Insight RS Console.
If this occurs, then the server's health displays an error icon because Insight RS cannot set up WMI. To
resolve this issue, complete one of the following steps:
l Remove the default WMI credentials and only associate them with the devices that are known to have the
WMI providers installed.
or
l Correct the WMI credentials attached to the server in the Insight RS Console.

HPE Insight Remote Support 7.10: Monitored Devices Configuration Guide Page 66 of 436
Chapter 4: Configuring ProLiant Windows servers

Configuring ProLiant Windows servers using SNMP

Insight Remote Support (RS) must be able to communicate with your ProLiant server before it can be
monitored. Insight RS can communicate with ProLiant servers running Windows with SNMP. The following
information describes how to install and configure the communication protocols and other recommended
software components so that it can be monitored by Insight RS.
Use these configuration instructions for Windows Server 2003, Windows Server 2008, and Windows Server
2012. Windows Server 2016 is supported on ProLiant Gen8 and later servers, but you may prefer to connect
them to Insight RS through the iLO. See "Configuring ProLiant Gen8 and Gen9 servers" on page 48.

Fulfill configuration requirements

To configure your ProLiant Windows servers using SNMP to be monitored by Insight RS, complete the
following sections:
Table 4.3 ProLiant Windows server using SNMP configuration steps
Task Complete?

Check the HPE Insight Remote Support Release Notes to make sure your ProLiant Windows
server is supported.

Install SNMP on the ProLiant Windows server, available from the Service Pack for ProLiant
(SPP).

Configure SNMP on the ProLiant Windows server.

Add the SNMP protocol to the Insight RS Console.

Discover the ProLiant Windows server in the Insight RS Console.

Send a test event to verify connectivity between your ProLiant Windows server and Insight RS.

Install and configure communication software on servers

To configure your monitored devices, complete the following sections:

Install and Configure SNMP Agents

Install Service Pack for ProLiant

The Service Pack for ProLiant (SPP) is a software bundle that includes drivers, utilities, and management
agents for ProLiant device(s). SPP is included on the HPE SmartStart CD that ships with every ProLiant. The
current version is also available at: http://www.hpe.com/info/SPP/download.
HPE ProLiant systems running Microsoft Windows are supported by Insight Management Agents (IM Agents
for SNMP support). Both providers and agents are available through the same SPP media.
If WBEM is available on the ProLiant Windows monitored device it is recommend that it be disabled from
monitoring in the Insight RS Console to prevent dual notification of a single failing component. This is done by
deleting the WMI protocol for the monitored device in the Insight RS Console.
If you are using the Windows SNMP Agents (IM Agents), you must configure SNMP to communicate with the
Hosting Device (see "Configuring SNMP").

HPE Insight Remote Support 7.10: Monitored Devices Configuration Guide Page 67 of 436
Chapter 4: Configuring ProLiant Windows servers

Install System Management Homepage

System Management Homepage (SMH) is also part of the SPP. It provides additional reporting capabilities on
the monitored device itself. While not mandatory for Insight Remote Support, if you have not configured your
SNMP services correctly to communicate with the Hosting Device during Insight Management Agent
installation you can use SMH to reconfigure those settings. If you have installed both the default SNMP
configuration and the optional WMI configuration while installing the SPP, then SMH will default to the WMI
configuration and you may need to reset it to the SNMP configuration if you choose to get your hardware
events through SNMP.

Configure SNMP

Your monitored devices must be configured to communicate with the Hosting Device. If you choose to use
SNMP the following steps are required to allow the monitored devices to fully communicate with the Hosting
Device.
Monitored devices that use SNMP notifications must include the following:
l All monitored devices must have a working intranet connection, such as through an Ethernet adapter, with
TCP/IP installed and running. Monitored devices must have two-way communication with the Hosting
Device over this connection.
l All monitored devices need the Insight Management Agent software for problem detection and trap
generation. The IM agents are distributed by HPE and are designed to generate SNMP traps with
information that allows for a more complete analysis.
l All monitored devices need to have the IP address of the Hosting Device host defined as a trap destination.
The Hosting Device must be able to communicate with the monitored device, but by default, Windows Server
only accepts SNMP packets from the localhost. To configure Windows Server to send traps to the Hosting
Device, complete the following steps:
1. In a web browser, access System Management Homepage (SMH) on the monitored device: https://
[ipaddress]:2381.
2. Log on using the administrator user name and password for the monitored device.
If you are not prompted for a logon, check the upper right corner of the SMH interface and click the Sign
In link. If you are not logged in as an administrator you will not have all of the relevant configuration
options.
3. In the top menu bar, click Settings.
If Settings displays the below image, this means that WBEM is set as the data source. You will need to
first set your data source to SNMP. If SNMP is already set as your data source, skip to the next step.
To change your data source to SNMP, complete the following steps:

HPE Insight Remote Support 7.10: Monitored Devices Configuration Guide Page 68 of 436
Chapter 4: Configuring ProLiant Windows servers

a. In the Select SMH Data Source pane, click the Select link.

b. In the Select Data Source pane, click the SNMP option and click Select.

c. In the top menu bar, click Settings. If you changed the data source to SNMP while logged into SMH
remotely, you will have to log on again and click the Settings tab.
4. In the SNMP Webagent pane, click the SNMP & Agent Settings link.

5. In the left menu of the Management Agents Configuration screen, click the Security link.

HPE Insight Remote Support 7.10: Monitored Devices Configuration Guide Page 69 of 436
Chapter 4: Configuring ProLiant Windows servers

6. In the Security Configuration screen click one of the following options in the Selected Hosts section:
l Accept SNMP packets from any host.
or
l Accept SNMP packets from these hosts and specify the IP address for your Hosting Device in the
text area.

HPE Insight Remote Support 7.10: Monitored Devices Configuration Guide Page 70 of 436
Chapter 4: Configuring ProLiant Windows servers

7. In the left menu of the Security Configuration screen, click the Trap link.
8. In the Trap Configuration screen, do one of the following:
l Add a Community Name that includes the Hosting Device as a Trap Destination.
or
l Edit the public Community Name to include the Hosting Device as a Trap Destination.

HPE Insight Remote Support 7.10: Monitored Devices Configuration Guide Page 71 of 436
Chapter 4: Configuring ProLiant Windows servers

Complete the preceding steps for each ProLiant Windows monitored device that uses SNMP to communicate
with the Hosting Device.

Configure firewall and port settings

Table 4.4 ProLiant Microsoft Windows and Hyper-V Connectivity - Firewall/Port
Requirements
Protocol Ports Source Destination Function Optional

ICMP N/A Hosting Monitored Provides system reachability (ping) check during Required
Device Systems system discovery and before other operations.

TCP 135 Monitored Hosting DCE endpoint resolution. Used by DCOM, and hence, Required
Systems Device Windows Management Interface (WMI) and Insight RS.

TCP 139 Monitored Hosting NETBIOS Session Service. Used by DCOM, and Required
Systems Device hence, Windows Management Interface (WMI) and
Insight RS.

TCP 1024- Monitored Hosting Windows Server 2003 Windows Management Interface Required
65535 Systems Device (WMI) Communications DCOM dynamic port
assignment. Note that the Hosting Device can be
configured to limit this range. The source port will
always be 135.

TCP 5989 Hosting Monitored Secured WBEM CIMOM protocol over HTTPS/SOAP. Required
Device Systems This port is used to communicate with WBEM end point
nodes.

TCP 7905 Monitored Hosting Secure HTTP (HTTPS) port used by the listener Required
Systems Device running in the Director's Web Interface. The monitored
host connects to the Hosting Device on this port (e.g.
https://<hostname>:7905).

HPE Insight Remote Support 7.10: Monitored Devices Configuration Guide Page 72 of 436
Chapter 4: Configuring ProLiant Windows servers

Table 4.4 ProLiant Microsoft Windows and Hyper-V Connectivity - Firewall/Port Require-
ments, continued
TCP 49152- Monitored Hosting Windows Server 2008/2012/2016 Windows Required
65535 Systems Device Management Interface (WMI) Communications DCOM
dynamic port assignment. Note that the Hosting Device
can be configured to limit this range. The source port
will always be 135.

UDP 137 Monitored Hosting NETBIOS Name Service. Used by DCOM, and hence, Required
Systems Device Windows Management Interface (WMI) and Insight RS.

UDP 138 Monitored Hosting NETBIOS Datagram Service. Used by DCOM, and Required
Systems Device hence, Windows Management Interface (WMI) and
Insight RS.

UDP 161 Hosting Monitored SNMP. This is the standard port used by SNMP agents Required
Device Systems on monitored systems. The Hosting Device sends
requests to devices on this port.

UDP 162 Monitored Hosting SNMP Trap. This is the port used by Insight RS to listen Required
Systems Device to SNMP traps.

UDP 445 Monitored Hosting Microsoft File Sharing. Used by DCOM, and hence, Required
Systems Device Windows Management Interface (WMI) and Insight RS.

Add protocol credentials and start discovery

To discover your monitored devices, complete the following sections:

Create an SNMP protocol credential in Insight RS Console

If your device's SNMP community string is set to public and your community access mode is read only,
Insight RS automatically associates an SNMP protocol with your device. If you use a different community
string or use a nonstandard port, you must create an SNMP protocol credential in the Insight RS Console.
To configure SNMP in the Insight RS Console, complete the following steps:
1. In a web browser, log on to the Insight RS Console.
2. In the main menu, select Discovery and click the Credentials tab.
3. From the Select and Configure Protocol drop-down list, select Simple Network Management Protocol
for the version of SNMP configured on your server.
4. Click New. The New Credential dialog box appears.
5. Type the information configured on your server.
6. Click Add.
Insight RS creates the protocol credential and it appears in the credentials table.

Discover the device in the Insight RS Console

To discover the device from the Insight RS Console, complete the following steps:
1. In a web browser, log on to the Insight RS Console.
2. In the main menu, select Discovery and click the Sources tab.

HPE Insight Remote Support 7.10: Monitored Devices Configuration Guide Page 73 of 436
Chapter 4: Configuring ProLiant Windows servers

3. Expand the IP Addresses section and add the IP address for your device:
a. Click New.
b. Select the Single Address, Address Range, or Address List option.
c. Type the IP address(es) of the devices to be discovered.
d. Click Add.
4. Click Start Discovery.

Verify discovery and device status

To verify the device was discovered correctly, complete the following steps:
1. In a web browser, log on to the Insight RS Console.
2. In the main menu, select Devices and click the Device Summary tab.

3. Make sure the Status column contains a success icon ( ).

If there is no success icon, determine which column has the problem and consult the Online Help for
troubleshooting information.

Verify communication between monitored device and

Insight RS
To verify communication between your monitored device and Insight RS, complete the following sections:

Send an SNMP test trap to the Hosting Device

To verify connectivity from the monitored device to the Hosting Device, send an SNMP test trap to the
Hosting Device and then verify the test trap was received in the Insight RS Console.
1. In a web browser, access System Management Homepage (SMH) on the monitored device: https://
[ipaddress]:2381.
2. Log on using the administrator user name and password for the monitored device.
If you are not prompted for a logon, check the upper right corner of the SMH interface and click the Sign
In link. If you are not logged in as an administrator you will not have all of the relevant configuration
options.
3. In the top menu bar, click Settings.
If you installed WBEM with SPP, it may be set as your data source. If that is the case, refer to "Configure
SNMP" on page 68 for information about how to set your data source to SNMP.
4. In the SNMP Webagent pane, click the SNMP & Agent Settings link.
5. In the left menu, click Send Test Trap.

Viewing test events in the Insight RS Console

Some monitored device types allow you to send a test event to Insight Remote Support. After you configure
your monitored device and send a test event, use the following process to verify the test event arrived.

HPE Insight Remote Support 7.10: Monitored Devices Configuration Guide Page 74 of 436
Chapter 4: Configuring ProLiant Windows servers

1. Log on to the Insight RS Console.

2. In the main menu, select Service Events. If your monitored device is properly configured, the event will
appear in the Service Events Information pane.

Verify collections in the Insight RS Console

Collections are not automatically run after discovery. HPE recommends that you manually run a collection
after discovery completes in order to verify connectivity. Run the collection schedule manually on the
Collection Services → Collection Schedules tab. For more information about scheduling collections, see the
Insight RS Help.
Verify that this collection ran successfully on the Collection Services → Basic Collection Results tab in the
Insight RS Console.
1. Log on to the Insight RS Console.
2. In the main menu, select Collection Services and then click the Basic Collection Results tab.
3. Expand the Server Basic Configuration Collection section.
4. Locate the entry for your device and check the Result column. If the collection was successful, a
success icon appears ( ). If it failed, an error icon appears ( ).

HPE Insight Remote Support 7.10: Monitored Devices Configuration Guide Page 75 of 436
 Chapter 5: Configuring ProLiant Linux
servers
Important: If you want to configure a Superdome X server, do not use this chapter. Use the
configuration information in "Configuring Integrity Superdome X servers" on page 147.

Fulfill configuration requirements

To configure your ProLiant Linux servers to be monitored by Insight RS, complete the following sections:
Table 5.1 ProLiant Linux server configuration steps
Task Complete?

Make sure Insight RS supports your ProLiant Linux server by checking the HPE Insight Remote
Support Release Notes.

Install SNMP on the ProLiant Linux server, available from the Service Pack for ProLiant (SPP).

Configure SNMP on the ProLiant Linux server.

Add the SNMP protocol to the Insight RS Console.

Discover the ProLiant Linux server in the Insight RS Console.

Send a test event to verify connectivity between your ProLiant Linux server and Insight RS.

Install and configure communication software on

servers
To configure your monitored devices, complete the following sections:

Install SNMP Agents

The Service Pack for ProLiant (SPP) is a system-specific software bundle that includes drivers, utilities, and
management agents for your ProLiant device(s). The SPP is shipped with every ProLiant on the HPE
SmartStart CD. The most current version is also available at: www.hpe.com/info/SPP/download.
For more information about SPP, go to: www.hpe.com/servers/spp or www.hpe.com/info/spp/docs.
HPE ProLiant systems running Linux support Insight Management Agents (IM Agents), which are delivered
through the SPP. IM Agents on the SmartStart CD and/or in SPP version 7.1 and higher are supported for
Insight Remote Support.
For supported Linux ProLiants, IM Agents version 7.1 or higher, must be installed (or verified if already
installed) from the SPP before you can continue.
To check the version of IM Agents installed, run the following command: rpm -q hp-snmp-agents

HPE Insight Remote Support 7.10: Monitored Devices Configuration Guide Page 76 of 436
Chapter 5: Configuring ProLiant Linux servers

Important: SNMP support (including IM Agents and Health Drivers) cannot be supported on the
same monitored device as WBEM (including IM Providers and Health Drivers). WBEM, if installed,
must be removed according to the SPP documentation available at:
http://www.hpe.com/info/spp/docs/.

Note: On your Linux monitored device, the /etc/snmp/snmpd.conf file contains the SNMP
configuration information. During the IM Agents installation script, watch for information about this
file. When the script prompts you about Configuring SNMP access from remote Management
Station(s), be sure to include the Hosting Device IP address. If you do not, you will need to
reconfigure SNMP.

System Management Homepage (SMH) is also part of the SPP. It provides additional reporting capabilities on
the monitored device itself. SMH is not mandatory for Insight Remote Support, but it can be used to
reconfigure SNMP if settings made during Insight Management Agent installation need to be changed.

Configure SNMP
Once you have installed the Insight Management Agents on your monitored devices, use SMH to edit the
snmpd.conf file to add the Hosting Device IP address and the SNMP community string. This enables SNMP
communication from the monitored device to the Hosting Device. You will need to do this for each Linux
monitored device.

Note: You can also edit the snmpd.conf file in a text editor if you are not using SMH.

The Hosting Device must be able to communicate with the monitored device. To configure the monitored
device to send traps to the Hosting Device, complete the following steps:
1. In a web browser, access System Management Homepage (SMH) on the monitored device: https://
[ipaddress]:2381.
2. Log on using the monitored device root username and password.
3. In the top menu bar, click Settings.

4. Click the SNMP Configuration link.

5. In the SNMP Configuration File add a trapsink entry for the Hosting Device IP address, for example
trapsink 1.2.3.4 public, and click Change.

HPE Insight Remote Support 7.10: Monitored Devices Configuration Guide Page 77 of 436
Chapter 5: Configuring ProLiant Linux servers

The trapsink command is required for events to be sent to Insight Remote Support for analysis. If the
trapsink command is not configured, Insight Remote Support will not receive traps.
A rocommunity directive allows SNMP GET and GETNEXT access. It is required for discovery and by the
analysis rules. The format is: rocommunity <community_string>, for example rocommunity public.
The community string used must be the same read community string configured in the Insight RS
Console SNMP protocol assigned to the ProLiant Linux server. The rocommunity is used during analysis
rules trap processing to retrieve additional information not supplied with traps.
The rwcommunity directive allows SNMP GET, GETNEXT, and SET access. It is not required for use by
Insight Remote Support, but may be needed by other applications.

Note: If you do not use the public community string in the trapsink entry, then you must add
a new SNMP protocol for this monitored device in the Insight RS Console that uses the same
community string.

6. For those Linux installations (for example Red Hat 4 or 5) that support the added security of view
statements, add a view systemview included entry. The view systemview included entry allows
Insight Remote Support to read the entire .232 MIB tree and gather all of the analysis data when events
occur. Make the following change to the default settings:

HPE Insight Remote Support 7.10: Monitored Devices Configuration Guide Page 78 of 436
Chapter 5: Configuring ProLiant Linux servers

a. Scroll down in the SNMP Configuration File to the view systemview included entries.

b. Comment out the default entries with a # character.

c. Add the following entry: view systemview included .1 80
d. Click Change.
7. Verify the following lines exist in the snmpd.conf file:
com2sec notConfigUser default public
group notConfigGroup v1 notConfigUser
group notConfigGroup v2c notConfigUser
view allview included .1.3.6
access notConfigGroup "" any noauth exact allview none none

If they do not exist, add them and click Change.

Configure firewall and port settings

Table 5.2 ProLiant Linux Connectivity - Firewall/Port Requirements
Protocol Ports Source Destination Function Optional

ICMP N/A Hosting Monitored Provides system reachability (ping) check during system Required
Device Systems discovery and before other operations.

UDP 161 Hosting Monitored SNMP. This is the standard port used by SNMP agents Required
Device Systems on monitored systems. The Hosting Device sends
requests to devices on this port.

UDP 162 Monitored Hosting SNMP Trap. This is the port used by Insight RS to listen Required
Systems Device to SNMP traps.

HPE Insight Remote Support 7.10: Monitored Devices Configuration Guide Page 79 of 436
Chapter 5: Configuring ProLiant Linux servers

Add protocol credentials and start discovery

To discover your monitored devices, complete the following sections:

Create an SNMP protocol credential in Insight RS Console

If your device's SNMP community string is set to public and your community access mode is read only,
Insight RS automatically associates an SNMP protocol with your device. If you use a different community
string or use a nonstandard port, you must create an SNMP protocol credential in the Insight RS Console.
To configure SNMP in the Insight RS Console, complete the following steps:
1. In a web browser, log on to the Insight RS Console.
2. In the main menu, select Discovery and click the Credentials tab.
3. From the Select and Configure Protocol drop-down list, select Simple Network Management Protocol
for the version of SNMP configured on your server.
4. Click New. The New Credential dialog box appears.
5. Type the information configured on your server.
6. Click Add.
Insight RS creates the protocol credential and it appears in the credentials table.

Discover the device in the Insight RS Console

To discover the device from the Insight RS Console, complete the following steps:
1. In a web browser, log on to the Insight RS Console.
2. In the main menu, select Discovery and click the Sources tab.
3. Expand the IP Addresses section and add the IP address for your device:
a. Click New.
b. Select the Single Address, Address Range, or Address List option.
c. Type the IP address(es) of the devices to be discovered.
d. Click Add.
4. Click Start Discovery.

Verify discovery and device status

To verify the device was discovered correctly, complete the following steps:
1. In a web browser, log on to the Insight RS Console.
2. In the main menu, select Devices and click the Device Summary tab.

3. Make sure the Status column contains a success icon ( ).

If there is no success icon, determine which column has the problem and consult the Online Help for
troubleshooting information.

HPE Insight Remote Support 7.10: Monitored Devices Configuration Guide Page 80 of 436
Chapter 5: Configuring ProLiant Linux servers

Verify communication between monitored device

and Insight RS
To verify communication between your monitored device and Insight RS, complete the following sections:

Verify connectivity by sending an SNMP test trap to the

Hosting Device
To verify connectivity from the monitored device to the Hosting Device, send an SNMP test trap to the
Hosting Device and then verify the test trap was received in the Insight RS Console.
Use one of the following methods to send an SNMP test trap to the Hosting Device.
l In SMH:
a. Click Settings.
b. In the SNMP Webagent pane, click SNMP Configuration.
c. Scroll to the bottom of the SNMP Configuration screen and in the Test Trap section, click Send Trap.
l On the command line, type the following command to send a test trap to the Hosting Device:
snmptrap -v 1 -c public [Hosting Device IP Address] .1.3.6.1.4.1.232 [Linux monitored
device IP Address] 6 11003 1234 .1.3.6.1.2.1.1.5.0 s test .1.3.6.1.4.1.232.11.2.11.1.0
i 0 .1.3.6.1.4.1.232.11.2.8.1.0 s [provide your own identifier and time stamp]
The resulting text with details of the monitored device and Hosting Device should be returned.
Management Agents Test Trap sent - [timestamp]

Viewing test events in the Insight RS Console

Some monitored device types allow you to send a test event to Insight Remote Support. After you configure
your monitored device and send a test event, use the following process to verify the test event arrived.
1. Log on to the Insight RS Console.
2. In the main menu, select Service Events. If your monitored device is properly configured, the event will
appear in the Service Events Information pane.

HPE Insight Remote Support 7.10: Monitored Devices Configuration Guide Page 81 of 436
Chapter 5: Configuring ProLiant Linux servers

Verify collections in the Insight RS Console

Collections are not automatically run after discovery. HPE recommends that you manually run a collection
after discovery completes in order to verify connectivity. Run the collection schedule manually on the
Collection Services → Collection Schedules tab. For more information about scheduling collections, see the
Insight RS Help.
Verify that this collection ran successfully on the Collection Services → Basic Collection Results tab in the
Insight RS Console.
1. Log on to the Insight RS Console.
2. In the main menu, select Collection Services and then click the Basic Collection Results tab.
3. Expand the Server Basic Configuration Collection section.
4. Locate the entry for your device and check the Result column. If the collection was successful, a
success icon appears ( ). If it failed, an error icon appears ( ).

HPE Insight Remote Support 7.10: Monitored Devices Configuration Guide Page 82 of 436
 Chapter 6: Configuring ProLiant VMware ESX
servers
Fulfill configuration requirements
To configure your ProLiant VMware ESX servers to be monitored by Insight RS, complete the following
sections:
Table 6.1 ProLiant VMware ESX server configuration steps
Task Complete?

Make sure Insight RS supports your ProLiant VMware ESX server by checking the HPE Insight
Remote Support Release Notes.

Configure SNMP on the ProLiant VMware ESX server.

Add the SNMP protocol credentials to the Insight RS Console.

Discover the ProLiant VMware ESX server in the Insight RS Console.

Send a test event to verify connectivity between your ProLiant VMware ESX server and Insight
RS.

Install and configure communication software on

servers
To configure your monitored devices, complete the following sections:

Configure SNMP
Your monitored devices must be configured to communicate with the Hosting Device. VMware ESX uses
SNMP for communication to the Hosting Device. SNMP should be installed by default with VMware ESX, but
you must configure your monitored device SNMP settings to communicate with the Hosting Device.
Monitored devices that participate in SNMP notifications must include the following:
l All monitored devices must have a working intranet connection, such as through an Ethernet adapter, with
TCP/IP installed and running. Monitored devices must have two-way communication with the Hosting
Device over this connection.
l Monitored devices need the Management Agent software for problem detection and trap generation. The IM
agents are distributed by HPE and are designed to generate SNMP traps with information that allows for a
more complete analysis. With VMware ESX the management agents are part of the VMware ESX bundle.
So, if your monitored device is properly configured, the agents will be present on the server.
l Finally, all monitored devices need to have the Hosting Device IP address defined as a trap destination.
SNMP Agents are required for VMware ESX monitored devices. Once you have installed the SNMP Agents
on your monitored devices, use SMH to edit the snmpd.conf file to add the Hosting Device IP address and the
SNMP community string. This enables SNMP communication from the monitored device to the Hosting
Device. You will need to do this for each VMware ESX monitored device.

HPE Insight Remote Support 7.10: Monitored Devices Configuration Guide Page 83 of 436
Chapter 6: Configuring ProLiant VMware ESX servers

Note: You can also edit the snmpd.conf file in a text editor if you are not using SMH.

The Hosting Device must be able to communicate with the monitored device. To configure the monitored
device to send traps to the Hosting Device, complete the following steps:
1. In a web browser, access System Management Homepage (SMH) on the monitored device: https://
[ipaddress]:2381.
2. Log on using the monitored device root user name and password.
3. In the top menu bar, click Settings.

4. Click the SNMP Configuration link.

5. In the SNMP Configuration File add a trapsink command that includes the IP address for your Hosting
Device, for example trapsink 1.2.3.4 public, and click Change.
The trapsink command is required for events to be sent to Insight Remote Support for analysis. If the
trapsink command is not configured, Insight Remote Support will not receive traps.
A rocommunity directive allows SNMP GET and GETNEXT access. It is required for discovery and by the
analysis rules. The format is: rocommunity <community_string>, for example rocommunity public.
The community string used must be the same read community string configured in the Insight RS
Console SNMP protocol assigned to the ProLiant ESX server. The rocommunity is used during analysis
rules trap processing to retrieve additional information not supplied with traps.
The rwcommunity directive allows SNMP GET, GETNEXT, and SET access. It is not required for use by
Insight Remote Support, but may be needed by other applications.

Note: If you do not use the public community string in the trapsink entry, then you must add
a new SNMP protocol for this monitored device in the Insight RS Console that uses the same
community string.

HPE Insight Remote Support 7.10: Monitored Devices Configuration Guide Page 84 of 436
Chapter 6: Configuring ProLiant VMware ESX servers

6. For those Linux installations (for example Red Hat 4 or 5) that support the added security of view
statements, add a view systemview included entry. The view systemview included entry allows
Insight Remote Support to read the entire .232 MIB tree and gather all of the analysis data when events
occur. Make the following change to the default settings:
a. Scroll down in the SNMP Configuration File to the view systemview included entries.

b. Comment out the default entries with a # character.

HPE Insight Remote Support 7.10: Monitored Devices Configuration Guide Page 85 of 436
Chapter 6: Configuring ProLiant VMware ESX servers

c. Add the following entry: view systemview included .1 80

d. Click Change.

Configure firewall and port settings

Table 6.2 ProLiant VMware ESX Connectivity - Firewall/Port Requirements
Protocol Ports Source Destination Function Optional

ICMP N/A Hosting Monitored Provides system reachability (ping) check during system Required
Device Systems discovery and before other operations.

UDP 161 Hosting Monitored SNMP. This is the standard port used by SNMP agents Required
Device Systems on monitored systems. The Hosting Device sends
requests to devices on this port.

UDP 162 Monitored Hosting SNMP Trap. This is the port used by Insight RS to listen Required
Systems Device to SNMP traps.

Add protocol credentials and start discovery

To discover your monitored devices, complete the following sections:
Create an SNMP protocol credential in Insight RS Console
If your device's SNMP community string is set to public and your community access mode is read only,
Insight RS automatically associates an SNMP protocol with your device. If you use a different community
string or use a nonstandard port, you must create an SNMP protocol credential in the Insight RS Console.
To configure SNMP in the Insight RS Console, complete the following steps:
1. In a web browser, log on to the Insight RS Console.
2. In the main menu, select Discovery and click the Credentials tab.
3. From the Select and Configure Protocol drop-down list, select Simple Network Management Protocol
for the version of SNMP configured on your server.
4. Click New. The New Credential dialog box appears.
5. Type the information configured on your server.
6. Click Add.
Insight RS creates the protocol credential and it appears in the credentials table.

Discover the device in the Insight RS Console

To discover the device from the Insight RS Console, complete the following steps:
1. In a web browser, log on to the Insight RS Console.
2. In the main menu, select Discovery and click the Sources tab.
3. Expand the IP Addresses section and add the IP address for your device:
a. Click New.
b. Select the Single Address, Address Range, or Address List option.
c. Type the IP address(es) of the devices to be discovered.

HPE Insight Remote Support 7.10: Monitored Devices Configuration Guide Page 86 of 436
Chapter 6: Configuring ProLiant VMware ESX servers

d. Click Add.
4. Click Start Discovery.

Verify discovery and device status

To verify the device was discovered correctly, complete the following steps:
1. In a web browser, log on to the Insight RS Console.
2. In the main menu, select Devices and click the Device Summary tab.

3. Make sure the Status column contains a success icon ( ).

If there is no success icon, determine which column has the problem and consult the Online Help for
troubleshooting information.

Verify communication between monitored device

and Insight RS
To verify communication between your monitored device and Insight RS, complete the following sections:

Verify connectivity by sending an SNMP test trap to the

Hosting Device
To verify connectivity from the monitored device to the Hosting Device, send an SNMP test trap to the
Hosting Device and then verify the test trap was received in the Insight RS Console.
Use one of the following methods to send an SNMP test trap to the Hosting Device.
l In SMH:
a. Click Settings.
b. In the SNMP Webagent pane, click SNMP Configuration.
c. Scroll to the bottom of the SNMP Configuration screen and in the Test Trap section, click Send Trap.
l On the command line, type the following command to send a test trap to the Hosting Device:
snmptrap -v 1 -c public [Hosting Device IP Address] .1.3.6.1.4.1.232 [Linux monitored
device IP Address] 6 11003 1234 .1.3.6.1.2.1.1.5.0 s test .1.3.6.1.4.1.232.11.2.11.1.0
i 0 .1.3.6.1.4.1.232.11.2.8.1.0 s [provide your own identifier and time stamp]
The resulting text with details of the monitored device and Hosting Device should be returned.
Management Agents Test Trap sent - [timestamp]

Viewing test events in the Insight RS Console

Some monitored device types allow you to send a test event to Insight Remote Support. After you configure
your monitored device and send a test event, use the following process to verify the test event arrived.
1. Log on to the Insight RS Console.
2. In the main menu, select Service Events. If your monitored device is properly configured, the event will

HPE Insight Remote Support 7.10: Monitored Devices Configuration Guide Page 87 of 436
Chapter 6: Configuring ProLiant VMware ESX servers

appear in the Service Events Information pane.

Verify collections in the Insight RS Console

Collections are not automatically run after discovery. HPE recommends that you manually run a collection
after discovery completes in order to verify connectivity. Run the collection schedule manually on the
Collection Services → Collection Schedules tab. For more information about scheduling collections, see the
Insight RS Help.
Verify that this collection ran successfully on the Collection Services → Basic Collection Results tab in the
Insight RS Console.
1. Log on to the Insight RS Console.
2. In the main menu, select Collection Services and then click the Basic Collection Results tab.
3. Expand the Server Basic Configuration Collection section.
4. Locate the entry for your device and check the Result column. If the collection was successful, a
success icon appears ( ). If it failed, an error icon appears ( ).

HPE Insight Remote Support 7.10: Monitored Devices Configuration Guide Page 88 of 436
 Chapter 7: Configuring ProLiant VMware
ESXi servers
Fulfill configuration requirements
To configure your ProLiant VMware ESXi servers to be monitored by Insight RS, complete the following
sections:
Table 7.1 ProLiant VMware ESXi server configuration steps
Task Complete?

Make sure Insight RS supports your ProLiant VMware ESXi server by checking the HPE Insight
Remote Support Release Notes.

Install and configure WBEM providers on the ESXi server. If using the HPE' ESXi image, all
necessary WBEM providers are included.

Add the WBEM protocol credentials to the Insight RS Console.

Discover the ProLiant VMware ESXi server in the Insight RS Console.

Verify communication between the ESXi server and Insight RS.

Install and configure communication software on

servers
To configure your monitored devices, complete the following sections:

Install an ESXi image

There are two methods of obtaining ESXi:
l Use the HPE ESXi image, which contains the WBEM providers and Utilities Bundle (see "Obtain the HPE
ESXi image" below).
l Use the VMware ESXi image, which does not contain the WBEM providers or Utilities Bundle. The WBEM
providers and Utilities Bundle need to be installed separately, which are also available from HPE (see
"Obtain bundles to configure the VMware ESXi image" on the next page).

Obtain the HPE ESXi image

The HPE ESXi image includes the necessary WBEM providers to send hardware events to the Hosting
Device. Use the root account credentials for the ESXi system when configuring the WBEM protocols for this
monitored device on the Hosting Device. The ability to send a test event is enabled by the Test Event Utility
that is a part of the ESXi Utilities Bundle included in the HPE ESXi image.

Important: If using the HPE ESXi image, then it is not necessary to download and install the
WBEM Providers bundle because the image already has the bundle integrated within.

Download the HPE ESXi image from the following link:

HPE Insight Remote Support 7.10: Monitored Devices Configuration Guide Page 89 of 436
Chapter 7: Configuring ProLiant VMware ESXi servers

www.hpe.com/info/esxidownload

Obtain bundles to configure the VMware ESXi image

HPE has developed WBEM providers for VMware ESXi. The bundle contains the WBEM providers, and it is
necessary to download and install the bundle when the image used to install the ESXi operating system were
obtained from VMware. To send test events, you must also install the HPE ESXi Utilities Bundle, which
includes the Test Event Utility.
Download the HPE ESXi Offline Bundles and Utilities Bundle from the following link:
www.hpe.com/info/esxidownload

Configure firewall and port settings

Table 7.2 ProLiant VMware ESXi Connectivity - Firewall/Port Requirements
Protocol Ports Source Destination Function Optional

ICMP N/A Hosting Monitored Provides system reachability (ping) check during system Required
Device Systems discovery and before other operations.

TCP 5989 Hosting Monitored Secured WBEM CIMOM protocol over HTTPS/SOAP. Required
Device Systems This port is used to communicate with WBEM end point
nodes.

TCP 7905 Monitored Hosting Secure HTTP (HTTPS) port used by the listener running Required
Systems Device in the Director's Web Interface. The monitored host
connects to the Hosting Device on this port (e.g.
https://<hostname>:7905).

Add protocol credentials and start discovery

Important: If you are managing your ESXi hosts using VMware vCenter Server, you can skip the
following steps and discover all of your ESXi hosts with a single discovery of the VMware vCenter
Server. For more information, see "Configuring VMware vCenter servers" on page 427.

To discover your monitored devices, complete the following sections:

Create a WBEM protocol credential in the Insight RS

Console
To configure WBEM in the Insight RS Console, complete the following steps:
1. In a web browser, log on to the Insight RS Console.
2. In the main menu, select Discovery and click the Credentials tab.
3. From the Select and Configure Protocol drop-down list, select Web-Based Enterprise Management
(WBEM).
4. Click New. The New Credential dialog box appears.

HPE Insight Remote Support 7.10: Monitored Devices Configuration Guide Page 90 of 436
Chapter 7: Configuring ProLiant VMware ESXi servers

5. Type the Username and Password you have configured on your device.
6. Click Add.
Insight RS creates the protocol credential and it appears in the credentials table.

Discover the device in the Insight RS Console

To discover the device from the Insight RS Console, complete the following steps:
1. In a web browser, log on to the Insight RS Console.
2. In the main menu, select Discovery and click the Sources tab.
3. Expand the IP Addresses section and add the IP address for your device:
a. Click New.
b. Select the Single Address, Address Range, or Address List option.
c. Type the IP address(es) of the devices to be discovered.
d. Click Add.
4. Click Start Discovery.

Verify discovery and device status

To verify the device was discovered correctly, complete the following steps:
1. In a web browser, log on to the Insight RS Console.
2. In the main menu, select Devices and click the Device Summary tab.

3. Make sure the Status column contains a success icon ( ).

If there is no success icon, determine which column has the problem and consult the Online Help for
troubleshooting information.

Verify communication between monitored device

and Insight RS
To verify communication between your monitored device and Insight RS, complete the following section:

Verify connectivity by sending a test event to the Hosting

Device
The ESXi Test Event Utility allows you to send test events to the Hosting Device. The Test Event Utility is
available for VMware ESXi 5.0, VMware vSphere® 5.1, and vSphere 5.5 and later versions.
For more information about using the Test Event Utility, see the HPE VMware Utilities User Guide.

Important: If you are using the VMware ESXi image you must install the ESXi Utilities Offline
Bundle to send test events. See "Obtain bundles to configure the VMware ESXi image" on the
previous page.

HPE Insight Remote Support 7.10: Monitored Devices Configuration Guide Page 91 of 436
Chapter 7: Configuring ProLiant VMware ESXi servers

On the monitored device, use one of the following methods to run the hptestevent command:
l Run the command directly on the ESXi host:
/opt/hp/tools/hptestevent
l Use the esxcli to run the command:
esxcli hptestevent execute

Viewing test events in the Insight RS Console

Some monitored device types allow you to send a test event to Insight Remote Support. After you configure
your monitored device and send a test event, use the following process to verify the test event arrived.
1. Log on to the Insight RS Console.
2. In the main menu, select Service Events. If your monitored device is properly configured, the event will
appear in the Service Events Information pane.

Verify collections in the Insight RS Console

Collections are not automatically run after discovery. HPE recommends that you manually run a collection
after discovery completes in order to verify connectivity. Run the collection schedule manually on the
Collection Services → Collection Schedules tab. For more information about scheduling collections, see the
Insight RS Help.
Verify that this collection ran successfully on the Collection Services → Basic Collection Results tab in the
Insight RS Console.
1. Log on to the Insight RS Console.
2. In the main menu, select Collection Services and then click the Basic Collection Results tab.
3. Expand the Server Basic Configuration Collection section.
4. Locate the entry for your device and check the Result column. If the collection was successful, a
success icon appears ( ). If it failed, an error icon appears ( ).

HPE Insight Remote Support 7.10: Monitored Devices Configuration Guide Page 92 of 436
 Chapter 8: Configuring ProLiant Citrix
XenServers
Fulfill configuration requirements
To configure your ProLiant Citrix XenServers to be monitored by Insight RS, complete the following sections:
Table 8.1 ProLiant Citrix XenServer configuration steps
Task Complete?

Make sure Insight RS supports your ProLiant Citrix XenServer by checking the HPE Insight
Remote Support Release Notes.

Install HPE SNMP Agents for Citrix XenServer on the ProLiant Citrix XenServer.

Configure SNMP on the ProLiant Citrix XenServer.

Add the SNMP protocol to the Insight RS Console.

Discover the ProLiant Citrix server in the Insight RS Console.

Send a test event to verify connectivity between your ProLiant Citrix XenServer and Insight RS.

Install and configure communication software on

servers
To configure your monitored devices, complete the following sections:

Install SNMP Agents for Citrix XenServer

Your Citrix monitored devices must be configured to communicate with the Hosting Device. Monitored
devices that use SNMP notifications must include the following:
l All monitored devices must have a working intranet connection, such as through an Ethernet adapter, with
TCP/IP installed and running. Monitored devices must have two-way communication with the Hosting
Device over this connection.
l Monitored devices need the SNMP Agent software for problem detection and trap generation. HPE
distributes the SNMP Agents and they are designed to generate SNMP traps with information that allows
for a more complete analysis.
l Finally, all monitored devices need to have the Hosting Device IP address defined as a trap destination.
The HPE SNMP Agents for Citrix XenServer is a system-specific software bundle that includes drivers,
utilities, and management agents for your Citrix ProLiant. HPE SNMP Agents for Citrix XenServer are
available from the following link: http://h20566.www2.hpe.com/hpsc/swd/public/detail?swItemId=MTX_
9f349b2b4fc94915ac6cde8b8a.
SNMP Agents support HPE ProLiant systems running Citrix, which are included in the HPE SNMP Agents
for Citrix XenServer software package.

HPE Insight Remote Support 7.10: Monitored Devices Configuration Guide Page 93 of 436
Chapter 8: Configuring ProLiant Citrix XenServers

Note: On your Citrix monitored device, the /etc/snmp/snmpd.conf file contains the current SNMP
configuration. During your configuration of the installation script of SNMP Agents, watch for
information about this file. When the script prompts you about Configuring SNMP access from
remote Management Station(s), be sure to include the Hosting Device IP address. If you do not,
you will need to reconfigure this on the monitored device.

System Management Homepage (SMH) is also included in the HPE SNMP Agents for Citrix XenServer
software package. It provides additional reporting capabilities on the monitored device itself. While not
mandatory for Insight Remote Support, if you configure SNMP services incorrectly to communicate with the
Hosting Device during SNMP Agent installation you will need SMH to reconfigure those settings.

Configure SNMP
SNMP Agents are required for Citrix monitored devices. Once you have installed the SNMP Agents on your
monitored devices, use SMH to edit the snmpd.conf file to add the Hosting Device IP address and the SNMP
community string. This enables SNMP communication from the monitored device to the Hosting Device. You
will need to do this for each Citrix monitored device.

Note: You can also edit the snmpd.conf file in a text editor if you are not using SMH.

The Hosting Device must be able to communicate with the monitored device. To configure the monitored
device to send traps to the Hosting Device, complete the following steps:
1. In a web browser, access System Management Homepage (SMH) on the monitored device: https://
[ipaddress]:2381.
2. Log on using the monitored device root user name and password.
3. In the top menu bar, click Settings.

4. Click the SNMP Configuration link.

5. In the SNMP Configuration File add a trapsink command that includes the Hosting Device IP address,
for example trapsink 1.2.3.4 public, and click Change.
The trapsink command is required for events to be sent to Insight Remote Support for analysis. If the
trapsink command is not configured, Insight Remote Support will not receive traps.
A rocommunity directive allows SNMP GET and GETNEXT access. It is required for discovery and by the
analysis rules. The format is: rocommunity <community_string>, for example rocommunity public.

HPE Insight Remote Support 7.10: Monitored Devices Configuration Guide Page 94 of 436
Chapter 8: Configuring ProLiant Citrix XenServers

The community string used must be the same read community string configured in the Insight RS
Console SNMP protocol assigned to the ProLiant Citrix server. The rocommunity is used during analysis
rules trap processing to retrieve additional information not supplied with traps.
The rwcommunity directive allows SNMP GET, GETNEXT, and SET access. It is not required for use by
Insight Remote Support, but may be needed by other applications.

Note: If you do not use the public community string in the trapsink entry, then you must add
a new SNMP protocol for this monitored device in the Insight RS Console that uses the same
community string.

6. For those Linux installations (for example Red Hat 4 or 5) that support the added security of view
statements, add a view systemview included entry. The view systemview included entry allows
Insight Remote Support to read the entire .232 MIB tree and gather all of the analysis data when events
occur. Make the following change to the default settings:

HPE Insight Remote Support 7.10: Monitored Devices Configuration Guide Page 95 of 436
Chapter 8: Configuring ProLiant Citrix XenServers

a. Scroll down in the SNMP Configuration File to the view systemview included entries.

b. Comment out the default entries with a # character.

c. Add the following entry: view systemview included .1 80
d. Click Change.

Configure firewall and port settings

Table 8.2 ProLiant Citrix Connectivity - Firewall/Port Requirements
Protocol Ports Source Destination Function Optional

ICMP N/A Hosting Monitored Provides system reachability (ping) check during Required
Device Systems system discovery and before other operations.

TCP 443 Hosting Onboard RIBCL Event Listener. Required

Device Administrator
iLO 4

UDP 161 Hosting Monitored SNMP. This is the standard port used by SNMP agents Required
Device Systems on monitored systems. The Hosting Device sends
requests to devices on this port.

UDP 162 Monitored Hosting SNMP Trap. This is the port used by Insight RS to listen Required
Systems Device to SNMP traps.

Add protocol credentials and start discovery

To discover your monitored devices, complete the following sections:
Create an SNMP protocol credential in Insight RS Console
If your device's SNMP community string is set to public and your community access mode is read only,
Insight RS automatically associates an SNMP protocol with your device. If you use a different community

HPE Insight Remote Support 7.10: Monitored Devices Configuration Guide Page 96 of 436
Chapter 8: Configuring ProLiant Citrix XenServers

string or use a nonstandard port, you must create an SNMP protocol credential in the Insight RS Console.
To configure SNMP in the Insight RS Console, complete the following steps:
1. In a web browser, log on to the Insight RS Console.
2. In the main menu, select Discovery and click the Credentials tab.
3. From the Select and Configure Protocol drop-down list, select Simple Network Management Protocol
for the version of SNMP configured on your server.
4. Click New. The New Credential dialog box appears.
5. Type the information configured on your server.
6. Click Add.
Insight RS creates the protocol credential and it appears in the credentials table.

Discover the device in the Insight RS Console

To discover the device from the Insight RS Console, complete the following steps:
1. In a web browser, log on to the Insight RS Console.
2. In the main menu, select Discovery and click the Sources tab.
3. Expand the IP Addresses section and add the IP address for your device:
a. Click New.
b. Select the Single Address, Address Range, or Address List option.
c. Type the IP address(es) of the devices to be discovered.
d. Click Add.
4. Click Start Discovery.

Verify discovery and device status

To verify the device was discovered correctly, complete the following steps:
1. In a web browser, log on to the Insight RS Console.
2. In the main menu, select Devices and click the Device Summary tab.

3. Make sure the Status column contains a success icon ( ).

If there is no success icon, determine which column has the problem and consult the Online Help for
troubleshooting information.

Verify communication between monitored device

and Insight RS
To verify communication between your monitored device and Insight RS, complete the following sections:

HPE Insight Remote Support 7.10: Monitored Devices Configuration Guide Page 97 of 436
Chapter 8: Configuring ProLiant Citrix XenServers

Verify connectivity by sending an SNMP test trap to the

Hosting Device
To verify connectivity from the monitored device to the Hosting Device, send an SNMP test trap to the
Hosting Device and then verify the test trap was received in the Insight RS Console.
Use one of the following methods to send an SNMP test trap to the Hosting Device.
l In SMH:
a. Click Settings.
b. In the SNMP Webagent pane, click SNMP Configuration.
c. Scroll to the bottom of the SNMP Configuration screen and in the Test Trap section, click Send Trap.
l On the command line, type the following command to send a test trap to the Hosting Device:
snmptrap -v 1 -c public [Hosting Device IP Address] .1.3.6.1.4.1.232 [Linux monitored
device IP Address] 6 11003 1234 .1.3.6.1.2.1.1.5.0 s test .1.3.6.1.4.1.232.11.2.11.1.0
i 0 .1.3.6.1.4.1.232.11.2.8.1.0 s [provide your own identifier and time stamp]
The resulting text with details of the monitored device and Hosting Device should be returned.
Management Agents Test Trap sent - [timestamp]

Viewing test events in the Insight RS Console

Some monitored device types allow you to send a test event to Insight Remote Support. After you configure
your monitored device and send a test event, use the following process to verify the test event arrived.
1. Log on to the Insight RS Console.
2. In the main menu, select Service Events. If your monitored device is properly configured, the event will
appear in the Service Events Information pane.

Verify collections in the Insight RS Console

Collections are not automatically run after discovery. HPE recommends that you manually run a collection
after discovery completes in order to verify connectivity. Run the collection schedule manually on the
Collection Services → Collection Schedules tab. For more information about scheduling collections, see the
Insight RS Help.

HPE Insight Remote Support 7.10: Monitored Devices Configuration Guide Page 98 of 436
Chapter 8: Configuring ProLiant Citrix XenServers

Verify that this collection ran successfully on the Collection Services → Basic Collection Results tab in the
Insight RS Console.
1. Log on to the Insight RS Console.
2. In the main menu, select Collection Services and then click the Basic Collection Results tab.
3. Expand the Server Basic Configuration Collection section.
4. Locate the entry for your device and check the Result column. If the collection was successful, a
success icon appears ( ). If it failed, an error icon appears ( ).

HPE Insight Remote Support 7.10: Monitored Devices Configuration Guide Page 99 of 436
 Chapter 9: Configuring Integrity Windows
2003 servers
Event Log Monitoring Collector (ELMC) is responsible for remote support monitoring on Windows 2003
Integrity monitored devices. SNMP is necessary for Discovery, and WBEM is necessary for configuration
collections.

Fulfill configuration requirements

To configure your Integrity Windows 2003 servers to be monitored by Insight RS, complete the following
sections:
Table 9.1 Integrity Windows 2003 server configuration steps
Task Complete?

Make sure Insight RS supports your Integrity Windows 2003 server by checking the HPE Insight
Remote Support Release Notes.

Install ELMC to the Integrity Windows 2003 server.

Verify SNMP is installed on the Integrity Windows 2003 server.

Verify WBEM is installed on the Integrity Windows 2003 server.

Add the ELMC protocol to the Insight RS Console.

Add the SNMP protocol to the Insight RS Console.

Add the WBEM protocol to the Insight RS Console.

Discover the Windows 2003 Integrity server in the Insight RS Console.

Send a test event to verify connectivity between your Windows 2003 Integrity server and Insight
RS.

Install and configure communication software on

servers
To configure your monitored devices, complete the following sections:

Install the ELMC software package on the monitored device

The monitored device must meet the following basic requirements before you install ELMC:
l Processor architecture: Itanium on Integrity Servers
l Operating system: On Integrity Servers, all supported versions of Windows 2003
l TCP-IP configured on the monitored server
l Required Permissions and Access: To install, upgrade, or uninstall ELMC, you must be logged on as the
Administrator or as a user with administrator privileges.
ELMC is required on the Integrity Windows 2003 server so that events can be forwarded to Insight RS.

HPE Insight Remote Support 7.10: Monitored Devices Configuration Guide Page 100 of 436
Chapter 9: Configuring Integrity Windows 2003 servers

If ELMC is already installed on the Integrity Windows 2003 server, make sure it is version 6.2 or later. If it's
older than version 6.2, it needs to be upgraded. To check the version of ELMC, run the following command:
wccproxy version.

Note: When upgrading to ELMC version 6.4, the incorrect version number is displayed in the
upgrade window. After performing the upgrade, the correct version number of 6.4 will show in the
Programs and Features window and when you run the wccproxy version command.

To install the ELMC software package, complete the following steps:

1. In the Insight RS Console, navigate to the Administrator Settings → Software Updates tab and select
the Event Log Monitoring Collector (ELMC) software package.
2. On the Available Version tab, click Download.
3. When the download completes, click Install. The ELMC packages are placed in the %HP_RS_
DATA%\SWM\LANDINGZONE\ELMC folder. This folder defaults to
C:\ProgramData\HP\RS\DATA\SWM\LANDINGZONE\ELMC.
Note: The ProgramData folder is a hidden folder. To view this folder, set the folder options to show
hidden folders.
4. Copy the appropriate Itanium (IA64) or x86/x64 ELMC software package into a temporary directory on
the Integrity Windows 2003 server.
5. Double-click the installer file to begin the install process. The kit will install and finish with no user
prompting. No user configuration input is required to install the ELMC software package.

Verify SNMP Agent prerequisites on the monitored device

For your Windows 2003 Integrity monitored device to be discovered by the Insight RS Console, you must
have HPE Integrity SNMP Agents for Windows Server 2003 installed and fully configured on your monitored
devices as directed in the HPE Smart Setup product documentation for the appropriate package.

Note: WBEM Providers can coexist with SNMP Agents on the monitored device system as long as
they have the same version number. Mismatched versions of HPE Insight Management WBEM
Providers and HPE Insight Management SNMP Agents are not supported.

Windows Integrity servers shipped by HPE manufacturing have the Smart Setup installation files pre-loaded
on the operating system disk. Otherwise the packages can be installed using the Smart Setup CD or
reinstallation media. You can download the Smart Setup CD or Integrity Support Pack at:
http://h20565.www2.hpe.com/hpsc/swd/public/readIndex?sp4ts.oid=3346453&swLangOid=8&swEnvOid=1
060.
For SNMP Agents to communicate to the Hosting Device, you must provide the SNMP credentials within the
Insight RS Console. These actions must occur within the Insight RS Console on the Hosting Device when
you are completing the Insight Remote Support configuration.

Verify WBEM Provider prerequisites on the monitored

device
For your Windows 2003 Integrity monitored device to support configuration collections, you must have HPE

HPE Insight Remote Support 7.10: Monitored Devices Configuration Guide Page 101 of 436
Chapter 9: Configuring Integrity Windows 2003 servers

Integrity WBEM Providers for Windows Server 2003 installed and fully configured on your monitored devices
as directed in the HPE Smart Setup product documentation for the appropriate package.

Note: WBEM Providers can coexist with SNMP Agents on the monitored device system as long as
they have the same version number. Mismatched versions of HPE Insight Management WBEM
Providers and HPE Insight Management SNMP Agents are not supported.

Windows Integrity servers shipped by HPE manufacturing have the Smart Setup installation files pre-loaded
on the operating system disk. Otherwise the packages can be installed using the Smart Setup CD or
reinstallation media. You can download the Smart Setup CD or Integrity Support Pack at:
http://h20565.www2.hpe.com/hpsc/swd/public/readIndex?sp4ts.oid=3346453&swLangOid=8&swEnvOid=1
060.
For WBEM Providers to communicate to the Hosting Device, you must provide the WBEM credentials as
directed in the HPE Insight Remote Support Installation and Configuration Guide. These actions must occur
within the Insight RS Console when you are completing the Insight Remote Support configuration.

Configure firewall and port settings

Table 9.2 Integrity Windows Server 2003 Connectivity - Firewall/Port Requirements
Protocol Ports Source Destination Function Optional

ICMP N/A Hosting Monitored Provides system reachability (ping) check during Required
Device Systems system discovery and before other operations.

TCP 135 Monitored Hosting DCE endpoint resolution. Used by DCOM, and hence, Required
Systems Device Windows Management Interface (WMI) and Insight RS.

TCP 139 Monitored Hosting NETBIOS Session Service. Used by DCOM, and hence, Required
Systems Device Windows Management Interface (WMI) and Insight RS.

TCP 1024- Monitored Hosting Windows Server 2003 Windows Management Interface Required
65535 Systems Device (WMI) Communications DCOM dynamic port
assignment. Note that the Hosting Device can be
configured to limit this range. The source port will
always be 135.

TCP 5989 Hosting Monitored Secured WBEM CIMOM protocol over HTTPS/SOAP. Required
Device Systems This port is used to communicate with WBEM end point
nodes.

TCP 7905 Monitored Hosting Secure HTTP (HTTPS) port used by the listener running Required
Systems Device in the Director's Web Interface. The monitored host
connects to the Hosting Device on this port (e.g.
https://<hostname>:7905).

TCP 7920 Hosting Monitored The Insight RS ELMC (formerly WCCProxy) process Required
Device Systems communicates with the Director on this port. This is a
proprietary protocol. Any connections that exchange
username and passwords use SSL. Not all connections
are SSL.

UDP 137 Monitored Hosting NETBIOS Name Service. Used by DCOM, and hence, Required
Systems Device Windows Management Interface (WMI) and Insight RS.

HPE Insight Remote Support 7.10: Monitored Devices Configuration Guide Page 102 of 436
Chapter 9: Configuring Integrity Windows 2003 servers

Table 9.2 Integrity Windows Server 2003 Connectivity - Firewall/Port Requirements, con-
tinued
UDP 138 Monitored Hosting NETBIOS Datagram Service. Used by DCOM, and Required
Systems Device hence, Windows Management Interface (WMI) and
Insight RS.

UDP 161 Hosting Monitored SNMP. This is the standard port used by SNMP agents Required
Device Systems on monitored systems. The Hosting Device sends
requests to devices on this port.

UDP 162 Monitored Hosting SNMP Trap. This is the port used by Insight RS to listen Required
Systems Device to SNMP traps.

UDP 445 Monitored Hosting Microsoft File Sharing. Used by DCOM, and hence, Required
Systems Device Windows Management Interface (WMI) and Insight RS.

Add protocol credentials and start discovery

To discover your monitored devices, complete the following sections:

Create an ELMC protocol credential in the Insight RS

Console
To configure an ELMC protocol credential in the Insight RS Console, complete the following steps:
1. In a web browser, log on to the Insight RS Console.
2. In the main menu, select Discovery and click the Credentials tab.
3. From the Select and Configure Protocol drop-down list, select Event Log Monitoring Collector
(ELMC).
4. Click New. The New Credential dialog box appears.
Insight RS creates the protocol credential and it appears in the credentials table.

Create an SNMPv1 protocol credential in the Insight RS

Console
If your device's SNMP community string is set to public and your community access mode is read only,
Insight RS automatically associates an SNMPv1 protocol with your device. If you use a different community
string or use a nonstandard port, you must create an SNMPv1 protocol credential in the Insight RS Console.
To configure SNMPv1 in the Insight RS Console, complete the following steps:
1. In a web browser, log on to the Insight RS Console.
2. In the main menu, select Discovery and click the Credentials tab.
3. From the Select and Configure Protocol drop-down list, select Simple Network Management Protocol
Version 1, V2C (SNMPv1, SNMPv2C).
4. Click New. The New Credential dialog box appears.

HPE Insight Remote Support 7.10: Monitored Devices Configuration Guide Page 103 of 436
Chapter 9: Configuring Integrity Windows 2003 servers

5. Type the Community String you have configured on your device.

6. Click Add.
Insight RS creates the protocol credential and it appears in the credentials table.

Create a WMI protocol credential in the Insight RS Console

To configure WMI in the Insight RS Console, complete the following steps:
1. In a web browser, log on to the Insight RS Console.
2. In the main menu, select Discovery and click the Credentials tab.
3. From the Select and Configure Protocol drop-down list, select Windows Management
Instrumentation (WMI).
4. Click New. The New Credential dialog box appears.
5. Type the Username and Password you have configured on your device.
6. Click Add.
Insight RS creates the protocol credential and it appears in the credentials table.

Discover the device in the Insight RS Console

To discover the device from the Insight RS Console, complete the following steps:
1. In a web browser, log on to the Insight RS Console.
2. In the main menu, select Discovery and click the Sources tab.
3. Expand the IP Addresses section and add the IP address for your device:
a. Click New.
b. Select the Single Address, Address Range, or Address List option.
c. Type the IP address(es) of the devices to be discovered.
d. Click Add.
4. Click Start Discovery.

Verify discovery and device status

To verify the device was discovered correctly, complete the following steps:
1. In a web browser, log on to the Insight RS Console.
2. In the main menu, select Devices and click the Device Summary tab.

3. Make sure the Status column contains a success icon ( ).

If there is no success icon, determine which column has the problem and consult the Online Help for
troubleshooting information.

HPE Insight Remote Support 7.10: Monitored Devices Configuration Guide Page 104 of 436
Chapter 9: Configuring Integrity Windows 2003 servers

Verify communication between monitored device

and Insight RS
To verify communication between your monitored device and Insight RS, complete the following sections:

Verify connectivity by sending an SNMP test trap

Use SNMP Agents to send SNMP Test Traps to verify connectivity.
1. In a web browser, access System Management Homepage (SMH) on the monitored device: https://
[ipaddress]:2381.
2. Log on using the administrator user name and password for the monitored device.

Note: If you are not prompted to log on, check the upper right corner of the SMH interface and
click the Sign In link. If you are not logged in as an administrator for the monitored device you
will not have all of the relevant configuration options.

3. If SNMP is not set as your Data Source, click Settings in the top menu bar.
4. In the Select SMH Data Source box, click the Select link.
5. In the Select Data Source section choose the SNMP option, and then click Select.

6. Once your Data Source is set to SNMP, click the Settings option, and then select the SNMP & Agent
Configuration setting.

HPE Insight Remote Support 7.10: Monitored Devices Configuration Guide Page 105 of 436
Chapter 9: Configuring Integrity Windows 2003 servers

7. In the Management Agents Configuration screen, click Send Test Trap.

Sending a WBEM test indication to verify connectivity

Use WBEM Providers to send WBEM Indications to verify connectivity.
1. In a web browser, access System Management Homepage (SMH) on the monitored device: https://
[ipaddress]:2381.
2. Log on using the administrator user name and password for the monitored device.

Note: If you are not prompted to log on, check the upper right corner of the SMH interface and
click the Sign In link. You will not have access to all relevant configuration options if you are
not logged in as an administrator for the monitored device.

3. In the top menu bar, click Settings.

4. If you chose to install WBEM with the Integrity Support Pack, it will be set as your Data Source. Click
the Send Test Indication option.

HPE Insight Remote Support 7.10: Monitored Devices Configuration Guide Page 106 of 436
Chapter 9: Configuring Integrity Windows 2003 servers

5. In the Send Test Indication screen, select an Event ID type and click Send.

Viewing test events in the Insight RS Console

Some monitored device types allow you to send a test event to Insight Remote Support. After you configure
your monitored device and send a test event, use the following process to verify the test event arrived.
1. Log on to the Insight RS Console.
2. In the main menu, select Service Events. If your monitored device is properly configured, the event will

HPE Insight Remote Support 7.10: Monitored Devices Configuration Guide Page 107 of 436
Chapter 9: Configuring Integrity Windows 2003 servers

appear in the Service Events Information pane.

Verify collections in the Insight RS Console

Collections are not automatically run after discovery. HPE recommends that you manually run a collection
after discovery completes in order to verify connectivity. Run the collection schedule manually on the
Collection Services → Collection Schedules tab. For more information about scheduling collections, see the
Insight RS Help.
Verify that this collection ran successfully on the Collection Services → Basic Collection Results tab in the
Insight RS Console.
1. Log on to the Insight RS Console.
2. In the main menu, select Collection Services and then click the Basic Collection Results tab.
3. Expand the Server Basic Configuration Collection section.
4. Locate the entry for your device and check the Result column. If the collection was successful, a
success icon appears ( ). If it failed, an error icon appears ( ).

HPE Insight Remote Support 7.10: Monitored Devices Configuration Guide Page 108 of 436
 Chapter 10: Configuring Integrity Windows
2008 servers
Fulfill configuration requirements
To configure your Integrity Windows 2008 servers to be monitored by Insight RS, complete the following
sections:
Table 10.1 Integrity Windows 2008 server configuration steps
Task Complete?

Make sure Insight RS supports your Integrity Windows 2008 server by checking the HPE Insight
Remote Support Release Notes.

Install WBEM on the Integrity Windows 2008 server.

Add the WBEM protocol to the Insight RS Console.

Discover the Windows 2008 Integrity server in the Insight RS Console.

Send a test event to verify connectivity between your Windows 2008 Integrity server and Insight
RS.

Install and configure communication software on

servers
To configure your monitored devices, complete the following sections:

Install WBEM Providers on the monitored device

For your Windows 2008 Integrity monitored device to be discovered by the Insight RS Console and to support
configuration collections, you must have HPE Integrity WBEM Providers for Windows Server 2008 installed
and fully configured on your monitored devices as directed in the HPE Smart Setup product documentation for
the appropriate package. Windows 2008 Integrity monitored devices also use WBEM for event
submission/remote monitoring.
Windows Integrity servers shipped by HPE manufacturing have the Smart Setup installation files pre-loaded
on the operating system disk. Otherwise the packages can be installed using the Smart Setup CD or
reinstallation media. You can download the Smart Setup CD or Integrity Support Pack at:
l Windows Server 2008:
http://h20566.www2.hpe.com/hpsc/swd/public/readIndex?sp4ts.oid=3346453&swLangOid=8&swEnvOid
=4023
l Windows Server 2008 R2:
http://h20566.www2.hpe.com/hpsc/swd/public/readIndex?sp4ts.oid=3346453&swLangOid=8&swEnvOid
=4068
For WBEM Providers to communicate to the Hosting Device, you must provide the WBEM credentials within
the Insight RS Console when you are completing the Insight Remote Support configuration.

HPE Insight Remote Support 7.10: Monitored Devices Configuration Guide Page 109 of 436
Chapter 10: Configuring Integrity Windows 2008 servers

Configure firewall and port settings

Table 10.2 Integrity Windows Server 2008 Connectivity - Firewall/Port Requirements
Protocol Ports Source Destination Function Optional

ICMP N/A Hosting Monitored Provides system reachability (ping) check during Required
Device Systems system discovery and before other operations.

TCP 135 Monitored Hosting DCE endpoint resolution. Used by DCOM, and hence, Required
Systems Device Windows Management Interface (WMI) and Insight RS.

TCP 139 Monitored Hosting NETBIOS Session Service. Used by DCOM, and Required
Systems Device hence, Windows Management Interface (WMI) and
Insight RS.

TCP 5989 Hosting Monitored Secured WBEM CIMOM protocol over HTTPS/SOAP. Required
Device Systems This port is used to communicate with WBEM end point
nodes.

TCP 7905 Monitored Hosting Secure HTTP (HTTPS) port used by the listener Required
Systems Device running in the Director's Web Interface. The monitored
host connects to the Hosting Device on this port (e.g.
https://<hostname>:7905).

TCP 49152- Monitored Hosting Windows Server 2008 Windows Management Interface Required
65535 Systems Device (WMI) Communications DCOM dynamic port
assignment. Note that the Hosting Device can be
configured to limit this range. The source port will
always be 135.

UDP 137 Monitored Hosting NETBIOS Name Service. Used by DCOM, and hence, Required
Systems Device Windows Management Interface (WMI) and Insight RS.

UDP 138 Monitored Hosting NETBIOS Datagram Service. Used by DCOM, and Required
Systems Device hence, Windows Management Interface (WMI) and
Insight RS.

UDP 445 Monitored Hosting Microsoft File Sharing. Used by DCOM, and hence, Required
Systems Device Windows Management Interface (WMI) and Insight RS.

Add protocol credentials and start discovery

To discover your monitored devices, complete the following sections:

Create a WBEM protocol credential in the Insight RS

Console
To configure WBEM in the Insight RS Console, complete the following steps:
1. In a web browser, log on to the Insight RS Console.
2. In the main menu, select Discovery and click the Credentials tab.
3. From the Select and Configure Protocol drop-down list, select Web-Based Enterprise Management
(WBEM).

HPE Insight Remote Support 7.10: Monitored Devices Configuration Guide Page 110 of 436
Chapter 10: Configuring Integrity Windows 2008 servers

4. Click New. The New Credential dialog box appears.

5. Type the Username and Password you have configured on your device.
6. Click Add.
Insight RS creates the protocol credential and it appears in the credentials table.

Discover the device in the Insight RS Console

To discover the device from the Insight RS Console, complete the following steps:
1. In a web browser, log on to the Insight RS Console.
2. In the main menu, select Discovery and click the Sources tab.
3. Expand the IP Addresses section and add the IP address for your device:
a. Click New.
b. Select the Single Address, Address Range, or Address List option.
c. Type the IP address(es) of the devices to be discovered.
d. Click Add.
4. Click Start Discovery.

Verify discovery and device status

To verify the device was discovered correctly, complete the following steps:
1. In a web browser, log on to the Insight RS Console.
2. In the main menu, select Devices and click the Device Summary tab.

3. Make sure the Status column contains a success icon ( ).

If there is no success icon, determine which column has the problem and consult the Online Help for
troubleshooting information.

Verify communication between monitored device

and Insight RS
To verify communication between your monitored device and Insight RS, complete the following sections:

Verify connectivity by sending a WBEM test indication

WBEM Providers may be used to send WBEM Indications to verify connectivity.
1. In a web browser, access System Management Homepage (SMH) on the monitored device: https://
[ipaddress]:2381.
2. Log on using the administrator user name and password for the monitored device.

HPE Insight Remote Support 7.10: Monitored Devices Configuration Guide Page 111 of 436
Chapter 10: Configuring Integrity Windows 2008 servers

Note: If you are not prompted for a logon, check the upper right corner of the SMH interface
and click the Sign In link. If you are not logged in as an administrator for the monitored device
you will not have all of the relevant configuration options.

3. In the top menu bar, click Settings.

4. If you chose to install WBEM with the Support Pack, it will be set as your Data Source, click the Send
Test Indication option.

5. In the Send Test Indication screen, select an Event ID type and click Send.

HPE Insight Remote Support 7.10: Monitored Devices Configuration Guide Page 112 of 436
Chapter 10: Configuring Integrity Windows 2008 servers

Viewing test events in the Insight RS Console

Some monitored device types allow you to send a test event to Insight Remote Support. After you configure
your monitored device and send a test event, use the following process to verify the test event arrived.
1. Log on to the Insight RS Console.
2. In the main menu, select Service Events. If your monitored device is properly configured, the event will
appear in the Service Events Information pane.

Verify collections in the Insight RS Console

Collections are not automatically run after discovery. HPE recommends that you manually run a collection
after discovery completes in order to verify connectivity. Run the collection schedule manually on the
Collection Services → Collection Schedules tab. For more information about scheduling collections, see the
Insight RS Help.
Verify that this collection ran successfully on the Collection Services → Basic Collection Results tab in the
Insight RS Console.

HPE Insight Remote Support 7.10: Monitored Devices Configuration Guide Page 113 of 436
Chapter 10: Configuring Integrity Windows 2008 servers

1. Log on to the Insight RS Console.

2. In the main menu, select Collection Services and then click the Basic Collection Results tab.
3. Expand the Server Basic Configuration Collection section.
4. Locate the entry for your device and check the Result column. If the collection was successful, a
success icon appears ( ). If it failed, an error icon appears ( ).

HPE Insight Remote Support 7.10: Monitored Devices Configuration Guide Page 114 of 436
 Chapter 11: Configuring Integrity Linux
servers
Important: Configuration collections are not supported.

Note: nPars are not supported on Linux Integrity servers except on Integrity Superdome X servers.

Fulfill configuration requirements

To configure your Integrity Linux servers to be monitored by Insight RS, complete the following sections:
Table 11.1 Integrity Linux server configuration steps
Task Complete?

Make sure Insight RS supports your Integrity Linux server by checking the HPE Insight Remote
Support Release Notes.

Verify that WBEM is installed and configured on the Integrity Linux server.

Add the WBEM protocol to the Insight RS Console.

Discover the Integrity Linux server in the Insight RS Console.

Send a test event to verify connectivity between your Integrity Linux server and Insight RS.

Install and configure communication software on

servers
To configure your monitored devices, complete the following sections:

Verify HPE WBEM providers installed

Important: When you are configuring Insight Remote Support, you must configure the WBEM
credentials for your Linux Integrity monitored devices in the Insight RS Console. Take note of these
credentials as you will need to provide them later.

The HPE WBEM Providers are required on your Integrity Linux monitored device(s). The Integrity Linux HPE
WBEM Providers and the relevant documentation are part of the Support Pack, which is part of the larger HPE
Integrity Essentials Foundation Pack for Linux. HPE recommends installing the HPE Integrity Essentials
Foundation Pack rather than installing the HPE Insight Management Agent or Insight Management WBEM
Provider alone as it contains additional recommended component updates. For more details, visit
www.hpe.com/us/en/servers/mission-critical.html.
You can download the latest version of the HPE Integrity Essentials Foundation Pack for Linux software at:
h20392.www2.hpe.com/portal/swdepot/displayProductInfo.do?productNumber=linsstk.

HPE Insight Remote Support 7.10: Monitored Devices Configuration Guide Page 115 of 436
Chapter 11: Configuring Integrity Linux servers

Configure firewall and port settings

Table 11.2 Integrity Linux Connectivity - Firewall/Port Requirements
Protocol Ports Source Destination Function Optional

ICMP N/A Hosting Monitored Provides system reachability (ping) check during system Required
Device Systems discovery and before other operations.

TCP 5989 Hosting Monitored Secured WBEM CIMOM protocol over HTTPS/SOAP. Required
Device Systems This port is used to communicate with WBEM end point
nodes.

TCP 7905 Monitored Hosting Secure HTTP (HTTPS) port used by the listener running Required
Systems Device in the Director's Web Interface. The monitored host
connects to the Hosting Device on this port (e.g.
https://<hostname>:7905).

Add protocol credentials and start discovery

To discover your monitored devices, complete the following sections:

Create a WBEM protocol credential in the Insight RS

Console
To configure WBEM in the Insight RS Console, complete the following steps:
1. In a web browser, log on to the Insight RS Console.
2. In the main menu, select Discovery and click the Credentials tab.
3. From the Select and Configure Protocol drop-down list, select Web-Based Enterprise Management
(WBEM).
4. Click New. The New Credential dialog box appears.
5. Type the Username and Password you have configured on your device.
6. Click Add.
Insight RS creates the protocol credential and it appears in the credentials table.

Discover the device in the Insight RS Console

To discover the device from the Insight RS Console, complete the following steps:
1. In a web browser, log on to the Insight RS Console.
2. In the main menu, select Discovery and click the Sources tab.
3. Expand the IP Addresses section and add the IP address for your device:
a. Click New.
b. Select the Single Address, Address Range, or Address List option.
c. Type the IP address(es) of the devices to be discovered.

HPE Insight Remote Support 7.10: Monitored Devices Configuration Guide Page 116 of 436
Chapter 11: Configuring Integrity Linux servers

d. Click Add.
4. Click Start Discovery.

Verify discovery and device status

To verify the device was discovered correctly, complete the following steps:
1. In a web browser, log on to the Insight RS Console.
2. In the main menu, select Devices and click the Device Summary tab.

3. Make sure the Status column contains a success icon ( ).

If there is no success icon, determine which column has the problem and consult the Online Help for
troubleshooting information.

Verify communication between monitored device

and Insight RS
To verify communication between your monitored device and Insight RS, complete the following sections:

Send a test event to the Hosting Device

To send a test event from the monitored device to the Hosting Device, from a command line on the monitored
device type the following command:
touch /tmp/SMX.test

Note: This process is not supported for Red Hat Linux 4 or 5.

This creates a zero-length file called SMX.test in the tmp directory. The SMX providers will create an
indication to send to the Hosting Device and remove the temporary file that you created in the previous step.

Viewing test events in the Insight RS Console

Some monitored device types allow you to send a test event to Insight Remote Support. After you configure
your monitored device and send a test event, use the following process to verify the test event arrived.
1. Log on to the Insight RS Console.
2. In the main menu, select Service Events. If your monitored device is properly configured, the event will

HPE Insight Remote Support 7.10: Monitored Devices Configuration Guide Page 117 of 436
Chapter 11: Configuring Integrity Linux servers

appear in the Service Events Information pane.

Verify collections in the Insight RS Console

Configuration collections are not supported for this device type except when it is part of a SAN collection. If
you have added this device to a SAN collection, you can manually run a SAN collection to verify the
configuration.
1. Log on to the Insight RS Console.
2. In the main menu, select Collection Services.
3. Click the Collection Schedules tab.
4. In the List of Collection Schedules pane, select the SAN Configuration Collection Schedule.
Information about the collection appears in the Collection Information pane. The On These Devices pane
lists the devices the collection will run on.
5. In the Schedule Information pane, click Run Now.
6. When the collection completes, click the SAN Storage Collection Results tab.
7. Expand the SAN Configuration Collection section.
8. Locate the entry for your device and check the Result column. If the collection was successful, a
success icon appears ( ). If it failed, an error icon appears ( ).

HPE Insight Remote Support 7.10: Monitored Devices Configuration Guide Page 118 of 436
 Chapter 12: Configuring Integrity and HP
9000 HP-UX servers
Before attempting to configure Insight Remote Support for your HP-UX monitored device, read the following
information.

Note: Insight RS supports HP-UX 11i v3 vPars v5 only. vPars v6 are not supported; Insight RS
cannot entitle vPars v6 partitions because they do not have unique serial numbers and are not
registered in the HPE entitlement system.

Fulfill configuration requirements

To configure your HP-UX servers to be monitored by Insight RS, complete the following sections:
Table 12.1 HP-UX server configuration steps
Task Completed?

Make sure Insight RS supports your HP-UX server by checking the HPE Insight Remote Support
Release Notes.

Install System Fault Management prerequisites on the HP-UX server:

l OS patches
l OpenSSL Secure Network Communications Protocol
l Online Diagnostics
l WBEM Services Core Product
l System Management Web

Install and configure System Fault Management on the HP-UX server.

Configure WBEM users on the HP-UX server.

Set firewall to allow communication on specific ports.

Add the WBEM protocol to the Insight RS Console.

Discover the HP-UX server in the Insight RS Console.

Send a test event to verify connectivity to the Hosting Device.

Install and configure communication software on

servers
To configure your monitored devices, complete the following sections:

Install System Fault Management

System Fault Management (SFM) is an Insight Remote Support communications requirement on all
supported versions of HP-UX. SFM has many patch prerequisites, and those are detailed in the section
"Meeting HP-UX Operating System, Software, and Patch Requirements" on the next page. If your system(s)

HPE Insight Remote Support 7.10: Monitored Devices Configuration Guide Page 119 of 436
Chapter 12: Configuring Integrity and HP 9000 HP-UX servers

already meet the minimum requirements identified in that section, then you do not need to remove or reinstall
those components.

Note: You may be familiar with the variety of SFM providers available in the different SFM offerings.
Insight Remote Support only requires the providers in the standard SFM package(s) as specified in
section "Meeting HP-UX Operating System, Software, and Patch Requirements" below.

Web-Based Enterprise Management (WBEM) is an industry initiative to standardize management information

across different platforms. System Fault Management (SFM) is the HP-UX fault management solution that
implements WBEM standards. SFM integrates with other manageability applications like Insight Remote
Support and System Management Homepage (SMH). SFM requires that HP-UX have WBEM Services for
HP-UX and other software installed.
Events in WBEM are called indications. Before an indication can be reported to a client system (for example,
the Hosting Device), the client system must first subscribe to the event. An event subscription tells the
monitored device's Common Information Model Object Manager (CIMOM) the Hosting Device is interested in
receiving indications from that monitored device. When the CIMOM receives an indication from an indication
provider, it sends the indication to those clients that previously subscribed to receive them.
Insight Remote Support subscribes to those indications. Once the subscription is completed, indications are
delivered to Insight Remote Support as they occur.
Consult the following tables to configure your HP-UX monitored devices before installing Insight Remote
Support on your Hosting Device. Then, on the Hosting Device, use the Insight RS Console to discover your
HP-UX monitored device and configure the System Information.
System Fault Management (SFM) is a Remote Support communications requirement on all supported
versions of HP-UX. SFM has many patch prerequisites, and those are detailed in the following tables. If your
system(s) already meet the minimum requirements, you do not need to remove or reinstall those components.
If your systems do not meet the minimum requirements, please upgrade accordingly.
Additionally, you may be familiar with the variety of SFM providers available in the different SFM offerings.
Insight Remote Support only requires the providers in the standard SFM package(s) specified in the tables
below to support your monitored devices.

Important: On the Hosting Device, discover your HP-UX monitored device and configure the
System Information after you have met the HP-UX prerequisites defined in this chapter.

Meeting HP-UX Operating System, Software, and Patch Requirements

Complete the following requirements for your version of HP-UX.
Fulfilling software and patch requirements for HP-UX 11i v1 (HP 9000 only)

Important: While not required for HP-UX 11i v1 (11.11), HPE strongly recommends installing
GOLDBASE11i - B.11.11.0612.459 Base Patches for HP-UX (December 2006).
GOLDBASE11i fulfills all system patch requirements and provides a stable supported environment.
The following table identifies the minimum required patches (required if GOLDBASE11i is not
installed).

HPE Insight Remote Support 7.10: Monitored Devices Configuration Guide Page 120 of 436
Chapter 12: Configuring Integrity and HP 9000 HP-UX servers

Note: Notes About the Following Table

l WBEM Services, Online Diagnostics, and SysMgmtWeb are available on the Operating
Environment (OE) media and can be selected for install during the SFM installation.
l The listed software versions are the minimum supported requirements. Newer versions are
supported unless otherwise noted.
l System Management Homepage (SMH), bundled in SysMgmtWeb, is optional, but it allows you
to use SFM’s EVWEB GUI component to view events handled by SFM on the host.
l If present, previous versions of SFM (A.01.00.01 or A.03.00.xx) must be uninstalled before
installing SFM version A.04.00.xx.
l The table lists items in the sequence in which they should be installed in case any of them are
missing and require upgrade or installation.

Table 12.2 Required software components for HP-UX 11i v1

Required software Version required

HP-UX Operating Environment 11i v1

How to Download or Access Software: www.hpe.com/info/hpux

Operating System Patch Requirements Any 11i v1 OE is supported, however any 11i v1 OE prior to
June, 2003, must also have patch bundle B.11.11.0306.1
installed.

How to Download or Access Software:

Go to www.hpe.com/support/hpesc and sign in using your HPE Passport account. In the menu, click the Patch
management link. Type the patch name into the Patch Management search box and press Enter.

OpenSSL Secure Network Communications A.00.09.07i.012 product bundle (December, 2006) or later
Protocol

How to Download or Access Software:

l Available on Application Software Media from December, 2006 onwards
l Alternatively, go to the following HPE Software Depot location for the latest version:
h20392.www2.hpe.com/portal/swdepot/try.do?productNumber=OPENSSL11I

Online Diagnostics B.11.11.18.05 Support Tools Bundle (December, 2006)

How to Download or Access Software:

l Available on HWE0612 media
l Alternatively, go to the following HPE Software Depot location for the latest version:
www.hpe.com/downloads/stm_ux

WBEMSvcs (WBEM Services Core Product) A.02.05 product bundle (December, 2006) or later

HPE Insight Remote Support 7.10: Monitored Devices Configuration Guide Page 121 of 436
Chapter 12: Configuring Integrity and HP 9000 HP-UX servers

Table 12.2 Required software components for HP-UX 11i v1, continued
Required software Version required

How to Download or Access Software:

l Available on Application Software Media from December 2006 onwards
l Alternatively, go to the following HPE Software Depot location for the latest version:
h20392.www2.hpe.com/portal/swdepot/try.do?productNumber=WBEMSvcs

System Management Web (recommended for A.2.2.5 product bundle (December, 2006)
event monitoring, required for configuration
collection)

System Management Web is recommended to take full advantage of SFM's EVWEB GUI component which allows
viewing of events handled by SFM on the host.
If only SysMgmtHomepage version 2.2.6.2 is present on the system, then the following patch must also be
applied:
For HP-UX 11i v1 (11.11) OE apply patch PHSS_36869
Patches can be obtained from the HPE Support Center:
Go to www.hpe.com/support/hpesc and sign in using your HPE Passport account. In the menu, click the Patch
management link. Type the patch name into the Patch Management search box and press Enter.
This is a “sharfile” and must be unpacked by running it as a script (sh PHSS_36869). Be sure to review the patch
installation instructions in the enclosed text file (PHSS_36869.text)

How to Download or Access Software:

l Available on Application Software Media from December, 2007 onwards
l Alternatively, go to the following HPE Software Depot location for the latest version:
h20392.www2.hpe.com/portal/swdepot/try.do?productNumber=SysMgmtWeb

hpuxwsApache A.2.0.49

hpuxwsApache is a requirement only for the Advanced Configuration Collector component that acts as an agent
for the configuration collection element of Remote Support. It is not required for Remote Device Monitoring.

When installing the product hpuxwsAPACHE, it is recommended the entire hpuxwsApache bundle be installed.
For the downloaded depot, the hpuxTomcat and hpuxWebmin bundles are not required.

How to Download or Access Software:

l Available on 11i v1 Jun04 OE/AR or later media
l Alternatively, go to the following HPE Software Depot location for the latest version:
h20392.www2.hpe.com/portal/swdepot/displayProductInfo.do?productNumber=HPUXWSAP4382

System Fault Management (SFM) A.04.00.04 product bundle (December, 2006)

Important: It is critical that SFM is the final prerequisite software component installed or upgraded from
this list.

HPE Insight Remote Support 7.10: Monitored Devices Configuration Guide Page 122 of 436
Chapter 12: Configuring Integrity and HP 9000 HP-UX servers

Table 12.2 Required software components for HP-UX 11i v1, continued
Required software Version required

How to Download or Access Software:

l Available on HWE0612 media
l Alternatively, go to the following HPE Software Depot location for the latest version:
h20392.www2.hpe.com/portal/swdepot/displayProductInfo.do?productNumber=SysFaultMgmt

Note: See the System Fault Management Release Notes for more details and additional SFM
prerequisites at www.hpe.com/info/hpux-diagnostics-sfm-docs.

Fulfilling software and patch requirements for HP-UX 11i v2

Important: While not required for HP-UX 11i v2 (11.23), HPE strongly recommends installing the
latest QPKBASE patch bundle. QPKBASE fulfills all system patch requirements and provides a stable
supported environment. The following table identifies the minimum required patches (required if
QPKBASE is not installed).

Note: Notes About the Following Table

l WBEM Services, Online Diagnostics, and SysMgmtWeb are available on the Operating
Environment (OE) media and can be selected for install during the SFM installation.
l The listed software versions are the minimum supported requirements. Newer versions are
supported unless otherwise noted.
l System Management Homepage (SMH), bundled in SysMgmtWeb, is optional, but it allows you
to use SFM’s EVWEB GUI component to view events handled by SFM on the host.
l The table lists items in the sequence in which they should be installed in case any of them are
missing and require upgrade or installation.

Table 12.3 Required software components for HP-UX 11i v2

Required software Version required

HP-UX Operating Environment l September, 2004 11i v2 OE (minimum OE release)

l May, 2005 11i v2 OE (required for vPars
enablement).

How to Download or Access Software: www.hpe.com/info/hpux

HPE Insight Remote Support 7.10: Monitored Devices Configuration Guide Page 123 of 436
Chapter 12: Configuring Integrity and HP 9000 HP-UX servers

Table 12.3 Required software components for HP-UX 11i v2, continued
Required software Version required

Operating System Patch Requirements BUNDLE 11i patch bundle B.11.23.0409.3 (September,
2004):
Note: These six additional patches for HP- l PHKL_36288 - 11.23 Cumulative diag2 driver and
UX 11i v2 are not part of the Bundle11i and vPars enablement (use in place of PHKL_32653),
must be installed in addition to it. requires a reboot
l PHKL_34795 - 11.23 Cumulative IPMI driver patch,
requires a reboot
l PHSS_37552 - 1.0 Aries cumulative patch
l PHSS_37947 - 1.0 linker + fdp cumulative patch
l PHSS_35055 - aC++ Runtime (IA: A.06.10, PA:
A.03.71)
l PHSS_36345 - 11.23 Integrity Unwind Library

How to Download or Access Software:

Go to www.hpe.com/support/hpesc and sign in using your HPE Passport account. In the menu, click the Patch
management link. Type the patch name into the Patch Management search box and press Enter.

OpenSSL Secure Network Communications Protocol A.00.09.07i.012 product bundle (December, 2006) or
later

How to Download or Access Software:

l Available on Application Software Media from December, 2006 onwards
l Alternatively, go to the following HPE Software Depot location for the latest version:
h20392.www2.hpe.com/portal/swdepot/try.do?productNumber=OPENSSL11I

Online Diagnostics B.11.23.10.05 HPUX 11.23 Support Tools Bundle

(December, 2007) or later

How to Download or Access Software:

l Available on HWE0706 media
l Alternatively, go to the following HPE Software Depot location for the latest version:
www.hpe.com/downloads/stm_ux

WBEMSvcs (WBEM Services Core Product) A.02.05.08 WBEM Services CORE Product (December,
2007) or later

How to Download or Access Software:

l Available on Application Software Media from December, 2007 onwards
l Alternatively, go to the following HPE Software Depot location for the latest version:
h20392.www2.hpe.com/portal/swdepot/try.do?productNumber=WBEMSvcs

System Management Web (recommended for event A.2.2.7 HP-UX Web Based System Management User
monitoring, required for configuration collection) Interface (December 2007) or later

HPE Insight Remote Support 7.10: Monitored Devices Configuration Guide Page 124 of 436
Chapter 12: Configuring Integrity and HP 9000 HP-UX servers

Table 12.3 Required software components for HP-UX 11i v2, continued
Required software Version required

System Management Web is recommended to take full advantage of SFM's EVWEB GUI component which allows
viewing of events handled by SFM on the host.
If only SysMgmtHomepage version 2.2.6.2 is present on the server, then the following patch must also be
applied:
For HP-UX 11i v2 (11.23) OE apply patch PHSS_36870
Patches can be obtained from the HPE Support Center:
Go to www.hpe.com/support/hpesc and sign in using your HPE Passport account. In the menu, click the Patch
management link. Type the patch name into the Patch Management search box and press Enter.
This is a "sharfile" and must be unpacked by running it as a script (sh PHSS_36870). Be sure to review the patch
installation instructions in the enclosed text file (PHSS_36870.text)

How to Download or Access Software:

l Available on Application Software Media from September 2007 onwards
l Alternatively, go to the following HPE Software Depot location for the latest version:
h20392.www2.hpe.com/portal/swdepot/try.do?productNumber=SysMgmtWeb

System Fault Management (SFM) B.07.01.01.yy System Fault Management (May, 2009)
or later

Important: It is critical that SFM is the final prerequisite software component installed or upgraded from
this list.

How to Download or Access Software:

l Available on HWE0712 media
l Alternatively, go to the following HPE Software Depot location for the latest version:
h20392.www2.hpe.com/portal/swdepot/displayProductInfo.do?productNumber=SysFaultMgmt

Note: See the System Fault Management Release Notes for more details and additional SFM
prerequisites at www.hpe.com/info/hpux-diagnostics-sfm-docs.

Fulfilling Software and Patch Requirements for HP-UX 11i v3

Note: Notes About the Following Table

l WBEM Services, Online Diagnostics, and SysMgmtWeb are available on the Operating
Environment (OE) media and can be selected for install during the SFM installation.
l The listed versions of the software are the minimum supported requirements. Newer versions are
supported unless otherwise noted.
l System Management Homepage (SMH), bundled in SysMgmtWeb, is optional, but it allows you
to use SFM’s EVWEB GUI component to view events handled by SFM on the host.

HPE Insight Remote Support 7.10: Monitored Devices Configuration Guide Page 125 of 436
Chapter 12: Configuring Integrity and HP 9000 HP-UX servers

l The table lists items in the sequence in which they should be installed in case any of them are
missing and require upgrade or installation.

Table 12.4 Required software components for HP-UX 11i v3

Required software Version required

HP-UX Operating Environment HP-UX 11i v3

How to Download or Access Software: www.hpe.com/info/hpux

Operating System Patch Requirements l EVM-Event Mgr B.11.31

l Baseboard Management Controller (BMC) firmware
version 05.21 or later
l SysMgmtBase B.00.02.03 or later

How to Download or Access Software:

Go to www.hpe.com/support/hpesc and sign in using your HPE Passport account. In the menu, click the Patch
management link. Type the patch name into the Patch Management search box and press Enter.

OpenSSL Secure Network Communications Protocol A.00.09.07e.013 or later

How to Download or Access Software:

l Available on Application Software Media from September 2007 onwards
l Alternatively, go to the following HPE Software Depot location for the latest version:
h20392.www2.hpe.com/portal/swdepot/try.do?productNumber=OPENSSL11I

Online Diagnostics: Diagnostic and Support Tools for B.11.31.01.yy or later (SysFaultMgmt version
HP-UX, including STM version A.49.10 or later and dependency.)
EMS version A.04.20 or later

How to Download or Access Software:

l Available HP-UX 11i v3 - February 2007 media
l Alternatively, go to the following HPE Software Depot location for the latest version:
www.hpe.com/downloads/stm_ux

WBEMSvcs (WBEM Services Core Product) A.02.05 or later

How to Download or Access Software:

l Available on Application Software Media from September 2007 onwards
l Alternatively, go to the following HPE Software Depot location for the latest version:
h20392.www2.hpe.com/portal/swdepot/try.do?productNumber=WBEMSvcs

System Management Web (recommended for event A.2.2.4 HP-UX Web Based System Management User
monitoring, required for configuration collection) Interfaces (December, 2007) or later

HPE Insight Remote Support 7.10: Monitored Devices Configuration Guide Page 126 of 436
Chapter 12: Configuring Integrity and HP 9000 HP-UX servers

Table 12.4 Required software components for HP-UX 11i v3, continued
Required software Version required

System Management Web is recommended to take full advantage of SFM's EVWEB GUI component which allows
viewing of events handled by SFM on the host.
If only SysMgmtHomepage version 2.2.6.2 is present on the server, then the following patch must also be
applied:
For HP-UX 11i v3 (11.31) OE apply patch PHSS_36871
Patches can be obtained from the HPE Support Center:
Go to www.hpe.com/support/hpesc and sign in using your HPE Passport account. In the menu, click the Patch
management link. Type the patch name into the Patch Management search box and press Enter.
This is a "sharfile" and must be unpacked by running it as a script (sh PHSS_36871). Be sure to review the patch
installation instructions in the enclosed text file (PHSS_36871.text)

How to Download or Access Software:

l Available on Application Software Media from September 2007 onwards
l Alternatively, go to the following HPE Software Depot location for the latest version:
h20392.www2.hpe.com/portal/swdepot/try.do?productNumber=SysMgmtWeb

System Fault Management (SFM) C.07.10.08.yy HPUX System Fault Management or later

It is critical that SFM is the final prerequisite software component installed or upgraded from this list.

How to Download or Access Software:

HPE recommends installing SFM through the WBEMMgmtBundle, available at:
http://www.hpe.com/info/swdepot/WBEMMgmtBundle

Note: See the System Fault Management Release Notes for more details and additional SFM
prerequisites at www.hpe.com/info/hpux-diagnostics-sfm-docs.

Verify System Fault Management is operational

To verify the System Fault Management (SFM) component is operational on a HP-UX monitored device,
complete the following steps:
1. Run the following command to verify the WBEM Services for HP-UX component is installed:
# swlist | grep –i WBEM
The output should look similar to the following:

2. To list registered CIM providers and their current status to make sure that they are all enabled, run the
following command:
# cimprovider –l –s
3. Run the following command to check OnlineDiag is installed and make sure it is version B.11.11.16xx or

HPE Insight Remote Support 7.10: Monitored Devices Configuration Guide Page 127 of 436
Chapter 12: Configuring Integrity and HP 9000 HP-UX servers

later.
# swlist | grep –i OnlineDiag
The output should look similar to the following:

4. Run the following command to check that OnlineDiag is reporting that Event Monitoring is Currently
Enabled and that EMS version is A.04.20 or later and the STM is A.49.10 or later:
# /etc/opt/resmon/lbin/monconfig
The output should look similar to the following:

5. Select 'Q' to exit the EMS Monitoring Request Manager Main Menu.
6. Disable EMS hardware monitors for HP-UX 11i v2 and 11i v3.

Important: HP-UX 11i v1 has only one mode, which means that SFM uses EMS to report the
events. You cannot disable EMS in 11i v1.

a. Check if SFM is used for hardware monitoring:

# /opt/sfm/bin/sfmconfig -w –q
b. If EMS is enabled for monitoring, switch to SFM using the command:
# /opt/sfm/bin/sfmconfig –w –s

HPE Insight Remote Support 7.10: Monitored Devices Configuration Guide Page 128 of 436
Chapter 12: Configuring Integrity and HP 9000 HP-UX servers

7. Run the following command to determine the version of the optional, but recommended, SMH component
is at least version A.2.2.6.2:
# swlist SysMgmtWeb SysMgmtHomepage
The output should look similar to the following:

8. Change the startup mode for SMH so that the autostart URL mode is set to OFF and start on boot mode is
set to ON:
# /opt/hpsmh/lbin/hpsmh stop
# /opt/hpsmh/bin/smhstartconfig -a off -b on
# /opt/hpsmh/lbin/hpsmh start
# /opt/hpsmh/bin/smhstartconfig

HPSMH 'autostart url' mode.........: OFF

HPSMH 'start on boot' mode.........: ON
Start Tomcat when HPSMH starts.....: OFF

Install vPar v5 Prerequsites (if required)

You need the following files installed on your HP-UX 11i v3 server for vPars v5 to be supported with Insight
RS.
l VirtualPartition A.05.10 – You need the fileset VPAR-RUN from this product, which is part of the
T1335DC bundle for the vPars v5 feature. The fileset provides virtual partition command line tools that
need to be available for the WBEM VPar provider to function properly.
To verify if you have this bundle installed, run the swlist -l bundle command. You should see output
similar to the following:
T1335DC HP-UX Virtual Partitions for 11.31 A.05.10

l VParProvider B.11.31.01.06 – This fileset is available as part of the WBEM Management Bundle,
available at:
h20392.www2.hpe.com/portal/swdepot/displayInstallInfo.do?productNumber=WBEMMgmtBundle.
l HP-UX WBEM Services A.02.07 – This fileset is available as part of the WBEM Management Bundle,
available at:
h20392.www2.hpe.com/portal/swdepot/displayInstallInfo.do?productNumber=WBEMMgmtBundle.
Note that you may have already installed the WBEM Management Bundle when you installed SFM.

HPE Insight Remote Support 7.10: Monitored Devices Configuration Guide Page 129 of 436
Chapter 12: Configuring Integrity and HP 9000 HP-UX servers

Create WBEM users

Insight RS requires the WBEM Services user and password to communicate with the HP-UX monitored
device. You can create a non-privileged user or, if using WBEM A.02.09.08 or later, create a privileged user in
the Insight Remote configuration file.
If using HP-UX 11i v1, 11i v2, or v3, and a version of WBEM Services earlier than A.02.09.08, see "Creating
non-privileged users with cimauth" below.
If using HP-UX 11i v2 or v3 and WBEM Services A.02.09.08 or later, see "Creating WBEM privileged users
with WBEM A.02.09.08 or later" on the next page.
For details on SysFaultMgmt, including defining WBEM user/password accounts on HP-UX, refer to the HP-
UX System Fault Management Administrator Guide at: http://www.hpe.com/info/hpux-diagnostics-sfm-docs.

Creating non-privileged users with cimauth

It is possible to use a non-privileged account for WBEM communication. Create a user or use an existing non-
privileged user. The specified username must represent a valid HP-UX user on the local host.
To create a non-privileged account on an HP-UX monitored device, complete the following steps:
1. Create a user, hpirs in this example, and assign the user to the users group:
# useradd –g users hpirs
2. Set the password for user hpirs:
# passwd hpirs (when prompted, provide and confirm the password)
3. Review the current CIM configuration, as follows:
# cimconfig –l –p
Example Output:
sslClientVerificationMode=disabled
enableSubscriptionsForNonprivilegedUsers=false
shutdownTimeout=30
authorizedUserGroups=
enableRemotePrivilegedUserAccess=false
enableHttpsConnection=true
enableHttpConnection=false

4. Based on the above output, set the following variables in the CIM planned configuration:
# cimconfig –s enableSubscriptionsForNonprivilegedUsers=true –p
# cimconfig –s enableNamespaceAuthorization=true –p

5. Stop and start the CIM Server to set the configuration changes in the CIM current configuration:
# cimserver –s
# cimserver
6. Verify the settings in the CIM current configuration:
# cimconfig –l -c
Example Output:

HPE Insight Remote Support 7.10: Monitored Devices Configuration Guide Page 130 of 436
Chapter 12: Configuring Integrity and HP 9000 HP-UX servers

sslClientVerificationMode=disabled
enableSubscriptionsForNonprivilegedUsers=true
shutdownTimeout=30
authorizedUserGroups=
enableRemoteprivilegedUserAccess=true
enableHttpsConnection=true
enableNamespaceAuthroization=true
enableHttpConnection=false

7. Add read and write authorizations for the user hpirs to each of the namespaces, root/cimv2, root/PG_
InterOp, and root/PG_Internal:
# cimauth –a –u hpirs –n root/cimv2 –R –W
# cimauth –a –u hpirs –n root/PG_InterOp –R –W
# cimauth –a –u hpirs –n root/PG_Internal –R –W
# cimauth –a –u hpirs –n root/cimv2/npar –R –W
# cimauth –a –u hpirs –n root/cimv2/vpar –R –W

8. Verify the user's authorizations:

#cimauth -l
Example Output:
hpirs, root/PG_InterOp, "rw"
hpirs, root/PG_Internal, "rw"
hpirs, root/cimv2, "rw"

Creating WBEM privileged users with WBEM A.02.09.08 or later

Specifying privileged users in WBEM release A.02.09.08 for HP-UX 11iv2 and 11iv3 servers has changed and
no longer requires the use of cimauth commands. WBEM Services version A.02.09.08 and later supports
Insight Remote Support configuration on HP-UX 11i v2 and HP-UX 11i v3 operating systems.
After installing WBEM version A.02.09.08 on previously functioning HP-UX 11iv2 and 11iV3 servers
monitored by Insight Remote Support, monitoring functionality may be broken. This is primarily due to how
privileged users are specified. In previous versions, root was the default user and additional users with root
privileges had to be added and configured with the cimauth command on the HP-UX server. With WBEM
release A.02.09.08 and above, this is now done with an Insight Remote Support configuration file, which
contains a default user called hp_irs.
This update removes the need to provide root credentials for WBEM access or the creation of special users
with root privileges and no system access to be used with WBEM.
To configure root privileges for Insight Remote Support users on an HP-UX system, complete the following
steps:
1. Install WBEM Services version A.02.09.08 or later on HP-UX 11i v3 and 11i v2 operating systems.
2. On the HP-UX server, edit the Insight Remote Support configuration file located at: /var/opt/wbem/hp_
irs_users.conf and type the required user name. By default, the hp_irs user name is added in the
Insight Remote Support configuration file.

HPE Insight Remote Support 7.10: Monitored Devices Configuration Guide Page 131 of 436
Chapter 12: Configuring Integrity and HP 9000 HP-UX servers

Note: Only system administrators can modify or create user names in the Insight Remote
Support configuration file. Ensure that the user name exists on the HP-UX system before
configuring in the Insight Remote Support configuration file.

3. Change enableSubscriptionsForNonprivilegedUsers to true:

# cimconfig -s enableSubscriptionsForNonprivilegedUsers=true -p
4. Stop the WBEM Services:
# cimserver -s
5. Restart the WBEM Services:
# cimserver

Note: Users configured in the Insight Remote Support configuration file can perform WBEM
operations with root privileges. However, these users can still continue to have system privileges
as defined in the HP-UX /etc/passwd file.

Important: For previous versions of WBEM and that have users configured with the cimauth
command, WBEM Services can stop working after performing the update-ux command (updating
to the September 2011 HP-UX version.) The WBEM bundle is in an Installed state when it should be
in a Configured state. Run swconfig on all filesets to resolve this issue.

Once WBEM version A.02.09.08 is installed, update the WBEM credentials/protocols in Insight RS to reflect
the new user hp_irs, or add the previously created users to the hp_irs_users.conf file.
For more information about WBEM, see the WBEM Services for HP-UX System Administrator Guide.

Configure firewall and port settings

Table 12.5 HP-UX Connectivity - Firewall/Port Requirements
Protocol Ports Source Destination Function Optional

ICMP N/A Hosting Monitored Provides system reachability (ping) check during system Required
Device Systems discovery and before other operations.

TCP 2381 Hosting Monitored SMH secure web server (HTTPS) and RDC from Optional
Device Systems monitored systems.

TCP 5989 Hosting Monitored Secured WBEM CIMOM protocol over HTTPS/SOAP. Required
Device Systems This port is used to communicate with WBEM end point
nodes.

TCP 7905 Monitored Hosting Secure HTTP (HTTPS) port used by the listener running Required
Systems Device in the Director's Web Interface. The monitored host
connects to the Hosting Device on this port (e.g.
https://<hostname>:7905).

Add protocol credentials and start discovery

To discover your monitored devices, complete the following sections:

HPE Insight Remote Support 7.10: Monitored Devices Configuration Guide Page 132 of 436
Chapter 12: Configuring Integrity and HP 9000 HP-UX servers

Add the WBEM protocol to the Insight RS Console

Insight RS automatically associates the WBEM protocol configured in the Insight RS Console with the HP-
UX server.

Option 1: Authenticate Using Username and Password

To configure WBEM in the Insight RS Console, complete the following steps:
1. In a web browser, log on to the Insight RS Console.
2. In the main menu, select Discovery and click the Credentials tab.
3. From the Select and Configure Protocol drop-down list, select Web-Based Enterprise Management
(WBEM).
4. Click New. The New Credential dialog box appears.
5. Type the Username and Password you have configured on your device. Use the user that was created
previously in "Create WBEM users" on page 130.
6. Click Add.
Insight RS creates the protocol credential and it appears in the credentials table.

Option 2: Authenticate to HP-UX WBEM using a certificate

Important: Repeat these steps one per year. The Jetty certificate is valid for a year, and while it
does automatically renew itself each year, the certificate needs to be moved to the HP-UX server
after it renews. To see when the Jetty certificate expires, change the filename from .pem to .cer
and then open the certificate to see property details.

To copy the certificate to the HP-UX server, complete the following steps:
1. On the Hosting Device, open a Command Prompt window and export the public certificate to a file called
UCACMS.pem, so it can be moved to the HP-UX server:
rsadmin cert –export -out c:\temp\UCACMS.pem
2. FTP the UCACMS.pem file in ASCII format to the cimserver_trust folder on the HP-UX server:
# ftp <hp-ux_server_ip_address>
ftp> cd /etc/opt/hp/sslshare/cimserver_trust/
ftp> ASCII
ftp> put UCACMS.pem
ftp> quit

3. From the Hosting Device, remotely log on to the HP-UX server.

4. Browse to the following directory:
cd /etc/opt/hp/sslshare/cimserver_trust/
5. Type the following commands to set up the WBEM certificate authentication on the HP-UX server:
a. Associate the Insight RS UCACMS.pem certificate with the root user:
# cimtrust -a -U root -f /etc/opt/hp/sslshare/cimserver_trust/UCACMS.pem -T s

HPE Insight Remote Support 7.10: Monitored Devices Configuration Guide Page 133 of 436
Chapter 12: Configuring Integrity and HP 9000 HP-UX servers

b. Associate the HP-UX certificate with the root user:

# cimtrust -a -U root -f /etc/opt/hp/sslshare/cert.pem -T s
c. Check the current cimom values:
# cimconfig -l -c
enableAuditLog=false
sslClientVerificationMode=optional
idleConnectionTimeout=0
enableSubscriptionsForNonprivilegedUsers=true
socketWriteTimeout=20
shutdownTimeout=30
authorizedUserGroups=
enableRemotePrivilegedUserAccess=true
enableHttpsConnection=true
enableNamespaceAuthorization=true
enableHttpConnection=false

d. Make sure the fields in red are defined as above. If they are not, change the values and validate them
using the following commands:
i. Set sslClientVerificationMode to optional:
# cimconfig -s sslClientVerificationMode=optional –p
ii. Set enableHttpsConnection to true:
# cimconfig -s enableHttpsConnection=true –p
iii. Stop the cimom daemon:
# cimserver -s
iv. Start the cimom daemon:
# cimserver
6. In the Insight RS Console, add a WBEM certificate credential on the Discovery → Credentials tab.
a. From the Select and Configure Protocol drop-down list, select Web-Based Enterprise
Management (WBEM).
b. Click New. The New Credential dialog box appears.
c. Select Certificate Credential from the Type drop-down list.
d. Leave the File Upload field blank because the certificate is already in the certificate store and it is
identified by using the alias name.
e. Type the Certificate Alias of “jetty”, which is the alias given to the certificate when it was exported

HPE Insight Remote Support 7.10: Monitored Devices Configuration Guide Page 134 of 436
Chapter 12: Configuring Integrity and HP 9000 HP-UX servers

above.

Option 3: Authenticate to HP-UX WBEM using user defined certificate

Important: The below OpenSSL commands require the openssl.cnf file. If openssl.cnf is not
present on your Hosting Device, you can get it using one of the following methods:
l If SMH is installed on the Hosting Device, openssl.cnf is available under
C:\hp\hpsmh\conf\openssl.cnf.
l Download openssl.cnf from https://stuff.mit.edu/afs/athena/contrib/crypto/openssl.cnf.
Copy the openssl.cnf file to the <OPENSSL_INSTALL_PATH>\bin\ folder, and add it to the path of
the OPENSSL_CONF environment variable with the following command:
set OPENSSL_CONF=<OPENSSL_INSTALL_PATH>\bin\openssl.cnf

To create the self-signed certificate and import it to Insight RS:

1. Create a self-signed certificate using OpenSSL:
openssl genrsa -out server.key 2048
openssl req -out server.csr -key server.key -new –sha1
openssl x509 -req –sha1 -days 365 -in server.csr -signkey server.key -out server.crt

2. Import the certificate:

rsadmin cert -import -alias hpux -trustfile server.crt
rsadmin cert -import -alias hpux -trustkey server.key

Note: The example uses "hpux" for the alias name, but the name can be any value you
choose.

HPE Insight Remote Support 7.10: Monitored Devices Configuration Guide Page 135 of 436
Chapter 12: Configuring Integrity and HP 9000 HP-UX servers

To copy the certificate to the HP-UX server, complete the following steps:
1. On the Hosting Device, open a Command Prompt window and export the public certificate to a file called
UCACMS.pem, so it can be moved to the HP-UX server:
rsadmin cert –export -out c:\temp\UCACMS.pem
2. FTP the UCACMS.pem file in ASCII format to the cimserver_trust folder on the HP-UX server:
# ftp <hp-ux_server_ip_address>
ftp> cd /etc/opt/hp/sslshare/cimserver_trust/
ftp> ASCII
ftp> put UCACMS.pem
ftp> quit

3. From the Hosting Device, remotely log on to the HP-UX server.

4. Browse to the following directory:
cd /etc/opt/hp/sslshare/cimserver_trust/
5. Type the following commands to set up the WBEM certificate authentication on the HP-UX server:
a. Associate the Insight RS UCACMS.pem certificate with the root user:
# cimtrust -a -U root -f /etc/opt/hp/sslshare/cimserver_trust/UCACMS.pem -T s
b. Associate the HP-UX certificate with the root user:
# cimtrust -a -U root -f /etc/opt/hp/sslshare/cert.pem -T s
c. Check the current cimom values:
# cimconfig -l -c
enableAuditLog=false
sslClientVerificationMode=optional
idleConnectionTimeout=0
enableSubscriptionsForNonprivilegedUsers=true
socketWriteTimeout=20
shutdownTimeout=30
authorizedUserGroups=
enableRemotePrivilegedUserAccess=true
enableHttpsConnection=true
enableNamespaceAuthorization=true
enableHttpConnection=false

d. Make sure the fields in red are defined as above. If they are not, change the values and validate them
using the following commands:
i. Set sslClientVerificationMode to optional:
# cimconfig -s sslClientVerificationMode=optional –p
ii. Set enableHttpsConnection to true:
# cimconfig -s enableHttpsConnection=true –p
iii. Stop the cimom daemon:
# cimserver -s

HPE Insight Remote Support 7.10: Monitored Devices Configuration Guide Page 136 of 436
Chapter 12: Configuring Integrity and HP 9000 HP-UX servers

iv. Start the cimom daemon:

# cimserver
6. In the Insight RS Console, add a WBEM certificate credential on the Discovery → Credentials tab.
a. From the Select and Configure Protocol drop-down list, select Web-Based Enterprise
Management (WBEM).
b. Click New. The New Credential dialog box appears.
c. Select Certificate Credential from the Type drop-down list.
d. Leave the File Upload field blank because the certificate is already in the certificate store and it is
identified by using the alias name.
e. Type the Certificate Alias of “hpux”, which is the alias given to the certificate when it was exported
above.

Discover the device in the Insight RS Console

To discover the device from the Insight RS Console, complete the following steps:
1. In a web browser, log on to the Insight RS Console.
2. In the main menu, select Discovery and click the Sources tab.
3. Expand the IP Addresses section and add the IP address for your device:
a. Click New.
b. Select the Single Address, Address Range, or Address List option.
c. Type the IP address(es) of the devices to be discovered.
d. Click Add.
4. Click Start Discovery.

HPE Insight Remote Support 7.10: Monitored Devices Configuration Guide Page 137 of 436
Chapter 12: Configuring Integrity and HP 9000 HP-UX servers

Verify discovery and device status

To verify the device was discovered correctly, complete the following steps:
1. In a web browser, log on to the Insight RS Console.
2. In the main menu, select Devices and click the Device Summary tab.

3. Make sure the Status column contains a success icon ( ).

If there is no success icon, determine which column has the problem and consult the Online Help for
troubleshooting information.

Verify communication between monitored device

and Insight RS
To verify communication between your monitored device and Insight RS, complete the following sections:

Verify connectivity by sending a test trap to the Hosting

Device
Send a test event from the HP-UX server to verify communication between the HP-UX server and the Hosting
Device. Execute one of the following commands on the HP-UX server:
# /etc/opt/resmon/lbin/send_test_event disk_em
or
# /opt/sfm/bin/sfmconfig -t -a
For details on SysFaultMgmt, including issuing test events, refer to the HP-UX System Fault Management
Administrator Guide at: http://www.hpe.com/info/hpux-diagnostics-sfm-docs.

Verify collections in the Insight RS Console

Collections are not automatically run after discovery. HPE recommends that you manually run a collection
after discovery completes in order to verify connectivity. Run the collection schedule manually on the
Collection Services → Collection Schedules tab. For more information about scheduling collections, see the
Insight RS Help.
Verify that this collection ran successfully on the Collection Services → Basic Collection Results tab in the
Insight RS Console.
1. Log on to the Insight RS Console.
2. In the main menu, select Collection Services and then click the Basic Collection Results tab.
3. Expand the Server Basic Configuration Collection section.
4. Locate the entry for your device and check the Result column. If the collection was successful, a
success icon appears ( ). If it failed, an error icon appears ( ).

HPE Insight Remote Support 7.10: Monitored Devices Configuration Guide Page 138 of 436
Chapter 12: Configuring Integrity and HP 9000 HP-UX servers

Maintenance
The following maintenance task is available for HP-UX servers:

Export certificates
Certificates are required for Insight RS to communicate with your HP-UX server. If you choose to use the jetty
certificate, and to prevent communication disruptions when certificates expire, Insight RS sends you email
notifications warning of the pending expiration 7, 14, 30, and 60 days prior to the certificate expiration date.
Insight RS now provides two certificates with a two week overlap. The certificate aliases are jetty and
jetty_next. During this overlap period either certificate on the HP-UX server will function.

Note: HP-UX will not allow a certificate dated in the future to be imported, and it will not allow two
certificates with the same common name to be imported. During this two week overlap period the
old certificate must be removed and the new jetty_next certificate must be imported.

The below procedure exports the certificates in the Insight RS Truststore, which you can then import onto
your monitored devices. If the existing certificates expire soon, you have the option of creating new
certificates with a longer duration before you import them to your monitored devices. By default, the
certificates expire after one year.
1. On your Hosting Device, open a Command Prompt window and export the certificate set so that it can be
imported into the affected monitored devices:
a. Browse to the following folder: %PROGRAM_FILES%HP/RS/BIN.
b. Based on your needs, execute one of the following command to export the certificates:
o To export the existing Insight RS certificates: GenJettyKeystore.bat
o To export the existing Insight RS jetty certificate and create the jetty_next certificate with a
custom duration: GenJettyKeystore.bat <days>
o To create jetty and jetty_next certificates valid for a custom
duration: GenJettyKeystore.bat <days> jetty

Note: Insight RS will begin using the new certificates within 10 minutes of creation or
you can restart the Insight RS services to use them immediately:
net stop hprsmain
net stop hprsreceivers
net start hprsmain
net start hprsreceivers

c. Follow the onscreen instructions and provide a Truststore password for each certificate.
The command exports the following files in the C:/ folder:
o jetty.cer—This is valid for the cert duration, whatever you set that to, but the default is 365.
o jetty_next.cer—This is valid from a few days before Jetty.cer expires and whatever the
duration is after.
o truststore

HPE Insight Remote Support 7.10: Monitored Devices Configuration Guide Page 139 of 436
Chapter 12: Configuring Integrity and HP 9000 HP-UX servers

2. Copy these files onto removable media so that you can import them onto the affected monitored devices.
3. Import these certificates onto the affected monitored devices listed in the email.

HPE Insight Remote Support 7.10: Monitored Devices Configuration Guide Page 140 of 436
 Chapter 13: Configuring Integrity Superdome
2 servers
The Superdome 2 system complex has two independent interfaces that report event indications: the HP-UX
partitions and the Superdome 2 Onboard Administrator (OA). HP-UX System Fault Manager (SFM) monitors
the IO devices within the partition domain and generates WBEM indications when it determines an important
event has occurred. The OA monitors the remainder of the system hardware and generates WS-Management
indications when it determines that an important event occurs. To enable complete system monitoring, both
the OA and the partitions must be monitored.
Insight RS requires WS-Man to monitor the Integrity Superdome 2 OA. If you need to send SNMP traps to
another enterprise management application, make sure you do not send the traps to the same Hosting Device
where Insight RS is installed. If the Hosting Devices receives SNMP traps in addition to the required WS-Man
notifications, this will result in duplicate notifications sent to HPE.

Fulfill configuration requirements

To configure your Integrity Superdome 2 servers to be monitored by Insight RS, complete the following
sections:
Table 13.1 Integrity Superdome 2 server configuration steps
Task Completed?

Make sure Insight RS supports your Integrity Superdome 2 server by checking the HPE Insight
Remote Support Release Notes.

Verify Superdome 2 network settings and protocol status.

Add the WBEM protocol to the Insight RS Console.

Add the WS-Man protocol to the Insight RS Console.

Discover the Superdome 2 server in the Insight RS Console.

Verify the Superdome 2 and the partitions were discovered correctly.

Send a test event to verify connectivity to the Hosting Device.

Install and configure communication software on

servers
To configure your monitored devices, complete the following sections:

Superdome 2 OA configuration verification

Connect to the Superdome 2 OA using Telnet, SSH or a web browser (HTTPS), and verify the network
settings and protocol status of the OA.
Verify the Network Settings are correct, including the DNS server addresses for both the active and standby
OAs, and verify the Protocol Status indicates that WS-Man is enabled. WS-Man is the supported event
reporting protocol for the Superdome 2 OA. SNMP should be disabled, unless you require its use, because the

HPE Insight Remote Support 7.10: Monitored Devices Configuration Guide Page 141 of 436
Chapter 13: Configuring Integrity Superdome 2 servers

SNMP Agents send redundant event notifications to Insight RS. HPE recommends that Enclosure IP Mode is
enabled.

Using Telnet or SSH

1. Telnet or SSH to the Onboard Administrator CLI.
2. Verify DNS is configured: type the show network command to show the Network Settings and Protocol
Status of the OA.
Using a web browser
1. In a web browser, log on to the Onboard Administrator web interface.
2. In the left menu, select Enclosure Information → Enclosure Settings → Enclosure TCP/IP
Settings.
3. Select Network Access and verify that WS-Management is enabled.
4. In the left menu, click the Complex Information link under Complex Overview. Click on the
Information tab to show the Product Number and Serial Number.

Install vPar v5 Prerequsites (if required)

Insight RS supports HP-UX 11i v3 vPars v5 only. vPars v6 are not supported; Insight RS cannot entitle vPars
v6 partitions because they do not have unique serial numbers and are not registered in the HPE entitlement
system.
You need the following files installed on your HP-UX 11i v3 server for vPars v5 to be supported with Insight
RS.
l VirtualPartition A.05.10 – You need the fileset VPAR-RUN from this product, which is part of the
T1335DC bundle for the vPars v5 feature. The fileset provides virtual partition command line tools that
need to be available for the WBEM VPar provider to function properly.
To verify if you have this bundle installed, run the swlist -l bundle command. You should see output
similar to the following:
T1335DC HP-UX Virtual Partitions for 11.31 A.05.10

l VParProvider B.11.31.01.06 – This fileset is available as part of the WBEM Management Bundle,
available at:
h20392.www2.hpe.com/portal/swdepot/displayInstallInfo.do?productNumber=WBEMMgmtBundle.
l HP-UX WBEM Services A.02.07 – This fileset is available as part of the WBEM Management Bundle,
available at:
h20392.www2.hpe.com/portal/swdepot/displayInstallInfo.do?productNumber=WBEMMgmtBundle.
Note that you may have already installed the WBEM Management Bundle when you installed SFM.

Configure firewall and port settings

Table 13.2 Superdome 2 Connectivity - Firewall/Port Requirements
Protocol Ports Source Destination Function Optional

HPE Insight Remote Support 7.10: Monitored Devices Configuration Guide Page 142 of 436
Chapter 13: Configuring Integrity Superdome 2 servers

Table 13.2 Superdome 2 Connectivity - Firewall/Port Requirements, continued

TCP 22 Hosting Integrity Secure Shell connection to Superdome OA to verify Optional
Device Superdome access credentials and generate test events.
2 OA

TCP 443 Hosting Integrity Secured WS-MAN communication to Superdome OA. Required
Device Superdome
2 OA

TCP 5989 Hosting Integrity WBEM communication to Integrity Superdome 2 Required

Device Superdome partitions.
2 Partitions

TCP 7905 Integrity Hosting Secure HTTP (HTTPS) port used by the listener Required
Superdome Device running in the Director's Web Interface. The monitored
2 OA host connects to the Hosting Device on this port (e.g.
https://<hostname>:7905).

TCP 7905 Integrity Hosting Secure HTTP (HTTPS) port used by the listener Required
Superdome Device running in the Director's Web Interface. The monitored
2 Partitions host connects to the Hosting Device on this port (e.g.
https://<hostname>:7905).

Add protocol credentials and start discovery

You must add WBEM and WS-Man protocol credentials to the Insight RS Console so Insight RS can
communicate with the Superdome 2 server.
To discover your monitored devices, complete the following sections:

Create a WBEM protocol credential in Insight RS Console

To configure WBEM in the Insight RS Console, complete the following steps:
1. In a web browser, log on to the Insight RS Console.
2. In the main menu, select Discovery and click the Credentials tab.
3. Selection the following filters:
a. From the Select Type drop-down list, select Server.
b. From the Select Sub-Type drop-down list, select HPE Integrity HPUX.
c. From the Select and Configure Protocol drop-down list, select Web-Based Enterprise
Management (WBEM).
4. Click New. The New Credential dialog box appears.
5. Type the Username and Password you have configured on your partitions. These are the credentials
Insight RS will use to communicate with the HP-UX partitions.
6. Click Add.

HPE Insight Remote Support 7.10: Monitored Devices Configuration Guide Page 143 of 436
Chapter 13: Configuring Integrity Superdome 2 servers

Create a WS-Man protocol credential in the Insight RS

Console
To configure WS-Man in the Insight RS Console, complete the following steps:
1. In a web browser, log on to the Insight RS Console.
2. In the main menu, select Discovery and click the Credentials tab.
3. From the Select and Configure Protocol drop-down list, select Web Services Management Protocol
(WSMAN).
4. Click New. The New Credential dialog box appears.
5. Type the Username and Password you have configured on your OA. These are the credentials Insight
RS will use to communicate with the OA.
6. Click Add.

Discover the Superdome 2 server in the Insight RS Console

To discover the Superdome 2 server and partitions from the Insight RS Console, complete the following
steps:
1. In a web browser, log on to the Insight RS Console.
2. In the main menu, select Discovery and click the Sources tab.
3. Expand the IP Addresses section and add the IP addresses for the OA and the partitions:
a. Click New.
b. Select the Single Address, Address Range, or Address List option.
c. Type the IP addresses of the OAs and HP-UX partitions to be discovered.
d. Click Add.
4. Click Start Discovery.

Note: If discovery is configured to discover standby OAs, it will populate the Devices screen with
minimal information on these devices because although their network interfaces can be active and
be reachable, they are not monitoring port 443 used for communication and therefore cannot provide
Insight RS with information about themselves. Likewise because they are standby devices Insight
RS will not be able to establish event monitoring subscriptions directly with them. If an OA failover
should occur, the OA will pass the subscription to the new Monarch and Insight RS will continue to
monitor the OA for event indications using that active subscription.

Verify Superdome 2 discovery

After discovery completes, select Devices from the main menu. Verify that all the Superdome 2 OAs and HP-
UX partitions previously configured for discovery were discovered and that the Status for those devices
shows the success icon ( ). Insight RS uses the enclosure Product Number and Serial Number for
entitlement.

HPE Insight Remote Support 7.10: Monitored Devices Configuration Guide Page 144 of 436
Chapter 13: Configuring Integrity Superdome 2 servers

Verify the Superdome 2 OA

To verify the device information for Superdome 2 OA, complete the following steps:
1. In the main menu, select Devices. Locate the Superdome 2 OA, and click its Device Name.
2. On the Device tab, expand the Status section and verify the Registration Status shows Registered, and
the Enabled has the Yes option selected.
3. Expand the Hardware section and verify the Device Name, Category, Product, Vendor, IP Address,
Acquired Serial Number and Acquired Product Number are populated correctly for the device.
4. Expand the Warranty & Contract section and verify the values listed are correct.

Note: The OS Name and OS Version fields will be blank if viewed from the Operating System
section.

5. Expand the Delivery section and verify the information is correct.

6. Expand the Device Relationships section and verify the OA and partitions have been properly
discovered. The OA should appear as the parent node with the partitions as children. Partitions that did
not discover properly display as OA_Name.nParx or OA_Name.vParx.nParx.
7. Click Save Changes to complete the discovery process for this device.

Note: Insight RS only monitors the Monarch (Active) OA. Insight RS subscribes to the OA that is
active at the time of Insight RS discovery and uses the subscription to listen for events. If an OA
failover occurs, Insight RS continues to monitor the active subscription once it is passed by the
Active OA to the Standby OA. The Insight RS Console will continue to show that it is actively
monitoring the previously configured Active OA (even though that OA has failed).

Note: A Superdome 2 32s configuration consists of two enclosures joined into a single server
complex. Each enclosure has a primary and a standby OA that manages and monitors that
enclosure. Only one of the two active OAs in the Superdome 2 32s complex is the Monarch OA for
the complex, and only it generates the WS-Man event indications produced by the Error Analysis
Engine. As is the case with Superdome 2 16s complex configurations, Insight RS will only
subscribe to the complex Monarch OA for WS-Man event indications and Insight RS will only
display the Monarch OA on its Managed Entity page.

Verify the Superdome 2 HP-UX partitions

To verify the device information for Integrity Superdome 2 HP-UX partitions, complete the following steps:
1. In the main menu, select Devices. Locate an Superdome 2 partition, and click its Device Name.
2. On the Device tab, expand the Status section and verify the Registration Status shows Registered, and
the Enabled has the Yes option selected.
3. Expand the Operating System section. The OS Name and OS Version fields reported for the partition
should match the values reported by the uname command. Type the following command in an SSH or
telnet window connection to the partition:
uname –rs

HPE Insight Remote Support 7.10: Monitored Devices Configuration Guide Page 145 of 436
Chapter 13: Configuring Integrity Superdome 2 servers

The values reported by the OS Hardware section should be the same values as reported in the OA
Hardware section detailed above. Expand the Warranty & Contract section and verify the values listed
are correct.
4. Expand the Delivery section and verify the information is correct.

Verify communication between monitored device

and Insight RS
To verify communication between your monitored device and Insight RS, complete the following sections:

Generating test events

Test events can be sent for the OA and partitions. The OA test event displays as OA event and the HP-UX
test events display as events for each partition.
The latest Superdome 2 firmware versions have the capability for an administrator to connect to the OA and
generate a WS-Man test indication. Check the HPE Support Center for recommended firmware updates.
Use the following procedure to generate a WS-Man test indication:
1. Telnet or SSH to the OA CLI interface and log on using a user account with administrator privileges.
2. Type the test wsman command.
3. In a web browser, log on to the Insight RS Console.
4. In the main menu, select Service Events. Click on the Date column header twice to sort the most recent
event to the top, and verify that Insight RS received the test event.
Send a test event from the HP-UX partitions to verify communication between the HP-UX partitions and the
Hosting Device. Execute the following command on the HP-UX server:
# /opt/sfm/bin/sfmconfig -t -a
For details on SysFaultMgmt, including issuing test events, refer to the HP-UX System Fault Management
Administration Guide at: http://www.hpe.com/info/hpux-diagnostics-sfm-docs.

Verify collections in the Insight RS Console

Collections are not automatically run after discovery. HPE recommends that you manually run a collection
after discovery completes in order to verify connectivity. Run the collection schedule manually on the
Collection Services → Collection Schedules tab. For more information about scheduling collections, see the
Insight RS Help.
Verify that this collection ran successfully on the Collection Services → Basic Collection Results tab in the
Insight RS Console.
1. Log on to the Insight RS Console.
2. In the main menu, select Collection Services and then click the Basic Collection Results tab.
3. Expand the Server Basic Configuration Collection section.
4. Locate the entry for your device and check the Result column. If the collection was successful, a
success icon appears ( ). If it failed, an error icon appears ( ).

HPE Insight Remote Support 7.10: Monitored Devices Configuration Guide Page 146 of 436
 Chapter 14: Configuring Integrity Superdome
X servers
The Integrity Superdome X system has implemented single-source event reporting such that all event
indications are reported through the Integrity Superdome X Onboard Administrator (OA). The OA monitors the
core system hardware and generates WS-Management alert indications when it determines that an important
event occurs. The Linux WS-Man providers, Windows WinRM (WS-Man) providers, and VMware WBEM
providers monitor partition IO devices and report their events through the OA as well.
Although the OA is the sole source for event reporting for the entire system complex, Insight RS still needs to
discover the partitions to support configuration collections.
Insight RS requires WS-Man to monitor the Integrity Superdome X OA.

Fulfill configuration requirements

To configure your Integrity Superdome X servers to be monitored by Insight RS, complete the following
sections:
Table 14.1 Integrity Superdome X server configuration steps
Task Completed?

Verify Integrity Superdome X network settings and protocol status.

In the Insight RS Console, add WS-Man protocol credentials for the OA for all supported
operating systems. WS-Man uses port 443 for the OA.
For Linux and Windows partitions, add WS-Man protocol credentials for the partitions. WS-Man
uses port 5986 for the Linux and Windows partitions.
For VMware partitions, add WBEM protocol credentials for the partitions. WBEM uses port 5989
for the VMware partitions.

Discover the Integrity Superdome X server in the Insight RS Console.

Discover the partitions in the Insight RS Console.

Verify the Integrity Superdome X OA and the partitions were discovered correctly.

Send an OA and partition test events to verify connectivity to the Hosting Device. Verify a
collection was successfully gathered from the OA and all partitions.

Configure communication software on servers

To configure your monitored devices, complete the following sections:

Configuring the OA
To configure your OA, complete the following sections:

Integrity Superdome X OA configuration verification

Connect to the Integrity Superdome X OA using Telnet, SSH or a web browser (HTTPS), as detailed below.
Both the username and password login credentials are case sensitive.

HPE Insight Remote Support 7.10: Monitored Devices Configuration Guide Page 147 of 436
Chapter 14: Configuring Integrity Superdome X servers

Verify the Network Settings are correct, including the DNS server addresses for both the active and standby
OAs, and verify the Protocol Status indicates that WS-Man is enabled.
HPE recommends that Enclosure IP Mode is enabled as it supports the passing of the active OA’s IP address
to the Standby OA should an OA failover occur. If Enclosure IP Mode is disabled then Insight RS should be
configured to discover both the active and the standby OA.
HPE recommends that you check www.hpe.com to make sure your OA is using the latest firmware version.

Using Telnet or SSH

1. Telnet or SSH to the Onboard Administrator CLI.
2. Verify DNS is configured: type the show network command to show the Network Settings and Protocol
Status of the OA.

Using a web browser

1. In a web browser, log on to the Onboard Administrator web interface. Either HTTP or HTTPS may be
used to open the connection to the default port.
2. In the left menu, select Enclosure Information → Enclosure Settings → Enclosure TCP/IP
Settings.

Verify the OA can send OS events

Check to verify the OA is correctly set up to send OS events with the following command:
SHOW OSEVENTS status
If set up correctly, this is the expected result:
Athena One Stop Fault Management mode is enabled for HP_AlertIndication and HP_
DeviceIndication events
If disabled, this is the expected result:
Athena One Stop Fault Management mode is disabled. Consequently, OA will not generate WS-
MAN alerts for OS events
To enable OS events, run the following command:
set OSEVENTS on

Add operator-level user (if required)

If you do not want to provide administrator access to your Superdome X OA, you may use an Operator
account on the OA for Insight RS to access. To create an Operator account, complete the following steps:
Shell > add user <name>
Shell > set user access <name> OPERATOR
Shell > assign OA <name>
Shell > assign partition all <name>

HPE Insight Remote Support 7.10: Monitored Devices Configuration Guide Page 148 of 436
Chapter 14: Configuring Integrity Superdome X servers

Configuring Linux partitions

To configure your Linux partitions, complete the following section:

Install WBEM providers

Every Linux partition must have WBEM providers installed. WS-Man uses common providers with WBEM.
Insight RS requires RHEL and SLES provider version 53 or higher for Linux partitions on Superdome X
systems to be monitored. WBEM Provider version 53 added the smx-EnableWsman component; this is
required by Insight RS.
To download and install the WBEM providers, complete the following steps:
1. In a browser, navigate to downloads.linux.hpe.com/SDR/repo/bl920-wbem/.
2. Download the providers for your version of Linux, and follow the installation instructions. The WBEM
providers require root access to install.
3. Install the SMH and smx-EnableWsman packages. The SMH and SMX-WEBAPP components are
required to generate test events from the OS partitions, and the SMX-WEBAPP component is required
for discovery and collections.
rpm -ivh hpsmh-<version>.<arch>.rpm
rpm -ivh hp-smx-EnableWsman-<version>.<distro>.<arch>.rpm

4. Create an SSL server key with the following script for the openwsman server to use:
/etc/openwsman/owsmangencert.sh
Type the information requested at the prompts.
5. Restart openwsman:
service openwsmand restart

Verify Linux Services after provider installation

After the Linux providers are installed, verify the required services are running by executing the following OS-
specific commands:
l RHEL 6.x:
service tog-pegasus status
service openwsmand status
service hpshd status
service hpmgmtbase status
service hpsmhd status

l RHEL 7.x:
systemctl status tog-pegasus
systemctl status openwsmand
systemctl status hpshd
systemctl status hpmgmtbase
service hpsmhd status

HPE Insight Remote Support 7.10: Monitored Devices Configuration Guide Page 149 of 436
Chapter 14: Configuring Integrity Superdome X servers

l SLES 11:
service sfcb status
service openwsmand status
service hpshd status
service hpmgmtbase status
service hpsmhd status

l SLES 12:
systemctl status sblim-sfcb
systemctl status openwsmand
systemctl status hpshd
systemctl status hpmgmtbase
systemctl status hpsmhd

Examples:
# service hpshd status
Checking HP Mission Critical Linux System Health Daemon 'hpshd': running
# service sfcb status
Checking for Small Footprint CIM Broker (SFCB): running
# systemctl status hpshd
hpshd.service - HP Mission Critical Linux System Health Daemon
Active: active (running) since Mon 2015-11-09 17:48:41 EST; 1 weeks 0 days ago

Configure non-root users (if required)

The WBEM providers require root access to install. However, non-root users can be used for WS-Man to
communicate between the Linux partition and Insight RS.
To configure non-root users on the Linux partition, complete the following steps for SLES:
1. Create a non-root user/password for use by Insight RS:
a. On the Linux partition, open a Command Prompt window.
b. Create a user: useradd <username>
c. Create a password for the user: passwd <username>
2. Add the new user to the sfcb group, which is created when the WBEM providers are initially installed:
usermod -G sfcb <username>
To configure non-root users on the Linux partition, complete the following steps for RHEL:
1. Create a non-root user/password for use by Insight RS:
a. On the Linux partition, open a Command Prompt window.
b. Create a user: useradd <username>
c. Create a password for the user: passwd <username>
2. Add the new user to the “pegasus” group, which is created when the WBEM providers are initially

HPE Insight Remote Support 7.10: Monitored Devices Configuration Guide Page 150 of 436
Chapter 14: Configuring Integrity Superdome X servers

installed:
usermod -G pegasus <username>
Use this non-root user when you set up the WS-Man protocol credential in the Insight RS Console. See
"Create a WS-Man protocol credential for the Linux and Windows partitions in the Insight RS Console" on
page 154.

Configuring Windows partitions

To configure your Windows partitions, complete the following sections:

Install WBEM providers

Every Windows partition must have WBEM providers installed. WS-Man uses common providers with
WBEM, and WinRM uses common providers with WMI.
To download and install the WBEM providers, complete the following steps:
1. Go to www.hpe.com/support/hpesc.
2. In the search field, type Superdome X server and click the product name in the suggested results.
3. Click the Drivers and Software tab and use the filters select your operating system.
4. In the results list, download the providers, and follow the installation instructions.

Create a signed certificate

To create a signed certificate, complete the following steps:
1. Install a signed certificate. Use the method of your choice, or use the following method using Microsoft
Management Console:
http://social.technet.microsoft.com/wiki/contents/articles/10377.create-a-certificate-request-using-
microsoft-management-console-mmc.aspx
2. As an administrator, open a Command Prompt window and execute:
winrm quickconfig –transport:https
winrm set winrm/config/service/auth @{Basic=”true”}

3. If the computer domain is a workgroup, you must add the domain suffix used in the common name when
you created the certificate:
a. Click Start, right-click Computer, and then click Properties.
b. Under Computer name, domain, and workgroup settings, click Change settings.
c. On the Computer Name tab, click Change, and then click More.
d. Add the primary DNS suffix of the computer.

Configure non-administrator users (if required)

The WBEM providers require administrator access to install. However, non-administrator users can be used
for WS-Man to communicate between the Windows 2012 or Windows 2016 partition and Insight RS.
To configure non-administrator users on the Windows 2012 or Windows 2016 partition, complete the following
steps:

HPE Insight Remote Support 7.10: Monitored Devices Configuration Guide Page 151 of 436
Chapter 14: Configuring Integrity Superdome X servers

1. Add a new user, and add the user to the following groups:
l Distributed Com Users
l WinRMRemoteWMIUsers__
l Remote Management Users
2. In Server Manager, open Tools → Computer Management.
3. In the left menu under Services and Applications, right click WMI Control and select Properties.
4. Add the user to Root:
a. In the WMI Control Properties window, on the Security tab, select Root and click Security.
b. Add the new user. Allow the same privileges as the Administrator except for Edit Security.
c. Click Advanced.
d. Select the new user and click Edit.
e. In the Apply to drop-down, select This namespace and subnamespaces.
f. Click OK, OK, OK.
5. Add the user to Interop:
a. In the WMI Control Properties window, on the Security tab, select Interop and click Security.
b. Add the new user if it does not exist. Allow the same privileges as the Administrator except for Edit
Security.
c. Click OK.
6. Add the user to HPQ:
a. In the WMI Control Properties window, on the Security tab, select HPQ and click Security.
b. Add the new user if it does not exist. Allow the same privileges as the Administrator except for Edit
Security.
c. Click OK.
The new user can now be used by Insight RS WS-Man to discover Windows 2012 or Windows 2016 partitions
on Superdome X servers.

Configuring VMware vSphere partitions

For information about configuring VMware vSphere on the partitions, see Running VMware vSphere on HPE
Integrity Superdome X at h20564.www2.hpe.com/hpsc/doc/public/display?docId=c05031408.
For information about the VMware images, see Contents of the HPE supplied VMware ESXi images at
h20564.www2.hpe.com/hpsc/doc/public/display?docId=c04430318.
In order to provide the best support experience, HPE recommends you use the latest release of providers and
firmware for new installations and recommends you update existing installations to the latest release as soon
as possible.

Verify partition status

To verify partitions' status, complete the following steps:

HPE Insight Remote Support 7.10: Monitored Devices Configuration Guide Page 152 of 436
Chapter 14: Configuring Integrity Superdome X servers

1. Telnet or SSH to the OA CLI interface and log on using a user account with administrator privileges.
2. Type the parstatus command. The output shows the partition state and status.
Par State/ Status* # of # of ILM/ Partition Name
Num RunState Blades IOBays SLM (first 15
(GB)** characters)
=== ======================= ======= ====== ====== ============= ===============
1 Active /UP OK 1 0 0.0/128.0 nPar0001
2 Active /UP OK 1 0 0.0/128.0 nPar0002
3 Active /UP OK 1 0 0.0/128.0 nPar0003
4 Active /UP OK 1 0 0.0/128.0 nPar0004
5 Active /UP OK 1 0 0.0/128.0 nPar0005
7 Active /UP OK 1 0 0.0/128.0 nPar0007

3. Verify all partitions indicate Active /UP status. The Active /UP status indicates that the partition WEBM
providers have started and the OS boot has completed.

Note: Note: VMware vSphere partitions will indicate OSBOOT status instead of Active /UP.

Configure firewall and port settings

Table 14.2 Superdome X Connectivity - Firewall/Port Requirements
Protocol Ports Source Destination Function Optional

TCP 22 Hosting Integrity Secure Shell connection to Superdome OA to verify Optional

Device Superdome access credentials and generate test events.
X OA

TCP 443 Hosting Integrity Secured WS-MAN communication to Superdome OA. Required
Device Superdome
X OA

TCP 5986 Hosting Integrity Secured WS-MAN communication to Integrity Required

Device Superdome Superdome X Linux Partitions.
X OA Linux
Partitions

TCP 5989 Hosting Integrity WBEM communication to Integrity Superdome X Required

Device Superdome VMware partitions.
X Partitions

TCP 7905 Integrity Hosting Secure HTTP (HTTPS) port used by the listener Required
Superdome Device running in the Director's Web Interface. The monitored
X OA host connects to the Hosting Device on this port (e.g.
https://<hostname>:7905).

TCP 7905 Integrity Hosting Secure HTTP (HTTPS) port used by the listener Required
Superdome Device running in the Director's Web Interface. The monitored
X Linux host connects to the Hosting Device on this port (e.g.
Partitions https://<hostname>:7905).

HPE Insight Remote Support 7.10: Monitored Devices Configuration Guide Page 153 of 436
Chapter 14: Configuring Integrity Superdome X servers

Add protocol credentials and start discovery

You must add the WS-Man protocol login credential for the OA to the Insight RS Console so Insight RS may
communicate with the OA. Also add WS-Man credentials for the Linux and Windows partitions, and add
WBEM credentials for the VMware partitions to the Insight RS Console so Insight RS may communicate with
the partitions.
To discover your monitored devices, complete the following sections:

Create a WS-Man protocol credential for the OA in the

Insight RS Console
To configure WS-Man in the Insight RS Console, complete the following steps:
1. In a web browser, log on to the Insight RS Console.
2. In the main menu, select Discovery and click the Credentials tab.
3. From the Select and Configure Protocol drop-down list, select Web Services Management Protocol
(WSMAN).
4. Click New. The New Credential dialog box appears.
5. Use the default port: 443.
6. Type the Username and Password credentials that Insight RS will use to communicate with the OA.
7. Click Add.

Create a WS-Man protocol credential for the Linux and

Windows partitions in the Insight RS Console
Note: The Windows partitions use WinRM, which is Microsoft's implementation of WS-Man. In the
Insight RS Console, configure a WS-Man protocol for both Linux and Windows partitions.

To configure WS-Man in the Insight RS Console, complete the following steps:

1. In a web browser, log on to the Insight RS Console.
2. In the main menu, select Discovery and click the Credentials tab.
3. From the Select and Configure Protocol drop-down list, select Web Services Management Protocol
(WSMAN).
4. Click New. The New Credential dialog box appears.
5. Change the default port to: 5986.
6. Type the Usernames and Passwords that Insight RS will use to communicate with each of the partitions.
7. Click Add.

Note: Create additional WS-Man protocol credentials if your partitions use different credentials.

HPE Insight Remote Support 7.10: Monitored Devices Configuration Guide Page 154 of 436
Chapter 14: Configuring Integrity Superdome X servers

Create a WBEM protocol credential for the VMware

vSphere partitions in the Insight RS Console
To configure WBEM in the Insight RS Console, complete the following steps:
1. In a web browser, log on to the Insight RS Console.
2. In the main menu, select Discovery and click the Credentials tab.
3. From the Select and Configure Protocol drop-down list, select Web-Based Enterprise Management
(WBEM).
4. Click New. The New Credential dialog box appears.
5. Type the Username and Password you have configured on your device.
6. Click Add.

Discover the Integrity Superdome X server and partitions in

the Insight RS Console
To discover the Integrity Superdome X server and partitions from the Insight RS Console, complete the
following steps:
1. In a web browser, log on to the Insight RS Console.
2. In the main menu, select Discovery and click the Sources tab.
3. Expand the IP Addresses section and add the IP addresses for the OA and the partitions:
a. Click New.
b. Select the Single Address, Address Range, or Address List option.
c. Type the IP addresses of the OAs and partitions to be discovered.
d. Click Add.
4. Click Start Discovery.

Note: If discovery is configured to discover standby OAs, it will populate the Devices screen with
minimal information on these devices because although their network interfaces can be active and
be reachable, they are not monitoring port 443 used for communication and therefore cannot provide
Insight RS with information about themselves. Likewise because they are standby devices Insight
RS will not be able to establish event monitoring subscriptions directly with them. If an OA failover
should occur, the OA will pass the subscription to the new Monarch and Insight RS will continue to
monitor the OA for event indications using that active subscription.

Verify Integrity Superdome X discovery

After discovery completes, select Devices from the main menu. Verify that all the Integrity Superdome X OAs
and partitions previously configured for discovery were discovered and that the Status for those devices
shows the success icon ( ).

HPE Insight Remote Support 7.10: Monitored Devices Configuration Guide Page 155 of 436
Chapter 14: Configuring Integrity Superdome X servers

Verify the Integrity Superdome X OA

To verify the device information for Integrity Superdome X OA devices, complete the following steps:
1. In the main menu, select Devices. Locate the Integrity Superdome X OA, and click its Device Name.
2. On the Device tab, expand the Status section and verify the Registration Status shows Registered, and
Enabled shows Yes.
3. Expand the Hardware section and verify the Device Name, Category, Product, Vendor, IP Address,
Acquired Serial Number and Acquired Product Number are populated correctly for the device. The
category should be reported as MANAGEMENT_DEVICE, the Product should be reported as
Superdome 2 16s x86 and the Vendor should be hp. The remaining values may be verified using the
Telnet or web browser steps outlined above.
4. Expand the Warranty & Contract section and verify the values listed are correct.

Note: The OS Name and OS Version fields reported for the OA will be blank if viewed from the
Operating System section.

5. Expand the Delivery section and verify the information is correct.

Verify the Integrity Superdome X partitions
To verify the device information for Integrity Superdome X partitions devices, complete the following steps:
1. In the main menu, select Devices. Locate an Integrity Superdome X partition, and click its Device Name.
2. On the Device tab, expand the Status section and verify the Registration Status shows Registered, and
the Enabled has the Yes option selected.
3. Expand the Operating System section. The OS Name and OS Version fields reported for the partition
should match the values reported by the following command:
l For Linux and VMware, type the following command in an SSH or telnet window connection to the
partition:
uname –rs
l For Windows, type the following command in a cmd window on the partition:
systeminfo | findstr /B /C:"OS Name" /C:"OS Version"
The values reported by the OS Hardware section should be the same values as reported in the OA
Hardware section detailed above. Expand the Warranty & Contract section and verify the values listed
are correct.
4. Expand the Delivery section and verify the information is correct.

Verify communication between monitored device

and Insight RS
To verify communication between your monitored device and Insight RS, complete the following sections:

HPE Insight Remote Support 7.10: Monitored Devices Configuration Guide Page 156 of 436
Chapter 14: Configuring Integrity Superdome X servers

Generating test events

The Integrity Superdome X supports the capability for an administrator to connect to the OA and generate a
WS-Man test indication. Use the following procedure to generate a WS-Man test indication:
1. Telnet or SSH to the OA CLI interface and log on using a user account with administrator privileges.
2. Type the test wsman command.
3. In a web browser, log on to the Insight RS Console.
4. In the main menu, select Service Events. Click on the Date column header twice to sort the most recent
event to the top, and verify that Insight RS received the test event.
Test events can be sent from the partitions using System Management Homepage (SMH). When you send a
test event, it is sent transmitted by the OS partition provider and also by the OA. Insight RS only uses the
event that comes through the OA path. The OS partition provider does not pass Informational events to the
OA, so an Informational test event should not be used for this verification step.
For Linux and Windows partitions, to send a test event from each partition, complete the following steps:
1. Open a web browser and connect to the System Management Homepage (SMH) running on the partition
on port 2381. Log on using a user account with administrator privileges.
2. In SMH, browse to Settings → Test Indication, and click Send Test Indication.
3. Select Warning or Error for the test indication Type.
4. Click Send.
5. In a separate web browser, log on to the Insight RS Console.
6. In the main menu, select Service Events. Click on the Date column header twice to sort the most recent
event to the top, and verify that Insight RS received the test event. Note that partition events are reported
through the OA, so you must click on the OA to view events. To identify which partition originated the
event, open the Service Event by clicking on the Event ID link, scroll down to the Failing Host Details
section and verify the value reported in the Failing Host Preferred FQDN field is the partition name and/or
the value reported in the Failing Host Preferred IP field is the IP address used for that partition.
SMH is not supported on VMware vSphere on the Superdome X, however the VMware vSphere installation
includes the installation of the “HPE ESXi utilities offline Bundle for VMware”, which includes a test event
utility.
For VMware vSphere partitions, to send a test event from each partition, compete the following steps:
1. SSH to a VMware vSphere partition.
2. Type the following command: /opt/hp/tools/hptestevent
This results in a HP_Test provider eventID 1 being generated and transmitted to Insight RS by the
Superdome X OA.

Verify collections in the Insight RS Console

Collections are not automatically run after discovery. HPE recommends that you manually run a collection
after discovery completes in order to verify connectivity. Run the collection schedule manually on the
Collection Services → Collection Schedules tab. For more information about scheduling collections, see the
Insight RS Help.

HPE Insight Remote Support 7.10: Monitored Devices Configuration Guide Page 157 of 436
Chapter 14: Configuring Integrity Superdome X servers

Verify that this collection ran successfully on the Collection Services → Basic Collection Results tab in the
Insight RS Console.
1. Log on to the Insight RS Console.
2. In the main menu, select Collection Services and then click the Basic Collection Results tab.
3. Expand the Server Basic Configuration Collection section.
4. Locate the entry for your device and check the Result column. If the collection was successful, a
success icon appears ( ). If it failed, an error icon appears ( ).

If desired, configure your Integrity Superdome X as

a solution
To add your Integrity Superdome X to Insight RS as a solution, complete the following steps:
1. In the main menu, select Solution Manager.
2. In the List of Solutions pane, click Add New Solution. The fields you need to complete appear in the
Create New Solution pane.
3. In the Create New Solution pane, complete the following fields:

Field Action

Solution Name Type a unique name for the solution.

Solution Type Select a solution from the drop-down list of supported HPE solutions.
This selection will populate the Solution Product Number and Solution
Product Model fields. If you select Other, you must populate those fields.

Solution Serial Number Type the serial number of the solution, which can be found on the hardware
label or in the order information when you purchased the HPE solution.

Solution Product Number The product number of the solution is automatically populated based on what
you selection in the Solution Type drop-down list.

Solution Product Model The product model of the solution is automatically populated based on what
you selection in the Solution Type drop-down list.

Custom Delivery ID Type the optional alphanumeric value that will only be required if it has been
supplied to you by your HPE representative or in setup instructions for the
purpose of customized handling or routing of service events sent to HPE.

4. Click Save. The system creates and displays the new solution in the List of Solutions pane. The
assigned devices pane appears where you can assign devices to the new solution.
5. Assign devices or partitions in the assigned devices pane. The default view shows devices not assigned
to the solution. To show additional devices, click the Not Assigned to this Solution or All Devices
options. To show devices in a specific device group, select a device group from the Filter by device
group drop-down list. To search for a specific device, type the device name into the Search box. The
table displays the devices based on your filter and search criteria.
l To add a device, select the check box next to the device in the devices table.

HPE Insight Remote Support 7.10: Monitored Devices Configuration Guide Page 158 of 436
Chapter 14: Configuring Integrity Superdome X servers

l To remove a device, clear the check box next to the device in the devices table.
6. Click Save Devices.
The system creates and displays the solution in the List of Solutions pane.

HPE Insight Remote Support 7.10: Monitored Devices Configuration Guide Page 159 of 436
 Chapter 15: Configuring Superdome Flex
servers
The Superdome Flex system can be monitored by Insight RS and discovered as a solution through the Rack
Management Controller (RMC), or, if your solution does not have an RMC, through embedded RMC (eRMC)
software on the Baseboard Management Controller (BMC).
For more information about Superdome Flex servers, go to: www.hpe.com/support/sd-flex-customer-docs.

Fulfill configuration requirements

To configure your Superdome Flex servers to be monitored by Insight RS, complete the following sections:
Table 15.1 Superdome Flex configuration steps
Task Required/ Complete?
Optional

Make sure Insight RS supports your Superdome Flex server by checking the Required
HPE Insight Remote Support Release Notes.

Install the DCD software. Required

Add the ESA protocol to the Insight RS Console. Required

Discover the Superdome Flex server in the Insight RS Console. Required

Verify connectivity between your Superdome Flex server and Insight RS. Required

Configure monitored devices

To configure your monitored devices, complete the following section:

Install and configure software

Ensure that you have the Data Collection Daemon (DCD) software installed. This enables Insight RS to
gather operating system information from the Superdome Flex server.
DCD is packaged and installed as part of HPE Foundation Software (HFS). When you download and install
HFS, DCD and its dependencies (storelib) get installed and the DCD service is automatically started for
monitoring your server.
To verify DCD is installed and started, run the following commands on Linux distributions:
l To verify if DCD is installed: rpm -qi hpe-dcd
l Show the version of DCD installed on the system: rpm -qi hpe-dcd | grep -i version
l DCD Service details and status can be checked using the following commands:
# systemctl status dcd.service
dcd.service must be in “Active” running state.
# ps -ef | grep dcdExecutive

HPE Insight Remote Support 7.10: Monitored Devices Configuration Guide Page 160 of 436
Chapter 15: Configuring Superdome Flex servers

Configure firewall and port settings

Table 15.2 Superdome Flex Connectivity - Firewall/Port Requirements
Protocol Ports Source Destination Function Optional

TCP 443 Hosting RMC ESA Event Listener. Required

Device

TCP 7906 RMC Hosting Secure HTTP (HTTPS) port used by the listener running on Required
Device the Embedded Support Device. The management device
connects to the Hosting Device on this port (e.g.
https://<hostname>:7906).

Add protocol credentials and start discovery

To enable Insight RS to view events and gather collections, you must set up Embedded Support Automation
(ESA) protocol credentials in the Insight RS Console.
Insight RS communicates with the Superdome Flex through the Rack Management Controller (RMC), or if
you ordered a Superdome Flex without an RMC, Insight RS communicates with the Superdome Flex through
the embedded RMC on the Baseboard Management Controller (BMC).
To discover your monitored devices, complete the following sections:

Create an Embedded Support Automation Protocol (ESA)

credential in the Insight RS Console
To configure ESA in the Insight RS Console, complete the following steps
1. In a web browser, log on to the Insight RS Console.
2. In the main menu, select Discovery and click the Credentials tab.
3. From the Select and Configure Protocol drop-down list, select Embedded Support Automation
Protocol (ESA).
4. Click New. The New Credential dialog box appears.
5. Use the default port: 443.
6. Type the Username and Password credentials for the RMC or BMC if it is an eRMC configuration. Use
the default Administrator account.
7. Click Add.

Discover the Superdome Flex server in the Insight RS

Console
To discover the Superdome Flex server from the Insight RS Console, complete the following steps:
1. In a web browser, log on to the Insight RS Console.
2. In the main menu, select Discovery and click the Sources tab.
3. Expand the IP Addresses section and add the IP address for the RMC:

HPE Insight Remote Support 7.10: Monitored Devices Configuration Guide Page 161 of 436
Chapter 15: Configuring Superdome Flex servers

a. Click New.
b. Select the Single Address, Address Range, or Address List option.
c. Type the IP address of the RMC or the BMC if it is an eRMC configuration.
d. Click Add.
4. Click Start Discovery.

Verify Superdome Flex discovery

After discovery completes, verify the Superdome Flex was discovered. The Superdome Flex is a solution,
and Insight RS does not discover the individual devices that comprise the solution. However, information
about the components of the solution are returned to Insight RS.
To verify the device information for the Superdome Flex and its components, complete the following steps:
1. In the main menu, select Devices. Locate the Superdome Flex. Verify the Superdome Flex was
discovered and that the Status shows the success icon ( ). Verify the Product is Superdome Flex and
the OS is Solution. At this level you will also see any Open Service Events.
2. Click the Superdome Flex Device Name, and on the Device tab, expand the Status section and verify
the Registration Status shows Registered, and Enabled shows Yes.
3. Expand the Hardware section and verify the Device Name, Category, Product, Vendor, IP Address,
Acquired Serial Number and Acquired Product Number are populated correctly for the device.
4. Expand the Warranty & Contract section and verify the values listed are correct.
5. Expand the Delivery section and verify the information is correct.
6. Expand the Solution Relationships section and verify every Superdome Flex component is listed.
7. Verify the details for each solution component:
l Option 1: Within the Solution Relationships section, click each components' name to view its details.
l Option 2: Return to Devices in the main menu. Click the icon next to the Superdome Flex solution
to show the components of the solution. Their status will be greyed out ( ), but they will show
Warranty & Contract, Eligible and Enabled statuses. Collections are also greyed out here because
collections are collected on the solution, not the components. Click each components' name to view
its details.
For each component, verify the following:
a. For the Base Chassis Hardware, verify the information in the Hardware section.
b. For the RMC, verify the information in the Hardware section.
c. For the Superdome Flex OS partition, verify the information in the Operating System section.

Verify communication between monitored device

and Insight RS
To verify communication between your monitored device and Insight RS, complete the following sections:

HPE Insight Remote Support 7.10: Monitored Devices Configuration Guide Page 162 of 436
Chapter 15: Configuring Superdome Flex servers

Generating test events

To verify connectivity from the monitored device to the Hosting Device, send a test event to the Hosting
Device and then verify the test event was received in the Insight RS Console.
To send a test event, complete the following steps:
1. On the Hosting Device, open a Command Prompt window and type the following command:
rsadmin endpointCmd -triggerTestEvent <Superdome_Flex_IP_Address>
2. In a web browser, log on to the Insight RS Console.
3. In the main menu, select Service Events. Click on the Date column header twice to sort the most recent
event to the top, and verify that Insight RS received the test event.

Verify collections in the Insight RS Console

Collections are not automatically run after discovery. HPE recommends that you manually run a collection
after discovery completes in order to verify connectivity. Run the collection schedule manually on the
Collection Services → Collection Schedules tab. For more information about scheduling collections, see the
Insight RS Help.
Verify that this collection ran successfully on the Collection Services → Basic Collection Results tab in the
Insight RS Console.
1. Log on to the Insight RS Console.
2. In the main menu, select Collection Services and then click the Basic Collection Results tab.
3. Expand the Server Basic Configuration Collection section.
4. Locate the entry for your device and check the Result column. If the collection was successful, a
success icon appears ( ). If it failed, an error icon appears ( ).

HPE Insight Remote Support 7.10: Monitored Devices Configuration Guide Page 163 of 436
 Chapter 16: Configuring HPE OpenVMS
Integrity servers
Fulfill configuration requirements
To configure your HPE OpenVMS servers to be monitored by Insight RS, complete the following sections:
Table 16.1 HPE OpenVMS server configuration steps
Task Complete?

Make sure Insight RS supports your Integrity OpenVMS server by checking the HPE Insight
Remote Support Release Notes.

Install and configure ELMC for HPE OpenVMS on the OpenVMS server.

Install the HPE OpenVMS WBEM Services and WBEM Providers or enable SNMP.

(Optional) Configure Dynamic Processor Resilience.

Add the WBEM or SNMP protocol to the Insight RS Console.

Discover the OpenVMS server in the Insight RS Console.

(Optional) Configure SAN collections.

Send a test event to verify connectivity between your OpenVMS server and Insight RS.

Manually run collections to verify they are gathered.

Install and configure communication software on

servers
To configure your monitored devices, complete the following sections:

Fulfill ELMC system requirements

HPE OpenVMS monitored devices must meet the following requirements before ELMC is installed. In
clusters, minimum requirements apply to each node in the cluster.

Fulfilling hardware and software requirements

l Processor architecture: Integrity (Itanium) Server
l Operating system: HPE OpenVMS Itanium (Integrity) — 8.3-1H1 or higher.

Note: Some supported HPE OpenVMS platforms require a minimum version of 8.4. See
h71000.www7.hp.com/openvms/hw_supportchart.html.

HPE Insight Remote Support 7.10: Monitored Devices Configuration Guide Page 164 of 436
Chapter 16: Configuring HPE OpenVMS Integrity servers

Note: HPE Sustaining Engineering maintains a schedule of support for the HPE OpenVMS
operating system. HPE does not commit to supporting Insight Remote Support when installed on
an operating system version that has exceeded its end-of-support date. For more information, go
to: h71000.www7.hp.com/openvms/hw_supportchart.html.

l Minimum 20,000 blocks free disk space.

l Connectivity: TCP/IP must be installed and running.
The ability to resolve the local host name into an IP address must be enabled. Otherwise, the Director
cannot handle ELMC message traffic correctly and fails to start.
ELMC officially supports only one TCP/IP product for HPE OpenVMS: TCP/IP Services for HPE
OpenVMS, version V5.6-9ECO2 or higher.

Note: Other TCP/IP products may work as is, so the Insight RS installation always completes
regardless of what, if any, TCP/IP product is installed.

l LOCALHOST entry: For ELMC to operate correctly, the LOCALHOST entry must be defined in the
OpenVMS TCP/IP HOSTS database. It is defined correctly by default, but it can be removed, which
causes Insight RS to fail.
Type the following command:
$ TCPIP SHOW HOST /LOCAL
Look for LOCALHOST, which should have an IP address of 127.0.0.1. If LOCALHOST does not appear in
the list, type the following command:
$ TCPIP SET HOST LOCALHOST /ADDRESS=127.0.0.1 /ALIAS=LOCALHOST
Type a ping command to verify that LOCALHOST was added:
$ TCPIP PING LOCALHOST
PING LOCALHOST (127.0.0.1): 56 data bytes
64 bytes from 127.0.0.1: icmp_seq=0 ttl=64 time=0 ms
64 bytes from 127.0.0.1: icmp_seq=1 ttl=64 time=0 ms
64 bytes from 127.0.0.1: icmp_seq=1 ttl=64 time=0 ms

After verifying that LOCALHOST responds to the ping command, you can use Ctrl-C or Ctrl-Y to stop pinging.
l System firmware: In general, users should take advantage of the latest improvements by obtaining the
most recent firmware version available for their platforms.

Fulfilling required permissions and access

Grant permissions required to install ELMC

To install or uninstall ELMC, the user needs all of the following OpenVMS privileges:
l ALTPRI
l BUGCHK
l BYPASS

HPE Insight Remote Support 7.10: Monitored Devices Configuration Guide Page 165 of 436
Chapter 16: Configuring HPE OpenVMS Integrity servers

l CMKRNL
l DIAGNOSE
l IMPERSONATE
l NETMBX
l OPER
l SYSLCK
l SYSPRV
l TMPMBX
HPE recommends that you install ELMC using the SYSTEM account.

Grant permissions required to run ELMC

To execute any ELMC commands, the user needs all of the following OpenVMS privileges. Note that these
are a subset of the privileges required to install, upgrade or uninstall ELMC:
l ALTPRI
l BUGCHK
l CMKRNL
l DIAGNOSE
l IMPERSONATE
l NETMBX
l SYSPRV
l TMPMBX

Heterogeneous cluster instructions

A heterogeneous cluster is a cluster with multiple system disks. Before beginning the ELMC installation in an
OpenVMS cluster with multiple system disks, check to see if the system disks are mounted cluster-wide. To
avoid potential problems, all remotely mounted system disks should be dismounted prior to installing ELMC
on an OpenVMS heterogeneous cluster. After the install is done, the system administrator can remount the
disks. Failure to perform this step can result in the following:
l When user has a heterogeneous cluster where the system disks are mounted cluster-wide, all of the ELMC
[root.SYSCOMMON.HP.NODES.nodename] directories will be created on the system disk where the install
was performed. No directories are created on the other system disks.
l The PCSI database will only be updated on the system disk where the installation was performed. The
WCCProxy process will be running on other cluster members with different system disks; however, a
PRODUCT SHOW PRODUCT will not provide any indication that the product was actually installed.
l On every node of the cluster the ELMC WCCPROXY process runs the images from the system disk where
the installation was performed. This may be problematic if the other system disks are running different
versions of OpenVMS or have different operating system patches installed.

HPE Insight Remote Support 7.10: Monitored Devices Configuration Guide Page 166 of 436
Chapter 16: Configuring HPE OpenVMS Integrity servers

l If the system disk where the installation was performed is unavailable due to a planned shutdown or crash,
the ELMC application will fail to run on the remaining nodes of the cluster. This means that no monitoring
will occur until the system disk where the installation was performed becomes available again.
The following example illustrates the issue: assume the user has a 2 node cluster with one system running
OpenVMS 8.3-1H1 and another system running OpenVMS 8.4. If ELMC is installed on the system running
OpenVMS 8.3-1H1, the system running OpenVMS 8.4 will have a WCCProxy process running images from
the OpenVMS 8.3-1H1 system disk, which will be using library modules from the OpenVMS 8.4 system disk.
This combination of images and library modules may cause issues. If the user examines the PCSI database
of the OpenVMS 8.4 system disk, there will be no evidence that ELMC is installed and running on this
system. The ELMC root for the OpenVMS 8.4 system will be created on the OpenVMS 8.3-1H1 system disk.
If the OpenVMS 8.3-1H1 system is shutdown, the ELMC application on the OpenVMS 8.4 system will stop
functioning until the OpenVMS 8.3-1H1 system is rebooted.

Archiving and cleaning the error log

After Insight Remote Support is installed on the Hosting Device, it uses ELMC to analyze all events stored in
the error log, which can result in high CPU usage over an extended period. To control this operation, you are
encouraged to archive and clean the error log before installing. This reduces the size of the log and the time
required for the initial scan.
Follow these guidelines for cleaning the error log. If ELMC is installed and running when you clean the log, you
do not need to stop and restart the Director process. Also, do not stop and restart the ERRFMT system event
logging process.
The default error log, typically SYS$SYSROOT:[SYSERR]ERRLOG.SYS, increases in size and remains on the
system disk until the user explicitly renames or deleted it. When either occurs, the system creates a new,
clean error log file after about 15 minutes.

Caution: After renaming or deleting the existing log, do not install ELMC until the new default log is
present.

If you rename the log, the saved log can be analyzed at a later time.
Aside from starting with a clean log before installing Insight Remote Support, you may want to perform regular
maintenance on the error log. One method is to rename errlog.sys on a monthly basis. For example, you
might rename errlog.sys to errlog.old at 00:01 on the first day of every month. To free space on the
system disk, you then can back up the renamed version to a different volume and delete the file from the
system disk.

Confirm SYSMAN is functioning cluster-wide

The installation of ELMC makes use of the SYSMAN utility. Confirm that SYSMAN is functioning correctly on
every node of a cluster before attempting ELMC installation. Issue the following command to confirm that the
SHOW DEVICE SYS$SYSDEVICE: command completes normally for all nodes in the cluster.
$ MCR SYSMAN
SYSMAN> SET ENV/CLUSTER
SYSMAN> DO SHOW DEVICE SYS$SYSDEVICE:

HPE Insight Remote Support 7.10: Monitored Devices Configuration Guide Page 167 of 436
Chapter 16: Configuring HPE OpenVMS Integrity servers

How to remove ELMC

If you have an older version of ELMC installed, remove this before installing the latest version of ELMC. You
can determine if you have an older version by issuing the following command.
$ PRODUCT SHOW PRODUCT WCCPROXY
If the version of WCCPROXY is anything other than V6.4, ELMC needs to be upgraded.
If the cluster has multiple system disks, check to see if the system disks are mounted cluster-wide. To avoid
potential problems, all remotely mounted system disks should be dismounted prior to removing ELMC on an
OpenVMS heterogeneous cluster.
1. Stop the WCCPROXY process:
l If this is a standalone system, issue the following command:
$ wccproxy stop
l If this is a cluster, stop WCCPROXY processes by issuing the following commands:
$ mcr sysman
SYSMAN> set env/cluster
SYSMAN> do wccproxy stop

2. Confirm no WCCPROXY processes exist by issuing the following command:

$ show system/process=wccproxy/cluster
If any WCCPROXY processes exist that could not be terminated, issue a STOP/ID=<pid_of_wccproxy_
process> on the system with the WCCPROXY process.
3. Find the WCCPROXY_INSTALL.COM procedure located in the installation directory of ELMC by issuing the
following command:
$ directory WCCPROXY_HOME:[*...]wccproxy_install.com
Directory WCCPROXY_COMMON:[COMMON.WCCPROXY.BIN]
WCCPROXY_INSTALL.COM;1
Total of 1 file.

4. If the WCCPROXY_HOME logical points to a nonexistent disk, then search the system disk for the WCCPROXY_
INSTALL.COM procedure.
$ directory sys$sysdevice:[*...]wccproxy_install.com
5. ELMC can be removed by executing the WCCPROXY_COM procedure found in the ELMC installation
directory.
$ @WCCPROXY_COMMON:[COMMON.WCCPROXY.BIN]wccproxy_install.com "uninstall"
If no WCCPROXY_INSTALL.COM procedure can be located, then use the v6.4 WCCPROXY_INSTALL.COM
procedure.

Install the ELMC HPE OpenVMS Software Package on the

Monitored Device
Check if ELMC is already installed with the command: product show product wccproxy.

HPE Insight Remote Support 7.10: Monitored Devices Configuration Guide Page 168 of 436
Chapter 16: Configuring HPE OpenVMS Integrity servers

If this returns 0 items found then ELMC has never been installed. If the version of WCCPROXY is anything
other than V6.4, ELMC needs to be upgraded. For how to uninstall older versions of ELMC, see "How to
remove ELMC" on the previous page.
To install the ELMC software package, complete the following steps:
1. In the Insight RS Console, navigate to the Administrator Settings → Software Updates tab and select
the Event Log Monitoring Collector (ELMC) software package.
2. On the Available Version tab, click Download.
3. When the download completes, click Install. The ELMC packages are placed in the %HP_RS_
DATA%\SWM\LANDINGZONE\ELMC folder. This folder defaults to
C:\ProgramData\HP\RS\DATA\SWM\LANDINGZONE\ELMC.

Note: The ProgramData folder is a hidden folder. To view this folder, set the folder options to
show hidden folders.

4. Copy the HPE OpenVMS Itanium ELMC software package (ELMCV64BL1KIT1_21-JUN-2012_

OVMSI64.EXE) to the OpenVMS monitored device. Place the .exe file in an empty directory. Make sure
that:
l There are no other kits in the directory, especially other versions of ELMC kits.
l There are no old ELMC or WCCProxy files in the directory left over from previous operations.
5. Extract the ELMC installation files:
$ run ELMCV64BL1KIT1_21-JUN-2012_OVMSI64.EXE
6. Run the wccproxy_install.com command procedure to either upgrade or install ELMC. Then follow the
prompts.
l Run the following command to install ELMC on the system disk:
$ @wccproxy_install.com "install"
l Run the following command to install ELMC on a disk other than the system disk:
$ @wccproxy_install.com "install" "<installation directory>"
Example:
$ @wccproxy_install.com "install" "COMMON$DISK:[ELMC]"
The installation asks the following question:
Use the following command to install standalone ELMC/Proxy kit
@WCCPROXY_INSTALL.COM INSTALL <installation_path> Do you want to continue?[NO]:

Respond YES to this question.

Note: The command executes the DCL script wccproxy_install.com in the current directory.
Do not run the product install wccproxy command that would normally be used to install a
PCSI-based product. This command aborts and prompts you to run the wccproxy_
install.com script instead. Set your default directory to the one containing the file wccproxy_
install.com, created by extracting the ELMC .exe file in the previous step.

HPE Insight Remote Support 7.10: Monitored Devices Configuration Guide Page 169 of 436
Chapter 16: Configuring HPE OpenVMS Integrity servers

When the DCL prompt ($) returns, the install has finished and the ELMC (WCCProxy) process will be
running.
7. Add the WCCPROXY STOP command to SYS$MANAGER:SYSHUTDWN.COM command procedure.
No command has to be added to the site specific boot command procedure since the installation will
have added the following to the SYSMAN utility:
SYSMAN> startup show file WCCPROXY$STARTUP.COM
%SYSMAN-I-COMFIL, contents of component database on node XXXX
Phase Mode File
------------ ------ ---------------------------------
LPMAIN DIRECT WCCPROXY$STARTUP.COM

WCCPROXY command verb reference

The installation of ELMC adds the WCCPROXY command to the DCLTABLES of the OpenVMS system.
l WCCPROXY START
This command starts the WCCPROXY process.
l WCCPROXY STOP
This command stops the WCCPROXY process.
l WCCPROXY STATUS
This command shows the status of the WCCPROXY process.

Install ELMC when a new system is added to an existing

ELMC installation
If the cluster has multiple system disks, check to see if the system disks are mounted clusterwide. To avoid
potential problems, all remotely mounted system disks should be dismounted prior to installing ELMC on an
OpenVMS heterogeneous cluster. After the install is done, the system administrator can remount the disks.
Next determine if the new cluster member boots off a system which already has ELMC installed.
$ PRODUCT SHOW PRODUCT WCCPROXY
If this returns, 0 items found then ELMC has never been installed on this system disk.
l If ELMC is not installed, install it by executing the following command in a directory that contains the
ELMC installation kit. For where to obtain the ELMC kit, see "Install the ELMC HPE OpenVMS Software
Package on the Monitored Device" on page 168.
$ @wccproxy_install.com "install"
l If ELMC is already installed on the system disk uninstall and reinstall ELMC. Complete the following in a
directory that contains the ELMC installation kit:
a. Remove WCCPROXY:
$ @wccproxy_install.com "uninstall"
b. Install WCCPROXY:
$ @wccproxy_install.com "install"

HPE Insight Remote Support 7.10: Monitored Devices Configuration Guide Page 170 of 436
Chapter 16: Configuring HPE OpenVMS Integrity servers

Install and configure WBEM or SNMP

You can configure either WBEM or SNMP for discovery. WBEM must be used if you require Basic
Configuration Collections, which are necessary if your system is covered by a Proactive services contract.
SNMP can be used if you do not require Basic Configuration Collections.

Option 1: Install the HPE OpenVMS WBEM Services and WBEM

Providers
The following steps configure WBEM Services (WBEMCIM) and WBEM Providers (WBEMPROVIDERS).
Make sure that you are logged into the SYSTEM account; a fully privileged user account is not sufficient for
this activity. For more information about HPE OpenVMS WBEM, see h71000.www7.hp.com/doc/wbem.html.
Before installing or upgrading, check what versions of WBEMCIM and WBEMPROVIDERS are installed. An
upgrade of these products will be necessary if you are not running the most recent version. The minimum
version that you should be running are shown below.
To view your version of WBEM, run the following command: PRODUCT SHOW PRODUCT WBEM*
l HPE OpenVMS 8.4
l HP I64VMS WBEMCIM V3.0-2
l HP I64VMS WBEMPROVIDERS V2.2-3
l HPE OpenVMS 8.3-1H1
l HP I64VMS WBEMCIM V3.0-2
l HP I64VMS WBEMPROVIDERS V1.7-21
l If your system has the product SSL1 installed then the following version of WBEMCIM and
WBEMPROVIDERS should be installed:
l HP I64VMS WBEMCIM V3.0-3
l HP I64VMS WBEMPROVIDERS V2.2-5
If your system has does not have SSL1 installed, go to the following webpage to obtain the latest kits for
WBEMCIM and WBEMPROVIDERS. h71000.www7.hp.com/openvms/products/wbem/wbem_
download.html.
If your system has SSL1 installed, go to the HPE Support Center website www.hpe.com/support/hpesc to
obtain the latest kits for WBEMCIM and WBEMPROVIDERS. Download the following patches:
l HP-I64VMS-WBEMCIM-V0300-3A-1
l HP-I64VMS-WBEMPROVIDERS-V0202-5-1
WBEM Services can be run and configured on any Integrity model. However, some WBEM Providers are only
supported for specific models:
v1.7-21 WBEM Providers (OpenVMS 8.3-1H1 version) is only supported for the following models:
l Integrity server blades - BL860c, BL870c
l Non-cell based systems - rx3600, and rx6600
v2.2-3 and V2.2-5 WBEM Providers (OpenVMS 8.4 version) is supported for the following:

HPE Insight Remote Support 7.10: Monitored Devices Configuration Guide Page 171 of 436
Chapter 16: Configuring HPE OpenVMS Integrity servers

l Integrity server blades - BL860c i2, BL870c i2, BL890c i2, BL860c, and BL870c
l Non-cell based systems - rx1620, rx2600, rx3600, rx4640, rx6600, and rx2800 i2 servers
l Cell based systems - Superdomes, rx7620, rx8620, and rx8640
l Integrity Virtual Machine running OpenVMS Version 8.4 as a guest
Confirm TCP/IP IP address and name resolution is functioning
Before configuring WBEM Services and WBEM Providers, confirm that TCP/IP is correctly configured. Make
sure that you are able to ping by IP address, system name, and fully qualified name from the Hosting Device
to the OpenVMS system and from the OpenVMS system to the Hosting Device. If the address or name is not
found, add it to the local host file or to the DNS server.
If your OpenVMS system has both a DNS TCP/IP cluster alias name and node specific name that refer to the
same IP address, add the fully qualified name of the node specific name to the local host file of the Insight RS
Hosting Device.

Check if WBEM was previously configured

Check to see if WBEM Services or WBEM Providers were previously configured so you know whether you
need to perform a fresh install or an upgrade. If any of the below tests are positive, then WBEM Services and
WBEM Providers has been previously configured and therefore you should upgrade instead of perform a fresh
install.
1. Are the following processes are running?
$ SHOW SYSTEM/PROCESS=OPEN*
00007252 OPENVMS_UTILD HIB 5 59581523 0 03:57:40.96 532 546
00007253 OPENVMS_EMS HIB 5 3975 0 00:00:01.87 1092 1965 M

$ SHOW SYS/PROCESS=CIM*
00007227 CIMSERVER HIB 10 197589 0 00:00:39.70 2131 2940 M

$ SHOW SYSTEM/PROCESS=WBEMP*
21000478 WBEMPROV$HOST_P HIB 6 445 0 00:00:01.72 1254 1421 M

2. Are WBEM logicals defined?

$ SHOW LOGICAL WBEM*
(LNM$SYSTEM_TABLE)
"WBEM_BIN" = "wbem_opt:[wbem.bin]"
"WBEM_CIMXX_MOF_DIR" = "wbem_opt:[wbem.mof.CIM29]"
"WBEM_ETC" = "SYS$SYSDEVICE:[SYS0.syscommon.wbem_services.etc.]"
"WBEM_LIB" = "sys$library"
"WBEM_MOF_DIR" = "SYS$SYSDEVICE:[SYS0.syscommon.wbem_services.opt.wbem.mof.]"
"WBEM_OPT" = "SYS$SYSDEVICE:[SYS0.syscommon.wbem_services.opt.]"
"WBEM_REPOSITORY_DIR" = "wbem_var:[opt.wbem.repository]"
"WBEM_SBIN" = "wbem_opt:[wbem.sbin]"
"WBEM_TMP" = "SYS$SPECIFIC:[WBEM_Services.tmp]"
"WBEM_VAR" = "$2$DKC300:[SYS0.WBEM_Services.var.]"
"WBEM_VAR_DATA_DIR" = "wbem_var:[opt.wbem]"

HPE Insight Remote Support 7.10: Monitored Devices Configuration Guide Page 172 of 436
Chapter 16: Configuring HPE OpenVMS Integrity servers

3. Has the following command has been added to the system startup? Check files such as SYS$MANAGER:
SYSTARTUP_VMS.COM.
$ @SYS$STARTUP:WBEM_Services$Startup.com
4. Has the WBEM repository has been created on the system disk?
$ DIRECTORY SYS$SYSDEVICE:[*...]repository.dir
Directory SYS$SYSDEVICE:[SYS0.WBEM_Services.var.opt.wbem]
repository.DIR;1
Total of 1 file.

If any of the above checks answered Yes, then go to "Upgrade WBEM" on page 177.
If all of the above checks answered No, then go to "Install WBEMCIM and WBEMPROVIDERS for the first
time" below.

Install WBEMCIM and WBEMPROVIDERS for the first time

Install WBEM Services and WBEM Providers with a PRODUCT INSTALL command using the kits downloaded
above.
1. Install WBEM Services and WBEM Providers:
$ PRODUCT INSTALL WBEMCIM
$ PRODUCT INSTALL WBEMPROVIDERS
2. Install remedial fixes. Remedial fixes can be obtained by contacting the HPE Customer Support Center.
If your system is running HPE OpenVMS 8.3-1H1, WBEMCIM V3.0-2, and WBEMPROVIDERS V1.7-
21, make sure the following remedial images are installed:
l LIBGS.EXE* from QUIX from QUIX case QXCM1001334161
l LIBBASECONSOLIDATEDSTATUS.EXE* from QUIX case QXCM1001334161
l LIBLANINSTANCEPROVIDER.EXE* from QUIX case QXCM1001415878
l LIBHASCOMMON.EXE from QUIX case QXCM1001415124
If your system is running HPE OpenVMS 8.4, WBEMCIM V3.0-2, and WBEMPROVIDERS V2.2-3,
make sure the following remedial images are installed:
l LIBGS.EXE* from QUIX case QXCM1001334161
l LIBBASECONSOLIDATEDSTATUS.EXE* from QUIX case QXCM1001334161
l LIBLANINSTANCEPROVIDER.EXE* from QUIX case QXCM1001363255
l LIBLANINDPROVIDER.EXE from QUIX case QXCM1001232499
l WBEMPROVIDERS$UTILD.EXE from QUIX case QXCM1001127252
* This signifies that these are important remedial fixes that should be applied. Without them not only can
the WBEM Providers application function poorly, it can also severely impact overall system
performance. Some of these significant problems include system hangs which will require system
reboots to rectify, CIMSERVER process stuck in a MUTEX or WINS state which requires a system
reboot to clear, or frequent CIMSERVER.DMP files which fill up the system disk.
It is unnecessary to install these remedial fixes if WBEMCIM V3.0-3 and WBEMPROVIDERS V2..2-5
are installed since these remedial fixes are included in the SSL1 compatible versions.

HPE Insight Remote Support 7.10: Monitored Devices Configuration Guide Page 173 of 436
Chapter 16: Configuring HPE OpenVMS Integrity servers

3. Configure WBEM Services and create repository. The following command which invokes the utility that
configures and initializes the environment for WBEM Services for OpenVMS including the creation of the
WBEM repository. By default the WBEM repository will be created on the system disk in SYS$SPECIFIC:
[WBEM_Services.var.opt.wbem.repository]. If the system disk is an ODS-2 structured disk, then the
WBEM repository must be created on another disk which is an ODS-5 structured disk.
$ RUN SYS$SYSROOT:[WBEM_Services]WBEM_Services$Config.exe
When prompted to start the CIMserver, answer YES.
In an OpenVMS Cluster, each member that runs WBEM Services for OpenVMS needs its own WBEM
repository. Therefore, you must execute this image on each of those cluster members.
4. Execute the following command procedure that defines WBEM commands and also add this command
to the login.com of the SYSTEM account in the section where interactive commands are invoked:
$ @SYS$COMMON:[wbem_services]WBEM_Services$Define_Commands.com
5. Verify WBEM Services:
a. Check if the CIMSERVER and CIMDAEMON processes exist and are in the HIB state:
$ SHOW SYSTEM/PROCESS=CIM*
20719DB1 CIMSERVER HIB 10 72063 0 00:00:14.27 3171 2905 M
207199C6 CIMDAEMON HIB 10 6449 0 00:00:00.39 1784 260

b. Confirm system knows about the providers created by WBEM Services and that their status is OK.
$ cimprovider –ls
MODULE STATUS
OperatingSystemModule OK
ComputerSystemModule OK
ProcessModule OK
IPProviderModule OK
If the cimprovider command is unknown:
$ cimprovider
%DCL-W-IVVERB, unrecognized command verb - check validity and spelling

Execute the following command procedure and also add this command to the login.com of the
SYSTEM account in the section where interactive commands are invoked:
$ @SYS$COMMON:[wbem_services]WBEM_Services$Define_Commands.com
c. Verify that the WBEM Services CIMSERVER is responding to requests by using the OSINFO
command:
$ OSINFO
OperatingSystem Information
Host: i64svr
Name: OpenVMS
Version: V8.3-1H1
UserLicense: Unlimited user license

HPE Insight Remote Support 7.10: Monitored Devices Configuration Guide Page 174 of 436
Chapter 16: Configuring HPE OpenVMS Integrity servers

Number of Users: 2 users

Number of Processes: 28 processes
OSCapability: 64 bit
LastBootTime: Mar 20, 2009 0:41:21 (-0600)
LocalDateTime: Mar 21, 2009 13:58:57 (-0600)

If the OSINFO command does not work then the CIMSERVER process may be hung.
d. Confirm that the CIMSERVER process is using port 5989 by issuing the following commands:
$ TCPIP SHOW DEVICE/PORT=5989
Port Remote
Device_socket Type Local Remote Service Host
bg22708 STREAM 5989 0 *
$ SHOW DEVICE <bg_device_name>/FULL
For example:
$ SHOW DEVICE bg22708/FULL
Device BG22708: device type unknown, is online, mounted, record-oriented
device, network device, mailbox device.
Error count 0 Operations completed 58
Owner process "CIMSERVER" Owner UIC [SYSTEM]
Owner process ID 00007227 Dev Prot S:RWPL,O:RWPL,G:RWPL,W:RWPL
Reference count 1 Default buffer size 256

6. Execute the command procedure that configures WBEM Providers.

Note: If you are running V1.7-21 WBEM Providers (HPE OpenVMS 8.3-1H1 version) and do
not have a supported model, avoid performing this step.

$ @SYS$COMMON:[WBEMPROVIDERS]WBEMPROVIDERS$CONFIGURE.COM
Verify WBEM Providers:
a. Verify that the list of WBEM Providers displays the following and that the status of all providers is
OK:
$ cimprovider -ls
MODULE STATUS
EventIndicationConsumerModule OK
EMSWrapperProviderModule OK
HPVMSLANIndicationProviderModule OK
StateChangeIndicationProviderModule OK
ChassisProviderModule OK
cpuprovidermodule OK
MemoryModule OK
FirmwareRevisionProviderModule OK
MPProviderModule OK

HPE Insight Remote Support 7.10: Monitored Devices Configuration Guide Page 175 of 436
Chapter 16: Configuring HPE OpenVMS Integrity servers

EnclosureProviderModule OK
HPHealthStateProviderModule OK
HPVMSLANProviderModule OK
HPVMSLANCSProviderModule OK
CSChassisProviderModule OK
HPVMProviderModule OK
HP_UtilizationProviderModule OK
OperatingSystemModule OK
ComputerSystemModule OK
ProcessModule OK
IPProviderModule OK

b. Confirm that the OPENVMS_EMS and OPENVMS_UTILD processes exist:

$ SHOW SYSTEM/PROCESS=OPEN*
000069EE OPENVMS_UTILD HIB 6 7476021 0 00:09:34.24 437 446
000069EF OPENVMS_EMS HIB 6 22234 0 00:00:00.18 1150 1928 M

c. Confirm that the WBEMPROV$HOST_P process exists on models that support setting
HOSTINFOPARAMS on the ILO:
$ SHOW SYSTEM/PROCESS=WBEMPROV*
000069F0 WBEMPROV$HOST_P HIB 6 275 0 00:00:00.11 1055 1689 M

7. Create a nonprivileged account and a cimuser user whose username and password corresponds to the
SYSUAF account. This user account will be used by Insight RS when communicating with your
OpenVMS system using the WBEM protocol.
The following is an example of what the OpenVMS account should look like:
$ mcr authorize show wbem
Username: WBEM Owner: WBEM
Account: WBEM UIC: [10,266] ([WBEM])
CLI: DCL Tables: DCLTABLES
Default: SYS$SYSDEVICE:[WBEM]
LGICMD:
Flags:
Primary days: Mon Tue Wed Thu Fri
Secondary days: Sat Sun
No access restrictions
Expiration: (none) Pwdminimum: 8 Login Fails: 0
Pwdlifetime: (none) Pwdchange: 14-JAN-2010 16:40
Last Login: 23-NOV-2009 10:31 (interactive), 3-FEB-2010 14:07 (non-interactive)
Maxjobs: 0 Fillm: 128 Bytlm: 256000
Maxacctjobs: 0 Shrfillm: 0 Pbytlm: 0
Maxdetach: 0 BIOlm: 150 JTquota: 4096
Prclm: 10 DIOlm: 150 WSdef: 4096
Prio: 4 ASTlm: 300 WSquo: 8192
Queprio: 0 TQElm: 100 WSextent: 16384
CPU: (none) Enqlm: 4000 Pgflquo: 700000

HPE Insight Remote Support 7.10: Monitored Devices Configuration Guide Page 176 of 436
Chapter 16: Configuring HPE OpenVMS Integrity servers

Authorized Privileges:
NETMBX TMPMBX
Default Privileges:
NETMBX TMPMBX

Note: The above WBEM account was created with the following commands:
$ mcr authorize add wbem/uic=
[10,266]/flag=nodisuser/nopwdexpired/password=wbem
$ mcr authorize modify wbem/nopwdlifetime/device=sys$sysdevice/directory=
[wbem]

a. Create the cimuser user with the following command. HPE recommends specifying the username in
lowercase and surrounded by quotes.
$ cimuser -a -u "<username>" -w "<password>"
Example:
$ cimuser -a -u "wbem" -w "mypassword"
b. Confirm that the user was created by issuing the command:
$ cimuser -l
wbem
c. Confirm that you can log on to the OpenVMS account.
8. Add WBEM Services and WBEM Providers to system startup and system shutdown to ensure they start
up at system boot and shutdown during a planned system shutdown.
Add the following command to the system startup:
$ @SYS$STARTUP:WBEM_Services$Startup.com
Since it may take a few minutes to startup WBEM Services, in order to not delay your system boot,
consider creating a batch command procedure that includes this command and invoking the batch job
from SYS$MANAGER:SYSTARTUP_VMS.COM.
Add the following command to the system shutdown in SYS$STARTUP:SYSHUTDWN.COM:
$ @SYS$STARTUP:WBEM_Services$Shutdown.com

Upgrade WBEM
If you need to upgrade a previously configured environment, HPE recommends that you perform the following
steps to upgrade the software. Note that whenever WBEM Services or WBEM Providers is upgraded, the
modified product needs to be reconfigured.
1. Install WBEM Services and WBEM Providers:
l Issue the following commands if both products need to be upgraded:
$ @SYS$COMMON:[WBEMPROVIDERS]WBEMPROVIDERS$DECONFIGURE.COM
$ @SYS$STARTUP:WBEM_Services$Shutdown.com
$ PRODUCT INSTALL WBEMCIM
$ PRODUCT INSTALL WBEMPROVIDERS

HPE Insight Remote Support 7.10: Monitored Devices Configuration Guide Page 177 of 436
Chapter 16: Configuring HPE OpenVMS Integrity servers

Install remedial images shown below.

$ RUN SYS$SYSROOT:[WBEM_Services]WBEM_Services$Config.exe
Issue the following command if you have an appropriate operating system version and model for
Configuring WBEM Providers
$ @SYS$COMMON:[WBEMPROVIDERS]WBEMPROVIDERS$CONFIGURE.COM
l Issue the following commands if only WBEM Services needs to be upgraded:
$ @SYS$STARTUP:WBEM_Services$Shutdown.com
$ PRODUCT INSTALL WBEMCIM

Install remedial images shown below.

$ RUN SYS$SYSROOT:[WBEM_Services]WBEM_Services$Config.exe

l Issue the following commands if only WBEM Providers needs to be upgraded:

$ @SYS$COMMON:[WBEMPROVIDERS]WBEMPROVIDERS$DECONFIGURE.COM
$ @SYS$STARTUP:WBEM_Services$Shutdown.com
$ PRODUCT INSTALL WBEMPROVIDERS

Install remedial images shown below.

$ @SYS$STARTUP:WBEM_Services$Startup.com
Issue the following command if you have an appropriate operating system version and model for
Configuring WBEM Providers
$ @SYS$COMMON:[WBEMPROVIDERS]WBEMPROVIDERS$CONFIGURE.COM
l Install remedial fixes. Remedial fixes can be obtained by contacting the HPE Customer Support
Center.
If your system is running HPE OpenVMS 8.3-1H1, WBEMCIM V3.0-2, and WBEMPROVIDERS
V1.7-21, make sure the following remedial images are installed:
o LIBGS.EXE* from QUIX from QUIX case QXCM1001334161
o LIBBASECONSOLIDATEDSTATUS.EXE* from QUIX case QXCM1001334161
o LIBLANINSTANCEPROVIDER.EXE* from QUIX case QXCM1001415878
o LIBHASCOMMON.EXE from QUIX case QXCM1001415124
If your system is running HPE OpenVMS 8.4, WBEMCIM V3.0-2, and WBEMPROVIDERS V2.2-3,
make sure the following remedial images are installed:
o LIBGS.EXE* from QUIX case QXCM1001334161
o LIBBASECONSOLIDATEDSTATUS.EXE* from QUIX case QXCM1001334161
o LIBLANINSTANCEPROVIDER.EXE* from QUIX case QXCM1001363255
o LIBLANINDPROVIDER.EXE from QUIX case QXCM1001232499
o WBEMPROVIDERS$UTILD.EXE from QUIX case QXCM1001127252
* These are important remedial fixes that should be applied. Without them not only can the WBEM
Providers application function poorly, it can also severely impact overall system performance. Some
of these significant problems include system hangs which will require system reboots to rectify,

HPE Insight Remote Support 7.10: Monitored Devices Configuration Guide Page 178 of 436
Chapter 16: Configuring HPE OpenVMS Integrity servers

CIMSERVER process stuck in a MUTEX or WINS state which requires a system reboot to clear, or
frequent CIMSERVER.DMP files which fill up the system disk.
It is unnecessary to install these remedial fixes if WBEMCIM V3.0-3 and WBEMPROVIDERS V2..2-
5 are installed since these remedial fixes are included in the SSL1 compatible versions.
2. Verify WBEM Services:
a. Check if the CIMSERVER and CIMDAEMON processes exist and are in the HIB state:
$ SHOW SYSTEM/PROCESS=CIM*
20719DB1 CIMSERVER HIB 10 72063 0 00:00:14.27 3171 2905 M
207199C6 CIMDAEMON HIB 10 6449 0 00:00:00.39 1784 260

b. Confirm system knows about the providers created by WBEM Services and that their status is OK.
$ cimprovider –ls
MODULE STATUS
OperatingSystemModule OK
ComputerSystemModule OK
ProcessModule OK
IPProviderModule OK

If the cimprovider command is unknown:

$ cimprovider
%DCL-W-IVVERB, unrecognized command verb - check validity and spelling

Execute the following command procedure and also add this command to the login.com of the
SYSTEM account in the section where interactive commands are invoked:
$ @SYS$COMMON:[wbem_services]WBEM_Services$Define_Commands.com
c. Verify that the WBEM Services CIMSERVER is responding to requests by using the OSINFO
command:
$ OSINFO
OperatingSystem Information
Host: i64svr
Name: OpenVMS
Version: V8.3-1H1
UserLicense: Unlimited user license
Number of Users: 2 users
Number of Processes: 28 processes
OSCapability: 64 bit
LastBootTime: Mar 20, 2009 0:41:21 (-0600)
LocalDateTime: Mar 21, 2009 13:58:57 (-0600)

If the OSINFO command does not work then the CIMSERVER process may be hung.
d. Confirm that the CIMSERVER process is using port 5989 by issuing the following commands:
$ TCPIP SHOW DEVICE/PORT=5989
Port Remote

HPE Insight Remote Support 7.10: Monitored Devices Configuration Guide Page 179 of 436
Chapter 16: Configuring HPE OpenVMS Integrity servers

Device_socket Type Local Remote Service Host

bg22708 STREAM 5989 0 *
$ SHOW DEVICE <bg_device_name>/FULL
For example:
$ SHOW DEVICE bg22708/FULL
Device BG22708: device type unknown, is online, mounted, record-oriented
device, network device, mailbox device.
Error count 0 Operations completed 58
Owner process "CIMSERVER" Owner UIC [SYSTEM]
Owner process ID 00007227 Dev Prot S:RWPL,O:RWPL,G:RWPL,W:RWPL
Reference count 1 Default buffer size 256

3. Execute the command procedure that configures WBEM Providers.

Note: If you are running V1.7-21 WBEM Providers (HPE OpenVMS 8.3-1H1 version) and do
not have a supported model, avoid performing this step.

$ @SYS$COMMON:[WBEMPROVIDERS]WBEMPROVIDERS$CONFIGURE.COM
Verify WBEM Providers:
a. Verify that the list of WBEM Providers displays the following and that the status of all providers is
OK:
$ cimprovider -ls
MODULE STATUS
EventIndicationConsumerModule OK
EMSWrapperProviderModule OK
HPVMSLANIndicationProviderModule OK
StateChangeIndicationProviderModule OK
ChassisProviderModule OK
cpuprovidermodule OK
MemoryModule OK
FirmwareRevisionProviderModule OK
MPProviderModule OK
EnclosureProviderModule OK
HPHealthStateProviderModule OK
HPVMSLANProviderModule OK
HPVMSLANCSProviderModule OK
CSChassisProviderModule OK
HPVMProviderModule OK
HP_UtilizationProviderModule OK
OperatingSystemModule OK
ComputerSystemModule OK
ProcessModule OK
IPProviderModule OK

HPE Insight Remote Support 7.10: Monitored Devices Configuration Guide Page 180 of 436
Chapter 16: Configuring HPE OpenVMS Integrity servers

b. Confirm that the OPENVMS_EMS and OPENVMS_UTILD processes exist:

$ SHOW SYSTEM/PROCESS=OPEN*
000069EE OPENVMS_UTILD HIB 6 7476021 0 00:09:34.24 437 446
000069EF OPENVMS_EMS HIB 6 22234 0 00:00:00.18 1150 1928 M

c. Confirm that the WBEMPROV$HOST_P process exists on models that support setting
HOSTINFOPARAMS on the ILO:
$ SHOW SYSTEM/PROCESS=WBEMPROV*
000069F0 WBEMPROV$HOST_P HIB 6 275 0 00:00:00.11 1055 1689 M

4. Remove all cimuser accounts and add them back again. The cimuser command is used to define the
WBEM user credentials that will be used by Insight RS when communicating with your OpenVMS
system using the WBEM protocol.
The following example shows how to remove and add a user back in again.
a. Show the user:
$ cimuser -l
wbem
b. Remove the user:
$ cimuser –r –u "wbem"
User removed successfully.
c. Before adding the cimuser account, confirm that the account exists in the SYSUAF and that you can
log into the account. If the user is missing, create a nonprivileged account and a cimuser user whose
username and password corresponds to the SYSUAF account.
The following is an example of what the OpenVMS account should look like:
$ mcr authorize show wbem
Username: WBEM Owner: WBEM
Account: WBEM UIC: [10,266] ([WBEM])
CLI: DCL Tables: DCLTABLES
Default: SYS$SYSDEVICE:[WBEM]
LGICMD:
Flags:
Primary days: Mon Tue Wed Thu Fri
Secondary days: Sat Sun
No access restrictions
Expiration: (none) Pwdminimum: 8 Login Fails: 0
Pwdlifetime: (none) Pwdchange: 14-JAN-2010 16:40
Last Login: 23-NOV-2009 10:31 (interactive), 3-FEB-2010 14:07 (non-interactive)
Maxjobs: 0 Fillm: 128 Bytlm: 256000
Maxacctjobs: 0 Shrfillm: 0 Pbytlm: 0
Maxdetach: 0 BIOlm: 150 JTquota: 4096
Prclm: 10 DIOlm: 150 WSdef: 4096
Prio: 4 ASTlm: 300 WSquo: 8192

HPE Insight Remote Support 7.10: Monitored Devices Configuration Guide Page 181 of 436
Chapter 16: Configuring HPE OpenVMS Integrity servers

Queprio: 0 TQElm: 100 WSextent: 16384

CPU: (none) Enqlm: 4000 Pgflquo: 700000
Authorized Privileges:
NETMBX TMPMBX
Default Privileges:
NETMBX TMPMBX

Note: The above WBEM account was created with the following commands:
$ mcr authorize add wbem/uic=
[10,266]/flag=nodisuser/nopwdexpired/password=wbem
$ mcr authorize modify wbem/nopwdlifetime/device=sys$sysdevice/directory=
[wbem]

d. Create the cimuser user with the following command. HPE recommends specifying the username in
lowercase and surrounded by quotes.
$ cimuser -a -u "<username>" -w "<password>"
Example:
$ cimuser -a -u "wbem" -w "mypassword"
e. Confirm that the user was created by issuing the command:
$ cimuser -l
wbem
f. Confirm that you can log on to the OpenVMS account.
5. Verify WBEM Services and WBEM Providers are in the system startup and system shutdown to ensure
they start up at system boot and shutdown during a planned system shutdown. If they are not, add them.
Add the following command to the system startup:
$ @SYS$STARTUP:WBEM_Services$Startup.com
Since it may take a few minutes to startup WBEM Services, in order to not delay your system boot,
consider creating a batch command procedure that includes this command and invoking the batch job
from SYS$MANAGER:SYSTARTUP_VMS.COM.
Add the following command to the system shutdown in SYS$STARTUP:SYSHUTDWN.COM:
$ @SYS$STARTUP:WBEM_Services$Shutdown.com

Option 2: Enable and configure SNMP

Confirm TCP/IP IP address and name resolution is functioning
Before configuring SNMP, confirm that TCP/IP is correctly configured. Make sure that you are able to ping by
IP address, system name, and fully qualified name from the Hosting Device to the OpenVMS system and
from the OpenVMS system to the Hosting Device. If the address or name is not found, add it to the local host
file or to the DNS server.
If your OpenVMS system has both a DNS TCP/IP cluster alias name and node specific name that refer to the
same IP address, add the fully qualified name of the node specific name to the local host file of the Hosting
Device.

HPE Insight Remote Support 7.10: Monitored Devices Configuration Guide Page 182 of 436
Chapter 16: Configuring HPE OpenVMS Integrity servers

Determine if the SNMP service is enabled

You can determine if SNMP is enabled by issuing the command:
$ TCPIP SHOW SERVICE SNMP
l If you see the below output, this means the TCP/IP service is defined and enabled. Proceed to "Configure
read community string" below.
$ TCPIP SHOW SERVICE SNMP
Service Port Proto Process Address State
SNMP 161 UDP TCPIP$SNMP 0.0.0.0 Enabled

l If you see the below output, this means SNMP is not defined or configured. Proceed to "Enable SNMP"
below.
$ TCPIP SHOW SERVICE SNMP
%TCPIP-W-NORECORD, information not found
-RMS-E-RNF, record not found

Enable SNMP
When the SNMP service does not exist it can be enabled by invoking SYS$MANAGER:TCPIP$CONFIG.COM
$ @SYS$MANAGER:TCPIP$CONFIG.COM
Choose option 3 for server components, then choose option 18 for SNMP.
If TCPIP$CONFIG.COM displays that the SNMP service is already enabled, then use the configuration tool to
disable it and re-enable it. Sometimes the display can get out of sync with reality due to commands issued at
the TCPIP prompt instead of in the TCPIP$CONFIG utility.

Configure read community string

Once the SNMP service is enabled, a read community string needs to be configured which corresponds to a
read community string on the Hosting Device. To confirm what the read community string is expected by the
Hosting Device, check the security tab on the Window service named SNMP Service.
1. Issue the following command on the OpenVMS server to see what community strings are defined:
$ TCPIP SHOW CONFIGURATION SNMP/FULL
2. If the read community string is missing on the OpenVMS system, it can be added by issuing the
command:
$ TCPIP SET CONFIGURATION SNMP /COMMUNITY=”<name_of_community_string>”/type=read
This command will create the read community string with an address of 0.0.0.0 which means that any
devices in your network will have read access using this community string. If you want to restrict this to
just the Hosting Device then issue the following command:
$ TCPIP SET CONF SNMP /COMMUNITY=”<name_of_community_string>”/type=read/address=
(127.0.0.1, <ip_address_of_hosting_device>)
Note that it is important to include the loop back address on the community string since the local system
needs the ability to access to this community string for SNMP to function correctly.

HPE Insight Remote Support 7.10: Monitored Devices Configuration Guide Page 183 of 436
Chapter 16: Configuring HPE OpenVMS Integrity servers

Also note that the community string is case sensitive so it must exactly match what you see on the
Hosting Device.
3. Restart SNMP after making any configuration change:
$ @SYS$MANAGER:TCPIP$SNMP_SHUTDOWN.COM
$ @SYS$MANAGER:TCPIP$SNMP_STARTUP.COM

Configure dynamic processor resilience

Dynamic Processor Resilience, also known as CPU Indictment, is the ability for Insight RS to detect various
error conditions occurring in the processor, or on the processor bus/links, and remove the processor from
operation. On HPE Integrity servers running OpenVMS, this capability is implemented by a combination of
analysis within Insight RS and Kernel CPU indictment services provided by the OpenVMS operating system.
When a CPU is indicted, the kernel CPU indictment service will remove the processor from the active set.
Additionally Insight RS will log a service call. By removing the failing processor from the active set this
prohibits the processor from failing fatally at some future time. Automatically logging the service call allows
automatic proactive repair further aiding in prompt resolution of the problem.
To use Dynamic Processor Resilience, it needs to be configured on the OpenVMS server and also enabled in
the Insight RS Console.
To enable Dynamic Processor Resilience on the OpenVMS server, complete the following steps:
1. Edit the SYS$INDICTMENT_POLICY.COM command procedure and change their values from 0 to 1:
$ DEFINE/SYSTEM/EXECUTIVE_MODE/NOLOG SYS$INDICT_START 1
$ DEFINE/SYSTEM/EXECUTIVE_MODE/NOLOG SYS$INDICT_ALLOW_CPUS 1

This enables all CPUs to be eligible for Indictment except for CPU 0.

Note: CPU 0 cannot be removed. If you wish to not have some CPU’s eligible, refer to the
HPE OpenVMS documentation for Indictment Service to learn how to modify this procedure to
meet your needs.

2. Reboot the server for the changes to take effect.

When the Indictment Server is started, there will be an INDICT_SERVER process shown in the SHOW
SYS output:
$ show system/process=INDICT_SERVER
0000041C INDICT_SERVER HIB 8 6 0 00:00:00.00 79 95

To enable the Dynamic Processor Resilience Adapter in the Insight RS Console, complete the following
steps:
1. In the main menu, select Administrator Settings.
2. Click the Integration Adapters tab.

HPE Insight Remote Support 7.10: Monitored Devices Configuration Guide Page 184 of 436
Chapter 16: Configuring HPE OpenVMS Integrity servers

3. Click the Dynamic Processor Resilience Adapter for HPE Integrity servers heading to expand the
adapter pane.

4. Select the Enable Dynamic Processor Resilience Adapter for HPE Integrity servers check box.
5. Click Save Adapter Settings.
Insight Remote Support enables the Dynamic Processor Resilience Adapter. (Enabled) now appears next to
the Dynamic Processor Resilience Adapter to indicate it is enabled.

Configure firewall and port settings

Table 16.2 OpenVMS Integrity Connectivity - Firewall/Port Requirements
Protocol Ports Source Destination Function Optional

ICMP N/A Hosting Monitored Provides system reachability (ping) check during Required
Device Systems system discovery and before other operations.

TCP 5989 Hosting Monitored Secured WBEM CIMOM protocol over Required
Device Systems HTTPS/SOAP. This port is used to communicate
with WBEM end point nodes.

TCP 7905 Monitored Hosting Secure HTTP (HTTPS) port used by the listener Required
Systems Device running in the Director's Web Interface. The
monitored host connects to the Hosting Device on
this port (e.g. https://<hostname>:7905).

TCP 7920 Hosting Monitored The Insight RS ELMC (WCCProxy) process Required
Device Systems communicates with the Director on this port. This is
a proprietary protocol. Any connections that
exchange username and passwords use SSL. Not
all connections are SSL.

UDP 161 Hosting Onboard SNMP. This is the standard port used by SNMP Required
Device Administrator agents on monitored systems. The Hosting Device
sends requests to devices on this port.

UDP 162 Onboard Hosting SNMP Trap. This is the port used by Insight RS to Required
Administrator Device listen to SNMP traps.

Add protocol credentials and start discovery

To discover your monitored devices, complete the following sections:

HPE Insight Remote Support 7.10: Monitored Devices Configuration Guide Page 185 of 436
Chapter 16: Configuring HPE OpenVMS Integrity servers

Create a protocol credential in the Insight RS Console

Create a WBEM or SNMPv1 protocol credential to correspond to the protocol you configured on your system
in "Option 1: Install the HPE OpenVMS WBEM Services and WBEM Providers" on page 171 or "Option 2:
Enable and configure SNMP" on page 182.

Option 1: Create a WBEM protocol credential in Insight RS Console

To configure WBEM in the Insight RS Console, complete the following steps:
1. In a web browser, log on to the Insight RS Console.
2. In the main menu, select Discovery and click the Credentials tab.
3. From the Select and Configure Protocol drop-down list, select Web-Based Enterprise Management
(WBEM).
Note that if you have more than one OpenVMS server with the same WBEM credentials, you may prefer
to create a Named Credential and use it here.
4. Click New. The New Credential dialog box appears.
5. Type the Username and Password you have configured on your device.
Type the Username and Password that corresponds to the cimuser account defined on the OpenVMS
server. The Username and Password are case sensitive and must match the cimuser credentials defined
on the OpenVMS server.
6. Click Add.
Insight RS creates the protocol credential and it appears in the credentials table.

Option 2: Create an SNMPv1 protocol credential in the Insight RS

Console
If your device's SNMP community string is set to public and your community access mode is read only,
Insight RS automatically associates an SNMPv1 protocol with your device. If you use a different community
string or use a nonstandard port, you must create an SNMPv1 protocol credential in the Insight RS Console.
To configure SNMPv1 in the Insight RS Console, complete the following steps:
1. In a web browser, log on to the Insight RS Console.
2. In the main menu, select Discovery and click the Credentials tab.
3. From the Select and Configure Protocol drop-down list, select Simple Network Management Protocol
Version 1, V2C (SNMPv1, SNMPv2C).
4. Click New. The New Credential dialog box appears.
5. Type the Community String you have configured on your device.
6. Click Add.
Insight RS creates the protocol credential and it appears in the credentials table.

Discover the device in the Insight RS Console

To discover the device from the Insight RS Console, complete the following steps:

HPE Insight Remote Support 7.10: Monitored Devices Configuration Guide Page 186 of 436
Chapter 16: Configuring HPE OpenVMS Integrity servers

1. In a web browser, log on to the Insight RS Console.

2. In the main menu, select Discovery and click the Sources tab.
3. Expand the IP Addresses section and add the IP address for your device:
a. Click New.
b. Select the Single Address, Address Range, or Address List option.
c. Type the IP address(es) of the devices to be discovered.
d. Click Add.
4. Click Start Discovery.

Verify discovery and device status

To verify the device was discovered correctly, complete the following steps:
1. In a web browser, log on to the Insight RS Console.
2. In the main menu, select Devices and click the Device Summary tab.

3. Make sure the Status column contains a success icon ( ).

If there is no success icon, determine which column has the problem and consult the Online Help for
troubleshooting information.
4. Verify monitoring:
a. Click the Monitoring & Collections tab, and then click the status icon in the Monitoring column.
b. Verify that the Event Log Monitoring Collector (ELMC) protocol is listed with a status of SUCCESS. If
ELMC protocol is listed as FAILURE, see "ELMC protocol troubleshooting" on page 195 for
troubleshooting steps.

Configure SAN configuration collections

Configuring an HPE OpenVMS device for a SAN Configuration Collection is only necessary if your system is
covered by a SAN assessments contract. You can use either TELNET or SSH. To configure SAN
Collections, complete the following steps:
1. Determine if SSH or TELNET service is enabled on OpenVMS system:
l $ TCPIP SHOW SERVICE SSH
Service Port Proto Process Address State
SSH 22 TCP TCPIP$SSH 0.0.0.0 Enabled

l $ TCPIP SHOW SERVICE TELNET

Service Port Proto Process Address State
TELNET 23 TCP not defined 0.0.0.0 Enabled

2. Run SYS$MANAGER:TCPIP$CONFIG.COM to create an SSH or TELNET service:

l When the SSH service does not exist, enable it with the following:
$ @SYS$MANAGER:TCPIP$CONFIG.COM

HPE Insight Remote Support 7.10: Monitored Devices Configuration Guide Page 187 of 436
Chapter 16: Configuring HPE OpenVMS Integrity servers

l When the TELNET service does not exist, enable it with the following:
$ @SYS$MANAGER:TCPIP$CONFIG.COM
3. Make sure to grant the privileges CMKRNL, SYSLCK, NETMBX, and TMPMBX to the OpenVMS account used to
run SAN Collections. This account is also used in the SSH or TELNET named credential below. These
privileges are required because the SAN Collection issues two OpenVMS commands (ANALYZE/SYSTEM
and PRODUCT SHOW HISTORY) which require these additional privileges.
4. If using SSH, edit the OpenVMS SSH server configuration file. After enabling and starting the SSH
service, edit the OpenVMS SSH server configuration file TCPIP$SSH_DEVICE:
[TCPIP$SSH.SSH2]SSHD2_CONFIG. If the AllowedAuthentications parameter is defined, make sure the
AllowedAuthentications parameter includes password. Also make sure the DenyHosts parameter
does not include a reference to the Windows server.
5. In the Insight RS Console, define a SSH or TELNET Named Credential:
a. In the main menu of the Insight RS Console, select Company Information and click the Named
Credentials tab.
b. Click Add New Credential.
c. Enter a Credential Name similar to OpenVMS-ssh or OpenVMS-telnet.
d. From the Protocol drop-down list, select Secure Shell (SSH) or Telnet depending on which
protocol you are configuring.
e. Enter the Username and Password of a valid OpenVMS account. You can use the same username
and password that you used for the WBEM Named Credential. Note that the user credential can be
an unprivileged account.
f. Click Save.
6. Add the SSH or TELNET protocol to the Insight RS OpenVMS device:
a. In the main menu of the Insight RS Console, select Devices. In the Devices pane, search for the
OpenVMS server name.
b. Click the device name, then the Credentials tab.
c. In the Credentials Information pane, expand the SSH or TELNET protocol you want to add. If
necessary, select the Configure additional Protocols check box to view all available protocols.
d. To add SSH protocol, click on Secure Shell (SSH) → Named Credential. To add the TELNET
protocol click on Telnet → Named Credential. Select the Named Credential created earlier.
e. Click on the Device tab, then click Discover Device.
7. Configure San Configuration Collection Schedule:
a. In the main menu of the Insight RS Console, select Collection Services.
b. Click the Collection Schedules tab.
c. In the List of Collection Schedules pane, select the SAN Configuration Collection Schedule.
d. Assign devices in the assigned devices pane. The default view shows devices assigned to the
schedule. To show additional devices, click the Not Assigned to this Schedule or All Devices
options. To show devices in a specific device group, select a device group from the Filter by device
group drop-down list. To search for a specific device, type the device name into the Search box.
The table displays the devices based on your filter and search criteria.

HPE Insight Remote Support 7.10: Monitored Devices Configuration Guide Page 188 of 436
Chapter 16: Configuring HPE OpenVMS Integrity servers

Add your OpenVMS device to the SAN Configuration Collection Schedule by selecting the check
box next to the device in the devices table.
e. Click Save Devices.
f. Click Run Now.
8. Confirm the SAN Configuration Collection Schedule ran successfully; see "Verify collections in the
Insight RS Console" below.

Verify communication between monitored device

and Insight RS
To verify communication between your monitored device and Insight RS, complete the following section:

Verify service event monitoring

The OpenVMS Test event tool is installed when you install the latest version of ELMC. The package includes
two executable files and a readme file that explains how to create a test event. After extracting the ELMC
Package, the test event tool can be found in the following folder on the Hosting Device:
C:\ProgramData\HP\RS\DATA\SWM\LANDINGZONE\ELMC\unzipped\lib\ELMC-testlog-utility-OVMS.zip
The zip package contains two executables:
l testlog.exe_ia64 – This is an Itanium executable. The Itanium image is supported for HPE OpenVMS
8.2-1, 8.3, 8.3-1H1, and 8.4.
l testlog.exe_axp – This is an AlphaServer executable.
Copy the ELMC-testlog-utility-OVMS.zip software package to the OpenVMS monitored device, and
extract the contents using the OpenVMS unzip utility. A copy of the OpenVMS unzip utility can be
downloaded from the following web page: h41379.www4.hpe.com/openvms/freeware/freeware.html
Use the Itanium executable for HPE OpenVMS servers. This executable adds a test event to the file
SYS$ERRORLOG:ERRLOG.SYS. If this file does not exist wait until the ERRFMT process creates the file. This
typically can take around 15 minutes for a new error log to be created by the operating system.
To run the Itanium executable, run the following command:
$ run TESTLOG.EXE_IA64
%TESTLOG-I-ADD, Test Event added to SYS$ERRORLOG:ERRLOG.SYS

Verify collections in the Insight RS Console

Collections are not automatically run after discovery. HPE recommends that you manually run a collection
after discovery completes in order to verify connectivity. Run the collection schedule manually on the
Collection Services → Collection Schedules tab. If you do not want to run the collection for all devices in the
collection schedule, add a new schedule that only includes the devices for which you want to verify. For more
information about scheduling collections, see the Insight RS Help.
Configuring your OpenVMS server for Basic Configuration Collections is necessary if your system is covered
by a Proactive services contract. Basic Configuration Collections use the WBEM protocol and require that an
unpriviledged OpenVMS account is configured for the WBEM credentials.

HPE Insight Remote Support 7.10: Monitored Devices Configuration Guide Page 189 of 436
Chapter 16: Configuring HPE OpenVMS Integrity servers

Configuring your OpenVMS server for SAN Configuration Collections is necessary if your system is covered
by a SAN assessments contract. SAN Configuration Collections use the TELNET or SSH protocol and
require that an OpenVMS account with the privileges CMKRNL, SYSLCK, NETMBX, and TMPMBX are configured for
the TELNET or SSH credentials.
To verify the collection ran successfully, complete the following steps:
1. Log on to the Insight RS Console.
2. In the main menu, select Devices.
3. Click the Monitoring & Collections tab, and search for the device you want to view.
4. View the collection status in the appropriate column, depending on if you are using Basic Collections or
SAN Collections. If the collection was successful, a success icon appears ( ). If it failed, an error icon
appears ( ). If an error icon appears, troubleshoot the protocol used for the collection type:
l For Basic Collections, see "WBEM protocol troubleshooting" on the next page.
l For SAN Collections, see "Telnet protocol troubleshooting" on page 200 or "SSH protocol
troubleshooting" on page 197.
If the following error is seen when you click the error icon, it means that Insight RS is unable to detect
the SSH or TELNET protocols on your OpenVMS system.
Protocol: Secure Shell (SSH)
Service: SAN_Configuration_Collection
Type: DEPENDENCY_CHECK
Status: FAILURE
Description: A valid connection could not be made to: <openvms_server_fully_
qualified_name>
Detailed: Please check the credentials for this device. If these credentials are
from a credential group, determine if other devices can use the credentials
successfully. If this device uses certificates for authentication, regenerate the
certificate.
Created: Tuesday, June 09, 2015 12:35:09 PM
Last Updated: Tuesday, June 09, 2015 12:35:09 PM
CollectionView Collection

If you are using SAN Collections and the collection was successful, verify that the collection XML file
contains no DCL errors. If errors exist, the collection was unsuccessful in gathering all of the required data.

Note: This procedure only applies if you have enabled local storage of collections. For details, see
the Online Help.

1. In the Insight RS Console, on the Devices → Monitoring & Collections tab, click the icon.
2. In the collection description, click View Collection.
3. In the Attachments section, click Retrieve File.
4. Click Download File.
5. Open the file in your browser or an XML editor, and verify there are no DCL errors. If you see errors,
troubleshoot the protocol you are using. See "Telnet protocol troubleshooting" on page 200 or "SSH
protocol troubleshooting" on page 197.

HPE Insight Remote Support 7.10: Monitored Devices Configuration Guide Page 190 of 436
Chapter 16: Configuring HPE OpenVMS Integrity servers

Optional post-configuration steps

Disable WBEM protocol
Once an OpenVMS device is successfully discovered, the ongoing monitoring of the device no longer requires
the WBEM protocol. Ongoing monitoring uses the ELMC protocol rather than the WBEM protocol. As a result,
you can optionally disable the WBEM protocol on the OpenVMS system if there is concern over the
performance impact of running WBEM Services and WBEM Providers on an ongoing basis.

Important: This step is only appropriate under the following conditions:

l You do not have a Proactive services contract. Proactive services contracts require basic
collections, and WBEM is required for basic collections.
l Your OpenVMS system is not in a blade enclosure. Blade enclosures use WBEM providers to
properly identify devices within the enclosure.

If WBEM Services and WBEM Providers is disabled by issuing the command:

$ @SYS$STARTUP:WBEM_SERVICES$SHUTDOWN.COM
some additional customizations are required to the Insight RS configuration in order to avoid impacting the
successful status of the OpenVMS device. Whenever a discovery is performed, the OpenVMS device is
added to the Server Basic Configuration Collection. The Server Basic Configuration Collection task uses the
WBEM protocol to gather details about the OpenVMS device. The Server Basic Configuration Collection task
is then scheduled to run once a month. To avoid running a Basic collection:
1. Disable automatic device discovery. In the Insight RS Console main menu, click Discovery. On the
Configuration tab, clear the Automatically start discovery task every month on day <day> at time
<hh:mm check box. Click Save Configuration.
2. Remove the OpenVMS device from the Server Basic Configuration Collection. In the Insight RS Console
main menu, click Collection Services. On the Collection Schedules tab, select Server Basic
Configuration Collection Schedule. In the assigned devices pane, clear the check box next to the
OpenVMS device. Click Save Devices. Repeat this step any time a discovery is done for the OpenVMS
device.

Disable SNMP protocol

If your site does not permit SNMP to be left running due to security requirements, this service can be disabled
once Insight RS discovery completes. To disable SNMP, run the following commands:
$ TCPIP DISABLE SERVICE SNMP
$ @SYS$MANAGER: TCPIP$SNMP_SHUTDOWN.COM

Troubleshooting
WBEM protocol troubleshooting
Check the following items if you are having issues with discovery.

HPE Insight Remote Support 7.10: Monitored Devices Configuration Guide Page 191 of 436
Chapter 16: Configuring HPE OpenVMS Integrity servers

l Make sure TCPIP IPv6 is not enabled on the OpenVMS server. No process should be found when issuing
this command:
$ show system/process=TCPIP$ND6HOST
l Modify the password in the SYSUAF to the account referenced in the cimuser command so it corresponds to
the password used when issuing the cimuser -a command.
l Confirm that the account referenced by cimuser does not have a flag of disuser in the SYSUAF. Confirm
that you can log into the account.
l Delete the cimuser account on the OpenVMS system with a cimuser –r command and recreate the
cimuser account and password.
l Re-enter the WBEM credentials within the Insight RS Console, making sure that the case matches the
cimuser account and password.
l Confirm that the processes CIMSERVER and CIMDAEMON exist on the OpenVMS server and that they are in
the HIB state. If they are in any other state, contact the HPE Customer Support Center for troubleshooting
assistance.
l Issue the cimprovider –ls command to confirm that all providers listed on the OpenVMS server have a
status of “OK”. If any are in a failed state, stop and restart WBEM Services. If this does not solve the issue
deinstall and reinstall WBEM Services and WBEM Providers.
l Confirm that port 5989 used for the WBEM protocol is not blocked by the firewall.
l Look for CIMSERVER.DMP files on the system disk. They are typically located in SYS$SPECIFIC:[WBEM_
Services]. If you find any current dumps, contact the HPE Customer Support Center for assistance.
l Check to see if data from the WBEM repository can be accessed by issuing the WBEMEXEC command on the
OpenVMS server. Details on this command can be obtained from the article OpenVMS - HPE Insight
Remote Support, How to Locally Test The Namespace Classes Referenced During Discovery. If you see
errors, consider deinstalling and reinstalling WBEM Services and WBEM Providers.
l Restart the services “Pegasus WMI Mapper” and “Pegasus WMIMapper Indications Service” on the
Windows Hosting Device.
l If WBEM Providers is configured, confirm that the OPENVMS_EMS, OPENVMS_UTILD, and WBEMPROV$HOST
processes exist. If these processes are missing, check the following log files in SYS$SPECIFIC:
[WBEMPROVIDERS] for errors:
$ type WBEMPROVIDERS$OPENVMS_EMS.OUT
$ type WBEMPROV$HOST_P.OUT
$ type WBEMPROVIDERS$OPENVMS_UTILD.OUT
l If all other troubleshooting of the WBEM protocol fails to yield results, deinstall and reinstall WBEM
Services and WBEM Providers.
a. Display WBEM logicals to determine where the products are installed:
$ SHOW LOGICAL WBEM*
b. If WBEM Services and WBEM Providers are running, shut them down:
$ @SYS$STARTUP:WBEM_Services$Shutdown.com
c. Run PRODUCT REMOVE commands and continue if any errors occur:
$ PRODUCT REMOVE WBEMPROVIDERS

HPE Insight Remote Support 7.10: Monitored Devices Configuration Guide Page 192 of 436
Chapter 16: Configuring HPE OpenVMS Integrity servers

$ PRODUCT REMOVE WBEMCIM

d. Delete any WBEMPROVIDERS.DIR and WBEM_Services.DIR directories and any files left in
SYS$STARTUP. If the products were installed on the system disk, run the following commands:
$ DELETE/TREE SYS$COMMON:[WBEMPROVIDERS…]*.*;*
$ DELETE/TREE SYS$COMMON:[WBEM_Services…]*.*;*
$ DELETE SYS$COMMON:[000000]WBEMPROVIDERS.DIR;1
$ DELETE SYS$COMMON:[000000]WBEM_Services.DIR;1
$ DELETE/TREE SYS$SPECIFIC:[WBEMPROVIDERS…]*.*;*
$ DELETE/TREE SYS$SPECIFIC:[WBEM_Services…]*.*;*
$ DELETE SYS$SPECIFIC:[000000]WBEMPROVIDERS.DIR;1
$ DELETE SYS$SPECIFIC:[000000]WBEM_Services.DIR;1
$ DELETE SYS$STARTUP:WBEMPROVIDER*.*;*
$ DELETE SYS$STARTUP:WBEM_SERVICES*.*;*
$ DELETE SYS$STARTUP:WBEMPROVIDERS*.*;*

Note that the DELETE/TREE qualifier is only available on OpenVMS 8.4. On an OpenVMS 8.3-1H1
system you will need to reissue the DELETE commands multiple times until all subdirectories and files
are deleted.
e. Delete all WBEM Services and WBEM Providers logicals:
$ DEASSIGN/SYSTEM WBEM_BIN
$ DEASSIGN/SYSTEM WBEM_CIMXX_MOF_DIR
$ DEASSIGN/SYSTEM WBEM_ETC
$ DEASSIGN/SYSTEM WBEM_LIB
$ DEASSIGN/SYSTEM WBEM_MOF_DIR
$ DEASSIGN/SYSTEM WBEM_OPT
$ DEASSIGN/SYSTEM WBEM_REPOSITORY_DIR
$ DEASSIGN/SYSTEM WBEM_SBIN
$ DEASSIGN/SYSTEM WBEM_TMP
$ DEASSIGN/SYSTEM WBEM_VAR
$ DEASSIGN/SYSTEM WBEM_VAR_DATA_DIR
$ DEASSIGN/SYSTEM/EXEC WBEM_PRIMARY_OWNER
$ DEASSIGN/SYSTEM/EXEC WBEM_PRIMARY_OWNER_CONTACT

l If reinstalling WBEM Services and WBEM Providers does not resolve the issue, execute the following
command procedure and provide the saveset output to the HPE Customer Support Center: $
@SYS$COMMON:[WBEMPROVIDERS]WBEM$REPORTER.COM

SNMP protocol troubleshooting

l Confirm that SNMP ports 161 and 162 are not blocked by the firewall.
l If the SNMP protocol cannot be discovered, confirm that the addresses on the OpenVMS READ Community
string are correctly defined. The address should either be 0.0.0.0 or 127.0.0.1 (the IP address to the
Hosting Device). You can examine the SNMP configuration by issuing the following command: $ tcpip
show config snmp/full.

HPE Insight Remote Support 7.10: Monitored Devices Configuration Guide Page 193 of 436
Chapter 16: Configuring HPE OpenVMS Integrity servers

l Confirm that the Named Credential read community string specified in Insight RS is identical to the
community string defined on the OpenVMS server and in the SNMP Service Security tab on the Hosting
Device. Note that the community string is case sensitive.
l If the community string is correct, run the following command to confirm that the SNMP service is enabled
on the OpenVMS server:
$ tcpip show service snmp
Service Port Proto Process Address State
SNMP 161 UDP TCPIP$SNMP 0.0.0.0 Enabled

l If the service is disabled issue the command:

$ tcpip enable service SNMP
l If the SNMP service stays disabled there is a possibility that there is a logic error in
SYS$MANAGER:SYLOGIN.COM or SYS$SYSDEVICE:[TCPIP$SNMP]LOGIN.COM. Evidence that this is the root
cause can be found in SYS$SYSDEVICE:[TCPIP$SNMP]TCPIP$SNMP_RUN.LOG. The following is an example
of what the log file will look like when there are errors:
%DCL-W-IVOPER, unrecognized operator in expression - check spelling and syntax \.0.\
%DCL-W-UNDSYM, undefined symbol - check validity and spelling \AUTH\
%DCL-W-IVOPER, unrecognized operator in expression - check spelling and syntax \.0.\
TCPIP$SNMP job terminated at 8-AUG-2009 21:01:06.94

To eliminate this problem, add the following command to the beginning of SYLOGIN.COM:
$ if f$mode() .eqs. "NETWORK" then exit
l Stop and restart the OpenVMS SNMP service to make sure that the configuration displayed is actually in
effect:
$ @sys$startup:tcpip$snmp_shutdown.com
$ @sys$startup:tcpip$snmp_startup.com

l If the SNMP service will not start on the OpenVMS server, confirm that the TCPIP$SNMP account shows
that its UIC identifier in the SYSUAF is TCPIP$SNMP. Also confirm the account does not have the disuser
flag. The following is an example of a properly defined TCPIP$SNMP account:
$ mcr authorize show tcpip$snmp
Username: TCPIP$SNMP Owner: TCPIP$SNMP
Account: TCPIP UIC: [3655,21] ([TCPIP$AUX,TCPIP$SNMP])
CLI: DCL Tables: DCLTABLES
Default: SYS$SYSDEVICE:[TCPIP$SNMP]
LGICMD: LOGIN
Flags: Restricted
Primary days: Mon Tue Wed Thu Fri
Secondary days: Sat Sun
Primary 000000000011111111112222 Secondary 000000000011111111112222
Day Hours 012345678901234567890123 Day Hours 012345678901234567890123
Network: ##### Full access ###### ##### Full access ######
Batch: ----- No access ------ ----- No access ------
Local: ----- No access ------ ----- No access ------
Dialup: ----- No access ------ ----- No access ------

HPE Insight Remote Support 7.10: Monitored Devices Configuration Guide Page 194 of 436
Chapter 16: Configuring HPE OpenVMS Integrity servers

Remote: ----- No access ------ ----- No access ------

Expiration: (none) Pwdminimum: 6 Login Fails: 1
Pwdlifetime: 90 00:00 Pwdchange: (pre-expired)
Last Login: (none) (interactive), 17-APR-2015 13:58 (non-interactive)
Maxjobs: 0 Fillm: 100 Bytlm: 52200
Maxacctjobs: 0 Shrfillm: 0 Pbytlm: 0
Maxdetach: 0 BIOlm: 400 JTquota: 4096
Prclm: 8 DIOlm: 50 WSdef: 350
Prio: 8 ASTlm: 100 WSquo: 1024
Queprio: 4 TQElm: 50 WSextent: 4000
CPU: (none) Enqlm: 100 Pgflquo: 50000
Authorized Privileges:
NETMBX TMPMBX

l Confirm the directory and the files in the directory SYS$SYSDEVICE:[TCPIP$SNMP] are owned by the
TCPIP$SNMP account
$ directory/owner SYS$SYSDEVICE:[000000]TCPIP$SNMP.DIR
$ directory/owner SYS$SYSDEVICE:[TCPIP$SNMP…]*.*

If they are not then issue the following commands:

$ @sys$startup:tcpip$snmp_shutdown.com
$ set file/owner=tcpip$snmp SYS$SYSDEVICE:[000000]TCPIP$SNMP.DIR
$ set file/owner=tcpip$snmp SYS$SYSDEVICE:[TCPIP$SNMP…]*.*;*
$ @sys$startup:tcpip$snmp_startup.com

l Confirm that the Windows service named SNMP Service is running.

ELMC protocol troubleshooting

Check the following items if service events are not being received by Insight RS.
l Confirm that the ELMC protocol is working
If WCCPROXY is functioning properly or restarted, a green check mark appears in the OpenVMS device’s
Monitoring & Collections column. If the WCCPROXY process is stopped, a red X will appear in the
OpenVMS device’s Monitoring & Collections column. Insight RS takes about a minute to reflect changes in
status.
Click the Monitoring & Collections tab for more information about the status of the ELMC protocol. Click
the status icon to display a pop-up window with details about the protocol status.
If you see a red X in the Monitoring column, this means that the ELMC protocol is not functioning. The pop-
up window will display the following:
Monitoring Status Description: <openvms_server_fully_qualified_name>.
Protocol: Event Log Monitoring Collection (ELMC)
Service: ELMC Connection
Type: CONNECTIVITY
Status: FAILURE
Description: Failed to connect to EMClient Agent running on host <openvms_server_
fully_qualified_name>.

HPE Insight Remote Support 7.10: Monitored Devices Configuration Guide Page 195 of 436
Chapter 16: Configuring HPE OpenVMS Integrity servers

Detailed: Failed to connect to EMClient Agent running on host <openvms_server_fully_

qualified_name>.
Created: <some date/time>
Last Updated: <some date/time>

Note if the pop-up shows the SNMPv1 protocol, discovery detected the SNMP protocol. The SNMP
protocol cannot be used to monitor OpenVMS devices and this particular entry can be removed by clicking
Clear.
If Insight RS is not able to successfully connect to the OpenVMS system using the ELMC protocol,
continue with the troubleshooting steps below.
l If the ELMC protocol was not discovered, confirm the product WCCPROXY v6.4 is installed on your
OpenVMS system by issuing the following command:
$ product show product wccproxy
If you need to upgrade, the installation media can be found in:
<partition_where_InsightRS_is installed>:\ProgramData\HP\RS\DATA\ELMC
If you do not see the media in this folder, in the Insight RS Console browse to Administrator Settings >
Software Update tab. Click on Event Log Monitoring Collector (ELMC) package. Then on the
Available Version tab, click Install. Copy the media to your OpenVMS server in binary mode and then
issue the following commands when logged into the SYSTEM account:
$ run ELMCV64BL1KIT1_21-JUN-2012_OVMSI64.EXE
$ @wccproxy_install uninstall
$ @wccproxy_install install
l Confirm that the WCCPROXY process is running on the OpenVMS server by issuing the following command
when logged into the SYSTEM account.
$ wccproxy status
If it does not show the WCCProxy is running, issue the command:
$ wccproxy start
l Try restarting the WCCPROXY process on the OpenVMS server by issuing the commands while logged into
the SYSTEM account:
$ wccproxy stop
$ wccproxy start

l Rename SYS$ERRLOG:ERRLOG.SYS. The operating system should recreate one in approximately 15

minutes.
If a new ERRLOG.SYS file is not created confirm that the ERRFMT process exists. If it does not exist it can be
started with the command:
$ @sys$system:startup.com errfmt
l Confirm that port 7920 used by the ELMC protocol is not blocked by the firewall.
l Issue the following command to check if your Insight RS server is communicating with the ELMC process
by examining port 7920. If it is working correctly you should see your Hosting Device mentioned in the
“Remote Host” column as shown in the following example:
$ tcpip show device/port=7920

HPE Insight Remote Support 7.10: Monitored Devices Configuration Guide Page 196 of 436
Chapter 16: Configuring HPE OpenVMS Integrity servers

Port Remote
Device_socket Type Local Remote Service Host
bg285 STREAM 7920 0 *
bg42927 STREAM 7920 59958 1.2.3.4
l Send a test event and examine the Insight RS log file KCT.###.log for evidence on why the events may be
rejected. This is found in:
<partition_where _InsightRS_is_installed>\ProgramData\HP\RS\LOG
In the case that the OpenVMS errlog.sys is corrupt, rename the errlog.sys file and let the operating
system create a new one. Also confirm that the hardware is supported by Insight RS by referring to the
HPE Insight Remote Support Release Notes at www.hpe.com/info/insightremotesupport/docs.
l If no test event is received, examine the time zone of the OpenVMS system, the Hosting Device, and the
time zone defined in Insight RS to see if there is a discrepancy. The time zone within Insight RS can be
determined by browsing to Company Information > Sites > <site_name>.
The time zone of OpenVMS can be determine by issuing the following command:
$ show logical *time*
The time on the OpenVMS system can be determined by issuing the command:
$ show time
l Check that none of the command procedures in WCCPROXY_SPECIFIC:[SPECIFIC.WCCPROXY.DATA] have a
version limit of 32767. If they do, stop WCCPROXY by determining the pid of the WCCPROXY and
issuing STOP/ID=<pid #>. Then delete the files in this directory, and restart WCCPROXY by issuing a
WCCPROXY START command.
l If you continue to have problems with the ELMC protocol, check the log files in WCCPROXY_SPECIFIC:
[SPECIFIC.WCCPROXY.LOGS] for issues.
l If none of the troubleshooting steps shown above have solved the issue, deinstall and reinstall ELMC
(WCCPROXY) on the OpenVMS server:
$ run ELMCV64BL1KIT1_21-JUN-2012_OVMSI64.EXE
$ @wccproxy_install uninstall
$ @wccproxy_install install

l If test events are not working for any OpenVMS system, confirm that ELMC was installed on the Insight
RS server. WCCPROXY 6.4 software should appear in the Control Panel → All Control Panel Items →
Programs and Features. If WCCPROXY is missing, log into the Insight RS Console and navigate to
Administrator Settings → Software Updates. Click on Event Log Monitoring Collector (ELMC), and
on the Available Version tab, click Install. Once the WCCPROXY software is installed, make sure that
the WCCPROXY service is started.
l If test events are not working for any OpenVMS system, determine if Insight Remote Support Advanced
(RSA) A.05.80 or below is installed on the same server running Insight RS 7.x. If Insight RSA A.05.08 or
below appears in Control Panel → All Control Panel Items → Programs and Features, this software
should be removed.

SSH protocol troubleshooting

Check the following items if you are having issues with SAN collections.

HPE Insight Remote Support 7.10: Monitored Devices Configuration Guide Page 197 of 436
Chapter 16: Configuring HPE OpenVMS Integrity servers

l Examine the SSH service on the OpenVMS server with the tcpip show service ssh/full command.
Confirm that the number of Active sessions does not exceed the Limit. Also confirm what port is being
used by the SSH service and that the service is enabled.
l Confirm that the TCPIP$SSH account shows that its UIC identifier in the SYSUAF is TCPIP$SSH and the
account does not have the disuser flag. The following is an example of a properly defined TCPIP$SSH
account:
$ mcr authorize show tcpip$ssh
Username: TCPIP$SSH Owner: TCPIP$SSH
Account: TCPIP UIC: [3655,15] ([TCPIP$AUX,TCPIP$SSH])
CLI: DCL Tables: DCLTABLES
Default: TCPIP$SSH_DEVICE:[TCPIP$SSH]
LGICMD: LOGIN
Flags: Restricted
Primary days: Mon Tue Wed Thu Fri
Secondary days: Sat Sun
Primary 000000000011111111112222 Secondary 000000000011111111112222
Day Hours 012345678901234567890123 Day Hours 012345678901234567890123
Network: ##### Full access ###### ##### Full access ######
Batch: ----- No access ------ ----- No access ------
Local: ----- No access ------ ----- No access ------
Dialup: ----- No access ------ ----- No access ------
Remote: ----- No access ------ ----- No access ------
Expiration: (none) Pwdminimum: 6 Login Fails: 0
Pwdlifetime: 90 00:00 Pwdchange: (pre-expired)
Last Login: (none) (interactive), 16-AUG-2016 19:25 (non-interactive)
Maxjobs: 0 Fillm: 100 Bytlm: 15000
Maxacctjobs: 0 Shrfillm: 0 Pbytlm: 0
Maxdetach: 0 BIOlm: 400 JTquota: 4096
Prclm: 8 DIOlm: 1000 WSdef: 350
Prio: 8 ASTlm: 100 WSquo: 1024
Queprio: 4 TQElm: 50 WSextent: 4000
CPU: (none) Enqlm: 100 Pgflquo: 50000
Authorized Privileges:
NETMBX TMPMBX
Default Privileges:
NETMBX TMPMBX

l Confirm the directory and the files in the directory SYS$SYSDEVICE:[TCPIP$SSH] are owned by the
TCPIP$SSH account.
$ directory/owner SYS$SYSDEVICE:[000000]TCPIP$SSH.DIR
$ directory/owner SYS$SYSDEVICE:[TCPIP$SSH…]*.*

If they are not, then issue the following commands:

$ @sys$startup:tcpip$ssh_shutdown.com
$ @sys$startup:tcpip$ssh_client_shutdown.com
$ set file/owner=tcpip$ssh SYS$SYSDEVICE:[000000]TCPIP$SSH.DIR
$ set file/owner=tcpip$ssh SYS$SYSDEVICE:[TCPIP$SSH…]*.*;*

HPE Insight Remote Support 7.10: Monitored Devices Configuration Guide Page 198 of 436
Chapter 16: Configuring HPE OpenVMS Integrity servers

$ @sys$startup:tcpip$ssh_startup.com
$ @sys$startup:tcpip$ssh_client_startup.com

l Confirm that port 22 used by the SSH protocol is not blocked by the firewall.
l Install a SSH client on the Windows Hosting Device. Test if you can log in to OpenVMS system using the
SSH client on the Windows Hosting Device. Use the same credentials as defined in the SSH Named
Credential.
l If port 22 is not blocked by the firewall but you cannot log into the OpenVMS system using the SSH client
on your Windows server, test if you can SSH from the OpenVMS system to itself.
$ SSH localhost
l Check if any other system has SSH access to the OpenVMS server.
l Confirm that the account you are trying to log into does not have the DISUSER flag set and that the
password is not expired. Also make sure that Pwdlifetime field is set to (none).
l Examine the OpenVMS SSH server configuration file TCPIP$SSH_DEVICE:[TCPIP$SSH.SSH2]SSH2_
CONFIG. Make sure the AllowedAuthentications parameter includes password. Make sure the
DenyHosts parameter does not include a reference to the Windows server. Make sure there are not any
other configuration errors. For more information about the parameters in this file reference the knowledge
base article OpenVMS - TCPIP SSH: What Are the Parameters in SSH2_CONFIG and Their Default
Values?
l Examine the TCPIP$SSH_DEVICE:TCPIP$SSH_RUN.LOG for clues as to why SSH is not working.
l To enable debug on the OpenVMS SSH server define the following logical:
$ DEFINE/SYSTEM TCPIP$SSH_SERVER_PARAMS "-i -d 5"
After troubleshooting is completed, deassign the logical with the command:
$ DEASSIGN/SYSTEM TCPIP$SSH_SERVER_PARAMS
l If the TCPIP$SSH_RUN.LOG does not exist, reference the knowledge base article OpenVMS - HP TCPIP
SSH, TCPIP$SSH_DEVICE:TCPIP$SSH_RUN.LOG is Missing.
l Confirm the OpenVMS account used for the SAN Collection SSH credentials also has the privileges of
CMKRNL, NETMBX, SYSLCK, and TMPMBX. The following is an example of a properly configured account:
$ mcr authorize show wbem
Username: WBEM Owner: WBEM
Account: WBEM UIC: [10,266] ([WBEM])
CLI: DCL Tables: DCLTABLES
Default: SYS$SYSDEVICE:[WBEM]
LGICMD:
Flags:
Primary days: Mon Tue Wed Thu Fri
Secondary days: Sat Sun
No access restrictions
Expiration: (none) Pwdminimum: 6 Login Fails: 0
Pwdlifetime: (none) Pwdchange: 26-JAN-2017 17:33
Last Login: 30-JAN-2017 21:45 (interactive), 1-FEB-2017 16:07 (non-interactive)
Maxjobs: 0 Fillm: 100 Bytlm: 64000
Maxacctjobs: 0 Shrfillm: 0 Pbytlm: 0

HPE Insight Remote Support 7.10: Monitored Devices Configuration Guide Page 199 of 436
Chapter 16: Configuring HPE OpenVMS Integrity servers

Maxdetach: 0 BIOlm: 150 JTquota: 4096

Prclm: 8 DIOlm: 150 WSdef: 2000
Prio: 4 ASTlm: 250 WSquo: 4000
Queprio: 4 TQElm: 10 WSextent: 16384
CPU: (none) Enqlm: 2000 Pgflquo: 50000
Authorized Privileges:
CMKRNL NETMBX SYSLCK TMPMBX
Default Privileges:
CMKRNL NETMBX SYSLCK TMPMBX

The following command shows the syntax for granting the required privileges to an OpenVMS account.
$ MCR AUTHORIZE MODIFY <username>/DEFPRIVILEGES=(NETMBX,TMPMBX,CMKRNL,SYSLCK) -
/PRIVILEGES=(NETMBX,TMPMBX,CMKRNL,SYSLCK)

l If the XML file created by the SAN Collection shows DCL errors similar to the following, the OpenVMS
account used for the credentials is missing the CMKRNL privilege:
%DCL-W-IVVERB, unrecognized command verb - check validity and spelling
\FC\
## FIBRE CARD INFO FINISHED ##
## Starting SCSI INFORMATION ##
%TYPE-W-SEARCHFAIL, error searching for SYS$SYSDEVICE:[WBEM]CLUE_SCSI.TXT;
-RMS-E-DNF, directory not found
-SYSTEM-W-NOSUCHFILE, no such file
%DELETE-W-SEARCHFAIL, error searching for SYS$SYSDEVICE:[WBEM]CLUE_SCSI.TXT;*
-RMS-E-DNF, directory not found
-SYSTEM-W-NOSUCHFILE, no such file
## Finishing SCSI INFORMATION ##
## Starting HARDWARE INFORMATION ##
%TYPE-W-SEARCHFAIL, error searching for SYS$SYSDEVICE:[WBEM]CLUE_CONFIG.TXT;
-RMS-E-DNF, directory not found
-SYSTEM-W-NOSUCHFILE, no such file
%DELETE-W-SEARCHFAIL, error searching for SYS$SYSDEVICE:[WBEM]CLUE_CONFIG.TXT;*
-RMS-E-DNF, directory not found
-SYSTEM-W-NOSUCHFILE, no such file

l If the XML file created by the SAN Collection shows DCL errors similar to the following, the OpenVMS
account used for the credentials is missing the SYSLCK privilege:
Excerpt xml file:
====== PCSI ======
%PCSIUI-E-PRIVCLASS1, operation requires SYSLCK privilege
%PCSIUI-E-ABORT, operation terminated due to an unrecoverable error condition

Telnet protocol troubleshooting

Check the following items if you are having issues with SAN collections.
l Examine the Telnet service on the OpenVMS server with the command tcpip show service
telnet/full. Confirm that the number of Active sessions does not exceed the Limit. Also confirm that
what port is being used by the Telnet service and that the service is enabled.
l Confirm that the TCPIP$TELNET account shows that its UIC identifier in the SYSUAF is TCPIP$TELNET and

HPE Insight Remote Support 7.10: Monitored Devices Configuration Guide Page 200 of 436
Chapter 16: Configuring HPE OpenVMS Integrity servers

the account does not have the disuser flag. The following is an example of a properly defined
TCPIP$TELNET account:
$ mcr authorize show tcpip$telnet
Username: TCPIP$TELNET Owner: TCPIP$TELNET
Account: TCPIP UIC: [3655,2] ([TCPIP$AUX,TCPIP$TELNET])
CLI: DCL Tables: DCLTABLES
Default: SYS$SYSDEVICE:[TCPIP$TELNET]
LGICMD: LOGIN
Flags: Restricted
Primary days: Mon Tue Wed Thu Fri
Secondary days: Sat Sun
Primary 000000000011111111112222 Secondary 000000000011111111112222
Day Hours 012345678901234567890123 Day Hours 012345678901234567890123
Network: ##### Full access ###### ##### Full access ######
Batch: ----- No access ------ ----- No access ------
Local: ----- No access ------ ----- No access ------
Dialup: ----- No access ------ ----- No access ------
Remote: ----- No access ------ ----- No access ------
Expiration: (none) Pwdminimum: 6 Login Fails: 0
Pwdlifetime: 90 00:00 Pwdchange: (pre-expired)
Last Login: (none) (interactive), (none) (non-interactive)
Maxjobs: 0 Fillm: 1024 Bytlm: 400000
Maxacctjobs: 0 Shrfillm: 0 Pbytlm: 0
Maxdetach: 0 BIOlm: 400 JTquota: 4096
Prclm: 8 DIOlm: 1000 WSdef: 350
Prio: 8 ASTlm: 2448 WSquo: 20000
Queprio: 4 TQElm: 20 WSextent: 20000
CPU: (none) Enqlm: 3000 Pgflquo: 20000
Authorized Privileges:
NETMBX TMPMBX
Default Privileges:
NETMBX TMPMBX

l Confirm the directory and the files in the directory SYS$SYSDEVICE:[TCPIP$TELNET] are owned by the
TCPIP$TELNET account.
$ directory/owner SYS$SYSDEVICE:[000000]TCPIP$TELNET.DIR
$ directory/owner SYS$SYSDEVICE:[TCPIP$TELNET…]*.*

If they are not then issue the following commands:

$ @sys$startup:tcpip$telnet_shutdown.com
$ set file/owner=tcpip$telnet SYS$SYSDEVICE:[000000]TCPIP$TELNET.DIR
$ set file/owner=tcpip$telnet SYS$SYSDEVICE:[TCPIP$TELNET…]*.*;*
$ @sys$startup:tcpip$telnet_startup.com

l Confirm that port 23 used by the telnet protocol is not blocked by the firewall.
l Enable the telnet client on the Insight RS Hosting Device. Open up a command prompt on the Windows
Hosting Device, enter telnet <ip_address_OpenVMS_system> and test if you can log into the OpenVMS
system. Use the same credentials as defined in the Telnet Named Credential.

HPE Insight Remote Support 7.10: Monitored Devices Configuration Guide Page 201 of 436
Chapter 16: Configuring HPE OpenVMS Integrity servers

l If port 23 is not blocked by the firewall but you cannot log into the OpenVMS system from the Hosting
Device, test if you can telnet from the OpenVMS system to itself: $ telnet localhost
l Check if any other system has telnet access to the OpenVMS server.
l Confirm that the account you are trying to log into does not have the DISUSER flag set and that the
password is not expired. Also make sure that Pwdlifetime field is set to (none).
l Confirm the OpenVMS account used for the SAN Collection TELNET credentials also has the privileges of
CMKRNL, NETMBX, SYSLCK, and TMPMBX. The following is an example of a properly configured account:
$ mcr authorize show wbem
Username: WBEM Owner: WBEM
Account: WBEM UIC: [10,266] ([WBEM])
CLI: DCL Tables: DCLTABLES
Default: SYS$SYSDEVICE:[WBEM]
LGICMD:
Flags:
Primary days: Mon Tue Wed Thu Fri
Secondary days: Sat Sun
No access restrictions
Expiration: (none) Pwdminimum: 6 Login Fails: 0
Pwdlifetime: (none) Pwdchange: 26-JAN-2017 17:33
Last Login: 30-JAN-2017 21:45 (interactive), 1-FEB-2017 16:07 (non-interactive)
Maxjobs: 0 Fillm: 100 Bytlm: 64000
Maxacctjobs: 0 Shrfillm: 0 Pbytlm: 0
Maxdetach: 0 BIOlm: 150 JTquota: 4096
Prclm: 8 DIOlm: 150 WSdef: 2000
Prio: 4 ASTlm: 250 WSquo: 4000
Queprio: 4 TQElm: 10 WSextent: 16384
CPU: (none) Enqlm: 2000 Pgflquo: 50000
Authorized Privileges:
CMKRNL NETMBX SYSLCK TMPMBX
Default Privileges:
CMKRNL NETMBX SYSLCK TMPMBX

The following command shows the syntax for granting the required privileges to an OpenVMS account.
$ MCR AUTHORIZE MODIFY <username>/DEFPRIVILEGES=(NETMBX,TMPMBX,CMKRNL,SYSLCK) -
/PRIVILEGES=(NETMBX,TMPMBX,CMKRNL,SYSLCK)

l If the XML file created by the SAN Collection shows DCL errors similar to the following, the OpenVMS
account used for the credentials is missing the CMKRNL privilege:
%DCL-W-IVVERB, unrecognized command verb - check validity and spelling
\FC\
## FIBRE CARD INFO FINISHED ##
## Starting SCSI INFORMATION ##
%TYPE-W-SEARCHFAIL, error searching for SYS$SYSDEVICE:[WBEM]CLUE_SCSI.TXT;
-RMS-E-DNF, directory not found
-SYSTEM-W-NOSUCHFILE, no such file
%DELETE-W-SEARCHFAIL, error searching for SYS$SYSDEVICE:[WBEM]CLUE_SCSI.TXT;*
-RMS-E-DNF, directory not found

HPE Insight Remote Support 7.10: Monitored Devices Configuration Guide Page 202 of 436
Chapter 16: Configuring HPE OpenVMS Integrity servers

-SYSTEM-W-NOSUCHFILE, no such file

## Finishing SCSI INFORMATION ##
## Starting HARDWARE INFORMATION ##
%TYPE-W-SEARCHFAIL, error searching for SYS$SYSDEVICE:[WBEM]CLUE_CONFIG.TXT;
-RMS-E-DNF, directory not found
-SYSTEM-W-NOSUCHFILE, no such file
%DELETE-W-SEARCHFAIL, error searching for SYS$SYSDEVICE:[WBEM]CLUE_CONFIG.TXT;*
-RMS-E-DNF, directory not found
-SYSTEM-W-NOSUCHFILE, no such file

l If the XML file created by the SAN Collection shows DCL errors similar to the following, the OpenVMS
account used for the credentials is missing the SYSLCK privilege:
Excerpt xml file:
====== PCSI ======
%PCSIUI-E-PRIVCLASS1, operation requires SYSLCK privilege
%PCSIUI-E-ABORT, operation terminated due to an unrecoverable error condition

Entitlement troubleshooting
Check the following items if you are having entitlement issues with your OpenVMS system.
l If the OpenVMS system does not pass the entitlement check, make sure you have the correct serial
number and product number specified on the contract.
l If the correct serial number and product number have been defined for the device and the entitlement check
continues to fail, confirm that the “Hosting Device Health” has a green check. This can be found in the
header of the Insight RS Console. If it shows a red x, click on “Hosting Device Health” for more details.
l Try stopping the following Window services in this order: 1) “HPE Insight Remote Support” and 2) “HPE
Insight RS Event Receiver” and then restarting them in that order.
l Confirm that port 443 used to communicate with the HPE backend is not blocked by the firewall.
Additional security firewall requirements are detailed in the HPE Insight Remote Support Security White
Paper at www.hpe.com/info/insightremotesupport/docs.
l Open up a browser on the Hosting Device and confirm if you can access this web page:
https://api.support.hpe.com/v1/version/index.html
l Issue a nslookup command and confirm that api.support.hpe.com can be resolved.
If api.support.hpe.com cannot be resolved by your DNS server, then add this address to the Windows
host file on the Hosting Device.
l Lack of connectivity to the HPE backend can sometimes be caused by issues with the HPE backend. For
additional assistance troubleshooting the lack of connectivity, contact the HPE Customer Support.

HPE Insight Remote Support 7.10: Monitored Devices Configuration Guide Page 203 of 436
 Chapter 17: Configuring VSI OpenVMS
Integrity servers
Fulfill configuration requirements
To configure your VSI OpenVMS servers to be monitored by Insight RS, complete the following sections:
Table 17.1 VSI OpenVMS server configuration steps
Task Complete?

Make sure Insight RS supports your Integrity OpenVMS server by checking the HPE Insight
Remote Support Release Notes.

Install and configure ELMC for VSI OpenVMS on the OpenVMS server.

Install the VSI OpenVMS WBEM Services and WBEM Providers.

(Optional) Configure Dynamic Processor Resilience.

Add the WBEM protocol to the Insight RS Console.

Discover the OpenVMS server in the Insight RS Console.

Send a test event to verify connectivity between your OpenVMS server and Insight RS.

Manually run collections to verify they are gathered.

Install and configure communication software on

servers
To configure your monitored devices, complete the following sections:

Fulfill ELMC system requirements

VSI OpenVMS monitored devices must meet the following requirements before ELMC is installed. In clusters,
minimum requirements apply to each node in the cluster.

Fulfilling hardware and software requirements

l Hardware support: Integrity 2800 i4/i6 servers and BL8x0C i4/i6 server blades
l Processor architecture: Integrity (Itanium) server
l Operating system: VSI OpenVMS 8.4-1H1 or higher

Note: Some supported VSI OpenVMS platforms require a minimum version of 8.4-1H1. See
www.vmssoftware.com/updates.html.

l Minimum 20,000 blocks free disk space.

l Connectivity: TCP/IP must be installed and running.

HPE Insight Remote Support 7.10: Monitored Devices Configuration Guide Page 204 of 436
Chapter 17: Configuring VSI OpenVMS Integrity servers

The ability to resolve the local host name into an IP address must be enabled. Otherwise, the Director
cannot handle ELMC message traffic correctly and fails to start.
ELMC officially supports two TCP/IP products for VSI OpenVMS:
l TCP/IP Services for VSI OpenVMS, version V5.7-13ECO5B or higher
l VSI TCP/IP Version 10.5 (requires VSI OpenVMS 8.4-2L1 or higher)

Note: Other TCP/IP products may work as is, so the Insight RS installation always completes
regardless of what, if any, TCP/IP product is installed.

l LOCALHOST entry: For ELMC to operate correctly, the LOCALHOST entry must be defined in the
OpenVMS TCP/IP HOSTS database. It is defined correctly by default, but it can be removed, which
causes Insight RS to fail.
Type the following command:
$ TCPIP SHOW HOST /LOCAL
Look for LOCALHOST, which should have an IP address of 127.0.0.1. If LOCALHOST does not appear in
the list, type the following command:
$ TCPIP SET HOST LOCALHOST /ADDRESS=127.0.0.1 /ALIAS=LOCALHOST
Type a ping command to verify that LOCALHOST was added:
l For TCP/IP Services for VSI OpenVMS: $ TCPIP PING LOCALHOST
l For VSI TCP/IP Version 10.5: $ IP PING LOCALHOST
PING LOCALHOST (127.0.0.1): 56 data bytes
64 bytes from 127.0.0.1: icmp_seq=0 ttl=64 time=0 ms
64 bytes from 127.0.0.1: icmp_seq=1 ttl=64 time=0 ms
64 bytes from 127.0.0.1: icmp_seq=1 ttl=64 time=0 ms

After verifying that LOCALHOST responds to the ping command, you can use Ctrl-C or Ctrl-Y to stop pinging.
l System firmware: In general, users should take advantage of the latest improvements by obtaining the
most recent firmware version available for their platforms.
Fulfilling required permissions and access

Grant permissions required to install ELMC

To install or uninstall ELMC, the user needs all of the following OpenVMS privileges:
l ALTPRI
l BUGCHK
l BYPASS
l CMKRNL
l DIAGNOSE
l IMPERSONATE
l NETMBX

HPE Insight Remote Support 7.10: Monitored Devices Configuration Guide Page 205 of 436
Chapter 17: Configuring VSI OpenVMS Integrity servers

l OPER
l SYSLCK
l SYSPRV
l TMPMBX
HPE recommends that you install ELMC using the SYSTEM account.

Grant permissions required to run ELMC

To execute any ELMC commands, the user needs all of the following OpenVMS privileges. Note that these
are a subset of the privileges required to install, upgrade or uninstall ELMC:
l ALTPRI
l BUGCHK
l CMKRNL
l DIAGNOSE
l IMPERSONATE
l NETMBX
l SYSPRV
l TMPMBX

Heterogeneous cluster instructions

A heterogeneous cluster is a cluster with multiple system disks. Before beginning the ELMC installation in an
OpenVMS cluster with multiple system disks, check to see if the system disks are mounted cluster-wide. To
avoid potential problems, all remotely mounted system disks should be dismounted prior to installing ELMC
on an OpenVMS heterogeneous cluster. After the install is done, the system administrator can remount the
disks. Failure to perform this step can result in the following:
l When user has a heterogeneous cluster where the system disks are mounted cluster-wide, all of the ELMC
[root.SYSCOMMON.HP.NODES.nodename] directories will be created on the system disk where the install
was performed. No directories are created on the other system disks.
l The PCSI database will only be updated on the system disk where the installation was performed. The
WCCProxy process will be running on other cluster members with different system disks; however, a
PRODUCT SHOW PRODUCT will not provide any indication that the product was actually installed.
l On every node of the cluster the ELMC WCCPROXY process runs the images from the system disk where
the installation was performed. This may be problematic if the other system disks are running different
versions of OpenVMS or have different operating system patches installed.
l If the system disk where the installation was performed is unavailable due to a planned shutdown or crash,
the ELMC application will fail to run on the remaining nodes of the cluster. This means that no monitoring
will occur until the system disk where the installation was performed becomes available again.
The following example illustrates the issue: assume the user has a 2 node cluster with one system running
OpenVMS 8.4-1H1 and another system running OpenVMS 8.4-2. If ELMC is installed on the system running
OpenVMS 8.4-1H1, the system running OpenVMS 8.4-2 will have a WCCProxy process running images from

HPE Insight Remote Support 7.10: Monitored Devices Configuration Guide Page 206 of 436
Chapter 17: Configuring VSI OpenVMS Integrity servers

the OpenVMS 8.4-1H1 system disk, which will be using library modules from the OpenVMS 8.4-2 system
disk. This combination of images and library modules may cause issues. If the user examines the PCSI
database of the OpenVMS 8.4-2 system disk, there will be no evidence that ELMC is installed and running on
this system. The ELMC root for the OpenVMS 8.4-2 system will be created on the OpenVMS 8.4-1H1 system
disk. If the OpenVMS 8.4-1H1 system is shutdown, the ELMC application on the OpenVMS 8.4-2 system will
stop functioning until the OpenVMS 8.4-1H1 system is rebooted.

Archiving and cleaning the error log

After Insight Remote Support is installed on the Hosting Device, it uses ELMC to analyze all events stored in
the error log, which can result in high CPU usage over an extended period. To control this operation, you are
encouraged to archive and clean the error log before installing. This reduces the size of the log and the time
required for the initial scan.
Follow these guidelines for cleaning the error log. If ELMC is installed and running when you clean the log, you
do not need to stop and restart the Director process. Also, do not stop and restart the ERRFMT system event
logging process.
The default error log, typically SYS$SYSROOT:[SYSERR]ERRLOG.SYS, increases in size and remains on the
system disk until the user explicitly renames or deleted it. When either occurs, the system creates a new,
clean error log file after about 15 minutes.

Caution: After renaming or deleting the existing log, do not install ELMC until the new default log is
present.

If you rename the log, the saved log can be analyzed at a later time.
Aside from starting with a clean log before installing Insight Remote Support, you may want to perform regular
maintenance on the error log. One method is to rename errlog.sys on a monthly basis. For example, you
might rename errlog.sys to errlog.old at 00:01 on the first day of every month. To free space on the
system disk, you then can back up the renamed version to a different volume and delete the file from the
system disk.

Confirm SYSMAN is functioning cluster-wide

The installation of ELMC makes use of the SYSMAN utility. Confirm that SYSMAN is functioning correctly on
every node of a cluster before attempting ELMC installation. Issue the following command to confirm that the
SHOW DEVICE SYS$SYSDEVICE: command completes normally for all nodes in the cluster.
$ MCR SYSMAN
SYSMAN> SET ENV/CLUSTER
SYSMAN> DO SHOW DEVICE SYS$SYSDEVICE:

How to remove ELMC

If you have an older version of ELMC installed, remove this before installing the latest version of ELMC. You
can determine if you have an older version by issuing the following command.
$ PRODUCT SHOW PRODUCT WCCPROXY
If the version of WCCPROXY is anything other than V6.4, ELMC needs to be upgraded.

HPE Insight Remote Support 7.10: Monitored Devices Configuration Guide Page 207 of 436
Chapter 17: Configuring VSI OpenVMS Integrity servers

If the cluster has multiple system disks, check to see if the system disks are mounted cluster-wide. To avoid
potential problems, all remotely mounted system disks should be dismounted prior to removing ELMC on an
OpenVMS heterogeneous cluster.
1. Stop the WCCPROXY process:
l If this is a standalone system, issue the following command:
$ wccproxy stop
l If this is a cluster, stop WCCPROXY processes by issuing the following commands:
$ mcr sysman
SYSMAN> set env/cluster
SYSMAN> do wccproxy stop

2. Confirm no WCCPROXY processes exist by issuing the following command:

$ show system/process=wccproxy/cluster
If any WCCPROXY processes exist that could not be terminated, issue a STOP/ID=<pid_of_wccproxy_
process> on the system with the WCCPROXY process.
3. Find the WCCPROXY_INSTALL.COM procedure located in the installation directory of ELMC by issuing the
following command:
$ directory WCCPROXY_HOME:[*...]wccproxy_install.com
Directory WCCPROXY_COMMON:[COMMON.WCCPROXY.BIN]
WCCPROXY_INSTALL.COM;1
Total of 1 file.

4. If the WCCPROXY_HOME logical points to a nonexistent disk, then search the system disk for the WCCPROXY_
INSTALL.COM procedure.
$ directory sys$sysdevice:[*...]wccproxy_install.com
5. ELMC can be removed by executing the WCCPROXY_COM procedure found in the ELMC installation
directory.
$ @WCCPROXY_COMMON:[COMMON.WCCPROXY.BIN]wccproxy_install.com "uninstall"
If no WCCPROXY_INSTALL.COM procedure can be located, then use the v6.4 WCCPROXY_INSTALL.COM
procedure.

Install the ELMC VSI OpenVMS Software Package on the

Monitored Device
Check if ELMC is already installed with the command: product show product wccproxy.
If this returns 0 items found then ELMC has never been installed. If the version of WCCPROXY is anything
other than V6.4, ELMC needs to be upgraded. For how to uninstall older versions of ELMC, see "How to
remove ELMC" on the previous page.
To install the ELMC software package, complete the following steps:
1. In the Insight RS Console, navigate to the Administrator Settings → Software Updates tab and select
the Event Log Monitoring Collector (ELMC) software package.
2. On the Available Version tab, click Download.

HPE Insight Remote Support 7.10: Monitored Devices Configuration Guide Page 208 of 436
Chapter 17: Configuring VSI OpenVMS Integrity servers

3. When the download completes, click Install. The ELMC packages are placed in the %HP_RS_
DATA%\SWM\LANDINGZONE\ELMC folder. This folder defaults to
C:\ProgramData\HP\RS\DATA\SWM\LANDINGZONE\ELMC.

Note: The ProgramData folder is a hidden folder. To view this folder, set the folder options to
show hidden folders.

4. Copy the VSI OpenVMS Itanium ELMC software package (ELMC_VSI_KIT1_17-MAY-2016_

OVMSI64.EXE) to the OpenVMS monitored device. Place the .exe file in an empty directory. Make sure
that:
l There are no other kits in the directory, especially other versions of ELMC kits.
l There are no old ELMC or WCCProxy files in the directory left over from previous operations.
5. Extract the ELMC installation files:
$ run ELMC_VSI_KIT1_17-MAY-2016_OVMSI64.EXE
6. Run the wccproxy_install.com command procedure to either upgrade or install ELMC. Then follow the
prompts.
l Run the following command to install ELMC on the system disk:
$ @wccproxy_install.com "install"
l Run the following command to install ELMC on a disk other than the system disk:
$ @wccproxy_install.com "install" "<installation directory>"
Example:
$ @wccproxy_install.com "install" "COMMON$DISK:[ELMC]"
The installation asks the following question:
Use the following command to install standalone ELMC/Proxy kit
@WCCPROXY_INSTALL.COM INSTALL <installation_path> Do you want to continue?[NO]:

Respond YES to this question.

Note: The command executes the DCL script wccproxy_install.com in the current directory.
Do not run the product install wccproxy command that would normally be used to install a
PCSI-based product. This command aborts and prompts you to run the wccproxy_
install.com script instead. Set your default directory to the one containing the file wccproxy_
install.com, created by extracting the ELMC .exe file in the previous step.

When the DCL prompt ($) returns, the install has finished and the ELMC (WCCProxy) process will be
running.
7. Add the WCCPROXY STOP command to SYS$MANAGER:SYSHUTDWN.COM command procedure.
No command has to be added to the site specific boot command procedure since the installation will
have added the following to the SYSMAN utility:
SYSMAN> startup show file WCCPROXY$STARTUP.COM
%SYSMAN-I-COMFIL, contents of component database on node XXXX

HPE Insight Remote Support 7.10: Monitored Devices Configuration Guide Page 209 of 436
Chapter 17: Configuring VSI OpenVMS Integrity servers

Phase Mode File

------------ ------ ---------------------------------
LPMAIN DIRECT WCCPROXY$STARTUP.COM

WCCPROXY command verb reference

The installation of ELMC adds the WCCPROXY command to the DCLTABLES of the OpenVMS system.
l WCCPROXY START
This command starts the WCCPROXY process.
l WCCPROXY STOP
This command stops the WCCPROXY process.
l WCCPROXY STATUS
This command shows the status of the WCCPROXY process.

Install ELMC when a new system is added to an existing

ELMC installation
If the cluster has multiple system disks, check to see if the system disks are mounted clusterwide. To avoid
potential problems, all remotely mounted system disks should be dismounted prior to installing ELMC on an
OpenVMS heterogeneous cluster. After the install is done, the system administrator can remount the disks.
Next determine if the new cluster member boots off a system which already has ELMC installed.
$ PRODUCT SHOW PRODUCT WCCPROXY
If this returns, 0 items found then ELMC has never been installed on this system disk.
l If ELMC is not installed, install it by executing the following command in a directory that contains the
ELMC installation kit. For where to obtain the ELMC kit, see "Install the ELMC VSI OpenVMS Software
Package on the Monitored Device" on page 208.
$ @wccproxy_install.com "install"
l If ELMC is already installed on the system disk uninstall and reinstall ELMC. Complete the following in a
directory that contains the ELMC installation kit:
a. Remove WCCPROXY:
$ @wccproxy_install.com "uninstall"
b. Install WCCPROXY:
$ @wccproxy_install.com "install"

Install the VSI OpenVMS WBEM Services and WBEM

Providers
Configure WBEM for discovery and Basic Configuration Collections, which are necessary if your system is
covered by a Proactive services contract.

HPE Insight Remote Support 7.10: Monitored Devices Configuration Guide Page 210 of 436
Chapter 17: Configuring VSI OpenVMS Integrity servers

The following steps configure WBEM Services (WBEMCIM) and WBEM Providers (WBEMPROVIDERS).
Make sure that you are logged into the SYSTEM account; a fully privileged user account is not sufficient for
this activity.
Before installing or upgrading, check what versions of WBEMCIM and WBEMPROVIDERS are installed. An
upgrade of these products will be necessary if you are not running the most recent version. The minimum
version that you should be running are shown below.
To view your version of WBEM, run the following command: PRODUCT SHOW PRODUCT WBEM*
l VSI OpenVMS 8.4-1H1 or 8.4-2
l VSI I64VMS WBEMCIM V3.0-B151019
l VSI I64VMS WBEMPROVIDERS V2.2-5
The installation kits for WBEMCIM V3.0-B151019 and WBEMPROVIDERS V2.2-5 can be found on the
VSI OpenVMS 8.4-2 operating system dvd in the [KITS.WBEMCIM] and [KITS.WBEMPROVIDERS]
directories.

Important: VSI OpenVSM 8.4-1H1 comes with WBEMCIM-V0299-B100614 and

WBEMPROVIDERS-V0202-3A. It is extremely important that WBEMCIM and
WBEMPROVIDERS are upgraded since these old versions are known to have significant issues
that can severally impact overall system performance. Some of these issues include system
hangs which will require system reboots to rectify, CIMSERVER process stuck in a MUTEX or
WINS state which requires a system reboot to clear, or frequent CIMSERVER.DMP files which
fill up the system disk.

l VSI OpenVMS V8.4-2L1

l VSI I64VMS WBEMCIM V3.0-C160513
l VSI I64VMS WBEMPROVIDERS V2.2-5C
WBEMCIM V3.0-C160513 and WBEMPROVIDERS V2.2-5C can be found on the VSI OpenVMS 8.4-2L1
operating system DVD.
l VSI TCP/IP Version 10.5
l VSI-I64VMS-WBEMCIM-V0300-C180108-1
Confirm TCP/IP IP address and name resolution is functioning
Before configuring WBEM Services and WBEM Providers, confirm that TCP/IP is correctly configured. Make
sure that you are able to ping by IP address, system name, and fully qualified name from the Hosting Device
to the OpenVMS system and from the OpenVMS system to the Hosting Device. If the address or name is not
found, add it to the local host file or to the DNS server.
If your OpenVMS system has both a DNS TCP/IP cluster alias name and node specific name that refer to the
same IP address, add the fully qualified name of the node specific name to the local host file of the Insight RS
Hosting Device.

Check if WBEM was previously configured

Check to see if WBEM Services or WBEM Providers were previously configured so you know whether you
need to perform a fresh install or an upgrade. If any of the below tests are positive, then WBEM Services and
WBEM Providers has been previously configured and therefore you should upgrade instead of perform a fresh

HPE Insight Remote Support 7.10: Monitored Devices Configuration Guide Page 211 of 436
Chapter 17: Configuring VSI OpenVMS Integrity servers

install.
1. Are the following processes are running?
$ SHOW SYSTEM/PROCESS=OPEN*
00007252 OPENVMS_UTILD HIB 5 59581523 0 03:57:40.96 532 546
00007253 OPENVMS_EMS HIB 5 3975 0 00:00:01.87 1092 1965 M

$ SHOW SYS/PROCESS=CIM*
00007227 CIMSERVER HIB 10 197589 0 00:00:39.70 2131 2940 M

$ SHOW SYSTEM/PROCESS=WBEMP*
21000478 WBEMPROV$HOST_P HIB 6 445 0 00:00:01.72 1254 1421 M

2. Are WBEM logicals defined?

$ SHOW LOGICAL WBEM*
(LNM$SYSTEM_TABLE)
"WBEM_BIN" = "wbem_opt:[wbem.bin]"
"WBEM_CIMXX_MOF_DIR" = "wbem_opt:[wbem.mof.CIM29]"
"WBEM_ETC" = "SYS$SYSDEVICE:[SYS0.syscommon.wbem_services.etc.]"
"WBEM_LIB" = "sys$library"
"WBEM_MOF_DIR" = "SYS$SYSDEVICE:[SYS0.syscommon.wbem_services.opt.wbem.mof.]"
"WBEM_OPT" = "SYS$SYSDEVICE:[SYS0.syscommon.wbem_services.opt.]"
"WBEM_REPOSITORY_DIR" = "wbem_var:[opt.wbem.repository]"
"WBEM_SBIN" = "wbem_opt:[wbem.sbin]"
"WBEM_TMP" = "SYS$SPECIFIC:[WBEM_Services.tmp]"
"WBEM_VAR" = "$2$DKC300:[SYS0.WBEM_Services.var.]"
"WBEM_VAR_DATA_DIR" = "wbem_var:[opt.wbem]"

3. Has the following command has been added to the system startup? Check files such as SYS$MANAGER:
SYSTARTUP_VMS.COM.
$ @SYS$STARTUP:WBEM_Services$Startup.com
4. Has the WBEM repository has been created on the system disk?
$ DIRECTORY SYS$SYSDEVICE:[*...]repository.dir
Directory SYS$SYSDEVICE:[SYS0.WBEM_Services.var.opt.wbem]
repository.DIR;1
Total of 1 file.

If any of the above checks answered Yes, then go to "Upgrade WBEM" on page 216.
If all of the above checks answered No, then go to "Install WBEMCIM and WBEMPROVIDERS for the first
time" below.

Install WBEMCIM and WBEMPROVIDERS for the first time

Install WBEM Services and WBEM Providers with a PRODUCT INSTALL command using the kits downloaded
above.

HPE Insight Remote Support 7.10: Monitored Devices Configuration Guide Page 212 of 436
Chapter 17: Configuring VSI OpenVMS Integrity servers

1. Install WBEM Services and WBEM Providers:

$ PRODUCT INSTALL WBEMCIM
$ PRODUCT INSTALL WBEMPROVIDERS
2. Configure WBEM Services and create repository. The following command which invokes the utility that
configures and initializes the environment for WBEM Services for OpenVMS including the creation of the
WBEM repository. By default the WBEM repository will be created on the system disk in SYS$SPECIFIC:
[WBEM_Services.var.opt.wbem.repository]. If the system disk is an ODS-2 structured disk, then the
WBEM repository must be created on another disk which is an ODS-5 structured disk.
$ RUN SYS$SYSROOT:[WBEM_Services]WBEM_Services$Config.exe
When prompted to start the CIMserver, answer YES.
In an OpenVMS Cluster, each member that runs WBEM Services for OpenVMS needs its own WBEM
repository. Therefore, you must execute this image on each of those cluster members.
3. Execute the following command procedure that defines WBEM commands and also add this command
to the login.com of the SYSTEM account in the section where interactive commands are invoked:
$ @SYS$COMMON:[wbem_services]WBEM_Services$Define_Commands.com
4. Verify WBEM Services:
a. Check if the CIMSERVER and CIMDAEMON processes exist and are in the HIB state:
$ SHOW SYSTEM/PROCESS=CIM*
20719DB1 CIMSERVER HIB 10 72063 0 00:00:14.27 3171 2905 M
207199C6 CIMDAEMON HIB 10 6449 0 00:00:00.39 1784 260

b. Confirm system knows about the providers created by WBEM Services and that their status is OK.
$ cimprovider –ls
MODULE STATUS
OperatingSystemModule OK
ComputerSystemModule OK
ProcessModule OK
IPProviderModule OK
If the cimprovider command is unknown:
$ cimprovider
%DCL-W-IVVERB, unrecognized command verb - check validity and spelling

Execute the following command procedure and also add this command to the login.com of the
SYSTEM account in the section where interactive commands are invoked:
$ @SYS$COMMON:[wbem_services]WBEM_Services$Define_Commands.com
c. Verify that the WBEM Services CIMSERVER is responding to requests by using the OSINFO
command:
$ OSINFO
OperatingSystem Information

HPE Insight Remote Support 7.10: Monitored Devices Configuration Guide Page 213 of 436
Chapter 17: Configuring VSI OpenVMS Integrity servers

Host: i64svr
Name: OpenVMS
Version: V8.3-1H1
UserLicense: Unlimited user license
Number of Users: 2 users
Number of Processes: 28 processes
OSCapability: 64 bit
LastBootTime: Mar 20, 2009 0:41:21 (-0600)
LocalDateTime: Mar 21, 2009 13:58:57 (-0600)

If the OSINFO command does not work then the CIMSERVER process may be hung.
d. Confirm that the CIMSERVER process is using port 5989 by issuing the following commands:
o For TCPIP V5.7:
$ TCPIP SHOW DEVICE_SOCKET/PORT=5989
Port Remote
Device_socket Type Local Remote Service Host
bg22708 STREAM 5989 0 *
o For TCPIP 10.5:
$ pipe ip show /conn=process | search /exact sys$pipe "(5989)"
CIMSERVER 0 0 *(5989) *(*)

$ SHOW DEVICE <bg_device_name>/FULL

For example:
$ SHOW DEVICE bg22708/FULL
Device BG22708: device type unknown, is online, mounted, record-oriented
device, network device, mailbox device.
Error count 0 Operations completed 58
Owner process "CIMSERVER" Owner UIC [SYSTEM]
Owner process ID 00007227 Dev Prot S:RWPL,O:RWPL,G:RWPL,W:RWPL
Reference count 1 Default buffer size 256

5. Execute the command procedure that configures WBEM Providers.

$ @SYS$COMMON:[WBEMPROVIDERS]WBEMPROVIDERS$CONFIGURE.COM
Verify WBEM Providers:
a. Verify that the list of WBEM Providers displays the following and that the status of all providers is
OK:
$ cimprovider -ls
MODULE STATUS
EventIndicationConsumerModule OK
EMSWrapperProviderModule OK
HPVMSLANIndicationProviderModule OK

HPE Insight Remote Support 7.10: Monitored Devices Configuration Guide Page 214 of 436
Chapter 17: Configuring VSI OpenVMS Integrity servers

StateChangeIndicationProviderModule OK
ChassisProviderModule OK
cpuprovidermodule OK
MemoryModule OK
FirmwareRevisionProviderModule OK
MPProviderModule OK
EnclosureProviderModule OK
HPHealthStateProviderModule OK
HPVMSLANProviderModule OK
HPVMSLANCSProviderModule OK
CSChassisProviderModule OK
HPVMProviderModule OK
HP_UtilizationProviderModule OK
OperatingSystemModule OK
ComputerSystemModule OK
ProcessModule OK
IPProviderModule OK

b. Confirm that the OPENVMS_EMS and OPENVMS_UTILD processes exist:

$ SHOW SYSTEM/PROCESS=OPEN*
000069EE OPENVMS_UTILD HIB 6 7476021 0 00:09:34.24 437 446
000069EF OPENVMS_EMS HIB 6 22234 0 00:00:00.18 1150 1928 M

c. Confirm that the WBEMPROV$HOST_P process exists on models that support setting
HOSTINFOPARAMS on the ILO:
$ SHOW SYSTEM/PROCESS=WBEMPROV*
000069F0 WBEMPROV$HOST_P HIB 6 275 0 00:00:00.11 1055 1689 M

6. Create a nonprivileged account and a cimuser user whose username and password corresponds to the
SYSUAF account. This user account will be used by Insight RS when communicating with your
OpenVMS system using the WBEM protocol.
The following is an example of what the OpenVMS account should look like:
$ mcr authorize show wbem
Username: WBEM Owner: WBEM
Account: WBEM UIC: [10,266] ([WBEM])
CLI: DCL Tables: DCLTABLES
Default: SYS$SYSDEVICE:[WBEM]
LGICMD:
Flags:
Primary days: Mon Tue Wed Thu Fri
Secondary days: Sat Sun
No access restrictions
Expiration: (none) Pwdminimum: 8 Login Fails: 0
Pwdlifetime: (none) Pwdchange: 14-JAN-2010 16:40
Last Login: 23-NOV-2009 10:31 (interactive), 3-FEB-2010 14:07 (non-interactive)
Maxjobs: 0 Fillm: 128 Bytlm: 256000

HPE Insight Remote Support 7.10: Monitored Devices Configuration Guide Page 215 of 436
Chapter 17: Configuring VSI OpenVMS Integrity servers

Maxacctjobs: 0 Shrfillm: 0 Pbytlm: 0

Maxdetach: 0 BIOlm: 150 JTquota: 4096
Prclm: 10 DIOlm: 150 WSdef: 4096
Prio: 4 ASTlm: 300 WSquo: 8192
Queprio: 0 TQElm: 100 WSextent: 16384
CPU: (none) Enqlm: 4000 Pgflquo: 700000
Authorized Privileges:
NETMBX TMPMBX
Default Privileges:
NETMBX TMPMBX

Note: The above WBEM account was created with the following commands:
$ mcr authorize add wbem/uic=
[10,266]/flag=nodisuser/nopwdexpired/password=wbem
$ mcr authorize modify wbem/nopwdlifetime/device=sys$sysdevice/directory=
[wbem]

a. Create the cimuser user with the following command. HPE recommends specifying the username in
lowercase and surrounded by quotes.
$ cimuser -a -u "<username>" -w "<password>"
Example:
$ cimuser -a -u "wbem" -w "mypassword"
b. Confirm that the user was created by issuing the command:
$ cimuser -l
wbem
c. Confirm that you can log on to the OpenVMS account.
7. Add WBEM Services and WBEM Providers to system startup and system shutdown to ensure they start
up at system boot and shutdown during a planned system shutdown.
Add the following command to the system startup:
$ @SYS$STARTUP:WBEM_Services$Startup.com
Since it may take a few minutes to startup WBEM Services, in order to not delay your system boot,
consider creating a batch command procedure that includes this command and invoking the batch job
from SYS$MANAGER:SYSTARTUP_VMS.COM.
Add the following command to the system shutdown in SYS$STARTUP:SYSHUTDWN.COM:
$ @SYS$STARTUP:WBEM_Services$Shutdown.com

Upgrade WBEM
If you need to upgrade a previously configured environment, HPE recommends that you perform the following
steps to upgrade the software. Note that whenever WBEM Services or WBEM Providers is upgraded, the
modified product needs to be reconfigured.

HPE Insight Remote Support 7.10: Monitored Devices Configuration Guide Page 216 of 436
Chapter 17: Configuring VSI OpenVMS Integrity servers

1. Install WBEM Services and WBEM Providers:

l Issue the following commands if both products need to be upgraded:
$ @SYS$COMMON:[WBEMPROVIDERS]WBEMPROVIDERS$DECONFIGURE.COM
$ @SYS$STARTUP:WBEM_Services$Shutdown.com
$ PRODUCT INSTALL WBEMCIM
$ PRODUCT INSTALL WBEMPROVIDERS
$ RUN SYS$SYSROOT:[WBEM_Services]WBEM_Services$Config.exe

Issue the following command if you have an appropriate operating system version and model for
Configuring WBEM Providers
$ @SYS$COMMON:[WBEMPROVIDERS]WBEMPROVIDERS$CONFIGURE.COM
l Issue the following commands if only WBEM Services needs to be upgraded:
$ @SYS$STARTUP:WBEM_Services$Shutdown.com
$ PRODUCT INSTALL WBEMCIM
$ RUN SYS$SYSROOT:[WBEM_Services]WBEM_Services$Config.exe

l Issue the following commands if only WBEM Providers needs to be upgraded:

$ @SYS$COMMON:[WBEMPROVIDERS]WBEMPROVIDERS$DECONFIGURE.COM
$ @SYS$STARTUP:WBEM_Services$Shutdown.com
$ PRODUCT INSTALL WBEMPROVIDERS
$ @SYS$STARTUP:WBEM_Services$Startup.com

Issue the following command if you have an appropriate operating system version and model for
Configuring WBEM Providers
$ @SYS$COMMON:[WBEMPROVIDERS]WBEMPROVIDERS$CONFIGURE.COM
2. Verify WBEM Services:
a. Check if the CIMSERVER and CIMDAEMON processes exist and are in the HIB state:
$ SHOW SYSTEM/PROCESS=CIM*
20719DB1 CIMSERVER HIB 10 72063 0 00:00:14.27 3171 2905 M
207199C6 CIMDAEMON HIB 10 6449 0 00:00:00.39 1784 260

b. Confirm system knows about the providers created by WBEM Services and that their status is OK.
$ cimprovider –ls
MODULE STATUS
OperatingSystemModule OK
ComputerSystemModule OK
ProcessModule OK
IPProviderModule OK

If the cimprovider command is unknown:

$ cimprovider
%DCL-W-IVVERB, unrecognized command verb - check validity and spelling

Execute the following command procedure and also add this command to the login.com of the
SYSTEM account in the section where interactive commands are invoked:

HPE Insight Remote Support 7.10: Monitored Devices Configuration Guide Page 217 of 436
Chapter 17: Configuring VSI OpenVMS Integrity servers

$ @SYS$COMMON:[wbem_services]WBEM_Services$Define_Commands.com
c. Verify that the WBEM Services CIMSERVER is responding to requests by using the OSINFO
command:
$ OSINFO
OperatingSystem Information
Host: i64svr
Name: OpenVMS
Version: V8.3-1H1
UserLicense: Unlimited user license
Number of Users: 2 users
Number of Processes: 28 processes
OSCapability: 64 bit
LastBootTime: Mar 20, 2009 0:41:21 (-0600)
LocalDateTime: Mar 21, 2009 13:58:57 (-0600)

If the OSINFO command does not work then the CIMSERVER process may be hung.
d. Confirm that the CIMSERVER process is using port 5989 by issuing the following commands:
o For TCPIP 5.7:
$ TCPIP SHOW DEVICE_SOCKET/PORT=5989
Port Remote
Device_socket Type Local Remote Service Host
bg22708 STREAM 5989 0 *
o For TCPIP 10.5:
$ pipe ip show /conn=process | search /exact sys$pipe "(5989)"
CIMSERVER 0 0 *(5989) *(*)

$ SHOW DEVICE <bg_device_name>/FULL

For example:
$ SHOW DEVICE bg22708/FULL
Device BG22708: device type unknown, is online, mounted, record-oriented
device, network device, mailbox device.
Error count 0 Operations completed 58
Owner process "CIMSERVER" Owner UIC [SYSTEM]
Owner process ID 00007227 Dev Prot S:RWPL,O:RWPL,G:RWPL,W:RWPL
Reference count 1 Default buffer size 256

3. Execute the command procedure that configures WBEM Providers.

$ @SYS$COMMON:[WBEMPROVIDERS]WBEMPROVIDERS$CONFIGURE.COM
Verify WBEM Providers:
a. Verify that the list of WBEM Providers displays the following and that the status of all providers is
OK:

HPE Insight Remote Support 7.10: Monitored Devices Configuration Guide Page 218 of 436
Chapter 17: Configuring VSI OpenVMS Integrity servers

$ cimprovider -ls
MODULE STATUS
EventIndicationConsumerModule OK
EMSWrapperProviderModule OK
HPVMSLANIndicationProviderModule OK
StateChangeIndicationProviderModule OK
ChassisProviderModule OK
cpuprovidermodule OK
MemoryModule OK
FirmwareRevisionProviderModule OK
MPProviderModule OK
EnclosureProviderModule OK
HPHealthStateProviderModule OK
HPVMSLANProviderModule OK
HPVMSLANCSProviderModule OK
CSChassisProviderModule OK
HPVMProviderModule OK
HP_UtilizationProviderModule OK
OperatingSystemModule OK
ComputerSystemModule OK
ProcessModule OK
IPProviderModule OK

b. Confirm that the OPENVMS_EMS and OPENVMS_UTILD processes exist:

$ SHOW SYSTEM/PROCESS=OPEN*
000069EE OPENVMS_UTILD HIB 6 7476021 0 00:09:34.24 437 446
000069EF OPENVMS_EMS HIB 6 22234 0 00:00:00.18 1150 1928 M

c. Confirm that the WBEMPROV$HOST_P process exists on models that support setting
HOSTINFOPARAMS on the ILO:
$ SHOW SYSTEM/PROCESS=WBEMPROV*
000069F0 WBEMPROV$HOST_P HIB 6 275 0 00:00:00.11 1055 1689 M

4. Remove all cimuser accounts and add them back again. The cimuser command is used to define the
WBEM user credentials that will be used by Insight RS when communicating with your OpenVMS
system using the WBEM protocol.
The following example shows how to remove and add a user back in again.
a. Show the user:
$ cimuser -l
wbem
b. Remove the user:
$ cimuser –r –u "wbem"
User removed successfully.
c. Before adding the cimuser account, confirm that the account exists in the SYSUAF and that you can

HPE Insight Remote Support 7.10: Monitored Devices Configuration Guide Page 219 of 436
Chapter 17: Configuring VSI OpenVMS Integrity servers

log into the account. If the user is missing, create a nonprivileged account and a cimuser user whose
username and password corresponds to the SYSUAF account.
The following is an example of what the OpenVMS account should look like:
$ mcr authorize show wbem
Username: WBEM Owner: WBEM
Account: WBEM UIC: [10,266] ([WBEM])
CLI: DCL Tables: DCLTABLES
Default: SYS$SYSDEVICE:[WBEM]
LGICMD:
Flags:
Primary days: Mon Tue Wed Thu Fri
Secondary days: Sat Sun
No access restrictions
Expiration: (none) Pwdminimum: 8 Login Fails: 0
Pwdlifetime: (none) Pwdchange: 14-JAN-2010 16:40
Last Login: 23-NOV-2009 10:31 (interactive), 3-FEB-2010 14:07 (non-interactive)
Maxjobs: 0 Fillm: 128 Bytlm: 256000
Maxacctjobs: 0 Shrfillm: 0 Pbytlm: 0
Maxdetach: 0 BIOlm: 150 JTquota: 4096
Prclm: 10 DIOlm: 150 WSdef: 4096
Prio: 4 ASTlm: 300 WSquo: 8192
Queprio: 0 TQElm: 100 WSextent: 16384
CPU: (none) Enqlm: 4000 Pgflquo: 700000
Authorized Privileges:
NETMBX TMPMBX
Default Privileges:
NETMBX TMPMBX

Note: The above WBEM account was created with the following commands:
$ mcr authorize add wbem/uic=
[10,266]/flag=nodisuser/nopwdexpired/password=wbem
$ mcr authorize modify wbem/nopwdlifetime/device=sys$sysdevice/directory=
[wbem]

d. Create the cimuser user with the following command. HPE recommends specifying the username in
lowercase and surrounded by quotes.
$ cimuser -a -u "<username>" -w "<password>"
Example:
$ cimuser -a -u "wbem" -w "mypassword"
e. Confirm that the user was created by issuing the command:
$ cimuser -l
wbem
f. Confirm that you can log on to the OpenVMS account.

HPE Insight Remote Support 7.10: Monitored Devices Configuration Guide Page 220 of 436
Chapter 17: Configuring VSI OpenVMS Integrity servers

5. Verify WBEM Services and WBEM Providers are in the system startup and system shutdown to ensure
they start up at system boot and shutdown during a planned system shutdown. If they are not, add them.
Add the following command to the system startup:
$ @SYS$STARTUP:WBEM_Services$Startup.com
Since it may take a few minutes to startup WBEM Services, in order to not delay your system boot,
consider creating a batch command procedure that includes this command and invoking the batch job
from SYS$MANAGER:SYSTARTUP_VMS.COM.
Add the following command to the system shutdown in SYS$STARTUP:SYSHUTDWN.COM:
$ @SYS$STARTUP:WBEM_Services$Shutdown.com

Configure dynamic processor resilience

Dynamic Processor Resilience, also known as CPU Indictment, is the ability for Insight RS to detect various
error conditions occurring in the processor, or on the processor bus/links, and remove the processor from
operation. On HPE Integrity servers running OpenVMS, this capability is implemented by a combination of
analysis within Insight RS and Kernel CPU indictment services provided by the OpenVMS operating system.
When a CPU is indicted, the kernel CPU indictment service will remove the processor from the active set.
Additionally Insight RS will log a service call. By removing the failing processor from the active set this
prohibits the processor from failing fatally at some future time. Automatically logging the service call allows
automatic proactive repair further aiding in prompt resolution of the problem.
To use Dynamic Processor Resilience, it needs to be configured on the OpenVMS server and also enabled in
the Insight RS Console.
To enable Dynamic Processor Resilience on the OpenVMS server, complete the following steps:
1. Edit the SYS$INDICTMENT_POLICY.COM command procedure and change their values from 0 to 1:
$ DEFINE/SYSTEM/EXECUTIVE_MODE/NOLOG SYS$INDICT_START 1
$ DEFINE/SYSTEM/EXECUTIVE_MODE/NOLOG SYS$INDICT_ALLOW_CPUS 1

This enables all CPUs to be eligible for Indictment except for CPU 0.

Note: CPU 0 cannot be removed. If you wish to not have some CPU’s eligible, refer to the VSI
OpenVMS documentation for Indictment Service to learn how to modify this procedure to meet
your needs.

2. Reboot the server for the changes to take effect.

When the Indictment Server is started, there will be an INDICT_SERVER process shown in the SHOW
SYS output:
$ show system/process=INDICT_SERVER
0000041C INDICT_SERVER HIB 8 6 0 00:00:00.00 79 95

To enable the Dynamic Processor Resilience Adapter in the Insight RS Console, complete the following
steps:
1. In the main menu, select Administrator Settings.
2. Click the Integration Adapters tab.

HPE Insight Remote Support 7.10: Monitored Devices Configuration Guide Page 221 of 436
Chapter 17: Configuring VSI OpenVMS Integrity servers

3. Click the Dynamic Processor Resilience Adapter for HPE Integrity servers heading to expand the
adapter pane.

4. Select the Enable Dynamic Processor Resilience Adapter for HPE Integrity servers check box.
5. Click Save Adapter Settings.
Insight Remote Support enables the Dynamic Processor Resilience Adapter. (Enabled) now appears next to
the Dynamic Processor Resilience Adapter to indicate it is enabled.

Configure firewall and port settings

Table 17.2 OpenVMS Integrity Connectivity - Firewall/Port Requirements
Protocol Ports Source Destination Function Optional

ICMP N/A Hosting Monitored Provides system reachability (ping) check during system Required
Device Systems discovery and before other operations.

TCP 5989 Hosting Monitored Secured WBEM CIMOM protocol over HTTPS/SOAP. Required
Device Systems This port is used to communicate with WBEM end point
nodes.

TCP 7905 Monitored Hosting Secure HTTP (HTTPS) port used by the listener running Required
Systems Device in the Director's Web Interface. The monitored host
connects to the Hosting Device on this port (e.g.
https://<hostname>:7905).

TCP 7920 Hosting Monitored The Insight RS ELMC (WCCProxy) process Required
Device Systems communicates with the Director on this port. This is a
proprietary protocol. Any connections that exchange
username and passwords use SSL. Not all connections
are SSL.

Add protocol credentials and start discovery

To discover your monitored devices, complete the following sections:

Create a WBEM protocol credential in Insight RS Console

To configure WBEM in the Insight RS Console, complete the following steps:
1. In a web browser, log on to the Insight RS Console.
2. In the main menu, select Discovery and click the Credentials tab.

HPE Insight Remote Support 7.10: Monitored Devices Configuration Guide Page 222 of 436
Chapter 17: Configuring VSI OpenVMS Integrity servers

3. From the Select and Configure Protocol drop-down list, select Web-Based Enterprise Management
(WBEM).
Note that if you have more than one OpenVMS server with the same WBEM credentials, you may prefer
to create a Named Credential and use it here.
4. Click New. The New Credential dialog box appears.
5. Type the Username and Password you have configured on your device.
Type the Username and Password that corresponds to the cimuser account defined on the OpenVMS
server. The Username and Password are case sensitive and must match the cimuser credentials defined
on the OpenVMS server.
6. Click Add.
Insight RS creates the protocol credential and it appears in the credentials table.

Discover the device in the Insight RS Console

To discover the device from the Insight RS Console, complete the following steps:
1. In a web browser, log on to the Insight RS Console.
2. In the main menu, select Discovery and click the Sources tab.
3. Expand the IP Addresses section and add the IP address for your device:
a. Click New.
b. Select the Single Address, Address Range, or Address List option.
c. Type the IP address(es) of the devices to be discovered.
d. Click Add.
4. Click Start Discovery.

Verify discovery and device status

To verify the device was discovered correctly, complete the following steps:
1. In a web browser, log on to the Insight RS Console.
2. In the main menu, select Devices and click the Device Summary tab.

3. Make sure the Status column contains a success icon ( ).

If there is no success icon, determine which column has the problem and consult the Online Help for
troubleshooting information.
4. Verify monitoring:
a. Click the Monitoring & Collections tab, and then click the status icon in the Monitoring column.
b. Verify that the Event Log Monitoring Collector (ELMC) protocol is listed with a status of SUCCESS. If
ELMC protocol is listed as FAILURE, see "ELMC protocol troubleshooting" on page 227 for
troubleshooting steps.

HPE Insight Remote Support 7.10: Monitored Devices Configuration Guide Page 223 of 436
Chapter 17: Configuring VSI OpenVMS Integrity servers

Verify communication between monitored device

and Insight RS
To verify communication between your monitored device and Insight RS, complete the following section:

Verify service event monitoring

The OpenVMS Test event tool is installed when you install the latest version of ELMC. The package includes
two executable files and a readme file that explains how to create a test event. After extracting the ELMC
Package, the test event tool can be found in the following folder on the Hosting Device:
C:\ProgramData\HP\RS\DATA\SWM\LANDINGZONE\ELMC\unzipped\lib\ELMC-testlog-utility-OVMS.zip
The zip package contains two executables:
l testlog.exe_ia64 – This is an Itanium executable. The Itanium image is supported for all versions of VSI
OpenVMS that Insight RS supports.
l testlog.exe_axp – This is an AlphaServer executable.
Copy the ELMC-testlog-utility-OVMS.zip software package to the OpenVMS monitored device, and
extract the contents using the OpenVMS unzip utility. A copy of the OpenVMS unzip utility can be
downloaded from the following web page: h41379.www4.hpe.com/openvms/freeware/freeware.html
Use the Itanium executable for VSI OpenVMS servers. This executable adds a test event to the file
SYS$ERRORLOG:ERRLOG.SYS. If this file does not exist wait until the ERRFMT process creates the file. This
typically can take around 15 minutes for a new error log to be created by the operating system.
To run the Itanium executable, run the following command:
$ run TESTLOG.EXE_IA64
%TESTLOG-I-ADD, Test Event added to SYS$ERRORLOG:ERRLOG.SYS

Verify collections in the Insight RS Console

Collections are not automatically run after discovery. HPE recommends that you manually run a collection
after discovery completes in order to verify connectivity. Run the collection schedule manually on the
Collection Services → Collection Schedules tab. If you do not want to run the collection for all devices in the
collection schedule, add a new schedule that only includes the devices for which you want to verify. For more
information about scheduling collections, see the Insight RS Help.
Configuring your OpenVMS server for Basic Configuration Collections is necessary if your system is covered
by a Proactive services contract. Basic Configuration Collections use the WBEM protocol and require that an
unpriviledged OpenVMS account is configured for the WBEM credentials.
Verify that this collection ran successfully on the Collection Services → Basic Collection Results tab in the
Insight RS Console.
1. Log on to the Insight RS Console.
2. In the main menu, select Collection Services and then click the Basic Collection Results tab.
3. Expand the Server Basic Configuration Collection section.

HPE Insight Remote Support 7.10: Monitored Devices Configuration Guide Page 224 of 436
Chapter 17: Configuring VSI OpenVMS Integrity servers

4. Locate the entry for your device and check the Result column. If the collection was successful, a
success icon appears ( ). If it failed, an error icon appears ( ). If an error icon appears, troubleshoot
the WBEM protocol. See "WBEM protocol troubleshooting" below.

Optional post-configuration steps

Disable WBEM protocol
Once an OpenVMS device is successfully discovered, the ongoing monitoring of the device no longer requires
the WBEM protocol. Ongoing monitoring uses the ELMC protocol rather than the WBEM protocol. As a result,
you can optionally disable the WBEM protocol on the OpenVMS system if there is concern over the
performance impact of running WBEM Services and WBEM Providers on an ongoing basis.

Important: This step is only appropriate under the following conditions:

l You do not have a Proactive services contract. Proactive services contracts require basic
collections, and WBEM is required for basic collections.
l Your OpenVMS system is not in a blade enclosure. Blade enclosures use WBEM providers to
properly identify devices within the enclosure.

If WBEM Services and WBEM Providers is disabled by issuing the command:

$ @SYS$STARTUP:WBEM_SERVICES$SHUTDOWN.COM
some additional customizations are required to the Insight RS configuration in order to avoid impacting the
successful status of the OpenVMS device. Whenever a discovery is performed, the OpenVMS device is
added to the Server Basic Configuration Collection. The Server Basic Configuration Collection task uses the
WBEM protocol to gather details about the OpenVMS device. The Server Basic Configuration Collection task
is then scheduled to run once a month. To avoid running a Basic collection:
1. Disable automatic device discovery. In the Insight RS Console main menu, click Discovery. On the
Configuration tab, clear the Automatically start discovery task every month on day <day> at time
<hh:mm check box. Click Save Configuration.
2. Remove the OpenVMS device from the Server Basic Configuration Collection. In the Insight RS Console
main menu, click Collection Services. On the Collection Schedules tab, select Server Basic
Configuration Collection Schedule. In the assigned devices pane, clear the check box next to the
OpenVMS device. Click Save Devices. Repeat this step any time a discovery is done for the OpenVMS
device.

Troubleshooting
WBEM protocol troubleshooting
Check the following items if you are having issues with discovery.
l Make sure TCPIP IPv6 is not enabled on the OpenVMS server. No process should be found when issuing
this command:
$ show system/process=TCPIP$ND6HOST

HPE Insight Remote Support 7.10: Monitored Devices Configuration Guide Page 225 of 436
Chapter 17: Configuring VSI OpenVMS Integrity servers

l Modify the password in the SYSUAF to the account referenced in the cimuser command so it corresponds to
the password used when issuing the cimuser -a command.
l Confirm that the account referenced by cimuser does not have a flag of disuser in the SYSUAF. Confirm
that you can log into the account.
l Delete the cimuser account on the OpenVMS system with a cimuser –r command and recreate the
cimuser account and password.
l Re-enter the WBEM credentials within the Insight RS Console, making sure that the case matches the
cimuser account and password.
l Confirm that the processes CIMSERVER and CIMDAEMON exist on the OpenVMS server and that they are in
the HIB state. If they are in any other state, contact the HPE Customer Support Center for troubleshooting
assistance.
l Issue the cimprovider –ls command to confirm that all providers listed on the OpenVMS server have a
status of “OK”. If any are in a failed state, stop and restart WBEM Services. If this does not solve the issue
deinstall and reinstall WBEM Services and WBEM Providers.
l Confirm that port 5989 used for the WBEM protocol is not blocked by the firewall.
l Look for CIMSERVER.DMP files on the system disk. They are typically located in SYS$SPECIFIC:[WBEM_
Services]. If you find any current dumps, contact the HPE Customer Support Center for assistance.
l Check to see if data from the WBEM repository can be accessed by issuing the WBEMEXEC command on the
OpenVMS server. Details on this command can be obtained from the article OpenVMS - HPE Insight
Remote Support, How to Locally Test The Namespace Classes Referenced During Discovery. If you see
errors, consider deinstalling and reinstalling WBEM Services and WBEM Providers.
l Restart the services “Pegasus WMI Mapper” and “Pegasus WMIMapper Indications Service” on the
Windows Hosting Device.
l If WBEM Providers is configured, confirm that the OPENVMS_EMS, OPENVMS_UTILD, and WBEMPROV$HOST
processes exist. If these processes are missing, check the following log files in SYS$SPECIFIC:
[WBEMPROVIDERS] for errors:
$ type WBEMPROVIDERS$OPENVMS_EMS.OUT
$ type WBEMPROV$HOST_P.OUT
$ type WBEMPROVIDERS$OPENVMS_UTILD.OUT
l If all other troubleshooting of the WBEM protocol fails to yield results, deinstall and reinstall WBEM
Services and WBEM Providers.
a. Display WBEM logicals to determine where the products are installed:
$ SHOW LOGICAL WBEM*
b. If WBEM Services and WBEM Providers are running, shut them down:
$ @SYS$STARTUP:WBEM_Services$Shutdown.com
c. Run PRODUCT REMOVE commands and continue if any errors occur:
$ PRODUCT REMOVE WBEMPROVIDERS
$ PRODUCT REMOVE WBEMCIM

d. Delete any WBEMPROVIDERS.DIR and WBEM_Services.DIR directories and any files left in
SYS$STARTUP. If the products were installed on the system disk, run the following commands:

HPE Insight Remote Support 7.10: Monitored Devices Configuration Guide Page 226 of 436
Chapter 17: Configuring VSI OpenVMS Integrity servers

$ DELETE/TREE SYS$COMMON:[WBEMPROVIDERS…]*.*;*
$ DELETE/TREE SYS$COMMON:[WBEM_Services…]*.*;*
$ DELETE SYS$COMMON:[000000]WBEMPROVIDERS.DIR;1
$ DELETE SYS$COMMON:[000000]WBEM_Services.DIR;1
$ DELETE/TREE SYS$SPECIFIC:[WBEMPROVIDERS…]*.*;*
$ DELETE/TREE SYS$SPECIFIC:[WBEM_Services…]*.*;*
$ DELETE SYS$SPECIFIC:[000000]WBEMPROVIDERS.DIR;1
$ DELETE SYS$SPECIFIC:[000000]WBEM_Services.DIR;1
$ DELETE SYS$STARTUP:WBEMPROVIDER*.*;*
$ DELETE SYS$STARTUP:WBEM_SERVICES*.*;*
$ DELETE SYS$STARTUP:WBEMPROVIDERS*.*;*

Note that the DELETE/TREE qualifier is only available on OpenVMS 8.4. On an OpenVMS 8.3-1H1
system you will need to reissue the DELETE commands multiple times until all subdirectories and files
are deleted.
e. Delete all WBEM Services and WBEM Providers logicals:
$ DEASSIGN/SYSTEM WBEM_BIN
$ DEASSIGN/SYSTEM WBEM_CIMXX_MOF_DIR
$ DEASSIGN/SYSTEM WBEM_ETC
$ DEASSIGN/SYSTEM WBEM_LIB
$ DEASSIGN/SYSTEM WBEM_MOF_DIR
$ DEASSIGN/SYSTEM WBEM_OPT
$ DEASSIGN/SYSTEM WBEM_REPOSITORY_DIR
$ DEASSIGN/SYSTEM WBEM_SBIN
$ DEASSIGN/SYSTEM WBEM_TMP
$ DEASSIGN/SYSTEM WBEM_VAR
$ DEASSIGN/SYSTEM WBEM_VAR_DATA_DIR
$ DEASSIGN/SYSTEM/EXEC WBEM_PRIMARY_OWNER
$ DEASSIGN/SYSTEM/EXEC WBEM_PRIMARY_OWNER_CONTACT

l If reinstalling WBEM Services and WBEM Providers does not resolve the issue, execute the following
command procedure and provide the saveset output to the HPE Customer Support Center: $
@SYS$COMMON:[WBEMPROVIDERS]WBEM$REPORTER.COM

ELMC protocol troubleshooting

Check the following items if service events are not being received by Insight RS.
l Confirm that the ELMC protocol is working
If WCCPROXY is functioning properly or restarted, a green check mark appears in the OpenVMS device’s
Monitoring & Collections column. If the WCCPROXY process is stopped, a red X will appear in the
OpenVMS device’s Monitoring & Collections column. Insight RS takes about a minute to reflect changes in
status.
Click the Monitoring & Collections tab for more information about the status of the ELMC protocol. Click
the status icon to display a pop-up window with details about the protocol status.
If you see a red X in the Monitoring column, this means that the ELMC protocol is not functioning. The pop-
up window will display the following:

HPE Insight Remote Support 7.10: Monitored Devices Configuration Guide Page 227 of 436
Chapter 17: Configuring VSI OpenVMS Integrity servers

Monitoring Status Description: <openvms_server_fully_qualified_name>.

Protocol: Event Log Monitoring Collection (ELMC)
Service: ELMC Connection
Type: CONNECTIVITY
Status: FAILURE
Description: Failed to connect to EMClient Agent running on host <openvms_server_
fully_qualified_name>.
Detailed: Failed to connect to EMClient Agent running on host <openvms_server_fully_
qualified_name>.
Created: <some date/time>
Last Updated: <some date/time>

Note if the pop-up shows the SNMPv1 protocol, discovery detected the SNMP protocol. The SNMP
protocol cannot be used to monitor OpenVMS devices and this particular entry can be removed by clicking
Clear.
If Insight RS is not able to successfully connect to the OpenVMS system using the ELMC protocol,
continue with the troubleshooting steps below.
l If the ELMC protocol was not discovered, confirm the product WCCPROXY v6.4 is installed on your
OpenVMS system by issuing the following command:
$ product show product wccproxy
If you need to upgrade, the installation media can be found in:
<partition_where_InsightRS_is installed>:\ProgramData\HP\RS\DATA\ELMC
If you do not see the media in this folder, in the Insight RS Console browse to Administrator Settings >
Software Update tab. Click on Event Log Monitoring Collector (ELMC) package. Then on the
Available Version tab, click Install. Copy the media to your OpenVMS server in binary mode and then
issue the following commands when logged into the SYSTEM account:
$ run ELMC_VSI_KIT1_17-MAY-2016_OVMSI64.EXE
$ @wccproxy_install uninstall
$ @wccproxy_install install
l Confirm that the WCCPROXY process is running on the OpenVMS server by issuing the following command
when logged into the SYSTEM account.
$ wccproxy status
If it does not show the WCCProxy is running, issue the command:
$ wccproxy start
l Try restarting the WCCPROXY process on the OpenVMS server by issuing the commands while logged into
the SYSTEM account:
$ wccproxy stop
$ wccproxy start

l Rename SYS$ERRLOG:ERRLOG.SYS. The operating system should recreate one in approximately 15

minutes.
If a new ERRLOG.SYS file is not created confirm that the ERRFMT process exists. If it does not exist it can be
started with the command:

HPE Insight Remote Support 7.10: Monitored Devices Configuration Guide Page 228 of 436
Chapter 17: Configuring VSI OpenVMS Integrity servers

$ @sys$system:startup.com errfmt
l Confirm that port 7920 used by the ELMC protocol is not blocked by the firewall.
l Issue the following command to check if your Insight RS server is communicating with the ELMC process
by examining port 7920. If it is working correctly you should see your Hosting Device mentioned in the
“Remote Host” column as shown in the following example:
$ tcpip show device/port=7920
Port Remote
Device_socket Type Local Remote Service Host
bg285 STREAM 7920 0 *
bg42927 STREAM 7920 59958 1.2.3.4
l Send a test event and examine the Insight RS log file KCT.###.log for evidence on why the events may be
rejected. This is found in:
<partition_where _InsightRS_is_installed>\ProgramData\HP\RS\LOG
In the case that the OpenVMS errlog.sys is corrupt, rename the errlog.sys file and let the operating
system create a new one. Also confirm that the hardware is supported by Insight RS by referring to the
HPE Insight Remote Support Release Notes at www.hpe.com/info/insightremotesupport/docs.
l If no test event is received, examine the time zone of the OpenVMS system, the Hosting Device, and the
time zone defined in Insight RS to see if there is a discrepancy. The time zone within Insight RS can be
determined by browsing to Company Information > Sites > <site_name>.
The time zone of OpenVMS can be determine by issuing the following command:
$ show logical *time*
The time on the OpenVMS system can be determined by issuing the command:
$ show time
l Check that none of the command procedures in WCCPROXY_SPECIFIC:[SPECIFIC.WCCPROXY.DATA] have a
version limit of 32767. If they do, stop WCCPROXY by determining the pid of the WCCPROXY and
issuing STOP/ID=<pid #>. Then delete the files in this directory, and restart WCCPROXY by issuing a
WCCPROXY START command.
l If you continue to have problems with the ELMC protocol, check the log files in WCCPROXY_SPECIFIC:
[SPECIFIC.WCCPROXY.LOGS] for issues.
l If none of the troubleshooting steps shown above have solved the issue, deinstall and reinstall ELMC
(WCCPROXY) on the OpenVMS server:
$ run ELMCV64BL1KIT1_21-JUN-2012_OVMSI64.EXE
$ @wccproxy_install uninstall
$ @wccproxy_install install

l If test events are not working for any OpenVMS system, confirm that ELMC was installed on the Insight
RS server. WCCPROXY 6.4 software should appear in the Control Panel → All Control Panel Items →
Programs and Features. If WCCPROXY is missing, log into the Insight RS Console and navigate to
Administrator Settings → Software Updates. Click on Event Log Monitoring Collector (ELMC), and
on the Available Version tab, click Install. Once the WCCPROXY software is installed, make sure that
the WCCPROXY service is started.

HPE Insight Remote Support 7.10: Monitored Devices Configuration Guide Page 229 of 436
Chapter 17: Configuring VSI OpenVMS Integrity servers

l If test events are not working for any OpenVMS system, determine if Insight Remote Support Advanced
(RSA) A.05.80 or below is installed on the same server running Insight RS 7.x. If Insight RSA A.05.08 or
below appears in Control Panel → All Control Panel Items → Programs and Features, this software
should be removed.

Entitlement troubleshooting
Check the following items if you are having entitlement issues with your OpenVMS system.
l If the OpenVMS system does not pass the entitlement check, make sure you have the correct serial
number and product number specified on the contract.
l If the correct serial number and product number have been defined for the device and the entitlement check
continues to fail, confirm that the “Hosting Device Health” has a green check. This can be found in the
header of the Insight RS Console. If it shows a red x, click on “Hosting Device Health” for more details.
l Try stopping the following Window services in this order: 1) “HPE Insight Remote Support” and 2) “HPE
Insight RS Event Receiver” and then restarting them in that order.
l Confirm that port 443 used to communicate with the HPE backend is not blocked by the firewall.
Additional security firewall requirements are detailed in the HPE Insight Remote Support Security White
Paper at www.hpe.com/info/insightremotesupport/docs.
l Open up a browser on the Hosting Device and confirm if you can access this web page:
https://api.support.hpe.com/v1/version/index.html
l Issue a nslookup command and confirm that api.support.hpe.com can be resolved.
If api.support.hpe.com cannot be resolved by your DNS server, then add this address to the Windows
host file on the Hosting Device.
l Lack of connectivity to the HPE backend can sometimes be caused by issues with the HPE backend. For
additional assistance troubleshooting the lack of connectivity, contact the HPE Customer Support.

HPE Insight Remote Support 7.10: Monitored Devices Configuration Guide Page 230 of 436
 Chapter 18: Configuring HPE OpenVMS
AlphaServers
Important: Configuration collections for HPE OpenVMS on AlphaServer are not available except
when the HPE OpenVMS server is part of a SAN collection.

Important: HPE only provides limited remote support for customers using HPE Alpha servers. As
with standard support, Insight Remote Support version 7.x will attempt to discover these products
as remotely monitored HPE products and send information about failure events to HPE.
However, if there are issues with the operation of the remote monitoring features of Insight Remote
Support version 7.x for these specific products, including the remote discovery or the reporting of
failure events to HPE, then HPE will resolve such issues in a commercially reasonable manner but
without guarantee of an immediate response or a resolution. If a failure event is successfully
received at HPE, it is managed according to the support level agreement.

Fulfill configuration requirements

To configure your HPE OpenVMS servers to be monitored by Insight RS, complete the following sections:
Table 18.1 HPE OpenVMS server configuration steps
Task Complete?

Make sure Insight RS supports your OpenVMS server by checking the HPE Insight Remote
Support Release Notes.

Install and configure ELMC for HPE OpenVMS on the HPE OpenVMS server.

Enable and configure SNMP.

Add the SNMP protocol to the Insight RS Console.

Discover the HPE OpenVMS server in the Insight RS Console.

Configure SAN collections.

Send a test event to verify connectivity between your HPE OpenVMS server and Insight RS.

Manually run collections to verify they are gathered.

Install and configure communication software on

servers
To configure your monitored devices, complete the following sections:

Fulfill ELMC system requirements

HPE OpenVMS monitored devices must meet the following requirements before ELMC is installed. In
clusters, minimum requirements apply to each node in the cluster.

HPE Insight Remote Support 7.10: Monitored Devices Configuration Guide Page 231 of 436
Chapter 18: Configuring HPE OpenVMS AlphaServers

Fulfilling hardware and software requirements

l Processor architecture: HPE AlphaServer
l Operating system: HPE OpenVMS AlphaServer — 7.3-2 or higher
l Minimum 20,000 blocks free disk space.
l Connectivity: TCP/IP must be installed and running.
The ability to resolve the local host name into an IP address must be enabled. Otherwise, the Director
cannot handle ELMC message traffic correctly and fails to start.
ELMC officially supports only one TCP/IP product for HPE OpenVMS: HPE TCP/IP Services for HPE
OpenVMS, version 5.4 or higher.

Note: Other TCP/IP products may work as is, so the Insight RS installation always completes
regardless of what, if any, TCP/IP product is installed.

l LOCALHOST entry: For ELMC to operate correctly, the LOCALHOST entry must be defined in the HPE
OpenVMS TCP/IP HOSTS database. It is defined correctly by default, but it can be removed, which
causes Insight RS to fail.
Type the following command:
$ TCPIP SHOW HOST /LOCAL
Look for LOCALHOST, which should have an IP address of 127.0.0.1. If LOCALHOST does not appear in
the list, type the following command:
$ TCPIP SET HOST LOCALHOST /ADDRESS=127.0.0.1 /ALIAS="localhost"
Type a ping command to verify that LOCALHOST was added:
$ TCPIP PING LOCALHOST
PING LOCALHOST (127.0.0.1): 56 data bytes
64 bytes from 127.0.0.1: icmp_seq=0 ttl=64 time=0 ms
64 bytes from 127.0.0.1: icmp_seq=1 ttl=64 time=0 ms
64 bytes from 127.0.0.1: icmp_seq=1 ttl=64 time=0 ms

After verifying that LOCALHOST responds to the ping command, you can use Ctrl-C or Ctrl-Y to stop pinging.
l System firmware: The prerequisite system firmware supports the logging of events according to the FRU
Table Version 5 Specification, which is required for Insight Remote Support FRU configuration tree
processing.
All DSxx and ES40 systems must have firmware V5.7–4 or higher.
In general, users should take advantage of the latest improvements by obtaining the most recent firmware
version available for their platforms.

Fulfilling required permissions and access

Grant permissions required to install ELMC

To install or uninstall ELMC, the user needs all of the following HPE OpenVMS privileges:

HPE Insight Remote Support 7.10: Monitored Devices Configuration Guide Page 232 of 436
Chapter 18: Configuring HPE OpenVMS AlphaServers

l ALTPRI
l BUGCHK
l BYPASS
l CMKRNL
l DIAGNOSE
l IMPERSONATE
l NETMBX
l OPER
l SYSLCK
l SYSPRV
l TMPMBX
HPE recommends that you install ELMC using the SYSTEM account.

Grant permissions required to run ELMC

To execute any ELMC commands, the user needs all of the following OpenVMS privileges. Note that these
are a subset of the privileges required to install, upgrade or uninstall ELMC:
l ALTPRI
l BUGCHK
l CMKRNL
l DIAGNOSE
l IMPERSONATE
l NETMBX
l SYSPRV
l TMPMBX

Heterogeneous cluster instructions

A heterogeneous cluster is a cluster with multiple system disks. Before beginning the ELMC installation in an
OpenVMS cluster with multiple system disks, check to see if the system disks are mounted cluster-wide. To
avoid potential problems, all remotely mounted system disks should be dismounted prior to installing ELMC
on an OpenVMS heterogeneous cluster. After the install is done, the system administrator can remount the
disks. Failure to perform this step can result in the following:
l When user has a heterogeneous cluster where the system disks are mounted cluster-wide, all of the ELMC
[root.SYSCOMMON.HP.NODES.nodename] directories will be created on the system disk where the install
was performed. No directories are created on the other system disks.
l The PCSI database will only be updated on the system disk where the installation was performed. The
WCCProxy process will be running on other cluster members with different system disks; however, a
PRODUCT SHOW PRODUCT will not provide any indication that the product was actually installed.

HPE Insight Remote Support 7.10: Monitored Devices Configuration Guide Page 233 of 436
Chapter 18: Configuring HPE OpenVMS AlphaServers

l On every node of the cluster the ELMC WCCPROXY process runs the images from the system disk where
the installation was performed. This may be problematic if the other system disks are running different
versions of OpenVMS or have different operating system patches installed.
l If the system disk where the installation was performed is unavailable due to a planned shutdown or crash,
the ELMC application will fail to run on the remaining nodes of the cluster. This means that no monitoring
will occur until the system disk where the installation was performed becomes available again.
The following example illustrates the issue: assume the user has a 2 node cluster with one system running
OpenVMS 8.3 and another system running OpenVMS 8.4. If ELMC is installed on the system running
OpenVMS 8.3, the system running OpenVMS 8.4 will have a WCCProxy process running images from the
OpenVMS 8.3 system disk, which will be using library modules from the OpenVMS 8.4 system disk. This
combination of images and library modules may cause issues. If the user examines the PCSI database of the
OpenVMS 8.4 system disk, there will be no evidence that ELMC is installed and running on this system. The
ELMC root for the OpenVMS 8.4 system will be created on the OpenVMS 8.3 system disk. If the OpenVMS
8.3 system is shutdown, the ELMC application on the OpenVMS 8.4 system will stop functioning until the
OpenVMS 8.3 system is rebooted.

Archiving and cleaning the error log

After Insight Remote Support is installed on the Hosting Device, it uses ELMC to analyze all events stored in
the error log, which can result in high CPU usage over an extended period. To control this operation, you are
encouraged to archive and clean the error log before installing. This reduces the size of the log and the time
required for the initial scan.
Follow these guidelines for cleaning the error log. If ELMC is installed and running when you clean the log, you
do not need to stop and restart the Director process. Also, do not stop and restart the ERRFMT system event
logging process.
The default error log, typically SYS$SYSROOT:[SYSERR]ERRLOG.SYS, increases in size and remains on the
system disk until the user explicitly renames or deleted it. When either occurs, the system creates a new,
clean error log file after about 15 minutes.

Caution: After renaming or deleting the existing log, do not install ELMC until the new default log is
present.

If you rename the log, the saved log can be analyzed at a later time.
Aside from starting with a clean log before installing Insight Remote Support, you may want to perform regular
maintenance on the error log. One method is to rename errlog.sys on a monthly basis. For example, you
might rename errlog.sys to errlog.old at 00:01 on the first day of every month. To free space on the
system disk, you then can back up the renamed version to a different volume and delete the file from the
system disk.

Confirm SYSMAN is functioning cluster-wide

The installation of ELMC makes use of the SYSMAN utility. Confirm that SYSMAN is functioning correctly on
every node of a cluster before attempting ELMC installation. Issue the following command to confirm that the
SHOW DEVICE SYS$SYSDEVICE: command completes normally for all nodes in the cluster.
$ MCR SYSMAN
SYSMAN> SET ENV/CLUSTER
SYSMAN> DO SHOW DEVICE SYS$SYSDEVICE:

HPE Insight Remote Support 7.10: Monitored Devices Configuration Guide Page 234 of 436
Chapter 18: Configuring HPE OpenVMS AlphaServers

How to remove ELMC

If you have an older version of ELMC installed, remove this before installing the latest version of ELMC. You
can determine if you have an older version by issuing the following command.
$ PRODUCT SHOW PRODUCT WCCPROXY
If the version of WCCPROXY is anything other than V6.4, ELMC needs to be upgraded.
If the cluster has multiple system disks, check to see if the system disks are mounted cluster-wide. To avoid
potential problems, all remotely mounted system disks should be dismounted prior to removing ELMC on an
OpenVMS heterogeneous cluster.
1. Stop the WCCPROXY process:
l If this is a standalone system, issue the following command:
$ wccproxy stop
l If this is a cluster, stop WCCPROXY processes by issuing the following commands:
$ mcr sysman
SYSMAN> set env/cluster
SYSMAN> do wccproxy stop

2. Confirm no WCCPROXY processes exist by issuing the following command:

$ show system/process=wccproxy/cluster
If any WCCPROXY processes exist that could not be terminated, issue a STOP/ID=<pid_of_wccproxy_
process> on the system with the WCCPROXY process.
3. Find the WCCPROXY_INSTALL.COM procedure located in the installation directory of ELMC by issuing the
following command:
$ directory WCCPROXY_HOME:[*...]wccproxy_install.com
Directory WCCPROXY_COMMON:[COMMON.WCCPROXY.BIN]
WCCPROXY_INSTALL.COM;1
Total of 1 file.

4. If the WCCPROXY_HOME logical points to a nonexistent disk, then search the system disk for the WCCPROXY_
INSTALL.COM procedure.
$ directory sys$sysdevice:[*...]wccproxy_install.com
5. ELMC can be removed by executing the WCCPROXY_COM procedure found in the ELMC installation
directory.
$ @WCCPROXY_COMMON:[COMMON.WCCPROXY.BIN]wccproxy_install.com "uninstall"
If no WCCPROXY_INSTALL.COM procedure can be located, then use the v6.4 WCCPROXY_INSTALL.COM
procedure.

Verify serial number

On AlphaServer GS80, GS160, and GS320 systems, verify the serial number as directed before installing
ELMC on the monitored device.

HPE Insight Remote Support 7.10: Monitored Devices Configuration Guide Page 235 of 436
Chapter 18: Configuring HPE OpenVMS AlphaServers

Certain GS80, GS160, and GS320 systems did not have their system serial number set correctly at the
factory, and Insight RS only functions when the serial number is set correctly. Affected serial numbers will
begin with the letter "G."
At the SRM console firmware prompt (the prompt when you first power the system on), check the serial
number with the following command:
show sys_serial_num
The serial number shown should match the actual serial number on the model/serial number tag located in the
power cabinet. If necessary, change the serial number with the following command:
set sys_serial_num
Type the six-character serial number provided on the tag in the power cabinet.

Note: This issue also can arise when multiple AlphaServers are ordered, because the factory may
assign an identical serial number to each system. In this scenario, Insight RS does not work
correctly because it requires that each AlphaServer have a unique number. If this is the case,
uniquely identify each AlphaServer by appending –1, –2, –3, and so on, to the serial numbers when
you use the set sys_serial_num command.

Note: Multiple partitions on the same AlphaServer always have the same serial number because
they reside on the same machine. There are no Insight RS conflicts in this case, so do not attempt
to assign unique serial numbers to different partitions on the same machine.

Install the ELMC HPE OpenVMS Software Package on the

Monitored Device
Check if ELMC is already installed with the command: product show product wccproxy.
If this returns 0 items found then ELMC has never been installed. If the version of WCCPROXY is anything
other than V6.4, ELMC needs to be upgraded. For how to uninstall older versions of ELMC, see "How to
remove ELMC" on the previous page.
To install the ELMC software package, complete the following steps:
1. In the Insight RS Console, navigate to the Administrator Settings → Software Updates tab and select
the Event Log Monitoring Collector (ELMC) software package.
2. On the Available Version tab, click Download.
3. When the download completes, click Install. The ELMC packages are placed in the %HP_RS_
DATA%\SWM\LANDINGZONE\ELMC folder. This folder defaults to
C:\ProgramData\HP\RS\DATA\SWM\LANDINGZONE\ELMC.

Note: The ProgramData folder is a hidden folder. To view this folder, set the folder options to
show hidden folders.

4. Copy the HPE OpenVMS AlphaServer ELMC software package (ELMCV64BL1KIT1_JUN-21-2012_

OVMSALP.EXE) to the HPE OpenVMS monitored device. Place the .exe file in an empty directory. Make
sure that:

HPE Insight Remote Support 7.10: Monitored Devices Configuration Guide Page 236 of 436
Chapter 18: Configuring HPE OpenVMS AlphaServers

l There are no other kits in the directory, especially other versions of ELMC kits.
l There are no old ELMC or WCCProxy files in the directory left over from previous operations.
5. Extract the ELMC installation files:
$ run ELMCV64BL1KIT1_JUN-21-2012_OVMSALP.EXE
6. Run the wccproxy_install.com command procedure to either upgrade or install ELMC. Then follow the
prompts.
l Run the following command to install ELMC on the system disk:
$ @wccproxy_install.com "install"
l Run the following command to install ELMC on a disk other than the system disk:
$ @wccproxy_install.com "install" "<installation directory>"
Example:
$ @wccproxy_install.com "install" "COMMON$DISK:[ELMC]"
The installation asks the following question:
Use the following command to install standalone ELMC/Proxy kit
@WCCPROXY_INSTALL.COM INSTALL masterwebes <installation_path> Do you want to
continue?[NO]:

Respond YES to this question.

Note: The command executes the DCL script wccproxy_install.com in the current directory.
Do not run the product install wccproxy command that would normally be used to install a
PCSI-based product. This command aborts and prompts you to run the wccproxy_
install.com script instead. Set your default directory to the one containing the file wccproxy_
install.com, created by extracting the ELMC .exe file in the previous step.

When the DCL prompt ($) returns, the install has finished and the ELMC (WCCProxy) process will be
running.
7. Add the WCCPROXY STOP command to SYS$MANAGER:SYSHUTDWN.COM command procedure.
No command has to be added to the site specific boot command procedure since the installation will
have added the following to the SYSMAN utility:
SYSMAN> startup show file WCCPROXY$STARTUP.COM
%SYSMAN-I-COMFIL, contents of component database on node XXXX
Phase Mode File
------------ ------ ---------------------------------
LPMAIN DIRECT WCCPROXY$STARTUP.COM

WCCPROXY command verb reference

The installation of ELMC adds the WCCPROXY command to the DCLTABLES of the OpenVMS system.
l WCCPROXY START
This command starts the WCCPROXY process.

HPE Insight Remote Support 7.10: Monitored Devices Configuration Guide Page 237 of 436
Chapter 18: Configuring HPE OpenVMS AlphaServers

l WCCPROXY STOP
This command stops the WCCPROXY process.
l WCCPROXY STATUS
This command shows the status of the WCCPROXY process.

Install ELMC when a new system is added to an existing

ELMC installation
If the cluster has multiple system disks, check to see if the system disks are mounted clusterwide. To avoid
potential problems, all remotely mounted system disks should be dismounted prior to installing ELMC on an
OpenVMS heterogeneous cluster. After the install is done, the system administrator can remount the disks.
Next determine if the new cluster member boots off a system which already has ELMC installed.
$ PRODUCT SHOW PRODUCT WCCPROXY
If this returns, 0 items found then ELMC has never been installed on this system disk.
l If ELMC is not installed, install it by executing the following command in a directory that contains the
ELMC installation kit. For where to obtain the ELMC kit, see "Install the ELMC HPE OpenVMS Software
Package on the Monitored Device" on page 236.
$ @wccproxy_install.com "install"
l If ELMC is already installed on the system disk uninstall and reinstall ELMC. Complete the following in a
directory that contains the ELMC installation kit:
a. Remove WCCPROXY:
$ @wccproxy_install.com "uninstall"
b. Install WCCPROXY:
$ @wccproxy_install.com "install"

Enable and configure SNMP

Confirm TCP/IP IP address and name resolution is functioning
Before configuring SNMP, confirm that TCP/IP is correctly configured. Make sure that you are able to ping by
IP address, system name, and fully qualified name from the Hosting Device to the OpenVMS system and
from the OpenVMS system to the Hosting Device. If the address or name is not found, add it to the local host
file or to the DNS server.
If your OpenVMS system has both a DNS TCP/IP cluster alias name and node specific name that refer to the
same IP address, add the fully qualified name of the node specific name to the local host file of the Hosting
Device.

Determine if the SNMP service is enabled

You can determine if SNMP is enabled by issuing the command:
$ TCPIP SHOW SERVICE SNMP

HPE Insight Remote Support 7.10: Monitored Devices Configuration Guide Page 238 of 436
Chapter 18: Configuring HPE OpenVMS AlphaServers

l If you see the below output, this means the TCP/IP service is defined and enabled. Proceed to "Configure
read community string" below.
$ TCPIP SHOW SERVICE SNMP
Service Port Proto Process Address State
SNMP 161 UDP TCPIP$SNMP 0.0.0.0 Enabled

l If you see the below output, this means SNMP is not defined or configured. Proceed to "Enable SNMP"
below.
$ TCPIP SHOW SERVICE SNMP
%TCPIP-W-NORECORD, information not found
-RMS-E-RNF, record not found

Enable SNMP
When the SNMP service does not exist it can be enabled by invoking SYS$MANAGER:TCPIP$CONFIG.COM
$ @SYS$MANAGER:TCPIP$CONFIG.COM
Choose option 3 for server components, then choose option 18 for SNMP.
If TCPIP$CONFIG.COM displays that the SNMP service is already enabled, then use the configuration tool to
disable it and re-enable it. Sometimes the display can get out of sync with reality due to commands issued at
the TCPIP prompt instead of in the TCPIP$CONFIG utility.

Configure read community string

Once the SNMP service is enabled, a read community string needs to be configured which corresponds to a
read community string on the Hosting Device. To confirm what the read community string is expected by the
Hosting Device, check the security tab on the Window service named SNMP Service.
1. Issue the following command on the OpenVMS server to see what community strings are defined:
$ TCPIP SHOW CONFIGURATION SNMP/FULL
2. If the read community string is missing on the OpenVMS system, it can be added by issuing the
command:
$ TCPIP SET CONFIGURATION SNMP /COMMUNITY=”name_of_community_string”/type=read
This command will create the read community string with an address of 0.0.0.0 which means that any
devices in your network will have read access using this community string. If you want to restrict this to
just the Hosting Device then issue the following command:
$ TCPIP SET CONF SNMP /COMMUNITY=”<name_of_community_string>”/type=read/address=
(127.0.0.1, <ip_address_of_hosting_device>)
Note that it is important to include the loop back address on the community string since the local system
needs the ability to access to this community string for SNMP to function correctly.
Also note that the community string is case sensitive so it must exactly match what you see on the
Hosting Device.
3. Restart SNMP after making any configuration change:
$ @SYS$MANAGER:TCPIP$SNMP_SHUTDOWN.COM
$ @SYS$MANAGER:TCPIP$SNMP_STARTUP.COM

HPE Insight Remote Support 7.10: Monitored Devices Configuration Guide Page 239 of 436
Chapter 18: Configuring HPE OpenVMS AlphaServers

Configure firewall and port settings

Table 18.2 HPE OpenVMS Connectivity - Firewall/Port Requirements
Protocol Ports Source Destination Function Optional

ICMP N/A Hosting Monitored Provides system reachability (ping) check during Required
Device Systems system discovery and before other operations.

TCP 7920 Hosting Monitored The Insight RS ELMC (WCCProxy) process Required
Device Systems communicates with the Director on this port. This is
a proprietary protocol. Any connections that
exchange username and passwords use SSL. Not
all connections are SSL.

TCP 7905 Monitored Hosting Secure HTTP (HTTPS) port used by the listener Required
Systems Device running in the Director's Web Interface. The
monitored host connects to the Hosting Device on
this port (e.g. https://<hostname>:7905).

UDP 161 Hosting Onboard SNMP. This is the standard port used by SNMP Required
Device Administrator agents on monitored systems. The Hosting Device
sends requests to devices on this port.

UDP 162 Onboard Hosting SNMP Trap. This is the port used by Insight RS to Required
Administrator Device listen to SNMP traps.

Add protocol credentials and start discovery

To discover your monitored devices, complete the following sections:

Create an SNMPv1 protocol credential in the Insight RS

Console
If your device's SNMP community string is set to public and your community access mode is read only,
Insight RS automatically associates an SNMPv1 protocol with your device. If you use a different community
string or use a nonstandard port, you must create an SNMPv1 protocol credential in the Insight RS Console.
To configure SNMPv1 in the Insight RS Console, complete the following steps:
1. In a web browser, log on to the Insight RS Console.
2. In the main menu, select Discovery and click the Credentials tab.
3. From the Select and Configure Protocol drop-down list, select Simple Network Management Protocol
Version 1, V2C (SNMPv1, SNMPv2C).
4. Click New. The New Credential dialog box appears.
5. Type the Community String you have configured on your device.
6. Click Add.
Insight RS creates the protocol credential and it appears in the credentials table.

HPE Insight Remote Support 7.10: Monitored Devices Configuration Guide Page 240 of 436
Chapter 18: Configuring HPE OpenVMS AlphaServers

Discover the device in the Insight RS Console

To discover the device from the Insight RS Console, complete the following steps:
1. In a web browser, log on to the Insight RS Console.
2. In the main menu, select Discovery and click the Sources tab.
3. Expand the IP Addresses section and add the IP address for your device:
a. Click New.
b. Select the Single Address, Address Range, or Address List option.
c. Type the IP address(es) of the devices to be discovered.
d. Click Add.
4. Click Start Discovery.
5. Enter Serial Number and Product Number:
a. In the Insight RS Console, navigate to Devices and click the OpenVMS Device Name.
b. Expand the Hardware section, type the serial number in the Override Serial Number field and the
product number in the Override Product Number field and click Save Changes.
c. Expand the Status section and click Discover Device.
d. Click Ok when the confirmation message appears.

Verify discovery and device status

To verify the device was discovered correctly, complete the following steps:
1. In a web browser, log on to the Insight RS Console.
2. In the main menu, select Devices and click the Device Summary tab.

3. Make sure the Status column contains a success icon ( ).

If there is no success icon, determine which column has the problem and consult the Online Help for
troubleshooting information.
4. Verify monitoring:
a. Click the Monitoring & Collections tab, and then click the status icon in the Monitoring column.
b. Verify that the Event Log Monitoring Collector (ELMC) protocol is listed with a status of SUCCESS. If
ELMC protocol is listed as FAILURE, see "ELMC protocol troubleshooting" on page 247 for
troubleshooting steps.

Configure SAN configuration collections

Configuring an HPE OpenVMS device for a SAN Configuration Collection is only necessary if your system is
covered by a SAN assessments contract. You can use either TELNET or SSH. To configure SAN
Collections, complete the following steps:

HPE Insight Remote Support 7.10: Monitored Devices Configuration Guide Page 241 of 436
Chapter 18: Configuring HPE OpenVMS AlphaServers

1. Determine if SSH or TELNET service is enabled on HPE OpenVMS system:

l $ TCPIP SHOW SERVICE SSH
Service Port Proto Process Address State
SSH 22 TCP TCPIP$SSH 0.0.0.0 Enabled

l $ TCPIP SHOW SERVICE TELNET

Service Port Proto Process Address State
TELNET 23 TCP not defined 0.0.0.0 Enabled

2. Run SYS$MANAGER:TCPIP$CONFIG.COM to create an SSH or TELNET service:

l When the SSH service does not exist, enable it with the following:
$ @SYS$MANAGER:TCPIP$CONFIG.COM
l When the TELNET service does not exist, enable it with the following:
$ @SYS$MANAGER:TCPIP$CONFIG.COM
3. Make sure to grant the privileges CMKRNL, SYSLCK, NETMBX, and TMPMBX to the OpenVMS account used to
run SAN Collections. This account is also used in the SSH or TELNET named credential below. These
privileges are required because the SAN Collection issues two OpenVMS commands (ANALYZE/SYSTEM
and PRODUCT SHOW HISTORY) which require these additional privileges.
4. If using SSH, edit the HPE OpenVMS SSH server configuration file. After enabling and starting the SSH
service, edit the HPE OpenVMS SSH server configuration file TCPIP$SSH_DEVICE:
[TCPIP$SSH.SSH2]SSHD2_CONFIG. If the AllowedAuthentications parameter is defined, make sure the
AllowedAuthentications parameter includes password. Also make sure the DenyHosts parameter
does not include a reference to the Windows server.
5. In the Insight RS Console, define a SSH or TELNET Named Credential:
a. In the main menu of the Insight RS Console, select Company Information and click the Named
Credentials tab.
b. Click Add New Credential.
c. Enter a Credential Name similar to OpenVMS-ssh or OpenVMS-telnet.
d. From the Protocol drop-down list, select Secure Shell (SSH) or Telnet depending on which
protocol you are configuring.
e. Enter the Username and Password of a valid HPE OpenVMS account. You can use the same
username and password that you used for the WBEM Named Credential. Note that the user
credential can be an unprivileged account.
f. Click Save.
6. Add the SSH or TELNET protocol to the Insight RS HPE OpenVMS device:
a. In the main menu of the Insight RS Console, select Devices. In the Devices pane, search for the
HPE OpenVMS server name.
b. Click the device name, then the Credentials tab.
c. In the Credentials Information pane, expand the SSH or TELNET protocol you want to add. If
necessary, select the Configure additional Protocols check box to view all available protocols.
d. To add SSH protocol, click on Secure Shell (SSH) → Named Credential. To add the TELNET

HPE Insight Remote Support 7.10: Monitored Devices Configuration Guide Page 242 of 436
Chapter 18: Configuring HPE OpenVMS AlphaServers

protocol click on Telnet → Named Credential. Select the Named Credential created earlier.
e. Click on the Device tab, then click Discover Device.
7. Configure San Configuration Collection Schedule:
a. In the main menu of the Insight RS Console, select Collection Services.
b. Click the Collection Schedules tab.
c. In the List of Collection Schedules pane, select the SAN Configuration Collection Schedule.
d. Assign devices in the assigned devices pane. The default view shows devices assigned to the
schedule. To show additional devices, click the Not Assigned to this Schedule or All Devices
options. To show devices in a specific device group, select a device group from the Filter by device
group drop-down list. To search for a specific device, type the device name into the Search box.
The table displays the devices based on your filter and search criteria.
Add your HPE OpenVMS device to the SAN Configuration Collection Schedule by selecting the
check box next to the device in the devices table.
e. Click Save Devices.
f. Click Run Now.
8. Confirm the SAN Configuration Collection Schedule ran successfully; see "Verify collections in the
Insight RS Console" on the next page.

Verify communication between monitored device

and Insight RS
To verify communication between your monitored device and Insight RS, complete the following section:

Verify service event monitoring

The OpenVMS Test event tool is installed when you install the latest version of ELMC. The package includes
two executable files and a readme file that explains how to create a test event. After extracting the ELMC
Package, the test event tool can be found in the following folder on the Hosting Device:
C:\ProgramData\HP\RS\DATA\SWM\LANDINGZONE\ELMC\unzipped\lib\ELMC-testlog-utility-OVMS.zip
The zip package contains two executables:
l testlog.exe_axp – This is an AlphaServer executable. The AlphaServer image is supported for HPE
OpenVMS 8.2, 8.3, and 8.4.
l testlog.exe_ia64 – This is an Itanium executable.
Copy the ELMC-testlog-utility-OVMS.zip software package to the OpenVMS monitored device, and
extract the contents using the OpenVMS unzip utility. A copy of the OpenVMS unzip utility can be
downloaded from the following web page: h41379.www4.hpe.com/openvms/freeware/freeware.html
Use the AlphaServer executable for AlphaServer HPE OpenVMS servers. This executable adds a test event
to the file SYS$ERRORLOG:ERRLOG.SYS. If this file does not exist wait until the ERRFMT process creates the file.
This typically can take around 15 minutes for a new error log to be created by the operating system.
To run the AlphaServer executable, run the following command:

HPE Insight Remote Support 7.10: Monitored Devices Configuration Guide Page 243 of 436
Chapter 18: Configuring HPE OpenVMS AlphaServers

$ run TESTLOG.EXE_axp
%TESTLOG-I-ADD, Test Event added to SYS$ERRORLOG:ERRLOG.SYS

Verify collections in the Insight RS Console

Collections are not automatically run after discovery. HPE recommends that you manually run a collection
after discovery completes in order to verify connectivity. Run the collection schedule manually on the
Collection Services → Collection Schedules tab. If you do not want to run the collection for all devices in the
collection schedule, add a new schedule that only includes the devices for which you want to verify. For more
information about scheduling collections, see the Insight RS Help.
Configuring your OpenVMS server for SAN Configuration Collections is necessary if your system is covered
by a SAN assessments contract. SAN Configuration Collections use the TELNET or SSH protocol and
require that an OpenVMS account with the privileges CMKRNL, SYSLCK, NETMBX, and TMPMBX are configured for
the TELNET or SSH credentials.
To verify the collection ran successfully, complete the following steps:
1. Log on to the Insight RS Console.
2. In the main menu, select Devices.
3. Click the Monitoring & Collections tab, and search for the device you want to view.
4. View the collection status in the SAN Collections column. If the collection was successful, a success
icon appears ( ). If it failed, an error icon appears ( ). If an error icon appears, see "Telnet protocol
troubleshooting" on page 252 or "SSH protocol troubleshooting" on page 249.
If the following error is seen when you click the error icon, it means that Insight RS is unable to detect the
SSH or TELNET protocols on your OpenVMS system.
Protocol: Secure Shell (SSH)
Service: SAN_Configuration_Collection
Type: DEPENDENCY_CHECK
Status: FAILURE
Description: A valid connection could not be made to: <openvms_server_fully_
qualified_name>
Detailed: Please check the credentials for this device. If these credentials are from
a credential group, determine if other devices can use the credentials successfully.
If this device uses certificates for authentication, regenerate the certificate.
Created: Tuesday, June 09, 2015 12:35:09 PM
Last Updated: Tuesday, June 09, 2015 12:35:09 PM
CollectionView Collection

If the SAN Collection was successful, verify that the collection XML file contains no DCL errors. If errors
exist, the collection was unsuccessful in gathering all of the required data.

Note: This procedure only applies if you have enabled local storage of collections. For details, see
the Online Help.

1. In the Insight RS Console, on the Devices → Monitoring & Collections tab, click the icon.
2. In the collection description, click View Collection.

HPE Insight Remote Support 7.10: Monitored Devices Configuration Guide Page 244 of 436
Chapter 18: Configuring HPE OpenVMS AlphaServers

3. In the Attachments section, click Retrieve File.

4. Click Download File.
5. Open the file in your browser or an XML editor, and verify there are no DCL errors. If you see errors,
troubleshoot the protocol you are using. See "Telnet protocol troubleshooting" on page 252 or "SSH
protocol troubleshooting" on page 249.

Optional post-configuration steps

Disable SNMP service
If due to security requirements your site does not permit SNMP to be left running, this service can be disabled
once the Insight RS discovery is complete.
$ TCPIP DISABLE SERVICE SNMP
$ @SYS$MANAGER: TCPIP$SNMP_SHUTDOWN.COM

Troubleshooting
SNMP protocol troubleshooting
l Confirm that SNMP ports 161 and 162 are not blocked by the firewall.
l If the SNMP protocol cannot be discovered, confirm that the addresses on the OpenVMS READ Community
string are correctly defined. The address should either be 0.0.0.0 or 127.0.0.1 (the IP address to the
Hosting Device). You can examine the SNMP configuration by issuing the following command: $ tcpip
show config snmp/full.
l Confirm that the Named Credential read community string specified in Insight RS is identical to the
community string defined on the OpenVMS server and in the SNMP Service Security tab on the Hosting
Device. Note that the community string is case sensitive.
l If the community string is correct, run the following command to confirm that the SNMP service is enabled
on the OpenVMS server:
$ tcpip show service snmp
Service Port Proto Process Address State
SNMP 161 UDP TCPIP$SNMP 0.0.0.0 Enabled

l If the service is disabled issue the command:

$ tcpip enable service SNMP
l If the SNMP service stays disabled there is a possibility that there is a logic error in
SYS$MANAGER:SYLOGIN.COM or SYS$SYSDEVICE:[TCPIP$SNMP]LOGIN.COM. Evidence that this is the root
cause can be found in SYS$SYSDEVICE:[TCPIP$SNMP]TCPIP$SNMP_RUN.LOG. The following is an example
of what the log file will look like when there are errors:
%DCL-W-IVOPER, unrecognized operator in expression - check spelling and syntax \.0.\
%DCL-W-UNDSYM, undefined symbol - check validity and spelling \AUTH\
%DCL-W-IVOPER, unrecognized operator in expression - check spelling and syntax \.0.\
TCPIP$SNMP job terminated at 8-AUG-2009 21:01:06.94

HPE Insight Remote Support 7.10: Monitored Devices Configuration Guide Page 245 of 436
Chapter 18: Configuring HPE OpenVMS AlphaServers

To eliminate this problem, add the following command to the beginning of SYLOGIN.COM:
$ if f$mode() .eqs. "NETWORK" then exit
l Stop and restart the OpenVMS SNMP service to make sure that the configuration displayed is actually in
effect:
$ @sys$startup:tcpip$snmp_shutdown.com
$ @sys$startup:tcpip$snmp_startup.com

l If the SNMP service will not start on the OpenVMS server, confirm that the TCPIP$SNMP account shows
that its UIC identifier in the SYSUAF is TCPIP$SNMP. Also confirm the account does not have the disuser
flag. The following is an example of a properly defined TCPIP$SNMP account:
$ mcr authorize show tcpip$snmp
Username: TCPIP$SNMP Owner: TCPIP$SNMP
Account: TCPIP UIC: [3655,21] ([TCPIP$AUX,TCPIP$SNMP])
CLI: DCL Tables: DCLTABLES
Default: SYS$SYSDEVICE:[TCPIP$SNMP]
LGICMD: LOGIN
Flags: Restricted
Primary days: Mon Tue Wed Thu Fri
Secondary days: Sat Sun
Primary 000000000011111111112222 Secondary 000000000011111111112222
Day Hours 012345678901234567890123 Day Hours 012345678901234567890123
Network: ##### Full access ###### ##### Full access ######
Batch: ----- No access ------ ----- No access ------
Local: ----- No access ------ ----- No access ------
Dialup: ----- No access ------ ----- No access ------
Remote: ----- No access ------ ----- No access ------
Expiration: (none) Pwdminimum: 6 Login Fails: 1
Pwdlifetime: 90 00:00 Pwdchange: (pre-expired)
Last Login: (none) (interactive), 17-APR-2015 13:58 (non-interactive)
Maxjobs: 0 Fillm: 100 Bytlm: 52200
Maxacctjobs: 0 Shrfillm: 0 Pbytlm: 0
Maxdetach: 0 BIOlm: 400 JTquota: 4096
Prclm: 8 DIOlm: 50 WSdef: 350
Prio: 8 ASTlm: 100 WSquo: 1024
Queprio: 4 TQElm: 50 WSextent: 4000
CPU: (none) Enqlm: 100 Pgflquo: 50000
Authorized Privileges:
NETMBX TMPMBX

l Confirm the directory and the files in the directory SYS$SYSDEVICE:[TCPIP$SNMP] are owned by the
TCPIP$SNMP account
$ directory/owner SYS$SYSDEVICE:[000000]TCPIP$SNMP.DIR
$ directory/owner SYS$SYSDEVICE:[TCPIP$SNMP…]*.*

If they are not then issue the following commands:

$ @sys$startup:tcpip$snmp_shutdown.com
$ set file/owner=tcpip$snmp SYS$SYSDEVICE:[000000]TCPIP$SNMP.DIR

HPE Insight Remote Support 7.10: Monitored Devices Configuration Guide Page 246 of 436
Chapter 18: Configuring HPE OpenVMS AlphaServers

$ set file/owner=tcpip$snmp SYS$SYSDEVICE:[TCPIP$SNMP…]*.*;*

$ @sys$startup:tcpip$snmp_startup.com

l Confirm that the Windows service named SNMP Service is running.

ELMC protocol troubleshooting

Check the following items if service events are not being received by Insight RS.
l Confirm that the ELMC protocol is working
If WCCPROXY is functioning properly or restarted, a green check mark appears in the OpenVMS device’s
Monitoring & Collections column. If the WCCPROXY process is stopped, a red X will appear in the
OpenVMS device’s Monitoring & Collections column. Insight RS takes about a minute to reflect changes in
status.
Click the Monitoring & Collections tab for more information about the status of the ELMC protocol. Click
the status icon to display a pop-up window with details about the protocol status.
If you see a red X in the Monitoring column, this means that the ELMC protocol is not functioning. The pop-
up window will display the following:
Monitoring Status Description: <openvms_server_fully_qualified_name>.
Protocol: Event Log Monitoring Collection (ELMC)
Service: ELMC Connection
Type: CONNECTIVITY
Status: FAILURE
Description: Failed to connect to EMClient Agent running on host <openvms_server_
fully_qualified_name>.
Detailed: Failed to connect to EMClient Agent running on host <openvms_server_fully_
qualified_name>.
Created: <some date/time>
Last Updated: <some date/time>

Note if the pop-up shows the SNMPv1 protocol, discovery detected the SNMP protocol. The SNMP
protocol cannot be used to monitor OpenVMS devices and this particular entry can be removed by clicking
Clear.
If Insight RS is not able to successfully connect to the OpenVMS system using the ELMC protocol,
continue with the troubleshooting steps below.
l If the ELMC protocol was not discovered, confirm the product WCCPROXY v6.4 is installed on your
OpenVMS system by issuing the following command:
$ product show product wccproxy
If you need to upgrade, the installation media can be found in:
<partition_where_InsightRS_is installed>:\ProgramData\HP\RS\DATA\ELMC
If you do not see the media in this folder, in the Insight RS Console browse to Administrator Settings >
Software Update tab. Click on Event Log Monitoring Collector (ELMC) package. Then on the
Available Version tab, click Install. Copy the media to your OpenVMS server in binary mode and then
issue the following commands when logged into the SYSTEM account:
$ run ELMCV64BL1KIT1_JUN-21-2012_OVMSALP.EXE
$ @wccproxy_install uninstall

HPE Insight Remote Support 7.10: Monitored Devices Configuration Guide Page 247 of 436
Chapter 18: Configuring HPE OpenVMS AlphaServers

$ @wccproxy_install install
l Confirm that the WCCPROXY process is running on the OpenVMS server by issuing the following command
when logged into the SYSTEM account.
$ wccproxy status
If it does not show the WCCProxy is running, issue the command:
$ wccproxy start
l Try restarting the WCCPROXY process on the OpenVMS server by issuing the commands while logged into
the SYSTEM account:
$ wccproxy stop
$ wccproxy start

l Rename SYS$ERRLOG:ERRLOG.SYS. The operating system should recreate one in approximately 15

minutes.
If a new ERRLOG.SYS file is not created confirm that the ERRFMT process exists. If it does not exist it can be
started with the command:
$ @sys$system:startup.com errfmt
l Confirm that port 7920 used by the ELMC protocol is not blocked by the firewall.
l Issue the following command to check if your Insight RS server is communicating with the ELMC process
by examining port 7920. If it is working correctly you should see your Hosting Device mentioned in the
“Remote Host” column as shown in the following example:
$ tcpip show device/port=7920
Port Remote
Device_socket Type Local Remote Service Host
bg285 STREAM 7920 0 *
bg42927 STREAM 7920 59958 1.2.3.4
l Send a test event and examine the Insight RS log file KCT.###.log for evidence on why the events may be
rejected. This is found in:
<partition_where _InsightRS_is_installed>\ProgramData\HP\RS\LOG
In the case that the OpenVMS errlog.sys is corrupt, rename the errlog.sys file and let the operating
system create a new one. Also confirm that the hardware is supported by Insight RS by referring to the
HPE Insight Remote Support Release Notes at www.hpe.com/info/insightremotesupport/docs.
l If no test event is received, examine the time zone of the OpenVMS system, the Hosting Device, and the
time zone defined in Insight RS to see if there is a discrepancy. The time zone within Insight RS can be
determined by browsing to Company Information > Sites > <site_name>.
The time zone of OpenVMS can be determine by issuing the following command:
$ show logical *time*
The time on the OpenVMS system can be determined by issuing the command:
$ show time

HPE Insight Remote Support 7.10: Monitored Devices Configuration Guide Page 248 of 436
Chapter 18: Configuring HPE OpenVMS AlphaServers

l Check that none of the command procedures in WCCPROXY_SPECIFIC:[SPECIFIC.WCCPROXY.DATA] have a

version limit of 32767. If they do, stop WCCPROXY by determining the pid of the WCCPROXY and
issuing STOP/ID=<pid #>. Then delete the files in this directory, and restart WCCPROXY by issuing a
WCCPROXY START command.
l If you continue to have problems with the ELMC protocol, check the log files in WCCPROXY_SPECIFIC:
[SPECIFIC.WCCPROXY.LOGS] for issues.
l If none of the troubleshooting steps shown above have solved the issue, deinstall and reinstall ELMC
(WCCPROXY) on the OpenVMS server:
$ run ELMCV64BL1KIT1_21-JUN-2012_OVMSI64.EXE
$ @wccproxy_install uninstall
$ @wccproxy_install install

l If test events are not working for any OpenVMS system, confirm that ELMC was installed on the Insight
RS server. WCCPROXY 6.4 software should appear in the Control Panel → All Control Panel Items →
Programs and Features. If WCCPROXY is missing, log into the Insight RS Console and navigate to
Administrator Settings → Software Updates. Click on Event Log Monitoring Collector (ELMC), and
on the Available Version tab, click Install. Once the WCCPROXY software is installed, make sure that
the WCCPROXY service is started.
l If test events are not working for any OpenVMS system, determine if Insight Remote Support Advanced
(RSA) A.05.80 or below is installed on the same server running Insight RS 7.x. If Insight RSA A.05.08 or
below appears in Control Panel → All Control Panel Items → Programs and Features, this software
should be removed.

SSH protocol troubleshooting

Check the following items if you are having issues with SAN collections.
l Examine the SSH service on the OpenVMS server with the tcpip show service ssh/full command.
Confirm that the number of Active sessions does not exceed the Limit. Also confirm what port is being
used by the SSH service and that the service is enabled.
l Confirm that the TCPIP$SSH account shows that its UIC identifier in the SYSUAF is TCPIP$SSH and the
account does not have the disuser flag. The following is an example of a properly defined TCPIP$SSH
account:
$ mcr authorize show tcpip$ssh
Username: TCPIP$SSH Owner: TCPIP$SSH
Account: TCPIP UIC: [3655,15] ([TCPIP$AUX,TCPIP$SSH])
CLI: DCL Tables: DCLTABLES
Default: TCPIP$SSH_DEVICE:[TCPIP$SSH]
LGICMD: LOGIN
Flags: Restricted
Primary days: Mon Tue Wed Thu Fri
Secondary days: Sat Sun
Primary 000000000011111111112222 Secondary 000000000011111111112222
Day Hours 012345678901234567890123 Day Hours 012345678901234567890123
Network: ##### Full access ###### ##### Full access ######
Batch: ----- No access ------ ----- No access ------
Local: ----- No access ------ ----- No access ------

HPE Insight Remote Support 7.10: Monitored Devices Configuration Guide Page 249 of 436
Chapter 18: Configuring HPE OpenVMS AlphaServers

Dialup: ----- No access ------ ----- No access ------

Remote: ----- No access ------ ----- No access ------
Expiration: (none) Pwdminimum: 6 Login Fails: 0
Pwdlifetime: 90 00:00 Pwdchange: (pre-expired)
Last Login: (none) (interactive), 16-AUG-2016 19:25 (non-interactive)
Maxjobs: 0 Fillm: 100 Bytlm: 15000
Maxacctjobs: 0 Shrfillm: 0 Pbytlm: 0
Maxdetach: 0 BIOlm: 400 JTquota: 4096
Prclm: 8 DIOlm: 1000 WSdef: 350
Prio: 8 ASTlm: 100 WSquo: 1024
Queprio: 4 TQElm: 50 WSextent: 4000
CPU: (none) Enqlm: 100 Pgflquo: 50000
Authorized Privileges:
NETMBX TMPMBX
Default Privileges:
NETMBX TMPMBX

l Confirm the directory and the files in the directory SYS$SYSDEVICE:[TCPIP$SSH] are owned by the
TCPIP$SSH account.
$ directory/owner SYS$SYSDEVICE:[000000]TCPIP$SSH.DIR
$ directory/owner SYS$SYSDEVICE:[TCPIP$SSH…]*.*

If they are not, then issue the following commands:

$ @sys$startup:tcpip$ssh_shutdown.com
$ @sys$startup:tcpip$ssh_client_shutdown.com
$ set file/owner=tcpip$ssh SYS$SYSDEVICE:[000000]TCPIP$SSH.DIR
$ set file/owner=tcpip$ssh SYS$SYSDEVICE:[TCPIP$SSH…]*.*;*
$ @sys$startup:tcpip$ssh_startup.com
$ @sys$startup:tcpip$ssh_client_startup.com

l Confirm that port 22 used by the SSH protocol is not blocked by the firewall.
l Install a SSH client on the Windows Hosting Device. Test if you can log in to OpenVMS system using the
SSH client on the Windows Hosting Device. Use the same credentials as defined in the SSH Named
Credential.
l If port 22 is not blocked by the firewall but you cannot log into the OpenVMS system using the SSH client
on your Windows server, test if you can SSH from the OpenVMS system to itself.
$ SSH localhost
l Check if any other system has SSH access to the OpenVMS server.
l Confirm that the account you are trying to log into does not have the DISUSER flag set and that the
password is not expired. Also make sure that Pwdlifetime field is set to (none).
l Examine the OpenVMS SSH server configuration file TCPIP$SSH_DEVICE:[TCPIP$SSH.SSH2]SSH2_
CONFIG. Make sure the AllowedAuthentications parameter includes password. Make sure the
DenyHosts parameter does not include a reference to the Windows server. Make sure there are not any
other configuration errors.
l Examine the TCPIP$SSH_DEVICE:TCPIP$SSH_RUN.LOG for clues as to why SSH is not working.
l To enable debug on the OpenVMS SSH server define the following logical:

HPE Insight Remote Support 7.10: Monitored Devices Configuration Guide Page 250 of 436
Chapter 18: Configuring HPE OpenVMS AlphaServers

$ DEFINE/SYSTEM TCPIP$SSH_SERVER_PARAMS "-i -d 5"

After troubleshooting is completed, deassign the logical with the command:
$ DEASSIGN/SYSTEM TCPIP$SSH_SERVER_PARAMS
l Confirm the OpenVMS account used for the SAN Collection SSH credentials also has the privileges of
CMKRNL, NETMBX, SYSLCK, and TMPMBX. The following is an example of a properly configured account:
$ mcr authorize show wbem
Username: WBEM Owner: WBEM
Account: WBEM UIC: [10,266] ([WBEM])
CLI: DCL Tables: DCLTABLES
Default: SYS$SYSDEVICE:[WBEM]
LGICMD:
Flags:
Primary days: Mon Tue Wed Thu Fri
Secondary days: Sat Sun
No access restrictions
Expiration: (none) Pwdminimum: 6 Login Fails: 0
Pwdlifetime: (none) Pwdchange: 26-JAN-2017 17:33
Last Login: 30-JAN-2017 21:45 (interactive), 1-FEB-2017 16:07 (non-interactive)
Maxjobs: 0 Fillm: 100 Bytlm: 64000
Maxacctjobs: 0 Shrfillm: 0 Pbytlm: 0
Maxdetach: 0 BIOlm: 150 JTquota: 4096
Prclm: 8 DIOlm: 150 WSdef: 2000
Prio: 4 ASTlm: 250 WSquo: 4000
Queprio: 4 TQElm: 10 WSextent: 16384
CPU: (none) Enqlm: 2000 Pgflquo: 50000
Authorized Privileges:
CMKRNL NETMBX SYSLCK TMPMBX
Default Privileges:
CMKRNL NETMBX SYSLCK TMPMBX

The following command shows the syntax for granting the required privileges to an OpenVMS account.
$ MCR AUTHORIZE MODIFY <username>/DEFPRIVILEGES=(NETMBX,TMPMBX,CMKRNL,SYSLCK) -
/PRIVILEGES=(NETMBX,TMPMBX,CMKRNL,SYSLCK)

l If the XML file created by the SAN Collection shows DCL errors similar to the following, the OpenVMS
account used for the credentials is missing the CMKRNL privilege:
%DCL-W-IVVERB, unrecognized command verb - check validity and spelling
\FC\
## FIBRE CARD INFO FINISHED ##
## Starting SCSI INFORMATION ##
%TYPE-W-SEARCHFAIL, error searching for SYS$SYSDEVICE:[WBEM]CLUE_SCSI.TXT;
-RMS-E-DNF, directory not found
-SYSTEM-W-NOSUCHFILE, no such file
%DELETE-W-SEARCHFAIL, error searching for SYS$SYSDEVICE:[WBEM]CLUE_SCSI.TXT;*
-RMS-E-DNF, directory not found
-SYSTEM-W-NOSUCHFILE, no such file
## Finishing SCSI INFORMATION ##

HPE Insight Remote Support 7.10: Monitored Devices Configuration Guide Page 251 of 436
Chapter 18: Configuring HPE OpenVMS AlphaServers

## Starting HARDWARE INFORMATION ##

%TYPE-W-SEARCHFAIL, error searching for SYS$SYSDEVICE:[WBEM]CLUE_CONFIG.TXT;
-RMS-E-DNF, directory not found
-SYSTEM-W-NOSUCHFILE, no such file
%DELETE-W-SEARCHFAIL, error searching for SYS$SYSDEVICE:[WBEM]CLUE_CONFIG.TXT;*
-RMS-E-DNF, directory not found
-SYSTEM-W-NOSUCHFILE, no such file

l If the XML file created by the SAN Collection shows DCL errors similar to the following, the OpenVMS
account used for the credentials is missing the SYSLCK privilege:
Excerpt xml file:
====== PCSI ======
%PCSIUI-E-PRIVCLASS1, operation requires SYSLCK privilege
%PCSIUI-E-ABORT, operation terminated due to an unrecoverable error condition

Telnet protocol troubleshooting

Check the following items if you are having issues with SAN collections.
l Examine the Telnet service on the OpenVMS server with the command tcpip show service
telnet/full. Confirm that the number of Active sessions does not exceed the Limit. Also confirm that
what port is being used by the Telnet service and that the service is enabled.
l Confirm that the TCPIP$TELNET account shows that its UIC identifier in the SYSUAF is TCPIP$TELNET and
the account does not have the disuser flag. The following is an example of a properly defined
TCPIP$TELNET account:
$ mcr authorize show tcpip$telnet
Username: TCPIP$TELNET Owner: TCPIP$TELNET
Account: TCPIP UIC: [3655,2] ([TCPIP$AUX,TCPIP$TELNET])
CLI: DCL Tables: DCLTABLES
Default: SYS$SYSDEVICE:[TCPIP$TELNET]
LGICMD: LOGIN
Flags: Restricted
Primary days: Mon Tue Wed Thu Fri
Secondary days: Sat Sun
Primary 000000000011111111112222 Secondary 000000000011111111112222
Day Hours 012345678901234567890123 Day Hours 012345678901234567890123
Network: ##### Full access ###### ##### Full access ######
Batch: ----- No access ------ ----- No access ------
Local: ----- No access ------ ----- No access ------
Dialup: ----- No access ------ ----- No access ------
Remote: ----- No access ------ ----- No access ------
Expiration: (none) Pwdminimum: 6 Login Fails: 0
Pwdlifetime: 90 00:00 Pwdchange: (pre-expired)
Last Login: (none) (interactive), (none) (non-interactive)
Maxjobs: 0 Fillm: 1024 Bytlm: 400000
Maxacctjobs: 0 Shrfillm: 0 Pbytlm: 0
Maxdetach: 0 BIOlm: 400 JTquota: 4096
Prclm: 8 DIOlm: 1000 WSdef: 350

HPE Insight Remote Support 7.10: Monitored Devices Configuration Guide Page 252 of 436
Chapter 18: Configuring HPE OpenVMS AlphaServers

Prio: 8 ASTlm: 2448 WSquo: 20000

Queprio: 4 TQElm: 20 WSextent: 20000
CPU: (none) Enqlm: 3000 Pgflquo: 20000
Authorized Privileges:
NETMBX TMPMBX
Default Privileges:
NETMBX TMPMBX

l Confirm the directory and the files in the directory SYS$SYSDEVICE:[TCPIP$TELNET] are owned by the
TCPIP$TELNET account.
$ directory/owner SYS$SYSDEVICE:[000000]TCPIP$TELNET.DIR
$ directory/owner SYS$SYSDEVICE:[TCPIP$TELNET…]*.*

If they are not then issue the following commands:

$ @sys$startup:tcpip$telnet_shutdown.com
$ set file/owner=tcpip$telnet SYS$SYSDEVICE:[000000]TCPIP$TELNET.DIR
$ set file/owner=tcpip$telnet SYS$SYSDEVICE:[TCPIP$TELNET…]*.*;*
$ @sys$startup:tcpip$telnet_startup.com

l Confirm that port 23 used by the telnet protocol is not blocked by the firewall.
l Enable the telnet client on the Insight RS Hosting Device. Open up a command prompt on the Windows
Hosting Device, enter telnet <ip_address_OpenVMS_system> and test if you can log into the OpenVMS
system. Use the same credentials as defined in the Telnet Named Credential.
l If port 23 is not blocked by the firewall but you cannot log into the OpenVMS system from the Hosting
Device, test if you can telnet from the OpenVMS system to itself: $ telnet localhost
l Check if any other system has telnet access to the OpenVMS server.
l Confirm that the account you are trying to log into does not have the DISUSER flag set and that the
password is not expired. Also make sure that Pwdlifetime field is set to (none).
l Confirm the OpenVMS account used for the SAN Collection TELNET credentials also has the privileges of
CMKRNL, NETMBX, SYSLCK, and TMPMBX. The following is an example of a properly configured account:
$ mcr authorize show wbem
Username: WBEM Owner: WBEM
Account: WBEM UIC: [10,266] ([WBEM])
CLI: DCL Tables: DCLTABLES
Default: SYS$SYSDEVICE:[WBEM]
LGICMD:
Flags:
Primary days: Mon Tue Wed Thu Fri
Secondary days: Sat Sun
No access restrictions
Expiration: (none) Pwdminimum: 6 Login Fails: 0
Pwdlifetime: (none) Pwdchange: 26-JAN-2017 17:33
Last Login: 30-JAN-2017 21:45 (interactive), 1-FEB-2017 16:07 (non-interactive)
Maxjobs: 0 Fillm: 100 Bytlm: 64000
Maxacctjobs: 0 Shrfillm: 0 Pbytlm: 0
Maxdetach: 0 BIOlm: 150 JTquota: 4096

HPE Insight Remote Support 7.10: Monitored Devices Configuration Guide Page 253 of 436
Chapter 18: Configuring HPE OpenVMS AlphaServers

Prclm: 8 DIOlm: 150 WSdef: 2000

Prio: 4 ASTlm: 250 WSquo: 4000
Queprio: 4 TQElm: 10 WSextent: 16384
CPU: (none) Enqlm: 2000 Pgflquo: 50000
Authorized Privileges:
CMKRNL NETMBX SYSLCK TMPMBX
Default Privileges:
CMKRNL NETMBX SYSLCK TMPMBX

The following command shows the syntax for granting the required privileges to an OpenVMS account.
$ MCR AUTHORIZE MODIFY <username>/DEFPRIVILEGES=(NETMBX,TMPMBX,CMKRNL,SYSLCK) -
/PRIVILEGES=(NETMBX,TMPMBX,CMKRNL,SYSLCK)

l If the XML file created by the SAN Collection shows DCL errors similar to the following, the OpenVMS
account used for the credentials is missing the CMKRNL privilege:
%DCL-W-IVVERB, unrecognized command verb - check validity and spelling
\FC\
## FIBRE CARD INFO FINISHED ##
## Starting SCSI INFORMATION ##
%TYPE-W-SEARCHFAIL, error searching for SYS$SYSDEVICE:[WBEM]CLUE_SCSI.TXT;
-RMS-E-DNF, directory not found
-SYSTEM-W-NOSUCHFILE, no such file
%DELETE-W-SEARCHFAIL, error searching for SYS$SYSDEVICE:[WBEM]CLUE_SCSI.TXT;*
-RMS-E-DNF, directory not found
-SYSTEM-W-NOSUCHFILE, no such file
## Finishing SCSI INFORMATION ##
## Starting HARDWARE INFORMATION ##
%TYPE-W-SEARCHFAIL, error searching for SYS$SYSDEVICE:[WBEM]CLUE_CONFIG.TXT;
-RMS-E-DNF, directory not found
-SYSTEM-W-NOSUCHFILE, no such file
%DELETE-W-SEARCHFAIL, error searching for SYS$SYSDEVICE:[WBEM]CLUE_CONFIG.TXT;*
-RMS-E-DNF, directory not found
-SYSTEM-W-NOSUCHFILE, no such file

l If the XML file created by the SAN Collection shows DCL errors similar to the following, the OpenVMS
account used for the credentials is missing the SYSLCK privilege:
Excerpt xml file:
====== PCSI ======
%PCSIUI-E-PRIVCLASS1, operation requires SYSLCK privilege
%PCSIUI-E-ABORT, operation terminated due to an unrecoverable error condition

Entitlement troubleshooting
Check the following items if you are having entitlement issues with your OpenVMS system.
l If the OpenVMS system does not pass the entitlement check, make sure you have the correct serial
number and product number specified on the contract.
l If the correct serial number and product number have been defined for the device and the entitlement check
continues to fail, confirm that the “Hosting Device Health” has a green check. This can be found in the
header of the Insight RS Console. If it shows a red x, click on “Hosting Device Health” for more details.

HPE Insight Remote Support 7.10: Monitored Devices Configuration Guide Page 254 of 436
Chapter 18: Configuring HPE OpenVMS AlphaServers

l Try stopping the following Window services in this order: 1) “HPE Insight Remote Support” and 2) “HPE
Insight RS Event Receiver” and then restarting them in that order.
l Confirm that port 443 used to communicate with the HPE backend is not blocked by the firewall.
Additional security firewall requirements are detailed in the HPE Insight Remote Support Security White
Paper at www.hpe.com/info/insightremotesupport/docs.
l Open up a browser on the Hosting Device and confirm if you can access this web page:
https://api.support.hpe.com/v1/version/index.html
l Issue a nslookup command and confirm that api.support.hpe.com can be resolved.
If api.support.hpe.com cannot be resolved by your DNS server, then add this address to the Windows
host file on the Hosting Device.
l Lack of connectivity to the HPE backend can sometimes be caused by issues with the HPE backend. For
additional assistance troubleshooting the lack of connectivity, contact the HPE Customer Support.

HPE Insight Remote Support 7.10: Monitored Devices Configuration Guide Page 255 of 436
 Chapter 19: Configuring Tru64 UNIX servers
Important: Configuration collections for Tru64 on AlphaServer are not available except when the
Tru64 server is part of a SAN collection.

Important: HPE only provides limited remote support for customers using HPE Alpha servers. As
with standard support, Insight Remote Support version 7.x will attempt to discover these products
as remotely monitored HPE products and send information about failure events to HPE.
However, if there are issues with the operation of the remote monitoring features of Insight Remote
Support version 7.x for these specific products, including the remote discovery or the reporting of
failure events to HPE, then HPE will resolve such issues in a commercially reasonable manner but
without guarantee of an immediate response or a resolution. If a failure event is successfully
received at HPE, it is managed according to the support level agreement.

Fulfill configuration requirements

To configure your Tru64 UNIX servers to be monitored by Insight RS, complete the following sections:
Table 19.1 Tru64 UNIX server configuration steps
Task Complete?

Make sure Insight RS supports your Integrity Tru64 server by checking the HPE Insight Remote
Support Release Notes.

Install and configure ELMC for Tru64 on the Tru64 UNIX server.

Add ELMC to the Insight RS Console.

Discover the Tru64 server in the Insight RS Console.

Install and configure communication software on

servers
To configure your monitored devices, complete the following sections:

Fulfill ELMC system requirements

Tru64 UNIX monitored devices must meet the following requirements before ELMC is installed. In clusters,
minimum requirements apply to each node in the cluster.

Hardware and software requirements

l Processor architecture: HPE AlphaServer
l Operating system: Tru64 UNIX version 4.0F, 4.0G, 5.1A or higher

HPE Insight Remote Support 7.10: Monitored Devices Configuration Guide Page 256 of 436
Chapter 19: Configuring Tru64 UNIX servers

Note: HPE Sustaining Engineering maintains a schedule of support for the Tru64 UNIX operating
system. HPE does not commit to supporting Insight Remote Support when installed on an
operating system version that has exceeded its end-of-support date.

l Minimum 20 MB free disk space for installation of all components.

l TCP/IP services must be installed and running.
l Upgrade to V1.22 or higher of the Emulex (EMX) driver if you have an EMX LP6000, LP7000, or LP8000
adapter (KGPSA–xx) using the SLI2 programming interface. Use of an EMX driver prior to V1.22 may result
in data not being processed correctly.
l System firmware: The prerequisite system firmware supports the logging of events according to the FRU
Table Version 5 Specification, which is required for Insight Remote Support FRU configuration tree
processing.
l All DSxx and ES40 systems must have firmware V5.7–4 or higher.
l All other systems (currently ES45, GSxx, and TS202c) ship with a compatible firmware version.
In general, users should take advantage of the latest improvements by obtaining the most recent firmware
version available for their platform.
Required permissions and access
To install, upgrade, or uninstall ELMC, you must be logged on as the root user. The /usr/opt/hp/svctools
directory is owned by root, and has rwx (read, write, and execute) permissions for root (owner), and no
permissions for any other user (group or world).

Archiving and cleaning the error log

After Insight Remote Support is installed on the Hosting Device, it uses ELMC to analyze all events stored in
the error log, which can result in high CPU usage over an extended period. To control this operation, you are
encouraged to archive and clean the error log before installing. This reduces the size of the log and the time
required for the initial scan.
Follow these guidelines for cleaning the error log. If ELMC is installed and running when you clean the log, you
do not need to stop and restart the Director process. Also, do not stop and restart the ERRFMT system event
logging process.

Tru64 UNIX version 4.0F

1. Stop the binlogd process: # /sbin/init.d/binlog stop
2. If desired, move the original error log to any appropriate name, for example:
# mv /var/adm/binary.errlog /var/adm/binary.errlog.2002_06_11
Saved logs can be analyzed at a later time.
3. If you skipped step 2, remove the original error log: # rm /var/adm/binary.errlog
4. Restart the server. During restart, the server creates a new binary.errlog file containing a new
configuration event. The server also restarts the binlogd process.

HPE Insight Remote Support 7.10: Monitored Devices Configuration Guide Page 257 of 436
Chapter 19: Configuring Tru64 UNIX servers

Tru64 UNIX version 4.0G

1. Stop the binlogd process: # /sbin/init.d/binlog stop
2. If desired, move the original error log to any appropriate name, for example:
# mv /var/adm/binary.errlog /var/adm/binary.errlog.2002_06_11
Saved logs can be analyzed at a later time.
3. If you skipped step 2, remove the original error log: # rm /var/adm/binary.errlog
4. Restart the binlogd process: # /sbin/init.d/binlog start

Tru64 UNIX version 5.A or higher

A new feature can send a signal to binlogd to save the current log and create a new one without stopping the
process. Follow the steps in section "Verify the binary.errlog CDSL" and section "Clear the Log with binlogd
Running".

Verify the binary.errlog CDSL

In version 5.1A or higher, the binary error log /var/adm/binary.errlog should be a context-dependent
symbolic link (CDSL) pointing to a file specific to each cluster node. This makes sure that the binlogd process
on each node stores that node's events to its own node-specific error log
/var/cluster/members/<memb>/adm/binary.errlog.
If the CDSL is ever deleted, binlogd recreates it as a regular, cluster-common file, which does not work
correctly. To check your file, issue the command:
# ls -l /var/adm/binary.errlog
Correct output looks similar to the following:
>lrwxrwxrwx 1 root adm 43 Jun 11 12:54 /var/adm/binary.errlog -
>../cluster/members/<memb>/adm/binary.errlog
Incorrect output does not show the -> link indicator:
-rw-r----- 1 root adm 560 Jun 11 12:59 /var/adm/binary.errlog
If necessary, correct the file by performing the following steps:
1. Stop the binlogd process on all cluster nodes by issuing the following command on each node:
# /sbin/init.d/binlog stop
2. Saved logs can be analyzed at a later time. If desired, move the original error log to any appropriate
name, for example:
# cd /var/adm
# mv binary.errlog binary.errlog.2002_06_11

3. Issue similar move commands for any node-specific error logs you wish to save, for example:
# mv /var/cluster/members/<memb>/adm/binary.errlog
/var/cluster/members/<memb>/adm/binary.errlog.2002_06_11

HPE Insight Remote Support 7.10: Monitored Devices Configuration Guide Page 258 of 436
Chapter 19: Configuring Tru64 UNIX servers

# mv /var/cluster/members/<memb>/adm/binlog.saved/binary.errlog.saved
/var/cluster/members/<memb>/adm/binlog.saved/binary.errlog.saved.2002_06_11

4. Remove existing error logs, ignoring any No such file or directory errors:
# rm /var/adm/binary.errlog
# rm /var/cluster/members/<memb>/adm/binary.errlog
# rm /var/cluster/members/<memb>/adm/binlog.saved/binary.errlog.saved

5. Create the CDSL:

# mkcdsl /var/adm/binary.errlog
6. Restart the binlogd process on all cluster nodes by issuing the following command on each node:
# /sbin/init.d/binlog start

Clear the log with binlogd running

For version 5.1A or higher, follow these steps on each cluster node that you want to clear:
1. Verify the binary.errlog CDSL section is complete as previously described.
2. If desired, keep any previously saved copy from being overwritten by moving it to any appropriate name,
for example:
# cd /var/cluster/members/member/adm/binlog.saved
# mv binary.errlog.saved binary.errlog.2002_06_11

3. Cause binlogd to copy and clear the original error log:

# kill -USR1 `cat /var/run/binlogd.pid`
The previous command does not kill the binlogd process. Instead, it sends a signal to binlogd that
causes it to copy /var/adm/binary.errlog to /var/cluster/members/member/adm/binlog.saved.
Then, the original /var/adm/binary.errlog file gets recreated with only a configuration event. Note that
/var/adm/binary.errlog is a CDSL that points to
/var/cluster/members/<memb>/adm/binary.errlog.
For further details, including how to automate this kind of error log management, see the section on Managing
the Binary Error Log File in the binlogd man page.

Verify serial number

On GS80, GS160, and GS320 systems, verify the serial number as directed before installing ELMC on the
monitored device.
Certain GS80, GS160, and GS320 systems did not have their system serial number set correctly at the
factory, and event rules on the Hosting Device only function when the serial number is set correctly. Affected
serial numbers will begin with the letter "G."
At the SRM console firmware prompt (the prompt when you first power on the server), check the serial number
with the following command:
show sys_serial_num
The serial number shown should match the actual serial number on the model/serial number tag located in the
power cabinet. If necessary, change the serial number with the following command:

HPE Insight Remote Support 7.10: Monitored Devices Configuration Guide Page 259 of 436
Chapter 19: Configuring Tru64 UNIX servers

set sys_serial_num
Type the six-character serial number provided on the tag in the power cabinet.

Note: This issue also can arise when multiple AlphaServers are ordered, because the factory may
assign an identical serial number to each system. In this scenario, event rules do not work correctly
because they require that each AlphaServer have a unique number. If this is the case, uniquely
identify each AlphaServer by appending –1, –2, –3, and so on, to the serial numbers when you use
the set sys_serial_num command.
Multiple partitions on the same AlphaServer always have the same serial number because they
reside on the same machine. There are no conflicts in this case, so do not attempt to assign unique
serial numbers to different partitions on the same machine.

Installing the ELMC Tru64 UNIX software package

First, extract the ELMC Software Package, then install it.
To extract the ELMC installation kit, place the kit .gz file in a temporary directory and unzip it:
# gunzip ELMC_<version>.tar.gz
Then, extract the tar file. If there is already a "kit" subdirectory when you perform this command, be sure there
are no previous ELMC kit files in this subdirectory before performing the command.
# tar -xvf ELMC_<version>.tar
This command creates a kit directory (if it does not already exist), and extracts the ELMC installation files.

Note: If installing in a TruCluster environment, make sure all nodes are up and running before
proceeding.

When your current directory is the one in which you extracted the kit, type the following command to install the
files for the ELMC WCCProxy.
# setld -l kit
Do not run setld -D to direct the ELMC installation to a non-default directory. The default directory is required
for proper ELMC operation.
The kit will install and finish with no user prompting. When you are returned to the shell prompt (#), the install
has finished and the wccproxy process will be running.

Add protocol credentials and start discovery

To discover your monitored devices, complete the following sections:

HPE Insight Remote Support 7.10: Monitored Devices Configuration Guide Page 260 of 436
Chapter 19: Configuring Tru64 UNIX servers

Create an ELMC protocol credential in the Insight RS

Console
To configure an ELMC protocol credential in the Insight RS Console, complete the following steps:
1. In a web browser, log on to the Insight RS Console.
2. In the main menu, select Discovery and click the Credentials tab.
3. From the Select and Configure Protocol drop-down list, select Event Log Monitoring Collector
(ELMC).
4. Click New. The New Credential dialog box appears.
Insight RS creates the protocol credential and it appears in the credentials table.

Discover the device in the Insight RS Console

To discover the device from the Insight RS Console, complete the following steps:
1. In a web browser, log on to the Insight RS Console.
2. In the main menu, select Discovery and click the Sources tab.
3. Expand the IP Addresses section and add the IP address for your device:
a. Click New.
b. Select the Single Address, Address Range, or Address List option.
c. Type the IP address(es) of the devices to be discovered.
d. Click Add.
4. Click Start Discovery.

Verify discovery and device status

To verify the device was discovered correctly, complete the following steps:
1. In a web browser, log on to the Insight RS Console.
2. In the main menu, select Devices and click the Device Summary tab.

3. Make sure the Status column contains a success icon ( ).

If there is no success icon, determine which column has the problem and consult the Online Help for
troubleshooting information.

Verify communication between monitored device

and Insight RS
To verify communication between your monitored device and Insight RS, complete the following section:

HPE Insight Remote Support 7.10: Monitored Devices Configuration Guide Page 261 of 436
Chapter 19: Configuring Tru64 UNIX servers

Verify collections in the Insight RS Console

Configuration collections are not supported for this device type except when it is part of a SAN collection. If
you have added this device to a SAN collection, you can manually run a SAN collection to verify the
configuration.
1. Log on to the Insight RS Console.
2. In the main menu, select Collection Services.
3. Click the Collection Schedules tab.
4. In the List of Collection Schedules pane, select the SAN Configuration Collection Schedule.
Information about the collection appears in the Collection Information pane. The On These Devices pane
lists the devices the collection will run on.
5. In the Schedule Information pane, click Run Now.
6. When the collection completes, click the SAN Storage Collection Results tab.
7. Expand the SAN Configuration Collection section.
8. Locate the entry for your device and check the Result column. If the collection was successful, a
success icon appears ( ). If it failed, an error icon appears ( ).

HPE Insight Remote Support 7.10: Monitored Devices Configuration Guide Page 262 of 436
 Chapter 20: Configuring NonStop Servers
Insight Remote Support supports NonStop systems, including HPE Integrity NonStop NS-series servers,
HPE Integrity NonStop BladeSystems, and HPE Integrity NonStop X-series servers. For details, see the
HPE Insight Remote Support Release Notes.
On NonStop systems, NonStop Open System Management (OSM) software performs problem diagnosis and
creates incident reports (IRs). OSM sends these IRs to Insight Remote Support, which in turn forwards them
on to HPE support.

Note: NonStop servers do not support configuration collections.

Using Insight Remote Support in the NonStop environment involves requirements and configuration steps
specific to NonStop. For information on how to get started, see the Insight Remote Support for NonStop
document. It is available from the following location:
support.hpe.com/hpsc/doc/public/display?docId=c04623664.

Note: Insight RS supports discovering devices with TCP instead of the default ICMP for customers
whose security policies do not allow ICMP. For details, see the Help.

HPE Insight Remote Support 7.10: Monitored Devices Configuration Guide Page 263 of 436
 Chapter 21: Configuring IBM servers
Insight Remote Support (RS) must be able to communicate with your IBM server before it can be monitored.
Insight RS can communicate with IBM servers running Windows with SNMP. The following information
describes how to install and configure the communication protocols and other recommended software
components so that it can be monitored by Insight RS.
Insight RS supports the following IBM servers:
l IBM System x™ (xSeries®)
l IBM BladeCenter® chassis and BladeCenter® servers

Note: Insight RS supports Microsoft Windows Server 2008 and 2008 R2 operating systems for IBM
servers.

Important: Configuration collections are not supported.

Fulfill configuration requirements

To configure your IBM servers to be monitored by Insight RS, complete the following sections:
Table 21.1 IBM server configuration steps
Task Complete?

Make sure Insight RS supports your IBM server by checking the HPE Insight Remote Support
Release Notes.

Configure the Windows SNMP service on the IBM server.

Install IBM Director Agent on the IBM server.

Configure the SNMP trap destination and SNMP read community string.

Add the SNMP protocol to the Insight RS Console.

Discover the IBM server in the Insight RS Console.

Add the device's Support Type and Support Identifier to the Insight RS Console.

Install and configure communication software on

servers
To configure your monitored devices, complete the following sections:

Configure the Windows SNMP service

1. On the monitored device, open the SNMP Service Properties window and select the Traps tab.

HPE Insight Remote Support 7.10: Monitored Devices Configuration Guide Page 264 of 436
Chapter 21: Configuring IBM servers

2. In the Community name field, type the SNMP community name and click Add to list.

Important: The community name must match the community name as configured in the
Insight RS Console.

3. In the trap destinations field, add the Hosting Device to the list:
a. To open the SNMP Service Configuration window, click Add.
b. Type the host name or IP address of the Hosting Device.
c. Click Add.
4. Click the Security tab and verify that the community name was added to the list of Accepted community
names.

HPE Insight Remote Support 7.10: Monitored Devices Configuration Guide Page 265 of 436
Chapter 21: Configuring IBM servers

5. Select the Send authentication trap check box.

6. Click the Accept SNMP packets from any host option.
7. Click OK to save the settings.

Install and configure SNMP

IBM Director Agent must be installed on the IBM server and the SNMP service must be configured. IBM
Director Agent includes an SNMP agent.
On a Windows 2008 and 2008 R2 server the solution was tested with IBM Systems Director Common Agent
version 6.1.1.

Important: Insight RS only supports agent version 6.1.1.

Installing IBM Director Agent

Download and install IBM Director Agent or IBM Systems Director Common Agent software for xSeries at:
http://www-03.ibm.com/systems/director/downloads/agents.html.

HPE Insight Remote Support 7.10: Monitored Devices Configuration Guide Page 266 of 436
Chapter 21: Configuring IBM servers

Note: If a service processor is installed on the monitored server, complete the following steps:
1. To configure the service processor’s trap destination use the Management Processor
Assistant task in the IBM Director console.
2. Add the IP address of the Hosting Device as a trap destination.
3. Restart the service processor.

Configuring the Management Module of the IBM BladeCenter® Chassis

1. Login into to the BladeCenter Management Module web page.
2. Select Alerts in the MM Control section of the left menu. The Alerts page appears.

3. Select one of the unused items from the Name column. The Remote Alert Recipient page appears.

HPE Insight Remote Support 7.10: Monitored Devices Configuration Guide Page 267 of 436
Chapter 21: Configuring IBM servers

4. On the Remote Alert Recipient page:

a. From the Status drop-down list, select Enabled.
b. In the Name field, type a Remote Alert Recipient name. For example: Remote Alert Recipient 1
c. From the Notification method drop-down list, select SNMPover LAN.
d. In the IP address or host name field, type the Hosting Device IP address.
e. Optional: In the E-mail address field, type an e-mail address, if you want to be notified about alerts by
e-mail
5. Select Save.The Alerts page appears. The saved Remote Alert Recipient now appears on the Alerts
page of the BladeCenter Management Module.
6. On the Alerts page scroll down to the Monitored Alerts section.
7. Select the following:
a. All Critical Alerts
b. From Warning Alerts:
i. Single Chassis Cooling Device (Blower) failure
ii. Temperature
iii. Voltage
c. From System Alerts:
i. PFA
ii. Network change

HPE Insight Remote Support 7.10: Monitored Devices Configuration Guide Page 268 of 436
Chapter 21: Configuring IBM servers

8. Save your settings.

9. In the MM Control section of the left menu, select Network Protocol. The Network Protocol page
appears.
10. Scroll down to SNMP.

HPE Insight Remote Support 7.10: Monitored Devices Configuration Guide Page 269 of 436
Chapter 21: Configuring IBM servers

11. From the SNMPv1 agent drop-down list, select Enabled.

12. Configure an SNMPv1 Community:
a. In the Community Name field, type a SNMP community name.
b. From the Access Type drop-down list, select Get.
c. In the Host Name or IP Address field, type the Hosting Device host name or IP address.
13. Click Save.
14. Restart the BladeCenter Management Module:
a. In the MM Control section of the left menu, select Restart MM.
b. Click Restart.

Install IBM device drivers and service processor firmware

To use an attached device, its device drivers must be installed. Make sure that the appropriate IBM server’s
service processors are installed.

HPE Insight Remote Support 7.10: Monitored Devices Configuration Guide Page 270 of 436
Chapter 21: Configuring IBM servers

Note:
l To determine which service processors are installed on an IBM server, refer to the Implementing
Systems Management Solutions using IBM Director document at:
http://www.redbooks.ibm.com/redbooks/pdfs/sg246188.pdf
l A combined device driver for all service processors is available for each operating system at:
http://www.ibm.com/systems/support/.
l No additional driver is needed for servers that have only an ISM processor installed.

Upgrade the service processor firmware to the latest version to ensure that all features of the service
processors are available.
To install the IBM device drivers, complete the following steps:
1. Go to: www.ibm.com/systems/support.
2. From the top navigation bar, select Support & downloads.
3. From the Choose support type drop-down list, select System x.
4. From the Popular links list, select Software and device drivers.
5. Download and install the device driver for your server.
6. Reboot the server(if requested).

Add protocol credentials and start discovery

To discover your monitored devices, complete the following sections:

Create an SNMPv1 protocol credential in the Insight RS

Console
If your device's SNMP community string is set to public and your community access mode is read only,
Insight RS automatically associates an SNMPv1 protocol with your device. If you use a different community
string or use a nonstandard port, you must create an SNMPv1 protocol credential in the Insight RS Console.
To configure SNMPv1 in the Insight RS Console, complete the following steps:
1. In a web browser, log on to the Insight RS Console.
2. In the main menu, select Discovery and click the Credentials tab.
3. From the Select and Configure Protocol drop-down list, select Simple Network Management Protocol
Version 1, V2C (SNMPv1, SNMPv2C).
4. Click New. The New Credential dialog box appears.
5. Type the Community String you have configured on your device.
6. Click Add.
Insight RS creates the protocol credential and it appears in the credentials table.

HPE Insight Remote Support 7.10: Monitored Devices Configuration Guide Page 271 of 436
Chapter 21: Configuring IBM servers

Discover the device in the Insight RS Console

To discover the device from the Insight RS Console, complete the following steps:
1. In a web browser, log on to the Insight RS Console.
2. In the main menu, select Discovery and click the Sources tab.
3. Expand the IP Addresses section and add the IP address for your device:
a. Click New.
b. Select the Single Address, Address Range, or Address List option.
c. Type the IP address(es) of the devices to be discovered.
d. Click Add.
4. Click Start Discovery.

Configure warranty and contract information

Monitoring support for non-HPE servers requires special attention to server warranty and contract data. The
serial number and product numbers that is discovered usually does not match the serial number and product
number listed in the HPE support contract.
To configure the serial number and product number, complete the following steps:
1. In the Insight RS Console, verify the server appears on the Devices page.

Important: For IBM BladeCenter® chassis the Product column is empty by default.

2. Click the Device Name and on the Device tab, type the following information:

Note: The HPE Account Support team must add the entitlement data for IBM servers in the
Insight RS Console.

l Override Serial Number (as listed in the contract)

l Override Product Number (as listed in the contract)
l Support Type
l Support Identifier

Verify discovery and device status

To verify the device was discovered correctly, complete the following steps:
1. In a web browser, log on to the Insight RS Console.
2. In the main menu, select Devices and click the Device Summary tab.

3. Make sure the Status column contains a success icon ( ).

If there is no success icon, determine which column has the problem and consult the Online Help for
troubleshooting information.

HPE Insight Remote Support 7.10: Monitored Devices Configuration Guide Page 272 of 436
 Chapter 22: Configuring Dell PowerEdge
servers
Insight Remote Support (RS) must be able to communicate with your Dell PowerEdge server before it can be
monitored. Insight RS can communicate with Dell PowerEdge servers with SNMP. The following information
describes how to install and configure the communication protocols and other recommended software
components so that it can be monitored by Insight RS.

Note: Insight RS supports Microsoft Windows Server 2008 and 2008 R2 operating systems for Dell
PowerEdge servers.

Important: Configuration collections are not supported.

Note: If you have a RAID controller installed on your system and you plan to install the storage
management function, ensure that the device drivers for each RAID controller are also installed.

Fulfill configuration requirements

To configure your Dell PowerEdge servers to be monitored by Insight RS, complete the following sections:
Table 22.1 Dell PowerEdge server configuration steps
Task Complete?

Make sure Insight RS supports your Dell PowerEdge server by checking the HPE Insight Remote
Support Release Notes.

Configure the Windows SNMP service on the Dell PowerEdge server.

Install Dell OpenManage Server Administrator on the Dell PowerEdge server.

Configure the SNMP trap destination and SNMP read community string.

Add the SNMP protocol to the Insight RS Console.

Discover the Dell PowerEdge server in the Insight RS Console.

Add the device's Support Type and Support Identifier to the Insight RS Console.

Install and configure communication software on

servers
To configure your monitored devices, complete the following sections:

Configure the Windows SNMP service

1. On the monitored device, open the SNMP Service Properties window and select the Traps tab.

HPE Insight Remote Support 7.10: Monitored Devices Configuration Guide Page 273 of 436
Chapter 22: Configuring Dell PowerEdge servers

2. In the Community name field, type the SNMP community name and click Add to list.

Important: The community name must match the community name as configured in the
Insight RS Console.

3. In the trap destinations field, add the Hosting Device to the list:
a. To open the SNMP Service Configuration window, click Add.
b. Type the host name or IP address of the Hosting Device.
c. Click Add.
4. Click the Security tab and verify that the community name was added to the list of Accepted community
names.

HPE Insight Remote Support 7.10: Monitored Devices Configuration Guide Page 274 of 436
Chapter 22: Configuring Dell PowerEdge servers

5. Select the Send authentication trap check box.

6. Click the Accept SNMP packets from any host option.
7. Click OK to save the settings.

Install and configure SNMP

Dell OpenManage Server Administrator must be installed on the Dell PowerEdge server and SNMP service
must be configured.
On a Windows 2008 and 2008 R2 server the solution was tested with Dell OpenManage Server Administrator
version 6.2.0.

Important: Insight RS only supports agent version 6.2.0.

Installing Dell OpenManage Server Administrator

Download and install Dell OpenManage Server Administrator software. To download the software, go to:
http://content.dell.com/us/en/enterprise/d/solutions/openmanage-server-administrator.

HPE Insight Remote Support 7.10: Monitored Devices Configuration Guide Page 275 of 436
Chapter 22: Configuring Dell PowerEdge servers

Note: You can verify the device driver under Windows by right-clicking My Computer, selecting
Manage, and then clicking Device Manager.

See also Dell OpenManage Installation and Security User’s Guide.

Configuring SNMP Traps in Dell OpenManage Server Administrator

1. Open Dell OpenManage Server Administrator.
2. Click the Alert Management tab.
3. Click the SNMP Traps link.
4. Select the following options:
l System
l Critical
l Temperatures
l Voltages
l Logs
l Memory
l Batteries

5. Click Apply Changes.

HPE Insight Remote Support 7.10: Monitored Devices Configuration Guide Page 276 of 436
Chapter 22: Configuring Dell PowerEdge servers

Add protocol credentials and start discovery

To discover your monitored devices, complete the following sections:

Create an SNMPv1 protocol credential in the Insight RS

Console
If your device's SNMP community string is set to public and your community access mode is read only,
Insight RS automatically associates an SNMPv1 protocol with your device. If you use a different community
string or use a nonstandard port, you must create an SNMPv1 protocol credential in the Insight RS Console.
To configure SNMPv1 in the Insight RS Console, complete the following steps:
1. In a web browser, log on to the Insight RS Console.
2. In the main menu, select Discovery and click the Credentials tab.
3. From the Select and Configure Protocol drop-down list, select Simple Network Management Protocol
Version 1, V2C (SNMPv1, SNMPv2C).
4. Click New. The New Credential dialog box appears.
5. Type the Community String you have configured on your device.
6. Click Add.
Insight RS creates the protocol credential and it appears in the credentials table.

Discover the device in the Insight RS Console

To discover the device from the Insight RS Console, complete the following steps:
1. In a web browser, log on to the Insight RS Console.
2. In the main menu, select Discovery and click the Sources tab.
3. Expand the IP Addresses section and add the IP address for your device:
a. Click New.
b. Select the Single Address, Address Range, or Address List option.
c. Type the IP address(es) of the devices to be discovered.
d. Click Add.
4. Click Start Discovery.

Configure warranty and contract information

Monitoring support for non-HPE servers requires special attention to server warranty and contract data. The
serial number and product numbers that is discovered usually does not match the serial number and product
number listed in the HPE support contract.
To type the serial number and product number, complete the following steps:

HPE Insight Remote Support 7.10: Monitored Devices Configuration Guide Page 277 of 436
Chapter 22: Configuring Dell PowerEdge servers

1. In the Insight RS Console, verify the server appears on the Devices page.

Important: For Dell PowerEdge chassis the Product column is empty by default.

2. Click the Device Name and on the Device tab, type the following information:

Note: The HPE Account Support team must configure the entitlement data for Dell Windows
servers in the Insight RS Console.

l Override Serial Number (as listed in the contract)

l Override Product Number (as listed in the contract)
l Support Type
l Support Identifier

Verify discovery and device status

To verify the device was discovered correctly, complete the following steps:
1. In a web browser, log on to the Insight RS Console.
2. In the main menu, select Devices and click the Device Summary tab.

3. Make sure the Status column contains a success icon ( ).

If there is no success icon, determine which column has the problem and consult the Online Help for
troubleshooting information.

HPE Insight Remote Support 7.10: Monitored Devices Configuration Guide Page 278 of 436
 Chapter 23: Configuring BladeSystem c-Class
Enclosures
HPE BladeSystem c-Class Enclosures can be monitored by Insight Remote Support (RS). Configuring the
BladeSystem c-Class Enclosure only enables Insight RS to monitor the enclosure itself. The blades installed
in the BladeSystem c-Class Enclosure need to be configured separately to be monitored by Insight RS. See
"Identify required communication protocols and software components" on page 26 for information about
configuring your individual blade types.
HPE BladeSystem c-Class Enclosures can be monitored using the embedded management capabilities in the
OA or by configuring SNMP in the Onboard Administrator (OA) depending on the OA firmware level:

Important: Do not attempt to use both configuration methods on the same Hosting Device. This is
not supported and monitoring will not work correctly.

l Option 1: OA firmware level 3.60 or above supports the embedded management capabilities. Register
with an Insight Remote Support Hosting Device through the OA to send service events to the Hosting
Device. If you have configured a primary and standby OA in your environment, ensure that the firmware
version for both OAs is 3.60 or higher.
See "Register Remote Support through the Onboard Administrator" on page 281.

Important: To address third-party software vulnerabilities, HPE recommends using OA 4.30 or

later. To access the OA 4.30 or later web interface, you must enable TLS in your browser. TLS is
the successor to Secure Sockets Layer (SSL).

l Option 2: All OA firmware levels support connecting to Insight RS using SNMP. Configure the SNMP
protocol to send traps to the Hosting Device. If you have configured a primary and standby OA in your
environment, discover only one of the OAs and not both.

Important: FIPS Top Secret Mode and SNMP are not compatible. If you choose to use SNMP,
you must disable FIPS Top Secret Mode.

l OA firmware level prior to 3.55 requires the use of SNMP. Embedded management is not supported.
l OA firmware level 4.01 or above supports SNMPv3.

Important: Insight RS only supports SNMPv3 traps, and does not support SNMPv3 Informs.
Insight RS listens on port 1162 for SNMPv3 traps, and your SNMPv3 passwords must be at
least 8 characters long.

See "Configure SNMP on the BladeSystem c-Class enclosure" on page 285.

Note: If using OA firmware versions 3.55 or 3.56 HPE recommends you upgrade to version 3.60.

HPE Insight Remote Support 7.10: Monitored Devices Configuration Guide Page 279 of 436
Chapter 23: Configuring BladeSystem c-Class Enclosures

Configuring BladeSystem c-Class Enclosures

through the OA
HPE BladeSystem c-Class Enclosures can be monitored by Insight Remote Support (RS). Configuring the
BladeSystem c-Class Enclosure only enables Insight RS to monitor the enclosure itself. The blades installed
in the BladeSystem c-Class Enclosure need to be configured separately to be monitored by Insight RS. See
"Identify required communication protocols and software components" on page 26 for information about
configuring your individual blade types.
HPE BladeSystem c-Class Enclosures can be monitored using the embedded management capabilities in the
OA or by configuring SNMP in the OA depending on the OA firmware level:
Important: Do not attempt to configure both configuration methods as this is not supported and monitoring
will not work correctly.
1. OA firmware level 3.60 or above: Register with an Insight Remote Support 7.10 Hosting Device through
the OA to send service events to the Hosting Device for both the primary and standby OA.

Important: To address third-party software vulnerabilities, HPE recommends using OA 4.30 or

later. To access the OA 4.30 or later web interface, you must enable TLS in your browser. TLS
is the successor to Secure Sockets Layer (SSL).

2. OA firmware level prior to 3.55: If you have configured a primary and standby OA in your environment,
you should configure the SNMP protocol to send traps to the Hosting Device. Discovery from the Insight
Remote Support Hosting Device should be limited to one of the OAs and not both. If using a firmware
version older than 3.55, see "Configuring BladeSystem c-Class Enclosures using SNMP" on page 284.
Note: If using OA firmware versions 3.55 or 3.56 HPE recommends you upgrade to version 3.60.
The latest firmware software can be found on the HPE website at: www.hpe.com/support/oa.

Fulfill configuration requirements

To configure your BladeSystem c-Class Enclosures through the OA to be monitored by Insight RS, complete
the following sections:
Table 23.1 BladeSystem c-Class Enclosure through the OA configuration steps
Task Complete?

Make sure Insight RS supports your BladeSystem c-Class enclosure by checking the HPE
Insight Remote Support Release Notes.

Register for Remote Support through the Onboard Administrator.

Verify the status of the BladeSystem c-Class enclosure in the Insight RS Console.

Send a test event to verify connectivity between your BladeSystem c-Class enclosure and Insight
RS.

Configure monitored devices

To configure your monitored devices, complete the following section:

HPE Insight Remote Support 7.10: Monitored Devices Configuration Guide Page 280 of 436
Chapter 23: Configuring BladeSystem c-Class Enclosures

Configure firewall and port settings

Table 23.2 BladeSystem c-Class Enclosure Connectivity - Firewall/Port Requirements
Protocol Ports Source Destination Function Optional

ICMP N/A Hosting Monitored Provides system reachability (ping) check Required
Device Systems during system discovery and before other
operations.

TCP 80 Hosting Onboard HTTP used for discovery and data collection. Required
Device Administrator

TCP 443 Hosting Onboard HTTPS used for discovery and data collection. Recommended
Device Administrator

TCP 7906 Onboard Hosting Secure HTTP (HTTPS) port used by the Required
Administrator Device listener running in the Director's Web
Interface. The monitored host connects to the
Hosting Device on this port (e.g.
https://<hostname>:7906).

Register the OA and verify discovery

To discover your monitored devices, complete the following sections:

Register Remote Support through the Onboard Administrator

If using OA firmware version 3.60 or above, you can enable Insight Remote Support for a BladeSystem c-
Class Enclosure using the Onboard Administrator (OA). The OA is not responsible for reporting information
about the blades installed in the BladeSystem c-Class Enclosure. The OA only reports enclosure issues,
such as problems with fans, power supplies, and media bays.

Important: To address third-party software vulnerabilities, HPE recommends using iLO 4 2.03 or
later. To access the iLO 4 2.03 or later web interface, you must enable TLS in your browser. TLS is
the successor to Secure Sockets Layer (SSL).

Important: If using a primary and standby OA, ensure that the firmware version for both OAs is 3.60
or higher.

Important: When registering for Remote Support through the OA, make sure your trap destination
is set to the same Insight RS Hosting Device as you register with for Remote Support. When the
OA sends service events to the Hosting Device, it also generates SNMP traps that are sent to the
SNMP trap destination. The SNMP trap destination needs to be the same Insight RS Hosting
Device, otherwise duplicate events are reported to HPE.

Registering the enclosure does not register the individual blades installed in the enclosure. You need to
configure each blade separately.
To register for Remote Support through he OA, complete the following steps:

HPE Insight Remote Support 7.10: Monitored Devices Configuration Guide Page 281 of 436
Chapter 23: Configuring BladeSystem c-Class Enclosures

1. In a web browser, log on to the HPE BladeSystem Onboard Administrator (https://<OA hostname or
IP address>).
2. Navigate to Enclosure Information → Enclosure Settings → Network Access, and click the
Protocols tab.
3. Make sure the Enable XML Reply check box is selected. If this check box is not selected, the OA
cannot be enabled in Insight RS.
4. Navigate to Enclosure Information → Enclosure Settings → Remote Support, and click the
Registration tab.

5. Click Register this enclosure through an HPE Insight Remote Support centralized hosting
device.
6. Type a host name or IP address.
7. In the Port field, type 7906.
8. Click Register.

Verify discovery and device status

To verify the device was discovered correctly, complete the following steps:
1. In a web browser, log on to the Insight RS Console.
2. In the main menu, select Devices and click the Device Summary tab.

3. Make sure the Status column contains a success icon ( ).

If there is no success icon, determine which column has the problem and consult the Online Help for
troubleshooting information.

Verify communication between monitored device and

Insight RS
To verify communication between your monitored device and Insight RS, complete the following sections:

HPE Insight Remote Support 7.10: Monitored Devices Configuration Guide Page 282 of 436
Chapter 23: Configuring BladeSystem c-Class Enclosures

Sending a test event

After registering the c-Class enclosure with Insight Remote Support, send a test event to confirm the
connection.
1. In the OA navigation menu, click Enclosure Settings → Remote Support → Service Events. The
Service Events screen appears.
2. Click Send Test Event.
When the transmission is complete, the test event is listed in the Service Event Log and in the Insight
RS Console.
The Time Generated column in the Service Event Log shows the date and time based on the configured
enclosure time zone.
3. Check the Insight RS Console to verify that the test event arrived:
a. Log on to the Insight RS Console.
b. In the main menu, select Devices.
c. Find the c-Class enclosure and click the device name.
d. Click the Service Events tab. All service events submitted against the system are displayed here
(even if you clear the Service Event Log).
Insight RS converts the OA service event Time Generated value to the time zone of the browser
used to access the Insight RS Console.

Note: Test events are automatically closed by HPE since no further actions are required.

Verify collections in the Insight RS Console

Collections are not automatically run after discovery. HPE recommends that you manually run a collection
after discovery completes in order to verify connectivity. Run the collection schedule manually on the
Collection Services → Collection Schedules tab. For more information about scheduling collections, see the
Insight RS Help.
Verify that this collection ran successfully on the Collection Services → Basic Collection Results tab in the
Insight RS Console.
1. Log on to the Insight RS Console.
2. In the main menu, select Collection Services and then click the Basic Collection Results tab.
3. Expand the Server Basic Configuration Collection section.
4. Locate the entry for your device and check the Result column. If the collection was successful, a
success icon appears ( ). If it failed, an error icon appears ( ).

Maintenance and troubleshooting

Disable monitoring of a BladeSystem c-Class Enclosure
There may be a reason that you need to temporarily disable a BladeSystem c-Class Enclosure so that is no
longer recognized by Insight Remote Support. For example, for routine maintenance of the device or if the

HPE Insight Remote Support 7.10: Monitored Devices Configuration Guide Page 283 of 436
Chapter 23: Configuring BladeSystem c-Class Enclosures

enclosure's warranty has expired.

Important: Disabling the c-Class Enclosure in the Insight RS Console does not unregister the
device in the OA. For the OA to be aware that the device has been disabled, you must unregister the
in the OA instead of disabling the device in the Insight RS Console.

Note the following:

l Disabling or deleting the c-Class enclosure in the Insight RS Console does not unregister the device in OA.
For OA to be aware that an enclosure is disabled, you must use OA to unregister from Insight Remote
Support. Additionally, if the enclosure is deleted in the Insight RS Console and the OA sends an SNMP
trap, Insight RS will trigger a re-discovery of the enclosure and possibly re-enable the device for remote
support.
l Unregistering an enclosure through OA temporarily discontinues monitoring of the enclosure, but the
enclosure is still listed in the Insight RS Console. To resume monitoring, use the OA software to re-register
the enclosure.
To temporarily unregister the from Insight RS, complete the following steps:
1. In a web browser, log on to the HPE BladeSystem Onboard Administrator (https://<OA hostname or
IP address>).
2. Navigate to Enclosure Information → Enclosure Settings → Remote Support.
3. Click Unregister. The following message appears:
Are you sure you want to un-register and disable Insight Remote Support?

4. Click OK. The following message appears:

Un-registration in progress. Please wait…

When the un-registration is finished, the Remote Support page shows the following message:
The enclosure is not registered.

The system disables monitoring and collections on this device.

Configuring BladeSystem c-Class Enclosures using

SNMP
HPE BladeSystem c-Class Enclosures can be monitored by Insight Remote Support (RS). Configuring the
BladeSystem c-Class Enclosure only enables Insight RS to monitor the enclosure itself. The blades installed
in the BladeSystem c-Class Enclosure need to be configured separately to be monitored by Insight RS. See
"Identify required communication protocols and software components" on page 26 for information about
configuring your individual blade types.
If using an OA firmware version below 3.55, you must configure SNMP in the Onboard Administrator (OA)
before the enclosure can be monitored by Insight RS. If using firmware version 3.60 or above, HPE
recommends registering your c-Class Enclosure through the OA. For more information, see "Configuring
BladeSystem c-Class Enclosures through the OA" on page 280. If using OA firmware versions 3.55 or 3.56
HPE recommends you upgrade to version 3.60.

HPE Insight Remote Support 7.10: Monitored Devices Configuration Guide Page 284 of 436
Chapter 23: Configuring BladeSystem c-Class Enclosures

Fulfill configuration requirements

To configure your BladeSystem c-Class Enclosures using SNMP to be monitored by Insight RS, complete
the following sections:
Table 23.3 BladeSystem c-Class Enclosure using SNMP configuration steps
Task Complete?

Make sure Insight RS supports your BladeSystem c-Class enclosure by checking the HPE
Insight Remote Support Release Notes.

Configure SNMP on the BladeSystem c-Class enclosure.

Add the SNMP protocol to the Insight RS Console.

Discover the BladeSystem c-Class enclosure in the Insight RS Console.

Send a test event to verify connectivity between your BladeSystem c-Class enclosure and Insight
RS.

Install and configure communication software on enclosures

To configure your monitored devices, complete the following sections:

Configure SNMP on the BladeSystem c-Class enclosure

You can use SNMPv1 or SNMPv3 to monitor your BladeSystem c-Class enclosure. Follow the steps in one
of the options below to configure SNMP on your enclosure.
For more information about configuring SNMP on your enclosure, see the HPE BladeSystem Onboard
Administrator User Guide, available at: www.hpe.com/support/OA_UG_en.

Important: Configuring the enclosure for remote support does not allow Insight RS to monitor the
blades installed in the enclosure. You need to configure each blade separately.

Option 1: Configure SNMPv1

Configure SNMPv1 in the OA to monitor the enclosure with Insight RS.

Important: If using a primary and standby OA, limit discovery to one of the OAs and not both.

To configure SNMPv1, complete the following steps:

1. In a web browser, open the HPE BladeSystem Onboard Administrator.
2. In the log on screen, type your user name and password and click Sign In.

HPE Insight Remote Support 7.10: Monitored Devices Configuration Guide Page 285 of 436
Chapter 23: Configuring BladeSystem c-Class Enclosures

3. Expand Enclosure Information → Enclosure Settings, and click SNMP Settings.

4. On the Settings tab, select the Enable SNMP check box and complete the following steps:
a. Add system location and contact information.
b. Set Read and Write community strings.
c. Click Apply.
5. Add an SNMP alert destination:
a. In the SNMP Alert Destinations section, click New.
b. In the Alert Destination field, type the IP address of the Hosting Device.
c. In the Community String field, type the SNMP community string for the Hosting Device.
d. Click Add Alert.

Option 2: Configure SNMPv3

Configure SNMPv3 in the OA to monitor the enclosure with Insight RS.

Important: If using a primary and standby OA, limit discovery to one of the OAs and not both.

Important: Insight RS only supports SNMPv3 traps, and does not support SNMPv3 Informs.
Insight RS listens on port 1162 for SNMPv3 traps, and your SNMPv3 passwords must be at least 8
characters long.

To configure SNMPv3, complete the following steps:

1. In a web browser, open the HPE BladeSystem Onboard Administrator.
2. In the log on screen, type your user name and password and click Sign In.

HPE Insight Remote Support 7.10: Monitored Devices Configuration Guide Page 286 of 436
Chapter 23: Configuring BladeSystem c-Class Enclosures

3. Expand Enclosure Information → Enclosure Settings, and click SNMP Settings.

4. On the Settings tab, select the Enable SNMP check box and complete the following steps:
a. Add system location and contact information.
b. Set Read and Write community strings.
c. Click Apply.
5. Create a user account to be used to send the SNMPv3 trap:
a. On the Users tab, click New.
b. In the User Name field, type a user name.
c. Select the Minimum Security required for operation: noAuthNoPriv, authNoPriv, authPriv. HPE
recommends authPriv. Your Minimum Security selection will alter what you enter for the remaining
steps of the configuration. For example, the noAuthNoPriv setting does not require a password for
either authentication or privacy. Note Minimum Security only applies to local users.
d. Select an Authentication Protocol: MD5 or SHA
e. In the Authentication Password field, type an authentication password. Confirm the password in
the next field.
f. Select a Privacy Protocol algorithm used to encrypt the trap: AES128, DES.
g. In the Privacy Password field, type a privacy password. Confirm the password in the next field.
6. Add an SNMP alert destination:
a. On the Settings tab, in the SNMP Alert Destinations section, click New.
b. In the Alert Destination field, type the IP address of the Hosting Device. Make sure you add the
SNMPv3 port: 1162. For example: <ip_address>:1162.
c. Select the SNMPv3 check box.

HPE Insight Remote Support 7.10: Monitored Devices Configuration Guide Page 287 of 436
Chapter 23: Configuring BladeSystem c-Class Enclosures

d. In the User field, select the user account to be used to send the trap. This is the account created in
the previous step.
e. Select the Security level used to send the trap: noAuthNoPriv, authNoPriv, authPriv. Make sure
this matches the Minimum Security setting you selected for the user.
f. Click Add Alert.

Configure firewall and port settings

Table 23.4 BladeSystem c-Class Enclosure Connectivity - Firewall/Port Requirements
Protocol Ports Source Destination Function Optional

ICMP N/A Hosting Monitored Provides system reachability (ping) check Required
Device Systems during system discovery and before other
operations.

TCP 80 Hosting Onboard HTTP used for discovery and data collection. Required
Device Administrator

TCP 443 Hosting Onboard HTTPS used for discovery and data collection. Recommended
Device Administrator

TCP 7906 Onboard Hosting Secure HTTP (HTTPS) port used by the Required
Administrator Device listener running in the Director's Web
Interface. The monitored host connects to the
Hosting Device on this port (e.g.
https://<hostname>:7906).

UDP 161 Hosting Onboard SNMP. This is the standard port used by Required
Device Administrator SNMP agents on monitored systems. The
Hosting Device sends requests to devices on
this port.

UDP 162 Onboard Hosting SNMP Trap. This is the port used by Insight Required*
Administrator Device RS to listen to SNMP traps.

UDP 1162 Onboard Hosting SNMPv3 Trap. This is the port used by Insight Required*
Administrator Device RS to listen to SNMPv3 traps.

* Dependent on the version of SNMP used on the monitored device.

Add Protocol credentials and start discovery

To discover your monitored devices, complete the following sections:

Create an SNMP protocol credential in the Insight RS Console

Create an SNMPv1 or SNMPv3 protocol credential to correspond to the protocol you configured on your
enclosure in "Option 1: Configure SNMPv1" on page 285 or "Option 2: Configure SNMPv3" on page 286.
Option 1: SNMPv1
If your device's SNMP community string is set to public and your community access mode is read only,
Insight RS automatically associates an SNMPv1 protocol with your device. If you use a different community
string or use a nonstandard port, you must create an SNMPv1 protocol credential in the Insight RS Console.
To configure SNMPv1 in the Insight RS Console, complete the following steps:

HPE Insight Remote Support 7.10: Monitored Devices Configuration Guide Page 288 of 436
Chapter 23: Configuring BladeSystem c-Class Enclosures

1. In a web browser, log on to the Insight RS Console.

2. In the main menu, select Discovery and click the Credentials tab.
3. From the Select and Configure Protocol drop-down list, select Simple Network Management Protocol
Version 1, V2C (SNMPv1, SNMPv2C).
4. Click New. The New Credential dialog box appears.
5. Type the Community String you have configured on your device.
6. Click Add.
Insight RS creates the protocol credential and it appears in the credentials table.

Option 2: SNMPv3
Create an SNMPv3 protocol credential in the Insight RS Console so Insight RS can communicate with your
device.
To configure SNMPv3 in the Insight RS Console, complete the following steps:
1. In a web browser, log on to the Insight RS Console.
2. In the main menu, select Discovery and click the Credentials tab.
3. From the Select and Configure Protocol drop-down list, select Simple Network Management Protocol
Version 3 (SNMPv3).
4. Click New. The New Credential dialog box appears.
5. Either use the default port of 161 or clear the Use default check box and type a new port number.
6. In the SNMP Account Credential fields, add:
a. Type the Username for the user on your device.
b. Select an Account Authentication Protocol: MD5 or SHA. Make sure these settings match what you
defined for the user in "Option 2: Configure SNMPv3" on page 286.
c. Type the Account Authentication Password.
d. Select an Account Privacy Protocol: DES, AES128. Make sure these settings match what you
defined for the user in "Option 2: Configure SNMPv3" on page 286.
e. Type the Account Privacy Passphrase.
f. Leave the Context Name blank.
7. Click Add.
Insight RS creates the protocol credential and it appears in the credentials table.

Discover the device in the Insight RS Console

Note: If there is an issue with HTTPS (SSL) communication, discovery will attempt to use HTTP to
discover the device.

To discover the device from the Insight RS Console, complete the following steps:
1. In a web browser, log on to the Insight RS Console.
2. In the main menu, select Discovery and click the Sources tab.

HPE Insight Remote Support 7.10: Monitored Devices Configuration Guide Page 289 of 436
Chapter 23: Configuring BladeSystem c-Class Enclosures

3. Expand the IP Addresses section and add the IP address for your device:
a. Click New.
b. Select the Single Address, Address Range, or Address List option.
c. Type the IP address(es) of the devices to be discovered.
d. Click Add.
4. Click Start Discovery.

Verify discovery and device status

To verify the device was discovered correctly, complete the following steps:
1. In a web browser, log on to the Insight RS Console.
2. In the main menu, select Devices and click the Device Summary tab.

3. Make sure the Status column contains a success icon ( ).

If there is no success icon, determine which column has the problem and consult the Online Help for
troubleshooting information.

Verify communication between monitored device and

Insight RS
To verify communication between your monitored device and Insight RS, complete the following sections:

Verify service event monitoring

To send a test event, complete the following steps:
1. In a web browser, open the HPE BladeSystem Onboard Administrator.
2. In the log on screen, type your user name and password and click Sign In.
3. Expand Enclosure Information → Enclosure Settings, and click SNMP Settings..
4. On the Settings tab, click Send Test Alert to send a test SNMP trap to the Hosting Device.

Verify collections in the Insight RS Console

Collections are not automatically run after discovery. HPE recommends that you manually run a collection
after discovery completes in order to verify connectivity. Run the collection schedule manually on the
Collection Services → Collection Schedules tab. For more information about scheduling collections, see the
Insight RS Help.
Verify that this collection ran successfully on the Collection Services → Basic Collection Results tab in the
Insight RS Console.
1. Log on to the Insight RS Console.
2. In the main menu, select Collection Services and then click the Basic Collection Results tab.
3. Expand the Server Basic Configuration Collection section.
4. Locate the entry for your device and check the Result column. If the collection was successful, a
success icon appears ( ). If it failed, an error icon appears ( ).

HPE Insight Remote Support 7.10: Monitored Devices Configuration Guide Page 290 of 436
Chapter 23: Configuring BladeSystem c-Class Enclosures

Maintenance and troubleshooting

Disable monitoring of a BladeSystem c-Class Enclosure
There may be a reason that you need to temporarily disable a BladeSystem c-Class Enclosure so that is no
longer recognized by Insight Remote Support. For example, for routine maintenance of the device or if the
enclosure's warranty has expired.
To disable a device in Insight Remote Support, complete the following steps:
1. In the main menu, select Devices.
2. Click the Device Summary tab.
3. Select the check box in the far left column for the devices you want to disable.
4. Click Actions → Disable Selected, and click OK in the confirmation dialog box.
The system disables monitoring and collections on this device.

HPE Insight Remote Support 7.10: Monitored Devices Configuration Guide Page 291 of 436
 Chapter 24: Configuring Virtual Connect
Modules
HPE Virtual Connect Modules require SNMP for event monitoring and collections.

Fulfill configuration requirements

To configure your Virtual Connect Modules to be monitored by Insight RS, complete the following sections:
Table 24.1 Virtual Connect Module configuration steps
Task Complete?

Make sure Insight RS supports your Virtual Connect Module by checking the HPE Insight
Remote Support Release Notes.

Configure SNMP in the HPE Virtual Connect Manager that manages your Virtual Connect
Modules.

Add the SNMP protocol to the Insight RS Console.

Discover the Virtual Connect Module in the Insight RS Console.

Configure Communication Software on Virtual Connect

Modules
To configure your monitored devices, complete the following sections:

Configure SNMP on the Virtual Connect Module

To configure SNMP, complete the following steps:
1. In a web browser, open the HPE Virtual Connect Manager that manages your Virtual Connect Modules.
2. In the log on screen, type your user name and password and click Sign In.
3. In the left menu, click SNMP Configuration in the Domain Settings section.
4. On the Settings tab, in the SNMP Configuration section, enable SNMP:
a. Select the Enable SNMP V1/V2 check box for Ethernet Modules and FlexFabric Modules.
b. Select the Enable SNMP V1/V2 check box for Fibre Channel Modules.

HPE Insight Remote Support 7.10: Monitored Devices Configuration Guide Page 292 of 436
Chapter 24: Configuring Virtual Connect Modules

5. In the SNMP Trap Destinations section, add the trap destination for your Insight RS Hosting Device.
6. Click Apply.

Configure firewall and port settings

Table 24.2 Virtual Connect Modules Connectivity - Firewall/Port Requirements
Protocol Ports Source Destination Function Optional

ICMP N/A Hosting Monitored Provides system reachability (ping) check during system Required
Device Systems discovery and before other operations.

UDP 161 Hosting Monitored SNMP. This is the standard port used by SNMP agents Required
Device Systems on monitored systems. The Hosting Device sends
requests to devices on this port.

UDP 162 Monitored Hosting SNMP Trap. This is the port used by Insight RS to listen Required
Systems Device to SNMP traps.

Add protocol credentials and start discovery

To discover your monitored devices, complete the following sections:

Create an SNMP protocol credential in Insight RS Console

If your device's SNMP community string is set to public and your community access mode is read only,
Insight RS automatically associates an SNMPv1 protocol with your device. If you use a different community

HPE Insight Remote Support 7.10: Monitored Devices Configuration Guide Page 293 of 436
Chapter 24: Configuring Virtual Connect Modules

string or use a nonstandard port, you must create an SNMP protocol credential in the Insight RS Console.
To configure SNMP in the Insight RS Console, complete the following steps:
1. In a web browser, log on to the Insight RS Console.
2. In the main menu, select Discovery and click the Credentials tab.
3. From the Select and Configure Protocol drop-down list, select Simple Network Management Protocol
Version 1, V2C (SNMPv1, SNMPv2C).
4. Click New. The New Credential dialog box appears.
5. Type the Community String you have configured on your device.
6. Click Add.
Insight RS creates the protocol credential and it appears in the credentials table.

Discover the device in the Insight RS Console

To discover the device from the Insight RS Console, complete the following steps:
1. In a web browser, log on to the Insight RS Console.
2. In the main menu, select Discovery and click the Sources tab.
3. Expand the IP Addresses section and add the IP address for your device:
a. Click New.
b. Select the Single Address, Address Range, or Address List option.
c. Type the IP address(es) of the devices to be discovered.
d. Click Add.
4. Click Start Discovery.

Verify discovery and device status

To verify the device was discovered correctly, complete the following steps:
1. In a web browser, log on to the Insight RS Console.
2. In the main menu, select Devices and click the Device Summary tab.

3. Make sure the Status column contains a success icon ( ).

If there is no success icon, determine which column has the problem and consult the Online Help for
troubleshooting information.

Verify communication between monitored device and

Insight RS
To verify communication between your monitored device and Insight RS, complete the following sections:

Verify collections in the Insight RS Console

Collections are not automatically run after discovery. HPE recommends that you manually run a collection
after discovery completes in order to verify connectivity. Run the collection schedule manually on the

HPE Insight Remote Support 7.10: Monitored Devices Configuration Guide Page 294 of 436
Chapter 24: Configuring Virtual Connect Modules

Collection Services → Collection Schedules tab. For more information about scheduling collections, see the
Insight RS Help.
Verify that this collection ran successfully on the Collection Services → Basic Collection Results tab in the
Insight RS Console.
1. Log on to the Insight RS Console.
2. In the main menu, select Collection Services and then click the Basic Collection Results tab.
3. Expand the Server Basic Configuration Collection section.
4. Locate the entry for your device and check the Result column. If the collection was successful, a
success icon appears ( ). If it failed, an error icon appears ( ).

HPE Insight Remote Support 7.10: Monitored Devices Configuration Guide Page 295 of 436
 Chapter 25: Configuring P6000 and
Enterprise Virtual Arrays
The P6000 Command View server can be either a standalone server with the Command View and SMI-S
software installed (referred to as Server Based Management - SBM) or it can be built in to the EVA device
itself, referred to as Array Based Management ABM.
l To configure a P6000 or EVA using Server Based Management, see "Configuring P6000 and Enterprise
Virtual Arrays using Server Based Management" below
l To configure a P6000 or EVA using Array Based Management, see "Configuring P6000 and Enterprise
Virtual Arrays using Array Based Management" on page 309

Configuring P6000 and Enterprise Virtual Arrays

using Server Based Management
The following information tells how to set up your P6000 Command View management server so that Insight
RS can monitor your Enterprise Virtual Array (EVA) devices. This includes instructions for when the
management server is a standalone server and when the management server is also the Insight Remote
Support (RS) Hosting Device.
For Insight RS to monitor your EVA devices, your management server requires two software applications:
P6000 Command View and the Event Log Monitoring Collector (ELMC).
Make sure you monitor your P6000 Command View management server with Insight RS. To be monitored by
Insight RS, the ProLiant Windows server hosting P6000 Command View has the same system requirements
and configuration as any ProLiant Windows server (see "Understanding monitored devices prerequisites" on
page 26). Make sure to set your communication protocol credentials accordingly.

Important: HP P6000 Command View 10.3.8 introduced the ability to disable TLS 1.0 and 1.1
protocols, but Insight RS does not support TLS 1.2 exclusive access. For more information, see the
HP P6000 Command View Suite User Guide at: www.hpe.com/support/hpesc.

Note: HPE highly recommends that you enable the Email Adapter on the Administrator Settings
→ Integration Adapters tab and, at the minimum, select the following notifications: Case Opened,
Application Failure, Entitlement Expiration, and Device Change.

Fulfill configuration requirements

To configure your P6000 and EVAs using Server Based Management (SBM) to be monitored by Insight RS,
complete the following sections:
Table 25.1 P6000 and Enterprise Virtual Array using SBM configuration steps
Task Complete?

Make sure Insight RS supports your P6000 disk array by checking the HPE Insight Remote
Support Release Notes.

HPE Insight Remote Support 7.10: Monitored Devices Configuration Guide Page 296 of 436
Chapter 25: Configuring P6000 and Enterprise Virtual Arrays

Table 25.1 P6000 and Enterprise Virtual Array using SBM configuration steps, continued
Task Complete?

Verify HP P6000 Command View is installed and configured on the management server.

Install ELMC on the management server.

Create a P6000 Command View protocol credential in the Insight RS Console.

Create an ELMC protocol credential in the Insight RS Console.

Create a protocol credential in the Insight RS Console for the management server.

Discover the EVA in the Insight RS Console.

Verify the EVA's warranty and contract information in the Insight RS Console.

Send a test event to verify connectivity between your EVA and Insight RS.

Install and configure communication software for arrays

The following software is required on the management server for Insight RS to monitor your EVA devices:
l P6000 Command View 9.4 through 10.3.x
P6000 Command View provides a communication path, via SMI-S, between Insight RS and the EVA.
l Windows ELMC
ELMC provides a communication path for Insight RS to monitor the event data written by P6000 Command
View.
To configure your monitored devices, complete the following sections:

Install and configure P6000 Command View

Insight RS monitors the management server rather than the EVA directly. To be supported by Insight RS, the
management server must have P6000 Command View installed (version 9.4 through 10.3.x) and be managing
at least one array. There can be multiple management servers in an environment for the purposes of fault
tolerance or load balancing; however there can only be one management server that is actively managing a
given EVA array at any time.
Insight RS requires SMI-S on the management server. SMI-S is installed with P6000 Command View by
default, and serves as the communication path between Insight RS and the array, using CIMOM for WBEM
communications.

Note: A P6000 Command View standard installation is the preferred baseline for Insight RS
supportability.

Insight RS supports two options for where P6000 Command View can be installed:
l Installed on a separate management server.
l Installed on the Insight RS Hosting Device, coexisting with the Insight RS software. Environments with
multiple instances of P6000 Command View can have one instance on the Hosting Device and other
instances of P6000 Command View on other monitored devices.
Multiple instances of P6000 Command View can share the management role of common attached EVA arrays
in the environment. This can be for the purpose of fault tolerance or load balancing, for example. Although

HPE Insight Remote Support 7.10: Monitored Devices Configuration Guide Page 297 of 436
Chapter 25: Configuring P6000 and Enterprise Virtual Arrays

there can be multiple instances of P6000 Command View capable of managing the EVA array, only one
instance of P6000 Command View can be the active manager of that array. Other instances of P6000
Command View that are not active in managing the array are considered to be passive.

Caution: Removing SMI-S from a host system also forces the removal of Command View for Tape
Libraries (TL). The version of Command View TL must match the firmware used in the tape library.
If the version of SMI-S installed by Command View TL is older than the one being used by P6000
Command View, then install or upgrade P6000 Command View after Command View TL to avoid a
conflict.
Additionally, the credentials used by each software application are overwritten by the other when it
installs. Therefore, use the same account for both.

Refer to the following P6000 Command View documentation for setting up your management server and
array. Documentation is available at: www.hpe.com/support/hpesc. Search for P6000 Command View
Software.
l HP P6000 Command View Suite Installation Guide
l HP P6000 Command View Suite Release Notes
l HP P6000 Enterprise Virtual Array Compatibility Reference
This document contains EVA system and hardware requirements. Refer to the following two tables in the
document: Table 4.1 Supported software on management servers and the management module and Table
4.2 Supported EVA software operating environments.
l Also see the P6000 Command View Software - Overview at:
h20564.www2.hpe.com/hpsc/doc/public/display?docId=emr_na-c03045333.
P6000 Command View management server system and access requirements
The management server requires the following access:
l Supported versions of P6000 Command View use a secure logon design.
l A Microsoft Windows account with the correct group privilege is required to access P6000 Command
View.
During the installation of P6000 Command View, you are required to create to new groups on the system: HP
Storage Admins (write access) and HP Storage Users (read access). P6000 Command View credentials are
required when setting up Insight RS; verify that you have this information.

Option 1: Install P6000 Command View on a separate management server

Install P6000 Command View following the steps in the HP P6000 Command View Suite Installation Guide.
After installation, verify the required components installed successfully:
1. Make sure that P6000 Command View 9.4 through 10.3.x is installed on the management server.
Go to the Windows Control Panel and make sure that HP P6000 Command View Software appears in
the Programs and Features window.
2. Make sure that the SMI-S is installed on the management server.
Verify the component is installed and running by checking the presence and status of the Service named
HP StorageWorks CIM Object Manager.

HPE Insight Remote Support 7.10: Monitored Devices Configuration Guide Page 298 of 436
Chapter 25: Configuring P6000 and Enterprise Virtual Arrays

Option 2: Install P6000 Command View on the Hosting Device

When Insight RS is installed on the same server where P6000 Command View is installed, the WMI Mapper
Proxy will have a port conflict with the SMI-S Provider component of Command View. Both use port 5989.
The typical result of this situation is that Insight RS is not able to communicate with the SMI-S provider,
meaning that Insight RS will not detect the associated storage systems for monitoring.
The simplest way to avoid this scenario is to avoid installing these products on the same server.
If there is a need to have them installed on the same server, the port for one needs to be changed. Note that
current versions of Command View should detect that the port is currently in use and allow for use of a
different port. But if for some reason a conflict is occurring, the port for the WMI Mapper Proxy can be changed
by following the below steps.
Install P6000 Command View following the steps in the HP P6000 Command View Suite Installation Guide.
After installation, verify the following:
1. Make sure that P6000 Command View 9.4 through 10.3.x is installed on the management server.
Go to the Windows Control Panel and make sure that HP P6000 Command View Software appears in
the Programs and Features window.
2. Make sure that SMI-S is installed and running on the management server.
Verify the presence and status of the Service named HP StorageWorks CIM Object Manager.
3. Verify there are no port conflicts by completing the following sections.
Change WMI Mapper port configuration
Insight RS and P6000 Command View require unique port assignments when both are hosted on the same
server. The procedure documented below will modify the port assignment for WMI Mapper and is the
recommended method. This preserves the default port assignment for the SMI-S CIMOM as a communication
hub to many other applications.

Note: This example uses the port value of 6989. Your environment may require a different port.
Using the netstat –a command from Command Prompt window will show your current port
assignments.

1. Stop the Pegasus WMI Mapper Service using the Windows Services API.
a. Select Start and Run, in the run field type services.msc.
b. Click OK.
c. Find and stop the Pegasus WMI Mapper service.
2. Using a text editor, add the variable httpsPort=6989 to the C:\Program Files\The Open Group\WMI
Mapper\cimserver_planned.conf file.
3. Restart the Pegasus WMI Mapper service in the Windows Services API.
4. Run the netstat –a command from Command Prompt window and verify that wmiservice.exe is
listening on port 6989.
a. Select Start and Run.
b. Type cmd.

HPE Insight Remote Support 7.10: Monitored Devices Configuration Guide Page 299 of 436
Chapter 25: Configuring P6000 and Enterprise Virtual Arrays

c. Click OK. The Command Prompt window appears.

d. Enter netstat –a at the command prompt.
e. Verify that port 6989 is now seen in the output.
Change SIM ports (if using SIM)
If Systems Insight Manager (SIM) is also installed on the server where Insight RS and P6000 Command View
are installed, complete following steps:
1. Change the WMI Mapper Proxy port in SIM:
a. Login to SIM with Administrative privileges.
b. Open Options → Protocol Settings → WMI Mapper Proxy.
c. Select the radio button preceding the CMS instance of WMI Mapper running on the localhost.
d. Click Edit.
e. Type 6989 in the port number field.
f. Click OK to save.
2. Add the text below to the C:\Program Files\HP\Systems Insight
Manager\config\identification\wbemportlist.xml file:

Note: This example uses the port value of 6989. Your environment may require a different port.
Using the netstat –a command from Command Prompt window will show your current port
assignments.

<?xml version="1.0" encoding="UTF-8"?>

<wbemportlist>
<port id="5989" protocol="https">
<cimnamespacelist>
<cimnamespace name="root/cimv2"/>
<cimnamespace name="vmware/esxv2"/>
</cimnamespacelist>
<interopnamespacelist>
<interopnamespace name="root/pg_interop"/>
<interopnamespace name="root"/>
<interopnamespace name="root/emulex"/>
<interopnamespace name="root/qlogic"/>
<interopnamespace name="root/ibm"/>
<interopnamespace name="root/emc"/>
<interopnamespace name="root/smis/current"/>
<interopnamespace name="root/hitachi/dm51"/>
<interopnamespace name="interop"/>
<interopnamespace name="root/interop"/>
<interopnamespace name="root/switch"/>
<interopnamespace name="root/cimv2"/>
</interopnamespacelist>
</port>

HPE Insight Remote Support 7.10: Monitored Devices Configuration Guide Page 300 of 436
Chapter 25: Configuring P6000 and Enterprise Virtual Arrays

<!-- WMI Mapper httpsPort=6989 -->

<port id="6989" protocol="https">
<interopnamespacelist>
<interopnamespace name="interop"/>
</interopnamespacelist>
</port>
</wbemportlist>

3. Restart the HPE SIM service:

Right click on the HPE Systems Insight Manager service in the Windows Services API and select
restart from the drop down menu.
4. Verify that the HPE Systems Insight Manager Identify Systems task is able to communicate with the
local WMI:
a. Login to HPE SIM UI with Administrative privileges.
b. First select the HPE SIM server and re-identify it.
c. Open Options → Identify Systems.
d. On the Identify Systems page click on the radio button preceding Search.
e. Type the hostname of the CMS in the field provided.
f. Click Search.
g. Click Apply.
h. Click Run Now.
i. Verify the following string is returned in the Task Results standard out window:
Got ComputerSystem WBEM/WMI data from the system

Install ELMC on the P6000 Command View server

ELMC requirements
Event data for the EVA is only delivered to the P6000 Command View server that is actively managing the
array. However, you should also install ELMC on any server that is running P6000 Command View that is
capable of being an active manager of an array of EVA devices. Any P6000 Command View instance that is
not currently actively managing an EVA is called a passive instance of P6000 Command View.
The P6000 Command View server, whether it is the Hosting Device or a separate management server, must
meet the following basic requirements before you install ELMC.
Disk space: 40MB must be available at install time on the drive where the Windows operating system is
installed (%SystemDrive%, typically C: by default). 30MB are needed after installation completes.
Installation Conditions and Requirements
Location of ELMC software: The ELMC for Windows component that was downloaded from Insight RS onto
the Hosting Device must be copied to a local drive on the P6000 Command View management server.
The ELMC installation must be completed from a local drive on the management server and does not support
installation from remote mapped shares. The installation gives an error if you map to a drive letter belonging to
another system.
Required Permissions and Access

HPE Insight Remote Support 7.10: Monitored Devices Configuration Guide Page 301 of 436
Chapter 25: Configuring P6000 and Enterprise Virtual Arrays

To install, remove, or update ELMC, the user ID must be one of the following:
l A member of the Administrators group on the server
l A member of a group that is a member of the Administrators group on the server. For example, if your user
ID is a Domain Admin, and you have added Domain Admins to the Administrator group on the local
machine, then you have the necessary permissions. To add Domain Administrators to the local
Administrator group, use the specific procedure relevant to your operating system.

Clear the Event Log

This step is optional, but HPE recommends that you archive and clear the application log on the management
server before you install ELMC.
ELMC provides a communication path for Insight RS to monitor the event data written by P6000 Command
View. Once this communication path is established, Insight RS analyzes the event data found in the
Windows Application Event Log. When ELMC is initially installed and started, recently logged events are
processed by Insight RS, which can temporarily tie-up resources. In general, this feature is useful when you
are installing ELMC on a system that is suspected of having a problem, whereby the application log
information is useful for problem resolution. If the Application Event Log has not been cleared, this initial
analysis can take a long time to complete and consume bandwidth on both the management server and
Hosting Device.
The best practice is to archive the old event data and clear the Application Event Log prior to installation to
reduce this overhead. HPE recommends that the Application Event Log Properties be set to be a minimum
size of 10MB with an ‘as needed’ overwrite time. These settings may require adjustment based on the
environment.
Follow these steps to archive and clean the Windows Application Event Log, before installing ELMC:
1. Open the event viewer and navigate to Start → Programs → Administrative Tools → Event Viewer.
2. In the left pane, expand Windows Logs and click on Application Log.
3. To clear all events, click Action → Clear Log. You are given the option to save the existing events to
another file before clearing. Saved logs can be analyzed at a later time.
4. Close the event viewer.

Install ELMC
ELMC must be installed on the management server to allow access to logged event data from the array.
ELMC is required on the management server so that events can be forwarded to Insight RS.
If ELMC is already installed on the management server, make sure it is version 6.2 or later. If it's older than
version 6.2, it needs to be upgraded. To check the version of ELMC, run the following command from a
Command Prompt window: wccproxy version.

Note: When upgrading to ELMC version 6.4, the incorrect version number is displayed in the
upgrade window. After performing the upgrade, the correct version number of 6.4 will show in the
Programs and Features window and when you run the wccproxy version command.

HPE Insight Remote Support 7.10: Monitored Devices Configuration Guide Page 302 of 436
Chapter 25: Configuring P6000 and Enterprise Virtual Arrays

Important: Real Time Event Data and communication to the array is only capable when there is a
connection to the P6000 Command View instance that is the active manager of the array. In order to
configure a monitored device, you must install ELMC on any server that is running P6000 Command
View that is capable of being the active manager of the array. Any P6000 Command View instance
that is not the active manager of an EVA is considered to be a passive instance of P6000 Command
View. Historic Event Data may be present on a passive instance if it had been the active manager in
the past. This event data may be of use for manual analysis.
Event data for the EVA is only delivered to the P6000 Command View server that is actively
managing the array. However, you should also install ELMC on any server that is running P6000
Command View that is capable of being an active manager of an array of EVA devices. Any P6000
Command View instance that is not currently actively managing an EVA is called a passive
instance of P6000 Command View.
A passive instance of P6000 Command View can see the array but cannot communicate with it.
Only the active management instance is capable of communicating with the array. This is why you
may see the array discovered but missing information about the array in some components.

To install the ELMC software package, complete the following steps:

1. In the Insight RS Console, navigate to the Administrator Settings → Software Updates tab and select
the Event Log Monitoring Collector (ELMC) software package.
2. On the Available Version tab, click Download.
3. When the download completes, click Install. The ELMC packages are placed in the %HP_RS_
DATA%\SWM\LANDINGZONE\ELMC folder. This folder defaults to
C:\ProgramData\HP\RS\DATA\SWM\LANDINGZONE\ELMC.
Note: The ProgramData folder is a hidden folder. To view this folder, set the folder options to show
hidden folders.
4. Copy the appropriate Windows x86/x64 ELMC software package into a temporary directory on the
management server.
5. Double-click the installer file to begin the install process. The kit will install and finish with no user
prompting. No user configuration input is required to install the ELMC software package.
6. To verify that ELMC installed, open a Command Prompt window on the management server and type:
wccproxy status
It should return: The WCCProxy service is running.

Configure firewall and port settings

Table 25.2 EVA Connectivity - Firewall/Port Requirements
Protocol Ports Source Destination Function Optional

ICMP N/A Hosting Monitored Provides system reachability (ping) check during system Required
Device Systems discovery and before other operations.

TCP 2372 Hosting P6000/EVA P6000/EVA CommandView - Storage Collections for Required
Device EVA (HTTPS).

HPE Insight Remote Support 7.10: Monitored Devices Configuration Guide Page 303 of 436
Chapter 25: Configuring P6000 and Enterprise Virtual Arrays

Table 25.2 EVA Connectivity - Firewall/Port Requirements, continued

TCP 2373 Hosting P6000/EVA P6000/EVA CommandView - Storage Collections for Required
Device P6000/EVA Array Based Management.

TCP 2374 Hosting P6000/EVA P6000/EVA Command View 10.x - Storage Collections Required
Device for P6000/EVA Array Based Management.

TCP 5989 Hosting Monitored Secured WBEM CIMOM protocol over HTTPS/SOAP. Required
Device Systems This port is used to communicate with WBEM end point
nodes.

TCP 7905 Monitored Hosting Secure HTTP (HTTPS) port used by the listener running Required
Systems Device in the Director's Web Interface. The monitored host
connects to the Hosting Device on this port (e.g.
https://<hostname>:7905).

TCP 7920 Hosting Monitored The Insight RS ELMC (formerly WCCProxy) process Required
Device Systems communicates with the Director on this port. This is a
proprietary protocol. Any connections that exchange
username and passwords use SSL. Not all connections
are SSL.

UDP 161 Hosting Monitored SNMP. This is the standard port used by SNMP agents Optional
Device Systems on monitored systems. The Hosting Device sends
requests to devices on this port.

UDP 162 Monitored Hosting SNMP Trap. This is the port used by Insight RS to listen Optional
Systems Device to SNMP traps.

Add protocol credentials and start discovery

To discover your monitored devices, complete the following sections:

Create a P6000 Command View protocol credential in the Insight RS

Console
P6000 Command View uses a secure logon design so there is a Windows account username and password
required to access the P6000 Command View UI. The P6000 Command View UI username and password is
also required for Insight RS to communicate with the EVA arrays, and must be manually entered into Insight
RS before EVA events can be processed. There are no default values for this username and password. The
account requires a minimum of read access (HP Storage Users) group privilege.
To configure a P6000 protocol credential in the Insight RS Console, complete the following steps:
1. In a web browser, log on to the Insight RS Console.
2. In the main menu, select Discovery and click the Credentials tab
3. In the Select and Configure Protocol drop-down list, select HP P6000 Command View.
4. Click New. The New Credential dialog box appears.
5. Type the Username and Password for the P6000 Command View instance. The Username must be a
user in the HP Storage Admins group on the management server.
6. Click Add.

HPE Insight Remote Support 7.10: Monitored Devices Configuration Guide Page 304 of 436
Chapter 25: Configuring P6000 and Enterprise Virtual Arrays

HPE recommends also creating credentials for the server that the P6000 Command View software is running
on.

Create an ELMC protocol credential in the Insight RS Console

To configure an ELMC protocol credential in the Insight RS Console, complete the following steps:
1. In a web browser, log on to the Insight RS Console.
2. In the main menu, select Discovery and click the Credentials tab.
3. From the Select and Configure Protocol drop-down list, select Event Log Monitoring Collector
(ELMC).
4. Click New. The New Credential dialog box appears.
Insight RS creates the protocol credential and it appears in the credentials table.

Create a protocol credential in the Insight RS Console for your

management server
Make sure you monitor your P6000 Command View management server with Insight RS. To be monitored by
Insight RS, the ProLiant Windows system hosting P6000 Command View has the same system requirements
and configuration as any ProLiant Windows server (see "Understanding monitored devices prerequisites" on
page 26). Make sure you create communication protocol credentials in the Insight RS Console. Your protocol
could be RIBCL, WMI, or SNMP, depending on which you chose to configure.
To configure a protocol credential in the Insight RS Console, complete the following steps:
1. In a web browser, log on to the Insight RS Console.
2. In the main menu, select Discovery and click the Credentials tab
3. In the Select and Configure Protocol drop-down list, select the protocol you configured on your
Windows server (RIBCL, WMI, or SNMP).
4. Click New. The New Credential dialog box appears.
5. Complete the required fields for your protocol.
6. Click Add.

Discover the EVA in the Insight RS Console

An EVA is not discovered directly. The EVA is located when discovering the management server that is
managing the EVA.

Important: When a new EVA array is added to an Insight RS environment that is already
configured, a manual Discovery of the server running P6000 Command View that is managing the
new array is required in order to detect the new EVA's warranty and contract information.

To discover the device from the Insight RS Console, complete the following steps:
1. In a web browser, log on to the Insight RS Console.
2. In the main menu, select Discovery and click the Sources tab.
3. Expand the IP Addresses section and add the IP address for your management server:

HPE Insight Remote Support 7.10: Monitored Devices Configuration Guide Page 305 of 436
Chapter 25: Configuring P6000 and Enterprise Virtual Arrays

a. Click New.
b. Select the Single Address, Address Range, or Address List option.
c. Type the IP address(es) of the devices to be discovered.
d. Click Add.
4. Click Start Discovery.

Verify discovery and device status

To verify the device was discovered correctly, complete the following steps:
1. In a web browser, log on to the Insight RS Console.
2. In the main menu, select Devices and click the Device Summary tab.

3. Make sure the Status column contains a success icon ( ).

If there is no success icon, determine which column has the problem and consult the Online Help for
troubleshooting information.

Verify warranty and contract information

Verify that the warranty and contract information was discovered correctly in the Insight RS Console:
1. In the Insight RS Console, navigate to Devices and click the EVA Device Name.
2. Expand the Hardware section, and make sure the Acquired Serial Number and Acquired Product
Number are correct. If they are not correct, type the correct values in the Override Serial Number and
Override Product Number fields and click Save Changes.

Verify communication between monitored device and

Insight RS
To verify communication between your monitored device and Insight RS, complete the following sections:

Sending a test event

To send a test event from P6000 Command View, complete the following steps:
1. In a web browser, log on to P6000 Command View.
2. In the left menu, select the EVA.

HPE Insight Remote Support 7.10: Monitored Devices Configuration Guide Page 306 of 436
Chapter 25: Configuring P6000 and Enterprise Virtual Arrays

3. On the General tab, click System Options.

4. On the System Options screen, under the Service heading, click Perform remote service test.
5. On the Perform Remote Service Test screen, click Perform Remote Service Test.
6. Click OK.
7. In the Insight RS Console, navigate to Devices → Service Events to verify that the event was received.

Verify collections in the Insight RS Console

Collections are not automatically run after discovery. HPE recommends that you manually run a collection
after discovery completes in order to verify connectivity. Run the collection schedule manually on the
Collection Services → Collection Schedules tab. For more information about scheduling collections, see the
Insight RS Help.
Verify that this collection ran successfully on the Collection Services → SAN Storage Collection Results tab
in the Insight RS Console.
1. Log on to the Insight RS Console.
2. In the main menu, select Collection Services and then click the SAN Storage Collection Results tab.
3. Expand the Storage Configuration Collection section.
4. Locate the entry for your device and check the Result column. If the collection was successful, a
success icon appears ( ). If it failed, an error icon appears ( ).

HPE Insight Remote Support 7.10: Monitored Devices Configuration Guide Page 307 of 436
Chapter 25: Configuring P6000 and Enterprise Virtual Arrays

Maintenance and troubleshooting

Enable User-Initiated Service Mode in P6000 Command View
User-Initiated Service Mode (UISM) provides a means of allowing Remote Support Diagnostic Service
incidents to be suppressed or revealed only to the client, while allowing the Remote Support Diagnostic
Technology to continue to monitor the device by writing a 'User Initiated Service Event' into the Device log.
Using UISM will reduce the number of non-actionable events that are created when you are installing software
or performing maintenance.
UISM is enabled through P6000 Command View. UISM will automatically transition back to normal mode
after an adjustable time delay expires or by manually disabling the mode. Two new P6000 Command View
management events will be created when UISM is enabled. The first will indicate the beginning of UISM and
will contain a timeout value in minutes within the event description. The second will indicate the end of UISM.
Being in this mode has no effect on the functionality of P6000 Command View or event handling within P6000
Command View. This mode is solely for the benefit of external support tools, such as Insight Remote
Support.
To enable User-Initiated Service Mode, complete the following steps:
1. Open P6000 Command View and select a device in the left menu tree.
2. On the General tab, click System Options.
3. On the System Options page, under the Service heading, select Configure User-Initiated Service
Mode (UISM).
4. On the Configure User Initiated Service Mode page, type a reason for the UISM in the Reason text area.
5. Modify the duration if necessary. The default is 30 minutes.
6. Click Start service mode.
7. In the pop-up window, click Start Service Mode to confirm that you want to enter UISM. The Configure
User Initiated Service Mode page will be updated to show that UISM is active, the Mode will have
changed, and the time left in the UISM will be displayed.
8. If you want to exit UISM before the duration has expired, you can click Stop service mode.

Perform a remote service test in P6000 Command View

The Remote Service Test provides a method to confirm a successful remote support setup and to
troubleshoot software communications problems. When a Remote Service Test is performed, Insight Remote
Support will receive the event and pass it on to HPE. HPE will then send the event back to the user. This
provides an end-to-end test that can be used test or troubleshoot the remote support software communication
path. The remote service test has no other effect within P6000 Command View beyond logging the event and
sending any configured notifications.
To perform a remote service test, complete the following steps:
1. Open P6000 Command View and select a device in the left menu tree.
2. On the System Options page, under the Service heading, select Perform remote service test.
3. On the Perform Remote Service Test page, click Perform remote service test.
4. Verify the test event was received in the Insight RS Console.

HPE Insight Remote Support 7.10: Monitored Devices Configuration Guide Page 308 of 436
Chapter 25: Configuring P6000 and Enterprise Virtual Arrays

Insight RS did not discover the EVA

Verify the EVA is managed by P6000 Command View on the target server
1. Open a browser to P6000 Command View.
2. Select the EVA array and verify you can navigate to components of the array.
3. Verify the WBEM Protocol settings are correctly set to port 5989 and the username and password for
SMI-S are set correctly for the version of P6000 Command View managing the array.
4. Verify SMI-S Service is running on management server: HP StorageWorks CIM Object Manager.

Troubleshooting the ELMC installation

If the ELMC installation fails on the management server, this can be due to the Windows Management
Instrumentation (WMI) service preventing access to required system files.
The solution is the stop the WMI service using the Windows Services Manager utility to unlock the files,
install ELMC, then restart the WMI service.

Configuring P6000 and Enterprise Virtual Arrays

using Array Based Management
EVA4400 and P6000 can be monitored using Array Based Management. The introduction of the EVA4400
included a new module to the HSV300 controller pair that installs Command View EVA on the array. This is
called Array Based Management (ABM) which has a network interface for access across the LAN. The ABM
is not capable of hosting SMI-S in the array, so SMI-S is required to be hosted elsewhere in the LAN to serve
as a proxy connection to the array.
The P6000 Command View installation kit allows for SMI-S to be installed independently on a designated
server. Install SMI-S on the Hosting Device or another supported server in the LAN.

Important: The ABM Fully Qualified Domain Name must not be the same as the EVA array name.
Insight RS has no way to differentiate between two devices that have the same name.

Fulfill configuration requirements

To configure your P6000 and Enterprise Virtual Arrays using ABM to be monitored by Insight RS, complete
the following sections:
Table 25.3 P6000 and Enterprise Virtual Array using ABM configuration steps
Task Complete?

Make sure Insight RS supports your P6000 disk array by checking the HPE Insight Remote
Support Release Notes.

Add P6000 Command View to the Insight RS Console.

Discover the P6000 in the Insight RS Console.

Add the device's Support Type and Support Identifier to the Insight RS Console.

HPE Insight Remote Support 7.10: Monitored Devices Configuration Guide Page 309 of 436
Chapter 25: Configuring P6000 and Enterprise Virtual Arrays

Configure monitored devices

To configure your monitored devices, complete the following section:

Configure firewall and port settings

Table 25.4 EVA Connectivity - Firewall/Port Requirements
Protocol Ports Source Destination Function Optional

ICMP N/A Hosting Monitored Provides system reachability (ping) check during Required
Device Systems system discovery and before other operations.

TCP 2372 Hosting P6000 ABM P6000/EVA Command View - Storage Collections for Required
Device EVA (HTTPS).

TCP 2373 Hosting P6000 ABM P6000/EVA Command View 9.x - Storage Collections Required
Device for P6000/EVA Array Based Management.

TCP 2374 Hosting P6000 ABM P6000/EVA Command View 10.x - Storage Required
Device Collections for P6000/EVA Array Based
Management.

TCP 5989 Hosting Monitored Secured WBEM CIMOM protocol over HTTPS/SOAP. Required
Device Systems This port is used to communicate with WBEM end
point nodes.

TCP 7905 Monitored Hosting Secure HTTP (HTTPS) port used by the listener Required
Systems Device running in the Director's Web Interface. The
monitored host connects to the Hosting Device on
this port (e.g. https://<hostname>:7905).

TCP 7906 Array Based Hosting Secure HTTP (HTTPS) port used by the listener Required
Management Device running in the Director's Web Interface. The
Module monitored host connects to the Hosting Device on
this port (e.g. https://<hostname>:7906).

TCP 7920 Hosting Monitored The Insight RS ELMC (formerly WCCProxy) process Required
Device Systems communicates with the Director on this port. This is a
proprietary protocol. Any connections that exchange
username and passwords use SSL. Not all
connections are SSL.

UDP 161 Hosting Monitored SNMP. This is the standard port used by SNMP Optional
Device Systems agents on monitored systems. The Hosting Device
sends requests to devices on this port.

UDP 162 Monitored Hosting SNMP Trap. This is the port used by Insight RS to Optional
Systems Device listen to SNMP traps.

Add Protocol credentials and start discovery

To discover your monitored devices, complete the following sections:

Create a P6000 Command View protocol in the Insight RS Console

To configure a P6000 protocol credential in the Insight RS Console, complete the following steps:

HPE Insight Remote Support 7.10: Monitored Devices Configuration Guide Page 310 of 436
Chapter 25: Configuring P6000 and Enterprise Virtual Arrays

1. In a web browser, log on to the Insight RS Console.

2. In the main menu, select Discovery and click the Credentials tab
3. In the Select and Configure Protocol drop-down list, select HP P6000 Command View.
4. Click New. The New Credential dialog box appears.
5. Type the Username and Password for the P6000 Command View instance.
Configure the credentials for the ABM that is running P6000 Command View and actively managing the
array. If the array is not being managed by the instance of P6000 Command View you are pointing to, you
will see the EVA array but Insight RS will not be able to obtain the Serial Number or Product Number
information.
6. Click Add.

Discover the ABM in the Insight RS Console

If you are managing the array from the P6000 Command View instance running on the Array Based
Management (ABM), then you need to discover the ABM.
To discover the device from the Insight RS Console, complete the following steps:
1. In a web browser, log on to the Insight RS Console.
2. In the main menu, select Discovery and click the Sources tab.
3. Expand the IP Addresses section and add the IP address for your device:
a. Click New.
b. Select the Single Address, Address Range, or Address List option.
c. Type the IP address(es) of the devices to be discovered.
d. Click Add.
4. Click Start Discovery.
5. After discovery completes successfully, browse to Devices in the main menu, and on the Device
Summary tab, click the array's Device Name to open the Device Details screen.
6. On the Device tab, expand the Warranty & Contract section and type the device's Support Type and
Support Identifier.
7. Click Save Changes to save the information.
8. Return to the Devices screen and verify that the Status of the device.

Verify discovery and device status

To verify the device was discovered correctly, complete the following steps:
1. In a web browser, log on to the Insight RS Console.
2. In the main menu, select Devices and click the Device Summary tab.

3. Make sure the Status column contains a success icon ( ).

If there is no success icon, determine which column has the problem and consult the Online Help for
troubleshooting information.

HPE Insight Remote Support 7.10: Monitored Devices Configuration Guide Page 311 of 436
Chapter 25: Configuring P6000 and Enterprise Virtual Arrays

Verify communication between monitored device and

Insight RS
To verify communication between your monitored device and Insight RS, complete the following section:

Verify collections in the Insight RS Console

Collections are not automatically run after discovery. HPE recommends that you manually run a collection
after discovery completes in order to verify connectivity. Run the collection schedule manually on the
Collection Services → Collection Schedules tab. For more information about scheduling collections, see the
Insight RS Help.
Verify that this collection ran successfully on the Collection Services → SAN Storage Collection Results tab
in the Insight RS Console.
1. Log on to the Insight RS Console.
2. In the main menu, select Collection Services and then click the SAN Storage Collection Results tab.
3. Expand the Storage Configuration Collection section.
4. Locate the entry for your device and check the Result column. If the collection was successful, a
success icon appears ( ). If it failed, an error icon appears ( ).

HPE Insight Remote Support 7.10: Monitored Devices Configuration Guide Page 312 of 436
 Chapter 26: Configuring StoreVirtual P4000
Storage systems
HPE Insight Remote Support software delivers secure remote support for your HPE servers, storage,
network, and SAN environments, which includes the P4000 SAN.

Note: HPE StoreVirtual Storage is the new name for HPE LeftHand Storage and HPE P4000 SAN
solutions. LeftHand Operating System (LeftHand OS) is the new name for SAN/iQ.

Important: Each P4000 Storage Node counts as 30 monitored devices within Insight RS.

Important: For every 100 P4000 devices being monitored by Insight RS, add 1 GB of free disk
space to the Hosting Device requirements.

P4000 documentation is available at: www.hpe.com/support/hpesc. Search for LeftHand P4000 SAN
Solutions.

Fulfill configuration requirements

To configure your P4000 Storage Systems to be monitored by Insight RS, complete the following sections:
Table 26.1 P4000 Storage system configuration steps
Task Complete?

Make sure Insight RS supports your P4000 Storage System by checking the HPE Insight Remote
Support Release Notes.

Install or upgrade CMC on the Hosting Device.

Install or upgrade LeftHand OS on the P4000.

Configure SNMP on the P4000.

Add the P4000 SAN Solution (SAN/iQ) protocol to the Insight RS Console.

Discover the P4000 Storage System in the Insight RS Console.

Send a test event to verify connectivity between your P4000 Storage System and Insight RS.

Install and configure communication software on

storage systems
To configure your monitored devices, complete the following sections:

Install and configure CMC on the Hosting Device

You need to do the complete install of Centralized Management Console (CMC) to install the SNMP MIBs. If
you do not modify the SNMP defaults that CMC uses, then SNMP should work with Insight Remote Support
without modification.

HPE Insight Remote Support 7.10: Monitored Devices Configuration Guide Page 313 of 436
Chapter 26: Configuring StoreVirtual P4000 Storage systems

Insight RS supports CMC 9.0 and higher (CMC 11.0 is recommended).

CMC 11.0 can be used to manage LeftHand OS 9.5, 10.x, 11.0, and 12.5 storage nodes.
CMC, Windows version has the following requirements:
Table 26.2 Memory and storage requirements for CMC
Memory size Free disk space

100 MB RAM during run-time 150 MB disk space for complete install

Note: CMC can be installed on the Hosting Device or it can be install on a separate system. If CMC
is already installed on another system, it does not need to be installed on the Hosting Device.

Install the centralized management console (CMC) on the computer that you will use to administer the SAN.
You need administrator privileges while installing the CMC.
1. Insert the P4000 Management SW DVD in the DVD drive. The installer should launch automatically. Or,
navigate to the executable (:\GUI\Windows\Disk1\InstData\VM\CMC_Installer.exe)
Or download CMC at:
h20392.www2.hpe.com/portal/swdepot/displayProductInfo.do?productNumber=StoreVirtualSW.
Click the Complete install option, which is recommended for users that use SNMP.

Note: If you already have Service Console installed, you don't need to disable it. Insight
Remote Support can co-exist with Service Console without conflict.

2. Use the Find Nodes wizard to discover the storage systems on the network, using either IP addresses or
host names, or by using the subnet and gateway mask of the storage network.

HPE Insight Remote Support 7.10: Monitored Devices Configuration Guide Page 314 of 436
Chapter 26: Configuring StoreVirtual P4000 Storage systems

The found storage systems appear in the available category in the CMC.

Upgrade LeftHand OS on the P4000 Storage systems

Note: LeftHand Operating System (LeftHand OS) is the new name for SAN/iQ.

HPE Insight Remote Support 7.10: Monitored Devices Configuration Guide Page 315 of 436
Chapter 26: Configuring StoreVirtual P4000 Storage systems

Use CMC to upgrade to LeftHand OS 9.5 or higher (LeftHand OS 11.0 is recommended) on the P4000 Storage
Systems. If your P4000 Storage Systems already has LeftHand OS 9.5 installed, you do not need to perform
this procedure.

Note: For LeftHand OS 9.5 devices, Patch Set 05 is required for all devices.

CMC version 9.0 and higher provide the option to download LeftHand OS upgrades and patches from HPE.
Once the current upgrades and patches are downloaded from HPE to the CMC system, CMC can be used to
update Management Groups or nodes with these changes.
When you upgrade the LeftHand OS software on a storage node, the version number changes. Check the
current software version by selecting a storage node in the navigation window and viewing the Details tab
window.

Note: Directly upgrading from LeftHand OS 9.5 to LeftHand OS 12.5 is not supported.

Important: When installing/upgrading LeftHand OS, do not modify the default SNMP settings. The
default settings are used by Insight Remote Support, and communication between the P4000
Storage System and the Hosting Device will not function properly if the SNMP settings are
modified. SNMP is enabled by default in LeftHand OS. In CMC 9.0 and higher, SNMP traps are
modified at the Management Group level, not at the node level.

Understand best practices

l LSMD upgrade — LSMD upgrade is required for upgrading from LeftHand OS 7.x.
l Virtual IP addresses — If a Virtual IP (VIP) address is assigned to a storage node in a cluster, the VIP
storage node needs to be upgraded last. The VIP storage node appears on the cluster iSCSI tab, see figure
"Find the Storage Node Running the VIP".
a. Upgrade the non-VIP storage nodes that are running managers, one at a time.
b. Upgrade the non-VIP non-manager storage nodes.
c. Upgrade the VIP storage node.
Figure 26.1 Find the Storage Node Running the VIP

l Remote Copy — If you are upgrading management groups with Remote Copy associations, you should
upgrade the remote management groups first. If you upgrade the primary group first, Remote Copy may
stop working temporarily, until both the primary management group and the remote group have finished
upgrading. Upgrade the primary site immediately after upgrading the remote site. Refer to "How to Verify
Management Group Version".

HPE Insight Remote Support 7.10: Monitored Devices Configuration Guide Page 316 of 436
Chapter 26: Configuring StoreVirtual P4000 Storage systems

Select the type of upgrade

CMC supports two methods of upgrades, as shown in figure "Viewing the CMC Upgrade/Installation
Window".
l One-at-a-time (recommended) - this is the default and only method that should be used if the storage
nodes exist in a management group.
l Simultaneous (advanced) - this allows you to upgrade multiple storage nodes at the same time if they are
not in a management group. Use this only for storage nodes in the Available pool.

Caution: Do not select "Simultaneous (advanced)" if your storage nodes are in a production cluster.

Figure 26.2 Viewing the CMC upgrade/installation window

Increase the size of the OS disk on the VSAs

Due to changes in the size of the VMware tools that get installed during software upgrades from pre-8.5
versions of LeftHand OS, you must increase the size of the OS disk before upgrading the VSA. Additional
space requirements are necessary for future software releases, as well. Therefore, we recommend increasing
the size of the OS disk to accommodate both requirements at this time.

HPE Insight Remote Support 7.10: Monitored Devices Configuration Guide Page 317 of 436
Chapter 26: Configuring StoreVirtual P4000 Storage systems

Note: These instructions apply to VMware ESX Server. Other VMware products have similar
instructions for extending a virtual disk. Please consult the appropriate VMware documentation for
the product you are using.

To increase the OS disk size on the VSA, complete the following steps:
1. Using the CMC, power off the VSA.
2. Open the VI Client and select VSA → Edit Settings → Hardware.
3. Select Hard disk 1 (verify that the Virtual Device Node is SCSI (0:0)).
4. Under Disk provisioning, changed the provisioned size to 8 GB.
5. Click OK.
6. Repeat these steps for Hard disk 2 (verify the Virtual Device Node is SCSI (0:1))
7. Using the VI Client, power on the VSA.
8. Find the VSA in the CMC and apply the upgrade.
Verify management group version
l When upgrading from version LeftHand OS 7.x to release 9.5 or higher, the management group version will
not move to the new release version until all storage nodes in the management group (and in the remote
management group if a Remote Copy relationship exists) are upgraded to release LeftHand OS 9.5 or
higher.
l When upgrading from LeftHand OS version 7.x to release 9.5 or higher, the upgrade process validates the
hardware identity of all of the storage nodes in the management group. If this validation fails for any reason,
the management group version will not be upgraded to 9.5 or higher. For example, if a management group
has a mix of platforms, some of which are unsupported by a software release; then only the supported
platforms get upgraded successfully, the management group version will not be upgraded if the
unsupported platforms remain in that management group.
To verify the management group version, complete the following steps:
1. In the CMC navigation window, select the management group, and then select the Registration tab. The
management group version number is at the top of the Registration Information section, as shown in
figure "Verifying the management group version number" below.
Figure 26.3 Verifying the management group version number

Check for patches

After you have upgraded LeftHand OS, use CMC to check for applicable patches required for your storage
node. CMC 9.0 and higher shows available patches and can be used to download them from HPE to the CMC
system.

HPE Insight Remote Support 7.10: Monitored Devices Configuration Guide Page 318 of 436
Chapter 26: Configuring StoreVirtual P4000 Storage systems

Configuring SNMP on the P4000 Storage System

Use the following procedure to verify your SNMP settings. If you did not modify the LeftHand OS SNMP
settings when you installed/upgraded LeftHand OS then you should not need to make any updates during the
following procedure.
With LeftHand OS, you can configure different severity Alert levels to send from the Management Group.
Under Insight Remote Support, configure each Management Group to send v1 SNMP traps of Critical and
Warning levels in Standard message text length.
LeftHand OS 9.5 and higher Management Groups configure the Hosting Device SNMP trap host destination
once at the Management Group level. Even though you only configure SNMP once at the Management Group
level under CMC 10.0 and higher, you need to configure SNMP on the Hosting Device to allow traps from all
LeftHand OS nodes.

Note: For LeftHand OS Management Groups, users can configure the Hosting Device trap host
destination P4000 CLI createSNMPTrapTarget command instead of using CMC. The
getGroupInfo command will show the current SNMP settings and SNMP trap host destinations
configured at the Management Group level.

Note: If using the P4000 CLI (CLIQ) createSNMPTrapTarget or getGroupInfo commands, the
path environment variable is not updated when the P4000 CLI is installed with Insight RS. You will
need to use the full path for the P4000 CLI, which is [InsightRS_Installation_Folder]\P4000.

To verify and/or update your SNMP settings, complete the following steps:
1. Open CMC.
2. Verify that SNMP is enabled for each storage system:

Note: LeftHand OS ships by default with SNMP enabled for all storage systems and
configured with the "Default" Access Control list.

Note: LeftHand OS Management Groups configure the Hosting Device SNMP trap host
destination once at the Management Group level. With LeftHand OS, you can configure
different severity Alert levels to send from the Management Group. Under Insight Remote
Support, configure each Management Group to send v1 SNMP traps of Critical and Warning
levels in Standard message text length.

a. Select SNMP in the left menu tree and open the SNMP General tab.
b. Verify that the Agent Status is enabled.
c. Verify that the P4000 Storage System SNMP Community String is set to public or the same value
configured in the Insight RS Console for SNMP discovery.
d. In the Access Control field, verify that either Default is listed or the Hosting Device host IP address
is listed. The Default option configures SNMP to be accessed by the public community string for
all IP addresses.

HPE Insight Remote Support 7.10: Monitored Devices Configuration Guide Page 319 of 436
Chapter 26: Configuring StoreVirtual P4000 Storage systems

Note: The SNMP settings on the P4000 Storage Systems need to match the SNMP
settings on the Hosting Device.

3. Select Alerts in the left menu tree, and verify that alerts are configured with the "trap" option for each
storage system.

Note: LeftHand OS ships by default with traps set for all alert cases.

HPE Insight Remote Support 7.10: Monitored Devices Configuration Guide Page 320 of 436
Chapter 26: Configuring StoreVirtual P4000 Storage systems

4. Add the Hosting Device IP address to the P4000 Storage System's SNMP trap send list. The Hosting
Device IP address is needed to configure SNMP traps on each storage system. Note that in CMC 9.0
and higher, SNMP traps are configured at the Management Group level, not at the node level.
a. Select SNMP in the left menu tree and open the SNMP Traps tab.
b. Open the Edit SNMP Traps dialog by browsing to SNMP Trap Tasks → Edit SNMP Traps.

HPE Insight Remote Support 7.10: Monitored Devices Configuration Guide Page 321 of 436
Chapter 26: Configuring StoreVirtual P4000 Storage systems

c. In the Edit SNMP Traps dialog, click Add.

d. In the Add IP or Hostname dialog, type the IP address or host name into the IP or Hostname field.
Verify that the Trap Version is v1, and click OK.

5. Repeat steps 3 to 4 for each P4000 Storage System. Alternatively, you could also configure one node
using steps 3 to 4, then use the CMC copy node configuration option to copy the configuration to all other
nodes.
6. Add an additional CMC user with read-only credentials. This is recommended if you don't want to have
the Hosting Device system administrator to have create/delete control of the storage systems.

HPE Insight Remote Support 7.10: Monitored Devices Configuration Guide Page 322 of 436
Chapter 26: Configuring StoreVirtual P4000 Storage systems

a. Select Administration in the left menu tree.

b. Create a user group with read-only access, if one does not already exist. Browse to Administrative
Tasks → New Group.

c. Create a new user. First select the group you created in the previous step, then go to Administrative
Tasks → New User. Type the User Name, Password, and click Add to add this user to the read-
only user group you created.

HPE Insight Remote Support 7.10: Monitored Devices Configuration Guide Page 323 of 436
Chapter 26: Configuring StoreVirtual P4000 Storage systems

Configure firewall and port settings

Table 26.3 P4000 Storage Systems Connectivity - Firewall/Port Requirements
Protocol Ports Source Destination Function Optional

ICMP N/A Hosting Monitored Provides system reachability (ping) check during Required
Device Systems system discovery and before other operations.

TCP 5989 CMC (can Monitored P4000 Centralized Management Console (CMC). Required
be running Systems
on Hosting
Device)

TCP 5989 Hosting Monitored Remote Support P4000 Integration Module - P4000 Required
Device Systems CLI API.

TCP 7905 Monitored Hosting Secure HTTP (HTTPS) port used by the listener Required
Systems Device running in the Director's Web Interface. The monitored
host connects to the Hosting Device on this port (e.g.
https://<hostname>:7905).

UDP 161 Hosting Monitored SNMP. This is the standard port used by SNMP Required
Device Systems agents on monitored systems. The Hosting Device
sends requests to devices on this port.

UDP 162 Monitored Hosting SNMP Trap. This is the port used by Insight RS to Required
Systems Device listen to SNMP traps.

Add protocol credentials and start discovery

To discover your monitored devices, complete the following sections:

HPE Insight Remote Support 7.10: Monitored Devices Configuration Guide Page 324 of 436
Chapter 26: Configuring StoreVirtual P4000 Storage systems

Add P4000 SAN Solution (SAN/iQ) protocol to the Insight

RS Console
To add the P4000 SAN Solution (SAN/iQ) protocol, complete the following steps:
1. In a web browser, log on to the Insight RS Console (https://<hosting_device_ip_or_fqdn>:7906.)
2. Create a Named Credential for every set of Management Group credentials:
a. In the Insight RS Console, navigate to Company Information → Named Credentials.
b. Click Add New Credential.
c. Type a Credential Name.
d. In the Protocol drop-down list, select P4000 SAN Solution (SAN/iQ).
e. Type the Username and Password for the Management Group created in "Configuring SNMP on the
P4000 Storage System" on page 319. These credentials can be either full LeftHand OS management
group or read-only LeftHand OS management group credentials.
f. Click Save.
3. Add Discovery credentials for the P4000 devices:
a. In the Insight RS Console, navigate to Discovery → Credentials.
b. Create discovery protocol credentials for each Named Credential created earlier.
i. In the Select and Configure Protocol drop-down list, select P4000 SAN Solution
(SAN/iQ).
ii. Click New.
iii. In the Named Credential drop-down list, select the Named Credential created earlier.
iv. Click Add.

Discover the P4000 in the Insight RS Console

To discover the device from the Insight RS Console, complete the following steps:
1. In a web browser, log on to the Insight RS Console.
2. In the main menu, select Discovery and click the Sources tab.
3. Expand the IP Addresses section and add the IP address for your device:
a. Click New.
b. Select the Single Address, Address Range, or Address List option.
c. Type the IP address(es) of the devices to be discovered.

HPE Insight Remote Support 7.10: Monitored Devices Configuration Guide Page 325 of 436
Chapter 26: Configuring StoreVirtual P4000 Storage systems

Note: When discovering new P4000 devices, do not include any P4000 Management
Group Virtual IP (VIP) addresses. VIP addresses are created when you create and
configure P4000 clusters. Instead, discover P4000 devices using individual IP addresses,
or create IP discovery ranges excluding all P4000 VIP addresses.
If you do discover a P4000 VIP address, you should delete the managed entity for the VIP
address from Insight Remote Support Advanced before running any collections or
capturing any test traps. After deleting the VIP address entity, re-discover the node using
the actual IP address for the P4000 device.

d. Click Add.
4. Click Start Discovery.

Note: Insight RS filters out iLO 4 but not iLO 2 or iLO 3 devices. If an iLO 2 or iLO 3 device is
discovered, manually deleted them on the Device Details screen.

Verify discovery
To verify the P4000 was discovered correctly, complete the following steps:
1. Verify that the appropriate protocols have been assigned to the P4000 device:
a. In the Insight RS Console, navigate to Devices and click the P4000 Device Name.
b. On the Credentials tab, verify that verify that the P4000 SAN Solution (SAN/iQ) and SNMPv1
protocols have been assigned to the device.

Add warranty and contract information

To add the P4000 device's warranty and contract information to Insight RS, complete the following steps:
1. In the Insight RS Console, navigate to Devices and click the P4000 Device Name.
2. Expand the Hardware section, and type the Serial Number in the Override Serial Number field and the
Product Number in the Override Product Number field.
3. Click Save Changes.

Verify discovery and device status

To verify the device was discovered correctly, complete the following steps:
1. In a web browser, log on to the Insight RS Console.
2. In the main menu, select Devices and click the Device Summary tab.

3. Make sure the Status column contains a success icon ( ).

If there is no success icon, determine which column has the problem and consult the Online Help for
troubleshooting information.

HPE Insight Remote Support 7.10: Monitored Devices Configuration Guide Page 326 of 436
Chapter 26: Configuring StoreVirtual P4000 Storage systems

Verify communication between monitored device

and Insight RS
To verify communication between your monitored device and Insight RS, complete the following sections:

Send a test event

To verify that the P4000 Storage System(s) are communicating with the Hosting Device, open CMC and
select at least one storage node and send a test trap to the Hosting Device. Select SNMP in the left menu tree
and open the SNMP Traps tab. In the SNMP Trap Tasks drop-down list, select Send Test Trap.

Note: In CMC, SNMP traps are configured at the Management Group level, not at the node level.

Go to Hosting Device configurations to verify that the test event was posted to the Hosting Device logs. The
CMC read-only credentials were verified during device discovery when each LeftHand OS device was added
to Hosting Device monitored listed.

Verify collections in the Insight RS Console

Collections are not automatically run after discovery. HPE recommends that you manually run a collection
after discovery completes in order to verify connectivity. Run the collection schedule manually on the

HPE Insight Remote Support 7.10: Monitored Devices Configuration Guide Page 327 of 436
Chapter 26: Configuring StoreVirtual P4000 Storage systems

Collection Services → Collection Schedules tab. For more information about scheduling collections, see the
Insight RS Help.
Verify that this collection ran successfully on the Collection Services → Basic Collection Results tab in the
Insight RS Console.
1. Log on to the Insight RS Console.
2. In the main menu, select Collection Services and then click the Basic Collection Results tab.
3. Expand the P4000 Family Configuration Collection section.
4. Locate the entry for your device and check the Result column. If the collection was successful, a
success icon appears ( ). If it failed, an error icon appears ( ).

HPE Insight Remote Support 7.10: Monitored Devices Configuration Guide Page 328 of 436
 Chapter 27: Configuring P2000 G3, MSA
1040/2040/2050 storage
Fulfill configuration requirements
To configure your P2000 G3, MSA 1040, MSA 2040, and MSA 2050 storage to be monitored by Insight RS,
complete the following sections:
Table 27.1 P2000, MSA 1040, MSA 2040, and MSA 2050 configuration steps
Task Complete?

Make sure Insight RS supports your MSA by checking the HPE Insight Remote Support Release
Notes.

Configure SNMP on the MSA.

Configure WBEM on the MSA.

Add the SNMP protocol to the Insight RS Console.

Add the WBEM protocol to the Insight RS Console.

Discover the MSA server in the Insight RS Console.

Install and configure communication software on

arrays
To configure your monitored devices, complete the following sections:

Configure SNMP on your MSA

Each MSA monitored device has factory-installed SNMP on the device.
To access the Storage Management Utility for the MSA and configure SNMP for Insight Remote Support,
complete the following steps:
1. Log on to the MSA Storage Management Utility (SMU).

Note: For basic information about setting up this tool and managing your credentials, consult
the MSA Storage Management Utility documentation at: www.hpe.com/support/hpesc.

2. Once you have logged into the utility, select Configuration → Services → Management.
3. Make sure that SNMP is selected from the Network Management Services list and click Apply.

Important: SNMP should be active by default. If for any reason it is not active, Insight Remote
Support will not be supported. It is critical to verify SNMP is active.

HPE Insight Remote Support 7.10: Monitored Devices Configuration Guide Page 329 of 436
Chapter 27: Configuring P2000 G3, MSA 1040/2040/2050 storage

4. From the menu select Configuration → Services → SNMP Notification.

5. On the Configure SNMP Notification page, modify the SNMP settings to include the Hosting Device
as an SNMP Trap Host and select your Notification Level from the drop-down list (the Informational
level is recommended).

HPE Insight Remote Support 7.10: Monitored Devices Configuration Guide Page 330 of 436
Chapter 27: Configuring P2000 G3, MSA 1040/2040/2050 storage

6. Click Apply to commit your changes.

7. Exit the utility and discover your MSA in the Insight RS Console.

About WBEM on the P2000 G3, MSA 1040/2040/2050

The SMI-S provider for the P2000 G3 MSA, MSA 1040, MSA 2040, and MSA 2050 is integrated in the
firmware and delivered with the P2000 G3, MSA 1040, MSA 2040, and MSA 2050 series disk arrays. It
provides a WBEM-based management framework. Insight RS can interact with this embedded provider
directly and does not need an intermediate proxy provider.
No configuration of WBEM on the P2000 G3, MSA 1040, MSA 2040, and MSA 2050 is necessary.

Important: The user you configure for the P2000 must also have access to SMI-S. By default users
only have access to the WBI and CLI. You must modify the user to include SMI-S or collections will
fail.

Add protocol credentials and start discovery

To discover your monitored devices, complete the following sections:

Create an SNMPv1 protocol credential in Insight RS

Console
If your device's SNMP community string is set to public and your community access mode is read only,
Insight RS automatically associates an SNMPv1 protocol with your device. If you use a different community
string or use a nonstandard port, you must create an SNMPv1 protocol credential in the Insight RS Console.
To configure SNMPv1 in the Insight RS Console, complete the following steps:
1. In a web browser, log on to the Insight RS Console.
2. In the main menu, select Discovery and click the Credentials tab.
3. From the Select and Configure Protocol drop-down list, select Simple Network Management Protocol
Version 1, V2C (SNMPv1, SNMPv2C).
4. Click New. The New Credential dialog box appears.
5. Type the Community String you have configured on your device.
6. Click Add.
Insight RS creates the protocol credential and it appears in the credentials table.

HPE Insight Remote Support 7.10: Monitored Devices Configuration Guide Page 331 of 436
Chapter 27: Configuring P2000 G3, MSA 1040/2040/2050 storage

Create a WBEM protocol credential in Insight RS Console

To configure WBEM in the Insight RS Console, complete the following steps:
1. In a web browser, log on to the Insight RS Console.
2. In the main menu, select Discovery and click the Credentials tab.
3. From the Select and Configure Protocol drop-down list, select Web-Based Enterprise Management
(WBEM).
4. Click New. The New Credential dialog box appears.
5. Type the Username and Password used to access the Storage Management Utility interface on the
MSA.
6. Click Add.
Insight RS creates the protocol credential and it appears in the credentials table.

Discover the device in the Insight RS Console

To discover the device from the Insight RS Console, complete the following steps:
1. In a web browser, log on to the Insight RS Console.
2. In the main menu, select Discovery and click the Sources tab.
3. Expand the IP Addresses section and add the IP address for your device:
a. Click New.
b. Select the Single Address, Address Range, or Address List option.
c. Type the IP address(es) of the MSA devices to be discovered.

Important: In a dual-controller system, you must discover both controller A and controller
B if both exist. If you do not discover both controllers, events that originate from the
controller that was not discovered could be lost.

d. Click Add.
4. Click Start Discovery.

Verify discovery and device status

To verify the device was discovered correctly, complete the following steps:
1. In a web browser, log on to the Insight RS Console.
2. In the main menu, select Devices and click the Device Summary tab.

3. Make sure the Status column contains a success icon ( ).

If there is no success icon, determine which column has the problem and consult the Online Help for
troubleshooting information.

HPE Insight Remote Support 7.10: Monitored Devices Configuration Guide Page 332 of 436
Chapter 27: Configuring P2000 G3, MSA 1040/2040/2050 storage

Verify communication between monitored device

and Insight RS
To verify communication between your monitored device and Insight RS, complete the following sections:

Verify service event monitoring

To send a test event from the MSA, complete the following steps:
1. In a web browser, log on to the MSA Storage Management Utility (SMU).
2. Select Tools → Send Test Notification.
3. In the Send Test Notifications window, click Send.
4. Click OK to acknowledge that the message was sent.
5. Sign out of SMU.

Verify collections in the Insight RS Console

Collections are not automatically run after discovery. HPE recommends that you manually run a collection
after discovery completes in order to verify connectivity. Run the collection schedule manually on the
Collection Services → Collection Schedules tab. For more information about scheduling collections, see the
Insight RS Help.
Verify that this collection ran successfully on the Collection Services → SAN Storage Collection Results tab
in the Insight RS Console.
1. Log on to the Insight RS Console.
2. In the main menu, select Collection Services and then click the SAN Storage Collection Results tab.
3. Expand the Storage Configuration Collection section.
4. Locate the entry for your device and check the Result column. If the collection was successful, a
success icon appears ( ). If it failed, an error icon appears ( ).

HPE Insight Remote Support 7.10: Monitored Devices Configuration Guide Page 333 of 436
 Chapter 28: Configuring StoreEasy Storage
systems
Insight Remote Support (RS) requires WMI to be installed and configured on your StoreEasy Storage system
(formerly Network Storage Systems) in order for Insight RS to communicate with your device for discovery,
event monitoring, and collections.
WMI comes pre-installed on StoreEasy Storage systems. No additional configuration of WMI is necessary.
However, you must add the WMI protocol credentials in the Insight RS Console for Insight RS to
communicate with your device.

Fulfill configuration requirements

To configure your StoreEasy Storage system to be monitored by Insight RS, complete the following sections:
Table 28.1 StoreEasy Storage system configuration steps
Task Complete?

Check the HPE Insight Remote Support Release Notes to make sure your StoreEasy Storage
system is supported.

Add the WMI protocol to the Insight RS Console.

Discover the StoreEasy Storage system in the Insight RS Console.

Send a test event to verify connectivity between your StoreEasy Storage system and Insight RS.

Configure StoreEasy devices

To configure your monitored devices, complete the following section:

Configure firewall
StoreEasy devices ship with Windows Firewall with Advanced Security enabled. To allow WMI through the
Windows Firewall, you must enable additional inbound and outbound rules.
To configure Windows Firewall on the StoreEasy device, complete the following steps:
1. Open the Windows Firewall from the Server Manager.
2. Click on the Tools menu.
3. Select Windows Firewall with Advanced Security.
4. Select the Inbound Rules link from the left menu and make sure the following inbound rules are enabled:
l File and Printer Sharing (Echo Request - ICMPv4-In)
l Windows Management Instrumentation (DCOM-In)
l Windows Management Instrumentation (WMI-In)
5. Select the Outbound Rules link from the left menu and make sure the following outbound rules are
enabled:

HPE Insight Remote Support 7.10: Monitored Devices Configuration Guide Page 334 of 436
Chapter 28: Configuring StoreEasy Storage systems

l File and Printer Sharing (Echo Request - ICMPv4-Out)

l Windows Management Instrumentation (WMI-Out)
More information regarding security in Insight RS can be found in the HPE Insight Remote Support Security
White Paper at: www.hpe.com/info/insightremotesupport/docs.

Note: You can confirm which protocols discovery associated with the StoreEasy device by clicking
the StoreEasy device name on the Devices screen, and then selecting the Credentials tab.
Confirm that WMI is one of the discovered credentials. SNMP should not be among the discovered
credentials.

Add protocol credentials and start discovery

To discover your monitored devices, complete the following sections:

Create a WMI protocol credential in Insight RS Console

WMI credentials must be set for each StoreEasy Storage system within the Insight RS Console before it can
be monitored. If you change your WMI credentials at any time, you must modify the entry for those credentials
in the Insight RS Console.
To configure WMI in the Insight RS Console, complete the following steps:
1. In a web browser, log on to the Insight RS Console.
2. In the main menu, select Discovery and click the Credentials tab.
3. From the Select and Configure Protocol drop-down list, select Windows Management
Instrumentation (WMI).
4. Click New. The New Credential dialog box appears.
5. Type the Username and Password you have configured on your device.
6. Click Add.
Insight RS creates the protocol credential and it appears in the credentials table.

Discover the device in the Insight RS Console

To discover the device from the Insight RS Console, complete the following steps:
1. In a web browser, log on to the Insight RS Console.
2. In the main menu, select Discovery and click the Sources tab.
3. Expand the IP Addresses section and add the IP address for your device:
a. Click New.
b. Select the Single Address, Address Range, or Address List option.
c. Type the IP address(es) of the devices to be discovered.
d. Click Add.
4. Click Start Discovery.

HPE Insight Remote Support 7.10: Monitored Devices Configuration Guide Page 335 of 436
Chapter 28: Configuring StoreEasy Storage systems

Verify discovery and device status

To verify the device was discovered correctly, complete the following steps:
1. In a web browser, log on to the Insight RS Console.
2. In the main menu, select Devices and click the Device Summary tab.

3. Make sure the Status column contains a success icon ( ).

If there is no success icon, determine which column has the problem and consult the Online Help for
troubleshooting information.

Verify communication between monitored device

and Insight RS
To verify communication between your monitored device and Insight RS, complete the following sections:

Send a WMI test indication to the Hosting Device

System Management Homepage (SMH) also comes pre-installed on your StoreEasy Storage system. It
provides additional reporting capabilities on the device itself. While not mandatory for Insight Remote Support,
SMH can be used to work with the WMI protocol such as sending test events.
To verify connectivity from the device to Insight RS, send a WMI test indication to the Hosting Device and
then verify the test indication was received in the Insight RS Console.
1. In a web browser, access System Management Homepage (SMH) on the monitored device: https://
[ipaddress]:2381.
2. Log on using the administrator user name and password for the monitored device.
If you are not prompted for a logon, check the upper right corner of the SMH interface and click the Sign
In link. If you are not logged in as an administrator for the monitored device you will not have all of the
relevant configuration options.
3. In the top menu bar, click Settings.
4. If you chose to install WMI with SPP, it will be set as your Data Source. In the Test Indication pane, click
Send Test Indication.

HPE Insight Remote Support 7.10: Monitored Devices Configuration Guide Page 336 of 436
Chapter 28: Configuring StoreEasy Storage systems

5. In the Send Test Indication screen, select an Event ID type (any will work) and click Send.

Viewing test events in the Insight RS Console

After sending the test indication, verify it arrived in the Insight RS Console.
To verify the test indication arrived, complete the following steps:
1. In a web browser, log on to the Insight RS Console.
2. In the main menu, select Service Events. If your monitored device is properly configured, the event will
appear in the Service Events Information pane.

Verify collections
Collections are not automatically run after discovery. HPE recommends that you manually run a collection
after discovery completes in order to verify connectivity. Run the collection schedule manually on the
Collection Services → Collection Schedules tab. For more information about scheduling collections, see the
Insight RS Help.
Also note that StoreEasy Storage systems use Server Basic Configuration Collections rather than Storage
Configuration Collections.
Verify that this collection ran successfully on the Collection Services → Basic Collection Results tab in the
Insight RS Console.

HPE Insight Remote Support 7.10: Monitored Devices Configuration Guide Page 337 of 436
Chapter 28: Configuring StoreEasy Storage systems

1. Log on to the Insight RS Console.

2. In the main menu, select Collection Services and then click the Basic Collection Results tab.
3. Expand the Server Basic Configuration Collection section.
4. Locate the entry for your device and check the Result column. If the collection was successful, a
success icon appears ( ). If it failed, an error icon appears ( ).

HPE Insight Remote Support 7.10: Monitored Devices Configuration Guide Page 338 of 436
 Chapter 29: Configuring StoreAll Storage
systems
Note: HPE StoreAll Storage is the new name for HPE IBRIX Storage.

Note the following limitations:

l For X9000 systems, the Insight Remote Support implementation is limited to hardware events.
l Some manual configurations require that the X9320 and X9300 nodes be recognized as a X9000 solution.
See section "Configure warranty and contract information" on page 341.

Fulfill configuration requirements

To configure your storage systems to be monitored by Insight RS, complete the following sections:
Table 29.1 StoreAll Storage system configuration steps
Task Complete?

Make sure Insight RS supports your StoreAll Storage system by checking the HPE Insight
Remote Support Release Notes.

Configure SNMP on the file server nodes.

Restart Insight Management Agents.

Add the SNMP protocol to the Insight RS Console.

Discover the StoreAll Storage system in the Insight RS Console.

Configure warranty and contract information in the Insight RS Console.

Send a test event to verify connectivity between your StoreAll Storage system and Insight RS.

Install and configure communication software on

storage systems
To configure your monitored devices, complete the following sections:

Configure SNMP on the file serving nodes

1. Run the /sbin/hpsnmpconfig script, which configures SNMP to integrate the Hosting Device running
on the Windows server with the System Management Homepage on the file serving node. The script
edits the /etc/snmp/snmpd.conf file, adding entries similar to the following:
# Following entries were added by HPE Insight Management Agents at
# <date> <time> UTC <year>
dlmod cmaX /usr/lib64/libcmaX64.so
rwcommunity public 127.0.0.1
rocommunity public 127.0.0.1
rwcommunity public <Manager IP>

HPE Insight Remote Support 7.10: Monitored Devices Configuration Guide Page 339 of 436
Chapter 29: Configuring StoreAll Storage systems

rocommunity public <Manager IP>

trapcommunity public
trapsink <Manager IP> public
syscontact
syslocation
# ---------------------- END --------------------

2. To add more than one SNMP Manager IP, copy the following lines:
rwcommunity public <Manager IP>
rocommunity public <Manager IP>
trapsink <Manager IP> public

3. After updating the snmpd.conf file, restart the snmpd service:

# service snmpd restart
For more information about the /sbin/hpsnmpconfig script, see “SNMP Configuration” in the hp-snmp-
agents(4) man page. For information about System Management Homepage, go to:
www.hpe.com/info/SMH.

Important: The /opt/hp/hp-snmp-agents/cma.conf file controls certain actions of the

SNMP agents. You can add a trapIf entry to the file to configure the IP address used by the
SNMP daemon when sending traps. For example, to send traps using the IP address of the
eth1 interface, add the following:
trapIf eth1
Then restart the SNMP agents:
service hp-snmp-agents restart
For more information about the cma.conf file, see Section 3.1 of the Managing ProLiant
servers with Linux HOWTO at:
http://h20565.www2.hpe.com/hpsc/doc/public/display?docId=emr_na-c00223285.

Start or restart Insight Management Agents

On the X9000, start or restart the following services:
l System Management Homepage:
# service hpsmhd restart
l SNMP Agent:
# service snmpd restart
l HPE SNMP Agents:
# service hp-snmp-agents start
To ensure that hp-snmp-agents restarts when the system is rebooted, type the following command:
# chkconfig hp-snmp-agents on

HPE Insight Remote Support 7.10: Monitored Devices Configuration Guide Page 340 of 436
Chapter 29: Configuring StoreAll Storage systems

Add protocol credentials and start discovery

To discover your monitored devices, complete the following sections:

Create an SNMPv1 protocol credential in the Insight RS

Console
If your device's SNMP community string is set to public and your community access mode is read only,
Insight RS automatically associates an SNMPv1 protocol with your device. If you use a different community
string or use a nonstandard port, you must create an SNMPv1 protocol credential in the Insight RS Console.
To configure SNMPv1 in the Insight RS Console, complete the following steps:
1. In a web browser, log on to the Insight RS Console.
2. In the main menu, select Discovery and click the Credentials tab.
3. From the Select and Configure Protocol drop-down list, select Simple Network Management Protocol
Version 1, V2C (SNMPv1, SNMPv2C).
4. Click New. The New Credential dialog box appears.
5. Type the Community String you have configured on your device.
6. Click Add.
Insight RS creates the protocol credential and it appears in the credentials table.

Discover the device in the Insight RS Console

To discover the device from the Insight RS Console, complete the following steps:
1. In a web browser, log on to the Insight RS Console.
2. In the main menu, select Discovery and click the Sources tab.
3. Expand the IP Addresses section and add the IP address for your device:
a. Click New.
b. Select the Single Address, Address Range, or Address List option.
c. Type the IP address(es) of the devices to be discovered.
d. Click Add.
4. Click Start Discovery.

Configure warranty and contract information

Configure the Insight RS Console to enable remote support for X9000 systems.
l Custom field settings for X9300/X9320
Servers are discovered with their IP addresses. When a server is discovered, edit the system properties in
the Insight RS Console. In the main menu, click Devices, then click the device name of your system.
On the Device tab, in the Hardware section:

HPE Insight Remote Support 7.10: Monitored Devices Configuration Guide Page 341 of 436
Chapter 29: Configuring StoreAll Storage systems

l Type the X9000 enclosure product number as the Override Product Number
l Type MC DATACENTER or MC HYPERSCALE as the Custom Delivery ID
On the Device tab, in the Warranty & Contract section:
l Type the appropriate Support Type and Support Identifier
l Custom field settings for MSA Storage Management Utility
Configure SNMP settings on the MSA Storage Management Utility section. (For more information, see
“Configuring SNMP event notification in SMU” in the 2300 Modular Smart Array Reference Guide at:
www.hpe.com/support/hpesc.)
A Modular Storage Array (MSA) unit should be discovered with its IP address. Once discovered, locate the
Entitlement Information section of the Contract and Warranty Information page and update the following:
l Type MC DATACENTER or MC HYPERSCALE as the Custom Delivery ID
l Type the appropriate Support Type and Support Identifier

Note: For storage support on X9300 systems, do not set the Custom Delivery ID. (The MSA is an
exception; the Custom Delivery ID is set as previously described.)

Verify discovery and device status

To verify the device was discovered correctly, complete the following steps:
1. In a web browser, log on to the Insight RS Console.
2. In the main menu, select Devices and click the Device Summary tab.

3. Make sure the Status column contains a success icon ( ).

If there is no success icon, determine which column has the problem and consult the Online Help for
troubleshooting information.

Verify communication between monitored device

and Insight RS
To verify communication between your monitored device and Insight RS, complete the following sections:

Send a test trap

To determine whether the traps are working properly, send a generic test trap with the following command:
snmptrap -v1 -c public <Hosting Device IP> .1.3.6.1.4.1.232 <Managed System IP> 6 11003
1234 .1.3.6.1.2.1.1.5.0 s test .1.3.6.1.4.1.232.11.2.11.1.0 i 0
.1.3.6.1.4.1.232.11.2.8.1.0 s "X9000 remote support testing"
For example, if the Hosting Device IP address is 10.2.2.2 and the X9000 node is 10.2.2.10, type the following:
snmptrap -v1 -c public 10.2.2.2 .1.3.6.1.4.1.232 10.2.2.10 6 11003 1234
.1.3.6.1.2.1.1.5.0 s test .1.3.6.1.4.1.232.11.2.11.1.0 i 0 .1.3.6.1.4.1.232.11.2.8.1.0 s
"X9000 remote support testing"

HPE Insight Remote Support 7.10: Monitored Devices Configuration Guide Page 342 of 436
Chapter 29: Configuring StoreAll Storage systems

For Insight Remote Support, replace the Hosting Device IP address with the IP address of the Insight Remote
Support server.

Verify collections
Collections are not automatically run after discovery. HPE recommends that you manually run a collection
after discovery completes in order to verify connectivity. Run the collection schedule manually on the
Collection Services → Collection Schedules tab. For more information about scheduling collections, see the
Insight RS Help.
Also note that StoreAll Storage systems use Server Basic Configuration Collections rather than Storage
Configuration Collections.
Verify that this collection ran successfully on the Collection Services → Basic Collection Results tab in the
Insight RS Console.
1. Log on to the Insight RS Console.
2. In the main menu, select Collection Services and then click the Basic Collection Results tab.
3. Expand the Server Basic Configuration Collection section.
4. Locate the entry for your device and check the Result column. If the collection was successful, a
success icon appears ( ). If it failed, an error icon appears ( ).

HPE Insight Remote Support 7.10: Monitored Devices Configuration Guide Page 343 of 436
 Chapter 30: Configuring StoreOnce Backup
(D2D) systems
Fulfill configuration requirements
To configure your StoreOnce Backup (D2D) systems to be monitored by Insight RS, complete the following
sections:
Table 30.1 StoreOnce Backup (D2D) system configuration steps
Task Complete?

Make sure Insight RS supports your StoreOnce Backup (D2D) System by checking the HPE
Insight Remote Support Release Notes.

Verify Firmware version on the StoreOnce Backup (D2D) System.

Configure SNMP on the StoreOnce Backup (D2D) System.

Add the SNMP protocol to the Insight RS Console.

Discover the StoreOnce Backup (D2D) System in the Insight RS Console.

Install and configure communication software on

backup systems
To configure your monitored devices, complete the following sections:

Verify the firmware version

Insight RS only supports StoreOnce Backup systems that use firmware version 2.1.03 or above. Check the
firmware version in the StoreOnce Backup user interface as shown below. If your firmware version is older
than version 2.1.03, update your firmware to a supported version.

Configure SNMP on your StoreOnce Backup (D2D) systems

You must add the Hosting Device as a trap destination on your D2D Backup Systems for service events to
reach Insight RS.

HPE Insight Remote Support 7.10: Monitored Devices Configuration Guide Page 344 of 436
Chapter 30: Configuring StoreOnce Backup (D2D) systems

Configure SNMP for StoreOnce Gen2 Backup (D2D) systems

To configure SNMP for StoreOnce Backup (D2D) Systems, complete the following steps:
1. Log on to the StoreOnce Backup System as "administrator" using https://<StoreOnce_Backup_IP>.
2. Click the Configuration tab.
3. On the Device Configuration pane, click the SNMP tab.
4. Click Edit, then enable the SNMP agent by selecting the SNMP Enabled check box.

5. Use the Hosting Device IP address to add a destination.

Configure SNMP for StoreOnce Gen3 B6200 and 2600/4200/4400

Backup systems
To configure the StoreOnce Backup B6200 and 2600/4200/4400 Backup Systems to send traps to Insight
Remote Support, complete the following steps:
1. Log on to the StoreOnce Backup System using the SSH protocol (Using "putty.exe" or a similar tool).
2. Check the current SNMP configuration by issuing the CLI command: snmp show config.
3. If the SNMP "State" displays as "off" run the CLI command: snmp enable.
4. To add your Hosting Device as a Trap Destination use: snmp add trapsink <IP address of Hosting
Device> events alert.

HPE Insight Remote Support 7.10: Monitored Devices Configuration Guide Page 345 of 436
Chapter 30: Configuring StoreOnce Backup (D2D) systems

5. Check that the current SNMP configuration shows the trap destination that you just configured by using:
snmp show config.
6. Type exit to log off.

Add protocol credentials and start discovery

To discover your monitored devices, complete the following sections:

Create an SNMPv1 protocol credential in the Insight RS

Console
If your device's SNMP community string is set to public and your community access mode is read only,
Insight RS automatically associates an SNMPv1 protocol with your device. If you use a different community
string or use a nonstandard port, you must create an SNMPv1 protocol credential in the Insight RS Console.
To configure SNMPv1 in the Insight RS Console, complete the following steps:
1. In a web browser, log on to the Insight RS Console.
2. In the main menu, select Discovery and click the Credentials tab.
3. From the Select and Configure Protocol drop-down list, select Simple Network Management Protocol
Version 1, V2C (SNMPv1, SNMPv2C).
4. Click New. The New Credential dialog box appears.
5. Type the Community String you have configured on your device.
6. Click Add.
Insight RS creates the protocol credential and it appears in the credentials table.

Discover the device in the Insight RS Console

In a cluster environment, discover the Virtual IP (VIP), which points to the Active Fusion Manager (FM) node.
If the active node fails, the VIP will change over to the new active node, and Insight RS will continue to
monitor the nodes in the cluster through the VIP. The VIP should not change, but if it does, then you must
rediscover the VIP in Insight RS.
To discover the device from the Insight RS Console, complete the following steps:
1. In a web browser, log on to the Insight RS Console.
2. In the main menu, select Discovery and click the Sources tab.
3. Expand the IP Addresses section and add the IP address for your device:
a. Click New.
b. Select the Single Address, Address Range, or Address List option.
c. Type the IP address(es) of the devices to be discovered.
d. Click Add.
4. Click Start Discovery.

HPE Insight Remote Support 7.10: Monitored Devices Configuration Guide Page 346 of 436
Chapter 30: Configuring StoreOnce Backup (D2D) systems

Verify discovery and device status

To verify the device was discovered correctly, complete the following steps:
1. In a web browser, log on to the Insight RS Console.
2. In the main menu, select Devices and click the Device Summary tab.

3. Make sure the Status column contains a success icon ( ).

If there is no success icon, determine which column has the problem and consult the Online Help for
troubleshooting information.

HPE Insight Remote Support 7.10: Monitored Devices Configuration Guide Page 347 of 436
 Chapter 31: Configuring Virtual Library
Systems
Fulfill configuration requirements
To configure your Virtual Library Systems to be monitored by Insight RS, complete the following sections:
Table 31.1 Virtual Library System configuration steps
Task Complete?

Make sure Insight RS supports your Virtual Library System by checking the HPE Insight Remote
Support Release Notes.

Configure SNMP on the Virtual Library System.

Discover the Virtual Library System in the Insight RS Console.

Send a test event to verify connectivity between your Virtual Library System and Insight RS.

Install and configure communication software on

Virtual Library Systems
To configure your monitored devices, complete the following section:

Configure SNMP on the Virtual Library System

To support your Virtual Library System (VLS) Tape Libraries, you need to configure SNMP in Command View
for Virtual Library Systems (VLS).
To configure SNMP on your VLS Tape Libraries, complete the following steps:
1. Log on to the Command View VLS web interface of each VLS node.
2. Click the Notifications tab.
3. Click the Edit SNMP settings task. Note that this task may be called SNMP Setup, depending on your
version of Command View VLS.

4. In the Hostname field, type the Hosting Device IP address or FQDN.

5. In the Community String field, if you select a non-standard trap community name (for example,
something other than public), verify the Insight RS Console recognizes this name.

HPE Insight Remote Support 7.10: Monitored Devices Configuration Guide Page 348 of 436
Chapter 31: Configuring Virtual Library Systems

6. The trap version is 1.

7. Click Add.

Add protocol credentials and start discovery

To discover your monitored devices, complete the following sections:

Create an SNMPv1 protocol credential in the Insight RS

Console
If your device's SNMP community string is set to public and your community access mode is read only,
Insight RS automatically associates an SNMPv1 protocol with your device. If you use a different community
string or use a nonstandard port, you must create an SNMPv1 protocol credential in the Insight RS Console.
To configure SNMPv1 in the Insight RS Console, complete the following steps:
1. In a web browser, log on to the Insight RS Console.
2. In the main menu, select Discovery and click the Credentials tab.
3. From the Select and Configure Protocol drop-down list, select Simple Network Management Protocol
Version 1, V2C (SNMPv1, SNMPv2C).
4. Click New. The New Credential dialog box appears.
5. Type the Community String you have configured on your device.
6. Click Add.
Insight RS creates the protocol credential and it appears in the credentials table.

Discover the device in the Insight RS Console

To discover the device from the Insight RS Console, complete the following steps:
1. In a web browser, log on to the Insight RS Console.
2. In the main menu, select Discovery and click the Sources tab.
3. Expand the IP Addresses section and add the IP address for your device:
a. Click New.
b. Select the Single Address, Address Range, or Address List option.
c. Type the IP address(es) of the devices to be discovered.
d. Click Add.
4. Click Start Discovery.

Verify discovery and device status

To verify the device was discovered correctly, complete the following steps:
1. In a web browser, log on to the Insight RS Console.
2. In the main menu, select Devices and click the Device Summary tab.

HPE Insight Remote Support 7.10: Monitored Devices Configuration Guide Page 349 of 436
Chapter 31: Configuring Virtual Library Systems

3. Make sure the Status column contains a success icon ( ).

If there is no success icon, determine which column has the problem and consult the Online Help for
troubleshooting information.

Verify communication between monitored device

and Insight RS
To verify communication between your monitored device and Insight RS, complete the following sections:

Send a test event to verify the configuration

Note: Do not pull a redundant FRU to test the configuration.

If you have the latest VLS firmware and the latest version of Command View VLS, click the Test SNMP
button on the Command View VLS SNMP configuration page to perform an end-to-end test. This test event
will not result in a case being created at HPE, but it will create a local email notification to confirm that the VLS
SNMP and Insight Remote Support is configured correctly.

Verify collections in the Insight RS Console

Configuration collections are not supported for this device type except when it is part of a SAN collection. If
you have added this device to a SAN collection, you can manually run a SAN collection to verify the
configuration.
1. Log on to the Insight RS Console.
2. In the main menu, select Collection Services.
3. Click the Collection Schedules tab.
4. In the List of Collection Schedules pane, select the SAN Configuration Collection Schedule.
Information about the collection appears in the Collection Information pane. The On These Devices pane
lists the devices the collection will run on.
5. In the Schedule Information pane, click Run Now.
6. When the collection completes, click the SAN Storage Collection Results tab.
7. Expand the SAN Configuration Collection section.
8. Locate the entry for your device and check the Result column. If the collection was successful, a
success icon appears ( ). If it failed, an error icon appears ( ).

HPE Insight Remote Support 7.10: Monitored Devices Configuration Guide Page 350 of 436
 Chapter 32: Configuring StoreEver Tape
Libraries
HPE’s physical tape libraries require a combination of their own web-based management interfaces and
aggregated HPE Command View for Tape Libraries (TL) library management software to work with Insight
Remote Support (RS). Users configure each library to send SNMP traps for hardware events, such as fan
failures, directly to the Insight RS server. Users configure Command View TL to send TapeAssure events
over SMI-S such as poor drive margin. You need to discover Command View TL and the libraries separately.

Note: Insight RS does not support standalone (non-library) tape drives.

Fulfill configuration requirements

To configure Command View TL TapeAssure and your Tape Libraries to be monitored by Insight RS,
complete the following sections:

Note: In future releases these configuration steps will be simplified.

Table 32.1 Tape Library configuration steps

Task Complete?

Make sure Insight RS supports your tape library by checking the HPE Insight Remote Support
Release Notes.

Configure Command View TL TapeAssure. Note that Command View TL supplies the WBEM
protocol for configuration collection support.

Configure SNMPv1 traps on each tape library with the Hosting Device as the trap destination.

Add the SNMP protocol to the Insight RS Console.

Add the WBEM protocol to the Insight RS Console (for ESL and EML).

Discover the tape library in the Insight RS Console.

Verify the warranty and contract information in the Insight RS Console.

Install and configure communication software on

Tape Libraries
To configure your monitored devices, complete the following sections:

Configure Command View TL TapeAssure

In addition to managing the tape libraries, Command View for Tape Libraries supplies the WBEM protocol that
is necessary for Insight RS to gather collections on your tape libraries. During discovery of either the tape
libraries or the Command View TL server, a WBEM protocol must be created in the Insight RS Console for the
Command View TL instance on the server, and the managing server must be actively managing the tape
libraries for collections to be gathered.

HPE Insight Remote Support 7.10: Monitored Devices Configuration Guide Page 351 of 436
Chapter 32: Configuring StoreEver Tape Libraries

Note: HPE recommends you use the latest version of Command View TL. Download the update at:
www.hpe.com/support/cvtl.

Important: Select Custom Installation to make sure the Command View TL SMI-S provider is
installed.

Use the following procedure to configure Command View TL to allow Insight RS to register for TapeAssure
events for Command View TL.

Configuring Command View TL 3.1 and above

The Command View TL 3.1 CIMOM has user authentication enabled. With authentication enabled, the
administrator of the Open Pegasus CIMOM has to create SMI-S users and provide access privileges for each
user. Any current, or newly created Windows user can become a cimuser.
To add users and namespaces for Command View TL 3.1 CIMOM authentication complete the following
steps:
1. Open a Command Prompt window and change directory to: C:\Program Files (x86)\Hewlett-
Packard\Command View TL\op-cimom\bin.
2. To create a cimuser, use the command:
cimuser –a –u <Windows username>
The command asks for password and a confirmation. Provide the password of your choice.
3. Provide Read/Write access to the namespaces. In the TapeAssure Provider, all classes are
implemented in two namespaces: root/PG_Interop and root/hptl. Both name spaces should be given
read/write access. To provide access to the above name spaces to a selected user, use the command:
cimauth –a -u <cimuser> -n <namespace> -R -W
Verifying Command View TL is monitoring your Tape Libraries
To configure Command View TL TapeAssure to monitor each library, complete the following steps:
1. In Command View TL, add the Tape Libraries to be monitored into the Command View TL Launcher
window. Library Selection → Actions → Add Library.
2. Select the TapeAssure tab and check that the monitored libraries appear in the TapeAssure Overview

HPE Insight Remote Support 7.10: Monitored Devices Configuration Guide Page 352 of 436
Chapter 32: Configuring StoreEver Tape Libraries

window.

Important: TapeAssure can also monitor standalone tape drives (those not in a tape library) and a
host name appears instead of a library name; however, standalone drives cannot be configured for
Insight RS.

Configure SNMP on your Tape Libraries

You must add the Hosting Device as a trap destination on your tape libraries for service events to reach
Insight RS.

Configure Enterprise Systems Library E-series and Enterprise Modular

Library
To allow Insight RS to register for your Enterprise Systems Library (ESL) E-series or Enterprise Modular
Library (EML) library health events using SNMP, Command View TL must be configured.
To configure SNMP in Command View TL, complete the following steps:
1. Log on to the Command View TL web interface for each ESL-E or EML.
2. Click the Configuration tab.

HPE Insight Remote Support 7.10: Monitored Devices Configuration Guide Page 353 of 436
Chapter 32: Configuring StoreEver Tape Libraries

3. In the left panel, select SNMP Alerts. The current SNMP traps appear in the right panel.

4. Do one of the following:

l In the right panel, right-click an SNMP trap, and then select Add Trap Entry.
or
l Select Actions → Add Trap Entry.
The SNMP Trap Entry screen appears.

5. In the Trap Destination field, type the Hosting Device IP address or Fully Qualified Domain Name
(FQDN).
6. Type public as the Community String unless you have defined another community string.
7. Click OK.

Configure Enterprise Systems Library G3 series

To allow Insight RS to register for your Enterprise Systems Library (ESL) G3 library health events using
SNMP, complete the following steps:
1. Log on to the ESL G3 user interface as admin.
2. In the console, go to Setup → Network Configuration → Network Security Settings.

HPE Insight Remote Support 7.10: Monitored Devices Configuration Guide Page 354 of 436
Chapter 32: Configuring StoreEver Tape Libraries

3. In the Security Configuration screen, select the SNMP/SMI-S tab.

Note: Library health events are monitored with SNMP only. You do not need to enable SMI-S
unless it is required for other Network Management software.

4. Click OK.
5. In the console, go to Setup → Notifications → SNMP Trap Registration.
6. In the SNMP Trap Registration screen, create an SNMPv1 trap, port 162 entry for the IP address of the
Hosting Device. Use public for the community name. Click Create.

HPE Insight Remote Support 7.10: Monitored Devices Configuration Guide Page 355 of 436
Chapter 32: Configuring StoreEver Tape Libraries

Configure Modular Systems Library G3 series

To allow Insight RS to register for your Modular Systems Library (MSL) G3 library health events using SNMP,
complete the following steps:
1. Log on to the Command View MSL web interface as Administrator.
2. Click the Configuration tab.
3. Click the Network Management tab.

HPE Insight Remote Support 7.10: Monitored Devices Configuration Guide Page 356 of 436
Chapter 32: Configuring StoreEver Tape Libraries

4. Verify the SNMP Enabled check box is selected.

5. In the IPv4 Target address field type the Hosting Device IP address or FQDN.
6. Verify SNMPv1 is the version selected.
7. In the SNMP Trap Notification Filter, select Critical and Warning Events as the filter level.
8. Click Submit.

Configure Modular Systems Library MSL6480

To allow Insight RS to register for your Modular Systems Library (MSL) MSL6480 library health events using
SNMP, complete the following steps:
1. Log on to the Log on to the MSL6480 web interface as Administrator.
2. Click Configuration.
3. Click the Network Management → SNMP tab.

HPE Insight Remote Support 7.10: Monitored Devices Configuration Guide Page 357 of 436
Chapter 32: Configuring StoreEver Tape Libraries

4. Verify the SNMP Enabled check box is selected.

5. In the SNMP Targets table, click Edit next to a target without an IP/Hostname.
6. In the IP/Hostname field type the Hosting Device IP address or FQDN.
7. Verify SNMPv1 is the version selected and enter the community string of the Hosting Device.
8. Click Submit.
9. Click OK in the confirmation dialogue box.

Configure firewall and port settings

Table 32.2 StoreEver Tape Libraries Connectivity - Firewall/Port Requirements
Protocol Ports Source Destination Function Optional

ICMP N/A Hosting Monitored Provides system reachability (ping) check during Required
Device Systems system discovery and before other operations.

TCP 2301 Customer's Hosting SMH port for Insight Manager Web Agents; HTTP Optional
Web Device redirected to 2381 (HTTPS). (Recommend using
Browser TCP/2381.)

TCP 2381 Hosting Monitored SMH port for Insight Manager Web Agents; Recommended
Device Systems HTTPS redirected to 2381 (HTTPS).

TCP 5989 Hosting Monitored Secured WBEM CIMOM protocol over Required
Device Systems HTTPS/SOAP. This port is used for basic
collections on HPE StoreEver ESL and EML
devices.

UDP 161 Hosting Monitored SNMP. This is the standard port used by SNMP Required
Device Systems agents on monitored systems. The Hosting
Device sends requests to devices on this port.

UDP 162 Monitored Hosting SNMP Trap. This is the port used by Insight RS to Required
Systems Device listen to SNMP traps.

HPE Insight Remote Support 7.10: Monitored Devices Configuration Guide Page 358 of 436
Chapter 32: Configuring StoreEver Tape Libraries

Add protocol credentials and start discovery

To discover your monitored devices, complete the following sections:

Create an SNMPv1 protocol credential in the Insight RS

Console
If your device's SNMP community string is set to public and your community access mode is read only,
Insight RS automatically associates an SNMPv1 protocol with your device. If you use a different community
string or use a nonstandard port, you must create an SNMPv1 protocol credential in the Insight RS Console.
To configure SNMPv1 in the Insight RS Console, complete the following steps:
1. In a web browser, log on to the Insight RS Console.
2. In the main menu, select Discovery and click the Credentials tab.
3. From the Select and Configure Protocol drop-down list, select Simple Network Management Protocol
Version 1, V2C (SNMPv1, SNMPv2C).
4. Click New. The New Credential dialog box appears.
5. Type the Community String you have configured on your device.
6. Click Add.
Insight RS creates the protocol credential and it appears in the credentials table.

Create a WBEM protocol credential in Insight RS Console

For ESL and EML tape libraries, you must create a WBEM protocol in the Insight RS Console for the
Command View TL server that monitors your tape libraries.
To configure WBEM in the Insight RS Console, complete the following steps:
1. In a web browser, log on to the Insight RS Console.
2. In the main menu, select Discovery and click the Credentials tab.
3. From the Select and Configure Protocol drop-down list, select Web-Based Enterprise Management
(WBEM).
4. Click New. The New Credential dialog box appears.
5. Type the Username and Password you have configured on your device.
6. Click Add.
Insight RS creates the protocol credential and it appears in the credentials table.

Discover the Tape Libraries in Insight RS

Insight RS does not raise incidents for tape libraries or TapeAssure unless they are recognized by Insight RS.
To make sure Insight RS raises incidents, complete the following steps:
1. In a web browser, log on to the Insight RS Console.
2. In the main menu, select Discovery and click the Sources tab.

HPE Insight Remote Support 7.10: Monitored Devices Configuration Guide Page 359 of 436
Chapter 32: Configuring StoreEver Tape Libraries

3. Type the IP addresses to be discovered:

a. Type the IP address of the Command View TL host server. Discover the Command View TL host
server individually by its IP address, making sure that when you create the Command View TL host
discovery task, the CIMOM user credentials created in section "Configure Command View TL
TapeAssure" on page 351 are used.
b. Type the IP addresses of the tape libraries. Either discover each library individually or discover them
within a range of IP addresses.
4. Click Start Discovery.

Verify warranty and contract information

After device discovery, verify the warranty and contract information.
1. In a web browser, log on to the Insight RS Console.
2. In the main menu, select Devices and click the Device Summary tab.
3. Check that all of the monitored tape libraries and the Command View TL host(s) appear in the devices
table.
4. Click the device name and expand the Hardware pane. Verify the correct product number and serial
number for the tape library was discovered. Edit the individual devices if any appear to be missing any
warranty and contract information.

Important: After discovery, the CVTL@<device> that Insight RS lists will always display an error
icon ( ) in the Warranty & Contract and status column.

Verify discovery and device status

To verify the device was discovered correctly, complete the following steps:
1. In a web browser, log on to the Insight RS Console.
2. In the main menu, select Devices and click the Device Summary tab.

3. Make sure the Status column contains a success icon ( ).

If there is no success icon, determine which column has the problem and consult the Online Help for
troubleshooting information.

Verify communication between monitored device

and Insight RS
To verify communication between your monitored device and Insight RS, complete the following section:

Verify collections in the Insight RS Console

Collections are not automatically run after discovery. HPE recommends that you manually run a collection
after discovery completes in order to verify connectivity. Run the collection schedule manually on the
Collection Services → Collection Schedules tab. For more information about scheduling collections, see the

HPE Insight Remote Support 7.10: Monitored Devices Configuration Guide Page 360 of 436
Chapter 32: Configuring StoreEver Tape Libraries

Insight RS Help.
Verify that this collection ran successfully on the Collection Services → SAN Storage Collection Results tab
in the Insight RS Console.
1. Log on to the Insight RS Console.
2. In the main menu, select Collection Services and then click the SAN Storage Collection Results tab.
3. Expand the Storage Configuration Collection section.
4. Locate the entry for your device and check the Result column. If the collection was successful, a
success icon appears ( ). If it failed, an error icon appears ( ).

HPE Insight Remote Support 7.10: Monitored Devices Configuration Guide Page 361 of 436
 Chapter 33: Configuring StoreFabric B-Series
switches
Fulfill configuration requirements
To configure your StoreFabric B-Series switches to be monitored by Insight RS, complete the following
sections:

Note: Test trap support for B-series SAN switches requires the installation of Fabric Operating
System v6.3.0b firmware or higher. For more details, refer to the HPE Fabric OS 6.3.0b Customer
Advisory at: http://h20565.www2.hpe.com/hpsc/doc/public/display?docId=emr_na-c01924282.

Note: Telnet or SSH is required for configuration collection support. Telnet and SSH are enabled by
default on StoreFabric B-Series switches.

Table 33.1 StoreFabric B-Series switch configuration steps

Task Complete?

Make sure Insight RS supports your B-Series switch by checking the HPE Insight Remote
Support Release Notes.

Configure SNMP on the B-Series switch.

Add the SNMP protocol to the Insight RS Console.

Discover the B-Series switch in the Insight RS Console.

Verify the status of the B-Series switch in the Insight RS Console.

Send a test event to verify connectivity between your B-Series switch and Insight RS.

Install and configure communication software on

SAN switches
To configure your monitored devices, complete the following sections:

Configure SNMP
You can use SNMPv1 or SNMPv3 to monitor your B-Series switches. Follow the steps in one of the options
below to configure SNMP on your switch.

Option 1: Configure SNMPv1

Use the following procedure to configure SNMP on a B-Series switch so that it can be monitored with Insight
Remote Support.
1. Display the current or default SNMPv1 settings:
> snmpconfig --show snmpv1

HPE Insight Remote Support 7.10: Monitored Devices Configuration Guide Page 362 of 436
Chapter 33: Configuring StoreFabric B-Series switches

SNMPv1 community and trap recipient configuration:

Community 1: public (rw) No trap recipient configured yet
Community 2: public (rw) No trap recipient configured yet
Community 3: public (rw) No trap recipient configured yet
Community 4: public (ro) No trap recipient configured yet
Community 5: common (ro) No trap recipient configured yet
Community 6: FibreChannel (ro) No trap recipient configured yet

2. Set SNMPv1 community string and Trap recipient:

> snmpconfig --set snmpv1
SNMP community and trap recipient configuration:
Community (rw): [public] gcc-public ! Create new community
Trap Recipient's IP address : [0.0.0.0] 1.2.3.4
Trap recipient Severity level : (0..5) [0] 2
Trap recipient Port : (0..65535) [162] Community (rw): [public]
Trap Recipient's IP address : [0.0.0.0] Community (rw): [public]
Trap Recipient's IP address : [0.0.0.0] Community (ro): [public]
Trap Recipient's IP address : [0.0.0.0] Community (ro): [common]
Trap Recipient's IP address : [0.0.0.0] Community (ro): [FibreChannel]
Trap Recipient's IP address : [0.0.0.0] Committing configuration...done.

Note: The trap severity level is associated with each trap recipient IP address. The event trap
level is in conjunction with the event's severity level. When an event occurs and if its severity
level is at or below the set value, the SNMP event traps (swEventTrap, swFabricWatchTrap,
and connUnitEventTrap) are sent to the trap recipients.

By default, this value is set to 0, implying that no such traps are sent. The possible values are the
following:
l 0 none
l 1 critical
l 2 error
l 3 warning
l 4 informational
l 5 debug
3. Display the new settings:
> snmpconfig --show snmpv1
SNMPv1 community and trap recipient configuration:
Community 1: gcc-public (rw) Trap recipient: 1.2.3.4 Trap port: 162 Trap recipient
Severity level: 2
Community 2: public (rw) No trap recipient configured yet
Community 3: public (rw) No trap recipient configured yet
Community 4: public (ro) No trap recipient configured yet
Community 5: common (ro) No trap recipient configured yet

HPE Insight Remote Support 7.10: Monitored Devices Configuration Guide Page 363 of 436
Chapter 33: Configuring StoreFabric B-Series switches

Community 6: FibreChannel (ro) No trap recipient configured yet

4. Set SNMP access control:

> snmpconfig --set accesscontrol
SNMP access list configuration:
Access host subnet area : [11.0.0.2] 1.2.3.4 ! set to the IP add of SIM Read/Write?
(true, t, false, f): [true]
Access host subnet area : [1.2.3.4] Read/Write? (true, t, false, f): [true] f
Access host subnet area : [1.2.3.4] Read/Write? (true, t, false, f): [true] f
Access host subnet area : [1.2.3.4] 0.0.0.0 ! remove this one Read/Write? (true, t,
false, f): [true] f
Access host subnet area : [1.2.3.4] Read/Write? (true, t, false, f): [true]
Access host subnet area : [1.2.3.4] Read/Write? (true, t, false, f): [true]
Committing configuration...done.

5. Remove the remaining IP address from the SNMP Access Control List if required:
> snmpconfig --set accesscontrol
SNMP access list configuration:
Access host subnet area : [1.2.3.4] Read/Write? (true, t, false, f): [true]
Access host subnet area : [1.2.3.4] 0.0.0.0 Read/Write? (true, t, false, f): [false]
f
Access host subnet area : [1.2.3.4] 0.0.0.0 Read/Write? (true, t, false, f): [false]
f
Access host subnet area : [0.0.0.0] Read/Write? (true, t, false, f): [false]
Access host subnet area : [1.2.3.4] 0.0.0.0 Read/Write? (true, t, false, f): [true] f
Access host subnet area : [1.2.3.4] 0.0.0.0 Read/Write? (true, t, false, f): [true] f
Committing configuration...done.

6. Check the access to SNMP control list:

> snmpconfig --show accesscontrol
SNMP access list configuration:
Entry 0: Access host subnet area 1.2.3.4 (rw)
Entry 1: No access host configured yet
Entry 2: No access host configured yet
Entry 3: No access host configured yet
Entry 4: No access host configured yet
Entry 5: No access host configured yet

7. Set MIB Capability:

> snmpconfig --set mibcapability
The SNMP Mib/Trap Capability has been set to support FE-MIB SW-MIB FA-MIB HA-MIB SW-
TRAP FA-TRAP HA-TRAP
FA-MIB (yes, y, no, n): [yes]
FICON-MIB (yes, y, no, n): [no]
HA-MIB (yes, y, no, n): [yes] yes
FCIP-MIB (yes, y, no, n): [no]

HPE Insight Remote Support 7.10: Monitored Devices Configuration Guide Page 364 of 436
Chapter 33: Configuring StoreFabric B-Series switches

ISCSI-MIB (yes, y, no, n): [no]

SW-TRAP (yes, y, no, n): [yes]
swFCPortScn (yes, y, no, n): [no] yes
swEventTrap (yes, y, no, n): [no] yes
swFabricWatchTrap (yes, y, no, n): [no] yes
swTrackChangesTrap (yes, y, no, n): [no] yes
FA-TRAP (yes, y, no, n): [yes]
connUnitStatusChange (yes, y, no, n): [no] yes
connUnitEventTrap (yes, y, no, n): [no] yes
connUnitSensorStatusChange (yes, y, no, n): [no] yes
connUnitPortStatusChange (yes, y, no, n): [no] yes
SW-EXTTRAP (yes, y, no, n): [no] yes

8. Display the IP address of the switch, so it can be added to the Insight RS Console:
> ipaddrshow
SWITCH Ethernet IP Address: 1.2.3.4
Ethernet Subnetmask: 1.2.3.4
Fibre Channel IP Address: none
Fibre Channel Subnetmask: none
Gateway IP Address: 1.2.3.4
DHCP: Off

9. Modify the switch systemgroup variables if required:

> snmpconfig --set systemGroup
Customizing MIB-II system variables ... At each prompt, do one of the following:
o to accept current value,
o enter the appropriate new value,
o to skip the rest of configuration, or
o to cancel any change.
To correct any input mistake: erases the previous character, erases the whole line,
sysDescr: [Fibre Channel Switch.] Brocade 4/16 FC Switch
sysLocation: [End User Premise.] HPE Building 11th floor
sysContact: [Field Support.] John Doe
authTrapsEnabled (true, t, false, f): [true]
Committing configuration...done.

Option 2: Configure SNMPv3

Before configuring SNMPv3, you will need the SNMP username and appropriate credentials to be used (Auth,
Priv, and passwords for each).

Important: HPE Insight RS supports the secure SNMPv3 protocol on B-Series switches that
support SNMPv3. Insight RS only supports SNMPv3 traps, and does not support SNMPv3
Informs. Insight RS listens on port 1162 for SNMPv3 traps, and your SNMPv3 passwords must be
at least 8 characters long. Refer to your device's documentation to determine the versions of SNMP
your device supports.

HPE Insight Remote Support 7.10: Monitored Devices Configuration Guide Page 365 of 436
Chapter 33: Configuring StoreFabric B-Series switches

To configure SNMPv3, complete the following steps. Example responses are shown in red.
1. Using PuTTY or suitable SSH access tool, SSH to the switch and login as an Administrator user.
2. Disable SNMPv1 using the following command:
#snmpconfig –disable snmpv1
3. Configure MIB capability on the switch to enabled the HA MIB and HA TRAPS:
#snmpconfig –set mibcapability
FE-MIB (yes, y, no, n): [yes] <return>
SW-MIB (yes, y, no, n): [yes] <return>
FA-MIB (yes, y, no, n): [yes] <return>
FICON-MIB (yes, y, no, n): [no] <return>
HA-MIB (yes, y, no, n): [no] Yes; if already Yes then <return>
FCIP-MIB (yes, y, no, n): [no] <return>
IF-MIB (yes, y, no, n): [yes] <return>
BD-MIB (yes, y, no, n): [yes] <return>
BROCADE-MAPS-MIB (yes, y, no, n): [yes] <return>
T11-FC-ZONE-SERVER-MIB (yes, y, no, n): [no] <return>
SW-TRAP (yes, y, no, n): [yes] <return>
swFCPortScn (yes, y, no, n): [yes] <return>
swEventTrap (yes, y, no, n): [yes] <return>
DesiredSeverity: (0..4) [0] <return>
swIPv6ChangeTrap (yes, y, no, n): [yes] <return>
swPmgrEventTrap (yes, y, no, n): [yes] <return>
swFabricReconfigTrap (yes, y, no, n): [no] <return>
swFabricSegmentTrap (yes, y, no, n): [no] <return>
swExtTrap (yes, y, no, n): [yes] <return>
swStateChangeTrap (yes, y, no, n): [no] <return>
swPortMoveTrap (yes, y, no, n): [no] <return>
swBrcdGenericTrap (yes, y, no, n): [no] <return>
swDeviceStatusTrap (yes, y, no, n): [no] <return>
swZoneConfigChangeTrap (yes, y, no, n): [no] <return>
FA-TRAP (yes, y, no, n): [yes] <return>
connUnitStatusChange (yes, y, no, n): [yes] <return>
connUnitEventTrap (yes, y, no, n): [yes] <return>
connUnitPortStatusChange (yes, y, no, n): [yes] <return>
HA-TRAP (yes, y, no, n): [no] yes
fruStatusChanged (yes, y, no, n): [no] yes
cpStatusChanged (yes, y, no, n): [no] yes
fruHistoryTrap (yes, y, no, n): [no] yes
IF-TRAP (yes, y, no, n): [yes] <return>
linkDown (yes, y, no, n): [yes] <return>
linkUp (yes, y, no, n): [yes] <return>
BD-TRAP (yes, y, no, n): [yes] <return>
bdTrap (yes, y, no, n): [yes] <return>
bdClearTrap (yes, y, no, n): [yes] <return>

HPE Insight Remote Support 7.10: Monitored Devices Configuration Guide Page 366 of 436
Chapter 33: Configuring StoreFabric B-Series switches

MAPS-TRAP (yes, y, no, n): [yes] <return>

mapsTrapAM (yes, y, no, n): [yes] <return>

4. Verify that the configuration changes have been accepted:

#snmpconfig –show mibcapability
FE-MIB: YES
SW-MIB: YES
FA-MIB: YES
FICON-MIB: NO
HA-MIB: YES
FCIP-MIB: NO
IF-MIB: YES
BD-MIB: YES
BROCADE-MAPS-MIB: YES
T11-FC-ZONE-SERVER-MIB: NO
SW-TRAP: YES
swFCPortScn: YES
swEventTrap: YES
DesiredSeverity:None
swIPv6ChangeTrap: YES
swPmgrEventTrap: YES
swFabricReconfigTrap: NO
swFabricSegmentTrap: NO
swExtTrap: YES
swStateChangeTrap: NO
swPortMoveTrap: NO
swBrcdGenericTrap: NO
swDeviceStatusTrap: NO
swZoneConfigChangeTrap: NO
FA-TRAP: YES
connUnitStatusChange: YES
connUnitEventTrap: YES
connUnitPortStatusChange: YES
FICON-TRAP: NO
linkRNIDDeviceRegistration: NO
linkRNIDDeviceDeRegistration: NO
linkLIRRListenerAdded: NO
linkLIRRListenerRemoved: NO
linkRLIRFailureIncident: NO
HA-TRAP: YES
fruStatusChanged: YES
cpStatusChanged: YES
fruHistoryTrap: YES
IF-TRAP: YES
linkDown: YES
linkUp: YES

HPE Insight Remote Support 7.10: Monitored Devices Configuration Guide Page 367 of 436
Chapter 33: Configuring StoreFabric B-Series switches

BD-TRAP: YES
bdTrap: YES
bdClearTrap: YES
MAPS-TRAP: YES
mapsTrapAM: YES
T11-FC-ZONE-SERVER-TRAP: NO
t11ZsRequestRejectNotify: NO
t11ZsMergeFailureNotify: NO
t11ZsMergeSuccessNotify: NO
t11ZsDefZoneChangeNotify: NO
t11ZsActivateNotify: NO

5. Begin to configure SNMPv3. Identify a configured SNMP user to use:

#snmpconfig -- show snmpv3
SNMP Informs = 0 (OFF)

SNMPv3 USM configuration:

User 1 (rw): snmpadmin1
Auth Protocol: noAuth
Priv Protocol: noPriv
User 2 (rw): snmpadmin2
Auth Protocol: noAuth
Priv Protocol: noPriv
User 3 (rw): snmpadmin3
Auth Protocol: noAuth
Priv Protocol: noPriv
User 4 (ro): snmpuser1
Auth Protocol: noAuth
Priv Protocol: noPriv
User 5 (ro): snmpuser2
Auth Protocol: noAuth
Priv Protocol: noPriv
User 6 (ro): snmpuser3
Auth Protocol: noAuth
Priv Protocol: noPriv

SNMPv3 Trap/Informs configuration:

Trap Entry 1: No trap recipient configured yet
Notify Type: TRAP(1)
Trap Entry 2: No trap recipient configured yet
Notify Type: TRAP(1)
Trap Entry 3: No trap recipient configured yet
Notify Type: TRAP(1)
Trap Entry 4: No trap recipient configured yet
Notify Type: TRAP(1)
Trap Entry 5: No trap recipient configured yet
Notify Type: TRAP(1)

HPE Insight Remote Support 7.10: Monitored Devices Configuration Guide Page 368 of 436
Chapter 33: Configuring StoreFabric B-Series switches

Trap Entry 6: No trap recipient configured yet

Notify Type: TRAP(1)

Choose a user not already defined in the SNMPv3 Trap/Inform configuration. In the example above, no
SNMPv3 Trap/Inform configuration has been defined so all the listed users are available for use. In this
example, we will use snmpadmin1.
6. Once you have selected the SNMP user and have the appropriate credentials you want to use for the
Auth/Priv configuration you can begin to configure SNMPv3.
SNMP Informs Enabled (true, t, false, f): [false] <return>; needs to be “false”

SNMPv3 user configuration (snmp user not configured in FOS user database will have
physical AD and admin role as the default):
User (rw): [snmpadmin1] <return>
Auth Protocol [MD5(1)/SHA(2)/noAuth(3)]: (1..3) 1; example selects MD5
New Auth Passwd: <enter password, must be at least 8 chracters>
Priv Protocol [DES(1)/noPriv(2)/AES128(3)/AES256(4)]): (1..4) 1; example selects DES
New Priv Passwd: <enter password, must be at least 8 chracters>
User (rw): [snmpadmin2] <return>
Auth Protocol [MD5(1)/SHA(2)/noAuth(3)]: (1..3) [3] <return>
Priv Protocol [DES(1)/noPriv(2)/AES128(3)/AES256(4)]): (2..2) [2] <return>
User (rw): [snmpadmin3] <return>
Auth Protocol [MD5(1)/SHA(2)/noAuth(3)]: (1..3) [3] <return>
Priv Protocol [DES(1)/noPriv(2)/AES128(3)/AES256(4)]): (2..2) [2] <return>
User (ro): [snmpuser1] <return>
Auth Protocol [MD5(1)/SHA(2)/noAuth(3)]: (1..3) [3] <return>
Priv Protocol [DES(1)/noPriv(2)/AES128(3)/AES256(4)]): (2..2) [2] <return>
User (ro): [snmpuser2] <return>
Auth Protocol [MD5(1)/SHA(2)/noAuth(3)]: (1..3) [3] <return>
Priv Protocol [DES(1)/noPriv(2)/AES128(3)/AES256(4)]): (2..2) [2] <return>
User (ro): [snmpuser3] <return>
Auth Protocol [MD5(1)/SHA(2)/noAuth(3)]: (1..3) [3] <return>
Priv Protocol [DES(1)/noPriv(2)/AES128(3)/AES256(4)]): (2..2) [2] <return>

SNMPv3 trap/inform recipient configuration:

Trap Recipient's IP address : [0.0.0.0] <Add RS Host IP Here>
Notify Type [TRAP(1)/INFORM(2)]: (1..1) [1] <return>; leave 1 for Traps
UserIndex: (1..6) [1]; snmpadmin1 is the first in the list above, so 1 represents
that user
Trap recipient Severity level : (0..5) [2] 4
Trap recipient Port : (0..65535) [162] 1162; must be 1162 for Insight RS listener
Trap Recipient's IP address : [0.0.0.0] <return>
Trap Recipient's IP address : [0.0.0.0] <return>
Trap Recipient's IP address : [0.0.0.0] <return>
Trap Recipient's IP address : [0.0.0.0] <return>
Trap Recipient's IP address : [0.0.0.0] <return>

The configuration of the Brocade is now complete.

HPE Insight Remote Support 7.10: Monitored Devices Configuration Guide Page 369 of 436
Chapter 33: Configuring StoreFabric B-Series switches

Configure firewall and port settings

Table 33.2 SAN Switch Connectivity - Firewall/Port Requirements
Protocol Ports Source Destination Function Optional

ICMP N/A Hosting Monitored Provides system reachability (ping) check during Required
Device Systems system discovery and before other operations.

UDP 161 Hosting Monitored SNMP. This is the standard port used by SNMP agents Required
Device Systems on monitored systems. The Hosting Device sends
requests to devices on this port.

UDP 162 Monitored Hosting SNMP Trap. This is the port used by Insight RS to listen Required*
Systems Device to SNMP traps.

UDP 1162 Monitored Hosting SNMPv3 Trap. This is the port used by Insight RS to Required*
Device Device listen to SNMPv3 traps.

TCP 22 Hosting Monitored SSH: Remote Data Collection Optional

Device Systems

TCP 23 Hosting Monitored Telnet: Remote Data Collection Optional

Device Systems

* Dependent on the version of SNMP used on the monitored device.

Add protocol credentials and start discovery

To discover your monitored devices, complete the following sections:

Create an SNMP protocol credential in the Insight RS

Console
Create an SNMPv1 or SNMPv3 protocol credential to correspond to the protocol you configured on your
switch in "Option 1: Configure SNMPv1" on page 362 or "Option 2: Configure SNMPv3" on page 365.

Option 1: SNMPv1
If your device's SNMP community string is set to public and your community access mode is read only,
Insight RS automatically associates an SNMPv1 protocol with your device. If you use a different community
string or use a nonstandard port, you must create an SNMPv1 protocol credential in the Insight RS Console.
To configure SNMPv1 in the Insight RS Console, complete the following steps:
1. In a web browser, log on to the Insight RS Console.
2. In the main menu, select Discovery and click the Credentials tab.
3. From the Select and Configure Protocol drop-down list, select Simple Network Management Protocol
Version 1, V2C (SNMPv1, SNMPv2C).
4. Click New. The New Credential dialog box appears.
5. Type the Community String you have configured on your device.
6. Click Add.

HPE Insight Remote Support 7.10: Monitored Devices Configuration Guide Page 370 of 436
Chapter 33: Configuring StoreFabric B-Series switches

Insight RS creates the protocol credential and it appears in the credentials table.

Option 2: SNMPv3
To configure SNMPv3 in the Insight RS Console, complete the following steps:
1. Create a Named Credential for every set of Management Group credentials:
a. In the Insight RS Console, navigate to Company Information → Named Credentials.
b. Click Add New Credential.
c. Type a Credential Name, for example: Brocade SNMPv3.
d. In the Protocol drop-down list, select Simple Network Management Protocol Version 3
(SNMPv3).
e. Use the default port of 161.
f. In the SNMP Account Credential fields, add:
i. Type the Username for the user identified in "Option 2: Configure SNMPv3" on page 365.
ii. Account Authentication Protocol: MD5 or SHA
The example used MD5 in "Option 2: Configure SNMPv3" on page 365.
iii. Account Authentication Password.
iv. Account Privacy Protocol: DES, DES3, AES128, AES192, AES256
The example used DES in "Option 2: Configure SNMPv3" on page 365.
v. Account Privacy Passphrase.
vi. Leave the Context Name blank.
g. Click Save.
2. Add Discovery credentials for the B-Series switches:
a. In the Insight RS Console, navigate to Discovery → Credentials.
b. Create discovery protocol credentials for the Named Credential created earlier.
i. In the Select and Configure Protocol drop-down list, select Simple Network Management
Protocol Version 3 (SNMPv3).
ii. Click New.
iii. In the Named Credential drop-down list, select the Named Credential created earlier.
iv. Click Add.

Discover the device in the Insight RS Console

To discover the device from the Insight RS Console, complete the following steps:
1. In a web browser, log on to the Insight RS Console.
2. In the main menu, select Discovery and click the Sources tab.
3. Expand the IP Addresses section and add the IP address for your device:

HPE Insight Remote Support 7.10: Monitored Devices Configuration Guide Page 371 of 436
Chapter 33: Configuring StoreFabric B-Series switches

a. Click New.
b. Select the Single Address, Address Range, or Address List option.
c. Type the IP address(es) of the devices to be discovered.
d. Click Add.
4. Click Start Discovery.

Verify discovery and device status

To verify the device was discovered correctly, complete the following steps:
1. In a web browser, log on to the Insight RS Console.
2. In the main menu, select Devices and click the Device Summary tab.

3. Make sure the Status column contains a success icon ( ).

If there is no success icon, determine which column has the problem and consult the Online Help for
troubleshooting information.

Verify warranty and contract information

Verify that the warranty and contract information was discovered correctly in the Insight RS Console:
1. In the Insight RS Console, navigate to Devices and click the switch Device Name.
2. Expand the Hardware section, and make sure the Acquired Serial Number and Acquired Product
Number are correct. If they are not correct, type the correct values in the Override Serial Number and
Override Product Number fields and click Save Changes.

Note: If your SAN switch is covered by a critical service level contract then add CS4SAN to the
Custom Delivery ID field in order to elevate the response to service events.

Verify communication between monitored device

and Insight RS
To verify communication between your monitored device and Insight RS, complete the following sections:

Send a test event

Since B-Series Fabric-OS v6.3.x was released, B-Series switches can emit test traps to ensure that the
complete end-to-end event flow can be verified. The user must log on to the switch CLI admin interface and
issue the following command:
Send SNMP traps to test the configuration:
1. Telnet or SSH to the B-Series switch.
2. Show the available traps you can send as tests:
snmptraps --show
3. Send a blanket test trap for all tests:

HPE Insight Remote Support 7.10: Monitored Devices Configuration Guide Page 372 of 436
Chapter 33: Configuring StoreFabric B-Series switches

snmptraps --send
4. Or send a specific test trap:
snmptraps --send --trap_name <trapname>
For example:
snmptraps --send -trap_name cp-status-change-trap -ip_address <hosting_device_ip>
where <hosting_device_ip> is the IP address of the Hosting Device. If the switch reports that the test
trap cannot be sent, make sure snmpmibcaps is configured to send HA traps. If it is configured correctly,
this command should create a test event visible in the Insight RS Console and also submit an incident to
HPE.

Note: Not all traps result in an incident being delivered to the Insight RS Console. Not all traps are
sent and not all are received. Some get received as ‘unregistered event’ if you have that option
selected as a receive option in Events. The events that show up as ‘unregistered’ are not compiled
in the SIM Mibs. FA-MIB’s generate a valid hardware event.

See the B-Series Switch documentation for more details.

Verify collections in the Insight RS Console

Collections are not automatically run after discovery. HPE recommends that you manually run a collection
after discovery completes in order to verify connectivity. Run the collection schedule manually on the
Collection Services → Collection Schedules tab. For more information about scheduling collections, see the
Insight RS Help.
Verify that this collection ran successfully on the Collection Services → SAN Storage Collection Results tab
in the Insight RS Console.
1. Log on to the Insight RS Console.
2. In the main menu, select Collection Services and then click the SAN Storage Collection Results tab.
3. Expand the Storage Configuration Collection section.
4. Locate the entry for your device and check the Result column. If the collection was successful, a
success icon appears ( ). If it failed, an error icon appears ( ).

HPE Insight Remote Support 7.10: Monitored Devices Configuration Guide Page 373 of 436
 Chapter 34: Configuring StoreFabric C-Series
switches
Fulfill configuration requirements
To configure your StoreFabric C-Series switches to be monitored by Insight RS, complete the following
sections:
Table 34.1 StoreFabric C-Series switch configuration steps
Task Complete?

Make sure Insight RS supports your C-Series switch by checking the HPE Insight Remote
Support Release Notes.

Configure SNMP on the C-Series switch.

Add the SNMP protocol to the Insight RS Console.

Discover the C-Series switch in the Insight RS Console.

Verify the status of the C-Series switch in the Insight RS Console.

Send a test event to verify connectivity between your C-Series switch and Insight RS.

Install and configure communication software on

SAN switches
To configure your monitored devices, complete the following sections:

Configure SNMP
To configure C-Series (formerly Cisco) SNMP, complete the following steps:
1. Log on to the CLI interface with Telnet, or use Fabric Manager.
2. Use the CLI commands config t and snmp-server host <IP> traps version 1 public udp-port
162 commands to add the Hosting Device IP address as a trap destination.
3. Choose to have all events returned as traps.
4. If you choose a non-standard trap community name (i.e. a name other than public), make sure this
name is used in the Insight RS Console credentials settings.
5. Type the IP address of Hosting Device into one of the trap destination settings. You can also configure
this with the C-Series Device Manager.
6. Discover the device in the Insight RS Console.
7. In the Insight RS Console, navigate to Devices and click the Device Name. Verify that the device
information was discovered correctly.

HPE Insight Remote Support 7.10: Monitored Devices Configuration Guide Page 374 of 436
Chapter 34: Configuring StoreFabric C-Series switches

Configure firewall and port settings

Table 34.2 SAN Switch Connectivity - Firewall/Port Requirements
Protocol Ports Source Destination Function Optional

ICMP N/A Hosting Monitored Provides system reachability (ping) check during system Required
Device Systems discovery and before other operations.

UDP 161 Hosting Monitored SNMP. This is the standard port used by SNMP agents Required
Device Systems on monitored systems. The Hosting Device sends
requests to devices on this port.

UDP 162 Monitored Hosting SNMP Trap. This is the port used by Insight RS to listen Required
Systems Device to SNMP traps.

Add protocol credentials and start discovery

To discover your monitored devices, complete the following sections:

Create an SNMPv1 protocol credential in the Insight RS

Console
If your device's SNMP community string is set to public and your community access mode is read only,
Insight RS automatically associates an SNMPv1 protocol with your device. If you use a different community
string or use a nonstandard port, you must create an SNMPv1 protocol credential in the Insight RS Console.
To configure SNMPv1 in the Insight RS Console, complete the following steps:
1. In a web browser, log on to the Insight RS Console.
2. In the main menu, select Discovery and click the Credentials tab.
3. From the Select and Configure Protocol drop-down list, select Simple Network Management Protocol
Version 1, V2C (SNMPv1, SNMPv2C).
4. Click New. The New Credential dialog box appears.
5. Type the Community String you have configured on your device.
6. Click Add.
Insight RS creates the protocol credential and it appears in the credentials table.

Discover the device in the Insight RS Console

To discover the device from the Insight RS Console, complete the following steps:
1. In a web browser, log on to the Insight RS Console.
2. In the main menu, select Discovery and click the Sources tab.
3. Expand the IP Addresses section and add the IP address for your device:
a. Click New.
b. Select the Single Address, Address Range, or Address List option.

HPE Insight Remote Support 7.10: Monitored Devices Configuration Guide Page 375 of 436
Chapter 34: Configuring StoreFabric C-Series switches

c. Type the IP address(es) of the devices to be discovered.

d. Click Add.
4. Click Start Discovery.

Verify discovery and device status

To verify the device was discovered correctly, complete the following steps:
1. In a web browser, log on to the Insight RS Console.
2. In the main menu, select Devices and click the Device Summary tab.

3. Make sure the Status column contains a success icon ( ).

If there is no success icon, determine which column has the problem and consult the Online Help for
troubleshooting information.

Verify warranty and contract information

Verify that the warranty and contract information was discovered correctly in the Insight RS Console:
1. In the Insight RS Console, navigate to Devices and click the switch Device Name.
2. Expand the Hardware section, and make sure the Acquired Serial Number and Acquired Product
Number are correct. If they are not correct, type the correct values in the Override Serial Number and
Override Product Number fields and click Save Changes.

Note: If your SAN switch is covered by a critical service level contract then add CS4SAN to the
Custom Delivery ID field in order to elevate the response to service events.

Verify communication between monitored device

and Insight RS
To verify communication between your monitored device and Insight RS, complete the following sections:

Send a test event

Note: Do not pull a redundant FRU to test the configuration.

Cisco has recently introduced a CLI test command to validate the device end-to-end event connectivity.
1. From the CLI prompt, issue the following command:
test pfm test-SNMP-trap power
2. This causes the C-Series switch to send a bad power supply test event to the Hosting Device. If
everything is configured correctly, this event results in an incident viewable at HPE.

Note: You can also use test pfm test-SNMP-trap fan, but the temp type event, if used, will be
ignored.

HPE Insight Remote Support 7.10: Monitored Devices Configuration Guide Page 376 of 436
Chapter 34: Configuring StoreFabric C-Series switches

Note: The first Cisco test trap will be forwarded by Insight Remote Support to HPE, but subsequent
test traps will be suppressed for 24 hours before another test trap can be forwarded to HPE.

Verify collections in the Insight RS Console

Collections are not automatically run after discovery. HPE recommends that you manually run a collection
after discovery completes in order to verify connectivity. Run the collection schedule manually on the
Collection Services → Collection Schedules tab. For more information about scheduling collections, see the
Insight RS Help.
Verify that this collection ran successfully on the Collection Services → SAN Storage Collection Results tab
in the Insight RS Console.
1. Log on to the Insight RS Console.
2. In the main menu, select Collection Services and then click the SAN Storage Collection Results tab.
3. Expand the Storage Configuration Collection section.
4. Locate the entry for your device and check the Result column. If the collection was successful, a
success icon appears ( ). If it failed, an error icon appears ( ).

HPE Insight Remote Support 7.10: Monitored Devices Configuration Guide Page 377 of 436
 Chapter 35: Configuring StoreFabric H-Series
switches
Fulfill configuration requirements
To configure your StoreFabric H-Series switches to be monitored by Insight RS, complete the following
sections:
Table 35.1 StoreFabric H-Series switch configuration steps
Task Complete?

Make sure Insight RS supports your H-Series switch by checking the HPE Insight Remote
Support Release Notes.

Configure SNMP on the H-Series switch.

Add the SNMP protocol to the Insight RS Console.

Discover the H-Series switch in the Insight RS Console.

Verify the status of the H-Series switch in the Insight RS Console.

Install and configure communication software on

SAN switches
To configure your monitored devices, complete the following sections:

Configure SNMP
Log on to the switch with Telnet and issue the following CLI commands to configure the HPE SN6000, 8/20q
and 2/8q FC switches to send SNMP traps to the Hosting Device.
1. Open the Admin session:
admin start
2. Configure the SNMP trap destinations:
set setup snmp
3. After configuration, type y to save and active the SNMP setup.
4. Close the Admin session:
admin end

Configure firewall and port settings

Table 35.2 SAN Switch Connectivity - Firewall/Port Requirements
Protocol Ports Source Destination Function Optional

HPE Insight Remote Support 7.10: Monitored Devices Configuration Guide Page 378 of 436
Chapter 35: Configuring StoreFabric H-Series switches

Table 35.2 SAN Switch Connectivity - Firewall/Port Requirements, continued

ICMP N/A Hosting Monitored Provides system reachability (ping) check during system Required
Device Systems discovery and before other operations.

UDP 161 Hosting Monitored SNMP. This is the standard port used by SNMP agents Required
Device Systems on monitored systems. The Hosting Device sends
requests to devices on this port.

UDP 162 Monitored Hosting SNMP Trap. This is the port used by Insight RS to listen Required
Systems Device to SNMP traps.

Add protocol credentials and start discovery

To discover your monitored devices, complete the following sections:

Create an SNMPv1 protocol credential in the Insight RS

Console
If your device's SNMP community string is set to public and your community access mode is read only,
Insight RS automatically associates an SNMPv1 protocol with your device. If you use a different community
string or use a nonstandard port, you must create an SNMPv1 protocol credential in the Insight RS Console.
To configure SNMPv1 in the Insight RS Console, complete the following steps:
1. In a web browser, log on to the Insight RS Console.
2. In the main menu, select Discovery and click the Credentials tab.
3. From the Select and Configure Protocol drop-down list, select Simple Network Management Protocol
Version 1, V2C (SNMPv1, SNMPv2C).
4. Click New. The New Credential dialog box appears.
5. Type the Community String you have configured on your device.
6. Click Add.
Insight RS creates the protocol credential and it appears in the credentials table.

Discover the device in the Insight RS Console

To discover the device from the Insight RS Console, complete the following steps:
1. In a web browser, log on to the Insight RS Console.
2. In the main menu, select Discovery and click the Sources tab.
3. Expand the IP Addresses section and add the IP address for your device:
a. Click New.
b. Select the Single Address, Address Range, or Address List option.
c. Type the IP address(es) of the devices to be discovered.
d. Click Add.
4. Click Start Discovery.

HPE Insight Remote Support 7.10: Monitored Devices Configuration Guide Page 379 of 436
Chapter 35: Configuring StoreFabric H-Series switches

Verify discovery and device status

To verify the device was discovered correctly, complete the following steps:
1. In a web browser, log on to the Insight RS Console.
2. In the main menu, select Devices and click the Device Summary tab.

3. Make sure the Status column contains a success icon ( ).

If there is no success icon, determine which column has the problem and consult the Online Help for
troubleshooting information.

Verify warranty and contract information

Verify that the warranty and contract information was discovered correctly in the Insight RS Console:
1. In the Insight RS Console, navigate to Devices and click the switch Device Name.
2. Expand the Hardware section, and make sure the Acquired Serial Number and Acquired Product
Number are correct. If they are not correct, type the correct values in the Override Serial Number and
Override Product Number fields and click Save Changes.

Note: If your SAN switch is covered by a critical service level contract then add CS4SAN to the
Custom Delivery ID field in order to elevate the response to service events.

Verify communication between monitored device

and Insight RS
To verify communication between your monitored device and Insight RS, complete the following section:

Verify collections in the Insight RS Console

Collections are not automatically run after discovery. HPE recommends that you manually run a collection
after discovery completes in order to verify connectivity. Run the collection schedule manually on the
Collection Services → Collection Schedules tab. For more information about scheduling collections, see the
Insight RS Help.
Verify that this collection ran successfully on the Collection Services → SAN Storage Collection Results tab
in the Insight RS Console.
1. Log on to the Insight RS Console.
2. In the main menu, select Collection Services and then click the SAN Storage Collection Results tab.
3. Expand the Storage Configuration Collection section.
4. Locate the entry for your device and check the Result column. If the collection was successful, a
success icon appears ( ). If it failed, an error icon appears ( ).

HPE Insight Remote Support 7.10: Monitored Devices Configuration Guide Page 380 of 436
 Chapter 36: Configuring ProVision-based
networking switches
ProVision-based networking switches (formerly E-series/ProCurve) require SNMP for discovery and event
monitoring. ProVision-based switches ship with SNMP installed and enabled.
You can use either Telnet or SSH for configuration collections. Telnet is enabled on ProVision-based switches
by default. If you want to use SSH for configuration collections, you must enable it (see section "Enabling
SSH").

Fulfill configuration requirements

To configure your ProVision-based networking switches to be monitored by Insight RS, complete the
following sections:
Table 36.1 ProVision-based networking switch configuration steps
Task Complete?

Make sure Insight RS supports your ProVision-based switch by checking the HPE Insight
Remote Support Release Notes.

Create Operator/Manager passwords on the switch.

Configure SSH on the switch.

Configure SNMP on the switch.

Add the Telnet or SSH and SNMP protocols to the Insight RS Console.

Discover the ProVision-based switch in the Insight RS Console.

Install and configure communication software on

switches
To configure your monitored devices, complete the following sections:

Create operator/manager passwords

It is required that you set a manager password.
To set a manager password, complete the following steps:
1. Type the password all command. You are prompted to type manager and operator passwords:
# password all
2. Type the password manager command to set the manager password:
# password manager

Configure SSH
Generate the Public/Private key for SSH

HPE Insight Remote Support 7.10: Monitored Devices Configuration Guide Page 381 of 436
Chapter 36: Configuring ProVision-based networking switches

1. Type the config command to enable the global configuration mode:

# config
2. Type the crypto command to generate an RSA key pair, which includes one public RSA key and one
private RSA key.
# crypto key generate ssh rsa
Enable SSH
You only need to enable SSH if you want to use it instead of Telnet. If you choose to use Telnet, you can skip
this section.
To enable SSH, execute the following commands from the switch command line:
1. Type the config command to enable the global configuration mode:
# config
2. Enable the SSH server:
# ip ssh
3. Type the write memory command to save the configuration changes:
# write mem
For more information about ProVision-based switches, please refer to the ProVision-based switch
documentation for your switch model at: www.hpe.com/us/en/networking/switches.html.

Verify Telnet/SSH Communication

To verify that Telnet or SSH communication is working properly, complete the following steps:
1. From the Hosting Device, connect to the ProVision-based switch using the protocol you want to verify.
Wait until the connection is established.
2. Type the username and password when prompted. If any of the following messages do occur then, it is
treated to be a login failure:
l Login incorrect
l User authorization failure
l Invalid login name
l Too many users logged on already
3. When the banner or login data is received, send a carriage return (\n) to make sure that the host is ready.
4. Type the exit command to disconnect.

Configure SNMPv1/v2 communication

To set the Hosting Devices as a trap destination and verify SNMP communication is working properly,
complete the following steps:
1. Type the show version command to determine which software version your ProVision-based switch is
running:
# sho ver

HPE Insight Remote Support 7.10: Monitored Devices Configuration Guide Page 382 of 436
Chapter 36: Configuring ProVision-based networking switches

2. Type the config command to enable the global configuration mode:

# config
3. The output should show a version number similar to x.14.60, where x will be a letter such as K.
4. Use the snmp-server command to type the Hosting Device's IP address. Depending on the version of
the firmware on the ProVision-based switch, use one of the following versions of the command:

Firmware version Command

14.60 and lower # snmp-server host <IP address> public not-info

14.61 and higher # snmp-server host <IP address> community public trap-level
not-info

5. Verify that the settings you just typed were saved:

# sho run
6. Type the write memory command to save the configuration changes:
# write mem

Configure SSH public key authentication

Option 1: Using the Hosting Device certificate

Prerequisites
l TFTP server — used to move the public key to the ProVision-based switch.

Copy the certificate to the switch

To copy the certificate to the ProVision-based switch, complete the following steps:
1. On the Hosting Device, export the Hosting Device public key. The alias name is “jetty”:
rsadmin cert -export -keycomment manager@[IP_of_switch] -sshkey -out [file_path_name]
where file_path_name is a path that the TFTP server can see.
2. Telnet or SSH to the switch using username/password authentication.
3. Enter configuration mode:
configure
4. Turn off filetransfer using SSH:
no ip ssh filetransfer
5. Enable the TFTP client:
tftp client
6. Move the public key to the switch:
copy tftp pub-key-file <tftp_server_ip> <public_key_file> manager
7. Enable public key authentication:

HPE Insight Remote Support 7.10: Monitored Devices Configuration Guide Page 383 of 436
Chapter 36: Configuring ProVision-based networking switches

aaa authentication ssh login public-key

8. Enable user/password authentication:
aaa authentication ssh enable local
9. Write the configuration and public key to memory:
wr mem

Create an SSH protocol credential in the Insight RS Console

To configure SSH in the Insight RS Console, complete the following steps:
1. In the Insight RS Console, add a SSH certificate credential on the Discovery → Credentials tab.
a. From the Select and Configure Protocol drop-down list, select Secure Shell (SSH) and click
New.
b. From the Type drop-down list, select Certificate Credential.
c. Leave the File Upload field blank because the certificate is already in the certificate store and it is
identified by using the alias name.
d. Type the Certificate Alias of “jetty-manager”, which is the alias given to the certificate when it was
exported above.

2. Click Add.

HPE Insight Remote Support 7.10: Monitored Devices Configuration Guide Page 384 of 436
Chapter 36: Configuring ProVision-based networking switches

Option 2: Using other certificates

Prerequisites
l PuTTYgen — used to generate a key pair if required.
l TFTP server — used to move the public key to a ProVision-based switch.

Copy the certificate to the switch

To copy the certificate to the ProVision-based switch, complete the following steps:
1. Use PuTTYgen to create a key pair.
2. Change the public key comment field in PuTTYgen to manager@IP for operator account access where IP
is the IP of the switch or manager@ip for manager account access.
3. Copy the public key to a file path that your TFTP server can see. (Refer to the TFTP server
documentation and server configuration for more information.)
4. In PuTTYgen, select Conversions → Export OpenSSH Key to export the private key. Don’t set a pass
phrase. Name the private key PCPrivate.pem.
5. Telnet or SSH to the switch using username/password authentication.
6. Enter configuration mode:
configure
7. Turn off filetransfer using SSH:
no ip ssh filetransfer
8. Enable the TFTP client:
tftp client
9. Move the public key to the switch:
copy tftp pub-key-file <tftp_server_ip> <public_key_file> manager
10. Enable public key authentication:
aaa authentication ssh login public-key
11. Enable user/password authentication:
aaa authentication ssh enable local
12. Write the configuration and public key to memory:
wr mem

Create an SSH protocol credential in the Insight RS Console

To configure SSH in the Insight RS Console, complete the following steps:
1. In the Insight RS Console, add a SSH certificate credential on the Discovery → Credentials tab.
a. From the Select and Configure Protocol drop-down list, select Secure Shell (SSH) and click
New.

HPE Insight Remote Support 7.10: Monitored Devices Configuration Guide Page 385 of 436
Chapter 36: Configuring ProVision-based networking switches

b. From the Type drop-down list, select Certificate Credential.

c. Browse to the private key file, PCPrivate.pem.
d. Type the Certificate Alias. The alias will take the form of switchname-manager. The SSH protocol
uses the -manager portion of the alias as the user name during log on.

2. Click Add.

Configure firewall and port settings

Table 36.2 ProVision-based Switch Connectivity - Firewall/Port Requirements
Protocol Ports Source Destination Function Optional

ICMP N/A Hosting Monitored Provides system reachability (ping) check during system Required
Device Systems discovery and before other operations.

TCP 22 Hosting Monitored SSH: Remote Data Collection Optional

Device Systems

UDP 161 Hosting Monitored SNMP. This is the standard port used by SNMP agents Required
Device Systems on monitored systems. The Hosting Device sends
requests to devices on this port.

UDP 162 Monitored Hosting SNMP Trap. This is the port used by Insight RS to listen Required
Systems Device to SNMP traps.

Add protocol credentials and start discovery

To discover your monitored devices, complete the following sections:

HPE Insight Remote Support 7.10: Monitored Devices Configuration Guide Page 386 of 436
Chapter 36: Configuring ProVision-based networking switches

Create an SNMPv1/v2 protocol credential in the Insight RS

Console
If your device's SNMP community string is set to public and your community access mode is read only,
Insight RS automatically associates an SNMPv1 protocol with your device. If you use a different community
string or use a nonstandard port, you must create an SNMPv1 protocol credential in the Insight RS Console.
To configure SNMPv1/v2 in the Insight RS Console, complete the following steps:
1. In a web browser, log on to the Insight RS Console.
2. In the main menu, select Discovery and click the Credentials tab.
3. From the Select and Configure Protocol drop-down list, select Simple Network Management Protocol
Version 1, V2C (SNMPv1, SNMPv2C).
4. Click New. The New Credential dialog box appears.
5. Type the Community String you have configured on your device.
6. Click Add.
Insight RS creates the protocol credential and it appears in the credentials table.

Discover the device in the Insight RS Console

To discover the device from the Insight RS Console, complete the following steps:
1. In a web browser, log on to the Insight RS Console.
2. In the main menu, select Discovery and click the Sources tab.
3. Expand the IP Addresses section and add the IP address for your device:
a. Click New.
b. Select the Single Address, Address Range, or Address List option.
c. Type the IP address(es) of the devices to be discovered.
d. Click Add.
4. Click Start Discovery.

Verify discovery and device status

To verify the device was discovered correctly, complete the following steps:
1. In a web browser, log on to the Insight RS Console.
2. In the main menu, select Devices and click the Device Summary tab.

3. Make sure the Status column contains a success icon ( ).

If there is no success icon, determine which column has the problem and consult the Online Help for
troubleshooting information.

HPE Insight Remote Support 7.10: Monitored Devices Configuration Guide Page 387 of 436
Chapter 36: Configuring ProVision-based networking switches

Verify communication between monitored device

and Insight RS
To verify communication between your monitored device and Insight RS, complete the following section:

Verify collections in the Insight RS Console

Collections are not automatically run after discovery. HPE recommends that you manually run a collection
after discovery completes in order to verify connectivity. Run the collection schedule manually on the
Collection Services → Collection Schedules tab. For more information about scheduling collections, see the
Insight RS Help.
Verify that this collection ran successfully on the Collection Services → Basic Collection Results tab in the
Insight RS Console.
1. Log on to the Insight RS Console.
2. In the main menu, select Collection Services and then click the Basic Collection Results tab.
3. Expand the Network Configuration Collection section.
4. Locate the entry for your device and check the Result column. If the collection was successful, a
success icon appears ( ). If it failed, an error icon appears ( ).

HPE Insight Remote Support 7.10: Monitored Devices Configuration Guide Page 388 of 436
 Chapter 37: Configuring Altoline networking
switches
Important: Altoline switches require the installation of Content Level Update 7.7.0.50. Altoline
switches also require Patch 7.7.0.42 or 7.7.0.49 be installed or discovery will not complete
successfully.

Fulfill configuration requirements

To configure your Altoline networking switches to be monitored by Insight RS, complete the following
sections:
Table 37.1 ProVision-based networking switch configuration steps
Task Complete?

Make sure Insight RS supports your Altoline switch by checking the HPE Insight Remote Support
Release Notes.

Configure SNMP on the Altoline switch.

Add the SNMP protocol to the Insight RS Console.

Discover the Altoline switch in the Insight RS Console.

Configure switch and communication software on

switches
To configure your monitored devices, complete the following sections:

Configure network and SNMP communication

There are three Altoline NOS options. Insight RS supports Pica8 and Cumulus Linux:
l Option 1: Pica8
l Option 2: Cumulus Linux
l Option 3: OpenSwitch—Insight RS does not support this HPE Networks NOS because there is currently
no SNMP hardware monitoring in the OpenSwitch NOS.

Option 1: Configure Pica8

Pica8 offer a Debian Linux based NOS called XorPlus. This NOS supports hardware FRU monitoring via
SNMP and a configuration CLI. This is the simplest NOS to configure for monitoring by Insight RS.
If PicOS is already installed, it will be in L2/L3 mode by default. Otherwise boot to the ONIE by entering run
onie_bootcmd at the U-Boot (=>) prompt. At the ONIE GRUB screen, PicOS will be installed.
Additional system configuration information can be found at the following URL:
www.pica8.com/wp-content/uploads/2015/09/v2.8/html/picos-system-configuration/

HPE Insight Remote Support 7.10: Monitored Devices Configuration Guide Page 389 of 436
Chapter 37: Configuring Altoline networking switches

Configure the L2/L3 mode IP address

If the switch found a DHCP server during boot, you can SSH to the switch, otherwise use the serial console
and set a temporary static IP address:
1. Log into the switch XorPlus console as admin using the default password of pica8. You will be asked to
set up the new UNIX password to proceed.
2. Type: sudo ifconfig eth0 <ip_address>
3. SSH to the switch.

Set the IP address of the management port

By default, the Management port will get its IP address from the DHCP server. To configure the IP address,
complete the following steps:
1. Enter the PicOS command line utility mode by typing cli at the XorPlus console prompt.
2. Enter the configuration mode by typing configure.
3. DHCP is the default PicOS management port mode, but can be set with this command:
set interface management-ethernet eth0 dhcp enable true
4. Alternatively, to set a static IP address for the management port:
set interface management-ethernet eth0 address <ip_address>
5. To set a gateway for the management port:
set interface management-ethernet eth0 gateway <ip_address>
6. To store these values permanently, type commit at the PicOS prompt.
7. If required, set the time-zone and clock information. You may use: set system management-ethernet.

Configure SNMP
At the PicOS configuration prompt, enter these commands to configure the SNMP agent:
1. Set the SNMP (RO) community name:
set protocols snmp community public
2. Set the contact name:
set protocols snmp contact <contact_name>
3. Set the switch location:
set protocols snmp location <switch_location>
4. Set the trap receiver (Insight RS):
set protocols snmp trap-group targets <ip_of_hosting_device>
5. Set the trap version:
set protocols snmp trap-group version v1
6. Save the current configuration and exit the configuration mode.

Option 2: Configure Cumulus Linux

HPE Insight Remote Support 7.10: Monitored Devices Configuration Guide Page 390 of 436
Chapter 37: Configuring Altoline networking switches

Set the IP address of the management interface

1. To set a static IP address for the management interface, use the net add interface eth0 address
<ip address/(CIDR)> command.
2. To set a gateway address for the management interface, use the net add interface eth0 gateway
<ip address> command.
3. To review these settings for the management interface, use the net pending command.
4. To make these values permanent for the management interface, use the net commit command.
Now you can SSH to the switch and change the hostname, time-zone information and install your license
(refer to the standard Cumulus installation notes at:
docs.cumulusnetworks.com/display/DOCS/Quick+Start+Guide).

Configure SNMP
To configure SNMP, complete the following steps:
1. Start the SNMP daemon: sudo systemctl start snmpd.service
2. To enable the SNMP daemon to run automatically after a reboot:
a. Type: sudo systemctl enable snmpd.service
b. Create a file called /etc/system/system/snmpd.service.d/restart.conf
c. Enter these lines and save the file:
[Service[
Restart=always
RestartSec=60

d. Run this command to reload the SNMP agent daemon: sudo systemctl daemon-reload
3. Edit the /etc/snmp/snmpd.conf file to configure values in the SNMP agent using nano or another file
editor.
a. To enable agent access:
o Comment out the line agentAddress udp:127.0.0.1:161
o Uncomment the line agentAddress udp:161,udp6:[::1]:161
b. Uncomment the lines:
o rocommunity public default -V systemonly
o rocommunity public localhost
c. Set your sysLocation and sysContact in the System Information section.
d. Uncomment the line trapsink localhost public and replace localhost with the IP address of your
Insight RS Hosting Device.
e. Uncomment the line defaultMonitors yes.
f. In the same area, uncomment these two lines:
o iquerySecName internalUser
o rouser internalUser

HPE Insight Remote Support 7.10: Monitored Devices Configuration Guide Page 391 of 436
Chapter 37: Configuring Altoline networking switches

g. Save the /etc/snmp/snmpd.conf file and issue the command: sudo systemctl restart
snmpd.service
4. To test the SNMP agent is running, walk the MIB tables. Note down the OIDs and values for both tables.
These will be used in the next step in the agent configuration.
a. Type the following command to walk one of the Entity MIB tables:
snmpwalk -v 2c -c public localhost .1.3.6.1.2.1.47.1.1.1.1.7
b. Type the following command to walk one of the Entity Sensor MIB tables:
snmpwalk -v 2c -c public localhost .1.3.6.1.2.1.99.1.1.1.5
5. Cumulus Linux can be configured to monitor the status of the FRU’s in the switch and send SNMP traps
to Insight RS. For more details, see docs.cumulusnetworks.com/display/DOCS/SNMP+Monitoring.
a. For each of the FRU’s listed in the Entity MIB table walked earlier, create a monitor entry in the
/etc/snmp/snmpd.conf file.
b. For each of the PSU and Fan items in the Entity MIB table walked earlier, create a monitor entry in
the Active Monitoring section of the /etc/snmp/snmpd.conf file.
For example:
monitor -I -r 10 -o 1.3.6.1.2.1.47.1.1.1.1.7.<FRU_OID> "Fan tray number, fan
location" 1.3.6.1.2.1.99.1.1.1.5.<Sensor_OID> > 1
where the first OID is OID of the Fan or PSU in the Entity MIB table and the second OID is the OID of the
Fan or PSU operational status in the Entity Sensor table.
When created for each of the FRUs to be monitored, this section will look like the below example (your
switch will have different OID numbers). Note on the first line, Fan #1 is set to alert if the operational
status is less than 2. This is to create a test of the whole trap reporting system in order to complete this
configuration. After you verify that Insight RS received the trap, change this alert status to > 1.
monitor -I -r 10 -o 1.3.6.1.2.1.47.1.1.1.1.2.100011001 "Fan tray 1, fan A"
1.3.6.1.2.1.99.1.1.1.5.100011001 < 2
monitor -I -r 10 -o 1.3.6.1.2.1.47.1.1.1.1.2.100011001 "Fan tray 1, fan A"
1.3.6.1.2.1.99.1.1.1.5.100011001 > 1
monitor -I -r 10 -o 1.3.6.1.2.1.47.1.1.1.1.2.100011002 "Fan tray 1, fan B"
1.3.6.1.2.1.99.1.1.1.5.100011002 > 1
monitor -I -r 10 -o 1.3.6.1.2.1.47.1.1.1.1.2.100011003 "Fan tray 2, fan A"
1.3.6.1.2.1.99.1.1.1.5.100011003 > 1
monitor -I -r 10 -o 1.3.6.1.2.1.47.1.1.1.1.2.100011004 "Fan tray 2, fan B"
1.3.6.1.2.1.99.1.1.1.5.100011004 > 1
monitor -I -r 10 -o 1.3.6.1.2.1.47.1.1.1.1.2.100011005 "Fan tray 3, fan A"
1.3.6.1.2.1.99.1.1.1.5.100011005 > 1
monitor -I -r 10 -o 1.3.6.1.2.1.47.1.1.1.1.2.100011006 "Fan tray 3, fan B"
1.3.6.1.2.1.99.1.1.1.5.100011006 > 1
monitor -I -r 10 -o 1.3.6.1.2.1.47.1.1.1.1.2.100011007 "Fan tray 4, fan A"
1.3.6.1.2.1.99.1.1.1.5.100011007 > 1
monitor -I -r 10 -o 1.3.6.1.2.1.47.1.1.1.1.2.100011008 "Fan tray 4, fan B"
1.3.6.1.2.1.99.1.1.1.5.100011008 > 1

HPE Insight Remote Support 7.10: Monitored Devices Configuration Guide Page 392 of 436
Chapter 37: Configuring Altoline networking switches

monitor -I -r 10 -o 1.3.6.1.2.1.47.1.1.1.1.2.100011009 "Fan tray 5, fan A"

1.3.6.1.2.1.99.1.1.1.5.100011009 > 1
monitor -I -r 10 -o 1.3.6.1.2.1.47.1.1.1.1.2.100011010 "Fan tray 5, fan B"
1.3.6.1.2.1.99.1.1.1.5.100011010 > 1
monitor -I -r 10 -o 1.3.6.1.2.1.47.1.1.1.1.2.100011011 "PSU 1 Fan"
1.3.6.1.2.1.99.1.1.1.5.100011011 > 1
monitor -I -r 10 -o 1.3.6.1.2.1.47.1.1.1.1.2.100011012 "PSU 2 Fan"
1.3.6.1.2.1.99.1.1.1.5.100011012 > 1
monitor -I -r 10 -o 1.3.6.1.2.1.47.1.1.1.1.2.110000001 "PSU 1"
1.3.6.1.2.1.99.1.1.1.5.110000001 > 1
monitor -I -r 10 -o 1.3.6.1.2.1.47.1.1.1.1.2.110000002 "PSU 2"
1.3.6.1.2.1.99.1.1.1.5.110000002 > 1
monitor -I -r 10 -o 1.3.6.1.2.1.47.1.1.1.1.2.100000001 "PSU 1 intake temperature
sensor" 1.3.6.1.2.1.99.1.1.1.5.100000001 > 1
monitor -I -r 10 -o 1.3.6.1.2.1.47.1.1.1.1.2.100000002 "PSU 1 max temperature sensor"
1.3.6.1.2.1.99.1.1.1.5.100000002 > 1
monitor -I -r 10 -o 1.3.6.1.2.1.47.1.1.1.1.2.100000003 "PSU 2 intake temperature
sensor" 1.3.6.1.2.1.99.1.1.1.5.100000003 > 1

6. Save the /etc/snmp/snmpd.conf file and issue the command: sudo systemctl restart
snmpd.service
7. Comment out the first line and re-save the /etc/snmp/snmpd.conf file and issue the command: sudo
systemctl restart snmpd.service

Add protocol credentials and start discovery

To discover your monitored devices, complete the following sections:

Create an SNMP protocol credential in the Insight RS

Console
Create an SNMP protocol credential for the version of SNMP that you configured on your switch:

Create an SNMPv1 protocol credential in the Insight RS Console

If your device's SNMP community string is set to public and your community access mode is read only,
Insight RS automatically associates an SNMPv1 protocol with your device. If you use a different community
string or use a nonstandard port, you must create an SNMPv1 protocol credential in the Insight RS Console.
To configure SNMPv1 in the Insight RS Console, complete the following steps:
1. In a web browser, log on to the Insight RS Console.
2. In the main menu, select Discovery and click the Credentials tab.
3. From the Select and Configure Protocol drop-down list, select Simple Network Management Protocol
Version 1, V2C (SNMPv1, SNMPv2C).
4. Click New. The New Credential dialog box appears.

HPE Insight Remote Support 7.10: Monitored Devices Configuration Guide Page 393 of 436
Chapter 37: Configuring Altoline networking switches

5. Type the Community String you have configured on your device.

6. Click Add.
Insight RS creates the protocol credential and it appears in the credentials table.

Discover the device in the Insight RS Console

To discover the device from the Insight RS Console, complete the following steps:
1. In a web browser, log on to the Insight RS Console.
2. In the main menu, select Discovery and click the Sources tab.
3. Expand the IP Addresses section and add the IP address for your device:
a. Click New.
b. Select the Single Address, Address Range, or Address List option.
c. Type the IP address(es) of the devices to be discovered.
d. Click Add.
4. Click Start Discovery.

Add warranty and contract information

Neither the Pica8 NOS nor the Cumulus Linux NOS expose the serial number and product number over
SNMP. Therefore, after device discovery, you must enter product data manually for entitlement.
Too add the serial number and product number, complete the following steps:
1. In the Insight RS Console, navigate to Devices and click the Device Name.
2. Expand the Hardware section, and type the correct serial number and product number in the Override
Serial Number and Override Product Number fields.
3. Click Save Changes.

Verify discovery and device status

To verify the device was discovered correctly, complete the following steps:
1. In a web browser, log on to the Insight RS Console.
2. In the main menu, select Devices and click the Device Summary tab.

3. Make sure the Status column contains a success icon ( ).

If there is no success icon, determine which column has the problem and consult the Online Help for
troubleshooting information.

HPE Insight Remote Support 7.10: Monitored Devices Configuration Guide Page 394 of 436
 Chapter 38: Configuring Comware-based
networking switches
Comware-based networking switches (formerly A-Series or H3C/3COM) require SNMP for discovery and
event monitoring.

Intelligent Resilient Framework Support

Insight RS supports Intelligent Resilient Framework (IRF) technology, and can detect the following IRF alerts:
l Power supply failures
l Fans and fan tray failures
l Module and board failures
l Over-temperature conditions
Insight RS only discovers the master switch in an IRF stack, and the rest of the switches in the stack are
identified through the MIB information. After the IRF stack is built, the master switch's IP address becomes a
virtual IP (VIP). The VIP remains stable even if the master role changes to a different member switch due to a
master switch failure. If the master switch fails, a new master takes its place, and the stack configuration is
identified through the MIB refresh.
When Insight RS discovers the IRF stack, an Object of Service (OOS) is created that contains the credentials
of the master switch at the time of discovery. When an event is sent to HPE, these credentials are checked
for entitlement, but even if the master has failed over to an undiscovered (but entitled) IRF member switch,
and the Serial Number of the master has thereby changed, the OOS will not change unless there has been an
intervening re-discovery of the IRF.
However, to satisfy the entitlement checks within Insight RS, HPE recommends that before an IRF stack is
built, each switch should be individually discovered to verify it has a valid warranty or contract and is eligible
for remote support. This prevents the scenario where the master switch fails over to a switch that does not
have a valid warranty or contract and is therefore not eligible for remote support. If the new master is not
eligible, the entire IRF stack becomes ineligible. If you do not want to disassemble an existing stack, make
sure that all member switches have a valid warranty or contract.

Important: Make sure all IRF stack member switches have a valid warranty or contract. If the
master switch fails, the member switch assigned to be the new master switch must also have a
valid warranty or contract for the stack to continue to be entitled for remote support. If the stack has
not been built yet, you can verify entitlement by discovering each switch individually. If the stack
has already been built you must verify each switch has a valid warranty or contract manually.

Fulfill configuration requirements

To configure your Comware-based networking switches to be monitored by Insight RS, complete the
following sections:

HPE Insight Remote Support 7.10: Monitored Devices Configuration Guide Page 395 of 436
Chapter 38: Configuring Comware-based networking switches

Table 38.1 Comware-based Networking Switch configuration steps

Task Complete?

Make sure Insight RS supports your Comware-based switch by checking the HPE Insight
Remote Support Release Notes.

Configure Telnet or SSH on the switch.

Configure SNMP traps on the switch.

Add SNMP protocol credentials to the Insight RS Console for monitoring.

Add Telnet or SSH protocol credentials to the Insight RS Console for collections.

Discover the Comware-based switch in the Insight RS Console.

Verify SNMP communication.

Install and configure communication software on

switches
To configure your monitored devices, complete the following sections:

Configure Telnet or SSH

To configure trap destinations to point to Insight Remote Support, you need to use Telnet or SSH (or use a
serial console) to access the CLI. You also need to configure Telnet or SSH to enable collection services.
Use the below procedures to configure Telnet or SSH.

Configuring Telnet
From a serial console, complete the following steps:
1. Enter system view, and enable the Telnet service.
<Sysname> system-view
[Sysname] telnet server enable

2. Configure an IP address for VLAN interface 1. This address will serve as the destination of the Telnet
connection.
[Switch] interface vlan-interface 1
[Switch-Vlan-interface1] ip address <ip_address> 255.255.255.0
[Switch-Vlan-interface1] quit

3. Set the authentication mode for the user interfaces to AAA.

[Switch] user-interface vty 0 4
[Switch-ui-vty0-4] authentication-mode scheme

4. Enable the user interfaces to support Telnet.

[Switch-ui-vty0-4] protocol inbound telnet
[Switch-ui-vty0-4] quit

5. Create local user manager, and set the user command privilege level to 3

HPE Insight Remote Support 7.10: Monitored Devices Configuration Guide Page 396 of 436
Chapter 38: Configuring Comware-based networking switches

[Switch] local-user manager

[Switch-luser-client001] password simple <password>
[Switch-luser-client001] service-type telnet

l If using Comware versions v7.1.045 or later:

[Switch-luser-client001] authorization-attribute user-role network-admin
l If using Comware versions below v7.1.045:
[Switch-luser-client001] authorization-attribute level 3
[Switch-luser-client001] quit
Configuring SSH version 2
From a serial console, complete the following steps:
1. <Switch> system-view
[Switch] public-key local create rsa
[Switch] public-key local create dsa
[Switch] ssh server enable

2. Configure an IP address for VLAN interface 1. This address will serve as the destination of the SSH
connection.
[Switch] interface vlan-interface 1
[Switch-Vlan-interface1] ip address <ip_address> 255.255.255.0
[Switch-Vlan-interface1] quit

3. Set the authentication mode for the user interfaces to AAA.

[Switch] user-interface vty 0 4
[Switch-ui-vty0-4] authentication-mode scheme

4. Enable the user interfaces to support SSH.

[Switch-ui-vty0-4] protocol inbound ssh
[Switch-ui-vty0-4] quit

5. Create local user manager, and set the user command privilege level to 3.
[Switch] local-user manager
[Switch-luser-client001] password simple <password>
[Switch-luser-client001] service-type ssh

l If using Comware versions v7.1.045 or later:

[Switch-luser-client001] authorization-attribute user-role network-admin
l If using Comware versions below v7.1.045:
[Switch-luser-client001] authorization-attribute level 3
[Switch-luser-client001] quit
Verifying Telnet/SSH communication
To verify that Telnet or SSH communication is working properly, complete the following steps:

HPE Insight Remote Support 7.10: Monitored Devices Configuration Guide Page 397 of 436
Chapter 38: Configuring Comware-based networking switches

1. From the Hosting Device, connect to the Comware-based switch using the protocol you want to verify.
Wait until the connection is established.
2. Type the username and password when prompted.
A successful log on confirms that Telnet/SSH is configured properly.

Setup SNMPv1 traps

Comware-based networking switches can be configured to use SNMPv1.
From a serial console, or through SSH or Telnet, complete the following steps:
1. <Sysname> system-view
[Sysname] snmp-agent sys-info version v1
[Sysname] snmp-agent community read public

2. Enable SNMP traps, and set the Hosting Device as the trap destination. Use public as the community
name.
[Sysname] snmp-agent trap enable
[Sysname] snmp-agent target-host trap address udp-domain <hosting_device_ip> params
securityname public v1

3. Save the configuration

From a serial console, complete the following steps:
a. Save your configuration changes by issuing the save command.
b. When prompted that the "current configuration will be written to the device", type Y.
c. Press Enter to leave the existing filename unchanged.
d. When prompted to overwrite the existing *.cfg file, type Y.
A confirmation message appears when the current configuration saves successfully.

Configure firewall and port settings

Table 38.2 Comware-based Switch Connectivity - Firewall/Port Requirements
Protocol Ports Source Destination Function Optional

ICMP N/A Hosting Monitored Provides system reachability (ping) check during system Required
Device Systems discovery and before other operations.

TCP 22 Hosting Monitored SSH: Remote Data Collection Optional

Device Systems

UDP 161 Hosting Monitored SNMP. This is the standard port used by SNMP agents Required
Device Systems on monitored systems. The Hosting Device sends
requests to devices on this port.

UDP 162 Monitored Hosting SNMP Trap. This is the port used by Insight RS to listen Required
Systems Device to SNMP traps.

HPE Insight Remote Support 7.10: Monitored Devices Configuration Guide Page 398 of 436
Chapter 38: Configuring Comware-based networking switches

Add protocol credentials and start discovery

To discover your monitored devices, complete the following sections:

Create an SNMPv1 protocol credential in the Insight RS

Console
If your device's SNMP community string is set to public and your community access mode is read only,
Insight RS automatically associates an SNMPv1 protocol with your device. If you use a different community
string or use a nonstandard port, you must create an SNMPv1 protocol credential in the Insight RS Console.
To configure SNMPv1 in the Insight RS Console, complete the following steps:
1. In a web browser, log on to the Insight RS Console.
2. In the main menu, select Discovery and click the Credentials tab.
3. From the Select and Configure Protocol drop-down list, select Simple Network Management Protocol
Version 1, V2C (SNMPv1, SNMPv2C).
4. Click New. The New Credential dialog box appears.
5. Type the Community String you have configured on your device.
6. Click Add.
Insight RS creates the protocol credential and it appears in the credentials table.

Create a Telnet or SSH protocol in the Insight RS Console

Create a Telnet or SSH protocol credential in the Insight RS Console. You do not need to configure both.

Create a Telnet protocol in the Insight RS Console

To configure Telnet in the Insight RS Console, complete the following steps:
1. In a web browser, log on to the Insight RS Console.
2. In the main menu, select Discovery and click the Credentials tab.
3. From the Select and Configure Protocol drop-down list, select Telnet.
4. Click New. The New Credential dialog box appears.
Insight RS creates the protocol credential and it appears in the credentials table.

Create an SSH protocol credential in the Insight RS Console

To configure SSH in the Insight RS Console, complete the following steps:
1. In a web browser, log on to the Insight RS Console.
2. In the main menu, select Discovery and click the Credentials tab.
3. From the Select and Configure Protocol drop-down list, select Secure Shell (SSH).
4. Click New. The New Credential dialog box appears.

HPE Insight Remote Support 7.10: Monitored Devices Configuration Guide Page 399 of 436
Chapter 38: Configuring Comware-based networking switches

5. Type the Username and Password you have configured on your device.
6. Click Add.
Insight RS creates the protocol credential and it appears in the credentials table.

Discover the device in the Insight RS Console

Important: ICMP is used by Insight RS for discovery. Make sure you have ICMP enabled on your
device.

To discover the device from the Insight RS Console, complete the following steps:
1. In a web browser, log on to the Insight RS Console.
2. In the main menu, select Discovery and click the Sources tab.
3. Expand the IP Addresses section and add the IP address for your device:

Note: If your switch is part of an IRF stack, only discover the master switch. The rest of the
switches in the stack are identified through the MIB information.

a. Click New.
b. Select the Single Address, Address Range, or Address List option.
c. Type the IP address(es) of the devices to be discovered.
d. Click Add.
4. Click Start Discovery.

Verify discovery and device status

To verify the device was discovered correctly, complete the following steps:
1. In a web browser, log on to the Insight RS Console.
2. In the main menu, select Devices and click the Device Summary tab.

3. Make sure the Status column contains a success icon ( ).

If there is no success icon, determine which column has the problem and consult the Online Help for
troubleshooting information.

Verify warranty and contract information

Verify that the warranty and contract information was discovered correctly in the Insight RS Console:
1. In the Insight RS Console, navigate to Devices and click the switch Device Name.
2. Expand the Hardware section, and make sure the Acquired Serial Number and Acquired Product
Number are correct. If they are not correct, type the correct values in the Override Serial Number and
Override Product Number fields and click Save Changes.

HPE Insight Remote Support 7.10: Monitored Devices Configuration Guide Page 400 of 436
Chapter 38: Configuring Comware-based networking switches

Verify communication between monitored device

and Insight RS
To verify communication between your monitored device and Insight RS, complete the following sections:

Verifying SNMP communication

There is not a way to manually verify the SNMP configuration without generating an event, which can only be
accomplished by performing an action like pulling a fan tray or disconnecting a power supply.

Note: Do not pull a redundant FRU to test the configuration.

You can verify SNMP communication by reviewing the running configuration from the Comware-based switch
command line. Look for the snmp-agent section in the output and verify that the community string is correct
and the trap destination is the Hosting Device.
To display the running configuration, run the following command:
> display current-configuration
# snmp-agent snmp-agent community read public snmp-agent sys-info version v1 snmp-agent
target-host trap address udp-domain <hosting_device_ip> params securityname public v1 #
If any of the settings are incorrect, use the undo command to remove the setting, for example, undo snmp-
agent community read public. Then return to "Setup SNMPv1 traps" on page 398 and reconfigure the
setting that was incorrect.

Verify collections in the Insight RS Console

Collections are not automatically run after discovery. HPE recommends that you manually run a collection
after discovery completes in order to verify connectivity. Run the collection schedule manually on the
Collection Services → Collection Schedules tab. For more information about scheduling collections, see the
Insight RS Help.
Verify that this collection ran successfully on the Collection Services → Basic Collection Results tab in the
Insight RS Console.
1. Log on to the Insight RS Console.
2. In the main menu, select Collection Services and then click the Basic Collection Results tab.
3. Expand the Network Configuration Collection section.
4. Locate the entry for your device and check the Result column. If the collection was successful, a
success icon appears ( ). If it failed, an error icon appears ( ).

HPE Insight Remote Support 7.10: Monitored Devices Configuration Guide Page 401 of 436
 Chapter 39: Configuring Mellanox InfiniBand
Switches
InfiniBand switches require SNMP for discovery, event monitoring, and collections.

Fulfill configuration requirements

To configure your InfiniBand switches to be monitored by Insight RS, complete the following sections:
Table 39.1 InfiniBand switch configuration steps
Task Complete?

Make sure Insight RS supports your InfiniBand switch by checking the HPE Insight Remote
Support Release Notes.

Configure SNMP traps on the switch.

Add SNMP protocol credentials to the Insight RS Console for monitoring.

Discover the InfiniBand switch in the Insight RS Console.

Verify SNMP communication.

Install and configure communication software on

switches
To configure your monitored devices, complete the following sections:

Setup SNMP traps

InfiniBand switches can be configured to use either SNMPv1, SNMPv2 or SNMPv3. Choose one of the
methods below:

Configure SNMPv1/v2
From a console, complete the following steps:
1. Activate the SNMP server on the switch (in configure mode) using the following commands:
switch (config) # snmp-server enable
switch (config) # snmp-server enable notify
switch (config) # snmp-server community public ro
switch (config) # snmp-server contact "contact name"
switch (config) # snmp-server host <hosting_device_IP_address> traps version 2c
public
switch (config) # snmp-server location "location name"
switch (config) # snmp-server user admin v3 enable
switch (config) # snmp-server user admin v3 prompt auth md5 priv des

2. Enable SNMP SET to allow SNMP SET operations using SNMPv1/v2:

HPE Insight Remote Support 7.10: Monitored Devices Configuration Guide Page 402 of 436
Chapter 39: Configuring Mellanox InfiniBand Switches

a. Enable SNMP communities:

switch (config) # snmp-server enable communities
b. Configure a read-write community:
switch (config) # snmp-server community my-community-name rw
c. Make sure SNMP communities are enabled. Make sure “(DISABLED)” does not appear beside
“Read-only communities” / “Read-write communities”.
switch (config) # show snmp

Configure SNMPv3

Important: Insight RS only supports SNMPv3 traps, and does not support SNMPv3 Informs.
Insight RS listens on port 1162 for SNMPv3 traps, and your SNMPv3 passwords must be at least 8
characters long. Refer to your device's documentation to determine the versions of SNMP your
device supports.

From a console, complete the following steps:

1. Configure an SNMPv3 user:
a. Configure the user:
switch (config) # snmp-server user admin v3 prompt auth <hash type> priv <privacy
type>
where hash type can equal md5 or sha, and privacy type can equal des or aes-128.
b. Enter authentication password and its confirmation.
c. Enter privacy password and its confirmation.
2. Set up the SNMP Notification traps:
a. Make sure SNMP and SNMP notification are enabled:
switch (config) # snmp-server enable
switch (config) # snmp-server enable notify

b. Configure the SNMP host:

switch (config) # snmp-server host <hosting_device_IP_address> traps version 3
user <username> auth sha <password>
c. Verify the SNMP host configuration.
switch (config) # show snmp host
3. Enable SNMP SET to allow SNMP SET operations using SNMPv3:
a. Create an SNMPv3 user:
switch (config) # snmp-server user <user> v3 auth sha <password1> priv aes-128
<password2>
b. Make sure the username is enabled for SET access and has admin capability level:
switch (config) # show snmp user

HPE Insight Remote Support 7.10: Monitored Devices Configuration Guide Page 403 of 436
Chapter 39: Configuring Mellanox InfiniBand Switches

Configure firewall and port settings

Table 39.2 Mellanox InfiniBand Switches Connectivity - Firewall/Port Requirements
Protocol Ports Source Destination Function Optional

ICMP N/A Hosting Monitored Provides system reachability (ping) check during Required
Device Systems system discovery and before other operations.

UDP 161 Hosting Monitored SNMP. This is the standard port used by SNMP agents Required
Device Systems on monitored systems. The Hosting Device sends
requests to devices on this port.

UDP 162 Monitored Hosting SNMP Trap. This is the port used by Insight RS to listen Required*
Systems Device to SNMP traps.

UDP 1162 Monitored Hosting SNMPv3 Trap. This is the port used by Insight RS to Required*
Device Device listen to SNMPv3 traps.

* Dependent on the version of SNMP used on the monitored device.

Add protocol credentials and start discovery

To discover your monitored devices, complete the following sections:

Create an SNMP protocol credential in the Insight RS

Console
Create an SNMP protocol credential for the version of SNMP that you configured on your switch:

Create an SNMPv1/v2 protocol credential in the Insight RS Console

If your device's SNMP community string is set to public and your community access mode is read only,
Insight RS automatically associates an SNMPv1 protocol with your device. If you use a different community
string or use a nonstandard port, you must create an SNMPv1 protocol credential in the Insight RS Console.
To configure SNMPv1/v2 in the Insight RS Console, complete the following steps:
1. In a web browser, log on to the Insight RS Console.
2. In the main menu, select Discovery and click the Credentials tab.
3. From the Select and Configure Protocol drop-down list, select Simple Network Management Protocol
Version 1, V2C (SNMPv1, SNMPv2C).
4. Click New. The New Credential dialog box appears.
5. Type the Community String you have configured on your device.
6. Click Add.
Insight RS creates the protocol credential and it appears in the credentials table.

Create an SNMPv3 protocol credential in the Insight RS Console

Create an SNMPv3 protocol credential in the Insight RS Console so Insight RS can communicate with your
device.

HPE Insight Remote Support 7.10: Monitored Devices Configuration Guide Page 404 of 436
Chapter 39: Configuring Mellanox InfiniBand Switches

To configure SNMPv3 in the Insight RS Console, complete the following steps:

1. In a web browser, log on to the Insight RS Console.
2. In the main menu, select Discovery and click the Credentials tab.
3. From the Select and Configure Protocol drop-down list, select Simple Network Management Protocol
Version 3 (SNMPv3).
4. Click New. The New Credential dialog box appears.
5. Either use the default port of 161 or clear the Use default check box and type a new port number.
6. In the SNMP Account Credential fields, add:
a. Type the Username for the user on your device.
b. Select an Account Authentication Protocol: MD5 or SHA
c. Type the Account Authentication Password.
d. Select an Account Privacy Protocol: DES, DES3, AES128, AES192, AES256
e. Type the Account Privacy Passphrase.
f. Type the Context Name, if set.
7. Click Add.
Insight RS creates the protocol credential and it appears in the credentials table.

Discover the device in the Insight RS Console

Important: ICMP is used by Insight RS for discovery. Make sure you have ICMP enabled on your
device.

To discover the device from the Insight RS Console, complete the following steps:
1. In a web browser, log on to the Insight RS Console.
2. In the main menu, select Discovery and click the Sources tab.
3. Expand the IP Addresses section and add the IP address for your device:
a. Click New.
b. Select the Single Address, Address Range, or Address List option.
c. Type the IP address(es) of the devices to be discovered.
d. Click Add.
4. Click Start Discovery.

Verify discovery and device status

To verify the device was discovered correctly, complete the following steps:
1. In a web browser, log on to the Insight RS Console.
2. In the main menu, select Devices and click the Device Summary tab.

3. Make sure the Status column contains a success icon ( ).

HPE Insight Remote Support 7.10: Monitored Devices Configuration Guide Page 405 of 436
Chapter 39: Configuring Mellanox InfiniBand Switches

If there is no success icon, determine which column has the problem and consult the Online Help for
troubleshooting information.

Verify communication between monitored device

and Insight RS
To verify communication between your monitored device and Insight RS, complete the following sections:

Verifying SNMP communication

Verify SNMP is communicating with the Hosting Device by sending a test trap SET request:
1. Send a SET request to the switch IP with the OID 1.3.6.1.4.1.33049.2.1.1.1.6.0.
2. Make sure the test trap is received by the trap receiver (OID: 1.3.6.1.4.1.33049.2.1.2.13).

Verify collections in the Insight RS Console

Collections are not automatically run after discovery. HPE recommends that you manually run a collection
after discovery completes in order to verify connectivity. Run the collection schedule manually on the
Collection Services → Collection Schedules tab. For more information about scheduling collections, see the
Insight RS Help.
Verify that this collection ran successfully on the Collection Services → Basic Collection Results tab in the
Insight RS Console.
1. Log on to the Insight RS Console.
2. In the main menu, select Collection Services and then click the Basic Collection Results tab.
3. Expand the Network Configuration Collection section.
4. Locate the entry for your device and check the Result column. If the collection was successful, a
success icon appears ( ). If it failed, an error icon appears ( ).

HPE Insight Remote Support 7.10: Monitored Devices Configuration Guide Page 406 of 436
 Chapter 40: Configuring Intel Omni-Path
Switches
Intel Omni-Path switches require SNMP for discovery and event monitoring.

Important: Configuration collections are not supported.

Fulfill configuration requirements

To configure your Intel Omni-Path switches to be monitored by Insight RS, complete the following sections:
Table 40.1 Intel Omni-Path switch configuration steps
Task Complete?

Make sure Insight RS supports your Intel Omni-Path switch by checking the HPE Insight Remote
Support Release Notes.

Configure SNMP traps on the switch.

Add SNMP protocol credentials to the Insight RS Console for monitoring.

Discover the Intel Omni-Path switch in the Insight RS Console.

Verify SNMP communication.

Configure communication on switches

To configure your monitored devices, complete the following sections:

Setup SNMP traps

Intel Omni-Path switches can be configured to use either SNMP. Choose one of the methods below:

Configure SNMP
To configure SNMP on your switch, see section 2.4 in the Intel Omni-Path switch documentation:
www.intel.com/content/dam/support/us/en/documents/network/omni-swtch100/sb/Intel_OP_Fabric_
Switches_GUI_UG_H76457_v1_0.pdf.

Add protocol credentials and start discovery

To discover your monitored devices, complete the following sections:

Create an SNMP protocol credential in the Insight RS

Console
Create an SNMP protocol credential for the version of SNMP that you configured on your switch:

HPE Insight Remote Support 7.10: Monitored Devices Configuration Guide Page 407 of 436
Chapter 40: Configuring Intel Omni-Path Switches

Create an SNMP protocol credential in the Insight RS Console

If your device's SNMP community string is set to public and your community access mode is read only,
Insight RS automatically associates an SNMPv1 protocol with your device. If you use a different community
string or use a nonstandard port, you must create an SNMPv1 protocol credential in the Insight RS Console.
To configure SNMP in the Insight RS Console, complete the following steps:
1. In a web browser, log on to the Insight RS Console.
2. In the main menu, select Discovery and click the Credentials tab.
3. From the Select and Configure Protocol drop-down list, select Simple Network Management Protocol
Version 1, V2C (SNMPv1, SNMPv2C).
4. Click New. The New Credential dialog box appears.
5. Type the Community String you have configured on your device.
6. Click Add.
Insight RS creates the protocol credential and it appears in the credentials table.

Discover the device in the Insight RS Console

To discover the device from the Insight RS Console, complete the following steps:
1. In a web browser, log on to the Insight RS Console.
2. In the main menu, select Discovery and click the Sources tab.
3. Expand the IP Addresses section and add the IP address for your device:
a. Click New.
b. Select the Single Address, Address Range, or Address List option.
c. Type the IP address(es) of the devices to be discovered.
d. Click Add.
4. Click Start Discovery.

Verify discovery and device status

To verify the device was discovered correctly, complete the following steps:
1. In a web browser, log on to the Insight RS Console.
2. In the main menu, select Devices and click the Device Summary tab.

3. Make sure the Status column contains a success icon ( ).

If there is no success icon, determine which column has the problem and consult the Online Help for
troubleshooting information.

HPE Insight Remote Support 7.10: Monitored Devices Configuration Guide Page 408 of 436
Chapter 40: Configuring Intel Omni-Path Switches

Verify communication between monitored device

and Insight RS
To verify communication between your monitored device and Insight RS, complete the following sections:

Verify collections in the Insight RS Console

Collections are not automatically run after discovery. HPE recommends that you manually run a collection
after discovery completes in order to verify connectivity. Run the collection schedule manually on the
Collection Services → Collection Schedules tab. For more information about scheduling collections, see the
Insight RS Help.
Verify that this collection ran successfully on the Collection Services → Basic Collection Results tab in the
Insight RS Console.
1. Log on to the Insight RS Console.
2. In the main menu, select Collection Services and then click the Basic Collection Results tab.
3. Expand the Network Configuration Collection section.
4. Locate the entry for your device and check the Result column. If the collection was successful, a
success icon appears ( ). If it failed, an error icon appears ( ).

HPE Insight Remote Support 7.10: Monitored Devices Configuration Guide Page 409 of 436
 Chapter 41: Configuring Networking Routers
HPE Networking Routers require SNMP for event monitoring and Telnet/SSH for collections.

Fulfill configuration requirements

To configure your routers to be monitored by Insight RS, complete the following sections:
Table 41.1 Networking Router configuration steps
Task Complete?

Make sure Insight RS supports your router by checking the HPE Insight Remote Support
Release Notes.

Configure Telnet or SSH on the router.

Configure SNMP traps on the router.

Add SNMP protocol credentials to the Insight RS Console for monitoring.

Add Telnet or SSH protocol credentials to the Insight RS Console for collections.

Discover the router in the Insight RS Console.

Verify SNMP communication.

Install and configure communication software on

routers
To configure your monitored devices, complete the following sections:

Configure Telnet or SSH

To configure trap destinations to point to Insight Remote Support, you need to use Telnet or SSH (or use a
serial console) to access the CLI. You also need to configure Telnet or SSH to enable collection services.
Use the below procedures to configure Telnet or SSH.

Configuring Telnet
From a serial console, complete the following steps:
1. Enter system view, and enable the Telnet service.
<Sysname> system-view [Sysname] telnet server enable
2. Configure an IP address for VLAN interface 1. This address will serve as the destination of the Telnet
connection.
[Sysname] interface vlan-interface 1 [Sysname-Vlan-interface1] ip address <ip-
address> 255.255.255.0 [Sysname-Vlan-interface1] quit
3. Set the authentication mode for the user interfaces to AAA.
[Sysname] user-interface vty 0 4 [Sysname-ui-vty0-4] authentication-mode scheme
4. Enable the user interfaces to support Telnet.

HPE Insight Remote Support 7.10: Monitored Devices Configuration Guide Page 410 of 436
Chapter 41: Configuring Networking Routers

[Sysname-ui-vty0-4] protocol inbound telnet [Sysname-ui-vty0-4] quit

5. Create local user manager, and set the user command privilege level to 3
[Sysname] local-user manager [Sysname-luser-client001] password simple <password>
[Sysname-luser-client001] service-type telnet [Sysname-luser-client001]
authorization-attribute level 3 [Sysname-luser-client001] quit
Configuring SSH version 2
From a serial console, complete the following steps:
1. <Sysname> system-view [Sysname] public-key local create rsa [Sysname] public-key
local create dsa [Sysname] ssh server enable
2. Configure an IP address for VLAN interface 1. This address will serve as the destination of the SSH
connection.
[Sysname] interface vlan-interface 1 [Sysname-Vlan-interface1] ip address <ip-
address> 255.255.255.0 [Sysname-Vlan-interface1] quit
3. Set the authentication mode for the user interfaces to AAA.
[Sysname] user-interface vty 0 4 [Sysname-ui-vty0-4] authentication-mode scheme
4. Enable the user interfaces to support SSH.
[Sysname-ui-vty0-4] protocol inbound ssh [Sysname-ui-vty0-4] quit
5. Create local user manager, and set the user command privilege level to 3.
[Sysname] local-user manager [Sysname-luser-client001] password simple <password>
[Sysname-luser-client001] service-type ssh [Sysname-luser-client001] authorization-
attribute level 3 [Sysname-luser-client001] quit
Verifying Telnet/SSH communication
To verify that Telnet or SSH communication is working properly, complete the following steps:
1. From the Hosting Device, connect to the router using the protocol you want to verify. Wait until the
connection is established.
2. Type the username and password when prompted.
A successful log on confirms that Telnet/SSH is configured properly.

Setup SNMP Traps

Networking Routers can be configured to use either SNMPv1, SNMPv2 or SNMPv3. Choose one of the
methods below:

Configure SNMPv1/v2
From a serial console, or through SSH or Telnet, complete the following steps:
1. <Sysname> system-view [Sysname] snmp-agent sys-info version v1 [Sysname] snmp-agent
community read public
2. Enable SNMP traps, and set the Hosting Device as the trap destination. Use public as the community
name.

HPE Insight Remote Support 7.10: Monitored Devices Configuration Guide Page 411 of 436
Chapter 41: Configuring Networking Routers

[Sysname] snmp-agent trap enable [Sysname] snmp-agent target-host trap address udp-
domain <hosting-device-ip> params securityname public v1
3. Save the configuration
From a serial console, complete the following steps:
a. Save your configuration changes by issuing the save command.
b. When prompted that the "current configuration will be written to the device", type Y.
c. Press Enter to leave the existing filename unchanged.
d. When prompted to overwrite the existing *.cfg file, type Y.
A confirmation message appears when the current configuration saves successfully.

Configure SNMPv3

Important: Insight RS only supports SNMPv3 traps, and does not support SNMPv3 Informs.
Insight RS listens on port 1162 for SNMPv3 traps, and your SNMPv3 passwords must be at least 8
characters long. Refer to your device's documentation to determine the versions of SNMP your
device supports.

From a serial console, or through SSH or Telnet, complete the following steps:
1. Enter system view:
system-view
2. Enable SNMP agent:
snmp-agent
3. Configure an SNMP group and specify its access right:
snmp-agent group v3 <group-name> [authentication | privacy] [read-view <read-view>]
[write-view <write-view>] [notify-view <notify-view>] [acl <acl-number>]
4. Add a user to the SNMP group:
snmp-agent usm-user v3 <user-name> <group-name> [[cipher] authentication-mode {md5 |
sha} <auth-password> [privacy-mode {3des | aes128 | des56} <priv-password>]] [acl
<acl-number>]
The auth-password needs to be at least 6 characters long for Insight RS.
5. Enable SNMP traps, and set the Hosting Device as the trap destination:
[Sysname] snmp-agent trap enable
[Sysname] snmp-agent target-host trap address udp-domain <hosting-device-ip> params
securityname <security-string> v3

6. Saving the current configuration

From a serial console, complete the following steps:
a. Save your configuration changes by issuing the save command.
b. When prompted that the "current configuration will be written to the device", type Y.

HPE Insight Remote Support 7.10: Monitored Devices Configuration Guide Page 412 of 436
Chapter 41: Configuring Networking Routers

c. Press Enter to leave the existing filename unchanged.

d. When prompted to overwrite the existing *.cfg file, type Y.
A confirmation message appears when the current configuration saves successfully.

Configure firewall and port settings

Table 41.2 Networking Routers Connectivity - Firewall/Port Requirements
Protocol Ports Source Destination Function Optional

ICMP N/A Hosting Monitored Provides system reachability (ping) check during Required
Device Systems system discovery and before other operations.

TCP 22 Hosting Monitored SSH: Remote Data Collection. Optional

Device Systems

UDP 161 Hosting Monitored SNMP. This is the standard port used by SNMP agents Required
Device Systems on monitored systems. The Hosting Device sends
requests to devices on this port.

UDP 162 Monitored Hosting SNMP Trap. This is the port used by Insight RS to listen Required*
Systems Device to SNMP traps.

UDP 1162 Monitored Hosting SNMPv3 Trap. This is the port used by Insight RS to Required*
Device Device listen to SNMPv3 traps.

* Dependent on the version of SNMP used on the monitored device.

Add protocol credentials and start discovery

To discover your monitored devices, complete the following sections:

Create an SNMP protocol credential in the Insight RS

Console
Create an SNMP protocol credential for the version of SNMP that you configured on your router:

Create an SNMPv1/v2 protocol credential in the Insight RS Console

If your device's SNMP community string is set to public and your community access mode is read only,
Insight RS automatically associates an SNMPv1 protocol with your device. If you use a different community
string or use a nonstandard port, you must create an SNMPv1 protocol credential in the Insight RS Console.
To configure SNMPv1/v2 in the Insight RS Console, complete the following steps:
1. In a web browser, log on to the Insight RS Console.
2. In the main menu, select Discovery and click the Credentials tab.
3. From the Select and Configure Protocol drop-down list, select Simple Network Management Protocol
Version 1, V2C (SNMPv1, SNMPv2C).
4. Click New. The New Credential dialog box appears.

HPE Insight Remote Support 7.10: Monitored Devices Configuration Guide Page 413 of 436
Chapter 41: Configuring Networking Routers

5. Type the Community String you have configured on your device.

6. Click Add.
Insight RS creates the protocol credential and it appears in the credentials table.

Create an SNMPv3 protocol credential in the Insight RS Console

Create an SNMPv3 protocol credential in the Insight RS Console so Insight RS can communicate with your
device.
To configure SNMPv3 in the Insight RS Console, complete the following steps:
1. In a web browser, log on to the Insight RS Console.
2. In the main menu, select Discovery and click the Credentials tab.
3. From the Select and Configure Protocol drop-down list, select Simple Network Management Protocol
Version 3 (SNMPv3).
4. Click New. The New Credential dialog box appears.
5. Either use the default port of 161 or clear the Use default check box and type a new port number.
6. In the SNMP Account Credential fields, add:
a. Type the Username for the user on your device.
b. Select an Account Authentication Protocol: MD5 or SHA
c. Type the Account Authentication Password.
d. Select an Account Privacy Protocol: DES, DES3, AES128, AES192, AES256
e. Type the Account Privacy Passphrase.
f. Type the Context Name, if set.
7. Click Add.
Insight RS creates the protocol credential and it appears in the credentials table.

Create a Telnet or SSH Protocol in the Insight RS Console

Create a Telnet or SSH protocol credential in the Insight RS Console. You do not need to configure both.

Create a Telnet protocol in the Insight RS Console

To configure Telnet in the Insight RS Console, complete the following steps:
1. In a web browser, log on to the Insight RS Console.
2. In the main menu, select Discovery and click the Credentials tab.
3. From the Select and Configure Protocol drop-down list, select Telnet.
4. Click New. The New Credential dialog box appears.
Insight RS creates the protocol credential and it appears in the credentials table.

Create an SSH protocol credential in the Insight RS Console

To configure SSH in the Insight RS Console, complete the following steps:

HPE Insight Remote Support 7.10: Monitored Devices Configuration Guide Page 414 of 436
Chapter 41: Configuring Networking Routers

1. In a web browser, log on to the Insight RS Console.

2. In the main menu, select Discovery and click the Credentials tab.
3. From the Select and Configure Protocol drop-down list, select Secure Shell (SSH).
4. Click New. The New Credential dialog box appears.
5. Type the Username and Password you have configured on your device.
6. Click Add.
Insight RS creates the protocol credential and it appears in the credentials table.

Discover the device in the Insight RS Console

Important: ICMP is used by Insight RS for discovery. Make sure you have ICMP enabled on your
device.

To discover the device from the Insight RS Console, complete the following steps:
1. In a web browser, log on to the Insight RS Console.
2. In the main menu, select Discovery and click the Sources tab.
3. Expand the IP Addresses section and add the IP address for your device:
a. Click New.
b. Select the Single Address, Address Range, or Address List option.
c. Type the IP address(es) of the devices to be discovered.
d. Click Add.
4. Click Start Discovery.

Verify discovery and device status

To verify the device was discovered correctly, complete the following steps:
1. In a web browser, log on to the Insight RS Console.
2. In the main menu, select Devices and click the Device Summary tab.

3. Make sure the Status column contains a success icon ( ).

If there is no success icon, determine which column has the problem and consult the Online Help for
troubleshooting information.

Verify warranty and contract information

Verify that the warranty and contract information was discovered correctly in the Insight RS Console:
1. In the Insight RS Console, navigate to Devices and click the router Device Name.
2. Expand the Hardware section, and make sure the Acquired Serial Number and Acquired Product
Number are correct. If they are not correct, type the correct values in the Override Serial Number and
Override Product Number fields and click Save Changes.

HPE Insight Remote Support 7.10: Monitored Devices Configuration Guide Page 415 of 436
Chapter 41: Configuring Networking Routers

Verify communication between monitored device

and Insight RS
To verify communication between your monitored device and Insight RS, complete the following sections:

Verifying SNMP communication

There is not a way to manually verify the SNMP configuration without generating an event, which can only be
accomplished by performing an action like pulling a fan tray or disconnecting a power supply.

Note: Do not pull a redundant FRU to test the configuration.

You can verify SNMP communication by reviewing the running configuration from the router command line.
Look for the snmp-agent section in the output and verify that the community string is correct and the trap
destination is the Hosting Device.
To display the running configuration, run the following command:
> display current-configuration
# snmp-agent snmp-agent community read public snmp-agent sys-info version v1 snmp-agent
target-host trap address udp-domain <hosting_device_ip> params securityname public v1 #
If any of the settings are incorrect, use the undo command to remove the setting, for example, undo snmp-
agent community read public. Then return to "Setup SNMP Traps" on page 411 and reconfigure the
setting that was incorrect.

Verify collections in the Insight RS Console

Collections are not automatically run after discovery. HPE recommends that you manually run a collection
after discovery completes in order to verify connectivity. Run the collection schedule manually on the
Collection Services → Collection Schedules tab. For more information about scheduling collections, see the
Insight RS Help.
Verify that this collection ran successfully on the Collection Services → Basic Collection Results tab in the
Insight RS Console.
1. Log on to the Insight RS Console.
2. In the main menu, select Collection Services and then click the Basic Collection Results tab.
3. Expand the Network Configuration Collection section.
4. Locate the entry for your device and check the Result column. If the collection was successful, a
success icon appears ( ). If it failed, an error icon appears ( ).

HPE Insight Remote Support 7.10: Monitored Devices Configuration Guide Page 416 of 436
 Chapter 42: Configuring CS250-HC
StoreVirtual System
The following sections show how to configure Insight RS to monitor the 250-HC StoreVirtual System using
the WBEM and RIBCL protocols.

Create local user ID

For Insight RS to communicate with the ESXi hosts using WBEM, you must create a local user ID on each
ESXi host.
On the vSphere Server, log into each ESXi host and add a local user.

Configure the iLO

For each ESXi host in the 250-HC deployment, complete the following steps:
1. Configure the iLO with Local User account.
2. Under the Administrator → Management → SNMP Settings tab, select Agentless Management.
3. Under the same tab, remove the following settings that are not required for Insight RS:
l remove Read Community
l remove Trap Community
l remove SNMP Alert Destination

Configure discovery
After you install Insight RS and register Insight RS with HPE Support, perform the following steps:
1. On the Hosting Device, open a Command Prompt window and enter following commands.
2. Set discovery to ignore server IPs given to Insight RS by the ILO to avoid issues if the HC environment
has several IPs assigned to a single interface or teamed interface:
rsadmin config -set discovery.ignoreILOServerIps=true
3. Set discovery to use the default behavior when discovering an iLO 4 that presents multiple server IP
addresses:
rsadmin config -delete siteipv4subnet.preference

Add protocol credentials

From the Insight RS Console, create two new Named Credentials:
1. In a web browser, log on to the Insight RS Console.
2. In the main menu, select Company Information and click the Named Credentials tab.
3. Create a WBEM Named Credential:

HPE Insight Remote Support 7.10: Monitored Devices Configuration Guide Page 417 of 436
Chapter 42: Configuring CS250-HC StoreVirtual System

a. Click Add New Credential.

b. Enter a Credential Name and select Web-Based Enterprise Management (WBEM).
c. Enter the Username and Password used when creating local ESXi host ID (see "Create local user
ID" on the previous page).
d. Click Save.
4. Assign each ESXi host in the 250-HC deployment to the WBEM Named Credential:
a. Assign devices in the assigned devices pane. To show unassigned devices, click the Not Assigned
to this Named Credential or All Devices options. To show devices in a specific device group,
select a device group from the Filter by device group drop-down list. To search for a specific
device, type the device name into the Search box. The table displays the devices based on your
filter and search criteria.
b. To add a device, select the check box next to the device in the devices table.
c. Click Save Devices.
5. Create a RIBCL Named Credential:
a. Click Add New Credential.
b. Enter a Credential Name and select Protocol iLO Remote Insight Board Command Language
Protocol (RIBCL).
c. Enter the Username and Password used when creating the local iLO login (see "Configure the iLO"
on the previous page).
d. Click Save.
6. Assign each ESXi host in the 250-HC deployment to the RIBCL Named Credential:
a. Assign devices in the assigned devices pane. To show unassigned devices, click the Not Assigned
to this Named Credential or All Devices options. To show devices in a specific device group,
select a device group from the Filter by device group drop-down list. To search for a specific
device, type the device name into the Search box. The table displays the devices based on your
filter and search criteria.
b. To add a device, select the check box next to the device in the devices table.
c. Click Save Devices.

Add the 250-HC as a Solution

For each 250-HC XL Chassis deployed, complete the following steps:
1. In the main menu, select Solution Manager.
2. Click Add New Solution, and enter the details for the solution:
a. Type a unique name for the solution.
b. Select Solution Type of HPE CS 250-HC StoreVirt System.
c. Enter Solution Serial Number. This is serial number of the 250-HC chassis. (See the 250-HC User
Guide for where to locate the 250-HC chassis serial number.)
d. Optional, enter a Custom Delivery ID if you have one.
e. Click Save.

HPE Insight Remote Support 7.10: Monitored Devices Configuration Guide Page 418 of 436
Chapter 42: Configuring CS250-HC StoreVirtual System

3. Assign the Devices added in "Add protocol credentials" on page 417 to Solution you just created:
a. Assign devices in the assigned devices pane. To show unassigned devices, click the Not Assigned
to this Named Credential or All Devices options. To show devices in a specific device group,
select a device group from the Filter by device group drop-down list. To search for a specific
device, type the device name into the Search box. The table displays the devices based on your
filter and search criteria.
b. To add a device, select the check box next to the device in the devices table.
c. Click Save Devices.

HPE Insight Remote Support 7.10: Monitored Devices Configuration Guide Page 419 of 436
 Chapter 43: Configuring Uninterruptable
Power Supplies
Uninterruptable Power Systems (UPS) come with either a Management Module or a Network Module
installed, depending on the model. Use the appropriate configuration procedure below for your model:
l To configure a UPS that uses a Management Module, see "Configuring UPS Management Modules"
below.
l To configure a UPS that uses a Network Module, see "Configuring UPS Network Modules" on page 423.

Configuring UPS Management Modules

The Uninterruptable Power Systems (UPS) Management Module is an option in several HPE Rack-
Mountable and Tower UPS units, and these units can be monitored by Insight Remote Support through the
module.

Important: Configuration collections are not supported.

Fulfill configuration requirements

To configure your UPS Management Modules to be monitored by Insight RS, complete the following sections:
Table 43.1 UPS Management Module configuration steps
Task Complete?

Make sure Insight RS supports your UPS Management Module by checking the HPE Insight
Remote Support Release Notes.

Configure SNMP on the UPS Management Module and set the Hosting Device as a trap
receiver.

Add the SNMP protocol to the Insight RS Console.

Discover the UPS Management Module in the Insight RS Console.

Send a test event to verify connectivity between your UPS Management Module and Insight RS.

Install and configure communication software on

Management Modules
To configure your monitored devices, complete the following sections:

Configure SNMP
SNMP can be setup in the SNMP Traps screen in the UPS Management Module web interface.
For more details about configuring SNMP, see the HPE UPS Management Module User Guide.
To configure SNMP trap notifications, complete the following steps:

HPE Insight Remote Support 7.10: Monitored Devices Configuration Guide Page 420 of 436
Chapter 43: Configuring Uninterruptable Power Supplies

1. Log on to the UPS Management Module web interface.

2. Click the Setup tab, and in the left menu, click Event Notifications.
3. Add the Insight RS Hosting Device as an SNMP trap recipient on the SNMP Traps tab.
a. Click the SNMP Traps tab. This screen enables administrators to configure SNMP trap event
notifications.
b. To enable SNMP traps for a server, select the Enable option.
c. Enter the IP address of the Hosting Device in the IP Address field.
d. Enter the community string of the Hosting Device in the Community field.
e. Click Save Settings.
4. Configure the management module to send event notifications to the Insight RS Hosting Device on the
Events tab.
a. Click the Events tab. This screen enables administrators to define the event notifications, emails, or
SNMP traps the management module sends for each event.
b. For each event description listed, select the Enabled check box to indicate that email notifications or
SNMP traps are sent for that event. To enable all events, click the Email check box and the SNMP
Trap check box at the top of each column.
c. For each email and SNMP trap enabled, enter the number of minutes that should pass between the
occurrence of an alert condition and the sending of the notification.

Note: If the event clears before the delay time has expired, then the event notification is
not sent.

d. Click Save Settings.

Configure firewall and port settings

Table 43.2 UPS Management Module Connectivity Connectivity - Firewall/Port
Requirements
Protocol Ports Source Destination Function Optional

UDP 161 Hosting Monitored SNMP. This is the standard port used by SNMP agents Required
Device Systems on monitored systems. The Hosting Device sends
requests to devices on this port.

UDP 162 Monitored Hosting SNMP Trap. This is the port used by Insight RS to listen Required
Systems Device to SNMP traps.

Add protocol credentials and start discovery

To discover your monitored devices, complete the following sections:

Create an SNMPv1 protocol credential in the Insight RS Console

If your device's SNMP community string is set to public and your community access mode is read only,
Insight RS automatically associates an SNMPv1 protocol with your device. If you use a different community
string or use a nonstandard port, you must create an SNMPv1 protocol credential in the Insight RS Console.

HPE Insight Remote Support 7.10: Monitored Devices Configuration Guide Page 421 of 436
Chapter 43: Configuring Uninterruptable Power Supplies

To configure SNMPv1 in the Insight RS Console, complete the following steps:

1. In a web browser, log on to the Insight RS Console.
2. In the main menu, select Discovery and click the Credentials tab.
3. From the Select and Configure Protocol drop-down list, select Simple Network Management Protocol
Version 1, V2C (SNMPv1, SNMPv2C).
4. Click New. The New Credential dialog box appears.
5. Type the Community String you have configured on your device.
6. Click Add.
Insight RS creates the protocol credential and it appears in the credentials table.

Discover the device in the Insight RS Console

To discover the device from the Insight RS Console, complete the following steps:
1. In a web browser, log on to the Insight RS Console.
2. In the main menu, select Discovery and click the Sources tab.
3. Expand the IP Addresses section and add the IP address for your device:
a. Click New.
b. Select the Single Address, Address Range, or Address List option.
c. Type the IP address(es) of the devices to be discovered.
d. Click Add.
4. Click Start Discovery.

Verify discovery and device status

To verify the device was discovered correctly, complete the following steps:
1. In a web browser, log on to the Insight RS Console.
2. In the main menu, select Devices and click the Device Summary tab.

3. Make sure the Status column contains a success icon ( ).

If there is no success icon, determine which column has the problem and consult the Online Help for
troubleshooting information.

Verify communication between monitored device and

Insight RS
To verify communication between your monitored device and Insight RS, complete the following section:

Send a test trap

To send a test trap, complete the following steps:
1. Log on to the UPS Management Module web interface.
2. Click the Setup tab.

HPE Insight Remote Support 7.10: Monitored Devices Configuration Guide Page 422 of 436
Chapter 43: Configuring Uninterruptable Power Supplies

3. In the left menu, click Event Notifications, then the SNMP Traps tab.
4. Click Send Test Trap to send a test SNMP trap.
5. Verify that Insight Remote Support received the test trap.

Configuring UPS Network Modules

The Uninterruptable Power Systems (UPS) Network Module is an option in several HPE Rack-Mountable and
Tower UPS units, and these units can be monitored by Insight Remote Support through the module.

Important: Configuration collections are not supported.

Fulfill configuration requirements

To configure your UPS Network Modules to be monitored by Insight RS, complete the following sections:
Table 43.3 UPS Network Module configuration steps
Task Complete?

Make sure Insight RS supports your UPS Network Module by checking the HPE Insight Remote
Support Release Notes.

Configure SNMP on the UPS Network Module and set the Hosting Device as a trap receiver.

Add the SNMP protocol to the Insight RS Console.

Discover the UPS Network Module in the Insight RS Console.

Send a test event to verify connectivity between your UPS Network Module and Insight RS.

Install and configure communication software on Network

Modules
To configure your monitored devices, complete the following sections:

Configure SNMP
SNMP can be setup in the SNMP Settings screen in the UPS Network Module web interface. The SNMP
Settings screen allows an administrator to configure SNMP settings for computers that use the HPE Power
MIB to request information from the UPS Network Module.
For more details about configuring SNMP, see the HPE UPS Network Module User Guide.
To configure SNMP, complete the following steps:
1. Log on to the UPS Network Module web interface.
2. In the left menu, click SNMP.

HPE Insight Remote Support 7.10: Monitored Devices Configuration Guide Page 423 of 436
Chapter 43: Configuring Uninterruptable Power Supplies

3. Select the SNMP version from the SNMP Version drop-down list.
4. Fill in the appropriate fields.
5. Click Save.
6. Set the Hosting Device as a trap receiver UPS Network Module web interface. The Trap Receivers
Settings screen allows an administrator to configure management applications to receive SNMP traps
from the UPS Network Module. SNMP management applications, such as Insight Remote Support, can
receive notifications from the UPS Network Module.
To configure the Hosting Device as an SNMP trap recipient, complete the following steps:
a. In the left menu, click Notified Applications, then click Add Trap Receiver. Configure up to three
applications to receive SNMP traps from the UPS Network Module.

b. Type the name of the application, such as Insight RS, in the Application Name field. HPE
recommends adding “SNMP” or “Trap” to the name to for easy monitoring.

HPE Insight Remote Support 7.10: Monitored Devices Configuration Guide Page 424 of 436
Chapter 43: Configuring Uninterruptable Power Supplies

c. Type the host name or the IP address of the management server on which the application is running
in the Hostname or IP address field.
d. Select the SNMP version from the Protocol drop-down menu.
e. If you selected SNMPv1, type the community string in the Trap Community field.
f. Select the check box for the appropriate MIB:
o HPE MIB (cpqpower.mib)—The HPE Power MIB
o IETF MIB (RFC1628)—A standard UPS MIB
g. Click Save. The application information appears on the Notified Applications screen.

Add protocol credentials and start discovery

To discover your monitored devices, complete the following sections:

Create an SNMPv1 protocol credential in the Insight RS Console

If your device's SNMP community string is set to public and your community access mode is read only,
Insight RS automatically associates an SNMPv1 protocol with your device. If you use a different community
string or use a nonstandard port, you must create an SNMPv1 protocol credential in the Insight RS Console.
To configure SNMPv1 in the Insight RS Console, complete the following steps:
1. In a web browser, log on to the Insight RS Console.
2. In the main menu, select Discovery and click the Credentials tab.
3. From the Select and Configure Protocol drop-down list, select Simple Network Management Protocol
Version 1, V2C (SNMPv1, SNMPv2C).
4. Click New. The New Credential dialog box appears.
5. Type the Community String you have configured on your device.
6. Click Add.
Insight RS creates the protocol credential and it appears in the credentials table.

Discover the device in the Insight RS Console

To discover the device from the Insight RS Console, complete the following steps:
1. In a web browser, log on to the Insight RS Console.
2. In the main menu, select Discovery and click the Sources tab.
3. Expand the IP Addresses section and add the IP address for your device:
a. Click New.
b. Select the Single Address, Address Range, or Address List option.
c. Type the IP address(es) of the devices to be discovered.
d. Click Add.
4. Click Start Discovery.

HPE Insight Remote Support 7.10: Monitored Devices Configuration Guide Page 425 of 436
Chapter 43: Configuring Uninterruptable Power Supplies

Verify discovery and device status

To verify the device was discovered correctly, complete the following steps:
1. In a web browser, log on to the Insight RS Console.
2. In the main menu, select Devices and click the Device Summary tab.

3. Make sure the Status column contains a success icon ( ).

If there is no success icon, determine which column has the problem and consult the Online Help for
troubleshooting information.

Verify communication between monitored device and

Insight RS
To verify communication between your monitored device and Insight RS, complete the following section:

Send a test trap

To send a test trap, complete the following steps:
1. Log on to the UPS Network Module web interface.
2. In the left menu, click Notified Applications, then click Add Trap Receiver. Up to three applications
can be configured to receive SNMP traps from the UPS Network Module.

3. Click Utility Failure Test. The UPS Network Module sends a Utility failure trap, and then sends a Utility
restored trap 30 seconds later.
4. Verify that Insight Remote Support received the test trap.

HPE Insight Remote Support 7.10: Monitored Devices Configuration Guide Page 426 of 436
 Chapter 44: Configuring VMware vCenter
servers
Insight RS can collect virtual machine configuration information for your IT environment from your vCenter
installation. Insight RS automatically discovers any VMware vCenter installations when the ProLiant
Windows server it is installed on is discovered as long as the proper security credentials are configured.
Insight RS supports collections for vCenter virtual machine guests, but does not support monitoring of the
virtual machine guests.

Note: vCenter installations on a virtual machine are not supported.

Communication with a vCenter installation requires the configuration of security credentials within the Insight
RS Console. Once discovered, information about the virtual machines on any server in your environment can
be collected and sent automatically to HPE on a scheduled basis. The vCenter cluster uses the same
warranty and contract information as the ProLiant server it's installed on. When the ESX and ESXi servers are
discovered, Insight RS does not have the ability to tell which vCenter cluster manages them.
The vCenter collection gathers information about the VM Guests and how they are configured on the VMware
vCenter cluster. There must be a Proactive Care contract on at least one of the ESX or ESXi devices that
make up the cluster. With vCenter there isn't a single device, but a cluster of servers hosting the virtual
environment. If at least one of the underlying servers hosting the vCenter managed virtual system is covered
by Proactive Care, then the entire virtual system is covered by Proactive Care.
The vCenter cluster appears in the Insight RS Console with a name of the form: VC@<hostname>.

Note: Although vCenter installations are visible in the Insight RS Console, they are not monitored
for events.

Insight RS does not differentiate between multiple DataCenter objects or between multiple cluster objects
being managed by a given vCenter instance. Insight RS 7.10 does not have hierarchical capability and
therefore cannot represent these constructs. All hosts from all clusters are added to Insight RS without
differentiating the various clusters in which they may be configured.
Insight RS can use CIM ticket authentication on ESXi clusters managed by vSphere, which offers the
following advantages:
l It allows Insight RS to communicate with the ESXi hosts when they are in lockdown mode.

Important: Insight RS supports ESXi hosts in lockdown mode when they are managed by
vCenter in a cluster configuration. Standalone ESXi hosts managed by vCenter are not
supported.

l It allows Insight RS to discover ESXi hosts when it discovers the vCenter server without having to enter
WBEM credentials for each ESXi host; the CIM ticket is used for the credentials instead.
To enable CIM ticketing for ESXi devices, whether in lockdown mode or not, you must provide the credentials
for the VMware vCenter cluster to the discovery tasks (see "Create a VMware VirtualCenter Web Service
Interface protocol credential in the Insight RS Console" on the next page.) If any of the ESXi hosts are
ProLiant Gen8/Gen9 devices, then appropriate RIBCL credentials must also be provided prior to discovery.

HPE Insight Remote Support 7.10: Monitored Devices Configuration Guide Page 427 of 436
Chapter 44: Configuring VMware vCenter servers

Important: The CIM ticket capability only applies to ESXi, not to ESX clusters. When Insight RS
discovers the vCenter server, it will also discover ESX hosts, but you must enter the SNMP
credentials in Insight RS before discovery for them to be monitored correctly.

Fulfill configuration requirements

To configure your VMware vCenter servers to be monitored by Insight RS, complete the following sections:
Table 44.1 ProLiant VMware vCenter server configuration steps
Task Complete?

Make sure Insight RS supports your ProLiant VMware ESX server by checking the HPE Insight
Remote Support Release Notes.

Add VMware vCenter Protocol Credentials in the Insight RS Console.

Discover the ProLiant vCenter server in the Insight RS Console.

Verify the status of the ProLiant VMware ESX server in the Insight RS Console.

Add protocol credentials and start discovery

To discover your monitored devices, complete the following sections:

Create a VMware VirtualCenter Web Service Interface

protocol credential in the Insight RS Console
For the vCenter cluster to be discovered, you need to add the administrator credentials you use to log into
vCenter. If these credentials are not added, the vCenter cluster will not be discovered. Adding this credential
enables CIM ticketing for ESXi devices, whether in lockdown mode or not.

Important: If any of the ESXi hosts are Gen8 ProLiant devices, then appropriate RIBCL credentials
must also be provided prior to discovery.

To configure VMware VirtualCenter Web Service Interface in the Insight RS Console, complete the following
steps:
1. Log on to the Insight RS Console.
2. In the main menu, select Discovery and click the Credentials tab.
3. In the Select and Configure Protocol drop-down list, select VMware VirtualCenter Web Service
Interface.
4. Click New. The New Credential dialog box appears.
5. Type the username and password you use to log on to vCenter.
6. Click Add.

HPE Insight Remote Support 7.10: Monitored Devices Configuration Guide Page 428 of 436
Chapter 44: Configuring VMware vCenter servers

Discover the ProLiant vCenter server in the Insight RS

Console
To discover the ProLiant vCenter server from the Insight RS Console, complete the following steps:
1. In a web browser, log on to the Insight RS Console.
2. In the main menu, select Discovery and click the Sources tab.
3. Expand the IP Addresses section and add the IP address for your device:
a. Click New.
b. Select the Single Address, Address Range, or Address List option.
c. Type the IP address(es) of the devices to be discovered. Use the IP address of the ProLiant server
where vCenter is installed, and as long as you have the vCenter credentials configured in the Insight
RS Console, vCenter will be discovered as well.
d. Click Add.
4. Click Start Discovery.

Note: The vCenter discovery causes the ESX and ESXi devices it manages to be discovered
as long as proper credentials are provided. For ESXi, proper credentials could be WBEM or
could be the vCenter CIM ticket. Make sure the ESX and ESXi devices have proper
credentials configured.

Verify the status of ProLiant vCenter server in the Insight

RS Console
To verify the device was discovered correctly, complete the following steps:
1. In a web browser, log on to the Insight RS Console.
2. In the main menu, select Devices and click the Device Summary tab.

3. Make sure the Status column contains a success icon ( ).

If there is no success icon, determine which column has the problem and consult the Online Help for
troubleshooting information.

Verify communication between monitored device

and Insight RS
To verify communication between your monitored device and Insight RS, complete the following section:

Verify collections in the Insight RS Console

Collections are not automatically run after discovery. HPE recommends that you manually run a collection
after discovery completes in order to verify connectivity. Run the collection schedule manually on the
Collection Services → Collection Schedules tab. For more information about scheduling collections, see the

HPE Insight Remote Support 7.10: Monitored Devices Configuration Guide Page 429 of 436
Chapter 44: Configuring VMware vCenter servers

Insight RS Help.
Verify that this collection ran successfully on the Collection Services → Basic Collection Results tab in the
Insight RS Console.
1. Log on to the Insight RS Console.
2. In the main menu, select Collection Services and then click the Basic Collection Results tab.
3. Expand the VMware vCenter Server Collection section.
4. Locate the entry for your device and check the Result column. If the collection was successful, a
success icon appears ( ). If it failed, an error icon appears ( ).

HPE Insight Remote Support 7.10: Monitored Devices Configuration Guide Page 430 of 436
 Glossary Custom Delivery ID
The Custom Delivery ID is a free text field that
can be individually populated for each monitored
device. Unless a specific value is specified within
A the documentation relating to configuring a
particular device, the field should be left blank. In
Agentless Management Service (AMS) some very specific circumstances, this field may
iLO 4 and iLO 5 Agentless Management uses out- also be populated by an HPE Representative to
of-band communication for increased security allow customized handling/routing of reported
and stability. With Agentless Management, incidents. In those instances, the field must be
health monitoring and alerting is built into the populated with a unique value associated with the
system and begins working the moment a power customized handling that is required.
cord is connected to the server. This feature runs Determination of the unique value must be done
on the iLO hardware, independent of the operating by the HPE Representative working with the
system and processor. The separately installed HPE Automation Team TS that sets up the
AMS collects additional operating system data. customizations. Failure to follow this guidance
could result in incorrectly handled incident
reports.
C
CDID D
See Custom Delivery ID.
device groups
Centralized Management Console (CMC) Configurable groups of devices within the Insight
The CMC is used to configure and manage the RS Console that helps users organize the
P4000 Storage Systems. devices in their environment.

CLIQ discovery
Legacy term for the LeftHand OS command line A feature within a management application that
interface. See P4000 CLI. finds and identifies network objects. In HPE
management applications, discovery finds and
cluster identifies all the devices within a specified
A cluster is a grouping of storage nodes that network range.
create the storage pool from which you create
volumes.
E
collection schedules
The frequency in which collections are run. The Enterprise Virtual Array (EVA)
schedule is configurable in the Insight RS An EVA is a high performance, high capacity and
Console. high availability virtual RAID storage solution for
high-end enterprise environments.
collections
See configuration collection. entitlement
The process of authorizing a request for support
based on the contents of warranty or support
configuration collection
HPE Insight Remote Support uses the term contracts held by the customer, normally with
configuration collection in reference to data respect to a specific Object of Service (OOS)
collected from a monitored device. This data is such as a hardware or software component. Your
sent to HPE for proactive analysis. level of entitlement is determined by your HPE

HPE Insight Remote Support 7.10: Monitored Devices Configuration Guide Page 431 of 436
Glossary: event - Insight Remote Support

Support contract. Contact your HPE Account in to all HPE Passport-enabled Web sites.
Team for more details.

event I
A general term for all types of notifications from
one process to another. identification
An aspect of the discovery process that identifies
Event Log Monitoring Collector (ELMC) the management protocol and type of system.
ELMC provides error condition detection of the
event log and communicates these events to iLO
Insight RS. Integrated Lights-Out. Embedded server
management technology that delivers web-based
remote management that is always available.
H
iLO Remote Insight Board Command
hardware event Language (RIBCL)
A specific type of event that suggests that a Communication protocol required for Insight
specific hardware component may be in trouble. Remote Support to communicate with ProLiant
Hardware events may result in a service event. Gen8 and later servers.

Health Check Insight Online

The LeftHand Networks Health Check Utility is HPE Insight Online provides one-stop
used to send monitoring log file information from personalized, secure access to support the
customer sites to LeftHand Networks for devices in your IT environment. It is integrated
troubleshooting and proactive health monitoring. into HPE Support Center for your IT staff who
See Service Console. deploy, manage and support systems, plus HPE
Authorized Channel Partners who support your IT
Hosting Device infrastructure. Insight Online can automatically
The Hosting Device is a supported Windows discover devices remotely monitored by HPE
ProLiant server that hosts the Insight Remote (requires Insight Remote Support 7.0 or later).
Support software. Depending on your support model you or your
HPE Authorized Channel Partner can easily
organize your devices into groups and have the
Hosting Device Setup Wizard
Step-by-step screens that helps users with the flexibility to efficiently monitor, track and service
initial configuration of their Hosting Device. your HPE devices.

HPE Authorized Reseller/Distributor Insight Remote Support

Channel partners who sell hardware and HPE Insight Remote Support provides proactive
services. remote monitoring, diagnostics, and
troubleshooting to help improve the availability of
supported HPE servers and storage systems in
HPE Authorized Service Partner
your data center. HPE Insight Remote Support
Channel partners who deliver services and/or
reduces cost and complexity through support of
installation service on HPE’s behalf.
systems. HPE Insight Remote Support securely
communicates hardware incident information
HPE Passport through your firewall and/or web proxy to the HPE
HPE Passport single sign-in service lets you use Data Center for reactive support. Additionally,
one user ID and password of your choice to sign- based on your support agreement, system

HPE Insight Remote Support 7.10: Monitored Devices Configuration Guide Page 432 of 436
Glossary: Insight RS Console - Secure Sockets Layer (SSL)

information can be collected for proactive remote administration of BladeSystem c-Class

analysis and services enclosures.

Insight RS Console
The Insight Remote Support user interface that is P
installed on the Hosting Device.
P4000 CLI
The P4000 CLI is the command line interface that
M is used to interface with the P4000 Storage
Systems from the Hosting Device. The P4000
management group CLI is installed with Insight Remote Support.
A collection of one or more storage nodes which Note that the P4000 CLI is sometimes referred to
serves as the container within which you cluster as cliq, which is the name of the command used
storage nodes and create volumes for storage. within the P4000 CLI.

Management Information Base (MIB)

The data specification for passing information R
using the SNMP protocol. An HPE MIB is also a
database of managed objects accessed by Remote Support Eligible Systems
network management protocols. Systems that are eligible for Remote Support,
and when enabled will submit events to the HPE
Data Center for incident resolution. Systems
management protocol
must also be entitled to Remote Support,
A set of protocols, such as WBEM, HTTP, or
otherwise submitted events will be closed. You
SNMP, used to establish communication with
can verify that an eligible system is actually
discovered systems.
supported by using the Remote Support
Entitlement Check.
monitored device
Any device monitored by HPE Insight Remote
Remote Support Entitlement Check (RSEC)
Support, such as servers, storage systems, and
The RSEC is a check against the HPE
switches. To monitor a device, some type of
entitlement datastore for the current obligation
management protocol (for example, SNMP or
status of a particular system. The Entitlement
WBEM) must be present on the device.
window displays the results of the Remote
Support Entitlement Check.
Monitored Device Setup Wizard
Step-by-step screens that helps users discover
RIBCL
devices in their environment to be monitored.
See iLO Remote Insight Board Command
Users specify the range of devices to be
Language.
discovered and the corresponding credentials.

O S
Secure Sockets Layer (SSL)
OA
Secure Sockets Layer is the standard security
Onboard Administrator. The Onboard
technology for establishing an encrypted link
Administrator for the BladeSystem enclosures is
between a web server and a browser. This link
the intelligence of the c-Class infrastructure. The
ensures that all data passed between the web
Onboard Administrator provides both local and
server and browsers remain private and integral.

HPE Insight Remote Support 7.10: Monitored Devices Configuration Guide Page 433 of 436
Glossary: Service Console - Transport Layer Security (TLS)

Service Console disk storage. Compared to managing hundreds of

The Service Console is the legacy software that servers, each with their own disks, SANs
enabled remote hardware and software support improve system administration.
for P4000 Storage Systems. This functionality is
now provided by Insight Remote Support. See Storage Management Server (SMS)
Health Check. A system on which HPE Enterprise Virtual Array
(EVA) software is installed, including P6000
service event Command View and HPE Replication Solutions
Insight RS monitors a customer’s hardware Manager, if used. It is a dedicated management
environment for service events that require action server that runs EVA management software
from the Service Provider (HPE Channel Partner exclusively.
and/or HPE services team) or customer. For the
most part, actionable service events require System Fault Management (SFM or
replacing a failed Field Replaceable Unit (FRU) or SysFaultMgmt)
Customer Replaceable Unit (CRU) in the SFM is the HP-UX fault management solution
monitored hardware. Non-actionable events are that implements WBEM standards. SFM
filtered out, and actionable service events are integrates with other manageability applications
forwarded to HPE. Insight RS monitors hardware like HPE SIM, HPE SMH, and other WBEM-
for hard failures from a major component on the based clients.
hardware such as CPU, disk, memory, and
power supply, and these will trigger a service
system health
event communication to HPE. In addition, Insight
Health status is an aggregate status all of the
RS monitors hardware for soft errors, and in some
status sources (which can be SNMP, WBEM,
instances, when the number of soft errors
and HTTP) with the most critical status being
exceeds a specific threshold, an event is sent to
displayed.
HPE. Further details regarding what classifies as
an actionable service event is HPE confidential
information. System Management Homepage (SMH)
System Management Homepage (SMH) is a
web-based interface that consolidates and
Simple Network Management Protocol (SNMP) simplifies single system management for HPE
One of the management protocols supported by
servers on HP-UX, Linux, and Windows
Insight Remote Support. Traditional management
operating systems.
protocol used extensively by networking systems
and most servers. MIB-2 is the standard
information available consistently across all
vendors.
T
Transport Layer Security (TLS)
SNMP trap Transport Layer Security is a protocol that
Asynchronous event generated by an SNMP ensures privacy between communicating
agent that the system uses to communicate a applications and their users on the Internet. When
fault. a server and client communicate, TLS ensures
that no third party may eavesdrop or tamper with
Storage Area Network (SAN) any message. TLS is the successor to the
A SAN is a network of storage devices and the Secure Sockets Layer (SSL).
initiators that store and retrieve information on
those devices, including the communication
infrastructure. In large enterprises, a SAN
connects multiple servers to a centralized pool of

HPE Insight Remote Support 7.10: Monitored Devices Configuration Guide Page 434 of 436
Glossary: virtual node - workflow case

V
virtual node
The P4000 Virtual SAN Appliance uses captive
server disk drives to build a virtual iSCSI SAN
consisting of Virtual Nodes that create the
storage pool from which virtualized volumes are
created. Virtual Nodes can be discovered and
managed in the same manner as physical
Storage Nodes.

volume
A logical entity that is made up of storage on one
or more storage nodes. It can be used as raw data
storage or it can be formatted with a file system
and used by a host or file server.

W
Web-Based Enterprise Management (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.

Windows Management Instrumentation (WMI)

Microsoft's implementation of Web-Based
Enterprise Management (WBEM).

workflow case
The specific HPE obligation to send a
replacement part for a failed customer part.

HPE Insight Remote Support 7.10: Monitored Devices Configuration Guide Page 435 of 436
 Index registering Remote Support 281

P
A
ProLiant Citrix Server 60, 93
Active Health System Report 45, 56 ProLiant Gen10 Server 39
ProLiant Gen8 Server 48
B ProLiant Gen9 Server 48
ProLiant Linux Server 76
BladeSystem c-Class Enclosure
ProLiant VMware ESX 83
configuring 279-280, 284
ProLiant VMware ESXi 89
C ProLiant Windows Server 60

configuring SNMP T
B-Series Switch 362
test event 44, 53
ProLiant Citrix 93
ProLiant Linux 76 U
ProLiant VMware ESX 83
ProLiant Windows 60 User Account Control 62

D W

Data Collection 45, 55 WBEM Test Indication 64, 336

ELMC Installation
EVA 301
ESXi
lockdown mode 427

HP ESXi 89

installing IM Providers or IM Agents 61, 67

installing SNMP 93
installing System Management Homepage 61, 68
ProLiant Citrix 93
ProLiant Linux 76
ProLiant Windows 60

lockdown mode 427

maintenance mode 46, 57

monitored devices prerequisites
communication protocols and software
components 26

Onboard Administrator
configuring SNMP 285

HPE Insight Remote Support 7.10: Monitored Devices Configuration Guide Page 436 of 436