This is a multipart message in MIME format.
--=_alternative 005CB45E862570FF_=
Content-Type: text/plain; charset="US-ASCII"
Did you get the latest mappings.txt?
Here is the NB 6.0 version...
http://seer.support.veritas.com/docs/281082.htm
I think the wizard uses mappings.txt...
an updated st driver might do the trick also patch 108725-22 for s2.8
Karl
"Paul Keating" <pkeating AT bank-banque-canada DOT ca>
Sent by: veritas-bu-admin AT mailman.eng.auburn DOT edu
01/23/2006 08:30 AM
To
<veritas-bu AT mailman.eng.auburn DOT edu>
cc
Subject
[Veritas-bu] anyone using LTO3 with Solaris 8?
I previously had four LTO2 drives in each of two libraries....do to a bad
GBIC in a switch, and several subsequent events, one drive wasn't visable,
so my backup server was only seeing 7 drives.
Last night, I replaced the 8 port Sun FC switches with a couple of Brocade
3800s that were released from another project, and added an additional 3
LTO3 drives in each library.
I did a /usr/openv/volmgr/bin/sg.build, followed by an sg.install
I've added the following to the /kernel/drv/st.conf
"HP Ultrium 3", "HP Ultrium LTO3", "ULTRIUM3";
ULTRIUM3 = 1,0x36,0,0xd639,4,0x44,0x44,0x44,0x44,3;
I can see all the drives when I do a:
bash-2.03# cfgadm -al -o show_FCP_dev
all eight LTO2, and six LTO3
devfsadm, or a boot -r picks up all the devices properly, and creates all
the proper device files, but sgscan sees only the 7 LTO2 drives.
I used tpconfig to remove all of the old drive configs and re-ran the GUI
device configuration wizard, but it sees 7 LTO2 drives, and 2 drives of
unknown type.
sg.conf is up to date with all WWN maps, etc.....so sg.conf isn't
reporting any errors about unmapped WWNs.....
I used tpconfig and manually configured all 14 drives and can exercise
them using robtest, but sgscan and the device config wizard still see the
same.
any idears?
Paul
--=_alternative 005CB45E862570FF_=
Content-Type: text/html; charset="US-ASCII"
<br><font size=2 face="sans-serif">Did you get the latest mappings.txt?</font>
<br>
<br><font size=2 face="sans-serif">Here is the NB 6.0 version...</font>
<br><font size=2
face="sans-serif">http://seer.support.veritas.com/docs/281082.htm</font>
<br>
<br><font size=2 face="sans-serif">I think the wizard uses
mappings.txt...</font>
<br>
<br><font size=2 face="sans-serif">an updated st driver might do the trick
also patch </font><font size=3><tt>108725-22</tt></font><font size=2
face="sans-serif">
for s2.8</font>
<br>
<br><font size=2 face="sans-serif">Karl<br>
</font>
<br>
<br>
<br>
<table width=100%>
<tr valign=top>
<td width=40%><font size=1 face="sans-serif"><b>"Paul Keating"
<pkeating AT bank-banque-canada DOT ca></b> </font>
<br><font size=1 face="sans-serif">Sent by: veritas-bu-admin AT
mailman.eng.auburn DOT edu</font>
<p><font size=1 face="sans-serif">01/23/2006 08:30 AM</font>
<td width=59%>
<table width=100%>
<tr valign=top>
<td>
<div align=right><font size=1 face="sans-serif">To</font></div>
<td><font size=1 face="sans-serif"><veritas-bu AT mailman.eng.auburn DOT
edu></font>
<tr valign=top>
<td>
<div align=right><font size=1 face="sans-serif">cc</font></div>
<td>
<tr valign=top>
<td>
<div align=right><font size=1 face="sans-serif">Subject</font></div>
<td><font size=1 face="sans-serif">[Veritas-bu] anyone using LTO3 with
Solaris 8?</font></table>
<br>
<table>
<tr valign=top>
<td>
<td></table>
<br></table>
<br>
<br>
<br><font size=3> </font>
<br><font size=2 face="Arial">I previously had four LTO2 drives in each
of two libraries....do to a bad GBIC in a switch, and several subsequent
events, one drive wasn't visable, so my backup server was only seeing 7
drives.</font>
<br><font size=3> </font>
<br><font size=2 face="Arial">Last night, I replaced the 8 port Sun FC
switches with a couple of Brocade 3800s that were released from another
project, and added an additional 3 LTO3 drives in each library.</font>
<br><font size=3> </font>
<br><font size=2 face="Arial">I did a /usr/openv/volmgr/bin/sg.build, followed
by an sg.install</font>
<br><font size=3> </font>
<br><font size=2 face="Arial">I've added the following to the
/kernel/drv/st.conf</font>
<br><font size=3> </font>
<br><font size=2 face="Arial"> "HP
Ultrium 3", "HP
Ultrium LTO3", "ULTRIUM3";</font>
<br><font size=3> </font>
<br><font size=2 face="Arial">ULTRIUM3 =
1,0x36,0,0xd639,4,0x44,0x44,0x44,0x44,3;</font>
<br><font size=2 face="Arial">I can see all the drives when I do a:</font>
<br><font size=2 face="Arial">bash-2.03# cfgadm -al -o show_FCP_dev</font>
<br><font size=3> </font>
<br><font size=2 face="Arial">all eight LTO2, and six LTO3</font>
<br><font size=3> </font>
<br><font size=2 face="Arial">devfsadm, or a boot -r picks up all the devices
properly, and creates all the proper device files, but sgscan sees only
the 7 LTO2 drives.</font>
<br><font size=2 face="Arial">I used tpconfig to remove all of the old
drive configs and re-ran the GUI device configuration wizard, but it sees
7 LTO2 drives, and 2 drives of unknown type.</font>
<br><font size=3> </font>
<br><font size=2 face="Arial">sg.conf is up to date with all WWN maps,
etc.....so sg.conf isn't reporting any errors about unmapped WWNs.....</font>
<br><font size=3> </font>
<br><font size=2 face="Arial">I used tpconfig and manually configured all
14 drives and can exercise them using robtest, but sgscan and the device
config wizard still see the same.</font>
<br><font size=3> </font>
<br><font size=2 face="Arial">any idears?</font>
<br><font size=3> </font>
<br><font size=2 face="Arial">Paul</font>
<br>
--=_alternative 005CB45E862570FF_=--
|
