Operational Defect Database
BugZero updated this defect 26 days ago.
Data sources
All data on this page is proprietary to BugZero® or gathered from public sources
VMware | 97822
HCX - MON (/32) host route removal post vCenter DRS based vMotion
Last update date:
4/23/2024
Affected products:
HCX
Affected releases:
No affected releases provided.
Fixed releases:
No fixed releases provided.
Description:
Symptoms
HCX Mobility Optimized Networking (MON) configures (/32) host route on target NSX DLR which may get removed during vCenter DRS based vMotion event for a Cloud workload VM sitting over MON enabled extended segment. Below logs will be generated under HCX Cloud manager app.log: [NetworkStretchService_SvcThread-49835, j: fb7bdaec, vm: <mo ref ID of CLOUD VM>, PR, TxId: dea6b0e9-9c2a-48f4-b8fa-121f7522236b] INFO c.v.v.h.n.HandleVMUpdateJob- Possible Vmotion:true, NewHost:<ESXI host ID> OldHost:<ESXI hostID> oldPoweredOn: true [NetworkStretchService_SvcThread-49836, j: a8470158, s: 01aa6a73, , TxId: dea6b0e9-9c2a-48f4-b8fa-121f7522236b] INFO c.v.v.h.n.ConfigureHostRoutesOnEdgeJob- Removing {"network":"<MON enabled VM IP>\/32","next_hops":[{"admin_distance":1,"scope":["\/infra\/segments\/hcx-ne-bbbbbbbbbbbbbbbbbbbbbbbbbb"]}],"enabled_on_secondary":false,"resource_type":"StaticRoutes","id":"xxxxxxxxxxxxxxxxxx","display_name":"HCX Policy based MON for Subnet <MON enabled VM subnet>","path":"\/infra\/tier-1s\/TNT17-T1\/static-routes\/zzzzzzzzzzzzzzzzzzzzzzzzz","relative_path":"yyyyyyyyyyyyyyyyyyyyyyy","parent_path":"\/infra\/tier-1s\/TNT17-T1","unique_id":"aaaaaaaaaaaaaaaaaa","realization_id":"cccccccccccccccccc
Purpose
Identify a known scenario or condition where MON /32 host route gets removed during vCenter DRS based vMotion event of Cloud workload VM.
Cause
When vMotion gets performed for a workload VM sitting over extended segment, the HCX Manager wait for certain amount of time before declaring the Cloud VM IP address as stale.Note: Once its declared to be stale then the existing host route needs to be removed from NSX DLR which is an expected workflow to avoid inactive/stale routes from routing base.As part of current implementations, when Cloud/dst vCenter is unable to send vMotion event completion response within 1min for the workload VM, HCX Manager removes the configured static/host route against that VM.IMPORTANT: vCenter DRS vMotion event depends upon a given infrastructure and may take additional time to complete all vMotion related workflow.
Impact / Risks
The HCX Migration and DR services remain unaffected.The MON enabled workload VM for which the (/32) host route gets removed will face connectivity issues.
Resolution
None at the moment.This behavior will be enhanced in upcoming HCX version to handle such delay occurred during vCenter DRS vMotion event.
Workaround
MON functionality needs to be toggled to re-instate the Network Extension job followed by re-addition of static routes against that workload VM.
Related Information
Refer HCX - Host Route (/32) missing after enabling MON (Mobility Optimized Networking)
