12 M9 Operating Systems

7/28/2019 12 M9 Operating Systems

1/30

2006 Hewlett-Packard Development Company, L.P.The information contained herein is subject to change without notice

Storage Presentationto Operating Systems

Module 9


2/30

Rev. 6.21 HP Restricted 1

Objective Verify device connectivity for:

HP-UX Windows OpenVMS Tru64


3/30


HP-UX

connectivity


4/30


ioscan To search for installed HBAs, issue:

# ioscan f Available switches

-f Full output -n Show device node information -k Scan kernel instead of I/O path -C Scan devices in a specific class -d td Restrict output to only td devices


5/30


Verifying HBA installation ioscan -f

Class I H/W Path Driver S/W State H/W Type Descriptionfc 3 1/10/0/0 fcd CLAIMED INTERFACE HP 2Gb Dual Portfc 4 1/10/0/1 fcd CLAIMED INTERFACE HP 2Gb Dual Port

HP-UX detected the HBA but the drivers are not properly loaded:Class I H/W Path Driver S/W State H/W Type Descriptionfc 0 8.0 fcT1 UNCLAIMED UNKNOWN


6/30


ioscan utility output# ioscan -fnCdisk | moreClass I H/W Path Driver S/W State H/W Type Description======================================================================disk 1 0/0/1/1.15.0 sdisk CLAIMED DEVICE COMPAQBD018122C0

/dev/dsk/c1t15d0 /dev/rdsk/c1t15d0disk 333 0/2/0/0.38.5.255.0.0.1 sdisk CLAIMED DEVICE DECHSG80




/dev/dsk/c99t0d2 /dev/rdsk/c99t0d2


7/30Rev. 6.21 HP Restricted 6

ioscan utility output description(1 of 4)

Class I H/W Path Driver S/W State H/W Type Description

==================================================================disk 333 0/2/0/0.38.5.255.0.0.1 sdisk CLAIMED DEVICE DEC HSG80


Field DescriptionClass Device category such as disk, tape, or printer

I Instance number associated with the device or card



Field Description

H/W path A decimal numerical string of hardware components, notated sequentially fromthe bus address to the deviceHBA path.domain id.port.255.bus.target.lun HBA Path Internal hardware path to the bus converter and HBA Domain ID Domain ID of the switch used to get to this storage Port Port of the switch used to get to this storage 255 Always set to 255 for fabric connected array controller Bus Dependent on addressing mode (PDF, LU, VSA) Target Dependent on addressing mode (PDF, LU, VSA) LUN LUN number of device as seen by HP-UX








Field DescriptionSoftwarestate

The result of software binding

CLAIMED Software bound successfullyUNCLAIMED No associated software foundDIFF_HW Software found does not match the associated software

NO_HW Hardware at this address is no longer responding

ERROR Hardware at this address is responding but is in an error stateSCAN Node locked, try again later







Field DescriptionHardwaretype

Entity identifier for the hardware componentUNKNOWN No hardware associated or the type of hardware is unknown

PROCESSOR Hardware component is a processor MEMORY Hardware component is memoryBUS_NEXUS Hardware component is bus converter or bus adapter

INTERFACE Hardware component is an interface card

DEVICE Hardware component is a device bus type; bus type associatedwith the node

Description Description of the device






HP-UX device naming Block device

/dev/dsk/cxtydz Raw device

/dev/rdsk/cxtydz

cxtydzc = Interface cardx = Instance number of that interfacet = Target address

y = Address valued = Device unitz = Unit number



Windows

connectivity



Windows Device Manager



Windows Disk Manager



LightPulse Utility/NT



OpenVMS

connectivity



Disk and disk path high availability Storage subsystem level components

Redundant HBAs Redundant paths from the HBAs to the storage controllers Storage controllers configured for automatic failover Appropriate RAID levels on the disks

Multipath I/O requires cooperation from the host operatingsystem

Support for multipath I/O can be Active In the event of a path failure, the operating system

reissues the I/O request to another path Passive Only one path is active at one time, but the other

path is ready to take over if the first path fails

OpenVMS supports passive multipath I/O with operator-controlled load balancing



OpenVMS multipath Multipath capability

Is integrated into the operating system Allows failover between device paths

Mount verify invoked when path is switched Failover between controllers takes 1 to 15 seconds Failover between controller ports is instantaneous Multipath set is created when two or more paths to a single

device are discovered

Each path name is constructed from the Fibre Channel portname and the controller port WWID

PGA0.5000-1FE1-0000-9631

or

PGB0.5000-1FE1-0000-9633



OpenVMS multipath discovery When OpenVMS discovers a disk with a valid identifier, it

creates a normal disk UCB When it finds the second path to the same disk, it converts

the unit into a multipath device OpenVMS only uses one active path to a device at a time

When additional paths are discovered, these paths areadded to the multipath device

Disks that have only had one path do not display a SHOWDEVICE/MULTIPATH command



OpenVMS device discovery To search for newly added virtual disks:

$mc sysman io auto/log To initialize and mount a virtual disk:

$init $1$dga1002: test$mount $1$dga1002: test

To display storage devices: show device d

Device naming convention:

$1$DGAidentifier where

D is a disk device G is a Fibre Channel device



Viewing device details in OpenVMS SHOW DEVICE/FULL devname s hows all valid paths to device

$ sho dev/full dga1001

Disk $1$DGA1001: (VMS24), device type HSG80, is online, file-oriented device,shareable, available to cluster, device has multiple I/O paths, errorlogging is enabled.

Error count 0 Operations completed 184Owner process "" Owner UIC [SYSTEM]Owner process ID 00000000 Dev Prot S:RWPL,O:RWPL,G:R,WReference count 0 Default buffer size 512Allocation class 1

I/O paths to device 4Path PGA0.5000-1FE1-000B-B283 (VMS24), primary path, current path.

Error count 0 Operations completed 46Path PGA0.5000-1FE1-000B-B282 (VMS24).

Error count 0 Operations completed 46Path PGB0.5000-1FE1-000B-B281 (VMS24).Error count 0 Operations completed 46

Path PGB0.5000-1FE1-000B-B284 (VMS24).Error count 0 Operations completed 46



Displaying system configuration To display system configuration, issue:

analyze/systemsda> clue config

TR Adapter ADP Host Bus BusArrayEntry Node CSR Vec/IRQ Port Slot Device Name / HW-Id-- ----------- ----------------- ---- ----------------------- ---- ---------------------- ---- ---- ---------------------------1 KA2208 FFFFFFFF.81457840 0 BUSLESS_SYSTEM2 PCI FFFFFFFF.81457C80 1 PCI

FFFFFFFF.814580A0 38 FFFFFFFF.85B6F800 FC PKA: 7 Symbios 895FFFFFFFF.81458110 48 FFFFFFFF.85B72800 40 9 PPB5

3 PCI FFFFFFFF.814584C0 1 PCIFFFFFFFF.814587F8 220 FFFFFFFF.85B76000 DC EIA: 4 DE602-AA i82558 100BaseTXFFFFFFFF.81458830 228 FFFFFFFF.85B78800 D8 EIB: 5 DE602-AA i82558 100BaseTX

4 PCI FFFFFFFF.81458EC0 0 PCI

FFFFFFFF.81459230 28 FFFFFFFF.85B7E800 40 5 MFPCIFFFFFFFF.81459268 30 FFFFFFFF.85BA5000 8C 6 MFPCIFFFFFFFF.814592A0 38 FFFFFFFF.85BB1800 BC GZA: 7 ELSA GLoria Synergy (3Dlabs P2A)FFFFFFFF.814592D8 40 FFFFFFFF.85BB4000 AC FGA: 8 KGPSA-CA (Emulex LP8000)FFFFFFFF.81459310 48 FFFFFFFF.85BB6800 9C FGB: 9 KGPSA-CA (Emulex LP8000)



Tru64

connectivity


24/30


#emxmgr -t emx2emx2 state information:

Link : connection is UPPoint to PointFabric attachedFC DID 0x210413 (tells us the HBA is plugged into switch 1 port 4)Link is SCSI bus 3 (this adapter was assigned scsi bus 3)SCSI target id 7portname is 1000-0000-C921-07C4nodename is 1000-0000-C921-07C4N_Port at FC DID 0x210013 - SCSI tgt id 5 :portname 5000-1FE1-0001-8932 (HBA driver assigned SCSI ID 5 to the bottomright controller port assuming MB)nodename 5000-1FE1-0001-8930Present, Logged in, FCP Target, FCP Logged in,N_Port at FC DID 0xfffffc - SCSI tgt id -1 :portname 20FC-0060-6900-5A1Bnodename 1000-0060-6900-5A1BPresent, Logged in, Directory Server,N_Port at FC DID 0xfffffe - SCSI tgt id -1 :portname 2004-0060-6900-5A1Bnodename 1000-0060-6900-5A1B

Present, Logged in, F_PORT,

emxmgr utility output

d f


25/30


Device discovery for Tru64 UNIX 5.x(1 of 2) Some StorageWorks solutions enable you to specify the

128-bit WWID of the LUN being presented When Tru64 UNIX 5.x boots, it probes the hardware starting

with bus 0, target 0 All devices found are assigned (in order) the next available

disk instance number All instance numbers are maintained in a hardware

database Each virtual disk is assigned a unique HWID

When Tru64 UNIX 5.x starts, any device that no longer hasany valid paths to it are still referenced in the hardwaredatabase

D i di f T 64 UNIX 5


26/30


Device discovery for Tru64 UNIX 5.x(2 of 2) To scan for newly added devices:

# /sbin/hwmgr -scan scsi

Newly discovered disks are assigned the next available diskinstance number

Devices that have been removed (no valid paths) are markedoffline/stale, but their device special files are retained

To create the device special files for new devices:# dsfmgr K

D i i f T 64 UNIX 5


27/30


Device naming for Tru64 UNIX 5.x(1 of 2) Tru64 UNIX 5.x naming convention

Device special files for disks start with dsk x y Device special files for CCLs start with scp x y

where: x is the disk instance y is the partition

Raw and block special device files are put in differentdirectories Block device special files are located in /dev/disk Raw device special files are located in /dev/rdisk

Example/dev/disk/dsk56c

The BTL of the device cannot be determined just by viewing

the device special file

D i i f T 64 UNIX V5


28/30


To determine the BTL of a device, use the hwmgr utility

# hwmgr -show scsi -full -id 62SCSI DEVICE DEVICE DRIVER NUM DEVICE FIRSTHWID: DEVICEID HOSTNAME TYPE SUBTYPE OWNER PATH FILE VALID

PATH-------------------------------------------------------------------------

62: 8 stgaxp12 disk none 2 4 dsk56 [5/0/4]WWID:01000010:6000-1fe1-0003-8610-0009-9471-2165-0687BUS TARGET LUN PATH STATE

--------------------------------------------------4 0 4 valid4 1 4 valid5 0 4 valid5 1 4 valid

The device special file name remains the same even if thedevice BTL is changed

The device is recognized by its 128-bit WWID, not by its BTLlocation

Device naming for Tru64 UNIX V5.x(2 of 2)


29/30

Learning

check


30/30

Documents

12 M9 Operating Systems