[Veritas-bu] Mismatch between sgscan output & st.conf entry?

To figure out the firmware version try sgscan -v or tpautoconf -show

-----Original Message-----
From: Donaldson, Mark [mailto:Mark.Donaldson AT experianems DOT com] 
Sent: Wednesday, August 13, 2003 11:38 PM
To: 'Zunker, Steven (STP)'
Cc: Veritasbu (E-mail)
Subject: RE: [Veritas-bu] Mismatch between sgscan output & st.conf
entry?


Don't know about the firmware version.  Can it be queried at the
command-line?  The STK is 1000 miles from my desk.

Good feedback - I'll check.  Restorals are rare & duplications more rare
in our environment so if this is a problem, it's likely we'd not
encounter it before.

-M

-----Original Message-----
From: Zunker, Steven (STP) [mailto:Steven.Zunker AT guidant DOT com]
Sent: Wednesday, August 13, 2003 3:08 PM
To: Donaldson, Mark
Subject: RE: [Veritas-bu] Mismatch between sgscan output & st.conf
entry?


Mark,

What firmware version are you running on your LTO drives?? We are at
E2A2. We had a huge problem last July with media position errors during
restores and duplications. We had to go to a Beta firmware version from
HP to resolve. That version is now the latest released version from HP.
Just thought I would check. 

Here is my sgscan and st.conf output.

/dev/sg/c1t1l0: Tape (/dev/rmt/1): "HP      Ultrium 1-SCSI" 
/dev/sg/c1t1l1: Tape (/dev/rmt/3): "HP      Ultrium 1-SCSI" 
/dev/sg/c2t0l0: Changer: "HP      A5597A"
/dev/sg/c4t0l0: Tape (/dev/rmt/4): "HP      Ultrium 1-SCSI" 
<snip>

tape-config-list=
        "HP      Ultrium 1-SCSI", "HP ULTRA-SAN", "ULTRIUM";
ULTRIUM         =       1,0x36,0,0x19639,4,0x00,0x00,0x00,0x00,3;

Steve Zunker
Guidant Corp


-----Original Message-----
From: Donaldson, Mark [mailto:Mark.Donaldson AT experianems DOT com]
Sent: Wednesday, August 13, 2003 12:51 PM
To: Veritasbu (E-mail)
Subject: [Veritas-bu] Mismatch between sgscan output & st.conf entry?


I've got this (potential) mismatch between my "sgscan tape" output & the
st.conf file (Solaris 8).  If I udnerstand correctly, the name returned
in the third field of sgscan for a tape should be the same as the first
field of the st.conf "tape-config-list" entry for that device.  

Can somebody confirm this?

If this is the case, it could be the root of some problems of mine.  I
may not be running an appropriate set of parameters for my LTO drives.

If this is not the case, what command should I be using to query the
drive identification to compare against the st.conf file?

Advise anyone?
-M

Here's "sgscan tape":
/dev/sg/c1t3l1: (/dev/rmt/0): "HP      Ultrium 1-SCSI"
<snip>
/dev/sg/c1t5l2: (/dev/rmt/8): "QUANTUM SuperDLT1"

Here's the relevant st.conf lines:
> grep -v "^#" /kernel/drv/st.conf

tape-config-list=
"HP Ultrium",           "HP Ultrium",           "HP_LTO",
"QUANTUM SuperDLT1",    "Quantum SDLT 220",     "SDLT_220";

HP_LTO          =       1,0x36,0,0x1d639,4,0x00,0x00,0x00,0x00,3;
SDLT_220        =       1,0x38,0,0x1d639,4,0x90,0x91,0x90,0x91,3;

_______________________________________________
Veritas-bu maillist  -  Veritas-bu AT mailman.eng.auburn DOT edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
_______________________________________________
Veritas-bu maillist  -  Veritas-bu AT mailman.eng.auburn DOT edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu

**************************************************************************************************
The contents of this email and any attachments are confidential.
It is intended for the named recipient(s) only.
If you have received this email in error please notify the system manager or  
the 
sender immediately and do not disclose the contents to any one or make copies.

MBI - System Team
**************************************************************************************************