Tape Libraries and Drives
cancel
Showing results for 
Search instead for 
Did you mean: 

Need help for configuring MSL 6000 on Solaris 10 and SLES 9

Kishan Kumar
Occasional Advisor

Need help for configuring MSL 6000 on Solaris 10 and SLES 9

HI,

I have a MSL 6000 Tape library connect to a FC switch through an NSR router(SCSI to FC router).I have connected 3 hosts in SAN to the FC switch.On HP-UX machine which is successfully configured For MSL 6000 and DP 5.5 installed which "devbra -dev" shows the changer as well as two tape drives.

However on the other two hosts solaris 10 and Sles 9 i have problems with the OS configuration itself for MSL 6000.

On solaris 10 when i try to load the sst drive (I followed DP documentation .SST driver comes along with DP software)it says driver loaded but failed to attach.( ie add_drv sst).This is a Sparc machine.
when i run "devbra - dev" it shows the 2 drives but not the changer.

ON SlES 9 i dodnot knwo how to configure MSL 6000 at the OS level itself forget about through DP.

Can anyone please help.Both the SLES 9 and Solarsi10 has qla2300 with appropraite drivers installed

Thanks in advance
Kishan
21 REPLIES
kholikt
Super Advisor

Re: Need help for configuring MSL 6000 on Solaris 10 and SLES 9

Hi,

Did you managed to get the problem resolve. I have the exact problem as yours. I am using MSL 5030
abc
Kishan Kumar
Occasional Advisor

Re: Need help for configuring MSL 6000 on Solaris 10 and SLES 9

YUp,

You need to populate your sst.conf file provided with DP
kholikt
Super Advisor

Re: Need help for configuring MSL 6000 on Solaris 10 and SLES 9

Hi,

Can I take a look of how your sst.conf look like? What is the steps you get it resolve?
abc
Kishan Kumar
Occasional Advisor

Re: Need help for configuring MSL 6000 on Solaris 10 and SLES 9

#
# Copyright (c) 1992,1997, by Sun Microsystems, Inc.
# All rights reserved.
#
# "@(#)sst.conf 1.5 97/09/14 SMI"
#
# Hardware Configuration file for sst, a Simple SCSI Target driver
# If you have more than one device attached, add more lines for the
# extra target/lun combinations (see sd.conf for an example)
#

name="sst" parent="fp" target=0 lun=1 fc-port-wwn="100000e00202dc0f";

# For attaching sst to a specific target:
# name="sst"
# parent="/iommu@f,e0000000/sbus@f,e0001000/espdma@f,400000/esp@f,800000"
# target=4 lun=0;

#
# For targets which support a logical unit number other than zero,
# change the lun field as appropriate, or for multiple logical
# unit numbers per target, add entries as follows:
#
# name="sst" class="scsi" target=5 lun=1;
#
=================================================

#
# Copyright 1995-2003 Sun Microsystems, Inc. All rights reserved.
# Use is subject to license terms.
#
#
#pragma ident "@(#)st.conf 1.32 03/09/08 SMI"
#

# This file contains configuration entries for both officially supported
# devices of Sun Microsystems and many 3rd party devices.
#
# The officially supported devices are :
#
# "ARCHIVE Python 28388" Note 1
# "ARCHIVE Python 28454" Note 1
# "ARCHIVE Python 29279" Note 1
# "ARCHIVE VIPER 150" Note 1
# "EXABYTE EXB-8200" Note 1
# "EXABYTE EXB-8500" Note 1
# "EXABYTE EXB-8505" Note 1
# "EXABYTE EXB-8900" Note 1
# "HP 88780" Note 1
# "HP C5683A" Note 1
# "HP C5713A" Note 1
# "Quantum DLT4000" Note 1
# "Quantum DLT7000" Note 1
# "Quantum DLT8000" Note 1
# "STK 9840" Note 1
# "SUN DLT4000" Note 1
# "SUN DLT4700" Note 1
# "SUN DLT7000" Note 1
# "TANDBERG SLR5" Note 1
# "TANDBERG TDC 4200" Note 1
# "TANDBERGMLR1" Note 1
# "TANDBERGMLR3" Note 1
#
# The unsupported devices are :
#
# "Emulex MTO2" Note 1
# "ANRITSU DMT2120" Note 1
# "ARCHIVE Python 04106" Note 1
# "ARCHIVE VIPER 255" Note 1
# "DEC DLT2"
# "DEC TZ87"
# "EXABYTE EXB-2501" Note 1
# "EXABYTE EXB-4200c" Note 1
# "EXABYTE EXB8500C"
# "FUJITSU M1016B M2483B"
# "FUJITSU M248"
# "HP C1533A" Note 1
# "HP C1553A "
# "HP C1537A" Note 1
# "HP C1557A" Note 1
# "HP HP35470A" Note 1
# "HP HP35480A" Note 1
# "IBM 03490"
# "IBM 9348"
# "KENNEDY" Note 1
# "LMS" Note 1
# "M4 DATA 123107 SCSI" Note 1
# "Metrum"
# "R-BYTE RB100"
# "Seagate STT20000N" Note 1
# "SONY SDT-5000" Note 1
# "SONY SDT-5200" Note 1
# "STK 9490"
# "STK 4280"
# "STK" Note 1
# "TANDBERG 4100" Note 1
# "TANDBERG 4200" Note 1
# "TELEX"
# "WANGTEK 51000 SCSI"
# "WANGTEK 5150ES" Note 1
# "WANGTEK 5525ES SCSI" Note 1
# "WANGTEK 6130-HS" Note 1
# "WangDAT Model 2600" Note 1
# "WangDAT Model 3400" Note 1
# "WangDAT" Note 1
# "\076\000" Note 1
#
# Notes
# -----
# 1 Drive is configured automatically - no entry is needed in st.conf.
#
# The 3rd party devices do apparently work with the configurations listed.
# All the entries have been taken from the net and probably have worked in
# the past, but have not been tested by Sun Microsystems. Use these entries
# as your starting point for generating your configuration entries.
#
#
#tape-config-list=
#"Emulex MTO2", "Emulex MT02 QIC-11/QIC-24", "MT02",
#"ANRITSU DMT2120", "Unisys 1/2\" Reel", "ANRITSU",
#"ARCHIVE Python 04106", "Seagate Scorpion 24 DDS3 DAT", "ARCH_04106",
#"ARCHIVE Python 28454", "Archive Python 4mm Helical Scan", "ARCH_Python",
#"ARCHIVE Python 29279", "Archive Python 4mm DAT Stacker", "ARCH_Python",
#"ARCHIVE Python 28388", "Archive/Conner CTDX004 4mm DAT", "Conner2-DAT",
#"ARCHIVE VIPER 150", "Archive QIC-150", "QIC150",
#"ARCHIVE VIPER 255", "Archive QIC-525", "QIC150",
#"DEC DLT2", "DEC DLT", "DLT2",
#"DEC TZ87", "DEC DLT", "DLT2",
#"EXABYTE EXB-2501", "Exabyte EXB-2501 QIC", "EXB-2501",
#"EXABYTE EXB-4200c", "Exabyte 4mm Helical Scan", "Exa4200c",
#"EXABYTE EXB-8200", "Exabyte EXB-8200 8mm Helical Scan","EXB-8200",
#"EXABYTE EXB-8500", "Exabyte EXB-8500 8mm Helical Scan","EXB-850X",
#"EXABYTE EXB-8505", "Exabyte EXB-8505 8mm Helical Scan","EXB-850X",
#"EXABYTE EXB8500C", "Exabyte 8500C 8mm Helical Scan", "EXB-850X",
#"FUJITSU M1016B M2483B", "Fujitsu 1/2\" Cartridge", "Fujitsu_comp",
#"FUJITSU M248", "Fujitsu 1/2\" Cartridge", "Fujitsu_m248x",
#"HP 88780", "HP-88780 1/2\" Reel", "HP_half",
#"HP C1533A", "HP DDS2 4mm DAT loader", "HP_DAT",
#"HP C1553A ", "HP C1553A 4mm DAT", "HP_DAT",
#"HP C1537A", "HP DDS-3 4mm DAT ", "HP_DAT_3",
#"HP C1557A", "HP DDS-3 4mm DAT loader", "HP_DAT_3",
#"HP HP35470A", "HP 35470A 4mm DAT", "HP_DAT",
#"HP HP35480A", "HP 35480A 4mm DAT", "HP_DAT",
#"IBM 03490", "IBM 3490E 1/2\" Cartridge", "CLASS_3490",
#"IBM 9348", "STK 4220 1/2\" Cartridge", "C3490",
#"KENNEDY", "Kennedy 1/2\" Reel", "KENNEDY",
#"LMS", "CDC 1/2\" Cartridge", "LMS",
#"M4 DATA 123107 SCSI", "M4-Data 1/2\" Reel", "M4_DATA",
#"Metrum", "Metrum VHS Cartridge", "MetD",
#"QUANTUM DLT7000", "Quantum DLT7000", "DLT7k-data",
#"SUN DLT7000", "Sun DLT7000", "DLT7k-data",
#"Quantum DLT4000", "Quantum DLT4000", "DLT-data",
#"SUN DLT4000", "DLT4000", "DLT-data",
#"SUN DLT4700", "DLT4700 Library", "DLT-data",
#"R-BYTE RB100", "R-Byte Whozits", "DAT",
#"Seagate STT20000N", "Seagate Hornet NS20 Travan", "NS20",
#"SONY SDT-5000", "SONY 4mm DAT", "DAT",
#"SONY SDT-5200", "SONY 4mm DAT", "DAT",
#"STK 9490", "STK 9490 1/2\" Cartridge", "CLASS_3490",
#"STK 4280", "STK 4280 1/2\" Cartridge", "C3490",
#"STK", "STK 1/2\" Cartridge", "CLASS_3490",
#"TANDBERG 4100", "Tandberg 4100 QIC", "TAND_4100_QIC",
#"TANDBERG 4200", "Tandberg 4200 QIC", "TAND_4200_QIC",
#"TANDBERG TDC 4200", "Tandberg QIC 2.5 Gig Tape Drive", "TANDB-2_5G",
#"TANDBERG SLR5", "Tandberg 8 Gig QIC", "TAND-8G-VAR",
#"TANDBERGMLR1", "Tandberg MLR1 QIC", "TANDBERG_MLR1",
#"TANDBERGMLR3", "Tandberg 50 Gig QIC", "TAND-50G-VAR",
#"TELEX", "STK 4220 1/2\" Cartridge", "C3490",
#"WANGTEK 51000 SCSI", "Wangtek 1.2GB QIC", "WtQIC",
#"WANGTEK 5150ES", "Wangtek QIC-150", "WANGTEK_QC150",
#"WANGTEK 5525ES SCSI", "Wangtek 525MB QIC", "WtQIC",
#"WANGTEK 6130-HS", "Wangtek 4mm Helical Scan", "WANGTEK_6130",
#"WangDAT Model 2600", "WangDAT 4mm DAT", "WangDAT",
#"WangDAT Model 3400", "WangDAT 4mm DAT", "WangDAT",
#"WangDAT", "Wang DAT 3.81 Helical Scan", "WangDAT",
#"\076\000", "Fujitsu 1/2\" Cartridge", "Fujitsu_half";
#"Seagate STT3401A", "Seagate Hornet Travan 40", "T40",
#"OnStreamADR Series", "On Stream USB Tape", "OnStream";

#ANRITSU = 1, 0x25, 0, 0x0041D, 4, 0x00, 0x02, 0x03, 0x03, 1;
#ARCH_04106 = 1, 0x2C, 0, 0x09639, 4, 0x00, 0x8C, 0x8C, 0x8C, 3;
#ARCH_Python = 1, 0x2C, 0, 0x0DE39, 4, 0x00, 0x8C, 0x8C, 0x8C, 3;
#CLASS_3490 = 1, 0x24, 0, 0x1C43D, 4, 0x00, 0x00, 0x00, 0x00, 0;
#C3490 = 1, 0x24, 0, 0x1C43D, 4, 0x00, 0x00, 0x00, 0x01, 2;
#Conner2-DAT = 1, 0x2C, 0, 0x0DE39, 4, 0x00, 0x00, 0x00, 0x00, 0;
#DAT = 1, 0x34, 0, 0x00439, 4, 0x00, 0x00, 0x00, 0x00, 0;
#DLT2 = 1, 0x38, 0, 0x0D639, 4, 0x17, 0x18, 0x80, 0x81, 2;
#DLT-data = 1, 0x38, 0, 0x0D639, 4, 0x80, 0x81, 0x82, 0x83, 2;
#DLT7k-data = 1, 0x38, 0, 0x0D639, 4, 0x82, 0x83, 0x84, 0x85, 2;
#EXB-2501 = 1, 0x28, 1024, 0x00442, 4, 0x00, 0x00, 0x00, 0x00, 0;
#EXB-8200 = 1, 0x28, 0, 0x08C79, 4, 0x00, 0x00, 0x00, 0x00, 0;
#EXB-850X = 1, 0x29, 0, 0x0CE39, 4, 0x14, 0x15, 0x8C, 0x8C, 1;
#Exa4200c = 1, 0x34, 0, 0x01639, 4, 0x63, 0x00, 0x00, 0x00, 1;
#Fujitsu_comp = 1, 0x21, 0, 0x18639, 4, 0x00, 0x00, 0x00, 0x09, 1;
#Fujitsu_half = 1, 0x21, 0, 0x0063B, 4, 0x00, 0x00, 0x00, 0x00, 0;
#Fujitsu_m248x = 1, 0x21, 0, 0x0C639, 4, 0x00, 0x00, 0x00, 0x00, 0;
#HP_DAT = 1, 0x34, 0, 0x19679, 4, 0x00, 0x00, 0x00, 0x00, 0;
#HP_DAT_3 = 1, 0x34, 0, 0x09639, 4, 0x00, 0x8C, 0x8C, 0x8C, 1;
#HP_half = 1, 0x23, 0, 0x0041D, 4, 0x01, 0x02, 0x03, 0xC3, 1;
#KENNEDY = 1, 0x22, 0, 0x0041D, 4, 0x01, 0x02, 0x03, 0x03, 1;
#LMS = 1, 0x20, 0, 0x0066B, 4, 0x00, 0x00, 0x00, 0x00, 0;
#M4_DATA = 1, 0x27, 0, 0x0049D, 4, 0x01, 0x02, 0x06, 0x06, 1;
#MT02 = 1, 0x14, 512, 0x00202, 4, 0x84, 0x05, 0x05, 0x05, 1;
#MetD = 1, 0x36, 0, 0x01639, 4, 0x00, 0x00, 0x00, 0x00, 0;
#NS20 = 1, 0x32, 512, 0x0C40A, 4, 0x00, 0x00, 0x00, 0x00, 0;
#QIC150 = 1, 0x15, 512, 0x00642, 4, 0x00, 0x00, 0x00, 0x00, 0;
#TANDB-2_5G = 1, 0x32, 0, 0x0D67B, 4, 0x00, 0x00, 0x00, 0x00, 0;
#TAND-8G-VAR = 1, 0x37, 0, 0x0963B, 4, 0xA0, 0xD0, 0xD0, 0xD0, 3;
#TANDBERG_MLR1 = 1, 0x32, 512, 0x0463A, 4, 0x00, 0x00, 0x00, 0x00, 0;
#TAND-50G-VAR = 1, 0x37, 0, 0x0963B, 4, 0xA0, 0xD0, 0xD0, 0xD0, 3;
#TAND_4100_QIC = 1, 0x32, 512, 0x0463A, 4, 0x00, 0x00, 0x00, 0x00, 0;
#TAND_4200_QIC = 1, 0x32, 512, 0x0463A, 4, 0x00, 0x00, 0x00, 0x00, 0;
#WANGTEK_6130 = 1, 0x2A, 0, 0x00659, 4, 0x00, 0x00, 0x00, 0x00, 0;
#WANGTEK_QC150 = 1, 0x16, 512, 0x00642, 4, 0x00, 0x00, 0x00, 0x00, 0;
#WangDAT = 1, 0x2B, 0, 0x00659, 4, 0x00, 0x00, 0x00, 0x00, 0;
#WangDAT = 1, 0x34, 0, 0x00679, 4, 0x00, 0x00, 0x00, 0x00, 0;
#WtQIC = 1, 0x32, 512, 0x0467A, 4, 0x00, 0x00, 0x00, 0x00, 0;
#T40 = 1, 0x32, 512, 0x161A, 4, 0x00, 0x00, 0x00, 0x00, 0;
#OnStream = 1, 0x36, 0x8000, 0x21658, 4, 0x00, 0x00, 0x00, 0x00, 0;
tape-config-list =
"HP Ultrium 1-SCSI", "HP Ultrium 1-SCSI", "LTO-data",
"HP Ultrium 2-SCSI", "HP_LTO", "HP-LTO2",
"DEC DLT2000", "Digital DLT2000", "DLT2k-data",
"Quantum DLT4000","Quantum DLT4000", "DLT4k-data",
"QUANTUM DLT7000", "Quantum DLT7000", "DLT7k-data",
"QUANTUM DLT8000", "Quantum DLT8000", "DLT8k-data",
"HP C9264CB-VS80","HP DLT vs80 DLTloader","HP_data1",
"QUANTUM SuperDLT1", "QUANTUM SuperDLT", "SDLT-data",
"TANDBERGSuperDLT1", "TANDBERG SuperDLT", "SDL-data",
"STK 9840", "STK 9840", "CLASS_9840";
DLT2k-data = 1,0x38,0,0x8639,4,0x17,0x18,0x80,0x81,3;
DLT4k-data = 1,0x38,0,0x8639,4,0x17,0x18,0x80,0x81,3;
DLT7k-data = 1,0x38,0,0x8639,4,0x82,0x83,0x84,0x85,3;
DLT8k-data = 1,0x77,0,0x1D639,4,0x84,0x85,0x88,0x89,3;
HP_data1 = 1,0x3a,0,0x8639,4,0x40,0x86,0x87,0x7f,0;
LTO-data = 1,0x7a,0,0x1d679,4,0x00,0x00,0x00,0x40,3;
HP-LTO2 = 1,0x7a,0,0xd639,4,0x00,0x00,0x00,0x42,3;
SDLT-data = 1,0x79,0,0x8639,4,0x90,0x91,0x90,0x91,3;
CLASS_9840 = 1,0x78,0,0x1d679,1,0x00,0;

name="st" class="scsi" parent="/pci@1e,600000/QLGC,qla@2/fp@0,0/st@w100000e00202dc0f,0" target=0 lun=0;
name="st" class="scsi" parent="/pci@1e,600000/QLGC,qla@2/fp@0,0/st@w100000e00202dc0f,2" target=0 lun=2;

#
#In case there are wide tape drives, one can use these targets
#
#name="st" class="scsi" target=8 lun=0;
#name="st" class="scsi" target=9 lun=0;
#name="st" class="scsi" target=10 lun=0;
#name="st" class="scsi" target=11 lun=0;
#name="st" class="scsi" target=12 lun=0;
#name="st" class="scsi" target=13 lun=0;
#name="st" class="scsi" target=14 lun=0;
#name="st" class="scsi" target=15 lun=0;
#name="st" class="scsi" target=5 lun=0;
#name="st" class="scsi" target=5 lun=1;
#name="st" class="scsi" target=6 lun=0;
#name="st" class="scsi" target=6 lun=1;
#name="st" class="scsi" target=8 lun=0;
#name="st" class="scsi" target=8 lun=1;
#name="st" class="scsi" target=9 lun=0;
#name="st" class="scsi" target=9 lun=1;
#name="st" class="scsi" target=10 lun=0;
#name="st" class="scsi" target=10 lun=1;
#name="st" class="scsi" target=11 lun=0;
# This line adds support for Fibre Channel Tapes
name="st" parent="fp" target=0;
=============================================
#ident "@(#)devlink.tab.sh 1.72 00/07/17 SMI"
#
# Copyright (c) 1998 by Sun Microsystems, Inc.
#
#
# This is the table used by devlinks
#
# Each entry should have 2 fields; but may have 3. Fields are separated
# by single tab ('\t') characters.
#
# The fields are:
#
# devfs-spec: a keyword-value set of devfs specifications, describing the set
# of devfs node entries to be linked.
#
# The keywords are:
#
# type - The devinfo node type (see for possible values)
#
# name - the devinfo node name (the part of a /devices entry that appears
# before the '@' or ':').
#
# addr - the devinfo node address part (the portion of the name between
# the '@' and the ':').
#
# minor - the minor-attributes (the portion of a /devices name after the
# ':').
#
# The keywords are separated from their valuse by an equals ('=') sign;
# keyword-value pairs are separated from each other by semicolons (';').
#
# dev name - the /dev name corresponding to the devfs node described by
# the devfs-spec field. This specification is assume to start rooted at
# /dev; THE INITIAL /dev/ SHOULD NOT BE SPECIFIED!
# The name can contain a number of escape-sequences to include parts of
# the devfs-name in the /dev/-name. These escape-sequences all start with
# a backslash ('\') character. The current sequences are:
#
# \D - the devfs 'name' field
#
# \An - the 'n'th component of the address field (n=0 means the whole
# address field)
#
# \Mn - the 'n'th component of the minor field (n=0 means the entire
# minor field).
#
# \Nn - a sequential counter, starting at n (a *single* digit, giving
# a starting range of 0 through 9).
#
# extra dev link - a few devices need a second link; that is, a second link
# pointing to the first link. This optional field specifies the /dev
# format of this second link. This entry can also use the above-described
# escape-sequences.
#
# Fields can be blank; seperated by single tab characters,
# Spaces are significant, and are considered part of a field. IN GENERAL THIS
# MEANS THERE SHOULD BE NO SPACE CHARACTERS IN THIS FILE!
# All fields must be present (even if blank)
#
#
# devfs-spec Dev-Namespec Extra-Link
#
type=ddi_pseudo;name=SUNW,rtvc;minor=ctl rtvc\M0
type=ddi_pseudo;name=SUNW,rtvc \M0
type=ddi_pseudo;name=sst;addr=w100000e00202dc0f,1; rsst\A1
kholikt
Super Advisor

Re: Need help for configuring MSL 6000 on Solaris 10 and SLES 9

Hi,

Thanks for the information but may I know "w100000e00202dc0f,1", Is this a world wide name use in the SAN switch.
abc
Kishan Kumar
Occasional Advisor

Re: Need help for configuring MSL 6000 on Solaris 10 and SLES 9

yes
kholikt
Super Advisor

Re: Need help for configuring MSL 6000 on Solaris 10 and SLES 9

Hi,

Sorry I am not very familiar with SAN. This is a port WWN. I can see many WWN there, even each port has their unique WWN. I suppose I should put in the port WWN that this library is connected
abc
Kishan Kumar
Occasional Advisor

Re: Need help for configuring MSL 6000 on Solaris 10 and SLES 9

yes the port wwn will do
kholikt
Super Advisor

Re: Need help for configuring MSL 6000 on Solaris 10 and SLES 9

w100000e00202dc0f,1

The number "1" in your /etc/devlink.tab at the back is this a Lun number. How can I find out my Lun number?
abc
kholikt
Super Advisor

Re: Need help for configuring MSL 6000 on Solaris 10 and SLES 9

still no luck

devfsadm: driver failed to attach: sst
Warning: Driver (sst) successfully added to system but failed to attach
abc
gzl
Honored Contributor

Re: Need help for configuring MSL 6000 on Solaris 10 and SLES 9

I have same problem,but hosts is IBM p550,AIX 5.3. On AIX 5.3 only tape drive device name,no changer.

cfgmgr: 0514-621 WARNING: The following device packages are required for
device support but are not currently installed.
devices.fcp.array
devices.fcp.changer
Configuration time: 1 seconds
# lsdev -Cc tape
rmt0 Available 06-08-01 Other FC SCSI Tape Drive
rmt1 Available 06-08-01 Other FC SCSI Tape Drive
rmt2 Available 09-08-01 Other FC SCSI Tape Drive
rmt3 Available 09-08-01 Other FC SCSI Tape Drive
# lsdev -Cc smc
# lsdev -Cc changer

wait for answer.....???


kholikt
Super Advisor

Re: Need help for configuring MSL 6000 on Solaris 10 and SLES 9

I can tell you it is hopeless. I am looking for this solution till now I give up already. I am putting a Wintel machine in the SAN to control the robotics arms. If you can switch to Netbackup please do so it has a better support than DP.
abc
Kishan Kumar
Occasional Advisor

Re: Need help for configuring MSL 6000 on Solaris 10 and SLES 9

HI ,

Regading MSL Robotic support on AIX 5.3 i would like to tell you that AIX 5.3 doesnot support Robotic control for MSL and its there in one of the IBM sites when i googled for it.so you have to do away with the drives only and not the robotic on AIX and as you knwo it AIX problem and no where related to MSL.

Regarding Netbackup i dont have much comment on it.The problem we discuss here is with configuration of Devices on operating systems and not the backup tool itself. As i ma using Dp from quite a long time i understand the advantage of DP an dam not aware much of NBU stuff.

Regading teh configuration of MSL on solaris , i suggest you please contact the SUN support guys for the same as i dint face much of a problem when confguring MSL on solaris using DP provided drivers.I suggest you redo the whole thing once again.

regards
kishan
kholikt
Super Advisor

Re: Need help for configuring MSL 6000 on Solaris 10 and SLES 9

The problem is something to do with the ssh remote execution

ssh user@hostname sar -u 1 5 > /tmp/sarcheck

The above line will only work if you run the script manually. It won't work if it was scheduled as cron.
abc

Re: Need help for configuring MSL 6000 on Solaris 10 and SLES 9

Hi Kishan,

Have you got the problem solved finally. If so, how? I am also running in to same problem and strugging for last two months.

Thanks

Champak

Re: Need help for configuring MSL 6000 on Solaris 10 and SLES 9

Now it looks much better. add_drv sst is not reporting any problem. But if I execute uma -ioctl to changer device it is not sensing.

# ./uma -ioctl /dev/scsi/changer/c3t100000E0022325E2d0
*** PROGRAM: UMA VERSION: HP OpenView Storage Data Protector A.05.50

*** (c) Copyright Hewlett-Packard Company 2004
*** License is restricted for use with licensed
*** HP OpenView Storage Data Protector products.

[Critical] From: UMA@search2.aetv.com "(unnamed)" Time: 03/17/06 15:51:26
[90:59] /dev/scsi/changer/c3t100000E0022325E2d0
Cannot open exchanger control device (Device type mismatch)



Any idea what is wrong?

dmesg shows the library as follows
Mar 17 15:50:11 search2.aetv.com sst: [ID 902828 kern.notice] sst11: found Changer device at tgt0, lun0
Mar 17 15:50:11 search2.aetv.com sst: [ID 902828 kern.notice] sst11: Vendor/Product ID = HP MSL6000 Series
Mar 17 15:50:11 search2.aetv.com scsi: [ID 799468 kern.info] sst11 at fp0: name w100000e0022325e2,0, bus address 31700
Mar 17 15:50:11 search2.aetv.com genunix: [ID 936769 kern.info] sst11 is /pci@1d,700000/SUNW,jfca@1/fp@0,0/sst@w100000e0022325e2,0


If I run cfgadm -al -o show_FCP_dev it shows

# cfgadm -al -o show_FCP_dev
Ap_Id Type Receptacle Occupant Condition
c3 fc-fabric connected configured unknown
c3::100000e0022325e2,0 med-changer connected configured unknown
c3::100000e0022325e2,1 tape connected configured unknown
c3::100000e0022325e2,2 array-ctrl connected unconfigured unknown
#


Kishan Kumar
Occasional Advisor

Re: Need help for configuring MSL 6000 on Solaris 10 and SLES 9

NOTE On Solaris systems, (especially in case of Solaris 64-bit), links to the
SCSI control device (picker) are not always created automatically. In this
case, create symbolic links. For example:
ln -s /devices/pci@1f,4000/scsi@3,1/sst@4,1:character
/dev/rsst4
You can use the Data Protector uma utility to verify the device. To
check the picker of the SCSI Exchanger device from the previous
example (using the SCSI port 4), enter:
echo â inqâ |/opt/omni/lbin/uma -ioctl /dev/rsst4
The picker must identify itself as a SCSI-2 device library. The library
can be checked by forcing it to initialize itself. The command is:
echo â initâ |/opt/omni/lbin/uma -ioctl /dev/rsst4
Make sure you use Berkeley-style device files, in this case,
/dev/rmt/ohb (not /dev/rmt/0h)for the exchanger drive and
/dev/rsst4 for the SCSI control device (picker).

The baove example is for a scsi device.
in case of a Fc device

/devices/pci@1f,4000/scsi@3,1/sst
{wwn number}:character
/dev/rsst{wwn number}

Re: Need help for configuring MSL 6000 on Solaris 10 and SLES 9

Finally I could solve the problem. Configuration of NS-E1200 router was not correct and I had to correct the mapping.

Thanks Kishan for giving me an idea about sst entry for FC device (which is not available in DP manual)

BTW, are you using default st.conf for LTO3? It has got entries for LTO1 and LTO2. However, I have got it from HP site and added to st.conf. Need more testing.

Champak
kholikt
Super Advisor

Re: Need help for configuring MSL 6000 on Solaris 10 and SLES 9

Hi Kishan,

Need your help. Here is my "cfgadm -al -o show_FCP_dev" output.

c4 fc-fabric connected configured unknown
c4::100000e00222a8f1,0 med-changer connected configured unknown
c4::100000e00222a8f1,1 tape connected configured unknown

I have attached my st.conf and sst.conf look like. I haven't apply the changes yet as wake for approval of downtime.

Currently I have a very strange problem, the MSL 5030 tape drive cannot archive it performance and the compression doesn't work at all. For example the backup data is 280G but the MSL tape drive after backup 100GB it will ask for more tape. But for the same server I have another standalone ultrium 2 scsi attached, using the same LTO1 catrdge it can backup 280GB of data.

mt -f /dev/rmt/1mbn config
"HP Ultrium 1", "HP Ultrium LTO", "CFGHPULTRIUMLTO";
CFGHPULTRIUMLTO = 2,0x3B,0,0x18659,4,0x40,0x40,0x40,0x40,3,60,300,600,1200,600,600,18000;

mt -f /dev/rmt/2mbn config
"HP Ultrium 2", "HP Ultrium LTO 2", "CFGHPULTRIUMLTO2";
CFGHPULTRIUMLTO2 = 2,0x3B,0,0x18619,4,0x40,0x40,0x42,0x42,3,60,300,600,1200,600,600,18000;
abc
kholikt
Super Advisor

Re: Need help for configuring MSL 6000 on Solaris 10 and SLES 9

I am getting a little bit closer now at least I can see the sst but I still cannot control the arm as I still getting the error message

Cannot open exchanger control device (Device type mismatch)

I have attached my st.conf sst.conf and my devlink.tab
abc
alims
Occasional Contributor

Re: Need help for configuring MSL 6000 on Solaris 10 and SLES 9

Dear Kishan

I'm also having IBM AIX v5.3 and MSL6030 FC Library with HP Ultrium 2 LTO SCSI Drives. AIX does detects this drives as Other FC SCSI Tape Drive (OST) - rmt1 and rmt2 with connection seetings as 2 nd 3 (where as Drive SCSI IDs are 1 and 2).

rmt0 is an directly attached scsi drive and is working fine.

When cfgmgr is executed it does report devices.fcp.array and devices.fcp.changer not available.

My problem is tar,dd or cpio none works with the tape. Could you pls. throw some more light on how did you manage to make the drives working in AIX.

Regards
Ali