It turns out to be a simple mistake while setting up the vsphere environment, but I think it’s worth noting it down so that it might remind me of not making the same mistake again…
When I set up the first vsphere host, host 1, I gave it a static ip of 192.168.*.* and I created a DNS record for this host in my DNS server with 192.169.*.* with typo. I could ping the host somehow from my environment and then got the host set up. But I noticed the connection was quite slow and when I checked back the ping result, I notice the latency was 200ms + which was not normal… I tried a lot of troubleshooting because my network is not a pure and simple internal domain network. I set up the VPN for my lab environment so that it can talk to services outside China and the performance could be good…
I troubleshooted again and again and I even checked the DNS records of this host several times. Finally it turned out the ip was gave wrong from DNS server and one more thing, that ip was given to another host before and the Nslookup of that ip still showed that other host which has been removed from the environment. But I finally corrected it all and now it works as expected.
A simple mistake but could cause us much time and effort to figure out. And I know it happens to our work as well, sometimes, it’s not we are not capable of doing certain work, but because some mistakes happened without our awareness and we need to spend more time to find them out and correct. This is also why we need formal documentation created for most of the work, especially when it comes to complicated work.