VMware 2V0-15.25 Exam - Topic 5 Question 9 Discussion

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.

Option A (edge-cluster status) shows cluster membership only. Option B (get logical-routers) shows logical router configuration, not BGP logs. Option C (edge-cluster history state) is unrelated to routing.