Through the VMware NSX Manager user interface, the administrator has identified an issue with BGP peering. Which command on the NSX Edge Transport Node provides more information about the issue?

Question

Options

• Aget edge-cluster status
• Bget logical-routers
• Cget edge-cluster history state
• Dget log-file routing follow

• A
  4% (1)
• B
  8% (2)
• C
  4% (1)
• D
  85% (22)

Explanation

When troubleshooting BGP peering issues on an NSX Edge Transport Node, VMware documentation directs administrators to examine routing logs, because BGP failures are often caused by adjacency negotiation errors, authentication mismatches, keepalive/hold timer issues, or route-policy failures. The NSX Edge CLI command: get log-file routing follow streams real-time routing logs, including BGP daemon logs (bfdd, routed, wdog) and provides detailed insight into: BGP session establishment and teardown Keepalive and hold timer exchanges Neighbor state transitions Route advertisement or rejection Authentication mismatches MTU or connectivity issues on TEP / uplinks This is the only command in the list that exposes diagnostic-level BGP information needed to troubleshoot peering.

No community discussion yet for this question.