VMware Solutions Discussions

cancel
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for 
Search instead for 
Did you mean: 

VMware Solutions Discussions

Start a New Post

Vibe ERROR: Could not find identifying LUN on storage appliance

jensendw2525
‎2008-10-15 09:48 AM
2,612 Views

I have been trying to get Vibe up and running, everything seems to work fine, but it errors with the following:

ERROR: Could not find identifying LUN on storage appliance 10.0.33.11!
Exiting with return code: 10

Please see below for the program output, it doesn't look like it's a permissions error to me:

LOG REPORT FOR VIBE
-----------------------------------------------------
VIBE Version: 1.0.3
Log Filename: C:\Program Files\NetApp\VIBE\Report\VIBE_20081015_082917.log
Backup Start Time: Wed Oct 15 08:29:17 2008
Datastore(s) selected: Mirrored_VMFS1,Mirrored_VMFS3
Datastore snapshot prefix will be used (VIBE_ds_snap).
Command line arguments successful.
Initializing connectivity to Virtual Center and storage appliances.
Converting Virtual Center hostname to IP address ...
Attempting to ping Virtual Center 10.0.33.130 ...
Ping of Virtual Center 10.0.33.130 successful.
Testing login to Virtual Center 10.0.33.130 ...
Virtual Center login successful.
Attempting to ping storage appliance 10.0.33.11 ...
Ping of storage appliance 10.0.33.11 successful.
Attempting to ping storage appliance 10.0.33.11 ...
Ping of storage appliance 10.0.33.11 successful.
Testing login to storage appliance 10.0.33.11 ...
Adding IP address 10.0.33.11 for storage appliance 10.0.33.11 ...
Storage appliance login successful.
Collecting VMware and storage appliance configuration data.
Collecting LUN information ...
Attempting to collect LUN serial numbers for storage appliance 10.0.33.11 ...
Already collected LUN serial numbers for storage appliance 10.0.33.11 ...
Collecting datacenter information ...
Datacenter information collected.
Collecting host system information ...
Host system information collected.
Looking for the requested Datastore(s) ...
Datastore discovered: ph33enoc01:storage1 (type: VMFS).
Datastore discovered: ph33enoc02:storage1 (type: VMFS).
Datastore discovered: ph33enoc04:storage1 (type: VMFS).
Datastore discovered: ph33noc05:storage1 (type: VMFS).
Datastore discovered: ph33enoc06:storage1 (type: VMFS).
Datastore discovered: ph33enoc07:storage1 (type: VMFS).
Datastore discovered: ph33enoc08:storage1 (type: VMFS).
Datastore discovered: ph33enoc09:storage1 (type: VMFS).
Datastore discovered: ph33enoc10:storage1 (type: VMFS).
Datastore discovered: ph33enoc03:storage1 (type: VMFS).
Datastore discovered: Mirrored_VMFS1 (type: VMFS).
Requested Datastore (Mirrored_VMFS1) is available.
Saving virtual machine information for PH40GNP01.
Saving virtual machine information for PH10GNP02.
Saving virtual machine information for PH54ENOC01.
Saving virtual machine information for PH53GNP01.
Saving virtual machine information for PH10ENOC01.
Saving virtual machine information for PH52ENOC01.
Searching for matching disk name vmhba2:0:0 on storage appliance 10.0.33.11 ...
Checking host system ph33enoc08 ...
Name = vmhba2:0:5, UUID = 43346373694a4b6f416c3442.
Name = vmhba2:0:7, UUID = 43346373694a4b74436a4430.
Name = vmhba2:0:2, UUID = 4334636e4c4a4a6d6e2d6975.
Name = vmhba2:0:0, UUID = 4334636e4c4a4a47434a3850.
Name = vmhba2:0:6, UUID = 43346373694a4b7338575672.
Checking host system ph33enoc03 ...
Name = vmhba2:0:5, UUID = 43346373694a4b6f416c3442.
Name = vmhba2:0:7, UUID = 43346373694a4b74436a4430.
Name = vmhba2:0:2, UUID = 4334636e4c4a4a6d6e2d6975.
Name = vmhba2:0:0, UUID = 4334636e4c4a4a47434a3850.
Name = vmhba2:0:6, UUID = 43346373694a4b7338575672.
Checking host system ph33enoc04 ...
Name = vmhba2:0:5, UUID = 43346373694a4b6f416c3442.
Name = vmhba2:0:7, UUID = 43346373694a4b74436a4430.
Name = vmhba2:0:2, UUID = 4334636e4c4a4a6d6e2d6975.
Name = vmhba2:0:0, UUID = 4334636e4c4a4a47434a3850.
Name = vmhba2:0:6, UUID = 43346373694a4b7338575672.
Checking host system ph33enoc06 ...
Name = vmhba2:0:5, UUID = 43346373694a4b6f416c3442.
Name = vmhba2:0:7, UUID = 43346373694a4b74436a4430.
Name = vmhba2:0:2, UUID = 4334636e4c4a4a6d6e2d6975.
Name = vmhba2:0:0, UUID = 4334636e4c4a4a47434a3850.
Name = vmhba2:0:6, UUID = 43346373694a4b7338575672.
Checking host system ph33enoc07 ...
Name = vmhba2:0:5, UUID = 43346373694a4b6f416c3442.
Name = vmhba2:0:7, UUID = 43346373694a4b74436a4430.
Name = vmhba2:0:2, UUID = 4334636e4c4a4a6d6e2d6975.
Name = vmhba2:0:0, UUID = 4334636e4c4a4a47434a3850.
Name = vmhba2:0:6, UUID = 43346373694a4b7338575672.
Checking host system ph33enoc09 ...
Name = vmhba2:0:5, UUID = 43346373694a4b6f416c3442.
Name = vmhba2:0:7, UUID = 43346373694a4b74436a4430.
Name = vmhba2:0:2, UUID = 4334636e4c4a4a6d6e2d6975.
Name = vmhba2:0:0, UUID = 4334636e4c4a4a47434a3850.
Name = vmhba2:0:6, UUID = 43346373694a4b7338575672.
Checking host system ph33enoc01 ...
Name = vmhba2:0:5, UUID = 43346373694a4b6f416c3442.
Name = vmhba2:0:7, UUID = 43346373694a4b74436a4430.
Name = vmhba2:0:2, UUID = 4334636e4c4a4a6d6e2d6975.
Name = vmhba2:0:0, UUID = 4334636e4c4a4a47434a3850.
Name = vmhba2:0:6, UUID = 43346373694a4b7338575672.
Checking host system ph33enoc10 ...
Name = vmhba2:0:5, UUID = 43346373694a4b6f416c3442.
Name = vmhba2:0:7, UUID = 43346373694a4b74436a4430.
Name = vmhba2:0:2, UUID = 4334636e4c4a4a6d6e2d6975.
Name = vmhba2:0:0, UUID = 4334636e4c4a4a47434a3850.
Name = vmhba2:0:6, UUID = 43346373694a4b7338575672.
Checking host system x.x.x.x ...
Checking host system ph33enoc02 ...
Name = vmhba2:0:5, UUID = 43346373694a4b6f416c3442.
Name = vmhba2:0:7, UUID = 43346373694a4b74436a4430.
Name = vmhba2:0:2, UUID = 4334636e4c4a4a6d6e2d6975.
Name = vmhba2:0:0, UUID = 4334636e4c4a4a47434a3850.
Name = vmhba2:0:6, UUID = 43346373694a4b7338575672.
Checking host system ph33enoc05 ...
Name = vmhba2:0:5, UUID = 43346373694a4b6f416c3442.
Name = vmhba2:0:7, UUID = 43346373694a4b74436a4430.
Name = vmhba2:0:2, UUID = 4334636e4c4a4a6d6e2d6975.
Name = vmhba2:0:0, UUID = 4334636e4c4a4a47434a3850.
Name = vmhba2:0:6, UUID = 43346373694a4b7338575672.
ERROR: Could not find identifying LUN on storage appliance 10.0.33.11!
Exiting with return code: 10

Any ideas?

0 Kudos
4 REPLIES 4

rmatt
NetApp
‎2008-10-18 04:37 PM
2,612 Views

It's not clear why the LUN serial number isn't matching up against the storage controllers. Can you send the output of 'lun show -v' (specifically looking for the serial number of the two VMFS datastores in question) on 10.0.33.11? VIBE does a conversion of the VMware UUID and pulls out the serial numbers, and we compare that to the LUN serial numbers on storage appliance 10.0.33.11.

For example, I see the following output for vmhba2:0:0 on ph33enoc03:

Name = vmhba2:0:0, UUID = 4334636e4c4a4a47434a3850.

If I convert the UUID to the LUN serial number (reversing the function), I should see the serial number C4cnLJJGCJ8P, which may/may not be the LUN you are looking for.

I also see x.x.x.x as a host system -- is that accurate for your environment? Finally, can you send your command line -- you are backing up multiple datastores. Are they on the same storage controller?

Let me know, thanks,

--Matt

0 Kudos

jensendw2525
‎2008-10-20 08:30 AM
In response to rmatt
2,612 Views

I spoke to NetAPP support after posting this, apparnetly it's a bug with Vibe 1.0.3, I installed 1.0.6 and this issue was gone.

0 Kudos

rmatt
NetApp
‎2008-10-20 08:36 AM
In response to jensendw2525
2,612 Views

I would recommend getting 1.0.8 until they get the latest version up on the NOW ToolChest. That's supposed to happen any day now. Contact me directly if you are having trouble getting it in the meantime.

Thanks,

--Matt

0 Kudos

rmatt
NetApp
‎2008-10-20 02:29 PM
In response to jensendw2525
2,612 Views

Version 1.0.8 is available on the NOW ToolChest. Feel free to download it or let me know if you can't get access to it.

Thanks,

--Matt

0 Kudos
All Community Forums
Public