A QRadar administrator added High Availability (HA) to the Event Processor and needs to verify the crossover link status between the primary and secondary hosts. Which commands can be used to verify…

Question

Options

• A/opt/qradar/ha/bin/ha_getstate.sh
• B/opt/qradar/ha/bin/getStatus crossover
• C/opt/qradar/ha/bin/qradar_nettune.pl crossover status
• D/opt/qradar/ha/bin/qradar_nettune.pl linkaggr <interface> status
• E/opt/qradar/ha/bin/ha cstate
• Fcat /proc/drbd

• A
  11% (3)
• B
  7% (2)
• C
  75% (21)
• D
  4% (1)
• F
  4% (1)

Explanation

Two commands directly address crossover link verification in QRadar HA: qradar_nettune.pl crossover status (C) queries the network tuning utility specifically for the crossover interface state between primary and secondary nodes, and ha cstate (E) reports the current HA state, which includes crossover link health as part of its output.

Why the distractors are wrong:

• A (ha_getstate.sh) retrieves general HA state but is not a crossover-specific check.
• B (getStatus crossover) is not a valid QRadar HA command - the syntax doesn't exist.
• D (qradar_nettune.pl linkaggr <interface> status) checks link aggregation (bonded interfaces), not the crossover link - same tool, different subcommand, different purpose.
• F (cat /proc/drbd) shows DRBD disk replication status (data sync between nodes), not the network crossover link.

Memory tip: Think "crossover = network cable between two nodes." The two correct commands both contain words hinting at current network/HA state - crossover explicitly in C, and cstate (current state) in E. If an answer is about disk (drbd) or bonding (linkaggr), it's checking the wrong layer.

No community discussion yet for this question.