topic Re: hpvmmodify: ERROR (host): GUID service error: Could not connect to GUID server. in Operating System - HP-UX

hpvmmodify: ERROR (host): GUID service error: Could not connect to GUID server.

Syedfurquan — Sun, 18 Jan 2015 20:55:23 GMT

Hello,

I am trying to create wwn for HPVM:

On physical host GUID server has been created as below:

# /opt/guid/bin/guidconfig -l
HOST=hp-ux .......<(Physical Host which is GUID server)
BE_LIBS=wwn

/opt/guid/bin/guidmgmt -L wwn
Permission denied (publickey,keyboard-interactive).
listGUIDrange() failed. error: Could not connect to GUID server

ON HP VM it is :

# /opt/guid/bin/guidconfig -l
HOST=hp-ux ...... <(Physical host GUID Server)
BE_LIBS=wwn

ON HPVM wwn is created :

# /opt/guid/bin/guidmgmt -L wwn
Range type Start(Hex) End(Hex) Size(Dec)
=============== ================== ================== ==========
HP-DEFINED-PWWN 0x50014c2000000000 0x50014c2000007fff 32768
HP-DEFINED-NWWN 0x50014c2800000000 0x50014c2800007fff 32768

I tried adding wwn to GUI server

# hpvmmodify -P vm001 -a hba:avio_stor:2,0,0x100000110a030000,0x100000110a030001:npiv:/dev/fcd0

hpvmmodify: Unable to dynamically create device hba:avio_stor:2,0,0x100000110A03
hpvmmodify: The modification process is continuing.
hpvmmodify: The vPar or VM needs to be restarted for all changes to take effect.
Permission denied (publickey,keyboard-interactive).
hpvmmodify: ERROR (host): GUID service error: Could not connect to GUID server.
hpvmmodify: ERROR (vm001): Unable to synchronize vPar or VM device(s) with the d
hpvmmodify: ERROR (vm001): Unable to update the configuration file.
hpvmmodify: ERROR (vm001): Unable to close vPar or VM.
hpvmmodify: Unable to modify the vPar or VM.

Any help how to fix this.

Regards,

Re: hpvmmodify: ERROR (host): GUID service error: Could not connect to GUID server.

Stan_M — Mon, 19 Jan 2015 09:34:11 GMT

2 things are unclear to me:

1. you setup GUIDMGR with range and yet to explicitly specify WWN at hpvmmodify command line,
GUIDMGR is exactly for avoiding that...

2. You say that "guidmgmt -L wwn" on the VSP works and hpvmmodify on VSP fails with ssh authentication
error? That would be pretty unusual. The failing "guidmgmt -L wwn" output is from the GUIDMGR server?
It looked mixed up to me.

Re: hpvmmodify: ERROR (host): GUID service error: Could not connect to GUID server.

Syedfurquan — Mon, 19 Jan 2015 18:12:17 GMT

Hi Stan,

Thanks for the reply.

My requirement is to do a zoning between HPVM (OS=HP-UX 11.31) and 3PAR to map disk on host HP-UX 11.31

1. you setup GUIDMGR with range and yet to explicitly specify WWN at hpvmmodify command line,
GUIDMGR is exactly for avoiding that...

I am not able to set range on GUIDMGR server. When I am trying that it gives me error as mentioned earlier. So I created range on Client.

GUIDMGR Server o/P below:

# guidmgmt -L wwn
Permission denied (publickey,keyboard-interactive).
listGUIDrange() failed. error: Could not connect to GUID

GUIDMGR Client o/p as:

# guidmgmt -L wwn
Range type Start(Hex) End(Hex) Size(Dec)
=============== ================== ================== ==========
HP-DEFINED-PWWN 0x50014c2000000000 0x50014c2000007fff 32768
HP-DEFINED-NWWN 0x50014c2800000000 0x50014c2800007fff 32768

No I have created wwn range for GUIDMGR CLient and then tried to modify it on HP VM but its failing.

# hpvmstatus -P vm001
[Virtual Machine Details]
Virtual Machine Name VM # Type OS Type State
==================== ===== ==== ======= ========
vm001 1 SH HPUX On (OS)

[Direct I/O Interface Details]
vPar/VM Physical
Device Adapter Bus Dev Ftn Mac Address Storage D
======= ======= === === === ================= ========= =

But Physical storage wwn is not detecting on HP VM

Re: hpvmmodify: ERROR (host): GUID service error: Could not connect to GUID server.

Dave Olker — Mon, 19 Jan 2015 18:56:09 GMT

It looks to me that the GUIDmgr server instance was never setup/initialized properly. Did you follow all the steps in the Admin guide to setup the GUIDmgr?

http://h20566.www2.hp.com/hpsc/doc/public/display?sp4ts.oid=4146186&docId=emr_na-c03686172&docLocale=en_US

When I'm setting up a GUIDmgr instance I always verify that I can query the GUID database, setup ranges, etc. on the GUIDmgr server before I get to the point of trying this from the client (i.e. VSP). You may want to go back and try the GUIDmgr setup over again and ensure that the GUIDmgr system can at least query its own database, create ranges of WWNs, etc. and then move onto configuring things on the VSP.

Dave

Re: hpvmmodify: ERROR (host): GUID service error: Could not connect to GUID server.

Syedfurquan — Mon, 19 Jan 2015 19:16:45 GMT

Hi,

GUIDmgr Server instance has been instance successfully as per the HP UX GUID Manager V1.0 Administrator guide.

While installing first time

#/opt/guid/utils/guid_server_prepare.sh

It run successfully and doesn't give any error.

I tried to run it again now with o/p attached.

Also tried:

#/opt/guid/sbin/guiddbutil -c wwn
Command failed: ERROR: database "wwn_db" already exists

Actual Command: create database wwn_db;
/opt/guid/sbin/guiddbutil : create database failed.

Re: hpvmmodify: ERROR (host): GUID service error: Could not connect to GUID server.

Dave Olker — Mon, 19 Jan 2015 19:45:04 GMT

After setting up the server, are you able to create WWN ranges and list them on the GUIDmgr server? If not, have you tried configuring the GUIDmgr server system as a client to itself? In other words, run through the "install client" portion on that same server and see if it can query itself successfully and create/list ranges.

Re: hpvmmodify: ERROR (host): GUID service error: Could not connect to GUID server.

Stan_M — Tue, 20 Jan 2015 10:08:29 GMT

It's ok and expected that running client command on GUIDMGR server fails unless you have configured

the server to be a client as well.

It's ok and expected to create a range on the server from the client on another system.

So there is nothing wrong up to this point.

If, on the same system where "guidmgmt -L wwn" works, hpvmmodify fails to add hba (you would use syntax without WWN to get it from GUIDMGR) due to connection failure, that's weird and the failure is likely to be specific to the user environment (home dir, permissions, real user id, environment variables affecting SSH..).

Re: hpvmmodify: ERROR (host): GUID service error: Could not connect to GUID server.

Syedfurquan — Tue, 20 Jan 2015 10:22:50 GMT

I have already created wwn manually for the HP VM but as mentioned above in the hpvmstatus it is not showing in the I/O details for HP VM.

How I will add thsi to be visible on SAN?

Regards

Re: hpvmmodify: ERROR (host): GUID service error: Could not connect to GUID server.

Stan_M — Tue, 20 Jan 2015 10:41:49 GMT

In the output above you showed only DIO section, but that's for networking DirectIO.

The NPIV goes into this part:

[Storage Interface Details]
vPar/VM Physical
Device Adapter Bus Dev Ftn Tgt Lun Storage Device
======= ========== === === === === === ========= =========================

If hpvmstatus -P xx doesn't show it there, you can also check deferred config using hpvmstatus -P xxx -D,

that will be active after reboot of the guest.

Only the latest version (V6.30) allows adding interfaces dynamically.

Re: hpvmmodify: ERROR (host): GUID service error: Could not connect to GUID server.

Syedfurquan — Tue, 20 Jan 2015 11:00:50 GMT

Hi Stan,

Many thanks for your support.

Attached is the hpvmstatus o/p for HP VM with -D option.

Re: hpvmmodify: ERROR (host): GUID service error: Could not connect to GUID server.

Stan_M — Tue, 20 Jan 2015 11:05:34 GMT

Clearly the NPIV has not been added.

Re: hpvmmodify: ERROR (host): GUID service error: Could not connect to GUID server.

Syedfurquan — Tue, 20 Jan 2015 11:39:08 GMT

could you please provide me the steps what i need to do now...

NPIV we can do for HP VM's also? or it is only for Vpar

I have HP VM no vpar

Re: hpvmmodify: ERROR (host): GUID service error: Could not connect to GUID server.

Syedfurquan — Thu, 22 Jan 2015 20:24:52 GMT

I have configured NPIV for my HPVM hosts. Now in the HPVM status I can see hba avio_stor but when I am doing ioscan -fnNC fc it doesn't show me any fc card.

# ioscan -fnNC fc
# hostname
vm001

hpvmstatus o/p in attachment.

Regards,

Re: hpvmmodify: ERROR (host): GUID service error: Could not connect to GUID server.

Dave Olker — Thu, 22 Jan 2015 20:32:22 GMT

Assuming the ioscan output was from within the VM guest itself, that is expected output. NPIV allows storage to be "presented" directly to the VM guest but is not the same as SR-IOV or Direct I/O where the FC port itself is dedicated to the VM. The port is still virtualized inside the VM guest and associated with the GVSD driver:

# ioscan -fnk

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

============================================================================
ext_bus 6 0/0/0/0/0 gvsd CLAIMED INTERFACE HPVM NPIV Stor Adapter
/dev/gvsd6
ext_bus 0 0/0/0/1/0 gvsd CLAIMED INTERFACE HPVM NPIV Stor Adapter
/dev/gvsd0

Regards,

Dave

Re: hpvmmodify: ERROR (host): GUID service error: Could not connect to GUID server.

Stan_M — Thu, 22 Jan 2015 20:35:48 GMT

That's because the class is not 'fc'. Look up HPVM admin guide under www.hp.com/go/hpux-hpvm-docs

Re: hpvmmodify: ERROR (host): GUID service error: Could not connect to GUID server.

Syedfurquan — Thu, 22 Jan 2015 20:39:14 GMT

Hello Dave,

Thanks for the reply. So I can proceed with the zoning and disk will be availaible on my HPVM?

# ioscan -fnk
Class       I H/W Path     Driver       S/W State   H/W Type     Description
==============================================================================
root        0               root           CLAIMED     BUS_NEXUS
ioa         0 0            cec_gen        CLAIMED     BUS_NEXUS
ba          0 0/0          gh2p           CLAIMED     BUS_NEXUS    Local Bus Adapter
ext_bus     0 0/0/0/0      gvsd           CLAIMED     INTERFACE    HPVM AVIO Stor Adapter
                           /dev/gvsd0
target      0 0/0/0/0.0    tgt            CLAIMED     DEVICE
disk        0 0/0/0/0.0.0 sdisk          CLAIMED     DEVICE       HP      Virtual FileDisk
                           /dev/dsk/c0t0d0     /dev/dsk/c0t0d0s2   /dev/rdsk/c0t0d0    /dev/rdsk/c0t0d0s2
                           /dev/dsk/c0t0d0s1   /dev/dsk/c0t0d0s3   /dev/rdsk/c0t0d0s1 /dev/rdsk/c0t0d0s3
lan         0 0/0/1/0      igssn          CLAIMED     INTERFACE    HP IGSSN PCI AVIO LAN Adapter
lan         1 0/0/2/0      igssn          CLAIMED     INTERFACE    HP IGSSN PCI AVIO LAN Adapter
ba          1 0/0/3/0      legacyio       CLAIMED     BUS_NEXUS    Legacy IO Core I/O Adapter (IFB)
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)
ba          2 0/1          gh2p           CLAIMED     BUS_NEXUS    Local Bus Adapter
ext_bus     2 0/1/5/0      gvsd           CLAIMED     INTERFACE    HPVM NPIV Stor Adapter
                           /dev/gvsd2
ba          3 0/2          gh2p           CLAIMED     BUS_NEXUS    Local Bus Adapter
ext_bus     3 0/2/0/0      gvsd           CLAIMED     INTERFACE    HPVM NPIV Stor Adapter
                           /dev/gvsd3
ba          4 0/3          gh2p           CLAIMED     BUS_NEXUS    Local Bus Adapter
ba          5 0/4          gh2p           CLAIMED     BUS_NEXUS    Local Bus Adapter
ba          6 0/5          gh2p           CLAIMED     BUS_NEXUS    Local Bus Adapter
ba          7 0/6          gh2p           CLAIMED     BUS_NEXUS    Local Bus Adapter
ba          8 0/7          gh2p           CLAIMED     BUS_NEXUS    Local Bus Adapter
processor   0 120          processor      CLAIMED     PROCESSOR    Processor
ba          9 250          pdh            CLAIMED     BUS_NEXUS    Core I/O Adapter
ipmi        0 250/0        ipmi           CLAIMED     INTERFACE    IPMI Controller
                           /dev/ipmi
acpi_node   0 250/1        acpi_node      CLAIMED     INTERFACE    Acpi Hardware
usbmsvbus   1 255/1        mass_storage   CLAIMED     VIRTBUS      USB Mass Storage
ext_bus     1 255/1/0      usb_ms_scsi    CLAIMED     INTERFACE    USB Mass Storage SCSI
#

Re: hpvmmodify: ERROR (host): GUID service error: Could not connect to GUID server.

Dave Olker — Thu, 22 Jan 2015 20:49:56 GMT

The VM guest can see and instantiate the NPIV adapters, so that looks good. I'm a little confused by the hpvmstatus output you posted previously:

hba avio_stor 1 5 npiv /dev/fcd0-0x50060B00006499A8,0x50060B00006499A9
hba avio_stor 2 0 npiv /dev/fcd0-0x100000110A030000,0x100000110A030001

Neither of those NPIV virtual HBAs are using the GUID manager's defined range. Are you no longer using the GUID manager to manage WWNs? Did you hard-code those specific WWNs on the command-line when you added the NPIV instances to this VM?

Compare this against my VSP:

# guidmgmt -L wwn
Range type Start(Hex) End(Hex) Size(Dec)
=============== ================== ================== ==========
HP-DEFINED-PWWN 0x50014c2000000000 0x50014c2000007fff 32768
HP-DEFINED-NWWN 0x50014c2800000000 0x50014c2800007fff 32768

You can see that the *port* WWN range begins at 0x50014c2000000000 and the *node* WWN range begins at 0x50014c2800000000. Each time a virtual HBA is assigned WWNs by the GUIDmgr it assigns one WWN from each range, so my virtual servers end up with virtual HBAs looking like this:

hba avio_stor 0 0 npiv /dev/fcd0-0x50014C2000000002,0x50014C2800000002
hba avio_stor 0 1 npiv /dev/fcd1-0x50014C2000000003,0x50014C2800000003

The first number is the port WWN, and you can see it falls into the configured range on the GUIDmgr. Same goes for the node WWN value falling into the node range.

Your VM guest is not only using values that are not in the HP defined range, your VM is using *consecutive* values for the port and node WWN. Are you absolutely certain this is how you want to manage your WWNs?

Dave

Re: hpvmmodify: ERROR (host): GUID service error: Could not connect to GUID server.

Syedfurquan — Thu, 22 Jan 2015 20:57:22 GMT

Hi Dave,

I have used hard code wwn range for my HPVM than the actual range created on guidmgr. Do now I need to delete these hba avio_stor and recreate new which should be in teh defined range.

# hostname
vm001

I have used below commands to modify it:

#hpvmmodify -P vm001 -a hba:avio_stor:1,5,0x50060b00006499a8,0x50060b00006499a9:npiv:/dev/fcd0

Regards,

Re: hpvmmodify: ERROR (host): GUID service error: Could not connect to GUID server.

Dave Olker — Thu, 22 Jan 2015 21:17:17 GMT

The whole point of using the GUIDmgr is to have it manage the WWNs so you don't accidentally assign the same WWNs to multiple virtual servers. If you're going to hard code values then don't bother with the GUIDmgr, but you'd better be absolutely certain you know what you're doing because using the wrong values can lead to multiple servers (physical or virtual) accessing the same storage and even data corruption.

My recommendation would be to shutdown the VM, delete the existing NPIV vHBAs and create new ones using syntax similar to the following:

# hpvmmodify -P vm001 -a hba:avio_stor::npiv:/dev/fcd0

That syntax tells the VSP to assign the bus/device/function values and tells the GUIDmgr to assign the WWNs. If you want multiple vWWNs then repeat the command to create a second instance. If you have multiple physical FC ports and you want the VM to use multiple paths then you can create the second vHBA and specify a different physical FC port such as /dev/fcd1.

Dave

Re: hpvmmodify: ERROR (host): GUID service error: Could not connect to GUID server.

Syedfurquan — Fri, 23 Jan 2015 13:33:59 GMT

Hello Dave, Stan,

Thanks alot for all yoru support.

As per Dave reference I have deleted all avio_stor and created default HP range for wwn.

vPar/VM                                Physical
Device Adapter    Bus Dev Ftn Tgt Lun Storage   Device
======= ========== === === === === === ========= =========================
disk    avio_stor    0   0   0   0   0 file      /ignite/vmos/vm001
hba     avio_stor    0   4             npiv      /dev/fcd0-0x50014C2000000000,0x50014C2800000000

Now did the zoning on the SAN and hence added the host on 3Par.

Created a new disk for 3par and is visible on vm001 hosts.

# ioscan -fnNC disk
Class     I H/W Path Driver S/W State   H/W Type     Description
===================================================================
disk      2 64000/0xfa00/0x0 esdisk   CLAIMED     DEVICE       HP      Virtual FileDisk
                      /dev/disk/disk2      /dev/rdisk/disk2
                      /dev/disk/disk2_p1   /dev/rdisk/disk2_p1
                      /dev/disk/disk2_p2   /dev/rdisk/disk2_p2
                      /dev/disk/disk2_p3   /dev/rdisk/disk2_p3
disk      7 64000/0xfa00/0x7 esdisk   CLAIMED     DEVICE       3PARdataVV
                      /dev/disk/disk7   /dev/rdisk/disk7

# hostname
vm001

Thanks for all your support.

Regards,