- Products
- Learn
- Local User Groups
- Partners
- More
Welcome to Maestro Masters!
Talk to Masters, Engage with Masters, Be a Maestro Master!
Join our TechTalk: Malware 2021 to Present Day
Building a Preventative Cyber Program
Be a CloudMate!
Check out our cloud security exclusive space!
Check Point's Cyber Park is Now Open
Let the Games Begin!
As YOU DESERVE THE BEST SECURITY
Upgrade to our latest GA Jumbo
CheckFlix!
All Videos In One Space
Here is yet another onliner for R77.xx
sqlite3 /var/log/CPView_history/CPViewDB.dat "SELECT datetime(a.Timestamp, 'unixepoch', 'localtime'), a.cluster_status FROM UM_STAT_UM_SYSTEM AS a WHERE a.cluster_status <> ( SELECT b.cluster_status FROM UM_STAT_UM_SYSTEM AS b WHERE a.Timestamp > b.Timestamp ORDER BY b.Timestamp DESC LIMIT 1 );"
Comand shows data for current member like show cluster failover in R80.20:
2019-11-01 15:31:03|Standby
2019-12-02 15:11:15|Down
2019-12-02 15:12:15|Standby
2019-12-02 15:15:15|Active
It is better than
show routed cluster-state detailed
because it shows only real changes excluding info like Jun 16 17:33:36 Master to Master and it shows more older data
And for R80.20 ?
I don't have any R80 on my hand right now so you may test it by yourself 🙂
I discovered this today: -
"cphaprob show_failover"
It shows the last cluster failover event, the failover count and the last 20 failovers since reboot/reset: -
Last cluster failover event:
Transition to new ACTIVE: Member 2 -> Member 1
Reason: Member state has been changed due to higher priority of remote cluster member 1 in PRIMARY-UP cluster
Event time: Thu Nov 21 21:43:49 2019
Cluster failover count:
Failover counter: 43
Time of counter reset: Mon Jun 24 12:44:41 2019 (reboot)
Cluster failover history (last 20 failovers since reboot/reset on Mon Jun 24 12:44:41 2019):
No. Time: Transition: CPU: Reason:
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
1 Thu Nov 21 21:43:49 2019 Member 2 -> Member 1 16 Member state has been changed due to higher priority of remote cluster member 1 in PRIMARY-UP cluster
2 Thu Nov 21 21:32:53 2019 Member 1 -> Member 2 00 Reboot
3 Mon Nov 18 13:06:00 2019 Member 2 -> Member 1 21 Member state has been changed due to higher priority of remote cluster member 1 in PRIMARY-UP cluster
4 Mon Nov 18 13:03:12 2019 Member 1 -> Member 2 00 Reboot
5 Mon Nov 18 11:47:33 2019 Member 2 -> Member 1 04 Member state has been changed due to higher priority of remote cluster member 1 in PRIMARY-UP cluster
6 Mon Nov 18 11:46:53 2019 Member 1 -> Member 2 03 Interface eth1 is down (disconnected / link down)
7 Wed Oct 9 17:13:34 2019 Member 2 -> Member 1 03 Member state has been changed due to higher priority of remote cluster member 1 in PRIMARY-UP cluster
8 Mon Oct 7 15:07:12 2019 Member 2 -> Member 1 10 Member state has been changed due to higher priority of remote cluster member 1 in PRIMARY-UP cluster
9 Mon Oct 7 15:04:45 2019 Member 1 -> Member 2 00 Reboot
10 Thu Sep 12 12:44:39 2019 Member 1 -> Member 2 00 Interface eth3 is down (Cluster Control Protocol packets are not received)
11 Wed Sep 11 11:55:06 2019 Member 2 -> Member 1 01 Member state has been changed due to higher priority of remote cluster member 1 in PRIMARY-UP cluster
12 Wed Sep 11 11:53:52 2019 Member 1 -> Member 2 00 ADMIN_DOWN PNOTE
13 Tue Sep 10 17:32:31 2019 Member 2 -> Member 1 00 Member state has been changed due to higher priority of remote cluster member 1 in PRIMARY-UP cluster
14 Tue Sep 10 16:45:42 2019 Member 1 -> Member 2 00 ADMIN_DOWN PNOTE
15 Tue Sep 10 15:19:41 2019 Member 2 -> Member 1 00 Member state has been changed due to higher priority of remote cluster member 1 in PRIMARY-UP cluster
16 Tue Sep 10 15:18:11 2019 Member 1 -> Member 2 01 ADMIN_DOWN PNOTE
17 Wed Aug 28 15:17:43 2019 Member 2 -> Member 1 22 Member state has been changed due to restart of the Cluster module
18 Wed Aug 28 14:12:45 2019 Member 1 -> Member 2 00 Interface eth1 is down (Cluster Control Protocol packets are not received)
19 Wed Aug 21 18:28:34 2019 Member 2 -> Member 1 00 Member state has been changed after returning from ACTIVE/ACTIVE scenario (remote cluster member 1 has higher priority)
20 Mon Aug 19 15:11:33 2019 Member 2 -> Member 1 00 Member state has been changed after returning from ACTIVE/ACTIVE scenario (remote cluster member 1 has higher priority)
About CheckMates
Learn Check Point
Advanced Learning
YOU DESERVE THE BEST SECURITY