NIOS-DDI-EXPERT practice question 3 of 15

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

Full set: 80 questions
Answer options
A: Use error messages recorded in syslog and debug log on both nodes Correct answer
B: Use traffic capture on the first node (the active node)
C: Use traffic capture on both nodes Correct answer
D: Reset everything before trying to re-join
Correct Answer:
A. Use error messages recorded in syslog and debug log on both nodes; C. Use traffic capture on both nodes
Explanation

Diagnosing a High Availability (HA) join failure requires a systematic approach that examines both application-level and network-level communications. The most effective method is to analyze the syslog and debug logs on both nodes (the active and the passive) to identify specific error messages related to the HA process, such as database replication or VRRP negotiation failures. Simultaneously, performing a traffic capture on both nodes is essential to verify that HA-related traffic (e.g., VRRP, bloxSYNC) is being successfully transmitted and received, which helps to identify network connectivity issues like firewalls or misconfigured switches that may be blocking communication.

Why Incorrect

B. Use traffic capture on the first node (the active node): This provides an incomplete view. A one-sided capture cannot confirm if packets are reaching the peer or if replies are being sent back, which is crucial for diagnosing bidirectional communication issues.
D. Reset everything before trying to re-join: This is a corrective action, not a diagnostic step. Resetting destroys valuable log data and system state information that is essential for identifying the root cause of the failure.

References

1. Infoblox NIOS Administrator Guide 9.0.1, Chapter 26, "Configuring HA Pairs," Section: "Troubleshooting HA Pairs," Page 930. The guide states, "You can view the syslog to monitor the status of an HA pair... The syslog contains messages about the status of the HA nodes and the HA transition." This supports using logs for diagnosis. The guide also emphasizes verifying network connectivity, for which traffic capture is the definitive tool: "Ensure that there are no firewalls, routers with access lists, or other filtering devices between the HA members..."

2. Infoblox Knowledge Base Article #1355, "Troubleshooting HA Join Failure." This official support document outlines a standard procedure for diagnosing HA issues. It explicitly recommends (1) checking the syslog on both nodes for error messages and (2) using tcpdump (the command-line packet capture utility) on both nodes to verify connectivity on required ports (e.g., VRRP, bloxSYNC, database replication), confirming that traffic is both sent and received. This directly supports using logs and dual-node traffic captures as primary diagnostic steps.

Scroll to Top