Hi!
I've got to make sf 880 (Solaris 9) work with SAN connected HP EVA5000 storage & MSL6060 library.
HBAs are FCA2257P and are redundant , so we use
the Secure path (3.0D) sw to work with the EVA storage.
The qla2300 driver comes with it. I cannot remove the
native (Solaris) qlc driver because of the internal disks.
Ok so far. I can use the storage disks, but I cannot acces the
library drives (LTO Ultrium 460). I don't need to control the robotics as the backup SW is already using another (Win) box to do that,
so successfull 'mt' operation would do.
1.) How do I enforce qlc driver to leave the HBAs to the qla2300
(is the change to /etc/driver_aliases all I've got to do) ?
2.) Can I use Solaris' st driver?
3.) As I added the HBAs later (st was already installed), how do
I get the device files and links (/dev/rmt/...)
created ?
Thanks.
Borut
I've got to make sf 880 (Solaris 9) work with SAN connected HP EVA5000 storage & MSL6060 library.
HBAs are FCA2257P and are redundant , so we use
the Secure path (3.0D) sw to work with the EVA storage.
The qla2300 driver comes with it. I cannot remove the
native (Solaris) qlc driver because of the internal disks.
Ok so far. I can use the storage disks, but I cannot acces the
library drives (LTO Ultrium 460). I don't need to control the robotics as the backup SW is already using another (Win) box to do that,
so successfull 'mt' operation would do.
1.) How do I enforce qlc driver to leave the HBAs to the qla2300
(is the change to /etc/driver_aliases all I've got to do) ?
2.) Can I use Solaris' st driver?
3.) As I added the HBAs later (st was already installed), how do
I get the device files and links (/dev/rmt/...)
created ?
Thanks.
Borut