> On the DL300 8 devices (IBM LTO2) are configured for each Solaris machine.
> The problem is the mapping from the physical device connections to the
> logical device names on the Solaris machines:
>
> Server1:
> [email protected]:IBM ULT3580-TD2 333K|Tape, /dev/rmt/1cbn
> [email protected]:IBM ULT3580-TD2 333K|Tape, /dev/rmt/2cbn
> [email protected]:IBM ULT3580-TD2 333K|Tape, /dev/rmt/3cbn
[...]
There are three common points on Solaris that affect the mapping. Any
one of which could affect your machines.
#1 SCSI/FC bridge.
If a SCSI tape is behind a FC bridge, the SCSI target to FC
identification can be static or dynamic. In a dynamic environment, this
can cause problems. Make the mapping static where possible.
#2 FC drivers on host.
Some drivers make a mapping from FC device/LUN to Solaris "target" and
lun. Making those mappings static will prevent the targets from jumping
around.
#3 Target/Lun to rmt instance
The tape "instances" are created in order based on when the device was
discovered. The past discoveries are recorded in /etc/path_to_inst with
"st" identifiers. While these mappings are static once created, they
can be in different orders from server to server. If you're careful,
you can modify the mapping in /etc/path_to_inst so that the st order is
the way you want it. If you do modify that file, you should probably
remove the /dev/rmt/* links and rebuild them with 'devfsadm'.
--
Darren Dunham ddunham AT taos DOT com
Senior Technical Consultant TAOS http://www.taos.com/
Got some Dr Pepper? San Francisco, CA bay area
< This line left intentionally blank to confuse you. >
--
Note: To sign off this list, send a "signoff networker" command via email
to listserv AT listserv.temple DOT edu or visit the list's Web site at
http://listserv.temple.edu/archives/networker.html where you can
also view and post messages to the list. Questions regarding this list
should be sent to stan AT temple DOT edu
=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=
|
