US Robotics 7931 Betriebsanweisung PDF herunterladen (Seite 200)

176 Sun StorageTek SAM Archive Configuration and Administration Guide • Version 4, Update 6, 04/07

The last two entries in this mcf file define the Sun SAM-Remote pseudo-devices, as

indicated by the rd equipment type. A pseudo-device defines a network connection

to an actual device on the Sun SAM-Remote server. Pseudo-device entries are

created when the system is rebooted. You can define an unlimited number of

pseudo-devices.

▼ To Define a Sun SAM-Remote Client

The Sun SAM-Remote client’s configuration file contains a single-line entry

consisting of the name of the Sun SAM-Remote server. As shown in “To Edit the mcf

Files” on page 173 in Step 2, the full path name of this client configuration file is

specified in the client’s mcf file.

1. On each client, use vi(1) or another editor to open a file to be known as the Sun

SAM-Remote client configuration file.

For example:

2. Edit the file and include only the name of the Sun SAM-Remote server.

CODE EXAMPLE 7-4 shows the client configuration file on portland after you have

edited it. It points to the Sun SAM-Remote server called chicago.

▼ To Define a Sun SAM-Remote Server in the Server’s mcf

File

Note – You must have at least one Sun StorageTek SAM file system configured in

the mcf file for the Sun SAM-Remote server.

● On the Sun SAM-Remote server, use vi(1) or another editor to edit the existing

Sun StorageTek SAM /etc/opt/SUNWsamfs/mcf file.

Suppose you edit the mcf file on server chicago. The resulting file defines a Sun

StorageTek QFS file system and also defines chicago as a Sun SAM-Remote server.

portland# vi /etc/opt/SUNWsamfs/rmt200

CODE EXAMPLE 7-4 Client Configuration File

portland# cat /etc/opt/SUNWsamfs/rmt200

chicago

1 2 ... 195 196 197 198 199 200 201 202 203 204 205 ... 287 288

Keine Kommentare

US Robotics 7931 Betriebsanweisung Seite 200