Page of 408
Download Table of ContentsContents Print This PagePrint Bookmark

HP StorageWorks 6400/8400 - Enterprise Virtual Array User Manual

Hp storageworks mpx200 multifunction router user guide (5697-0202, february 2010).
Hide thumbs
   
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 101 102 103 104 105 106 107 108 109 110 111 112 113 114 115 116 117 118 119 120 121 122 123 124 125 126 127 128 129 130 131 132 133 134 135 136 137 138 139 140 141 142 143 144 145 146 147 148 149 150 151 152 153 154 155 156 157 158 159 160 161 162 163 164 165 166 167 168 169 170 171 172 173 174 175 176 177 178 179 180 181 182 183 184 185 186 187 188 189 190 191 192 193 194 195 196 197 198 199 200 201 202 203 204 205 206 207 208 209 210 211 212 213 214 215 216 217 218 219 220 221 222 223 224 225 226 227 228 229 230 231 232 233 234 235 236 237 238 239 240 241 242 243 244 245 246 247 248 249 250 251 252 253 254 255 256 257 258 259 260 261 262 263 264 265 266 267 268 269 270 271 272 273 274 275 276 277 278 279 280 281 282 283 284 285 286 287 288 289 290 291 292 293 294 295 296 297 298 299 300 301 302 303 304 305 306 307 308 309 310 311 312 313 314 315 316 317 318 319 320 321 322 323 324 325 326 327 328 329 330 331 332 333 334 335 336 337 338 339 340 341 342 343 344 345 346 347 348 349 350 351 352 353 354 355 356 357 358 359 360 361 362 363 364 365 366 367 368 369 370 371 372 373 374 375 376 377 378 379 380 381 382 383 384 385 386 387 388 389 390 391 392 393 394 395 396 397 398 399 400 401 402 403 404 405 406 407 408

Advertisement

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, FCIP, and data migration. 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-0202
Fifth edition: February 2010

Advertisement

   Also See for HP StorageWorks 6400/8400 - Enterprise Virtual Array

   Related Manuals for HP StorageWorks 6400/8400 - Enterprise Virtual Array

   Summary of Contents for HP StorageWorks 6400/8400 - 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, FCIP, and data migration. 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 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 ..........21 MPX200 features ........................21 MPX200 configuration options ....................23 Planning the MPX200 installation ....................27 Total number of initiators ..................... 28 Number of paths required per initiator .................. 28 Use of iSNS ........................28 Use of iSCSI ports ......................

  • Page 4: Table Of Contents

    Supported IP network adapters ....................55 IP network requirements ......................55 Setting up the iSCSI initiator ....................... 55 Windows Server iSCSI initiator ................... 55 Multipathing ........................61 Installing the MPIO feature for Windows Server 2008 ............. 62 Installing the MPIO feature for Windows Server 2003 ............. 64 Microsoft Windows Server 2003 Scalable Networking Pack ............

  • Page 5: Table Of Contents

    MPX200 FCIP product description ..................... 113 Redundant FCIP network structure example ................. 114 Using FCIP to encapsulate FC packets ..................114 FCIP Impact on existing iSCSI configurations ................114 FCIP and iSCSI performance ....................116 MPX200 iSCSI/FCIP configurations ................... 116 HP Continuous Access EVA 3 site configurations ..............

  • Page 6: Table Of Contents

    Users ..........................144 Getting started ........................144 Supported configurations ....................144 Fabric configuration ....................144 Supported Fibre Channel fabrics .................. 145 Supported storage arrays .................... 145 Best practices ........................146 Migration considerations .................... 146 High availability and redundant configurations .............. 146 Choosing the right DMS options ..................

  • Page 7: Table Of Contents

    Installing a data migration license key ................. 181 Installing a data migration license key in the GUI ............182 Installing a data migration license key in the CLI ............183 Applying an array-based license to a specific array .............. 183 Applying an array-based license to a specific array in the GUI ........

  • Page 8: Table Of Contents

    show vpgroups ......................236 target rescan ......................237 save capture ......................238 array rm ........................239 array_licensed_port rm ....................240 readjust_priority ......................241 show compare_luns ....................242 Performance ........................... 242 Performance factors ......................242 Maximizing performance ....................243 Optimal configuration and zoning ..................243 Using the HP MSA2012fc Storage Array ...................

  • Page 9: Table Of Contents

    A Command reference ............... 263 Command syntax ........................263 Command line completion ....................263 Authority requirements ...................... 263 Commands ..........................264 Admin ..........................264 Beacon ........................... 265 Blade ..........................265 Clear ..........................265 Date ..........................266 Exit ..........................266 Fciproute ......................... 267 FRU ..........................

  • Page 10: Table Of Contents

    Show NTP ........................296 Show perf ........................297 Show presented targets ..................... 298 Show properties ....................... 299 Show SNMP ........................299 Show stats ........................300 Show system ........................302 Show targets ........................303 Show VPGroups ....................... 303 Shutdown ........................304 Target ..........................

  • Page 11: Table Of Contents

    Laser safety warning ....................356 Certification and classification information ..............356 Laser product label ....................356 International notices and statements ..................357 Canadian notice (avis Canadien) ..................357 Class A equipment ..................... 357 BSMI notice ........................357 Japanese notice ....................... 357 Korean notices .........................

  • Page 12: Table Of Contents

    Minimizing downtime ....................... 374 Before application downtime ..................374 During application downtime ..................374 Validating integrity of the data ..................375 Operating systems dependencies ....................375 Windows operating system ....................375 UNIX operating system (HP_UX, Linux, AIX, Solaris) .............. 375 Checklist examples .........................

  • Page 13: Table Of Contents

    Figures MPX200 single-blade fabric-attached configuration ............. 24 MPX200 dual-blade fabric-attached configuration ............24 MPX200 single-blade multi-EVA configuration ............. 25 MPX200 dual-blade multi-EVA configuration ............... 25 MPX200 dual-blade direct connect to one EVA configuration ........26 MPX200 single-blade direct connect to one EVA configuration ........26 MPX200 dual-blade direct connect to two EVA configuration ........

  • Page 14: Table Of Contents

    Host details ......................59 Targets tab ......................60 Select Features page ....................62 MPIO MPIO Properties page before reboot ..............63 MPIO Properties page after reboot ................63 Software update installation wizard ................64 Discover targets ...................... 66 Add static IP address ....................66 Discovered targets list ....................

  • Page 15: Table Of Contents

    MPX200 FCIP with B-series Integrated Routing ............117 MPX200 high-availability configuration with one or two long-distance links ....118 MPX200 high-availability configuration with fully-redundant long-distance links ..... 118 MPX200 configuration with remote IP Distance gateway (mpx110) ......118 MPX200 highly-redundant configuration with one or two long-distance lists ....119 MPX200 highly redundant pairs of gateways with fully-redundant long-distance links ..

  • Page 16: Table Of Contents

    Features page: License Information ................182 New License Key dialog box .................. 182 Add license dialog box ..................183 License Array dialog box ..................185 Information page showing array is licensed .............. 186 Data Migration Info ....................187 MPX200 chassis diagnostic LEDs ................249 Normal blink pattern .....................

  • Page 17: Table Of Contents

    Adding a second host port ..................395 Presenting Vdisks ....................396 Viewing enterprise storage ..................397 Registering Initiator Record ..................398 Creating storage group ..................399 Adding DM-Host to storage group ................400 Adding LUNs to DM-Host ..................401 MPX200 Multifunction Router...

  • Page 18: Table Of Contents

    Tables MPX200 part numbers and options ................21 MPX200 blade configurations .................. 27 MPX200 supported configuration maximums .............. 28 Supported MPX200 maximums ................. 50 Support for EVA storage system software with MPX200 iSCSI ........52 Operating system and multipath software support ............52 Supported IP network adapters .................

  • Page 19: Table Of Contents

    SNMP trap configuration parameters ............... 312 MPX200 log messages ..................331 DM log messages ....................349 FCIP log messages ....................352 Storage array information ..................371 Server information ....................371 Physical device information ..................372 LUN ID mappings ....................372 Pre-migration Fibre Channel zoning information ............

  • Page 21: 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 22

    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 23: 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 24: 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 25: 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 Figure Figure 6, and...

  • Page 26: Mpx200 Dual-blade Direct Connect To One Eva Configuration

    IP network management (WAN/LAN) MPX200 blade 2 MPX200 blade 1 MGMT MGMT HP StorageWorks HP StorageWorks MPX200 MPX200 1 GbE Blade 1 GbE Blade MPX200 Multifunction Router MPX200 Multifunction Router IOIOI IOIOI MGMT MGMT iSCSI IP network iSCSI data (LAN/VLAN) EVA storage system 26639a Figure 5 MPX200 dual-blade direct connect to one EVA configuration...

  • Page 27: Planning The Mpx200 Installation, Mpx200 Blade Configurations

    Planning the MPX200 installation Before installing the MPX200, it is important to define the requirements for iSCSI server connectivity and MPX200 multi-function usage. You should consider present and future needs as they relate to the following MPX200 configuration attributes: • Simultaneous operation You can configure the MPX200 chassis with a single blade or dual blades to run up to two oper- ations simultaneously per blade as shown in...

  • Page 28: Total Number Of Initiators, Number Of Paths Required Per Initiator, Use Of Iscsi Ports

    Table 3 MPX200 supported configuration maximums Configuration parameter Per port Per blade Per chassis (2 blades iSCSI connections, 1-GbE model 1,024 2,048 iSCSI connections, 10-GbE model 2,048 4,096 2,048 Initiators, 1-GbE model Initiators, 10-GbE model LUNs, 1-GbE model 4,096 4,096 LUNs, 10-GbE model 4,096 4,096...

  • Page 29: Gbe Initiators, Chap Security

    Because iSCSI and data migration traffic can share the same FC ports, it is prudent to understand how each function effects the other during I/O operation. The use of bandwidth throttling for data migration or MPIO to control the amount and path I/O follows. 10-GbE initiators HP recommends that you map servers with 10-GbE NICs for login to the 10-GbE ports on the MPX200.

  • Page 30

    MPX200 Multifunction Router overview...

  • Page 31: 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 8 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 32: 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 33: 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 34: 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 12).

  • Page 35: 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 13). Repeat for the right blade. NOTE: The right blade requires the power cord to extend approximately 12 in.

  • Page 36: 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 37: 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 38: Fibre Channel Switch-based Zoning, Open Zone Configuration

    Figure 15 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 39: Hp Command View Eva Discovery, Fibre Channel Zone Configuration, Iscsi Devices Folder Properties

    Figure 16 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 17).

  • Page 40: 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 18).

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

    Figure 19 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 20).

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

    Figure 20 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 43: Code Load, Set Iscsi Controller Time

    Figure 21 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 44: Shutting Down And Restarting The Mpx200, Saving Or Restoring The Mpx200 Configuration

    Figure 22 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 23). Figure 23 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 45: 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 46: Removing An Iscsi Controller, Blue Led Locating Beacon, Locate Hardware Device

    Figure 25 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 26). Figure 26 Locate hardware device Removing an iSCSI controller Before you remove an iSCSI controller permanently, ensure that all virtual disk presentations have been removed.

  • Page 47: Iscsi Controller Options: Remove Controller

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

  • Page 48

    Managing the MPX200 using HP Command View EVA...

  • Page 49: 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 50: Eva Storage System Rules And Guidelines, Hp Command View Eva Management Rules And Guidelines

    Table 4 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 27. 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 51: 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 52: Fibre Channel Switch And Fabric Support, Operating System And Multipath Software Support

    Table 5 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 53: 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 23 and Appendix on page 307 for more information. • Both single-path and multipath initiators are supported on the same MPX200. •...

  • Page 54: 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 55: 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 7 lists the IP network adapters supported by the MPX200. Table 7 Supported IP network adapters Operating system Network interconnect...

  • Page 56: 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 28). Figure 28 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 57: Iscsi Initiator Properties: Discovery Tab

    Figure 29 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 30). Figure 30 iSCSI initiator properties: Discovery tab In the Target Portals section, click Add. A dialog box opens.

  • Page 58: 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 31, MPX200-XL is the target EVA storage system. Figure 31 Adding a host Select the Hosts folder. Click Add host to create an iSCSI initiator host.

  • Page 59: Virtual Disk Properties

    Figure 32 Virtual disk properties Figure 33 Host details MPX200 Multifunction Router...

  • Page 60: 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 34). The status should be Inactive. Figure 34 Targets tab Select the target IQN noted in Step 2.d, and then click Log On.

  • Page 61: 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 62: 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 35).

  • Page 63: Mpio Mpio Properties Page Before Reboot, Mpio Properties Page After Reboot

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

  • Page 64: 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 38). Figure 38 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 65: 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 66: 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 39).

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

    Figure 41 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 42).

  • Page 68: 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 69: Selecting The Newly Added Target, Select Status

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

  • Page 70: 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 71: 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 47). Figure 47 Configure the iSCSI initiator and targets Select the Discovered Targets tab and enter the iSCSI target IP address (Figure 48).

  • Page 72: Log In To The Target

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

  • Page 73: 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 50). Figure 50 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 74

    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 75: 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 76: 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 77: Presenting Eva Storage For Linux, Iscsi Initiator Setup For Vmware

    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 78: Configuration Tab

    Configure the VMKernel TCP/IP networking stack for iSCSI support. Configure the VMkernel service console with dedicated virtual switch with a dedicated NIC for iSCSI data traffic. Follow the instructions from VMware. Figure 51 on page 78 shows an example of a configuration. Figure 51 Configuration tab MPX200 iSCSI configuration rules and guidelines...

  • Page 79: Firewall Properties Dialog Box

    Open a firewall port by enabling the iSCSI software client service: Using the VMware VI client, select the server. Click the Configuration tab, and then click Security Profile. Click the Properties link. The Firewall Properties dialog box is displayed. See Figure 52 on page 79.

  • Page 80: General Properties Dialog Box

    Enable the iSCSI software initiators: In the VMware VI client, select the server from the inventory panel. Click the Configuration tab, and then click Storage Adapters under Hardware. Under iSCSI Software Adapter, choose the available software initiator. Click the Properties link of the software adapter. The iSCSI Initiator Properties dialog box is displayed.

  • Page 81: Add Send Target Server Dialog Box

    Set up Discovery Addressing for the software initiator: Repeat Step 4 to open the iSCSI initiator Properties dialog box. Click the Dynamic Discovery tab. Click Add to add a new iSCSI target. The Add Send Target Server dialog box is displayed. See Figure 54 on page 81.

  • Page 82: Configuring Multipath With The Solaris 10 Iscsi Initiator, Rescan Dialog Box

    To verify that the LUNs are presented to the VMware host, rescan for new iSCSI LUNs: In VMware’s VI client, select a server and click the Configuration tab. Choose Storage Adapters in the hardware panel and click Rescan above the Storage Adapters panel.

  • Page 83: Mpxio Overview

    MPxIO overview The Sun multipathing software (MPxIO) provides basic failover and load-balancing capability to HP StorageWorks EVA4x00/6x00/8x00 storage arrays. MPxIO allows the merging of multiple SCSI layer paths, such as an iSCSI device exposing the same LUN through several different iSCSI target names.

  • Page 84

    • With no load balancing • With no failback To configure MPxIO for HP storage arrays, you must add information to the /kernel/drv/ scsi_vhci.conf file. Use a text editor to modify the configuration file. For example: # vi /kernel/drv/scsi_vhci.conf Change load balancing to none: load-balance="none";...

  • Page 85

    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 86

    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 87

    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 88

    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 89

    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 90

    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 91: 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 92: 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 56 iSCSI initiator MPIO properties Microsoft MPIO for iSCSI load-balancing policies The Microsoft MPIO for iSCSI load-balancing policies are as follows: •...

  • Page 93: 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 94: Configuring The Qlogic Iscsi Hba, Microsoft Iscsi Initiator Installation

    Access the Microsoft iSCSI Initiation Installation page of the Software Update Installation Wizard (Figure Figure 57 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 95: Connect To Host Window, Start General Configuration Wizard

    Click Yes to launch the general configuration wizard (Figure 59). 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 96: 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 60). Enter the first iSCSI target port IP address. Figure 60 HBA Port Target Configuration window Repeat steps 1 and 2 for each MPX200 you want to add. Click Next.

  • Page 97: 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 58 to: • Create an iSCSI host. • Present LUNs to the iSCSI host. On the iSCSI HBA tab (Figure 62), verify that the QLogic iSCSI HBA is connected to the iSCSI LUNs in SMS under the HBA iSCSI port.

  • Page 98: Microsoft Windows Cluster Support, Microsoft Cluster Server For Windows 2003

    Figure 63 HP MPIO DSM Manager with iSCSI devices Microsoft Windows Cluster support Microsoft Cluster Server for Windows 2003 iSCSI Failover clustering is supported on the HP StorageWorks MPX200 Multifunction Router. For more information, see http://www.microsoft.com/windowsserver2003/technologies/storage/iscsi/ iscsicluster.mspx. Requirements • Operating system: Windows Server 2003 Enterprise, SP2, R2, x86/x64 •...

  • Page 99: Microsoft Cluster Server For Windows 2008, Iscsi Persistent Reservation Setup

    Click Modify to make changes. See Figure 64 on page 99. Click Done to finish. Figure 64 iSCSI Persistent Reservation Setup Each cluster is required to have its own value, and each node of a single cluster must have its own value.

  • Page 100: Setting Up Authentication, Chap Restrictions

    Requirements • Operating system: Windows Server 2008 Enterprise, SP2, R2, x86/x64 • Firmware: Minimum version—3.1.0.0, released November 2009 • Initiator: • Multiple NIC/iSCSI HBA ports—four recommended • one public • one private • two storage, for higher availability and performance •...

  • Page 101: Microsoft Initiator Chap Secret Restrictions, Linux Chap Restrictions, Atto Macintosh Chap Restrictions, Recommended Chap Policies

    • 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 • When an initiator uses iSNS for target discovery, only normal session CHAP applies NOTE: There is no restriction on the type of characters that can be entered.

  • Page 102: Enabling Single-direction Chap During Discovery Session And Normal Session, Chap Single-direction Settings

    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. To enable single-direction CHAP, you must enable CHAP for a specific initiator record on the MPX200 and enter a corresponding CHAP secret from the iSCSI host.

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

    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). Click OK.

  • Page 104: 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 105

    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 106: Session, Chap Single-direction Settings

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

  • Page 107: 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 108

    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 109

    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 110

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

  • Page 111

    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 112

    MPX200 iSCSI configuration rules and guidelines...

  • Page 113: Mpx200 Fcip, 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 114: Redundant Fcip Network Structure Example, Using Fcip To Encapsulate Fc Packets

    Redundant FCIP network structure example In a high-availability FCIP configuration, pairs of MPX200 routers and two independent IP networks provide full redundancy. Loss of connectivity through one of the IP networks will not result in a loss of connectivity between the fabrics. The redundant configuration can be either a single HP StorageWorks MPX200 Multifunction Router 1 GbE Base Chassis with a HP StorageWorks MPX200 Router 1 GbE Upgrade Blade, or an HP StorageWorks MPX200 Multifunction Router 10 1 GbE Base Chassis with a HP StorageWorks...

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

    Configuring an FCIP route and specifying an FC and GE port pair take precedence over any previous configuration for the port pair (FC/GE). This means that for an existing or new iSCSI configuration, once an FCIP Route is configured, one FC port and one GE port are no longer available for iSCSI or DM use.

  • Page 116: Fcip And Iscsi Performance, Mpx200 Iscsi/fcip Configurations

    Figure 68 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. Therefore, only the targets from one fabric or the other will be available to iSCSI initiators connected to that MPX200 blade;...

  • Page 117: Mpx200 Basic Fcip Configuration With One Or Two Long-distance Links

    • Figure 78 on page 121 MPX200 iSCSI and FCIP dedicated blades, both local and remote • Figure 79 on page 122 HP Continuous Access EVA 3 site configuration with four gateways • Figure 80 on page 123 HP Continuous Access EVA 3 site configuration with six gateways •...

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

    Figure 71 MPX200 high-availability configuration with one or two long-distance links Figure 72 MPX200 high-availability configuration with fully-redundant long-distance links Figure 73 MPX200 configuration with remote IP Distance gateway (mpx110) MPX200 FCIP...

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

    Figure 74 MPX200 highly-redundant configuration with one or two long-distance lists Figure 75 MPX200 highly redundant pairs of gateways with fully-redundant long-distance links MPX200 Multifunction Router...

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

    Figure 76 MPX200 simultaneous iSCSI and FCIP with remote dedicated FCIP blade Figure 77 MPX200 simultaneous iSCSI and FCIP, both local and remote MPX200 FCIP...

  • Page 121: Hp Continuous Access Eva 3 Site Configurations

    Figure 78 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 122: Site Configuration With Four Mpx200 Routers, Site Configuration With Six Mpx200 Routers

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

  • Page 123: Site Configuration With Eight Mpx200 Routers

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

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

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

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

    Figure 82 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 126: 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 127: 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 128: 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 129: 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 130: 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 17 through Table 23 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 17 through Table 23...

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

    128K 1 or less Table 19 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 20 OC—3 150 Mb/Sec (Bandwidth = 148 Mb) Round trip time (RTT) in Compression recommend- Window size (bytes)

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

    1 or less Table 21 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 22 OC—12 621 Mb/Sec (Bandwidth = 699 Mb) Round trip time (RTT) in Compression recommend- Window size (bytes)

  • Page 133: Configuring An Fcip Route, Step 1. Verify Your System Requirements, Step 2. Pre-installation Checklist

    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 65 on page 113): • HP StorageWorks MPX200 Multifunction Router 1 GbE Base Chassis or HP StorageWorks MPX200 Multifunction Router 10 1 GbE Base Chassis.

  • Page 134: Step 3. Rack-mount The Mpx200, Step 4. Install The Sfps

    • 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 • IP address of the remote MPX200 that connects to the first available GE port •...

  • Page 135: Mpx200 Ports And Leds

    Verify that the heartbeat LED is blinking (once per second) and that the System fault LED does not light. Figure 83 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 136: 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 84): Figure 84 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 137: 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 138: Step 8. Cable The Mpx200 Fc, Ge And Management Ports

    • 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 • C-Switch(config)# exit • C-Switch# copy run start Step 8. Cable the MPX200 FC, GE and management ports Follow these steps to cable the MPX200: Connect the management port cable to your Ethernet network, which is accessible from the management server.

  • Page 139: Offline Data Migration, Features Overview

    6 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 140: Feature Details, Job Scheduling, Immediate Schedule, Delayed Schedule, Serial Schedule

    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 141: 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 142: 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 143: Data Migration Job States, Data Migration Job Commands, Logs

    Data migration job states Table 24 lists the possible data migration job states. Table 24 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 144: Getting Started, Supported Configurations, Fabric Configuration, 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 145: 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 146: 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 147: 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 148: Installing The Mpx200 Mpx Manager For Data Migration Services, Download The Application, Component Requirements

    • 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 149: 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 150: Hardware Setup, Software Setup, Using Dms, General Steps For Data Migration

    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 151: 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 173). If the router fails to discover arrays, use the target rescan option (see “Rescanning targets” on page 169). 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 152: Setting Array Properties: Target Type

    From the Target Type list, select Source, as shown in Figure Figure 89 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 153: 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 154: 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 155: 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 156: 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 91 Migration Schedule Options: individual job Depending on your selection in the preceding step, continue with either Scheduling an individual...

  • Page 157: 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 92 shows an example.

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

    In the Data Migration Jobs Options dialog box (see Figure 93), 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 159

    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 160

    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 161: 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 162: 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 163: Starting Serial Scheduled Jobs, Serial Data Migration Jobs Options

    In the Data Migration Jobs Options dialog box (Figure 93 on page 158), 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 164: 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 165: Adding Luns To The Dms Iscsi Host Entry With Hp Command View Eva

    Figure 97 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 166: 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 98 shows the creation of a virtual disk with HP Command View EVA.

  • Page 167: Viewing The Status Of Data Migration Jobs, Viewing Data Migration Job Status In The Gui

    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. If there are redundant iSCSI blades, the LUN will be presented to the DMS iSCSI initiator and VPGroup on each blade.

  • Page 168: 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 100. Figure 100 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 169: 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 170: 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 171: 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 101. Figure 101 Viewing migration job details (Optional) From the migration job details pane, perform any of the following job control actions as needed: •...

  • Page 172: 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 173: 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 174: 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 175

    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 176: Mpx Log: Migration Log

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

  • Page 177: 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 178: 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 179: 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 104), click Options. Figure 104 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 180: Acknowledging A Data Migration Job, Verifying Jobs Options

    In the Verifying Jobs Options dialog box (Figure 105), 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 181: 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 182: Installing A Data Migration License Key In The Gui, New License Key Dialog Box

    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 183: 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 108) indicates the success of the license add operation. Figure 108 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 106 on page 182.

  • Page 184: 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 185: License Array Dialog Box

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

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

    Figure 110 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 187: 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 188: Admin Session, Command Line Interface, User Accounts, User Sessions

    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 227): show migration_usage The following example shows the show migration_usage command. MPX200 (miguser) #>...

  • Page 189: Miguser Session, Commands, Cli 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 190

    “show fc” on page 216 “show migration” on page 217 “show array” on page 218 “show luninfo” on page 220 “show migration_luninfo” on page 221 “show migration_params” on page 223 “show mgmt” on page 224 “show memory” on page 225 “show properties”...

  • Page 191: Set System

    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 192: Set Features

    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 193

    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 194: 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 195: 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 196: 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 197: 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 198: 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 199: 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 200

    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 201: 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 202: 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 203: 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 204: 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 205: 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 206: 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 207: 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 208: 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 209

    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 210: 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 211: 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 212: 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 213: 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 214: Compare_luns Resume

    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 215: 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 216

    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 217: 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 218: 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 219

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

  • Page 220: Show Luninfo

    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 221: 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 222

    Controller Id WWPN, PortId Path Status ------------- --------------------------------- ----------- 20:78:00:c0:ff:d5:92:e5, 02-04-00 Current Optimized Offline Data Migration...

  • Page 223: 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 MPX200 Multifunction Router...

  • Page 224: Show Mgmt

    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 225: 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 226: Show Properties

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

  • Page 227: 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 228: Show Perf

    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 229: 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 230: Show Features

    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 231: 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 232: 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 233: 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 234

    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 Offline Data Migration...

  • Page 235: Show Targets

    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 236: 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 237: 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 238: 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 239: 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 240: 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 241: 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 242: Show Compare_luns, Performance, Performance Factors

    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 243: Maximizing Performance, Optimal Configuration And Zoning, Using The Hp Msa2012fc Storage Array, Msa2012fc Array Behavior

    • 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 244: 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 245: Restrictions, Reconfiguring Luns On A Storage Array, Removing An Array After Completing Data Migration Jobs

    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 246

    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 247

    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 248

    Offline Data Migration...

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

    7 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 112.

  • Page 250: 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 251: 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 115). Figure 115 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 252: 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 118). Figure 118 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 253: Troubleshooting Using Hp Command View Eva, Fcip Route Ping Command, Iscsi Controller Properties

    Figure 119 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 120).

  • Page 254: 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 255: 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 122 Figure 123). Figure 122 Virtual disk properties: Host details Figure 123 iSCSI initiator properties: Targets tab MPX200 Multifunction Router...

  • Page 256: 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 257

    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 258

    Diagnostics and troubleshooting...

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

    8 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 260: 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 261: 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 30 Document conventions Convention Element Blue text: Table 30 Cross-reference links and email addresses Blue, underlined text:...

  • Page 262: 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 263: Command Line Completion, Authority Requirements, A Command Reference, Command Syntax, 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 264: Admin, Commands

    • 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 265: 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 266: 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 267: 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 268

    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 269: 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 270

    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 271: 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 272: 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 273: 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 274

    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 275: 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 276: 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 277: 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 278

    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 279: Set Alias

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

  • Page 280: 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 281

    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 282: 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 283: 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 284: 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 285

    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 286: Show, Set Vpgroups

    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 287

    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 288: Show Chap

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

  • Page 289: 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 290: 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 291: Show Initiators, Show Features, 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 292: 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 293: 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 294

    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 295: 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 296: Show Ntp, Show Mgmt

    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 297

    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 298: 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 299: Show Snmp, Show Properties

    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 300: 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 301

    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 302: 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 303

    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 304: 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 305: 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 306

    Command referencecommand reference...

  • Page 307: 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 308: 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 309: Working With Mpx200 Router Configurations, Modifying A Configuration, Saving And Restoring 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 310: 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 311: 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 312: Snmp Trap Configuration Parameters, Management Information Base, Network Port Table

    SNMP trap configuration parameters SNMP trap configuration lets you set up to eight trap destinations. Choose from Trap 1 through Trap 8 to configure each trap. Table 33 describes the parameters for configuring an SNMP trap. Table 33 SNMP trap configuration parameters Parameter Description Enables or disables trap n.

  • Page 313

    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 314: 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 315

    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 316: 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 317

    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 318: 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 319

    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 320: 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 321

    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 322

    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 323: 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 324: 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 325: 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 326: 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 327: 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 328: 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 329: 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 330

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

  • Page 331: 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 332

    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 333

    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 334

    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 335

    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 336

    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 337

    #%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 338

    #%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 339

    #%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 340

    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 341

    #%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 342

    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 343

    #%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 344

    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 345

    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 346

    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 347

    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 348

    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 349

    Table 35 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 350

    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 351

    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 352

    Table 36 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 353

    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 354

    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 355: E Regulatory Compliance And Safety, Regulatory Compliance, Federal Communications Commission Notice For Class A Equipment

    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 356: 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 357: International Notices And Statements, Canadian Notice (avis Canadien), Class A Equipment, Bsmi Notice, Japanese Notice

    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 358: Korean Notices, Safety, Battery Replacement Notice

    Korean notices Safety Battery replacement notice Your switch is equipped with a lithium manganese dioxide, a vanadium pentoxide, or an alkaline internal battery or battery pack. There is a danger of explosion and risk of personal injury if the battery is incorrectly replaced or mistreated.

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

    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 360: 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 361: 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 362: 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 363: 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 364: 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 365: 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 366: Restoring The Mpx200 Configuration, 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 367

    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 368

    Saving and restoring the MPX200 configuration...

  • Page 369: G Data Migration Best Practices, Overview, Terminology, Relationship Between Application Data And Physical Storage

    G Data migration best practices This appendix provides end-to-end “best practices” for using the HP StorageWorks MPX200 data migration service. The MPX200 data migration service migrates the data at block level. When data migration is successful, the application is able to access the same data after the data is migrated to a new logical unit number (LUN).

  • Page 370: Lun Access To A Server, General Steps For Data Migration

    • The Windows SharePoint application accesses its data through a mount point F:\Sharepoint. • The Oracle application running on a HP-UX (UNIX) host accesses its data through a mount point /home/oracle. • The Apache Web Server application on a Linux (UNIX) host access its data through a mount point /data/webinfo Typically, you create a mount point on a volume.

  • Page 371: Inventory Checklists, Step 1. List The Source And Destination Storage Array

    Inventory checklists Data migration checklists help you take inventory of all items affected by a data migration project. This section provides a list of servers and applications, and defines relationships of application data to LUNs and how LUNs are accessed through the server. The migration checklists will also help you identify the changes you may need to make to the server after migration.

  • Page 372: Step 4. List And Create Lun Id Mappings, Physical Device Information, Lun Id Mappings

    most cases, the OS automatically discovers the relationship between the volume and the migrated LUN(s) on a destination storage array. Table 39 Physical device information Server Application Mount Point Volume Physical Disk or LUN ID Raw Device Node (if any) Step 4.

  • Page 373: Step 5. List And Create Fibre Channel Zoning, Performance And Downtime

    Step 5. List and create Fibre Channel zoning For a Fibre Channel SAN, create a list of fabric zones that contain the WWPN associated with servers, storage arrays (source and destination) and MPX200, as shown in Table 41. The destination array should be zoned in only with the MPX200 before migration.

  • Page 374: Minimizing Downtime, Before Application Downtime, During Application Downtime

    Minimizing downtime The ability of the MPX200's to deliver a migration rate of 4TB/hr. per blade, combined with seamless integration of the MPX200 in the SAN and data protection features such as array attributes (source/destination), make it likely that the downtime objective will be met by offline data migration. The following recommendations will simplify the data migration project: •...

  • Page 375: Validating Integrity Of The Data, Operating Systems Dependencies, Windows Operating System

    After the data is migrated for the specified server or cluster, present the destination LUNs to the server or cluster by changing the fabric zoning and LUN presentation from the array. Reboot the server, and then validate that the new LUNs are seen by the system and that the volumes are mounted on the destination LUNs.

  • Page 376: Checklist Examples, Step 1. List The Source And Destination Storage Array, Example: Storage Array Information

    If volumes are not managed through a logical volume manager in the system, it is important to follow the pre-migration checklists to identify the physical device nodes (/dev/rdsk/c0t1d1) on which the volume is mounted. After data migration, the physical device node may change. Change the volume mount such that it now it points to the new physical device (dev/rdsk/c0t2d5).

  • Page 377: Step 2. List The Servers Impacted By The Data Migration Project

    Step 2. List the servers impacted by the data migration project Table 44 shows an example of the server information that can be retrieved by server administrators. Table 44 Example: Server information Server Operating sys- IP address Multi-pathing Logical Multi-pathing soft- tem and ver- software for volume...

  • Page 378: Example: Lun Id Mappings, Step 4. List And Create Lun Id Mappings

    Step 4. List and create LUN ID mappings Table 46 shows that a different LUN from a storage array is presented as the same LUN ID (2) on two different servers (HR-Dept, iPortal). Table 46 Example: LUN ID mappings Server Source Volume Capacity...

  • Page 379: Assigning Luns To The Mpx200 For Data Migration, Assigning Luns From An Msa2012fc Array

    Table 48 shows new Fibre Channel zones information to configure MPX200 for data migration and to migrate the data. The MPX200 Fibre Channel ports are configured with source and destination arrays. Table 48 Example B: Pre-migration Fibre Channel zoning information FC switch and FC zone Zone members (WWPNs)

  • Page 380: Viewing The Storage Management Utility

    To assign LUNs: Perform zoning as follows: Connect the Fibre Channel ports of the data migration appliance to a switch where the storage controller ports are also logged. Using switch management tools, create a zone DM_Host_MSA2012, and then add the WWPN of the data migration appliance Fibre Channel ports and storage controller ports in this zone.

  • Page 381: Viewing Wwpns In Storage Management Utility

    In the left pane, click VOLUME MANAGEMENT, click volume mapping, and then click manage host list. Figure 126 shows the WWPN of the data migration appliance in the right pane. Figure 126 Viewing WWPNs in Storage Management Utility In the Manufacturer Nickname box, type DM-Host.s. To accept and save the changes, click Update.

  • Page 382: Assigning Luns From An Msa1000/1500 Array, Selecting Luns In Storage Management Utility

    In the right pane, click the LUN to be assigned to the data migration appliance (see Figure 127). Figure 127 Selecting LUNs in Storage Management Utility In the Assign Host Access Privileges table, select the DM-Host in the Host WWN - Name list, and then enter the appropriate, planned LUN ID.

  • Page 383: Configure Available Device(s), Entering A Connection Name

    Open the Array Configuration Utility. The Configure Available Device(s) window appears, as shown in Figure 128. Figure 128 Configure available device(s) In the right pane under Common Tasks, click Selective Storage Presentation, and then click Enable. A list of the WWPNs seen by the MSA controller appears, as shown in Figure 129.

  • Page 384: Assigning Luns From An Hds Array, Selecting The Host Mode, Selecting Luns

    From the list box, select Windows as the host mode value, as shown in Figure 130. Figure 130 Selecting the host mode Select the LUNs to be assigned to the DM-Host by checking the box associated with the previously planned LUNs, as shown in Figure 131.

  • Page 385: Changing To Management Mode

    Perform zoning as follows: Connect the Fibre Channel ports of the data migration appliance to a switch where the storage controller ports are also logged. Using switch management tools, create a zone, DM_Host_HDS. In this zone, add the WWPN of the data migration appliance Fibre Channel ports and storage controller ports.

  • Page 386: Selecting A Port For New Host Group

    In the left pane, right-click the port of the array that has been zoned with the data migration appliance, and then click Add New Host Group (see Figure 133). Figure 133 Selecting a port for New Host Group In the Host Group dialog box, type DM-Host in the Name box, and then click OK. Data migration best practices...

  • Page 387: Selecting Dm-host Nodes

    In the Array System Viewer left pane under Host Groups, click the + sign next to the port to expand the newly-created DM-Host group entity. Three nodes are listed: Options, Logical Unit, and WWN, as shown in Figure 134. Figure 134 Selecting DM-Host nodes In the left pane, click the Options node, and then at the bottom of the right pane, click Simple Setting.

  • Page 388: Array System Viewer

    In the Array System Viewer dialog box, under the DM-Host group, click the WWN node. Then at the bottom of the right pane, click Modify WWN Information (see Figure 135). Figure 135 Array System Viewer Complete the Modify WWN Information dialog box as follows: Under Assignable WWN, click the WWN of the data migration appliance.

  • Page 389: Assigning Luns From An Ibm Ds4k/ds5k/lsi Array, Modifying Mapping

    Complete the Modify Mapping dialog box as follows (see Figure 136): Under H-LUN / Available Logical Units, select an appropriate LUN. Click the (up arrow) to map the LUN to the DM-Host group. To accept and save the LUN assignment, click OK. Figure 136 Modifying mapping Refresh the data migration user interface to see if the LUN assignment is reflected properly and that the appropriate array entity appears under FC Array.

  • Page 390: Selecting Host To Define

    Perform zoning as follows: Connect the Fibre Channel ports of the data migration appliance to a switch where the storage controller ports are also logged. Using switch management tools, create a zone, DM_Host_IBM. In this zone, add the WWPN of the data migration appliance Fibre Channel ports and storage controller ports.

  • Page 391: Defining The Host

    Complete the Define Host wizard as follows (see Figure 138): Figure 138 Defining the host Under Specify name of host, type DM-Host as the name for the data migration appliance. In the Known HBA host port identifiers box, click the WWPN of the data migration appliance. Click Add to move the selected WWPN to the Selected HBA host port identifiers/aliases box.

  • Page 392: Selecting Host Operating System

    Figure 139 Selecting host operating system Click Next. On the Subsystem Management window, in the left pane’s Mapping View page, click either Undefined Mappings or the host group/host that currently has access to the LUNs that need to be part of data migration jobs. Select the LUNs to be assigned to the DM-Host by right-clicking the LUN in the right pane, and then clicking Change Mappings.

  • Page 393: Defining Additional Mapping

    Complete the Define Additional Mapping dialog box as follows (see Figure 140): In the Host group or host box, click DM-Host. In the Logical unit number (LUN) (0 to 255) box, click the previously planned LUN number. Under Logical Drive, click the appropriate logical drive. To accept and save the LUN assignment, click Add.

  • Page 394: Assigning Luns From An Eva 4/6/8000 Series Array, Opening Hp Command View Eva

    Assigning LUNs from an EVA 4/6/8000 series array Storage Vendor Array Model EVA 4/6/8000 series arrays LUN Assignment Tool HP Command View EVA user interface To assign LUNs: Perform zoning as follows: Connect the Fibre Channel ports of the data migration appliance to a switch where the storage controller ports are also logged.

  • Page 395

    Complete the Add a Host information in the right pane as follows (see Figure 142): Under Basic Settings in the Name box, type DM-Host. Under Port World Wide Name, click the WWN of the data migration appliance. Under Operating System, click Microsoft Windows. Click the Add host button.

  • Page 396: Assigning Luns From An Emc Clariion Array, Presenting Vdisks

    Present virtual disks as follows (see Figure 144): In the left pane, double-click the Virtual Disks node. Click the LUN that needs to be presented to the data migration appliance for data migration. In the right pane, click the Presentation tab, and then click the DM-Host. To accept and save the LUN assignment, click Present Vdisk.

  • Page 397: Viewing Enterprise Storage

    Perform zoning as follows: Connect the Fibre Channel ports of the data migration appliance to a switch where the storage controller ports are also logged. Using switch management tools, create a zone, DM_Host_EMC. In this zone, add the WWPN of the data migration appliance Fibre Channel ports and storage controller ports.

  • Page 398: Registering Initiator Record

    Complete the Register Initiator Record dialog box as follows (see Figure 146): In the Initiator Type box, click CLARIION Open. Under Host Information, type the values for Host Name and IP Address. Click OK. Figure 146 Registering Initiator Record Data migration best practices...

  • Page 399: Creating Storage Group

    Create a storage group to add to the newly-registered DM-Host entity as follows (see Figure 147): In the Enterprise Storage window, Storage page, right-click the Storage Groups node. Click Create Storage Group. In the Create Storage Group dialog box, type DM-Host as the Storage Group Name. To save the changes, click either OK or Apply.

  • Page 400: Adding Dm-host To Storage Group

    Add the DM-Host host entity to the DM-Host storage group entity as follows (see Figure 148): Under the Storage Groups node, right-click DM-Host. Click Connect Hosts. In the DM-Host: Storage Group Properties dialog box, click the Hosts tab. On the Hosts page under Available Hosts, select the DM-Host host entity. Click the (right arrow) button to move DM-Host to the right pane’s Host to be Connected box.

  • Page 401: Adding Luns To Dm-host

    Add LUNs to the DM-Host storage group entity as follows (see Figure 149): Under the Storage Groups tree, right-click DM-Host. Click Select LUNs to view a list of available LUNs. In the DM-Host: Storage Group Properties dialog box, click the LUNs tab. On the LUNs page, select All on the Show LUNs list to view all LUNs that have been assigned to the host and that will be part of the data migration jobs.

  • Page 402

    Data migration best practices...

  • Page 403: Index

    Index additional equipment, required, admin command, agent shutdown notification, agent startup notification, Apple Mac iSCSI initiator, storage setup, Apple Mac OS X iSCSI initiator, assigning LUNs during data migration EMC CLARiiON array, EVA 4/6/8000 series array, HDS array, IBM DS4K/DS5K/LSI array, MSA1000/1500 array, MSA2012fc array, authority requirements,...

  • Page 404: Table Of Contents

    commands show stats, admin, show system, beacon, show targets, blade, show vpgroups, clear, shutdown, date, target, exit, traceroute, fciproute, configuration fru, blades, help, dual-blade fabric-attached, history, dual-blade multi-EVA, image, maximums, initiator, modifying, logout, single-blade fabric-attached, lunmask, single-blade multi-EVA, ping, configuration options, quit, configuring reboot,...

  • Page 405

    iSCSI Apple Mac initiator, EVA storage systems, Apple Mac OS X initiator, exit command, configuration, configuring MPIO devices, enable target discovery, initiator rules and guidelines, FC port down notification, initiator setup for Linux, FC port table, initiator setup for VMware, FCC notice, Linux initiator, fciproute command,...

  • Page 406

    MPX200 blade, locating, MPX200 features, rack mounting, MPxIO rack stability, enabling for HP EVA storage array, reboot command, multipath devices, monitoring, Red Hat Linux multipathing, installing and configuring, related documentation, reset command, router blade, network port down notification, network port table, notices battery replacement, save command,...

  • Page 407

    show system command, show targets command, websites show vpgroups command, HP Subscriber's choice for business, shutdown command, product manuals, SNMP Windows Cluster support, parameters, Windows Server 2003 trap configuration parameters, iSCSI initiator, Scalable Networking Pack, setup, Windows Server 2003, software storage system, statistics, storage...

Comments to this Manuals

Symbols: 0
Latest comments: