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 13: OpenVMS Server Configuration
l SYSLCK
l SYSPRV
l TMPMBX
When uninstalling WEBES, the user who performs the uninstallation must use the same username
originally used to install WEBES.
The set process command sets privileges for all cluster nodes only when the cluster is served by a single
system disk. However, on a cluster with multiple system disks, you might choose to install WEBES on
nodes served by system disks other than the one serving the node from which you are installing. In that
case, set process does not set privileges on those other nodes (the nodes served by the other system
disks), and WEBES does not install correctly on those other nodes.
To correctly install on clusters with multiple system disks, set up the required privileges as defaults (the
privileges you get when logging in) on all nodes where you wish to install ELMC, instead of using the set
process command.
See "Installing the ELMC OpenVMS Software Package on the Managed System" on page 93, for more
precautions about one system disk versus multiple system disks.
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
Cluster Node Access to ELMC Install Directory
The installation package only can install itself on cluster nodes that have access to the target directory
where you choose to install ELMC. Another way to explain this is that the nodes must mount the disk
containing the target directory. This means that an installation might not always place ELMC on all cluster
nodes, since all nodes might not be able to identify the place where ELMC is being installed.
The following illustrate this issue:
l Cluster: All nodes share the same system disk.
Install Node: Any node.
Install Target: The default location SYS$COMMON:[HP...].
HP Insight Remote Support Advanced (A.05.80)Page 91 of 204