An administrator logs into the VMware NSX Manage UI and observes a "Remote Logging Not Configured" alarm for each NSX Management node. What is a possible reason for this issue?

Question

Options

• AUpdate the NSX Edge Cluster Profile to configure a remote logging server.
• BUpdate the NSX Uplink Profile to configure a remote logging server.
• CUpdate the NSX Node Profile to configure a remote logging server.
• DUpdate the NSX Configuration Profile to configure a remote logging server.

• A
  13% (8)
• B
  3% (2)
• C
  77% (49)
• D
  8% (5)

Explanation

The "Remote Logging Not Configured" alarm in NSX Manager is a system-health alert indicating that one or more Transport Nodes (Edges or Hypervisors) or Management Nodes do not have a Syslog server defined. NSX Node Profiles: In VMware NSX (and by extension VCF), the standard method to apply consistent administrative settings--such as Syslog Servers, NTP settings, and Core Dump configurations--across a fleet of nodes is to use an NSX Node Profile. Configuration Path: The administrator should navigate to System > Fabric > Profiles > Node Profiles. Here, they can create or edit a profile that specifies the remote syslog server's IP/FQDN, port, and protocol. Application: Once the Node Profile is applied to the NSX Management Cluster or Edge Clusters, the configuration is pushed to all respective appliances, clearing the alarm.

No community discussion yet for this question.