All Topics

Hi all,  i am running Workstation 16 Pro with 8 Vm's, specific to each site that I visit. The Vm's need to all be on separate Subnets, i.e. 10.131.xxx.xxx, 172.28.xxx.xxx, 192.168.xxx.xxx, so forth and so on, what I am trying to do is not have to change the host machines IP, I would like to keep this the same for all sites, as it can be problematic changing it due to some routes tables on some sites that are required on the host machine. At some sites i require access to both the physical ethernet network as well as the Wi-Fi network, and I have been able to set this up but I am still required to set the host machine IP to the same range of that of the VM. the issue I have is changing the host machine VM can be problematic due to IT policies, not impossible to work with but i can be time consuming. Unfortunately I can use DHCP either as some site have this feature turned off on their end due. I've read through quite a few KB articles but I am having no luck with setting these up, I sure i am only missing one or two settings.  I have attached pics of the network settings that I have working, is there anyway around this? any information would be greatly appreciated

Hello, we have been slow to migrate our NSX to NSX-T.  We finally got around to it but im missing something as our Edges cant migrate without adding a Gateway now.   We have a very simple setup, we only use NSX for Firewall and 3 Edge Network Load balancers.   We currently have no Virtual Gateway for the Edge NLBs and everything is working great. But when we use the migration tool for NSX-T, when it gets to the Edge migration its says we need to connect them to a Gateway or it will not Migrate them.   We have no cloud stuff.   Is the Gateway really necessary with NSX-T, or am i missing something silly? Can is skip the Edge migration, then just setup new Edges in NSX-t without a gateway, this would be a pain, but we could plan a maintenance window? Just doing simple Load balancing with the Edges If the gateway is needed, This adds a complexity to things that i need to research and learn Thanks for any input  

Hello, I have a need to add resources to my Service Engine ( CPU, RAM, Disk ) which is in production. I haven't found much on the net, can you help me out? I wanted to give as little disruption as possible. Thank you so much, Fabio

Hi everyone,      I'm new to NSX-ALB and I'm trying to load balance our Horizon environment.  I can find some guides on both Avi's website and Vmware's website, but I find them confusing.  Does anyone have a link to a good concise guide for setting up load balancing for both UAG's and for Connection Servers?  Thanks for any help!   Tony

The NSX Manager has a Transport Node Profile on the Fabric > Host side of the Cluster. If I remove the server from vCenter, which is the connected Compute manager, perform the remove NSX configuration in the NSX manager. At this time, NSX remove is done in the Standalone tab, not the Cluster tab in the Fabric> Host menu.  Do I have an NSX API to check if this NSX remove is complete?   What I need is an NSX API, not a command. I already know that I can run and check the command below. esxcli software vib list ⁇ grep -E 'nsx' And in the NSX API, GET / transport-nodes /{transportnode-id}/ state is the state value pending, in_progress, success, failed, partial_success, orphaned, unknown I can check the install and see the results, I can not use it in Remove.   Please let me know if you know NSX API ~

  My NSX-T environment is 3.1.3. After the host is ready, it displays a status of "closed", but its manager status, network card, and tunnel are all displayed in green, and there are no errors reported about the host in the alarm，Please help to take a look. Thank you！

Hi All “””I have setup VMware SDDC and it has default NSX Edge. I have deployed another set of NSX Edge and gave inbound internet connectivity to it i.e. DMZ environment. I have deployed ALB. The Management layer and the backend nginx servers reside on the overlay segment connected to the default NSX Edge. The Virtual service component (on ALB) is hosted on the DMZ overlay segment for public access to the backend servers. I have enabled the routing between the edges. Windows machine hosted on Web segment is able to communicate to Windows machine hosted on the external AVI-VS segment.””” I have setup static route on the external vrf context pointing to its default gateway The issue I am facing is the ALB VS hosted on the public-facing Edge is not able to communicate to the backend servers. Any suggestions here .. thanks

Hi Experts of NSX, I got some questions if someone already have experience on how to fix this kind of error. I am currently migrating from NSXV to NSXT 3.2.3.0.0xxxxx I dont have error during the migrate configuration but on the prepare infrastructure i have this error always. Failed to prepare infrastructure for host migration [Reason: SecurityGroup failed with '400: Another object with same name : IPv4_IPSet_DFW_VLANxxxxx_securitygroup-xxxx already exists in the current scope : globalroot-0. for url: https://xxxxxxxx.xxx..local/api/2.0/services/ipset/globalroot-0'].   appreciate your response.  thank you

Hi, I have a problem, I was using Vmware with the softwares I needed to share with my workers fine but then a problem occured with one of them, the software I needed to share are single user only, as in only 1 user can use them and I have more then 10 people who are gonna use this simultaneously, is there any way I can make rdp give my staff members seperate instances for each new rdp connection that connects to that Vm? or I can turn the software into multiuser software

Hi everyone, we have migrated VMs from one VCF stack where we had NSX-T Version 3.1.3.5.0.19068434 to another VCF stack with NSX-T version 3.2.2.1.0.21487560. We noticed that we cannot open URLs of ILO management interfaces from VMs which have IPs in the new VCF stack.  We get an error in browser: ERR_SSL_SERVER_CERT_BAD_FORMAT. If we try to do the same from the same VM, but we change IP to be from traditional VLAN based network, no issue. If I move VM back to the old VCF stack, continue using NSX-T segment in the old VCF stack, also no issue. We did a bit of digging and did tests with PING command and noticed that packets get fragmented. But not always.  For example: • I tried to ping with packet size 1472 – fragmented • Tried to reduce packet size to 1400 – worked • Increased packet size to 1450 – worked • Increased to 1470 – fragmented • Decreased to 1468 – fragmented • Decreased to 1462 – worked • Increased to 1472 – failed 2x and 3rd time it started working. This is happening sometimes when we try ping VMs default gateway using packet size 1472! But then it starts working and on the next hop packets are fragmented and after that it starts working and on the 3rd hop it gets fragmented etc. Of course we opened a ticket with VMware and they didn't find anything in the logs. Network team says physical network devices look fine, all good. The moment VM is not using NSX-T segment, even if it stays in the same cluster, running on the same host, we don't see the problem. Has anyone seen or heard about similar issue? Any ideas how to try to troubleshoot this? Thanks for any suggestions or ideas what to try to identify the root cause of this.

I assigned the wrong network to VM, therefore my host and my VM machine is not responding. My host is a management host and attached to a VLAN. The wrong network that I have attached to my VM has a different VLAN. For that reason I cannot access the host 10.0.x.x and cannot access my VM as well. I need help with suggestions and advices Thank you

When executing the command: $ipsetsvc = Get-NsxtService -Name com.vmware.nsx.ip_sets there are over a thousand results, but only the first 50 are returned. Can someone assist with how to get the next page, and the next, etc.?   Thanks

I need help understanding something. I've been referencing NSX Reference Design Guides, Multi-Location Design Guides, and a lot more but haven't quite found what I'm looking for.  In my lab environment, I have an edge cluster stretched between two sites. Site A has two edge nodes and Site B has two edge nodes. All North/South traffic should be routed through Site A unless it goes completely down and then Site B would take over. I've created my failure domains with Site A being the preferred site. I also want my SR's running in Active-Standby mode. So essentially, I would have one Active edge node out of all four nodes. If it goes down, the other edge node at site A should take over. Only if both of those edge nodes go down should the nodes at Site B take over.  Most of what I've found in VMware documents and online only discuss failure domains with an active-active SR configuration. Does anyone know if there's a way to specifically configure the node failover the way I'm wanting? Will I be achieving this by configuring Active-Standby on my SRs and creating the two failure domains?

Hello, We have the below scenario: 2 clusters deployed within a vCenter (v 7) - first cluster with 8 hosts, second one with 11 hosts - that are currently managed by one NSX-T manager ( v 3.2.3). We would like to add one more cluster with 15 host to this vcenter under a different NSX-T manager with same version using the multi-NSX option that is available from NSX-T 3.2.2. The NSX-T limit for system wide logical switch ports is 25000, is this limit applicable to only one NSX-T manager or for the entire vCenter managed by two NSX-T managers that are in multi-NSX mode?