VMware Networking Community
SrVMwarer
Hot Shot
Hot Shot

Can't create Logical Switches

Hello VMwarer,

Kindly I have deployed successfully my NSX Manager and a single controller within single cluster with two ESXi hosts prepared everything VxLAN and Transport Zones all is fine, but when I create a new LS it give me this Error message

The last operation failed for the entity with the following error message.

Error creating network vxw-dvs-13-universalwire-5-sid-7000-VDI - A specified parameter was not correct: spec.uplinkTeamingPolicy.uplinkPortOrder.standbyUplinkPort; nested exception is (vmodl.fault.InvalidArgument) {

   faultCause = null,

   faultMessage = (vmodl.LocalizableMessage) [

      com.vmware.vim.binding.impl.vmodl.LocalizableMessageImpl@5d841505

   ],

   invalidProperty = spec.uplinkTeamingPolicy.uplinkPortOrder.standbyUplinkPort

}.

Also this is my VDS Configs vmks at the very bottom 192.168.2.40/192.168.2.41 is for my hosts and Management Services enabled on both created automatically as much as I can remember while preparing hosts.

PSO VDS.PNG

Notice, I am still learning the ABC NSX  Smiley Happy , thanks for you help

Regards, İlyas
13 Replies
SrVMwarer
Hot Shot
Hot Shot

UP

Regards, İlyas
Reply
0 Kudos
mauricioamorim
VMware Employee
VMware Employee

This usually happens if you change something on the VDS that was configured by NSX. Did you do anything on the vDS after prepping the hosts?

Error suggests that:

  • NSX manager is referencing an uplink to its port group which no longer exists.
  • some of the uplinks were removed from DVS.
nipanwar
Enthusiast
Enthusiast

seems to be issue with load balancing policy,

What is the policy configured on NSX while configuring VXLAN (under host preparation) and what is the policy on vtep (vxlan) port group on vDS?

Sample attached

SrVMwarer
Hot Shot
Hot Shot

nipanwar​  mauricioamorim 

Many thanks to you guys, I'd like to tell that I am deploying that lab on my vCloud the VMK that is VxLAN Enabled configured with IP 192.168.2.4x bound to The 192 Network UP link portgroup that is attached to VMNIC that is also configured in the same Network subnet

Regards, İlyas
Reply
0 Kudos
nipanwar
Enthusiast
Enthusiast

that is ok, you have two uplinks in the dvs prepared for Vxlan per host. But did you check the load balancing policy I asked for?

SrVMwarer
Hot Shot
Hot Shot

I am checking and will  report to you immediately, just getting access back to me Smiley Happy

Thanks for you patients

Regards, İlyas
Reply
0 Kudos
SrVMwarer
Hot Shot
Hot Shot

NSXVTEP.png

How can I fix and why it have to be Routing based on original VM port and teaming policy as you stated, I am still learning the dots of NSX

Many many thanks in Avdnace

Regards, İlyas
nipanwar
Enthusiast
Enthusiast

not necessary to have route based on source ID. For clarification you can refer to NSX and Teaming Policy – Route to Cloud

Why i asked for those detail is to make sure that your NSX teaming policy and vDS teaming policy are same and there is no mismatch.

Now from your screenshot I can see that NSX teaming policy is failover which should create 1 NSX vmk VTEP per host and thats what I can see from your previous details.

Can you also verify vDS Vxlan port group load balance policy?

SrVMwarer
Hot Shot
Hot Shot

VxLAN VDP port: Routing based on originating virtual port,

another question sorry for my misunderstanding what is the difference between vxlan vds policy and NSX teaming policy

Thanks in Advance.

Regards, İlyas
Reply
0 Kudos
nipanwar
Enthusiast
Enthusiast

the teaming policy under NSX VXLAN configuration and teaming policy under Vxlan port group should be same. When you install NSX and select the teaming policy (failover in your case) the vxlan port group is created with that policy.Looks like in your environment vxlan port group policy is manually changed after NSX installation.


Now can you change Vxlan port group policy to failover so that it matches that of NSX installation settings and then try if it fixes the issue.

Reply
0 Kudos
SrVMwarer
Hot Shot
Hot Shot

I have only one physical uplink each hosts

NSXVTEP 2.PNG

Regards, İlyas
Reply
0 Kudos
nipanwar
Enthusiast
Enthusiast

irrespective of the number of physical nics on the host, you still need a load balancing policy which should be type failover.

SrVMwarer
Hot Shot
Hot Shot

sorry for long time not replying, internet issue Smiley Happy

Re-deployed :smileygrin: :smileygrin: :smileygrin:

Regards, İlyas
Reply
0 Kudos