Unreachable Collector On Dpu Alarm

Products

• VMware NSX

Issue/Introduction

Event ID: communication.unreachable_collector_on_dpu

Alarm Description:

• Purpose: Check if the configured collector is reachable.
• Impact: The exporting from certain service would not work.

 

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:
    • sshdpu -d {DPU ID}
• Make following checks:
  • Check if there is(are) vmknic(s) with expected stack {stack_alias} created and configured with appropriate IPv4(6) addresses
  • Check if the network connection to {vertical_name} collector {collector_ip} is also fine
  • Check if collector {collector_ip} is reachable:
    • vmkping {collector_ip} -S {stack_alias}
• If there is no vmknic(s) with expected stack {stack_alias} created or the IPv4(6) addresses (is)are not correct, please create vmknic(s) with stack {stack_alias} on DVS {dvs_alias} and configure it with appropriate IPv4(6) address from vCenter. If there is network connection issue, diagnose this issue to make it work. And then check the reachability to the collector again.

Maintenance window required for remediation? NO