HP StorageWorks EVA iSCSI Connectivity User Guide Part Number: 5697-0511 Thirteenth edition: August 2010
Legal and notice information © Copyright 2006-2010 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 ................................................................................. 17 Overview ................................................................................................................................. Intended audience .............................................................................................................. Related documentation ........................................................................................................
OpenVMS software requirements ................................................................................... OpenVMS iSCSI rules and guidelines ............................................................................. iSCSI Initiator software ................................................................................................. EVA storage system rules and guidelines ......................................................................................
Management Ethernet port .................................................................................................. Serial port ......................................................................................................................... Installation and maintenance ...................................................................................................... Power requirements .......................................................................................................
iSCSI Initiator setup for OpenVMS .............................................................................................. Configuring TCP/IP services ................................................................................................. Configuring VLANs ............................................................................................................ Enabling Ethernet jumbo frames ...........................................................................................
Unpresenting a virtual disk to an iSCSI Initiator using HP Command View EVA ............................... 129 8 iSCSI Boot from SAN ...................................................................... 131 HP Multifunction Gigabit server adapter requirements .................................................................. Supported operating systems for the HP Multifunction Gigabit server adapter ........................... Supported hardware ...........................................................
Set System command ................................................................................................. Set VLAN command ................................................................................................... Show command ........................................................................................................ Show Chap command ................................................................................................ Show Features command .......................
FC driver ......................................................................................................................... 193 System ............................................................................................................................ 194 D Simple Network Management Protocol ............................................. 195 SNMP properties ....................................................................................................................
Agent startup notification ................................................................................................... Agent shutdown notification ............................................................................................... Network port down notification .......................................................................................... FC port down notification ..................................................................................................
Glossary .......................................................................................... 229 Index ...............................................................................................
Figures 1 Direct connect iSCSI-Fibre Channel attachment mode configuration ............................... 23 2 EVA4400 direct connect iSCSI-Fibre Channel attachment mode configuration ................. 23 3 HP Command View EVA deployment configuration 1 ................................................... 24 4 HP Command View EVA deployment configuration 2 ................................................... 24 5 EVA4400 direct connect iSCSI-Fibre Channel attachment mode ABM configuration .........
33 Presented EVA LUNs ................................................................................................ 78 34 Configure initiator and targets .................................................................................. 79 35 Discovered Targets tab ............................................................................................ 79 36 Target login ...........................................................................................................
70 License key complete dialog box ............................................................................. 137 71 Display installed license key ................................................................................... 138 72 Chassis LEDs ........................................................................................................ 173 73 Normal heartbeat blink pattern ............................................................................... 174 74 System error blink pattern .
Tables 1 Document conventions ............................................................................................. 18 2 iSCSI Fibre Channel attachment option part numbers ................................................... 21 3 Connectivity attachment mode supported ................................................................... 26 4 Multipathing software requirements ........................................................................... 27 5 Supported mpx100 maximums .....................
33 SNMP parameters ................................................................................................ 196 34 CHAP single direction settings ................................................................................ 209 35 CHAP single and bidirectional settings .................................................................... 212 36 CHAP bidirectional and single 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: • Overview, page
• • • • • HP HP HP HP HP StorageWorks StorageWorks StorageWorks StorageWorks StorageWorks 4400 Enterprise Virtual Array user guide 4400 Enterprise Virtual Array installation guide 4000/6000/8000 Enterprise Virtual Array user guide Enterprise Virtual Array 3000/5000 user guide Replication Solutions Manager installation guide Document conventions and symbols Table 1 provides the conventions and symbols used in this document.
NOTE: Provides additional information. TIP: Provides helpful hints and shortcuts. Rack stability Observe the following rack stability warning to protect personnel and equipment. 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.
After subscribing, locate your products by selecting Business support and then Storage under Product Category. Other HP websites For additional information, see the following HP websites: • • • • 20 http://www.hp.com http://www.hp.com/go/storage http://www.hp.com/service_locator http://www.docs.hp.
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 26 • Security, page 30 • Configuring HP StorageWorks Continuous Access EVA and Business Copy, page 30 EVA and EVA4400 iSCSI connectivity product description The EVA family of Fibre Channel (FC) storage systems is s
AE352A AJ713A AJ714A T5471A HP StorageWorks EVA iSCSI Upgrade Option (optional) The AE324A connectivity option and an EVA storage system to provide high-availability multipath connectivity or to upgrade an existing EVA with iSCSI connectivity for multipath A redundant mpx100 hardware unit for customers who require high availability.
Figure 1 Direct connect iSCSI-Fibre Channel attachment mode configuration . Figure 2 EVA4400 direct connect iSCSI-Fibre Channel attachment mode configuration . Figure 3 and Figure 4 illustrate the HP Command View EVA iSCSI deployment configurations. These configurations are used with EVA 4x00/6x00/8x00 storage systems and allow for HP Command View connectivity without the need for a Fibre Channel switch. Figure 4 shows a redundant configuration using two mpx100/100b's.
Figure 3 HP Command View EVA deployment configuration 1 . Figure 4 HP Command View EVA deployment configuration 2 .
Discovery IP Address Presented iSCSI Targets D1 FP2A FP2B FP2A D2 D3 D4 FP2B FP1A FP1B FP1A FP1B IP Network management (WAN/LAN) mpx100/100b 1 mpx100/100b 2 MGMT MGMT HP StorageWorks mpx100 HP StorageWorks mpx100 MGMT IOIOI MGMT IOIOI ! FC1 FC1 FC2 FC2 GE1 GE1 ! GE2 FC1 GE2 FC1 FC2 FC2 GE1 GE2 GE1 GE2 D2 D1 D4 D3 iSCSI IP Network iSCSI data (LAN/VLAN) NIC EVA4400 with ABM running Command View EVA A B 26657a Figure 5 EVA4400 direct connect iSCSI-Fibre Channel attachmen
Figure 7 Fabric-iSCSI-Fibre Channel attachment mode . EVA and EVA4400 iSCSI connectivity hardware and software support This section identifies the hardware, devices, and operating systems compatible with the mpx100/100b. Hardware support mpx100/100b data transport The EVA and EVA4400 iSCSI options support both direct connect and Fibre Channel fabric connectivity through the mpx100/100b to the EVA storage system.
The mpx100 fabric through a Fibre Channel switch (Figure 7) The mpx100 fabric through a Fibre Channel switch (Figure 7) 1 A Fibre Channel switch is not required for the mpx100 and Windows host direct connect or HP Command View EVA iSCSI deployment. See Figure 1, Figure 2, Figure 3, Figure 4, and Figure 6 for more information. Fibre Channel switch hardware support The EVA and EVA4400 iSCSI options are supported with most B-series, C-series, and M-series product line switches.
Microsoft Windows 2008 Microsoft Windows XP Professional Linux OpenVMS Apple Mac OS X Solaris VMware ESX EVA 3000/5000 (active/active, fabric attach only) EVA4000/4100/4400/4400 with embedded switch /6000/6100/8000/8100, EVA6400/8400 For the latest information on EVA software version support, see the product release notes or SPOCK at http://www.hp.com/ storage/spock. You must sign up for an HP Passport to enable access.
Figure 9 Multipath Fabric-iSCSI-Fibre Channel attachment mode configuration . NOTE: Dual NICs and dual IP fabrics are supported for complete redundancy. Figure 10 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.
Figure 10 EVA4x00/6x00/8x00 fabric with four iSCSI-Fibre Channel controller host ports . Security The mpx100/100b supports Challenge Handshake Authentication Protocol (CHAP) at the connection setup. CHAP is a security protocol that includes support for both the bidirectional (mutual) authentication and the one-way (target) authentication options. You can configure and set up CHAP in the mpx100/100b. The target mpx100/100b can have its own unique password for One-Way CHAP option.
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 Configuration 1 mpx100—150 (single-path or multipath) Total number of iSCSI Initiators 1 mpx100b—16 (base), 48 (license upgrade 1), 150 (license upgrade 2) Note that the mpx100/100b can serve both single-path and multipath LUNs concurrently.
Microsoft Windows Server 2008 Server Core Linux Sun Solaris 10 VMware Initiator rules and guidelines This section describes the following iSCSI Initiator rules and guidelines: • “iSCSI Initiator rules and guidelines” on page 33 • “VMware iSCSI Initiator rules and guidelines” on page 33 • “Windows iSCSI Initiator rules and guidelines” on page 34 • “OpenVMS iSCSI Initiator rules and guidelines” on page 36 • “Apple Mac OS X iSCSI Initiator rules and guidelines” on page 35 • “Linux iSCSI Initiator rules and gu
• Hardware iSCSI HBA • NIC teaming • VMware native iSCSI software initiator. See “Installing and upgrading EVA iSCSI connectivity” on page 41. Network teaming The EVA iSCSI option supports NIC teaming with VMware. iSCSI Initiator software The EVA iSCSI option supports the VMware native iSCSI software Initiator. See “Installing and upgrading EVA iSCSI connectivity” on page 41 for information on version support.
Apple Mac OS X iSCSI Initiator rules and guidelines Firmware and hardware required: • Power PC and Intel Power Mac G5, Xserve, Mac Pro • ATTO Mac driver version 3.10 (minimum) Supports • ISNS • CHAP Does not support: • Multipathing iSCSI Initiator operating system considerations • Configure the Mac host mode iSCSI Initiator setting through HP Command View. See “HP StorageWorks mpx manager for Windows” on page 60 for more information on HP StorageWorks mpx Manager. • Host mode setting is Apple Mac OS X.
• • • • Multipath on single or dual mpx100's/100b's. MPxIO Symmetric option only. MPxIO round-robin. MPxIO auto-failback.
• iSNS • Multipath • OpenVMS V8.3-1H1 or later Not supported: • CHAP • Header and Data Digests • iSCSI boot iSCSI Initiator software The EVA iSCSI option supports the OpenVMS native iSCSI software Initiator. See OpenVMS software requirements, page 36 for information on version support. EVA storage system rules and guidelines Table 7 identifies the EVA storage system rules and guidelines.
• An EVA storage system can present LUNs to iSCSI Initiators and Fibre Channel hosts concurrently. HP StorageWorks EVA storage system software An EVA LUN that has been presented to an iSCSI initiator is supported with EVA storage applications such as HP StorageWorks Continuous Access, Business Copy, SSSU, and Replication Solutions Manager. There are some restrictions with iSCSI hosts when using the EVA iSCSI connectivity option, as described in the following sections.
Fibre Channel switch/fabric rules and guidelines In fabric-attachment mode, the mpx100/100b is supported with Fibre Channel switches (Table 9). For minimum switch firmware version, contact you HP representative. Table 9 Fibre Channel switch/fabric requirements Switch series B-series C-series M-series Model/Firmware level For the latest information on operating system version support, see the product release notes or SPOCK at http:// www.hp.com/storage/spock.
HP OpenVMS All standard GbE NICs/ASICs supported by HP for OpenVMS Apple Mac OS X All standard GbE NICs/ASICs supported by Apple All standard GbE NICs/ASICs supported by HP for Linux1: • HP NC3xx Linux • HP NC510x (Red Hat 4, SUSE 9 only), TOE NIC features are not supported • QLA4052C/QLE4062C/QMH4062C Microsoft Windows 2008, 2008 Server Core, 2003, and Windows XP • All standard GbE NICs/ASICs supported by HP for Windows 2008, 2003 and Windows XP: • HP NC3xx TOE with MS scalable networking pack • QLA
3 Installing and upgrading EVA iSCSI connectivity This chapter contains information about the following topics: • Verify your system requirements, page 41 • Verify your installation type and components, page 42 • EVA and EVA4400 iSCSI connectivity installation, page 43 • Rack mount the mpx100/100b, page 46 • Connect the mpx100/100b to an IP switch, page 47 • Start the mpx100/100b, page 48 • Set the mpx100/100b management port to use HP StorageWorks Command View EVA, page 48 To install your EVA iSCSI connect
Verify your installation type and components Table 11 describes the iSCSI installation types and attachment modes for the HP StorageWorks EVA and EVA4400 iSCSI connectivity option.
Option Installation components HP StorageWorks EVA and EVA4400 iSCSI Upgrade Option (parts list) 1 1 1 1 1 mpx100 or mpx100b EULA SR 232 port converter Quick install instructions ReadMeFirst * 2.0m copper cables are for use in direct-connect configurations only. See Figure 1 through Figure 6 and Figure 8. Copper cables are not supported for fabric attach. Optical cables and SFPs can also be used for direct connect configurations.
NOTE: For the EVA4400, see the product installation documentation. a. Press the Down Arrow key on the EVA front panel. System Information is displayed. b. Press the Right Arrow key. Versions is displayed. c. Press the Down Arrow key. Host Port Config is displayed. d. Press the Right Arrow key. Fabric is displayed. e. f. Press Enter. Press the Down Arrow key until the port that you want to change to Fabric Connect Mode is displayed. Press Enter.
8. d. Press the Right Arrow key. Fabric is displayed. e. Press the Down Arrow key. Direct Connect is displayed. f. Press the Right Arrow key. Port 1 is displayed. g. Press the Down Arrow key until the port that you want to change to Direct Connect Mode is displayed. h. i. Press Enter. Repeat the process for the other controller. Continue with “Connect the mpx100/100b to an IP switch” on page 47.
2. 3. 4. 5. 6. Remove the orange Fibre Channel cable from the existing mpx100/100b FC2 port and Fibre Channel switch port. Connect one end of the cable into the new mpx100/100b FC1 port and the other end into the second Fibre Channel switch port. Disconnect the orange Fibre Channel cable from the top controller FP1 at the Fibre Channel switch end and connect it to the second Fibre Channel switch port.
NOTE: The 1U space in a rack includes three rail mounting holes; these rack holes, however, are not evenly spaced. For best installation the C-Shelf can be centered in a 1U space. Locate the center, find a hole that is 5/8" on center from the holes immediately above and below. This is the center of a 1U mounting position. The holes, two above and two below this center, are only 1/2" on center from their adjacent holes. b. c. d. e. f. g. h. i. 3.
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 11 shows the location of the ports and LEDs on the mpx100/100b. Figure 11 The mpx100 port and LED locations . 1.
3. Enter the command admin start with the password config to enable administrator privileges. 4. Enter the set mgmt command and follow the prompts to set the management port properties to enable HP Command View EVA to communicate with the mpx100/100b management port. 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. 6.
Figure 13 Hardware/iSCSI devices . 8. 50 Enter the IP address and subnet mask for Port 1 on the IP Ports tab, and then click Save changes.
4 Configuring the mpx100/100b This chapter contains the following major sections: • General description, page 51 • Installation and maintenance, page 57 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 14). The mpx100/100b connects to iSCSI hosts through IP connections, and to an EVA storage system directly through FC ports or FC switch ports. Figure 14 The mpx100 external components .
Figure 15 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 16 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.
Use a pointed nonmetallic tool to briefly press the Maintenance button. Release the button after seven seconds (observe seven flashes of the Heartbeat LED). The mpx100/100b boots and configures the maintenance port for DHCP. The boot time is less than one minute. 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.
Alert LED (yellow) The Alert LED indicates any port fault conditions.
Figure 18 Gigabit Ethernet (iSCSI) ports . 1. Activity LED 2. Status LED Port LEDs The iSCSI/TOE ports each have two LEDs: the Link Status LED (green) and the Activity LED (green). 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.
2. Activity LED Serial port The mpx100/100b is equipped with an RS-232 serial port for maintenance purposes. The serial port location is shown in Figure 20, and is labeled IOIOI. You can manage the mpx100/100b through the serial port using the CLI. Figure 20 Serial port . The serial port is connected using a standard 8-wire Ethernet cable and the supplied dongle to convert the Ethernet RJ–45 connector to a female DB9 connector.
Power requirements Power requirements for the mpx100/100b are 0.5 Amp at 100 VAC or 0.25 A at 240 VAC. Environmental conditions Consider the factors that affect the climate in your facility, such as equipment heat dissipation and ventilation.
1. Connect the cable with the supplied dongle from a COM port on the management server to the serial port on the mpx100/100b. 2. Configure the server serial port according to your operating system. For Windows: a. Open the HyperTerminal application. b. Select Start > Programs > Accessories > HyperTerminal > HyperTerminal. c. Enter a name for the mpx100/100b connection and choose an icon in the Connection Description window, and then click OK. d.
NOTE: For Windows, you can write the .iso file to a CD-ROM or copy the .zip file to a folder. Table 15 mpx Manager GUI server requirements Component Requirement Windows: Guest OS: Windows 2003 Windows Server 2003 SP1, 2003 r2, 2003 SP2 Windows Server 2003 x64 Edition SP1, 2003 r2, 2003 SP2 Linux: (Itanium and X86/x64 systems) Red Hat: Operating system • Red Hat Advanced Server Linux 4, Update 3 (kernel 2.6.
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 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. 2. Unpack the file to a temporary directory. For example: tar -zxvf hpmpx_n.
NOTE: Click Connect to add mpx100's/100b's to be managed simultaneously. 5. Click Connect to display the selected HP mpx Manager. A typical mpx Manager is displayed (Figure 22). Figure 21 Connect to the mpx100/100b . Figure 22 Typical mpx Manager display . Starting HP StorageWorks mpx Manager for Linux To start HP StorageWorks mpx Manager for Linux: 1. 62 Enter the mpx100/100b command: ./HPmpx100Manager. The Connect to the mpx100/100b window is displayed (Figure 21 on page 62).
2. 3. Enter the host name or IP address of the management port of the mpx100/100b. Click Connect to display the selected HP mpx Manager. A typical mpx Manager is displayed (Figure 22 on page 62). 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 dash character (-) = U+002d ASCII dot character (.) = U+002e ASCII colon character (:) = U+003a ASCII lowercase characters (a through z) = U+0061 through U+007a ASCII digit characters (0 through 9) = U+0030 through U+0039 See section 3.2.
TIP: You can exit the set system command window without making changes to the existing values by pressing q or Q, and then pressing Enter. 2. Enter a unique Symbolic Name or press Enter to accept the current value. 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.
5. After enabling the iSCSI port for iSNS, verify that an iSCSI port target entry appears in the iSNS server database. Example 1. iSNSCLI command issued on iSNS server C:> isnscli listmodes iqn.1986-03.com.hp:fcgw.mpx100:mpx100-65.1. 50001fe150002f70.50001fe150002f7f Where: iqn.1986-03.com.hp:fcgw.mpx100 The standard IQN name for all mpx100's/100b's mpx100-65 Symbolic Name 1 iSCSI port number 50001fe150002f70.
2. FTP to the mpx100/100b management port and log in with the following information: Username: ftp Password: ftp 3. To set FTP for binary transfer, enter the following information: ftp> bin ftp> put mpx100-x_x_x_x.bin ftp> quit 4. Use Telnet to connect to the mpx100/100b and log in as guest. Username: guest Password: password 5. Set administrative privileges to allow for the firmware upgrade with the following information: mpx100> admin start password: config 6.
Configuring the mpx100/100b
5 Setting up the iSCSI Initiator and storage This chapter contains the following topics: • • • • • • • • iSCSI initiator setup, page 69 iSCSI initiator setup for Windows (single-path), page 69 Storage setup for Windows (single-path) About Microsoft Windows server 2003 scalable networking pack iSCSI Initiator setup for Apple Mac OS X (single-path) iSCSI initiator setup for Linux, page 79 iSCSI initiator setup for Solaris (single-path), page 85 iSCSI initiator setup for VmWare, page 89 • iSCSI initiator set
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 23). Figure 23 Adding an IP address . f. g. h. Click Add to add the IP address of Port 1 on the mpx100/100b. Click OK to exit. Click the Targets tab. The target status is Inactive (Figure 24). Figure 24 Inactive target status . 70 i. Select a single target and then click Log On. j.
Figure 25 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 127. 2. Set a. b. c. up the iSCSI drive on the iSCSI Initiator: Open the Windows Computer Management window.
SNP setup with HP NC 3xxx GbE multifunction adapter Microsoft’s Scalable Networking Pack works in conjunction with HP’s NC3xxxx Multifunction Gigabit server adapters and Alacritech's SES2xxxxx adapter for Windows 2003 only. To set up SNP on a Windows 2003 server: 1. Install the hardware and necessary software for the NC3xxx Multifunction Gigabit server adapter, following the manufacturer’s installation procedures. 2. Download the SNP package from the Microsoft website: http://support.microsoft.
2. Run the Xtend SAN application to discover and configure the EVA iSCSI targets. The Xtend SAN iSCSI Initiator can discover targets either by static address or iSNS. For static address discovery: a. Select Discover Targets and then select Discover by DNS/IP (Figure 26). Figure 26 Discover targets . b. Add the static IP address of the mpx iSCSI port in the Address field and then select Finish (Figure 27). Figure 27 Add static IP address . c.
Figure 28 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 29). Figure 29 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.
Figure 30 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. 76 e. Select the newly-added target under Host name in the left frame. f. Check the Visible box (Figure 31). 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. Click Save. Figure 31 Selecting newly added target . i. Select Status, select Network Node, and then select Login to connect to the mpx target (Figure 32). The Network Node displays a status of Connected and the target status light turns green. Figure 32 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 127. 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 33). Figure 33 Presented EVA LUNs .
iSCSI Initiator setup for Linux Installing and configuring the SUSE Linux Enterprise 10 iSCSI driver Configure the initiator using the built-in GUI-based tool or the open-iscsi administration utility using the iscsiadm command. See the iscsiadm (8) man pages for detailed command information. 1. Modify the Initiator Name by issuing the following command: # vi /etc/initiatorname.iscsi 2.
4. Log in to the target (Figure 36). Figure 36 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 37). Figure 37 Connected Targets tab .
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.
If there are problems starting the iscsi daemon, they are usually caused by an incorrect IP Address or an ill-formatted initiator name. Installing the initiator for Red Hat 3 and SUSE 8 If you are upgrading from a previous installation of an iSCSI driver, HP recommends that you remove the /etc/initiatorname.iscsi file before installing the new driver. See the following website for the latest version of the Linux driver for EVA iSCSI connectivity: http://sourceforge.
Variations in process scheduling and network delay can result in iSCSI targets being mapped to different SCSI device nodes every time the driver is started. Because of this variability, configuring applications or operating system utilities to use the standard SCSI device nodes to access iSCSI devices can result in sending SCSI commands to the wrong target or logical unit. To provide consistent naming, the iSCSI driver scans the system to determine the mapping from SCSI device nodes to iSCSI targets.
Target bindings The iSCSI driver automatically maintains a bindings file, /var/iscsi/bindings. This file contains persistent bindings to ensure that the same iSCSI bus and target ID number are used for every iSCSI session with a particular iSCSI TargetName, even when the driver is repeatedly restarted. This feature ensures that the SCSI number in the device symlinks (described in “Device names” on page 82) always map to the same iSCSI target.
To avoid file system corruption, the iSCSI shutdown script automatically stops all processes using devices in /etc/fstab.iscsi, first by sending them SIGTERM, and then by sending any remaining processes SIGKILL. The iSCSI shutdown script unmounts all iSCSI file systems and stops the iSCSI daemon, terminating all connections to iSCSI devices. CAUTION: File systems not listed in /etc/fstab.iscsi cannot be automatically unmounted. Presenting EVA storage for Linux To set up LUNs using HP Command View: 1. 2.
1. Use Telnet to connect to the mpx management port or connect to the mpx serial port using the HP-supplied connector. The mpx management port's default IP address is 10.0.0.1/255.0.0.0˙. The mpx serial port's default setting is 115200/8/n/1. 2. To log in, enter: • User name: guest • Password: password 3. To enable administrator privileges, enter: • admin start • config 4. Issue the Set System command. 5. Follow the prompts to disable Controller LUN AutoMap.
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.
5. Create the iSCSI device links for the local system: # devfsadm -i iscsi 6. Verify mpx targets are available to the initiator: # iscsiadm list target 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.
. Monitoring your iSCSI configuration Display information and modify settings on the iSCSI Initiator and target devices by using the following commands: iscsiadm list initiator-node iscsiadm list discovery iscsiadm list target iscsiadm list target-param iscsiadm modify initiator-node iscsiadm modify discovery iscsiadm modify target-param For more details on using the iscsiadm command, see the #man iscsiadm man pages.
2. Configure the VMKernel TCP/IP networking stack for iSCSI support. Configure the VMkernel, service console with dedicated virtual switch with a dedicated NIC for iSCSI data traffic. Follow the instructions from VMware. Figure 38 shows an example of a configuration. Figure 38 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.
4. Enable the iSCSI software initiators: a. In VMware’s VI client, select the server from the inventory panel. b. Click the Configuration tab, and then click Storage Adapters under Hardware. c. Under iSCSI software Adapter, choose the available software initiator. d. Click the Properties link of the software adapter. e. The iSCSI initiator properties dialog box is displayed. Click Configure. f. The General properties dialog box displays (Figure 40). Select the Enabled checkbox .
7. See iSCSI initiator setup for Windows (single-path) for instructions to set up LUNs using HP Command View. 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 42. d.
• • • • Configuring target discovery, page 93 Starting the iSCSI Initiator, page 95 Stopping the iSCSI Initiator, page 96 Setting up storage for OpenVMS, page 96 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.
2. 3. Edit the new file and add a list of the IP names or addresses of the iSCSI target ports that should be probed for available storage devices. The header included in this file defines the proper format for these addresses. The manual target list is automatically loaded when the iSCSI Initiator is started. By default, changes to this file will not take effect until the system is rebooted or until the initiator is stopped and restarted.
1. To configure the OpenVMS initiators for iSNS, copy the file SYS$COMMON: [SYSMGR] ISCSI$ISNS_SERVICES.TEMPLATE to SYS$COMMON: [SYSMGR] ISCSI$ISNS_SERVICES.DAT The directory SYS$SPECIFIC:[SYSMGR] can be used if the file is to be node-specific rather than cluster-wide. 2. Edit the new file and add a list of the IP names or addresses of the iSNS servers that should be probed for available targets. The header in this file defines the proper format for these addresses.
NOTE: Note that TCP/IP must be fully loaded before the iSCSI Initiator is started. Stopping the iSCSI Initiator Generally, there should be no need to stop the iSCSI Initiator after it has been loaded. However, should the need arise to stop the initiator, execute the DCL command procedure SYS$STARTUP:ISCSI$INITIATOR_SHUTDOWN.COM. NOTE: Note that if TCP/IP is stopped on a system running the iSCSI Initiator, the initiator will be automatically stopped and unloaded as part of the rundown of TCP/IP.
6 Setting up the iSCSI Initiator for multipathing This chapter contains the following topics: • • • • • • Overview, page 97 Configuring multipath with Windows iSCSI initiator, page 102 Configuring multipath with the VMware iSCSI initiator, page 113 Configuring multipath with the Solaris 10 iSCSI initiator, page 116 Configuring multipath with the OpenVMS iSCSI initiator, page 122 Device Mapper Multipath Enablement Kit for HP StorageWorks Disk Arrays, page 125 Overview The mpx100/100b supports iSCSI multipa
The mpx100/100b FC ports do not necessarily have to be connected to the EVA storage controller to be added to the iSCSI host entry. Upon iSCSI device discovery, HP Command View polls the mpx100/100b for both FC port WWPNs and adds them to the iSCSI host entry FC port list. If a single mpx100/100b is discovered as an iSCSI controller (see Figure 43), both of its FC ports will be included in the single HP Command View iSCSI host entry.
Figure 45 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 46). Figure 46 Example: Dual mpx100 multipath — iSCSI target configuration .
Figure 47 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 48). Figure 48 Example: Single mpx100 iSCSI port IP addressing . Each iSCSI GbE port has duplicate paths to the LUN because each GE port is presenting two unique targets with the same LUN information. Each unique target should be considered an iSCSI path to the LUN.
iSCSI Initiator—virtual path mpx100/100b iSCSI GbE port—physical path EVA FC port—physical path 16.10.11.03 50:05:08:b4:01:01:f6:7c iqn.199602…..f67c iqn.199603…..f678 iqn.199604…..f67c Adding another mpx100/100b and two more EVA ports to this configuration results in the configuration in Figure 49 and Table 17: Figure 49 Example: Dual mpx100 iSCSI port IP addressing . Table 17 provides an example of a dual multipath configuration.
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. With multiple physical connections, the MS iSCSI Initiator control panel applet allows setting a specific link to be used as the primary iSCSI session during target login.
Figure 50 Add Features page . After the server reboots, add support for iSCSI Devices using the MPIO applet (see Figure 51).
Figure 51 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 52). 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 52 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 53). Click Next to display the Targets tab. Figure 53 Properties screen for iSCSI Initiator .
Figure 54 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 127.
Figure 55 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 56): a. Start the MS iSCSI control panel applet. b. Select the Target tab. c. Click Details. d. Click Devices. e.
Figure 56 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 58). 2. Click Yes to start the general configuration wizard (see Figure 59).
Figure 59 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 60). 2. Enter the first mpx100/100b iSCSI target port IP address. Figure 60 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 61). Figure 61 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 128 to: • Create an iSCSI host entry, and • Present LUNs to the iSCSI host 2.
3. Use Microsoft’s iSCSI services to manage the iSCSI target login and LUN load balancing policies (see Figure 63). Figure 63 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.
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 89 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. VMware 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.
NOTE: MPxIO is not supported on versions of the EVA3000/5000. For more information about MPxIO, see the Solaris Fibre Channel and Storage Multipathing Administration Guide at: http://docs.sun.com/source/819-0139 Preparing the host system To verify that MPxIO is enabled: 1. Issue the following command to verify that the MPIO setting is no: /kernel/drv/iscsi.conf file to verify mpxio-disable=”no” 2.
2. Create a Solaris iSCSI host entry to present LUNs to an iSCSI host using HP Command View EVA. Follow the procedure Creating an iSCSI initiator host via HP Command View EVA, page 128. (Note that the host mode setting for Solaris is Linux/MAC. 3. Enable the SendTargetsdiscovery method: # iscsiadm modify discovery --sendtargets enable 4.
LUN: 4 Vendor: HP Product: HSV210 OS Device Name: /dev/rdsk/ c4t600508B400107271000060000C540000d0s2 Target: iqn.1986-03.com.hp:fcgw.mpx100:mpx100-65.1. 50001fe150002f70.50001fe150002f7e Alias — ISID: 4000002a0000 Connections: 1 LUN: 3 Vendor: HP Product: HSV210 OS Device Name: /dev/rdsk/c4t600508B400107271000060000C540000d0s2 LUN: 4 Vendor: HP Product: HSV210 OS Device Name: /dev/rdsk/c4t600508B400107271000060000C4A0000d0s2 Target: iqn.1986-03.com.hp:fcgw.mpx100: mpx100-65.1.50001fe150002f70.
2. c4t600508B400107271000060000C540000d0/scsi_vhci/ssd@g600508b400107271000060000c Enabling MPxIO To enable MPxIO for HP storage devices, the appropriate information for device-type-scsioptions-list must be added in the /kernel/drv/scsi_vhci.conf file. To enable MPxIO for HP: 1. Use a text editor to change the configuration file. For example: # vi /kernel/drv/scsi_vhci.conf 2.
Total Path Count: 4 Operational Path Count: 4 # 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: libmpscsi_vhci.
66.0.50001fe150002f70.50001fe150002f78,0 Relative ID: 0 Name: 4000002a0000,iqn.1986-03.com.hp:fcgw.mpx100:mpx10066.0.50001fe150002f70.50001fe150002f7a,0 Relative ID: 0 Name: 4000002a0000,iqn.1986-03.com.hp:fcgw.mpx100:mpx10065.1.50001fe150002f70.50001fe150002f7e,0 Relative ID: 0 # Configuring multipath with the OpenVMS iSCSI Initiator Multipath support for the OpenVMS iSCSI Initiator is native to OpenVMS. No additional software is required for full iSCSI multipath support.
SHOW DEVICE /MULTIPATH device-name An example of the command is shown in Figure 65. Figure 65 SHOW DEVICE / MULTIPATH Example . For more comprehensive information about an iSCSI device, including all available paths, issue the command: SHOW DEVICE /FULL device-name An example of the command is shown in Figure 66.
Figure 66 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.
An example of the command is shown in Figure 67. Figure 67 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.
Installing the Device Mapper Multipath Enablement Kit To install the kit, follow the steps described in the Installation and Reference Guide Device Mapper Multipath Enablement Kit for HP StorageWorks Disk Arrays: 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.
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 127 Creating an iSCSI initiator host via HP Command View EVA, page 128 Presenting a virtual disk to an iSCSI initiator via HP Command View EVA, page 129 Unpresenting a virtual disk to an iSCSI initiator via HP Command View EVA, page 129 HP Command View allows LUN management for iSCSI Initiators through additional screens.
To discover the mpx100/100b: 1. 2. 3. Start HP Command View EVA and click the EVA storage system icon that is configured to present iSCSI storage. Click the iSCSI Devices folder under Hardware. Click Discover iSCSI Devices on the Properties bar. If mpx100/100b devices are discovered, a new icon named iSCSI Controller appears under the iSCSI Devices folder. If the devices are not automatically discovered, click Add iSCSI Device and add the mpx100/100b management port IP address.
4. 5. In the Operating system field, select the appropriate operating system for the iSCSI Initiator, as follows: Supported iSCSI Initiator Operating system setting with Command View 8.0 Windows Windows Red Hat or SUSE Linux Linux/Mac OS Macintosh Linux/Mac OS VMware VMware Solaris Solaris OpenVMS OpenVMS Click Add Host to save the changes. Figure 68 Add a host for Command View EVA .
2. Click the Presentation tab in the VDisk Properties screen. HP Command View lists the iSCSI host assigned to the VDisk. 3. Select the appropriate iSCSI host and click the Unpresent host(s) button. NOTE: If multipathing is active, HP Command View EVA recognizes and automatically unpresents the LUN from the same iSCSI Initiator on both the mpx100 and mpx100b. The LUN is unpresented to the iSCSI Initiator when the virtual disk is no longer presented to the iSCSI Initiator.
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.
• • • • HP HP HP HP NC373i PCI Express Multifunction Gigabit Server Adapter NC373m PCI Express Dual Port Multifunction Gigabit Server Adapter for c-Class BladeSystem NC374m PCI Express Dual Port Multifunction Gigabit Server Adapter NC380T PCI Express Dual Port Multifunction Gigabit Server Adapter 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.
NOTE: When the iSCSI boot path is initialized and after system POST, the iSCSI Option ROM is successfully logged in to the mpx100. Use HP Command View EVA to present the boot LUN to the initiator, and then set the initiator host mode to Linux/Mac. Configuring the BIOS on QLogic iSCSI HBAs To configure the BIOS: IMPORTANT: Before you begin, use the F9 key to disable any other internal storage adapters. 1. 2. Press Ctrl-Q to enter the Fast!UTIL program. Select the desired HBA. 3. 4. 5. 6. 7. 8. 9. 10. 11.
Installing the OS on QLogic iSCSI HBAs To install Linux: 1. 2. 3. Obtain the appropriate installation media. Insert the DVD/CD and follow the on-screen instructions. For those operating systems requiring the driver diskette, see the Readme files for installation instructions on the QLogic download web page: http://support.qlogic.com/support/product_resources.asp?id=964 To install Windows Server 2008/2003: 1. 2. 3. 4. Obtain the appropriate installation media. Boot the DVD/CD.
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.
4. Enter the license key in the New License Key dialog box (Figure 69). Figure 69 New license key dialog box . 5. Click OK. The Add new license key complete dialog box appears (Figure 70). Figure 70 License key complete dialog box .
6. Click OK. The newly-installed license key is listed (Figure 71). Figure 71 Display installed license key .
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.
command keyword keyword [value] keyword [value1] [value2] The command is followed by one or more keywords. Consider the following rules and conventions: • Commands and keywords are case-insensitive. • 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.
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.
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. The restored configuration does not take effect until the mpx100/100b is rebooted.
Example 144 Command line interface
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 | mgmt | ntp | properties snmp | syst
show stats show system show targets [ fc | iscsi ] shutdown target [ add | rm ] targetmap [ add | rm ] - Not supported 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.
Example The following is an example of the image command: mpx100 (admin) #> image unpack iSR-6140-2_0_0_1.bin Unpack Completed. Please reboot the system for FW to take effect. mpx100 (admin) #> reboot Are you sure you want to reboot the System (y/n): y System will now be rebooted... Initiator command Adds, modifies, or removes an initiator in the mpx100/100b database. Authority Admin session only to set Syntax initiator add mod remove Keywords add: Adds an initiator to the mpx100/100b database.
Logout command Exits the CLI and returns the operator to the login prompt. Authority Admin session only to set Syntax logout Example mpx100 #> LUNmask command Maps a target LUN to an initiator. Also removes mappings. The command prompts the operator to pick from a list of targets, LUNs, and initiators. Authority Admin session only to set Syntax LUNmask add remove Keywords add: Map a LUN to an initiator.
Examples The following is an example of the LUNmask add command: mpx100 (admin) #> LUNmask add Index (WWNN/iSCSI Name) -------------------0 iqn.1991-05.com.
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.
Examples The following is an example of the reboot command: mpx100 (admin) #> reboot Are you sure you want to reboot the System (y/n): y System will now be rebooted... 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, LUNs, and initiators. The factory default IP addresses is restored. Authority Admin session.
Examples The following is an example of the save logs command: mpx100 (admin) #> save logs Save Event Logs completed. Package is mpx100_Evl.tar.gz Please use FTP to extract the file out from the System. The following are two examples of the save traces command: mpx100 (admin) #> save traces Save ASIC Traces completed. Package is mpx100_Asic_Trace.tar.gz Please use FTP to extract the file out from the System. mpx100 (admin) #> save traces No ASIC trace files exist to save. Command aborted.
Authority Admin session Syntax set chap Example The following is an example of the set chap command: mpx100 (admin) #> set chap Index (WWNN,WWPN/iSCSI Name) ----- ---------------------0 iqn.2004-08.com.hp.mpx100.0539A01064.0.2000002037fd8bab. 2200002037fd8bab 1 iqn.2004-08.com.hp.mpx100.0539A01064.1.2000002037fd8bab. 2200002037fd8bab Please select a presented target from the list above ('q' to quit): 0 A list of attributes with formatting and current values will follow.
Set Features command Adds licenses for the mpx100/100b. Set iSCSI command Configures an iSCSI port. 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.
Set iSNS command Configures iSNS parameters for an iSCSI port. 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.
Set NTP command Configures NTP parameters. 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.
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.
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. of FC Ports No.
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.
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.
Examples The following is an example of the show system command: mpx100 #> show system System Information -------------------Product Name Symbolic Name System Mode Serial Number HW Version SW Version No. of FC Ports No. of iSCSI Ports Log Level Log Length (KB) Temperature (c) HP StorageWorks mpx100 Rack3 iSCSI Server Connectivity Mode 0539A01070 2 1.0.5.0 2 2 0 32768 32 Show MGMT command Displays management information for the mpx100/100b.
Examples The following is an example of the show iscsi command: iSCSI Port Information -----------------------iSCSI Port 1 Port Status Enabled Link Status Up iSCSI Base Name iqn.1986-03.com.hp:fcgw.mpx100:mpx100-74.0 MAC Address 00-c0-dd-0c-8d-c2 IP Address 33.33.66.73 Subnet Mask 255.255.0.0 Gateway IP Address 0.0.0.0 Firmware Revision No. 3.00.02.44 No. of Open Connections 0 Target TCP Port No.
Authority None Syntax show initiators fc iscsi Keywords fc: Specifies the display of FC initiators. iscsi: Specifies the display of iSCSI Initiators. Examples The following is an example of the show initiators command: mpx100 #> show initiators Initiator Information ----------------------Initiator Name iqn.1991-05.com.microsoft:hp-8qdaqlxt Alias IP Address 10.3.5.130 Portal No.
Show iSNS command Displays iSNS configuration information for the specified iSCSI port. If the port is not specified, the iSNS configuration information for both iSCSI ports is displayed. Authority None Syntax show isns [] Parameters port_num: The iSCSI port number whose iSNS configuration is to be displayed. Examples The following is an example of the Show iSNS command: mpx100 #> show isns iSNS Information -----------------iSCSI Port 1 iSNS Disabled IP Address 0.0.0.0 TCP Port No.
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:9
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:00 COMPA
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.
Syntax show snmp Examples The following is an example of the show snmp command: mpx100 #> show snmp SNMP configuration -----------------------------Read Community Trap Community System Location System Contact Authentication traps System OID System Description Trap Destination IP Address Trap Port Trap Version Show Stats command Displays the mpx100/100b for statistics, FC and iSCSI. Authority None Syntax show stats 168 Command line interface Public Private 1.3.6.1.4.1.3873.1.
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 61199467593726 MAC Xm
Examples (continued) 170 Command line interface 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 Byt
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 Tim
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 WWPN Port ID Portal No. State 50:00:1f:e1:50:06:9d:20 50:00:1f:e1:50:06:9d:2c 01-08-00 1 Online The following is an example of the Show Targets iSCSI command: mpx100 #> show targets iscsi No Targets found. Show VLAN command See the show iscsi command.
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.
System Alert LED is illuminated The System Fault LED is illuminated when a fault exists in the mpx100/100b firmware or hardware. If the System Fault LED is illuminated, check the Heartbeat LED for an error blink pattern and take necessary actions. See “Heartbeat LED blink patterns” on page 174 for more information. Power-on self-test diagnostics The mpx100/100b performs a series of tests as part of its power-on procedure.
Management port IP address conflict blink pattern An IP address conflict on the management Ethernet port is indicated with a four-blink pattern (see Figure 75). Figure 75 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 mpx100/100b statistics Statistics are available from the mpx100/100b for the Fibre Channel and iSCSI ports, and can be displayed through the CLI or the mpx Manager GUI. See “Show Stats command” on page 168. Troubleshooting LUN presentation from the EVA to the iSCSI Initiator This section describes basic troubleshooting when presenting a LUN from the EVA to the iSCSI Initiator.
Troubleshooting iSCSI Initiator connections to the EVA iSCSI targets If the iSCSI Initiator cannot connect to the EVA iSCSI targets presented by the mpx100/100b: • For a Windows Initiator: • Verify that the iSCSI driver is installed. • Ping the mpx100/100b iSCSI port from the iSCSI Initiator. • Select General > Secret and check the security setting on the initiator. • Verify that the iSCSI Initiator’s iqn name changed in the General tab.
If the iqn name has changed, choose from one of the following options to reinstate the original iqn name: • For Windows—In the initiator GUI, click the General tab, and then select Change > Reset to reset it to the original iqn name. • For Linux—Edit the InitiatorName setting in the /etc/initiatorname.iscsi file. • For Linux and Windows—Reinstall the initiator to create a valid iqn name. • For OpenVMS—Ensure that the TCP/IP host name has not changed.
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 191 The following sections describe the log message categories.
ID Log message Message Number Description 54683 QLIS_OpenConnectionNotification: Target connection opened (Port %d, DDB %d) 1435 An iSCSI initiator logged into a router presented target. 54938 QLIS_HandleTeb: UTM_EC_OPEN_CONNECTION 1690 Event notification: iSCSI open connection request. 54939 QLIS_HandleTeb: UTM_EC_CLOSE_CONNECTION or UTM_EC_CONNECTION_CLOSED 1691 Event notification: iSCSI close connection request or connection closed.
ID Log message Message Number Description 87350 #%d: QLGetFwStateCallback: Invalid link speed 0x%x 1334 iSCSI port link speed could not be determined. Link speed may be incorrectly programmed. Fibre Channel driver The informational log messages for the Fibre Channel driver are common to both FC ports 1 (FC1) and 2 (FC2). The messages are listed and described in Table 23. Log messages beginning with #0 apply to FC port 1 (FC1) and log messages beginning with #1 apply to FC port 2 (FC2).
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 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 Message Number Description 41769 QLBI_GetLUNList: REPORT LUNS command failed with CHECK CONDITION, SCSI STATUS 0x%02X 809 Report LUNs command failed with CHECK CONDITION status. The Report LUNs command was issued by the mpx100/100b as part of its discovery process. 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.
ID Log message 42027 QLFC_Logout: VP Index 0x%x not configured 1067 Logout attempted using Fibre Channel VP (virtual port) index which has not been configured. Operation attempted on an unconfigured VP. 42068 QLFC_HandleTeb: System Error 1108 Event notification: Fibre Channel processor encountered a system error (unrecoverable firmware error). 42069 QLFC_HandleTeb: Driver Fatal Error 1109 Event notification: Fibre Channel driver encountered a fatal error. 42072 QLFC_HandleTeb: FC Logout.
ID 41272 41283 Log message QLIS_LoginPduContinue: CONN_STATE_IN_LOGIN, Unknown InitTaskTag. QLIS_LoginPduContinue: TSIH 0x%x out of range Message Number Description 312 iSCSI login PDU received with an incorrect initiator task tag for a session which is partially logged in. This would occur if a login PDU other than the initial login PDU used an initiator task tag that was different from the initiator task tag provided in the initial login PDU.
ID Log message Message Number Description 74069 #%d: QLUtmProcessResponseQueue: Immediate data addr %08x:%08x in unsupported PduType 341 Driver received an unsupported pdu type with immediate data address. 74241 #%d: QLiSNSEnableCallback: iSNS Server TCP Connect failed 513 The iSCSI processor was unable to connect with iSNS (iSCSI name server).
Fibre Channel driver The Fibre Channel driver error log messages are listed and described in Table 26 and described in this section. Log messages beginning with #0 apply to FC port 1 (FC1) and log messages beginning with #1 apply to FC port 2 (FC2).
ID Log message Message Number Description 107029 #%d: QLUpdateDeviceData: out of slots in host database 533 The drivers host (initiator) database is full. 107030 #%d: QLUpdateDeviceData: out of slots in target database 534 The drivers target database is full. 107041 #%d: QLUpdateDeviceDatabase 0x%x: GET_ID failed %x 545 The drivers host (initiator) database is full. Maximum host database = 64.
ID Log message Message Number Description 139282 QBRPC_Initialize:GetStats Mem Allocation error 18 Failed memory allocation for Get Statistics API. 139283 QBRPC_Initialize:InitListMem Allocation error 19 Failed memory allocation for Get Initiator List API. 139284 QBRPC_Initialize:TargetList Mem Allocation error 20 Failed memory allocation for Get Target List API. 139285 QBRPC_Initialize:LUNList Mem Allocation error 21 Failed memory allocation for Get LUN List API.
ID Log message 151842 FW Upgrade performed: new version is: %d.%d.%d.%d 290 Performed router firmware upgrade, new version number is d.d.d.d. 151843 REBOOT/SHUTDOWN Command from user. Code=%d 291 User performed a router reboot or shutdown. 151889 #%d: qapisetfcinterfaceparams_1_svc: FC port configuration changed 337 FC port configuration has been modified. 151890 #%d: qapisetiscsiinterfaceparams_1_svc: iSCSI port configuration changed 338 iSCSI port configuration has been modified.
System The error log messages provided by system modules are listed and described in Table 28. Table 28 System—error log messages ID Log message Message Number Description 237572 Failed to kill sys killer %d\n 4 Failed to kill system task. 237573 Temperature over high threshold %d 5 Reporting router exceeds maximum operating temperature. 249862 Temperature is back to normal range %d 6 The router temperature has returned to the normal operating range and is d (C).
ID Log message Message Number Description 69966 #%d: QLEnable: QLRebootTimer failed AF %x RS %x Time %d 334 Port enable reboot timer failed. 70224 #%d: QLProcSrblessiSNSResponse: Invalid handle %x 592 iSNS response contains invalid handle. 70400 #%d: QLInitializeDevice: QLStartAdapter failed 768 Start iSCSI processor failed. 70417 #%d: QLInitializeAdapter: QLInitializeFW failed 785 iSCSI processor firmware initialization failed.
ID Log message Message Number Description 70837 #%d: QLStartFw: Load Fw loader timeout 1205 iSCSI failed to load firmware in time allotted. FC driver The fatal log messages are listed and described in Table 30. Log messages beginning with #0 apply to FC port 1 (FC1) and log messages beginning with #1 apply to FC port 2 (FC2).
ID Log message Message Number Description 102746 #%d: QLProcessResponseQueue: Invalid handle %x, type %x 346 Response queue entry contains invalid handle. 102752 #%d: QLTimer: Ext Ram parity error exceed limit cnt 0x%x, limit 0x%x, Disabled adapter 352 FC processor external SRAM parity error count exceeded limit: FC port disabled. 102755 #%d: QLTimer: Heartbeat failed 355 FC processor heartbeat failed. 102800 #%d: QLRestartRisc: restart RISC 400 FC processor being restarted.
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 196. Traps can be formatted using SNMP versions 1 or 2 “Notifications” on page 204.
SNMP trap configuration SNMP trap configuration supports setting up to eight trap destinations. Choose from Trap 1 to Trap 8 to configure each trap. Table 33 describes the parameters for configuring an SNMP trap. 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.
qsrSwVersion Syntax SnmpAdminString Access read-only Description The system software (firmware) version number qsrNoOfFcPorts Syntax Unsigned32 Access read-only Description The number of FC ports on the system 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 port
qsrNwPortEntry Syntax QsrNwPortEntry Access not-accessible Description Each entry (row) contains information about a specific network port.
qsrNwPortAddressMode Syntax INTEGER 1 - Static 2 - DHCP 3 - Bootp 4 - RARP Access read-only Description The method the port uses tot get its IP address. qsrIPAddressType Syntax InetAddressType Access read-only Description The type of the IP address, for example, ipv4 or ipv6.
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 type, link status, and rate.
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 qsrFcPortNodeWwn Syntax PhysAddress Access read-only Description The WWN of the node that contains this port
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.
QsrSensorEntry A sensor entry consists of the following sequence of objects: 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
qsrUpperThreshold Syntax Integer32 Access read-only Description The upper-level threshold for this sensor. qsrLowerThreshold Syntax Integer32 Access read-only Description The lower-level threshold for this sensor qsrSensorState Syntax INTEGER Access read-only The state of this sensor, indicating the health of the system. • unknown—The sensor value/threshold cannot be determined. Description • normal—The sensor value is within normal operational limits.
qsrEventSeverity Syntax INTEGER Access accessible-for-notify Description This indicates the severity of the event. The value clear is used to specify that a condition that caused an earlier trap is not present now.
FC port down notification Indicates that the specified FC port is down. If the port comes up thereafter, this event is sent with the qsrEventSeverity object set to clear. qsrFcPortDown—Uses the following object: • qsrFcLinkStatus • qsrEventTimeStamp • qsrEventSeverity Sensor notification Indicates that the state for the specified sensor is not normal. Once the sensor goes back to normal, this event is sent with the qsrEventSeverity object set to clear.
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.
• Enabling bi-directional CHAP during discovery and bi-directional CHAP during normal session, page 216 CHAP restrictions The mpx100/100b CHAP secret restrictions • Maximum length of 100 characters. • 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.
• Single-direction—The target authenticates the identity of the initiator with the user-provided CHAP secret. To enable single-direction CHAP, you need to enable CHAP for a specific initiator record on the mpx100/100b and input a corresponding CHAP secret from the iSCSI host. • Bidirectional—The initiator and target authenticate identity of each other with the user-provided CHAP secrets.
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. ii. Enter the initiator add command and add the iSCSI Initiator that is about to do discovery. Enable CHAP and enter a CHAP secret. For example: CHAPsecret01 • If the iSCSI Initiator is already listed under the Show Initiators command: i. ii.
Enabling CHAP for the mpx100/100b-discovered iSCSI initiator entry To enable CHAP for the mpx100/100b-discovered iSCSI initiator entry using the HP StorageWorks mpx Manager • If the iSCSI initiator is not listed under Discovered iSCSI Initiators: 1. Go to the Wizard menu and select the Add Initiator Wizard and enter the iqn name string. 2. Select the Enable CHAP checkbox. 3. Enter a CHAP secret, for example, CHAPsecret01. • If the iSCSI initiator is already listed under Discovered iSCSI Initiators: 1.
4. Select the CHAP Login Information checkbox. 5. Enter the CHAP secret for the mpx100/100b–discovered iSCSI Initiator in the Target Secret box. 6. Click OK and then click OK again. Enabling single–direction CHAP during discovery and bidirectional CHAP during normal session Table 35 lists the parameters you need to enable single-direction CHAP during discovery and bidirectional CHAP during normal sessions.
• If the iSCSI Initiator is already listed under the Show Initiators command: i. ii. 2. Enter the initiator mod command and select the iSCSI Initiator that is about to do discovery. Enable CHAP and enter a CHAP secret. For example: CHAPsecret01 Enable CHAP for the mpx100/100b iSCSI presented target: • To enable CHAP for the mpx100/100b Discovered iSCSI Initiator entry using the HP StorageWorks mpx Manager: a. Select the iSCSI Presented Target the initiator will log in to. b. Click the Information tab. c.
i. j. k. 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 l. Select the Mutual Authentication check box. m. Click OK. n. Click OK and the initiator completes normal login.
• If the iSCSI Initiator is not listed under the Show Initiators command: i. ii. Enter the initiator add command and add the iSCSI Initiator that is about to do discovery. Enable CHAP and enter a CHAP secret. For example: CHAPsecret01 • If the iSCSI Initiator is already listed under the Show Initiators command: i. ii. 2. Enter the initiator mod command and select the iSCSI Initiator that is about to do discovery. Enable CHAP and enter a CHAP secret.
• Using iSNS for Target discovery: i. Click Add under iSNS Servers. ii. Enter the IP address of the iSNS server. iii. Click OK. g. h. i. j. k. l. Click Targets. Select the appropriate target for login. Click Log On. 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 m. Select the Mutual Authentication check box. n. Click OK. o.
i. ii. iii. iv. b. Select the Initiator in the left-hand column of the Discovered ISCSI Initiator list. Click the Information tab. Select the Enable CHAP check box. Enter a CHAP secret. For example: CHAPsecret01 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. ii. Enter the initiator add command and add the iSCSI Initiator that is about to do discovery.
iii. Click Advanced. iv. Select the CHAP Login Information check box. v. Enter the CHAP secret for the mpx100/100b discovered iSCSI Initiator in the Target Secret box. For example: CHAPsecret01 vi. Select the Mutual Authentication check box. vii. Click OK. viii. 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. g. h. i. j. k. l. Click Targets.
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.
Saving the configuration using the mpx100/100b CLI To save the configuration using the mpx100/100b CLI: 1. Log in to the mpx100/100b using a Telnet session to the management port or the console port. Username: guest Password: password 2. Enter the following command: mpx100> admin start 3. Enter config as the password. 4. Enter the following command: mpx100 (admin) #> fru save FRU save completed. Configuration File is HP_StorageWorks_mpx100_FRU.bin.
2. 3. 4. Click Browse and select the appropriate file name to restore. Select Full Configuration Restore or Partial Restore (Mappings). Click Start. The Security Check dialog box is displayed. 5. Enter the password config, and then click OK. 6. Reboot the system for the configuration to take effect. Restoring the configuration using the mpx100/100b CLI To restore the configuration using the mpx100/100b CLI: 1.
Saving and restoring the mpx100/100b configuration
G Regulatory compliance and safety This appendix describes the following sections: • Regulatory compliance, page 223 • Safety, page 226 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.
Cables Connections to this device must be made with shielded cables with metallic RFI/EMI connector hoods in order to maintain compliance with FCC Rules and Regulations. 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.
International notices and statements Canadian notice (avis Canadien) Class A equipment This Class A Digital apparatus meets all requirements of the Canadian Interference-Causing Equipment Regulations. Cet appareil numérique de la classe A respecte toutes les exigences du Règlement sur le matériel brouilleur du Canada.
Japanese notice 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.
WARNING! Your switch contains an internal lithium manganese dioxide, a vanadium pentoxide, or an alkaline battery pack. There is risk of fire and burns if the battery pack is not properly handled. To reduce the risk of personal injury: • Do not attempt to recharge the battery. • Do not expose to temperatures higher than 60 ºC (140 ºF). • Do not disassemble, crush, puncture, short external contacts, or dispose of in fire or water. • Replace only with the HP spare part designated for this product.
of 1.00 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.
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.
Switch An IP network communications device that routes packets (messages or fragments of messages) between nodes across virtual circuits. teaming The concept of multiple network adapters working together as a single network adapter. target An iSCSI device that executes a command from an iSCSI Initiator to perform some task.
Index Symbols EVA4x00/6x00/8x00 fabric mode, 25 host ports EVA8000, 42 A AC power mpx100/100b, 61 accounts user CLI, 139 application support EVA storage system, 38 audience, 17 B battery replacement notice, 226 BSMI notice, 225 Business Copy fabric, 38 Business Copy configuring, 30 direct connect, 38 button maintenance, 53 C cables, 224 Canadian notice, 225 Cautions file systems, 85 using the registry editor, 34 challenge handshake authentication protocol See CHAP CHAP, 30 chassis controls, 52 Class A eq
components installation, 42 configuring mpx Manager, 61 server serial port, 58 connectivity rules EVA iSCSI, 32 iSCSI Initiator, 33 operating system, 32 Windows Initiator, 34 Continuous Access EVA configuring, 30 FCIP gateways, 38 controls chassis, 52 conventions document, 18 text symbols, 18 D data transport mpx100, 26, 51 declaration of conformity, 223 device names Linux Initiator, 82 DHCP enabling, 53 diagnostics chassis, 173 input power LED, 173 direct connect EVA4x00/6x00/8x00, 22 direct connect descr
HP Command View EVA, 27 configuring LUNs, 127 mpx100 rules, 39 rules, 39 I initial discovery mpx100/100b, 127 initiator Linux, 34, 37 Microsoft Windows, 34, 37 setup iSCSI, 69 initiator setup Linux, 79, 92 Windows single-path, 69 installation hardware requirements, 41 mpx100, 57 installation type EVA iSCSI connectivity, 42 Installing EVA iSCSI connectivity, 41 installing mpx Manager, 59 mpx100/100b firmware, 66 international notices, 225 BSMI notice, 225 Canadian notice, 225 Class A equipment, 225 European
mpx Manager configuring, 61 display, 62, 63 installing firmware, 66 Linux, 61 starting, 61 Windows server, 60 mpx100 configuring, 51 data transport, 26, 51 IP switch connection, 47 management port, 48 rack mount, 46 resetting, 53 starting, 48 mpx100 defaults factory, 54 mpx100/100b AC power, 61 initial discovery, 127 installing firmware, 66 SAN, 139 server connections, 58 server requirements, 60 multipathing direct connect EVA4x00/6x00/8x00, 28 direct connect EVA iSCSI upgrade option, 45 dual mpx100 configu
rules configuration EVA storage system, 37 HP Command View EVA, 39 S Safety, 226 safety battery replacement notice, 226 Japanese power cord statement, 228 power cords, 227 Taiwan battery recycling notice, 227 SAN configurations mpx100/100b, 139 security CHAP, 30 serial pin definition , 57 server serial port configuring, 58 server connections mpx100/100b, 58 server requirements mpx Manager, 60 single direction CHAP discovery session, 209 normal session, 209 single mpx100 IP addressing iSCSI port, 100 single
