A customer reports difficulty joining a standalone High Availability (HA) pair. How should the customer diagnose the issue? Choose 2 answers

Comprehensive and Detailed In-Depth

Joining a standalone HA pair to a Grid involves network, authentication, and sync issues. Best

diagnostics:

A: Syslog (show log syslog) and debug logs (e.g., infoblox.log in support bundle) on both nodes reveal

errors (e.g., “Join failed: invalid secret”). Essential for root cause. Correct.

C: Traffic capture (tcpdump via CLI) on both nodes checks VRRP, bloxSync, and network issues (e.g.,

blocked ports). Comprehensive view of communication. Correct.

B: Capturing only the active node misses passive node issues (e.g., firewall blocking sync).

Incomplete. Incorrect.

D: Resetting erases logs and configs, hindering diagnosis—last resort, not initial step. Incorrect.

Practical Example: In an INE lab, you’d check syslog for “sync failed,” run tcpdump -i eth0 port 443 on

both, and troubleshoot a blocked SSL port.

Reference: Infoblox NIOS Administrator Guide – HA Troubleshooting; INE Course Content: NIOS DDI

Grid Troubleshooting.