VM failed to Ping after a vMotion

VM failed to Ping after a vMotion

Hello All,

Recently I have experienced an issue after vMotion a Virtual Machine. Virtual Machine has stopped responding to Ping response just after it got migrated to a new Host.

I did check VM Network and Other Virtual Machines which were hosted on same ESXi and Same VM Network and could not found any issue. Finally i took ssh and reviewed vmkernel.log file. and found below entries in the log file.

/var/log # cat vmkernel.log |grep 0x300000a

2017-11-09T12:23:37.587Z cpu26:49280)Net: 2312: connected dfwlxplant31.eth0 eth0 to vDS, portID 0x300000a

2017-11-09T12:23:37.587Z cpu26:49280)Net: 3127: associated dvPort 23922 with portID 0x300000a

2017-11-09T12:23:37.591Z cpu26:49280)Team.etherswitch: TeamESPolicySet:5519: Port 0x300000a frp numUplinks 4 active 4(max 4) standby 0

2017-11-09T12:23:37.591Z cpu26:49280)Team.etherswitch: TeamESPolicySet:5527: Update: Port 0x300000a frp numUplinks 4 active 4(max 4) standby 0

2017-11-09T12:23:37.591Z cpu26:49280)NetPort: 1426: enabled port 0x300000a with mac 00:50:56:8d:74:e0

2017-11-09T12:26:39.280Z cpu18:49280)NetPort: 1632: disabled port 0x300000a

2017-11-09T12:26:40.822Z cpu24:32906)Net: 3348: dissociate dvPort 23922 from port 0x300000a

2017-11-09T12:26:40.822Z cpu24:32906)Net: 3354: disconnected client from port 0x300000a

Above logs clearly shows that VM Network did not resume after the vMotion on specified Port ID.

Resolution: In my case I updated Network Firmware and Drivers for NIC Card and it resolved the issue.

Thanks

Jatin

Comments

Hello, Jatin!

Who is vendor of your hardware? I have similar issue with new blade equipment...

Version history
Revision #:
1 of 1
Last update:
‎11-13-2017 08:22 AM
Updated by: