Highlighted
Enthusiast
Enthusiast

BUG: VlanID always zero for vSwitch PortGroups

Jump to solution

After upgrading vCO 5.5 to 5.5.1 I discovered to my dismay that it is now impossible to retrieve the vlan ID for a traditional portgroup; the reported vlanId is now always '0' (not null or undefined).

This is clearly a bug, and in my case it breaks all sorts of things.

I use the following code, which worked in 5.5:

var hosts=Server.findAllForType("VC:HostSystem");

var host=hosts[0];

allpg=host.config.network.portgroup

for (var n=0; n<allpg.length;n++) {

  spec=allpg[n].spec;

  var pgvlan=spec.vlanId

  pgname=spec.name

  System.log("Portgroup "+pgname+" has vlan "+pgvlan)

}


As of version 5.5.1, the vlan ID returned is always 0.

1 Solution

Accepted Solutions
Highlighted
VMware Employee
VMware Employee

This is an issue with the inventory service. You can tell vCO to NOT use the inventory service by adding the following line to vmo.properties, then restarting your vco-server service:

com.vmware.o11n.vim.useInventoryService=false

VMware is aware of the issue and will resolve it in a future release. Until then, you can use the vmo.properties setting as a work-around

If my answer resolved or helped you, please mark it as Correct or Helpful to award points. Thank you! Visit http://www.vcoteam.info & http://blogs.vmware.com/orchestrator for vRealize Orchestrator tips and tutorials - @TechnicalValues on Twitter

View solution in original post

0 Kudos
7 Replies
Highlighted
VMware Employee
VMware Employee

This is an issue with the inventory service. You can tell vCO to NOT use the inventory service by adding the following line to vmo.properties, then restarting your vco-server service:

com.vmware.o11n.vim.useInventoryService=false

VMware is aware of the issue and will resolve it in a future release. Until then, you can use the vmo.properties setting as a work-around

If my answer resolved or helped you, please mark it as Correct or Helpful to award points. Thank you! Visit http://www.vcoteam.info & http://blogs.vmware.com/orchestrator for vRealize Orchestrator tips and tutorials - @TechnicalValues on Twitter

View solution in original post

0 Kudos
Highlighted
VMware Employee
VMware Employee

Have you opened a support request for this ?

If my answer resolved or helped you, please mark it as Correct or Helpful to award points. Thank you! Visit http://www.vcoteam.info & http://blogs.vmware.com/orchestrator for vCenter Orchestrator tips and tutorials - @vCOTeam on Twitter
0 Kudos
Highlighted
Enthusiast
Enthusiast

Well, if I disable the inventory service I can't even access vcenter:

  • ch.dunes.util.DunesServerException: Could not initialize class com.vmware.vmo.plugin.vi4.VimPluginFactory

Which is bad Smiley Wink

0 Kudos
Highlighted
VMware Employee
VMware Employee

Then you definitely need to open an SR in case this is a known issue with a fix.

If my answer resolved or helped you, please mark it as Correct or Helpful to award points. Thank you! Visit http://www.vcoteam.info & http://blogs.vmware.com/orchestrator for vCenter Orchestrator tips and tutorials - @vCOTeam on Twitter
0 Kudos
Highlighted
Enthusiast
Enthusiast

Yep, I did open an issue immediately after posting the thread here on the community.

0 Kudos
Highlighted
Enthusiast
Enthusiast

Okay, I tried removing and readding one of my vcenters and either that, or the second restart of the vCO server, actually helped.

So now I am able to both access the vCenter inventory (whew) and the portgroupSpec contains the correct vlanId.

Thank you very much, Burke - that was a very quick response, impressive work Smiley Happy

Highlighted
VMware Employee
VMware Employee

It seems that leveraging the inventory service has been the source of a lot of gaps like this one. You should be all set now.

If my answer resolved or helped you, please mark it as Correct or Helpful to award points. Thank you! Visit http://www.vcoteam.info & http://blogs.vmware.com/orchestrator for vCenter Orchestrator tips and tutorials - @vCOTeam on Twitter
0 Kudos