VMware Cloud Community
vVikingNL
Contributor
Contributor
Jump to solution

L4_Protocol vs L4protocol error using initialize-L4PortSerServiceEntry cmdlet (PowerCLI)

I'm using the "new" vmware.sdk.nsx.policy powershell module.

I'm trying to clone NSXv service objects to NSXt-service objects.

When I'm trying to create the Service object, it keeps complaining:

Invoke-PatchServiceForTenant : Error calling PatchServiceForTenant: {
 "details" : "Field level validation errors: {required property service_entries[0].l4_protocol is missing}"

The Initialize-L4PortSetServiceEntry cmdlet keeps returning an "L4Protocol" property instead of "L4_Protocol" property <- look at the "_".
I'm not sure where I can give feedback to the VMware team regarding this flaw.
Does someone have a workaround for this?

Reply
0 Kudos
1 Solution

Accepted Solutions
vVikingNL
Contributor
Contributor
Jump to solution

Reply
0 Kudos
1 Reply
vVikingNL
Contributor
Contributor
Jump to solution

This is solved

Reply
0 Kudos