Page 1 HP MPX200 Multifunction Router User Guide Abstract This document describes the MPX200 Multifunction Router, which supports HP 3PAR StoreServ, P6000 EVA, and P9000/XP families of Fibre Channel storage systems for integrated iSCSI connectivity, FCIP, FCoE, and data migration (see the Data Migration Services User's Guide).
Page 2 Warranty 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.
Page 3: Table Of Contents
Recommended switch infrastructure for an IP-SAN..............23 Network latency........................25 3 Installing the MPX200................26 MPX200 components......................26 Rack mounting the MPX200.....................27 4 Managing MPX200 iSCSI using HP P6000 Command View......31 Setting up the MPX200 management port..................31 Fibre Channel zoning......................31 Open zoning........................31 Fibre Channel switch-based zoning..................32 HP P6000 Command View discovery..................32...
Page 4 Installing the MPIO feature for Windows Server 2003............68 Microsoft Windows Server 2003 Scalable Networking Pack............69 Setting up SNP for the HP NC3xxx Multifunction Gigabit server adapter......69 iSCSI initiator setup for Apple Mac OS X (single-path)............69 Setting up the iSCSI initiator for Apple Mac OS X.............70 Setting up storage for Apple Mac OS X................74...
Page 5 3-site configuration with four MPX200 routers..............116 3-site configuration with six MPX200 routers..............116 3-site configuration with eight MPX200 routers..............117 3-site configuration with six MPX200 routers and full inter-site connectivity......118 FCIP configuration rules and guidelines................119 General FCIP configuration rules...................119 Operating system and multipath support................119 Storage system rules and guidelines................120...
Page 6 HP P6000 Command View does not discover MPX200............147 Initiator cannot log in to MPX200 iSCSI target..............147 Initiator logs in to MPX200 iSCSI target, but P6000 EVA-assigned LUNs do not appear on initiator..........................148 P6000 EVA-presented virtual disk not seen by initiator............148 Windows initiators may display Reconnecting if NIC MTU changes after connection has logged in..........................149...
Page 7 Typographical conventions.....................152 Rack stability........................153 Product warranties........................153 12 Documentation feedback...............154 A Command reference................155 Command syntax........................155 Command line completion....................155 Authority requirements......................155 Commands..........................155 Admin..........................156 Beacon...........................157 Blade..........................157 Clear..........................157 Date..........................157 Exit..........................158 Fciproute........................158 FRU..........................160 Help..........................161 History...........................162 Image..........................162 Initiator...........................163 Logout..........................164 Lunmask.........................164 Passwd...........................166 Ping..........................166 Quit..........................166 Reboot...........................167 Reset..........................167 Save..........................167 Set..........................168 Set alias.........................169 Set CHAP........................169...
Page 8 Target device discovery....................212 Target presentation (mapping)...................213 VP group notification......................213 Sensor notification......................213 Generic notification......................214 D Log messages..................216 E HP mpx100/mpx100b to MPX200 upgrade..........238 To upgrade from mpx100/mpx100b to the MPX200 Multifunction Router:........238 F Regulatory compliance and safety.............240 Regulatory compliance notices....................240 Contents...
Page 9 Italian notice........................246 Latvian notice........................247 Lithuanian notice......................247 Polish notice........................247 Portuguese notice......................247 Slovakian notice......................248 Slovenian notice......................248 Spanish notice.........................248 Swedish notice........................248 G Saving and restoring the MPX200 configuration........249 Saving the configuration using MPX200 CLI................249 Restoring the configuration using MPX200 CLI................249 Glossary....................251 Index.......................255 Contents...
Page 10: Mpx200 Multifunction Router Overview
20). For more information on data migration, see the Data Migration Services User's Guide. MPX200 storage system support The MPX200 storage system support may be different based on the protocol. Not all storage system models are supported on all the MPX200 supported protocols. The storage system support for each...
Page 11 Table 1 MPX200 storage system support by protocol MPX200 FCIP SAN MPX200 iSCSI MPX200 FCoE extension support Target support Target support and and management MPX200 data migration and management management software (MPX200 support and management Storage system software software CLI) software (mpx Manager) HP 3PAR StoreServ 7000;...
Page 12 Go to http://www.hp.com/go/hpsc. Under Support Options/DOWNLOAD OPTIONS, click Drivers, Software, & Firmware. Enter MPX 10- 1 GbE Base Multifunction Router in the Find an HP product by search box and then click GO. Select HP MPX 10-1GbE Base Multifunction Router.
Page 13 HP Storage Data Migration Utilities kit which includes additional data migration tools. The MPX200 chassis contains one or two router blades, two PCMs, and a mid-plane. There are two types of router blades: a 4-port 1-GbE blade and a 2-port 10-GbE/2-port 1-GbE blade. Both blade options include two 8-Gb/s FC ports.
Page 14 License MPX200 Chassis. NOTE: When configured for iSCSI bridging, HP recommends use of the same blade option type (1 GbE or 10GbE- 1 GbE) in a common chassis to ensure balanced performance in a redundant configuration. The following additional equipment is required to configure the MPX200:...
Page 15: Mpx200 Configuration Options For P6000 Eva
You can configure a P6000 EVA storage system for simultaneous connectivity to iSCSI/FCoE and FC attached hosts. Support for iSCSI/FCoE to a P6000 EVA is provided through the MPX200 and an FC switch fabric port (fabric attach) or the MPX200 directly connected to the P6000 EVA.
Page 16 Figure 3 MPX200 single-blade multi-P6000 EVA configuration Figure 4 (page 16) illustrates a multi-P6000 EVA configuration with connectivity for up to four P6000 EVA storage systems from dual MPX200 blades. This configuration provides high availability with failover between blades. Figure 4 MPX200 dual-blade multi-P6000 EVA configuration...
Page 17: Mpx200 Configurations For Xp24000/20000
MPX200 configurations for XP24000/20000 An XP storage system can be configured for simultaneous connectivity to iSCSI and FC attached hosts. Support for iSCSI to an XP storage system is provided through the MPX200 and an existing FC switch fabric port (fabric-attached).
Page 18 Figure 8 MPX200-XP single-blade fabric-attached configuration Figure 9 (page 18) shows an MPX200-XP dual-blade fabric-attached configuration. This configuration provides high availability with failover between blades. Figure 9 MPX200-XP dual-blade fabric-attached configuration Figure 10 (page 19) shows a multi-XP configuration with connectivity for up to four XP storage systems from a single MPX200 blade.
Page 19 Figure 10 MPX200-XP multi-XP fabric-attached configuration MPX200 configurations for XP24000/20000...
Page 20: Planning The Mpx200 Installation
The MPX200 supports the following functions: iSCSI-FCoE, FCIP, Data Migration. For simultaneous operation, you can configure the MPX200 chassis with a single blade or dual blades to run up to two functions per blade in the combinations shown in Table 3 (page 20).
Page 21: Iscsi/Fcoe Operation
The MPX200 presents one iSCSI target for each VPG (a total of four). Each initiator, therefore, discovers four times the number of FC targets. HP recommends that you use iSNS to present to the initiator only the required iSCSI targets.
Page 22: 10-Gbe Initiators
A Fibre Channel switch installed in your environment for MPX200 fabric-attached configurations Equipment cabinet suitable for 2U-sized enclosures A 1 GbE or 10-GbE switch to connect to the MPX200 1GbE iSCSI ports or to the MPX200 10GbE iSCSI/FCoE ports as iSCSI targets...
Page 23: General Ip-San
Table 5 (page 24) describes minimum recommended Ethernet switch capabilities for an MPX200 based IP-SAN. For more information about FCoE, see the converged network switches and the HP SAN Design Reference Guide at http://h18006.www1.hp.com/storage/networking/index.html MPX200 storage and IP network best practices...
Page 24 Switch capability Description 1 and 10 Gigabit The 1 GbE iSCSI blade of the MPX200 comes with four copper GbE ports (802.3ab). To Ethernet support take advantage of full duplex gigabit capabilities, you need infrastructure of Cat5e or Cat6 cabling. The 10-GbE iSCSI/FCoE blade of the MPX200 comes with two SFP+ 10 Gb ports.
Page 25: Network Latency
GE port 2 and GE port 4 for improved performance balancing. Host Server connectivity: Dual NICs connected to the IP storage network with a single port connected to each switch. For Windows 2003/2008, use the HP DSM for MPIO for multiple NIC support.
Page 26: Installing The Mpx200
This chapter describes how to rack mount the MPX200. WARNING! Mount the MPX200 in the rack so that the weight is evenly distributed. An unevenly loaded rack can become unstable, possibly resulting in equipment damage or personal injury. This product is supplied with a 3 wire cable and plug for the user's safety. Use this power cable in conjunction with a properly grounded outlet to avoid electrical shock.
Page 27: Rack Mounting The Mpx200
Use a crosshead screwdriver to perform the rack mount procedure. To rack mount the MPX200: Attach the two chassis rails to the MPX200 chassis using three 10-32 x 1/4 in. screws for each rail. Make sure that the end with the flange is facing the rear of the chassis (Figure 12 (page 27)).
Page 28 3. Washer Install the chassis in the rack: Starting from the back of the rack, slide the MPX200 chassis and rail assembly into the rack rails. Fasten the chassis to the rack using two 10-32 x 3/8 in. screws in the middle hole on...
Page 29 Route the power cord: Starting from the front of the rack, connect the power cord to the MPX200. For the left blade, route the cord by following the gap between the chassis and the chassis rail (see Figure 16 (page 29)).
Page 30 Remove the four 10-32 x 3/8 in. screws that secure the rack rails to the front of the rack. Position the bezel support plate in front of the MPX200 chassis, with the arrows pointing Replace the four 10-32 x 3/8 in. screws, two on each side of the bezel support plate.
Page 31: Managing Mpx200 Iscsi Using Hp P6000 Command View
Because the MPX200 can be a fabric-connected device, it is important to understand the zoning requirements. Open zoning When using an open zone configuration, each FC port on each MPX200 must be connected to a separate fabric (see “Open zone configuration” (page 31)).
Page 32: Fibre Channel Switch-Based Zoning
Fibre Channel switch-based zoning Each FC port on the MPX200 uses NPIV to create a total of four unique, virtual WWNNs per physical FC port. To create proper zoning, you must understand the use of VPGs. A VPG consists of a WWNN from each of the four physical FC ports. This allows presentation for up to 1,024 LUNs from a single P6000 EVA or XP array.
Page 33 After the discovery is complete, the MPX200s appear in the iSCSI Devices folder as iSCSI Controller 01 and iSCSI Controller 02. The four iSCSI MPX200 hosts appear in the Hosts folder (see Figure 21 (page 33)). The ports associated with each host consist of the VPGs from each blade.
Page 34: Setting Up The Iscsi Ip Ports
Each iSCSI IP port must have an IP address—IPv4, IPv6, or both. Set the IP address on the IP Ports tab on the iSCSI Controller Properties page (see Figure 23 (page 35)). NOTE: A target portal is created for each IP address that you set. Managing MPX200 iSCSI using HP P6000 Command View...
Page 35: Setting The Date And Time On The Mpx200
Figure 23 iSCSI controller properties: IP Ports tab Setting the date and time on the MPX200 Setting the date and time on the MPX200 ensures the synchronization of events and assists in troubleshooting. You have three options for setting the date and time (see Figure 24 (page 36)).
Page 36: Code Load
Figure 24 Set iSCSI controller time Code load NOTE: HP recommends that you load the latest MPX200 firmware. See http://www.hp.com/ go/hpsc for updates. You load the firmware from the P6000 Command View Code Load page for the iSCSI controller. Firmware is loaded for the selected controller only; for a dual-blade configuration, you must perform this procedure for each blade.
Page 37: Shutting Down And Restarting The Mpx200
Figure 25 Code Load page for the iSCSI controller Shutting down and restarting the MPX200 If you need to restart the MPX200, select the General tab, and then click Restart. If you need to shut down the MPX200, click Shut down. See Figure 26 (page 37).
Page 38: Locating The Mpx200
10. Management port 10/100/1000 Ethernet To enable or disable the locating beacon: Select the iSCSI controller. Click Locate. Click Locate ON or Locate OFF, and then click OK (Figure 29 (page 39)). Managing MPX200 iSCSI using HP P6000 Command View...
Page 39: Removing An Iscsi Controller
Figure 29 Locate hardware device Removing an iSCSI controller Before you remove an iSCSI controller permanently, ensure that all virtual disk presentations have been removed. To remove an iSCSI controller: Select the iSCSI controller. Click Set Options. Select Remove controller, and then click OK. (see Figure 30 (page 39)).
Page 40: Managing Mpx200 Iscsi For 3Par Storeserv Storage
3PAR StoreServ 10000/7000, 3PAR T-Class/F-Class Storage. For more information, see “MPX200 iSCSI configuration rules and guidelines” (page 52). Setting up the MPX200 management port Access to the MPX200 CLI is required for initial setup. Connect to the CLI through one of the following: RS-232 serial port (1 15200/8/n/1) Telnet When connected, select the blade to manage by using the blade <1 | 2>...
Page 41: Setting Up The Iscsi Ports
Figure 34 The set iscsi command Fibre Channel zoning Use the following diagram as a guide to implement zones. Use the show vpgroups command to determine the MPX200 WWNs used in zoning (see Figure 35 (page 42)). Zones include WWNs from the MPX200 and the 3PAR array ports.
Page 42: Lun Provisioning
LUN provisioning LUN masking for MPX200 connectivity to a 3PAR array is accomplished by executing the following procedure in which the MPX200 is treated as if it were a Windows FC host to the 3PAR array. NOTE: To properly set up LUN masking, you must create a host that includes the WWNs from a single VPG.
Page 43 Figure 36 The show vpgroups command Using the InForm Management Console, create a host and add only WWNs that belong to the same VPG. There can be up to four hosts that represent the MPX200. NOTE: Figure 37 (page 43) shows an example with eight connections from the MPX200 to the array.
Page 44 Perform a Discovery of an iSCSI port on each MPX200 blade from the initiator to register the initiator IQN. Download, install, and run the mpx Manager. NOTE: Although you can accomplish LUN masking using either the mpx Manager GUI or the command line, the mpx Manager is the preferred method.
Page 45: Setting Up The Iscsi Initiator
45). Be sure to run this command for each 3PAR target port on each blade. Figure 40 The lunmask add command Setting up the iSCSI initiator For instructions to configure the iSCSI host, see the HP 3PAR Implementation Guide that pertains to your operating system, available at http://h20000.www2.hp.com/bizsupport/TechSupport/ DocumentIndex.jsp?lang=en&cc=us&prodClassId=- 1 &contentType=SupportManual&...
Page 46: Managing Mpx200 Iscsi For Xp24000/20000
“MPX200 iSCSI configuration rules and guidelines” (page 52). Setting up the MPX200 management port Access to the MPX200 CLI is required for initial setup. Connect to the CLI through one of the following: RS-232 serial port (1 15200/8/n/1) Telnet By default, the management port obtains a DHCP address. If the management port cannot obtain a DHCP address, you must set a static IP address.
Page 47: Setting Up The Iscsi Ports
Fibre Channel zoning “Fibre Channel zoning” (page 31) “Fibre Channel switch-based zoning” (page 32) zoning information. WWNs used in zoning can be found in the MPX200 using the show vpgroups command (see Figure 45 (page 48)). Setting up the iSCSI ports...
Page 48: Lun Management
Figure 45 The show vpgroup command LUN management LUN masking for MPX200 connectivity to XP is accomplished by executing the following procedure. The MPX200 is treated as if it were a Windows FC host to the XP. Managing MPX200 iSCSI for XP24000/20000...
Page 49 To identify which WWNs belong to a VPG see the fourth bit (circled in Figure 46 (page 49)). You can create up to four groups, each containing WWNs from each VPG from each MPX200 blade. LUNs can be created and assigned to the groups at this time. Figure 46 LUN management window Install the Microsoft iSCSI Initiator software.
Page 50 Figure 47 LUN Selection window Expand the desired ports and select the same LUN from each (see Figure 48 (page 50)). Figure 48 Expanded ports Select the initiator and finish (see Figure 49 (page 51)). Managing MPX200 iSCSI for XP24000/20000...
Page 51 Figure 49 Select the Initiators Follow the steps beginning with Step 5 to log in to the target. LUN management...
Page 52: Mpx200 Iscsi Configuration Rules And Guidelines
Each P6000 EVA storage system can connect to a maximum of one MPX200 chassis (two blades). Each P6000 EVA controller host port can connect to a maximum of two MPX200 Fibre Channel ports. MPX200 iSCSI configuration rules and guidelines...
Page 53: Hp P6000 Command View Management Rules And Guidelines
A maximum of one MPX200 chassis (two blades) can be zoned with up to four P6000 EVA storage systems. A P6000 EVA storage system can present LUNs to iSCSI initiators and Fibre Channel hosts concurrently. HP P6000 Command View management rules and guidelines...
Page 54: Features Not Supported For Iscsi Hosts
CLI support to enter replication commands from iSCSI hosts Features not supported for iSCSI hosts LUNs that are presented to iSCSI hosts through the MPX200, and that require a host agent on the iSCSI initiator, do not support advanced replication features because there are no iSCSI replication host agents available.
Page 55: Fibre Channel Switch And Fabric Support
FC switch. Each XP storage system can connect to a maximum of one MPX200 chassis (two blades). A maximum of one MPX200 chassis (two blades) can be zoned with up to four XP storage systems. XP and P6000 EVA storage systems can connect to the same MPX200, The total allowable number of storage systems is four per MPX200 chassis.
Page 56: Iscsi Initiator Rules And Guidelines
This section describes the iSCSI initiator rules and guidelines for Apple Mac OS, Microsoft Windows, Linux, Solaris, and VMware. General iSCSI initiator rules and guidelines follow: iSCSI initiators and MPX200 iSCSI ports can be in different IP subnets. This requires setting the MPX200 iSCSI gateway feature. For more information, see “MPX200 configuration options...
Page 57: Linux Iscsi Initiator Rules And Guidelines
Use Registry Editor at your own risk. Back up the registry before you make any changes. NOTE: The registry parameters are set automatically by the HP StorageWorks MPX200 for Enterprise Virtual Array Windows software kit, which is available at http://h18006.www1.hp.com/ products/storageworks/evaiscsiconnect/index.html...
Page 58: Supported Ip Network Adapters
Network protocol: TCP/IP IPv6 or IPv4, Ethernet 1,000 Mb/s or 10 GbE NOTE: If you configure IPv6 on any MPX200 iSCSI port, you must also configure IPv6 on the HP Command View management server. IP data—LAN/VLAN supported with less than 10 ms latency; maximum of two VLANs per port, one VLAN per protocol IP management—LAN/WAN supported...
Page 59: Windows Server Iscsi Initiator
For Windows Server 2012, 2008, the iSCSI initiator is included with the operating system. For Windows Server 2003, you must download and install the iSCSI initiator (version 2.08 recommended). Install the HP StorageWorks MPX200 iSCSI kit. Start the installer by running Launch.exe. (If you are using a CD-ROM, the installer should start automatically.) Click Install iSCSI software package.
Page 60 Click the Microsoft iSCSI Initiator icon to open the Control Panel applet. The iSCSI Initiator Properties window opens. Select the Discovery tab. See Figure 52 (page 60) Figure 53 (page 61). Figure 52 iSCSI initiator properties: Discovery tab (Windows 2003) MPX200 iSCSI configuration rules and guidelines...
Page 61 In the Target Portals section, click Add (Windows 2003) or Discover Portal (Windows 2012, 2008). A dialog box opens. Enter the iSCSI port IP address. Click OK. The discovery is complete. In HP P6000 Command View, set up the iSCSI host and virtual disks. Setting up the iSCSI initiator...
Page 62 NOTE: For Windows 2012, select the default operating system “Windows” as the host mode in Command View, then go to the MPX200 CLI and change the host mode of this host to “Windows 2012”. MPX200 iSCSI configuration rules and guidelines...
Page 63 Create a virtual disk and present it to the host you created in Step 4.c. Note the circled number in the target IQN; it is referenced during initiator login. See Figure 55 (page 63) Figure 56 (page 63). Figure 55 Virtual disk properties Figure 56 Host details Setting up the iSCSI initiator...
Page 64 Select the Targets tab and then click the Refresh button to see the available targets. See Figure 57 (page 64) Figure 58 (page 65). The status should be Inactive. Figure 57 Targets tab (Windows 2003) MPX200 iSCSI configuration rules and guidelines...
Page 65: Multipathing
Select the Multipathing check box to enable MPIO. The target status is Connected when logged in. NOTE: HP recommends using the Advanced button to choose the Local Adapter, Source IP, and Target Portal. The Target Portal IP Address is the iSCSI port that this initiator connection is defined.
Page 66: Installing The Mpio Feature For Windows Server 2012, 2008
NICs and a separate network infrastructure (cables, switches, and MPX200 blades). HP recommends using separate target ports. Microsoft MPIO allows the initiator to log in to multiple sessions to the same target and aggregate the duplicate devices into a single device exposed to Windows. Each session to the target can be established using different NICs, network infrastructure, and target ports.
Page 67 Select the Multipath I/O check box on the Select Features page (Figure 59 (page 67)). Figure 59 Select Features page Click Next, and then click Install. After the server reboots, add support for iSCSI devices using the MPIO applet (Figure 60 (page Figure 61 (page 68)).
Page 68: Installing The Mpio Feature For Windows Server 2003
Microsoft MPIO component, leave the other check boxes blank; select only the Microsoft MPIO check box. NOTE: After the installation is complete, you must reboot the system. MPX200 iSCSI configuration rules and guidelines...
Page 69: Microsoft Windows Server 2003 Scalable Networking Pack
SNP also includes the Receive Side Scaling feature, which allows receive packet processing to scale across multiple CPUs. The HP NC3xxx Multifunction Gigabit server adapters use SNP to support TCP off-load functionality. For support details, see the latest HP adapter information at http://h18004.www1.hp.com/...
Page 70: Setting Up The Iscsi Initiator For Apple Mac Os X
(Figure 63 (page 70)). Figure 63 Discover targets Enter the static IP address of the mpx iSCSI port in the Address box, and then click Finish (Figure 64 (page 70)). Figure 64 Add static IP address MPX200 iSCSI configuration rules and guidelines...
Page 71 Select a target from the Discovered Targets list and then click Add (Figure 65 (page 71)). Figure 65 Discovered Targets list NOTE: The mpx iSCSI port may present several iSCSI targets to the Xtend SAN iSCSI Initiator. Select only one target from the list. For ISNS discovery Select Initiator and then enter the iSNS name or IP address in the box (Figure 66 (page...
Page 72 Select the Visible check box to allow the initiator to display the target status (Figure 68 (page 73)). Select the Auto Login check box to configure the initiator to automatically log in to the iSCSI target at system startup. MPX200 iSCSI configuration rules and guidelines...
Page 73 Click Save. Figure 68 Selecting the newly added target Click Status, select the network node, and then click Login to connect to the MPX target (Figure 69 (page 73)). The target status is Connected and the target status light turns green. Figure 69 Select status Setting up the iSCSI initiator...
Page 74: Setting Up Storage For Apple Mac Os X
Verify that the P6000 EVA LUNs are presented to the Xtend SAN iSCSI Initiator: Open the Xtend SAN iSCSI application. Select the MPX200 target entry under the host name. Click LUNs. A list of presented P6000 EVA LUNs is displayed (Figure 70 (page 74)).
Page 75 Figure 71 Configure the iSCSI initiator and targets Select the Discovered Targets tab and enter the iSCSI target IP address (Figure 72 (page 75)). Figure 72 Discovered Targets tab Log in to the target (Figure 73 (page 76)). Setting up the iSCSI initiator...
Page 76 Figure 73 Log in to the target Select the Connected Targets tab, and then click the Toggle Start-Up button for each target listed so the targets start automatically (Figure 74 (page 76)). Figure 74 Connected Targets tab MPX200 iSCSI configuration rules and guidelines...
Page 77: Installing And Configuring The Iscsi Driver For Red Hat 5
Installing the iSCSI initiator for Red Hat 3 and SUSE 8 If you are upgrading from a previous version of an iSCSI driver, HP recommends that you remove the /etc/<initiatorname>.iscsi file before installing the new driver. For the latest version of the Linux driver for P6000 EVA iSCSI connectivity, see: http://sourceforge.net/projects/linux-iscsi...
Page 78: Assigning Device Names
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 if the driver is restarted repeatedly. MPX200 iSCSI configuration rules and guidelines...
Page 79: Mounting File Systems
Mapping inconsistencies can occur between SCSI device nodes and iSCSI targets (for example, the wrong device is mounted because of device name changes resulting from iSCSI target configuration changes or network delays). Instead of directly mounting SCSI devices, HP recommends that you do one of the following: Mount the /dev/iscsi symlink tree.
Page 80: Iscsi Initiator Setup For Vmware
Initiator setup for VMware The software iSCSI Initiator is built into the ESX server VMkernel and uses standard 10GigE/GigE NICs to connect to the MPX200. To set up software-based iSCSI storage connectivity: Install the appropriate license from VMware to enable iSCSI software driver using the VMware instructions.
Page 81 Figure 76 Firewall Properties dialog box Enable the iSCSI software initiators: In the VMware VI client, select the server from the inventory panel. Click the Configuration tab, and then click Storage Adapters under Hardware. Under iSCSI Software Adapter, choose the available software initiator. Click the Properties link of the software adapter.
Page 82 The Add Send Target Server dialog box is displayed. See “Add Send Target Server dialog box” (page 82). Enter the iSCSI IP address of the MPX200. Click OK. Figure 78 Add Send Target Server dialog box MPX200 iSCSI configuration rules and guidelines...
Page 83: Configuring Multipath With The Solaris 10 Iscsi Initiator
Configuring multipath with the Solaris 10 iSCSI initiator This section explains how to configure multipath with the Solaris 10 iSCSI initiator to the MPX200. For details on managing and troubleshooting Solaris iSCSI multipath devices, see the Solaris System Administration Guide: Devices and File Systems, available at http://dlc.sun.com/pdf/817-5093/...
Page 84: Preparing The Host System
# mpxio-disable="yes"; mpxio-disable="no"; Enabling MPxIO for an HP P6000 EVA storage array This section explains how to configure a Solaris server to recognize an HP storage array in an iSCSI multipath environment with the MPX200. Editing the scsi_vhci.conf file HP storage arrays are supported with MPxIO:...
Page 85 # reboot -- -r Editing the sgen.conf file To ensure that the HP storage arrays are recognized by Solaris as SCSI controllers, you must add information to the /kernel/drv/sgen.conf file: Use a text editor to modify the configuration file. For example: # vi /kernel/drv/sgen.conf...
Page 86: Enable Iscsi Target Discovery
Creating an sgen driver alias The HP storage array is a self-identifying SCSI device and must be bound to the sgen driver using an alias. Execute the following procedure to create an sgen driver alias: Update the sgen driver: # update_drv –a –I “scsiclass,0c”...
Page 87: Modifying The Target Parameter Maxrecvdataseglen
Verify that SendTargets is enabled: # iscsiadm list discovery The MPX200 has multiple iSCSI ports available to the Solaris iSCSI initiator. To discover the targets available, enter the following command for each iSCSI port IP address that the iSCSI initiator accesses: #iscsiadm add discovery-address ‘iscsi port IP address’...
Page 88: Monitoring The Multipath Devices
Data Digest: NONE/- Configured Sessions: 1 Monitoring the multipath devices After HP P6000 Command View has presented the virtual disks to the Solaris host, enter the following commands to monitor the configuration: iscsiadm list target -S This command lists targets with their presented LUNs. In a multipath environment, the same LUN should appear under different P6000 EVA port targets from the same controller.
Page 89: Configuring Microsoft Mpio Iscsi Devices
600508b4000b15a200005000038e0000 Asymmetric: Current Load Balance: none Logical Unit Group ID: Auto Failback: Auto Probing: Paths: Initiator Port Name: iqn.1986-03.com.sun:01:sansun-s04,4000002a00ff Target Port Name: 4000002a0000,iqn.1986-03.com.hp:fcgw.mpx200.0834e00028. b2.01.50014380025c4179 Override Path: Path State: Disabled: Initiator Port Name: iqn.1986-03.com.sun:01:sansun-s04,4000002a00ff Target Port Name: 4000002a0000,iqn.1986-03.com.hp:fcgw.mpx200.0834e00028. b1.01.50014380025c417d Override Path:...
Page 90: Microsoft Mpio For Iscsi Load-Balancing Policies
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 on the QLogic iSCSI HBA, it is not necessary to install the Microsoft iSCSI initiator. MPX200 iSCSI configuration rules and guidelines...
Page 91: Installing The Qlogic Iscsi Hba
Installing the QLogic iSCSI HBA Install the QLogic iSCSI HBA hardware and software following the instructions in the QLogic installation manual. The QLogic iSCSI HBA is managed by the QLogic SANsurfer Management Suite (SMS). NOTE: After installing the QLogic iSCSI HBA, you must configure the QLogic iSCSI initiator through SMS.
Page 92 Configure the HBA Port network settings. Configure the HBA Port DNS settings (optional). Configure the SLP Target Discovery settings (optional). Configure the iSNS Target Discovery settings (optional). Figure 82 Connect to Host window Figure 83 Start general configuration wizard MPX200 iSCSI configuration rules and guidelines...
Page 93: Adding Targets To The Qlogic Iscsi Initiator
93)). Enter the first iSCSI target port IP address. Figure 84 HBA Port Target Configuration window Repeat steps 1 and 2 for each MPX200 you want to add. Click Next. To activate the changes, enter the SMS password: config. Select the Target Settings tab. Verify that the HBA state is Ready, Link Up and that each target...
Page 94: Presenting Luns To The Qlogic Iscsi Initiator
Follow the procedure in the Installation and Reference Guide, available at http:// h20000.www2.hp.com/bizsupport/TechSupport/DocumentIndex.jsp?contentType=SupportManual& lang=en&cc=us&docIndexId=64179&taskId=101&prodTypeId=18964&prodSeriesId=421492. After installing the HP MPIO Full Featured DSM for P6000 EVA, open Computer Management to view and control the iSCSI LUNs (Figure 87 (page 95)). MPX200 iSCSI configuration rules and guidelines...
Page 95: Microsoft Windows Cluster Support
Figure 87 HP MPIO DSM Manager with iSCSI devices Microsoft Windows Cluster support Microsoft Cluster Server for Windows 2003 iSCSI Failover clustering is supported on the HP StorageWorks MPX200 Multifunction Router. For more information, see http://www.microsoft.com/windowsserver2003/technologies/storage/ iscsi/iscsicluster.mspx. Requirements Operating system: Windows Server 2003 Enterprise, SP2, R2, x86/x64 Firmware: Minimum version—3.1.0.0, released November 2009...
Page 96: Microsoft Cluster Server For Windows 2008
Value Node 1 Node 2 Node 3 Node 4 When the HP Full Featured DSM for P6000 EVA is installed, Persistent Reservation is set in the registry by default. For more information on the HP DSM, see http://h20000.www2.hp.com/ bizsupport/TechSupport/DocumentIndex.jsp?contentType=SupportManual&lang=en&cc=us& docIndexId=64179&taskId=101&prodTypeId=18964&prodSeriesId=421492 Microsoft Cluster Server for Windows 2008 iSCSI Failover clustering is supported on the HP MPX200 Multifunction Router.
Page 97: Setting Up Authentication
Maximum length of 100 characters Minimum length of 1 character Entering an IQN using the HP P6000 Command View add host tab requires the iSCSI initiator to have been registered in the iSCSI or iSCSI/FCoE module's initiator database. Setting up authentication...
Page 98: Microsoft Initiator Chap Secret Restrictions
CHAP is enforced on both discovery and normal sessions. MPX200 CHAP modes The MPX200 supports two CHAP modes. Once CHAP is enabled, it is enforced for both discovery sessions and normal sessions. You can choose only the CHAP mode: Single-direction—The target authenticates the identity of the initiator with the user-provided CHAP secret.
Page 99: Enabling Single-Direction Chap During Discovery Session And Normal Session
If the iSCSI initiator is not listed when you execute the set chap command, do one of the following: ◦ From HP P6000 Command View, select Hosts, and then select the Add Host tab. Enter the IQN string. ◦ From the CLI, use the add command to add the iSCSI initiator that will perform the discovery.
Page 100: Enabling Chap For The Mpx200-Discovered Iscsi Initiator Entry
Enter the CHAP secret for the MPX200-discovered iSCSI initiator in the Target Secret box. Click OK. Click OK again. The initiator completes normal login. Enabling CHAP for the MPX200-discovered iSCSI initiator entry You must use the CLI to enable CHAP for the MPX200-discovered iSCSI initiator entry:...
Page 101: Enabling Chap For The Open-Iscsi Iscsi Initiator
[root@sanergy33 iscsi]# iscsiadm -m discovery -t sendtargets -p 10.10.1.23 Use the iscsiadm command to log in to the iSCSI target. For example: [root@sanergy33 iscsi]# iscsiadm --mode node --targetname iqn.1986-03.com.hp:fcgw.mpx200.0840e00002. b1.01.50001fe15006ac39 --login The following is a sample iscsid.conf file for CHAP: # *************...
Page 102: Enabling Single-Direction Chap During Discovery Session And Bidirectional Chap During Normal Session
NOTE: These are examples of secret settings. Configure CHAP using settings that apply to your network environment. Enable CHAP for the MPX200 discovered iSCSI initiator entry (CHAP can be enabled via CLI only). If the iSCSI initiator is not listed under the set chap command, do one of the following: From HP P6000 Command View, select Hosts, and then select the Add Host tab.
Page 103 Select the appropriate target for login. Click Log On. Click Advanced. Select the CHAP Login Information check box. Enter the CHAP secret for the MPX200 discovered iSCSI initiator in the Target Secret box (for example: CHAPsecret01). Select the Mutual Authentication check box. m. Click OK.
Page 104: Enabling Bidirectional Chap During Discovery Session And Single-Direction Chap During Normal Session
NOTE: These are examples of secret settings. Configure CHAP using settings that apply to your network environment. Enable CHAP for the MPX200 discovered iSCSI initiator entry (CHAP can be enabled via CLI only). If the iSCSI initiator is not listed when you execute the set chap command, do one of the following: From HP P6000 Command View, select Hosts, and then select the Add Host tab.
Page 105: Enabling Bidirectional Chap During Discovery Session And Bidirectional Chap During Normal Session
Select the appropriate target for login. Click Log On. Click Advanced. Select the CHAP Login Information check box. Enter the CHAP secret for the MPX200 discovered iSCSI initiator in the Target Secret box (for example, CHAPsecret01). m. Select the Mutual Authentication check box. Click OK.
Page 106 NOTE: These are examples of secret settings. Configure CHAP using settings that apply to your network environment. Enable CHAP for the MPX200 discovered iSCSI initiator entry (CHAP can be enabled via CLI only): If the iSCSI initiator is not listed when you execute the set chap command, do one of the following: From HP P6000 Command View, select Hosts and then select the Add Host tab.
Page 107 Select the appropriate target for login. Click Log On. Click Advanced. Select the CHAP Login Information check box. Enter the CHAP secret for the MPX200 discovered iSCSI initiator in the Target Secret box (for example: CHAPsecret01). m. Select the Mutual Authentication check box. Click OK.
Page 108: Mpx200 Fcip
P6000/EVA, and XP storage system families and Remote Copy and HP Continuous Access software, the MPX200 enables long-distance remote replication for disaster tolerance. A base FCIP configuration consists of a minimum of two MPX200 blades, one for the local site and one for the remote site.
Page 109: Using Fcip To Encapsulate Fc Packets
FCIP blade and a shared iSCSI/FCIP blade. A dedicated MPX200 blade running only FCIP does not have any impact on a dedicated MPX200 blade running iSCSI. There is, however, an impact and possibly changes required for existing MPX200 iSCSI configurations when FCIP is added to the same blade.
Page 110: Fcip And Iscsi Performance
FC port available for iSCSI. Therefore, only the targets from one fabric or the other will be available to iSCSI initiators connected to that MPX200 blade; access to targets on the other fabric are through another MPX200 blade.
Page 111: Mpx200 Iscsi/Fcip Configurations
Integrated Routing. This provides fabric isolation between the local and remote fabrics, allowing device access without merging the fabrics. This can be implemented in all supported MPX200 FCIP configurations using B-series Fibre Channel switches with Integrated Routing or B-series routers configured for Fibre Channel routing.
Page 112 MPX200 with FCIP and C-series switches with IVR. This provides fabric isolation between the local and remote fabrics, allowing device access without merging the fabrics. This can be implemented in all supported MPX200 FCIP configurations using C-series Fibre Channel switches with IVR.
Page 113 Figure 97 MPX200 high-availability configuration with fully-redundant long-distance links Figure 98 MPX200 configuration with remote IP Distance gateway (mpx1 10) Figure 99 MPX200 highly-redundant configuration with one or two long-distance lists MPX200 iSCSI/FCIP configurations 1 13...
Page 114 Figure 100 MPX200 highly redundant pairs of gateways with fully-redundant long-distance links Figure 101 MPX200 simultaneous iSCSI and FCIP with remote dedicated FCIP blade 1 14 MPX200 FCIP...
Page 115: Hp Continuous Access 3-Site Configurations
Figure 102 MPX200 simultaneous iSCSI and FCIP, both local and remote Figure 103 MPX200 iSCSI and FCIP dedicated blades, both local and remote HP Continuous Access 3-site configurations This section describes the following HP Continuous Access 3-site configurations: HP Continuous Access 3-site configuration with four MPX200 routers...
Page 116: 3-Site Configuration With Four Mpx200 Routers
MPX200 routers. Figure 106 (page 118) shows the highest level of 3-site connectivity using eight MPX200 routers. Figure 107 (page 119) is similar to Figure 105 (page 117), with additional connectivity to allow for replication between Site 2 and Site 3.
Page 117: 3-Site Configuration With Eight Mpx200 Routers
Figure 105 HP Continuous Access 3-site configuration with six MPX200 routers 3-site configuration with eight MPX200 routers The configuration in Figure 106 (page 118) provides the highest 3-site redundancy, with a dedicated MPX200 pair for all long-distance links to all three sites.
Page 118: 3-Site Configuration With Six Mpx200 Routers And Full Inter-Site Connectivity
Figure 106 HP Continuous Access 3-site configuration with eight MPX200 routers 3-site configuration with six MPX200 routers and full inter-site connectivity Figure 107 (page 119) provides long-distance link redundancy and full connectivity between all three sites. 1 18 MPX200 FCIP...
Page 119: Fcip Configuration Rules And Guidelines
IP network. HP does not support FCIP connectivity between other gateway models. FCIP is supported on GbE ports only. For the MPX200 1 GbE blade, ports GE1, GE2, GE3, and GE4 are GbE. For the MPX200 10 GbE blade, ports GE1 and GE2 are GbE.
Page 120: Storage System Rules And Guidelines
Storage system rules and guidelines The MPX200 Multifunction Router configured for FCIP is supported for use with the following HP Continuous Access storage systems: ◦ EVA4400/4400 with embedded switch ◦ EVA4000/4100/6000/6100/8000/8100 ◦ EVA6400/8400 ◦ P6300/P6350/P6500/P6550 ◦ EVA3000/5000 ◦ P9500 ◦...
Page 121: Fc Switch Requirements
“Storage system rules and guidelines” (page 120). For MPX200 IP data—Local and remote pairs are supported for up to 100 ms of IP network delay one-way, or 200 ms round-trip for HP Continuous Access. HP requires dedicated IP bandwidth (see Table 20 (page 121)).
Page 122: Distance
45 Mb/s and 15 Mb/s is allocated to network traffic, the remaining 30 Mb/s is available for FCIP. If in this example the MPX200 is configured for two routes, based on the 30 Mb/s total bandwidth available for FCIP, you would set the MPX200 bandwidth parameter to 15, the available bandwidth for each FCIP route.
Page 123: Compression
Modifying the window size and scaling factor The MPX200 window size can be set to a maximum of 32 KB. The scaling factor is used as a multiplier to increase the window size above 32 KB. Modify the window size and scaling factor in the MPX200 Multifunction Router pairs based on the WAN RTT and link speed.
Page 124: Tcp Window Size And Scaling Factor Recommendations
Round trip time (RTT) in ms Window size (bytes) Scaling factor (2 1 or less Table 23 T3/DS-3 45 Mb/sec (bandwidth = 43 Mb) Round trip time (RTT) in ms Window size (bytes) Scaling factor (2 512K 256K 124 MPX200 FCIP...
Page 125 Table 23 T3/DS-3 45 Mb/sec (bandwidth = 43 Mb) (continued) 128K 128K 128K 1 or less Table 24 OC-1 50 Mb/sec (bandwidth = 50 Mb) Round trip time (RTT) in ms Window size (bytes) Scaling factor (2 512K 256K 128K 128K 128K 1 or less...
Page 126: Fcip Link Diagnostics
Table 28 OC-24 and above 1.244 Gb/sec (bandwidth = 1000 Mb) Round trip time (RTT) in ms Window size (bytes) Scaling factor (2 512K 1 or less 128K FCIP link diagnostics For information on FCIP diagnostics, see “WANLink diagnostic” (page 145). 126 MPX200 FCIP...
Page 127: Configuring An Fcip Route
FCIP configuration” (page 108)): HP MPX200 Multifunction Router 1-GbE Base Chassis or HP MPX200 Multifunction Router 10- 1 GbE Base Chassis. Note that FCIP is currently supported only on MPX200 1 GbE ports. HP MPX200 Half Chassis FCIP License Continuous Access EVA...
Page 128: Step 3. Rack-Mount The Mpx200
MPX200 configuration parameters. You can connect the MPX200 management port to an IP switch, a hub, or directly to the workstation using an Ethernet crossover cable. If you are using the MPX200 serial port, the settings are 1 15,200 baud, 8 bit, 1 stop bit, no parity, and no flow control.
Page 129: Step 6. Configure The Mpx200 Fcip Route Parameters
Step 6. Configure the MPX200 FCIP Route parameters Install FCIP license For each MPX200 chassis, select the blade with the serial number used to obtain either the Full or Half Chassis License and add the FCIP license as shown in Figure 109 (page 129).
Page 130: Critical Fcip Performance Settings
121). NOTE: HP recommends that you accept the default settings for TCP Port and GE Port Speed. If you need to change the port speed, select Full Duplex mode; Half Duplex mode is not supported. The Ethernet switch port settings must be set to match the MPX GE port settings.
Page 131: Step 7. Configure Fc Switch Settings For The Mpx200
113). NOTE: Use a standard Cat 5e straight network cable to connect MPX200 GE ports to an IP switch port. Use a Cat 5e crossover network cable to directly connect two MPX200s through their respective GE ports without an IP switch.
Page 132: Step 9. Verify Fcip Links And Firmware Version
Step 9. Verify FCIP links and firmware version To determine whether a firmware upgrade is necessary, go to the SPOCK website at http:// www.hp.com/storage/spock. You must sign up for an HP Passport to enable access. Upgrade accordingly. Use the CLI ping command to verify FCIP link connectivity.
Page 133: Mpx200 Fcoe Feature Description
9 MPX200 FCoE feature description The HP MPX200 Multifunction Router provides FCoE target functionality. Used with the HP arrays, the MPX200 enables FCoE connectivity over a 10-GbE link at no additional cost. FCoE features include: 10-GbE model only Support enabled with firmware version 3.2.2.0 (minimum) by default, no license required...
Page 134: Setting Up For Fcoe Connectivity To Hp P6000 Evas
For information regarding switch setup, see the Fibre Channel Over Ethernet chapter of the HP SAN Design Reference Guide, available at: http://www.hp.com/go/sdgmanuals The MPX200 10-GbE ports must be connected to the FCoE switch, as described in the section “FCoE configurations” (page 133).
Page 135 Create an FCoE zone. Zone the WWNN from the MPX200 FCoE port from each blade and the host CNA. If multiple fabrics exist, create zones where redundancy requires it. There are two ways to identify the FCoE ports on the MPX200:...
Page 136 Use the Add a Host function to create the FCoE host entry. Name the host. In the Type field, select FCoE. Select the WWNN that belongs to the host. Select the appropriate operating system. Click Add Host (see Figure 1 14 (page 137)). 136 MPX200 FCoE feature description...
Page 137 Note that the host has its own icon. Each host entry has only one WWPN associated with it, so any host with multiple port CNAs must have an entry for each (see Figure 1 15 (page 137)). Figure 1 15 Host properties Setting up for FCoE connectivity to HP P6000 EVAs 137...
Page 138: Setting Up Fcoe Connectivity To 3Par Arrays
Figure 1 16 Host Details display Setting up FCoE connectivity to 3PAR arrays Before executing the following procedure, ensure that MPX200 host has been created in the InForm Management Console as described in “Managing MPX200 iSCSI for 3PAR StoreServ Storage”...
Page 139 NOTE: Because the same array port worldwide names can be exposed through both MPX200 blades to the fabric, you must create a new target alias. Using the mpx Manager, start the Target Map Wizard: On the Select a Target page, expand an array port, and then select a VPGROUP (the...
Page 140 Step Figure 1 18 3PAR MPX zoning — FCoE Use the InForm Management Console to provision LUNs to the MPX200 host. You can now use the mpx Manager LUN Presentation Wizard for LUN presentation to the initiator.
Page 141: 10 Diagnostics And Troubleshooting
Replace the MPX200 blade. System Fault LED is illuminated The System Fault LED is illuminated when a fault exists in the MPX200 firmware or hardware. If the System Fault LED is illuminated, check the Heartbeat LED for an error blink pattern and take the necessary actions.
Page 142: Fibre Channel Port Leds
The Heartbeat LED indicates the operational status of the MPX200. When the POST completes with no errors, the Heartbeat LED blinks at a steady rate of once per second. When the MPX200 is in maintenance mode, the Heartbeat LED blinks continuously. The blink patterns that indicate critical errors are described in the following sections.
Page 143: Over-Temperature Blink Pattern
Over-temperature blink pattern An over-temperature condition is indicated by a five-blink pattern followed by a two-second pause. The five-blink pattern indicates that the air temperature inside the MPX200 has exceeded the failure temperature threshold of 70 °C (Figure 123 (page 143)).
Page 144: Locating The Mpx200 Blade
Locating the MPX200 blade A flashing blue LED indicates that the MPX200 blade beacon is ON. There are two ways to identify the location of an MPX200 blade: Enter the CLI command beacon on (Figure 124 (page 144)). Figure 124 Using the beacon on command to locate an MPX200 blade In HP P6000 Command View, select the General tab, and then click the Locate button.
Page 145: Fcip Route Link Failure - Event Log Entries
Tue Feb 05 23:54:39 EST 2013 FCIP FcipRoute#0: In last 10 number of outstanding FC Frames. secs TCP Timer Expired=1 Fast Retransmissions=59 OutStanding Completions=0 FC Frames WANLink diagnostic NOTE: This command is only supported for use with MPX200 1 GbE ports. MPX200 chassis diagnostics 145...
Page 146: Troubleshooting Using Hp P6000 Command View
FCIP Route(s). For example, if when testing the WAN link the diagnostic determines there is a 100 Mbps of UDP bandwidth and this link is shared with two pairs of MPX200 routers, then each pair of MPX200 routers would be configured for 50 Mbps or one-half the total bandwidth.
Page 147: Issues And Solutions
Solution 3: Ensure that the HP P6000 Command View station is on the same subnet as the management ports. Solution 4: Enter the known IP address of the management port of the iSCSI controller in the HP P6000 Command View discovery screen.
Page 148: Initiator Logs In To Mpx200 Iscsi Target, But P6000 Eva-Assigned Luns Do Not Appear On Initiator
Figure 128 iSCSI controller properties: IP Ports tab Initiator logs in to MPX200 iSCSI target, but P6000 EVA-assigned LUNs do not appear on initiator Solution 1: The initiator must log in to the target to which the P6000 EVA LUN was assigned.
Page 149: Windows Initiators May Display Reconnecting If Nic Mtu Changes After Connection Has Logged In
If only the IPv6 management port IP address is set, enter a valid IPv6 management IP address under Mgmt Port, and then click Save changes. NOTE: If you configure IPv6 on any MPX200 iSCSI port, you must also configure IPv6 on the HP P6000 Command View management server. HP P6000 Command View issues and solutions...
Page 150: Virtual Disk Operation Troubleshooting
P6000 EVA. Not a supported configuration. The specified MPX200 A P6000 EVAFC host exists of which the MPX200 FC port controller host port does not exist. is a member. Locate the FC host and remove the port.
Page 151: 1 Support And Other Resources
HP Enterprise Virtual Array user guide for your array HP SAN Design Reference Guide HP 9500 and XP storage system user guides You can find the documents referenced in this guide on the Manuals page of the HP Business Support Center website: http://www.hp.com/support/manuals For P6000 EVA documents, under Storage, select Disk Storage Systems, and then under EVA P6000 Storage, select HP EVA P6000 Storage.
Page 152: Subscription Service
Operating system type and revision level Detailed questions Subscription service HP recommends that you register your product at the Subscriber's choice for business website: http://www.hp.com/go/e-updates After registering, you will receive email notification of product enhancements, new driver versions, firmware updates, and other product resources.
Page 153: Rack Stability
In multiple-rack installations, fasten racks together securely. Extend only one rack component at a time. Racks can become unstable if more than one component is extended. Product warranties For information about HP product warranties, see the warranty information website: http://www.hp.com/go/storagewarranty Rack stability 153...
Page 154: 12 Documentation Feedback
12 Documentation feedback HP is committed to providing documentation that meets your needs. To help us improve the documentation, send any errors, suggestions, or comments to Documentation Feedback (docsfeedback@hp.com). Include the document title and part number, version number, or the URL when submitting your feedback.
Page 155: A Command Reference
A Command reference This chapter lists and describes the MPX200 CLI commands in alphabetical order. Command syntax The MPX200 CLI command syntax uses the following format: 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 not case sensitive.
Page 156: Admin
Telnet, you must either wait for the Admin session to time out, or use the admin cancel command. Example: The following example shows how to open and close an Admin session: MPX200 <1> #> admin start Password : ****** MPX200 <1> (admin) #> MPX200 <1> (admin) #> admin end MPX200 <1> #> 156 Command reference...
Page 157: Beacon
Allows you to select the blade to be managed. This command is valid only at the chassis CLI prompt. The chassis CLI prompt does not include the blade number (for example, MPX200 #>), whereas the blade CLI prompt includes the blade number (for example, MPX200 <1> #>).
Page 158: Exit
[add | mod | rm] Keywords Configure a new FCIP route Modify an existing FCIP route Remove an existing FCIP route Example 1: MPX200 <1> (admin) #> fciproute add A list of attributes with formatting and current values will follow. 158 Command reference...
Page 159 All attribute values for FCIP Route 1 will now be saved. MPX200 <1> (admin) #> Example 2: MPX200 <1> (admin) #> fciproute mod 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.
Page 160: Fru
MPX200 <1> (admin) #> Example 3: MPX200 <2> (admin) #> fciproute rm 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.
Page 161: Help
[factory | mappings] show [chassis] Example 2: The following example shows the help command for the blade: MPX200 <1> #> help admin [begin | end | start | stop | cancel] beacon [ on | off ] date [MMDDhhmmCCYY]...
Page 162: History
Displays a numbered list of the previously entered commands. Authority None Syntax history Example: MPX200 <1> (admin) #> history 1: admin start 2: help 3: history MPX200 <1> (admin) #> Image Updates the router’s firmware image and cleans up (removes) the image files in the router’s /var/ ftp directory.
Page 163: Initiator
-------------- ---------- Blade 1 (local) isr-6200-3_0_0_5.bin Example 3: MPX200 <1> (admin) #> image unpack HP_StorageWorks_MPX200-2_0_0_1.bin Unpack Completed. Please reboot the system for FW to take effect. MPX200 <1> (admin) #> reboot Are you sure you want to reboot the System (y/n): y System will now be rebooted...
Page 164: Logout
CLI displays a series of prompts from which you choose the initiator, target, and LUN. Example 1: The following example shows the lunmask add command: MPX200 <1> (admin) #> lunmask add Index (WWNN/iSCSI Name) ----- ----------------- 0 iqn.1991-05.com.microsoft:server1...
Page 165 Please select a LUN to present to the initiator ('q' to quit): 1 All attribute values that have been changed will now be saved. Example 3: The following example shows the lunmask rm command: MPX200 <1> (admin) #> lunmask rm Index (WWNN,WWPN/iSCSI Name) ----- ----------------------...
Page 166: Passwd
Syntax ping Example: MPX200 <1> (admin) #> ping 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.
Page 167: Reboot
IP addresses, FC and Ethernet port statistics, and passwords. Clears only the LUN mappings mappings Example 1: MPX200 <1>(admin) #> reset factory Are you sure you want to restore to factory default settings (y/n): y Please reboot the System for the settings to take effect Example 2: MPX200 <1>(admin) #>...
Page 168: Set
Each time it generates dump data, the system adds an event log entry. Example 1: MPX200 <1>(admin) #> save capture Debug capture completed. Package is System_Capture.tar.gz Please use FTP to extract the file out from the System.
Page 169: Set Alias
Syntax set alias Example: MPX200 <2> (admin) #> set alias 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.
Page 170: Set Chassis
Syntax set chassis Example: MPX200 <1>(admin) #> set chassis 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.
Page 171 Execution Throttle (Min=16, Max=256) [64 ] Programmed Connection Option: (0=Loop Only, 1=P2P Only, 2=Loop Pref) [Loop Pref ] All attribute values for Port 1 that have been changed will now be saved. Configuring FC Port: 2 ------------------------- Link Rate (0=Auto, 1=1Gb, 2=2Gb) [Auto ] Frame Size (0=512B, 1=1024B, 2=2048B) [2048 ] Execution Throttle (Min=16, Max=256) [64 ] Programmed Connection Option:...
Page 172: Set Features
The number of the iSCSI port to be configured. Example: MPX200 <1>(admin) #> set iscsi 1 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.
Page 173: Set Mgmt
Syntax set mgmt Example 1: MPX200 <1>(admin) #> set mgmt 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.
Page 174: Set Properties
'q' or 'Q' and the ENTER key to do so. CLI Inactivity Timer (0=Disable, 1=15min, 2=60min) [15min ] CLI Prompt (Max=32 Characters) [HP StorageWorks MPX200 ] All attribute values that have been changed will now be saved. Set SNMP Configures general SNMP) properties and eight trap destinations.
Page 175: Set System
Syntax set system Example: MPX200 <1>(admin) #> set system 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.
Page 176: Show
press 'q' or 'Q' and the ENTER key to do so. Configuring VpGroup: 1 ------------------------- Status (0=Enable, 1=Disable) [Enabled ] VpGroup Name (Max = 64 characters) [VPGROUP_1 ] All attribute values for VpGroup 1 that have been changed will now be saved. Configuring VpGroup: 2 ------------------------- Status (0=Enable, 1=Disable) [Disabled ] 0...
Page 177 Displays licensed features. See “show features features command” (page 180). Displays initiator information for iSCSI or FC. See “show initiators [fc or iscsi] initiators command” (page 180). Displays initiators and the LUNs to which they are initiators_lunmask mapped. See “show initiators LUN mask command”...
Page 178: Show Chap
Displays the CHAP configuration for iSCSI nodes. Authority None Syntax show chap Example: MPX200 <1>(admin) #> show chap The following is a list of iSCSI nodes that have been configured with CHAP 'ENABLED': Type iSCSI Node -------- ------------ Init iqn.1991-05.com.microsoft:server1 Show chassis Displays the chassis information and status.
Page 179: Show Fc
Displays the current settings for a particular FCIP route or for all FCIP routes. Authority None Syntax show fciproutes [link_id] Keywords Route number to display [link_id] Example: MPX200 <2> (admin) #> show fciproutes FCIP Route Information ------------------------ FCIP Route FCIP Interfaces Status Enabled FCIP Link Status FC Port GE Port...
Page 180: Show Features
MPX200 <2> (admin) #> Show features Displays any licensed features. Authority None Syntax show features Example: MPX200 <1>#> show features No Feature Keys exist in the system. Show initiators Displays SCSI initiator information for iSCSI. Authority None Syntax iscsi show...
Page 181: Show Iscsi
Authority None Syntax [port_num] show iscsi Keywords [port_num] The number of the iSCSI port. Example: MPX200 <1>(admin) #> show iscsi iSCSI Port Information ------------------------ iSCSI Port Port Status Enabled Link Status iSCSI Name iqn.1986-03.com.hp:fcgw.mpx200.0834e00025.b1.0 Firmware Revision 3.00.01.57 Current Port Speed...
Page 182: Show Logs
01/01/2008 00:00:22 QL4022 3 #0: QLIsrDecodeMailbox: Link up Show LUNinfo Displays detailed information for a specified LUN and target. Authority None Syntax show luninfo Example: MPX200 <1>(admin) #> show luninfo 50:00:1f:e1:50:07:0c:e0,50:00:1f:e1:50:07:0c:e9 50:00:1f:e1:50:07:0c:e0,50:00:1f:e1:50:07:0c:ec Please select a Target from the list above ('q' to quit): Index (LUN/VpGroup) ----- ------...
Page 183: Show Luns
Show LUNs Displays LUN information for each target. Authority None Syntax show luns Example: MPX200 <1>#> show luns Target(WWPN) VpGroup ============ ======= 50:00:1f:e1:50:07:0c:e9 VPGROUP_1 VPGROUP_1 VPGROUP_1 VPGROUP_1 VPGROUP_1 50:00:1f:e1:50:07:0c:ec VPGROUP_2 VPGROUP_2 VPGROUP_2 VPGROUP_2 VPGROUP_2 Show LUNmask Displays all initiators mapped to the specified LUN.
Page 184: Show Memory
Show mgmt Displays the blade management port (10/100) configuration. Authority None Syntax show mgmt Example: MPX200 <1>(admin) #> show mgmt Management Port Information ----------------------------- IPv4 Interface Enabled IPv4 Mode Dhcp IPv4 IP Address 172.17.137.129 IPv4 Subnet Mask 255.255.254.0 IPv4 Gateway 172.17.136.1...
Page 185: Show Perf
-------- -------- -------- -------- Example 2: MPX200 <1>#> show perf byte WARNING: Valid data is only displayed for port(s) that are not associated with any configured FCIP routes. Displaying bytes/sec (total)... (Press any key to stop display) -------------------------------- Example 3: MPX200 <1>#>...
Page 186: Show Presented Targets
Keywords Displays FC presented targets. Displays iSCSI presented targets. iscsi Example 1: MPX200 <1>#> show presented_targets fc No Presented Targets found. Example 2: MPX200 <1>#> show presented_targets iscsi Presented Target Information iSCSI Presented Targets ==================== Name iqn.1986–03.com.hp:fcgw.mpx200.0834e00025.b1.01.50001fe150070ce9 Alias <MAPS TO>...
Page 187: Show Properties
Prompt String MPX200 Show SNMP Displays the router’s SNMP configuration and any configured traps. Authority None Syntax show snmp Example: MPX200 <1>(admin) #> show snmp SNMP Configuration ------------------ Read Community Public Trap Community Private System Location System Contact Authentication traps Disabled System OID 1.3.6.1.4.1.3873.1.5...
Page 188 Example: MPX200 <1>#> show stats FC Port Statistics -------------------- FC Port 1 Interrupt Count 23 Target Command Count 0 Initiator Command Count 0 FC Port 2 Interrupt Count 1717443350 Target Command Count 0 Initiator Command Count 1815115822 iSCSI Port Statistics...
Page 189 MAC Xmit Dropped Frames 0 MAC Xmit Jumbo Frames 0 MAC Rcvd Frames 186 MAC Rcvd Byte Count 39260 MAC Rcvd Unknown Control Frames 0 MAC Rcvd Pause Frames 0 MAC Rcvd Control Frames 0 MAC Rcvd Dribbles 0 MAC Rcvd Frame Length Errors 0 MAC Rcvd Jabbers 0 MAC Rcvd Carrier Sense Errors 0 MAC Rcvd Dropped Frames 0...
Page 190: Show System
Displays the targets discovered by the FC router, iSCSI router, or both. Authority None Syntax show targets iscsi Keywords Displays FC targets. Displays iSCSI targets. iscsi Example 1: MPX200 <1>#> show targets fc Target Information -------------------- WWNN 50:00:1f:e1:50:07:0c:e0 WWPN 50:00:1f:e1:50:07:0c:e9 Port ID 02-f7-01 State Online...
Page 191: Show Vpgroups
Keywords The number (1–4) of the VPG to be displayed. vp index Example 1: The following example shows the show vpgroups command for a specific VPG: MPX200 <1>#> show vpgroups 2 VpGroup Information --------------------- Index VpGroup Name VPGROUP_2...
Page 192: Target
Authority Admin session Syntax target Keywords Removes a target from the router’s target database. Example: MPX200 <1>(admin) #> target rm Index State (WWNN,WWPN/iSCSI Name) ----- ----- ---------------------- 0 Offline 20:00:00:14:c3:3d:d2:bf,22:00:00:14:c3:3d:d2:bf 1 Online 20:00:00:14:c3:44:9b:86,22:00:00:14:c3:44:9b:86 2 Online 20:00:00:14:c3:44:9b:9d,22:00:00:14:c3:44:9b:9d 3 Online 20:00:00:14:c3:44:9a:fa,22:00:00:14:c3:44:9a:fa Please select an OFFLINE Target from the list above ('q' to...
Page 193 Example 1: The following example illustrates the use of the wanlinktest setup command. MPX200 <2>(admin) #> wanlinktest setup 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.
Page 194 Wan link test initialization completed successfully Example 3: The following example illustrates the use of the wanlinktest show command. MPX200 <1>(admin) #> wanlinktest show Not completed single iteration yet Wan link test started for the duration of 10 Minutes at on GigePort 1 LocalIP: 66.66.1.120...
Page 195: B Command Line Interface Usage
B Command Line Interface usage The CLI enables you to perform a variety of MPX200 management tasks through an Ethernet or serial port connection. Logging on to an MPX200 You can use either Telnet or SSH to log on to a router, or you can log on to the switch through the serial port.
Page 196: Working With Mpx200 Router Configurations
[ chassis ] Account name: guest Password: password MPX200 #> show chassis Chassis Information --------------------- Product Name HP StorageWorks MPX200 Chassis Name Router Chassis Name Serial Number 0834E00019 HW Version 20697-03 A Fan Speed Normal Blade 1 Information (Left Slot)
Page 197: Saving And Restoring Router Configurations
200 Type set to I. ftp> get HP_StorageWorks_MPX200_FRU.bin 200 PORT command successful. 150 Opening BINARY mode data connection for 'HP_StorageWorks_MPX200_FRU.bin' (6168 bytes). 226 Transfer complete. ftp: 6168 bytes received in 0.00Seconds 6168000.00Kbytes/sec. ftp> quit 221 Goodbye. Working with MPX200 router configurations 197...
Page 198: Restoring Router Configuration And Persistent Data
200 Type set to I. ftp> put HP StorageWorks MPX200_FRU.bin 200 PORT command successful. 150 Opening BINARY mode data connection for 'HP StorageWorks MPX200_FRU.bin'. 226 Transfer complete. ftp: 6168 bytes sent in 0.00Seconds 6168000.00Kbytes/sec. ftp> quit 221 Goodbye.
Page 199: C Simple Network Management Protocol Setup
C Simple Network Management Protocol setup SNMP provides monitoring and trap functions for managing the router through third-party applications that support SNMP. The router firmware supports SNMP versions 1 and 2 and a QLogic Management Information Base (MIB) (see “Management Information Base ” (page 200)).
Page 200: Snmp Trap Configuration Parameters
SNMP trap configuration parameters SNMP trap configuration lets you set up to eight trap destinations. Choose from Trap 1 through Trap 8 to configure each trap. Table 33 (page 200) describes the parameters for configuring an SNMP trap. Table 33 SNMP trap configuration parameters Parameter Description Enables or disables trap n.
Page 201 qsrNwLinkStatus QsrLinkStatus qsrNwLinkRate QsrLinkRate qsrNwPortRole Syntax QsrPortRole Access Not accessible Description Operational role of this port: management port or iSCSI port. qsrNwPortIndex Syntax Unsigned32 Access Not accessible Description A positive integer indexing each network port in a given role. qsrNwPortAddressMode Syntax INTEGER 1 = Static...
Page 202: Fc Port Table
qsrMacAddress Syntax IMacAddress Access Read-only Description MAC address for this port. qstNwLinkStatus Syntax QsrLinkStatus Access Read-only Description Operational link status for this port. qsrNwLinkRate Syntax QsrLinkRate Access Read-only Description Operational link rate for this port. FC port table This table contains a list of the FC ports on the router. There are as many entries in this table as there are FC ports on the router.
Page 203 qsrFcLinkStatus QsrLinkStatus qsrFcLinkRate QsrLinkRate qsrFcPortRole Syntax QsrPortRole Access Not accessible Description Operational role of this port: FCP mode or frame shuttle mode. qsrFcPortIndex Syntax Unsigned32 Access Not accessible Description A positive integer indexing each FC port in a given role. qsrFcPortNodeWwn Syntax PhysAddress...
Page 204: Initiator Object Table
qsrFcLinkRate Syntax QsrLinkRate Access Read-only Description Current link rate for this port. Initiator object table The initiator object table is a list of the iSCSI initiators that have been discovered by the router. There are as many entries in this table as there are iSCSI initiators on the router. qsrIsInitTable Syntax SEQUENCE OF QsrIsInitEntry...
Page 205: Lun Table
qsrIsInitAlias Syntax SnmpAdminString Access Read-only Description Alias for the iSCSI initiator. qsrIsInitAddressType Syntax InetAddressType Access Read-only Description Type of iSCSI initiator’s IP address (IPv4 or IPv6). qsrIsInitAddress Syntax InetAddress Access Read-only Description IP address of the iSCSI initiator. qsrIsInitStatus Syntax Integer: 1 = unknown, 2 = loggedIn,...
Page 206 Access Not accessible Description A list of the LUNs on the FC targets discovered by the router. There are as many entries in this table as there are FC targets on the router. qsrLunEntry Syntax QsrLunEntry Access Not accessible Description Each entry (row) contains information about a specific LUN.
Page 207: Vp Group Table
qsrLunSize Syntax Unsigned32 Access Read-only Description Size of the LUN (in megabytes) qsrLunState Syntax Integer 1 = online, 2 = offline, 3 = reserved Access Read-only Description State of the LUN (online or offline) qsrLunVPGroupid Syntax Integer Access Read-only Description ID of the VP group to which this LUN belongs qsrLunVPGroupname Syntax...
Page 208 qsrVPGroupWWNN VpGroupWwnnAndWwpn qsrVPGroupWWPN VpGroupWwnnAndWwpn qsrVPGroupStatus INTEGER qsrVPGroupIndex Syntax Unsigned32 Access Read-only Description VP group index. qsrVPGroupId Syntax Integer Access Read-only Description VP group ID. qsrVPGroupName Syntax SnmpAdminString Access Read-only Description VP group name or host group name. qsrVPGroupWWNN Syntax VpGroupWwnnAndWwpn Access Read-only Description...
Page 209: Sensor Table
Sensor table The sensor table lists all the sensors on the router. Each table row specifies a single sensor. qsrSensorTable Syntax SEQUENCE OF QsrSensorEntry Access Not accessible Description List of all the sensors on the router. The table contains as many entries (rows) as there are sensors.
Page 210: Notifications
Warning = The sensor value is approaching a threshold. Critical = The sensor value has crossed a threshold. Notifications This section describes the MPX200 notification types. NOTE: Every notification uses qsrBladeSlot as one of the objects. This determines the originator blade for the same notification.
Page 211: Notification Objects
qsrSwVersion Syntax SnmpAdminString Access Read-only Description System software (firmware) version number. qsrNoOfFcPorts Syntax Unsigned32 Access Read-only Description Quantity of FC ports on the system. qsrNoOfGbEPorts Syntax Unsigned32 Access Read-only Description Quantity of gigabit Ethernet ports on the system. qsrAgentVersion Syntax SnmpAdminString Access Read-only...
Page 212: Agent Startup Notification
Agent startup notification The agent startup notification indicates that the agent on the router has started running. qsrAgentStartup uses the qsrEventTimeStamp object. Agent shutdown notification The agent shutdown notification indicates that the agent on the router is shutting down. qsrAgentShutdown uses the qsrEventTimeStamp object. Network port down notification The network port down notification indicates that the specified network port is down.
Page 213: Target Presentation (Mapping)
FC target device discovery notifications are sent for the following event: FC Target ◦ State: Discovered, went offline, or went online ◦ Target WWPN ◦ Blade number (1 or 2) Target presentation (mapping) The target presentation notification indicates that the specified target has been presented (mapped) or unpresented (unmapped).
Page 214: Generic Notification
qsrEventTimeStamp qsrEventSeverity Sensor notifications are sent for the following events: Over Temperature ◦ Blade number (1 or 2) ◦ Sensor number (1 of 3) Temperature returned to normal ◦ Blade number (1 or 2) ◦ Sensor number (1 of 3) Fans at high speed ◦...
Page 215 Generic notifications are sent for the following events: FC port configuration change ◦ Blade number (1 or 2) ◦ Port number (1 of 4) iSCSI port configuration change ◦ Blade number (1 or 2) ◦ Port number (1 of 4) iSNS configuration change ◦...
Page 216: D Log Messages
The ID column specifies the message identification numbers in ascending order. The Log Message column indicates the message text displayed in the MPX200 CLI. Note that: ◦ Log messages for the iSCSI driver module are common to both iSCSI ports. Log messages beginning with #0 denote iSCSI port 1 (GE1) and log messages beginning with #1 denote iSCSI port 2 (GE2).
Page 217 Table 34 MPX200 log messages (continued) 41060 Error Unable to create an object for the QLBA_CreateTargetNodeObject: target node; exceeded the maximum Too many devices number of target devices. 41067 Error Memory unavailable for LUN object. QLBA_CreateLunObject: LunObject memory unavailable 41077...
Page 218 Table 34 MPX200 log messages (continued) (router is target) in subsequent login PDUs. 41284 Error iSCSI login PDU was received with an QLIS_LoginPduContinue: Session invalid TSIH value. The TSIH is invalid does not exist, invalid TSIH because there is no session with that 0x%x TSIH value.
Page 219 Table 34 MPX200 log messages (continued) the router as part of its discovery process. 41769 Error Report LUNs command failed with QLBI_GetLunList: REPORT LUNS check condition status. The Report command failed with CHECK LUNs command was issued by the CONDITION, SCSI STATUS 0x%02X router as part of its discovery process.
Page 220 Table 34 MPX200 log messages (continued) 42654 Error Event notification; attempt to connect QLIS_HandleTeb: iSNS Connection to the iSNS server failed. Failed 43265 Error Failed to allocate memory for TPB QLUT_AllocateTpbExtension: TPB extension. allocation failed 43267 Error Failed to allocate DSD (buffer length...
Page 221 Table 34 MPX200 log messages (continued) 54939 Info Event notification; iSCSI close QLIS_HandleTeb: connection request or connection UTM_EC_CLOSE_CONNECTION or closed. UTM_EC_CONNECTION_CLOSED 54940 Info Event notification; iSCSI connection QLIS_HandleTeb: closed. UTM_EC_CLOSE_CONNECTION or UTM_EC_CONNECTION_CLOSED 54941 Info Event notification; connection opened QLIS_HandleTeb:iSNS Server Open with iSNS server.
Page 222 Table 34 MPX200 log messages (continued) 70499 iSCSI Fatal Response queue invalid handle for ET #%d: QLProcessResponseQueue: pass-through. Invalid handle for ET_PASSTHROUGH_STATUS 70501 #%d: QLProcessResponseQueue: iSCSI Fatal Response queue invalid entry type. Invalid entry type in response queue %x 70502...
Page 223 Table 34 MPX200 log messages (continued) 74577 iSCSI Error iSCSI processor reported that the iSCSI #%d: QLIsrDecodeMailbox: NVRAM port NVRAM contains invalid data invalid (checksum error). 74580 iSCSI Error iSCSI processor reported a duplicate #%d: QLIsrDecodeMailbox: AEN IP address was detected (address xxxx %04x, Duplicate IP address xxxx xxxx xxxx xxxx).
Page 224 Table 34 MPX200 log messages (continued) 87348 iSCSI Info iSCSI controller reported a link #%d: QLGetFwStateCallback: link speed/configuration of 1000 Mb FDX. 1000Mb FDX 87350 iSCSI Info iSCSI controller reported an invalid #%d: QLGetFwStateCallback: link speed. Invalid link speed 0x%x...
Page 225 Table 34 MPX200 log messages (continued) or has run out of resources to execute additional commands. 106589 Error FC processor was disabled by an #%d: QLIoctlEnable: Adapter IOCTL request to the driver. disabled 106590 Error FC processor firmware failed #%d: QLIoctlEnable: Initialize initialization.
Page 226 Table 34 MPX200 log messages (continued) 108032 Error FC controller failed the Get VP #%d: QLGetVpDatabase: Database command (for virtual port MBOX_CMD_GET_VP_DATABASE for VP %d). %d fatal error 108033 Error FC controller failed the Get VP #%d: QLGetVpDatabase: Database command (for virtual port MBOX_CMD_GET_VP_DATABASE for VP %d) with status x.
Page 227 Table 34 MPX200 log messages (continued) 120376 Info For FCoE protocol, the IDC time #%d: QLIsrEventHandler: IDC extended notification is received. Time Extended (%x), %x, %x, %x, %x, %x, %x, %x 120377 Info For FCoE protocol, the DCBX protocol #%d: QLIsrEventHandler: DCBX has started.
Page 228 Table 34 MPX200 log messages (continued) 139296 User Error Failed memory allocation for FC QBRPC_Initialize:FcTgt Mem Target API. Allocation error 139297 User Error Failed memory allocation for System QBRPC_Initialize:BridgeStatus Status API. Mem Allocation error 139298 User Error Failed memory allocation for QBRPC_Initialize:Diag Mem Diagnostic API.
Page 229 Table 34 MPX200 log messages (continued) 151843 User Info User issued a REBOOT or SHUTDOWN REBOOT/SHUTDOWN Command from command. user. Code=%d 151889 User Info FC port configuration has changed. #%d: qapisetfcinterfaceparams_1_svc: FC port configuration changed 151890 User Info iSCSI port configuration has changed.
Page 230 Table 34 MPX200 log messages (continued) 152129 User Info Left power and cooling module (PCM) sysTempMon: Left PCM Installed is or has been installed. 152130 User Info Left PCM is or has been uninstalled. sysTempMon: Left PCM Un-installed 152131 User Info Right PCM is or has been installed.
Page 231 Table 34 MPX200 log messages (continued) 172240 FCIP Error FCIP route #n local node is out of sync FcipRoute#%d: De-encapsulation with the remote peer. Error on Receive 172245 FCIP Error FCIP route #n not able to transmit FcipRoute#%d: Transmit Failure data.
Page 232 Table 34 MPX200 log messages (continued) 172322 FCIP Error The FCIP route #n went down because FcipRoute#%d: FC link on the the Fibre Channel port on the remote remote peer went down peer went down. 184515 FCIP Info TCP link for FCIP route #n has been FcipRoute#%d: TCP Link Up established.
Page 233 Table 35 DM log messages (continued) id, source and destination lun ids, AdditionalErrorStatus %x at as well as the error. line %d 56321 Info An array went offline because all QLMP_Logout: Virtual Target the target ports of the array went Logged out offline.
Page 234 Table 35 DM log messages (continued) 56884 Info Did not find a Migration job for QLDM_DeleteMigrationJobByLun: the associated LUN object. Could not find migration object 152096 User Info A set array was performed on qapisetmigrfctargets_1_svc: one of the arrays. Configuration Changed for migration target 152099 User...
Page 235 Table 36 WD log messages Log Message Module type Description type WD: port GE1 mode changed from iSCSI User Info Ports mode changed from iSCSI to to GE Ethernet. WD: port GE1 mode restored from GE to User Info Ports mode changed from Ethernet to iSCSI iSCSI.
Page 236 Table 36 WD log messages (continued) WD: Unable to resotre GE2 Network IPV4 User Error Unable to change IPV4 setting back to params original. WD: Unable to resotre GE2 Network IPV6 User Error Unable to change IPV6 setting back to params original.
Page 237 Table 36 WD log messages (continued) WD: wanlinktest setup GetportInfo Failed. User Error Wanlink Test failed because error occurred while reading port information. WD: Unable to start PMTU thread due to User Error Path MTU calculation process not insufficient system resources started due to insufficient resources.
Page 238: E Hp Mpx100/Mpx100B To Mpx200 Upgrade
NOTE: Ensure that the latest firmware is installed. 13. Boot all Hosts. Configure each iSCSI initiator to perform a discovery of the MPX200 target portals. 14. Create an iSCSI host entry for each initiator using HP P6000 Command View or SSSU.
Page 239 Mount drives. Windows: On the Targets tab of the iSCSI Initiator applet, click Refresh. Log in to proper targets. iii. Rescan devices and use Disk Management to mount disks. To upgrade from mpx100/mpx100b to the MPX200 Multifunction Router: 239...
Page 240: F Regulatory Compliance And Safety
Laser device All HP systems equipped with a laser device comply with safety standards, including International Electrotechnical Commission (IEC) 825. With specific regard to the laser, the equipment complies with laser product performance standards set by government agencies as a Class 1 laser product.
Page 241: Laser Product Label
Laser product label The optional label in Figure 131 (page 241) or equivalent may be located on the surface of the HP supplied laser device. Figure 131 Class 1 laser product label This optional label indicates that the product is classified as a CLASS 1 LASER PRODUCT. This label may appear on the laser device installed in your product.
Page 242: Japanese 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 242 Regulatory compliance and safety...
Page 243: Taiwan Battery Recycling Notice
1.00 mm 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.
Page 244: Japanese Power Cord Statement
Japanese power cord statement Chinese warning messages Altitude warning message May be used safely only in areas where the attitude is less than 2000m. Non-tropical warning message May be used safely only in non-tropical climates. Waste Electrical and Electronic Equipment directive English notice Disposal of waste equipment by users in private households in the European Union This symbol on the product or on its packaging indicates that this product must not be disposed...
Page 245: Czechoslovakian Notice
natuurlijke bronnen worden behouden en kan het materiaal worden hergebruikt op een manier waarmee de volksgezondheid en het milieu worden beschermd. Neem contact op met uw gemeente, het afvalinzamelingsbedrijf of de winkel waar u het product hebt gekocht voor meer informatie over inzamelingspunten waar u oude apparatuur kunt aanbieden voor recycling.
Page 246: Greek Notice
Das Symbol auf dem Produkt oder seiner Verpackung weist darauf hin, dass das Produkt nicht über den normalen Hausmüll entsorgt werden darf. Benutzer sind verpflichtet, die Altgeräte an einer Rücknahmestelle für Elektro- und Elektronik-Altgeräte abzugeben. Die getrennte Sammlung und ordnungsgemäße Entsorgung Ihrer Altgeräte trägt zur Erhaltung der natürlichen Ressourcen bei und garantiert eine Wiederverwertung, die die Gesundheit des Menschen und die Umwelt schützt.
Page 247: Latvian Notice
Para obter mais informações sobre locais que reciclam esse tipo de material, entre em contato com o escritório da HP em sua cidade, com o serviço de coleta de lixo ou com a loja em que o produto foi adquirido.
Page 248: Slovakian Notice
Slovakian notice Slovenian notice Spanish notice Eliminación de residuos de equipos eléctricos y electrónicos por parte de usuarios particulares en la Unión Europea Este símbolo en el producto o en su envase indica que no debe eliminarse junto con los desperdicios generales de la casa.
Page 249: G Saving And Restoring The Mpx200 Configuration
Using the MPX200 CLI to save the configuration information places the file in the MPX200’s FTP directory. You must then move the file using FTP from the MPX200 (an FTP client accesses the file and moves it to any desired location).
Page 250 Enter the following command to set the FTP transfer type to binary: ftp> bin Enter the following command to put the HP_StorageWorks_MPX200_FRU.bin file: ftp> put HP_StorageWorks_MPX200_FRU.bin Log in to the MPX200 using a Telnet session to the management port or console port: Username: guest Password: password Enter the following command: MPX200>...
Page 251: Glossary
Glossary array A storage system that contains multiple disk or tape drives. A disk array, for example, is differentiated from a disk enclosure, in that the array has cache memory and advanced functionality, like RAID and virtualization. Components of a typical disk array include disk array controllers, cache memories, disk enclosures, and power supplies.
Page 252 Gigabit Ethernet. heartbeat A periodic synchronization signal issued by cluster software or hardware to indicate that a node is an active member of the cluster. The MPX200 heartbeat LED blinks at a rate of once per second during normal operation. initiator A media (host) server that runs the backup/restore application that passes commands and data between the network and the VLS.
Page 253 MPIO Microsoft Multipathing I/O software. Maximum Transmission Unit. multipath routing The routing technique of leveraging multiple alternative paths through a network, which can yield a variety of benefits such as fault tolerance, increased bandwidth, or improved security. Maximum window size. Network interface controller.
Page 254 Secure shell. Protocol that secures connections to the switch for the command line interface. SSSU Storage System Scripting Utility. An HP command line interface that allows you to configure and control EVAs. Used to script and run repetitious and complex configuration tasks.
Page 255: Index
Symbols set, 3PAR set alias, LUN provisioning, set chap, setting up the iSCSI ports, set chassis, setting up the MPX200 management port, set fc, 3PAR storage, set features, FCoE connectivity, set iscsi, MPX zoning, set isns, set mgmt, set ntp,...
Page 256 Windows Server 2003 initiator, fciproute command, iSCSI ports FCoE, setting up, 3PAR MPX zoning, iSNS configurations, use of, connectivity to 3PAR storage systems, connectivity to HP P6000 EVAs, feature description, LEDs feedback heartbeat, product, Input Power, Fibre Channel, System Alert, Fibre Channel zoning,...
Page 257 Properties page, router blade, with QLogic iSCSI HBA, RSM, MPX200 blade, locating, MPX200 features, MPxIO SAN, enabling for HP P6000 EVA storage array, save command, multipath devices, monitoring, secure shell, multipath routing, security multipathing, CHAP, Select Features page,...
Page 258 WANLinktest diagnostic, shutdown command, websites SNMP HP Subscriber's choice for business, parameters, product manuals, trap configuration parameters, Windows Cluster support, Windows Server 2003 setup, iSCSI initiator, Windows Server 2003,...

HP MPX200 User Manual

MPX200 Multifunction Router Overview

Planning the MPX200 Installation

Installing the MPX200

Managing MPX200 Iscsi Using HP P6000 Command View

Managing MPX200 Iscsi for 3PAR Storeserv Storage

Managing MPX200 Iscsi for XP24000/20000

MPX200 Iscsi Configuration Rules and Guidelines

Mpx200 Fcip

MPX200 Fcoe Feature Description

10 Diagnostics and Troubleshooting

1 Support and Other Resources

12 Documentation Feedback

A Command Reference

B Command Line Interface Usage

C Simple Network Management Protocol Setup

Quick Links

Troubleshooting

Related Manuals for HP MPX200

Summary of Contents for HP MPX200