A.05.80 HP Insight Remote Support Advanced Managed Systems Configuration Guide (June 2013)
Table Of Contents
- Managed Systems Configuration Guide
- Contents
- About This Document
- Insight Remote Support Advanced Managed Systems Overview
- ProLiant Windows Server Configuration
- ProLiant Linux Server Configuration
- ProLiant VMware ESX Server Configuration
- ProLiant VMware ESXi Server Configuration
- Proliant Citrix Server Configuration
- ProLiant c-Class BladeSystem Enclosure Configuration
- Integrity Windows 2003 Server Configuration
- Integrity Windows 2008 Server Configuration
- Integrity Linux Server Configuration
- Integrity Superdome 2 Server Configuration
- HP-UX Server Configuration
- Meeting HP-UX Operating System, Software, and Patch Requirements
- More About WBEM and SFM with Insight Remote Support
- Verifying System Fault Management is Operational
- Creating WBEM Users
- Configuring WEBES to Support WBEM Indications
- Firewall and Port Requirements for HP-UX Managed Systems
- Configuring HP-UX Managed Systems for Proactive Collection Services
- OpenVMS Server Configuration
- Tru64 UNIX Server Configuration
- NonStop Server Configuration
- Enterprise Virtual Array Configuration
- Understanding the Different Server Types and Software Applications
- Command View EVA 8.0.1 and Higher Hosted on the CMS
- Important Port Settings Information
- Important Information Regarding New HP SIM Installations
- Correcting an Existing HP SIM Installation
- Change the WMI Mapper Proxy port in the HP SIM User Interface on the CMS
- Restore Defaults to the wbemportlist.xml file
- Installing and Configuring Command View EVA After HP SIM
- Resetting the Port Numbers when Command View EVA was Installed before HP SIM
- Command View EVA Hosted on a Separate SMS
- Requirements and Documentation to Configure Command View EVA on the SMS
- Overview of Command View EVA 7.0.1 through 8.0.1 with SMI-S Requirements
- SMS System and Access Requirements
- WEBES – EVA Communication
- HP SIM – EVA Communication
- Software Required on the SMS
- Fulfilling ELMC Common Requirements for a Windows SMS
- Installing MC3 on the SMS
- Configuring EVA-Specific Information on the CMS
- Requirements to Support EVA4400 and P6000 with Command View EVA on the ABM
- Enabling User-Initiated Service Mode in Command View EVA 9.3
- Performing a Remote Service Test in Command View EVA 9.3
- Troubleshooting EVA Managed Systems
- P4000 Storage Systems Migration Procedure
- Network Storage System Configuration
- Modular Smart Array Configuration
- Tape Library Configuration
- System Requirements
- Managed Systems Configuration
- Nearline (Tape Library) Configuration
- Secure Key Manager Configuration
- StoreOnce D2D (Disk-to-Disk) Backup System Configuration
- Enterprise Systems Library G3 Configuration
- TapeAssure Service Configuration
- Prerequisites
- Command View for Tape Libraries and TapeAssure Service Installation
- Configure the Command View TL 2.8 CIMOM and TapeAssure Provider
- Configure the Command View TL 3.0 CIMOM and TapeAssure Provider
- HP SIM Device Discovery
- WEBES Configuration
- Create a New SMI-S Protocol in WEBES
- Subscribe to the Command View TL and TapeAssure CIMOM
- SAN Switch Configuration
- E-Series Switch Configuration
- A-Series Switch Configuration
- UPS Network Module Configuration
- Modular Cooling System Configuration
- Glossary
- Index

Chapter 1
Insight Remote Support Advanced Managed
Systems Overview
Understanding Managed Systems Prerequisites
To use Insight Remote Support Advanced you need at least two pieces of hardware: a supported
Windows ProLiant server to be used as the Central Management Server (CMS) and at least one managed
system. Before you get started, verify Insight Remote Support Advanced supports your managed
systems. This document provides the necessary information to validate your hardware is properly
configured before you install and configure the Insight Remote Support Advanced software on your CMS.
Identify Communication Protocols for Your Managed
System Types
Managed systems can communicate with the CMS using one or more of the following protocols:
l SNMP
SNMP must be installed on managed systems that require SNMP to communicate.
l WBEM
WBEM must be installed on managed systems that require WBEM to communicate. You must have
the WBEM providers installed and configured and you must identify the credentials for those managed
systems before you complete the CMS configuration.
Important: When monitoring managed systems using WBEM credentials, if you change the
username/password, or if the credentials expire as part of your security policies, you must modify
those corresponding credentials in HP SIM on the CMS to continue monitoring your managed
system(s).
l ELMC
The Event Log Monitoring Collector (ELMC) provides error condition detection of the event log and
communicates these events to WEBES.
If you have not configured SNMP or WBEM for your managed systems, the devices will not communicate
with the CMS and your events and managed system configuration collections will not be sent to HP for
support.
The required communication protocol(s) are determined by the managed system type. Read the
appropriate managed system chapter(s) in this document to understand what configuration is necessary
for your specific managed system. Some managed system 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 HP SIM to
discover managed systems while other protocols may be used to monitor hardware events or retrieve
HP Insight Remote Support Advanced (A.05.80)Page 18 of 204