Sun System Handbook - ISO 3.4 June 2011 Internal/Partner Edition | |||
|
|
Solution Type Technical Instruction Sure Solution 1004634.1 : Using the Command Line Interface for the Sun StorEdge SRC/P Intelligent SCSI RAID Controller[TM] (dptmgr)
PreviouslyPublishedAs 206427 Description Using the Command Line Interface for the Sun StorEdge SRC/P Intelligent SCSI RAID Controller[TM] (dptmgr) Steps to Follow Command Line Examples ------------------------------------------------------------------------ Unlike Sun's other hardware raid products, there is only 1 command that comes with SRC/P, /opt/SUNWhwrdg/dptutil. Use this command to check the status of the logical storage units, or build new "LSU's". The following examples show how to build a variety of arrays and check on their status. Example 1: This command example creates a RAID 0 stripe across two drives. In this particular case, -l identifies a raid level of 0 and -g identifies which disks are to be used. Notice that drive names do not include the slice value and are separated by commas. Note: Do not separate drive names with spaces. # dptutil -l 0 -g c2t0d0,c2t1d0 Example 2: This command example creates a RAID 0 stripe across five drives. Once again, the -l parameter identifies a raid level of 0 while -g identifies the drive selection. Additionally, -s creates a 100MB Logical Storage Unit while -z identifies the stripe segment size of 128k. Note: Use caution with the -s option. A drive can only be used once with SRC/P. If a 9GB drive is selected and the -s option is used to build a 1GB raid, the remaining 8GB cannot be used. # dptutil -l 0 -s 100 -z 128 -g c2t0d0,c2t1d0,c2t2d0,c3t0d0,c3t1d0 Example 3: This command example creates a raid 5 device. What is different from the previous example is the -r option. This tells dptmgr to build the LSU as fast as possible. This will slow down any other I/O through the raid card such as system activity to another LSU behind the card. The options for -r are slow, medslow, med, medfast, fast or 0-9 where 9 is the highest construction rate. # dptutil -l 5 -s 200 -z 128 -g c2t0d0,c2t1d0,c2t2d0,c3t0d0 -r fast Example 4: This command example creates a mirror of 4 drives. Previously discussed modifiers -g, -r -l and -s are used. Note that -z would be an illegal option as we cannot stripe a mirror. Notice the -d option. This identifies which SRC/P controller card to use. SRC/P identifies each card on the system with a 'd' value. Typically, they are numbered 0, 1, 2, etc. Identification of the 'd' value is discussed later with the 'dptutil -L all' command. # dptutil -d 0 -l 1 -s 200 -g c2t1d0,c2t2d0,c3t0d0,c3t1d0 -r medfast Example 5: This command example creates the same mirror just created. However, it introduces the new option +. This allows grouping the drives prior to creating the LSU. In this case, + allows grouping drives across controllers to get the best RAID 1 performance possible. # dptutil -d 0 -l 1 -s 200 -g c2t1d0+c3t1d0,c2t0d0+c3t0d0 -r 2 Example 6: This command example is a trick! It appears to create a 3GB raid 0 of 4 drives with a stripe segment of 8k. However, this command will actually create a Raid5 of 4 drives with a stripe segment of 32k. This is because the -l, -s and -w options must precede the -g modifier. Otherwise they are ignored and the defaults are used. # dptutil -g c2t1d0,c3t1d0,c2t0d0,c3t0d0 -l 0 -s 3000 -w 8 -r 5 Example 7: This command example creates a hot spare drive. Two new modifiers are used. The -c option identifies the SRC/P card to use. It provides the same function as the -d option in the previous example. This option would be used if multiple cards were present. c2 is the controller value originally assigned to the drives behind this card. The -c option can be used in any dptutil command. Obviously, -h identifies the drive to be a hot spare. # dptutil -c c2 -h c3t1d0 Example 8: This command example is just the converse of the previous. It removes the hot spare drive created. Note that hot spares are not assigned to LSU's. They will deploy to any redundant LSU behind the SRC/P card. # dptutil -c c2 -H c3t1d0 We've seen how to create an LSU, now lets delete them. The -D option is used to delete an LSU. However, it is kind of tricky to figure out what to delete. An easy thing to do is to pass the -D option the 'all' modifier. This gets rid of everything behind the card. To delete a specific LSU, pass it the LSU identifier value. These values start at 0 and increment. There is no way to correlate an LSU to its respective logical identifier value. If only one LSU needs to be deleted behind an SRC/P card, it should be done from the GUI. Example 9: This command example shows how to delete all LSU's # dptutil -d 0 -D all or just one LSU # dptutil -d 0 -D 1 Like most hardware raid, SRC/P has a cache buffer within the card. Write caching is a function of the disk drive, not the LSU. Device names specified will affect the drives only. The 'on' option will cache date prior to writing to disk while the 'off' option will pass data straight through. The doc refers to these options as 'write back' and 'write thru'. Example 10: This command example turns on caching for 2 drives. # dptutil -w on c2t2d0,c2t0d0 The dptutil command can also be used to monitor and diagnose problems with SRC/P. The command: # dptutil -L all tells everything. It is the equivalent of metastat or vxprint -ht. There are other options to the -L modifier, but they filter the data returned. The amount of information returned is not so great that it needs be removed. Avoid options such as controller, logical, physical, raid, spare, and speed. There are several other options to dptutil. The man page discusses them briefly. -a allows an audible alarm to sound in the event of a raid event. -I displays controller information. Most of this we already have with -L . -F can be used to flash update controller firmware. -X will reset the controller to its default settings. Lastly, it is important to realize that this is a GUI based tool. Many operations are not possible from the command line. They must be done with the GUI. For example, a drive cannot be failed from the command line. This is very important because this is normally the method for returning a hot spare to a hot spare pool. Other examples include changing some controller properties. Controller transfer rates and battery properties must be done through the GUI. System monitoring tools such as Event Broadcasting cannot be configured from the command line. So, as great as the command line is, the GUI will probably have to be used at some point. Product Sun Enterprise 250 Server Sun Enterprise 450 Server E450, E250 Previously Published As 21419 Change History Date: 2003-05-20 User Name: Administrator Action: Migration from KMSCreator Comment: updated by : Gary Northup comment : edited content date : Jan 5, 2000 Version: 0 Attachments This solution has no attachment |
||||||||||||
|