P. 1
Brocade Switch 12 M9 Operating Systems

Brocade Switch 12 M9 Operating Systems

|Views: 8|Likes:
Published by sreenathonweb
Brocade Switch 12 M9 Operating Systems
Brocade Switch 12 M9 Operating Systems

More info:

Published by: sreenathonweb on Jun 22, 2013
Copyright:Attribution Non-commercial


Read on Scribd mobile: iPhone, iPad and Android.
download as PPT, PDF, TXT or read online from Scribd
See more
See less





Storage Presentation to Operating Systems

Module 9

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

• Verify device connectivity for:
– HP-UX – Windows – OpenVMS – Tru64

Rev. 6.21

HP Restricted


HP-UX connectivity

Rev. 6.21

HP Restricted


6.ioscan • To search for installed HBAs. issue: # ioscan –f – Available switches • -f • -n • -k • -C • -d — Full output — Show device node information — Scan kernel instead of I/O path — Scan devices in a specific class td — Restrict output to only ‗td‘ devices Rev.21 HP Restricted 3 .

21 HP Restricted 4 . 6.Verifying HBA installation • ioscan -f Class fc fc I 3 4 H/W Path 1/10/0/0 1/10/0/1 Driver fcd fcd S/W State CLAIMED CLAIMED H/W Type INTERFACE INTERFACE Description HP 2Gb Dual Port HP 2Gb Dual Port • HP-UX detected the HBA but the drivers are not properly loaded: Class fc I 0 H/W Path 8.0 Driver fcT1 S/W State UNCLAIMED H/W Type UNKNOWN Description Rev.

38.2 sdisk CLAIMED DEVICE DEC HSG80 /dev/dsk/c95t0d2 /dev/rdsk/c95t0d2 disk 367 0/2/0/0.1 sdisk CLAIMED DEVICE DEC HSG80 /dev/dsk/c99t0d1 /dev/rdsk/c99t0d1 disk 368 0/2/0/ 6.ioscan utility output # ioscan -fnCdisk | more Class I H/W Path Driver S/W State H/W Type Description ====================================================================== disk 1 0/0/1/ sdisk CLAIMED DEVICE DEC HSG80 /dev/dsk/c95t0d1 /dev/rdsk/c95t0d1 disk 334 0/2/0/ sdisk CLAIMED DEVICE COMPAQ BD018122C0 /dev/dsk/c1t15d0 /dev/rdsk/c1t15d0 disk 333 0/2/0/ HP Restricted 5 .2 sdisk CLAIMED DEVICE DEC HSG80 /dev/dsk/c99t0d2 /dev/rdsk/c99t0d2 Rev.

21 HP Restricted 6 .5.0.1 sdisk DEVICE /dev/dsk/c95t0d1 /dev/rdsk/c95t0d1 Field Class I Description Device category such as disk. or printer Instance number associated with the device or card Rev.ioscan utility output description (1 of 4) Class disk I H/W Path Driver S/W State H/W Type CLAIMED Description DEC HSG80 ================================================================== 333 0/2/0/0.255. tape. 6.38.0.

ioscan utility output description (2 of 4) Class I H/W Path Driver S/W State H/W Type Description ================================================================== disk 333 0/2/0/0.255.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.domain id.255. LU.target. VSA) Target –Dependent on addressing mode (PDF.port.0.0.21 HP Restricted 7 . notated sequentially from the bus address to the device HBA path.38.1 sdisk CLAIMED /dev/dsk/c95t0d1 /dev/rdsk/c95t0d1 DEVICE DEC HSG80 Field H/W path Description A decimal numerical string of hardware components.bus.5. VSA) LUN – LUN number of device as seen by HP-UX Rev. 6. LU.

255.ioscan utility output description (3 of 4) Class I H/W Path Driver S/W State H/W Type Description ================================================================== disk 333 0/2/0/0. try again later Rev.0.0.1 sdisk CLAIMED /dev/dsk/c95t0d1 /dev/rdsk/c95t0d1 DEVICE DEC HSG80 Field Software state Description The result of software binding       CLAIMED – Software bound successfully UNCLAIMED – No associated software found DIFF_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 state SCAN – Node locked. 6.21 HP Restricted 8 .5.38.

38. 6.255.1 sdisk CLAIMED /dev/dsk/c95t0d1 /dev/rdsk/c95t0d1 DEVICE DEC HSG80 Field Hardware type Description Entity identifier for the hardware component  UNKNOWN – No hardware associated or the type of hardware is unknown      PROCESSOR – Hardware component is a processor MEMORY – Hardware component is memory BUS_NEXUS – Hardware component is bus converter or bus adapter INTERFACE – Hardware component is an interface card DEVICE – Hardware component is a device bus type.5. bus type associated with the node Description Description of the device Rev.0.21 HP Restricted 9 .ioscan utility output description (4 of 4) Class I H/W Path Driver S/W State H/W Type Description ================================================================== disk 333 0/2/0/0.0.

21 HP Restricted 10 .HP-UX device naming • Block device /dev/dsk/cxtydz • Raw device /dev/rdsk/cxtydz • cxtydz c = Interface card x = Instance number of that interface t = Target address y = Address value d = Device unit z = Unit number Rev. 6.

Windows connectivity Rev. 6.21 HP Restricted 11 .

21 HP Restricted 12 .Windows Device Manager Rev. 6.

21 HP Restricted 13 .Windows Disk Manager Rev. 6.

LightPulse Utility/NT Rev. 6.21 HP Restricted 14 .

OpenVMS connectivity Rev. 6.21 HP Restricted 15 .

but the other path is ready to take over if the first path fails • OpenVMS supports passive multipath I/O with operatorcontrolled load balancing Rev. the operating system reissues the I/O request to another path – Passive — Only one path is active at one time.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 operating system • Support for multipath I/O can be – Active — In the event of a path failure. 6.21 HP Restricted 16 .

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 port name and the controller port WWID PGA0. 6.5000-1FE1-0000-9631 or PGB0.21 HP Restricted 17 .5000-1FE1-0000-9633 Rev.

21 HP Restricted 18 . 6.OpenVMS multipath discovery • When OpenVMS discovers a disk with a valid identifier. 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 are added to the multipath device • Disks that have only had one path do not display a SHOW DEVICE/MULTIPATH command Rev. it creates a normal disk UCB • When it finds the second path to the same disk.

21 HP Restricted 19 .OpenVMS device discovery • To search for newly added virtual disks: $mc sysman io auto/log • To initialize and mount a virtual disk: $init $mount $1$dga1002: $1$dga1002: test 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 Rev. 6.

file-oriented device.O:RWPL. device type HSG80. error logging is enabled.5000-1FE1-000B-B283 Error count Path PGA0. 0 Operations completed 46 46 46 46 Rev. current path. 0 Operations completed (VMS24).21 HP Restricted 20 . primary path. 6.W Default buffer size 512 I/O paths to device Path PGA0. Error count Owner process Owner process ID Reference count Allocation class 0 "" 00000000 0 1 Operations completed 184 Owner UIC [SYSTEM] Dev Prot S:RWPL. 0 Operations completed (VMS24). shareable. 0 Operations completed (VMS24).5000-1FE1-000B-B284 Error count 4 (VMS24).5000-1FE1-000B-B282 Error count Path PGB0.5000-1FE1-000B-B281 Error count Path PGB0.Viewing device details in OpenVMS • SHOW DEVICE/FULL devname shows all valid paths to device $ sho dev/full dga1001 Disk $1$DGA1001: (VMS24). is online. device has multiple I/O paths. available to cluster.G:R.

81457C80 1 PCI FFFFFFFF.85B7E800 40 5 MFPCI FFFFFFFF.81458110 48 FFFFFFFF.814580A0 38 FFFFFFFF.85BB1800 BC GZA: 7 ELSA GLoria Synergy (3Dlabs P2A) FFFFFFFF.81457840 0 BUSLESS_SYSTEM 2 PCI FFFFFFFF.85B78800 D8 EIB: 5 DE602-AA i82558 100BaseTX 4 PCI FFFFFFFF.81458830 228 FFFFFFFF.---------------------.85BB4000 AC FGA: 8 KGPSA-CA (Emulex LP8000) FFFFFFFF.81459230 28 FFFFFFFF.85B6F800 FC PKA: 7 Symbios 895 FFFFFFFF.---.---.---.814592D8 40 FFFFFFFF.21 HP Restricted 21 .814587F8 220 FFFFFFFF.----------.814584C0 1 PCI FFFFFFFF.85B76000 DC EIA: 4 DE602-AA i82558 100BaseTX FFFFFFFF.----------------------.--------------------------1 KA2208 FFFFFFFF. 6.85BA5000 8C 6 MFPCI FFFFFFFF.---.----------------.85B72800 40 9 PPB5 3 PCI FFFFFFFF. issue: analyze/system sda> clue config TR Adapter ADP Host Bus BusArrayEntry Node CSR Vec/IRQ Port Slot Device Name / HW-Id -.85BB6800 9C FGB: 9 KGPSA-CA (Emulex LP8000) Rev.Displaying system configuration • To display system configuration.814592A0 38 FFFFFFFF.81459268 30 FFFFFFFF.81459310 48 FFFFFFFF.81458EC0 0 PCI FFFFFFFF.

Tru64 connectivity Rev.21 HP Restricted 22 . 6.

21 HP Restricted 23 . 6. Logged in. N_Port at FC DID 0xfffffe . F_PORT. FCP Target. Logged in. Rev. FCP Logged in. Logged in.emxmgr utility output #emxmgr -t emx2 emx2 state information: Link : connection is UP Point to Point Fabric attached FC 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 7 portname is 1000-0000-C921-07C4 nodename is 1000-0000-C921-07C4 N_Port at FC DID 0x210013 . Directory Server.SCSI tgt id 5 : portname 5000-1FE1-0001-8932 (HBA driver assigned SCSI ID 5 to the bottom right controller port – assuming MB) nodename 5000-1FE1-0001-8930 Present. N_Port at FC DID 0xfffffc .SCSI tgt id -1 : portname 20FC-0060-6900-5A1B nodename 1000-0060-6900-5A1B Present.SCSI tgt id -1 : portname 2004-0060-6900-5A1B nodename 1000-0060-6900-5A1B Present.

Device discovery for Tru64 UNIX 5.x boots. 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. any device that no longer has any valid paths to it are still referenced in the hardware database Rev.21 HP Restricted 25 .x (1 of 2) • Some StorageWorks solutions enable you to specify the 128-bit WWID of the LUN being presented • When Tru64 UNIX 5. 6. it probes the hardware starting with bus 0.x starts.

6.Device discovery for Tru64 UNIX 5. but their device special files are retained • To create the device special files for new devices: # dsfmgr –K Rev.x (2 of 2) • To scan for newly added devices: # /sbin/hwmgr -scan scsi – Newly discovered disks are assigned the next available disk instance number – Devices that have been removed (no valid paths) are marked offline/stale.21 HP Restricted 26 .

x (1 of 2) • Tru64 UNIX 5. 6.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 different directories – 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 Rev.21 HP Restricted 27 .Device naming for Tru64 UNIX 5.

21 HP Restricted 28 . use the hwmgr utility # hwmgr -show scsi -full -id 62 SCSI DEVICE DEVICE DRIVER NUM DEVICE FIRST HWID: 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-0687 BUS TARGET LUN PATH STATE -------------------------------------------------4 0 4 valid 4 1 4 valid 5 0 4 valid 5 1 4 valid • The device special file name remains the same even if the device BTL is changed – The device is recognized by its 128-bit WWID.Device naming for Tru64 UNIX V5. not by its BTL location Rev.x (2 of 2) • To determine the BTL of a device. 6.

Learning check .

Rev.21 HP Restricted 31 . 6.

You're Reading a Free Preview

/*********** DO NOT ALTER ANYTHING BELOW THIS LINE ! ************/ var s_code=s.t();if(s_code)document.write(s_code)//-->