I ran into the same issue as described by Eric Sloof: https://www.ntpro.nl/blog/archives/3570-Edge-Tunnels-Down-when-hosting-NSX-T-on-the-same-DVS.html The problem I had was i did not have enough uplinks to create a new dvSwitch to get the tunnel to work. For the tunnel to work, the geneve traffic has to leave the host and get routed back in. I had a layer 3 physical switch and decided to make use of inter-vlan routing. Once logged into the switch:...
Some notes from a recent lab I configured: My current lab looks like this - I have few production VMs in one VLAN segment External network access and Internet access is through another VLAN segment There is a jumpbox VM that is uplinked to both the VLAN segments. VMware vDS is currently being used and there are no free uplinks to make use of nvds. What do I want to accomplish?...
I accidentally used the wrong VLAN on a portgroup in vDS while playing with NSX-T.(long story) This caused vCenter to lose access to all the hosts in a cluster. There is a KB article that goes through a few hoops before we can get the hosts back into vCenter Server, Recovering from a management portgroup VLAN misconfiguration on a vNetwork Distributed Switch (vDS) To resolve the issue, As i still had access to vCenter, after configuring the right vlan in vCenter I used net-dvs to manually change the vlan on each vmkernel interface....
Have you ever wondered why esxtop will not work in a Mac OS X terminal? This has been on my mind lately and i’ve managed to get esxtop to work in Mac OS X. Just change the terminal emulation to xterm instead of xterm 256 Launch terminal -> Terminal -> Preferences -> Profiles -> Select Profile -> Advanced -> Change declare terminal as to “xterm” ….the why? Esxi by default uses the busybox shell which uses xterm for emulation....
So I’ve been trying to get Horizon direct connection working in my home lab. The goal is to remote into a home PC using the Horizon client(PCOIP/BLAST) via DDNS, PFSense and Horizon direct connection. For the direct connection feature, one of the key requirements is to run the Horizon agent install silently using the command, VMware-Horizon-Agent-x86_64-7.8.0-12599301 /v VDM_SKIP_BROKER_REGISTRATION=1 Little did I know I would spend an hour troubleshooting the agent install, which usually is a straight forward install....