What is a likely cause of the Secondary state being Unknown after moving to a new switch and capturing traffic?

• A. The firewall is blocking communication between the switches.
• B. The administrator made both NetScalers Primary.
• C. The Secondary NetScaler CANNOT communicate in HA when moved to a new switch.
• D. The remote procedure call (RPC) nodes are NOT configured correctly.

Answer: (D)

In NetScaler high availability, the devices exchange control information through RPC nodes to coordinate state and failover. If the RPC nodes are not configured correctly, the two appliances cannot establish or maintain that inter-node communication, so the secondary’s status can appear Unknown. Moving to a new switch can disrupt this channel if the RPC configuration isn’t updated to reflect the new network paths or IPs, leaving the secondary unable to communicate with the primary. That’s why ensuring the RPC node configuration is correct and that the pair can reach each other on the required paths resolves the Unknown state. The other options describe possible symptoms or impossible setups rather than the root cause in this scenario.