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
Managed Systems Configuration Guide
Chapter 1: Insight Remote Support Advanced Managed Systems Overview
Hardware
Platform
Required
Protocols and
Components Notes
WBEM (WMI) See "Integrity Windows 2003 Server Configuration" on page
55.
Windows 2008 on
Integrity
WBEM (WMI) Must install the Integrity Support Pack and all providers that
ship with it.
See "Integrity Windows 2008 Server Configuration" on page
59.
Linux on Integrity 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.
See "Integrity Linux Server Configuration" on page 61.
Integrity
Superdome 2
Onboard
Administrator
WBEM and
WS-Man and
HTTPS
Discovery uses WS-Man and collections use HTTPS. The
OA is managed using WS-Man, but the Superdome 2
partitions are managed using WBEM.
See "Integrity Superdome 2 Server Configuration" on page
62.
HP-UX 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.
For Mission Critical support, the RS-ACC must be installed
and certificates exchanged for Advanced, Availability, and
Performance collections. Configuration collections use
HTTPS and are certificate based, using SMH and SIM
credentials.
See "HP-UX Server Configuration" on page 69.
OpenVMS on
Integrity
WBEM and
ELMC
(SNMP optional)
Must install the OpenVMS WBEM provider.
Configuration collections only work when the WBEM
providers are installed and the credentials are properly
configured.
Discovery can use SNMP or WBEM, therefore SNMP is an
optional component.
See "OpenVMS Server Configuration" on page 89.
OpenVMS on
Alpha
SNMP and
ELMC
Configuration collections are not available except when the
OpenVMS Alpha server is part of a SAN collection. (See
"Table 1.2. Required Protocols and Components for SAN
Services Devices" on page 22.)
HP Insight Remote Support Advanced (A.05.80)Page 20 of 204