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 8
Integrity Windows 2003 Server Configuration
This chapter applies only to Windows 2003 Integrity managed systems. Event Log Monitoring Collector
(ELMC) is responsible for remote support monitoring on Windows 2003 Integrity managed systems.
SNMP is necessary for Discovery, and WBEM is necessary for Remote Data Collections. Before you can
monitor your Integrity Windows 2003 managed systems you must:
l Verify the managed systems are supported by checking the Insight Remote Support Advanced
Release Notes.
l Verify that ELMC is installed and configured.
l Verify that SNMP and WBEM are installed and configured. To determine which version of SNMP
Agents and WBEM Providers your managed systems require, consult the support matrix at the
following URL: http://h20338.www2.hp.com/integrity/w1/en/os/windows-on-integrity-releases.html.
l Verify connectivity from the managed systems to the CMS.
Fulfilling ELMC Requirements
The managed system 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 managed server
l Required Permissions and Access: To install, upgrade, or uninstall WEBES or the ELMC component,
you must be logged on as the Administrator or as a user with administrator privileges.
Installing the ELMC Software Package on the
Managed System
Copy the appropriate (IA64 or x86/x64) ELMC client from the RSSWM download folder on the CMS into a
temporary directory. Double click the installer file to begin the install process. The kit will install and finish
with no user prompting, for example there is no user configuration input required for this software package.
Verifying SNMP Agent Prerequisites on the
Managed System
For your Windows 2003 Integrity managed system to be discovered by HP SIM, you must have HP
Integrity SNMP Agents for Windows Server 2003 installed and fully configured on your managed systems
as directed in the HP SmartSetup product documentation for the appropriate package.
Note: WBEM Providers can coexist with SNMP Agents on the managed system system as long as
they have the same version number. Mismatched versions of HP Insight Management WBEM
HP Insight Remote Support Advanced (A.05.80)Page 55 of 204