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 14: Tru64 UNIX Server Configuration
Verify the binary.errlog CDSL
In version 5.1A or higher, the binary error log /var/adm/binary.errlog should be a context-
dependent symbolic link (CDSL) pointing to a file specific to each cluster node. This makes sure that the
binlogd process on each node stores that node’s events to its own node-specific error log
/var/cluster/members/<memb>/adm/binary.errlog.
If the CDSL is ever deleted, binlogd recreates it as a regular, cluster-common file, which does not work
correctly. To check your file, issue the command:
# ls -l /var/adm/binary.errlog
Correct output looks similar to the following:
>lrwxrwxrwx 1 root adm 43 Jun 11 12:54 /var/adm/binary.errlog -
>../cluster/members/<memb>/adm/binary.errlog
Incorrect output does not show the -> link indicator:
-rw-r----- 1 root adm 560 Jun 11 12:59 /var/adm/binary.errlog
If necessary, correct the file by performing the following steps:
1. Stop the binlogd process on all cluster nodes by issuing the following command on each node:
# /sbin/init.d/binlog stop
2. Saved logs can be analyzed at a later time. If desired, move the original error log to any appropriate
name, for example:
# cd /var/adm
# mv binary.errlog binary.errlog.2002_06_11
3. Issue similar move commands for any node-specific error logs you wish to save, for example:
# mv /var/cluster/members/<memb>/adm/binary.errlog
/var/cluster/members/<memb>/adm/binary.errlog.2002_06_11
# mv /var/cluster/members/<memb>/adm/binlog.saved/binary.errlog.saved
/var/cluster/members/<memb>/adm/binlog.saved/binary.errlog.saved.2002_
06_11
4. Remove existing error logs, ignoring any No such file or directory errors:
# rm /var/adm/binary.errlog
# rm /var/cluster/members/<memb>/adm/binary.errlog
# rm /var/cluster/members/<memb>/adm/binlog.saved/binary.errlog.saved
5. Create the CDSL:
# mkcdsl /var/adm/binary.errlog
6. Restart the binlogd process on all cluster nodes by issuing the following command on each node:
# /sbin/init.d/binlog start
HP Insight Remote Support Advanced (A.05.80)Page 99 of 204