| Sun StorEdge SAM-FS Installation and Upgrade Guide |    
|
| Sun StorEdge SAM-FS Installation and Upgrade Guide |
|
| A P P E N D I X D |
|
mcf File Examples |
This appendix contains some specific examples of mcf files for complex Sun StorEdge SAM-FS environments.
This appendix contains the following sections:
For the examples in this appendix, assume that the following equipment is to be included in the Sun StorEdge SAM-FS configuration:
This equipment is connected to three SCSI buses with the following SCSI targets:
CODE EXAMPLE D-1 shows the output from the Sun Solaris format(1M) command. It reports how the disks are partitioned.
This example creates one Sun StorEdge SAM-FS file system (samfs1) on partition 0 of disk c1t0d0 and partition 5 of c1t1d0. It creates another file system (samfs2) on partition 1 of disk c1t0d0 and partition 0 of disk c1t1d0.
The following procedure explains how to begin writing the mcf file for this example configuration by defining the file systems and their disk partitions.
|
Follow these steps first for the samfs1 file system and then for the samfs2 file system.
1. Make an ms (mass storage) entry for the file system.
The ms entry is the Equipment Identifier for a Sun StorEdge SAM-FS file system.
You will use the name of the file system later when writing the /etc/vfstab entry for the file system and creating the file system.
|
Note - The name as specified in the Equipment Identifier field must be the same as the Family Set name for the file system. |
2. Make a series of md (magnetic disk) entries listing the partitions for the file system member devices.
CODE EXAMPLE D-2 shows the mcf with the file systems defined.
The HP Model C1716T is target ID 2 on the internal SCSI bus.
|
1. Examine the /var/adm/messages file to find the messages for these devices.
CODE EXAMPLE D-3 shows the information in /var/adm/messages associated with the HP Model C1716T and target 2. Note that the third line wraps to the next line.
2. Issue the cd(1) command to change to the /dev/samst directory.
3. Use the ls(1) and grep(1) commands to find the correct symbolic link:
The ls(1) command searches for a symbolic link that points to the hardware path shown in CODE EXAMPLE D-4.
lrwxrwxrwx 1 root other 88 Aug 23 12:27 c0t2u0 -> /devices/iommu@0,10000000/sbus@0,10001000/espdma@5,8400000/esp@5,8800000/samst@2,0:a,raw |
The Sun samst driver uses the name /dev/samst/c0t2u0 when referencing the device.
4. Open the /etc/opt/SUNWsamfs/mcf file, and add the following entry for the drive:
This entry contains the device name (/dev/samst/c0t2u0), a unique Equipment Ordinal (30), the Equipment Type of the drive (od), a dash (-) to indicate that a Family Set name is not associated with the drive, and the device state (on).
The HP C1710T automated library has three SCSI devices: the robotic mechanism and the two magneto-optical drives that the automated library loads and unloads.
|
1. Examine the /var/adm/messages file to find the messages for these devices.
CODE EXAMPLE D-5 shows these messages.
2. Issue the cd(1) command to change to the /dev/samst directory.
3. Use ls(1) and grep(1) commands to find the symbolic links for the devices.
CODE EXAMPLE D-6 shows the ls(1) commands to use to search for the three symbolic links that point to the /devices files with the same Sun Solaris hardware paths shown in CODE EXAMPLE D-5.
# ls -l | grep "samst@2" lrwxrwxrwx 1 root other 74 Aug 23 12:27 c1t2u0 -> /devices/iommu@0,10000000/sbus@0,10001000/QLGC,isp@1,10000/samst@2,0:a,raw # ls -l | grep "samst@5" lrwxrwxrwx 1 root other 74 Aug 23 12:27 c1t5u0 -> /devices/iommu@0,10000000/sbus@0,10001000/QLGC,isp@1,10000/samst@5,0:a,raw # ls -l | grep "samst@6" lrwxrwxrwx 1 root other 74 Aug 23 12:27 c1t6u0 -> /devices/iommu@0,10000000/sbus@0,10001000/QLGC,isp@1,10000/samst@6,0:a,raw |
4. Open the /etc/opt/SUNWsamfs/mcf file, and add the following entries for the library and drives:
The first line defines the automated library itself. It contains the /dev/samst name for the device (/dev/samst/c1t2u0) followed by a unique Equipment Ordinal (50), the Equipment Identifier (rb, for a generic SCSI-attached library), the Family Set identifier specified on all devices associated with this library (hp30), and the device state (on).
The two remaining lines define the drives inside the library. They are similar to the manually loaded drives defined in the previous section except that instead of a dash, they include the Family Set name of the library where they reside (hp30).
|
Caution - The order of drives as specified in the mcffile must match the logical order of the drives in a SCSI-attached automated library. For more information, see Checking the Drive Order, or refer to your hardware documentation. Incorrect configuration can cause cartridges to be mounted in the wrong drives, which will lead to total inoperability of this software. |
When configuring DLT drives, be sure to add the DLT definitions to the /kernel/drv/st.conf file. DLT drives are not part of the standard Sun Solaris configuration, and the software does not recognize them if they are configured incorrectly. For more information, see Configuring Storage Devices.
|
1. Examine the /var/adm/messages file to find the messages for these devices.
CODE EXAMPLE D-7 shows the /var/adm/messages file lines that refer to the manual DLT drive.
2. Use the ls(1) and grep(1) commands to search for the symbolic links that point to the /devices files with the same Sun Solaris hardware paths shown in the /var/adm/messages file.
The following ls(1) and grep(1) commands are used to locate the DLT drive identified as scsi@5.
# ls -l /dev/rmt|grep 'pci@1f,4000/scsi@5,1/st@0'|grep cbn lrwxrwxrwx 1 root other 45 Feb 14 09:48 0cbn -> ../../devices/pci@1f,4000/scsi@5,1/st@0,0:cbn |
When making the mcf entry, always use the b and n options. CODE EXAMPLE D-8 shows the symbolic link for a drive that supports compression. If the drive supports compression and you want compression in the hardware, use cbn as the prefix.
3. Open the /etc/opt/SUNWsamfs/mcf file, and add the following entry for the device:
This entry contains the st driver name for the device (/dev/rmt/0cbn), a unique Equipment Ordinal (40), the Equipment Type (tp for a generic tape), a dash (-) to indicate that a Family Set name is not associated with the manually mounted device, and the device state (on).
The last piece of equipment to define is the STK 9730 automated library. This automated library has three SCSI devices: the robotic mechanism and the two DLT 7000 tape drives that the robot loads and unloads.
|
1. Examine the /var/adm/messages to find the messages for these devices.
CODE EXAMPLE D-9 shows the /var/adm/messages file.
2. Issue the cd(1) command to change to the /dev/samst directory.
3. Use the ls(1) and grep(1) commands to find the symbolic links that point to the /devices files with the same Sun Solaris hardware paths shown in the /var/adm/messages file:
# cd /dev/samst # ls -l | grep "samst@0" lrwxrwxrwx 1 root other 49 Feb 4 09:42 c6t0u0 -> ../../devices/pci@6,4000/scsi@2,1/samst@0,0:a,raw |
4. Use the ls(1) and grep(1) commands to find a symbolic link in /dev/rmt that points to the tape devices:
There are multiple symbolic links in the directory that point to the same hardware path. To enable hardware compression, choose the one with the cbn suffix. If your drive does not support hardware compression, choose the link that ends with bn.
5. Open the /etc/opt/SUNWsamfs/mcf file, and add entries for this library and its drives:
The first line defines the automated library. It includes the /dev/samst name (/dev/samst/c2t0u0), a unique Equipment Ordinal (60), the Equipment Type (rb, for the generic robot Equipment Type), a Family Set name for the robot and the drive (9730), and the device state (on).
The second line defines the first DLT tape drive inside the library. It contains the Equipment Identifier for this tape device (/dev/rmt/0cbn), the Equipment Ordinal for the device (61), the Equipment Type (tp), the Family Set name (9730), and the device state (on).
The third line defines the second DLT tape drive inside the automated library.
6. If you are configuring DLT drives, add the DLT definitions to the /kernel/drv/st.conf file.
Configuring Storage Devices describes how to add definitions to the /kernel/drv/st.conf file. DLT drives are not part of the standard Sun Solaris configuration.
CODE EXAMPLE D-10 shows the completed mcf file.
The following examples show mcf file entries for network attached devices. In these examples, the first line of each library definition is the full path to the parameters file for that library.
You create the parameters files for network attached libraries as described in Creating Parameters Files for Network Attached Automated Libraries.
Example 1. CODE EXAMPLE D-11 shows the mcf file for an ADIC/Grau network attached automated library.
Example 2. CODE EXAMPLE D-12 shows the mcf file for a Fujitsu LMF network attached automated library.
Example 3. CODE EXAMPLE D-13 shows the mcf file for an IBM 3494 network attached automated library.
Example 4. CODE EXAMPLE D-14 shows the mcf file for a Sony network attached automated library.
Example 5. CODE EXAMPLE D-15 shows the mcf file for a StorageTek ACSLS-attached automated library.
For more information, see the mcf(4) man page. There are example mcf files located in /opt/SUNWsamfs/examples/mcf.
| Sun StorEdge SAM-FS Installation and Upgrade Guide | 819-4330-10 |
|
Copyright © 2006, Sun Microsystems, Inc. All Rights Reserved.
To Write the mcf File
