DEL SISTEMA DE AGUA POTABLE

Table 28 shows the special file naming convention and the associated device attributes recognized by the IBMtape device driver.

Table 28. IBM SCSI Tape/Medium Changer Special Files for Solaris

Special File Name

BSD Compatibility (Note

1) Rewind on Close (Note 2) Compression (Note 3)

/dev/rmt/[0–255]smc(Note 4) N/A N/A N/A

/dev/rmt/[0–255]stn(Note 5) No No No

/dev/rmt/[0–255]stcn(Note 5) No No Yes

/dev/rmt/[0–255]st(Note 5) No Yes No

/dev/rmt/[0–255]stc(Note 5) No Yes Yes

/dev/rmt/[0–255]stbn(Note 5) Yes No No

/dev/rmt/[0–255]stcbn(Note 5) Yes No Yes

/dev/rmt/[0–255]stb(Note 5) Yes Yes No

/dev/rmt/[0–255]stcb(Note 5) Yes Yes Yes

Notes:

1. TheBSD (b)device special file modifiesclosebehavior for non-rewind devices. If the device is opened forno rewind on closeinnon-BSDmode, and if the last command before closing the device was a read, then the tape is positioned after the filemark immediately following the last block read. If the device is opened forno rewind on closeinBSDmode, and if the last command before closing the device was a read, the tape is left positioned exactly where it was following the last block read. If the device is opened forrewind on closetheBSDmode is not relevant.

2. Theno rewind on close (n)device special file does not rewind the tape during acloseoperation. Otherwise, the tape is rewound when the device is closed. If the last operation before closing the device was a write or write filemark, then a sufficient number of filemarks is written so that two filemarks follow the data.

For the non-rewind special files, the tapes are positioned between the trailing filemarks before closing. If the device is then reopened and more data is written, it is separated by a single filemark from the previous data. 3. Thecompression (c)device special file determines whether the tape device uses built-in hardware compression

while storing data on the tape. The compression mode of the device can also be set to the desired state programmatically through the STIOC_SET_PARMioctl, regardless of the default compression mode established by the special file originally used to open the device.

4. Thesmcspecial file is created only for IBM tape systems that provide medium changer capability. For IBM tape libraries and autoloaders, thesmcspecial file is the only file created because the IBMtape device driver supports only the medium changer portion and does not support the tape drive portion of these devices. For the IBM 3490E Magnetic Tape System, there is nosmcspecial file created.

5. Only onestspecial file may be opened at one time. Thesmcspecial file may be opened by itself or in conjunction with one of thesttype files. Thesmcspecial file accepts only medium changer commands. Tape drive commands issued to the medium changer fail, witherrnoset to 22, invalid argument.

Aside from the normal configuration with the medium changer answering as a distinct target/LUN pair, some supported devices can be configured with a nonstandard integrated medium changer reporting at the same target and LUN as the tape drive. In such a case, bothstandsmcspecial files accept a limited subset of medium changer commands. If you want to use this nonstandard mode, consult the appropriate hardware reference to determine whether the drive supports such a configuration.

Persistent Naming Support

The device special file names are created by the IBMtape driver in the order that the tape devices are presented by the Solaris system. Each device special file name is maintained with the same logical name across reboots, even when an existing device is powered off or not connected.

However, the logical names of devices may be changed due to the swapping of connecting cables, HBA mapping changes, tape device driver updates, or other reasons.

The user can rename the logical name by editing the/etc/devlink.tabsystem file for the persistent name binding and reloading the IBMtape driver as follows:

1. Before the persistent name binding, make sure that the IBM tape devices are configured at the different target and LUN addresses if the devices are attached on more than one HBA.

The Ultrium-3 tape drive is connected to two Emulex HBAs with the same address of target 3 and LUN 0 via a switch in the following example. You have to use the HBA utility, follow HBA vendor instructions, or both to persistently bind the tape devices at the different mapped target and LUN.

# tapelist -l

Inst# Special File Device Serial No TGT/LUN Device Physical Path

--- --- --- --- --- ---

454 /dev/rmt/2st ULT3580-TD3 1210003557 3/0 /devices/pci@6,2000/pci@1/fibre-channel@5/IBMtape@3,0 582 /dev/rmt/8st ULT3580-TD3 1210003557 3/0 /devices/pci@1f,2000/pci@1/fibre-channel@5/IBMtape@3,0

The tape drive is mapped at target 3, LUN 0 on HBA 1 and target 24, LUN 0 on HBA 2 after device persistent binding.

# tapelist -l

Inst# Special File Device Serial No TGT/LUN Device Physical Path

--- --- --- --- --- ---

454 /dev/rmt/4st ULT3580-TD3 1210003557 3/0 /devices/pci@6,2000/pci@1/fibre-channel@5/IBMtape@3,0 1136 /dev/rmt/7st ULT3580-TD3 1210003557 24/0 /devices/pci@1f,2000/pci@1/fibre-channel@5/IBMtape@18,0

Note: Device persistent binding is not provided on Sun HBAs, so this

persistent name approach cannot be used with the same physical drive that is attached to multiple Sun HBA ports.

2. Start persistent name binding. In this example, the user renames4stand 7stto

10stand11st.

a. Create the entry for persistent naming. Determine the target address from the Device Physical Path in the output oftapelist -land add the planned device special file name in the entry. Here, 4st and 7st drives are located at 3,0 (target 3, LUN 0) and 18,0 (target 24 (0x18), LUN 0) at the device

physical paths of/devices/pci@6,2000/pci@1/fibre-channel@5/IBMtape@3,0

and/devices/pci@1f,2000/pci@1/fibre-channel@5/IBMtape@18,0. Add the

address and device file name into the entries: type=ddi_byte:tape;addr=3,0; rmt/10\M0 type=ddi_byte:tape;addr=18,0; rmt/11\M0 Notes:

1) A tab is entered between addr=3,0; and rmt/10\M0.

3) To avoid conflicts with the current device special files assigned by the system automatically, be sure to assign a higher number for the persistent name.

4) The address is w500507630059f007,0 for the tape drive on the Sun HBA with the path of /devices/pci@1,0/pci1022,7450@1/pci1077,141@1/

fp@0,0/tape@w500507630059f007,0.

b. Add the above entry into the/etc/devlink.tabsystem file.

c. Remove existing links created by the IBMtape driver from/dev/rmtby running the# rmcommand.

d. Run the# devfsadmcommand without any options to enable IBMtape to create the new device special file name as defined in the entries in

/etc/devlink.tab. A system reboot is also required if the tape device is

attached on Sun HBA.

e. Runtapelistto list the device special files.

# tapelist -l

Inst# Special File Device Serial No TGT/LUN Device Physical Path --- --- --- --- --- ---

454 /dev/rmt/10st ULT3580-TD3 1210003557 3/0 /devices/pci@6,2000/pci@1/fibre-channel@5/IBMtape@3,0 1136 /dev/rmt/11st ULT3580-TD3 1210003557 24/0 /devices/pci@1f,2000/pci@1/fibre-channel@5/IBMtape@18,0