2.8.3 Intermittent Error Monitoring Actions
Intermittent error monitoring is performed on each path, and it automatically starts as soon as a path is recovered from an error by using the automatic failback function. This subsection describes the following intermittent error monitoring actions: When an intermittent error occurs When an intermittent error does not occur When the conditions for an intermittent error to occur are changed during error monitoring (1) When an Intermittent Error Occurs When an error occurs on a path a specified number of times within a specified interval, the error monitoring will finish and the path is determined to have an intermittent error, upon which the path is removed from those subject to automatic failbacks. The path that is removed will remain in the error status until the online operation is performed. However, if the path satisfies certain conditions (see Figure 2-11: Path Status Transitions), it will be subject to automatic failbacks and change to the Online status. Figure 2-12: Action What Will Happen When an Intermittent Error Occurs on a Path shows what will happen when an intermittent error occurs. For this example, the path is determined to have an intermittent error when the error occurs 3 or more times within 30 minutes. The events that occur are described by using the time arrows. Figure 2-12: Action What Will Happen When an Intermittent Error Occurs on a Path
(2) When an Intermittent Error Does Not Occur If an error does not occur on a path a specified number of times within a specified interval, an intermittent error will not occur. In such a case, the error monitoring will finish when the specified error-monitoring interval finishes, upon which the number of errors is reset to 0. If an error occurs on the path again at a later time, error monitoring will resume when the path is recovered from the error via an automatic failback. If it takes a long time for an error to occur, an intermittent error can be more easily detected by increasing the error-monitoring interval or by decreasing the number of times that the error needs to occur. Figure 2-13: What Will Happen When an Intermittent Error Does Not Occur on a Path shows what will happen when an intermittent error does not occur. For this example, the path is determined to have an intermittent error if the error occurs three or more times in 30 minutes. The events that occur are described by using the time arrows. Figure 2-13: What Will Happen When an Intermittent Error Does Not Occur on a Path

HDLM GUI logs:

\Program Files\HITACHI\DynamicLinkM anager\log\dlmgui[1-2].log
Hitachi Command Suite Common Agent Component logs:
\Program Files\HITACHI\DynamicLinkM anager\log\dlmwebagent[1-n ].log#2
The value n depends on a setting in the file dlmwebagent.properties. Event log
Critical or Error) is collected.
Information about very severe errors (a severity level of
Event log (application log)
You can use administrative tools such as Event Viewer to check these event logs.
#1 For Windows Server 2003 (excluding the x86 edition) and Windows Server 2008 (excluding the x86 edition), Program Files is Program Files (x86). #2 The underlined part indicates the folder specified during the installation. After obtaining these files, be sure to also copy them to a backup location. For details on error levels, see 2.11.2 Filtering of Error Information. Note To collect logs, HDLM uses the Hitachi Network Objectplaza Trace Library service. If this service is not active, start it by doing the following: From Control Panel, choose Administrative Tools and then Services to open the Services window. From the list of services, select Hitachi Network Objectplaza Trace Monitor 2, and then from the Action menu choose Start.
2.11.2 Filtering of Error Information
Errors detected by HDLM are classified into various error levels. Table 2-8: Error Levels lists the error levels, in the order of most to least severe. Table 2-8: Error Levels
Error level Critical Error Warning Information Meaning Fatal errors that may stop the system. Errors that adversely affect the system. This type of error can be avoided by performing a failover or other countermeasures. Errors that enable the system to continue but, if left, might cause the system to improperly operate. Information that simply indicates the operating history when the system is operating normally. Level shown in Event Viewer Error Error Warning Information
Error information is filtered by error level, and then collected. The error information in error logs and in the event log is collected based on the user-defined collection level. The collection levels are as follows: Collection levels for error logs and event logs: The event log always collects error information from the selected error level and higher. The error log can collect information from any of the following levels: Collects no error information. Collects error information from the Error level and higher. Collects error information from the Warning level and higher. Collects error information from the Information level and higher (information from all the levels is collected). Collects error information from the Information level and higher (including maintenance information). Collection levels for log information in trace files: Outputs no trace information Outputs error information only Outputs trace information on program operation summaries Outputs trace information on program operation details

HDLM-installation-folder\bin\dlmprsvkey -v Make sure that the PRSV key displayed by the dlmprsvkey utility is unique among all the other hosts in the SAN. If the PRSV key is not unique or is not registered, or if the KAPL09131-W message appears, execute the dlmprsvkey utility with the -r parameter specified to re-register the PRSV key. If the PRSV key is not registered, the HDLM functions might not properly operate. For details about the dlmprsvkey utility, see 7.4 The dlmprsvkey Utility for Registering an HDLM Persistent Reservation Key. If you used a license key file, it will be deleted after the installation finishes. The KAPL09115-W message will appear if deletion of this file fails. If this happens, delete the file manually. 17. Shut down the host. Leave the host in a single-path configuration until you check (in step 24) whether HDLM has been successfully installed. 18. For all the hosts that make up the cluster system, perform steps 3 to 16. 19. Make sure that all the hosts that make up the cluster system have been completely shut down. 20. Restart each host. 21. Log on to Windows again as a member of the Administrators group. 22. Execute the dlnkmgr command's view operation to display the status of each program: An example of executing the dlnkmgr command's view operation is as follows:
>dlnkmgr view -sys HDLM Version : x.x.x-xx Service Pack Version : Load Balance : on(extended lio) Support Cluster : off Elog Level : 3 Elog File Size (KB) : 9900 Number Of Elog Files : 2 Trace Level : 0 Trace File Size(KB) : 1000 Number Of Trace Files : 4 Path Health Checking : on(30) Auto Failback : on(1) Remove LU : off Intermittent Error Monitor : off HDLM Manager Ver WakeupTime Alive x.x.x-xx yyyy/mm/dd hh:mm:ss
HDLM Alert Driver Ver WakeupTime ElogMem Size Alive x.x.x-xx yyyy/mm/dd hh:mm:ss 128 HDLM Driver Ver WakeupTime Alive x.x.x-xx yyyy/mm/dd hh:mm:ss License Type Expiration Permanent KAPL01001-I The HDLM command completed normally. Operation name = view, completion time = yyyy/mm/dd hh:mm:ss
23. Use the results of the view operation to check the version of the installed HDLM. If x.x.x-xx is displayed in HDLM Version, the correct version of HDLM has been installed. 24. Use the results of the view operation to check that the programs are running properly. If HDLM Manager, HDLM Alert Driver, and HDLM Driver are all Alive, all the programs are running correctly. 25. After the installation finishes, check the path information as described in 3.6 Checking the Path Configuration, and make sure that you have successfully installed HDLM in a single-path configuration. 26. Connect cables to all the HBAs to change the configuration to a multi-path configuration. 27. Check the path information as described in 3.6 Checking the Path Configuration to make sure that you have successfully assembled a multi-path configuration. 28. Shut down the host. 29. For all the hosts that make up the cluster system, perform steps 19 to 27. 30. Restart each host. 31. Install MSCS. 32. Shut down each host after completing the installation of MSCS on it. 33. Restart each host. 34. Log on to Windows again as a member of the Administrators group. 35. Make sure that the program is working normally running properly, by examining the results of the dlnkmgr command's view operation. Make sure that on MSCS is displayed in Support Cluster. An example of executing the dlnkmgr command's view operation is as follows:

18. Modify the storage system settings. Modify the storage system settings by following the procedure described in the maintenance documentation for that particular storage system. 19. Restart each host. 20. Log on to Windows again as a member of the Administrators group. 21. Make sure that the program is running properly, by examining the results of the dlnkmgr command's view operation. Make sure that on MSCS is displayed in Support Cluster. An example of executing the dlnkmgr command's view operation is as follows:
>dlnkmgr view -sys HDLM Version : x.x.x-xx Service Pack Version : Load Balance : on(extended lio) Support Cluster : on MSCS Elog Level : 3 Elog File Size (KB) : 9900 Number Of Elog Files : 2 Trace Level : 0 Trace File Size(KB) : 1000 Number Of Trace Files : 4 Path Health Checking : on(30) Auto Failback : on(1) Remove LU : off Intermittent Error Monitor : off HDLM Manager Ver WakeupTime Alive x.x.x-xx yyyy/mm/dd hh:mm:ss HDLM Alert Driver Ver WakeupTime ElogMem Size Alive x.x.x-xx yyyy/mm/dd hh:mm:ss 128 HDLM Driver Ver WakeupTime Alive x.x.x-xx yyyy/mm/dd hh:mm:ss License Type Expiration Permanent KAPL01001-I The HDLM command completed normally. Operation name = view, completion time = yyyy/mm/dd hh:mm:ss
22. Use the results of the view operation to check the version of the installed HDLM. If x.x.x-xx is displayed in HDLM Version, the correct version of HDLM has been installed. 23. Use the results of the view operation to check that the programs are running properly.
If HDLM Manager, HDLM Alert Driver, and HDLM Driver are all Alive, all the programs are running correctly. 24. After the installation finishes, check the path information as described in 3.6 Checking the Path Configuration, and make sure that you have successfully installed HDLM in a single-path configuration. 25. Connect cables to all the HBAs to change the configuration to a multi-path configuration. 26. Check the path information as described in 3.6 Checking the Path Configuration to make sure that you have successfully assembled a multi-path configuration. (3) When VCS Is Used To install HDLM when VCS is used: 1. 2. 3. 4. 5. 6. Start each host. Start them in a single-path configuration. Use the VCS Configuration Wizard to configure the Cluster components. Restart the hosts. Log on to Windows as a member of the Administrators group. Stop VCS. Save the license key file directly under the Windows installation-destination drive. Also, instead of using the license key file, you can directly specify the license key during the installation of HDLM. installation-drive:\hdlm_license
The license key file will be deleted after the installation finishes. 7. Perform the installation. If you are not performing an unattended installation, insert the DVD into the drive and run the installation program setup.exe. The program checks whether HDLM has already been installed. If HDLM 5.4 or earlier has been installed, the KAPL09129-E message will appear. If this happens, carry out the procedure shown in 3.5.6 Migrating from HDLM 5.4 or Earlier to HDLM 5.5 or Later. If HDLM 5.5 or later has been installed, the KAPL09173-W message will appear. If this happens, carry out the procedure shown in 3.5.5 Upgrade Installation or Re-installation of

The default of the HDLM management-target device is the same as that before the upgrade installation or re-installation. For example, if you select EMC Symmetrix DMX Series, CLARiiON CX Series when you installed HDLM for the first time, EMC Symmetrix DMX Series, CLARiiON CX Series will already be selected when it appears in the dialog box. Note: If you want to install all HDLM components on a host on which the HDLM Core components have been installed, use an unattended installation. When you install HDLM without using the unattended installation option, only the HDLM Core components, which were already installed in the previous environment, will be installed. For details about unattended installations, see 7.7 The installhdlm Utility for Installing HDLM.
3.5.6 Migrating from HDLM 5.4 or Earlier to HDLM 5.5 or Later
To upgrade from HDLM 5.4 or earlier: 1. Copy the following files to any location other than the HDLM installation folder.
dlmmgr.xml is a file that specifies information needed to run HDLM managers. dlmwebagent.properties is a file that specifies information needed for linkage with Global Link Manager. dlmwebagent.properties only exists in
HDLM 05-02 or later. If you migrate to HDLM 5.9.1 or later, you do not need to copy the dlmwebagent.properties file.
\HDLM-installation-folder\config\dlmmgr.xml \HDLM-installation-folder\config\dlmwebagent.properties
Uninstall HDLM by referring to the HDLM manual for the corresponding version. If you uninstalled HDLM 5.4, go to step 3 because you need to delete the HDLM driver setup information files from the system before restarting the host. In other cases, go to step 4.
Do a search for any setup information files (files with the inf file extension) that satisfy all of the following conditions: The file is stored in the following folder:
Windows-installation-folder\inf
The file contains the text dlmfdrv.sys (a driver file). The file has the name oemn.inf (where n is a number). Delete any setup information files that satisfy all of the above conditions. In
addition, delete the files that have the same names as the above files, but with the extension pnf (oemn.pnf). If you do not delete the correct files, the host might not run properly. Before deleting a file, make sure that it satisfies all of the above conditions. 4. 5. Perform a new HDLM installation by following the procedure in 3.5 Installing HDLM. Copy the files copied in step 1 to the following location, and then overwrite the existing files:
Delete the files copied in step 1. Restart the host. When you install HDLM 5.5 or later in an environment where HDLM 5.4 or earlier was installed, DLMAlertDriver is displayed in the Non-Plug and Play Drivers area of the Device Manager window. You can delete DLMAlertDriver by using the procedure below. Note, however, that leaving DLMAlertDriver on the window will not affect HDLM operations: 1. 2. 3. 4. 5. From the Device Manager window, in the View menu, choose Show hidden devices. From the View menu, choose Devices by connection. Select Non-Plug and Play Drivers to display DLMAlertDriver. Delete DLMAlertDriver. Restart the system.

A Dev number. A 0 is displayed for a Dev that takes up the entire LU. This is the same as the DNum that is displayed by the view operation. For details on the view operation, see 6.7 view (Displays Information).

HDevName

The name of the host device. A drive letter is used. If no drive letter has been assigned, a hyphen (-) will be
displayed. This is the same as the HDevName that is displayed by the view operation. For details on the view operation, see 6.7 view (Displays Information).
5.3 What To Do for a Path Error
When a path error is detected by HDLM, you must immediately resolve the error and restore the path. A path error check is performed every time an I/O is issued, or the Windows plug-and-play functionality detects that a path is disconnected. If there are any paths through which I/Os are not normally issued, such as a non-owner path, you should enable path health checking in order to detect any possible errors. For details about path health checking, see 2.9 Detecting Errors by Using Path Health Checking. When a path error is detected, HDLM performs a failover on the path and outputs the KAPL08022-E message. This message indicates that an error has occurred in the components that make up the path. Figure 5-1: Error Location When the KAPL08022-E Message Is Output indicates these components. Figure 5-1: Error Location When the KAPL08022-E Message Is Output
Figure 5-2: Troubleshooting Procedure When a Path Error Occurs shows the troubleshooting procedure when the KAPL08022-E message is output.
Figure 5-2: Troubleshooting Procedure When a Path Error Occurs
The following shows the procedure for using the HDLM command (dlnkmgr) to handle a path error.
5.3.1 Examining the Messages
Examine the messages that are output to the host event log. If the KAPL08022-E message is output, view the message to check the path in which the error has occurred. For details on each item displayed in messages, see 5.2 Checking Error Information in Messages. If errors have occurred on all the paths to an LU, the KAPL08022-E message will appear, in addition to the KAPL08026-E message. When using the LU dynamic deletion function, the KAPL05301-E message will appear if all the paths are deleted.
5.3.2 Obtaining Path Information
Obtain path information to narrow down the hardware in which an error has occurred. Execute the following command:
>dlnkmgr view -path -iem -hbaportwwn > pathinfo.txt
pathinfo.txt is the redirection-output file name. Use a file name that matches your

environment.

5.3.3 Identifying the Error Path
Check the obtained path information to find the path with the error. In the Status column, the error path has the status Offline(E) or Online(E).

Command format

Enter the command using the following format: dlnkmgr operation [parameter [parameter-value]]

dlnkmgr

The command name. operation The type of operation entered after dlnkmgr. parameter A value required for an operation. parameter-value A value required for an operation parameter.
Operations of the dlnkmgr command
Table 6-1: Operations of the dlnkmgr Command shows the operations of dlnkmgr and their functions. Table 6-1: Operations of the dlnkmgr Command

Operation

Functions Initializes (0) the statistics (I/O count and I/O errors) of all paths managed by the HDLM system. For details, see 6.2 clear (Returns the Path Statistics to the Initial Value). Displays the format of the operations used for HDLM. For details, see 6.3 help (Displays the Operation Format). Places offline an online path or paths. For details, see 6.4 offline (Places Paths Offline). Places online an offline path or paths. For details, see 6.5 online (Places Paths Online). Sets the HDLM operating environment. For details, see 6.6 set (Sets Up the Operating Environment). Displays HDLM program information, path information, LU information, and HDLM management-target device information. For details, see 6.7 view (Displays Information).

offline online set

If you are using Windows Server 2003, execute HDLM commands as a member of the Administrators group. If you are executing HDLM commands in Windows Server 2008, see 4.1.6 Using Windows Server 2008. To specify a value that contains a space in its parameter, enclose the entire value in double quotes (").
6.2 clear (Returns the Path Statistics to the Initial Value)
The dlnkmgr command's clear operation clears the statistics (I/O count and I/O errors) of all paths that are managed by HDLM, and returns them to their initial value.

6.2.1 Format

(1) To Set the Path Statistics to 0

dlnkmgr clear -pdst [-s]

(2) To Display the Format of the clear Operation

dlnkmgr clear -help

6.2.2 Parameters
Clears statistics (I/O count and I/O errors) of all paths managed by HDLM to the initial value (0). Example
>dlnkmgr clear -pdst KAPL01049-I Would you like to execute the operation? Operation name = clear [y/n]:y KAPL01001-I The HDLM command completed normally. Operation name = clear, completion time = yyyy/mm/dd hh:mm:ss > -s
Executes the command without displaying a message asking for confirmation of command execution from the user. Specify this parameter if you want to skip the response to the confirmation message: for example, when you want to execute the command in a shell script or batch file. Example

Table 6-12: Items That Can Be Selected by the -path -item Parameter and the Sub-parameters

Selectable items

PathID# PathName HBAPortWWN DskName iLU ChaPort Status# Type IO-Count IO-Errors DNum HDevName IEP

Sub-parameters None

pn hbaportwwn dn lu cp

type ic ie dnu hd iep

# Because both PathID and Status are always displayed, you do not have to specify any parameters. In the sub-parameters following -path -item, you can list the paths (-hdev) and sort the list (-srt). If you omit both parameters, the command displays information for all the paths in ascending order of AutoPATH_IDs. These sub-parameters are:
Displays information only for the paths accessing the specified host device. Specify a drive letter to indicate the desired host device. You cannot specify the host device unless a drive letter has been assigned. The host-device-name string is case sensitive. When you specify this parameter, HDevName is displayed by default. It is not
necessary to specify hd for the -item parameter. If the command ends with the KAPL01064-W or KAPL01013-E message, follow the recommended action in the message.
Use this parameter for the Thunder 9500V series, Lightning 9900 series, Lightning 9900V series, Hitachi USP, Hitachi AMS2000/AMS/WMS/SMS series, Universal Storage Platform V/VM, or Virtual Storage Platform to display the model ID of the storage system in the product ID element of the DskName field. When this parameter is omitted, the command displays the product ID or emulation type of the storage system instead. For details about the information to be displayed for product IDs, see Table 6-15: Product ID Displayed by the View -path Operation. When you use this parameter, DskName is displayed by default. It is not necessary to specify dn for the -item parameter.
Use this parameter to sort the path information in ascending order, according to the specified sorting key. The sorting keys are as follows: the first sorting key is the name of the storage system (DskName), the second sorting key is the value specified by the -srt parameter, and the third sorting key is AutoPATH_ID. The parameter values available to specify the second sorting key are: pn: Path name lu: LU number of the storage system cp: Port number of the channel adapter When the -srt parameter is omitted, the path information is listed in order of ascending AutoPATH_IDs. When you use this parameter, the items used for the sorting keys (DskName, AutoPATH_ID, and the item specified by this parameter) are displayed by default. Therefore, it is not necessary to specify these items for the -item parameter.
When an HDLM management-target device is in the EMC DMX series, EMC CX series, or HP EVA series: If this parameter is specified, all 32 digits of the iLU are displayed instead of truncating the iLU to 13 digits. If this parameter is not specified, any characters after the 13th digit of the iLU of the EMC

Details The system could not access the HDLM manager when the Option window was started up or the Set Option Information operation was executed. aa.aa: Get Option Information or Set Option Information Action Execute the view operation of the HDLM command (dlnkmgr) to check whether the HDLM manager has started. If the HDLM manager has not started, start the HDLM manager, and then restart the HDLM GUI. For details on the view operation, see 6.7 view (Displays Information).

KAPL02011-I

Would you like to execute the aa.aa operation? [OK/Cancel]
Details This is a confirmation for execution. If you want to execute the operation, click OK. To cancel the operation, click Cancel. aa.aa: Clear Data Action
If you want to execute the operation, click OK. To cancel the operation, click Cancel.

KAPL02012-I

aa.aa has started.
Details aa.aa: Operation (character string) Export CSV Set Option Information Refresh Online Offline Clear Data Action None.

KAPL02013-I

aa.aa has completed successfully.
Details aa.aa: Operation (character string) Export CSV Define Option Information Refresh Clear Data Action None.

KAPL02014-W

No data has been input in aa.aa.
Details Nothing has been entered into the input field of the Option window. aa.aa: Input item (character string) Path Health Checking Interval Auto Failback Checking Interval
Error Log File Size Monitoring Interval Number of times Error Log Number of Files Trace File Size Trace Number of Files Action Data has not been input for the specified item. See the HDLM GUI Help to specify a number within the valid range.

KAPL02015-W

A value which is not a number has been input in aa.aa.
Details A character other than a numeric character has been entered in the input field of the Option window. aa.aa: Input item (character string) Path Health Checking Interval Auto Failback Checking Interval Error Log File Size Monitoring Interval Number of times Error Log Number of Files Trace File Size Trace Number of Files Action Specify a number for the item.

KAPL02016-W

A value which is outside of the valid range has been input in aa.aa.
Details The entered value for the input field of the Option window is not within the valid range. aa.aa: Input item (character string)
Path Health Checking Interval Auto Failback Checking Interval Error Log File Size Monitoring Interval Number of times Error Log Number of Files Trace File Size Trace Number of Files Action See the HDLM GUI Help to specify a number within the valid range.

KAPL02017-I

The currently selected paths will be changed to the Online status. Is this OK? [OK/Cancel]
Details The currently selected paths will be changed to the Online status. If you want to continue, click OK. If you do not want to proceed, click Cancel. Action If you want to execute online processing, click OK. To cancel online processing, click Cancel.

KAPL02063-W

The version number cannot be displayed.
Details The version number could not be acquired because an attempt to read a parameter file, which starts up the HDLM GUI, failed. Action The version number cannot be displayed, but HDLM GUI operations can be executed. If you want to display the version number, reinstall HDLM.

KAPL02064-W

KAPL02065-W
The getting PathInformation has been stopped because the configuration of paths was changed during the processing of the getting PathInformation.
Details Updated path information could not be acquired because the path configuration was changed after an Offline, Online, or Clear Data operation was performed. Action After confirming that the paths are not currently being reconfigured, click the Refresh button.

KAPL02076-W

An attempt to acquire the HDLM version information failed. Details = aa.aa
The HDLM version information could not be acquired. aa.aa: Code showing the reason for the error Action Re-execute the command. If the same error occurs again, execute the DLMgetras utility for collecting HDLM error information, and then contact your HDLM vendor or maintenance company if there is a maintenance contract for HDLM.

KAPL02077-W

An attempt to acquire the Service Pack version information failed. Details = aa.aa
Details aa.aa: Code showing the reason for the error Action Re-execute the command. If the same error occurs again, execute the DLMgetras utility for collecting HDLM error information, and then contact your HDLM vendor or maintenance company if there is a maintenance contract for HDLM.

KAPL02080-W

All the current trace files will be deleted. Is this OK? [OK/ Cancel]
Details If you choose a value that is less than the current value of the trace file size or number of trace files, all the current trace files will be deleted. To continue the operation, click OK. To cancel the operation, click Cancel. Action If you want to execute the operation, click OK. To cancel the operation, click Cancel.

KAPL02083-I

HDLM GUI is started by the user-specified JRE. aa.aa, bb.bb
Details aa.aa: The user-specified JRE version (character string) bb.bb: Vendor who provided the user-specified JRE (character string) Action None.

KAPL02084-E

An error occurred in HDLM GUI startup processing. HDLM GUI cannot start. Details = aa.aa bb.bb cc.cc
Details During the GUI startup, an error occurred that was plrobably not a result of a user operation. aa.aa: Executed function name (character string) bb.bb: Return value of function (decimal (base-10) number) cc.cc: Information detailing where the failure occurred (character string) Action Re-execute the command. If the same error occurs again, execute the DLMgetras utility for collecting HDLM error information, and then contact your HDLM vendor or maintenance company if there is a maintenance contract for HDLM.

KAPL09222-E

HDLM could not be uninstalled.
Details HDLM could not be uninstalled. Action Contact your HDLM vendor or the maintenance company if there is a maintenance contact of HDLM.

KAPL09223-E

A feature could not be installed. (feature = aa.aa) Contact your HDLM vendor or the maintenance company if there is a maintenance contract of HDLM.
Details You cannot use any features that have not been installed.
aa.aa: Feature that has not been installed If the value of aa.aa is HDLM GUI: The HDLM GUI cannot be used. If Hitachi Command Suite Common Agent Component is used: HDLM cannot be managed from Global Link Manager. If the value of aa.aa is MPIO Setting: An MPIO setting managed by Windows Management Instrumentation (WMI) has not been changed. Action Contact your HDLM vendor or the maintenance company if there is a maintenance contact of HDLM.

KAPL09224-E

A feature could not be uninstalled. (feature = aa.aa)
Details A feature for Hitachi Command Suite Common Agent Component could not be uninstalled. HDLM cannot be managed from Global Link Manager. aa.aa: Feature that could not be uninstalled Action Contact your HDLM vendor or the maintenance company if there is a maintenance contact of HDLM.

KAPL09226-I

An update (QFE) for MPIO has been installed. Driver version = aa.aa Only the HDLM driver will be installed, without overwriting the MPIO driver.
Details If an update (QFE) for MPIO from Microsoft has been installed, the MPIO driver bundled with HDLM will not be installed. aa.aa: Version number of the installed MPIO driver Action None. If you want to install the MPIO driver bundled with HDLM, uninstall the update (QFE) for MPIO, and then install HDLM.

KAPL09253-W

y cannot be specified in the HDLM_core key when all HDLM components are installed.
Details In an environment where all HDLM components have been installed, HDLM cannot be reinstalled or upgraded using the HDLM Core installation option. Action To install HDLM using the HDLM Core installation option in an environment where all the HDLM components have already been installed, uninstall everything and then perform a new installation of HDLM.

KAPL09254-W

The specified folder does not exist.
Details The folder specified with the -w parameter of the uninstallhdlm utility for installing HDLM does not exist. Action Check the path name of the specified folder.

KAPL09255-W

HDLM has already been uninstalled.
Details The uninstallation stopped because HDLM has already been uninstalled. Action None.

KAPL09256-E

No search paths have been specified for the Path system environment variable. Add the search paths that were specified during the installation of Windows, and then re-install HDLM.

obtaining path information 201 program information 203 offline 26, 214 offline(C) status 31 offline(E) status 31 offline(P) status 32 online 26, 220 online status 30 online(E) status 31 online(EP) status 31 online(P) status 30 operating environment 225 setting 225
view [view operation] 249 operation name 316 operations 208 displaying format 212 of the HDLM command 208 Oracle RAC note 85 organization of this manual i overview command 208 HDLM 1 owner controller 21, 460 owner path 21, 460
Product ID displayed by the view -path operation 267 program configuration 16 program error what to do for 203, 204 program information obtaining 203 PRSV key 297
related publications ii related Software notes on 84 Remove LU 461 reservation 461
P 10, 13 path 9, 11, 460 checking the configuration 140 path error handling 200 Path Health Checking 41 path health checking 4, 41, 230, 460 path information obtaining 201 path name 460 path status transition 30 path status transitions 32 path switching automatically 26 manually 29 PathID 198 PathName 198 paths to which load balancing is applied 21 Performance 183 Performance Monitor 183 Performing Failovers and Failbacks Using Path Switching 26 persistent reservation 461 clearing 167 placing a path or paths offline 214 placing a path or paths online 220 Placing the Path Online 202 port 9, 11 product ID 263
SAN (Storage Area Network) 461 SCSI bus number 267 SCSI device 461 SCSI port number 267 serial number 263 service status 316 set 225 setup HDLM 142 integrated traces 154 single path configuration 90, 124 SLPR(Storage Logical Partition) 462 starting HDLM manager 185 statistics 210 clearing to the initial value 210 stopping HDLM manager 185 storage systems 2 notes 78 symbol conventions xii syntax conventions xiii system configuration 9, 11

Target Id 267

TB meaning xiv term in message 316 trace file 45 trace file size 229 trace level values 229 types of collected logs 45 types of error information 45
what is HDLM? 2 what to do for program error 203, 204 Windows notes on 80 use in non-English Windows system xiv
unattended installation 92 notes on 93 uninstallation HDLM 158, 159 uninstallhdlm 313 uninstalling Hitachi Network Objectplaza Trace Library (HNTRLib2) 165 upgrade installation or re-installation of HDLM 134 using Windows administrative tool (Performance) checking path information 183 utilities for checking HDLM installation information 301 for checking HDLM paths 299 for clearing HDLM persistent reservation 294 for collecting HDLM error information 286 for registering a HDLM persistent reservation key 297 for uninstalling HDLM 313 installing HDLM 303 overview 284 utility for uninstalling HDLM 313

HDLM supports the following storage systems. Hitachi AMS2000/AMS/WMS/SMS series Hitachi USP
Thunder 9500V series Lightning 9900V series Universal Storage Platform V/VM Virtual Storage Platform

1.2 HDLM Features

HDLM features include the following: The ability to distribute a load across multiple paths. This is also known as load balancing. When a host is connected to a storage system via multiple paths, HDLM can distribute the load across all the paths. This prevents one, loaded down path from affecting the processing speed of the entire system. For details on load balancing, see 2.6 Distributing a Load Using Load Balancing. The ability to continue running operations between a host and storage system, even if there is a failure. This is also known as performing a failover. When a host is connected to a storage system via multiple paths, HDLM can automatically switch to another path if there is some sort of failure in the path that is currently being used. This allows operations to continue between a host and a storage system. For details on performing failovers, see 2.7 Performing Failovers and Failbacks Using Path Switching. The ability to bring a path that has recovered from an error back online. This is also known as performing a failback. If a path is recovered from an error, HDLM can bring that path back online. This enables the maximum possible number of paths to always be available and online, which in turn enables HDLM to better distribute the load across multiple paths. Failbacks can be performed manually or automatically. In an automatic failback, HDLM will automatically restore the path to an active state after the user has corrected the problem that exists on the physical path. For details on performing failbacks, see 2.7 Performing Failovers and Failbacks Using Path Switching. The ability to automatically check the status of any given path at regular intervals. This is also known as path health checking. HDLM can easily detect errors by checking the statuses of paths at user-defined time intervals. This allows you to check for any existing path errors and to resolve them promptly and efficiently. For details on setting up and performing path health checking, see 2.9 Detecting errors by using path health checking.
This chapter describes the various functions that are built into HDLM. Before the function specifications are explained though, this chapter will go into detail about the HDLM management targets, system configuration, and basic terms that are necessary to know to effectively operate HDLM. After that, the rest of the chapter focus on describing all the HDLM functions, including the main ones: load distribution across paths and path switching. 2.1 2.2 2.3 2.4 2.5 2.6 2.7 2.8 Devices Managed by HDLM System Configuration LU Configuration Program Configuration Position of the HDLM Driver and hdisk Distributing a Load Using Load Balancing Performing Failovers and Failbacks Using Path Switching Monitoring intermittent errors (functionality when automatic failback is used) 2.9 Detecting errors by using path health checking 2.10 Error management 2.11 Collecting Audit Log Data 2.12 Integrated HDLM management using Global Link Manager 2.13 Cluster support

This sub-section explains these keys. Path priority number This number indicates the priority level set for each path. Priority levels can be set from 1 to 255. The lower the number, the higher the priority. The default is 1. The priority level is set by using OS commands. The following shows an example of the procedure for setting the path priority number. 1. Execute a command that displays the path information for the LU:
# lspath -l hdisk4 -F"name parent path_id connection path_status status" hdisk4 fscsi50060e8005271720,31000000000000 Available Enabled hdisk4 fscsi50060e8005271730,31000000000000 Available Enabled hdisk4 fscsi50060e8005271740,31000000000000 Available Enabled hdisk4 fscsi50060e8005271750,31000000000000 Available Enabled
Execute a command that displays the information for the path whose path priority number you want to set:
# lspath -l hdisk4 -p fscsi0 -w 50060e8005271720,31000000000000 -E scsi_id 0x651400 SCSI ID False
node_name 0x50060e8005271720 FC Node Name False state priority Enabled 1 N/A N/A True True
Execute a command that changes the path priority number:
# chpath -l hdisk4 -p fscsi0 -w 50060e8005271720,31000000000000 -a priority=5 path Changed
Execute a command that displays the information for the path for which a new path priority number has been set:
node_name 0x50060e8005271720 FC Node Name False state priority Enabled 5 N/A N/A True True
Slot number This number indicates the position of the slot where an HBA is mounted. You can find the order of the slot numbers by comparing their physical location code. The following describes how to obtain the physical location code. 1. Execute the following command to find hdisk, based on AutoPATH_ID.
# /usr/DynamicLinkManager/bin/dlnkmgr view -drv PathID HDevName OSPathID LDEV 000000 hdiskhdiskhdiskhdiskhdiskhdisk00001 9500V.0051.0005 9500V.0051.0015 9500V.0051.0020 9500V.0051.0005 9500V.0051.0015 9500V.0051.0020
Execute the following command to find the parent device of hdisk (the HBA device instance).
# lsdev -C -l hdisk4 -F 'parent' fscsi0
Execute the following command to find the physical location code, based on the HBA device instance.

For a new installation, proceed to step 7. 6. If you are upgrading or re-installing HDLM, back up the HDLM settings. If an upgrade installation or re-installation fails, AIX automatically uninstalls HDLM, and the HDLM settings are deleted. Perform this step so that a copy of the HDLM settings is available in this case. If an upgrade installation or re-installation fails, perform a new installation, and then re-execute setup to reflect the settings that have been backed up. Save the HDLM environment settings information.
In the following cases, prepare the license key or the license key file: If you are installing HDLM for the first time If you are upgrading or re-installing HDLM after the licensing term has expired If the directory that contains the license key or the license key file is specified in the installation information settings file, you can use any storage directory name and file name. The following shows examples of when the default storage directory specified in the installation information settings file is to be used:
The license key file or license key is not deleted after the installation. 8. Create an installation information settings file. To use the sample file, copy it from the DVD-ROM to a directory on the hard disk.
# cp -p /cdrom/HDLM_AIX/hdlmtool/instutil/ sample_installhdlm.conf /any-directory
You can change the sample_installhdlm.conf file name. The following shows an example of copying the sample_installhdlm.conf file, and then changing the file name to install_set.conf:
# cp -p /cdrom/HDLM_AIX/hdlmtool/instutil/ sample_installhdlm.conf /any-directory/install_set.conf
For details about how to edit the installation information settings file, which is used by the installhdlm utility, see 7.12.3 Items To Be Defined in an installation-information Settings File. 9. Execute either of the following commands: To execute installux.sh:
# /cdrom/installux.sh -f /any-directory/
installation-information-settings-file To execute installdhlm:
# /cdrom/HDLM_AIX/hdlmtool/instutil/installhdlm -f / any-directory/installation-information-settings-file
Even though a message asking you to restart the host is displayed during installation, you do not have to restart the host. When installation is successful, the KAPL09211-I message is output. During installation, the KAPL09241-W message might be output. In this case, installation of HDLM continues, but installation of HDLM components has failed. After installing HDLM, resolve the problem according to the KAPL09241-W message if necessary. For an upgrade installation or re-installation of HDLM, the configuration of the existing hdisks recognized as HDLM management-target devices is inherited. 10. Unmount the DVD-ROM.
12. Delete the installation information settings file.

18. If GPFS + RVSD was used, delete the setting information from the /etc/vsd/ oemdisktypes.lst file. If HP XP series is used, delete the following line:
19. If GPFS or GPFS + RVSD was used, execute the following utility to set the LUN RESET option to off:
20. If you have been using VCS and have registered VCS scripts, you must delete the VCS script registrations. Delete the following line that was added to the preonline script:
21. If you do not need to start the preonline script when VCS starts, delete the preonline script and specify the settings so that the preonline script does not start. For details on the setting method, refer to the VCS documentation. In the following example, the settings do not start the preonline script when VCS starts:

# # # #

rm /opt/VRTSvcs/bin/triggers/preonline haconf -makerw hagrp -modify service-group PreOnline 0 haconf -dump -makero
22. Execute the following command:
23. Change the boot device list, according to the host environment you are using. If you are not using a virtual I/O server, uninstallation of HDLM is complete and you do not need to perform the remaining steps. 24. If you are using a virtual I/O server, define an hdisk as a virtual target device. On the virtual I/O server, execute one of the following commands: To create an hdisk as a virtual target device
25. Execute the following command in the client logical partition to reconfigure the device:
26. Execute the following command in the client logical partition to check that the physical volume has been recognized as hdisk:
Make sure that the following execution result is displayed:
27. Execute the following command to restore the backed up volume group:
3.14.3 Uninstalling Hitachi Network Objectplaza Trace Library (HNTRLib2)
When you uninstall HDLM, if the KAPL09019-E or KAPL09020-E message is output, follow the directions below to uninstall HNTRLib2. To uninstall HNTRLib2: 1. 2. Log in to AIX as the root user. Execute the following command to unregister the name of the bundled program products.
# /opt/hitachi/HNTRLib2/etc/hntr2cancel "Hitachi Dynamic Link Manager"
Execute the following command.
# /opt/hitachi/HNTRLib2/etc/hntr2setup
The HNTRLib2 setup menu will appear. 4. From the Setup menu, select 9. HNTRLib2 will be uninstalled. If HNTRLib2 is not being used by any other programs: HNTRLib2 will be uninstalled normally, and the following message will appear.

Unsetup is complete.

Make sure that the boot disk is in a multi-path configuration:
Check the current boot disk list:
Specify boot disks that are suitable for your host environment:
Make sure that the number of configured boot disks is the same as the number of paths that you checked in step 2:
# bootlist -m normal -o hdisk10 blv=hd5
hdisk10 blv=hd5 hdisk0 blv=hd5 hdisk1 blv=hd5.
4.5.5 Replacing a Fiber Cable
If there are multiple active paths for an LU, you can replace a desired cable while running your applications by placing offline only the path that goes through the cable to be replaced and using other paths to continue access. Note The following procedure is only for replacing a fiber cable. To replace a fiber cable: 1. Execute the dlmodmset utility for setting the HDLM execution environment ODM to check the NPIV option setting.
Lun Reset Online(E) IO Block NPIV Option : off : on : off
Check the NPIV Option line. 2. Place in Offline (C) status the path that goes through the cable to be replaced (path that goes through the HBA to which the cable is connected). Depending on the NPIV option setting for the dlmodmset utility checked in step 1, execute one of the following commands: If the NPIV option is set to off: Specify the HBA adapter number and bus number, and then execute the command shown below. The following example shows how to place the path in Offline (C) status when the path goes through an HBA whose HBA adapter number is 08 and whose bus number is 11:
If the NPIV option is set to on: Use the fscsi number to execute the command below. The following example shows how to place the path in Offline (C) status when the path goes through fscsi number 1 (fscsi1):
Replace the cable. Note If you change the port on the Fibre Channel switch or on the storage system, the path configuration will be changed. Delete the hdisk that are associated with the cable to be replaced and then reconfigure the device.
Place in Online status the path that goes through the replaced cable. Place in Online status the path that goes through the HBA to which the replaced cable is connected. Depending on the NPIV option setting for the dlmodmset utility checked in step 1, execute one of the following commands: If the NPIV option is set to off: Specify the HBA adapter number and bus number, and then execute the command shown below. The following example shows how to place the path in Offline (C) status when the path goes through an HBA whose HBA adapter number is 08 and whose bus number is 11:
# /usr/DynamicLinkManager/bin/dlnkmgr online -hba 08.11
# /usr/DynamicLinkManager/bin/dlnkmgr online -hba 00.01

environment.

5.3.3 Identifying the Error Path
Check the obtained path information to find the path with the error. In the Status column, the error path has the status Offline(E) or Online(E).
5.3.4 Narrowing Down the Hardware That Might Have Caused the Error
Check the DskName , iLU , ChaPort , and HBAPortWWN columns of the path with the error to narrow down the hardware that may be the cause of the error. To physically identify the hardware corresponding to DskName, iLU, and ChaPort, use the information provided by the storage-system management program.
5.3.5 Identifying the Error Location and Correcting any Hardware Errors
Use the AIX and hardware management tools to identify the error location, and then take appropriate, corrective action. For hardware maintenance, contact your hardware vendor or maintenance company if there is a maintenance contract.
5.3.6 Placing the Path Online
After the path has recovered from the error, use the dlnkmgr command's online operation to place the path back online. For details on the online operation, see 6.5 online (Places Paths Online). Execute the following command:
# /usr/DynamicLinkManager/bin/dlnkmgr online
Executing this command places all the offline paths online. If any path cannot be placed online due to an error, the KAPL01039-W message will appear. To ignore such paths and to continue processing, type y. Type n to cancel processing. Check the statuses of the paths that cannot be placed online, and resolve the problem.
5.4 What To Do for a Program Error
The following describes what to do to handle errors that occur in an HDLM program. Figure 5-3: Troubleshooting Procedure When a Program Error Occurs shows the troubleshooting procedure. Figure 5-3: Troubleshooting Procedure When a Program Error Occurs
The following shows the procedure for handling a program error by using the HDLM command (dlnkmgr).
5.4.1 Examining the Messages
Examine the message that is output to syslog in the host. If an error occurs in an HDLM program, a message other than KAPL08xxx is output to syslog. Examine the content of the message. Messages with error level E (Error) or higher require corrective action.
5.4.2 Obtaining Program Information
Obtain the information that you need to report to your HDLM vendor or maintenance company. Use the DLMgetras utility for collecting HDLM error information. For details on the DLMgetras utility and the information it collects, see 7.2 DLMgetras Utility for Collecting HDLM Error Information. Some of the information collected by the DLMgetras utility might be cleared when the host is restarted. Because of this, whenever an error occurs, execute the DLMgetras utility as soon as possible.

6.4 offline (Places Paths Offline)
The dlnkmgr command's offline operation places online paths offline. Specify the paths to be placed offline by specifying an HBA port, CHA port, single path, or host device. There must always be at least one online path accessing each LU. Placing too many paths offline might prevent paths from being able to switch if an error occurs. Before placing a path offline, use the view operation to check how many online paths remain. For details about the view operation, see 6.7 view (Displays Information).

6.4.1 Format

(1) To Place Paths Offline
/usr/DynamicLinkManager/bin/dlnkmgr offline [-path] {-hba HBA-adapter-number.bus-number-or-adapter-type.adapter-number |-hbaid HBA-port-ID |-cha -pathid AutoPATH_ID |-chaid CHA-port-ID |-pathid AutoPATH_ID |-hdev host-device-name -ospathid OS-management-path-ID} [-s]
(2) To Display the Format of the Offline Operation
/usr/DynamicLinkManager/bin/dlnkmgr offline -help

6.4.2 Parameters

Indicates that the target of the operation is a path managed by HDLM. This parameter is optional because offline is always used for paths, so it is assumed. Make sure that you specify the paths to be placed offline by using the -hba, -hbaid, -cha, -chaid, or -pathid parameter, or the -hdev and -ospathid parameters.
-hba HBA-adapter-number.bus-number
-hba adapter-type.adapter-number
Use this parameter to place offline, at one time, all the paths that pass through a specific HBA port. The command will place offline all the paths connected to the HBA port that has the specified HBA-adapter-number.bus-number or adapter-type.adapter-number. Specify the HBA adapter number and bus number, or adapter type and adapter number, of the target HBA port: the numbers are found in the PathName field displayed using the view operation. Enter a period between these two parameter values. For details about the view operation, see 6.7 view (Displays Information). The HBA-adapter-number.bus-number and adapter-type.adapter-number strings are case-sensitive. Example The following example shows how to place offline all paths connected to the HBA port whose HBA adapter number is 01 and bus number is 01. When the confirmation message is displayed, the user enters y to continue, or n to cancel the operation.

000002, online without asking for confirmation of command execution
The following example shows how to place a path, whose AutoPATH_ID is

from the user:

# /usr/DynamicLinkManager/bin/dlnkmgr online -pathid 2 -s KAPL01061-I 1 path(s) were successfully placed Online; 0 path(s) were not. Operation name = online #
Displays the format of the online operation. Example The following example shows how to display the format of the online operation:
# /usr/DynamicLinkManager/bin/dlnkmgr online -help online: Format dlnkmgr online [-path] [-s] dlnkmgr online [-path] { -hba HBAPortNumber.BusNumber | -hbaid HBA_ID } [-s] dlnkmgr online [-path] { -cha -pathid AutoPATH_ID | -chaid CHA_ID } [-s] dlnkmgr online [-path] [-pathid AutoPATH_ID] [-s] dlnkmgr online [-path] [-hdev Host_Device_Name [-ospathid OS_Path_ID]] [-s] Valid value AutoPATH_ID { 000000 - 999999 }(Decimal) HBA_ID {00000 - 99999}(Decimal) CHA_ID {00000 - 99999}(Decimal) OS_Path_ID {00000 - 99999}(Decimal) KAPL01001-I The HDLM command completed normally. Operation name = online, completion time = yyyy/mm/dd hh:mm:ss # Reference
Using the view operation together with standard UNIX commands enables you to filter the path information listed for a specific HBA port or CHA port. For details about the view operation, see 6.7 view (Displays Information). We recommend that you use the following command and verify the information on the target paths before you execute the online operation to place online all the paths connected to a specific HBA port or CHA port. Example 1 The following example shows how to filter and display the information on all paths that pass through the HBA port whose HBA adapter number is 04 and bus number is 01.
The above command will display information on all the paths that pass through the specified HBA port. Example 2
The following example shows how to filter and display the information on all paths that pass through the CHA port 0A of the Thunder 9500V series:
6.6 set (Sets Up the Operating Environment)
The dlnkmgr command's set operation sets the HDLM operating environment.

6.6.1 Format

(1) To Set Up the HDLM Operating Environment
/usr/DynamicLinkManager/bin/dlnkmgr set {-lb {on [-lbtype {rr|exrr|lio|exlio|lbk|exlbk}]|off} |-ellv error-log-collection-level |-elfs error-log-file-size |-elfn number-of-error-log-files |-systflv trace-level |-systfs trace-file-size |-systfn number-of-trace-files |-pchk {on [-intvl checking-interval]|off} |-afb {on [-intvl checking-interval]|off} |-iem { on [-intvl error-monitoring-interval] [-iemnum number-of-times-error-is-to-occur] | off } |-lic |-audlog {on [-audlv audit-log-data-collection-level] [-category [[ss] [a] [ca]|all]]|off} |-audfac facility-value} [-s]
(2) To Display the Format of the Set Operation

When you specify on, specify the checking interval by specifying the parameter immediately following on. If you do not specify a checking interval, path statuses will be checked in the following way: When the checking interval has not been specified before: Every 60 minute (default setting) When the checking interval has been specified before: The previously used interval The explanation for the following sub-parameter describes how to specify the interval between path status checks.
Specify the interval between path status checks. Specify a value from 1 to 1440 minutes. The default is 60. Specify an interval appropriate for your operating environment. If intermittent error monitoring is on and the number of times that the error is to occur is set to a value of 2 or more, the following condition must be satisfied: error-monitoring-interval >= checking-interval-for-automatic-failback x number-of-times-error-is-to-occur-during-intermittent-error-monitoring
If this condition is not satisfied, the KAPL01080-W message will be output and an error will occur. If this happens, change any of the following settings: the checking interval for automatic failbacks, intermittent error-monitoring interval, or the number of times that the error is to occur. When you set the number of times that the error is to occur to 1, the above condition does not need to be satisfied. When you changed the error monitor interval while intermittent error monitoring is running, the new settings will take effect immediately. When the checking interval is shortened and the checking interval time after the change has already elapsed during the current checking interval, the path status check will start over. This setting remains stored in the system, even if you disable the function by changing the setting of automatic failbacks to off. Therefore, if you re-enable automatic failbacks and do not change the interval, path status checks will be executed at the interval already stored in the system.
-iem { on [-intvl error-monitoring-interval] [-iemnum
number-of-times-error-is-to-occur] | off } Enables or disables intermittent error monitoring.
Intermittent error monitoring can be enabled only when automatic failback is set to on. When you use automatic failback, we recommend that you set intermittent error monitoring to on to prevent an intermittent error from reducing I/O performance. If on is specified, be sure to also specify the intermittent error monitoring interval and the number of times that the error is to occur. The system assumes that an intermittent error is occurring if the specified number of times that the error is to occur is reached during the monitoring interval. A path that is assumed to have an intermittent error is excluded from automatic failbacks. Intermittent error monitoring is performed on each path. Intermittent error monitoring starts when a path is recovered from an error by performing an automatic failback. If you omit the intermittent error monitoring interval or the number of times that the error is to occur, each setting is specified as follows: When the intermittent error monitoring interval or the number of times that the error is to occur has not been specified before: The intermittent error monitoring interval is set to 210 minutes, and the number of times that the error is to occur is set to 3. When the intermittent error monitoring interval or the number of times that the error is to occur has been specified before: The values specified from the last time are used. When a value of 2 or more is specified for the number of times, the following condition must be satisfied: error-monitoring-interval >= checking-interval-for-automatic-failback x number-of-times-error-is-to-occur-during-intermittent-error-monitoring

Value (severity) Critical-level, Error-level, Warning-level, and Informational-level audit log data is collected. Critical-level audit log data is collected. Critical-level and Error-level audit log data is collected. Critical-level, Error-level, and Warning-level audit log data is collected. No audit log data is collected. Explanation
-category [[ss] [a] [ca]|all]
Specifies the categories of audit log data to be collected. Table 6-8: Values Indicating Audit Log Data Categories lists the values that indicate categories of audit log data. The default is all. Note that if you enter -category without specifying any category (ss, a, ca, or all), it is assumed that all is specified. Table 6-8: Values Indicating Audit Log Data Categories
Explanation Audit log events of the StartStop category are collected. Audit log events of the Authentication category are collected. Audit log events of the ConfigurationAccess category are collected. Audit log events of the StartStop, Authentication, and ConfigurationAccess categories are collected.

-audfac facility-value

Specifies the audit log facility. Table 6-9: Values of the Audit Log Facility describes the values of the audit log facility. The default is user.
Table 6-9: Values of the Audit Log Facility
user or 1 local0 or 16 local1 or 17 local2 or 18 local3 or 19 local4 or 20 local5 or 21 local6 or 22 local7 or 23 user local0 local1 local2 local3 local4 local5 local6 local7
Executes the command without displaying the message asking for confirmation of command execution from the user. Specify this parameter if you want to skip the response to the confirmation message: for example, when you want to execute the command in a shell script or batch file. (2) To Display the Format of the Set Operation
Displays the format of the set operation. Example The following example shows how to display the format of the set operation:
# /usr/DynamicLinkManager/bin/dlnkmgr set -help set: Format dlnkmgr set { -lb on [ -lbtype { rr | exrr | lio | exlio | lbk | exlbk } ] | -lb off | -ellv ElogLevel | -elfs ElogFileSize
| -elfn Number-Of-ElogFiles | -systflv TraceLevel | -systfs TraceFileSize | -systfn Number-Of-TraceFiles | -pchk on [ -intvl Interval-Time ] | -pchk off | -afb | -afb | -iem on [ -intvl Interval-Time ] off on [ -intvl Error-Monitor-Interval ] [ -iemnum Number-Of-Times ] | -iem | -lic | -audlog on [ -audlv AudlogLevel ] [ -category Category-Value ] | -audlog off | -audfac { Facility-Name | Facility-Number } } [-s] Valid value ElogLevel ElogFileSize Number-Of-ElogFiles TraceLevel TraceFileSize Number-Of-TraceFiles Interval-Time { 0 | 1 | 2 | 3 | 4 } (Default Value 3) { 100 - 2000000 }(KB) (Default Value 9900) { 2 - 16 }(Files) (Default Value 2) off

ChaPort#

Status
Attribute of the path Own: Owner path Non: Non-owner path When connecting to the Lightning 9900V series, Hitachi USP, Universal Storage Platform V/VM, Virtual Storage Platform, Hitachi AMS2000 series, or Hitachi SMS, all paths are owner paths.

IO-Count#

Total I/O count for the path, indicated by a decimal number. The maximum value that can be displayed is 232 - 1 (4294967295). If the total I/O count reaches the maximum value, it will re-start from 0. To reset the IO-Count value to 0, execute the dlnkmgr command's clear operation. Executing the clear operation also resets the number of I/O errors (IO-Errors) to 0. For details about the clear operation, see 6.2 clear (Returns the Path Statistics to the Initial Value). Total I/O error count for the path, indicated by a decimal number. The maximum value that can be displayed is 232 - 1 (4294967295). If the total I/O error count reaches the maximum value, it will re-start from 0. To reset the IO-Errors value to 0, execute the dlnkmgr command's clear operation. Executing the clear operation also clears the number of I/O operations (IO-Count) to 0. For details about the clear operation, see 6.2 clear (Returns the Path Statistics to the Initial Value). Dev number, indicated by a decimal number. This item pertains to a logical volume number. There is one Dev in an LU, so the number is fixed to 0. Host device name. Hdisk name is displayed. Information about the intermittent error. This item is displayed only when you specify -iem with the -path parameter. One of the following values is displayed for each path: Indicates that intermittent error monitoring is disabled or the monitoring time for an intermittent error is out of range. A value of at least 0 Indicates the number of errors that occurred during intermittent error monitoring. * Indicates that an intermittent error occurred (automatic failbacks do not check the path). A 16-digit hexadecimal number indicating the WWN information for an HBA connected to the storage system. This item is displayed only when you specify -iem together with the -hbaportwwn parameter.

HDevName# IEP#

HBAPortWW N

Legend: -: Not displayed

-item parameter.
The path information is displayed only when a value is specified for the -path
Table 6-13: Elements of a Path Name
Element HBA adapter number (example: 08)#1 Bus number (example: 14)#1 AIX representation HBA adapter number Corresponding information The HBA adapter number, which is displayed by executing the lsdev -Cc disk command The parent bus number, which is displayed by executing the lsdev -Cc disk command Always 00 The fscsi number, which is displayed by executing the lsdev -C command The value of scsi_id, which is displayed by executing the lsattr -El hdisk-name command The value of lun_id, which is displayed by executing the lsattr -El hdisk-name command

Filters the information only for the paths accessing the specified host device. Specify hdisk name for host-device-name. The host-device-name string is case-sensitive.

-pathid AutoPATH_ID

Use this parameter to display only the information about the LU that is connected to the path with that specified AutoPATH_ID.
Omits the title for each information item. Example The following example shows how to display the LU information without selecting items to be displayed:
# /usr/DynamicLinkManager/bin/dlnkmgr view -lu Product : USP SerialNumber : 0014010 LUs : 10
iLU HDevName OSPathID PathID Status 003A hdisk000000 Online Online 003B hdisk000002 Online Online 003C hdisk000004 Online Online 003D hdisk000006 Online Online 003E hdisk000008 Online Online 003F hdisk000010 Online Online 0040 hdisk000012 Online Online 0041 hdisk000014 Online Online 0042 hdisk000016 Online Online 0043 hdisk000018 Online Online KAPL01001-I The HDLM command completed normally. Operation name = view, completion time = yyyy/mm/dd hh:mm:ss # To display LU information (by adding items to be displayed) -lu -item
The items specified with the -item option are displayed among with those displayed by the -lu option. If no value or all is specified for the -item parameter, all the items that can be added are displayed. Table 6-15: Items That Can Be Added by Using the -lu -item Parameter and Sub-parameters lists the items that can be added by using the -item parameter and the parameters that can be specified after the -item parameter. Table 6-15: Items That Can Be Added by Using the -lu -item Parameter and Sub-parameters

Item that can be added

SLPR PathName slpr pn

Subsequent parameter

ChaPort CLPR Type IO-Count IO-Errors DNum IEP VG cp clpr type ic ie dnu iep vg all

All items are displayed

In the sub-parameters, -hdev or -pathid, you can filter the LU information to be displayed. If you omit both parameters, the command displays the information about all the LUs recognized by HDLM. For details on the contents of each displayed item, see Table 6-17: Displayed LU Information. The sub-parameters are:
Omits the title for each information item. Example: The following example shows how to add SLPR, PathName, ChaPort, CLPR, Type, IO-Count, IO-Errors, DNum, IEP, and VG to the displayed items for LU information.
To display a summary of LU information -lu -c
When the -c parameter is specified with the -lu parameter, a summary of LU configuration information is displayed on one line. The total number of paths recognized by HDLM and the number of online paths are displayed for each LU.

KAPL11905-E

Details An exception occurred during processing on the host. Action Execute the DLMgetras utility for collecting HDLM error information to collect the error information, and then contact your HDLM vendor or maintenance company if there is a maintenance contract for HDLM.For details on the DLMgetras utility, see 7.2 DLMgetras Utility for Collecting HDLM Error Information.

KAPL11906-I

GUI information - aa.aa
Details This information is required for resolving problems. aa.aa: Trace information Action

KAPL11907-I

XML reception - aa.aa
Details This information is required for resolving problems. aa.aa: XML information Action None.

KAPL11908-I

XML transmission - aa.aa
8.12 KAPL13001 to KAPL14000

KAPL13001-I

The dlmmigsts utility completed successfully.

KAPL13002-E

The dlmmigsts utility ended abnormally.
Action Refer to action of the message outputted just before this message.

KAPL13003-I

The specified file already exists. Do you want to overwrite it? [y/n]:
Action To overwrite the specified file, enter y. To stop execution, enter n.

KAPL13004-W

Action Enter either y or n.

KAPL13005-E

Action To execute dlmmigsts again, re-execute. For details about the dlmmigsts utility, see 7.6 dlmmigsts Utility for Assisting HDLM Migration.

KAPL13006-I

KAPL13007-W
Action Specify the -h option in the HDLM migration support utility, confirm the option that should be specified, and then re-execute. For details about the dlmmigsts
utility, see 7.6 dlmmigsts Utility for Assisting HDLM Migration.

KAPL13008-W

Details aa.aa: Parameter (character string) Action Specify the -h option in the HDLM migration support utility, confirm the option that should be specified, and then re-execute. For details about the dlmmigsts utility, see 7.6 dlmmigsts Utility for Assisting HDLM Migration.

KAPL13009-W

No parameter value has been specified. parameter = aa.aa