Troubleshooting the Configuration Files

Version 1

    Troubleshooting the Configuration Files

    After the software packages have been installed, you need to tailor the configuration files to the site installation in order to bring the system into an operational state. Syntactical and typographical errors in these configuration files manifest themselves in unexpected behavior.

    Configuration Files and Their Locations

    Configuration File PurposeDefault Location
    Master configuration file/etc/opt/SUNWsamfs/mcf
    st device file/kernel/drv/st.conf
    samst(7) device file/kernel/drv/samst.conf
    Device mapping/etc/opt/SUNWsamfs/inquiry.conf
    Default settings file/etc/opt/SUNWsamfs/defaults.conf

     

    The /etc/opt/SUNWsamfs/mcf File

    The mcf file defines the file system devices and device family sets.

     

    The mcf file is read when sam-fsd(1M) is started. It can be changed at any time, even while sam-fsd is running, but sam-fsd(1M) recognizes mcf file changes only when the daemon is restarted. The following example shows an mcf file for an archiving environment.

    Example – Example mcf File Configured for Archiving

     

    #

     

    # SAM-QFS file system configuration example

    #

    # Equipment Eq Eq Family Dev Additional

    # Identifier Or Tp Set St Parameters

    # --------------- -- -- ------ --- ----------

    samfs1 10 ms samfs1

    /dev/dsk/c1t1d0s6 11 md samfs1 on

    /dev/dsk/c2t1d0s6 12 md samfs1 on

    /dev/dsk/c3t1d0s6 13 md samfs1 on

    /dev/dsk/c4t1d0s6 14 md samfs1 on

    /dev/dsk/c5t1d0s6 15 md samfs1 on

    #

    samfs2 20 ms samfs2

    /dev/dsk/c1t1d0s0 21 md samfs2 on

    /dev/dsk/c1t0d0s1 22 md samfs2 on

     

    #

    /dev/samst/c1t2u0 200 rb hp30 on

    /dev/samst/c1t5u0 201 od hp30 on

    /dev/samst/c1t6u0 202 od hp30 on

     

     

    /dev/samst/c4t500104F0009C2F6Fu0 300 sn L500 on

    /dev/rmt/0cbn 301 li L500 on

    /dev/rmt/1cbn 302 li L500 on

    The most common problems with the mcf file are syntactical and typographical errors. The sam-fsd(1M) command is a useful tool in debugging the mcf file. If sam-fsd encounters an error as it processes the mcf file, it writes error messages to the SAM-QFS log file (if configured). It also reports errors detected in the following other files, if present:

    • diskvols.conf
    • samfs.cmd
    • defaults.conf
    For a newly created or modified mcf file, run the sam-fsd(1M) command and check for error messages. If necessary, correct the mcf file and rerun the sam-fsd command to ensure that the errors have been corrected. Repeat this process until all errors have been eliminated. When the mcf file is error free, re initialize the sam-fsd daemon by sending it the SIGHUP command. The following example shows this process.
    Example – Checking the mcf File

     

    skeeball # sam-fsd 6: /dev/dsk/c1t2d0s0 10 md samfs1 on /dev/rdsk/c1t2d0s0 *** Error in line 6: Equipment Number 10 already in use 1 error in "/etc/opt/SUNWsamfs/mcf"sam-fsd: Read mcf /etc/opt/SUNWsamfs/mcf failed. skeeball # skeeball # cat mcf # # Equipment Eq Eq Family Device Additional # Identifier ORD Type Set State Parameters #----------- --- ---- ------ ------ ---------- samfs1 10 ms samfs1 on /dev/dsk/c1t2d0s0 10 md samfs1 on # samfs2 20 ms samfs2 on /dev/dsk/c1t2d0s1 21 md samfs2 on # # # ---------- STK ACSLS Tape Library ----------- # # Equipment Eq Eq Family Device Additional # Identifier Ord Type Set State Parameters #----------- --- ---- ------ ------ ---------- /etc/opt/SUNWsamfs/stk30 30 sk stk30 on /dev/rmt/0cbn 31 sg stk30 on /dev/rmt/1cbn 32 sg stk30 on skeeball # <correct error> skeeball # sam-fsd Trace file controls: sam-archiverd /var/opt/SUNWsamfs/trace/sam-archiverd cust err fatal misc proc date size 0 age 0sam-catserverd /var/opt/SUNWsamfs/trace/sam-catserverd cust err fatal misc proc date size 0 age 0sam-fsd /var/opt/SUNWsamfs/trace/sam-fsd cust err fatal misc proc date size 0 age 0sam-ftpd /var/opt/SUNWsamfs/trace/sam-ftpd cust err fatal misc proc date size 0 age 0sam-recycler /var/opt/SUNWsamfs/trace/sam-recycler cust err fatal misc proc date size 0 age 0sam-sharefsd /var/opt/SUNWsamfs/trace/sam-sharefsd cust err fatal misc proc date size 0 age 0sam-stagerd /var/opt/SUNWsamfs/trace/sam-stagerd cust err fatal misc proc date size 0 age 0Would stop sam-archiverd() Would stop sam-ftpd() Would stop sam-stagealld() Would stop sam-stagerd() Would stop sam-amld() skeeball # skeeball # samd config skeeball #

     

    Enable the changes to the mcf file for a running system by running the samd(1M) command with its config option (as shown at the end of the example above) or by sending the SIGHUP signal to sam-fsd. The procedure for reinitializing sam-fsd to make it recognize mcf file modifications varies, depending on the nature of the changes implemented in the mcf file. For the procedures to be followed in specific circumstances, see the Sun QFS File System Configuration and Administration Guide on OTN.

    Verifying mcf Drive Order Matching

    For direct attached libraries with more than a single drive, the order in which drive entries appear in the mcf file must match the order in which they are identified by the library controller. The drive that the library controller identifies as the first drive must be the first drive entry for that library in the mcf file, and so on.Network attached libraries use different procedures from direct attached libraries, because the drive order for a network attached library is defined by the library control software. For example, for a network attached StorageTek library, the drive mapping in the ACSLS parameters file must match the drives as presented by the ACSLS interface. In this case, the procedure is similar to that for a library without a front panel, except that an additional check is necessary to ensure that the ACSLS parameters file mapping is correct.

    The /kernel/drv/st.conf File

    Some tape devices that are compatible with SAM-QFS software are not supported by default in the Solaris OS kernel. The file /kernel/drv/st.conf is the Solaris st(7D) tape driver configuration file for all supported tape drives. This file can be modified to enable operation of normally unsupported drives with a SAM-QFS system. Attempting to use any such device in the SAM-QFS environment without updating the st.conf file, or with an incorrectly modified file, causes the system to write messages such as the following to the device log file:

    Aug 3 19:43:36 samfs2 scanner[242]: Tape device 92 is defaulttype. Update /kernel/drv/st.conf

    If your configuration is to include devices not supported by the Solaris OS, consult the /opt/SUNWsamfs/examples/st.conf_changes file for instructions on how to modify the st.conf file.For example, the IBM LTO drive is not supported by default in Solaris kernel. The following example shows the lines you need to add to the st.conf file in order to include IBM LTO drives in a SAM-QFS environment.

    Example – Lines to be Added to st.conf
    "IBM ULTRIUM-TD1", "IBM Ultrium", "CLASS_3580", CLASS_3580 = 1,0x24,0,0x418679,2,0x00,0x01,0;

    The st.conf file is read only when the st driver is loaded, so if the /kernel/drv/st.conf file is modified, perform one of the following actions in order to direct the system to recognize the changes:

    • Use the unload(1M) and modload(1M) command to reload the driver.
    • Reboot the system.

    The /kernel/drv/samst.conf File

    # /usr/sbin/devfsadm -i samst
    name="samst" parent="fp" lun=0 fc-port-wwn="500104f00041182b";
    Example – Using cfgadm(1M) to obtain the WWN
    # cfgadm -al

    The /etc/opt/SUNWsamfs/inquiry.conf File

    Example – Part of the inquiry.conf File
    "ATL", "ACL2640", "acl2640" # ACL 2640 tape library
    # samcmd aridle
    Example – Messages Regarding inquiry.conf Problems
    .

    The /etc/opt/SUNWsamfs/defaults.conf File