[HCX] VM residing on L2 extended network experiences target router location change unexpectedly
search cancel

[HCX] VM residing on L2 extended network experiences target router location change unexpectedly

book

Article ID: 323661

calendar_today

Updated On:

Products

VMware HCX VMware Cloud on AWS

Issue/Introduction

To outline how to troubleshoot this issue if encountered in the future.

Symptoms:
A virtual machine that resides on a MON enabled L2 extended network has their Target Router Location value changed unexpectedly from "OnPrem" location to "Cloud Tier-1".  This can be following a DRS migration or a snapshot being taken of the VM.

Resolution

If this issue is observed please gather the following.
  • VM name, Segment name, Time stamp of when this change happened (or if unavailable, time stamp of when the change back fixed the connectivity)
  • On-Prem and Cloud vCenter logs
  • Gather screenshots of the VM event logs from vCenter around the time stamp of the interruption
  • On-Prem and Cloud HCX logs <including the database dump>
  • Validate the number of VMs that are residing upon MON enabled segments


Workaround:
Manually change the 'Target Router Location' back to the correct location.

Additional Information

Impact/Risks:
This may result in the VM losing its network connectivity.