Professional Documents
Culture Documents
Release Notes
HP-UX
November 2002
30-00856-011
Disclaimer
The information contained in this publication is subject to change without notice.
VERITAS Software Corporation makes no warranty of any kind with regard to this
manual, including, but not limited to, the implied warranties of merchantability and
fitness for a particular purpose. VERITAS Software Corporation shall not be liable for
errors contained herein or for incidental or consequential damages in connection with the
furnishing, performance, or use of this manual.
Copyright
Copyright © 2002 VERITAS Software Corporation. All rights reserved. VERITAS,
VERITAS SOFTWARE, the VERITAS logo, and all other VERITAS product names and
slogans are trademarks or registered trademarks of VERITAS Software Corporation in the
USA and/or other countries. Other product names and/or slogans mentioned herein may
be trademarks or registered trademarks are the property of their respective companies.
VERITAS Software Corporation
350 Ellis Street
Mountain View, CA 94043
Phone 650–527–8000
Fax 650-527-2908
www.veritas.com
iii
Getting Product Information Updates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
Known Problems and Workarounds . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
Installation Issues . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
Cautionary Note when using HP-UX Maintenance Mode Boot (MMB) . . . . . . . . . 21
vxassist Issues . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22
VEA Issues . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
VxVM DMP Issues . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
Miscellaneous Issues . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
Using FUJITSU Disks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36
Note Before you install the packages, please review this entire document.
Organization
Note Before you install the packages, please review this entire document.
1
Getting Help
Getting Help
If you have any comments or problems with the VERITAS products, contact the VERITAS
Technical Support:
◆ U.S. and Canadian Customers: 1-800-342-0652
◆ International Customers: +1 (650) 527-8555
◆ E-mail: support@veritas.com
For license information:
◆ Phone: 1-925-931-2464
◆ Email: license@veritas.com
◆ Fax: 1-925-931-2908
For software updates:
◆ Email: swupdate@veritas.com
For late-breaking news about this release, please see the section called “Known Problems
and Workarounds” on page 20.
For additional technical support information, including
- TechNotes
- Product alerts
- Hardware compatibility lists
visit the VERITAS Technical Support Web site at:
http://support.veritas.com
For information about VERITAS products and services:
Phone 1-800-258-UNIX (1-800-258-8649) or 1-650-527-8000
Email vx-sales@veritas.com
For additional information about VERITAS and VERITAS products, visit the Web site at:
http://www.veritas.com
Using VRTSexplorer
The VRTSexplorer program can help VERITAS Technical Support engineers diagnose
the cause of technical problems associated with VERITAS products. You can download
this program from the VERITAS FTP site or install it from the VERITAS Installation CD.
For more information, consult the README file in the support directory on the
VERITAS Installation CD.
1. Use a web browser or the ftp program to download the VRTSexplorer program at
the following URL:
ftp://ftp.veritas.com/pub/support/vxexplore.tar.Z
Save the file to a temporary directory such as /tmp as shown in these instructions. If
you download the file to a different directory, substitute its path name for /tmp
throughout.
2. Log in as root on the affected system, and use the following commands to extract
the contents of the downloaded file to the directory /tmp/VRTSexplorer:
# cd /tmp
# zcat vxexplore.tar.Z | tar xvf -
4. When VRTSexplorer prompts you for a destination directory for the information
that it collects, press Return to accept the default directory /tmp, or enter a path name
of your own choice. VRTSexplorer writes the results of its investigations to a
compressed tar file named VRTSexplorer_casenumber_hostname.tar.Z in the
specified directory.
5. Use the file upload facility of your web browser or the ftp program to transfer the file
output by VRTSexplorer to the VERITAS Customer Support anonymous FTP site:
ftp://ftp.veritas.com/incoming
6. Call VERITAS Customer Support on 1-800-342-0652, inform them that you have run
VRTSexplorer and tell them the name of the file that you transferred to the FTP site.
Alternatively, if you have already been assigned a call ID number by Customer
Support, email support@veritas.com including your case ID number in the
subject line.
Conventions
The following table describes the typographic conventions used in this document.
Note “Dynamic Disk Groups" were formerly known as "Disk Groups." They are still
sometimes referred to as "Disk Groups" in documentation, menu displays, and the
CLI.
VRTSvlic package. Both licensing packages can co-exist on the same system to
support older VERITAS products that do not understand the new licensing utilities.
For more information, see the VERITAS Volume Manager 3.5 Installation Guide.
◆ VxVM tunables
The values of various tunables have been adjusted to match the performance expected
from current systems. For more information about configuring VxVM tunables, see
the “Performance Monitoring and Tuning” chapter in the VERITAS Volume Manager
3.5 Administrator’s Guide.
◆ VERITAS Enterprise Administrator (VEA)
VEA replaces the VERITAS Volume Manager Storage Administrator (VMSA) as the
graphical configuration tool for VxVM.
Note For information about new features in VERITAS Volume Replicator (VVR), please
see the VVR Release Notes.
First make sure you have the UNOF_init_dump patch, then use crashconf as you
would under LVM.
For example;
# crashconf /dev/vx/dsk/rootdg/your_dump_volume
Changing the Boot Disk to be the New Volume Manager Root Disk
Unless you have installed the required license, you may not be able to use certain features
of VERITAS VxVM 3.5. For example, you require a VERITAS VxVM 3.5 license to be able
to create mirrored volumes other than the root disk.
You also require a VERITAS VxVM 3.5 license to make effective use of an Add-on licenses
to VxVM. For example, FastResync (a FlashSnap license feature) reduces the time taken to
resynchronize volume snapshots (a VERITAS VxVM 3.5 license feature).
features are known as base CVM. These basic clustering features can be used
without the purchase of VERITAS Cluster Volume Manager 3.5 for HP-UX
(B9117AA).
Number of - 32 32 - Supported
mirrors
supported
Note In an active/passive peripheral, LUNs only accept I/O on one path at any time. In
an active/active peripheral, LUNs accept I/O on either path at any time.
◆ The VERITAS Volume Manager 3.5 for HP-UX now supports the HP Process Resource
Manager (PRM) product. An HP OS patch is required to be able to gather statistics on
disks managed by VxVM. The patch number was not known at the time this
document was written. See Patches and Fixes in This Version for instructions on
finding the latest patches.
◆ A disk monitor integrated with the EMS framework is not yet available for disks
being managed by VERITAS Volume Manager 3.5 for HP-UX.
◆ You must use LVM to manage your cluster lock disk; you cannot use VERITAS
Volume Manager for HP-UX or VERITAS Cluster Volume Manager 3.5 for HP-UX to
manage a cluster lock disk with this release.
◆ The maximum number of nodes in a ServiceGuard cluster is 4 in this release of
VERITAS Cluster Volume Manager 3.5 for HP-UX.
HP is continually adding support for additional hardware and software. Contact your HP
Service Representative for information about additional support or refer to the latest
edition of these Release Notes on http://docs.hp.com. Refer to Hardware Requirements
later in this document for the current list of platforms and peripherals that are supported
with VERITAS Volume Manager 3.5 for HP-UX.
Documentation
The following documents describe the VERITAS Volume Manager for HP-UX. They are
available with the VRTSvmdoc package which is installed by default with the HP AR0902
CD in the Base-VXVM bundle, or can be installed from the VERITAS CD.
◆ VERITAS Volume Manager 3.5 Administrator’s Guide
◆ VERITAS Volume Manager 3.5 Troubleshooting Guide
◆ VERITAS Volume Manager 3.5 User’s Guide—VEA
◆ VERITAS Volume Manager 3.5 Migration Guide
◆ VERITAS Volume Manager 3.5 Installation Guide
◆ VERITAS Volume Manager 3.5 Hardware Notes
Manual pages are also available on your system via the man(1) command when you install
the software.
The following documents describe MC/ServiceGuard and ServiceGuard OPS Edition.
They are available in hardcopy or on the web at http://docs.hp.com/hpux/ha.
◆ Managing MC/ServiceGuard
◆ Configuring OPS Clusters with ServiceGuard OPS Edition
◆ MC/ServiceGuard Release Notes for Versions A.11.13 and A.11.14
◆ ServiceGuard OPS Edition Version A.11.13 Release Notes
Software Requirements
◆ HP-UX 11i 32-bit OS
◆ HP-UX 11i 64-bit OS
Note The VERITAS File System Manager (VxFS), which can be used with VxVM,
operates and is supported only on the HP-UX 11i 64-bit OS. (The HP VxFS 3.3
product is supported on both 32-bit and 64-bit OS.)
Other Requirements
During vxinstall, it is advisable to have at least two disks (preferably on separate
controllers) in the default VxVM disk group, rootdg. Having at least two disks
guarantees that multiple copies of the VxVM configuration database exist. This database
is required not only to start VxVM, but is also required when making VxVM configuration
changes (for example, creating volumes).
Note Despite its name, rootdg does not necessarily include your root disk.
Note You must register with the IT Resource Center to search the patch database
HP may release patches that supersede those in the above list. To verify that you have the
latest HP-UX patches, you should refer to the patchlist at the VERITAS support website:
http://seer.support.veritas.com/docs/250499.htm
Alternatively, you can use Hewlett-Packard's Patch Database, offered under the
Maintenance and Support section of the HP Services & Support - IT Resource Center. HP's
Patch Database provides fast, accurate searches for the latest recommended and
superseded patches available for the VERITAS File System or VERITAS Volume Manager.
3. Select Volume Manager for UNIX from the Search Product pull-down menu and
enter the search phrase “late breaking information”.
This will show you any information that has been amended or added to the VxVM 3.5
product documentation.
Installation Issues
Note This is fixed in AR0902. The problem does not arise if you install AR0902 on
different disk on a machine that already has a vxvm root disk.
Note The TUTIL0 and PUTIL0 fields have been removed in the above vxprint output
for readability.
Once the system has been repaired and is up in normal mode, the root volume can be
remirrord using the command:
vxassist -g rootdg mirror rootvol dm:rootdisk02
vxassist Issues
a. Use the following commands to discover the original volume name of each
snapshot plex:
# volrid=‘vxprint -g diskgroup -p -F “%snap_rid” plexname‘
# vxprint -g diskgroup -n -v -e v_rid=$volrid
b. Using the information discovered in step a, identify the volumes to which the
snapshot plexes originally belonged, and reattach them to those original volume
as in the following command:
# vxplex att original_volume plex1 [plex2 ...]
VEA Issues
The following issues have been identified as VEA problems, and will be fixed in either
patches or a future release of VxVM.
Connecting to X Windows
The following X Window System error may occur when starting VEA:
Import Lock
When a host in a non-clustered environment imports a disk group, an import lock is
written on all disks in that disk group. The import lock is cleared when the host deports
the disk group. The presence of the import lock prevents other hosts from importing the
disk group until the importing host has deported the disk group.
Specifically, when a host imports a disk group, the import normally fails if any disks
within the disk group appear to be locked by another host. This allows automatic
re-importing of disk groups after a reboot (autoimporting) and prevents imports by another
host, even while the first host is shut down. If the importing host is shut down without
deporting the disk group, the disk group can only be imported by another host by
clearing the host ID lock first (discussed later).
The import lock contains a host ID (in VxVM, this is the host name) reference to identify
the importing host and enforce the lock. Problems can therefore arise if two hosts have the
same host ID.
Note Since VxVM uses the host name as the host ID (by default), it is advisable to change
the host name of one machine if another machine shares its host name. To change
the host name, use the vxdctl hostid new_hostname command.
Failover
The import locking scheme works well in an environment where disk groups are not
normally shifted from one system to another. However, consider a setup where two hosts,
Node A and Node B, can access the drives of a disk group. The disk group is first
imported by Node A, but the administrator wants to access the disk group from Node B if
Node A crashes. This kind of scenario (failover) can be used to provide manual high
availability to data, where the failure of one node does not prevent access to data. Failover
can be combined with a “high availability” monitor to provide automatic high availability
to data: when Node B detects that Node A has crashed or shut down, Node B imports
(fails over) the disk group to provide access to the volumes.
VxVM can support failover, but it relies on the administrator or on an external
high-availability monitor to ensure that the first system is shut down or unavailable
before the disk group is imported to another system. For details on how to clear locks and
force an import, see the vxdg(1M) manual page and the section on moving disk groups
between systems in the VERITAS Volume Manager Administrator’s Guide.
See the VERITAS Volume Manager Troubleshooting Guide for more information on VxVM
error messages.
If you use the VERITAS VCS product, all disk group failover issues can be managed
correctly. VCS includes a high availability monitor and includes failover scripts for VxVM,
VxFS, and for several popular databases.
The -t option to vxdg prevents automatic re-imports on reboot, and is necessary when
used with a host monitor (such as VCS) that controls imports itself, rather than relying on
automatic imports by VxVM.
Mirroring Disks
◆ Problem: The Actions > Disk Mirror menu is incorrectly disabled if you do not have a
full VxVM license.
◆ Workaround: Use the vxmirror command line to mirror the disk.
Note After using the command line to split the disk group, VEA will not allow you to
split/join the same disk group. However, if you right-click on the split disk group,
the source and target disk groups are displayed, allowing you to rejoin the split.
Miscellaneous Issues
Note In the case where VxVM and XP512 BCs are being used together; if the BCs are split,
you cannot then import the split BC to the machine on which P-Vol is currently
being used. The reason for this is that the split BC and the P-Vol will have the same
private region, and VxVM allows you to import only one of them; by default, it
chooses P-Vol. If you want, however, you can import the split BC (S-Vol) onto a
secondary host.
Note The vxdctl enable command initiates an entire disk device scan. Therefore the
length of time VxVM takes to scan all of the devices in the environment of that
particular host will increase as the number of devices increases. If you know which
disk’s state has been changed, it is faster to use vxdisk online diskname to update
that disk only.
(For more information, refer to “Issues Regarding Persistent Simple/Nopriv Disks with
Enclosure-Based Naming” in the VERITAS Volume Manager Administrator’s Guide. See also
vxdarestore (1M) manual page.)
1. Find the plexes in SNAPDONE state that reside on the failing disk. For each plex,
perform steps 2 and 3, as follows:
2. Disassociate each plex (plex-name) from the disk group (dg-name), using the
command:
3. Attach the plex to the original volume (vol-name) using the command:
# vxplex -g dg-name att vol-name plex-name
The plexes are now synch'd with the contents of the volume.