Limited Reachability On Dpu Alarm

Products

• VMware NSX

Issue/Introduction

Event ID: communication.limited_reachability_on_dpu

Alarm Description:

• Purpose: Check if the configured collector is reachable via the same DVS where the vertical is enabled.
• Impact: The exporting from certain service might be broken in future if the another DVS migrates to another DPU or moves back to ESXi.

Environment

VMware NSX

Resolution

Steps to Resolve

For 4.0.1 and higher

Recommendation:

• Login the DPU as root:
  • Find out the ID of the DPU according to the DPU UUID:
    • In the NSX UI, navigate to "System | Fabric | Hosts | Clusters" or "System | Fabric | Hosts | Other Nodes"
    • Anchor the transport node by the "Reported by Node" in alarm, then go to "View Details | Monitor | System Usage"
    • Check the DPU under System Usage one by one to find the one reporting the alarm by checking its UUID
  • Login ESXi node(Reported by Node) at first:
    • ssh root {Reported by Node}
  • Jump to ESXio with DPU ID specified:
    • vim-cmd combinersvc/dpu_services/start TSM-SSH {DPU ID}
    • sshdpu -d {DPU ID}
• Create vmknic(s) with stack {stack_alias} on DVS {dvs_alias} and configure it with appropriate IPv4(6) address from vCenter.
• Check if the {vertical_name} collector {collector_ip} can be reached via the newly-created vmknic(s) on DPU:
  • Get the interface name for the newly-created vmknic(s):
    • esxcfg-vmknic -l | grep -i {stack_alias}
  • vmkping {collector_ip} -S {stack_alias} -I vmkX

Maintenance window required for remediation? NO