VMware Performance Community
BAllen22
Contributor
Contributor
Jump to solution

VMmark 3.1.1 - Provisioning Issue

Ran into an issue when provisioning where we were hit with an exception error as a result of using a dvswitch port group. The error reads: Exception Caught: DC Null Exception : Review Log and Configurationcheck naming : exitSetting false

Exception in thread "main" java.lang.NullPointerException
at com.vmware.vim25.mo.InventoryNavigator.retrieveObjectContents(InventoryNavigator.java:62)
at com.vmware.vim25.mo.InventoryNavigator.searchManagedEntities(InventoryNavigator.java:53)
at com.vmware.vim25.mo.InventoryNavigator.searchManagedEntities(InventoryNavigator.java:38)
at com.vmware.vmmark.VcsComm.ValidateProvisioningConfiguration(VcsComm.java:644)
at com.vmware.vmmark.VMmark3.main(VMmark3.java:1779)

It did work when we created a new port group on a new standard switch but that's obviously not ideal for long-term use because now we have one leg from each host in the standard switch and one in the distributed switch.

Any assistance you can provide would be great!

0 Kudos
1 Solution

Accepted Solutions
jpschnee
VMware Employee
VMware Employee
Jump to solution

Hello, 

Dvswitches are supported but they do required the use of ephemeral distributed port groups.  Can you double check that things were setup correctly and try again?  Also, you may want to ensure that names passed were correct and that there aren't duplicate names involved.  The null exception is often due to a search for a object type that wasn't found.

-Joshua

View solution in original post

0 Kudos
1 Reply
jpschnee
VMware Employee
VMware Employee
Jump to solution

Hello, 

Dvswitches are supported but they do required the use of ephemeral distributed port groups.  Can you double check that things were setup correctly and try again?  Also, you may want to ensure that names passed were correct and that there aren't duplicate names involved.  The null exception is often due to a search for a object type that wasn't found.

-Joshua
0 Kudos