You are on page 1of 9

Sun System Handbook - ISO 2.2.

0 January 2009 Internal/Partner


Edition
Home | Current Systems | EOL Systems | Components | General Info | Search |
Feedback
Asset ID: 1-61-214679-1
Update Date: Mon Nov 24 00:00:00 MST 2008
Keywords:
Solution Type Technical Instruction

Solution 214679 : Sun StorEdge[TM] A3x00/A1000: Locating drives for a specific


LUN(and other example commands) using the RM6 Command Line

Related Categories

• Home>Product>Storage>Storage
Management Software

Description
This document will help find the drives constituting a LUN(Logical Unit), using
the command line interface of RAID Manager 6(RM6) software.

This applies to the following arrays:-


Sun StorEdge[TM] A1000,
Sun StorEdge[TM] A3000,
Sun StorEdge[TM] A3500 and
Sun StorEdge[TM] A3500FC

Also, this document lists various other utilities that RAID manager offers,
their syntax and usage.

Steps to Follow
Finding on which physical drives a LUN resides, using a command line, is
necessary when upgrading drives, replacing drives, and for diagrams/labeling
purposes when the RM6 GUI is not available. Use the following procedure:

1. Type "healthck -a"


-This provides the RAID module name - write it down
2. Type "lad" (This command is explained later in the section)
3. Type "format"
4. Compare the c#t#d# from the format command output, and lad output - they
should be the same
The d# in format, should match with the corresponding LUN number in the
associated lad c#t# (d# = LUN number for that controller)
NOTE: All the c#t#d# you see in format output, represent LUNs. A LUN could
span several physical disks.
NOTE: If lad and format outputs don't match, there could be a
configuration
problem.
5. Type "drivutil -l <raid_module_name>" (get module name from step 1)
-This will list the Groups and the LUNs
-Write down the Group Number and the LUN Number associated with it
EXAMPLE OUTPUT:
LUN Group Device RAID Capacity Status
Name Level (MB)
0 1 c8t5d0 5 68778 Optimal
1 2 c9t4d1 5 68778 Optimal
Write Down:
Group 1 is made up of LUN 0
Group 2 is made up of LUN 1
6. Type "drivutil -d <raid_module_name>" (get module name from step 1)
-This will list the drives in each Group
EXAMPLE OUTPUT:
Drives in Group for Bigfoot-FC
Group Drive List [Channel,Id]
Unassigned [3,4];
Hot Spare [2,4];
Group 1: [1,0]; [2,0]; [4,0]; [1,3]; [2,3]; [3,3]; [4,3]; [1,4];
Group 2: [3,0]; [1,1]; [2,1]; [3,1]; [4,1]; [1,2]; [2,2]; [3,2];
THE PHYSICAL DRIVE LOCATIONS FOR THE LUN, CAN NOW BE IDENTIFIED
EXAMPLE:
In step 5, it can be seen that Group 1 is associated with LUN 0. Then,
Step 6 shows that Group 1(LUN 0) contains the drives [1,0]; [2,0]; [4,0];
[1,3]; [2,3]; [3,3]; [4,3]; [1,4]. These are the physical drive locations
for LUN 0.
[1,0] -> 1 corresponds to the tray id, and 0 corresponds to the drive id
within that tray.

ADDITIONAL INFORMATION FOR


LOCATING DRIVES BY SERIAL
NUMBER
1. Type "drivutil -i <raid_module_name>" (get module name from step 1)

Example:
Loc Capacity Status Vendor Product Firmware Serial #
[1,0] 8637 Optimal SEAGATE ST39102LCSUN9.0G 6329 LJM0693600
[2,0] 8637 Optimal SEAGATE ST39102LCSUN9.0G 6329 LJM0094700
[4,0] 8637 Optimal SEAGATE ST39102LCSUN9.0G 6329 LJK7471600
[1,1] 8637 Optimal SEAGATE ST39102LCSUN9.0G 6329 LJM1458200
[2,1] 8637 Optimal SEAGATE ST39102LCSUN9.0G 6329 LJM0411500
[3,1] 8637 Optimal SEAGATE ST39102LCSUN9.0G 6329 LJM1268800

2. Write down the locations and Serial Numbers

[1,0] LJM0693600
[2,0] LJM0094700
[4,0] LJK7471600
[1,1] LJM1458200
[2,1] LJM0411500
[3,1] LJM1268800

3. Drop the first and last 2 digits

Example Serial # - LJM0693600


^^ ^^
|| ||
***Drop these 4 digits
4. The serial number with the 4 digits removed(for example M06936), is the
last
6 digits of the serial number located on the disk drive label.

The following section, will cover all the RM6


commands, and give examples.
To list all rm6 commands:
# cd /usr/sbin/osa
# ls
drivutil healthck logutil parityck rdacutil storutil
fwutil lad nvutil raidutil rm6

RM6 Commands

Contents
--------

1. Show how many drives(LUNs) are currently available:


2. Display the available RAID modules(aka hardware raid arrays):
3. Display the controller numbers of the RAID modules by name:
4. Display information about a specific RAID module, such as how many
5. Display a list of LUNs and their status in a specific RAID module:
6. Display which drives belong to which drive groups
7. Verify the status of two different luns (0 and then 31)
8. Display drive group information:
9. Display a list of the luns, their size and firmware info in a raid module:
10. Verify that the controllers have the proper nvsram settings:
11. Display information about the drives in a raid module:
12. Display firmware information about a RAID module:
13. Display the battery age:
14. Delete an existing lun:
15. Confirm your previous step:
16. Create a 1000m raid 5 LUN using specific drives:
17. Verify your previous step:
18. Create a mirrored lun with similar capabilities:
18. Create a mirrored lun with similar capabilities:
19. Create a RAID 3 LUN:
20. Create a simple LUN (RAID 0):
21. Perform a health check of all enclosures:
22. Perform a health check of a specific enclosure:

1. To show how many drives (LUNs) are currently available:


# format
Searching for disks...done
c1t5d0: configured with capacity of 6.00MB
AVAILABLE DISK SELECTIONS:
0. c0t0d0 <SUN18G cyl 7506 alt 2 hd 19 sec 248>
/pci@1f,4000/scsi@3/sd@0,0
1. c1t5d0 <Symbios-StorEdgeA3500FCd-0003 cyl 3 alt 2 hd 64 sec 64>
/pseudo/rdnexus@1/rdriver@5,0
2. c3t5d0 <Symbios-StorEDGEA1000-0003 cyl 3 alt 2 hd 64 sec 64>
/pseudo/rdnexus@3/rdriver@5,0
3. c3t5d1 <Symbios-StorEDGEA1000-0003 cyl 48 alt 2 hd 64 sec 64>
/pseudo/rdnexus@3/rdriver@5,1
Specify disk (enter its number): ^D
Note: The LUNs will identify themselves as A3500FC or A1000
2. To display the available RAID modules(aka hardware RAID arrays):
# ./lad
c1t5d0 1T03701713 LUNS: 0 <- first controller of the a3500fc
c2t4d0 1T03701636 LUNS: <- second controller of the a3500fc
c3t5d0 1T81006267 LUNS: 0 1 <- controller of the a1000
Note: The 0 and 1 next to each controller, indicates that the A1000
sees two LUNs, and the first controller of the 3500FC has one.
After creating another LUN, you would see the following:
# ./lad
c1t5d0 1T03701713 LUNS: 0
c2t4d0 1T03701636 LUNS:
c3t5d0 1T81006267 LUNS: 0 1 2 <- notice that a new lun appears here now
3. To display the controller numbers of the RAID modules by name:
# ./storutil -c ultra60_A1000 -d (one controller only)
ultra60_A1000:
Controller A: 1T81006267 ( c3t5d0 )
Independent Controller Configuration: OFF
# ./storutil -c ultra60_A3500FC -d (two controllers in a 3500fc)
ultra60_A3500FC:
Controller A: 1T03701713 ( c1t5d0 )
Controller B: 1T03701636 ( c2t4d0 )
Independent Controller Configuration: OFF
4. To display information about a specific RAID module, such as how many
controllers:
# ./rdacutil -i ultra60_A1000
ultra60_A1000: single-controller
Active controller a (c3t5d0) units: 0 1
./rdacutil succeeded!
5. To display a list of LUNs and their status in a specific RAID module:
# ./drivutil -l ultra60_A1000
Logical Unit Information for ultra60_A1000
LUN Group Device RAID Capacity Status
Name Level (MB)
0 1 c3t5d0 0 10 Optimal
1 2 c3t5d1 1 100 Optimal
drivutil succeeded!
6. To display which drives belong to which drive groups
# ./drivutil -d ultra60_A1000
Drives in Group for ultra60_A1000
Group Drive List [Channel,Id]
Unassigned [1,3]; [2,3]; [1,4]; [2,4]; [1,5]; [2,5];
Group 1: [1,0]; [2,0];
Group 2: [1,1]; [2,1];
Group 3: [1,2]; [2,2];
drivutil succeeded!
7. To verify the status of two different luns (0 and then 31)
# ./drivutil -p 0 c3t5d0
ultra60_A1000 unit 0: optimal
drivutil succeeded!
# ./drivutil -p 31 c3t5d0
ultra60_A1000 unit 31: does not exist
drivutil succeeded!
Note: This is what you would see if you chose an invalid one
8. To display drive group information:
# ./drivutil -I c3t5d0
Group Information for ultra60_A1000
Group No. of RAID No. of Total Remaining
LUNs Level Drives Space(MB) Space(MB)
Unassigned 0 - 6 24564 -
1 1 0 2 8108 8098
2 1 1 2 4054 3954
3 1 1 2 4054 0
drivutil succeeded!
9. To display a list of the luns, their size and firmware info in a RAID
module:
# ./raidutil -c c3t5d0 -i
LUNs found on c3t5d0.
LUN 0 RAID 0 10 MB
LUN 1 RAID 1 100 MB
Vendor ID Symbios
ProductID StorEDGE A1000
Product Revision 0003
Boot Level 03.01.04.00
Boot Level Date 04/05/01
Firmware Level 03.01.04.75
Firmware Date 04/11/02
raidutil succeeded!
10. To verify that the controllers have the proper nvsram settings:
# ./nvutil -v
The NVSRAM settings of controller c1t5d0(1T03701713) are correct.
The NVSRAM settings of controller c2t4d0(1T03701636) are correct.
The NVSRAM settings of controller c3t5d0(1T81006267) are correct.
nvutil command succeeded.
11. To display information about the drives in a RAID module:
# ./drivutil -i c3t5d0
Drive Information for ultra60_A1000
Location Capacity Status Vendor Product Firmware
Serial (MB) ID Version
Number
[1,0] 4094 Optimal SEAGATE ST34501WCSUN4.2G 0558
LG551899
[2,0] 4094 Optimal SEAGATE ST34501WCSUN4.2G 0558
LG551587
[1,1] 4094 Optimal SEAGATE ST34501WCSUN4.2G 0558
LG551974
[2,1] 4094 Optimal SEAGATE ST34501WCSUN4.2G 0558
LG548431
[1,2] 4094 Optimal SEAGATE ST34501WCSUN4.2G 0558
LG549790
[2,2] 4094 Optimal SEAGATE ST34501WCSUN4.2G 0558
LG551944
[1,3] 4094 Optimal SEAGATE ST34501WCSUN4.2G 0558
LG551869
[2,3] 4094 Optimal SEAGATE ST34501WCSUN4.2G 0558
LG551591
[1,4] 4094 Optimal SEAGATE ST34501WCSUN4.2G 0558
LG548929
[2,4] 4094 Optimal SEAGATE ST34501WCSUN4.2G 0558
LG548750
[1,5] 4094 Optimal SEAGATE ST34501WCSUN4.2G 0558
LG552389
[2,5] 4094 Optimal SEAGATE ST34501WCSUN4.2G 0558
LG551966
drivutil succeeded!
12. To display firmware information about a RAID module:
# ./fwutil -v c3t5d0
The controller firmware version for controller c3t5d0 (module:
ultra60_A1000) is 3.01.04. The recommended firmware version for this
application is 3.00.00 or higher.
fwutil succeeded!
13. To display the battery age:
# ./raidutil -c c3t5d0 -B
LUNs found on c3t5d0.
LUN 0 RAID 0 10 MB
LUN 1 RAID 1 100 MB
LUN 2 RAID 1 4054 MB
Battery age is between 360 days and 450 days.
raidutil succeeded!
14. To delete an existing LUN:
# ./raidutil -c c3t5d0 -D 2
LUNs found on c3t5d0.
LUN 0 RAID 0 10 MB
LUN 1 RAID 1 100 MB
LUN 2 RAID 1 4054 MB
Deleting LUN 2.
Press Control C to abort.
LUNs successfully deleted
raidutil succeeded!
15. To confirm your previous step:
# ./raidutil -c c3t5d0 -B
LUNs found on c3t5d0.
LUN 0 RAID 0 10 MB
LUN 1 RAID 1 100 MB
Battery age is between 360 days and 450 days.
raidutil succeeded!
16. To create a 1000m raid 5 LUN using specific drives:
# ./raidutil -c c3t5d0 -n 3 -l 5 -s 1000 -g 24,25,14,15
LUNs found on c3t5d0.
LUN 0 RAID 0 10 MB
Capacity available in drive group: 24909504 blocks (12162 MB).
Creating LUN 3
Registering new logical unit 3 with system.
Formatting logical unit 3 RAID 5 1000 MB
LUNs found on c3t5d0.
LUN 0 RAID 0 10 MB
LUN 3 RAID 5 1000 MB
LUNs successfully created
raidutil succeeded!
Note: -s indicates size (always in MB), -l indicates RAID level, -n
indicates LUN number
17. To verify your previous step:
# ./raidutil -c c3t5d0 -B
LUNs found on c3t5d0.
LUN 0 RAID 0 10 MB
LUN 3 RAID 5 1000 MB
Battery age is between 360 days and 450 days. <- disregard for this
example
raidutil succeeded!
18. To create a mirrored LUN with similar capabilities:
# ./raidutil -c c3t5d0 -n 4 -l 1 -s 1000 -g 24,25,14,15
LUNs found on c3t5d0.
LUN 0 RAID 0 10 MB
Capacity available in drive group: 16606208 blocks (8108 MB).
Creating LUN 4
Registering new logical unit 4 with system.
Formatting logical unit 4 RAID 1 1000 MB
LUNs found on c3t5d0.
LUN 0 RAID 0 10 MB
LUN 4 RAID 1 1000 MB
LUNs successfully created
raidutil succeeded!
19. To create a raid 3 lun:
# ./raidutil -c c3t5d0 -n 4 -l 3 -s 1000 -g 24,25,14,15
LUNs found on c3t5d0.
LUN 0 RAID 0 10 MB
Capacity available in drive group: 24909312 blocks (12162 MB).
Creating LUN 4
Registering new logical unit 4 with system.
Formatting logical unit 4 RAID 3 1000 MB
LUNs found on c3t5d0.
LUN 0 RAID 0 10 MB
LUN 4 RAID 3 1000 MB
LUNs successfully created
raidutil succeeded!
20. To create a simple lun (raid 0):
# ./raidutil -c c3t5d0 -n 4 -l 0 -s 1000 -g 24,25,14,15
LUNs found on c3t5d0.
LUN 0 RAID 0 10 MB
Capacity available in drive group: 33212416 blocks (16217 MB).
Creating LUN 4
Registering new logical unit 4 with system.
Formatting logical unit 4 RAID 0 1000 MB
LUNs found on c3t5d0.
LUN 0 RAID 0 10 MB
LUN 4 RAID 0 1000 MB
21. To perform a health check of all enclosures:
# ./healthck -a
Health Check Summary Information
ultra60_A3500FC: Optimal
ultra60_A1000: Optimal
healthck succeeded!
22. To perform a health check of a specific enclosure:
# ./healthck ultra60_A1000
Health Check Summary Information
ultra60_A1000: Optimal
healthck succeeded!

Internal Comments
NOTE: If lad and format outputs don't match, there could be a configuration problem, so refer to
Technical Instruction:

< Solution: 202094 > (RM6 - Editing the /usr/lib/osa/rdac_address file to get
lad and format matched) to correct this problem.

Product
Sun StorageTek A3500 FC Array
Sun StorageTek A3500 Array
Sun StorageTek A3000
Sun StorEdge A1000 Array
Netra st A1000 Array

Keywords
RM, RM6, RM6.22, Raid Manager, LUN, drives, drive, location, map

Previously Published As
70235

Change History
Date: 2005-05-31
User Name: 71396
Action: Approved
Comment: See history.
Version: 10

Date: 2005-05-31
User Name: 71396
Action: Reassign
Comment: Made error, unpublished the wrong document. Republishing this one, and deleting the
incorrect one.
Version: 0

Attachments
This solution has no attachment
Copyright 1994-2009 Sun Microsystems, Inc. All rights reserved.
Legal Terms Privacy Policy Feedback

You might also like