Page of 362
Download Table of ContentsContents Print This PagePrint Bookmark

HP StorageWorks 6100 - Enterprise Virtual Array User Manual

Hp storageworks mpx200 multifunction router user guide (5697-0306, january 2010).
Hide thumbs
HP StorageWorks
MPX200 Multifunction Router
This user guide describes the MPX200 Multifunction Router, which supports the EVA family of Fibre Channel
storage systems for integrated iSCSI connectivity. The MPX200 hardware is integrated with up to four EVA
storage systems and HP Command View EVA to deliver multi-protocol capabilities, including Fibre Channel,
iSCSI, and FCIP. This document is intended for system administrators with knowledge of HP StorageWorks
EVA4x00/6x00/8x00 storage systems, configuring LUNs using HP Command View EVA, HP Fibre Channel
SANs, Ethernet, TCP/IP networking, iSCSI, and FCIP.
Part number: 5697-0306
Fourth edition: January 2010

Advertising

   Related Manuals for HP StorageWorks 6100 - Enterprise Virtual Array

   Summary of Contents for HP StorageWorks 6100 - Enterprise Virtual Array

  • Page 1: User Guide

    HP StorageWorks MPX200 Multifunction Router User Guide This user guide describes the MPX200 Multifunction Router, which supports the EVA family of Fibre Channel storage systems for integrated iSCSI connectivity. The MPX200 hardware is integrated with up to four EVA storage systems and HP Command View EVA to deliver multi-protocol capabilities, including Fibre Channel, iSCSI, and FCIP.

  • Page 2

    Legal and notice information © Copyright 2009 2010-NaN Hewlett-Packard Development Company, L.P. Confidential computer software. Valid license from HP required for possession, use or copying. Consistent with FAR 12.211 and 12.212, Commercial Computer Software, Computer Software Documentation, and Technical Data for Commercial Items are licensed to the U.S.

  • Page 3: Table Of Contents

    Contents 1 MPX200 Multifunction Router overview ..........19 MPX200 features ........................19 MPX200 configuration options ....................21 Planning the MPX200 installation ....................24 Total number of initiators ..................... 24 Number of paths required per initiator .................. 25 Use of iSNS ........................25 Use of iSCSI ports ......................

  • Page 4: Table Of Contents

    Supported IP network adapters ....................51 IP network requirements ......................51 Setting up the iSCSI initiator ....................... 51 Windows Server iSCSI initiator ................... 51 Multipathing ........................57 Installing the MPIO feature for Windows Server 2008 ............. 58 Installing the MPIO feature for Windows Server 2003 ............. 60 Microsoft Windows Server 2003 Scalable Networking Pack ............

  • Page 5: Table Of Contents

    FCIP and iSCSI performance ....................104 MPX200 iSCSI/FCIP configurations ................... 104 HP Continuous Access EVA 3 site configurations ..............108 3-site configuration with four MPX200 routers ..............109 3-site configuration with six MPX200 routers ..............109 3-site configuration with eight MPX200 routers .............. 110 3-site configuration with six MPX200 routers and full inter-site connectivity ......

  • Page 6: Table Of Contents

    HP Command View EVA issues and solutions ................134 7 Support and other resources ............137 Intended audience ........................137 Related documentation ......................137 Contacting HP ........................138 HP technical support ......................138 Subscription service ......................138 Product feedback ......................138 Documentation feedback ....................

  • Page 7: Table Of Contents

    Set VPGroups ........................164 Show ..........................164 Show CHAP ........................166 Show chassis ........................167 Show FC ......................... 168 Show fciproutes ....................... 168 Show features ........................169 Show initiators ......................... 169 Show initiators LUNmask ....................169 Show iSCSI ........................170 Show iSNS ........................

  • Page 8: Table Of Contents

    FC port down notification ....................205 Target device discovery ..................... 205 Target presentation (mapping) .................... 205 VP group notification ......................206 Sensor notification ......................206 Generic notification ......................207 D Log messages ................209 E Regulatory compliance and safety ............ 233 Regulatory compliance ......................

  • Page 9: Table Of Contents

    Restoring the MPX200 configuration ..................244 Restoring the configuration using the MPX200 CLI ..............244 G Offline Data Migration ..............247 Features overview ........................247 Feature details ........................248 Job scheduling ......................... 248 Immediate schedule ....................248 Delayed schedule ...................... 248 Serial schedule ......................

  • Page 10: Table Of Contents

    Viewing the status of data migration jobs ................275 Viewing data migration job status in the GUI ..............275 Viewing data migration jobs status in the CLI ..............276 Rescanning targets ......................277 Viewing job details and controlling job actions ..............278 Viewing job details and controlling job actions in the GUI ..........

  • Page 11: Table Of Contents

    compare_luns resume ....................322 compare_luns acknowledge ..................323 show fc ........................324 show migration ......................325 show array ....................... 326 show luninfo ......................329 show luninfo ......................329 show migration_luninfo ....................330 show migration_params ....................332 show mgmt ....................... 333 show memory ......................

  • Page 12: Table Of Contents

    Figures MPX200 single-blade fabric-attached configuration ............. 22 MPX200 dual-blade fabric-attached configuration ............22 MPX200 single-blade multi-EVA configuration ............. 23 MPX200 dual-blade multi-EVA configuration ............... 23 MPX200 components ....................27 Chassis rails ......................28 Rack rails ....................... 28 Inner rack view ....................... 29 Rear view ......................

  • Page 13: Table Of Contents

    MPIO MPIO Properties page before reboot ..............59 MPIO Properties page after reboot ................59 Software update installation wizard ................60 Discover targets ...................... 62 Add static IP address ....................62 Discovered targets list ....................63 iSNS discovery and verification ................63 Discovered targets ....................

  • Page 14: Table Of Contents

    HP Continuous Access EVA 3 site configuration with six MPX200 routers ..... 110 HP Continuous Access EVA 3 site configuration with eight MPX200 routers ....111 HP Continuous Access EVA 3 site configuration with six MPX200 router full peer-to-peer connectivity ......................112 MPX200 ports and LEDs ..................

  • Page 15: Table Of Contents

    mpx Log: Migration Log ..................284 Verify migration job wizard ..................287 Verifying jobs options .................... 288 Features page: License Information ................290 New License Key dialog box .................. 290 Add license dialog box ..................291 License Array dialog box ..................293 Information page showing array is licensed ..............

  • Page 16: Table Of Contents

    Tables MPX200 part numbers and options ................19 MPX200 supported configuration maximums .............. 24 Supported MPX200 maximums ................. 46 Support for EVA storage system software with MPX200 iSCSI ........48 Operating system and multipath software support ............48 Supported IP network adapters ................. 51 Differences between Windows Server 2008 and Windows Server 2003 .......

  • Page 17

    Component requirements ..................256 CLI commands ...................... 297 Troubleshooting ....................354 MPX200 Multifunction Router...

  • Page 19: Mpx200 Multifunction Router Overview, Mpx200 Features, Mpx200 Part Numbers And Options

    1 MPX200 Multifunction Router overview MPX200 features The Enterprise Virtual Array (EVA) family of Fibre Channel (FC) storage systems is supported for integrated iSCSI connectivity using the MPX200. The MPX200 hardware is integrated with up to four EVA storage systems, for iSCSI connectivity, to deliver multi-protocol capabilities. This provides iSCSI and FC attached servers access to block storage through an FC network and an Ethernet IP network simultaneously.

  • Page 20

    The AP771A or AP773A • one 1-GbE blade with four MPX200 base chassis and up 1-GbE iSCSI ports and two to four EVA storage systems, HP StorageWorks MPX200 8-Gb/s FC ports AP772A or to upgrade existing EVA 1GbE Upgrade Blade •...

  • Page 21: Mpx200 Configuration Options

    The following additional equipment is required to configure the MPX200: • B-series or C-series FC switch • Optical small form-factor pluggables (SFPs) • FC ports, 8 Gb/s short-range SFP (AJ718A) • FC ports, 4 Gb/s short-range SFP (A744B) • 10-GbE ports, short-range SFP+ (455883 B21) •...

  • Page 22: Mpx200 Single-blade Fabric-attached Configuration, Mpx200 Dual-blade Fabric-attached Configuration

    Figure 1 MPX200 single-blade fabric-attached configuration Figure 2 illustrates an MPX200 dual-blade fabric-attached configuration. This configuration provides high availability with failover between blades. NOTE: A dual-blade configuration may require reconfiguration of device mappings. Figure 2 MPX200 dual-blade fabric-attached configuration Figure 3 illustrates a multi-EVA configuration with connectivity for up to four EVA storage systems from a single MPX200 blade.

  • Page 23: Mpx200 Single-blade Multi-eva Configuration, Mpx200 Dual-blade Multi-eva Configuration

    Figure 3 MPX200 single-blade multi-EVA configuration Figure 4 illustrates a multi-EVA configuration with connectivity for up to four EVA storage systems from dual MPX200 blades. This configuration provides high availability with failover between blades. Figure 4 MPX200 dual-blade multi-EVA configuration MPX200 Multifunction Router...

  • Page 24: Planning The Mpx200 Installation, Total Number Of Initiators, Mpx200 Supported Configuration Maximums

    Planning the MPX200 installation Before installing the MPX200, it is important to define the requirements for iSCSI server connectivity. You should consider present and future needs as they relate to the following MPX200 configuration attributes: • Simultaneous operation • Total number of initiators •...

  • Page 25: Number Of Paths Required Per Initiator, Use Of Iscsi Ports, Balancing The Load, Gbe Initiators

    Number of paths required per initiator After establishing the number of initiators, determine how many paths are required by each. The number of connections per blade is finite, and every initiator login constitutes a connection to the MPX200. In a multipath environment, HP recommends a minimum of one connection per blade; high-performance applications may require up to four connections per blade (a total of eight).

  • Page 26

    MPX200 Multifunction Router overview...

  • Page 27: Installing The Mpx200, Rack Mounting The Mpx200, Mpx200 Components

    2 Installing the MPX200 This chapter describes how to rack mount the MPX200. Rack mounting the MPX200 Figure 5 shows the MPX200 components. 1. Rack rail, inner (2) 5. Screw, flathead, 10 32 x 1/4 in. (6) 2. Rack rail, outer (2). 6.

  • Page 28: Chassis Rails, Rack Rails

    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 The MPX200 has multiple mounting holes to allow for adjustable setback.

  • Page 29: Inner Rack View

    Install the rails in the rack. There are two inner rails and two outer rails. Slide each inner rail into the corresponding outer rail to create a complete rack rail. Extend the rack rails to fit the inner dimensions of the rack. The rail flanges on both ends fit inside the rack.

  • Page 30: Rear View

    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 each rail flange (Figure 1.

  • Page 31: Power Cord

    Route the power cord: Starting from the front of the rack, connect the power cord to the MPX200. For the left blade, the cord by following the gap between the chassis and the chassis rail (Figure 10). Repeat for the right blade. NOTE: The right blade requires the power cord to extend approximately 12 in.

  • Page 32: Bezel View

    Install the HP StorageWorks MPX200 bezel: 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.

  • Page 33: Managing The Mpx200 Using Hp Command View Eva, Setting Up The Mpx200 Management Port

    3 Managing the MPX200 using HP Command View EVA This chapter provides instructions for setting up the MPX200 management port, Fibre Channel zoning, HP Command View EVA discovery, setting up the iSCSI IP ports, and setting the date and time. NOTE: DMS and FCIP functionality are not completely configured using HP Command View EVA.

  • Page 34: Fibre Channel Switch-based Zoning, Open Zone Configuration

    Figure 12 Open zone configuration Fibre Channel switch-based zoning Each FC port on the MPX200 uses N_Port ID Virtualization (NPIV) to create a total of four unique, virtual world wide node names (WWNNs) per physical FC port. To create proper zoning, you must understand the use of VPGs.

  • Page 35: Hp Command View Eva Discovery, Fibre Channel Zone Configuration, Iscsi Devices Folder Properties

    Figure 13 Fibre Channel zone configuration HP Command View EVA discovery Once the management port IP address is set and the router FC ports are visible to the EVA, you can perform the MPX200 discovery. You discover the MPX200 iSCSI controllers using the Discover iSCSI Devices button or the Add iSCSI Device button (see Figure 14).

  • Page 36: Host Properties

    NOTE: HP recommends that you set a static IP address on the management port to ensure connectivity. 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 15).

  • Page 37: Setting Up The Iscsi Ip Ports, Iscsi Controller Properties: Mgmt Port Tab

    Figure 16 iSCSI controller properties: Mgmt Port tab 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 17).

  • Page 38: Setting The Date And Time On The Mpx200, Iscsi Controller Properties: Ip Ports Tab

    Figure 17 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, as shown in Figure NOTE: HP recommends using the Network Time Protocol (NTP) settings, if available on your network.

  • Page 39: Code Load, Set Iscsi Controller Time

    Figure 18 Set iSCSI controller time Code load NOTE: HP recommends that you load the latest MPX200 firmware. Check http://www.hp.com/go/mpx200 for updates. You load the firmware from the Code Load page for the iSCSI controller. Firmware is loaded for the selected controller only;...

  • Page 40: Shutting Down And Restarting The Mpx200, Saving Or Restoring The Mpx200 Configuration

    Figure 19 Code Load page for the iSCSI controller Shutting down and restarting the MPX200 If you need to restart or shut down the MPX200, click the Power down button (see Figure 20). Figure 20 iSCSI controller shutdown options Saving or restoring the MPX200 configuration After initial setup of the MPX200, it is a good practice to save the configuration.

  • Page 41: Locating The Mpx200, Iscsi Controller Configuration Selection

    NOTE: A Restore action reboots the blade. In a dual-blade configuration, a copy of the configuration for each router is kept on the peer. If you add a new blade, the configuration of the peer blade is copied to the new blade and is ready for use immediately;...

  • Page 42: Removing An Iscsi Controller, Blue Led Locating Beacon, Locate Hardware Device

    Figure 22 Blue LED locating beacon To enable or disable the locating beacon: Select the desired iSCSI controller. Click the Locate button. Click the Locate ON or Locate OFF button (Figure 23). Figure 23 Locate hardware device Removing an iSCSI controller Before you remove an iSCSI controller permanently, ensure that all virtual disk presentations have been removed.

  • Page 43: Iscsi Controller Options: Remove Controller

    Figure 24 iSCSI controller options: Remove controller MPX200 Multifunction Router...

  • Page 44

    Managing the MPX200 using HP Command View EVA...

  • Page 45: Mpx200 Iscsi Configuration Rules And Guidelines, Iscsi Rules And Supported Maximums

    4 MPX200 iSCSI configuration rules and guidelines This chapter describes the iSCSI configuration rules and guidelines for the MPX200. iSCSI rules and supported maximums The MPX200 chassis can be configured with one or two blades. Dual-blade configurations provide for high availability with failover between blades, and are supported as redundant pairs only. iSCSI-connected servers can be configured for access to one or both blades.

  • Page 46: Eva Storage System Rules And Guidelines, Hp Command View Eva Management Rules And Guidelines

    Table 3 Supported MPX200 maximums Description Maximum per MPX200 solution Hardware EVA storage systems MPX200 One chassis with up to 2 blades “Planning the MPX200 installa- MPX200 iSCSI port connections tion” on page 24. Configuration parameter 300 per chassis for 1 GbE (1 or 2 blades) Total number of iSCSI initiators 600 per chassis for 10 GbE (1 or 2 blades) Total number of iSCSI logical unit numbers (LUNs)

  • Page 47: Eva Storage System Software, Features Supported For Iscsi Hosts, Features Not Supported For Iscsi Hosts

    • Requires HP Command View EVA 9.1.1 or later for array-based and server-based management. • A maximum of one MPX200 chassis (two blades) can be discovered by an EVA storage system. • HP Command View EVA manages the MPX200 out of band (IP) through the MPX200 management IP port.

  • Page 48: Fibre Channel Switch And Fabric Support, Operating System And Multipath Software Support

    Table 4 Support for EVA storage system software with MPX200 iSCSI HP StorageWorks product MPX200 iSCSI support HP StorageWorks Business Copy HP StorageWorks Replication Solutions Manager iSCSI and Fibre Channel hosts are supported. SSSU HP StorageWorks Continuous Access EVA iSCSI and Fibre Channel hosts and LUN remote replic- HP StorageWorks Continuous Access EVA with HP- ation are supported.

  • Page 49: Apple Mac Os X Iscsi Initiator Rules And Guidelines

    • iSCSI initiators and MPX200 iSCSI ports can be in different IP subnets. This requires setting the MPX200 iSCSI gateway feature. See “MPX200 configuration options” on page 21 and Appendix on page 185 for more information. • Both single-path and multipath initiators are supported on the same MPX200. •...

  • Page 50: Sun Solaris Iscsi Initiator Rules And Guidelines, Vmware Iscsi Initiator Rules And Guidelines

    iSCSI initiator operating system considerations follow: • Host-mode setting—Linux • NIC bonding—Not supported Sun Solaris iSCSI initiator rules and guidelines The The Sun Solaris iSCSI initiator supports the following: • Solaris iSCSI initiator only • Multipath using MPxIO • MPxIO Symmetric option only •...

  • Page 51: Windows Server Iscsi Initiator, Supported Ip Network Adapters, Ip Network Requirements

    Supported IP network adapters For the latest information on IP network adapter 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. Table 6 lists the IP network adapters supported by the MPX200. Table 6 Supported IP network adapters Operating system Network interconnect...

  • Page 52: Installing The Windows Server 2003 Kit

    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 (Figure 25). Figure 25 Installing the Windows Server 2003 kit For Windows Server 2003, the Microsoft iSCSI initiator installation presents an option for installing MPIO using the Microsoft generic DSM (Microsoft MPIO Multipathing Support for iSCSI check box).

  • Page 53: Iscsi Initiator Properties: Discovery Tab

    Figure 26 Installation Wizard Click the Microsoft iSCSI initiator icon to open the Control Panel applet. The iSCSI Initiator Properties window opens. Select the Discovery tab (Figure 27). Figure 27 iSCSI initiator properties: Discovery tab In the Target Portals section, click Add. A dialog box opens.

  • Page 54: Adding A Host

    In HP Command View EVA, set up the iSCSI host and virtual disks. Click the EVA storage system icon to start the iSCSI storage presentation. Figure 28, MPX200-XL is the target EVA storage system. Figure 28 Adding a host Select the Hosts folder. Click Add host to create an iSCSI initiator host.

  • Page 55: Virtual Disk Properties, Host Details

    Figure 29 Virtual disk properties Figure 30 Host details MPX200 Multifunction Router...

  • Page 56: Targets Tab

    Set up the iSCSI disk on the iSCSI initiator. Open the iSCSI initiator Control Panel applet. Select the Targets tab and then click the Refresh button to see the available targets (Figure 31). The status should be Inactive. Figure 31 Targets tab Select the target IQN noted in Step 2.d, and then click Log On.

  • Page 57: Multipathing, Differences Between Windows Server 2008 And Windows Server 2003, Mpio Options For The Mpx200

    Select Action > Rescan Disks. Verify that the newly assigned disk is listed; if not, you may need to reboot. Format and partition the disk to prepare it for use. Multipathing Microsoft MPIO includes support for redundant paths to send I/O from the initiator to the target. For Windows Server 2008, MPIO is a separate feature that must be installed separately.

  • Page 58: Installing The Mpio Feature For Windows Server 2008, Select Features

    Installing the MPIO feature for Windows Server 2008 NOTE: Microsoft Windows 2008 includes an MPIO feature that must be installed separately. It also includes the iSCSI initiator, which does not require download or installation. To install the MPIO feature for Windows Server 2008: Select the Multipath I/O check box on the Select Features page (Figure 32).

  • Page 59: Mpio Properties Page After Reboot

    After the server reboots, add support for iSCSI devices using the MPIO applet (Figure 33 Figure 34). NOTE: You must present a virtual disk to the initiator to enable the Add support for iSCSI devices check box (see Figure 33). Figure 33 MPIO MPIO Properties page before reboot Figure 34 MPIO Properties page after reboot Reboot the system to MPIO the devices.

  • Page 60: Installing The Mpio Feature For Windows Server 2003, Microsoft Windows Server 2003 Scalable Networking Pack

    Installing the MPIO feature for Windows Server 2003 For Windows Server 2003, if you are installing the initiator for the first time, select all of the installation option check boxes, and then click Next (Figure 35). Figure 35 Software update installation wizard To add or remove Microsoft iSCSI initiator components after the initial installation, run the setup package executable and select the Microsoft MPIO Multipathing Support for iSCSI check box.

  • Page 61: Setting Up Snp For The Hp Nc3xxx Multifunction Gigabit Server Adapter

    To download the SNP package and for more details, see http://support.microsoft.com/kb/912222. NOTE: Windows Server 2003 SP2 includes SNP functionality. Setting up SNP for the HP NC3xxx Multifunction Gigabit server adapter SNP works in conjunction with the HP NC3xxx Multifunction Gigabit server adapters for Windows 2003 only.

  • Page 62: Discover Targets, Add Static Ip Address

    Run the Xtend SAN iSCSI 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: Click Discover Targets, and then click Discover by DNS/IP (Figure 36).

  • Page 63: Discovered Targets List, Isns Discovery And Verification

    Figure 38 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 39).

  • Page 64: Discovered Targets

    Test the connection from the initiator to the iSNS server by clicking Verify iSNS. If successful, click Save. If necessary, from the iSNS server, make the appropriate edits to add the Xtend SAN iSCSI Initiator to any iSNS discovery domains that include MPX iSCSI targets. Click Discover Targets, and then click Discover by iSNS.

  • Page 65: Selecting The Newly Added Target, Select Status

    Click Save. Figure 41 Selecting the newly added target Click Status, select the network node, and then click Login to connect to the MPX target (Figure 42). The target status is Connected and the target status light turns green. Figure 42 Select status MPX200 Multifunction Router...

  • Page 66: Setting Up Storage For Apple Mac Os X, Iscsi Initiator Setup For Linux

    Setting up storage for Apple Mac OS X In HP Command View EVA, present the LUNs. Verify that the 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.

  • Page 67: Configure The Iscsi Initiator And Targets, Discovered Targets Tab

    Modify the initiator name: # vi /etc/<initiatorname>.iscsi To configure the initiator and targets, start the iSCSI initiator applet (located in the YaST Control Center under Network Services), and then set the initiator to start at boot time (Figure 44). Figure 44 Configure the iSCSI initiator and targets Select the Discovered Targets tab and enter the iSCSI target IP address (Figure 45).

  • Page 68: Log In To The Target

    Log in to the target (Figure 46). Figure 46 Log in to the target MPX200 iSCSI configuration rules and guidelines...

  • Page 69: Connected Targets Tab

    Select the Connected Targets tab, and then click the Toggle Start-Up button for each target listed so the targets start automatically (Figure 47). Figure 47 Connected Targets tab Installing and configuring the iSCSI driver for Red Hat 5 NOTE: The iSCSI driver package is included but is not installed by default. Install the package iscsi initiator utils during or after operating system installation.

  • Page 70

    Verify that the iSCSI service starts automatically: #chkconfig iscsi on NOTE: For details, see the man pages for the iscsiadm open-iscsi administration utility. Installing and configuring the iSCSI driver for Red Hat 4 and SUSE 9 NOTE: The iSCSI driver is included with the Red Hat 4 and SUSE 9 distributions and is installed by default. Configuration is the same for Red Hat 3 and 4 and SUSE 8 and 9.

  • Page 71: Assigning Device Names

    NOTE: The Linux driver supports both Red Hat 3 and SUSE 8. See the Readme file in the tar ball for information on how to configure the Linux iSCSI initiator. Assigning device names Linux assigns SCSI device nodes dynamically when it detects a SCSI logical unit; therefore, the mapping from device nodes (such as /dev/sda and /dev/sdb) to iSCSI targets and logical units may vary.

  • Page 72: Target Bindings, Mounting File Systems, Unmounting File Systems

    that modprobe could not find a driver for a particular combination of major and minor numbers. You can ignore these messages, which occur when Linux is unable to find a driver to associate with a SCSI device node that the iSCSI daemon is opening as part of the symlink creation process. To prevent these messages from occurring, remove the SCSI device nodes that do not contain an associated high-level SCSI driver.

  • Page 73: Presenting Eva Storage For Linux, Configuring Multipath With The Solaris 10 Iscsi Initiator, Mpxio Overview

    Linux does not unmount file systems that are being used by a process; therefore, any process using those devices must be stopped (see the man page for fuser(1)) before iSCSI devices can be unmounted. To prevent file system corruption, the iSCSI shutdown script automatically stops all processes using devices in /etc/fstab.iscsi.

  • Page 74

    Example: MPxIO on all iSCSI port settings in /kernel/dev/iscsi.conf # Copyright 2006 Sun Microsystems, Inc. All rights reserved. # Use is subject to license terms. #ident "@(#)iscsi.conf 1.2 06/06/12 SMI" name="iscsi" parent="/" instance=0; ddi-forceattach=1; # I/O multipathing feature (MPxIO) can be enabled or disabled using # mpxio-disable property.

  • Page 75

    Add the following lines for the EVA4x00/6x00/8x00 storage arrays: device-type-scsi-options-list = “HP HSV“, “symmetric-option“; symmetric-option = 0x1000000; NOTE: You must enter six spaces between HP and HSV. Example: HP storage array settings in /kernel/drv/scsi_vhci.conf # Copyright 2004 Sun Microsystems, Inc. All rights reserved.

  • Page 76

    Add array_ctrl to device-type-config-list: device-type-config-list="array_ctrl"; Uncomment all target/LUN pair entries. Example: HP storage array settings in /kernel/drv/sgen.conf # devices on your system. Please refer to sgen(7d) for details. # sgen may be configured to bind to SCSI devices exporting a particular device # type, using the device-type-config-list, which is a ',' delimited list of # strings.

  • Page 77

    Update the sgen driver: # update_drv –a –I “scsiclass,0c” sgen NOTE: Lowercase c is mandatory. Verify the sgen alias setting: #egrep sgen /etc/driver_aliases Example: # rep sgen /etc/driver_aliases sgen "scsa,08.bfcp" sgen "scsa,08.bvhci" sgen "scsiclass,0c" Enable iSCSI target discovery Solaris supports three iSCSI target discovery methods: •...

  • Page 78

    After discovery addresses are entered, the Solaris iSCSI initiator polls each address for all targets available. To list the targets available to the initiator, enter the following command: #iscsiadm list target Example: #iscsiadm list target Target: iqn.1986-03.com.hp:fcgw.mpx200.0834e00028.b2.01.50014380025c4179 Alias: - TPGT: 0 ISID: 4000002a0000 Connections: 1 Target: iqn.1986-03.com.hp:fcgw.mpx200.0834e00028.b1.01.50014380025c417d...

  • Page 79

    Use the following example to verify the target setting: # iscsiadm list target-param Target: iqn.1986-03.com.hp:fcgw.mpx200.0834e00028.b1.01.50014380025c417d #iscsiadm modify target-param –p maxrecvdataseglen=65536 iqn.1986-03.com.hp:fcgw.mpx200. 0834e00028.b1.01.50014380025c417d # iscsiadm list target-param -v iqn.1986-03.com.hp:fcgw.mpx200.0834e00028.b1.01. 50014380025c417d Target: iqn.1986-03.com.hp:fcgw.mpx200.0834e00028.b1.01.50014380025c417d Alias: - Bi-directional Authentication: disabled Authentication Type: NONE Login Parameters (Default/Configured): Data Sequence In Order: yes/- Data PDU In Order: yes/- Default Time To Retain: 20/-...

  • Page 80

    iscsiadm list target -S This command lists targets with their presented LUNs. In a multipath environment, the same LUN should appear under different EVA port targets from the same controller. Example: iscsiadm list target -S Target: iqn.1986-03.com.hp:fcgw.mpx200.0834e00028.b2.01.50014380025c4179 Alias: - TPGT: 0 ISID: 4000002a0000 Connections: 1 LUN: 120...

  • Page 81: Configuring Microsoft Mpio Iscsi Devices

    mpathadm show lu logical-unit This command displays details about a logical unit. Use this command to verify symmetric mode, load balancing, and auto-failback settings, as well as path and target port information. Example: #mpathadm show lu /dev/rdsk/c5t600508B4000B15A200005000038E0000d0s2 Logical Unit: /dev/rdsk/c5t600508B4000B15A200005000038E0000d0s2 mpath-support: libmpscsi_vhci.so Vendor:...

  • Page 82: Microsoft Mpio For Iscsi Load-balancing Policies, Iscsi Initiator Mpio Properties

    Click Details. Click Devices. Highlight a LUN device name, and then click Advanced. Select the MPIO check box. Select the desired options on the Load Balance Policy menu. Figure 48 iSCSI initiator MPIO properties Microsoft MPIO for iSCSI load-balancing policies The Microsoft MPIO for iSCSI load-balancing policies are as follows: •...

  • Page 83: Microsoft Mpio With Qlogic Iscsi Hba, Installing The Qlogic Iscsi Hba

    NOTE: For raw disk access, the MPIO load-balancing policy must be Failover Only. For file system disk access, all MPIO load-balancing policies are supported. Failover policies are set on a LUN-by-LUN basis. MPIO does not support global failover settings. 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.

  • Page 84: Configuring The Qlogic Iscsi Hba, Microsoft Iscsi Initiator Installation

    Access the Microsoft iSCSI Initiation Installation page of the Software Update Installation Wizard (Figure Figure 49 Microsoft iSCSI Initiator Installation page IMPORTANT: Do not select the Software Initiator check box. The QLogic initiator resides on the iSCSI HBA. Reboot the system. Configuring the QLogic iSCSI HBA To configure the QLogic iSCSI HBA: Launch the QLogic SMS from the desktop icon or through Start >...

  • Page 85: Connect To Host Window, Start General Configuration Wizard

    Click Yes to launch the general configuration wizard (Figure 51). Use the wizard to: • Select iSCSI HBA port to configure the QLogic iSCSI HBA. • Configure the HBA Port network settings. • Configure the HBA Port DNS settings (optional). •...

  • Page 86: Adding Targets To The Qlogic Iscsi Initiator, Hba Port Target Configuration Window, Target Settings Tab

    Adding targets to the QLogic iSCSI initiator To add HBA port targets: Click the green plus sign (Figure 52). Enter the first iSCSI target port IP address. Figure 52 HBA Port Target Configuration window Repeat steps 1 and 2 for each MPX200 you want to add. Click Next.

  • Page 87: Presenting Luns To The Qlogic Iscsi Initiator

    Presenting LUNs to the QLogic iSCSI initiator To present LUNs to the QLogic iSCSI initiator: Follow the procedure in Step 2 on page 54 to: • Create an iSCSI host. • Present LUNs to the iSCSI host. On the iSCSI HBA tab (Figure 54), verify that the QLogic iSCSI HBA is connected to the iSCSI LUNs in SMS under the HBA iSCSI port.

  • Page 88: Setting Up Authentication, Hp Mpio Dsm Manager With Iscsi Devices

    Figure 55 HP MPIO DSM Manager with iSCSI devices Setting up authentication CHAP is an authentication protocol used for secure login between the iSCSI initiator and iSCSI target. CHAP uses a challenge-response security mechanism to verify the identity of an initiator without revealing the secret password shared by the two entities.

  • Page 89: Chap Restrictions, Microsoft Initiator Chap Secret Restrictions, Linux Chap Restrictions, Atto Macintosh Chap Restrictions

    CHAP restrictions The CHAP restrictions follow: • Maximum length of 100 characters • Minimum length of 1 character Microsoft initiator CHAP secret restrictions The Microsoft initiator CHAP secret restrictions follow: • Maximum length of 16 characters • Minimum length of 12 characters •...

  • Page 90: Mpx200 Chap Modes, Enabling Single-direction Chap During Discovery Session And Normal Session, Chap Single-direction Settings

    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 only choose the CHAP mode: • Single-direction—The target authenticates the identity of the initiator with the user-provided CHAP secret.

  • Page 91: Enabling Chap For The Mpx200-discovered Iscsi Initiator Entry, Enabling Chap For The Microsoft Iscsi Initiator

    To enable CHAP for the Microsoft iSCSI initiator: Click Discovery. • To discover iSCSI target portals manually: Click Add under Target Portals. Enter the IP address of the MPX200 iSCSI port. 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).

  • Page 92: Enabling Chap For The Open-iscsi Iscsi Initiator

    Click Discovery. To manually discover iSCSI target portals: Click Add under Target Portals. Enter the IP address of the iSCSI port of the MPX200. Click Advanced. Select the CHAP Login Information checkbox. Enter the CHAP secret for the MPX200-discovered iSCSI initiator in the Target Secret box (for example, CHAPsecret01).

  • Page 93

    Save the /etc/iscsi/iscsid.conf file and start or restart iSCSI: [root@sanergy33 iscsi]# /etc/init.d/iscsi start or /etc/init.d/iscsi restart Use the iscsiadm command to perform a discovery. For example: [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.

  • Page 94: Session, Chap Single-direction Settings

    Enabling single-direction CHAP during discovery session and bi-directional CHAP during normal session Table 10 lists the settings you use to enable single-direction CHAP during a discovery session and bi-directional CHAP during a normal session. Table 10 CHAP single-direction settings MPX200 secret settings Microsoft initiator secret settings Source Setting (example)

  • Page 95: Chap Bi-directional Settings, Session

    Enable CHAP for the Microsoft iSCSI initiator. Select the General tab. Click Secret in the middle of the screen. Click Reset. Enter the MPX200 iSCSI Presented Target CHAP secret (for example: hpstorageworks). Click Discovery. • To discover iSCSI target portals manually: Click Add under Target Portals.

  • Page 96

    iSCSI Port General Tab Secret hpstorageworks hpstorageworks Discovered iSCSI Add Target Portal CHAPsecret01 CHAPsecret0 Initiator iSCSI Presented Log on to Target CHAPsecret01 Target 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).

  • Page 97

    Enable CHAP for the Microsoft iSCSI initiator. Select the General tab. Click Secret in the middle of the screen. Click Reset. Enter the MPX200 iSCSI Presented Target CHAP secret (for example: hpstorageworks). Click OK. Click Discovery. • To discover iSCSI target portals manually: Click Add under Target Portals.

  • Page 98

    Enabling bi-directional CHAP during discovery session and bi-directional CHAP during normal session Table 12 lists the settings you use to enable bi-directional CHAP during a discovery session and bi-directional CHAP during a normal session. Table 12 CHAP bi-directional settings MPX200 secret settings Microsoft initiator secret settings Source Setting (example)

  • Page 99

    Enable CHAP for the MPX200 iSCSI presented target using the CLI: Enter the set CHAP command. Select the Presented Target the initiator will log in to. Enable CHAP and enter a CHAP secret (for example, hpstorageworks). Enable CHAP for the Microsoft iSCSI initiator. Select the General tab.

  • Page 100

    MPX200 iSCSI configuration rules and guidelines...

  • Page 101: Mpx200 Fcip, Mpx200 Fcip Product Description, Redundant Fcip Network Structure Example, Mpx200 Basic Fcip Configuration

    5 MPX200 FCIP MPX200 FCIP product description The HP StorageWorks MPX200 Multifunction Router with an FCIP license provides FC SAN extension over an IP network. Used in conjunction with the EVA storage system families and the HP Continuous Access EVA 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 102: Using Fcip To Encapsulate Fc Packets, Fcip Impact On Existing Iscsi Configurations

    StorageWorks MPX200 Multifunction Router 10 1 GbE Base Chassis with a HP StorageWorks MPX200 Router 10 1 GbE Upgrade Blade. Note that FCIP is currently supported only on MPX200 1 GbE ports. See Figure Figure 57 MPX200 high-availability configuration with fully-redundant long-distance links Using FCIP to encapsulate FC packets With FCIP, gateways transport FC frames over an IP network.

  • Page 103: Fcip Impact On Existing Iscsi Configurations Single Fabric Per Blade

    remaining iSCSI FC port of that blade. Once the targets are rezoned, the impact to iSCSI is the loss of one 1 GbE port. Figure 58 FCIP impact on existing iSCSI configurations single fabric per blade Figure 59 FCIP impact on existing iSCSI configurations — dual fabrics per blade In the dual FC fabric case, the impact is higher because after adding an FCIP Route there is only one remaining FC port available for iSCSI.

  • Page 104: Mpx200 Iscsi/fcip Configurations, Mpx200 Basic Fcip Configuration With One Or Two Long-distance Links

    FCIP and iSCSI performance In most use cases, mixing iSCSI and FCIP on the same blade will provide adequate performance. However, high availability/performance goals may dictate a dedicated MPX200 for each function or protocol. For example, if your performance needs are for more that 8 Gb/s of FC access for iSCSI alone, configuring FCIP on the same blade would limit FC access to only 8 Gb/s and would not meet the performance requirements for that situation.

  • Page 105: Mpx200 High-availability Configuration With One Or Two Long-distance Links

    Figure 61 MPX200 high-availability configuration with one or two long-distance links Figure 62 MPX200 high-availability configuration with fully-redundant long-distance links Figure 63 MPX200 configuration with remote IP Distance gateway (mpx110) MPX200 Multifunction Router...

  • Page 106: Mpx200 Highly-redundant Configuration With One Or Two Long-distance Lists

    Figure 64 MPX200 highly-redundant configuration with one or two long-distance lists Figure 65 MPX200 highly redundant pairs of gateways with fully-redundant long-distance links MPX200 FCIP...

  • Page 107: Mpx200 Simultaneous Iscsi And Fcip With Remote Dedicated Fcip Blade

    Figure 66 MPX200 simultaneous iSCSI and FCIP with remote dedicated FCIP blade Figure 67 MPX200 simultaneous iSCSI and FCIP, both local and remote MPX200 Multifunction Router...

  • Page 108: Hp Continuous Access Eva 3 Site Configurations

    Figure 68 MPX200 iSCSI and FCIP dedicated blades, both local and remote HP Continuous Access EVA 3 site configurations This section describes the following HP Continuous Access EVA 3-site configurations: • HP Continuous Access EVA 3-site configuration with four MPX200 routers •...

  • Page 109: Site Configuration With Four Mpx200 Routers, Site Configuration With Six Mpx200 Routers

    3-site configuration with four MPX200 routers The configuration shown in Figure 69 provides long-distance link redundancy between all three sites. Figure 69 HP Continuous Access EVA 3 site configuration with four MPX200 routers 3-site configuration with six MPX200 routers The configuration shown in Figure 70 provides the same long-distance link redundancy as the configuration shown in...

  • Page 110: Site Configuration With Eight Mpx200 Routers

    Figure 70 HP Continuous Access EVA 3 site configuration with six MPX200 routers 3-site configuration with eight MPX200 routers The configuration shown in Figure 71 provides the highest 3-site redundancy, with a dedicated MPX200 pair for all long-distance links to all three sites. MPX200 FCIP...

  • Page 111: Site Configuration With Six Mpx200 Routers And Full Inter-site Connectivity

    Figure 71 HP Continuous Access EVA 3 site configuration with eight MPX200 routers 3-site configuration with six MPX200 routers and full inter-site connectivity Figure 72 provides long-distance link redundancy and full connectivity between all three sites. MPX200 Multifunction Router...

  • Page 112: Configuration Rules And Guidelines, General Configuration Rules

    Figure 72 HP Continuous Access EVA 3 site configuration with six MPX200 router full peer-to-peer connectivity Configuration rules and guidelines This section defines the configuration rules for using the MPX200 Multifunction Router. General configuration rules The following general configuration rules apply: •...

  • Page 113: Operating System And Multipath Support, Eva Storage System Rules And Guidelines

    Operating system and multipath support The MPX200 Multifunction Router is supported using FCIP with all operating systems and multipath software supported by HP for Continuous Access EVA. For more information, see the HP StorageWorks SAN design reference guide, available at http://www.hp.com/go/SDGManuals. EVA storage system rules and guidelines •...

  • Page 114: Network Requirements For The Mpx200 With Xcs And Vcs

    FC switch requirements For additional B-series and C-series FC switches, local and remote MPX200 Multifunction Router pairs must be connected to the same Fibre Channel switch product line series. NOTE: The MPX200 Fibre Channel ports operate at 2, 4, and 8 Gb/s. IP network requirements HP requires that the following standards be met for the IP network: •...

  • Page 115: Ip Performance Tuning, Distance, Bandwidth, Latency, Mtu/jumbo Frames

    IP performance tuning The MPX200 supports Fibre Channel service at transmission rates of 1 Gb/s or 2 Gb/s with a maximum frame size of 2,148 bytes. It supports Ethernet service at transmission rates of 1,000 or 100 Mb/s with an MTU size between 1,000 and 9,000 bytes (jumbo frames). Related performance characteristics include the following: •...

  • Page 116: Compression, Tcp Window Size/scaling Performance Tuning, Modifying The Window Size And Scaling Factor

    Encryption boxes on the WAN link often add a few bytes to each frame, so it may be necessary to decrease the MTU size to 1450 to allow the encryption box add the bytes and keep the MTU size under 1500 bytes. NOTE: Jumbo frames are not supported for use with HP Continuous Access EVA Continuous Access.

  • Page 117: Tcp Window Size Recommendations, T1/ds-1 1.554 Mb/sec (bandwidth = 1 Mb)

    256 to 512 512 or greater TCP window size recommendations Table 16 through Table 22 provide TCP window scaling factor and window size settings for specific WAN environments. These tables are organized by typical link speed. NOTE: The TCP window size recommendations listed in Table 16 through Table 22...

  • Page 118: Oc—1 50 Mb/sec (bandwidth = 50 Mb), Oc—3 150 Mb/sec (bandwidth = 148 Mb)

    128K 1 or less Table 18 OC—1 50 Mb/Sec (Bandwidth = 50 Mb) Round trip time (RTT) in Compression recommend- Window size (bytes) Scaling factor (2 ation 512K 256K 128K 128K 128K 1 or less Table 19 OC—3 150 Mb/Sec (Bandwidth = 148 Mb) Round trip time (RTT) in Compression recommend- Window size (bytes)

  • Page 119: Ds 5 400 Mb/sec (bandwidth = 384 Mb), Oc—12 621 Mb/sec (bandwidth = 699 Mb)

    1 or less Table 20 DS 5 400 Mb/Sec (Bandwidth = 384 Mb) Round trip time (RTT) in Compression recommend- Window size (bytes) Scaling factor (2 ation 512K 512K 256K 256K 128K 1 or less Table 21 OC—12 621 Mb/Sec (Bandwidth = 699 Mb) Round trip time (RTT) in Compression recommend- Window size (bytes)

  • Page 120: Configuring An Fcip Route, Step 1. Verify Your System Requirements

    512K 1 or less 128K Configuring an FCIP route Step 1. Verify your system requirements Verify that you have the following for both the local site and the remote site (see Figure 56 on page 101): • HP StorageWorks MPX200 Multifunction Router 1 GbE Base Chassis or HP StorageWorks MPX200 Multifunction Router 10 1 GbE Base Chassis.

  • Page 121: Step 2. Pre-installation Checklist, Step 3. Rack-mount The Mpx200, Step 4. Install The Sfps

    Step 2. Pre-installation checklist Before you begin the configuration process, contact your system administrator for the following information for both sites: • IP address, subnet mask and gateway for the MPX200 management port (if not using DHCP) • IP address, subnet mask and gateway for the first available GE port •...

  • Page 122: Mpx200 Ports And Leds

    Verify that the heartbeat LED is blinking (once per second) and that the System fault LED does not light. Figure 73 shows the location of the ports and LEDs on the MPX200. 1 GbE iSCSI ports Input fault LED System power LED Heartbeat LED HP StorageWorks MPX200...

  • Page 123: Step 6. Configure The Mpx200 Fcip Route Parameters, Install Fcip License, Critical Fcip Performance Settings

    Enter the command set mgmt to set the initial parameters. Follow the on-screen prompts to configure the management port (or press Enter to accept the default settings, as shown in Figure 74): Figure 74 Setting IP addresses The management port is now configured with the appropriate IP address and network parameters. IMPORTANT: If you are using Telnet to configure the MPX200, the Telnet session is terminated.

  • Page 124: Configure The Fcip Routes Using The Cli

    • TCP Windows size • TCP Windows scaling factor • Use the recommended setting documented in this guide for the actual bandwidth and RTT of the link • Software compression • Enable compression for IP links with round-trip time (RTT) >= 50 milliseconds or a guaranteed WAN bandwidth <= 155 Mb/s.

  • Page 125: Step 8. Cable The Mpx200 Fc, Ge And Management Ports

    • C-Switch(config)# in-order-guarantee VSAN n (where n stands for all VSANs that use the FCIP link) • C-Switch(config)# vsan database • C-Switch(config-vsan-db)# vsan n loadbalancing src-dst-id (where n stands for all VSANs that use the FCIP link) • C-Switch(config-vsan-db)# exit •...

  • Page 126

    MPX200 FCIP...

  • Page 127: Diagnostics And Troubleshooting, Mpx200 Chassis Diagnostics, Input Power Led Is Extinguished, Mpx200 Chassis Diagnostic Leds

    6 Diagnostics and troubleshooting This chapter describes MPX200 chassis diagnostics and provides information to help you troubleshoot problems. Diagnostic information is also available through diagnostics, HP Command View EVA, and the CLI event logs and error messages. MPX200 chassis diagnostics Chassis diagnostics are indicated by the chassis LEDs shown in Figure NOTE:...

  • Page 128: System Fault Led Is Illuminated, Power-on Self-test (post) Diagnostics, Heartbeat Led Blink Patterns

    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 129: Locating The Mpx200 Blade, Management Port Ip Address Conflict Blink Pattern, Over-temperature Blink Pattern

    Management port IP address conflict blink pattern An IP address conflict on the management port is indicated by a four-blink pattern (Figure 80). Figure 80 Management 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.

  • Page 130: Mpx200 Log Data, Mpx200 Statistics, Mpx200 Ping Command

    • In HP Command View EVA, select the General tab, and then click the Locate button. Use the Locate ON and Locate OFF buttons to control the blue LED (Figure 83). Figure 83 Using HP Command View EVA to locate a hardware device MPX200 log data The MPX200 maintains a log that can be displayed through the CLI.

  • Page 131: Troubleshooting Using Hp Command View Eva, Fcip Route Ping Command, Iscsi Controller Properties

    Figure 84 FCIP route ping command Troubleshooting using HP Command View EVA You can use HP Command View EVA to display the properties for each iSCSI controller. At a glance, you can check each controller’s serial number, temperature, and power/cooling status (Figure 85).

  • Page 132: Issues And Solutions, Hp Command View Eva Does Not Discover Mpx200

    Issues and solutions HP Command View EVA does not discover MPX200 Solution 1: Ensure that a DHCP server is available. Solution 2: Use the CLI to set a static IP address on each MPX200 blade. Solution 3: Ensure that the HP Command View EVA station is on the same subnet as the management ports.

  • Page 133: Eva-presented Virtual Disk Not Seen By Initiator, Virtual Disk Properties: Host Details

    EVA-presented virtual disk not seen by initiator Solution: The initiator must log in to the appropriate iSCSI target. Match the virtual disk presentation properties to the initiator’s target login (Figure 87 Figure 88). Figure 87 Virtual disk properties: Host details Figure 88 iSCSI initiator properties: Targets tab MPX200 Multifunction Router...

  • Page 134: Communication Between Hp Command View Eva And Mpx200 Is Down

    Windows initiators may display Reconnecting if NIC MTU changes after connection has logged in Solution. Log out of the sessions and log in again to re-establish the Connected state. Communication between HP Command View EVA and MPX200 is down When communication between HP Command View EV and the MPX200 is down, use the following options: •...

  • Page 135

    Unable to process the command at this time. iSCSI Check all FC connections and zoning. controller FC ports are unavailable. Ensure that the correct file is being used to restore the Invalid iSCSI controller configuration file extension. configuration. The firmware file may be invalid or corrupt. Obtain Operation failed.

  • Page 136

    Diagnostics and troubleshooting...

  • Page 137: Support And Other Resources, Intended Audience, Related Documentation

    7 Support and other resources This user guide provides information to help you do the following: • Understand the MPX200 options and configurations • Plan the installation of the MPX200 • Install the MPX200 • Configure the MPX200 for iSCSI •...

  • Page 138: Contacting Hp, Hp Technical Support, Subscription Service, Product Feedback, Documentation Feedback, Related Information, Hp Websites

    For EVA documents, go to Storage and select Disk Storage Systems. For MPX200 documents, go the Storage Category and select Storage Networking. Contacting HP HP technical support For worldwide technical support information, see the HP support website: http://www.hp.com/support Before contacting HP, collect the following information: •...

  • Page 139: Typographical Conventions, Document Conventions

    • HP Partner Locator: http://www.hp.com/service_locator • HP Software Downloads: http://www.hp.com/support/downloads • HP Software Depot: http://h20293.www2.hp.com • HP Single Point of Connectivity Knowledge (SPOCK) http://www.software.hp.com • HP StorageWorks SAN manuals: http://www.hp.com/go/sdgmanuals Typographical conventions Table 23 Document conventions Convention Element Blue text: Table 23 Cross-reference links and email addresses Blue, underlined text:...

  • Page 140: Rack Stability, Product Warranties

    Convention Element An alert that calls attention to additional or supplementary NOTE: information. TIP: An alert that calls attention to helpful hints and shortcuts. Rack stability To reduce the risk of personal injury or damage to equipment: • Extend leveling jacks to the floor. •...

  • Page 141: A Command Reference, Command Syntax, Command Line Completion, Authority Requirements, Command Line Completion Keystrokes

    A Command reference This chapter lists and describes the MPX200 CLI commands in alphabetical order. Each command description includes syntax, keywords, notes, and examples. 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.

  • Page 142: Commands, Admin

    • Commands for configuration tasks are available only in an Admin session. An account must have admin authority to execute the admin start command, which opens an Admin session (see admin command). Commands This section lists and describes the MPX200 CLI commands in alphabetical order. Each command description includes syntax, keywords, notes, and examples.

  • Page 143: Beacon, Blade, Clear

    Beacon Enables or disables the flashing of the blue beacon LED. Authority None Syntax beacon Turns on the flashing beacon. Keywords Turns off the flashing beacon. Example: The following example shows how to turn the flashing beacon on: MPX200 <1>#> beacon on Blade Allows you to select the blade to be managed.

  • Page 144: Date, Exit

    Date Displays or sets the date and time. To set the date and time, enter the information in the format MMDDhhmmCCYY (numeric representation of month-date-hour-minute-century-year). The new date and time take effect immediately. each blade separately. This ensures that event log entries are dated correctly.

  • Page 145: Fciproute

    Fciproute Configures a new FCIP route or modifies or deletes an existing FCIP route. Each FCIP route requires a dedicated FC and Gigabit Ethernet (GbE) port. Configuring an FCIP route and specifying an FC and GE port pair take precedence over any previous configuration for the port pair (FC/GE). Authority Admin session Syntax...

  • Page 146

    WARNING: The following command might cause a loss of connections to both GE ports. Route FC Port ID GE Port ID ----- ---------- ---------- Please select a FCIP route from the list above ('q' to quit): 1 Configuring FCIP Route: ----------------------- FCIP Interfaces FC &...

  • Page 147: Help

    Saves and restores the router’s configuration. Authority Admin session to restore restore Syntax save The fru restore command requires that you first FTP the tar file containing the configuration to the router. When you issue this command, the system prompts you to enter the restore level.

  • Page 148

    logout quit 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] clear [logs | stats] exit fru [restore | save] help...

  • Page 149: History, Image

    show mgmt show ntp show perf [byte | init_rbyte | init_wbyte |tgt_rbyte | rgt_wbyte] show presented_targets [fc|iscsi] show properties] show snmp show stats show system show targets [fc | iscsi] show vpgroups [vpgroup index] shutdown target [rm] traceroute History Displays a numbered list of the previously entered commands. Authority None Syntax...

  • Page 150: Initiator

    MPX200 <1>(admin) #> image cleanup Example 2: MPX200 <1>(admin) #> image list Image Location Image File -------------- ---------- 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) #>...

  • Page 151: Logout, Lunmask

    'Q' and the ENTER key to do so. OS Type (0=MS Windows, 1=Linux, 2=Other) [MS Windows ] All attribute values that have been changed will now be saved. Example 3: MPX200 <1>(admin) #> initiator remove Index Status (WWNN,WWPN/iSCSI Name) ----- ------ ---------------------- 0 LoggedOut test 1 LoggedOut iqn.1991-05.com.microsoft:server1 Please select a 'LoggedOut' Initiator from the list above ('q' to quit): 0...

  • Page 152

    2 20:00:00:20:37:fd:9c:f7,22:00:00:20:37:fd:9c:f7 3 20:00:00:20:37:fd:8d:00,22:00:00:20:37:fd:8d:00 Please select a Target from the list above ('q' to quit): 0 LUN WWULN Vendor ---- ---------- -------- 0 20:00:00:20:37:fd:8b:ab:00:00:00:00:fc:b7:3f:fa SEAGATE Please select a LUN to present to the initiator ('q' to quit): 0 All attribute values that have been changed will now be saved. Example 2: The following example shows the lunmask add command with VPGs: MPX200 <1>(admin) #>...

  • Page 153: Passwd, Ping

    MPX200 <1>(admin) #> lunmask remove Index (WWNN,WWPN/iSCSI Name) ----- ---------------------- 0 50:06:01:60:c1:e0:0d:a2,50:06:01:60:41:e0:0d:a2 1 50:06:01:60:c1:e0:0d:a2,50:06:01:68:41:e0:0d:a2 Please select a Target from the list above ('q' to quit): 0 Index (LUN/VpGroup) Vendor ----- ------------- ------ 0 0/VPGROUP_1 DGC 1 1/VPGROUP_1 DGC 2 2/VPGROUP_1 DGC 3 3/VPGROUP_1 DGC 4 0/VPGROUP_2 DGC Please select a LUN from the list above ('q' to quit): 0...

  • Page 154: Quit, Reboot

    'Q' and the ENTER key to do so. IP Address (IPv4 or IPv6) [0.0.0.0] fe80::217:a4ff:fe99:c279 Iteration Count (0=Continuously) [0 ] 10 Outbound Port (0=Mgmt, 1=GE1, 2=GE2, ...) [Mgmt ] Size Of Packet (Min=1, Max=65486 Bytes) [56 ] Pinging fe80::217:a4ff:fe99:c279 with 56 bytes of data: Request timed out.

  • Page 155: Reset, Save

    Reset Restores the router configuration parameters to the factory default values. The reset factory command deletes all LUN mappings, as well as all persistent data for targets, LUNs, initiators, VPG settings, log files, iSCSI and management IP addresses, FC and Ethernet port statistics, and passwords. This command also restores the factory default IP addresses.

  • Page 156

    The save traces command creates a tar file that con- tains the router’s dump data, storing the file in the router’s /var/ftp directory. When the command has finished ex- ecuting, you must FTP the trace’s tar file from the blade. traces The system notifies you if the router does not have any dump data.

  • Page 157: Set Alias

    Applies license keys to the router. See “set features features command” on page 159. Sets the iSCSI port parameters. See “set iSCSI iscsi [<PORT_NUM>] command” on page 160. Sets the Internet Simple Name Service (iSNS) parameters. See “set iSNS com- isns mand”...

  • Page 158: Set Chap, Set Chassis

    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. Set CHAP Configures the CHAP parameters.

  • Page 159: Set Features

    Chassis Name (Max = 64 characters) [ ] rack 14 All attribute values that have been changed will now be saved. Set FC Configures an FC port. Authority Admin session Syntax set fc [<PORT_NUM>] Keywords The number of the FC port to be configured. [ <...

  • Page 160: Set Iscsi, Set Isns

    Syntax set features Set iSCSI Configures an iSCSI port. Authority Admin session set isc- [<PORT_NUM>] Syntax Keywords [ < P O R T _ N U M > ] 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.

  • Page 161: Set Mgmt, Set Ntp

    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. iSNS (0=Enable, 1=Disable) [Disabled ] 0 iSNS Address (IPv4 or IPv6) [0.0.0.0 ] 10.3.6.33 TCP Port No. [3205 ] All attribute values that have been changed will now be saved.

  • Page 162: Set Properties, Set Snmp

    Example: MPX200 <1>(admin) #> set ntp A list of attributes with formatting and current values will follow. Enter a new value or simply press the ENTER key to accept the current value. If you wish to terminate this process before reaching the end of the list press 'q' or 'Q' and the ENTER key to do so.

  • Page 163: Set System

    Authentication Traps (0=Enable, 1=Disable) [Disabled ] All attribute values that have been changed will now be saved. Example 2: The following example shows the set snmp command for configuring an SNMP trap destination: MPX200 <1>(admin) #> set snmp trap_destinations 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 164: Show

    alphabetical (a-z, A-Z), numerical (0-9), colon, hyphen, and period. Changes to the Settings below will be effective after a reboot. System Symbolic Name (Max = 64 characters) [Blade-1 ] Embed Symbolic Name (0=Enable, 1=Disable) [Disabled ] Mode (0=iSCSI Server Connectivity), 1=SAN over WAN, 2=iSCSI Server Connectivity/SAN over WAN, 3=Data Migration) [iSCSI Connectivity]...

  • Page 165

    chap chassis fc [port_num] features initiators [fc or iscsi] initiators_lunmask iscsi [port_num] isns [port_num] logs [last_x_entries] luninfo lunmask luns memory Syntax show mgmt perf [ byte | init_rbyte | init_wbyte | tgt_rbyte | tgt_wbyte ] presented_targets [fc or iscsi] properties snmp stats system...

  • Page 166: Show Chap

    Displays detailed LUN information for a specified target and LUN. See “show LUNinfo com- luninfo mand” on page 172. Displays LUN mappings. See “show lunmask lunmask command” on page 173. Displays information about LUNs and their targets. luns “show LUNs command”...

  • Page 167: Show Chassis

    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. You can execute this command from the chassis management level or blade management level.

  • Page 168: Show Fciproutes

    Show FC Displays FC port information for the specified port. If you do not specify a port, the command displays all ports. Authority None [port_num] Syntax show fc [port_num] Keywords Identifies the number of the FC port. Example: MPX200 <1>#> show fc 2 FC Port Information --------------------- FC Port 2...

  • Page 169: Show Features, Show Initiators, Show Initiators Lunmask

    TCP Window Size 32768 Window Scaling Enabled Window Scaling Factor TCP Port No 3225 Current GE Port Speed 100Mb/FDX Programmed GE Port Speed Auto Bandwidth, Mbit/sec 1000 VLAN Disabled FCIP SW Compression Disabled MPX200 <2> (admin) #> Show features Displays any licensed features. Authority None Syntax...

  • Page 170: Show Iscsi

    Authority None Syntax show initiators_lunmask Example: MPX200 <1>#> show initiators_lunmask Index (WWNN,WWPN/iSCSI Name) ----- ---------------------- 0 iqn.1991-05.com.microsoft:server1 Please select an Initiator from the list above ('q' to quit): 0 Target(WWPN) (LUN/VpGroup) VendorId ------------ ------------- -------- 21:00:00:11:c6:17:12:22 0/VPGROUP_1 SEAGATE 50:06:01:60:3a:60:0a:63 0/VPGROUP_2 50:06:01:60:3a:60:0a:63 1/VPGROUP_2 50:06:01:60:3a:60:0a:63 2/VPGROUP_2 50:06:01:60:3a:60:0a:63 3/VPGROUP_2...

  • Page 171: Show Isns, Show Logs

    IPv6 Address 2 IPv6 Link Local fe80::2c0:ddff:fe13:1644 IPv6 Default Router IPv6 Target TCP Port No. IPv6 VLAN Disabled iSCSI Max First Burst 65536 iSCSI Max Burst 262144 iSCSI Header Digests Disabled iSCSI Data Digests Disabled Show iSNS Displays iSNS configuration information for the specified iSCSI port. If you do not specify a port, the command displays iSNS configuration information for all iSCSI ports.

  • Page 172: Show Luninfo, Show Luns

    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) ----- ------ 0/VPGROUP_1 1/VPGROUP_1 Please select a LUN from the list above ('q' to quit): LUN Information...

  • Page 173: Show Lunmask, Show Memory

    VPGROUP_2 VPGROUP_2 Show LUNmask Displays all initiators mapped to the specified LUN. Authority None Syntax show lunmask Example: MPX200 <1>#> show lunmask Index (WWNN,WWPN/iSCSI Name) ----- ---------------------- 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 174: Show Mgmt, Show Ntp

    MPX200 <1>#> show memory Memory Units Free/Total -------------- ---------- Physical 415MB/1002MB Buffer Pool 6866/8960 Nic Buffer Pool 0/0 Process Blocks 8192/8192 Request Blocks 8192/8192 Event Blocks 2048/2048 Control Blocks 2048/2048 Sessions 2048/2048 Connections: GE1 256/256 GE2 256/256 GE3 256/256 GE4 256/256 Show mgmt Displays the blade’s management port (10/100) configuration.

  • Page 175: Show Perf

    Show perf Displays the port, read, write, initiator, or target performance, in bytes per second (b/s). Authority None [byte | init_rbyte | init_wbyte | tgt_rbyte show Syntax | tgt_wbyte ] perf Displays performance data for all ports. byte Displays initiator mode read performance. init_rbyte Keywords Displays initiator mode write performance.

  • Page 176: Show Presented Targets

    Example 4: MPX200 <1>#> show perf tgt_wbyte WARNING: Valid data is only displayed for port(s) that are not associated with any configured FCIP routes. Displaying bytes/sec (target mode write)... (Press any key to stop display) -------------------------------- Show presented targets Displays the targets presented by the FC router, iSCSI router, or both. Authority None show...

  • Page 177: Show Properties, Show Snmp

    WWPN 50:00:1f:e1:50:07:0c:e9 Name iqn.1986–03.com.hp:fcgw.mpx200.0834e00025.b1.04.50001fe150070ce9 Alias <MAPS TO> WWNN 50:00:1f:e1:50:07:0c:e0 WWPN 50:00:1f:e1:50:07:0c:e9 Name iqn.1986–03.com.hp:fcgw.mpx200.0834e00025.b1.01.50001fe150070cec Alias <MAPS TO> WWNN 50:00:1f:e1:50:07:0c:e0 WWPN 50:00:1f:e1:50:07:0c:ec Name iqn.1986–03.com.hp:fcgw.mpx200.0834e00025.b1.02.50001fe150070cec Alias <MAPS TO> WWNN 50:00:1f:e1:50:07:0c:e0 WWPN 50:00:1f:e1:50:07:0c:ec Name iqn.1986–03.com.hp:fcgw.mpx200.0834e00025.b1.03.50001fe150070cec Alias <MAPS TO> WWNN 50:00:1f:e1:50:07:0c:e0 WWPN 50:00:1f:e1:50:07:0c:ec Name iqn.1986–03.com.hp:fcgw.mpx200.0834e00025.b1.04.50001fe150070cec Alias <MAPS TO>...

  • Page 178: Show Stats

    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 System Description HP StorageWorks MPX200 Trap Destination 1 ------------------ IP Address 10.0.0.5 Trap Port 1024 Trap Version 2 Show stats Displays the blade statistics for FC and iSCSI.

  • Page 179

    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 MAC Rcvd CRC Errors 0 MAC Rcvd Encoding Errors 0 MAC Rcvd Length Errors Large 1...

  • Page 180: Show System

    PDU Xmit Count 2729500577 PDU Xmit Count 2729500577 IP Xmit Packets 54392134283 IP Xmit Byte Count 59132566295008 IP Xmit Fragments 0 IP Rcvd Packets 42061430681 IP Rcvd Byte Count 58764046068744 IP Rcvd Fragments 0 IP Datagram Reassembly Count 0 IP Error Packets 0 IP Fragment Rcvd Overlap 0 IP Fragment Rcvd Out of Order 0 IP Datagram Reassembly Timeouts 0...

  • Page 181: Show Targets, Show Vpgroups

    Show targets Displays the targets discovered by the FC router, iSCSI router, or both. Authority None show tar- Syntax iscsi gets Displays FC targets. Keywords 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...

  • Page 182: Shutdown, Target

    MPX200 <1>#> show vpgroups VpGroup Information --------------------- Index VpGroup Name VPGROUP_1 Status Enabled WWPNs 21:00:00:c0:dd:13:16:44 21:00:00:c0:dd:13:16:45 Index VpGroup Name VPGROUP_2 Status Enabled WWPNs 21:01:00:c0:dd:13:16:44 21:01:00:c0:dd:13:16:45 Index VpGroup Name VPGROUP_3 Status Enabled WWPNs 21:02:00:c0:dd:13:16:44 21:02:00:c0:dd:13:16:45 Index VpGroup Name VPGROUP_4 Status Enabled WWPNs 21:03:00:c0:dd:13:16:44 21:03:00:c0:dd:13:16:45...

  • Page 183: Traceroute

    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 quit): 0 All attribute values for that have been changed will now be saved.

  • Page 184

    Command referencecommand reference...

  • Page 185: B Command Line Interface Usage, Logging On To An Mpx200

    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 Secure Shell (SSH) to log on to a router, or you can log on to the switch through the serial port.

  • Page 186: Understanding The Guest Account

    Understanding the guest account Routers come from the factory with the guest account already defined. This guest account provides access to the router and its configuration. After planning your router management needs, consider changing the password for this account. For information about changing passwords, see the “passwd command”...

  • Page 187: Modifying A Configuration, Saving And Restoring Router Configurations, Working With Mpx200 Router Configurations

    MPX200 #>blade 1 MPX200 <1>#> Working with MPX200 router configurations Successfully managing routers with the CLI depends on effective router configurations. Key router management tasks include modifying configurations, backing up configurations, and restoring configurations. Modifying a configuration The router has the following major areas of configuration: •...

  • Page 188: Restoring Router Configuration And Persistent Data

    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. Restoring router configuration and persistent data Transfer the saved data from a workstation to the router by executing an FTP utility on the workstation.

  • Page 189: C Simple Network Management Protocol Setup, Snmp Parameters

    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 190: Network Port Table, Snmp Trap Configuration Parameters, Management Information Base

    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 26 describes the parameters for configuring an SNMP trap. Table 26 SNMP trap configuration parameters Parameter Description Enables or disables trap n.

  • Page 191

    qsrNwPortRole QsrPortRole qsrNwPortIndex unsigned32 qsrNwPortAddressMode INTEGER qsrIPAddressType InetAddressType qsrIPAddress InetAddress qsrNetMask InetAddress qsrGateway InetAddress qsrMacAddress MacAddress 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...

  • Page 192: Fc Port Table

    qsrIPAddress Syntax InetAddress Access Read-only Description IP address of the port. qsrNetMask Syntax InetAddress Access Read-only Description Subnet mask for this port. qsrGateway Syntax InetAddress Access Read-only Description Gateway for this port. qsrMacAddress Syntax IMacAddress Access Read-only Description MAC address for this port. qstNwLinkStatus Syntax QsrLinkStatus...

  • Page 193

    qsrFcPortTable Syntax SEQUENCE OF QsrFcPortEntry Access Not accessible A list of the FC ports on the router. The table contains as many entries Description as there are FC ports on the router. qsrFcPortEntry Syntax QsrFcPortEntry Access Not accessible Description Each entry (row) contains information about a specific FC port. An FC port entry consists of the following sequence of objects: qsrFcPortRole QsrPortRole...

  • Page 194: Initiator Object Table

    Description World Wide Name of the node that contains this port. qsrFcPortWwn Syntax PhysAddress Access Read-only Description World Wide Name for this port. qsrFcPortId Syntax PhysAddress Access Read-only Description Interface's 24-bit FC address identifier. qsrFcPortType Syntax Unsigned32 Access Read-only Type of FC port, as indicated by the use of the appropriate value as- Description signed by IANA.

  • Page 195

    Access Not accessible Description Entries in this table contain Information about initiators. qsrIsInitEntry Syntax QsrIsInitEntry Access Not accessible Description Each entry (row) contains information about a specific iSCSI initiator. An iSCSI initiator information entry consists of the following sequence of the objects: qsrIsInitIndex Unsigned32 qsrIsInitName...

  • Page 196: Lun Table

    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 Integer: 1 = unknown, Syntax 2 = loggedIn, 3 = loggedOut, 4 = recovery Access Read-only Status of the iSCSI initiator, that is, whether or not it is logged in to the...

  • Page 197

    Access Not accessible A list of the LUNs on the FC targets discovered by the router. There are Description as many entries in this table as there are FC targets on the router. qsrLunEntry Syntax QsrLunEntry Access Not accessible Each entry (row) contains information about a specific LUN. This table Description extends scsiDscLunTable in QLOGIC-SCSI-MIB.

  • Page 198: Vp Group Table

    qsrLunProdRevLevel Syntax SnmpAdminString Access Read-only Description Product revision level for the LUN qsrLunSize Syntax Unsigned32 Access Read-only Description Size of the LUN (in megabytes) qsrLunState Integer 1 = online, Syntax 2 = offline, 3 = reserved Access Read-only Description State of the LUN (online or offline) qsrLunVPGroupid Syntax Integer...

  • Page 199

    qsrVPGroupEntry Syntax QsrVPGroupEntry Access Not accessible Description Each entry in the VP group table Index { qsrVPGroupIndex } ::= { qsrVPGroupTable 1 } The QsrVPGroupEntry contains the following sequence of objects: qsrVPGroupIndex Unsigned32 qsrVPGroupId INTEGER qsrVPGroupName SnmpAdminString qsrVPGroupWWNN VpGroupWwnnAndWwpn qsrVPGroupWWPN VpGroupWwnnAndWwpn qsrVPGroupStatus INTEGER...

  • Page 200

    qsrVPGroupStatus Integer: 0 = enabled; 1 = disabled Syntax Access Read-only Description Maintain the status of the VP group (enabled/disabled) Simple Network Management Protocol setup...

  • Page 201: 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 List of all the sensors on the router. The table contains as many entries Description (rows) as there are sensors.

  • Page 202: Notifications

    qsrSensorUnits INTEGER Syntax Celsius = 1 Access Read-only Description Unit of measurement for the sensor. qsrSensorValue Syntax Integer32 Access Read-only Description Current value of the sensor. qsrUpperThreshold Syntax Integer32 Access Read-only Description Upper-level threshold for this sensor. qsrLowerThreshold Syntax Integer32 Access Read-only Description...

  • Page 203: System Information Objects

    NOTE: Every notification uses qsrBladeSlot as one of the objects. This determines the originator blade for the same notification. System information objects System information objects provide the system serial number, version numbers (hardware/software/agent), and number of ports (FC/GE). qsrSerialNumber Syntax SnmpAdminString Access Read-only...

  • Page 204: Notification Objects, Agent Startup Notification, Agent Shutdown Notification, Network Port Down Notification

    Syntax SnmpAdminString Access Read-only Description Version number of the agent software on the system. Notification objects This section defines the objects used in notifications. qsrEventSeverity Syntax INTEGER Access Accessible for notify Indicates the severity of the event. The value clear specifies that a Description condition that caused an earlier trap is no longer present.

  • Page 205: Fc Port Down Notification, Target Device Discovery, Target Presentation (mapping)

    • qsrNwLinkStatus • qsrEventTimeStamp • qsrEventSeverity Network notifications are sent for the following events: • Management port: down or up • iSCSI port: down or up • Port number (1 4) FC port down notification The FC port down notification indicates that the specified FC port is down. The next time the port comes up, this event is sent with the qsrEventSeverity object set to clear.

  • Page 206: Vp Group Notification, Sensor Notification

    • qsrPresTgtUnmapped • qsrEventSeverity Target presentation notifications are sent for the following event: • Target Presentation • State: Presented (mapped) or unpresented (unmapped) • Target name • Blade number (1 or 2) VP group notification The VP group notification indicates that the specified VP group is enabled or disabled. It also represents change in the name of the VP group.

  • Page 207: Generic Notification

    • PCM installed • PCM number (1 or 2) • PCM removed • PCM number (1 or 2) • PCM powered (AC power connected) • PCM number (1 or 2) • PCM un-powered (AC power removed) • PCM number (1 or 2) •...

  • Page 208

    • Blade number (1 or 2) Simple Network Management Protocol setup...

  • Page 209: D Log Messages, Mpx200 Log Messages

    D Log messages This appendix provides details about messages logged to a file. The message logs are persistent because they are maintained across router power cycles and reboots. Information in the following tables is organized as follows: • The ID column specifies the message identification numbers in ascending order. •...

  • Page 210

    Unable to create an object for the target QLBA_CreateTargetDeviceO- 41058 Error device; exceeded the maximum number of bject: Too many devices target devices. Unable to create an object for the target node; QLBA_CreateTargetNodeOb- 41060 Error exceeded the maximum number of target ject: Too many devices devices.

  • Page 211

    iSCSI login PDU received with an incorrect initiator task tag for a session which is partially QLIS_LoginPduContinue: logged in. This would occur if a login PDU 41272 Error CONN_STATE_IN_LOGIN, Un- other than the initial login PDU used an initiator known InitTaskTag task tag which was different than the initiator task tag provided in the initial login PDU.

  • Page 212

    Pass-Through command issued by management QLBI_Passthru: Invalid 41701 Error application (such as GUI) failed due to invalid data length %d bytes data length. Pass-Through command issued by management QLBI_Passthru: Invalid 41717 Error application (such as GUI) was interrupted or data length %d bytes timed out.

  • Page 213

    QLIS_InstantiateSession: Unable to allocate iSCSI initiator object while 42258 Error Can't add Initiator to instantiating session. the database QLIS_InstantiateSession: iSCSI session login rejected because the max- Maximum number (%d) of 42259 Error imum number of allowed hosts are already allowed hosts already logged in.

  • Page 214

    FC login occurred, origin xx (1 = adapter, 2 QLFC_Login: Origin 0x%x, 54274 Info = target, 3 = initiator), VP (virtual port) xx, ID VP Index 0x%x, Id 0x%x (loop ID) xx. QLFC_Login: Port ID 54275 Info FC login occurred with port ID xx.xx.xx. %.2x%.2x%.2x FC login occurred with WWNN QLFC_Login: Node Name...

  • Page 215

    #%d: qlutm_init: Diagnost- 69652 iSCSI Fatal iSCSI processor SRAM test failed. ic failed, invalid SRAM #%d: qlutm_init: Diagnost- 69653 iSCSI Fatal iSCSI processor failed diagnostic reboot. ic failed, fail reboot #%d: qlutm_init: Diagnost- 69654 iSCSI Fatal iSCSI processor failed NVRAM diagnostic. ic failed, invalid NVRAM #%d: qlutm_init: Diagnost- 69655...

  • Page 216

    #%d: QLProcessRespon- 70501 iSCSI Fatal Response queue invalid entry type. seQueue: Invalid entry type in response queue %x #%d: QLProcessRespon- Response queue invalid handle for specified 70502 iSCSI Fatal seQueue: Invalid handle entry type. %x EntryType %x #%d: QLProcessAen: Inval- 70524 iSCSI Fatal...

  • Page 217

    #%d: QLUtmReceiveScsiCmd: iSCSI processor reported an invalid Accept 74068 iSCSI Error Invalid ATIO Continuation Target I/O (ATIO) Continuation type x. type %x #%d: QLUtmProcessRespon- iSCSI processor reported an Immediate data seQueue: Immediate data 74069 iSCSI Error address (xxxxxxxx:xxxxxxxx) in an unsuppor- addr %08x:%08x in unsup- ted PDU type.

  • Page 218

    Driver’s initiator database is full. The driver is #%d: QLUpdateInitiat- capable of storing 1024 iSCSI initiators in its 74784 iSCSI Error orData: No more room in database. Use the CLI or GUI to remove un- Initiator Database. wanted/unused iSCSI initiators. Driver’s target database is full.

  • Page 219

    #%d: QLInitializeAdapter: FC processor receive sequencer code load 102658 Fatal Load ISP2322 receive se- failed. quencer code failed #%d: QLInitializeAdapter: FC processor transmit sequencer code load 102659 Fatal Load ISP2322 transmit se- failed. quencer code failed #%d: QLInitializeAdapter: 102662 Fatal FC processor firmware checksum failed.

  • Page 220

    FC processor failed to re-initialize in response #%d: QLIoctlDisable: Re- 106593 Error to an IOCTL disable request. initialize adapter failed #%d: QLIsrEventHandler: 106803 Error FC processor reported a link down condition. Link down (%x) #%d: QLIsrEventHandler: FC processor reported an unexpected asyn- Unexpected async event chronous event.

  • Page 221

    #%d: QLWriteFlashDword: FC controller failed a Flash write (address x 107984 Error Write fails at addr 0x%x data x). data 0x%x #%d: QLGetVpDatabase: FC controller failed the Get VP Database 108032 Error MBOX_CMD_GET_VP_DATABASE command (for virtual port %d). for VP %d fatal error #%d: QLGetVpDatabase: FC controller failed the Get VP Database 108033...

  • Page 222

    QBRPC_Initialize:Get- Get System Advanced API memory allocation 139267 User Error BridgeAdv Mem Allocation failed. error Get Management API memory allocation QBRPC_Initialize:GetMgmt 139268 User Error failed. Mem Allocation error QBRPC_Initialize:GetIscsi 139269 User Error Get iSCSI API memory allocation failed. Mem Allocation error Get iSCSI advanced API memory allocation QBRPC_Initialize:GetIscsi- 139270...

  • Page 223

    QBRPC_Initialize:Diag Mem 139298 User Error Failed memory allocation for Diagnostic API. Allocation error Failed memory allocation for Diagnostic Log QBRPC_Initialize:DiagLog 139299 User Error API. Mem Allocation error QBRPC_Initialize:FruImage 139300 User Error Failed memory allocation for FRU Image API. Mem Allocation error Failed memory allocation for OEM Manufac- QBRPC_Initialize:OemMfg 139301...

  • Page 224

    qapisetlunmask_1_svc: LUN mask was removed for LUN %d. 151895 User Info Lunmask removed for LUN qapisetmgmintfc- params_1_svc:Management 151896 User Info Management port configuration has changed. port configuration changed qapisetbridgebasi- 151897 User Info Router configuration has changed. cinfo_1_svc:Bridge config- uration changed GE%d: Port status changed GE port %d was enabled user.

  • Page 225

    sysTempMon: Power for 152133 User Info Left PCM is connected AC power. Left PCM Plugged-in Left PCM is not connected to AC power (un- sysTempMon: Power for 152134 User Info plugged). Left PCM Un-plugged sysTempMon: Power for 152135 User Info Right PCM is connected AC power.

  • Page 226

    Sys- "Failed to kill sys 237572 Error Failed to kill system task. killer %d\n" Sys- Router temperature has exceeded the high Temperature over high 237573 Error temperature threshold. threshold %d Sys- Router temperature has returned to the normal Temperature is back to 249862 Info operating range.

  • Page 227

    Table 28 DM log messages Mod- Mes- Log Message sage Description type type QLDM_HandleMigError: Mi- An error occurred on an I/O that was issued gration Job %d stopped for a migration job. The description provides 44549 Error for Src Lun %hd Dest Lun the job id, source and destination lun ids, as %hd Error %x AdditionalEr- well as the error.

  • Page 228

    QLDM_CreateMigrationOb- Failed to allocate memory for the destination 56871 Info ject: Failed to create LUN of a Migration job. Destination Lun Object QLDM_CreateMigrationOb- Failed to allocate memory for the Migration 56872 Info ject: MigrationObject job. memory unavailable Start time got from user The log displays the configured start time and 56880 Info...

  • Page 229

    ValidateSerialSchedule: Reset the serial schedule delayed time to inval- 152108 User Info Previous time %ld New id if the last serial schedule job was removed. time %ld addMigration: Creating 152109 User Info Failed to Create a Migration Job. migration Job Failed with error %d MPX200 Multifunction Router...

  • Page 230

    Table 29 FCIP log messages Mod- Mes- Log Message sage Description type type #%d: QLTimer: VP %d dis- A VP logs in to a device, but the device rejects 119144 Info cover a reject device PID the login. %02x%02x%02x #%d: QLFlashGetNvram: In- Update Nvram for the invalid Serial Link 120278 Info...

  • Page 231

    Indicates an error in the received FCIP PDU FcipRoute#%d: Synchroniz- 172238 FCIP Error Framing. The router will disconnect and recon- ation Error on Receive nect with the remote router to clear the error. Indicates that the receiver could not decom- press a received FCIP frame.

  • Page 232

    Route definition includes VLAN, but the net- work VLAN device instance does not exist. FcipRoute#%d: VLAN Info 184542 FCIP Info This is an internal error. Try removing and re- Unavailable entering the route definition. The Ethernet device could not successfully communicate with the link peer at the highest QL3xxx:eth%x PHY Down- 204835...

  • Page 233: Federal Communications Commission Notice For Class A Equipment, Modifications, Cables, Regulatory Compliance Identification Numbers

    Hewlett-Packard could result in the product not meeting the Class A limits, in which case the FCC could void the user's authority to operate the equipment.

  • Page 234: Laser Safety Warning, Certification And Classification Information, Laser Product Label, Class 1 Laser Product Label

    Laser safety warning WARNING! To reduce the risk of exposure to hazardous radiation: • Do not try to open the laser device enclosure. There are no user-serviceable components inside. • Do not operate controls, make adjustments, or perform procedures to the laser device other than those specified herein.

  • Page 235: Canadian Notice (avis Canadien), Class A Equipment, Bsmi Notice, Japanese Notice, International Notices And Statements

    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.

  • Page 236: Korean Notices, Battery Replacement Notice, Safety

    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.

  • Page 237: Taiwan Battery Recycling Notice, Power Cords, Japanese Power Cord Statement, English Notice

    Batteries, battery packs, and accumulators should not be disposed of together with the general household waste. To forward them to recycling or proper disposal, use the public collection system or return them to HP, an authorized HP Partner, or their agents. For more information about battery replacement or proper disposal, contact an HP authorized reseller or service provider.

  • Page 238: Dutch Notice, Czechoslovakian Notice, Estonian Notice, Finnish Notice

    This symbol on the product or on its packaging indicates that this product must not be disposed of with your other household waste. Instead, it is your responsibility to dispose of your waste equipment by handing it over to a designated collection point for recycling of waste electrical and electronic equipment.

  • Page 239: French Notice, German Notice, Greek Notice

    Jos tuotteessa tai sen pakkauksessa on tämä merkki, tuotetta ei saa hävittää kotitalousjätteiden mukana. Tällöin hävitettävä laite on toimitettava sähkölaitteiden ja elektronisten laitteiden kierrätyspisteeseen. Hävitettävien laitteiden erillinen käsittely ja kierrätys auttavat säästämään luonnonvaroja ja varmistamaan, että laite kierrätetään tavalla, joka estää terveyshaitat ja suojelee luontoa.

  • Page 240: Hungarian Notice, Italian Notice, Latvian Notice, Lithuanian Notice

    Hungarian notice Italian notice Smaltimento delle apparecchiature da parte di privati nel territorio dell’Unione Europea Questo simbolo presente sul prodotto o sulla sua confezione indica che il prodotto non può essere smaltito insieme ai rifiuti domestici. È responsabilità dell'utente smaltire le apparecchiature consegnandole presso un punto di raccolta designato al riciclo e allo smaltimento di apparecchiature elettriche ed elettroniche.

  • Page 241: Polish Notice, Portuguese Notice, Slovakian Notice

    Polish notice Portuguese notice Descarte de Lixo Elétrico N/A Comunidade Européia Este símbolo encontrado no produto ou N/A embalagem indica que o produto não deve ser descartado no lixo doméstico comum. É responsabilidade do cliente descartar o material usado (lixo elétrico), encaminhando-o para um ponto de coleta para reciclagem.

  • Page 242: Slovenian Notice, Spanish Notice, Swedish 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. Es responsabilidad del usuario eliminar los residuos de este tipo depositándolos en un "punto limpio"...

  • Page 243: F Saving And Restoring The Mpx200 Configuration, Saving The Mpx200 Configuration

    F Saving and restoring the MPX200 configuration The MPX200 configuration information is saved as a .bin or .tgz file, depending on the method used to restore the MPX200 persistent data. The MPX200 configuration information is saved and restored using the MPX200 CLI commands or HP Command View EVA (see “ Saving or restoring the MPX200 configuration”...

  • Page 244: Restoring The Configuration Using The Mpx200 Cli

    Enter the following command: MPX200 (admin) #> fru save FRU save completed. Configuration File is HP_Storage- Works_MPX200_FRU.bin. Please use FTP to extract the file out from the System. MPX200 (admin) #> NOTE: The FRU save creates a bin file containing the router’s persistent data, configuration, and LUN mappings.

  • Page 245

    Enter the following command: MPX200 (admin) #> fru restore A list of attributes with formatting and current values will follow. Enter a new value or simply press the Enter key to accept the current value. If you wish to terminate this process before reaching the end of the list press 'q' or 'Q' and the Enter key to do so.

  • Page 246

    Saving and restoring the MPX200 configuration...

  • Page 247: G Offline Data Migration, Features Overview

    G Offline Data Migration Data Migration Service (DMS) is a block-level, offline, data migration service in the HP StorageWorks MPX200 Multifunction Router data transport device. Features overview The HP StorageWorks mpx Manager for Data Migration Services software is designed to simplify data migration jobs for minimum downtime, while providing protection against common user errors.

  • Page 248: Job Scheduling, Immediate Schedule, Delayed Schedule, Serial Schedule, Feature Details

    Feature details This section describes the features of the Data Migration Service. Because the current DMS is an offline-only service, it is assumed that when a data migration job for the specified LUN starts, applications (Microsoft Exchange, Oracle Applications, and other applications that are using the source LUNs for data storage) and server access to the LUN is blocked.

  • Page 249: Data Migration Job Groups, Array Properties

    Job priority 1 is highest and job priority 255 is lowest. After all the jobs are configured for serial execution, you must schedule this batch of serially-scheduled jobs. The batch can be started immediately or at a later time. The Serial Data Migration Jobs Options dialog box provides an easy way to start or schedule the batch.

  • Page 250: Protection, Data Migration Jobs, Data Migration Job Attributes

    other applications and servers using the same source array to continue to perform at an acceptable performance level. • Load Balancing: The MPX200 detects all available multiple active and passive paths to the LUN. Load balancing balances the load for migration jobs over multiple active paths, thus improving the migration rate.

  • Page 251: Data Migration Job States, Data Migration Job Commands, Logs

    Data migration job states Table 30 lists the possible data migration job states. Table 30 Data migration job states Job state Description Running Job is currently running. You can pause or stop a running job. Scheduled Job is waiting to be run. Completed Job is complete.

  • Page 252: Users, Supported Configurations, Fabric Configuration, Getting Started, Single And Dual Blade High-availability Setup

    Users The MPX200 supports two types of users: • Administrative user: To manage the MPX200, you must be in an administrative session. The default password for the administrator is config. • Data migration user (miguser): This user session is required to configure migration-related activities. The default password is migration.

  • Page 253: Supported Fibre Channel Fabrics, Supported Storage Arrays, Migration Between Dissimilar Vendor Sans

    Attachable Modular Storage (AMS) family Hitachi Data Systems (HDS) Workgroup Modular Storage (WMS) family HP StorageWorks Modular Storage Array (MSA) family Hewlett-Packard (HP) HP StorageWorks Enterprise Virtual Array (EVA) family System Storage DS4000 family System Storage DS5000 family MPX200 Multifunction Router...

  • Page 254: Best Practices, Migration Considerations, High Availability And Redundant Configurations

    Best practices This sections provides some “best practices” recommendations for DMS usage. Migration considerations Although this appendix focuses on the migration functionality available with the MPX200, it is important to note that a successful migration strategy includes a thorough understanding of the processes that should be considered before and after physically moving data.

  • Page 255: Choosing The Right Dms Options, General Precautions

    • To optimize performance, HP recommends that LUNs under migration are balanced across two controllers of a storage array. Choosing the right DMS options Follow these guidelines when choosing DMS options: • To get optimum MPX200 performance, schedule a maximum of eight jobs to run simultaneously. •...

  • Page 256: Installing The Mpx200 Mpx Manager For Data Migration Services, Download The Application

    • If the array-based license was used and the array will not be used in the next project, remove the license for this array. • Array-based license use requires the following precautions: • If you reconfigure a removed array, it may require a new array-based license. •...

  • Page 257: Hp Storageworks Mpx Manager For Data Migration Services For Windows

    A chmod may be necessary prior to execution. Follow the installation instructions on the screen and note the installation location. The default directory is /opt/Hewlett-Packard/mpxManager. HP StorageWorks mpx Manager for Data Migration Services for Mac OS X After downloading the application, see the previous step,...

  • Page 258: Hardware Setup, Software Setup, General Steps For Data Migration, Using Dms

    Hardware setup For information on installing your MPX200 Multifunction Router, see “Installing the MPX200” in the HP StorageWorks MPX200 Quick Start Instructions. To set up the hardware for DMS: To manage the MPX200, the MPX200 must be accessible over the network connection from the machine on which the mpx Manager is installed.

  • Page 259: Setting Array Properties, Setting Array Properties In The Gui

    Before beginning data migration, clear the migration logs (see “Viewing system and data migration logs” on page 281). If the router fails to discover arrays, use the target rescan option (see “Rescanning targets” on page 277). If you are using an array-based license, follow the License Array wizard to apply the license. Set the array properties: symbolic name (optional) and target type (Source or Destination) (see “Setting array properties”...

  • Page 260: Setting Array Properties: Target Type

    From the Target Type list, select Source, as shown in Figure Figure 92 Setting array properties: target type To save your changes, click Save. In the Security Check dialog box, enter the administrative password. (The default password is migration.) The mpx Manager displays a message indicating that the array properties have changed. Click OK to close the message box.

  • Page 261: Setting Array Properties In The Cli, Setting Array Bandwidth

    To set the array bandwidth: On the Information page of the selected array, click Array Bandwidth, and then click one of the following values: • Slow (50 MB/s) • Medium (200 MB/s) • Fast (1600 MB/s) • Throttle If you select Throttle, enter a value between 1 and 400 in the User Defined Bandwidth (MB/s) box.

  • Page 262: Creating A Data Migration Job Group, Setting Array Properties In The Gui

    Open a miguser session using the following command (the default password for miguser is migration.): miguser start -p migration To access the array properties, enter the following command: set array Select a target ID by entering its index number. At the prompts, modify the symbolic name, target type, or array bandwidth for the source and destination arrays.

  • Page 263: Creating A Data Migration Job Group In The Cli, Using The Data Migration Wizard

    In the Input dialog box, enter a group name that you want to assign to administer a set of data migration jobs, and then click OK. In the Security Check dialog box, enter the data migration user password (default is migration), and then click OK.

  • Page 264: Scheduling An Individual Data Migration Job In The Gui, Migration Schedule Options: Individual Job

    Select the scheduling mode as follows: In the top section of the Data Migration wizard, click Options. In the Migration Schedule Options dialog box, select either Schedule in batch mode or Schedule individual job, as shown in Figure Click OK. Figure 94 Migration Schedule Options: individual job Depending on your selection in the preceding step, continue with either Scheduling an individual...

  • Page 265: Create Data Migration Job: Individual Job

    Choose the appropriate Source and Destination LUN for the data migration job by dragging and dropping the LUNs from the right pane onto the Source LUN or Destination LUN for the data migration job in the left pane. Figure 95 shows an example.

  • Page 266: Scheduling An Individual Data Migration Job In The Cli, Data Migration Jobs: Individual

    In the Data Migration Jobs Options dialog box (see Figure 96), specify the job attributes as follows: Under Scheduling Type, select one of the following: • Click Start Now to start the job immediately. • Click Schedule for Later, and then enter a Start Time and Start Date. •...

  • Page 267

    Select a source array. (Every migration job is defined by a Source LUN and a Destination LUN. The CLI lists the source arrays that you have previously defined and prompts you to select one.) Select one LUN. (From the selected source array, the CLI lists the LUNs that have been exposed to the MPX200 for migration, and prompts you to select one LUN.# The CLI lists the destination arrays that you have previously defined, and prompts you to select one.

  • Page 268

    VPGROUP_3 VPGROUP_4 Please select a VPGroup for Source Lun ('q' to quit): 4 Vendor LUN Size( GB) Attributes ------ -------------- ---------- 5.00 5.00 5.00 5.00 5.00 Please select a LUN as a Source Lun ('q' to quit): 1 Index WWPN, PortId Symbolic Name Target Type -----...

  • Page 269: Scheduling Data Migration Jobs In Batch Mode, Migration Schedule Options: Batch Mode

    All attribute values for that have been changed will now be saved. Scheduling data migration jobs in batch mode Batch mode for data migration jobs is an mpx Manager GUI-only feature used to schedule multiple jobs having the same priority, I/O size, and group options. This option is particularly useful for migration jobs specified as Schedule for later and Serial Schedule Jobs on the Data Migration Jobs Options dialog box, where the jobs need to be classified under a specific group for better management.

  • Page 270: Create Data Migration Job: Batch

    Choose the appropriate source and destination LUN for the migration job by dragging and dropping the LUNs from the right pane onto the Source LUN or Destination LUN under DataMigration Job (New) in the left pane. The mpx Manager populates the Source LUN and Destination LUN attributes and creates a new DataMigration Job n (New) object below the first one.

  • Page 271: Starting Serial Scheduled Jobs, Serial Data Migration Jobs Options

    In the Data Migration Jobs Options dialog box (Figure 96 on page 266), specify the job attributes as follows: Under Scheduling Type, select one of the following: • Click Start Now to start the job immediately. • Click Schedule for Later, and then enter a Start Time and Start Date. •...

  • Page 272: Migrating Data To An Eva Array Configured For Iscsi

    The serial scheduled jobs will start according to your schedule. Migrating data to an EVA array configured for iSCSI The DMS is based upon the ability to assign and present data LUNs to the MPX200 FC ports by creating an EVA DM Fibre Channel host entity for the MPX200 FC ports. Both the source and destination arrays used for migration must have a DM Fibre Channel host entry for LUN presentation to the MPX200.

  • Page 273: Adding Luns To The Dms Iscsi Host Entry With Hp Command View Eva

    Figure 100 DMS iSCSI host entry in HP Command View EVA Adding LUNs to the DMS iSCSI host entry with HP Command View EVA This procedure follows the same method of creating and presenting LUNs for any iSCSI initiator connected to the EVA through the MPX200. 1.

  • Page 274: Virtual Disk Creation

    NOTE: If LUN presentation to the DMS iSCSI initiator is done from Advanced Settings at the time of virtual disk creation, HP Command View EVA will present the LUN to VPGroup 1 by default. Presenting the LUN after the virtual disk is created will allow the user to select the VPGroup. Figure 101 shows the creation of a virtual disk with HP Command View EVA.

  • Page 275: Viewing Data Migration Job Status In The Gui, Dms Virtual Disk Presentation

    IMPORTANT: Each iSCSI MPX host number under Available iSCSI Controller Paths corresponds to a VPGroup WWPN on the MPX200. For example, iSCSI MPX Host 04 maps to VPGroup 4. NOTE: If there are redundant iSCSI blades, the LUN will be presented to the DMS iSCSI initiator and VPGroup on each blade.

  • Page 276: Viewing Data Migration Jobs Status In The Cli, Active Data Migration Jobs

    In the right pane, select the Active Data Migration Jobs tab. The Active Data Migration Jobs page in the right pane shows a summarized view of all active jobs, as shown in Figure 103. Figure 103 Active Data Migration jobs To see a summarized view of all completed jobs, select the Completed Data Migration Jobs tab in the right pane.

  • Page 277: Rescanning Targets

    To see the configuration details for a specific job, enter the appropriate job ID. The following is an example of the use of the CLI to view the status of data migration jobs: MPX200 <1> (admin) (miguser) #> show migration Migration State Type ( 1=Running 2=Failed 3=Completed 4=All ) : 4 Owner Type...

  • Page 278: Viewing Job Details And Controlling Job Actions

    To rescan targets in the CLI: Open a miguser session using the following command: miguser start -p config To rescan for target ports, enter the following command: target rescan For example: MPX200 (admin) #> target rescan Scanning Target WWPN 00:00:02:00:00:00:00:00 Target Rescan done Scanning Target WWPN 00:00:01:00:00:00:00:00 Target Rescan done...

  • Page 279: Viewing Migration Job Details

    In the left pane, click the job by JobID. Details for the specified job are listed in the right pane, as shown in Figure 104. Figure 104 Viewing migration job details (Optional) From the migration job details pane, perform any of the following job control actions as needed: •...

  • Page 280: Viewing Job Details And Controlling Job Actions In The Cli

    Viewing job details and controlling job actions in the CLI You can also perform the preceding job control actions from the summary view. To do so, right-click a specific job, and then click the appropriate action on the shortcut menu. To view data migration job details in the CLI: Open a miguser session using the following command: miguser start -p migration...

  • Page 281: Viewing System And Data Migration Job Logs

    The CLI prompts you to select the appropriate job ID to perform the operation on the selected job. The following are examples of the migration job action commands: MPX200 (miguser) #> migration stop Job Id Type Status LUN ID LUN Size(MB) Src Symbolic Name ------ ----...

  • Page 282: Viewing Logs In The Gui, Mpx Log: System Log

    Viewing logs in the GUI This section provides procedures for viewing the system log and the data migration job log in the mpx Manager. To view the system log in the GUI: On the mpx Manager main window, click the View Logs button. In the Log Type dialog box, click System Logs.

  • Page 283

    To view the data migration job log in the GUI: On the mpx Manager main window, click the View Logs button. MPX200 Multifunction Router...

  • Page 284

    In the Log Type dialog box, click Data Migration Logs. Figure 106 shows an example of the mpx Log: Migration Log dialog box. Figure 106 mpx Log: Migration Log The migration job log contains the following columns of information: • SeqID: Sequential ID of log entries. •...

  • Page 285: Viewing Logs In The Cli

    Viewing logs in the CLI This section provides procedures for viewing the system log and the data migration job log in the CLI. To view the system log in the CLI Open a miguser session using the following command: miguser start -p migration To view all logs related to all migration jobs, enter the following command (see “show logs”...

  • Page 286: Using The Verify Migration Job Wizard, Starting The Verify Migration Job Wizard

    Thu Sep 10 13:15:49 2009 Seq id: 645 : Job Type: Migration : miguser :COMPLETED : JobId 0(Offline) of group Group 0 with priority 0 from Target HP HSV200-0 Lun 60:05:08:b4:00:07:59:a4:00:02:a0:00:00:7e:00:00(6) to Target HP HSV200-0 Lun 60:05:08:b4:00:07:59:a4:00:02:a0:00:00:83:00:00(7) with migration size 5.00 GB Thu Sep 10 13:33:16 2009 Seq id: 646 : Job Type: Migration : miguser :ACKNOWLEDGED : JobId 0(Offline) of group Group 0 with priority 0 from Target HP HSV200-0 Lun...

  • Page 287: Scheduling Verification Of Job Options, Verify Migration Job Wizard

    Scheduling verification of job options Follow these steps to schedule the verification of job options: In the Verify Migration Jobs wizard (Figure 107), click Options. Figure 107 Verify migration job wizard In the Verify Schedule Options dialog box, select the Scheduling Mode: either batch mode or individual job, and then click OK.

  • Page 288: Acknowledging A Data Migration Job, Verifying Jobs Options

    In the Verifying Jobs Options dialog box (Figure 108), specify the job attributes as follows: Under Scheduling Type, select one of the following: • Click Start Now to start the job immediately. • Click Schedule for Later, and then enter a Start Time and Start Date. •...

  • Page 289: Removing An Offline Array, Data Migration Licenses, Types Of Data Migration Licenses, Capacity-based Licenses

    On the Completed Data Migration Jobs page, scroll over a job that is specified as 100% in the % Completed column. On the shortcut menu, click Acknowledge Completed Data Migration. Removing an offline array You should remove arrays used in data migration because they are kept in persistent storage. To remove an offline array: In the left pane of the mpx Manager, select the Services tab.

  • Page 290: Installing A Data Migration License Key In The Gui, Features Page: License Information

    Installing a data migration license key in the GUI Follow this procedure to install a data migration license key in the mpx Manager for Data Migration Services GUI. In the mpx Manager, select the mpx Manager tab in the left pane. In the left pane, click mpx HP StorageWorks MPX200: <IP address>...

  • Page 291: Installing A Data Migration License Key In The Cli

    Enter a valid DM license key, and then click OK. The Add License dialog box (Figure 111) indicates the success of the license add operation. Figure 111 Add license dialog box Click OK to close the verification dialog box. Verify that the newly-added key appears in the list of keys on the Features page, as shown in Figure 109 on page 290.

  • Page 292: Applying An Array-based License To A Specific Array In The Gui

    Applying an array-based license to a specific array in the GUI If you have purchased array-based licenses and installed the licenses in the MPX200, follow these steps to license a specific array for data migration. For every array that is licensed, one license is consumed: In the left pane of the mpx Manager main window, select the mpx Manager tab.

  • Page 293: License Array Dialog Box

    In the License Array dialog box (Figure 112), select the array for which you want to apply the license, and then click OK. Figure 112 License Array dialog box The Information page for the selected array now shows the Array License as Licensed, as shown Figure 113.

  • Page 294: Applying An Array-based License To A Specific Array In The Cli

    Figure 113 Information page showing array is licensed Applying an array-based license to a specific array in the CLI If you have purchased array-based licenses and installed the licenses in the MPX200, follow these steps to license a specific array for data migration. For every array that is licensed, one license is consumed.

  • Page 295: Viewing Data Migration License Usage, Viewing Data Migration License Usage In The Gui

    3 20:70:00:c0:ff:d5:9a:05, 01-0f-ef HP MSA2012fc-3 Unknown Please select a Target Id from the list above ('q' to quit): 1 Symbolic Name (Max = 128 characters) [HP HSV210-1] Target Type (1=SrcTarget, 2=DstTarget, 3=Src+Dest Target) [3 ] 1 Bandwidth for Migration (0=Array Bandwidth, 1-400 MBps ) [0 ] Do you want to apply array license (yes/no) [No ]yes All attribute values for that have been changed will now be saved.

  • Page 296: Command Line Interface, User Accounts, User Sessions, Admin Session

    Open a miguser session using the following command: miguser start -p migration To view the status of migration license consumed and available on the current system, enter the following command (see “show migration_usage” on page 336): show migration_usage The following example shows the show migration_usage command. MPX200 (miguser) #>...

  • Page 297: Miguser Session, Commands

    Miguser session The miguser is the migration administrator session that has privileges to run CLI commands related to the migration operations. The default password for starting the miguser session is migration. You can start and stop a miguser session using the following commands: miguser [start/begin] miguser [end/cancel/stop] For example:...

  • Page 298

    “show fc” on page 324 “show migration” on page 325 “show array” on page 326 “show luninfo” on page 329 “show migration_luninfo” on page 330 “show migration_params” on page 332 “show mgmt” on page 333 “show memory” on page 334 “show properties”...

  • Page 299

    set system Displays or changes the system attributes of an MPX200 blade. Session: admin 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 300

    set features Saves and activates the array's data migration license key. Session: admin Example: MPX200 <1> (admin) #> set features 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 301

    set fc Sets the port status and programmed connection status Session: admin Example: MPX200 (admin) #> set fc A list of attributes with formatting and current values will follow. Enter a new value or simply press the ENTER key to accept the current value. If you wish to terminate this process before reaching the end of the list press 'q' or 'Q' and the ENTER key to do so.

  • Page 302: Set Array

    set array Sets the target type of an array to make it behave as either a source, a destination, or both. Session: miguser Example: MPX200 <1> (admin)(miguser) #> set array 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 303: Set Vpgroups

    set VPGroups Enables or disables the virtual port groups (VP groups), and specifies names to each VP group. VpGroup 1 cannot be disabled; however, you can change its name. Session: admin Example: MPX200 <1> (admin) (miguser) #> set vpgroups The following wizard will query for attributes before persisting and activating the updated mapping in the system configuration.

  • Page 304: Migration_group Add

    migration_group add Creates a data migration job group that you can use to combine migration jobs to simplify scheduling and monitoring data migration processes. Session: miguser Example: MPX200 (miguser) #> migration_group add Please Enter Group Name that you want to create (Min = 4 Max = 64 chars) DM_1 Successfully created Group DM_1 Offline Data Migration...

  • Page 305: Migration_group Remove

    migration_group remove Deletes or removes an existing data migration group that will not be used in any of the new data migration jobs that need to be scheduled. You may need to delete groups because there is limit of eight groups into which the MPX200 can classify data migration jobs. Session: miguser Example: MPX200 (miguser) #>...

  • Page 306: Migration_group Edit

    migration_group edit Renames an already existing data migration job group. Use this command to correct spelling mistakes that might have occurred when you typed the name while creating the data migration job group. Session: miguser Example: MPX200 (miguser) #> migration_group edit Index Group Name ----- ---------- Group 0...

  • Page 307: Migration Add

    migration add Schedules a data migration job. You can enter a name for the data migration job and associate it with a job group. Scheduling options include: immediately, at a pre-defined later time, or by serial scheduling. Serial scheduling requires that you assign a priority to the job. The priority is used to schedule it before (lower priority value) or after (higher priority value) a specific job in the serial schedule queue of data migration jobs.

  • Page 308

    VPGROUP_2 VPGROUP_3 VPGROUP_4 Please select a VPGroup for Destination Lun ('q' to quit): 1 Vendor LUN Size( GB) Attributes ------ -------------- ---------- 10.00 10.00 20.00 20.00 10.00 5.00 5.00 5.00 Please select a LUN as a Destination Lun('q' to quit): 1 I/O Size (0=32KB, 1=64KB, 2=128KB, 3=512KB, 4=1MB) [64KB ] Please Enter a Job Description (Max = 64 characters) default name [ DGC RAID-2:VPG4:001 to HP HSV210-3:VPG1:001 ]...

  • Page 309: Migration Rm

    migration rm Deletes a data migration job. Session: miguser Example: MPX200 <1> (admin)(miguser) #> migration rm Type Status Job Description ---- ----------------------- ------------------------------------ Offline Running ( 5%) DGC RAID-2:VPG4:001 to HP HSV210-3 Please select a Job Id from the list above ('q' to quit): 0 Do you wish to continue with the operation(yes/no)? [No] yes All attribute values for that have been changed will now be saved.

  • Page 310: Migration Stop

    migration stop Stops running the data migration job. Use this command if you want to restart the migration process later due to some technical or business need. You can also use it on already-scheduled jobs to change the scheduling time. Session: miguser Example: MPX200 <1>...

  • Page 311: Migration Start

    migration start Restarts a previously stopped migration job. The migration process starts over from the first block. Session: miguser Example: MPX200 <1> (admin)(miguser) #> migration start Type Status Job Description ---- ------------------------ ------------------------------------ Offline Stopped HP HSV200-0:LUN1 to DGC RAID-1:LUN0 Please select a Job Id from the list above ('q' to quit): 0 Start Time for JobId 0:(1=Now, 2=Delayed, 3=JobSerialScheduling) [Now ] 2 Please specify a Date &...

  • Page 312: Migration Pause

    migration pause Pauses a running migration job. This command freezes the migration process. You can later resume the job from the block where the migration was paused. Session: miguser Example: MPX200 <1> (admin)(miguser) #> migration pause Type Status Job Description ---- ------------------------ ------------------------------------...

  • Page 313: Migration Resume

    migration resume Resumes a paused data migration job. The job is resumed from the block where the data migration was paused. Session: miguser Example: MPX200 <1> (admin)(miguser) #> migration resume Type Status Job Description ---- ------------------------ ------------------------------------ Offline Paused ( 80%) HP HSV200-0:LUN1 to DGC RAID-1:LUN0 Please select a Job Id from the list above ('q' to quit): 0 All attribute values for that have been changed will now be saved.

  • Page 314: Migration Acknowledge

    migration acknowledge Acknowledges a completed data migration job. After running this command, the migration job is permanently deleted from the database. Session: miguser Example: MPX200 (miguser) #> migration acknowledge Type Status Job Description ---- ------------------------ ------------------------------------ Offline Completed (100%) HP HSV200-0:LUN1 to DGC RAID-1:LUN0 Please select a Job Id from the list above ('q' to quit): 0 All attribute values for that have been changed will now be saved.

  • Page 315: Start_serial_jobs

    start_serial_jobs Starts one or more serial scheduled jobs that have been configured but not yet started. Session: miguser Example: MPX200 (miguser) #> start_serial_jobs Serial Job Start Time (1=Now, 2=Delayed) [Now ] 2 Please specify a Date & Time (in <MMddhhmmCCYY format) when the serial schduled jobs should start.

  • Page 316: Compare_luns Add

    compare_luns add Schedules a standalone LUN compare job. You can name the job and associate it with a job group. Scheduling options include: immediately, at a pre-defined later time, or by serial scheduling. Serial scheduling requires that you assign a priority to the job, which will be used to schedule it before (lower priority value) or after (higher priority value) a specific job in the serial schedule queue.

  • Page 317

    VPGROUP_4 Please select a VPGroup for Destination Lun ('q' to quit): 1 Vendor LUN Size( GB) Attributes ------ -------------- ---------- 10.00 SRC LUN 10.00 20.00 20.00 10.00 5.00 5.00 5.00 Please select a LUN as a Destination Lun('q' to quit): 2 I/O Size (0=32KB, 1=64KB, 2=128KB, 3=512KB, 4=1MB) [64KB ] Please Enter a Job Description (Max = 64 characters) default name [ HP HSV210-3:VPG1:001 to HP HSV210-3:VPG1:002 ]...

  • Page 318: Compare_luns Rm

    compare_luns rm Deletes a LUN compare job. Session: miguser Example: MPX200 (miguser) #> compare_luns rm Type Status Job Description ---- ------------------------ ------------------------------------- Offline Verify Running HP HSV200-0:0001 to DGC RAID-1:0000 Please select a Job Id from the list above ('q' to quit): 0 Do you wish to continue with the operation(yes/no)? [No] yes All attribute values for that have been changed will now be saved.

  • Page 319: Compare_luns Stop

    compare_luns stop Stops running a LUN compare job. Use this command if you need to restart the compare process due to some technical or business need. Use this command also on already-configured scheduled jobs to change the scheduling time. Session: miguser Example: MPX200 (miguser) #>...

  • Page 320: Compare_luns Start

    compare_luns start Restarts a stopped LUN compare job. The compare process restarts from the first block. Session: miguser Example: MPX200 (miguser) #> compare_luns start Type Status Job Description ---- ------------------------ ------------------------------------ Offline Stopped HP HSV200-0:0001 to DGC RAID-1:0000 Please select a Job Id from the list above ('q' to quit): 0 Start Time for JobId 0:(1=Now, 2=Delayed, 3=JobSerialScheduling) [Now ] 2 Please specify a Date &...

  • Page 321: Compare_luns Pause

    compare_luns pause Interrupts a LUN compare job. This command freezes the compare process. You can later resume the job from the block where the compare was paused. Session: miguser Example: MPX200 (miguser) #> compare_luns pause Type Status Job Description ---- ------------------------ ------------------------------------ Offline...

  • Page 322

    compare_luns resume Resumes a paused LUN compare job. The job resumes from the block where the compare was paused. Session: miguser Example: MPX200 (miguser) #> compare_luns resume Type Status Job Description ---- ------------------------ ------------------------------------ Offline Verify Paused HP HSV200-0:0001 to DGC RAID-1:0000 Please select a Job Id from the list above ('q' to quit): 0 All attribute values for that have been changed will now be saved.

  • Page 323: Compare_luns Acknowledge

    compare_luns acknowledge Acknowledges a LUN compare job. After you run this command, the LUN compare job is permanently deleted from the database. Session: miguser Example: MPX200 (miguser) #> compare_luns acknowledge Job Type Status Job Description --- ---- ------------------------ ------------------------------------ Offline Completed HP HSV200-0:0001 to DGC RAID-1:0000 Please select a Job Id from the list above ('q' to quit): 0 All attribute values for that have been changed will now be saved.

  • Page 324

    show fc Displays the port status and link status of each Fibre Channel port, along with the port name and node name. Session: admin Example: MPX200 <1> (admin) #> show fc FC Port Information --------------------- FC Port Port Status Enabled Port Mode Link Status Current Link Rate...

  • Page 325: Show Migration

    show migration Displays a summarized status of either all migration jobs or those having a specific state. It also lists the configuration details of the selected job. Session: miguser Example: MPX200 <1> (admin) (miguser) #> show migration Migration State Type ( 1=Running 2=Failed 3=Completed 4=All ) : 4 Owner Type Status...

  • Page 326: Show Array

    show array Displays the status of array objects identified by the DMS. Session: miguser Example: MPX200 (miguser) #> show array Array Information ----------------- Symbolic Name HP HSV200-0 State Online Vendor ID Product ID HSV200 Target Type Src+Dest WWPN 50:00:1f:e1:50:0a:e1:4c Port ID 01-2b-00 State Online...

  • Page 327

    Load Balancing Enabled Array License Not Applied MPX200 Multifunction Router...

  • Page 328

    show luninfo Displays the status of LUN objects indenified by the DMS. Session: miguser Notes: The show luninfo command displays all the LUNs that are seen by the MPX200 and their size and path information. To view a list of LUNs without the details, run the show luns command instead.

  • Page 329

    show luninfo Displays the status of LUN objects indenified by the DMS. Session: miguser Example: MPX200 (miguser) #> show luninfo MPX200 <1> (admin) #> show luninfo Index (WWNN,WWPN/iSCSI Name) ----- ---------------------- 20:78:00:c0:ff:d5:9a:05,20:78:00:c0:ff:d5:9a:05 20:78:00:c0:ff:d5:9a:05,21:78:00:c0:ff:d5:9a:05 50:06:01:60:cb:a0:35:de,50:06:01:60:4b:a0:35:de 50:00:1f:e1:50:0a:e1:40,50:00:1f:e1:50:0a:e1:49 50:00:1f:e1:50:0a:37:10,50:00:1f:e1:50:0a:37:18 50:00:1f:e1:50:0a:37:10,50:00:1f:e1:50:0a:37:1b Please select a Target from the list above ('q' to quit): 5 Index (LUN/VpGroup) -----...

  • Page 330: Show Migration_luninfo

    show migration_luninfo Provides the current status and path information for any array LUN. Use this command to check the usability of a path in failover scenarios. The paths specified as passive are not used by data migration jobs if the current path fails. The passive path is capable of reading only the LUN size, vendor, and product information, but cannot perform any I/O operation.

  • Page 331

    Controller Id WWPN, PortId Path Status ------------- --------------------------------- ----------- 20:78:00:c0:ff:d5:92:e5, 02-04-00 Current Optimized MPX200 Multifunction Router...

  • Page 332: Show Migration_params

    show migration_params Displays the current time and start time of a serial scheduled job. Session: miguser Example: MPX200 (miguser) #> show migration_params Current Time : Mon Dec 15 08:36:12 2009 Serial Scheduled Start Time : Mon Dec 15 08:37:00 2009 Offline Data Migration...

  • Page 333

    show mgmt Displays management port information, including the IP address, subnet mask, and gateway. Session: miguser Example: MPX200 (miguser) #> show mgmt Management Port Information ----------------------------- IPv4 Interface Enabled IPv4 Mode Static IPv4 IP Address 172.35.14.53 IPv4 Subnet Mask 255.255.254.0 IPv4 Gateway 172.35.14.1 IPv6 Interface...

  • Page 334: Show Memory

    show memory Displays the free and total memory. Session: miguser Example: MPX200 (miguser) #> show memory Memory Units Free/Total -------------- ---------- Physical 309MB/1002MB Buffer Pool 9433/10496 Nic Buffer Pool 40960/40960 Process Blocks 14336/14336 Request Blocks 14336/14336 Event Blocks 8182/8192 Control Blocks 2048/2048 Client Req Blocks 14336/14336...

  • Page 335

    show properties Displays the CLI properties. Session: miguser Example: MPX200 (miguser) #> show properties CLI Properties ---------------- Inactivty Timer 15 minutes Prompt String MPX200 MPX200 Multifunction Router...

  • Page 336: Show Migration_usage

    show migration_usage Displays the CLI properties. Session: miguser Example: MPX200 (miguser) #> show migration_usage Migration License Usage ----------------------- Total capacity licensed 10240.00 GB Migration license consumed 1.00 GB License consumed by active jobs 10.00 GB Total capacity available 10229.00 GB Array Based Licenses -------------------- Array based licences issued...

  • Page 337

    show perf Displays the performance (in bytes) of the active job. Session: miguser Example: MPX200 (miguser) #> 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...

  • Page 338: Show Perf Byte

    show perf byte Displays the active job performance in bytes. Session: miguser Example: MPX200 (miguser) #> 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) -------------------------------- 189M 189M...

  • Page 339

    show features Displays the feature key information. Session: miguser Example: MPX200 <1> (admin) (miguser) #> show features License Information ------------------- FCIP 1Gig Not Licensed DM Capacity Licensed DM Array Licensed Feature Key Information ------------------------- 806400-LCPJRHKUYZ9NS-DM-100TB (DATA-MIGRATION CAPACITY 100TB) Chassis Licensed 0851E00035 Date Applied Tue Jan 6 01:28:57 2009...

  • Page 340: Show Migration_logs

    show migration_logs Displays the data migration logs and the operation performed on it. Session: miguser Example: MPX200 (admin) (miguser) #> show migration_logs 6 Tue Sep 8 15:28:00 2009 Seq id: 640 : Job Type: Migration : miguser :COMPLETED : JobId 1(Offline) of group Group 0 with priority 0 from Target HP HSV200-0 Lun 60:05:08:b4:00:07:59:a4:00:02:a0:00:03:ba:00:00(9) to Target HP HSV200-0 Lun 60:05:08:b4:00:07:59:a4:00:02:a0:00:00:83:00:00(7) with migration size 1.00 GB...

  • Page 341: Show Logs

    show logs Displays log BridgeApp event information. Session: miguser Example: MPX200 <1> (admin) (miguser) #> show logs 10 10/09/2009 11:11:04 BridgeApp 3 QLFC_Login: Port Name 500601604ba035de 10/09/2009 11:15:29 QLFC 3 #0: QLIsrEventHandler: RSCN update (8015) rscnInfo:0x2080000 VpIndex:0x0 10/09/2009 11:15:29 QLFC 3 #0: QLIsrEventHandler: RSCN update (8015) rscnInfo:0x2080000 VpIndex:0x1 10/09/2009 11:15:29 QLFC 3 #0: QLIsrEventHandler: RSCN update (8015) rscnInfo:0x2080000 VpIndex:0x2...

  • Page 342: Show Luns

    show luns Displays all the LUNs and their detailed information. Session: miguser Example: MPX200 <1> (admin) (miguser) #> show luns Target(WWPN) VpGroup ============ ======= 20:78:00:c0:ff:d5:9a:05 VPGROUP_1 VPGROUP_1 VPGROUP_1 VPGROUP_1 VPGROUP_1 VPGROUP_1 VPGROUP_1 VPGROUP_1 VPGROUP_1 VPGROUP_1 VPGROUP_1 VPGROUP_1 VPGROUP_1 VPGROUP_1 VPGROUP_1 21:78:00:c0:ff:d5:9a:05 VPGROUP_1 VPGROUP_1...

  • Page 343

    VPGROUP_1 VPGROUP_1 VPGROUP_1 VPGROUP_1 VPGROUP_1 VPGROUP_1 50:00:1f:e1:50:0a:37:1b VPGROUP_1 VPGROUP_1 VPGROUP_1 VPGROUP_1 VPGROUP_1 VPGROUP_1 VPGROUP_1 VPGROUP_1 VPGROUP_1 MPX200 Multifunction Router...

  • Page 344

    show targets Displays the WWPN and WWNN for all targets that are zoned in with the router ports. If one or more data LUNs are exposed to the router ports from the target, no information is shown. Session: miguser Example: MPX200 (miguser) #>...

  • Page 345: Show Vpgroups

    show vpgroups Lists the status and WWPN for each virtual port group (VP group). The router’s Fibre Channel ports can present four virtual ports (if enabled) to zone with Fibre Channel targets and allow the target to expose more LUNs to the router. The router provides the VP group by combining virtual port entities from each Fibre Channel port.

  • Page 346: Target Rescan

    target rescan Scans the target ports to see whether one or more data LUNs are exposed to the router ports from the target. This command causes the router to create an array entity for the target ports through which the router is able to see data LUNs. The router deletes those ports from show targets output (see “show targets”...

  • Page 347: Save Capture

    save capture Captures the system log that you can use to detect and troubleshoot problems when the MPX200 is exhibiting erroneous behavior. This command generates a System_Capture.tar.gz file that provides a detailed analysis. Session: admin Example: MPX200 (admin) #> save capture Debug capture completed.

  • Page 348: Array Rm

    array rm Removes details associated with an offline array from persistence, and removes the license information associated with the array. Session: miguser Example: MPX200 (miguser) #> array 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 349: Array_licensed_port Rm

    array_licensed_port rm Removes licensed offline array ports. Use this command to remove the ports (shown by the show migration_usage command) for which you have removed an array without also removing the array’s license. Session: miguser Example: MPX200 (admin) (miguser) #> array_licensed_port rm 01.

  • Page 350: Readjust_priority

    readjust_priority Modifies the priority of serial scheduled jobs. Use this feature if you have more than 256 jobs that must be executed sequentially. This operation is allowed only if the high priority jobs are completed, and there is room for shifting the priority values on already configured jobs. This reduces the priority value of the last job from 256 by the value of the priority of the currently running serial job, and makes room to configure more serial jobs.

  • Page 351: Show Compare_luns, Performance Factors, Performance

    show compare_luns Summarizes the status of verify jobs either with a specific state or all jobs. It also lists the configuration details of the selected job. Session: miguser Example: MPX200 <1> (miguser) #> show compare_luns Compare State Type ( 1=Running 2=Failed 3=Completed 4=All ) : 4 Owner Type Status...

  • Page 352: Maximizing Performance, Optimal Configuration And Zoning, Msa2012fc Array Behavior, Using The Hp Msa2012fc Storage Array

    • I/O traffic serviced by the array from other applications active during data migration • Fibre Channel link speed • RAID configuration of LUNs Maximizing performance Here are some suggestions for maximizing performance: • Use the Array Bandwidth feature (see “Setting array properties”...

  • Page 353: Using Array-based Licenses For Msa2012fc Array

    Using array-based licenses for MSA2012fc array Each controller of the MSA2012fc array presents different LUNs to the MPX200 ports and hence appears as two separate arrays. Using array-based licenses to migrate LUNs owned by both controllers requires two array licenses. If, however, all LUNs requiring migration are owned by a single controller, one array license should suffice.

  • Page 354: Reconfiguring Luns On A Storage Array, Removing An Array After Completing Data Migration Jobs, Restrictions

    Restrictions This section details the restrictions that apply to DMS for reconfiguring LUNs on a storage array and provides the steps for removing an array after completing data migration jobs. Reconfiguring LUNs on a storage array Reconfigure a LUN ID following these guidelines: •...

  • Page 355

    The migration add command fails to start a Verify that the arrays are still visible and online. job. Array bandwidth is a source-only feature. Make sure that Setting the array bandwidth does not cause any the bandwidth setting has been configured on the array change in the data transfer rate in show perf that contains the source LUN.

  • Page 356

    Verify that the MPX200 port is registered with the storage system through the same storage controller port through which it is trying to access the LUNs. If the MPX200 ports are registered with SPA-0 port, and SPA-1 port is zoned with the MPX200 ports on the switch, the MPX200 will not see any of the assigned LUNs.

  • Page 357: Index

    Index Symbols save command, additional equipment, required, admin command, agent shutdown notification, agent startup notification, Apple Mac storage setup, Apple Mac OS XiSCSI initiator, Apple Mac iSCSI initiator, authority requirements, battery replacement notice, beacon command, blade command, Cautions file systems, chassis diagnostics, clear command, CLI usage,...

  • Page 358: Table Of Contents

    commands target, admin, traceroute, beacon, commandslunmask, blade, commandsset alias, clear, commandsset chap, date, commandsset chassis, exit, commandsset features, fciproute, configuration fru, dual-blade multi-EVA, help, dual-blade fabric-attached, history, maximums, image, modifying, initiator, single-blade fabric-attached, logout, single-blade multi-EVA, ping, configuration options, quit, configuring reboot, restoring,...

  • Page 359

    Linux installing Red Hat, generic notification, iSCSI initiator, guest account, understanding, iSCSI initiator setup for, presenting EVA storage for, Linux initiator device names, hardware device, locating, target bindings, help command, load balancing, history command, log data, host system, preparing, log messages, HP Command View EVA logging on, troubleshooting,...

  • Page 360

    show chassis command, show command, pages show fc command, MPIO Properties, show fciproutes command, Select Features, show features command, part numbers and options, show initiators command, ping command, show initiators_lunmask, power control module, show iscsi command, product show isns command, providing feedback, show logs command, show luninfo command,...

  • Page 361

    tabsTarget Settings, Taiwan battery recycling notice, target login, target bindings, target command, target device discovery, target parameter, modify, target presentation, Target Settings tab, traceroute command, VMwareiSCSI initiator, VP group notification, VP group table, websites HP Subscriber's choice for business, product manuals, Windows Server 2003 iSCSI initiator, Windows Server 2003...

Comments to this Manuals

Symbols: 0
Latest comments: