1 Reply Latest reply on Mar 2, 2018 6:25 PM by daphnissov

    vmotion network config error

    project722 Lurker

      I am having difficulty doing a vmotion migration, or, more accurately, a relocation via vmotion. I am using the vcenter web client. I am getting the error that the "migrations failed because the ESX host were not able to connect over the vmotion network."


      From one ESX host, (we'll call it ESX A)I can see that it can ping the target ESX host (ESX B) vmotion IP but it can only ping it if I specify the vmk port for mgmt, not vmotion, on ESX A.


      Below vmk1 is the vmotion port IP and vmk0 is the mgmt port IP.  vmotion is only enabled on

      vmk1. But, since I CAN ping the target host vmotion port IP ( using vmk0, I'm thinking I may can just enable vmotion on the mgmt port, and it could work. (And disable vmotion on the vmotion port) My main concern with this is freaking out the host if I enable vmotion on the mgmt port as I don't want to bring down this production system.


      Or, is there a way to correct the routing to where vmk1 can ping then ultimately vmotion over the vmotion network like it should work?


      [root@ucs-c1-s1:~] esxcfg-route -l
      VMkernel Routes:
      Network          Netmask          Gateway          Interface      Local Subnet     vmk0           Local Subnet     vmk1          
      default    vmk0       
      [root@ucs-c1-s1:~] vmkping -I vmk0
      PING ( 56 data bytes
      64 bytes from icmp_seq=0 ttl=62 time=0.256 ms
      64 bytes from icmp_seq=1 ttl=62 time=0.254 ms


      --- ping statistics ---
      2 packets transmitted, 2 packets received, 0% packet loss
      round-trip min/avg/max = 0.254/0.255/0.256 ms


      [root@ucs-c1-s1:~] vmkping -I vmk1
      PING ( 56 data bytes


      --- ping statistics ---
      3 packets transmitted, 0 packets received, 100% packet loss