HP StorageWorks EVA iSCSI connectivity user guide Part number: 5697-7577 Tenth edition: July 2008
Legal and notice information © Copyright 2006-2008 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice. The only warranties for HP products and services are set forth in the express warranty statements accompanying such products and services. Nothing herein should be construed as constituting an additional warranty. HP shall not be liable for technical or editorial errors or omissions contained herein.
Contents About this guide . . . . . . . . . . . . . . . . . . . . . . . . . . Overview . . . . . . . . . . . Intended audience . . . . . Related documentation . . . Document conventions and symbols Rack stability . . . . . . . . . HP technical support . . . . . . Subscription service . . . . . . Other HP websites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Features not supported for iSCSI hosts . . . . . . Fibre Channel switch/fabric rules and guidelines . . . . . HP Command View EVA management rules and guidelines Supported IP network adapters . . . . . . . . . . . . IP network requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Connecting the mpx100/100b to AC power . . . . . . . . . . . . . . . . . . . . . . . . Starting and configuring the mpx100/100b . . . . . . . . . . . . . . . . . . . . . . . . Starting HP StorageWorks mpx Manager for Windows . . . . . . . . . . . . . . . . . Starting HP StorageWorks mpx Manager for Linux . . . . . . . . . . . . . . . . . . . Configuring the mpx100/100b . . . . . . . . . . . . . . . . . . . . . . . . . . .
Microsoft MPIO multipathing support for iSCSI . . . . . . . . . . Installing the MPIO feature for Windows Server 2008 . . . . . Installing the MPIO feature for Windows Server 2003 . . . . . Load balancing features of Microsoft MPIO for iSCSI . . . . . Microsoft MPIO with QLogic iSCSI HBA . . . . . . . . . . . Configuring multipath with the VMware iSCSI Initiator . . . . . . . . . Native multipathing solution for iSCSI . . . . . . . . . . . . . . Setting up multipath configurations . . . . . . . . . . . . .
Command line interface for the mpx100/100b . . . . . . . mpx100/100b log-on, user accounts, and backup and restore Logging on to a SAN mpx100/100b . . . . . . . . . User accounts . . . . . . . . . . . . . . . . . . . Backup and restore . . . . . . . . . . . . . . . . Commands . . . . . . . . . . . . . . . . . . . . Admin command . . . . . . . . . . . . . . . Beacon command . . . . . . . . . . . . . . . Date command . . . . . . . . . . . . . . . . Clear command . . . . . . . . . . . . . . . . FRU command . .
Chassis diagnostics . . . . . . . . . . . . . . . . . . . . . . Input Power LED is extinguished . . . . . . . . . . . . . . . System Alert LED is illuminated . . . . . . . . . . . . . . . . Power-on self-test diagnostics . . . . . . . . . . . . . . . . Heartbeat LED blink patterns . . . . . . . . . . . . . . mpx100/100b log data . . . . . . . . . . . . . . . . . . The mpx100/100b statistics . . . . . . . . . . . . . . . . . Troubleshooting LUN presentation from the EVA to the iSCSI Initiator . .
qsrFcPortIndex . . . . . . qsrFcPortNodeWwn . . . qsrFcPortWwn . . . . . . qsrFcPortId . . . . . . . qsrFcPortType . . . . . . qsrFcLinkStatus . . . . . qsrFcLinkRate . . . . . . Sensor table . . . . . . . . qsrSensorTable . . . . . qsrSensorEntry . . . . . qsrSensorType . . . . . . qsrSensorIndex . . . . . qsrSensorUnits . . . . . qsrSensorValue . . . . . qsrUpperThreshold . . . . qsrLowerThreshold . . . . qsrSensorState . . . . . Notifications . . . . . . . . . . Notification objects . . . . .
Cables . . . . . . . . . . . . . . . Regulatory compliance identification numbers Laser device . . . . . . . . . . . . . . Laser safety warning . . . . . . . . . Laser product label . . . . . . . . . . International notices and statements . . . . Canadian notice (avis Canadien) . . . Class A equipment . . . . . . . . . . European Union notice . . . . . . . . BSMI notice . . . . . . . . . . . . . Japanese notice . . . . . . . . . . . Korean notices . . . . . . . . . . . Safety . . . . . . . . . . . . . . . .
Figures 1 Direct connect iSCSI-Fibre Channel attachment mode configuration . . . . . . . . . . . 22 2 EVA4400 direct connect iSCSI-Fibre Channel attachment mode configuration . . . . . . 23 3 HP Command View EVA deployment configuration 1 . . . . . . . . . . . . . . . . . 23 4 HP Command View EVA deployment configuration 2 . . . . . . . . . . . . . . . . . 24 5 EVA8x00 mpx100 and Windows host direct-connect only . . . . . . . . . . . . . . 24 6 Fabric iSCSI-Fibre Channel attachment mode . . . .
35 Target login . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77 36 Connected Targets tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77 37 Configuration tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87 38 Security profile information . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87 39 General properties dialog box . . . . . . . . . . . . . . . . . . . . . . . . . . 88 40 Add send targets server dialog box . . . . . . . . . . .
73 System error blink pattern . . . . . . . . . . . . . . . . . . . . . . . . . . . . 174 74 Port IP address conflict blink pattern . . . . . . . . . . . . . . . . . . . . . . . . 175 75 Over-temperature blink pattern . . . . . . . . . . . . . . . . . . . . . . . . . . 175 76 Class 1 laser product label . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Tables 1 Document conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18 2 iSCSI Fibre Channel attachment option part numbers . . . . . . . . . . . . . . . . . 21 3 Connectivity attachment mode supported . . . . . . . . . . . . . . . . . . . . . . 25 4 Multipathing software requirements . . . . . . . . . . . . . . . . . . . . . . . . 26 5 Supported mpx100 maximums . . . . . . . . . . . . . . . . . . . . . . . . . . 29 6 Operating systems . . . . . . . . . . . . . . . . . . . .
34 CHAP single direction settings . . . . . . . . . . . . . . . . . . . . . . . . . . 205 35 CHAP single and bidirectional settings . . . . . . . . . . . . . . . . . . . . . . . 207 36 CHAP bidirectional and single settings . . . . . . . . . . . . . . . . . . . . . . . 209 37 CHAP bidirectional and bidirectional settings . . . . . . . . . . . . . . . . . . . .
About this guide This user guide provides information to help you: • • • • • • Install the Enterprise Virtual Array (EVA) or EVA4400 iSCSI connectivity option Install an additional EVA or EVA4400 iSCSI connectivity option for high availability Configure EVA or EVA4400 iSCSI connectivity multipath software Install software initiators for different operating systems Configure EVA iSCSI LUNs using HP Command View EVA Configure the mpx100 or mpx100b This section contains the following topics: • • • • • Overv
Document conventions and symbols Table 1 provides the conventions and symbols used in this document. Table 1 Document conventions Convention Element Blue text: Table 1 Cross-reference links and e-mail addresses Blue, underlined text: http://www.hp.
WARNING! To • • • • • reduce the risk of personal injury or damage to equipment: Extend leveling jacks to the floor. Ensure that the full weight of the rack rests on the leveling jacks. Install stabilizing feet on the rack. In multiple-rack installations, fasten racks together securely. Extend only one rack component at a time. Racks can become unstable if more than one component is extended.
About this guide
1 Overview of the EVA and EVA4400 iSCSI connectivity option This chapter contains the following topics: • EVA and EVA4400 iSCSI connectivity product description, page 21 • EVA and EVA4400 iSCSI connectivity options, page 22 • EVA and EVA4400 iSCSI connectivity hardware and software support, page 25 • Security, page 28 • Configuring HP StorageWorks Continuous Access EVA and Business Copy, page 28 EVA and EVA4400 iSCSI connectivity product description The EVA family of Fibre Channel (FC) storage systems is s
AJ714A T5471A HP StorageWorks EVA4400 iSCSI Upgrade Option (optional) HP StorageWorks EVA4400 iSCSI Connectivity 32 Initiator Upgrade License (LTU) (optional) The AJ713A connectivity option and an EVA4400 storage system to provide high availability multipath connectivity, or order separately to upgrade an existing EVA4400 with iSCSI connectivity for multipath. A redundant mpx100b hardware unit for customers who require high availability. Supports up to 16 iSCSI initiators.
Discovery IP Address Presented iSCSI Targets D1 FP1A FP1B FP1A D2 FP1B FP1A FP1B FP1A FP1B D3 D4 IP Network management (WAN/LAN) mpx100/100b 1 HP StorageWorks mpx100 mpx100/100b 2 MGMT HP StorageWorks mpx100 MGMT IOIOI FC1 FC1 FC2 FC2 GE1 MGMT MGMT IOIOI ! ! GE2 FC1 GE1 GE2 GE1 FC2 FC1 FC2 GE2 GE1 GE2 D2 D1 D4 D3 iSCSI IP Network iSCSI data (LAN/VLAN) NIC EVA4400 Storage System Command View EVA A B 26381b Figure 2 EVA4400 direct connect iSCSI-Fibre Channel attachment mod
Discovery IP Address Presented iSCSI Targets D1 FP2A FP2B FP2A D2 FP2B FP1A FP1B FP1A FP1B D3 D4 IP Network management (WAN/LAN) mpx100/100b 1 HP StorageWorks mpx100 mpx100/100b 2 MGMT HP StorageWorks mpx100 MGMT IOIOI FC1 FC1 GE1 FC2 FC2 MGMT MGMT IOIOI ! ! GE2 FC1 GE1 GE2 FC1 FC2 FC2 GE1 GE2 GE1 GE2 D2 D1 D4 IP Network iSCSI data (LAN/VLAN) D3 NIC iSCSI initiator & Command View EVA server EVA Storage System 26485a Figure 4 HP Command View EVA deployment configuration 2
Discovery IP address Presented iSCSI targets D1 FP2A IP network management (WAN/LAN) FP2B FP1A mpx100/100b* MGMT HP StorageWorks mpx100 MGMT IOIOI ! FP1B FC1 FC1 FC2 FC2 GE1 GE2 GE1 D1 EVA storage system FP1 FP2 FP1 FP2 IP network iSCSI data (LAN/VLAN) iSCSI NIC Existing Fibre Channel HA fabric 1 A B Command View EVA Existing Fibre Channel HA fabric 2 *mpx100b supported on EVA4400 only 25164b Figure 6 Fabric iSCSI-Fibre Channel attachment mode EVA and EVA4400 iSCSI connectivi
the EVA4400 embedded Fibre Channel switch. Contact an HP storage representative for the latest information about support for specific switch models. Storage systems The mpx100 is supported with the EVA4000/4100/6x00/8x00 and EVA3000/5000 storage systems. The mpx100b is supported only with the EVA4400. Software support requirements Management software requirements • HP Command View 6.0.2 or later is required to configure iSCSI LUNs. • HP Command View 8.
Figure 7 illustrates the high-availability multipath direct connect iSCSI–Fibre Channel attachment mode configuration. This configuration is used with the EVA4000/4100/6x00/8x00 using the mpx100's and with the EVA4400 using the mpx100b's.
NOTE: Dual NICs and dual IP fabrics are supported for complete redundancy. Figure 9 illustrates the high availability multipath fabric iSCSI–Fibre Channel attachment mode configuration with four iSCSI controller host ports. This configuration is used with EVA4000/4100/6x00/8x00 storage systems. Discovery IP Address Presented iSCSI Targets D1 FP1A FP1B FP2A D2 D3 D4 FP2B FP2A FP2B FP1A FP1B Note: Zoning is required to limit access to the targets shown in the table.
2 Configuration rules and guidelines This chapter discusses the rules and guidelines for the HP StorageWorks EVA and EVA4400 iSCSI connectivity option.
Description Maximum per EVA or EVA4400 iSCSI connectivity solution Total number of iSCSI LUNs 150 LUNs maximum Total number of iSCSI targets per initiator 8 (see Figure 9 on page 28) General EVA and EVA4400 iSCSI connectivity rules NOTE: The EVA iSCSI connectivity option (mpx100) is supported with EVA4000/4100/4400/6x00/8x00 and EVA3000/5000 storage systems. The EVA4400 iSCSI connectivity option (mpx100b) is supported only with EVA4400 storage systems.
Initiator rules and guidelines This section describes the following iSCSI Initiator rules and guidelines: • “iSCSI Initiator rules and guidelines” on page 31 • “VMware iSCSI Initiator rules and guidelines” on page 31 • “Windows iSCSI Initiator rules and guidelines” on page 32 • “OpenVMS iSCSI Initiator rules and guidelines” on page 33 • “Apple Mac OS X iSCSI Initiator rules and guidelines” on page 32 • “Linux iSCSI Initiator rules and guidelines” on page 32 • “Solaris iSCSI Initiator rules and guidelines” o
Windows iSCSI Initiator rules and guidelines Windows requirements • Microsoft iSCSI Initiator versions 2.06, 2.07 • TCPIP parameter Tcp1323Opts must be entered in the registry with a value of DWord=2 under the registry setting# HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters. NOTE: This parameter is automatically set by the HP StorageWorks iSCSI Connectivity Option for Enterprise Virtual Array Windows software kit. This kit is available at http://h18006.www1.hp.
• Fibre Channel LUNs and iSCSI LUNs are not supported on the same server. • NIC bonding is not supported. Does not support: • NIC bonding iSCSI Initiator operating system considerations: • Configure the Linux host mode iSCSI Initiator setting through the mpx Manager GUI, CLI or through HP Command View 6.0.2 or later. See “HP StorageWorks mpx manager for Windows” on page 57 for more information.
NOTE: Note that since V8.3-1H1 is an I64 only release, Alpha support will not be made available until the next Alpha release. • iSCSI Targets • The only supported iSCSI targets are the HP StorageWorks EVA iSCSI connectivity option (mpx100). The mpx100 provides iSCSI access to EVA-based storage. • No other iSCSI storage targets are currently supported. • NICs The platform on which the initiator is installed must contain at least one supported GbE NIC.
Table 7 EVA configuration table (mpx100/100b) EVA array Operating system Software version One mpx100 Second mpx1001 Fabric attach mpx100 Direct connect mpx100 Microsoft Windows XCS 6.100 or later, XCS 09000000 or later √ √ √ √ Apple Mac OS X XCS 6.100 or later, XCS 09000000 or later √ Not supported √ √ HP OpenVMS XCS 6.100 or later, XCS 09000000 or later (mpx100 only) √ Not supported √ √ Microsoft Windows VCS 4.001 or later √ √ √ Apple Mac OS X VCS 4.
Supported features for iSCSI hosts For HP StorageWorks Business Copy, iSCSI hosts are supported with the following basic Business Copy features: • • • • • • Snapshots of LUNs presented to iSCSI hosts Snapclones (normal or 3-phase) of LUNs presented to iSCSI hosts Instant Restore from snapclone to original source iSCSI hosts can access and write to EVA snapshots iSCSI hosts can access and write to EVA snapclones HP Command View, SSSU, or RSM can be used to create snapshots manually or automatically on a sch
HP Command View EVA management rules and guidelines The following rules and guidelines for HP Command View EVA are applicable when using the EVA and EVA4400 iSCSI connectivity option: • Supports HP Command View EVA iSCSI connectivity (Fibre Channel switch not required). See Figure 3, Figure 4, and the HP StorageWorks Command View EVA iSCSI deployment whitepaper at: http://h71028.www7.hp.com/ERC/downloads/4AA2-0607ENA.pdf. • A maximum of two mpx100's/100b's can be discovered by an EVA storage system.
NOTE: For further information on Alacritech adapters, visit the HP Supplies and Accessories website: http://h30094.www3.hp.com/searchresults.asp?search=keyword&search_field;=description& search_criteria;=alacritech&Image1.x;=9&Image1.y;=10 NOTE: For further information on Qlogic adapters, visit www.qlogic.com. IP network requirements HP recommends the following: • • • • 38 Network protocol: TCP/IP IPv6, IPv4 Ethernet 1000 Mb/s. IP data: LAN/VLAN support with less than 10 ms latency.
3 Installing and upgrading EVA iSCSI connectivity This chapter contains information about the following topics: • Verify your system requirements, page 39 • Verify your installation type and components, page 39 • EVA and EVA4400 iSCSI connectivity installation, page 40 • Rack mount the mpx100/100b, page 43 • Connect the mpx100/100b to an IP switch, page 44 • Start the mpx100/100b, page 45 • Set the mpx100/100b management port to use HP StorageWorks Command View EVA, page 45 To install your EVA iSCSI connect
Table 11 Installation information Installation type Fibre Channel attachment mode Factory installed with the Enterprise Virtual Array (EVA) Direct connect (Figure 1 on page 22 and Figure 2 on page 23) Field upgrade iSCSI option for an existing EVA Field upgrade option for multipathing capability for an existing EVA with an iSCSI option1 Fabric (Figure 6 on page 25) Direct connect (Figure 1 on page 22 and Figure 2 on page 23) Fabric (Figure 6 on page 25) Direct connect (Figure 7 on page 27) Fabric (Figu
To install the HP StorageWorks EVA or EVA4400 iSCSI option, select the appropriate installation procedure: • Fabric attach—Reconfigure the factory-installed EVA or EVA4400 iSCSI connectivity option to fabric attachment mode • Field direct connect—HP StorageWorks EVA or EVA4400 iSCSI connectivity option with direct connect attachment mode • Field direct connect—HP StorageWorks EVA or EVA4400 iSCSI connectivity option with direct connect attachment mode • Multipath direct connect—HP StorageWorks EVA or EVA440
Field direct connect—HP StorageWorks EVA or EVA4400 iSCSI connectivity option with direct connect attachment mode Figure 1 illustrates the direct connect iSCSI–Fibre Channel attachment mode configuration. NOTE: This option is supported only on the EVA4400 running XCS 9.000 or later firmware, or EVA4x00/6x00/8x00 running XCS 5.100 or later firmware. To install field direct connect with direct connect attachment mode: 1. Rack mount the mpx100/100b. (See “Rack mount the mpx100/100b” on page 43.) 2.
4. Connect one end of the orange Fibre Channel cable to the FC2 SFP port of the mpx100/100b. Connect the other end of the orange Fibre Channel cable to any available SFP port on the Fibre Channel switch. 5. Connect one end of the orange Fibre Channel cable to any available SFP port on the Fibre Channel switch. Connect the other end of the orange Fibre Channel cable to an available FP port on the top HSV controller. 6.
c. Place the nut plate outside the right-hand slide bracket with the dimpled threaded holes pointing outboard. d. Place two screws (10-32 Pan 0.625 XRCS) through the two holes at the back of the C-Shelf, through the slide plate slots, and loosely into the front two threaded holes of the nut plate. e. Repeat with the opposite hand slide bracket. 2. Install the C-Shelf assembly into the rack. a. Locate a clear 1U area space within the rack.
Starting the mpx100/100b To start the mpx100/100b: 1. Attach the AC power cord to the mpx100/100b and the power distribution unit (PDU). Verify that the mpx100’s/100b's System Power LED is illuminated. The mpx100/100b runs a self-test and begins normal operation. 2. Verify that the Heartbeat LED is blinking (once per second) and that the Input Fault LED is not illuminated. Figure 10 shows the location of the ports and LEDs on the mpx100/100b.
NOTE: Changes to the management port using the set mgmt command are effective immediately. Communications may be lost if Telnet was used to log in to the mpx100/100b. 5. Start HP Command View EVA and select the iSCSI Devices folder under the Hardware folder in the HP StorageWorks Command View EVA window. 6. Click Discover iSCSI Devices (Figure 11). If the iSCSI device is not discovered, click Add iSCSI Device, enter the mpx100/100b IP address, and then click OK. Figure 11 Discover iSCSI devices 7.
Figure 12 Hardware/iSCSI devices 8. Enter the IP address and subnet mask for Port 1 on the IP Ports tab, and then click Save changes.
Installing and upgrading EVA iSCSI connectivity
4 Configuring the mpx100/100b This chapter contains the following major sections: • General description, page 49 • Installation and maintenance, page 55 General description of the mpx100/100b The mpx100/100b The mpx100 serves as the data transport between iSCSI hosts and the EVA storage system (see Figure 13). The mpx100/100b connects to iSCSI hosts through IP connections, and to an EVA storage system directly through FC ports or FC switch ports.
1 2 3 25264a Figure 14 Chassis LEDs 1. Heartbeat LED 2. Input Power LED 3. System Fault LED Power LED (green) The Power LED indicates the input voltage status at the mpx100/100b logic circuit board. During normal operation, this LED is illuminated to indicate that the mpx100/100b logic circuit board is receiving the DC voltage from the power supply. Heartbeat LED (green) The Heartbeat LED indicates the status of the internal mpx100/100b processor and any power-on self test (POST) error results.
Figure 15 Chassis controls Maintenance button The Maintenance button is a multifunction momentary switch on the front panel. It provides the following functions: • • • • • Reset Select boot image Reset IP address Enable DHCP Factory defaults Resetting the mpx100/100b To reset the mpx100/100b, use a pointed nonmetallic tool to briefly press and release (less than two seconds) the Maintenance button. The mpx100/100b responds as follows: 1. All the chassis LEDs are illuminated. 2.
Resetting to factory default configuration To reset the mpx100/100b and restore it to the factory default configuration (that is, to reset passwords, maintenance port IP address 10.0.0.1, iSCSI ports disabled with no IP address, erase presentations, erase discovered initiators and targets), use a pointed nonmetallic tool to briefly press the Maintenance button. Release the button after twenty seconds (observe twenty flashes of the Heartbeat LED). The mpx100/100b boots and is restored to factory defaults.
Table 13 Port LED messages Activity Amber LED Green LED Yellow LED Power off OFF OFF OFF Power on (before F/W Initialization) ON ON ON On-Line link established at 1-Gbps OFF 3 seconds on—Flash off once OFF Activity at 1-Gbps ON 3 seconds on—Flash off once OFF On-Line Link established at 2-Gbps OFF 3 seconds on—Flash off twice OFF Activity at 2-Gbps ON 3 seconds on—Flash off twice OFF Power on (after FW initialization and/or loss of synchronization) OFF ON ON Firmware error E
Activity LED (green) The Activity LED illuminates when data is being transmitted or received over the Ethernet connection. Link Status LED (green) The Link Status LED illuminates continuously when an Ethernet connection has been established. Management Ethernet port The management Ethernet port shown in Figure 18 is an RJ-45 connector. It provides a connection to a management server through a 10/100 Base-T Ethernet cable. The port is labeled MGMT.
Table 14 Serial port pin definition Dongle DB9 pin number mpx100/100b RJ–45 pin number nl Description 1 5 Data carrier detect (DCD) 2 6 Receive data (RxD) 3 3 Transmit data (TxD) 4 2&7 Data terminal ready (DTR) 5 4 Signal ground (GND) 6 5 Data set ready (DSR) 7 1 Request to send (RTS) 8 8 Clear to send (CTS) 9 N/C Ring indicator (RI) Installation and maintenance This section describes how to install and configure the mpx100/100b.
If you plan to use HP StorageWorks mpx Manager to manage the mpx100/100b, see “Install the management application” on page 56. Setting the server IP address The IP address of a new mpx100/100b is 10.0.0.1\255.0.0.0. To ensure that your server is configured to communicate with the 10.0.0 subnet, see the following instructions for your server. To set the server address for a Windows server: 1. Select Start > Settings > Control Panel > Network and Dial-up Connections. 2. Select Make New Connection. 3.
Option for Enterprise Virtual Arrays software kit. The Linux kit is provided in .tar.gz format and the Windows kit is provided as a CD image (.iso file or .zip file). The kits are available at: http://h18006.www1.hp.com/products/storageworks/evaiscsiconnect/index.html. Table 15 lists the requirements for the management servers running HP StorageWorks mpx Manager. NOTE: For Windows, you can write the .iso file to a CD-ROM or copy the .zip file to a folder.
HP StorageWorks mpx Manager for Linux This section describes how to install HP StorageWorks mpx Manager on a Linux server. NOTE: In the following procedure, replace n.n.nn and n.nnbnn with a file names (for example, 2.0.65 and 2.65b85). 1. Download the hpmpx_n.n.nn_linux_install.tar.gz file from http:// h18006.www1.hp.com/products/storageworks/evaiscsiconnect/. The .gz file contains the GUI.bin file and a GUI install README file. nl 2. Unpack the file to a temporary directory.
A typical mpx Manager is displayed (Figure 21). Figure 20 Connect to the mpx100/100b Figure 21 Typical mpx Manager display Starting HP StorageWorks mpx Manager for Linux To start HP StorageWorks mpx Manager for Linux: 1.
nl ./HPmpx100Manager. The Connect to the mpx100/100b window is displayed (Figure 20 on page 59). 2. Enter the host name or IP address of the management port of the mpx100/100b. 3. Click Connect to display the selected HP mpx Manager. A typical mpx Manager is displayed (Figure 21 on page 59). nl nl Configuring the mpx100/100b You can configure the mpx100/100b using the HP StorageWorks mpx Manager application or the CLI. To configure the mpx100/100b using the CLI: 1.
3. Enter a unique name in the Symbolic Name box. NOTE: The Symbolic Name syntax must follow the iSCSI standard for iqn naming. Only the following ASCII characters (U+0000 to U+007F), are allowed: • • • • • ASCII ASCII ASCII ASCII ASCII dash character (-) = U+002d dot character (.) = U+002e colon character (:) = U+003a lower-case characters (a through z) = U+0061 through U+007a digit characters (0 through 9) = U+0030 through U+0039 See section 3.2.
System Symbolic Name (Max = 64 characters) [ ] MPX100-65 Embed Symbolic Name (0=Enable,1=Disable) [Disabled ] System Log Level (Min = 0, Max = 3) [0 ] NOTE: The Symbolic Name syntax must follow the iSCSI standard for IQN naming. Only the following ASCII characters (U+0000 to U+007F), are allowed: • • • • • ASCII ASCII ASCII ASCII ASCII dash character (-) = U+002d dot character (.
WARNING! Installing and then activating the new firmware is disruptive. For activation, you must reboot the mpx100/100b. However, the reboot can result in incorrect data being transferred between devices connected to the mpx100/100b. HP recommends suspending activity on the interfaces before activating firmware. For the latest mpx100/100b firmware, go to the HP website: http://h18006.www1.hp.com/products/storageworks/evaiscsiconnect/index.html.
Configuring the mpx100/100b
5 Setting up the iSCSI Initiator and storage This chapter contains the following topics: • • • • • • • • • iSCSI initiator setup, page 65 iSCSI initiator setup for Windows (single-path), page 65 Storage setup for Windows (single-path) About Microsoft Windows server 2003 scalable networking pack iSCSI Initiator version 3.
NOTE: The terms initiator and host are used interchangeably. The initiator is the host that is accessing the storage. e. Click the Discovery tab, (Figure 22). Figure 22 Adding an IP address f. Click Add to add the IP address of Port 1 on the mpx100/100b. g. Click OK to exit. h. Click the Targets tab. The target status is Inactive (Figure 23). nl Figure 23 Inactive target status i. j. 66 Select a single target and then click Log On.
Figure 24 Connected target status NOTE: Each target represents a path to the EVA. Logging into multiple targets may inadvertently present the same LUN multiple times to the operating system. Storage setup for Windows (single-path) To set up LUNs using HP Command View: 1. Set up LUNs using HP Command View. See Using HP Command View EVA to configure LUNs to iSCSI initiators, page 129. 2. Set up the iSCSI drive on the iSCSI Initiator: a. Open the Windows Computer Management window. b. Select Disk Management.
2. Download the SNP package from the Microsoft website: http://support.microsoft.com/kb/912222. a. To start the installation immediately click Run, or b. To copy the download to your computer for installation at a later time, click Save. A reboot is required after successful installation. 3.
Figure 25 Discover targets b. Add the static IP address of the mpx iSCSI port in the Address field and then select Finish (Figure 26). Figure 26 Add static IP address c. Select a target from the Discovered Target list and then click Add (Figure 27).
Figure 27 Discovered target list NOTE: The mpx iSCSI port may present several iSCSI targets to the Xtend SAN iSCSI Initiator. Select only one target from the list. 3. For iSNS discovery: a. Select Initiator and then enter the iSNS name or IP address in the iSNS Address field (Figure 28).
Figure 28 iSNS discovery and verification b. Test the connection from the initiator to the iSNS server by selecting Verify iSNS. If successful, select Save. If necessary, working on the iSNS server, make the appropriate edits to add the Xtend SAN iSCSI Initiator to any iSNS discovery domains that include mpx iSCSI targets. c. Select Discover Targets. d. Select Discover by iSNS. A list of mpx targets appears under Discovered Targets (Figure 29).
Figure 29 Discovered targets NOTE: The mpx iSCSI port may present several iSCSI targets to the Xtend SAN iSCSI Initiator. Select only one target from the list. e. Select the newly-added target under Host name in the left frame. f. Check the Visible box (Figure 30). This allows the initiator to display the target status. g. Check the Auto Login box. This configures the iSCSI Initiator to automatically log in to the iSCSI target at system startup. h. 72 Click Save.
Figure 30 Selecting newly added target i. Select Status, select Network Node, and then select Login to connect to the mpx target (Figure 31). The Network Node displays a status of Connected and the target status light turns green.
Figure 31 Select status Storage setup for Apple Mac OS X 1. Present LUNs using HP Command View EVA. See Using HP Command View EVA to configure LUNs to iSCSI initiators, page 129. 2. Verify that the EVA LUNs are presented to the Macintosh iSCSI Initiator: a. Open the Xtend SAN iSCSI application. b. Select the mpx100b target entry under the host name. c. Click the LUNs button. A list of presented EVA LUNs is displayed (Figure 32).
Figure 32 Presented EVA LUNs NOTE: If no LUNs appear in the list, log out and then log in again to the target, or a system reboot may be required. 3. Set up the iSCSI drive on the iSCSI Initiator: a. Open Disk Utilities from the Apple Max OS X Finder Applications list. b. Format and partition the EVA LUN as needed.
Figure 33 Configure initiator and targets 3. Click the Discovered Targets tab and enter your iSCSI target IP address (Figure 34). Figure 34 Discovered Targets tab 4.
Log in to the target (Figure 35).Figure 35 Target login 5. Click the Connected Targets tab, and then click the Toggle Start-Up button on each target listed so the targets start automatically (Figure 36). Figure 36 Connected Targets tab Installing and configuring for Red Hat 5 To install and configure for Red Hat 5: NOTE: The iSCSI driver package is included but is not installed by default. Install the package named iscsi-initiator-utils-6.2.0.742-0.5.e15 during or after operating system installation.
1. Use the iscsiadm command to control discovery and connectivity: # iscsiadm –m discovery –t st –p 10.6.0.33:3260 2. Edit the initiator name: # vi /etc/iscsi/initiatorname.iscsi 3. To start the iSCSI service use the service command: # service iscsi start 4. Verify that the iSCSI service autostarts: #chkconfig iscsi on NOTE: For more detail, see the man pages regarding the iscsiadm open-iscsi administration utility.
NOTE: The Linux driver supports both Red Hat 3 and SUSE 8. See the Readme file in the tar ball for more information on how to configure the Linux iSCSI Initiator. Installing the iSCSI driver In a newly installed Red Hat Linux kernel, an iSCSI instance may be running. Before installing the iSCSI driver, you must stop the instance. To stop the instance: 1. Run setup. 2. Deselect iSCSI. 3. Reboot the system. See the Readme file in the tar ball for more information on configuring the iSCSI Initiator.
NOTE: These symbolic links exist regardless of the number of disk partitions. Opening the partition devices results in an error if the partition does not actually exist on the disk. • The symbolic link mt maps to the auto-rewind SCSI tape device node for the LUN /dev/st0, for example. Additional links for mtl, mtm, and mta map to the other auto-rewind devices /dev/st0l, /dev/st0m, /dev/st0a, regardless of whether these device nodes actually exist or could be opened.
Mapping inconsistencies can occur between SCSI device nodes and iSCSI targets, such as mounting the wrong device due to device name changes resulting from iSCSI target configuration changes or network delays. Instead of directly mounting SCSI devices, HP recommends one of the following options: • Mount the /dev/iscsi tree symlinks. • Mount file system UUIDs or labels (see man pages for mke2fs, mount, and fstab). • Use logical volume management (see Linux LVM).
LUN 0 can be prevented from being sent to the Solaris iSCSI Initiator by disabling the Controller LUN AutoMap parameter with the mpx system settings. LUN 0 is not presented to any host entry in HP Command View 8.0 with any iSCSI host mode setting of Solaris. Disabling Controller LUN AutoMap using the mpx CLI To disable Controller LUN AutoMap using the CLI: 1. Use Telnet to connect to the mpx management port or connect to the mpx serial port using the HP-supplied connector.
1. Become a superuser. 2. Verify that the iSCSI software packages are installed: # pkginfo SUNWiscsiu SUNWiscsir system SUNWiscsiu Sun iSCSI Device Driver (root) system SUNWiscsir Sun iSCSI Management Utilities (usr) 3. Verify that you are running a Solaris 10 1/06 or later release. 4. Confirm that your TCP/IP network is set up. Configure for EVA iSCSI target discovery This procedure assumes that you are logged in to the local system where you want to configure access to an iSCSI target device.
NOTE: The iSCSI connection is not initiated until the discovery method is enabled. For more details on using the iscsiadm command, see the #man iscsiadm man pages. For more details on iSCSI Initiator setup, see Sun Microsystems System Administration Guide, Devices and File Systems, Section 15.
Please select a Target from the list above ('q' to quit): 0 LUN Vendor — ——— — 0 HP 1 HP 2 HP 3 HP 4 HP . . . Please select a LUN from the list above ('q' to quit): 0 Index Initiator — ——– 0 iqn.2005-03.com:sanlabmac-s01 1 iqn.1986-03.com.sun:rack81-s16 2 iqn.1991-05.com.microsoft:rack77-s16.sanbox.com 3 iqn.1991-05.com.microsoft:rack77-s14.sanbox.com 4 iqn.1996-04.de.SUSE:bl7-04.sanbox.com 5 iqn.1996-04.de.SUSE:bl7-03.sanbox.com 6 iqn.1996-04.de.SUSE:bl7-02.sanbox.com . . .
/pci@8,600000/SUNW,qlc@4/fp@0,0/ssd@w500000e0106e3ba1,0 2. c3t0d0 /iscsi/disk@0000iqn.2001-05.com.abcstorage%3A6-8a0900-477d70401b0fff044352423a2-hostname-020000,0 3. c3t1d0 /iscsi/disk@0000iqn.2001-05.com.abcstorage%3A6-8a0900-3fcd70401 -085ff04434f423a2-hostname-010000,0 . . .
Figure 37 Configuration tab 3. Open a firewall port by enabling the iSCSI software client service. a. Using VMware’s VI client, select the server. b. Click the Configuration tab, and then click Security Profile. c. Select the check box for iSCSI service to enable iSCSI traffic. d. Click OK (Figure 38). Figure 38 Security profile information 4.
Enable the iSCSI software initiators: a. In VMware’s VI client, select the server from the inventory panel. b.c. Under iSCSI software Adapter, choose the available software initiator. d. Click the Properties link of the software adapter. e. The iSCSI initator propeties dialog box is displayed. Click Configure. f. The General properties dialog box displays (Figure 39). Select the Enabled checkbox . Figure 39 General properties dialog box g. Click OK. 5. Set up Discovery Addressing for the software initiator: a. Repeat Step 4 to open the iSCSI initiator Properties dialog box. b. Click the Dynamic Discovery tab.
8. To verify that the LUNs are presented to the VMware host: a. Rescan for new iSCSI LUNs. b. In VMware’s VI client, select a server and click the Configuration tab. c. Choose Storage Adapters in the hardware panel and click Rescan above the Storage Adapters panel. The Rescan dialog box displays; see Figure 41. d. Select the Scan for New Storage Devices and the Scan for New VMFS Volumes checkboxes. e. Click OK. The LUNs are now available for ESX server.
Configuring TCP/IP services Before you start the iSCSI Initiator, TCP/IP must be properly configured and enabled. The initiator will only function with the TCP/IP stack provided by HP TCP/IP Services for OpenVMS. Only the basic TCP/IP core functionality needs to be configured. Note that particular attention should be paid to the system’s hostname, which is a defining element in the iSCSI Initiator name (a unique name assigned to each host running the iSCSI Initiator software).
been removed from this file will not be removed from the initiator's scan list until the system is rebooted or the initiator is stopped and restarted. NOTE: Regardless of whether IP addresses or IP names are used in the manual target data file, every iSCSI target port must be known to TCP/IP. The command TCPIP SHOW HOST can be used to determine if the target port is known to TCP/IP. The host can be added to the local TCP/IP host database with the command TCPIP SET HOST.
NOTE: Regardless whether IP addresses or IP names are used in the iSNS server data file, every iSNS server listed must be known to TCP/IP. Use the command TCPIP SHOW HOST to determine if the server is known to TCP/IP. Use the command TCPIP SET HOST to add the server to the local TCP/IP host database. A server not known to TCP/IP will not be queried by the iSCSI Initiator. NOTE: The default TCP/IP port used for iSNS traffic is 3205. This port number cannot be configured.
2. Discover and configure the iSCSI drives on the OpenVMS host using the following command: $ mcr sysman io auto/log NOTE: This step is required only if the LUNs are configured via HP Command View EVA after the initiator has been loaded. The command procedure used to load the initiator issues this command by default.
Setting up the iSCSI Initiator and storage
6 Setting up the iSCSI Initiator for multipathing This chapter contains the following topics: • • • • • • Overview, page 95 Configuring multipath with Windows iSCSI initiator, page 100 Configuring multipath with the VMware iSCSI initiator, page 112 Configuring multipath with the Solaris 10 iSCSI initiator, page 116 Configuring multipath with the OpenVMS iSCSI initiator, page 123 Device Mapper Multipath Enablement Kit for HP StorageWorks Disk Arrays, page 126 Overview The mpx100/100b supports iSCSI multipa
Figure 42 Example: Single mpx100 multipath—WWPN configuration Figure 43 Example: Dual mpx100 multipath—WWPN configuration The mpx100/100b perspective When an EVA storage system FC port connects to the mpx100/100b, the mpx100/100b creates in its database a unique iSCSI target name that includes the WWPN of the EVA storage controller port. This iSCSI target name is used by the iSCSI Initiator to connect to the EVA storage system.
Figure 44 Example: Single mpx100 multipath—iSCSI target configuration As with any other Fibre Channel host entry within HP Command View EVA, when a LUN is presented to the iSCSI host entry the LUN is presented to all mpx100/100b FC port WWPNs contained in that entry (see Figure 45). iSCSI Target Name iqn.1986-03.com.hp:fcgw.mpx100.0.500508b40101f670.500508b40101f678 50:05:08:b4:01:01:f6:78 50:05:08:b4:01:01:f6:7c iSCSI Target Name iqn.1986-03.com.hp:fcgw.mpx100.0.500508b40101f670.
50:…..f6:78 Lun 0,1,2,3 FC1 EVA FC2 50:…..f6:7c Lun 0,1,2,3 M P X 1 0 0 T=Iqn.1996…..f678 Lun 0,1,2,3 T=Iqn.1996…..f67c Lun 0,1,2,3 IP Network GE1 GE2 T=Iqn.1996…..f678 Lun 0,1,2,3 T=Iqn.1996…..f67c Lun 0,1,2,3 Figure 46 Example: Fibre Channel to IP port/target translation The iSCSI Initiator discovers the targets presented out of the mpx100/100b GE ports by discovering the GE port's IP addresses and logging in to the target (see Figure 47).
Table 16 Single mpx100/100b multipath configuration iSCSI Initiator—virtual path iqn.199601…..f678 iqn.199602…..f67c iqn.199603…..f678 iqn.199604…..f67c mpx100/100b iSCSI GbE port—physical path EVA FC port—physical path 16.10.11.02 50:05:08:b4:01:01:f6:78 16.10.11.
The iSCSI Initiator may use all virtual paths as if they were physical paths following the rules/restrictions of the iSCSI multipath software residing on the iSCSI Initiator. The iSCSI Initiator host can have single or multiple physical connections or links to the IP storage network. With a single physical connection, the iSCSI virtual paths can share the same link, because IP packets with their TCP/iSCSI payloads are routed via the IP packet network addressing information.
Figure 49 Add Features page After the server reboots, add support for iSCSI Devices using the MPIO applet (see Figure 50).
Figure 50 MPIO Properties page Installing the MPIO feature for Windows Server 2003 For Windows Server 2003, if you are installing the initiator for the first time, check all the installation option checkboxes and then click Next to continue (Figure 51). To add or remove specific MS iSCSI software Initiator components after the initial install, run the setup package executable and select the check box to add MPIO. The application automatically checks the boxes for components that are already installed.
Figure 51 Software update installation wizard Start the iSCSI Initiator from the Start > All Programs menu. At the Discovery tab, add the mpx100/100b iSCSI port IP addresses that will serve storage to this server. Note that depending on the Fibre Channel and IP connections to and from the mpx100/100b and to the iSCSI Initiator, the mpx100/100b iSCSI port may have more than one target (see Figure 52). Click Next to display the Targets tab.
Figure 53 Log on to target A status of Connected indicates the iSCSI Initiator is logged into the mpx100/100b and is ready to be presented with EVA LUNs from HP Command View EVA. Setting up storage for multiple paths in Windows To set up storage for multiple paths in Windows: 1. Set up LUNs using HP Command View. See Using HP Command View EVA to configure LUNs to iSCSI initiators, page 129.
Figure 54 Computer management NOTE: After a rescan or reboot, the multipath information for the LUN can be found in the iSCSI UI. In addition, the system event log records iSCSI Initiator and path information. 2. For Microsoft MPIO, the load balance policies apply to each LUN individually. To display and modify the LUN load balance policy (see Figure 55): a. Start the MS iSCSI control panel applet. b. Select the Target tab. c. Click Details. d. Click Devices. e.
Figure 55 iSCSI Initiator properties Load balancing features of Microsoft MPIO for iSCSI The features of MS MPIO for iSCSI include: • Failover Only—No load balancing is performed. There is a single active path and the rest of the paths are standby paths. The active path is used for sending all I/O. If the active path fails, then one of the standby paths is used. When the formally active path is reconnected, it becomes active and the activated standby path returns to standby.
Microsoft MPIO with QLogic iSCSI HBA The QLogic iSCSI HBA is supported in a multipath Windows configuration that is used in conjunction with Microsoft iSCSI Initiator Services and Microsoft MPIO. Because the iSCSI driver resides onboard the QLogic iSCSI HBA it is not necessary to install the Microsoft iSCSI Initiator. Installing the QLogic iSCSI HBA Install the QLogic iSCSI HBA hardware and software following the instructions in the QLogic installation manual.
Configuring the Qlogic iSCSI HBA To configure the QLogic iSCSI HBA: 1. Start QLogic SMS either from the desktop icon or through Start/Programs and connect to localhost (see Figure 57). 2. Click Yes to start the general configuration wizard (see Figure 58).
Figure 58 Start general configuration window Adding Targets to QLogic iSCSI Initiator To add the HBA Port iSCSI targets: 1. Click the green plus sign (see Figure 59). 2. Enter the first mpx100/100b iSCSI target port IP address. Figure 59 HBA port target configuration 3. Repeat Step 1 and Step 2 for each additional mpx you want to add. 4. Click Next.
5. To enable the changes, enter the SMS password: config. 6. Select the Target Settings tab. Verify that the HBA state is Ready, Link Up and each target entry’s state is Session Active (Figure 60). Figure 60 Target settings tab Presenting LUNs to the QLogic iSCSI Initiator To present LUNs to the QLogic iSCSI Initiator: 1. Follow procedures in “Creating an iSCSI initiator host via HP Command View EVA” on page 130 to: • Create an iSCSI host entry, and • Present LUNs to the iSCSI host 2.
Figure 61 HBA iSCSI port connections 3. Use Microsoft’s iSCSI services to manage the iSCSI target login and LUN load balancing policies (see Figure 62).
Figure 62 iSCSI Initiator properties — Targets tab Configuring multipath with the VMware iSCSI Initiator Native multipathing solution for iSCSI VMware supports a native multipathing solution for iSCSI. However, the software iSCSI Initiator can run only one instance of VMkernel, hence, it is impossible to bind two different IP addresses with one VMkernel. But VMware’s support for NIC teaming solves the problem at the server level, avoiding a single NIC failure.
2. Configure the VMkernel, Service console with a dedicated virtual switch and two dedicated NICs in Teaming for iSCSI data traffic. Follow the instructions from VMware to set up NIC teaming. 3. When configuring the iSCSI software Initiator, set up the Discovery Address: a. Open the iSCSI Initiator Properties dialog box, see iSCSI initiator setup for VmWare, page 86 b. Click the Dynamic Discovery tab. c. Click Add to add a new iSCSI target. The Add Send Target Server dialog box is displayed. d.
• Most Recently Used—ESx server uses the most recent path to the disk until this path becomes unavailable. Even if the path becomes available, the host does not automatically revert back to the preferred path. • Round Robin (Experimental)—The ESX Server load balances across all available paths. WMware defines the Round Robin policy as Experimental; Round Robin, therefore, is not a supported multipathing policy. NOTE: HP recommends using Fixed (default) for EVA iSCSI connectivity.
4. Click Manage Paths to view and modify your selections. 5. Click OK. Important information about multi-initiators and VMFS clusters In a multipath environment, configure two ESX servers to view the same LUN. When presenting a LUN from HP Command View EVA, present the LUN to both initiators: • From one initiator, create a VMFS file system and mount it. By default this files system is in PUBLIC mode. • The second host also accesses the same file system created on the shared LUN.
IMPORTANT: Multi-initiators can access the same LUN in single path as well. Accessing the same LUN is not restricted to multipathing. Configuring multipath with the Solaris 10 iSCSI Initiator This section contains information about configuring multipath with the Solaris 10 iSCSI Initiator. MPxIO overview The Sun multipathing software (MPxIO) provides basic failover and load-balancing capability to HP StorageWorks EVA4x00/6x00/8x00 storage systems.
# Global mpxio-disable property: # # To globally enable MPxIO on all iscsi ports set: # mpxio-disable="no";# # To globally disable MPxIO on all iscsi ports set: # mpxio-disable="yes"; # mpxio-disable="no"; # Setting configuration settings To configure iSCSI target settings: 1. Use the iscsiadm command to add the mpx100/100b iSCSI port IP addresses: iscsiadm add discovery-address 33.33.66.
c. • User name: guest • Password: password To enable administrator privileges, enter: • admin start • config d. Issue the command: LUNmask rm e. Follow the prompts to remove the Solaris iSCSI Initiator from each iSCSI presented target. For example: > telnet 10.6.7.
. . Please select an Initiator to remove ('a' to remove all, 'q' to quit): 1 All attribute values for that have been changed will now be saved. mpx100 (admin) #> 4. Enable the SendTargetsdiscovery method: # iscsiadm modify discovery --sendtargets enable 5.
Vendor: Product: HP HSV210 OS Device Name: /dev/rdsk/c4t600508B400107271000060000C540000d0s2 LUN: 4 Vendor: Product: HP HSV210 OS Device Name: /dev/rdsk/c4t600508B400107271000060000C540000d0s2 Target: iqn.1986-03.com.hp:fcgw.mpx100:mpx10065.1.50001fe150002f70.
AVAILABLE DISK SELECTIONS: /pci@1f,4000/scsi@3/sd@0,0 1. c4t600508B400107271000060000C4A0000d0/scsi_vhci/ssd@g600508b400107271000060000c4a0000 2. c4t600508B400107271000060000C540000d0/scsi_vhci/ssd@g600508b400107271000060000c Enabling MPxIO To enable MPxIO for HP storage devices, the appropriate information for device-typescsioptions-list need to be added in the /kernel/drv/scsi_vhci.conf file.
# Verify mpath-support parameter and Target Portal Group To verify that the mpath-support parameter Asymmetric is set to no and that all paths are in one Target Portal Group, execute the mpathadm show lu command: # mpathadm show lu /dev/rdsk/c4t600508B400107271000060000C4A0000d0s2 Logical Unit: /dev/rdsk/c4t600508B400107271000060000C4A0000d0s2 mpath-support: Vendor: HP Product: HSV210 Revision: Name Type: Name: libmpscsi_vhci.
Override Path: Path State: Disabled: NA OK no Target Ports: Name: 4000002a0000,iqn.1986-03.com.hp:fcgw.mpx100:mpx100 66.0.50001fe150002f70.50001fe150002f78,0 Relative ID: 0 Name: 4000002a0000,iqn.1986-03.com.hp:fcgw.mpx100:mpx100- 66.0.50001fe150002f70.50001fe150002f7a,0 Relative ID: 0 Name: 4000002a0000,iqn.1986-03.com.hp:fcgw.mpx100:mpx100- 65.1.50001fe150002f70.
Figure 63 Typical iSCSI path description string Table 18 Typical iSCSI path description string Unit Description 1 The iSCSI ‘device’ (Note that DEA0: is the pseudo-device associated with the software-based iSCSI Initiator.
Figure 65 SHOW DEVICE/FULL Example Manual path switching At times, you may need to manually switch a device’s current path. One common reason for doing this would be to manually distribute an I/O load. To perform a manual path switch, use the following command: SET DEVICE /SWITCH /PATH=path-description-string device-name An example of the command is shown in Figure 66.
Figure 66 SET DEVICE/SWITCH/PATH Example Device Mapper Multipath Enablement Kit for HP StorageWorks Disk Arrays The HPDM Multipath software kit is an HP-released Device Mapper multipath binary, based on Device Mapper Multipath, which is included in Linux Operating System distributions, with enablement for HP StorageWorks Disk Arrays. Device Mapper is an infrastructure in the Linux kernel. It provides a generic way to create virtual layers of block devices.
http://h20000.www2.hp.com/bizsupport/TechSupport/SoftwareDescription.jsp?swItem=co-58129-1& lang=en&cc=us&idx=1&mode=4& iSCSI Initiator timeout settings for Red Hat 4 and SUSE 9 systems To define the iSCSI Initiator timeout settings for Red Hat 4 and SUSE 9 systems, move the /etc/iscsi.
Setting up the iSCSI Initiator for multipathing
7 Using HP Command View EVA to configure LUNs to iSCSI Initiators This chapter contains the following topics: • • • • Initial discovery of the mpx100 via HP Command View EVA, page 129 Creating an iSCSI initiator host via HP Command View EVA, page 130 Presenting a virtual disk to an iSCSI initiator via HP Command View EVA, page 131 Unpresenting a virtual disk to an iSCSI initiator via HP Command View EVA, page 131 HP Command View allows LUN management for iSCSI Initiators through additional screens.
NOTE: Changes must be saved before the new IP Port address is available to iSCSI Initiators. Creating an iSCSI Initiator host via HP Command View EVA To create an HP Command View host entry for an iSCSI Initiator: 1. Click Add Host under the Hosts folder. In the Add a Host screen (Figure 67) click the iSCSI radio button in the Type field. The Basic Settings screen is automatically refreshed to the iSCSI fields necessary to create an iSCSI host entry. 2. Enter the Host name.
Figure 67 Add a host for Command View EVA Presenting a virtual disk to an iSCSI Initiator via HP Command View EVA To present a virtual disk to an iSCSI Initiator: 1. Under the Virtual Disks folder select the appropriate Vdisk name. 2. Click the Presentation tab in the VDisk Properties screen. 3. Click the Present tab. HP Command View lists all host entries for both Fibre Channel hosts and iSCSI hosts. 4. Select the appropriate iSCSI host entry and click Present Vdisk.
Using HP Command View EVA to configure LUNs to iSCSI Initiators
8 iSCSI Boot from SAN iSCSI Boot from SAN allows systems to boot from EVA disks using the EVA iSCSI connectivity option in Single Path configurations only.
iSCSI option ROM Version 1.18 is the minimum required for use with the EVA iSCSI connectivity option. NOTE: For Windows, Version 2.4.2.0 is the minimum required mpx firmware. QLogic iSCSI Host Bus adapter The following sections summarize QLogic iSCSI Host Bus adapter (HBA) requirements.
IMPORTANT: Before you begin, use the F9 key to disable any other internal storage adapters. 1. 2. 3. 4. 5. 6. 7. 8. 9. 10. 11. 12. 13. 14. 15. 16. 17. 18. 19. Press Ctrl-Q to enter the Fast!UTIL program. Select the desired HBA. Select Configuration Settings. Select Host Adapter Settings. Set the Initiator IP Settings. Set the desired Initiator iSCSI Name. Press ESC. Select iSCSI Boot Settings. Set Adapter Boot Mode to Manual. Select Primary Boot Device Settings. Set the target IP address and Boot LUN.
3. 4. 5. 6. 136 Shut down the host. Use Command View to unpresent the boot LUN. Present the boot LUN again to ensure that all paths are available. Boot the host and verify the multiple paths to the boot LUN.
9 EVA4400 iSCSI Connectivity 32 Initiator Upgrade License The EVA4400 iSCSI connectivity option (mpx100b) is a licensed version of the EVA iSCSI connectivity option mpx100). The mpx100b allows storage connectivity to the EVA4400 only and licenses the number of iSCSI Initiators or hosts that can be actively mapped or connected to storage LUNs. Initially, the mpx100b supports a maximum of 16 iSCSI Initiators with LUNs mapped to them.
2. Open an admin session and enter the following commands to install the license: a. Enter admin mode: mpx100b #> admin start Password: config (default password) b. Make sure the system date is set by entering the command: mpx100b (admin) #> date The system returns today's date and the current time. For example: Thu Feb 28 16:56:00 2008 c. If the date is not set, you must set it. The format for entering the date is MMDDhhmmYYYY.
Figure 68 New license key dialog box 5. Click OK. The Add new license key complete dialog box appears (Figure 69). Figure 69 License key complete dialog box 6. Click OK. The newly-installed license key is listed (Figure 70).
Figure 70 Display installed license key 140 EVA4400 iSCSI Connectivity 32 Initiator Upgrade License
A Command line interface Command line interface for the mpx100/100b This appendix contains information about using the CLI for mpx100/100b, including the command syntax with examples. mpx100/100b log-on, user accounts, and backup and restore This section contains information about he logging on to a SAN mpx100/100b, mpx100/100b user accounts, and backing up and restoring the mpx100/100b.
• Required keyword values appear in standard font: [value]. Optional values are shown in italics: [value]. • Underlined portions of the keyword in the command format indicate the abbreviated form that can be used. For example, the Delete keyword can be abbreviated Del. The command-line completion feature makes entering and repeating commands easier. Table 20 lists the command-line completion keystrokes. Table 20 Command-line completion Keystroke Effect Tab Completes the command line.
cancel Terminates an Admin session opened by another user. Use this keyword with care because it terminates the Admin session without warning the other user and without saving pending changes. Notes Closing a Telnet window during an admin session does not release the session. In this case, you must either wait for the Admin session to time out, or use the Admin Cancel command.
Keywords [MMDDhhmmCCYY] Specifies the date. This requires an admin session. Exception: if you omit [MMDDhhmmCCYY], the current date is displayed, which does not require an admin session. Notes Network Time Protocol (NTP) must be disabled to set the time with the Date command. See “Set command” on page 152 for information about NTP.
Authority Admin session only to set Syntax fru restore save Keywords restore: The FRU restore command requires that the user first ftp the tar file containing the desired configuration to the mpx100/100b. When this command is issued, it prompts the user for the restore level. The user has the option of fully restoring the mpx100/100b configuration (all configuration parameters and LUN mappings) or restoring only the LUN mappings.
Authority Syntax help Example The following is an example of the help command: mpx100 (admin) #> help mpx100 #> help admin [ begin | end | start | stop | cancel ] beacon [ on | off ] date [ ] clear [ logs | stats ] fru [ restore | save ] history image [ cleanup | list | unpack ] image cleanup image list image unpack [ ] initiator [ add | mod | rm ] logout lunmask [ add | rm ] passwd ping quit reboot reset factory save [ capture | logs | traces ] set [ chap | fc | features | iscsi isns | mg
History command Displays a history of the commands the user has issued through the CLI. Authority Admin session only to set Syntax history Notes Closing a Telnet window during an admin session does not release the session. You must either wait for the admin session to time out, or use the Admin Cancel command.
Authority Admin session only to set Syntax initiator add mod remove Keywords add: Adds an initiator to the mpx100/100b database. mod: Modifies the settings of an initiator. remove: Removes an initiator. Examples The following is an example of the initiator add command: A list of attributes with formatting and current values follows. Enter a new value or simply press Enter to accept the current value.
Authority Admin session only to set Syntax LUNmask add remove EVA iSCSI connectivity user guide 149
Keywords add: Map a LUN to an initiator. The operator is prompted to select an initiator from a list of initiators, then to select a target from a list of targets and finally to select the LUN that is to be mapped from a list of LUNs for the selected target. remove: Remove the mapping of a LUN from an initiator.
Authority Admin session only to set Syntax password start (or begin) end (or stop) cancel Example The following is an example of the password command: mpx100 (admin) #> passwd Press 'q' and the Enter key to abort this command. Select password to change (0=guest, 1=admin): 1 account OLD password : ****** account NEW password (6-128 chars) : ****** please confirm account NEW password : ****** Ping command Issues a ping to a device at a specific IP Address.
Reset command Restores the mpx100/100b configuration parameters to the factory default values. All LUN mappings are deleted as is all persistent data regarding targets, LUN,s and initiators. The factory default IP addresses is restored. Authority Admin session. Syntax reset Keywords factory: Restores the mpx100/100b to its factory default configuration.
Authority Admin session only Syntax set chap fc [] features iscsi [] isns [] mgmt ntp properties system Keywords fc []: Sets FC port parameters. features: Setsfeatures. iscsi []: Sets iSCSI port parameters. isns []: Sets iSNS parameters. mgmt: Sets management port parameters. ntp: Sets NTP parameters. properties: Sets properties. system: Set system parameters.
Authority Admin session Syntax set fc [] Parameters port_num: The number of the FC port to be configured. Examples The following is an example of the set fc command: mpx100 (admin) #> set fc A list of attributes with formatting and current values will follow. Enter a new value or simply press the Enter key to accept the current value. If you wish to terminate this process before reaching the end of the list press 'q' or 'Q' and the Enter key to do so.
Authority Admin session Syntax set iscsi [] Parameters port_num: The number of the iSCSI port to be configured. Examples The following is an example of the set iscsi command: mpx100 (admin) #> set iscsi A list of attributes with formatting and current values will follow. Enter a new value or simply press the Enter key to accept the current value. If you wish to terminate this process before reaching the end of the list press 'q' or 'Q' and the Enter key to do so.
Authority Admin session Syntax set isns [] Parameters port_num: The number of the iSCSI port to be configured for iSNS. Examples The following is an example of the set isns command: mpx100 (admin) #> set isns A list of attributes with formatting and current values will follow. Enter a new value or simply press the Enter key to accept the current value. If you wish to terminate this process before reaching the end of the list press 'q' or 'Q' and the Enter key to do so.
Authority Admin session Syntax set ntp Parameters port_num: The number of the iSCSI port to be configured for iSNS. Examples The following is an example of the Set NTP command: mpx100 (admin) #> set ntp A list of attributes with formatting and current values will follow. Enter a new value or simply press the Enter key to accept the current value. If you wish to terminate this process before reaching the end of the list press 'q' or 'Q' and the Enter key to do so.
Authority Admin session Syntax set snmp Parameters trap_destinations: The number of the trap destinations to be configured for SNMP. The following is an example of the set snmp command: Examples mpx100 (admin) #> set snmp A list of attributes with formatting and current values will follow. Enter a new value or simply press the Enter key to accept the current value. If you wish to terminate this process before reaching the end of the list press 'q' or 'Q' and the Enter key to do so.
Authority Admin session only to set Syntax show [keyword] Keywords chap features mpx100 fc [] initiators fc or iscsi initiators_LUNmask iscsi [] isns [] logs [] luninfo LUNs LUNmask mgmt ntp perf presented_targets fc or iscsi properties stats system targets fc or iscsi Examples The following is an example of the show command: mpx100 #> show mpx100 mpx100 Information ——————– Product Name Symbolic Name mpx100 Mode Serial Number HW Version SW Version No.
Authority None Syntax show chap Examples The following is an example of the show chap command: mpx100 #> show chap The following is a list of iSCSI nodes that have been configured with CHAP 'ENABLED': Type iSCSI Node ——– ———— Init iqn.1998-01.com.vmware:rack86-s09-1ac2c0e4 Init iqn.1998-01.com.vmware:rack86-s02-39ae5fb4 Show Features command Displays license information for the mpx100/100b. Show Logs Command Displays the latest entries in the mpx100/100b system log file.
Authority None Syntax show perf Examples The following is an example of the show perf command: mpx100 #> show perf WARNING: Valid data is only displayed for port(s) that are not associated with any configured FCIP routes. Port Bytes/s Bytes/s Bytes/s Bytes/s Bytes/s Number (init_r) (init_w) (tgt_r) (tgt_w) (total) —— ——– ——– ——– ——– ——– GE1 0 0 0 27K 27K GE2 0 0 0 0 0 FC1 0 0 0 0 0 FC2 0 27K 0 0 27K Show Properties command Displays the values of both the Inactivity Timer and the CLI Prompt name.
Show MGMT command Displays management information for the mpx100/100b. Authority None Syntax show mgmt Examples The following is an example of the show mgmt command: mpx100 #> show mgmt Management Port Information —————————– Mode Dhcp Link Status Up IP Address 172.17.137.210 Subnet mask 255.255.254.0 Gateway 172.17.136.1 MAC Address 00-c0-dd-0c-60-10 Show iSCSI command Displays iSCSI information for the specified port. If the port is not specified, both ports are displayed.
Authority None Syntax show fc [] Parameters port_num: The number of the FC port to be displayed. Examples The following is an example of the show fc command: mpx100 #> show fc 1 FC Port Information ——————— FC Port 1 Link Status Down Current Link Rate Unknown Programmed Link Rate Auto WWNN WWPN Port ID Firmware Revision No. Frame Size Execution Throttle Connection Mode Programmed Connection Option 20:00:00:c0:dd:0c:60:11 21:00:00:c0:dd:0c:60:11 00-00-00 3.03.
Authority None Syntax show initiators_LUNmask Examples The following is an example of the show initiators_LUNmask command: mpx100 #> show initiators_LUNmask Index (WWNN/iSCSI Name) ———————0 iqn.1991-05.com.
Authority None Syntax show luns Examples The following is an example of the show luns command: mpx100 #> show LUNs LUN Information —————– Target 50:00:1f:e1:50:01:11:50,50:00:1f:e1:50:01:11:58 ———————————————————WWULN 50:00:1f:e1:50:01:11:50:00:00:00:00:00:00:00:00 LUN Number 0 VendorId COMPAQ ProductId HSV110 (C)COMPAQ ProdRevLevel 3010 Portal 0 LUN Size 0 MB LUN State Online WWULN LUN Number VendorId ProductId ProdRevLevel Portal LUN Size LUN State 60:05:08:b4:00:01:1f:60:00:1d:40:00:00:9a:00:00 1 C
Authority None Syntax show lunmask Examples The following is an example of the show lunmask command: mpx100 #> show LUNmask Index (WWNN,WWPN/iSCSI Name) ————————— 0 50:00:1f:e1:50:01:11:50,50:00:1f:e1:50:01:11:58 1 50:00:1f:e1:50:06:9d:20,50:00:1f:e1:50:06:9d:2c Please select a Target from the list above ('q' to quit): 0 LUN WWULN Vendor ———————0 50:00:1f:e1:50:01:11:50:00:00:00:00:00:00:00:00 COMPAQ 1 60:05:08:b4:00:01:1f:60:00:1d:40:00:00:9a:00:00 COMPAQ 2 60:05:08:b4:00:01:1f:60:00:1d:40:00:00:9f:00
Authority None Syntax show presented_targets fc iscsi Keywords fc: Specifies the display of FC-presented targets. iscsi: Specifies the display of iSCSI-presented targets. Examples The following is an example of the show presented targets FC command: mpx100 #> show presented_targets fc No Presented Targets found.
Authority None Syntax show snmp Examples The following is an example of the show snmp command: mpx100 #> show snmp SNMP configuration —————————— Read Community Public Trap Community Private System Location System Contact Authentication traps System OID 1.3.6.1.4.1.3873.1.4 System Description HP StorageWorks mpx100 Trap Destination IP Address Trap Port Trap Version 1 10.0.0.5 1024 2 Show Stats command Displays the mpx100/100b for statistics, FC and iSCSI.
Authority None Syntax show stats Examples The following is an example of the show stats command: mpx100 #> show stats FC Port Statistics ——————– FC Port Interrupt Count Target Command Count Initiator Command Count 1 23 0 0 FC Port Interrupt Count Target Command Count Initiator Command Count 2 1717443350 0 1815115822 iSCSI Port Statistics ———————– iSCSI Port 1 Interrupt Count 3108358287 Target Command Count 1815115673 Initiator Command Count 0 MAC Xmit Frames 54392137663 MAC Xmit Byte Count 61199467
Examples (continued) 170 iSCSI Port 2 Interrupt Count 51604 Target Command Count 0 Initiator Command Count 0 MAC Xmit Frames 0 MAC Xmit Byte Count 0 MAC Xmit Multicast Frames 0 MAC Xmit Broadcast Frames 0 MAC Xmit Pause Frames 0 MAC Xmit Control Frames 0 MAC Xmit Deferrals 0 MAC Xmit Late Collisions 0 MAC Xmit Aborted 0 MAC Xmit Single Collisions 0 MAC Xmit Multiple Collisions 0 MAC Xmit Collisions 0 MAC Xmit Dropped Frames 0 MAC Xmit Jumbo Frames 0 MAC Rcvd Frames 186 MAC Rcvd Byte Count 39260 MAC Rcvd U
Examples (continued) iSCSI Shared Statistics ———————– PDUs Xmited Data Bytes Xmited PDUs Rcvd Data Bytes Rcvd I/O Completed Unexpected I/O Rcvd iSCSI Format Errors Header Digest Errors Data Digest Errors Sequence Errors PDU Xmit Count PDU Xmit Count PDU Xmit Count IP Xmit Packets IP Xmit Byte Count IP Xmit Fragments IP Rcvd Packets IP Rcvd Byte Count IP Rcvd Fragments IP Datagram Reassembly Count IP Error Packets IP Fragment Rcvd Overlap IP Fragment Rcvd Out of Order IP Datagram Reassembly Timeouts TCP Xmi
Authority None Syntax show targets fc iscsi Keywords fc: Specifies the display of FC targets iscsi: Specifies the display of iSCSI targets. Examples The following is an example of the show targets fc command: mpx100 #> show targets fc Target Information ——————– WWNN 50:00:1f:e1:50:01:11:50 WWPN 50:00:1f:e1:50:01:11:58 Port ID 01-0d-00 Portal No. 1 State Online WWNN 50:00:1f:e1:50:06:9d:20 WWPN 50:00:1f:e1:50:06:9d:2c Port ID 01-08-00 Portal No.
B Diagnostics and troubleshooting Diagnostic information about the mpx100/100b is available through the chassis LEDs and the port LEDs. Diagnostic information is also available through the HP StorageWorks mpx Manager and CLI event logs and error displays.
Power-on self-test diagnostics The mpx100/100b performs a series of tests as part of its power-on procedure. The POST diagnostic program performs the following tests: • • • • Memory FLASH validation PCI device discovery Management Ethernet port Heartbeat LED blink patterns The Heartbeat LED indicates the operational status of the mpx100/100b. When the POST completes with no errors, the Heartbeat LED blinks at a steady rate of once per second.
Figure 74 Port IP address conflict blink pattern Using the CLI or GUI, the IP address conflict blink pattern may be cleared using the Beacon OFF function. Over-temperature blink pattern An mpx100/100b over-temperature condition is indicated with a five-blink pattern followed by a two-second pause. The five-blink error pattern indicates that the air temperature inside the mpx100/100b has exceeded the failure temperature threshold at 70 °C (see Figure 75).
Presenting an EVA LUN to an iSCSI Initiator is a two-step process in HP Command View: 1. Presenting the LUN to the iSCSI host entry. This communication presents the LUN from the EVA FC ports to the mpx100/100b FC ports. 2. Presenting the LUN to the iSCSI Initiator. This communication presents the LUN from the mpx100/100b Gigabit Ethernet ports to the iSCSI Initiator.
• Verify that the iSCSI Target status is connected with the command iscsi-ls –l. • For a Macintosh Initiator: • Verify that the iSCSI driver is installed. • Ping the mpx100/100b iSCSI port from the iSCSI Initiator. • Verify that the target's Visible field is set to Yes in the Manager Targets screen. • Verify that the target's status in the Target Status field is connected. • For an OpenVMS Initiator: • Verify that TCP/IP has been started and is properly configured.
Diagnostics and troubleshooting
C Log data The mpx100/100b maintains a message log that can be displayed and retrieved by the operator, either through the CLI or the SANsurfer GUI. The message log is persistent in that it is maintained across the mpx100/100b power cycles and reboots. The three log message categories are: • Informational log messages, page 179 • Error log messages, page 181 • Fatal log messages, page 187 The following sections describe the log message categories.
iSCSI driver The following log messages are common to both iSCSI ports, 1 (GE1) and 2 (GE2). They are listed in Table 22 and described in this section. Log messages beginning with #0 apply to iSCSI port 1 (GE1), and log messages beginning with #1 apply to iSCSI port 2 (GE2). Table 22 SCSI driver—informational log messages ID Log message 86347 #%d: QLDisable: Restart RISC Message Number Description 331 Restart iSCSI processor (RISC).
Error log messages The following sections list and describe, by reporting module, the error log messages. Application modules The error log messages provided by application modules are listed in Table 24 and described in this section. Table 24 Application module—error log messages ID Log message Message Number 40967 QLBA_NullDoorbell: driver unloaded, port disabled 7 Null doorbell routine for unloaded drivers. When a driver is unloaded, the doorbell routine is redirected to this null routine.
ID Log message 41771 QLBI_GetLUNList: LUN allocation failed for LUNId %d 811 Failed to allocate LUN object: out of resources. 41626 QLBI_GetLUNInfo: INQUIRY failed, TPB status 0x%x 666 Inquiry command failed. The Inquiry command was issued by the mpx100/100b as part of its discovery process. 41629 QLBI_GetLUNInfo: QLBI_PassthruCommand failed for INQUIRY (page code 0x83) 669 Inquiry command for page 83 failed. The Inquiry command was issued by the mpx100/100b as part of its discovery process.
ID Log message Message Number Description 42069 QLFC_HandleTeb: Driver Fatal Error 1109 Event notification: Fibre Channel driver encountered a fatal error. 42072 QLFC_HandleTeb: FC Logout. 1112 Event notification: FC port logged out. 42242 QLIS_AllocateSessionObject: Out of session resources. 1282 Failed to allocate object for iSCSI session: out of session resources. 42252 QLIS_EnqueueiScsiPdu: Duplicate PDU, CmdSN %d (0x%x), dropping it.
ID Log message Message Number Description 324 iSCSI login PDU was received with an invalid TSIH value. The TSIH is invalid because there is no session with that TSIH value. This would occur if the iSCSI Initiator attempting the login failed to used the TSIH value provided in the target login response PDU (the mpx100/100b is the target) in subsequent login PDUs. 42648 QLIS_HandleTeb: Driver Fatal Error 1688 Event notification: iSCSI driver encountered a fatal error.
ID Log message Message Number 74665 #%d: QLReadyTimer: QLiSNSReenable failed Description 937 The driver timed out while attempting to reconnect with iSNS. 74784 #%d: QLUpdateInitiatorData: No more room in Initiator Database 1056 The driver's initiator database is full. The driver is capable of storing 1024 iSCSI Initiators in its database. Use the CLI or GUI to remove unwanted/unused iSCSI Initiators.
ID Log message #%d: QLMarkDeviceOffline: Device Id: %x marked offline, 106928 cLinkDownTimeout = %x, cPortDownRetryCount=%x Message Number Description 432 The driver was unable to reestablish connection to target within the time-out and retry counts and is therefore marking it offline. 106948 #%d: QLSnsGetAllNext: Name server login FAILED %x 452 The FC processor is unable to log into the FC fabric name server.
ID Log message Message Number 139289 QBRPC_Initialize:TgtDevice Mem Allocation error 25 139296 QBRPC_Initialize:FcTgt Mem Allocation error 32 139297 QBRPC_Initialize:BridgeStatus Mem Allocation error 33 139298 QBRPC_Initialize:Diag Mem Allocation error 34 139299 QBRPC_Initialize:DiagLog Mem Allocation error 35 139300 QBRPC_Initialize:FruImage Mem Allocation error 36 139301 QBRPC_Initialize:OemMfg Mem Allocation error 37 139302 QBRPC_Initialize:Status Mem Allocation error 38 139303
Message Number Description #%d: qlutm_init: 69654 Diagnostic failed, invalid NVRAM 22 iSCSI processor failed NVRAM diagnostic. #%d: qlutm_init: 69655 Diagnostic failed, invalid DRAM 23 iSCSI processor failed DRAM diagnostic. #%d: qlutm_init: Failed to 69656 return diagnostic result to Bridge 24 iSCSI processor failed to return diagnostic result. ID Log message 69941 #%d: QLUtmProcessResponseQueue: Invalid handle %x EntryType %x 309 Response queue entry contains invalid handle.
ID Log message #%d: QLProcessResponse70502 Queue: Invalid handle %x EntryType %x Message Number Description 870 Response queue invalid handle for specified entry type. 70524 #%d: QLProcessAen: Invalid event %x 892 Asynchronous event for unknown event type. 70544 #%d: QLRebootTimer: Reboot failed! 912 Reboot timer failed. #%d: QLReadyTimer: Adapter missed heartbeat 70563 for 0x%x seconds. Rebooting 931 iSCSI driver missed iSCSI processor heartbeat. iSCSI processor rebooted.
ID Log message Message Number Description 102659 #%d: QLInitializeAdapter: Load ISP2322 transmit sequencer code failed 259 FC processor transmit sequencer code load failed. 102662 #%d: QLInitializeAdapter: Verify Checksum command failed (%x) 262 FC processor firmware checksum failed. 102680 #%d: QLInitializeFW: FAILED 280 FC processor firmware initialization failed.
D Simple Network Management Protocol SNMP provides monitoring and trap functions for managing the router through third-party applications that support SNMP. The mpx100/100b firmware supports SNMP versions 1 and 2 and an HP MIB “Management Information Base (MIB)” on page 192. Traps can be formatted using SNMP versions 1 or 2 “Notifications” on page 199.
Table 33 SNMP parameters Parameter Description Trap n Enabled Enables or disables trap n. If disabled, the trap is not configured. Trap Address1 Specifies the IP address to which the SNMP traps are sent. A maximum of 8 trap addresses are supported. The default address for traps is 0.0.0.0. Trap Port1 The port number on which the trap is sent. The default is 162. Trap Version Specifies the SNMP version (1 or 2) with which to format traps. 1Trap address (other than 0.0.0.
qsrNoOfGbEPorts Syntax Unsigned32 Access read-only Description The number of Gigabit Ethernet ports on the system qsrAgentVersion Syntax SnmpAdminString Access read-only Description The version number of the agent software on the system Network port table A list of network ports that are operational on the router. The entries in this table include the management port and the iSCSI and TOE ports on the router.
qsrNwPortRole Syntax QsrPortRole Access not-accessible Description The operational role of this port as, for example, a management port, an iSCSI port, or a TOE. A positive integer indexing each network port in a given role.
qsrMacAddress Syntax IMacAddress Access read-only Description The Apple Macintosh address for this port qstNwLinkStatus Syntax QsrLinkStatus Access read-only Description The operational link for this port qsrNwLinkRate Syntax QsrLinkRate Access read-only Description The operational link rate for this port FC port table information The Fibre Channel port table lists the FC ports on the router, the sequence of objects in a port entry, and the port;s role, index, physical address, port typ, l
qsrFcPortRole QsrPortRole qsrFcPortIndex Unsigned32 qsrFcPortNodeWwn PhysAddress qsrFcPortWwn PhysAddress qsrFcPortId PhysAddress qsrFcPortType Unsigned32 qsrFcLinkStatus QsrLinkStatus qsrFcLinkRate QsrLinkRate qsrFcPortRole Syntax QsrPortRole Access not-accessible Description The operational role of this port (that is in FCP mode or in frame shuttle mode) qsrFcPortIndex Syntax Unsigned32 Access not-accessible Description A positive integer indexing each FC port in a given role q
qsrFcPortType Syntax Unsigned32 Access read-only Description The type of FC port, as indicated by the use of the appropriate value assigned by IANA. The IANA-maintained registry for FC port types is at http://www.iana.org/assignments/fc-por)t-types.
qsrSensorType INTEGER qsrSensorIndex Unsigned32 qsrSensorUnits INTEGER qsrSensorValue Integer32 qsrUpperThreshold Integer32 qsrLowerThreshold Integer32 qsrSensorState INTEGER qsrSensorType Syntax INTEGER temperature = 1 Access not-accessible Description The type of data being measured by this sensor qsrSensorIndex Syntax Unsigned32 Access not-accessible Description A positive integer identifying each sensor of a given type qsrSensorUnits Syntax INTEGER celsius = 1 Access read-on
qsrSensorState Syntax INTEGER Access read-only Description The state of this sensor, indicating the health of the system. • unknown—The sensor value/threshold cannot be determined. • normal—The sensor value is within normal operational limits. • warning—The sensor value is approaching a threshold. • critical—The sensor value has crossed a threshold. Notifications The router provides six notification types.
qsrEventTimeStamp Syntax DateAndTime Access accessible-for-notify Description When the event occurred Agent startup notification Indicates that the agent on the router has started running. qsrAgentStartup—uses the following objects: • qsrEventTimeStamp Agent shutdown notification Indicates that the agent on the router is shutting down. qsrAgentShutdown—uses the following objects: • qsrEventTimeStamp Network port down notification Indicates that the specified network port is down.
• qsrEventTimeStamp • qsrEventSeverity • qsrEventDescription EVA iSCSI connectivity user guide 201
Simple Network Management Protocol
E Setting up authentication Challenge Handshake Authentication Protocol (CHAP) is an authentication protocol used for secure logon between the iSCSI Initiator and iSCSI target. CHAP uses a challenge-response security mechanism for verifying the identity of an initiator without revealing a secret password that is shared by the two entities. It is also referred to as a three-way handshake.
• Minimum length of 1 character. • No restriction on the type of characters that can be entered. Microsoft Initiator CHAP secret restrictions • • • • Maximum length of 16 characters. Minimum length of 12 characters. No restriction on the type of characters that can be entered. When an initiator uses iSNS for target discovery, only normal session CHAP applies. Linux version 3.6.3 CHAP restrictions CHAP setup with Linux iSCSI Initiator version 3.6.
• bidirectional CHAP during discovery and during normal session. Enabling single–direction CHAP during discovery and normal session Table 34 lists the parameters you use to enable single–direction CHAP.
ii. iii. iv. v. Enter the IP address of the iSCSI port of the mpx100/100b. Click Advanced. Select the CHAP Login Information check box. Enter the CHAP secret for the mpx100/100b discovered iSCSI Initiator in the Target Secret box. For example: CHAPsecret01 See “CHAP restrictions” on page 203 for more information on CHAP. vi. Click OK and the initiator completes Target discovery. • Using iSNS for target discovery: i. Click Add under iSNS Servers. ii. Enter the IP address of the iSNS server. iii. Click OK.
Enable CHAP for the Microsoft iSCSI Initiator 1. Click Discovery. For manually discovering iSCSI target portals: a. Click Add under Target Portals. b. Enter the IP address of the iSCSI port of the mpx100/100b. c. Click Advanced. d. Select the CHAP Login Information checkbox. e. Enter the CHAP secret for the mpx100/100b–discovered iSCSI Initiator in the Target Secret box, for example, CHAPsecret01. f. Click OK and the initiator completes Target discovery. Using iSNS for target discovery: i.
CHAPsecret01 • If the iSCSI Initiator is already listed under Discovered iSCSI Initiators i. Select the initiator in the left-hand column of the Discovered ISCSI Initiator list. ii. Click the Information tab. iii. Select the Enable CHAP check box. iv. Enter a CHAP secret. For example: CHAPsecret01 b. To enable CHAP for the mpx100/100b Discovered iSCSI Initiator entry using the mpx100/100b CLI: • If the iSCSI Initiator is not listed under the Show Initiators command: i.
i. Click Add under iSNS Servers. ii. Enter the IP address of the iSNS server. iii. Click OK. f. Click Targets. g. Select the appropriate target for login. h. Click Log On. i. Click Advanced. j. Select the CHAP Login Information check box. k. Enter the CHAP secret for the mpx100/100b discovered iSCSI Initiator in the Target Secret box. For example: CHAPsecret01 l. Select the Mutual Authentication check box. m. Click OK. n. Click OK and the initiator completes normal login.
i. Enter the initiator add command and add the iSCSI Initiator that is about to do discovery. ii. Enable CHAP and enter a CHAP secret. For example: CHAPsecret01 • If the iSCSI Initiator is already listed under the Show Initiators command: i. Enter the initiator mod command and select the iSCSI Initiator that is about to do discovery. ii. Enable CHAP and enter a CHAP secret. For example: CHAPsecret01 2.
k. l. Select the CHAP Login Information check box. Enter the CHAP secret for the mpx100/100b discovered iSCSI Initiator in the Target Secret box. For example: CHAPsecret01 m. Select the Mutual Authentication check box. n. Click OK. o. Click OK and the initiator completes normal login. Enabling bidirectional CHAP during discovery and bidirectional CHAP during normal session Table 37 lists the parameters you need to enable bi–directional CHAP during discovery and bidirectional CHAP during normal session.
ii. Enable CHAP and enter a CHAP secret. For example: CHAPsecret01 2. Enable CHAP for the mpx100/100b iSCSI port: • To enable CHAP for the mpx100/100b iSCSI port using the HP StorageWorks mpx Manager: a. Select the appropriate iSCSI port number. b. Click Advanced Configuration. c. Select the Enable CHAP check box. d. Enter a CHAP secret. For example: hpstorageworks • To enable CHAP for the mpx100/100b iSCSI port using the mpx100/100b CLI: a. Enter the set iscsi portnumber command. b.
F Saving and restoring the mpx100/100b configuration The mpx100/100b configuration information is saved as a .bin or .tgz file, depending on the method used to restore the mpx100/100b persistent data. The mpx100/100b configuration information is saved and restored using the mpx Manager GUI or the mpx100/100b CLI commands.
4. Enter the following command: mpx100 (admin) #> fru save FRU save completed. Configuration File is HP_StorageWorks_mpx100_FRU.bin. Please use FTP to extract the file out from the System. mpx100 (admin) #> NOTE: The FRU save creates a bin file containing the router’s persistent data, configuration, and LUN mappings. The file is stored in the routers /var/ftp directory. You must then FTP the tar file from the router. 5.
Password: password 5. Enter the following command: mpx100> admin start 6. Enter config as the password. 7. Enter the following command: mpx100 (admin) #> fru restore A list of attributes with formatting and current values will follow. Enter a new value or simply press the Enter key to accept the current value. If you wish to terminate this process before reaching the end of the list press 'q' or 'Q' and the Enter key to do so. Type of restore (0=full, 1=mappings only) [full] FRU restore completed. 8.
Saving and restoring the mpx100/100b configuration
G Regulatory compliance and safety This appendix describes the following sections: • Regulatory compliance, page 217 • Safety, page 220 Regulatory compliance Federal Communications Commission notice for Class A equipment This equipment has been tested and found to comply with the limits for a Class A digital device, pursuant to Part 15 of the FCC Rules. These limits are designed to provide reasonable protection against harmful interference when the equipment is operated in a commercial environment.
Regulatory compliance identification numbers For the purpose of regulatory compliance certifications and identification, your product has been assigned a unique Regulatory Model Number. The RMN can be found on the product nameplate label, along with all required approval markings and information. When requesting compliance information for this product, always refer to this RMN. The Regulatory Model Number should not be confused with the marketing name or model number of the product.
European Union notice Products bearing the CE Marking comply with both the EMC Directive (89/336/EEC) and the Low Voltage Directive (73/23/EEC) issued by the Commission of the European Community and if this product has telecommunication functionality, the R&TTE Directive (1995/5/EC).
Korean notices Safety Battery replacement notice Your switch is equipped with a lithium manganese dioxide, a vanadium pentoxide, or an alkaline internal battery or battery pack. There is a danger of explosion and risk of personal injury if the battery is incorrectly replaced or mistreated. Replacement is to be done by an HP authorized service provider using the HP spare part designated for this product.
mm2 or 18 AWG, and the length of the cord must be between 1.8 m, (6 ft) and 3.6 m (12 ft). If you have questions about the type of power cord to use, contact an HP authorized service provider. NOTE: Route power cords so that they will not be walked on and cannot be pinched by items placed upon or against them. Pay particular attention to the plug, electrical outlet, and the point where the cords exit from the product.
Regulatory compliance and safety
Glossary CHAP Challenge Handshake Authentication Protocol. An authentication technique for confirming the identity of one computer to another. direct connect A utility used to connect a server or mpx100/100b FC port directly to the EVA FC port without a the need for a Fibre Channel switch. fabric connect A utility used to connect a server or mpx100/100b FC port to a Fibre Channel switch to access the EVA FC ports.
target An iSCSI device that executes a command from an iSCSI Initiator to perform some task. TOE TCP Offload Engine A piece of hardware that replaces a NIC and shifts TCP packet processing tasks from the server CPU to specialized TCP processors on the network adapter or storage device. VLAN virtual local area network. A network of computers that behave as if they are connected to the same wire even though they may actually be physically located on different segments of a LAN.
Index Symbols EVA4x00/6x00/8x00 fabric mode, 24 A AC power mpx100/100b, 58 accounts user CLI, 141 application support EVA storage system, 36 audience, 17 B battery replacement notice, 220 BSMI notice, 219 Business Copy configuring, 28 direct connect, 36 fabric, 36 button maintenance, 51 C cables, 217 Canadian notice, 218 Cautions file systems, 81 using the registry editor, 32 challenge handshake authentication protocol See CHAP CHAP, 28 chassis controls, 50 Class A equipment, 218 CLI installing firmw
connectivity rules EVA iSCSI, 30 iSCSI Initiator, 31 operating system, 30 Windows Initiator, 32 Continuous Access EVA configuring, 28 FCIP gateways, 36 controls chassis, 50 conventions document, 18 text symbols, 18 D data transport mpx100, 25, 49 declaration of conformity, 217 device names Linux Initiator, 79 DHCP enabling, 51 diagnostics chassis, 173 input power LED, 173 direct connect description, 22 EVA4x00/6x00/8x00, 22 EVA8000 and Windows host, 24 document conventions, 18 related documentation, 17 du
installation hardware requirements, 39 mpx100, 55 installation type EVA iSCSI connectivity, 39 Installing EVA iSCSI connectivity, 39 installing mpx Manager, 56 mpx100/100b firmware, 62 international notices, 218 BSMI notice, 219 Canadian notice, 218 Class A equipment, 218 European Union notice, 219 Japanese notice, 219 Korean notices, 220 Internet Storage Name Service See ISNS IP address resetting, 51 IP network adapters, 37 iSCSI connectivity overview, 21 iSCSI connectivity option AE324A, 21 iSCSI Initiato
multipathing direct connect EVA4x00/6x00/8x00, 27 direct connect EVA iSCSI upgrade option, 43 dual mpx100 configuration, 99 iSCSI target configuration, 97 EVA3000/5000, 32 EVA4x00/6x00/8x00, 32 fabric EVA4x00/6x00/8x00, 27 EVA8000, 28 fabric attach EVA iSCSI upgrade option, 43 Fibre Channel mpx100/100b, 95 installing MS initiator, 100 requirements, 32 single mpx100 iSCSI target configuration, 96 single mpx100/100b configuration, 98 Windows, 32, 95 configuring iSCSI Initiator, 100 multipathing software, 26
single direction CHAP discovery session, 205 normal session, 205 single mpx100 IP addressing iSCSI port, 98 single mpx100/100b multipathing, 95 software multipathing, 26 software support, 25 SSSU direct connect, 36 fabric, 36 storage presenting for Linux, 67, 81 Storage System Scripting Utility See SSSU Subscriber's choice, HP, 19 support hardware, 25 software, 25, 26 storage system, 26 support switch, 25 switch support, 25 model, 36 series, 36 versions, 36 symbols in text, 18 teaming support, 31 technical
