Some initial discovery troubleshooting I’d recommend: Get a better view of the whole picture, and then narrow down in areas where it makes sense. It’s always best not to draw conclusions and to be as logical and methodical as possible. Just because you can’t ping something does not mean the virtual machine is completely isolated. When it comes to troubleshooting virtual machine network connectivity, the best place to start is to simply gather information relating to the problem – what works and what doesn’t.
More often than not, it winds up being something quite simple. It may be tempting to quickly draw conclusions and dive right into packet captures and even guest operating system troubleshooting, but knowing what questions to ask can make all the difference when trying to narrow down the problem. You’ve got your virtual machines, their respective network stacks, Standard vSwitches, Distributed Switches, different load balancing types, physical network adapters, their respective drivers, the vmkernel itself and we haven’t even begun to mention what lies outside of the host yet. Networking in vSphere is a very far reaching topic with many layers. As vague and simple as that description is, it may not always be clear where to even start looking for a solution. Perhaps one of the most common types of problems we encounter here at VMware Technical Support is relating to loss of network connectivity to one or more virtual machines on a host.
0 kommentar(er)
