Sun StorEdge 3510

Dears,
Good day,
I need your support to guide me to configure Sun StorEdge 3510. I have 24 Disks and single controller. I is connected to one host. I want to configure it with the most biggest storage. I want to implement RAID 5 on 11 disks on the first enclosure and the same to the second enclosure with two disks spare each one in the same enclosure.
Can you guide me throw this?
Thanks a lot.

Wow, it took me about 5 hours to set mine up from scratch and I'm a pretty strong storage guy. Here's an overview of what I did. Most of the info is in the 3510 documentation.
Step 1 is connectivity. Get your host to see the 3510 (FC).
Step 2 - use the cli utilities to setup the IP address on the controller (in-band).
Step 3 - ssh in, setup the RAID and presentation of the luns
Step 4 - rescan on the hosts to see the new luns

Similar Messages

SUN StorEdge 3510 MIBs

Hi all,
Does anybody know, where to get MIB files for SUN storage devices (in particular, StorEdge 3510) ? My company have a few 3510, and as long as I'm is a developer and maintainer of "self-made" monitoring system for all network, power, storage & other devices and servers, I want to include support for monitoring SUN storage devices in it.
Thanks, Oleg.

Hello,
a few days ago a subscriber of the Sunmanagers list lost his "patience" and posted a checklist about the resources to consult before posting on the Sunmanagers list. This was due to the increasing number of inappropriate posts.
The Sunmanagers list is for timecritical problems.
These forums are not offical Sun Support, all contributors just volunteer.
I did a google search (substitute your favorite search machine) with the query "MIB +StorEdge", the third hit was a site that offered MIBs for free.
It's really recommended to research before posting on these forums.
Michael

Sun StorEdge 3510 ADD new disks

I have working array StorEdge 3510 connected to SunFire V490.
What I need to do is to ADD another 4 disks and split them into a RAID 5.
For that reason im going to connect directly to array.
Does anyone can tell me what steps should I take to attach these disks and make them visable under Solaris 10 ?
Let me say again - array is working with 7 other disks and its fine. all of them are visable in Solaris - I NEED TO ADD another 4.

Wow, it took me about 5 hours to set mine up from scratch and I'm a pretty strong storage guy. Here's an overview of what I did. Most of the info is in the 3510 documentation.
Step 1 is connectivity. Get your host to see the 3510 (FC).
Step 2 - use the cli utilities to setup the IP address on the controller (in-band).
Step 3 - ssh in, setup the RAID and presentation of the luns
Step 4 - rescan on the hosts to see the new luns

Sun Storedge 3510 FC - NVRAM CRC ERROR

Hi,
I installed the latest patch for this issue. patch installed on 3510 FC storedge - 113723-20. Still the problem persist. How can I resolve this issue.
Is there any additional patch required for this issue.
While rebooting the stroredge I used to get an error messgae like "NVRAM CRC ERROR - nvram must be reinitialized - replace controller" and type to continue:
Regards,
Senthilkumar

Hi,
The patch readme seems to suggest this is a firmware update, have you applied the new firmware to the array? Have you checked to see if the Host FC ports also have a firmware update available?
Stuart.

Storedge 3510 failover configuration with 1 host

I people.
I'm new to the storedge configuration.
I have a Sun storedge 3510 - 2 controllers with 2 x host port fc and 1x drive port each.
I want to do a simple configuration - connect 1 host to the storedge with failover.
It's correct to connect the 2 controllers using the drive port - because i want failover?
It's possible to use only 1 pci single FC adapter in the machine?
I will connect the machine with the storedge usinge 1 fibre cable,
I will use the host port FC1. And to do the failover I will connect the 2 controllers
using the drive port fc3 e fc2. - THIS IS CORRECT?
My problem is who to connect the cables and who to configure the storedge. I'm
already connected to the COM Port.
Another thing i have in the first controller amber light - this is a hardware problem?
And wath is the best configuration to use with 3510 storedge, one host, and failover?
Thank you. I need this help for now.. Please.

Isn't it wonderful when people respond?
I, too, am running into the same scenario. We have a single 3510FC that is connected to a single host through two controller cards. The drives are configured as a single logical drive under RAID-5. We want to have this configuration multi-pathed for redundancy, not throughput, even though controller cards NEVER fail. [sarcasm] We will be using Veritas VxVM DMP for redundancy.
Unfortunately, I can only ever see the logical drive/LUN on one controller. The main connection is channel 0 of the primary controller. Whenever I try to configure it to simultaneously be on channel 5 of the secondary controller, the 3510 won't let me do it. I can't figure out how to get the LUN to be assigned to two host channels when one is on the primary controller and one is on the secondary controller.
I find this to be absurd. Controllers fail. That's all that there is to it. Yet the design of the 3510 (and the 3310 as well) seem to fight like hell whenever you want to spread the logical drives across physical controllers.
What's the solution to this one, guys?

StorEdge 3510 disk array & SunMC

Hi
I have a question regarding Sun StorEdge 3510 & SMC. I want to have notifications about hdd problems, cache or controller faults. I know that I can install StorADE and send messages to SMC. Is there any other way to have 3510 notifications in SMC withouht hiring StorADE?
Regards
Paul

Hello,
You can use following way to monitores 3510 Raid array :
Install packages on the 3510 connected server
system SUNWsccli Sun StorEdge(tm) 3000 Family CLI
system SUNWscsa Sun StorEdge(tm) Diagnostic Reporter daemon
system SUNWscsd Sun StorEdge(tm) Configuration Service Agent
application SUNWscsu Sun StorEdge(tm) Configuration Service Console
system SUNWscui Sun StorEdge(tm) Diagnostic Reporter console
This provide ssconsole binary. Start it and assign your 3510 Raid ctrl to send alarms to one Solaris host.
Exact procedure (account creation, etc...) to do so should be present somewhere on docs.sun.com
Now, each time an event occurs on the 3510, a log will appears with SUNWscsd... blablabla into /var/adm/messages :
/var/adm/messages.0:Jun 26 15:48:11 PNMSSS082 SUNWscsdMonitor[522]: [ID 163373 daemon.error] [SUNWscsd 0x030B2007:0x00FFFF00 Informational] <rctrl2041> Logical Drive 0(ID=6327904A, RAID 5), Rebuild Completed. Informational message. Replace defective drive with new drive. (Mon Jun 26 15:22:48 2006) {Unique ID#: 07e60a}
Use SMC agent log file scanning to monitor trap with this string "SUNWscsd"
Hope this will help.
Regards,
Damien

Sun StorEdge[TM] 3510/3310/3511

Dear
What does the "2(3)" mean in the show disks output under the channel ID (Ch) for Sun StorEdge[TM] 3310/3510/3511
:)Thanks
Mohammed Tanvir

Hi
2(3) means there are two channels configured for the storedge 2 and 3 or I should say that it is in redundant mode. And at present control is with 2nd channel.
Regards

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!?

X4200 + RHEL4 32bit + SG-XPCI1FC-QLC + STOREDGE 3510

Hi,
this is my configuration :
- sun x4200
+ SG-XPCI1FC-QLC
+ STOREDGE 3510
- RHEL 4 32bit (CENTOS)
This is an application server that have to run cobol applications connected to oracle
and for this i must use a 32 bit system (rtsora for cobol don't build on 64).
But i have a problem with the storedge i can't see any partition mapped to this host!
If i use the 64 bit os version with kernel 2.6.9-22.ELsmp all work fine on the same at 32
the qla6312 kernel driver load correctly but i can't see any attached scsi device.
Any ideas ?

Hi, thanks for response,
no i've not compiled a new kernel i installed the 32bit release of RHEL-4 (because i have a cobol application that must work a 32).
I have 2 server identical: 2 x4200 the first with RHEL-4 64bit the second RHEL-4 32bit the second don't work but if i made a kernel update on RHEL-4 64bit with the new one the controller stop to work!
I havo no idea.

Performance to expect from a StorEdge 3510

Hi all,
Really need some advice regarding a 3510FC array. We currently have a dual-controller setup with a RAID array + JBOD expansion. Each array has 10 drives, which we've setup as two RAID5 LD's as 8 data, 1 parity + 1 hotspare. The array firmware is 4.15.
Performance isn't good. We can't seem to get anything better than 65Mb/s, (based upon "mkfile 2g testfile"). Whilst I appreciate this is a far from scientific test, our HDS AMS200 performs this little task in 18secs, as opposed to 32secs on the 3510.
In the real world, Oracle is running like a dog on it :-(
I hoping that it's just our RAID5 setup that is not good, but before I consider the pain of -- backup data, reconfigure LD's, restore data -- I want to know if really the 3510 should be performing better.
If I re-jig the array with RAID1 Luns, + perhaps sequential for redo logs, should I be able to get some decent throughput from this array?
All help appreciated!

Here's our config ...
Sun StorEdge 3000 Family CLI
Copyright 2002-2005 Dot Hill Systems Corporation.
All rights reserved. Use is subject to license terms.
sccli version 2.3.0
built 2006.03.15.09.49
build 12 for solaris-sparc
* inquiry-data
Vendor: SUN
Product: StorEdge 3510
Revision: 415F
Peripheral Device Type: 0x0
NVRAM Defaults: 415F 3510 S470F
Bootrecord version: 1.31H
Serial Number: 0A7805
Page 80 Serial Number: 0A78055F4B554305
Page 83 Logical Unit Device ID: 600C0FF0000000000A78055F4B554305
Page 83 Target Device ID: 206000C0FF0A7805
IP Address:
Page D0 Fibre Channel Address: 05 (id 255)
Page D0 Node Name: 206000C0FF0A7805
Page D0 Port Name: 256000C0FFCA7805
Ethernet Address: 00:C0:FF:0A:78:05
Device Type: Primary
unique-identifier: A7805
controller-name: "R2 3510"
* network-parameters
ip-address:
netmask: 255.255.255.224
gateway:
mode: static
* host-parameters
max-luns-per-id: 32
queue-depth: 1024
fibre-connection-mode: point-to-point
inband-management: enabled
* drive-parameters
spin-up: disabled
disk-access-delay: 15s
scsi-io-timeout: 30s
queue-depth: 32
polling-interval: 30s
enclosure-polling-interval: 30s
auto-detect-swap-interval: disabled
smart: detect-clone-replace
auto-global-spare: disabled
* redundant-controller-configuration
Redundant Controller Configuration: primary
Cache Synchronization: enabled
Host Channel Failover Mode: shared
Local/Remote Redundant Mode: local
Write-Through Data Synchronization: disabled
Secondary RS-232 Port Status: disabled
Communication Channel Type: Fibre
* redundancy-mode
Primary controller serial number: 8104488
Primary controller location: Lower
Redundancy mode: Active-Active
Redundancy status: Enabled
Secondary controller serial number: 8103724
* cache-parameters
mode: write-back
optimization: random
sync-period: disabled
current-global-write-policy: write-back
* RS232-configuration
COM1 speed: 9600bps
* channels
Ch Type Media Speed Width PID / SID
0 Host FC(P) 2G Serial 40 / N/A
1 Host FC(P) N/A Serial N/A / 42
2 DRV+RCC FC(L) 2G Serial 14 / 15
3 DRV+RCC FC(L) 2G Serial 14 / 15
4 Host FC(P) 2G Serial 44 / N/A
5 Host FC(P) N/A Serial N/A / 46
6 Host LAN N/A Serial N/A / N/A
* disks
Ch Id Size Speed LD Status IDs Rev
2(3) 0 279.40GB 200MB ld1 ONLINE SEAGATE ST330000FSUN300G 055A
S/N 38528TGW
WWNN 2000001862363F9C
2(3) 1 279.40GB 200MB ld0 ONLINE SEAGATE ST330000FSUN300G 055A
S/N 0751KPTT
WWNN 20000014C38511B6
2(3) 2 279.40GB 200MB GLOBAL STAND-BY SEAGATE ST330000FSUN300G 055A
S/N 38528FH8
WWNN 2000001862364997
2(3) 3 279.40GB 200MB ld0 ONLINE SEAGATE ST330000FSUN300G 055A
S/N 385263B5
WWNN 20000018623649A3
2(3) 4 279.40GB 200MB ld0 ONLINE SEAGATE ST330000FSUN300G 055A
S/N 38528TS7
WWNN 20000018623647DD
2(3) 5 279.40GB 200MB ld0 ONLINE SEAGATE ST330000FSUN300G 055A
S/N 3852GAAM
WWNN 20000018623644A8
2(3) 6 279.40GB 200MB ld0 ONLINE SEAGATE ST330000FSUN300G 055A
S/N 38525B67
WWNN 200000186236463E
2(3) 7 279.40GB 200MB ld0 ONLINE SEAGATE ST330000FSUN300G 055A
S/N 385293LK
WWNN 20000018623647D4
2(3) 8 279.40GB 200MB ld0 ONLINE SEAGATE ST330000FSUN300G 055A
S/N 38528E2E
WWNN 2000001862364A4A
2(3) 9 279.40GB 200MB ld0 ONLINE SEAGATE ST330000FSUN300G 055A
S/N 3852FPF2
WWNN 2000001862364137
2(3) 10 279.40GB 200MB ld0 ONLINE SEAGATE ST330000FSUN300G 055A
S/N 38525BZE
WWNN 200000186236438E
2(3) 11 279.40GB 200MB ld1 ONLINE SEAGATE ST330000FSUN300G 055A
S/N 3852F9C1
WWNN 2000001862364519
2(3) 12 279.40GB 200MB ld1 ONLINE SEAGATE ST330000FSUN300G 055A
S/N 22526XFP
WWNN 20000014C3D8B5CD
2(3) 13 279.40GB 200MB ld1 ONLINE SEAGATE ST330000FSUN300G 055A
S/N 225280ZR
WWNN 20000014C3D8B9F4
2(3) 14 279.40GB 200MB ld1 ONLINE SEAGATE ST330000FSUN300G 055A
S/N 38527GP1
WWNN 2000001862364001
2(3) 15 279.40GB 200MB ld1 ONLINE FUJITSU MAW3300FCSUN300G 1303
S/N 000629D01NGJ
WWNN 500000E0126502D0
2(3) 16 279.40GB 200MB NONE FRMT FUJITSU MAW3300FCSUN300G 1303
S/N 000629D01NG9
WWNN 500000E0126501A0
2(3) 17 279.40GB 200MB ld1 ONLINE FUJITSU MAW3300FCSUN300G 1303
S/N 000629D01NG0
WWNN 500000E0126500F0
2(3) 18 279.40GB 200MB ld1 ONLINE FUJITSU MAW3300FCSUN300G 1303
S/N 000629D01NGH
WWNN 500000E0126502B0
2(3) 19 279.40GB 200MB ld1 ONLINE FUJITSU MAW3300FCSUN300G 1303
S/N 000629D01NGE
WWNN 500000E012650210
* logical-drives
LD LD-ID Size Assigned Type Disks Spare Failed Status
ld0 5F4B5543 2.18TB Primary RAID5 9 1 0 Good
Write-Policy Default StripeSize 32KB
ld1 07190DF2 2.18TB Secondary RAID5 9 1 0 Good
Write-Policy Default StripeSize 32KB
* logical-volumes
* partitions
LD/LV ID-Partition Size
ld0-00 5F4B5543-00 5.00GB
ld0-01 5F4B5543-01 5.00GB
ld0-02 5F4B5543-02 5.00GB
ld0-03 5F4B5543-03 45.00GB
ld0-04 5F4B5543-04 45.00GB
ld0-05 5F4B5543-05 300.00GB
ld0-06 5F4B5543-06 1.79TB
ld1-00 07190DF2-00 5.00GB
ld1-01 07190DF2-01 5.00GB
ld1-02 07190DF2-02 5.00GB
ld1-03 07190DF2-03 515.00GB
ld1-04 07190DF2-04 500.00GB
ld1-05 07190DF2-05 180.00GB
ld1-06 07190DF2-06 1023.17GB
* lun-maps
Ch Tgt LUN ld/lv ID-Partition Assigned Filter Map
0 40 0 ld0 5F4B5543-00 Primary 210000E08B929600 {tvlp-node-n01p01}
0 40 0 ld0 5F4B5543-00 Primary 210000E08B92B831 {tvlp-node-n02p01}
0 40 1 ld0 5F4B5543-01 Primary 210000E08B927C31 {tvlp-node-n03p01}
0 40 1 ld0 5F4B5543-01 Primary 210000E08B925A02 {tvlp-node-n04p01}
0 40 2 ld0 5F4B5543-02 Primary 210000E08B927C31 {tvlp-node-n03p01}
0 40 2 ld0 5F4B5543-02 Primary 210000E08B925A02 {tvlp-node-n04p01}
0 40 3 ld0 5F4B5543-03 Primary 210000E08B927C31 {tvlp-node-n03p01}
0 40 3 ld0 5F4B5543-03 Primary 210000E08B925A02 {tvlp-node-n04p01}
0 40 4 ld0 5F4B5543-04 Primary 210000E08B927C31 {tvlp-node-n03p01}
0 40 4 ld0 5F4B5543-04 Primary 210000E08B925A02 {tvlp-node-n04p01}
0 40 5 ld0 5F4B5543-05 Primary 210000E08B927C31 {tvlp-node-n03p01}
0 40 5 ld0 5F4B5543-05 Primary 210000E08B925A02 {tvlp-node-n04p01}
1 42 0 ld1 07190DF2-00 Secondary 210000E08B920100 {tvlp-node-n05p01}
1 42 1 ld1 07190DF2-01 Secondary 210000E08B920100 {tvlp-node-n05p01}
1 42 2 ld1 07190DF2-02 Secondary 210000E08B920100 {tvlp-node-n05p01}
1 42 3 ld1 07190DF2-03 Secondary 210000E08B920100 {tvlp-node-n05p01}
1 42 4 ld1 07190DF2-04 Secondary 210000E08B920100 {tvlp-node-n05p01}
1 42 5 ld1 07190DF2-05 Secondary 210000E08B920100 {tvlp-node-n05p01}
4 44 0 ld0 5F4B5543-00 Primary 210000E08B92BC01 {tvlp-node-n01p02}
4 44 0 ld0 5F4B5543-00 Primary 210000E08B92DB02 {tvlp-node-n02p02}
4 44 1 ld0 5F4B5543-01 Primary 210000E08B91FDFF {tvlp-node-n04p02}
4 44 1 ld0 5F4B5543-01 Primary 210000E08B924A03 {tvlp-node-n03p02}
4 44 2 ld0 5F4B5543-02 Primary 210000E08B924A03 {tvlp-node-n03p02}
4 44 2 ld0 5F4B5543-02 Primary 210000E08B91FDFF {tvlp-node-n04p02}
4 44 3 ld0 5F4B5543-03 Primary 210000E08B924A03 {tvlp-node-n03p02}
4 44 3 ld0 5F4B5543-03 Primary 210000E08B91FDFF {tvlp-node-n04p02}
4 44 4 ld0 5F4B5543-04 Primary 210000E08B924A03 {tvlp-node-n03p02}
4 44 4 ld0 5F4B5543-04 Primary 210000E08B91FDFF {tvlp-node-n04p02}
4 44 5 ld0 5F4B5543-05 Primary 210000E08B924A03 {tvlp-node-n03p02}
4 44 5 ld0 5F4B5543-05 Primary 210000E08B91FDFF {tvlp-node-n04p02}
5 46 0 ld1 07190DF2-00 Secondary 210000E08B91EDFF {tvlp-node-n05p02}
5 46 1 ld1 07190DF2-01 Secondary 210000E08B91EDFF {tvlp-node-n05p02}
5 46 2 ld1 07190DF2-02 Secondary 210000E08B91EDFF {tvlp-node-n05p02}
5 46 3 ld1 07190DF2-03 Secondary 210000E08B91EDFF {tvlp-node-n05p02}
5 46 4 ld1 07190DF2-04 Secondary 210000E08B91EDFF {tvlp-node-n05p02}
5 46 5 ld1 07190DF2-05 Secondary 210000E08B91EDFF {tvlp-node-n05p02}
* protocol
Identifier Status Port Parameters
telnet enabled 23 inactivity-timeout=disabled
http enabled 80 n/a
https disabled n/a n/a
ftp enabled 21 n/a
ssh enabled 22 n/a
priagent enabled 58632 n/a
snmp disabled n/a n/a
dhcp enabled 68 n/a
ping enabled n/a n/a
* auto-write-through-trigger
controller-failure: enabled
battery-backup-failure: enabled
ups-ac-power-loss: disabled
power-supply-failure: enabled
fan-failure: enabled
temperature-exceeded-delay: 30min
* peripheral-device-status
Item Value status
CPU Temp Sensor(primary) 52.50C within safety range
Board1 Temp Sensor(primary) 55.50C within safety range
Board2 Temp Sensor(primary) 64.00C within safety range
+3.3V Value(primary) 3.352V within safety range
+5V Value(primary) 5.019V within safety range
+12V Value(primary) 12.199V within safety range
Battery-Backup Battery(primary) 00 Hardware:OK
CPU Temp Sensor(secondary) 52.50C within safety range
Board1 Temp Sensor(secondary) 57.50C within safety range
Board2 Temp Sensor(secondary) 62.00C within safety range
+3.3V Value(secondary) 3.384V within safety range
+5V Value(secondary) 5.099V within safety range
+12V Value(secondary) 12.381V within safety range
Battery-Backup Battery(secondary) 00 Hardware:OK
* enclosure-status
Ch Id Chassis Vendor/Product ID Rev PLD WWNN WWPN
2 124 0A7805 SUN StorEdge 3510F A 1080 1000 204000C0FF0A7805 214000C0FF0A7805
Topology: loop(a) Status: OK
3 124 0A7805 SUN StorEdge 3510F A 1080 1000 204000C0FF0A7805 224000C0FF0A7805
Topology: loop(b) Status: OK
Enclosure Component Status:
Type Unit Status FRU P/N FRU S/N Add'l Data
Fan 0 OK 371-0108 GK0XC2 --
Fan 1 OK 371-0108 GK0XC2 --
Fan 2 OK 371-0108 GK0XC5 --
Fan 3 OK 371-0108 GK0XC5 --
PS 0 OK 371-0108 GK0XC2 --
PS 1 OK 371-0108 GK0XC5 --
Temp 0 OK 371-0531 0A7805 temp=30
Temp 1 OK 371-0531 0A7805 temp=28
Temp 2 OK 371-0531 0A7805 temp=31
Temp 3 OK 371-0531 0A7805 temp=30
Temp 4 OK 371-0531 0A7805 temp=31
Temp 5 OK 371-0531 0A7805 temp=30
Temp 6 OK 371-0532 HL12LM temp=37
Temp 7 OK 371-0532 HL12LM temp=41
Temp 8 OK 371-0532 HL12QD temp=37
Temp 9 OK 371-0532 HL12QD temp=38
Temp 10 OK 371-0108 GK0XC2 temp=30
Temp 11 OK 371-0108 GK0XC5 temp=25
Voltage 0 OK 371-0108 GK0XC2 voltage=5.110V
Voltage 1 OK 371-0108 GK0XC2 voltage=11.750V
Voltage 2 OK 371-0108 GK0XC5 voltage=5.020V
Voltage 3 OK 371-0108 GK0XC5 voltage=11.520V
Voltage 4 OK 371-0532 HL12LM voltage=2.480V
Voltage 5 OK 371-0532 HL12LM voltage=3.250V
Voltage 6 OK 371-0532 HL12LM voltage=5.000V
Voltage 7 OK 371-0532 HL12LM voltage=12.120V
Voltage 8 OK 371-0532 HL12QD voltage=2.500V
Voltage 9 OK 371-0532 HL12QD voltage=3.300V
Voltage 10 OK 371-0532 HL12QD voltage=5.050V
Voltage 11 OK 371-0532 HL12QD voltage=12.240V
DiskSlot 0 OK 371-0531 0A7805 addr=0,led=off
DiskSlot 1 Absent 371-0531 0A7805 addr=1,led=off
DiskSlot 2 Absent 371-0531 0A7805 addr=2,led=off
DiskSlot 3 OK 371-0531 0A7805 addr=3,led=off
DiskSlot 4 OK 371-0531 0A7805 addr=4,led=off
DiskSlot 5 OK 371-0531 0A7805 addr=5,led=off
DiskSlot 6 OK 371-0531 0A7805 addr=6,led=off
DiskSlot 7 OK 371-0531 0A7805 addr=7,led=off
DiskSlot 8 OK 371-0531 0A7805 addr=8,led=off
DiskSlot 9 OK 371-0531 0A7805 addr=9,led=off
DiskSlot 10 OK 371-0531 0A7805 addr=10,led=off
DiskSlot 11 OK 371-0531 0A7805 addr=11,led=off
* SES
Ch Id Chassis Vendor/Product ID Rev PLD WWNN WWPN
2 124 0A7805 SUN StorEdge 3510F A 1080 1000 204000C0FF0A7805 214000C0FF0A7805
Topology: loop(a)
3 124 0A7805 SUN StorEdge 3510F A 1080 1000 204000C0FF0A7805 224000C0FF0A7805
Topology: loop(b)
* port-WWNs
Ch Id WWPN
0 40 216000C0FF8A7805
1 42 226000C0FFAA7805
4 44 256000C0FFCA7805
5 46 266000C0FFEA7805
* inter-controller-link
inter-controller-link upper channel 0: connected
inter-controller-link lower channel 0: connected
inter-controller-link upper channel 1: connected
inter-controller-link lower channel 1: connected
inter-controller-link upper channel 4: connected
inter-controller-link lower channel 4: connected
inter-controller-link upper channel 5: connected
inter-controller-link lower channel 5: connected
* battery-status
Upper Battery Type: 1
Upper Battery Manufacturing Date: Fri Jun 16 00:00:00 2006
Upper Battery Placed In Service: Tue Aug 8 09:27:53 2006
Upper Battery Expiration Date: Thu Aug 7 09:27:53 2008
Upper Battery Expiration Status: OK
Lower Battery Type: 1
Lower Battery Manufacturing Date: Fri Jun 16 00:00:00 2006
Lower Battery Placed In Service: Tue Aug 8 09:27:52 2006
Lower Battery Expiration Date: Thu Aug 7 09:27:52 2008
Lower Battery Expiration Status: OK
Upper Battery Hardware Status: OK
Lower Battery Hardware Status: OK
* sata-router
no sata routers found
* sata-mux
0 mux boards found
* host-wwn-names
Host-ID/WWN Name
210000E08B91EDFF tvlp-node-n05p02
210000E08B91FDFF tvlp-node-n04p02
210000E08B925A02 tvlp-node-n04p01
210000E08B927C31 tvlp-node-n03p01
210000E08B924A03 tvlp-node-n03p02
210000E08B92DB02 tvlp-node-n02p02
210000E08B92BC01 tvlp-node-n01p02
210000E08B92B831 tvlp-node-n02p01
210000E08B920100 tvlp-node-n05p01
210000E08B929600 tvlp-node-n01p01
* FRUs
7 FRUs found in chassis SN#0A7805 at ch 2 id 124
Name: FC_CHASSIS_BKPLN
Description: SE3510 FC Chassis/backplane
Part Number: 371-0531
Serial Number: 0A7805
Revision: 01
Initial Hardware Dash Level: 01
FRU Shortname:
Manufacturing Date: Sun Jul 16 05:25:36 2006
Manufacturing Location: Suzhou,China
Manufacturer JEDEC ID: 0x0301
FRU Location: FC MIDPLANE SLOT
Chassis Serial Number: 0A7805
FRU Status: OK
Name: FC_RAID_IOM
Description: SE3510 I/O w/SES RAID FC 2U
Part Number: 371-0532
Serial Number: HL12LM
Revision: 01
Initial Hardware Dash Level: 01
FRU Shortname:
Manufacturing Date: Wed Jul 5 12:11:49 2006
Manufacturing Location: Suzhou,China
Manufacturer JEDEC ID: 0x0301
FRU Location: UPPER FC RAID IOM SLOT
Chassis Serial Number: 0A7805
FRU Status: OK
Name: BATTERY_BOARD
Description: SE351X Hot Swap Battery Module
Part Number: 371-0539
Serial Number: GP15BJ
Revision: 01
Initial Hardware Dash Level: 01
FRU Shortname:
Manufacturing Date: Thu Jul 6 03:25:30 2006
Manufacturing Location: Suzhou,China
Manufacturer JEDEC ID: 0x0301
FRU Location: UPPER BATTERY BOARD SLOT
Chassis Serial Number: 0A7805
FRU Status: OK
Name: AC_POWER_SUPPLY
Description: SE3XXX AC PWR SUPPLY/FAN, 2U
Part Number: 371-0108
Serial Number: GK0XC5
Revision: 01
Initial Hardware Dash Level: 01
FRU Shortname:
Manufacturing Date: Mon May 22 08:45:16 2006
Manufacturing Location: Irvine California, USA
Manufacturer JEDEC ID: 0x048F
FRU Location: RIGHT AC PSU SLOT #1 (RIGHT)
Chassis Serial Number: 0A7805
FRU Status: OK
Name: AC_POWER_SUPPLY
Description: SE3XXX AC PWR SUPPLY/FAN, 2U
Part Number: 371-0108
Serial Number: GK0XC2
Revision: 01
Initial Hardware Dash Level: 01
FRU Shortname:
Manufacturing Date: Mon May 22 08:53:42 2006
Manufacturing Location: Irvine California, USA
Manufacturer JEDEC ID: 0x048F
FRU Location: AC PSU SLOT #0 (LEFT)
Chassis Serial Number: 0A7805
FRU Status: OK
Name: FC_RAID_IOM
Description: SE3510 I/O w/SES RAID FC 2U
Part Number: 371-0532
Serial Number: HL12QD
Revision: 01
Initial Hardware Dash Level: 01
FRU Shortname:
Manufacturing Date: Wed Jul 5 15:16:42 2006
Manufacturing Location: Suzhou,China
Manufacturer JEDEC ID: 0x0301
FRU Location: LOWER FC RAID IOM SLOT
Chassis Serial Number: 0A7805
FRU Status: OK
Name: BATTERY_BOARD
Description: SE351X Hot Swap Battery Module
Part Number: 371-0539
Serial Number: GP15GW
Revision: 01
Initial Hardware Dash Level: 01
FRU Shortname:
Manufacturing Date: Thu Jul 6 05:26:03 2006
Manufacturing Location: Suzhou,China
Manufacturer JEDEC ID: 0x0301
FRU Location: LOWER BATTERY BOARD SLOT
Chassis Serial Number: 0A7805
FRU Status: OK
* access-mode
access-mode: inband
* controller-date
Boot time : Fri Jan 5 10:20:15 2007
Current time : Thu Feb 8 10:25:36 2007
Time Zone : GMT
* disk-array
init-verify: disabled
rebuild-verify: disabled
normal-verify: disabled
rebuild-priority: normal

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

Solstice backup 6.1 hang when invoking the autochanger "SUN Storedge L8 "

My company have a SUN Storedge L8 attached to a SUN Solaris 9 (SPARC) while I can only do a tar to the /dev/rmt/0, whenever I tried to interact with the jukebox with the solstice backup, the program hang definitely.
grep '/usr/kernel/drv/lus' /var/sadm/install/contents
/usr/kernel/drv/lus f none 0555 root bin 34624 12073 993189557 SUNWsbus2
/usr/kernel/drv/lus.conf f none 0444 root bin 3754 45438 993190441 SUNWsbus2
/usr/kernel/drv/lus32 f none 0555 root bin 33444 4422 993213667 SUNWsbus2
pkginfo -l SUNWsbus2
PKGINST: SUNWsbus2
NAME: Solstice Backup (Backup/Recover) Device Drivers
CATEGORY: system
ARCH: sparc
VERSION: 6.1,REV=Build.186
BASEDIR: /
VENDOR: Sun Microsystems, Inc.
PSTAMP: gelato010622054128
INSTDATE: Apr 08 2003 13:25
STATUS: completely installed
FILES: 48 installed pathnames
44 executables
37896 blocks used (approx)
this machine has installed the solstice backup manager
pkginfo | grep -i Solstice
system SUNWmibii Solstice Enterprise Agents 1.0.3 SNMP daemon
system SUNWsacom Solstice Enterprise Agents 1.0.3 files for root file system
system SUNWsadmi Solstice Enterprise Agents 1.0.3 Desktop Management Interface
system SUNWsadml Solstice Launcher.
system SUNWsadmx Solstice Enterprise Agents 1.0.3 Desktop Management Interface Libraries (64-bit)
system SUNWsasnm Solstice Enterprise Agents 1.0.3 Simple Network Management Protocol
system SUNWsasnx Solstice Enterprise Agents 1.0.3 Simple Network Management Protocol Libraries (64-bit)
application SUNWsbuc Solstice Backup (Backup/Recover) Client
application SUNWsbum Solstice Backup (Backup/Recover) Man
application SUNWsbun Solstice Backup (Backup/Recover) Storage Node
application SUNWsbus1 Solstice Backup (Backup/Recover) Server
system SUNWsbus2 Solstice Backup (Backup/Recover) Device Drivers
under the server->registration, I found that the registration contains :-
Autochanger Module, 9 slots/9
ClientPaks for Windows/1
Networker for UNIX, Workgroup edition (8 clients per server)1 server
Networker Module for Oracl/1
BTW, inquire shows:-
/etc/LGTOuscsi/inquire
[email protected]:TOSHIBA DVD-ROM SD-M14011009|CD-ROM
[email protected]:ADIC FastStor 2 A12r|Autochanger (Jukebox)
[email protected]:HP Ultrium 1-SCSI E3 |Tape
[email protected]:HP Ultrium 1-SCSI E3 |Tape
where cfgadm -alv shows:-
Ap_Id Receptacle Occupant Condition Information
When Type Busy Phys_Id
c0 connected configured unknown
unavailable scsi-bus n /devices/pci@8,700000/scsi@6:scsi
c0::/dev/lus connected configured unknown TOSHIBA DVD-ROM SD-M1401
unavailable CD-ROM n /devices/pci@8,700000/scsi@6:scsi::/dev/lus
c0::dsk/c0t6d0 connected configured unknown TOSHIBA DVD-ROM SD-M1401
unavailable CD-ROM y /devices/pci@8,700000/scsi@6:scsi::dsk/c0t6d0
c1 connected configured unknown
unavailable fc-private n /devices/pci@8,600000/SUNW,qlc@4/fp@0,0:fc
c1::21000004cfe34092 connected configured unknown SEAGATE ST373307FSUN72G
unavailable disk n /devices/pci@8,600000/SUNW,qlc@4/fp@0,0:fc::21000004cfe34092
c1::21000004cfe34350 connected configured unknown SEAGATE ST373307FSUN72G
unavailable disk n /devices/pci@8,600000/SUNW,qlc@4/fp@0,0:fc::21000004cfe34350
c2 connected configured unknown
unavailable scsi-bus n /devices/pci@8,700000/scsi@6,1:scsi
c2::lus1 connected configured unknown
unavailable unknown n /devices/pci@8,700000/scsi@6,1:scsi::lus1
c3 connected configured unknown
unavailable scsi-bus n /devices/pci@8,600000/pci@1/scsi@4:scsi
c3::lus2 connected configured unknown HP Ultrium 1-SCSI
unavailable unknown n /devices/pci@8,600000/pci@1/scsi@4:scsi::lus2
c3::rmt/0 connected configured unknown HP Ultrium 1-SCSI
unavailable tape n /devices/pci@8,600000/pci@1/scsi@4:scsi::rmt/0
c4 connected configured unknown
unavailable scsi-bus n /devices/pci@8,600000/pci@1/scsi@5:scsi
c4::lus3 connected configured unknown
unavailable unknown n /devices/pci@8,600000/pci@1/scsi@5:scsi::lus3
usb0/1 connected configured ok Mfg: <undef> Product: <undef> NConfigs: 1 Config: 0 <no cfg str descr>
unavailable usb-kbd n /devices/pci@8,700000/usb@5,3:1
usb0/2 empty unconfigured ok
unavailable unknown n /devices/pci@8,700000/usb@5,3:2
usb0/3 connected configured ok Mfg: <undef> Product: <undef> NConfigs: 1 Config: 0 <no cfg str descr>
unavailable usb-mouse n /devices/pci@8,700000/usb@5,3:3
usb0/4 empty unconfigured ok
unavailable unknown n /devices/pci@8,700000/usb@5,3:4
nsrjb shows
Jukebox L8:
slot volume pool volume id recyclable
1: dwbak.inc.day0.wk0.001* 2481680129
2: dwbak.inc.day0.wk0.002 DW Incremental 2481704705 no
3: dwbak.inc.day0.wk0.003 DW Incremental 2481729793 no
4: -* -
5: dwbak.inc.day0.wk0.005 DW Incremental 2481779201 no
6: dwbak.inc.day0.wk0.006 DW Incremental 2481804289 no
7: dwbak.inc.day0.wk0.007 DW Incremental 2481829889 no
8: dwbak.inc.day0.wk0.008 DW Incremental 2481854209 no
*not registered in the NetWorker media data base
drive 1 (/dev/rmt/0cbn) slot 5: dwbak.inc.day0.wk0.005
nsrjb -HE hang indefinitly, so does nsrjb -HHE. devfsadm -c tape also hang while simply devfsadm can run without problem and cfgadm -alv c3 provide the following:-
Ap_Id Receptacle Occupant Condition Information
When Type Busy Phys_Id
c3 connected configured unknown
unavailable scsi-bus n /devices/pci@8,600000/pci@1/scsi@4:scsi
c3::lus2 connected configured unknown HP Ultrium 1-SCSI
unavailable unknown n /devices/pci@8,600000/pci@1/scsi@4:scsi::lus2
c3::rmt/0 connected configured unknown HP Ultrium 1-SCSI
unavailable tape n /devices/pci@8,600000/pci@1/scsi@4:scsi::rmt/0
nsjrb result should be past history, coz I am doing tar and manually changing the slot for quite some time already. Now I unconnect the cable and run devfsadm and then cfgadm -alv shows
cfgadm -alv
Ap_Id Receptacle Occupant Condition Information
When Type Busy Phys_Id
c0 connected configured unknown
unavailable scsi-bus n /devices/pci@8,700000/scsi@6:scsi
c0::/dev/lus connected configured unknown TOSHIBA DVD-ROM SD-M1401
unavailable CD-ROM n /devices/pci@8,700000/scsi@6:scsi::/dev/lus
c0::dsk/c0t6d0 connected configured unknown TOSHIBA DVD-ROM SD-M1401
unavailable CD-ROM y /devices/pci@8,700000/scsi@6:scsi::dsk/c0t6d0
c1 connected configured unknown
unavailable fc-private n /devices/pci@8,600000/SUNW,qlc@4/fp@0,0:fc
c1::21000004cfe34092 connected configured unknown SEAGATE ST373307FSUN72G
unavailable disk n /devices/pci@8,600000/SUNW,qlc@4/fp@0,0:fc::21000004cfe34092
c1::21000004cfe34350 connected configured unknown SEAGATE ST373307FSUN72G
unavailable disk n /devices/pci@8,600000/SUNW,qlc@4/fp@0,0:fc::21000004cfe34350
c2 connected configured unknown
unavailable scsi-bus n /devices/pci@8,700000/scsi@6,1:scsi
c2::lus1 connected configured unknown
unavailable unknown n /devices/pci@8,700000/scsi@6,1:scsi::lus1
c3 connected configured unknown
unavailable scsi-bus n /devices/pci@8,600000/pci@1/scsi@4:scsi
c3::lus2 connected configured unknown HP Ultrium 1-SCSI
unavailable unknown n /devices/pci@8,600000/pci@1/scsi@4:scsi::lus2
c3::rmt/0 connected configured unknown HP Ultrium 1-SCSI
unavailable tape n /devices/pci@8,600000/pci@1/scsi@4:scsi::rmt/0
c4 connected configured unknown
unavailable scsi-bus n /devices/pci@8,600000/pci@1/scsi@5:scsi
c4::lus3 connected configured unknown
unavailable unknown n /devices/pci@8,600000/pci@1/scsi@5:scsi::lus3
usb0/1 connected configured ok Mfg: <undef> Product: <undef> NConfigs: 1 Config: 0 <no cfg str descr>
unavailable usb-kbd n /devices/pci@8,700000/usb@5,3:1
usb0/2 empty unconfigured ok
unavailable unknown n /devices/pci@8,700000/usb@5,3:2
usb0/3 connected configured ok Mfg: <undef> Product: <undef> NConfigs: 1 Config: 0 <no cfg str descr>
unavailable usb-mouse n /devices/pci@8,700000/usb@5,3:3
usb0/4 empty unconfigured ok
unavailable unknown n /devices/pci@8,700000/usb@5,3:4
and inquire still shows
[email protected]:TOSHIBA DVD-ROM SD-M14011009|CD-ROM
[email protected]:ADIC FastStor 2 A12r|Autochanger (Jukebox)
[email protected]:HP Ultrium 1-SCSI E3 |Tape
[email protected]:HP Ultrium 1-SCSI E3 |Tape
and then I reconnect the cable I saw a lot of error message in dmesg:-
Jun 19 13:47:37 server scsi: [ID 107833 kern.warning] WARNING: /pci@8,600000/pci@1/scsi@4 (qus0):
Jun 19 13:47:37 server Received unexpected SCSI Reset
Jun 19 13:47:37 server scsi: [ID 107833 kern.warning] WARNING: /pci@8,600000/pci@1/scsi@4 (qus0):
Jun 19 13:47:37 server Received unexpected SCSI Reset
Jun 19 13:51:30 server scsi: [ID 107833 kern.notice] /pci@8,600000/pci@1/scsi@4 (qus0):
Jun 19 13:51:30 server Failed to Get Features
Jun 19 13:51:50 server scsi: [ID 107833 kern.warning] WARNING: /pci@8,600000/pci@1/scsi@4 (qus0):
Jun 19 13:51:50 server ISP: Firmware cmd timeout
Jun 19 13:51:50 server scsi: [ID 107833 kern.warning] WARNING: /pci@8,600000/pci@1/scsi@4 (qus0):
Jun 19 13:51:50 server Fatal error, resetting interface, flg 1
and devfsadm hang. So I double check the past demsg and found a lot of similar SCSI error message as below:-
Jun 19 13:43:12 server probe request for LUN 0 denied: max LUN -1
Jun 19 13:43:12 server scsi: [ID 107833 kern.warning] WARNING: /pci@8,600000/pci@1/scsi@5 (qus1):
Is that represent a hardware failure either on the jukebox or the SCSI controller? Or it is indeed a software corruption that can only be solved by reinstallation? But unfortunately I don't have the media on hand.
PS.a more details can be found under expert exchange thru the links below:-
http://www.experts-exchange.com/OS/Unix/Solaris/Q_23413012.html#a21749881
http://www.experts-exchange.com/OS/Unix/Solaris/Q_23478147.html

My company have a SUN Storedge L8 attached to a SUN Solaris 9 (SPARC) while I can only do a tar to the /dev/rmt/0, whenever I tried to interact with the jukebox with the solstice backup, the program hang definitely.
grep '/usr/kernel/drv/lus' /var/sadm/install/contents
/usr/kernel/drv/lus f none 0555 root bin 34624 12073 993189557 SUNWsbus2
/usr/kernel/drv/lus.conf f none 0444 root bin 3754 45438 993190441 SUNWsbus2
/usr/kernel/drv/lus32 f none 0555 root bin 33444 4422 993213667 SUNWsbus2
pkginfo -l SUNWsbus2
PKGINST: SUNWsbus2
NAME: Solstice Backup (Backup/Recover) Device Drivers
CATEGORY: system
ARCH: sparc
VERSION: 6.1,REV=Build.186
BASEDIR: /
VENDOR: Sun Microsystems, Inc.
PSTAMP: gelato010622054128
INSTDATE: Apr 08 2003 13:25
STATUS: completely installed
FILES: 48 installed pathnames
44 executables
37896 blocks used (approx)
this machine has installed the solstice backup manager
pkginfo | grep -i Solstice
system SUNWmibii Solstice Enterprise Agents 1.0.3 SNMP daemon
system SUNWsacom Solstice Enterprise Agents 1.0.3 files for root file system
system SUNWsadmi Solstice Enterprise Agents 1.0.3 Desktop Management Interface
system SUNWsadml Solstice Launcher.
system SUNWsadmx Solstice Enterprise Agents 1.0.3 Desktop Management Interface Libraries (64-bit)
system SUNWsasnm Solstice Enterprise Agents 1.0.3 Simple Network Management Protocol
system SUNWsasnx Solstice Enterprise Agents 1.0.3 Simple Network Management Protocol Libraries (64-bit)
application SUNWsbuc Solstice Backup (Backup/Recover) Client
application SUNWsbum Solstice Backup (Backup/Recover) Man
application SUNWsbun Solstice Backup (Backup/Recover) Storage Node
application SUNWsbus1 Solstice Backup (Backup/Recover) Server
system SUNWsbus2 Solstice Backup (Backup/Recover) Device Drivers
under the server->registration, I found that the registration contains :-
Autochanger Module, 9 slots/9
ClientPaks for Windows/1
Networker for UNIX, Workgroup edition (8 clients per server)1 server
Networker Module for Oracl/1
BTW, inquire shows:-
/etc/LGTOuscsi/inquire
[email protected]:TOSHIBA DVD-ROM SD-M14011009|CD-ROM
[email protected]:ADIC FastStor 2 A12r|Autochanger (Jukebox)
[email protected]:HP Ultrium 1-SCSI E3 |Tape
[email protected]:HP Ultrium 1-SCSI E3 |Tape
where cfgadm -alv shows:-
Ap_Id Receptacle Occupant Condition Information
When Type Busy Phys_Id
c0 connected configured unknown
unavailable scsi-bus n /devices/pci@8,700000/scsi@6:scsi
c0::/dev/lus connected configured unknown TOSHIBA DVD-ROM SD-M1401
unavailable CD-ROM n /devices/pci@8,700000/scsi@6:scsi::/dev/lus
c0::dsk/c0t6d0 connected configured unknown TOSHIBA DVD-ROM SD-M1401
unavailable CD-ROM y /devices/pci@8,700000/scsi@6:scsi::dsk/c0t6d0
c1 connected configured unknown
unavailable fc-private n /devices/pci@8,600000/SUNW,qlc@4/fp@0,0:fc
c1::21000004cfe34092 connected configured unknown SEAGATE ST373307FSUN72G
unavailable disk n /devices/pci@8,600000/SUNW,qlc@4/fp@0,0:fc::21000004cfe34092
c1::21000004cfe34350 connected configured unknown SEAGATE ST373307FSUN72G
unavailable disk n /devices/pci@8,600000/SUNW,qlc@4/fp@0,0:fc::21000004cfe34350
c2 connected configured unknown
unavailable scsi-bus n /devices/pci@8,700000/scsi@6,1:scsi
c2::lus1 connected configured unknown
unavailable unknown n /devices/pci@8,700000/scsi@6,1:scsi::lus1
c3 connected configured unknown
unavailable scsi-bus n /devices/pci@8,600000/pci@1/scsi@4:scsi
c3::lus2 connected configured unknown HP Ultrium 1-SCSI
unavailable unknown n /devices/pci@8,600000/pci@1/scsi@4:scsi::lus2
c3::rmt/0 connected configured unknown HP Ultrium 1-SCSI
unavailable tape n /devices/pci@8,600000/pci@1/scsi@4:scsi::rmt/0
c4 connected configured unknown
unavailable scsi-bus n /devices/pci@8,600000/pci@1/scsi@5:scsi
c4::lus3 connected configured unknown
unavailable unknown n /devices/pci@8,600000/pci@1/scsi@5:scsi::lus3
usb0/1 connected configured ok Mfg: <undef> Product: <undef> NConfigs: 1 Config: 0 <no cfg str descr>
unavailable usb-kbd n /devices/pci@8,700000/usb@5,3:1
usb0/2 empty unconfigured ok
unavailable unknown n /devices/pci@8,700000/usb@5,3:2
usb0/3 connected configured ok Mfg: <undef> Product: <undef> NConfigs: 1 Config: 0 <no cfg str descr>
unavailable usb-mouse n /devices/pci@8,700000/usb@5,3:3
usb0/4 empty unconfigured ok
unavailable unknown n /devices/pci@8,700000/usb@5,3:4
nsrjb shows
Jukebox L8:
slot volume pool volume id recyclable
1: dwbak.inc.day0.wk0.001* 2481680129
2: dwbak.inc.day0.wk0.002 DW Incremental 2481704705 no
3: dwbak.inc.day0.wk0.003 DW Incremental 2481729793 no
4: -* -
5: dwbak.inc.day0.wk0.005 DW Incremental 2481779201 no
6: dwbak.inc.day0.wk0.006 DW Incremental 2481804289 no
7: dwbak.inc.day0.wk0.007 DW Incremental 2481829889 no
8: dwbak.inc.day0.wk0.008 DW Incremental 2481854209 no
*not registered in the NetWorker media data base
drive 1 (/dev/rmt/0cbn) slot 5: dwbak.inc.day0.wk0.005
nsrjb -HE hang indefinitly, so does nsrjb -HHE. devfsadm -c tape also hang while simply devfsadm can run without problem and cfgadm -alv c3 provide the following:-
Ap_Id Receptacle Occupant Condition Information
When Type Busy Phys_Id
c3 connected configured unknown
unavailable scsi-bus n /devices/pci@8,600000/pci@1/scsi@4:scsi
c3::lus2 connected configured unknown HP Ultrium 1-SCSI
unavailable unknown n /devices/pci@8,600000/pci@1/scsi@4:scsi::lus2
c3::rmt/0 connected configured unknown HP Ultrium 1-SCSI
unavailable tape n /devices/pci@8,600000/pci@1/scsi@4:scsi::rmt/0
nsjrb result should be past history, coz I am doing tar and manually changing the slot for quite some time already. Now I unconnect the cable and run devfsadm and then cfgadm -alv shows
cfgadm -alv
Ap_Id Receptacle Occupant Condition Information
When Type Busy Phys_Id
c0 connected configured unknown
unavailable scsi-bus n /devices/pci@8,700000/scsi@6:scsi
c0::/dev/lus connected configured unknown TOSHIBA DVD-ROM SD-M1401
unavailable CD-ROM n /devices/pci@8,700000/scsi@6:scsi::/dev/lus
c0::dsk/c0t6d0 connected configured unknown TOSHIBA DVD-ROM SD-M1401
unavailable CD-ROM y /devices/pci@8,700000/scsi@6:scsi::dsk/c0t6d0
c1 connected configured unknown
unavailable fc-private n /devices/pci@8,600000/SUNW,qlc@4/fp@0,0:fc
c1::21000004cfe34092 connected configured unknown SEAGATE ST373307FSUN72G
unavailable disk n /devices/pci@8,600000/SUNW,qlc@4/fp@0,0:fc::21000004cfe34092
c1::21000004cfe34350 connected configured unknown SEAGATE ST373307FSUN72G
unavailable disk n /devices/pci@8,600000/SUNW,qlc@4/fp@0,0:fc::21000004cfe34350
c2 connected configured unknown
unavailable scsi-bus n /devices/pci@8,700000/scsi@6,1:scsi
c2::lus1 connected configured unknown
unavailable unknown n /devices/pci@8,700000/scsi@6,1:scsi::lus1
c3 connected configured unknown
unavailable scsi-bus n /devices/pci@8,600000/pci@1/scsi@4:scsi
c3::lus2 connected configured unknown HP Ultrium 1-SCSI
unavailable unknown n /devices/pci@8,600000/pci@1/scsi@4:scsi::lus2
c3::rmt/0 connected configured unknown HP Ultrium 1-SCSI
unavailable tape n /devices/pci@8,600000/pci@1/scsi@4:scsi::rmt/0
c4 connected configured unknown
unavailable scsi-bus n /devices/pci@8,600000/pci@1/scsi@5:scsi
c4::lus3 connected configured unknown
unavailable unknown n /devices/pci@8,600000/pci@1/scsi@5:scsi::lus3
usb0/1 connected configured ok Mfg: <undef> Product: <undef> NConfigs: 1 Config: 0 <no cfg str descr>
unavailable usb-kbd n /devices/pci@8,700000/usb@5,3:1
usb0/2 empty unconfigured ok
unavailable unknown n /devices/pci@8,700000/usb@5,3:2
usb0/3 connected configured ok Mfg: <undef> Product: <undef> NConfigs: 1 Config: 0 <no cfg str descr>
unavailable usb-mouse n /devices/pci@8,700000/usb@5,3:3
usb0/4 empty unconfigured ok
unavailable unknown n /devices/pci@8,700000/usb@5,3:4
and inquire still shows
[email protected]:TOSHIBA DVD-ROM SD-M14011009|CD-ROM
[email protected]:ADIC FastStor 2 A12r|Autochanger (Jukebox)
[email protected]:HP Ultrium 1-SCSI E3 |Tape
[email protected]:HP Ultrium 1-SCSI E3 |Tape
and then I reconnect the cable I saw a lot of error message in dmesg:-
Jun 19 13:47:37 server scsi: [ID 107833 kern.warning] WARNING: /pci@8,600000/pci@1/scsi@4 (qus0):
Jun 19 13:47:37 server Received unexpected SCSI Reset
Jun 19 13:47:37 server scsi: [ID 107833 kern.warning] WARNING: /pci@8,600000/pci@1/scsi@4 (qus0):
Jun 19 13:47:37 server Received unexpected SCSI Reset
Jun 19 13:51:30 server scsi: [ID 107833 kern.notice] /pci@8,600000/pci@1/scsi@4 (qus0):
Jun 19 13:51:30 server Failed to Get Features
Jun 19 13:51:50 server scsi: [ID 107833 kern.warning] WARNING: /pci@8,600000/pci@1/scsi@4 (qus0):
Jun 19 13:51:50 server ISP: Firmware cmd timeout
Jun 19 13:51:50 server scsi: [ID 107833 kern.warning] WARNING: /pci@8,600000/pci@1/scsi@4 (qus0):
Jun 19 13:51:50 server Fatal error, resetting interface, flg 1
and devfsadm hang. So I double check the past demsg and found a lot of similar SCSI error message as below:-
Jun 19 13:43:12 server probe request for LUN 0 denied: max LUN -1
Jun 19 13:43:12 server scsi: [ID 107833 kern.warning] WARNING: /pci@8,600000/pci@1/scsi@5 (qus1):
Is that represent a hardware failure either on the jukebox or the SCSI controller? Or it is indeed a software corruption that can only be solved by reinstallation? But unfortunately I don't have the media on hand.
PS.a more details can be found under expert exchange thru the links below:-
http://www.experts-exchange.com/OS/Unix/Solaris/Q_23413012.html#a21749881
http://www.experts-exchange.com/OS/Unix/Solaris/Q_23478147.html

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

Veritas Volume manager 4.0 with Sun StorEdge 3310 D

I am running into a problem. The vxconfigd deamon always dump core when rebooting.
Our environment is listed below.
OS environemt.
     SunOS server1 5.8 Generic_117350-43 sun4u sparc SUNW,Sun-Fire-V240
Software installed.
     Sun Cluster 3.0
     Veritas Volume Manager 4.0 MP2.
Disk Array associated.
     Sun StorEdge 3310 D.
I looked up veritas.com and find Array Support Library (ASL) for Sun StorEdge 3xxx Series is recommended. But I didn't find this library is running on this server.
Please refer to this following link
http://support.veritas.com/docs/277923
As our system is one of critical systems and I'd like to confirm that I can follow up this procedure without doing harm things to our system.
Jeff

No problem Jeff :)
I took a look at the Veritas doc and you're right it does seem to cover everthing.
Has the vxconfigd core dumped since the start? ie from the moment it was installed?
I have installed VXVM 4.0 with Solaris 8 but without the ASL and this worked ok, I know that's not much help to you but I am not sure the ASL will help. Mind you I have not installed it with Sun Cluster 3.0.

Sun StorEdge L8 Tape Library (UREGENT!!)

hi all
help needed.. i am new in this.. i ahve to do backup in the Sun StorEdge L8 every weekend.. as usual i will unload the Tape 1 and load the Tape 2 for this weekend backup.. Recently the tape shows '!' at the Tape 2.. when i try to unload the Tape 2, it shows me no tape is load.. wat does the '!' means?? can anyone explain? is it the tape is bad??
this is wat it shows when i mt staus
HP Ultrium LTO 2 tape drive:
sense key(0x6)= Unit Attention residual= 0 retries= 0
file no= 0 block no= 0
can anyone explain..
Thanks..

Hi Surajsid
Do you still have a support contract for this Library ? If it's still showing the same issues after power cycling the drive I would log a call with Orcale/Sun.
Have you changed anything in your backup environment lately ?
Regards
David

Sun StorEdge 3510

Similar Messages

Maybe you are looking for