HPE StoreEver LTO-5 User Manual
  1. Manuals
  2. Brands
  3. HPE Manuals
  4. Storage
  5. StoreEver LTO 5
  6. User manual

HPE StoreEver LTO-5 User Manual

Failover
Hide thumbs Also See for StoreEver LTO-5:
Table of Contents

Advertisement

Quick Links

Download this manual
HPE StoreEver LTO-5 and LTO-6 Failover
User Guide
Part Number: 5200-2563
Published: December 2017
Edition: 8

Advertisement

Table of Contents
loading
Need help?

Need help?

Do you have a question about the StoreEver LTO-5 and is the answer not in the manual?

Questions and answers

Related Manuals for HPE StoreEver LTO-5

Summary of Contents for HPE StoreEver LTO-5

  • Page 1 HPE StoreEver LTO-5 and LTO-6 Failover User Guide Part Number: 5200-2563 Published: December 2017 Edition: 8...

  • Page 2: Table Of Contents

    Contents Overview....................6 Traditional library control path and drive connections without failover..........7 Basic path failover.........................9 Basic data path port failover details................... 9 Basic control path failover details..................10 Technology for basic control path failover................ 11 Advanced path failover....................... 12 Driver operation during device open................13 Driver operation while opening a connection to a library control path ......13 Driver operation during normal communications..............14 Path failure detection.......................
  • Page 3 Configuring failover for the MSL3040 or MSL6480 ......32 Control path failover configuration....................32 Enabling control path failover...................32 Locating the library world-wide node name after enabling basic control path failure ..33 Verifying basic control path failover..................33 Verifying advanced control path failover................34 Data path failover configuration....................
  • Page 4 Installing and using HP-UX advanced path failover drivers..... 59 Installing advanced path failover drivers..................59 Commands for viewing tape and library devices connected to a system........60 Finding the lockdown path......................62 Troubleshooting advanced path failover..................62 Enabling or disabling advanced path failover................62 Troubleshooting failover operation.............64 Locating a failed path........................64 Windows debugging logs and tools....................
  • Page 5 © Copyright 2014, 2016 Hewlett Packard Enterprise Development LP Acknowledgments ® ® ® ® Intel , Itanium , Pentium , Intel Inside , and the Intel Inside logo are trademarks of Intel Corporation in the United States and other countries. ®...

  • Page 6: Overview

    Overview With today’s high dependency on access to business information, safe-guarded data and limited backup windows, the reliability of the backup hardware and software is vital. Additionally, backup operations are usually automated, often done at night, and any first pass operator intervention is done remotely. To assist with these enterprise demands, Hewlett Packard Enterprise provides High Availability Failover features for ESL G3 Tape Libraries and the MSL2024, MSL3040, MSL4048, MSL6480, MSL8048, and MSL8096 Tape Libraries with LTO-5 and LTO-6 Fibre Channel tape drives.

  • Page 7: Traditional Library Control Path And Drive Connections Without Failover

    ◦ Available for the ESL G3, MSL3040, and MSL6480 Tape Libraries. ◦ Not available for the 1/8 G2 Tape Autoloader nor the MSL2024, MSL4048, MSL8048, or MSL8096 Tape Libraries. Traditional library control path and drive connections without failover A typical connection for a Fibre Channel tape library using the drive to bridge commands to the library controller in a two drive tape library is shown in Figure 1: Typical bridged library controller connection on page 7.

  • Page 8: Part Number

    1. Ultrium Dual Port Fibre Channel Tape Drives 2. Host connection 3. Internal connection In the typical bridged library controller connection each tape drive has one physical link to the SAN switch and connects to the SAN switch as one Fibre Channel device. The tape drive hosting the library controller path connects as one Fibre Channel device containing two logical units.

  • Page 9: Basic Path Failover

    Basic path failover Basic path failover uses features in the tape drive and library firmware to recover paths following a link failure. Basic data path port failover details Basic data path port failover (see Figure 3: Data path port failover example configuration on page 9) can be configured on each LTO-5 or LTO-6 dual-port Fibre Channel tape drive in the library.

  • Page 10: Basic Control Path Failover Details

    1. Primary data path 2. Secondary data path 3. Host connection 4. Ultrium dual port Fibre Channel tape drive Basic control path failover details Library basic control path port failover (see Figure 4: Control path port failover example configuration on page 11) is configured with one drive hosting the active logical link to the library controller and a second drive configured as the passive logical link to the library controller.

  • Page 11: Technology For Basic Control Path Failover

    Figure 4: Control path port failover example configuration 1. Primary data path 2. Standby data path 4. Ultrium Dual Port Fibre Channel Tape Drives 3. Host connection 5. Passive logical link to switch shares physical link 6. Active logical link to switch shares physical link on drive #2 on drive #1 Technology for basic control path failover...

  • Page 12: Advanced Path Failover

    INCITS/T11 working group (see clause 6) in the FC-LS-2 specification. NPIV allows a single physical port to connect to a Fibre Channel switch multiple times using multiple node and port names. Advanced path failover Advanced path failover uses capabilities in the LTO-6 tape drives and the libraries in which they are installed, combined with software drivers running on a host system to provide path failover when multiple paths are available to a tape drive or to a library controller.

  • Page 13: Driver Operation During Device Open

    Addressed Logical Port Example SCSI Example Logical Unit Unit address Worldwide Identifier Tape drive 1 Port B ID 2 LUN 0 50:01:10:a0:00:00:00:01 Library Controller Port B ID 2 LUN 1 50:01:10:a0:00:00:00:02 Tape drive 2 Port A ID 3 LUN 0 50:01:10:a0:00:00:00:03 Library Controller Port A...

  • Page 14: Driver Operation During Normal Communications

    available control path drive to determine the preferred control path drive (called the ‘active’ control path drive) before requesting a connection. Driver operation during normal communications The advanced path failover driver passes commands through without any command translation and with minimal additional processing in normal operation to retain the maximum possible performance.

  • Page 15: Library Controller Path Failure Recovery

    Library controller path failure recovery In most cases. the library controller path failure recovery is the same as the tape drive path failure recovery. If all paths to the drive hosting the library controller have failed, the advanced path failover driver can open a connection to the library controller through another tape drive.

  • Page 16: Enabling Basic Path Failover

    4G connections, set the fill word to idle. • The switch is running a supported version of software. For a list of supported software, see the compatibility matrix on the Backup, Recovery and Archive website: http://www.hpe.com/storage/ daprcompatibility • The drive port FC topology must be in Fabric mode and the switch side must be set to F-port or Auto Sense.

  • Page 17: Hardware-Specific Requirements For Basic Failover

    • The switch is running a supported version of software. For a list of supported software, see the compatibility matrix on the Barkup, Recovery and Archive website: http://www.hpe.com/storage/ daprcompatibility • For advanced data path failover, the host must have a physical path to both the first port and secondary port on the Fibre Channel drive.

  • Page 18: Installing Advanced Path Failover

    If only one switch is available, that switch must be zoned to create two logical SANs. Review the SAN design guidelines The general SAN design guidelines for tape are documented at: http://www.hpe.com/storage/ daprcompatibility Installing advanced path failover...

  • Page 19: Preparing The Library

    Preparing the library Advanced path failover is a licensed feature with Control Path Failover and Data Path Failover licensed separately. Licenses for all failover solutions are also available as a high-availability bundle. Control Path Failover provides path fault tolerance for the robot controller and Data Path Failover provides fault tolerance for the tape drive data path.
  • Page 20 information. The Linux path failover driver and the HP-UX operating system have built-in load balancing and when a tape drive is opened the operating system selects the best path based on the current path loading. The Linux advanced path failover driver has a command for requesting a partition path to be preferred. That setting will only persist until the next reboot because the hardware configuration can change when the server reboots.

  • Page 21: Configuring Failover For The Esl G3 Tape Libraries

    Library and tape drive prerequisites for basic data path failover • The HPE StoreEver ESL G3 LTO-5/LTO-6 Ultrium Data Path Failover license is installed on the library. • The host has a physical path to both the primary and secondary ports on the FC drive.

  • Page 22: Library Configurations For Mixed Failover Environments

    The host will have two different worldwide names for the two different HBAs and each worldwide name may be granted access to all ports or one name may be granted access to the first Fibre Channel port and the second name may be granted access to the second Fibre Channel port. Library configurations for mixed failover environments In a mixed failover environment, hosts with advanced path failover drivers and hosts without advanced path failover drivers all access the same tape library.

  • Page 23: Verifying Data Path Failover

    NOTE: In the following illustration, with 720H and later firmware versions, the ADPF column is labeled Driver. 5. Wait for the configuration change to complete. Verifying data path failover To verify that basic data path failover is configured, navigate to Monitor > Drives to launch the Drive Status dialog.

  • Page 24: Diagnosing Basic Data Path Failover

    • To verify that basic or advanced data path failover is working: • From the Fibre Channel switch's management console, down the main Fibre Channel port to a drive. • From the host computers confirm that the drive is still accessible. After confirming that the drive is still accessible the host logs should show a failover event.
  • Page 25 Configuring failover for the ESL G3 Tape Libraries...

  • Page 26: Disabling Data Path Failover

    Library and tape drive prerequisites for basic control path failover Procedure 1. The HPE StoreEver ESL G3 LTO-5/LTO-6 Ultrium Control Path Failover license is installed on the library. 2. The host has a physical path to both the primary and secondary FC drives.

  • Page 27: Library And Tape Drive Prerequisites For Advanced Control Path Failover

    Library and tape drive prerequisites for advanced control path failover Procedure 1. The HPE StoreEver ESL G3 LTO-5/LTO-6 Ultrium Control Path Failover license is installed on the library. 2. The host has a physical path to both the primary and secondary FC drives.

  • Page 28: Configuring The Library After Enabling Control Path Failure

    NOTE: With firmware versions 720H and later, the Advanced button shown in this illustration is labeled Driver. 7. Click OK. Configuring the library after enabling control path failure Library configuration requirements when using Secure Manager Use the Secure Manager Configuration Wizard to map hosts that have been granted access to FC drive ports.
  • Page 29 SAN configuration requirements When basic control path failover is enabled, the library is no longer presented as a logical unit behind the tape drive and is assigned a new Fibre Channel node name which needs to be zoned in the same zone as the primary and secondary control path drives.

  • Page 30: Verifying Control Path Failover

    Verifying control path failover Before testing control path failover, verify that the configuration is correct in the Drive Status dialog, which is accessed from the Monitor > Drives menu. The Control Path column identifies the primary and secondary control path drives. The drive currently hosting control path access is marked Active. Procedure 1.
  • Page 31 7. The Control Path dialog appears with the command path drive highlighted in yellow and the failover drive selected. Un-select the failover drive, and click OK. 8. Click Yes in the Warning dialog to take the partition offline. Wait for the configuration change to complete.

  • Page 32: Configuring Failover For The Msl3040 Or Msl6480

    Advanced path failover is not enabled for the partition. Advanced and basic failover may not be mixed within a partition. • The HPE MSL6480 LTO-5&6 Control Path (CtrlP) Failover license has been added to the library. The requirements for using advanced control path failover are: •...

  • Page 33: Locating The Library World-Wide Node Name After Enabling Basic Control Path Failure

    Procedure 1. From the Configuration area, click Expert Wizard in the Partitions menu. 2. Select the partition to be configured and then click Next until the wizard displays the Select Control Path Failover Type screen. 3. Select the type of control path failover for the partition and then click Next. 4.

  • Page 34: Verifying Advanced Control Path Failover

    Procedure 1. When basic control path failover is enabled, the library is presented as LUN 0 on its own world-wide node name. 2. When basic control path failover is NOT enabled, the library is presented as LUN 1 on the drive world- wide node name.

  • Page 35: Data Path Failover Configuration

    • The HPE MSL6480 LTO-5&6 Control Path (CtrlP) Failover license or the HPE MSL3040 Ctrl Failover license has been added to the library. •...

  • Page 36: Verifying Data Path Failover

    Procedure 1. From the Configuration area, click Expert Wizard in the Partitions menu. 2. Select the partition to be configured and then click Next until the wizard displays the Select Data Path Failover Settings screen. 3. For example, Figure 7: Enabling data path failover on page 36 shows advanced data path failover enabled for drives 1 and 2.

  • Page 37: Configuring Failover For Other Msl Tape Libraries

    Configuring failover for other MSL Tape Libraries The MSL2024, MSL4048, MSL8048, and MSL8096 tape libraries with dual-port LTO-5 or LTO-6 FC tape drives support basic data path failover. The MSL2024, MSL4048, MSL8048, and MSL8096 tape libraries with multiple LTO-5 or LTO-6 FC tape drives support basic control path failover.

  • Page 38: Verifying Data Path Port Failover

    Figure 8: Enabling data path port failover Verifying data path port failover Procedure 1. Navigate to the Drive > Status screen. 2. Verify that status of one of the ports is Login complete and the other is Standby. 3. Note the status of each port. 4.

  • Page 39: Making The Standby Port Be The Active Port

    Figure 9: Standby and active ports After verifying that the configuration change was successful, verify that the hosts with access to the tape drive are still able to communicate with the drive. After verifying host access via the initial path, force a data path port failover by disconnecting the cable from the active port on the drive or using an FC switch management interface to down the port connected to the tape drive.
  • Page 40 Procedure 1. Navigate to the RMI Configuration > Drive screen. 2. For each tape drive that will be configured for control path failover, configure the Port Type as Fabric (N/F) if necessary. 3. Navigate to the RMI Configuration > System screen. 4.

  • Page 41: The "Enable Library Control Path Failover" Setting Is Not Selectable

    Figure 11: Configure library, basic control path failover configuration disabled In Figure 12: Configure library, basic control path failover configuration available on page 41 the configuration requirements for enabling basic control path failover have been met and the library has made the option for Enable Library Control Path Failover selectable as well as providing a selection for the “Alternate Drive for Library Control Path.”...

  • Page 42: Verifying Basic Control Path Failover

    Action Verify that the library or logical library meets the prerequisites for the number, type, and configuration of tape drives. Verifying basic control path failover After enabling basic control path failover, verify the configuration of both paths. After verifying library connectivity using each of the library control paths the library control path may be moved back to the original drive if so desired by using the Procedure 1.

  • Page 43: Installing And Using Windows Advanced Path Failover Drivers

    Installing the Windows advanced path failover drivers Prerequisites • Windows Installer version 4.5 or later • Windows driver for the HPE LTO-6 tape drive • Windows driver for the tape library Procedure 1. Locate the drivers on the Hewlett Packard Enterprise website: a.

  • Page 44: The Windows Installer Reports Error 0X80070643

    NOTE: The installation requires Windows Installer version 4.5 or later. If it is not present, the installer reports the following errors: • Error 0x80070643: Failed to install MSI package • Error 0x80070643: Failed to execute MSI package. • Error 0x80070643: Failed to configure per-machine MSI package. •...

  • Page 45: Uninstalling The Drivers

    http://www.microsoft.com/en-us/download/details.aspx?id=8483 Uninstalling the drivers Procedure 1. Select Start > Programs > Control Panel. 2. Select Advanced Failover Drivers entry, and then click Uninstall/Change. 3. Follow the prompts to complete the driver removal process. Verifying that the tape and changer drivers are correctly installed Procedure 1.

  • Page 46: Windows Driver Theory Of Operation

    Table 2: Application path list Addressed Device Path Port Example Logical Unit Logical Unit Handle Worldwide Identifier Tape drive 1 TAPE0 Active Port A 50:01:10:a0:00:00:00:01 Standby Port B 50:01:10:a0:00:00:00:01 Tape drive 2 TAPE1 Active Port A 50:01:10:a0:00:00:00:03 Standby Port B 50:01:10:a0:00:00:00:03 Library CHANGER0 Active...
  • Page 47 Figure 13: Driver and system organization Storage bus filter driver The storage bus filter driver is named HPtapeFailover_filt and manages the OS notifications indicating that devices have been added or removed. The storage bus filter driver bus enumerator is usually "PCI". It attaches as an upper filter to all HBA drivers. It then monitors the creation of raw devices, looking for supported failover capable devices.
  • Page 48 Multi-path intermediate class driver The intermediate class (IC) driver, HPtapeFailover_mpio, has two halves. The upper half is a virtual bus (VB) driver. This VB driver provides a virtual device which manages the paths to all of the devices that support failover. The lower half is a multi-path function driver for the devices using the hardware ID created by the lower-level filter driver.
  • Page 49 Figure 14: Drivers and device objects Installing and using Windows advanced path failover drivers...
  • Page 50 Device manager view Figure 15: Device manager window on page 50 shows the configured failover path instances in the Windows Device Manager. Figure 15: Device manager window NOTE: A number of devices have been removed from this view to improve readability. In the system shown in Figure 16: Library configuration example on page 51, the library has two tape drives and each tape drive has two primary ports attached to a different switch.

  • Page 51: Device Firmware

    Each physical device appears once in the Device Manager. Under Tape drives there are two instances of Hewlett Packard Enterprise LTO Ultrium 6 drive and under Medium Changer devices there is one instance of HPE ESL G3 Tape Library. Device firmware These two Windows drivers work in conjunction with firmware in the library and tape devices.

  • Page 52: Installing And Using Linux Advanced Path Failover Drivers

    Linux will not operate properly in other revisions. See the most recent release notes to find out which RPM file to use for the Linux operating system that is running on the server. a. Navigate to http://www.hpe.com/support/hpesc. b. Enter ESL G3 (for ESL G3), MSL3040 (for MSL3040), or MSL6480 (for MSL6480), and then click c.

  • Page 53: Updating The Driver Without Rebooting

    the application software. See the host application software user guide for instructions on configuring the block size. Updating the driver without rebooting Procedure The advanced path failover driver may be updated without rebooting the system by first removing the existing drivers and then loading the new version. Verify that no applications have devices open that are using the advanced path failover drivers and then use rpm -U <filename>.rpm to update the drivers.

  • Page 54: Full Balancing Algorithm

    Full Balancing algorithm When a device file is opened to a tape drive, the driver determines the number of open device files to tape drives using the HBA of the last known good path. The driver selects a path on an HBA that is in use by the fewest number of open tape drive device files.

  • Page 55: Viewing The Current Driver Revision

    path by replacing the device identifier with the identifier from the sg or st device. For example, a command executed on pfo3 will report information for the device at sg3 and st3. Viewing the current driver revision The driver revision number indicates the build date of the driver and can be viewed by running: cat /proc/scsi/sg/version Viewing device status You can view the status of a device that is controlled by the failover driver by reading a file in the /sys file...

  • Page 56: Setting The Preferred Path

    1:0:0:1 active_drive 1:0:1:1 1:0:2:1 active_drive 1:0:3:1 sg=/dev/sg2 st=/dev/st1 wwnn=50014382c6c2f007 type=tape 0:0:1:0 wwpn=50014382c6c2f008 0:0:2:0 open - wwpn=50014382c6c2f009 1:0:1:0 wwpn=50014382c6c2f008 1:0:3:0 wwpn=50014382c6c2f009 In this example, the tape drive at the top of the list can be accessed via either /dev/sg0 or /dev/st0. The other tape drive is available via either /dev/sg2 or /dev/st1.

  • Page 57: Path Rotation Exercise Function

    The balancing process starts by placing each drive on its preferred path, if one has been assigned. It will then balance the paths for any drives that do not have a preferred path. The command will balance paths even if there are sessions established with the tape drives. To balance the tape drive paths: echo rebalance >...
  • Page 58 candidate for failover. If the device is a candidate for failover, the driver determines the serial number (SN) or worldwide name (WWN) of the device. If the device is capable of advanced path failover, the driver determines whether failover is enabled for the device. If the device supports advanced failover and failover is enabled, the driver masks all duplicate paths and presents a single path to application clients.

  • Page 59: Installing And Using Hp-Ux Advanced Path Failover Drivers

    Installing and using HP-UX advanced path failover drivers Advanced path failover for HP-UX is implemented by updating HP-UX drivers to support advanced path failover with the LTO-6 tape drives. The drivers function as both failover and non-failover drivers. The updated drivers are: •...

  • Page 60: Commands For Viewing Tape And Library Devices Connected To A System

    Commands for viewing tape and library devices connected to a system You can use ioscan to view the tape and library (media changer) devices connected to the HP-UX host. The device special file (DSF) is listed as the last item in the description as shown in bold type. Using ioscan (1M) to view tape devices # ioscan -knNfC tape Class...
  • Page 61 To find this information with HP-UX commands, use ioscan -knNfC autoch to see the list of tape libraries, and then use ioscan -m lun -H <H/W path> for the partition. For example, if the LUN hardware path for the library is 64000/0xfa00/0x12: # ioscan -m lun -H 64000/0xfa00/0x12 Class Lun H/W Path...

  • Page 62: Finding The Lockdown Path

    tape29_BESTn /dev/rtape/tape29_BESTnb <— Tape device special files Finding the lockdown path Procedure 1. The load-balance policy used to route data on multiple paths to a tape drive or library is called the "path-lockdown" policy. Use the scsimgr get_info command to see the current lockdown path for a library.
  • Page 63 • On the HP-UX host, run rmsf -H on the lunpath hardware paths that are in NO_HW state. For example: rmsf –H 0/4/0/0/0/1.0x50014380023560d4.0x1000000000000 • Run ioscan -kfNH <HBA path>. For example: ioscan -kfNH 0/4/0/0/0 Hewlett Packard Enterprise recommends only enabling or disabling advanced path failover when the library is not open by any applications.

  • Page 64: Troubleshooting Failover Operation

    Troubleshooting failover operation Cause To find diagnostic information about the operation of basic and advanced path failover: • Examine the library event log or RAS tickets. See Library path failover events on page 75 and Additional tape drive sense codes on page 77. •...

  • Page 65: Windows Debugging Logs And Tools

    • Powered-off switches • Failed host bus adapter ports The first sign of a path failure, such as a disconnected Fibre Channel cable or a failed switch, is often an alert or warning reported by the library in the web interface and event log. Failure of a single path to a drive should not interfere with operation of most backup applications, and might go unnoticed.

  • Page 66: Confirming Failover Operation

    Confirming failover operation To confirm that the advanced path failover drivers have installed and are operating correctly, open the system event viewer. See Driver components on page 46 for instructions on how to filter out irrelevant events. The following events should be present; the first event in this list will be the first to occur after system restart: HPtapeFailover_filt Path failover driver loaded...

  • Page 67: Diagnostic Application

    Event Severity Message Failover session established Informational Failover session established on SCSI Port %2 SCSI Bus %3 Target Id %4 Logical Unit %5 Failover session establishment Error Failover session establishment error error on SCSI Port %2 SCSI Bus %3 Target Id %4 Logical Unit %5.
  • Page 68 C:\Program Files\Hewlett-Packard\Advanced Failover Drivers\Utils or C:\Program Files (x86)\Hewlett-Packard\Advanced Failover Drivers\HPAdvFoDgn. The application consists of two files, HPAdvFoDgn.exe and HPtapeFailover_mpio.dll. Operation The diagnostic application is started by double-clicking its icon. It displays a window similar to the window shown in Figure 17: Advanced failover diagnostic application on page 68. The window contains four panes: Figure 17: Advanced failover diagnostic application The Devices pane lists the tape drives and media changers that are associated with the path failover...
  • Page 69 paths to the SMC device server. All other paths are passive, i.e., they pass through a passive control path drive (see Active and passive control path drives on page 14). If the selected device is a tape drive, the capital A indicates the active data path, and there will be no lower case a.
  • Page 70 Figure 19: Report Device menu item Table 4: Device information Menu Item Data Enabled Reports whether advanced path failover is enabled for the SSC device server (i.e., for the tape drive data path), and for the SMC device server (i.e., for the media changer controller path) Session Status Expected FSC: A command indicator used for management of commands that...
  • Page 71 Table 5: Local SMC device server information Menu item Data Legacy SET: 1: An initiator has a legacy reservation established. Reservations 0: No initiator has a legacy reservation established. NOIV: 1: The following fields are valid. 0: The following are not valid and should be ignored.
  • Page 72 The Clear Nexus Settings action is used to clear legacy and persistent reservations placed on a changer device. This can be used to recover from the loss of a host that has placed a reservation on the changer. If an application is reporting “Reservation Conflict” errors when it attempts to access the changer device or “Medium Removal Prevented”...

  • Page 73: Diagnostic Dumps

    Figure 24: Enable Logging dialog The Enable selection immediately begins capturing driver diagnostic information after OK is clicked. The Enable setting is not persistent across a system reboot. If the diagnostic information during a reboot is desired, select Continue after reboot . In the Log Files Location field, enter or use the … button to designate a local directory for log files.

  • Page 74: Linux Logs And Troubleshooting Tools

    Memory dump setup To configure Windows to produce a memory dump, see http://support.microsoft.com/kb/254649. The configuration process includes specifying the name and location for the dump file, as well as the type of the dump. The type should be a kernel memory dump, although the larger complete memory dump is acceptable.

  • Page 75: Reading The Trace Log

    Procedure 1. To minimize the level of debug messages: echo 0x0000 > /sys/bus/scsi/drivers/pfo/debug_flag 2. To maximize the level of debug messages: echo 0xffff > /sys/bus/scsi/drivers/pfo/debug_flag Increased debug logging will affect performance. 3. To set the default level of debug messages: echo minimum >...
  • Page 76 Table 7: MSL3040 or MSL6480 events related to path failover Event Message and description Details and solution code 4037 Loss of redundant data path. Verify that both FC ports are correctly cabled to the SAN. 4038 The drive configuration failed because of Advanced path failover, ADPF and ACPF, unsupported ADPF features selected.

  • Page 77: Additional Tape Drive Sense Codes

    Event Message and description Details and solution code 4057 Passive control path drive not available for Verify that the configured control path control path failover. failover drive is present, powered on, and ready to accept the control path. 4058 Disabling active control path drive caused If the failover is unplanned or unexpected, failover to passive one.
  • Page 78 Because these ASCs may be visible in device logs and diagnostic tools, they are listed in the table below. Table 9: Advanced failover vendor specific additional sense codes ASCQ Description Meaning FAILOVER Failover is enabled but the device driver has not SESSION opened a failover capable connection to the device.

  • Page 79: Advanced Troubleshooting Techniques

    Generating a driver debug dump log file requires installing checked drivers and the DebugView application. Procedure Navigate to the Hewlett Packard Enterprise technical support website (http://www.hpe.com/ support/storage) and then download drivers for the host with debug capability enabled. Navigate to the support website and then download drivers for the host with debug capability enabled.
  • Page 80 Restart the system after updating the registry so the changes will take effect. Navigate to http://technet.microsoft.com/en-us/sysinternals/bb896647 and then download DebugView. Unzip the files to a local folder. There is no installer. 10. Run DebugView and configure it to capture Kernel-Mode debug output by selecting Capture > Capture Kernel (Ctrl+K).

  • Page 81: Support And Other Resources

    Support and other resources Accessing Hewlett Packard Enterprise Support • For live assistance, go to the Contact Hewlett Packard Enterprise Worldwide website: http://www.hpe.com/assistance • To access documentation and support services, go to the Hewlett Packard Enterprise Support Center website: http://www.hpe.com/support/hpesc Information to collect •...

  • Page 82: Customer Self Repair

    IMPORTANT: Access to some updates might require product entitlement when accessed through the Hewlett Packard Enterprise Support Center. You must have an HPE Passport set up with relevant entitlements. Customer self repair Hewlett Packard Enterprise customer self repair (CSR) programs allow you to repair your product. If a CSR part needs to be replaced, it will be shipped directly to you so that you can install it at your convenience.

  • Page 83: Regulatory Information

    Documentation Feedback (docsfeedback@hpe.com). When submitting your feedback, include the document title, part number, edition, and publication date located on the front cover of the document. For online help content, include the product name, product version, help edition, and publication date located on the legal notices page.

  • Page 84: Known Issues And Workarounds

    4. Download the latest Advanced Failover Drivers for Windows Server 2012 from the Hewlett Packard Enterprise website. a. Navigate to http://www.hpe.com/support/hpesc. b. Enter ESL G3 (for ESL G3) or MSL6480 (for MSL6480), and then click Go. c. In the Results, select your library.

  • Page 85: Device Connectivity Is Lost After Several Closely Spaced Path Failovers

    Device connectivity is lost after several closely spaced path failovers Symptom If several closely spaced path failures occur on all of the available paths, the operating system might not detect a path change and report that to the driver causing a loss of connectivity with the device. Cause The current implementation is failure tolerant only and not intended to fix unstable SAN environments.

  • Page 86: A Host In A Multi-Initiator Environment Does Not Discover A Path To The Library Controller

    Action If a particular path is preferred, load the HBA for that path in the lower numbered hardware location. A host in a multi-initiator environment does not discover a path to the library controller Symptom A host in a multi-initiator environment does not discover a path to the library controller when it is booted or the devices are rescanned when another initiator is using the library.
  • Page 87 Action 1. Clear the stale settings using the Windows diagnostic application from Actions > Clear Nexus Settings. 2. Clear the stale settings from the ESL G3 GUI. Navigate to Tools > Drives and then click Remove IT Nexus. 3. Use the library GUI to power-cycle the tape drive hosting the library controller and then clear persistent reservation settings using the application that established the settings.

  • Page 88: Data Protector Device Discovery With Advanced Path Failover

    Data Protector device discovery with advanced path failover When using the Data Protector Autoconfigure functionality, Data Protector will discover both active and passive control and data paths to the library robot control and drive paths respectively. Data Protector will associate all active data paths with the active control path, and can be identified by the library in the list that includes the selection box.
  • Page 89 Data Protector device discovery with advanced path failover...

  • Page 90: Troubleshooting Commvault Simpana Device Discovery With Hp- Ux 11.31

    The APF drivers do not support Commvault Express. For supported versions of Commvault Simpana, see the Design Guide for Backup and Archive on the Backup, Recovery and Archive website: http://www.hpe.com/storage/daprcompatibility root@ssdcl197 [/opt/simpana/Base]# ioscan -knfC autoch Class I H/W Path...
  • Page 91 configure into Commvault. For HP-UX, select the path of the virtual device for the library controller and ignore the others. # ioscan -knfNC autoch root@ssdcl197 [/]# ioscan -knNfC autoch Class I H/W Path Driver S/W State H/W Type Description =================================================================================== autoch 4 64000/0xfa00/0x9 eschgr CLAIMED DEVICE HP ESL G3 Series /dev/rchgr/autoch4 The same set of paths is displayed in the Commvault GUI.

This manual is also suitable for:

Storeever lto-6

Table of Contents