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

Similar Messages

  • My ipod shuffle(2nd gen) is not visible on  itunes, i have downloaded latest version of itunes on my pc, how do i solve the problem ?

    My ipod shuffle(2nd gen) is not visible on  itunes, i have downloaded latest version of itunes on my pc, how do i solve the problem ?

    Hope the below link may help you to fix your issue:
    http://support.apple.com/kb/TS3716

  • 3510 Not visible  in Solris 8

    Dear ALL,
    I have a 3510 storedge with sun fire 490 server.i installed solaris 8 ,recommended os patches,san packages,san patches.i have created one ld in storedge ,but it is not visible in Solaris server.
    OK prompt it is detecting,but in solaris 8 it is not dectecting.My solaris is 2/04 .please give some suggestions.

    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

  • 2nd gen iPod not visible on Desktop or in iTunes

    I have a 40GB 2nd gen iPod that works fine and until recently always appeared on the Desktop and in iTunes whenever connected. Haven't had any problems with the iPod or iTunes. Now it is not visible at all but it does still recharge.
    It's connected with FireWire 400 but it doesn't show up in System Profiler or Disk Utility.
    I've reset it. I've forced Disk Mode. Nothing works.
    Another thing... I have my whole music collection stored on an external LaCie drive and connected to the laptop with FireWire 800. iTunes works fine, though, whenever I connect the iPod to the laptop, iTunes stops playing (the spinning colorwheel appears) and as soon as I disconnect the iPod, I hear the external drive kick in and iTunes resumes playing.
    Please help! Thank you.

    Thank you for your reply, socrates.
    I always connect the iPod into my Powerbook via FireWire 400 and the external LaCie is connected to the laptop via FireWire 800. So, there is no daisy-chain setup.
    Actually, I've just realized that my iPod is 3rd generation not 2nd. When I looked at the "Settings" on the iPod it says Version: 2.3 so I thought that meant 2nd generation but just discovered otherwise. Is there any way that I can change the title of the thread?
    And any more advice would be much appreciated. Thanks.

  • Physical Disks in StorEdge 3320 not visible in CLI Manager

    Hello,
    After installing the CLI manager on Solaris 10 for x86 platforms, I was able to connect the server to the StorEdge array. However, I cannot see the 6 physical disks that are in the array. The LEDs on the physical disks are green, but there is just no communication between them and the CLI manager. Could this be a bad controller card? What else could it be?
    DannyMac

    Where are you looking for the physical disks?

  • StorEdge 3510: can't newfs on Solaris 10

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

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

  • Purchased songs and movies not visible on 2nd computer in Store

    Hi.
    Purchased songs and movies not visible on 2nd computer in Store. To confirm I went to re-purchase and received message telling me it was already purchased. Heeeelllppp! <smile>

    The purchased content will only be on the computer you actually downloaded it to unless you somehow move it to the other computer. You could burn content to a CD or DVD, use an external hard drive, a thumb drive, a network connection or, if you have one, an iPod.

  • 2nd Internal Hard Disk Not visible on desktop

    Hello,
    Last night I was trying to rename some files and my G5 was acting very slowly. I relaunched the finder and it seemed to fix the problem. I resumed renaming files and it kept locking up. After the fourth time this happened, the system locked up and I pushed the front power button until the system shut down. When I turned the computer back on, my second internal hard drive was not visible. I looked in disk utility and did not see it, and it is also not visible in about this mac. Help!!!

    HI
    I have a similar problem that the second drive does not always appear on starting up from cold but usualy appears on a hot restart
    second drive is a Hitachi HDS725050KLA360 primary drive: HDS725050KLA360 (465.76 GB)
    (Telephone support was useless)
    It has been operating since March Photoshop and Aperture applications I do power down every night.
    And back up to external just in case I loose it but would prefer to have more confidence in its reliability
    Has anyone else had similar experience ? and any idea what might be the cause?

  • Mac mini (Server) 2010 - 2nd HDD not visible

    I have a Mac mini (Server) running Mavericks Server. The second HDD is visible on Disk Utility and About\MoreInfo\Storage, but is not visible on the finder or desktop (the preferences are set correctly).
    I can see the ammoutn of files/folders in the drive via Disk Utility. Other users in the network can see the drive. I can verify the disk, but I cant seem to verify perfmision. Its grayed out.
    If I try to unmount/mount the drive via Disk Utility it fails.
    Any idea?

    Triple-click anywhere in the line below on this page to select it:
    ls -@Oaen /V* | open -ef
    Copy the selected text to the Clipboard by pressing the key combination command-C.
    Launch the Terminal application in any of the following ways:
    ☞ Enter the first few letters of its name into a Spotlight search. Select it in the results (it should be at the top.)
    ☞ In the Finder, select Go ▹ Utilities from the menu bar, or press the key combination shift-command-U. The application is in the folder that opens.
    ☞ Open LaunchPad. Click Utilities, then Terminal in the icon grid.
    Paste into the Terminal window by pressing the key combination command-V. I've tested these instructions only with the Safari web browser. If you use another browser, you may have to press the return key after pasting.
    Wait for a new line ending in a dollar sign (“$”) to appear.
    A TextEdit window will open with the output of the command. If the command produced no output, the window will be empty. Post the contents of the TextEdit window (not the Terminal window), if any — the text, please, not a screenshot. The title of the window doesn't matter, and you don't need to post that.
    If any personal information appears in the output, anonymize before posting, but don’t remove the context.

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

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

  • 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

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

Maybe you are looking for