‘How do you add StoreOnce Devices to a HP VSE guest?

I have an admin who has the question "‘How do you add StoreOnce Devices to a HP VSE guest?’". Our HPVM is running HP-UX 11.31 and HPVM Version B.06.30.05. I can 'see' the Catalyst over Fiber on the host but am unable to get it visible on the guests. Any whitepaper? Docs?   the CM is also running HP-UX 11.31 and DP 9.07.  The Catalyst over Fibre works like a charm o nthe stand alone systems...

Here is the fiber on the host system.
(root@s928-dvsapvm1)# ioscan -fun | grep -i cofc
ctl 9 0/0/0/3/0/0/0.11.129.255.0.0.0 sctl CLAIMED DEVICE HP StoreOnce CoFC
ctl 10 0/0/0/3/0/0/0.11.129.255.0.0.1 sctl CLAIMED DEVICE HP StoreOnce CoFC
ctl 11 0/0/0/3/0/0/0.11.129.255.0.0.2 sctl CLAIMED DEVICE HP StoreOnce CoFC
ctl 12 0/0/0/3/0/0/0.11.129.255.0.0.3 sctl CLAIMED DEVICE HP StoreOnce CoFC
ctl 13 0/0/0/3/0/0/0.11.129.255.0.0.4 sctl CLAIMED DEVICE HP StoreOnce CoFC
ctl 14 0/0/0/3/0/0/0.11.129.255.0.0.5 sctl CLAIMED DEVICE HP StoreOnce CoFC
ctl 15 0/0/0/3/0/0/0.11.129.255.0.0.6 sctl CLAIMED DEVICE HP StoreOnce CoFC
ctl 16 0/0/0/3/0/0/0.11.129.255.0.0.7 sctl CLAIMED DEVICE HP StoreOnce CoFC
ctl 25 0/0/0/9/0/0/0.12.129.255.0.0.0 sctl CLAIMED DEVICE HP StoreOnce CoFC
ctl 26 0/0/0/9/0/0/0.12.129.255.0.0.1 sctl CLAIMED DEVICE HP StoreOnce CoFC
ctl 27 0/0/0/9/0/0/0.12.129.255.0.0.2 sctl CLAIMED DEVICE HP StoreOnce CoFC
ctl 28 0/0/0/9/0/0/0.12.129.255.0.0.3 sctl CLAIMED DEVICE HP StoreOnce CoFC
ctl 29 0/0/0/9/0/0/0.12.129.255.0.0.4 sctl CLAIMED DEVICE HP StoreOnce CoFC
ctl 30 0/0/0/9/0/0/0.12.129.255.0.0.5 sctl CLAIMED DEVICE HP StoreOnce CoFC
ctl 31 0/0/0/9/0/0/0.12.129.255.0.0.6 sctl CLAIMED DEVICE HP StoreOnce CoFC
ctl 32 0/0/0/9/0/0/0.12.129.255.0.0.7 sctl CLAIMED DEVICE HP StoreOnce CoFC

Tags:

Parents
  • Hi Vince,

    I´m not sure if your ioscan was executed at the HP VM Hypervisor or inside of virtual machine.

    If it was the VM add the "N" because if using HPVM NPIV Stor Adapter you will have only persistent devices.

    An "ioscan -fun" instead of "ioscan -funN" is nearly empty in a VM.

    I´m very happy with NPIV under HP-UX. Works great. I can have "direct" attached devices like LTO6, VTL, 3par, EVA inside of VM. Evainfo and 3parinfo are working too. Try this with Hyper-V or VMware.... ;-)

    Hope this helps a little bit.

    Mathias

     

     


  • @Datenverarbeitung wrote:

    I´m not sure if your ioscan was executed at the HP VM Hypervisor or inside of virtual machine.

    If it was the VM add the "N" because if using HPVM NPIV Stor Adapter you will have only persistent devices.

    An "ioscan -fun" instead of "ioscan -funN" is nearly empty in a VM.

    I´m very happy with NPIV under HP-UX. Works great. I can have "direct" attached devices like LTO6, VTL, 3par, EVA inside of VM. Evainfo and 3parinfo are working too. Try this with Hyper-V or VMware.... ;-)


     

    Was the VM Host.  I am trying figure out how to the the fiber from the host visible to the guests so I can use CofC.   Having no class on HPVM makes for a lot of reading.  If you guys have done it can I reach out to you directly?

     

    Vince

Reply

  • @Datenverarbeitung wrote:

    I´m not sure if your ioscan was executed at the HP VM Hypervisor or inside of virtual machine.

    If it was the VM add the "N" because if using HPVM NPIV Stor Adapter you will have only persistent devices.

    An "ioscan -fun" instead of "ioscan -funN" is nearly empty in a VM.

    I´m very happy with NPIV under HP-UX. Works great. I can have "direct" attached devices like LTO6, VTL, 3par, EVA inside of VM. Evainfo and 3parinfo are working too. Try this with Hyper-V or VMware.... ;-)


     

    Was the VM Host.  I am trying figure out how to the the fiber from the host visible to the guests so I can use CofC.   Having no class on HPVM makes for a lot of reading.  If you guys have done it can I reach out to you directly?

     

    Vince

Children
  • I don't see that Mathias is using StoreOnce Catalyst. Pass-through of other devices such as physical and virtual tape is supported according to the matrix.

    Please use the Accept Solution button next to my post and assign a KUDO (thumbs up icon) if this works for you.

    Regards,
    Sebastian Koehler

  • Hello Sebastian,

    you are right, I don´t use the catalyst.

    But when working with HPVM in a FC environment I would recommend generally to use NPIV. It is a very little effort to setup an GUID server. After that the configuration of a VM is very simple because we avoid to add some disks and tapes or whatever. Simply adding the NPIV- HBA and present whatever to this HBA. I´m sure this will also work for CoFC.

    If this is fully supported by HP (or HPE or HPE_MF....) is a different question..... ;-)

    @Vince

    As an example, this is a little VM:

    root # hpvmstatus -d -P vm
    [Virtual Machine Devices]

    [Storage Interface Details]
    hba:avio_stor:0,1,0x50014C2xxxx00021,0x50014C28xxxx001F:npiv:/dev/fcd0
    hba:avio_stor:0,2,0x50014C2xxxx00022,0x50014C28xxxx0020:npiv:/dev/fcd1

    [Network Interface Details]
    network:avio_lan:0,0,0x266A5DC6xxxx:vswitch:VSwitch.1:portid:5
    [Direct I/O Interface Details]

    [Misc Interface Details]
    serial:com1::tty:console

    That´s it. Setup such VM is done in 4 steps:

    /opt/hpvm/bin/hpvmcreate -P vm -O HPUX -c 2 -r 8G -e 50 -B manual
    /opt/hpvm/bin/hpvmmodify -P vm -a network:avio_lan:,,26-6a-5d-c6-xx-xx:vswitch:VSwitch.1
    /opt/hpvm/bin/hpvmmodify -P vm -a hba:avio_stor:0,1,::/dev/fcd0
    /opt/hpvm/bin/hpvmmodify -P vm -a hba:avio_stor:0,2,::/dev/fcd1

    Without configured GUID server you have to give a unique WWN by yourself when adding HBA.

    vm:/root # ioscan -funN
    Class I H/W Path Driver S/W State H/W Type Description
    =================================================================================
    ext_bus 0 0/0/0/0 gvsd CLAIMED INTERFACE HPVM NPIV Stor Adapter
    /dev/gvsd0
    ext_bus 2 0/0/1/0 gvsd CLAIMED INTERFACE HPVM NPIV Stor Adapter
    /dev/gvsd2
    lan 0 0/0/2/0 igssn CLAIMED INTERFACE HP IGSSN PCI AVIO LAN Adapter
    tty 0 0/0/3/0/1 asio0 CLAIMED INTERFACE Built-in RS-232C
    /dev/diag/mux0 /dev/mux0 /dev/tty0p0
    pseudo 1 0/0/4/0 hpvmdynmem CLAIMED INTERFACE PCI class(0,0) (103c12d8)
    pseudo 0 0/0/5/0 hpvmguestdvr CLAIMED INTERFACE PCI class(0,0) (103c7108)
    ipmi 0 250/0 ipmi CLAIMED INTERFACE IPMI Controller
    /dev/ipmi
    acpi_node 0 250/1 acpi_node CLAIMED INTERFACE Acpi Hardware
    usbmsvbus 0 64000/0x0 mass_storage CLAIMED VIRTBUS USB Mass Storage
    escsi_ctlr 0 64000/0x0/0x0 usb_ms_scsi CLAIMED INTERFACE USB Mass Storage Virt Ctlr
    ctl 0 64000/0xfa00/0x0 esctl CLAIMED DEVICE HP HSV400
    /dev/pt/pt0
    disk 0 64000/0xfa00/0x14 esdisk CLAIMED DEVICE HP HSV400
    /dev/disk/disk0 /dev/disk/disk0_p2 /dev/rdisk/disk0 /dev/rdisk/disk0_p2
    /dev/disk/disk0_p1 /dev/disk/disk0_p3 /dev/rdisk/disk0_p1 /dev/rdisk/disk0_p3
    tape 38 64000/0xfa00/0x28 estape CLAIMED DEVICE HP Ultrium 4-SCSI
    /dev/rtape/tape38_BEST /dev/rtape/tape38_BESTn
    /dev/rtape/tape38_BESTb /dev/rtape/tape38_BESTnb
    snip

    autoch 3 64000/0xfa00/0x2e eschgr CLAIMED DEVICE HP MSL G3 Series
    /dev/rchgr/autoch3
    disk 1 64000/0xfa00/0xba esdisk CLAIMED DEVICE HP HSV400
    /dev/disk/disk1 /dev/rdisk/disk1
    disk 2 64000/0xfa00/0xbb esdisk CLAIMED DEVICE HP HSV400
    /dev/disk/disk2 /dev/rdisk/disk2
    tape 44 64000/0xfa00/0xc8 estape CLAIMED DEVICE HP Ultrium 6-SCSI
    /dev/rtape/tape44_BEST /dev/rtape/tape44_BESTn
    /dev/rtape/tape44_BESTb /dev/rtape/tape44_BESTnb
    snip

    autoch 5 64000/0xfa00/0xcc eschgr CLAIMED DEVICE HP MSL6480
    /dev/rchgr/autoch5
    tape 48 64000/0xfa00/0xd9 estape CLAIMED DEVICE HP Ultrium 6-SCSI
    /dev/rtape/tape48_BEST /dev/rtape/tape48_BESTn
    /dev/rtape/tape48_BESTb /dev/rtape/tape48_BESTnb
    snip

    tape 52 64000/0xfa00/0xea estape CLAIMED DEVICE HP Ultrium VT
    /dev/rtape/tape52_BEST /dev/rtape/tape52_BESTn
    /dev/rtape/tape52_BESTb /dev/rtape/tape52_BESTnb
    tape 53 64000/0xfa00/0xeb estape CLAIMED DEVICE HP Ultrium VT
    /dev/rtape/tape53_BEST /dev/rtape/tape53_BESTn
    /dev/rtape/tape53_BESTb /dev/rtape/tape53_BESTnb

  • Thanks for the update!  As soon as the fires die down here a bit I will attempt anmd post what has been suggested.  Sorry for being quiet but I am also the DBA and had a few systems to restore recently.  Fun never ends.

    -Vince

  • OK... so on my HPVM host I have this:

    (root@s928-dvsapvm1)# ioscan -funC fc

    Class I H/W Path Driver S/W State H/W Type Description

    =====================================================================

    fc 0 0/0/0/3/0/0/0 fcd CLAIMED INTERFACE HP SN1000Q 16Gb Dual Port PCIe Fibre Channel Adapter (FC Port 1)

    /dev/fcd0

    fc 1 0/0/0/3/0/0/1 fcd CLAIMED INTERFACE HP SN1000Q 16Gb Dual Port PCIe Fibre Channel Adapter (FC Port 2)

    /dev/fcd1

    fc 2 0/0/0/9/0/0/0 fcd CLAIMED INTERFACE HP SN1000Q 16Gb Dual Port PCIe Fibre Channel Adapter (FC Port 1)

    /dev/fcd2

    fc 3 0/0/0/9/0/0/1 fcd CLAIMED INTERFACE HP SN1000Q 16Gb Dual Port PCIe Fibre Channel Adapter (FC Port 2)

    /dev/fcd3

     

    On, for example, one of my guests I have this:

    (root@s928-dvsapvm1)# hpvmstatus -d -P s928-dbsapet1

    [Virtual Machine Devices]

    [Storage Interface Details]

    disk:avio_stor:0,0,0:lv:/dev/vgvms/rlvtrn_vg00

    [Network Interface Details]

    network:avio_lan:0,1,0x3A81D4A74E0A:vswitch:EntLAN:portid:2

    network:avio_lan:0,2,0xE63AFC49E895:vswitch:BKLAN:portid:1

    [Direct I/O Interface Details]

    [Misc Interface Details]

    serial:com1::tty:console

     

    Did it get set up wrong?  Or can I add a fiber connection like your example (to one that supports NPIV)?

  • Hi Vince,

    The VM Config is OK, but without access to your SAN. If you want to have SAN access read "HP-UX vPars and Integrity VM v6.4
    Administrator Guide" and specially chapter 7 "NPIV with vPars and Integrity VM".  Trust me, NPIV is very easy to use.  If you have your GUID server running you can create a VM with virtualized HBA in minutes. After that you have to zone this HBA in the same way as physical HBA´s,.

    Keep in mind that using rlvol´s   as VM- disk is the slowest way....

     


  • @Datenverarbeitung wrote:

     

    The VM Config is OK, but without access to your SAN. If you want to have SAN access read "HP-UX vPars and Integrity VM v6.4
    Administrator Guide" and specially chapter 7 "NPIV with vPars and Integrity VM".  Trust me, NPIV is very easy to use.  If you have your GUID server running you can create a VM with virtualized HBA in minutes. After that you have to zone this HBA in the same way as physical HBA´s,.

    Keep in mind that using rlvol´s   as VM- disk is the slowest way....

     


    I wish the guy doing the setup would reply...  I dislike being the middle man.

    Apparently the guests can see the SAN the way he set it up - just not the fiber.  The Admin also says disk/SAN performance is not a concern at this point.  His concern is being able to back it up. That is where me (and my one StoreOnce class) comes in. 

    The GUID server is currently apparently not an option since it would require many hoops to jump through just to get it installed in a production environment.  He, and I, are unsure of it's impact on any other server/service in our environment. 

    THAT being said... he said to go ahead and make up a WWN and try to get fiber working that way. SO, on my HPVM Host I have this: 

    root@server# fcmsutil /dev/fcd0 npiv_info
    PFC Hardware Path              = 0/0/0/3/0/0/0
    PFC DSF                        = /dev/fcd0
    PFC Class Instance             = 0
    PFC Driver state               = ONLINE
    PFC Port WWN                   = 0x51402ec0005f6ad8
    PFC Node WWN                   = 0x51402ec0005f6ad9
    PFC Switch Port WWN            = 0x20990027f8a91200
    PFC Switch Node WWN            = 0x10000027f8a91200

    When I tried one way, it didn't work and want's WWN.  not sure what WWN goes where and don't I want a "fc" and not "hba" if I am going to try to do Catalyst over Fiber (See my first post in this thread).

    (root@server)# hpvmmodify -P s928-dbsapeq1 -a hba:avio_stor:0,1,::/dev/fcd0

    hpvmmodify: Missing required device fields.

    hpvmmodify: Invalid backing type ''.

    hpvmmodify: Invalid value specified with the -a option (hba:avio_stor:0,1,::/dev/fcd0)

    Any suggestions that would help me move this along?

    Thanks!

     

  • sorry for delay ;-)

    In you command the word NPIV was missing, try this:

    hpvmmodify -P s928-dbsapeq1 -a hba:avio_stor:0,1,::npiv:/dev/fcd0

    Without GUID server maybe you run into the next trap and you have to define your own WWN´s ....

    Mathias