Highlighted
Enthusiast
Enthusiast

InvalidArgument when reading datastore details

Hi all,

I'm reviewing a system for a customer and have come across a weird error. When trying to view the Path Management settings for a VMFS volume via VirtualCenter, I get the following error: "InvalidArgument"=Value of '0' is not valid for 'index'. Parameter name: index".

Has anyone seen this before ?

I've included a screenshot.

Thanks,

Neil.!InvalidArgument.jpg!

0 Kudos
5 Replies
Highlighted
Hot Shot
Hot Shot

i too have seen this error, InvalidArgument=Value of '3' is not valid for 'index' in my VC 2.X environment. Seems to be when navigating AWAY from datastores, or selecting an esx server underneath the cluster in the Hosts and Clusters view. Not exactly sure what this is, havent seen any other posts regarding this particular error. Everything else seems to continue to work. Any ideas?

If you found this or any other post helpful please consider the use of the Helpfull/Correct buttons to award points

If you found this or any other post helpful please consider the use of the Helpfull/Correct buttons to award points
0 Kudos
Highlighted
Contributor
Contributor

I'm getting the same error right now and can't figure out what the issue is. You can query the paths via the cli and everything looks fine, not sure why it's broken in VI Client...

0 Kudos
Highlighted
Hot Shot
Hot Shot

have you tried to do a esxcfg-rescan of the hbas?

This sounds like something has gone off.

Can you also look at /vmfs/volumes/ anything strange there?

0 Kudos
Highlighted
Contributor
Contributor

I have tried rescanning and it didn't change the behaviour. Nothing other than that error is out of the ordinary, the storage works fine. If I take a look at /vmfs/volumes everything looks good and if I look at /vmfs/devices/disks it shows two paths to that volume via the two iSCSI HBAs. I do see the same error on every ESX host that is using that particular iSCSI target, which is a DELL MD3000i.

0 Kudos
Highlighted
Hot Shot
Hot Shot

Hi Philxor,

Chances are then that it might5 be a trivial misconfig on the Md3000i

Here is a document from DEll on how to setup the MD3000i http://www.dell.com/downloads/global/solutions/md3000i_esx_deploy_guide.pdf

To be honest the setup is pretty simple. It starts on page 4.

Not sure you will want to look at it since your servers are working and it seems like a cosmetic error

0 Kudos