Solaris 10 StorEdge L1000

I am looking for information on getting a L1000
working with Solaris 10 on a e450.
Driver setup and any administration commands for
configuration, control and monitoring etc.
I have the L1000 users manual but it does not cover
OS level config. I am also aware of LibMON 2.0, but is
this support on solaris 10, or are there utilities built into
the OS now(something like luxadm)?
Thanks!
Mike Spenard

Anyone?

Similar Messages

How to remove / replace Tape Drives from SUN StorEdge L1000 ? Need document

I have the User's guide but it does not provide any info. My sunsolve access does not allow me to see anything. Is there somewhere I can find this information ? Thank you

you have the users guide and have looked at page 27?
http://dlc.sun.com/pdf/805-4823-10/805-4823-10.pdf
seems kinda easy... unless you can't open the doors...
you might try this page...
http://www.sunshack.org/data/sh/2.1/infoserver.central/data/syshbk/Systems/L1000/docs.html
keep trying..
haroldkarl

L1000 lost key

Does anyone know if/where I can get a key for my L1000?
Thanks,
Susan

can't seem to find my Sun Key list... but it is the same as the SS1000.... 330-1651..
here is the link for the L1000 parts http://sunsolve.sun.com/handbook_pub/Systems/L1000/component s.html
when I searched the Sun site, I couldn't raise the Store...
might try Ebay, my friends at rescue@sunhelp.org ...
I can just hear it now... just ask your IT people.... if it is that important, I'll try to find one... are you in the US ?
I guess Seattle is in the US... I am in Oregon...
good luck,
haroldkarl
SS1000 / SC2000      330-1651
StorEdge L400           330-1651
StorEdge L1000      330-1651
StorEdge L11000      330-1651

SG-XPCI2FC-QF2

Is there a difference between QLogic QLA2342 and the sun card SG-XPCI2FC-QF2

The Sun version of the card has firmware that has been developed for use with Sun Solaris and StorEdge products ( arrays, switches etc. ). The firmware has a different lifecycle to the Qlogic firmware also and is released in patch form through Sun solve.

Install SUN StorEdge L280 to Solaris 10 x86

Hi, i need help with install & configure SUN StorEdge L280. I have SOLARIS 10 x86 platform on HP DL 380 g3. I need help with this. I dont understend what with this, what drivers is need... On sparc is all ok with veritas netbackup, but on x86...any help?thanks

i need help with install & configure SUN StorEdge L280. I have SOLARIS 10 x86 platform on HP DL 380 g3. I need help with this. I dont understend what with this, what drivers is need... On sparc is all ok with veritas netbackup, but on x86...any help?thanks
The L280 (or HP SureStore Autoloader 718) contains a DLT7000 drive. There is no reason why the generic SCSI tape driver doesn't support these drives.
If you're asking for software to control the autoloader, a similar software like Veritas NetBackup is required. Veritas supplies a replacement driver.
Now I see why your L280 doesn't work with your HP server. The L280 requires a HVD (High Voltage Differential) SCSI controller. The standard SCSI interface is SE (Single Ended) or LVD (Low Voltage Differential). Neither SE nor LVD are compatible with HVD. You won't see the device and can even damage the device and/or the controller.
Get a HVD SCSI controller (Symbios SYM22802, Part-No 375-0006) or Adaptec AHA-2944UW (not AHA-2940UW which is SE!!).
The Sun labeled HP Autoloaders (StorEdge L9, L280) use HVD SCSI while the original ones (SureStore 1/9, 718) use LVD or SE SCSI.
Michael
Robert,
any update ?
Message was edited by:
MAALATFT

Solaris V240 and StorEdge Multipack

I have an issue with a Solaris V240.
Is it possible connect a Multipack StorEdge 599-2061-01 on external scsi port of this Server?
I have tryed the connection but on boot I have an error:
Testing /pci@1c,600000/scsi@2,1
ERROR : All register test failed
SUMMARY : Obs=0x00000000 Exp=0x00001000 XOR=0x00001000 AND-Mask=0x78c2749b Addr=0xfedc0000
DEVICE : /pci@1c,600000/scsi@2,1
SUBTEST : selftest:scsi-reg-test
MACHINE : Sun Fire V240
SERIAL# : 66969949
DATE : 08/27/2010 15:38:01 GMT
CONTR0LS: diag-level=max test-args=
Error: /pci@1c,600000/scsi@2,1 selftest failed, return code = 1
Testing /pci@1e,600000/isa@7/serial@0,2e8
I have used a cable DEL partnumber 1H181 HD68 to VHDCI
Could you please help me?
Thanks.
Edited by: mautig on Aug 31, 2010 1:34 PM

I'ld believe that it should work, if the KVM switch was on and the Sun server selected when the Sun server was powered on, but thats my guess..

Solaris 9 and Storedge C2

Hello,
i have a V240 Server witch an library Storedge C2 attached. I receive this entries in the /var/adm/messages:
Jan 14 06:30:21 BCKMAL genunix: [ID 408822 kern.info] NOTICE: glm1: fault detected in device; service still available
Jan 14 06:30:21 BCKMAL genunix: [ID 611667 kern.info] NOTICE: glm1: got SCSI bus reset
Jan 14 06:30:36 BCKMAL scsi: [ID 107833 kern.warning] WARNING: /pci@1c,600000/scsi@2,1 (glm1):
Jan 14 06:30:36 BCKMAL SCSI bus parity error - illegal phase

Hi,
I have a Sun V240 and a C2 running under Solaris 10 without any problem.
Now this does not help you, but I Had an L20 before I got the C2 and at some point in time
had similar problems like you have.
Sun replaced the HBA to no avail, drive in the L20 was replaced and all firmware updated (drive + robot). That fixed it.
In the end it was probably some firmware problem.
So in your case it could still be anything i am afraid.
Regards,
Nico

StorEdge 3320 supported on Solaris 10 x86?

Hello,
I cannot install the SUNWsscs package on my X4200 SunFire that is running Solaris 10 for x86. It says it is not the right package, that the SUNWsscs is only for SPARC systems. Does anyone know the correct package to use to install the CLI?
Thanks,
Dan

The x86 version of the software can be downloaded from the URL below:
http://www.sun.com/download/products.xml?id=4436c6a0

Solaris 10 support on Sun Storedge 6120/6020

Hi ,
I have bought a SE6120 arrays attach to two Sun Fire 4800 as cluster
shared storage with Solaris 9 OS. I intend to upgrade the OS to Solaris 10. But after find the information at sunsolve.sun.com, it not mention about wether Solaris 10. Hope somebody will provide me solution..
Thanks in advance !!
Message was edited by:
Mohd.Suhaimi

The array is supported with Solaris 10. The noticeable change from prior OS is that the SAN drivers and packages are included with the base OS. You do not need to add anything as you did for Solaris 9 and 10.

StorEdge L9 Autoloader on Solaris 8

Hi,
I recently found a StorEdge L9 Autoloader with Quantum DLT8000 unused in my organisation and trying to get it work.
The Autoloader looks to be working and I can run manual UFSDUMPS onto the tape. However, I have problems all over to get MTX working with the Autoloader working.
I installed MTX from sunfreeware.com and have edited the /kernel/drv/sgen.conf file to reflect as follows:
device-type-config-list="changer","sequential";
inquiry-config-list= "*", "*";
and have enabled all lines like
name="sgen" class="scsi" target=0 lun=0;
However, after a recofigure reboot I cannot find the /dev/scsi/changer/ being created. However, I can see /dev/scsi/sequential/ being created.
The probe-scsi-all from OBP shows as follows:
ok probe-scsi-all
/pci@1f,2000/scsi@1,1
Target 0
Unit 0 Disk Symbios StorEDGE A1000 0205
Unit 1 Device type 20 Symbios StorEDGE A1000 0205
Unit 2 Device type 20 Symbios StorEDGE A1000 0205
Unit 3 Device type 20 Symbios StorEDGE A1000 0205
Unit 4 Device type 20 Symbios StorEDGE A1000 0205
Unit 5 Device type 20 Symbios StorEDGE A1000 0205
Unit 6 Device type 20 Symbios StorEDGE A1000 0205
Unit 7 Device type 20 Symbios StorEDGE A1000 0205
/pci@1f,2000/scsi@1
Target 4
Unit 0 Removable Tape QUANTUM DLT8000 0114
/pci@1f,4000/scsi@3,1
/pci@1f,4000/scsi@3
Target 0
Unit 0 Disk FUJITSU MAB3045S SUN4.2G1705
Target 1
Unit 0 Disk SEAGATE ST318404LSUN18G 4203
Target 6
Unit 0 Removable Read Only device TOSHIBA XM5701TASUN12XCD2395
As you can see, the Quantum DLT8000 shows up but nothing at all about the autoloader. I'm not sure if it would be listed there but I've googled a lot and can find people say it should be.
The SCSI IDs are "0" for Autoloader and "1" for Drive. The Autoloader and the A1000 are conncted to the same Differential SCSI card on the server. However, disconnecting the A1000 doesn't help as well.

Managed to get this problem fixed just when I was at the end of the rope.
I realised once when there was a problem with a external SCSI tape drive on a DELL 2850 (RHEL3), I have to shutdown the server and the Tape drive, disconnect all the cables to drain any static energies in there and reconnect the cables and start the server wich eventually fixed the problem.
As a last resort, I tried this by disconnecting all the SCSI cables and the switching off the devices, power-off the server and leave for a few minutes and restarted with the autochanger connected to the port where the A1000 was connected and bingo, probe-scsi-all was able to see the autoloader and then the tape drive. Shutdown again and connected the A1000 to the port where the L9 was connected earlier and all was fine.
Rebooted the server a few times and all was fine. Edited the /kernel/drv/sgen.conf file and rebooted the server and I can see the "/dev/scsi/changer" and MTX does respond.
Hope this helps someone who has a similar problem.

StorEdge 3510: can't newfs on Solaris 10

We have Solaris 10 with ssconsole and all relevant drivers and software installed. Using ssconsole I created three logical drives. format sees them and I can successfully repartition all three disks:
AVAILABLE DISK SELECTIONS:
0. c1t0d0 <SUN72G cyl 14087 alt 2 hd 24 sec 424>
/pci@9,600000/SUNW,qlc@2/fp@0,0/ssd@w500000e010d77c01,0
1. c1t1d0 <SUN72G cyl 14087 alt 2 hd 24 sec 424>
/pci@9,600000/SUNW,qlc@2/fp@0,0/ssd@w500000e010d828d1,0
2. c2t42d0 <SUN-StorEdge3510-327R cyl 4391 alt 2 hd 255 sec 255>
/pci@8,600000/SUNW,qlc@1/fp@0,0/ssd@w226000c0ffa7fe9d,0
3. c4t40d0 <SUN-StorEdge3510-327R cyl 6588 alt 2 hd 255 sec 255>
/pci@8,600000/SUNW,qlc@2/fp@0,0/ssd@w216000c0ff87fe9d,0
4. c4t40d1 <SUN-StorEdge3510-327R cyl 6588 alt 2 hd 255 sec 255>
/pci@8,600000/SUNW,qlc@2/fp@0,0/ssd@w216000c0ff87fe9d,1
When I do newfs on any of the new disks partition I get this error:
bash-3.00# newfs /dev/rdsk/c2t42d0s0
newfs: construct a new file system /dev/rdsk/c2t42d0s0: (y/n)? y
There is no block size that can support this disk
Any help?

Upgrading the 3510 firmware to 4.x may help with this issue. I can't see what your logical drive size is, but I suspect that it is too big for that drive geometry. The 4.x firmware reduces the geomtry so that newfs doesn't complain.
With Solaris 9 newfs complains, but gives you some hints as to what you can do to get around the limitation. When I swithced to 4.11 (and 4.13) newfs stopped complaining.

2nd StorEdge 3510 not visible to OS solaris 9

Added 2nd 3510 array via daisy chain to existing 3510. First one has been in operation, now after adding the second one the OS does not see the new LUNS. One logical drive 4.2 TB with 5 partitions each under 900 GB. Thought that maybe a reboot -- -r might fix it, but not true. Mapped the LUNS to each partition. Read about the changing the geometry for logical drives larger than 253 GB. Won't that change the geometry on the existing 3510 disks. Any advice is much appreciated.

You said you installed the necessary "san packages, san patches". Are these the packages to be found in "Sun StorEdge [tm] 3000 Family Storage Products--Related Software V2.x"? I have worked with 3310s and these are not SAN, but directly attached and need the above drivers to work.
Cheers,
Arty

StorEdge 3510FC - cannot see related SES in Solaris 9 or Solaris 10 (b63)

I used with success SE 3510FC on Solaris 8.
When I tried to use it on Solaris 10, I discovered that SES cannot be seen by OS. In Solaris 8 if I have no logical drives LUN mapped, then SES device is present in /dev/es and I can sccli on it. On the other hand, in Solaris 10 I can see the damn device only if something is LUN mapped as LUN0. (and I see it in /dev/rdsk ...) but never saw an entry for the enclosure in /dev/es.
In Solaris 8 I use a custom method to automaticaly install 3510FC at system installation time via JumpStart and misc scripts after... works perfect.
In Solaris 10 I cannot do this because it needs operator intervention - to create and LUN map LUN0. However the main problem is that SES entry in /dev/es is not present.
Any ideas?
Thank you very much !
Adrian.

I used with success SE 3510FC on Solaris 8.
When I tried to use it on Solaris 10, I discovered that SES cannot be seen by OS. In Solaris 8 if I have no logical drives LUN mapped, then SES device is present in /dev/es and I can sccli on it. On the other hand, in Solaris 10 I can see the damn device only if something is LUN mapped as LUN0. (and I see it in /dev/rdsk ...) but never saw an entry for the enclosure in /dev/es.
In Solaris 8 I use a custom method to automaticaly install 3510FC at system installation time via JumpStart and misc scripts after... works perfect.
In Solaris 10 I cannot do this because it needs operator intervention - to create and LUN map LUN0. However the main problem is that SES entry in /dev/es is not present.
Any ideas?
Thank you very much !
Adrian.

New to Solaris administration - Need some help with some issues

Hello all,
I am a new to Solaris administration and need some assistance with a few things. I was going to make separate posts but decided it would be easy to keep track of in one. I really do not know much about the OS but I do have a little Linux background so that might help me out. I am going to number my problems to keep them sorted, so here we go.
The machine:
Sunfire V880
4x 73GB HDs
PCI dual fiber channel host adapter
Attached RAID array:
Sun StorEdge T3 Array with 9x 73GB HDs
Sun DDS4 Tape Drive in a Unipack
OS: Solaris 5.10
Updates: Updated everything except 2 patches (Updating is a real pain isn't it? At least it seems that way to me.)
1. So I might as well start with the update issues! These 2 updates will not install:
-PostgreSQL 8.2 source code, (137004-02)
Utility used to install the update failed with exit code {0}.
-Patch for mediaLib in solaris, (121620-03)
Install of update failed. Utility used to install the update is not able to save files. Utility used to install the update failed with exit code 4.
No idea why the PostgreSQL update is not working, but the medialib patch seems to not have enough hard drive space.
2. Where are all the drives? I don't know how to find the RAID box or the other 3 internal hard drives. When I installed the OS, I think I installed it on only one hard drive and that might be part of the reason why the medialibe update above says that I don't have enough space.
3. I probably need more space for the OS and updates, is there a way to "add" space onto the hard drive that currently is running the OS?
3. Once I see the other hard drives I wish to combine them to make a RAID 0 and RAID 5 array, how do I go about doing that?
4. How can I find/see the tape drive?
5. Does my swap space really need to be 64GB? I know the book I have read suggests it, but I only made it 5GB because it didn't seem to make sense to make it 64GB.
Thank you in advance for the help. I know these are a lot of questions to ask but please go easy on me :)
rjbanker
Edited by: rjbanker on Mar 7, 2008 8:21 AM

SolarisSAinPA*
1.
-PostgreSQL 8.2 source code, (137004-02)
Utility used to install the update failed with exit code {0}.
Exit code 0 means there were no errors. When you run showrev -p 137004-02, does your system show that the patch is installed? You can check the log for a particular patch add attempt in /var/sadm/patch/+patch_num_rev+1- A bunch of stuff shows up, here is a portion (I am not entirely sure what it means, there must be a least a page of stuff like this):
Patch: 121081-08 Obsoletes: Requires: 121453-02 Incompatibles: Packages: SUNWc cccrr, SUNWccccr, SUNWccfw, SUNWccsign, SUNWcctpx, SUNWccinv, SUNWccccfg, SUNWcc fwctrl
Patch: 122231-01 Obsoletes: Requires: 121453-02 Incompatibles: Packages: SUNWc ctpx
Patch: 120932-01 Obsoletes: Requires: Incompatibles: Packages: SUNWcctpx
Patch: 123123-02 Obsoletes: Requires: Incompatibles: Packages: SUNWccinv
Patch: 121118-12 Obsoletes: Requires: 121453-02 Incompatibles: Packages: SUNWc smauth, SUNWppror, SUNWpprou, SUNWupdatemgru, SUNWupdatemgrr, SUNWppro-plugin-su nos-base
2.
Where are all the drives? I don't know how to find the RAID box or the other 3 internal hard drives. When I >installed the OS, I think I installed it on only one hard drive and that might be part of the reason why the >medialibe update above says that I don't have enough space.
When you run format command, how many drives are listed? Identify your root drive (compare with output of df command you ran earlier) Please post here.2. Output of df-hk, looks like I ran out of room. Should I just go ahead and reinstall the OS?
Filesystem size used avail capacity Mounted on
/dev/dsk/c1t0d0s0 5.9G 5.4G 378M 94% /
/devices 0K 0K 0K 0% /devices
ctfs 0K 0K 0K 0% /system/contract
proc 0K 0K 0K 0% /proc
mnttab 0K 0K 0K 0% /etc/mnttab
swap 42G 1.3M 42G 1% /etc/svc/volatile
objfs 0K 0K 0K 0% /system/object
/platform/sun4u-us3/lib/libc_psr/libc_psr_hwcap1.so.1
5.9G 5.4G 378M 94% /platform/sun4u-us3/lib/libc_psr.so.1
/platform/sun4u-us3/lib/sparcv9/libc_psr/libc_psr_hwcap1.so.1
5.9G 5.4G 378M 94% /platform/sun4u-us3/lib/sparcv9/libc_psr.so.1
fd 0K 0K 0K 0% /dev/fd
swap 42G 1.1M 42G 1% /tmp
swap 42G 32K 42G 1% /var/run
/dev/dsk/c1t0d0s7 46G 47M 46G 1% /export/home
3. So I guess the general consensus is to reinstall the OS, is that correct?
4. There is nothing in \dev\rmt, and unfortunately I don't have a tape to test it with!
5. I guess 5GB will be ok for what we do.
Alan.pae*
1. I think the above text might explain why it failed, although I don't know how to correct it.
2. Output of format:
# mount
/ on /dev/dsk/c1t0d0s0 read/write/setuid/devices/intr/largefiles/logging/xattr/onerror=panic/dev=1d80008 on Mon Mar 10 10:56:51 2008
/devices on /devices read/write/setuid/devices/dev=4dc0000 on Mon Mar 10 10:56:19 2008
/system/contract on ctfs read/write/setuid/devices/dev=4e00001 on Mon Mar 10 10:56:19 2008
/proc on proc read/write/setuid/devices/dev=4e40000 on Mon Mar 10 10:56:19 2008
/etc/mnttab on mnttab read/write/setuid/devices/dev=4e80001 on Mon Mar 10 10:56:19 2008
/etc/svc/volatile on swap read/write/setuid/devices/xattr/dev=4ec0001 on Mon Mar 10 10:56:19 2008
/system/object on objfs read/write/setuid/devices/dev=4f00001 on Mon Mar 10 10:56:19 2008
/platform/sun4u-us3/lib/libc_psr.so.1 on /platform/sun4u-us3/lib/libc_psr/libc_psr_hwcap1.so.1 read/write/setuid/devices/dev=1d80008 on Mon Mar 10 10:56:50 2008
/platform/sun4u-us3/lib/sparcv9/libc_psr.so.1 on /platform/sun4u-us3/lib/sparcv9/libc_psr/libc_psr_hwcap1.so.1 read/write/setuid/devices/dev=1d80008 on Mon Mar 10 10:56:50 2008
/dev/fd on fd read/write/setuid/devices/dev=50c0001 on Mon Mar 10 10:56:51 2008
/tmp on swap read/write/setuid/devices/xattr/dev=4ec0002 on Mon Mar 10 10:56:52 2008
/var/run on swap read/write/setuid/devices/xattr/dev=4ec0003 on Mon Mar 10 10:56:52 2008
/export/home on /dev/dsk/c1t0d0s7 read/write/setuid/devices/intr/largefiles/logging/xattr/onerror=panic/dev=1d8000f on Mon Mar 10 10:56:57 2008
3. Judging by the above text I will be doing a reinstall huh?
4. Actually I am not familiar with tape backups let alone solaris backup apps! Any suggestions? (Preferably free, have to cut down on costs.)
5. No comment
Thanks for the help, hope to hear from you again!
rjbanker

StorEdge 3510 FC Array Transport/Hard Errors

We have a StorEdge 3510 connected to a V440 running Solaris 9. /var/messages indicates no errors however iostat -e shows hard and transport errors that increment continuously. If I access the controller on the 3510 I can see transport errors when I look at the Fibre Chanel errors on the drive side. The system contains 2 controllers in redundant mode, however we only have one FC cable path to the HBA on the V440. I have replaced the fibre cable to the HBA, the GBIC and swapped the controllers all of which have not resolved the issue. I have also had a case open with Sun for 2 months and they have no idea.
What could be causing these errors?

I presume that by now you have sorted this problem, but in case not, 512Gb is the maximum logical drive size when the i/o optimisation is random.
On the max disk size, I read somewhere that VxFS might help.
I found your query when looking for help on directing StorEdge events to the syslogd on our central loghost - which I still haven't found out how to do!?

Solaris 10 StorEdge L1000

Similar Messages

Maybe you are looking for