OceanStor Dorado 6.

x & OceanStor
6.x Host Connectivity Guide for HP-
UX

Issue 10
Date 2023-08-02

HUAWEI TECHNOLOGIES CO., LTD.

Copyright © Huawei Technologies Co., Ltd. 2023. All rights reserved.
No part of this document may be reproduced or transmitted in any form or by any means without prior
written consent of Huawei Technologies Co., Ltd.

Trademarks and Permissions

and other Huawei trademarks are trademarks of Huawei Technologies Co., Ltd.
All other trademarks and trade names mentioned in this document are the property of their respective
holders.

Notice
The purchased products, services and features are stipulated by the contract made between Huawei and
the customer. All or part of the products, services and features described in this document may not be
within the purchase scope or the usage scope. Unless otherwise specified in the contract, all statements,
information, and recommendations in this document are provided "AS IS" without warranties, guarantees
or representations of any kind, either express or implied.

The information in this document is subject to change without notice. Every effort has been made in the
preparation of this document to ensure accuracy of the contents, but all statements, information, and
recommendations in this document do not constitute a warranty of any kind, express or implied.

Huawei Technologies Co., Ltd.

Address: Huawei Industrial Base
Bantian, Longgang
Shenzhen 518129
People's Republic of China

Website: https://e.huawei.com

Issue 10 (2023-08-02) Copyright © Huawei Technologies Co., Ltd. i

OceanStor Dorado 6.x & OceanStor 6.x Host
Connectivity Guide for HP-UX Contents

Contents

1 About This Document.............................................................................................................1

1.1 Purpose....................................................................................................................................................................................... 1
1.2 Audience..................................................................................................................................................................................... 2
1.3 Related Documents................................................................................................................................................................ 2
1.4 Conventions............................................................................................................................................................................... 2
1.5 Where To Get Help................................................................................................................................................................. 3

2 Introduction.............................................................................................................................. 5
2.1 Basic Concepts.......................................................................................................................................................................... 5
2.1.1 Introduction to HP-UX........................................................................................................................................................5
2.1.2 File Systems in HP-UX........................................................................................................................................................ 5
2.1.3 Directory Structures in HP-UX......................................................................................................................................... 6
2.2 Host-SAN Connectivity.......................................................................................................................................................... 7
2.2.1 FC Connectivity..................................................................................................................................................................... 7
2.2.2 iSCSI Connectivity................................................................................................................................................................ 8
2.2.3 Multipath Connectivity...................................................................................................................................................... 8
2.2.4 SAN Boot.............................................................................................................................................................................. 10
2.3 Interoperability Query......................................................................................................................................................... 11
2.3.1 Querying Host Version Information............................................................................................................................ 11
2.3.1.1 Querying the Current Host Version......................................................................................................................... 11
2.3.1.2 Querying the Version of a Component.................................................................................................................. 11
2.3.2 Querying Interoperability Between HP-UX and Storage Systems.................................................................... 11
2.4 Specifications.......................................................................................................................................................................... 13
2.4.1 File Systems......................................................................................................................................................................... 13
2.4.2 Number of LUNs................................................................................................................................................................ 13
2.4.3 Volume Management Software................................................................................................................................... 14
2.5 Common Management Tools and Commands........................................................................................................... 15
2.5.1 Management Tool............................................................................................................................................................. 15
2.5.2 Management Commands............................................................................................................................................... 15

3 Planning Connectivity.......................................................................................................... 18
3.1 Non-HyperMetro Scenarios............................................................................................................................................... 18
3.1.1 Direct-Attached FC Connections.................................................................................................................................. 19
3.1.2 Fabric-Attached FC Connections...................................................................................................................................20

Issue 10 (2023-08-02) Copyright © Huawei Technologies Co., Ltd. ii

OceanStor Dorado 6.x & OceanStor 6.x Host
Connectivity Guide for HP-UX Contents

3.1.3 Direct-Attached iSCSI Connections.............................................................................................................................. 23

3.1.4 Fabric-Attached iSCSI Connections.............................................................................................................................. 25
3.2 HyperMetro Scenarios......................................................................................................................................................... 26

4 Preparing for Configuration............................................................................................... 28

4.1 Storage System...................................................................................................................................................................... 28
4.2 Host........................................................................................................................................................................................... 28
4.2.1 Identifying HBAs................................................................................................................................................................ 28
4.2.2 Querying HBA Properties................................................................................................................................................ 29

5 Configuring Connectivity.....................................................................................................31
5.1 Establishing Fibre Channel Connections....................................................................................................................... 31
5.1.1 Host Configuration........................................................................................................................................................... 31
5.1.2 Storage System Configuration...................................................................................................................................... 32
5.1.3 Scanning LUNs on a Host............................................................................................................................................... 35
5.2 Scanning LUNs on the Host.............................................................................................................................................. 37

6 Configuring Multipathing................................................................................................... 39
6.1 Non-HyperMetro Scenarios............................................................................................................................................... 39
6.1.1 Storage System Configuration...................................................................................................................................... 39
6.1.2 Host Configuration........................................................................................................................................................... 41
6.2 HyperMetro Scenarios......................................................................................................................................................... 44
6.2.1 Storage System Configuration...................................................................................................................................... 44
6.2.2 Host Configuration........................................................................................................................................................... 47
6.2.3 Verification........................................................................................................................................................................... 48

7 FAQs..........................................................................................................................................53
7.1 Changing LUN Mappings When Third-Party Multipathing Software Is Used on an HP-UX Host............53
7.2 iSCSI Software Installation Failure.................................................................................................................................. 57
7.3 LUNs Cannot Be Discovered After a LUN with the Host LUN ID Being 0 Is Manually Added.................. 60
7.4 Recommended Configurations for 6.x Series Storage Systems for Taking Over Data from Other
Huawei Storage Systems When the Host Uses the OS Native Multipathing Software...................................... 60

8 Acronyms and Abbreviations..............................................................................................63

9 Appendix A Volume Management.................................................................................... 65
9.1 LVM............................................................................................................................................................................................ 65
9.1.1 Overview............................................................................................................................................................................... 65
9.1.2 Installation........................................................................................................................................................................... 67
9.1.3 Common Configuration Commands........................................................................................................................... 67
9.2 VxVM......................................................................................................................................................................................... 81
9.2.1 Overview............................................................................................................................................................................... 81
9.2.2 Installation........................................................................................................................................................................... 81
9.2.3 Common Configuration Commands........................................................................................................................... 82

10 Introduction to High-Availability Technologies...........................................................86

10.1 MC/SG.................................................................................................................................................................................... 86

Issue 10 (2023-08-02) Copyright © Huawei Technologies Co., Ltd. iii

OceanStor Dorado 6.x & OceanStor 6.x Host
Connectivity Guide for HP-UX Contents

10.1.1 Overview............................................................................................................................................................................ 86
10.1.2 Working Principles.......................................................................................................................................................... 87
10.1.2.1 Cluster Manager.......................................................................................................................................................... 87
10.1.2.2 Package Manager........................................................................................................................................................ 87
10.1.2.3 Network Manager....................................................................................................................................................... 87
10.1.3 Installation and Configuration................................................................................................................................... 87
10.1.4 Cluster Maintenance...................................................................................................................................................... 88
10.1.4.1 Common Maintenance Commands.......................................................................................................................88
10.1.4.2 Cluster Log Analysis.................................................................................................................................................... 88
10.2 Veritas VCS............................................................................................................................................................................ 89
10.2.1 Overview............................................................................................................................................................................ 89
10.2.2 Version Compatibility.....................................................................................................................................................89
10.2.3 Installation and Configuration................................................................................................................................... 89

Issue 10 (2023-08-02) Copyright © Huawei Technologies Co., Ltd. iv

OceanStor Dorado 6.x & OceanStor 6.x Host
Connectivity Guide for HP-UX 1 About This Document

1 About This Document

1.1 Purpose
1.2 Audience
1.3 Related Documents
1.4 Conventions
1.5 Where To Get Help

1.1 Purpose
This document details the configuration methods and precautions for connecting
OceanStor Dorado storage systems to Hwelett Packard UniX (HP-UX for short)
hosts.
The following table lists the product models that this document is applicable to.

Product Series Product Model Product Version

OceanStor Dorado OceanStor Dorado 3000 6.0.0

6.0.1
OceanStor Dorado 5000 6.1.0
OceanStor Dorado 6000 6.1.2
6.1.3
OceanStor Dorado 8000
6.1.5
OceanStor Dorado 18000 6.1.6

OceanStor Dorado 2000 6.1.5

6.1.6

OceanStor OceanStor 5310 6.1.3

6.1.5
OceanStor 5510
6.1.6
OceanStor 5610

Issue 10 (2023-08-02) Copyright © Huawei Technologies Co., Ltd. 1

OceanStor Dorado 6.x & OceanStor 6.x Host
Connectivity Guide for HP-UX 1 About This Document

Product Series Product Model Product Version

OceanStor 6810

OceanStor 18510

OceanStor 18810

OceanStor 2200 6.1.6

OceanStor 2600

OceanStor 2220

OceanStor 2620

1.2 Audience
This document is intended for:

● Huawei technical support engineers

● Technical engineers of Huawei's partners
● Personnel who are involved in interconnecting Huawei SAN and HP-UX
servers or who are interested in the interconnection.

Readers of this guide are expected to be familiar with the following topics:

● Huawei storage systems

● HP-UX

1.3 Related Documents

For the hosts, host bus adapters (HBAs), and operating systems that are
compatible with Huawei storage devices, go to support-open.huawei.com.

For the latest Huawei storage product documentation, go to support.huawei.com.

For HP-UX-related documentation or support, go to https://support.hpe.com/

hpesc/public/home.

1.4 Conventions
Symbol Conventions
Symbol Description

Indicates a hazard with a high level of risk which,

if not avoided, will result in death or serious
injury.

Issue 10 (2023-08-02) Copyright © Huawei Technologies Co., Ltd. 2

OceanStor Dorado 6.x & OceanStor 6.x Host
Connectivity Guide for HP-UX 1 About This Document

Symbol Description

Indicates a hazard with a medium level of risk

which, if not avoided, could result in death or
serious injury.

Indicates a hazard with a low level of risk which,

if not avoided, could result in minor or moderate
injury.

Indicates a potentially hazardous situation which,

if not avoided, could result in equipment damage,
data loss, performance deterioration, or
unanticipated results.
NOTICE is used to address practices not related to
personal injury.

Supplements the important information in the

main text.
NOTE is used to address information not related
to personal injury, equipment damage, and
environment deterioration.

1.5 Where To Get Help

Huawei support and product information can be obtained on the Huawei Online
Support site.

Product Information
For documentation, release notes, software updates, and other information about
Huawei products and support, go to the Huawei Online Support site (registration
required) at https://support.huawei.com/enterprise/.

Technical Support
Huawei has a global technical support system, able to offer timely onsite and
remote technical support service.

For any assistance, contact:

● Your local technical support

https://e.huawei.com/en/branch-office-query
● Huawei company headquarters.
Huawei Technologies Co., Ltd.
Address: Huawei Industrial Base Bantian, Longgang Shenzhen 518129
People's Republic of China
Website: https://e.huawei.com/

Issue 10 (2023-08-02) Copyright © Huawei Technologies Co., Ltd. 3

OceanStor Dorado 6.x & OceanStor 6.x Host
Connectivity Guide for HP-UX 1 About This Document

Document Feedback
Huawei welcomes your suggestions for improving our documentation. If you have
comments, send your feedback to [email protected].

Issue 10 (2023-08-02) Copyright © Huawei Technologies Co., Ltd. 4

OceanStor Dorado 6.x & OceanStor 6.x Host
Connectivity Guide for HP-UX 2 Introduction

2 Introduction

2.1 Basic Concepts

2.2 Host-SAN Connectivity
2.3 Interoperability Query
2.4 Specifications
2.5 Common Management Tools and Commands

2.1 Basic Concepts

2.1.1 Introduction to HP-UX

HP-UX is Hewlett Packard Enterprise's proprietary implementation of the UNIX
operating system, based on UNIX System V (initially System III) and first released
in 1984. Recent versions support the HP 9000 series of computer systems, based
on the PA-RISC processor architecture, and HP Integrity systems, based on Intel's
Itanium architecture.

2.1.2 File Systems in HP-UX

HP-UX typically supports four types of file systems: High Performance File System
(HFS), Journaled File System (JFS), Network File System (NFS), and CD-ROM File
System (CDFS). These file systems are described as follows:
● HFS
HFS is created on large-capacity storage devices, typically disk drives. In
versions earlier than HP-UX 10.01, HFS is the only disk file system developed
by HP.
● JFS
JFS, also called Veritas file system (VxFS), is an extended log file system that
provides functions such as fast file system recovery and online backup. The
log file records recent changes made to the file system data structure. If a
disk error occurs, the system can check the log file and perform rollback or
rollforward.

Issue 10 (2023-08-02) Copyright © Huawei Technologies Co., Ltd. 5

OceanStor Dorado 6.x & OceanStor 6.x Host
Connectivity Guide for HP-UX 2 Introduction

● NFS
NFS allows different systems to share files through servers. NFS allows
transparent file access from any location on a network. An NFS server outputs
a directory and allows hosts on a network to access the directory. NFS clients
mount that directory to access the directory on the NFS server. For NFS client
users, that directory is equivalent to a local file system.
● CDFS
CDFS is a file system used on a CD-ROM.
To view the file system type of a volume, use either of the following methods:
● To query the type of mounted file systems, run the following command:
bash-4.0# mount -v
/dev/vg00/lvol3 on / type vxfs ioerror=mwdisable,largefiles,delaylog,nodatainlog,dev=40000003 on
Thu Jul 26 10:33:11 2012
/dev/vg00/lvol1 on /stand type vxfs
ioerror=mwdisable,nolargefiles,log,nodatainlog,tranflush,dev=40000001 on Thu Jul 26 10:33:19 2012
/dev/vg00/lvol8 on /var type vxfs ioerror=mwdisable,largefiles,delaylog,nodatainlog,dev=40000008 on
Thu Jul 26 10:33:45 2012
/dev/vg00/lvol7 on /usr type vxfs ioerror=mwdisable,largefiles,delaylog,nodatainlog,dev=40000007 on
Thu Jul 26 10:33:45 2012
/dev/vg00/lvol4 on /tmp type vxfs ioerror=mwdisable,largefiles,delaylog,nodatainlog,dev=40000004
on Thu Jul 26 10:33:45 2012
/dev/vg00/lvol6 on /opt type vxfs ioerror=mwdisable,largefiles,delaylog,nodatainlog,dev=40000006 on
Thu Jul 26 10:33:45 2012
/dev/vg00/lvol5 on /home type vxfs ioerror=mwdisable,largefiles,delaylog,nodatainlog,dev=40000005
on Thu Jul 26 10:33:45 2012
-hosts on /net type autofs ignore,indirect,nosuid,soft,nobrowse,dev=4000002 on Thu Jul 26 10:39:10
2012
bash-4.0#

According to the command output, all mounted file systems are VxFS.
● To query the file system type of a specific volume, run the following
command:
bash-4.0# fstyp -v /dev/vg00/rlvol3
vxfs
version: 6
f_bsize: 8192
f_frsize: 8192
f_blocks: 131072
f_bfree: 91695
f_bavail: 90979
f_files: 25504
f_ffree: 22912
f_favail: 22912
f_fsid: 1073741827
f_basetype: vxfs
f_namemax: 254
f_magic: a501fcf5
f_featurebits: 0
f_flag: 16
f_fsindex: 9
f_size: 131072

According to the command output, the value of f_basetype is vxfs, indicating that
the file system type of the /dev/vg00/rlvol3 volume is VxFS.

2.1.3 Directory Structures in HP-UX

HP-UX uses the same file and directory structures as other UNIX operating
systems. The structures are called file trees. In the tree structure, directories, which
act as root nodes of a tree, properly organize data and programs into groups. A
file acts as a leaf node of the tree and belongs to a directory.

Issue 10 (2023-08-02) Copyright © Huawei Technologies Co., Ltd. 6

OceanStor Dorado 6.x & OceanStor 6.x Host
Connectivity Guide for HP-UX 2 Introduction

Table 2-1 describes common directories in HP-UX.

Table 2-1 Common directories in HP-UX

Directory Description

/dev Saves device files.

/etc Saves system configuration files

excluding executable files.

/home User directory.

/mnt Local installation directory.

/opt Saves application programs.

/sbin Saves essential commands for system

boot and installation of other file
systems.

/stand Saves the kernel and boot loader.

/tmp Saves operating system's temporary

files.

/usr Saves shared operating system

commands, library files, and
documents.

/var Saves dynamic information such as log

and buffer files.

2.2 Host-SAN Connectivity

2.2.1 FC Connectivity
A Fibre Channel (FC) SAN is a specialized high-speed network that connects host
servers to storage systems. The FC SAN components include HBAs in the host
servers, switches that help route storage traffic, cables, storage processors (SPs),
and storage disk arrays.
To transfer traffic from host servers to shared storage, the FC SAN uses the Fibre
Channel protocol that packages SCSI commands into Fibre Channel frames.
● Ports in FC SAN
Each node in the SAN, such as a host, a storage device, or a fabric component
has one or more ports that connect it to the SAN. Ports are identified in a
number of ways, such as by:
– World Wide Port Name (WWPN)
A globally unique identifier for a port that allows certain applications to
access the port. The FC switches discover the WWPN of a device or host
and assign a port address to the device.

Issue 10 (2023-08-02) Copyright © Huawei Technologies Co., Ltd. 7

OceanStor Dorado 6.x & OceanStor 6.x Host
Connectivity Guide for HP-UX 2 Introduction

– Port_ID (or port address)

Within a SAN, each port has a unique port ID that serves as the FC
address for the port. This unique ID enables routing of data through the
SAN to that port. The FC switches assign the port ID when the device logs
in to the fabric. The port ID is valid only when the device is logged on.
● Zoning
Zoning provides access control in the SAN topology. Zoning defines which
HBAs can connect to which targets. When you configure a SAN by using
zoning, the devices outside a zone are not visible to the devices inside the
zone.
Zoning has the following effects:
– Reduces the number of targets and LUNs presented to a host.
– Controls and isolates paths in a fabric.
– Separates different environments, for example, a test from a production
environment.

2.2.2 iSCSI Connectivity

In computing, Internet Small Computer Systems Interface (iSCSI) is an IP-based
storage networking standard for linking data storage systems.

By carrying SCSI commands over IP networks, iSCSI is used to access remote block
devices in the SAN, providing hosts with the illusion of locally attached devices.

A single discoverable entity on the iSCSI SAN, such as an initiator or a target,

represents an iSCSI node.

Each iSCSI node can be identified in a number of ways, such as by:

● IP address
Each iSCSI node can have an IP address associated with it so that routing and
switching equipment on your network can establish the connection between
the server and storage. This address is just like the IP address that you assign
to your computer to get access to your company's network or the Internet.
● iSCSI name
A worldwide unique name for identifying the node. iSCSI uses the iSCSI
Qualified Name (IQN) and Extended Unique Identifier (EUI).
By default, HP-UX generates unique iSCSI names for your iSCSI initiators, for
example, iqn.1986-03.com.hp:HPV2.72570eb6-90cb-11dd-a3ed-
ed01f70c7e77_P0. Usually, you do not have to change the default value, but if
you do, make sure that the new iSCSI name you enter is worldwide unique.

2.2.3 Multipath Connectivity

HP-UX provides Native Multipathing Plug-In (NMP).

Overview
NMP is native to HP-UX 11i v3 and is available to applications without any special
configuration.

Issue 10 (2023-08-02) Copyright © Huawei Technologies Co., Ltd. 8

OceanStor Dorado 6.x & OceanStor 6.x Host
Connectivity Guide for HP-UX 2 Introduction

NOTE

For more information about NMP, see HP-UX 11i v3 Native Multi-Pathing for Mass
Storage Technical White Paper.

Operating Environment Requirements

NMP is available only in HP-UX 11i v3.

Functions
NMP offers the following functions:
● Optimal distribution of I/O traffic across LUN paths
● Dynamic discovery of LUNs
● Automatic monitoring of LUN paths
● Automatic LUN path failover and recovery
● Intelligent I/O retry algorithms to deal with failed LUN paths
● LUN path authentication to avoid data corruption

Features
Load balancing policies:
NMP supports the following I/O load balancing policies
● Round-robin (round_robin)
This policy distributes the I/O load equally across all active LUN paths
irrespective of the current load on each LUN path. It is suitable when LUN
paths have similar I/O operation turnaround characteristics.
● Least command load (least_cmd_load)
This policy selects the LUN path with the least number of pending I/O
requests for the next I/O operation. It is suitable when LUN paths have
asymmetric performance characteristics.
● Cell aware round robin (cl_round_robin)
This policy is applicable to servers supporting hard partitions, which have high
latencies for non-local memory access operations. The LUN path chosen to
issue an I/O operation is in the same locality in which the I/O is issued. This
policy helps optimize memory access latency.
● Closest path (closest_path)
This policy selects the LUN path based on its affinity with the CPU processing
the I/O operation so as to minimize memory access latency. This policy is
more appropriate for cell-based platforms. The affinity between the LUN path
and CPU is determined based on the relative locations of the CPU processing
the I/O operation and the CPU to which the HBA used by the LUN path is
bound.
● Preferred path (preferred_path), Preferred target port (pref_tport)
These two policies apply to certain types of targets that present an
optimized/un-optimized controller model (different from active-passive). An
optimized/un-optimized controller pair is one in which the optimized
controller is favored for accessing that LUN since it yields better performance.

Issue 10 (2023-08-02) Copyright © Huawei Technologies Co., Ltd. 9

OceanStor Dorado 6.x & OceanStor 6.x Host
Connectivity Guide for HP-UX 2 Introduction

With the preferred path, you specify a LUN path to the optimized controller.
This LUN path is used preferably for I/O transfers to the disk device.
● Weighted round-robin (weighted_rr)
This policy distributes the I/O load across all active LUN paths in a round-
robin manner and according to the weight assigned to each LUN path. A
number of I/O operations corresponding to the weight of the LUN path is
transferred on the same LUN path before another LUN path is selected. LUN
paths with a weight of 0 are excluded from I/O transfer.

LUN failure management

● Managing loss of accessibility to a LUN

When all the LUN paths to a LUN are taken offline, the LUN becomes
inaccessible. The storage system still accepts I/O operations to this LUN
during a transient grace period. This mechanism gives some time for the LUN
to recover and shields applications from SAN transient conditions that may
cause a temporary loss of accessibility to the LUN. If at least one path
becomes active before the end of the grace period, incoming I/O operations
can flow again. After this grace period expires, pending I/O operations and
further incoming I/O operations to this LUN are returned with a failure
indication until a path comes back online.
● Managing authentication failure
Whenever a LUN is opened, the host authenticates the LUN. The goal is to
prevent data written on the physical LUN device from being corrupted by
mistake when LUN devices are swapped. To be specific, the host checks
whether the LUN's WWID is the same as the stored WWID. If the WWIDs are
the same, the LUN passes the authentication and can be used. If the WWIDs
are different, the LUN is changed. In this case, related serial port information
is displayed, all suspended I/Os of the LUN fail, and the LUN becomes
unavailable.

2.2.4 SAN Boot

SAN Boot is a network storage management system that stores data (including
servers' operating systems) totally on storage systems. Specifically, operating
systems are installed on and booted from SAN storage devices. SAN Boot is also
called Remote Boot or boot from SAN.

SAN Boot can help to improve system integration, enable centralized

management, and facilitate recovery.

● Server integration: Blade servers are used to integrate a large number of

servers within a small space. There is no need to configure local disks.
● Centralized management: Boot disks of servers are centrally managed on a
storage device. All advanced management functions of the storage device can
be fully utilized. For example, the snapshot function can be used for backup.
Devices of the same model can be quickly deployed using the snapshot
function. In addition, the remote replication function can be used for disaster
recovery.
● Quick recovery: Once a server that is booted from SAN fails, its boot volume
can be quickly mapped to another server, achieving quick recovery.

Issue 10 (2023-08-02) Copyright © Huawei Technologies Co., Ltd. 10

OceanStor Dorado 6.x & OceanStor 6.x Host
Connectivity Guide for HP-UX 2 Introduction

2.3 Interoperability Query

2.3.1 Querying Host Version Information

Earlier than HP-UX 11.11, HP uses a major version plus a minor version to indicate
an HP-UX version. For example, the major version 9 contains 9.01, 9.03, and 9.05.

Starting from HP-UX 11.11, HP uses 11i plus v and a number, such as 11i v1, 11i
v2, and 11i v3, where the letter i indicates that a version has Internet functions.

NOTE

● HP-UX 11.11 is HP-UX 11i v1.

● HP-UX 11.23 is HP-UX 11i v2.
● HP-UX 11.31 is HP-UX 11i v3.

2.3.1.1 Querying the Current Host Version

To query the current host version, run the following command:
bash-4.1# uname -a
HP-UX renyuan B.11.31 U ia64 0999971421 unlimited-user license
bash-4.1# swlist |grep HPUX11i
HPUX11i-BOE B.11.31.1103 HP-UX Base Operating Environment
bash-4.1# swlist -l bundle|grep -i oe
HPUX11i-BOE B.11.31.1103 HP-UX Base Operating Environment
bash-4.1#

According to the command output, the current host version is 11.31, that is, HP-
UX 11i v3.

2.3.1.2 Querying the Version of a Component

To query the current version of a component, run the following command:
bash-4.1# swlist -l product|grep -i FibreChannel
FC-FCD B.11.31.1103 FibreChannel (FCD) Driver
FC-FCLP B.11.31.1103 PCIe FibreChannel
FC-FCOC B.11.31.1103 PCIe FibreChannel
FC-TACHYON-TL B.11.31.1003 FibreChannel (TD) Driver
bash-4.1#

The command output shows version information about the Fibre Channel HBA
driver.

2.3.2 Querying Interoperability Between HP-UX and Storage

Systems
When connecting a storage system to an HP-UX host, consider the interoperability
of upper-layer applications and components (such as storage systems, HP-UX
systems, HBAs, and switches) in the environment.

You can query the latest compatibility information by performing the following
steps:

Issue 10 (2023-08-02) Copyright © Huawei Technologies Co., Ltd. 11

OceanStor Dorado 6.x & OceanStor 6.x Host
Connectivity Guide for HP-UX 2 Introduction

Step 1 Log in to the website https://info.support.huawei.com/storage/#/home.

Step 2 On the home page, choose Tools > Install and Deploy > Compatibility Query.

Figure 2-1 Huawei Storage Interoperability Navigator

The Huawei Storage Interoperability Navigator is displayed.

Step 3 Select the desired product and to enter the query page.

Issue 10 (2023-08-02) Copyright © Huawei Technologies Co., Ltd. 12

OceanStor Dorado 6.x & OceanStor 6.x Host
Connectivity Guide for HP-UX 2 Introduction

Figure 2-2 Query page

----End

2.4 Specifications

2.4.1 File Systems

Table 2-2 provides restrictions on HFS specifications in HP-UX.

Table 2-2 Restrictions on HFS specifications

File Type File Size File System Size Supported
Operating
System Version

HFS 128 GB 128 GB HP-UX 11i v1, 11i

v2, and 11i v3

2.4.2 Number of LUNs

Table 2-3 lists the numbers of LUNs supported in HP-UX 11i v1, 11i v2, and 11i v3.

Issue 10 (2023-08-02) Copyright © Huawei Technologies Co., Ltd. 13

OceanStor Dorado 6.x & OceanStor 6.x Host
Connectivity Guide for HP-UX 2 Introduction

Table 2-3 Restrictions on the number of LUNs

Operating HP-UX 11i v1 HP-UX 11i v2 HP-UX 11i v3

System
Version

Maximum 8192 16,384 16,384 65,536

number of
LUNs
supported by
each
operating
system

Maximum 1536 1536 1536

number of
LUNs
supported by
each HBA

NOTE

In Table 2-3, there are two values regarding the maximum number of LUNs supported by
HP-UX 11i v1, where 16,384 is the maximum number of LUNs supported by the update
version that was released in December 2003.

2.4.3 Volume Management Software

HP-UX supports Logical Volume Manager (LVM) and Veritas Volume Manager
(VxVM) for volume management. LVM is the default volume management tool
provided by HP-UX. Table 2-4 provides the details about the specification
restrictions on LVM and VxVM.

Table 2-4 Specification restrictions on LVM and VxVM

Volume Volume Type Size Supported

Management Operating
Tool System Version

LVM Physical volume 2 TB HP-UX 11i v1, 11i

v2, and 11i v3

Logical volume 2 TB HP-UX 11i v1 and

11i v2

Logical volume 16 TB HP-UX 11i v3

VxVM Physical volume 2 TB HP-UX 11i v1, 11i

v2, and 11i v3

Logical volume 256 TB HP-UX 11i v1, 11i

v2, and 11i v3

Issue 10 (2023-08-02) Copyright © Huawei Technologies Co., Ltd. 14

OceanStor Dorado 6.x & OceanStor 6.x Host
Connectivity Guide for HP-UX 2 Introduction

2.5 Common Management Tools and Commands

This section describes management tool and commands that may be used for
connecting an HP-UX host to a storage system.

2.5.1 Management Tool

HP-UX provides a powerful management tool named System Administration
Manager (SAM) that offers well-developed online help to help users complete
system management tasks.

NOTE

In HP-UX 11i v3, System Management Homepage (SMH) replaces SAM. Users can run SAM
or SMH commands to enter the user interface.

SAM is easy to use and includes most system management functions.

Figure 2-3 shows the SAM menu tool that covers almost all HP-UX functions.

Figure 2-3 Functions of the SAM tool

NOTE

The preceding figure shows SMH commands. However, you can still run SAM commands to
enter the user interface.

2.5.2 Management Commands

Table 2-5 describes management commands commonly used in the scenario
where HP-UX hosts are connected to storage systems.

Issue 10 (2023-08-02) Copyright © Huawei Technologies Co., Ltd. 15

OceanStor Dorado 6.x & OceanStor 6.x Host
Connectivity Guide for HP-UX 2 Introduction

Table 2-5 Common HP-UX commands

Command Function

bdf Queries the file system size and usage.

diskinfo /dev/rdisk/disk# Displays the capacity of disk#.

fcmsutil /dev/fcd# Queries information about a Fibre

Channel HBA.

fcmsutil /dev/fcd# vpd Queries information about the

firmware of a Fibre Channel HBA.

ifconfig Configures network interface

parameters.

ioscan ● Scans for hardware and lists all

devices and other discovered
devices.
● Displays the hardware address,
type, and description of each
component.

ioscan -funC disk Displays devices of the specified type

(applicable to HP-UX 11i v2 and earlier
versions).

ioscan -funNC disk Displays devices of the specified type

(applicable to HP-UX 11i v3, where
device information after multipathing
virtualization can be displayed).

lanadmin -g 0 Queries details about lan0.

lanscan Queries network configurations.

lvdisplay -v /dev/vgname/lvname Queries details about an LV.

mount Mounts a logical volume.

set_parms Sets system parameters.

shutdown -h now Shuts down a host.

shutdown –ry 0 Restarts a host.

strings /etc/lvmtab Queries information about volume

groups and physical volumes that
compose these volume groups.

swlist iSCSI-00 Checks whether the software iSCSI-00

is installed.

swinstall -s /bash/iSCSI-00_B. Installs software iSCSI-00_B.

11.31.03b_HP-UX_B.11.31_IA_PA.depot 11.31.03b_HP-UX_B.
11.31_IA_PA.depot.

Issue 10 (2023-08-02) Copyright © Huawei Technologies Co., Ltd. 16

OceanStor Dorado 6.x & OceanStor 6.x Host
Connectivity Guide for HP-UX 2 Introduction

Command Function

vgdisplay -v vgname Queries details about a VG.

vgscan Scans for VGs that exist in the system.

NOTE

In the preceding table, # in command lines is a variable and must be set to a number based
on site requirements.

Issue 10 (2023-08-02) Copyright © Huawei Technologies Co., Ltd. 17

OceanStor Dorado 6.x & OceanStor 6.x Host
Connectivity Guide for HP-UX 3 Planning Connectivity

3 Planning Connectivity

Hosts and storage systems can be connected based on different criteria. Table 3-1
describes the typical connection modes.

Table 3-1 Connection modes

Criteria Connection Mode

Interface module Fibre Channel connection/iSCSI connection

type

Whether switches are Direct-attached connection (no switches are used)/

used Fabric-attached connection (switches are used)

Whether multiple Single-path connection/Multi-path connection

paths exist

Whether HyperMetro HyperMetro/Non-HyperMetro

is configured

Fibre Channel connections are the most widely used. To ensure service data
security, both direct-attached connections and fabric-attached connections require
multiple paths.
The following details the connections in HyperMetro and non-HyperMetro
scenarios.
3.1 Non-HyperMetro Scenarios
3.2 HyperMetro Scenarios

3.1 Non-HyperMetro Scenarios

You are advised to use LLDesigner to plan connectivity based on site requirements
and export low level design (LLD) files. This section describes how to plan
connectivity based on LLDesigner.

Issue 10 (2023-08-02) Copyright © Huawei Technologies Co., Ltd. 18

OceanStor Dorado 6.x & OceanStor 6.x Host
Connectivity Guide for HP-UX 3 Planning Connectivity

3.1.1 Direct-Attached FC Connections

This section describes how to directly connect a host to a two-controller storage
system and a four-controller storage system through FC multi-path connections.

Two-Controller Storage System

Figure 3-1 shows how to directly connect a host to a 2 U two-controller storage
system through FC multi-path connections.

Figure 3-1 Direct-attached FC multi-path connections (two-controller storage

system)

NOTE

In this connection diagram, each of the two controllers is connected to a host HBA port
with an optical fiber. The cable connections are detailed in Table 3-2.

Table 3-2 Cable connections (two-controller storage system)

Cable No. Description

1 Connects Port Slot1.P0 on Host001 to Port A.IOM0.P0 on

Storage001.

2 Connects Port Slot1.P1 on Host001 to Port B.IOM0.P0 on

Storage001.

Four-Controller Storage System

Figure 3-2 shows how to directly connect a host to a 4 U four-controller storage
system through FC multi-path connections.

Issue 10 (2023-08-02) Copyright © Huawei Technologies Co., Ltd. 19

OceanStor Dorado 6.x & OceanStor 6.x Host
Connectivity Guide for HP-UX 3 Planning Connectivity

Figure 3-2 Direct-attached FC multi-path connections (four-controller storage

system)

NOTE

In this connection diagram, each front-end interface module is fully interconnected with the
four controllers and therefore can be accessed by all of them.

3.1.2 Fabric-Attached FC Connections

This section describes how to connect a host to a two-controller storage system
and a four-controller storage system through FC multi-path connections using
switches.

Two-Controller Storage System

Figure 3-3 shows how to connect a host to a 2 U two-controller storage system
through FC multi-path connections using switches.

Issue 10 (2023-08-02) Copyright © Huawei Technologies Co., Ltd. 20

OceanStor Dorado 6.x & OceanStor 6.x Host
Connectivity Guide for HP-UX 3 Planning Connectivity

Figure 3-3 Fabric-attached FC multi-path connections (two-controller storage

system)

NOTE

In this connection diagram, two controllers of the storage system and two ports of the host
are connected to switches through optical fibers. On the switches, the ports connecting to a
storage controller and to the host are grouped in a zone, ensuring connectivity between the
host port and the storage system.

Table 3-3 Zone division on switches (two-controller storage system)

Zone Name Zone Member

Zone001 Ports 1 and 3

Zone002 Ports 1 and 4

Zone003 Ports 2 and 5

Zone004 Ports 2 and 6

NOTE

● Port numbers in the Zone Member column in this table refer to numbers in Figure 3-3
rather than switch port IDs.
● Zone division in this table is for reference only. Plan zones based on site requirements.
● If you use LLDesigner to plan connectivity, you can obtain zone division data from the
Zone Planning worksheet in the exported LLD file.

Issue 10 (2023-08-02) Copyright © Huawei Technologies Co., Ltd. 21

OceanStor Dorado 6.x & OceanStor 6.x Host
Connectivity Guide for HP-UX 3 Planning Connectivity

Four-Controller Storage System

Figure 3-4 shows how to connect a host to a 4 U four-controller storage system
through FC multi-path connections using switches.

Figure 3-4 Fabric-attached FC multi-path connections (four-controller storage

system)

NOTE

In this connection diagram, four controllers of the storage system and two ports of the host
are connected to switches through optical fibers. On the switches, the ports connecting to a
storage controller and to the host are grouped in a zone, ensuring connectivity between the
host port and the storage system.

Table 3-4 Zone division on switches (four-controller storage system)

Zone Name Zone Member

Zone001 Ports 1 and 3

Zone002 Ports 1 and 4

Zone003 Ports 2 and 5

Zone004 Ports 2 and 6

Issue 10 (2023-08-02) Copyright © Huawei Technologies Co., Ltd. 22

OceanStor Dorado 6.x & OceanStor 6.x Host
Connectivity Guide for HP-UX 3 Planning Connectivity

NOTE

● Port numbers in the Zone Member column in this table refer to numbers in Figure 3-4
rather than switch port IDs.
● Zone division in this table is for reference only. Plan zones based on site requirements.
● If you use LLDesigner to plan connectivity, you can obtain zone division data from the
Zone Planning worksheet in the exported LLD file.

3.1.3 Direct-Attached iSCSI Connections

This section describes how to directly connect a host to a two-controller storage
system and a four-controller storage system through iSCSI multi-path connections.

Two-Controller Storage System

Figure 3-5 shows how to directly connect a host to a 2 U two-controller storage
system through iSCSI multi-path connections.

Figure 3-5 Direct-attached iSCSI multi-path connections (two-controller storage

system)

NOTE

In this connection diagram, each of the two controllers is connected to a host NIC port with
an Ethernet cable.

Table 3-5 IP address plan (two-controller storage system)

Port Description IP Address Subnet

Mask

Port Slot1.P0 on Connects to Port A.IOM0.P0 192.168.5.5 255.255.0.0

Host001 on Storage001.

Port Slot1.P1 on Connects to Port B.IOM0.P0 192.168.6.5 255.255.0.0

Host001 on Storage001.

Port A.IOM0.P0 on Connects to Port Slot1.P0 on 192.168.5.6 255.255.0.0

Storage001 Host001.

Port B.IOM0.P0 on Connects to Port Slot1.P1 on 192.168.6.6 255.255.0.0

Storage001 Host001.

Issue 10 (2023-08-02) Copyright © Huawei Technologies Co., Ltd. 23

OceanStor Dorado 6.x & OceanStor 6.x Host
Connectivity Guide for HP-UX 3 Planning Connectivity

NOTE

● IP addresses in this table are for reference only. Plan IP addresses based on site
requirements.
● If you use LLDesigner to plan connectivity, you can obtain IP address data from the IP
Address Planning worksheet in the exported LLD file.

Four-Controller Storage System

Figure 3-6 shows how to directly connect a host to a 4 U four-controller storage
system through iSCSI multi-path connections.

Figure 3-6 Direct-attached iSCSI multi-path connections (four-controller storage

system)

NOTE

In this connection diagram, each of the four controllers is connected to a host NIC port with
an Ethernet cable.

Table 3-6 IP address plan (four-controller storage system)

Port Description IP Address Subnet

Mask

Port Slot1.P0 on Connects to Port IOM.H0.P0 192.168.5.5 255.255.0.0

Host001 on Storage001.

Port Slot1.P1 on Connects to Port IOM.L0.P0 192.168.6.5 255.255.0.0

Host001 on Storage001.

Port Slot2.P0 on Connects to Port 192.168.7.5 255.255.0.0

Host001 IOM.H13.P0 on Storage001.

Port Slot2.P1 on Connects to Port IOM.L13.P0 192.168.8.5 255.255.0.0

Host001 on Storage001.

Issue 10 (2023-08-02) Copyright © Huawei Technologies Co., Ltd. 24

OceanStor Dorado 6.x & OceanStor 6.x Host
Connectivity Guide for HP-UX 3 Planning Connectivity

Port Description IP Address Subnet

Mask

Port IOM.H0.P0 on Connects to Port Slot1.P0 on 192.168.5.6 255.255.0.0

Storage001 Host001.

Port IOM.L0.P0 on Connects to Port Slot1.P1 on 192.168.6.6 255.255.0.0

Storage001 Host001.

Port IOM.H13.P0 Connects to Port Slot2.P0 on 192.168.7.6 255.255.0.0

on Storage001 Host001.

Port IOM.L13.P0 Connects to Port Slot2.P1 on 192.168.8.6 255.255.0.0

on Storage001 Host001.

NOTE

● IP addresses in this table are for reference only. Plan IP addresses based on site
requirements.
● If you use LLDesigner to plan connectivity, you can obtain IP address data from the IP
Address Planning worksheet in the exported LLD file.

3.1.4 Fabric-Attached iSCSI Connections

This section describes how to connect a host to a two-controller storage system
and a four-controller storage system through iSCSI multi-path connections using
switches.

Two-Controller Storage System

Figure 3-7 shows how to connect a host to a 2 U two-controller storage system
through iSCSI multi-path connections using switches.

Figure 3-7 Fabric-attached iSCSI multi-path connections (two-controller storage

system)

Issue 10 (2023-08-02) Copyright © Huawei Technologies Co., Ltd. 25

OceanStor Dorado 6.x & OceanStor 6.x Host
Connectivity Guide for HP-UX 3 Planning Connectivity

NOTE

● In this connection diagram, two controllers of the storage system and two NIC ports of
the host are connected to switches through Ethernet cables, ensuring the connectivity
between the host ports and the storage.
● If you use LLDesigner to plan connectivity, you can obtain IP address data from the IP
Address Planning worksheet in the exported LLD file.

Four-Controller Storage System

Figure 3-8 shows how to connect a host to a 4 U four-controller storage system
through iSCSI multi-path connections using switches.

Figure 3-8 Fabric-attached iSCSI multi-path connections (four-controller storage

system)

NOTE

● In this connection diagram, four controllers of the storage system and two NIC ports of
the host are connected to switches through Ethernet cables, ensuring the connectivity
between the host ports and the storage.
● If you use LLDesigner to plan connectivity, you can obtain IP address data from the IP
Address Planning worksheet in the exported LLD file.

3.2 HyperMetro Scenarios

For details on how to plan connectivity in HyperMetro scenarios, see the
HyperMetro Feature Guide for Block.

Issue 10 (2023-08-02) Copyright © Huawei Technologies Co., Ltd. 26

OceanStor Dorado 6.x & OceanStor 6.x Host
Connectivity Guide for HP-UX 3 Planning Connectivity

NOTE

● You can log in to Huawei's technical support website (https://support.huawei.com/

enterprise/) and enter the product model + document name in the search box to search
for, browse, and download documents.
● You can use the same method to search for and download other Huawei documents
referenced in this document.

Issue 10 (2023-08-02) Copyright © Huawei Technologies Co., Ltd. 27

OceanStor Dorado 6.x & OceanStor 6.x Host
Connectivity Guide for HP-UX 4 Preparing for Configuration

4 Preparing for Configuration

This chapter describes the preparations on storage systems and hosts.

NOTE

If switches are used, obtain official product documentation specific to the switch model and
version, and learn about how to configure the switches.

4.1 Storage System

4.2 Host

4.1 Storage System

Create storage pools, LUNs, hosts, and mappings on the storage system according
to your service requirements. For details, see the Basic Storage Service
Configuration Guide for Block.

NOTE

In HyperMetro storage scenarios, the Fast Write function cannot be enabled on both the
storage devices and switches (this function is called Fast Write on Brocade switches and
Write Acceleration on Cisco switches).

4.2 Host
Before connecting a host to a storage system, ensure that the host HBAs have
been identified and are functioning properly. You also need to obtain the world
wide names (WWNs) of HBA ports for subsequent storage system configurations.

4.2.1 Identifying HBAs

After installing an HBA on a host, run the following command to check whether
the host operating system has identified the HBA:
bash-4.1# ioscan -funC fc
Class I H/W Path Driver S/W State H/W Type Description
=================================================================
fc 0 0/0/0/7/0/0/0/5/0/0/0 fclp CLAIMED INTERFACE HP AT094-60001 PCIe Fibre Channel 2-port
8Gb FC/2-port 10GBE Combo Adapter
/dev/fclp0

Issue 10 (2023-08-02) Copyright © Huawei Technologies Co., Ltd. 28

OceanStor Dorado 6.x & OceanStor 6.x Host
Connectivity Guide for HP-UX 4 Preparing for Configuration

fc 1 0/0/0/7/0/0/0/5/0/0/1 fclp CLAIMED INTERFACE HP AT094-60001 PCIe Fibre Channel 2-port

8Gb FC/2-port 10GBE Combo Adapter
/dev/fclp1
bash-4.1#

According to the command output, the host has identified two 8 Gbit/s Fibre
Channel host ports provided by an HP AT094-60001 HBA. The information is
consistent with that about the actually installed HBA, indicating that the host
operating system has identified the installed HBA.
By running the preceding command, you can also obtain the device name
assigned by the host operating system to each port on the HBA, for
example, /dev/fclp0 and /dev/fclp1 in the preceding command output. These
device names will be used in follow-up query commands.

4.2.2 Querying HBA Properties

You can view attributes of an HBA installed on a host only after the host identifies
the HBA.
Typically, you need to pay attention to the WWN, speed, topology, and firmware
of an HBA.

HP-UX 11i v2
You can query the WWN and speed of an HBA by running the fcmsutil command.

HP-UX 11i v3
You can run either the fcmsutil or scsimgr command to query the WWN and
speed of an HBA.
bash-4.1# fcmsutil /dev/fclp0

Vendor ID is = 0x10df
Device ID is = 0xf100
PCI Sub-system Vendor ID is = 0x103c
PCI Sub-system ID is = 0x3392
Chip version = 3
Firmware Version = 2.00A4 SLI-3 (U3D2.00A4)
EFI Version = UU5.03A10
EFI Boot = ENABLED
Driver-Firmware Dump Available = NO
Driver-Firmware Dump Timestamp = N/A
Previous Topology = PTTOPT_FABRIC
Link Speed = 8Gb
Local N_Port_id is = 0x130900
Previous N_Port_id is = None
N_Port Node World Wide Name = 0x2000ac162d1ea160
N_Port Port World Wide Name = 0x1000ac162d1ea160
Switch Port World Wide Name = 0x200900051edda111
Switch Node World Wide Name = 0x100000051edda111
N_Port Symbolic Port Name = louis201_fclp0
N_Port Symbolic Node Name = louis201_HP-UX_B.11.31
Driver state = AWAITING_LINK_UP
Hardware Path is = 0/0/0/7/0/0/0/5/0/0/0
Maximum Frame Size = 2048
TYPE = PFC
NPIV Supported = YES
Driver Version = @(#) FCLP: PCIe Fibre Channel driver (FibrChanl-02), B.11.31.1403, Dec 2 2013, FCLP_IFC
(3,2)

bash-4.1#

Issue 10 (2023-08-02) Copyright © Huawei Technologies Co., Ltd. 29

OceanStor Dorado 6.x & OceanStor 6.x Host
Connectivity Guide for HP-UX 4 Preparing for Configuration

bash-4.1# scsimgr get_info -D /dev/fclp0

STATUS INFORMATION FOR SCSI CONTROLLER : /dev/fclp0

Generic Status Information

SCSI services internal state = IDLE

Target paths probed =0
Target paths registered (active/inactive) = 0
LUN paths registered =0
Trace buffer size =0
Port name = 0x1000ac162d1ea160
Port id = 0x130900
Protocol = fibre_channel
I/F driver version = B.11.31.1403
Firmware version = U3D2.00A4
Operating negotiated/configured speed = 8Gb
Maximum supported speed = 8Gb
Capability = "Boot Dump"
Type = "Physical"
Number of I/O objects =1
I/O objects :
Object index = 0, cpu = 2

bash-4.1#

To query firmware information about an HBA, you can also run the following
command:
bash-4.1# fcmsutil /dev/fclp0 vpd
VITALPRODUCTDATA
--------- ------------- -------

Product Description : "HP AT094A Fibre Channel PCIe 2p 8Gb FC and 2p 1/10GbE Adtr"

Part number : "AT094-60001"

Part Serial number : "5CF211013Y"

Engineering Date Code : "A-5206"

Mfd. Date : "5211"

Misc. Information : "PW=25W, PCIE-X8 GEN2"

ROM Firmware version : "2.00A4 SLI-3 (U3D2.00A4)"

EFI version : "UU5.03A10"

bash-4.1#

Issue 10 (2023-08-02) Copyright © Huawei Technologies Co., Ltd. 30

OceanStor Dorado 6.x & OceanStor 6.x Host
Connectivity Guide for HP-UX 5 Configuring Connectivity

5 Configuring Connectivity

This chapter describes how to configure connectivity between storage systems and
hosts.

NOTE

If switches are used, configure zones (for FC connections) or VLANs (for iSCSI connections)
by referring to the official product documentation specific to the switch model and version.

5.1 Establishing Fibre Channel Connections

5.2 Scanning LUNs on the Host

5.1 Establishing Fibre Channel Connections

This section describes how to establish Fibre Channel connections between
application servers and storage systems.

5.1.1 Host Configuration

NOTE

● Ensure that the domain IDs of the FC switches are not 8.

● If Cisco MDS switches are used, ensure that the persistent FC_ID feature is enabled on
them. For details, see https://www.cisco.com/en/US/docs/storage/san_switches/
mds9000/sw/san-os/quick/guide/qcg_ids.html.

Query the WWN of an HBA. The following provides an example:

bash-4.1# fcmsutil /dev/fcd0

Vendor ID is = 0x1077
Device ID is = 0x2422
PCI Sub-system Vendor ID is = 0x103C
PCI Sub-system ID is = 0x12DE
PCI Mode = PCI-X 133 MHz
ISP Code version = 5.6.5
ISP Chip version = 3
Topology = PTTOPT_FABRIC
Link Speed = 4Gb
Local N_Port_id is = 0x011c00
Previous N_Port_id is = None
N_Port Node World Wide Name = 0x50014380017ab03f
N_Port Port World Wide Name = 0x50014380017ab03e

Issue 10 (2023-08-02) Copyright © Huawei Technologies Co., Ltd. 31

OceanStor Dorado 6.x & OceanStor 6.x Host
Connectivity Guide for HP-UX 5 Configuring Connectivity

Switch Port World Wide Name = 0x201c50eb1ae9a135

Switch Node World Wide Name = 0x100050eb1ae9a135
N_Port Symbolic Port Name = hpux1403_fcd0
N_Port Symbolic Node Name = hpux1403_HP-UX_B.11.31
Driver state = ONLINE
Hardware Path is = 0/2/1/0/4/0
Maximum Frame Size = 2048
Driver-Firmware Dump Available = NO
Driver-Firmware Dump Timestamp = N/A
TYPE = PFC
NPIV Supported = YES
Driver Version = @(#) fcd B.11.31.1403 Dec 4 2013

bash-4.1#

5.1.2 Storage System Configuration

This section details how to add initiators to the hosts on the storage system. For
other storage configurations, see the Basic Storage Service Configuration Guide
corresponding to your storage system.

Step 1 After configuring zones on the switches, log in to DeviceManager of the storage
system. On the Hosts page, select the desired host, click on the right, and
choose Add Initiator.

Figure 5-1 Adding an initiator

NOTE

● The information displayed on the GUI may vary slightly with the product version.

● On DeviceManager of OceanStor Dorado 6.0.1 and later versions, the icon is changed
to More.

Step 2 Check whether the host initiators can be discovered.

Issue 10 (2023-08-02) Copyright © Huawei Technologies Co., Ltd. 32

OceanStor Dorado 6.x & OceanStor 6.x Host
Connectivity Guide for HP-UX 5 Configuring Connectivity

Figure 5-2 Querying initiators

In the preceding figure, the host initiator (WWN: 50014380017ab03e) has been
discovered.

NOTE

If host initiators cannot be discovered on the storage system, add the initiators manually.

Step 3 Select the desired initiators and click .

Figure 5-3 Selecting initiators

Step 4 Click OK.

Issue 10 (2023-08-02) Copyright © Huawei Technologies Co., Ltd. 33

OceanStor Dorado 6.x & OceanStor 6.x Host
Connectivity Guide for HP-UX 5 Configuring Connectivity

Figure 5-4 Confirming initiators

Step 5 Confirm the information and click OK.

Figure 5-5 Confirming the operation

Step 6 Verify that the initiators have been added successfully.

Issue 10 (2023-08-02) Copyright © Huawei Technologies Co., Ltd. 34

OceanStor Dorado 6.x & OceanStor 6.x Host
Connectivity Guide for HP-UX 5 Configuring Connectivity

Figure 5-6 Initiators added successfully

Step 7 Click the host name and check the initiators. Ensure that the Status of the
initiators is Online.

Figure 5-7 Checking the initiator status

If the initiator is in the Offline state, run the ioscan command on the host and
then check the initiator status again. In the preceding figure, the initiator has been
added to the host and its Status is Online. Then the Fibre Channel connections
have been established.

----End

5.1.3 Scanning LUNs on a Host

After configuring an initiator, check its status.

Issue 10 (2023-08-02) Copyright © Huawei Technologies Co., Ltd. 35

OceanStor Dorado 6.x & OceanStor 6.x Host
Connectivity Guide for HP-UX 5 Configuring Connectivity

● If its Status is Online, the FC connection is set up successfully.

● If its Status is Offline, run the ioscan command on the host.

NOTICE

● If a LUN mapped to a host does not have any service, the initiator on the
storage system is in the offline state. To restore the initiator status to Online,
run the ioscan command or read/write the mapped LUN.
● Due to the restrictions of the host, when LUNs are mapped from the storage
system to the host, the LUN whose Host LUN ID is 0 must be mapped.
Otherwise, the host may fail to scan for LUNs. There are no such requirements
on the device LUN ID (Dev LUN ID) allocated when a LUN was created.

To enable the host to discover mapped LUNs, perform the following operations:

Step 1 Run the ioscan command.

bash-4.1# ioscan

Step 2 View the information about disks identified by the operating system.
● For HP-UX 11i v2 or 11i v1, run the ioscan -funC disk command.
● For HP-UX 11i v3, run the ioscan -funNC disk command.

The following is an example:

bash-4.1# ioscan -funNC disk
Class I H/W Path Driver S/W State H/W Type Description
===================================================================
disk 2 64000/0xfa00/0x0 esdisk CLAIMED DEVICE HP DG146BB976
/dev/disk/disk2 /dev/disk/disk2_p1 /dev/disk/disk2_p2 /dev/rdisk/disk2 /dev/rdisk/
disk2_p1 /dev/rdisk/disk2_p2
disk 3 64000/0xfa00/0x1 esdisk CLAIMED DEVICE HP DG146BB976
/dev/disk/disk3 /dev/disk/disk3_p1 /dev/disk/disk3_p2 /dev/disk/disk3_p3 /dev/rdisk/
disk3 /dev/rdisk/disk3_p1 /dev/rdisk/disk3_p2 /dev/rdisk/disk3_p3
disk 5 64000/0xfa00/0x2 esdisk CLAIMED DEVICE TEAC DVD-ROM DW-224EV
/dev/disk/disk5 /dev/rdisk/disk5
disk 12 64000/0xfa00/0xa esdisk CLAIMED DEVICE HUAWEI XSG1
/dev/disk/disk12 /dev/rdisk/disk12
bash-4.1#

In this example, one mapped LUN is found, and its device file is disk12. If the host
operating system does not create a device file for a mapped LUN, you must run
the insf -e command to create one for the LUN.

You can run the following command to view the disk capacity information:
bash-4.1# diskinfo /dev/rdisk/disk12
SCSI describe of /dev/rdisk/disk12:
vendor: HUAWEI
product id: XSG1
type: direct access
size: 104857600 Kbytes
bytes per sector: 512
bash-4.1#

----End

Issue 10 (2023-08-02) Copyright © Huawei Technologies Co., Ltd. 36

OceanStor Dorado 6.x & OceanStor 6.x Host
Connectivity Guide for HP-UX 5 Configuring Connectivity

5.2 Scanning LUNs on the Host

After configuring an initiator, check its status.
● If its Status is Online, the connection is set up successfully.
● If its Status is Offline, run the ioscan command on host.

NOTICE

● If a LUN mapped to a host does not have any service, the initiator on the
storage system is in the offline state. To restore the initiator status to Online,
run the ioscan command or read/write the mapped LUN.
● Due to the restrictions of the host, when LUNs are mapped from the storage
system to the host, the LUN whose Host LUN ID is 0 must be mapped.
Otherwise, the host may fail to scan for LUNs. There are no such requirements
on the device LUN ID (Dev LUN ID) allocated when a LUN was created.
● To change the LUN mappings on the storage system, refer to 7.1 Changing
LUN Mappings When Third-Party Multipathing Software Is Used on an HP-
UX Host.

To enable the host to discover mapped LUNs, perform the following operations:

Step 1 Run the ioscan command.

bash-4.1# ioscan

Step 2 View the information about disks identified by the operating system.
● For HP-UX 11i v2 or 11i v1, run the ioscan -funC disk command.
● For HP-UX 11i v3, run the ioscan -funNC disk command.
The following is an example:
bash-4.1# ioscan -funNC disk
Class I H/W Path Driver S/W State H/W Type Description
===================================================================
disk 2 64000/0xfa00/0x0 esdisk CLAIMED DEVICE HP DG146BB976
/dev/disk/disk2 /dev/disk/disk2_p1 /dev/disk/disk2_p2 /dev/rdisk/disk2 /dev/rdisk/
disk2_p1 /dev/rdisk/disk2_p2
disk 3 64000/0xfa00/0x1 esdisk CLAIMED DEVICE HP DG146BB976
/dev/disk/disk3 /dev/disk/disk3_p1 /dev/disk/disk3_p2 /dev/disk/disk3_p3 /dev/rdisk/
disk3 /dev/rdisk/disk3_p1 /dev/rdisk/disk3_p2 /dev/rdisk/disk3_p3
disk 5 64000/0xfa00/0x2 esdisk CLAIMED DEVICE TEAC DVD-ROM DW-224EV
/dev/disk/disk5 /dev/rdisk/disk5
disk 12 64000/0xfa00/0xa esdisk CLAIMED DEVICE HUAWEI XSG1
/dev/disk/disk12 /dev/rdisk/disk12
bash-4.1#

In this example, one mapped LUN is found, and its device file is disk12. If the host
operating system does not create a device file for a mapped LUN, you must run
the insf -e command to create one for the LUN.
You can run the following command to view the disk capacity information:
bash-4.1# diskinfo /dev/rdisk/disk12
SCSI describe of /dev/rdisk/disk12:
vendor: HUAWEI

Issue 10 (2023-08-02) Copyright © Huawei Technologies Co., Ltd. 37

OceanStor Dorado 6.x & OceanStor 6.x Host
Connectivity Guide for HP-UX 5 Configuring Connectivity

product id: XSG1

type: direct access
size: 104857600 Kbytes
bytes per sector: 512
bash-4.1#

----End

Issue 10 (2023-08-02) Copyright © Huawei Technologies Co., Ltd. 38

OceanStor Dorado 6.x & OceanStor 6.x Host
Connectivity Guide for HP-UX 6 Configuring Multipathing

6 Configuring Multipathing

6.1 Non-HyperMetro Scenarios

6.2 HyperMetro Scenarios

6.1 Non-HyperMetro Scenarios

6.1.1 Storage System Configuration

If you use OS native multipathing software, retain the default host and initiator
settings. By default, Host Access Mode is Load balancing. You can click the host
name and check the settings on the Summary tab page.

Figure 6-1 Checking storage configurations

NOTE

The information displayed on the GUI may vary slightly with the product version.

Issue 10 (2023-08-02) Copyright © Huawei Technologies Co., Ltd. 39

OceanStor Dorado 6.x & OceanStor 6.x Host
Connectivity Guide for HP-UX 6 Configuring Multipathing

If Host Access Mode is not Load balancing, perform the following steps to
change it:

Step 1 Click the host name and choose Operation > Modify.

Figure 6-2 Modifying the host properties

Step 2 Set Host Access Mode to Load balancing and click OK.

Figure 6-3 Modifying the host access mode

Step 3 Confirm the information and click OK.

Issue 10 (2023-08-02) Copyright © Huawei Technologies Co., Ltd. 40

OceanStor Dorado 6.x & OceanStor 6.x Host
Connectivity Guide for HP-UX 6 Configuring Multipathing

Figure 6-4 Confirming the operation

----End

NOTICE

● For details about the HP-UX versions, see the Huawei Storage Interoperability
Navigator.
● If a LUN has been mapped to a host, you must restart the host for the
configuration to take effect after you modify Host Access Mode. If you map
the LUN for the first time, restart is not needed.
● When data is migrated from other Huawei storage systems (including Dorado
V3, OceanStor V3, and OceanStor V5) to 6.x series storage systems, configure
the storage system by following instructions in 7.4 Recommended
Configurations for 6.x Series Storage Systems for Taking Over Data from
Other Huawei Storage Systems When the Host Uses the OS Native
Multipathing Software.

6.1.2 Host Configuration

This section describes how to check whether NMP is enabled and how to
configure NMP in various modes.

Checking Whether NMP Is Enabled

In HP-UX 11i v3, NMP is enabled by default, without the need for any extra
settings.
To check whether NMP is enabled, perform the following operations:

Step 1 Run the following command to check the NMP status:

bash-4.1# scsimgr get_attr -a leg_mpath_enable

SCSI GLOBAL ATTRIBUTES:

Issue 10 (2023-08-02) Copyright © Huawei Technologies Co., Ltd. 41

OceanStor Dorado 6.x & OceanStor 6.x Host
Connectivity Guide for HP-UX 6 Configuring Multipathing

name = leg_mpath_enable
current = true
default = true
saved =

The command output indicates that NMP has been enabled.

Step 2 (Optional) If NMP is disabled (current = false), run either of the following
commands to enable NMP:
scsimgr set_attr -a leg_mpath_enable=true
scsimgr save_attr -a leg_mpath_enable=true

NOTE

The first command will be invalid after the host is restarted. The second command is
effective permanently.

Step 3 Check the disks that the system discovers and the NMP status of mapped LUNs.
bash-4.1# ioscan -funNC disk
Class I H/W Path Driver S/W State H/W Type Description
===================================================================
disk 2 64000/0xfa00/0x0 esdisk CLAIMED DEVICE HP DG146BB976
/dev/disk/disk2 /dev/disk/disk2_p1 /dev/disk/disk2_p2 /dev/rdisk/disk2 /dev/rdisk/
disk2_p1 /dev/rdisk/disk2_p2
disk 3 64000/0xfa00/0x1 esdisk CLAIMED DEVICE HP DG146BB976
/dev/disk/disk3 /dev/disk/disk3_p1 /dev/disk/disk3_p2 /dev/disk/disk3_p3 /dev/rdisk/
disk3 /dev/rdisk/disk3_p1 /dev/rdisk/disk3_p2 /dev/rdisk/disk3_p3
disk 5 64000/0xfa00/0x2 esdisk CLAIMED DEVICE TEAC DVD-ROM DW-224EV
/dev/disk/disk5 /dev/rdisk/disk5
disk 12 64000/0xfa00/0xa esdisk CLAIMED DEVICE HUAWEI XSG1
/dev/disk/disk12 /dev/rdisk/disk12
bash-4.1# scsimgr get_attr -D /dev/rdisk/disk12 -a leg_mpath_enable

SCSI ATTRIBUTES FOR LUN : /dev/rdisk/disk12

name = leg_mpath_enable
current = true
default = true
saved =

According to the command output, the system identifies one LUN mapped from
the Huawei storage system (model: XSG1). The device name assigned to the LUN
is /dev/disk/disk12.
NMP is enabled for /dev/disk/disk12.
Step 4 (Optional) If NMP is already enabled for the LUN, skip this step. If the NMP status
for the LUN is false, run either of the following commands to change it to the
enabled state:
scsimgr set_attr -D /dev/rdisk/disk12 -a leg_mpath_enable=true
scsimgr save_attr -D /dev/rdisk/disk12 -a leg_mpath_enable=true

NOTE

The first command will be invalid after the host is restarted. The second command is
effective permanently.

----End

Checking NMP Configuration

When ALUA is disabled, round-robin is the default path selection policy for NMP,
without the need for any extra settings.

Issue 10 (2023-08-02) Copyright © Huawei Technologies Co., Ltd. 42

OceanStor Dorado 6.x & OceanStor 6.x Host
Connectivity Guide for HP-UX 6 Configuring Multipathing

Perform the following steps to check the NMP path policy:

Step 1 Check a LUN's path policy.

bash-4.1# scsimgr get_attr -D /dev/rdisk/disk12 -a load_bal_policy

SCSI ATTRIBUTES FOR LUN : /dev/rdisk/disk12

name = load_bal_policy
current = round_robin
default = round_robin
saved =

bash-4.1#

In this example, disk12's current path policy is round-robin.

Step 2 View the path information about the disks managed by NMP.
bash-4.1# scsimgr lun_map -D /dev/rdisk/disk12

LUN PATH INFORMATION FOR LUN : /dev/rdisk/disk12

Total number of LUN paths =4

World Wide Identifier(WWID) = 0x6002d52100f14ac30485420100000015

LUN path : lunpath7

Class = lunpath
Instance =7
Hardware path = 0/2/1/0/4/0.0x2211002d52f14ac3.0x4001000000000000
SCSI transport protocol = fibre_channel
State = ACTIVE
Last Open or Close state = ACTIVE

LUN path : lunpath8

Class = lunpath
Instance =8
Hardware path = 0/2/1/0/4/0.0x2201002d52f14ac3.0x4001000000000000
SCSI transport protocol = fibre_channel
State = ACTIVE
Last Open or Close state = ACTIVE

LUN path : lunpath9

Class = lunpath
Instance =9
Hardware path = 0/2/1/0/4/0.0x2202002d52f14ac3.0x4001000000000000
SCSI transport protocol = fibre_channel
State = ACTIVE
Last Open or Close state = ACTIVE

LUN path : lunpath11

Class = lunpath
Instance = 11
Hardware path = 0/2/1/0/4/0.0x2212002d52f14ac3.0x4001000000000000
SCSI transport protocol = fibre_channel
State = ACTIVE
Last Open or Close state = ACTIVE

bash-4.1#

In the preceding command output, ensure that all paths are in the ACTIVE state.

Issue 10 (2023-08-02) Copyright © Huawei Technologies Co., Ltd. 43

OceanStor Dorado 6.x & OceanStor 6.x Host
Connectivity Guide for HP-UX 6 Configuring Multipathing

NOTICE

When a LUN mapped to the host does not have any service, the state of paths to
this LUN on the host becomes UNOPEN. To restore the path status to ACTIVE, run
the ioscan command or read or write the mapped LUN.

----End

6.2 HyperMetro Scenarios

This section describes the multipathing configurations on the hosts and storage
systems. For details about how to configure HyperMetro services, see the
OceanStor Dorado HyperMetro Feature Guide.

6.2.1 Storage System Configuration

If the OS native multipathing software is used, retain the default settings of the
initiator and configure Host Access Mode and Preferred Path for HyperMetro as
required. Table 6-1 lists the detailed settings.

Table 6-1 Storage configurations for interconnection with HP-UX application servers
HyperMetro Storage OS Host Access Preferred Description
Working System Setting Mode Path for
Mode HyperMetro

Load Local HP-UX Asymmetric Yes The host uses all paths of
balancing storage a disk with equal priority.

Remote HP-UX Asymmetric Yes

storage

Local Local HP-UX Asymmetric Yes The host considers the

preferred storage paths from the local
storage system as
Remote HP-UX Asymmetric No preferred paths, and
storage those from the remote
storage system as non-
preferred paths.

Issue 10 (2023-08-02) Copyright © Huawei Technologies Co., Ltd. 44

OceanStor Dorado 6.x & OceanStor 6.x Host
Connectivity Guide for HP-UX 6 Configuring Multipathing

NOTICE

● For details about the HP-UX versions, see the Huawei Storage Interoperability
Navigator.
● If a LUN has been mapped to a host, you must restart the host for the
configuration to take effect after you modify Host Access Mode or Preferred
Path for HyperMetro. If you map the LUN for the first time, restart is not
needed.
● Ensure that HyperMetro is working properly when modifying networking.
● When data is migrated from other Huawei storage systems (including
OceanStor Dorado V3, OceanStor V3, and OceanStor V5) to 6.x series storage
systems, configure the storage system by following instructions in 7.4
Recommended Configurations for 6.x Series Storage Systems for Taking
Over Data from Other Huawei Storage Systems When the Host Uses the
OS Native Multipathing Software.

Configuring the Load Balancing Mode

Step 1 Click the host name and choose Operation > Modify.

Figure 6-5 Modifying the host properties

NOTE

The information displayed on the GUI may vary slightly with the product version.

Step 2 For both the local and remote storage systems, set Host Access Mode to
Asymmetric and Preferred Path for HyperMetro to Yes..

Issue 10 (2023-08-02) Copyright © Huawei Technologies Co., Ltd. 45

OceanStor Dorado 6.x & OceanStor 6.x Host
Connectivity Guide for HP-UX 6 Configuring Multipathing

Figure 6-6 Settings on the local and remote storage systems

----End

Configuring the Local Preferred Mode

Step 1 Click the host name and choose Operation > Modify.

Figure 6-7 Modifying the host properties

Step 2 For the local storage system, set Host Access Mode to Asymmetric and Preferred
Path for HyperMetro to Yes. For the remote storage system, set Host Access
Mode to Asymmetric and Preferred Path for HyperMetro to No.

Issue 10 (2023-08-02) Copyright © Huawei Technologies Co., Ltd. 46

OceanStor Dorado 6.x & OceanStor 6.x Host
Connectivity Guide for HP-UX 6 Configuring Multipathing

Figure 6-8 Settings on the local storage system

Figure 6-9 Settings on the remote storage system

----End

6.2.2 Host Configuration

Verifying Version and Patch Requirements
NMP requires that the operating system should not be earlier than HP-UX 11i v3
Update 4 (11.31.0903).
Run the following command to query the operating system version:
bash-4.1# swlist | grep HPUX11i
HPUX11i-DC-OE B.11.31.1403 HP-UX Data Center Operating Environment
bash-4.1#

According to the command output, the version is HP-UX 11i v3 1403, meeting
requirements.

Issue 10 (2023-08-02) Copyright © Huawei Technologies Co., Ltd. 47

OceanStor Dorado 6.x & OceanStor 6.x Host
Connectivity Guide for HP-UX 6 Configuring Multipathing

Enabling Multipathing Software

By default, NMP is enabled. No extra setting is required.
You can run the following command to check the load balancing policy and ALUA
status of a LUN:
bash-4.1# scsimgr get_attr -D /dev/rdisk/disk12 -a load_bal_policy

SCSI ATTRIBUTES FOR LUN : /dev/rdisk/disk12

name = load_bal_policy
current = round_robin
default = round_robin
saved =

bash-4.1#
bash-4.1# scsimgr get_attr -D /dev/rdisk/disk12 -a alua_enabled

SCSI ATTRIBUTES FOR LUN : /dev/rdisk/disk12

name = alua_enabled
current = true
default = true
saved =

bash-4.1#

According to the command output, the load balancing policy is round-robin, and
ALUA is enabled.

NOTE

disk12 is a device file created for the mapped LUN after connectivity is configured.

Configuring Multipathing Software

Retain the default settings. You can run the scsimgr lun_map -D /dev/rdisk/
disk# command to view the disk path information and LUN attributes. For details,
see 6.2.3 Verification.

6.2.3 Verification
Verifying the Load Balancing Mode
Step 1 Run the ioscan -funNC disk command to check whether HyperMetro LUNs have
been properly aggregated.
HyperMetro LUNs should be aggregated as a drive letter on the host, such as
disk12 in the following example:
bash-4.1# ioscan -funNC disk
Class I H/W Path Driver S/W State H/W Type Description
===================================================================
disk 2 64000/0xfa00/0x0 esdisk CLAIMED DEVICE HP DG146BB976
/dev/disk/disk2 /dev/disk/disk2_p1 /dev/disk/disk2_p2 /dev/rdisk/disk2 /dev/rdisk/
disk2_p1 /dev/rdisk/disk2_p2
disk 3 64000/0xfa00/0x1 esdisk CLAIMED DEVICE HP DG146BB976
/dev/disk/disk3 /dev/disk/disk3_p1 /dev/disk/disk3_p2 /dev/disk/disk3_p3 /dev/rdisk/
disk3 /dev/rdisk/disk3_p1 /dev/rdisk/disk3_p2 /dev/rdisk/disk3_p3
disk 5 64000/0xfa00/0x2 esdisk CLAIMED DEVICE TEAC DVD-ROM DW-224EV
/dev/disk/disk5 /dev/rdisk/disk5
disk 12 64000/0xfa00/0xa esdisk CLAIMED DEVICE HUAWEI XSG1
/dev/disk/disk12 /dev/rdisk/disk12

Issue 10 (2023-08-02) Copyright © Huawei Technologies Co., Ltd. 48

OceanStor Dorado 6.x & OceanStor 6.x Host
Connectivity Guide for HP-UX 6 Configuring Multipathing

Step 2 Run the scsimgr lun_map -D /dev/rdisk/disk# command to check the path status
and number of paths.
The number of paths should be the sum of the logical paths on both storage
systems (consistent with the actual configuration).
bash-4.1# scsimgr lun_map -D /dev/rdisk/disk12

LUN PATH INFORMATION FOR LUN : /dev/rdisk/disk12

Total number of LUN paths =8

World Wide Identifier(WWID) = 0x6002d52100f14ac30485420100000015

LUN path : lunpath17

Class = lunpath
Instance = 17
Hardware path = 0/2/1/0/4/0.0x2992010203040509.0x4001000000000000
SCSI transport protocol = fibre_channel
State = UNOPEN
Last Open or Close state = ACTIVE

LUN path : lunpath16

Class = lunpath
Instance = 16
Hardware path = 0/2/1/0/4/0.0x2991010203040509.0x4001000000000000
SCSI transport protocol = fibre_channel
State = UNOPEN
Last Open or Close state = ACTIVE

LUN path : lunpath19

Class = lunpath
Instance = 19
Hardware path = 0/2/1/0/4/0.0x2812010203040509.0x4001000000000000
SCSI transport protocol = fibre_channel
State = UNOPEN
Last Open or Close state = ACTIVE

LUN path : lunpath7

Class = lunpath
Instance =7
Hardware path = 0/2/1/0/4/0.0x2211002d52f14ac3.0x4001000000000000
SCSI transport protocol = fibre_channel
State = UNOPEN
Last Open or Close state = ACTIVE

LUN path : lunpath11

Class = lunpath
Instance = 11
Hardware path = 0/2/1/0/4/0.0x2212002d52f14ac3.0x4001000000000000
SCSI transport protocol = fibre_channel
State = UNOPEN
Last Open or Close state = ACTIVE

LUN path : lunpath9

Class = lunpath
Instance =9
Hardware path = 0/2/1/0/4/0.0x2202002d52f14ac3.0x4001000000000000
SCSI transport protocol = fibre_channel
State = UNOPEN
Last Open or Close state = ACTIVE

LUN path : lunpath8

Class = lunpath
Instance =8
Hardware path = 0/2/1/0/4/0.0x2201002d52f14ac3.0x4001000000000000
SCSI transport protocol = fibre_channel
State = UNOPEN
Last Open or Close state = ACTIVE

LUN path : lunpath13

Issue 10 (2023-08-02) Copyright © Huawei Technologies Co., Ltd. 49

OceanStor Dorado 6.x & OceanStor 6.x Host
Connectivity Guide for HP-UX 6 Configuring Multipathing

Class = lunpath
Instance = 13
Hardware path = 0/2/1/0/4/0.0x2811010203040509.0x4001000000000000
SCSI transport protocol = fibre_channel
State = UNOPEN
Last Open or Close state = ACTIVE

bash-4.1#

In the preceding command output, State=ACTIVE corresponds to preferred paths.

State of eight paths (lunpath7, lunpath8, lunpath9, lunpath11, lunpath13,
lunpath16, lunpath17, and lunpath19) is ACTIVE, which is consistent with the
actual configuration. The configuration is successful.

NOTICE

When a LUN mapped to the host does not have any service, the state of paths to
this LUN on the host becomes UNOPEN. To restore the path status to ACTIVE, run
the ioscan command or read or write the mapped LUN.

----End

Verifying the Local Preferred Mode

Step 1 Run the ioscan -funNC disk command to check HyperMetro LUNs have been
aggregated.
HyperMetro LUNs should be aggregated as a drive letter on the host, such as
disk12 in the following example:
bash-3.2# ioscan -funNC disk
Class I H/W Path Driver S/W State H/W Type Description
===================================================================
disk 2 64000/0xfa00/0x0 esdisk CLAIMED DEVICE HP DG146BB976
/dev/disk/disk2 /dev/disk/disk2_p1 /dev/disk/disk2_p2 /dev/rdisk/disk2 /dev/rdisk/
disk2_p1 /dev/rdisk/disk2_p2
disk 3 64000/0xfa00/0x1 esdisk CLAIMED DEVICE HP DG146BB976
/dev/disk/disk3 /dev/disk/disk3_p1 /dev/disk/disk3_p2 /dev/disk/disk3_p3 /dev/rdisk/
disk3 /dev/rdisk/disk3_p1 /dev/rdisk/disk3_p2 /dev/rdisk/disk3_p3
disk 5 64000/0xfa00/0x2 esdisk CLAIMED DEVICE TEAC DVD-ROM DW-224EV
/dev/disk/disk5 /dev/rdisk/disk5
disk 12 64000/0xfa00/0xa esdisk CLAIMED DEVICE HUAWEI XSG1
/dev/disk/disk12 /dev/rdisk/disk12

Step 2 Run the scsimgr lun_map -D /dev/rdisk/disk# command to check the path status
and number of paths.
The number of paths should be the sum of the logical paths on both storage
systems (consistent with the actual configuration).
bash-4.1# scsimgr lun_map -D /dev/rdisk/disk12

LUN PATH INFORMATION FOR LUN : /dev/rdisk/disk12

Total number of LUN paths =8

World Wide Identifier(WWID) = 0x6002d52100f14ac30485420100000015

LUN path : lunpath13

Class = lunpath
Instance = 13
Hardware path = 0/2/1/0/4/0.0x2811010203040509.0x4001000000000000
SCSI transport protocol = fibre_channel
State = UNOPEN

Issue 10 (2023-08-02) Copyright © Huawei Technologies Co., Ltd. 50

OceanStor Dorado 6.x & OceanStor 6.x Host
Connectivity Guide for HP-UX 6 Configuring Multipathing

Last Open or Close state = STANDBY

LUN path : lunpath7

Class = lunpath
Instance =7
Hardware path = 0/2/1/0/4/0.0x2211002d52f14ac3.0x4001000000000000
SCSI transport protocol = fibre_channel
State = UNOPEN
Last Open or Close state = ACTIVE

LUN path : lunpath16

Class = lunpath
Instance = 16
Hardware path = 0/2/1/0/4/0.0x2991010203040509.0x4001000000000000
SCSI transport protocol = fibre_channel
State = UNOPEN
Last Open or Close state = STANDBY

LUN path : lunpath9

Class = lunpath
Instance =9
Hardware path = 0/2/1/0/4/0.0x2202002d52f14ac3.0x4001000000000000
SCSI transport protocol = fibre_channel
State = UNOPEN
Last Open or Close state = ACTIVE

LUN path : lunpath8

Class = lunpath
Instance =8
Hardware path = 0/2/1/0/4/0.0x2201002d52f14ac3.0x4001000000000000
SCSI transport protocol = fibre_channel
State = UNOPEN
Last Open or Close state = ACTIVE

LUN path : lunpath17

Class = lunpath
Instance = 17
Hardware path = 0/2/1/0/4/0.0x2992010203040509.0x4001000000000000
SCSI transport protocol = fibre_channel
State = UNOPEN
Last Open or Close state = STANDBY

LUN path : lunpath11

Class = lunpath
Instance = 11
Hardware path = 0/2/1/0/4/0.0x2212002d52f14ac3.0x4001000000000000
SCSI transport protocol = fibre_channel
State = UNOPEN
Last Open or Close state = ACTIVE

LUN path : lunpath19

Class = lunpath
Instance = 19
Hardware path = 0/2/1/0/4/0.0x2812010203040509.0x4001000000000000
SCSI transport protocol = fibre_channel
State = UNOPEN
Last Open or Close state = STANDBY

In the preceding command output, State=ACTIVE corresponds to preferred paths,

and State=STANDBY corresponds to non-preferred paths. State of four paths
(lunpath7, lunpath8, lunpath9, and lunpath11) is ACTIVE, and that of the other
four (lunpath13, lunpath16, lunpath17, and lunpath19) is STANDBY, which are
consistent with the actual configuration. The configuration is successful.

Issue 10 (2023-08-02) Copyright © Huawei Technologies Co., Ltd. 51

OceanStor Dorado 6.x & OceanStor 6.x Host
Connectivity Guide for HP-UX 6 Configuring Multipathing

NOTICE

When a LUN mapped to the host does not have any service, the state of paths to
this LUN on the host becomes UNOPEN. To restore the path status to ACTIVE, run
the ioscan command or read or write the mapped LUN.

----End

Issue 10 (2023-08-02) Copyright © Huawei Technologies Co., Ltd. 52

OceanStor Dorado 6.x & OceanStor 6.x Host
Connectivity Guide for HP-UX 7 FAQs

7 FAQs

7.1 Changing LUN Mappings When Third-Party Multipathing Software Is Used on

an HP-UX Host
7.2 iSCSI Software Installation Failure
7.3 LUNs Cannot Be Discovered After a LUN with the Host LUN ID Being 0 Is
Manually Added
7.4 Recommended Configurations for 6.x Series Storage Systems for Taking Over
Data from Other Huawei Storage Systems When the Host Uses the OS Native
Multipathing Software

7.1 Changing LUN Mappings When Third-Party

Multipathing Software Is Used on an HP-UX Host
Symptom
Follow the correct procedure when you change LUN mappings on a storage
system, including removing and adding a LUN, changing host LUN IDs, enabling
command devices and manually allocating host LUN ID 0 to a LUN, and changing
ports on a storage system.

Root Cause
When a LUN mapping is removed from the storage system, the HP-UX host does
not delete the disk corresponding to the LUN. When a new LUN is mapped to the
host and the LUN has the same host LUN ID with the previously deleted one, NMP
may manage paths incorrectly after the host scans disks and identify the new and
previously deleted LUNs as the same one. As a result, the drive letter of the new
LUN cannot be refreshed. To prevent this problem, you must follow the correct
procedure when changing LUN mappings.

Procedure
In non-HyperMetro scenarios:

Issue 10 (2023-08-02) Copyright © Huawei Technologies Co., Ltd. 53

OceanStor Dorado 6.x & OceanStor 6.x Host
Connectivity Guide for HP-UX 7 FAQs

1. Stop the services running on the disk for which you want to change the
mapping.
2. Run the ioscan -funNC disk and diskinfo /dev/rdisk/diskxxx commands to
check whether residual disk information and command devices (16 KB disks)
exist on the host.
In the following example, NO_HW indicates that residual disk information
exist.

In the following example, command devices exist.

NOTE

If the third-party Veritas DMP multipathing software is used, run the vxdisk rm
huawei-xsg1*_# command to delete the disks managed by DMP, and then go to 3.
3. If the host has residual disk information and command devices, run the rmsf -
a /dev/disk/diskXXX command to delete all residual disk information and
command devices. This operation may change the drive letter of the disk after
the new LUN is mapped. If upper-layer applications on the host depend on
the drive letter, record the relationship between the drive letter and WWN
before deleting the disk, which helps you reconfigure services or restore the
original drive letter after the change.
The following is an example:

Issue 10 (2023-08-02) Copyright © Huawei Technologies Co., Ltd. 54

OceanStor Dorado 6.x & OceanStor 6.x Host
Connectivity Guide for HP-UX 7 FAQs

NOTICE

If the newly mapped LUN does not preempt the host LUN ID of the command
device, you do not need to delete the command device.

4. Add new mappings on the storage system and scan for disks on the host.
5. Contact the administrator to restart the services.
In HyperMetro scenarios:
To change the mappings on both storage systems, use the same method as the
non-HyperMetro scenario. If you only need to change the mapping on one storage
system, perform the following steps:
1. On the storage system, suspend the services on the LUN for which you want
to change the mapping. After all services have been switched to the other
storage system, perform 2.
2. Run the scsimgr lun_map -D /dev/rdisk/diskXXX command to query all
logical paths of the LUN for which you want to change the mapping.

Issue 10 (2023-08-02) Copyright © Huawei Technologies Co., Ltd. 55

OceanStor Dorado 6.x & OceanStor 6.x Host
Connectivity Guide for HP-UX 7 FAQs

3. Run the rmsf –H Hardware_path command to delete all logical paths of the
involved LUN.

Issue 10 (2023-08-02) Copyright © Huawei Technologies Co., Ltd. 56

OceanStor Dorado 6.x & OceanStor 6.x Host
Connectivity Guide for HP-UX 7 FAQs

4. Add new mappings on the storage system and scan for disks on the host.
5. Run the scsimgr lun_map -D /dev/rdisk/diskXXX command to check whether
the paths of the involved LUN are identified successfully.

7.2 iSCSI Software Installation Failure

Symptom
During iSCSI software installation, an error message "Could not open remote
depot/root" is displayed.

Issue 10 (2023-08-02) Copyright © Huawei Technologies Co., Ltd. 57

OceanStor Dorado 6.x & OceanStor 6.x Host
Connectivity Guide for HP-UX 7 FAQs

Figure 7-1 Error message

Root Cause Analysis

The host operating system installs a file based on a network path by default. If the
preceding error occurs, change the path to the correct local directory.

Troubleshooting
To change the path to the correct local directory, perform the following
operations:

Step 1 On the software installation interface, choose Actions > Change Source.

Figure 7-2 Software installation window-1

Step 2 In the Source Depot Type drop-down list, change Network Directory/CDROM to
Local Directory.

Issue 10 (2023-08-02) Copyright © Huawei Technologies Co., Ltd. 58

OceanStor Dorado 6.x & OceanStor 6.x Host
Connectivity Guide for HP-UX 7 FAQs

Figure 7-3 Software installation window-2

Set Source Depot Path to the absolute path of the installation package. Figure
7-3 shows the configuration information after modification.

Figure 7-4 Configuration information after modification

NOTICE

Source Host Name must be the same as that configured in the /etc/hosts.
Otherwise, the software cannot be installed.

Step 3 Mark again the software to be installed and then reinstall it.

----End

Issue 10 (2023-08-02) Copyright © Huawei Technologies Co., Ltd. 59

OceanStor Dorado 6.x & OceanStor 6.x Host
Connectivity Guide for HP-UX 7 FAQs

7.3 LUNs Cannot Be Discovered After a LUN with the

Host LUN ID Being 0 Is Manually Added
Symptom
After a user adds initiators to and maps LUNs to a host or host group, the host
can discover the LUNs. Then, the user maps a LUN with the host LUN ID being 0
to the host on DeviceManager. However, after the host scans for LUNs again, no
LUNs can be discovered.

Root Cause Analysis

In this scenario, the host considers that the WWN of the LUN whose host LUN ID
is 0 is different from that of the subsequently mapped LUN whose host LUN ID is
also 0. As a result, the host stops scanning for LUNs. In the event of replacing a
LUN, this problem also occurs.

Troubleshooting
If the tracing log contains "Run'scsimgr replace_wwid' command to validate the
change", run the scsimgr replace_wwid command to rectify the fault.
For example, the /var/adm/syslog/syslog.log file contains the following
information:
Oct 12 10:52:15 root vmunix: class : lunpath, instance 11
Oct 12 10:52:15 root vmunix: Evpd inquiry page 83h/80h failed or the current page 83h/80h data do
not match the previous known page 83h/80h data on LUN id 0x0 probed beneath the target path (class =
tgtpath, instance = 5) The lun path is (class = lunpath, instance 11).Run 'scsimgr replace_wwid' command
to validate the change
Oct 12 10:52:15 root vmunix:
Oct 12 10:52:15 root vmunix: An attempt to probe existing LUN id 0x0 failed with errno of 14.

In this case, you need to run the scsimgr replace_wwid -C lunpath –I 11

command and then the ioscan command to scan for LUNs. This ensures that the
host can properly scan for and discover LUNs.
To prevent the preceding problem, map LUNs to hosts by following instructions in
the Basic Storage Service Configuration Guide corresponding to your storage
system and then scan LUNs on the host.

7.4 Recommended Configurations for 6.x Series Storage

Systems for Taking Over Data from Other Huawei
Storage Systems When the Host Uses the OS Native
Multipathing Software
When data is migrated from other Huawei storage systems (including Dorado V3,
OceanStor V3, and OceanStor V5) to 6.x series storage systems, the old storage
system and 6.x storage system will connect to the host concurrently. You must
select a proper migration and configuration method based on the configurations

Issue 10 (2023-08-02) Copyright © Huawei Technologies Co., Ltd. 60

OceanStor Dorado 6.x & OceanStor 6.x Host
Connectivity Guide for HP-UX 7 FAQs

of the old storage and host to ensure proper running. The following provides
recommended configurations.

1. Configuration method for 6.x series storage systems working in load balancing mode

Host OS Current Configuration on the Configuration Before Migration Configuration After

Customer's Live Network (Both the Old Storage and 6.x Migration (Old
Storage Exist) Storage Offline)

Old Old Current Old 6.x Host 6.x Host

Storage Storage Host Storage Storage Configur Storage Configur
Scenario Configur Configur Configur Configur ation Configur ation
ation ation ation ation ation

HP-UX Non- ALUA ALUA Unchang Use the Unchang Unchang Unchang
HyperM ed default ed ed ed
etro host
access
mode,
that is,
load
balancin
g.

ALUA AA Unchang Use the Unchang Unchang Unchang

not used ed default ed ed ed
host
access
mode,
that is,
load
balancin
g.

HyperM ALUA ALUA Unchang Use the Unchang Unchang Unchang

etro ed default ed ed ed
host
access
mode,
that is,
load
balancin
g.

Note 1: If LUNs have been mapped to the host, you must restart the host for the configuration to
take effect after changing the initiator mode or host access mode on the storage systems.

2. Configuration method for 6.x series storage systems working in asymmetric mode

Host OS Current Configuration Before Migration Configuration After

Configuration on (Both the Old Storage and 6.x Migration (Old
the Customer's Live Storage Exist) Storage Offline)
Network

Issue 10 (2023-08-02) Copyright © Huawei Technologies Co., Ltd. 61

OceanStor Dorado 6.x & OceanStor 6.x Host
Connectivity Guide for HP-UX 7 FAQs

Old Old Current Old 6.x Host 6.x Host

Storage Storage Host Storage Storage Configur Storage Configur
Scenario Configur Configur Configur Configur ation Configur ation
ation ation ation ation ation

HP-UX Non- ALUA ALUA Unchang Set the Unchang Unchang Unchang
HyperM ed host ed ed ed
etro access
mode to
asymme
tric.

ALUA AA Unchang Set the Unchang Unchang Unchang

not used ed host ed ed ed
access
mode to
asymme
tric.

HyperM ALUA ALUA Unchang Set the Unchang Unchang Unchang

etro ed host ed ed ed
access
mode to
asymme
tric.

Note 1: If LUNs have been mapped to the host, you must restart the host for the configuration to
take effect after changing the initiator mode or host access mode on the storage systems.

Issue 10 (2023-08-02) Copyright © Huawei Technologies Co., Ltd. 62

OceanStor Dorado 6.x & OceanStor 6.x Host
Connectivity Guide for HP-UX 8 Acronyms and Abbreviations

8 Acronyms and Abbreviations

A
AN Active Non-optimized
AO Active Optimized

C
CLI Command Line Interface
CDFS CD-ROM File System

E
EUI Extended Unique Identifier

F
FC Fibre Channel
FCoE Fibre Channel over Ethernet

H
HBA Host Bus Adapter
HFS High Performance File System
HP-UX Hewlett Packard UniX

I
iSCSI Internet Small Computer System
Interface
ISM Integrated Storage Manager

J
JFS Journaled File System

Issue 10 (2023-08-02) Copyright © Huawei Technologies Co., Ltd. 63

OceanStor Dorado 6.x & OceanStor 6.x Host
Connectivity Guide for HP-UX 8 Acronyms and Abbreviations

L
LE Logical Extent
LACP Link Aggregation Control Protocol
LUN Logical Unit Number
LV Logic Volume
LVM Logical Volume Manager

M
MC Multi-Computer

N
NMP Native Multipathing Plug-In
NFS Network File System

R
RAID Redundant Array of Independent Disks

S
SAM System Administration Manager
SG ServiceGuard
SMH System Management Homepage
SP storage processor

P
PE Physical Extent

V
VG Volume Group
VxFS Veritas file system
VxVM Veritas Volume Manager

W
WWN World Wide Name

Issue 10 (2023-08-02) Copyright © Huawei Technologies Co., Ltd. 64

OceanStor Dorado 6.x & OceanStor 6.x Host
Connectivity Guide for HP-UX 9 Appendix A Volume Management

9 Appendix A Volume Management

Volume management software widely used in HP-UX includes LVM delivered with
HP-UX and VxVM provided by Symantec.

This chapter details LVM and VxVM.

9.1 LVM
9.2 VxVM

9.1 LVM

9.1.1 Overview
LVM combines space in several disks (physical volumes) into a volume group (VG)
and then divides the space in the VG into logical volumes (LVs), namely, partitions
in LVM.

LVM is superior to the complete disk method in the following aspects:

● LVs that cross multiple disks can be created.

● Multiple LVs can be created on the same disk.
● LVs can be expanded and compressed as required.

Before using LVM, master the following concepts:

Physical Volume
Disks managed by LVM are called physical volumes (PVs). Before disks are used by
LVM, certain special data is constructed on these disks. Disks with the constructed
data are considered to be PVs and can be added to VGs.

Physical Volume Device File

You can use PV-related disk device files to reference PVs. Disks may be associated
as block devices or character devices. Therefore, each PV has a block device file
and a character device file. For example:

Issue 10 (2023-08-02) Copyright © Huawei Technologies Co., Ltd. 65

OceanStor Dorado 6.x & OceanStor 6.x Host
Connectivity Guide for HP-UX 9 Appendix A Volume Management

● /dev/dsk/c0t3d0: a block device file in SCSI address 3

● /dev/rdsk/c0t3d0: a character device file in SCSI address 3

Volume Group
A volume group (VG) consists of one or more PVs. PVs in a VG provide disk space
that can be assigned to one or more LVs.

Volume Group Device File

VGs are associated by using device files. The /dev directory includes subdirectories
corresponding to each VG. Each subdirectory contains a device file named group
that is associated with the corresponding VG and device files associated with all
LVs in the VG. A VG subdirectory name determines the name of the corresponding
VG. For example:
● /dev/vg01: the directory that contains device files associated with the VG
named vg01
● /dev/vg01/group: the device file associated with the VG named vg01

Logical Volume
The disk space of a VG can be assigned to one or more LVs. Similar to a partition,
an LV can contain a file system, swap area, or original data.
In addition, LVs have the following characteristics:
● An LV can contain the space of all or some PVs.
● An LV can be expanded to include multiple PVs managed by LVM.
● The size of an LV can be changed, and an LV can be moved to another disk.

Logical Volume Device File

LV device files are stored in their VG directories. Each LV contains two device files:
One is used when the LV is accessed in character mode and the other is used
when the LV is accessed in block mode. For example:
● /dev/vg01/lvol01: the block device file associated with lvol01 in vg0
● /dev/vg01/rlvol01: the logical device file associated with lvol01 in vg01

LVM Major and Minor Numbers

Each LV or VG device file has a major number and a minor number.
The major number of all LVM device files is 64. The major number is related to the
LVM kernel driver.
The first two digits of a minor number indicate the related VG, and the last two
digits indicate the related LV.
The following is an example:
bash-4.0# ls -lrt /dev/vg_try/*
crw-r--r-- 1 root sys 64 0x050000 Jul 27 17:13 /dev/vg_try/group
brw-r----- 1 root sys 64 0x050001 Jul 27 17:57 /dev/vg_try/lv_try00

Issue 10 (2023-08-02) Copyright © Huawei Technologies Co., Ltd. 66

OceanStor Dorado 6.x & OceanStor 6.x Host
Connectivity Guide for HP-UX 9 Appendix A Volume Management

crw-r----- 1 root sys 64 0x050001 Jul 27 17:57 /dev/vg_try/rlv_try00

brw-r----- 1 root sys 64 0x050002 Jul 27 17:57 /dev/vg_try/lv_try01
crw-r----- 1 root sys 64 0x050002 Jul 27 17:57 /dev/vg_try/rlv_try01
bash-4.0#

The preceding command output is about lv_try01. The detailed explanation is as

follows:
● Name: /dev/vg_try/lv_try01
● Major number: 64
● Minor number: 0x050002
The first two digits (05) indicate that the volume is in the vg_try VG, and the last
two digits (02) indicate the LV name is lv_try01.

PE and LE
In LVM, the minimum space unit assigned is called extent. PVs can be divided into
multiple physical extents (PEs). PVs can be assigned and used immediately after
being added to a VG.
An LV contains a series of sequential logical extents (LEs). Each LE is a pointer
that points to a PE on a disk.
The size of a PE and that of LE in a VG are the same and can be set during VG
creation. By default, the extent size is 4 MB.

9.1.2 Installation
By default, LVM is automatically installed along with the installation of the host
operating system and does not need to be configured.

9.1.3 Common Configuration Commands

Creating a PV
To create a PV, perform the following steps:

Step 1 Query disks that exist in the system.

bash-4.0# ioscan -funC disk
Class I H/W Path Driver S/W State H/W Type Description
==================================================================
disk 0 0/0/0/2/0/0/0.8.0 sdisk CLAIMED DEVICE HP EH0072FAWJA
/dev/dsk/c0t8d0 /dev/rdsk/c0t8d0
disk 1 0/0/0/2/0/0/0.8.1 sdisk CLAIMED DEVICE HP EH0072FAWJA
/dev/dsk/c0t8d1 /dev/dsk/c0t8d1s2 /dev/rdsk/c0t8d1 /dev/rdsk/c0t8d1s2
/dev/dsk/c0t8d1s1 /dev/dsk/c0t8d1s3 /dev/rdsk/c0t8d1s1 /dev/rdsk/c0t8d1s3
disk 52 0/0/0/7/0/0/0.3.20.0.0.0.0 sdisk CLAIMED DEVICE HUAWEI S3900-M200
/dev/dsk/c13t0d0 /dev/rdsk/c13t0d0
disk 53 0/0/0/7/0/0/0.3.20.0.0.0.1 sdisk CLAIMED DEVICE HUAWEI S3900-M200
/dev/dsk/c13t0d1 /dev/rdsk/c13t0d1
disk 54 0/0/0/7/0/0/1.1.20.0.0.0.0 sdisk CLAIMED DEVICE HUAWEI S3900-M200
/dev/dsk/c14t0d0 /dev/rdsk/c14t0d0
disk 55 0/0/0/7/0/0/1.1.20.0.0.0.1 sdisk CLAIMED DEVICE HUAWEI S3900-M200
/dev/dsk/c14t0d1 /dev/rdsk/c14t0d1
bash-4.0#

Step 2 Select proper disks to create PVs.

bash-4.0# pvcreate -f /dev/rdsk/c13t0d0
Physical volume "/dev/rdsk/c13t0d0" has been successfully created.

Issue 10 (2023-08-02) Copyright © Huawei Technologies Co., Ltd. 67

OceanStor Dorado 6.x & OceanStor 6.x Host
Connectivity Guide for HP-UX 9 Appendix A Volume Management

bash-4.0#
bash-4.0# pvcreate -f /dev/rdsk/c14t0d0
Physical volume "/dev/rdsk/c14t0d0" has been successfully created.
bash-4.0#

In the preceding example, c13t0d0 and c14t0d0 are selected to create PVs.

If you are not sure whether disks have bad blocks, run the mediainit command to
initialize the disks. This command checks disk completeness in read and write test
mode and sets all identified bad blocks to the idle state. The command syntax is
as follows:
bash-4.0# mediainit /dev/rdsk/c14t0d2

NOTICE

The mediainit command damages all existing user data on a disk. Therefore,
exercise caution when using this command.

Step 3 Run the pvdisplay command to check whether PVs are created successfully.
bash-4.0# pvdisplay -l /dev/dsk/c13t0d0
/dev/dsk/c13t0d0:LVM_Disk=yes
bash-4.0# pvdisplay -l /dev/dsk/c13t0d1
/dev/dsk/c13t0d1:LVM_Disk=no
bash-4.0#

If a PV is successfully created, the value of LVM_Disk is yes. If a PV fails to be

created, the value is no. The preceding command output indicates that a PV is
successfully created on the c13t0d0 disk but a PV is not created on the c13t0d1
disk.

----End

Creating a VG
To create a VG, perform the following steps:

Step 1 Create a VG directory and VG device file.

bash-4.0# ls -lrt /dev/*/group
crw-r----- 1 root sys 64 0x000000 May 23 17:38 /dev/vg00/group
crw-r--r-- 1 root sys 64 0x030000 May 26 17:10 /dev/vg_test2/group
crw-r--r-- 1 root sys 64 0x060000 May 28 09:43 /dev/vg_testB/group
crw-r--r-- 1 root sys 64 0x040000 May 28 10:03 /dev/vg_testC/group
bash-4.0#
bash-4.0# mkdir /dev/vg_try
bash-4.0# mknod /dev/vg_try/group c 64 0x050000
bash-4.0#

The first command queries the VG device files that exist in the system. The second
and third commands are used to create a VG device file.

VG device files (also called control files) enable the LVM kernel and LVM
commands to communicate in the created VGs.

Issue 10 (2023-08-02) Copyright © Huawei Technologies Co., Ltd. 68

OceanStor Dorado 6.x & OceanStor 6.x Host
Connectivity Guide for HP-UX 9 Appendix A Volume Management

NOTE

The group file is a character device file. Its major number is 64 and its minor number ends
with 0000 in hexadecimal format as follows:
0xhh0000
hh indicates a VG number in hexadecimal format and its value varies with VGs.

Step 2 Select PVs to create a VG.

bash-4.0# vgcreate /dev/vg_try /dev/dsk/c13t0d0 /dev/dsk/c14t0d0
Increased the number of physical extents per physical volume to 1535.
Volume group "/dev/vg_try" has been successfully created.
Volume Group configuration for /dev/vg_try has been saved in /etc/lvmconf/vg_try.conf
bash-4.0#

The preceding command creates a VG named vg_try with two PV members

c13t0d0 and c14t0d0. If the two PVs are devices on different paths of the same
LUN, the LUN is managed by the PV-Links multipathing software.
Step 3 Query VG information.
bash-4.0# vgdisplay -v vg_try
--- Volume groups ---
VG Name /dev/vg_try
VG Write Access read/write
VG Status available
Max LV 255
Cur LV 0
Open LV 0
Max PV 16
Cur PV 1
Act PV 1
Max PE per PV 1535
VGDA 2
PE Size (Mbytes) 4
Total PE 1535
Alloc PE 0
Free PE 1535
Total PVG 0
Total Spare PVs 0
Total Spare PVs in use 0
VG Version 1.0
VG Max Size 98240m
VG Max Extents 24560

--- Physical volumes ---

PV Name /dev/dsk/c13t0d0
PV Name /dev/dsk/c14t0d0 Alternate Link
PV Status available
Total PE 1535
Free PE 1535
Autoswitch On
Proactive Polling On

Devices on two paths of the same LUN are added to the vg_try VG. Therefore, the
LUN is managed by PV-Links.
The preceding command output indicates that the current primary path
is /dev/dsk/c13t0d0 and the secondary path is /dev/dsk/c14t0d0.

Issue 10 (2023-08-02) Copyright © Huawei Technologies Co., Ltd. 69

OceanStor Dorado 6.x & OceanStor 6.x Host
Connectivity Guide for HP-UX 9 Appendix A Volume Management

NOTICE

The primary/secondary state of each path is determined by the sequence of PVs

displayed in the command for creating a VG.

----End

Expanding a VG
The command syntax is as follows:
vgextend vgname pvname

The following is an example:

bash-4.0# vgdisplay -v /dev/vg_tong
--- Volume groups ---
VG Name /dev/vg_tong
VG Write Access read/write
VG Status available
Max LV 255
Cur LV 0
Open LV 0
Max PV 16
Cur PV 1
Act PV 1
Max PE per PV 1791
VGDA 2
PE Size (Mbytes) 4
Total PE 1791
Alloc PE 0
Free PE 1791
Total PVG 0
Total Spare PVs 0
Total Spare PVs in use 0
VG Version 1.0
VG Max Size 114624m
VG Max Extents 28656
--- Physical volumes ---
PV Name /dev/dsk/c14t0d1
PV Status available
Total PE 1791
Free PE 1791
Autoswitch On
Proactive Polling On
bash-4.0# vgextend /dev/vg_tong /dev/dsk/c13t0d1
Volume group "/dev/vg_tong" has been successfully extended.
Volume Group configuration for /dev/vg_tong has been saved in /etc/lvmconf/vg_tong.conf
bash-4.0#
bash-4.0# vgdisplay -v /dev/vg_tong
--- Volume groups ---
VG Name /dev/vg_tong
VG Write Access read/write
VG Status available
Max LV 255
Cur LV 0
Open LV 0
Max PV 16
Cur PV 1
Act PV 1
Max PE per PV 1791
VGDA 2
PE Size (Mbytes) 4
Total PE 1791
Alloc PE 0
Free PE 1791

Issue 10 (2023-08-02) Copyright © Huawei Technologies Co., Ltd. 70

OceanStor Dorado 6.x & OceanStor 6.x Host
Connectivity Guide for HP-UX 9 Appendix A Volume Management

Total PVG 0
Total Spare PVs 0
Total Spare PVs in use 0
VG Version 1.0
VG Max Size 114624m
VG Max Extents 28656
--- Physical volumes ---
PV Name /dev/dsk/c14t0d1
PV Name /dev/dsk/c13t0d1 Alternate Link
PV Status available
Total PE 1791
Free PE 1791
Autoswitch On
Proactive Polling On
bash-4.0#

The /dev/vg_tong VG contains the /dev/dsk/c14t0d1 PV. The preceding

command adds /dev/dsk/c13t0d1 to the VG for expansion purposes.

Creating an LV
To create an LV, perform the following steps:

Step 1 Run the lvcreate interactive command to create an LV.

The following is an example:
bash-4.0# lvcreate -L 10 -n lv_try00 vg_try
Warning: rounding up logical volume size to extent boundary at size "12" MB.
Logical volume "/dev/vg_try/lv_try00" has been successfully created with
character device "/dev/vg_try/rlv_try00".
Logical volume "/dev/vg_try/lv_try00" has been successfully extended.
Volume Group configuration for /dev/vg_try has been saved in /etc/lvmconf/vg_try.conf
bash-4.0#
bash-4.0# lvcreate -l 100 -n lv_try01 vg_try
Logical volume "/dev/vg_try/lv_try01" has been successfully created with
character device "/dev/vg_try/rlv_try01".
Logical volume "/dev/vg_try/lv_try01" has been successfully extended.
Volume Group configuration for /dev/vg_try has been saved in /etc/lvmconf/vg_try.conf
bash-4.0#

Some parameters in the command are described as follows:

● -L: size of the LV in MB
The actual size depends on the minimum value of complete logical extents. In
the preceding example, the intended LV size is 10 MB. However, the size of a
logical extent is 4 MB. Therefore, three logical extents are used to form an LV,
making the LV size be 12 MB.
● -l: number of logical extents in the LV
● -n: name of the LV
Retain default values for other parameters. Then press Enter to create the LV.
Step 2 Check the information about the created LV.
bash-4.0# vgdisplay -v vg_try
--- Volume groups ---
VG Name /dev/vg_try
VG Write Access read/write
VG Status available
Max LV 255
Cur LV 2
Open LV 2
Max PV 16
Cur PV 1

Issue 10 (2023-08-02) Copyright © Huawei Technologies Co., Ltd. 71

OceanStor Dorado 6.x & OceanStor 6.x Host
Connectivity Guide for HP-UX 9 Appendix A Volume Management

Act PV 1
Max PE per PV 1535
VGDA 2
PE Size (Mbytes) 4
Total PE 1535
Alloc PE 103
Free PE 1432
Total PVG 0
Total Spare PVs 0
Total Spare PVs in use 0
VG Version 1.0
VG Max Size 98240m
VG Max Extents 24560

--- Logical volumes ---

LV Name /dev/vg_try/lv_try00
LV Status available/syncd
LV Size (Mbytes) 12
Current LE 3
Allocated PE 3
Used PV 1

LV Name /dev/vg_try/lv_try01
LV Status available/syncd
LV Size (Mbytes) 400
Current LE 100
Allocated PE 100
Used PV 1

--- Physical volumes ---

PV Name /dev/dsk/c13t0d0
PV Name /dev/dsk/c14t0d0 Alternate Link
PV Status available
Total PE 1535
Free PE 1432
Autoswitch On
Proactive Polling On
bash-4.0#
bash-4.0# lvdisplay -v /dev/vg_try/lv_try00
--- Logical volumes ---
LV Name /dev/vg_try/lv_try00
VG Name /dev/vg_try
LV Permission read/write
LV Status available/syncd
Mirror copies 0
Consistency Recovery MWC
Schedule parallel
LV Size (Mbytes) 12
Current LE 3
Allocated PE 3
Stripes 0
Stripe Size (Kbytes) 0
Bad block on
Allocation strict
IO Timeout (Seconds) default

--- Distribution of logical volume ---

PV Name LE on PV PE on PV
/dev/dsk/c13t0d0 3 3

--- Logical extents ---

LE PV1 PE1 Status 1
00000 /dev/dsk/c13t0d0 00000 current
00001 /dev/dsk/c13t0d0 00001 current
00002 /dev/dsk/c13t0d0 00002 current
bash-4.0#
bash-4.0# lvdisplay -v /dev/vg_try/lv_try01
--- Logical volumes ---
LV Name /dev/vg_try/lv_try01

Issue 10 (2023-08-02) Copyright © Huawei Technologies Co., Ltd. 72

OceanStor Dorado 6.x & OceanStor 6.x Host
Connectivity Guide for HP-UX 9 Appendix A Volume Management

VG Name /dev/vg_try
LV Permission read/write
LV Status available/syncd
Mirror copies 0
Consistency Recovery MWC
Schedule parallel
LV Size (Mbytes) 400
Current LE 100
Allocated PE 100
Stripes 0
Stripe Size (Kbytes) 0
Bad block on
Allocation strict
IO Timeout (Seconds) default

--- Distribution of logical volume ---

PV Name LE on PV PE on PV
/dev/dsk/c13t0d0 100 100

--- Logical extents ---

LE PV1 PE1 Status 1
00000 /dev/dsk/c13t0d0 00003 current
00001 /dev/dsk/c13t0d0 00004 current
00002 /dev/dsk/c13t0d0 00005 current
00003 /dev/dsk/c13t0d0 00006 current
00004 /dev/dsk/c13t0d0 00007 current
00005 /dev/dsk/c13t0d0 00008 current
00006 /dev/dsk/c13t0d0 00009 current
00007 /dev/dsk/c13t0d0 00010 current
00008 /dev/dsk/c13t0d0 00011 current
00009 /dev/dsk/c13t0d0 00012 current
00010 /dev/dsk/c13t0d0 00013 current
00011 /dev/dsk/c13t0d0 00014 current
00012 /dev/dsk/c13t0d0 00015 current
00013 /dev/dsk/c13t0d0 00016 current
00014 /dev/dsk/c13t0d0 00017 current
00015 /dev/dsk/c13t0d0 00018 current
00016 /dev/dsk/c13t0d0 00019 current
00017 /dev/dsk/c13t0d0 00020 current
00018 /dev/dsk/c13t0d0 00021 current
00019 /dev/dsk/c13t0d0 00022 current
00020 /dev/dsk/c13t0d0 00023 current
00021 /dev/dsk/c13t0d0 00024 current
00022 /dev/dsk/c13t0d0 00025 current
00023 /dev/dsk/c13t0d0 00026 current
00024 /dev/dsk/c13t0d0 00027 current
00025 /dev/dsk/c13t0d0 00028 current
00026 /dev/dsk/c13t0d0 00029 current
00027 /dev/dsk/c13t0d0 00030 current
00028 /dev/dsk/c13t0d0 00031 current
00029 /dev/dsk/c13t0d0 00032 current
00030 /dev/dsk/c13t0d0 00033 current
00031 /dev/dsk/c13t0d0 00034 current
00032 /dev/dsk/c13t0d0 00035 current
00033 /dev/dsk/c13t0d0 00036 current
00034 /dev/dsk/c13t0d0 00037 current
00035 /dev/dsk/c13t0d0 00038 current
00036 /dev/dsk/c13t0d0 00039 current
00037 /dev/dsk/c13t0d0 00040 current
00038 /dev/dsk/c13t0d0 00041 current
00039 /dev/dsk/c13t0d0 00042 current
00040 /dev/dsk/c13t0d0 00043 current
00041 /dev/dsk/c13t0d0 00044 current
00042 /dev/dsk/c13t0d0 00045 current
00043 /dev/dsk/c13t0d0 00046 current
00044 /dev/dsk/c13t0d0 00047 current
00045 /dev/dsk/c13t0d0 00048 current
00046 /dev/dsk/c13t0d0 00049 current
00047 /dev/dsk/c13t0d0 00050 current

Issue 10 (2023-08-02) Copyright © Huawei Technologies Co., Ltd. 73

OceanStor Dorado 6.x & OceanStor 6.x Host
Connectivity Guide for HP-UX 9 Appendix A Volume Management

00048 /dev/dsk/c13t0d0 00051 current

00049 /dev/dsk/c13t0d0 00052 current
00050 /dev/dsk/c13t0d0 00053 current
00051 /dev/dsk/c13t0d0 00054 current
00052 /dev/dsk/c13t0d0 00055 current
00053 /dev/dsk/c13t0d0 00056 current
00054 /dev/dsk/c13t0d0 00057 current
00055 /dev/dsk/c13t0d0 00058 current
00056 /dev/dsk/c13t0d0 00059 current
00057 /dev/dsk/c13t0d0 00060 current
00058 /dev/dsk/c13t0d0 00061 current
00059 /dev/dsk/c13t0d0 00062 current
00060 /dev/dsk/c13t0d0 00063 current
00061 /dev/dsk/c13t0d0 00064 current
00062 /dev/dsk/c13t0d0 00065 current
00063 /dev/dsk/c13t0d0 00066 current
00064 /dev/dsk/c13t0d0 00067 current
00065 /dev/dsk/c13t0d0 00068 current
00066 /dev/dsk/c13t0d0 00069 current
00067 /dev/dsk/c13t0d0 00070 current
00068 /dev/dsk/c13t0d0 00071 current
00069 /dev/dsk/c13t0d0 00072 current
00070 /dev/dsk/c13t0d0 00073 current
00071 /dev/dsk/c13t0d0 00074 current
00072 /dev/dsk/c13t0d0 00075 current
00073 /dev/dsk/c13t0d0 00076 current
00074 /dev/dsk/c13t0d0 00077 current
00075 /dev/dsk/c13t0d0 00078 current
00076 /dev/dsk/c13t0d0 00079 current
00077 /dev/dsk/c13t0d0 00080 current
00078 /dev/dsk/c13t0d0 00081 current
00079 /dev/dsk/c13t0d0 00082 current
00080 /dev/dsk/c13t0d0 00083 current
00081 /dev/dsk/c13t0d0 00084 current
00082 /dev/dsk/c13t0d0 00085 current
00083 /dev/dsk/c13t0d0 00086 current
00084 /dev/dsk/c13t0d0 00087 current
00085 /dev/dsk/c13t0d0 00088 current
00086 /dev/dsk/c13t0d0 00089 current
00087 /dev/dsk/c13t0d0 00090 current
00088 /dev/dsk/c13t0d0 00091 current
00089 /dev/dsk/c13t0d0 00092 current
00090 /dev/dsk/c13t0d0 00093 current
00091 /dev/dsk/c13t0d0 00094 current
00092 /dev/dsk/c13t0d0 00095 current
00093 /dev/dsk/c13t0d0 00096 current
00094 /dev/dsk/c13t0d0 00097 current
00095 /dev/dsk/c13t0d0 00098 current
00096 /dev/dsk/c13t0d0 00099 current
00097 /dev/dsk/c13t0d0 00100 current
00098 /dev/dsk/c13t0d0 00101 current
00099 /dev/dsk/c13t0d0 00102 current
bash-4.0#

The mapping between the PEs and LEs is displayed.

----End

Creating a File System

To create a file system, perform the following steps:

Step 1 Run the newfs command to create a file system. The following is an example:
bash-4.0# newfs -F vxfs -o largefiles /dev/vg_try/rlv_try00
version 7 layout
12288 sectors, 12288 blocks of size 1024, log size 1024 blocks
largefiles supported
bash-4.0#

Issue 10 (2023-08-02) Copyright © Huawei Technologies Co., Ltd. 74

OceanStor Dorado 6.x & OceanStor 6.x Host
Connectivity Guide for HP-UX 9 Appendix A Volume Management

bash-4.0# newfs -F hfs -o largefiles /dev/vg_try/rlv_try01

mkfs (hfs): Warning - 40 sector(s) in the last cylinder are not allocated.
mkfs (hfs): /dev/vg_try/rlv_try01 - 409600 sectors in 2660 cylinders of 7 tracks, 22 sectors
419.4Mb in 167 cyl groups (16 c/g, 2.52Mb/g, 384 i/g)
Super block backups (for fsck -b) at:
16, 2504, 4992, 7480, 9968, 12456, 14944, 17432, 19728, 22216,
24704, 27192, 29680, 32168, 34656, 37144, 39440, 41928, 44416, 46904,
49392, 51880, 54368, 56856, 59152, 61640, 64128, 66616, 69104, 71592,
74080, 76568, 78864, 81352, 83840, 86328, 88816, 91304, 93792, 96280,
98576, 101064, 103552, 106040, 108528, 111016, 113504, 115992, 118288, 120776,
123264, 125752, 128240, 130728, 133216, 135704, 138000, 140488, 142976, 145464,
147952, 150440, 152928, 155416, 157712, 160200, 162688, 165176, 167664, 170152,
172640, 175128, 177424, 179912, 182400, 184888, 187376, 189864, 192352, 194840,
197136, 199624, 202112, 204600, 207088, 209576, 212064, 214552, 216848, 219336,
221824, 224312, 226800, 229288, 231776, 234264, 236560, 239048, 241536, 244024,
246512, 249000, 251488, 253976, 256272, 258760, 261248, 263736, 266224, 268712,
271200, 273688, 275984, 278472, 280960, 283448, 285936, 288424, 290912, 293400,
295696, 298184, 300672, 303160, 305648, 308136, 310624, 313112, 315408, 317896,
320384, 322872, 325360, 327848, 330336, 332824, 335120, 337608, 340096, 342584,
345072, 347560, 350048, 352536, 354832, 357320, 359808, 362296, 364784, 367272,
369760, 372248, 374544, 377032, 379520, 382008, 384496, 386984, 389472, 391960,
394256, 396744, 399232, 401720, 404208, 406696, 409184
bash-4.0#

In the preceding command, the largefiles parameter specifies whether to support

a large file system.
By default, the file system to be created by the HP-UX host system is a small file
system. To be specific, the size of a single file cannot exceed 2 GB. However, in
practical applications, files that are larger than 2 GB are common. Therefore,
enable the file system to support files larger than 2 GB by using the largefiles
parameter.
To check whether a file system created on an LV supports large files, run fstyp.
The command syntax is as follows:
#fstyp -v /dev/vgXX/lvolX

The value of f_flag can be 0 or 16. 16 indicates that a large file system is
supported. If the value is 0, a large file system is not supported.
Step 2 Create mounting points for the file system and mount LVs to the mounting points.
bash-4.0# mkdir -p /test/mnt1
bash-4.0# mkdir -p /test/mnt2
bash-4.0# mount /dev/vg_try/lv_try00 /test/mnt1/
bash-4.0# mount /dev/vg_try/lv_try01 /test/mnt2/

Step 3 View the mounting information.

bash-4.0# bdf
Filesystem kbytes used avail %used Mounted on
/dev/vg00/lvol3 1048576 315152 727752 30% /
/dev/vg00/lvol1 1835008 364368 1459224 20% /stand
/dev/vg00/lvol8 8912896 1419480 7436496 16% /var
/dev/vg00/lvol7 6553600 3037552 3488696 47% /usr
/dev/vg00/lvol4 524288 20952 499536 4% /tmp
/dev/vg00/lvol6 7864320 3071152 4760808 39% /opt
/dev/vg00/lvol5 114688 37872 76352 33% /home
/dev/vg_try/lv_try00
12288 2141 9520 18% /test/mnt1
/dev/vg_try/lv_try01
398869 9 358973 0% /test/mnt2

Two LVs are properly mounted and the I/O operations can be performed properly.
Step 4 To unmount a volume, run the following commands:
bash-4.0# umount /dev/vg_try/lv_try00
bash-4.0# umount /test/mnt2/

Issue 10 (2023-08-02) Copyright © Huawei Technologies Co., Ltd. 75

OceanStor Dorado 6.x & OceanStor 6.x Host
Connectivity Guide for HP-UX 9 Appendix A Volume Management

bash-4.0# bdf
Filesystem kbytes used avail %used Mounted on
/dev/vg00/lvol3 1048576 315296 727608 30% /
/dev/vg00/lvol1 1835008 364368 1459224 20% /stand
/dev/vg00/lvol8 8912896 1419528 7436448 16% /var
/dev/vg00/lvol7 6553600 3037552 3488696 47% /usr
/dev/vg00/lvol4 524288 20952 499536 4% /tmp
/dev/vg00/lvol6 7864320 3071152 4760808 39% /opt
/dev/vg00/lvol5 114688 37872 76352 33% /home
bash-4.0#

----End

Expanding an LV
To expand an existing LV, perform the following steps:

Step 1 Unmount the LV.

bash-4.0# bdf
Filesystem kbytes used avail %used Mounted on
/dev/vg00/lvol3 1048576 315368 727536 30% /
/dev/vg00/lvol1 1835008 364368 1459224 20% /stand
/dev/vg00/lvol8 8912896 1421144 7434840 16% /var
/dev/vg00/lvol7 6553600 3037552 3488696 47% /usr
/dev/vg00/lvol4 524288 20952 499536 4% /tmp
/dev/vg00/lvol6 7864320 3071152 4760808 39% /opt
/dev/vg00/lvol5 114688 37872 76352 33% /home
/dev/vg_try/lv_try00
12288 2141 9520 18% /test/mnt1
bash-4.0# umount /dev/vg_try/lv_try00
bash-4.0# bdf
Filesystem kbytes used avail %used Mounted on
/dev/vg00/lvol3 1048576 314880 728016 30% /
/dev/vg00/lvol1 1835008 364368 1459224 20% /stand
/dev/vg00/lvol8 8912896 1421248 7434736 16% /var
/dev/vg00/lvol7 6553600 3037552 3488696 47% /usr
/dev/vg00/lvol4 524288 20952 499536 4% /tmp
/dev/vg00/lvol6 7864320 3071152 4760808 39% /opt
/dev/vg00/lvol5 114688 37872 76352 33% /home
bash-4.0#

Step 2 Run the LV expansion command. The command syntax is as follows:

lvextend -l xxx lv_path

or
lvextend -L yyy lvpath

In the preceding commands, xxx indicates the logical extent after the expansion,
and yyy indicates the capacity after the expansion.
The following is an example:
bash-4.0# lvextend -l 300 /dev/vg_try/lv_try00
Logical volume "/dev/vg_try/lv_try00" has been successfully extended.
Volume Group configuration for /dev/vg_try has been saved in /etc/lvmconf/vg_try.conf
bash-4.0#
bash-4.0# lvextend -L 800 /dev/vg_try/lv_try01
Logical volume "/dev/vg_try/lv_try01" has been successfully extended.
Volume Group configuration for /dev/vg_try has been saved in /etc/lvmconf/vg_try.conf

Step 3 Expand the file system.

bash-4.0# fstyp /dev/vg_try/rlv_try00
vxfs
bash-4.0# fstyp /dev/vg_try/rlv_try01
hfs
bash-4.0# extendfs -F vxfs /dev/vg_try/rlv_try00

Issue 10 (2023-08-02) Copyright © Huawei Technologies Co., Ltd. 76

OceanStor Dorado 6.x & OceanStor 6.x Host
Connectivity Guide for HP-UX 9 Appendix A Volume Management

bash-4.0# extendfs -F hfs /dev/vg_try/rlv_try01

max number of sectors extendible is 409600.
extend file system /dev/vg_try/rlv_try01 to have 409600 sectors more.
Warning: 80 sector(s) in last cylinder unallocated
extended super-block backups (for fsck -b#) at:
411672, 413968, 416456, 418944, 421432, 423920, 426408, 428896, 431384, 433680,
436168, 438656, 441144, 443632, 446120, 448608, 451096, 453392, 455880, 458368,
460856, 463344, 465832, 468320, 470808, 473104, 475592, 478080, 480568, 483056,
485544, 488032, 490520, 492816, 495304, 497792, 500280, 502768, 505256, 507744,
510232, 512528, 515016, 517504, 519992, 522480, 524968, 527456, 529944, 532240,
534728, 537216, 539704, 542192, 544680, 547168, 549656, 551952, 554440, 556928,
559416, 561904, 564392, 566880, 569368, 571664, 574152, 576640, 579128, 581616,
584104, 586592, 589080, 591376, 593864, 596352, 598840, 601328, 603816, 606304,
608792, 611088, 613576, 616064, 618552, 621040, 623528, 626016, 628504, 630800,
633288, 635776, 638264, 640752, 643240, 645728, 648216, 650512, 653000, 655488,
657976, 660464, 662952, 665440, 667928, 670224, 672712, 675200, 677688, 680176,
682664, 685152, 687640, 689936, 692424, 694912, 697400, 699888, 702376, 704864,
707352, 709648, 712136, 714624, 717112, 719600, 722088, 724576, 727064, 729360,
731848, 734336, 736824, 739312, 741800, 744288, 746776, 749072, 751560, 754048,
756536, 759024, 761512, 764000, 766488, 768784, 771272, 773760, 776248, 778736,
781224, 783712, 786200, 788496, 790984, 793472, 795960, 798448, 800936, 803424,
805912, 808208, 810696, 813184, 815672, 818160,
bash-4.0#

Step 4 Remount the LV.

bash-4.0# mount /dev/vg_try/lv_try00 /test/mnt1
bash-4.0# mount /dev/vg_try/lv_try01 /test/mnt2
bash-4.0# bdf
Filesystem kbytes used avail %used Mounted on
/dev/vg00/lvol3 1048576 314912 727984 30% /
/dev/vg00/lvol1 1835008 364368 1459224 20% /stand
/dev/vg00/lvol8 8912896 1421176 7434816 16% /var
/dev/vg00/lvol7 6553600 3037552 3488696 47% /usr
/dev/vg00/lvol4 524288 20952 499536 4% /tmp
/dev/vg00/lvol6 7864320 3071152 4760808 39% /opt
/dev/vg00/lvol5 114688 37872 76352 33% /home
/dev/vg_try/lv_try00
1228800 2447 1149713 0% /test/mnt1
/dev/vg_try/lv_try01
797845 9 718051 0% /test/mnt2
bash-4.0#

In the preceding example, the LV capacity is updated, indicating that the

expansion is successful.

NOTE

If the file system is an online JFS, you can perform online expansion for the JFS by running
fsadm. For example, run the following command to expand the /test/mnt1 directory to 32
MB:
fsadm -F vxfs -b 32768 /test/mnt1
The b parameter indicates the number of blocks of the new file system. The size of a JFS
block is typically 1 KB.

----End

Activating a VG
After importing a VG, you must activate it before mounting it and performing I/O
operations on it. The command syntax is as follows:
vgchange -a y VG name

The following is an example:

Issue 10 (2023-08-02) Copyright © Huawei Technologies Co., Ltd. 77

OceanStor Dorado 6.x & OceanStor 6.x Host
Connectivity Guide for HP-UX 9 Appendix A Volume Management

bash-4.0# vgchange -a y /dev/vg_tong

Activated volume group.
Volume group "/dev/vg_tong" has been successfully changed.
bash-4.0#

Deactivating a VG
Before exporting a VG, you must deactivate it. The command syntax is as follows:
vgchange –a n VG name

The following is an example:

bash-4.0# vgchange -a n /dev/vg_tong
Volume group "/dev/vg_tong" has been successfully changed.
bash-4.0#

Exporting a VG
VGs must be imported or exported in cluster, data backup, and data restoration
application scenarios.

The command syntax is as follows:

vgexport –p –s –v –m vgname.map VG name

The preceding command saves the VG information in the vgname.map file. Before
exporting a VG, you must deactivate it.

The following is an example:

bash-4.0# vgchange -a n /dev/vg_tong
Volume group "/dev/vg_tong" has been successfully changed.
bash-4.0# vgexport -p -s -v -m vg_tong.map /dev/vg_tong
Beginning the export process on Volume Group "/dev/vg_tong".
/dev/dsk/c14t0d1
/dev/dsk/c13t0d1
vgexport: Preview of vgexport on volume group "/dev/vg_tong" succeeded.
bash-4.0# ls -lrt ./vg_tong.map
-rw-r--r-- 1 root sys 34 Jul 30 14:00 ./vg_tong.map
bash-4.0#

Importing a VG
The command syntax is as follows:
vgimport –s –v –m vgname.map VG name

To import the VG to another host (for example, in a cluster environment), copy

the vgname.map file generated during the previous VG export to this host and
create necessary directories and VG device files for this VG. The created directories
and files must be the same as those in the source host.

The following is an example of importing a VG to the same host where it is

generated:
bash-4.0# vgimport -s -v -m vg_tong.map /dev/vg_tong
Beginning the import process on Volume Group "/dev/vg_tong".
vgimport: Volume group "/dev/vg_tong" already exists in the "/etc/lvmtab" file.
bash-4.0# vgchange -a y /dev/vg_tong
Activated volume group.
Volume group "/dev/vg_tong" has been successfully changed.
bash-4.0#

Issue 10 (2023-08-02) Copyright © Huawei Technologies Co., Ltd. 78

OceanStor Dorado 6.x & OceanStor 6.x Host
Connectivity Guide for HP-UX 9 Appendix A Volume Management

Deleting an LV
The command syntax is as follows:
lvremove lvname

The following is an example:

bash-4.0# bdf
Filesystem kbytes used avail %used Mounted on
/dev/vg00/lvol3 1048576 314880 728016 30% /
/dev/vg00/lvol1 1835008 364368 1459224 20% /stand
/dev/vg00/lvol8 8912896 1421296 7434696 16% /var
/dev/vg00/lvol7 6553600 3037552 3488696 47% /usr
/dev/vg00/lvol4 524288 20952 499536 4% /tmp
/dev/vg00/lvol6 7864320 3071152 4760808 39% /opt
/dev/vg00/lvol5 114688 37872 76352 33% /home
/dev/vg_try/lv_try00
1228800 2447 1149713 0% /test/mnt1
/dev/vg_try/lv_try01
797845 9 718051 0% /test/mnt2
/dev/vg_tong/lv_tong00
398869 9 358973 0% /test/mnt3
bash-4.0#
bash-4.0# umount /dev/vg_tong/lv_tong00
bash-4.0# lvremove /dev/vg_tong/lv_tong00
Current path "/dev/dsk/c13t0d1" is an alternate link, skip.
The logical volume "/dev/vg_tong/lv_tong00" is not empty;
do you really want to delete the logical volume (y/n) : y
Logical volume "/dev/vg_tong/lv_tong00" has been successfully removed.
Volume Group configuration for /dev/vg_tong has been saved in /etc/lvmconf/vg_tong.conf
bash-4.0#

Deleting a VG
The command syntax is as follows:
vgremove vgname

To delete a VG, perform the following steps:

Step 1 Ensure that all LVs have been deleted from the VG.
bash-4.0# vgdisplay -v /dev/vg_tong
--- Volume groups ---
VG Name /dev/vg_tong
VG Write Access read/write
VG Status available
Max LV 255
Cur LV 0
Open LV 0
Max PV 16
Cur PV 1
Act PV 1
Max PE per PV 1791
VGDA 2
PE Size (Mbytes) 4
Total PE 1791
Alloc PE 0
Free PE 1791
Total PVG 0
Total Spare PVs 0
Total Spare PVs in use 0
VG Version 1.0
VG Max Size 114624m
VG Max Extents 28656

--- Physical volumes ---

PV Name /dev/dsk/c14t0d1

Issue 10 (2023-08-02) Copyright © Huawei Technologies Co., Ltd. 79

OceanStor Dorado 6.x & OceanStor 6.x Host
Connectivity Guide for HP-UX 9 Appendix A Volume Management

PV Name /dev/dsk/c13t0d1 Alternate Link

PV Status available
Total PE 1791
Free PE 1791
Autoswitch On
Proactive Polling On
bash-4.0#

Step 2 Keep one PV and delete all other PVs from the VG.
bash-4.0# vgreduce /dev/vg_tong /dev/dsk/c13t0d1
Device file path "/dev/dsk/c13t0d1" is an alternate path.
Volume group "/dev/vg_tong" has been successfully reduced.
Volume Group configuration for /dev/vg_tong has been saved in /etc/lvmconf/vg_tong.conf
bash-4.0# vgdisplay -v /dev/vg_tong
--- Volume groups ---
VG Name /dev/vg_tong
VG Write Access read/write
VG Status available
Max LV 255
Cur LV 0
Open LV 0
Max PV 16
Cur PV 1
Act PV 1
Max PE per PV 1791
VGDA 2
PE Size (Mbytes) 4
Total PE 1791
Alloc PE 0
Free PE 1791
Total PVG 0
Total Spare PVs 0
Total Spare PVs in use 0
VG Version 1.0
VG Max Size 114624m
VG Max Extents 28656

--- Physical volumes ---

PV Name /dev/dsk/c14t0d1
PV Status available
Total PE 1791
Free PE 1791
Autoswitch On
Proactive Polling On
bash-4.0#

Step 3 Delete the VG.

bash-4.0# vgremove /dev/vg_tong
Volume group "/dev/vg_tong" has been successfully removed.
bash-4.0#

----End

Deleting a PV
The command syntax is as follows:
pvremove raw device name

The following is an example:

bash-4.0# pvremove /dev/rdsk/c13t0d1
The physical volume associated with "/dev/rdsk/c13t0d1" has been removed.
bash-4.0# pvremove /dev/rdsk/c14t0d1
pvremove: Physical Volume "/dev/rdsk/c14t0d1" contains no LVM information
bash-4.0#
bash-4.0# pvdisplay -l /dev/dsk/c13t0d1
/dev/dsk/c13t0d1:LVM_Disk=no

Issue 10 (2023-08-02) Copyright © Huawei Technologies Co., Ltd. 80

OceanStor Dorado 6.x & OceanStor 6.x Host
Connectivity Guide for HP-UX 9 Appendix A Volume Management

bash-4.0# pvdisplay -l /dev/dsk/c14t0d1

/dev/dsk/c14t0d1:LVM_Disk=no
bash-4.0#

9.2 VxVM

9.2.1 Overview
VxVM is a storage management subsystem that enables you to manage physical
disks as logical devices.

Application programs and operating systems consider a VxVM volume as a

physical disk where file systems, databases, and other entrusted data objects can
be configured.

VxVM provides simple functions of managing online disks for the computation
environment and storage area networks (SANs). It has the following advantages:

● Supports RAID.
● Provides functions that improve error tolerance and enable quick disk failure
recovery.
● Provides an LV management layer to enable cross-disk management and
remove physical restrictions of disk devices.
● Provides tools that improve performance and ensure data availability and
integrity.
● Enables dynamic disk storage configuration when the system is active.

9.2.2 Installation
VxVM is not for free and not come pre-installed in an operating system.

Pre-installation Check
Before installation, run the following command to check whether VxVM has been
installed:
swlist|grep –i vxvm

No information will be displayed if it is not installed.

Installation Procedure
To install VxVM, perform the following steps:

Step 1 Upload the VxVM installation package to a directory in the UP-UX system.

Step 2 Decompress the package.

If the file name extension of the package is .gz, run gunzip filename.gz.

If the file name extension of the package is .tar, run tar -xvf filename.tar.

Set filename as required.

Issue 10 (2023-08-02) Copyright © Huawei Technologies Co., Ltd. 81

OceanStor Dorado 6.x & OceanStor 6.x Host
Connectivity Guide for HP-UX 9 Appendix A Volume Management

Step 3 In the directory containing the package, run chmod +x installer to grant
permissions to the installer file.
Step 4 Run ./installer to install VxVM.

----End

9.2.3 Common Configuration Commands

Loading Disks
After you run the LUN scanning command, the HP-UX system identifies the LUNs
mapped by the host.
VxVM does not manage the LUNs directly. Instead, disks are loaded first before
being managed by VxVM. The command syntax is as follows:
vxdisk scandisks

Displaying Managed Disks

Run the vxdisk list command to display disks managed by VxVM. The following is
an example:
bash-4.0# vxdisk list
DEVICE TYPE DISK GROUP STATUS
disk_0s2 auto:LVM - - LVM
disk_1s2 auto - - error
huawei-xsg10_0 auto:none - - online invalid
huawei-xsg10_1 auto:none - - online invalid
huawei-xsg10_2 auto:FS_wholedisk - - FS_wholedisk
huawei-xsg10_3 auto:FS_wholedisk - - FS_wholedisk
huawei-xsg10_4 auto:none - - online invalid

Initializing Disks
Disks that were just managed are not in online state because they have not been
initialized. As a result, they cannot be used. Therefore, you must run the
vxdisksetup -i disk name command to initialize them first. The status of
successfully initialized disks is online. The following is an example:
bash-4.0# /opt/VRTS/bin/vxdisksetup -i huawei-xsg10_0
bash-4.0# vxdisk list
DEVICE TYPE DISK GROUP STATUS
disk_0s2 auto:LVM - - LVM
disk_1s2 auto - - error
huawei-xsg10_0 auto:cdsdisk - - online
huawei-xsg10_1 auto:none - - online invalid
huawei-xsg10_2 auto:FS_wholedisk - - FS_wholedisk
huawei-xsg10_3 auto:FS_wholedisk - - FS_wholedisk
huawei-xsg10_4 auto:none - - online invalid
bash-4.0#

Creating a Disk Group

You can run the vxdg init DG name disk name command to create a disk group
(DG) from initialized disks. The following is an example:
bash-4.0# vxdg init dg1 huawei-xsg10_0 huawei-xsg10_1
bash-4.0# vxdisk list
DEVICE TYPE DISK GROUP STATUS

Issue 10 (2023-08-02) Copyright © Huawei Technologies Co., Ltd. 82

OceanStor Dorado 6.x & OceanStor 6.x Host
Connectivity Guide for HP-UX 9 Appendix A Volume Management

disk_0s2 auto:LVM - - LVM

disk_1s2 auto - - error
huawei-xsg10_0 auto:cdsdisk huawei-xsg10_0 dg1 online
huawei-xsg10_1 auto:cdsdisk huawei-xsg10_1 dg1 online
huawei-xsg10_2 auto:FS_wholedisk - - FS_wholedisk
huawei-xsg10_3 auto:FS_wholedisk - - FS_wholedisk
huawei-xsg10_4 auto:none - - online invalid
bash-4.0#

Creating a Volume
You can run the vxassist -g DG name make volume name capacity command to
create a volume in a created DG. The following is an example:
bash-4.0# vxassist -g dg1 make vol2 1g
bash-4.0# vxprint -g dg1 -t vol2
V NAME RVG/VSET/CO KSTATE STATE LENGTH READPOL PREFPLEX UTYPE

v vol2 - ENABLED ACTIVE 1048576 SELECT - fsgen

bash-4.0#

Creating a File System

A created volume cannot be used unless it is mounted to a file system. The syntax
of the file system creation command is the same here as that in LVM. The
difference is the device name.
● To create an OS native VxFS, run the following command:
bash-4.0# newfs -F vxfs -o largefiles /dev/vx/rdsk/dg1/vol2
version 7 layout
1048576 sectors, 1048576 blocks of size 1024, log size 16384 blocks
largefiles supported
bash-4.0#

● To create a third-party Veritas VxFS, run the following command:

bash-4.0# mkfs -F vxfs /dev/vx/rdsk/dg1/vol2

Mounting a Volume
You can mount a created volume to a directory.
● To mount a volume to an OS native VxFS, run the following command:
mount /dev/vx/dsk/<disk group>/<volume name> <mount directory>

● To mount a volume to a third-party Veritas VxFS, run the following command:

mount -F vxfs /dev/vx/dsk/<disk group>/<volume name> <mount directory>

Disabling a Volume
This command makes a volume unavailable to a user and changes the volume
status from ENABLED or DETACHED to DISABLED. The command syntax is as
follows:
vxvol -g DG name stop volume name

The following is an example:

bash-4.0# vxvol -g dg1 stop vol2
bash-4.0# vxprint -g dg1 -t vol2
V NAME RVG/VSET/CO KSTATE STATE LENGTH READPOL PREFPLEX UTYPE

v vol2 - DISABLED CLEAN 1048576 SELECT - fsgen

bash-4.0#

Issue 10 (2023-08-02) Copyright © Huawei Technologies Co., Ltd. 83

OceanStor Dorado 6.x & OceanStor 6.x Host
Connectivity Guide for HP-UX 9 Appendix A Volume Management

Enabling a Volume
This command makes a volume available to a user and changes the volume status
from DISABLED to ENABLED or DETACHED.

The command syntax is as follows:

vxvol -g DG name start volume name

The following is an example:

bash-4.0# vxvol -g dg1 start vol2
bash-4.0# vxprint -g dg1 -t vol2
V NAME RVG/VSET/CO KSTATE STATE LENGTH READPOL PREFPLEX UTYPE

v vol2 - ENABLED ACTIVE 1048576 SELECT - fsgen

bash-4.0#

Deleting a Volume
The command syntax is as follows:
vxedit -g DG name -rf rm volume name

The following is an example:

bash-4.0# vxedit -g dg1 -rf rm vol2
bash-4.0# vxprint
Disk group: dg1
TY NAME ASSOC KSTATE LENGTH PLOFFS STATE TUTIL0 PUTIL0
dg dg1 dg1 - - - - - -
dm huawei-xsg10_0 huawei-xsg10_0 - 6254464 - - - -
dm huawei-xsg10_1 huawei-xsg10_1 - 7303040 - - - -
bash-4.0#

Exporting a DG
DGs must be imported or exported in cluster, data backup, and data restoration
application scenarios. Before exporting a DG, you must stop all volumes on the
DG. Run the vxdg deport DG name command to export the DG. The following is
an example:
bash-4.0# vxvol -g dg1 stop vol2
bash-4.0# vxdg deport dg1
bash-4.0# vxdg list
NAME STATE ID
bash-4.0#

Importing a DG
The command syntax is as follows:
vxdg import DG name

After importing a DG, you must activate it before using it. The following is an
example:
bash-4.0#vxdg import dg1
bash-4.0#vxdg list
NAME STATE ID
dg1 enabled,cds 1330044217.14.ibm130
bash-4.0#vxvol -g dg1 startall

Issue 10 (2023-08-02) Copyright © Huawei Technologies Co., Ltd. 84

OceanStor Dorado 6.x & OceanStor 6.x Host
Connectivity Guide for HP-UX 9 Appendix A Volume Management

Adding a Disk to a DG
You can add disks to a DG when its capacity is insufficient. The command syntax is
as follows:
vxdg -g DG name adddisk disk name

The following is an example:

bash-4.0# vxdg -g dg1 adddisk huawei-xsg10_1
bash-4.0# vxdisk list
DEVICE TYPE DISK GROUP STATUS
disk_0s2 auto:LVM - - LVM
disk_1s2 auto - - error
huawei-xsg10_0 auto:cdsdisk huawei-xsg10_0 dg1 online
huawei-xsg10_1 auto:cdsdisk huawei-xsg10_1 dg1 online
huawei-xsg10_2 auto:FS_wholedisk - - FS_wholedisk
huawei-xsg10_3 auto:FS_wholedisk - - FS_wholedisk
huawei-xsg10_4 auto:none - - online invalid
bash-4.0#

Removing a Disk from a DG

The command syntax is as follows:
vxdg -g DG name rmdisk disk name

The following is an example:

bash-4.0# vxdg -g dg1 rmdisk huawei-xsg10_1
bash-4.0# vxdisk list
DEVICE TYPE DISK GROUP STATUS
disk_0s2 auto:LVM - - LVM
disk_1s2 auto - - error
huawei-xsg10_0 auto:cdsdisk huawei-xsg10_0 dg1 online
huawei-xsg10_1 auto:cdsdisk - - online
huawei-xsg10_2 auto:FS_wholedisk - - FS_wholedisk
huawei-xsg10_3 auto:FS_wholedisk - - FS_wholedisk
huawei-xsg10_4 auto:none - - online invalid

Issue 10 (2023-08-02) Copyright © Huawei Technologies Co., Ltd. 85

OceanStor Dorado 6.x & OceanStor 6.x Host
Connectivity Guide for HP-UX 10 Introduction to High-Availability Technologies

10 Introduction to High-Availability
Technologies

10.1 MC/SG
10.2 Veritas VCS

10.1 MC/SG

10.1.1 Overview
With ever-increasing service requirements, mission-critical applications must be
always available and the system must be tolerant of errors. However, systems with
error tolerance capabilities are costly. Therefore, the error tolerance capability
needs to be provided by applications at low cost.

A high availability (HA) solution ensures that a user can use applications and data
even if errors occur in any component in the system. Scheduled and unscheduled
system suspension is eliminated or insensible by eliminating single points of
failure (SPOFs).

The Multi-Computer/ServiceGuard (MC/SG) software is a piece of HA cluster

software on the HP-UX system. It eliminates SPOFs using redundancy
configurations and therefore ensures continuous HA, safety, and reliability of the
entire system.

MC/SG has the following features:

● High reliability
● Balanced workload
● Data integrity protection
● Integrated MC/SG cluster and network node management programs

As of the release of this document, the latest MC/SG version issued with the HP-
UX is A.11.20.

Issue 10 (2023-08-02) Copyright © Huawei Technologies Co., Ltd. 86

OceanStor Dorado 6.x & OceanStor 6.x Host
Connectivity Guide for HP-UX 10 Introduction to High-Availability Technologies

10.1.2 Working Principles

The Multi-Computer/ServiceGuard (MC/SG) software consists of three parts: the
Cluster Manager, the Package Manager, and the Network Manager.

10.1.2.1 Cluster Manager

A cluster consists of nodes, to be specific, master and backup nodes.

MC/SG manages nodes to form a cluster. The master node is called the Cluster
Coordinator. It receives heartbeat messages from other nodes to identify their
states.

If a node becomes abnormal, MC/SG forms a new cluster without this abnormal
node. The configuration information about this new cluster is transmitted to the
Package Manager to prevent application systems from running on the abnormal
node.

10.1.2.2 Package Manager

Packages refer to background processes and services required for application
running. The Package Manager's functions are as follows:

● Determines the time and node for running, suspending, and migrating a
package.
● Executes a user-defined control text file to properly suspend and run a
package.

10.1.2.3 Network Manager

A static IP address must be configured for the currently active network adapter
(primary network adapter) on each node. The static IP address can be transmitted
to the backup network adapter but not to another node. Therefore, do not
configure an IP address for the backup network adapter.

In addition, a unique floating IP address is configured for each package. The

floating IP address of each node in a cluster is the same and is in the same
network segment as the primary static IP address. When a package is initiated, the
floating IP address is assigned to the primary network adapter. If the primary
network adapter becomes faulty, the static IP address and the package address of
the primary network adapter are switched over to the backup network adapter.
Therefore, applications that access packages do not need to be notified of the
static IP address or host name of the current node.

10.1.3 Installation and Configuration

For details about installation and configuration of MC/SG, click the following HP-
UX official link:

http://h20565.www2.hpe.com/portal/site/hpsc/template.PAGE/public/psi/
manualsResults/?
sp4ts.oid=4162060&spf_p.tpst=psiContentResults&spf_p.prp_psiContentResults
=wsrp-navigationalState%3Daction%253Dmanualslist%257Ccontentid
%253DUser-Guide-%252528how-to-use%252529%257Clang

Issue 10 (2023-08-02) Copyright © Huawei Technologies Co., Ltd. 87

OceanStor Dorado 6.x & OceanStor 6.x Host
Connectivity Guide for HP-UX 10 Introduction to High-Availability Technologies

%253Den&javax.portlet.begCacheTok=com.vignette.cachetoken&javax.portlet.
endCacheTok=com.vignette.cachetoken

10.1.4 Cluster Maintenance

10.1.4.1 Common Maintenance Commands

Enabling a Cluster
The command syntax is as follows:
# cmruncl -v
# cmruncl -v -n nodename1 -n nodename2

Disabling a Cluster
The command syntax is as follows:
# cmhaltcl -f -v

To disable the cluster service on one node, run the following command:
# cmhaltnode -f -v nodename1

Checking the Cluster Status

The command syntax is as follows:
cmviewcl -v

Switching a Package from One Node to Another

To switch a package from one node to another, perform the following steps:

Step 1 Disable the package service on one node:

cmhaltpkg -n nodename1 pkg1

Step 2 Enable the package service on another:

cmrunpkg -n nodename2 pkg1cmmodpkg -e pkg1

----End

10.1.4.2 Cluster Log Analysis

If a cluster is not running properly, you can use logs to help locate the cause.
Logs related to MC/SG are as follows:
● /var/adm/syslog/syslog.log
This log provides the following information:
– Executed commands and execution results
– Cluster events that may or may not be errors
– Cluster status information
● /etc/cmcluster/pkg1/pkg1.cntl.log
This log provides information about cluster packages.

Issue 10 (2023-08-02) Copyright © Huawei Technologies Co., Ltd. 88

OceanStor Dorado 6.x & OceanStor 6.x Host
Connectivity Guide for HP-UX 10 Introduction to High-Availability Technologies

● /var/opt/cmom/cmomd.log
This log provides information recorded by cmomd, the cluster object manager
daemon. You can run the cmreadlog command to view the information. The
command syntax is as follows:
cmreadlog /var/opt/cmom/cmomd.log

The cmomd log file includes information about programs that request data from
the object manager, such as data type and timestamp.

10.2 Veritas VCS

10.2.1 Overview
Veritas Cluster Server (VCS) can connect multiple independent systems to a
management framework to improve availability. Each system (or node) runs its
own operating system and collaborates at the software level to form a cluster. The
VCS combines common hardware with intelligent software to provide failover and
control for applications. If a node or a monitored application becomes faulty,
other nodes perform predefined operations to take over services and start these
services in other locations in the cluster.

10.2.2 Version Compatibility

The VCS software must meet the compatibility requirements of the host operating
system. VCS software of a specific version may not be suitable for all versions of
HP-UX.
For details about the compatibility between VCS and HP-UX, see the Veritas
Enterprise Products and Platforms Matrix.

10.2.3 Installation and Configuration

For details on how to install and configure Veritas products, visit its official
website: https://sort.veritas.com/documents.
For 6.0.x and earlier versions, select Storage Foundation and High Availability
for Product to obtain the installation and configuration guide of the
corresponding version.

Issue 10 (2023-08-02) Copyright © Huawei Technologies Co., Ltd. 89