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 16: Enterprise Virtual Array Configuration
Read community string field.
Figure 15.8. Default SNMP settings area
4. Select the Traps tab.
5. Enter the Community name.
6. Enter the Trap destination. This is the TCP/IP address of the CMS. The localhost or loopback
address must also be included as a destination; if it is not, HP SIM will not retrieve enough
information from the SMS and it will fail the Remote Support Entitlement Check (RSEC).
7. Click OK.
Installing ELMC on the SMS for EVA Remote Support
Clearing the Event Log on the SMS
In the context of EVA Remote Support, this step is optional, but HP recommends that you archive and
clear the application log on the SMS before you install ELMC.
When ELMC is initially installed and started, recently logged events are processed by WEBES, 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 very useful for problem
resolution.
Follow these steps to archive and clean the Windows Application Event Log, before installing ELMC:
1. Open the event viewer:
On Windows Server 2003: Start → Programs → Administrative Tools → Event Viewer
2. Click on Application Log in the left pane of the event viewer window.
Clear all events: Choose Action → Clear all Events. You are given the option to save the existing
events to another file before clearing. Saved logs can be analyzed at a later time. Save the log to a
directory of your choice, unless you know there is no value in keeping the current list of events.
3. Close the event viewer.
HP Insight Remote Support Advanced (A.05.80)Page 117 of 204