Upload
duongcong
View
228
Download
4
Embed Size (px)
Citation preview
Technical White Paper
HUAWEI SAN Storage Host Connectivity Guide for Solaris
OceanStor Storage Solaris
Huawei Technologies Co., Ltd. 2017-08-15
Issue (2017-07-19) Huawei Proprietary and Confidential
Copyright © Huawei Technologies Co., Ltd.
i
Copyright © Huawei Technologies Co., Ltd. 2017. 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: http://e.huawei.com
HUAWEI SAN Storage Host Connectivity Guide for Solaris About This Document
Issue (2017-07-19) Huawei Proprietary and Confidential
Copyright © Huawei Technologies Co., Ltd.
ii
About This Document
Overview
This document details the configuration methods and precautions for connecting Huawei SAN
storage devices to Solaris hosts.
Intended Audience
This document is intended for:
Huawei technical support engineers
Technical engineers of Huawei's partners
Conventions
Symbol Conventions
The symbols that may be found in this document are defined as follows:
Symbol Description
Indicates a hazard with a high level of risk, which if not
avoided, will result in death or serious injury.
Indicates a hazard with a medium or 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 degradation, or unexpected results.
Indicates a tip that may help you solve a problem or save time.
Provides additional information to emphasize or supplement
important points of the main text.
HUAWEI SAN Storage Host Connectivity Guide for Solaris About This Document
Issue (2017-07-19) Huawei Proprietary and Confidential
Copyright © Huawei Technologies Co., Ltd.
iii
General Conventions
Convention Description
Times New Roman Normal paragraphs are in Times New Roman.
Boldface Names of files, directories, folders, and users are in
boldface. For example, log in as user root.
Italic Book titles are in italics.
Courier New Examples of information displayed on the screen are in
Courier New.
Command Conventions
Format Description
Boldface The keywords of a command line are in boldface.
Italic Command arguments are in italics.
HUAWEI SAN Storage Host Connectivity Guide for Solaris About This Document
Issue (2017-07-19) Huawei Proprietary and Confidential
Copyright © Huawei Technologies Co., Ltd.
iv
Contents
About This Document .................................................................................................................... ii
1 Solaris Operating System ............................................................................................................ 1
1.1 Introduction to Solaris .................................................................................................................................................. 1
1.2 File Systems in Solaris .................................................................................................................................................. 1
1.3 Directory Structure in Solaris ....................................................................................................................................... 2
1.4 Common Management Tools and Commands .............................................................................................................. 3
1.4.1 Management Tool ...................................................................................................................................................... 3
1.4.2 Management Commands ........................................................................................................................................... 3
1.5 Version Information ...................................................................................................................................................... 4
1.5.1 Querying the Current Version .................................................................................................................................... 4
1.5.2 Querying the Version of Software .............................................................................................................................. 5
1.6 Interoperability Between Solaris and Storage Systems................................................................................................. 5
2 Network Planning ......................................................................................................................... 7
2.2 Non-HyperMetro Network ........................................................................................................................................... 7
2.2.1 Fibre Channel Networking Diagram .......................................................................................................................... 7
2.2.2 iSCSI Network Diagram .......................................................................................................................................... 10
2.3 HyperMetro Network .................................................................................................................................................. 12
2.3.1 Fibre Channel Networking Diagram ........................................................................................................................ 12
3 Configuration Preparations (Hosts) ........................................................................................ 15
3.1 Identifying HBAs........................................................................................................................................................ 15
3.2 Querying HBA Properties ........................................................................................................................................... 16
3.2.1 Solaris 8 and 9 ......................................................................................................................................................... 16
3.2.2 Solaris 10 and 11 ...................................................................................................................................................... 18
4 Preparations Before Configuration (on a Storage System) ................................................. 19
5 Configuring Switches ................................................................................................................. 20
5.1 Fibre Channel Switch ................................................................................................................................................. 20
5.1.1 Querying the Switch Model and Version ................................................................................................................. 20
5.1.2 Configuring Zones ................................................................................................................................................... 23
5.1.3 Precautions ............................................................................................................................................................... 26
5.2 Ethernet Switch ........................................................................................................................................................... 27
5.2.1 Configuring VLANs ................................................................................................................................................ 27
HUAWEI SAN Storage Host Connectivity Guide for Solaris About This Document
Issue (2017-07-19) Huawei Proprietary and Confidential
Copyright © Huawei Technologies Co., Ltd.
v
5.2.2 Binding Ports ........................................................................................................................................................... 27
5.3 FCoE Switch ............................................................................................................................................................... 29
5.3.2 Command Introduction ............................................................................................................................................ 29
5.3.3 Creating a VSAN ..................................................................................................................................................... 32
5.3.4 Creating a VLAN ..................................................................................................................................................... 33
5.3.5 Configuring a Port and Adding It to the VLAN ....................................................................................................... 34
5.3.6 Creating a Zone and Adding the Port to It ............................................................................................................... 35
5.3.7 Creating a Zoneset and Adding the Created Zone to It ............................................................................................ 36
6 Establishing Fibre Channel Connections ............................................................................... 38
6.1 Checking Topology Modes ......................................................................................................................................... 38
6.1.1 OceanStor T V1 Series Storage System ................................................................................................................... 38
6.1.2 OceanStor 18000/T V2 /V3/Dorado V3 Series Enterprise Storage System ............................................................. 39
6.2 Adding Initiators ......................................................................................................................................................... 39
6.3 Establishing Connections ............................................................................................................................................ 40
7 Establishing iSCSI Connections .............................................................................................. 41
7.1 Checking and Installing the iSCSI Software Package ................................................................................................ 41
7.1.1 Checking the iSCSI Software Package .................................................................................................................... 41
7.1.2 Installing the iSCSI Software Package .................................................................................................................... 41
7.2 Configuring Service IP Addresses on Storage ............................................................................................................ 42
7.2.1 OceanStor T Series Storage System ......................................................................................................................... 43
7.2.2 OceanStor 18000/T V2 /V3/Dorado V3 Series Enterprise Storage System ............................................................. 47
7.3 Configuring IP Addresses on Hosts ............................................................................................................................ 48
7.3.1 Solaris 10 and Earlier ............................................................................................................................................... 48
7.3.2 Solaris 11 and Later ................................................................................................................................................. 50
7.4 Configuring Initiators on Hosts .................................................................................................................................. 51
7.5 Configuring Services on Hosts ................................................................................................................................... 53
7.6 Establishing Connections ............................................................................................................................................ 55
8 Mapping and Using LUNs ........................................................................................................ 56
8.1 Mapping LUNs to Hosts ............................................................................................................................................. 56
8.2 Scanning for LUNs on Hosts ...................................................................................................................................... 56
8.3 Using LUNs on Hosts ................................................................................................................................................. 59
8.3.1 SPARC ..................................................................................................................................................................... 59
8.3.2 x86 ........................................................................................................................................................................... 60
8.4 Troubleshooting .......................................................................................................................................................... 62
8.4.1 Symptom .................................................................................................................................................................. 62
8.4.2 Root Cause Analysis ................................................................................................................................................ 62
8.4.3 Solution .................................................................................................................................................................... 62
9 Multipathing Management ....................................................................................................... 64
9.1 Overview .................................................................................................................................................................... 64
9.2 Functions and Features of STMS ................................................................................................................................ 64
HUAWEI SAN Storage Host Connectivity Guide for Solaris About This Document
Issue (2017-07-19) Huawei Proprietary and Confidential
Copyright © Huawei Technologies Co., Ltd.
vi
9.2.1 Functions ................................................................................................................................................................. 64
9.2.2 Load Balancing Policies .......................................................................................................................................... 64
9.3 Operating Environment Requirements ....................................................................................................................... 65
9.4 Installing Multipathing Software ................................................................................................................................ 65
9.5 Configuring and Enabling Multipathing Function ...................................................................................................... 65
9.5.1 Multipathing Configuration for New-Version HUAWEI Storage ............................................................................ 65
9.5.2 Multipathing Configuration for Old-Version HUAWEI Storage ............................................................................. 84
9.6 Management Commands Related to Multipathing ..................................................................................................... 85
9.6.1 Viewing the Relationship Between Virtual LUNs and Original LUNs .................................................................... 85
9.6.2 Viewing Information About Paths to Virtual LUNs ................................................................................................. 86
9.6.3 Viewing Information About Multipathing Support .................................................................................................. 86
9.6.4 Viewing Attributes of Specific Initiator ................................................................................................................... 87
9.6.5 Viewing Information About Specific LUNs ............................................................................................................ 88
9.6.6 Viewing Information About LUNs on Specific Ports .............................................................................................. 90
9.7 Troubleshooting .......................................................................................................................................................... 91
9.7.1 Symptom .................................................................................................................................................................. 91
9.7.2 Root Cause Analysis ................................................................................................................................................ 91
10 Volume Management ............................................................................................................... 94
10.1 SVM.......................................................................................................................................................................... 94
10.1.1 Overview ............................................................................................................................................................... 94
10.1.2 Component Overview ............................................................................................................................................ 95
10.1.3 Installing SVM ....................................................................................................................................................... 98
10.1.4 Common Configuration Commands ...................................................................................................................... 98
10.2 VxVM ..................................................................................................................................................................... 109
10.2.1 Overview ............................................................................................................................................................. 109
10.2.2 Installation ........................................................................................................................................................... 109
10.2.3 Common Configuration Commands .................................................................................................................... 110
11 High-Availability Technologies........................................................................................... 115
11.1 Overview ................................................................................................................................................................. 115
11.2 Key Concepts .......................................................................................................................................................... 115
11.2.1 Cluster Nodes ....................................................................................................................................................... 115
11.2.2 Cluster Interconnection ........................................................................................................................................ 116
11.2.3 Cluster Membership ............................................................................................................................................. 116
11.2.4 Cluster Configuration Repository ........................................................................................................................ 116
11.2.5 Fault Monitors ...................................................................................................................................................... 117
11.2.6 Quorum Devices .................................................................................................................................................. 118
11.2.7 Data Services ....................................................................................................................................................... 120
11.3 Installation and Configuration ................................................................................................................................ 121
11.4 Cluster Maintenance ............................................................................................................................................... 122
11.4.1 Common Maintenance Commands ...................................................................................................................... 122
11.4.2 Cluster Messages ................................................................................................................................................. 122
HUAWEI SAN Storage Host Connectivity Guide for Solaris About This Document
Issue (2017-07-19) Huawei Proprietary and Confidential
Copyright © Huawei Technologies Co., Ltd.
vii
12 Acronyms and Abbreviations ............................................................................................... 123
HUAWEI SAN Storage Host Connectivity Guide for Solaris About This Document
Issue (2017-07-19) Huawei Proprietary and Confidential
Copyright © Huawei Technologies Co., Ltd.
viii
Figures
Figure 1-1 Functions of the SMC menu tool ......................................................................................................... 3
Figure 1-2 Interoperability query page .................................................................................................................. 6
Figure 1-3 OceanStor Interoperability Navigator ............................................................................................. 6
Figure 2-2 Fibre Channel multi-path directly connected network diagram (dual-controller) ................................ 8
Figure 2-3 Fibre Channel multi-path directly connected network diagram (four-controller) ................................ 8
Figure 2-4 Fibre Channel multi-path switch-connected network diagram (dual-controller) ................................. 9
Figure 2-5 Fibre Channel multi-path switch-connected network diagram (four-controller) ................................. 9
Figure 2-6 iSCSI multi-path directly connected network diagram (dual-controller) ........................................... 10
Figure 2-7 iSCSI multi-path directly connected network diagram (four-controller) ........................................... 10
Figure 2-8 iSCSI multi-path switch-connected network diagram (dual-controller) ............................................ 11
Figure 2-9 iSCSI multi-path switch-connected network diagram (four-controller) ............................................ 12
Figure 2-10 Fibre Channel multi-path switch-connected networking diagram (dual-controller) ........................ 13
Figure 2-11 Fibre Channel multi-path switch-connected networking diagram (four-controller) ........................ 14
Figure 5-1 Switch information ............................................................................................................................ 21
Figure 5-2 Switch port indicator status................................................................................................................ 23
Figure 5-3 Zone tab page ..................................................................................................................................... 24
Figure 5-4 Zone configuration............................................................................................................................. 24
Figure 5-5 Zone Config tab page ......................................................................................................................... 25
Figure 5-6 Name Server page .............................................................................................................................. 26
Figure 5-7 Process for configuring an FCoE switch ........................................................................................... 29
Figure 6-1 Fibre Channel port details .................................................................................................................. 38
Figure 6-2 Fibre Channel port details .................................................................................................................. 39
Figure 7-1 Modifying IPv4 addresses ................................................................................................................. 43
Figure 7-2 Initiator CHAP configuration............................................................................................................. 44
Figure 7-3 CHAP Configuration dialog box........................................................................................................ 45
Figure 7-4 Create CHAP dialog box ................................................................................................................... 45
HUAWEI SAN Storage Host Connectivity Guide for Solaris About This Document
Issue (2017-07-19) Huawei Proprietary and Confidential
Copyright © Huawei Technologies Co., Ltd.
ix
Figure 7-5 Assigning the CHAP account to the initiator ..................................................................................... 46
Figure 7-6 Setting CHAP status .......................................................................................................................... 46
Figure 7-7 Enabling CHAP ................................................................................................................................. 47
Figure 7-8 Initiator status after CHAP is enabled ................................................................................................ 47
Figure 9-1 Going to the host configuration page ................................................................................................. 71
Figure 9-2 Selecting an initiator of which information you want to modify ....................................................... 71
Figure 9-3 Modifying initiator information ......................................................................................................... 72
Figure 9-4 LUN information in Solaris ............................................................................................................... 76
Figure 9-5 Enabling ALUA for T series V100R005/Dorado2100/Dorado5100/Dorado2100 G2 ....................... 84
Figure 9-6 Enabling ALUA for T Series V200R002/18000 Series/V3 Series ..................................................... 85
HUAWEI SAN Storage Host Connectivity Guide for Solaris About This Document
Issue (2017-07-19) Huawei Proprietary and Confidential
Copyright © Huawei Technologies Co., Ltd.
x
Tables
Table 1-1 Common directories .............................................................................................................................. 2
Table 1-2 Common Solaris commands .................................................................................................................. 3
Table 2-1 Networking modes ................................................................................................................................. 7
Table 5-1 Mapping between switch types and names .......................................................................................... 21
Table 5-2 Comparison of link aggregation modes ............................................................................................... 28
Table 9-1 Configuration methods and application scenarios of the typical working modes ................................ 66
Table 9-2 HUAWEI storage's support for ALUA ................................................................................................ 67
Table 9-3 Initiator parameter description ............................................................................................................. 68
Table 9-4 Multipathing configuration on non-HyperMetro Huawei storage interconnected with Solaris ........... 72
Table 9-5 Multipathing configuration on HyperMetro Huawei storage interconnected with Solaris .................. 73
Table 10-1 SVM component functions ................................................................................................................ 95
Table 10-2 Common maintenance commands for managing state database replicas .......................................... 98
Table 10-3 Common maintenance commands for three kinds of volumes .......................................................... 99
Table 10-4 Common maintenance commands for soft partitions ...................................................................... 103
Table 10-5 Common maintenance commands for hot spare pools .................................................................... 103
Table 10-6 Common maintenance commands for disk sets ............................................................................... 106
Table 11-1 Cluster quorum, split brain, and amnesia ......................................................................................... 118
HUAWEI SAN Storage Host Connectivity Guide for Solaris 1 Solaris Operating System
Issue (2017-07-19) Huawei Proprietary and Confidential
Copyright © Huawei Technologies Co., Ltd.
1
1 Solaris Operating System
1.1 Introduction to Solaris
As a computer operating system developed by Sun Microsystems, Solaris is derived from
Unix operating systems. It is compatible with SPARC- and x86-based systems.
1.2 File Systems in Solaris
Solaris supports the following three types of file systems:
Network File System
Network File System (NFS) indicates a file system based on a network.
Virtual File System (VFS)
VFS is also called pseudo file system. Most virtual file systems are in-memory file
systems, which consist of the following:
− Temporary File System (TMPFS)
TMPFS indicates a file system that reads/writes data in local memory. The default
application in Solaris is the /tmp directory.
− Loopback File System (LOFS)
A LOFS can be used to create a new, virtual and original file system and access files
using another path name.
− Process File System (PROCFS)
PROCFS that resides in memory is displayed as a /proc directory. The list of active
process numbers and ps commands use the information contained in the /proc
directory. Debuggers and other development tools may also access IP address space
of these processes by invoking a PROCFS.
− Cache File System (CacheFS)
CacheFS improves the data read rate of NFS and CD-ROM and caches the data read.
− SWAP File System (SWAPFS)
SWAPFS indicates the file system used by the system kernel when a swap area is
additionally established by running mkfile and swap commands.
Disk-based File System
Including:
HUAWEI SAN Storage Host Connectivity Guide for Solaris 1 Solaris Operating System
Issue (2017-07-19) Huawei Proprietary and Confidential
Copyright © Huawei Technologies Co., Ltd.
2
− Unix File System (UFS)
Traditional BSD Fast File System–based UFS is the default Solaris file system. The
log recording function of UFS is enabled by default.
− High Sierra File System (HSFS)
HSFS is used as a read-only file system of CD-ROM.
− PC File System (PCFS)
PCFS can read/write data stored on disks in DOS formats, such as FAT32.
− Universal Disk Format (UDF)
UDF indicates a DVD file system.
To view the file system type of a volume, use the following method:
bash-3.2# fstyp /dev/dsk/c1t0d0s0
ufs
bash-3.2#
From the preceding command output, it can be found that the file system type of the
/dev/dsk/c1t0d0s0 volume is ufs.
1.3 Directory Structure in Solaris
Solaris consists of important system directories and necessary functional files of operating
systems. Table 1-1 lists common directories of Solaris.
Table 1-1 Common directories
Directory Description
/ Covers the space used for naming all file systems.
/devices Indicates a root directory for physical device names.
/etc/mnttab Describes the mount state of the current system.
/proc Describes information about current running system processes.
/tmp Indicates a temporary file directory. It can be automatically cleared when
a system is started.
/var/run Contains lock files, specified files, and reference files for multiple
processes and services.
/usr Contains programs, scripts, and library files used by all system users.
/sbin Contains executable single-user bin, which is used for manual system
troubleshooting and boot.
HUAWEI SAN Storage Host Connectivity Guide for Solaris 1 Solaris Operating System
Issue (2017-07-19) Huawei Proprietary and Confidential
Copyright © Huawei Technologies Co., Ltd.
3
1.4 Common Management Tools and Commands
When Solaris hosts are connected to storage systems, the host system management tool and
commands may be used.
1.4.1 Management Tool
Solaris provides a powerful management tool named Solaris Management Console (SMC)
that offers well-developed online help to help users complete system management tasks.
Figure 1-1 shows the SMC menu tool that covers almost all Solaris functions.
Figure 1-1 Functions of the SMC menu tool
1.4.2 Management Commands
Table 1-2 describes management commands commonly used in the scenario where Solaris
hosts are connected to storage systems.
Table 1-2 Common Solaris commands
Command Function
cfgadm Manages configuration.
df -k Queries the file system size and usage.
devfsadm Manages /dev devices.
fcinfo hba-port Queries information about a Fibre Channel host bus
adapter (HBA).
HUAWEI SAN Storage Host Connectivity Guide for Solaris 1 Solaris Operating System
Issue (2017-07-19) Huawei Proprietary and Confidential
Copyright © Huawei Technologies Co., Ltd.
4
Command Function
format Views information about system disks on a host.
ifconfig Configures network interface parameters.
iscsiadm Manages iSCSI.
luxadm -e port Views the connection status of Fibre Channel ports on an
operating system.
mount Mounts file systems.
mpathadm Manages STMS multipathing.
pkgadd Installs patches.
pkginfo Queries patch information.
pkgrm Deletes a patch.
shutdown -h now Directly shuts down an operating system installed on a
host.
shutdown -y Shuts down an operating system by entering y for many
times.
svcs Displays the running status of an operating system.
svcadm Modifies the running status of an operating system.
umount Unmounts file systems.
In the preceding table, # in command lines is a variable and must be set to a number based on-site
requirements.
1.5 Version Information
Solaris was initially called SunOS based on BSD Unix.
SUN Microsystems started to develop System V Release 4 (SVR4) from SunOS 5.0 and gave
it a new name Solaris 2.0. After Solaris 2.6 was released, SUN Microsystems renamed SunOS
2.10 to Solaris 10. Later, the earlier versions of Solaris were renamed to Solaris 1.x.
Therefore, the word "SunOS" is used to exclusively indicate the Solaris operating system
kernel. Based on this, it is deemed that Solaris consists of SunOS, GUI, and other network
enhancements.
1.5.1 Querying the Current Version
To query the current system version, run the following command:
bash-3.2# cat /etc/release
Oracle Solaris 10 8/11 s10s_u10wos_17b SPARC
Copyright (c) 1983, 2011, Oracle and/or its affiliates. All rights reserved.
HUAWEI SAN Storage Host Connectivity Guide for Solaris 1 Solaris Operating System
Issue (2017-07-19) Huawei Proprietary and Confidential
Copyright © Huawei Technologies Co., Ltd.
5
Assembled 23 August 2011
bash-3.2#
In the preceding example, the Solaris version is Solaris 10 U8 that was released in August
2011.
1.5.2 Querying the Version of Software
View information about the current version of software by running the following command:
bash-3.2# pkginfo -l VRTSvxvm
PKGINST: VRTSvxvm
NAME: Binaries for VERITAS Volume Manager by Symantec
CATEGORY: system
ARCH: sparc
VERSION: 6.0.000.000,REV=11.07.2011.15.29
BASEDIR: /
VENDOR: Symantec Corporation
DESC: Virtual Disk Subsystem
PSTAMP: 6.0.000.000-GA-2011-11-07
INSTDATE: Jun 13 2012 18:06
HOTLINE: http://www.symantec.com/business/support/assistance_care.jsp
STATUS: completely installed
FILES: 842 installed pathnames
41 shared pathnames
119 directories
346 executables
393226 blocks used (approx)
bash-3.2#
In the preceding example, we can see that VRTSvxvm is in version 6.0.
1.6 Interoperability Between Solaris and Storage Systems
When connecting a storage system to a Solaris host, consider the interoperability of
upper-layer applications and components (such as storage systems, Solaris systems, HBAs,
and switches) in the environment.
You can query the latest compatibility information by performing the following steps:
Step 1 Log in to the website support-open.huawei.com.
Step 2 On the home page, choose Interoperability Center > Storage Interoperability.
HUAWEI SAN Storage Host Connectivity Guide for Solaris 1 Solaris Operating System
Issue (2017-07-19) Huawei Proprietary and Confidential
Copyright © Huawei Technologies Co., Ltd.
6
Figure 1-2 Interoperability query page
Then, the OceanStor Interoperability Navigator is displayed.
Figure 1-3 OceanStor Interoperability Navigator
----End
HUAWEI SAN Storage Host Connectivity Guide for Solaris 2 Network Planning
Issue (2017-07-19) Huawei Proprietary and Confidential
Copyright © Huawei Technologies Co., Ltd.
7
2 Network Planning
Solaris hosts and storage systems can be networked based on different criteria. Table 2-1
describes the typical networking modes.
Table 2-1 Networking modes
Criteria Networking Mode
Interface module type Fibre Channel network or iSCSI network
Whether switches are used Directly connected network (with no switches used) or
switch-connected network (with switches used)
Whether multiple paths exist Single-path network or multi-path network
Whether HyperMetro is used HyperMetro network, or non-HyperMetro network
The Fibre Channel network is the most widely used network for Solaris operating systems. To
ensure service data security, both directly connected network and switch-connected network
are multi-path networks.
The following details commonly used Fibre Channel and iSCSI networks.
2.2 Non-HyperMetro Network
2.2.1 Fibre Channel Networking Diagram
2.2.1.1 Multi-Path Directly Connected Network
Huawei provides dual-controller and multi-controller storage systems, whose network
diagrams differ. The following describes network diagrams of dual-controller and
multi-controller storage systems respectively.
2.2.1.1.1 Dual-Controller
The following uses HUAWEI OceanStor S5500T as an example to explain how to connect a
Solaris host to a storage system over a Fibre Channel multi-path directly connected network,
as shown in Figure 2-2.
HUAWEI SAN Storage Host Connectivity Guide for Solaris 2 Network Planning
Issue (2017-07-19) Huawei Proprietary and Confidential
Copyright © Huawei Technologies Co., Ltd.
8
Figure 2-1 Fibre Channel multi-path directly connected network diagram (dual-controller)
On this network, both controllers of the storage system are connected to the host's HBAs through optical
fibers.
2.2.1.1.2 Multi-Controller
The following uses HUAWEI OceanStor 18800 (four-controller) as an example to explain
how to connect a Solaris host to a storage system over a Fibre Channel multi-path directly
connected network, as shown in Figure 2-2.
Figure 2-2 Fibre Channel multi-path directly connected network diagram (four-controller)
On this network, the four controllers of the storage system are connected to the host's HBAs through
optical fibers.
2.2.1.2 Multi-Path Switch-connected Network
Huawei provides dual-controller and multi-controller storage systems, whose network
diagrams differ. The following describes network diagrams of dual-controller and
multi-controller storage systems respectively.
2.2.1.2.1 Dual-Controller
The following uses HUAWEI OceanStor S5500T as an example to explain how to connect a
Solaris host to a storage system over a Fibre Channel multi-path switch-connected network, as
shown in Figure 2-3.
HUAWEI SAN Storage Host Connectivity Guide for Solaris 2 Network Planning
Issue (2017-07-19) Huawei Proprietary and Confidential
Copyright © Huawei Technologies Co., Ltd.
9
Figure 2-3 Fibre Channel multi-path switch-connected network diagram (dual-controller)
On this network, the storage system is connected to the host via two switches. Both controllers of the
storage system are connected to the switches through optical fibers and both switches are connected to
the host through optical fibers. To ensure the connectivity between the host and the storage system, each
zone contains only one storage port and its corresponding host port.
2.2.1.2.2 Multi-Controller
The following uses HUAWEI OceanStor 18800 (four-controller) as an example to explain
how to connect a Solaris host to a storage system over a Fibre Channel multi-path
switch-connected network, as shown in Figure 2-4.
Figure 2-4 Fibre Channel multi-path switch-connected network diagram (four-controller)
HUAWEI SAN Storage Host Connectivity Guide for Solaris 2 Network Planning
Issue (2017-07-19) Huawei Proprietary and Confidential
Copyright © Huawei Technologies Co., Ltd.
10
On this network, the storage system is connected to the host via two switches. All controllers of the
storage system are connected to the switches through optical fibers and both switches are connected to
the host through optical fibers. To ensure the connectivity between the host and the storage system, each
zone contains only one storage port and its corresponding host port.
2.2.2 iSCSI Network Diagram
2.2.2.1 Multi-Path Directly Connected Network
Huawei provides dual-controller and multi-controller storage systems, whose network
diagrams differ. The following describes network diagrams of dual-controller and
multi-controller storage systems respectively.
2.2.2.1.1 Dual-Controller
The following uses HUAWEI OceanStor S5500T as an example to explain how to connect a
Solaris host to a storage system over an iSCSI multi-path directly connected network, as
shown in Figure 2-5.
Figure 2-5 iSCSI multi-path directly connected network diagram (dual-controller)
On this network, both controllers of the storage system are connected to the host's network adapter
through Ethernet cables.
2.2.2.2 Multi-Controller
The following uses HUAWEI OceanStor 18800 (four-controller) as an example to explain
how to connect a Solaris host to a storage system over an iSCSI multi-path directly connected
network, as shown in Figure 2-6.
Figure 2-6 iSCSI multi-path directly connected network diagram (four-controller)
HUAWEI SAN Storage Host Connectivity Guide for Solaris 2 Network Planning
Issue (2017-07-19) Huawei Proprietary and Confidential
Copyright © Huawei Technologies Co., Ltd.
11
On this network, the four controllers of the storage system are connected to the host's network adapter
through Ethernet cables.
2.2.2.3 Multi-Path Switch-connected Network
Huawei provides dual-controller and multi-controller storage systems, whose network
diagrams differ. The following describes network diagrams of dual-controller and
multi-controller storage systems respectively.
2.2.2.3.1 Dual-Controller
The following uses HUAWEI OceanStor S5500T as an example to explain how to connect a
Solaris host to a storage system over an iSCSI multi-path switch-connected network, as
shown in Figure 2-7.
Figure 2-7 iSCSI multi-path switch-connected network diagram (dual-controller)
On this network, the storage system is connected to the host via two Ethernet switches. Both controllers
of the storage system are connected to the switches through Ethernet cables and both switches are
connected to the host's network adapter through Ethernet cables. To ensure the connectivity between the
host and the storage system, each VLAN contains only one storage port and its corresponding host port.
2.2.2.3.2 Multi-Controller
The following uses HUAWEI OceanStor 18800 (four-controller) as an example to explain
how to connect a Solaris host to a storage system over an iSCSI multi-path switch-connected
network, as shown in Figure 2-8.
HUAWEI SAN Storage Host Connectivity Guide for Solaris 2 Network Planning
Issue (2017-07-19) Huawei Proprietary and Confidential
Copyright © Huawei Technologies Co., Ltd.
12
Figure 2-8 iSCSI multi-path switch-connected network diagram (four-controller)
On this network, the storage system is connected to the host via two Ethernet switches. All controllers of
the storage system are connected to the switches through Ethernet cables and both switches are
connected to the host's network adapter through Ethernet cables. To ensure the connectivity between the
host and the storage system, each VLAN contains only one storage port and its corresponding host port.
2.3 HyperMetro Network
HyperMetro using the OS native multipathing function has the following networking
requirements:
Uses the multi-path switch-connected networking by default.
In the switches' zone configuration, allows a zone to only contain one initiator and one
target.
You are advised to use dual-switch networking to prevent single points of failure.
2.3.1 Fibre Channel Networking Diagram
2.3.1.1 Multi-Path Switch-Connected Network
Huawei provides dual-controller and multi-controller storage systems, whose network
diagrams differ. The following describes network diagrams of dual-controller and
multi-controller storage systems respectively.
2.3.1.1.1 Dual-Controller
The following uses HUAWEI OceanStor 6800 V3 (dual-controller) as an example to explain
how to connect a Solaris host to a storage system over a Fibre Channel multi-path
switch-connected network, as shown in Figure 2-9.
HUAWEI SAN Storage Host Connectivity Guide for Solaris 2 Network Planning
Issue (2017-07-19) Huawei Proprietary and Confidential
Copyright © Huawei Technologies Co., Ltd.
13
Figure 2-9 Fibre Channel multi-path switch-connected networking diagram (dual-controller)
On this network, the storage system is connected to the host via two switches. The two storage systems'
two controllers are connected to the switches through optical fibers and both switches are connected to
the host through optical fibers. To ensure the connectivity between the host and the storage system, each
zone contains only one storage port and its corresponding host port. In this example, the two storage
systems' two controllers are interconnected through optical cables to form replication links. Alternatively,
you can also connect the two controllers through a switch to form replication links.
2.3.1.1.2 Multi-Controller
The following uses HUAWEI OceanStor 6800 V3 (four-controller) as an example to explain
how to connect a Solaris host to a storage system over a Fibre Channel multi-path
switch-connected network, as shown in Figure 2-10.
HUAWEI SAN Storage Host Connectivity Guide for Solaris 2 Network Planning
Issue (2017-07-19) Huawei Proprietary and Confidential
Copyright © Huawei Technologies Co., Ltd.
14
Figure 2-10 Fibre Channel multi-path switch-connected networking diagram (four-controller)
On this network, the storage system is connected to the host via two switches. All the two storage
systems' four controllers are connected to the switches through optical fibers and both switches are
connected to the host through optical fibers. To ensure the connectivity between the host and the storage
system, each zone contains only one storage port and its corresponding host port. In this example, the
two storage systems' four controllers are interconnected through optical cables to form replication links.
Alternatively, you can also connect the four controllers through two switches to form replication links.
HUAWEI SAN Storage Host Connectivity Guide for Solaris 3 Configuration Preparations (Hosts)
Issue (2017-07-19) Huawei Proprietary and Confidential
Copyright © Huawei Technologies Co., Ltd.
15
3 Configuration Preparations (Hosts)
Before connecting hosts to storage systems, check that HBAs on the hosts are identified
correctly and work properly. In addition, find out the WWNs of the corresponding ports on
HBAs to facilitate data configuration on storage systems.
This chapter describes the two operations in detail.
3.1 Identifying HBAs
After an HBA is installed on a host, check whether the host has identified the HBA by running
the following command:
bash-3.2# cfgadm -al
Ap_Id Type Receptacle Occupant Condition
c0 scsi-bus connected configured unknown
c0::dsk/c0t0d0 CD-ROM connected configured unknown
c1 scsi-sata connected configured unknown
c1::dsk/c1t0d0 disk connected configured unknown
c1::dsk/c1t1d0 disk connected configured unknown
c1::dsk/c1t2d0 disk connected configured unknown
c1::dsk/c1t3d0 disk connected configured unknown
c7 fc-private connected configured unknown
c7::2013323232323232 disk connected configured unknown
c8 fc-private connected configured unknown
c8::2003323232323232 disk connected configured unknown
usb0/1 unknown empty unconfigured ok
usb0/2 unknown empty unconfigured ok
usb0/3 unknown empty unconfigured ok
usb1/1.1 unknown empty unconfigured ok
usb1/1.2 unknown empty unconfigured ok
usb1/1.3 unknown empty unconfigured ok
usb1/1.4 unknown empty unconfigured ok
usb1/2 unknown empty unconfigured ok
usb1/3 unknown empty unconfigured ok
usb2/1 unknown empty unconfigured ok
usb2/2 unknown empty unconfigured ok
usb2/3 unknown empty unconfigured ok
usb2/4 unknown empty unconfigured ok
usb2/5 unknown empty unconfigured ok
HUAWEI SAN Storage Host Connectivity Guide for Solaris 3 Configuration Preparations (Hosts)
Issue (2017-07-19) Huawei Proprietary and Confidential
Copyright © Huawei Technologies Co., Ltd.
16
usb2/6 unknown empty unconfigured ok
usb2/7 unknown empty unconfigured ok
usb2/8 unknown empty unconfigured ok
The results show that two Ap_Ids (c7 and c8) are of fc-private type. This indicates that the
host has identified two Fibre Channel ports on the HBA.
Make sure that Receptacle is in the connected state and Occupant is in the configured state.
If both parameters are in incorrect states, follow-up operations such as LUN discovery are
affected.
If Receptacle is in the connected state and Occupant is in the unconfigured state, recover
the unconfigured state using the following methods:
Manually configuring devices
Manually configure devices by running the cfgadm -c configure cx command. cx is a
variable.
Forcibly initializing devices
Re-initialize Fibre Channel links by running the following commands:
bash-3.2# luxadm -e port
/devices/pci@1f,700000/pci@0/fibre-channel@2/fp@0,0:devctl CONNECTED
/devices/pci@1f,700000/pci@0/fibre-channel@2,1/fp@0,0:devctl CONNECTED
bash-3.2#
bash-3.2# luxadm -e forcelip
/devices/pci@1f,700000/pci@0/fibre-channel@2/fp@0,0:devctl
bash-3.2#
You will initialize an HBA port when running the preceding commands. All port links may be
disconnected and reconnected.
Restarting servers
If the preceding two methods fail, reboot servers. You need to use this method with
caution, because this operation may interrupt system services on a host.
3.2 Querying HBA Properties
Typically, you need to pay attention to the WWN, speed, topology, and firmware of an HBA.
The methods for viewing the properties vary with Solaris operating system versions. The
section describes how to view HBA properties in detail.
3.2.1 Solaris 8 and 9
To query HBA information on Solaris 8 and 9 operating systems, perform the following
operations:
Step 1 View information about Fibre Channel ports.
On a host, run the following command:
HUAWEI SAN Storage Host Connectivity Guide for Solaris 3 Configuration Preparations (Hosts)
Issue (2017-07-19) Huawei Proprietary and Confidential
Copyright © Huawei Technologies Co., Ltd.
17
bash-3.2# cfgadm
Ap_Id Type Receptacle Occupant Condition
c0 scsi-bus connected configured unknown
c1 scsi-sata connected configured unknown
c7 fc-private connected configured unknown
c8 fc-private connected configured unknown
usb0/1 unknown empty unconfigured ok
usb0/2 unknown empty unconfigured ok
usb0/3 unknown empty unconfigured ok
usb1/1.1 unknown empty unconfigured ok
usb1/1.2 unknown empty unconfigured ok
usb1/1.3 unknown empty unconfigured ok
usb1/1.4 unknown empty unconfigured ok
usb1/2 unknown empty unconfigured ok
usb1/3 unknown empty unconfigured ok
usb2/1 unknown empty unconfigured ok
usb2/2 unknown empty unconfigured ok
usb2/3 unknown empty unconfigured ok
usb2/4 unknown empty unconfigured ok
usb2/5 unknown empty unconfigured ok
usb2/6 unknown empty unconfigured ok
usb2/7 unknown empty unconfigured ok
usb2/8 unknown empty unconfigured ok
bash-3.2#
In the preceding example, we can see that ports whose Ap_Ids are c7 and c8 are devices
corresponding to Fibre Channel HBAs.
Step 2 Search for the device name of a Fibre Channel HBA.
Search for the complete device name of a Fibre Channel HBA by running the following
command:
bash-3.2# cfgadm -lv c7
Ap_Id Receptacle Occupant Condition Information
When Type Busy Phys_Id
c7 connected configured unknown
unavailable fc-private n
/devices/pci@1f,700000/pci@0/fibre-channel@2/fp@0,0:fc
Based on the preceding results, we can see that the complete device name of c7 is
/devices/pci@1f,700000/pci@0/fibre-channel@2/fp@0,0:fc.
Step 3 Search for the WWN of a Fibre Channel HBA.
Search for the WWN of a Fibre Channel HBA by running the following command:
bash-3.2# luxadm -e dump_map /devices/pci@1f,700000/pci@0/fibre-channel@2/fp@0,0:fc
Pos AL_PA ID Hard_Addr Port WWN Node WWN Type
0 1 7d 0 10000000c96fa382 20000000c96fa382 0x1f (Unknown Type,Host Bus
Adapter)
1 b6 1c b6 2013323232323232 2100323232323232 0x0 (Disk device)
bash-3.2#
Based on the preceding results, we can see that the WWN of c7 is 10000000c96fa382.
----End
HUAWEI SAN Storage Host Connectivity Guide for Solaris 3 Configuration Preparations (Hosts)
Issue (2017-07-19) Huawei Proprietary and Confidential
Copyright © Huawei Technologies Co., Ltd.
18
3.2.2 Solaris 10 and 11
You can query HBA information on the Solaris 10 operating system and later by running the
following command:
bash-3.2# fcinfo hba-port
HBA Port WWN: 10000000c96fa382
OS Device Name: /dev/cfg/c7
Manufacturer: Emulex
Model: LP11002-E
Firmware Version: 2.10a10 (B2F2.10A10)
FCode/BIOS Version: Boot:1.70a3 Fcode:none
Serial Number: VM74944560
Driver Name: emlxs
Driver Version: 2.60k (2011.03.24.16.45)
Type: L-port
State: online
Supported Speeds: 1Gb 2Gb 4Gb
Current Speed: 4Gb
Node WWN: 20000000c96fa382
HBA Port WWN: 10000000c96fa383
OS Device Name: /dev/cfg/c8
Manufacturer: Emulex
Model: LP11002-E
Firmware Version: 2.10a10 (B2F2.10A10)
FCode/BIOS Version: Boot:1.70a3 Fcode:none
Serial Number: VM74944560
Driver Name: emlxs
Driver Version: 2.60k (2011.03.24.16.45)
Type: L-port
State: online
Supported Speeds: 1Gb 2Gb 4Gb
Current Speed: 4Gb
Node WWN: 20000000c96fa383
bash-3.2#
In the preceding example, we can see that the WWNs of HBAs are 10000000c96fa382 and
10000000c96fa383. The types, topology modes, and current rate of HBAs are also queried.
HUAWEI SAN Storage Host Connectivity Guide for Solaris
4 Preparations Before Configuration (on a Storage
System)
Issue (2017-07-19) Huawei Proprietary and Confidential
Copyright © Huawei Technologies Co., Ltd.
19
4 Preparations Before Configuration (on a Storage System)
Make sure that RAID groups, LUNs, and hosts are correctly created on the storage systems.
These configurations are common and therefore not detailed here.
HUAWEI SAN Storage Host Connectivity Guide for Solaris 5 Configuring Switches
Issue (2017-07-19) Huawei Proprietary and Confidential
Copyright © Huawei Technologies Co., Ltd.
20
5 Configuring Switches
Solaris hosts and storage systems can be connected over a Fibre Channel switch-based
network and an iSCSI switch-based network. A Fibre Channel switch-based network uses
Fibre Channel switches and an iSCSI network uses Ethernet switches. This chapter describes
how to configure a Fibre Channel switch and an Ethernet switch respectively.
5.1 Fibre Channel Switch
The commonly used Fibre Channel switches are mainly from Brocade, Cisco, and QLogic.
The following uses a Brocade switch as an example to explain how to configure switches.
5.1.1 Querying the Switch Model and Version
Perform the following steps to query the switch model and version:
Step 1 Log in to the Brocade switch from a web page.
On the web page, enter the IP address of the Brocade switch. The Web Tools switch login
dialog box is displayed. Enter the account and password. The default account and password
are admin and password. The switch management page is displayed.
CAUTION
Web Tools works correctly only when Java is installed on the host. Java 1.6 or later is
recommended.
Step 2 View the switch information.
On the switch management page that is displayed, click Switch Information. The switch
information is displayed, as shown in Figure 5-1.
HUAWEI SAN Storage Host Connectivity Guide for Solaris 5 Configuring Switches
Issue (2017-07-19) Huawei Proprietary and Confidential
Copyright © Huawei Technologies Co., Ltd.
21
Figure 5-1 Switch information
Tue June
Note the following parameters:
Fabric OS version: indicates the switch version information. The interoperability
between switches and storage systems varies with the switch version. Only switches of
authenticated versions can interconnect correctly with storage systems.
Type: This parameter is a decimal consists of an integer and a decimal fraction. The
integer indicates the switch model and the decimal fraction indicates the switch template
version. You only need to pay attention to the switch model. Table 5-1 describes switch
model mapping.
Table 5-1 Mapping between switch types and names
Switch Type
Switch Name Switch Type
Switch Name
1 Brocade 1000 Switch 58 Brocade 5000 Switch
2,6 Brocade 2800 Switch 61 Brocade 4424 Embedded
Switch
3 Brocade 2100, 2400 Switches 62 Brocade DCX Backbone
4 Brocade 20x0, 2010, 2040,
2050 Switches
64 Brocade 5300 Switch
5 Brocade 22x0, 2210, 2240,
2250 Switches
66 Brocade 5100 Switch
7 Brocade 2000 Switch 67 Brocade Encryption Switch
HUAWEI SAN Storage Host Connectivity Guide for Solaris 5 Configuring Switches
Issue (2017-07-19) Huawei Proprietary and Confidential
Copyright © Huawei Technologies Co., Ltd.
22
Switch Type
Switch Name Switch Type
Switch Name
9 Brocade 3800 Switch 69 Brocade 5410 Blade
10 Brocade 12000 Director 70 Brocade 5410 Embedded
Switch
12 Brocade 3900 Switch 71 Brocade 300 Switch
16 Brocade 3200 Switch 72 Brocade 5480 Embedded
Switch
17 Brocade 3800VL 73 Brocade 5470 Embedded
Switch
18 Brocade 3000 Switch 75 Brocade M5424 Embedded
Switch
21 Brocade 24000 Director 76 Brocade 8000 Switch
22 Brocade 3016 Switch 77 Brocade DCX-4S
Backbone
26 Brocade 3850 Switch 83 Brocade 7800 Extension
Switch
27 Brocade 3250 Switch 86 Brocade 5450 Embedded
Switch
29 Brocade 4012 Embedded
Switch 87 Brocade 5460 Embedded
Switch
32 Brocade 4100 Switch 90 Brocade 8470 Embedded
Switch
33 Brocade 3014 Switch 92 Brocade VA-40FC Switch
34 Brocade 200E Switch 95 Brocade VDX 6720-24
Data Center Switch
37 Brocade 4020 Embedded
Switch 96 Brocade VDX 6730-32
Data Center Switch
38 Brocade 7420 SAN Router 97 Brocade VDX 6720-60
Data Center Switch
40 Fibre Channel Routing (FCR)
Front Domain
98 Brocade VDX 6730-76
Data Center Switch
41 Fibre Channel Routing,
(FCR) Xlate Domain
108 Dell M8428-k FCoE
Embedded Switch
42 Brocade 48000 Director 109 Brocade 6510 Switch
43 Brocade 4024 Embedded
Switch
116 Brocade VDX 6710 Data
Center Switch
44 Brocade 4900 Switch 117 Brocade 6547 Embedded
Switch
HUAWEI SAN Storage Host Connectivity Guide for Solaris 5 Configuring Switches
Issue (2017-07-19) Huawei Proprietary and Confidential
Copyright © Huawei Technologies Co., Ltd.
23
Switch Type
Switch Name Switch Type
Switch Name
45 Brocade 4016 Embedded
Switch
118 Brocade 6505 Switch
46 Brocade 7500 Switch 120 Brocade DCX 8510-8
Backbone
51 Brocade 4018 Embedded
Switch
121 Brocade DCX 8510-4
Backbone
55.2 Brocade 7600 Switch
Ethernet IPv4: indicates the switch IP address.
Effective Configuration: indicates the currently effective configurations. This parameter
is important and is related to zone configurations. In this example, the currently effective
configuration is ss.
----End
5.1.2 Configuring Zones
Zone configuration is important for Fibre Channel switches. Perform the following steps to
configure switch zones:
Step 1 Log in to the Brocade switch from a web page. This step is the same as that in section 5.1.1
"Querying the Switch Model and Version."
Step 2 Check the switch port status.
Normally, the switch port indicators are steady green, as shown in Figure 5-2.
Figure 5-2 Switch port indicator status
If the port indicators are abnormal, check the topology mode and rate. Proceed with the next
step after all indicators are normal.
Step 3 Go to the Zone Admin page.
In the navigation tree of Web Tools, choose Task > Manage > Zone Admin. You can also
choose Manage > Zone Admin in the navigation bar.
Step 4 Check whether the switch identifies hosts and storage systems.
On the Zone Admin page, click the Zone tab. In Ports&Attached Devices, check whether
all related ports are identified, as shown in Figure 5-3.
HUAWEI SAN Storage Host Connectivity Guide for Solaris 5 Configuring Switches
Issue (2017-07-19) Huawei Proprietary and Confidential
Copyright © Huawei Technologies Co., Ltd.
24
Figure 5-3 Zone tab page
The preceding figure shows that ports 1,8 and 1,9 in use are correctly identified by the switch.
Step 5 Create a zone.
On the Zone tab page, click New Zone to create a new zone and name it zone_8_9. Select
ports 1,8 and 1,9 and click Add Member to add them to the new zone, as shown in Figure
5-4.
Figure 5-4 Zone configuration
CAUTION
To ensure data is transferred separately, ensure that each zone contains one initiator and one
target only.
HUAWEI SAN Storage Host Connectivity Guide for Solaris 5 Configuring Switches
Issue (2017-07-19) Huawei Proprietary and Confidential
Copyright © Huawei Technologies Co., Ltd.
25
Step 6 Add the new zone to the configuration file and activate the new zone.
On the Zone Admin page, click the Zone Config tab. In the Name drop-down list, choose the
currently effective configuration ss.
In Member Selection List, select zone zone_8_9 and click Add Member to add it to the
configuration file.
Click Save Config to save the configuration and click Enable Config to make the
configuration effective.
Figure 5-5 shows the Zone Config page.
Figure 5-5 Zone Config tab page
Step 7 Verify that the configuration takes effect.
In the navigation tree of Web Tools, choose Task > Monitor > Name Server to go to the
Name Server page. You can also choose Monitor > Name Server in the navigation bar.
Figure 5-6 shows the Name Server page.
HUAWEI SAN Storage Host Connectivity Guide for Solaris 5 Configuring Switches
Issue (2017-07-19) Huawei Proprietary and Confidential
Copyright © Huawei Technologies Co., Ltd.
26
Figure 5-6 Name Server page
The preceding figure shows that ports 8 and 9 are members of zone_8_9 that is now effective.
An effective zone is marked by an asterisk (*).
----End
5.1.3 Precautions
Note the following when connecting a Brocade switch to a storage system at a rate of 8
Gbit/s:
The topology mode of the storage system must be set to switch.
fill word of ports through which the switch is connected to the storage system must be
set to 0. To configure this parameter, run the portcfgfillword <port number> 0
command on the switch.
Note the following when connecting a Brocade switch to a storage system at a rate of 8
Gbit/s:
When the switch is connected to module HP VC 8Gb 20-port FC or HP VC FlexFabric
10Gb/24-port, change the switch configuration. For details, visit:
https://h20566.www2.hp.com/portal/site/hpsc/template.PAGE/public/psi/troubleshootDisplay/
?javax.portlet.prp_efb5c0793523e51970c8fa22b053ce01=wsrp-navigationalState%3DdocId%
3Demr_na-c02619780%7CdocLocale%3Dzh_CN&lang=en&javax.portlet.begCacheTok=co
m.vignette.cachetoken&sp4ts.oid=3984629&javax.portlet.endCacheTok=com.vignette.cachet
oken&javax.portlet.tpst=efb5c0793523e51970c8fa22b053ce01&hpappid=sp4ts&cc=US&ac.a
dmitted=1337927146324.876444892.199480143
HUAWEI SAN Storage Host Connectivity Guide for Solaris 5 Configuring Switches
Issue (2017-07-19) Huawei Proprietary and Confidential
Copyright © Huawei Technologies Co., Ltd.
27
5.2 Ethernet Switch
This section describes how to configure Ethernet switches, including configuring VLANs and
binding ports.
5.2.1 Configuring VLANs
On an Ethernet network to which many hosts are connected, a large number of broadcast
packets are generated during the host communication. Broadcast packets sent from one host
will be received by all other hosts on the network, consuming more bandwidth. Moreover, all
hosts on the network can access each other, resulting data security risks.
To save bandwidth and prevent security risks, hosts on an Ethernet network are divided into
multiple logical groups. Each logical group is a VLAN. The following uses HUAWEI
Quidway 2700 Ethernet switch as an example to explain how to configure VLANs.
In the following example, two VLANs (VLAN 1000 and VLAN 2000) are created. VLAN
1000 contains ports GE 1/0/1 to 1/0/16. VLAN 2000 contains ports GE 1/0/20 to 1/0/24.
Step 1 Go to the system view.
<Quidway>system-view
System View: return to User View with Ctrl+Z.
Step 2 Create VLAN 1000 and add ports to it.
[Quidway]VLAN 1000
[Quidway-vlan1000]port GigabitEthernet 1/0/1 to GigabitEthernet 1/0/16
Step 3 Configure the IP address of VLAN 1000.
[Quidway-vlan1000]interface VLAN 1000
[Quidway-Vlan-interface1000]ip address 1.0.0.1 255.255.255.0
Step 4 Create VLAN 2000, add ports, and configure the IP address.
[Quidway]VLAN 2000
[Quidway-vlan2000]port GigabitEthernet 1/0/20 to GigabitEthernet 1/0/24
[Quidway-vlan2000]interface VLAN 2000
[Quidway-Vlan-interface2000]ip address 2.0.0.1 255.255.255.0
----End
5.2.2 Binding Ports
When storage systems and hosts are connected in point-to-point mode, existing bandwidth
may be insufficient for storage data transmission. Moreover, devices cannot be redundantly
connected in point-to-point mode. To address these problems, ports are bound (link
aggregation). Port binding can improve bandwidth and balance load among multiple links.
5.2.2.1 Link Aggregation Modes
Three Ethernet link aggregation modes are available:
Manual aggregation
Manually run a command to add ports to an aggregation group. Ports added to the
aggregation group must have the same link type.
HUAWEI SAN Storage Host Connectivity Guide for Solaris 5 Configuring Switches
Issue (2017-07-19) Huawei Proprietary and Confidential
Copyright © Huawei Technologies Co., Ltd.
28
Static aggregation
Manually run a command to add ports to an aggregation group. Ports added to the
aggregation group must have the same link type and LACP enabled.
Dynamic aggregation
The protocol dynamically adds ports to an aggregation group. Ports added in this way
must have LACP enabled and the same speed, duplex mode, and link type.
Table 5-2 compares the three link aggregation modes.
Table 5-2 Comparison of link aggregation modes
Link Aggregation Mode
Packet Exchange Port Detection CPU Usage
Manual aggregation No No Low
Static aggregation Yes Yes High
Dynamic
aggregation
Yes Yes High
5.2.2.2 Configuration
HUAWEI OceanStor storage devices support 802.3ad link aggregation (dynamic aggregation).
In this link aggregation mode, multiple network ports are in an active aggregation group and
work in duplex mode and at the same speed. After binding iSCSI host ports on a storage
device, enable aggregation for their peer ports on a switch. Otherwise, links are unavailable
between the storage device and the switch.
This section uses switch ports GE 1/0/1 and GE 1/0/2 and iSCSI host ports P2 and P3 as
examples to explain how to bind ports. You can adjust related parameters based on site
requirements.
Bind the iSCSI host ports.
Step 1 Log in to the ISM and go to the page for binding ports.
In the ISM navigation tree, choose Device Info > Storage Unit > Ports. In the function pane,
click iSCSI Host Ports.
Step 2 Bind ports.
Select the ports that you want to bind and choose Bind Ports > Bind in the menu bar. In this
example, the ports to be bound are P2 and P3.
The Bind iSCSI Port dialog box is displayed. In Bond name, enter the name for the port
bond and click OK.
The Warning dialog box is displayed. In the Warning dialog box, select I have read the
warning message carefully and click OK.
The Information dialog box is displayed, indicating that the operation succeeded. Click OK.
After the storage system ports are bound, configure link aggregation on the switch. Run the
following command on the switch:
<Quidway>system-view
HUAWEI SAN Storage Host Connectivity Guide for Solaris 5 Configuring Switches
Issue (2017-07-19) Huawei Proprietary and Confidential
Copyright © Huawei Technologies Co., Ltd.
29
System View: return to User View with Ctrl+Z.
[Quidway-Switch]interface GigabitEthernet 1/0/1
[Quidway-Switch-GigabitEthernet1/0/19]lacp enable
LACP is already enabled on the port!
[Quidway-Switch-GigabitEthernet1/0/19]quit
[Quidway-Switch]interface GigabitEthernet 1/0/2
[Quidway-Switch-GigabitEthernet1/0/20]lacp enable
LACP is already enabled on the port!
[Quidway-Switch-GigabitEthernet1/0/20]quit
After the command is executed, LACP is enabled for ports GE 1/0/1 and GE 1/0/2. Then the
ports can be automatically detected and added to an aggregation group.
----End
5.3 FCoE Switch
The configurations of FCoE switches are different from those of FC switches and Ethernet
switches. For details, see the specific switch vendor-provided configuration guide.
Taking Cisco Nexus5548 as an example, Figure 5-7 shows an FCoE configuration process.
Figure 5-7 Process for configuring an FCoE switch
5.3.2 Command Introduction
When using SSH to log in to and manage an FCoE switch, you can have all supported
commands displayed by inputting "?":
switch# ?
callhome Callhome commands
cd Change current directory
cfs CFS parameters
checkpoint Create configuration rollback checkpoint
clear Reset functions
cli CLI commands
clock Manage the system clock
configure Enter configuration mode
copy Copy from one file to another
debug Debugging functions
debug-filter Enable filtering for debugging functions
HUAWEI SAN Storage Host Connectivity Guide for Solaris 5 Configuring Switches
Issue (2017-07-19) Huawei Proprietary and Confidential
Copyright © Huawei Technologies Co., Ltd.
30
delete Delete a file or directory
diff-clean Remove temp files created by '| diff' filters
dir List files in a directory
discover Discover information
dos2nxos DOS to NXOS text file format converter
echo Echo argument back to screen (useful for scripts)
ethanalyzer Configure cisco packet analyzer
event Event Manager commands
fcdomain Fcdomain internal command
fcping Ping an N-Port
fctrace Trace the route for an N-Port.
find Find a file below the current directory
fips Enable/Disable FIPS mode
gunzip Uncompresses LZ77 coded files
gzip Compresses file using LZ77 coding
hardware Change hardware usage settings
install Upgrade software
ip Configure IP features
ipv6 Configure IPv6 features
load Load system image
locator-led Turn on locator beacon
mkdir Create new directory
modem Modem commands
move Move files
mping Run mping
mtrace Trace multicast path from receiver to source
no Negate a command or set its defaults
ntp NTP configuration
ping Test network reachability
ping6 Test IPv6 network reachability
pktmgr Display Packet Manager information
purge Deletes unused data
pwd View current directory
reload Reboot the entire box
restart Manually restart a component
rmdir Delete a directory
rollback Rollback configuration
routing-context Set the routing context
run-script Run shell scripts
san-port-channel Port-Channel related commands
scripting Configure scripting parameters
send Send message to open sessions
setup Run the basic SETUP command facility
show Show running system information
sleep Sleep for the specified number of seconds
sockets Display sockets status and configuration
ssh SSH to another system
system System management commands
system System configuration commands
tac-pac Save tac info in a compressed .gz file at specific location
tail Display the last part of a file
tar Archiving operations
tclsh Source tclsh script
telnet Telnet to another system
telnet6 Telnet6 to another system using IPv6 addressing
HUAWEI SAN Storage Host Connectivity Guide for Solaris 5 Configuring Switches
Issue (2017-07-19) Huawei Proprietary and Confidential
Copyright © Huawei Technologies Co., Ltd.
31
terminal Set terminal line parameters
test Test command
traceroute Traceroute to destination
traceroute6 Traceroute6 to destination
undebug Disable Debugging functions (See also debug)
write Write current configuration
xml Xml agent
xml Module XML agent
zone Execute Zone Server commands
zoneset Execute zoneset commands
end Go to exec mode
exit Exit from command interpreter
pop Pop mode from stack or restore from name
push Push current mode to stack or save it under name
where Shows the cli context you are in
switch#
For example, to query the model and version, run the following command:
switch# show version
Cisco Nexus Operating System (NX-OS) Software
TAC support: http://www.cisco.com/tac
Documents:
http://www.cisco.com/en/US/products/ps9372/tsd_products_support_series_home.html
Copyright (c) 2002-2012, Cisco Systems, Inc. All rights reserved.
The copyrights to certain works contained herein are owned by
other third parties and are used and distributed under license.
Some parts of this software are covered under the GNU Public
License. A copy of the license is available at
http://www.gnu.org/licenses/gpl.html.
Software
BIOS: version 3.5.0
loader: version N/A
kickstart: version 5.1(3)N1(1a)
system: version 5.1(3)N1(1a)
power-seq: Module 1: version v1.0
Module 3: version v2.0
uC: version v1.2.0.1
SFP uC: Module 1: v1.0.0.0
BIOS compile time: 02/03/2011
kickstart image file is: bootflash:///n5000-uk9-kickstart.5.1.3.N1.1a.bin
kickstart compile time: 2/7/2012 23:00:00 [02/08/2012 07:49:30]
system image file is: bootflash:///n5000-uk9.5.1.3.N1.1a.bin
system compile time: 2/7/2012 23:00:00 [02/08/2012 12:44:33]
Hardware
cisco Nexus5548 Chassis ("O2 32X10GE/Modular Universal Platform Supervisor")
Intel(R) Xeon(R) CPU with 8263880 kB of memory.
Processor Board ID FOC16256KUW
Device name: switch
bootflash: 2007040 KB
HUAWEI SAN Storage Host Connectivity Guide for Solaris 5 Configuring Switches
Issue (2017-07-19) Huawei Proprietary and Confidential
Copyright © Huawei Technologies Co., Ltd.
32
Kernel uptime is 15 day(s), 1 hour(s), 59 minute(s), 8 second(s)
Last reset at 299763 usecs after Wed Feb 18 05:48:07 2009
Reason: Reset Requested by CLI command reload
System version: 5.1(3)N1(1a)
Service:
plugin
Core Plugin, Ethernet Plugin, Fc Plugin
5.3.3 Creating a VSAN
To create a VSAN on a Cisco Nexus5548 VSAN, do as follows:
Step 1 Activate FCoE.
switch# conf t
Enter configuration commands, one per line. End with CNTL/Z.
switch(config)# feature fcoe
fcoe fcoe-npv
switch(config)# feature fcoe
switch(config)# show fcoe
Global FCF details
FCF-MAC is 54:7f:ee:b4:f8:20
FC-MAP is 0e:fc:00
FCF Priority is 128
FKA Advertisement period for FCF is 8 seconds
Step 2 Create a VSAN.
In the following display, the switch(config-vsan-db)# vsan 200 command in red is the VSAN
create command. Additionally, you can run show vsan command to check whether the VSAN
is created successfully.
switch(config)# show vsan
vsan 1 information
name:VSAN0001 state:active
interoperability mode:default
loadbalancing:src-id/dst-id/oxid
operational state:down
vsan 100 information
name:VSAN0100 state:active
interoperability mode:default
loadbalancing:src-id/dst-id/oxid
operational state:up
vsan 4079:evfp_isolated_vsan
vsan 4094:isolated_vsan
switch(config)# vsan database
switch(config-vsan-db)# vsan 200
switch(config-vsan-db)# exit
switch(config)# show vsan
vsan 1 information
HUAWEI SAN Storage Host Connectivity Guide for Solaris 5 Configuring Switches
Issue (2017-07-19) Huawei Proprietary and Confidential
Copyright © Huawei Technologies Co., Ltd.
33
name:VSAN0001 state:active
interoperability mode:default
loadbalancing:src-id/dst-id/oxid
operational state:down
vsan 100 information
name:VSAN0100 state:active
interoperability mode:default
loadbalancing:src-id/dst-id/oxid
operational state:up
vsan 200 information
name:VSAN0200 state:active
interoperability mode:default
loadbalancing:src-id/dst-id/oxid
operational state:down
vsan 4079:evfp_isolated_vsan
vsan 4094:isolated_vsan
----End
5.3.4 Creating a VLAN
To create a VLAN on a CISCO Nexus5548, do as follows:
Step 1 Check for existing VLANs.
switch(config)# show vlan
VLAN Name Status Ports
---- -------------------------------- --------- -------------------------------
1 default active Eth1/1, Eth1/2, Eth1/4, Eth1/5
Eth1/6, Eth1/7, Eth1/8, Eth1/15
Eth1/21, Eth1/22, Eth1/23
Eth1/24, Eth1/25, Eth1/26
Eth1/27, Eth1/28
100 VLAN0100 active Eth1/1, Eth1/2, Eth1/3, Eth1/4
Eth1/5, Eth1/6, Eth1/7, Eth1/8
Eth1/9, Eth1/10, Eth1/11
Eth1/12, Eth1/13, Eth1/14
Eth1/15, Eth1/16, Eth1/17
Eth1/18, Eth1/19, Eth1/20
VLAN Type Vlan-mode
---- ----- ----------
1 enet CE
100 enet CE
Remote SPAN VLANs
-------------------------------------------------------------------------------
Primary Secondary Type Ports
------- --------- --------------- -------------------------------------------
HUAWEI SAN Storage Host Connectivity Guide for Solaris 5 Configuring Switches
Issue (2017-07-19) Huawei Proprietary and Confidential
Copyright © Huawei Technologies Co., Ltd.
34
Step 2 Create a VLAN and check whether the creation is successful.
switch(config)# vlan 200
switch(config-vlan)# show vlan
VLAN Name Status Ports
---- -------------------------------- --------- -------------------------------
1 default active Eth1/1, Eth1/2, Eth1/4, Eth1/5
Eth1/6, Eth1/7, Eth1/8, Eth1/15
Eth1/21, Eth1/22, Eth1/23
Eth1/24, Eth1/25, Eth1/26
Eth1/27, Eth1/28
100 VLAN0100 active Eth1/1, Eth1/2, Eth1/3, Eth1/4
Eth1/5, Eth1/6, Eth1/7, Eth1/8
Eth1/9, Eth1/10, Eth1/11
Eth1/12, Eth1/13, Eth1/14
Eth1/15, Eth1/16, Eth1/17
Eth1/18, Eth1/19, Eth1/20
200 VLAN0200 active Eth1/1, Eth1/2, Eth1/4, Eth1/5
Eth1/6, Eth1/7, Eth1/8, Eth1/15
VLAN Type Vlan-mode
---- ----- ----------
1 enet CE
100 enet CE
200 enet CE
Remote SPAN VLANs
-------------------------------------------------------------------------------
Primary Secondary Type Ports
------- --------- --------------- -------------------------------------------
----End
5.3.5 Configuring a Port and Adding It to the VLAN
To configure and add a port to a created VLAN, do as follows:
Step 1 Configure the port running mode and add it to the VLAN.
switch (config)# interface ethernet 1/1
switch (config-if)# switchport mode trunk
switch (config-if)# spanning-tree port type edge trunk
Step 2 Create a VFC and bind it to the physical port.
switch (config)# interface vfc 1
switch (config-if)# bind interface ethernet 1/1
switch (config-if)# no shutdown
Step 3 Add the new VFC to the VSAN.
NEXUS(config)# vsan database
NEXUS(config-vsan-db)# vsan 2 interface vfc 1
HUAWEI SAN Storage Host Connectivity Guide for Solaris 5 Configuring Switches
Issue (2017-07-19) Huawei Proprietary and Confidential
Copyright © Huawei Technologies Co., Ltd.
35
----End
5.3.6 Creating a Zone and Adding the Port to It
To create a zone and add a port to it on a CISCO Nexus5548, do as follows:
Step 1 Check the WWN of the FCoE device connected to the CISCO Nexus5548 switch:
switch# show flogi database
--------------------------------------------------------------------------------
INTERFACE VSAN FCID PORT NAME NODE NAME
--------------------------------------------------------------------------------
vfc1 100 0x2b0002 21:00:00:0e:1e:0a:6b:ab 20:00:00:0e:1e:0a:6b:ab
vfc4 100 0x2b0008 21:00:00:c0:dd:13:e2:a1 20:00:00:c0:dd:13:e2:a1
[lzh1]
vfc5 100 0x2b0007 20:00:00:07:43:ab:ce:07 10:00:00:07:43:ab:ce:07
vfc6 100 0x2b0009 21:00:00:c0:dd:13:e2:a3 20:00:00:c0:dd:13:e2:a3
[lzh2]
Total number of flogi = 4.
Step 2 On the switch, register a device name for the FCoE device. Then, either the device name or
the WWN can be used during later operations such as zone division.
switch(config)# device-alias database
switch(config-device-alias-db)# device-alias name test1 pwwn 20:00:00:0e:1e:0a:6b:ab
switch(config-device-alias-db)# device-alias name test2 pwwn 10:00:00:07:43:ab:ce:07
switch(config-device-alias-db)# device-alias commit
switch(config-device-alias-db)# show device-alias database
device-alias name lzh1 pwwn 21:00:00:c0:dd:13:e2:a1
device-alias name lzh2 pwwn 21:00:00:c0:dd:13:e2:a3
device-alias name lzh3 pwwn 20:00:00:07:43:ab:cd:ef
device-alias name lzh4 pwwn 20:00:00:07:43:ab:cd:f7
device-alias name test1 pwwn 20:00:00:0e:1e:0a:6b:ab
device-alias name test2 pwwn 10:00:00:07:43:ab:ce:07
Step 3 Add the device name to the zone.
switch# show zone
zone name zonexzh vsan 100
pwwn 21:00:00:0e:1e:0a:6b:ab
pwwn 00:00:00:07:43:ab:cd:f7
pwwn 20:00:00:07:43:ab:ce:07
zone name zonexzh02 vsan 100
pwwn 21:00:00:0e:1e:0a:6b:af
zone name zonexz vsan 100
pwwn 21:00:00:c0:dd:12:06:03
pwwn 20:00:00:07:43:ab:cd:ff
zone name lzhzone1 vsan 100
pwwn 21:00:00:c0:dd:13:e2:a1 [lzh1]
pwwn 20:00:00:07:43:ab:cd:ef [lzh3]
zone name lzhzone2 vsan 100
HUAWEI SAN Storage Host Connectivity Guide for Solaris 5 Configuring Switches
Issue (2017-07-19) Huawei Proprietary and Confidential
Copyright © Huawei Technologies Co., Ltd.
36
pwwn 21:00:00:c0:dd:13:e2:a3 [lzh2]
pwwn 20:00:00:07:43:ab:cd:f7 [lzh4]
zone name lzhzone3 vsan 100
switch(config)# zone name lzhzone3 vsan 100
switch(config-zone)# member device-alias test1
switch(config-zone)# member device-alias test2
switch(config-zone)# show zone
zone name zonexzh vsan 100
pwwn 21:00:00:0e:1e:0a:6b:ab
pwwn 00:00:00:07:43:ab:cd:f7
pwwn 20:00:00:07:43:ab:ce:07
zone name zonexzh02 vsan 100
pwwn 21:00:00:0e:1e:0a:6b:af
zone name zonexz vsan 100
pwwn 21:00:00:c0:dd:12:06:03
pwwn 20:00:00:07:43:ab:cd:ff
zone name lzhzone1 vsan 100
pwwn 21:00:00:c0:dd:13:e2:a1 [lzh1]
pwwn 20:00:00:07:43:ab:cd:ef [lzh3]
zone name lzhzone2 vsan 100
pwwn 21:00:00:c0:dd:13:e2:a3 [lzh2]
pwwn 20:00:00:07:43:ab:cd:f7 [lzh4]
zone name lzhzone3 vsan 100
pwwn 20:00:00:0e:1e:0a:6b:ab [test1]
pwwn 10:00:00:07:43:ab:ce:07 [test2]
----End
5.3.7 Creating a Zoneset and Adding the Created Zone to It
To create a zoneset and add a zone to it, do as follows:
Step 1 Create a zoneset in the VSAN.
switch(config)# zoneset name lzhzoneset5 vsan 100
switch(config-zoneset)# show zoneset
zoneset name zoneset100 vsan 100
zone name zonexzh vsan 100
pwwn 21:00:00:0e:1e:0a:6b:ab
pwwn 00:00:00:07:43:ab:cd:f7
pwwn 20:00:00:07:43:ab:ce:07
zone name zonexzh02 vsan 100
pwwn 21:00:00:0e:1e:0a:6b:af
zone name zonexz vsan 100
pwwn 21:00:00:c0:dd:12:06:03
pwwn 20:00:00:07:43:ab:cd:ff
zone name lzhzone1 vsan 100
HUAWEI SAN Storage Host Connectivity Guide for Solaris 5 Configuring Switches
Issue (2017-07-19) Huawei Proprietary and Confidential
Copyright © Huawei Technologies Co., Ltd.
37
pwwn 21:00:00:c0:dd:13:e2:a1 [lzh1]
pwwn 20:00:00:07:43:ab:cd:ef [lzh3]
zone name lzhzone2 vsan 100
pwwn 21:00:00:c0:dd:13:e2:a3 [lzh2]
pwwn 20:00:00:07:43:ab:cd:f7 [lzh4]
zoneset name lzhzoneset5 vsan 100
Step 2 Add the zone to the created zoneset.
switch(config-zoneset)# member lzhzone3
switch(config-zoneset)# show zoneset
zoneset name zoneset100 vsan 100
zone name zonexzh vsan 100
pwwn 21:00:00:0e:1e:0a:6b:ab
pwwn 00:00:00:07:43:ab:cd:f7
pwwn 20:00:00:07:43:ab:ce:07
zone name zonexzh02 vsan 100
pwwn 21:00:00:0e:1e:0a:6b:af
zone name zonexz vsan 100
pwwn 21:00:00:c0:dd:12:06:03
pwwn 20:00:00:07:43:ab:cd:ff
zone name lzhzone1 vsan 100
pwwn 21:00:00:c0:dd:13:e2:a1 [lzh1]
pwwn 20:00:00:07:43:ab:cd:ef [lzh3]
zone name lzhzone2 vsan 100
pwwn 21:00:00:c0:dd:13:e2:a3 [lzh2]
pwwn 20:00:00:07:43:ab:cd:f7 [lzh4]
zoneset name lzhzoneset5 vsan 100
zone name lzhzone3 vsan 100
pwwn 20:00:00:0e:1e:0a:6b:ab [test1]
pwwn 10:00:00:07:43:ab:ce:07 [test2]\
Step 3 Activate the zoneset.
switch (config)# zoneset activate name zoneset_1 vsan 2
zoneset activation initiated. check zone status
WARNING
Generally, for an FCoE switch, only one zoneset can be activated. Therefore, it is advisable to
keep all the zones in a same zoneset, preventing impacts on other services.
HUAWEI SAN Storage Host Connectivity Guide for Solaris 6 Establishing Fibre Channel Connections
Issue (2017-07-19) Huawei Proprietary and Confidential
Copyright © Huawei Technologies Co., Ltd.
38
6 Establishing Fibre Channel Connections
After connecting a host to a storage system, check the topology modes of the host and the
storage system. Fibre Channel connections are established between the host and the storage
system after host initiators are identified by the storage system. The following describes how
to check topology modes and add initiators.
6.1 Checking Topology Modes
Each type of HBAs supports specific topology modes. The topology mode of a storage system
must be consistent with that of supported by host HBAs.
You can use the storage management software ISM to manually change the topology mode of
a storage system to that supported by host HBAs. If the storage ports connected to host HBAs
are adaptive, there is no need to manually change the storage system topology mode.
The method for checking topology modes varies with storage systems. The following
describes how to check the topology mode of the OceanStor T series storage system.
6.1.1 OceanStor T V1 Series Storage System
The check method is as follows:
In the ISM navigation tree, choose Device Info > Storage Unit > Ports. In the function pane,
click FC Host Ports. Select a port connected to the host and then view the port details, as
shown in Figure 6-1.
Figure 6-1 Fibre Channel port details
HUAWEI SAN Storage Host Connectivity Guide for Solaris 6 Establishing Fibre Channel Connections
Issue (2017-07-19) Huawei Proprietary and Confidential
Copyright © Huawei Technologies Co., Ltd.
39
As shown in the preceding figure, the topology mode of the OceanStor T series storage
system is Public Loop.
If the storage system and Solaris hosts are connected through switches, you can set the storage
system's port information according to the port modes supported by the switches.
6.1.2 OceanStor 18000/T V2 /V3/Dorado V3 Series Enterprise Storage System
For the OceanStor 18000/T V2/V3/Dorado V3 series, the check method is as follows:
In the ISM navigation tree, choose System. Then click the device view icon in the upper right
corner. Choose Controller Enclosure ENG0 > Controller > Interface Module > FC Port
and click the port whose details that you want to view, as shown in Figure 6-2.
In the navigation tree, you can see controller A and controller B, each of which has different interface
modules. Choose a controller and an interface module based on actual conditions.
Figure 6-2 Fibre Channel port details
As shown in the preceding figure, the port working mode of the OceanStor 18000/T
V2/V3/Dorado V3 series enterprise storage system is P2P.
6.2 Adding Initiators
This section describes how to add host HBA initiators on a storage system. Perform the
following steps to add initiators:
Step 1 Check HBA WWNs on the host.
Step 2 Check host WWNs on the storage system and add the identified WWNs to the host.
Log in to the ISM and choose SAN Services > Mappings > Initiators in the navigation tree.
In the function pane, check the initiator information. Ensure that the WWNs in step 1 are
HUAWEI SAN Storage Host Connectivity Guide for Solaris 6 Establishing Fibre Channel Connections
Issue (2017-07-19) Huawei Proprietary and Confidential
Copyright © Huawei Technologies Co., Ltd.
40
identified. If the WWNs are not identified, check the Fibre Channel port status. Ensure that
the port status is normal.
----End
6.3 Establishing Connections
Add the WWNs (initiators) to the host and ensure that the initiator connection status is
Online.
HUAWEI SAN Storage Host Connectivity Guide for Solaris 7 Establishing iSCSI Connections
Issue (2017-07-19) Huawei Proprietary and Confidential
Copyright © Huawei Technologies Co., Ltd.
41
7 Establishing iSCSI Connections
This chapter describes how to establish iSCSI connections between a host and a storage
system.
To establish iSCSI connections, you must configure IP addresses and iSCSI services.
Therefore, the operations are more complex than establishing Fibre Channel connections. The
process for establishing iSCSI connections is as follows:
Step 1 Confirm that the corresponding software package is installed on the host.
Step 2 Assign service IP addresses to the host and storage system.
Step 3 Configure an iSCSI initiator on the host.
Step 4 Configure iSCSI services on the host.
Step 5 On the arrays, find out the initiator and establish connections.
----End
7.1 Checking and Installing the iSCSI Software Package
7.1.1 Checking the iSCSI Software Package
During the installation of Solaris, the corresponding iSCSI software package is installed by
default. You can also run the following command to check whether the software package is
installed in the operating system
bash-3.2# pkginfo |grep iscsi
system SUNWiscsir Sun iSCSI Device Driver (root)
system SUNWiscsitgtr Sun iSCSI Target (Root)
system SUNWiscsitgtu Sun iSCSI Target (Usr)
system SUNWiscsiu Sun iSCSI Management Utilities (usr)
In the preceding example, iSCSI software has been installed on the operating system.
7.1.2 Installing the iSCSI Software Package
If no iSCSI software is installed in the operating system, install the iSCSI software as follows:
Step 1 Insert the CD-ROM loaded with an operating system into the host CD-ROM drive.
HUAWEI SAN Storage Host Connectivity Guide for Solaris 7 Establishing iSCSI Connections
Issue (2017-07-19) Huawei Proprietary and Confidential
Copyright © Huawei Technologies Co., Ltd.
42
Step 2 Run software installation commands on the host.
SUNWiscsir is installed as follows:
bash-3.2# pkgadd -d /cdrom/Solaris_10/Product SUNWiscsir
Processing package instance <SUNWiscsir> from </cdrom/Solaris_10/Product>
Sun iSCSI Device Driver (root)(sparc) 11.10.0,REV=2005.01.04.14.31
Copyright (c) 2010, Oracle and/or its affiliates. All rights reserved.
Using </> as the package base directory.
## Processing package information.
## Processing system information.
15 package pathnames are already properly installed.
## Verifying package dependencies.
## Verifying disk space requirements.
## Checking for conflicts with packages already installed.
## Checking for setuid/setgid programs.
This package contains scripts which will be executed with super-user
permission during the process of installing this package.
Do you want to continue with the installation of <SUNWiscsir> [y,n,?] y
Installing Sun iSCSI Device Driver (root) as <SUNWiscsir>
## Executing preinstall script.
## Installing part 1 of 1.
/kernel/drv/iser.conf
/kernel/drv/sparcv9/iscsi
/kernel/drv/sparcv9/iser
/kernel/misc/sparcv9/idm
/lib/svc/method/iscsi-initiator
/lib/svc/method/iscsid
[ verifying class <none> ]
Modifying /etc/ima.conf
[ verifying class <build> ]
[ verifying class <iscsiconf> ]
[ verifying class <manifest> ]
[ verifying class <rbac> ]
## Executing postinstall script.
System configuration files modified but iser driver not loaded or attached.
Installation of <SUNWiscsir> was successful.
bash-3.2#
----End
7.2 Configuring Service IP Addresses on Storage
Storage systems and hosts use IP addresses to identify each other in iSCSI services. Therefore,
service IP addresses must be configured for storage systems and hosts. The following
describes how to configure service IP addresses for a storage system and a host.
HUAWEI SAN Storage Host Connectivity Guide for Solaris 7 Establishing iSCSI Connections
Issue (2017-07-19) Huawei Proprietary and Confidential
Copyright © Huawei Technologies Co., Ltd.
43
Different versions of storage systems support different IP protocols. Specify the IP protocols
for storage systems based on actual storage system versions and application scenarios.
Observe the following principles when configuring IP addresses of iSCSI ports on storage
systems:
The IP addresses of an iSCSI host port and a management network port must reside on
different network segments.
The IP addresses of an iSCSI host port and a heartbeat network port must reside on
different network segments.
The IP addresses of iSCSI host ports on the same controller must reside on different
network segments. In some storage systems of the latest versions, IP addresses of iSCSI
host ports on the same controller can reside on the same network segment. However, this
configuration is not recommended.
CAUTION
Read-only users are not allowed to modify the IP address of an iSCSI host port.
Modifying the IP address of an iSCSI host port will interrupt the services on the port.
The following explains how to configure IPv4 addresses on the OceanStor T series storage
system and the OceanStor 18000 series enterprise storage system.
7.2.1 OceanStor T Series Storage System
In the ISM navigation tree, choose Device Info > Storage Unit > Ports. In the function pane,
click iSCSI Host Ports.
Select a port and choose IP Address > Modify IPv4 Address in the tool bar, as shown in
Figure 7-1.
Figure 7-1 Modifying IPv4 addresses
In the dialog box that is displayed, enter the new IP address and subnet mask and click OK.
Step 2 If CHAP authentication is not required between the storage system and host, the host initiator
configuration is completed. If CHAP authentication is required, proceed with the following
steps to configure CHAP authentication on the storage system.
HUAWEI SAN Storage Host Connectivity Guide for Solaris 7 Establishing iSCSI Connections
Issue (2017-07-19) Huawei Proprietary and Confidential
Copyright © Huawei Technologies Co., Ltd.
44
Step 3 In the ISM navigation tree, choose SAN Services > Mappings > Initiators. In the function
pane, select the initiator whose CHAP authentication you want to configure and choose
CHAP > CHAP Configuration in the navigation bar, as shown in Figure 7-2.
Figure 7-2 Initiator CHAP configuration
Step 4 In the CHAP Configuration dialog box that is displayed, click Create in the lower right
corner, as shown in Figure 7-3.
HUAWEI SAN Storage Host Connectivity Guide for Solaris 7 Establishing iSCSI Connections
Issue (2017-07-19) Huawei Proprietary and Confidential
Copyright © Huawei Technologies Co., Ltd.
45
Figure 7-3 CHAP Configuration dialog box
In the Create CHAP dialog box that is displayed, enter the CHAP user name and password,
as shown in Figure 7-4.
Figure 7-4 Create CHAP dialog box
The CHAP user name contains 4 to 25 characters and the password contains 12 to 16 characters. The
limitations to CHAP user name and password vary with storage systems. For details, see the help
documentation of corresponding storage systems.
Assign the CHAP user name and password to the initiator, as shown in Figure 7-5.
HUAWEI SAN Storage Host Connectivity Guide for Solaris 7 Establishing iSCSI Connections
Issue (2017-07-19) Huawei Proprietary and Confidential
Copyright © Huawei Technologies Co., Ltd.
46
Figure 7-5 Assigning the CHAP account to the initiator
Step 5 Enable the CHAP account that is assigned to the host.
In the ISM navigation tree, choose SAN Services > Mappings > Initiators. In the function
pane, select the initiator whose CHAP account is to be enabled and choose CHAP > Status
Settings in the navigation bar, as shown in Figure 7-6.
Figure 7-6 Setting CHAP status
HUAWEI SAN Storage Host Connectivity Guide for Solaris 7 Establishing iSCSI Connections
Issue (2017-07-19) Huawei Proprietary and Confidential
Copyright © Huawei Technologies Co., Ltd.
47
In the Status Settings dialog box that is displayed, choose Enabled from the CHAP Status
drop-down list, as shown in Figure 7-7.
Figure 7-7 Enabling CHAP
On the ISM, view the initiator status, as shown in Figure 7-8.
Figure 7-8 Initiator status after CHAP is enabled
----End
7.2.2 OceanStor 18000/T V2 /V3/Dorado V3 Series Enterprise Storage System
After the network is changed, modify iSCSI host port parameters accordingly. Otherwise, the
communication may be abnormal between storage systems and hosts.
Note the following when modifying iSCSI host ports:
Changing the IP address of an iSCSI host port interrupts services. Therefore, ensure that
the storage system is redundantly connected. If the storage system is not redundantly
connected, stop services on the host. Do not change the IP address of an iSCSI host port
unless necessary.
The IP addresses of an iSCSI host port and a heartbeat network port must reside on
different network segments. The default IP address is 127.127.127.10 or 127.127.127.11
and the subnet mask is 255.255.255.0 for the heartbeat network port of the storage
system.
The IP addresses of an iSCSI host port and a management network port must reside on
different network segments.
The IP addresses of an iSCSI host port and a maintenance network port must reside on
different network segments.
The IP address of an iSCSI host port must reside on the same network segment as that of its connected service network port on the host or that of its connected iSCSI host port on
HUAWEI SAN Storage Host Connectivity Guide for Solaris 7 Establishing iSCSI Connections
Issue (2017-07-19) Huawei Proprietary and Confidential
Copyright © Huawei Technologies Co., Ltd.
48
another storage system. If the network segment has no available IP address, add a route
between them.
Perform the following steps:
Step 1 Go to the iSCSI Host Port dialog box.
1. On the right navigation bar, click .
2. In the basic information area of the function pane, click the device icon.
3. In the middle function pane, click the cabinet whose iSCSI ports you want to view.
4. Click the controller enclosure where the desired iSCSI host ports reside. The controller
enclosure view is displayed.
5. Click to switch to the rear view.
6. Click the iSCSI host port whose information you want to modify.
7. The iSCSI Host Port dialog box is displayed.
8. Click Modify.
Step 2 Modify the iSCSI host port.
1. In IPv4 Address or IPv6 Address, enter the IP address of the iSCSI host port.
2. In Subnet Mask or Prefix, enter the subnet mask or prefix of the iSCSI host port.
3. In MTU (Byte), enter the maximum size of data packet that can be transferred between
the iSCSI host port and the host. The value is an integer ranging from 1500 to 9216.
Step 3 Confirm the iSCSI host port modification.
1. Click Apply. The Danger dialog box is displayed.
2. Carefully read the contents of the dialog box. Then click the check box next to the
statement I have read the previous information and understood subsequences of the
operation to confirm the information.
3. Click OK. The Success dialog box is displayed, indicating that the operation succeeded.
4. Click OK.
----End
7.3 Configuring IP Addresses on Hosts
7.3.1 Solaris 10 and Earlier
IP addresses are configured in the same manner for hosts with the Solaris 10 operating system
and earlier.
The procedure is described as follows:
Step 1 Confirm names of network ports connected to storage systems.
Generally, a Solaris-based server has four network ports of the same model. The four network
ports are numbered by 0, 1, 2, and 3. When an operating system is installed, one management
IP address is configured for one network port. For example:
bash-3.2# ifconfig -a
HUAWEI SAN Storage Host Connectivity Guide for Solaris 7 Establishing iSCSI Connections
Issue (2017-07-19) Huawei Proprietary and Confidential
Copyright © Huawei Technologies Co., Ltd.
49
lo0: flags=2001000849<UP,LOOPBACK,RUNNING,MULTICAST,IPv4,VIRTUAL> mtu 8232 index 1
inet 127.0.0.1 netmask ff000000
bge0: flags=1000843<UP,BROADCAST,RUNNING,MULTICAST,IPv4> mtu 1500 index 2
inet 129.22.23.61 netmask ffff0000 broadcast 129.22.255.255
ether 0:14:4f:a3:83:a6
bash-3.2#
In the preceding example, a management IP address (129.22.23.61) is configured for a
network port marked by 0. The type of the network port is bge. The name of the network port
is bge0.
Based on the preceding information, we can conclude that names of remaining three network
ports are bge1, bge2, and bge3. We select the name (bge3) of the last network port for IP
address configuration.
In addition, we can search for names of all network ports by running the following command:
bash-3.2# dladm show-dev
bge0 link: up speed: 100 Mbps duplex: full
bge1 link: unknown speed: 0 Mbps duplex: unknown
bge2 link: unknown speed: 0 Mbps duplex: unknown
bge3 link: down speed: 0 Mbps duplex: unknown
bash-3.2#
In the preceding example, we can see that names of network ports conform to the preceding
conclusion.
Step 2 Create a configuration file for a network port.
Create a configuration file for a network port after it is selected.
The configuration file is saved under the /etc directory and named hostname.xx (xx indicates
the name of the network port). The network port name is included in the file.
For example:
bash-3.2# cat /etc/hostname.bge3
serv01
bash-3.2#
Step 3 Modify the hosts file.
Add the network port name included in the preceding configuration file to the hosts file, and
configure an IP address for the network port.
For example:
bash-3.2# cat /etc/hosts
#
# Internet host table
#
::1 localhost
127.0.0.1 localhost
129.22.23.61 osssvr-1 loghost
192.168.56.200 serv01
bash-3.2#
In the preceding example, we have set the IP address of the network port to 192.168.56.200.
Step 4 Restart network services for the configuration to take effect.
HUAWEI SAN Storage Host Connectivity Guide for Solaris 7 Establishing iSCSI Connections
Issue (2017-07-19) Huawei Proprietary and Confidential
Copyright © Huawei Technologies Co., Ltd.
50
Restart network services on a host by running the following commands:
bash-3.2# svcadm restart network/physical
bash-3.2# ifconfig -a
lo0: flags=2001000849<UP,LOOPBACK,RUNNING,MULTICAST,IPv4,VIRTUAL> mtu 8232 index 1
inet 127.0.0.1 netmask ff000000
bge0: flags=1000843<UP,BROADCAST,RUNNING,MULTICAST,IPv4> mtu 1500 index 2
inet 129.22.23.61 netmask ffff0000 broadcast 129.22.255.255
ether 0:14:4f:a3:83:a6
bge3: flags=1000843<UP,BROADCAST,RUNNING,MULTICAST,IPv4> mtu 1500 index 3
inet 192.168.56.200 netmask ff000000 broadcast 192.255.255.255
ether 0:14:4f:a3:83:a9
bash-3.2#
After IP addresses are configured for hosts and storage systems, run the Ping command to
check whether hosts can communicate with storage systems. If hosts cannot communicate
with storage systems, check whether physical links and IP addresses are correctly configured.
----End
7.3.2 Solaris 11 and Later
The configuration of IP addresses on the host differs greatly from the preceding configuration
in the Solaris 11 operating system and later. This section describes how to configure an IP
address in detail.
Step 1 Switch network management from automatic mode to manual mode.
Switch the network management mode by running the following command:
bash-3.2# netadm enable -p ncp DefaultFixed
Check by running the following command:
bash-3.2# netadm list
netadm: DefaultFixed NCP is enabled;
automatic network management is not available.
'netadm list' is only supported when automatic network management is active.
Step 2 Confirm the name of a network port to be configured.
The command is shown as follows:
dladm show-phys
Command parameters in Solaris 11 and later are different from those in the preceding versions.
For example:
bash-3.2# dladm show-phys
LINK MEDIA STATE SPEED DUPLEX DEVICE
net2 Ethernet up 10000 full hxge0
net3 Ethernet up 10000 full hxge1
net4 Ethernet up 10 full usbecm0
net0 Ethernet up 1000 full igb0
net1 Ethernet up 1000 full igb1
net9 Ethernet unknown 0 half e1000g0
net5 Ethernet unknown 0 half e1000g1
net10 Ethernet unknown 0 half e1000g2
net11 Ethernet unknown 0 half e1000g3
HUAWEI SAN Storage Host Connectivity Guide for Solaris 7 Establishing iSCSI Connections
Issue (2017-07-19) Huawei Proprietary and Confidential
Copyright © Huawei Technologies Co., Ltd.
51
Step 3 Configure a port IP address.
For example, configure the network port net0 by running the following commands:
bash-3.2# ipadm create-ip net0
bash-3.2# ipadm create-addr -T static -a 192.168.56.200/24 net0/v4
In the preceding example, we have configured a fixed IP address (192.168.56.200) for the
network port net0. You can confirm it by running the following command:
bash-3.2# ipadm show-addr
Step 4 Configure a gateway.
If you need to configure a gateway, run the following command:
bash-3.2# route -p add default 192.168.0.1
add net default: gateway 192.168.0.1
add persistent net default: gateway 192.168.0.1
bash-3.2#
In the preceding example, the default gateway is set to 192.168.0.1.
Step 5 Check network configuration by running the ping command.
After IP addresses are configured for the host and storage system, run the ping command to
check whether they can communicate with each other. If the communication fails, check
whether physical links and IP addresses are correct.
----End
7.4 Configuring Initiators on Hosts
After ensuring that the service network between the host and storage system works properly,
you can view and configure an iSCSI initiator on the host. The configuration procedure is as
follows:
Step 1 View information about the initiator on a host.
bash-3.2# iscsiadm list initiator-node
Initiator node name: iqn.1986-03.com.sun:01:00144fa383a6.4fd58856
Initiator node alias: -
Login Parameters (Default/Configured):
Header Digest: NONE/-
Data Digest: NONE/-
Authentication Type: NONE
RADIUS Server: NONE
RADIUS access: unknown
Tunable Parameters (Default/Configured):
Session Login Response Time: 60/-
Maximum Connection Retry Time: 180/-
Login Retry Time Interval: 60/-
Configured Sessions: 1
bash-3.2#
From the preceding command output, it can be found that the initiator name of the host is
iqn.1986-03.com.sun:01:00144fa383a6.4fd58856.
HUAWEI SAN Storage Host Connectivity Guide for Solaris 7 Establishing iSCSI Connections
Issue (2017-07-19) Huawei Proprietary and Confidential
Copyright © Huawei Technologies Co., Ltd.
52
Step 2 If you need to change the initiator name, refer to the following command syntax:
bash-3.2# iscsiadm modify initiator-node -N iqn.2004-10.com.SUN.host-1
bash-3.2# iscsiadm list initiator-node
Initiator node name: iqn.2004-10.com.sun.host-1
Initiator node alias: -
Login Parameters (Default/Configured):
Header Digest: NONE/-
Data Digest: NONE/-
Authentication Type: NONE
RADIUS Server: NONE
RADIUS access: unknown
Tunable Parameters (Default/Configured):
Session Login Response Time: 60/-
Maximum Connection Retry Time: 180/-
Login Retry Time Interval: 60/-
Configured Sessions: 1
bash-3.2#
In the preceding example, the initiator name is changed to iqn.2004-10.com.SUN.host-1.
The iSCSI initiator naming rules are as follows:
The format is iqn.domaindate.reverse.domain.name:optional name.
An iSCSI initiator name can only contain the following characters:
Special characters: hyphens (-), dots (.), and colons (:)
Lowercase letters: a to z
Digits: 0 to 9
In addition, an iSCSI initiator name can contain a maximum of 223 characters.
Step 3 Add or modify the initiator alias. In Solaris, the initiator alias is empty by default. You need
to assign a parameter value for it. Otherwise, the iSCSI connection between the host and
storage system may fail to be established.
Refer to the following command:
bash-3.2# iscsiadm modify initiator-node -A china
bash-3.2# iscsiadm list initiator-node
Initiator node name: iqn.1986-03.com.sun:01:00144fa383a6.4fd58856
Initiator node alias: china
Login Parameters (Default/Configured):
Header Digest: NONE/-
Data Digest: NONE/-
Authentication Type: NONE
RADIUS Server: NONE
RADIUS access: unknown
Tunable Parameters (Default/Configured):
Session Login Response Time: 60/-
Maximum Connection Retry Time: 180/-
Login Retry Time Interval: 60/-
Configured Sessions: 1
bash-3.2#
In the preceding example, the value of Initiator Alias is changed to china.
----End
HUAWEI SAN Storage Host Connectivity Guide for Solaris 7 Establishing iSCSI Connections
Issue (2017-07-19) Huawei Proprietary and Confidential
Copyright © Huawei Technologies Co., Ltd.
53
7.5 Configuring Services on Hosts
If the service IP address of a host and that of a storage system can successfully ping each other,
you can perform other necessary configurations on the host to establish a connection between
the host and storage system.
Step 1 Enable iSCSI services on a host.
Check whether iSCSI services have been enabled by running the following command:
bash-3.2# svcs|grep iscsi
online 16:58:10 svc:/network/iscsi/initiator:default
bash-3.2#
In the preceding example, iSCSI services have been enabled. If iSCSI services have not been
enabled, run the svcadm enable svc:/network/iscsi/initiator:default command.
Step 2 Select a search mode.
A host with a Solaris operating system is provided with two search modes: dynamic device
search and static device search.
Dynamic device search
Two dynamic device search methods, including SendTargets and iSNS, are available.
− SendTargets
If numerous targets, such as iSCSI-to-FC network bridges, are detected on iSCSI
nodes, this method can be used to combine IP addresses with port numbers of these
nodes and search for devices by enabling the SendTargets function of the iSCSI
initiator.
− Internet Storage Name Service (iSNS)
It enables the iSCSI initiator to search for accessible targets with minimum
configuration. It also notifies the iSCSI initiator of status change of a storage node.
The default port number of the iSNS server is 3205.
Static device search
If a small number of targets are detected on iSCSI nodes or targets that the initiator
attempts to access are restricted, you can configure target-name in static mode based on
rules for naming static target addresses.
For example, we can set the search mode to SendTargets.
bash-3.2# iscsiadm modify discovery --sendtargets enable
bash-3.2#
bash-3.2# iscsiadm list discovery
Discovery:
Static: disabled
Send Targets: enabled
iSNS: disabled
bash-3.2#
In the preceding example, SendTargets has been enabled.
Step 3 Add a detected target. Set the service IP address of a storage system to 192.168.56.201. Run
the following commands on the host:
bash-3.2# iscsiadm add discovery-address 192.168.56.201:3260
bash-3.2# iscsiadm list discovery-address
HUAWEI SAN Storage Host Connectivity Guide for Solaris 7 Establishing iSCSI Connections
Issue (2017-07-19) Huawei Proprietary and Confidential
Copyright © Huawei Technologies Co., Ltd.
54
Discovery Address: 192.168.56.201:3260
bash-3.2#
Step 4 Create an iSCSI device link for local systems.
bash-3.2# devfsadm -i iscsi
Step 5 If CHAP authentication is not needed between the host and storage system, no further action
is required. To configure CHAP authentication, go to the next step.
Step 6 Configure CHAP authentication information on the host.
Specify relevant parameters on the host by running the iscsiadm command. The command
format is shown as follows:
bash-3.2# iscsiadm modify initiator-node help
iscsiadm: at least one option required
iscsiadm modify initiator-node <OPTIONS>
OPTIONS:
-N, --node-name <initiator node name>
-A, --node-alias <initiator node alias>
-h, --headerdigest <none|CRC32>
-d, --datadigest <none|CRC32>
-C, --CHAP-secret (exclusive)
-a, --authentication <CHAP|none>
-R, --radius-access <enable|disable>
-r, --radius-server <<IP address>[:port]>
-P, --radius-shared-secret (exclusive)
-H, --CHAP-name <CHAP name>
-c, --configured-sessions <<# sessions>|<IP Address>[,<IP Address>]*>
-T, --tunable-param <tunable-prop=value>
For more information, please see iscsiadm(1M)
bash-3.2#
For example:
bash-3.2# iscsiadm modify initiator-node -a CHAP
bash-3.2# iscsiadm modify initiator-node -H root
bash-3.2# iscsiadm modify initiator-node -C
Enter secret:
Re-enter secret:
bash-3.2#
bash-3.2# iscsiadm list initiator-node
Initiator node name: iqn.2004-10.com.sun.host-1
Initiator node alias: china
Login Parameters (Default/Configured):
Header Digest: NONE/-
Data Digest: NONE/-
Authentication Type: CHAP
CHAP Name: root
RADIUS Server: NONE
RADIUS access: unknown
Tunable Parameters (Default/Configured):
Session Login Response Time: 60/-
Maximum Connection Retry Time: 180/-
Login Retry Time Interval: 60/-
HUAWEI SAN Storage Host Connectivity Guide for Solaris 7 Establishing iSCSI Connections
Issue (2017-07-19) Huawei Proprietary and Confidential
Copyright © Huawei Technologies Co., Ltd.
55
Configured Sessions: 1
bash-3.2#
----End
7.6 Establishing Connections
After completing the preceding preparations, establish connections between the host and
storage system. The detailed steps are described as follows:
Step 1 On the storage system, add LUNs to the host. On the host, run the following command to
establish a connection between the host and storage system.
bash-3.2# devfsadm -i iscsi
bash-3.2#
After the preceding command is executed, the initiator status displayed on the storage system
changes to Connected.
Step 2 On the host, run the format scan command to discover the mapped LUNs.
----End
HUAWEI SAN Storage Host Connectivity Guide for Solaris 8 Mapping and Using LUNs
Issue (2017-07-19) Huawei Proprietary and Confidential
Copyright © Huawei Technologies Co., Ltd.
56
8 Mapping and Using LUNs
8.1 Mapping LUNs to Hosts
8.2 Scanning for LUNs on Hosts
After mapping LUNs on storage systems, perform the following steps on hosts to discover the
mapped LUNs:
Step 1 View all information about configurable hardware.
View all information about configurable hardware and re-scan for LUNs by running the
following command:
bash-3.2# cfgadm -al
Ap_Id Type Receptacle Occupant Condition
c0 scsi-bus connected configured unknown
c0::dsk/c0t0d0 CD-ROM connected configured unknown
c1 scsi-sata connected configured unknown
c1::dsk/c1t0d0 disk connected configured unknown
c1::dsk/c1t1d0 disk connected configured unknown
c1::dsk/c1t2d0 disk connected configured unknown
c1::dsk/c1t3d0 disk connected configured unknown
c7 fc-private connected configured unknown
c7::2013323232323232 disk connected configured unknown
c8 fc-private connected configured unknown
c8::2003323232323232 disk connected configured unknown
usb0/1 unknown empty unconfigured ok
usb0/2 unknown empty unconfigured ok
usb0/3 unknown empty unconfigured ok
usb1/1.1 unknown empty unconfigured ok
usb1/1.2 unknown empty unconfigured ok
usb1/1.3 unknown empty unconfigured ok
usb1/1.4 unknown empty unconfigured ok
usb1/2 unknown empty unconfigured ok
usb1/3 unknown empty unconfigured ok
usb2/1 unknown empty unconfigured ok
usb2/2 unknown empty unconfigured ok
usb2/3 unknown empty unconfigured ok
usb2/4 unknown empty unconfigured ok
HUAWEI SAN Storage Host Connectivity Guide for Solaris 8 Mapping and Using LUNs
Issue (2017-07-19) Huawei Proprietary and Confidential
Copyright © Huawei Technologies Co., Ltd.
57
usb2/5 unknown empty unconfigured ok
usb2/6 unknown empty unconfigured ok
usb2/7 unknown empty unconfigured ok
usb2/8 unknown empty unconfigured ok
bash-3.2#
Step 2 View information about disks identified by the operating system.
On a host, view information about identified LUNs by running the following command:
bash-3.2# format
Searching for disks...done
c7t28d1: configured with capacity of 4.00GB
c8t4d1: configured with capacity of 4.00GB
AVAILABLE DISK SELECTIONS:
0. c1t0d0 <FUJITSU-MAY2073RCSUN72G-0501 cyl 14087 alt 2 hd 24 sec 424>
/pci@1e,600000/pci@0/pci@a/pci@0/pci@8/scsi@1/sd@0,0
1. c1t1d0 <FUJITSU-MAY2073RCSUN72G-0501 cyl 14087 alt 2 hd 24 sec 424>
/pci@1e,600000/pci@0/pci@a/pci@0/pci@8/scsi@1/sd@1,0
2. c1t2d0 <SUN72G cyl 14087 alt 2 hd 24 sec 424>
/pci@1e,600000/pci@0/pci@a/pci@0/pci@8/scsi@1/sd@2,0
3. c1t3d0 <FUJITSU-MAY2073RCSUN72G-0501 cyl 14087 alt 2 hd 24 sec 424>
/pci@1e,600000/pci@0/pci@a/pci@0/pci@8/scsi@1/sd@3,0
4. c7t28d0 <HUAWEI-S2600T-2102 cyl 10920 alt 2 hd 30 sec 64>
/pci@1f,700000/pci@0/fibre-channel@2/fp@0,0/ssd@w2013323232323232,0
5. c7t28d1 <HUAWEI-S2600T-2102 cyl 4367 alt 2 hd 30 sec 64>
/pci@1f,700000/pci@0/fibre-channel@2/fp@0,0/ssd@w2013323232323232,1
6. c8t4d0 <HUAWEI-S2600T-2102 cyl 10920 alt 2 hd 30 sec 64>
/pci@1f,700000/pci@0/fibre-channel@2,1/fp@0,0/ssd@w2003323232323232,0
7. c8t4d1 <HUAWEI-S2600T-2102 cyl 4367 alt 2 hd 30 sec 64>
/pci@1f,700000/pci@0/fibre-channel@2,1/fp@0,0/ssd@w2003323232323232,1
Specify disk (enter its number):
In the preceding example, drive letters of LUNs on four paths mapped from storage systems
have been identified on hosts. c7t28d0 and c8t4d0 indicate drive letters of one LUN on two
paths. c7t28d1 and c8t4d1 indicate drive letters of another LUN on two paths. Here, only two
LUNs are mapped to hosts.
Step 3 Label detected LUNs.
Disks cannot be used by Solaris operating systems until they are labeled.
For example:
bash-3.2# format
Searching for disks...done
c7t28d1: configured with capacity of 4.00GB
c8t4d1: configured with capacity of 4.00GB
AVAILABLE DISK SELECTIONS:
0. c1t0d0 <FUJITSU-MAY2073RCSUN72G-0501 cyl 14087 alt 2 hd 24 sec 424>
/pci@1e,600000/pci@0/pci@a/pci@0/pci@8/scsi@1/sd@0,0
1. c1t1d0 <FUJITSU-MAY2073RCSUN72G-0501 cyl 14087 alt 2 hd 24 sec 424>
HUAWEI SAN Storage Host Connectivity Guide for Solaris 8 Mapping and Using LUNs
Issue (2017-07-19) Huawei Proprietary and Confidential
Copyright © Huawei Technologies Co., Ltd.
58
/pci@1e,600000/pci@0/pci@a/pci@0/pci@8/scsi@1/sd@1,0
2. c1t2d0 <SUN72G cyl 14087 alt 2 hd 24 sec 424>
/pci@1e,600000/pci@0/pci@a/pci@0/pci@8/scsi@1/sd@2,0
3. c1t3d0 <FUJITSU-MAY2073RCSUN72G-0501 cyl 14087 alt 2 hd 24 sec 424>
/pci@1e,600000/pci@0/pci@a/pci@0/pci@8/scsi@1/sd@3,0
4. c7t28d0 <HUAWEI-S2600T-2102 cyl 10920 alt 2 hd 30 sec 64>
/pci@1f,700000/pci@0/fibre-channel@2/fp@0,0/ssd@w2013323232323232,0
5. c7t28d1 <HUAWEI-S2600T-2102 cyl 4367 alt 2 hd 30 sec 64>
/pci@1f,700000/pci@0/fibre-channel@2/fp@0,0/ssd@w2013323232323232,1
6. c8t4d0 <HUAWEI-S2600T-2102 cyl 10920 alt 2 hd 30 sec 64>
/pci@1f,700000/pci@0/fibre-channel@2,1/fp@0,0/ssd@w2003323232323232,0
7. c8t4d1 <HUAWEI-S2600T-2102 cyl 4367 alt 2 hd 30 sec 64>
/pci@1f,700000/pci@0/fibre-channel@2,1/fp@0,0/ssd@w2003323232323232,1
Specify disk (enter its number): 7
selecting c8t4d1
[disk formatted]
Disk not labeled. Label it now? yes
FORMAT MENU:
disk - select a disk
type - select (define) a disk type
partition - select (define) a partition table
current - describe the current disk
format - format and analyze the disk
repair - repair a defective sector
label - write label to the disk
analyze - surface analysis
defect - defect list management
backup - search for backup labels
verify - read and display labels
save - save new disk/partition definitions
inquiry - show vendor, product and revision
volname - set 8-character volume name
!<cmd> - execute <cmd>, then return
quit
format> p
PARTITION MENU:
0 - change `0' partition
1 - change `1' partition
2 - change `2' partition
3 - change `3' partition
4 - change `4' partition
5 - change `5' partition
6 - change `6' partition
7 - change `7' partition
select - select a predefined table
modify - modify a predefined partition table
name - name the current table
print - display the current table
label - write partition map and label to the disk
!<cmd> - execute <cmd>, then return
quit
HUAWEI SAN Storage Host Connectivity Guide for Solaris 8 Mapping and Using LUNs
Issue (2017-07-19) Huawei Proprietary and Confidential
Copyright © Huawei Technologies Co., Ltd.
59
partition> p
Current partition table (default):
Total disk cylinders available: 4367 + 2 (reserved cylinders)
Part Tag Flag Cylinders Size Blocks
0 root wm 0 - 136 128.44MB (137/0/0) 263040
1 swap wu 137 - 273 128.44MB (137/0/0) 263040
2 backup wu 0 - 4366 4.00GB (4367/0/0) 8384640
3 unassigned wm 0 0 (0/0/0) 0
4 unassigned wm 0 0 (0/0/0) 0
5 unassigned wm 0 0 (0/0/0) 0
6 usr wm 274 - 4366 3.75GB (4093/0/0) 7858560
7 unassigned wm 0 0 (0/0/0) 0
partition>
In the preceding example, we first select the disk 7 whose drive letter is c8t4d1. "Label it
now?" is displayed on the host as the disk is not labeled. After we enter yes, the host displays
operable commands after labeling the disk. We have queried information about disk partitions.
Two disk types, including VTOC and EFI, are available on a Solaris operating system.
For a disk with a capacity of smaller than 1 TB, its type is VTOC by default when it is being labeled. The disk
consists of 8 partitions numbered from 0 to 7. Partition 2 indicates the whole disk. For a disk with a capacity
of larger than 2 TB, its type is EFI by default when it is being labeled.
The x86-based Solaris operating system disk whose type is VTOC consists of 10 partitions numbered from 0
to 9. The disk whose type is EFI consists of 9 partitions numbered from 0 to 8. The SPARC-based Solaris
operating system disk whose type is VTOC consists of 8 partitions numbered from 0 to 7. The disk whose
type is EFI consists of 9 partitions numbered from 0 to 8.
For operating systems earlier than Solaris 11, the disk capacity is smaller than 1 TB if the disk type is VTOC.
The disk capacity is larger than 1 TB if the disk type is EFI.
For Solaris 11 and later, the addressable disk capacity is within 2 TB if the disk type is VTOC. The disk
capacity is larger than 2 TB if the disk type is EFI.
----End
8.3 Using LUNs on Hosts
This section describes SPARC- and x86-based Solaris operating systems.
8.3.1 SPARC
After detecting mapped LUNs on a host, you can use a bare metal to configure corresponding
services or reuse the bare metal after creating corresponding file systems.
For SPARC-based Solaris operating systems, you can create a file system on a drive. In
addition, you can manage disks with volume management software installed on a host, and
then create a file system on managed devices.
The following shows how to create a file system on a drive:
bash-3.2# newfs /dev/rdsk/c8t4d1s2
HUAWEI SAN Storage Host Connectivity Guide for Solaris 8 Mapping and Using LUNs
Issue (2017-07-19) Huawei Proprietary and Confidential
Copyright © Huawei Technologies Co., Ltd.
60
newfs: construct a new file system /dev/rdsk/c8t4d1s2: (y/n)? y
/dev/rdsk/c8t4d1s2: 8384640 sectors in 4367 cylinders of 30 tracks, 64 sectors
4094.1MB in 86 cyl groups (51 c/g, 47.81MB/g, 6016 i/g)
super-block backups (for fsck -F ufs -o b=#) at:
32, 98016, 196000, 293984, 391968, 489952, 587936, 685920, 783904, 881888,
7442720, 7540704, 7638688, 7736672, 7834656, 7932640, 8030624, 8128608,
8226592, 8324576
bash-3.2#
bash-3.2# mount /dev/dsk/c8t4d1s2 /mountpoint/mnt1/
In the preceding example, we have created a UFS on the c8t4d1 drive and mounted it under
the /mountpoint/mnt1/ directory.
8.3.2 x86
For x86-based Solaris operating systems, you need to create partitions before using mapped
LUNs.
Create partitions by running the fdisk command. For example:
bash-3.00# format -e
Searching for disks...done
AVAILABLE DISK SELECTIONS:
0. c0t0d0 <DEFAULT cyl 35027 alt 2 hd 255 sec 63>
/pci@0,0/pci8086,25e3@3/pci1028,1f0c@0/sd@0,0
1. c0t1d0 <DEFAULT cyl 35537 alt 2 hd 255 sec 63>
/pci@0,0/pci8086,25e3@3/pci1028,1f0c@0/sd@1,0
2. c0t2d0 <DEFAULT cyl 2767 alt 2 hd 255 sec 63>
/pci@0,0/pci8086,25e3@3/pci1028,1f0c@0/sd@2,0
3. c4t60022A11000AFD57000370FB00000000d0 <DEFAULT cyl 1021 alt 2 hd 64 sec 32>
/scsi_vhci/disk@g60022a11000afd57000370fb00000000
4. c4t60022A11000AFD57000377C800000001d0 <DEFAULT cyl 1020 alt 2 hd 64 sec 32>
/scsi_vhci/disk@g60022a11000afd57000377c800000001
5. c4t60022A11000AFD57000557D700000002d0 <DEFAULT cyl 1021 alt 2 hd 64 sec 32>
/scsi_vhci/disk@g60022a11000afd57000557d700000002
6. c4t60022A11000AFD57000613A60000000Ad0 <DEFAULT cyl 13052 alt 2 hd 255 sec 63>
/scsi_vhci/disk@g60022a11000afd57000613a60000000a
7. c4t60022A11000AFD57000613D40000000Bd0 <DEFAULT cyl 13052 alt 2 hd 255 sec 63>
/scsi_vhci/disk@g60022a11000afd57000613d40000000b
8. c4t60022A11000AFD57000872C90000000Ed0 <DEFAULT cyl 1021 alt 2 hd 64 sec 32>
/scsi_vhci/disk@g60022a11000afd57000872c90000000e
Specify disk (enter its number): 5
selecting c4t60022A11000AFD57000557D700000002d0
[disk formatted]
FORMAT MENU:
disk - select a disk
type - select (define) a disk type
partition - select (define) a partition table
current - describe the current disk
format - format and analyze the disk
fdisk - run the fdisk program
repair - repair a defective sector
HUAWEI SAN Storage Host Connectivity Guide for Solaris 8 Mapping and Using LUNs
Issue (2017-07-19) Huawei Proprietary and Confidential
Copyright © Huawei Technologies Co., Ltd.
61
label - write label to the disk
analyze - surface analysis
defect - defect list management
backup - search for backup labels
verify - read and display labels
save - save new disk/partition definitions
inquiry - show vendor, product and revision
scsi - independent SCSI mode selects
cache - enable, disable or query SCSI disk cache
volname - set 8-character volume name
!<cmd> - execute <cmd>, then return
quit
format> fdisk
No fdisk table exists. The default partition for the disk is:
a 100% "SOLARIS System" partition
Type "y" to accept the default partition, otherwise type "n" to edit the
partition table.
y
format> p
PARTITION MENU:
0 - change `0' partition
1 - change `1' partition
2 - change `2' partition
3 - change `3' partition
4 - change `4' partition
5 - change `5' partition
6 - change `6' partition
7 - change `7' partition
9 - change `9' partition
select - select a predefined table
modify - modify a predefined partition table
name - name the current table
print - display the current table
label - write partition map and label to the disk
!<cmd> - execute <cmd>, then return
quit
partition> p
Current partition table (original):
Total disk cylinders available: 1020 + 2 (reserved cylinders)
Part Tag Flag Cylinders Size Blocks
0 unassigned wm 0 0 (0/0/0) 0
1 unassigned wm 0 0 (0/0/0) 0
2 backup wu 0 - 1019 1020.00MB (1020/0/0) 2088960
3 unassigned wm 0 0 (0/0/0) 0
4 unassigned wm 0 0 (0/0/0) 0
5 unassigned wm 0 0 (0/0/0) 0
6 unassigned wm 0 0 (0/0/0) 0
7 unassigned wm 0 0 (0/0/0) 0
8 boot wu 0 - 0 1.00MB (1/0/0) 2048
9 unassigned wm 0 0 (0/0/0) 0
HUAWEI SAN Storage Host Connectivity Guide for Solaris 8 Mapping and Using LUNs
Issue (2017-07-19) Huawei Proprietary and Confidential
Copyright © Huawei Technologies Co., Ltd.
62
partition>
Add s2 (indicates the whole disk) next to a drive letter.
For details about the application of volume management software configured for hosts, see
section 10.1 "SVM."
For details about multipathing management, see chapter 9 "Multipathing Management."
8.4 Troubleshooting
8.4.1 Symptom
When a user expands the LUN capacity to larger than 1 TB on a storage system, runs the
format command, and selects type > 0. Auto configure, the expanded capacity fails to be
updated on the system.
8.4.2 Root Cause Analysis
By default, the SMI labels a disk with a capacity of smaller than 1 TB as VTOC in Solaris 10.
After the disk is expanded to a capacity larger than 1 TB, its type needs to be changed to EFI.
Otherwise, capacity expansion fails.
8.4.3 Solution
If the target capacity is larger than 1 TB, change the disk type to EFI before expansion.
Exercise caution when changing the type of a disk stored with data to EFI, because it may
cause data loss.
To change the disk type to EFI, perform the following steps:
Step 1 Enter the following command:
bash-3.2#format -e
After command execution, all LUNs mapped to a host are displayed. Enter Arabic numerals
used for LUN operations next to Specify disk.
Step 2 Run the Verify command as follows:
format>verify
HUAWEI SAN Storage Host Connectivity Guide for Solaris 8 Mapping and Using LUNs
Issue (2017-07-19) Huawei Proprietary and Confidential
Copyright © Huawei Technologies Co., Ltd.
63
Step 3 Run the label command as follows:
format>label
Step 4 In the box next to Specify Label type, enter 1 to select EFI for the disk type.
----End
HUAWEI SAN Storage Host Connectivity Guide for Solaris 9 Multipathing Management
Issue (2017-07-19) Huawei Proprietary and Confidential
Copyright © Huawei Technologies Co., Ltd.
64
9 Multipathing Management
9.1 Overview
Solaris supports two kinds of multipathing software, including UltraPath and StorEdge Traffic
Manager Software (STMS).
UltraPath is the Huawei-developed multipathing software. For details about its installation
and configuration, see relevant user guides.
STMS is the Solaris operating system–based multipathing software to manage devices that are
accessed by hosts on multiple paths.
This section describes STMS in detail.
9.2 Functions and Features of STMS
9.2.1 Functions
STMS has the following functional features:
Manages multipathing configuration.
Enables I/O load balancing on a group of HBAs.
Implements path switchover when connection links or controllers fail.
Supports single instance multipath devices.
Enables dynamic re-configuration.
9.2.2 Load Balancing Policies
STMS can be used based on the following two load balancing policies:
Round_robin (default)
I/Os are concurrently delivered on all paths.
none
I/Os can be delivered on only one path to a LUN. When the current path for delivering
I/Os fails, I/Os are delivered on another path.
HUAWEI SAN Storage Host Connectivity Guide for Solaris 9 Multipathing Management
Issue (2017-07-19) Huawei Proprietary and Confidential
Copyright © Huawei Technologies Co., Ltd.
65
9.3 Operating Environment Requirements
STMS is compatible with Solaris 8, 9, 10, and 11.
9.4 Installing Multipathing Software
You need to manually install software packages on operating systems earlier than Solaris 10.
For Solaris 10 and later, these software packages have been installed on CD-ROMs by default
but have not been enabled.
For Solaris 8 and 9, StorageTek SAN Foundation is used. The latest version of StorageTek
SAN Foundation is SAN 4.4.
You can obtain software upgrade records and version installation documents at:
http://www.oracle.com/technetwork/documentation/san-software-194281.html
9.5 Configuring and Enabling Multipathing Function
This section describes the multipathing configurations on interconnected Solaris-running
hosts and HUAWEI storage systems.
HUAWEI storage firmwares' support for the OS-inherent multipathing HyperMetro solution
is as follows:
Old-version HUAWEI storage (namely, storage that does not support multi-controller
ALUA or ALUA HyperMetro): OceanStor T V1/T V2/18000
V1/V300R001/V300R002/V300R003C00/V300R003C10/V300R005/Dorado V300R001C00
New-version HUAWEI storage (namely, storage that supports multi-controller ALUA and ALUA HyperMetro): V300R003C20/V300R006C00 (only V300R006C00SPC100 and
later)/Dorado V300R001C01 (only V300R001C01SPC100 and later)
9.5.1 Multipathing Configuration for New-Version HUAWEI Storage
9.5.1.1 HyperMetro Working Modes
Typically, HyperMetro works in load balancing mode or local preferred mode. The typical
working modes are valid only when both the storage system and host use ALUA. It is advised
to set the host's path selection policy to round-robin. If HyperMetro works in load balancing
mode, the host's path selection policy must be round-robin. If the host does not use ALUA or
its path selection policy is not round-robin, the host's multipathing policy determines the
working mode of HyperMetro.
HyperMetro storage arrays can be classified into a local and a remote array by their distance
to the host. The one closer to the host is the local array and the other one is the remote array.
Table 9-1 describes the configuration methods and application scenarios of the typical
working modes.
HUAWEI SAN Storage Host Connectivity Guide for Solaris 9 Multipathing Management
Issue (2017-07-19) Huawei Proprietary and Confidential
Copyright © Huawei Technologies Co., Ltd.
66
Table 9-1 Configuration methods and application scenarios of the typical working modes
Working Mode
Configuration Method Application Scenario
Load balancing
mode
Enable ALUA on the host and set the path
selection policy to round-robin.
Configure a switchover mode that supports
ALUA for both HyperMetro storage arrays'
initiators that are added to the host.
Set the path type for both storage arrays'
initiators to the optimal path.
The distance between
both HyperMetro
storage arrays is less
than 1 km. For example,
they are in the same
equipment room or on
the same floor.
Local preferred
mode
Enable ALUA on the host. It is advised to set
the path selection policy to round-robin.
Configure a switchover mode that supports
ALUA for both HyperMetro storage arrays'
initiators that are added to the host.
Set the path type for the local storage array's
initiators to the optimal path and that for the
remote storage array's initiators to the
non-optimal path.
The distance between
both HyperMetro
storage arrays is greater
than 1 km. For example,
they are in different
locations or data centers.
Other modes Set the initiator switchover mode for the
HyperMetro storage arrays by following
instructions in the follow-up chapters in this
guide. The path type does not require manual
configuration.
User-defined
9.5.1.1.2 Working Principles and Failover
When ALUA works, the host multipathing software divides the physical paths to disks into
Active Optimized (AO) and Active Non-optimized (AN) paths. The host delivers services to
the storage system via the AO paths preferentially.
An AO path is the optimal I/O access path and is between the host and a working
controller.
An AN path is the suboptimal I/O access path and is between the host and a non-working
controller.
When HyperMetro works in load balancing mode, the host multipathing software selects the
paths to the working controllers on both HyperMetro storage arrays as the AO paths, and
those to the other controllers as the AN paths. The host accesses the storage arrays via the AO
paths. If an AO path fails, the host delivers I/Os to another AO path. If the working controller
of a storage array fails, the system switches the other controller to the working mode and
maintains load balancing.
Host
A B A B
AO AOAN AN
Host
A B A B
AO AOAO’AN
Site A Site B Site A Site B
Path failure SP failure
HUAWEI SAN Storage Host Connectivity Guide for Solaris 9 Multipathing Management
Issue (2017-07-19) Huawei Proprietary and Confidential
Copyright © Huawei Technologies Co., Ltd.
67
When HyperMetro works in local preferred mode, the host multipathing software selects the
paths to the working controller on the local storage array as the AO paths. This ensures that
the host delivers I/Os only to the working controller on the local storage array, reducing link
consumption. If all AO paths fail, the host delivers I/Os to the AN paths on the non-working
controller. If the working controller of the local storage array fails, the system switches the
other controller to the working mode and maintains the local preferred mode.
Host
A B A B
AO ANAN AN
Host
A B A B
AO ANAO’ AN
Site A Site B Site A Site B
Path failure SP failure
9.5.1.2 Introduction to ALUA
9.5.1.2.1 ALUA Definition
Asymmetric Logical Unit Access (ALUA) is a multi-target port access model. In a
multipathing state, the ALUA model provides a way of presenting active/passive LUNs to a
host and offers a port status switching interface to switch over the working controller. For
example, when a host multipathing program that supports ALUA detects a port status change
(the port becomes unavailable) on a faulty controller, the program will automatically switch
subsequent I/Os to the other controller.
9.5.1.2.2 Support by HUAWEI Storage
Old-version HUAWEI storage supports ALUA only in dual-controller configuration, but not
in multi-controller or HyperMetro configuration.
New-version HUAWEI storage supports ALUA in dual-controller, multi-controller, and
HyperMetro configurations.
Table 9-2 describes the HUAWEI storage's support for ALUA.
Table 9-2 HUAWEI storage's support for ALUA
Storage Type Version Remarks
Old-version HUAWEI
storage (namely,
storage that does not
support multi-controller
ALUA or ALUA
HyperMetro)
T V1/T V2/18000
V1/V300R001/V300R002/V300R
003C00/V300R003C10/V300R00
5/Dorado V300R001C00
New-version HUAWEI
storage (namely,
storage that supports
multi-controller ALUA
and ALUA
HyperMetro)
V300R003C20/V300R006C00/D
orado V300R001C01
V300R006C00: refers to
only
V300R006C00SPC100 and
later versions.
Dorado V300R001C01: refers to only
HUAWEI SAN Storage Host Connectivity Guide for Solaris 9 Multipathing Management
Issue (2017-07-19) Huawei Proprietary and Confidential
Copyright © Huawei Technologies Co., Ltd.
68
V300R001C01SPC100 and
later versions.
9.5.1.2.3 ALUA Impacts
ALUA is mainly applicable to a storage system that has one (only one) preferred LUN
controller. All host I/Os can be routed through different controllers to the working controller
for execution. The storage ALUA will instruct the hosts to deliver I/Os preferentially from the
LUN working controller, thereby reducing the I/O routing-consumed resources on the
non-working controllers.
Once the LUN working controller's all I/O paths are disconnected, the host I/Os will be
delivered only from a non-working controller and then routed to the working controller for
execution. This scenario must be avoided.
9.5.1.2.4 Suggestions for Using ALUA on HUAWEI Storage
To prevent I/Os from being delivered to a non-working controller, you are advised to:
Ensure that the LUN home/working controllers are evenly distributed on storage
systems.
A change to the storage system (node fault or replacement) may cause an I/O path
switchover. Ensure that the host always tries the best to select the optimal path to deliver
I/Os.
Prevent all host service I/Os from being delivered only to one controller, thereby
preventing load unbalancing on the storage system.
9.5.1.3 Initiator Mode
9.5.1.3.1 Initiator Parameter Description
Table 9-3 Initiator parameter description
Parameter Description Example
Uses
third-party
multipath
software
This parameter is displayed only after an initiator
has been added to the host.
If LUNs have been mapped to the host before you
enable or disable this parameter, restart the host
after you configure this parameter.
You do not need to enable this parameter on a host
with UltraPath.
Enabled
Switchover
Mode
Path switchover mode
The system supports the following modes:
early-version ALUA: default value of
Switchover Mode for an upgrade from an
earlier version to the current version. The
detailed requirements are as follows:
− The storage system is upgraded from
V300R003C10 and earlier to
V300R003C20 or V300R006C00SPC100
HUAWEI SAN Storage Host Connectivity Guide for Solaris 9 Multipathing Management
Issue (2017-07-19) Huawei Proprietary and Confidential
Copyright © Huawei Technologies Co., Ltd.
69
Parameter Description Example
and later; from V300R005 to
V300R006C00SPC100 and later; from
Dorado V300R001C00 to Dorado
V300R001C01SPC100 and later.
− Before the upgrade, the storage system has a
single or dual controllers and has enabled
ALUA.
common ALUA: applies to V300R003C20 and
later, V300R006C00SPC100 and later, or
Dorado V300R001C01SPC100 and later. The
detailed requirements are as follows:
− The storage system version is V300R003C20,
V300R006C00SPC100, Dorado
V300R001C01SPC100, or later.
− The OS of the host that connects to the storage
system is SUSE, Red Hat 6.X, Windows
Server 2012 (using Emulex HBAs),
Windows Server 2008 (using Emulex
HBAs), or HP-UX 11i V3.
ALUA not used: does not support ALUA or
HyperMetro. This mode is used when a host
such as HP-UX 11i V2 does not support ALUA
or ALUA is not needed.
Special mode: supports ALUA and has multiple
values. It applies to V300R003C20 and later,
V300R006C00SPC100 and later, or Dorado
V300R001C01SPC100 and later. It is used by
host operating systems that are not supported by
the common ALUA mode. The detailed
requirements are as follows:
− The storage system version V300R003C20,
V300R006C00SPC100, Dorado
V300R001C01SPC100, or later.
− The OS of the host that connects to the storage
system is VMware, AIX, Red Hat 7.X,
Windows Server 2012 (using QLogic
HBAs), or Windows Server 2008 (using
QLogic HBAs).
Special mode
type
Special modes support ALUA and apply to
V300R003C20 and later, V300R006C00SPC100
and later, or Dorado V300R001C01SPC100 and
later. The detailed requirements are as follows:
Mode 0:
− The host and storage system must be
connected using a Fibre Channel network.
− The OS of the host that connects to the storage
system is Red Hat 7.X, Windows Server
2012 (using QLogic HBAs), or Windows
Server 2008 (using QLogic HBAs).
Mode 0
HUAWEI SAN Storage Host Connectivity Guide for Solaris 9 Multipathing Management
Issue (2017-07-19) Huawei Proprietary and Confidential
Copyright © Huawei Technologies Co., Ltd.
70
Parameter Description Example
Mode 1:
− The OS of the host that connects to the storage
system is AIX or VMware.
− HyperMetro works in load balancing mode.
Mode 2:
− The OS of the host that connects to the storage
system is AIX or VMware.
− HyperMetro works in local preferred mode.
Path Type The value can be either Optimal Path or
Non-Optimal Path.
When HyperMetro works in load balancing
mode, set the Path Type for the initiators of
both the local and remote storage arrays to
Optimal Path. Enable ALUA on both the host
and storage arrays. If the host uses the
round-robin multipathing policy, it delivers I/Os
to both storage arrays in round-robin mode.
When HyperMetro works in local preferred
mode, set the Path Type for the initiator of the
local storage array to Optimal Path, and that of
the remote storage array to Non-Optimal Path.
Enable ALUA on both the host and storage
arrays. The host delivers I/Os to the local
storage array preferentially.
Optimal Path
Configure the initiators according to the requirements of each OS. The initiators that are
added to the same host must be configured with the same switchover mode. Otherwise, host
services may be interrupted.
After the initiator mode is configured on a storage array, you must restart the host for the
configuration to take effect.
9.5.1.3.2 Configuring the Initiators
If you want to configure the initiator mode, perform the following operations.
Step 1 Go to the host configuration page.
Open OceanStor DeviceManager. In the right navigation tree, click Provisioning and then
click Host, as shown in Figure 9-1.
HUAWEI SAN Storage Host Connectivity Guide for Solaris 9 Multipathing Management
Issue (2017-07-19) Huawei Proprietary and Confidential
Copyright © Huawei Technologies Co., Ltd.
71
Figure 9-1 Going to the host configuration page
Step 2 Select an initiator of which information you want to modify.
On the Host tab page, select a host you want to modify. Then select the initiator (on the host)
you want to modify. Click Modify.
Figure 9-2 Selecting an initiator of which information you want to modify
Step 3 Modify the initiator information.
In the Modify Initiator dialog box that is displayed, modify the initiator information based on
the requirements of your operating system. Figure 9-3 shows the initiator information
modification page.
HUAWEI SAN Storage Host Connectivity Guide for Solaris 9 Multipathing Management
Issue (2017-07-19) Huawei Proprietary and Confidential
Copyright © Huawei Technologies Co., Ltd.
72
Figure 9-3 Modifying initiator information
Step 4 Repeat the preceding operations to modify the information about other initiators on the host.
Step 5 Restart the host to enable the configuration to take effect.
----End
9.5.1.4 Storage Array Configuration
9.5.1.4.1 For Non-HyperMetro Storage
For non-HyperMetro storage, use the configuration listed in Table 9-4.
Table 9-4 Multipathing configuration on non-HyperMetro Huawei storage interconnected with
Solaris
Operating System
Configuration on the Storage Array
Storage Operating System
Third-Party Multipathing Software
Switchover Mode
Special Mode
Path Type
Solaris 10
Solaris 11
Dual-controller,
multi-controller
Solaris Enabled common
ALUA
Optimal
Path
Other
Solaris
versions
Dual-controller,
multi-controller
Solaris Enabled ALUA not
used
Optimal
Path
To query compatible Solaris versions, refer to:
http://support-open.huawei.com/ready/pages/user/compatibility/support-matrix.jsf
HUAWEI SAN Storage Host Connectivity Guide for Solaris 9 Multipathing Management
Issue (2017-07-19) Huawei Proprietary and Confidential
Copyright © Huawei Technologies Co., Ltd.
73
WARNING
After the initiator mode is configured on a storage array, you must restart the host to enable
the new configuration to take effect.
9.5.1.4.2 For HyperMetro Storage
For HyperMetro storage, use the configuration listed in Table 9-5.
Table 9-5 Multipathing configuration on HyperMetro Huawei storage interconnected with Solaris
OS Storage Array Configuration
HyperMetro
Working
Mode
Storage OS Third-Party
Multipathing
Software
Switchover
Mode
Special
Mode
Type
Path Type
Solaris Load
balancing
Local
storage
array
Solaris Enabled Common
ALUA
Optimal
path
Remote
storage
array
Solaris Enabled Common
ALUA
Optimal
path
Local
preferred
Local
storage
array
Solaris Enabled Common
ALUA
Optimal
path
Remote
storage
array
Solaris Enabled Common
ALUA
Non-optimal
path
To query compatible Solaris versions, refer to:
http://support-open.huawei.com/ready/pages/user/compatibility/support-matrix.jsf
WARNING
After the initiator mode is configured on a storage array, you must restart the host to enable
the new configuration to take effect.
9.5.1.5 Host Configuration
9.5.1.5.1 Solaris 8 and 9
Currently, Solaris 8 and 9 are rarely applied and Solaris 8 has been out of maintenance.
HUAWEI SAN Storage Host Connectivity Guide for Solaris 9 Multipathing Management
Issue (2017-07-19) Huawei Proprietary and Confidential
Copyright © Huawei Technologies Co., Ltd.
74
This section describes how to configure Solaris 8 and 9.
You need to disable ALUA for arrays to interconnect with Solaris 8 and 9 because neither
operating system supports the ALUA feature. Additionally, you need to configure files for
multipathing software installed on both operating systems. The detailed configuration
procedure is described as follows:
Step 1 Check whether HBA drives are in normal condition.
On a host, check whether the HBA drive is normal by running the following command:
bash-3.2# cfgadm
Ap_Id Type Reseptacle Occupant Condition
C0 scsi_bus connected configured unknown
C1 scsi_bus connected unconfigured unknown
C2 fc_private connected configured unknown
C3 fc_private connected configured unknown
In the preceding example, the type of c2 and c3 is fc-private, indicating that c2 and c3 are
two HBAs. Reseptacle is in the connected state and Occupant is in the configured state,
indicating that the drive has been successfully loaded. If the preceding states are not displayed
by running this command, it indicates that the HBA drive has been unsuccessfully loaded.
Run the reboot -r command, ensuring that the operating system automatically reloads the
HBA drive.
The HBA type queried by running the cfgmgr command is relevant to HBA networking modes. When
an HBA connects to a storage system, its type is displayed as fc-private. When an HBA connects to a
switch, its type is displayed as fc-fabric.
Step 2 Query the vendor ID and product ID of a storage system.
Select a disk mapped and enter i to query information about a LUN by running the following
command:
bash-3.2# format
Searching for disks...done
AVAILABLE DISK SELECTIONS:
0. c1t0d0 <FUJITSU-MAY2073RCSUN72G-0501 cyl 14087 alt 2 hd 24 sec 424>
/pci@1e,600000/pci@0/pci@a/pci@0/pci@8/scsi@1/sd@0,0
1. c1t1d0 <FUJITSU-MAY2073RCSUN72G-0501 cyl 14087 alt 2 hd 24 sec 424>
/pci@1e,600000/pci@0/pci@a/pci@0/pci@8/scsi@1/sd@1,0
2. c1t2d0 <SUN72G cyl 14087 alt 2 hd 24 sec 424>
/pci@1e,600000/pci@0/pci@a/pci@0/pci@8/scsi@1/sd@2,0
3. c1t3d0 <FUJITSU-MAY2073RCSUN72G-0501 cyl 14087 alt 2 hd 24 sec 424>
/pci@1e,600000/pci@0/pci@a/pci@0/pci@8/scsi@1/sd@3,0
4. c7t28d0 <HUAWEI-S2600T-2102 cyl 10920 alt 2 hd 30 sec 64>
/pci@1f,700000/pci@0/fibre-channel@2/fp@0,0/ssd@w2013323232323232,0
5. c7t28d1 <HUAWEI-S2600T-2102 cyl 4367 alt 2 hd 30 sec 64>
/pci@1f,700000/pci@0/fibre-channel@2/fp@0,0/ssd@w2013323232323232,1
6. c8t4d0 <HUAWEI-S2600T-2102 cyl 10920 alt 2 hd 30 sec 64>
/pci@1f,700000/pci@0/fibre-channel@2,1/fp@0,0/ssd@w2003323232323232,0
7. c8t4d1 <HUAWEI-S2600T-2102 cyl 4367 alt 2 hd 30 sec 64>
/pci@1f,700000/pci@0/fibre-channel@2,1/fp@0,0/ssd@w2003323232323232,1
Specify disk (enter its number): 4
selecting c7t28d0
[disk formatted]
HUAWEI SAN Storage Host Connectivity Guide for Solaris 9 Multipathing Management
Issue (2017-07-19) Huawei Proprietary and Confidential
Copyright © Huawei Technologies Co., Ltd.
75
FORMAT MENU:
disk - select a disk
type - select (define) a disk type
partition - select (define) a partition table
current - describe the current disk
format - format and analyze the disk
repair - repair a defective sector
label - write label to the disk
analyze - surface analysis
defect - defect list management
backup - search for backup labels
verify - read and display labels
save - save new disk/partition definitions
inquiry - show vendor, product and revision
volname - set 8-character volume name
!<cmd> - execute <cmd>, then return
quit
format> i
Vendor: HUAWEI
Product: S2600T
Revision: 2102
format>
In the preceding example, the queried vendor ID of the LUN is HUAWEI, and product ID is
S2600T.
Step 3 Add the vendor ID and product ID of a storage system to the /kernel/drv/scsi_vhci.conf file.
For example:
scsi-vhci-failover-override =
"HUAWEI S5500T", "f_sym",
...
"HUAWEI S2600T", "f_sym";
In the preceding example, two kinds of storage systems, including S5500T and S2600T, have
been added. Where HUAWEI indicates the vendor ID of both storage systems, and S5500T
and S2600T indicate their product IDs.
Add spaces to the end of the vendor ID until it becomes an eight-digit string. The product ID
has no length limit.
Separate a vendor ID + product ID from another vendor ID + product ID using a comma (,).
The last vendor ID + product ID ends with a semicolon (;).
Step 4 In the vi /kernel/drv/fp/conf file, change the mpxio-disable value to no, and enter the wq
command.
Step 5 Enable the STMS function on the host.
Run the stmsboot -e command.
HUAWEI SAN Storage Host Connectivity Guide for Solaris 9 Multipathing Management
Issue (2017-07-19) Huawei Proprietary and Confidential
Copyright © Huawei Technologies Co., Ltd.
76
The operating system prompts you to reboot STMS. During the reboot, the /etc/vfstab file
and dumping configurations are updated to indicate that device names have been changed.
If update //plat is displayed, the host is logging in to the official server update platform.
----End
9.5.1.5.2 Solaris 10
ALUA Enabled on the Storage Arrays
Step 1 Install and enable the multipathing software.
After ALUA is enabled on the storage system, you do not need to perform any ALUA
configurations on the host system; instead, directly run the stmsboot -D fp -e command.
Example command output:
bash-3.2# stmsboot -D fp -e
WARNING: This operation will require a reboot.
Do you want to continue ? [y/n] (default: y) y
The changes will come into effect after rebooting the system.
Reboot the system now ? [y/n] (default: y) y
updating /platform/sun4u/boot_archive
WARNING
After the preceding operation is performed, the host system restarts.
After the host system restarts, the LUN information is as follows:
Figure 9-4 LUN information in Solaris
The path format is scsi_vhci, which contains the path information after multiple paths are aggregated.
Step 2 Configure the multipathing function.
HUAWEI SAN Storage Host Connectivity Guide for Solaris 9 Multipathing Management
Issue (2017-07-19) Huawei Proprietary and Confidential
Copyright © Huawei Technologies Co., Ltd.
77
After ALUA is enabled on the storage system, the storage-served hosts can directly use the
ALUA function with no need for extra configurations on the hosts.
Step 3 Check that the ALUA configurations are successful.
After the LUNs are mapped from a storage system to a host, scan for and check the LUN
information to ensure that the numbers and status of the preferred and non-preferred paths are
correct.
root@solarisx86:~# mpathadm show lu /dev/dsk/c0t6222222100222222000E25A800000004d0s2
Logical Unit: /dev/rdsk/c0t6222222100222222000E25A800000004d0s2
mpath-support: libmpscsi_vhci.so
Vendor: HUAWEI
Product: XSG1
Revision: 4303
Name Type: unknown type
Name: 6222222100222222000e25a800000004
Asymmetric: yes
Current Load Balance: round-robin
Logical Unit Group ID: NA
Auto Failback: on
Auto Probing: NA
Paths:
Initiator Port Name: 2100001b3210fbda
Target Port Name: 200800ac01020304
Override Path: NA
Path State: OK
Disabled: no
Initiator Port Name: 2100001b3210fbda
Target Port Name: 2602222222222222
Override Path: NA
Path State: OK
Disabled: no
Initiator Port Name: 2100001b3210fbda
Target Port Name: 2619222222222222
Override Path: NA
Path State: OK
Disabled: no
Initiator Port Name: 2100001b3210fbda
Target Port Name: 202800ac01020304
Override Path: NA
Path State: OK
Disabled: no
Initiator Port Name: 2101001b3230fbda
Target Port Name: 201800ac01020304
Override Path: NA
Path State: OK
Disabled: no
Initiator Port Name: 2101001b3230fbda
Target Port Name: 2601222222222222
HUAWEI SAN Storage Host Connectivity Guide for Solaris 9 Multipathing Management
Issue (2017-07-19) Huawei Proprietary and Confidential
Copyright © Huawei Technologies Co., Ltd.
78
Override Path: NA
Path State: OK
Disabled: no
Initiator Port Name: 2101001b3230fbda
Target Port Name: 2618222222222222
Override Path: NA
Path State: OK
Disabled: no
Initiator Port Name: 2101001b3230fbda
Target Port Name: 203800ac01020304
Override Path: NA
Path State: OK
Disabled: no
Target Port Groups:
ID: 33
Explicit Failover: no
Access State: active optimized
Target Ports:
Name: 200800ac01020304
Relative ID: 8193
ID: 1
Explicit Failover: no
Access State: active optimized
Target Ports:
Name: 2602222222222222
Relative ID: 23
Name: 2601222222222222
Relative ID: 22
ID: 2
Explicit Failover: no
Access State: active not optimized
Target Ports:
Name: 2619222222222222
Relative ID: 282
Name: 2618222222222222
Relative ID: 281
ID: 35
Explicit Failover: no
Access State: active not optimized
Target Ports:
Name: 202800ac01020304
Relative ID: 8705
ID: 34
Explicit Failover: no
Access State: active not optimized
Target Ports:
HUAWEI SAN Storage Host Connectivity Guide for Solaris 9 Multipathing Management
Issue (2017-07-19) Huawei Proprietary and Confidential
Copyright © Huawei Technologies Co., Ltd.
79
Name: 201800ac01020304
Relative ID: 8449
ID: 36
Explicit Failover: no
Access State: active not optimized
Target Ports:
Name: 203800ac01020304
Relative ID: 8961
root@solarisx86:~#
As shown in the preceding command output, there are three preferred paths and five
non-preferred paths.
----End
ALUA Disabled on the Storage Arrays
When ALUA is disabled on a storage system, you need to modify a multipathing
configuration file on a host. In this way, the multipathing software can take over the LUNs
that are mapped from the storage system.
In the scenario where ALUA is disabled on a storage system, configure STMS for a host by
performing the following procedure:
Step 1 View the vendor ID and product ID of a storage system mapped.
Select a disk mapped and enter i to query information about a LUN by running the following
command:
bash-3.2# format
Searching for disks...done
AVAILABLE DISK SELECTIONS:
0. c1t0d0 <FUJITSU-MAY2073RCSUN72G-0501 cyl 14087 alt 2 hd 24 sec 424>
/pci@1e,600000/pci@0/pci@a/pci@0/pci@8/scsi@1/sd@0,0
1. c1t1d0 <FUJITSU-MAY2073RCSUN72G-0501 cyl 14087 alt 2 hd 24 sec 424>
/pci@1e,600000/pci@0/pci@a/pci@0/pci@8/scsi@1/sd@1,0
2. c1t2d0 <SUN72G cyl 14087 alt 2 hd 24 sec 424>
/pci@1e,600000/pci@0/pci@a/pci@0/pci@8/scsi@1/sd@2,0
3. c1t3d0 <FUJITSU-MAY2073RCSUN72G-0501 cyl 14087 alt 2 hd 24 sec 424>
/pci@1e,600000/pci@0/pci@a/pci@0/pci@8/scsi@1/sd@3,0
4. c7t28d0 <HUAWEI-S2600T-2102 cyl 10920 alt 2 hd 30 sec 64>
/pci@1f,700000/pci@0/fibre-channel@2/fp@0,0/ssd@w2013323232323232,0
5. c7t28d1 <HUAWEI-S2600T-2102 cyl 4367 alt 2 hd 30 sec 64>
/pci@1f,700000/pci@0/fibre-channel@2/fp@0,0/ssd@w2013323232323232,1
6. c8t4d0 <HUAWEI-S2600T-2102 cyl 10920 alt 2 hd 30 sec 64>
/pci@1f,700000/pci@0/fibre-channel@2,1/fp@0,0/ssd@w2003323232323232,0
7. c8t4d1 <HUAWEI-S2600T-2102 cyl 4367 alt 2 hd 30 sec 64>
/pci@1f,700000/pci@0/fibre-channel@2,1/fp@0,0/ssd@w2003323232323232,1
Specify disk (enter its number): 4
selecting c7t28d0
[disk formatted]
FORMAT MENU:
HUAWEI SAN Storage Host Connectivity Guide for Solaris 9 Multipathing Management
Issue (2017-07-19) Huawei Proprietary and Confidential
Copyright © Huawei Technologies Co., Ltd.
80
disk - select a disk
type - select (define) a disk type
partition - select (define) a partition table
current - describe the current disk
format - format and analyze the disk
repair - repair a defective sector
label - write label to the disk
analyze - surface analysis
defect - defect list management
backup - search for backup labels
verify - read and display labels
save - save new disk/partition definitions
inquiry - show vendor, product and revision
volname - set 8-character volume name
!<cmd> - execute <cmd>, then return
quit
format> i
Vendor: HUAWEI
Product: S2600T
Revision: 2102
format>
In the preceding example, the queried vendor ID of the LUN is HUAWEI, and product ID is
S2600T.
Step 2 Modify a multipathing configuration file on the host.
You need to configure the vendor ID and product ID of a LUN that has been taken over in the
/kernel/drv/scsi_vhci.conf file for the multipathing software installed on Solaris 10.
The following shows a file that has been properly configured:
bash-3.2# cat /kernel/drv/scsi_vhci.conf
#
# Copyright (c) 2001, 2011, Oracle and/or its affiliates. All rights reserved.
#
#pragma ident "@(#)scsi_vhci.conf 1.10 11/04/12 SMI"
#
name="scsi_vhci" class="root";
#
# Load balancing global configuration: setting load-balance="none" will cause
# all I/O to a given device (which supports multipath I/O) to occur via one
# path. Setting load-balance="round-robin" will cause each path to the device
# to be used in turn.
#
load-balance="round-robin";
#
# Automatic failback configuration
# possible values are auto-failback="enable" or auto-failback="disable"
auto-failback="enable";
#
# For enabling MPxIO support for 3rd party symmetric device need an
# entry similar to following in this file. Just replace the "SUN SENA"
# part with the Vendor ID/Product ID for the device, exactly as reported by
# Inquiry cmd.
#
device-type-scsi-options-list =
HUAWEI SAN Storage Host Connectivity Guide for Solaris 9 Multipathing Management
Issue (2017-07-19) Huawei Proprietary and Confidential
Copyright © Huawei Technologies Co., Ltd.
81
"HUAWEI S2600T", "symmetric-option";
#
symmetric-option = 0x1000000;
#mpxio-disable="yes";
#BEGIN: UPDATE_PATHSTATE_ON_RESET_BLOCK (DO NOT MOVE OR DELETE)
#
# Tunable for updating path states after a UNIT ATTENTION reset.
# There are arrays which do not queue UAs during resets
# after an implicit failover. For such arrays, we need to
# update the path states after any type of UA resets, since
# UA resets take higher precedence among other UNIT ATTENTION
# conditions. By default, scsi_vhci does not update path states
# on UA resets. To make scsi_vhci do that for such arrays, you need
# to set the tunable scsi-vhci-update-pathstate-on-reset to "yes"
# for the VID/PID combination as described below.
#
# "012345670123456789012345", "yes" or "no"
# "|-VID--||-----PID------|",
# scsi-vhci-update-pathstate-on-reset =
# "Pillar Axiom 600", "yes";
#
#END: UPDATE_PATHSTATE_ON_RESET_BLOCK (DO NOT MOVE OR DELETE)
bash-3.2#
Based on the preceding information, we need to focus on the following:
load-balance
It is set to round-robin by default and does not need to be modified.
auto-failback
It is set to enable by default and does not need to be modified.
Device information
The default information is shown as follows:
#
#device-type-scsi-options-list =
#"SUN SENA", "symmetric-option";
#
#symmetric-option = 0x1000000;
In the preceding example, SUN SENA indicates array information. SUN indicates
the vendor ID, and SENA indicates the product ID.
Here, we need to delete the comment symbol (#) and modify the vendor ID and product
ID of a LUN based on actual conditions. For example:
device-type-scsi-options-list =
"HUAWEI S5500T", "symmetric-option",
"HUAWEI S2600T", "symmetric-option";
#
symmetric-option = 0x1000000;
In the preceding example, two kinds of storage systems, including S5500T and S2600T,
have been added.
HUAWEI SAN Storage Host Connectivity Guide for Solaris 9 Multipathing Management
Issue (2017-07-19) Huawei Proprietary and Confidential
Copyright © Huawei Technologies Co., Ltd.
82
Add spaces to the end of the vendor ID until it becomes an eight-digit string. The product ID
has no length limit.
Separate a vendor ID + product ID from another vendor ID + product ID using a comma (,).
The last vendor ID + product ID ends with a semicolon (;).
Step 3 Enable the STMS function on the host.
Similar to the procedure for enabling ALUA, enable the STMS function by running the
stmsboot -D fp -e command. STMS can work after the host is restarted.
----End
9.5.1.5.3 Solaris 11
ALUA Enabled on the Storage Arrays
The method is the same as that used on Solaris 10.
ALUA Disabled on the Storage Arrays
Solaris 11 is slightly different from Solaris 10 in terms of the configuration procedure.
The detailed configuration procedure is described as follows:
Step 1 Query the vendor ID and product ID of a storage system.
Select a disk mapped and enter i to query information about a LUN by running the following
command:
bash-3.2# format
Searching for disks...done
AVAILABLE DISK SELECTIONS:
0. c1t0d0 <FUJITSU-MAY2073RCSUN72G-0501 cyl 14087 alt 2 hd 24 sec 424>
/pci@1e,600000/pci@0/pci@a/pci@0/pci@8/scsi@1/sd@0,0
1. c1t1d0 <FUJITSU-MAY2073RCSUN72G-0501 cyl 14087 alt 2 hd 24 sec 424>
/pci@1e,600000/pci@0/pci@a/pci@0/pci@8/scsi@1/sd@1,0
2. c1t2d0 <SUN72G cyl 14087 alt 2 hd 24 sec 424>
/pci@1e,600000/pci@0/pci@a/pci@0/pci@8/scsi@1/sd@2,0
3. c1t3d0 <FUJITSU-MAY2073RCSUN72G-0501 cyl 14087 alt 2 hd 24 sec 424>
/pci@1e,600000/pci@0/pci@a/pci@0/pci@8/scsi@1/sd@3,0
4. c7t28d0 <HUAWEI-S2600T-2102 cyl 10920 alt 2 hd 30 sec 64>
/pci@1f,700000/pci@0/fibre-channel@2/fp@0,0/ssd@w2013323232323232,0
5. c7t28d1 <HUAWEI-S2600T-2102 cyl 4367 alt 2 hd 30 sec 64>
/pci@1f,700000/pci@0/fibre-channel@2/fp@0,0/ssd@w2013323232323232,1
6. c8t4d0 <HUAWEI-S2600T-2102 cyl 10920 alt 2 hd 30 sec 64>
/pci@1f,700000/pci@0/fibre-channel@2,1/fp@0,0/ssd@w2003323232323232,0
7. c8t4d1 <HUAWEI-S2600T-2102 cyl 4367 alt 2 hd 30 sec 64>
/pci@1f,700000/pci@0/fibre-channel@2,1/fp@0,0/ssd@w2003323232323232,1
Specify disk (enter its number): 4
selecting c7t28d0
[disk formatted]
HUAWEI SAN Storage Host Connectivity Guide for Solaris 9 Multipathing Management
Issue (2017-07-19) Huawei Proprietary and Confidential
Copyright © Huawei Technologies Co., Ltd.
83
FORMAT MENU:
disk - select a disk
type - select (define) a disk type
partition - select (define) a partition table
current - describe the current disk
format - format and analyze the disk
repair - repair a defective sector
label - write label to the disk
analyze - surface analysis
defect - defect list management
backup - search for backup labels
verify - read and display labels
save - save new disk/partition definitions
inquiry - show vendor, product and revision
volname - set 8-character volume name
!<cmd> - execute <cmd>, then return
quit
format> i
Vendor: HUAWEI
Product: S2600T
Revision: 2102
format>
In the preceding example, the queried vendor ID of the LUN is HUAWEI, and product ID is
S2600T.
Step 2 Copy the /kernel/drv/scsi_vhci.conf file to the /etc/driver/drv/scsi_vhci.conf file.
Step 3 Add the vendor ID and product ID of a storage system to the /etc/driver/drv/scsi_vhci.conf
file.
For example:
scsi-vhci-failover-override =
"HUAWEI S5500T", "f_sym",
...
"HUAWEI S2600T", "f_sym";
In the preceding example, two kinds of storage systems, including S5500T and S2600T, have
been added, where HUAWEI indicates the vendor ID of both storage systems, and S5500T
and S2600T indicate their product IDs.
Add spaces to the end of the vendor ID until it becomes an eight-digit string. The product ID
has no length limit.
Separate a vendor ID + product ID from another vendor ID + product ID using a comma (,).
The last vendor ID + product ID ends with a semicolon (;).
Step 4 Enable the STMS function on the host.
Run the stmsboot -D fp -e command.
HUAWEI SAN Storage Host Connectivity Guide for Solaris 9 Multipathing Management
Issue (2017-07-19) Huawei Proprietary and Confidential
Copyright © Huawei Technologies Co., Ltd.
84
The operating system prompts you to reboot STMS. During the reboot, the /etc/vfstab file
and dumping configurations are updated to indicate that device names have been changed.
If update //plat is displayed, the host is logging in to the official server update platform.
----End
9.5.2 Multipathing Configuration for Old-Version HUAWEI Storage
9.5.2.1.1 Storage Array Configuration
For HUAWEI storage that does not support multi-controller ALUA or ALUA HyperMetro, it
is advisable to retain the ALUA disabled state by default. To enable the ALUA function, do as
follows:
9.5.2.1.2 T Series V100R005/Dorado2100/Dorado5100/Dorado2100 G2
Use the Huawei OceanStor ISM system to enable ALUA for all the host initiators, as shown in
Figure 9-5.
Figure 9-5 Enabling ALUA for T series V100R005/Dorado2100/Dorado5100/Dorado2100 G2
9.5.2.1.3 T Series V200R002/18000 Series/V3 Series
Use the Huawei OceanStor DeviceManager to enable ALUA for all the host initiators, as
shown in Figure 9-6.
HUAWEI SAN Storage Host Connectivity Guide for Solaris 9 Multipathing Management
Issue (2017-07-19) Huawei Proprietary and Confidential
Copyright © Huawei Technologies Co., Ltd.
85
Figure 9-6 Enabling ALUA for T Series V200R002/18000 Series/V3 Series
Multi-controller ALUA is not supported. When there are more than two controllers, ALUA is disabled
by default and the ALUA status cannot be changed.
9.5.2.2 Host Configuration
The host configurations are similar to those in section 9.5.1 "Multipathing Configuration for
New-Version HUAWEI Storage". Remember to change the vendor and product according to
your site information.
9.6 Management Commands Related to Multipathing
This section describes management commands related to multipathing by taking Solaris 10 as
an example.
9.6.1 Viewing the Relationship Between Virtual LUNs and Original LUNs
Run the following command to obtain the relationship between LUNs virtualized by
multipathing and original LUNs:
bash-3.2# stmsboot -L
non-STMS device name STMS device name
------------------------------------------------------------------
/dev/rdsk/c8t4d1 /dev/rdsk/c2t632323210032323206B0E17A00000005d0
/dev/rdsk/c7t28d1 /dev/rdsk/c2t632323210032323206B0E17A00000005d0
/dev/rdsk/c7t28d0 /dev/rdsk/c2t63232321003232320516B53500000004d0
/dev/rdsk/c8t4d0 /dev/rdsk/c2t63232321003232320516B53500000004d0
HUAWEI SAN Storage Host Connectivity Guide for Solaris 9 Multipathing Management
Issue (2017-07-19) Huawei Proprietary and Confidential
Copyright © Huawei Technologies Co., Ltd.
86
bash-3.2#
9.6.2 Viewing Information About Paths to Virtual LUNs
Run the following commands to obtain information about logical paths to LUNs virtualized
by multipathing:
bash-3.2# luxadm probe
No Network Array enclosures found in /dev/es
Found Fibre Channel device(s):
Node WWN:2100323232323232 Device Type:Disk device
Logical Path:/dev/rdsk/c2t632323210032323206B0E17A00000005d0s2
Node WWN:2100323232323232 Device Type:Disk device
Logical Path:/dev/rdsk/c2t63232321003232320516B53500000004d0s2
bash-3.2#
bash-3.2# luxadm display /dev/rdsk/c2t632323210032323206B0E17A00000005d0s2
DEVICE PROPERTIES for disk: /dev/rdsk/c2t632323210032323206B0E17A00000005d0s2
Vendor: HUASY
Product ID: S2600T
Revision: 2102
Serial Num: S2600T129123456789020005
Unformatted capacity: 4096.000 MBytes
Read Cache: Enabled
Minimum prefetch: 0x0
Maximum prefetch: 0x10
Device Type: Disk device
Path(s):
/dev/rdsk/c2t632323210032323206B0E17A00000005d0s2
/devices/scsi_vhci/ssd@g632323210032323206b0e17a00000005:c,raw
Controller /devices/pci@1f,700000/pci@0/fibre-channel@2,1/fp@0,0
Device Address 2003323232323232,1
Host controller port WWN 10000000c96fa383
Class secondary
State ONLINE
Controller /devices/pci@1f,700000/pci@0/fibre-channel@2/fp@0,0
Device Address 2013323232323232,1
Host controller port WWN 10000000c96fa382
Class primary
State ONLINE
bash-3.2#
In the preceding example, we can view information about physical paths to virtual LUNs.
9.6.3 Viewing Information About Multipathing Support
Identify information about multipathing support and attributes using the name of the
multipathing API plug-in library. Relevant query commands are shown as follows:
bash-3.2# mpathadm list mpath-support
mpath-support: libmpscsi_vhci.so
bash-3.2#
bash-3.2# mpathadm show mpath-support libmpscsi_vhci.so
mpath-support: libmpscsi_vhci.so
HUAWEI SAN Storage Host Connectivity Guide for Solaris 9 Multipathing Management
Issue (2017-07-19) Huawei Proprietary and Confidential
Copyright © Huawei Technologies Co., Ltd.
87
Vendor: Sun Microsystems
Driver Name: scsi_vhci
Default Load Balance: round-robin
Supported Load Balance Types:
round-robin
logical-block
Allows To Activate Target Port Group Access: yes
Allows Path Override: no
Supported Auto Failback Config: 1
Auto Failback: on
Failback Polling Rate (current/max): 0/0
Supported Auto Probing Config: 0
Auto Probing: NA
Probing Polling Rate (current/max): NA/NA
Supported Devices:
Vendor: SUN
Product: T300
Revision:
Supported Load Balance Types:
round-robin
Vendor: HUASY
Product: S2600T
Revision:
Supported Load Balance Types:
round-robin
bash-3.2#
The list of devices that multipathing software is compatible with is displayed after you run the
preceding commands. In the preceding example, our configured products have appeared in the
list.
9.6.4 Viewing Attributes of Specific Initiator
View attributes of specific initiator ports by running the following commands:
bash-3.2# mpathadm list initiator-port
Initiator Port: 10000000c96fa382
Initiator Port: 10000000c96fa383
Initiator Port: iqn.1986-03.com.sun:01:00144fa383a6.505138ff,4000002a00ff
bash-3.2#
bash-3.2# mpathadm show initiator-port 10000000c96fa382
Initiator Port: 10000000c96fa382
Transport Type: Fibre Channel
OS Device File: /devices/pci@1f,700000/pci@0/fibre-channel@2/fp@0,0
bash-3.2#
bash-3.2# mpathadm show initiator-port
iqn.1986-03.com.sun:01:00144fa383a6.505138ff,4000002a00ff
Initiator Port: iqn.1986-03.com.sun:01:00144fa383a6.505138ff,4000002a00ff
Transport Type: iSCSI
OS Device File: /devices/iscsi
bash-3.2#
HUAWEI SAN Storage Host Connectivity Guide for Solaris 9 Multipathing Management
Issue (2017-07-19) Huawei Proprietary and Confidential
Copyright © Huawei Technologies Co., Ltd.
88
9.6.5 Viewing Information About Specific LUNs
View details about paths to specific LUNs by running the following commands:
bash-3.2# mpathadm list lu
/dev/rdsk/c2t632323210032323206B0E17A00000005d0s2
Total Path Count: 2
Operational Path Count: 2
/dev/rdsk/c2t63232321003232320516B53500000004d0s2
Total Path Count: 2
Operational Path Count: 2
bash-3.2# mpathadm show lu /dev/rdsk/c2t632323210032323206B0E17A00000005d0s2
Logical Unit: /dev/rdsk/c2t632323210032323206B0E17A00000005d0s2
mpath-support: libmpscsi_vhci.so
Vendor: HUASY
Product: S2600T
Revision: 2102
Name Type: unknown type
Name: 632323210032323206b0e17a00000005
Asymmetric: no
Current Load Balance: round-robin
Logical Unit Group ID: NA
Auto Failback: on
Auto Probing: NA
Paths:
Initiator Port Name: 10000000c96fa383
Target Port Name: 2003323232323232
Override Path: NA
Path State: OK
Disabled: no
Initiator Port Name: 10000000c96fa382
Target Port Name: 2013323232323232
Override Path: NA
Path State: OK
Disabled: no
Target Ports:
Name: 2003323232323232
Relative ID: 0
Name: 2013323232323232
Relative ID: 0
bash-3.2#
For x86-based Solaris 10, if ALUA is enabled, relative IDs of target ports on all paths to a
LUN are displayed by running the following command:
bash-3.00# mpathadm show lu /dev/rdsk/c4t60022A11000AFD57000872C90000000Ed0s2
Logical Unit: /dev/rdsk/c4t60022A11000AFD57000872C90000000Ed0s2
mpath-support: libmpscsi_vhci.so
Vendor: HUAWEI
Product: Dorado5100
Revision: 2101
Name Type: unknown type
HUAWEI SAN Storage Host Connectivity Guide for Solaris 9 Multipathing Management
Issue (2017-07-19) Huawei Proprietary and Confidential
Copyright © Huawei Technologies Co., Ltd.
89
Name: 60022a11000afd57000872c90000000e
Asymmetric: yes
Current Load Balance: round-robin
Logical Unit Group ID: NA
Auto Failback: on
Auto Probing: NA
Paths:
Initiator Port Name: 10000000c98147b5
Target Port Name: 22020022a10afd57
Override Path: NA
Path State: OK
Disabled: no
Initiator Port Name: 10000000c98147b6
Target Port Name: 22130022a10afd57
Override Path: NA
Path State: OK
Disabled: no
Initiator Port Name: 10000000c98147b6
Target Port Name: 22020022a10afd57
Override Path: NA
Path State: OK
Disabled: no
Target Port Groups:
ID: 1
Explicit Failover: yes
Access State: active optimized
Target Ports:
Name: 22020022a10afd57
Relative ID: 7984
Name: 22020022a10afd57
Relative ID: 529
Name: 22020022a10afd57
Relative ID: 530
Name: 22020022a10afd57
Relative ID: 531
Name: 22020022a10afd57
Relative ID: 532
ID: 2
Explicit Failover: yes
Access State: active not optimized
Target Ports:
Name: 22130022a10afd57
Relative ID: 16176
Name: 22130022a10afd57
Relative ID: 8721
HUAWEI SAN Storage Host Connectivity Guide for Solaris 9 Multipathing Management
Issue (2017-07-19) Huawei Proprietary and Confidential
Copyright © Huawei Technologies Co., Ltd.
90
Name: 22130022a10afd57
Relative ID: 8722
Name: 22130022a10afd57
Relative ID: 8723
Name: 22130022a10afd57
Relative ID: 8724
9.6.6 Viewing Information About LUNs on Specific Ports
View all LUNs related to specific target ports by performing the following procedure:
Step 1 View the LUN list.
bash-3.2# mpathadm list lu
/dev/rdsk/c2t632323210032323206B0E17A00000005d0s2
Total Path Count: 2
Operational Path Count: 2
/dev/rdsk/c2t63232321003232320516B53500000004d0s2
Total Path Count: 2
Operational Path Count: 2
bash-3.2#
Step 2 View information about a specific LUN to identify target ports.
bash-3.2# mpathadm show lu /dev/rdsk/c2t632323210032323206B0E17A00000005d0s2
Logical Unit: /dev/rdsk/c2t632323210032323206B0E17A00000005d0s2
mpath-support: libmpscsi_vhci.so
Vendor: HUASY
Product: S2600T
Revision: 2102
Name Type: unknown type
Name: 632323210032323206b0e17a00000005
Asymmetric: no
Current Load Balance: round-robin
Logical Unit Group ID: NA
Auto Failback: on
Auto Probing: NA
Paths:
Initiator Port Name: 10000000c96fa383
Target Port Name: 2003323232323232
Override Path: NA
Path State: OK
Disabled: no
Initiator Port Name: 10000000c96fa382
Target Port Name: 2013323232323232
Override Path: NA
Path State: OK
Disabled: no
Target Ports:
Name: 2003323232323232
Relative ID: 0
HUAWEI SAN Storage Host Connectivity Guide for Solaris 9 Multipathing Management
Issue (2017-07-19) Huawei Proprietary and Confidential
Copyright © Huawei Technologies Co., Ltd.
91
Name: 2013323232323232
Relative ID: 0
bash-3.2#
In the preceding example, target port names are 2003323232323232 and 2013323232323232.
Step 3 View LUN information of a specific target port.
bash-3.2# mpathadm list lu -t 2003323232323232
mpath-support: libmpscsi_vhci.so
/dev/rdsk/c2t632323210032323206B0E17A00000005d0s2
Total Path Count: 2
Operational Path Count: 2
mpath-support: libmpscsi_vhci.so
/dev/rdsk/c2t63232321003232320516B53500000004d0s2
Total Path Count: 2
Operational Path Count: 2
bash-3.2#
----End
9.7 Troubleshooting
9.7.1 Symptom
After LUN partitions are created and a mapped LUN is deleted, an error message is reported
when you run the mpathadm command to view paths managed by STMS. The error message
indicates that the configuration information cannot be found and you cannot perform the
operation. For example:
bash-3.2# mpathadm list LU
/dev/rdsk/c0t5000C500552839D3d0s2
Total Path Count: 1
Operational Path Count: 1
/dev/rdsk/c0t5000C500552087F3d0s2
Total Path Count: 1
Operational Path Count: 1
/dev/rdsk/c0t60022A1100041661001DBD4300000000d0s2
Total Path Count: 2
Operational Path Count: 2
/dev/rdsk/c0t60022A1100041661001DF8EA00000001d0s2
Total Path Count: 2
Operational Path Count: 2
mpathadm: Error: Unable to get configuration information.
mpathadm: Unable to complete operation
9.7.2 Root Cause Analysis
The command execution fails because residual information about the deleted LUN has caused
an execution error.
HUAWEI SAN Storage Host Connectivity Guide for Solaris 9 Multipathing Management
Issue (2017-07-19) Huawei Proprietary and Confidential
Copyright © Huawei Technologies Co., Ltd.
92
Solution
Clear residual information about the deleted LUN by performing the following procedure:
Step 1 View Ap_Id values of FC mount points by running the following command:
c5 and c6 whose type is fc-fabric indicate FC mount points matched with two HBA ports.
bash-3.2# cfgadm -al
Ap_Id Type Receptacle Occupant Condition
c2 scsi-sas connected configured unknown
c2::w5000c500552839d1,0 disk-path connected configured unknown
c3 scsi-sas connected configured unknown
c3::w5000c500552087f1,0 disk-path connected configured unknown
c4 scsi-sas connected unconfigured unknown
c5 fc-fabric connected configured unknown
c5::201b0022a1041661 disk connected configured unknown
c6 fc-fabric connected configured unknown
c6::200a0022a1041661 disk connected configured unknown
Step 2 Manually unconfigure and configure two mount points to update LUN information.
Only one port (c6) generates I/Os because ALUA is enabled for arrays described in the
preceding example, although STMS is set to round-robin. Therefore, it shows that this
operation fails when you unconfigure c6. This is normal. It indicates that this operation has
not interrupted I/O read/write. The I/O monitoring results also show that I/Os have not been
interrupted.
bash-3.2# cfgadm -c unconfigure c5
bash-3.2# cfgadm -c unconfigure c6
cfgadm: Library error: remove operation failed:
/devices/pci@77,0/pci8086,3c06@2,2/pci10df,f134@0,1/fp@0,0/disk@w200a0022a1041661,
0: I/O error
remove operation failed:
/devices/pci@77,0/pci8086,3c06@2,2/pci10df,f134@0,1/fp@0,0/disk@w200a0022a1041661,
0: I/O error
failed to unconfigure ANY device on FCA port
bash-3.2# cfgadm -c configure c6
bash-3.2# cfgadm -c configure c5
Step 3 Run the format command again and view the LUN status to check whether the residual
information about the deleted LUN has been cleared.
bash-3.2# format
Searching for disks...done
AVAILABLE DISK SELECTIONS:
0. c0t5000C500552087F3d0 <DEFAULT cyl 36469 alt 2 hd 255 sec 63>
/scsi_vhci/disk@g5000c500552087f3
1. c0t5000C500552839D3d0 <DEFAULT cyl 36469 alt 2 hd 255 sec 63>
/scsi_vhci/disk@g5000c500552839d3
2. c0t60022A1100041661001DBD4300000000d0 <DEFAULT cyl 2557 alt 2 hd 128 sec 32>
/scsi_vhci/disk@g60022a1100041661001dbd4300000000
Specify disk (enter its number):
Step 4 Run the mpathadm command to view the LUN information.
HUAWEI SAN Storage Host Connectivity Guide for Solaris 9 Multipathing Management
Issue (2017-07-19) Huawei Proprietary and Confidential
Copyright © Huawei Technologies Co., Ltd.
93
All information is in normal condition.
----End
HUAWEI SAN Storage Host Connectivity Guide for Solaris 10 Volume Management
Issue (2017-07-19) Huawei Proprietary and Confidential
Copyright © Huawei Technologies Co., Ltd.
94
10 Volume Management
Volume management software widely used in Solaris includes SVM delivered with Solaris
and VxVM provided by Symantec.
This chapter details SVM and VxVM.
10.1 SVM
10.1.1 Overview
Solaris Volume Manager (SVM) is the software to manage a large number of disks and data
stored on them. SVM is mainly applied in the following:
Expanding storage capacity
Improving data availability
Simplifying the management of large-scale storage devices
In addition, SVM can improve I/O performance.
10.1.1.1 Managing Storage Systems
SVM manages physical disks and their associated data using virtual disks. Virtual disks are
called volumes. For historical reasons, volumes are called metadevices in command-line
utilities.
For application programs or file systems, volumes are equal to physical disks in terms of
functions. SVM can be used to convert a volume-oriented I/O request into a disk-oriented I/O
request.
Additionally, SVM can improve data reliability and availability using the RAID-1 (mirror)
volume and RAID-5 volume. SVM hot spares can further improve data availability of the
mirrored volume and RAID-5 volume.
10.1.1.2 Managing SVM
You can manage SVM using the following two methods:
GUI (Solaris Management Console)
HUAWEI SAN Storage Host Connectivity Guide for Solaris 10 Volume Management
Issue (2017-07-19) Huawei Proprietary and Confidential
Copyright © Huawei Technologies Co., Ltd.
95
You can manage volumes on the GUI (Solaris Management Console). The GUI provides
wizard-based processing functions for SVM components including volumes, hot spare
pools, and state database replicas, ensuring that you can quickly configure disks or
change the existing configuration.
Command lines
You can manage volumes using multiple commands. The core commands for SVM
management begin with meta, such as metainit and metastat.
You can use either command lines or GUI to manage SVM.
Configuration changes may cause unpredictable consequences.
10.1.2 Component Overview
Five types of basic components created using SVM include volumes, soft partitions, disk sets,
state database replicas, and hot spare pools. Table 10-1 lists each component function.
Table 10-1 SVM component functions
Component Definition Function
RAID-0 (stripe,
concatenation or
concatenation/stripe) volume
RAID-1 (mirror) volume
RAID-5 volume
Indicates a set of physical
disk slices. It is displayed as
a single logical device.
Expands storage capacity,
and improves performance
and data availability.
Soft partition Indicates the subunit of a
physical disk slice or logical
volume, providing smaller
storage units that are
convenient for management.
Improves the
manageability of
large-scale storage
volumes.
State database (state database
replica)
Indicates a database that
contains information about
the configuration and status
of all volumes, hot spares,
and disk sets. SVM cannot
be operated until a state
database replica is created.
Stores information about
the configuration status of
SVM.
Hot spare pool Indicates a set of reserved
disk slices (hot spares). An
operating system replaces
failed submirrors or RADI-5
volumes with these slices.
Improves data availability
of the RAID-1 volume and
RAID-5 volume.
Disk set Indicates a set of shared disk
drives stored in a separate namespace. It includes
Improves data redundancy
and data availability, and provides a separate
HUAWEI SAN Storage Host Connectivity Guide for Solaris 10 Volume Management
Issue (2017-07-19) Huawei Proprietary and Confidential
Copyright © Huawei Technologies Co., Ltd.
96
Component Definition Function
volumes and hot spares
shared by different hosts.
namespace for convenient
management.
The following describes each component in detail.
10.1.2.2 Volume
A volume consists of a set of physical disk slices. It is displayed as a single logical device. As
a standard UNIX term, a volume indicates a pseudo or virtual device.
Volumes can be used to improve storage capacity, performance, and data availability. In
addition, volumes can improve I/O performance. Volumes are equal to slices in terms of
functions. Because volumes look like slices, they are transparent to end users, applications,
and file systems. You can access volumes by the name of a block device or an original device,
just like accessing physical devices. The volume name varies with a block device or an
original device.
You can run most file system commands for volumes, such as mkfs, mount, umount,
ufsdump, and ufsrestore except for the format command. You can read, write, and copy files
on volumes only if volumes contain mounted file systems.
Similar to physical disks, the logical names of volumes also appear in file systems. Logical
volume names map to items under the /dev/md/dsk directory of block devices and the
/dev/md/rdsk directory of original devices. A meta* command usually uses an abbreviated
volume name (d1) instead of a specified complete volume name (/dev/md/dsk/volume-name).
10.1.2.3 Soft Partition
As the storage capacity of disks grows, Solaris operating systems use disk arrays as larger
logical devices. To create more file systems or partitions that are convenient for management,
a user may need to divide a disk or logical volume into more than 8 partitions. The soft
partition function of SVM is a good choice.
For SVM, each disk set contains a maximum of 8192 logical volumes. This case applies to
local (unspecified) disk sets. Volumes can be configured for SVM.
Disk slices or logical volumes can be divided into multiple partitions (soft partitions). Naming
each partition (that is, soft partition), just like naming other storage volumes, such as stripes
or mirrors. Application programs and file systems can access soft partitions that are named
and excluded from other volumes. Soft partitions included in other volumes cannot be
accessed.
You can set a soft partition above a disk or at the top of a mirrored volume, striped volume or
RAID-5 volume. A soft partition cannot be located above or below other volumes. For
example, if a mirror is generated on a soft partition, the soft partition cannot appear on a
stripe.
In file systems and other application programs, a soft partition seems like a single and
continuous logical volume. However, a soft partition consists of a series of expansions that
may be located on any position of basic media. Information about soft partitions is also
recorded on the table header of extended disk partition called data restoration area, ensuring
data restoration in case of catastrophic faults.
HUAWEI SAN Storage Host Connectivity Guide for Solaris 10 Volume Management
Issue (2017-07-19) Huawei Proprietary and Confidential
Copyright © Huawei Technologies Co., Ltd.
97
10.1.2.4 State Database
A state database is a database that is used for storing information about the configuration
status of SVM. It records and traces changes to configuration. In case of any change to
configuration or status, SVM automatically updates state databases.
A state database is a set of multiple database replicas. Each state database replica can ensure
the validity of data imported to a state database. Multiple state database replicas can prevent
data loss in case of a single point of failure. A state database can trace positions and states of
all known state database replicas.
SVM cannot be operated until a state database and its replicas are created. A state database
must be operated during the configuration of SVM.
During the configuration, you can store state database replicas on the following positions:
A dedicated slice
A slice that will be part of a volume
SVM can be used to identify a slice that contains state database replicas. If the slice is
included in a volume and is in-service, SVM automatically skips the replicas on the disk
during identification. Slices reserved for state database replicas can be used only for specified
purposes.
Multiple state database replicas can be stored on a slice. However, an operating system may
be damaged in case of single point failure.
The Solaris operating system can work normally after all state database replicas are removed.
However if you reboot the operating system when the existing state database replicas are
removed from disks, all configuration data of SVM will be lost.
10.1.2.5 Hot Spare Pool
A hot spare pool is a set of slices (hot spares) that are reserved by SVM and can be used to
automatically replace failed components. You can use these hot spares in submirrors or
RAID-5 volumes. Hot spares can enhance data availability of RAID-1 volumes and RAID-5
volumes.
In case of component failure, you can use SVM to search for the first hot spare whose size is
not smaller than that of the failed component. If the hot spare part is found, SVM
automatically replaces the failed component and re-synchronizes data. If slices of proper size
are not found in the list of hot spares, it indicates that submirrors or RAID-5 volumes have
failed.
10.1.2.6 Disk Set
A disk set is a set of physical storage volumes that contain logical volumes and hot spares.
Volumes and hot spare pools must be built on drives within the disk set. After creating a
volume within a disk set, you can use the volume just like using a physical disk slice.
Disk sets can ensure data availability in a cluster environment. If a host fails, another host can
take over disk sets of the failed host. This configuration method is called failover
configuration. Additionally, you can manage the namespace of SVM and access storage
devices connected over network at any time using disk sets.
HUAWEI SAN Storage Host Connectivity Guide for Solaris 10 Volume Management
Issue (2017-07-19) Huawei Proprietary and Confidential
Copyright © Huawei Technologies Co., Ltd.
98
10.1.3 Installing SVM
By default, SVM is automatically installed along with the installation of the host operating
system and does not need to be configured.
10.1.4 Common Configuration Commands
This section describes how to configure SVM using CLIs.
This document only lists common maintenance commands. You can obtain more details at:
http://docs.oracle.com/cd/E18752_01/html/816-4520/tasks-basics-28.html
10.1.4.1 State Database
The SVM state database contains configuration and status information about all volumes, hot
spares, and disk sets. SVM maintains multiple replicas of the state database to provide
redundancy and to prevent the database from being corrupted during a system crash (at most,
only one database replica will be corrupted).
The state database replicas ensure that the data in the state database is always valid. When the
state database is updated, each state database replica is also updated. Only one replica is
updated at a time in case of corruption of all updated replicas due to system crash.
Table 10-2 lists common maintenance commands used for managing SVM state database
replicas.
Table 10-2 Common maintenance commands for managing state database replicas
Task Command
Create a state database
replica.
metadb -a -c number -f ctds-of-slice
Check the status of a state
database replica.
metadb -i
Delete a state database
replica.
metadb -d -f ctds-of-slice
Do not place state database replicas on fabric-attached storage, SANs, or other storage that is
not directly attached to the system. You might not be able to boot SVM. Replicas must be on
storage devices that are available at the same point in the boot process as traditional SCSI or
IDE drives.
For example:
bash-3.2# metadb -a -c 3 -f c1t2d0s2
bash-3.2# metadb -i
flags first blk block count
a u 16 8192 /dev/dsk/c1t2d0s2
a u 8208 8192 /dev/dsk/c1t2d0s2
HUAWEI SAN Storage Host Connectivity Guide for Solaris 10 Volume Management
Issue (2017-07-19) Huawei Proprietary and Confidential
Copyright © Huawei Technologies Co., Ltd.
99
a u 16400 8192 /dev/dsk/c1t2d0s2
r - replica does not have device relocation information
o - replica active prior to last mddb configuration change
u - replica is up to date
l - locator for this replica was read successfully
c - replica's location was in /etc/lvm/mddb.cf
p - replica's location was patched in kernel
m - replica is master, this is replica selected as input
W - replica has device write errors
a - replica is active, commits are occurring to this replica
M - replica had problem with master blocks
D - replica had problem with data blocks
F - replica had format problems
S - replica is too small to hold current data base
R - replica had device read errors
bash-3.2#
bash-3.2# metadb -d -f c1t2d0s2
bash-3.2#
bash-3.2# metadb -i
10.1.4.2 Volume
The Solaris operating system supports RAID-0, RAID-1, and RAID-5. Table 10-3 lists
common maintenance commands for these three kinds of volumes.
Table 10-3 Common maintenance commands for three kinds of volumes
Volume Name
Command
RAID-0 metainit volume-name number-of-stripes components-per-stripe
component-names
RAID-1 metainit volume-name -m submirror-name
metattach volume-name submirror-name
RAID-5 metainit volume-name -r component component component
In the preceding table, each parameter is defined as follows:
volume-name: indicates the name of a volume that you need to create.
number-of-stripes: indicates the number of stripes that you need to create.
components-per-stripe: indicates the quantity of components included in each stripe.
component: indicates the name of a component that you have used. You need to separate
them by a space ( ) if you have used multiple components.
submirror-name: indicates the name of a component to be used as the first submirror.
The following describes how to create the preceding three kinds of volumes:
Create a RAID-0 volume:
bash-3.00# metainit d10 1 2 c3t2200001882E6B60Bd1s5 c3t2200001882E6B60Bd2s2
d10: Concat/Stripe is setup
bash-3.00#
HUAWEI SAN Storage Host Connectivity Guide for Solaris 10 Volume Management
Issue (2017-07-19) Huawei Proprietary and Confidential
Copyright © Huawei Technologies Co., Ltd.
100
bash-3.00# metastat
d10: Concat/Stripe
Size: 4181760 blocks (2.0 GB)
Stripe 0: (interlace: 32 blocks)
Device Start Block Dbase Reloc
/dev/dsk/c3t2200001882E6B60Bd1s5 0 No Yes
/dev/dsk/c3t2200001882E6B60Bd2s2 1920 No Yes
Device Relocation Information:
Device Reloc Device ID
/dev/dsk/c3t2200001882E6B60Bd1 Yes id1,ssd@n6001882100e6b60b0060b97b00000005
/dev/dsk/c3t2200001882E6B60Bd2 Yes id1,ssd@n6001882100e6b60b008f84bd00000007
A RAID-0 (stripe) volume has been created by running the preceding commands.
bash-3.00# metainit d12 2 1 c3t2200001882E6B60Bd1s5 1 c3t2200001882E6B60Bd2s2
d12: Concat/Stripe is setup
bash-3.00# metastat
d12: Concat/Stripe
Size: 4189440 blocks (2.0 GB)
Stripe 0:
Device Start Block Dbase Reloc
/dev/dsk/c3t2200001882E6B60Bd1s5 0 No Yes
Stripe 1:
Device Start Block Dbase Reloc
/dev/dsk/c3t2200001882E6B60Bd2s2 1920 No Yes
Device Relocation Information:
Device Reloc Device ID
/dev/dsk/c3t2200001882E6B60Bd1 Yes id1,ssd@n6001882100e6b60b0060b97b00000005
/dev/dsk/c3t2200001882E6B60Bd2 Yes id1,ssd@n6001882100e6b60b008f84bd00000007
bash-3.00#
A RAID-0 (concatenation) volume has been created by running the preceding commands.
Create a RAID-1 volume:
bash-3.00# metainit d10 1 1 c3t2200001882E6B60Bd3s2
d10: Concat/Stripe is setup
bash-3.00# metainit d12 1 1 c3t2200001882E6B60Bd4s2
d12: Concat/Stripe is setup
bash-3.00# metastat
d12: Concat/Stripe
Size: 10481280 blocks (5.0 GB)
Stripe 0:
Device Start Block Dbase Reloc
/dev/dsk/c3t2200001882E6B60Bd4s2 0 No Yes
d10: Concat/Stripe
Size: 10481280 blocks (5.0 GB)
Stripe 0:
Device Start Block Dbase Reloc
/dev/dsk/c3t2200001882E6B60Bd3s2 0 No Yes
Device Relocation Information:
Device Reloc Device ID
/dev/dsk/c3t2200001882E6B60Bd4 Yes id1,ssd@n6001882100e6b60b00b333bf00000009
HUAWEI SAN Storage Host Connectivity Guide for Solaris 10 Volume Management
Issue (2017-07-19) Huawei Proprietary and Confidential
Copyright © Huawei Technologies Co., Ltd.
101
/dev/dsk/c3t2200001882E6B60Bd3 Yes id1,ssd@n6001882100e6b60b00b32e0000000008
bash-3.00#
bash-3.00# metainit d13 -m d10
d13: Mirror is setup
bash-3.00# metattach d13 d12
d13: submirror d12 is attached
bash-3.00# metastat
d13: Mirror
Submirror 0: d10
State: Okay
Submirror 1: d12
State: Resyncing
Resync in progress: 0 % done
Pass: 1
Read option: roundrobin (default)
Write option: parallel (default)
Size: 10481280 blocks (5.0 GB)
d10: Submirror of d13
State: Okay
Size: 10481280 blocks (5.0 GB)
Stripe 0:
Device Start Block Dbase State Reloc Hot Spare
/dev/dsk/c3t2200001882E6B60Bd3s2 0 No Okay Yes
d12: Submirror of d13
State: Resyncing
Size: 10481280 blocks (5.0 GB)
Stripe 0:
Device Start Block Dbase State Reloc Hot Spare
/dev/dsk/c3t2200001882E6B60Bd4s2 0 No Okay Yes
Device Relocation Information:
Device Reloc Device ID
/dev/dsk/c3t2200001882E6B60Bd4 Yes id1,ssd@n6001882100e6b60b00b333bf00000009
/dev/dsk/c3t2200001882E6B60Bd3 Yes id1,ssd@n6001882100e6b60b00b32e0000000008
bash-3.00#
A RAID-1 volume has been created by running the preceding commands.
When creating a RAID-1 volume, you must note the following:
You need to create RAID-0 (stripe or concatenation) volumes before creating a mirror.
You need to create a one-way mirror and attach the second submirror. This policy enables
re-synchronization.
You need to use submirrors of the same size, because partial disk space may be
unavailable if you use submirrors of different sizes.
HUAWEI SAN Storage Host Connectivity Guide for Solaris 10 Volume Management
Issue (2017-07-19) Huawei Proprietary and Confidential
Copyright © Huawei Technologies Co., Ltd.
102
If the first submirror is not attached from cylinder 0 to a mirrored file system, all other
submirrors attached also do this.
You only need to mount a mirroring device. Do not mount any submirror unless such a
mirror is in the offline state and mounted in read-only mode. Do not mount slices that are
part of submirrors. To mount these disks may cause data destruction and system crash.
Create a RAID-5 volume:
bash-3.00# metainit d15 -r c3t2200001882E6B60Bd7s2 c3t2200001882E6B60Bd8s2
c3t2200001882E6B60Bd9s2
d15: RAID is setup
bash-3.00# metastat
d15: RAID
State: Initializing
Initialization in progress: 1.7% done
Interlace: 32 blocks
Size: 12566400 blocks (6.0 GB)
Original device:
Size: 12567616 blocks (6.0 GB)
Device Start Block Dbase State Reloc Hot Spare
/dev/dsk/c3t2200001882E6B60Bd7s2 2250 No Initializing Yes
/dev/dsk/c3t2200001882E6B60Bd8s2 2250 No Initializing Yes
/dev/dsk/c3t2200001882E6B60Bd9s2 2250 No Initializing Yes
Device Relocation Information:
Device Reloc Device ID
/dev/dsk/c3t2200001882E6B60Bd7 Yes id1,ssd@n6001882100e6b60b00f28b680000000c
/dev/dsk/c3t2200001882E6B60Bd8 Yes id1,ssd@n6001882100e6b60b00f291420000000d
/dev/dsk/c3t2200001882E6B60Bd9 Yes id1,ssd@n6001882100e6b60b00f297770000000e
bash-3.00#
bash-3.00# metastat
d15: RAID
State: Okay
Interlace: 32 blocks
Size: 12566400 blocks (6.0 GB)
Original device:
Size: 12567616 blocks (6.0 GB)
Device Start Block Dbase State Reloc Hot Spare
/dev/dsk/c3t2200001882E6B60Bd7s2 2250 No Okay Yes
/dev/dsk/c3t2200001882E6B60Bd8s2 2250 No Okay Yes
/dev/dsk/c3t2200001882E6B60Bd9s2 2250 No Okay Yes
Device Relocation Information:
Device Reloc Device ID
/dev/dsk/c3t2200001882E6B60Bd7 Yes id1,ssd@n6001882100e6b60b00f28b680000000c
/dev/dsk/c3t2200001882E6B60Bd8 Yes id1,ssd@n6001882100e6b60b00f291420000000d
/dev/dsk/c3t2200001882E6B60Bd9 Yes id1,ssd@n6001882100e6b60b00f297770000000e
bash-3.00#
After you create the RAID-1 and RAID-5 volumes, data synchronization is enabled. You
cannot perform other volume operations until data is completely synchronized.
10.1.4.3 Soft Partition
Table 10-4 lists common maintenance commands for soft partitions
HUAWEI SAN Storage Host Connectivity Guide for Solaris 10 Volume Management
Issue (2017-07-19) Huawei Proprietary and Confidential
Copyright © Huawei Technologies Co., Ltd.
103
Table 10-4 Common maintenance commands for soft partitions
Task Command
Create a soft partition. metainit [-s diskset] soft-partition -p [-e] component size
Check a soft partition. metastat soft-partition
Delete a soft partition. metaclear [-s diskset] component
metaclear [-s diskset] -r soft-partition
metaclear [-s diskset] -p component
In the preceding table, each parameter is defined as follows:
-s diskset: indicates a disk set that you need to use. If -s diskset is not specified, a local
(default) disk set is to be used.
-p: indicates that you need to configure a soft partition.
-e: indicates that you must reformat the whole disk. The formatted disk contains slice 0,
which occupies most disk space. In addition, it provides slice 7 whose size is at least 4
MB and the slice 7 contains state database replicas.
soft-partition: indicates the name of a soft partition. The name is displayed in dnnn
format, where nnn indicates a number that ranges from 0 to 8192.
component: indicates a disk, slice, or logical volume where you need to create the soft
partition. All existing data stored on the component is destroyed, because the soft
partition headers are written at the beginning of the component.
size: indicates the size of a soft partition.
For example:
bash-3.00# metainit d100 -p d17 2048M
d100: Soft Partition is setup
bash-3.00# metainit d101 -p d16 2048M
d101: Soft Partition is setup
bash-3.00# metainit d102 -p c3t2200001882E6B60Bd15s2 2G
d102: Soft Partition is setup
bash-3.00# metaclear d17
bash-3.00# metaclear -p c3t2200001882E6B60Bd15s2
bash-3.00# metaclear d101
10.1.4.4 Hot Spare Pool
Table 10-5 lists common maintenance commands for hot spare pools
Table 10-5 Common maintenance commands for hot spare pools
Task Command
Create a hot spare pool. metainit hot-spare-pool-name ctds-for-slice
Add slices to a hot spare
pool.
metahs -a hot-spare-pool-name slice-to-add
metahs -a -all hot-spare-pool-name slice-to-add
HUAWEI SAN Storage Host Connectivity Guide for Solaris 10 Volume Management
Issue (2017-07-19) Huawei Proprietary and Confidential
Copyright © Huawei Technologies Co., Ltd.
104
Task Command
Associate a hot spare pool
with volumes
metaparam -h hot-spare-pool component
Check the states of a hot
spare pool and hot spares.
metastat hot-spare-pool-name
Replace hot spares
included in a hot spare
pool.
metahs -r hot-spare-pool-name current-hot-spare
replacement-hot-spare
Delete hot spares included
in a hot spare pool.
metahs -d hot-spare-pool-name current-hot-spare
In the preceding table, each parameter is defined as follows:
hot-spare-pool-name: indicates the name of a hot spare pool.
ctds-for-slice: indicates slices that you need to add to a hot spare pool. For each slice to
be added to a hot spare pool, you need to repeat this task.
slice-to-add: indicates slices that you need to add to a hot spare pool.
component: indicates the name of a submirror or RAID-5 volume associated with a hot
spare pool.
current-hot-spare: indicates the name of the current hot spare to be replaced.
replacement-hot-spare: indicates the name of a slice of the current hot spare to be
replaced in a specified hot spare pool.
Examples are given as follows:
Create a hot spare pool:
bash-3.00# metainit hsp001 c3t2200001882E6B60Bd16s2 c3t2200001882E6B60Bd17s2
hsp001: Hotspare pool is setup
Add slices to a hot spare pool:
bash-3.00# metastat hsp003
hsp003: 1 hot spare
Device Status Length Reloc
/dev/dsk/c3t2200001882E6B60Bd21s2 Available 2092800 blocks Yes
Device Relocation Information:
Device Reloc Device ID
/dev/dsk/c3t2200001882E6B60Bd21 Yes id1,ssd@n6001882100e6b60b04c54b6f0000001a
bash-3.00#
bash-3.00# metahs -a hsp003 c3t2200001882E6B60Bd20s2
hsp003: Hotspare is added
bash-3.00# metastat hsp003
hsp003: 2 hot spares
Device Status Length Reloc
/dev/dsk/c3t2200001882E6B60Bd21s2 Available 2092800 blocks Yes
/dev/dsk/c3t2200001882E6B60Bd20s2 Available 2092800 blocks Yes
Device Relocation Information:
Device Reloc Device ID
HUAWEI SAN Storage Host Connectivity Guide for Solaris 10 Volume Management
Issue (2017-07-19) Huawei Proprietary and Confidential
Copyright © Huawei Technologies Co., Ltd.
105
/dev/dsk/c3t2200001882E6B60Bd21 Yes id1,ssd@n6001882100e6b60b04c54b6f0000001a
/dev/dsk/c3t2200001882E6B60Bd20 Yes id1,ssd@n6001882100e6b60b04c545d400000019
Associate a hot spare pool with volumes:
bash-3.00# metaparam -h hsp001 d16
bash-3.00# metastat d16
d16: Concat/Stripe
Hot spare pool: hsp001
Size: 12568320 blocks (6.0 GB)
Stripe 0: (interlace: 32 blocks)
Device Start Block Dbase State Reloc Hot Spare
/dev/dsk/c3t2200001882E6B60Bd11s2 0 No Okay Yes
/dev/dsk/c3t2200001882E6B60Bd12s2 1920 No Okay Yes
Device Relocation Information:
Device Reloc Device ID
/dev/dsk/c3t2200001882E6B60Bd11 Yes id1,ssd@n6001882100e6b60b00f2a33c00000010
/dev/dsk/c3t2200001882E6B60Bd12 Yes id1,ssd@n6001882100e6b60b00f2a8d300000011
bash-3.00#
Replace hot spares included in a hot spare pool:
bash-3.00# metastat hsp002
hsp002: 2 hot spares
Device Status Length Reloc
/dev/dsk/c3t2200001882E6B60Bd18s2 Available 2092800 blocks Yes
/dev/dsk/c3t2200001882E6B60Bd19s2 Available 2092800 blocks Yes
Device Relocation Information:
Device Reloc Device ID
/dev/dsk/c3t2200001882E6B60Bd18 Yes id1,ssd@n6001882100e6b60b04c53acc00000017
/dev/dsk/c3t2200001882E6B60Bd19 Yes id1,ssd@n6001882100e6b60b04c5404b00000018
bash-3.00# metahs -r hsp002 c3t2200001882E6B60Bd18s2 c3t2200001882E6B60Bd22s2
hsp002: Hotspare c3t2200001882E6B60Bd18s2 is replaced with c3t2200001882E6B60Bd22s2
bash-3.00# metastat hsp002
hsp002: 2 hot spares
Device Status Length Reloc
/dev/dsk/c3t2200001882E6B60Bd22s2 Available 2092800 blocks Yes
/dev/dsk/c3t2200001882E6B60Bd19s2 Available 2092800 blocks Yes
Device Relocation Information:
Device Reloc Device ID
/dev/dsk/c3t2200001882E6B60Bd22 Yes id1,ssd@n6001882100e6b60b04c550fc0000001b
/dev/dsk/c3t2200001882E6B60Bd19 Yes id1,ssd@n6001882100e6b60b04c5404b00000018
bash-3.00#
Delete hot spares included in a hot spare pool:
bash-3.00# metastat hsp003
hsp003: 2 hot spares
Device Status Length Reloc
/dev/dsk/c3t2200001882E6B60Bd20s2 Available 2092800 blocks Yes
/dev/dsk/c3t2200001882E6B60Bd21s2 Available 2092800 blocks Yes
Device Relocation Information:
Device Reloc Device ID
HUAWEI SAN Storage Host Connectivity Guide for Solaris 10 Volume Management
Issue (2017-07-19) Huawei Proprietary and Confidential
Copyright © Huawei Technologies Co., Ltd.
106
/dev/dsk/c3t2200001882E6B60Bd20 Yes id1,ssd@n6001882100e6b60b04c545d400000019
/dev/dsk/c3t2200001882E6B60Bd21 Yes id1,ssd@n6001882100e6b60b04c54b6f0000001a
bash-3.00# metahs -d hsp003 c3t2200001882E6B60Bd20s2
hsp003: Hotspare is deleted
bash-3.00# metastat hsp003
hsp003: 1 hot spare
Device Status Length Reloc
/dev/dsk/c3t2200001882E6B60Bd21s2 Available 2092800 blocks Yes
Device Relocation Information:
Device Reloc Device ID
/dev/dsk/c3t2200001882E6B60Bd21 Yes id1,ssd@n6001882100e6b60b04c54b6f0000001a
10.1.4.5 Disk Set
Table 10-6 lists common maintenance commands for disk sets
Table 10-6 Common maintenance commands for disk sets
Task Command
Create a disk set. metaset -s diskset-name -a -h -M hostname
Add disks to a disk set. metaset -s diskset-name -a disk-name
Add hosts to a disk set. metaset -s diskset-name -a -h hostname
Create SVM volumes in a
disk set.
command -s diskset-name
Delete disks from a disk
set.
metaset -s diskset-name -d disk-name
Delete a host or disk set. metaset -s diskset-name -d -h hostname
In the preceding table, each parameter is defined as follows:
diskset-name: indicates the name of a disk set for which the metaset command is
executed.
hostname: indicates a host name, which is the same as that found in the /etc/nodename
file.
disk-name: indicates a disk that you need to operate. The disk name takes the cxtxdx
format. You can add a disk without the sx identifier to a disk set.
The commands for creating an SVM volume in a disk set are the same as those for creating a
volume. However, each command is followed by -s diskset-name.
Examples are given as follows:
Create a disk set:
HUAWEI SAN Storage Host Connectivity Guide for Solaris 10 Volume Management
Issue (2017-07-19) Huawei Proprietary and Confidential
Copyright © Huawei Technologies Co., Ltd.
107
bash-3.00# metaset
bash-3.00# metaset -s blue -a -h solaris11
bash-3.00# metaset
Set name = blue, Set number = 1
Host Owner
solaris11
bash-3.00#
Add disks to a disk set:
bash-3.00# metaset -s blue -a c3t2200001882E6B60Bd18
bash-3.00# metaset -s blue -a c3t2200001882E6B60Bd24 c3t2200001882E6B60Bd23
bash-3.00# metaset
Set name = blue, Set number = 1
Host Owner
solaris11 Yes
Drive Dbase
/dev/dsk/c3t2200001882E6B60Bd18 Yes
/dev/dsk/c3t2200001882E6B60Bd24 Yes
/dev/dsk/c3t2200001882E6B60Bd23 Yes
Multi-owner Set name = red, Set number = 2, Master =
Host Owner Member
solaris11 Yes
bash-3.00#
Add hosts to a disk set:
bash-3.00# metaset -s blue -a -h host2
bash-3.00# metaset
Set name = blue, Set number = 1
Host Owner
host1 Yes
host2
Drive Dbase
c1t6d0 Yes
c2t6d0 Yes
Create SVM volumes in a disk set:
bash-3.00# metainit -s blue d11 1 1 c1t6d0s0
blue/d11: Concat/Stripe is setup
bash-3.00# metainit -s blue d12 1 1 c2t6d0s0
blue/d12: Concat/Stripe is setup
bash-3.00# metainit -s blue d10 -m d11
blue/d10: Mirror is setup
bash-3.00# metattach -s blue d10 d12
HUAWEI SAN Storage Host Connectivity Guide for Solaris 10 Volume Management
Issue (2017-07-19) Huawei Proprietary and Confidential
Copyright © Huawei Technologies Co., Ltd.
108
blue/d10: submirror blue/d12 is attached
bash-3.00#
bash-3.00#
bash-3.00# metastat -s blue
blue/d10: Mirror
Submirror 0: blue/d11
State: Okay
Submirror 1: blue/d12
State: Resyncing
Resync in progress: 0 % done
Pass: 1
Read option: roundrobin (default)
Write option: parallel (default)
Size: 17674902 blocks
blue/d11: Submirror of blue/d10
State: Okay
Size: 17674902 blocks
Stripe 0:
Device Start Block Dbase State Reloc Hot Spare
c1t6d0s0 0 No Okay
blue/d12: Submirror of blue/d10
State: Resyncing
Size: 17674902 blocks
Stripe 0:
Device Start Block Dbase State Reloc Hot Spare
c2t6d0s0 0 No Okay
Delete disks from a disk set:
bash-3.00# metaset -s blue -d c3t2200001882E6B60Bd23
Delete a host or disk set:
bash-3.00# metaset -s blue -d c3t2200001882E6B60Bd23
bash-3.00# metaset -s blue -d c3t2200001882E6B60Bd18
metaset: solaris11: Must specify -f option to delete all drives from set
bash-3.00# metaset -s blue -f -d c3t2200001882E6B60Bd18
bash-3.00# metaset -s blue
Set name = blue, Set number = 1
Host Owner
solaris11
bash-3.00# metaset -s blue -d -h solaris11
bash-3.00# metaset
Multi-owner Set name = red, Set number = 2, Master = solaris11
Host Owner Member
solaris11 multi-owner Yes
Drive Dbase
/dev/dsk/c3t2200001882E6B60Bd25 Yes
/dev/dsk/c3t2200001882E6B60Bd26 Yes
HUAWEI SAN Storage Host Connectivity Guide for Solaris 10 Volume Management
Issue (2017-07-19) Huawei Proprietary and Confidential
Copyright © Huawei Technologies Co., Ltd.
109
10.2 VxVM
10.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.
10.2.2 Installation
VxVM is not for free and does not come pre-installed in an operating system.
10.2.2.1 Pre-installation Check
Before installation, run the following command to check whether VxVM has been installed:
pkginfo|grep –i vxvm
No information will be displayed if it is not installed.
10.2.2.2 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.
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
HUAWEI SAN Storage Host Connectivity Guide for Solaris 10 Volume Management
Issue (2017-07-19) Huawei Proprietary and Confidential
Copyright © Huawei Technologies Co., Ltd.
110
10.2.3 Common Configuration Commands
10.2.3.1 Loading Disks
After you run the LUN scanning command, the Solaris 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-3.2# vxdisk list
DEVICE TYPE DISK GROUP STATUS
aluadisk0_0 auto:none - - online invalid
aluadisk0_1 auto - - error
bash-3.2#
A LUN mapped to a host is in the error or nolabel state on VxVM.
If the LUN is labeled on the host, the LUN turns to the online invalid state.
The LUN changes to the online state after it is initialized on VxVM.
10.2.3.2 Initializing Disks
You need to initialize a disk by running the vxdisksetup -i diskname command. The disk
turns to the online state after the disk is successfully initialized. For example:
bash-3.2# vxdisksetup -i aluadisk0_0
bash-3.2# vxdisk list
DEVICE TYPE DISK GROUP STATUS
aluadisk0_0 auto:cdsdisk - - online
aluadisk0_1 auto - - error
bash-3.2#
10.2.3.3 Creating a Disk Group
After initializing a disk, you can create a disk group by running the following command:
bash-3.2# vxdg init dg1 aluadisk0_0
bash-3.2# vxdisk list
DEVICE TYPE DISK GROUP STATUS
aluadisk0_0 auto:cdsdisk aluadisk0_0 dg1 online
aluadisk0_1 auto:none - - online invalid
bash-3.2#
10.2.3.4 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-3.2# vxassist -g dg1 make vol1 1g
HUAWEI SAN Storage Host Connectivity Guide for Solaris 10 Volume Management
Issue (2017-07-19) Huawei Proprietary and Confidential
Copyright © Huawei Technologies Co., Ltd.
111
bash-3.2# vxprint
Disk group: dg1
TY NAME ASSOC KSTATE LENGTH PLOFFS STATE TUTIL0 PUTIL0
dg dg1 dg1 - - - - - -
dm aluadisk0_0 aluadisk0_0 - 10415488 - - - -
v vol1 fsgen ENABLED 2097152 - ACTIVE - -
pl vol1-01 vol1 ENABLED 2097152 - ACTIVE - -
sd aluadisk0_0-01 vol1-01 ENABLED 2097152 0 - - -
bash-3.2#
10.2.3.5 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.
The following is an example:
bash-3.2# newfs /dev/vx/rdsk/dg1/vol1
newfs: construct a new file system /dev/vx/rdsk/dg1/vol1: (y/n)? y
/dev/vx/rdsk/dg1/vol1: 2097152 sectors in 1024 cylinders of 32 tracks, 64 sectors
1024.0MB in 32 cyl groups (32 c/g, 32.00MB/g, 15872 i/g)
super-block backups (for fsck -F ufs -o b=#) at:
32, 65632, 131232, 196832, 262432, 328032, 393632, 459232, 524832, 590432,
1443232, 1508832, 1574432, 1640032, 1705632, 1771232, 1836832, 1902432,
1968032, 2033632
bash-3.2#
10.2.3.6 Mounting a Volume
You can mount a created volume to a directory. The command syntax is as follows:
mount /dev/vx/dsk/diskgroup/volumename directory
10.2.3.7 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 diskgroup stop volumename
The following is an example:
bash-3.2# vxprint
Disk group: dg1
TY NAME ASSOC KSTATE LENGTH PLOFFS STATE TUTIL0 PUTIL0
dg dg1 dg1 - - - - - -
dm aluadisk0_0 aluadisk0_0 - 10415488 - - - -
v vol1 fsgen ENABLED 2097152 - ACTIVE - -
pl vol1-01 vol1 ENABLED 2097152 - ACTIVE - -
sd aluadisk0_0-01 vol1-01 ENABLED 2097152 0 - - -
bash-3.2# vxvol -g dg1 stop vol1
bash-3.2# vxprint
HUAWEI SAN Storage Host Connectivity Guide for Solaris 10 Volume Management
Issue (2017-07-19) Huawei Proprietary and Confidential
Copyright © Huawei Technologies Co., Ltd.
112
Disk group: dg1
TY NAME ASSOC KSTATE LENGTH PLOFFS STATE TUTIL0 PUTIL0
dg dg1 dg1 - - - - - -
dm aluadisk0_0 aluadisk0_0 - 10415488 - - - -
v vol1 fsgen DISABLED 2097152 - CLEAN - -
pl vol1-01 vol1 DISABLED 2097152 - CLEAN - -
sd aluadisk0_0-01 vol1-01 ENABLED 2097152 0 - - -
bash-3.2#
10.2.3.8 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-3.2# vxvol -g dg1 start vol1
bash-3.2# vxprint
Disk group: dg1
TY NAME ASSOC KSTATE LENGTH PLOFFS STATE TUTIL0 PUTIL0
dg dg1 dg1 - - - - - -
dm aluadisk0_0 aluadisk0_0 - 10415488 - - - -
v vol1 fsgen ENABLED 2097152 - ACTIVE - -
pl vol1-01 vol1 ENABLED 2097152 - ACTIVE - -
sd aluadisk0_0-01 vol1-01 ENABLED 2097152 0 - - -
bash-3.2#
10.2.3.9 Deleting a Volume
The command syntax is described as follows:
vxedit -g DG -rf rm volume name
The following is an example:
bash-3.2# vxedit -g dg1 -rf rm vol1
bash-3.2# vxprint
Disk group: dg1
TY NAME ASSOC KSTATE LENGTH PLOFFS STATE TUTIL0 PUTIL0
dg dg1 dg1 - - - - - -
dm aluadisk0_0 aluadisk0_0 - 10415488 - - - -
bash-3.2#
HUAWEI SAN Storage Host Connectivity Guide for Solaris 10 Volume Management
Issue (2017-07-19) Huawei Proprietary and Confidential
Copyright © Huawei Technologies Co., Ltd.
113
10.2.3.10 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-3.2# vxvol -g dg1 stop vol1
bash-3.2# vxdg deport dg1
bash-3.2# vxprint
bash-3.2#
10.2.3.11 Importing a DG
The command syntax is as follows:
vxdg import DG name
The following is an example:
bash-3.2# vxdg import dg1
bash-3.2# vxprint
Disk group: dg1
TY NAME ASSOC KSTATE LENGTH PLOFFS STATE TUTIL0 PUTIL0
dg dg1 dg1 - - - - - -
dm aluadisk0_0 aluadisk0_0 - 10415488 - - - -
v vol1 fsgen ENABLED 2097152 - ACTIVE - -
pl vol1-01 vol1 ENABLED 2097152 - ACTIVE - -
sd aluadisk0_0-01 vol1-01 ENABLED 2097152 0 - - -
bash-3.2#
10.2.3.12 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 type
The following is an example:
bash-3.2# vxdisk list
DEVICE TYPE DISK GROUP STATUS
aluadisk0_0 auto:cdsdisk aluadisk0_0 dg1 online
aluadisk0_1 auto:cdsdisk - - online
bash-3.2# vxdg -g dg1 adddisk aluadisk0_1
bash-3.2# vxdisk list
DEVICE TYPE DISK GROUP STATUS
aluadisk0_0 auto:cdsdisk aluadisk0_0 dg1 online
aluadisk0_1 auto:cdsdisk aluadisk0_1 dg1 online
bash-3.2#
10.2.3.13 Removing a Disk from a DG
The command syntax is as follows:
HUAWEI SAN Storage Host Connectivity Guide for Solaris 10 Volume Management
Issue (2017-07-19) Huawei Proprietary and Confidential
Copyright © Huawei Technologies Co., Ltd.
114
vxdg -g DG name rmdisk disk name
The following is an example:
bash-3.2# vxdg -g dg1 rmdisk aluadisk0_1
bash-3.2# vxdisk list
DEVICE TYPE DISK GROUP STATUS
aluadisk0_0 auto:cdsdisk aluadisk0_0 dg1 online
aluadisk0_1 auto:cdsdisk - - online
bash-3.2#
HUAWEI SAN Storage Host Connectivity Guide for Solaris 11 High-Availability Technologies
Issue (2017-07-19) Huawei Proprietary and Confidential
Copyright © Huawei Technologies Co., Ltd.
115
11 High-Availability Technologies
11.1 Overview
A cluster consists of two or more systems or nodes, which provide applications, system
resources, and data for users as a sustainable system. Each cluster node is an independent
system that has complete functions.
A high availability (HA) cluster keeps running in the event of a fault, ensuring almost
continuous access to data and applications. However, these faults cause a single server to
break down. A single fault, such as a hardware, software, or network fault, does not cause the
failure of a cluster.
A Sun Cluster system is a set of closely connected nodes, which provide a single management
view for network services and applications. The Sun Cluster system enables HA by
combining hardware with software as follows:
Redundant disk systems provide storage.
Redundant hot-swap components, such as power supply and cooling systems, maintain
the continuous operation of the Sun Cluster system after hardware fails, improving
system HA.
Based on the HA framework, the Sun Cluster system can quickly detect node faults and
migrate applications or services to another node that runs in the same environment.
11.2 Key Concepts
This chapter explains the key concepts related to the hardware and software components of
the Sun Cluster system that you need to understand before using with Sun Cluster systems.
You can obtain more details at:
http://docs.oracle.com/cd/E19787-01/820-2553/concepts-1/index.html
11.2.1 Cluster Nodes
A cluster node is a computer that runs both the Solaris software and Sun Cluster software. The
Sun Cluster software enables a cluster to have two to eight nodes.
HUAWEI SAN Storage Host Connectivity Guide for Solaris 11 High-Availability Technologies
Issue (2017-07-19) Huawei Proprietary and Confidential
Copyright © Huawei Technologies Co., Ltd.
116
Cluster nodes are generally connected to one or more disks. Nodes that are not attached to
disks use the cluster file system to access the multi-host disks. In parallel database
configurations, nodes can concurrently access to some or all disks.
Every node in the cluster knows when another node joins or leaves the cluster. Also, every
node in the cluster knows the resources that are running locally as well as the resources that
are running on the other cluster nodes.
Nodes in the same cluster must have similar processing capabilities, memory, and I/O
capacity to enable failover without significant decrease in performance. Because of the
possibility of failover, each node must have sufficient capacity to meet service level
agreements if a node fails.
11.2.2 Cluster Interconnection
Cluster interconnection is the physical configuration of devices that are used to transfer
cluster-dedicated communications and data service communications between cluster nodes.
Redundant interconnections enable operations to continue over the surviving interconnection
when system administrators isolate failures and repair communication. The Sun Cluster
software detects, repairs, and automatically re-initiates communication over a repaired
interconnection.
11.2.3 Cluster Membership
The Cluster Membership Monitor (CMM) is a set of distributed agents that exchange
messages over the cluster interconnection to complete the following tasks:
Ensuring a consistent membership view on all nodes (quorum)
Synchronizing configurations in response to membership changes
Handling cluster partitioning
Ensuring full connectivity among all cluster members by leaving failed nodes out of the
cluster until they are repaired
The main function of the CMM is to establish cluster membership, which requires a
cluster-wide agreement between nodes that participate in the cluster at any time.
The CMM detects major cluster status changes on each node, such as communication
interruption of one or more nodes.
The CMM relies on the transport kernel module to generate heartbeats across the transport
medium to other nodes in the cluster. When the CMM does not detect a heartbeat from a node
within a defined time-out period, it considers that the node has failed and initiates a cluster
reconfiguration to renegotiate cluster membership.
To determine cluster membership and data integrity, the CMM performs the following tasks:
Describing a change in cluster membership, such as a node joining or leaving the cluster
Ensuring that a failed node leaves the cluster
Ensuring that a failed node remains inactive until it is repaired
Preventing the cluster from being divided into node subsets
11.2.4 Cluster Configuration Repository
The Cluster Configuration Repository (CCR) is a private, cluster-wide, and distributed
database for storing information about the configuration and status of the cluster. To avoid
HUAWEI SAN Storage Host Connectivity Guide for Solaris 11 High-Availability Technologies
Issue (2017-07-19) Huawei Proprietary and Confidential
Copyright © Huawei Technologies Co., Ltd.
117
corrupting configuration data, each node must be aware of the current state of cluster
resources. The CCR ensures that you have a consistent view of the cluster from all nodes. The
CCR is updated when an error occurs, recovery is implemented, or the general status of the
cluster changes.
The CCR structure contains the following information:
Cluster and node names
Cluster transport configuration
The names of SVM, disk sets, or Veritas disk groups
A list of nodes that can master each disk group
Valid parameter values for data services
Paths to callback methods for data services
DID device configuration
Current cluster status
11.2.5 Fault Monitors
The Sun Cluster system makes all components on the "path" between users and data highly
available by monitoring applications, file systems, and network ports.
The Sun Cluster software detects a node failure quickly and creates an equivalent server for
resources on the failed node. The Sun Cluster software ensures that resources unaffected by
the failed node are constantly available during the recovery and that resources of the failed
node are available as soon as they are recovered.
11.2.5.1 Data Services Monitoring
Each Sun Cluster data service has a fault monitor that periodically probes the data service to
determine its health. A default monitor checks whether application daemons are running and
that clients are being served. Based on the information returned through detection, pre-defined
actions, such as restarting daemons or causing a failover, can be initiated.
11.2.5.2 Disk Path Monitoring
Sun Cluster software supports disk-path monitoring (DPM). DPM improves the overall
reliability of failover and switchover by reporting the failure of a secondary disk-path. You
can use two methods for monitoring paths to disks. The first method is provided by running
the scdpm command. This command enables you to monitor, unmonitor, or display the status
of paths to disks in your cluster.
The second method is provided by the SunPlex Manager GUI. SunPlex Manager provides a
topological view of the monitored paths to disks. The view is updated every 10 minutes to
provide information about the number of failed force replies.
11.2.5.3 IP Multipath Monitoring
Each cluster node has its own IP network multipathing configuration, which may vary with
cluster nodes. IP network multipathing monitors the following network communication
failures:
The transmit and receive path of network adapter has stopped transmitting packets.
The network adapter is disconnected with links.
Ports on switches do not transmit or receive packets.
HUAWEI SAN Storage Host Connectivity Guide for Solaris 11 High-Availability Technologies
Issue (2017-07-19) Huawei Proprietary and Confidential
Copyright © Huawei Technologies Co., Ltd.
118
Physical interfaces in a group are unavailable during system boot.
11.2.6 Quorum Devices
A quorum device is a disk that is shared by two or more nodes and is used to check whether a
cluster is running by votes. A cluster can operate only when a quorum of votes is available.
The quorum device is used to determine which nodes constitute a new cluster when a cluster
is divided into separate sets of nodes.
Both cluster nodes and quorum devices vote to form quorum. By default, cluster nodes
acquire a quorum vote count of one when they boot and become cluster members. Nodes can
have a vote count of zero when a node is being installed, or when an administrator has set a
node to the maintenance state.
Quorum devices acquire quorum vote counts that are based on the number of nodes
connecting to the devices. When you set up a quorum device, it acquires the maximum vote
count of N-1 where N is the number of connected votes to the quorum device. For example, a
quorum device that is connected to two nodes with nonzero vote counts has a quorum count
of one (two minus one).
11.2.6.1 Data Integrity
The Sun Cluster system attempts to prevent data corruption and ensure data integrity. A
cluster must never be split into separate zones that are active at the same time, because cluster
nodes share data and resources. The CMM guarantees that only one cluster is operational at
any time.
Two types of problems may arise from cluster partitions: split brain and amnesia. Split brain
occurs when the cluster interconnection between nodes is lost, the cluster is partitioned into
subclusters, and each subcluster believes that it is the unique partition. A subcluster that is not
aware of other subclusters may cause a conflict in shared resources, such as duplicate network
addresses and data corruption.
Amnesia occurs if all nodes leave the cluster in staggered groups. An example is a two-node
cluster with nodes A and B. If the node A is shut down, only CCR configuration data stored in
the node B instead of the node A is updated. If the node B is shut down and the node A is
rebooted, the node A may run with original CCR configuration data. This state is called
amnesia, which may cause the operation of a cluster based on original configuration data.
You can avoid split brain and amnesia by giving each node one vote and mandating a majority
of votes for an operational cluster. A partition with a majority of votes takes up a quorum and
is enabled to operate. This multi-vote mechanism applies to a cluster that contains more than
two nodes. Most two-node clusters have two partitions. If such a cluster is partitioned, an
external vote enables a partition to gain quorum. This external vote is provided by a quorum
device. A quorum device can be any disk that is shared between two nodes.
Table 11-1 describes how the Sun Cluster software uses quorum to avoid split brain and
amnesia.
Table 11-1 Cluster quorum, split brain, and amnesia
Partition Type Quorum Solution
Split brain Enables only a partition (subcluster) with a majority of votes to run
as the cluster (only one partition can exist with a majority of votes).
After a node loses the race for quorum, it is out of service.
HUAWEI SAN Storage Host Connectivity Guide for Solaris 11 High-Availability Technologies
Issue (2017-07-19) Huawei Proprietary and Confidential
Copyright © Huawei Technologies Co., Ltd.
119
Partition Type Quorum Solution
Amnesia Guarantees that when a cluster is booted, it has at least one node that
is one of latest cluster members (latest configuration data is
provided).
11.2.6.2 Failure Fencing
A major issue for clusters is a failure that causes the partitioning of a cluster (called split
brain). When this situation occurs, not all nodes can be used for communication. A single
node or subset may attempt to form a separate cluster or subset. Each subset or partition may
"believe" that it has the sole access and ownership to multiple host disks. Attempts by
multiple nodes to write data to disks may cause data corruption.
Failure fencing limits node access to multiple host disks by preventing access to disks. When
a node leaves a cluster that either fails or is partitioned, failure fencing ensures that the node
cannot access disks any longer. Only the current member node has access to disks, ensuring
data integrity.
The Sun Cluster system uses SCSI disk reservations to implement failure fencing. Failed
nodes are "fenced" away from multiple host disks through SCSI reservations, preventing
themselves from accessing those disks.
When a cluster member detects that another node does not interconnect with it, it initiates a
failure fencing procedure to prevent the failed node from accessing shared disks. When this
failure fencing occurs, the fenced node is out of service and a "reservation conflict" message
is displayed on its console.
11.2.6.3 Failfast Mechanism for Failure Fencing
The failfast mechanism disables failed nodes but does not prevent failed nodes from being
rebooted. Failed nodes may be rebooted and rejoined in a cluster after being disabled.
If a node disconnects with other nodes in a cluster and the node is not part of a partition that
can achieve quorum, it is forcibly removed by another node from the cluster. Any node that is
part of a partition that can achieve quorum places reservations on shared disks. Nodes whose
quantity cannot reach a quorum are disabled based on the failfast mechanism.
11.2.6.4 Devices
A global file system makes all files in a cluster equally accessible and visible to all nodes.
Similarly, the Sun Cluster software makes all devices in a cluster accessible and visible
throughout the cluster. That is, the I/O subsystem can access any device in the cluster from
any node, without regard to the place where the device is physically attached. This access is
called global device access.
11.2.6.5 Global Devices
The Sun Cluster system uses global devices to provide cluster-wide, highly available access to
any device in a cluster from any node. Generally, if a node cannot be used to access a global
device, Sun Cluster software switches the current path to another path to the device and
redirects access to the path. This redirection is easy with global devices regardless of the path,
because devices are provided with the same name. Accessing to a remote device is like
accessing a local device of the same name. In addition, APIs used for accessing global devices
in a cluster are the same as those for accessing local devices.
HUAWEI SAN Storage Host Connectivity Guide for Solaris 11 High-Availability Technologies
Issue (2017-07-19) Huawei Proprietary and Confidential
Copyright © Huawei Technologies Co., Ltd.
120
Sun Cluster global devices include disks, CD-ROMs, and tapes. However, disks are the
unique multi-port global devices supported.
A cluster assigns a unique ID to a disk, CD-ROM, or tape. This assignment enables consistent
access to each device from any node in a cluster.
11.2.6.6 Device ID
Sun Cluster software manages global devices using a device ID (DID) driver. The driver
automatically assigns a unique ID to each device in a cluster, such as multiple host disks, tape
drives, and CD-ROMs.
The DID driver is an integral part of accessing global devices in a cluster. It can detect all
cluster nodes and build a list of unique disk devices. Additionally, the DID driver assigns
unique and consistent primary number and secondary number to each device in all cluster
nodes. The DID driver assigns a unique DID instead of Solaris DID to access global devices.
11.2.6.7 Local Devices
Sun Cluster software also manages local devices. These local devices can only be accessed by
nodes that are running and physically connect to the cluster. Local devices are superior to
global devices in terms of performance, because they do not need to concurrently replicate the
status information of multiple nodes. If a device domain fails, the device cannot be accessed
until it is shared by multiple nodes.
11.2.6.8 Device Groups
Disk device groups enable volume manager disk groups to be global, because they provide
multiple paths and hosts for the underlying disks. Each cluster node that physically connects
to multiple host disks provides a path to disk device groups.
In the Sun Cluster system, you can control multiple host disks that use Sun Cluster software
by registering multiple host disks as disk device groups. This makes the Sun Cluster system
detect which volume manager disk group is mapped to a node. The Sun Cluster software
creates a raw disk device group for each disk device and tape device in a cluster. These cluster
device groups keep in the offline state until you access them as global devices either by
mounting a global file system or accessing a raw database file.
11.2.7 Data Services
A data service is the combination of software and configuration files. It helps applications run
normally without the modification of Sun Cluster configuration. When running in a Sun
Cluster configuration, an application runs as a resource under the control of Resource Group
Manager (RGM). Data services enable you to configure applications such as Oracle databases
on a cluster instead of a single server.
Data service software provides the following Sun Cluster management methods for operating
applications:
Starting an application
Stopping an application
Monitoring application faults and removing these faults
The configuration file for data services defines the properties of resources that represent
applications in RGM.
HUAWEI SAN Storage Host Connectivity Guide for Solaris 11 High-Availability Technologies
Issue (2017-07-19) Huawei Proprietary and Confidential
Copyright © Huawei Technologies Co., Ltd.
121
RGM is responsible for processing failover of a cluster and scalable data services. RGM is
used to enable and disable data services on a node selected from a cluster, responding to
change of cluster members. RGM ensures data service applications to use the cluster
framework.
RGM manages data services as resources. A cluster administrator can create and manage
resources in a container called resource group. RGM and administrator operations can ensure
that resources and the resource group are switched between the online state and the offline
state.
11.2.7.1 Description of a Resource Type
A resource type is a collection of properties that describe applications in a cluster. The
collection contains information about how to enable, disable, and monitor applications on a
cluster node. Resource type also includes application-specific properties, which need to be
defined when you run these applications in a cluster. Sun Cluster data services are pre-defined
with multiple resource types. For example, the resource type of Sun Cluster HA for Oracle is
SUNW.oracle-server. The resource type of Sun Cluster HA for Apache is SUNW.apache.
11.2.7.2 Description of a Resource
Resources are instances of resource types defined within a cluster range. You can install
multiple application instances on a cluster based on resource types. When you initialize
resources, RGM assigns values to application-specific properties and the resources inherit any
property on the resource type level.
Data services utilize multiple types of resources. Applications, such as Apache Web Server or
Sun Java System Web Server, utilize network IP addresses that they rely on, including logical
host names and shared IP addresses. Applications and network resources form a basic unit
managed by RGM.
11.2.7.3 Description of a Resource Group
Resources managed by RGM are stored in a resource group and managed as a unit. A resource
group is a group consisting of associated or inter-dependent resources. For example, resources
derived from SUNW.LogicalHostname may be stored in the same resource group together
with resources derived from an Oracle database. If you enable failover or switchover of a
resource group, the resource group is transplanted as a unit.
11.2.7.4 Data Service Types
Data services enable applications to be highly available and scalable, preventing important
cluster applications from being interrupted in case of a single point of failure.
When configuring a data service, you must configure it as one of the following types:
Failover data service
Scalable data service
Parallel data service
11.3 Installation and Configuration
For details about installation and configuration of Solaris Cluster, click the following Solaris official link:
HUAWEI SAN Storage Host Connectivity Guide for Solaris 11 High-Availability Technologies
Issue (2017-07-19) Huawei Proprietary and Confidential
Copyright © Huawei Technologies Co., Ltd.
122
http://www.oracle.com/technetwork/indexes/documentation/index.html
Select corresponding Solaris Cluster version in the Systems Software list to obtain relevant
document directories.
In addition, Huawei provides configuration proposal documents related to the Solaris Cluster
software application for your reference. For details, contact Huawei customer service center.
11.4 Cluster Maintenance
11.4.1 Common Maintenance Commands
11.4.1.1 Viewing the Cluster Status
The command syntax is as follows:
# scstat
11.4.1.2 Switching Resources
Switch resources from a node to another node by running the following command:
scswitch -z -g resource_name -h host_name
11.4.2 Cluster Messages
If a cluster is not running properly, you can use cluster logs and messages to help locate the
cause.
Log information is stored on the /var/adm/messages path.
You can query error messages at:
http://docs.oracle.com/cd/E19050-01/sun.cluster31/819-0427/6n2rsdb6f/index.html
HUAWEI SAN Storage Host Connectivity Guide for Solaris 12 Acronyms and Abbreviations
Issue (2017-07-19) Huawei Proprietary and Confidential
Copyright © Huawei Technologies Co., Ltd.
123
12 Acronyms and Abbreviations
A
ALUA Asymmetric Logical Unit Access
C
CacheFS Cache File System
CCR Cluster Configuration Repository
CDFS CD-ROM File System
CLI Command Line Interface
CMM Cluster Membership Monitor
D
DPM Disk Path Monitoring
F
FC Fibre Channel
H
HBA Host Bus Adapter
HSFS High Sierra File System
I
IP Internet Protocol
HUAWEI SAN Storage Host Connectivity Guide for Solaris 12 Acronyms and Abbreviations
Issue (2017-07-19) Huawei Proprietary and Confidential
Copyright © Huawei Technologies Co., Ltd.
124
ISM Integrated Storage Manager
iSCSI Internet Small Computer System Interface
L
LOFS Loopback File System
LUN Logical Unit Number
N
NFS Network File System
P
PCFS PC File System
PROCFS Process File System
R
RAID Redundant Array of Independent Disks
RGM Resource Group Manager
S
SMC Solaris Management Console
SPARC Scalable Processor Architecture
STMS StorEdge Traffic Manager Software
SVM Solaris Volume Manager
SWAPFS SWAP File System
T
TMPFS Temporary File System
U
UDF Universal Disk Format
HUAWEI SAN Storage Host Connectivity Guide for Solaris 12 Acronyms and Abbreviations
Issue (2017-07-19) Huawei Proprietary and Confidential
Copyright © Huawei Technologies Co., Ltd.
125
V
VxVM Veritas Volume Manager
W
WWN World Wide Name