HUAWEI SAN Storage Host Connectivity Guide for AIXsupport-open.huawei.com/ready/files/document/host-doc/en/AIX.pdf · Technical White Paper HUAWEI SAN Storage Host Connectivity Guide

Technical White Paper

HUAWEI SAN Storage Host Connectivity Guide for AIX

OceanStor Storage

AIX

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://enterprise.huawei.com

http://enterprise.huawei.com/

HUAWEI SAN Storage Host Connectivity Guide for

AIX About This Document



ii

About This Document

Overview

This document details the configuration methods and precautions for connecting Huawei SAN

storage devices to Advanced Interactive eXectuive (AIX) 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.


AIX About This Document



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.


AIX Contents



iv

Contents

About This Document .................................................................................................................... ii

1 AIX Operating System ................................................................................................................. 1

1.1 Introduction to AIX ....................................................................................................................................................... 1

1.2 File Systems in AIX ...................................................................................................................................................... 1

1.3 Directory Structure in AIX............................................................................................................................................ 3

1.4 Common Management Tools and Commands .............................................................................................................. 3

1.4.1 Management Tool ...................................................................................................................................................... 3

1.5 Management Commands .............................................................................................................................................. 4

1.6 Querying and Updating the Operating System Version ................................................................................................ 5

1.6.1 Querying the Current Version .................................................................................................................................... 5

1.6.2 Querying Files That Must Be Updated Before a System Upgrade ............................................................................ 5

1.6.3 Viewing the File Version ............................................................................................................................................ 6

1.7 Application Scenarios ................................................................................................................................................... 6

1.8 Interoperability Between AIX and Storage Systems ..................................................................................................... 7

2 Network Planning ......................................................................................................................... 8

2.1 Non-HyperMetro Network ........................................................................................................................................... 9

2.1.1 Fibre Channel Networking Diagram .......................................................................................................................... 9

2.1.2 iSCSI Network Diagram .......................................................................................................................................... 11

2.2 HyperMetro Network .................................................................................................................................................. 11

2.2.1 Fibre Channel Networking Diagram ........................................................................................................................ 12

3 Preparations Before Configuration (on a Host)..................................................................... 14

3.1 Adjusting the Directory Size ....................................................................................................................................... 14

3.2 Changing the File Size Limit ...................................................................................................................................... 15

3.3 Viewing and Configuring HBAs ................................................................................................................................. 16

3.3.1 HBA Identification ................................................................................................................................................... 16

3.3.2 HBA WWNs ............................................................................................................................................................ 16

3.3.3 HBA Physical Device Identifier Properties ............................................................................................................. 17

3.3.4 HBA Virtual Device Identifier Properties ................................................................................................................ 18

3.3.5 HBA Parameters ...................................................................................................................................................... 18

4 Preparations Before Configuration (on a Storage System) ................................................. 19

5 Switch Configuration ................................................................................................................. 20


AIX Contents



v

5.1 Fibre Channel Switch ................................................................................................................................................. 20

5.1.1 Querying the Switch Model and Version ................................................................................................................. 20

5.1.2 Configuring Zones ................................................................................................................................................... 22

5.1.3 Precautions ............................................................................................................................................................... 25

5.2 Ethernet Switch ........................................................................................................................................................... 25

5.2.1 Configuring VLANs ................................................................................................................................................ 25

5.2.2 Binding Ports (Link Aggregation) ........................................................................................................................... 26

5.3 FCoE Switch ............................................................................................................................................................... 27

5.3.2 Command Introduction ............................................................................................................................................ 28

5.3.3 Creating a VSAN ..................................................................................................................................................... 30

5.3.4 Creating a VLAN ..................................................................................................................................................... 32

5.3.5 Configuring a Port and Adding It to the VLAN ....................................................................................................... 33

5.3.6 Creating a Zone and Adding the Port to It ............................................................................................................... 33

5.3.7 Creating a Zoneset and Adding the Created Zone to It ............................................................................................ 35

6 Establishing Fibre Channel Connections ............................................................................... 37

6.1 Checking Topology Modes ......................................................................................................................................... 37

6.1.1 OceanStor T Series Storage System ......................................................................................................................... 37

6.1.2 OceanStor 18000/T V2/V3/Dorado V3 Series Enterprise Storage System .............................................................. 38

6.2 Adding Initiators ......................................................................................................................................................... 39

6.3 Establishing Connections ............................................................................................................................................ 39

7 Establishing iSCSI Connections .............................................................................................. 40

7.1 Checking iSCSI Software on the Host ........................................................................................................................ 40

7.2 Configuring Service IP Addresses .............................................................................................................................. 41

7.2.1 Storage System ........................................................................................................................................................ 41

7.2.2 Host .......................................................................................................................................................................... 43

7.3 Configuring Initiators on a Host ................................................................................................................................. 44

7.4 Checking Storage System Targets ............................................................................................................................... 45



7.5 Configuring the Host iSCSI Service ........................................................................................................................... 46

7.5.1 S2000 Series/S2600/S5000 Series/S6800E ............................................................................................................. 47

7.5.2 OceanStor S2200T ................................................................................................................................................... 49

7.5.3 S2600T/S5500T/S5600T/S5800T/S6800T .............................................................................................................. 50

7.5.4 S2900/S3900/S5900/S6900 ..................................................................................................................................... 51

7.5.5 OceanStor 18000 Series Enterprise Storage System ................................................................................................ 52

7.6 Establishing Connections ............................................................................................................................................ 52

8 Mapping and Scanning for LUNs ............................................................................................ 53

8.1 Mapping LUNs to a Host ............................................................................................................................................ 53



8.2 Scanning for LUNs on a Host ..................................................................................................................................... 55


AIX Contents



vi

9 Multipathing Management Software...................................................................................... 56

9.1 Overview .................................................................................................................................................................... 56

9.2 UltraPath ..................................................................................................................................................................... 56

9.2.1 Functions ................................................................................................................................................................. 56

9.2.2 Installation and Uninstallation ................................................................................................................................. 57

9.3 MPIO .......................................................................................................................................................................... 57

9.3.1 Configuring and Enabling Multipathing Function ................................................................................................... 57

9.3.2 Multipathing Configuration for New-Version HUAWEI Storage ............................................................................ 57

9.3.3 Multipathing Configuration for Old-Version HUAWEI Storage ............................................................................. 68

10 Volume Management Software.............................................................................................. 71

10.1 LVM .......................................................................................................................................................................... 71

10.1.1 Overview ............................................................................................................................................................... 71

10.1.2 Installation ............................................................................................................................................................. 72

10.1.3 Common Configuration Commands ...................................................................................................................... 72

10.2 VxVM ....................................................................................................................................................................... 78

10.2.1 Overview ............................................................................................................................................................... 78

10.2.2 Installation ............................................................................................................................................................. 78

10.2.3 Common Configuration Commands ...................................................................................................................... 79

11 Host High-Availability ............................................................................................................ 82

11.1 Overview ................................................................................................................................................................... 82

11.2 Version Compatibility ............................................................................................................................................... 82

11.3 Installation and Configuration .................................................................................................................................. 83

11.4 Cluster Maintenance ................................................................................................................................................. 83

11.4.1 Common Maintenance Commands ........................................................................................................................ 83

11.4.2 Cluster Log Analysis .............................................................................................................................................. 85

A Acronyms and Abbreviations .................................................................................................. 86


AIX Figures



vii

Figures

Figure 1-1 Comparison between JFS2 and JFS ..................................................................................................... 2

Figure 1-2 JFS2 size limits in 32-bit and 64-bit kernel AIX operating systems .................................................... 2

Figure 1-3 SMIT menu .......................................................................................................................................... 4

Figure 1-4 Interoperability query page .................................................................................................................. 7

Figure 2-1 Fibre Channel multi-path directly-connected network (dual-controller) ............................................. 9

Figure 2-2 Fibre Channel multi-path directly-connected network (four-controller).............................................. 9

Figure 2-3 Fibre Channel multi-path switch-connected network diagram (dual-controller) ............................... 10

Figure 2-4 Fibre Channel multi-path switch-connected network diagram (four-controller) ............................... 11

Figure 2-5 Fibre Channel multi-path switch-connected networking diagram (dual-controller) .......................... 12

Figure 2-6 Fibre Channel multi-path switch-connected networking diagram (four-controller) .......................... 13

Figure 3-1 Changing fsize in configuration file /etc/security/limits .................................................................. 15

Figure 5-1 Switch information ............................................................................................................................ 21

Figure 5-2 Switch port indicator status................................................................................................................ 22

Figure 5-3 Zone tab page .................................................................................................................................... 23

Figure 5-4 Zone configuration............................................................................................................................. 23

Figure 5-5 Zone Config tab page ......................................................................................................................... 24

Figure 5-6 Name Server page ............................................................................................................................ 24

Figure 5-7 Process for configuring an FCoE switch ........................................................................................... 28

Figure 6-1 Fibre Channel port details .................................................................................................................. 37

Figure 6-2 Fibre Channel port details .................................................................................................................. 38

Figure 7-1 Screen for selecting the installation source ........................................................................................ 41

Figure 7-2 Software installation screen ............................................................................................................... 41

Figure 7-3 Modifying IPv4 addresses ................................................................................................................. 42

Figure 7-4 Screen for configuring IP addresses ................................................................................................... 44

Figure 7-5 Change/Show Characteristics of an iSCSI Adapter screen........................................................... 45

Figure 9-1 Going to the host configuration page ................................................................................................. 63


AIX Figures



viii

Figure 9-2 Selecting an initiator of which information you want to modify ....................................................... 63

Figure 9-3 Modifying initiator information ......................................................................................................... 64

Figure 9-4 Querying the special mode type ......................................................................................................... 66

Figure 9-5 Enabling ALUA for T series V100R005/Dorado2100/Dorado5100/Dorado2100 G2 ....................... 68

Figure 9-6 Enabling ALUA for T Series V200R002/18000 Series/V3 Series ..................................................... 69

Figure 10-1 Screen for configuring volume groups............................................................................................. 73

Figure 10-2 Screen for configuring logical volume properties ............................................................................ 74

Figure 10-3 Screen for configuring file systems (logical volumes available) ..................................................... 75

Figure 10-4 Screen for configuring file systems (no logical volumes)................................................................ 76

Figure 11-1 Cluster process status ....................................................................................................................... 84

Figure 11-2 Cluster service status ........................................................................................................................ 85


AIX Tables



ix

Tables

Table 1-1 Commonly used directories in AIX ....................................................................................................... 3

Table 1-2 Common AIX commands ...................................................................................................................... 4

Table 2-1 Networking modes ................................................................................................................................. 8

Table 5-1 Switch model mapping ........................................................................................................................ 21

Table 5-2 Comparison of link aggregation modes ............................................................................................... 26

Table 9-1 Configuration methods and application scenarios of the typical working modes ................................ 58

Table 9-2 HUAWEI storage's support for ALUA ................................................................................................ 59

Table 9-3 Initiator parameter description ............................................................................................................. 60

Table 9-4 Multipathing configuration on non-HyperMetro Huawei storage interconnected with AIX ............... 64

Table 9-5 Multipathing configuration on HyperMetro Huawei storage interconnected with AIX ...................... 65

Table 10-1 VG limitations ................................................................................................................................... 72

Table 11-1 Compatibility between HACMP and the AIX operating system........................................................ 82

HUAWEI SAN Storage Host Connectivity Guide

for AIX 1 AIX Operating System



1

1 AIX Operating System 1.1 Introduction to AIX

AIX is a UNIX operating system developed by IBM. Complying with the Open Group UNIX

98 Base Brand, AIX supports the concurrent running of 32-bit and 64-bit applications and

flexible application expansion. AIX can run on IBM P series and IBM RS/6000 workstations,

servers, and large-scale parallel supercomputers.

AIX is IBM's proprietary UNIX operating system. The current versions of AIX include

AIX5.2, AIX5.3, AIX6.1, AIX7.1, and AIX7.2. Each basic AIX version has its patches

subsequently released. For details about AIX version releases, visit:

http://www-03.ibm.com/systems/cn/power/software/aix/index.shtml

AIX boasts virtual services, high operating efficiency, thorough cluster management, robust

reliability, and ensured security. Therefore, AIX is seldom used in desktop systems. Instead, it

is mainly used to run large-scale database systems such as Oracle, Sybase, and DB2.

1.2 File Systems in AIX

AIX supports the following file systems:

JFS

Journaled File System (JFS) uses journals to keep structure integrity.

JFS2

Enhanced Journaled File System (JFS2) is the enhanced JFS. JFS2 is larger than JFS and

has higher performance. JFS2 also stores much larger files than JFS.

NFS

Network File System (NFS) is a distributed file system that allows users to access files

and directories on remote PCs the same as on local PCs.

CDRFS

CD-ROM File System (CDRFS) allows access to CD-ROM contents from common file

system interfaces.

In traditional UNIX operating systems, files may be damaged after a system fault, particularly

the files that are constantly updated. When the contents of a file change, AIX records the

structure change of the file to a database log before updating the file contents.

../../../q00250221/Desktop//3.20/%20%20%20word/Eachhttp://www-03.ibm.com/systems/cn/power/software/aix/index.shtml





2

The log used for recording file structure (metadata) changes is called a JFS log. After an

accident such as a file system breakdown, AIX uses the JFS log to recover the file system.

JFS and JFS2 are the most widely applied file systems in common applications. The two file

systems are compared in Figure 1-1.

Figure 1-1 Comparison between JFS2 and JFS

For more information, visit:

http://publib.boulder.ibm.com/infocenter/pseries/v5r3/index.jsp?topic=/com.ibm.aix.baseadm

n/doc/baseadmndita/fs_jfs_jfs2.htm

Note that AIX6.1 and later support only 64-bit kernels. AIX5.1, 5.2, and 5.3 support both

32-bit and 64-bit kernels. The maximum size of a JFS2 file system and maximum size of a

JFS2 file vary with the AIX kernel. For details, see Figure 1-2.

Figure 1-2 JFS2 size limits in 32-bit and 64-bit kernel AIX operating systems

For more information, visit:

http://publib.boulder.ibm.com/infocenter/pseries/v5r3/index.jsp?topic=/com.ibm.aix.baseadmn/doc/baseadmndita/fs_jfs_jfs2.htmhttp://publib.boulder.ibm.com/infocenter/pseries/v5r3/index.jsp?topic=/com.ibm.aix.baseadmn/doc/baseadmndita/fs_jfs_jfs2.htm





3

http://publib.boulder.ibm.com/infocenter/pseries/v5r3/index.jsp?topic=/com.ibm.aix.baseadm

n/doc/baseadmndita/jfs2sizelim.htm

1.3 Directory Structure in AIX

AIX uses the same file and directory structures as other UNIX operating systems. The

structures are called file trees. In a file tree, directories are root nodes, which orderly organize

data and programs in groups. Files are leaf nodes owned by directories.

Table 1-1 describes the commonly used directories in AIX.

Table 1-1 Commonly used directories in AIX

Directory Description

/ Starts a UNIX file system file tree. This directory contains a key directory

and its files (for example, /sbin, /dev, and /etc) as well as files used in

system startup.

/etc Stores configuration files of the system and applications.

/dev Stores device files.

/home Root directory that stores all accounts except account root.

/u Link directory that navigates to /home.

/tmp Stores temporary files created by users or the system.

/usr Stores AIX operation commands, databases, and other applications.

/var Stores system operation logs.

/opt Used for installing common application systems.

/admin Used for AIX system management.

/sbin Stores commands and scripts that are important for file system /usr and

system startup.

/lost+found Stores files found by the fsck command.

1.4 Common Management Tools and Commands

1.4.1 Management Tool

AIX uses the System Management Interface Tools (SMIT) to manage system functions. The

SMIT provides users with a menu-based user interface to perform management tasks.

The SMIT is easy-to-use and provides most of AIX system management functions. Figure 1-3

shows the SMIT menu. The menu covers almost all AIX functions.

http://publib.boulder.ibm.com/infocenter/pseries/v5r3/index.jsp?topic=/com.ibm.aix.baseadmn/doc/baseadmndita/jfs2sizelim.htmhttp://publib.boulder.ibm.com/infocenter/pseries/v5r3/index.jsp?topic=/com.ibm.aix.baseadmn/doc/baseadmndita/jfs2sizelim.htm





4

Figure 1-3 SMIT menu

1.5 Management Commands

Table 1-2 lists the management commands used for connecting an AIX host to a Huawei

storage system.

Table 1-2 Common AIX commands

Command Function

bootinfo -s hdisk# Views the capacity of hdisk#.

cfgmgr -v Scans for physical hardware.

chdev -l fcs# -a

max_xfer_size=0x1000000

Changes the value of max_xfer_size in fcs#.

chfs Changes the directory size.

lsattr -EHl fcs# Views the properties of fcs#.

lsattr -EHl fscsi# Views the properties of fscsi#.

lsattr -El hdisk# Views the properties of hdisk#.

lsattr -Rl fcs# -a

max_xfer_size

Views the available values of max_xfer_size in fcs#.

lscfg -vpl fcs# Views information about the adapters of fcs#.

lscfg -vpl hdisk# Views the properties of hdisk#.





5

Command Function

lscfg | grep scsi Displays the existing or system-defined SCSI I/O controllers.

lsdev -Cc adapter Views the information about adapters identified by the host.

lsdev -Cc disk Displays information about disks identified by the host.

lslpp -l Views the software installed in the host.

lsvg -l vgname Displays the specified volume group's logical volumes, file

system type, logical partitions, physical partitions, and status.

lsvg -o Displays all activated volume groups.

mount Mounts a logical volume.

varyonvg vgname Activates a volume group.

varyoffvg vgname Deactivates a volume group.

The pound (#) in this table indicates a numerical digit that can be specified based on your actual

conditions.

1.6 Querying and Updating the Operating System Version

The version of the AIX operating system is a digit string in the format of

AAAA-BB-CC-DDEE, for example, 5300-08-06-0919.

AAAA: indicates the AIX release version.

BB: indicates a technical level (TL).

CC: indicates a service package (SP).

DDEE: indicates a release number, where DD indicates the last two digits of the release

year and EE indicates the release week.

For example, if AIX 6.1TL6 SP3 was released in the 48th week in 2010, its version is

6100-06-03-1048.

1.6.1 Querying the Current Version

Run the following command to query the current operating system version:

bash-3.00# oslevel -s

6100-05-01-1016

bash-3.00#

1.6.2 Querying Files That Must Be Updated Before a System Upgrade

Run the following command to query the files that must be updated before upgrading the

current system version to a specific target version:





6

bash-3.00# oslevel -rl 6100-06

Fileset Actual Level Recommended ML

-----------------------------------------------------------------------------

Java5.ext.java3d 5.0.0.1 5.0.0.175

printers.epsonLQ1600K_CN.rte 6.1.0.0 6.1.6.0

printers.escpj84_JP.rte 6.1.0.0 6.1.6.0

printers.hindi.rte 6.1.0.0 6.1.6.0

printers.hplj-2p_CN.rte 6.1.0.0 6.1.6.0

printers.ibm4332_HI.rte 6.1.0.0 6.1.6.0

printers.ibmgb18030_CN.rte 6.1.0.0 6.1.6.0

printers.ibmuniversal.rte 6.1.0.0 6.1.6.0

printers.starAR2463_CN.rte 6.1.0.0 6.1.6.0

bash-3.00#

This example command return shows the files that must be updated before upgrading the

system version to 6100-06.

1.6.3 Viewing the File Version

Run the following command to view the version of a specific file:

bash-3.00# lslpp -L UltraPath-3.01.015.AIX6.1.ppc_64.rte

Fileset Level State Type Description (Uninstaller)

----------------------------------------------------------------------------

UltraPath-3.01.015.AIX6.1.ppc_64.rte

3.1.15.1 C F ODM definitions for Array disk

devices

State codes:

A -- Applied.

B -- Broken.

C -- Committed.

E -- EFIX Locked.

O -- Obsolete. (partially migrated to newer version)

? -- Inconsistent State...Run lppchk -v.

Type codes:

F -- Installp Fileset

P -- Product

C -- Component

T -- Feature

R -- RPM Package

E -- Interim Fix

bash-3.00#

This command return shows the version of UltraPath-3.01.015.AIX6.1.ppc_64.rte.

1.7 Application Scenarios

AIX and storage systems generally work together in industries (for example, large banks,

telcos, and multinationals) that have high data security requirements. When interworking with

AIX, the storage system must ensure high availability, performance, and security of data in the operating system.





7

1.8 Interoperability Between AIX and Storage Systems

When connecting a storage system to an AIX host, consider the interoperability of

components (such as storage systems, AIX systems, HBAs, and switches) and upper-layer

applications 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.

Figure 1-4 Interoperability query page

Then, the OceanStor Interoperability Navigator is displayed.

CAUTION

When connecting to a storage system, an AIX host must use only IBM's HBAs (not HBAs

from other vendors).

----End


for AIX 2 Network Planning



8

2 Network Planning AIX hosts and storage systems support various networking modes.

Table 2-1 Networking modes

Classified By Networking Mode

Interface module type Fibre Channel network/iSCSI network

Whether switches are

used

Directly connected network (no switches are

used)/Switch-connected network (switches are used)

Whether multiple paths

exist

Single-path network/Multi-path network

Whether HyperMetro is

used

HyperMetro network, or non-HyperMetro network

Generally, the directly-connected network applies to small-scale storage systems (such as

those for university libraries and small hospitals); the switch-connected network applies to

large-scale storage systems (such as those for banks, financial institutions, and large-scale

enterprises), which need to manage a massive amount of service data.

The Fibre Channel network is the most widely used network for AIX operating systems. To

ensure service data security, both directly-connected network and the switch-connected

network are generally multi-path networkings.

This chapter mainly introduces the Fibre Channel multi-path directly-connected network and

the Fibre Channel multi-path switch-connected network.





9

2.1 Non-HyperMetro Network

2.1.1 Fibre Channel Networking Diagram

2.1.1.1 Multi-Path Directly Connected Network

Huawei provides dual-controller and multi-controller storage systems, and they support

different networkings. The following describes network diagrams of dual-controller and

multi-controller storage systems respectively.

2.1.1.1.1 Dual-Controller

The following explains how to connect an AIX host and a storage system (HUAWEI

OceanStor S5500T, for example) over a Fibre Channel multi-path directly-connected network,

as shown in Figure 2-1.

Figure 2-1 Fibre Channel multi-path directly-connected network (dual-controller)

In this networking, both controllers of the storage system are connected to the host's HBAs through

optical fibers.

2.1.1.1.2 Multi-Controller

The following explains how to connect an AIX host and a storage system (a four-controller

HUAWEI OceanStor 18800, for example) over a Fibre Channel multi-path direct connection

network, as shown in Figure 2-2.

Figure 2-2 Fibre Channel multi-path directly-connected network (four-controller)





10

In this networking, the four controllers of the storage system are connected to the host's HBAs through

optical fibers.

2.1.1.2 Multi-Path Switch-Connected Network





The following explains how to connect an AIX host and a storage system (HUAWEI

OceanStor S5500T, for example) over a Fibre Channel multi-path switch-connected network,

as shown in Figure 2-3.

Figure 2-3 Fibre Channel multi-path switch-connected network diagram (dual-controller)

In this networking example, the storage system is connected to the host through 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.



HUAWEI OceanStor 18800, for example) over a Fibre Channel multi-path switch-connected

network, as shown in Figure 2-4.





11

Figure 2-4 Fibre Channel multi-path switch-connected network diagram (four-controller)

In this networking example, the storage system is connected to the host through two switches. All

controllers of the storage system are connected to the switches through optical fibers and both switches


storage system, each zone contains only one storage port and its corresponding host port.

2.1.2 iSCSI Network Diagram

By the release of this document, no multipathing software is applicable to iSCSI networks.

Therefore, iSCSI networks can only be single-path networks (directly-connected or

switch-connected).

iSCSI single-path networkings are simple and therefore not detailed here.

2.2 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 contain only one initiator and one

target.

You are advised to use dual-switch networking to prevent single points of failure.





12

2.2.1 Fibre Channel Networking Diagram

2.2.1.1 Multi-Path Switch-Connected Network





The following explains how to connect an AIX host and a storage system (a dual-controller

HUAWEI OceanStor 6800 V3, for example) over a Fibre Channel multi-path

switch-connected network, as shown in Figure 2-5.

Figure 2-5 Fibre Channel multi-path switch-connected networking diagram (dual-controller)

In this networking example, the storage systems are connected to the host through two switches. Each

storage system' two controllers are connected to the switches through optical fibers and both switches


storage system, each zone contains only one storage port and its corresponding host port. The two

storage systems' controllers are interconnected through optical cables to form replication links.

Alternatively, you can also connect the two storage systems' controllers through a switch to form

replication links.



HUAWEI OceanStor 6800 V3, for example) over a Fibre Channel multi-path

switch-connected network, as shown in Figure 2-6.





13

Figure 2-6 Fibre Channel multi-path switch-connected networking diagram (four-controller)

In this networking, the storage systems are connected to the host through two switches. Each 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. The two storage

systems' controllers are interconnected through optical cables to form replication links. Alternatively,

you can also connect the controllers through two switches to form replication links.


for AIX 3 Preparations Before Configuration (on a Host)



14

3 Preparations Before Configuration (on a Host)

3.1 Adjusting the Directory Size

The default directory size is small upon the AIX installation. You need to manually adjust the

directory size based on site requirements. Otherwise, later operations may fail.

Capacities of directories such as /, /home, and /usr need to be expanded. Expand the

directories based on actual disk capacities. Usually, the directory size can be larger than 10

GB.

Perform the following steps to expand directory capacities:

Step 1 Display directory capacities.

bash-3.00# df -k

Filesystem 1024-blocks Free %Used Iused %Iused Mounted on

/dev/hd4 2097152 2071096 2% 2297 1% /

/dev/hd2 4194304 2789996 34% 36955 6% /usr

/dev/hd9var 2097152 2035544 3% 681 1% /var

/dev/hd3 4194304 4174628 1% 70 1% /tmp

/dev/fwdump 131072 130724 1% 4 1% /var/adm/ras/platform

/dev/hd1 4194304 2881680 32% 841 1% /home

/proc - - - - - /proc

/dev/hd10opt 262144 940 100% 2729 76% /opt

/dev/lv00 131072 121988 7% 21 1% /audit

bash-3.00#

Step 2 Expand capacities of desired directories.

The command used for expanding directory capacities in AIX is chfs -a size=capacity

directory.

bash-3.00# chfs -a size=5G /tmp

Filesystem size changed to 10485760

bash-3.00#

The example command expands the capacity of /tmp is to 5 GB.

Step 3 Verify the capacity expansion.

View the directory capacity again to check that its capacity is expanded successfully.





15

bash-3.00# df -k

Filesystem 1024-blocks Free %Used Iused %Iused Mounted on

/dev/hd4 2097152 2071096 2% 2297 1% /

/dev/hd2 4194304 2789996 34% 36955 6% /usr

/dev/hd9var 2097152 2035544 3% 681 1% /var

/dev/hd3 5242880 5223044 1% 70 1% /tmp

/dev/fwdump 131072 130724 1% 4 1% /var/adm/ras/platform

/dev/hd1 4194304 2881680 32% 841 1% /home

/proc - - - - - /proc

/dev/hd10opt 262144 940 100% 2729 76% /opt

/dev/lv00 131072 121988 7% 21 1% /audit

bash-3.00#

----End

3.2 Changing the File Size Limit

By default, the maximum file size is 2 GB after AIX is installed. Files larger than 2 GB

cannot be created under any directory. However, files larger than 2 GB are common. To

ensure normal file creation, you need to change the file size limit.

To change the file size limit, change fsize in file size limit configuration file

/etc/security/limits to -1, where 1 indicates no limits on file size, as shown in Figure 3-1. The

change takes effect immediately without the need to restart the system.

Figure 3-1 Changing fsize in configuration file /etc/security/limits

After fsize is changed, run the following command to verify that the change takes effect:

bash-3.00# ulimit -a

core file size (blocks, -c) 1048575

data seg size (kbytes, -d) 131072

file size (blocks, -f) unlimited

max memory size (kbytes, -m) 32768

open files (-n) 2000

pipe size (512 bytes, -p) 64

stack size (kbytes, -s) 32768

cpu time (seconds, -t) unlimited

max user processes (-u) 262144

virtual memory (kbytes, -v) unlimited

bash-3.00#

In the output, file size is changed to unlimited, indicating that the change takes effect.





16

3.3 Viewing and Configuring HBAs

Ensure that HBAs installed on a host are correctly identified. Then configure HBA parameters

based on site requirements.

3.3.1 HBA Identification

After an HBA is installed on a host, run the following command on the host to check whether

the HBA is identified by the host.

bash-3.00# lsdev -Cc adapter |grep fc

fcs0 Available 06-00 4Gb FC PCI Express Adapter (df1000fe)

fcs1 Available 06-01 4Gb FC PCI Express Adapter (df1000fe)

fcs2 Available 05-00 8Gb PCI Express Dual Port FC Adapter (df1000f114108a03)

fcs3 Available 05-01 8Gb PCI Express Dual Port FC Adapter (df1000f114108a03)

bash-3.00#

The output shows that two 4 Gbit/s Fibre Channel host ports and two 8 Gbit/s Fibre Channel

host ports are identified. The output is consistent with the ports on the two newly installed

HBAs, one dual-port 4 Gbit/s HBA and one dual-port 8 Gbit/s HBA. This output means that

the host has identified the HBAs correctly.

The output also shows the physical device identifier for each HBA port, for example, fcs0.

The identifiers will be used in follow-up query commands.

3.3.2 HBA WWNs

After the host identifies a newly installed HBA, you can view properties of the HBA on the

host. The following describes how to view the HBA properties.

Run the following command to view the world wide name (WWN) of the HBA.

bash-3.00# lscfg -vpl fcs2

fcs2 U78A0.001.DNWGHBR-P1-C2-T1 8Gb PCI Express Dual Port FC Adapter

(df1000f114108a03)

Part Number.................10N9824

Serial Number...............1B0080484B

Manufacturer................001B

EC Level....................D76482B

Customer Card ID Number.....577D

FRU Number..................10N9824

Device Specific.(ZM)........3

Network Address.............10000000C99B5D94

ROS Level and ID............02781135

Device Specific.(Z0)........31004549




Device Specific.(Z4)........FF781110



Device Specific.(Z7)........0B7C1135

Device Specific.(Z8)........20000000C99B5D94

Device Specific.(Z9)........US1.10X5

Device Specific.(ZA)........U2D1.10X5





17

Device Specific.(ZB)........U3K1.10X5

Device Specific.(ZC)........000000EF

Hardware Location Code......U78A0.001.DNWGHBR-P1-C2-T1

PLATFORM SPECIFIC

Name: fibre-channel

Model: 10N9824

Node: fibre-channel@0

Device Type: fcp

Physical Location: U78A0.001.DNWGHBR-P1-C2-T1

The output shows the HBA specifications (Part Number and Customer Card ID Number)

and WWN (Network Address).

3.3.3 HBA Physical Device Identifier Properties

AIX assigns a unique physical device identifier (fcs#) and a virtual device identifier (fscsi#)

to each HBA port. The properties of the two identifiers are used in the interaction among

storage systems, AIX, and upper-layer applications. Therefore, configure these properties

correctly based on site requirements.

Run the following command to view the properties of an HBA's physical device identifier:

bash-3.00# lsattr -EHl fcs0

attribute value description user_settable

bus_intr_lvl Bus interrupt level False

bus_io_addr 0xff800 Bus I/O address False

bus_mem_addr 0xffe7e000 Bus memory address False

init_link al INIT Link flags True

intr_msi_1 581 Bus interrupt level False

intr_priority 3 Interrupt priority False

lg_term_dma 0x800000 Long term DMA True

max_xfer_size 0x100000 Maximum Transfer Size True

num_cmd_elems 200 Maximum number of COMMANDS to queue to the adapter True

pref_alpa 0x1 Preferred AL_PA True

sw_fc_class 2 FC Class for Fabric True

bash-3.00#

Among the preceding properties, note the following parameters:

init_link

Indicates the Fibre Channel HBA port mode. Possible values are auto, al, and pt2pt,

indicating three connection modes. Connection modes vary with HBAs. For example,

some HBAs support only al and pt2pt and some support only auto.

lg_term_dma

Indicates the size of the memory where fcs# stores I/O commands and data. By default,

the value is 0x800000, namely, 8 MB. This parameter is related to read/write

performance.

max_xfer_size

Indicates the maximum I/O transfer length of fcs#. By default, the value is 0x100000,

namely, 1 MB. This property is related to read/write performance.

num_cmd_elems





18

Indicates the size of concurrent I/Os of fcs#. By default, the value is 200. This parameter

is related to read/write performance.

The preceding parameters need to be adjusted only when the connection failed between the

host and storage systems or the read/write performance is poor.

3.3.4 HBA Virtual Device Identifier Properties

Run the following command to view the properties of an HBA's virtual device identifier:

bash-3.00# lsattr -EHl fscsi0

attribute value description user_settable

attach none How this adapter is CONNECTED False

dyntrk no Dynamic Tracking of FC Devices True

fc_err_recov delayed_fail FC Fabric Event Error RECOVERY Policy True

scsi_id Adapter SCSI ID False

sw_fc_class 3 FC Class for Fabric True

bash-3.00#

Among the preceding properties, note the following parameters:

dyntrk

Indicates the status of the dynamic tracking function. By default, the value is no. When

dynamic tracking is enabled, HBA service status is monitored in a timely manner.

fc_err_recov

Indicates the status of the fast error recovery function. By default, the value is

delayed_fail. This parameter determines the time an HBA spent in fault diagnosis.

These parameters are related to service path selection. Configure these parameters based on

site requirements when multiple paths exist. For details about how to configure the parameters,

see the user guides specific to multipathing.

3.3.5 HBA Parameters

Before changing a parameter value, run the following command to view available values of

the parameter:

bash-3.00# lsattr -Rl fcs0 -a max_xfer_size

0x100000

0x200000

0x400000

0x800000

0x1000000

bash-3.00#

The output shows the five possible values of max_xfer_size of fcs0.

Run the following command to change the value of max_xfer_size of fcs0:

bash-3.00# chdev -l fcs0 -a max_xfer_size=0x1000000

After changing the parameter value, run the lsattr -EHl fcs0 command to verify that the

change is successful.


for AIX 4 Preparations Before Configuration (on a Storage System)



19

4 Preparations Before Configuration (on a Storage System)

Make sure that RAID, LUNs, and hosts are created correctly on the storage system. These

configurations are common and therefore not detailed here.


for AIX 5 Switch Configuration



20

5 Switch Configuration A Fibre Channel multi-path network is recommended for AIX. This chapter details the Fibre

Channel switches used in this network.

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.





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 Switch model mapping

Switch Type B-Series Switch Model Switch Type B-Series Switch Model

12 3900 61 4424

16 3200 62 Brocade DCX

21 24000 64 5300

26 3850 66 5100

27 3250 67 Brocade Encryption Switch

29 4012 69 5410

34 200E 71 300

37 4020 72 5480

43 4024 75 M5424

44 4900 76 8000





22

Switch Type B-Series Switch Model Switch Type B-Series Switch Model

45 4016 77 Brocade DCX-4S

51 4018 83 7800

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:

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 1 Check the switch port status.

Normally, the switch port indicators are steady green, as shown in 0.

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 2 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 3 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.





23

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 4 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 0.

Figure 5-4 Zone configuration

Step 5 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.





24

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 Zone Config tab page

Step 6 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 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 (*).





25

----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 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

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.

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.

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=com.vignette.cachetoken&sp4ts.oid=3984629&javax.portlet.endCacheTok=com.vignette.cachetoken&javax.portlet.tpst=efb5c0793523e51970c8fa22b053ce01&hpappid=sp4ts&cc=US&ac.admitted=1337927146324.876444892.199480143https://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=com.vignette.cachetoken&sp4ts.oid=3984629&javax.portlet.endCacheTok=com.vignette.cachetoken&javax.portlet.tpst=efb5c0793523e51970c8fa22b053ce01&hpappid=sp4ts&cc=US&ac.admitted=1337927146324.876444892.199480143https://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=com.vignette.cachetoken&sp4ts.oid=3984629&javax.portlet.endCacheTok=com.vignette.cachetoken&javax.portlet.tpst=efb5c0793523e51970c8fa22b053ce01&hpappid=sp4ts&cc=US&ac.admitted=1337927146324.876444892.199480143https://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=com.vignette.cachetoken&sp4ts.oid=3984629&javax.portlet.endCacheTok=com.vignette.cachetoken&javax.portlet.tpst=efb5c0793523e51970c8fa22b053ce01&hpappid=sp4ts&cc=US&ac.admitted=1337927146324.876444892.199480143https://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=com.vignette.cachetoken&sp4ts.oid=3984629&javax.portlet.endCacheTok=com.vignette.cachetoken&javax.portlet.tpst=efb5c0793523e51970c8fa22b053ce01&hpappid=sp4ts&cc=US&ac.admitted=1337927146324.876444892.199480143https://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=com.vignette.cachetoken&sp4ts.oid=3984629&javax.portlet.endCacheTok=com.vignette.cachetoken&javax.portlet.tpst=efb5c0793523e51970c8fa22b053ce01&hpappid=sp4ts&cc=US&ac.admitted=1337927146324.876444892.199480143





26

[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 (Link Aggregation)

When storage devices and application servers 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.

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.

Figure 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 Procedure

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.





27

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:

system-view

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.

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.





28

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

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





29

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

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





30

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

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





31

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