StoreEver Tape Storage
1752648 Members
5679 Online
108788 Solutions
New Discussion юеВ

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

 
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