PrepAway - Latest Free Exam Questions & Answers

what is the most likely cause of the clustering issue?

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

PrepAway - Latest Free Exam Questions & Answers

A.
There is an interface down on Cluster A

B.
There is a sync network issue between Cluster A and Cluster B

C.
The routing table on Cluster B is different from Cluster A

D.
Cluster B and Cluster A have different versions of policy installed.

2 Comments on “what is the most likely cause of the clustering issue?

  1. wonhunglo says:

    D. Cluster B and Cluster A have different versions of policy installed.

    sk55081

    Section 2, Default Critical Devices:
    Filter | Shows the success or failure of loading the Security Policy (whether the Policy was/is installed or not).

    Section 3, Simulating cluster failure

    A user might want to simulate a cluster failure by causing one of the default Critical Devices to report a problem.

    Examples:

    Unplugging a cable from a cluster interface – a problem will be reported by the “Interface Active Check” pnote.
    Shutting down a cluster interface – a problem will be reported by the “Interface Active Check” pnote.
    Unloading the Security Policy – a problem will be reported by the “Filter” pnote.
    Stopping FWD daemon – a problem will be reported by the “FWD” pnote.




    0



    0
  2. wonhunglo says:

    For the sake of cleaning up the formatting of the question, here you go:

    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




    1



    0

Leave a Reply