HP StoreEver Tape Libraries Failover User Guide (5697-3323, June 2014)
Table Of Contents
- HP StoreEver Tape Libraries Failover User Guide
- Contents
- 1 Overview
- 2 Enabling basic path failover
- 3 Installing advanced path failover
- 4 Preparing the switches and hosts for failover
- 5 Configuring failover for the HP StoreEver ESL G3 Tape Libraries
- 6 Configuring failover for HP StoreEver MSL6840 Tape Libraries
- 7 Configuring failover for other HP StoreEver MSL Tape Libraries
- 8 Installing and using Windows advanced path failover drivers
- 9 Installing and using Linux advanced path failover drivers
- 10 Installing and using HP-UX advanced path failover drivers
- 11 Troubleshooting failover operation
- 12 Advanced troubleshooting techniques
- 13 Support and other resources
- A Data Protector device discovery with advanced path failover
- Index
12 Advanced troubleshooting techniques
The techniques in this chapter assume an advanced level of experience.
Windows driver debug dump setup
Generating a driver debug dump log file requires installing checked drivers and the DebugView
application.
Drivers with debug capability are available from HP technical support (http://www.hp.com/
support).
1. Uninstall the release drivers as explained in “Uninstalling drivers” (page 36).
2. In Windows 2008 or 2012 systems, place the system in Test Mode by opening a command
window and entering the command bcdedit testsigning on and then restarting. After
restarting, the desktop will display Test Mode in the lower right. If this step is not done, then
after installing a checked driver, the system will boot into Recovery Mode. If the bcdedit
command is not recognized, it is not required for that system.
For further details, see:
http://msdn.microsoft.com/en-us/library/windows/hardware/ff553484(v=vs.85).aspx
3. Configure the location and type of the debug output to save a kernel dump in a known location.
A kernel dump is preferred to the much larger complete memory dump.
4. Install the appropriate checked drivers for your operating system using the procedure in
“Downloading and installing the drivers” (page 36). When prompted whether to allow
installation of an unsigned driver, allow installation.
5. In Windows 2008 or 2012 enable the debug print filter by editing the registry:
a. Run a registry editing application (e.g., Regedit.exe) with administrative privileges.
b. Navigate to HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\
Session Manager\Debug Print Filter. You may need to create the key Debug
Print Filter.
c. Add a new sub-key DEFAULT (this is different from the automatically created sub-key
“(Default)”) with type DWORD and set it to 15 (0xF). The registry value can be created
by sending this command from a command window that has been opened with
administrative privileges.
d. As an alternative to steps Step 5.a through Step 5.c, open a command window and issue
the command:
reg add HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\
Session Manager\Debug Print Filter" /v DEFAULT /t REG_DWORD /D
15.
e. Restart the machine after updating the registry for the changes to take effect.
6. Download DebugView from http://technet.microsoft.com/en-us/sysinternals/bb896647 and
unzip the files to a local folder. There is no installer.
7. Run DebugView and configure it to capture Kernel-Mode debug output by checking
Capture→Capture Kernel (Ctrl+K).
8. To capture driver debug messages during boot time, select Capture→Log Boot.
9. Select a file to receive the log with File→Log to File or File→Log to File As....
The help file for DebugView is comprehensive; please refer to that for details. If Help does not
work because the right pane displays Navigation to the webpage was canceled, locate
the dbgview.chm file in the destination folder. Right-click on the file, select Properties, and on
the General Tab on the lower right click Unblock.
Windows driver debug dump setup 63