hp disks with veritas

HP Surestore Disk Array XP Operating System Configuration Guide

H

Sun Solaris

Notice

© 2001, Hewlett-Packard Company.

Order number A5951-90903

E0201 A5951-96031

Hewlett-Packard Company makes no warranty of any kind with regard to this material, including, but not limited to, the implied warranties of merchantability and fitness for a particular purpose. Hewlett-Packard shall not be liable for errors contained herein or for incidental or consequential damages in connection with the furnishing, performance, or use of this material.

This document contains proprietary information, which is protected by copyright. No part of this document may be photocopied, reproduced, or translated into another language without the prior written consent of Hewlett-Packard. The information contained in this document is subject to change without notice.

Warranty

If you have any questions about the warranty for this product, contact your dealer or local HP sales representative.

Trademarks

Sun, Sun Microsystems, Solaris, and Ultra are registered trademarks or trademarks of Sun Microsystems, Inc.

Other reserved names are trademarks of the respective companies.

Safety notices

Any servicing, adjustment, maintenance, or repair must be performed only by authorized service-trained personnel.

Caution Denotes a hazard that can cause hardware or software damage.

WARNING Denotes a hazard that can cause personal injury or death.

Format conventions

literal Specifies text to be typed exactly as shown, such as commands, path names, file names, and directory names.

variable Indicates that you must supply a value.

output Denotes text displayed on the screen.

2

CONTENTS

Revision History 7Updates 8

1 Installation 9Installation Requirements 10

Differential SCSI Adapters (XP256 Only) 11Full-Speed (100 Mbps) Fibre Channel Interface 11Connectivity Options 12Supported Device Types 13

Installation Procedures 14Preparing to Connect to the Disk Array 15

Hardware Installation 15Remote Console PC and LUN Configuration Manager Installation 16

Identifying the Available SCSI Paths (XP256 only) 17Setting the Host Mode for the Ports 18Configuring the Fibre Channel Ports 19

Defining the SCSI/Fibre Channel Paths 21Adding the New SCSI Paths to the System 22Configuring the Host Fibre Channel Adapter 23

Setting the Disk and Device Parameters 40Connecting the Disk Array 42

Shut Down the Sun System 42Connect the Disk Array 42

3

Configuring the Disk Devices 44Verify New Device Recognition 44Verify Fibre Channel Host Adapter Recognition (Fibre Channel Only)

46Partition and Label the Devices 47

Creating and Mounting the File Systems 55Create the File Systems 55Create and Verify the Mount Directories 56Mount and Verify the File Systems 57Set and Verify the Auto-Mount Parameters 58

Operation With Veritas Volume Manager 60

2 Troubleshooting 61Error Conditions 62Verbose Mode 65

Examples of Error Messages 65Connection Problems 67Calling the HP Support Center 68

A Worksheet 69SCSI Path Worksheet 70

B Disk Parameters 71Parameter Tables for OPEN-K/3/8/9/E Devices 72SCSI TID Map for Fibre Channel Adapters 92Byte Information Table 105Physical Partition Size Table 106Host Bus Adapter Modes 108

C Supported Host Modes 111

4 HP Surestore Disk Array XP Operating System Configuration Guide: Sun Solaris

D SNMP Remote Disk Array Management 115

E Online Installation and Deinstallation of Devices 117

Glossary 119

Index 131

5

Revision History

September 15, 1999 Open-8 emulation added.

January 15, 2000 Content extensively revised and reorganized.

June 1, 2000 Added support for XP512. Content reorganized and revised.

February 1, 2001 Added appendixes B, C, D, and E.Added glossary.

7

Updates

For the most current information about HP Surestore XP products, visit the support web site:

www.hp.com/support/stressfree

For information about product availability, configuration, and connectivity, consult your HP account representative.


http://www.hp.com/support/stressfree

1INSTALLATION

This manual describes the requirements and procedures for connecting the XP family of disk arrays to a host system and configuring the new disk array for operation with the Sun Solaris operating system.

Installation of the HP Surestore Disk Array XP is performed by users with administrator privileges and the HP service representative. The HP service representative performs the physical installation of the disk array and formats the disk devices. The user configures the Sun system for the new devices with assistance as needed from the HP service representative.

The HP account representative can assist in determining the supported configurations for your system.

9

Installation Requirements

The disk array can support concurrent attachment to multiple UNIX-based and PC-server platforms as well as S/390 mainframe systems.The disk array operates with multihost applications and host clusters, and is designed to handle very large databases as well as data warehousing and data mining applications that store and retrieve terabytes of data.

The disk array can be configured with Fibre Channel ports and/or serial interface ports (compatible with ESCON® protocol) to provide connectivity with the Solaris host as well as S/390® mainframe hosts.

Contact your HP account representative for specific installation requirements, such as software versions and hardware configurations.

To install the disk array into the host system, ensure that the environment conforms to these requirements:

• HP Surestore Disk Array XP

• Sun Enterprise server

• Sun Solaris operating system, version 2.5.1, 2.6, 7.0, or 8.0

Confirm with your Sun service representative that the most current OS patches are installed.

• (Recommended) HP Surestore Command View XP software

• (Optional and recommended) LUN Configuration Manager XP remote control software product

LUN Configuration Manager enables you to define and reconfigure the SCSI-to-logical device (LDEV) paths for the disk array as needed, change the host mode of each SCSI port for connection with other open-system hosts as needed, and access the remote service information messages (R-SIMs) generated by the disk array. LUN Configuration Manager runs on the remote console PC and can support up to eight disk arrays.

(HP service representative) If LUN Configuration Manager is not used, you must configure the SCSI-to-LDEV paths by using the service processor (SVP) of the disk array.


There may be restrictions on relevant firmware or driver versions used. An HP service representative can provide information on supported firmware and driver versions.

Differential SCSI Adapters (XP256 Only)

For the XP256, the system must have differential SCSI-2 adapters. Do not attach the disk array to any single-ended SCSI device. Ultra-wide differential or fast-wide differential (FWD) adapters are recommended. The SCSI cable length attached to each SCSI adapter must not exceed 20 meters (65.6 feet). The disk array supports up to two Paralan SCSI bus extenders to extend cable length to a maximum of 60 meters (196.8 feet).

Full-Speed (100 Mbps) Fibre Channel Interface

The disk array supports full-speed (100 MB/s) Fibre Channel interface, including:

• short-wave non-OFC (open fibre control) optical interface

Do not connect any OFC-type connector to the disk array.

• multimode optical cables with SC connectors

• point-to-point (P-P), arbitrated loop (FC-AL), and fabric topologies

Caution The total fiber cable length attached to each Fibre Channel adapter must not exceed 500 meters (1,640 feet).

Installation 11

For information about supported optical cables, adapters, hubs, and switches, contact your HP service representative.

Connectivity Options

XP256

The XP256 disk array supports Fibre Channel, ESCON, and differential SCSI host connectivity.

XP512/XP48

The XP512 and XP48 disk arrays support Fibre Channel and ESCON host connectivity.

Table 1. Driver Requirements for Fibre Channel Adapters

HBA OS Version Driver Version

Emulex LP7000 2.6(minimum)

4.02d

JNI FCI-1063 (PCI) 2.6(minimum)

2.5.8-HIT or higher

JNI FC64-1063 (Sbus) 2.6(minimum)

2.5.8-HIT or higher

Sun X6729ASun X6730A

2.6(minimum)

Solaris native driver 107280-05 (PCI bus) or105356-12


Supported Device Types

The disk array supports the following types of devices:

• OPEN-K/3/8/9/E devices

The disk array supports OPEN host emulation mode devices.

• LUSE devices (OPEN-x*n)

The Logical Unit Size Expansion (LUSE) feature of the disk array enables you to configure custom-size LDEVs, which are larger than standard OPEN-K/3/8/9/E LDEVs.

• CVS devices (OPEN-x CVS)

The Custom Volume Size (CVS) feature of the disk array enables you to configure CVS devices. The CVS capability allows you to “slice up” a single LDEV into several smaller LDEVs to best fit application needs and improve host access to frequently used files.

• CVS LUSE devices (OPEN-x*n CVS)

CVS LUSE devices combine the CVS and LUSE features of the disk array. The CVS feature is used first to create custom-size devices. Then, the LUSE feature is used to combine these CVS devices. You can combine from 2 to 36 CVS devices into one CVS LUSE device.

Installation 13

Installation Procedures

Installation and configuration of the disk array requires the user and the HP service representative to perform the following procedures.

To install and configure the disk array:

1. (HP service representative only) Prepare to connect the disk array (page 15).

2. (XP256 only) Identify the available SCSI paths (page 17).

3. Define the SCSI/Fibre Channel paths (page 21).

4. Set the disk and device parameters (page 40).

5. Connect the disk array (page 42).

6. Configure the disk devices (page 44).

7. Create and mount the file systems (page 55).


Preparing to Connect to the Disk Array

The disk array comes with all hardware and cabling required for installation. Installation of the disk array includes these activities:

• hardware installation

• remote console and LUN Configuration Manager installation

The user configures the host system with assistance as needed from the HP service representative.

Hardware Installation

The HP service representative installs the disk array, including these tasks:

• final hardware assembly

The HP service representative performs hardware installation as specified in the disk array maintenance manual.

• loading microprogram updates for SCSI or Fibre Channel support

• installing SCSI or Fibre Channel adapters and cabling

The total fibre cable length attached to each Fibre Channel adapter must not exceed 500 meters (1,640 feet). Do not connect any open fibre control (OFC) type connector to the disk array.

Caution Do not connect or disconnect fibre cabling that is being actively used for I/O. This can cause the system to hang. Always confirm that the devices on the fibre cable are offline before connecting or disconnecting the fibre cable.

• installing and formatting the logical devices (LDEVs) using the internal service processor (SVP) of the disk array.

Obtain the desired LDEV configuration information from the user, including the desired number of OPEN-K/3/8/9/E, CVS, LUSE, and multiplatform (Data Exchange) devices.

Installation 15

Fabric

Connect the disk array port to the F-port of the fabric switch. Connect the host adapter to the FL-port of the fabric switch.

Disk Array FC Port

The Fibre Channel topology parameters for each disk array Fibre Channel port depend on the type of device to which the disk array port is connected. Determine the topology parameters supported by the device, and set your topology accordingly. See “Configuring the Fibre Channel Ports” (page 19). The type of disk array port is also important.

Remote Console PC and LUN Configuration Manager Installation

The user or HP service representative can install the remote console PC and HP Surestore LUN Configuration Manager XP. You use the LUN Configuration Manager software on the remote console PC to set the host modes for the disk array ports and configure the Fibre Channel ports.

Related Information For instructions on installing the LUN Configuration Manager software, see the product manual:

HP Surestore LUN Configuration Manager XP: User’s Guide


Identifying the Available SCSI Paths (XP256 only)

Identify the device information for existing peripheral devices to avoid duplicating any SCSI target IDs (TIDs) during disk array installation.

The HP service representative performs this activity.

To verify the current system configuration for SCSI:

1. Verify that all existing SCSI devices are powered on and properly connected.

2. Log in to the system as root.

3. Display the device information for all peripheral devices using the dmesg command with the output piped to more. The device information includes the SCSI bus number, SCSI TID, and LUN.

Example

# dmesg | moreMar 16 14:09SunOS Release 5.5 Version Generic_Patch [Unix(R) System V Release 4.0]Copyright (C) 1983-1995, Sun Microsystems, Inc.pac: enabled - SuperSPARCcpu0: TI,TMS390Z50 (mid 8 impl 0x0 ver 0x3 clock 50 MHz)mem = 81920K (0x5000000)avail mem = 71004160Ethernet address = 8:0:20:1a:a6:73root nexus = SUNW,SPARCstation-20iommu0 at root: obio 0xe0000000sbus0 at iommu0: obio 0xe0001000espdma0 at sbus0: SBus slot f 0x400000dma2 at sbus0: SBus slot 1 0x81000esp0 at espdma0: SBus slot f 0x800000 sparc ipl 4esp2 at dma2: SBus slot 1 0x80000 SBus level 3 sparc ipl 5esp0 at SBus slot f 0x800000 pri 4 (onboard)sd1 at esp0 target 1 lun0

sd1 is /iommu@f,e0000000/sbus@f,e0001000/espdma@f,400000/esp@f,800000/sd@1,0 <SUN1.05 cyl 2036 alt 2 hd 14 sec 72> .....TID=1 LUN=0 DASD devicesd3 at esp0 target 3 lun 0

sd3 is /iommu@f,e0000000/sbus@f,e0001000/espdma@f,400000/esp@f,800000/sd@3,0 <SUN1.05 cyl 2036 alt 2 hd 14 sec 72> .....TID=3 LUN=0 DASD devicesd6 at esp0 target 6 lun0

Installation 17

sd6 is /iommu@f,e0000000/sbus@f,e0001000/espdma@f,400000/esp@f,800000/sd@6,0 <CD-ROM Disc for SunOS Installation cyl 2048 alt 0 hd 1 sec 640> .....TID=6 lUN=0 CD-ROM device

This example shows the following device information:

SCSI disk sd1 is connected to SCSI bus esp0 and has SCSI target ID=1 and LUN=0.



4. For each SCSI bus, identify and record the available SCSI TIDs and LUNs that can be assigned to the disk array devices. See “SCSI Path Worksheet” (page 70).

Setting the Host Mode for the Ports

Use LUN Configuration Manager to set the host mode of each port for the supported HBA. If the remote LUN Configuration Manager feature is not installed, the HP service representative can set the host modes for you by using the SVP.

The disk array ports have special modes which must be set for various middleware environments (for example, VERITAS VxVM-DMP for Solaris).

The required host mode setting for using the disk array in a Solaris environment with Solaris VxVM-DMP mode is 09.


For additional host mode configurations, see appendix B, “Host Bus Adapter Modes” (page 108).

Related Information For information about how to set the host mode with LUN Configuration Manager, see the product manual:


Configuring the Fibre Channel Ports

Configure the Fibre Channel ports to define the fibre topology parameters (for example, arbitrated loop) and port addresses.

Configuring Topology Parameters

Use the LUN Configuration Manager software to define the topology parameters for each Fibre Channel port.

Select the appropriate settings for each Fibre Channel port based on the device to which the port is connected. Determine the topology parameters supported by the device, and set your topology accordingly. The type of port is also important.

In a heterogeneous fabric switched environment, it is necessary to implement Secure Manager XP.

When you are finished configuring the FC ports (and SCSI paths), you can exit the LUN Configuration Manager software.

HBA Host Mode for Sun Solaris

Emulex LP7000 09

JNI FCI-1063 (PCI)JNI FC64-1063 (Sbus)

09

Sun X6729ASun X6730A

09

Installation 19

Related Information For information about how to configure Fibre Channel ports with LUN Configuration Manager, see the product manual:


If the remote LUN Configuration Manager feature is not installed, please contact your HP service representative for information on LUN Configuration Manager configuration services.

Configuring the Port Address

In fabric environments, the port addresses are assigned automatically by fabric switch port number and are not controlled by the port settings. In arbitrated loop environments, the port addresses are set by entering an arbitrated-loop physical address (AL-PA) or loop ID. Fibre Channel protocol uses the AL-PAs to communicate on the Fibre Channel link, but the software driver of the platform host adapter translates the AL-PA value assigned to the port to a SCSI target ID (TID). The disk array supports up to 256 LDEVs per fibre-channel port.

Appendix B (page 92) shows the available AL-PA values ranging from 01 to EF.

Loop ID Conflicts To avoid conflicts, the AL-PAs must be unique for each device on the loop. Do not use more than one port address with the same TID in the same loop (for example, addresses EF and CD both have TID 0). If a loop ID conflict occurs with a Fibre Channel port, the disk array automatically changes the port's AL-PA to resolve the conflict condition.

Table 2. Fibre Topology Settings on the Remote Console

Fabric Parameter

Connection Parameter Provides

ON FC-AL FL-port (public arbitrated loop)

ON Point-to-Point F-port (fabric port)

OFF FC-AL AL-port (private arbitrated loop)

OFF Point-to-Point Not supported


Defining the SCSI/Fibre Channel Paths

Use the LUN Configuration Manager feature of the Remote Control product to define the LUN mapping (SCSI/Fibre Channel-to-LDEV paths) for the devices on the disk array. If LUN Configuration Manager is not installed, the HP service representative configures the LUN mapping by using the SVP of the disk array.

To define the SCSI/Fibre Channel paths for the new devices:

1. Determine the SCSI TID and LUN for each new device.

2. Use LUN Configuration Manager to define the SCSI/Fibre Channel paths for each new SCSI/Fibre Channel device. Use only available TIDs and LUNs. Do not duplicate any TIDs or LUNs on the SCSI/Fibre Channel buses.

Caution Do not duplicate any SCSI target IDs on the SCSI buses.

SCSI TID 7 (first priority) is usually assigned to the SCSI initiator, SCSI TID 6 (second priority) is usually assigned to the CD-ROM device, and SCSI TID 3 is usually assigned to the boot device. Make sure not to use the TIDs assigned to these devices for the disk array. Slow devices (for example, tape drives) should be given higher SCSI priority than fast devices (for example, disk drives).

To use ultra SCSI transfer with the disk array, the HP service representative must set the host mode of each disk array ultra SCSI port to SCSI (Ultra 1A) or Fibre (FWD 09), using the LUN Configuration Manager XP software. The HP service representative can also set the host mode by using the SVP of the disk array.

3. Use LUN Configuration Manager to define the port ID and topology parameters for each SCSI/Fibre Channel port. The port ID takes the place of the SCSI/Fibre Channel target ID in a Fibre Channel environment. Connectivity is limited to eight LUNs per Fibre Channel port.

Installation 21

4. (HP service representative) Verify that the status of the SCSI/Fibre Channel adapters and LDEVs is NORMAL and check the SCSI/Fibre Channel path configuration to ensure that all target IDs for the host system are unique.

Adding the New SCSI Paths to the System

Now that you have determined and defined the SCSI paths for the new disk arrays, you must add the new SCSI paths to the driver configuration file (/kernel/drv/sd.conf) so that the system will recognize the new devices. You must add the paths for all new devices, including OPEN-K/3/8/9/E. When the Sun system boots up, the SCSI paths defined in the driver configuration file are verified. If the path for a device is not defined in this file, the Sun system will not recognize the device on that SCSI path.

Caution When the Sun system boots up, the SCSI paths are verified in the order they appear in the driver configuration file. To ensure that the system can boot properly even if you make a mistake in the driver configuration file, make sure the system boot device is defined before the rest of the devices. For example, if you add a new device before the boot device and accidentally type a colon (:) instead of a semi-colon (;), the system will stop checking the driver configuration file when it encounters the error, and the boot operation will fail.

Unnecessary entries in the sd.conf file can lead to a long delay in the boot procedure. If there are a large number of nonexistent LUNs, the Solaris sd driver must probe for each missing LUN for the sd timeout period specified in the /etc/system file.

To add the newly installed disk array devices to the system:

1. Power on the system.

2. Log in as root.

3. Make a backup copy of the /kernel/drv/sd.conf driver configuration file.

Example # cp -ip /kernel/drv/sd.conf /kernel/drv/sd.conf.standard


4. Edit the /kernel/drv/sd.conf file using the UNIX vi editor.

Add two lines for each new device, as shown. Enter the correct SCSI TID and LUN for each device.

Example # Copyright (c) 1992, by Sun Microsystems, Inc.##ident "@(#)sd.conf 1.8 93/05/03 SMI”

name="sd" class="scsi" target=10 lun=0 hba="fca-pci0";name="sd" class="scsi" target=10 lun=1 hba="fca-pci0";name="sd" class="scsi" target=10 lun=2 hba="fca-pci0";

name="sd" class="scsi"target=0 lun=0;


name="sd" class="scsi"

5. Save the changes and exit the vi editor.

Configuring the Host Fibre Channel Adapter

To ensure that the host configuration is correct, verify recognition of the Fibre Channel Adapter (FCA) and the FCA driver. For supported drivers, see “Host Bus Adapter Modes” (page 108) in appendix B.

To verify the Fibre Channel host configuration:

1. Log in to the system as root. Verify that all existing devices are powered on and properly connected to the system.

2. Display the host configuration using the dmesg command. The fibre information includes the recognition of the Fibre Channel adapter, the SCSI bus characteristics, the worldwide name, and the FCA driver. Make sure that the host recognizes these four classes. If this information is not displayed or if error messages are displayed, the host environment may not be configured properly.

Installation 23

Example (JNI FC-1063)

# dmesg

Nov 9 23:14ems, Inc.mem = 65536K (0x4000000)avail mem = 60129280Ethernet address = 8:0:20:92:32:48root nexus = Sun Ultra 1 SBus (UltraSPARC 167MHz)sbus0 at root: UPA 0x1f 0x0 ...espdma0 at sbus0: SBus0 slot 0xe offset 0x8400000esp0: esp-options=0x46esp0 at espdma0: SBus0 slot 0xe offset 0x8800000 Onboard device sparc9 ipl 4sd0 at esp0: target 0 lun 0sd0 is /sbus@1f,0/espdma@e,8400000/esp@e,8800000/sd@0,0 <SUN2.1G cyl 2733 alt 2 hd 19 sec 80>sd6 at esp0: target 6 lun 0sd6 is /sbus@1f,0/espdma@e,8400000/esp@e,8800000/sd@6,0fca0: JNI Fibre Channel Adapter (1062 MB/sec), model FC Verify thatfca0: SBus 1: IRQ 4: FCODE Version 11.0.9 [1a6384]: SCSI ID 125: AL_PA 01

these itemsfca0: Fibre Channel WWN: 100000e0690000d5 are listed.fca0: FCA Driver Version 2.2.HIT.03, Oct 09, 1999 Solaris 2.5, 2.6çfca0: All Rights Reserved.fca0: < Total IOPB space used: 1125824 bytes >fca0: < Total DMA space used: 565277 bytes >root on /sbus@1f,0/espdma@e,8400000/esp@e,8800000/sd@0,0:a fstype ufszs0 at sbus0: SBus0 slot 0xf offset 0x1100000 Onboard device sparc9 ipl 12zs0 is /sbus@1f,0/zs@f,1100000zs1 at sbus0: SBus0 slot 0xf offset 0x1000000 Onboard device sparc9 ipl 12zs1 is /sbus@1f,0/zs@f,1000000keyboard is </sbus@1f,0/zs@f,1000000> major <29> minor <2>mouse is </sbus@1f,0/zs@f,1000000:b> major <29> minor <3>stdin is </sbus@1f,0/zs@f,1000000> major <29> minor <2>


Example (Emulex LightPulse 7000)

# dmesg

Nov 6 18:55cpu0: SUNW,UltraSPARC-IIi (upaid 0 impl 0x12 ver 0x13 clock 333 MHz)SunOS Release 5.6 Version Generic_105181-14 [UNIX(R) System V Release 4.0]Copyright (c) 1983-1997, Sun Microsystems, Inc.mem = 262144K (0x10000000)avail mem = 256278528Ethernet address = 8:0:20:a7:0:d9root nexus = Sun Ultra 5/10 UPA/PCI (UltraSPARC-IIi 333MHz)pci0 at root: UPA 0x1f 0x0pci0 is /pci@1f,0PCI-device: pci@1,1, simba #0PCI-device: pci@1, simba #1dad0 at pci1095,6460 target 0 lun 0 : :NOTICE: Emulex LightPulse FC SCSI/IP 3.39m-COMBO Verify that

these itemsNOTICE: Device Path for interface lpfc0: are listed.pci10df,f7000 is /pci@1f,0/pci@1/fibre-channel@3NOTICE: lpfc0: WWPN:10:00:00:00:c9:20:cb:b7 WWNN:10:00:00:00:c9:20:cb:b7ç dump on /dev/dsk/c0t0d0s1 size 131520K

Installation 25

Example(Sun Host Adapter)

# dmesg

Jan 24 09:48major <37> minor <0>mouse is </pci@1f,0/pci@1,1/ebus@1/su@14,3062f8> major <37> minor <1>stdin is </pci@1f,0/pci@1,1/ebus@1/su@14,3083f8> major <37> minor <0>SUNW,m64B0 is /pci@1f,0/pci@1,1/SUNW,m64B@2m64#0: 1152x900, 2M mappable, rev 4750.7cstdout is </pci@1f,0/pci@1,1/SUNW,m64B@2> major <8> minor <0>se0 at ebus0: offset 14,400000se0 is /pci@1f,0/pci@1,1/ebus@1/se@14,400000SUNW,hme0: CheerIO 2.0 (Rev Id = c1) FoundSUNW,hme0 is /pci@1f,0/pci@1,1/network@1,1SUNW,hme0: Using Internal TransceiverSUNW,hme0: 100 Mbps half-duplex Link Up

<HP-OPEN-3-5244 cyl 3336 alt 2 hd 15 sec 96>fdthree0 at ebus0: offset 14,3023f0fdthree0 is /pci@1f,0/pci@1,1/ebus@1/fdthree@14,3023f0ecpp0 at ebus0: offset 14,3043bcecpp0 is /pci@1f,0/pci@1,1/ebus@1/ecpp@14,3043bcpower0 at ebus0: offset 14,724000power0 is /pci@1f,0/pci@1,1/ebus@1/power@14,724000pseudo-device: winlock0winlock0 is /pseudo/winlock@0atapicd2 at pci1095,6460 target 2 lun 0atapicd2 is /pci@1f,0/pci@1,1/ide@3/atapicd@2,0pseudo-device: lockstat0lockstat0 is /pseudo/lockstat@0pseudo-device: vol0vol0 is /pseudo/vol@0pseudo-device: llc10llc10 is /pseudo/llc1@0SUNW,CS42310 at ebus0: offset 14,200000SUNW,CS42310 is /pci@1f,0/pci@1,1/ebus@1/SUNW,CS4231@14,200000ifp0: LIP reset occurred; cause f8f7ifp0: LIP occurred; cause f8f7ifp0: Loop upifp0: Loop reconfigure in progressifp0: Loop reconfigure donepci1077,21000 is /pci@1f,0/pci@1/SUNW,ifp@3ifp0: Chip 2100 Rev 3; Firmware Version: 1.17.30ssd12 at pci1077,21000: name w50000e10fff62200,0, bus address efssd12 is /pci@1f,0/pci@1/SUNW,ifp@3/ssd@w50000e10fff62200,0 <HP-OPEN-3-5245 cyl 3336 alt 2 hd 15 sec 96>ssd13 at pci1077,21000: name w50000e10fff62200,1, bus address efssd13 is /pci@1f,0/pci@1/SUNW,ifp@3/ssd@w50000e10fff62200,1 <HP-OPEN-3-5245 cyl 3336 alt 2 hd 15 sec 96>


Configuring the JNI Driver

To configure the JNI FCI-1063 or FC64-1063, edit the fca*.conf file in the/kernel/drv/ directory. For 32-bit SBus adapters, configure the /kernel/drv/fca.conf file. For 64-bit SBus adapters, configure the /kernel/drv/fca-pci.conf file.

Add the following descriptions to the configuration file:

timeout_reset_enable = 1link_recovery_delay = 500

When using a switched environment, set the following variable:

def_hba_binding = "non-jni*";

When using VERITAS Volume Manager (VxVM) Dynamic Multi Pathing (DMP), set the following values:

Recovery_attempts = 5Failover = 30

Editing the /kernel/drv/fca-pci.conf file

To edit the /kernel/drv/fca-pci.conf file:

1. Log in as root.

2. Make a backup of fca-pci.conf:

cp /kernel/drv/fca-pci.conf /kernel/drv/fca-pci.bk

3. Use vi to edit the fca-pci.conf file.

4. When a command to a target times out, the driver can attempt to clear the problem in two ways: (timeout_reset_enable = 1) will reset the target, while (timeout_reset_enable = 0) will send an abort exchange (ABTS_LS) request to the target. Enter:

timeout_reset_enable = 1

5. Set the delay between link up state and login recovery. This delay helps ensure link stability before recovery of communications to ports. The delay is in milliseconds with a 10 millisecond resolution. Enter:

link_recovery_delay = 500

Installation 27

6. Define the number of times login_recovery is attempted. Enter:

recovery_attempts = 5

7. Define the number of seconds after link failure before failing all pending commands on targets. Enter:

failover = 30.

8. Save your changes and exit the text editor.

9. Reboot the Sun system to establish the I/O TOV setting.

Connecting to Fibre Switch

The JNI port adapter should be connected to a switch F-Port. The disk array Fibre Channel port should be connected to a switch FL-Port.

Use the zoning function when attempting to connect multiple types of servers to the disk array via the same switch.

To enable the fibre switch connection:

1. Edit the /kernel/drv/fca.conf file.

2. Enter:

fca_nport = 1


Example

## fca-pci.conf - JNI FCA DRIVER (Solaris SCSI-IP HBA) CONFIGURATION FILE

# Configuration variable scsi-initiator-id# Type: integer, 0-125; default: none (must be explicitly set for PCI driver)# Defines the adapters SCSI ID (and hence FC AL_PA) on the loopscsi-initiator-id = 0x7d;

# Configuration flag fca_nport# Type: boolean; default: 0 (false)# If false (0), then fca initializes on a loop# If true (1), then fca initializes as an N_Port# and fabric operation is enabledfca_nport = 1;

# Configuration flag public_loop# Type: boolean; default: 0 (false)# If false (0), then fca-pci initializes according to what fca_nport is set to # If true (1), then fca initializes as an NL_Port on a public loop# and fabric operation is enabled via the FLPort of the switch


# if public_loop = 1, then fca_nport is overridden to be 0public_loop = 0;

# Configuration target_controllers# Type: integer, count; default: 126# Defines the number of target controllers to support.# The absolute maximum is 5000.# If set to greater than 5000, the driver will reset to 5000.target_controllers = 126;

# Configuration flag ip_disable# Type: boolean; default; 0 (false)# if false (0), then the IP side of the driver is enabled# if true (1), then the IP side of the driver is completely disabledip_disable = 1; # Configuration variable qfull_retry_count# Type: integer, count; defalt: 0 # Defines the number of times a command is retried by the HBA if a target # rejects it with a queue full status. # if 0, then the HBA will retry forever# if > 0, then the HBA tries at least qfull_retry_count times # if qfull_retry_count exceeded, then the HBA returns the command to the target # driver with reason set to transport error. qfull_retry_count = 0; # Configuration variable qfull_retry_interval# Type: integer, milliseconds; default: 1000 # Time the HBA waits before retrying a rejected command due to queue full qfull_retry_interval = 1000;

# Configuration variable failover# Type: integer, seconds; default: 30# Defines the number of seconds after target is declared "offline" # before target is declared "failed" and all pending commands # are flushed back to the application.# See failover_extension for additional info. failover = 30;

# Configuration variable failover_extension# Type: integer, seconds; default: 0# Extends a target's failover period by this number of seconds to perform target rediscovery.# If defined and the target has pending commands at the time it is declared "failed",# the target will first be declared "missing" for this period before being declared "failed".

# When a target is declared "missing" the link will be reset once and targets will be rediscovered. # This provides a "last chance" opportunity for the target to go "online" before # the target is declared "failed" and all pending commands are flushed.# See failover for additional info. failover_extension = 0;

# Configuration variable recovery_attempts# Type: integer, count; default: 5# Defines the number of times login_recovery is attempted before failedrecovery_attempts = 5;

# Configuration flag class2_enable# Type: boolean; default: 0# If set to 1 (true), then FC Class 2 exchanges (ACK_1 model) are enabled for# devices which support it [even when connected to a loop].

Installation 29

class2_enable = 0;

# Configuration variable fca_heartbeat# Type: value, microseconds; default: 0# Defines the number of microseconds between "heartbeat" frames.# Only used for debugging.fca_heartbeat = 0;

# Configuration flag reset_glm# Type: boolean; default: 0# If non-zero, then the Gigabit Link Module will be reset before# adapter initialization. This is a workaround for specific boot-up# conditions.reset_glm = 0;

# Configuration flag timeout_reset_enable# Type: boolean; default: 0# When a command times out to a target, the driver can attempt to clear the problem in two ways:# 1. (timeout_reset_enable = 1) Reset the target.# 2. (timeout_reset_enable = 0) Send an abort exchange (ABTS_LS) request to the target.timeout_reset_enable = 0;

# Configuration flag busy_retry_delay# Type: unsigned int; default: 100# Sets delay between retries after a SCSI device returns a BUSY response for a command.# The delay is in milliseconds with a 10 millisecond resolution.busy_retry_delay = 500;

# Configuration flag link_recovery_delay# Type: unsigned int; default: 1000# Sets delay between link up state and login recovery.# This delay helps ensure link stability before recovery of communications to ports.# The delay is in milliseconds with a 10 millisecond resolution.# for combined SCSI/IP operation, this should be set to at least 1000link_recovery_delay = 1000;

# Configuration flag scsi_probe_delay# Type: unsigned int, milliseconds; default: 500# Sets delay before SCSI probes are allowed to occur during boot.# This allows time for the driver to build a network port list for target binding.# The delay is in milliseconds with a 10 millisecond resolution.scsi_probe_delay = 5000;

# Configuration flag def_hba_binding# Type: string; default: "fca-pci*" (means all target/lun instances will be initialized by all fca-pci instances)# Sets the default HBA binding for every target/lun instance which does not explicitly define one.# - A "*" following an hba name indicates all instances of that hba driver# *See technote for details on hba bindingsdef_hba_binding = "non-jni*";

# Configuration flag def_wwXn_binding where X is either n for node or p for port.# Type: string; default: "$xxxxxxxxxxxxxxxx" (means WWXN is "static don't care")# Sets the 16 digit hexidecimal default wwXn binding for every target/lun instance which does not # explicitly define one.# - A "$" preceding the string indicates static binding enabled# - A "x" in place of a digit indicates "don't care" for that digit# *See technote for details on wwn bindingsdef_wwpn_binding = "$xxxxxxxxxxxxxxxx";def_wwnn_binding = "$xxxxxxxxxxxxxxxx";


# Configuration flag def_port_binding# Type: string; default: "xxxxxx" (means PORT is "non-static don't care")# Sets the 6 digit hexidecimal default port binding for every target/lun instance which does not # explicitly define one.# - A "$" preceding the string indicates static binding enabled# - A "x" in place of a digit indicates "don't care" for that digit# *See technote for details on port bindingsdef_port_binding = "xxxxxx";

# Configuration flag fca_verbose# Type: boolean; default: 1# Determines how many messages are displayed directly to the console. # - A "0" will quiet the driver messages to the console, but still print them to the # system message log. # (NOTE: a "boot -v" will override this setting and make the driver verbose again)# - A "1" will make the driver print all messages to the console and to the system # message log.fca_verbose = 0;

target10_wwpn="500060e802757015";target10_hba="fca-pci0";

Example(/kernel/drv/sd.conf)

## Copyright (c) 1992, by Sun Microsystems, Inc.##ident"@(#)sd.conf1.893/05/03 SMI"

## Please use the following conventions when defining persistent bindings for the JNI driver. # Always add the definitions at the top of this file.## Port CL1-J#name="sd" class="scsi" target=10 lun=0 hba="fca-pci0";name="sd" class="scsi" target=10 lun=1 hba="fca-pci0";name="sd" class="scsi" target=10 lun=2 hba="fca-pci0";name="sd" class="scsi" target=10 lun=3 hba="fca-pci0";name="sd" class="scsi" target=10 lun=4 hba="fca-pci0";name="sd" class="scsi" target=10 lun=5 hba="fca-pci0";name="sd" class="scsi" target=10 lun=6 hba="fca-pci0";name="sd" class="scsi" target=10 lun=7 hba="fca-pci0";## End of XP definitions





Installation 31










target=13 lun=0;



Connecting to Fibre Channel Arbitrated Loop

If there are multiple servers on loop and two or more of the hosts’ ports have the same AL-PA, change the AL-PA.

To change the port for the FCI-1064 HBA:

1. Back up the fca-pci.conf file:

cp /kernel/drv/fca-pci.conf /kernel/drv/fca-pci.bk

2. Edit the fca-pci.conf file

3. Define the adapter’s SCSI ID (and hence FC AL-PA) on the loop. Enter:

scsi-initiator-id = 0xZZ:0-125


5. Shut down and reboot.


Example

## fca-pci.conf - JNI FCA DRIVER (Solaris SCSI-IP HBA) CONFIGURATION FILE

# Configuration variable scsi-initiator-id# Type: integer, 0-125; default: none (must be explicitly set for PCI driver)# Defines the adapters SCSI ID (and hence FC AL_PA) on the loopscsi-initiator-id = 0x7d;

# Configuration flag fca_nport# Type: boolean; default: 0 (false)# If false (0), then fca initializes on a loop# If true (1), then fca initializes as an N_Port# and fabric operation is enabledfca_nport = 0;

# Configuration flag public_loop# Type: boolean; default: 0 (false)# If false (0), then fca-pci initializes according to what fca_nport is set to # If true (1), then fca initializes as an NL_Port on a public loop# and fabric operation is enabled via the FLPort of the switch# if public_loop = 1, then fca_nport is overridden to be 0public_loop = 0;

# Configuration target_controllers# Type: integer, count; default: 126# Defines the number of target controllers to support.# The absolute maximum is 5000.# If set to greater than 5000, the driver will reset to 5000.target_controllers = 126;

# Configuration flag ip_disable# Type: boolean; defalt; 0 (false)# if false (0), then the IP side of the driver is enabled# if true (1), then the IP side of the driver is completely disabledip_disable = 1; # Configuration variable qfull_retry_count# Type: integer, count; defalt: 0 # Defines the number of times a command is retried by the HBA if a target # rejects it with a queue full status. # if 0, then the HBA will retry forever# if > 0, then the HBA tries at least qfull_retry_count times # if qfull_retry_count exceeded, then the HBA returns the command to the target # driver with reason set to transport error. qfull_retry_count = 0; # Configuration variable qfull_retry_interval# Type: integer, milliseconds; default: 1000 # Time the HBA waits before retrying a rejected command due to queue full qfull_retry_interval = 1000;

# Configuration variable failover# Type: integer, seconds; default: 30# Defines the number of seconds after target is declared "offline" # before target is declared "failed" and all pending commands # are flushed back to the application.# See failover_extension for additional info. failover = 30;

# Configuration variable failover_extension# Type: integer, seconds; default: 0# Extends a target's failover period by this number of seconds to perform target rediscovery.# If defined and the target has pending commands at the time it is declared "failed",

Installation 33

# the target will first be declared "missing" for this period before being declared "failed". # When a target is declared "missing" the link will be reset once and targets will be rediscovered. # This provides a "last chance" opportunity for the target to go "online" before # the target is declared "failed" and all pending commands are flushed.# See failover for additional info. failover_extension = 0;

# Configuration variable recovery_attempts# Type: integer, count; default: 5# Defines the number of times login_recovery is attempted before failedrecovery_attempts = 5;

# Configuration flag class2_enable# Type: boolean; default: 0# If set to 1 (true), then FC Class 2 exchanges (ACK_1 model) are enabled for# devices which support it [even when connected to a loop].class2_enable = 0;

# Configuration variable fca_heartbeat# Type: value, microseconds; default: 0# Defines the number of microseconds between "heartbeat" frames.# Only used for debugging.fca_heartbeat = 0;

# Configuration flag reset_glm# Type: boolean; default: 0# If non-zero, then the Gigabit Link Module will be reset before# adapter initialization. This is a workaround for specific boot-up# conditions.reset_glm = 0;

# Configuration flag timeout_reset_enable# Type: boolean; default: 0# When a command times out to a target, the driver can attempt to clear the problem in two ways:# 1. (timeout_reset_enable = 1) Reset the target.# 2. (timeout_reset_enable = 0) Send an abort exchange (ABTS_LS) request to the target.timeout_reset_enable = 0;

# Configuration flag busy_retry_delay# Type: unsigned int; default: 100# Sets delay between retries after a SCSI device returns a BUSY response for a command.# The delay is in milliseconds with a 10 millisecond resolution.busy_retry_delay = 500;

# Configuration flag link_recovery_delay# Type: unsigned int; default: 1000# Sets delay between link up state and login recovery.# This delay helps ensure link stability before recovery of communications to ports.# The delay is in milliseconds with a 10 millisecond resolution.# for combined SCSI/IP operation, this should be set to at least 1000link_recovery_delay = 1000;

# Configuration flag scsi_probe_delay# Type: unsigned int, milliseconds; default: 500# Sets delay before SCSI probes are allowed to occur during boot.# This allows time for the driver to build a network port list for target binding.# The delay is in milliseconds with a 10 millisecond resolution.scsi_probe_delay = 5000;

# Configuration flag def_hba_binding# Type: string; default: "fca-pci*" (means all target/lun instances will be initialized by all fca-pci instances)


# Sets the default HBA binding for every target/lun instance which does not explicitly define one.# - A "*" following an hba name indicates all instances of that hba driver# *See technote for details on hba bindingsdef_hba_binding = "fca-pci*";

# Configuration flag def_wwXn_binding where X is either n for node or p for port.# Type: string; default: "$xxxxxxxxxxxxxxxx" (means WWXN is "static don't care")# Sets the 16 digit hexidecimal default wwXn binding for every target/lun instance which does not # explicitly define one.# - A "$" preceding the string indicates static binding enabled# - A "x" in place of a digit indicates "don't care" for that digit# *See technote for details on wwn bindingsdef_wwpn_binding = "$xxxxxxxxxxxxxxxx";def_wwnn_binding = "$xxxxxxxxxxxxxxxx";

# Configuration flag def_port_binding# Type: string; default: "xxxxxx" (means PORT is "non-static don't care")# Sets the 6 digit hexidecimal default port binding for every target/lun instance which does not # explicitly define one.# - A "$" preceding the string indicates static binding enabled# - A "x" in place of a digit indicates "don't care" for that digit# *See technote for details on port bindingsdef_port_binding = "xxxxxx";

# Configuration flag fca_verbose# Type: boolean; default: 1# Determines how many messages are displayed directly to the console. # - A "0" will quiet the driver messages to the console, but still print them to the # system message log. # (NOTE: a "boot -v" will override this setting and make the driver verbose again)# - A "1" will make the driver print all messages to the console and to the system # message log.fca_verbose = 0;

Example(/kernel/drv/sd.conf)

## Copyright (c) 1992, by Sun Microsystems, Inc.##ident"@(#)sd.conf1.893/05/03 SMI"

## Please use the following conventions when defining persistent bindings for the JNI driver. # Always add the definitions at the top of this file.## Port CL1-J#name="sd" class="scsi" target=10 lun=0 hba="fca-pci0";name="sd" class="scsi" target=10 lun=1 hba="fca-pci0";name="sd" class="scsi" target=10 lun=2 hba="fca-pci0";name="sd" class="scsi" target=10 lun=3 hba="fca-pci0";name="sd" class="scsi" target=10 lun=4 hba="fca-pci0";name="sd" class="scsi" target=10 lun=5 hba="fca-pci0";name="sd" class="scsi" target=10 lun=6 hba="fca-pci0";name="sd" class="scsi" target=10 lun=7 hba="fca-pci0";## End of XP definitions

Installation 35

Configuration for Emulex LightPulse LP7000

Edit the configuration in the lpfc.conf file to set the avoid-resets parameter.

If there are multiple servers on the same FC-AL and two or more hosts’ ports have the same AL-PA, change the AL-PA by changing the lpfcX-assign-alpa parameter in the lpfc.conf file.

To edit the /kernel/drv/lpfc.conf file:

1. Back up the configuration file by entering:

cp /kernel/drv/lpfc.conf /kernel/drv/lpfc.bk

2. Edit the /kernel/drv/lpfc.conf file.

Solaris LightPulse lpfc (SCSI) / lpfn (IP) driver: global initialized data. : :# Set a ALPA for interface, only valid if topology=4# lpfc0-assign-alpa=2; Request ALPA 2 for lpfc0 lpfc0-assign-alpa=0x3; : :# Set avoid-resets to 1, to avoid having the target driver# send BUS RESET commands down to the HBA driver.# Default is 1.avoid-resets=0;

3. Set avoid-resets to 0.

4. Set lpfcX-assign-alpa to the AL-PA, where X is the HBA number and the AL-PA is a valid AL-PA value.


6. Shut down and reboot.

Installation 37

Configuration for the Sun X6729A Adapter

To configure the Sun X6729A adapter:

1. Make a backup of the ssd.conf file. Enter:

cp –ip /kernel/drv/ssd.conf /kernel/drv/ssd.conf.standard

2. Edit the /kernel/drv/ssd.conf file. For the X6729A adapter, values higher than LUN=16 are not available.

# Copyright (c) 1995, by Sun Microsystems, Inc.# All rights reserved.##ident "@(#)ssd.conf 1.5 97/02/20 SMI"

name="ssd" parent="SUNW,pln" port=0 target=0;name="ssd" parent="SUNW,pln" port=0 target=1;name="ssd" parent="SUNW,pln" port=0 target=2;

name="ssd" parent="SUNW,pln" port=0 target=15;name="ssd" parent="SUNW,pln" port=1 target=0;name="ssd" parent="SUNW,pln" port=1 target=1;name="ssd" parent="SUNW,pln" port=1 target=2;

name="ssd" parent="SUNW,pln" port=5 target=14;name="ssd" parent="SUNW,pln" port=5 target=15;name="ssd" parent="sf" target=0;name="ssd" parent="ifp" target=127;name="ssd" parent="ifp" target=0 lun=0;name="ssd" parent="ifp" target=0 lun=1;name="ssd" parent="ifp" target=0 lun=2;

name="ssd" parent="ifp" target=6 lun=10;name="ssd" parent="ifp" target=6 lun=11;

3. Save the changes and exit the text editor.

4. Reboot.

5. Make a backup of the /kernel/drv/ses.conf file. Enter:

cp –ip /kernel/drv/ses.conf /kernel/drv/ses.conf.standard


6. Edit the /kernel/drv/ses.conf file. Add the underlined lines in the example to the configuration file.

Example ## Copyright (c) 1996, by Sun Microsystems, Inc.# All rights reserved.# ##ident "@(#)ses.conf 1.1 97/02/10 SMI"#

name="ses" parent="sf" target=15;

name="ses" parent="SUNW,pln" port=0 target=15;name="ses" parent="SUNW,pln" port=1 target=15;name="ses" parent="SUNW,pln" port=2 target=15;name="ses" parent="SUNW,pln" port=3 target=15;name="ses" parent="SUNW,pln" port=4 target=15;name="ses" parent="SUNW,pln" port=5 target=15;

name="ses" class="scsi"target=15 lun=0;name="ses" parent="ifp" target=127;name="ses" parent="ifp" target=0 lun=0;name="ses" parent="ifp" target=0 lun=1;name="ses" parent="ifp" target=0 lun=2;name="ses" parent="ifp" target=0 lun=3;name="ses" parent="ifp" target=0 lun=4;name="ses" parent="ifp" target=0 lun=5;

7. Save the changes and exit the text editor.

8. Reboot.

Installation 39

Setting the Disk and Device Parameters

The I/O timeout value (TOV) for disk array devices is 60 seconds (the default). If the I/O timeout value has been changed, you must change it back to 60 seconds by editing the sd_io_time parameter in the /etc/system file.

You should also verify all other required settings for your operational environment (for example, Fibre Channel support). You must also make sure that the device parameters are the same for all disk array devices. For Fibre Channel, the settings in the system file are effective for the whole system, not for just the Fibre Channel adapter.

To set the I/O timeout value:

1. Make a backup copy of the system specification file using the cp command:

Example # cp /etc/system /etc/system.backup

2. Open the system specification file using the vi editor.

Example # vi /etc/systemident “@(#)System 1.15 92/11/14 SMI” / SVRA 1.5 */** SYSTEM SPECIFICAtION FILE** moddir:** Set the search path for modules. This has a format similar to the* csh path variable. If the module isn’t found in the first directory* it tries the second and so on. The default is /kernel /usr/kernel** Example:* moddir: /kernel /usr/kernel /other/modules* : :* set:** Set an integer variable in the kernel or a module to a new value.* This facility must be used with caution. See system(4).* Examples:** To set variables in ‘unix’:** set nautopush=32* set maxusers=40** To set a variable named ‘debug in the module named ‘test_module** set test_module:debug = 0x13* set sd:sd_io_time = 0x3c set sd:sd_max_throttle = 16


3. Look for the following line:

set sd:sd_io_time = 0xXX.

If this line does not appear anywhere in the file, you do not need to add it because the TOV will default to 60 seconds. If this line has already been added to the file, make sure the value is 0x3c hex (decimal 60).

4. Look for the following line:

set sd:sd_max_throttle = x

If this line does not appear anywhere in the file, you need to add it. If this line has already been added to the file, make sure the max throttle is set to the appropriate value.

Example To set the max throttle value to 8, enter:

set sd:sd_max_throttle = 8

5. Save the changes and exit the vi editor.

You must shut down and restart the system for these changes to take effect.

Installation 41

Connecting the Disk Array

After you have added the new SCSI paths to the driver configuration file and edited the system configuration file as needed, you are ready to connect the disk to the Sun system.

Shut Down the Sun System

The Sun system must be shut down and powered off before the disk is connected.

To shut down and power off the Sun system:

1. Shut down the Sun system as usual.

Example # shutdown –y –i 0 –g 30

2. Reset the system.

You are now ready to connect the disk array to the Sun system as described in the next section.

Connect the Disk Array

The disk array comes with all hardware and cabling required for connection to the host systems.

To connect the disk array:

1. Verify disk array installation.

The HP service representative verifies that the status of the SCSI/Fibre Channel adapters and LDEVs is NORMAL.

The HP service representative must also check the SCSI paths to make sure all SCSI TIDs for each host system are unique.


2. Connect the disk array to the Sun system.

The Sun system must be powered OFF before the disk array is connected.

The HP representative installs the SCSI/Fibre Channel cables between the disk array and the Sun system.

Make sure to install SCSI terminators as required.

3. Power on the Sun system display.

4. Power on all peripheral devices.

The disk array must already be on, the SCSI paths must already be defined, and the driver configuration file and system configuration file must already be edited.

If the SCSI paths are defined after the Sun system is powered on, the system must be restarted to recognize the new devices.

5. Confirm the ready status of all peripheral devices, including the disk array.

6. Power on the Sun system.

Installation 43

Configuring the Disk Devices

After connecting the disk array, you must configure the system.

Verify New Device Recognition

The first step in new device configuration is to verify that the Sun system recognizes the new disk drives correctly.

To verify new device recognition:

1. Reboot the system using the boot –r command.

The –r option tells the system to rebuild the devices. Using boot by itself will not build the devices on the newly installed disk array.

2. Log in to the system as root.

3. Display the device information.

Example

# dmesg | more :sbus0 at root: UPA 0x1f 0x0 ...fas0: rev 2.2 FEPS chip

SUNW,fas0 at sbus0: SBus0 slot 0xe offset 0x8800000 and slot 0xe offset 0x8810000 Onboard device sparc9 ipl 4SUNW,fas0 is /sbus@1f,0/SUNW,fas@e,8800000sd0 at SUNW,fas0: target 0 lun 0sd0 is /sbus@1f,0/SUNW,fas@e,8800000/sd@0,0

<SUN2.1G cyl 2733 alt 2 hd 19 sec 80>sd6 at SUNW,fas0: target 6 lun 0sd6 is /sbus@1f,0/SUNW,fas@e,8800000/sd@6,0WARNING: fca0: fmle: sc1: 000e0000 sc2: 00000000fca0: JNI Fibre Channel Adapter (1062 MB/sec), model FCfca0: SBus 1 / IRQ 4 / FCODE Version 10 [20148b] / SCSI ID 125 / AL_PA 0x1fca0: Fibre Channel WWN: 100000e0690002b7fca0: FCA Driver Version 2.1+, June 24, 1998 Solaris 2.5, 2.6fca0: All Rights Reserved.fca0: < Total IOPB space used: 1100624 bytes >fca0: < Total DMA space used: 532644 bytes >fca0: <HP :OPEN-3 :5235> target 2 (alpa 0xe4) lun 0 onlinesd192 at fca: target 2 lun 0


LUN (Logical Unit Number)=0 target ID=2sd192 is /sbus@1f,0/fca@1,0/sd@2,0WARNING: /sbus@1f,0/fca@1,0/sd@2,0 (sd192)

corrupt label - wrong magic number Not yet labeled.Vendor 'HP', product 'OPEN-3', 4806720 512 byte blocks

Vendor name Product name Number of blocks

fca0: <HP :OPEN-3 :5235> target 2 (alpa 0xdc) lun 2 onlinesd193 at fca: target 2 lun 1 (LUN=1, target ID=2)sd193 is /sbus@1f,0/fca@1,0/sd@2,1WARNING: /sbus@1f,0/fca@1,0/sd@2,1 (sd193) corrupt label - wrong magic number Vendor 'HP', product 'OPEN-3', 4806720 512 byte blocksfca0: <HP :OPEN-9 :5235> target 6 (alpa 0xdc) lun 0 onlinesd.. at fca: target lun 0 (LUN=0, target ID=6)sd.. is /sbus@1f,0/fca@1,0/sd@4,0WARNING: /sbus@1f,0/fca@1,0/sd@4,0 (sd..) corrupt label - wrong magic number Not yet labeled. Vendor 'HP', product 'OPEN-9', 14423040 512 byte blockssd.. at fca: target 6 lun 0 Verify the target ID. corrupt label - wrong magic number Not yet labeled. Vendor 'HP', product 'OPEN-9', 14423040 512 byte blockssd.. is /sbus@1f,0/fca@1,0/sd@5,0WARNING: /sbus@1f,0/fca@1,0/sd@5,0 (sd..) corrupt label - wrong magic number Not yet labeled. Vendor 'HP', product '3390-3B', 5822040 512 byte blockssd.. is /sbus@1f,0/fca@1,0/sd@6,0WARNING: /sbus@1f,0/fca@1,0/sd@6,0 (sd..) corrupt label - wrong magic number Not yet labeled. Vendor 'HP', product '3390-3A', 5825520 512 byte blockssd.. is /sbus@1f,0/fca@1,0/sd@8,0

4. Verify that the system recognizes the disk array devices. Verify that the device information for each new device (vendor, product, number of blocks, block size) is correct. Refer to “Parameter Tables for OPEN-K/3/8/9/E Devices” (page 72) in appendix B for device information.

Example This example shows that the Sun system recognizes the following devices on the disk array.

HP OPEN-3 device: SCSI bus = ....,isp@1, SCSI target ID = 2, LUN = 0.HP OPEN-3 device: SCSI bus = ....,isp@1, SCSI target ID = 2, LUN = 1.HP OPEN-9 device: SCSI bus = ....,isp@1, SCSI target ID = 4, LUN = 0.

If any device information is missing or incorrect, check the SVP SCSI-to-LDEV path configuration to make sure the SCSI TIDs and LUNs

Installation 45

are not duplicated. Also, be sure that the SCSI cables and terminators are installed correctly or that Fibre Channel cabling is correct.

Verify Fibre Channel Host Adapter Recognition (Fibre Channel Only)

After the installation for the host adapter, use the dmesg command to verify that the host adapter is recognized.

To verify host adapter recognition:

1. Enter dmesg to display information.

2. Verify that the bold text is displayed.

If the message is missing or an error message appears, the host environment may not be installed properly. Check the host adapter hardware and driver installation or host configuration. In this example, the operating system level is given in the third line.

Example # dmesgMar 16 14:09SunOS Release 5.5 Version Generic_Patch [Unix(R) System V Release 4.0]Copyright (C) 1983-1995, Sun Microsystems, Inc.pac: enabled - SuperSPARCcpu0: TI,TMS390Z50 (mid 8 impl 0x0 ver 0x3 clock 50 MHz)mem = 81920K (0x5000000)avail mem = 71004160Ethernet address = 8:0:20:1a:a6:73root nexus = SUNW,SPARCstation-20iommu0 at root: obio 0xe0000000sbus0 at iommu0: obio 0xe0001000espdma0 at sbus0: SBus slot f 0x400000dma2 at sbus0: SBus slot 1 0x81000esp0 at espdma0: SBus slot f 0x800000 sparc ipl 4esp2 fat dma2: SBus slot 1 0x80000 SBus level 3 sparc ipl 5esp0 at SBus slot f 0x800000 pri 4 (onboard)sd1 at esp0 target 1 lun0fca0:JNI Fibre Channel Adapter (1062 MB/sec), model FCfca0: SBUS 1: IRQ 4: FCODE Version 11.0.9 [la6384] : SCSIID 125 : AL_PA 01fca0: Fibre Channel WWN: 100000e0690000d5fca0: FCA Driver Version 2.2.HIT.03, Oct 09, 1999 Solaris 2.5, 2.6fca0: All Rights Reserved.fca0: < Total IOPB space used: 11258245 bytes >fca0: <Total DMA space used: 565277bytes >:


Partition and Label the Devices

All new devices must be partitioned and labeled using the Sun format utility. OPEN-K/3/8/9/E devices can have more than one partition. The device partitioning and labeling procedure involves the following tasks:

• defining and setting the disk type

• setting the partitions

• labeling the disk

• verifying the disk label

Caution Be extremely careful when using the Sun format utility. Do not use any format commands not described in this document. The Sun format utility is designed for Sun disks. Some format commands are not compatible with the disk array and can overwrite the data on the disk. The disk array will not respond to the format command (the disks are formatted by the HP service representative using the SVP), and will not report any defect data in response to the defect command.

To partition and label the disks, work with all devices of one type (for example, OPEN-3), then all devices of the next type (for example, OPEN-9), and so on until you have partitioned and labeled all new devices.

During the disk partitioning and labeling procedure, enter the disk type parameter information. Refer to “Parameter Tables for OPEN-K/3/8/9/E Devices” (page 72) in appendix B for values.

Installation 47

To partition and label the devices:

1. Enter format at the root prompt to start the format utility.

Example

# format

searching for disks...done

c1t2d0: configured with capacity of 2.29GB (OPEN-3)



AVAILABLE DISK SELECTIONS

0. c0t1d0 <SUN1.05 cyl 2036 alt 2 hd 14 sec 72>

/iommu@f,e0000000/sbus@f,e0001000/espdma@f,400000/esp@f,800000/sd@1,0

1. c0t3d0 <SUN1.05 cyl 2036 alt 2 hd 14 sec 72>

/iommu@f,e0000000/sbus@f,e0001000/espdma@f,400000/esp@f,800000/sd@3,0

2. c1t2d0 <HP-OPEN-3-0315

/iommu@f,e0000000/sbus@f,e0001000/....,isp@0,10000/sd@2,0

3. c1t2d1 <HP-OPEN-3-0315


4. c1t4d0 <HP-OPEN-9-0315


2. Verify that all new devices are displayed.

If not, exit the format utility (quit or Ctrl-D), and make sure the SCSI/Fibre Channel-to-LDEV paths were defined for all devices and that all new devices were added to the driver configuration file.

3. Record the character-type device file names (for example, c1t2d0) for all of the newly installed disk array devices.

You will need this information later to create the file systems.


4. When you are asked to specify the disk, enter the number of the device to be partitioned and labeled.

Example Specify disk (enter its number): 2

selecting c1t2d0

[disk formatted]

5. When you are asked if you want to label the disk, enter n for “no.”

Example Disk not labeled. Label it now ? n

6. After the format menu is displayed, enter type to display the disk types.

Example format> type

AVAILABLE DRIVE TYPES 0. Auto configure : 14. SUN2.1G 15. HP-OPEN-3-0315 16. HP OPEN-3 17. other

7. If the disk type for the selected device is already defined, enter the number for that disk type, and go to step 10.

Do not use HP-OPEN-x-0315, HP-3390-3A/B-0315, or HP-3380-KA/B-0315. These disk types are created automatically by Solaris and cannot be used for disk array devices.

Example Specify disk type (enter its number):16

8. If the disk type for the selected device is not already defined, enter its number to define the disk type.

Example AVAILABLE DRIVE TYPES 0. Auto configure : 14. SUN2.1G 15. HP-OPEN-3-0315 16. other Specify disk type (enter its number):16

Installation 49

9. Enter the disk type parameters for the selected device using the data provided in the tables at the beginning of this procedure.

Example Enter number of data cylinders:3336Enter number of alternate cylinders[2]:2Enter number of physical cylinders[3338]:Enter number of heads: 15Enter number of physical heads[defaults]:Enter number of data sectors/track:96Enter number of physical sectors/track[defaults]:Enter rpm of drive [3600]:6300Enter format time[defaults]:Enter cylinder skew[defaults]:Enter track skew[defaults]Enter track per zone[defaults]:Enter alternate tracks[defaults]:Enter alternate sectors[defaults]:Enter cache control[defaults]:Enter prefetch threshold[defaults]:Enter minimum prefetch[defaults]:Enter maximum prefetch[defaults]:Enter disk type name(remember quotes):"HP OPEN-3"selecting c1t2d0[disk formatted]No defined partition tables.Disk not labeled. Label it now ? n

10. When you are asked whether you want to label the disk, enter n for “no.”

Example Disk not labeled. Label it now ? nformat>


11. After the format menu is displayed, enter partition to display the partition menu.

Example FORMAT MENU: disk - select a disk type - select (define) a disk type partition - select (define) a partition table current - describe the current disk format - format and analyze the disk repair - repair a defective sector label - write label to the disk analyze - surface analysis defect - defect list management backup - search for backup labels verify - read and display labels save - save new disk/partition definitions inquiry - show vendor, product and revision volume - set 8-character volume name quitformat> partition

PARTITION MENU 0 - change ‘0’ partition 1 - change ‘1’ partition 2 - change ‘2’ partition 3 - change ‘3’ partition 4 - change ‘4’ partition 5 - change ‘5’ partition 6 - change ‘6’ partition 7 - change ‘7’ partition select - select a predefined table modify - modify a predefined partition table name - name the current table print - display the current table label - write partition map and label to the disk quitpartition>

Installation 51

12. Enter the desired partition number, and then enter the partition parameters.

Example partition> 0Part Tag Flag Cylinders Size Blocks 0 unassigned wm 0 - 0 (0/0/0)

Enter partition id tag [root]:Enter partition permission flags [wm]:Enter new starting cyl [0]:Enter partition size [0b, 0c, 0.00mb]:3336c

13. Display the current partition table.

Example

partition> print:Current partition table (unnamed)Part Tag Flag Cylinders Size Blocks 0 root wm 0 - 0 (0/0/0) 0 1 swap wm 0 - 0 (0/0/0) 0 2 backup wu 0 - 3335 2.29 GB (3336/0/0) 4803840 3 unassigned wu 0 - 0 (0/0/0) 0 4 unassigned wm 0 - 0 (0/0/0) 0 5 unassigned wm 0 - 0 (0/0/0) 0 6 usr wm 336 - 3335 204 GB (2970/0/0) 4276800 7 unassigned wm 0 - 0 (0/0/0) 0

14. Repeat steps 12 and 13 as needed to set the partitions for the selected device.


15. When you are finished setting the partitions for the selected device, enter label at the partition> prompt, and then enter y to label the device.

Example PARTITION MENU 0 - change ‘0’ partition 1 - change ‘1’ partition 2 - change ‘2’ partition 3 - change ‘3’ partition 4 - change ‘4’ partition 5 - change ‘5’ partition 6 - change ‘6’ partition 7 - change ‘7’ partition select - select a predefined table modify - modify a predefined partition table name - name the current table print - display the current table label - write partition map and label to the disk quitpartition> labelReady to label disk, continue? y

16. Exit the partition utility and return to the format utility.

Example partition> quit

17. Display the available disks by entering disk at the format> prompt. Make sure the disk you just labeled is displayed with the proper disk type name and parameters.

Example

format> disk

AVAILABLE DISK SELECTIONS 0. c0t1d0 <SUN1.05 cyl 2036 alt 2 hd 14 sec 72> /iommu@f,e0000000/sbus@f,e0001000/espdma@f,400000/esp@f,800000/sd@1,0 1. c0t3d0 <SUN1.05 cyl 2036 alt 2 hd 14 sec 72> /iommu@f,e0000000/sbus@f,e0001000/espdma@f,400000/esp@f,800000/sd@3,0 2. c1t2d0 <HP OPEN-3 cyl 3336 alt 2 hd 15 sec 96> /iommu@f,e0000000/sbus@f,e0001000/....,isp@0,10000/sd@2,0 3. c1t2d1 <HP-OPEN-3-0315 .....................> /iommu@f,e0000000/sbus@f,e0001000/....,isp@0,10000/sd@2,1 4. c1t2d0 <HP-OPEN-9-0315 .....................> /iommu@f,e0000000/sbus@f,e0001000/....,isp@0,10000/sd@4,0 Specify disk (enter its number): 3

Installation 53

18. Repeat steps 2 through 17 for each new device to be labeled.

After a disk type is defined (for example, HP OPEN-3), you can label all devices of that same type without having to enter the disk type parameters (that is, you can skip steps 8 and 9). For this reason, you may want to label the devices by type, for example, labeling all OPEN-3 devices, then all OPEN-9 devices, and so on until all new devices have been partitioned and labeled.

19. When you finish labeling the disks and verifying the disk labels, enter quit or press Ctrl-D to exit the format utility.


Creating and Mounting the File Systems

When you finish labeling the disks and verifying the disk labels, you must create and mount the file systems.

Create the File Systems

First create the file system.

To create the file systems:

1. Create the file system using the newfs –C maxconfig command.

Example # newfs -C 6 /dev/rdsk/c1t2d0s0

Use 6 or one of the following multiples of 6 as the maxconfig value for all disk array OPEN-K/3/8/9/E devices: 12, 18, 24, or 30.

If 6 is used, the Sun OS will access 48 KB as a unit (6*8 KB), which matches the track size of the OPEN-K/3/8/9/E devices. These maxconfig values (6, 12, 18, 24, 30) optimize the I/O performance of the disk array by keeping the I/O data range on one track. The maxconfig value that you choose depends on your applications, and you can change the maxconfig parameter to a different value at any time.

Use the character-type device file (for example, /dev/rdsk/c1t2d0s0) as the argument.

Example /dev/rdsk/c1t2d0s0

2. When the confirmation appears, verify that the device file name is correct.

If correct, enter y for yes.

If not correct, enter n for no, and repeat step 1, using the correct device file name.

Installation 55

Example

newfs:construct a new file system /dev/rdsk/c1t2d0s0:(y/n) y/dev/rdsk/c1t2d0s0: 4803840 sectors in 3336 cylinders of 15 tracks, 96 sectors 22345.6MB in 209 cyl groups (16 c/g, 11.25MB/g, 5440 i/g)super-block backups (for fsck -F ufs -o b=#) at: 32, 23168, 46304, 69440, 92576, 115712, 138848, 161984, 185120, 208256, : :4747616, 4770752, 4792352,#

3. Repeat steps 1 and 2 for each OPEN-K/3/8/9/E device on the newly installed disk array.

Use the same maxconfig value for all disk array devices.

Create and Verify the Mount Directories

Create and verify the mount directories for the new OPEN-K/3/8/9/E devices. Each logical partition requires a unique mount directory, and the mount directory name should identify the logical volume and the partition.

To create the mount directories:

1. Go to the root directory.

Example # cd# pwd/

2. Create the mount directory. Choose a name for the mount directory, which identifies both the logical volume and the partition.

Example # mkdir /XP

3. Verify the new mount directory.

4. Repeat steps 2 and 3 for each logical partition on each new OPEN-K/3/8/9/E device.


Mount and Verify the File Systems

After the file system and mount directories are created, you are ready to mount and verify the file systems.

To mount and verify the file systems:

1. Mount the file system by using the mount command.

Use the correct block-type device file name and mount directory for the device/partition. If you have already added the device to the /etc/vfstab file, you do not need to specify the block-type device file, only the mount directory.

Example # mount /dev/dsk/c1t2d0s0 /XP# mount /dev/dsk/c1t2d1s0 /XP# mount /dev/dsk/c1t2d2s0 /XP :

2. Repeat step 1 for each partition of each newly-installed OPEN-K/3/8/9/E device.

3. Display the mounted devices and verify that all new OPEN-K/3/8/9/E LUNs are displayed correctly.

Example # df -kFile system Kbytes used avail capacity Mounted on/dev/dsk/c0t3d0s0 28775 27706 0 100% //dev/dsk/c0t3d0s6 269191 234897 7384 97% /usr/proc 0 0 0 0% /proc fd 0 0 0 0% /dev/fd /dev/dsk/c0t3d0s4s 57567 29515 22302 57% /var swap 142204 20 142184 0% /tmp /dev/dsk/c0t3d0s7 462119 206000 209909 50% /export/home/dev/dsk/c0t3d0s5 47975 42059 1126 97% /opt /dev/dsk/c1t2d0s0 2256436 9 2030787 0% /XP00/dev/dsk/c1t2d1s0 2256436 9 2030787 0% /XP01/dev/dsk/c1t2d2s0 6774358 9 6548709 0% /XP02 :

4. As a final verification, perform some basic UNIX operations (for example, file creation, copying, and deletion) on each logical unit to make sure that the newly installed devices are fully operational.

Installation 57

Set and Verify the Auto-Mount Parameters

Add the new OPEN-K/3/8/9/E devices to the /etc/vfstab file, specifying the auto-mount parameters for each device. After a device is added to this file, you can mount the device without having to specify its block-type device file name, because the /etc/vfstab file associates the device with its mount directory.

Table 3. fstab Parameters

Parameter Number Name Enter

P1 Device to mount Block-type device file name

P2 Device to fsck Character-type device file name

P3 Mount point Mount directory name

P4 FS type File system type (for example, ufs)

P5 Fsck pass Order for performing file system checks

P6 Mount at boot Yes = auto-mounted at boot/mountallNo = not auto-mounted at boot/mountall


To set the auto-mount parameters:

1. Make a backup copy of the /etc/vfstab file.

# cp -ip /etc/vfstab /etc/vfstab.standard

2. Edit the /etc/fstab file, adding one line for each device to be auto-mounted. Table 3 (page 58) shows the auto-mount parameters.

Example

3. Reboot the system.

4. Display the mounted devices using the df –k command, and verify that the devices were auto-mounted.

# cp -ip /etc/vfstab /etc/vfstab.standard# vi /etc/vfstab#device device mount FS fsck mount mount#to mount to fsck point type pass at boooptions

/proc - /proc procfs - no fd - /dev/fd fd - no swap - /tmp tmpfs - yes /dev/dsk/c0t3d0s0 /dev/rdsk/c0t3d0s0 / ufs 1 no /dev/dsk/c0t3d0s6 /dev/rdsk/c0t3d0s6 /usr ufs 2 no /dev/dsk/c0t3d0s7 /dev/rdsk/c0t3d0s7 /export ufs 3 yes /dev/dsk/c0t3d0s5 /dev/rdsk/c0t3d0s5 /opt ufs 4 yes /dev/dsk/c0t3d0s1 - - swapfs - no /dev/dsk/c0t2d0s0 /dev/rdsk/c0t2d0s0 /XP ufs 5 yes /dev/dsk/c0t2d1s0 /dev/rdsk/c0t2d1s0 /XP ufs 5 yes /dev/dsk/c0t2d1s0 /dev/rdsk/c0t2d1s0 /XP ufs 5 yes

P1 P2 P3 P4 P5 P6

Installation 59

Operation With Veritas Volume Manager

HP Surestore Storage Arrays are all certified for VxVM support. To ensure proper operation of the Dynamic Multi Pathing (DMP) feature of VxVM, update the /kernel/drv/vxdmp.conf file to reflect the appropriate Vendor string.

Example # @(#)src/sol/kernel/vxdmp/vxdmp.conf 1.6.21.1 02/26/00 16:12:41 - Copyright (c) 1999 VERITAS Software Corp.#ident "@(#)vxvm:src/sol/kernel/vxdmp/vxdmp.conf 1.6.21.1"

# Copyright (c) 2000 VERITAS Software Corporation. ALL RIGHTS RESERVED.# UNPUBLISHED -- RIGHTS RESERVED UNDER THE COPYRIGHT# LAWS OF THE UNITED STATES. USE OF A COPYRIGHT NOTICE# IS PRECAUTIONARY ONLY AND DOES NOT IMPLY PUBLICATION# OR DISCLOSURE.## THIS SOFTWARE CONTAINS CONFIDENTIAL INFORMATION AND# TRADE SECRETS OF VERITAS SOFTWARE. USE, DISCLOSURE,# OR REPRODUCTION IS PROHIBITED WITHOUT THE PRIOR# EXPRESS WRITTEN PERMISSION OF VERITAS SOFTWARE.## RESTRICTED RIGHTS LEGEND# USE, DUPLICATION, OR DISCLOSURE BY THE GOVERNMENT IS# SUBJECT TO RESTRICTIONS AS SET FORTH IN SUBPARAGRAPH# (C) (1) (ii) OF THE RIGHTS IN TECHNICAL DATA AND# COMPUTER SOFTWARE CLAUSE AT DFARS 252.227-7013.# VERITAS SOFTWARE# 1600 PLYMOUTH STREET, MOUNTAIN VIEW, CA 94043

name="vxdmp" parent="pseudo" instance=0# dmp_jbod="HITACHI";dmp_jbod="HP";

Further, when using the JNI adaptor, ensure that the failover parameter is set to a value other than 0. The recommended value is 30. Failure to do so results in a loss of path failover in DMP.


2TROUBLESHOOTING

If the disk array has an error condition, see “Error Conditions” (page 62), for recommended actions. The table lists potential error conditions during disk array configuration for Sun Solaris and provides instructions for resolving each condition.

If you are unable to resolve an error condition, ask your HP support representative for assistance. See “Calling the HP Support Center” (page 68).

61

Error Conditions

Error Condition Recommended Action

The logical devices are not recognized by the system.

Verify that the READY indicator lights on the disk array are ON.

Verify that the SCSI/Fibre Channel cables are correctly installed and firmly connected.

Verify that the SCSI terminators are properly connected.

Verify that the SCSI target IDs are properly configured. The LUNs for each SCSI TID must start at 0 and continue sequentially without skipping any numbers.

Verify that the SCSI TIDs on each bus are unique. Do not install two devices with the same SCSI TID on the same bus.

Run dmesg to recheck the SCSI/Fibre Channel buses for new devices.

Verify that LUSE devices are not intermixed with normal LUNs or with multiplatform devices on the same SCSI port.

Verify that the maximum number of LUSE devices per SCSI port is 16.

The system does not reboot properly after hard shutdown.

If the system is powered off without executing the shutdown process, wait three minutes before restarting it. This pause allows the internal timeout process of the disk array to purge all queued commands so that the disk array is available (not busy) during system startup. If the system is restarted too soon, the disk array will continue trying to process queued commands, and the system will not reboot successfully.

Physical volumes cannot be created.

Verify that the disk array logical devices are correctly formatted.

Verify that the character-type device file exists and is correctly named.

(continued)


Volume groups cannot be created.

Verify that the directory for a volume group, the control file and the block-type device files exist.

Verify that the block-type device file is named correctly.

Logical volumes cannot be created.

Verify that the volume capacity for OPEN-3 volumes is not greater than 2344 MB, and that the volume capacity for OPEN-9 volumes is not greater than 7040 MB.

Verify that the capacity of the volume group is not less than the total capacity of the partitioned logical volume.

A file system cannot be created.

Verify that logical volume name is a character-type volume.

A file system is not mounted after rebooting.

Verify that the system was powered on correctly.

Verify that the file system attributes are correct.

Verify that the auto-mount information in the /etc/fstab file is correct.

The disk array performs a self reboot because the disk array was busy or it logged a panic message.

Reboot the Sun system.

The disk array responds “Not Ready or the disk array has displayed “Not Ready” and timed out.

Contact HP.

The Sun system detects a parity error.

Check the SCSI adapter card and make sure that it has been installed properly.

Reboot the Sun system.

The system hangs, or devices are declared and the system hangs.

Verify that the target IDs are set to 0-7 and 8-15, and that target ID 7 has been reserved for the SCSI controller card.

(continued)


Troubleshooting 63

Pinned track. To repair a pinned track, write dummy data to the pinned track, using the analyze-write command in the format utility. This procedure resets the ECC/LRC error status of the pinned track.



Verbose Mode

One method of troubleshooting involves the “verbose” mode. The following paragraphs are examples of error messages that may occur.

A possible debugging method is to select the device and turn on verbose mode. Then attempt the boot process again.

Verbose error messages will provide information which will help isolate the problem.

To turn on the verbose flag:

Enter the following command sequence:

ok " /sbus/fca" select-devok true to fca-verboseok boot fcadisk

Examples of Error Messages

Error message:Cannot Assemble drivers for /sbus@1f,0/fcaw@1,0/sd@0,0:aCannot Mount root on /sbus@1f,0/fcaw@1,0/sd@0,0:aProblem: The process of copying the OS to the fibre channels was not complete, or the drive specified on the boot command is not the same as the one the OS was constructed on.

Error message:Can’t open boot deviceProblem: The wwn specified with the set-bootn0-wwn does not correspond to the wwn of the device. Could also be a cable problem – the adapter cannot initialize.

Error message:The file just loaded does not appear to be bootableProblem: The bootblk was not installed on the target.

Troubleshooting 65

Error message:mount: /dev/dsk/c0t0d0s0 – not of this fs typeProblem: At this point the process hangs. This happens if the /etc/vfstab file has not been updated on the fibrechannel boot drive to reflect the new target.

Error message:Get PortID request rejected by nameserver Problem: The wwn of the target is not correct. Select the adapter and perform set-bootn0-wwn. If this is correct, check the switch to see that target is properly connected.

Error message:Can’t read disk labelProblem: The selected target is not a Solaris filesystem.

Error message:Nport init failed –Problem: Card is connected to an arbitrated loop device, but wants to initialize as an NPORT. The bootn0-wwn property has probably been set to a valid WWN.

Error message:Panic dump not savedProblem: After the system is successfully booted to Solaris from the fibrechannel and a panic occurs the panic does not get saved to the swap device.This can be the result not properly defined the swap partition.Use the format command to view the slices on the fibre channel drive.Take the partition option, then the print option.The swap partition should look something like this: 1 swap wm 68-459 298.36MB (402/0/0) 611040Sizes and cylinders will probably be different on your system. Make sure that the flag is wm and that the sizes are defined (not 0). Then use the label option from partition to write the label to the drive. After this the panic should be saved to the swap partition. If the partition needs to be changed chose the partition option, and enter 1 to select slice 1.

Error message:Can’t open /packagesProblem: The bootblk was not properly installed


Connection Problems

If problems occur when you attempt to connect the disk array and the Sun Solaris host, check the items below during troubleshooting.

• Disk array logical devices cannot be recognized

Check that disk array’s READY light is ON.

Confirm that target IDs are correctly set.

Confirm that SCSI IDs are not duplicated by other devices.

Verify the contents of the /kernel/drv/sd.conf file.

• File system cannot be created (newfs command)

Check that character-type device file is specified for as the device file in the newfs command.

Verify that the logical unit is correctly labeled by the format command.

• File system is not mounted after rebooting

Verify that the system is powered.

Verify that /etc/vfstab is correctly edited.

• There is a pinned track condition

Reset ECC/LRC pinned track error status using the Solaris analyze command.

Troubleshooting 67

Calling the HP Support Center

If you need to call HP customer support, provide as much information about the problem as possible, including the circumstances surrounding the error or failure and the exact content of any error messages displayed on the host system. If the Remote Control XP software product is installed on a remote console PC, check the R-SIM window and note the reference codes and severity levels of recent R-SIMs.


AWORKSHEET

69

SCSI Path Worksheet

LDEV (CU:LDEV)(CU = control unit)

DeviceType

SCSI BusNumber Path 1 Alternate Paths

0:00 TID:LUN:

TID:LUN:

TID:LUN:

0:01 TID:LUN:

TID:LUN:

TID:LUN:

0:02 TID:LUN:

TID:LUN:

TID:LUN:

0:03 TID:LUN:

TID:LUN:

TID:LUN:

0:04 TID:LUN:

TID:LUN:

TID:LUN:

0:05 TID:LUN:

TID:LUN:

TID:LUN:

0:06 TID:LUN:

TID:LUN:

TID:LUN:

0:07 TID:LUN:

TID:LUN:

TID:LUN:

0:08 TID:LUN:

TID:LUN:

TID:LUN:

0:09 TID:LUN:

TID:LUN:

TID:LUN:

0:10 TID:LUN:

TID:LUN:

TID:LUN:

0:11 TID:LUN:

TID:LUN:

TID:LUN:

0:12 TID:LUN:

TID:LUN:

TID:LUN:

0:13 TID:LUN:

TID:LUN:

TID:LUN:


BDISK PARAMETERS

This appendix provides general disk array parameters. Some parameters may not be relevant to your specific operating system. Consult your HP representative for information about supported configurations for specific operating systems.

Table 4 (page 72) through table 11 (page 88) describe the parameter values used in the installation process. These tables are referenced from the installation procedure.

71

Parameter Tables for OPEN-K/3/8/9/E Devices

Table 4. Parameters for OPEN-K/3/8/9/E Disk Types

Parameters for OPEN-K/3/8/9/E

Disk Type

OPEN-K OPEN-3 OPEN-8 OPEN-9 OPEN-E

Usage SCSI disk SCSI disk SCSI disk SCSI disk SCSI disk

Vendor name HP HP HP HP HP

Product name OPEN-K OPEN-3 OPEN-8 OPEN-9 OPEN-E

Number of blocks (512-byte block)

3661920 4806720 14351040 14423040 28452960

Sector size (byte) 512 512 512 512 512

Number of data cylinders(see Note 7)

2543 3338 9966 10016 19759

Number of heads 15 15 15 15 15

Number of sectors per track

96 96 96 96 96

Capacity (MB) 1740 2344 7004 7040 13888

Physical partition size in megabytes

See Note 2 4 8 8 8

Size of file system (see Note 1)

See Note 3 4792320 14319616 14401536 28409856

Queuing type Simple Simple Simple Simple Simple

Read/write time-out value

HP-UX: 30Other: 60

HP-UX: 30Other: 60

HP-UX: 30Other: 60

HP-UX: 30Other: 60

HP-UX: 30Other: 60

See “Notes for Parameter Tables for OPEN-K/3/8/9/E Devices” (page 76).


Table 5. Parameters for OPEN-K/3/8/9/E*n Disk Types

Parameters for OPEN-K/3/8/9/E*n

Disk Type

OPEN-K*n OPEN-3*n OPEN-8*n OPEN-9*n OPEN-E*n

Usage LU size expansion

LU size expansion

LU size expansion

LU size expansion

LU size expansion


Product name OPEN-K*n OPEN-3*n OPEN-8*n OPEN-9*n OPEN-E*n


361920*n 4806720*n 14351040*n 14423040*n 28452960*n

Sector size (byte) 512 512 512 512 512

Number of data cylinders

2543*n 3338*n 9966*n 10016*n 19759*n



96 96 96 96 96


See Note 2


See Note 3


Read/write time-out value

HP-UX: 30Other: 60

HP-UX: 30Other: 60

HP-UX: 30Other: 60

HP-UX: 30Other: 60

HP-UX: 30Other: 60


Disk Parameters 73

Table 6. Parameters for OPEN-K/3/8/9/E CVS Disk Types

Parameters for OPEN-K/3/8/9/E CVS

Disk Type

OPEN-K CVS OPEN-3 CVS OPEN-8 CVS OPEN-9 CVS OPEN-E CVS

Usage SCSI disk SCSI disk SCSI disk SCSI disk SCSI disk


Product name OPEN-K-CVS

OPEN-3-CVS

OPEN-8-CVS

OPEN-9-CVS

OPEN-E-CVS


See Note 4

Sector size (byte) 512 512 512 512 512

Number of data cylinders See Note 5



96 96 96 96 96


See Note 2


See Note 3


Read/write timeout value HP-UX: 30Other: 60

HP-UX: 30Other: 60

HP-UX: 30Other: 60

HP-UX: 30Other: 60

HP-UX: 30Other: 60



Table 7. Parameters for OPEN-K/3/8/9/E CVS*n Disk Types

Parameters for OPEN-K/3/8/9/E CVS*n

Disk Type

OPEN-K CVS*n OPEN-3 CVS*n OPEN-8 CVS*n OPEN-9 CVS*n OPEN-E CVS*n

Usage CVS LUSE CVS LUSE CVS LUSE CVS LUSE CVS LUSE


Product name OPEN-K*n-CVS

OPEN-3*n-CVS

OPEN-8*n-CVS

OPEN-9*n-CVS

OPEN-E*n-CVS


[Note 4]*n

Sector size (byte) 512 512 512 512 512

Number of data cylinders

See Note 6



96 96 96 96 96


See Note 2


See Note 3


Read/write timeout value

HP-UX: 30Other: 60

HP-UX: 30Other: 60

HP-UX: 30Other: 60

HP-UX: 30Other: 60

HP-UX: 30Other: 60


Disk Parameters 75

Notes for Parameter Tables for OPEN-K/3/8/9/E Devices

1. The operating system allocates some disk space for its own use. The maximum capacity of the disk cannot be specified for SIZE of File System at Add a Journaled File System.

2. The value of [Note 2] is the physical partition size in megabytes. The selectable physical partition sizes are 1, 2, 4, 8, 16, 32, 64, 128, and 256. The physical partition number for one disk must be less than or equal to 1016.

For OPEN-3*n, OPEN-8*n, and OPEN-9*n devices, use the physical partition size listed in “Physical Partition Size Table” (page 106).

For OPEN-K/3/8/9/E CVS, calculate the physical partition size [Note 2] using the following:

[Note 2] = round up ([Note 4]/(2048×1016)) to 2n

where:

[Note 6] = number of cylinders of LUSE composed byOPEN-K/3/8/9/E CVS volumes specified by SVP or remote console.

[Note 5] = number of cylinders of OPEN-K/3/8/9/E CVS specified by SVP or the remote console.

[Note 4] = number of blocks of CVS volumes calculated by:[Note 5] × (number of head) × (number of sectors per track).

Example To calculate the value of [Note 2] for OPEN-9 CVS, which has 6676 cylinders:

[Note 4] = 6676 × 15 × 96 = 9613440

([Note 4]/(2048 × 1016)) = (9613440/(2048 × 1016)) = 4.62

[Note 2] = round up 4.62 to 2n = 8


3. The value of [Note 3] is the size of the file system. Confirm the number of free physical partitions and the size of the physical partition.

Calculate the maximum size of the file system using the following equation:

Maximum size of file system = (Free PPs −1) × (PP Size) × 2048

where:

Free PPs = the number of free physical partitions

PP size = the size of physical partition

Example To calculate the maximum file size of an OPEN-3*20 device:

Free PPs = 733PP size = 64

Maximum size of file system = (Free PPs −1) × (PP Size) × 2048 =(733 −1) × 64 × 2048 = 95944704

95944704 is maximum size of file system for OPEN-3*20.

4. The value of [Note 4] is the number of blocks of CVS volumes.

This number is calculated by the equation:

[Note 4] = [Note 5] × (number of heads) × (number of sectors per track).

5. The value of [Note 5] is the number of cylinders of OPEN-K/3/8/9/E CVS corresponding to the capacity specified by the SVP or the remote console. The CVS size of OPEN-K/3/8/9/E is specified by capacity in megabytes, not by the number of cylinders. The number of cylinders in an OPEN-K/3/8/9/E CVS volume can be calculated as follows:

Number of cylinders = ↑ (specified capacity (MB) from SVP or remote console) × 1024 / 720↑ (↑↑ means round up to integer)

Example When 37 MB is specified for OPEN-3 CVS volume from the SVP, the number of cylinders of the OPEN-3 CVS can be calculated as follows:

37 × 1024/720 = 52.62

↑ 52.62 ↑ = 53 (↑↑ means round up to integer)

The OPEN-3 CVS volume has 53 cylinders.

Disk Parameters 77

6. The value of [Note 6] is the number of cylinders of LUSE composed of OPEN-K/3/8/9/E CVS volumes corresponding to the capacity specified by SVP or remote console. The CVS size of an OPEN-K/3/8/9/E device is specified by capacity in megabytes, not by the number of cylinders.

To calculate the number of cylinders of OPEN-K/3/8/9/E CVS volumes:

Number of cylinders = ↑ (specified capacity (mega byte) from the SVP or the remote console) × 1024 / 720 ↑ × n (↑↑ means round up to integer)

where n = the number of concatenated volumes for LUSE

Example When an OPEN-3 CVS volume is specified as 37 MB and the volumes are concatenated, calculate the number of cylinders of the OPEN-3 CVS as follows:

↑ 37 × 1024/720 ↑ × 4 = ↑ 52.62 ↑ × 4 = 53 × 4 = 212

The LUSE for OPEN-3 CVS volume has 212 cylinders.

7. Each disk has 2 alternate cylinders.


Table 8. Parameter Values of the OPEN-3 Disk Types

Disk Type

ParameterOPEN-3

OPEN-3*n (n=2 to 36) OPEN-3 CVS

OPEN-3 CVS*n (n=2 to 36)

ty Disk category Winchester Winchester Winchester Winchester

dt Control type SCSI SCSI SCSI SCSI

ns Sectors/tracks 96 96 96 96

nt Tracks/cylinder 15 15 15 15

nc Number of all cylinders 3,338 3,338*n Depends on configuration

of CV1

Depends on configuration

of CV3

rm Number of rotations of the disk

6,300 6,300 6,300 6,300

oa a partition offset(Starting block in a partition)

Set optionally Set optionally Set optionally Set optionally

ob b partition offset(Starting block in b partition)


oc c partition offset(Starting block in c partition)

0 0 0 0

od d partition offset(Starting block in d partition)


oe e partition offset(Starting block in e partition)


of f partition offset(Starting block in f partition)


og g partition offset(Starting block in g partition)


(continued)

Disk Parameters 79

oh h partition offset(Starting block in h partition)


pa a partition size Set optionally2 Set optionally2 Set optionally2 Set optionally2

pb b partition size Set optionally Set optionally Set optionally Set optionally

pc c partition size 4,806,720 4,806,720*n Depends on configuration

of CV1


of CV3

pd d partition size Set optionally Set optionally Set optionally Set optionally

pe e partition size Set optionally Set optionally Set optionally Set optionally

pf f partition size Set optionally Set optionally Set optionally Set optionally

pg g partition size Set optionally Set optionally Set optionally Set optionally

ph h partition size Set optionally Set optionally Set optionally Set optionally

ba a partition block size 8,192 8,192 8,192 8,192

bb b partition block size 8,192 8,192 8,192 Set optionally

bc c partition block size 8,192 8,192 8,192 8,192

bd d partition block size 8,192 8,192 8,192 8,192

be e partition block size 8,192 8,192 8,192 8,192

bf f partition block size 8,192 8,192 8,192 8,192

bg g partition block size 8,192 8,192 8,192 8,192

bh h partition block size 8,192 8,192 8,192 8,192

fa a partition fragment size 1,024 1,024 1,024 1,024

fb b partition fragment size 1,024 1,024 1,024 1,024

fc c partition fragment size 1,024 1,024 1,024 1,024

(continued)

Table 8. Parameter Values of the OPEN-3 Disk Types (continued)

Disk Type

ParameterOPEN-3




fd d partition fragment size 1,024 1,024 1,024 1,024

fe e partition fragment size 1,024 1,024 1,024 Set optionally

ff f partition fragment size 1,024 1,024 1,024 1,024

fg g partition fragment size 1,024 1,024 1,024 1,024

fh h partition fragment size 1,024 1,024 1,024 1,024

See “Notes for Table 8 Through Table 11” (page 90).


Disk Type

ParameterOPEN-3



Disk Parameters 81


Disk Type

ParameterOPEN-8






nt Tracks/cylinder 15 15 15 Set optionally


of CV1


of CV1


6,300 6,300 6,300 6,300

oa a partition offset(Starting block in a partition)


ob b partition offset(Starting block in b partition)


oc c partition offset(Starting block in c partition)

0 0 0 0

od d partition offset(Starting block in d partition)


oe e partition offset(Starting block in e partition)


of f partition offset(Starting block in f partition)


og g partition offset(Starting block in g partition)




(continued)





of CV1


of CV1







bb b partition block size 8,192 8,192 8,192 8,192




bf f partition block size 8,192 8,192 8,192 Set optionally

bg g partition block size 8,192 8,192 8,192 Set optionally






fe e partition fragment size 1,024 1,024 1,024 1,024

(continued)


Disk Type

ParameterOPEN-8



Disk Parameters 83






Disk Type

ParameterOPEN-8





Disk Type

ParameterOPEN-9






nt Tracks/cylinder 15 15 15 15


of CV1


of CV3


6,300 6,300 6,300 6,300

oa a partition offset(Starting block in apartition)


ob b partition offset(Starting block in bpartition)


oc c partition offset(Starting block in cpartition)

0 0 0 0

od d partition offset(Starting block in dpartition)


oe e partition offset(Starting block in epartition)


of f partition offset(Starting block in fpartition)


og g partition offset(Starting block in gpartition)


oh h partition offset(Starting block in hpartition)


(continued)

Disk Parameters 85




of CV1


of CV3







bb b partition block size 8,192 8,192 8,192 Set optionally




bf f partition block size 8,192 8,192 8,192 8,192







fe e partition fragment size 1,024 1,024 1,024 Set optionally

(continued)


Disk Type

ParameterOPEN-9









Disk Type

ParameterOPEN-9



Disk Parameters 87

Table 11. Parameter Values of the OPEN-K (XP256 only) Disk Types

Disk Type

ParameterOPEN-K

OPEN-K*n (n=2 to 36) OPEN-K CVS

OPEN-K CVS*n (n=2 to 36)

ty Disk category Winchester Winchester Depends on configuration

of CV1

Winchester

dt Control type SCSI SCSI Set optionally SCSI

ns Sectors/tracks 96 96 Set optionally 96

nt Tracks/cylinder 15 15 Set optionally Set optionally

nc Number of all cylinders 2,543 2,543*n Set optionally Depends on configuration

of CV3


6,300 6,300 Set optionally 6,300



pa a partition size Set optionally2 Set optionally2 1,024 Set optionally2

pb b partition size Set optionally Set optionally 1,024 Set optionally

pc c partition size 3,661,920 3,661,920*n 1,024 Depends on configuration

of CV3

pd d partition size Set optionally Set optionally 1,024 Set optionally

pe e partition size Set optionally Set optionally 1,024 Set optionally

pf f partition size Set optionally Set optionally 1,024 Set optionally

pg g partition size Set optionally Set optionally 1,024 Set optionally

ph h partition size Set optionally Set optionally 1,024 Set optionally

(continued)


ba a partition block size 8,192 8,192 Depends on configuration

of CV1

8,192

bb b partition block size 8,192 8,192 Set optionally 8,192

bc c partition block size 8,192 8,192 Set optionally 8,192

bd d partition block size 8,192 8,192 Set optionally 8,192

be e partition block size 8,192 8,192 Set optionally 8,192

bf f partition block size 8,192 8,192 Set optionally 8,192




fb b partition fragment size 1,024 1,024 8,192 Set optionally



fe e partition fragment size 1,024 1,024 8,192 1,024





Table 11. Parameter Values of the OPEN-K (XP256 only) Disk Types (continued)

Disk Type

ParameterOPEN-K

OPEN-K*n (n=2 to 36) OPEN-K CVS

OPEN-K CVS*n (n=2 to 36)

Disk Parameters 89

Notes for Table 8 Through Table 11

1. The value of pc is calculated as follows:

pc = nc ∗ nt ∗ ns

The nc of OPEN-K/3/8/9/E CVS corresponds to the capacity specified by SVP or remote console.

The CVS size of OPEN-K/3/8/9/E is specified by capacity (megabyte), not by number of cylinders.

The number of cylinders of an OPEN-K/3/8/9/E CVS volume can be obtained by the following calculation (↑ ↑means round up to integer).

The number of cylinders = ↑ (specified capacity in megabytes from SVP or remote console) × 1,024 / 720 ↑.

Example When 37 MB is specified for an OPEN-3 CVS volume from SVP, the number of cylinders of the OPEN-3 CVS can be calculated as follows:

37 × 1,024 / 720 = 52.62

↑52.62↑ = 53

The OPEN-3 CVS volume has 53 cylinders.

2. The value of pa must be equal to or more than 131,072.

3. The number of cylinders of a Logical Unit Size Expansion (LUSE) composed of OPEN-K/3/8/9/E CVS volumes corresponds to the capacity specified by the SVP or the remote console. CVS size ofOPEN-K/3/8/9/E is specified by the capacity (megabyte), not by the number of cylinders. The number of cylinders of the OPEN-K/3/8/9/E CVS volume can be obtained by the following calculation (↑ ↑ means round up to integer):

The number of cylinders = ↑ (specified capacity in megabytes from SVP or remote console) × 1,024 / 720 ↑ × n

where n is the number of concatenated volumes for LUSE.


Example When 37 MB is specified for the OPEN-3 CVS volume and the four volumes are concatenated, the number of cylinders of the OPEN-3 CVS can be calculated as follows:

↑37 × 1,024 / 720↑ × 4 = ↑52.62↑ × 4 = 53 × 4 = 212

The LUSE for the OPEN-3 CVS volume has 212 cylinders.

Disk Parameters 91

SCSI TID Map for Fibre Channel Adapters

When an arbitrated loop (AL) is established or reestablished, the port addresses are assigned automatically to prevent duplicate TIDs. With the SCSI over Fibre Channel protocol (FCP), there is no longer a need for target IDs in the traditional sense.

SCSI is a bus-oriented protocol requiring each device to have a unique address since all commands go to all devices. For Fibre Channel, the AL-PA is used instead of the TID to direct packets to the desired destination.

Unlike traditional SCSI, when control of the loop is acquired, a point-to-point connection is established from initiator to target. To enable transparent use of FCP, the operating system maps a TID to each AL-PA.

The host maps SCSI protocol to Fibre Channel protocol and detects and accesses Fibre Channel–connected devices using device files (/dev/dsk/c*t*d* and /dev/rdsk/c*t*d*) in the same way as for SCSI-connected devices. The device files for Fibre Channel–connected devices are configured in a different way from SCSI-connected devices, because Fibre Channel supports 126 addresses per path while SCSI supports 16 TIDs per path.

Table 12 (page 93) identifies the fixed mappings between the TID (drive) values assigned by the operating system and the Fibre Channel native addresses (AL_PA/SEL_ID) for Fibre Channel adapters. The controller number (the dks value in /dev/dsk/dks*d*l*s*) depends on the server configuration, and a different value is assigned per each column of table 12 (page 93).

The mapping cannot be guaranteed under the following conditions:

• when disk array devices and other types of devices are connected in the same loop

• when information for unused devices remains in the server system

• when multiple ports participate in the same arbitrated loop


Table 12. AL-PA to SCSI TID Mapping (t value)

AL-PA t value AL-PA t value AL-PA t value AL-PA t value AL-PA t value AL-PA t value AL-PA t value AL-PA t value

EF 0 CD 0 B2 0 98 0 72 0 55 0 3A 0 25 0

E8 1 CC 1 B1 1 97 1 71 1 54 1 39 1 23 1

E4 2 CB 2 AE 2 90 2 6E 2 53 2 36 2 1F 2

E2 3 CA 3 AD 3 8F 3 6D 3 52 3 35 3 1E 3

E1 4 C9 4 AC 4 88 4 6C 4 51 4 34 4 1D 4

E0 5 C7 5 AB 5 84 5 6B 4 4E 5 33 5 1B 5

DC 6 C6 6 AA 6 82 6 6A 6 4D 6 32 6 18 6

DA 7 C5 7 A9 7 81 7 69 7 4C 7 31 7 17 7

D9 8 C3 8 A7 8 80 8 67 8 4B 8 2E 8 10 8

D6 9 BC 9 A6 9 7C 9 66 9 4A 9 2D 9 0F 9

D5 10 BA 10 A5 10 7A 10 65 10 49 10 2C 10 08 10

D4 11 B9 11 A3 11 79 11 63 11 47 11 2B 11 04 11

D3 12 B6 12 9F 12 76 12 5C 12 46 12 2A 12 02 12

D2 13 B5 13 9E 13 75 13 5A 13 45 13 29 13 01 13

D1 14 B4 14 9D 14 74 14 59 14 43 14 27 14 00 –

CE 15 B3 15 9B 15 73 15 56 15 3C 15 26 15

Disk Parameters 93

Table 13 and table 14 identify the fixed mappings between the bus/TID/LUN addresses assigned by the operating system and the FC native addresses (AL_PA/SEL_ID) for FC adapters. There are two potential mappings, depending on the value of the ScanDown registry parameter:

• For ScanDown = 0 (default), see table 13 (page 95).

• For ScanDown = 1, see table 14 (page 100).

When disk array devices and other types of devices are connected in the same arbitrated loop, the mappings defined in table 13 and table 14 cannot be guaranteed.

Emulex The Emulex driver emulates six Fibre busses per adapter to map all 126 possible AL-PAs to target IDs. The first bus (bus 0) is a dummy bus.


Table 13. SCSI TID map for Emulex FC Adapter(ScanDown=0)

Bus Number TID LUN AL_PA SEL_ID

0 0-31 0-7 None None1 0 0-7 0x01 0x7D

1 0-7 0x02 0x7C

2 0-7 0x04 0x7B3 0-7 0x08 0x7A4 0-7 0x0F 0x79

5 0-7 0x10 0x786 0-7 0x17 0x777 0-7 0x18 0x76

8 0-7 0x1B 0x759 0-7 0x1D 0x7410 0-7 0x1E 0x73

11 0-7 0x1F 0x7212 0-7 0x23 0x7113 0-7 0x25 0x70

14 0-7 0x26 0x6F15 0-7 0x27 0x6E16 0-7 0x29 0x6D

17 0-7 0x2A 0x6C18 0-7 0x2B 0x6B19 0-7 0x2C 0x6A

20 0-7 0x2D 0x6921 0-7 0x2E 0x6822 0-7 0x31 0x67

23 0-7 0x32 0x6624 0-7 0x33 0x6525 0-7 0x34 0x64

26 0-7 0x35 0x6327 0-7 0x36 0x6228 0-7 0x39 0x61

29 0-7 0x3A 0x6030 0-7 0x3C 0x5F31 0-7 None None

(continued)

Disk Parameters 95

2 0 0-7 0x43 0x5E1 0-7 0x45 0x5D2 0-7 0x46 0x5C

3 0-7 0x47 0x5B4 0-7 0x49 0x5A5 0-7 0x4A 0x59

6 0-7 0x4B 0x587 0-7 0x4C 0x578 0-7 0x4D 0x56

9 0-7 0x4E 0x5510 0-7 0x51 0x5411 0-7 0x52 0x53

12 0-7 0x53 0x5213 0-7 0x54 0x5114 0-7 0x55 0x50

15 0-7 0x56 0x4F16 0-7 0x59 0x4E17 0-7 0x5A 0x4D

18 0-7 0x5C 0x4C19 0-7 0x63 0x4B20 0-7 0x65 0x4A

21 0-7 0x66 0x4922 0-7 0x67 0x4823 0-7 0x69 0x47

24 0-7 0x6A 0x4625 0-7 0x6B 0x4526 0-7 0x6C 0x44

27 0-7 0x6D 0x4328 0-7 0x6E 0x4229 0-7 0x71 0x41

30 0-7 0x72 0x4031 0-7 None None

(continued)

Table 13. SCSI TID map for Emulex FC Adapter(ScanDown=0) (continued)



3 0 0-7 0x73 0x5E1 0-7 0x74 0x5D

2 0-7 0x75 0x5C3 0-7 0x76 0x5B4 0-7 0x79 0x5A

5 0-7 0x7A 0x596 0-7 0x7C 0x587 0-7 0x80 0x57

8 0-7 0x81 0x569 0-7 0x82 0x5510 0-7 0x84 0x54

11 0-7 0x88 0x5312 0-7 0x8F 0x5213 0-7 0x90 0x51

14 0-7 0x97 0x5015 0-7 0x98 0x4F16 0-7 0x9B 0x4E

17 0-7 0x9D 0x4D18 0-7 0x9E 0x4C19 0-7 0x9F 0x4B

20 0-7 0xA3 0x4A21 0-7 0xA5 0x4922 0-7 0xA6 0x48

23 0-7 0xA7 0x4724 0-7 0xA9 0x4625 0-7 0xAA 0x45

26 0-7 0xAB 0x4427 0-7 0xAC 0x4328 0-7 0xAD 0x42

29 0-7 0x71 0xAE30 0-7 0x72 0xB131 0-7 None None

(continued)



Disk Parameters 97

4 0 0-7 0xB2 0x201 0-7 0xB3 0x1F

2 0-7 0xB4 0x1E3 0-7 0xB5 0x1D4 0-7 0xB6 0x1C

5 0-7 0xB9 0x1B6 0-7 0xBA 0x1A7 0-7 0xBC 0x19

8 0-7 0xC3 0x189 0-7 0xC5 0x1710 0-7 0xC6 0x16

11 0-7 0xC7 0x1512 0-7 0xC9 0x1413 0-7 0xCA 0x13

14 0-7 0xCB 0x1215 0-7 0xCC 0x1116 0-7 0xCD 0x10

17 0-7 0xCE 0x0F18 0-7 0xD1 0x0E19 0-7 0xD2 0x0D

20 0-7 0xD3 0x0C21 0-7 0xD4 0x0B22 0-7 0xD5 0x0A

23 0-7 0xD6 0x0924 0-7 0xD9 0x0825 0-7 0xDA 0x07

26 0-7 0xDC 0x0627 0-7 0xE0 0x0528 0-7 0xE1 0x04

29 0-7 0xE2 0x0330 0-7 0xE4 0x0231 0-7 None None

(continued)




5 0 0-7 None None1 0-7 None None

2 0-7 None None3 0-7 None None4 0-7 None None












Disk Parameters 99

Table 14. SCSI TID map for Emulex FC Adapter (ScanDown=1)


0 0-31 0-7 None None1 0 0-7 0xEF 0x00

1 0-7 0xE8 0x01

2 0-7 0xE4 0x023 0-7 0xE2 0x034 0-7 0xE1 0x04

5 0-7 0xE0 0x056 0-7 0xDC 0x067 0-7 0xDA 0x07

8 0-7 0xD9 0x089 0-7 0xD6 0x0910 0-7 0xD5 0x0A

11 0-7 0xD4 0x0B12 0-7 0xD3 0x0C13 0-7 0xD2 0x0D

14 0-7 0xD1 0x0E15 0-7 0xCE 0x0F16 0-7 0xCD 0x10

17 0-7 0xCC 0x1118 0-7 0xCB 0x1219 0-7 0xCA 0x13

20 0-7 0xC9 0x1421 0-7 0xC7 0x1522 0-7 0xC6 0x16

23 0-7 0xC5 0x1724 0-7 0xC3 0x1825 0-7 0xBC 0x19

26 0-7 0xBA 0x1A27 0-7 0xB9 0x1B28 0-7 0xB6 0x1C

29 0-7 0xB5 0x1D30 0-7 0xB4 0x1E31 0-7 None None

(continued)


2 0 0-7 0xB3 0x1F1 0-7 0xB2 0x20

2 0-7 0xB1 0x213 0-7 0xAE 0x224 0-7 0xAD 0x23

5 0-7 0xAC 0x246 0-7 0xAB 0x257 0-7 0xAA 0x26

8 0-7 0xA9 0x279 0-7 0xA7 0x2810 0-7 0xA6 0x29

11 0-7 0xA5 0x2A12 0-7 0xA3 0x2B13 0-7 0x9F 0x2C

14 0-7 0x9E 0x2D15 0-7 0x9D 0x2E16 0-7 0x9B 0x2F

17 0-7 0x98 0x3018 0-7 0x97 0x3119 0-7 0x90 0x32

20 0-7 0x8F 0x3321 0-7 0x88 0x3422 0-7 0x84 0x35

23 0-7 0x82 0x3624 0-7 0x81 0x3725 0-7 0x80 0x38

26 0-7 0x7C 0x3927 0-7 0x7A 0x3A28 0-7 0x79 0x3B

29 0-7 0x76 0x3C30 0-7 0x75 0x3D31 0-7 None None

(continued)

Table 14. SCSI TID map for Emulex FC Adapter (ScanDown=1) (continued)


Disk Parameters 101

3 0 0-7 0x74 0x3E1 0-7 0x73 0x3F

2 0-7 0x72 0x403 0-7 0x71 0x414 0-7 0x6E 0x42

5 0-7 0x6D 0x436 0-7 0x6C 0x447 0-7 0x6B 0x45

8 0-7 0x6A 0x469 0-7 0x69 0x4710 0-7 0x67 0x48

11 0-7 0x66 0x4912 0-7 0x65 0x4A13 0-7 0x63 0x4B

14 0-7 0x5C 0x4C15 0-7 0x5A 0x4D16 0-7 0x59 0x4E

17 0-7 0x56 0x4F18 0-7 0x55 0x5019 0-7 0x54 0x51

20 0-7 0x53 0x5221 0-7 0x52 0x5322 0-7 0x51 0x54

23 0-7 0x4E 0x5524 0-7 0x4D 0x5625 0-7 0x4C 0x57

26 0-7 0x4B 0x5827 0-7 0x4A 0x5928 0-7 0x49 0x5A

29 0-7 0x47 0x5B30 0-7 0x46 0x5C31 0-7 None None

(continued)




4 0 0-7 0x45 0x5D1 0-7 0x43 0x5E

2 0-7 0x3C 0x5F3 0-7 0x3C 0x604 0-7 0x39 0x61

5 0-7 0x36 0x626 0-7 0x35 0x637 0-7 0x34 0x64

8 0-7 0x33 0x659 0-7 0x32 0x6610 0-7 0x31 0x67

11 0-7 0x2E 0x6812 0-7 0x2D 0x6913 0-7 0x2C 0x6A

14 0-7 0x2B 0x6B15 0-7 0x2A 0x6C16 0-7 0x29 0x6D

17 0-7 0x27 0x6E18 0-7 0x26 0x6F19 0-7 0x25 0x70

20 0-7 0x23 0x7121 0-7 0x1F 0x7222 0-7 0x1E 0x73

23 0-7 0x1D 0x7424 0-7 0x1B 0x7525 0-7 0x18 0x76

26 0-7 0x17 0x7727 0-7 0x10 0x7828 0-7 0x0F 0x79

29 0-7 0x08 0x7A30 0-7 0x04 0x7B31 0-7 None None

(continued)



Disk Parameters 103

5 0 0-7 0x02 0x7C1 0-7 0x01 0x7D














Byte Information Table

Category LU Product NameNumber of Bytes per Inode

OPEN-3 OPEN-3OPEN-3*2-OPEN-3*28

4096

OPEN-3*29-OPEN-3*36 8192


4096

OPEN-8*10-OPEN-8*18 8192

OPEN-8*19-OPEN-8*36 16384


4096

OPEN-8*10-OPEN-8*18 8192

OPEN-8*19-OPEN-8*36 16384

OPEN-3/8/9/K CVS

OPEN-3 CVSOPEN-9 CVS

4096

OPEN-3/8/9/K*n CVS

35-64800 4096

64801-126000 8192

126001 and higher 16384

OPEN-E OPEN-E 4096

Disk Parameters 105

Physical Partition Size Table

Category LU Product NamePhysical Partition Size in Megabytes

OPEN-K OPEN-K 2

OPEN-K*2 4

OPEN-K*3 to OPEN-K*4 8




OPEN-3 OPEN-3 4

OPEN-3*2 to OPEN-3*3 8




OPEN-3*28 to OPEN-3*36 128

OPEN-8 OPEN-8 8

OPEN-8*2 16



OPEN-8*10 to OPEN-8*18 128

OPEN-8*19 to OPEN-8*36 256

(continued)


OPEN-9 OPEN-9 8

OPEN-9*2 16



OPEN-9*10 to OPEN-9*18 128

OPEN-9*19 to OPEN-9*36 256

OPEN-E OPEN-E 16

OPEN-E*2 32

OPEN-E*3 to OPEN-E*4 64



OPEN-K/3/8/9/E*n CVS

35 to1800 2

1801 to 2300 4

2301 to 7000 8

7001 to 16200 16

13201 to 32400 32

32401 to 64800 64

64801 to 126000 128

126001 and higher 256

Category LU Product NamePhysical Partition Size in Megabytes

Disk Parameters 107

Host Bus Adapter Modes

HBA Operating System Host Mode

Compaq KGPSA-BY Compaq Tru64 00

Compaq 64Bit/66MHz120186-B21 (P/N)

Windows 2000Windows NT

08

Emulex LP6000 Sequent Dynix Ptx 04

Emulex LP7000/E IBM AIX 00


00 or 0C (Non-MSCS)

0C (MSCS)

Novell NetWare 0A

Sun Solaris 09

Linux Red Hat 00

Emulex LP8000 Windows 2000Windows NT

00 or 0C (Non-MSCS)

0C (MSCS)

Linux Red Hat 00

Novell NetWare 0A

HP A5158A HP-UX 08

HP A3740A HP-UX 08

HP A3636A HP-UX 08

HP A3591B HP-UX 08

HP A3404A HP-UX 08

HP D8602A Windows 2000Windows NT

08

Novell NetWare 0A

(continued)


IBM 6227 IBM AIX 00 (Non-HACMP)

0F (HACMP)

JNI FCI-1063JNI FC64-1063

Sun Solaris 09

Q-Logic QLA2100F Linux Red Hat 00

SGI IRIX 00

Novell NetWare 0A

SGI IRIX 00


00 or 0C (Non-MSCS)

0C (MSCS)

Q-Logic QLA2200F Windows 2000Windows NT

00 or 0C (Non-MSCS)

0C (MSCS)

Novell NetWare 0A

Q-Logic QLA2202F Linux Red Hat 00


00 or 0C (Non-MSCS)

0C (MSCS)

Novell NetWare 0A

SGI IRIX 00

Sequent Sequent Dynix Ptx 04

SUN X6729ASUN X6730A

Sun Solaris 09

HBA Operating System Host Mode

Disk Parameters 109

Related Information For information about HBAs and to download drivers, execute a search at the appropriate vendor’s web site:

Agilent & HP www.hp.com

Emulex www.emulex.com

QLogic www.qlogic.com

Sun www.sun.com


http://www.hp.com/

http://www.emulex.com/

http://www.qlogic.com/

http://www.sun.com/

CSUPPORTED HOST MODES

Table 15 (page 112) lists the supported host modes for the disk arrays.

111

Table 15. Host Modes Supported by the Disk Array

Interface TypeHost Mode Description XP256

XP48XP512

Fast-Wide Differential (FWD) SCSI or Fibre Channel (FC)

00 Standard mode: FWD/FC (see note 1) Supported Supported

01 IBM-7135 (FWD) Supported Not supported(see note 2)

02 NCR (FWD) Supported Not supported(see note 2)

03 Reserved

04 Sequent (FWD) Supported Supported

05 Compaq OpenVMS (FWD) Supported Supported

06 Reserved

07 Reserved

08 HP-UX (FWD or FC)Queue depth: 1024LUNs per port: 120HP NetServer with HP-HBAs(see note 3)

Supported Supported

09 Sun Vx VM-DMP/Sun Cluster (FWD) Supported Supported

0A NetWare (FWD) Supported Supported

0B MPE Supported Not supported(see note 2)

0C Microsoft Cluster Server (MSCS) Multipath: non-HP HBAs (FWD)(see note 4)

Supported Supported

0D Compaq OpenVMS (FC) Supported Supported

0E Reserved

0F HACMP + Tachyon Supported Supported

(continued)


Ultra SCSI 10 Standard SCSI + Ultra SCSI mode(see note 1)

Supported Not supported(see note 2)

11 IBM-7135 host mode + Ultra SCSI mode

Supported

12 NCR host mode + Ultra SCSI mode Supported

13 Reserved

14 Sequent host mode + Ultra SCSI mode Supported

15 Compaq OpenVMS (Ultra SCSI) Supported

16 Reserved

17 Reserved

18 HP host mode + Ultra SCSI mode Supported

19 Sun VxVM-DMP + Ultra SCSI mode(see note 4)

Supported

1A NetWare + Ultra SCSI mode Supported

1B MPE Mode Supported

1C Microsoft Cluster Server (MSCS) + Ultra SCSI mode (non-HP HBAs)

Supported

1D Compaq OpenVMS (Ultra SCSI) Supported

1E Reserved

1F Reserved

Table notes:

1. Modes 00/10 are used for Windows NT and Windows 2000 (non-HP FC HBAs and all NT SCSIs), Solaris, DEC, and AIX FWD SCSI.

2. These host modes are not supported in Fibre Channel environment.

3. Mode 08 is used for FC-AL on HP-UX, SCSI on MPE/iX, Windows 2000, and NT FC with HP HBAs.Mode 08 allows a queue depth of 1024 and 120 (XP256); 256 (XP512) LUNs per port.

4. Enabling Veritas host mode also requires enabling system mode 19 via the service processor (SVP) in addition to setting the host mode for the port. This activity is no longer required as of 43-12 microcode. Contact your HP representative for assistance with this procedure.

Table 15. Host Modes Supported by the Disk Array (continued)

Interface TypeHost Mode Description XP256

XP48XP512

Supported Host Modes 113

DSNMP REMOTE DISK ARRAY

MANAGEMENT

Simple Network Management Protocol (SNMP) is a part of the TCP/IP protocol suite that supports maintenance functions for storage and communication devices. The disk array uses SNMP to transfer status and management commands to a PC server or open-system host via the remote console PC.

When the SNMP manager requests status information or when a remote service information message (R-SIM) is generated, the SNMP agent on the remote console PC notifies the SNMP manager on the PC server or open-system host. R-SIM reporting enables the user to monitor the disk array from the PC server or open-system host without having to check the remote console PC for R-SIMs.

115

Figure 1. SNMP Information Flow

The SNMP agent on the remote console PC can perform error reporting operations for up to eight disk arrays. The SNMP agent only initiates trap operations, which alert the SNMP manager when an R-SIM occurs.

The SNMP manager, which resides on the PC server or open-system host, requests information from the SNMP agent and receives the R-SIM traps from the SNMP agent. For assistance with SNMP manager configuration on the PC server or open-system host, please refer to the vendor’s documentation for the SNMP management software, or contact the vendor’s technical support.


EONLINE INSTALLATION AND

DEINSTALLATION OF DEVICES

After initial installation and configuration of the disk array, additional devices can be installed or deinstalled online without having to restart the system. After online installation, the device parameters for new volumes must be changed to match the LUs defined under the same Fibre Channel port.

Related Information For additional instructions regarding online installation and deinstallation of LUs, see the following product manual:


117

GLOSSARY

ACA HP Surestore Asynchronous Continuous Access XP.

ACP Array Control Processor. The ACP handles the passing of data between the cache and the physical drives held in the DKUs. ACPs work in pairs, providing a total of 8 SCSI buses. Each SCSI bus associated with one ACP is paired with a SCSI bus on the other ACP pair element. In the event of an ACP failure, the redundant ACP takes control. Both ACPs work together sharing the load.

AL Arbitrated loop.

AL-PA Arbitrated loop physical address

allocation The ratio of allocated storage capacity versus total capacity as a percentage. “Allocated storage” refers to those LDevs that have Paths assigned to them. The allocated storage capacity is the sum of the storage of these LDevs. Total capacity refers to the sum of the capacity of all Ldevs on the Array.

arraygroup The number of physical disk drives contained in a RAID group. This num-ber depends on the RAID configuration. For example, there may be two or four physical disks in a RAID1 group. There are four physical disks in a RAID5 group.

BC The HP Surestore Business Copy XP software program that lets you maintain up to nine internal copies of logical volumes on the disk array.

BS Basic supply.

BTU British thermal unit.

°C Degrees centigrade/Celsius.

119

CA The HP Surestore Continuous Access XP software program that lets you create and maintain duplicate copies of the data store on a local disk array.

ca Cache.

cache Very high speed memory that is used to speed I/O transaction time. All reads and writes to the XP array family are sent to the cache. The data is buffered there until the transfer to/from physical disks (with slower data throughput) is complete.

The benefit of cache memory is that it speeds I/O throughput to the applica-tion. The larger the cache size, the greater amount of data buffering can occur and the greater throughput to the applications.

The XP array family supports between 1-16 GB of cache memory. In the event of power loss, the contents of the cache boards are battery backed in order to survive up to 48 hours.

CE Customer engineer.

CFW Cache fast write.

CH Channel.

channel adapter (CHA)

The channel adapter (CHA) provides the interface between the disk array and the external host system. Occasionally this term is used synonymously with the term channel host interface processor (CHIP)

channel host interface processor (CHIP)

Synonymous with the term channel adapter (CHA).

channel processor (CHP)

The processor(s) located on the channel adapter (CHA).

CHPID Channel path identifier.

CKD Count key data.

CL Cluster.

command device A volume on the disk array that accepts CA or BC control operations which are then executed by the disk array.


configuration file A file that defines the pair configurations.

consistency group ID (CTGID)

The group identifier for which the disk array guarantees the sequence of asynchronous data transfer for the asynchronous CA volume group.

control unit To organize the storage space attached to the DKC, you can group similarly configured logical devices (LDEVs) with unique control unit images (CUs). CUs are numbered sequentially.

The XP256 supports up to 4 CUs. The XP512/48 supports up to 16 CUs.

Each CU is able to manage up to 256 LDEVs. Therefore, to uniquely iden-tify a particular LDEV requires both the CU number as well as the LDEV number.

CPU Central processing unit.

CSA Canadian Standards Association

CT Continuous Track maintenance support application.

CU control unit.

CVS Custom Volume Size (also called Virtual LVI).

daemon A process that resides in the UNIX system and waits for events and that does not disappear after an event is carried out.

DASD Direct Access Storage Device.

DCR Dynamic cache residency (also called Cache LUN XP).

DE HP Surestore Data Exchange XP.

DFDSS Data Facility Dataset Services.

DFSMS Data Facility System Managed Storage.

DFW DASD Fast Write.

disk adapter (DKA) Synonymous with the term ACP.

disk controller unit (DKC)

The disk controller unit (DKC) refers to the array hardware which houses the channel adapters and service processor (SVP).

Glossary 121

disk cabinet unit (DKU)

The Disk Cabinet Unit (DKU) refers to the array hardware which houses the physical disks in the array.

disk recovery and restore unit (DRR)

The unit located on the ACP that is responsible for data recovery and resto-ration in the event of a cache failure.

disk group The physical disk locations associated with a parity group.

disk type The manufacturing label burned into the physical disk controller firmware. In most cases, the disk type is identical to the disk model number.

DMP Dynamic multipathing.

dr Drive.

DSF Device support facilities.

DW Duplex write.

DWL Duplex write line.

ECKD Extended Count Key Data.

EFS The IRIX standard file system.

emulation modes The Logical Devices (LDEVs) associated with each raid group may have one of the following emulation modes. These modes change the behavior of the disks and determine their size.

• Open-3: 2.46 GB

• Open-8: 7.38 GB

• Open-9: 7.42 GB

EOF End Of Field.

EPO Emergency power-off.

EREP Error reporting.

ESA Enterprise Systems Architecture.

ESCON Enterprise System Connection (the IBM trademark for optical channels).


expanded LUN A LUN is normally associated with only a single LDEV. The LUN Size Expansion (LUSE) feature allows a LUN to be associated with between 1-36 LDEVs. Essentially, LUSE makes it possible for applications to access a single large pool of storage. The LUSE feature is available when the HP Surestore LUN Configuration Manager product is installed.

ExSA Extended serial adapter.

failover Disconnecting a failed portion and replacing it with another normal portion or alternative portion in order to continue functioning.

FAL File Access Library (part of the Data Exchange software).

FBA Fixed-Block Architecture.

FC Fibre Channel.

FC-AL Fibre Channel arbitrated loop.

FCC Federal Communications Commission.

FCP Fibre Channel Protocol.

FCU File conversion utility (part of the Data Exchange software).

FDR Fast dump/restore.

fence level A level for selecting rejection of a write I/O request from the host according to the condition of mirroring consistency.

F/M Format/Message.

ft. Foot or feet.

FWD Fast wide differential.

fx The IRIX disk utility.

GB Gigabytes.

GLM Gigabyte link module.

GUI Graphical user interface.

HA High availability.

Glossary 123

HBA Host bus adapter.

HCD Hardware configuration definition.

HORC HP Surestore Continuous Access XP.

HORCM_CMD A section of the RM instance configuration file that defines the disk devices used by RM to communicate with the disk array.

HORCM_DEV A section of the RM instance configuration file that defines the volumes of the instance.

HORCM_INST A section of the RM instance configuration file that defines how RM groups link to remote RM instances.

HORCM_MON A section of the RM instance configuration file that defines the instance you are configuring.

host mode Each port can be configured with various options referred to as host modes. These modes are represented as a 2 digit hexidecimal number. The first hex digit represents special options; currently only number 10 is defined which represents Fast Wide SCSI protocol support. The second hex digit repre-sents behavior for a specific host. These two numbers may be combined. For example, mode 18 represents Fast Wide SCSI protocol support on an HP-UX host.

hot standby Using two or more servers as a standby in case of a primary server failure.

HP Hewlett-Packard Company.

H/W Hardware.

Hz Hertz.

IBM International Business Machines Corporation.

ICKDSF A DSF command used to perform media maintenance.

IDCAMS Access method services (a component of Data Facility Product).

IML Initial microprogram load.

in. Inches.


I/O Input/output (applies to an operation or device).

IOCP Input/output configuration program

instance An independent copy of RM. Instances are local or remote and can run on the same host.

JCL Job control language.

KB Kilobyte.

kcal Kilocalorie.

kg Kilogram.

km Kilometer.

kVA Kilovolt-ampere.

kW Kilowatt.

LAN Local area network.

lb. Pound.

LCP Local control port.

LD, LDEV Logical device. An LDEV is created when a RAID group is carved into pieces according to the selected host emulation mode (that is, OPEN-3, OPEN-8, OPEN-9). The number of resulting LDEVs depends on the selected emulation mode. The term LDEV is often used synonymously with the term volume.

LED Light emitting diode.

local disk A local disk in the host.

local instance The instance currently being configured or the instance to which commands are issued.

LPAR Logical partition.

LCP Link Control Processor or Local Control Port.

LRU Least recently used.

Glossary 125

LU Logical Unit.

LUN Logical Unit Number. A LUN results from mapping a SCSI logical unit number, port ID, and LDEV ID to a RAID group. The size of the LUN is determined by the emulation mode of the LDEV, and the number of LDevs associated with the Lun. For example, a LUN associated with two Open-3 LDEVs will have a size of 4,693 MB.

LUSE Logical unit size expansion.

LVI Logical volume image.

LVM Logical Volume Manager.

LVM mirror A disk duplicating function provided by Logical Volume Manager (LVM) (capable of triplicating disks).

m Meters.

MB Megabytes.

MCU Main control unit.

mirroring consistency

The consistency (usability) of data in a volume (for example, S-VOL).

mm Millimeters.

MP Microprocessor.

MPLF Multipath Locking Facility.

MR Magnetoresistive.

ms, msec Milliseconds.

mutual hot standby system

Two servers that are poised to cover for each other if necessary.

MVS Multiple Virtual Storage (including MVS/370, MVS/ESA, MVS/XA).

NHAS Novell High Availability Server.

node Logically speaking, an environment where instances can be executed. Physically, a processor, which is an element of a cluster system.


NVS Nonvolatile storage.

OEM Original Equipment Manufacturer.

OFC Open Fibre Control.

OLM Optical link module.

ORM Online read margin.

OS Operating system.

P/DAS PPRC/Dynamic Address Switching.

PA Physical address.

parity group A parity group is a mode of disk operation and configuration. It is synony-mous with the term RAID group.

partition Dividing a specific physical disk according to the HP-UX kernel or device driver layer into two or more areas as if there are two or more physical disks.

path On the XP256 array, a path and a LUN are synonymous. Paths are created by associating a port, a target, and a LUN ID to one or more LDEVs.

PC Personal computer.

PCI Power control interface or peripheral component interconnect.

PM Performance Manager software.

port The number of supported ports on an XP disk array is dependent upon the number of supported I/O slots and the number of ports available per I/O adapter. The XP family of disk arrays supports SCSI, Fibre Channel (FC/AL), and ESCON I/O interfaces. I/O support may vary with the selected disk array.

Ports are named based upon their port group and port letter. Examples of port names include CL1-A through CL1-R and CL2-A through CL2-R (letters I and O are skipped).

P-P Point-to-point.

PPRC Peer-to-peer remote copy.

Glossary 127

PS Power supply.

P-VOL The primary or main volume that contains the data to be copied.

R&S Russel & Stoll.

RAID Redundant array of inexpensive disks.

RAID Group A RAID group is a mode of disk operation and configuration. RAID groups 1 to 5 vary in the number of bits used in data/parity encoding, mirroring, and striping features.

You may occasionally see the term parity group used synonymously with RAID group.

RAM Random access memory.

RC Reference code or remote control software.

RCP Remote control port.

RCU Remote control unit.

remote instance The instance to which the local instance communicates as configured in the HORCM_INST section of the RM instance configuration file.

RISC Reduced instruction set computer.

RM HP Surestore RAID Manager XP.

RMC Remote console.

RM instance configuration file

A file that defines the link between a volume and an RM instance. This file consists of four sections: HORCM_MON, HORCM_CMD, HORCM_DEV and HORCM_INST.

R-SIM Remote service information message.

R/W, r/w Read/write.

S/390 IBM System/390 architecture.

SAM System Administration Manager.

script file A file containing a shell script.


SCSI Small computer system interface.

sec. Second.

seq. Sequential.

SGI Silicon Graphics Incorporated.

shell script A command sequence executed by a UNIX shell.

Sidefile An area of XP256 cache used to store the data sequence number, record location, record length, and queued control information before transmit over the ESCON link.

SIM Service information message.

SMS System managed storage.

SNMP Simple Network Management Protocol.

special files Files that indicate physical devices and are different from regular files in the UNIX system. The functions of the device drivers (that is, access to system peripherals) become available through these special files.

SSID Storage subsystem identification.

SVP Service processor, which is the laptop PC that is built into the DKC. The SVP provides a direct interface into the disk array. SVP use is reserved for the HP CE only.

S-VOL Secondary or remote volume. The copy volume that receives the data from the primary volume.

takeover The actions of a standby server that takes over processing from the previously active server.

TB Terabyte.

TID Target ID.

TPF Transaction processing facility.

TSO Time-sharing option (an IBM System/370 operating system option).

UCB Unit control block.

Glossary 129

UL Underwriters’ Laboratories.

VDE Verband Deutscher Elektrotechniker.

VM Virtual machine (an IBM S/390 system control program).

VOLID Volume ID.

volser Volume serial number.

Volume Synonymous with LDEV.

XRC Extended Remote Copy.

VSE Virtual Storage Extension (an IBM S/390 operating system).

VTOC Volume table of contents.

XA System/370 Extended Architecture.

XDF Extended distance feature (for ExSA channels).

XF IRIX extended file system.

XLV Extended logical volume manager.


INDEX

Aauto-mount parameter

set and verify 58

Cconfiguration

disk array 44Emulex LightPulse LP7000 37Sun X6729A adapter 38

connection problemstroubleshooting 68

connectivityoptions 12

cylinderscalculating for disk volume 90

Ddevices

add 22display information 17label 47set parameters 40supported types 13verify recognition 44

disk arrayconfigure 44connect 42prepare to connect 15

disk parametersset 40

disk volumecalculating number of cylinders 90

EEmulex LightPulse LP7000

configure 37error messages

troubleshooting 65

FFibre Channel

interface 11topology parameters 16verify host adapter recognition 46

Fibre Channel adaptersSCSI TID map 92verify installation 23

Fibre Channel pathsdefine 21

Fibre Channel portsconfigure 19

131

fibre switchconnect 28

file systemcreate 55mount and verify 57

Gglossary 119

Hhost bus adapters

modes 108host modes

set 18supported 112

II/O timeout

set 40installation

LUN Configuration Manager 16parameter values 71procedures 14remote console PC 16requirements 10

JJNI driver

configure 27

Lloop ID

conflicts 20LUN Configuration Manager

install 16

Mmount directory

create and verify 56

OOPEN-3 disk type

parameter values 79OPEN-8 disk type

parameter values 82OPEN-9 disk type

parameter values 85OPEN-K (XP256) disk type

parameter values 88

Pparameter tables

byte information 105host bus adapter modes 108OPEN-K/3/8/9/E devices 72physical partition size 106

parameter valuesinstallation 71OPEN-3 disk type 79OPEN-8 disk type 82OPEN-9 disk type 85OPEN-K (XP256) 88

partitioncreate 47label 47

pinned trackrepair 64

port addressconfigure 20

Rremote console PC

installation 16


SSCSI adapters

differential 11SCSI paths

add 22define 21identify 17worksheet 70

shut downsystem 42

Sun X6729A adapterconfigure 38

Ttopology parameters

configure 19troubleshooting

connection problems 67error conditions 62error messages 65HP Support Center 68verbose mode 65

Vverbose mode

troubleshooting 65

Wworksheet

SCSI paths 70

133

Reader Comment Sheet

HP Surestore Disk Array XP Operating System Configuration GuideSun Solaris

We welcome your evaluation of this manual. Your comments and suggestions will help us improve our publications. Remove

this page and mail or FAX it to 916-785-4677. Use and attach additional pages if necessary.

Comments_________________________________________________________________________________

________________________________________________________________________________

________________________________________________________________________________

________________________________________________________________________________

___ Check here if you would like a reply.

Hewlett-Packard has the right to use submitted suggestions without obligation, with all such ideas becoming the property of Hewlett-Packard.

XPSO Technical Marketing A5951-96031 E0201

Agree Disagree N/A

The manual is well organized.

The information is technically accurate.

Information is easy to find.

Step-by-step procedures are easy to perform.

There are enough examples and pictures.

The examples and pictures are useful.

Name: Phone:

Title: FAX:

Company: E-mail:

Address: ZIP:

City & State: Country:

NO POSTAGE NECESSARY

IF MAILEDIN THE

UNITED STATES

��

Fold Here

Tape Please Do Not Staple Tape

BUSINESS REPLY MAILFIRST CLASS MAIL PERMIT NO. 256 ROSEVILLE, CA

Attention: Technical Marketing (MS 5785)

XPSOHewlett-Packard Company8000 Foothills Blvd.Roseville, CA 95747-5785

POSTAGE WILL BE PAID BY ADDRESSEE

�

Copyright © 2001Hewlett-Packard CompanyPrinted in USA

Customer Order NumberA5951-90903

E0201 Manufacturing Part NumberA5951-96031

*A5951-96031*

hp disks with veritas

Documents