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

Similar Messages

StorEdge 3510 FC array Configuration

Hello,
I'm running Solaris 8 on a Neta 20. I have 3 StorEdge 3510 FC arrays attached; one controller each array. Each has 12x146 drives for a total of 2TB each array. As this if my first time dealing with this array, I need some advise. I configured my first array with one logical drive and 4 partitions. maped the luns, and reset. (oh I changed the seq to ramdom)
I am now trying to configure the 2nd array, however it will only let me make a logical drive of 512GB max. I've tried everything I could think of to overcome this. Any ideas, I was talking to someone today and they mentioned that solaris will only reconize 1TB. Is this true? If so does anyone have any ideas on a better way to configure the arrays. They will be used for large oracle databases.
Thanks
[email protected]

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

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

What do iostat hard errors and transport errors mean?

Can anyone give me some insight into the following output from iostat
-bash-3.00# iostat -En c1t5d0
c1t5d0 Soft Errors: 0 Hard Errors: 5 Transport Errors: 8
Vendor: FUJITSU Product: MAN3735F SUN72G Revision: 0704 Serial No: 0305V94190
Size: 73.41GB <73407865856 bytes>
Media Error: 0 Device Not Ready: 0 No Device: 1 Recoverable: 0
Illegal Request: 0 Predictive Failure Analysis: 0
Obviously there are 5 hard errors and 8 transport errors, but what does that normally mean? Reseat the drive to fix? Run fsck? How many errors are acceptable before needing to become concerned?

Hi.
This counters - Solaris realated. It's not permanent for device.
After reboot - all this error counters will be reset to 0.
It's not normal that this counters not 0, but it's not meaning that device is bad or should be replaced.
No Device: 1 - So - possible device was removed and reinserting, may be transport porblem.
This disc - FC-AL. So it may be problem on other device in loop.
Is it interanl or external disk? What server ?
Soft, Hard, Transport - it's level of error when operating with this device. For more inforamtion need
analyze /var/adm/messages.
Where fixed wha error happens and more detail information.
Regards.

SCSI transport failed error

Hi,
I am getting SCSI transport failed error on my Solaris 10 servers. iostat is reporting Hard & Transport errors.
I am able to access to lun and able to write data to it without any problem.
Questions:
1. what does this error mean?
2. could this impact the performance?
3. possible fix?
/scsi_vhci/ssd@g60a98000486e5a75576f4e4949586c42 (ssd0):
Jun 1 20:59:20 APP001 SCSI transport failed: reason 'tran_err': retrying command
Jun 1 21:00:41 APP001 scsi: WARNING: /scsi_vhci/ssd@g60a98000486e5a75576f4e4949586c42 (ssd0):
Jun 1 21:00:41 APP001 SCSI transport failed: reason 'timeout': retrying command
Jun 1 21:00:41 APP001 scsi: WARNING: /scsi_vhci/ssd@g60a98000486e5a75576f4e4949586c42 (ssd0):
Jun 1 21:00:41 APP001 SCSI transport failed: reason 'tran_err': retrying command
=========================
root@STFEMAPAPP001 # iostat -En
c1t0d0 Soft Errors: 2 Hard Errors: 0 Transport Errors: 0
Vendor: LSILOGIC Product: Logical Volume Revision: 3000 Serial No:
Size: 146.56GB <146561286144 bytes>
Media Error: 0 Device Not Ready: 0 No Device: 0 Recoverable: 0
Illegal Request: 2 Predictive Failure Analysis: 0
c0t0d0 Soft Errors: 3 Hard Errors: 0 Transport Errors: 0
Vendor: TSSTcorp Product: CD/DVDW TS-T632A Revision: SR03 Serial No:
Size: 0.00GB <0 bytes>
Media Error: 0 Device Not Ready: 0 No Device: 0 Recoverable: 0
Illegal Request: 3 Predictive Failure Analysis: 0
c6t60A98000486E5A75576F4E4949586C42d0 Soft Errors: 2 Hard Errors: 648 Transport Errors: 659
Vendor: NETAPP Product: LUN Revision: 0.2 Serial No:
Size: 107.36GB <107357405184 bytes>
Media Error: 0 Device Not Ready: 0 No Device: 0 Recoverable: 0
Illegal Request: 2 Predictive Failure Analysis:
Help appreciated.
Thanks.

it means that when the sun tried to send or recive data to the drive it could not. this could be cable or scsi controler. but the most likely proublem is your drive. i would get the data off and try a new drive be fore it fails.

Storedge 3510 changed logical path after installation

Hi everyone!
I have a E450 with 2 HBA conneted to a Storedge 3510, and I installed Solaris 10, but after that my storedge 3510 changed the original LUN's logical path. For example:
Before installation: c4t600601608ED80800C109FE8C4652DB11d0s2
After installation: c4t45d0
Does anybody know why I see this in a different way???
I need the old name!!!
THAHKS!!

Hi.
fcinfo hba-port Speed information etc.
luxadm -e port Show available FC-ports and him status.
luxadm -e dump_map <controller address from previos comand>
cfgadm -al
cfgadm -al -o show_FCP_dev
Try reconnect array.
You use direct connections or FC-switch?
I not sure but some-times can be damaged /kernel/drv/fp.conf
/kernel/drv/scsi_vhci.conf
Check it:
# grep -v "#" fp.conf
name="fp" class="fibre-channel" port=0;
name="fp" class="fibre-channel" port=1;
scsi-binding-set="fcp";
load-ulp-list="1","fcp";
ddi-forceattach=1;
mpxio-disable="yes";
# grep -v "#" scsi_vhci.conf
name="scsi_vhci" class="root";
load-balance="round-robin";
auto-failback="enable";
#Regards.

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

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

StorageTek 3510 FC Array - Unknown password

Hi,
We have 2 StorageTek 3510 FC Arrays which are password protected (bought "used")
How do I set it back to factory defaults to clear the password?
Thanks
Paul

Sun StorEdge 3000 Family CLI 2.4 User's Guide
[http://docs.sun.com/source/817-4951-17/preface.html]
Controller Commands
[http://docs.sun.com/source/817-4951-17/03_controller.html#81504]

Hard error for non PO duplicate invoice

Hi,
In FB60 for a non PO invoice, how can we restrict the duplicate invoice through reference number for different date and amounts. How can I create a hard error when the user posts a duplicate invoice for different amount and date. Right now the hard error is appearing for the reference num, same date and same amount.
I wanted to create a z function module and tag it to 1110 fucntion module in FIBF Tcode. But can anybody advice if any standard SAP process is available.
Thanks,
Vardhan.

No standard feature.
You can use the mentioned BTE in FIBF or a validation in GGB0/ OB28
Regards,
Gaurav

Material shortage ( soft or hard error ) while releasing production order?

Hi Guys
I am a SAP tech guy wrote a BDC program to release production order. It worked fine in one enviroment but not working another enviroment saying ..Material shortage.
My BDC program can't afford any hard errors in the process. The execution stop abruptly for any hard error.
How to change that Material shortage from hard error to soft error or any info message.
Any ideas? any thing to do with material master or spro?
Thanks
Hari

Hi
You can make settings in SPRO, so that the material availability check will not restrict you to go further...
follow the path:
SPRO>Production->Shop floor control>Operations->Availability Check-->Scope of check
There you will find the settings for order creation and release (1 & 2)..
You have remove the restriction there.
Regards
Bala

Unknown Hard Error when installing Windows XP?

Ok first off I tried installing Windows Vista Home Premium on my new 24in iMac and after installation had problems installing drivers. Found out it was because I had a 64 bit version of Vista and the iMacs dont support that. Then I got a copy of XP Home Service Pack 3 from a friend to try. Im not sure if it is 32 or 64 bit but I was going to try it anyways. Its starts to extract the files and get ready for the install but not long after it does that it gives me an unknown error and the blue screen of death.
"STOP: c0000221 Unknown Hard Error
\SystemRoot\System32\ntdll.dll"
Does anyone know what this means? I would really like to get one of them installed. I dont care which one...if anyone knows how I can put a 64bit version of Vista on my iMac that would probably be best since it installed fine and just messed up when installing the drivers. Otherwise can anyone tell me what to do about this unknown error? Or do I need to search around for yet another operating system cd?
Any help will be greatly appreciated.

Hi KadeP,
there is indeed not a solution for that CD-problem, since you are getting it when installing from the CD not after the installation, when there is a problem with that specific file on your harddisk.
So, apart from the checking of the CD for physical problems (dirt, dust, scratches) the only other solution would be the use of another CD and maybe doing a full disc-copy of that CD onto a CD-R or CD-RW and hoping the best.
As for the Vista procedures the hatter described, all these has to be done before even installing Vista and also on a Windows PC.
The outcome of that would be a modified Vista Installation DVD, which seems to be installing even on iMacs not really supported.
Since I don't have Vista I never tried it myself, though.
But the hatter is 'our local Vista/Windows 7 genius'
As for the 'old XP CD' you found:
such behaviour/error is usually a sign that the XP CD is not at Service Pack level 2 (SP2) which is a must for XP CDs.
However, you can use these instructions http://www.winsupersite.com/showcase/windowsxpsp2slipstream.asp to 'slipstream' yourself a XP SP2 installation CD.
But again, you have to do it on a running Windows PC.
Regards
Stefan

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.

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

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 FC Array Transport/Hard Errors

Similar Messages

Maybe you are looking for