How to attaching disks to a integrity vm

[Jason_L]

GUID Manager is integrated with HP Integrity VM V4.3 (January 2012 patch release), HP-UX
Virtual Partitions V6.0 (vPars V6.0), and vPars and Integrity VM V6.1 or later.
NPIV allows you to create multiple virtual fiber channel ports (VFCs) over one physical port (PFC)
on a host. Each of these virtual ports should be created with a unique World Wide Node name
(WWN) and World Wide Port name (pWWN).

http://h20566.www2.hp.com/portal/site/hpsc/template.BINARYPORTLET/public/kb/docDisplay/resource.process/?spf_p.tpst=kbDocDisplay_ws_BI&spf_p.rid_kbDocDisplay=docDisplayResURL&javax.portlet.begCacheTok=com.vignette.cachetoken&spf_p.rst_kbDocDisplay=wsrp-resourceState%3DdocId%253Demr_na-c03686172-2%257CdocLocale%253Den_US&javax.portlet.endCacheTok=com.vignette.cachetoken

IMPORTANT: HP recommends using the HP-UX GUID Manager to allocate and maintain WWNs

and vWWNs. For more information about HP-UX GUID Manager, see the HP-UX GUID Manager
Administrator Guide available on the HP website at http://www.hp.com/go/hpux-hpvm-docs.

Also for reference:

The range that HP has reserved for NPIV is 0x50014c2000000000 to 0x50014c27ffffffff for Port WWNs and
0x50014c2800000000 to 0x50014c2fffffffff for Node WWNs. For more information about installing, configuring and using GUIDMgr, please see the HP-UX GUID Manager Administrator Guide and the GUIDMgr man pages: 

Allocating IDs manually or with third-party products
When manually configuring vHBAs, vWWNs may safely be picked from the range 0x100000110a0300 -
0x100000110a030fff. 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.

So maybe GUID MGR has to be running even to assign the WWN manually? You mentioned GUID services are not running. Try starting them and running the command again?

Hope this helps.

[Eric SAUBIGNAC]

Bonsoir,

For your first post, the syntaxe looks fine.

For the second one, really don't know. May be HPVM is aware of the GUID ? Have you configured something to locate the GUID ?

[iazuarah]

ok, the problem with the guidmgr was resolved. Now, my problem is that the vm doesn't recognize the luns attached to this vhba. In the Npar the luns appears correctly.

VM

---

siiautdb_vm# ioscan -H 0/2/0/0
H/W Path  Class             Description
=======================================
0/2/0/0             ext_bus HPVM NPIV Stor Adapter
siiautdb_vm# ioscan -H 0/3/0/0
H/W Path  Class             Description
=======================================
0/3/0/0             ext_bus HPVM NPIV Stor Adapter

NPAR

------

disk    185  42/0/0/2/0/0/0/5/0/0/1.1.201.0.0.0.0  sdisk   CLAIMED      DEVICE       HITACHI OPEN-V
                         /dev/dsk/c38t0d0   /dev/rdsk/c38t0d0
disk    186  42/0/0/2/0/0/0/5/0/0/1.1.201.0.0.0.1  sdisk   CLAIMED       DEVICE      HITACHI OPEN-V
                         /dev/dsk/c38t0d1   /dev/rdsk/c38t0d1
disk    187  42/0/0/2/0/0/0/5/0/0/1.1.201.0.0.0.2  sdisk   CLAIMED       DEVICE      HITACHI OPEN-V
                         /dev/dsk/c38t0d2   /dev/rdsk/c38t0d2
disk    188  42/0/0/2/0/0/0/5/0/0/1.1.201.0.0.0.3  sdisk   CLAIMED       DEVICE       HITACHI OPEN-V
                         /dev/dsk/c38t0d3   /dev/rdsk/c38t0d3
disk    189  42/0/0/2/0/0/0/5/0/0/1.1.201.0.0.0.4  sdisk   CLAIMED       DEVICE       HITACHI OPEN-V
                         /dev/dsk/c38t0d4   /dev/rdsk/c38t0d4
disk    190  42/0/0/2/0/0/0/5/0/0/1.1.201.0.0.0.5  sdisk   CLAIMED       DEVICE       HITACHI OPEN-V
                         /dev/dsk/c38t0d5   /dev/rdsk/c38t0d5
disk    191  42/0/0/2/0/0/0/5/0/0/1.1.201.0.0.0.6  sdisk   CLAIMED       DEVICE       HITACHI OPEN-V
                         /dev/dsk/c38t0d6   /dev/rdsk/c38t0d6
disk    192  42/0/0/2/0/0/0/5/0/0/1.1.201.0.0.0.7  sdisk   CLAIMED       DEVICE       HITACHI OPEN-V
                         /dev/dsk/c38t0d7   /dev/rdsk/c38t0d7

-----------------------------------------------------------------------------------------------------------------

disk    201  45/0/2/0/0/0/0/5/0/0/1.1.73.0.0.0.0   sdisk    CLAIMED     DEVICE       HITACHI OPEN-V
                         /dev/dsk/c40t0d0   /dev/rdsk/c40t0d0
disk    202  45/0/2/0/0/0/0/5/0/0/1.1.73.0.0.0.1   sdisk    CLAIMED      DEVICE       HITACHI OPEN-V
                         /dev/dsk/c40t0d1   /dev/rdsk/c40t0d1
disk    203  45/0/2/0/0/0/0/5/0/0/1.1.73.0.0.0.2   sdisk   CLAIMED       DEVICE       HITACHI OPEN-V
                         /dev/dsk/c40t0d2   /dev/rdsk/c40t0d2
disk    204  45/0/2/0/0/0/0/5/0/0/1.1.73.0.0.0.3   sdisk   CLAIMED       DEVICE       HITACHI OPEN-V
                         /dev/dsk/c40t0d3   /dev/rdsk/c40t0d3
disk    205  45/0/2/0/0/0/0/5/0/0/1.1.73.0.0.0.4   sdisk   CLAIMED       DEVICE       HITACHI OPEN-V
                         /dev/dsk/c40t0d4   /dev/rdsk/c40t0d4
disk    206  45/0/2/0/0/0/0/5/0/0/1.1.73.0.0.0.5   sdisk   CLAIMED       DEVICE       HITACHI OPEN-V
                         /dev/dsk/c40t0d5   /dev/rdsk/c40t0d5
disk    207  45/0/2/0/0/0/0/5/0/0/1.1.73.0.0.0.6   sdisk   CLAIMED       DEVICE       HITACHI OPEN-V
                         /dev/dsk/c40t0d6   /dev/rdsk/c40t0d6
disk    208  45/0/2/0/0/0/0/5/0/0/1.1.73.0.0.0.7   sdisk   CLAIMED       DEVICE       HITACHI OPEN-V
                         /dev/dsk/c40t0d7   /dev/rdsk/c40t0d7

Regards !!

[iazuarah]

The problem with the GuidMgr was resolved. I disabled all the components. After that, i can attach my vhba to the vm using your sintax.

My problem now is that the vm didn't discover the luns under this vhba. Obviously i declare this new vwwn's to the fabric switch zonning for the hitachi storage.

Some idea ??.

Regards

[Jason_L]

---

@iazuarah wrote:
The problem with the GuidMgr was resolved. I disabled all the components. After that, i can attach my vhba to the vm using your sintax.

My problem now is that the vm didn't discover the luns under this vhba. Obviously i declare this new vwwn's to the fabric switch zonning for the hitachi storage.

Some idea ??.

Regards

---

Do you see the WWN logged into the fabric?

For B-Series it will look like:

#switchshow

17 17 id N8 Online FC F-Port 

1 N Port + 3 NPIV public

The above shows port 17 is a NPIV port with 3 devices logged in.

Then you can do a "portshow (port number)" to list the NPIV WWN's sharing/logged into that port.

Also, you have to make sure NPIV is enabled on the switch/port.

[iazuarah]

Well, after make an extra probes, everything is working now. Thank's for the support !!

[Dennis Handly]

>HP has reserved for NPIV is 0x50014c2000000000 for Port WWNs and 0x50014c2800000000 for Node WWNs.

The OUI for these is 0x14c2, which belongs to HP.

>vHBAs, vWWNs may safely be picked from the range 0x100000110a030000

The OUI for this is 0x110a, which also belongs to HP.

http://standards.ieee.org/develop/regauth/oui/oui.txt