<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: How to attaching disks to a integrity vm in Operating System - HP-UX</title>
    <link>https://community.hpe.com/t5/operating-system-hp-ux/how-to-attaching-disks-to-a-integrity-vm/m-p/6149185#M521710</link>
    <description>&lt;P&gt;Hi, i'm starting to install the NPIV on my npar and vm. But i'm having a connection problem between the server and client. This is the message:&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;# /opt/guid/bin/guid_client_prepare -a&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;NOTE:&lt;BR /&gt;&amp;nbsp;We found Host is configured in /opt/guid/etc/guid.conf. This&lt;BR /&gt;may because current machine has been once installed and&lt;BR /&gt;configured as a GUID client.&amp;nbsp; Or user has defined hostname in&lt;BR /&gt;guid.conf by CLI tool "guidconfig -h".&lt;BR /&gt;&amp;nbsp;In this case, we only try setting up authentications between&lt;BR /&gt;current client and remote GUID servers, which are configured&lt;BR /&gt;in HOST.&lt;BR /&gt;&lt;BR /&gt;Install pubkey on GUID server(sd16dom2) succeeded.&lt;BR /&gt;&lt;BR /&gt;Connect to host sd16dom2 failed. ---&amp;gt; NOTE: BOTH SERVERS ARE IN THE SAME SUBNET&lt;BR /&gt;&lt;BR /&gt;ListRange of wwn from GUID server(sd16dom2) failed.&lt;BR /&gt;&lt;BR /&gt;GUIDMGR client preparation accomplished.&lt;BR /&gt;&lt;BR /&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Some suggestion ??.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Regards&lt;/P&gt;</description>
    <pubDate>Fri, 26 Jul 2013 16:51:33 GMT</pubDate>
    <dc:creator>iazuarah</dc:creator>
    <dc:date>2013-07-26T16:51:33Z</dc:date>
    <item>
      <title>How to attaching disks to a integrity vm</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/how-to-attaching-disks-to-a-integrity-vm/m-p/6146369#M521702</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I have a Superdome 2 16s server. In this server i had 2 npars and each one, will define several vm's. I'm using the last release for Integrity VM on the npar:&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;vmGuestLib&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; B.06.20&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; Integrity VM vmGuestLib&lt;BR /&gt;vmGuestSW&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; B.06.20&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; Integrity VM vmGuestSW&lt;BR /&gt;vmKernel&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; B.06.20&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; Integrity VM vmKernel&lt;BR /&gt;vmOVMMSW&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; B.06.20&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; Integrity VM vmOVMMSW&lt;BR /&gt;vmProvider&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; B.06.20&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; WBEM Provider for Integrity VM vmProvide&lt;BR /&gt;vmVirtProvider&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; B.06.20&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; Integrity VM vmVirtProvider&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;My external disks comes from a Hitachi Storage Server that is connected to different fiber channel hbas installed in different IOX.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;This fc hbas are managed by the Npar2:&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;sd16dom2_npar2# ioscan -fnkC fc&lt;/STRONG&gt;&lt;BR /&gt;Class&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; I&amp;nbsp; H/W Path&amp;nbsp; Driver S/W State&amp;nbsp;&amp;nbsp; H/W Type&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; Description&lt;BR /&gt;=================================================================&lt;BR /&gt;fc&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; 0&amp;nbsp; 42/0/0/2/0/0/0/5/0/0/0&amp;nbsp; fclp&amp;nbsp;&amp;nbsp; CLAIMED&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; INTERFACE&amp;nbsp;&amp;nbsp;&amp;nbsp; HP AT094-60001 PCIe Fibre Channel 2-port 8Gb FC/2-port 10GBE Combo Adapter&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; /dev/fclp0&lt;BR /&gt;fc&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; 20&amp;nbsp; 45/0/2/0/0/0/0/5/0/0/0&amp;nbsp; fclp&amp;nbsp;&amp;nbsp; CLAIMED&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; INTERFACE&amp;nbsp;&amp;nbsp;&amp;nbsp; HP AT094-60001 PCIe Fibre Channel 2-port 8Gb FC/2-port 10GBE Combo Adapter&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; /dev/fclp20&lt;BR /&gt;&lt;BR /&gt;When i run the ioscan command on my Npar2, i can discover the disks that will assign to the vm1. In this case are 4 disks (disk21, disk22, disk23, disk24).&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;NPAR2&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;sd16dom2_npar2# hpvmstatus&lt;/STRONG&gt;&lt;BR /&gt;[Virtual Machines]&lt;BR /&gt;Virtual Machine Name VM #&amp;nbsp; Type OS Type&amp;nbsp;&amp;nbsp; State&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; #VCPUs&amp;nbsp; #Devs&amp;nbsp; #Nets&amp;nbsp; Memory&lt;BR /&gt;==================== ===== ==== ======= ========= ====== ===== ===== =======&lt;BR /&gt;infisrv&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; 1&amp;nbsp;&amp;nbsp; SH&amp;nbsp; &amp;nbsp; HPUX&amp;nbsp;&amp;nbsp; &amp;nbsp;&amp;nbsp; On (OS)&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; 6&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; 2&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; 1&amp;nbsp;&amp;nbsp; 48 GB&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;sd16dom2_npar2# ioscan -fnC disk | grep HITACHI&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;disk&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; 17&amp;nbsp; 45/0/2/0/0/0/0/5/0/0/0.1.73.0.0.0.0&amp;nbsp;&amp;nbsp; sdisk&amp;nbsp;&amp;nbsp; CLAIMED&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; DEVICE&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; HITACHI OPEN-V&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; /dev/dsk/c10t0d0&amp;nbsp;&amp;nbsp; /dev/rdsk/c10t0d0&lt;BR /&gt;disk&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; 18&amp;nbsp; 45/0/2/0/0/0/0/5/0/0/0.1.73.0.0.0.1&amp;nbsp;&amp;nbsp; sdisk&amp;nbsp;&amp;nbsp; CLAIMED&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; DEVICE&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; HITACHI OPEN-V&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; /dev/dsk/c10t0d1&amp;nbsp;&amp;nbsp; /dev/rdsk/c10t0d1&lt;BR /&gt;disk&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; 19&amp;nbsp; 45/0/2/0/0/0/0/5/0/0/0.1.73.0.0.0.2&amp;nbsp;&amp;nbsp; sdisk&amp;nbsp;&amp;nbsp; CLAIMED&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; DEVICE&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; HITACHI OPEN-V&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; /dev/dsk/c10t0d2&amp;nbsp;&amp;nbsp; /dev/rdsk/c10t0d2&lt;BR /&gt;disk&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; 20&amp;nbsp; 45/0/2/0/0/0/0/5/0/0/0.1.73.0.0.0.3&amp;nbsp;&amp;nbsp; sdisk&amp;nbsp;&amp;nbsp; CLAIMED&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; DEVICE&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; HITACHI OPEN-V&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; /dev/dsk/c10t0d3&amp;nbsp;&amp;nbsp; /dev/rdsk/c10t0d3&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;sd16dom2_npar2# ioscan -m dsf&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;/dev/rdisk/disk21&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; /dev/rdsk/c10t0d1&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; /dev/rdsk/c12t0d1&lt;BR /&gt;/dev/rdisk/disk22&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; /dev/rdsk/c10t0d3&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; /dev/rdsk/c12t0d3&lt;BR /&gt;/dev/rdisk/disk23&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; /dev/rdsk/c10t0d0&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; /dev/rdsk/c12t0d0&lt;BR /&gt;/dev/rdisk/disk24&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; /dev/rdsk/c10t0d2&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; /dev/rdsk/c12t0d2&lt;BR /&gt;&lt;BR /&gt;&lt;/P&gt;&lt;P&gt;&lt;FONT color="#3366FF"&gt;What is the recommended procedure for assign these disks to the vm 1 ??. I was reading the Integrity VM V 6.2 Administration Guide, but i have some dudes about the storage assigment to the vm's. I'm interesting in use the attached i/O method because i don't want to share these disks to others vm's on the npar2. In fact, i was thinking if is convenient to assign the 2 fc hba's hardware paths to the vm 1 and then discover directly these 4 disks since the vm 1 os ??. it's possible or is not necessary ??.&lt;/FONT&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Thank's in advance&lt;/P&gt;&lt;P&gt;Ivan&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Wed, 24 Jul 2013 19:34:12 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/how-to-attaching-disks-to-a-integrity-vm/m-p/6146369#M521702</guid>
      <dc:creator>iazuarah</dc:creator>
      <dc:date>2013-07-24T19:34:12Z</dc:date>
    </item>
    <item>
      <title>Re: How to attaching disks to a integrity vm</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/how-to-attaching-disks-to-a-integrity-vm/m-p/6146387#M521703</link>
      <description>&lt;P&gt;There are tradeoffs as documented in the VM User Guide as to which "backing" method you choose to use.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;For instace file backing although highly portable is not a good choice for high I/O devices.&amp;nbsp; More suitable for DVD etc.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Then you have LVM backed storage.&amp;nbsp; Where basically you create a volume group and logical volume and assign to a VM.&amp;nbsp; these are better in performance than file backed, yet offer some versatility - like naming conventions.&amp;nbsp; This makes each LV easy to identify as belonging to a VM.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Then there is disk backed storeage.&amp;nbsp; Disk backed storage is even higher in performance than both LV and file backed storage.&amp;nbsp; You basically assign the VM a "raw" disk device,which then shows up as a disk with IOSCAN from the VM guest.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;With all of the above you will need to use the AVIO_STOR device&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I believe 6.1 or 6.2&amp;nbsp;also introduced the NPIV feature allowing you to perform direct assignement of a SAN based volume to a VM guest.&amp;nbsp; This would in theory be the best performer of the group, however I do not have much experience with this method.&amp;nbsp; Most of my experiences are with the "raw" disk backed storage devices assigned to the VM guest.&amp;nbsp; This gives you some granularity of control, but also offers good performance.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Bottom line the higher you go up the I/O stack on the VM host, the more performance hit you take on the guest.&amp;nbsp; Which is why I would NOT recommend file backed storage for applications etc.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;As for the exact commands, there are many examples in the config guide, once you decide which method you would prefer.&lt;/P&gt;</description>
      <pubDate>Wed, 24 Jul 2013 19:49:20 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/how-to-attaching-disks-to-a-integrity-vm/m-p/6146387#M521703</guid>
      <dc:creator>Jason_L</dc:creator>
      <dc:date>2013-07-24T19:49:20Z</dc:date>
    </item>
    <item>
      <title>Re: How to attaching disks to a integrity vm</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/how-to-attaching-disks-to-a-integrity-vm/m-p/6146391#M521704</link>
      <description>&lt;P&gt;A&amp;nbsp;pretty good read on the NPIV.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;A target="_blank" href="http://h20195.www2.hp.com/V2/GetPDF.aspx%2F4AA3-9894ENW.pdf"&gt;http://h20195.www2.hp.com/V2/GetPDF.aspx%2F4AA3-9894ENW.pdf&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Link is for 6.1 version, I am looking for the 6.2 version as well.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;FONT color="#3366ff"&gt;"What is the recommended procedure for assign these disks to the vm 1 ??. I was reading the Integrity VM V 6.2 Administration Guide, but i have some dudes about the storage assigment to the vm's. I'm interesting in use the attached i/O method because i don't want to share these disks to others vm's on the npar2. In fact, i was thinking if is convenient to assign the 2 fc hba's hardware paths to the vm 1 and then discover directly these 4 disks since the vm 1 os ??. it's possible or is not necessary ??."&lt;/FONT&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;FONT color="#000000"&gt;With the legacy AVIO you had to present ALL of the storage to the VM host, then either use file, LV or RAW backed storage and assign to the VM guest.&amp;nbsp; With NPIV, you create a virtual HBA and you assign the HBA to the VM guest.&amp;nbsp; This will provide the guest with a unigue WWN which you can then zone and provision SAN based volumes.&lt;/FONT&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;FONT color="#000000"&gt;So yes, if you choose this mentod, you will be able to discover the volumes directly on the guest and there is no need to present the volumes to the host. Be aware though to read through the caveats in the NPIV document.&lt;/FONT&gt;&lt;/P&gt;</description>
      <pubDate>Wed, 24 Jul 2013 20:11:59 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/how-to-attaching-disks-to-a-integrity-vm/m-p/6146391#M521704</guid>
      <dc:creator>Jason_L</dc:creator>
      <dc:date>2013-07-24T20:11:59Z</dc:date>
    </item>
    <item>
      <title>Re: How to attaching disks to a integrity vm</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/how-to-attaching-disks-to-a-integrity-vm/m-p/6146485#M521705</link>
      <description>&lt;P&gt;Thank's Jason, your information is very interesting and the NPIV is the best solution for me, but need to cover many prerequisites in hardware an software. By the way, is posible to have a mix environment , using NPIV for some virtual machines and the avio_stor for others ??.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Best Regards&lt;/P&gt;</description>
      <pubDate>Wed, 24 Jul 2013 22:08:32 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/how-to-attaching-disks-to-a-integrity-vm/m-p/6146485#M521705</guid>
      <dc:creator>iazuarah</dc:creator>
      <dc:date>2013-07-24T22:08:32Z</dc:date>
    </item>
    <item>
      <title>Re: How to attaching disks to a integrity vm</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/how-to-attaching-disks-to-a-integrity-vm/m-p/6146499#M521706</link>
      <description>&lt;P&gt;Yes it is possible to mix and match VM storage on VM guests - even on the same VM guest. You can configure an NPIV-based LUN as a boot disk, use AVIO LUNs as data disks, use LVM logical volumes, file-based backing stores, NFS-based backing stores, etc. &amp;nbsp;There is no requirement to use only one storage type.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I prefer to use NPIV whole LUNs or AVIO whole LUNs as they perform better than LVM, file, NFS-based backing stores.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Dave&lt;/P&gt;</description>
      <pubDate>Wed, 24 Jul 2013 22:26:10 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/how-to-attaching-disks-to-a-integrity-vm/m-p/6146499#M521706</guid>
      <dc:creator>Dave Olker</dc:creator>
      <dc:date>2013-07-24T22:26:10Z</dc:date>
    </item>
    <item>
      <title>Re: How to attaching disks to a integrity vm</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/how-to-attaching-disks-to-a-integrity-vm/m-p/6146519#M521707</link>
      <description>ok, perfect.&lt;BR /&gt;&lt;BR /&gt;By the way, i'm triying to attach a disk using the avio procedure:&lt;BR /&gt;&lt;BR /&gt;# hpvmmodify -p 1 -a disk:avio_stor::disk:/dev/rdisk/disk21&lt;BR /&gt;&lt;BR /&gt;that's correct ??.&lt;BR /&gt;&lt;BR /&gt;Ivan</description>
      <pubDate>Wed, 24 Jul 2013 22:48:14 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/how-to-attaching-disks-to-a-integrity-vm/m-p/6146519#M521707</guid>
      <dc:creator>iazuarah</dc:creator>
      <dc:date>2013-07-24T22:48:14Z</dc:date>
    </item>
    <item>
      <title>Re: How to attaching disks to a integrity vm</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/how-to-attaching-disks-to-a-integrity-vm/m-p/6146533#M521708</link>
      <description>&lt;P&gt;Assuming you want to add the whole disk /dev/rdisk/disk21 to guest #1 via AVIO, yes that syntax looks correct.&lt;/P&gt;</description>
      <pubDate>Wed, 24 Jul 2013 23:01:38 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/how-to-attaching-disks-to-a-integrity-vm/m-p/6146533#M521708</guid>
      <dc:creator>Dave Olker</dc:creator>
      <dc:date>2013-07-24T23:01:38Z</dc:date>
    </item>
    <item>
      <title>Re: How to attaching disks to a integrity vm</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/how-to-attaching-disks-to-a-integrity-vm/m-p/6146535#M521709</link>
      <description>Thanks in advance !!</description>
      <pubDate>Wed, 24 Jul 2013 23:04:00 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/how-to-attaching-disks-to-a-integrity-vm/m-p/6146535#M521709</guid>
      <dc:creator>iazuarah</dc:creator>
      <dc:date>2013-07-24T23:04:00Z</dc:date>
    </item>
    <item>
      <title>Re: How to attaching disks to a integrity vm</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/how-to-attaching-disks-to-a-integrity-vm/m-p/6149185#M521710</link>
      <description>&lt;P&gt;Hi, i'm starting to install the NPIV on my npar and vm. But i'm having a connection problem between the server and client. This is the message:&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;# /opt/guid/bin/guid_client_prepare -a&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;NOTE:&lt;BR /&gt;&amp;nbsp;We found Host is configured in /opt/guid/etc/guid.conf. This&lt;BR /&gt;may because current machine has been once installed and&lt;BR /&gt;configured as a GUID client.&amp;nbsp; Or user has defined hostname in&lt;BR /&gt;guid.conf by CLI tool "guidconfig -h".&lt;BR /&gt;&amp;nbsp;In this case, we only try setting up authentications between&lt;BR /&gt;current client and remote GUID servers, which are configured&lt;BR /&gt;in HOST.&lt;BR /&gt;&lt;BR /&gt;Install pubkey on GUID server(sd16dom2) succeeded.&lt;BR /&gt;&lt;BR /&gt;Connect to host sd16dom2 failed. ---&amp;gt; NOTE: BOTH SERVERS ARE IN THE SAME SUBNET&lt;BR /&gt;&lt;BR /&gt;ListRange of wwn from GUID server(sd16dom2) failed.&lt;BR /&gt;&lt;BR /&gt;GUIDMGR client preparation accomplished.&lt;BR /&gt;&lt;BR /&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Some suggestion ??.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Regards&lt;/P&gt;</description>
      <pubDate>Fri, 26 Jul 2013 16:51:33 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/how-to-attaching-disks-to-a-integrity-vm/m-p/6149185#M521710</guid>
      <dc:creator>iazuarah</dc:creator>
      <dc:date>2013-07-26T16:51:33Z</dc:date>
    </item>
    <item>
      <title>Re: How to attaching disks to a integrity vm</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/how-to-attaching-disks-to-a-integrity-vm/m-p/6149479#M521711</link>
      <description>&lt;P&gt;I assume you have a GUID manager configured at this point and have created a range of WWN values. &amp;nbsp;You can try manually setting the hostname of the GUID manager using "guidconfig -h" and then see if you can query the GUID manager to display the list of managed WWN ranges:&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;# /opt/guid/bin/guidconfig -h &amp;lt;hostname of GUID manager&amp;gt;&lt;/P&gt;&lt;P&gt;# /opt/guid/bin/guidmgmt -L wwn&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Dave&lt;/P&gt;</description>
      <pubDate>Sat, 27 Jul 2013 00:53:24 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/how-to-attaching-disks-to-a-integrity-vm/m-p/6149479#M521711</guid>
      <dc:creator>Dave Olker</dc:creator>
      <dc:date>2013-07-27T00:53:24Z</dc:date>
    </item>
    <item>
      <title>Re: How to attaching disks to a integrity vm</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/how-to-attaching-disks-to-a-integrity-vm/m-p/6152439#M521712</link>
      <description>&lt;P&gt;Bonjour,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Not sure that everybody will agree with that : you can also manage manually NPIV WWN.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Extract from &lt;A target="_blank" href="http://bizsupport2.austin.hp.com/bc/docs/support/SupportManual/c03199402/c03199402.pdf"&gt;HP-UX vPars 6.0 N-Port ID Virtualization (NPIV)&lt;/A&gt;, bottom of page 9 :&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;FONT color="#0000ff"&gt;Allocating IDs manually or with third-party products&lt;/FONT&gt;&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;&lt;FONT color="#0000ff"&gt;When manually configuring vHBAs, &lt;STRONG&gt;&lt;U&gt;vWWNs may safely be picked from the range 0x100000110a0300 - 0x100000110a030fff&lt;/U&gt;&lt;/STRONG&gt;. This is a total of 4096 WWN which are not in the range that is handled automatically by GUIDMgr (see above). A user may use GUIDMgr for some NPIV HBAs and still manually select from the above range for other vHBAs. If this is being done, please note that you can save your manual settings in the GUIDMgr for tracking purposes, but the GUIDMgr never assigns a WWN outside of the range that HP has reserved.&lt;/FONT&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Note there is a typo : range should begin @ 0x100000110a0300&lt;FONT color="#ff0000"&gt;00&lt;FONT color="#000000"&gt;.&lt;/FONT&gt; &lt;FONT color="#000000"&gt;Two&lt;/FONT&gt; &lt;FONT color="#000000"&gt;zeroes&lt;/FONT&gt; &lt;FONT color="#000000"&gt;are&lt;/FONT&gt; &lt;FONT color="#000000"&gt;missing.&lt;/FONT&gt;&lt;/FONT&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Don't know how many virtual HBA you will have to manage, but it could be easier to maintain an Excel spreadsheet. That's what I do : I don't want to have to maintain an additional software layer if I can avoid it.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;HTH&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Eric&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Tue, 30 Jul 2013 08:38:30 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/how-to-attaching-disks-to-a-integrity-vm/m-p/6152439#M521712</guid>
      <dc:creator>Eric SAUBIGNAC</dc:creator>
      <dc:date>2013-07-30T08:38:30Z</dc:date>
    </item>
    <item>
      <title>Re: How to attaching disks to a integrity vm</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/how-to-attaching-disks-to-a-integrity-vm/m-p/6153159#M521713</link>
      <description>&lt;P&gt;Opps, sorry by the delay. In fact i',m triying to install my NPIV scenario by first time. Here we go:&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;a) In the NPAR and VM&amp;nbsp;servers i'm&amp;nbsp;following the next procedure from the manual:&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P align="left"&gt;2.2.1 Installing on the server&lt;/P&gt;&lt;P align="left"&gt;To install the HP-UX GUID Manager software on the database server, enter the following command&lt;/P&gt;&lt;P align="left"&gt;on the server:&lt;/P&gt;&lt;P align="left"&gt;#&lt;/P&gt;&lt;P align="left"&gt;&lt;STRONG&gt;&lt;FONT face="Courier-Bold" size="1"&gt;&lt;FONT face="Courier-Bold" size="1"&gt;swinstall -s ${DEPOT_PATH}/GUIDMGR_A.01.00.603_HP-UX_B.11.31_IA.depot GUIDMGR&lt;/FONT&gt;&lt;/FONT&gt;&lt;/STRONG&gt;&lt;/P&gt;&lt;P align="left"&gt;#&lt;/P&gt;&lt;P align="left"&gt;&lt;STRONG&gt;&lt;FONT face="Courier-Bold" size="1"&gt;&lt;FONT face="Courier-Bold" size="1"&gt;swlist GUIDMGR&lt;/FONT&gt;&lt;/FONT&gt;&lt;/STRONG&gt;&lt;/P&gt;&lt;P align="left"&gt;GUIDMGR A.01.00.603 HP-UX GUID Manager&lt;/P&gt;&lt;P align="left"&gt;This command initializes the GUIDMgr server-side environment, including creating a GUID private&lt;/P&gt;&lt;P align="left"&gt;user account, initializing the database, and starting the database service. If no error occurs during&lt;/P&gt;&lt;P align="left"&gt;initialization, GUIDMgr related daemons are started. If any error occurs, you must fix the error&lt;/P&gt;&lt;P align="left"&gt;before performing the next step or distributing current host name to any GUIDMgr client.&lt;/P&gt;&lt;P align="left"&gt;To initialize the server, enter the following command:&lt;/P&gt;&lt;P align="left"&gt;#&lt;/P&gt;&lt;P align="left"&gt;&lt;STRONG&gt;&lt;FONT face="Courier-Bold" size="2"&gt;&lt;FONT face="Courier-Bold" size="2"&gt;/opt/guid/utils/guid_server_prepare.sh&lt;/FONT&gt;&lt;/FONT&gt;&lt;/STRONG&gt;&lt;/P&gt;&lt;P align="left"&gt;This command configures the GUIDMgr on the target system. After the GUID Manager is configured&lt;/P&gt;&lt;P align="left"&gt;on the server, the database is empty. The&lt;/P&gt;&lt;P align="left"&gt;&lt;FONT face="Courier" size="3"&gt;&lt;FONT face="Courier" size="3"&gt;guid_server_prepare &lt;/FONT&gt;&lt;/FONT&gt;&lt;FONT face="FuturaBk" size="3"&gt;&lt;FONT face="FuturaBk" size="3"&gt;command creates some guid&lt;/FONT&gt;&lt;/FONT&gt;&lt;/P&gt;&lt;P align="left"&gt;tables without any guid data. The guid_server_prepare.sh script executes the following commands&lt;/P&gt;&lt;P align="left"&gt;automatically:&lt;/P&gt;&lt;P align="left"&gt;2.1 Installation requirements 9&lt;/P&gt;&lt;P align="left"&gt;•&lt;/P&gt;&lt;P align="left"&gt;&lt;FONT face="Courier" size="3"&gt;&lt;FONT face="Courier" size="3"&gt;/opt/guid/bin/guidconfig &lt;/FONT&gt;&lt;/FONT&gt;&lt;FONT face="Courier" size="3"&gt;&lt;FONT face="Courier" size="3"&gt;–&lt;/FONT&gt;&lt;/FONT&gt;&lt;FONT face="Courier" size="3"&gt;&lt;FONT face="Courier" size="3"&gt;b wwn &lt;/FONT&gt;&lt;/FONT&gt;&lt;FONT face="FuturaBk" size="3"&gt;&lt;FONT face="FuturaBk" size="3"&gt;is executed to set up the library linkage for the&lt;/FONT&gt;&lt;/FONT&gt;&lt;/P&gt;&lt;P align="left"&gt;commands.&lt;/P&gt;&lt;P align="left"&gt;•&lt;/P&gt;&lt;P align="left"&gt;&lt;FONT face="Courier" size="3"&gt;&lt;FONT face="Courier" size="3"&gt;/opt/guid/sbin/guidd &lt;/FONT&gt;&lt;/FONT&gt;&lt;FONT face="FuturaBk" size="3"&gt;&lt;FONT face="FuturaBk" size="3"&gt;is started as the main daemon for a GUID server.&lt;/FONT&gt;&lt;/FONT&gt;&lt;/P&gt;&lt;P align="left"&gt;•&lt;/P&gt;&lt;P align="left"&gt;&lt;FONT face="Courier" size="3"&gt;&lt;FONT face="Courier" size="3"&gt;/opt/guid/sbin/guidkeyd &lt;/FONT&gt;&lt;/FONT&gt;&lt;FONT face="FuturaBk" size="3"&gt;&lt;FONT face="FuturaBk" size="3"&gt;is started, so you can SSH tunnel to GUID server from GUID&lt;/FONT&gt;&lt;/FONT&gt;&lt;/P&gt;&lt;P align="left"&gt;client.&lt;/P&gt;&lt;P align="left"&gt;•&lt;/P&gt;&lt;P align="left"&gt;&lt;FONT face="Courier" size="3"&gt;&lt;FONT face="Courier" size="3"&gt;/opt/guid/sbin/guiddbutil &lt;/FONT&gt;&lt;/FONT&gt;&lt;FONT face="Courier" size="3"&gt;&lt;FONT face="Courier" size="3"&gt;–&lt;/FONT&gt;&lt;/FONT&gt;&lt;FONT face="Courier" size="3"&gt;&lt;FONT face="Courier" size="3"&gt;c wwn &lt;/FONT&gt;&lt;/FONT&gt;&lt;FONT face="FuturaBk" size="3"&gt;&lt;FONT face="FuturaBk" size="3"&gt;is used to create the initial database, if not&lt;/FONT&gt;&lt;/FONT&gt;&lt;/P&gt;&lt;P align="left"&gt;already created.&lt;/P&gt;&lt;P align="left"&gt;The&lt;/P&gt;&lt;P align="left"&gt;&lt;FONT face="Courier" size="3"&gt;&lt;FONT face="Courier" size="3"&gt;/opt/guid/tools/postgresql &lt;/FONT&gt;&lt;/FONT&gt;&lt;FONT face="FuturaBk" size="3"&gt;&lt;FONT face="FuturaBk" size="3"&gt;directory contains binaries to set up the a &lt;/FONT&gt;&lt;/FONT&gt;&lt;FONT face="Courier" size="3"&gt;&lt;FONT face="Courier" size="3"&gt;postgresql&lt;/FONT&gt;&lt;/FONT&gt;&lt;/P&gt;&lt;P align="left"&gt;database for private use by a GUID server. Various PostgreSQL commands are executed to set up&lt;/P&gt;&lt;P align="left"&gt;the database for the first time, if not already created, and start the&lt;/P&gt;&lt;P align="left"&gt;&lt;FONT face="Courier" size="3"&gt;&lt;FONT face="Courier" size="3"&gt;postgresql &lt;/FONT&gt;&lt;/FONT&gt;&lt;FONT face="FuturaBk" size="3"&gt;&lt;FONT face="FuturaBk" size="3"&gt;daemons needed&lt;/FONT&gt;&lt;/FONT&gt;&lt;/P&gt;&lt;P align="left"&gt;to access the database.&lt;/P&gt;&lt;P align="left"&gt;2.2.2 Installing on the client&lt;/P&gt;&lt;P align="left"&gt;To install the GUID client, enter the following command on all the VSP hosts:&lt;/P&gt;&lt;P align="left"&gt;#&lt;/P&gt;&lt;P align="left"&gt;&lt;STRONG&gt;&lt;FONT face="Courier-Bold" size="1"&gt;&lt;FONT face="Courier-Bold" size="1"&gt;swinstall -s ${DEPOT_PATH}/GUIDMGR_A.01.00.603_HP-UX_B.11.31_IA.depot GUIDMGR&lt;/FONT&gt;&lt;/FONT&gt;&lt;/STRONG&gt;&lt;/P&gt;&lt;P align="left"&gt;NOTE:&lt;/P&gt;&lt;P align="left"&gt;&lt;FONT face="FuturaBk" size="3"&gt;&lt;FONT face="FuturaBk" size="3"&gt;After installing and verifying the client installation, you must set up authentication on&lt;/FONT&gt;&lt;/FONT&gt;&lt;/P&gt;&lt;P align="left"&gt;GUID client. Otherwise, any GUID request to remote server will fail. See&lt;/P&gt;&lt;P align="left"&gt;&lt;FONT color="#005391" size="3" face="FuturaBk"&gt;&lt;FONT color="#005391" size="3" face="FuturaBk"&gt;&lt;FONT color="#005391" size="3" face="FuturaBk"&gt;“Verifying the installation&lt;/FONT&gt;&lt;/FONT&gt;&lt;/FONT&gt;&lt;/P&gt;&lt;P&gt;of GUIDMgr” (page 10) &lt;FONT size="3" face="FuturaBk"&gt;&lt;FONT size="3" face="FuturaBk"&gt;for information about setting up authentication.&lt;/FONT&gt;&lt;/FONT&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P align="left"&gt;3.1 Setting up the server and the client&lt;/P&gt;&lt;P align="left"&gt;This section provides the steps for setting up the server and the client. After installing, initializing,&lt;/P&gt;&lt;P align="left"&gt;and configuring the GUID manager on the server (see &lt;FONT color="#005391" size="3" face="FuturaBk"&gt;&lt;FONT color="#005391" size="3" face="FuturaBk"&gt;&lt;FONT color="#005391" size="3" face="FuturaBk"&gt;“Installing on the server” (page 9)&lt;/FONT&gt;&lt;/FONT&gt;&lt;/FONT&gt;&lt;FONT size="3" face="FuturaBk"&gt;&lt;FONT size="3" face="FuturaBk"&gt;), follow&lt;/FONT&gt;&lt;/FONT&gt;&lt;/P&gt;&lt;P align="left"&gt;these steps to set up the server:&lt;/P&gt;&lt;P align="left"&gt;1.&lt;/P&gt;&lt;P align="left"&gt;&lt;FONT size="3" face="FuturaBk"&gt;&lt;FONT size="3" face="FuturaBk"&gt;Set the GUIDMgr server &lt;/FONT&gt;&lt;/FONT&gt;&lt;EM&gt;&lt;FONT size="3" face="Courier-Oblique"&gt;&lt;FONT size="3" face="Courier-Oblique"&gt;hostname&lt;/FONT&gt;&lt;/FONT&gt;&lt;/EM&gt;&lt;FONT size="3" face="FuturaBk"&gt;&lt;FONT size="3" face="FuturaBk"&gt;:&lt;/FONT&gt;&lt;/FONT&gt;&lt;/P&gt;&lt;P align="left"&gt;#&lt;/P&gt;&lt;P align="left"&gt;&lt;STRONG&gt;&lt;FONT size="2" face="Courier-Bold"&gt;&lt;FONT size="2" face="Courier-Bold"&gt;/opt/guid/bin/guidconfig -h &lt;/FONT&gt;&lt;/FONT&gt;&lt;EM&gt;&lt;FONT size="2" face="Courier-BoldOblique"&gt;&lt;FONT size="2" face="Courier-BoldOblique"&gt;guid_server_hostname&lt;/FONT&gt;&lt;/FONT&gt;&lt;/EM&gt;&lt;/STRONG&gt;&lt;/P&gt;&lt;P align="left"&gt;&amp;nbsp;&lt;/P&gt;&lt;P align="left"&gt;After installing GUID Manager on the client &lt;FONT color="#005391" size="3" face="FuturaBk"&gt;&lt;FONT color="#005391" size="3" face="FuturaBk"&gt;&lt;FONT color="#005391" size="3" face="FuturaBk"&gt;“Installing on the client” (page 10)&lt;/FONT&gt;&lt;/FONT&gt;&lt;/FONT&gt;&lt;FONT size="3" face="FuturaBk"&gt;&lt;FONT size="3" face="FuturaBk"&gt;, perform the&lt;/FONT&gt;&lt;/FONT&gt;&lt;/P&gt;&lt;P align="left"&gt;following steps to set up the client:&lt;/P&gt;&lt;P align="left"&gt;1.&lt;/P&gt;&lt;P align="left"&gt;&lt;FONT size="3" face="FuturaBk"&gt;&lt;FONT size="3" face="FuturaBk"&gt;Configure client access to the database:&lt;/FONT&gt;&lt;/FONT&gt;&lt;/P&gt;&lt;P align="left"&gt;#&lt;/P&gt;&lt;P align="left"&gt;&lt;STRONG&gt;&lt;FONT size="2" face="Courier-Bold"&gt;&lt;FONT size="2" face="Courier-Bold"&gt;/opt/guid/bin/guid_client_prepare -a&lt;/FONT&gt;&lt;/FONT&gt;&lt;/STRONG&gt;&lt;/P&gt;&lt;P align="left"&gt;2.&lt;/P&gt;&lt;P align="left"&gt;&lt;FONT size="3" face="FuturaBk"&gt;&lt;FONT size="3" face="FuturaBk"&gt;Set the GUIDMgr server &lt;/FONT&gt;&lt;/FONT&gt;&lt;EM&gt;&lt;FONT size="3" face="Courier-Oblique"&gt;&lt;FONT size="3" face="Courier-Oblique"&gt;hostname&lt;/FONT&gt;&lt;/FONT&gt;&lt;/EM&gt;&lt;FONT size="3" face="FuturaBk"&gt;&lt;FONT size="3" face="FuturaBk"&gt;:&lt;/FONT&gt;&lt;/FONT&gt;&lt;/P&gt;&lt;P align="left"&gt;#&lt;/P&gt;&lt;P align="left"&gt;&lt;STRONG&gt;&lt;FONT size="2" face="Courier-Bold"&gt;&lt;FONT size="2" face="Courier-Bold"&gt;/opt/guid/bin/guidconfig -h &lt;/FONT&gt;&lt;/FONT&gt;&lt;EM&gt;&lt;FONT size="2" face="Courier-BoldOblique"&gt;&lt;FONT size="2" face="Courier-BoldOblique"&gt;guid_server_hostname&lt;/FONT&gt;&lt;/FONT&gt;&lt;/EM&gt;&lt;/STRONG&gt;&lt;/P&gt;&lt;P align="left"&gt;3.&lt;/P&gt;&lt;P align="left"&gt;&lt;FONT size="3" face="FuturaBk"&gt;&lt;FONT size="3" face="FuturaBk"&gt;Create a range of WWNs to manage:&lt;/FONT&gt;&lt;/FONT&gt;&lt;/P&gt;&lt;P align="left"&gt;#&lt;/P&gt;&lt;P align="left"&gt;&lt;STRONG&gt;&lt;FONT size="2" face="Courier-Bold"&gt;&lt;FONT size="2" face="Courier-Bold"&gt;/opt/guid/bin/guidmgmt -S wwn 50014c2000000000 50014c2000007fff&lt;/FONT&gt;&lt;/FONT&gt;&lt;/STRONG&gt;&lt;/P&gt;&lt;P align="left"&gt;4.&lt;/P&gt;&lt;P align="left"&gt;&lt;FONT size="3" face="FuturaBk"&gt;&lt;FONT size="3" face="FuturaBk"&gt;Verify database access by querying the pools of WWNs:&lt;/FONT&gt;&lt;/FONT&gt;&lt;/P&gt;&lt;P align="left"&gt;#&lt;/P&gt;&lt;P align="left"&gt;&lt;STRONG&gt;&lt;FONT size="2" face="Courier-Bold"&gt;&lt;FONT size="2" face="Courier-Bold"&gt;/opt/guid/bin/guidmgmt -L wwn&lt;/FONT&gt;&lt;/FONT&gt;&lt;/STRONG&gt;&lt;/P&gt;&lt;P align="left"&gt;Range type Start(Hex) End(Hex) Size(dec)&lt;/P&gt;&lt;P align="left"&gt;=============== ================== ================== ==========&lt;/P&gt;&lt;P align="left"&gt;HP-DEFINED-PWWN 0x50014c2000000000 0x50014c2000007fff 32768&lt;/P&gt;&lt;P align="left"&gt;HP-DEFINED-NWWN 0x50014c2800000000 0x50014c2800007fff 32768&lt;/P&gt;&lt;P align="left"&gt;5.&lt;/P&gt;&lt;P align="left"&gt;&lt;FONT size="3" face="FuturaBk"&gt;&lt;FONT size="3" face="FuturaBk"&gt;Verify ranges with these commands:&lt;/FONT&gt;&lt;/FONT&gt;&lt;/P&gt;&lt;P align="left"&gt;#&lt;/P&gt;&lt;P align="left"&gt;&lt;STRONG&gt;&lt;FONT size="2" face="Courier-Bold"&gt;&lt;FONT size="2" face="Courier-Bold"&gt;/opt/guid/sbin/guiddbutil -s range_wwn wwn&lt;/FONT&gt;&lt;/FONT&gt;&lt;/STRONG&gt;&lt;/P&gt;&lt;P align="left"&gt;#&lt;/P&gt;&lt;P align="left"&gt;&lt;STRONG&gt;&lt;FONT size="2" face="Courier-Bold"&gt;&lt;FONT size="2" face="Courier-Bold"&gt;/opt/guid/sbin/guiddbutil -s addr_wwn wwn&lt;/FONT&gt;&lt;/FONT&gt;&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;3.2 Verify&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;But this procedure isn't working for me because i obtain the same result on the vm :&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;# /opt/guid/bin/guid_client_prepare -a&amp;nbsp;&amp;nbsp;&amp;nbsp;&lt;/P&gt;&lt;P&gt;　&lt;/P&gt;&lt;P&gt;NOTE:&lt;/P&gt;&lt;P&gt;We found Host is configured in /opt/guid/etc/guid.conf. This&lt;/P&gt;&lt;P&gt;may because current machine has been once installed and&lt;/P&gt;&lt;P&gt;configured as a GUID client.&amp;nbsp; Or user has defined hostname in&lt;/P&gt;&lt;P&gt;guid.conf by CLI tool "guidconfig -h".&lt;/P&gt;&lt;P&gt;In this case, we only try setting up authentications between&lt;/P&gt;&lt;P&gt;current client and remote GUID servers, which are configured&lt;/P&gt;&lt;P&gt;in HOST.&lt;/P&gt;&lt;P&gt;　&lt;/P&gt;&lt;P&gt;Install pubkey on GUID server(sd16dom2) succeeded.&lt;/P&gt;&lt;P&gt;Connect to host sd16dom2 failed.&lt;/P&gt;&lt;P&gt;ListRange of wwn from GUID server(sd16dom2) failed.&lt;/P&gt;&lt;P&gt;GUIDMGR client preparation accomplished.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Some idea ??&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Regards !!&lt;/P&gt;</description>
      <pubDate>Tue, 30 Jul 2013 18:58:33 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/how-to-attaching-disks-to-a-integrity-vm/m-p/6153159#M521713</guid>
      <dc:creator>iazuarah</dc:creator>
      <dc:date>2013-07-30T18:58:33Z</dc:date>
    </item>
    <item>
      <title>Re: How to attaching disks to a integrity vm</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/how-to-attaching-disks-to-a-integrity-vm/m-p/6153165#M521714</link>
      <description>&lt;P&gt;Sounds interesting, could you give me&amp;nbsp;an example using this alternate procedure&amp;nbsp;, please. I don't want to manage an additional software for this porpouse.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Regards&lt;/P&gt;</description>
      <pubDate>Tue, 30 Jul 2013 19:03:20 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/how-to-attaching-disks-to-a-integrity-vm/m-p/6153165#M521714</guid>
      <dc:creator>iazuarah</dc:creator>
      <dc:date>2013-07-30T19:03:20Z</dc:date>
    </item>
    <item>
      <title>Re: How to attaching disks to a integrity vm</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/how-to-attaching-disks-to-a-integrity-vm/m-p/6153973#M521715</link>
      <description>&lt;P&gt;Check the attached spreadsheet ... my own GUI ;-) Of course, I can't assume any bug. It's just a tool for myself I can share&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;BR /&gt;Just add the name of the vm guest you want to modify, the virtual bus where you want to connect the virtual hba, the physical hba on the host and you will find all the commands to modify the vm guest and to add the corresponding host in a 3Par storage.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;If you add the existing aliases of a storage in the san, you will get commands to create the corresponding zones in the fabrics&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Fabric number is optional. Just a way to color the commands for the fabrics.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;HTH&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Eric&lt;/P&gt;</description>
      <pubDate>Wed, 31 Jul 2013 11:13:20 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/how-to-attaching-disks-to-a-integrity-vm/m-p/6153973#M521715</guid>
      <dc:creator>Eric SAUBIGNAC</dc:creator>
      <dc:date>2013-07-31T11:13:20Z</dc:date>
    </item>
    <item>
      <title>Re: How to attaching disks to a integrity vm</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/how-to-attaching-disks-to-a-integrity-vm/m-p/6153991#M521717</link>
      <description>&lt;P&gt;Dont know what is happening : unable to attach the document :-((((&lt;/P&gt;</description>
      <pubDate>Wed, 31 Jul 2013 11:23:06 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/how-to-attaching-disks-to-a-integrity-vm/m-p/6153991#M521717</guid>
      <dc:creator>Eric SAUBIGNAC</dc:creator>
      <dc:date>2013-07-31T11:23:06Z</dc:date>
    </item>
    <item>
      <title>Re: How to attach disks to a integrity VM</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/how-to-attaching-disks-to-a-integrity-vm/m-p/6154033#M521718</link>
      <description>&lt;P&gt;&amp;gt;unable to attach the document&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Attachments have to have known suffixes like .txt, .pdf, .zip, etc.&lt;/P&gt;&lt;P&gt;You can edit your post by Post Options &amp;gt; Edit Reply&lt;/P&gt;</description>
      <pubDate>Tue, 26 Nov 2013 23:21:17 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/how-to-attaching-disks-to-a-integrity-vm/m-p/6154033#M521718</guid>
      <dc:creator>Dennis Handly</dc:creator>
      <dc:date>2013-11-26T23:21:17Z</dc:date>
    </item>
    <item>
      <title>Re: How to attaching disks to a integrity VM</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/how-to-attaching-disks-to-a-integrity-vm/m-p/6154133#M521719</link>
      <description>&lt;P&gt;Many thanks Dennis. I am going to do some tests&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;.../...&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;a little bit later&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;It doesn't work :-( Tried with a true .txt file, a true .pdf, a zip archive ...&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;IMG title="Capture.PNG" align="center" border="0" alt="Capture.PNG" src="https://community.hpe.com/t5/image/serverpage/image-id/26385i36C7A1EA02551702/image-size/original?v=mpbl-1&amp;amp;px=-1" /&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;After browsing the file, I have tried do click immediatly on the "Post" button. I have also tried to click on the "Add Attachment" button before. No way&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Wed, 31 Jul 2013 13:00:58 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/how-to-attaching-disks-to-a-integrity-vm/m-p/6154133#M521719</guid>
      <dc:creator>Eric SAUBIGNAC</dc:creator>
      <dc:date>2013-07-31T13:00:58Z</dc:date>
    </item>
    <item>
      <title>Re: How to attach disks to a integrity VM</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/how-to-attaching-disks-to-a-integrity-vm/m-p/6154159#M521721</link>
      <description>&lt;P&gt;&amp;gt;It doesn't work&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;What browser are you using?&amp;nbsp; Works fine with firefox 22.0.&lt;/P&gt;&lt;P&gt;No problems with IE10 and Windows 8.&lt;/P&gt;</description>
      <pubDate>Tue, 26 Nov 2013 23:20:18 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/how-to-attaching-disks-to-a-integrity-vm/m-p/6154159#M521721</guid>
      <dc:creator>Dennis Handly</dc:creator>
      <dc:date>2013-11-26T23:20:18Z</dc:date>
    </item>
    <item>
      <title>Re: How to attaching disks to a integrity VM</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/how-to-attaching-disks-to-a-integrity-vm/m-p/6154171#M521723</link>
      <description>&lt;P&gt;IE 9, 32 bits, from a Windows 7 64 bits OS&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Same thing with IE 64 bits&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I will try a reboot&lt;/P&gt;</description>
      <pubDate>Wed, 31 Jul 2013 13:07:29 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/how-to-attaching-disks-to-a-integrity-vm/m-p/6154171#M521723</guid>
      <dc:creator>Eric SAUBIGNAC</dc:creator>
      <dc:date>2013-07-31T13:07:29Z</dc:date>
    </item>
    <item>
      <title>Re: How to attaching disks to a integrity VM</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/how-to-attaching-disks-to-a-integrity-vm/m-p/6154187#M521724</link>
      <description>&lt;P&gt;Reboot done. And it doesn't work anymore ...&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Updated Java. All caches emptied. Still not working&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Can you tell me what URL do you see on buttons "Remove" and "Add Attachment". I see the same URL on both buttons :&amp;nbsp;&amp;nbsp;http:// h30499.www3.hp.com/t5/forums/editpage/board-id/itrc-855/message-id/5810/is-draft/false#&amp;nbsp; ????&lt;/P&gt;</description>
      <pubDate>Wed, 31 Jul 2013 13:37:23 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/how-to-attaching-disks-to-a-integrity-vm/m-p/6154187#M521724</guid>
      <dc:creator>Eric SAUBIGNAC</dc:creator>
      <dc:date>2013-07-31T13:37:23Z</dc:date>
    </item>
  </channel>
</rss>

