
Chapter 7 Using the Sun SAM-Remote Software 175
The mcf entry on the client consists of a single-line entry for the Sun SAM-Remote
client and a pseudo-device entry for each device you want to configure. These
entries follow the syntax as defined in the mcf(4) man page.
The first set of entries defines a Sun StorageTek QFS file system.
The second set of entries defines the Sun SAM-Remote client, portland, to the Sun
SAM-Remote server, chicago. The first line defines the Sun SAM-Remote server
itself, as described below.
■ Equipment identifier, consisting of the path name of the client configuration file,
which is created later in “To Define a Sun SAM-Remote Client” on page 176.
■ Equipment ordinal, consisting of a unique number from 1 through 65535.
■ Equipment type, consisting of a two-letter mnemonic that identifies a Sun SAM-
Remote client.
■ Family set, consisting of the family set name of the daemon to be used on this
particular server. A Sun SAM-Remote server can have one server daemon per
client.
■ Device state, either on or off.
■ Additional parameters, an optional field consisting here of the path to the catalog
file.
CODE EXAMPLE 7-3 mcf File on portland
# mcf file on portland
#
# Sun StorageTek QFS file system
#
# Equipment Eq Eq Family Dev Additional
# Identifier Ord Ty Set St Parameters
# ========== === == ====== == ==========
samfs1 1 ms samfs1 on
/dev/dsk/c1t1d0s0 10 md samfs1 on /dev/rdsk/c1t1d0s0
/dev/dsk/c1t2d0s0 12 md samfs1 on /dev/rdsk/c1t2d0s0
#
# Define Sun SAM-Remote Client portland to Sun SAM-Remote server chicago
#
/etc/opt/SUNWsamfs/rmt200 200 sc chicagoss on /var/opt/SUNWsamfs/catalog/tcat
/dev/samrd/rd0 201 rd chicagoss on
/dev/samrd/rd1 202 rd chicagoss on
Commentaires sur ces manuels