We help IT Professionals succeed at work.

We've partnered with Certified Experts, Carl Webster and Richard Faulkner, to bring you a podcast all about Citrix Workspace, moving to the cloud, and analytics & intelligence. Episode 2 coming soon!Listen Now

x

Vm not accessible in network

Medium Priority
58 Views
Last Modified: 2020-04-14
vm machine get inaccessible suddenly.
which log can be used to verify why the vm got inaccessible
Comment
Watch Question

David Johnson, CDSimple Geek from the '70s
CERTIFIED EXPERT
Distinguished Expert 2019

Commented:
VMware Workstation/Player or ESXI ?
Doodad BoySupprt

Author

Commented:
it is ESXI
David Johnson, CDSimple Geek from the '70s
CERTIFIED EXPERT
Distinguished Expert 2019

Commented:
Check the VM Switch configuration on the other server
Doodad BoySupprt

Author

Commented:
any special command or log i can go and look for it
Louis LIETAERSystem Infrastructure Architect
CERTIFIED EXPERT

Commented:
Hi, Are you able to access to remote console of this vm, with ESXi web sphere client ?
Doodad BoySupprt

Author

Commented:
the vm was not able to rdp and ping. when open the vm console in the vmware server windows was up.
Hello ThereSystem Administrator
CERTIFIED EXPERT
Distinguished Expert 2018

Commented:
What actions have you made recently?

Can you check the IP configuration? Are you able to ping anything in the network form this VM?

Can you disable Windows Firewall for testing purposes?

Isn't it the issue? Inaccessible virtual machines are named as Unknown VM
https://kb.vmware.com/s/article/2172
Doodad BoySupprt

Author

Commented:
i not able to ping anything outside from the vm. gateway, dns, domain
Hello ThereSystem Administrator
CERTIFIED EXPERT
Distinguished Expert 2018

Commented:
Ok.

What actions have you made recently?

Can you check the IP configuration?

Can you disable Windows Firewall for testing purposes?
Doodad BoySupprt

Author

Commented:
no recent change has been made.
IP config in vm able to display, but just not able to perform ping and rdp toward the vm.
Firewall is disable
But i able to ping and rdp when i migrate the vm to another host
Hello ThereSystem Administrator
CERTIFIED EXPERT
Distinguished Expert 2018

Commented:
So it's the host issue. Can you check the IP configuration on the host? The gateway, mask...

Is there any other VM on the host?
Louis LIETAERSystem Infrastructure Architect
CERTIFIED EXPERT

Commented:
You said "But i able to ping and rdp when i migrate the vm to another host", so you have a different network configuration for each ESXi.

So please check each configuration of each switch of each esxi.
Doodad BoySupprt

Author

Commented:
the vm which i migrated within the cluster, migrate to another host in the same cluster
Louis LIETAERSystem Infrastructure Architect
CERTIFIED EXPERT

Commented:
Host being in the same cluster does not insure they are configure the same way, so please check the network configuration of each esxi host
Hello ThereSystem Administrator
CERTIFIED EXPERT
Distinguished Expert 2018

Commented:
Can you check the IP configuration on the host? The gateway, mask...

Is there any other VM on the host?
Doodad BoySupprt

Author

Commented:
yes, there are some other vm on the reported host.
Hello ThereSystem Administrator
CERTIFIED EXPERT
Distinguished Expert 2018

Commented:
Thank you. Are they ok? Pinging, RDP...
Doodad BoySupprt

Author

Commented:
the other vm looks fine 
Doodad BoySupprt

Author

Commented:
meanwhile, i found below event flooding my log as per below: can anyone tell what is about:
2020-04-03T04:03:41.263Z cpu45:24942561)WARNING: NetPort: 1934: failed to disable port 0x100000e7 on DvsPortset-1: Busy
2020-04-03T04:03:41.263Z cpu45:24942561)netschedHClk: NetSchedHClkPortQuiesce:4980: vmnic5: received a force quiesce for port 0x100000e7
2020-04-03T04:03:41.263Z cpu45:24942561)netschedHClk: NetSchedHClkHashQuiesceHierarchyIter:396: vmnic5: dropped 13 pkts from queue netsched.pools.persist.default while quiescing port 0x100000e7
2020-04-03T04:03:41.263Z cpu45:24942561)netschedHClk: NetSchedHClkHashQuiesceHierarchyIter:396: vmnic5: dropped 432 pkts from queue netsched.pools.vm.268435687 while quiescing port 0x100000e7
2020-04-03T04:03:41.264Z cpu45:24942561)NetPort: 1881: disabled port 0x100000e7
2020-04-03T04:03:41.268Z cpu45:24942561)Vmxnet3: 17295: Disable Rx queuing; queue size 1024 is larger than Vmxnet3RxQueueLimit limit of 64.
2020-04-03T04:03:41.268Z cpu45:24942561)Vmxnet3: 17653: Using default queue delivery for vmxnet3 for port 0x100000e7
2020-04-03T04:03:41.268Z cpu45:24942561)NetPort: 3208: resuming traffic on DV port 440
2020-04-03T04:03:41.268Z cpu45:24942561)Team.etherswitch: TeamESPolicySet:5942: Port 0x100000e7 frp numUplinks 1 active 1(max 1) standby 0
2020-04-03T04:03:41.268Z cpu45:24942561)Team.etherswitch: TeamESPolicySet:5950: Update: Port 0x100000e7 frp numUplinks 1 active 1(max 1) standby 0
2020-04-03T04:03:41.268Z cpu45:24942561)NetPort: 1662: enabled port 0x100000e7 with mac 00:40:46:8b:5b:d4
2020-04-03T04:03:41.271Z cpu42:24942561)NetPort: 1881: disabled port 0x100000e7
2020-04-03T04:03:41.301Z cpu42:24942561)Vmxnet3: 17295: Disable Rx queuing; queue size 1024 is larger than Vmxnet3RxQueueLimit limit of 64.
2020-04-03T04:03:41.301Z cpu42:24942561)Vmxnet3: 17653: Using default queue delivery for vmxnet3 for port 0x100000e7
2020-04-03T04:03:41.301Z cpu42:24942561)NetPort: 3208: resuming traffic on DV port 440
2020-04-03T04:03:41.301Z cpu42:24942561)Team.etherswitch: TeamESPolicySet:5942: Port 0x100000e7 frp numUplinks 1 active 1(max 1) standby 0
2020-04-03T04:03:41.301Z cpu42:24942561)Team.etherswitch: TeamESPolicySet:5950: Update: Port 0x100000e7 frp numUplinks 1 active 1(max 1) standby 0
2020-04-03T04:03:41.301Z cpu42:24942561)NetPort: 1662: enabled port 0x100000e7 with mac 00:50:56:7b:3b:c4


Hello ThereSystem Administrator
CERTIFIED EXPERT
Distinguished Expert 2018

Commented:
What ESXi version do you have?
https://kb.vmware.com/s/article/2038301
Doodad BoySupprt

Author

Commented:
we having vcenter 6.7 version
Doodad BoySupprt

Author

Commented:
i saw related link as per below, but it does not update with the actual resolution

https://communities.vmware.com/thread/553243
Louis LIETAERSystem Infrastructure Architect
CERTIFIED EXPERT

Commented:
Sorry to insist, have you check the vswitch configuration of your esxi(s) ?
Doodad BoySupprt

Author

Commented:
Please brief what need to be check at vswitch level. please update further
David Johnson, CDSimple Geek from the '70s
CERTIFIED EXPERT
Distinguished Expert 2019

Commented:
what are the settings for the switch? Is it using a NIC that has a network cable attached?
Doodad BoySupprt

Author

Commented:
virtual switch connected to physical Uplinks connected with cable
System Infrastructure Architect
CERTIFIED EXPERT
Commented:
With sphere client, you will have to go configure->network for a selected host.

for each vswitch: check configuration of assigned NIC, for each PortGroup ; check all parameters (vlan, etc).

Working esxi should be the reference, you will have to find the difference of configuration between not working esxi and working esxi.

See attached print screen.
vcenter-network.png

Not the solution you were looking for? Getting a personalized solution is easy.

Ask the Experts
Doodad BoySupprt

Author

Commented:
anyone can update me about the given esxi event log above here
Louis LIETAERSystem Infrastructure Architect
CERTIFIED EXPERT

Commented:
You can have a quick look at portGroup witch vm is attached to (of course)
Hello ThereSystem Administrator
CERTIFIED EXPERT
Distinguished Expert 2018

Commented:
He told us in previous posts that there are more VMs on the host and they are fine. I am not sure it's in the vSwitch.

I checked known networking issues for 6.7. One of them is related to Intel Fortville NICs X710, XL710, and XXV710.
https://docs.vmware.com/en/VMware-vSphere/6.7/rn/vsphere-esxi-vcenter-server-67-release-notes.html#knownissues

Also, a similar issue is described here but it's related to vSphere 6.5. The log showed "vmnicx: dropped ___ pkts from queue" and "failed to disable port ___ on DvsPortset-0: Busy" events and the "only way to recover the VM networking was to vMotion to a different host". Sounds familiar? In this case it was a driver issue.
https://forums.intel.com/s/question/0D50P0000490WHASA2/re-intel-x710-on-huawei-servermalicious-driver-detection-appear-in-the-log?language=en_US
Louis LIETAERSystem Infrastructure Architect
CERTIFIED EXPERT

Commented:
Hi before investigating further, I really want to have vswitch configuration analysis, if not possible issues are infinite.
Doodad BoySupprt

Author

Commented:
Hi all, dvs swicth has been created and assigned to all hosting server in the cluster. The status is connected. and found the few server in the assigned dvs lan able to ping now
Access more of Experts Exchange with a free account
Thanks for using Experts Exchange.

Create a free account to continue.

Limited access with a free account allows you to:

  • View three pieces of content (articles, solutions, posts, and videos)
  • Ask the experts questions (counted toward content limit)
  • Customize your dashboard and profile

*This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.

OR

Please enter a first name

Please enter a last name

8+ characters (letters, numbers, and a symbol)

By clicking, you agree to the Terms of Use and Privacy Policy.