Overland Storage SnapSAN S3000 User Manual

Overland Storage SnapSAN S3000 User Manual

Path manager linux
Hide thumbs Also See for SnapSAN S3000:
Table of Contents

Advertisement

Quick Links

SnapSAN
Overland
Storage
April 2013
10400424-002
Path Manager Linux
User Guide
S3000/S5000

Advertisement

Table of Contents
loading
Need help?

Need help?

Do you have a question about the SnapSAN S3000 and is the answer not in the manual?

Questions and answers

Subscribe to Our Youtube Channel

Summary of Contents for Overland Storage SnapSAN S3000

  • Page 1 SnapSAN Path Manager Linux Overland ™ Storage User Guide S3000/S5000 April 2013 10400424-002...
  • Page 2 Overland Storage. Overland Storage provides this manual as is, without warranty of any kind, either expressed or implied, including, but not limited to, the implied warranties of merchantability and fitness for a particular purpose. Overland Storage may make improvements or changes in the product(s) or programs described in this manual at any time.
  • Page 3 Storage Area Network (SAN), and Redundant Array of Independent Disks (RAID) technology. Product Documentation and Firmware Updates Overland Storage SnapSAN product documentation and additional literature are available online, along with the latest release of the SnapSAN 3000/5000 software. Point your browser to: http: //docs.overlandstorage.com/snapsan...
  • Page 4 SnapSAN S3000/S5000 Path Manager Linux User Guide For a complete list of support times depending on the type of coverage, visit our web site at: http: //support.overlandstorage.com/support/overland_care.html Conventions This user guide exercises several typographical conventions: Convention Description & Usage Boldface Words in a boldface font (Example) indicate items to select such as menu items or command buttons.
  • Page 5: Table Of Contents

    Manual Uninstallation ......................... 2-20 Updating PathManager .......................... 2-23 Chapter 3 - Functions Limit of Paths and Disks ..........................3-1 Load Distribution Function ........................3-1 Load Distribution ............................3-2 Static Load Distribution (FailoverOnly) ....................3-2 10400424-002 04/2013 ©2013 Overland Storage, Inc. ...
  • Page 6 Chapter 5 - Cautions and Restrictions Cautions ..............................5-1 Restrictions ..............................5-1 Appendix A - Commands Commands of Function Version 5.1.0 or Later ..................A-1 mkdd command ..........................A-1 spsadmin command ........................A-1 Command of Function Version Less than 5.1.0 ..................A-7 10400424-002 04/2013 ©2013 Overland Storage, Inc. ...
  • Page 7 Setting up kdump with a PathManager Device ................F-1 Resetting the kdump setting ......................F-2 SUSE Linux Enterprise Server 10 ........................F-3 Setting up kdump with a PathManager device ................F-3 Resetting the kdump setting ......................F-6 Appendix G - Error Messages Index 10400424-002 04/2013 ©2013 Overland Storage, Inc. ...
  • Page 8: Chapter 1 - Path Manager Linux

    To make the most of the features, one static load distribution mode and two dynamic load distribution modes, a total of three load distribution modes, are available. You can use the load distribution function for more efficient access. 10400424-002 04/2013  ©2013 Overland Storage, Inc.
  • Page 9: Structure Of Pathmanager

    SnapSAN S3000/S5000 Path Manager Linux User Guide Structure of PathManager PathManager runs on a server like Linux and monitors the path between the HBA (Host Bus Adapter) or NIC (Network Interface Card) on the server and the HP (Host Port) on the disk array.
  • Page 10: System Configuration

    SnapSAN S3000/S5000 Path Manager Linux User Guide Figure 1-1: Multiplex SCSI Path System The active path is the path that can currently perform I/O processing. The alternate path is the path to be switched and used as the active path when a fault occurs on the active path.
  • Page 11: Multiple Server Configuration

    Figure 1-3: Multi Server Configuration Cluster Configuration An example of a cluster system configuration is shown below. An FC switch is installed between each server and a SnapSAN S3000/35000 to show the same logical unit from multiple servers. 10400424-002 04/2013 ...
  • Page 12 SnapSAN S3000/S5000 Path Manager Linux User Guide Figure 1-4: Cluster Configuration 10400424-002 04/2013  ©2013 Overland Storage, Inc.
  • Page 13: Chapter 2 - Installation

    • Red Hat Enterprise Linux 5 (kernel-2.6.18-164.el5) (IA32/EM64T) or later • Red Hat Enterprise Linux 5 Advanced Platform (kernel-2.6.18-164.el5) (IA32/EM64T) or later • Red Hat Enterprise Linux 6 (kernel-2.6.32-131.0.15.el6) (IA32/EM64T) or later • SUSE Linux Enterprise Server 10 (kernel-2.6.16.60-0.57.1) (IA32/EM64T) or later 10400424-002 04/2013  ©2013 Overland Storage, Inc.
  • Page 14 SnapSAN S3000/S5000 Path Manager Linux User Guide 7. In the case you use the Overland Storage which has both FC and iSCSI connections, the distribution and kernel version must be one of shown below. • Red Hat Enterprise Linux 5 (kernel-2.6.18-194.el5) (IA32/EM64T) or later •...
  • Page 15 SnapSAN S3000/S5000 Path Manager Linux User Guide Directory/File name Description Linux RPM files `-- RPMS |-- RHEL4 Packages of PathManager (*1) |-- RHEL5 | |-- 5.1 | |-- 5.2 | |-- 5.3 | |-- 5.4 | |-- 5.5 | |-- 5.6 | |-- 5.7...
  • Page 16 SnapSAN S3000/S5000 Path Manager Linux User Guide Directory/File name Description Linux For Scalable HA Servers `-- RPMS |-- RHEL5 | |-- 5.3 | | `-- EM64T |-- sps-driver-E-4.2.4-2.6.18.128.el5.x86_64.rpm |-- sps-mcopt-1.1.0-0.x86_64.rpm (*3) `-- sps-utils-4.2.2-1.x86_64.rpm | `-- 5.6 `-- EM64T |-- sps-driver-E-5.0.3-2.6.18.238.9.1.el5.x86_64.rpm |-- sps-mcopt-1.1.1-0.el5.x86_64.rpm(*3)
  • Page 17 SnapSAN S3000/S5000 Path Manager Linux User Guide Directory/File name Description RPM files Linux `-- RPMS |-- RHEL4 Packages of PathManager (*1) |-- RHEL5 |-- 5.1 |-- 5.2 |-- 5.3 |-- 5.4 |-- 5.5 |-- 5.6 |-- 5.7 `-- 5.8 |-- IA32 |-- sps-driver-E-5.0.9-2.6.18.308.el5.i686.rpm...
  • Page 18: Prepare To Install

    SnapSAN S3000/S5000 Path Manager Linux User Guide Directory/File name Description For Linux/Scalable Linux HA Servers `-- RPMS |-- RHEL5 |-- 5.3 `-- EM64T |-- sps-driver-E-4.2.4-2.6.18.128.el5.x86_64.rpm |-- sps-mcopt-1.1.0-0.x86_64.rpm (*3) `-- sps-utils-4.2.2-1.x86_64.rpm `-- 5.6 `-- EM64T |-- sps-driver-E-5.0.3-2.6.18.238.9.1.el5.x86_64.rpm |-- sps-mcopt-1.1.1-0.el5.x86_64.rpm(*3) `-- sps-utils-5.0.2-1.el5.x86_64.rpm `-- RHEL6 |-- 6.1...
  • Page 19: Installing Pathmanager Rpm Package

    SnapSAN S3000/S5000 Path Manager Linux User Guide Connect the server to the Overland Storage and check whether the server recognizes a logical disk. If "Overland" is displayed in "Vendor" item and "Model Name" or "DISK ARRAY" is displayed in "Model" item as the result of execution of the command as follows, the Server is recognized normally.
  • Page 20: Manual Installation

    SnapSAN S3000/S5000 Path Manager Linux User Guide b. Execute the "install.sh" with "-i" option (as shown by the underlined part below). *1: If you use the "--silent" option, the installer reboots the server automatically. (You must reboot before operating the PathManager.) *2: If the system uses iSCSI connection, pass the "--iscsi"...
  • Page 21 SnapSAN S3000/S5000 Path Manager Linux User Guide - If the environment is as follows - Model of the server Linux RHEL5 Distribution Release version IA32 Architecture Installation Commands 1. RHEL 6 Execute the following command to install the RPM files corresponding to the kernel version you use.
  • Page 22 SnapSAN S3000/S5000 Path Manager Linux User Guide 3. Earlier than RHEL 5.3 (2.6.18-128.el5) Execute the following command to install the RPM files corresponding to the kernel version you use. (Shaded part shows the corresponding kernel. Even if the displayed kernel version includes "PAE", "smp", "hugemem"...
  • Page 23 SnapSAN S3000/S5000 Path Manager Linux User Guide The kernel version like "Kernel-2.6.18.29.1.10.el5" is an errata kernel. With this operation, the following files are installed: /lib/modules/(kernel version)/ kernel/drivers/scsi/dd_mod.ko /lib/modules/(kernel version)/ kernel/drivers/scsi/sps_mod.ko /lib/modules/(kernel version)/ kernel/drivers/scsi/sps_mod2.ko (*2) /sbin/dd_daemon /sbin/spscmd /sbin/spsadmin(*9) /sbin/hotaddpath /sbin/hotremovepath /sbin/removearrayinfo...
  • Page 24 SnapSAN S3000/S5000 Path Manager Linux User Guide *9: This file is installed if the OS is Red Hat Enterprise Linux 6. *10: The Path Patrol daemon is not installed as "/etc/rc.d/init.d/dd_daemon, but installed as "/etc/init.d/dd_daemon". Execute the following command to check that no error is displayed.
  • Page 25 SnapSAN S3000/S5000 Path Manager Linux User Guide If iSCSI connection, follow the procedures shown below. Skip this procedure if your system is following: • Red Hat Enterprise Linux 5.4 or later • Red Hat Enterprise Linux 6 • SUSE Linux Enterprise Server 10 10400424-002 04/2013 ...
  • Page 26: Shifting To A Pathmanager Environment

    SnapSAN S3000/S5000 Path Manager Linux User Guide Reboot the system and check that it starts up normally. The installation is complete. If you use LVM, set LVM according to "Adding PathManager Devices to LVM" section. If any application or setting file uses the standard SCSI device of storage as /dev/sdX,...
  • Page 27: Starting Operation

    SnapSAN S3000/S5000 Path Manager Linux User Guide See the device information of /dev/sdf using "sg_scan" command. Search /dev/ddX device which corresponds to /dev/sdf. The procedures are different according to the function version of PathManager. Execute "spsconfig" command with "-chk" option, then you can see the corresponding device.
  • Page 28: Rhel4, Rhel5, Sles10

    SnapSAN S3000/S5000 Path Manager Linux User Guide Execute the following steps. 1. Open the terminal. 2. Type "spsadmin --lun" and press the return key 3. Check the output. If PathManager works normally and conditions of all paths are normal, plural lines of path information appear under the "LoadBalance"...
  • Page 29 SnapSAN S3000/S5000 Path Manager Linux User Guide Check /proc/scsi/sps/ddX (X takes a value of a, b, c, and so on to indicate the number of LUNs created on the disk array). If "partition-info:" is NML, the paths are normally multiplexed. If nothing is displayed, a disk array is not recognized by either path.
  • Page 30: Pathmanager Uninstallation

    SnapSAN S3000/S5000 Path Manager Linux User Guide PathManager Uninstallation Shifting to a Non-PathManager Environment PathManagerChange the configuration from using PathManager devices (/dev/ddX) to using SCSI devices (/dev/sdX) corresponding to PathManager devices. For example, the following procedure shows how to change the /etc/fstab.
  • Page 31: Uninstalling Pathmanager Rpm Package

    SnapSAN S3000/S5000 Path Manager Linux User Guide Uninstalling PathManager RPM Package The PathManager uninstallation procedures depend on the system configuration (OS distribution / kernel). PathManager OS Distribution Kernel Version Red Hat Enterprise Linux AS 4 Red Hat Enterprise Linux ES 4 Red Hat Enterprise Linux 5 earlier than 2.6.18-164.el5...
  • Page 32: Manual Uninstallation

    SnapSAN S3000/S5000 Path Manager Linux User Guide PathManager"sps Uninstall Completed" (the shadowed part in above) is the sign of that the uninstallation has finished normally. When the uninstallation is finished normally, the system is going to restart in a minute (If specifying "--silent"...
  • Page 33 SnapSAN S3000/S5000 Path Manager Linux User Guide 2. Delete the description of PathManager from /etc/modprobe.conf. a. Open the /etc/modprobe.conf by any editor. b. Delete the "sps_mod2" line added in installation. 3. Save the data and quit the editor. 4. PathManager Unpatch the startup script.
  • Page 34 SnapSAN S3000/S5000 Path Manager Linux User Guide PathManager When you execute the patch command, the message "Unreversed patch detected! Ignore -R? [n]" may appear. In such case, answer "n". Next, "Apply anyway? [n]" appears. Answer "y" to this question. If an error message appears, the unpatching is failed. In that case, edit /etc/rc.d/rc.sysinit or /etc/rc.d/init.d/iscsi and delete the all that appropriate lines.
  • Page 35: Updating Pathmanager

    SnapSAN S3000/S5000 Path Manager Linux User Guide The uninstallation is complete. Updating PathManager To update PathManager, uninstall PathManager and then install PathManager. Particularly, how to update PathManager when you update the kernel is described below. 1. Uninstall the current PathManager.
  • Page 36: Chapter 3 - Functions

    And you can also set the path priority by the configuration file. In addition, PathManager automatically distinguishes the model of Overland and automatically selects the load distribution mode based on the model (*1). 10400424-002 04/2013  ©2013 Overland Storage, Inc.
  • Page 37: Load Distribution

    SnapSAN S3000/S5000 Path Manager Linux User Guide Figure 3-1: Static Load Distribution Figure 3-2: Dynamic Load Distribution PathManager does not support the automatic setting of load distribution mode. And this function works only when no configuration file exists. Load Distribution Static Load Distribution (FailoverOnly) The mode of load distribution (FailoverOnly).
  • Page 38: Round Robin Mode (Roundrobin)

    SnapSAN S3000/S5000 Path Manager Linux User Guide Round Robin Mode (RoundRobin) The path to which each I/O request is issued is changed sequentially from the higher priority path to the lower priority path. After an I/O request is issued to the lowest priority path, the next request is issued to the highest priority path.
  • Page 39: File Format

    SnapSAN S3000/S5000 Path Manager Linux User Guide Function Version Configuration File Format 4.1.1 to 4.3.X 3.0.2 to 4.0.X *1: The automatically created setting is not necessarily the best according to the environment. So select the best load distribution mode by measuring the I/O performances if needed.
  • Page 40 SnapSAN S3000/S5000 Path Manager Linux User Guide Setting Name (summary) Description Disk entry Write disk array information used for the device entry. The disk-info: information to be written includes: - Vendor name - Product name - Serial Number - LU Number LUN WWN (in the case that the file format is 1.2)
  • Page 41: Changing Configuration Of Pathmanager

    SnapSAN S3000/S5000 Path Manager Linux User Guide <Example for two devices> Changing Configuration of PathManager You can change the setting of PathManager whether the PathManager is operating. You can change the load distribution mode, the path monitoring interval, and the enable/disable setting of path monitoring.
  • Page 42 SnapSAN S3000/S5000 Path Manager Linux User Guide LoadBalance Sign of Distribution mode Setting Displaying Path Status (*2) FailoverOnly Static load distribution RoundRobin Dynamic load distribution (round robin mode) LeastSectors Dynamic load distribution (least I/O size mode) <Example> -- When the initial status (/dev/dda) is as follows:-- 1.
  • Page 43: Changing The Path Monitoring Interval

    SnapSAN S3000/S5000 Path Manager Linux User Guide The path status is changed as follows (the shaded parts are changed): Changing the Path Monitoring Interval 3. To change the path monitoring interval, change the configuration file (/etc/sps.conf), and then execute the mkdd command to reflect the settings.
  • Page 44 SnapSAN S3000/S5000 Path Manager Linux User Guide 5. Use the mkdd command to reflect the above setting. You can see the changed status if you refer to /proc/scsi/sps/interval. Changing path monitoring interval is complete. Enable/Disable setting of Path Monitoring 6. To change the enable/disable setting of path monitoring, change the configuration file (/etc/sps.conf), and then execute the mkdd command to reflect the settings.
  • Page 45: Changing Environment Of Pathmanager

    SnapSAN S3000/S5000 Path Manager Linux User Guide Changing path monitoring interval is complete. Enable/Disable setting of Intermittent Error Monitoring 8. To change the enable/disable setting of intermittent-error monitoring, change the configuration file (/etc/sps.conf), and then execute the mkdd command to reflect the settings.
  • Page 46 SnapSAN S3000/S5000 Path Manager Linux User Guide <Example> • When you add "Lun:03" - <Adding procedure for function version 4.0.1 or later> Execute scsi-rescan command so that the OS detects the added LUN. # scsi-rescan Scanning SCSI subsystem for new devices The scsi-rescan command is included in the rpm package named "sg3_utils".
  • Page 47 SnapSAN S3000/S5000 Path Manager Linux User Guide 10400424-002 04/2013  3-12 ©2013 Overland Storage, Inc.
  • Page 48 SnapSAN S3000/S5000 Path Manager Linux User Guide 10400424-002 04/2013  3-13 ©2013 Overland Storage, Inc.
  • Page 49: Initializing Configuration Of Pathmanager

    SnapSAN S3000/S5000 Path Manager Linux User Guide Initializing Configuration of PathManager For initializing the configuration of PathManager, remake the configuration file and make PathManager rediscover the disks. Follow the procedures below. 10400424-002 04/2013  3-14 ©2013 Overland Storage, Inc.
  • Page 50: Log Information

    SnapSAN S3000/S5000 Path Manager Linux User Guide The assignment of PathManager devices may be changed by initialization. If the new assignment is different from the backup file of /etc/sps.conf, put the "device:" lines in correct order and reboot the system.
  • Page 51: System Log Messages

    SnapSAN S3000/S5000 Path Manager Linux User Guide System Log Messages Event System log message Handling (Table) Phenomenon sps: Warning: Failover /dev/ddX (p) host:h channel:c id:s lun:l Failover Warning: A fault occurred on the active path and the active path is switched.
  • Page 52 SnapSAN S3000/S5000 Path Manager Linux User Guide Event System log message Handling (Table) Phenomenon sps: Warning: Path overflow (support to 32) /dev/ddX (p) host:h Path overflow channel:c id:s lun:l Warning: The number of paths to 1 device overflowed. You can use up to 32 paths.
  • Page 53 SnapSAN S3000/S5000 Path Manager Linux User Guide Event System log message Handling (Table) Phenomenon sps: Error: Trespass failed /dev/ddX (p) host:h channel:c id:s lun:l Changing the LU Owner was Error: Changing the owner of LU was failed failed sps: Info: Change ACT path/dev/ddX (p) host:h channel:c id:s lun:l...
  • Page 54: Proc File System

    SnapSAN S3000/S5000 Path Manager Linux User Guide Number Handling The number of paths is over the limit of PathManager. Review the system and reduce the number of paths which a server detects. Use the supported disk array. No serial number is registered to the Overland. It is likely to be configuration failure.
  • Page 55 SnapSAN S3000/S5000 Path Manager Linux User Guide Path information To check the path information of the PathManager driver, refer to the /proc/scsi/sps/ddX (X indicates the unit name such as a, b, c,...) file. Meaning of each entry displayed in (1) is same as /proc/scsi/scsi provided by OS.
  • Page 56 SnapSAN S3000/S5000 Path Manager Linux User Guide Device Status Device status * Description Abbreviation for NORMAL. Indicates that the operation status is normal. (Normal) Abbreviation for FAULT. Indicates that one (or some) of the paths is faulty. All paths are not faulty.
  • Page 57 SnapSAN S3000/S5000 Path Manager Linux User Guide Path State Transition 10400424-002 04/2013  3-22 ©2013 Overland Storage, Inc.
  • Page 58 SnapSAN S3000/S5000 Path Manager Linux User Guide Events Related to Path State Transition Number Event Description Active path If the load distribution mode is static, an alternate path becomes ACT ((i)-a) change when one of the following is occurred; • path disconnection •...
  • Page 59 SnapSAN S3000/S5000 Path Manager Linux User Guide 10400424-002 04/2013  3-24 ©2013 Overland Storage, Inc.
  • Page 60: Path Status Display

    SnapSAN S3000/S5000 Path Manager Linux User Guide Version information Check To check the version of PathManager, execute as shown below. < RHEL 6 > # spsadmin --version Utility Package: X.X.X Driver Package: X.X.X < RHEL 4, RHEL 5, SLES 10 >...
  • Page 61: Logical Unit

    SnapSAN S3000/S5000 Path Manager Linux User Guide Logical Unit To check the path statuses of all logical units managed by PathManager, use the "--lun" option of PathManager command. It shows the condition such as the active path, faulty path, and the configuration of the load distribution mode. You can execute the command on the terminal.
  • Page 62: Displaying Detail Information ("-V" Option)

    SnapSAN S3000/S5000 Path Manager Linux User Guide Position Meaning Number Status of the PathManager device Normal: All of the paths corresponding to this device are normal. Degraded: One or more paths corresponding to this device are faulty. Dead: No path corresponding to this device exists. Or all of the paths are faulty (all-path-fault).
  • Page 63 SnapSAN S3000/S5000 Path Manager Linux User Guide An example is shown below. "/dev/dda" is a case of FC connection, "/dev/ddr" is a case of iSCSI. The meaning of each item in the case of FC/SAS connection is shown below. Meaning of Each Item in the example ("-v" version (FC))
  • Page 64 SnapSAN S3000/S5000 Path Manager Linux User Guide Position Meaning Number SCSI-ID of SCSI address of the PathManager device LUN of SCSI address of the PathManager device Device name of PathManager device (/dev/ddX) Status of the PathManager device Normal: All of the paths corresponding to this device are normal.
  • Page 65 SnapSAN S3000/S5000 Path Manager Linux User Guide Position Meaning Number Bus ID associated with the HBA WWPN of the HBA WWPN of a port of the Overland Host Director Number of the Overland Port Number of the Overland Protocol of the Overland...
  • Page 66 SnapSAN S3000/S5000 Path Manager Linux User Guide Position Definition Number Product ID of the Overland Serial number of the Overland LUN (Logical Unit Number) of Overland Mode of Load Balancing (load distribution) FailOverOnly: Static Load Distribution mode RoundRobin: Round-robin mode...
  • Page 67: Path Patrol Daemon

    SnapSAN S3000/S5000 Path Manager Linux User Guide Path Patrol Daemon Basic Operation of the Path Patrol Daemon The PathManager driver automatically performs path switching if a fault occurs. The driver requires an external trigger to restore a faulty path. This trigger is given by the path patrol daemon.
  • Page 68: Enable/Disable Setting Of Path Monitoring

    SnapSAN S3000/S5000 Path Manager Linux User Guide Entry Description Default Minimum setting Intervals to monitor the active 60 seconds(*2) 10 seconds(*3) path and alternate path (*1) 600 seconds(*2) Intervals to try recovery 180 seconds 10 seconds processing on the faulty unit...
  • Page 69: Naming Rules

    SnapSAN S3000/S5000 Path Manager Linux User Guide Naming Rules Type Symbol Remarks Base name Fixed Unit name a,b,c…x,y,z One-to-one aa,ab,ac…ax,ay,az correspondence with ba,bb,bc… LUNs Partition number 1 to 15 Entire LUN when no number is specified For example, the device file for the first partition of the first LUN is named /dev/dda1. About major number, PathManager uses 245.
  • Page 70 SnapSAN S3000/S5000 Path Manager Linux User Guide *If the path detected an intermittent error is the last active (ACT) path, this function doesn't block the path to avoid the situation that no I/O path is active. Intermittent Error Monitoring Function is available with PathManager function.
  • Page 71 SnapSAN S3000/S5000 Path Manager Linux User Guide Disabling the Intermittent Error Monitoring To disable the intermittent error monitoring function, follow the procedures below. 10400424-002 04/2013  3-36 ©2013 Overland Storage, Inc.
  • Page 72: Getting Error History Function

    SnapSAN S3000/S5000 Path Manager Linux User Guide Message of Path Blocking when Intermittent Error Occurs When a path is blocked because of intermittent errors, the message shown below is output into the system-log in addition to a failover message. sps: Warning: Intermittent errors occurred. stopped Failback of path:p...
  • Page 73: Details Of Output

    SnapSAN S3000/S5000 Path Manager Linux User Guide But you cannot detect the occurrence of an important failure with the default operations of an OS. If you use this function, you can know the occurrence of a minor error which does not cause a failover, and you will get a chance to handle the error which is hard to detect, and this prevents an important failure which may occur in the future.
  • Page 74 SnapSAN S3000/S5000 Path Manager Linux User Guide 10400424-002 04/2013  3-39 ©2013 Overland Storage, Inc.
  • Page 75 SnapSAN S3000/S5000 Path Manager Linux User Guide 10400424-002 04/2013  3-40 ©2013 Overland Storage, Inc.
  • Page 76 SnapSAN S3000/S5000 Path Manager Linux User Guide 10400424-002 04/2013  3-41 ©2013 Overland Storage, Inc.
  • Page 77: Chapter 4 - Operation

    • All-path fault …All redundant paths with PathManager get faulty. <How to check> This example assumes that the normal path status is as shown below and a path fault occurred at the shaded path. 10400424-002 04/2013  ©2013 Overland Storage, Inc.
  • Page 78 SnapSAN S3000/S5000 Path Manager Linux User Guide -- Fault Pattern I -- 1. If the path info line of the faulty path is displayed (as the shaded part).Go on to the "YES" route. 10400424-002 04/2013  ©2013 Overland Storage, Inc.
  • Page 79 SnapSAN S3000/S5000 Path Manager Linux User Guide -- Fault Pattern II -- 2. If the path info line of the faulty path is not displayed (as the shaded part).Go on to the "NO" route. 10400424-002 04/2013  ©2013 Overland Storage, Inc.
  • Page 80: Restoration By Rebooting The System

    SnapSAN S3000/S5000 Path Manager Linux User Guide Restoration by Rebooting the System 3. If a path fault occurs, shut down the system, replace the faulty part, and then reboot the system. Rebooting the system restores PathManager. When the system is rebooted, execute step (v) described in next section "Restoration using operation...
  • Page 81 SnapSAN S3000/S5000 Path Manager Linux User Guide The restored path immediately enters the monitored (SACT) status. The path is monitored for 5 minutes by default. If no fault occurs within 5 minutes, the path gets out of the monitored status and enters the active status.
  • Page 82 SnapSAN S3000/S5000 Path Manager Linux User Guide 10400424-002 04/2013  ©2013 Overland Storage, Inc.
  • Page 83 SnapSAN S3000/S5000 Path Manager Linux User Guide To recover from the monitored status, the path patrol daemon must be running. Restoration of the Specified Path (all paths fault): An example of recovery from an all-path fault using operation commands is shown below.
  • Page 84 SnapSAN S3000/S5000 Path Manager Linux User Guide If all paths enter the faulty status, the following message is output to the system log. From this message, you can tell that all paths are faulty. sps: Error: All path fail /dev/dda If many messages as shown below are output, all paths may be faulty.
  • Page 85 SnapSAN S3000/S5000 Path Manager Linux User Guide (iii) After removing the cause of the fault, execute the spscmd command as shown below to restore path number 0. There is no restriction on the order in which paths are to be restored.
  • Page 86: Restoration By Scanning All Paths

    SnapSAN S3000/S5000 Path Manager Linux User Guide (vii) When the command is executed successfully, the following message is output to the system log: sps: Info: Recover HOT path /dev/dda (1) host:1 channel:0 id:0 lun:0 (viii) Execute the "spsadmin --lun" or refer to /proc/scsi/sps/dda to check that path number 1 has returned to the HOT status and the partition status has returned to NML.
  • Page 87 SnapSAN S3000/S5000 Path Manager Linux User Guide 10400424-002 04/2013  4-11 ©2013 Overland Storage, Inc.
  • Page 88 SnapSAN S3000/S5000 Path Manager Linux User Guide The meaning of each message is shown as below. 10400424-002 04/2013  4-12 ©2013 Overland Storage, Inc.
  • Page 89 SnapSAN S3000/S5000 Path Manager Linux User Guide Message Definition Rescanning under the hostX sd scan:hostX. Registering the path which is recognized dd scan:hostX. by rescanning under the hostX. Information about the path which has sps: Info: Attached path to /dev/dda been recognized by PathManager.
  • Page 90: Restoration By Iscsiadm Command

    SnapSAN S3000/S5000 Path Manager Linux User Guide Restoration by iscsiadm Command An example of recovery from a path fault (or all-path fault) using iscsiadm command is shown below. This restoration procedures are for iSCSI connection. <Example> -- If the initial status before the fault is as follows and the fault occurred on the shaded path.
  • Page 91 SnapSAN S3000/S5000 Path Manager Linux User Guide 10400424-002 04/2013  4-15 ©2013 Overland Storage, Inc.
  • Page 92 SnapSAN S3000/S5000 Path Manager Linux User Guide After removing the cause of the fault, execute the iscsiadm command as shown below to recover the paths. Some error messages may output (*1, *2), but they don't mean any problems with PathManager.
  • Page 93 SnapSAN S3000/S5000 Path Manager Linux User Guide When the kernel recognizes the path which is ready to use, the messages like below are output to the system log. 10400424-002 04/2013  4-17 ©2013 Overland Storage, Inc.
  • Page 94 SnapSAN S3000/S5000 Path Manager Linux User Guide 10400424-002 04/2013  4-18 ©2013 Overland Storage, Inc.
  • Page 95: Chapter 5 - Cautions And Restrictions

    1. PathManager corresponds with LVM (Logical Volume Manager) on the OSes below. But, a disk array units connected via iSCSI are not supported. • Red Hat Enterprise Linux AS/ES 4 (Kernel-2.6.9-42.EL) or later 10400424-002 04/2013  ©2013 Overland Storage, Inc.
  • Page 96 SnapSAN S3000/S5000 Path Manager Linux User Guide • Red Hat Enterprise Linux 5 (Kernel-2.6.18-53.el5) or later • Red Hat Enterprise Linux 5 Advanced Platform (Kernel-2.6.18-53.el5) or later • Red Hat Enterprise Linux 6 (Kernel-2.6.32.131.0.15.el6) or later • SUSE Linux Enterprise Server 10 (Kernel-2.6.16.60-0.21) or later PathManager does not correspond with Red Hat Enterprise Linux AS/ES 4 whose kernel is earlier than the above.
  • Page 97 SnapSAN S3000/S5000 Path Manager Linux User Guide Connection Kernel (Red Hat) Kernel (SUSE) 2.6.18-194.el5 or later 2.6.16.60-0.57.1 or later iSCSI FC / iSCSI 2.6.16.60-0.57.1 or later iSCSI FC / iSCSI 2.6.16.60-0.57.1 or later iSCSI FC / iSCSI 8. PathManager supports the Overland which has both FC and iSCSI connections if the function version of PathManager is 4.4.2 or later and on the OSes shown below.
  • Page 98: Appendix A - Commands

    If you execute the mkdd command, I/O performance may be decrease temporarily. Therefore, operate without any I/O to the PathManager devices if possible spsadmin command [Name] spsadmin - Controlling PathManager device / path and displaying its status. 10400424-002 04/2013  ©2013 Overland Storage, Inc.
  • Page 99 SnapSAN S3000/S5000 Path Manager Linux User Guide [Syntax] spsadmin --active target spsadmin --err [-m {simple | detail | counts}] [-t number | -a] [-v] target spsadmin --failback target spsadmin --help spsadmin --lun [-v] [target] spsadmin --mode spsadmin --rollback target spsadmin --standby [-v] target...
  • Page 100 SnapSAN S3000/S5000 Path Manager Linux User Guide By using -v suboption, displays in detail. spsadmin --mode Displays the settings shown below. 1. Cluster mode (Enable / Disable) 2. Intermittent Error Monitoring mode (Enable / Disable) spsadmin --rollback target Sets the path state (active / standby) of the logical unit specified in target into the initial state.
  • Page 101 In the upper one, two items are serial number of storage unit and logical disk number. But, logical disk number can not be used as same as the physical address description. To specify the logical disk on Overland SnapSAN S3000/S5000, use the lower description. It consists of only logical disk identifier (LunWWN).
  • Page 102 SnapSAN S3000/S5000 Path Manager Linux User Guide Command Mapping Recover a faulty path spscmd -recover [path | [serial]:HD] spsadmin --failback [path | [--serial serial] --hd HD] Suspend a path spscmd -rm [path | [serial]:HD] spsadmin --suspend [path | [--serial serial] --hd HD]...
  • Page 103 SnapSAN S3000/S5000 Path Manager Linux User Guide spsconfig -sanboot-cfg-add spsconfig -sanboot-cfg-del spsconfig -chk target [Description] It is used to set the auto startup and set the SAN-Boot environment. And it is used to check the correspondence between PathManager devices and SCSI devices.
  • Page 104: Command Of Function Version Less Than 5.1.0

    SnapSAN S3000/S5000 Path Manager Linux User Guide Command of Function Version Less than 5.1.0 This section refers to the following OSes • Red Hat Enterprise Linux AS/ES 4 • Red Hat Enterprise Linux 5 (Advanced Platform) • SUSE Linux Enterprise Server 10...
  • Page 105 HD. You can confirm the serial number and host director number from the configuration of Overland storage. Serial is omissible. If serial is omitted, controllers whose number is specified with HD on all storage units in the system become target.
  • Page 106 SnapSAN S3000/S5000 Path Manager Linux User Guide • Red Hat Enterprise Linux 4: PathManager ver. 3.1.0 or later. • Red Hat Enterprise Linux 5: PathManager ver. 4.3.1 or later. • SUSE Linux Enterprise Server 10 : PathManager ver. 4.3.1 or later.
  • Page 107 SnapSAN S3000/S5000 Path Manager Linux User Guide -chk{sddev| dddev}...Displays the PathManager devices corresponding to sddev if the SCSI devices are specified. Displays the SCSI devices corresponding to dddev if the PathManager devices are specified. (*2) -add dddev...Displays the optional setting to add the PathManager devices specified in dddev.
  • Page 108: Appendix B - Information Collection

    *3: If you execute the command on the following condition, some I/O error messages may be output. But there is no problem with the command execution and the system. • Some paths are failed on using FC connection. 10400424-002 04/2013  ©2013 Overland Storage, Inc.
  • Page 109: Appendix C - Cluster Mode Setup

    (*1) If you use application servers use Cluster Mode. How to Enable the Cluster Mode Follow the procedures below to enable the Cluster Mode. How to Disable the Cluster Mode Follow the procedures below to disable the Cluster Mode. 10400424-002 04/2013  ©2013 Overland Storage, Inc.
  • Page 110 SnapSAN S3000/S5000 Path Manager Linux User Guide 10400424-002 04/2013  ©2013 Overland Storage, Inc.
  • Page 111: Appendix D - Application Servers

    ![ if you use application servers X 1.0 (Version 1.1.0-1 or later) to 3.0 ] [ if you use application servers X 1.0 (until Version 1.0.3-1) ] [ if you use application servers SE Ver3.1 ] 10400424-002 04/2013  ©2013 Overland Storage, Inc.
  • Page 112: Updating Server1/Server2

    SnapSAN S3000/S5000 Path Manager Linux User Guide 7. Activation of application servers auto startup Execute the following command on all the servers: application servers is configured to start automatically when OS starts at next time. Confirm that the above commands are executed on all servers, then go on the next procedure.
  • Page 113 SnapSAN S3000/S5000 Path Manager Linux User Guide 6. Execute the following command to modify the starting configuration of services. application servers is configured to start automatically when OS starts at next time. Check that above (iii)-(vi) procedures are executed on the server2. After checking, go on to the next procedures.
  • Page 114 SnapSAN S3000/S5000 Path Manager Linux User Guide Server1 1. Move the groups you want to execute on server1 to server1 from server2. If you don't use application servers, execute clpgrp command on server2 to move the groups. 2. Check that each resource of moved groups is operating normally by using WebManager.
  • Page 115: Appendix E - Lvm Setup

    To add PathManager devices to LVM, follow the procedures described below. Execute the sg_scan command and confirm the SCSI disks recognized by the OS. If "Overland Storage" and "Model Name" are displayed, this SCSI disk is Overland (shown by the shaded part).
  • Page 116 SnapSAN S3000/S5000 Path Manager Linux User Guide In "filter" entries, "a" means accept, "r" means reject. You must specify the all partitions managed by LVM. For example, if sda2 and sdb1 are local disks managed by LVM, set as follows.
  • Page 117 SnapSAN S3000/S5000 Path Manager Linux User Guide Don't write the PathManager device name (ddX) to /etc/fstab. Write the logical volume name which is made by PathManager devices. Restart the OS. After the OS is restarted, confirm that LVM recognizes the PathManager devices by using pvdisplay and lvmdiskscan command.
  • Page 118: Removing Pathmanager Devices From Lvm

    SnapSAN S3000/S5000 Path Manager Linux User Guide If the alert message shown below is displayed as a result of pvdisplay or lvmdiskscan command, both the PathManager device (/dev/ddX) and the SCSI device (/dev/sdX) come from the same device are accepted in the "filter" entry of LVM setting file. In this case, modify the LVM setting file so that only the PathManager device (/dev/ddX) is accepted.
  • Page 119: Appendix F - Kdump Setup

    2. Write the setting that kdump loads the "dd_mod.ko". 3. Write the setting that the target of kdump is /dev/dda1. <Red Hat Enterprise Linux 6> Execute "spsconfig" command with "-kdump-cfg-add" option. #spsconfig -kdump-cfg-add /dev/dda >> /etc/kdump.conf 10400424-002 04/2013  ©2013 Overland Storage, Inc.
  • Page 120: Resetting The Kdump Setting

    SnapSAN S3000/S5000 Path Manager Linux User Guide Next, go to Step 4. <Red Hat Enterprise Linux 5> Modify the "/etc/modprobe.conf" file 1. Making the backup copy of modprobe.conf. (This will be used to reset) Make the backup copy of "/etc/modprobe.conf" to "/etc/modprobe.conf.sps".
  • Page 121: Suse Linux Enterprise Server 10

    SnapSAN S3000/S5000 Path Manager Linux User Guide 4. Reset kdump.conf and modprobe.conf by the backup copies which are made in "Setting up the kdump with a PathManager Device". The resetting the kdump setting is complete. SUSE Linux Enterprise Server 10 The following three RPM packages are required to use PathManager device as kdump output.
  • Page 122 SnapSAN S3000/S5000 Path Manager Linux User Guide If you specify an in-use partition as a destination of kdump, kdump breaks the file system of it when dumping. Therefore, be careful to set the configuration. (iii)Modify the "/etc/modprobe.conf" file. 1.Making a backup copy of "/etc/modprobe.conf".
  • Page 123 SnapSAN S3000/S5000 Path Manager Linux User Guide Move to the directory of compatible RPM files in installation CD-ROM. How to specify the directory is shown below. - If the kernel version of your system is 2.6.16-60-0.39.3, and its architecture is IA32 (smp) - 10400424-002 04/2013 ...
  • Page 124: Resetting The Kdump Setting

    SnapSAN S3000/S5000 Path Manager Linux User Guide With that, installation of PathManager driver for kdump is complete. Resetting the kdump setting To reset the setting of kdump with a PathManager device, follow the procedure: The backup copies are used to reset.
  • Page 125 SnapSAN S3000/S5000 Path Manager Linux User Guide The resetting the kdump setting is complete. 10400424-002 04/2013  ©2013 Overland Storage, Inc.
  • Page 126: Appendix G - Error Messages

    Some of PathManager RPM packages are already installed. ErrCode:[2-04] Failed to read the media. Failed to read the media. When installation, the current directory should be the one where the installer exists in the media. 10400424-002 04/2013  ©2013 Overland Storage, Inc.
  • Page 127 SnapSAN S3000/S5000 Path Manager Linux User Guide Error Message Handling No.* (refer to Handling List) Description ErrCode:[3-01] Couldn't find sps-driver-xxx.rpm in this media. 3 (RPMPKG) Couldn't find the PathManager driver RPM package corresponding to the kernel of this system. ErrCode:[3-02] Couldn't find sps-utils rpm in this media.
  • Page 128 SnapSAN S3000/S5000 Path Manager Linux User Guide Error Message Handling No.* (refer to Handling List ) Description ErrCode:[5-01] Failed to modprobe. 5 (DRIVER) Failed to probe the sps driver. ErrCode:[5-02] dd_mod.ko isn't found. Couldn't find the dd_mod.ko. ErrCode:[5-03] sps_mod.ko isn't found.
  • Page 129 SnapSAN S3000/S5000 Path Manager Linux User Guide Error Message Handling No.* (refer to Handling List) Description ErrCode:[8-01] Failed to patched for FC. 8 (PATCH) Failed to apply a patch for fibre channel in installation. ErrCode:[8-02] Failed to patched for iSCSI.
  • Page 130 SnapSAN S3000/S5000 Path Manager Linux User Guide Error Message Handling No.* (refer to Handling List) Description ErrCode:[11-01] Failed to sps-kdump rpm uninstallation. 9 (UNINSTALL) Failed to uninstall the sps-kdump RPM package. ErrCode:[11-02] Failed to sps-mcopt rpm uninstallation. Failed to uninstall the sps-mcopt RPM package.
  • Page 131 SnapSAN S3000/S5000 Path Manager Linux User Guide Handling No. Meaning How to do 5 (DRIVER) Driver Error sps-driver may fail to start, or some files related to sps-driver may be missing. Uninstall the PathManager and then install it again. 6 (MKDD) MKDD Error •...
  • Page 132: Index

    Disabling the Intermittent Error Monitoring 3-36 disk-info 3-5 Least I/O Size Mode (LeastSectors) 3-3 Dynamic Load Distribution 3-2 Limit of Paths and Disks 3-1 dynamic load distribution 3-3 Load Distribution Function 3-1 LoadBalance 3-5 Log Information 3-15 10400424-002 04/2013 @2013 Overland Storage, Inc. ...
  • Page 133 SnapSAN S3000/S5000 Path Management Linux User Guide Single Server Configuration 1-3 software update PR-iii Manual Uninstallation 2-20 sps.conf 2-23 Message of Path Blocking when Intermittent Error spsconfig command A-9 Occurs 3-37 static load distribution 1-1 Messages 3-16 Static Load Distribution (Failover Only) 3-2...

This manual is also suitable for:

Snapsan s5000

Table of Contents