This discussion is archived
9 Replies Latest reply: Mar 22, 2011 10:11 AM by Nik RSS

do we need to install the data host proxy on the SUN server?

799683 Newbie
Currently Being Moderated
Hi folks,

Hopefully somebody can help me out here as I’m new to sun storage. Basically we have one 6140 arrays attached to Solaris servers. We have installed the CAM software on a CentOS system and connected to the array. We also created the VOLUMEs.

When we check the storage from the Solaris server, we can only see those single disks, but not the volumes we created.

Wandering do we need to install the proxy in the Solaris server to get those volume info?

Thanks,
  • 1. Re: do we need to install the data host proxy on the SUN server?
    Nik Expert
    Currently Being Moderated
    Hi.
    You not need install host proxy on solaris.

    Are you map new created volumes?
    You map to specific host or to default domain ?

    You use direct connectrions or FC-switch?
    What version of Solaris?

    Please show from Solaris results of commands

    luxadm -e port
    cfgadm -alv
    cfgadm -al -o show_FCP_dev
    for f in /dev/fc/fp*
    do
    echo $f
    luxadm -e dump_map $f
    done
    Regards
  • 2. Re: do we need to install the data host proxy on the SUN server?
    799683 Newbie
    Currently Being Moderated
    thanks for your reply.

    Yes, I tried to mapping the volume to host. But still the same.

    I did run all those commands, no any help for me at all. All I can see from the Solaris system ( Solaris 10) were the naked disks. NOT the volume.

    I finally give it up by using zfs file system for them.

    So you know any performance drawback by using ZFS instead of UFS?
  • 3. Re: do we need to install the data host proxy on the SUN server?
    Nik Expert
    Currently Being Moderated
    Hi.
    Previos list of commands for - for trubleshuting. So i hope see results. :)
    What mean: "naked disk not volume"?
    If you don't see volume from array how you plan use it for ZFS?

    About performance - it's ver depend of server configuration and aplication.
    ZFS give many features that not possible for any other FS. ZFS not alvays degrade performance.

    Regards.
  • 4. Re: do we need to install the data host proxy on the SUN server?
    799683 Newbie
    Currently Being Moderated
    unfortunately, I can not access this server right now.

    I can see all the hard disks ( like (c1t2d0, c1t2d1...), they are all the row disks. not the volume I created through CAM software.

    I created the ZFS pool through solaris system using "zfspool create ..." command.

    thanks,
  • 5. Re: do we need to install the data host proxy on the SUN server?
    Nik Expert
    Currently Being Moderated
    Hi!

    Are you sure that you see disk c1t2d1 ? General disk can not have LUN != 0 .


    It's not clear for me what difference you want see between raw disk and volume.


    You use FC-switch or direct attached storage?

    Do you enable multypathing ? stmsboot -e

    How many internal disks have server and how many disks you see in format ?

    Regards.
  • 6. Re: do we need to install the data host proxy on the SUN server?
    799683 Newbie
    Currently Being Moderated
    yes, I do see the raw disks c1t1d0...

    we dont use FC switch, instead we direct connect to host to the storage

    no, we didnt enable multipath

    we have 16 disks, and can see all of them through format.

    thanks,
  • 7. Re: do we need to install the data host proxy on the SUN server?
    Nik Expert
    Currently Being Moderated
    Hi.
    I ask: Are you sure that you see disk c1t2d1
    You answer: yes, I do see the raw disks c1t1d0

    You answer on different questions.
    What server you have with 16 disks?

    Please show result of format and commands from my first post.

    You should enable MPXIO for use this array correctly.
    Regards.
  • 8. Re: do we need to install the data host proxy on the SUN server?
    799683 Newbie
    Currently Being Moderated
    I enabled the MPXIO, still the same, please check the returns for the commands you requested:
    root@host:/# luxadm -e port
    /devices/pci@9,600000/SUNW,qlc@2/fp@0,0:devctl                     CONNECTED
    /devices/pci@8,600000/SUNW,emlxs@1/fp@0,0:devctl                   CONNECTED
    /devices/pci@8,600000/SUNW,emlxs@1,1/fp@0,0:devctl                 NOT CONNECTED
    root@snow:/# cfgadm -alv
    Ap_Id                          Receptacle   Occupant     Condition  Information
    When         Type         Busy     Phys_Id
    c0                             connected    configured   unknown
    unavailable  scsi-bus     n        /devices/pci@8,700000/ide@6:scsi
    c0::dsk/c0t0d0                 connected    configured   unknown    TOSHIBA ODD-DVD SD-C2732
    unavailable  CD-ROM       n        /devices/pci@8,700000/ide@6:scsi::dsk/c0t0d0
    c1                             connected    configured   unknown
    unavailable  fc-private   n        /devices/pci@9,600000/SUNW,qlc@2/fp@0,0:fc
    c1::21000014c3203319           connected    configured   unknown
    unavailable  disk         n        /devices/pci@9,600000/SUNW,qlc@2/fp@0,0:fc::21000014c3203319
    c1::21000014c3203e13           connected    configured   unknown
    unavailable  disk         n        /devices/pci@9,600000/SUNW,qlc@2/fp@0,0:fc::21000014c3203e13
    c2                             connected    configured   unknown
    unavailable  fc-private   n        /devices/pci@8,600000/SUNW,emlxs@1/fp@0,0:fc
    c2::22000024b6aaf918           connected    configured   unknown
    unavailable  disk         n        /devices/pci@8,600000/SUNW,emlxs@1/fp@0,0:fc::22000024b6aaf918
    c2::22000024b6aaf98d           connected    configured   unknown
    unavailable  disk         n        /devices/pci@8,600000/SUNW,emlxs@1/fp@0,0:fc::22000024b6aaf98d
    c2::22000024b6aaf9d6           connected    configured   unknown
    unavailable  disk         n        /devices/pci@8,600000/SUNW,emlxs@1/fp@0,0:fc::22000024b6aaf9d6
    c2::22000024b6abaabc           connected    configured   unknown
    unavailable  disk         n        /devices/pci@8,600000/SUNW,emlxs@1/fp@0,0:fc::22000024b6abaabc
    c2::22000024b6abba22           connected    configured   unknown
    unavailable  disk         n        /devices/pci@8,600000/SUNW,emlxs@1/fp@0,0:fc::22000024b6abba22
    c2::22000024b6abcb78           connected    configured   unknown
    unavailable  disk         n        /devices/pci@8,600000/SUNW,emlxs@1/fp@0,0:fc::22000024b6abcb78
    c2::22000024b6abce7e           connected    configured   unknown
    unavailable  disk         n        /devices/pci@8,600000/SUNW,emlxs@1/fp@0,0:fc::22000024b6abce7e
    c2::22000024b6adb82e           connected    configured   unknown
    unavailable  disk         n        /devices/pci@8,600000/SUNW,emlxs@1/fp@0,0:fc::22000024b6adb82e
    c2::22000024b6adba7f           connected    configured   unknown
    unavailable  disk         n        /devices/pci@8,600000/SUNW,emlxs@1/fp@0,0:fc::22000024b6adba7f
    c2::22000024b6adbd22           connected    configured   unknown
    unavailable  disk         n        /devices/pci@8,600000/SUNW,emlxs@1/fp@0,0:fc::22000024b6adbd22
    c2::22000024b6fc6c6a           connected    configured   unknown
    unavailable  disk         n        /devices/pci@8,600000/SUNW,emlxs@1/fp@0,0:fc::22000024b6fc6c6a
    c2::22000024b6fc6da6           connected    configured   unknown
    unavailable  disk         n        /devices/pci@8,600000/SUNW,emlxs@1/fp@0,0:fc::22000024b6fc6da6
    c2::22000024b6fc6ed0           connected    configured   unknown
    unavailable  disk         n        /devices/pci@8,600000/SUNW,emlxs@1/fp@0,0:fc::22000024b6fc6ed0
    c2::22000024b6fc71ba           connected    configured   unknown
    unavailable  disk         n        /devices/pci@8,600000/SUNW,emlxs@1/fp@0,0:fc::22000024b6fc71ba
    c2::22000024b6fc71c4           connected    configured   unknown
    unavailable  disk         n        /devices/pci@8,600000/SUNW,emlxs@1/fp@0,0:fc::22000024b6fc71c4
    c2::22000024b6fc72d8           connected    configured   unknown
    unavailable  disk         n        /devices/pci@8,600000/SUNW,emlxs@1/fp@0,0:fc::22000024b6fc72d8
    c3                             connected    unconfigured unknown
    unavailable  fc           n        /devices/pci@8,600000/SUNW,emlxs@1,1/fp@0,0:fc
    usb0/1                         empty        unconfigured ok
    unavailable  unknown      n        /devices/pci@9,700000/usb@1,3:1
    usb0/2                         empty        unconfigured ok
    unavailable  unknown      n        /devices/pci@9,700000/usb@1,3:2
    usb0/3                         empty        unconfigured ok
    unavailable  unknown      n        /devices/pci@9,700000/usb@1,3:3
    usb0/4                         empty        unconfigured ok
    unavailable  unknown      n        /devices/pci@9,700000/usb@1,3:4
    root@host:/# cfgadm -al -o show_FCP_dev
    Ap_Id                          Type         Receptacle   Occupant     Condition
    c1                             fc-private   connected    configured   unknown
    c1::21000014c3203319,0         disk         connected    configured   unknown
    c1::21000014c3203e13,0         disk         connected    configured   unknown
    c2                             fc-private   connected    configured   unknown
    c2::22000024b6aaf918,0         disk         connected    configured   unknown
    c2::22000024b6aaf98d,0         disk         connected    configured   unknown
    c2::22000024b6aaf9d6,0         disk         connected    configured   unknown
    c2::22000024b6abaabc,0         disk         connected    configured   unknown
    c2::22000024b6abba22,0         disk         connected    configured   unknown
    c2::22000024b6abcb78,0         disk         connected    configured   unknown
    c2::22000024b6abce7e,0         disk         connected    configured   unknown
    c2::22000024b6adb82e,0         disk         connected    configured   unknown
    c2::22000024b6adba7f,0         disk         connected    configured   unknown
    c2::22000024b6adbd22,0         disk         connected    configured   unknown
    c2::22000024b6fc6c6a,0         disk         connected    configured   unknown
    c2::22000024b6fc6da6,0         disk         connected    configured   unknown
    c2::22000024b6fc6ed0,0         disk         connected    configured   unknown
    c2::22000024b6fc71ba,0         disk         connected    configured   unknown
    c2::22000024b6fc71c4,0         disk         connected    configured   unknown
    c2::22000024b6fc72d8,0         disk         connected    configured   unknown
    c3                             fc           connected    unconfigured unknown
    root@host:/# for f in /dev/fc/fp*
    
    do
    echo $f
    luxadm -e dump_map $f
    done
    /dev/fc/fp0 Pos AL_PA ID Hard_Addr Port WWN         Node WWN         Type 0     1   7d    0      21000003badbcc5b 20000003badbcc5b 0x1f (Unknown Type,Host Bus Adapter) 1     ef  0     ef     21000014c3203e13 20000014c3203e13 0x0  (Disk device) 2     e8  1     e8     21000014c3203319 20000014c3203319 0x0  (Disk device) /dev/fc/fp1 Pos AL_PA ID Hard_Addr Port WWN         Node WWN         Type 0     2   7c    0      10000000c97c2c86 20000000c97c2c86 0x1f (Unknown Type,Host Bus Adapter) 1     ce  f     ce     22000024b6fc6da6 20000024b6fc6da6 0x0  (Disk device) 2     d1  e     d1     22000024b6fc6c6a 20000024b6fc6c6a 0x0  (Disk device) 3     d2  d     d2     22000024b6fc71ba 20000024b6fc71ba 0x0  (Disk device) 4     d3  c     d3     22000024b6aaf918 20000024b6aaf918 0x0  (Disk device) 5     d4  b     d4     22000024b6abcb78 20000024b6abcb78 0x0  (Disk device) 6     d5  a     d5     22000024b6abaabc 20000024b6abaabc 0x0  (Disk device) 7     d6  9     d6     22000024b6aaf9d6 20000024b6aaf9d6 0x0  (Disk device) 8     d9  8     d9     22000024b6fc6ed0 20000024b6fc6ed0 0x0  (Disk device) 9     da  7     da     22000024b6abba22 20000024b6abba22 0x0  (Disk device) 10    dc  6     dc     22000024b6fc71c4 20000024b6fc71c4 0x0  (Disk device) 11    e0  5     e0     22000024b6fc72d8 20000024b6fc72d8 0x0  (Disk device) 12    e1  4     e1     22000024b6adbd22 20000024b6adbd22 0x0  (Disk device) 13    e2  3     e2     22000024b6abce7e 20000024b6abce7e 0x0  (Disk device) 14    e4  2     e4     22000024b6adb82e 20000024b6adb82e 0x0  (Disk device) 15    e8  1     e8     22000024b6adba7f 20000024b6adba7f 0x0  (Disk device) 16    ef  0     ef     22000024b6aaf98d 20000024b6aaf98d 0x0  (Disk device) /dev/fc/fp2 No devices are found on /dev/fc/fp2. root@host:/# format Searching for disks...done AVAILABLE DISK SELECTIONS:        0. c4t20000014C3203E13d0 <SUN146G cyl 14087 alt 2 hd 24 sec 848>           /scsi_vhci/ssd@g20000014c3203e13        1. c4t20000014C3203319d0 <SEAGATE-ST314670FSUN146G-055A cyl 14087 alt 2 hd 24 sec 848>           /scsi_vhci/ssd@g20000014c3203319        2. c4t20000024B6AAF9D6d0 <SEAGATE-ST3300657FC-0006-279.40GB>           /scsi_vhci/ssd@g20000024b6aaf9d6        3. c4t20000024B6AAF98Dd0 <SEAGATE-ST3300657FC-0006-279.40GB>           /scsi_vhci/ssd@g20000024b6aaf98d        4. c4t20000024B6AAF918d0 <SEAGATE-ST3300657FC-0006-279.40GB>           /scsi_vhci/ssd@g20000024b6aaf918        5. c4t20000024B6ABAABCd0 <SEAGATE-ST3300657FC-0006-279.40GB>           /scsi_vhci/ssd@g20000024b6abaabc        6. c4t20000024B6ABBA22d0 <SEAGATE-ST3300657FC-0006-279.40GB>           /scsi_vhci/ssd@g20000024b6abba22        7. c4t20000024B6ABCB78d0 <SEAGATE-ST3300657FC-0006-279.40GB>           /scsi_vhci/ssd@g20000024b6abcb78        8. c4t20000024B6ABCE7Ed0 <SEAGATE-ST3300657FC-0006-279.40GB>           /scsi_vhci/ssd@g20000024b6abce7e        9. c4t20000024B6ADB82Ed0 <SEAGATE-ST3300657FC-0006-279.40GB>           /scsi_vhci/ssd@g20000024b6adb82e       10. c4t20000024B6ADBA7Fd0 <SEAGATE-ST3300657FC-0006-279.40GB>           /scsi_vhci/ssd@g20000024b6adba7f       11. c4t20000024B6ADBD22d0 <SEAGATE-ST3300657FC-0006-279.40GB>           /scsi_vhci/ssd@g20000024b6adbd22       12. c4t20000024B6FC6C6Ad0 <SEAGATE-ST3300657FC-0006-279.40GB>           /scsi_vhci/ssd@g20000024b6fc6c6a       13. c4t20000024B6FC6DA6d0 <SEAGATE-ST3300657FC-0006-279.40GB>           /scsi_vhci/ssd@g20000024b6fc6da6       14. c4t20000024B6FC6ED0d0 <SEAGATE-ST3300657FC-0006-279.40GB>           /scsi_vhci/ssd@g20000024b6fc6ed0       15. c4t20000024B6FC71BAd0 <SEAGATE-ST3300657FC-0006-279.40GB>           /scsi_vhci/ssd@g20000024b6fc71ba       16. c4t20000024B6FC71C4d0 <SEAGATE-ST3300657FC-0006-279.40GB>           /scsi_vhci/ssd@g20000024b6fc71c4       17. c4t20000024B6FC72D8d0 <SEAGATE-ST3300657FC-0006-279.40GB>           /scsi_vhci/ssd@g20000024b6fc72d8 Specify disk (enter its number): ^C
  • 9. Re: do we need to install the data host proxy on the SUN server?
    Nik Expert
    Currently Being Moderated
    Hi.
    Please read manual for 6140.
    You connect you server to uncorrect port of 6140. (Port expansion insted Host Port).
    http://download.oracle.com/docs/cd/E19381-01/819-7497-11/819-7497-11.pdf Page 76. FIGURE 3-2
    You connect only one HBA to 6140. For redumdancy and performance - you should connect both HBA to different controllers of 6140.

    Please, connect storage correctly.

    In case you write anything on disk 300GB, you damage virtual disk on 6140.
    So after correct connecting 6140 restart it, check status of all volumes. Best - recreate all.

    Regards.

Legend

  • Correct Answers - 10 points
  • Helpful Answers - 5 points