HCNA-Storage Building the Structureof Storage Network Lab Guide V2.1

Huawei Certified

HCNA-Storage BSSN Building the Structure of Storage Network （Lab Guide）

Huawei Technologies Co.,Ltd

m

N

Copyright © Huawei Technologies Co., Ltd. 2014. 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 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 the warranty of any kind, express or implied.

Huawei Certified HCNA-BSSN Building the Structure of Storage Network Lab Guide Version 2.1

m

O

Huawei Certification System Relaying on its strong technical and professional training system, according to different customers at different levels of ICT technology, Huawei certification is committed to provide customs customs with authentic, professional certification. certification.

Based on characteristics characteristics of

ICT technologies and customers ’needs at different levels, Huawei certification provides customers with certification system of four levels. HCNA-Storage BSSN (Huawei Certified Network Associate –Storage Building the Structure of Storage Network) training aims to provide guidance to participants in learning contents related to the HCNA-Storage exam.The training covers the knowledge, technologies and application of SAN,NAS, and structure ,network, connection, deploying ,troubleshooting in Huawei SAN Storage system. HCNP-Storage certification is positioned in ability construction for IT information storage professional engineer or storage scheme expert. The curriculum includes, but is not limited to the following: SAN, NAS, Backup and DS technology, Unified storage system principle and application, Huawei storage solution planning, deployment, troubleshooting and maintenance. HCIE-Storage (Huawei Certified Internetwork Expert-Storage) is designed to endue engineers with a variety of Storage network and system technology and proficiency in maintenance, diagnostics and troubleshooting of Huawei solution, which equips the engineers with competence in planning, design and optimization of large-scale ICT Solution.

m

P

  



Foreword Outline HCNA-Storage covers the storage technologies (RAID, SCSI, iSCSI, FC) and its application, focusing on the IP-SAN, FC-SAN architecture, networking, connectivity, deployment and maintenance.

Content The course contains a total of 10 modules ： Module1 Describes the IT infrastructure and data center ， Storage application environment, Structures and working principles of HDD and SSD, Host application environment. Module2 Describes the RAID levels and principles, RAID 2.0+ Technology. Module3 Describes the components of a storage array,

universal storage array

technologies, application of Huawei storage arrays. Module4 Describes the DAS basics,

SCSI protocol,

SAN basics,

Fibre Channel

connection and protocol, application of Huawei SAN storage. Module5 Describes the background of IP SANs, the components and networking of an IP SAN, iSCSI protocol, convergence of Fibre Channel and TCP/IP,

Huawei IP SAN

storage applications. Module6 Describes the functions and installation of the ISM, Initial configuration of storage devices, basic settings on storage devices, basic settings on hosts. Module7 Describes the NAS structure and implementation, NAS file sharing protocols, NFS and CIFS, I/Os and performance of a NAS system,

differences and relationship

between SAN and NAS, Huawei NAS products. Module8 Describes the basic concepts of big data, object-based storage technologies, key technologies of big data, Huawei's big data solution and technologies. Module9 Describes the backup concept and topologies, backup technologies, backup policies, Huawei backup solutions and application, Disaster Recovery. Module10 Describes the concept and background of cloud computing, deployment and business models of cloud computing, core technologies and value of cloud computing, Huawei cloud computing solutions. In conclusion, you should be able to plan and deploy SAN networks and storage systems, to install, deploy, and maintain Huawei

SAN storage products, and to

become a qualified SAN storage engineer or system administrator.

m

R

Readers’ Knowledge Background Know server fundamental and application. Know SAN, NAS, DR concepts and technology. Understand mainstream OS and DB operation and management.

m

S

Icons Used in This Book

FC Switch

GE Switch

Storage Array

Host

m

T

Account for Experiment environment Experiment network introduce The experiment environment aims to provide guidance to participants in learning contents related to the HCNA-Storage exam( H13-611-ENG). Experiment contents include storage array hardware installation, network deploying of FC SAN and IP SAN, storage management, configuration RAID/LUN/ mapping ,connection between storage and hosts 、storage maintenance etc. One suit of experiment equipment includes : 1 PCS GE switch,1 PCS FC switch,1 PCS Windows host（with OS and NIC or HBA card ）,1PCS Linux host（with OS and NIC or HBA card）,1－2 PCS S2600T or S5000T storage array, several network cables ,2 －4 PCS PC for students. One suit of experiment equipment fits 2-4 students operating at the same time.

Equipment introduce Device type Storage array

Device name S2600T or S5500T

Switch Server

SNS2124 OR S3900 Windows 2008 SP2 SuSE 11 SP2 Network cable 8PCS FC 6 PCS PC

cable Console PC

m

U

Software version S2600T V100R005 S5500T V100R005 General version Be compatible with storage Null Win7

BSSN-HCNA-Storage Experiment Guide (For trainees)ISSUE 2.00

Contents

Contents 1 About This Document ................................................................................................................ 13 1.1 Scope of Application................................................................... ............................................................... ................. 13 1.2 Safety Precautions ...................................................................................................................................................... 13 1.3 Devices Used in Labs ................................................................................................................................................. 14

2 Server RAID Configurations .................................................................................................... 18 2.1 Objectives ................................................................................................................................................................... 18 2.2 Devices ....................................................................................................................................................................... 18 2.3 Networking Diagram .................................................................................................................................................. 18 2.4 Procedure ................................................ .................................................................... ................................................ 19 2.4.1 Starting the CU Tool ................................................................ ............................................................... ................. 19 2.4.2 Configuring RAID 0 ................................................................................................. ............................................... 19

3 Server Management Using iMana ........................................................................................... 22 3.1 Objectives ................................................................................................................................................................... 22 3.2 Devices ....................................................................................................................................................................... 22 3.3 Networking Diagram .................................................................................................................................................. 22 3.4 Procedure ................................................ .................................................................... ................................................ 22 3.4.1 Logging In to the Web Page ..................................................... ................................................................ ................ 22 3.4.2 Viewing System Information .............................................................................................. ..................................... 23 3.4.3 System Hardware .......................................................... ................................................................ ........................... 25 3.4.4 Remote Control ............................................................. ................................................................ ........................... 26 3.4.5 General Configuration Items.................................................................................................................................... 32

4 Storage Array Components and Installation Lab ................................................................. 37 4.1 Objectives ................................................................................................................................................................... 37 4.2 Devices ....................................................................................................................................................................... 37 4.3 Labal Environment ..................................................................................................................................................... 37 4.4 Procedure ................................................ .................................................................... ................................................ 38 4.4.1 Knowing the Hardware Components and Port Functions of the S2600T or S5500T ................................. ............. 38 4.4.2 Installation Procedure .............................................................................................................................................. 38 4.4.3 Powering On or Off a SAN Storage Device ....................................................................... ..................................... 39 4.5 Questions .................................................................................................................................................................... 40

5 SAN Networking Lab ................................................................................................................. 41 Issue 01 (2014-01-16)

Huawei confidential. No spreading without permission..

i 




Contents

5.1 Fibre Channel SAN Networking Lab of the S2600T or S5500T ...................................................... .......................... 41 5.1.1 Objectives ................................................................................................................................................................ 41 5.1.2 Devices .................................................................................................................................................................... 41 5.1.3 Networking Diagram ............................................................................................................................................... 41 5.1.4 Procedure ............................................. .................................................................... ................................................ 42 5.2 IP SAN Networking Lab of the S2600T or S5500T ................................................... ................................................ 48 5.2.1 Objectives ................................................................................................................................................................ 48 5.2.2 Devices .................................................................................................................................................................... 48 5.2.3 Networking Diagram ............................................................................................................................................... 48 5.2.4 Procedure ............................................. .................................................................... ................................................ 49 5.3 Fibre Channel SAN Networking Lab of the S2600T or S5500T ...................................................... .......................... 51 5.3.1 Objectives ................................................................................................................................................................ 51 5.3.2 Devices .................................................................................................................................................................... 51 5.3.3 Networking Diagram ............................................................................................................................................... 51 5.3.4 Procedure ............................................. .................................................................... ................................................ 52 5.4 IP SAN Networking Lab of the S2600T or S5500T ................................................... ................................................ 55 5.4.1 Objectives ................................................................................................................................................................ 55 5.4.2 Devices .................................................................................................................................................................... 55 5.4.3 Networking Diagram ............................................................................................................................................... 56 5.4.4 Procedure ............................................. .................................................................... ................................................ 56

6 Know DeviceManager and SAN Storage Management Lab .............................................. 59 6.1 Objectives ................................................................................................................................................................... 59 6.2 Devices ....................................................................................................................................................................... 59 6.3 Networking Diagram .................................................................................................................................................. 59 6.4 Procedure ................................................ .................................................................... ................................................ 60 6.4.1 Logging In to t he DeviceManager ..................................................... ............................................................. ......... 60 6.4.2 Configuring Basic Information About a Storage System ............................................................... .......................... 61 6.4.3 Setting Storage Device Time ................................................................................................................................... 63

7 Managing Devices....................................................................................................................... 66 7.1 Objectives ................................................................................................................................................................... 66 7.2 Devices ....................................................................................................................................................................... 66 7.3 Networking Diagram .................................................................................................................................................. 66 7.4 Procedure ................................................ .................................................................... ................................................ 66 7.4.1 Monitoring Controller Enclosure ..................................................................................................................... ........ 66 7.4.2 Monitoring Disk Enclosures .................................................................................................................................... 73 7.4.3 Powering On and Off an Interface Module .............................................................. ................................................ 75 7.4.4 Powering Off a Device ............................................................................................................................................ 77

8 Basic Function Configuration Lab of SAN Storage Products............................................. 78 8.1 Objectives ................................................................................................................................................................... 78 8.2 Devices ....................................................................................................................................................................... 78 8.3 Networking Diagram .................................................................................................................................................. 78

Issue 01 (2014-01-16)    

 


ii


Contents

8.4 Procedure ................................................ ..................................................................... ............................................... 79 8.4.1 Configuring Management Port on S2600T or S5500T ..................................................................................... ....... 79 8.4.2 Creating a Disk Domain .......................................................................................................................................... 82 8.4.3 Creating a Storage Pool ........................................................................................................................................... 85 8.4.4 Creating a LUN............................................................ ................................................................ ............................ 88 8.4.5 Creating a LUN Group ............................................................................................................................................ 91

9 Connecting SAN Storage Devices to Windows-based Hosts ............................................. 94 9.1 Objectives ................................................................................................................................................................... 94 9.2 Devices ....................................................................................................................................................................... 94 9.3 Networking Diagram .................................................................................................................................................. 94 9.4 IP Address Planning .............................................. ................................................................. ..................................... 95 9.5 Procedure ................................................ .................................................................... ................................................ 96 9.5.1 Building a Fibre Channel SAN in the Windows Environment ........................................... ..................................... 96 9.5.2 Building an IP SAN in the Windows Environment ............................................................. ................................... 126 9.6 Questions .................................................................................................................................................................. 149

10 Connecting SAN Storage Devices to Linux-based Hosts ................................................ 150 10.1 Objectives ............................................................................................................................................................... 150 10.2 Devices ................................................................................................................................................................... 150 10.3 Networking Diagram .............................................................................................................................................. 150 10.4 IP Address Planning ....................................................... ............................................................... .......................... 151 10.5 Procedure ................................................. ................................................................. .............................................. 152 10.5.1 Building a Fibre Channel SAN in the SUSE Linux Environment ....................................................................... 152 10.5.2 Building an IP SAN in the SUSE Linux Environment .......................................... .............................................. 176 10.6 Questions ................................................................................................................................................................ 210

11 Routine Maintenance Lab of SAN Storage Products ....................................................... 211 11.1 Objectives ............................................................................................................................................................... 211 11.2 Devices ................................................................................................................................................................... 211 11.3 Networking Diagram .............................................................................................................................................. 211 11.4 Procedure ............................................................ ................................................................ .................................... 212 11.4.1 Exporting Configuration Data of the Stor age Device Using the DeviceManager...................... .......................... 212 11.4.2 Using the Maintenance Tool ............................................................ ............................................................. ....... 213 11.4.3 Inspection (including reviewal inspection) ......................................................................................... ................. 214 11.4.4 Collecting Information ...................................................................... ............................................................ ....... 219

12 Parts Replacement Lab of SAN Storage Products ............................................................ 221 12.1 Objectives ............................................................................................................................................................... 221 12.2 Devices ................................................................................................................................................................... 221 12.3 Networking Diagram .............................................................................................................................................. 221 12.4 Procedure ................................................. ................................................................. .............................................. 221 12.4.1 Removing a Controller......................................................................................................................................... 221 12.4.2 Installing a Controller .......................................................................................................................................... 223

Issue 01 (2014-01-16)


iii    

 


Contents

12.4.3 Replacing a Dis k ......................................................... ............................................................... .......................... 224 12.4.4 Replacing a Power Module .............................................................. ............................................................. ....... 227 12.4.5 Replacing a Fan-BBU Module.................................................................... ......................................................... 229 12.5 Questions ................................................................................................................................................................ 231

13 Upgrade Lab of SAN Storage Products............................................................................... 232 13.1 Objectives ............................................................................................................................................................... 232 13.2 Devices ................................................................................................................................................................... 232 13.3 Networking Diagram .............................................................................................................................................. 232 13.4 Procedure ................................................. ................................................................. .............................................. 232 13.4.1 Obtaining the Latest Version of Software ............................................................................................................ 232 13.4.2 Preparing to Upgrade a Controller .............................................................. ......................................................... 233 13.4.3 Backing Up Data......................................................... ............................................................... .......................... 233 13.4.4 Stopping Host Services .......................................................... .............................................................. ................ 234 13.4.5 Upgrading a Controller Using Toolkit .............................................................................. ................................... 234 13.4.6 Upgrading the UltraPath ......................................................................................... ............................................. 240 13.5 Questions ................................................................................................................................................................ 240

Issue 01 (2014-01-16) m~

=

NO


iv


1 About This Document

1

About This Document

This document is designed for use in instructing trainees to configure and deploy Huawei storage products. The information provided will help trainees in completing the lab sections of the training program.

1.1 Scope of Application This document describes the labs involved in the H CNA-Storage training. Equipment required: Storage device: T series V200R002 Rack server: RH2285 V2 Fibre Channel switch: SNS2124 V100R002 IP switch: GE switch

1.2 Safety Precautions 

Alarm and safety symbols When operating devices, observe the precautions provided by warning and safety symbols to prevent personal injury and device damage.



Electrostatic discharge (ESD) When installing and maintaining devices, observe the ESD safety precautions to prevent personal injury and device damage.



Using lasers safely When installing and maintaining devices, observe the laser safety precautions to prevent personal injury and device damage.



Using optical fibers safely Use optical fibers in a safe and correct manner to ensure the normal operation of devices and to prevent personal injury and device damage.



Short circuit protection When installing and maintaining devices, use and place tools in compliance with the regulations to prevent short circuits.



Operating devices safely When installing and maintaining devices, observe the electrical safety precautions to prevent personal injury and device damage.



Issue 01 (2014-01-16)

Condensation prevention


13 m~

=

NP



Before installing devices, ensure that no condensation is formed on the devices to prevent power-on failures.

1.3 Devices Used in Labs S2600T Front panel

3.5-inch disk enclosure



12 x 3.5-inch disks



Support for mainstream SAS disks, SATA disks, and SSDs



The first four disks serve as coffer disks in 2 x (1+1) redundancy mode



Support for powering on and off each disk independently

Rear panel

Controller module for controller and disk integration

1

Management network port

4

Mini SAS expansion port

2

Maintenance network port

5

8 Gbit/s Fibre Channel host port

3

Serial port

6

1 Gbit/s iSCSI host port

S5500T Front panel

Issue 01 (2014-01-16) m  

N Q


14



2.5-inch disks 

24 x 2.5-inch disks



Support for mainstream SAS disks, SATA disks, and SSDs



The first four disks serve as coffer disks in 2 x (1+1) redundancy mode



Support for powering on and off each disk independently

Rear panel

1


4


2


5


3

Serial port

6


RH2285 V2 Front panel



2 x Intel® Xeon E5-2400 CPUs



12 x RDIMM/LRDIMM memory slots

Issue 01 (2014-01-16)


15 m~

=

NR

BSSN-HCNA-Storage Experiment Guide (For trainees)ISSUE 2.00 


12 x 3.5-inch + 2 x 2.5-inch, 8 x 2.5-inch, or 26 x 2.5-inch SAS or SATA disks, RAID 0, 1, 5, 10, 50, 6, and 60 available

Rear panel

SNS2124 Fibre Channel switch 

8 to 24 Fibre Channel ports per set



Support for a rate of 1, 2, 4, and 8 Gbit/s



8-port expansion increments

1

Management serial port

3

Fibre Channel port

2


4

Power supply

Cables Ground cable Connects to the ground to prevent ESD. Serial cable Connects to a serial port on a storage array so that the array can be managed using the command-line interface (CLI).

Issue 01 (2014-01-16) m~

=

NS


16



Mini SAS cable SAS expansion cable

Network cable Connects to an iSCSI port or a management network port.

Optical fiber (multi-mode) Fibre Channel expansion cable Connects to a Fibre Channel host port. AC power cable

DC power cable

Issue 01 (2014-01-16)


17 m~

=

NT


2

2 Server RAID Configurations

Server RAID Configurations

2.1 Objectives Upon completing this lab, you will know how to configure RAID on a server.

2.2 Devices RH2285 (1), monitor (1), mouse (1), keyboard (1)

2.3 Networking Diagram Connect the monitor, mouse, and keyboard directly to the server.

Issue 01 (2014-01-16) m~

=

NU


18



2.4 Procedure 2.4.1 Starting the CU Tool When Press Ctrl-C to Start LSI Corp Configuration Utility... is displayed during the system startup, press Ctrl+C to start the CU tool. Then Please wait, invoking SAS Configuration Utility... is displayed. After the system is powered on and the self-checking is complete, the CU management window is displayed.

2.4.2 Configuring RAID 0 To configure redundant array of independent disks (RAID) 0 properties on the CU management screen, perform the following steps: 1.

Select an SAS controller.

2.

Press Enter . The Controller Properties screen is displayed.

Issue 01 (2014-01-16)


19 m~

=

NV



3.

Select RAID Properties, and press Enter . The Select New Volume Type screen is displayed.

4.

Choose Create RAID 0 Volume. The Create New Volume screen lists available hard disks.

CAUTION: The data on the selected hard disks will be lost. 5.

Press the -, +, or space key to identify a hard disk to be configured or not for the current RAID properties.

Issue 01 (2014-01-16) m~

=

OM


20



NOTE: If a hard disk is identified as No, the hard disk is not configured with the current RAID properties. If a hard disk is identified as Yes, the hard disk is configured with the current RAID properties. 6.

Press C, and select Save changes then exit this menu .

Issue 01 (2014-01-16)


21 m~

=

ON


3

3 Server Management Using iMana

Server Management Using iMana

3.1 Objectives Upon completing this lab, you will have a working knowledge of the configuration and management of servers using iMana.

3.2 Devices RH2285 V2 (1), maintenance terminal (1)

3.3 Networking Diagram

3.4 Procedure 3.4.1 Logging In to the Web Page Step 1 Ensure that the maintenance terminal communicates with the iMana management network port correctly.

Issue 01 (2014-01-16) m~

=

OO


22



Step 2 Open Internet Explorer and enter the IP address of the iMana management network port in the browser address box. Ensure that the IP address of the maintenance terminal resides in the same segment as that of the management network port.

Step 3 In the Security Alert dialog box that is displayed, clickYes. Step 4 On the login page that is displayed, as shown in Figure 3-1: a. b.

Select a language. Enter your user name and password. The default user name is root and password isHuawei12#$ for the iMana Web.

c.

Select This iMana.

d.

Click Log In to go to the iMana 200 graphical user interface (GUI) or clickReset to reset the parameters.

Figure 3-1 Logging in to the iMana 200

----End

3.4.2 Viewing System Information Step 1 In the navigation tree, choose System Information >Firmware Version. The Firmware Version page is displayed.

This page shows the firmware information about the mainboard and other existing components.

Issue 01 (2014-01-16)


23 m~

=

OP



Step 2 In the navigation tree, choose System Information >Asset Information. The Asset Information page is displayed. This page has two subnodes:Mainboard andPS.

Issue 01 (2014-01-16) m~

=

OQ


24



----End

3.4.3 System Hardware In the navigation tree, choose System Information >System Hardware. The System Hardware page is displayed. You can obtain information about the existing CPUs, memory, disks, power supplies, fans, disk backplane, RAID card, network interface card (NIC), and integrated RAID.

Issue 01 (2014-01-16)


25 m~

=

OR



3.4.4 Remote Control Setting the Resolution of a Controlled Device Step 1 Right-click on the real-time desktop of a controlled device and choose Properties (R) from the shortcut menu. The Display Properties dialog box is displayed.

Step 2 Click the Settings tab and drag the Screen resolution slider to change the resolution. Step 3 Click OK . The remote control window will be displayed in the new resolution. Full screen display On the toolbar, click a full screen.

. The real-time desktop of the controlled device will be displayed in

Press Ctrl+Shift+Alt. The full-screen mode toolbar is displayed.

Issue 01 (2014-01-16) m~

=

OS


26



----End

Controlling the Power-On and Power-Off of a Remote Device On the toolbar, click to select a power control mode. Power control modes include power-on, power-off, restart, safe restart, and USB reset. Description Power-on: powers on the device. Power-off: powers off the device. Restart: cold resets the devices. Safe restart: soft resets the device. This process includes logout. USB reset: resets the USB keyboard and mouse.

Connecting to the Virtual Drive Step 1 On the toolbar, click

. The Virtual Drive area is displayed.

Step 2 Select Drive or Image file. If Drive is selected, the drop-down list shows a drive to be virtualized from the client to the server. If Image file is selected, click Browse and select a disc image file to be virtualized from the client to the server.

Step 3 Click Connect. After the connection is set up, the button name changes to Disconnect. ----End

Issue 01 (2014-01-16)


27 m  

O T



Changing an Image File Step 1 In the area, click Eject. The button is renamed to Insert. Step 2 Click Browse and reselect a disc image file. Step 3 Click Insert. After the image file has been changed, the button is renamed to Eject. ----End

Generating an Image File Step 1 On the toolbar, click

. The Virtual Drive area is displayed.

Step 2 In the Select Drive drop-down list, select a CD-ROM drive or floppy drive. Step 3 Click Browse and select a location to save the image file.

Before generating an image file, ensure that the virtual CD-ROM drive or floppy drive is disconnected and the CD-ROM drive or floppy drive on the client is not being invoked by other applications.

Step 4 Click Generate . The button name changes to Stop and the client starts to generate an image file. You can click Stop to stop the image file generation process. Meanwhile, the Generation progress bar shows the progress until the image file is generated. ----End

Power Supply Control

Only users in the Administrators orOperators group are allowed to control power supplies. In the navigation tree, choose PS Management >Power Control. The Power Control page is displayed. Select a power-on/off control mode. Click OK . After the mode is selected, a dialog box will be displayed indicating that the operation succeeded.

Before a power-off, restart, or safe restart, make sure that the operation has no risks on services.

Issue 01 (2014-01-16) m~

=

OU


28



The power-on/off control modes include power-on, power-off, restart, safe restart, and non-maskable interrupt (NMI). 

Power-on: powers on the device.



Power-off: powers off the device.



Restart: cold resets the devices.



Safe restart: soft resets the device. This process includes logout.



NMI: causes the service system to generate a non-maskable interrupt.

System Events In the navigation tree, choose Events and Logs >System Events. The System Events page is displayed. On this page, you can search for, query, and clear system events. In the event view, click First, Previous, Next, or Last, or enter a page number and click Go to to go to the desired page. ClickClear to clear all logs. Click

to display the Search tab page, on which you can s et query criteria.

The clear operation is irreversible. Exercise caution before clicking Clear. Table 3-1 describes the parameters of system events.

Issue 01 (2014-01-16)


29 m~

=

OV



Table 3-1 Description of system event parameters

Parameter

Description

Severity

Health status level of an event, including Normal ( ( ), Major ( ), andCritical ( ).

Generation time

Time when the event occurred.

Sensor

Sensor that triggered the event.

Event description

Details about the event.

Event code

Code of the event.

Status

Current status of the event. It could be generated or cleared.

),Minor

Indicators In the navigation tree, choose Real-time Monitoring >LED. The LED page is displayed.

Indicator information includes the indicator name, status, supported color, default color (local control), and default color (override state). Indicator status includes control status, lit status, and color. 

Issue 01 (2014-01-16) m~

=

PM

Control status includes local control and override.


30





−

Local control: The system sets the indicator status based on the health status of the device.

−

Override: A user configured indicator status.

Lit status includes on and off.

You can click an indicator name to set the status information of the indicator, including blinking time, test duration, color, and on/off status. Table 3-2 describes indicator parameters. Table 3-2 Description of indicator parameters

Parameter

Description

State

The current indicator state

Blinking

The time during which the indicator alternates between the ON state and the OFF state. You can click the Color drop-down list box to set the indicator blinking color. Note: The blinking intervals range from 10 ms to 2500 ms.

Test

Time during which an indicator is on. You can set the color for an indicator state by clicking the Color drop-down list box. The value range from 100 ms to 12,700 ms.

On/Off

Turns an indicator on or off.

Switch to the automatic mode

Sets the current indicator to the local control state.

Issue 01 (2014-01-16)


31 m~

=

PN



3.4.5 General Configuration Items Management Network Port



Changing the IP address of a management network port will result in network disconnection. Perform this operation with caution.



The IP address of a management network port cannot reside on the same network segment as that of a shared network port. Otherwise, the network connection will fail.

Go to the Management Network Port page. Only users in the Administrators andOperators groups are allowed to configure management network ports.

On the Management Network Port page, you can: 

Enable or disable the management network port



Set the IPv4 address acquisition method, IPv4 address, subnet mask, and default gateway of the management network port



Set the IPv6 address acquisition method, IPv6 address, prefix length, and default gateway of the management network port

After completing the settings, click OK .

DNS Go to the DNS page. Domain name system (DNS) is a core service of the Internet, which maps a domain name to an IP address to let users access a network using the domain name instead of the IP address. DNS page

Issue 01 (2014-01-16) m~

=

PO


32



On the DNS page, you can set the following: 

DNS bond network interface



DNS information including the domain name, primary DNS server, and secondary DNS server

After completing the settings, click OK .

Host Name Go to the Host Name page.

Issue 01 (2014-01-16)


33 m~

=

PP



Local User Go to the Local User page. You can add, modify, and delete local users.

On the Local User page, an administrator can set a maximum of 16 users. Two administrator accounts are available on the web page: root andADMIN.

Issue 01 (2014-01-16) m~

=

PQ


34





For servers that do not have password complexity requirements, the default password is root for userroot andADMIN for userADMIN.



For servers that have password complexity requirements, the default password is Huawei12#$ for either userroot orADMIN.

The user root cannot be deleted and its permissions cannot be modified, but its password can be changed. The user ADMIN can be modified and deleted.

A user name has a maximum of 16 characters. A password has a maximum of 20 characters and can be blank. On the Local User page, you can set the following: 

Enabling or disabling password complexity



Adding, editing, or deleting a user

In the Operation column, click

to edit or add a user, and click

to delete a user.

Power Restore Policy Go to the Power Restore Policy page.

On the Power Restore Policy page, you can set the power-on policy of the system. The options include: 

Stay Off: does not power on the system after the power is turned on.



Turn On: powers on the system after the power is turned on.

Issue 01 (2014-01-16)


35 m~

=

PR

BSSN-HCNA-Storage Experiment Guide (For trainees)ISSUE 2.00 


Restore Previous State: retains the state before the power-off which is restored after the power-on. That is:

If the system was on before the power-off, the system turns on after the power is turned on.

−

−

If the system is off before the power-off, the system remains in the off state after the power is turned on.

System Boot Option Go to the System Boot Option page. On the System Boot Option page, you can set the first boot device of the server without entering the BIOS. The first boot device options include HDD, CD/DVD, Floppy/primary removable media, PXE, and No override. This setting takes effect only once. After the system restarts, this setting is invalidated.

Issue 01 (2014-01-16) m~

=

PS



HDD: boots the system from the disk.



CD/DVD: boots the system from the CD-ROM or DVD-ROM drive.



Floppy/primary removable media: boots the system from the floppy drive or removable device.



PXE: boots the system from the preboot execution environment (PXE).



No override: boots the system in BIOS default mode.


36


4

4 Storage Array Components and Installation Lab

Storage Array Components and Installation Lab

4.1 Objectives Upon completing this course you will have a working knowledge of: 

The hardware components and port functions of the S2600T or S5500T.



The hardware installation and installation precautions of the S2600T or S5500T.

4.2 Devices S2600T or S5500T

4.3 Labal Environment 1.

Components of an S5500T controller enclosure

1

Controller enclosure Power indicator

2

Controller enclosure Alarm indicator

3

Disk Alarm/Location indicator

4

Disk Running indicator

5

Coffer disk identifier

6

Disk handle

7

Disk module

The controller enclosure supports 1 Gbit/s iSCSI, 10 Gbit/s iSCSI, and 8 Gbit/s Fibre Channel host interface modules. The following figure shows a controller enclosure configured with 8 Gbit/s Fibre Channel interface modules.

Issue 01 (2014-01-16)


37 m~

=

PT



1

Power module Running/Alarm indicator

2

Power module handle

3

Power module

4

Fan-BBU module Running/Alarm indicator

5

Fan-BBU module handle

6

Fan-BBU module

7

Controller handle

8

9


10

RS-232 serial port

11

Fibre Channel interface module handle

12

8 Gbit/s Fibre Channel interface module

14

Power module socket

8 Gbit/s Fibre Channel port

13


15

Controller Power button

16

Controller Reset button

17

Fibre Channel port Link indicator

18

Controller Alarm indicator

19

Controller Power indicator

20

Expansion Status indicator

21


4.4 Procedure 4.4.1 Knowing the Hardware Components and Port Functions of the S2600T or S5500T Read section 1.3 "Devices Used in Labs" and get yourself familiar with the hardware components and port functions of the S2600T or S5500T.

4.4.2 Installation Procedure For details about how to install the S2600T or S5500T hardware, see S2600T or S5500T Series Storage System Quick Installation Guide.

Issue 01 (2014-01-16) m~

=

PU


38



Figure 4-1 S2600T or S5500T installation flowchart

4.4.3 Powering On or Off a SAN Storage Device Power on a system in the following order: cabinet → disk enclosure (waiting until it is completely powered on) → controller enclosure (by pressing the Power button on either controller) → switch (if any) → application server Power off a system in the following order: stopping services on application servers → pressing the Power button on either controller → disconnecting the controller enclosure and disk enclosures from the external power Before powering on a system, ensure that it is properly grounded. For details, see S2600T or S5500T Series Storage System Quick Installation Guide. Q&A

Issue 01 (2014-01-16)


39 m~

=

PV



Why should we connect the two power supplies of a S2600T or S5500T controller enclosure to two separate power sockets?

4.5 Questions Why should a system be powered on or off in a given order? If the order applied is incorrect, what faults may occur on the system?

Issue 01 (2014-01-16) m~

=

QM


40


5 SAN Networking Lab

5

SAN Networking Lab

5.1 Fibre Channel SAN Networking Lab of the S2600T or S5500T 5.1.1 Objectives Upon completing this lab, you will have a working knowledge of: 

Principles and methods used in Fibre Channel SAN networking of the S2600T or S5500T.



Devices and components used in Fibre Channel networking of the S2600T or S5500T.

5.1.2 Devices S2600T or S5500T, Fibre Channel switch, Fibre Channel HBA, optical fibers

5.1.3 Networking Diagram

Issue 01 (2014-01-16)


41 m~

=

QN



5.1.4 Procedure Task 1: Build a directly connected network with one single-port or dual-port HBA. Procedure: Connect the devices as shown or draw a schematic diagram.

Task 2: Build a multipathing network with one single-port HBA. Procedure: Connect the devices as shown or draw a schematic diagram.

Task 3: Build a multipathing network with two single-port HBAs or one dual-port HBA. Procedure: Connect the devices as shown or draw a schematic diagram.

Issue 01 (2014-01-16) m~

=

QO


42



Task 4: Build a full-redundancy network with two dual-port HBAs. Procedure: Connect the devices as shown or draw a schematic diagram.

Task 5: Configure zoning for a Fibre Channel switch. This task is optional. If the networking mode is simple, zoning is not required.

Step 1 Go to the Zone page on the Web Tools.

Issue 01 (2014-01-16)


43 m~

=

QP



Step 2 Create a zone.

Issue 01 (2014-01-16) m~

=

QQ


44



Step 3 Select members for the zone.

Step 4 Add zone members.

Issue 01 (2014-01-16)


45 m~

=

QR



Step 5 Save the configurations.

Step 6 Create a zone configuration.

Issue 01 (2014-01-16) m~

=

QS


46



Step 7 Add a zone to the zone configuration.

Step 8 Enable the zone configuration.

Issue 01 (2014-01-16)


47 m~

=

QT



5.2 IP SAN Networking Lab of the S2600T or S5500T 5.2.1 Objectives Upon completing this lab, you will have a working knowledge of: 

Principles and methods used in IP SAN networking of the S2600T or S5500T.



Devices used in IP SAN networking of the S2600T or S5500T.

5.2.2 Devices S2600T or S5500T, IP switch, server, network cable

5.2.3 Networking Diagram Figure 5-1 Labal networking

Issue 01 (2014-01-16) m~

=

QU


48



5.2.4 Procedure Task 1: Build a directly connected network with one or two network ports. Procedure: Connect the devices as shown or draw a schematic diagram.

Task 2: Build a multipathing network with one network port. Procedure: Connect the devices as shown or draw a schematic diagram.

Issue 01 (2014-01-16)


49 m~

=

QV



Task 3: Build a multipathing network with two network ports. Procedure: Connect the devices as shown or draw a schematic diagram.

Task 4: Build a full-redundancy network. Procedure: Connect the devices as shown or draw a schematic diagram.

Issue 01 (2014-01-16) m~

=

RM


50



5.3 Fibre Channel SAN Networking Lab of the S2600T or S5500T 5.3.1 Objectives Upon completing this lab, you will have a working knowledge of: 

Principles and methods used in Fibre Channel SAN networking of the S2600T or S5500T.



Devices and components used in Fibre Channel networking of the S2600T or S5500T.

5.3.2 Devices S2600T or S5500T, Fibre Channel switch, Fibre Channel HBA, optical fibers

5.3.3 Networking Diagram

Issue 01 (2014-01-16)


51 m~

=

RN



5.3.4 Procedure Task 1: Build a directly connected network with one single-port or dual-port HBA. Procedure: Connect the devices as shown or draw a schematic diagram.

Task 2: Build a multipathing network with one single-port HBA. Procedure: Connect the devices as shown or draw a schematic diagram.

Issue 01 (2014-01-16) m~

=

RO


52



Task 3: Build a multipathing network with two single-port HBAs or one dual-port HBA. Procedure: Connect the devices as shown or draw a schematic diagram.

Issue 01 (2014-01-16)


53 m~

=

RP



Task 4: Build a full-redundancy network with two dual-port HBAs. Procedure: Connect the devices as shown or draw a schematic diagram.

Issue 01 (2014-01-16) m~

=

RQ


54



5.4 IP SAN Networking Lab of the S2600T or S5500T 5.4.1 Objectives Upon completing this lab, you will have a working knowledge of: 

Principles and methods for IP SAN networking of the S2600T or S5500T.



Devices used in IP SAN networking of the S2600T or S5500T.

5.4.2 Devices S2600T or S5500T, IP switch, server, network cable

Issue 01 (2014-01-16)


55 m~

=

RR



5.4.3 Networking Diagram Figure 5-2 Labal networking

5.4.4 Procedure Task 1: Build a directly connected network with one or two network ports. Procedure: Connect the devices as shown or draw a schematic diagram.

Task 2: Build a multipathing network with one network port.

Issue 01 (2014-01-16) m~

=

RS


56



Procedure: Connect the devices as shown or draw a schematic diagram.

Task 3: Build a multipathing network with two network ports. Procedure: Connect the devices as shown or draw a schematic diagram.

Task 4: Build a full-redundancy network. Procedure: Connect the devices as shown or draw a schematic diagram.

Issue 01 (2014-01-16)


57 m~

=

RT


Issue 01 (2014-01-16) m~

=

RU



58


6

6 Know DeviceManager and SAN Storage M anagement Lab

Know DeviceManager and SAN Storage Management Lab

6.1 Objectives Upon completing this lab, you will have a working knowledge of: 

How to log in to the DeviceManager



Know the DeviceManager



Configuration and basic management of SAN storage devices.

6.2 Devices S2600T or S5500T, maintenance terminal, IP switch, network cable


The figure above shows the network. You must assign an IP address to the maintenance terminal and ensure that the IP address resides on the same network segment as those of the S2600T or S5500T management network ports.

Issue 01 (2014-01-16)


59 m~

=

RV



6.4 Procedure Before attempting to conduct this lab, ensure that: 1.

The S2600T or S5500T hardware is correctly installed.

2.

The S2600T or S5500T is properly powered on.

3.

The maintenance terminal can communicate with the S2600T or S5500T through its management network port on controller A or B.

4.

The IP address of the maintenance terminal must reside on the same network segment as that of the S2600T or S5500T management network ports.

5.

The maintenance terminal operating system and browser versions requirement.

Operating System

Fully Compatible Browser

Partially Compatible Browser

Windows XP Professional for X86/X64



Firefox 24 and later



Chrome 27 and later

Windows 7 Professional for X86/X64



Internet Explorer 9.0 and later Internet Explorer 8.0



Firefox 24 and later



Chrome 27 and later

Windows Server 2008 R2 Enterprise Edition SP1 for X64

Internet Explorer 8.0

Internet Explorer 8.0 and later

6.4.1 Logging In to the DeviceManager Step 1 Run Internet Explorer on the maintenance terminal. Step 2 In the address box, type https://192.168.128.101:8088 and press Enter .

NOTE:

Issue 01 (2014-01-16) m~

=

SM


60



The default management network port IP addresses of the controller A and controller B are 192.168.128.101 and 192.168.128.102, and the default subnet mask is 255.255.0.0. The default user name and password of the super administrator are admin and Admin@storage. This document uses the Windows operating system as an example to explain how to log in to the DeviceManager. The login operations on other operating systems need to be adjusted accordingly.

Step 3 Click Advanced, Set the authentication mode and language . Step 4 Type your user name, password, and verification code in Username, Password and Verification Code respectively .

Step 5 Click Log In. The DeviceManager main window is displayed.

----End

6.4.2 Configuring Basic Information About a Storage System Step 1 On the right navigation bar, click

.

Step 2 In the Viewing and Settings area, clickBasic Information.

Issue 01 (2014-01-16)


61 m~

=

SN



Step 3 Select the Device Information node. Step 4 Set Device Name andDevice Location

Step 5 Click Save, TheExecution Result dialog box is displayed, indicating that the operation succeeded.

Issue 01 (2014-01-16) m~

=

SO


62



Step 6 Click Close.

6.4.3 Setting Storage Device Time Step 1 On the right navigation bar, click

.

Step 2 In the Viewing and Settings area, clickBasic Information. Step 3 Select the Device Time node

Issue 01 (2014-01-16)


63 m~

=

SP



Step 4 Select Manual Step 5 Click Modify

Step 6 Change the storage device time, then click OK

Issue 01 (2014-01-16) m~

=

SQ


64



Step 7 Click OK

Step 8 Click Close ----End

Issue 01 (2014-01-16)


65 m  

S R


7 Managing Devices

7

Managing Devices

7.1 Objectives Upon completing this lab, you will have a working knowledge of Managing Devices using DeviceManager.



7.4 Procedure This lab will guide you through the Managing Devices of the S5500T.

7.4.1 Monitoring Controller Enclosure Step 1 On the right navigation bar, click

.

Step 2 In the Basic Information area of the function pane, click the device icon.

Issue 01 (2014-01-16) m~

=

SS


66


7 Managing Devices

Step 3 In the right function pane, click the cabinet whose Fibre Channel host port you want to view. Step 4 Click the controller enclosure where the Fibre Channel host port resides. Step 5 Click

to switch to the rear view.

Step 6 Click the Fibre Channel host port whose information you want to view.

Step 7 Click Modify.

Issue 01 (2014-01-16)


67 m~

=

ST


7 Managing Devices

Step 8 In Configured Rate (Gbit/s), select a data transfer rate for the Fibre Channel host port. Step 9 Click Apply. Step 10 Confirm the information in the dialog box and select I have read the previous information and understood subsequences of the operation .

Step 11 Click OK. TheSuccess message box is displayed, indicating that the operation succeeded. Step 12 Click OK .

Issue 01 (2014-01-16) m~

=

SU


68


7 Managing Devices

Step 13 Click the Ethernet port whose information you want to view.


Issue 01 (2014-01-16)


69 m~

=

SV


7 Managing Devices

Step 15 In the IPv4 address text box, enter an IP address for the Ethernet port. Step 16 In the Subnet Mask area, enter the subnet mask of the Ethernet port. Step 17 In MTU (Byte), type a maximum transfer unit (MTU) for the packets transferred between the Ethernet port and the application server. NOTE: The MTU must be an integer ranging from 1500 to 9000.

Step 18 Click Apply. Step 19 Confirm the information in the dialog box and select I have read the previous information and understood subsequences of the operation .

Issue 01 (2014-01-16) m~

=

TM


70


7 Managing Devices

Step 20 Click OK . The Success message box is displayed, indicating that the operation succeeded. . Step 21 Click OK

Step 22 Click the Ethernet port to which you want to add a route. Step 23 Click Route Management.

Issue 01 (2014-01-16)


71 m~

=

TN


7 Managing Devices

Step 24 In IP Address, select the IP address of the Ethernet port. Step 25 Click Add.

Step 26 In Type, select default. Step 27 In Gateway, enter the gateway where the local end Ethernet port's IP address resides. Issue 01 (2014-01-16) m~

=

TO


72


7 Managing Devices

Step 28 Click OK . The route information is added to the route list. Step 29 Confirm the information in the dialog box and select I have read the previous information and understood subsequences of the operation.

. The Success message box is displayed, indicating that the operation succeeded. Step 30 Click OK

Step 31 Click Close. ----End

7.4.2 Monitoring Disk Enclosures Step 1 On the right navigation bar, click

.

Step 2 In the Basic Information area of the function pane, click the device icon. Step 3 In the right function pane, click the cabinet whose disk you want to view. Step 4 Click the disk enclosure that houses the disk. Step 5 Click the disk whose information you want to view.

Issue 01 (2014-01-16)


73 m~

=

TP


7 Managing Devices

Step 6 Select the disk you want to locate and click Locate Disk in the lower area of the function pane. The Execution Result dialog box is displayed, indicating that the operation succeeded.

NOTE: After the disk is replaced with a new one, the disk Location indicator remains on. In this case, cancel disk locating.

Step 7 Click Close.

Issue 01 (2014-01-16) m~

=

TQ


74


7 Managing Devices

Step 8 Select the disk of which you want to cancel locating and click Cancel Locating in the lower area of the function pane. The Execution Result message box is displayed, indicating that the operation succeeded.


7.4.3 Powering On and Off an Interface Module Step 1 On the right navigation bar, click

.

Step 2 In the Basic Information area of the function pane, click the device icon. Step 3 In the right function pane, click the cabinet whose interface module port you want to power on and off.

Step 4 Click the controller enclosure that houses the interface module. Step 5 Click


Step 6 Click the interface module you want to power on and off.

Issue 01 (2014-01-16)


75 m~

=

TR


7 Managing Devices

Step 7 Click Power On. The Success message box is displayed, indicating that the operation succeeded.

Step 8 Click OK . The interface module is powered on. . Step 9 Click Power Off

Step 10 Confirm the information in the dialog box and select I have read the previous information and understood subsequences of the operation .

Issue 01 (2014-01-16) m~

=

TS


76


7 Managing Devices

Step 11 Click OK . The Success message box is displayed, indicating that the operation succeeded. . The interface module is powered off. Step 12 Click OK ----End

7.4.4 Powering Off a Device Step 1 On the right navigation bar, click

.

Step 2 In the Task area, choosePower Off Device.

Step 3 Confirm the information in the dialog box and select I have read the previous information and understood subsequences of the operation .

Step 4 Click OK . The Success message box is displayed, indicating that the operation succeeded. Issue 01 (2014-01-16)


77 m~

=

TT


8 Basic Function Configuration Lab of SAN Storage Products

Step 5 Click OK . You have powered off the storage system. ----End

8

Basic Function Configuration Lab of SAN Storage Products

8.1 Objectives Upon completing this lab, you will have a working knowledge of basic configuration and functions of SAN storage products. The basic functions include Disk Domains, Storage Pools,, LUNs, LUN Groups, Hosts, Host Groups, Host Ports, Port G roup, Mapping Views and initiators. This lab uses the S5500T as an example.



Issue 01 (2014-01-16) m~

=

TU


78



8.4 Procedure This lab will guide you through allocating storage space, configuring hosts, and importing licenses for SAN storage products.

8.4.1 Configuring Management Port on S2600T or S5500T Step 1 On the right navigation bar, click

.


Step 3 In the right function pane, click the cabinet whose Management port you want to view. Step 4 Click the controller enclosure where the Management port resides. Step 5 Click


Step 6 Click the Management port whose information you want to view.

Issue 01 (2014-01-16)


79 m~

=

TV




Issue 01 (2014-01-16) m~

=

UM


80



Step 8 In the IPv4 address text box, enter an IP address for the Management port. Step 9 In the Subnet Mask area, enter the subnet mask of the Management port. Step 10 Click Apply. Step 11 Confirm the information in the dialog box and select I have read the previous information and understood subsequences of the operation .

Issue 01 (2014-01-16)


81 m  

U N



Step 12 Click OK . The Success message box is displayed, indicating that the operation succeeded. Step 13 Click OK .

8.4.2 Creating a Disk Domain

The Disks in slots 0 through 3 of the controller enclosure are system coffer disks, which are used to save critical system data. Do not insert or remove the coffer disks, nor change the sequence of the coffer disks unless it is absolutely necessary. Otherwise, system data may be damaged. Do not insert or remove disks in other slots unless necessary. Otherwise, data loss may occur. Ensure that coffer disks are of the same type.

Step 1 Log in to the DeviceManager. NOTE: Now you will use 192.168.6.21 to log in to the DeviceManager.

Step 2 On the right navigation bar, click

.

Step 3 In the View and Management area, click Disk Domain.

Step 4 Click Create. The Create Disk Domain dialog box is displayed.

Issue 01 (2014-01-16) m~

=

UO


82



Step 5 In the Name text box, enter a name for the disk domain. Step 6 In the Description text box, enter the function and properties of the disk domain. The descriptive information helps identify the disk domain.

Step 7 In Disk type, select Manually select menus to set the types of disks that comprise the disk domain.

Step 8 Click Select.

Issue 01 (2014-01-16)


83 m~

=

UP



Step 9 In Available Disks area,select the disks that you want to add to the disk domain. Step 10 Click

Issue 01 (2014-01-16) m~

=

UQ

.


84



Step 11 Click OK. Step 12 Click OK. A message is displayed, indicating that t he operation succeeded.

Step 13 Click OK . ----End

8.4.3 Creating a Storage Pool Step 1 Log in to the DeviceManager.


.

Step 3 In the View and Management area, click Storage Pool. Step 4 Click Create.

Issue 01 (2014-01-16)


85 m~

=

UR



Step 5 In the Name text box, enter a name for the storage pool. Step 6 In the Description text box, enter the function and properties of the storage pool. The descriptive information helps identify the storage pool.

Step 7 In Disk Domain, select the disk domain to be added. Step 8 In RAID Policy, select the RAID 5 and 2D+1P. Step 9 In Capacity, enter 2.

Issue 01 (2014-01-16) m~

=

US


86



Step 10 Click Advanced.

Step 11 In Capacity Alarm Threshold, enter 80. Step 12 In Data Migration Granularity, select 4MB. Step 13 Click OK. Step 14 Click OK.The Execution Result dialog box is displayed indicating that the operation succeeded.

Step 15 Click Close.

Issue 01 (2014-01-16)


87 m~

=

UT



----End

8.4.4 Creating a LUN Step 1 Log in to the DeviceManager.


.

Step 3 In the View and Management area, click LUN. Step 4 Click Create.

Issue 01 (2014-01-16) m~

=

UU


88



Step 5 In the Name, enter Name of a newly created LUN. Step 6 In the Description, enter Description of a newly created LUN. Step 7 In the Capacity, enter 100. Step 8 In the Owning Storage Pool, select the storage pool to which the LUN you are creating belongs

Step 9 Click Advanced . The Advanced dialog box is displayed. Step 10 Click the Properties tabs.

Issue 01 (2014-01-16)


89 m~

=

UV



Step 11 In Owning Controller, select ENG0.A. Other parameter use default. . Step 12 Click OK

Step 13 Click OK . The Execution Result dialog box is displayed, indicating that the operation succeeded.

Issue 01 (2014-01-16) m~

=

VM


90




8.4.5 Creating a LUN Group Step 1 Log in to the DeviceManager.


.

Step 3 In the View and Management area, click LUN. Step 4 Select the LUN Group tab. Step 5 Click Create.

Issue 01 (2014-01-16)


91 m~

=

VN



Step 6 In the Name, enter Name of a newly created LUN Group. Step 7 In the Description, enter Description of a newly created LUN Group. Step 8 In the Available LUNs area, select one or multiple LUNs based on your service need. Step 9 Click

Issue 01 (2014-01-16) m~

=

VO

to add the LUNs to the Selected LUNs area.


92



Step 10 Click OK . The Execution Result message box is displayed, indicating that the operation succeeded.


Issue 01 (2014-01-16)


93 m  

V P


9

9 Connecting SAN Storage Devices to Windows-based Hosts

Connecting SAN Storage Devices to Windows-based Hosts


Fibre Channel SAN configuration in the Windows environment.



IP SAN configuration in the Windows environment.



Disk management for Windows-based hosts.

9.2 Devices S2600T or S5500T, maintenance terminal, Fibre Channel switch, IP switch, optical fiber, network cable

9.3 Networking Diagram Fibre Channel SAN

IP SAN

Issue 01 (2014-01-16) m~

=

VQ


94



9.4 IP Address Planning 

The IP addresses of the maintenance terminal and the management network port of the storage device are on the same network segment.



The IP addresses of the maintenance terminal and the management network port of the server are on the same network segment.



The service network port IP addresses of the storage device and the server are on the same network segment.

Device Name

Management IP Address

Service IP Address

S5500T

Controller A: 192.168.6.21

Controller A: 192.168.7.21 Controller B: 192.168.7.22

Controller B: 192.168.6.22 RH2285 V2

192.168.6.23

Maintenance terminal

192.168.6.24

VLAN ID (configured based on site requirements)

Vlan6

Issue 01 (2014-01-16)


192.168.7.23

Vlan7

95 m~

=

VR



9.5 Procedure 9.5.1 Building a Fibre Channel SAN in the Windows Environment Installing a Driver for the Fibre Channel HBA on the Windows-based Server Step 1 Open the server chassis and install a Fibre Channel HBA. Step 2 Start up the Windows-based server and log in to the server as a user in the Administrators group.

Step 3 Install a Fibre Channel HBA driver for Windows Server 2003 . ----End

Querying the WWPN of a Fibre Channel HBA (Qlogic QLE2562 HBA) Step 1 Double-click the icon of the Qlogic HBA application. The QConvergeConsole CLI window is displayed.

Step 2 In the Main Menu screen, type 1 and press Enter.

Issue 01 (2014-01-16) m~

=

VS


96



Step 3 In the FC Adapter Information screen, type 1 and press Enter. The Adapter Information screen is displayed, as shown in the red square in the following figure.

----End

Creating a Host on S2600T or S5500T Step 1 Log in to the DeviceManager.


.

Step 3 On the host management page, click Host. Step 4 Choose Create > Manual Creation.

Issue 01 (2014-01-16)


97 m~

=

VT



Step 5 In the Name, enter Name of the host. Step 6 In the Description, enter Description of the host. Step 7 In the OS, select windows. Step 8 Click Next.

Issue 01 (2014-01-16) m~

=

VU


98



Step 9 In the Available Initiators area, select one or multiple initiators based on your service need. NOTE: If the initiator information has been configured on the application server, the DeviceManager can automatically detect the configured initiator. You only need to select the initiator information from t he initiator list rather than manually creating it, so you can skip Step 10 to 15. You do not add initiators on different application servers to a same host.

Step 10 Click Create. Step 11 From the Type list, select FC. Step 12 In WWPN, enter the WWPN number. For example: 21000024FF3FB076.

Issue 01 (2014-01-16)


99 m~

=

VV



Step 13 Click OK.

Step 14 Click OK. Step 15 In the Available Initiators area, select one initiators based on your service need. Step 16 Click

Issue 01 (2014-01-16) m~

=

NMM

to add the initiator to the Selected Initiators area.


100



Step 17 Click Next.

Issue 01 (2014-01-16)


101 m~

=

NMN



Step 18 Click Finish.

.

Issue 01 (2014-01-16) m~

=

NMO


102



Step 19 Carefully read the content in the dialog box. Then select I have read the previous information and understood subsequences of the operation for confirmation.

Step 20 Click OK . The Execution Result dialog box is displayed indicating that the operation succeeded.

Step 21 Click close. ----End

Creating a Host Group Step 1 Log in to the DeviceManager.


.

Step 3 On the host management page, click Host. Step 4 Click the Host Group tab.

Issue 01 (2014-01-16)


103 m~

=

NMP



Step 5 Click Create .

Step 6 In the Name, enter Name of the host group. Step 7 In the Description, enter Description of the host group. Step 8 In the Available Hosts area, select one or multiple initiators based on your service need. Step 9 Click

to add the hosts to the Selected Hosts area.

. The Execution Result message box is displayed, indicating that the operation Step 10 Click OK succeeded.

Issue 01 (2014-01-16) m~

=

NMQ


104



Step 11 Click Close. ---End

Creating a Port Group Step 1 Log in to the DeviceManager.


.

Step 3 On the host management page, click Host Port. Step 4 Click the Port Group tab. Step 5 Click Create.

Issue 01 (2014-01-16)


105 m~

=

NMR



Step 6 In the Name, enter Name of the port group. Step 7 In the Description, enter Description of the port group. Step 8 Select the ports you want to add to the port group in Available Ports list. Step 9 Click

and add the ports to Selected Ports .

. The Execution result message box is displayed, indicating that the operation Step 10 Click OK succeeded.

Issue 01 (2014-01-16) m~

=

NMS


106




Creating a Mapping View


.

Step 2 On the host management page, click Mapping View. Step 3 Click Create.

Issue 01 (2014-01-16)


107 m~

=

NMT



Step 4 In the Name text box, enter a name for the mapping view. Step 5 In the Description text box, describe the mapping view. Step 6 In LUN group, Click

. The Select LUN Group dialog box is displayed.

Step 7 From the LUN group list, select the LUN group you want to add to the mapping view.

Issue 01 (2014-01-16) m~

=

NMU


108



. Step 8 Click OK

Step 9 In host group, Click

. The Select Host Group dialog box is displayed.

Step 10 From the host group list, select the host group you want to add to the mapping view. Step 11 Click OK .

Issue 01 (2014-01-16)


109 m~

=

NMV


Step 12 In port group, Click

Issue 01 (2014-01-16) m~

=

NNM


. The Select Port Group dialog box is displayed.


110



Step 13 From the port group list, select the port group you want to add to the mapping view. Step 14 Click OK .

Issue 01 (2014-01-16)


111 m~

=

NNN



. The Execution Result dialog box is displayed, indicating that the operation Step 15 Click OK succeeded.


Issue 01 (2014-01-16) m

NNO


112



Viewing a LUN Step 1 Right-click My Computer and chooseManage from the shortcut menu. In theComputer Management window that is displayed, right-clickDisk Management in the navigation tree and choose Rescan Disks from the shortcut menu.

Two new disks are discovered because of the two initiators configured. Multipathing software must be installed before you can use the disks.

Issue 01 (2014-01-16)


113 m~

=

NNP



Step 2 Right-click My Computer and chooseDevice Manager from the shortcut menu. The disk information is displayed under Disk drives.

----End

Installing Multipathing Software Step 1 Obtain the Huawei-supplied multipathing software named UltraPath from the Huawei official website or the CD-ROM included with the delivery. Pay attention to the compatibility of the UltraPath.

Step 2 Decompress the UltraPath. Step 3 Double-click the installation file.

Issue 01 (2014-01-16) m~

=

NNQ


114



Step 4 Install the UltraPath as prompted.

Issue 01 (2014-01-16)


115 m~

=

NNR


Issue 01 (2014-01-16) m~

=

NNS



116



Step 5 Restart the host after the installation.

Step 6 After the operating system restarts, view disk information of the host. The number of new disks is half that discovered before the UltraPath installation.

Issue 01 (2014-01-16)


117 m~

=

NNT



----End

Using a LUN Step 1 Go to the Computer Management window.

Issue 01 (2014-01-16) m~

=

NNU


118



from the shortcut menu. Step 2 Right-click the new disk and choose Initialize Disk

Step 3 Create a partition.

Issue 01 (2014-01-16)


119 m~

=

NNV


Issue 01 (2014-01-16) m~

=

NOM



120



Step 4 Create a logical drive.

Issue 01 (2014-01-16)


121 m~

=

NON


Issue 01 (2014-01-16) m~

=

NOO



122


Issue 01 (2014-01-16)



123 m~

=

NOP


Issue 01 (2014-01-16) m~

=

NOQ



124



----End

Issue 01 (2014-01-16)


125 m

NOR



9.5.2 Building an IP SAN in the Windows Environment Installing Initiator Software in the Windows Environment Step 1 Log in to the Windows-based server as a user in the Administrators group. Step 2 Install Microsoft iSCSI Initiator. Restart the server after the installation is complete. You can download the installation program of Microsoft iSCSI Initiator from the Microsoft website. Version 2.01 or later is required. If you are going to install the UltraPath, do not select Microsoft MPIO Multipathing Support for iSCSI for Installation Options when installing Microsoft iSCSI Initiator. You need to configure Microsoft iSCSI Initiator only when the host connects to iSCSI host ports on the storage device.

----End

Querying the Name of an Initiator Step 1 Open Microsoft iSCSI Initiator. On the General tab page, click Change.

Issue 01 (2014-01-16) m~

=

NOS


126



Step 2 View the initiator name in Initiator node name.

----End

Configuring iSCSI Host Port Step 1 On the right navigation bar, click

.


Issue 01 (2014-01-16)


127 m~

=

NOT



Step 3 In the right function pane, click the cabinet whose iSCSI Host Port you want to view. Step 4 Click the controller enclosure where the iSCSI Host Port resides. Step 5 Click


Step 6 Click the iSCSI Host Port whose information you want to view.

Issue 01 (2014-01-16) m~

=

NOU


128




Step 8 In the IPv4 address text box, enter an IP address for the iSCSI Host Port. Step 9 In the Subnet Mask area, enter the subnet mask of the iSCSI Host Port. Step 10 In MTU (Byte), type a maximum transfer unit (MTU) for the packets transferred between the Ethernet port and the application server. NOTE: The MTU must be an integer ranging from 1500 to 9000.

Step 11 Click Apply. Step 12 Confirm the information in the dialog box and select I have read the previous information and understood subsequences of the operation .

Issue 01 (2014-01-16)


129 m~

=

NOV



Step 13 Click OK . The Success message box is displayed, indicating that the operation succeeded. Step 14 Click OK .

Creating a Host on S2600T or S5500T Step 1 Log in to the DeviceManager.


.


Issue 01 (2014-01-16) m~

=

NPM


130



Step 5 In the Name, enter Name of the host. Step 6 In the Description, enter Description of the host. Step 7 In the OS, select windows. Step 8 In the IP Address, enter IP Address of the host, for example: 192.168.7.23 Step 9 Click Next.

Issue 01 (2014-01-16)


131 m~

=

NPN




Step 11 Click Create. Step 12 From the Type list, select iSCSI. Step 13 In IQN, enter the iSCSI Qualified Name (IQN) of an iSCSI initiator. For example: iqn.1991-05.com.microsoft:tc132.

Issue 01 (2014-01-16) m~

=

NPO


132



Step 14 Click OK.


Issue 01 (2014-01-16)



133 m~

=

NPP



Step 18 Click Next.

Issue 01 (2014-01-16) m~

=

NPQ


134




.

Issue 01 (2014-01-16)


135 m~

=

NPR








.

Step 3 On the host management page, click Host.

Issue 01 (2014-01-16) m~

=

NPS


136



Step 4 Click the Host Group tab. Step 5 Click Create .



Step 10 Click OK . The Execution Result message box is displayed, indicating that the operation succeeded.

Issue 01 (2014-01-16)


137 m~

=

NPT






.


Issue 01 (2014-01-16) m~

=

NPU


138






Issue 01 (2014-01-16)


139 m~

=

NPV






.


Issue 01 (2014-01-16) m~

=

NQM


140






Issue 01 (2014-01-16)


141 m~

=

NQN



. Step 8 Click OK




Issue 01 (2014-01-16) m~

=

NQO


142



Issue 01 (2014-01-16)




143 m~

=

NQP




Issue 01 (2014-01-16) m~

=

NQQ


144





Issue 01 (2014-01-16)


145 m

NQR



Configuring and Connecting an Initiator Step 1 Start Microsoft iSCSI Initiator. The iSCSI Initiator Properties dialog box is displayed. See the following figure. Figure 9-1 Starting Microsoft iSCSI Initiator

Step 2 On the General tab page, clickChange. In the Initiator Node Name Change dialog box that is displayed, change the name of the initiator. (You can skip this step if you do not want to rename the initiator) Figure 9-2 Renaming the initiator

Issue 01 (2014-01-16) m~

=

NQS


146



Ensure that the initiator node name is the same as the Alias inConfigure Initiator. Otherwise, the LUN is inaccessible on the server. Q&A

Are the initiator options available on the ISM when the server is disconnected from the storage device or when initiator software is not installed on the server? What is the best installation and configuration procedure?

Step 3 On the Discovery tab page, clickAdd in theTarget Portals area. TheAdd Target Portal dialog box is displayed. See the following figure.

Q&A

In a SAN, the initiator is on the server end, and the target is on the storage array end. In the Add Target Portal dialog box, the IP address is that of the storage array. What IP address should be used in the initial configuration of the storage array?

Step 4 In the IP address or DNS name text box,enter the IP address of the iSCSI host port that connects to the application server.

Step 5 Click OK . You can view the information about the added target port in the Target Portals area.

Step 6 Click the Targets tab. The status of the target isInactive.

Issue 01 (2014-01-16)


147 m~

=

NQT



Step 7 In the Targets area, select an available target and clickLog On. The Log On to Target dialog box is displayed. See the following figure.

. The system returns to the Log On to Target dialog box. Step 8 Click OK

Step 9 Click OK Properties dialog box. . The system returns to the iSCSI Initiator Properties Step 10 In the Targets tab, check that the status of the target isConnected. In this case, the host can access the storage device. See the following figure.

Issue 01 (2014-01-16) m~

=

NQU


148



Figure 9-3 Connection status of the target port

Step 11 Click OK .

You need to configure Microsoft iSCSI Initiator only when the host connects to iSCSI host ports on the storage device. device. ----End

Installing Multipathing Software For details, see section "Installing Multipathing Software."

Using a LUN For details, see section "Using a LUN."

9.6 Questions If the host connects to the storage device through Fibre Channel links, how will the host configurations differ from those in the case of an iSCSI connection?

Issue 01 (2014-01-16)


149 m~

=

NQV


10

10 Connecting SAN Storage Devices to Linux-based Hosts

Connecting SAN Storage Devices to Linux-based Hosts


Fibre Channel SAN configuration in the SUSE Linux environment.



IP SAN configuration in the SUSE Linux environment.



Disk management in the SUSE Linux environment.

10.2 Devices S2600T or S5500T, maintenance terminal, Fibre Channel switch, IP switch, optical fiber, network cable

10.3 Networking Diagram Fibre Channel SAN

IP SAN

Issue 01 (2014-01-16) m~

=

NRM


150



Labal networking The figures above show the network layout. You must assign two IP addresses to the maintenance terminal. Ensure that one IP address resides on the same network segment as those of the S5500T management network ports and the other resides on the same network segment as those of the S5500T iSCSI service network ports. The application server connects to the S5500T using Fibre Channel HBAs on the server and LC-LC multi-mode optical fibers.

10.4 IP Address A ddress Planning 1.

The IP addresses of the maintenance terminal and the management network port of the storage device are on the same network segment.

2.

The IP addresses of the maintenance terminal and the management network port of the server are on the same network segment.

3.

The service network port IP addresses of the storage device and the server are on the same network segment.

Device Name


Service IP Address

S5500T

Controller A: 192.168.6.21

Controller: 192.168.7.21

Controller B: 192.168.6.22

Controller B: 192.168.7.22

192.168.6.23

192.168.7.23

RH2285 V2

Issue 01 (2014-01-16)


151 m~

=

N RN



Device Name


Maintenance terminal

192.168.6.24

VLAN ID (configured based on site requirements)

Vlan6

Service IP Address

Vlan7

10.5 Procedure This document uses an application server that runs SUSE Linux Enterprise Server 10 SP2 (SLES 10 SP2 for short) as an example to explain how to connect a Linux-based application server to an S5500T.

10.5.1 Building a Fibre Channel SAN in the SUSE Linux Environment Installing a Fibre Channel HBA Driver in the SUSE Linux Environment Step 1 Log in to the Linux-based application server as user root. Check whether the host has identified the HBA. If the host already has the driver for the HBA, go to step 2. Log in to the application server as user root. Run cat /etc/issue to query the operating system version. The output is as follows: #cat /etc/issue Welcome to SUSE Linux Enterprise Server 10 SP2 (x86_64) - Kernel \r (\l). Check whether the host has identified the Fibre Channel HBA. SUSE 10 has an HBA driver. Run cat /sys/class/fc_host/host5/node_name to query the WWN of the HBA. If this file does not exist, go to step 2. The output is as follows: # cat /sys/class/fc_host/host5/node_name 0x2000001b32923fd8

Step 2 If the host did not identify the Fibre Channel HBA, you must manually install the HBA driver. Download the RPM package from the official website of the HBA vendor and upload it to the application server.

Install the RPM package compatible with the existing SUSE Linux operating system. Log in to the application server as user root. Run rpm –ivh XXX whereXXX is the name of the Fibre Channel HBA driver RPM package to install. Then perform step 1 again to check the result.

Issue 01 (2014-01-16) m~

=

NRO


152



Step 3 Run systool -c fc_host -A node_name to query the WWN of the Fibre Channel HBA. linux-1uez:~ # systool -c fc_host -A node_name Class = "fc_host" Class Device = "host4" node_name

= "0x20000024ff3fb076" "0x20000024ff3fb076"

Device = "host4" Class Device = "host5" node_name

= "0x20000024ff3fb077" "0x20000024ff3fb077"

Device = "host5" ----End

Creating a Host on S2600T or S5500T Step 1 Log in to the DeviceManager. DeviceManager.


.


Issue 01 (2014-01-16)


153 m~

=

NR P



Step 5 In the Name, enter Name of the host. Step 6 In the Description, enter Description of the host. Step 7 In the OS, select Linux. Step 8 Click Next.

Issue 01 (2014-01-16) m~

=

N RQ


154





Issue 01 (2014-01-16)


155 m~

=

NRR



Step 13 Click OK.


Issue 01 (2014-01-16) m~

=

NR S



156



Step 17 Click Next.

Issue 01 (2014-01-16)


157 m~

=

NRT




Issue 01 (2014-01-16) m~

=

NRU


158








.

Step 3 On the host management page, click Host. Step 4 Click the Host Group tab. Issue 01 (2014-01-16)


159 m~

=

NRV







Issue 01 (2014-01-16) m~

=

NSM


160






.


Issue 01 (2014-01-16)


161 m~

=

NSN






Issue 01 (2014-01-16) m~

=

NSO


162






.


Issue 01 (2014-01-16)


163 m~

=

NSP






Issue 01 (2014-01-16) m~

=

NSQ


164



. Step 8 Click OK




Issue 01 (2014-01-16)


165 m~

=

NSR



Issue 01 (2014-01-16) m~

=

NSS




166




Issue 01 (2014-01-16)


167 m~

=

NST





Issue 01 (2014-01-16) m

NSU


168



Viewing a LUN Run fdisk –l to view LUNs mapped to the host.

You can also run lsscsi to view LUNs mapped to the host.

Two new disks are discovered although only one LUN is mapped to the host. Multipathing software must be installed before the disks can be used.

Installing Multipathing Software in the SUSE Linux Environment Step 1 The following figure shows the directory of the UltraPath for Linux installation package.

Step 2 Copy the installation package to a directory on the Linux-based application server. Step 3 Log in to the Linux-based application server and navigate to the directory. Run the following commands in sequence:

Issue 01 (2014-01-16)


169 m~

=

NSV



dos2unix install.sh chmod +x install.sh ./ install.sh

The output is as follows:

Select the initiator type based on the networking mode. Type 1 for an IP SAN and 2 for a Fibre Channel SAN.

Step 4 Select a system boot type. To boot the operating system on the local disk, type 1. To boot the operating system on the SAN, type 2.

Step 5 Once the installation is complete, you are asked to restart the operating system. Type Y.

Step 6 Once the system starts up, check the number of disks. If only one disk exists, the multipathing software has taken effect.

Issue 01 (2014-01-16) m~

=

NTM


170



1.

Do not copy the UltraPath installation package to a directory that contains a space in the path name, for example, /home/Dad Dir/. Otherwise, execution of the script install.sh will encounter an error.

2.

If the UltraPath has been installed on the host and the directory of the UltraPath installation package still exists, do not copy the new UltraPath installation package to that directory to avoid confusion.

----End

Using a LUN Step 1 Log in to the Linux-based application server as user root. Step 2 In the case of a multipathing network, check whether the UltraPath for Linux software is installed on the application server. Run rpm –q UltraPath. If the following information is displayed: package UltraPath is not installed The UltraPath for Linux is not installed. Install the software by following the instructions detailed in the previous section. If the following information is displayed: UltraPath-5.01.070-2

The UltraPath for Linux is installed.

Issue 01 (2014-01-16)


171 m~

=

NTN



UltraPath 5.01.070-2 is used as an example. The actual UltraPath version may be different.

Step 3 Enable the port services on the application server. When iSCSI host ports are used and UltraPath is not installed: Run service open-iscsi restart to start the iSCSI service and scan for newly mapped LUNs. When iSCSI host ports are used and UltraPath is installed: Run /etc/init.d/iSCSI restart to start the iSCSI service. Run hot_add to scan for identifiable LUNs. When Fibre Channel host ports are used and UltraPath is installed: Run hot_add to identify loaded LUNs, as shown in the following figure.

Sometimes, you may need to run hot_add several times to scan for newly mapped LUNs. When Fibre Channel host ports are used and UltraPath is not installed, you need to restart the host in order to discover disks.

Step 4 Run fdisk -1 to view the information about all disks on the application server. The output is as follows:

Step 5 In this example, run fdisk /dev/sdb to partition the sdb logical disk. The output is as follows: linux-suse-icy:/usr/sbin # fdisk /dev/sdb Device contains neither a valid DOS partition table, nor Sun, SGI or OSF disklabel

Issue 01 (2014-01-16) Page

172


172



Building a new DOS disklabel. Changes will remain in memory only, until you decide to write them. After that, of course, the previous content won't be recoverable. The number of cylinders for this disk is set to 10240. There is nothing wrong with that, but this is larger than 1024, and could in certain setups cause problems with: 1) software that runs at boot time (for example, old versions of LILO) 2) booting and partitioning software from other OSs (for example, DOS FDISK, OS/2 FDISK) Warning: invalid flag 0x0000 of partition table 4 will be corrected by w(rite) Command (m for help): m Command action a

toggle a bootable flag

b

edit bsd disklabel

c

toggle the dos compatibility flag

d

delete a partition

l

list known partition types

m

print this menu

n

add a new partition

o

create a new empty DOS partition table

p

print the partition table

q

quit without saving changes

s

create a new empty Sun disklabel

t

change a partition's system id

u

change display/entry units

v

verify the partition table

w

write table to disk and exit

x

extra functionality (experts only)

Command (m for help): n Command action e

extended

p

primary partition (1-4)

e Partition number (1-4): 1

Issue 01 (2014-01-16)


173 Page

173



First cylinder (1-10240, default 1): Using default value 1 Last cylinder or +size or +sizeM or +sizeK (1-10240, default 10240): Using default value 10240 Command (m for help): w The partition table has been altered! Calling ioctl() to re-read partition table. Syncing disks.

Step 6 Set /dev/sdb as the logical partition. linux-suse-icy:~ # fdisk /dev/sdb The number of cylinders for this disk is set to 10240. There is nothing wrong with that, but this is larger than 1024, and could in certain setups cause problems with: 1) software that runs at boot time (for example, old versions of LILO) 2) booting and partitioning software from other OSs (for example, DOS FDISK, OS/2 FDISK) Command (m for help): m Command action a

toggle a bootable flag

b

edit bsd disklabel

c

toggle the dos compatibility flag

d

delete a partition

l

list known partition types

m

print this menu

n

add a new partition

o

create a new empty DOS partition table

p

print the partition table

q

quit without saving changes

s

create a new empty Sun disklabel

t

change a partition's system id

u

change display/entry units

v

verify the partition table

w

write table to disk and exit

x

extra functionality (experts only)

Issue 01 (2014-01-16) Page

174


174



Command (m for help): n Command action l

logical (5 or over)

p

primary partition (1-4)

l First cylinder (1-10240, default 1): Using default value 1 Last cylinder or +size or +sizeM or +sizeK (1-10240, default 10240): Using default value 10240 Command (m for help): w The partition table has been altered! Calling ioctl() to re-read partition table. Syncing disks.

Step 7 Run mkfs.ext3 /dev/sdb5 to create a file system for the sdb. (Perform this step based on actual requirements.) The output is as follows: linux-suse-icy:~ # mkfs.ext3 /dev/sdb5 mke2fs 1.38 (30-Jun-2005) Filesystem label= OS type: Linux Block size=4096 (log=2) Fragment size=4096 (log=2) 1310720 inodes, 2621432 blocks 131071 blocks (5.00%) reserved for the super user First data block=0 Maximum filesystem blocks=2684354560 80 block groups 32768 blocks per group, 32768 fragments per group 16384 inodes per group Superblock backups stored on blocks: 32768, 98304, 163840, 229376, 294912, 819200, 884736, 1605632 Writing inode tables: done Creating journal (32768 blocks): done Writing superblocks and filesystem accounting information: done

Issue 01 (2014-01-16)


175 Page

175



This filesystem will be automatically checked every 36 mounts or 180 days, whichever comes first. Use tune2fs -c or -i to override.

Step 8 Run the following command to create a directory. Name the directory based on actual requirements. mkdir /mnt/sdb5

Step 9 Run the following command to mount the device to the directory. mount /dev/sdb5 /mnt/sdb5

Step 10 Check whether the mounting is successful.

----End

10.5.2 Building an IP SAN in the SUSE Linux Environment The prerequisites of this lab are: 1.

The IP addresses of the maintenance terminal and the management network ports of the storage device and the server are on the same network segment.

2.

The service IP addresses of the storage device and the server are on the same network segment.

Installing iSCSI Software in the SUSE Linux Environment Envi ronment Step 1 Log in to the Linux-based application server as user root. Step 2 Run rpm -qa|grep open-iscsi to check whether the iSCSI RPM package is installed on the application server. If the following information is displayed, the RPM package is installed on the application server. Go to step 4. Otherwise, go to step 3. #rpm -qa|grep open-iscsi

open-iscsi-2.0.707-0.44

Step 3 Install the RPM package.

Install the RPM package compatible with the existing SUSE Linux operating system. Installation method 1: using RPM commands Copy the iSCSI Initiator installation package to a directory on the Linux-based application server. Temporary files are usually put in the /tmp directory. Double-click rpm –ivh XXXX.rpm to install the package.

Issue 01 (2014-01-16) m~

=

NTS


176



Installation method 2: using YaST Run the yast command. The YaST screen is displayed.

Step 4 On the left of the screen, navigate to Software. Then on the right, select Software Management . Press Enter .

Press Alt+S and search for files that contain the string "iSCSI iSCSI". The following figure shows the Package Search screen. PressAlt+O to confirm the operation.

Issue 01 (2014-01-16)


177 m~

=

NTT



Figure 10-1 Package Search screen

Step 5 Select open-iscsi to be installed, as shown in the following figure. PressAlt+A to confirm the operation. Figure 10-2 Selecting open-iscsi

Step 6 Install the RPM package as prompted.

Issue 01 (2014-01-16) m~

=

NTU


178



Step 7 Run chkconfig iscsi on to set the iSCSI service to automatic start. ----End

Querying the Name of an Initiator Run cat /etc/iscsi/initiatorname.iscsi to query the initiator name. The result is shown in the red square in the following figure.

----End

Configuring iSCSI Host Port on S2600T or S5500T For details, see section " Configuring iSCSI Host Port."

Creating a Host and a Host Group For details, see section "Creating a Host on S2600T or S5500T Log in to the DeviceManager.

Issue 01 (2014-01-16)


179 m~

=

NTV




.


Step 11 In the Name, enter Name of the host. Step 12 In the Description, enter Description of the host. Step 13 In the OS, select Linux. Step 14 Click Next.

Issue 01 (2014-01-16) m~

=

NUM


180





Issue 01 (2014-01-16)


181 m~

=

NUN



Step 19 Click OK.


Issue 01 (2014-01-16) m~

=

NUO



182



Step 23 Click Next.

Issue 01 (2014-01-16)


183 m~

=

NUP




Issue 01 (2014-01-16) m~

=

NUQ


184








.

Step 30 On the host management page, click Host. Step 31 Click the Host Group tab. Issue 01 (2014-01-16)


185 m~

=

NUR







Issue 01 (2014-01-16) m~

=

NUS


186






.


Issue 01 (2014-01-16)


187 m~

=

NUT






Issue 01 (2014-01-16) m~

=

NUU


188






.


Issue 01 (2014-01-16)


189 m~

=

NUV






Issue 01 (2014-01-16) m~

=

NVM


190



. Step 57 Click OK




Issue 01 (2014-01-16)


191 m~

=

NVN



Issue 01 (2014-01-16) m~

=

NVO




192




Issue 01 (2014-01-16)


193 m~

=

NVP





Issue 01 (2014-01-16) m

NVQ


194



."

Creating a Port Group For details, see section "Creating a Host on S2600T or S5500T

Step 66 Log in to the DeviceManager.


.


Step 70 In the Name, enter Name of the host. Step 71 In the Description, enter Description of the host. Step 72 In the OS, select Linux.

Issue 01 (2014-01-16)


195 m~

=

NVR



Step 73 Click Next.



Issue 01 (2014-01-16) m~

=

NVS


196



Step 78 Click OK.


Issue 01 (2014-01-16)



197 m~

=

NVT



Step 82 Click Next.

Issue 01 (2014-01-16) m~

=

NVU


198




Issue 01 (2014-01-16)


199 m~

=

NVV








.

Step 89 On the host management page, click Host. Step 90 Click the Host Group tab. Issue 01 (2014-01-16) m~

=

OMM


200







Issue 01 (2014-01-16)


201 m~

=

OMN






.

Step 100 On the host management page, click Host Port. Step 101 Click the Port Group tab. Step 102 Click Create .

Issue 01 (2014-01-16) m~

=

OMO


202






Issue 01 (2014-01-16)


203 m~

=

OMP






.

Step 110 On the host management page, click Mapping View. Step 111 Click Create .

Issue 01 (2014-01-16) m~

=

OMQ


204






Issue 01 (2014-01-16)


205 m~

=

OMR



. Step 116 Click OK




Issue 01 (2014-01-16) m~

=

OMS


206



Issue 01 (2014-01-16)




207 m~

=

OMT




Issue 01 (2014-01-16) m~

=

OMU


208





Issue 01 (2014-01-16)


209 m

OMV



."

Creating a Mapping View For details, see section " Creating a Mapping View."

Configuring the iSCSI Connection in the SUSE Linux Environment Step 1 Log in to the Linux-based application server as user root. Step 2 Run iscsiadm –m discovery –t st –p 192.168.7.21 andiscsiadm –m discovery –t st –p 192.168.7.22, where 192.168.7.21 is the IP address of the iSCSI host port connected to the application server. If multipathing is used, enter the command again. The parameter following –p is the IP address of the iSCSI host port on the other controller. The prerequisite is that the host can properly communicate with the iSCSI host port on the other controller.

Run iscsiadm –m node –l to log in to the target.

Step 3 Run /etc/init.d/open-iscsi restart to restart the iSCSI service. ----End

Viewing a LUN For details, see section "Viewing a LUN."

Installing Multipathing Software in the SUSE Linux Environment For details, see section "Installing Multipathing Software in the SUSE Linux Environment."

Using a LUN For details, see section "Using a LUN."

10.6 Questions What are the differences between the Fibre Channel SAN mounting in the SUSE Linux environment and that in the Windows environment? What precautions should be taken when installing multipathing software?

Issue 01 (2014-01-16) m~

=

ONM


210


11

11 Routine Maintenance Lab of SAN Storage Products

Routine Maintenance Lab of SAN Storage Products

11.1 Objectives Upon completing this lab, you will have a working knowledge of methods involved in collecting and saving various fault diagnosis information.

11.2 Devices S2600T or S5500T, IP switch, maintenance terminal, network cable


The above figure shows the networking. You must assign an IP address to the maintenance terminal and ensure that the IP address resides on the same network segment as those of the S2600T or S5500T management network ports.

Issue 01 (2014-01-16)


211 m~

=

ONN



11.4 Procedure The prerequisites of this lab are: 1.

You are familiar with the components of the S2600T or S5500T.

2.

You know how to manage the S2600T or S5500T using the DeviceManager.

11.4.1 Exporting Configuration Data of the Storage Device Using the DeviceManager Step 1 Log in to the DeviceManager.


.

area, clickExport Data. Step 3 In the Task

Step 4 In Running Data of theExport Data dialog box, clickDownload.

Issue 01 (2014-01-16) m~

=

ONO


212



Step 5 In System Log of theExport Data dialog box, clickDownload. Step 6 In Disk Log of theExport Data dialog box, clickDownload. Step 7 Click Close ----End

11.4.2 Using the Maintenance Tool Step 1 Download the OceanStor Toolkit maintenance tool package from the Huawei official website: www.huawei.com.

Issue 01 (2014-01-16)


213 m~

=

ONP



Step 2 Install the OceanStor Toolkit as prompted. Click Next while maintaining the default options until the installation is complete.

Step 3 Start the OceanStor Toolkit. Click ToolStore, select the tools you want to use. Custom install tools in OceanStor Toolkit

11.4.3 Inspection (including reviewal inspection) Step 1 Start the OceanStor Toolkit. Step 2 Click ToolCase and go to theMaintain tab page.

Issue 01 (2014-01-16) m~

=

ONQ


214



Step 3 Click Inspection (including reviewal inspection). The Inspection Wizard dialog box is displayed.

Step 4 Click Next. The Select Devices tab page is displayed. ClickAdd Device. In the Add device dialog box that is displayed, enter the basic information about the device and click Next.

Issue 01 (2014-01-16)


215 m~

=

ONR



If the device is displayed in t he Inspection Device List , it is successfully added.

Step 5 Select the newly added device and click Next.

Issue 01 (2014-01-16) m~

=

ONS


216



Step 6 On the Select Check Items tab page that is displayed, select the items to be checked and click Next.

Step 7 On the Set Check Policy tab page that is displayed, set the check policy.

Issue 01 (2014-01-16)


217 m~

=

ONT



Step 8 Click Next. The inspection starts.

Step 9 After the inspection is complete, click Finish. Handle the failed items as prompted. ----End

Issue 01 (2014-01-16) m

ONU


218



11.4.4 Collecting Information Step 1 Start the OceanStor Toolkit. On the Maintain tab page, clickInformation Collection. The Information Collection dialog box is displayed.

Step 2 Select the device whose information you want to collect and click Collect.

The OceanStor Toolkit starts to collect device information.

Issue 01 (2014-01-16)


219 m~

=

ONV



Step 3 After the collection is complete, the progress bar reaches 100% and Collection Succeeded is displayed, as highlighted by the red square in the following figure.

----End

Issue 01 (2014-01-16) m

OOM


220


12

12 Parts Replacement Lab of SAN Storage Products

Parts Replacement Lab of SAN Storage Products


Parts replacement of storage products.



Precautions to be taken before replacing parts of storage products.



Precautions to be taken after replacing parts of storage products.

12.2 Devices S2600T or S5500T

12.3 Networking Diagram None

12.4 Procedure 12.4.1 Removing a Controller

Ensure that power is cut off before attempting to remove hardware components.

Issue 01 (2014-01-16)


221 m~

=

OON



Remove and insert a controller with gentle force. Excessive force may damage the appearance or connectors of the controller.

Procedure Step 1 Wear an ESD wrist strap, ESD gloves, and ESD clothing. Step 2 Remove the cables from the controller to be removed. Step 3 Close the handles on the controller in the direction of the arrows, as shown in the following figure.

----End

Issue 01 (2014-01-16) m

OOO


222



12.4.2 Installing a Controller Step 1 Wear an ESD wrist strap or ESD gloves. Step 2 Take the new controller module out of its ESD bag. Step 3 As shown in step 1 in the following figure, insert the new controller module into the vacant slot.

Step 4 Open the handles on the controller, as shown in step 2 in the following figure.

Step 5 Connect the cables to their appropriate sockets. Step 6 Check whether the controller is successfully installed according to the status of the controller Power indicator and Alarm indicator. A controller takes 5 to 8 minutes to start. After it powers on, check whether it is successfully installed by observing the indicators.

Issue 01 (2014-01-16)


223 m~

=

OOP



If the Power indicator is on and the Fault indicator is off, the controller is successfully installed. If the Power indicator is off or the Alarm indicator is on, the controller is incorrectly installed. In this case, remove and reinsert the controller. Log in to the ISM. In the navigation tree, choose Device Info > Storage Unit> Controllers. In the function pane, check whether the status of each component is normal. If yes, the installation is complete. On the menu bar, choose Event >Event Management. In the Event Management dialog box that is displayed, you can view the recovery time of the event in the Recovered At column on theEvents tab page. If no, the installation was not successful. On the menu bar, choose Event >Event Management . In the Event Management dialog box that is displayed, click theEvents tab page and double-click the entry that you want to view. Handle the fault according to the troubleshooting suggestions provided by the Details dialog box that is displayed. If the fault persists, contact technical support. ----End

12.4.3 Replacing a Disk Removing a Disk

Issue 01 (2014-01-16) m~

=

OOQ


224



Procedure Step 1 Wear an ESD wrist strap, ESD gloves, and ESD clothing. Step 2 Press the latch on the disk handle in the direction of the arrow, as shown in step 1 in the above figure.

Step 3 Open the handle and remove the disk, as shown in step 2 in the above figure. Step 4 Put the removed disk module into an ESD bag. Step 5 Wait for 1 minute. Log in to the ISM, choose Event >Event Management on the menu bar. Check whether an event indicating that the disk module has been removed is displayed on the Events tab page. Q&A

What types of disks does the S5500T support? What are their major differences? How are the different types of disks connected to the backplane of an S5500T controller enclosure? ----End

Installing a Disk Step 1 Read the safety precautions carefully. Step 2 Insert the new disk into the vacant slot, as shown in step 1 in the following figure. Step 3 Close the disk handle, as shown in step 2 in the following figure. If the disk Running indicator blinks when the disk is starting, data is being migrated to the disk.

Issue 01 (2014-01-16)


225 m~

=

OOR



Check whether the installation is successful by observing the disk Running indicator and Alarm indicator. If the Running indicator is on and the Alarm indicator is off, the disk is successfully installed. If the disk Alarm indicator is on, the disk is incorrectly installed. In this case, remove the disk and wait 1 minute before reinserting. If the disk Alarm indicator remains on, the disk is defective. Replace the defective disk with a new one.

Wait 1 minute. Log in to the ISM, and click Device Info in the navigation tree. Check whether the status of each component is normal. 

If yes, the installation is complete. On the menu bar, choose Event >Event Management . In the Event Management dialog box that is displayed, you can view the recovery time of the event in the Recovered At column on theEvents tab page.



If no, the installation fails. On the menu bar, choose Event >Event Management . In the Event Management dialog box that is displayed, click theEvents tab page and double-click the entry that you want to view. Handle the fault according to the troubleshooting suggestions provided by the Details dialog box that is displayed. If the fault persists, contact technical support.

Issue 01 (2014-01-16) m~

=

OOS


226



12.4.4 Replacing a Power Module Removing a Power Module

Step 1 Wear an ESD wrist strap, ESD gloves, and ESD clothing. Step 2 Disconnect the power cable from the power module to be removed. Step 3 Press the latch on the power module handle in the direction of the arrow, hold the handle, and remove the power module, as shown in the above figure. ----End

Installing a Power Module Step 1 Read the safety precautions carefully.

Issue 01 (2014-01-16)


227 m~

=

OOT



Step 2 Take the new power module out of its ESD bag. Step 3 Insert the new power module into the vacant slot, as shown in the following figure. Step 4 Connect the power cable to the power module.

Observe the power Running/Alarm indicator to determine whether the installation succeeded. 

If the power Running/Alarm indicator is steady green, the installation is successful.



If the power Running/Alarm indicator is off or steady orange, the power module is incorrectly installed. In this case, remove and reinsert the power module. Wait 1 minute. Log in to the ISM, and click Device Info in the navigation tree. Check whether the status of each component is normal.



If yes, the installation is complete.



If no, view fault information on the ISM.

----End

Issue 01 (2014-01-16) m

OOU


228



12.4.5 Replacing a Fan-BBU Module Removing a Fan-BBU Module Figure 12-1 Removing a fan-BBU module of the S5500T

Step 1 Wear an ESD wrist strap, ESD gloves, and ESD clothing. Step 2 Press the latch on the fan module handle in the direction of the arrow, hold the handle, and remove the fan module, as shown in the above figure. ----End

Installing a Fan-BBU Module Step 1 Take the new fan module out of its ESD bag. Step 2 Insert the new fan module into the vacant slot, as shown in the following figure.

Issue 01 (2014-01-16)


229 m~

=

OOV



Observe the fan Running/Alarm indicator and determine whether the installation is successful. 

If the fan Running/Alarm indicator is steady green, the installation is successful.



If the fan Running/Alarm indicator is off or steady red, the fan module is incorrectly installed. In this case, remove and reinsert the fan module. Wait 1 minute. Log in to the ISM, and choose Device Info >Storage Unit > Controllers in the navigation tree. Check whether the status of each component is normal.



If yes, the installation is complete.



If no, view fault information on the ISM.

After a parts replacement is completed, verify that the services are normal and export configuration data again. ----End

Issue 01 (2014-01-16) m

OPM


230



12.5 Questions What should be done after the parts replacement is completed?

Issue 01 (2014-01-16)


231 m~

=

OPN


13

13 Upgrade Lab of SAN Storage Products

Upgrade Lab of SAN Storage Products

13.1 Objectives Upon completing this lab, you will have a working knowledge of the procedure involved in upgrading storage products.

13.2 Devices S2600T or S5500T, IP switch, maintenance terminal, network cable

13.3 Networking Diagram 13.4 Procedure 13.4.1 Obtaining the Latest Version of Software Step 1 Log in to www.huawei.com.

Step 2 Download the latest version of software. Step 3 Verify the upgrade package.

Issue 01 (2014-01-16) m~

=

OPO


232



----End

13.4.2 Preparing to Upgrade a Controller Check Time

Check Item

One week before the upgrade

Obtain upgrade reference documents Obtain upgrade software and tools Obtain the license file of the new version

Three days before the upgrade

Query system information Check the running status of the device

13.4.3 Backing Up Data For details, see section 11.4.1 " Exporting Configuration Data of the Storage Device Using the DeviceManager "

Issue 01 (2014-01-16)


233 m~

=

OPP



Make sure that you have exported configuration data before the upgrade.

Make sure that you have exported the latest configuration data after the upgrade.

13.4.4 Stopping Host Services 1.

Stop host applications.

2.

Stop databases. In Windows or Linux operating systems, you can run shutdown normal in SQLPlus to stop Oracle database services. If no application is running, you can run shutdown immediate.

3.

Stop the file system. Windows file system Copy the sync.exe application program to the C:\ root directory on the host. The program is downloaded from the Microsoft website. It is compatible with all versions of the Windows operating system. Go to the Command Prompt window and runcd \ to move into the directory containing sync.exe. Enter sync.exe to write memory data to disks. To write data to a specific disk, run sync.exe –r drive letter , for example, sync.exe –r F . Linux file system Run umount to unmount the corresponding web disk.

4.

Disable automatic startup.

5.

Disconnect the host from the storage device. Verify that the host services are stopped. Remove the cable between the host and the storage device.

13.4.5 Upgrading a Controller Using Toolkit Step 1 Start the OceanStor Toolkit. Step 2 Click Upgrade to go to the Upgrade tab page.

Issue 01 (2014-01-16) m~

=

OPQ


234



Step 3 Click Upgrade

.

Step 4 Click Add Device to add the device which you want to upgrade.

Issue 01 (2014-01-16)


235 m~

=

OPR



Step 5 Click Add Device .

Issue 01 (2014-01-16) m~

=

OPS


236



Step 6 Enter the device IP address which you want to upgrade. Step 7 Click Next.

Issue 01 (2014-01-16)


237 m~

=

OPT



Step 8 Enter the username and password of the device. Step 9 Click Finish.

Issue 01 (2014-01-16) m~

=

OPU


238



Step 10 Click Next.

Step 11 Click Browse under Select Upgrade Package. Choose the device upgrade package files.

Issue 01 (2014-01-16)


239 m~

=

OPV

HCNA-Storage Building the Structureof Storage Network Lab Guide V2.1

Recommend Documents