HP-UX iSCSI Software Initiator Support Guide (Edition 7) HP-UX 11i v3 HP Part Number: T1452-90018 Published: E0414 Edition: Edition 7
© Copyright 2007, 2014 Hewlett-Packard Development Company L.P. Legal Notices The information contained herein is subject to change without notice. Warranty The only warranties for HP products and services are set forth in the express warranty statements accompanying such products and services. Nothing herein should be construed as constituting an additional warranty. HP shall not be liable for technical or editorial errors or omissions contained herein. U.S.
About This Document This document describes how to install, configure, and troubleshoot the HP-UX iSCSI Software Initiator on HP-UX 11i v3 platforms. The document manufacturing part numberand publication time frame provide a unique identifier for this document and indicate when it was published. The manufacturing part number will change when a new edition is released. Document updates may be issued between editions to correct errors or document product changes.
Related Documents The HP-UX iSCSI Software Initiator Release Notes and the HP-UX iSCSI Software Initiator Support Matrix can be accessed at http://www.docs.hp.com in the Networking and Communications collection under the iSCSI category. HP Encourages Your Comments HP is committed to providing documentation that meets your needs. Please let us know if you have suggestions or find any errors. Please include the document title and manufacturing part number, and send comments to: netinfo_feedback@cup.hp.
1 iSCSI Overview This chapter contains information on: • “iSCSI Protocol Overview” (page 5) • “The iSCSI PDU” (page 6) • “iSCSI Layering” (page 6) • “iSCSI Session and TCP Connections” (page 7) • “iSCSI Login” (page 8) • “iSCSI Concepts: Network Entities, Portals, and Nodes” (page 9) 1.1 iSCSI Protocol Overview NOTE: This chapter provides a brief, high level, overview of the iSCSI Protocol as defined by RFC 3720.
1.2 The iSCSI PDU iSCSI initiators and targets communicate with messages known as “iSCSI Protocol Data Units”. An iSCSI PDU has a Header and an optional Data Section. Figure 2 iSCSI Protocol Data Unit (PDU) iSCSI PDUs are transported in the TCP Segment Data Area of Ethernet Frames. The size of an iSCSI PDU is not dictated by the capacity of the TCP segment data area and an iSCSI PDU does not need to begin at a specific offset within a TCP segment data area.
In the inbound direction (Target to Initiator): 1. The iSCSI layer receives iSCSI PDUs on one or more TCP connections in a TCP/IP stream. 2. The iSCSI layer extracts the SCSI CDBs from the iSCSI PDUs and passes them to the SCSI layer. Figure 4 iSCSI Layering 1.4 iSCSI Session and TCP Connections In an iSCSI session, communication between an initiator and a target occurs over one or more TCP connections.
1.5 iSCSI Login The iSCSI login enables: • A TCP connection for iSCSI use • Authentication of the parties • Negotiation of the session’s parameters • Marking the connection as belonging to an iSCSI session An iSCSI session is established to identify all of the connections between an initiator and a target belonging to the same I_T nexus. Targets listen on a well-known TCP port (3260, as defined in the iSCSI Protocol Specification), or on a user configured TCP port, for incoming connections.
One of the keys that is negotiated in this stage of the Login Phase is AuthMethod. For example: • ◦ key=value ◦ AuthMethod defines the authentication method. AuthMethod=CHAP Operational Parameters Negotiation Stage This stage consists of text string negotiation of operating parameters using key=value pairs of login parameter exchanges. Two of the many login keys that are negotiated in the Operational Parameters Negotiation stage of the Login Phase are MaxRecvDataSegmentLength and FirstBurstLength.
Figure 7 Network Entities, Portals and Nodes • Portal Groups - a set of network portals within a network entity that share network connections and can collectively coordinate an iSCSI session. • Target Portal Group (TPG) - Although iSCSI initiators and iSCSI targets use portal groups to coordinate iSCSI sessions, only target portal groups are used directly in the iSCSI protocol.
2 HP-UX iSCSI Software Initiator Product Overview This chapter contains information on: • “HP-UX iSCSI Software Initiator Features” (page 11) • “HP-UX iSCSI Software Initiator Components” (page 12) • “Targets” (page 13) • “Hardware Path Representation” (page 13) • “Device Discovery” (page 14) • “Static Discovery” (page 14) • “Service Location Protocol Based Dynamic Discovery” (page 14) 2.
• Challenge-Handshake Authentication Protocol (CHAP) The iSCSI Software Initiator supports CHAP for target authentication of initiators and initiator authentication of targets. • Multiprocessor Compatible The iSCSI Software Initiator is usable in a multi-processor environment. • New Management Tool The iSCSI Software Initiator introduces the “iscsiutil” management tool to the system. The iscsiutil tool is installed with the iSCSI Software Initiator.
Figure 9 HP-UX iSCSI Software Initiator Block Diagram 2.3 Targets The iSCSI Software Initiator is interoperable with all iSCSI Protocol Specification (RFC 3720) compliant targets. No component of the iSCSI Software Initiator implementation is, in any way, HP proprietary. The iSCSI Software Initiator supports the static discovery of targets and, optionally, the dynamic discovery of targets. 2.3.
2.3.2 Device Discovery The implementation of iSCSI on HP-UX uses a static discovery algorithm as the default means of identifying iSCSI targets (devices). As an option, dynamic discovery of targets is available using Service Location Protocol (SLP). 2.3.2.1 Static Discovery Static discovery requires the system administrator to identify all iSCSI discovery targets that will be accessible to an HP-UX host before an ioscanis executed.
Figure 10 Service Location Protocol NOTE: Once the operational targets are registered, the process used for static discovery of targets applies to them (starting from normal session establishment to operational targets), see “Static Discovery” (page 14). Table 2 SLP Server Installation Information and Related Documents Description url Service Location Protocol, version 2 (RFC 2608) http://www.ietf.org/rfc/rfc2608.txt An API for Service Location (RFC 2614) http://www.ietf.org/rfc/rfc2614.
3 Installation This chapter contains information on: • “Locating and Installing the iSCSI Software Initiator” (page 16) • “iSCSI Software Initiator Components” (page 16) • “Kernel Build” (page 17) • “Verifying the Installation” (page 17) 3.1 Locating and Installing the iSCSI Software Initiator The 1. 2. 3. 4. iSCSI Software Initiator is located at the HP Software Depot. Go to http://www.software.hp.com. Enter “iSCSI Software Initiator” in the “search” box.
• /sbin/rc2.d/S532iscsi This is the iSCSI startup script, which is symbolically linked to the /sbin/init.d/iscsi file. • /usr/share/man/man7.Z/iscsi.7 /usr/share/man/man1m.Z/iscsiutil.1m /usr/share/man/man1m.Z/iscsi-daemons.1m /usr/share/man/man1m.Z/iswd.1m /usr/share/man/man1m.Z/islpd.1m /usr/share/man/man1m.Z/iradd.1m /usr/share/man/man1m.Z/iscsi_resolvd.1m These are the iSCSI man pages. • /opt/iscsi/bin/iscsidiag This is a diagnostic tool for debugging the iSCSI Software Initiator.
2. Issue the ioscan command as follows: # ioscan -NkfnC iscsi If the software is installed correctly, the generated output will look similar to this: Class I H/W Path Driver S/W State H/W Type Description =================================================================== iscsi 0 64000/0x0 iscsi CLAIMED VIRTBUS iSCSI Virtual Root If the software is not installed correctly, see “Troubleshooting the iSCSI Software Initiator Installation” (page 32).
4 Configuration This chapter contains information on: • “Configuring the iSCSI Software Initiator” (page 19) • “Challenge-Handshake Authentication Protocol (CHAP) Configuration” (page 22) • “Configuring CHAP Authentication Uni-directional” (page 23) • “Configuring CHAP Authentication Bi-directional” (page 24) • “Starting the iradd (iSCSI CHAP) Daemon” (page 25) • “Configuring iSCSI Service Location Protocol (SLP) Scope” (page 26) 4.
following the colon (:) in the example above depicts the hostname (hpfcs214) followed by the partition identifier (2000853943). With the exception of the colon prefix, the owner of the domain name can designate the content of the optional string. It is the responsibility of the naming authority to ensure the iSCSI names it assigns are unique worldwide. For example, if the Hewlett-Packard Company owned the domain name "stor.hp.
where -a adds a discovery target address into iSCSI persistent information. Only discovery target addresses can be added using this option. -I is the option that requires the IP Address or the Hostname of the discovery target portal address as an argument. is the IP Address or Hostname component of the target network portal. [-P ] is the listening TCP port component of the discovery target network portal (optional). The default iSCSI TCP port number is 3260.
4.2 Challenge-Handshake Authentication Protocol (CHAP) Configuration Challenge-Handshake Authentication Protocol (CHAP) is an authentication protocol that defines a methodology for authenticating initiators and targets. If you do not intend to use CHAP for authentication, this aspect of the iSCSI Software Intitator configuration is not necessary and can be ignored. The iSCSI Software Initiator has visible system administration interactions with the Challenge-Handshake Authentication Protocol (CHAP).
Two authentication options are available if CHAP is chosen as the authentication method: • Uni-directional CHAP method: The target uses CHAP to authenticate the initiator. The initiator does not authenticate the target. The Uni-directional CHAP method does not require the use of theiradd daemon (iSCSI CHAP daemon). It also does not require configuration of a RADIUS server on the host (initiator) side. The default CHAP method is Uni-directional.
or # iscsiutil -u -W 0xed345ba678dfffe54e35666fa2c3c3 To configure the CHAP secret for a specific Discovery Target Address: # iscsiutil -u -W mychapsecret -I 192.1.1.34 -M 1 To configure the CHAP secret for a particular Operational Target: # iscsiutil -u -W mychapsecret -T iqn.2003-11.com.hp.stor:iSCSI To configure the CHAP secret for a particular Operational Target Address: # iscsiutil -u -W mychapsecret -T iqn.2003-11.com.hp.stor:iSCSI -I 192.1.1.
is the IP address or hostname of the RADIUS server. (3) Configure for the Bi-directional authentication method as follows: # iscsiutil -u -H [-T ] [-I ] ] [-P ] [-M To configure Bi-directional authentication on a global basis: # iscsiutil -u -H CHAP_BI To configure Bi-directional authentication for a particular Discovery Target Address: # iscsiutil -u -H CHAP_BI -I 192.1.1.
To start the iradd daemon: # iradd Once the iradd daemon has been started, the iradd daemon will be restarted automatically each time the system reboots. NOTE: For more information on iradd, see “iSCSI Challenge-Handshake Authentication Protocol Daemon (iradd)” (page 30). 4.3 Configuring iSCSI Service Location Protocol Daemon "Start on Boot" The iSCSI Software Initiator uses the iSCSI Service Location Protocol daemon (islpd) for SLPv2 based dynamic target discovery.
5 Management This chapter contains information on: • “ioscan” (page 27) • “The iscsiutil tool” (page 28) • “iscsiutil Command Utilization” (page 28) • “iSCSI Transport Statistics” (page 30) • “Diagnostic Messages” (page 30) • “iSCSI Software Initiator Daemons” (page 30) • “iSCSI Software Initiator Name Resolution Daemon (iscsi_resolvd)” (page 30) • “iSCSI Challenge-Handshake Authentication Protocol Daemon (iradd)” (page 30) • “iSCSI Service Location Protocol Daemon (islpd)” (page 31) 5.
The first line of the sample ioscanoutput displays the iSCSI virtual node. This is the root node for all iSCSI storage and will occur only once in the ioscan output. The iSCSI transport driver claims the iSCSI root node. The second line of the same ioscan output displays the iscsi virtual controller which represents the iSCSI S/W initiator. This line appears only once as there is only one instance of S/W initiator.. The third line displays the iSCSI normal session.
• A TCP port may be specified for the iSCSI target. If no port is specified, the default iSCSI port (3260) will be used. • The target portal group tag may be specified (a value from 0 to 65535 inclusive); otherwise, a default value of 1 will be used.
• - The target IP address and port. • - The target portal group tag. • -C displays statistics for all connections of the specified session instance (ssn_inst); if a connection identifier (cid) is specified, only the statistics for that connection will be displayed. • -V displays negotiated login key information.
The iradd daemon receives authentication requests from the iSCSI Software Transport driver. It forwards the authentication requests to the RADIUS server via a RADIUS message "Access Request". The RADIUS server responds toiradd with a RADIUS message, "Access Accept" (if the authentication of the target succeeded), or with "Access Reject" (if the authentication failed). The iradd daemon then passes the result to the iSCSI Software Transport driver.
6 Troubleshooting This chapter contains information on: • “Troubleshooting the iSCSI Software Initiator Installation” (page 32) • “Troubleshooting Undetected Target Devices” (page 33) • “Troubleshooting issues with iswd daemon” (page 34) • “Diagnostics” (page 35) 6.
9. Verify that the files listed in “iSCSI Software Initiator Components” (page 16), are installed in the correct directories on the HP-UX system. 10. Verify that there are no kernel build errors (see step 5 for details). 11. If the problem is still not resolved, try installing the iSCSI Software Initiator again. 6.2 Troubleshooting Undetected Target Devices 1. 2. 3. Verify that all of the required patches or superseding patches for the iSCSI Software Initiator have been installed.
5. Issue the iscsiutil -sG command and look at the following statistics: • Number of Discovery session open failures If there is a non-zero value for this statistic, determine the cause of failure by either looking at the message logged in the /var/adm/syslog/syslog.log file or by monitoring the EMS/STM log files.
If you notice one instance of iswd, it means that currently iswd daemon is active but the I-T nexus is not active with any of the targets. If multiple instances of iswd are present, that implies that there is at least one I-T nexus that is currently active. If the iswd daemon is accidentally terminated the behavior displayed depends on the state of the iswd daemon. The most likely scenario would be: 1.
7 The iSCSI Software Interface Driver This chapter contains information on: • “iSCSI Software Interface Driver Overview” (page 36) • “iSCSI Software Interface Driver Technical Overview” (page 36) • “System Startup” (page 36) • “iSCSI Software Interface Driver Technical Specifications” (page 37) • “Features” (page 37) • “Limitations” (page 37) • “iSCSI Software Interface Driver Configuration” (page 37) • “Kernel Build” (page 37) • “iSCSI Software Interface Driver Management” (page 37) • “i
on an iSCSI target. Also, the boot, root, primary swap, and dump file systems are not supported on iSCSI volumes. 7.3 iSCSI Software Interface Driver Technical Specifications 7.3.1 Features • The iSCSI SWD conforms to the iSCSI Protocol Specification (RFC 3720). • The iSCSI SWD will function over standard NICs (Network Interface Cards). • The iSCSI SWD will be a compute-intensive driver. 7.3.
7.7 iSCSI Software Interface Driver Statistics Statistics are maintained in the iSCSI Software Interface Driver (SWD). For a detailed listing and explanation of the iSCSI Software Interface Driver statistics see Appendix D (page 53). 7.8 iSCSI Software Interface Driver Diagnostic Messages By default, the iSCSI Software Interface Driver logs all diagnostic messages to the Support Tools Manager (STM) log files.
A Login Key Configuration A.1 Configuring iSCSI Login Keys In accordance with the iSCSI protocol, an iSCSI initiator must negotiate iSCSI login keys with each iSCSI target to: — enable an iSCSI connection — authenticate the parties — negotiate the session’s parameters — mark the connection as belonging to an iSCSI session All of the iSCSI login keys configured by default by the iSCSI Software Initiator apply to all of the targets connected to the iSCSI host node.
CRC32C • DataDigest A data digest that can be negotiated during iSCSI login. The list of values that the DataDigest key can accept are: None CRC32C • AuthMethod An authentication method that can be negotiated during iSCSI login.
# iscsiutil -t authmethod None CHAP -T iqn.2003-11.com.hp. stor:iSCSI.Storage Configure the AuthMethod key with "CHAP" as the Authentication Method for an Operational Target Address: # iscsiutil -t authmethod CHAP -I 192.1.1.58 -M 2 -T iqn.2003-11.com.hp.stor:iSCSI.Storage A.1.3 Displaying Login Keys NOTE: The values displayed for the login keys by the following commands are the values proposed by the iSCSI Software Initiator to the iSCSI target, in order of preference.
B Transport Statistics B.1 Transport Statistics Transport statistics are explained in Table 4: “Transport Statistics” (page 42). The Class column (CL) provides message classification. Messages can be informational (I), target errors (T), transient driver errors (D), or connectivity problems (C). Informational Messages are counters for driver events. They are not an indication of an error, but should an error occur, they may provide some profiling information.
Table 4 Transport Statistics (continued) iscsiutil Statistic CL Description of Field Number of SendTargets commands issued I The number of iSCSI SendTargets commands sent to iSCSI targets. The iSCSI SendTargets command is used in discovery sessions to determine normal targets behind a target port (portal group). Normal sessions can then be established with the normal targets for I/O operations.
Table 4 Transport Statistics (continued) iscsiutil Statistic CL Description of Field Number of destination hostname resolution failures C The number of hostname resolution failures. Hostname resolution is performed via the iscsi_resolvd daemon. A hostname resolution failure indicates a network configuration problem. Number of destination address routing failures C The number of destination address routing failures. Destination address routing is performed through host networking.
Table 4 Transport Statistics (continued) iscsiutil Statistic CL Description of Field Number of task management commands sent I Number of times a task management operation has been forwarded to iSCSI software initiator for further processing. Task management commands not sent due to no connection D/T Number of times task management operation could not be sent to target due to unavailability of an active I-T nexus.
Table 4 Transport Statistics (continued) 46 iscsiutil Statistic CL Description of Field I/Os timed out D/T Number of times an I/O failed due to time-out. An I/O can get timed out due to transient error conditions in the I-T nexus or due to memory crunch situations or due to tag allocation failures that can happen when a device is slow and I/O load is heavy. I/Os failed due to connection being offline D/T Number of times an I/O failed due to connection being in offline state.
C Diagnostic Messages C.1 Diagnostic Messages By default, the iSCSI Software Interface Driver logs all diagnostic messages to the Support Tools Manager (STM) log files. At the time of this publication, there is no support to display messages logged by the iSCSI driver in the HP-UX 11i v3 version of STM. When this support is released, STM can be used to view these diagnostic messages.
The third entry in each message listing is a brief description of the message. It is necessary to have a familiarity with the iSCSI specification and the driver implementation to completely understand the messages. See Table 5: “Logging Levels for the syslog.log File” (page 47) for a detailed explanation of logging levels. C.1.1 Message Descriptions 1. ISCSI_LOG_INV_LUN_ADDR_TYPE "Unsupported LUN Addressing type recognized." The target has attempted to use invalid LUN addressing. LVL_ERR 2.
"Initiator login key (%s) was not understood by \n" "the target." The initiator login key supplied to the target was not recognized or understood by the iSCSI target.This information should be provided to the support team for analysis. 11. ISCSI_LOG_PROTOCOL_INIT_KEY_REJECTED LVL_ERR "Initiator login key (%s) was rejected by the target." The initiator login key supplied to the iSCSI target was recognized by the iSCSItarget and then rejected.
"No response received from the target for character \n" "login key (%s)." The target failed to respond to or recognize, a string key. The login failed as a result of the protocol violation. 19. ISCSI_LOG_PROTOCOL_TOO_MANY_LOGIN_EXCH LVL_ERR "The maximum number of exchanges (%d) for a login stage has been \n" "exceeded." The initiator and target have performed exchanges in an attempt to successfully complete the login phase.
29. ISCSI_LOG_SSN_RESOLV_FAIL LVL_ERR "Unable to resolve the Target Hostname (%s)." The specified Hostname is not a Qualified Domain Name. This will cause the target port hostname resolution to fail. Check if the hostname specified for the target port is a Qualified Domain Name. If the problem persists, please contact your network administrator for further assistance. 30. ISCSI_LOG_SSN_ROUTE_FAIL LVL_ERR "No route found for IP address (%s).
The target requested the login to be redirected to a new target address. The request was granted and the redirected login succeeded. 39. ISCSI_LOG_INCOR_TGT_ADDR_REDI "Invalid key value (%s) received from the target for\n" "TargetAddress key." An invalid key value was sent by the target within a login redirection response for TargetAddress text key. The discovery of target devices would fail as a result.
D iSCSI Software Interface Driver Statistics D.1 iSCSI Software Interface Driver Statistics Statistics are maintained in the iSCSI Software Interface Driver (SWD). These statistics are explained in Table 6: “Software Interface Driver Statistics” (page 53). The Class column (CL) provides message classification. Messages can be informational (I), target errors (T), transient driver errors (D), or connectivity problems (C). Informational Messages are counters for driver events.
Table 6 Software Interface Driver Statistics (continued) iscsiutil Statistic CL Number of failures to send a login command D due to kernel memory allocation failure The number of attempts to send the Login command that failed due to memory allocation failures. The upper level driver recovery may retry the session open, resulting in a re-attempt to send the Login command. If the memory allocation request succeeds, the Login command will transmit successfully.
Table 6 Software Interface Driver Statistics (continued) iscsiutil Statistic CL Description of Field that some outbound command, or a NOP-OUT in response to a NOP-IN, could not be completed. As a result: — The regular occurrence of this event will have a negative impact on performance. — Failed I/Os will be retried according to existing SCSI retry policies (same as Fibre Channel and parallel SCSI), however, there is no retry policy for native iSCSI commands.
Table 6 Software Interface Driver Statistics (continued) iscsiutil Statistic CL Description of Field regular occurrence of this event will have a negative impact on performance. Failed I/Os will be retried according to existing SCSI retry policies (same as Fibre Channel and parallel SCSI). Number of streams message allocation failures D The number of memory allocation attempts for a kernel driver structure that failed.
Table 6 Software Interface Driver Statistics (continued) iscsiutil Statistic CL Description of Field indicates that the Expected Data Transfer Length in the I/O request was not sufficient. Number of I/O failures due to response code errors T The total number of I/Os that failed due to a response code error in the SCSI response PDU. This means that the target failed to execute the I/Os. A large value here could indicate that the target is not functioning properly.
Table 6 Software Interface Driver Statistics (continued) 58 iscsiutil Statistic CL Description of Field Number of "target requests parameter negotiation" Async events received I The total number of times the target sent an asynchronous event with the AsyncEvent set as "target request parameter negotiation". Number of "vendor specific" Async events received I The total number of times the target sent an asynchronous event with the AsyncEvent set as "vendor specific Async event".
E iSCSI Software Interface Driver Diagnostic Messages E.1 iSCSI Software Interface Driver Diagnostic Messages By default, the iSCSI Software Interface Driver logs all diagnostic messages to the Support Tools Manager (STM) log files. At the time of this publication, there is no support to display messages logged by the iSCSI driver in the HP-UX 11i v3 version of STM. When this support is released, STM can be used to view these diagnostic messages.
F Glossary This chapter contains definitions of terminology and acronyms used throughout this document. F.1 Terminology Directory Agent - A process which collects service advertisements. There can only be one DA present per given host. Discovery Session - Initiated with a Discovery Target to discover Operational Targets in a Network Entity.
Supported - A feature in a release for which implementation and testing for that release have been completed. Target Address - consists of three components, the IP address of the network portal the target uses, its TCP port number, and its target portal group tag. Transport Driver - A protocol specific layer combining aspects of the iSCSI Adaption Layer and the iSCSI Transport Layer, which defines a transport technique for SCSI block IO.
SA - Service Agent SAM - System Administration Manager - an HP-UX GUI tool for system level administration. SAM-2 - SCSI Architecture Model (2) - a T10 standard. SAN - Storage Area Network - a network with emphasis on storage with a defined protocol for the infrastructure. SCSI - Small Computer Systems Interface - a mass storage data transmission protocol. SD - Software Distributor - an HP-UX tool for installation and distribution of software. SG - Serviceguard - an HA product for HP-UX.
Index A aborted reopen sessions, 43 addresses IP, 14, 30, 51 Operational targets, 24, 39, 40 routing failures, 44 alert level syslog message, 47 asynchronous events driver statistics, 54, 57 transport statistics, 43, 44 authentication.
host systems driver configuration, 37 static Discovery, 14 hostname configuration, 24 iscsi_resolvd daemon, 16, 30 resolution of, 44, 51 hostname resolution daemon (iscsi_resolvd), 16 HP-UX Event Monitoring Services (EMS), 30, 38 see also diagnostics HP-UX iSCSI Software Initiator.
syslog messages, 48 types, 21 logouts, tracking, 44, 54 LUNs (logical unit numbers) and hardware path, 13 diagnostic messages, 48 LVL_ALERT, 47 LVL_CRIT, 47 LVL_DEBUG, 47 LVL_ERR, 47 LVL_INFO, 47 LVL_NOTE, 47 LVL_PANIC, 47 LVL_WARN, 47 M man pages, iSCSI, 17 mass storage transport protocol.
STM, 38, 47, 59 STM log files, 30 streams message failures, 55, 56, 57 SWD (iSCSI Software Interface Driver). see iSCSI Software Interface Driver swlist command verifying installation, 17 syslog file messages descriptions, 48 driver-related, 59 syslog.
