Viewing Critical Devices
In the R81.10.X releases, this command is available starting from the R81.10.15 version.
Description
There are a number of built-in Critical Devices, and the Administrator can define additional Critical Devices.
When a Critical Device reports its state as a "problem", the Cluster Member reports its state as "DOWN".
To see the list of Critical Devices on a Cluster Member, and of all the other Cluster Members, run the commands listed below on the Cluster Member.
|
Critical Device |
Description |
Meaning of the "OK" state |
Meaning of the "problem" state |
||
|---|---|---|---|---|---|
|
|
Monitors all the Critical Devices. |
None of the Critical Devices on this Cluster Member report its state as |
At least one of the Critical Devices on this Cluster Member reports its state as " |
||
|
|
Monitors the state of cluster interfaces. |
All cluster interfaces on this Cluster Member are up (CCP packets are sent and received on all cluster interfaces). |
At least one of the cluster interfaces on this Cluster Member is down (CCP packets are not sent and/or received on time). |
||
|
|
Currently is not used. |
||||
|
|
Monitors CoreXL configuration for inconsistencies on all Cluster Members. |
Number of configured CoreXL Firewall instances on this Cluster Member is the same as on all peer Cluster Members. |
Number of configured CoreXL Firewall instances on this Cluster Member is different from peer Cluster Members. Important - A Cluster Member with a greater number of CoreXL Firewall instances changes its state to DOWN. |
||
|
|
Monitors if Full Sync on this Cluster Member completed successfully. |
This Cluster Member completed Full Sync successfully. |
This Cluster Member was not able to complete Full Sync. |
||
|
|
Monitors if the Security Policy is installed. |
This Cluster Member successfully installed Security Policy. |
Security Policy is not currently installed on this Cluster Member. |
||
|
|
Monitors the ClusterXL process called |
|
|
||
|
|
Runs the cluster Full Sync. |
|
|
||
|
|
Monitors the Gaia process called |
|
|
||
|
|
Monitors the Threat Emulation process called |
|
|
||
|
|
Monitors the Critical Device " |
|
User ran the |
||
|
|
Monitors if " |
This Cluster Member receives cluster state information from peer Cluster Members. |
|
||
|
|
Monitors the probing mechanism on the cluster interfaces. |
CCP packets are received on all cluster interfaces. |
At least one of the cluster interfaces on this Cluster Member does not (or did not) receive CCP packets for 5 seconds. The probing started for the network connected to the affected interface.
|
Syntax
|
|
Where:
|
Command |
Description |
|---|---|
|
|
Shows only the Critical Devices that report their state as " |
|
|
Shows the list of all Critical Devices. |
|
|
When there are no issues on the Cluster Member, shows: When a Critical Device reports a problem, prints only the Critical Devices that report their state as " |
|
|
When there are no issues on the Cluster Member, shows: When a Critical Device reports a problem, prints the Critical Device " |
|
|
When there are no issues on the Cluster Member, shows: When a Critical Device reports a problem, prints only the Critical Devices that report their state as " |
Related topics
Example 1 - "cphaprob list"
There are no Critical Devices that report their state as "problem"
[Expert@Member1]# cphaprob list There are no pnotes in problem state [Expert@Member1]# |
Example 2 - "cphaprob list"
The Critical Devices "Interface Active Check" and "Local Probing" report their state as "problem"
[Expert@Member1]# cphaprob list Built-in Devices: Device Name: Interface Active Check Current state: problem (non-blocking) Registered Devices: Device Name: Local Probing Registration number: 6 Timeout: none Current state: problem Time since last report: 90.5 sec [Expert@Member1]# |
Example 3 - "cphaprob -l list"
Complete list.
All Critical Devices report their state as "OK".
[Expert@Member1]# cphaprob -l list Built-in Devices: Device Name: Interface Active Check Current state: OK Device Name: Recovery Delay Current state: OK Device Name: CoreXL Configuration Current state: OK Registered Devices: Device Name: Fullsync Registration number: 0 Timeout: none Current state: OK Time since last report: 857.8 sec Device Name: Policy Registration number: 1 Timeout: none Current state: OK Time since last report: 857.8 sec Device Name: cphad Registration number: 2 Timeout: 120 sec Current state: OK Time since last report: 883 sec Process Status: UP Device Name: cxld Registration number: 3 Timeout: 120 sec Current state: OK Time since last report: 883 sec Process Status: UP Device Name: routed Registration number: 4 Timeout: none Current state: OK Time since last report: 848.9 sec Device Name: Init Registration number: 5 Timeout: none Current state: OK Time since last report: 878 sec Device Name: Local Probing Registration number: 6 Timeout: none Current state: OK Time since last report: 103.9 sec [Expert@Member1]# |
Example 4 - "cphaprob -l list"
Complete list.
The Critical Devices "Interface Active Check" and "Local Probing" report their state as "problem"
[Expert@Member1]# cphaprob -l list Built-in Devices: Device Name: Interface Active Check Current state: problem (non-blocking) Device Name: Recovery Delay Current state: OK Device Name: CoreXL Configuration Current state: OK Registered Devices: Device Name: Fullsync Registration number: 0 Timeout: none Current state: OK Time since last report: 111.8 sec Device Name: Policy Registration number: 1 Timeout: none Current state: OK Time since last report: 111.8 sec Device Name: cphad Registration number: 2 Timeout: 120 sec Current state: OK Time since last report: 137.3 sec Process Status: UP Device Name: cxld Registration number: 3 Timeout: 120 sec Current state: OK Time since last report: 137.2 sec Process Status: UP Device Name: routed Registration number: 4 Timeout: none Current state: OK Time since last report: 75.7 sec Device Name: Init Registration number: 5 Timeout: none Current state: OK Time since last report: 132.3 sec Device Name: Local Probing Registration number: 6 Timeout: none Current state: problem Time since last report: 124.8 sec [Expert@Member1]# |