Virtual machines fails to ping their gateway

Products

• VMware
• VMware NSX
• VMware vCenter Server
• VMware vSphere ESXi

Issue/Introduction

• Virtual machines fails to ping their gateway
• Running the net-vdr -l -l command displays 0.0.0.0 for virtual machine gateway
• This is displayed as com.vmware.net.vxlan.id = 0xff.ff.ff.ff
• Running the net-vdr -l --route default+edge-1 command to list the routes for a DLR shows that a particular virtual machine does not have the correct Gateway information:
  
  For example:
  

  net-vdr -l --route default+edge-1
  
  VDR default+edge-1 Route Table
  
  Legend: [U: Up], [G: Gateway], [C: Connected], [I: Interface]
  
  Legend: [H: Host], [F: Soft Flush] [!: Reject] [E: ECMP]
  
  Destination  GenMask    Gateway    Flags Ref Origin UpTime Interface
  
  -----------  -------    -------    ----- --- ------ ------ ---------
  
  0.0.0.0      0.0.0.0     #.#.#.#     UGE 349 AUTO 8831326 570d455500000002
  
  #.#.#.# 255.255.255.0    #.#.#.#     UGE 1   AUTO 10835228 570d455500000002
  
  #.#.#.# 255.255.254.0    0.0.0.0     UCI 102 MANUAL 10835394 570d45550000000b --------<VM with the problem>

   
• Running the net-vdr -l -nbr default+edge-1 command to list the mac table for a DLR instance shows that a virtual machine has all zeros for its mac address even after the expiration date.
  
  For example:
  

  # net-vdr -l -nbr default+edge-1
  
  VDR default+edge-1 ARP Information :
  
  Legend: [S: Static], [V: Valid], [P: Proxy], [I: Interface]
  
  Legend: [N: Nascent], [L: Local], [D: Deleted]
  
  Network     Mac               Flags Expiry SrcPort Refcnt Interface
  
  -------     ---               ----- ------ ------- ------ ---------
  
  #.#.#.#  ##:##:##:##:##:##   VI permanent  0       1    570d455500000016
  
  #.#.#.#  ##:##:##:##:##:##   VI permanent  0       1    570d455500000014
  
  #.#.#.#  ##:##:##:##:##:##  VL  503 50332382      1    570d4555000000
  
  #.#.#.#  ##:##:##:##:##:##  VL  490 50332409      1    570d45550000000b
  
  #.#.#.#  00:00:00:00:00:00   NP            0       1    570d45550000000b --------<VM with the problem>
  
  #.#.#.#  ##:##:##:##:##:## VL  521 50332238      1    570d45550000000b

   
• If a virtual machine is in this error state, you do not see the mac appear on the controllers.
  
  For example:
  
  nsx-controller # show control-cluster logical-switches mac-table 5002
   
• Running the net-dvs -l command for a DV port displays all 'ffs' for its mac address.
  
  For example:
  
  com.vmware.common.port.volatile.persist = /vmfs/volumes/<datastore-uuid>/.dvsData/da ## 17 50 ## c2 ab ##-a9 4c ce 5c ## 1d 8f ##/543 , propType = CONFIG
  com.vmware.net.vxlan.cp = 0xff.ff.ff.ff
  propType = CONFIG POLICY
  com.vmware.net.vxlan.id = 0xff.ff.ff.ff -----------------------> all ffffs for vxlan id
  propType = CONFIG POLICY
  com.vmware.net.vxlan.mcastip = 0xff.ff.ff.ff
  propType = CONFIG POLICY

Environment

VMware vSphere Client 5.5
VMware vCenter Server Appliance 5.5.x
VMware NSX for vSphere 6.2.x
VMware vCenter Converter Standalone 6.x
VMware vSphere ESXi 5.5
VMware vCenter Server 6.0.x
VMware vSphere ESXi 6.0
VMware Update Manager 5.5
VMware Update Manager 6.0 Beta
VMware vCenter Server 5.5.x
VMware vCenter Server 6.0 Beta
VMware vCenter Server Appliance 6.0.x
VMware NSX for vSphere 6.4.x
VMware Update Manager 6.0
VMware vSphere ESXi 5.5 Beta

Cause

This issue occurs due to corrupt ports on the DVS.

Resolution

To resolve this issue, please contact Broadcom Technical Support for assistance.

See Creating and managing Broadcom support cases for details on opening a case.