If you use an LSI, maybe you install the LSI Logic MPT Configuration
Utility.
Example of the usage :
lsiutil
LSI Logic MPT Configuration Utility, Version 1.61, September 18, 2008
1 MPT Port found
Port Name Chip Vendor/Type/Rev MPT Rev Firmware Rev IOC
1. mpt0 LSI Logic SAS1068E B3 105 011a0000 0
Select a device: [1-1 or 0 to quit] 1
1. Identify firmware, BIOS, and/or FCode
2. Download firmware (update the FLASH)
4. Download/erase BIOS and/or FCode (update the FLASH)
8. Scan for devices
10. Change IOC settings (interrupt coalescing)
13. Change SAS IO Unit settings
16. Display attached devices
20. Diagnostics
21. RAID actions
22. Reset bus
23. Reset target
42. Display operating system names for devices
45. Concatenate SAS firmware and NVDATA files
59. Dump PCI config space
60. Show non-default settings
61. Restore default settings
66. Show SAS discovery errors
69. Show board manufacturing information
97. Reset SAS link, HARD RESET
98. Reset SAS link
99. Reset port
e Enable expert mode in menus
p Enable paged mode
w Enable logging
Main menu, select an option: [1-99 or e/p/w or 0 to quit] 16
SAS1068E's links are down, down, down, down, 3.0 G, 3.0 G, 3.0 G, 3.0 G
B___T SASAddress PhyNum Handle Parent Type
500605b000eea990 0001 SAS Initiator
500605b000eea991 0002 SAS Initiator
500605b000eea992 0003 SAS Initiator
500605b000eea993 0004 SAS Initiator
500605b000eea994 0005 SAS Initiator
500605b000eea995 0006 SAS Initiator
500605b000eea996 0007 SAS Initiator
500605b000eea997 0008 SAS Initiator
50030480003d95ff 4 0009 0005 Edge Expander
0 10 50030480003d95c4 4 000a 0009 SATA Target
0 11 50030480003d95c5 5 000b 0009 SATA Target
0 12 50030480003d95c6 6 000c 0009 SATA Target
0 13 50030480003d95c7 7 000d 0009 SATA Target
0 14 50030480003d95c8 8 000e 0009 SATA Target
0 15 50030480003d95c9 9 000f 0009 SATA Target
0 17 50030480003d95ca 10 0010 0009 SATA Target
0 16 50030480003d95cb 11 0011 0009 SATA Target
0 18 50030480003d95cc 12 0012 0009 SATA Target
0 19 50030480003d95cd 13 0013 0009 SATA Target
0 20 50030480003d95ce 14 0014 0009 SATA Target
0 21 50030480003d95cf 15 0015 0009 SATA Target
0 22 50030480003d95d0 16 0016 0009 SATA Target
0 23 50030480003d95d1 17 0017 0009 SATA Target
0 24 50030480003d95d2 18 0018 0009 SATA Target
0 25 50030480003d95d3 19 0019 0009 SATA Target
0 26 50030480003d95d6 22 001a 0009 SATA Target
0 8 50030480003d95fd 36 001b 0009 SAS Initiator and Target
The colum PhyNum , im my case points out to the drive disk slot in the
JBOD chassis.
However i don't know how this works with multipath.
The ideal solution would be to use the cfgadm with the hardware option,
to put the disk led blinking.
Something like, as seen in
http://docs.sun.com/app/docs/doc/816-5166/cfgadm-scsi-1m?a=view :
Example 6 Display the Value of the Locator for a Disk
The following command displays the value of the locator for a disk. This
example is specific to the SPARC Enterprise Server family:
# *cfgadm -x locator c0::dsk/c0t6d0*
The system responds with the following:
Disk Led
c0t6d0 locator=on
But maybe this option is just for SPARC with SCSI?
Bruno
SHOUJIN WANG wrote:
Hi there,
What I am tring to do is: Build a NAS storage server based on the following
hardware architecture:
Server-->SAS HBA--->SAS JBOD
I plugin 2 SAS HBA cards into a X86 box, I also have 2 SAS I/O Modules on SAS JBOD. From each HBA card, I have one SAS cable which connects to SAS JBOD.
Configured MPT successfully on server, I can see the single multipahted disks likes the following:
r...@super01:~# format
Searching for disks...done
AVAILABLE DISK SELECTIONS:
0. c0t5000C5000D34BEDFd0 <SEAGATE-ST31000640SS-0001-931.51GB>
/scsi_vhci/d...@g5000c5000d34bedf
1. c0t5000C5000D34BF37d0 <SEAGATE-ST31000640SS-0001-931.51GB>
/scsi_vhci/d...@g5000c5000d34bf37
2. c0t5000C5000D34C727d0 <SEAGATE-ST31000640SS-0001-931.51GB>
/scsi_vhci/d...@g5000c5000d34c727
3. c0t5000C5000D34D0C7d0 <SEAGATE-ST31000640SS-0001-931.51GB>
/scsi_vhci/d...@g5000c5000d34d0c7
4. c0t5000C5000D34D85Bd0 <SEAGATE-ST31000640SS-0001-931.51GB>
/scsi_vhci/d...@g5000c5000d34d85b
The problem is: if one of disks failed, I don't know how to locate the disk in
chasiss. It is diffcult for failed disk replacement.
Is there any utility in opensoalris which can be used to locate/blink the
failed disk(or do we have any michanism to implement the SES command in bond of
SAS)? Or do we have a tool to map the multipathing device ID to the original
single pathing device ID likes the following?
c0t5000C5000D34BF37d0
|----c2t0d0
\----c3t0d0
Regards,
Autumn Wang.
--
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.
_______________________________________________
zfs-discuss mailing list
zfs-discuss@opensolaris.org
http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
