156-115.77 · Question #50
From the output of the following cphaprob -i list, what is the most likely cause of the clustering issue? Cluster B> cphaprob -i list Built-in Devices: Device Name: Interface Active Check Current…
The correct answer is D. Cluster B and Cluster A have different versions of policy installed. See the full explanation below for the reasoning.
Question
From the output of the following cphaprob -i list, what is the most likely cause of the clustering issue? Cluster B> cphaprob -i list Built-in Devices:
Device Name: Interface Active Check Current state: OK Device Name: HA Initialization Current state: OK Device Name: Recovery Delay Current state: OK Registered Devices:
Device Name: Synchronization Registration number: 0 Timeout: none Current state: OK Time since last report: 3651.5 sec Device Name: Filter Registration number: 1 Timeout: none Current state:
problem Time since last report: 139 sec Device Name: routed Registration number: 2 Timeout: none Current state:
OK Time since last report: 3651.9 sec Device Name: cphad Registration number: 3 Timeout: none Current state:
OK Time since last report: 3696.5 sec Device Name: fwd Registration number: 4 Timeout: none Current state: OK Time since last report: 3696.5 sec
Options
- AThere is an interface down on Cluster A
- BThere is a sync network issue between Cluster A and Cluster B
- CThe routing table on Cluster B is different from Cluster A
- DCluster B and Cluster A have different versions of policy installed.
How the community answered
(32 responses)- A6% (2)
- B13% (4)
- C3% (1)
- D78% (25)
Community Discussion
No community discussion yet for this question.