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

Similar Messages

Slow Performance Expected from Beta Release?

LR3 runs like a dream on my machine. However, the Develop module in LR4 is quite sluggish - the sliders take a few seconds before the changes are visible.
Is this to be expected from a beta release, or is LR4 realy that much more resource-intensive?
Thank you,
~Steve

Both.

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 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.

How to configure StorEdge 3510 as a SAN?

Hi all, just joined!
We've got a StorEdge 3510 set up as a DAS (private loop mode) connected to three servers. We've gone through hell and high water getting things configured (firmware upgrades were particularly troublesome), but now that we've got everything running, we're starting to think about future expansion. However, despite my experimentation, I can't work out how to set them up in a switched fabric.
We have a test 3510 set up as Point-to-Point, connected to an Emulex 355 FC switch. In Loop mode, the device shows up as a SCSI device, but I can't get Windows to see anything on the end of the HBA when it's in PTP. Half the time, the HBA won't even acknowledge a link.
I can't work out where to start with this. The switch, admittedly, came from Apple with an Xserve RAID, but we've had the 3510 plugged into it in Loop mode and visible, so I don't think there's any problem with Apple ROM-ing the switch.
I've tried Zoning the switch, and Smart-Setting the ports to be Switched Fabrics, but nothing seems to make the StorEdge visible to the host. I thought that the test box might be at fault initially, since it has a Dell-EMC FC HBA and it wouldn't surprise me if it's ROM'd to EMC boxes only, but it seems that another box with a generic QLogic card won't see the StorEdge either.
Full tech specs of the system:
-3510 dual-controller, firmware 4.23A, 12 146GB 10K disks
-Emulex 355 12-port FC SAN Switch
-Dell PowerEdge 1850 with Emulex LP1050Ex-E PCI-E HBA
-Dell PowerEdge 2850 with QLogic QLA210 PCI HBA
-Windows Server 2003 x64
Any advice or starting points would be massively appreciated!
Thanks,
Rob

You are right in changing the A3510 to point to point
From:
sccli> sho host
max-luns-per-id: 32
queue-depth: 1024
fibre-connection-mode: loop
inband-management: enabled
To:
sccli> sho host
max-luns-per-id: 32
queue-depth: 1024
fibre-connection-mode: point-to-point
inband-management: enabled
The 3510 is now configured to work in a SAN.
In loop mode you will see the enclosure as an ses device. In point to point you won't, you will just see the available LUNs.
In P2P you should see all your configured logical volumes or disks with there WWN names on the hosts side
From:
sccli> show logical
LD LD-ID Size Assigned Type Disks Spare Failed Status
ld0 5E714957 545.91GB Primary RAID5 5 2 0 Good
Write-Policy Default StripeSize 128KB
ld1 1F4ABC1D 545.91GB Secondary RAID5 5 2 0 Good
Write-Policy Default StripeSize 128KB
with
Serial Number: 07FE18
You should see something like (these names are taken from a Solaris luxadm probe)
Node WWN:206000c0ff07fe18 Device Type:Disk device
Logical Path:/dev/rdsk/c7t600C0FF00000000007FE181F4ABC1D00d0s2
Node WWN:206000c0ff07fe18 Device Type:Disk device
Logical Path:/dev/rdsk/c7t600C0FF00000000007FE185E71495700d0s2
I don't have any clue how this would show up under windows. Putting a fabric on your switch should make things more tidy, but shouldn't fundamentally change anything.

SSAS Tabular Performance Issue moving from Laptop to Server

Hi all,
I've got an issue where my tabular model in SSAS on a Lenovo W520 laptop (DEV) is out-performing the same model on a Dell R720 server (details of each system below). Our unit tests involves 1 query that takes 2-3 seconds on the laptop
vs 12-15 seconds on the server. The main difference is the laptop is running Windows 7 Pro and the server is Windows Server 2012 R2.
So for some additional tests we did the following:
1. Loaded up the model on another laptop (same model and specs as before) the same way we moved the model over to the server and it performed as expected 2-3 seconds for the query.
2. Loaded up the model on a dell OptiPlex system (i3 processor, 8GB Ram, Win7 Pro) and runs 2-3 seconds still for the query.
3. Loaded up Win2k8R2 on the dell OptiPlex system (above) and still run 2- 3 seconds)
At this point we are thinking it is an OS issue between 2008R2 and Server 2012 R2 but not sure what the true difference is between the OS(s) that would cause such a huge performance difference. We thought it might be the power saving mode that ships
with 2012 R2 so set that performance but still seeing a long lag in the query.
Laptop Specs:
Lenovo W520
1 x i7 2.5GHz 2860QM Processor (8 Cores, )
16 GB Memory (DDR3, Dual)
Windows 7 Pro
Server Specs:
Dell R720
2 x E5-2697 V2 (12 Cores each, 2.7GHz, with turbo boost enabled)
4 x 32GB Memory (LRDIM 1866 MT/s)
Windows Server 2012 R2 (All latest updates and drivers)
There has to be some simple setting I'm missing in the 2012 R2 server that is causing this poor performance in SQL Server. I've seen folks in the tabular forums using Server 2012 R2 so there has to be a way to have this server perform better.
I'm about at my wits end on this one and reaching out for help from the experts out there. What advice can you give me?
Thanks in advance for any help you can provide!
Best regards,
Michael

Hi Michael,
Acording to your description, you encounter the perofrmance issue in SQL Server Analysis Services Tabular model, right?
as you increase the data load, add more users, or run complex queries, you need to have a strategy for maintaining and tuning performance. Here is a document that describes strategies and specific techniques for getting the best performance from your tabular
models, including processing and partitioning strategies, DAX query tuning, and server tuning for specific workloads.
http://msdn.microsoft.com/en-us/library/dn393915.aspx
Besides, if you cannot determine your answer here or on your own for a complex problem, consider opening a support case with Microsoft. Visit this link to see the various support options that are available to better meet your needs:
http://support.microsoft.com/default.aspx?id=fh;en-us;offerprophone
Regards,
Charlie Liao
TechNet Community Support

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

HT1752 I both one Mac Pro 15" March 2009 and five month ago I have to change the harddrive and put some actional memories, since I have to make the upgrade for Lion IOS. Now the motherboard fails. What should I do or expect from Apple to solve this probl

Hi everyone. I both a Mac Pro 15" in March 2009. Five month ago I was forced to buy by one new hard drive and extent the memory, because I had to make the upgrade (and pay) to install the new Lion operation system. Four days ago the Mother-board fails. To change it will cost a fortune. What should I do or expect from Apple to solve this problem? I am very disappointed because my trust on Apple was destroyed.

I am not sure why you are upset with Apple. Electronics equipment does fail. If the product is out of warranty or you do not have AppleCare there's not much you can do with Apple. Apple will charge you for the repair. Suggest you look for a third party repair store since they are usually less expensive than Apple. Alternatively you can buy one for about $850US and install it yourself. Sorry, but there aren't many choices in this situation.

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

What sort of functionality can I expect from Time Capsule in a Windows 7 environment?

I'm looking to use time capsule as a backup for all of our families photos and such. What kind of functionality can I expect from Windows 7 and Time Capsule.

You can use it as a network drive. You can also use it for automatic back-up purposes.

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.

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?

Pass parameter to ssrs report in performance point webpart from textbox text

How to pass parameter to ssrs report in performance point webpart from textbox text
Please help me to solve this ...
Bikky Kumar

Edit your SharePoint page and add new text filter web part.
Then pass the text filter value to your performance point report using connections. Your report should include at least one parameter to get the value. More over you can set default value in text filter.

Steps to setup MML on veritas Netbackup to perform rman restore from tape

RMAN backup is taken to tape...
can anyone please give the steps to setup the MML on veritas Netbackup ...
and also the steps to perform rman restore from tape to a new server ....
Thanks in advance

can u please answer them ..
1)how to find out that the which tape is mounted on a backup server ?? command please ....
2)how to find out that the rman backup was successful on the tape ?
3)how to find out what are the tapes involved in that backup ?
4)do u have to the create a auxillary database while restoring from rman by tape to a new server ?
5)is there a way to findout how many GB completed in x timeframe by RMAN on oracle 11.2.0.2/10g and and oracle 9i during the backup process ??
and also please answer ...
#)RMAN backup is taken to tape...
can anyone please give the steps to setup the MML on veritas Netbackup ...
and also the steps to perform rman restore from tape to a new server ....
and
#)--- can i know the steps for the MML
CATALOG command to define new locations
----May i know the commands

Can I perform persistence activities from within a JPA lifecycle event

I have a question about what is valid while inside JPA lifecycle events like @PrePersist or even Eclipselink lifecycles like postBuild. I would like to perform persist and delete operations from within these lifecycles, however they seem to get lost when the commit finally happens at the end of the transaction.
Is this not valid...and if not how to I perform persistence operations from within these lifecycles. For example I may want to delete objects from a @PostDelete.
Thanks.

I don't see any reason why doing a persist() or remove() from instead a JPA PrePersist or PostRemove event would not work. What is your code for your event? Make sure you use the same EntityManager.
For the EclipseLink events, most of the write events are raised during the commit, so it is too late to perform a JPA operation such as persist(). You can however use EclipseLink DatabaseQuery to insert or delete objects, but you need to be careful doing this. In general it may be better to put this logic in your application instead of events.
James : http://www.eclipselink.org

Performance to expect from a StorEdge 3510

Similar Messages

Maybe you are looking for